Bug#1073366: marked as done (ansible-runner: FTBFS: ModuleNotFoundError: No module named 'six')

2024-06-20 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jun 2024 06:49:32 + with message-id and subject line Bug#1073366: fixed in ansible-runner 2.4.0-0.1 has caused the Debian Bug report #1073366, regarding ansible-runner: FTBFS: ModuleNotFoundError: No module named 'six' to be marked as done. This means that you claim

Bug#1073428: marked as done (sogo: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 22:22:00 + with message-id and subject line Bug#1073428: fixed in sogo 5.10.0-3 has caused the Debian Bug report #1073428, regarding sogo: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to be marked

Bug#1072591: marked as done (silx: debci fails tests (testClickOnBackToParentTool))

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 23:19:57 +0200 (CEST) with message-id <1001614626.61759754.1718918397631.javamail.zim...@synchrotron-soleil.fr> and subject line silx: debci fails tests (testClickOnBackToParentTool) has caused the Debian Bug report #1072591, regarding silx: debci fails tests (t

Bug#1073318: marked as done (gupnp-av: FTBFS: ../libgupnp-av/gupnp-didl-lite-parser.c:233:9: error: ‘xmlRecoverMemory’ is deprecated [-Werror=deprecated-declarations])

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 21:21:28 + with message-id and subject line Bug#1073318: fixed in gupnp-av 0.14.1-3 has caused the Debian Bug report #1073318, regarding gupnp-av: FTBFS: ../libgupnp-av/gupnp-didl-lite-parser.c:233:9: error: ‘xmlRecoverMemory’ is deprecated [-Werror=depreca

Processed: Bug#1073318 marked as pending in gupnp-av

2024-06-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1073318 [src:gupnp-av] gupnp-av: FTBFS: ../libgupnp-av/gupnp-didl-lite-parser.c:233:9: error: ‘xmlRecoverMemory’ is deprecated [-Werror=deprecated-declarations] Added tag(s) pending. -- 1073318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Bug#1073318: marked as pending in gupnp-av

2024-06-20 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #1073318 in gupnp-av reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gupnp-av/-/commit/0107fbdaa98a9ff083f6a635ac5

Processed: Re: Bug#1069402: gcr: FTBFS on arm64: test segfaults

2024-06-20 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 gcr: FTBFS: failing tests Bug #1069402 [src:gcr] gcr: FTBFS on arm64: test segfaults Changed Bug title to 'gcr: FTBFS: failing tests' from 'gcr: FTBFS on arm64: test segfaults'. > severity -1 important Bug #1069402 [src:gcr] gcr: FTBFS: failing tests Seve

Bug#1069402: gcr: FTBFS on arm64: test segfaults

2024-06-20 Thread Jeremy Bícha
Control: retitle -1 gcr: FTBFS: failing tests Control: severity -1 important Control: forwarded -1 https://gitlab.gnome.org/GNOME/gcr/-/issues/119 On Sat, Apr 20, 2024 at 8:23 AM Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on arm64. > … > > 16/4

Processed: Bug#1033210 marked as pending in cairomm

2024-06-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1033210 [src:cairomm] cairomm FTBFS with nocheck profile: missing boost test Added tag(s) pending. -- 1033210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1033210: marked as pending in cairomm

2024-06-20 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #1033210 in cairomm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/cairomm/-/commit/6211d268c94830241f2bdffd412c9

Bug#1071058: mumble-server: prompting due to modified conffiles which were not modified by the user: /etc/mumble/mumble-server.ini

2024-06-20 Thread Chris Knadle
Hopefully this bug will be fixed with the addition of the following file == debian/mumble-server.maintscript: mv_conffile /etc/mumble-server.ini /etc/mumble/mumble-server.ini 1.5.517-1~ == Thanks On 5/13/24 12:19, Andreas Beckmann wrote: https://wiki.

Bug#1072650: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64

2024-06-20 Thread Paul Gevers
Hi Dirk, On 20-06-2024 2:17 p.m., Dirk Eddelbuettel wrote: It is a (very) big package, but it has not grown much lately. Not being able to build may lead to auto-removal which is bad, excluding an architecture is also not good. Not clear what the least bad move is here... You might be aware,

Processed: [bts-link] source package firefox

2024-06-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package firefox > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting

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

2024-06-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:booth > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setti

Bug#1072798: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2024-0090, CVE-2024-0092)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 18:47:44 + with message-id and subject line Bug#1072798: fixed in nvidia-graphics-drivers-tesla-470 470.256.02-1~deb11u1 has caused the Debian Bug report #1072798, regarding nvidia-graphics-drivers-tesla-470: CVE-2024-0090, CVE-2024-0092 to be marked as don

Bug#1072792: marked as done (nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 18:47:44 + with message-id and subject line Bug#1072792: fixed in nvidia-graphics-drivers-tesla-470 470.256.02-1~deb11u1 has caused the Debian Bug report #1072792, regarding nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092 to be marked a

Bug#1064061: marked as done (wpa: CVE-2023-52160)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 18:47:45 + with message-id and subject line Bug#1064061: fixed in wpa 2:2.9.0-21+deb11u1 has caused the Debian Bug report #1064061, regarding wpa: CVE-2023-52160 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Processed: closing 1073937

2024-06-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1073937 3.23.0+dfsg-0.2 Bug #1073937 [src:opencryptoki] opencryptoki: Do not build on several architectures due to libitm1 build-dependency Marked as fixed in versions opencryptoki/3.23.0+dfsg-0.2. Bug #1073937 [src:opencryptoki] opencrypto

Bug#1072800: marked as done (nvidia-open-gpu-kernel-modules: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 18:32:32 + with message-id and subject line Bug#1072800: fixed in nvidia-open-gpu-kernel-modules 535.183.01-1~deb12u1 has caused the Debian Bug report #1072800, regarding nvidia-open-gpu-kernel-modules: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092 to be mar

Bug#1072798: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2024-0090, CVE-2024-0092)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 18:32:32 + with message-id and subject line Bug#1072798: fixed in nvidia-graphics-drivers-tesla-470 470.256.02-1~deb12u1 has caused the Debian Bug report #1072798, regarding nvidia-graphics-drivers-tesla-470: CVE-2024-0090, CVE-2024-0092 to be marked as don

Bug#1072792: marked as done (nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 18:32:32 + with message-id and subject line Bug#1072792: fixed in nvidia-graphics-drivers-tesla-470 470.256.02-1~deb12u1 has caused the Debian Bug report #1072792, regarding nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092 to be marked a

Bug#1072792: marked as done (nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 18:32:29 + with message-id and subject line Bug#1072792: fixed in nvidia-graphics-drivers 535.183.01-1~deb12u1 has caused the Debian Bug report #1072792, regarding nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092 to be marked as done. T

Bug#1064061: marked as done (wpa: CVE-2023-52160)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 18:32:51 + with message-id and subject line Bug#1064061: fixed in wpa 2:2.10-12+deb12u1 has caused the Debian Bug report #1064061, regarding wpa: CVE-2023-52160 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1040223: marked as done (libimage-imlib2-perl: Creates empty package on bookworm upwards (maybe because of libimlib2-dev?))

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 18:32:25 + with message-id and subject line Bug#1040223: fixed in libimage-imlib2-perl 2.03-1.2~deb12u1 has caused the Debian Bug report #1040223, regarding libimage-imlib2-perl: Creates empty package on bookworm upwards (maybe because of libimlib2-dev?) to

Bug#1070201: marked as done (scikit-learn: autopkgtest regression on i386 with NumPy 1.26)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 18:24:06 + with message-id and subject line Bug#1070201: fixed in scikit-learn 1.4.2+dfsg-2 has caused the Debian Bug report #1070201, regarding scikit-learn: autopkgtest regression on i386 with NumPy 1.26 to be marked as done. This means that you claim tha

Processed: Re: [Debian-med-packaging] Bug#1071448: marked as done (dipy: FTBFS on 32 bit archs with ArrayMemoryError)

2024-06-20 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1071448 {Done: "Michael R. Crusoe" } [src:dipy] dipy: FTBFS on 32 bit archs with ArrayMemoryError 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopene

Bug#1071448: [Debian-med-packaging] Bug#1071448: marked as done (dipy: FTBFS on 32 bit archs with ArrayMemoryError)

2024-06-20 Thread Graham Inggs
Control: reopen -1 On Wed, 19 Jun 2024 at 09:00, Debian Bug Tracking System wrote: > This was fixed in the latest release autopkgtest now succeeds again on i386 [1], but still failing on armhf [2], where it passed previously on 2024-04-13. [1] https://ci.debian.net/packages/d/dipy/testing/i386

Bug#1069426: nocache: FTBFS on armhf: ccsSPzHW.s:3650: Error: symbol `fopen64' is already defined

2024-06-20 Thread Christoph Biedl
Guillem Jover wrote... > I've provided a PR upstream to fix this at: > > https://github.com/Feh/nocache/pull/55 Thanks a lot for that. @Maintainer: As that change is rather huge and relies on other changes upstream, I'd rather forward to upstream release 1.2[1] and Guillem's work on top of it

Processed: Re: Bug#1038168: glom: unmaintained upstream

2024-06-20 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1038168 [src:glom] glom: unmaintained upstream Severity set to 'serious' from 'important' -- 1038168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1072807: rust-instant: crate is abandoned - recommended replacement is web_time

2024-06-20 Thread Jonas Smedegaard
Quoting Matthias Geiger (2024-06-20 18:24:04) > On 20.06.24 17:29, Jonas Smedegaard wrote: > > Quoting Matthias Geiger (2024-06-20 17:14:08) > >> On Sat, 08 Jun 2024 08:12:48 +0200 Jonas Smedegaard wrote: > >>> Source: rust-instant > Version: 0.1.12-3 > Severity: serious > Tags: > >>> upstream >

Bug#1073942: jami: Fails to build with webrtc-audio-processing

2024-06-20 Thread Jeremy Bícha
Package: jami Version: 20231201.0~ds1-1 Severity: serious X-Debbugs-CC: band...@gnu.org jami fails to build with webrtc-audio-processing 1.3 https://launchpad.net/ubuntu/+source/jami/20231201.0~ds2-1build3 Thank you, Jeremy Bícha

Bug#1072807: rust-instant: crate is abandoned - recommended replacement is web_time

2024-06-20 Thread Matthias Geiger
On 20.06.24 17:29, Jonas Smedegaard wrote: Quoting Matthias Geiger (2024-06-20 17:14:08) On Sat, 08 Jun 2024 08:12:48 +0200 Jonas Smedegaard wrote: Source: rust-instant > Version: 0.1.12-3 > Severity: serious > Tags: upstream > The crate is buggy and unmaintained, according to this: https://g

Bug#1072807: rust-instant: crate is abandoned - recommended replacement is web_time

2024-06-20 Thread Blair Noctis
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Sat, 08 Jun 2024 08:12:48 +0200 Jonas Smedegaard wrote: > Source: rust-instant > Version: 0.1.12-3 > Severity: serious > Tags: upstream > > The crate is buggy and unmaintained, according to this: > https://github.com/sebcrozet/instant/issues/52 >

Bug#1072807: rust-instant: crate is abandoned - recommended replacement is web_time

2024-06-20 Thread Jonas Smedegaard
Quoting Matthias Geiger (2024-06-20 17:14:08) > On Sat, 08 Jun 2024 08:12:48 +0200 Jonas Smedegaard wrote: > > Source: rust-instant > Version: 0.1.12-3 > Severity: serious > Tags: > > upstream > > > The crate is buggy and unmaintained, according to this: > > https://github.com/sebcrozet/instant/

Bug#1058130: marked as done (python-nmea2: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 15:24:30 + with message-id and subject line Bug#1058130: fixed in python-nmea2 1.19.0-3 has caused the Debian Bug report #1058130, regarding python-nmea2: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you claim that

Bug#1072807: rust-instant: crate is abandoned - recommended replacement is web_time

2024-06-20 Thread Matthias Geiger
On Sat, 08 Jun 2024 08:12:48 +0200 Jonas Smedegaard wrote: Source: rust-instant > Version: 0.1.12-3 > Severity: serious > Tags: upstream > The crate is buggy and unmaintained, according to this: https://github.com/sebcrozet/instant/issues/52 The recommended (seemingly drop-in) replacement is w

Bug#1071046: marked as done (rust-mimalloc: FTBFS on armhf (E: Build killed with signal TERM after 150 minutes of inactivity))

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 10:55:54 -0400 with message-id and subject line Re: Bug#1071046: rust-mimalloc: FTBFS on armhf (E: Build killed with signal TERM after 150 minutes of inactivity) has caused the Debian Bug report #1071046, regarding rust-mimalloc: FTBFS on armhf (E: Build kille

Bug#896834: /usr/bin/apt-key: also unstable with gpgv 2.2.43-{6,7} ...

2024-06-20 Thread Julian Andres Klode
On Thu, Jun 20, 2024 at 12:39:39PM GMT, Julian Andres Klode wrote: > Control: reassign -1 gpgv-from-sq > Control: affects -1 apt > Control: severity -1 serious > > On Wed, Jun 19, 2024 at 09:59:52AM GMT, Pti Zoom wrote: > > Package: apt > > Version: 2.9.5 > > Followup-For: Bug #896834 > > > > Dea

Processed: Re: Bug#1058130: closed by Debian FTP Masters (reply to Ulises Vitulli ) (Bug#1058130: fixed in python-nmea2 1.19.0-1)

2024-06-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1058130 +confirmed +pending Bug #1058130 [src:python-nmea2] python-nmea2: FTBFS: ModuleNotFoundError: No module named 'imp' Added tag(s) confirmed. Bug #1058130 [src:python-nmea2] python-nmea2: FTBFS: ModuleNotFoundError: No module named 'i

Processed: bug 1073443 is forwarded to https://github.com/pytest-dev/pytest-rerunfailures/issues/267

2024-06-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1073443 > https://github.com/pytest-dev/pytest-rerunfailures/issues/267 Bug #1073443 [src:pytest-rerunfailures] pytest-rerunfailures: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned

Bug#1066572: marked as done (libpam-pwdfile: FTBFS: bigcrypt.c:62:25: error: implicit declaration of function ‘crypt’; did you mean ‘bigcrypt’? [-Werror=implicit-function-declaration])

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 13:49:47 + with message-id and subject line Bug#1066572: fixed in libpam-pwdfile 2.0-1 has caused the Debian Bug report #1066572, regarding libpam-pwdfile: FTBFS: bigcrypt.c:62:25: error: implicit declaration of function ‘crypt’; did you mean ‘bigcrypt’? [

Bug#1061526: marked as done (astroidmail: Stop using webkit2gtk 4.0)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 13:34:07 + with message-id and subject line Bug#1061526: fixed in astroidmail 0.16-2.1 has caused the Debian Bug report #1061526, regarding astroidmail: Stop using webkit2gtk 4.0 to be marked as done. This means that you claim that the problem has been deal

Bug#1073937: opencryptoki: Do not build on several architectures due to libitm1 build-dependency

2024-06-20 Thread Laurent Bigonville
Source: opencryptoki Version: 3.23.0+dfsg-0.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, It seems that opencryptoki BD again against libitm1 but that package is not available on all architectures. I did fix that in bug #989

Processed: Re: sight: FTBFS with VTK 9.3.0

2024-06-20 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1073822 [src:sight] sight: FTBFS with VTK 9.3.0 Added tag(s) patch. -- 1073822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1073822: sight: FTBFS with VTK 9.3.0

2024-06-20 Thread Gianfranco Costamagna
control: tags -1 patch cat debian/patches/new-libxml2.12.patch Description: Fix build failure with libxml >= 2.12 Author: Gianfranco Costamagna Origin: Inspired from https://github.com/0ad/0ad/commit/d242631245edb66816ef9960bdb2c61b68e56cec.patch Bug-Debian: https://bugs.debian.org/1073822 Last

Processed: your mail

2024-06-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1073077 serious Bug #1073077 [src:krita] krita: Fails to build with jpeg-xl 0.9 Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 1073077: https://bugs.de

Bug#1073315: marked as done (flickcurl: FTBFS: args.c:43:5: error: implicit declaration of function ‘free’ [-Werror=implicit-function-declaration])

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 12:19:28 + with message-id and subject line Bug#1073315: fixed in flickcurl 1.26-8 has caused the Debian Bug report #1073315, regarding flickcurl: FTBFS: args.c:43:5: error: implicit declaration of function ‘free’ [-Werror=implicit-function-declaration] to

Bug#1072650: src:quantlib-swig: fails to migrate to testing for too long: FTBFS on armel, armhf, i386 and riscv64

2024-06-20 Thread Dirk Eddelbuettel
On 20 June 2024 at 12:16, Bo YU wrote: | hi, | | On Mon, Jun 17, 2024 at 7:16 AM Bo YU wrote: | > | > Hi, | > | > On Mon, Jun 17, 2024 at 6:41 AM Dirk Eddelbuettel wrote: | > > | > > | > > Hi Paul, | > > | > > Thanks for the prompt and detailed reply. | > > | > > On 16 June 2024 at 16:13, Paul

Bug#1073931: composer: security update broke feature branches

2024-06-20 Thread Heiko Przybyl
Package: composer Version: 2.0.9-2+deb11u3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: h...@users.noreply.github.com, t...@security.debian.org Dear Maintainer, yesterday unattended-upgrades installed version 2.0.9-2+deb11u3 composer including security fixes for bugs #107

Bug#1069838: khard: Builds fine here.

2024-06-20 Thread Colin Watson
On Thu, Jun 20, 2024 at 12:42:17PM +0200, Santiago Vila wrote: > El 20/6/24 a las 10:13, Colin Watson escribió: > > Santiago, is khard still failing to build for you? > > As of today (version 0.19.1-2 in unstable), yes, all the time. In that case I could use some help reproducing it, because http

Bug#1070063: Remmina fails to connect with Windows systems: Protocol Security Negotiation Failure (older release works)

2024-06-20 Thread Kentaro HAYASHI
Hi, On Mon, 29 Apr 2024 15:41:02 +0200 Daniel Leidert wrote: > Package: remmina > Version: 1.4.35+dfsg-1+b1 > Severity: serious > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi, > > when I try to connect to a windows (11) system, I get errors saying > something like "check security

Bug#1069838: khard: Builds fine here.

2024-06-20 Thread Santiago Vila
El 20/6/24 a las 10:13, Colin Watson escribió: On Sun, Jun 16, 2024 at 09:42:10PM +, Martin Dosch wrote: I just built khard locally and it builds fine. I also can't reproduce this, and I wouldn't normally expect circular import issues to be semi-reproducible - in a given codebase they usua

Bug#1073431: marked as pending in octave-symbolic

2024-06-20 Thread Rafael Laboissière
Control: tag -1 pending Hello, Bug #1073431 in octave-symbolic reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-octave-team/octave-symbolic/-/commit/cb1a16ff

Processed: Bug#1073431 marked as pending in octave-symbolic

2024-06-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1073431 [src:octave-symbolic] octave-symbolic: Failing unit tests in vpa.m and @sym/bernoulli.m Added tag(s) pending. -- 1073431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073431 Debian Bug Tracking System Contact ow...@bugs.debian.org

Processed: Re: Bug#896834: /usr/bin/apt-key: also unstable with gpgv 2.2.43-{6,7} ...

2024-06-20 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 gpgv-from-sq Bug #896834 [apt] /usr/bin/apt-key: apt-key fails in an lxc environment after upgrade to stretch Bug reassigned from package 'apt' to 'gpgv-from-sq'. No longer marked as found in versions apt/1.4.8 and apt/2.9.5. Ignoring request to alter fi

Processed: Re: Bug#1073431: octave-symbolic: FTBFS: ValueError: octoutput does not know how to export type

2024-06-20 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 octave-symbolic: Failing unit tests in vpa.m and @sym/bernoulli.m Bug #1073431 [src:octave-symbolic] octave-symbolic: FTBFS: ValueError: octoutput does not know how to export type Changed Bug title to 'octave-symbolic: Failing unit tests in vpa.m and @s

Bug#1073431: octave-symbolic: FTBFS: ValueError: octoutput does not know how to export type

2024-06-20 Thread Rafael Laboissière
Control: retitle -1 octave-symbolic: Failing unit tests in vpa.m and @sym/bernoulli.m Control: tags -1 + confirmed upstream Hi Lucas, Thank you for the bug report. The relevant parts of the build log are these ones: [inst/vpa.m] /<>/inst/vpa.m […] * test % non-equality

Bug#1072828: marked as done (texlive-binaries upgrade breaks therion build)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 10:07:27 + with message-id and subject line Bug#1072828: fixed in texlive-base 2024.20240401-3 has caused the Debian Bug report #1072828, regarding texlive-binaries upgrade breaks therion build to be marked as done. This means that you claim that the proble

Bug#1072828: Work-around is ineffective on !amd64

2024-06-20 Thread Preuße
Control: reassign -1 texlive-base Control: found -1 2024.20240401-2 Control: tags -1 + pending patch On 19.06.2024 13:19, Adrien Nader wrote: Hello, I found https://tug.org/svn/texlive?revision=71214&view=revision this morning. It only touches the win32 implementations however. I did somethin

Processed: Re: Bug#1072828: Work-around is ineffective on !amd64

2024-06-20 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 texlive-base Bug #1072828 [texlive-binaries] texlive-binaries upgrade breaks therion build Bug reassigned from package 'texlive-binaries' to 'texlive-base'. No longer marked as found in versions texlive-bin/2024.20240313.70630+ds-2. Ignoring request to al

Bug#1070112: marked as done (ipykernel: nose-style setup/teardown is no longer supported in pytest 8)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 09:19:47 + with message-id and subject line Bug#1070112: fixed in ipykernel 6.29.4-1 has caused the Debian Bug report #1070112, regarding ipykernel: nose-style setup/teardown is no longer supported in pytest 8 to be marked as done. This means that you clai

Processed: systemd-{container,cryptsetup,repart}: ineffective Replaces due to /usr-move (DEP17)

2024-06-20 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + systemd Bug #1073922 [systemd-container,systemd-cryptsetup,cryptsetup-repart] systemd-{container,cryptsetup,repart}: ineffective Replaces due to /usr-move (DEP17) Warning: Unknown package 'cryptsetup-repart' Added indication that 1073922 affects system

Bug#1073922: systemd-{container,cryptsetup,repart}: ineffective Replaces due to /usr-move (DEP17)

2024-06-20 Thread Helmut Grohne
Package: systemd-container,systemd-cryptsetup,cryptsetup-repart Version: 256.1-1 Severity: serious Control: affects -1 + systemd User: helm...@debian.org Usertags: dep17p1 Hi, Version 256.1-1 was restructured splitting a number of pieces from the main systemd package into other packages. As far a

Processed: Bug#1070112 marked as pending in ipykernel

2024-06-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1070112 [src:ipykernel] ipykernel: nose-style setup/teardown is no longer supported in pytest 8 Added tag(s) pending. -- 1070112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070112 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1071955: marked as done (shishi: FTBFS against libgcrypt 1.11)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 08:56:42 + with message-id and subject line Bug#1071955: fixed in shishi 1.0.3-5 has caused the Debian Bug report #1071955, regarding shishi: FTBFS against libgcrypt 1.11 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1070112: marked as pending in ipykernel

2024-06-20 Thread Colin Watson
Control: tag -1 pending Hello, Bug #1070112 in ipykernel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/ipykernel/-/commit/09a2d18d16928cd

Bug#1073320: marked as done (eurephia: FTBFS: eurephia_nullsafe.h:47:43: error: implicit declaration of function ‘atoi’ [-Werror=implicit-function-declaration])

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 08:52:45 + with message-id and subject line Bug#1073320: fixed in eurephia 1.1.1-3 has caused the Debian Bug report #1073320, regarding eurephia: FTBFS: eurephia_nullsafe.h:47:43: error: implicit declaration of function ‘atoi’ [-Werror=implicit-function-dec

Bug#1050805: dhcpcd-base: DoS: zero-length packet cause eventual lease expiration

2024-06-20 Thread Martin-Éric Racine
to 20. kesäk. 2024 klo 11.32 Nicolas Cavallari (nicolas.cavall...@green-communications.fr) kirjoitti: > > On 18/06/2024 16:39, Martin-Éric Racine wrote: > > ti 18. kesäk. 2024 klo 15.52 Nicolas Cavallari > > (nicolas.cavall...@green-communications.fr) kirjoitti: > >> > >> On 18/06/2024 13:14, Marti

Bug#1069838: khard: Builds fine here.

2024-06-20 Thread Colin Watson
On Sun, Jun 16, 2024 at 09:42:10PM +, Martin Dosch wrote: > I just built khard locally and it builds fine. I also can't reproduce this, and I wouldn't normally expect circular import issues to be semi-reproducible - in a given codebase they usually either fail or they don't. Santiago, is khar

Bug#1050805: dhcpcd-base: DoS: zero-length packet cause eventual lease expiration

2024-06-20 Thread Nicolas Cavallari
On 18/06/2024 16:39, Martin-Éric Racine wrote: ti 18. kesäk. 2024 klo 15.52 Nicolas Cavallari (nicolas.cavall...@green-communications.fr) kirjoitti: On 18/06/2024 13:14, Martin-Éric Racine wrote: su 16. kesäk. 2024 klo 9.05 Martin-Éric Racine (martin-eric.rac...@iki.fi) kirjoitti: la 15. kes

Bug#1073857: marked as done (keyboard-configuration: fails to install with xkb-data dependency conflict)

2024-06-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jun 2024 07:49:47 + with message-id and subject line Bug#1073857: fixed in console-setup 1.228 has caused the Debian Bug report #1073857, regarding keyboard-configuration: fails to install with xkb-data dependency conflict to be marked as done. This means that you

Bug#1073793: camitk FTBFS with VTK 9.3

2024-06-20 Thread Gianfranco Costamagna
Hello, I'm attaching a "patch" that at least makes it build properly. I will upload to Ubuntu, hopefully upstream will solve it in the future cat debian/patches/vtk-9.3.patch Description: Followup with deprecated vtkConfigure.h header, renaming of SetQuadQualityMeasureToMaxEdgeRatios into SetQu