Bug#959561: guile-ssh: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2
On 2020-05-03, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): >> make[5]: Entering directory '/<>/tests' ... >> FAIL: dist.scm >> >>Guile-SSH 0.11.3: tests/test-suite.log >> >> >> # TOTAL: 11 >> # PASS: 10 >> # SKIP: 0 >> # XFAIL: 0 >> # FAIL: 1 >> # XPASS: 0 >> # ERROR: 0 >> >> .. contents:: :depth: 2 >> >> FAIL: dist >> == >> >> Starting test dist (Writing full log to "dist.log") >> >> Some deprecated features have been used. Set the environment >> variable GUILE_WARN_DEPRECATED to "detailed" and rerun the >> program to get more information. Set it to "no" to suppress >> this message. >> Starting test dist (Writing full log to "dist.log") >> tests/dist.scm:216: FAIL with-ssh >> # of expected passes 18 >> # of unexpected failures 1 ... >> Test begin: >> test-name: "with-ssh" >> source-file: "tests/dist.scm" >> source-line: 216 >> source-form: (test-assert "with-ssh" (begin (set-log-userdata! "with-ssh") >> (run-client-test (lambda (server) (server-listen server) (server-set! server >> (quote log-verbosity) (quote functions)) (let ((session (server-accept >> server))) (server-handle-key-exchange session) (start-session-loop session >> (lambda (msg type) (format-log/scm (quote nolog) "server" "msg: ~a; type: >> ~a" msg type) (case (car type) ((request-channel-open) (let ((c >> (message-channel-request-open-reply-accept msg))) (format-log/scm (quote >> nolog) "server" "channel 0: ~a" c) (write-line "Enter `,help' for help." c) >> (format-log/scm (quote nolog) "server" "channel 1: ~a" c) (usleep 100) (poll >> c (lambda args (let ((result (read-line c))) (format-log/scm (quote nolog) >> "server" "sexp: ~a" result) (or (string=? result "(begin (+ 21 21))") (error >> "Wrong result 1" result))) (let ((result (read-line c))) (format-log/scm >> (quote nolog) "server" "sexp: ~a" result) (or (string=? result "(newline)") >> (error "Wrong result 2" result))) (write-line "scheme@(guile-user)> $1 = >> 42\n" c) (sleep 5) (close c) (while #t (sleep 60)) (else >> (message-reply-success msg))) (lambda () (call-with-connected-session >> (lambda (session) (authenticate-server session) (format-log/scm (quote >> nolog) "client" "session: ~a" session) (unless (equal? (userauth-none! >> session) (quote success)) (error "Could not authenticate with a server" >> session)) (let ((n (make-node session #:start-repl-server? #f))) (= >> (with-ssh n (+ 21 21)) 42 >> result) (or (string=? result "(newline)") (error "Wrong result 2" result))) >> (write-line "scheme@(guile-user)> $1 = 42\n" c) (sleep 5) (close c) (while >> #t (sleep 60)) (else (message-reply-success msg))) (lambda () >> (call-with-connected-session (lambda (session) (authenticate-server session) >> (format-log/scm (quote nolog) "client" "session: ~a" session) (unless >> (equal? (userauth-none! session) (quote success)) (error "Could not >> authenticate with a server" session)) (let ((n (make-node session >> #:start-repl-server? #f))) (= (with-ssh n (+ 21 21)) 42 >> Test end: >> result-kind: fail >> actual-value: #f >> actual-error: (guile-ssh-error "read_from_channel_port" "Error reading >> from the channel" # #f) >> Group end: dist >> # of expected passes 18 >> # of unexpected failures 1 >> FAIL dist.scm (exit status: 1) ... > The full build log is available from: >http://qa-logs.debian.net/2020/05/01/guile-ssh_0.11.3-2_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! I can't reproduce this issue on amd64 or arm64, with versions 0.11.3-2 (sid/bullseye) or 0.12.0-1 (experimental). Both versions also built fine on the buildd's, originally... Reading the above mentioned wiki page, I tried building without network to ensure it wasn't somehow trying to ssh over the network, but the tests passed. How is network disabled in your tests? According to https://tests.reproducible-builds.org/debian/guile-ssh, amd64 and arm64 have failures, but they appear to be different tests entirely. > 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. All my tests were also on updated, clean, minimal chroots... is there anything unusual with your test setup not mentioned on the FAQ? > Every failed build was retried once to eliminate random failures. Did the retried build fail in the same way vs. just testing that it failed twice? Thanks for all your QA work! live well, vagrant signature.asc Description: PGP signature
Bug#960458: marked as done (libreswan: CVE-2020-1763)
Your message dated Fri, 22 May 2020 23:18:39 + with message-id and subject line Bug#960458: fixed in libreswan 3.32-1 has caused the Debian Bug report #960458, regarding libreswan: CVE-2020-1763 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.) -- 960458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libreswan Version: 3.29-2 Severity: important Tags: security upstream Control: found -1 3.27-6 Hi, The following vulnerability was published for libreswan. CVE-2020-1763[0]: | An out-of-bounds buffer read flaw was found in the pluto daemon of | libreswan from versions 3.27 till 3.31 where, an unauthenticated | attacker could use this flaw to crash libreswan by sending specially- | crafted IKEv1 Informational Exchange packets. The daemon respawns | after the crash. 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-1763 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1763 [1] https://libreswan.org/security/CVE-2020-1763/CVE-2020-1763.txt Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: libreswan Source-Version: 3.32-1 Done: Daniel Kahn Gillmor We believe that the bug you reported is fixed in the latest version of libreswan, 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. Daniel Kahn Gillmor (supplier of updated libreswan 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: Fri, 22 May 2020 18:33:46 -0400 Source: libreswan Architecture: source Version: 3.32-1 Distribution: unstable Urgency: medium Maintainer: Daniel Kahn Gillmor Changed-By: Daniel Kahn Gillmor Closes: 931858 958355 960458 Changes: libreswan (3.32-1) unstable; urgency=medium . [ Stephen Kitt ] * Remove the systemd dependency (Closes: #931858) . [ Daniel Kahn Gillmor ] * New upstream version, fixing CVE-2020-1763 (Closes: #960458) * refresh patches, dropping those already applied upstream * Standards-Version: bump to 4.5.0 (no changes needed) * move to dh 13 * drop unneeded lintian-override * d/copyright: drop annotations for removed source * move subcommand executables from /usr/lib/ipsec to /usr/libexec/ipsec * fix upstream spelling errors * added buildtime and runtime checks that the crypto works as expected * include upstream patch to address subtle NSS API variance * autopkgtest: add CAVP/ACVP tests * use dh_auto_build instead of $(MAKE) when building * enable cross-building (Closes: #958355) * d/tests/opportunistic: avoid dropping into a pager if run from a terminal Checksums-Sha1: 31826973bacaed30cdc237fb6448ab619083e41e 2028 libreswan_3.32-1.dsc d752c8df37c90733a01c24849d439733acd4e8f0 4141631 libreswan_3.32.orig.tar.gz a4d354143c609abf9f90075ef8ab6a5d71835095 858 libreswan_3.32.orig.tar.gz.asc e8060bafc8554ceb1ebc56a54cc1a4854db96fe3 16768 libreswan_3.32-1.debian.tar.xz 9c30c34b71114141e157c3df9190274fac38b9a2 10645 libreswan_3.32-1_amd64.buildinfo Checksums-Sha256: 1d8ecc44064f1f8d09d52139224ac38d8040c15ab3324075111d196b46078bb8 2028 libreswan_3.32-1.dsc 236b57fee8f562302c54f2b16d8a839a9039fcb5893668e61b398ec6b179432e 4141631 libreswan_3.32.orig.tar.gz 6ae46fa0ef215ea70828cf6ffe348c686f620201ec4277d2d91586d9d7fb854c 858 libreswan_3.32.orig.tar.gz.asc 6d86cc22d87a5095b911f2dc293bbcd95a0a0845f46f3900cfd4c6986140e8aa 16768 libreswan_3.32-1.debian.tar.xz ed7c7089b5ff04cbceea8de77f186aa7454960968802ec93806b8c822c07a21c 10645 libreswan_3.32-1_amd64.buildinfo Files: 3feda47abbdccbecd7482632c1dcc1ec 2028 net optional libreswan_3.32-1.dsc 754519242e69e4ac516b0e172a127d9b 4141631 net optional libreswan_3.32.orig.tar.gz f23a5a569a4af429c7c87289a88190d0 858 net optional libreswan_3.32.orig.tar.gz.asc 6a2cd8ec148421bb9e9da95124187309 16768 net optional
Bug#961302: sane-backends 1.0.30 released with security fixes
Source: sane-backends
Version: 1.0.29-1~experimental4
Severity: grave
Tags: security upstream
Justification: user security hole
The Sane team released a new version of sane-backends a few days ago, fixing
about 5 or 6 CVEs. From [their announcement][1]:
,
| Kevin Backhouse of the [GitHub Security Lab team][1] has discovered
| several issues in the epson2, epsonds and magicolor backends that could
| be exploited by a malicious network device. All three backends are
| enabled by default. Moreover, all enable automatic discovery of network
| devices. The issues can be used to crash SANE frontends at start up or
| when starting a scan as well as corrupt memory leading to a possibility
| of remote code execution.
`
[1]: https://alioth-lists.debian.net/pipermail/sane-announce/2020/41.html
Please, upload a new version of the package as soon as possible.
Thanks,
Rogério Brito.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (200, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.0-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.utf-8, LC_CTYPE=pt_BR.utf-8 (charmap=UTF-8),
LANGUAGE=en_US.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
Bug#951722: autopkgtest suite flaky on arm64
I'm convinced that applying such hacks are a bad practice and should be avoided. I also have to add, that my motivation to further look into this has now basically dropped to zero. signature.asc Description: OpenPGP digital signature
Bug#951722: autopkgtest suite flaky on arm64
On Fri, May 22, 2020 at 11:51:07PM +0200, Michael Biebl wrote: > > I will upload a new upstream version to sid containing the workaround > > for the test failures. I will leave this bug open, but will reduce the > > severity to 'normal'. In a subsequent upload, I will apply a patch to > > implement sd_notify and will resolve the bug. Please feel free to send > > a patch if you don't want to wait however long it'll take for me to get > > around to putting one together. > > Please don't apply this hack. If you don't want to fix this properly to > get a (newer) version into testing, please just disable the test for the > time being. If we don't test it, it can't be broken, right? > It's great that the autopkgtest suite unconvered a real issue. > Let's not mutilate the test suite. I think the test suite with the workaround in place has more value than the suite with this test completely disabled. If the service never becomes available, the test with the workaround will still detect the situation, which is exactly what it's there for. noah
Bug#951722: autopkgtest suite flaky on arm64
Am 22.05.20 um 07:29 schrieb Noah Meyerhans: > On Sun, May 10, 2020 at 11:06:26PM +0200, Michael Biebl wrote: >>> +echo "Waiting for the service to be available" >>> +c=0 >>> +while ! nc -z -U /var/run/dovecot/auth-userdb; do >>> + c=$(($c+1)) >>> + sleep 2 >>> + if [ $c -gt 30 ]; then >>> + echo "Timed out waiting for the service to be available" >&2 >>> + exit 1 >>> + fi >>> +done >> >> Looping until the service is ready appears to be a workaround/hack at >> best imho. > > I agree, however... > >> The dovecot service should only signal its readiness when the >> communication sockets are ready yet to accept connections. I.e. this >> autopkgtest appears to point at a real issue that should be fixed properly. > > I do not believe that this is an RC issue. In order to address the > stale upstream version and pending security updates in sid, and allow > the package to again enter bullseye, I propose the following: That's a policy determined by the release manager/ maintainers of debci. The recommended that I should file such issues with RC severity. If you don't agree with that policy, you should probably contact them directly. > I will upload a new upstream version to sid containing the workaround > for the test failures. I will leave this bug open, but will reduce the > severity to 'normal'. In a subsequent upload, I will apply a patch to > implement sd_notify and will resolve the bug. Please feel free to send > a patch if you don't want to wait however long it'll take for me to get > around to putting one together. Please don't apply this hack. If you don't want to fix this properly to get a (newer) version into testing, please just disable the test for the time being. It's great that the autopkgtest suite unconvered a real issue. Let's not mutilate the test suite. > Dovecot has been essentially unmaintained in Debian since August 2019, > and there's quite a backlog of work to do. I'm going to work on getting > it back into shape, but it will be a little while before it's where it > should be. It won't happen all at once.> > noah > The patch to add sd_notify is rather trivial. Problem is, that dovecot unhelpfully clears the full environment. In src/master/main.c, sd_notify() should be called around/after main_init(). Unfortunately, at this point master_service_env_clean() has been called, clearing the process environment, including NOTIFY_SOCKET, which is passed from systemd to dovecot and is needed to make sd_notify work. I haven't found a way how to instruct dovecot not to clear the NOTIFY_SOCKET env var. Regards, Michael signature.asc Description: OpenPGP digital signature
Bug#961298: jodd: CVE-2018-21234: Potential vulnerability in JSON deserialization
Source: jodd Version: 3.8.6-1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/oblac/jodd/issues/628 Hi, The following vulnerability was published for jodd. I'm filling it as RC severity since altough one might dispute the severity for the issue itself, it looks that in Debian there was ever only one upload of jodd, there are no reverse (build) dependencies neither. Is the package acutally of some use or planned use? CVE-2018-21234[0]: | Jodd before 5.0.4 performs Deserialization of Untrusted JSON Data when | setClassMetadataName is set. 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-2018-21234 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21234 [1] https://github.com/oblac/jodd/issues/628 Regards, Salvatore
Bug#959545: libmateweather: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Control: forwarded -1 https://github.com/mate-desktop/libmateweather/issues/76 Hi, On So 03 Mai 2020 14:55:57 CEST, Lucas Nussbaum wrote: Source: libmateweather Version: 1.24.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200501 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[2]: Entering directory '/<>/data' xmllint --valid --noout ../data/Locations.xml.in ./check-timezones.sh ./Locations.xml.in Invalid timezones in ./Locations.xml.in: America/Godthab make[2]: *** [Makefile:637: check] Error 1 make[2]: Leaving directory '/<>/data' make[1]: *** [Makefile:490: check-recursive] Error 1 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/05/01/libmateweather_1.24.0-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. I have forwarded the above upstream. https://github.com/mate-desktop/libmateweather/issues/76 Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgp8B4g2kfP0R.pgp Description: Digitale PGP-Signatur
Processed: Remove pspp from postgres bug 924937
Processing commands for cont...@bugs.debian.org: > affects 924937 - pspp Bug #924937 [ftp.debian.org] libpq5: OpenSSL license contamination of GPL reverse-dependencies Removed indication that 924937 affects pspp > thanks Stopping processing here. Please contact me if you need assistance. -- 924937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936336: coz-profiler: Python2 removal in sid/bullseye
I pushed some changes to the package repository to solve the bug when it was opened (should be rebased onto the latest upstream release now). Unfortunately I do not have upload privileges and couldn't find anybody that would keep uploading them for coz.
Processed: Re: Bug#961230: guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000.
Processing control commands: > clone -1 -2 Bug #961230 [src:guile-2.2] guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000. Bug 961230 cloned as bug 961295 > reassign -2 src:guile-2.0 Bug #961295 [src:guile-2.2] guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000. Bug reassigned from package 'src:guile-2.2' to 'src:guile-2.0'. No longer marked as found in versions guile-2.2/2.2.7+1-5. Ignoring request to alter fixed versions of bug #961295 to the same values previously set > retitle -2 guile-2.0 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority > expects min version < 1000 Bug #961295 [src:guile-2.0] guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000. Changed Bug title to 'guile-2.0 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000' from 'guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000.'. > tags -2 bullseye sid Bug #961295 [src:guile-2.0] guile-2.0 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000 Added tag(s) sid and bullseye. -- 961230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961230 961295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961230: guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000.
Control: clone -1 -2
Control: reassign -2 src:guile-2.0
Control: retitle -2 guile-2.0 FTBFS with make-dfsg/4.3-1: ERROR: alternatives
priority expects min version < 1000
Control: tags -2 bullseye sid
On Fri, May 22, 2020 at 02:41:05PM +0200, Helmut Grohne wrote:
> Control: clone -1 -2
> Control: reassign -2 src:guile-3.0
>
> On Thu, May 21, 2020 at 07:13:27PM +0200, Helmut Grohne wrote:
> > While bootstrap testing unstable, I noticed that guile-2.2 fails to
> > build from source (natively). A build now ends quicky:
> >
> > | dpkg-buildpackage: info: source package guile-2.2
> > | dpkg-buildpackage: info: source version 2.2.7+1-5
> > | dpkg-buildpackage: info: source distribution unstable
> > | dpkg-buildpackage: info: source changed by Rob Browning
> >
> > | dpkg-source --before-build .
> > | dpkg-buildpackage: info: host architecture amd64
> > | fakeroot debian/rules clean
> > | /bin/bash: ${\#x}: bad substitution
> > | debian/rules:70: *** ERROR: alternatives priority expects min version <
> > 1000. Stop.
> > | dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned
> > exit status 2
> >
> > This only happens since make-dfsg/4.3-1, but I think the bug here
> > ultimately is with guile-2.2. The relevant code from debian/rules is:
> >
> > | ifneq (ok,$(shell x='$(deb_src_min_ver)'; [ "$${\#x}" -lt 4 ] && echo
> > ok;))
> > | $(error ERROR: alternatives priority expects min version < 1000)
> > | endif
> >
> > It is surprising that this didn't fail with earlier versions of make.
> > The shell substitution is clearly wrong. It is unclear what it is
> > supposed to achieve. In any case, deleting these lines makes the build
> > proceed.
>
> guile-3.0 also has this exact same bug.
So does guile-2.0:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/guile-2.0.html
> Helmut
cu
Adrian
Processed: retitle 961280 to guile-3.0 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000
Processing commands for cont...@bugs.debian.org: > retitle 961280 guile-3.0 FTBFS with make-dfsg/4.3-1: ERROR: alternatives > priority expects min version < 1000 Bug #961280 [src:guile-3.0] guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000. Changed Bug title to 'guile-3.0 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000' from 'guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000.'. > thanks Stopping processing here. Please contact me if you need assistance. -- 961280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959625: caml-crush: FTBFS: SP line 7: Not found a value in env for: session
Hello, I've released a new version of the package that addresses the issue with coccinelle, I've then attempted to push the new package on ftpmaster-anon as sources only. Let me know if this was the right process. Thanks! Thomas Calderon On Sun, 3 May 2020, 14:12 Lucas Nussbaum, wrote: > Source: caml-crush > Version: 1.0.8-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200501 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 > '/<>/build-SERVER/src/bindings-pkcs11' > > camlidl -header ../../../src/bindings-pkcs11/pkcs11.idl > > cat ../../../src/bindings-pkcs11/pkcs11_stubs.c | sed -e > 's/Begin_roots_block(\(.*\)).*/Begin_roots_block(\1);/g' | sed -e > 's/Begin_root(\(.*\)).*/Begin_root(\1);/g' | sed -e > 's/End_roots(\(.*\)).*/End_roots(\1);/g' > ./tmp > > mv ./tmp ../../../src/bindings-pkcs11/pkcs11_stubs.c > > #Sed to patch (GetSlotList/GetMechList/FindObjects/GetObjectSize) > > sed -i "s/* int/\* nativeint/g" ../../../src/bindings-pkcs11/pkcs11.mli > > sed -i "s/* int/\* nativeint/g" ../../../src/bindings-pkcs11/pkcs11.ml > > spatch --no-show-diff --in-place --sp-file > ../../../src/bindings-pkcs11/pkcs11_stubs.cocci > ../../../src/bindings-pkcs11/pkcs11_stubs.c > > init_defs_builtins: /usr/bin/../lib/coccinelle/standard.h > > warning: line 96: _ctxs, previously declared as a metavariable, is used > as an identifier > > warning: line 97: _ctx, previously declared as a metavariable, is used > as an identifier > > warning: line 97: _ctxs, previously declared as a metavariable, is used > as an identifier > > warning: line 98: _c1, previously declared as a metavariable, is used as > an identifier > > warning: line 99: _c2, previously declared as a metavariable, is used as > an identifier > > warning: line 104: _v3, previously declared as a metavariable, is used > as an identifier > > warning: line 104: _c2, previously declared as a metavariable, is used > as an identifier > > warning: line 104: _ctx, previously declared as a metavariable, is used > as an identifier > > warning: line 105: _c2, previously declared as a metavariable, is used > as an identifier > > warning: line 105: _v3, previously declared as a metavariable, is used > as an identifier > > warning: line 802: _ctxs, previously declared as a metavariable, is used > as an identifier > > warning: line 821: _ctxs, previously declared as a metavariable, is used > as an identifier > > HANDLING: ../../../src/bindings-pkcs11/pkcs11_stubs.c > > #Sed because spatch is not able to preprocess > > sed -i 's/^_CAMLIDL_EXTERN_C/extern/g' > ../../../src/bindings-pkcs11/pkcs11.h > > #Sed to change the structure packing pragma in WIN32 mode: CamlIDL fixes > it to 8 while > > #PKCS11 header fixes it to 1 => this can create binary interoperability > issues > > sed -i 's/push,8/push,1\/* Replaced for PKCS11 compatibiliy *\//g' > ../../../src/bindings-pkcs11/pkcs11.h > > spatch --no-show-diff --in-place --sp-file > ../../../src/bindings-pkcs11/pkcs11.cocci > ../../../src/bindings-pkcs11/pkcs11.h > > init_defs_builtins: /usr/bin/../lib/coccinelle/standard.h > > HANDLING: ../../../src/bindings-pkcs11/pkcs11.h > > SP line 7: Not found a value in env for: session > > make[3]: *** [Makefile:37: idl] Error 255 > > The full build log is available from: >http://qa-logs.debian.net/2020/05/01/caml-crush_1.0.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. >
Bug#932951: marked as done (pspp build-depends on cruft package.)
Your message dated Fri, 22 May 2020 19:00:10 + with message-id and subject line Bug#932951: fixed in pspp 1.2.0-4 has caused the Debian Bug report #932951, regarding pspp build-depends on cruft package. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 932951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pspp Version: 3.5.2-1 Tags: bullseye, sid, patch Severity: serious pspp build-depends on texlive-generic-reccomended which is no longer built by the texlive-base source package. Please build-depend on texlive-plain-generic instead. --- End Message --- --- Begin Message --- Source: pspp Source-Version: 1.2.0-4 Done: Friedrich Beckmann We believe that the bug you reported is fixed in the latest version of pspp, 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 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Friedrich Beckmann (supplier of updated pspp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 22 May 2020 14:09:07 +0200 Source: pspp Binary: pspp pspp-dbgsym Architecture: source amd64 Version: 1.2.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Friedrich Beckmann Description: pspp - Statistical analysis tool Closes: 923417 932951 Changes: pspp (1.2.0-4) unstable; urgency=medium . [ Andreas Tille ] * Do not Build-Depend texlive-generic-recommended Closes: #932951 * d/rules: remove old boilerplate * hardening=+all * sys-file-writer: Remove assertions based on file position. Fixes: CVE-2019-9211 Closes: #923417 . [ Friedrich Beckmann ] * d/upstream/metadata - added bug link * removed postgresql due to license issue: #924937 * d/copyright: added GFDL and CC-BY-SA license Checksums-Sha1: 8c051b405c654c8129cf8a8c34044d01c794e138 2276 pspp_1.2.0-4.dsc f679a5da2af7cd296d806da0b5f10d47889bc799 36396 pspp_1.2.0-4.debian.tar.xz 62ef3bea09eb6b6b031f2ad12c954b49550868e0 2995936 pspp-dbgsym_1.2.0-4_amd64.deb b52df3beb2a646f24c344c9f37475e55a3ea18e7 17012 pspp_1.2.0-4_amd64.buildinfo 1d6ef47f993476bd300d169c9b4a4e7c523b237c 3816592 pspp_1.2.0-4_amd64.deb Checksums-Sha256: 5cafe3a1b090752a0488804bb1f8e9d1f7a774fb549930bb7b03e49c77a605cc 2276 pspp_1.2.0-4.dsc 13c7b33693303d587ef73a2cf87eb008df847cc4600f8308344a4e71d2fe993b 36396 pspp_1.2.0-4.debian.tar.xz 609a9f1b7b31db495668d55945e1520f516537bd6d57e205855909bec6e495ca 2995936 pspp-dbgsym_1.2.0-4_amd64.deb 3005d5d98d19933a0bd00ddad695f668f3b10a71c1708695acf4c4480e1a1b5e 17012 pspp_1.2.0-4_amd64.buildinfo 5bd7457528f77331890b0a3d10bd7016531ede457a52f7a36a44997a9aa861a6 3816592 pspp_1.2.0-4_amd64.deb Files: 4c212455940cc4689671f08a55142849 2276 math optional pspp_1.2.0-4.dsc 50c51f080fc499d35dc4b8d3cd8e5f4b 36396 math optional pspp_1.2.0-4.debian.tar.xz a1d07d6a32110d22338736224f057395 2995936 debug optional pspp-dbgsym_1.2.0-4_amd64.deb f10eddf8567d01a3bb5393d1392ea0a2 17012 math optional pspp_1.2.0-4_amd64.buildinfo 472b5e8bb8403741d411e72d9cf703ff 3816592 math optional pspp_1.2.0-4_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAl7HxGgACgkQYS7xYT4F D1QfEg/7B7vsLZpJuXFLXR3fzRC4G/mwFE7fvsWriSRL82hUU7vazXRuPYBoubPI 5CObVpxeuuqr7MI8qszftBgWDU2xIXjQYGKQhaxq+B3BlPVGoiUi6KONQy7lBQEa Ck/uBGJqEP9UN5JOk0JknAelYpXz+/+AEYBzhubUJeRg5JOpqlIY7xla8XKcSuwl xN2qyGYffBiE3u3LqaC38qNcKDr4KZhUPdU0rN1WdCB/4HKtsD9hXdn9OUH7iKCq jV7dTivvYT9NuxjP0hbfX9O+h+1Hx74p0k5DSlolYGiDmYvEevQYNJHz+jlSRCgs LF+LEkqCthATXeGa3kiL9eU73bdjJ/NgOb5PIg5CnQMtiJ5xbpwsOppij9CupcBv QxS8yMQxiys7qpGSlTlkmR0Azelqo3MHXkQbbDAg9BBlMFfw4I6NFdLrHiXk1Zed AuC9qr/BjOzuEcTGK6mcPVU2V4rTpAexhYCE3HibrVMx4kbTLL8SYa7gZkICLZod wIv2hb4y4o0FRTCsd933WNLhTS9tqLTjj1Gpqx5xGomiaGxII1QaZJU5P5Ag2PfC CHXe4g6SS5B23hE2/iXXh6Mgc7xQ5OUxuB5M+ekiB6GyR6igxWRFWYkPM68BESfv sZNfiUAN5xuH7BlvbsY/8WDOZZRV7/AcUwFT3nSTmc9l8u6KUmQ= =WEYl -END PGP SIGNATURE End Message ---
Processed: oggvideotools: diff for NMU version 0.9.1-5.1
Processing control commands: > tags 959814 + patch Bug #959814 [src:oggvideotools] oggvideotools: Test dependency on pysycache-i18n that will likely be removed Added tag(s) patch. > tags 959814 + pending Bug #959814 [src:oggvideotools] oggvideotools: Test dependency on pysycache-i18n that will likely be removed Added tag(s) pending. -- 959814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959814: oggvideotools: diff for NMU version 0.9.1-5.1
Control: tags 959814 + patch Control: tags 959814 + pending Dear maintainer, I've prepared an NMU for oggvideotools (versioned as 0.9.1-5.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru oggvideotools-0.9.1/debian/changelog oggvideotools-0.9.1/debian/changelog --- oggvideotools-0.9.1/debian/changelog 2019-04-05 10:46:07.0 +0300 +++ oggvideotools-0.9.1/debian/changelog 2020-05-22 21:49:26.0 +0300 @@ -1,3 +1,11 @@ +oggvideotools (0.9.1-5.1) unstable; urgency=medium + + * Non-maintainer upload. + * Don't run test-oggjoin that depends on pysycache-i18n +that will likely be removed. (Closes: #959814) + + -- Adrian Bunk Fri, 22 May 2020 21:49:26 +0300 + oggvideotools (0.9.1-5) unstable; urgency=medium * Team upload. diff -Nru oggvideotools-0.9.1/debian/control oggvideotools-0.9.1/debian/control --- oggvideotools-0.9.1/debian/control 2019-04-05 10:46:07.0 +0300 +++ oggvideotools-0.9.1/debian/control 2020-05-22 21:49:26.0 +0300 @@ -16,7 +16,6 @@ libgd-dev, libboost-dev, debconf, - pysycache-i18n, python3-mecavideo, Standards-Version: 4.3.0 Vcs-Git: https://salsa.debian.org/multimedia-team/oggvideotools.git diff -Nru oggvideotools-0.9.1/debian/rules oggvideotools-0.9.1/debian/rules --- oggvideotools-0.9.1/debian/rules 2019-04-05 10:46:07.0 +0300 +++ oggvideotools-0.9.1/debian/rules 2020-05-22 21:49:26.0 +0300 @@ -9,7 +9,7 @@ # Run our test suite until the upstream source get one override_dh_auto_test: dh_auto_test - TESTBINDIR=`pwd`/obj-*/src/binaries/ ./debian/tests/test-oggjoin + #TESTBINDIR=`pwd`/obj-*/src/binaries/ ./debian/tests/test-oggjoin TESTBINDIR=`pwd`/obj-*/src/binaries/ ./debian/tests/test-oggcut debian-copyright: diff -Nru oggvideotools-0.9.1/debian/tests/control oggvideotools-0.9.1/debian/tests/control --- oggvideotools-0.9.1/debian/tests/control 2019-04-05 10:46:07.0 +0300 +++ oggvideotools-0.9.1/debian/tests/control 2020-05-22 21:49:26.0 +0300 @@ -1,4 +1,4 @@ -Tests: test-oggjoin test-oggcut -Depends: @, debconf, pysycache-i18n, python3-mecavideo, valgrind +Tests: test-oggcut +Depends: @, debconf, python3-mecavideo, valgrind Restrictions: allow-stderr
Bug#955689: marked as done (libcatmandu-filestore-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 255)
Your message dated Fri, 22 May 2020 18:48:31 +
with message-id
and subject line Bug#955689: fixed in libcatmandu-filestore-perl 1.16-1
has caused the Debian Bug report #955689,
regarding libcatmandu-filestore-perl: FTBFS: dh_auto_test: error: perl Build
test --verbose 1 returned exit code 255
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.)
--
955689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcatmandu-filestore-perl
Version: 1.13-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package libcatmandu-filestore-perl
> dpkg-buildpackage: info: source version 1.13-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by gregor herrmann
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean
>dh_clean
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building libcatmandu-filestore-perl using existing
> ./libcatmandu-filestore-perl_1.13.orig.tar.gz
> dpkg-source: info: building libcatmandu-filestore-perl in
> libcatmandu-filestore-perl_1.13-2.debian.tar.xz
> dpkg-source: info: building libcatmandu-filestore-perl in
> libcatmandu-filestore-perl_1.13-2.dsc
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_auto_configure
> perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config
> "ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'Catmandu-FileStore' version '1.13'
>dh_auto_build
> perl Build
> Building Catmandu-FileStore
>dh_auto_test
> perl Build test --verbose 1
>
> # Failed test 'found the correct file'
> # at t/Catmandu-Cmd-stream.t line 49.
> # Looks like you failed 1 test of 6.
> t/Catmandu-Cmd-stream.t ...
> ok 1 - use Catmandu::Cmd::stream;
> ok 2 - require Catmandu::Cmd::stream;
> # download
> ok 3 - threw no exceptions
> # upload
> ok 4
> ok 5 - threw no exceptions
> not ok 6 - found the correct file
> 1..6
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/6 subtests
> t/Catmandu-DirectoryIndex-Map.t ...
> ok 1 - use Catmandu::DirectoryIndex::Map;
> ok 2 - require Catmandu::DirectoryIndex::Map;
> ok 3 - require Catmandu::Store::Hash;
> ok 4 - bag must be Catmandu::Bag (1)
> ok 5 - bag must be Catmandu::Bag (2)
> ok 6
> ok 7
> ok 8
> ok 9
> ok 10
> ok 11
> ok 12
> ok 13
> ok 14
> ok 15
> ok 16
> ok 17
> 1..17
> ok
> need natural number
>
> Trace begun at /<>/blib/lib/Catmandu/DirectoryIndex/Number.pm
> line 29
> Catmandu::DirectoryIndex::Number::format_id('Catmandu::DirectoryIndex::Number=HASH(0x560bc3c3cc68)',
> 2) called at
> /<>/blib/lib/Catmandu/DirectoryIndex/Number.pm line 73
> Catmandu::DirectoryIndex::Number::add('Catmandu::DirectoryIndex::Number=HASH(0x560bc3c3cc68)',
> 2) called at t/Catmandu-DirectoryIndex-Number.t line 95
> # Tests were run but no plan was declared and done_testing() was not seen.
> # Looks like your test exited with 2 just after 10.
> t/Catmandu-DirectoryIndex-Number.t
> ok 1 - use Catmandu::DirectoryIndex::Number;
> ok 2 - require Catmandu::DirectoryIndex::Number;
> ok 3 - keysize must be a multiple of 3
> ok 4
> ok 5 - ids must be natural numbers
> ok 6 - ids must be bigger or equal to zero
> ok 7 - ids must fit into configured keysize
> ok 8
> ok 9 - get returns mapping
> ok 10 - number are converted to left padded strings
> Dubious, test returned 2 (wstat 512, 0x200)
> All 10 subtests passed
>
> # Failed test 'use Catmandu::DirectoryIndex::UUID;'
> # at t/Catmandu-DirectoryIndex-UUID.t line 15.
> # Tried to use 'Catmandu::DirectoryIndex::UUID'.
> # Error: Can't locate Data/UUID.pm in @INC (you may need to install the
> Data::UUID module) (@INC contains: /<>/blib/lib
> /<>/blib/arch /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0
> /usr/lib/x86_64-linux-gnu/perl5/5.30
Bug#950404: Bug#953181: src:ndpi: fails to migrate to testing for too long
On Thu, Mar 05, 2020 at 04:39:44PM +0100, Paul Gevers wrote: >... > 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. >... The 32bit problem has been fixed upstream. Dimitri, what is the status of your big endian porting for s390x[1]? cu Adrian [1] https://github.com/ntop/nDPI/issues/843
Processed: reopening 516394
Processing commands for cont...@bugs.debian.org:
> reopen 516394
Bug #516394 {Done: Debian FTP Masters }
[djbdns] [security]: Rapid DNS Poisoning in dnscache
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1:1.05-8+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
516394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#960963: marked as done (dovecot: CVE-2020-10957 CVE-2020-10958 CVE-2020-10967)
Your message dated Fri, 22 May 2020 17:02:28 + with message-id and subject line Bug#960963: fixed in dovecot 1:2.3.4.1-5+deb10u2 has caused the Debian Bug report #960963, regarding dovecot: CVE-2020-10957 CVE-2020-10958 CVE-2020-10967 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.) -- 960963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dovecot Version: 1:2.3.7.2-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 1:2.3.4.1-5+deb10u1 Control: found -1 1:2.3.2-1 Hi, The following vulnerabilities were published for dovecot. CVE-2020-10957[0]: | In Dovecot before 2.3.10.1, unauthenticated sending of malformed | parameters to a NOOP command causes a NULL Pointer Dereference and | crash in submission-login, submission, or lmtp. CVE-2020-10958[1]: | In Dovecot before 2.3.10.1, a crafted SMTP/LMTP message triggers an | unauthenticated use-after-free bug in submission-login, submission, or | lmtp, and can lead to a crash under circumstances involving many | newlines after a command. CVE-2020-10967[2]: | In Dovecot before 2.3.10.1, remote unauthenticated attackers can crash | the lmtp or submission process by sending mail with an empty | localpart. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-10957 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10957 [1] https://security-tracker.debian.org/tracker/CVE-2020-10958 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10958 [2] https://security-tracker.debian.org/tracker/CVE-2020-10967 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10967 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: dovecot Source-Version: 1:2.3.4.1-5+deb10u2 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of dovecot, 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. Salvatore Bonaccorso (supplier of updated dovecot 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: Mon, 18 May 2020 22:09:08 +0200 Source: dovecot Architecture: source Version: 1:2.3.4.1-5+deb10u2 Distribution: buster-security Urgency: high Maintainer: Dovecot Maintainers Changed-By: Salvatore Bonaccorso Closes: 960963 Changes: dovecot (1:2.3.4.1-5+deb10u2) buster-security; urgency=high . * Non-maintainer upload by the Security Team. * Apply upstream fixes for CVE-2020-10957, CVE-2020-10958 and CVE-2020-10967 (Closes: #960963) - lib-smtp: smtp-server-cmd-vrfy - Restructure parameter parsing. - lib-smtp: smtp-syntax - Do not allow NULL return parameters for smtp_string_parse(). - lib-smtp: smtp-syntax - Do not allow NULL return parameters for smtp_xtext_parse(). - lib-smtp: syntax: Fix smtp_ehlo_line_parse() to also record the last parameter. - lib-smtp: smtp-syntax - Do not allow NULL return parameters for smtp_ehlo_line_parse(). - lib-smtp: smtp-syntax - Return 0 for smtp_string_parse() with empty input. - lib-smtp: Add tests for smtp_string_parse() and smtp_string_write(). - lib-smtp: test-smtp-server-errors - Add tests for VRFY and NOOP commands with invalid parameters. - lib-smtp: server: command: Move core of smtp_server_command_submit_reply() into a separate function. - lib-smtp: smtp-server-command - Assign cmd->reg immediately. - lib-smtp: smtp-server-command - Guarantee that non-destroy hooks aren't called for an ended command. - lib-smtp: smtp-server-command - Perform initial command execution in separate function. - lib-smtp: smtp-server-connection - Hold a command reference while executing a command. - lib-smtp: test-smtp-server-errors - Add tests for
Bug#945171: marked as done (bind9: CVE-2019-6477: TCP-pipelined queries can bypass tcp-clients limit)
Your message dated Fri, 22 May 2020 17:02:10 + with message-id and subject line Bug#945171: fixed in bind9 1:9.11.5.P4+dfsg-5.1+deb10u1 has caused the Debian Bug report #945171, regarding bind9: CVE-2019-6477: TCP-pipelined queries can bypass tcp-clients limit 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.) -- 945171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bind9 Version: 1:9.11.5.P4+dfsg-5.1 Severity: grave Tags: security upstream Control: found -1 1:9.15.5-1 Hi, The following vulnerability was published for bind9. CVE-2019-6477[0]: TCP-pipelined queries can bypass tcp-clients limit If I undrestand this correctly then versions not listed in the advisory, but those patched for CVE-2018-5743 are affected by the issue. 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-2019-6477 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6477 [1] https://kb.isc.org/docs/cve-2019-6477 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: bind9 Source-Version: 1:9.11.5.P4+dfsg-5.1+deb10u1 Done: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= We believe that the bug you reported is fixed in the latest version of bind9, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý (supplier of updated bind9 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: Mon, 18 May 2020 10:02:41 +0200 Source: bind9 Binary: bind9 bind9-dbgsym bind9-doc bind9-host bind9-host-dbgsym bind9utils bind9utils-dbgsym dnsutils dnsutils-dbgsym libbind-dev libbind-export-dev libbind9-161 libbind9-161-dbgsym libdns-export1104 libdns-export1104-dbgsym libdns-export1104-udeb libdns1104 libdns1104-dbgsym libirs-export161 libirs-export161-dbgsym libirs-export161-udeb libirs161 libirs161-dbgsym libisc-export1100 libisc-export1100-dbgsym libisc-export1100-udeb libisc1100 libisc1100-dbgsym libisccc-export161 libisccc-export161-dbgsym libisccc-export161-udeb libisccc161 libisccc161-dbgsym libisccfg-export163 libisccfg-export163-dbgsym libisccfg-export163-udeb libisccfg163 libisccfg163-dbgsym liblwres161 liblwres161-dbgsym Architecture: source amd64 all Version: 1:9.11.5.P4+dfsg-5.1+deb10u1 Distribution: buster-security Urgency: high Maintainer: Debian DNS Team Changed-By: Ondřej Surý Description: bind9 - Internet Domain Name Server bind9-doc - Documentation for BIND bind9-host - DNS lookup utility (deprecated) bind9utils - Utilities for BIND dnsutils - Clients provided with BIND libbind-dev - Static Libraries and Headers used by BIND libbind-export-dev - Development files for the exported BIND libraries libbind9-161 - BIND9 Shared Library used by BIND libdns-export1104 - Exported DNS Shared Library libdns-export1104-udeb - Exported DNS library for debian-installer (udeb) libdns1104 - DNS Shared Library used by BIND libirs-export161 - Exported IRS Shared Library libirs-export161-udeb - Exported IRS library for debian-installer (udeb) libirs161 - DNS Shared Library used by BIND libisc-export1100 - Exported ISC Shared Library libisc-export1100-udeb - Exported ISC library for debian-installer (udeb) libisc1100 - ISC Shared Library used by BIND libisccc-export161 - Command Channel Library used by BIND libisccc-export161-udeb - Command Channel Library used by BIND (udeb) libisccc161 - Command Channel Library used by BIND libisccfg-export163 - Exported ISC CFG Shared Library libisccfg-export163-udeb - Exported ISC CFG library for debian-installer (udeb) libisccfg163 - Config File Handling Library used by BIND liblwres161 - Lightweight Resolver Library used by BIND Closes: 945171 Changes: bind9 (1:9.11.5.P4+dfsg-5.1+deb10u1) buster-security; urgency=high . * [CVE-2019-6477]: TCP-pipelined queries can bypass tcp-clients limit.
Processed: Re: Bug#959545: libmateweather: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Processing control commands: > forwarded -1 https://github.com/mate-desktop/libmateweather/issues/76 Bug #959545 [src:libmateweather] libmateweather: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Set Bug forwarded-to-address to 'https://github.com/mate-desktop/libmateweather/issues/76'. -- 959545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream
On Fri, 22 May 2020 09:58:12 +0200, intrigeri wrote: > So, once aptitude >= 0.8.13-1 has migrated to testing, we'll need to > ask (presumably the release team) for libparse-debianchangelog-perl to > lose its "key package" status, so the autoremoval machinery can remove > it from testing due to this very RC bug. Unless we go directly for an RM;RoM bug, then it will be removed from testing when it's gone from unstable. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#961286: libmagplus3v5: Depends on removed ttf-dejavu-* packages
Package: libmagplus3v5 Severity: grave Version: 4.3.3-1 Tags: bullseye sid X-Debbugs-CC: mckins...@debian.org Dear Debian magics++ maintainer, As in https://bugs.debian.org/872809 , The latest upload of fonts- dejavu removed transition packages: * ttf-dejavu * ttf-dejavu-core * ttf-dejavu-extra Your library package libmagplus3v5 still depends on the latter 2 packages. Please use the real package names (fonts-dejavu-core, fonts-dejavu- extra) and verify that your package did not use hardcoded font paths since the font path has changed with the transition from ttf-dejavu* to fonts-dejavu*. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#960584: src:theme-d-gnome: fails to migrate to testing for too long: self-build arch/all binaries
Control: tags -1 + pending X-Debbugs-CC: elb...@debian.org 在 2020-05-22星期五的 23:53 +0800，Boyuan Yang写道： > Control: reopen -1 > Control: found -1 0.9.0-1 > Control: tags -1 +bullseye +sid -pending > Control: forcemerge 960584 961285 > X-Debbugs-CC: elb...@debian.org > > This bug is actually not fixed. Reopening and tagging accordingly. > Let > me know if you have any questions or need any help. Well... I didn't notice an existing deferred NMU. With the NMU it seems that the problem can be solved soon. Currently the testing autoremoval will take place on June 12; we should have enough time to get the fix into Testing before the removal actually takes place. Sorry for the noise. -- Regards, Boyuan Yang
Processed: Re: Bug#960584: src:theme-d-gnome: fails to migrate to testing for too long: self-build arch/all binaries
Processing control commands: > tags -1 + pending Bug #960584 [src:theme-d-gnome] src:theme-d-gnome: fails to migrate to testing for too long: self-build arch/all binaries Bug #961285 [src:theme-d-gnome] theme-d-gnome: Failed to migrate to testing for too long Added tag(s) pending. Added tag(s) pending. -- 960584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960584 961285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#960584: src:theme-d-gnome: fails to migrate to testing for too long: self-build arch/all binaries
Processing control commands:
> reopen -1
Bug #960584 {Done: Paul Gevers } [src:theme-d-gnome]
src:theme-d-gnome: fails to migrate to testing for too long: self-build
arch/all binaries
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions theme-d-gnome/0.9.0-1.
> found -1 0.9.0-1
Bug #960584 [src:theme-d-gnome] src:theme-d-gnome: fails to migrate to testing
for too long: self-build arch/all binaries
Marked as found in versions theme-d-gnome/0.9.0-1.
> tags -1 +bullseye +sid -pending
Bug #960584 [src:theme-d-gnome] src:theme-d-gnome: fails to migrate to testing
for too long: self-build arch/all binaries
Ignoring request to alter tags of bug #960584 to the same tags previously set
Bug #960584 [src:theme-d-gnome] src:theme-d-gnome: fails to migrate to testing
for too long: self-build arch/all binaries
Ignoring request to alter tags of bug #960584 to the same tags previously set
Bug #960584 [src:theme-d-gnome] src:theme-d-gnome: fails to migrate to testing
for too long: self-build arch/all binaries
Removed tag(s) pending.
> forcemerge 960584 961285
Bug #960584 [src:theme-d-gnome] src:theme-d-gnome: fails to migrate to testing
for too long: self-build arch/all binaries
Bug #961285 [src:theme-d-gnome] theme-d-gnome: Failed to migrate to testing for
too long
Marked as found in versions theme-d-gnome/0.8.2-1.
Merged 960584 961285
--
960584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960584
961285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#960584: src:theme-d-gnome: fails to migrate to testing for too long: self-build arch/all binaries
Control: reopen -1 Control: found -1 0.9.0-1 Control: tags -1 +bullseye +sid -pending Control: forcemerge 960584 961285 X-Debbugs-CC: elb...@debian.org This bug is actually not fixed. Reopening and tagging accordingly. Let me know if you have any questions or need any help. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#961285: theme-d-gnome: Failed to migrate to testing for too long
Source: theme-d-gnome Version: 0.9.0-1 Severity: serious Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync X-Debbugs-CC: tommi.hoynalan...@iki.fi alteh...@debian.org 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. Your package src:theme-d-gnome in its current version in unstable has been trying to migrate for 68 days. 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. Currently your package only needs another source-only upload to be able tomigrate to Testing; please refer to https://wiki.debian.org/SourceOnlyUpload to see how to make a source-only upload. Let me know if you need any help in package sponsorship. Regards, Boyuan Yang [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html signature.asc Description: This is a digitally signed message part
Processed: affects 959828
Processing commands for cont...@bugs.debian.org: > affects 959828 src:e17 Bug #959828 [systemctl] systemctl: `Provides: systemd`, but doesn't provide what systemd does Added indication that 959828 affects src:e17 > thanks Stopping processing here. Please contact me if you need assistance. -- 959828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961283: libhttp-tiny-perl: Don't release with bullseye
Package: libhttp-tiny-perl Version: 0.076-1 Severity: serious Justification: maintainer libhttp-tiny-perl at this version should not be released with bullseye, since perl contains the same version.
Bug#961256: marked as done (sra-toolkit: srapath is a broken symlink)
Your message dated Fri, 22 May 2020 14:35:22 + with message-id and subject line Bug#961256: fixed in sra-sdk 2.10.6+dfsg-4 has caused the Debian Bug report #961256, regarding sra-toolkit: srapath is a broken symlink 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.) -- 961256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sra-toolkit Version: 2.10.6+dfsg-3 Severity: serious Control: affects -1 src:sra-sdk $ file /usr/bin/srapath* /usr/bin/srapath: broken symbolic link to sratools.2.10.6 /usr/bin/srapath-orig.2.10.6: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=20f0f36fab86a1389d442e83d4a4040eec1bfd92, for GNU/Linux 3.2.0, stripped $ This is also the cause of the autopkgtest failure. --- End Message --- --- Begin Message --- Source: sra-sdk Source-Version: 2.10.6+dfsg-4 Done: u...@debian.org (Aaron M. Ucko) We believe that the bug you reported is fixed in the latest version of sra-sdk, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aaron M. Ucko (supplier of updated sra-sdk 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: Fri, 22 May 2020 09:25:13 -0400 Source: sra-sdk Architecture: source Version: 2.10.6+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Aaron M. Ucko Closes: 961256 Changes: sra-sdk (2.10.6+dfsg-4) unstable; urgency=medium . * Account for new sratools setup. (Closes: #961256.) - debian/rules: Rework deversioning logic to account for sratools and *-orig.* while still keeping hardcoding to a minimum; formally supply a hardcoded but originally random standard installation ID in a new /etc/ncbi/debian.kfg. - debian/patches/use_unversioned_tools.patch (new): Have sratools look for executable names without version extensions. Checksums-Sha1: 00ec1728e9e028842fc5759795f3fcbae5e6ffa0 2228 sra-sdk_2.10.6+dfsg-4.dsc 250dc97884ba4960d865204b855e4a1862d72ed1 3843984 sra-sdk_2.10.6+dfsg-4.debian.tar.xz fb596a35442443eecb83207186914752d97acbb7 7607 sra-sdk_2.10.6+dfsg-4_source.buildinfo Checksums-Sha256: 1f1757f695a7f19ff2bc4580b004968ff03c035c6c875a90c2ad21abb5711034 2228 sra-sdk_2.10.6+dfsg-4.dsc 5109ad155488591f2d8721844b5868a629831e988cb60f63c91524d834b6b312 3843984 sra-sdk_2.10.6+dfsg-4.debian.tar.xz 7b0af056730ab654577d6b2e01c8b8c8bd62c6acb9a7039d01131d5fca30fa54 7607 sra-sdk_2.10.6+dfsg-4_source.buildinfo Files: 369b5f9ef2937199db9f33ae9875946a 2228 science optional sra-sdk_2.10.6+dfsg-4.dsc f51bc9ce85ff2a74ad43e0a6b842bee1 3843984 science optional sra-sdk_2.10.6+dfsg-4.debian.tar.xz 191e1e773d6e5e9f48e08a437610778a 7607 science optional sra-sdk_2.10.6+dfsg-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEEfDq5z9IwvTDdAJxZHnCRsfFKZKIFAl7H0x8QHHVja29AZGVi aWFuLm9yZwAKCRAecJGx8UpkooqkD/9PQ7ODe0r1Ap0dQFzObDtkUbLSkfJd3S5x M2wc6M6TaxfLmJ/yIUKpWXOHpdQmAHBblC8uhuLPPvguJSZtNJFgznwjyR8xi0Oz hFTtU5zZkCpkeQoDWPDiyO64MImvR1Rnfd3zP7ROhpwtVxYtYz71/EpWmE0jXOi6 QIlUg0I2zg5sSWY1HyHz4grHkCU+0TR37zZ0jTO1dzPu/srhVcP1BLJJn2PLaRFv kv/RWe/cw9L3uYvZ8LqDlp5W2ZvdGncNzqzSwJDIpWVajDbgqiaeqJGFaEEzvYzb 1Iok0zTfkV9X4Yvqfh0rOfDABYGsYfQ/Kk1iIziZ7WLc3I70fsu2Fybwtr/8dlBt URQqOZcBNSXZxz88MQyOs4Qf1DvPjGlau2TLLVPQ4/wGmWprKVgSLQbdoqpWdoOw o/XLAQ9vbKmmvfWsNHwbk1bdvgzojPcFA36C4H4lfpt1U03bhRdxSEr0+vlM6gX1 4t3uTMVCwo2o+OfdawVz6M75KdKmzA74bAEKis1vUTilsSECpLCAtHZxYe6SZ365 WjpC/VkmFezBGPvNnsc0VpldbejckwsfAizPExdXoVvh9cK1K8AE1xi+vyWKwPhM t9EZlTCuO1fFc4v3mVuMZGSE9XFaOoQH6xfv2OrVCcxLaCR7o7G5bdHgJICSDgB7 BAISdD0rDA== =VpTw -END PGP SIGNATURE End Message ---
Bug#961122: 1.5.0.87+dfsg1-1 is out of the way already
Hi, I don't understand why you report a bug on 1.5.0.87+dfsg1-1 on the 20th of may when testing has 1.5.0.87+dfsg1-4 since the 9th of march, and unstable had it since the 4th of march. Isn't the problem history already? JP
Processed: tagging 960361
Processing commands for cont...@bugs.debian.org: > tags 960361 + ftbfs Bug #960361 [src:chromium] src:chromium: FTBFS with re2 20200501 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 960361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961230: guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000.
Control: clone -1 -2
Control: reassign -2 src:guile-3.0
On Thu, May 21, 2020 at 07:13:27PM +0200, Helmut Grohne wrote:
> While bootstrap testing unstable, I noticed that guile-2.2 fails to
> build from source (natively). A build now ends quicky:
>
> | dpkg-buildpackage: info: source package guile-2.2
> | dpkg-buildpackage: info: source version 2.2.7+1-5
> | dpkg-buildpackage: info: source distribution unstable
> | dpkg-buildpackage: info: source changed by Rob Browning
>
> | dpkg-source --before-build .
> | dpkg-buildpackage: info: host architecture amd64
> | fakeroot debian/rules clean
> | /bin/bash: ${\#x}: bad substitution
> | debian/rules:70: *** ERROR: alternatives priority expects min version <
> 1000. Stop.
> | dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned
> exit status 2
>
> This only happens since make-dfsg/4.3-1, but I think the bug here
> ultimately is with guile-2.2. The relevant code from debian/rules is:
>
> | ifneq (ok,$(shell x='$(deb_src_min_ver)'; [ "$${\#x}" -lt 4 ] && echo ok;))
> | $(error ERROR: alternatives priority expects min version < 1000)
> | endif
>
> It is surprising that this didn't fail with earlier versions of make.
> The shell substitution is clearly wrong. It is unclear what it is
> supposed to achieve. In any case, deleting these lines makes the build
> proceed.
guile-3.0 also has this exact same bug.
Helmut
Processed: Re: guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000.
Processing control commands: > clone -1 -2 Bug #961230 [src:guile-2.2] guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000. Bug 961230 cloned as bug 961280 > reassign -2 src:guile-3.0 Bug #961280 [src:guile-2.2] guile-2.2 FTBFS with make-dfsg/4.3-1: ERROR: alternatives priority expects min version < 1000. Bug reassigned from package 'src:guile-2.2' to 'src:guile-3.0'. No longer marked as found in versions guile-2.2/2.2.7+1-5. Ignoring request to alter fixed versions of bug #961280 to the same values previously set -- 961230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961230 961280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961279: Experimental version needs to be ported to mozjs68
Package: policykit-1 Version: 0.116-2 Severity: serious Tags: experimental Hello, policykit-1 0.116 from experimental needs to be ported to mozjs68 now that mozjs60 is gone from the archive. Kind regards, Laurent Bigonville -- 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.6.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages policykit-1 depends on: ii adduser 3.118 ii dbus 1.13.14-1 ii libc62.30-8 ii libexpat12.2.9-1 ii libgcc-s1 [libgcc1] 10.1.0-2 ii libglib2.0-0 2.64.2-1 ii libmozjs-60-060.8.0-2 ii libpam-systemd [logind] 245.5-3 ii libpam0g 1.3.1-5 ii libpolkit-agent-1-0 0.116-2 ii libpolkit-gobject-1-00.116-2 ii libstdc++6 10.1.0-2 ii libsystemd0 245.5-3 policykit-1 recommends no packages. policykit-1 suggests no packages. Versions of packages policykit-1 is related to: pn elogind pn libpam-elogind ii libpam-systemd 245.5-3 ii systemd 245.5-3 -- Configuration Files: /etc/polkit-1/rules.d/40-debian-sudo.rules [Errno 13] Permission non accordée: '/etc/polkit-1/rules.d/40-debian-sudo.rules' /etc/polkit-1/rules.d/50-default.rules [Errno 13] Permission non accordée: '/etc/polkit-1/rules.d/50-default.rules' -- no debconf information
Bug#872215: sosreport: fdisk dependency needed
Control: severity -1 important On Tue, Aug 15, 2017 at 10:14:35AM +0200, andr...@fatal.se wrote: >... > quick analysis suggested you might want to add a dependency (and/or > build-dependency if you use it at build-time, eg. tests). > > Please use the backwards-compatible way of specifying the dependency > as suggested in the debian-devel-announce mail: > > fdisk | util-linux (<< 2.29.2-3~) >... Similar to #887181 this is a plugin dependency, in both cases Recommends would likely be the best solution. cu Adrian
Processed: Re: Bug#872215: sosreport: fdisk dependency needed
Processing control commands: > severity -1 important Bug #872215 [src:sosreport] sosreport: fdisk dependency needed Severity set to 'important' from 'serious' -- 872215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960283: [Pkg-javascript-devel] Bug#960283: Not in backports
Le 22/05/2020 à 09:56, Viktor Csiky a écrit : > Hello > > This fix still didn't surface in backports. > > Please add it to backports, otherwise (I guess unlike testing) there is > no feasible means for anyone using backports to fix the whole npm bunch, > except disabling backports, purging and reinstalling (the older one). Hi, I pushed node-dot-prop in backports. Since this package is new in backports, wait 2-3 days to get it Cheers, Xavier Forwarder mail From: Debian FTP Masters Subject: node-dot-prop_5.2.0-1~bpo10+1_amd64.changes is NEW binary:node-dot-prop is NEW. binary:node-dot-prop is NEW. source:node-dot-prop is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Bug#936336: coz-profiler: Python2 removal in sid/bullseye
Package: coz-profiler Version: 0.1.0-2 Followup-For: Bug #936336 Any updates on bringing coz-profiler to newer version and back to testing? Upstream is at 0.2.1 and doesn't use Python 2 anymore.
Bug#961207: marked as done (libgraphics-colorobject-perl: FTBFS: Cannot load color naming scheme module Graphics::ColorNames::HTML)
Your message dated Fri, 22 May 2020 09:33:49 + with message-id and subject line Bug#961207: fixed in libgraphics-colorobject-perl 0.5.0-10 has caused the Debian Bug report #961207, regarding libgraphics-colorobject-perl: FTBFS: Cannot load color naming scheme module Graphics::ColorNames::HTML 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.) -- 961207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961207 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libgraphics-colorobject-perl Version: 0.5.0-9 Severity: serious This package failed to build on the arch:all autobuilder. https://buildd.debian.org/status/fetch.php?pkg=libgraphics-colorobject-perl=all=0.5.0-9=1590030764=0 # Failed test 'use Graphics::ColorObject;' # at t/01load.t line 2. # Tried to use 'Graphics::ColorObject'. # Error: Cannot load color naming scheme module Graphics::ColorNames::HTML at /<>/blib/lib/Graphics/ColorObject.pm line 2096. # Compilation failed in require at t/01load.t line 2. # BEGIN failed--compilation aborted at t/01load.t line 2. # Looks like you failed 1 test of 1. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: libgraphics-colorobject-perl Source-Version: 0.5.0-10 Done: Manoj Srivastava We believe that the bug you reported is fixed in the latest version of libgraphics-colorobject-perl, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Manoj Srivastava (supplier of updated libgraphics-colorobject-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 22 May 2020 02:13:44 -0700 Source: libgraphics-colorobject-perl Architecture: source Version: 0.5.0-10 Distribution: unstable Urgency: medium Maintainer: Manoj Srivastava Changed-By: Manoj Srivastava Closes: 961207 Changes: libgraphics-colorobject-perl (0.5.0-10) unstable; urgency=medium . * It is not HTML anymore, it is WWW, * Bug fix: "FTBFS: Cannot load color naming scheme module Graphics::ColorNames::HTML", thanks to Niko Tyni (Closes: #961207). Checksums-Sha1: d5eefc810a3bfa191df45806aa458d354340e8b7 2132 libgraphics-colorobject-perl_0.5.0-10.dsc 95cde7fe53ed0b4c57b1681c8654bcbfcd0cbe5a 25357 libgraphics-colorobject-perl_0.5.0-10.diff.gz Checksums-Sha256: 21f0a0f4aa898e5324fb8fc9a0013f375505a7d528799ef3a3035c75b59aa727 2132 libgraphics-colorobject-perl_0.5.0-10.dsc 63021989971b54cbbb966df4eeb35ad749f986940051df23a39f1fc4defa85c0 25357 libgraphics-colorobject-perl_0.5.0-10.diff.gz Files: bd2ee8bbab3daa691a8d6ee0e00dd173 2132 perl optional libgraphics-colorobject-perl_0.5.0-10.dsc 9f2a17a1b7b414e324e5315fbb3da453 25357 perl optional libgraphics-colorobject-perl_0.5.0-10.diff.gz -BEGIN PGP SIGNATURE- iQGZBAEBCgCDFiEEq6cQJaG1qIpOX2jCNr1yD29XZHIFAl7HmktQFIAAGwAs c3JpdmFzdGFAZ29sZGVuLWdyeXBob24uY29tQUJBNzEwMjVBMUI1QTg4QTRFNUY2 OEMyMzZCRDcyMEY2RjU3NjQ3Ml8yMzIUHHNyaXZhc3RhQGRlYmlhbi5vcmcACgkQ Nr1yD29XZHLNNAgA6Ib9cf9d7bmVvIxBvUVektJ1UNid0M+SEAIVoCVcB9bxTxWm BWHR019M0inr4vVC6OUuqX/wvKAuwS2/FhPBwo5Uj9n7CFUZxVtpYx/hgC6Djxwj wsjaIReHTva//e6pFfvWpFGD9+UP93booxGI5AvmrPWvaXoxr8JYTIMemUzjifkF ymjJUHsglgM9Qr3IKY/PDKeKtkp1Mfeq6FTL2s66q7RwBXUUdIDEpeAwnZCdRZfo owFCKoNhKqFC9P81T0/woX3QzLYdT4Th0bDfx1sc7aLgs8B8vbaClepsyLDQj6Sj B3OxFom0CksKoQbkp0nJM4+VySVF4y12qiz4cg== =iuIR -END PGP SIGNATURE End Message ---
Processed: Bug#961028: hplip: No scanner found: SANE cannot load the hpaio backend
Processing commands for cont...@bugs.debian.org: > reassign 961028 libsane-hpaio Bug #961028 [hplip] hplip: No scanner found: SANE cannot load the hpaio backend Bug reassigned from package 'hplip' to 'libsane-hpaio'. No longer marked as found in versions hplip/3.20.5+dfsg0-2. Ignoring request to alter fixed versions of bug #961028 to the same values previously set > severity 961088 important Bug #961088 [libsane-hpaio] libsane-hpaio fails to detect HP MFDs Severity set to 'important' from 'serious' > forwarded 961028 https://bugs.launchpad.net/hplip/+bug/1880065 Bug #961028 [libsane-hpaio] hplip: No scanner found: SANE cannot load the hpaio backend Set Bug forwarded-to-address to 'https://bugs.launchpad.net/hplip/+bug/1880065'. > forwarded 961088 https://bugs.launchpad.net/hplip/+bug/1880065 Bug #961088 [libsane-hpaio] libsane-hpaio fails to detect HP MFDs Set Bug forwarded-to-address to 'https://bugs.launchpad.net/hplip/+bug/1880065'. > merge 961028 961088 Bug #961028 [libsane-hpaio] hplip: No scanner found: SANE cannot load the hpaio backend Bug #961028 [libsane-hpaio] hplip: No scanner found: SANE cannot load the hpaio backend Marked as found in versions hplip/3.20.5+dfsg0-2. Bug #961088 [libsane-hpaio] libsane-hpaio fails to detect HP MFDs Merged 961028 961088 > thanks Stopping processing here. Please contact me if you need assistance. -- 961028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961028 961088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951306: marked as done (snek: unsatisfiable b-d on picolibc-arm-none-eabi )
Your message dated Fri, 22 May 2020 09:04:58 + with message-id and subject line Bug#951306: fixed in snek 1.4-2 has caused the Debian Bug report #951306, regarding snek: unsatisfiable b-d on picolibc-arm-none-eabi 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.) -- 951306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: snek Version: 1.3-1 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hi, snek build-depends on picolibc-arm-none-eabi which does not exist (yet) in sid. -Ralf. --- End Message --- --- Begin Message --- Source: snek Source-Version: 1.4-2 Done: Keith Packard We believe that the bug you reported is fixed in the latest version of snek, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Keith Packard (supplier of updated snek 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: Thu, 21 May 2020 15:55:29 -0700 Source: snek Architecture: source Version: 1.4-2 Distribution: unstable Urgency: medium Maintainer: Keith Packard Changed-By: Keith Packard Closes: 951306 Changes: snek (1.4-2) unstable; urgency=medium . * Prepare source upload Closes: #951306. Checksums-Sha1: aa9147e4c24471706e8828ea1e9e9b28fce7c473 2143 snek_1.4-2.dsc 6c0a86273d9ea2d3402ae27fc8b43307b25b331f 6336 snek_1.4-2.debian.tar.xz b73aa588e10f24ddbbe5cbc9442d75be399fc884 10833 snek_1.4-2_amd64.buildinfo Checksums-Sha256: 42ddecfaec9dd2cafd620393be23a265f1664f3090c1c2f9014a99d4c7ece490 2143 snek_1.4-2.dsc 44161fd859c4a5faff24c07c8129dcdca17cc9fc3b5bed7ee428150a64e032a8 6336 snek_1.4-2.debian.tar.xz 2323168cddea1321384d7a46fed4a178bc647bade1b2a9eb1e2991d74a93b12c 10833 snek_1.4-2_amd64.buildinfo Files: 239897b1021f7c007ae83d001379e57a 2143 interpreters optional snek_1.4-2.dsc 64d8ea550d2846ae4f8848af57226354 6336 interpreters optional snek_1.4-2.debian.tar.xz 8339cb1fdd636f4f98768b33f99128f6 10833 interpreters optional snek_1.4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAl7HlDMACgkQ2yIaaQAA ABG+9A/+MY5hS8ShX/KPgk7usPSkPOQSwYKkXhMGw4AgHTaOc8e0qtHej1UfsB9Z CClqAyWFd+p6s9qW2+sr7lrLHDiaBhWBaUVdkdKhGY69GmtzwWJQFm2Yee16Dzq3 C0pZIrMKXu4Jyj2ge4wpTif5l0OZy/ko19z1RG/VEO2+puEbI7kIHIqT6j75Opu9 XOYQ/yo7N8iuPQXSXqi/9XDU/YSCmSduV8vinam07SXgP/Msis1OjsEeA70RQA7c FGRUr9eraOqfPr4xSw4lXsP1D+KMnIdzrDKgU1in+Yj6Sce4AnqPhFmVnwbCapgp HdCWPRtzeCZ+j0Ya5u2UxUgQpo7maTSvWnNcrtcWSMkZwvRJVzcHd04TeqYmTb2Z sBIp6DbjmJ3BbvEdVL6cyaJWDMI0C4DqAYHBiWDmQlVL7J3s8pJz6FJ2/SCwU4dg /SsIirWan+93CYLRD3zFCNl2wb0uLQU9ghxhCcRpIvt60ALmTATSzAsk1NBDi157 LheJiWHpNJ694E5SEr7jN9Sh+x3E+6U7UgjYQ7HoY+zi02Yg3aZcjXql5RJvxDPq psye07+JU9LLl+ekXkFiUgwYSD1e6n1J/ucdyV7HWCXnlNVnNYr9yVO01NCydyjj vY0/GAKVCiZc+hn9XuxUzgj5v6LC0FlwE09CkIOpWN6ZoWicd7w= =ZPm1 -END PGP SIGNATURE End Message ---
Bug#961245: mercurial-common: trying to overwrite '/usr/lib/python2.7/dist-packages/hgext/git/__init__.py', which is also in package mercurial-git 0.8.12-1.2
* Axel Beckert , 2020-05-22, 00:22: dpkg: error processing archive /var/cache/apt/archives/mercurial-common_5.4-1_all.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/hgext/git/__init__.py', which is also in package mercurial-git 0.8.12-1.2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/mercurial-common_5.4-1_all.deb Note that there's no such conflict upstream, because hg-git installs the module as "hggit" (not in the "hgext" namespace). This mess is my fault. When I packaged hg-git in 2009, it was so immature it didn't even have installation scripts. Instead their README said: Clone this repository somewhere and make the 'extensions' section in your `~/.hgrc` file look something like this: [extensions] hgext.bookmarks = hgext.hg-git = [path-to]/hg-git I decided to install it as a public module "hgext.git", without even talking to upstream. In retrospect, it was a terrible idea. :-( Ideally this should be fixed by renaming the hg-git's module back to what upstream uses. But of course this is going to break all hg-git users' configurations. :-/ -- Jakub Wilk
Processed: Document the bugs I just fixed upstream in po4a
Processing commands for cont...@bugs.debian.org: > tag 960892 fixed-upstream Bug #960892 [po4a] po4a: --srcdir ignored by [po_directory] Added tag(s) fixed-upstream. > tag 725931 fixed-upstream Bug #725931 [po4a] random order in SGML tags Added tag(s) fixed-upstream. > tag 810988 fixed-upstream Bug #810988 [po4a] po4a: Always fuzzies one string, even if translation is correct (German goobox man page) Added tag(s) fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 725931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725931 810988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810988 960892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960283: Not in backports
Hello This fix still didn't surface in backports. Please add it to backports, otherwise (I guess unlike testing) there is no feasible means for anyone using backports to fix the whole npm bunch, except disabling backports, purging and reinstalling (the older one). Best, Victor
Bug#933128: libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream
Hi,
intrig...@debian.org (2019-07-26):
> Therefore, at the pkg-perl BoF today at DebConf, after pondering other
> options such as orphaning this package, we decided that we don't want
> this package to be included in Bullseye (at least, maintained under
> the Perl team umbrella) unless someone else steps up and becomes its
> upstream maintainer. [...]
> libparse-debianchangelog-perl has quite a few reverse-dependencies, [...]
10 months later, we've reached the point when there's 1 single
reverse dependency left in sid: customdeb, whose maintainer promptly
agreed it can be removed at the same time as libparse-debianchangelog-perl.
All other previous reverse dependencies were ported to something else
(most often libdpkg-perl) and nobody volunteered to adopt it upstream.
Thanks a lot to everyone who participated in making this happen :)
In testing there's another reverse-dependency: aptitude, which has
been ported away from libparse-debianchangelog-perl in 0.8.13-1.
So, once aptitude >= 0.8.13-1 has migrated to testing, I think it'll
be time to ensure libparse-debianchangelog-perl itself is removed from
testing, which was the goal of the whole operation.
But:
> Note that libparse-debianchangelog-perl is on the list of key
> packages¹ so this RC bug won't trigger the autoremoval machinery for
> it, nor for any of its reverse dependencies.
>
> [1] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
libparse-debianchangelog-perl is on the list of key packages because
it's installed on many machines ("popcon"). This will prevent the
autoremoval machinery from removing it from testing.
So, once aptitude >= 0.8.13-1 has migrated to testing, we'll need to
ask (presumably the release team) for libparse-debianchangelog-perl to
lose its "key package" status, so the autoremoval machinery can remove
it from testing due to this very RC bug.
Cheers!
Bug#960892: another fix
Control: -1 fixed-upstream Thanks On Fri, May 22, 2020 at 02:35:34AM +0200, Axel Beckert wrote: > Hi Martin. > > Martin Quinson wrote: > > I gave another try to this fix, and the current git version of po4a > > manages to build aptitude even with the recent patch removed. > > > > Could you please give it a try, just to ensure that I didn't mess up > > my verification? > > Can confirm. Thanks for caring! Thanks for this test. I'm happy that this bug is gone now. I will release a new upstream version on Sunday. I'm just giving a few days to the translators to update their work since the fix introduced some strings, and since you have a temporarily fix in aptitude. Have a good one, Mt. -- Walking on water and developing software from a specification are easy if both are frozen. signature.asc Description: PGP signature
Processed: Re: Bug#933131: customdeb: depends on libparse-debianchangelog-perl that has no upstream maintainer
Processing control commands: > severity -1 serious Bug #933131 [customdeb] customdeb: depends on libparse-debianchangelog-perl that has no upstream maintainer Severity set to 'serious' from 'important' -- 933131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938261: marked as done (python-werkzeug: Python2 removal in sid/bullseye)
Your message dated Fri, 22 May 2020 07:35:00 + with message-id and subject line Bug#938261: fixed in python-werkzeug 1.0.1+dfsg1-1 has caused the Debian Bug report #938261, regarding python-werkzeug: Python2 removal in sid/bullseye 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.) -- 938261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-werkzeug Version: 0.14.1+dfsg1-4 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 Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-werkzeug If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-werkzeug Source-Version: 1.0.1+dfsg1-1 Done: =?utf-8?b?T25kxZllaiBOb3bDvQ==?= We believe that the bug you reported is fixed in the latest version of python-werkzeug, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Nový (supplier of updated python-werkzeug package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 22 May 2020 09:18:21 +0200 Source: python-werkzeug Binary: python-werkzeug-doc python3-werkzeug Architecture: source all Version: 1.0.1+dfsg1-1 Distribution: experimental Urgency: medium Maintainer: Python Modules Packaging Team Changed-By: Ondřej Nový Description: python-werkzeug-doc - documentation for the werkzeug Python library (docs) python3-werkzeug - collection of utilities for WSGI applications (Python 3.x) Closes: 938261 Changes: python-werkzeug (1.0.1+dfsg1-1) experimental; urgency=medium . * New upstream release. * Sync with unstable (Closes: #938261). * Bump upstream compat level to 13. Checksums-Sha1: 04ae502c3f1156cb1e238b0b79c8f399da461c65 2442 python-werkzeug_1.0.1+dfsg1-1.dsc 4b5aa9ff48e780268966cbfca8cafd82586ba8a9 730032 python-werkzeug_1.0.1+dfsg1.orig.tar.xz cdc49b1e7a4cfb384eb2a13f0a256cabb1445e3a 7392
Processed: Bug#938261 marked as pending in python-werkzeug
Processing control commands: > tag -1 pending Bug #938261 [src:python-werkzeug] python-werkzeug: Python2 removal in sid/bullseye Added tag(s) pending. -- 938261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938261: marked as pending in python-werkzeug
Control: tag -1 pending Hello, Bug #938261 in python-werkzeug 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/python-werkzeug/-/commit/479ad96fd9e7d7a96ec6392a25374e810aea8276 Drop python2 support; Closes: #938261 (this message was generated automatically) -- Greetings https://bugs.debian.org/938261
Bug#955535: marked as done (httping: flaky autopkgtest: PING google.com:80)
Your message dated Fri, 22 May 2020 06:48:39 + with message-id and subject line Bug#955535: fixed in httping 2.5-5.1 has caused the Debian Bug report #955535, regarding httping: flaky autopkgtest: PING google.com:80 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.) -- 955535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: httping Version: 2.5-5 Severity: serious Tags: sid bullseye User: debian...@lists.debian.org Usertags: flaky The test for httping passed on amd64[0] and failed on arm64[1]. Looking at the failed log |autopkgtest [17:03:58]: test command3: httping -F -c 4 http://google.com |autopkgtest [17:03:58]: test command3: [--- |PING google.com:80 (/): |connect time out | |connect time out | |connect time out | |connect time out | |--- http://google.com/ ping statistics --- |4 connects, 0 ok, 100.00% failed, time 124118ms |autopkgtest [17:06:02]: test command3: ---] |autopkgtest [17:06:02]: test command3: - - - - - - - - - - results - - - - - - - - - - |command3 FAIL non-zero exit status 127 |autopkgtest [17:06:02]: summary |command1 PASS |command2 PASS |command3 FAIL non-zero exit status 127 it seems to have failed because the test is not allowed to connect to the internet (or google itself). Could it be verified what the test policy is in regard to network access and then - run the test again once CI enabled network access on all nodes - removed that test from CI. [0] https://ci.debian.net/data/autopkgtest/testing/amd64/h/httping/4779756/log.gz [1] https://ci.debian.net/data/autopkgtest/testing/arm64/h/httping/4780569/log.gz Sebastian --- End Message --- --- Begin Message --- Source: httping Source-Version: 2.5-5.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of httping, 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. Adrian Bunk (supplier of updated httping package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 08 May 2020 09:30:50 +0300 Source: httping Architecture: source Version: 2.5-5.1 Distribution: unstable Urgency: low Maintainer: Abhijith PA Changed-By: Adrian Bunk Closes: 955535 Changes: httping (2.5-5.1) unstable; urgency=low . * Non-maintainer upload. * Add needs-internet restrictions to autopkgtest. (Closes: #955535) * Remove unnecessary test depends. Checksums-Sha1: 7b83db3ef903e2301ac2b1055f8d68187c70d32d 1930 httping_2.5-5.1.dsc 7af990123e546ae905b7688e613f7dcb37f3f106 4628 httping_2.5-5.1.debian.tar.xz Checksums-Sha256: 2baff0c8a533a0c28aa864457286867f0ca3abbc4ec1c15a4973cb41e088932c 1930 httping_2.5-5.1.dsc 2138781f435d50b945352c4a2f4649e38458f1a48a1b6d7af0bf85f428373d25 4628 httping_2.5-5.1.debian.tar.xz Files: 484cc6c8dd2b0d7a86a0400aa801fc55 1930 net optional httping_2.5-5.1.dsc 47e3cf1f155393cceaaedf2f6d30afb0 4628 net optional httping_2.5-5.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl60/zYACgkQiNJCh6LY mLHwmA/+I/YorpLW/bVc88IiKa1tm3/2TYxw1QCqWfXIF/hq1G9ZySda09DcFIHk GvARezF+79CpLq1fTdIJ/dPmkSa5giTzohwWPN9Q9jDlX8gda7zc3nw5soxgXO3L QGhDEIP9hM/ZyzkwPqfkOQThn22/x10WGFW1tpgsxOBudnRmXQMVPnX5gXLtC5FT f0wBGJjASAoUatPcG+5vzjHuxjb70fmsbxs7zy9eoXWd8Vl/7qFA/F2vcFWWroye CrmqwEJ8ehOjaouzgOawFSxutgPZjxdHe9RZ8OIH0sXK45JDZSEhQ/Nzg9G3jJXV CSaEbVmWpx0yneE7dO+nloNTDKvv1OTx+m7KIeZ3emJg5n+r1d5rntXMyVCymqo0 vtuwRLTCbjmHRzQ1w3HkYa8t4DrFOJ8UkloXvtLQImK11UpYF4mfO6EL0727imLv RGANONUGwL7BwKJSKR9wFDsOuvrykTa5vyJgr+9FoVxCjYFVDY82xJL8F2+JBw3C +YD/l4u4UmG0hHnR1mBAbi8cNJCRPBU24sNFeY56/yx/V6QLIzs6tBhMiEQYcIcf OjvzQCZen0KsNqGmG5fCe4HZ6SuBH2VnnGXg1f/H1PHEMU24E7egktjh1sY6ZX3S tmdCefNUeViJZZt7oMpoC8RWt51O6SWF6Ujrofjt/QT/pHMQz0M= =wpCw -END PGP SIGNATURE End Message ---
Bug#961147: libcolor-calc-perl: broken by new libgraphics-colornames-perl
Hi, Niko Tyni (2020-05-21): > So IMO we should either to package Graphics::ColorNames::HTML even though > it's deprecated, or drop Color::Calc from Debian. > libcolor-calc-perl has just one reverse dependency AFAICS: > libcgi-application-plugin-authentication-perl. I took a quick look. At runtime, Color::Calc optionally enhances libcgi-application-plugin-authentication-perl: it allows providing one base color and letting the module derive other colors from it — as opposed to sticking with the default colors, or specifying every color one wants to use. At build time, it seems libcgi-application-plugin-authentication-perl should build just fine if Color::Calc is not available: the corresponding tests should be skipped. So that reverse build-dependency is probably not, in itself, a blocker for removing Color::Calc from Debian. libcolor-calc-perl's popcon is low and steadily decreasing since 10 years.
Bug#961256: sra-toolkit: srapath is a broken symlink
Package: sra-toolkit Version: 2.10.6+dfsg-3 Severity: serious Control: affects -1 src:sra-sdk $ file /usr/bin/srapath* /usr/bin/srapath: broken symbolic link to sratools.2.10.6 /usr/bin/srapath-orig.2.10.6: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=20f0f36fab86a1389d442e83d4a4040eec1bfd92, for GNU/Linux 3.2.0, stripped $ This is also the cause of the autopkgtest failure.
Processed: sra-toolkit: srapath is a broken symlink
Processing control commands: > affects -1 src:sra-sdk Bug #961256 [sra-toolkit] sra-toolkit: srapath is a broken symlink Added indication that 961256 affects src:sra-sdk -- 961256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961107: marked as done (slic3r-prusa FTBFS on mipsel and i386)
Your message dated Fri, 22 May 2020 06:03:42 + with message-id and subject line Bug#961107: fixed in slic3r-prusa 2.2.0+dfsg1-2 has caused the Debian Bug report #961107, regarding slic3r-prusa FTBFS on mipsel and i386 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.) -- 961107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slic3r-prusa Version: 2.2.0+dfsg1-1 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/fetch.php?pkg=slic3r-prusa=mipsel=2.2.0%2Bdfsg1-1=1586422709=0 ... virtual memory exhausted: Cannot allocate memory make[3]: *** [src/libslic3r/CMakeFiles/libslic3r_cgal.dir/build.make:66: src/libslic3r/CMakeFiles/libslic3r_cgal.dir/MeshBoolean.cpp.o] Error 1 https://buildd.debian.org/status/fetch.php?pkg=slic3r-prusa=i386=2.2.0%2Bdfsg1-1=1586426190=0 ... test cases: 28 | 27 passed | 1 failed assertions: 519 | 517 passed | 2 failed E: Build killed with signal TERM after 150 minutes of inactivity Fix/workaround: --- debian/rules.old2020-04-07 15:08:57.0 + +++ debian/rules2020-05-20 06:43:06.593960217 + @@ -4,7 +4,11 @@ # less debug info to avoid running out of address space ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel)) - export DEB_CXXFLAGS_MAINT_APPEND += -g1 + export DEB_CXXFLAGS_MAINT_APPEND += --param ggc-min-expand=5 -g0 +endif + +ifneq (,$(filter $(DEB_HOST_ARCH), i386)) +export DEB_CXXFLAGS_MAINT_APPEND += -ffloat-store endif %: --- End Message --- --- Begin Message --- Source: slic3r-prusa Source-Version: 2.2.0+dfsg1-2 Done: Chow Loong Jin We believe that the bug you reported is fixed in the latest version of slic3r-prusa, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chow Loong Jin (supplier of updated slic3r-prusa package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 22 May 2020 12:40:15 +0800 Source: slic3r-prusa Architecture: source Version: 2.2.0+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian 3-D Printing Packages <3dprinter-gene...@lists.alioth.debian.org> Changed-By: Chow Loong Jin Closes: 961107 Changes: slic3r-prusa (2.2.0+dfsg1-2) unstable; urgency=medium . * [38942b0] Fix FTBFS on mips, and mipsel (oom), and i386 (float issues) Thanks to Adrian Bunk (Closes: #961107) Checksums-Sha1: 1fa498b7e394a695708f1a86f377c7ec4d0b801b 2398 slic3r-prusa_2.2.0+dfsg1-2.dsc fab4d61faf1897dee9eebb5551bf5e280b17345f 42304 slic3r-prusa_2.2.0+dfsg1-2.debian.tar.xz a5c895a23f5bcfe9e69a0483112e5850b68c7586 14777 slic3r-prusa_2.2.0+dfsg1-2_source.buildinfo Checksums-Sha256: 19ed765d8b1d0d5cd701e7f47baba8702516790fb9c4255655d4a45e6b9bb349 2398 slic3r-prusa_2.2.0+dfsg1-2.dsc 3d82b68a59983d954e55dd26f5b5990d8d8040d9be60a162f6a4872834279168 42304 slic3r-prusa_2.2.0+dfsg1-2.debian.tar.xz ba5624e5493ce8e814999f34a114183bce7504a224d2926180c9b2f568142c78 14777 slic3r-prusa_2.2.0+dfsg1-2_source.buildinfo Files: 6f1db741df0faa51f296f8ebac6bdb67 2398 misc optional slic3r-prusa_2.2.0+dfsg1-2.dsc f76a732ccfcd4e3ad9a3aeb7b54474db 42304 misc optional slic3r-prusa_2.2.0+dfsg1-2.debian.tar.xz 64fc3793be144b9aa807d45ce4362181 14777 misc optional slic3r-prusa_2.2.0+dfsg1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEEuDQnfs/9/dZ027Q+9UiW1iHUqEFAl7HZNwACgkQ+9UiW1iH UqFGaw//RQjmlg+xXPCgxLKjP8qN0FuyR6G8SlMlh5DIsRGNPxHJh2o2G9zG+BJz 0TwwZB1CNCXK/wWpI6t2Px7hvkIjtiLd1nee3U0bsBVeDdGiBePrAeP2bwiNpusS 9x7tF6C0RoqZbDrXOdskh9a0PK3u3mziwdCbkvufI2b7vxTif/kiK3ktLRDvXYOM ow4FvwXBT+lsbmHmGEwybCk4KXVtNlqPu/FWnm4RqSVQFV2QxW/brU70OZcLvBDy vbmDBYK8lE0peY7uHwNOPQ3TmdbzUjGHDOuexyaV9oTb/YhbQ3ACmb1S4rB39aYi kfgBqQahEdNbq36kSk6zwEq94LnEJY/rLgk+nw+0t53ZKRe7N1E99oAeCtyk9KQx AcFlAedhKxzrjGurqdOw6VQgTM5OnMMANzm8tftqTV3aWZrS0bQ/3ZKv+D72szfD k4/DGS+2wxO5LYPXlj+6Fg8LH2PRcrEOLxTjFD6yMyKjhYH2tFJbv85bogmAt8lZ Bowa+yXoIf3rJSYLG270WlGrBTE7H5UwJOLZzGB+wwHf9hX8m4VqiIP5RCxmvLUy ISc2MDfKzoee10GZeCEjUwJO7vwYagXl8eFswRIbIQb/HAYnO284mmcwoguDd3kl
