Processed: severity of 1031379 is important, tagging 1031379

Processing commands for cont...@bugs.debian.org: > severity 1031379 important Bug #1031379 [kaffeine] kaffeine: does not work Severity set to 'important' from 'grave' > tags 1031379 = moreinfo Bug #1031379 [kaffeine] kaffeine: does not work Removed tag(s) sid and bookworm. > thanks Stopping

Bug#1031460: marked as done (enlighten: FTBFS: AssertionError: '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.00 K[105 chars] s/B' != '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.

Your message dated Sun, 26 Feb 2023 07:19:06 + with message-id and subject line Bug#1031460: fixed in enlighten 1.11.2-1 has caused the Debian Bug report #1031460, regarding enlighten: FTBFS: AssertionError: '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.00 K[105 chars] s/B' !=

Bug#1031974: python3-pydle: import fails: AttributeError: module 'asyncio' has no attribute 'coroutine'

Package: python3-pydle Version: 0.9.4 Severity: serious Dear Maintainer, This import fails in a Sid chroot: Python 3.11.2 (main, Feb 12 2023, 00:48:52) [GCC 12.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import pydle Traceback (most recent call

Bug#1031971: libxfce4panel-2.0-dev fails to build with valac installed

Package: libxfce4panel-2.0-dev Version: 4.18.1-1 Severity: serious Tags: ftbfs patch Justification: fails to build from source (but built successfully in the past) Dear Maintainer, To reproduce the problem please follow these steps: $ sudo apt install valac $ apt-get source

Bug#1031888: emacs-nox: bullseye-security update fails to install on mips64el

On Fri, Feb 24, 2023 at 06:32:46PM +, Adam D. Barratt wrote: > Source: emacs > Version: 1:27.1+1-3.1+deb11u2 > Severity: grave > Control: affects -1 + security.debian.org > Control: affects -1 + release.debian.org > X-Debbugs-Cc: t...@security.debian.org > X-Debbugs-Cc:

Bug#1031968: libxfconf-0-dev fails to build with valac installed

Package: libxfconf-0-dev Version: 4.18.0-1 Severity: serious Tags: ftbfs patch Justification: fails to build from source (but built successfully in the past) Dear Maintainer, To reproduce the problem please follow these steps: $ sudo apt install valac $ apt-get source libxfconf-0-dev $ cd

Bug#1031967: libxfce4util-dev fails to build with valac installed

Package: libxfce4util-dev Version: 4.18.1-1 Severity: serious Tags: ftbfs patch Justification: fails to build from source (but built successfully in the past) Dear Maintainer, to repeat the problem, please follow these steps: $ sudo apt install valac $ apt-get source libxfce4util-dev $ cd

Bug#1031966: python-pydata-sphinx-theme-doc is empty

Package: python-pydata-sphinx-theme-doc Version: 0.7.2-2 Severity: serious /. /usr /usr/share /usr/share/doc /usr/share/doc/python-pydata-sphinx-theme-doc /usr/share/doc/python-pydata-sphinx-theme-doc/changelog.Debian.gz /usr/share/doc/python-pydata-sphinx-theme-doc/changelog.gz

Bug#1031965: python3-pyodc-docs is empty

Package: python3-pyodc-docs Version: 1.1.2-1 Severity: serious /. /usr /usr/share /usr/share/doc /usr/share/doc/python3-pyodc-docs /usr/share/doc/python3-pyodc-docs/changelog.Debian.gz /usr/share/doc/python3-pyodc-docs/changelog.gz /usr/share/doc/python3-pyodc-docs/copyright

Processed: libtrilinos-{globi,opti}pack-{13.2,dev} are empty

Processing control commands: > affects -1 libtrilinos-globipack-13.2 libtrilinos-optipack-13.2 > libtrilinos-globipack-dev libtrilinos-optipack-dev Bug #1031964 [src:trilinos] libtrilinos-{globi,opti}pack-{13.2,dev} are empty Added indication that 1031964 affects libtrilinos-globipack-13.2,

Bug#1031964: libtrilinos-{globi,opti}pack-{13.2,dev} are empty

Source: trilinos Version: 13.2.0-3 Severity: serious Control: affects -1 libtrilinos-globipack-13.2 libtrilinos-optipack-13.2 libtrilinos-globipack-dev libtrilinos-optipack-dev /. /usr /usr/share /usr/share/doc /usr/share/doc/libtrilinos-globipack-13.2

Bug#1031961: qtmir FTBFS on several architectures: symbol differences

Source: qtmir Version: 0.8.0~git20230223.bd21224-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=qtmir=0.8.0%7Egit20230223.bd21224-1

Bug#1031960: cpufetch FTBFS on ppc64/ppc64el

Source: cpufetch Version: 1.03-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=cpufetch=1.03-2 ... src/common/printer.c: In function ‘print_ascii_generic’: src/common/printer.c:487:23: error: ‘ATTRIBUTE_CPU_NUM’ undeclared (first use in this function); did you mean

Processed: vdr: diff for NMU version 2.6.0-1.1

Processing control commands: > tags 1026310 + pending Bug #1026310 [vdr-dev] vdr-dev: dh_vdrplugin_depends fail with "error: Bug in helper:" Bug #1026475 [vdr-dev] vdr-plugin-remote: FTBFS: make: *** [debian/rules:7: binary] Error 25 Bug #1026533 [vdr-dev] vdr-plugin-femon: FTBFS: make: ***

Bug#1026310: vdr: diff for NMU version 2.6.0-1.1

Control: tags 1026310 + pending Dear maintainer, I've prepared an NMU for vdr (versioned as 2.6.0-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru vdr-2.6.0/debian/changelog vdr-2.6.0/debian/changelog --- vdr-2.6.0/debian/changelog

Bug#1024589: dislocker: FTBFS with ruby3.1: mv: cannot stat '/<>/debian/tmp/usr/lib/libdislocker*': No such file or directory

On Tue, Feb 07, 2023 at 03:10:27PM +0100, Santiago Vila wrote: > severity 1024589 serious > thanks > > Hi. I can reproduce this, and I believe everybody who will try > to build the package using sbuild right now in unstable should also > be able to reproduce it. > > (If you still can't reproduce

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

It's too late for a trip through New and Bookworm. We probably should have done it before, but not now. I think setting a minimum version of the current package will be sufficient and about all we can do now anyway. Scott K On February 25, 2023 10:26:50 PM UTC, Sebastian Andrzej Siewior

Processed: Re: Bug#1030829: mmc-utils: FTBFS on ppc64el with error: ‘cnt’ may be used uninitialized

Processing control commands: > severity -1 normal Bug #1030829 [mmc-utils] mmc-utils: FTBFS on ppc64el with error: ‘cnt’ may be used uninitialized Severity set to 'normal' from 'serious' -- 1030829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030829 Debian Bug Tracking System Contact

Bug#1030829: mmc-utils: FTBFS on ppc64el with error: ‘cnt’ may be used uninitialized

Control: severity -1 normal On Tue, Feb 07, 2023 at 04:38:20PM -0500, Nick Rosbrook wrote: > Package: mmc-utils > Severity: serious > Tags: patch ftbfs > Justification: fails to build from source (but built successfully in the past) > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu

Bug#1031904: marked as done (firmware-ath9k-htc: insufficient coordination around moving files between packages)

Your message dated Sat, 25 Feb 2023 23:43:04 +0100 with message-id <0955c399-3144-fd25-40c5-d5a42a82d...@debian.org> and subject line Re: Bug#1031904: firmware-ath9k-htc: insufficient coordination around moving files between packages has caused the Debian Bug report #1031904, regarding

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

On 25 February 2023 16:20:45 UTC, Scott Kitterman wrote: >True. > >I'm not a C programmer, so I may be unduly concerned about the maintenance >load. I'll defer to your judgement. I'm going to throw this on my machine to get more testing - more than just the test suite. What about going

Bug#1031952: marked as forwarded (gettext: Missing source for an installed windows binary)

Your message dated Sat, 25 Feb 2023 23:21:34 +0100 with message-id <76103372-aecb-81e3-6e1a-dd89f7fdd...@debian.org> has caused the report #1031952, regarding gettext: Missing source for an installed windows binary to be marked as having been forwarded to the upstream software author(s)

Bug#1031952: Fwd: Bug#1031952: gettext: Missing source for an installed windows binary

Hello. I've received the following report from the Debian bug system. Summary: There is no source for gettext-tools/m4/csharpexec-test.exe. Note: The Debian package disabled the mono stuff in version 0.17-7 (dated 2009-08-17), so I guess this file is one without which we could live, but I

Bug#1028680: libzypp: diff for NMU version 17.25.7-2.4

On Sa 25 Feb 2023 21:59:19 CET, Adrian Bunk wrote: Control: tags 1028680 + patch Control: tags 1028680 + pending Dear maintainer, I've prepared an NMU for libzypp (versioned as 17.25.7-2.4) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian Thanks

Bug#1031950: libgeo-distance-perl should add Breaks and Replaces on libgeo-distance-xs-perl

On Sat, 25 Feb 2023 23:13:12 +0200, Adrian Bunk wrote: > Package: libgeo-distance-perl > Version: 0.25-2 > Severity: serious > > Upgrading libgeo-distance-perl from bullseye to bookworm should > remove libgeo-distance-xs-perl since it is now useless. Good point, thank you. I just don't

Processed: drslib: diff for NMU version 0.3.1.p3-2.1

Processing control commands: > tags 1030456 + patch Bug #1030456 [src:drslib] drslib: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '0.3.1p3' Added tag(s) patch. > tags 1030456 + pending Bug #1030456 [src:drslib] drslib: FTBFS:

Bug#1030456: drslib: diff for NMU version 0.3.1.p3-2.1

Control: tags 1030456 + patch Control: tags 1030456 + pending Dear maintainer, I've prepared an NMU for drslib (versioned as 0.3.1.p3-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru drslib-0.3.1.p3/debian/changelog

Bug#1031952: gettext: Missing source for an installed windows binary

Package: gettext Version: 0.21-11 Severity: serious Tags: ftbfs upstream Justification: DFSG #2 User: lintian-ma...@debian.org Usertags: source-is-missing X-Debbugs-Cc: ftpmas...@debian.org Hi, your package includes some files that seem to lack sources in preferred forms of modification:

Bug#1028743: python-bottle: FTBFS: AssertionError: b'OK' != "URLError(ConnectionRefusedError(111, 'Connection refused'))"

Hello! Just wanted to chime in to confirm that James' patch does make the package compile.

Processed: twms: diff for NMU version 0.07z+git20201202+bb7c3f8-1.2

Processing control commands: > tags 1030449 + patch Bug #1030449 [src:twms] twms: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '0.06y' Added tag(s) patch. > tags 1030449 + pending Bug #1030449 [src:twms] twms: FTBFS:

Bug#1030449: twms: diff for NMU version 0.07z+git20201202+bb7c3f8-1.2

Control: tags 1030449 + patch Control: tags 1030449 + pending Dear maintainer, I've prepared an NMU for twms (versioned as 0.07z+git20201202+bb7c3f8-1.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru

Bug#1013594: insubstantial: FTBFS: Caused by: : java.lang.VerifyError: Expecting a stackmap frame at branch target 33

Control: user debian-rele...@lists.debian.org Control: usertag -1 + bsp-2023-02-ca-montreal Hello, I've worked on this today: I can confirm the FTBFS issue occurs consistently, but I wasn't able to find a solution. Upstream isn't much help here: 7.3 is the latest release and was tagged in 2014

Bug#901245: Handling of -e violates policy for x-terminal-emulator

Ok, so pushing further. -e does seem to work fine with terminator 2.1.2-1. At least, these commands works fine: x-terminal-emulator -e 'if test -x /bin/ss ; then watch -t ss -putsw; else netstat -c; fi' x-terminal-emulator -e 'watch /' Adding "sh -c" fails though:

Bug#1016732: [Pkg-javascript-devel] Bug#1016732: Please help to reproduce (Was: shiny-server: server-function? don't run)

On ഞാ, ഫെബ്രു 26 2023 at 02:33:31 രാവിലെ +05:30:00 +05:30:00, Pirate Praveen wrote: On ഞാ, ഫെബ്രു 26 2023 at 02:24:00 രാവിലെ +05:30:00 +05:30:00, Nilesh Patra wrote: On Sun, Feb 26, 2023 at 12:46:15AM +0530, Pirate Praveen wrote: Thanks for the pointer. However, unfortunately even

Bug#997179: marked as done (tty-clock: FTBFS: ttyclock.c:278:73: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Sat, 25 Feb 2023 21:13:03 + with message-id and subject line Bug#997179: fixed in tty-clock 2.3-2 has caused the Debian Bug report #997179, regarding tty-clock: FTBFS: ttyclock.c:278:73: error: format not a string literal and no format arguments [-Werror=format-security]

Bug#1031935: marked as done (firmware-ath9k-htc: missing hardware identifiers in dep-11 metadata)

Your message dated Sat, 25 Feb 2023 21:10:44 + with message-id and subject line Bug#1031935: fixed in open-ath9k-htc-firmware 1.4.0-108-gd856466+dfsg1-1.3 has caused the Debian Bug report #1031935, regarding firmware-ath9k-htc: missing hardware identifiers in dep-11 metadata to be marked as

Bug#1028625: marked as done (src:x-loader: fails to migrate to testing for too long: FTBFS)

Your message dated Sat, 25 Feb 2023 21:13:18 + with message-id and subject line Bug#1028625: fixed in x-loader 1.5.1+git20110715+fca7cd2-4 has caused the Debian Bug report #1028625, regarding src:x-loader: fails to migrate to testing for too long: FTBFS to be marked as done. This means that

Bug#1026364: marked as done (FTBFS: error: dangling pointer ‘dentptr’ to ‘dent’ may be used)

Your message dated Sat, 25 Feb 2023 21:13:18 + with message-id and subject line Bug#1026364: fixed in x-loader 1.5.1+git20110715+fca7cd2-4 has caused the Debian Bug report #1026364, regarding FTBFS: error: dangling pointer ‘dentptr’ to ‘dent’ may be used to be marked as done. This means that

Bug#1031950: libgeo-distance-perl should add Breaks and Replaces on libgeo-distance-xs-perl

Package: libgeo-distance-perl Version: 0.25-2 Severity: serious Upgrading libgeo-distance-perl from bullseye to bookworm should remove libgeo-distance-xs-perl since it is now useless.

Bug#1016732: Please help to reproduce (Was: shiny-server: server-function? don't run)

On ഞാ, ഫെബ്രു 26 2023 at 02:24:00 രാവിലെ +05:30:00 +05:30:00, Nilesh Patra wrote: On Sun, Feb 26, 2023 at 12:46:15AM +0530, Pirate Praveen wrote: Thanks for the pointer. However, unfortunately even after propagating the "-t" flag with coffee, the generated code does not work to fine (the

Processed: libzypp: diff for NMU version 17.25.7-2.4

Processing control commands: > tags 1028680 + patch Bug #1028680 [src:libzypp] libzypp: FTBFS: RpmHeader.cc:41:16: error: ‘strcmp’ was not declared in this scope Added tag(s) patch. > tags 1028680 + pending Bug #1028680 [src:libzypp] libzypp: FTBFS: RpmHeader.cc:41:16: error: ‘strcmp’ was not

Bug#1028680: libzypp: diff for NMU version 17.25.7-2.4

Control: tags 1028680 + patch Control: tags 1028680 + pending Dear maintainer, I've prepared an NMU for libzypp (versioned as 17.25.7-2.4) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru libzypp-17.25.7/debian/changelog

Bug#1031947: marked as done (eos-sdk: FTBFS everywhere)

Your message dated Sat, 25 Feb 2023 20:54:51 + with message-id and subject line Bug#1031947: fixed in eos-sdk 0~git20230107+ds-2 has caused the Debian Bug report #1031947, regarding eos-sdk: FTBFS everywhere to be marked as done. This means that you claim that the problem has been dealt

Bug#1016732: Please help to reproduce (Was: shiny-server: server-function? don't run)

On Sun, Feb 26, 2023 at 12:46:15AM +0530, Pirate Praveen wrote: > On Sun, 12 Feb 2023 23:16:06 +0530 Nilesh Patra wrote: > > Sorry for pinging you again, but would you be able to take a look at this > please? > > I don't know enough coffeescript to be able to check this and it'd be > > awesome if

Bug#1028398: snapd: both Telegram-desktop and Skype cannot load and save files

Hi there, This could be happening for many reasons. Just to investigate one possiblity: in your syslog do you see messages from apparmor when you try to load a file?

Processed: Re: nodejs: [arm64] RangeError: Maximum call stack size exceeded

Processing control commands: > forwarded -1 https://github.com/nodejs/node/issues/41163 Bug #1030284 [nodejs] nodejs: [arm64] RangeError: Maximum call stack size exceeded Set Bug forwarded-to-address to 'https://github.com/nodejs/node/issues/41163'. -- 1030284:

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

Package: nodejs Followup-For: Bug #1030284 Control: forwarded -1 https://github.com/nodejs/node/issues/41163

Processed: owner 987008

Processing commands for cont...@bugs.debian.org: > owner 987008 anar...@debian.org Bug #987008 [grub2] Grub fails to find LVM volume after previous LV rename Owner recorded as anar...@debian.org. > thanks Stopping processing here. Please contact me if you need assistance. -- 987008:

Bug#987008: working on this bug

owner 987008 anar...@debian.org thanks Hi, I've ported the submitted patch here into the package and plan to upload an NMU shortly. To quote the actual patch file I ended up with: Description: fix renamed LV detection It looks like the detection of the LVM logical volumes fails in certain

Bug#1028725: flycheck: FTBFS: make: *** [debian/rules:4: binary] Error 25

On Monday, February 20 2023, David Bremner wrote: > David Bremner writes: > >> I don't think these are the same as previously encountered >> native-compilation related failures. I get the same / similar failures >> when running >> >> EMACS_INHIBIT_AUTOMATIC_NATIVE_COMPILATION=t emacs -q -batch

Bug#1031880: unattended-upgrades: requires on_ac_power from package powermgmt-base to function at all

Hi Jochen, Thanks very much for looking into this so quickly. On a machine with root's $PATH set to the default value: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Without powermgmt-base installed, I am seeing the following: root# which -a on_ac_power root# (i.e. an executable

Processed: bookworm-ignore

Processing commands for cont...@bugs.debian.org: > # tzdata change got reverted for now > tag 1031442 bookworm-ignore Bug #1031442 {Done: Adrian Bunk } [src:gnustep-base] gnustep-base: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned exit

Processed: Re: Bug#997179: tty-clock: FTBFS: ttyclock.c:278:73: error: format not a string literal and no format arguments [-Werror=format-security]

Processing commands for cont...@bugs.debian.org: > tag 997179 +pending Bug #997179 [src:tty-clock] tty-clock: FTBFS: ttyclock.c:278:73: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) pending. > user debian-rele...@lists.debian.org Setting user

Bug#997179: tty-clock: FTBFS: ttyclock.c:278:73: error: format not a string literal and no format arguments [-Werror=format-security]

tag 997179 +pending user debian-rele...@lists.debian.org usertag 997179 + bsp-2023-02-ca-montreal thanks I've orphaned this package (#1031941) but I figured I could at least fix this bug before I go. -- When the power of love overcomes love of power

Bug#1031947: eos-sdk: FTBFS everywhere

Source: eos-sdk Version: 0~git20230107+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/package.php?p=eos-sdk=sid Cheers -- Sebastian Ramacher

Bug#1000209: Bug #1000209

Hi, I'm working with Gabriel on this as part of a BSP. Problems experienced earlier were caused by us trying to build the package in bullseye. We tried again from bookworm and were able to build the package again. We've been able to install the package using the attached patch that doesn't hack

Processed: tagging 1025884

Processing commands for cont...@bugs.debian.org: > tags 1025884 + fixed Bug #1025884 {Done: Paul Gevers } [src:ddnet] src:ddnet: fails to migrate to testing for too long: FTBFS on s390x Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1025884:

Bug#1019273: package built and lintian passed

I forgot to mention, that I added the COPYING file to and built apt 2.5.6, and not apt 2.5.2 against which the bug was reported. It was against 2.5.6 that lintian was run. -- Znoteer znot...@mailbox.org

Bug#1019273: package built and lintian passed

I built the package with the new copyright file, and ran the resulting .changes file through lintian. There were no errors reported by lintian, so the COPYING file provided appears to have correct systax. -- Znoteer znot...@mailbox.org

Bug#1016732: Please help to reproduce (Was: shiny-server: server-function don't run)

On Sun, 12 Feb 2023 23:16:06 +0530 Nilesh Patra wrote: > Sorry for pinging you again, but would you be able to take a look at this please? > I don't know enough coffeescript to be able to check this and it'd be > awesome if you could consider taking a look. Coffeescript 2 creates ESM format

Bug#901245: Handling of -e violates policy for x-terminal-emulator

user debian-rele...@lists.debian.org usertag 901245 + bsp-2023-02-ca-montreal thank you Thanks for the excellent debugging session :) I've tried to apply the patch [1] but it does not seem to fix the bug itself. I'll try to dig further during the Montreal BSP. Cheers, [1]:

Processed: ltrace: diff for NMU version 0.7.3-6.4

Processing control commands: > tags 1023436 + patch Bug #1023436 [ltrace] unusable on mipsel: unexpected breakpoint at 0x... Added tag(s) patch. > tags 1023436 + pending Bug #1023436 [ltrace] unusable on mipsel: unexpected breakpoint at 0x... Added tag(s) pending. -- 1023436:

Bug#1023436: ltrace: diff for NMU version 0.7.3-6.4

Control: tags 1023436 + patch Control: tags 1023436 + pending Dear maintainer, I've prepared an NMU for ltrace (versioned as 0.7.3-6.4) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru ltrace-0.7.3/debian/changelog

Bug#916596: marked as done (iptables.postinst failure on link creation)

Your message dated Sat, 25 Feb 2023 20:17:15 +0200 with message-id and subject line Re: Bug#916596: iptables.postinst failure on link creation has caused the Debian Bug report #916596, regarding iptables.postinst failure on link creation to be marked as done. This means that you claim that the

Bug#1031942: marked as done (sphinxbase: Please drop the ltrace build dependency on mipsel)

Your message dated Sat, 25 Feb 2023 18:20:19 + with message-id and subject line Bug#1031942: fixed in sphinxbase 0.8+5prealpha+1-16 has caused the Debian Bug report #1031942, regarding sphinxbase: Please drop the ltrace build dependency on mipsel to be marked as done. This means that you

Bug#1031943: ebtables: symlink removal removal code in the postinst does not seem to be working

Package: ebtables Version: 2.0.11-5 Severity: serious ... Setting up ebtables (2.0.11-5) ... update-alternatives: using /usr/sbin/ebtables-legacy to provide /usr/sbin/ebtables (ebtables) in auto mode update-alternatives: error: cannot stat file '/usr/sbin/ebtables': Too many levels of symbolic

Processed: tagging 1031942

Processing commands for cont...@bugs.debian.org: > tags 1031942 + pending Bug #1031942 [src:sphinxbase] sphinxbase: Please drop the ltrace build dependency on mipsel Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031942:

Bug#1000209: Not able to build the package: multiple patches fail to apply

Hi, I've just taken a look at this issue together with someone else during the Montreal BSP and we think that the init script is possibly the source of the problem: the stop action fails if it is called when the service is not running, which is the case when you install the package on a new

Processed: sphinxbase: Please drop the ltrace build dependency on mipsel

Processing control commands: > block 1023436 by -1 Bug #1023436 [ltrace] unusable on mipsel: unexpected breakpoint at 0x... 1023436 was not blocked by any bugs. 1023436 was not blocking any bugs. Added blocking bug(s) of 1023436: 1031942 -- 1023436:

Bug#1031942: sphinxbase: Please drop the ltrace build dependency on mipsel

Source: sphinxbase Version: 0.8+5prealpha+1-15 Severity: serious Control: block 1023436 by -1 I am planning to fix #1023436 by dropping the broken mipsel binary, and sphinxbase is the only user. sphinxbase uses ltrace only for debugging in case of test failure, checking the logfile that is not

Processed: tagging 1031832

Processing commands for cont...@bugs.debian.org: > tags 1031832 + upstream fixed-upstream Bug #1031832 [python3-vispy] python3-vispy: import fails: AttributeError: module 'numpy' has no attribute 'bool' Added tag(s) fixed-upstream and upstream. > thanks Stopping processing here. Please contact

Bug#1031895: marked as done (zoph fails to purge when mariadb-client is not installed)

Your message dated Sat, 25 Feb 2023 17:59:25 + with message-id and subject line Bug#1031895: fixed in zoph 1.0.1-3 has caused the Debian Bug report #1031895, regarding zoph fails to purge when mariadb-client is not installed to be marked as done. This means that you claim that the problem

Bug#1031436: marked as done (ubuntu-dev-tools: FTBFS because of ./run-linters during build)

Your message dated Sat, 25 Feb 2023 17:55:00 + with message-id and subject line Bug#1031436: fixed in ubuntu-dev-tools 0.193 has caused the Debian Bug report #1031436, regarding ubuntu-dev-tools: FTBFS because of ./run-linters during build to be marked as done. This means that you claim that

Bug#963433: marked as done (libcolor-calc-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 2)

Your message dated Sat, 25 Feb 2023 17:52:14 + with message-id and subject line Bug#961147: fixed in libcolor-calc-perl 1.074-3 has caused the Debian Bug report #961147, regarding libcolor-calc-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 2 to be marked as

Bug#961147: marked as done (libcolor-calc-perl: broken by new libgraphics-colornames-perl)

Your message dated Sat, 25 Feb 2023 17:52:14 + with message-id and subject line Bug#961147: fixed in libcolor-calc-perl 1.074-3 has caused the Debian Bug report #961147, regarding libcolor-calc-perl: broken by new libgraphics-colornames-perl to be marked as done. This means that you claim

Bug#1031744: marked as done (httpdirfs: usage of ubsan might introduce vulnerabilities)

Your message dated Sat, 25 Feb 2023 17:51:09 + with message-id and subject line Bug#1031744: fixed in httpdirfs-fuse 1.2.5-1 has caused the Debian Bug report #1031744, regarding httpdirfs: usage of ubsan might introduce vulnerabilities to be marked as done. This means that you claim that the

Bug#1019273: actual patch for debian/copyright file

user debian-rele...@lists.debian.org usertags -1 + bsp-2023-02-ca-montreal Thank you The original file offered was not a patch. Here is a patch. You can now see the EXPAT and BSD licences in the patch. -- Znoteer znot...@mailbox.org diff --git a/COPYING b/COPYING index 2f9ab10e8..d518ef5d4

Bug#1031442: marked as done (gnustep-base: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned exit code 2)

Your message dated Sat, 25 Feb 2023 19:01:09 +0200 with message-id and subject line Re: Bug#1031442: gnustep-base: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned exit code 2 has caused the Debian Bug report #1031442, regarding

Bug#1031438: marked as done (qca2: FTBFS: dh_auto_test: error: cd build && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)

Your message dated Sat, 25 Feb 2023 16:34:07 + with message-id and subject line Bug#1031438: fixed in qca2 2.3.5-2 has caused the Debian Bug report #1031438, regarding qca2: FTBFS: dh_auto_test: error: cd build && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 to be marked as

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

True. I'm not a C programmer, so I may be unduly concerned about the maintenance load. I'll defer to your judgement. I do wonder if we should make a stab at switching the rust bits to using Debian packages instead of the embedded copies. If we could manage it, then any security issues in

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

On 25 February 2023 14:57:28 UTC, Scott Kitterman wrote: >Generally favorably, but I'd rather wait for upstream to agree on it, >otherwise it may be a patch we have to maintain forever. Now we maintain the tfm bits. >What's their reaction to the change? No reply so far. The first few patches

Bug#1031649: wine: /usr/bin/wine64 still required

On 20.02.23 01:17, Austin English wrote: On Sun, Feb 19, 2023, 17:33 Jens Reyer > wrote: Yes, it's arguably a bug in winetricks. Film what I gather upstream, it's also not yet fully supported. I would advise reverting for now. At least until upstream fully

Bug#1031895: zoph fails to purge when mariadb-client is not installed

I have made this change, although on my system piuparts (1.1.7) does not give me this result - I still get a piuparts failure due to 9m55.8s ERROR: FAIL: Package purging left files on system: /etc/dbconfig-common/ owned by: dbconfig-common /etc/mysql/owned by: mariadb-server,

Bug#1031931: youtube-dl: All binaries missing in youtube-dl 2021.12.17-2

Control: severity -1 important Am Sat, Feb 25, 2023 at 03:39:19PM +0100 schrieb Michael Stoeger: > Package: youtube-dl > Version: 2021.12.17-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > it looks like the whole binary part is missing in the current

Processed: Re: Bug#1031931: youtube-dl: All binaries missing in youtube-dl 2021.12.17-2

Processing control commands: > severity -1 important Bug #1031931 [youtube-dl] youtube-dl: All binaries missing in youtube-dl 2021.12.17-2 Severity set to 'important' from 'grave' -- 1031931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031931 Debian Bug Tracking System Contact

Processed: flashrom: diff for NMU version 1.3.0-2.1

Processing control commands: > tags 1031448 + patch Bug #1031448 [libflashrom-dev] libfrashrom-dev missing dependency on pkg-config required libraries Added tag(s) patch. > tags 1031448 + pending Bug #1031448 [libflashrom-dev] libfrashrom-dev missing dependency on pkg-config required libraries

Bug#1031448: flashrom: diff for NMU version 1.3.0-2.1

Control: tags 1031448 + patch Control: tags 1031448 + pending Dear maintainer, I've prepared an NMU for flashrom (versioned as 1.3.0-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru flashrom-1.3.0/debian/changelog

Bug#1031935: firmware-ath9k-htc: missing hardware identifiers in dep-11 metadata

Package: firmware-ath9k-htc Version: 1.4.0-108-gd856466+dfsg1-1.2 Severity: serious Justification: regression in hardware support X-Debbugs-Cc: b...@debian.org, debian-ker...@lists.debian.org, debian-b...@lists.debian.org Hi, Here's another thing that was totally overlooked while forcing the

Bug#1031706: marked as done (optuna: test_create_new_trial randomly fails on s390x)

Your message dated Sat, 25 Feb 2023 15:49:16 + with message-id and subject line Bug#1031706: fixed in optuna 3.1.0-4 has caused the Debian Bug report #1031706, regarding optuna: test_create_new_trial randomly fails on s390x to be marked as done. This means that you claim that the problem has

Bug#1031231: tries to overwrite /etc/cron.yearly/.placeholder from systemd-cron

Hi, I was not explicit enough. It's the "cron-daemon-common" binary package that needs this Conflicts: / Breaks, not the "cron" binary package Le mar. 14 févr. 2023 à 22:41, Alexandre Detiste a écrit : > > To be explicit: on your side you'd need yet another upload with a > >Conflicts:

Processed: reopening 1031231

Processing commands for cont...@bugs.debian.org: > reopen 1031231 Bug #1031231 {Done: Georges Khaznadar } [cron-daemon-common] tries to overwrite /etc/cron.yearly/.placeholder from systemd-cron 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be

Bug#1026501: marked as done (request-tracker4: FTBFS: make[1]: *** [Makefile:381: test-parallel] Error 1)

Your message dated Sat, 25 Feb 2023 15:20:59 + with message-id and subject line Bug#1026501: fixed in request-tracker4 4.4.6+dfsg-1.1 has caused the Debian Bug report #1026501, regarding request-tracker4: FTBFS: make[1]: *** [Makefile:381: test-parallel] Error 1 to be marked as done. This

Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

Hi, Andrew, please use reply-all, to reply to the bug and to the bug submitter. A list-only reply doesn't quite help… Andrew M.A. Cater (2023-02-25): > > I have installed Debian testing (bookworm) from one of the latest ISO images > >

Processed: pacparser: diff for NMU version 1.3.6-1.4

Processing control commands: > tags 1026106 + patch Bug #1026106 [src:pacparser] pacparser: CVE-2019-25078: memory overwrite issue for pacparser_find_proxy function Added tag(s) patch. > tags 1026106 + pending Bug #1026106 [src:pacparser] pacparser: CVE-2019-25078: memory overwrite issue for

Processed: qca2: diff for NMU version 2.3.5-1.1

Processing control commands: > tags 1031438 + patch Bug #1031438 [src:qca2] qca2: FTBFS: dh_auto_test: error: cd build && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 Added tag(s) patch. > tags 1031438 + pending Bug #1031438 [src:qca2] qca2: FTBFS: dh_auto_test: error: cd build

Bug#1031438: qca2: diff for NMU version 2.3.5-1.1

Control: tags 1031438 + patch Control: tags 1031438 + pending Dear maintainer, I've prepared an NMU for qca2 (versioned as 2.3.5-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru qca2-2.3.5/debian/changelog qca2-2.3.5/debian/changelog ---

Bug#1026106: pacparser: diff for NMU version 1.3.6-1.4

Control: tags 1026106 + patch Control: tags 1026106 + pending Dear maintainer, I've prepared an NMU for pacparser (versioned as 1.3.6-1.4) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru pacparser-1.3.6/debian/changelog

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

Generally favorably, but I'd rather wait for upstream to agree on it, otherwise it may be a patch we have to maintain forever. What's their reaction to the change? It's also late in the release cycle to do it (not definitely a problem, but calls for caution). Scott K On February 25, 2023

Bug#1031931: youtube-dl: All binaries missing in youtube-dl 2021.12.17-2

Package: youtube-dl Version: 2021.12.17-2 Severity: grave Justification: renders package unusable Dear Maintainer, it looks like the whole binary part is missing in the current version of youtube-dl in Debian testing and unstable. Of course, the program is not usable with /usr/bin/youtube-dl

Bug#1031801: marked as done (libduktape.so.207: undefined symbol: log2)

Your message dated Sat, 25 Feb 2023 14:35:29 + with message-id and subject line Bug#1031801: fixed in duktape 2.7.0-2 has caused the Debian Bug report #1031801, regarding libduktape.so.207: undefined symbol: log2 to be marked as done. This means that you claim that the problem has been dealt

  1   2   >