Bug#960073: Package:python-pyqt5 Run the example code with Trace and crash (SIGABRT)【请注意，邮件由mity...@gmail.com代发】
Hi! Some information on this, it look like the same issue as #963709. (gdb) r PnsAppWebX.py Starting program: /usr/bin/python PnsAppWebX.py [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1". [New Thread 0xe6bc41e0 (LWP 21532)] Could not initialize GLX Thread 1 "python" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: 没有那个文件或目录. (gdb) b libglxmapping.c:432 No source file named libglxmapping.c. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (libglxmapping.c:432) pending. (gdb) p vendor->dlhandle No symbol "vendor" in current context. (gdb) p (char *)dlerror() $1 = 0xab233500 "/lib/aarch64-linux-gnu/libglapi.so.0: cannot allocate memory in static TLS block" (gdb) Now, is this the only way we can fix this issue？and is there any way to fix this issue fundamentally？ Thank you for letting me know. BRs //Zongli
Processed: tagging 964048
Processing commands for cont...@bugs.debian.org: > tags 964048 + bullseye sid Bug #964048 [src:golang-github-tsenart-tb] golang-github-tsenart-tb: FTBFS: TestThrottler_Wait failure Added tag(s) bullseye and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 964048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 964042
Processing commands for cont...@bugs.debian.org: > close 964042 13.1.0+dfsg-1 Bug #964042 [src:gitaly] gitaly: FTBFS: 'go install' fails Marked as fixed in versions gitaly/13.1.0+dfsg-1. Bug #964042 [src:gitaly] gitaly: FTBFS: 'go install' fails Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 964042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964053: marked as done (haskell-diagrams-gtk: FTBFS: Encountered missing or private dependencies)
Your message dated Tue, 30 Jun 2020 22:33:59 + with message-id and subject line Bug#964053: fixed in haskell-diagrams-gtk 1.4-7 has caused the Debian Bug report #964053, regarding haskell-diagrams-gtk: FTBFS: Encountered missing or private dependencies 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.) -- 964053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-diagrams-gtk Version: 1.4-6 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: Configuring diagrams-gtk-1.4... CallStack (from HasCallStack): die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:1022:20 in Cabal-3.0.1.0:Distribution.Simple.Configure configureFinalizedPackage, called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:475:12 in Cabal-3.0.1.0:Distribution.Simple.Configure configure, called at libraries/Cabal/Cabal/Distribution/Simple.hs:625:20 in Cabal-3.0.1.0:Distribution.Simple confHook, called at libraries/Cabal/Cabal/Distribution/Simple/UserHooks.hs:65:5 in Cabal-3.0.1.0:Distribution.Simple.UserHooks configureAction, called at libraries/Cabal/Cabal/Distribution/Simple.hs:180:19 in Cabal-3.0.1.0:Distribution.Simple defaultMainHelper, called at libraries/Cabal/Cabal/Distribution/Simple.hs:116:27 in Cabal-3.0.1.0:Distribution.Simple defaultMain, called at Setup.hs:2:8 in main:Main hlibrary.setup: Encountered missing or private dependencies: base >=4.2 && <4.13 make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] Error 1 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: haskell-diagrams-gtk Source-Version: 1.4-7 Done: Clint Adams We believe that the bug you reported is fixed in the latest version of haskell-diagrams-gtk, 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. Clint Adams (supplier of updated haskell-diagrams-gtk 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 17:41:44 -0400 Source: haskell-diagrams-gtk Architecture: source Version: 1.4-7 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Clint Adams Closes: 964053 Changes: haskell-diagrams-gtk (1.4-7) unstable; urgency=medium . * Patch for newer base. closes: #964053. Checksums-Sha1: 27fe388993b3a405ec37350b878576da6fc13283 2785 haskell-diagrams-gtk_1.4-7.dsc b8006f86354dd053ad9a65c9fb2f8b6bf86e2886 3628 haskell-diagrams-gtk_1.4.orig.tar.gz a9cbd5b20eb3bab6b3b4e2cfea656e044c7f5ba4 3504 haskell-diagrams-gtk_1.4-7.debian.tar.xz 719bf5f6a6b2b727c73480f083da11cda12883d6 11743 haskell-diagrams-gtk_1.4-7_source.buildinfo Checksums-Sha256: a88998909c365d177b600b739dd41c8ab55b96cd5173bd5c3f46cdf8fdad5028 2785 haskell-diagrams-gtk_1.4-7.dsc b66bde621a09b79b99185af50b2d1ed0b2bd3988c95ed27c7e92e5383917eae9 3628 haskell-diagrams-gtk_1.4.orig.tar.gz 172432243c5085af111be5f4dd366c2dfca660b89cd28e356720daf1eab32176 3504 haskell-diagrams-gtk_1.4-7.debian.tar.xz 65775389db5a105154093fff777e3eb8b14521627d39f8aa297e6fd62f47c350 11743 haskell-diagrams-gtk_1.4-7_source.buildinfo Files: e58c0b4280add544895fd1003408fd9d 2785 haskell optional haskell-diagrams-gtk_1.4-7.dsc 2f12b11bfc60c662884f37d5c31433ff 3628 haskell optional haskell-diagrams-gtk_1.4.orig.tar.gz c14853a838db10bba79efba39aa49f1e 3504 haskell optional haskell-diagrams-gtk_1.4-7.debian.tar.xz 39f6579bec52273665ea46f7136048c3 11743 haskell optional haskell-diagrams-gtk_1.4-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAvFiEEdYHsh0BT5sgHeRubVZIzHhmdOKgFAl77uzIRHGNsaW50QGRl Ymlhbi5vcmcACgkQVZIzHhmdOKjmzg/4omjPws1EQqnAIU5jEDhE2hFwkQJwmTqu 5JaGdIKw2ZjfrfwKnH/e1YFT4W0NwuZS3fRhbAp+60/G4oO4dnAB2F/A+4OWYfd2 8CmHlcO/St22rV1TmatdXf9o+dHS+LgTMeLFo8OUh0aHkc9tadbKYD/KE10YXyIu tFTRa4tCj458irF/wNCKSrXmuqyRcNm83WZar6x5wZq8vdelUW/WPGoLswLml664
Bug#964056: Should ksh93 be removed?
On Wed, Jul 01, 2020 at 12:40:17AM +0300, Adrian Bunk wrote: > Package: ksh93 > Severity: serious > > ksh (2020.0.0+really93u+20120801-6) unstable; urgency=high > > * v2020 of ksh is no longer being maintained and upstream repository has > been reverted back to the last stable version of 93u+. This update > reverts back the ksh2020 changes back to the original ksh93 from AT > ... > -- Anuradha Weeraman Sat, 27 Jun 2020 21:17:32 -0400 > > > The 2020 version of ksh was never part of any Debian distribution > other than unstable, and this seems to make it obsolete. #963858 is open with the ftp-master to have ksh93 removed. -- Regards Anuradha
Bug#937645: [Python-modules-team] Bug#937645: python-cjson: Python2 removal in sid/bullseye
Cheers, Arias Emmanuel @eamanu http://eamanu.com El mar., 30 de jun. de 2020 a la(s) 17:51, Bernd Zeimetz (b...@debian.org) escribió: > > > > On 6/30/20 10:41 PM, Moritz Mühlenhoff wrote: > > There's no movement on https://github.com/AGProjects/python-cjson/issues/6 > > and at this point there are no reverse dependencies left, let's remove it? +1 :) > > yes, good plan - I've filed a ROM removal bug. > > > Bernd > > > -- > Bernd ZeimetzDebian GNU/Linux Developer > http://bzed.dehttp://www.debian.org > GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F > > ___ > Python-modules-team mailing list > python-modules-t...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
Bug#964056: Should ksh93 be removed?
Package: ksh93 Severity: serious ksh (2020.0.0+really93u+20120801-6) unstable; urgency=high * v2020 of ksh is no longer being maintained and upstream repository has been reverted back to the last stable version of 93u+. This update reverts back the ksh2020 changes back to the original ksh93 from AT ... -- Anuradha Weeraman Sat, 27 Jun 2020 21:17:32 -0400 The 2020 version of ksh was never part of any Debian distribution other than unstable, and this seems to make it obsolete.
Bug#964055: hddemux: FTBFS: failed to query server
Source: hddemux Version: 0.4-7 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: Signing certificate... make knot-resolver configuration on 127.64.173.140:8853 --- make hddeumx configuration on 127.64.173.140:2000 - set up nginx on 127.64.173.140:4433 --- test with kdig -- [tls] RFC 7858 OOB key-pin (0): pin-sha256="" ;; WARNING: TLS, handshake failed (The TLS connection was non-properly terminated.) ;; ERROR: failed to query server 127.64.173.140@2000(TCP) [...] ==> /tmp/tmp.M18miQDa2Y/hddemux.err <== Listening on 127.64.173.140:2000 as 3. Communication attempt on fd 3. Execing ./hddemux (./hddemux) [0] closing due to outbound read error: (-104): connection reset by peer ==> /tmp/tmp.M18miQDa2Y/kresd.err <== Listening on 127.64.173.140:8853 as 3. Communication attempt on fd 3. Execing /usr/sbin/kresd (/usr/sbin/kresd -c /tmp/tmp.M18miQDa2Y/kresd.conf /tmp/tmp.M18miQDa2Y) [system] bind to '127.0.0.1@53' (UDP): Permission denied [system] error while loading config: /usr/lib/x86_64-linux-gnu/knot-resolver/postconfig.lua:34: bind to 127.0.0.1@53 error occured here (config filename:lineno is at the bottom, if config is involved): stack traceback: [C]: at 0x0040cdf0 [C]: in function 'pcall' /usr/lib/x86_64-linux-gnu/knot-resolver/postconfig.lua:32: in main chunk ERROR: net.listen() failed to bind (workdir '/tmp/tmp.M18miQDa2Y') ==> /tmp/tmp.M18miQDa2Y/nginx.err <== nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied) ./testsuite: line 56: kill: (4020973) - No such process cleaning up working directory /tmp/tmp.M18miQDa2Y make[1]: *** [Makefile:13: check] Error 1 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j4 check returned exit code 2 make: *** [debian/rules:10: binary] Error 25 -- Niko Tyni nt...@debian.org
Bug#964053: haskell-diagrams-gtk: FTBFS: Encountered missing or private dependencies
Source: haskell-diagrams-gtk Version: 1.4-6 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: Configuring diagrams-gtk-1.4... CallStack (from HasCallStack): die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:1022:20 in Cabal-3.0.1.0:Distribution.Simple.Configure configureFinalizedPackage, called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:475:12 in Cabal-3.0.1.0:Distribution.Simple.Configure configure, called at libraries/Cabal/Cabal/Distribution/Simple.hs:625:20 in Cabal-3.0.1.0:Distribution.Simple confHook, called at libraries/Cabal/Cabal/Distribution/Simple/UserHooks.hs:65:5 in Cabal-3.0.1.0:Distribution.Simple.UserHooks configureAction, called at libraries/Cabal/Cabal/Distribution/Simple.hs:180:19 in Cabal-3.0.1.0:Distribution.Simple defaultMainHelper, called at libraries/Cabal/Cabal/Distribution/Simple.hs:116:27 in Cabal-3.0.1.0:Distribution.Simple defaultMain, called at Setup.hs:2:8 in main:Main hlibrary.setup: Encountered missing or private dependencies: base >=4.2 && <4.13 make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] Error 1 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -- Niko Tyni nt...@debian.org
Bug#964042: [pkg-go] Bug#964042: gitaly: FTBFS: 'go install' fails
On 2020, ജൂലൈ 1 1:57:21 AM IST, Niko Tyni wrote: >Source: gitaly >Version: 1.78.0+dfsg-2 >Severity: serious >Tags: ftbfs > >This package fails to build on current sid. The version in experimental works, but it is blocked by rails 6 transition. Around first week of August, we plan to upload rails 6 to unstable and gitaly in experimental will be reuploaded to unstable at that time. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#937645: python-cjson: Python2 removal in sid/bullseye
On 6/30/20 10:41 PM, Moritz Mühlenhoff wrote: > There's no movement on https://github.com/AGProjects/python-cjson/issues/6 > and at this point there are no reverse dependencies left, let's remove it? yes, good plan - I've filed a ROM removal bug. Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bug#964048: golang-github-tsenart-tb: FTBFS: TestThrottler_Wait failure
Source: golang-github-tsenart-tb Version: 0.0~git20151208.0.19f4c3d-2 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: --- PASS: TestBucket_Take_throughput (1.70s) TestBucket_Wait: bucket_test.go:178: bucket.Wait(2000) with cap=1000, freq=1ms: Want: 1s, Got 2.035s TestBucket_Wait: bucket_test.go:178: bucket.Wait(2000) with cap=1000, freq=1ms: Want: 1s, Got 2.029s TestThrottler_Wait: throttler_test.go:64: Expected wait of 2s. Got: 3.116s --- FAIL: TestThrottler_Wait (3.12s) --- FAIL: TestBucket_Wait (7.01s) FAIL FAIL github.com/tsenart/tb 7.035s ? github.com/tsenart/tb/examples [no test files] ? github.com/tsenart/tb/http [no test files] ? github.com/tsenart/tb/io[no test files] FAIL dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/tsenart/tb github.com/tsenart/tb/examples github.com/tsenart/tb/http github.com/tsenart/tb/io returned exit code 1 make: *** [debian/rules:4: build] Error 25 -- Niko Tyni nt...@debian.org
Bug#964047: golang-github-src-d-gcfg: FTBFS: TestScanFully failure
Source: golang-github-src-d-gcfg Version: 1.4.0-1 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: === RUN TestEnumParserBool TestEnumParserBool: enum_test.go:26: "tRuE": got true, TestEnumParserBool: enum_test.go:26: "False": got false, TestEnumParserBool: enum_test.go:26: "t": got false, failed to parse bool `t` --- PASS: TestEnumParserBool (0.00s) === RUN TestParseInt TestParseInt: int_test.go:63: ParseInt(int, "0", IntMode(Dec)): pass; got 0, error TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Dec)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "-10", IntMode(Dec)): pass; got -10, error TestParseInt: int_test.go:63: ParseInt(int, "x", IntMode(Dec)): pass; got 0, error failed to parse "x" as int: expected integer TestParseInt: int_test.go:63: ParseInt(int, "0xa", IntMode(Hex)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "a", IntMode(Hex)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Hex)): pass; got 16, error TestParseInt: int_test.go:63: ParseInt(int, "-0xa", IntMode(Hex)): pass; got -10, error TestParseInt: int_test.go:54: ParseInt(int, "0x", IntMode(Hex)): fail; got error failed to parse "0x" as int: strconv.ParseInt: parsing "0x": invalid syntax, want ok TestParseInt: int_test.go:54: ParseInt(int, "-0x", IntMode(Hex)): fail; got error failed to parse "-0x" as int: strconv.ParseInt: parsing "-0x": invalid syntax, want ok TestParseInt: int_test.go:63: ParseInt(int, "-a", IntMode(Hex)): pass; got -10, error TestParseInt: int_test.go:63: ParseInt(int, "-10", IntMode(Hex)): pass; got -16, error TestParseInt: int_test.go:63: ParseInt(int, "x", IntMode(Hex)): pass; got 0, error failed to parse "x" as int: expected integer TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Oct)): pass; got 8, error TestParseInt: int_test.go:63: ParseInt(int, "010", IntMode(Oct)): pass; got 8, error TestParseInt: int_test.go:63: ParseInt(int, "-10", IntMode(Oct)): pass; got -8, error TestParseInt: int_test.go:63: ParseInt(int, "-010", IntMode(Oct)): pass; got -8, error TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Dec|Hex)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "010", IntMode(Dec|Hex)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "0x10", IntMode(Dec|Hex)): pass; got 16, error TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Dec|Oct)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "010", IntMode(Dec|Oct)): pass; got 8, error TestParseInt: int_test.go:63: ParseInt(int, "0x10", IntMode(Dec|Oct)): pass; got 0, error failed to parse "0x10" as int: extra characters "x10" TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Hex|Oct)): pass; got 0, error ambiguous integer value; must include '0' prefix TestParseInt: int_test.go:63: ParseInt(int, "010", IntMode(Hex|Oct)): pass; got 8, error TestParseInt: int_test.go:63: ParseInt(int, "0x10", IntMode(Hex|Oct)): pass; got 16, error TestParseInt: int_test.go:63: ParseInt(int, "10", IntMode(Dec|Hex|Oct)): pass; got 10, error TestParseInt: int_test.go:63: ParseInt(int, "010", IntMode(Dec|Hex|Oct)): pass; got 8, error TestParseInt: int_test.go:63: ParseInt(int, "0x10", IntMode(Dec|Hex|Oct)): pass; got 16, error --- FAIL: TestParseInt (0.00s) === RUN TestScanFully TestScanFully: scan_test.go:32: ScanFully(*int, "a", 'v') = failed to parse "a" as int: expected integer; *ptr==0 TestScanFully: scan_test.go:23: ScanFully(*int, "0x", 'v'): want ok, got error failed to parse "0x" as int: strconv.ParseInt: parsing "0x": invalid syntax TestScanFully: scan_test.go:32: ScanFully(*int, "0x", 'd') = failed to parse "0x" as int: extra characters "x"; *ptr==0 --- FAIL: TestScanFully (0.00s) FAIL FAIL github.com/src-d/gcfg/types 0.016s FAIL dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/src-d/gcfg github.com/src-d/gcfg/scanner github.com/src-d/gcfg/token github.com/src-d/gcfg/types returned exit code 1 make: *** [debian/rules:4: build] Error 25 -- Niko Tyni nt...@debian.org
Bug#964046: python3-skimage: missing (unversioned) Breaks+Replaces: python-skimage
Package: python3-skimage Version: 0.17.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-skimage_0.17.2-1_all.deb ... Unpacking python3-skimage (0.17.2-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-skimage_0.17.2-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/skivi.1.gz', which is also in package python-skimage 0.14.2-2 Errors were encountered while processing: /var/cache/apt/archives/python3-skimage_0.17.2-1_all.deb Since python-skimage no longer exists, the B+R can be unversioned. cheers, Andreas python-skimage=0.14.2-2_python3-skimage=0.17.2-1.log.gz Description: application/gzip
Bug#937645: python-cjson: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:37:25AM +, Matthias Klose wrote: > Package: src:python-cjson > Version: 1.2.1-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html There's no movement on https://github.com/AGProjects/python-cjson/issues/6 and at this point there are no reverse dependencies left, let's remove it? Cheers, Moritz
Bug#964045: golang-github-shirou-gopsutil: FTBFS: Test_Process_memory_maps failure
Source: golang-github-shirou-gopsutil
Version: 2.19.11-1
Severity: serious
Tags: ftbfs
This package fails to build from source on current sid.
>From my build log:
=== RUN Test_SendSignal
--- PASS: Test_SendSignal (0.00s)
=== RUN Test_Pids
--- PASS: Test_Pids (0.00s)
=== RUN Test_Pids_Fail
Test_Pids_Fail: process_test.go:48: darwin only
--- SKIP: Test_Pids_Fail (0.00s)
=== RUN Test_Pid_exists
--- PASS: Test_Pid_exists (0.00s)
=== RUN Test_NewProcess
--- PASS: Test_NewProcess (0.00s)
=== RUN Test_Process_memory_maps
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
{"path":"","rss":0,"size":0,"pss":0,"sharedClean":0,"sharedDirty":0,"privateClean":0,"privateDirty":0,"referenced":0,"anonymous":0,"swap":0}
Test_Process_memory_maps: process_test.go:114: memory map get error
Bug#964043: golang-github-caarlos0-env: FTBFS: TestParseInvalidURL fails
Source: golang-github-caarlos0-env Version: 6.0.0-1 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: dh_auto_test -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/caarlos0/env === RUN TestParsesEnv [...] --- PASS: TestParseURL (0.00s) === RUN TestParseInvalidURL TestParseInvalidURL: env_test.go:953: Error Trace:env_test.go:953 Error: Error message not equal: expected: "env: parse error on field \"ExampleURL\" of type \"url.URL\": unable parse URL: parse nope://s s/: invalid character \" \" in host name" actual : "env: parse error on field \"ExampleURL\" of type \"url.URL\": unable parse URL: parse \"nope://s s/\": invalid character \" \" in host name" Test: TestParseInvalidURL --- FAIL: TestParseInvalidURL (0.00s) === RUN TestIgnoresUnexported --- PASS: TestIgnoresUnexported (0.00s) === RUN TestPrecedenceUnmarshalText --- PASS: TestPrecedenceUnmarshalText (0.00s) === RUN ExampleParse --- PASS: ExampleParse (0.00s) === RUN ExampleParseWithFuncs --- PASS: ExampleParseWithFuncs (0.00s) FAIL FAIL github.com/caarlos0/env 0.030s FAIL dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/caarlos0/env returned exit code 1 make: *** [debian/rules:4: build] Error 25 -- Niko Tyni nt...@debian.org
Bug#964044: mrpt: FTBFS: test failure
Source: mrpt Version: 1:2.0.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) binNMUs of mrpt failed to build: | [--] 1 test from RawlogGrabberApp | [ RUN ] RawlogGrabberApp.CGenericCamera_AVI | [CCameraSensor::initialize] Opening camera... | [CCameraSensor::initialize] FFmpeg stream: /<>/share/mrpt/datasets/dummy_video.avi... | [CCameraSensor::initialize] Done! | Rawlog grabbed objects: 1 | /<>/libs/apps/src/RawlogGrabberApp_unittest.cpp:94: Failure | Expected: (app.rawlog_saved_objects) >= (REQUIRED_GRAB_OBS), actual: 1 vs 3 | [ FAILED ] RawlogGrabberApp.CGenericCamera_AVI (1511 ms) | [--] 1 test from RawlogGrabberApp (1511 ms total) See https://buildd.debian.org/status/fetch.php?pkg=mrpt=amd64=1%3A2.0.4-1%2Bb1=1593549279=0 for example Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#964042: gitaly: FTBFS: 'go install' fails
Source: gitaly Version: 1.78.0+dfsg-2 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 16 -ldflags "-X gitlab.com/gitlab-org/gitaly/internal/version.version=1.78.0" gitlab.com/gitlab-org/gitaly/auth [...] gitlab.com/gitlab-org/gitaly/proto/go/internal/linter gitlab.com/gitlab-org/gitaly/streamio returned exit code 2 make[1]: *** [debian/rules:28: override_dh_auto_build] Error 25 make[1]: Leaving directory '/build/1st/gitaly-1.78.0+dfsg' make: *** [debian/rules:18: build] Error 2 -- Niko Tyni nt...@debian.org
Bug#964041: git-repair: FTBFS: duration parse error
Source: git-repair Version: 1.20200102-1 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: [21 of 69] Compiling Utility.HumanTime ( Utility/HumanTime.hs, dist/build/git-repair/git-repair-tmp/Utility/HumanTime.o ) Utility/HumanTime.hs:58:21: error: • Could not deduce (MonadFail m) arising from a use of ‘fail’ from the context: Monad m bound by the type signature for: parseDuration :: forall (m :: * -> *). Monad m => String -> m Duration at Utility/HumanTime.hs:47:1-48 Possible fix: add (MonadFail m) to the context of the inferred type of parsefail :: m a or the type signature for: parseDuration :: forall (m :: * -> *). Monad m => String -> m Duration • In the expression: fail "duration parse error; expected eg \"5m\" or \"1h5m\"" In an equation for ‘parsefail’: parsefail = fail "duration parse error; expected eg \"5m\" or \"1h5m\"" In an equation for ‘parseDuration’: parseDuration = maybe parsefail (return . Duration) . go 0 where go n [] = return n go n s = do num <- ... parsefail = fail "duration parse error; expected eg \"5m\" or \"1h5m\"" | 58 | parsefail = fail "duration parse error; expected eg \"5m\" or \"1h5m\"" | ^^^ make[1]: *** [Makefile:8: build] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: error: make -j1 returned exit code 2 make: *** [debian/rules:10: binary] Error 25 -- Niko Tyni nt...@debian.org
Bug#964040: git-buildpackage: FTBFS: E741 ambiguous variable name 'l'
Source: git-buildpackage Version: 0.9.19 Severity: serious Tags: ftbfs This package fails to build on current sid. >From my build log: make[2]: Entering directory '/<>' flake8 ./.pybuild/cpython3_3.8/build/gbp/patch_series.py:108:81: E741 ambiguous variable name 'l' ./.pybuild/cpython3_3.8/build/gbp/scripts/pq.py:123:22: E741 ambiguous variable name 'l' ./.pybuild/cpython3_3.8/build/gbp/git/repository.py:518:37: E741 ambiguous variable name 'l' ./.pybuild/cpython3_3.8/build/gbp/git/repository.py:600:37: E741 ambiguous variable name 'l' ./gbp/patch_series.py:108:81: E741 ambiguous variable name 'l' ./gbp/scripts/pq.py:123:22: E741 ambiguous variable name 'l' ./gbp/git/repository.py:518:37: E741 ambiguous variable name 'l' ./gbp/git/repository.py:600:37: E741 ambiguous variable name 'l' make[2]: *** [Makefile:20: syntax-check] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:22: override_dh_auto_test] Error 2 -- Niko Tyni nt...@debian.org
Bug#964039: vg: FTBFS on mips64el
Source: vg Version: 1.25.0+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) vg failed to build on mips64el: | Test Summary Report | --- | t/34_vg_pack.t (Wstat: 0 Tests: 18 Failed: 2) | Failed tests: 16-17 | t/48_vg_convert.t (Wstat: 0 Tests: 26 Failed: 2) | Failed tests: 15, 19 | Files=50, Tests=672, 2446 wallclock secs ( 3.33 usr 0.48 sys + 3450.18 cusr 398.58 csys = 3852.57 CPU) | Result: FAIL | make[1]: *** [debian/rules:70: override_dh_auto_test-arch] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=vg=mips64el=1.25.0%2Bds-1=1593113654=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#964037: src:quickfix: fails to migrate to testing for too long: FTBFS on i386
Source: quickfix Version: 1.15.1+dfsg-3 Severity: serious Control: close -1 1.15.1+dfsg-4 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:quickfix in its current version in unstable has been trying to migrate for 62 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=quickfix signature.asc Description: OpenPGP digital signature
Processed: src:quickfix: fails to migrate to testing for too long: FTBFS on i386
Processing control commands: > close -1 1.15.1+dfsg-4 Bug #964037 [src:quickfix] src:quickfix: fails to migrate to testing for too long: FTBFS on i386 Marked as fixed in versions quickfix/1.15.1+dfsg-4. Bug #964037 [src:quickfix] src:quickfix: fails to migrate to testing for too long: FTBFS on i386 Marked Bug as done -- 964037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#963325 marked as pending in alot
Processing control commands:
> tag -1 pending
Bug #963325 [src:alot] alot: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.8 returned exit code 13
Added tag(s) pending.
--
963325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#963325: marked as pending in alot
Control: tag -1 pending Hello, Bug #963325 in alot 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/python-team/applications/alot/-/commit/1f5013b4619ec108a0cc990635cbb246eb080ac9 d/control: Add build-dep locales-all. Closes: #963325 Signed-off-by: Jordan Justen (this message was generated automatically) -- Greetings https://bugs.debian.org/963325
Processed: retitle 964034 to ksh93: CVE-2019-14868, reopening 964034
Processing commands for cont...@bugs.debian.org:
> retitle 964034 ksh93: CVE-2019-14868
Bug #964034 {Done: Boyuan Yang } [src:ksh93] ksh:
CVE-2019-14868
Changed Bug title to 'ksh93: CVE-2019-14868' from 'ksh: CVE-2019-14868'.
> reopen 964034
Bug #964034 {Done: Boyuan Yang } [src:ksh93] ksh93:
CVE-2019-14868
Bug reopened
Ignoring request to alter fixed versions of bug #964034 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
964034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Both ship /etc/skel/.kshrc
Processing commands for cont...@bugs.debian.org: > fixed 950762 ksh/2020.0.0+really93u+20120801-6 Bug #950762 [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-6. > 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: cloning 948989, reassign -1 to src:ksh93
Processing commands for cont...@bugs.debian.org:
> clone 948989 -1
Bug #948989 {Done: Boyuan Yang } [src:ksh] ksh: CVE-2019-14868
Bug 948989 cloned as bug 964034
> reassign -1 src:ksh93 93u+20120801-7
Bug #964034 {Done: Boyuan Yang } [src:ksh] ksh: CVE-2019-14868
Bug reassigned from package 'src:ksh' to 'src:ksh93'.
No longer marked as found in versions ksh/93u+20120801-3.1,
ksh/93u+20120801-3.4, and ksh/2020.0.0-2.
No longer marked as fixed in versions ksh/2020.0.0+really93u+20120801-6 and
ksh/2020.0.0-2.1.
Bug #964034 {Done: Boyuan Yang } [src:ksh93] ksh:
CVE-2019-14868
Marked as found in versions ksh93/93u+20120801-7.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
948989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948989
964034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#960762: libvirt: random (?) test hangs
On Sat, May 16, 2020 at 03:00:46PM +0300, Adrian Bunk wrote: > Source: libvirt > Version: 6.0.0-7 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=libvirt=all=6.0.0-7=1589452859=0 > https://buildd.debian.org/status/fetch.php?pkg=libvirt=i386=6.0.0-7=1589494701=0 > > ... > make check-TESTS > make[4]: Entering directory '/<>/debian/build/tests' > make[5]: Entering directory '/<>/debian/build/tests' > PASS: sockettest > PASS: virbuftest > PASS: virhostcputest [...] > PASS: virsh-vcpupin > PASS: virsh-optparse > PASS: virt-aa-helper-test > E: Build killed with signal TERM after 150 minutes of inactivity Has anyone managed to reproduce this? I've built 6.0.0-7 from source in a tight loop 100 times, both in a sid:i386 chroot via cowbuilder and in a sid:i386 VM, without encountering a single failure. The latest build attempt on i386 also failed: https://buildd.debian.org/status/fetch.php?pkg=libvirt=i386=6.4.0-1=1593097042=0 However, the failure in this case was not limited to i386 and the error was completely different, caused this time by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963704 All I can think of at this point is a temporary glitch of the buildd. In a couple of weeks, when we upload 6.5.0, we'll hopefully see that build fine on all architectures, i386 included... Does anyone have any better theories? Or a way to dig further? -- Andrea Bolognani Resistance is futile, you will be garbage collected. signature.asc Description: PGP signature
Bug#937490: pynifti: Python2 removal in sid/bullseye
On Mon, Jun 29, 2020 at 08:41:26PM +0200, Michael Hanke wrote: > Hi, > > yes, that sounds like to best course of action to me. Ack, I've filed an RM bug. Cheers, Moritz
Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)
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 > Presumably there is a build dependency on libsystemd-dev, but I don't see it > in > the log. That's probably not required for apt to find the unwanted solution. Ansgar
Bug#963975: blender: Blender crashes on launch (failed assert)
Package: blender Version: 2.83.1+dfsg-1 Followup-For: Bug #963975 Dear Maintainer, I have updated to 2.83.1 + dfsg-1 and have the same problem (I don't remember if I used 2.81 or 2.82 previously but it worked) In my case, however, the fonts in question are not installed by blender-data, the fonts directory is missing, if I create it and copy the fonts blender does not work anyway, I guess we should run font config, if I copy the fonts in the configuration directory of blender, in the user's home, blender works. dpkg -L blender-data|grep '\.ttf$' /usr/share/locale/fonts/bmonofont-i18n.ttf /usr/share/locale/fonts/droidsans.ttf ls -l /usr/share/locale/fonts/bmonofont-i18n.ttf /usr/share/locale/fonts/droidsans.ttf ls: cannot access '/usr/share/locale/fonts/bmonofont-i18n.ttf': No such file or directory ls: cannot access '/usr/share/locale/fonts/droidsans.ttf': No such file or directory cp blender-2.83.1-linux64/2.83/datafiles/fonts/bmonofont-i18n.ttf blender-2.83.1-linux64/2.83/datafiles/fonts/droidsans.ttf /home/alex/.config/blender/2.83/datafiles/fonts -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 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: AppArmor: enabled Versions of packages blender depends on: ii blender-data 2.83.1+dfsg-1 ii fonts-dejavu 2.37-2 ii libavcodec-extra58 [libavcodec58] 7:4.3-2 ii libavdevice58 7:4.3-2 ii libavformat58 7:4.3-2 ii libavutil567:4.3-2 ii libboost-locale1.71.0 1.71.0-6+b2 ii libc6 2.30-8 ii libfftw3-double3 3.3.8-2 ii libfreetype6 2.10.1-2 ii libgcc-s1 10.1.0-4 ii libgl1 1.3.1-1 ii libglew2.1 2.1.0-4+b1 ii libgomp1 10.1.0-4 ii libilmbase24 2.3.0-6 ii libjack-jackd2-0 [libjack-0.125] 1.9.12~dfsg-2+b1 ii libjemalloc2 5.2.1-1 ii libjpeg62-turbo1:1.5.2-2+b1 ii libopenal1 1:1.19.1-1+b1 ii libopencolorio1v5 1.1.1~dfsg0-6+b1 ii libopenexr24 2.3.0-6 ii libopenimageio2.1 2.1.16.0~dfsg0-1 ii libopenjp2-7 2.3.1-1 ii libopenvdb7.0 7.0.0-3+b1 ii libosdcpu3.4.3 3.4.3-3 ii libosdgpu3.4.3 3.4.3-3 ii libpcre3 2:8.39-13 ii libpng16-161.6.37-2 ii libpython3.8 3.8.3-1 ii libsdl2-2.0-0 2.0.12+dfsg1-1 ii libsndfile11.0.28-8 ii libspnav0 0.2.3-1+b2 ii libstdc++6 10.1.0-4 ii libswscale57:4.3-2 ii libtbb22020.2-2 ii libtiff5 4.1.0+git191117-2 ii libx11-6 2:1.6.9-2+b1 ii libxfixes3 1:5.0.3-2 ii libxi6 2:1.7.10-1 ii libxml22.9.10+dfsg-5+b1 ii libxrender11:0.9.10-1 ii libxxf86vm11:1.1.4-1+b2 ii zlib1g 1:1.2.11.dfsg-2 blender recommends no packages. blender suggests no packages. -- no debconf information
Bug#962424: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint
Sorry, it's been three weeks and lots of stuff happened since there, I don't know if I edited that file or not now, but I guess probably yeah. Here's something pulled from my server right now. Cheers On Tue, 2020-06-30 at 06:24 -0600, Antonio Russo wrote: > Control: tags -1 +moreinfo > > Hello! > > Is that attached file literally what is in /etc/zfs/zfs-list.cache > ? How was it generated, and how did it get there? > > Because it's wrong---it's space separated, and must be tab > separated. Use -H, per man zfs-mount-generator, if it must be done > by hand. > > Best, > Antonio -- Wxcafé rpool / off on on off on off on off - none- - - - - - - - rpool/ROOT noneoff on on off on off on off - none- - - - - - - - rpool/ROOT/debian / noauto on on off on off on off - none- - - - - - - - rpool/backups /backupsnoauto on on off on off on off - none- - - - - - - - rpool/backups/kirby /backups/kirby noauto on on off on off on off - none- - - - - - - - rpool/backups/kirby/backups /backups/kirby/backups on on on off on off on off - none- - - - - - - - rpool/backups/kirby/backups/cwh /backups/kirby/backups/cwh noauto on on off on off on off rpool/backups/kirby/backups/cwh prompt - - - - - - - - rpool/backups/kirby/backups/link/backups/kirby/backups/link noauto on on off on off on off rpool/backups/kirby/backups/linkprompt - - - - - - - - rpool/backups/kirby/srvpool /backups/kirby/srvpool noauto on on off on off on off - none- - - - - - - - rpool/backups/kirby/srvpool/srv /backups/kirby/srvpool/srv noauto on on off on off on off - none- - - - - - - - rpool/backups/kirby/srvpool/srv/storage /srv/storagenoauto on on off on off on off rpool/backups/kirby/srvpool/srv/storage prompt - - - - - - - - rpool/backups/local /backups/local on on on off on off on off - none- - - - - - - - rpool/backups/support /backups/supportnoauto on on off on off on off - none- - - - - - - - rpool/backups/support/bpool / noauto on on off on off on off - none- - - - - - - - rpool/backups/support/bpool/BOOTnonenoauto on on off on off on off - none- - - - - - - - rpool/backups/support/bpool/BOOT/debian legacy noauto on on off on off on off - none- - - - - - - - rpool/backups/support/rpool / noauto on on off on off on off - none- - - - - - - - rpool/backups/support/rpool/ROOTnonenoauto on on off on off on off - none- - - - - - - - rpool/backups/support/rpool/ROOT/debian / noauto on on off on off on off - none- - - - - - - - rpool/backups/support/rpool/home/home noauto on on off on off on off - none- - - - - - - - rpool/backups/support/rpool/home/root /root noauto on on off on off on off - none- - - - - - - - rpool/backups/support/rpool/home/wxcafe /home/wxcafenoauto on on off on off on off - none- - - - - - - - rpool/backups/support/rpool/srv /srvnoauto on on off on off on off - none- - - - - - - -
Processed: Re: Bug#964027: incompatible with kernel 5.7.0: ERROR: modpost: "__pagevec_lru_add" [...] undefined!
Processing commands for cont...@bugs.debian.org: > tags 964027 pending fixed-upstream Bug #964027 [openafs-modules-dkms] incompatible with kernel 5.7.0: ERROR: modpost: "__pagevec_lru_add" [...] undefined! Added tag(s) fixed-upstream and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 964027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964027: incompatible with kernel 5.7.0: ERROR: modpost: "__pagevec_lru_add" [...] undefined!
tags 964027 pending fixed-upstream thanks On Tue, Jun 30, 2020 at 12:48:41PM -0400, Ryan Kavanagh wrote: > Package: openafs-modules-dkms > Version: 1.8.6~pre1-3 > Severity: grave > Justification: package is not compatible with the current kernel > > The package cannot successfully be installed under 5.7.0-1-amd64. > The build fails with: Upstream 1.8.6, released yesterday, will support the 5.7 kernel. Thanks for the report, Ben
Bug#964027: incompatible with kernel 5.7.0: ERROR: modpost: "__pagevec_lru_add" [...] undefined!
Package: openafs-modules-dkms Version: 1.8.6~pre1-3 Severity: grave Justification: package is not compatible with the current kernel The package cannot successfully be installed under 5.7.0-1-amd64. The build fails with: LD [M] /var/lib/dkms/openafs/1.8.6pre1/build/src/libafs/MODLOAD-5.7.0-1-amd64-SP/afspag.o MODPOST 2 modules ERROR: modpost: "__pagevec_lru_add" [/var/lib/dkms/openafs/1.8.6pre1/build/src/libafs/MODLOAD-5.7.0-1-amd64-SP/openafs.ko] undefined! make[5]: *** [/usr/src/linux-headers-5.7.0-1-common/scripts/Makefile.modpost:99: __modpost] Error 1 make[4]: *** [/usr/src/linux-headers-5.7.0-1-common/Makefile:1658: modules] Error 2 make[3]: *** [/usr/src/linux-headers-5.7.0-1-common/Makefile:180: sub-make] Error 2 make[3]: Leaving directory '/usr/src/linux-headers-5.7.0-1-amd64' FAILURE: make exit code 2 make[2]: *** [Makefile.afs:279: openafs.ko] Error 1 make[2]: Leaving directory '/var/lib/dkms/openafs/1.8.6pre1/build/src/libafs/MODLOAD-5.7.0-1-amd64-SP' make[1]: *** [Makefile:186: linux_compdirs] Error 2 make[1]: Leaving directory '/var/lib/dkms/openafs/1.8.6pre1/build/src/libafs' make: *** [Makefile:15: all] Error 2 The entire build log, /var/lib/dkms/openafs/1.8.6pre1/build/make.log, is attached. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_CA.UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openafs-modules-dkms depends on: ii dkms 2.8.2-2 ii libc6-dev 2.31-0experimental0 ii perl 5.30.3-4 Versions of packages openafs-modules-dkms recommends: ii openafs-client 1.8.6~pre1-3 openafs-modules-dkms suggests no packages. -- no debconf information -- |)|/ Ryan Kavanagh | GPG: 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A DKMS make.log for openafs-1.8.6pre1 for kernel 5.7.0-1-amd64 (x86_64) Tue 30 Jun 2020 12:34:56 PM EDT checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for a BSD-compatible install... /usr/bin/install -c checking for flex... flex checking lex output file root... lex.yy checking lex library... -lfl checking whether yytext is a pointer... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for libxslt... no checking for saxon... no checking for xalan-j... no checking for xsltproc... xsltproc checking for fop... no checking for dblatex... no checking for docbook2pdf... no configure: WARNING: Docbook stylesheets not found; some documentation can't be built checking for kindlegen... no checking for doxygen... no checking for dot... dot checking for library containing strerror... none required checking for pid_t... yes checking for size_t... yes checking whether ln -s works... yes checking for ranlib... ranlib checking for bison... bison -y checking if lex is flex... yes checking whether byte order is known at compile time... yes checking whether byte ordering is bigendian... no checking whether printf understands the %z length modifier... yes checking your OS... linux checking for ranlib... (cached) ranlib checking for as... as checking for mv... mv checking for rm... rm checking for ld... ld checking for cp... cp checking for gencat... gencat checking if gcc accepts -march=pentium... no checking if gcc needs -fno-strength-reduce... yes checking if gcc needs -fno-strict-aliasing... yes checking if gcc supports -fno-common... yes checking if gcc supports -pipe... yes checking if linux kbuild requires EXTRA_CFLAGS... no checking if linux kernel module build works... yes checking
Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)
Ansgar, Thanks for this. On Tue, Jun 30, 2020 at 06:27:20PM +0200, Ansgar wrote: > Package: libelogind0 > Version: 243.7-1+debian1 > Severity: serious > > libelogind0's `Provides: libsystemd0` causes unrelated packages to > fail to build due to unmet dependencies. See [1] for an example. > > The relevant log part is: > > +--- > | The following packages have unmet dependencies: > | libelogind0 : Conflicts: libsystemd0 > | E: Broken packages > | apt-get failed. > +--- I am struggling to understand how libelogind0 came to be installed in the build in the first place. Can you help me understand that? Presumably there is a build dependency on libsystemd-dev, but I don't see it in the log. Thanks Mark
Bug#964026: libelogind0: `Provides: libsystemd0` causes unrelated packages to fail to build (unmet dependencies)
Package: libelogind0 Version: 243.7-1+debian1 Severity: serious libelogind0's `Provides: libsystemd0` causes unrelated packages to fail to build due to unmet dependencies. See [1] for an example. The relevant log part is: +--- | The following packages have unmet dependencies: | libelogind0 : Conflicts: libsystemd0 | E: Broken packages | apt-get failed. +--- Other packages are also affected. Currently the w-b team sometimes adds manual build conflicts against libelogind0 to work around the issue, but that is not really a sustainable solution. Ansgar [1]: https://buildd.debian.org/status/logs.php?pkg=libreoffice=1%3A7.0.0%7Ebeta2-2=amd64=experimental
Bug#963420: marked as done (zsh: FTBFS: sh: 1: colcrt: not found)
Your message dated Tue, 30 Jun 2020 16:19:40 +
with message-id
and subject line Bug#963420: fixed in zsh 5.8-5
has caused the Debian Bug report #963420,
regarding zsh: FTBFS: sh: 1: colcrt: not found
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.)
--
963420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zsh
Version: 5.8-4
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[3]: Entering directory '/<>/obj/Doc'
> /bin/sh ../../mkinstalldirs
> /<>/debian/zsh-common/usr/share/man/man1
> mkdir -m 755 -p -- /<>/debian/zsh-common/usr/share/man/man1
> for file in zsh.1 zshbuiltins.1 zshcalsys.1 zshcompctl.1 zshcompwid.1
> zshcompsys.1 zshcontrib.1 zshexpn.1 zshmisc.1 zshmodules.1 zshoptions.1
> zshparam.1 zshroadmap.1 zshtcpsys.1 zshzftpsys.1 zshzle.1 zshall.1; do \
> test -s $file || exit 1; \
> /usr/bin/install -c -m 644 $file
> /<>/debian/zsh-common/usr/share/man/man1/`echo $file | sed
> 's|zsh|zsh|'` || exit 1; \
> done
> make[3]: Leaving directory '/<>/obj/Doc'
> make[2]: Leaving directory '/<>/obj'
> perl /<>/Util/helpfiles obj/Doc/zshbuiltins.1
> debian/zsh-common/usr/share/zsh/help
> helpfiles: attempting man obj/Doc/zshbuiltins.1
> >debian/zsh-common/usr/share/zsh/help/man.tmp
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> helpfiles: attempting nroff -man obj/Doc/zshbuiltins.1
> >debian/zsh-common/usr/share/zsh/help/man.tmp
> helpfiles: attempting col -bx >debian/zsh-common/usr/share/zsh/help/col.tmp
> sh: 1: col: not found
> helpfiles: attempting colcrt - debian/zsh-common/usr/share/zsh/help/man.tmp
> >debian/zsh-common/usr/share/zsh/help/col.tmp
> sh: 1: colcrt: not found
> helpfiles: col -bx and colcrt - both failed
> make[1]: *** [debian/rules:97: override_dh_auto_install-indep] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/06/20/zsh_5.8-4_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: zsh
Source-Version: 5.8-5
Done: Axel Beckert
We believe that the bug you reported is fixed in the latest version of
zsh, 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.
Axel Beckert (supplier of updated zsh 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: SHA256
Format: 1.8
Date: Tue, 30 Jun 2020 17:42:41 +0200
Source: zsh
Architecture: source
Version: 5.8-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Zsh Maintainers
Changed-By: Axel Beckert
Closes: 960298 963420
Changes:
zsh (5.8-5) unstable; urgency=medium
.
[ Axel Beckert ]
* [75eb3334] Retroactively mention #928194 in 5.8-1 changelog entry.
* [d4dedd99] Adapt to "col" having been moved from bsdmainutils to
bsdextrautils. (Closes: #963420)
* [71a1b8a4] Try to fix cross-installability of run-testsuite
autopkgtest check.
* [dc40a872] Add a minimal debian/salsa-ci.yml file.
* [27586e0e] Bump debhelper compatibility level to 13.
* [c2242d6d] Cherry-pick 754658af from upstream to fix "git stash drop"
tab-completion.
* [eda6cb4d] Update lintian overrides wrt. renamed lintian tags.
.
[ Daniel Shahaf ]
* [49dbae2c] Retroactively close #740587 in 5.2-test-1-1.
* [e8d6bb61] Cherry-pick d128bc0b from upstream: 45731: _debsnap: New
completion function (Closes: #960298)
Checksums-Sha1:
f22585436490d1bcd974ecc5723cfd6d288368d7 2801 zsh_5.8-5.dsc
Bug#963419: marked as done (kombu: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 --system=custom "--test-args={interpreter} setup.py test" returned exit code 13)
Your message dated Tue, 30 Jun 2020 13:49:12 +
with message-id
and subject line Bug#963419: fixed in kombu 4.6.11-1
has caused the Debian Bug report #963419,
regarding kombu: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.8 --system=custom "--test-args={interpreter} setup.py
test" returned exit code 13
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.)
--
963419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kombu
Version: 4.6.8-1
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 '/<>'
> dh_auto_test -- --system=custom --test-args="{interpreter} setup.py test"
> I: pybuild base:217: python3.8 setup.py test
> running test
> WARNING: Testing via this command is deprecated and will be removed in a
> future version. Users looking for a generic test entry point independent of
> test runner are encouraged to use tox.
> WARNING: The pip package is not available, falling back to EasyInstall for
> handling setup_requires/test_requires; this is deprecated and will be removed
> in a future version.
> Searching for amqp<2.6,>=2.5.2
> Reading https://pypi.org/simple/amqp/
> Download error on https://pypi.org/simple/amqp/: [Errno 111] Connection
> refused -- Some packages may not be found!
> Couldn't retrieve index page for 'amqp'
> Scanning index of all packages (this may take a while)
> Reading https://pypi.org/simple/
> Download error on https://pypi.org/simple/: [Errno 111] Connection refused --
> Some packages may not be found!
> No local packages or working download links found for amqp<2.6,>=2.5.2
> error: Could not find suitable distribution for
> Requirement.parse('amqp<2.6,>=2.5.2')
> E: pybuild pybuild:352: test: plugin custom failed with: exit code=1:
> python3.8 setup.py test
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8
> --system=custom "--test-args={interpreter} setup.py test" returned exit code
> 13
The full build log is available from:
http://qa-logs.debian.net/2020/06/20/kombu_4.6.8-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: kombu
Source-Version: 4.6.11-1
Done: Michael Fladischer
We believe that the bug you reported is fixed in the latest version of
kombu, 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.
Michael Fladischer (supplier of updated kombu 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 14:53:43 +0200
Source: kombu
Architecture: source
Version: 4.6.11-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team
Changed-By: Michael Fladischer
Closes: 963419
Changes:
kombu (4.6.11-1) unstable; urgency=low
.
* New upstream release (Closes: #963419).
* Refresh patches.
* Add python3-botocore to Build-Depends-Indep, required by tests.
* Bump debhelper version to 13.
* Fix file name in d/copyright so lintian can correctly detect that it
exists.
* Remove debian/upstream-signing-key.pgp from include-binaries, no
longer used.
Checksums-Sha1:
1c1805cf89e4322fa68f7243b54e97f29c3d7512 2542 kombu_4.6.11-1.dsc
5b299e030a522bafe0dcd27469a30bef9dd647d2 406968 kombu_4.6.11.orig.tar.gz
214db0c0bcc04a442245da7956200874b35a3d4f 11896 kombu_4.6.11-1.debian.tar.xz
e435acdcf3d819d466ceeeb8b2c8ce314bfbb9fc 8902 kombu_4.6.11-1_amd64.buildinfo
Checksums-Sha256:
90e94b306b47988156ca5d20cb64a31d09b209a90cb396875bf222b7407bc0d9 2542
kombu_4.6.11-1.dsc
Bug#963419: marked as pending in kombu
Control: tag -1 pending Hello, Bug #963419 in kombu 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/python-team/modules/kombu/-/commit/ae26cccabec9ec3d50dba5fede4f50dcb3a02c93 New upstream release (Closes: #963419). (this message was generated automatically) -- Greetings https://bugs.debian.org/963419
Processed: Bug#963419 marked as pending in kombu
Processing control commands:
> tag -1 pending
Bug #963419 [src:kombu] kombu: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.8 --system=custom
"--test-args={interpreter} setup.py test" returned exit code 13
Added tag(s) pending.
--
963419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#959157: fix for CVE-2020-1749 in linux-image-4.19.0-9 breaks wireguard
Just to tie a loose end, it _does_ work fine on buster if you're actually on the latest kernel. If you have a long uptime and not rebooted, you will have these problems when it tries to compile wireguard for your currently used, old kernel, but there's no problem as such 4.19.0-9 anymore. -Timo signature.asc Description: OpenPGP digital signature
Processed: severity of 962650 is serious
Processing commands for cont...@bugs.debian.org: > severity 962650 serious Bug #962650 [src:libcamera] libcamera: API and ABI appear to be changing without a SONAME bump Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 962650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#733094: uvcdynctrl still filling the disk
Any movement on this, the issue was fixed upstream 5+ years ago but as of today, /lib/udev/uvcdynctrl in sid still contains debug=1 OK users can change that, but on the next upgrade it'll get reverted and fill the disk. Seems like a simple patch to change it to debug=0 by default and/or mark it as a conffile to not overwrite. Without this we can't install guvcview safely. If the fix isn't forthcoming then surely this needs to be upgraded to "grave" to prevent people installing it? Regards. -- Simon John
Processed: Re: zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint
Processing control commands: > tags -1 +moreinfo Bug #962424 [zfsutils-linux] zfsutils-linux: systemd zfs-mount-generator breaks boot if multiple datasets have the same mountpoint Added 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
Control: tags -1 +moreinfo Hello! Is that attached file literally what is in /etc/zfs/zfs-list.cache ? How was it generated, and how did it get there? Because it's wrong---it's space separated, and must be tab separated. Use -H, per man zfs-mount-generator, if it must be done by hand. Best, Antonio
Bug#963393: marked as done (harvid: FTBFS: Makefile:20: *** "libjpeg is required - install libjpeg-dev, libjpeg8-dev or libjpeg62-dev". Stop.)
Your message dated Tue, 30 Jun 2020 11:18:47 + with message-id and subject line Bug#963393: fixed in harvid 0.8.3-2 has caused the Debian Bug report #963393, regarding harvid: FTBFS: Makefile:20: *** "libjpeg is required - install libjpeg-dev, libjpeg8-dev or libjpeg62-dev". Stop. 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.) -- 963393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: harvid Version: 0.8.3-1 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): > ar cru libharvid.a decoder_ctrl.o ffdecoder.o frame_cache.o image_cache.o > timecode.o vinfo.o > ar: `u' modifier ignored since `D' is the default (see `U') > ranlib libharvid.a > make[3]: Leaving directory '/<>/libharvid' > make -C src > make[3]: Entering directory '/<>/src' > Makefile:20: *** "libjpeg is required - install libjpeg-dev, libjpeg8-dev or > libjpeg62-dev". Stop. > make[3]: Leaving directory '/<>/src' > make[2]: *** [Makefile:9: src] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/06/20/harvid_0.8.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: harvid Source-Version: 0.8.3-2 Done: =?utf-8?q?IOhannes_m_zm=C3=B6lnig_=28Debian/GNU=29?= We believe that the bug you reported is fixed in the latest version of harvid, 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. IOhannes m zmölnig (Debian/GNU) (supplier of updated harvid 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: SHA256 Format: 1.8 Date: Tue, 30 Jun 2020 12:08:34 +0200 Source: harvid Architecture: source Version: 0.8.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 912831 963393 Changes: harvid (0.8.3-2) unstable; urgency=medium . * Team upload. . * Drop build-test for libjpeg (Closes: #963393) * Update vim-common build dependency to xxd. Thanks to Helmut Grohne (Closes: #912831) * Bump dh-compat to 13 * Use https:// for Homepage-stanza * Bump standards-version to 4.5.0 * Declare that building this package does not require 'root' powers * Patch to fix spelling errors Checksums-Sha1: f4c89b096133d1d35f06c634af117e17e9cf39d2 2056 harvid_0.8.3-2.dsc 6f1a75426bb80c1a82f3cfb982da98c15e0bdc59 4828 harvid_0.8.3-2.debian.tar.xz 2bcfcb83af52d1ba6ee9dacab1577b94134afbde 9028 harvid_0.8.3-2_amd64.buildinfo Checksums-Sha256: b5026a87d631b383feb6dbe7936f6c33f2577cc227e0a412e1394e900e98433c 2056 harvid_0.8.3-2.dsc 6235156c9f02b3ed15af4d6000e0372be8b6c5c284ddc4aa1308e80ae3f720af 4828 harvid_0.8.3-2.debian.tar.xz 8da1055b99c45bbd221b4964d693c9da576ff6eb16449bc9aaed740bebddd9a3 9028 harvid_0.8.3-2_amd64.buildinfo Files: 233a30a9e196afc9d61cfe278cddaa71 2056 video optional harvid_0.8.3-2.dsc 485853edf7a8a1ed27be31503f4e0b16 4828 video optional harvid_0.8.3-2.debian.tar.xz 52f3a0bef3d0a273fad312144e93107f 9028 video optional harvid_0.8.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAl77G9cACgkQtlAZxH96 NvhHjA/9ETgcRZy8cTb5DbFh714wIhDDEi0cVCGe4nWqaUAsotgIJnld2mge36y9 ijTf24S/U8tJXymUCxXGLNzhY3vlx7CDMrO7GcT8Q1+QgusL+zy9JFAw9E2WBpBk E4ZvAoO0nSObYcefFkZR7NTJheQ2gdItE0MmEqyd4PANRheTee9Vm+K9xnqy6jel IPmBNg7W4GkohEOJsZVtLboidGkO2F5MJCTM/F360YRxVY+2yj5W1nMhuc9qV/Ru qfaXtliLT8RuT3IwMj/GjiODw5RdbyNlhLw+DSZmTDlXtJScJcfXFn6XW3z3nFv7 vq1vPiSLuPG+RgrbDJfB/wcPSnq2vLkCarSylk4LksV+JBwjXpVbVWaFaHsuKP8f
Processed: Bug#963393 marked as pending in harvid
Processing control commands: > tag -1 pending Bug #963393 [src:harvid] harvid: FTBFS: Makefile:20: *** "libjpeg is required - install libjpeg-dev, libjpeg8-dev or libjpeg62-dev". Stop. Added tag(s) pending. -- 963393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963393: marked as pending in harvid
Control: tag -1 pending Hello, Bug #963393 in harvid 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/harvid/-/commit/b881a3e91f3edd5cefba1463441439947294b214 Drop build-test for libjpeg Closes: #963393 (this message was generated automatically) -- Greetings https://bugs.debian.org/963393
Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup
* Simon McVittie [200630 11:23]: > On Tue, 30 Jun 2020 at 10:51:39 +0200, Chris Hofstaedtler wrote: > > I'm not sure it was a good idea before. Is static linking something > > you actively want to support for glib? > > It has worked in the past, Policy says the static library "is usually > provided", and we occasionally get bug reports from people who want to > link random libraries statically, so I didn't feel comfortable with > unilaterally disabling it for no particular reason. The autopkgtest > is there partly because things we don't test usually don't work, and > partly because static linking to libmount regressed during GLib's move > from Autotools to Meson (the pkg-config metadata in GLib was wrong); > I added it to confirm that the regression fix had been effective. > > If I'm disabling the static library because dependencies no longer > support it, then I can redirect bug reporters to the dependency and > let them argue their case there if they want to (as with libdbus, which > can't be linked statically any more due to libsystemd). Understood. Feel free to point people at libmount/src:util-linux. I'll see about removing libmount's static library in the -dev package. > People occasionally try to change Policy to say that static equivalents > of shared libraries are definitely optional, or even that they are > discouraged, but this never reaches consensus, because someone always > appears and says "well actually, I rely on Debian shipping shared libfoo > and libbar for armhf so that I can statically link them into a binary > for my embedded frobnicator device, which > (has glibc from 2005|doesn't have glibc|doesn't have space for glibc|...)". > The obvious counterpoint that solving this is not really Debian's job > is rarely effective. > > It is technically possible to link just the top of a dependency stack > statically (for example a GLib program with static GLib and libmount, > but dynamic libcryptsetup and glibc), but pkg-config doesn't make this > straightforward and in practice it requires hard-coding paths to static > libraries, so the autopkgtest in GLib doesn't attempt to exercise this. Thanks for the explanation! Best, Chris
Bug#963335: marked as done (autogen: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Tue, 30 Jun 2020 09:34:30 + with message-id and subject line Bug#963335: fixed in make-dfsg 4.3-4 has caused the Debian Bug report #963335, regarding autogen: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity 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.) -- 963335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: autogen Version: 1:5.18.16-4 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[3]: Leaving directory '/<>/xml2ag' > make[2]: Leaving directory '/<>/xml2ag' > Making check in doc > make[2]: Entering directory '/<>/doc' > make check-am > make[3]: Entering directory '/<>/doc' > make[3]: Nothing to be done for 'check-am'. > make[3]: Leaving directory '/<>/doc' > make[2]: Leaving directory '/<>/doc' > Making check in pkg > make[2]: Entering directory '/<>/pkg' > make[2]: Nothing to be done for 'check'. > make[2]: Leaving directory '/<>/pkg' > make[2]: Entering directory '/<>' > make[2]: Leaving directory '/<>' > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2020/06/20/autogen_5.18.16-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: make-dfsg Source-Version: 4.3-4 Done: Manoj Srivastava We believe that the bug you reported is fixed in the latest version of make-dfsg, 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. Manoj Srivastava (supplier of updated make-dfsg 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 00:58:36 -0700 Source: make-dfsg Architecture: source Version: 4.3-4 Distribution: unstable Urgency: high Maintainer: Manoj Srivastava Changed-By: Manoj Srivastava Closes: 963335 Changes: make-dfsg (4.3-4) unstable; urgency=high . * Cherry picked [SV 58232] Disable inheritance of jobserver FDs for recursive make from ther development branch * Bug fix: "FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity", thanks to Lucas Nussbaum (Closes: #963335). Checksums-Sha1: 9c0ee95e574fca66d75a114b8965143c7670bfcd 1657 make-dfsg_4.3-4.dsc 1114cfb2639f41ac9a10425e44f3be4633cd179a 50880 make-dfsg_4.3-4.diff.gz Checksums-Sha256: f647a112fa53ecb8707247741cb3aab4a0a6899fb466bdb4bbd44d30604168da 1657 make-dfsg_4.3-4.dsc 6f4196d2d8fe593e61a58cc885b6ea8ecf9b19d6a4e64bc9a32bb966f7d9a699 50880 make-dfsg_4.3-4.diff.gz Files: f93c05b440d8dfc6498a99a8dcfd0a27 1657 devel optional make-dfsg_4.3-4.dsc 6a2664fdee9c6f36508930f16eaf1dd7 50880 devel optional make-dfsg_4.3-4.diff.gz -BEGIN PGP SIGNATURE- iNoEARYKAIIWIQQO92S3P16UNa7t1nMNYuRk6Juj4gUCXvsERU8UgAAbACtz cml2YXN0YUBnb2xkZW4tZ3J5cGhvbi5jb20wRUY3NjRCNzNGNUU5NDM1QUVFREQ2 NzMwRDYyRTQ2NEU4OUJBM0UyXzI0FBxzcml2YXN0YUBkZWJpYW4ub3JnAAoJEA1i 5GTom6Pi9OsBAM+u9YcrMGjD4J7xX8tPiXA0XqWagKaQAePN7QMhVR5CAQDpNqfC N85aray7UXAWpf+GbEwfIRoBLoK1DEVEKTiCDQ== =CACO -END PGP SIGNATURE End Message ---
Bug#963734: marked as done (make: breaks autogen make check)
Your message dated Tue, 30 Jun 2020 09:34:30 + with message-id and subject line Bug#963335: fixed in make-dfsg 4.3-4 has caused the Debian Bug report #963335, regarding make: breaks autogen make check 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.) -- 963335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: make Version: 4.3-1 Severity: normal Hello, upgrading make from 4.2.1-2+b1 to 4.3-1 (or 4.3-3) lets autogen FTBFS on parallel builds (-j2 and higher). All tests are run successfully but make just hangs: ametzler@argenau:~$ pstree -aph 243168 dpkg-buildpacka,243168 /usr/bin/dpkg-buildpackage -uc -us -rfakeroot -j2 └─rules,243213 -f debian/rules binary └─dh,243216 /usr/bin/dh binary └─dh_auto_test,251687 /usr/bin/dh_auto_test └─make,251831 -j2 check VERBOSE=1 cu Andreas --- End Message --- --- Begin Message --- Source: make-dfsg Source-Version: 4.3-4 Done: Manoj Srivastava We believe that the bug you reported is fixed in the latest version of make-dfsg, 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. Manoj Srivastava (supplier of updated make-dfsg 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 00:58:36 -0700 Source: make-dfsg Architecture: source Version: 4.3-4 Distribution: unstable Urgency: high Maintainer: Manoj Srivastava Changed-By: Manoj Srivastava Closes: 963335 Changes: make-dfsg (4.3-4) unstable; urgency=high . * Cherry picked [SV 58232] Disable inheritance of jobserver FDs for recursive make from ther development branch * Bug fix: "FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity", thanks to Lucas Nussbaum (Closes: #963335). Checksums-Sha1: 9c0ee95e574fca66d75a114b8965143c7670bfcd 1657 make-dfsg_4.3-4.dsc 1114cfb2639f41ac9a10425e44f3be4633cd179a 50880 make-dfsg_4.3-4.diff.gz Checksums-Sha256: f647a112fa53ecb8707247741cb3aab4a0a6899fb466bdb4bbd44d30604168da 1657 make-dfsg_4.3-4.dsc 6f4196d2d8fe593e61a58cc885b6ea8ecf9b19d6a4e64bc9a32bb966f7d9a699 50880 make-dfsg_4.3-4.diff.gz Files: f93c05b440d8dfc6498a99a8dcfd0a27 1657 devel optional make-dfsg_4.3-4.dsc 6a2664fdee9c6f36508930f16eaf1dd7 50880 devel optional make-dfsg_4.3-4.diff.gz -BEGIN PGP SIGNATURE- iNoEARYKAIIWIQQO92S3P16UNa7t1nMNYuRk6Juj4gUCXvsERU8UgAAbACtz cml2YXN0YUBnb2xkZW4tZ3J5cGhvbi5jb20wRUY3NjRCNzNGNUU5NDM1QUVFREQ2 NzMwRDYyRTQ2NEU4OUJBM0UyXzI0FBxzcml2YXN0YUBkZWJpYW4ub3JnAAoJEA1i 5GTom6Pi9OsBAM+u9YcrMGjD4J7xX8tPiXA0XqWagKaQAePN7QMhVR5CAQDpNqfC N85aray7UXAWpf+GbEwfIRoBLoK1DEVEKTiCDQ== =CACO -END PGP SIGNATURE End Message ---
Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup
On Tue, 30 Jun 2020 at 10:51:39 +0200, Chris Hofstaedtler wrote: > I'm not sure it was a good idea before. Is static linking something > you actively want to support for glib? It has worked in the past, Policy says the static library "is usually provided", and we occasionally get bug reports from people who want to link random libraries statically, so I didn't feel comfortable with unilaterally disabling it for no particular reason. The autopkgtest is there partly because things we don't test usually don't work, and partly because static linking to libmount regressed during GLib's move from Autotools to Meson (the pkg-config metadata in GLib was wrong); I added it to confirm that the regression fix had been effective. If I'm disabling the static library because dependencies no longer support it, then I can redirect bug reporters to the dependency and let them argue their case there if they want to (as with libdbus, which can't be linked statically any more due to libsystemd). People occasionally try to change Policy to say that static equivalents of shared libraries are definitely optional, or even that they are discouraged, but this never reaches consensus, because someone always appears and says "well actually, I rely on Debian shipping shared libfoo and libbar for armhf so that I can statically link them into a binary for my embedded frobnicator device, which (has glibc from 2005|doesn't have glibc|doesn't have space for glibc|...)". The obvious counterpoint that solving this is not really Debian's job is rarely effective. It is technically possible to link just the top of a dependency stack statically (for example a GLib program with static GLib and libmount, but dynamic libcryptsetup and glibc), but pkg-config doesn't make this straightforward and in practice it requires hard-coding paths to static libraries, so the autopkgtest in GLib doesn't attempt to exercise this. smcv
Bug#963990: marked as done (libemf: FTBFS everywhere)
Your message dated Tue, 30 Jun 2020 09:18:51 + with message-id and subject line Bug#963990: fixed in libemf 1.0.13-2 has caused the Debian Bug report #963990, regarding libemf: FTBFS everywhere 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.) -- 963990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libemf Version: 1.0.13-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) libemf fails to build everywhere: | dh_missing: warning: usr/lib/x86_64-linux-gnu/libEMF.la exists in debian/tmp but is not installed to anywhere | dh_missing: error: missing files, aborting | The following debhelper tools have reported what they installed (with files per package) |* dh_install: libemf-dev (3), libemf-doc (0), libemf1 (2), printemf (1) |* dh_installdocs: libemf-dev (0), libemf-doc (4), libemf1 (0), printemf (0) |* dh_installman: libemf-dev (0), libemf-doc (73), libemf1 (0), printemf (0) | If the missing files are installed by another tool, please file a bug against it. | When filing the report, if the tool is not part of debhelper itself, please reference the | "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). | (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) | Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built | For a short-term work-around: Add the files to debian/not-installed | make: *** [debian/rules:6: binary-arch] Error 25 For example, see https://buildd.debian.org/status/fetch.php?pkg=libemf=amd64=1.0.13-1=1593211525=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: libemf Source-Version: 1.0.13-2 Done: b...@debian.org (Barak A. Pearlmutter) We believe that the bug you reported is fixed in the latest version of libemf, 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. Barak A. Pearlmutter (supplier of updated libemf 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 10:06:19 +0100 Source: libemf Architecture: source Version: 1.0.13-2 Distribution: unstable Urgency: medium Maintainer: Barak A. Pearlmutter Changed-By: Barak A. Pearlmutter Closes: 963990 Changes: libemf (1.0.13-2) unstable; urgency=medium . * .la files are not installed on purpose (closes: #963990) Checksums-Sha1: 02e37212aebb32944d0b3f056a52da45d997df7f 2496 libemf_1.0.13-2.dsc 08e3f9ff715f5ebd23d66c9081be0ea53971b43f 30280 libemf_1.0.13-2.debian.tar.xz 594f76582720acd84b05e8d1b3e9c1882951b963 10288 libemf_1.0.13-2_source.buildinfo Checksums-Sha256: d89a4472da146c92d3125fcedacc0d35088344a7527e7461234faf346f77476a 2496 libemf_1.0.13-2.dsc 44e647d2c2ecd004d97ec7ea5e12c2efe516e59aacbc32b81168e877d044a0ca 30280 libemf_1.0.13-2.debian.tar.xz 819a3ca73cc36d2018af8e6b6755f5e3971b9750dcdfbe4cd27170549d4fccb7 10288 libemf_1.0.13-2_source.buildinfo Files: 152d429010dc6848365e88722299f489 2496 libs optional libemf_1.0.13-2.dsc 2d141b7d773c524cffda8fb2a19c97d8 30280 libs optional libemf_1.0.13-2.debian.tar.xz 9a44251b5611684376eb6b78879a491c 10288 libs optional libemf_1.0.13-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEZPQp426hHMLZZlRvEltXR14ZDRgFAl77AKwPHGJhcEBkZWJp YW4ub3JnAAoJEBJbV0deGQ0YjoIP/jZSGxiALN3w8rzv7TH+yfQSyZqEjLaBa/Fa rUdTDW1/eBXsCXLaml8Tl2QD54AhQ0jpfaNvAszkLTTuQ3LYe2aMAlMqS+DwTTx9 w2ifVU6G3C/WVfCfotV4qyKAX1u1cihOhHdMT5LYpuJXLeDew1JR2hR0lAlLW+Go ayPNcHFAa/2lzoYsGXeKi2PClLQOTDCdXn6sonHOhRBZ3oRYQkvgmqtMGDP9wb8N j3FpZvq/RTtklWEIp1J9KHvw0kH6nSH7egB+mLqK01xYgGnBmRWPFpoMeQizPVsA eTNQQr4Aq4cnORvSCn7UGGU+U4wZrkI61wWbIWKuEaLMr6Bx336c/SmoOTdTZZNl dzFEsAjBj0M4mQKE4V0TPmB9fwxe5N0fIi6llF5mfpFEtFHgufXb7r3e7210KfnH /1IR+S+1qeL1g2wNPQIRAWOjp2Ww7dvl9AhJ8wEjHYc7nrLWBdScuvYWyMvvD3Xv XAbPuvW3Un+Aj9AZ5VO9y5sE3VWPGVAO70vLud16EM4eUEtX5B7zbTlzah+UButQ
Bug#955020: marked as done (php-horde-form: CVE-2020-8866)
Your message dated Tue, 30 Jun 2020 09:04:19 + with message-id and subject line Bug#955020: fixed in php-horde-form 2.0.20-1 has caused the Debian Bug report #955020, regarding php-horde-form: CVE-2020-8866 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.) -- 955020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-horde-form Version: 2.0.19-1 Severity: important Tags: security upstream Control: found -1 2.0.18-3.1 Control: found -1 2.0.15-1+deb9u1 Control: found -1 2.0.15-1 Hi, The following vulnerability was published for php-horde-form. CVE-2020-8866[0]: | This vulnerability allows remote attackers to create arbitrary files | on affected installations of Horde Groupware Webmail Edition 5.2.22. | Authentication is required to exploit this vulnerability. The specific | flaw exists within add.php. The issue results from the lack of proper | validation of user-supplied data, which can allow the upload of | arbitrary files. An attacker can leverage this in conjunction with | other vulnerabilities to execute code in the context of the www-data | user. Was ZDI-CAN-10125. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-8866 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8866 Regards, Salvatore --- End Message --- --- Begin Message --- Source: php-horde-form Source-Version: 2.0.20-1 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of php-horde-form, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated php-horde-form 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: SHA256 Format: 1.8 Date: Tue, 30 Jun 2020 10:36:20 +0200 Source: php-horde-form Architecture: source Version: 2.0.20-1 Distribution: unstable Urgency: medium Maintainer: Horde Maintainers Changed-By: Mike Gabriel Closes: 955020 Changes: php-horde-form (2.0.20-1) unstable; urgency=medium . [ Juri Grabowski ] * New upstream version 2.0.20 * SECURITY: Prevent ability to specify temporary filename (CVE-2020-8866) (Closes: #955020). . [ Mike Gabriel ] * d/salsa-ci.yml: Add file with salsa-ci.yml and pipeline-jobs.yml calls. * d/control: Bump DH compat level to version 13. * d/control: Add to Uploaders: Juri Grabowski. Checksums-Sha1: af5162b88ec4318ab69db428b36ebda4a94180a7 2063 php-horde-form_2.0.20-1.dsc fa7b0bb1c927176c54c38cf94b886e6291c84cad 198229 php-horde-form_2.0.20.orig.tar.gz ad0747258858e8623ea6eb14370b16e57d414b03 3368 php-horde-form_2.0.20-1.debian.tar.xz dfcbeabbba8264ae4a7573fecd19083be7b15b17 7024 php-horde-form_2.0.20-1_source.buildinfo Checksums-Sha256: f3945070f3b2ee8590ae3b59977076debf7398fc82c45b552e02f7c310bc6790 2063 php-horde-form_2.0.20-1.dsc dc2c993464d7f192c938cfbb4cbe9630bce6d23ce141a0a52efb83a71b99e177 198229 php-horde-form_2.0.20.orig.tar.gz 70f21b9803a04088f7aad3edbe64c6234991bb749d5ba5df9bb00c8ae9e3d682 3368 php-horde-form_2.0.20-1.debian.tar.xz 28de4848d620b05c9dce02a8aea9a0998ecb8f4e6d62538923e1b1d6d6634ace 7024 php-horde-form_2.0.20-1_source.buildinfo Files: 8b4434af56523a74cb0dade900cc697b 2063 php optional php-horde-form_2.0.20-1.dsc 6a7a2b3d5c7163fe68b0587aaeef6361 198229 php optional php-horde-form_2.0.20.orig.tar.gz 3dcd1c2b70f54a775a68ad08a98c81ae 3368 php optional php-horde-form_2.0.20-1.debian.tar.xz ce7863a7a0d959101ef378496e5ae61c 7024 php optional php-horde-form_2.0.20-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl76+aQVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxB9YQAJU1FYbED48AZCofeDmtqTSG9/vc 02PWbrpXE6l5jTooFHg6oIKXJeIuUsI8I8Sk8BYO3KT0Z5b/yfvQMbN8Y2x+MZo2 WnHbyS/rk2E2C2BZgb/WSRocjZnguWr5VtHPg1MIJtv445bvO7gY8S+5uCO1jV3q efElXd+uu+SR9kzgfvLy5NHQR6UTx2bRwuhkjOtpYVq8H2pAoQTBpDBWhIkrZ0Mi
Bug#955019: marked as done (php-horde-trean: CVE-2020-8865)
Your message dated Tue, 30 Jun 2020 09:04:25 + with message-id and subject line Bug#955019: fixed in php-horde-trean 1.1.10-1 has caused the Debian Bug report #955019, regarding php-horde-trean: CVE-2020-8865 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.) -- 955019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-horde-trean Version: 1.1.9-4 Severity: important Tags: security upstream Control: found -1 1.1.9-3 Hi, The following vulnerability was published for php-horde-trean. CVE-2020-8865[0]: | This vulnerability allows remote attackers to execute local PHP files | on affected installations of Horde Groupware Webmail Edition 5.2.22. | Authentication is required to exploit this vulnerability. The specific | flaw exists within edit.php. When parsing the params[template] | parameter, the process does not properly validate a user-supplied path | prior to using it in file operations. An attacker can leverage this in | conjunction with other vulnerabilities to execute code in the context | of the www-data user. Was ZDI-CAN-10469. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-8865 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8865 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: php-horde-trean Source-Version: 1.1.10-1 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of php-horde-trean, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated php-horde-trean 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: SHA256 Format: 1.8 Date: Tue, 30 Jun 2020 10:44:28 +0200 Source: php-horde-trean Architecture: source Version: 1.1.10-1 Distribution: unstable Urgency: medium Maintainer: Horde Maintainers Changed-By: Mike Gabriel Closes: 955019 Changes: php-horde-trean (1.1.10-1) unstable; urgency=medium . [ Juri Grabowski ] * New upstream version 1.1.10 * SECURITY: The Trean application of the Horde Application Framework contained a directory traversal vulnerability (CVE-2020-8865) resulting from insufficient input sanitization. An authenticated remote attacker could use this flaw to execute code in the context of the web server user. (Closes: #955019). . [ Mike Gabriel ] * d/salsa-ci.yml: Add file with salsa-ci.yml and pipeline-jobs.yml calls. * d/control: Bump DH compat level to version 13. * d/control: Add to Uploaders: Juri Grabowski. Checksums-Sha1: b03e50b532a3bb81f2e962e4c8a291eb8a6cd006 2090 php-horde-trean_1.1.10-1.dsc ecd495cf90e5a262e4417bfd6585e901f2fbb2af 664691 php-horde-trean_1.1.10.orig.tar.gz 7cb3d1e0dfca2cae0fce86cb179c48796e25375e 4164 php-horde-trean_1.1.10-1.debian.tar.xz 5909516ca2f5e7e4f2d89c34e5c3e9ab7eb08e93 7059 php-horde-trean_1.1.10-1_source.buildinfo Checksums-Sha256: c835e7d1d23a15130fb6dd76861b0331ae4f1507acda20c874164debcd186f79 2090 php-horde-trean_1.1.10-1.dsc c1a24d64b4a88976005eea21c9e5939572e8e957e159e73698a9a042868738d5 664691 php-horde-trean_1.1.10.orig.tar.gz ea401d05c48e0aed29b152823e65333449a8d9f9f6bffafd29c81333b792de5b 4164 php-horde-trean_1.1.10-1.debian.tar.xz f8763b22092d826c76f96d345f30b6675adb72dbf3d2a51f041c67ee547a77ef 7059 php-horde-trean_1.1.10-1_source.buildinfo Files: fbb831901636eae7ab043ffdd7841b29 2090 php optional php-horde-trean_1.1.10-1.dsc f85a80bef474994f27622beb3563d94c 664691 php optional php-horde-trean_1.1.10.orig.tar.gz 8f732c539bfe4ebf1e8c1d6e6efaf491 4164 php optional php-horde-trean_1.1.10-1.debian.tar.xz 2344708d5c5bfe55c22bc6f91c12b584 7059 php optional php-horde-trean_1.1.10-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl76/FkVHHN1bndlYXZl
Bug#963853: [Pkg-clamav-devel] Bug#963853: clamav: FTBFS on IPv6-only environments
On Tue, Jun 30, 2020 at 08:28:15AM +0200, Sebastian Andrzej Siewior wrote: > On 2020-06-28 12:48:20 [+0100], Dominic Hargreaves wrote: > > Source: clamav > > Version: 0.102.3+dfsg-1 > > Severity: serious > > Justification: FTBFS (when it built before) > > > > During archive-wide test rebuilding of an IPv6-only environment (which > > Is this decision blessed by the release team? If so where is it > documented? If you're asking about the decision to introduce IPv-only buildds, then I don't really know the answer. I was unable to find any announcement/discussion about an introduction of ipv6 only buildds, unfortunately. But the buildds are there - the perl team has had this happen on several occasions during normal uploads. We (perl team) did a full archive rebuild to assess the impact, which seems to be around 25 non-perl-related packages. We should probably add a usertag and maybe post more generally about this to centralise the discussion. Best Dominic
Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup
* Simon McVittie [200629 01:16]: > On Sun, 28 Jun 2020 at 22:00:58 +0200, Chris Hofstaedtler wrote: > > the autopkgtest suite offers quite interesting behaviour: > > With an installed libcryptsetup-dev, ld fails with "cannot find > > -lcryptsetup". > ... > > I imagine this might be caused by libcryptsetup-dev not shipping an > > .a library. > > This means that GLib could previously be successfully statically linked > (and we had a test to prove it), and now it cannot. > > Do you consider this to be a deliberate change? Is statically linking > a library that depends on libmount no longer supported? I'm not sure it was a good idea before. Is static linking something you actively want to support for glib? For libmount, if we want to support verity, this appears to be out of the question -- libcryptsetup will always make this impossible. While turning off verity will give us temporarily a libmount that can be statically linked again, I can imagine future changes pulling in libdevice-mapper. Then we'll be in another static-binary-with-dlopen situation. Which wont't work, AFAIK. Might be hypothetical, but all this "low level" stuff is quite dynamic nowadays. > (If it is, then we might as well stop providing static libraries for > GLib too, and you might as well stop providing static libraries for > libmount.) (Indeed.) Chris
Bug#960880: marked as done (pev: autopkgtest failure: pehash did not report ASLR status)
Your message dated Tue, 30 Jun 2020 08:35:48 + with message-id and subject line Bug#960880: fixed in pev 0.80-5 has caused the Debian Bug report #960880, regarding pev: autopkgtest failure: pehash did not report ASLR status 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.) -- 960880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pev Version: 0.80-4 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package pev has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest are now considered RC in testing. Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/pev/5529710/log.gz autopkgtest [13:21:31]: test test-runs: [--- valgrind is /usr/bin/valgrind ==831== Memcheck, a memory error detector ==831== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==831== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==831== Command: pesec /usr/share/win32/gzip.exe ==831== plugins: could not open directory 'src/build/plugins' -- No such file or directory ==831== ==831== HEAP SUMMARY: ==831== in use at exit: 18 bytes in 1 blocks ==831== total heap usage: 3 allocs, 2 frees, 4,602 bytes allocated ==831== ==831== LEAK SUMMARY: ==831==definitely lost: 0 bytes in 0 blocks ==831==indirectly lost: 0 bytes in 0 blocks ==831== possibly lost: 0 bytes in 0 blocks ==831==still reachable: 18 bytes in 1 blocks ==831== suppressed: 0 bytes in 0 blocks ==831== Rerun with --leak-check=full to see details of leaked memory ==831== ==831== For lists of detected and suppressed errors, rerun with: -s ==831== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) error: pesec did not report ASLR status ==833== Memcheck, a memory error detector ==833== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==833== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==833== Command: pehash /usr/share/win32/gzip.exe ==833== plugins: could not open directory 'src/build/plugins' -- No such file or directory ==833== ==833== HEAP SUMMARY: ==833== in use at exit: 18 bytes in 1 blocks ==833== total heap usage: 3 allocs, 2 frees, 4,602 bytes allocated ==833== ==833== LEAK SUMMARY: ==833==definitely lost: 0 bytes in 0 blocks ==833==indirectly lost: 0 bytes in 0 blocks ==833== possibly lost: 0 bytes in 0 blocks ==833==still reachable: 18 bytes in 1 blocks ==833== suppressed: 0 bytes in 0 blocks ==833== Rerun with --leak-check=full to see details of leaked memory ==833== ==833== For lists of detected and suppressed errors, rerun with: -s ==833== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) error: pehash did not report ASLR status autopkgtest [13:21:33]: test test-runs: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: pev Source-Version: 0.80-5 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of pev, 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. Adrian Bunk (supplier of updated pev 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 11:09:02 +0300 Source: pev Architecture: source Version: 0.80-5 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Adrian Bunk Closes: 960880 Changes: pev (0.80-5) unstable; urgency=low . * QA upload. * Fix the autopkgtest. (Closes: #960880) Checksums-Sha1: 5f37c0939ddeac36b35c9d8e3c9019e0a049cdeb 1851 pev_0.80-5.dsc 85dd8a45a6a36376ff4598954f1e561b3c4efaf1 4648 pev_0.80-5.debian.tar.xz Checksums-Sha256:
Bug#959507: marked as done (dub: flaky autopkgtest: Package dub not found for registry at https://code.dlang.org/)
Your message dated Tue, 30 Jun 2020 08:34:36 + with message-id and subject line Bug#959507: fixed in dub 1.19.0-1.1 has caused the Debian Bug report #959507, regarding dub: flaky autopkgtest: Package dub not found for registry at https://code.dlang.org/ 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.) -- 959507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dub Version: 1.19.0-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky needs-internet Dear maintainer(s), You package has an autopkgtest, great. However, since 1.19.0-1 it seems to regularly fail. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Please either fix the test to be more robust, or use the "flaky" restriction for the offending test until a solution has been found. On top of that, it seems that your test requires internet to test the functionality of your package. We recently added a needs-internet restriction to autopkgtest that you'll have to add to your control file to ensure this is known. I copied the output at the bottom of this report. All the failing tests that I inspected look like it. I'll have the migration software ignore the results of your autopkgtest until this bug is fixed. Paul https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dub/5200977/log.gz autopkgtest [05:47:55]: test run: [--- Package dub not found for registry at https://code.dlang.org/ (fallbacks registry at https://code-mirror.dlang.io/, registry at https://dub-registry.herokuapp.com/): HTTP request returned status code 0 () Getting a release version failed: No package dub was found matching the dependency >=0.0.0 Retry with ~master... Package dub not found for registry at https://code.dlang.org/ (fallbacks registry at https://code-mirror.dlang.io/, registry at https://dub-registry.herokuapp.com/): HTTP request returned status code 0 () No package dub was found matching the dependency ~master autopkgtest [05:48:25]: test run: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: dub Source-Version: 1.19.0-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of dub, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated dub 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, 16 Jun 2020 09:55:55 +0300 Source: dub Architecture: source Version: 1.19.0-1.1 Distribution: unstable Urgency: low Maintainer: Debian D Language Group Changed-By: Adrian Bunk Closes: 959507 Changes: dub (1.19.0-1.1) unstable; urgency=low . * Non-maintainer upload. * Add a needs-internet restriction to the autopkgtest. (Closes: #959507) Checksums-Sha1: f1f65c5ad8a6d86deaf59cc2017e782e02f50096 1924 dub_1.19.0-1.1.dsc e8ea79d558af7ad23b51fd053e1f0f5a9ec5ccac 4348 dub_1.19.0-1.1.debian.tar.xz Checksums-Sha256: 681011ac7f9c3d354bfb342eb1150a659f212669055f028f27ff9e52ad25624e 1924 dub_1.19.0-1.1.dsc e95e0137779642e46be02688fc78d49936d5d9dc55e2cb01a7e38827b2c30235 4348 dub_1.19.0-1.1.debian.tar.xz Files: 9eb1ae4cd53db53c155588a43c5dc3c8 1924 devel optional dub_1.19.0-1.1.dsc fcd971e4b31ef714ec5fede18e3f7cdd 4348 devel optional dub_1.19.0-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7obV0ACgkQiNJCh6LY mLE6thAApbFLWyJF/cs3p14pvBU4gvzaivzecBksbnTXEqU6Y5SinloYPAqHBfTI zFtV1XDwnQKOYNlgEWAt1E+3uoDdUoXrFx7S78Y66BKJ7DNbwbv+uVWnr5KhiAn3 6iV/hM7JYnEMN4yHWnmaA1RfxAx6XmyqYvTruaitp8/pLGSZVogyrkCOPxys7g76 gCGcIaFPtsvh39iaYGpjhsiiXNjX1E63rUY8QA1axEchlfPDSFMVPIKLrsbdbvL0
Bug#964002: closing 964002
close 964002 0.7.2-4 thanks
Processed: closing 964002
Processing commands for cont...@bugs.debian.org: > close 964002 0.7.2-4 Bug #964002 [librostime1d] librostime1d: missing Breaks+Replaces: librostime0d (>= 0.7.2) Marked as fixed in versions ros-roscpp-core/0.7.2-4. Bug #964002 [librostime1d] librostime1d: missing Breaks+Replaces: librostime0d (>= 0.7.2) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 964002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964004: jest: missing Breaks+Replaces: node-typescript-types (<< 20200626)
Package: jest Version: 24.9.0+ds-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../jest_24.9.0+ds-3_all.deb ... Unpacking jest (24.9.0+ds-3) ... dpkg: error processing archive /var/cache/apt/archives/jest_24.9.0+ds-3_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/@types/jest/index.d.ts', which is also in package node-typescript-types 20200219-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/jest_24.9.0+ds-3_all.deb cheers, Andreas node-typescript-types=20200219-1_jest=24.9.0+ds-3.log.gz Description: application/gzip
Bug#964002: librostime1d: missing Breaks+Replaces: librostime0d (>= 0.7.2)
Package: librostime1d Version: 0.7.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../librostime1d_0.7.2-3_amd64.deb ... Unpacking librostime1d:amd64 (0.7.2-3) ... dpkg: error processing archive /var/cache/apt/archives/librostime1d_0.7.2-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/librostime.so.0.7.2', which is also in package librostime0d:amd64 0.7.2-2 Errors were encountered while processing: /var/cache/apt/archives/librostime1d_0.7.2-3_amd64.deb cheers, Andreas librostime0d=0.7.2-2_librostime1d=0.7.2-3.log.gz Description: application/gzip
Bug#963853: [Pkg-clamav-devel] Bug#963853: clamav: FTBFS on IPv6-only environments
On 2020-06-28 12:48:20 [+0100], Dominic Hargreaves wrote: > Source: clamav > Version: 0.102.3+dfsg-1 > Severity: serious > Justification: FTBFS (when it built before) > > During archive-wide test rebuilding of an IPv6-only environment (which Is this decision blessed by the release team? If so where is it documented? Sebastian
