Bug#934089: firehol fails to use iptables-restore
Dear Jean Louis, thanks for your report. Have you tried, as suggested in the FireHOL message, /usr/sbin/firehol nofast try Please let me know the output of this action, if possible. Thanks in advance, Jerome -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B signature.asc Description: OpenPGP digital signature
Bug#934034: monkeysphere: FTBFS in stretch
Chris Lamb: > [Correctly adding t...@release.debian.org to CC...] > > Hi Santiago, > >> For completeness I would also make the build-dependency on gnupg to be >> versioned. > > Good idea; updated patch attached. > > Stable release managers, would you consider this for the next stretch > point release? > > > Regards, > Hi Chris, Thanks for considering to fix bugs in stretch. Please use the process described in [1] to ensure we will get to look at it: 1) The current bug metadata suggests it affects sid. Please ensure the bug is resolved in sid (by fixing it in sid or correcting bug metadata as appropriate). 2) File an opu (and a separate pu bug if it also affects buster) with the full debdiff (including changelog). This ensures that the stable release team will get have a look at the issue. We are quite insisting on 2) as it is very hard for us to keep track of non-bugs requests. This is a lesson learned time and again (both for us and Debian contributors). As for your concrete diff (IANASRM, but my personally take is that): It looks like something we would accept as stable update. Note that [1] describes some short cuts that may or may not be applicable to your situation. Thanks, ~Niels [1] https://lists.debian.org/debian-devel-announce/2019/08/msg0.html
Bug#923084: Misuse of dh_python3
Howdy,
On Wed, 14 Aug 2019, Ben Finney wrote:
On 01-Apr-2019, Unit 193 wrote:
dh_python3 reads [its arguments such that] any path passed as an
argument is prefixed with 'debian/$package/', which in this case
ends up being 'debian/gandi-cli/debian/gandi-cli/...'
I can now confirm this difference.
The original described problem was that Debhelper was reading the
package control stanza's “Depends” field in the source package:
Depends: ${python3:Depends}, ${misc:Depends}
and incorrectly expanding its “python3:Depends” placeholder to an
empty dependency list in the binary package:
Depends:
When I change the ‘dh_python3’ arguments as Unit 193 describes, the
resulting “Depends” field in the binary package is:
Depends: python3-click (>= 7.0), python3-ipy,
python3-pkg-resources, python3-requests, python3-yaml,
python3:any
Unit 193, can you confirm that is correct to resolve this bug?
Just passing dh_python3 with no arguments does give me the expected value of
Depends: python3-click (>= 7.0), python3-ipy, python3-pkg-resources,
python3-requests, python3-yaml, python3:any
So yep, I can indeed confirm!
~Unit 193
Unit193 @ freenode
Unit193 @ OFTC
Bug#933848: FTBFS if cmake is installed or if built twice in a row
Source: pygalmesh Followup-For: Bug #933848 Control: severity -1 important Control: tags -1 + moreinfo,unreproducible There is no cmake-related FTBFS for me. Fixing the tags for moreinfo,unreproducible -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Processed: Re: FTBFS if cmake is installed or if built twice in a row
Processing control commands:
> severity -1 important
Bug #933848 {Done: Drew Parsons } [src:pygalmesh] FTBFS if
cmake is installed or if built twice in a row
Severity set to 'important' from 'serious'
> tags -1 + moreinfo,unreproducible
Bug #933848 {Done: Drew Parsons } [src:pygalmesh] FTBFS if
cmake is installed or if built twice in a row
Added tag(s) moreinfo and unreproducible.
--
933848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#923084: Misuse of dh_python3
Processing control commands: > tags -1 + confirmed pending Bug #923084 [gandi-cli] gandi-cli: Show ‘dh_python3’ where to find install requirements Added tag(s) confirmed and pending. -- 923084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923084: Misuse of dh_python3
Control: tags -1 + confirmed pending
On 01-Apr-2019, Unit 193 wrote:
> dh_python3 reads [its arguments such that] any path passed as an
> argument is prefixed with 'debian/$package/', which in this case
> ends up being 'debian/gandi-cli/debian/gandi-cli/...'
I can now confirm this difference.
The original described problem was that Debhelper was reading the
package control stanza's “Depends” field in the source package:
Depends: ${python3:Depends}, ${misc:Depends}
and incorrectly expanding its “python3:Depends” placeholder to an
empty dependency list in the binary package:
Depends:
When I change the ‘dh_python3’ arguments as Unit 193 describes, the
resulting “Depends” field in the binary package is:
Depends: python3-click (>= 7.0), python3-ipy,
python3-pkg-resources, python3-requests, python3-yaml,
python3:any
Unit 193, can you confirm that is correct to resolve this bug?
--
\ “If trees could scream, would we be so cavalier about cutting |
`\ them down? We might, if they screamed all the time, for no good |
_o__)reason.” —Jack Handey |
Ben Finney
signature.asc
Description: PGP signature
Processed: [PATCH] Keep help files in upstream location
Processing commands for cont...@bugs.debian.org: > tags 934661 patch Bug #934661 [python3-fava] python3-fava: Fails to start with ModuleNotFoundError: No module named 'fava.help' Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 934661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934661: [PATCH] Keep help files in upstream location
tags 934661 patch
thanks
- >8 -
Removing the entire contents due to the missing __init__.py file.
Removing the markdown files from this location prevents the help from
being displayed through the web UI.
---
debian/python3-fava.docs | 1 -
debian/rules | 4
2 files changed, 5 deletions(-)
diff --git a/debian/python3-fava.docs b/debian/python3-fava.docs
index bd619a9..a1320b1 100644
--- a/debian/python3-fava.docs
+++ b/debian/python3-fava.docs
@@ -1,2 +1 @@
README.rst
-fava/help/
diff --git a/debian/rules b/debian/rules
index f1bf718..d6e9c81 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,7 +4,6 @@ include /usr/share/dpkg/pkg-info.mk
export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie
-export PYBUILD_AFTER_INSTALL=rm -rf '{destdir}/{install_dir}/fava/help'
export PYBUILD_NAME=fava
%:
dh $@ --with python3 --buildsystem=pybuild
@@ -26,6 +25,3 @@ endif
override_dh_auto_clean:
dh_auto_clean
rm -f debian/manpages/fava.1
-
-override_dh_installdocs:
- dh_installdocs -X __init__.py -X __pycache__
--
2.23.0.rc1
signature.asc
Description: PGP signature
Bug#923481: alpine: replies lose In-Reply-To and References headers
Howdy, On Tue, 13 Aug 2019, Thorsten Glaser wrote: severity 923481 serious thanks (Please remember to Cc the bug submitter when replying.) On Sat, 9 Mar 2019, Unit 193 wrote: As I understand it, this is not a regression in alpine but a difference in how pine and alpine function, correct? No, this is definitively a serious loss of functionality, namely, message threading (which is expected to work correctly in contemporary MUAs excepting those from Redmond). Ah right. Though while looking through several of my recent sent items, it seems it preserved those fields as expected. I am using alpine 2.21. It seems I am unable to reproduce the results you're getting? ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#934716: binutils patch applied, package now ftbfs
Package: src:cross-toolchain-base-mipsen VersioN: 5 Severity: serious Tags: sid bullseye the binutils patch is now applied, and the package now ftbfs. please remove the patch again.
Bug#934034: monkeysphere: FTBFS in stretch
[Correctly adding t...@release.debian.org to CC...] Hi Santiago, > For completeness I would also make the build-dependency on gnupg to be > versioned. Good idea; updated patch attached. Stable release managers, would you consider this for the next stretch point release? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-diff --git a/debian/control b/debian/control index 95750f4..19c4dbb 100644 --- a/debian/control +++ b/debian/control @@ -9,7 +9,7 @@ Build-Depends: cpio, debhelper (>= 10~), dpkg-dev (>= 1.17.14), - gnupg , + gnupg (>= 2.1.18-8~deb9u4) , gnupg-agent , libassuan-dev, libcrypt-openssl-rsa-perl , diff --git a/tests/keytrans b/tests/keytrans index fd9a144..5b23a16 100755 --- a/tests/keytrans +++ b/tests/keytrans @@ -137,9 +137,9 @@ gpg --list-keys cat >"$TEMPDIR"/expectedout <"$TEMPDIR"/expectedout <"$TEMPDIR"/expectedout <
Bug#934034: monkeysphere: FTBFS in stretch
[Adding rele...@lists.debian.org to CC] Hi Santiago, > For completeness I would also make the build-dependency on gnupg to be > versioned. Good idea; updated patch attached. Stable release managers, would you consider this for the next stretch point release? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-diff --git a/debian/control b/debian/control index 95750f4..19c4dbb 100644 --- a/debian/control +++ b/debian/control @@ -9,7 +9,7 @@ Build-Depends: cpio, debhelper (>= 10~), dpkg-dev (>= 1.17.14), - gnupg , + gnupg (>= 2.1.18-8~deb9u4) , gnupg-agent , libassuan-dev, libcrypt-openssl-rsa-perl , diff --git a/tests/keytrans b/tests/keytrans index fd9a144..5b23a16 100755 --- a/tests/keytrans +++ b/tests/keytrans @@ -137,9 +137,9 @@ gpg --list-keys cat >"$TEMPDIR"/expectedout <"$TEMPDIR"/expectedout <"$TEMPDIR"/expectedout <
Processed: Re: Bug#934711: Please package latest upstream, and switch to Python 3
Processing control commands: > severity -1 normal Bug #934711 [python-googleapi] Please package latest upstream, and switch to Python 3 Severity set to 'normal' from 'serious' > tags -1 pending Bug #934711 [python-googleapi] Please package latest upstream, and switch to Python 3 Added tag(s) pending. -- 934711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934711: Please package latest upstream, and switch to Python 3
Control: severity -1 normal Control: tags -1 pending On Tue, Aug 13, 2019 at 9:48 PM Thomas Goirand wrote: > We're trying to remove Python 2 for Bullseye. Yup, I do know it like you. > Please package the latest version upstream which has support for Python 3, > and remove Python 2 support / use. I'm working on it. A day or two and it will be uploaded. Regards, Laszlo/GCS
Bug#695873: memtest86+: Serial console does not work
Hi, Feel free do NMU - thanks much for this :) - Mail original - > De: "Louis-Philippe Véronneau" > À: 695...@bugs.debian.org > Envoyé: Mardi 13 Août 2019 21:44:38 > Objet: Bug#695873: memtest86+: Serial console does not work > > Hello! > > I'd be happy to make an NMU to fix this, since: > > * there is a patch > * the patch was tested by 4 people and it seems to work > * the patch looks trivial > * the patch has been merged in Fedora [1] > > I've emailed the maintainer directly to ask him if it would be OK > with > him for me to NMU this. > > If I don't get an answer I'll look into fixing this by an NMU :) > > Cheers, > > [1] > https://src.fedoraproject.org/rpms/memtest86+/blob/master/f/memtest86+-5.01-serial-console-fix.patch > > -- > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau > ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org > ⠈⠳⣄ > >
Bug#921506: marked as done (sysbench: build-depends on libck-dev which is not available on several architectures)
Your message dated Tue, 13 Aug 2019 22:12:40 +0200 with message-id <20190813221134.27f40...@vip.jcf.pm> and subject line Re: sysbench: build-depends on libck-dev which is not available on several architectures has caused the Debian Bug report #921506, regarding sysbench: build-depends on libck-dev which is not available on several architectures 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.) -- 921506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sysbench Version: 1.0.15+ds-1 Severity: serious Your package build-depends on libck-dev, which is not available on several release architectures where sysbench built in the past, thus making the package unbuildable and out of date there, preventing testing migration of the new version: https://buildd.debian.org/status/package.php?p=sysbench The solution to this is to either make the package there by making the libck-dev build-dependency conditional to the architectures where it's available (assuming sysbench can built without it), or to remove sysbench from the architectures where it can no longer be built by filing an RM bug against ftp.debian.org. Emilio --- End Message --- --- Begin Message --- RM bug for the archs lacking ck was filed as #934705 pgpmF1e8Vl3Yg.pgp Description: OpenPGP digital signature --- End Message ---
Bug#906697: ck: baseline violation on i386
Looks like upstream release 0.7.0 has an option to disable sse, see: https://github.com/concurrencykit/ck/commit/f00aaa977b0cbdfb513e1e4e68c1e31ec42270d7 pgpPTo9_YUvPB.pgp Description: OpenPGP digital signature
Bug#933220: siridb-server: missing source for Release/makefile
Control: severity -1 normal Hi Jeroen, On 13-08-2019 11:51, Jeroen van der Heijden wrote: > The SiriDB project once started by using the Eclipse IDE which generates > the make-files and adds the "Auto generated.." comments. Since the > project is ejected from Eclipse we can now simply remove the comments > and make future changes by hand. (This does not happen a lot, so changes > are relative easy to maintain). If you as upstream consider these files the preferred source for modification, than this bug isn't severity serious. Can you please remove the text upstream, so that it will be in the next release and we can close this bug when that happens, as the text *is* confusing. The same applies to Debug/makefile I assume. Paul signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#933220: siridb-server: missing source for Release/makefile
Processing control commands: > severity -1 normal Bug #933220 [src:siridb-server] siridb-server: missing source for Release/makefile Severity set to 'normal' from 'serious' -- 933220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933035: dmtcp: Should this package be removed?
Hi Moritz, I'm sorry for the delayed reply. We are about to release DMTCP version 2.6.0, and we are including a Debian package. We have verified with Yaroslav Halchenko that our proposed Debian package will pass. We should be submitting it this week. Also, we are replacing Kapil Arya by Paul Grosu (pgr...@gmail.com) as the new maintainer for DMTCP. Thanks, - Gene From: Moritz Muehlenhoff Sent: Thursday, July 25, 2019 5:35:07 PM To: Debian Bug Tracking System Subject: Bug#933035: dmtcp: Should this package be removed? Source: dmtcp Severity: serious The last upload was in 2014 and it's RC-buggy for a long time, it missed two stable releases already. Cheers, Moritz
Bug#695873: memtest86+: Serial console does not work
Hello! I'd be happy to make an NMU to fix this, since: * there is a patch * the patch was tested by 4 people and it seems to work * the patch looks trivial * the patch has been merged in Fedora [1] I've emailed the maintainer directly to ask him if it would be OK with him for me to NMU this. If I don't get an answer I'll look into fixing this by an NMU :) Cheers, [1] https://src.fedoraproject.org/rpms/memtest86+/blob/master/f/memtest86+-5.01-serial-console-fix.patch -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ signature.asc Description: OpenPGP digital signature
Bug#934711: Please package latest upstream, and switch to Python 3
Package: python-googleapi Version: 1.5.5-1 Severity: serious Hi, We're trying to remove Python 2 for Bullseye. python-monotonic support for Python 2 is removed, and therefore, your package depends on a cruft package. Please package the latest version upstream which has support for Python 3, and remove Python 2 support / use. Cheers, Thomas Goirand (zigo)
Processed: systemtap: autopkgtest fails when there are two versions of linux-latest available
Processing control commands: > affects -1 src:linux-latest Bug #934710 [src:systemtap] systemtap: autopkgtest fails when there are two versions of linux-latest available Added indication that 934710 affects src:linux-latest -- 934710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934710: systemtap: autopkgtest fails when there are two versions of linux-latest available
Source: systemtap Version: 4.1-7 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Control: affects -1 src:linux-latest Dear maintainers, With a recent upload of linux-latest the autopkgtest of systemtap fails in testing when that autopkgtest is run with the binary packages of linux-latest from unstable. It passes when run with only packages from testing. In tabular form: passfail linux-latest from testing106 systemtap from testing4.1-7 versioned deps [0] from testingfrom unstable all others from testingfrom testing Currently this regression is blocking the migration of linux-latest to testing [1], but I'll tell the migration software to ignore this failure, as it seems to me that your autopkgtest is broken when it is tested in our migration setup with a different linux-latest the two suites that are tested together. I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from linux-latest/106. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=linux-latest https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemtap/2720472/log.gz autopkgtest [08:11:28]: test build-hello: [--- Checking "/lib/modules/5.2.0-2-amd64 4.19.0-5-amd64/build/.config" failed with error: No such file or directory Tip: /usr/share/doc/systemtap/README.Debian should help you get started. autopkgtest [08:11:28]: test build-hello: ---] and autopkgtest [08:11:32]: test list-coreutils-probe-points: [--- Checking "/lib/modules/5.2.0-2-amd64 4.19.0-5-amd64/build/.config" failed with error: No such file or directory Tip: /usr/share/doc/systemtap/README.Debian should help you get started. autopkgtest [08:11:32]: test list-coreutils-probe-points: ---] signature.asc Description: OpenPGP digital signature
Bug#932649: marked as done (swauth: (build-)depends on cruft package.)
Your message dated Tue, 13 Aug 2019 19:28:52 + with message-id and subject line Bug#934672: Removed package(s) from unstable has caused the Debian Bug report #932649, regarding swauth: (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.) -- 932649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: swauth Severity: serious Tags: bullseye, sid swauth (build-)depends on the python-swiftclient binary package which is no longer built by the python-swiftclient source package. You probably need to migrate to python3 --- End Message --- --- Begin Message --- Version: 1.3.0-2+rm Dear submitter, as the package swauth has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/934672 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#933524: marked as done (python-libpcap: fails to install: Sorry: IndentationError: expected an indented block (pcap.py, line 115))
Your message dated Tue, 13 Aug 2019 19:26:57 + with message-id and subject line Bug#934582: Removed package(s) from unstable has caused the Debian Bug report #933524, regarding python-libpcap: fails to install: Sorry: IndentationError: expected an indented block (pcap.py, line 115) 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.) -- 933524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-libpcap Version: 0.6.4-1 Severity: serious Tags: sid bullseye User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python-libpcap (0.6.4-1+b1) ... Sorry: IndentationError: expected an indented block (pcap.py, line 115) dpkg: error processing package python-libpcap (--configure): installed python-libpcap package post-installation script subprocess returned error exit status 101 Processing triggers for libc-bin (2.28-10) ... Errors were encountered while processing: python-libpcap cheers, andreas python-libpcap_0.6.4-1+b1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 0.6.4-1+rm Dear submitter, as the package python-libpcap has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/934582 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#934709: v4l2loopback: autopkgtest fails when there is a new version of linux-latest
Source: v4l2loopback Version: 0.12.1-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: issue Control: affects -1 src:linux-latest Dear maintainers, With a recent upload of linux-latest the autopkgtest of v4l2loopback fails in testing when that autopkgtest is run with the binary packages of linux-latest from unstable. It passes when run with only packages from testing. In tabular form: passfail linux-latest from testing106 v4l2loopback from testing0.12.1-1 versioned deps [0] from testingfrom unstable all others from testingfrom testing Currently this regression is blocking the migration of linux-latest to testing [1], but I'll tell the migration software to ignore this failure, as it seems to me that your package is broken when the latest linux kernel isn't equal to the kernel running your test. I copied some of the output at the bottom of this report. For your first test, if this really can't be fixed and this installation is supposed to fail, I suggest you mark the first test with the skip-not-installable restriction. Maybe the second test should be marked as skippable as well (I don't know, but you'll need to make it exit with code 77 in the skippable situation). More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from linux-latest/106. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=linux-latest https://ci.debian.net/data/autopkgtest/testing/amd64/v/v4l2loopback/2720576/log.gz Setting up v4l2loopback-dkms (0.12.1-1) ... Loading new v4l2loopback-0.12.1 DKMS files... It is likely that 4.9.0-8-amd64 belongs to a chroot's host Building for 5.2.0-2-amd64 Building initial module for 5.2.0-2-amd64 Error! Bad return status for module build on kernel: 5.2.0-2-amd64 (x86_64) Consult /var/lib/dkms/v4l2loopback/0.12.1/build/make.log for more information. dpkg: error processing package v4l2loopback-dkms (--configure): installed v4l2loopback-dkms package post-installation script subprocess returned error exit status 10 Setting up linux-headers-5.2.0-2-amd64 (5.2.7-1) ... /etc/kernel/header_postinst.d/dkms: Error! Bad return status for module build on kernel: 5.2.0-2-amd64 (x86_64) Consult /var/lib/dkms/v4l2loopback/0.12.1/build/make.log for more information. dpkg: dependency problems prevent configuration of autopkgtest-satdep: autopkgtest-satdep depends on v4l2loopback-dkms; however: Package v4l2loopback-dkms is not configured yet. dpkg: error processing package autopkgtest-satdep (--configure): dependency problems - leaving unconfigured Setting up linux-headers-amd64 (5.2+106) ... Processing triggers for systemd (241-7) ... Processing triggers for libc-bin (2.28-10) ... Errors were encountered while processing: v4l2loopback-dkms autopkgtest-satdep E: Sub-process /usr/bin/dpkg returned an error code (1) and: # Build modules /usr/bin/make -C /usr/src/modules/v4l2loopback v4l2loopback \ KERNEL_DIR=/usr/src/linux-headers-5.2.0-2-amd64 KERNEL_VERSION=5.2.0-2-amd64 KERNELCONF=/usr/src/linux-headers-5.2.0-2-amd64/.config make[2]: Entering directory '/usr/src/modules/v4l2loopback' Building v4l2-loopback driver... /usr/bin/make -C /usr/src/linux-headers-5.2.0-2-amd64 M=/usr/src/modules/v4l2loopback modules make[3]: Entering directory '/usr/src/linux-headers-5.2.0-2-amd64' CC [M] /usr/src/modules/v4l2loopback/v4l2loopback.o /usr/src/modules/v4l2loopback/v4l2loopback.c: In function ‘vidioc_qbuf’: /usr/src/modules/v4l2loopback/v4l2loopback.c:1509:4: error: implicit declaration of function ‘v4l2_get_timestamp’; did you mean ‘v4l2_get_subdevdata’? [-Werror=implicit-function-declaration] v4l2_get_timestamp(>buffer.timestamp); ^~ v4l2_get_subdevdata cc1: some warnings being treated as errors make[6]: *** [/usr/src/linux-headers-5.2.0-2-common/scripts/Makefile.build:290: /usr/src/modules/v4l2loopback/v4l2loopback.o] Error 1 make[5]: *** [/usr/src/linux-headers-5.2.0-2-common/Makefile:1610: _module_/usr/src/modules/v4l2loopback] Error 2 make[4]: *** [Makefile:179: sub-make] Error 2 make[3]: *** [Makefile:8: all] Error 2 make[3]: Leaving directory '/usr/src/linux-headers-5.2.0-2-amd64' make[2]: *** [Makefile:43: v4l2loopback.ko] Error 2 make[2]: Leaving directory '/usr/src/modules/v4l2loopback' make[1]: *** [debian/rules:17: binary-modules] Error 2 make[1]: Leaving directory '/usr/src/modules/v4l2loopback' make: *** [/usr/share/modass/include/common-rules.make:56: kdist_build] Error 2 tput: No value for $TERM and no
Processed: v4l2loopback: autopkgtest fails when there is a new version of linux-latest
Processing control commands: > affects -1 src:linux-latest Bug #934709 [src:v4l2loopback] v4l2loopback: autopkgtest fails when there is a new version of linux-latest Added indication that 934709 affects src:linux-latest -- 934709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#839608: marked as done (python-application: keep out of stretch for now)
Your message dated Tue, 13 Aug 2019 19:22:30 + with message-id and subject line Bug#934568: Removed package(s) from unstable has caused the Debian Bug report #839608, regarding python-application: keep out of stretch for now 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.) -- 839608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-application Version: 1.4.1-1 Severity: serious See #838818 for details. -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F --- End Message --- --- Begin Message --- Version: 1.4.1-1+rm Dear submitter, as the package python-application has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/934568 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#896331: marked as done (python-simpleparse-mxtexttools: simpleparse.stt.TextTools.mxTextTools fails to import)
Your message dated Tue, 13 Aug 2019 19:18:33 +
with message-id
and subject line Bug#934560: Removed package(s) from unstable
has caused the Debian Bug report #896331,
regarding python-simpleparse-mxtexttools: simpleparse.stt.TextTools.mxTextTools
fails to import
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.)
--
896331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-simpleparse-mxtexttools
Version: 2.2.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-simpleparse-mxtexttools importing the module
simpleparse.stt.TextTools.mxTextTools
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named simpleparse.stt.TextTools.mxTextTools
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Version: 2.2.0-1+rm
Dear submitter,
as the package simpleparse has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/934560
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#755625: marked as done (python-django-extdirect: Please ensure it works with Django 1.7)
Your message dated Tue, 13 Aug 2019 19:18:59 + with message-id and subject line Bug#934561: Removed package(s) from unstable has caused the Debian Bug report #755625, regarding python-django-extdirect: Please ensure it works with Django 1.7 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.) -- 755625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-django-extdirect Version: 0.9-1 Severity: important User: python-dja...@packages.debian.org Usertags: django17 Hello, your package python-django-extdirect depends on python-django. As you might know, Django 1.7 will be soon available and as each new upstream major version, it brings many changes, some of them which are backwards incompatible (after a deprecation period covering 2 major versions): https://docs.djangoproject.com/en/1.7/releases/1.7/ https://docs.djangoproject.com/en/1.7/releases/1.7/#backwards-incompatible-changes-in-1-7 We intend to upload Django 1.7 to unstable as soon as it is available because we really want the latest version in jessie and the freeze is approaching fast. In preparation of that, I have uploaded a release candidate in experimental. Please test your package against Django 1.7 in experimental. If a new upstream version of your package is required, please package it now. If you can't upload it to unstable because it only works with Django 1.7, feel free to upload it to experimental too. If the current package works fine, please close this bug (or retitle it as a suggestion to implement Python 3 support and drop its severity to wishlist[1]). If it's broken, please tag it as confirmed. If it's not broken, but would benefit from further work, please tag it as confirmed but reduce the severity. If you have experimental in your sources.list you can install the latest version easily: $ sudo apt-get install -t experimental python-django python3-django [1] We have recently added Python 3 support with the addition of python3-django. Consider doing the same if your package is a Django application/library. Thank you for your help! PS: I will raise the "confirmed" bugs that are still of severity "important" to "serious" once we upload Django 1.7 to unstable. --- End Message --- --- Begin Message --- Version: 0.10-1+rm Dear submitter, as the package python-django-extdirect has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/934561 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#752101: marked as done (python-django-piston: Missing dependencies)
Your message dated Tue, 13 Aug 2019 19:16:06 + with message-id and subject line Bug#934555: Removed package(s) from unstable has caused the Debian Bug report #752101, regarding python-django-piston: Missing dependencies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 752101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-django-piston Version: 0.2.3-2 Looks like with the bump from 0.2.2-1 to 0.2.3-2 some required dependencies were lost. Specifically: python-django python-oauth python-decorator python-support Thanks, Greg --- End Message --- --- Begin Message --- Version: 0.2.3-2+rm Dear submitter, as the package python-django-piston has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/934555 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#755584: marked as done (django-adminaudit: Please ensure it works with Django 1.7)
Your message dated Tue, 13 Aug 2019 19:13:20 + with message-id and subject line Bug#934548: Removed package(s) from unstable has caused the Debian Bug report #755584, regarding django-adminaudit: Please ensure it works with Django 1.7 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.) -- 755584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: django-adminaudit Version: 0.3.3-1 Severity: important User: python-dja...@packages.debian.org Usertags: django17 Hello, your package django-adminaudit depends on python-django. As you might know, Django 1.7 will be soon available and as each new upstream major version, it brings many changes, some of them which are backwards incompatible (after a deprecation period covering 2 major versions): https://docs.djangoproject.com/en/1.7/releases/1.7/ https://docs.djangoproject.com/en/1.7/releases/1.7/#backwards-incompatible-changes-in-1-7 We intend to upload Django 1.7 to unstable as soon as it is available because we really want the latest version in jessie and the freeze is approaching fast. In preparation of that, I have uploaded a release candidate in experimental. Please test your package against Django 1.7 in experimental. If a new upstream version of your package is required, please package it now. If you can't upload it to unstable because it only works with Django 1.7, feel free to upload it to experimental too. If the current package works fine, please close this bug (or retitle it as a suggestion to implement Python 3 support and drop its severity to wishlist[1]). If it's broken, please tag it as confirmed. If it's not broken, but would benefit from further work, please tag it as confirmed but reduce the severity. If you have experimental in your sources.list you can install the latest version easily: $ sudo apt-get install -t experimental python-django python3-django [1] We have recently added Python 3 support with the addition of python3-django. Consider doing the same if your package is a Django application/library. Thank you for your help! PS: I will raise the "confirmed" bugs that are still of severity "important" to "serious" once we upload Django 1.7 to unstable. --- End Message --- --- Begin Message --- Version: 0.3.3-2+rm Dear submitter, as the package django-adminaudit has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/934548 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#866471: marked as done (python-trml2pdf: depends on obsolete python-imaging (replace with python3-pil or python-pil))
Your message dated Tue, 13 Aug 2019 19:12:57 + with message-id and subject line Bug#934547: Removed package(s) from unstable has caused the Debian Bug report #866471, regarding python-trml2pdf: depends on obsolete python-imaging (replace with python3-pil or python-pil) 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.) -- 866471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-trml2pdf Version: 1.2-3 Severity: important Tags: sid buster User: d...@debian.org Usertags: imaging-pillow One or more binary packages built from this source depends on or recommends python-imaging, which is obsolete for some years now. Please build the source using the python-pil package. If your package doesn't need to be built with Python2, please consider using Python3 and depend on python3-pil. Planning to remove python-imaging for the buster release, so the severity of this issues might be raised. --- End Message --- --- Begin Message --- Version: 1.2-3+rm Dear submitter, as the package python-trml2pdf has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/934547 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 695873 serious Bug #695873 [memtest86+] memtest86+: Serial console does not work Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 695873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934708: gitlab: CVE-2019-14942 CVE-2019-14944 (GitLab Critical Security Release: 12.1.6, 12.0.6, and 11.11.8)
Source: gitlab Version: 11.8.10+dfsg-1 Severity: grave Tags: security upstream Justification: user security hole Hi, The following vulnerabilities were published for gitlab, another round of gitlab issues. Where this time only two CVE are affecting the versions present in Debian. CVE-2019-14942[0]: Insecure Cookie Handling on GitLab Pages CVE-2019-14944[1]: Multiple Command-Line Flag Injection Vulnerabilities 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-2019-14942 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14942 [1] https://security-tracker.debian.org/tracker/CVE-2019-14944 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14944 [2] https://about.gitlab.com/2019/08/12/critical-security-release-gitlab-12-dot-1-dot-6-released/ Regards, Salvatore
Bug#932584: Please help fix pydoctor
Hi, On Sun, Jul 28, 2019 at 02:00:56PM +0100, Ian Jackson wrote: > Hi, Python folks. > > I think help is needed regarding > > #932584 python-pydoctor: Epydoc will be removed > > It seems to be languishing rather. What I don't understand is why > pydoctor depends on epydoc given that, in the words of the > Description: > > [Pydoctor] was written primarily to replace epydoc ... > > I had a quick look through the source but I don't know enough about > pydoctor to make immediate sense of the results of my grep. Maybe > some person who knows more about pydoctor can help ? > > (I'm CCing this to the gbp maintainers because this came to my > attention due to an autoremoval bug where a package of mine has a > dependency chain via gbp.) epydoc only seems to be used for formatting and README.Debian confirms this: ...and looking at the bug it seems it was already dealt with by dropping the epydoc dependency. Thanks! -- Guido > > Thanks, > Ian. > > -- > Ian JacksonThese opinions are my own. > > If I emailed you from an address @fyvzl.net or @evade.org.uk, that is > a private address which bypasses my fierce spamfilter. >
Bug#934673: libgit2-glib ftbfs with meson.build:148:2: ERROR: Assert failed: libgit2 ssh support was requested, but not found. Use -Dssh=false to build without it
On 2019, ഓഗസ്റ്റ് 13 4:37:35 PM IST, Simon McVittie wrote:
>On Tue, 13 Aug 2019 at 14:14:01 +0530, Pirate Praveen wrote:
>> When building with sbuild,
>
>Is ccache preinstalled in the chroot you used?
Yes.
>> #include
>> int
>> main(int argc, const char *argv[])
>> {
>> git_libgit2_init ();
>> return ((git_libgit2_features() & GIT_FEATURE_SSH) != 0)
>? 0
>> : 1;
>> }
>
>If you compile this small program yourself, does it work and exit 0?
I will try it later and confirm.
>> Compiler stderr:
>> ccache: error: Failed to create directory
>> /sbuild-nonexistent/.ccache/tmp: Permission denied
>
>If my guess about the root cause is correct, then this will affect
>every
>package that builds with Meson and does not reset HOME in its packaging
>(but many GNOME packages need a working HOME for their build-time
>tests,
>so they reset it in debian/rules, as seen in for example glib2.0).
Yes, makes sense, #933799 is also the same issue.
>Perhaps Meson should not automatically use ccache if $HOME is not
>writeable, or perhaps the dh build system for Meson should explicitly
>disable it in this situation.
Yes, this should be fixed at dh level.
>smcv
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#933799: geary FTBFS - ERROR: Problem encountered: SQLite3 is missing FTS3 tokenizer support
On Sat, 03 Aug 2019 21:10:48 +0530 Pirate Praveen wrote: > Package: geary > version: 3.32.0-1 > Severity: serious > > I tried building in both buster and sid, both builds failed. Built with > an uptodate chroot using sbuild. > > Header has symbol "SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER" > with dependency sqlite3: NO > > meson.build:111:2: ERROR: Problem encountered: SQLite3 is missing FTS3 > tokenizer support. Please compile it with -DSQLITE_ENABLE_FTS3. > See https://bugzilla.gnome.org/show_bug.cgi?id=763203 for details. This seems caused by ccache installed in chroot, similar to libgit2-glib bug #934673 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#934441: marked as done (python-etcd3gw (build-)depends on cruft package.)
Your message dated Tue, 13 Aug 2019 16:20:26 + with message-id and subject line Bug#934441: fixed in python-etcd3gw 0.2.1-2 has caused the Debian Bug report #934441, regarding python-etcd3gw (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.) -- 934441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-etcd3gw Version: 0.2.1-1 Severity: serious Tags: patch, bullseye, sid python-etcd3gw (build-)depends on the python-futurist binary package which is no longer built by the corresponding source package. It's probably time to drop python 2 support from this package. I notice that ubuntu have already done so, their patch can be found at https://launchpadlibrarian.net/432629348/python-etcd3gw_0.2.1-1_0.2.1-1ubuntu1.diff.gz --- End Message --- --- Begin Message --- Source: python-etcd3gw Source-Version: 0.2.1-2 We believe that the bug you reported is fixed in the latest version of python-etcd3gw, 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 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-etcd3gw package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 13 Aug 2019 17:57:27 +0200 Source: python-etcd3gw Architecture: source Version: 0.2.1-2 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 934441 Changes: python-etcd3gw (0.2.1-2) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https in Format * Removing gbp.conf, not used anymore or should be specified in the developers dotfiles * d/control: Use team+openst...@tracker.debian.org as maintainer * Use debhelper-compat instead of debian/compat. . [ Thomas Goirand ] * Removed Python 2 support (Closes: #934441). Checksums-Sha1: 597b11b7ec50b14038e6a897a095615b66ddab20 2411 python-etcd3gw_0.2.1-2.dsc 57dd3d62b0482dc3f75ed8ac8b77c3790d1b5d41 2364 python-etcd3gw_0.2.1-2.debian.tar.xz 255ae4e1a651eb57df8e412bdb85b50dfbabbb6e 10792 python-etcd3gw_0.2.1-2_amd64.buildinfo Checksums-Sha256: b9efbca3530954a97b46cd385899f08a745bf46c5e398ee68c023991d20851af 2411 python-etcd3gw_0.2.1-2.dsc 0026a237408706097fb44a902fbed93add5ef4ac15028ee86f00a3b9e9509c81 2364 python-etcd3gw_0.2.1-2.debian.tar.xz e4a47cf69f1cce18de58760abb3759b92dc8f6fabcb4795507c5b947098a35c9 10792 python-etcd3gw_0.2.1-2_amd64.buildinfo Files: 2a37f9d4343340fb22364ea1c7aac3da 2411 python optional python-etcd3gw_0.2.1-2.dsc 8fced34c6736a17144b895e3855652b0 2364 python optional python-etcd3gw_0.2.1-2.debian.tar.xz 7dd97427b4419355f1613533bf6b1a0f 10792 python optional python-etcd3gw_0.2.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl1S3tkACgkQ1BatFaxr Q/6b1xAAkJZZaewjMsk0wKmayyZuAwu1sEKy4rAKrhH/TcbucYLSZe0l+ecvbNdU LWn2WlFLHLX4LDsrWQHM0ci8M8P2uq0BCELQvIpvzHtkZFLMeQLsSFcTaIqHVLNe 8nVn/Z3rqmKoHhc41W9MAhvHLQcJ9ADVwskn2zPGV+YBQNOCkj08gMF1+YrdfU0q nvwJ931aZJKXoFWsdndJYfFnGShZNlgNq2DYFUXDtfNKNtZ7Ux9VWvBdY229nVmw ra69D2U1ecgKKCu82OuyV3k1OBuE8pkFtWNxurCR9rJbeLycViHHxspDsYAu5hcH W8W01J8UYQdp3LLaPb1U3/pZQUa6CjGv6wCSTSBBGXB+u4PdmlW+gbLagW+2TpPP +lfEQVyv9d/JJS527p9iEShoxw5vLUz5248k7U1KDaJVyAEfPCHAUSb/q0O27AhB LaVR5DYxtFaM5hXYr53sXQR9xPNuiFCJ0e8hVVem6PQzMvSRBUPHChap0j/nhUVc Ue+mRi+WqCwKsRGJzPulrI1Hmnr8zW5S3jQhYiBIVHlRxyBtWL0vfXW2Haf5ZA6d 0p1921moPhQHfCKd9cwYoPJodM4yvpd77PSgrdKbxmv0Z7G3CYM7LurDbgOaH4te VVWnBRLPr5ECFTJwM5Roip3E6X63bTubnJXp1bMuGPpfft2cHzg= =II91 -END PGP SIGNATURE End Message ---
Bug#934442: marked as done (python-gabbi (build-)depends on cruft package.)
Your message dated Tue, 13 Aug 2019 16:05:52 + with message-id and subject line Bug#934442: fixed in python-gabbi 1.40.0-5 has caused the Debian Bug report #934442, regarding python-gabbi (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.) -- 934442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python-gabbi Version: 1.40.0-4 Severity: serious Tags: bullseye, sid python-gabbi (build-)depends on the python-jsonpath-rw-ext binary package which is no longer built by the corresponding source package. It's probably time to drop python 2 support from this package. --- End Message --- --- Begin Message --- Source: python-gabbi Source-Version: 1.40.0-5 We believe that the bug you reported is fixed in the latest version of python-gabbi, 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 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-gabbi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 13 Aug 2019 17:45:34 +0200 Source: python-gabbi Architecture: source Version: 1.40.0-5 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 934442 Changes: python-gabbi (1.40.0-5) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Use team+openst...@tracker.debian.org as maintainer * Use debhelper-compat instead of debian/compat. . [ Thomas Goirand ] * Removed Python 2 support (Closes: #934442). Checksums-Sha1: 4a9f8a5204c86561a9e2a3bb9939e8c6b16fd8ef 2372 python-gabbi_1.40.0-5.dsc 32ca2f644e8f43e87f60507e1d7097bb3a715298 4272 python-gabbi_1.40.0-5.debian.tar.xz 3d4558d5e5e5c9fc9d43a0290261f7c450315566 9578 python-gabbi_1.40.0-5_amd64.buildinfo Checksums-Sha256: d933f426c0f0d6407df519af95959a086832170f37c5efcc524cff2502eeb570 2372 python-gabbi_1.40.0-5.dsc a9f4904ca70500b1230241d7c397f01e291dc5bc557fdd062dd8d57025ab8630 4272 python-gabbi_1.40.0-5.debian.tar.xz 257aa0007f0290e531e558daf43d7759298ad3902a6a28a704566866e68f8928 9578 python-gabbi_1.40.0-5_amd64.buildinfo Files: 939c54574a67797e9017f5ef86a3c1fc 2372 python optional python-gabbi_1.40.0-5.dsc c45b1a53fef3bbf35fa6fea2893f2bda 4272 python optional python-gabbi_1.40.0-5.debian.tar.xz 0ce99e437c4308fcfb14debd973c4b89 9578 python optional python-gabbi_1.40.0-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl1S3JEACgkQ1BatFaxr Q/4yOw//YmY8JsqIkpHq8DW/WBrX6C+SSfPtdJjo2gRddRKMebH/vPlKxJrd33w9 CLilkUALD6On1QdJ3udGw6jai9G5BbNnXoV9vUz2j0RrXuTb3VMLL+HvKBef2k5u 3bNu+khMSb21mxbuVwJm/bRe0RokY2rOX7i9WrYGkxEfMdUDICZ8buwGGMQjqBO3 RFkJ4Zui7pXlQKWC1lE3nd+s7ZoSRyyM8FDEwxsfmbztY3TPUd1Tl+JXLu9kIM1X XJufPehpSxxxgnytsfKq2hkQQGF0R8dQ8UETF4BXY3T1XyXZtbMWSxU0zIxKmXG8 at7FABPn/3NOsfBN1UKTAFHlF5orppVfNR447476xdpAAMFiV3bsM03BAmxPBVtS fo8K1rXiMiHUmg+e+km6kKsz8IDh+A8mpu4H6+NNHDNhruhu/s3F4d6kJAMZeBDV tHWxwFov/NYUbf0+J2ujXZbbvYN7+Grd5xy10xbqfL2fWR9nWI27exjRRNDdZ2Qw rvSru2tXIo7qEGo8HEC+y3M99DP2beTs+YV4LocO9CmmuxYj9uxnHB6lZMwnkmyy RUVdu2Tb/9soKzjH84V983HS9af4DNdi1UsCUNS9uI0grWlutoRPG2FpncuVoyga 217wUbTEG1022ATwU153WLkFXRD/VzlDwx3LB97Upv6Gr/gXjKk= =E9RX -END PGP SIGNATURE End Message ---
Processed: Bug#934442 marked as pending in python-gabbi
Processing control commands: > tag -1 pending Bug #934442 [python-gabbi] python-gabbi (build-)depends on cruft package. Added tag(s) pending. -- 934442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934442: marked as pending in python-gabbi
Control: tag -1 pending Hello, Bug #934442 in python-gabbi 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/openstack-team/python/python-gabbi/commit/6a3e62ddf6ba5ba9186b07e01875d4172ed9a83a Removed Python 2 support (Closes: #934442). (this message was generated automatically) -- Greetings https://bugs.debian.org/934442
Processed: Re: alpine: replies lose In-Reply-To and References headers
Processing commands for cont...@bugs.debian.org: > severity 923481 serious Bug #923481 [alpine] alpine: replies lose In-Reply-To and References headers Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 923481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921194: amarok: Amarok depends on libmariadbd18, which doesn't exist any longer
Hi, I'll try to have a look at this and prepare an NMU this weekend to fix this. Cheers! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ signature.asc Description: OpenPGP digital signature
Bug#934691: rekall: maintainer address bounces
Package: rekall Severity: serious x-debbugs-cc: sa...@debian.org x-debbugs-cc: ben...@debian.org While sending https://lists.debian.org/debian-python/2019/08/msg00072.html I got forensics-de...@lists.alioth.debian.org (generated fromrek...@packages.debian.org) host alioth-lists-mx.debian.net [2001:ba8:0:2c77:0:4:0:1] SMTP error from remote mail server after RCPT TO:: 550 Unrouteable address
Bug#933868: grunt should look for tasks in /usr/share/nodejs as well
Control: severity -1 normal Decreasing severity since no stable package installs something in /usr/share/nodejs (apt-file search /usr/share/nodejs returns nothing). Bug exists only for backports and can be workaround using a grunt backport.
Processed: Re: grunt should look for tasks in /usr/share/nodejs as well
Processing control commands:
> severity -1 normal
Bug #933868 {Done: Pirate Praveen } [grunt] grunt should
look for tasks in /usr/share/nodejs as well
Severity set to 'normal' from 'grave'
--
933868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#934687: heudiconv, indirectly build-depends on cruft package, needs to migrate to python 3
Package: heudiconv Severity: serious Version: 0.5.3-1 heudiconv build-depends on the python-datalad binary package which in turn depends on the python-fasteners binary package, which in turn depends on the python-monotonic binary package which is no longer built by the python-monotonic source package. Furthermore Debian's goal for bullseye is to move away from python 2, not to add more new python 2 only packages. Even if python-monotonic gets reinstated I don't think this should migrate to testing in it's current form.
Bug#934511: marked as done (qtbase5-dev fails to coinstall with itself aka Multi-Arch:same violation)
Your message dated Tue, 13 Aug 2019 11:51:38 +
with message-id
and subject line Bug#934215: fixed in qtbase-opensource-src 5.11.3+dfsg1-3
has caused the Debian Bug report #934215,
regarding qtbase5-dev fails to coinstall with itself aka Multi-Arch:same
violation
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.)
--
934215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qtbase5-dev
Version: 5.11.3+dfsg1-2+b1
Severity: important
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:qtwayland-opensource-src
qtbase5-dev fails to coinstall with itself on any of pair of release
architectures. A typical error is:
| Unpacking qtbase5-dev:s390x (5.11.3+dfsg1-2+b1) ...
| Selecting previously unselected package qtbase5-dev:amd64.
| Preparing to unpack .../449-qtbase5-dev_5.11.3+dfsg1-2+b1_amd64.deb ...
| Unpacking qtbase5-dev:amd64 (5.11.3+dfsg1-2+b1) ...
| dpkg: error processing archive
/tmp/apt-dpkg-install-o9TSE3/449-qtbase5-dev_5.11.3+dfsg1-2+b1_amd64.deb
(--unpack):
| trying to overwrite shared
'/usr/share/qt5/doc/global/template/images/Qt-logo.png', which is different
from other instances of package qtbase5-dev:amd64
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
The multiarch hinter reports:
| qtbase5-dev conflicts on 4 files starting with
/usr/share/qt5/doc/global/template/ on any two of amd64, arm64, armel, armhf,
and 6 more
Running diffoscope on that file yields the following:
| $ diffoscope {a,b}/usr/share/qt5/doc/global/template/images/Qt-logo.png
| --- a/usr/share/qt5/doc/global/template/images/Qt-logo.png
| +++ b/usr/share/qt5/doc/global/template/images/Qt-logo.png
| ├── sng
| │ @@ -2,21 +2,21 @@
| │ IHDR {
| │ width: 74; height: 88; bitdepth: 8;
| │ using color alpha;
| │ }
| │ bKGD {red: 255; green: 255; blue: 255;}
| │ pHYs {xpixels: 2835; ypixels: 2835; per: meter;} # (72 dpi)
| │ tIME {
| │ -# 7 Aug 2019 18:06:40 GMT
| │ +# 7 Aug 2019 17:41:15 GMT
| │ year: 2019
| │ month: 8
| │ day:7
| │ -hour: 18
| │ -minute: 6
| │ -second: 40
| │ +hour: 17
| │ +minute: 41
| │ +second: 15
| │ }
| │ IMAGE {
| │ pixels hex
| │
7ec24214 7ec24238 7ec24232 7ec24224
7ec24207
| │
7ec24207 7ec24272 7ec242e5 7ec242ff 7ec242ff 7ec242ff 7ec242ff
7ec242fc 7ec242da 7ec242b0 7ec24286 7ec2425b 7ec24231 7ec24209
| │ 7ec24201
7ec2425b 7ec242df 7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242ff
7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242fd 7ec242dd
7ec242b3 7ec24289 7ec2425f 7ec24235 7ec2420c
| │ 7ec24201 7ec242b3
7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242ff
7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242ff 7ec242ff
7ec242ff 7ec242ff 7ec242ff 7ec242ff
Bug#934215: marked as done (qtbase5-dev: trying to overwrite shared ....png which is different from other instances of the package)
Your message dated Tue, 13 Aug 2019 11:51:38 + with message-id and subject line Bug#934215: fixed in qtbase-opensource-src 5.11.3+dfsg1-3 has caused the Debian Bug report #934215, regarding qtbase5-dev: trying to overwrite shared png which is different from other instances of the 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.) -- 934215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qtbase5-dev Version: 5.11.3+dfsg1-2+b1 Severity: normal Dear Maintainer, during my daily apt upgrade, I got this error: Unpacking qtbase5-dev:i386 (5.11.3+dfsg1-2+b1) over (5.11.3+dfsg1-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-OL1lMs/021-qtbase5-dev_5.11.3+dfsg1-2+b1_i386.deb (--unpack): trying to overwrite shared '/usr/share/qt5/doc/global/template/images/Qt-logo.png', which is different from other instances of package qtbase5-dev:i386 (I have the amd64 and i386 versions installed) I had to use dpkg --force-overwrite to work around it, which showed the additional messages: Preparing to unpack .../qtbase5-dev_5.11.3+dfsg1-2+b1_i386.deb ... Unpacking qtbase5-dev:i386 (5.11.3+dfsg1-2+b1) over (5.11.3+dfsg1-2) ... dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite shared '/usr/share/qt5/doc/global/template/images/Qt-logo.png', which is different from other instances of package qtbase5-dev:i386 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite shared '/usr/share/qt5/doc/global/template/images/ico_out.png', which is different from other instances of package qtbase5-dev:i386 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite shared '/usr/share/qt5/doc/global/template/style/list_arrow.png', which is different from other instances of package qtbase5-dev:i386 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite shared '/usr/share/qt5/doc/global/template/style/list_expand.png', which is different from other instances of package qtbase5-dev:i386 Usually, for a multiarch issue, the +b1 in the version number would make me suspicious, but maybe not here, the image seems to contain a creation time. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: qtbase-opensource-src Source-Version: 5.11.3+dfsg1-3 We believe that the bug you reported is fixed in the latest version of qtbase-opensource-src, 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 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated qtbase-opensource-src package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Aug 2019 14:21:20 +0300 Source: qtbase-opensource-src Architecture: source Version: 5.11.3+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Closes: 934215 Changes: qtbase-opensource-src (5.11.3+dfsg1-3) unstable; urgency=medium . * Tell dh_strip_nondeterminism to ignore .png files (closes: #934215). * Update symbols files from buildds’ logs. Checksums-Sha1: 5a86fd1ac537925df19b067113e9842d758c9359 5174 qtbase-opensource-src_5.11.3+dfsg1-3.dsc 452135ccfb5ab360baa81fe5d1a85113fa2728e7 240032 qtbase-opensource-src_5.11.3+dfsg1-3.debian.tar.xz a25ce53eda9bf53cf888783ecbfcc11ea4357ce2 17784 qtbase-opensource-src_5.11.3+dfsg1-3_source.buildinfo
Bug#934265: marked as done (qtbase5-dev: different archs ship different version of Qt-logo.png)
Your message dated Tue, 13 Aug 2019 11:51:38 + with message-id and subject line Bug#934215: fixed in qtbase-opensource-src 5.11.3+dfsg1-3 has caused the Debian Bug report #934215, regarding qtbase5-dev: different archs ship different version of Qt-logo.png 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.) -- 934215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qtbase5-dev Version: 5.11.3+dfsg1-2+b1 Severity: serious Unpacking qtbase5-dev:i386 (5.11.3+dfsg1-2+b1) over (5.11.3+dfsg1-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-01jgzV/14-qtbase5-dev_5.11.3+dfsg1-2+b1_i386.deb (--unpack): trying to overwrite shared '/usr/share/qt5/doc/global/template/images/Qt-logo.png', which is different from other instances of package qtbase5-dev:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) --- End Message --- --- Begin Message --- Source: qtbase-opensource-src Source-Version: 5.11.3+dfsg1-3 We believe that the bug you reported is fixed in the latest version of qtbase-opensource-src, 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 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated qtbase-opensource-src package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Aug 2019 14:21:20 +0300 Source: qtbase-opensource-src Architecture: source Version: 5.11.3+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Closes: 934215 Changes: qtbase-opensource-src (5.11.3+dfsg1-3) unstable; urgency=medium . * Tell dh_strip_nondeterminism to ignore .png files (closes: #934215). * Update symbols files from buildds’ logs. Checksums-Sha1: 5a86fd1ac537925df19b067113e9842d758c9359 5174 qtbase-opensource-src_5.11.3+dfsg1-3.dsc 452135ccfb5ab360baa81fe5d1a85113fa2728e7 240032 qtbase-opensource-src_5.11.3+dfsg1-3.debian.tar.xz a25ce53eda9bf53cf888783ecbfcc11ea4357ce2 17784 qtbase-opensource-src_5.11.3+dfsg1-3_source.buildinfo Checksums-Sha256: a2164536f00bd2a27aafd3670e8cbc0f5dfa2e92ae3e60d15aa240b5325f6f82 5174 qtbase-opensource-src_5.11.3+dfsg1-3.dsc a301cf953c7ab5e4a6fd018bca760d70b8f2b4c1fe942cb7e4b2dbddac820e13 240032 qtbase-opensource-src_5.11.3+dfsg1-3.debian.tar.xz a4e56a0c0bab496b2215243ee6893e7d039dd53eed522beb5fc64c7cfba284a6 17784 qtbase-opensource-src_5.11.3+dfsg1-3_source.buildinfo Files: 23f7257b957a6308fcd62c1dd7fd54fb 5174 libs optional qtbase-opensource-src_5.11.3+dfsg1-3.dsc 326334bdfa1c75d12841a08fcff5a8ad 240032 libs optional qtbase-opensource-src_5.11.3+dfsg1-3.debian.tar.xz 5572dd5599d7fce57681cc383bde98c2 17784 libs optional qtbase-opensource-src_5.11.3+dfsg1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE8kKZ/xu8kBi5BqTLYCaTbS8ciuAFAl1Sni8THG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBgJpNtLxyK4HmMEACRAEHm5DcyUsUnNv8KHI6+FDYU83mx eQejBu0ct6z0MrIPKfhQiZpZZzCCgTufUnE1mIju4v8EuLGakaXm3W0tgqvrnHjC hmDS6LWcOlDrVtMr+djsSTSdeSdVE44djddtFeW6iJSTudpVz/3blgYHH2QttqNX 7YK+iTVXLzWDnKm2V0qrW5uH1dgHV5kB1WtWysqt6BszM/NucK4MkdJlEhfclSLj 8/RtpUVwtLdQya1B77JTTVa5UnCyFcoY+FME+f+wDwHVmw0c5aclTQGE/uKznt0n yNMu2lIgayZ3LC2gIu8dKODg8GMhXvZ7yxsPW36xTm9GwxGIGqfs05kwktePMx1/ 5DHfvUI2O2PD8CfrdY0Sej+MF0axyoiECBPvkWRBzIIKy0uEY+MyhNnFi+5DYXjS MN6ykUJqJSJYZb0JebUTLxBz5llkx3PMyPdljvSEGumZN6FCnNktkQDESlS3SD7f YHr2nE9kN+D4gKtbp6lZhjivzF9AfCYl4ovJipFnsDTspuKI5nH2s+bVxZtt/aiI jGquQFEHue6EwxbAf3eWH+6LjhqlktJ+hewhpGXXIB/Ku+4cjJs7VfDkGvflB6n2 HWPPVI/knxIyfonVw3UKirDk494K0dMy/6mb5gVeaRK0yke8jdgRZob1xSopbdfS T7OIZVUEirHTmQ== =pxgC -END PGP SIGNATURE End Message ---
Processed: Bug#934215 marked as pending in qtbase-opensource-src
Processing control commands: > tag -1 pending Bug #934215 [qtbase5-dev] qtbase5-dev: trying to overwrite shared png which is different from other instances of the package Bug #934265 [qtbase5-dev] qtbase5-dev: different archs ship different version of Qt-logo.png Bug #934511 [qtbase5-dev] qtbase5-dev fails to coinstall with itself aka Multi-Arch:same violation Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. -- 934215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934215 934265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934265 934511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934215: marked as pending in qtbase-opensource-src
Control: tag -1 pending Hello, Bug #934215 in qtbase-opensource-src 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/qt-kde-team/qt/qtbase/commit/7e8731cd5616d47b29e7b2b6ed48809f26601806 Tell dh_strip_nondeterminism to ignore .png files. Also call it with --verbose flag to see what files are changed. Closes: #934215. (this message was generated automatically) -- Greetings https://bugs.debian.org/934215
Bug#934673: libgit2-glib ftbfs with meson.build:148:2: ERROR: Assert failed: libgit2 ssh support was requested, but not found. Use -Dssh=false to build without it
On Tue, 13 Aug 2019 at 14:14:01 +0530, Pirate Praveen wrote:
> When building with sbuild,
Is ccache preinstalled in the chroot you used?
> #include
> int
> main(int argc, const char *argv[])
> {
> git_libgit2_init ();
> return ((git_libgit2_features() & GIT_FEATURE_SSH) != 0) ? 0
> : 1;
> }
If you compile this small program yourself, does it work and exit 0?
> Compiler stderr:
> ccache: error: Failed to create directory
> /sbuild-nonexistent/.ccache/tmp: Permission denied
If my guess about the root cause is correct, then this will affect every
package that builds with Meson and does not reset HOME in its packaging
(but many GNOME packages need a working HOME for their build-time tests,
so they reset it in debian/rules, as seen in for example glib2.0).
Perhaps Meson should not automatically use ccache if $HOME is not
writeable, or perhaps the dh build system for Meson should explicitly
disable it in this situation.
smcv
Bug#929406: marked as done (hdf5: libhdf5-*103-1 missing Breaks+Replaces: libhdf5-*103)
Your message dated Tue, 13 Aug 2019 10:49:34 + with message-id and subject line Bug#929406: fixed in hdf5 1.10.5+repack-1~exp7 has caused the Debian Bug report #929406, regarding hdf5: libhdf5-*103-1 missing Breaks+Replaces: libhdf5-*103 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.) -- 929406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libhdf5-103-1,libhdf5-cpp-103-1,libhdf5-mpich-103-1,libhdf5-mpich-cpp-103-1,libhdf5-openmpi-103-1,libhdf5-openmpi-cpp-103-1 Version: 1.10.5+repack-1~exp6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'experimental' to 'experimental'. It installed fine in 'experimental', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package libhdf5-103-1:amd64. Preparing to unpack .../libhdf5-103-1_1.10.5+repack-1~exp6_amd64.deb ... Unpacking libhdf5-103-1:amd64 (1.10.5+repack-1~exp6) ... dpkg: error processing archive /var/cache/apt/archives/libhdf5-103-1_1.10.5+repack-1~exp6_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libhdf5_serial.so.103.1.0', which is also in package libhdf5-103:amd64 1.10.5+repack-1~exp5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libhdf5-103-1_1.10.5+repack-1~exp6_amd64.deb Selecting previously unselected package libhdf5-openmpi-103-1:amd64. Preparing to unpack .../libhdf5-openmpi-103-1_1.10.5+repack-1~exp6_amd64.deb ... Unpacking libhdf5-openmpi-103-1:amd64 (1.10.5+repack-1~exp6) ... dpkg: error processing archive /var/cache/apt/archives/libhdf5-openmpi-103-1_1.10.5+repack-1~exp6_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libhdf5_openmpi.so.103', which is also in package libhdf5-openmpi-103:amd64 1.10.4+repack-10 Selecting previously unselected package libhdf5-openmpi-cpp-103-1:amd64. Preparing to unpack .../libhdf5-openmpi-cpp-103-1_1.10.5+repack-1~exp6_amd64.deb ... Unpacking libhdf5-openmpi-cpp-103-1:amd64 (1.10.5+repack-1~exp6) ... dpkg: error processing archive /var/cache/apt/archives/libhdf5-openmpi-cpp-103-1_1.10.5+repack-1~exp6_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libhdf5_openmpi_cpp.so.103.1.0', which is also in package libhdf5-openmpi-cpp-103:amd64 1.10.5+repack-1~exp5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libhdf5-openmpi-103-1_1.10.5+repack-1~exp6_amd64.deb /var/cache/apt/archives/libhdf5-openmpi-cpp-103-1_1.10.5+repack-1~exp6_amd64.deb I didn't check all failures, but I assume it's the same problem in all packages. cheers, Andreas libhdf5-openmpi-cpp-103=1.10.5+repack-1~exp5_libhdf5-openmpi-cpp-103-1=1.10.5+repack-1~exp6.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: hdf5 Source-Version: 1.10.5+repack-1~exp7 We believe that the bug you reported is fixed in the latest version of hdf5, 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 929...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gilles Filippini (supplier of updated hdf5 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Aug 2019 11:58:38 +0200 Source: hdf5 Architecture: source Version: 1.10.5+repack-1~exp7 Distribution: experimental Urgency: medium Maintainer: Debian GIS Project Changed-By: Gilles Filippini Closes: 929406 933850 Changes: hdf5 (1.10.5+repack-1~exp7) experimental; urgency=medium . [ Gilles Filippini ] * Add missing Breaks + Replaces to libhdf5-*103-1 (closes: #929406) * Update symbols file for
Bug#933002: docker.io: CVE-2019-13139
Hi On Tue, Aug 13, 2019 at 11:31:41AM +0200, Arnaud Rebillout wrote: > This is fixed in unstable. Thanks! > Question from a non-experienced DM: what's the procedure to get this > into stable? It seems that I shouldn't file a bug to release.debian.org, > and instead get in touch with the security team. > > What's the workflow? Should I file a bug against the pseudo-package > security.debian.org? Or should I just follow up on this bug and CC security? This one is marked as no-dsa. But if something is not yet marked it can as well mean we simply have not assessed it for buster or stretch. Feel free to CC the security team alias when unsure. For getting packages via a point release there are some steps outlined here: https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#upload-stable When involving security some guidelines are given at https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#s5.6.4 and https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#bug-security . Hope this helps! Regards, Salvatore
Bug#933220: siridb-server: missing source for Release/makefile
Hi Paul, The SiriDB project once started by using the Eclipse IDE which generates the make-files and adds the "Auto generated.." comments. Since the project is ejected from Eclipse we can now simply remove the comments and make future changes by hand. (This does not happen a lot, so changes are relative easy to maintain). Kind regards, Jeroen On Sun, Jul 28, 2019 at 10:51 AM Paul Gevers wrote: > Hi Helmut, > > On 27-07-2019 18:47, Helmut Grohne wrote: > > The Release/makefile starts with: > > > > > > > # Automatically-generated file. Do not edit! > > > > > > > However, I was unable to find the source for the generator. This is a > > DFSG#2 violation. > > Thank you for this report. I'm sure Jeroen, upstream and co-maintainer, > will be able to clarify and fix this quickly. > > I'm slight curious, you're doing QA and found this, or are you actually > interested in siridb-server? > > Paul > >
Bug#933002: docker.io: CVE-2019-13139
This is fixed in unstable. Question from a non-experienced DM: what's the procedure to get this into stable? It seems that I shouldn't file a bug to release.debian.org, and instead get in touch with the security team. What's the workflow? Should I file a bug against the pseudo-package security.debian.org? Or should I just follow up on this bug and CC security? Thanks! Arnaud
Bug#930356: marked as done (CVE-2019-12760)
Your message dated Tue, 13 Aug 2019 09:21:54 + with message-id and subject line Bug#930356: fixed in parso 0.5.1-0.1 has caused the Debian Bug report #930356, regarding CVE-2019-12760 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.) -- 930356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: parso Severity: grave Tags: security Please see https://bugzilla.redhat.com/show_bug.cgi?id=1718212 Patch is at https://gist.github.com/dhondta/f71ae7e5c4234f8edfd2f12503a5dcc7 Cheers, Moritz --- End Message --- --- Begin Message --- Source: parso Source-Version: 0.5.1-0.1 We believe that the bug you reported is fixed in the latest version of parso, 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 930...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated parso 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: Mon, 29 Jul 2019 10:12:25 +0200 Source: parso Architecture: source Version: 0.5.1-0.1 Distribution: unstable Urgency: medium Maintainer: Piotr Ożarowski Changed-By: Georges Khaznadar Closes: 930356 Changes: parso (0.5.1-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release. Closes: #930356 Checksums-Sha1: 81853102a04d9c2f0117c15fbdf683849264e3e4 1980 parso_0.5.1-0.1.dsc 24ce8b1641d71580e93f587250375e3d9552b340 391247 parso_0.5.1.orig.tar.gz b2d5c9549dbb2ae6e0cc5c4b07f2ec0091dc67d6 4916 parso_0.5.1-0.1.debian.tar.xz b34d05641181a68363bf5726402210ecbf71102f 7421 parso_0.5.1-0.1_source.buildinfo Checksums-Sha256: 17ccce45aac15d07a477333f54e06496636afc8642f407f9ad7d1b7085274540 1980 parso_0.5.1-0.1.dsc 666b0ee4a7a1220f65d367617f2cd3ffddff3e205f3f16a0284df30e774c2a9c 391247 parso_0.5.1.orig.tar.gz fec55541bcc5ddb41ed7910008320897084168e22237b0c396a6593b97ad57b2 4916 parso_0.5.1-0.1.debian.tar.xz 472c3169ec33657aa792a880776e9b9da4f0d3e4535c34fee1705ecddd048d08 7421 parso_0.5.1-0.1_source.buildinfo Files: ccf13f716d9d678649478559083610e2 1980 python optional parso_0.5.1-0.1.dsc cfdc0d7ce446ac3984cd7ef3e5850354 391247 python optional parso_0.5.1.orig.tar.gz a66b1c8c27c75f73d236f54388af1e5c 4916 python optional parso_0.5.1-0.1.debian.tar.xz 79065c51fe45824d0adb03e8c5aec92d 7421 python optional parso_0.5.1-0.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAl0+rOoUHGdlb3JnZXNr QGRlYmlhbi5vcmcACgkQHCgWkHE2rjlucw//d7v/QshbqbBxB5NuW5cBxv9aK+PS lAMY2QmxAxp0Ct6czthBJu/JsRNAViWkJ+uebPhFuWPx4I7N4QobCw3PvMV3Cy87 uHTp9MclraAe5E9PJskFgI/GGvSQDtBwZEOPq5FEiFNy7+g7sOaI9MXYTk8ejaqS jexjes5kyHP2Zxuw4fHzC4HHedv6RTY2Zv3cNJZC5sjVQIGgZcQttHsdAkoVTrEW vZ6vqpIV+pTwy0yupslxSuZsjkkUGsOStMzFxWpZ+6TKUARXVn+lnjsiHczkvv94 NYeCZDtp+z3bkOV487lsqKzNjGR5LWYOSaTKfs6jNNPsbXeYswUwi2faRvP4czwA sPUHE337BuomI4VcpNGakoO7jg1nOt9iiKztsgqnvvrAU9gLiMvj770/hmzo7UNI pTGXQ0PrG4HZBek9xyX7flo3ej1hIKR9VsRFMW8IDcSaNqGSrHbAKhGY5KQr4glW qL0U9oYF5vNOc7yjH/nwGJeTUe6LpWnIswjwBEwV9QjEorFiFQOHWBHQG020c4oY ojD2U1TxowlwQQS2c7AIgKmgg2T2obq8+7RNQJAmCV/g+ilPtYkEPZFdzgyLp6FH af+E69Do1Qu70eKi5ocl5pVb0XoHmD/CPjLnnWNF06y3JAFfnt99kOWHydvnyQXS 8EJ93qFNZQIHqHA= =6BL8 -END PGP SIGNATURE End Message ---
Bug#934313: marked as done (gertty: unbuildable in testing due to B-D on python-alembic)
Your message dated Tue, 13 Aug 2019 09:08:12 + with message-id and subject line Bug#934313: fixed in gertty 1.6.0-1 has caused the Debian Bug report #934313, regarding gertty: unbuildable in testing due to B-D on python-alembic 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.) -- 934313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gertty Version: 1.5.0-3 Severity: serious Binary package python-alembic is no longer built from source and has been removed from testing. As a result, gertty is currently unbuildable in testing. Please make gertty build-depend on python3-alembic instead. --- End Message --- --- Begin Message --- Source: gertty Source-Version: 1.6.0-1 We believe that the bug you reported is fixed in the latest version of gertty, 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 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Badia (supplier of updated gertty package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Aug 2019 10:37:47 +0200 Source: gertty Architecture: source Version: 1.6.0-1 Distribution: unstable Urgency: medium Maintainer: Sebastien Badia Changed-By: Sebastien Badia Closes: 934313 Changes: gertty (1.6.0-1) unstable; urgency=medium . * New upstream version 1.6.0 * d/copyright: + Update Source location (according OpenDev migration) * d/control: + wrap-and-sort -f debian/control + Update Homepage location (according OpenDev migration) + Bump debhelper compatibility to 12 + Bump to Standards-Version 4.4.0 (no changes needed) + Fix alembic B-D, Thx Esa! (Closes: #934313) * d/rules: Cleanup rules… and use pybuild * d/tests: Introduce basic testing Checksums-Sha1: 255dec21d0446215c4f88f917d7db71905b25d66 2040 gertty_1.6.0-1.dsc cfbf2151da5526d454cf869149fe88cf5a2f236a 122570 gertty_1.6.0.orig.tar.gz 0b6533002fa1b7130ce98af5d58287b5d3f042ea 4304 gertty_1.6.0-1.debian.tar.xz 320a8e7a25507dd7a38c88159539bd1836e5909e 7280 gertty_1.6.0-1_source.buildinfo Checksums-Sha256: 1a61791c27dc7f0ed5ccdc621e504607d1246737be9462424654e0674dcef2c9 2040 gertty_1.6.0-1.dsc 1c3593d2e6ce53bd84b27d6ac92df4a86d8923afd18b4f4f8e2c979f8a6277df 122570 gertty_1.6.0.orig.tar.gz 6c4b3175c6795fab7ef3459d0a58d6b06d3dd396ad919cf77646542d995b790c 4304 gertty_1.6.0-1.debian.tar.xz 9464d8fa4b00de3efc8b16809f107f1ce72b7be59f7499e262ef3628881405ba 7280 gertty_1.6.0-1_source.buildinfo Files: df3f6ed985dbd1f5392832bc99bdd74b 2040 devel optional gertty_1.6.0-1.dsc eade23548fefcbc68bf8ceb75db1d3a1 122570 devel optional gertty_1.6.0.orig.tar.gz b9b62ad2bb32370560f4056148867ead 4304 devel optional gertty_1.6.0-1.debian.tar.xz 7ee3da44302baad8b33a0ba82283a4a2 7280 devel optional gertty_1.6.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfkPprL9yerPPCIUzhxbORhSkUtgFAl1SeUEACgkQhxbORhSk UtiAUw//SfitJWOwdaGpjTteb9RSXi3TZejbP9UG2owZzz2Q7SzyINK3JBp06E5P NjG+zIRXkfFkYXuJ77tZgJdzbXpnAWxri//SJDESvlAJNq3HoqIVvP0y3YWgi5S1 /+AJ1a3xOKL3QhVrd0awDeaZODcH8vlu/DXZGBUDf5eyYsU11fWD3Uj1lz4MG+Rk U0qtas2eywg4AUuFLPh5F6UlY326/fIl+PM8wgZFYZPFZuszZbAFpZ1APyjnOVaY Gyxn6BYnwyE38JRhpIxbcME6mX7zjPyq8caz2k+ZcsXYea8n0H2lHQ2EED99M6cv mvkV328HNTJrK2wgPVFd1/nO6nmCqhCQzovM7RugN1G61FdsOP5LQhQnF5B2KyVi 1HSkBV8GZGgu6hmml9mC39U56PWa0Q2bA/CxH1B8apu4FhwjL8OVsJEfGx6iFMmI hfjv1iWQcp3DdG+a06yL11dgyCAAtX2dWoevNE2u203dMW9u0ugY/fe9y0CLSIgq WMPVokcyYOKDKKVehKPcKOcYvoBb2AlYZ4yaMv4wwrkYoMsSimYeFD3KxvZpOqH8 yXWo108IfIwqG+zaQBlSFE4EummOOPawi2qTzKzUljd3q3zbDxKTeJblZBzI5/nX UGpR3x1IvB29i9sHCdJWift+JIAXfpdWujJztg6wNmIS0oB+Y5I= =bIe6 -END PGP SIGNATURE End Message ---
Bug#934674: python-os-win: (build-)depends on cruft package.
Package: python-os-win Version: 4.0.0-3 Severity: serious Tags: bullseye Python-os-win in testing (build-)depends on a number of python2 packages that are no longer built by the corresponding source packages. This is already fixed in unstable, by dropping python 2 support, but the unstable version is currently unable to migrate due to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928129
Processed: found 934673 in 0.27.7-1
Processing commands for cont...@bugs.debian.org: > found 934673 0.27.7-1 Bug #934673 [libgit2-glib] libgit2-glib ftbfs with meson.build:148:2: ERROR: Assert failed: libgit2 ssh support was requested, but not found. Use -Dssh=false to build without it There is no source info for the package 'libgit2-glib' at version '0.27.7-1' with architecture '' Unable to make a source version for version '0.27.7-1' Marked as found in versions 0.27.7-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 934673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libgit2-glib ftbfs with meson.build:148:2: ERROR: Assert failed: libgit2 ssh support was requested, but not found. Use -Dssh=false to build without it
Processing control commands: > block 931684 by -1 Bug #931684 [libgit2-glib] libgit2 0.28 transition and libgit2-glib 931684 was not blocked by any bugs. 931684 was not blocking any bugs. Added blocking bug(s) of 931684: 934673 -- 931684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931684 934673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934673: libgit2-glib ftbfs with meson.build:148:2: ERROR: Assert failed: libgit2 ssh support was requested, but not found. Use -Dssh=false to build without it
Package: libgit2-glib
version: 0.27.8-1
severity: serious
Control: block 931684 by -1
When building with sbuild,
Determining dependency 'libgit2' with pkg-config executable
'/usr/bin/pkg-config'
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --modversion libgit2` -> 0
0.27.7
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config --cflags libgit2` -> 0
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config libgit2 --libs` -> 0
-L/usr/lib/x86_64-linux-gnu -lgit2
PKG_CONFIG_PATH:
Called `/usr/bin/pkg-config libgit2 --libs` -> 0
-lgit2
Run-time dependency libgit2 found: YES 0.27.7
Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner)
No VALAFLAGS in the environment, not changing global flags.
No LDFLAGS in the environment, not changing global flags.
Running compile:
Working directory: /tmp/tmprx948as5
Command line: valac /tmp/tmprx948as5/testfile.vala -C
Code:
class MesonSanityCheck : Object { }
Compiler stdout:
Compiler stderr:
Vala compiler for the build machine: valac (valac 0.42.5)
No VALAFLAGS in the environment, not changing global flags.
No LDFLAGS in the environment, not changing global flags.
Using cached compile:
Cached command line: valac /tmp/tmprx948as5/testfile.vala -C
Code:
class MesonSanityCheck : Object { }
Cached compiler stdout:
Cached compiler stderr:
Vala compiler for the host machine: valac (valac 0.42.5)
Program meson_vapi_link.py found: YES (/usr/bin/python3
/<>/meson_vapi_link.py)
Running compile:
Working directory: /tmp/tmpuanwhmo8
Command line: ccache cc /tmp/tmpuanwhmo8/testfile.c -o
/tmp/tmpuanwhmo8/output.obj -pipe -c -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
-D_FILE_OFFSET_BITS=64 -O0
Code:
#include
int
main(int argc, const char *argv[])
{
git_libgit2_init ();
return ((git_libgit2_features() & GIT_FEATURE_SSH) != 0) ? 0
: 1;
}
Compiler stdout:
Compiler stderr:
ccache: error: Failed to create directory
/sbuild-nonexistent/.ccache/tmp: Permission denied
Checking if "libgit2 supports SSH" compiles: NO
meson.build:148:2: ERROR: Assert failed: libgit2 ssh support was
requested, but not found. Use -Dssh=false to build without it.
dh_auto_configure: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu
--libexecdir=lib/x86_64-linux-gnu -Dgtk_doc=true returned exit code 1
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build] Error 2
Bug#934638: marked as done (ghostscript: CVE-2019-10216)
Your message dated Tue, 13 Aug 2019 08:40:14 + with message-id and subject line Bug#934638: fixed in ghostscript 9.27~dfsg-3.1 has caused the Debian Bug report #934638, regarding ghostscript: CVE-2019-10216 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.) -- 934638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghostscript Version: 9.27~dfsg-3 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=701394 Control: found -1 9.27~dfsg-2 Control: found -1 9.26a~dfsg-0+deb9u2 Control: found -1 9.26a~dfsg-0+deb9u3 Control: found -1 9.06~dfsg-2 Control: fixed -1 9.26a~dfsg-0+deb9u4 Control: fixed -1 9.27~dfsg-2+deb10u1 Hi, The following vulnerability was published for ghostscript. CVE-2019-10216[0]: | -dSAFER escape via .buildfont1 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-10216 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10216 [1] https://bugs.ghostscript.com/show_bug.cgi?id=701394 [2] http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=5b85ddd19a8420a1bd2d5529325be35d78e94234 Regards, Salvatore --- End Message --- --- Begin Message --- Source: ghostscript Source-Version: 9.27~dfsg-3.1 We believe that the bug you reported is fixed in the latest version of ghostscript, 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 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated ghostscript package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Aug 2019 09:49:11 +0200 Source: ghostscript Architecture: source Version: 9.27~dfsg-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Printing Team Changed-By: Salvatore Bonaccorso Closes: 934638 Changes: ghostscript (9.27~dfsg-3.1) unstable; urgency=medium . * Non-maintainer upload (with maintainers approval). * protect use of .forceput with executeonly (CVE-2019-10216) (Closes: #934638) Checksums-Sha1: 4d5894c6a76860fe0fe2b24de1362e35016dd399 2965 ghostscript_9.27~dfsg-3.1.dsc e7b97c0d670c702d30a81764eff3a10c8a4b6582 111316 ghostscript_9.27~dfsg-3.1.debian.tar.xz Checksums-Sha256: 8c44649907b3480c45ddcd9e2f2ea685351a5ed3a9cfc934f1ec272a881318fd 2965 ghostscript_9.27~dfsg-3.1.dsc 002431936315ed31541d6f62541e83a899d8edd3b9e2da84ed157bb218101a2f 111316 ghostscript_9.27~dfsg-3.1.debian.tar.xz Files: 305561f0bb72faf83d3542f6ad15b5b2 2965 text optional ghostscript_9.27~dfsg-3.1.dsc d8373e08b9df33ec898c549e961a8b33 111316 text optional ghostscript_9.27~dfsg-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl1ScoNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EJkYP/2vF/VF8CosTnQnm/B/qbw6ycu2qwGMF L5WAktAA+58G+3hRgo/Z7TTQDidYXyPQKcz0tQ3GGC+AhwOAGAt7Qy7nBX0RL+wr IPEbZDeredjZMR89W6JQ0uVV4gWSY4cJxKw6U442XAKHU2bySY4Jae7JVESwtW6j tgk2dR9Vtfovo+3ZyvtU2p46N/wTRLEftiaSwwqP+tmH14Odk3MLv6CkfpDWMRps ntKKPKdNrseWiRQ6T5TW2JCkHWHXDFNWuUn53kZsGjikMoe2KZYN1TPRP0rVdjZl f/BQ3vIhgzjwQPuZKWJnX0JaTS5Itr1hr1PBWgMipxZDKsoLij3Je/mzoXzF+P2l egsn1CskjuJov1RHPIbkMYIFqYJt4nGE2X6Tm3aQV0LqpfPXSqvV9JnR4G5p+M9t UpSlIKFgZIdmkMDLUZSprbA5vuvdHkExKJ4dL5oo5Eij4EzdDs5ReH0iltqwSIm3 JWkUqSQVQIf+FpOsbX+XM7C6w457bwYEnP8ymZ0zCkaJzVMokiXGxSRp6CMF6+Xj bkq8s+PMQakuUTdoYHJZFhRBc5dOp1BvmrLU4taTy9fZ9MZSAXiYNPEu6/s9/I9T XntXmcCw9TZyDE2+vPvwv9h/NHLfM2JzP/OUCzk46e+vJo3B8H2+wkPur6Q0YJVo 2FaRXGkTWjsM =bXVF -END PGP SIGNATURE End Message ---
Bug#934638: ghostscript: diff for NMU version 9.27~dfsg-3.1
Control: tags 934638 + patch
Control: tags 934638 + pending
Dear Jonas,
I've prepared an NMU for ghostscript (versioned as 9.27~dfsg-3.1) and
uploaded it to according to your ack.
Merge request is as well in
https://salsa.debian.org/printing-team/ghostscript/merge_requests/7
(as the others for the respective versions in buster- and
stretch-security).
Regards,
Salvatore
diff -Nru ghostscript-9.27~dfsg/debian/changelog ghostscript-9.27~dfsg/debian/changelog
--- ghostscript-9.27~dfsg/debian/changelog 2019-07-24 17:45:28.0 +0200
+++ ghostscript-9.27~dfsg/debian/changelog 2019-08-13 09:49:11.0 +0200
@@ -1,3 +1,11 @@
+ghostscript (9.27~dfsg-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload (with maintainers approval).
+ * protect use of .forceput with executeonly (CVE-2019-10216)
+(Closes: #934638)
+
+ -- Salvatore Bonaccorso Tue, 13 Aug 2019 09:49:11 +0200
+
ghostscript (9.27~dfsg-3) unstable; urgency=medium
* Declare compliance with Debian Policy 4.4.0.
diff -Nru ghostscript-9.27~dfsg/debian/patches/020190802~5b85ddd.patch ghostscript-9.27~dfsg/debian/patches/020190802~5b85ddd.patch
--- ghostscript-9.27~dfsg/debian/patches/020190802~5b85ddd.patch 1970-01-01 01:00:00.0 +0100
+++ ghostscript-9.27~dfsg/debian/patches/020190802~5b85ddd.patch 2019-08-13 09:49:11.0 +0200
@@ -0,0 +1,52 @@
+From: Chris Liddell
+Date: Fri, 2 Aug 2019 15:18:26 +0100
+Subject: Bug 701394: protect use of .forceput with executeonly
+Origin: http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=5b85ddd19a8420a1bd2d5529325be35d78e94234
+Bug-Debian: https://bugs.debian.org/934638
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2019-10216
+Bug: https://bugs.ghostscript.com/show_bug.cgi?id=701394
+
+---
+ Resource/Init/gs_type1.ps | 14 +++---
+ 1 file changed, 7 insertions(+), 7 deletions(-)
+
+diff --git a/Resource/Init/gs_type1.ps b/Resource/Init/gs_type1.ps
+index 6c7735bc0cc3..a039ccee3590 100644
+--- a/Resource/Init/gs_type1.ps
b/Resource/Init/gs_type1.ps
+@@ -118,25 +118,25 @@
+ ( to be the same as glyph: ) print 1 index //== exec } if
+3 index exch 3 index .forceput
+ % scratch(string) RAGL(dict) AGL(dict) CharStrings(dict) cstring gname
+- }
++ }executeonly
+ {pop} ifelse
+- } forall
++ } executeonly forall
+pop pop
+- }
++ } executeonly
+ {
+pop pop pop
+ } ifelse
+- }
++ } executeonly
+{
+% scratch(string) RAGL(dict) AGL(dict) CharStrings(dict) cstring gname
+ pop pop
+} ifelse
+- } forall
++ } executeonly forall
+ 3 1 roll pop pop
+- } if
++ } executeonly if
+ pop
+ dup /.AGLprocessed~GS //true .forceput
+- } if
++ } executeonly if
+
+%% We need to excute the C .buildfont1 in a stopped context so that, if there
+%% are errors we can put the stack back sanely and exit. Otherwise callers won't
+--
+2.20.1
+
diff -Nru ghostscript-9.27~dfsg/debian/patches/series ghostscript-9.27~dfsg/debian/patches/series
--- ghostscript-9.27~dfsg/debian/patches/series 2019-04-20 10:09:53.0 +0200
+++ ghostscript-9.27~dfsg/debian/patches/series 2019-08-13 09:49:11.0 +0200
@@ -1,4 +1,5 @@
020190410~06c9207.patch
+020190802~5b85ddd.patch
2001_docdir_fix_for_debian.patch
2002_gs_man_fix_debian.patch
2003_support_multiarch.patch
Processed: ghostscript: diff for NMU version 9.27~dfsg-3.1
Processing control commands: > tags 934638 + patch Bug #934638 [src:ghostscript] ghostscript: CVE-2019-10216 Added tag(s) patch. > tags 934638 + pending Bug #934638 [src:ghostscript] ghostscript: CVE-2019-10216 Added tag(s) pending. -- 934638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934660:
Hi On 2019-08-12 23:32:39, Pedro Terra Delboni wrote: > Hi, > > I just saw in the logs: > > modprobe: FATAL: Module nvidia-current-modeset not found in directory > /lib/modules/5.2.0-2-amd64 > > Sorry for the noise, doesn't look a gdm bug after all, just a missing module. > Should I report this against the kernel package or the nvidia driver? There's no need for that, see #934344 for details. Cheers > Thanks > Pedro -- Sebastian Ramacher
Bug#934660: marked as done (gdm3: "System can't recover" due to integer parameter out of range for operation)
Your message dated Tue, 13 Aug 2019 08:16:34 +0100 with message-id <20190813071634.ga29...@espresso.pseudorandom.co.uk> and subject line Re: Bug#934660: Module nvidia-current-modeset not found has caused the Debian Bug report #934660, regarding gdm3: "System can't recover" due to integer parameter out of range for operation 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.) -- 934660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gdm3 Version: 3.30.2-3 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Booting with kernel linux-image-5.2.0-2-amd64 * What exactly did you do (or not do) that was effective (or ineffective)? Booting with linux-image-4.19.0-5-amd64 works great. This happend in my desktop and also my notebook. Both uses nvidia driver (and not nouveau). nvidia-driver/unstable,now 418.74-1 amd64 [installed] Please, let me know if I should report this to the kernel package instead. * What was the outcome of this action? When I boot with kernel linux-image-5.2.0-2-amd64, I get the screen: "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again." And clicking in the logout button leads to a tty console (that doesn't really work, I had to hit Alt+F3 to get a console). When I look at journalctl I see these: Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: X Error of failed request: BadValue (integer parameter out of range for operation) Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: Major opcode of failed request: 151 (GLX) Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: Minor opcode of failed request: 3 (X_GLXCreateContext) Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: Value in failed request: 0x0 Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: Serial number of failed request: 19 Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: Current serial number in output stream: 20 Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: gnome-session-check-accelerated: GL Helper exited with code 256 Aug 12 22:34:45 livingroom gnome-session-c[1248]: eglGetDisplay() failed Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: gnome-session-check-accelerated: GLES Helper exited with code 256 Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: gnome-session-binary[1228]: WARNING: software acceleration check failed: Child process exited with code 1 Aug 12 22:34:45 livingroom /usr/lib/gdm3/gdm-x-session[911]: gnome-session-binary[1228]: GLib-DEBUG(+): posix_spawn avoided (fd close requested) Aug 12 22:34:45 livingroom gnome-session-binary[1228]: WARNING: software acceleration check failed: Child process exited with code 1 Aug 12 22:34:45 livingroom gnome-session-binary[1228]: GLib-DEBUG(+): posix_spawn avoided (fd close requested) The full log is available at http://ix.io/1Rts * What outcome did you expect instead? I expected the gdm login GUI screen and not the "Oh no" screen after booting. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gdm3 depends on: ii accountsservice 0.6.45-2 ii adduser 3.118 ii dconf-cli 0.30.1-2 ii dconf-gsettings-backend 0.30.1-2 ii debconf [debconf-2.0] 1.5.73 ii gir1.2-gdm-1.03.30.2-3 ii gnome-session [x-session-manager] 3.30.1-2 ii gnome-session-bin 3.30.1-2 ii gnome-settings-daemon 3.30.2-3 ii gnome-shell 3.30.2-10 ii gnome-terminal [x-terminal-emulator] 3.30.2-2 ii gsettings-desktop-schemas 3.28.1-1 ii libaccountsservice0 0.6.45-2 ii libaudit1 1:2.8.5-2 ii libc6 2.28-10 ii libcanberra-gtk3-00.30-7 ii libcanberra0
