Bug#1068900: elpa-magit-forge: Missing versioned dependency on elpa-transient

2024-04-12 Thread Arto Jantunen
Package: elpa-magit-forge Version: 0.3.2+git20231227.1.299bbaa-1 Severity: serious Justification: Policy 3.5 Upgrading to the new snapshot of magit-forge on testing results in the following: install/magit-forge-0.3.2.50snapshot: Handling install of emacsen flavor emacs install/magit-forge-0.3.2.5

Bug#1068431: rakarrack dependencies unsatisfiable on 32-bit non-i386 architectures.

2024-04-12 Thread Steve Langasek
Package: rakarrack Followup-For: Bug #1068431 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Please find attached a patch for this issue which has been uploaded to Ubuntu. -- Steve Langasek Give me a lever long enough and a

Processed: Re: rakarrack dependencies unsatisfiable on 32-bit non-i386 architectures.

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1068431 [rakarrack] rakarrack dependencies unsatisfiable on 32-bit non-i386 architectures. Added tag(s) patch. -- 1068431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068431 Debian Bug Tracking System Contact ow...@bugs.debian.org with pr

Bug#1013395: marked as done (mpdecimal: FTBFS with Sphinx 5.0, docutils 0.18: make[1]: *** [debian/rules:60: override_dh_sphinxdoc] Error 255)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 01:53:33 + with message-id and subject line Bug#1056785: Removed package(s) from unstable has caused the Debian Bug report #1013395, regarding mpdecimal: FTBFS with Sphinx 5.0, docutils 0.18: make[1]: *** [debian/rules:60: override_dh_sphinxdoc] Error 255 t

Processed: Re: FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’}

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1067623 [src:acm] FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’} Added tag(s) patch. -- 1067623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067623 Debian Bug Tra

Bug#1067623: FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’}

2024-04-12 Thread Steve Langasek
Package: acm Followup-For: Bug #1067623 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Please find attached a patch for this issue which has been uploaded to Ubuntu. -- Steve Langasek Give me a lever long enough and a Free

Bug#1066612: marked as done (prctl: FTBFS: prctl.c:82:31: error: implicit declaration of function ‘prctl’ [-Werror=implicit-function-declaration])

2024-04-12 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 00:36:02 + with message-id and subject line Bug#1066612: fixed in prctl 1.6-2 has caused the Debian Bug report #1066612, regarding prctl: FTBFS: prctl.c:82:31: error: implicit declaration of function ‘prctl’ [-Werror=implicit-function-declaration] to be mar

Processed: Re: kraptor: FTBFS: src/main.c:57:5: error: implicit declaration of function ‘mkdir’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1066315 [src:kraptor] kraptor: FTBFS: src/main.c:57:5: error: implicit declaration of function ‘mkdir’ [-Werror=implicit-function-declaration] Added tag(s) patch. -- 1066315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066315 Debian Bug T

Bug#1066315: kraptor: FTBFS: src/main.c:57:5: error: implicit declaration of function ‘mkdir’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Steve Langasek
Package: kraptor Followup-For: Bug #1066315 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Please find attached a patch for this issue which has been uploaded to Ubuntu. -- Steve Langasek Give me a lever long enough and a F

Bug#1066434: marked as done (uucp: FTBFS: ../uucp.h:103:3: error: #error ANSI C compiler without void or unsigned char or prototypes)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 23:21:26 + with message-id and subject line Bug#1066434: fixed in uucp 1.07-29 has caused the Debian Bug report #1066434, regarding uucp: FTBFS: ../uucp.h:103:3: error: #error ANSI C compiler without void or unsigned char or prototypes to be marked as done.

Bug#1066629: ucspi-tcp: FTBFS: tcpserver.c:143:29: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Peter Pentchev
On Fri, Apr 12, 2024 at 02:56:02PM -0600, Zixing Liu wrote: > Package: ucspi-tcp > Followup-For: Bug #1066629 > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu noble ubuntu-patch > Control: tags -1 patch > > Dear Maintainer, > > In Ubuntu, the attached patch was applied to achieve t

Bug#1068586: marked as done (ghc: Broken on arm{el,hf} because of time_t transition)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 22:35:18 + with message-id and subject line Bug#1068586: fixed in ghc 9.4.7-5 has caused the Debian Bug report #1068586, regarding ghc: Broken on arm{el,hf} because of time_t transition to be marked as done. This means that you claim that the problem has be

Bug#1066483: scrollz: FTBFS: configure: error: Fatal: You must get working getaddrinfo() function.

2024-04-12 Thread Zixing Liu
Package: scrollz Followup-For: Bug #1066483 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/patches/gcc13.patch: Fix build with GCC 13 and add mis

Processed: Re: scrollz: FTBFS: configure: error: Fatal: You must get working getaddrinfo() function.

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1066483 [src:scrollz] scrollz: FTBFS: configure: error: Fatal: You must get working getaddrinfo() function. Added tag(s) patch. -- 1066483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066483 Debian Bug Tracking System Contact ow...@bugs.d

Bug#1068880: marked as done (fwbuilder FTBFS: error: debhelper compat level specified both in debian/compat and in debian/control)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 22:19:20 + with message-id and subject line Bug#1068880: fixed in fwbuilder 5.3.7-8 has caused the Debian Bug report #1068880, regarding fwbuilder FTBFS: error: debhelper compat level specified both in debian/compat and in debian/control to be marked as don

Bug#1064061: CVE-2023-52160

2024-04-12 Thread Bastien Roucariès
control: tags -1 + patch Hi, You will find a merge request for fixing CVE-2023-52160 https://salsa.debian.org/debian/wpa/-/merge_requests/15 I can do a NMU if neeeded Bastien signature.asc Description: This is a digitally signed message part.

Processed: CVE-2023-52160

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1064061 [src:wpa] wpa: CVE-2023-52160 Added tag(s) patch. -- 1064061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064061 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: samhain: FTBFS: x_sh_prelude.c:840:42: error: implicit declaration of function ‘isblank’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1066529 [src:samhain] samhain: FTBFS: x_sh_prelude.c:840:42: error: implicit declaration of function ‘isblank’ [-Werror=implicit-function-declaration] Added tag(s) patch. -- 1066529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066529 Deb

Bug#1066529: samhain: FTBFS: x_sh_prelude.c:840:42: error: implicit declaration of function ‘isblank’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Zixing Liu
Package: samhain Followup-For: Bug #1066529 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/patches/gcc13.patch: Add missing includes and use va_c

Bug#1068887: ucommon: FTBFS on i386 after package hijack

2024-04-12 Thread Bastian Germann
Source: ucommon Version: 7.0.1-0.3 X-Debbugs-Cc: vor...@debian.org Severity: serious Hi Steve, with your last ucommon NMU you have fixed the armel/armhf builds but you have introduced a symbol-based FTBFS on i386: https://buildd.debian.org/status/fetch.php?pkg=ucommon&arch=i386&ver=7.0.1-0.3&st

Processed: tagging 1061519

2024-04-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1061519 + fixed-upstream Bug #1061519 [src:shim] shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 CVE-2023-40549 CVE-2023-40550 CVE-2023-40551 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need a

Bug#1066629: ucspi-tcp: FTBFS: tcpserver.c:143:29: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Zixing Liu
Package: ucspi-tcp Followup-For: Bug #1066629 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * debian/patches/0006-implicit-declarations.patch: Add missin

Processed: Re: ucspi-tcp: FTBFS: tcpserver.c:143:29: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1066629 [src:ucspi-tcp] ucspi-tcp: FTBFS: tcpserver.c:143:29: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration] Added tag(s) patch. -- 1066629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066629 Deb

Bug#1064560: marked as done (ucommon: FTBFS on armel and armhf: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 22:46:23 +0200 with message-id <11882ebd-7357-4e46-887d-e08bc8001...@debian.org> and subject line Re: ucommon: FTBFS on armel and armhf: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below has caused the Debian

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

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 20:42:02 + with message-id and subject line Bug#1058396: fixed in pdudaemon 0.0.8.109.gaa25f15-1 has caused the Debian Bug report #1058396, regarding pdudaemon: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" retur

Bug#1068812: marked as done (pcb-rnd: hardcoded librnd4 dependency)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 19:22:18 + with message-id and subject line Bug#1068812: fixed in pcb-rnd 3.1.4-2 has caused the Debian Bug report #1068812, regarding pcb-rnd: hardcoded librnd4 dependency to be marked as done. This means that you claim that the problem has been dealt with

Bug#1068869: mu4e: Cannot open load file: No such file or directory, mu4e

2024-04-12 Thread Jeremy Sowden
On 2024-04-12, at 10:58:59 -0700, Xiyue Deng wrote: > Jeremy Sowden writes: > > Control: tags -1 confirmed > > > > On 2024-04-12, at 16:56:25 +0200, Clément Calmels wrote: > >> Package: mu4e > >> Version: 1.12.3-2 > >> Severity: grave > >> Justification: renders package unusable > >> > >> Dear Ma

Bug#1068811: marked as done (camv-rnd: hardcoded librnd4 dependency)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 19:04:42 + with message-id and subject line Bug#1068811: fixed in camv-rnd 1.1.4-3 has caused the Debian Bug report #1068811, regarding camv-rnd: hardcoded librnd4 dependency to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1068810: marked as done (sch-rnd: hardcoded librnd4 dependency)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 19:05:38 + with message-id and subject line Bug#1068810: fixed in sch-rnd 1.0.5-2 has caused the Debian Bug report #1068810, regarding sch-rnd: hardcoded librnd4 dependency to be marked as done. This means that you claim that the problem has been dealt with

Bug#1066243: marked as done (bristol: FTBFS: bristolmemorymoog.c:280:25: error: implicit declaration of function ‘doPitchWheel’ [-Werror=implicit-function-declaration])

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 19:04:31 + with message-id and subject line Bug#1066243: fixed in bristol 0.60.11-5 has caused the Debian Bug report #1066243, regarding bristol: FTBFS: bristolmemorymoog.c:280:25: error: implicit declaration of function ‘doPitchWheel’ [-Werror=implicit-fun

Bug#1066223: marked as done (ftpcopy: FTBFS: conftest1663576.c:7:9: error: implicit declaration of function ‘_exit’ [-Werror=implicit-function-declaration])

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 18:49:07 + with message-id and subject line Bug#1066223: fixed in ftpcopy 0.6.7-7 has caused the Debian Bug report #1066223, regarding ftpcopy: FTBFS: conftest1663576.c:7:9: error: implicit declaration of function ‘_exit’ [-Werror=implicit-function-declarat

Bug#1068810: [Pkg-electronics-devel] Bug#1068810:

2024-04-12 Thread Bdale Garbee
Gianfranco Costamagna writes: > yes, but the library was renamed in librnd4t64, so either you need to > depend on the new one, or drop it, to let the auto decrufter finish > the time64_t transition and decruft it. Ah, thank you, that's a useful observation. Since the relevant version hasn't mad

Bug#1068880: fwbuilder FTBFS: error: debhelper compat level specified both in debian/compat and in debian/control

2024-04-12 Thread Adrian Bunk
Source: fwbuilder Version: 5.3.7-7 Severity: serious Tags: ftbfs X-Debbugs-Cc: Jeremy Bícha https://buildd.debian.org/status/logs.php?pkg=fwbuilder&ver=5.3.7-7 ... fakeroot debian/rules clean dh clean dh: warning: Please specify the debhelper compat level exactly once. dh: warning: * debian/co

Bug#1068869: mu4e: Cannot open load file: No such file or directory, mu4e

2024-04-12 Thread Xiyue Deng
Jeremy Sowden writes: > Control: tags -1 confirmed > > On 2024-04-12, at 16:56:25 +0200, Clément Calmels wrote: >> Package: mu4e >> Version: 1.12.3-2 >> Severity: grave >> Justification: renders package unusable >> >> Dear Maintainer, >> >> I upgraded my Sid machine with the latest mu4e and mai

Bug#1068134: marked as done (globus-gram-job-manager-scripts: arch:all package depends on pre-t64 library)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 19:39:29 +0200 with message-id <5225a1ac62a59534fe684972fc33ff676eb6d276.ca...@physics.uu.se> and subject line Re: Bug#1068134: globus-gram-job-manager-scripts: arch:all package depends on pre-t64 library has caused the Debian Bug report #1068134, regarding glob

Processed: Also set fixed...

2024-04-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1068133 5.1-3 Bug #1068133 {Done: Mattias Ellert } [src:globus-gram-audit] globus-gram-audit: arch:all package depends on pre-t64 library Marked as fixed in versions globus-gram-audit/5.1-3. > fixed 1068134 7.3-2 Bug #1068134 [src:globus-g

Bug#1068133: marked as done (globus-gram-audit: arch:all package depends on pre-t64 library)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 19:09:48 +0200 with message-id <23bcc6fd0dcd734d36e68aee94a4bf6e3f00.ca...@physics.uu.se> and subject line Re: Bug#1068133: globus-gram-audit: arch:all package depends on pre-t64 library has caused the Debian Bug report #1068133, regarding globus-gram-audit:

Bug#1068754: marked as done (circe: FTBFS: failing tests)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 10:09:41 -0700 with message-id <87v84mbj8q@debian-hx90.lan> and subject line Re: Bug#1068754: circe: FTBFS: failing tests has caused the Debian Bug report #1068754, regarding circe: FTBFS: failing tests to be marked as done. This means that you claim that th

Processed: Re: Bug#1068134: globus-gram-job-manager-scripts: arch:all package depends on pre-t64 library

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > found 1068134 7.3-1 Bug #1068134 [src:globus-gram-job-manager-scripts] globus-gram-job-manager-scripts: arch:all package depends on pre-t64 library Marked as found in versions globus-gram-job-manager-scripts/7.3-1. > notfound 1068134 7.3-2 Bug #1068134 [src:globus-g

Bug#1068134: globus-gram-job-manager-scripts: arch:all package depends on pre-t64 library

2024-04-12 Thread Mattias Ellert
Control: found 1068134 7.3-1 Control: notfound 1068134 7.3-2 The bug reported here is already fixed in the version for which the bug was reported. This bug was present in the previous version. The current version was uploaded precisely to fix the problem reported. Previous version (7.3-1) had D

Processed: Re: Bug#1068133: globus-gram-audit: arch:all package depends on pre-t64 library

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > found 1068133 5.1-2 Bug #1068133 [src:globus-gram-audit] globus-gram-audit: arch:all package depends on pre-t64 library Marked as found in versions globus-gram-audit/5.1-2. > notfound 1068133 5.1-3 Bug #1068133 [src:globus-gram-audit] globus-gram-audit: arch:all pac

Bug#1068133: globus-gram-audit: arch:all package depends on pre-t64 library

2024-04-12 Thread Mattias Ellert
Control: found 1068133 5.1-2 Control: notfound 1068133 5.1-3 The bug reported here is already fixed in the version for which the bug was reported. This bug was present in the previous version. The current version was uploaded precisely to fix the problem reported. Previous version (5.1-2) had D

Bug#1068757: marked as pending in python-musicpd

2024-04-12 Thread Geoffroy Youri Berret
Control: tag -1 pending Hello, Bug #1068757 in python-musicpd 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-musicpd/-/commit/a9aca

Processed: Bug#1068757 marked as pending in python-musicpd

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1068757 [src:python-musicpd] python-musicpd: FTBFS: dh_installchangelogs: error: could not find changelog Added tag(s) pending. -- 1068757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068757 Debian Bug Tracking System Contact ow...@bugs.

Bug#1066238: marked as done (dvbackup: FTBFS: dvconnect.c:264:33: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration])

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 16:49:02 + with message-id and subject line Bug#1066238: fixed in dvbackup 1:0.0.4-10 has caused the Debian Bug report #1066238, regarding dvbackup: FTBFS: dvconnect.c:264:33: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-decla

Bug#1066626: marked as done (lua-svn: FTBFS: src/luasvn.c:1306:13: error: implicit declaration of function ‘svn_prop_needs_translation’ [-Werror=implicit-function-declaration])

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 16:25:45 + with message-id and subject line Bug#1066626: fixed in lua-svn 0.4.0-11 has caused the Debian Bug report #1066626, regarding lua-svn: FTBFS: src/luasvn.c:1306:13: error: implicit declaration of function ‘svn_prop_needs_translation’ [-Werror=impli

Processed: Re: Bug#1068869: mu4e: Cannot open load file: No such file or directory, mu4e

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 confirmed Bug #1068869 [mu4e] mu4e: Cannot open load file: No such file or directory, mu4e Added tag(s) confirmed. -- 1068869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1068869: mu4e: Cannot open load file: No such file or directory, mu4e

2024-04-12 Thread Jeremy Sowden
Control: tags -1 confirmed On 2024-04-12, at 16:56:25 +0200, Clément Calmels wrote: > Package: mu4e > Version: 1.12.3-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I upgraded my Sid machine with the latest mu4e and maildir-utils > packages : 1.12.3-2. Ema

Bug#1049951: marked as done (fwbuilder: maintained by ubuntu-devel-disc...@lists.ubuntu.com)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 15:19:24 + with message-id and subject line Bug#1049951: fixed in fwbuilder 5.3.7-7 has caused the Debian Bug report #1049951, regarding fwbuilder: maintained by ubuntu-devel-disc...@lists.ubuntu.com to be marked as done. This means that you claim that the

Bug#1068869: mu4e: Cannot open load file: No such file or directory, mu4e

2024-04-12 Thread Clément Calmels
Package: mu4e Version: 1.12.3-2 Severity: grave Justification: renders package unusable Dear Maintainer, I upgraded my Sid machine with the latest mu4e and maildir-utils packages : 1.12.3-2. Emacs isn't able to find the mu4e command anymore. From *Messages*: "Cannot open load file: No such file o

Processed: Re: xrdp: after bullseye-security upgrade, empty turquoise screen after logging in

2024-04-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1052197 xorgxrdp Bug #1052197 {Done: Gürkan Myczko } [xrdp] xrdp: after bullseye-security upgrade, empty turquoise screen after logging in Bug reassigned from package 'xrdp' to 'xorgxrdp'. No longer marked as found in versions xrdp/0.9.2

Bug#1052197: xrdp: after bullseye-security upgrade, empty turquoise screen after logging in

2024-04-12 Thread Thorsten Glaser
reassign 1052197 xorgxrdp affects 1052197 xrdp found 1052197 1:0.2.12-1 fixed 1052197 1:0.2.12-1+deb11u1 fixed 1052197 1:0.9.19-1 thanks Gürkan Myczko dixit: > This bug has been closed upstream, and upstream packages have been in > the archive for a while. No, the bug has been fixed by binNMUing

Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

2024-04-12 Thread Guilhem Moulin
On Fri, 12 Apr 2024 at 14:37:16 +0200, Guilhem Moulin wrote: > What is that “GUI” view? src:cryptsetup doesn't provide that, I wonder > if it might be what needs libphtread. FWIW, I later noticed you used a splash screen (plymouth) and thought it might be because of that, but I still cannot repro

Bug#1067234: symfit: autopkgtest regression with NumPy 1.26

2024-04-12 Thread Michael R. Crusoe
On Mon, 8 Apr 2024 17:09:33 + Graham Inggs wrote: > Control: tags -1 + patch > > Hi Maintainer > > While asserting that no warnings are raised is a useful test for the > upstream developers, I don't think it makes sense for downstreams. > > I propose to disable the assertion as follows: > > -

Processed: Re: Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + unreproducible moreinfo Bug #1068849 [cryptsetup-initramfs] cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1 Bug #1068848 [cryptsetup-initramfs] cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1 Added tag(s) unrepro

Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

2024-04-12 Thread Guilhem Moulin
Control: tag -1 + unreproducible moreinfo On Fri, 12 Apr 2024 at 12:45:09 +0200, Milan Broz wrote: > Just FYI (for upstream code): if cryptsetup/libcryptsetup is linked with > OpenSSL >= 3.2, > it does not need libphtread (as threads are implemented in OpenSSL for Argon2 > internally). Thanks f

Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

2024-04-12 Thread Jan Katins
On Fri, 12 Apr 2024 at 14:00, Chris Hofstaedtler wrote: > Can you tell us which part was wanting libgcc_s.so.1? > cryptsetup in the initramfs doesn't seem to be the (original) > problem of that. How would I find out? (I've never debugged such a problem, and have basically no clue what is happenin

Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

2024-04-12 Thread Chris Hofstaedtler
On Fri, Apr 12, 2024 at 09:11:51AM +0200, Jan Katins wrote: > Package: cryptsetup > Version: 2:2.7.2-1 > Severity: normal > > Dear Maintainer, > > After a recent apt upgrade on a debian sid system (installed about 3 > years ago with an installer, choosing to encrypt the filesystem, no > idea what

Processed: Re: dolfinx-mpc: NMU diff for 64-bit time_t transition

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > severity 1062383 important Bug #1062383 [src:dolfinx-mpc] dolfinx-mpc: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > tags 1062383 moreinfo Bug #1062383 [src:dolfinx-mpc] dolfinx-mpc: NMU diff for 64-bit time_t transition Added t

Bug#1062383: dolfinx-mpc: NMU diff for 64-bit time_t transition

2024-04-12 Thread Drew Parsons
Source: dolfinx-mpc Followup-For: Bug #1062383 Control: severity 1062383 important Control: tags 1062383 moreinfo This patch was never applied. Do we not need it after all? Can we close this bug now?

Bug#1067233: marked as done (python-pomegranate: autopkgtest regression with NumPy 1.26)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 11:21:17 + with message-id and subject line Bug#1067294: fixed in python-pomegranate 0.14.8-5 has caused the Debian Bug report #1067294, regarding python-pomegranate: autopkgtest regression with NumPy 1.26 to be marked as done. This means that you claim tha

Bug#1067233: marked as done (python-pomegranate: autopkgtest regression with NumPy 1.26)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 11:21:17 + with message-id and subject line Bug#1067233: fixed in python-pomegranate 0.14.8-5 has caused the Debian Bug report #1067233, regarding python-pomegranate: autopkgtest regression with NumPy 1.26 to be marked as done. This means that you claim tha

Bug#1066854: marked as done (don't hard-code the name of the shared library)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 11:21:24 + with message-id and subject line Bug#1066854: fixed in ruby-magic 0.2.9-4 has caused the Debian Bug report #1066854, regarding don't hard-code the name of the shared library to be marked as done. This means that you claim that the problem has bee

Bug#1067294: marked as pending in python-pomegranate

2024-04-12 Thread Michael R. Crusoe
Control: tag -1 pending Hello, Bug #1067294 in python-pomegranate 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-pomegranate/-/comm

Processed: Bug#1067294 marked as pending in python-pomegranate

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1067294 [src:python-pomegranate] python-pomegranate: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 Bug #1067233 [src:python-pomegranate] python-pomegranate: autopkgtest regressi

Processed: Bug#1067233 marked as pending in python-pomegranate

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1067233 [src:python-pomegranate] python-pomegranate: autopkgtest regression with NumPy 1.26 Bug #1067294 [src:python-pomegranate] python-pomegranate: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" retu

Bug#1067233: marked as pending in python-pomegranate

2024-04-12 Thread Michael R. Crusoe
Control: tag -1 pending Hello, Bug #1067233 in python-pomegranate 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-pomegranate/-/comm

Bug#1066854: marked as pending in ruby-magic

2024-04-12 Thread Antonio Terceiro
Control: tag -1 pending Hello, Bug #1066854 in ruby-magic 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/ruby-team/ruby-magic/-/commit/3a95d42fa6ea9355487927f2

Processed: Bug#1066854 marked as pending in ruby-magic

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1066854 [src:ruby-magic] don't hard-code the name of the shared library Added tag(s) pending. -- 1066854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: fenics-dolfinx: NMU diff for 64-bit time_t transition

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > severity 1062587 important Bug #1062587 [src:fenics-dolfinx] fenics-dolfinx: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > tags 1062587 moreinfo Bug #1062587 [src:fenics-dolfinx] fenics-dolfinx: NMU diff for 64-bit time_t transi

Bug#1062587: fenics-dolfinx: NMU diff for 64-bit time_t transition

2024-04-12 Thread Drew Parsons
Source: fenics-dolfinx Followup-For: Bug #1062587 Control: severity 1062587 important Control: tags 1062587 moreinfo This time_t patch was never applied. I presume it's not needed after all and we can close this bug now?

Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

2024-04-12 Thread Milan Broz
On 4/12/24 9:11 AM, Jan Katins wrote: I snooped around in the source code a bit and found that libgcc_s seems to be dlopened and is special cased: https://salsa.debian.org/kernel-team/initramfs-tools/-/blob/master/hook-functions?ref_type=heads#L248-249 (original bugreport: https://bugs.debian.org

Processed: Re: ftpcopy: FTBFS: conftest1663576.c:7:9: error: implicit declaration of function ‘_exit’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1066223 [src:ftpcopy] ftpcopy: FTBFS: conftest1663576.c:7:9: error: implicit declaration of function ‘_exit’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066223 Deb

Bug#1066223: ftpcopy: FTBFS: conftest1663576.c:7:9: error: implicit declaration of function ‘_exit’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Andreas Beckmann
Followup-For: Bug #1066223 X-Debbugs-Cc: Bastian Germann Control: tag -1 pending Hi Bastian, I've fixed the remaining implicit function declarations and related bugs in GIT. Do you want to take it from here again? We should probably fix the nonverbose build in this very special build system, too

Processed: Re: Bug#1064531: src:amberol: unsatisfied build dependency in testing: librust-lofty-0.17-dev

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1064531 [src:amberol] src:amberol: unsatisfied build dependency in testing: librust-lofty-0.17-dev Added tag(s) patch. -- 1064531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064531 Debian Bug Tracking System Contact ow...@bugs.debian.o

Bug#1064531: src:amberol: unsatisfied build dependency in testing: librust-lofty-0.17-dev

2024-04-12 Thread Emanuele Rocca
Control: tags -1 + patch Hi, On 2024-02-23 08:33, Paul Gevers wrote: > Dose [1] is reporting a build issue with your package, it's missing a > build dependency. It's actually two build deps that are missing: librust-lofty-0.17-dev and librust-mpris-server-0.6-dev. Setting both to the versions cu

Bug#1066275:

2024-04-12 Thread Miriam Espana Acebal
Hi, In ubuntu we applied the upstream's fix at https://github.com/rlancaste/stellarsolver/pull/139. I adapted it to a patch that I attach here for fixing this FTBFS. I am sending this for your consideration, and I hope it helps. Best, Miriam -- [image: Canonical-20th-anniversary] Miriam Espa

Bug#1066213:

2024-04-12 Thread Miriam Espana Acebal
Hi, In ubuntu we applied the upstream's fix at https://github.com/jedsoft/slrn/pull/1 (with some refreshing action) that I'll attach here for fixing this FTBFS. I am sending this for your consideration, and I hope that it helps. Best, Miriam -- [image: Canonical-20th-anniversary] Miriam Esp

Bug#1068115: marked as done (tardy: FTBFS on arm{el,hf}: ./tardy/main.cc:282:(.text.startup+0x578): undefined reference to `tardy_mtime(long)')

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 09:51:41 + with message-id and subject line Bug#1068115: fixed in tardy 1.25-3 has caused the Debian Bug report #1068115, regarding tardy: FTBFS on arm{el,hf}: ./tardy/main.cc:282:(.text.startup+0x578): undefined reference to `tardy_mtime(long)' to be mark

Bug#1066651: marked as done (spectools: FTBFS: wispy_hw_gen1.c:296:15: error: implicit declaration of function ‘wispy24x_adler_checksum’; did you mean ‘wispy1_adler_checksum’? [-Werror=implicit-functi

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 09:51:31 + with message-id and subject line Bug#1066651: fixed in spectools 201601r1-4 has caused the Debian Bug report #1066651, regarding spectools: FTBFS: wispy_hw_gen1.c:296:15: error: implicit declaration of function ‘wispy24x_adler_checksum’; did you

Processed: Re: Bug#1068647: python-pot: autopkgtest regression on i386 with NumPy 1.26.4

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/PythonOT/POT/issues/618 Bug #1068647 [src:python-pot] python-pot: autopkgtest regression on i386 with NumPy 1.26.4 Set Bug forwarded-to-address to 'https://github.com/PythonOT/POT/issues/618'. -- 1068647: https://bugs.debian.org/cgi

Bug#1068647: python-pot: autopkgtest regression on i386 with NumPy 1.26.4

2024-04-12 Thread Gard Spreemann
Control: forwarded -1 https://github.com/PythonOT/POT/issues/618 Thanks for the bug report. This seems like a simple case of a missing floating point tolerance in upstream's test. It's easy to patch, but I've sent a reproducible example upstream [1] as they're likely to have better insight into t

Bug#1065980: marked as done (gfarm: FTBFS on arm{el,hf}:)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 08:35:08 + with message-id and subject line Bug#1065980: fixed in gfarm 2.7.20+dfsg-1.2 has caused the Debian Bug report #1065980, regarding gfarm: FTBFS on arm{el,hf}: to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: merging 1068849 1068848, reassign 1068848 to cryptsetup-initramfs, severity of 1068848 is serious

2024-04-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1068849 1068848 Bug #1068849 [cryptsetup] cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1 Bug #1068848 [cryptsetup] cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1 Merged 1068848 1068849 > reassi

Processed: Re: Bug#1067957: [[maude-bugs]] [EXTERNAL] Re: Maude fails to build on armhf

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > severity -1 wishlist Bug #1067957 [src:maude] FTBFS: error: call of overloaded ‘__gmp_expr(__time64_t&)’ is ambiguous Severity set to 'wishlist' from 'serious' -- 1067957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067957 Debian Bug Tracking System Contact

Bug#1067957: [[maude-bugs]] [EXTERNAL] Re: Maude fails to build on armhf

2024-04-12 Thread Nilesh Patra
Control: severity -1 wishlist Hi, maude has been -rm'ed on 32-bit archs as per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068766 So this issue is now moot and I am downgrading the severity. On Thu, Apr 11, 2024 at 07:53:08AM +0200, Andreas Tille wrote: > Hi, > > Am Wed, Apr 10, 2024 at

Bug#1065980: gfarm: diff for NMU version 2.7.20+dfsg-1.2

2024-04-12 Thread Sebastian Ramacher
Control: tags 1065980 + patch Dear maintainer, I've prepared an NMU for gfarm (versioned as 2.7.20+dfsg-1.2). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru gfarm-2.7.20+dfsg/debian/changelog gfarm-2.7.20+dfsg/debian/changelog --- gfarm-2.7.20+dfsg/debian/changelo

Processed: gfarm: diff for NMU version 2.7.20+dfsg-1.2

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tags 1065980 + patch Bug #1065980 [src:gfarm] gfarm: FTBFS on arm{el,hf}: Ignoring request to alter tags of bug #1065980 to the same tags previously set -- 1065980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065980 Debian Bug Tracking System Contact ow...@b

Bug#1065778: marked as done (libcdio: FTBFS on arm{el,hf}: _cdio_stdio.c:53:20: error: implicit declaration of function ‘fseeko64’; did you mean ‘fseeko’? [-Werror=implicit-function-declaration])

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 07:34:10 + with message-id and subject line Bug#1065778: fixed in libcdio 2.1.0-4.2 has caused the Debian Bug report #1065778, regarding libcdio: FTBFS on arm{el,hf}: _cdio_stdio.c:53:20: error: implicit declaration of function ‘fseeko64’; did you mean ‘fse

Processed (with 1 error): reopening also camv-rnd

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1068811 {Done: Bdale Garbee } [camv-rnd] camv-rnd: hardcoded librnd4 dependency '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 reopened No longer marked

Bug#1068811: reopening also camv-rnd

2024-04-12 Thread Gianfranco Costamagna
control: reopen -1 control: notifxed -1 1.1.4-2 control: severity -1 serious there is one left... Package: camv-rnd-export-vector Architecture: any -Depends: ${misc:Depends}, ${shlibs:Depends}, camv-rnd-core (= ${binary:Version}), librnd4 +Depends: ${misc:Depends}, ${shlibs:Depends}, camv-rnd

Processed: libcdio: diff for NMU version 2.1.0-4.2

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > tags 1065778 + patch Bug #1065778 [src:libcdio] libcdio: FTBFS on arm{el,hf}: _cdio_stdio.c:53:20: error: implicit declaration of function ‘fseeko64’; did you mean ‘fseeko’? [-Werror=implicit-function-declaration] Ignoring request to alter tags of bug #1065778 to t

Bug#1065778: libcdio: diff for NMU version 2.1.0-4.2

2024-04-12 Thread Sebastian Ramacher
Control: tags 1065778 + patch Dear maintainer, I've prepared an NMU for libcdio (versioned as 2.1.0-4.2). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru libcdio-2.1.0/debian/changelog libcdio-2.1.0/debian/changelog --- libcdio-2.1.0/debian/changelog 2024-02-29 11:3

Processed: Re:

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1068810 {Done: Bdale Garbee } [sch-rnd] sch-rnd: hardcoded librnd4 dependency Bug reopened Ignoring request to alter fixed versions of bug #1068810 to the same values previously set > severity -1 serious Bug #1068810 [sch-rnd] sch-rnd: hardcoded libr

Processed: Re:

2024-04-12 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1068812 [pcb-rnd] pcb-rnd: hardcoded librnd4 dependency Bug 1068812 is not marked as done; doing nothing. > severity -1 serious Bug #1068812 [pcb-rnd] pcb-rnd: hardcoded librnd4 dependency Severity set to 'serious' from 'minor' -- 1068812: https://bu

Bug#1068810:

2024-04-12 Thread Gianfranco Costamagna
control: reopen -1 control: severity -1 serious On Thu, 11 Apr 2024 13:17:44 -0600 Bdale Garbee wrote: The librnd4 runtime dependency is needed to ensure at least a minimum version of that library is available so required capability is present. The "hard coded" dependency is not actually a bug,

Bug#965837: tart: Change of debhelper compat

2024-04-12 Thread Andrey Rakhmatullin
On Fri, Jan 12, 2024 at 05:12:36PM +0800, i...@0w.al wrote: > I have changed the compat version from 5 to 13 to fix the build error, and > fixed some lintian warnings Hello. As the package is orphaned, it's not very useful to send patches to its bug reports unless you want to do the upload yoursel