Processed: Re: python3-gevent: gevent 1.4 not compatible with python 3.8

Processing control commands: > tags -1 + patch Bug #958476 [python3-gevent] python3-gevent: gevent 1.4 not compatible with python 3.8 Added tag(s) patch. -- 958476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#958476: python3-gevent: gevent 1.4 not compatible with python 3.8

Control: tags -1 + patch I packaged the recent version, cause the current isn't compatible with 3.9 either. All triggered autopkg tests passed. Packaging proposal at https://launchpad.net/ubuntu/+source/python-gevent/20.9.0-0ubuntu1

Processed: Re: aria2: autopkgtest needs update for new version of python3-defaults: output to stderr

Processing control commands: > tags -1 + patch Bug #975900 [src:aria2] aria2: autopkgtest needs update for new version of python3-defaults: output to stderr Added tag(s) patch. -- 975900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975900 Debian Bug Tracking System Contact

Bug#975900: aria2: autopkgtest needs update for new version of python3-defaults: output to stderr

Control: tags -1 + patch patch at https://patches.ubuntu.com/a/aria2/aria2_1.35.0-2ubuntu1.patch

Processed: bug 973605 is forwarded to https://github.com/odoo/odoo/pull/61199

Processing commands for cont...@bugs.debian.org: > forwarded 973605 https://github.com/odoo/odoo/pull/61199 Bug #973605 [src:odoo] odoo: Multiple privacy-breach-generic (fetching data from an external website at runtime) Set Bug forwarded-to-address to 'https://github.com/odoo/odoo/pull/61199'.

Processed: Re: Bug#976171: fmutils failed, breaking tex-common

Processing control commands: > reassign -1 texlive-latex-base Bug #976171 [texlive-base] fmutils failed, breaking tex-common Bug reassigned from package 'texlive-base' to 'texlive-latex-base'. No longer marked as found in versions texlive-base/2020.20201129-1. Ignoring request to alter fixed

Bug#976171: fmutils failed, breaking tex-common

Control: reassign -1 texlive-latex-base Control: severity 976170 serious Control: forcemerge -1 976170 Am 01.12.2020 um 02:07 teilte Vincent Lefevre mit: Dup of bug 976170? Probably. Forcemerge. Hilmar -- sigfault OpenPGP_signature Description: OpenPGP digital signature

Bug#974705: Changes to job handling cause hangs in wait

On Tue, Dec 01, 2020 at 05:06:18PM +1100, Herbert Xu wrote: > > For some reason this is causing the final two tee's to be created > as children of debian/tests/timedated rather than the bash shell. An alternative to changing the parent is of course to do wait $MONPID instead of

Bug#957206: EXTERNAL: Re: Bug#957206: New upstream version available (Was: Bug#957206: fis-gtm: ftbfs with GCC-10)

Hi Andreas, The latest GT.M version, V6.3-014, has a number of GCC-10 fixes in it. debian/rules needed some changes to handle executables that are no longer in the build. I made the necessary changes and tested the build (GCC-10) on my Debian unstable machine. I pushed the changes. Please let

Bug#974705: Changes to job handling cause hangs in wait

On Tue, Dec 01, 2020 at 04:38:37PM +1100, Herbert Xu wrote: > > FWIW I'm unable to reproduce it with autopkgtest. This is what > I get: > > root@test0:~# autopkgtest --test-name=timedated systemd-246.6/ -B -- lxc -s > autopkgtest-sid > autopkgtest [16:32:45]: starting date: 2020-12-01 >

Bug#974705: Changes to job handling cause hangs in wait

On Mon, Nov 16, 2020 at 10:29:16AM +, Andrej Shadura wrote: > > I’d like to forward a bug report I received. Michael, who reported it, > was able to bisect it to 6c691b3, which was the first of the series of > commits changing job handling. > > I must note that I had troubles debugging it: I

Bug#957206: EXTERNAL: Re: Bug#957206: New upstream version available (Was: Bug#957206: fis-gtm: ftbfs with GCC-10)

Hi Amul, thanks for the quick response. Unfortunately the package does not build successfully yet: make[2]: Leaving directory '/build/fis-gtm-6.3-014/obj-x86_64-linux-gnu' cd debian/fis-gtm-6.3-007-stage1/usr/lib/x86_64-linux-gnu/fis-gtm/V6.3-014_x86_64 && \

Bug#952003: marked as done (relion: FTBFS: src/mpi.cpp:56:23: error: call to ‘MPI_Errhandler_set’ declared with attribute error: MPI_Errhandler_set was removed in MPI-3.0. Use MPI_Comm_set_errhandler

Your message dated Tue, 1 Dec 2020 07:05:14 +0100 with message-id <20201201060514.gd31...@an3as.eu> and subject line Bug was closed with new upstream version has caused the Debian Bug report #952003, regarding relion: FTBFS: src/mpi.cpp:56:23: error: call to ‘MPI_Errhandler_set’ declared with

Bug#974705: Changes to job handling cause hangs in wait

On Tue, Dec 01, 2020 at 04:42:03PM +1100, Herbert Xu wrote: > > Nevermind, I see that the script has been modified to use bash. > > I can reproduce the problem now so it's all good. OK the problem is this: sh -c 'sleep 1d& exec $MYSHELL -c "sleep 1& wait"' You can replace MYSHELL with

Bug#975849: marked as done (cjs: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Tue, 01 Dec 2020 05:52:53 + with message-id and subject line Bug#975849: fixed in cjs 4.8.0-1 has caused the Debian Bug report #975849, regarding cjs: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be

Bug#975411: meson: autopkgtest arm64

Hello, I implemented this test in https://github.com/mesonbuild/meson/commit/631a7b5a2a8ffa31d0d126608e79841be02ecfea . Please enable it in the next version. Michel Le Bihan

Bug#976171: fmutils failed, breaking tex-common

Dup of bug 976170? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976170 976170: fmtutil [ERROR]: running `aleph -ini -jobname=lamed -progname=lamed *lambda.ini - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA -

Bug#974754: marked as done (libjbig0: invalid ELF header when loading libjbig.so.0)

Your message dated Tue, 1 Dec 2020 01:11:04 +0100 with message-id <08fd4679-3f07-0ad5-a0c9-928bdffdf...@debian.org> and subject line Re: libjbig0: invalid ELF header when loading libjbig.so.0 has caused the Debian Bug report #974754, regarding libjbig0: invalid ELF header when loading libjbig.so.0

Processed: tagging 975818, tagging 975797, tagging 975849, tagging 975854, tagging 975851, tagging 975848 ...

Processing commands for cont...@bugs.debian.org: > tags 975818 + experimental Bug #975818 [src:libgtkada] libgtkada: FTBFS: AttributeError: 'xml.etree.ElementTree.Element' object has no attribute 'getchildren' Added tag(s) experimental. > tags 975797 + experimental Bug #975797

Bug#975143: marked as done (rosegarden: FTBFS: Panner.cpp:138:18: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)

Your message dated Mon, 30 Nov 2020 23:48:40 + with message-id and subject line Bug#975143: fixed in rosegarden 1:20.06-2 has caused the Debian Bug report #975143, regarding rosegarden: FTBFS: Panner.cpp:138:18: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined

Processed: Re: Bug#954403: joblib: configuration error installing python3-joblib

Processing control commands: > reassign -1 python3-minimal 3.8.6-1 Bug #954403 [src:joblib] joblib: configuration error installing python3-joblib Bug #975517 [src:joblib] joblib fails to install with Python 3.9 Bug reassigned from package 'src:joblib' to 'python3-minimal'. Bug reassigned from

Bug#954403: joblib: configuration error installing python3-joblib

Control: reassign -1 python3-minimal 3.8.6-1 Control: affects -1 src:joblib On 2020-03-21 11:25:31 +0200, Graham Inggs wrote: > Source: joblib > Version: 0.14.0-3 > Severity: serious > Control: affects -1 src:spades src:circlator > > Hi Maintainer > > While attempting to run the autopkgtests

Bug#973174: marked as done (python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13)

Your message dated Mon, 30 Nov 2020 21:48:38 + with message-id and subject line Bug#973174: fixed in python-envisage 4.9.0-2.1 has caused the Debian Bug report #973174, regarding python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13

Bug#973074: marked as done (python-apptools: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13)

Your message dated Mon, 30 Nov 2020 21:35:55 + with message-id and subject line Bug#973074: fixed in python-apptools 4.5.0-1.1 has caused the Debian Bug report #973074, regarding python-apptools: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned

Bug#957276: marked as done (gluegen2: ftbfs with GCC-10)

Your message dated Mon, 30 Nov 2020 21:33:48 + with message-id and subject line Bug#957276: fixed in gluegen2 2.3.2-8 has caused the Debian Bug report #957276, regarding gluegen2: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: affects 976171

Processing commands for cont...@bugs.debian.org: > affects 976171 tex-common Bug #976171 [texlive-base] fmutils failed, breaking tex-common Added indication that 976171 affects tex-common > thanks Stopping processing here. Please contact me if you need assistance. -- 976171:

Bug#957184: eurephia: diff for NMU version 1.1.0-6.1

Hi, Sudip. Thanks for the upload. No need to cancel it :-) On Mon, Nov 30, 2020 at 08:52:30PM +, Sudip Mukherjee wrote: > Control: tags 957184 + patch > Control: tags 957184 + pending > -- > > Dear maintainer, > > I've prepared an NMU for eurephia (versioned as 1.1.0-6.1) and > uploaded it

Processed: freebirth: diff for NMU version 0.3.2-9.3

Processing control commands: > tags 957228 + patch Bug #957228 [src:freebirth] freebirth: ftbfs with GCC-10 Added tag(s) patch. > tags 957228 + pending Bug #957228 [src:freebirth] freebirth: ftbfs with GCC-10 Added tag(s) pending. -- 957228:

Bug#957228: freebirth: diff for NMU version 0.3.2-9.3

Control: tags 957228 + patch Control: tags 957228 + pending -- Dear maintainer, I've prepared an NMU for freebirth (versioned as 0.3.2-9.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -u freebirth-0.3.2/debian/changelog

Bug#975133: marked as done (tupi: FTBFS: tslider.cpp:292:29: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)

Your message dated Mon, 30 Nov 2020 20:53:08 + with message-id and subject line Bug#975133: fixed in tupi 0.2+git08-4 has caused the Debian Bug report #975133, regarding tupi: FTBFS: tslider.cpp:292:29: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined to be

Processed: eurephia: diff for NMU version 1.1.0-6.1

Processing control commands: > tags 957184 + patch Bug #957184 [src:eurephia] eurephia: ftbfs with GCC-10 Added tag(s) patch. > tags 957184 + pending Bug #957184 [src:eurephia] eurephia: ftbfs with GCC-10 Added tag(s) pending. -- 957184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957184

Bug#957184: eurephia: diff for NMU version 1.1.0-6.1

Control: tags 957184 + patch Control: tags 957184 + pending -- Dear maintainer, I've prepared an NMU for eurephia (versioned as 1.1.0-6.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru eurephia-1.1.0/debian/changelog

Bug#973210: marked as done (python-django-celery-results: FTBFS: ModuleNotFoundError: No module named 'celery.five')

Your message dated Mon, 30 Nov 2020 20:48:30 + with message-id and subject line Bug#973210: fixed in python-django-celery-results 2.0.0-1 has caused the Debian Bug report #973210, regarding python-django-celery-results: FTBFS: ModuleNotFoundError: No module named 'celery.five' to be marked

Bug#954613: marked as done (rust-process-viewer: FTBFS: unsatisfiable build-dependency: librust-sysinfo-0.9+default-dev (versioned dep on a virtual pkg?))

Your message dated Mon, 30 Nov 2020 20:49:20 + with message-id and subject line Bug#954613: fixed in rust-process-viewer 0.2.6-2 has caused the Debian Bug report #954613, regarding rust-process-viewer: FTBFS: unsatisfiable build-dependency: librust-sysinfo-0.9+default-dev (versioned dep on a

Bug#976169: psi4: autopkgtest regression in testing: ImportError: cannot import name 'core' from partially initialized module 'psi4'

Source: psi4 Version: 1:1.3.2-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent change in testing (I believe the added support of Python3.9) the autopkgtest of psi4 started to fail. I copied some

Bug#957206: New upstream version available (Was: Bug#957206: fis-gtm: ftbfs with GCC-10)

Hi again Amul, I updated Git to the next upstream version. It also does not build successfully. We *really* should fix this *right* now. Otherwise fis-gtm will be not released with the next stable release. Kind regards Andreas. On Thu, Oct 01, 2020 at 03:52:01PM +0200, Andreas Tille

Bug#969074: [PATCH] d/p/lp-1894129-*: fix FTBFS (LP: #1894129 Closes: #969074)

Hi all, Christian, On Tue, 8 Sep 2020 15:40:11 +0200 Christian Ehrhardt wrote: > Signed-off-by: Christian Ehrhardt > --- > ...raseReserved-override-driver-queue_p.patch | 74 > ...BlockEraseReserved-skip-unless-iSCSI.patch | 39 > ...e-Write-override-driver-queue_pdu-ca.patch

Processed: Re: src:imlib2: fails to migrate to testing for too long: FTBFS on s390x

Processing control commands: > tags -1 ftbfs Bug #973353 {Done: Paul Gevers } [src:imlib2] src:imlib2: fails to migrate to testing for too long: FTBFS on s390x Added tag(s) ftbfs. > reopen -1 Bug #973353 {Done: Paul Gevers } [src:imlib2] src:imlib2: fails to migrate to testing for too long:

Bug#973353: src:imlib2: fails to migrate to testing for too long: FTBFS on s390x

Control: tags -1 ftbfs Control: reopen -1 Hi, On Thu, 29 Oct 2020 11:49:42 +0100 Paul Gevers wrote: > This bug will trigger auto-removal when appropriate. As with all new > bugs, there will be at least 30 days before the package is auto-removed. This package is a key package, and as such will

Processed: src:rust-redox-syscall: fails to migrate to testing for too long: FTBFS everywhere

Processing control commands: > close -1 0.1.57-1 Bug #976167 [src:rust-redox-syscall] src:rust-redox-syscall: fails to migrate to testing for too long: FTBFS everywhere The source 'rust-redox-syscall' and version '0.1.57-1' do not appear to match any binary packages Marked as fixed in versions

Bug#976167: src:rust-redox-syscall: fails to migrate to testing for too long: FTBFS everywhere

Source: rust-redox-syscall Version: 0.1.40-2 Severity: serious Control: close -1 0.1.57-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 971209 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that

Processed: Bug#973210 marked as pending in python-django-celery-results

Processing control commands: > tag -1 pending Bug #973210 [src:python-django-celery-results] python-django-celery-results: FTBFS: ModuleNotFoundError: No module named 'celery.five' Added tag(s) pending. -- 973210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973210 Debian Bug Tracking

Bug#973210: marked as pending in python-django-celery-results

Control: tag -1 pending Hello, Bug #973210 in python-django-celery-results 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:

Bug#976111: topydo 0.13-3 upload seems to hang ci.debian.net workers while testing todo.txt-base

Hi David, On 30-11-2020 17:05, David Steele wrote: > All works well, until you test the new version of one package along with > the old version of the other. In one scenario there is a recursion, where > topydo ends up calling itself via the alternatives hook. Ack. That's probably what we're

Processed: Re: Bug#974090 closed by Debian FTP Masters (reply to Hideki Yamane ) (Bug#974090: fixed in lcdf-typetools 2.108-2)

Processing commands for cont...@bugs.debian.org: > # BTS doesn't handle these double assigned bugs extremely well > reassign 974090 src:lcdf-typetools 2.108-1 Bug #974090 {Done: Hideki Yamane } [src:fonts-gfs-artemisia, src:lcdf-typetools] fonts-gfs-artemisia breaks lcdf-typetools autopkgtest:

Processed: RM: xnnpack [armhf] -- RoQA; package no longer builds on armhf

Processing control commands: > block 973560 by -1 Bug #973560 {Done: Paul Gevers } [src:xnnpack] src:xnnpack: fails to migrate to testing for too long: FTBFS on armhf 973560 was not blocked by any bugs. 973560 was not blocking any bugs. Added blocking bug(s) of 973560: 976164 -- 973560:

Bug#975994: zimlib breaks python-libzim autopkgtest: segfaults

Hi Kunal On 30-11-2020 02:34, Kunal Mehta wrote: > So I plan to close this bug with an upload of python-libzim 0.0.3-2 that > depends on libzim-dev >= 6.3.0. Will that be enough for the CI system or > do I also need to have zimlib Break the older python-libzim versions? That versioned Depends

Bug#976081: [Pkg-javascript-devel] Bug#976081: Bug#976081: yarnpkg: Provide prebuilt yarnpkg in contrib

On Tue, Dec 1, 2020 at 00:28, Pirate Praveen wrote: On Mon, Nov 30, 2020 at 19:46, Paolo Greppi wrote: The resulting package was not installable due to node-babel-runtime missing from testing May be we can add babel-runtime as a component? (it is going to contrib anyway) Or see

Bug#976081: [Pkg-javascript-devel] Bug#976081: yarnpkg: Provide prebuilt yarnpkg in contrib

On Mon, Nov 30, 2020 at 19:46, Paolo Greppi wrote: On Sun, 29 Nov 2020 18:02:16 +0530 Pirate Praveen wrote: Control: clone -1 -2 Control: retitle -2 "Provide prebuilt yarnpkg in contrib" On Sat, Nov 28, 2020 at 22:07, Paolo Greppi wrote: >> 3. Build it using 'deb >>

Bug#976081: [Pkg-javascript-devel] Bug#976081: yarnpkg: Provide prebuilt yarnpkg in contrib

On Sun, 29 Nov 2020 18:02:16 +0530 Pirate Praveen wrote: Control: clone -1 -2 Control: retitle -2 "Provide prebuilt yarnpkg in contrib" On Sat, Nov 28, 2020 at 22:07, Paolo Greppi wrote: >> 3. Build it using 'deb >> https://snapshot.debian.org/archive/debian/20200502T085134Z sid >> main'

Bug#975457: marked as done (mandos: password-agent autopkgtest does not seem to be reliable)

Your message dated Mon, 30 Nov 2020 18:48:24 + with message-id and subject line Bug#975457: fixed in mandos 1.8.13-1 has caused the Debian Bug report #975457, regarding mandos: password-agent autopkgtest does not seem to be reliable to be marked as done. This means that you claim that the

Bug#976155: [Pkg-javascript-devel] Bug#976155: yarnpkg: depends on obsolete virtual node-node-uuid

On Mon, Nov 30, 2020 at 19:35, Jonas Smedegaard wrote: Btw, it seems you need to push latest changes to git for yarnpkg The recent changes are in master-1 branch as we could not fix the master branch (attempted to build with babel 7 without success).

Bug#976155: [Pkg-javascript-devel] Bug#976155: yarnpkg: depends on obsolete virtual node-node-uuid

Quoting Jonas Smedegaard (2020-11-30 19:31:26) > Quoting Pirate Praveen (2020-11-30 18:43:27) > > On Mon, Nov 30, 2020 at 18:32, Jonas Smedegaard wrote: > > > yarnpkg depends on node-node-uuid. > > > > > > node-node-uuid was deprecated 2 yars ago, replaced by node-uuid. > > > > > > Please

Bug#976155: [Pkg-javascript-devel] Bug#976155: yarnpkg: depends on obsolete virtual node-node-uuid

Quoting Pirate Praveen (2020-11-30 18:43:27) > On Mon, Nov 30, 2020 at 18:32, Jonas Smedegaard wrote: > > yarnpkg depends on node-node-uuid. > > > > node-node-uuid was deprecated 2 yars ago, replaced by node-uuid. > > > > Please change to instead depend on node-uuid. > > > > Raised severity as

Bug#976035: marked as done (Doesn't work with Python 3.9)

Your message dated Mon, 30 Nov 2020 18:18:34 + with message-id and subject line Bug#976035: fixed in mitmproxy 5.3.0-1 has caused the Debian Bug report #976035, regarding Doesn't work with Python 3.9 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#975178: marked as done (mitmproxy: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Mon, 30 Nov 2020 18:18:34 + with message-id and subject line Bug#975178: fixed in mitmproxy 5.3.0-1 has caused the Debian Bug report #975178, regarding mitmproxy: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that

Bug#975157: (no subject)

This has been fixed upstream, so an upcoming update will resolve it. signature.asc Description: OpenPGP digital signature

Processed: [bts-link] source package src:consul

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:consul > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Processed: [bts-link] source package src:compyle

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:compyle > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#976155: [Pkg-javascript-devel] Bug#976155: yarnpkg: depends on obsolete virtual node-node-uuid

On Mon, Nov 30, 2020 at 18:32, Jonas Smedegaard wrote: Package: yarnpkg Version: 1.22.4-4 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 yarnpkg depends on node-node-uuid. node-node-uuid was deprecated 2 yars ago, replaced by

Bug#976156: libapache-mod-auth-kerb probably shouldn't be released in its current form

package: libapache-mod-auth-kerb severity: serious version: 5.4-2.4 tags: security justification: unmaintained with security weaknesses Hi. As part of a recent krb5 transition, I took a look at libapache-mod-auth-kerb. As part of that transition, libapache-mod-auth-kerb was removed from

Bug#976155: yarnpkg: depends on obsolete virtual node-node-uuid

Package: yarnpkg Version: 1.22.4-4 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 yarnpkg depends on node-node-uuid. node-node-uuid was deprecated 2 yars ago, replaced by node-uuid. Please change to instead depend on node-uuid. Raised

Bug#976047: marked as done (shoogle: flaky autopkgtest on ci.debian.net and missing needs-internet restriction)

Your message dated Mon, 30 Nov 2020 17:23:22 + with message-id and subject line Bug#976047: fixed in shoogle 0.1.4-10 has caused the Debian Bug report #976047, regarding shoogle: flaky autopkgtest on ci.debian.net and missing needs-internet restriction to be marked as done. This means that

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

Package: nvidia-legacy-340xx-driver Version: 340.108-8 Followup-For: Bug #976056 X-Debbugs-Cc: pitsior...@gmail.com As it seems, arch builds its kernel with the same parameter disabled, as seen on line 6528 here https://github.com/archlinux/svntogit-packages/blob/packages/linux/trunk/config And

Bug#973096: python-bleach: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

Hi, I've prepared a fix for this package at https://salsa.debian.org/python-team/packages/python-bleach/-/merge_requests/1 I lack permissions to merge to master and upload this package. The patch itself is based on a pending upstream MR, details are in the quilt patch annotation. Regards,

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

Package: nvidia-legacy-340xx-driver Version: 340.108-8 Followup-For: Bug #976056 X-Debbugs-Cc: pitsior...@gmail.com That is tough! It may also be the end for me on debian, after ~13 years, because my financial status does not allow a hw upgrade right now. Why is that kernel parameter so

Bug#976111: topydo 0.13-3 upload seems to hang ci.debian.net workers while testing todo.txt-base

On Sun, Nov 29, 2020 at 3:51 PM Paul Gevers wrote: > Source: topydo > Version: 0.13-3 > Severity: serious > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: issue > > Dear David, > > I have no idea what's happening, but currently we have multiple workers >

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

On 11/30/20 4:59 PM, Andreas Beckmann wrote: > I'm afraid that is the end for 340xx, at least if you want to use a > recent kernel (i.e. newer than stable). Or you build your own kernel - rebuilding the Debian kernel with some configure option toggled should not be that difficult. Andreas

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

On 11/30/20 4:34 PM, jim_p wrote: > So, this change is/was really needed? What will happen to nvidia 340 now? > One of the reasons I am still on debian is that it still packages it. I can > not > find a patch for it so as to help more. > Also, will this change be made in future kernel builds as

Processed: Re: Bug#975344: libapache-mod-auth-kerb: Uses Internal Krb5 APIs [test this patch please]

Processing control commands: > tags -1 pending Bug #975344 [libapache2-mod-auth-kerb] FTBFS with krb5 1.18: significant use of internal Added tag(s) pending. -- 975344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975344 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#975344: libapache-mod-auth-kerb: Uses Internal Krb5 APIs [test this patch please]

control: tags -1 pending I've uploaded to delayed/3, using your minimal patch. Thanks. --Sam

Bug#957572: marked as done (munipack: ftbfs with GCC-10)

Your message dated Mon, 30 Nov 2020 15:33:51 + with message-id and subject line Bug#957572: fixed in munipack 0.5.12-1 has caused the Debian Bug report #957572, regarding munipack: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

Package: nvidia-legacy-340xx-driver Version: 340.108-8 Followup-For: Bug #976056 X-Debbugs-Cc: pitsior...@gmail.com So, this change is/was really needed? What will happen to nvidia 340 now? One of the reasons I am still on debian is that it still packages it. I can not find a patch for it so as

Bug#976147: [debian-mysql] Bug#976147: Upgrade from mariadb-server-10.3 to mariadb-server-10.5 fails

Hi Jörg! I am not sure that I understand what are the steps that I could follow to verify this. Are you trying to dist-upgrade from buster to sid? In that case, I was not able to reproduce the error in a container with the following steps: | # podman run -it debian:10 bash | # apt update | # apt

Bug#975275: marked as done (ceph: CVE-2020-25660: CEPHX_V2 replay attack protection lost)

Your message dated Mon, 30 Nov 2020 14:33:56 + with message-id and subject line Bug#975275: fixed in ceph 14.2.15-1 has caused the Debian Bug report #975275, regarding ceph: CVE-2020-25660: CEPHX_V2 replay attack protection lost to be marked as done. This means that you claim that the

Bug#963760: marked as done (new upstream release (1.4.11))

Your message dated Mon, 30 Nov 2020 14:33:56 + with message-id and subject line Bug#963760: fixed in ceph 14.2.15-1 has caused the Debian Bug report #963760, regarding new upstream release (1.4.11) to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#957079: marked as done (ceph: ftbfs with GCC-10)

Your message dated Mon, 30 Nov 2020 14:33:56 + with message-id and subject line Bug#957079: fixed in ceph 14.2.15-1 has caused the Debian Bug report #957079, regarding ceph: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#972908: marked as done (ceph fbfs with python3.9)

Your message dated Mon, 30 Nov 2020 14:33:56 + with message-id and subject line Bug#957079: fixed in ceph 14.2.15-1 has caused the Debian Bug report #957079, regarding ceph fbfs with python3.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: Re: Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)

Processing control commands: > severity -1 serious Bug #976056 [nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64) Ignoring request to change severity of Bug 976056 to the same value. > retitle -1

Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)

Control: severity -1 serious Control: retitle -1 nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards Control: tag -1 upstream wontfix On 11/29/20 1:37 PM, Salvatore Bonaccorso wrote: > Some background: In the 5.9.11-1 upload for src:linux we disabled >

Processed: Confirm bug

Processing commands for cont...@bugs.debian.org: > tags 933798 confirmed Bug #933798 [libnetfilter-conntrack-dev] libnetfilter-conntrack-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you

Bug#973098: marked as done (twms: FTBFS: error: Error: setup script specifies an absolute path:)

Your message dated Mon, 30 Nov 2020 13:33:21 + with message-id and subject line Bug#973098: fixed in twms 0.07z+git20201130+6edd37d-1 has caused the Debian Bug report #973098, regarding twms: FTBFS: error: Error: setup script specifies an absolute path: to be marked as done. This means that

Processed: Falcon builds but autopkgtest fails (and some build time test failures are ignored

Processing control commands: > tags -1 pending Bug #936503 [src:falcon] falcon: Python2 removal in sid/bullseye Added tag(s) pending. -- 936503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#936503: Falcon builds but autopkgtest fails (and some build time test failures are ignored

Control: tags -1 pending Hi, since some time falcon[1] in Git builds with some cheating - some test errors are simply ignored. Also the autopktest is failing. It would be great if someone would spent time on these two RC bugs in an advent calendar attempt. Kind regards Andreas. [1]

Processed: Falcon builds but autopkgtest fails (and some build time test failures are ignored

Processing control commands: > tags -1 pending Bug #902132 [src:falcon] falcon: FTBFS since python-networkx version 2.1-1; fails in test suite Added tag(s) pending. -- 902132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902132 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#976147: Upgrade from mariadb-server-10.3 to mariadb-server-10.5 fails

Package: mariadb-server-10.5 Version: 1:10.5.8-3 Severity: critical -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, on apt dist-upgrade on my sid system mariadb-server-10.3 are uninstalled and mariadb-server-10.5 are not installed. [quote] Start-Date: 2020-11-30 12:52:01 Commandline:

Bug#971703: marked as done (golang-github-knadh-koanf: not buildable from source in Debian)

Your message dated Mon, 30 Nov 2020 12:33:25 + with message-id and subject line Bug#971703: fixed in golang-github-knadh-koanf 0.10.0-2 has caused the Debian Bug report #971703, regarding golang-github-knadh-koanf: not buildable from source in Debian to be marked as done. This means that you

Bug#972907: marked as done (astra-toolbox ftbfs with python3.9)

Your message dated Mon, 30 Nov 2020 12:33:20 + with message-id and subject line Bug#972907: fixed in astra-toolbox 1.8.3-3 has caused the Debian Bug report #972907, regarding astra-toolbox ftbfs with python3.9 to be marked as done. This means that you claim that the problem has been dealt

Processed: tagging 975178, tagging 976035

Processing commands for cont...@bugs.debian.org: > tags 975178 + pending Bug #975178 [src:mitmproxy] mitmproxy: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) pending. > tags 976035 + pending Bug #976035 [mitmproxy] Doesn't work with Python 3.9 Added tag(s)

Bug#976109: [Pkg-xen-devel] Bug#976109: xen: CVE-2020-29040

Hi, On 11/29/20 8:50 PM, Salvatore Bonaccorso wrote: > Source: xen > Version: 4.14.0+80-gd101b417b7-1 > Severity: grave > Tags: security upstream > Justification: user security hole > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > > Hi, > > The following vulnerability was published

Bug#972504: marked as done (python-cogent ftbfs with python3.9 as supported python3 version)

Your message dated Mon, 30 Nov 2020 12:29:16 +0100 with message-id and subject line Re: python-cogent ftbfs with python3.9 as supported python3 version has caused the Debian Bug report #972504, regarding python-cogent ftbfs with python3.9 as supported python3 version to be marked as done. This

Bug#976068: marked as done (python-fakeredis' autopkg tests fail)

Your message dated Mon, 30 Nov 2020 11:03:24 + with message-id and subject line Bug#976068: fixed in python-fakeredis 1.4.5-1 has caused the Debian Bug report #976068, regarding python-fakeredis' autopkg tests fail to be marked as done. This means that you claim that the problem has been

Bug#964496: libjson-validator-perl: URL is gone, this is now RC

Hello, On 2020-11-29 18:59, Wouter Verhelst wrote: > This bug is still present. Additionally, the URL for the OpenAPI JSON > scheme now returns a 404 error, which means that any software using > OpenAPI on Debian with this bug present will fail to function correctly.> > Please fix this bug before

Processed: bug 968318 is forwarded to https://gitlab.esrf.fr/mirone/pyhst2/-/issues/3

Processing commands for cont...@bugs.debian.org: > forwarded 968318 https://gitlab.esrf.fr/mirone/pyhst2/-/issues/3 Bug #968318 [src:pyhst2] pyhst2: FTBFS with CUDA 11: Unsupported gpu architecture 'compute_30' Set Bug forwarded-to-address to 'https://gitlab.esrf.fr/mirone/pyhst2/-/issues/3'. >

Processed: reassign 972095 to src:python-fakeredis, forcibly merging 972153 972095

Processing commands for cont...@bugs.debian.org: > reassign 972095 src:python-fakeredis Bug #972095 [python-fakeredis] missing test-dependency Bug reassigned from package 'python-fakeredis' to 'src:python-fakeredis'. No longer marked as found in versions 1.4.3-1. Ignoring request to alter fixed

Processed (with 1 error): unarchiving 972153, forcibly merging 972153 972095

Processing commands for cont...@bugs.debian.org: > unarchive 972153 Bug #972153 {Done: =?utf-8?b?T25kxZllaiBOb3bDvQ==?= } [src:python-fakeredis] python-fakeredis autopkg test fails Unarchived Bug 972153 > forcemerge 972153 972095 Bug #972153 {Done: =?utf-8?b?T25kxZllaiBOb3bDvQ==?= }

Processed: Bug#976068 marked as pending in python-fakeredis

Processing control commands: > tag -1 pending Bug #976068 [src:python-fakeredis] python-fakeredis' autopkg tests fail Added tag(s) pending. -- 976068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#976068: marked as pending in python-fakeredis

Control: tag -1 pending Hello, Bug #976068 in python-fakeredis 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:

Bug#976105: marked as done (golang-github-tidwall-buntdb FTBFS: FAIL: TestOnExpiredSync)

Your message dated Mon, 30 Nov 2020 10:18:22 + with message-id and subject line Bug#976105: fixed in golang-github-tidwall-buntdb 1.1.2-3 has caused the Debian Bug report #976105, regarding golang-github-tidwall-buntdb FTBFS: FAIL: TestOnExpiredSync to be marked as done. This means that you

Processed: Bug#976105 marked as pending in golang-github-tidwall-buntdb

Processing control commands: > tag -1 pending Bug #976105 [src:golang-github-tidwall-buntdb] golang-github-tidwall-buntdb FTBFS: FAIL: TestOnExpiredSync Added tag(s) pending. -- 976105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976105 Debian Bug Tracking System Contact

  1   2   >