ssvnc: Fails to build source after successful build

Bug #2053196 reported by Vladimir Petko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ssvnc (Debian)
New
Unknown
ssvnc (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

his package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S
> ------------------------------------------------------------------------------------------------------------------
>
> dpkg-buildpackage: info: source package ssvnc
> dpkg-buildpackage: info: source version 1.0.29-6
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Magnus Holmgren <email address hidden>
> dpkg-source --before-build .
> fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-stamp configure-stamp
> /usr/bin/make clean
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> cd vnc_unixsrc/libvncauth; /usr/bin/make clean
> make[2]: Entering directory '/<<PKGBUILDDIR>>/vnc_unixsrc/libvncauth'
> rm -f libvncauth.a vncauth.o d3des.o
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/vnc_unixsrc/libvncauth'
> cd vnc_unixsrc/vncviewer; /usr/bin/make clean
> make[2]: Entering directory '/<<PKGBUILDDIR>>/vnc_unixsrc/vncviewer'
> rm -f vncviewer argsresources.o caps.o colour.o cursor.o desktop.o dialogs.o fullscreen.o listen.o misc.o popup.o rfbproto.o selection.o shm.o sockets.o tunnel.o vncviewer.o
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/vnc_unixsrc/vncviewer'
> if [ "Xultraftp" != "X" ]; then cd ultraftp; /usr/bin/make clean; fi
> make[2]: Entering directory '/<<PKGBUILDDIR>>/ultraftp'
> rm -f *.class *.jar
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/ultraftp'
> cd vncstorepw; /usr/bin/make clean
> make[2]: Entering directory '/<<PKGBUILDDIR>>/vncstorepw'
> rm -f *.o vncstorepw unwrap.so lim_accept.so ultravnc_dsm_helper
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/vncstorepw'
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> rm vnc_unixsrc/*/Makefile
> rm: cannot remove 'vnc_unixsrc/*/Makefile': No such file or directory
> make: *** [debian/rules:41: clean] Error 1
> dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2
>
> E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S' failed to run.

The full build log is available from:
http://qa-logs.debian.net/2023/08/13/ssvnc_1.0.29-6_unstable.log

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Related branches

Revision history for this message
Vladimir Petko (vpa1977) wrote :

build source package after successfull build (pass)

Changed in ssvnc (Debian):
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ssvnc - 1.0.29-6ubuntu1

---------------
ssvnc (1.0.29-6ubuntu1) noble; urgency=medium

  * d/rules: use java_compat_level variable provided by java-common
    to adjust -source/-target level to the minimum required by
    the default Java (LP: #2053195).
  * d/rules: force deletion of vnc_unixsrc/*/Makefile (LP: #2053196).

 -- Vladimir Petko <email address hidden> Thu, 15 Feb 2024 10:55:51 +1300

Changed in ssvnc (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.