Bug#1057548: marked as done (cloud-init: FTBFS: failing tests)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Wed, 13 Mar 2024 02:49:13 + with message-id and subject line Bug#1057548: fixed in cloud-init 24.1.1-1 has caused the Debian Bug report #1057548, regarding cloud-init: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been dealt

Bug#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

2024-03-12 Thread Vincent Lefevre
And on a 3rd machine, where I used aptitude --log-file=/tmp/aptitude.log --log-level=info dpkg: dependency problems prevent removal of libb2-1:amd64: libqt6core6t64:amd64 depends on libb2-1 (>= 0.98.1). dpkg: error

Processed: tagging 1066067, tagging 1064762, found 1064762 in 9.1.0+really9.1.0+dfsg2-7, tagging 1066138 ...

2024-03-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1066067 + sid trixie Bug #1066067 [src:cl-plus-ssl] cl-plus-ssl: hardcoded libssl3 dependency Added tag(s) sid and trixie. > tags 1064762 = Bug #1064762 [vtk9] Parsing of vtk files fails for files that worked previously (e.g. in bookworm)

Bug#1066108: marked as done (intel-microcode: CVE-2023-43490 CVE-2023-39368 CVE-2023-38575 CVE-2023-22655 CVE-2023-28746)

2024-03-12 Thread Debian Bug Tracking System
sion: 3.20240312.1 Distribution: unstable Urgency: medium Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique de Moraes Holschuh Closes: 1066108 Changes: intel-microcode (3.20240312.1) unstable; urgency=medium . * New upstream microcode datafile 20240312 (closes: #1066108) - Mitigat

Bug#1065214: marked as done (iproute2: recent libc6-dev change causes the RPC support to be dropped)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 23:39:06 + with message-id and subject line Bug#1065214: fixed in iproute2 6.8.0-1 has caused the Debian Bug report #1065214, regarding iproute2: recent libc6-dev change causes the RPC support to be dropped to be marked as done. This means that you claim

Processed: tagging 1066108

2024-03-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1066108 + pending Bug #1066108 [src:intel-microcode] intel-microcode: CVE-2023-43490 CVE-2023-39368 CVE-2023-38575 CVE-2023-22655 CVE-2023-28746 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Processed: Re: Bug#1066137: gnupg2: -Werror=implicit-function-declaration failure testing for ldap_open

2024-03-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 1066137 -1 Bug #1066137 [src:gnupg2] gnupg2: -Werror=implicit-function-declaration failure testing for ldap_open Bug 1066137 cloned as bug 1066138 > reassign -1 gnupg1 1.4.23-1.1 Bug #1066138 [src:gnupg2] gnupg2:

Bug#1066137: gnupg2: -Werror=implicit-function-declaration failure testing for ldap_open

2024-03-12 Thread Thorsten Glaser
clone 1066137 -1 reassign -1 gnupg1 1.4.23-1.1 retitle -1 gnupg1: fails to build gpgkeys_ldap, probably due to -Werror=implicit-function-declaration thanks Dixi quod… >This matches the following failure mode at the end of the build: Same for gnupg1 according to the buildd page:

Bug#1066137: gnupg2: -Werror=implicit-function-declaration failure testing for ldap_open

2024-03-12 Thread Thorsten Glaser
Source: gnupg2 Version: 2.2.40-1.1 Severity: serious Justification: ftbfs X-Debbugs-Cc: t...@mirbsd.de Trying to binNMU gnupg2 to make it installable during t64 transition, I notice the following configury output: […] checking for library containing dn_skipname... none required checking whether

Bug#1066136: python3-xapian-haystack: unusable on stable due to use of deprecated module django.utils.six

2024-03-12 Thread Ole Peder Brandtzæg
Package: python3-xapian-haystack Version: 2.1.1-1 Severity: grave Tags: upstream patch Justification: renders package unusable Dear Maintainer, I installed python3-xapian-haystack in order to employ Xapian as a Haystack backend in mailman3-web on stable (bookworm). However, upon actually trying

Bug#1065974: marked as done (ghmm: FTBFS on arm{el,hf}: mcmc.c:144:3: error: implicit declaration of function ‘init_priors’ [-Werror=implicit-function-declaration])

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 22:53:37 + with message-id and subject line Bug#1065974: fixed in ghmm 0.9~rc3-6 has caused the Debian Bug report #1065974, regarding ghmm: FTBFS on arm{el,hf}: mcmc.c:144:3: error: implicit declaration of function ‘init_priors’

Bug#1066134: FTBFS due -Werror=implicit-function-declaration

2024-03-12 Thread Christoph Biedl
Source: ppp Version: 2.4.9-1+1.1 Severity: serious Tags: patch upstream ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian.a...@manchmal.in-ulm.de Hi Chris, ppp no longer builds in unstable here, tested in a minimal chroot. A build in a

Bug#1066117: FTBFS: missing build-dep on libnsl-dev

2024-03-12 Thread Preuße
On 12.03.2024 21:59, Aurelien Jarno wrote: Hi Aurelien, Starting with glibc 2.31, support for NIS (libnsl library) has been moved to a separate libnsl2 package. In order to allow a smooth transition, a libnsl-dev has been added to the libc6-dev package. This dependency has been temporarily

Bug#1065759: marked as done (libbio-samtools-perl: FTBFS: lib/Bio/DB/Sam.xs:324:4: error: implicit declaration of function ‘bam_sort_core’; did you mean ‘bam_format1_core’? [-Werror=implicit-function-

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 22:19:41 + with message-id and subject line Bug#1065759: fixed in libbio-samtools-perl 1.43-5 has caused the Debian Bug report #1065759, regarding libbio-samtools-perl: FTBFS: lib/Bio/DB/Sam.xs:324:4: error: implicit declaration of function

Bug#1062911: solvespace: NMU diff for 64-bit time_t transition

2024-03-12 Thread Rylie Pavlik
On Thu, 29 Feb 2024 17:03:41 + Benjamin Drung wrote: Source: solvespace Dear maintainer, Please find attached a final version of this patch for the time_t transition. This patch is being uploaded to unstable. Note that this adds a versioned build-dependency on dpkg-dev, to guard against

Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2

2024-03-12 Thread Antonio Terceiro
On Tue, Mar 12, 2024 at 09:13:09PM +0100, Sebastian Andrzej Siewior wrote: > tried with 1.50+nmu2 which is in deferred for the next 11h. So tomorrow > it should be all good. Please make sure to commit the patch to the pristine-tar git repository as well. signature.asc Description: PGP signature

Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2

2024-03-12 Thread Jeremy Bícha
On Tue, Mar 12, 2024 at 4:13 PM Sebastian Andrzej Siewior wrote: > > On 2024-03-12 09:26:32 [-0400], Jeremy Bícha wrote: > > > Could someone check this, please? > > > > Did you try running autopkgtests on this version? The autopkgtests fail for > > me. > > autopkgtests were the first thing that

Bug#1025559: marked as done (fwupd: dependency on transitional policykit-1 package)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 22:11:34 +0100 with message-id <43a1d607-d21f-4578-a8ab-736aed570...@debian.org> and subject line fwupd: dependency on transitional policykit-1 package has caused the Debian Bug report #1025559, regarding fwupd: dependency on transitional policykit-1 package to

Processed: fastdds: CVE-2023-50716

2024-03-12 Thread Debian Bug Tracking System
Processing control commands: > found -1 2.11.2+ds-6 Bug #1066119 [src:fastdds] fastdds: CVE-2023-50716 Marked as found in versions fastdds/2.11.2+ds-6. -- 1066119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1066118: telegram-desktop: does not start under Debian sid

2024-03-12 Thread Paul Martin
Package: telegram-desktop Version: 4.14.9+ds-1+b1 Severity: grave Justification: renders package unusable It depends on a symbol not present in the current libqt5quick5 (automatically rebuilt as part of the time_t migration). $ telegram-desktop telegram-desktop: symbol lookup error:

Bug#1066119: fastdds: CVE-2023-50716

2024-03-12 Thread Salvatore Bonaccorso
Source: fastdds Version: 2.11.2+ds-6.1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 2.11.2+ds-6 Hi, The following vulnerability was published for fastdds. CVE-2023-50716[0]: | eProsima Fast DDS (formerly Fast RTPS) is a C++

Processed: Re: Bug#1065759: Retitle libbio-samtools-perl: FTBFS on arm{el,hf}: lib/Bio/DB/Sam.xs:324:4: error: implicit declaration of function ‘bam_sort_core’; did you mean ‘bam_format1_core’? [-Wer

2024-03-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #1065759 [src:libbio-samtools-perl] libbio-samtools-perl: FTBFS: lib/Bio/DB/Sam.xs:324:4: error: implicit declaration of function ‘bam_sort_core’; did you mean ‘bam_format1_core’? [-Werror=implicit-function-declaration] Added tag(s) patch. --

Bug#1065759: Retitle libbio-samtools-perl: FTBFS on arm{el,hf}: lib/Bio/DB/Sam.xs:324:4: error: implicit declaration of function ‘bam_sort_core’; did you mean ‘bam_format1_core’? [-Werror=implicit-fu

2024-03-12 Thread Niko Tyni
Control: tag -1 patch On Tue, Mar 12, 2024 at 06:31:20PM +0100, Andreas Tille wrote: > I can confirm that this bug also occures on amd64 thus removing the > arm-restriction from the title. Unfortunately I have no idea how to fix > this (except by possibly suppressing the

Bug#1066117: FTBFS: missing build-dep on libnsl-dev

2024-03-12 Thread Aurelien Jarno
Source: proftpd-dfsg Version: 1.3.8.b+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: debian-gl...@lists.debian.org Usertags: libnsl-dev Dear maintainer, Starting with glibc 2.31, support for NIS (libnsl library) has been

Bug#1066115: mpg123: FTBFS: error: implicit declaration of function ‘mpg321_alsa_get_volume’ [-Werror=implicit-function-declaration]

2024-03-12 Thread Sebastian Ramacher
Source: mpg321 Version: 0.3.2-3.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/fetch.php?pkg=mpg321=armel=0.3.2-3.1%2Bb1=1710256758=0 gcc -DHAVE_CONFIG_H -I. -g

Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2

2024-03-12 Thread Sebastian Andrzej Siewior
On 2024-03-12 09:26:32 [-0400], Jeremy Bícha wrote: > > Could someone check this, please? > > Did you try running autopkgtests on this version? The autopkgtests fail for > me. autopkgtests were the first thing that pointed me here and they passed. If you say they fail for you then I may have

Bug#1026750: marked as done (glean-parser: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 18:46:05 + with message-id and subject line Bug#1026750: fixed in glean-parser 13.0.0-1 has caused the Debian Bug report #1026750, regarding glean-parser: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit

Bug#1065767: libopendbx: FTBFS on arm{el,hf}: mssql_basic.c:324:21: error: implicit declaration of function ‘dbpoll’ [-Werror=implicit-function-declaration]

2024-03-12 Thread Andrey Rakhmatullin
On Sat, Mar 09, 2024 at 09:26:38PM +0100, Sebastian Ramacher wrote: > mssql_basic.c: In function ‘mssql_odbx_result’: > mssql_basic.c:324:21: error: implicit declaration of function ‘dbpoll’ > [-Werror=implicit-function-declaration] > 324 | if( dbpoll( dbproc, ms, , ) == FAIL )

Processed: intel-microcode: CVE-2023-43490 CVE-2023-39368 CVE-2023-38575 CVE-2023-22655 CVE-2023-28746

2024-03-12 Thread Debian Bug Tracking System
Processing control commands: > found -1 3.20231114.1~deb12u1 Bug #1066108 [src:intel-microcode] intel-microcode: CVE-2023-43490 CVE-2023-39368 CVE-2023-38575 CVE-2023-22655 CVE-2023-28746 Marked as found in versions intel-microcode/3.20231114.1~deb12u1. > found -1 3.20231114.1~deb11u1 Bug

Processed: Retitle libbio-samtools-perl: FTBFS on arm{el,hf}: lib/Bio/DB/Sam.xs:324:4: error: implicit declaration of function ‘bam_sort_core’; did you mean ‘bam_format1_core’? [-Werror=implicit-funct

2024-03-12 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 libbio-samtools-perl: FTBFS: lib/Bio/DB/Sam.xs:324:4: error: > implicit declaration of function ‘bam_sort_core’; did you mean > ‘bam_format1_core’? [-Werror=implicit-function-declaration] Bug #1065759 [src:libbio-samtools-perl] libbio-samtools-perl:

Bug#1065759: Retitle libbio-samtools-perl: FTBFS on arm{el,hf}: lib/Bio/DB/Sam.xs:324:4: error: implicit declaration of function ‘bam_sort_core’; did you mean ‘bam_format1_core’? [-Werror=implicit-fun

2024-03-12 Thread Andreas Tille
Control: retitle -1 libbio-samtools-perl: FTBFS: lib/Bio/DB/Sam.xs:324:4: error: implicit declaration of function ‘bam_sort_core’; did you mean ‘bam_format1_core’? [-Werror=implicit-function-declaration] Control: tags -1 help thanks I can confirm that this bug also occures on amd64 thus

Bug#1066108: intel-microcode: CVE-2023-43490 CVE-2023-39368 CVE-2023-38575 CVE-2023-22655 CVE-2023-28746

2024-03-12 Thread Salvatore Bonaccorso
Source: intel-microcode Version: 3.20231114.1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 3.20231114.1~deb12u1 Control: found -1 3.20231114.1~deb11u1 Hi, The following vulnerabilities were

Processed: libstb: diff for NMU version 0.0~git20230129.5736b15+ds-1.2

2024-03-12 Thread Debian Bug Tracking System
Processing control commands: > tags 1065764 + patch Bug #1065764 [src:libstb] libstb: FTBFS on arm{el,hf}: stb_dxt.c:608:7: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration] Added tag(s) patch. > tags 1065764 + pending Bug #1065764 [src:libstb] libstb:

Bug#1065764: libstb: diff for NMU version 0.0~git20230129.5736b15+ds-1.2

2024-03-12 Thread Andrey Rakhmatullin
Control: tags 1065764 + patch Control: tags 1065764 + pending Dear maintainer, I've prepared an NMU for libstb (versioned as 0.0~git20230129.5736b15+ds-1.2) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. Regards. -- WBR, wRAR diff -Nru

Bug#1064762: Works with vtk9.3 installed in venv via pip (was Re: dune-grid: FTBFS: make[1]: *** [/usr/share/dune/dune-debian.mk:39: override_dh_auto_test] Error 1)

2024-03-12 Thread Markus Blatt
Hi, I did some further tests with the provided test case. If I install vtk (latest version 9.3) with pip in a venve. The script also does not report an error for the relative paths. Tested on stable and in a sid chroot. Best, Markus

Bug#1000061: cfengine3: depends on obsolete pcre3 library

2024-03-12 Thread Christoph Martin
version 3.24.0 is not released yet but expected for mid 2024. Am 18.12.23 um 15:14 schrieb Bastian Germann: On Fri, 18 Aug 2023 12:01:17 +0200 Bastian Germann wrote: cfengine3 is a key package and requires pcre, so this has to be fixed. Upstream claims that this is fixed with 3.24.0.

Bug#1057420: marked as done (cfengine3: FTBFS: dh_install: warning: cfengine3 missing files: debian/tmp/lib/systemd)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 15:49:38 +0100 with message-id <6e814006-e80f-4c61-b353-14aad38ca...@uni-mainz.de> and subject line Fwd: cfengine3_3.21.4-1_source.changes ACCEPTED into unstable has caused the Debian Bug report #1057420, regarding cfengine3: FTBFS: dh_install: warning:

Bug#1065323: marked as done (petsc: bad Provides in libpetsc64-real3.19t64, libpetsc64-complex3.19t64 and libpetsc-real3.19t64)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 15:44:51 +0100 with message-id and subject line Re: Bug#1065323 petsc: bad Provides in libpetsc64-real3.19t64, libpetsc64-complex3.19t64 and libpetsc-real3.19t64 has caused the Debian Bug report #1065323, regarding petsc: bad Provides in

Processed: Re: Bug#1065323 petsc: bad Provides in libpetsc64-real3.19t64, libpetsc64-complex3.19t64 and libpetsc-real3.19t64

2024-03-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1065323 3.19.6+dfsg1-2.2 Bug #1065323 [src:petsc] petsc: bad Provides in libpetsc64-real3.19t64, libpetsc64-complex3.19t64 and libpetsc-real3.19t64 Marked as fixed in versions petsc/3.19.6+dfsg1-2.2. > thanks Stopping processing here.

Bug#1064561: marked as done (dune-grid: FTBFS on i386: 98% tests passed, 1 tests failed out of 66)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 14:37:44 + with message-id and subject line Bug#1064561: fixed in dune-grid 2.9.0-3 has caused the Debian Bug report #1064561, regarding dune-grid: FTBFS on i386: 98% tests passed, 1 tests failed out of 66 to be marked as done. This means that you claim

Bug#1065610: marked as done (libguestfs0t64: All appliance dependencies lost during time_t transition)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 13:49:26 + with message-id and subject line Bug#1065610: fixed in libguestfs 1:1.52.0-5 has caused the Debian Bug report #1065610, regarding libguestfs0t64: All appliance dependencies lost during time_t transition to be marked as done. This means that you

Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2

2024-03-12 Thread Jeremy Bícha
On Sun, Mar 10, 2024 at 4:46 PM Sebastian Andrzej Siewior wrote: > I've prepared an NMU for pristine-tar (versioned as 1.50+nmu2) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. > > Could someone check this, please? Did you try running autopkgtests on

Bug#1065127: marked as done (pike8.0: recent libc6-dev change causes Yp module to be empty)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 12:20:11 + with message-id and subject line Bug#1065127: fixed in pike8.0 8.0.1738-1.3 has caused the Debian Bug report #1065127, regarding pike8.0: recent libc6-dev change causes Yp module to be empty to be marked as done. This means that you claim that

Processed: Re: pygobject: FTBFS on armhf: time_t build test failure

2024-03-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1066032 src:pygobject Bug #1066032 [src:gobject-introspection] pygobject: FTBFS on armhf: time_t build test failure Added indication that 1066032 affects src:pygobject > End of message, stopping processing here. Please contact me if you

Processed: Re: pygobject: FTBFS on armhf: time_t build test failure

2024-03-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1066032 src:gobject-introspection 1.78.1-15 Bug #1066032 [src:pygobject] pygobject: FTBFS on armhf: time_t build test failure Bug reassigned from package 'src:pygobject' to 'src:gobject-introspection'. No longer marked as found in

Bug#1063461: marked as done (lsof: FTBFS during tests: LTlock ... lock mismatch: expected W, got " ")

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 12:07:05 + with message-id and subject line Bug#1063461: fixed in lsof 4.95.0-1.1 has caused the Debian Bug report #1063461, regarding lsof: FTBFS during tests: LTlock ... lock mismatch: expected W, got " " to be marked as done. This means that you claim

Bug#1065283: marked as done (lsof: recent libc6-dev change causes the RPC support to be dropped)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 12:07:05 + with message-id and subject line Bug#1065283: fixed in lsof 4.95.0-1.1 has caused the Debian Bug report #1065283, regarding lsof: recent libc6-dev change causes the RPC support to be dropped to be marked as done. This means that you claim that

Bug#1064707: devscripts: FTBFS: AssertionError: black found code that needs reformatting:

2024-03-12 Thread Simon McVittie
On Sun, 25 Feb 2024 at 20:36:58 +0100, Lucas Nussbaum wrote: > > FAIL: test_black (devscripts.test.test_black.BlackTestCase.test_black) > > Test: Run black code formatter on Python source code. I think lint checks like this one should be run by contributors and CI when targeting the main branch,

Bug#1066003: libberkeleydb-perl: FTBFS on arm{el,hf}: Failed 1/35 test programs. 1/1861 subtests failed.

2024-03-12 Thread Graham Inggs
I think the actual error is: # : BDB4015 library build did not include support for sequences # Failed test (t/sequence.t at line 33) # The object isn't defined Can't call method "set_cachesize" on an undefined value at t/sequence.t line 35. # Looks like you planned 13 tests but only ran

Bug#1066078: marked as done (vigor FTBFS due to -Werror=implicit-function-declaration)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 11:08:07 + with message-id and subject line Bug#1066078: fixed in vigor 0.016-32 has caused the Debian Bug report #1066078, regarding vigor FTBFS due to -Werror=implicit-function-declaration to be marked as done. This means that you claim that the problem

Processed: Bug#1066078 marked as pending in vigor

2024-03-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1066078 [src:vigor] vigor FTBFS due to -Werror=implicit-function-declaration Added tag(s) pending. -- 1066078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1066078: marked as pending in vigor

2024-03-12 Thread Colin Watson
Control: tag -1 pending Hello, Bug #1066078 in vigor 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#1065626: libgtk2.0-0t64 / libgtk2.0-bin dependency problem makes dpkg fail with attempt of removal of libgtk2.0-common

2024-03-12 Thread Vincent Lefevre
The same problem occurred on another machine, with other packages: dpkg: dependency problems prevent removal of libjte2:amd64: libisofs6t64:amd64 depends on libjte2. dpkg: error processing package libjte2:amd64 (--purge): dependency problems - not removing (Reading database ... 708510 files

Bug#1065603: marked as done (libdebuginfod1t64 dependency problem makes dpkg fail with attempt of removal of libdebuginfod-common)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 11:40:04 +0100 with message-id <46dc2d0c-93af-4ce1-826a-ab0897a96...@debian.org> and subject line Re: libdebuginfod1t64 dependency problem makes dpkg fail with attempt of removal of libdebuginfod-common has caused the Debian Bug report #1065603, regarding

Bug#989736: Bug#1066051: openjdk-8: make package usable on systems without t64 packages

2024-03-12 Thread fabstz-it
Thanks for the information. Le lundi 11 mars 2024 à 21:52:54 UTC+1, Thorsten Glaser a écrit : close 1066051 thanks Fab Stz dixit: >I usually install openjdk-8 from unstable on bookworm. This has never been officially supported. I’ve had an entire discussion around that last

Bug#1065724: epics-base: FTBFS on amd64: Tests failed

2024-03-12 Thread PICCA Frederic-Emmanuel
Here an analyse of the FTBFS On the amd64, I have two failures dureing the test Test Summary Report --- testPVAServer.t(Wstat: 0 Tests: 0 Failed: 0) Parse errors: No plan found in TAP output Files=6, Tests=129, 1 wallclock secs ( 0.05 usr 0.01 sys + 0.09 cusr 0.06 csys

Bug#1063754:

2024-03-12 Thread james
stop

Bug#1065610: marked as done (libguestfs0t64: All appliance dependencies lost during time_t transition)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 09:21:35 + with message-id and subject line Bug#1065610: fixed in libguestfs 1:1.52.0-4 has caused the Debian Bug report #1065610, regarding libguestfs0t64: All appliance dependencies lost during time_t transition to be marked as done. This means that you

Bug#1065395: spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space

2024-03-12 Thread Andreas Beckmann
Hi Paul, On 06/03/2024 06.20, Paul Gevers wrote: Unfortunately the test still takes upto 33 GB at least (see below). Did you have time to test the -12 version, yet? Andreas

Bug#1065214: marked as done (iproute2: recent libc6-dev change causes the RPC support to be dropped)

2024-03-12 Thread Debian Bug Tracking System
Your message dated Tue, 12 Mar 2024 08:43:12 + with message-id and subject line Bug#1065214: fixed in iproute2 6.7.0-2.1 has caused the Debian Bug report #1065214, regarding iproute2: recent libc6-dev change causes the RPC support to be dropped to be marked as done. This means that you claim

Processed: NMU iproute2

2024-03-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #1065214 [src:iproute2] iproute2: recent libc6-dev change causes the RPC support to be dropped Added tag(s) pending. -- 1065214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065214 Debian Bug Tracking System Contact

Bug#1065214: NMU iproute2

2024-03-12 Thread Helmut Grohne
Control: tags -1 + pending Hi Luca, this bug causes issues to /usr-move. iproute2 pulls libtirpc3 and nothing pulls libtirpc3t64. Hence, the we still include libtirpc3, which is aliased rather than libtirpc3t64, which is /usr-moved. To fix this, I'd need a binNMU of iproute2, but this bug would

Bug#1065751: pristine-tar: diff for NMU version 1.50+nmu2

2024-03-12 Thread Sebastian Andrzej Siewior
On 2024-03-11 21:23:03 [+], Amin Bandali wrote: > Hi, Hi, > On Mon, Mar 11, 2024 at 05:55:31PM +0100, Sebastian Andrzej Siewior wrote: > > On 2024-03-11 00:05:54 [+], Amin Bandali wrote: > > > Hi Sebastian, all, > > Hi, > > > > > Will this fix be enough for addressing all cases, though?

Bug#1066078: vigor FTBFS due to -Werror=implicit-function-declaration

2024-03-12 Thread Helmut Grohne
Source: vigor Version: 0.016-31 Severity: serious Tags: ftbfs Due to time64 and thus enabling -Werror=implicit-function-declaration, vigor now fails to build from source: | ../../build/../cl/cl_screen.c: In function ‘cl_screen’: | ../../build/../cl/cl_screen.c:112:25: error: implicit declaration