Bug#1069747: ext4 data loss issue in backport kernels still unfixed?

2024-04-23 Thread Robin
Package: linux-image-6.6.13+bpo-amd64 Version: 6.6.13 Severity: grave The issue was fixed already in the 6.1 kernels, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 From that bug report I read that all kernels are safe if both commits are present: 91562895f803 ("ext4: properly

Bug#1065341: marked as done (src:openstructure: unsatisfied build dependency in testing: sip-dev)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Wed, 24 Apr 2024 06:34:58 + with message-id and subject line Bug#1065341: fixed in openstructure 2.5.0-2 has caused the Debian Bug report #1065341, regarding src:openstructure: unsatisfied build dependency in testing: sip-dev to be marked as done. This means that you claim

Bug#1064311: rdkit: NMU diff for 64-bit time_t transition

2024-04-23 Thread Andrius Merkys
Hi, On Mon, 19 Feb 2024 21:35:16 + Steve Langasek wrote:> Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together

Processed: zeroc-ice: FTBFS on armel: appears to be out-of-memory condition

2024-04-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1069538 + moreinfo Bug #1069538 [src:zeroc-ice] zeroc-ice: FTBFS on armel: make[3]: *** [Makefile:29: tests] Error 1 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069538: https://bu

Bug#1069538: zeroc-ice: FTBFS on armel: make[3]: out of memory error

2024-04-23 Thread Chris Knadle
Hello Lucas. The zeroc-ice 3.7.10-2.2 package built correctly on an armel buildd within two weeks ago: https://buildd.debian.org/status/logs.php?pkg=zeroc-ice&ver=3.7.10-2.2&arch=armel The underlying error in the build logs you sent looks like an out-of-memory condition: > Failed to execut

Bug#1069363: marked as done (atlas-ecmwf: FTBFS on arm64: No such file or directory)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Wed, 24 Apr 2024 05:49:10 + with message-id and subject line Bug#1069363: fixed in atlas-ecmwf 0.37.0-1 has caused the Debian Bug report #1069363, regarding atlas-ecmwf: FTBFS on arm64: No such file or directory to be marked as done. This means that you claim that the probl

Processed: Re: nvidia-open-gpu-kernel-modules: CVE-2024-0074, CVE-2024-0075, CVE-2024-0078

2024-04-23 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1064991 {Done: Andreas Beckmann } [src:nvidia-open-gpu-kernel-modules] nvidia-open-gpu-kernel-modules: CVE-2024-0074, CVE-2024-0075, CVE-2024-0078 Severity set to 'important' from 'serious' -- 1064991: https://bugs.debian.org/cgi-bin/bu

Bug#1064991: nvidia-open-gpu-kernel-modules: CVE-2024-0074, CVE-2024-0075, CVE-2024-0078

2024-04-23 Thread Andreas Beckmann
Followup-For: Bug #1064991 Control: severity -1 important migration is currently blocked by the t64 migration Andreas

Bug#1069538: zeroc-ice: FTBFS on armel: appears to be out-of-memory condition

2024-04-23 Thread Chris Knadle
tags 1069538 + moreinfo thanks

Processed: upstream patch available

2024-04-23 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1058362 [src:libsass-python] libsass-python: FTBFS: TypeError: not all arguments converted during string formatting Added tag(s) patch. -- 1058362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058362 Debian Bug Tracking System Contact ow

Processed: upstream patch available

2024-04-23 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1042614 [src:libsass-python] libsass-python: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting Added tag(s) patch. -- 1042614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042614 Debian

Processed: downgrade 1066669

2024-04-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # https://lists.debian.org/debian-devel/2024/03/msg00232.html > severity 109 important Bug #109 {Done: Nicholas Breen } [src:grace] grace: FTBFS: configure: error: M*tif has not been found Severity set to 'important' from 'serious' > user

Bug#1042614: upstream patch available

2024-04-23 Thread Matthias Klose
Control: tags -1 + patch patch at https://launchpadlibrarian.net/725823106/libsass-python_0.22.0-1build1_0.22.0-1ubuntu1.diff.gz

Bug#1056410: marked as done (i3pystatus autopkg tests fail with Python 3.12)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Wed, 24 Apr 2024 02:35:14 + with message-id and subject line Bug#1056410: fixed in i3pystatus 3.35+git20191126.5a8eaf4-2.2 has caused the Debian Bug report #1056410, regarding i3pystatus autopkg tests fail with Python 3.12 to be marked as done. This means that you claim tha

Bug#1066536: marked as done (sniffit: FTBFS: sn_generation.c:66:1: error: implicit declaration of function ‘input_field’ [-Werror=implicit-function-declaration])

2024-04-23 Thread Debian Bug Tracking System
Your message dated Wed, 24 Apr 2024 02:36:12 + with message-id and subject line Bug#1066536: fixed in sniffit 0.6-1 has caused the Debian Bug report #1066536, regarding sniffit: FTBFS: sn_generation.c:66:1: error: implicit declaration of function ‘input_field’ [-Werror=implicit-function-decla

Bug#1069004: marked as done (casacore-data-services: Hard coded build-depends on decrufted lib libcasa-meas7)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 19:49:06 + with message-id and subject line Bug#1069004: fixed in casacore-data-sources 2-5 has caused the Debian Bug report #1069004, regarding casacore-data-services: Hard coded build-depends on decrufted lib libcasa-meas7 to be marked as done. This mean

Bug#1066337: marked as done (tightvnc: FTBFS: vncconnect.c:17:5: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration])

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 19:34:45 + with message-id and subject line Bug#1066337: fixed in tightvnc 1:1.3.10-8 has caused the Debian Bug report #1066337, regarding tightvnc: FTBFS: vncconnect.c:17:5: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declarat

Bug#1069686: libsequoia-octopus-librnp: postinst script Syntax error: "fi" unexpected

2024-04-23 Thread Daniel Kahn Gillmor
On Mon 2024-04-22 20:17:54 +, Holger Levsen wrote: > fixed in git. thanks! I've just uninstalled the octopus, but i'll consider reinstalling it later if this and some of the performance issues can be ironed out (or maybe to help iron out the performance issues, visible upstream at https://git

Bug#1069728: freerdp2: CVE-2024-32039 CVE-2024-32040 CVE-2024-32041 CVE-2024-32458 CVE-2024-32459 CVE-2024-32460

2024-04-23 Thread Salvatore Bonaccorso
Source: freerdp2 Version: 2.11.5+dfsg1-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for freerdp2. CVE-2024-32039[0]: | FreeRDP is a free implementation of the Re

Processed: nautilus-wipe: diff for NMU version 0.4.alpha2-0.2

2024-04-23 Thread Debian Bug Tracking System
Processing control commands: > tags 1069334 + patch Bug #1069334 [nautilus-wipe] Not installable due to hardcoded pre-t64 library deps Added tag(s) patch. > tags 1069334 + pending Bug #1069334 [nautilus-wipe] Not installable due to hardcoded pre-t64 library deps Added tag(s) pending. -- 106933

Bug#1069334: nautilus-wipe: diff for NMU version 0.4.alpha2-0.2

2024-04-23 Thread Sebastian Ramacher
Control: tags 1069334 + patch Control: tags 1069334 + pending Dear maintainer, I've prepared an NMU for nautilus-wipe (versioned as 0.4.alpha2-0.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru nautilus-wipe-0.4.alp

Bug#1061330: marked as done (calamares: identified for time_t transition but no ABI in shlibs)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 21:18:51 +0200 with message-id and subject line has caused the Debian Bug report #1061330, regarding calamares: identified for time_t transition but no ABI in shlibs to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1069687: librust-bitflags-1-dev: fails to co-install

2024-04-23 Thread Fabian Grünbichler
On Tue, Apr 23, 2024 at 07:51:36AM +0200, Helmut Grohne wrote: > Hi Matthias, > > On Mon, Apr 22, 2024 at 10:34:11PM +0200, Matthias Geiger wrote: > > This is the same situation as in #1040477. This is an issue wrt how we > > generate the semvers. I image rust-proc-macro-crate-1 would pose the sam

Bug#1069724: slurm-wlm: autopkgtest regression on !amd64: trying to overwrite '/usr/lib/-linux-gnu/slurm-wlm/accounting_storage_mysql.so'

2024-04-23 Thread Paul Gevers
Source: slurm-wlm Version: 23.11.4-1.4 X-Debbugs-CC: bdr...@debian.org, vor...@debian.org, mckins...@debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of slurm-wlm the autopkgtest of slurm-wlm fails in testing when that a

Processed: bug 1067913 is forwarded to https://sourceforge.net/p/linssid/discussion/bugs/thread/90c0e93d6b/

2024-04-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1067913 > https://sourceforge.net/p/linssid/discussion/bugs/thread/90c0e93d6b/ Bug #1067913 [src:linssid] FTBFS: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’} Set Bug forwarded-to-address to 'https:

Bug#1064920: marked as done (FTBFS on 32-bit architectures)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:50:36 + with message-id and subject line Bug#1064920: fixed in rshim-user-space 2.0.20+debian-2 has caused the Debian Bug report #1064920, regarding FTBFS on 32-bit architectures to be marked as done. This means that you claim that the problem has been d

Bug#1067062: marked as done (OpenSSL.crypto.PKCS12 is removed in pyOpenSSL 24.1.0)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:27:02 + with message-id and subject line Bug#1069654: Removed package(s) from unstable has caused the Debian Bug report #1067062, regarding OpenSSL.crypto.PKCS12 is removed in pyOpenSSL 24.1.0 to be marked as done. This means that you claim that the prob

Bug#1055179: marked as done (salt: CVE-2023-34049)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:27:02 + with message-id and subject line Bug#1069654: Removed package(s) from unstable has caused the Debian Bug report #1055179, regarding salt: CVE-2023-34049 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1051504: marked as done (salt: CVE-2023-20897 CVE-2023-20898)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:27:02 + with message-id and subject line Bug#1069654: Removed package(s) from unstable has caused the Debian Bug report #1051504, regarding salt: CVE-2023-20897 CVE-2023-20898 to be marked as done. This means that you claim that the problem has been deal

Bug#1033808: marked as done (ImportError: cannot import name 'Markup' from 'jinja2')

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:27:02 + with message-id and subject line Bug#1069654: Removed package(s) from unstable has caused the Debian Bug report #1033808, regarding ImportError: cannot import name 'Markup' from 'jinja2' to be marked as done. This means that you claim that the pr

Bug#1028421: marked as done (Only include in Bookworm with commitment to stable updates)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:27:02 + with message-id and subject line Bug#1069654: Removed package(s) from unstable has caused the Debian Bug report #1028421, regarding Only include in Bookworm with commitment to stable updates to be marked as done. This means that you claim that th

Bug#1022530: marked as done (src:salt: autopkgtest timeouts)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:27:02 + with message-id and subject line Bug#1069654: Removed package(s) from unstable has caused the Debian Bug report #1022530, regarding src:salt: autopkgtest timeouts to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1021920: marked as done (FTBFS: dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned exit code 13)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:27:02 + with message-id and subject line Bug#1069654: Removed package(s) from unstable has caused the Debian Bug report #1021920, regarding FTBFS: dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned exit code 13 to be marked as done

Bug#1021317: marked as done (salt-master: Fails to start with "zmq.error.ZMQError: Invalid argument")

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:27:02 + with message-id and subject line Bug#1069654: Removed package(s) from unstable has caused the Debian Bug report #1021317, regarding salt-master: Fails to start with "zmq.error.ZMQError: Invalid argument" to be marked as done. This means that you

Bug#1013872: marked as done (salt: CVE-2022-22967)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:27:02 + with message-id and subject line Bug#1069654: Removed package(s) from unstable has caused the Debian Bug report #1013872, regarding salt: CVE-2022-22967 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#991245: marked as done (diaspora fails to handle triggers in postinst)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:25:05 + with message-id and subject line Bug#1069615: Removed package(s) from unstable has caused the Debian Bug report #991245, regarding diaspora fails to handle triggers in postinst to be marked as done. This means that you claim that the problem has

Bug#974014: marked as done (Fails to install due to depending on ruby-rails < 6.0)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:25:05 + with message-id and subject line Bug#1069615: Removed package(s) from unstable has caused the Debian Bug report #974014, regarding Fails to install due to depending on ruby-rails < 6.0 to be marked as done. This means that you claim that the prob

Bug#924109: marked as done (diaspora: fails to install noninteractively)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:25:05 + with message-id and subject line Bug#1069615: Removed package(s) from unstable has caused the Debian Bug report #924109, regarding diaspora: fails to install noninteractively to be marked as done. This means that you claim that the problem has be

Bug#1067084: marked as done (ruby-sigar: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64")

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:26:18 + with message-id and subject line Bug#1069619: Removed package(s) from unstable has caused the Debian Bug report #1067084, regarding ruby-sigar: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only

Bug#1031479: marked as done (ruby-eye: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'cell

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 17:25:42 + with message-id and subject line Bug#1069616: Removed package(s) from unstable has caused the Debian Bug report #1031479, regarding ruby-eye: FTBFS: ERROR: Test "ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue

Bug#1069520: sbcl: FTBFS on armhf: make[1]: *** [debian/rules:53: override_dh_auto_build] Error 1

2024-04-23 Thread Peter Van Eynde
This looks a lot like a problem between the `OBSERVED-INTERNAL-REAL-TIME-DELTA-SEC` which is a word and the new 64-bit counters. ❯ git grep observed-internal-real-time-delta-sec src/code/thread-structs.lisp: #-64-bit (observed-internal-real-time-delta-sec 0 :type sb-vm:word) src/code/unix.lisp

Bug#1066327: chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration]

2024-04-23 Thread Zixing Liu
Package: chmlib Followup-For: Bug #1066327 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Dear Maintainer, This is the updated patch that tries to address the build issue on amd64. Thanks for considering the patch. -- System Information: D

Processed: Re: chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration]

2024-04-23 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1066327 [src:chmlib] chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration] Ignoring request to alter tags of bug #1066327 to the same tags previously set -- 1066327: https:/

Bug#1069191: marked as done (glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 16:47:08 + with message-id and subject line Bug#1069191: fixed in glibc 2.36-9+deb12u6 has caused the Debian Bug report #1069191, regarding glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence to be

Bug#1069191: marked as done (glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 16:47:50 + with message-id and subject line Bug#1069191: fixed in glibc 2.31-13+deb11u9 has caused the Debian Bug report #1069191, regarding glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape sequence to be

Bug#1056447: marked as done (pontos autopkg tests fail with Python 3.12)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 16:35:41 + with message-id and subject line Bug#1056447: fixed in pontos 24.3.1-1 has caused the Debian Bug report #1056447, regarding pontos autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt

Bug#1066225: RFS: libtranscript/0.3.3-1.1 [NMU] [RC] -- Character set conversion library

2024-04-23 Thread Bo YU
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "libtranscript": * Package name : libtranscript Version : 0.3.3-1.1 Upstream contact : Gertjan Halkes * URL : https://os.ghalkes.nl/libtranscript.html * L

Bug#1041415: details

2024-04-23 Thread David Edmondson
tag 1041415 - upstream thanks Ultimately this fails because /proc is not available in the chroot. The version of libc in use *emulates* fchmodat() using /proc/self/fd rather than using the fchmodat system call. When /proc is provided in the chroot, the fchmodat emulation works successfully and e

Processed: Re: details

2024-04-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 1041415 - upstream Bug #1041415 [emacs] emacs: fails to install: post-installation script subprocess returned error exit status 1 Removed tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 10414

Bug#1067075: marked as done (openvas-scanner: FTBFS on arm{el,hf}: /<>/src/attack.c:1617:16: error: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘__time64_t’

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 15:06:04 + with message-id and subject line Bug#1067075: fixed in openvas-scanner 23.0.1-1 has caused the Debian Bug report #1067075, regarding openvas-scanner: FTBFS on arm{el,hf}: /<>/src/attack.c:1617:16: error: format ‘%ld’ expects argument of type ‘lo

Bug#1069692: marked as done (nfs-ganesha: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64")

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 14:37:58 + with message-id and subject line Bug#1069692: fixed in nfs-ganesha 4.3-10 has caused the Debian Bug report #1069692, regarding nfs-ganesha: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only wi

Processed: Bug#1067075 marked as pending in openvas-scanner

2024-04-23 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1067075 [src:openvas-scanner] openvas-scanner: FTBFS on arm{el,hf}: /<>/src/attack.c:1617:16: error: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘__time64_t’ {aka ‘long long int’} [-Werror=format=] Added tag(s) pen

Bug#1067075: marked as pending in openvas-scanner

2024-04-23 Thread Sophie Brun
Control: tag -1 pending Hello, Bug #1067075 in openvas-scanner 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-security-team/openvas-scanner/-/commit/5fd9ac

Bug#1052376: lxpanel: no longer obeys its geometry settings

2024-04-23 Thread jim_p
Package: lxpanel Version: 0.10.2.rc1-1 Followup-For: Bug #1052376 X-Debbugs-Cc: pitsior...@outlook.com Since there is no interest from the maintainers in fixing a 6+ month old grave bug, I want to ask. Has anyone moved away from lxpanel or even lxde? I would switch to lxqt, but lxqt is one major v

Processed: Bug#1058300 marked as pending in python-pytest-flake8

2024-04-23 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058300 [src:python-pytest-flake8] python-pytest-flake8: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Added tag(s) pending. -- 1058300: https://bugs.debian.org/cgi-bin/bugrepo

Bug#1058300: marked as pending in python-pytest-flake8

2024-04-23 Thread Timo Röhling
Control: tag -1 pending Hello, Bug #1058300 in python-pytest-flake8 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/python-pytest-flake8/-/

Bug#1069332: marked as pending in gvmd

2024-04-23 Thread Sophie Brun
Control: tag -1 pending Hello, Bug #1069332 in gvmd 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-security-team/gvmd/-/commit/f32a81f1ac69996103106e233320

Processed: Re: details

2024-04-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 1041415 + upstream Bug #1041415 [emacs] emacs: fails to install: post-installation script subprocess returned error exit status 1 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041415

Processed: Bug#1069332 marked as pending in gvmd

2024-04-23 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1069332 [gvmd] Not installable due to hardcoded pre-t64 library deps Added tag(s) pending. -- 1069332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1041415: details

2024-04-23 Thread David Edmondson
tag 1041415 + upstream thanks The error message: >>Error occurred processing /usr/share/emacs/site-lisp/debian-startup.el: File >>error (("Doing chmod" "Operation not supported" >>"/usr/share/emacs/site-lisp/debian-startup.elcFx8oFi")) comes from the emacs byte compiler. Tracing through the by

Bug#1069692: nfs-ganesha: FTBFS on arm{el,hf}: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

2024-04-23 Thread Christoph Martin
Hi Sebastian, this is interesting. If you take a look into the commandline you see -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 there is -D_FILE_OFFSET_BITS=64 even twice. .. But the GPFS code has: /* _FILE_OFFSET_BITS macro causes F_GETLK/SETLK/SETLKW to be defined to * F_GETLK64/SETLK64/SETLKW6

Bug#1069441: marked as done (pi-tm1638: FTBFS on armhf: configure: error: cannot run C compiled programs.)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 13:20:18 + with message-id and subject line Bug#1069441: fixed in pi-tm1638 1.0-2 has caused the Debian Bug report #1069441, regarding pi-tm1638: FTBFS on armhf: configure: error: cannot run C compiled programs. to be marked as done. This means that you cl

Processed: block 1060330 with 1069715 1069716

2024-04-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1060330 with 1069715 1069716 Bug #1060330 [sccache] sccache: Please enable distributed storage before the migration to testing/next release 1060330 was not blocked by any bugs. 1060330 was not blocking any bugs. Added blocking bug(s) of 106

Bug#1041415: details

2024-04-23 Thread David Edmondson
Ah, by specifically using a chroot rather than a systemd-nspawn container, I *am* able to reproduce the failure. Off to debug... -- I'm not living in the real world, no more, no more.

Bug#1041415: details

2024-04-23 Thread David Edmondson
I was not able to reproduce this failure. Is there anything interesting about the filesystem underlying the chroot used during the install? Is root able to write files with impunity in the relevant directories? Are you able to reproduce the failure? -- Time is waiting to explain, why refuse?

Bug#1069715: librust-opendal-dev: package is impossible to install

2024-04-23 Thread Jonas Smedegaard
Package: librust-opendal-dev Version: 0.44.1-1+b1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package is impossible to install due to numerous missing dependencies including librust-async-backtrace-0.2+default-dev and librust-atomic-

Bug#1066584: marked as done (gnome-breakout: FTBFS: anim.c:58:17: error: implicit declaration of function ‘gb_error’; did you mean ‘g_error’? [-Werror=implicit-function-declaration])

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 12:19:16 + with message-id and subject line Bug#1066584: fixed in gnome-breakout 0.5.3-8 has caused the Debian Bug report #1066584, regarding gnome-breakout: FTBFS: anim.c:58:17: error: implicit declaration of function ‘gb_error’; did you mean ‘g_error’? [

Bug#1066327: chmlib: FTBFS: chm_http.c:167:32: error: implicit declaration of function ‘inet_addr’ [-Werror=implicit-function-declaration]

2024-04-23 Thread Kartik Mistry
On Tue, Apr 23, 2024 at 12:48 AM Zixing Liu wrote: > In Ubuntu, the attached patch was applied to achieve the following: > > * debian/patches/implicit-declarations.patch: Add missing includes and > fix large file support. (LP: #2062947). > Thanks! Patch builds package locally, but seems f

Bug#1017834: analysis

2024-04-23 Thread David Edmondson
The failure to build elpa-cider is caused by: > In toplevel form: > cider.el:218:1: Error: Wrong number of arguments: (3 . 4), 2 In the source, this corresponds to: > (define-obsolete-variable-alias 'cider-default-repl-command > 'cider-jack-in-default) In recent versions of emacs, the definiti

Bug#1066770: marked as done (ccdproc: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 10:49:07 + with message-id and subject line Bug#1066770: fixed in ccdproc 2.4.1-3 has caused the Debian Bug report #1066770, regarding ccdproc: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Bug#1066379: marked as done (loqui: FTBFS: loqui-core-gtk.gob:256:25: error: implicit declaration of function ‘account_list_dialog_open_for_connect’ [-Werror=implicit-function-declaration])

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 10:34:09 + with message-id and subject line Bug#1066379: fixed in loqui 0.7.0-2.1 has caused the Debian Bug report #1066379, regarding loqui: FTBFS: loqui-core-gtk.gob:256:25: error: implicit declaration of function ‘account_list_dialog_open_for_connect’ [

Bug#1066491: marked as done (libt3window: FTBFS: .config.c:8:13: error: implicit declaration of function ‘setupterm’; did you mean ‘set_term’? [-Werror=implicit-function-declaration])

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 10:19:06 + with message-id and subject line Bug#1066491: fixed in libt3window 0.4.0-1.1 has caused the Debian Bug report #1066491, regarding libt3window: FTBFS: .config.c:8:13: error: implicit declaration of function ‘setupterm’; did you mean ‘set_term’? [

Bug#1066491: libt3window: FTBFS: .config.c:8:13: error: implicit declaration of function ‘setupterm’

2024-04-23 Thread Bastian Germann
I am sponsoring a NMU with the debdiff given in #1069662.

Bug#1069686: marked as done (libsequoia-octopus-librnp: postinst script Syntax error: "fi" unexpected)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 09:34:49 + with message-id and subject line Bug#1069686: fixed in rust-sequoia-octopus-librnp 1.8.1-4 has caused the Debian Bug report #1069686, regarding libsequoia-octopus-librnp: postinst script Syntax error: "fi" unexpected to be marked as done. This m

Bug#1068999: marked as done (plantuml: Fontconfig head is null, check your fonts or fonts configuration when running plantuml)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 08:49:42 + with message-id and subject line Bug#1068999: fixed in plantuml 1:1.2020.2+ds-5 has caused the Debian Bug report #1068999, regarding plantuml: Fontconfig head is null, check your fonts or fonts configuration when running plantuml to be marked as

Bug#1067918: marked as done (FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 6 has type ‘time_t’ {aka ‘long long int’})

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 07:49:29 + with message-id and subject line Bug#1067918: fixed in mmsd-tng 2.6.0-3 has caused the Debian Bug report #1067918, regarding FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 6 has type ‘time_t’ {aka ‘long long int’} to

Bug#1069685: marked as done (haskell-language-c-quote: Missing build dependency on alex)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 07:27:12 + with message-id and subject line Bug#1069685: fixed in haskell-language-c-quote 0.13.0.1-2 has caused the Debian Bug report #1069685, regarding haskell-language-c-quote: Missing build dependency on alex to be marked as done. This means that you c

Bug#1069554: marked as done (winff: FTBFS on armel: build-dependency not installable: libreoffice-draw-nogui)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 07:27:37 + with message-id and subject line Bug#1069554: fixed in winff 1.6.4+dfsg-1 has caused the Debian Bug report #1069554, regarding winff: FTBFS on armel: build-dependency not installable: libreoffice-draw-nogui to be marked as done. This means that

Bug#1069642: linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20

2024-04-23 Thread Bastian Blank
Control: reassign -1 src:linux Control: severity -1 normal Control: tags -1 moreinfo On Mon, Apr 22, 2024 at 09:12:59AM +0200, bouv...@buxtehude.debian.org wrote: > Something seems wrong in 6.1.0-20, but it is not immediately wrong: it waits > until some sort of trigger. After that, rebooting over

Processed: Re: Bug#1069642: linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20

2024-04-23 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:linux Bug #1069642 [linux-image-6.1.0-20-amd64] linux-image-6.1.0-20-amd64: kernel panic after 2024-04-20 Bug reassigned from package 'linux-image-6.1.0-20-amd64' to 'src:linux'. Ignoring request to alter found versions of bug #1069642 to the same va

Bug#1033127: marked as done (odr-padenc: Exclude this package from the future bookworm release)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 08:57:21 +0200 with message-id and subject line Re: ITP: odr-audioenc -- DAB and DAB+ audio encoder that integrates into the ODR-mmbTools has caused the Debian Bug report #1033127, regarding odr-padenc: Exclude this package from the future bookworm release to b

Bug#1033126: marked as done (odr-dabmux: Exclude this package from the future bookworm release)

2024-04-23 Thread Debian Bug Tracking System
Your message dated Tue, 23 Apr 2024 08:57:21 +0200 with message-id and subject line Re: ITP: odr-audioenc -- DAB and DAB+ audio encoder that integrates into the ODR-mmbTools has caused the Debian Bug report #1033126, regarding odr-dabmux: Exclude this package from the future bookworm release to b