Processed: severity of 1003893 is important

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1003893 important Bug #1003893 [pseudo] pseudo breaks tar and thereby building python2.7 Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 1003893:

Bug#979934: marked as done (jquery-caret.js: node-uglify is deprecated in favor of uglifyjs)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Feb 2022 07:33:33 + with message-id and subject line Bug#979934: fixed in jquery-caret.js 0.3.1+dfsg.1-3 has caused the Debian Bug report #979934, regarding jquery-caret.js: node-uglify is deprecated in favor of uglifyjs to be marked as done. This means that you

Bug#1005796: marked as done (libxmu: FTBFS on arch-indep buildd)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Feb 2022 07:33:40 + with message-id and subject line Bug#1005796: fixed in libxmu 2:1.1.3-3 has caused the Debian Bug report #1005796, regarding libxmu: FTBFS on arch-indep buildd to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: libxmu: FTBFS on arch-indep buildd

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1005796 [src:libxmu] libxmu: FTBFS on arch-indep buildd Added tag(s) patch. -- 1005796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1005796: libxmu: FTBFS on arch-indep buildd

2022-02-14 Thread Sebastiaan Couwenberg
Control: tags -1 patch The attached patch resolves the issue. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1From 4ca536e51e51850a7a93da8c173c5395828965fb Mon Sep 17 00:00:00 2001 From: Bas Couwenberg Date: Tue, 15 Feb

Bug#1005796: libxmu: FTBFS on arch-indep buildd

2022-02-14 Thread Bas Couwenberg
Source: libxmu Version: 2:1.1.3-2 Severity: serious Tags: ftbfs Justification: makes the package in question unusable or mostly so Control: affects -1 src:pdl Dear Maintainer, Your package FTBFS on the all buildd: dh_missing: error: missing files, aborting The following debhelper tools

Processed: libxmu: FTBFS on arch-indep buildd

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:pdl Bug #1005796 [src:libxmu] libxmu: FTBFS on arch-indep buildd Added indication that 1005796 affects src:pdl -- 1005796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005796 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: found 1005787 in 5:6.0.15-1

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1005787 5:6.0.15-1 Bug #1005787 [redis] redis: CVE-2022-0543 Marked as found in versions redis/5:6.0.15-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1005787:

Bug#1005632: marked as done (prettytable registers itself as version 0.0.0)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Feb 2022 03:33:51 + with message-id and subject line Bug#1005632: fixed in prettytable 2.5.0-2 has caused the Debian Bug report #1005632, regarding prettytable registers itself as version 0.0.0 to be marked as done. This means that you claim that the problem has

Processed: Bug#1005632 marked as pending in prettytable

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005632 [python3-prettytable] prettytable registers itself as version 0.0.0 Added tag(s) pending. -- 1005632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1005632: marked as pending in prettytable

2022-02-14 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #1005632 in prettytable 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#1005789: libpmix2: unable to open mca_pmix_ext3x: cannot open shared object file: No such file or directory

2022-02-14 Thread Drew Parsons
Package: libpmix2 Version: 4.1.2-1 Severity: serious Looks like something is missing in the new pmix package. mpi4py tests show the problem, referring to a missing mca_pmix_ext3x autopkgtest [03:24:44]: test command1: OMPI_MCA_rmaps_base_oversubscribe=yes mpiexec -n 5 python3 test/runtests.py

Bug#1005395: marked as done (src:gem: fails to migrate to testing for too long: FTBFS on ppc64el)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 23:18:45 + with message-id and subject line Bug#1005395: fixed in gem 1:0.94-7 has caused the Debian Bug report #1005395, regarding src:gem: fails to migrate to testing for too long: FTBFS on ppc64el to be marked as done. This means that you claim that the

Bug#1005787: redis: CVE-2022-0543

2022-02-14 Thread Chris Lamb
Package: redis Version: 5:5.0.14-1+deb10u1 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, A vulnerability was published for redis as CVE-2022-0543[0]. This is the placeholder Debian bug which will be renamed and fleshed out later with more details once it has become

Bug#1005574: marked as done (gnome-characters: FTBFS: ../data/meson.build:49:5: ERROR: Function does not take positional arguments.)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 22:05:04 + with message-id and subject line Bug#1005574: fixed in gnome-characters 41.0-3 has caused the Debian Bug report #1005574, regarding gnome-characters: FTBFS: ../data/meson.build:49:5: ERROR: Function does not take positional arguments. to be

Bug#1005574: marked as done (gnome-characters: FTBFS: ../data/meson.build:49:5: ERROR: Function does not take positional arguments.)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 21:38:40 + with message-id and subject line Bug#1005574: fixed in gnome-characters 41.0-2 has caused the Debian Bug report #1005574, regarding gnome-characters: FTBFS: ../data/meson.build:49:5: ERROR: Function does not take positional arguments. to be

Bug#1005574: marked as pending in gnome-characters

2022-02-14 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #1005574 in gnome-characters 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#1005574 marked as pending in gnome-characters

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005574 [src:gnome-characters] gnome-characters: FTBFS: ../data/meson.build:49:5: ERROR: Function does not take positional arguments. Added tag(s) pending. -- 1005574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005574 Debian Bug

Processed: lower prio

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1005369 normal Bug #1005369 [xserver-xorg-core] xserver-xorg-core: Breaks middle button trackpoint scrolling Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1005522: marked as done (gnome-disk-utility: FTBFS: ../data/meson.build:13:7: ERROR: Function does not take positional arguments.)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 20:43:42 + with message-id and subject line Re: Bug#1005522: gnome-disk-utility: FTBFS: ../data/meson.build:13:7: ERROR: Function does not take positional arguments. has caused the Debian Bug report #1005522, regarding gnome-disk-utility: FTBFS:

Bug#1005311: forcing dependency is not enough, at least for optirun

2022-02-14 Thread Gianluigi Tiesi
optirun glxinfo optirun glxinfo [ 1566.529702] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Unable to locate/open config directory: "/etc/bumblebee/xorg.conf.d" [ 1566.529735] [ERROR]Aborting because fallback start is disabled. in xorg log: [ 1566.527] (II) NVIDIA dlloader X

Bug#1005779: djangorestframework: autopkgtest needs update for new version of pygments

2022-02-14 Thread Paul Gevers
Source: djangorestframework Version: 3.12.4-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, pygme...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:pygments Dear maintainer(s), With a (not so) recent upload of

Processed: djangorestframework: autopkgtest needs update for new version of pygments

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:pygments Bug #1005779 [src:djangorestframework] djangorestframework: autopkgtest needs update for new version of pygments Added indication that 1005779 affects src:pygments -- 1005779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005779

Bug#1005778: src:pypandoc: fails to migrate to testing for too long: autopkgtest failure

2022-02-14 Thread Paul Gevers
Source: pypandoc Version: 1.6.4+ds0-1 Severity: serious Control: close -1 1.7.2+ds0-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60

Processed: src:pypandoc: fails to migrate to testing for too long: autopkgtest failure

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.7.2+ds0-1 Bug #1005778 [src:pypandoc] src:pypandoc: fails to migrate to testing for too long: autopkgtest failure Marked as fixed in versions pypandoc/1.7.2+ds0-1. Bug #1005778 [src:pypandoc] src:pypandoc: fails to migrate to testing for too long:

Bug#1001498: marked as done (No OpenSSL 3.0 support in XCA 2.3.0 and later)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 14:12:59 -0500 with message-id <759a7bb3-f92e-fbe3-1ea5-92ca53847...@ubuntu.com> and subject line Patches Available and Included has caused the Debian Bug report #1001498, regarding No OpenSSL 3.0 support in XCA 2.3.0 and later to be marked as done. This means

Processed: bug 1005747 is forwarded to https://tracker.freecad.org/view.php?id=4809, tagging 1005747 ...

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1005747 https://tracker.freecad.org/view.php?id=4809 Bug #1005747 [src:freecad] freecad: CVE-2021-45844 - Improper sanitization in the invocation of ODA File Converter Set Bug forwarded-to-address to

Processed: your mail

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # XCA update includes upstream fixes. > fixed 1001498 xca/2.4.0-2 Bug #1001498 [src:xca] No OpenSSL 3.0 support in XCA 2.3.0 and later Marked as fixed in versions xca/2.4.0-2. > End of message, stopping processing here. Please contact me if you

Bug#1005612: marked as done (drawing: FTBFS: ../help/meson.build:2:6: ERROR: Program 'itstool' not found or not executable)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 19:04:04 + with message-id and subject line Bug#1005612: fixed in drawing 0.8.5-2 has caused the Debian Bug report #1005612, regarding drawing: FTBFS: ../help/meson.build:2:6: ERROR: Program 'itstool' not found or not executable to be marked as done. This

Bug#1005622: [Pkg-utopia-maintainers] Bug#1005622: libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below

2022-02-14 Thread Michael Biebl
Am 14.02.22 um 18:51 schrieb Michael Biebl: I agree. Apparently this isn't the first time that dmraid has been bitten by this split-usr issue (and having to manually fiddle with the creation of the .so symlink) [1] Getting rid of this unnecessary complexity would solve this once and for

Bug#1005622: [Pkg-utopia-maintainers] Bug#1005622: libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below

2022-02-14 Thread Michael Biebl
Am 14.02.22 um 17:55 schrieb Helmut Grohne: We have this moratorium in place that says you should not move files from / to /usr, because it could go bad when moving files. ttbomk, those "bad" things only happen if you move files from /lib to /usr (under the same name) but *also* move it

Bug#1005622: [Pkg-utopia-maintainers] Bug#1005622: libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below

2022-02-14 Thread Helmut Grohne
Control: tags -1 + patch Hi Michael, On Sun, Feb 13, 2022 at 02:20:26PM +0100, Michael Biebl wrote: > I suspect the following: > > in 1.0.0.rc16-10 /usr/lib/libdmraid.so is a dangling symlink to > /lib/libdmraid.so.1.0.0.rc16 (yay for those pointless split-usr shenanigans, > can we please have

Processed: Re: [Pkg-utopia-maintainers] Bug#1005622: libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1005622 [libdmraid-dev] libblockdev: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below Added tag(s) patch. -- 1005622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005622 Debian Bug

Bug#1005586: marked as done (gnome-font-viewer: FTBFS: ../src/meson.build:42:5: ERROR: Function does not take positional arguments.)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 17:42:48 + with message-id and subject line Bug#1005586: fixed in gnome-font-viewer 41.0-2 has caused the Debian Bug report #1005586, regarding gnome-font-viewer: FTBFS: ../src/meson.build:42:5: ERROR: Function does not take positional arguments. to be

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

2022-02-14 Thread Andreas Beckmann
Package: ortools-samples Version: 8.2+ds-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, 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

Processed: [bts-link] source package src:zope.exceptions

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:zope.exceptions > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user

Bug#1005772: go-rpmdb: trying to overwrite '/usr/bin/rpmdb', which is also in package rpm

2022-02-14 Thread Andreas Beckmann
Package: go-rpmdb Version: 0.0~git20210911.73bd0ce-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following

Processed: Bug#1005586 marked as pending in gnome-font-viewer

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005586 [src:gnome-font-viewer] gnome-font-viewer: FTBFS: ../src/meson.build:42:5: ERROR: Function does not take positional arguments. Added tag(s) pending. -- 1005586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005586 Debian Bug

Bug#1005586: marked as pending in gnome-font-viewer

2022-02-14 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #1005586 in gnome-font-viewer 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: tagging 1005458

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1005458 + pending Bug #1005458 [src:spirv-llvm-translator] spirv-llvm-translator: FTBFS: SPIRVOpCode.h:52:31: error: ‘OpConstFunctionPointerINTEL’ was not declared in this scope Added tag(s) pending. > thanks Stopping processing here.

Bug#1005103: marked as done (gem: FTBFS with gmerlin-avdecoder 2.0)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 17:03:48 + with message-id and subject line Bug#1005103: fixed in gem 1:0.94-6 has caused the Debian Bug report #1005103, regarding gem: FTBFS with gmerlin-avdecoder 2.0 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1005462: xserver-xorg-video-mach64: FTBFS: ../../src/aticonfig.c:315:63: error: ‘ValueUnion’ has no member named ‘bool’; did you mean ‘boolean’?

2022-02-14 Thread Sven Joachim
Control: tags -1 + patch On 2022-02-13 08:03 +0100, Lucas Nussbaum wrote: > Source: xserver-xorg-video-mach64 > Version: 6.9.6-3 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220212 ftbfs-bookworm > > Hi, > > During a rebuild

Processed: Re: Bug#1005462: xserver-xorg-video-mach64: FTBFS: ../../src/aticonfig.c:315:63: error: ‘ValueUnion’ has no member named ‘bool’; did you mean ‘boolean’?

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1005462 [src:xserver-xorg-video-mach64] xserver-xorg-video-mach64: FTBFS: ../../src/aticonfig.c:315:63: error: ‘ValueUnion’ has no member named ‘bool’; did you mean ‘boolean’? Added tag(s) patch. -- 1005462:

Bug#1005480: xserver-xorg-video-trident: FTBFS: ../../src/trident.h:41:10: fatal error: xf86RamDac.h: No such file or directory

2022-02-14 Thread Sven Joachim
Control: tags -1 + patch On 2022-02-13 08:03 +0100, Lucas Nussbaum wrote: > Source: xserver-xorg-video-trident > Version: 1:1.3.8-2 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220212 ftbfs-bookworm > > Hi, > > During a

Processed: Re: Bug#1005480: xserver-xorg-video-trident: FTBFS: ../../src/trident.h:41:10: fatal error: xf86RamDac.h: No such file or directory

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1005480 [src:xserver-xorg-video-trident] xserver-xorg-video-trident: FTBFS: ../../src/trident.h:41:10: fatal error: xf86RamDac.h: No such file or directory Added tag(s) patch. -- 1005480:

Bug#997120:

2022-02-14 Thread Andreas Tille
Hi Jose, Am Mon, Feb 14, 2022 at 12:18:47AM +0100 schrieb Jose Luis Rivero: > > You are welcome. This bug is preventing one of my packages (Gazebo) from > being > migrated to testing. Could we please upload a revision bump of the current > version to solve this issue while we work on 5.0.2?

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

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 15:50:02 + with message-id and subject line Bug#1002325: fixed in python-envisage 6.0.1-1 has caused the Debian Bug report #1002325, regarding python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code

Bug#979907: marked as done (jquery-reflection: node-uglify is deprecated in favor of uglifyjs)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 15:34:17 + with message-id and subject line Bug#979907: fixed in jquery-reflection 1.1-2 has caused the Debian Bug report #979907, regarding jquery-reflection: node-uglify is deprecated in favor of uglifyjs to be marked as done. This means that you claim

Bug#979906: marked as done (jquery-coolfieldset: node-uglify is deprecated in favor of uglifyjs)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 15:34:10 + with message-id and subject line Bug#979906: fixed in jquery-coolfieldset 1.0.1-3 has caused the Debian Bug report #979906, regarding jquery-coolfieldset: node-uglify is deprecated in favor of uglifyjs to be marked as done. This means that you

Processed: severity of 1005747 is grave

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1005747 grave Bug #1005747 [src:freecad] freecad: CVE-2021-45844 - Improper sanitization in the invocation of ODA File Converter Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need

Bug#979943: marked as done (jquery-watermark: node-uglify is deprecated in favor of uglifyjs)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 15:18:47 + with message-id and subject line Bug#979943: fixed in jquery-watermark 3.1.4-2 has caused the Debian Bug report #979943, regarding jquery-watermark: node-uglify is deprecated in favor of uglifyjs to be marked as done. This means that you claim

Processed: Bug#979906 marked as pending in jquery-coolfieldset

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #979906 [jquery-coolfieldset] jquery-coolfieldset: node-uglify is deprecated in favor of uglifyjs Added tag(s) pending. -- 979906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979906 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#979906: marked as pending in jquery-coolfieldset

2022-02-14 Thread Yadd
Control: tag -1 pending Hello, Bug #979906 in jquery-coolfieldset 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#979907: marked as pending in jquery-reflection

2022-02-14 Thread Yadd
Control: tag -1 pending Hello, Bug #979907 in jquery-reflection 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#979907 marked as pending in jquery-reflection

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #979907 [jquery-reflection] jquery-reflection: node-uglify is deprecated in favor of uglifyjs Added tag(s) pending. -- 979907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979907 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#979911: marked as done (jquery-lazyload: node-uglify is deprecated in favor of uglifyjs)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 15:07:10 + with message-id and subject line Bug#979911: fixed in jquery-lazyload 1.9.7-2 has caused the Debian Bug report #979911, regarding jquery-lazyload: node-uglify is deprecated in favor of uglifyjs to be marked as done. This means that you claim

Processed: Bug#979943 marked as pending in jquery-watermark

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #979943 [jquery-watermark] jquery-watermark: node-uglify is deprecated in favor of uglifyjs Added tag(s) pending. -- 979943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979943 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#979943: marked as pending in jquery-watermark

2022-02-14 Thread Yadd
Control: tag -1 pending Hello, Bug #979943 in jquery-watermark 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#1005623: marked as done (python-pydot-ng: FTBFS: tests failed)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 15:00:56 + with message-id and subject line Bug#1005756: Removed package(s) from unstable has caused the Debian Bug report #1005623, regarding python-pydot-ng: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been

Bug#979911: marked as pending in jquery-lazyload

2022-02-14 Thread Yadd
Control: tag -1 pending Hello, Bug #979911 in jquery-lazyload 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#979911 marked as pending in jquery-lazyload

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #979911 [jquery-lazyload] jquery-lazyload: node-uglify is deprecated in favor of uglifyjs Added tag(s) pending. -- 979911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979911 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1005758: hiera-eyaml: eyaml command is unusable with ruby-rubygems 3.3.5-2

2022-02-14 Thread intrigeri
Package: hiera-eyaml Version: 3.2.2-2 Severity: serious Hi, I usually use "eyaml edit FILE.eyaml" to edit files. It's currently broken for me on sid. Even this simpler command fails: $ eyaml version Traceback (most recent call last): 7: from /bin/eyaml:25:in `' 6: from

Bug#1002325: [Help] Re: python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

2022-02-14 Thread Stefano Rivera
Hi Andreas (2022.02.14_13:00:13_+) > I switched to Github downloads and followed the Fedora approach. > I'd be happy if you could review my changes[1]. That looks like it's all doing the right thing, I only have minor nit-picks from review: I'd suggest starting the multi-line shell thing

Bug#1005608: marked as done (lomiri-url-dispatcher: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 2)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 13:49:01 + with message-id and subject line Bug#1005608: fixed in lomiri-url-dispatcher 0.1.0-6 has caused the Debian Bug report #1005608, regarding lomiri-url-dispatcher: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test

Processed: bug 1005518 is forwarded to https://gitlab.gnome.org/GNOME/frogr/-/issues/8

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1005518 https://gitlab.gnome.org/GNOME/frogr/-/issues/8 Bug #1005518 [src:frogr] frogr: FTBFS: ../data/meson.build:32:5: ERROR: Function does not take positional arguments. Set Bug forwarded-to-address to

Bug#1005608: marked as pending in lomiri-url-dispatcher

2022-02-14 Thread Mike Gabriel
Control: tag -1 pending Hello, Bug #1005608 in lomiri-url-dispatcher 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#1005608 marked as pending in lomiri-url-dispatcher

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005608 [src:lomiri-url-dispatcher] lomiri-url-dispatcher: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 2 Added tag(s) pending. -- 1005608:

Bug#1005518: frogr: FTBFS: ../data/meson.build:32:5: ERROR: Function does not take positional arguments.

2022-02-14 Thread Alberto Garcia
On Sun, Feb 13, 2022 at 08:27:19AM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Configuring org.gnome.frogr.desktop.in using configuration > > > > ../data/meson.build:32:5: ERROR: Function does not take positional > >

Bug#1005755: debian/copyright missing GPL-3+ copyright statements

2022-02-14 Thread David Mohammed
Package: gnome-control-center Version: 1:41.2-2 Severity: serious Hi, gnome-control-center has several files that are stated as GPL-3+ in their source headers for example - panels/applications/search.h panels/applications/cc-applications-panel.h panels/network/cc-qr-code.h In the package,

Bug#1005754: libopenmpi3: linked library libpmix.so.2 not found

2022-02-14 Thread Markus Blatt
Package: libopenmpi3 Version: 4.1.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, I just updated my chroot of cowbuilder to build my own package that runs some parallel programs during make test. When these are run I get errors like this 7/27 Test #16:

Bug#1005103: marked as pending in gem

2022-02-14 Thread IOhannes zmölnig
Control: tag -1 pending Hello, Bug #1005103 in gem 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#1005103 marked as pending in gem

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1005103 [gem] gem: FTBFS with gmerlin-avdecoder 2.0 Added tag(s) pending. -- 1005103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1005632: python-novaclient: FTBFS: make[1]: pyversions: No such file or directory

2022-02-14 Thread Thomas Goirand
Hi Lucas & Sandro, It looks like the issue isn't in novaclient, but in prettytable. Indeed, the package registers itself as version 0.0.0 (ie: it shows in the egg-info directory name and in the generated PKG-INFO file). This breaks the version detection from python3-novaclient, which leads to

Bug#1005725: gavodachs2-server: fails to install with new python3-twisted.

2022-02-14 Thread Ole Streicher
Hi Markus, On 14.02.22 13:47, Markus Demleitner wrote: My plan right now would be to fix this in unstable by just packaging release 2.6, which ought to happen in May 2022 and will contain the patch (or whatever else). If that's a major problem for someone, speak up and I'll try to provide a

Processed: retitle 1005632 prettytable registers itself as version 0.0.0

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1005632 prettytable registers itself as version 0.0.0 Bug #1005632 [python3-prettytable] python-novaclient: FTBFS: make[1]: pyversions: No such file or directory Changed Bug title to 'prettytable registers itself as version 0.0.0' from

Processed: reassign 1005632 python3-prettytable

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1005632 python3-prettytable Bug #1005632 [src:python-novaclient] python-novaclient: FTBFS: make[1]: pyversions: No such file or directory Bug reassigned from package 'src:python-novaclient' to 'python3-prettytable'. No longer marked as

Bug#1002325: [Help] Re: python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

2022-02-14 Thread Andreas Tille
Hi Scott, thanks a lot for your hints. Am Sun, Feb 13, 2022 at 10:28:15PM -0500 schrieb Scott Talbert: > I spent some time looking into this. The problem is that upstream includes > binary eggs (which are Python version specific) as part of its test suite. > The problem here is that there are

Bug#1005725: gavodachs2-server: fails to install with new python3-twisted.

2022-02-14 Thread Markus Demleitner
On Sun, Feb 13, 2022 at 11:57:56PM +, peter green wrote: > > Exception payload: module 'twisted.web.template' has no attribute > > '_ToStan' > > dpkg: error processing package gavodachs2-server (--configure): > > installed gavodachs2-server package post-installation script subprocess > >

Bug#1005397: src:ruby2.7: fails to migrate to testing for too long: FTBFS on ppc64el

2022-02-14 Thread Lucas Kanashiro
AFAIK we are not working to fix it (if some of the other maintainers is actively working on this, correct me please). We are willing to ship ruby3.0 in bookworm (instead of ruby2.7), but at the moment we are waiting for the release team to start the ruby2.7 removal. Hopefully, ruby2.7 will be

Bug#998995: marked as done (openoffice.org-en-au: missing required debian/rules targets build-arch and/or build-indep)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 11:36:08 + with message-id and subject line Bug#998995: fixed in openoffice.org-en-au 2.1-5.6 has caused the Debian Bug report #998995, regarding openoffice.org-en-au: missing required debian/rules targets build-arch and/or build-indep to be marked as

Bug#965757: marked as done (openoffice.org-en-au: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 11:36:08 + with message-id and subject line Bug#965757: fixed in openoffice.org-en-au 2.1-5.6 has caused the Debian Bug report #965757, regarding openoffice.org-en-au: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This

Bug#965741: marked as done (myspell-sq: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 11:35:56 + with message-id and subject line Bug#965741: fixed in myspell-sq 1.6.4-1.2 has caused the Debian Bug report #965741, regarding myspell-sq: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim

Bug#965584: marked as done (hunspell-ar: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 11:35:37 + with message-id and subject line Bug#965584: fixed in hunspell-ar 3.2-1.2 has caused the Debian Bug report #965584, regarding hunspell-ar: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim

Processed: hunspell-ar: diff for NMU version 3.2-1.2

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tags 965584 + patch Bug #965584 [src:hunspell-ar] hunspell-ar: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965584 + pending Bug #965584 [src:hunspell-ar] hunspell-ar: Removal of obsolete debhelper compat 5 and 6 in bookworm

Bug#965584: hunspell-ar: diff for NMU version 3.2-1.2

2022-02-14 Thread Jonas Smedegaard
Control: tags 965584 + patch Control: tags 965584 + pending Dear maintainer, I've prepared an NMU for hunspell-ar (versioned as 3.2-1.2) and uploaded it without delay, due to fixing release-critical bug. Regards, - Jonas diff -Nru hunspell-ar-3.2/debian/changelog

Bug#965857: marked as done (uzbek-wordlist: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 11:20:10 + with message-id and subject line Bug#965857: fixed in uzbek-wordlist 0.6-5 has caused the Debian Bug report #965857, regarding uzbek-wordlist: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you

Processed: myspell-sq: diff for NMU version 1.6.4-1.2

2022-02-14 Thread Debian Bug Tracking System
Processing control commands: > tags 965741 + patch Bug #965741 [src:myspell-sq] myspell-sq: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965741 + pending Bug #965741 [src:myspell-sq] myspell-sq: Removal of obsolete debhelper compat 5 and 6 in bookworm

Bug#965741: myspell-sq: diff for NMU version 1.6.4-1.2

2022-02-14 Thread Jonas Smedegaard
Control: tags 965741 + patch Control: tags 965741 + pending Dear maintainer, I've prepared an NMU for myspell-sq (versioned as 1.6.4-1.2) and uploaded it without delay, due to fixing release-critical bugs. Regards, - Jonas diff -Nru myspell-sq-1.6.4/debian/changelog

Bug#965740: marked as done (myspell-hy: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 10:49:02 + with message-id and subject line Bug#965740: fixed in myspell-hy 0.20.0-2.2 has caused the Debian Bug report #965740, regarding myspell-hy: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim

Bug#999266: marked as done (myspell-hy: missing required debian/rules targets build-arch and/or build-indep)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 10:49:02 + with message-id and subject line Bug#999266: fixed in myspell-hy 0.20.0-2.2 has caused the Debian Bug report #999266, regarding myspell-hy: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means

Bug#1005481: marked as done (halide: FTBFS: clang: error: linker command failed with exit code 1 (use -v to see invocation))

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 13:49:25 +0300 with message-id and subject line has caused the Debian Bug report #1005481, regarding halide: FTBFS: clang: error: linker command failed with exit code 1 (use -v to see invocation) to be marked as done. This means that you claim that the

Bug#1001823: marked as done (Ardentryst near-unplayable after Python3 port)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 10:48:41 + with message-id and subject line Bug#1001823: fixed in ardentryst 1.71-9 has caused the Debian Bug report #1001823, regarding Ardentryst near-unplayable after Python3 port to be marked as done. This means that you claim that the problem has been

Processed (with 6 errors): Re: Processed (with 1 error): Re: Processed (with 1 error): your mail

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1005666 1005481 Bug #1005666 {Done: Sylvestre Ledru } [src:llvm-toolchain-13] iwyu: FTBFS: The imported target "RemoteIndexProto" references the file "/usr/lib/llvm-13/lib/libRemoteIndexProto.a" but this file does not exist. Bug

Bug#1005401: marked as done (Fails to build due to netfilter change in Linux 5.15)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 10:34:06 + with message-id and subject line Bug#1005401: fixed in iptables-netflow 2.6-3 has caused the Debian Bug report #1005401, regarding Fails to build due to netfilter change in Linux 5.15 to be marked as done. This means that you claim that the

Bug#1004964: marked as done (lbzip2: Current package (version 2.5-2.2) is empty besides /usr/share/doc folder. No binary.)

2022-02-14 Thread Debian Bug Tracking System
Your message dated Mon, 14 Feb 2022 10:34:11 + with message-id and subject line Bug#1004964: fixed in lbzip2 2.5-2.3 has caused the Debian Bug report #1004964, regarding lbzip2: Current package (version 2.5-2.2) is empty besides /usr/share/doc folder. No binary. to be marked as done. This

Bug#1001823: Bug#733469: Patch to fix both issues

2022-02-14 Thread Markus Koschany
Hi, Am Donnerstag, dem 10.02.2022 um 18:55 +0100 schrieb Jens Rottmann: > Tags: patch > > I dug deeper, turns out I was wrong, the 2 crashes when renaming or deleting > saves weren't related after all. > > Anyway, I made a patch fixing both of them. Note that it's meant to be > applied _after_

Processed (with 1 error): Re: Processed (with 1 error): your mail

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1005345 1005481 1005666 1005690 Bug #1005345 {Done: Sylvestre Ledru } [src:llvm-toolchain-13] autopkgtest failure due to removed libRemoteIndex*.a Bug #1005666 {Done: Sylvestre Ledru } [src:llvm-toolchain-13] iwyu: FTBFS: The imported

Processed (with 1 error): your mail

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1005481 1005666 Bug #1005481 [clang-13] halide: FTBFS: clang: error: linker command failed with exit code 1 (use -v to see invocation) Unable to merge bugs because: done of #1005666 is 'Sylvestre Ledru ' not '' affects of #1005666 is

Processed: your mail

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1005481 clang-13 Bug #1005481 [src:halide] halide: FTBFS: clang: error: linker command failed with exit code 1 (use -v to see invocation) Bug reassigned from package 'src:halide' to 'clang-13'. No longer marked as found in versions

Processed: retitle 1005467 mistral FTBFS with Tenacity >= 8.0.1

2022-02-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1005467 mistral FTBFS with Tenacity >= 8.0.1 Bug #1005467 [src:mistral] mistral: FTBFS: AttributeError: 'Retrying' object has no attribute 'call' Changed Bug title to 'mistral FTBFS with Tenacity >= 8.0.1' from 'mistral: FTBFS:

  1   2   >