Processed: Bug#963971 marked as pending in samba
Processing control commands: > tag -1 pending Bug #963971 [samba-libs] samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency Added tag(s) pending. -- 963971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963971: marked as pending in samba
Control: tag -1 pending Hello, Bug #963971 in samba reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/samba-team/samba/-/commit/a3504968b70842d17ee82363975d34c6f694e6ef Add Breaks: sssd-ad-common (<< 2.3.0), due to libndr so bump (Closes: #963971) (this message was generated automatically) -- Greetings https://bugs.debian.org/963971
Bug#959075: Still not working on Debian testing
On Fri, 3 Jul 2020 11:15:30 +0200 richard lucassen wrote: > Ok, two remaining cometic issues in 2.11 than :-) Sounds like the issue is fixed then, marked it as fixed. > # ifup bond0 > /etc/network/if-pre-up.d/ifenslave: 39: echo: echo: I/O error > /etc/network/if-pre-up.d/ifenslave: 39: echo: echo: I/O error > > You get this error when you try to set a /sys/ option that is not > allowed, but the script does not tell which option throws an error. See > diff attached. I'll apply the patch you sent in another upload. > Another cosmetic issue: > > # ifdown bond0 > # modprobe -rv bonding > rmmod bonding > # ifup bond0 > RTNETLINK answers: File exists > # Is this a regression from 2.9 or just an old bug still present? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: fixed 959075 in 2.11, closing 959075
Processing commands for cont...@bugs.debian.org: > fixed 959075 2.11 Bug #959075 [ifenslave] ifupdown: Bonding is not working with ifenslave 2.10 wich removes ifenslave command Bug #959236 [ifenslave] Bringing up a bond results in an infinite loop Marked as fixed in versions ifenslave/2.11. Marked as fixed in versions ifenslave/2.11. > close 959075 Bug #959075 [ifenslave] ifupdown: Bonding is not working with ifenslave 2.10 wich removes ifenslave command Bug #959236 [ifenslave] Bringing up a bond results in an infinite loop Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 959075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959075 959236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 5 errors): Re: [Pkg-samba-maint] Bug#963971: samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency
Processing commands for cont...@bugs.debian.org: > clone 963971 -1 Bug #963971 [samba-libs] samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency Bug 963971 cloned as bug 964240 > tag 963971 + upstream Bug #963971 [samba-libs] samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency Added tag(s) upstream. > tag -1 + upstream fixed-upstream patch Bug #964240 [samba-libs] samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency Added tag(s) upstream, patch, and fixed-upstream. > reassign -1 sssd-ad-common Bug #964240 [samba-libs] samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency Bug reassigned from package 'samba-libs' to 'sssd-ad-common'. No longer marked as found in versions samba/2:4.12.3+dfsg-2. Ignoring request to alter fixed versions of bug #964240 to the same values previously set > Le lun. 29 juin 2020 à 14:48, Michael Stone a écrit : Unknown command or malformed arguments to command. > > Unknown command or malformed arguments to command. > > Package: samba-libs Unknown command or malformed arguments to command. > > Version: 2:4.12.3+dfsg-2 Unknown command or malformed arguments to command. > > Severity: critical Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 963971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963971 964240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964240 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963971: [Pkg-samba-maint] Bug#963971: samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency
clone 963971 -1 tag 963971 + upstream tag -1 + upstream fixed-upstream patch reassign -1 sssd-ad-common Le lun. 29 juin 2020 à 14:48, Michael Stone a écrit : > > Package: samba-libs > Version: 2:4.12.3+dfsg-2 > Severity: critical > Justification: breaks the whole system > > The new samba-libs package changes the soname of libndr from libndr.so.0 to > libndr.so.1 without reflecting this change in the package name. sssd-ad-common > has a dependency on samba-libs (>= 2:4.11.5+dfsg) and links to libndr.so.0. > When the samba-libs package is updated and libndr.so.0 disappears sssd fails > to > start, which then makes a system's remote users unavailable. (Worse, this > doesn't happen until the next time sssd restarts--which may not be until the > next reboot.) It looks to be fixed in sssd 2.3.0: https://github.com/SSSD/sssd/commit/bc56b10aea999284458dcc293b54cf65288e325d I'm cloning this bug: - on the samba side I'll add a breaks: sssd-ad-common (<< 2.3.0) - on the sssd side, an update to 2.3.0+ is needed Regards -- Mathieu Parent
Bug#964234: dpkg-source: Considers missing symlink targets directory traversals
Control: reassign -1 dpkg-dev Control: retitle -1 dpkg-source: Considers missing symlink targets directory traversals Control: found -1 1.20.0 On Sat, 2020-07-04 at 01:20:18 +0200, Andreas Beckmann wrote: > Source: dpkg,firmware-nonfree > Version: 20190717-2 > Severity: serious > Tags: ftbfs > Justification: fails to build from source > Control: found -1 20190717-2 > Control: found -1 1.20.3 > src:firmware-nonfree fails to unpack in sid with latest dpkg: > > dpkg-source: info: extracting firmware-nonfree in firmware-nonfree-20190717 > dpkg-source: info: unpacking firmware-nonfree_20190717.orig.tar.xz > dpkg-source: info: unpacking firmware-nonfree_20190717-2.debian.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: applying gitignore.patch > Use of uninitialized value $canon_pathname in pattern match (m//) at > /usr/share/perl5/Dpkg/Source/Package.pm line 550. > dpkg-source: error: pathname > 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points > outside source root > > Since this could also be a dpkg error (see the perl warning before the > failure) > I'm assigning this bug to both packages, please reassign as appropriate. It is, the pathname above is a symlink to a missing target, which is definitely not a directory traversal attempt. I'm fixing this now, and will upload tomorrow. Thanks, Guillem
Processed: Re: Bug#964234: dpkg-source: Considers missing symlink targets directory traversals
Processing control commands: > reassign -1 dpkg-dev Bug #964234 [src:dpkg,src:firmware-nonfree] dpkg,firmware-nonfree: cannot unpack: dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root Bug reassigned from package 'src:dpkg,src:firmware-nonfree' to 'dpkg-dev'. No longer marked as found in versions dpkg/20190717-2, dpkg,firmware-nonfree/20190717-2, dpkg/1.20.3, firmware-nonfree/1.20.3, and firmware-nonfree/20190717-2. Ignoring request to alter fixed versions of bug #964234 to the same values previously set > retitle -1 dpkg-source: Considers missing symlink targets directory traversals Bug #964234 [dpkg-dev] dpkg,firmware-nonfree: cannot unpack: dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root Changed Bug title to 'dpkg-source: Considers missing symlink targets directory traversals' from 'dpkg,firmware-nonfree: cannot unpack: dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root'. > found -1 1.20.0 Bug #964234 [dpkg-dev] dpkg-source: Considers missing symlink targets directory traversals Marked as found in versions dpkg/1.20.0. -- 964234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#940017: crypto-policies: Incomplete debian/copyright?
On Wednesday, September 11, 2019 4:03:59 AM EDT Chris Lamb wrote: > I just ACCEPTed minder from NEW but noticed it was missing attribution > for at least Tomáš Mráz. This bug is against crypto-policies, but it appears you accepted minder too the same day. Did you mean to file this against minder? signature.asc Description: This is a digitally signed message part.
Bug#964234: dpkg,firmware-nonfree: cannot unpack: dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root
Hi Andreas, > dpkg-source: error: pathname > points outside source root Maybe the same as Bug#964111? Kind regards Felix Lechner
Bug#964234: dpkg,firmware-nonfree: cannot unpack: dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root
Source: dpkg,firmware-nonfree Version: 20190717-2 Severity: serious Tags: ftbfs Justification: fails to build from source Control: found -1 20190717-2 Control: found -1 1.20.3 Hi, src:firmware-nonfree fails to unpack in sid with latest dpkg: dpkg-source: info: extracting firmware-nonfree in firmware-nonfree-20190717 dpkg-source: info: unpacking firmware-nonfree_20190717.orig.tar.xz dpkg-source: info: unpacking firmware-nonfree_20190717-2.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying gitignore.patch Use of uninitialized value $canon_pathname in pattern match (m//) at /usr/share/perl5/Dpkg/Source/Package.pm line 550. dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root Since this could also be a dpkg error (see the perl warning before the failure) I'm assigning this bug to both packages, please reassign as appropriate. Andreas
Processed: dpkg,firmware-nonfree: cannot unpack: dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root
Processing control commands: > found -1 20190717-2 Bug #964234 [src:dpkg,src:firmware-nonfree] dpkg,firmware-nonfree: cannot unpack: dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root The source 'dpkg' and version '20190717-2' do not appear to match any binary packages Marked as found in versions firmware-nonfree/20190717-2 and dpkg/20190717-2. > found -1 1.20.3 Bug #964234 [src:dpkg,src:firmware-nonfree] dpkg,firmware-nonfree: cannot unpack: dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root The source 'firmware-nonfree' and version '1.20.3' do not appear to match any binary packages Marked as found in versions dpkg/1.20.3 and firmware-nonfree/1.20.3. -- 964234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964208: wsjtx: FTBFS without internet access
Hi Niko, On Fri, Jul 03, 2020 at 07:47:21PM +0300, Niko Tyni wrote: > Source: wsjtx > Version: 2.2.1+repack-1 > Severity: serious > Tags: ftbfs > > This package fails to build on a system without internet access. > I suppose it's xsltproc calling out for external resources or something > like that. > > This is probably the cause for the 2.2.2+repack-1 armhf build failure too; > I think the conova buildds only have IPv6 connectivity. Thank you for connecting the dots... I reproduced this exact build failure on amd64 by disabling the network. > From the build log: > > a2x: ERROR: "xsltproc" -param man.endnotes.list.enabled 0 -param > man.endnotes.are.numbered 0 --stringparam callout.graphics 0 --stringparam > navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics > 0 "/etc/asciidoc/docbook-xsl/manpage.xsl" > "/<>/obj-x86_64-linux-gnu/manpages/man/man1/wsjtx.1.xml" > returned non-zero exit status 5 Cheers, tony signature.asc Description: PGP signature
Processed: owner 964208
Processing commands for cont...@bugs.debian.org: > owner 964208 tmanc...@debian.org Bug #964208 [src:wsjtx] wsjtx: FTBFS without internet access Owner recorded as tmanc...@debian.org. > thanks Stopping processing here. Please contact me if you need assistance. -- 964208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960407: marked as done (hexter: gtk interface segfaults)
Your message dated Fri, 03 Jul 2020 22:19:24 + with message-id and subject line Bug#960407: fixed in hexter 1.1.0-7 has caused the Debian Bug report #960407, regarding hexter: gtk interface segfaults to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 960407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: hexter Version: 1.1.0-5 Severity: grave Justification: renders package unusable The package currently in unstable segfaults when it tries to run its gtk gui: hexter_gtk starting (pid 6866)... Gtk-Message: 12:49:06.836: Failed to load module "atk-bridge" Segmentation fault (core dumped) Downgrading to version 1.0.3-3+b1 in buster works. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.10-rt4 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: default Versions of packages hexter depends on: ii dssi-host-jack 1.1.1~dfsg0-4 ii libasound2 1.2.2-2.1 ii libc62.30-8 ii libcairo21.16.0-4 ii libglib2.0-0 2.64.2-1 ii libgtk2.0-0 2.24.32-4 ii liblo7 0.30-3 ii libpango-1.0-0 1.44.7-4 ii libpangocairo-1.0-0 1.44.7-4 hexter recommends no packages. hexter suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: hexter Source-Version: 1.1.0-7 Done: Dennis Braun We believe that the bug you reported is fixed in the latest version of hexter, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dennis Braun (supplier of updated hexter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Jul 2020 22:58:28 +0200 Source: hexter Architecture: source Version: 1.1.0-7 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dennis Braun Closes: 960407 Changes: hexter (1.1.0-7) unstable; urgency=medium . * Fix segfault on startup (Closes: #960407) Checksums-Sha1: 39472416ecfd2c65e30ceb3f3e17a59871e4ef33 2088 hexter_1.1.0-7.dsc dc7df9284dea27d69f378e536f363103f0e4c81c 28504 hexter_1.1.0-7.debian.tar.xz Checksums-Sha256: 64149ab50d96bf3ba9348557801ade335a692b477cd23c28f6019ddcbc8cd3df 2088 hexter_1.1.0-7.dsc 6cb4a975d49221e3a9b04ebbfcab6b06e6558f19261355c6942ccaaa7e9f0b47 28504 hexter_1.1.0-7.debian.tar.xz Files: 635b18b0618556420a8076ddd41723a7 2088 sound optional hexter_1.1.0-7.dsc 3e3af377be8126fb9ddbe1dc2aa6ba96 28504 sound optional hexter_1.1.0-7.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl7/q9kACgkQafL8UW6n GZPM0Q//VdXJQorlniTu8C4o1Ep+0LBC+CWqaIBZMJVHE+1z3zDwjgZhX5YtL4If /CeUP2IuqCfH2bikcOTT0Gw6+aZpT4ZrgSKs8dtjzpiCRVkRN646NwjoGw1JysDn v3/34KBbfdryCcjxAi5q2hF2zghSoTn26cOViizxF9Y8JUkxnSNAHL+fsaPA8K1i l3nuOfDd4WB0GZVChuOkD1uKnz1IibDAga/EiPKhH+EaJebcjPP3au5BYcXHbTkV IE6dQ9RQIOFArDm4mcuZsXQIh4/aBe4jgR7UXPPSQfgVS6UA5kvjUTGwsR+VJkb5 dyfb76rY2A/4wo2itO2KiMGEsmv8PlLvtTkSV4cjgjj/3+js3qItMJNJfSLcxoFf TYSFXLsfzbtzgmUXDFQ9qS6paSgG6Qdz9e0dFaLli36RgeG15FI7c5fbbyqDglw0 PWdfJzziFMlVKUglbW4wKAINGQhZQHRrs71whQ6phVDLC8n0jibr6h+3E9bp6b0S emgmuWgbrpoFr0oSdE36L00Buu2MYC/DinGumrX2gI93AypeK5hICgtiiSafVABy Q+oddRiwLcnAGpegwB/6gjTs5gJ759oG4WLKNodH4xFdoC3krrKtGVNMtAFfoaMc 9MHSoStUdLEt8tGa3DAdgKO6mt4kpCDC41y7Yx76TGvAR2R/fiY= =3ihH -END PGP SIGNATURE End Message ---
Processed: Bug#960407 marked as pending in hexter
Processing control commands: > tag -1 pending Bug #960407 [hexter] hexter: gtk interface segfaults Added tag(s) pending. -- 960407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960407 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960407: marked as pending in hexter
Control: tag -1 pending Hello, Bug #960407 in hexter reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/hexter/-/commit/799ea5ddcbfeb0fb3d83b54a0a08702175699496 Fix segfault on startup (Closes: #960407) (this message was generated automatically) -- Greetings https://bugs.debian.org/960407
Bug#953416: marked as done (php-horde-javascriptminify-jsmin: needs binary upload)
Your message dated Fri, 03 Jul 2020 20:41:13 + with message-id <20200703204113.horde.pzpvifjuiqmlljnqrbd7...@mail.das-netzwerkteam.de> and subject line non-free autobuilds now enabled has caused the Debian Bug report #953416, regarding php-horde-javascriptminify-jsmin: needs binary upload to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 953416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: src:php-horde-javascriptminify-jsmin version: 1.0.2-6 severity: serious tags: ftbfs Hi, The latest upload of php-horde-javascriptminify-jsmin to unstable has no binaries, because the buildds are not building it (it is non-free). If the binaries can be auto-built, the package should be whitelisted, as described in https://www.debian.org/doc/manuals/developers-reference/pkgs.html#non-free-buildd If not, a binary upload must be done (note that binary uploads for sources in contrib and non-free are allowed to migrate to testing). Cheers, Ivo --- End Message --- --- Begin Message --- Just received feedback from Philipp Kern that autobuilds for php-horde-javascriptminify-jsmin are now enabled. Thus, closing this issue. Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpOybDk8JBDQ.pgp Description: Digitale PGP-Signatur --- End Message ---
Bug#964185: marked as done (freetype2.pc depends on libbrotlidec.pc without a dependency on the libbrotli-dev package)
Your message dated Fri, 03 Jul 2020 20:34:37 + with message-id and subject line Bug#964185: fixed in freetype 2.10.2+dfsg-2 has caused the Debian Bug report #964185, regarding freetype2.pc depends on libbrotlidec.pc without a dependency on the libbrotli-dev package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libfreetype6-dev Version: 2.10.2+dfsg-1 Severity: serious Firefox failed to build with: ERROR: Package libbrotlidec was not found in the pkg-config search path. ERROR: Perhaps you should add the directory containing `libbrotlidec.pc' ERROR: to the PKG_CONFIG_PATH environment variable ERROR: Package 'libbrotlidec', required by 'freetype2', not found See e.g. https://buildd.debian.org/status/fetch.php?pkg=firefox=amd64=78.0.1-1=1593768167=0 The problem is that freetype2.pc has a new dependency on libbrotlidec.pc, but that is not reflected in the package dependencies. Arguably, freetype2.pc shouldn't depend on libbrotlidec.pc except with a Required.private, assuming one doesn't actually need to include libbrotli headers or link against libbrotli library (presumably, that's the case). Mike --- End Message --- --- Begin Message --- Source: freetype Source-Version: 2.10.2+dfsg-2 Done: Hugh McMaster We believe that the bug you reported is fixed in the latest version of freetype, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hugh McMaster (supplier of updated freetype package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Jul 2020 22:40:45 +1000 Source: freetype Architecture: source Version: 2.10.2+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Hugh McMaster Changed-By: Hugh McMaster Closes: 964185 Changes: freetype (2.10.2+dfsg-2) unstable; urgency=medium . * debian/control: Add libbrotli-dev as a dependency of libfreetype-dev (Closes: #964185). Checksums-Sha1: d456cdeaf99e83934a58261bee81b8dc9c9cb3dc 3609 freetype_2.10.2+dfsg-2.dsc 48715ee4afd084c73b01b1cc2e1049fda101e785 115356 freetype_2.10.2+dfsg-2.debian.tar.xz 24e9fe8bb602546eb60348130513a099b9e30dcc 8402 freetype_2.10.2+dfsg-2_amd64.buildinfo Checksums-Sha256: 102d417b3aac0db6496ed1499d42c76522123427d0fc0d9986eb150b5b4c230e 3609 freetype_2.10.2+dfsg-2.dsc 3d635e093195ee93bd409ffb8afcc8eff93a880c768dfaf48c72f82abe84f212 115356 freetype_2.10.2+dfsg-2.debian.tar.xz 15986ff476ab7b6204b1495cc6f2015f82dfb09de1fb0990d854fd8dbda727be 8402 freetype_2.10.2+dfsg-2_amd64.buildinfo Files: 7eaa175a819edae29045978c38963788 3609 libs optional freetype_2.10.2+dfsg-2.dsc 3ece6f4c4adfa1f4d3c92db7a5b1d530 115356 libs optional freetype_2.10.2+dfsg-2.debian.tar.xz f554ed221fa3d95ea9c17868ef8b9b43 8402 libs optional freetype_2.10.2+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAl7/kakACgkQCBa54Yx2 K61WxhAAhpspMsTRhb4s++Txdm4WoQXlQ+21dBZbw2b79yzbxYMhKh9pAA28FSRM EOLS03jGMorwrbhMFM887ROKDiQj1UrlCTAykFKtAXLS4BoTHxw2VHJT95eych7S XvoNM1dpePoTXp6bhNiWIbf22Q7JPDCix/898rZ7eCfyqR5vZEHz0oIpOswkJRAZ xcfxywJr3q3VMmcdZuPArVsRLN2NsWTbBXo+PEOygmgiWr7O3ThMB33HhFKjeBG+ R0UBxIkBU/KCjknV5L4ODhlwdr0Lnho+41lYpfWj+qgx0O7qesVXUNg8ViVj7FXh +iuWWisoHXRWxwjB7PH81IpuEWm6GtXWckN35gqa1OsplnG+Yevtj5wQoD9ZKjST eX4PaUpK/fr6SfItLJznVqkQkPhe9lyjt0wHFMX6N6PIViZw++xaeHB6va0Qx9Ck dswTwYdeuCFLEVXcxFyIWnQRG5URmKB4Tq330J0kyZFd5DhHy981lPJ2fyZw6LEJ ImdZ0RcgTUc9TPP1h3ojK3Kw9Jxmg4zOGopxoBZgL5eGUIJJ7Tox5h09+fVOiJnv 5JuiwMSPk1jSw0VJ9Ta2GuH/zRI4QCHN/ONNQSFPn5EcEgsQq3+dUw5aCFtIT1rw 6Qw69imRqWsl3LryeK1HQ40D3xgoiN++kOWw4tetzADnxsZEaYg= =5aeN -END PGP SIGNATURE End Message ---
Bug#893203: marked as done (src:collada2gltf: FTBFS with rapidjson 1.0.2)
Your message dated Fri, 03 Jul 2020 18:48:48 + with message-id and subject line Bug#893203: fixed in collada2gltf 20140924-6 has caused the Debian Bug report #893203, regarding src:collada2gltf: FTBFS with rapidjson 1.0.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 893203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:collada2gltf Version: 20140924-4 Severity: serious Forwarded: https://github.com/KhronosGroup/glTF/issues/417 Tags: sid Dear Maintainer, as said in the above github issue: " Unfortunately, the (already deprecated in 0.11/0.12 git) FileStream class/filestream.h got removed completely, so the build of COLLADA2GLTF with rapidjson 1.0.2 fails: [ 2%] Building CXX object CMakeFiles/collada2gltfConvert.dir/COLLADA2GLTFWriter.cpp.o /usr/bin/c++ -DLIBXML_STATIC_FOR_DLL -DSTATIC_COLLADA2GLTF -DUSE_LIBPNG -DUSE_OPEN3DGC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -std=c++11 -I/home/rene/tmp/collada2gltf-20140924 -I/home/rene/tmp/collada2gltf-20140924/GLTF -I/home/rene/tmp/collada2gltf-20140924/JSON -I/home/rene/tmp/collada2gltf-20140924/shaders -I/home/rene/tmp/collada2gltf-20140924/helpers -I/home/rene/tmp/collada2gltf-20140924/convert -I/home/rene/tmp/collada2gltf-20140924/assetModifiers -I/usr/include/rapidjson -I/usr/include/opencollada/COLLADAFramework -I/usr/include/opencollada/COLLADABaseUtils -I/usr/include/opencollada/COLLADASaxFrameworkLoader -I/usr/include/opencollada/GeneratedSaxParser -I/home/rene/tmp/collada2gltf-20140924/extensions/o3dgc-compression -I/usr/include/o3dgc -fPIC -o CMakeFiles/collada2gltfConvert.dir/COLLADA2GLTFWriter.cpp.o -c /home/rene/tmp/collada2gltf-20140924/COLLADA2GLTFWriter.cpp In file included from /home/rene/tmp/collada2gltf-20140924/COLLADA2GLTFWriter.h:30:0, from /home/rene/tmp/collada2gltf-20140924/COLLADA2GLTFWriter.cpp:28: /home/rene/tmp/collada2gltf-20140924/GLTF/GLTF.h:55:24: fatal error: filestream.h: No such file or directory compilation terminated. CMakeFiles/collada2gltfConvert.dir/build.make:65: recipe for target 'CMakeFiles/collada2gltfConvert.dir/COLLADA2GLTFWriter.cpp.o' failed make[3]: *** [CMakeFiles/collada2gltfConvert.dir/COLLADA2GLTFWriter.cpp.o] Error 1 make[3]: Leaving directory '/home/rene/tmp/collada2gltf-20140924/obj-x86_64-linux-gnu' CMakeFiles/Makefile2:70: recipe for target 'CMakeFiles/collada2gltfConvert.dir/all' failed make[2]: *** [CMakeFiles/collada2gltfConvert.dir/all] Error 2 make[2]: Leaving directory '/home/rene/tmp/collada2gltf-20140924/obj-x86_64-linux-gnu' Makefile:86: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/rene/tmp/collada2gltf-20140924/obj-x86_64-linux-gnu' I think you want to use FileWriteStream/filewritestream.h now? " I just uploaded rapidjson 1.1.0 to unstable... Regards, Rene --- End Message --- --- Begin Message --- Source: collada2gltf Source-Version: 20140924-6 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of collada2gltf, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 893...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated collada2gltf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Jul 2020 18:26:49 +0100 Source: collada2gltf Architecture: source Version: 20140924-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sudip Mukherjee Closes: 893203 Changes: collada2gltf (20140924-6) unstable; urgency=medium . * QA upload. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/changelog: Remove trailing whitespaces * d/rules: Remove trailing whitespaces . [ Sudip Mukherjee ] * Fix FTBFS with rapidjson. (Closes: #893203) * Update Standards-Version to 4.5.0 * Use debhelper-compat. - Update to compat level 13. * Remove whitespace from d/control and d/rules. Checksums-Sha1: dd1daabbab5cc22a4077c923f6af93a100ddaf2e
Processed: tagging 964197, tagging 964195
Processing commands for cont...@bugs.debian.org: > tags 964197 + upstream Bug #964197 [src:freedroidrpg] CVE-2020-14938 CVE-2020-14939 Added tag(s) upstream. > tags 964195 + upstream Bug #964195 [src:guacamole-client] CVE-2020-9497 CVE-2020-9498 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 964195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964195 964197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects viking
Processing commands for cont...@bugs.debian.org: > affects 964185 src:viking Bug #964185 [libfreetype6-dev] freetype2.pc depends on libbrotlidec.pc without a dependency on the libbrotli-dev package Added indication that 964185 affects src:viking > thanks Stopping processing here. Please contact me if you need assistance. -- 964185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964185: freetype2.pc depends on libbrotlidec.pc without a dependency on the libbrotli-dev package
On Fri, 03 Jul 2020 18:45:07 +0900 Mike Hommey
wrote:
..
> Arguably, freetype2.pc shouldn't depend on libbrotlidec.pc except with a
> Required.private, assuming one doesn't actually need to include
> libbrotli headers or link against libbrotli library (presumably, that's
> the case).
The thing is that libbrotli *is* in Requires.private, and pkg-config still
insists on it to exist.
Current (buggy) version:
$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/freetype2.pc
prefix=/usr
exec_prefix=/usr
libdir=/usr/lib/x86_64-linux-gnu
includedir=/usr/include
Name: FreeType 2
URL: https://freetype.org
Description: A free, high-quality, and portable font engine.
Version: 23.2.17
Requires:
Requires.private: zlib, libpng, libbrotlidec
Libs: -L${libdir} -lfreetype
Libs.private:
Cflags: -I${includedir}/freetype2
$ _
As you can see, libbrotlidec is in Requires.private.
Should pkgconfig skip this?
/mjt
Processed: Both ship /etc/skel/.kshrc
Processing commands for cont...@bugs.debian.org:
> fixed 950762 ksh/2020.0.0+really93u+20120801-7
Bug #950762 {Done: Anuradha Weeraman } [ksh,ksh93]
ksh,ksh93: both ship /etc/skel/.kshrc with insufficient
Conflicts/Breaks/Replaces
Marked as fixed in versions ksh/2020.0.0+really93u+20120801-7.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 964213 is important
Processing commands for cont...@bugs.debian.org: > severity 964213 important Bug #964213 [src:nodejs] nodejs: FTBFS without internet access Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 964213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964213: [Pkg-javascript-devel] Bug#964213: nodejs: FTBFS without internet access
Le ven. 3 juil. 2020 à 19:09, Niko Tyni a écrit :
> Source: nodejs
> Version: 12.18.1~dfsg-1
> Severity: serious
> Tags: ftbfs
>
> This package fails to build on a system without internet access.
>
> From the build log:
>
> not ok 430 parallel/test-dns-setserver-when-querying
> ---
> duration_ms: 0.137
> severity: fail
> exitcode: 1
> stack: |-
> assert.js:100
> throw new AssertionError(obj);
> ^
>
> AssertionError [ERR_ASSERTION]: Missing expected exception.
> at Object.
> (/<>/test/parallel/test-dns-setserver-when-querying.js:17:12)
> at Module._compile (internal/modules/cjs/loader.js:1138:30)
> at Object.Module._extensions..js
> (internal/modules/cjs/loader.js:1158:10)
> at Module.load (internal/modules/cjs/loader.js:986:32)
> at Function.Module._load (internal/modules/cjs/loader.js:879:14)
> at Function.executeUserEntryPoint [as runMain]
> (internal/modules/run_main.js:71:12)
> at internal/main/run_main_module.js:17:47 {
> generatedMessage: false,
> code: 'ERR_ASSERTION',
> actual: undefined,
> expected: [Object],
> operator: 'throws'
> }
> ...
> [...]
> ok 2601 sequential/test-worker-prof
> ---
> duration_ms: 0.332
> ...
> make[2]: *** [Makefile:510: test-ci-js] Error 1
> make[2]: Leaving directory '/<>'
> make[1]: *** [debian/rules:214: override_dh_auto_test-arch] Error 2
>
This is not a bug report that can lead to any kind of resolution. It's
missing:
- environment
- build log
- short explanation of how you came to this
Jérémy
Bug#961377: raspi3-firmware: recent stable update causes non-booting systems
Thorsten Glaser dijo [Fri, Jul 03, 2020 at 04:28:37PM +]: > Gunnar Wolf, Sun, 24 May 2020 16:03:04 -0500: > > >I will try to build+test+upload this in the next couple of days. > > $ rmadison -u qa raspi3-firmware > raspi3-firmware | 1.20161123-2 | stretch/non-free | source, arm64 > raspi3-firmware | 1.20190215-1+deb10u3 | buster/non-free | source, arm64, > armel, armhf > raspi3-firmware | 1.20200212-1 | bullseye/non-free | arm64, armel, > armhf > raspi3-firmware | 1.20200212-1 | sid/non-free | arm64, armel, > armhf > > *cough* Cough indeed! Thanks for the reminder - I am trying to get some time to fix some not directly related issues in this package (and failed). I will try to upload today. I am short on time, but will _surely_ do an upload by early next week. signature.asc Description: PGP signature
Bug#964213: nodejs: FTBFS without internet access
Source: nodejs
Version: 12.18.1~dfsg-1
Severity: serious
Tags: ftbfs
This package fails to build on a system without internet access.
>From the build log:
not ok 430 parallel/test-dns-setserver-when-querying
---
duration_ms: 0.137
severity: fail
exitcode: 1
stack: |-
assert.js:100
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Missing expected exception.
at Object.
(/<>/test/parallel/test-dns-setserver-when-querying.js:17:12)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js
(internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Function.executeUserEntryPoint [as runMain]
(internal/modules/run_main.js:71:12)
at internal/main/run_main_module.js:17:47 {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: undefined,
expected: [Object],
operator: 'throws'
}
...
[...]
ok 2601 sequential/test-worker-prof
---
duration_ms: 0.332
...
make[2]: *** [Makefile:510: test-ci-js] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:214: override_dh_auto_test-arch] Error 2
--
Niko Tyni nt...@debian.org
Bug#964212: net-cpp: FTBFS without internet access
Source: net-cpp Version: 2.2.1+dfsg1-4 Severity: serious Tags: ftbfs This package fails to build on a system without internet access. It looks like the build hangs in "http_streaming_client_test". >From the build log: Running tests... /usr/bin/ctest --force-new-ctest-process -j1 Test project /<>/obj-x86_64-linux-gnu Start 1: header_test 1/4 Test #1: header_test .. Passed0.01 sec Start 2: http_client_test 2/4 Test #2: http_client_test . Passed4.19 sec Start 3: http_streaming_client_test E: Build killed with signal TERM after 150 minutes of inactivity -- Niko Tyni nt...@debian.org
Bug#964211: octave-instrument-control: FTBFS without internet access
Source: octave-instrument-control
Version: 0.5.0-1
Severity: serious
Tags: ftbfs
This package fails to build on a system without internet access.
>From the build log (hopefully I spotted the relevant part):
[src/tcp/tcp_timeout.cc]
> /<>/src/tcp/tcp_timeout.cc
* test
addr = resolvehost ('gnu.org', 'address');
a = tcp (addr, 80);
assert(tcp_timeout(a), -1);
a.timeout = 2.5;
assert(tcp_timeout(a), 2500);
a.timeout = 0;
assert(tcp_timeout(a), 0);
a.timeout = -1;
assert(tcp_timeout(a), -1);
tcp_close(a);
! test failed
resolvehost: could not lookup IP address
1 test, 0 passed, 0 known failure, 0 skipped
--
Niko Tyni nt...@debian.org
Bug#964210: octave-nan: FTBFS without internet access
Source: octave-nan Version: 3.4.5-2 Severity: serious Tags: ftbfs This package fails to build on a system without internet access. >From the build log: [inst/load_fisheriris.m] > /<>/inst/load_fisheriris.m * test load_fisheriris assert(all(size(meas)==[150,4])) assert(all(size(species)==[150,1])) --2020-07-02 22:34:48-- http://archive.ics.uci.edu/ml/machine-learning-databases/iris/iris.data Resolving archive.ics.uci.edu (archive.ics.uci.edu)... failed: Temporary failure in name resolution. wget: unable to resolve host address ‘archive.ics.uci.edu’ ! test failed fread: invalid stream number = -1 1 test, 0 passed, 0 known failure, 0 skipped -- Niko Tyni nt...@debian.org
Bug#964209: python-blessed: FTBFS without internet access
Source: python-blessed
Version: 1.17.6-1
Severity: serious
Tags: ftbfs
This package fails to build on a system without internet access.
>From the build log:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sphinx/cmd/build.py", line 272, in
build_main
app = Sphinx(args.sourcedir, args.confdir, args.outputdir,
File "/usr/lib/python3/dist-packages/sphinx/application.py", line 272, in
__init__
self._init_builder()
File "/usr/lib/python3/dist-packages/sphinx/application.py", line 328, in
_init_builder
self.events.emit('builder-inited')
File "/usr/lib/python3/dist-packages/sphinx/events.py", line 99, in emit
results.append(callback(self.app, *args))
File "/usr/lib/python3/dist-packages/sphinx/ext/intersphinx.py", line 239,
in load_mappings
updated = [f.result() for f in concurrent.futures.as_completed(futures)]
File "/usr/lib/python3/dist-packages/sphinx/ext/intersphinx.py", line 239,
in
updated = [f.result() for f in concurrent.futures.as_completed(futures)]
File "/usr/lib/python3.8/concurrent/futures/_base.py", line 432, in result
return self.__get_result()
File "/usr/lib/python3.8/concurrent/futures/_base.py", line 388, in
__get_result
raise self._exception
File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3/dist-packages/sphinx/ext/intersphinx.py", line 224,
in fetch_inventory_group
logger.warning(__("failed to reach any of the inventories "
File "/usr/lib/python3.8/logging/__init__.py", line 1800, in warning
self.log(WARNING, msg, *args, **kwargs)
File "/usr/lib/python3/dist-packages/sphinx/util/logging.py", line 124, in
log
super().log(level, msg, *args, **kwargs)
File "/usr/lib/python3.8/logging/__init__.py", line 1832, in log
self.logger.log(level, msg, *args, **kwargs)
File "/usr/lib/python3.8/logging/__init__.py", line 1500, in log
self._log(level, msg, args, **kwargs)
File "/usr/lib/python3.8/logging/__init__.py", line 1577, in _log
self.handle(record)
File "/usr/lib/python3.8/logging/__init__.py", line 1587, in handle
self.callHandlers(record)
File "/usr/lib/python3.8/logging/__init__.py", line 1649, in callHandlers
hdlr.handle(record)
File "/usr/lib/python3.8/logging/__init__.py", line 946, in handle
rv = self.filter(record)
File "/usr/lib/python3.8/logging/__init__.py", line 807, in filter
result = f.filter(record)
File "/usr/lib/python3/dist-packages/sphinx/util/logging.py", line 406, in
filter
raise SphinxWarning(message)
sphinx.errors.SphinxWarning: failed to reach any of the inventories with the
following issues:
intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable
due to :
HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded
with url: /3/objects.inv (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution'))
Warning, treated as error:
failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://docs.python.org/3/objects.inv' not fetchable
due to :
HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded
with url: /3/objects.inv (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution'))
make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary] Error 2
--
Niko Tyni nt...@debian.org
Bug#964208: wsjtx: FTBFS without internet access
Source: wsjtx Version: 2.2.1+repack-1 Severity: serious Tags: ftbfs This package fails to build on a system without internet access. I suppose it's xsltproc calling out for external resources or something like that. This is probably the cause for the 2.2.2+repack-1 armhf build failure too; I think the conova buildds only have IPv6 connectivity. >From the build log: make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<> /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/CMakeFiles/wsjt_fort_autogen.dir/DependInfo.cmake --color= a2x: ERROR: "xsltproc" -param man.endnotes.list.enabled 0 -param man.endnotes.are.numbered 0 --stringparam callout.graphics 0 --stringparam navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 "/etc/asciidoc/docbook-xsl/manpage.xsl" "/<>/obj-x86_64-linux-gnu/manpages/man/man1/wsjtx.1.xml" returned non-zero exit status 5 make[3]: *** [manpages/CMakeFiles/manpages.dir/build.make:73: manpages/man/man1/wsjtx.1.gz] Error 1 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:2390: manpages/CMakeFiles/manpages.dir/all] Error 2 -- Niko Tyni nt...@debian.org
Bug#961377: raspi3-firmware: recent stable update causes non-booting systems
Gunnar Wolf, Sun, 24 May 2020 16:03:04 -0500: >I will try to build+test+upload this in the next couple of days. $ rmadison -u qa raspi3-firmware raspi3-firmware | 1.20161123-2 | stretch/non-free | source, arm64 raspi3-firmware | 1.20190215-1+deb10u3 | buster/non-free | source, arm64, armel, armhf raspi3-firmware | 1.20200212-1 | bullseye/non-free | arm64, armel, armhf raspi3-firmware | 1.20200212-1 | sid/non-free | arm64, armel, armhf *cough* bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Bug#964204: nbsphinx: FTBFS without internet access
Source: nbsphinx Version: 0.4.3+ds-1 Severity: serious Tags: ftbfs This package fails to build on a system without internet access. >From the build log: Notebook error: CellExecutionError in code-cells.ipynb: -- Image(url='https://www.python.org/static/img/python-logo-large.png', embed=True) -- [...] URLError: You can ignore this error by setting the following in conf.py: nbsphinx_allow_errors = True make[1]: *** [debian/rules:20: override_dh_sphinxdoc] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:13: binary] Error 2 -- Niko Tyni nt...@debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 964203 serious Bug #964203 [libnginx-mod-nchan] libnginx-mod-nchan distributes old/incompatible module Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 964203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > found 964203 1.18.0-3 Bug #964203 [libnginx-mod-nchan] libnginx-mod-nchan distributes old/incompatible module Marked as found in versions nginx/1.18.0-3. > End of message, stopping processing here. Please contact me if you need assistance. -- 964203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962424: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint
Control: severity -1 wishlist Control: tag -1 -moreinfo On 2020-07-03 09:49, Wxcafé wrote: > My problem is that canmount=noauto datasets should not be mounted > automatically (I mean it’s in the name, isn’t it?) and right now they are > being mounted automatically (through systemd) systemd mounts parent datasets it understands whenever child datasets are mounted. I will re-iterate: if you do not want systemd doing systemd things on a subset of your datsets, do zfs set org.openzfs.systemd:ignore=on $dataset I agree that it is different behavior, but I suspect upstream will not reverse course on this. Feel free to weigh in on that discussion, but I'm recommending closing this bug report as a "feature not a bug" because it is upstream's explicit intention. Antonio
Processed: Re: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint
Processing control commands: > severity -1 wishlist Bug #962424 [zfsutils-linux] zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint Severity set to 'wishlist' from 'grave' > tag -1 -moreinfo Bug #962424 [zfsutils-linux] zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint Removed tag(s) moreinfo. -- 962424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962424: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint
I masked the systemd zfs-mount-generator, I’d imagine setting systemd:ignore=on would work too yeah. My problem is that canmount=noauto datasets should not be mounted automatically (I mean it’s in the name, isn’t it?) and right now they are being mounted automatically (through systemd) Similarly yeah changing the mountpoint of the backup root or setting canmount=off would probably solve the symptom but the cause is still present Looking at that discussion I do agree that publicizing the change, both in the OpenZFS release notes and probably in apt-listchanges(1) too, would have made this way more painless :) Wxcafé wxc...@wxcafe.net > On Jul 3, 2020, at 11:38 AM, Antonio Russo wrote: > > Can you confirm that > > zfs set org.openzfs.systemd:ignore=on rpool/backups > > resolves your issue? Right now, you've got backup datasets that are > canmount=noauto, but presumably > should never be mounted at those mountpoints. Other options are > > - change your mountpoint on your backup root, and have everything inherit > from that. (my recommendation) > - set canmount=off for all the datasets that you cannot actually mount right > now. > > We're having an upstream discussion [1]. > > [1] https://github.com/openzfs/zfs/issues/10530
Bug#962424: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint
Can you confirm that zfs set org.openzfs.systemd:ignore=on rpool/backups resolves your issue? Right now, you've got backup datasets that are canmount=noauto, but presumably should never be mounted at those mountpoints. Other options are - change your mountpoint on your backup root, and have everything inherit from that. (my recommendation) - set canmount=off for all the datasets that you cannot actually mount right now. We're having an upstream discussion [1]. [1] https://github.com/openzfs/zfs/issues/10530
Bug#963757: marked as done (fonts-font-awesome breaks streamlink autopkgtest: /usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.eot MISSING)
Your message dated Fri, 03 Jul 2020 14:51:02 + with message-id and subject line Bug#963757: fixed in streamlink 1.4.1+dfsg-2 has caused the Debian Bug report #963757, regarding fonts-font-awesome breaks streamlink autopkgtest: /usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.eot MISSING to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fonts-font-awesome, streamlink Control: found -1 fonts-font-awesome/5.0.10+really4.7.0~dfsg-2 Control: found -1 streamlink/1.4.1+dfsg-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of fonts-font-awesome the autopkgtest of streamlink fails in testing when that autopkgtest is run with the binary packages of fonts-font-awesome from unstable. It passes when run with only packages from testing. In tabular form: passfail fonts-font-awesome from testing5.0.10+really4.7.0~dfsg-2 streamlink from testing1.4.1+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. fonts-font-awesome changed paths, I didn't check if it forgot something, or if streamlink needs adjustments (then fonts-font-awesome really should add a versioned breaks). Currently this regression is blocking the migration of fonts-font-awesome to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=fonts-font-awesome https://ci.debian.net/data/autopkgtest/testing/amd64/s/streamlink/6047974/log.gz Checking files: Checking file /usr/share/doc/python3-streamlink/html/index.html OK Checking file /usr/share/doc/python3-streamlink/html/_static/fonts/FontAwesome.otf OK Checking file /usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.eot MISSING Checking file /usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.svg MISSING Checking file /usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.ttf OK Checking file /usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.woff MISSING Checking file /usr/share/doc/python3-streamlink/html/_static/js/modernizr.min.js OK signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: streamlink Source-Version: 1.4.1+dfsg-2 Done: Alexis Murzeau We believe that the bug you reported is fixed in the latest version of streamlink, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexis Murzeau (supplier of updated streamlink package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 30 Jun 2020 23:55:57 +0200 Source: streamlink Architecture: source Version: 1.4.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Alexis Murzeau Changed-By: Alexis Murzeau Closes: 963757 Changes: streamlink (1.4.1+dfsg-2) unstable; urgency=medium . [ Lukas Märdian ] * doc: adopt link target of font-awesome files (Closes: #963757) - fonts-font-awesome 5.0.10+really4.7.0~dfsg-2 provides only OpenType and TrueType under /usr/share/fonts/ Checksums-Sha1: 2d64b9f5fa8c2056677696ea9bd5481fd43f773f 2523 streamlink_1.4.1+dfsg-2.dsc d09b0e28a607a133b8e6a8ce44a3134d4b08b248 15460 streamlink_1.4.1+dfsg-2.debian.tar.xz Checksums-Sha256: 74a78a7905416a78638eacc339af7927328031be22466e04add4ea33bd0b092f 2523 streamlink_1.4.1+dfsg-2.dsc c749709ce697764167e8302563cb31748e0e7f1abd096c4d4ed72a490431336c 15460 streamlink_1.4.1+dfsg-2.debian.tar.xz Files: 16ae6e702f0ced842f9612e4bb42537b
Bug#963401: marked as done (node-proxyquire: FTBFS: failed tests)
Your message dated Fri, 03 Jul 2020 14:50:51 + with message-id and subject line Bug#963401: fixed in node-proxyquire 2.1.3+~1.0.1+~1.0.2-10 has caused the Debian Bug report #963401, regarding node-proxyquire: FTBFS: failed tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-proxyquire Version: 2.1.3+~1.0.1+~1.0.2-9 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > eslint --format tap --no-eslintrc --env es6,node --no-inline-config '**/*.js' > TAP version 13 > 1..59 > ok 1 - /<>/examples/api/api-test.js > ok 2 - /<>/examples/api/samples/bar.js > ok 3 - /<>/examples/api/samples/foo.js > ok 4 - /<>/examples/api/samples/stats.js > ok 5 - /<>/examples/async/foo-tests.js > ok 6 - /<>/examples/async/foo.js > ok 7 - /<>/examples/example-utils.js > ok 8 - /<>/examples/simple/foo.inlineoverride.test.js > ok 9 - /<>/examples/simple/foo.js > ok 10 - /<>/examples/simple/foo.test.js > ok 11 - /<>/examples/sinon/foo-tests.js > ok 12 - /<>/examples/sinon/foo.js > ok 13 - /<>/index.js > ok 14 - /<>/lib/is.js > ok 15 - /<>/lib/proxyquire-error.js > ok 16 - /<>/lib/proxyquire.js > ok 17 - /<>/test/proxyquire-api.js > ok 18 - /<>/test/proxyquire-argumentvalidation.js > ok 19 - /<>/test/proxyquire-cache.js > ok 20 - /<>/test/proxyquire-compat.js > ok 21 - /<>/test/proxyquire-extensions.js > ok 22 - /<>/test/proxyquire-global.js > ok 23 - /<>/test/proxyquire-independence.js > ok 24 - /<>/test/proxyquire-non-object.js > ok 25 - /<>/test/proxyquire-notexisting.js > ok 26 - /<>/test/proxyquire-relative-paths.js > ok 27 - /<>/test/proxyquire-remove.js > ok 28 - /<>/test/proxyquire-sub-dependencies.js > ok 29 - /<>/test/proxyquire.js > ok 30 - /<>/test/samples/bar.js > ok 31 - /<>/test/samples/boof.js > ok 32 - /<>/test/samples/cache/bar.js > ok 33 - /<>/test/samples/cache/foo.js > ok 34 - /<>/test/samples/extensions.js > ok 35 - /<>/test/samples/foo-singleton.js > ok 36 - /<>/test/samples/foo.js > ok 37 - /<>/test/samples/fooarray.js > ok 38 - /<>/test/samples/foobool.js > ok 39 - /<>/test/samples/foonum.js > ok 40 - /<>/test/samples/global/bar.js > ok 41 - /<>/test/samples/global/baz.js > ok 42 - /<>/test/samples/global/foo-deferred.js > ok 43 - /<>/test/samples/global/foo.js > ok 44 - /<>/test/samples/no-call-thru-test/index.js > ok 45 - /<>/test/samples/no-call-thru-test/required.js > ok 46 - /<>/test/samples/notexisting/foo-relative.js > ok 47 - /<>/test/samples/notexisting/foo.js > ok 48 - /<>/test/samples/relative-paths/a/index.js > ok 49 - /<>/test/samples/relative-paths/a/util.js > ok 50 - /<>/test/samples/relative-paths/b/index.js > ok 51 - /<>/test/samples/relative-paths/b/util.js > ok 52 - /<>/test/samples/stats.js > ok 53 - /<>/test/samples/sub-dependencies/bar.js > ok 54 - /<>/test/samples/sub-dependencies/baz.js > ok 55 - /<>/test/samples/sub-dependencies/foo.js > ok 56 - /<>/Xerror/index.js > ok 57 - /<>/Xerror/test.js > ok 58 - /<>/Xkeys/index.js > ok 59 - /<>/Xkeys/test.js > > tape Xerror/test.js Xkeys/test.js > TAP version 13 > # (anonymous) > not ok 1 should be equal > --- > operator: equal > expected: |- > 'Cannot find module \'foo\'\nRequire stack:\n- > /<>/Xerror/test.js\n- /usr/lib/nodejs/tape/bin/tape' > actual: |- > 'Cannot find module \'foo\'' > at: Test. (/<>/Xerror/test.js:12:7) > stack: |- > Error: should be equal > at Test.assert [as _assert] > (/usr/lib/nodejs/tape/lib/test.js:235:54) > at Test.bound [as _assert] (/usr/lib/nodejs/tape/lib/test.js:87:32) > at Test.equal (/usr/lib/nodejs/tape/lib/test.js:395:10) > at Test.bound [as equal] (/usr/lib/nodejs/tape/lib/test.js:87:32) > at Test. (/<>/Xerror/test.js:12:7) > at Test.bound [as _cb] (/usr/lib/nodejs/tape/lib/test.js:87:32) > at Test.run (/usr/lib/nodejs/tape/lib/test.js:106:10) > at Test.bound [as run] (/usr/lib/nodejs/tape/lib/test.js:87:32) > at Immediate.next [as _onImmediate] > (/usr/lib/nodejs/tape/lib/results.js:71:15) > at processImmediate (internal/timers.js:456:21) > ... > ok 2 should be equal > # fill-keys > # es5 > ok 3 simple deep equality > ok 4 mutates dest > ok 5 fills prototype > ok 6 both > ok 7 source undefined > ok 8 dest
Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)
Control: reassign -1 apt-cudf Dear apt-cudf maintainers, On Tue, Jun 30, 2020 at 07:43:52PM +0200, Ansgar wrote: > On Tue, 2020-06-30 at 17:45 +0100, Mark Hindley wrote: > > I am struggling to understand how libelogind0 came to be installed in the > > build > > in the first place. Can you help me understand that? > > No idea; apt's resolver is sometimes creative. Other examples include > [1], [2], [3]. > > [1]: > https://buildd.debian.org/status/logs.php?pkg=hplip=3.20.6%2Bdfsg0-1=amd64 > [2]: > https://buildd.debian.org/status/logs.php?pkg=gnome-applets=3.37.2-1=amd64 > [3]: > https://buildd.debian.org/status/logs.php?pkg=kopete=4%3A20.04.1-1=amd64 The common feature in all of these experimental buildd failures is that apt-cudf fails to find the correct solution leaving a libsystemd-dev <=> libelogind0 conflict. Reassiging. Thanks. Mark
Processed: Re: Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)
Processing control commands: > reassign -1 apt-cudf Bug #964026 [libelogind0] libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies) Bug reassigned from package 'libelogind0' to 'apt-cudf'. No longer marked as found in versions elogind/243.7-1+debian1. Ignoring request to alter fixed versions of bug #964026 to the same values previously set -- 964026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963282: marked as done (nsis: FTBFS: i686-w64-mingw32-ld: build/urelease/stub_bzip2-x86-unicode/decompress.o:decompress.c:(.text+0x445): undefined reference to `memmove')
Your message dated Fri, 03 Jul 2020 14:34:15 + with message-id and subject line Bug#963282: fixed in nsis 3.05-3 has caused the Debian Bug report #963282, regarding nsis: FTBFS: i686-w64-mingw32-ld: build/urelease/stub_bzip2-x86-unicode/decompress.o:decompress.c:(.text+0x445): undefined reference to `memmove' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nsis Version: 3.05-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ (Debian 9.3.0-14) 9.3.0 > Copyright (C) 2019 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > Checking for C library gdi32... no > Checking for C library user32... no > Checking for C library pthread... yes > Checking for C library iconv... no > Checking for C library shlwapi... no > Checking for C library oleaut32... no > Checking for C library z... yes > Checking for C library dl... yes > Checking for C library gdi32... no > Checking for C library iconv... no > Checking for C library pthread... yes > Checking for C library user32... no > Checking for C library oleaut32... no > Checking for C library z... yes > Checking for C++ library cppunit... yes > scons: done reading SConscript files. > scons: Building targets ... > i686-w64-mingw32-gcc -o build/urelease/stub_bzip2-x86-unicode/bgbg.o -c -Os > -Wall -xc -fno-strict-aliasing -DNSISCALL="__attribute__((__stdcall__))" > -D_UNICODE -DUNICODE -DEXEHEAD -DWIN32_LEAN_AND_MEAN -D_WIN32_IE=0x0500 > -DNSIS_COMPRESS_USE_BZIP2 -Ibuild/urelease/config Source/exehead/bgbg.c > i686-w64-mingw32-gcc -o build/urelease/stub_bzip2-x86-unicode/components.o -c > -Os -Wall -xc -fno-strict-aliasing -DNSISCALL="__attribute__((__stdcall__))" > -D_UNICODE -DUNICODE -DEXEHEAD -DWIN32_LEAN_AND_MEAN -D_WIN32_IE=0x0500 > -DNSIS_COMPRESS_USE_BZIP2 -Ibuild/urelease/config Source/exehead/components.c > i686-w64-mingw32-gcc -o build/urelease/stub_bzip2-x86-unicode/exec.o -c -Os > -Wall -xc -fno-strict-aliasing -DNSISCALL="__attribute__((__stdcall__))" > -D_UNICODE -DUNICODE -DEXEHEAD -DWIN32_LEAN_AND_MEAN -D_WIN32_IE=0x0500 > -DNSIS_COMPRESS_USE_BZIP2 -Ibuild/urelease/config Source/exehead/exec.c > i686-w64-mingw32-gcc -o build/urelease/stub_bzip2-x86-unicode/fileform.o -c > -Os -Wall -xc -fno-strict-aliasing -DNSISCALL="__attribute__((__stdcall__))" > -D_UNICODE -DUNICODE -DEXEHEAD -DWIN32_LEAN_AND_MEAN -D_WIN32_IE=0x0500 > -DNSIS_COMPRESS_USE_BZIP2 -Ibuild/urelease/config Source/exehead/fileform.c > i686-w64-mingw32-gcc -o build/urelease/stub_bzip2-x86-unicode/Main.o -c -Os > -Wall -xc -fno-strict-aliasing -DNSISCALL="__attribute__((__stdcall__))" > -D_UNICODE -DUNICODE -DEXEHEAD -DWIN32_LEAN_AND_MEAN -D_WIN32_IE=0x0500 > -DNSIS_COMPRESS_USE_BZIP2 -Ibuild/urelease/config Source/exehead/Main.c > i686-w64-mingw32-gcc -o build/urelease/stub_bzip2-x86-unicode/plugin.o -c -Os > -Wall -xc -fno-strict-aliasing -DNSISCALL="__attribute__((__stdcall__))" > -D_UNICODE -DUNICODE -DEXEHEAD -DWIN32_LEAN_AND_MEAN -D_WIN32_IE=0x0500 > -DNSIS_COMPRESS_USE_BZIP2 -Ibuild/urelease/config Source/exehead/plugin.c > i686-w64-mingw32-gcc -o build/urelease/stub_bzip2-x86-unicode/Ui.o -c -Os > -Wall -xc -fno-strict-aliasing -DNSISCALL="__attribute__((__stdcall__))" > -D_UNICODE -DUNICODE -DEXEHEAD -DWIN32_LEAN_AND_MEAN -D_WIN32_IE=0x0500 > -DNSIS_COMPRESS_USE_BZIP2 -Ibuild/urelease/config Source/exehead/Ui.c > i686-w64-mingw32-gcc -o build/urelease/stub_bzip2-x86-unicode/util.o -c -Os > -Wall -xc -fno-strict-aliasing -DNSISCALL="__attribute__((__stdcall__))" > -D_UNICODE -DUNICODE -DEXEHEAD -DWIN32_LEAN_AND_MEAN -D_WIN32_IE=0x0500 > -DNSIS_COMPRESS_USE_BZIP2 -Ibuild/urelease/config Source/exehead/util.c > i686-w64-mingw32-gcc -o build/urelease/stub_bzip2-x86-unicode/crc32.o -c -Os > -Wall -xc -fno-strict-aliasing -DNSISCALL="__attribute__((__stdcall__))" > -D_UNICODE -DUNICODE -DEXEHEAD -DWIN32_LEAN_AND_MEAN -D_WIN32_IE=0x0500 > -DNSIS_COMPRESS_USE_BZIP2 -Ibuild/urelease/config Source/crc32.c > i686-w64-mingw32-gcc -o build/urelease/stub_bzip2-x86-unicode/bzlib.o -c -Os > -Wall -xc -fno-strict-aliasing -DNSISCALL="__attribute__((__stdcall__))" > -D_UNICODE -DUNICODE -DEXEHEAD
Bug#964149: marked as done (starpu: autopkgtest regression: /usr/lib/x86_64-linux-gnu/starpu/examples/async_tasks_overhead: No such file or directory)
Your message dated Fri, 03 Jul 2020 14:10:11 + with message-id and subject line Bug#964149: fixed in starpu-contrib 1.3.4+dfsg-3 has caused the Debian Bug report #964149, regarding starpu: autopkgtest regression: /usr/lib/x86_64-linux-gnu/starpu/examples/async_tasks_overhead: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: starpu Version: 1.3.4+dfsg-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Control: affects -1 starpu-contrib Dear maintainer(s), With a recent upload of starpu the autopkgtest of starpu fails in testing when that autopkgtest is run with the binary packages of starpu from unstable. It passes when run with only packages from testing. In tabular form: passfail starpu from testing1.3.4+dfsg-2 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=starpu https://ci.debian.net/data/autopkgtest/testing/amd64/s/starpu/6099200/log.gz autopkgtest [11:15:11]: test examples: [--- dpkg-architecture: warning: cannot determine CC system type, falling back to default (native compilation) Running /usr/lib/x86_64-linux-gnu/starpu/examples/add_vectors [starpu][check_bus_config_file] No performance model for the bus, calibrating... [starpu][check_bus_config_file] ... done Running /usr/lib/x86_64-linux-gnu/starpu/examples/add_vectors_cpp11 Running /usr/lib/x86_64-linux-gnu/starpu/examples/add_vectors_interface Running /usr/lib/x86_64-linux-gnu/starpu/examples/async_tasks_data_overhead.sh /usr/lib/x86_64-linux-gnu/starpu/examples/async_tasks_data_overhead.sh: line 19: /usr/lib/x86_64-linux-gnu/starpu/examples/async_tasks_overhead: No such file or directory autopkgtest [11:15:11]: test examples: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: starpu-contrib Source-Version: 1.3.4+dfsg-3 Done: Samuel Thibault We believe that the bug you reported is fixed in the latest version of starpu-contrib, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated starpu-contrib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 02 Jul 2020 20:03:46 +0200 Source: starpu-contrib Binary: libsocl-contrib-1.3-0 libsocl-contrib-1.3-0-dbgsym libstarpu-contrib-1.3-3 libstarpu-contrib-1.3-3-dbgsym libstarpu-contrib-dev libstarpu-contribfft-1.3-1 libstarpu-contribfft-1.3-1-dbgsym libstarpu-contribmpi-1.3-2 libstarpu-contribmpi-1.3-2-dbgsym starpu-contrib-examples starpu-contrib-examples-dbgsym starpu-contrib-tools starpu-contrib-tools-dbgsym Architecture: source amd64 Version: 1.3.4+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Samuel Thibault Changed-By: Samuel Thibault Description: libsocl-contrib-1.3-0 - Task scheduler for heterogeneous multicore machines libstarpu-contrib-1.3-3 - Task scheduler for heterogeneous multicore machines libstarpu-contrib-dev - Task scheduler for heterogeneous multicore machines - dev libstarpu-contribfft-1.3-1 - Task scheduler for heterogeneous multicore machines libstarpu-contribmpi-1.3-2 - Task scheduler for heterogeneous multicore machines starpu-contrib-examples - Task scheduler for heterogeneous multicore machines - exs starpu-contrib-tools - Task scheduler for heterogeneous multicore machines - tools Closes: 964149 Changes: starpu-contrib (1.3.4+dfsg-3)
Processed: fixed 960243 in 6.1.3-4
Processing commands for cont...@bugs.debian.org:
> fixed 960243 6.1.3-4
Bug #960243 {Done: Sebastian Ramacher } [src:zimlib]
zimlib FTBFS with ICU 67.1
Marked as fixed in versions zimlib/6.1.3-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
960243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 962882 is serious
Processing commands for cont...@bugs.debian.org: > # fonts-glewlwyd has now been removed > severity 962882 serious Bug #962882 [python3-djangorestframework] python3-djangorestframework: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 962882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964195: CVE-2020-9497 CVE-2020-9498
Source: guacamole-client Severity: grave Tags: security Please see https://www.openwall.com/lists/oss-security/2020/07/02/3 https://www.openwall.com/lists/oss-security/2020/07/02/2 Cheers, Moritz
Processed: tagging 961338
Processing commands for cont...@bugs.debian.org: > # The newcomer tag is for bugs that would be good choices for a new Debian > contributor to work on. > tags 961338 - newcomer Bug #961338 [subliminal] subliminal: update to 2.1 required to fix discarded provider problem Removed tag(s) newcomer. > thanks Stopping processing here. Please contact me if you need assistance. -- 961338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963525: steam: crashes with libmount version that depends on libcryptsetup12
Control: severity -1 normal Control: tags -1 + wontfix For now, I have worked around this in glib2.0 by removing the libmount dependency. It looks as though a libmount maintainer (upstream or in Debian, whoever gets there first!) is going to make this dependency non-problematic in practice, either by loading libcryptsetup on-demand with dlopen() (upstream) or by disabling that feature until that happens (in Debian). When that has happened, I'll re-enable libmount in glib2.0. Either of these workarounds should be enough to stop Steam crashing, so I'm lowering the severity of this bug. It is still a bug that the Steam client crashes when its dependencies pull in OpenSSL, but that is a bug that Debian cannot solve, because it is to do with Valve's proprietary binaries; so I'm also tagging this wontfix. In this case please interpret it as "can't fix". smcv
Processed: Re: Bug#963525: steam: crashes with libmount version that depends on libcryptsetup12
Processing control commands: > severity -1 normal Bug #963525 [steam] steam: crashes with libmount version that depends on libcryptsetup12 Bug #963571 [steam] steam: crashes with libmount version that depends on libcryptsetup12 Bug #963941 [steam] steam: Steam fails to start Severity set to 'normal' from 'grave' Severity set to 'normal' from 'grave' Severity set to 'normal' from 'grave' > tags -1 + wontfix Bug #963525 [steam] steam: crashes with libmount version that depends on libcryptsetup12 Bug #963571 [steam] steam: crashes with libmount version that depends on libcryptsetup12 Bug #963941 [steam] steam: Steam fails to start Added tag(s) wontfix. Added tag(s) wontfix. Added tag(s) wontfix. -- 963525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963525 963571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963571 963941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#964185 marked as pending in freetype
Processing control commands: > tag -1 pending Bug #964185 [libfreetype6-dev] freetype2.pc depends on libbrotlidec.pc without a dependency on the libbrotli-dev package Added tag(s) pending. -- 964185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964185: marked as pending in freetype
Control: tag -1 pending Hello, Bug #964185 in freetype reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/freetype/-/commit/617db19c7a36a8c6f3b1b9cf13954bd7b60f11b5 debian/control: Add libbrotli-dev as a dependency of libfreetype-dev Closes: #964185 (this message was generated automatically) -- Greetings https://bugs.debian.org/964185
Bug#964190: subliminal (stretch) is not working with current providers
Package: subliminal
Version: 1.1.1-2
Severity: grave
Justification: renders package unusable
See also #961338 for the sid version of this package → requires update to
actual version 2.1
The package is missing in buster/bullseye.
The stretch version is also not working any more.
The following error output is emitted:
Traceback (most recent call last):
File "/usr/bin/subliminal", line 9, in
load_entry_point('subliminal==1.1.1', 'console_scripts', 'subliminal')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 489, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2793,
in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2411,
in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2417,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/subliminal/__init__.py", line 10, in
from .api import (ProviderPool, check_video, provider_manager,
download_best_subtitles, download_subtitles,
File "/usr/lib/python3/dist-packages/subliminal/api.py", line 13, in
from .subtitle import compute_score, get_subtitle_path
File "/usr/lib/python3/dist-packages/subliminal/subtitle.py", line 7, in
from guessit.matchtree import MatchTree
ModuleNotFoundError: No module named 'guessit.matchtree'
-- System Information:
Debian Release: 10.4
APT prefers stable
APT policy: (1000, 'stable'), (600, 'stable-updates'), (600, 'stable'), (500,
'oldstable-updates'), (500, 'oldstable'), (200, 'testing'), (101, 'unstable'),
(10, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.0-0.bpo.2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8), LANGUAGE=de_DE:de:en_US:en (charmap=UTF-8) (ignored:
LC_ALL set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages subliminal depends on:
ii python3 3.7.3-1
ii python3-subliminal 1.1.1-2
subliminal recommends no packages.
subliminal suggests no packages.
-- no debconf information
Processed: tagging 964185
Processing commands for cont...@bugs.debian.org: > tags 964185 + ftbfs Bug #964185 [libfreetype6-dev] freetype2.pc depends on libbrotlidec.pc without a dependency on the libbrotli-dev package Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 964185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 964185
Processing commands for cont...@bugs.debian.org: > affects 964185 src:firefox Bug #964185 [libfreetype6-dev] freetype2.pc depends on libbrotlidec.pc without a dependency on the libbrotli-dev package Added indication that 964185 affects src:firefox > thanks Stopping processing here. Please contact me if you need assistance. -- 964185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964185: freetype2.pc depends on libbrotlidec.pc without a dependency on the libbrotli-dev package
Package: libfreetype6-dev Version: 2.10.2+dfsg-1 Severity: serious Firefox failed to build with: ERROR: Package libbrotlidec was not found in the pkg-config search path. ERROR: Perhaps you should add the directory containing `libbrotlidec.pc' ERROR: to the PKG_CONFIG_PATH environment variable ERROR: Package 'libbrotlidec', required by 'freetype2', not found See e.g. https://buildd.debian.org/status/fetch.php?pkg=firefox=amd64=78.0.1-1=1593768167=0 The problem is that freetype2.pc has a new dependency on libbrotlidec.pc, but that is not reflected in the package dependencies. Arguably, freetype2.pc shouldn't depend on libbrotlidec.pc except with a Required.private, assuming one doesn't actually need to include libbrotli headers or link against libbrotli library (presumably, that's the case). Mike
Bug#959075: Still not working on Debian testing
On Fri, 03 Jul 2020 10:42:26 +0800
Paul Wise wrote:
> > $ dpkg -l | grep ifenslave
> > ii ifenslave2.10+nmu2
> >
> > The lines "bond-slaves" and "bond-primary" still do not work:
>
> Please retry your test with ifenslave 2.11.
Oops, sorry, I missed that one, I did not realize I'm on testing, not
sid :-(
Ok, two remaining cometic issues in 2.11 than :-)
# ifup bond0
/etc/network/if-pre-up.d/ifenslave: 39: echo: echo: I/O error
/etc/network/if-pre-up.d/ifenslave: 39: echo: echo: I/O error
You get this error when you try to set a /sys/ option that is not
allowed, but the script does not tell which option throws an error. See
diff attached. Example updelay and downdelay are apparently not allowed
using arp and this patch will tell you what went wrong:
iface bond0 inet static
address 10.234.0.33
netmask 255.255.255.0
network 10.234.0.0
broadcast 10.234.0.255
bond-slaves eth2 eth3
bond-mode active-backup
bond-primary eth2
bond-downdelay 200
bond-updelay 200
bond-arp_interval 2000
bond-arp_ip_target 10.234.0.32, 10.234.0.34
# ifup bond0
[error] unable to set downdelay to 200
[error] unable to set updelay to 200
Another cosmetic issue:
# ifdown bond0
# modprobe -rv bonding
rmmod bonding
# ifup bond0
RTNETLINK answers: File exists
#
But when loading the kernel module before ifup then the RTNETLINK
error disappears:
# ifdown bond0
# modprobe -rv bonding
rmmod bonding
# modprobe -v bonding
insmod /lib/modules/5.7.0-1-amd64/kernel/drivers/net/bonding/bonding.ko
# ifup bond0
#
For the rest is seems to be ok now, thnx! :)
Just my 2 cts,
R.
--
richard lucassen
https://contact.xaq.nl/
--- /etc/network/if-pre-up.d/ifenslave 2020-07-02 10:35:20.0 +0200
+++ /etc/network/if-pre-up.d/ifenslave.new 2020-07-03 11:03:15.807658451 +0200
@@ -36,8 +36,10 @@
# $1 = basename of the file in bonding/ to write to.
# $2 = value to write. Won't write if $2 is empty.
if [ -n "$2" ] ; then
- echo "$2" > "/sys/class/net/$BOND_MASTER/bonding/$1"
- return $?
+ echo "$2" > "/sys/class/net/$BOND_MASTER/bonding/$1" 2>/dev/null
+ EXITCODE=$?
+ [ ${EXITCODE} -ne 0 ] && echo "[error] unable to set $1 to $2"
+ return ${EXITCODE}
fi
return 0
}
Processed: block 963728 with 964039 963246 963245 963244, tagging 964039, found 963246 in 1.24.0+ds-1 ...
Processing commands for cont...@bugs.debian.org: > block 963728 with 964039 963246 963245 963244 Bug #963728 [release.debian.org] transition: protobuf 963728 was not blocked by any bugs. 963728 was not blocking any bugs. Added blocking bug(s) of 963728: 963246, 964039, 963244, and 963245 > tags 964039 + ftbfs Bug #964039 [src:vg] vg: FTBFS on mips64el Ignoring request to alter tags of bug #964039 to the same tags previously set > found 963246 1.24.0+ds-1 Bug #963246 [src:vg] vg FTBFS with Protobuf 3.12.3 Marked as found in versions vg/1.24.0+ds-1. > found 963245 1.6.0+dfsg-3 Bug #963245 [src:onnx] onnx FTBFS with Protobuf 3.12.3 Marked as found in versions onnx/1.6.0+dfsg-3. > found 963244 2.23.2815.102+dfsg-9 Bug #963244 [src:mozc] mozc FTBFS with Protobuf 3.12.3 Marked as found in versions mozc/2.23.2815.102+dfsg-9. > thanks Stopping processing here. Please contact me if you need assistance. -- 963244: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963244 963245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963245 963246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963246 963728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963728 964039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963798: srt: Documentation is not installed into libsrt-doc and causes FTBFS if pbuilder is used
Hi Vasyl On 2020-07-03 07:25:42 +, Vasyl Gello wrote: > Hi Sebastian! > > I know that Build-Depends must be installed prior to clean target, however > git-pbuilder introduced the way to skip installing build-dependencies if > pbuilder chroot is used. I like this idea, because host system is not bloated > by unaccountable dependencies. I had a recent discussion with Mattia on that > matter, > and he recommended me to use dh-sequence-XXX under Build-Depends-Arch (and/or > Build-Depends-Indep if needed) to extend this behaviour to packages > requiring 'special' dependencies. > > I think it won't hurt anyone to apply this technique to libsrt which I did in > proposed patches. Anyway, more robust build and more proper usage of chroot > (on my strong belief) is worth the additional work. … but that does not qualify as a FTBFS bug with severity serious. The package correctly declares the required dependencies and does not fail to build. If the pbuilder way of building packages does not honor Build-Dependencies when running clean, then please discuss this issue with the pbuilder maintainers. Replacing python3-sphinx and dh --with sphinxdoc with dh-sequence-sphinxdoc is a whishlist bug at best. Note that patch 0001 actually drops the use of dh_sphinxdoc. In any case, there is a bug here to fix: libsrt-doc is empty and useless. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#963301: gstreamer1.0: FTBFS:
On Sun, 21 Jun 2020 21:53:15 +0200 Lucas Nussbaum wrote: > > > During a rebuild of all packages in sid, your package failed to build > on amd64. > [...] Thanks for reporting. This happens because GNU make was updated to 4.3, which includes backwards incompatible changes. Updating to that was probably a bad idea before making sure most things work with the new version... The package in experimental has this fixed by getting rid of the autotools/make-based build system and switching to meson. GStreamer 1.18.0 should make it in time for bullseye so I'm not going to bother fixing this separately.
Bug#963798: srt: Documentation is not installed into libsrt-doc and causes FTBFS if pbuilder is used
Hi Sebastian! I know that Build-Depends must be installed prior to clean target, however git-pbuilder introduced the way to skip installing build-dependencies if pbuilder chroot is used. I like this idea, because host system is not bloated by unaccountable dependencies. I had a recent discussion with Mattia on that matter, and he recommended me to use dh-sequence-XXX under Build-Depends-Arch (and/or Build-Depends-Indep if needed) to extend this behaviour to packages requiring 'special' dependencies. I think it won't hurt anyone to apply this technique to libsrt which I did in proposed patches. Anyway, more robust build and more proper usage of chroot (on my strong belief) is worth the additional work. -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com Skype: vasek.gello == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다 July 3, 2020 7:07:36 AM UTC, Sebastian Ramacher написав(-ла): >Control: tags -1 - ftbfs >Control: retitle -1 srt: empty documentation package > >On 2020-06-27 13:04:06 +, Vasyl Gello wrote: >> Source: srt >> Version: 1.4.1-5 >> Severity: serious >> Tags: patch ftbfs >> Justification: fails to build from source (but built successfully in the >> past) >> >> Dear colleagues, >> >> Doing a no-change rebuild of srt for buster-backports/amd64, I noticed that >> 'gbp buildpackage' fails on 'dh clean --with sphinxdoc': >> >> dpkg-checkbuilddeps: error: Unmet build dependencies: cmake chrpath help2man >> libgnutls28-dev libssl-dev pkg-config tclsh >> .[1;33mW: Unmet build-dependency in source.[0m >> dpkg-source: info: using patch list from debian/patches/series >> dpkg-source: info: applying 001-multiarch-rpath.patch >> dh clean --with sphinxdoc >> dh: error: unable to load addon sphinxdoc: Can't locate >> Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the >> Debian::Debhelper::Sequence >> BEGIN failed--compilation aborted at (eval 14) line 1. >> >> make: *** [debian/rules:21: clean] Error 25 >> >> The core issue is that sphinxdoc is installed in chroot while dh_clean is >> first >> called on host system. > >Build-Depends and Build-Conflicts must be satisfied for the clean >target. When you run that outside of the pbuilder chroot, you have to >install Build-Depends there as well. See >https://www.debian.org/doc/debian-policy/ch-relationships.html#relationships-between-source-and-binary-packages-build-depends-build-depends-indep-build-depends-arch-build-conflicts-build-conflicts-indep-build-conflicts-arch > >Cheers >-- >Sebastian Ramacher signature.asc Description: PGP signature
Bug#963798: srt: Documentation is not installed into libsrt-doc and causes FTBFS if pbuilder is used
Control: tags -1 - ftbfs Control: retitle -1 srt: empty documentation package On 2020-06-27 13:04:06 +, Vasyl Gello wrote: > Source: srt > Version: 1.4.1-5 > Severity: serious > Tags: patch ftbfs > Justification: fails to build from source (but built successfully in the past) > > Dear colleagues, > > Doing a no-change rebuild of srt for buster-backports/amd64, I noticed that > 'gbp buildpackage' fails on 'dh clean --with sphinxdoc': > > dpkg-checkbuilddeps: error: Unmet build dependencies: cmake chrpath help2man > libgnutls28-dev libssl-dev pkg-config tclsh > .[1;33mW: Unmet build-dependency in source.[0m > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: applying 001-multiarch-rpath.patch > dh clean --with sphinxdoc > dh: error: unable to load addon sphinxdoc: Can't locate > Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the > Debian::Debhelper::Sequence > BEGIN failed--compilation aborted at (eval 14) line 1. > > make: *** [debian/rules:21: clean] Error 25 > > The core issue is that sphinxdoc is installed in chroot while dh_clean is > first > called on host system. Build-Depends and Build-Conflicts must be satisfied for the clean target. When you run that outside of the pbuilder chroot, you have to install Build-Depends there as well. See https://www.debian.org/doc/debian-policy/ch-relationships.html#relationships-between-source-and-binary-packages-build-depends-build-depends-indep-build-depends-arch-build-conflicts-build-conflicts-indep-build-conflicts-arch Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Re: Bug#963798: srt: Documentation is not installed into libsrt-doc and causes FTBFS if pbuilder is used
Processing control commands: > tags -1 - ftbfs Bug #963798 [src:srt] srt: Documentation is not installed into libsrt-doc and causes FTBFS if pbuilder is used Removed tag(s) ftbfs. > retitle -1 srt: empty documentation package Bug #963798 [src:srt] srt: Documentation is not installed into libsrt-doc and causes FTBFS if pbuilder is used Changed Bug title to 'srt: empty documentation package' from 'srt: Documentation is not installed into libsrt-doc and causes FTBFS if pbuilder is used'. -- 963798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954190: dh-runit: FTBFS on armhf due to shake testsuite failure
Package: src:dh-runit Followup-For: Bug #954190 This is probably a bug in libghc-shake-dev, for example the changelog of haskell-shake that says ' * Disable testsuite on armhf, fails on Ubuntu builders, probably due to a misalignment bug due to 64bit kernel. ' -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit)
