Bug#1005953: needrestart: user session restart needing detection broken probably by cgroupv2 from systemd 247.2-4

2022-02-17 Thread Michael Biebl
Am 18.02.22 um 02:42 schrieb Paul Wise: systemd upstream seems to have deleted their 247.2 git tag and there is no reference to it in their NEWS files. Stable point releases are available from https://github.com/systemd/systemd-stable In this specific instance from the v247-stable branch

Processed: nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4

2022-02-17 Thread Debian Bug Tracking System
Processing control commands: > found -1 fq/0.0.4-2 Bug #1005961 [nq,fq] nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4 Marked as found in versions fq/0.0.4-2. > found -1 nq/0.3.1-4 Bug #1005961 [nq,fq] nq,fq: trying to overwrite '/usr/bin/fq', which is also in

Bug#1005961: nq,fq: trying to overwrite '/usr/bin/fq', which is also in package nq 0.3.1-4

2022-02-17 Thread Axel Beckert
Package: nq,fq Severity: serious Control: found -1 fq/0.0.4-2 Control: found -1 nq/0.3.1-4 Trying to install fq fails for me as follows: Preparing to unpack .../archives/fq_0.0.4-2_amd64.deb ... Unpacking fq (0.0.4-2) ... dpkg: error processing archive

Bug#1005685: marked as done (cvise: FTBFS: The imported target "RemoteIndexProto" references the file "/usr/lib/llvm-13/lib/libRemoteIndexProto.a" but this file does not exist.)

2022-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Feb 2022 04:14:59 +0100 with message-id <6d4d664a-234d-dce3-e725-5eabb50a3...@debian.org> and subject line closing, not reproducible has caused the Debian Bug report #1005685, regarding cvise: FTBFS: The imported target "RemoteIndexProto" references the file

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

2022-02-17 Thread Chris Chang
I was unable to replicate this issue on a Debian EC2 instance. However, there are very few things that happen between printing "End time:" and program exit, so I have added a bunch of debug-prints (active when the --debug flag is passed in) to the latest GitHub commit that should reveal which of

Bug#1005953: needrestart: user session restart needing detection broken probably by cgroupv2 from systemd 247.2-4

2022-02-17 Thread Paul Wise
Package: needrestart Version: 3.5-5 Severity: serious X-Debbugs-CC: syst...@packages.debian.org User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: cgroupv2 needrestart detects that user@1000.service needs to be restarted, instead of that the pabs user sessions have outdated binaries.

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

2022-02-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Feb 2022 00:49:31 + with message-id and subject line Bug#1002348: fixed in pyflakes 2.4.0-1 has caused the Debian Bug report #1002348, regarding pyflakes: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" returned exit code 13

Processed: Re: offlineimap3: 'int' object is not subscriptable when connecting to outlook.office365.com

2022-02-17 Thread Debian Bug Tracking System
Processing control commands: > severity 997933 important Bug #997933 [offlineimap3] offlineimap3: 'int' object is not subscriptable when connecting to outlook.office365.com Severity set to 'important' from 'serious' -- 997933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997933 Debian Bug

Bug#997933: offlineimap3: 'int' object is not subscriptable when connecting to outlook.office365.com

2022-02-17 Thread Sudip Mukherjee
Control: severity 997933 important -- On Wed, Oct 27, 2021 at 11:47:34AM +0100, ael wrote: > Package: offlineimap3 > Version: 0.0~git20211018.e64c254+dfsg-1 > Severity: serious > Justification: 4 > > In the last week or so, offlineimap is usually (but not always) > failing to connect to

Bug#1005947: ignition-math: FTBFS on armel and mipsel

2022-02-17 Thread Paul Gevers
Source: ignition-math Version: 6.10.0+ds2-1 Severity: serious Tags: ftbfs Dear maintainer You recent upload FTBFS on armel and mipsel and your package is part of the ruby3.0 as default ruby transition. Please fix ASAP. Paul [ 65%] Linking CXX executable ../bin/UNIT_Sphere_TEST cd

Processed: cloning 1005933, reassign -1 to nvidia-graphics-drivers-tesla-510 ...

2022-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 1005933 -1 Bug #1005933 [xserver-xorg-video-nvidia-tesla-460] nvidia-graphics-drivers-tesla-460: incompatible with xorg-server video ABI 25 Bug 1005933 cloned as bug 1005946 > reassign -1 nvidia-graphics-drivers-tesla-510 510.47.03-1 Bug

Bug#1005899: mplayer: should not release with bookworm

2022-02-17 Thread Sebastian Ramacher
On 2022-02-17 19:13:08 +0100, Reimar Döffinger wrote: > > > On 16 Feb 2022, at 23:25, Sebastian Ramacher wrote: > > > > Let's stop pretending that mplayer is maintained. > > What is your criteria for "maintained"? In Debian or upstream? Upstream > issues are still addressed from time to time,

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

2022-02-17 Thread Andreas Tille
Am Thu, Feb 17, 2022 at 11:39:30AM -0800 schrieb Chris Chang: > Haven't yet replicated this on any of my usual non-Debian test machines, > but I will spin up a Debian EC2 instance within the next two days and try > to replicate the crash there. Thanks a lot, Andreas. -- http://fam-tille.de

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

2022-02-17 Thread Chris Chang
Haven't yet replicated this on any of my usual non-Debian test machines, but I will spin up a Debian EC2 instance within the next two days and try to replicate the crash there. On Wed, Feb 16, 2022 at 11:30 PM Andreas Tille wrote: > PS to last mail: Here > >

Bug#1005637: marked as done (wxpython4.0: FTBFS: tar: wx_siplib-12.9.0.tar.gz: Cannot open: No such file or directory)

2022-02-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Feb 2022 19:21:05 + with message-id and subject line Bug#1005637: fixed in wxpython4.0 4.0.7+dfsg-13 has caused the Debian Bug report #1005637, regarding wxpython4.0: FTBFS: tar: wx_siplib-12.9.0.tar.gz: Cannot open: No such file or directory to be marked as done.

Bug#1005899: mplayer: should not release with bookworm

2022-02-17 Thread Reimar Döffinger
> On 16 Feb 2022, at 23:25, Sebastian Ramacher wrote: > > Let's stop pretending that mplayer is maintained. What is your criteria for "maintained"? In Debian or upstream? Upstream issues are still addressed from time to time, there are still several people around that can address issues, in

Bug#1005011: marked as done (lots of missing entries in debian/copyright)

2022-02-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Feb 2022 17:04:18 + with message-id and subject line Bug#1005011: fixed in capnproto 0.8.0-3 has caused the Debian Bug report #1005011, regarding lots of missing entries in debian/copyright to be marked as done. This means that you claim that the problem has been

Bug#997319: marked as done (davfs2: FTBFS: configure: error: could not find neon)

2022-02-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Feb 2022 16:49:00 + with message-id and subject line Bug#997319: fixed in davfs2 1.6.1-1 has caused the Debian Bug report #997319, regarding davfs2: FTBFS: configure: error: could not find neon to be marked as done. This means that you claim that the problem has

Bug#994521: marked as done (ledmon: libsgutils2-2 1.46 update breaks ledmon)

2022-02-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Feb 2022 16:49:21 + with message-id and subject line Bug#994521: fixed in ledmon 0.95-2 has caused the Debian Bug report #994521, regarding ledmon: libsgutils2-2 1.46 update breaks ledmon to be marked as done. This means that you claim that the problem has been

Processed: Re: [Pkg-javascript-devel] Bug#1005940: node-lockfile: Abandoned upstream

2022-02-17 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1005940 [node-lockfile] node-lockfile: Abandoned upstream Severity set to 'serious' from 'normal' -- 1005940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#997367: marked as done (virt-manager: FTBFS: AssertionError: Command was: ./virt-xml test-for-virtxml --print-diff --define --add-device --host-device usb_device_4b3_4485_noserial --connect __vir

2022-02-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Feb 2022 15:08:38 + with message-id and subject line Bug#997367: fixed in virt-manager 1:3.2.0-3.1 has caused the Debian Bug report #997367, regarding virt-manager: FTBFS: AssertionError: Command was: ./virt-xml test-for-virtxml --print-diff --define --add-device

Bug#997367: marked as pending in virt-manager

2022-02-17 Thread Guido Günther
Control: tag -1 pending Hello, Bug #997367 in virt-manager 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#997367: [Pkg-libvirt-maintainers] Bug#997367: virt-manager: FTBFS: AssertionError

2022-02-17 Thread Guido Günther
Hi Bastian, On Thu, Feb 17, 2022 at 03:50:37PM +0100, Bastian Germann wrote: > No team member reacted to Fabio's requests, so I am going to sponsor Fabio's > NMU. > The debdiff is enclosed. Seems I missed that. Thanks for NMUing. Cheers, -- Guido > diff -Nru

Processed: Bug#997367 marked as pending in virt-manager

2022-02-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #997367 [src:virt-manager] virt-manager: FTBFS: AssertionError: Command was: ./virt-xml test-for-virtxml --print-diff --define --add-device --host-device usb_device_4b3_4485_noserial --connect

Bug#1005773: ortools-samples: ships /usr/bin/knapsack, /usr/bin/tsp

2022-02-17 Thread Agathe Porte
Hi Andreas, On Mon, 14 Feb 2022 18:31:03 +0100 Andreas Beckmann wrote: > during a test with piuparts I noticed your package failed to install > because it tries to overwrite other packages files. > > I do not think that Breaks+Replaces would be an appropriate solution in > this case. > > Given

Bug#997367: virt-manager: FTBFS: AssertionError

2022-02-17 Thread Bastian Germann
No team member reacted to Fabio's requests, so I am going to sponsor Fabio's NMU. The debdiff is enclosed.diff -Nru virt-manager-3.2.0/debian/changelog virt-manager-3.2.0/debian/changelog --- virt-manager-3.2.0/debian/changelog 2020-12-05 09:36:56.0 +0100 +++

Bug#1005930: nvidia-graphics-drivers-tesla-418: incompatible with xorg-server video ABI 25

2022-02-17 Thread Julien Cristau
Control: clone -1 -2 -3 -4 Control: reassign -2 xserver-xorg-video-nvidia-tesla-450 450.172.01-1 Control: retitle -2 nvidia-graphics-drivers-tesla-450: incompatible with xorg-server video ABI 25 Control: reassign -3 xserver-xorg-video-nvidia-tesla-460 460.106.00-1 Control: retitle -3

Processed: Re: Bug#1005930: nvidia-graphics-drivers-tesla-418: incompatible with xorg-server video ABI 25

2022-02-17 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 -3 -4 Bug #1005930 [src:nvidia-graphics-drivers-tesla-418] nvidia-graphics-drivers-tesla-418: incompatible with xorg-server video ABI 25 Bug 1005930 cloned as bugs 1005932-1005934 > reassign -2 xserver-xorg-video-nvidia-tesla-450 450.172.01-1 Bug

Bug#1005930: nvidia-graphics-drivers-tesla-418: incompatible with xorg-server video ABI 25

2022-02-17 Thread Julien Cristau
Source: nvidia-graphics-drivers-tesla-418 Version: 418.226.00-1 Severity: serious xorg-server's video ABI was recently bumped, and nvidia-graphics-drivers-tesla-418 only declares compatibility for up to v24. Cheers, Julien

Bug#1004873: marked as done (python-django-netfields: autopkgtest regression: runuser: not found)

2022-02-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Feb 2022 13:34:43 + with message-id and subject line Bug#1004873: fixed in python-django-netfields 1.2.4-3 has caused the Debian Bug report #1004873, regarding python-django-netfields: autopkgtest regression: runuser: not found to be marked as done. This means that

Processed: Re: python-epimodels: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

2022-02-17 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #1002335 [src:python-epimodels] python-epimodels: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 Added tag(s) upstream. > forwarded -1

Bug#1002335: python-epimodels: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

2022-02-17 Thread Andreas Tille
Control: tags -1 upstream Control: forwarded -1 https://github.com/fccoelho/epimodels/issues/4

Bug#1004873: marked as pending in python-django-netfields

2022-02-17 Thread Michael Fladischer
Control: tag -1 pending Hello, Bug #1004873 in python-django-netfields 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:

Processed: Bug#1004873 marked as pending in python-django-netfields

2022-02-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1004873 [src:python-django-netfields] python-django-netfields: autopkgtest regression: runuser: not found Added tag(s) pending. -- 1004873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004873 Debian Bug Tracking System Contact

Bug#1005920: marked as done (coq-doc: FTBFS: Error: Library "zarith" not found.)

2022-02-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Feb 2022 12:48:52 + with message-id and subject line Bug#1005920: fixed in coq-doc 8.15.0-2 has caused the Debian Bug report #1005920, regarding coq-doc: FTBFS: Error: Library "zarith" not found. to be marked as done. This means that you claim that the problem has

Bug#1003165: scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, ppc64el and s390x

2022-02-17 Thread Andreas Tille
Hi, Am Wed, Feb 16, 2022 at 12:09:23PM +0100 schrieb John Paul Adrian Glaubitz: > > So, I have skimmed over the build logs and one of the main issues is the use > of > -march flags to enforce a certain baseline [1]: > > powerpc64le-linux-gnu-gcc: error: unrecognized command-line option >

Processed: Bug#1005920 marked as pending in coq-doc

2022-02-17 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005920 [src:coq-doc] coq-doc: FTBFS: Error: Library "zarith" not found. Added tag(s) pending. -- 1005920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1005920: marked as pending in coq-doc

2022-02-17 Thread Julien Puydt
Control: tag -1 pending Hello, Bug #1005920 in coq-doc 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#1005924: roger-router: bump B-D to librm-dev (>= 2.2.2+really2.2.0)

2022-02-17 Thread Andreas Beckmann
Source: roger-router Version: 2.4.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) roger-router/experimental started to FTBFS when librm-dev was reverted to 2.2.2+really2.1.4-0.1 - please bump the build dependency accordingly. (There

Bug#965625: marked as done (libapache2-mod-authz-unixgroup: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-02-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Feb 2022 11:04:17 + with message-id and subject line Bug#965625: fixed in libapache2-mod-authz-unixgroup 1.1.0-1 has caused the Debian Bug report #965625, regarding libapache2-mod-authz-unixgroup: Removal of obsolete debhelper compat 5 and 6 in bookworm to be

Bug#999147: marked as done (libapache2-mod-authz-unixgroup: missing required debian/rules targets build-arch and/or build-indep)

2022-02-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Feb 2022 11:04:17 + with message-id and subject line Bug#999147: fixed in libapache2-mod-authz-unixgroup 1.1.0-1 has caused the Debian Bug report #999147, regarding libapache2-mod-authz-unixgroup: missing required debian/rules targets build-arch and/or build-indep

Processed: Forwarded report

2022-02-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 992164 https://github.com/calamares/calamares/issues/1889 Bug #992164 [calamares] calamares: Creating a new blank partition table GPT/UEFI results in failure Set Bug forwarded-to-address to

Bug#1005920: coq-doc: FTBFS: Error: Library "zarith" not found.

2022-02-17 Thread Andreas Beckmann
Source: coq-doc Version: 8.15.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, I cannot rebuild coq-doc in sid (minimal pbuilder chroot), it fails with [...] dh binary --with sphinxdoc dh_update_autotools_config dh_autoreconf debian/rules

Bug#994833: marked as done (OpenCL programs abort when intel-opencl-icd is installed)

2022-02-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Feb 2022 10:21:04 + with message-id and subject line Bug#994833: fixed in intel-compute-runtime 21.32.20609-2 has caused the Debian Bug report #994833, regarding OpenCL programs abort when intel-opencl-icd is installed to be marked as done. This means that you

Bug#1005912: hydrogen: autopkgtest regression on arm64 and ppc64el: H2Core::Instrument::dequeue(): Assertion `__queued > 0' failed.

2022-02-17 Thread Paul Gevers
Source: hydrogen Version: 1.1.1-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of hydrogen the autopkgtest of hydrogen fails in testing when that autopkgtest is run with the binary