Bug#1066334: cython/bison issue (Was: acedb: FTBFS: acein.c:2045:15: error: implicit declaration of function ‘add_history’ [-Werror=implicit-function-declaration])

2024-04-13 Thread Andreas Tille
Hi Jeremy, Am Sat, Apr 13, 2024 at 10:46:17PM +0100 schrieb Jeremy Sowden: > > The one after this looks like a GTK problem, and that's the point at > which I bow out. Thanks a lot for your help so far. Your patches are pushed to Git. Kind regards Andreas. -- https://fam-tille.de

Bug#1068065: marked as done (RM: quorum [armhf i386 armel] -- ROM; cannot build on 32-bit archs due to missing builddeps)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2024 00:29:11 -0400 with message-id <2712742.osAmPtH0pn@zini-1880> and subject line Re: RM: quorum [armhf i386 armel] -- ROM; cannot build on 32-bit archs due to missing builddeps has caused the Debian Bug report #1068065, regarding RM: quorum [armhf i386 armel] --

Bug#1066670: marked as done (ldap2dns: FTBFS: ldap2dns.c:477:25: error: implicit declaration of function ‘ldap_search_s’; did you mean ‘ldap_search_ext’? [-Werror=implicit-function-declaration])

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2024 02:38:01 + with message-id and subject line Bug#1066670: fixed in ldap2dns 0.3.1-6 has caused the Debian Bug report #1066670, regarding ldap2dns: FTBFS: ldap2dns.c:477:25: error: implicit declaration of function ‘ldap_search_s’; did you mean

Bug#1066310: dx: FTBFS: _compparse.c:51:17: error: implicit declaration of function ‘_dxfcclex’ [-Werror=implicit-function-declaration]

2024-04-13 Thread Bo YU
Hi, On Sun, Apr 14, 2024 at 5:11 AM Graham Inggs wrote: > > Hi Bo > > > I have attached one debdiff and it can be built with it. So could you > > upload it with it? > > The attached patch just seems to be papering over the problem, so I > would rather not. I agree with that. I should add some

Bug#1068402: marked as done (lua-lxc dependencies unsatisfiable on 32-bit non-i386 architectures.)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2024 01:50:10 + with message-id and subject line Bug#1068402: fixed in lua-lxc 1:3.0.2-3 has caused the Debian Bug report #1068402, regarding lua-lxc dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as done. This means that you claim

Bug#1068937: marked as done (python3-lxc: hard-coded dependency on liblcx1)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sun, 14 Apr 2024 01:51:33 + with message-id and subject line Bug#1068937: fixed in python3-lxc 1:5.0.0-2 has caused the Debian Bug report #1068937, regarding python3-lxc: hard-coded dependency on liblcx1 to be marked as done. This means that you claim that the problem has

Bug#1066342: eterm: FTBFS: libscream.c:3231:16: error: implicit declaration of function ‘safe_print_string’ [-Werror=implicit-function-declaration]

2024-04-13 Thread Steve Langasek
Package: eterm Followup-For: Bug #1066342 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: eterm: FTBFS: libscream.c:3231:16: error: implicit declaration of function ‘safe_print_string’ [-Werror=implicit-function-declaration]

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1066342 [src:eterm] eterm: FTBFS: libscream.c:3231:16: error: implicit declaration of function ‘safe_print_string’ [-Werror=implicit-function-declaration] Added tag(s) patch. -- 1066342:

Bug#1068903: marked as done (elpa-magit: missing dependency on elpa-transient (>= 0.5.0))

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 23:27:04 + with message-id and subject line Bug#1068903: fixed in magit 3.3.0+git20240412.1.da14749d-1 has caused the Debian Bug report #1068903, regarding elpa-magit: missing dependency on elpa-transient (>= 0.5.0) to be marked as done. This means that

Processed: Re: mrtdreader: FTBFS: mrtdreader.c:95:41: error: implicit declaration of function ‘isprint’ [-Werror=implicit-function-declaration]

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1066260 [src:mrtdreader] mrtdreader: FTBFS: mrtdreader.c:95:41: error: implicit declaration of function ‘isprint’ [-Werror=implicit-function-declaration] Added tag(s) patch. -- 1066260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066260

Bug#1066260: mrtdreader: FTBFS: mrtdreader.c:95:41: error: implicit declaration of function ‘isprint’ [-Werror=implicit-function-declaration]

2024-04-13 Thread Michael Hudson-Doyle
Package: mrtdreader Followup-For: Bug #1066260 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: michael.hud...@ubuntu.com Control: tags -1 patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * Add #include of

Bug#1066567: marked as done (easyh10: FTBFS: ucs2char_iconv.c:319:25: error: implicit declaration of function ‘close’; did you mean ‘pclose’? [-Werror=implicit-function-declaration])

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 22:50:31 + with message-id and subject line Bug#1066567: fixed in easyh10 1.5-6 has caused the Debian Bug report #1066567, regarding easyh10: FTBFS: ucs2char_iconv.c:319:25: error: implicit declaration of function ‘close’; did you mean ‘pclose’?

Bug#1068404: marked as done (mariadb-plugin-s3 dependencies unsatisfiable on 32-bit non-i386 architectures.)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 22:34:46 + with message-id and subject line Bug#1068404: fixed in mariadb 1:10.11.7-4 has caused the Debian Bug report #1068404, regarding mariadb-plugin-s3 dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as done. This means that

Bug#1068403: marked as done (mariadb-plugin-hashicorp-key-management dependencies unsatisfiable on 32-bit non-i386 architectures.)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 22:34:46 + with message-id and subject line Bug#1068403: fixed in mariadb 1:10.11.7-4 has caused the Debian Bug report #1068403, regarding mariadb-plugin-hashicorp-key-management dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as

Bug#1067491: marked as done (time_t transition upgrade: failed systemctl call in preinst due to missing pre-dependencies)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 22:34:46 + with message-id and subject line Bug#1067491: fixed in mariadb 1:10.11.7-4 has caused the Debian Bug report #1067491, regarding time_t transition upgrade: failed systemctl call in preinst due to missing pre-dependencies to be marked as done.

Bug#1067066: marked as done (ruby-fusefs: fusefs_fuse.c:31:10: error: implicit declaration of function ‘fuse_chan_fd’ [-Werror=implicit-function-declaration])

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 22:03:29 + with message-id and subject line Bug#1067066: fixed in ruby-fusefs 0.7.0-6 has caused the Debian Bug report #1067066, regarding ruby-fusefs: fusefs_fuse.c:31:10: error: implicit declaration of function ‘fuse_chan_fd’

Processed: RM: quorum [armhf i386 armel] -- ROM; cannot build on 32-bit archs due to missing builddeps

2024-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1068065 RM: quorum [armhf i386 armel] -- ROM; cannot build on 32-bit > archs due to missing builddeps Bug #1068065 [src:quorum] quorum: FTBFS on armel, armhf,i386 (error: no matching function for call to ‘min(const long long unsigned

Bug#1068065: RM: quorum [armhf i386 armel] -- ROM; cannot build on 32-bit archs due to missing builddeps

2024-04-13 Thread Nilesh Patra
retitle 1068065 RM: quorum [armhf i386 armel] -- ROM; cannot build on 32-bit archs due to missing builddeps reassign 1068065 ftp.debian.org user ftp.debian@packages.debian.org usertags 1068065 remove stop Hi, quorum builddeps on jellyfish which is not present on 32-bit archs any longer[1].

Processed: closing 1053839

2024-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1053839 Bug #1053839 [src:ruby-github-markup] src:ruby-github-markup: unsatisfied build dependency in testing: ruby-sanitize Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1053839:

Bug#1053839: closing 1053839

2024-04-13 Thread Cédric Boutillier
close 1053839 thanks It seems that ruby-sanitize is back to testing. All the dependencies can be satisfied there, and the package seems installable, according to the page linked in the initial bug report. I am therefore closing the bug. Cheers, Cédric

Bug#1066956: marked as done (blimps: FTBFS with -Werror=implicit-function-declaration)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 21:49:54 + with message-id and subject line Bug#1066956: fixed in blimps 3.9+ds-2 has caused the Debian Bug report #1066956, regarding blimps: FTBFS with -Werror=implicit-function-declaration to be marked as done. This means that you claim that the problem

Bug#1066334: cython/bison issue (Was: acedb: FTBFS: acein.c:2045:15: error: implicit declaration of function ‘add_history’ [-Werror=implicit-function-declaration])

2024-04-13 Thread Jeremy Sowden
On 2024-04-13, at 21:48:10 +0100, Jeremy Sowden wrote: > On 2024-04-13, at 09:31:07 +0200, Andreas Tille wrote: > > Control: tags -1 help > > thanks > > > > Hi, > > > > while I was able to fix the origininal cause of the failure I'm now blocked > > by > > some issue that cython seems to miss

Processed: Bug#1066956 marked as pending in blimps

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

Bug#1066956: marked as pending in blimps

2024-04-13 Thread Nilesh Patra
Control: tag -1 pending Hello, Bug #1066956 in blimps 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#1068433: marked as done (riseup-vpn dependencies unsatisfiable on 32-bit non-i386 architectures.)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 21:38:31 + with message-id and subject line Bug#1068433: fixed in riseup-vpn 0.21.11+ds1-5.1 has caused the Debian Bug report #1068433, regarding riseup-vpn dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as done. This means that

Bug#1067066: marked as pending in ruby-fusefs

2024-04-13 Thread Cédric Boutillier
Control: tag -1 pending Hello, Bug #1067066 in ruby-fusefs 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:

Processed: Bug#1067066 marked as pending in ruby-fusefs

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1067066 [src:ruby-fusefs] ruby-fusefs: fusefs_fuse.c:31:10: error: implicit declaration of function ‘fuse_chan_fd’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1067066:

Processed: severity of 1062558 is serious

2024-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # -3 reverted time_t changes > severity 1062558 serious Bug #1062558 [src:libosmo-netif] libosmo-netif: NMU diff for 64-bit time_t transition Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you

Bug#1067088: [Pkg-zfsonlinux-devel] Bug#1067088: zfs-linux: missing B-D: libtirpc-dev

2024-04-13 Thread Sebastian Ramacher
Hi Aron On 2024-03-18 18:29:51 +0800, Aron Xu wrote: > Control: tags -1 + pending > > On Mon, Mar 18, 2024 at 5:31 PM Andreas Beckmann wrote: > > > > > > This could be fixed by adding an explicit Build-Depends on libtirpc-dev. > > The glibc change will likely be reverted in the short term, but

Bug#1065721: simage: FTBFS: error: conflicti ng types for ‘GifQuantizeBuffer’; have ‘int(unsigned int, unsigned int, int *, GifBy teType *, GifByteType *, GifByteType *, GifByteType *, GifColo

2024-04-13 Thread Steven Robbins
Control: severity -1 normal thanks On Sat, 9 Mar 2024 13:03:05 +0100 Sebastian Ramacher wrote: > Source: simage > Version: 1.8.3+ds-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) The bug is fixed in unstable. But the

Processed: Re: simage: FTBFS: error: conflicti ng types for ‘GifQuantizeBuffer’; have ‘int(unsigned int, unsigned int, int *, GifBy teType *, GifByteType *, GifByteType *, GifByteType *, GifCo

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #1065721 {Done: Steve M. Robbins } [src:simage] simage: FTBFS: error: conflicting types for ‘GifQuantizeBuffer’; have ‘int(unsigned int, unsigned int, int *, GifByteType *, GifByteType *, GifByteType *, GifByteType *, GifColorType *)’

Bug#1068944: multipath-tools: hard-coded dependency on libaio1

2024-04-13 Thread Sebastian Ramacher
Package: multipath-tools Version: 0.9.7-6 Severity: serious X-Debbugs-Cc: sramac...@debian.org multipath-tools has a hard-coded depenency on libaio1 which is involved in the time_t transition. Note that libaio1t64 is included in ${shlib:Depends} so the hard-coded dependency can be removed.

Bug#1067567: marked as done (dhcp-probe: [time_t] Remove hardcoded dependencies on libpcap0.8, libnet, shlibs takes care of them)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 21:20:34 + with message-id and subject line Bug#1067567: fixed in dhcp-probe 1.3.0-10.2 has caused the Debian Bug report #1067567, regarding dhcp-probe: [time_t] Remove hardcoded dependencies on libpcap0.8, libnet, shlibs takes care of them to be marked as

Bug#1066292: marked as done (createrepo-c: FTBFS: xml_file.c:338:36: error: implicit declaration of function ‘rasprintf’; did you mean ‘g_sprintf’? [-Werror=implicit-function-declaration])

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 21:20:27 + with message-id and subject line Bug#1066292: fixed in createrepo-c 0.17.3-3 has caused the Debian Bug report #1066292, regarding createrepo-c: FTBFS: xml_file.c:338:36: error: implicit declaration of function ‘rasprintf’; did you mean

Bug#1068221: marked as done (comet-ms, dependencies unsatisfiable on 32-bit non-i386 architectures.)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 21:20:09 + with message-id and subject line Bug#1068221: fixed in comet-ms 2019015+cleaned1-4.1 has caused the Debian Bug report #1068221, regarding comet-ms, dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as done. This means

Bug#1068219: marked as done (chatty, dependencies unsatisfiable on 32-bit non-i386 architectures.)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 21:19:37 + with message-id and subject line Bug#1068219: fixed in chatty 0.8.2-1.1 has caused the Debian Bug report #1068219, regarding chatty, dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as done. This means that you claim

Bug#1067174: marked as done (cpupower-gui: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 21:20:17 + with message-id and subject line Bug#1067174: fixed in cpupower-gui 0.7.2-2.2 has caused the Debian Bug report #1067174, regarding cpupower-gui: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf to be marked as done.

Processed: found 1065633 in 2.6.7+dfsg-1~exp1

2024-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1065633 2.6.7+dfsg-1~exp1 Bug #1065633 {Done: Ryan Tandy } [src:openldap] openldap: FTBFS on hppa - implicit declaration of function ‘kadm5_s_init_with_password_ctx’ Marked as found in versions openldap/2.6.7+dfsg-1~exp1 and reopened. >

Bug#1066310: dx: FTBFS: _compparse.c:51:17: error: implicit declaration of function ‘_dxfcclex’ [-Werror=implicit-function-declaration]

2024-04-13 Thread Graham Inggs
Hi Bo > I have attached one debdiff and it can be built with it. So could you > upload it with it? The attached patch just seems to be papering over the problem, so I would rather not. Regards Graham

Bug#1068219: chatty: diff for NMU version 0.8.2-1.1

2024-04-13 Thread Sebastian Ramacher
Dear maintainer, I've prepared an NMU for chatty (versioned as 0.8.2-1.1). The diff is attached to this message. Regards. -- Sebastian Ramacher diff -Nru chatty-0.8.2/debian/changelog chatty-0.8.2/debian/changelog --- chatty-0.8.2/debian/changelog 2024-03-18 03:21:04.0 +0100 +++

Processed: riseup-vpn: diff for NMU version 0.21.11+ds1-5.1

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tags 1068433 + patch Bug #1068433 [riseup-vpn] riseup-vpn dependencies unsatisfiable on 32-bit non-i386 architectures. Added tag(s) patch. -- 1068433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068433 Debian Bug Tracking System Contact

Bug#1066334: cython/bison issue (Was: acedb: FTBFS: acein.c:2045:15: error: implicit declaration of function ‘add_history’ [-Werror=implicit-function-declaration])

2024-04-13 Thread Jeremy Sowden
On 2024-04-13, at 09:31:07 +0200, Andreas Tille wrote: > Control: tags -1 help > thanks > > Hi, > > while I was able to fix the origininal cause of the failure I'm now blocked by > some issue that cython seems to miss adding some >#include > but I have no idea how to accomplish this. The

Bug#1068433: riseup-vpn: diff for NMU version 0.21.11+ds1-5.1

2024-04-13 Thread Sebastian Ramacher
Control: tags 1068433 + patch Dear maintainer, I've prepared an NMU for riseup-vpn (versioned as 0.21.11+ds1-5.1). The diff is attached to this message. Regards. -- Sebastian Ramacher diff -Nru riseup-vpn-0.21.11+ds1/debian/changelog riseup-vpn-0.21.11+ds1/debian/changelog ---

Bug#1065790: libosmo-netif: FTBFS on arm{el,hf}: tests fail

2024-04-13 Thread Steve Langasek
Package: libosmo-netif Followup-For: Bug #1065790 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Well, maybe a version of the patch without a stray character that breaks compilation. -- Steve Langasek Give me a lever long

Processed: Re: libosmo-netif: FTBFS on arm{el,hf}: tests fail

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1065790 {Done: Thorsten Alteholz } [src:libosmo-netif] libosmo-netif: FTBFS on arm{el,hf}: tests fail Ignoring request to alter tags of bug #1065790 to the same tags previously set -- 1065790:

Bug#1067567: dhcp-probe: diff for NMU version 1.3.0-10.2

2024-04-13 Thread Sebastian Ramacher
Dear maintainer, I've prepared an NMU for dhcp-probe (versioned as 1.3.0-10.2). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru dhcp-probe-1.3.0/debian/changelog dhcp-probe-1.3.0/debian/changelog --- dhcp-probe-1.3.0/debian/changelog 2014-10-15 14:20:18.0

Processed: comet-ms: diff for NMU version 2019015+cleaned1-4.1

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tags 1068221 + patch Bug #1068221 [comet-ms] comet-ms, dependencies unsatisfiable on 32-bit non-i386 architectures. Added tag(s) patch. -- 1068221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068221 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1068221: comet-ms: diff for NMU version 2019015+cleaned1-4.1

2024-04-13 Thread Sebastian Ramacher
Control: tags 1068221 + patch Dear maintainer, I've prepared an NMU for comet-ms (versioned as 2019015+cleaned1-4.1). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru comet-ms-2019015+cleaned1/debian/changelog comet-ms-2019015+cleaned1/debian/changelog ---

Bug#1066499: marked as done (thesias: FTBFS: src/thesiaslib.c:57:13: error: implicit declaration of function ‘thesiasRun’ [-Werror=implicit-function-declaration])

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 20:27:01 + with message-id and subject line Bug#1066499: fixed in thesias 3.1.1-2 has caused the Debian Bug report #1066499, regarding thesias: FTBFS: src/thesiaslib.c:57:13: error: implicit declaration of function ‘thesiasRun’

Bug#1067174: cpupower-gui: diff for NMU version 0.7.2-2.2

2024-04-13 Thread Sebastian Ramacher
Dear maintainer, I've prepared an NMU for cpupower-gui (versioned as 0.7.2-2.2). The diff is attached to this message. Cheer -- Sebastian Ramacher diff -Nru cpupower-gui-0.7.2/debian/changelog cpupower-gui-0.7.2/debian/changelog --- cpupower-gui-0.7.2/debian/changelog 2023-08-04

Bug#1068942: src:oscar4: unsatisfied build dependency in testing: emboss-data

2024-04-13 Thread Paul Gevers
Source: oscar4 Version: 5.2.0+dfsg-2 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be

Bug#1068941: src:mdevctl: unsatisfied build dependency in testing: librust-env-logger-0.10.0+default-dev

2024-04-13 Thread Paul Gevers
Source: mdevctl Version: 1.3.0-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed

Bug#1062881: mia: NMU diff for 64-bit time_t transition

2024-04-13 Thread Adrian Bunk
On Sat, Feb 03, 2024 at 09:20:05PM +, Graham Inggs wrote: > Source: mia > Version: 2.4.7-13 > Severity: serious > Tags: patch pending sid trixie > Justification: library ABI skew on upgrade > User: debian-...@lists.debian.org > Usertags: time-t >... Was this forgotten to upload to unstable,

Bug#1065790: libosmo-netif: FTBFS on arm{el,hf}: tests fail

2024-04-13 Thread Steve Langasek
Package: libosmo-netif Followup-For: Bug #1065790 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch Control: tags -1 patch Please find attached an alternative solution to this which has been uploaded to Ubuntu. I found it easier to fix the portability issue than deal

Processed: Re: libosmo-netif: FTBFS on arm{el,hf}: tests fail

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1065790 {Done: Thorsten Alteholz } [src:libosmo-netif] libosmo-netif: FTBFS on arm{el,hf}: tests fail Added tag(s) patch. -- 1065790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065790 Debian Bug Tracking System Contact

Processed: Re: Bug#1066408: fixed in ncl 6.6.2.dfsg.1-6

2024-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfixed 1066408 ncl/6.6.2.dfsg.1-6 Bug #1066408 {Done: Alastair McKinstry } [src:ncl] ncl: FTBFS: ld: cannot find -lncarg_c: No such file or directory No longer marked as fixed in versions ncl/6.6.2.dfsg.1-6. > fixed 1068387 ncl/6.6.2.dfsg.1-6

Bug#1050313: marked as done (kde-spectacle: crash because of missing dependencies)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 19:11:12 + with message-id and subject line Bug#1050313: fixed in kde-spectacle 23.08.5-1 has caused the Debian Bug report #1050313, regarding kde-spectacle: crash because of missing dependencies to be marked as done. This means that you claim that the

Bug#1053351: marked as done (filelight: Crashes on launch)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 19:05:46 + with message-id and subject line Bug#1053351: fixed in filelight 4:23.08.5-1 has caused the Debian Bug report #1053351, regarding filelight: Crashes on launch to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1057565: marked as done (kalzium: FTBFS: linking error)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 18:57:06 + with message-id and subject line Bug#1057565: fixed in kalzium 4:23.08.5-1 has caused the Debian Bug report #1057565, regarding kalzium: FTBFS: linking error to be marked as done. This means that you claim that the problem has been dealt with.

Processed: reassign 1068666 to ghc, forcibly merging 1068586 1068666

2024-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1068666 ghc Bug #1068666 [src:haskell-fold-debounce] haskell-fold-debounce: FTBFS on arm{el,hf}: 14 examples, 2 failures Bug reassigned from package 'src:haskell-fold-debounce' to 'ghc'. No longer marked as found in versions

Bug#1068657: marked as done (pkcs11-provider FTBFS with openssl 3.2.1-3)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 18:29:03 + with message-id and subject line Bug#1068657: fixed in pkcs11-provider 0.3-2 has caused the Debian Bug report #1068657, regarding pkcs11-provider FTBFS with openssl 3.2.1-3 to be marked as done. This means that you claim that the problem has

Bug#1067636: marked as done (nodejs: Testsuite fails with openssl 3.2)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 18:28:40 + with message-id and subject line Bug#1067636: fixed in nodejs 18.20.1+dfsg-2 has caused the Debian Bug report #1067636, regarding nodejs: Testsuite fails with openssl 3.2 to be marked as done. This means that you claim that the problem has been

Bug#1068869: marked as done (mu4e: Cannot open load file: No such file or directory, mu4e)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 18:26:33 + with message-id and subject line Bug#1068869: fixed in maildir-utils 1.12.3-3 has caused the Debian Bug report #1068869, regarding mu4e: Cannot open load file: No such file or directory, mu4e to be marked as done. This means that you claim that

Processed: Bug#1068497 marked as pending in golang-github-antonini-golibjpegturbo

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1068497 [src:golang-github-antonini-golibjpegturbo] golang-github-antonini-golibjpegturbo: FTBFS: Tries to access the network during build Added tag(s) pending. -- 1068497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068497 Debian Bug

Bug#1068497: marked as pending in golang-github-antonini-golibjpegturbo

2024-04-13 Thread Maytham Alsudany
Control: tag -1 pending Hello, Bug #1068497 in golang-github-antonini-golibjpegturbo 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:

Processed: Bug#1068403 marked as pending in mariadb

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1068403 [mariadb-plugin-hashicorp-key-management] mariadb-plugin-hashicorp-key-management dependencies unsatisfiable on 32-bit non-i386 architectures. Ignoring request to alter tags of bug #1068403 to the same tags previously set -- 1068403:

Processed: Bug#1068403 marked as pending in mariadb

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1068403 [mariadb-plugin-hashicorp-key-management] mariadb-plugin-hashicorp-key-management dependencies unsatisfiable on 32-bit non-i386 architectures. Added tag(s) pending. -- 1068403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068403

Processed: Bug#1068404 marked as pending in mariadb

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1068404 [mariadb-plugin-s3] mariadb-plugin-s3 dependencies unsatisfiable on 32-bit non-i386 architectures. Ignoring request to alter tags of bug #1068404 to the same tags previously set -- 1068404:

Processed: Bug#1068404 marked as pending in mariadb

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1068404 [mariadb-plugin-s3] mariadb-plugin-s3 dependencies unsatisfiable on 32-bit non-i386 architectures. Added tag(s) pending. -- 1068404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068404 Debian Bug Tracking System Contact

Bug#1068404: marked as pending in mariadb

2024-04-13 Thread Otto Kekäläinen
Control: tag -1 pending Hello, Bug #1068404 in mariadb 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#1068404: marked as pending in mariadb

2024-04-13 Thread Otto Kekäläinen
Control: tag -1 pending Hello, Bug #1068404 in mariadb 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#1068403: marked as pending in mariadb

2024-04-13 Thread Otto Kekäläinen
Control: tag -1 pending Hello, Bug #1068403 in mariadb 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#1068403: marked as pending in mariadb

2024-04-13 Thread Otto Kekäläinen
Control: tag -1 pending Hello, Bug #1068403 in mariadb 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#1068217: [Debichem-devel] Bug#1068217: atomes: diff for NMU version 1.1.14-1.1

2024-04-13 Thread Pierre Gruet
Hello Sebastian, Le 13/04/2024 à 19:45, Sebastian Ramacher a écrit : Control: tags 1068217 + patch Control: tags 1068217 + pending Dear maintainer, I've prepared an NMU for atomes (versioned as 1.1.14-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer.

Bug#1068937: python3-lxc: hard-coded dependency on liblcx1

2024-04-13 Thread Sebastian Ramacher
Package: python3-lxc Version: 1:5.0.0-1 Severity: serious X-Debbugs-Cc: sramac...@debian.org python3-lxc has an unneeded and hard-coded dependency on liblxc1 which is involved in the time_t transition. Please remove it. shlibs:Depends contains the correct dependency in this case. Cheers --

Bug#1068646: marked as done (pyorbital: autopkgtest regression on i386 with NumPy 1.26.4)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 17:58:50 + with message-id and subject line Bug#1068646: fixed in pyorbital 1.8.2-2 has caused the Debian Bug report #1068646, regarding pyorbital: autopkgtest regression on i386 with NumPy 1.26.4 to be marked as done. This means that you claim that the

Bug#1068936: libcanberra-gtk3-module: hard-coded dependency on libgtk-3-0

2024-04-13 Thread Sebastian Ramacher
Package: libcanberra-gtk3-module Version: 0.30-12 Severity: serious X-Debbugs-Cc: sramac...@debian.org This package has a hard-coded dependency on libgtk-3-0. Since libgtk-3-0 was renamed for the time_t transition, the dependency needs to be updated or simply removed. Even oldstable has a recent

Bug#1068934: perl: autopkgtest failure due to the t64 package rename

2024-04-13 Thread Niko Tyni
Source: perl Version: 5.38.2-3.2 Severity: serious Tags: patch User: debian-...@lists.debian.org Usertags: time-t X-Debbugs-Cc: Steve Langasek perl is failing its own autopkgtest checks in sid because of the libperl5.38 rename to libperl5.38t64.

Processed: tpm2-initramfs-tool: diff for NMU version 0.2.2-2.1

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tags 1068688 + patch Bug #1068688 [tpm2-initramfs-tool] tpm2-initramfs-tool dependencies unsatisfiable on 32-bit non-i386 architectures. Added tag(s) patch. > tags 1068688 + pending Bug #1068688 [tpm2-initramfs-tool] tpm2-initramfs-tool dependencies unsatisfiable

Bug#1068688: tpm2-initramfs-tool: diff for NMU version 0.2.2-2.1

2024-04-13 Thread Sebastian Ramacher
Control: tags 1068688 + patch Control: tags 1068688 + pending Dear maintainer, I've prepared an NMU for tpm2-initramfs-tool (versioned as 0.2.2-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru

Processed: atomes: diff for NMU version 1.1.14-1.1

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tags 1068217 + patch Bug #1068217 [atomes] atomes, dependencies unsatisfiable on 32-bit non-i386 architectures. Added tag(s) patch. > tags 1068217 + pending Bug #1068217 [atomes] atomes, dependencies unsatisfiable on 32-bit non-i386 architectures. Added tag(s)

Bug#1068217: atomes: diff for NMU version 1.1.14-1.1

2024-04-13 Thread Sebastian Ramacher
Control: tags 1068217 + patch Control: tags 1068217 + pending Dear maintainer, I've prepared an NMU for atomes (versioned as 1.1.14-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru atomes-1.1.14/debian/changelog

Bug#1063192: marked as done (supercollider: NMU diff for 64-bit time_t transition)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 17:29:22 + with message-id and subject line Bug#1063192: fixed in supercollider 1:3.13.0+repack-2 has caused the Debian Bug report #1063192, regarding supercollider: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that

Processed: 1068420

2024-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1068420 2.0-2 Bug #1068420 {Done: Luca Boccassi } [pidgin-gnome-keyring] pidgin-gnome-keyring - still depends on old libpurple after binnmu No longer marked as found in versions pidgin-gnome-keyring/2.0-2. > End of message, stopping

Bug#1057565: state of kalzium package, and metapackage dependencies on it.

2024-04-13 Thread Peter Green
kalzium needs to be rebuilt for the time64 transition, but it has had a FTBFS bug with no maintainer response for 4 months. The only reverse dependencies seem to be a number of metapackages. In particular, the kdeedu package is a key package and has a hard dependency on kalzium. This means that

Bug#1066551: ramond: FTBFS: src/main.c:164:17: error: implicit declaration of function ‘LOG’ [-Werror=implicit-function-declaration]

2024-04-13 Thread Steve Langasek
Package: ramond Followup-For: Bug #1066551 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: ramond: FTBFS: src/main.c:164:17: error: implicit declaration of function ‘LOG’ [-Werror=implicit-function-declaration]

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1066551 [src:ramond] ramond: FTBFS: src/main.c:164:17: error: implicit declaration of function ‘LOG’ [-Werror=implicit-function-declaration] Added tag(s) patch. -- 1066551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066551 Debian Bug

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

2024-04-13 Thread Guilhem Moulin
On Sat, 13 Apr 2024 at 10:06:32 -0400, Wesley Schwengle wrote: > I had the same issue a while back, because of the t64 transitioning I chaulked > it up to that. I fixed it as described in Ubuntu bug: > > https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594 libcryptsetup12

Bug#1068933: node-babel7: FTBFS in bookworm against nodejs 18.19.0+dfsg-6~deb12u1

2024-04-13 Thread Jérémy Lal
Package: node-babel7 Version: 7.20.15+ds1+~cs214.269.168-6 Severity: serious Tags: ftbfs Justification: fails to build from source This package FTBFS When rebuilding it in bookworm, against nodejs 18.19.0+dfsg-6~deb12u1 node-undici 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4 (not yet uploaded) The way

Bug#1065538: bind9-libs hard-codes a dependency on libuv1

2024-04-13 Thread Andreas Metzler
On 2024-03-06 Ondřej Surý wrote: >> On 6. 3. 2024, at 12:45, Matthias Klose wrote: >> Package: bind9-libs >> Version: 1:9.19.21-1 >> Severity: serious >> Tags: sid trixie >> bind9-libs hard-codes a dependency on libuv1, that should be >> libuv1t64 now. But better derive it form the libuv1-dev

Processed: fixed 1066454 in 2.44.1-1

2024-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1066454 2.44.1-1 Bug #1066454 {Done: Alberto Garcia } [src:wpewebkit] wpewebkit: FTBFS: SharedContextMutex.cpp:219:41: error: inlining failed in call to ‘always_inline’ ‘egl::SharedContextMutex* egl::SharedContextMutex::doTryLock() [with

Bug#1058552: marked as done (science.js: FTBFS: SyntaxError: Error parsing /<>/package.json: Unexpected end of JSON input)

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 15:28:35 + with message-id and subject line Bug#1058552: fixed in science.js 1.9.3+dfsg-4 has caused the Debian Bug report #1058552, regarding science.js: FTBFS: SyntaxError: Error parsing /<>/package.json: Unexpected end of JSON input to be marked as

Bug#1067561: FTBFS: Error: symbol `open64' is already defined

2024-04-13 Thread Peter Green
Hi, thanks for the patch. It looks a bit strong though, undefining stuff like that unconditionally. Do you have pointers to the Ubuntu bug or something? I've looked at upstream commits and issues and couldn't see anything there. My understanding of the issue. In glibc _FILE_OFFSET_BITS=64 is

Bug#1066398: marked as done (xwayland: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): undefined reference to `SHA1I

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 15:08:52 + with message-id and subject line Bug#1065184: fixed in xwayland 2:23.2.6-1 has caused the Debian Bug report #1065184, regarding xwayland: FTBFS:

Bug#1065184: marked as done (xwayland: missing build-dep on libtirpc-dev )

2024-04-13 Thread Debian Bug Tracking System
Your message dated Sat, 13 Apr 2024 15:08:52 + with message-id and subject line Bug#1065184: fixed in xwayland 2:23.2.6-1 has caused the Debian Bug report #1065184, regarding xwayland: missing build-dep on libtirpc-dev to be marked as done. This means that you claim that the problem has

Bug#1058552: marked as pending in science.js

2024-04-13 Thread Petter Reinholdtsen
Control: tag -1 pending Hello, Bug #1058552 in science.js 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:

Processed: Bug#1058552 marked as pending in science.js

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058552 [src:science.js] science.js: FTBFS: SyntaxError: Error parsing /<>/package.json: Unexpected end of JSON input Added tag(s) pending. -- 1058552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058552 Debian Bug Tracking System

Bug#1066398: xwayland: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): undefined reference to `SHA1Init'

2024-04-13 Thread Diederik de Haas
Control: forcemerge -1 1065184 On Saturday, 13 April 2024 16:32:04 CEST Andreas Metzler wrote: > > If you agree, please merge these two bugs. > > FTR: Bug #1065184 is already fixed in git. > > FWIW I can cobnfirm that xwayland builds successfully if libtirpc-dev is > installed. Thanks, then I'm

Processed: Re: Bug#1066398: xwayland: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): undefined reference to `SHA1In

2024-04-13 Thread Debian Bug Tracking System
Processing control commands: > forcemerge -1 1065184 Bug #1066398 [src:xwayland] xwayland: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): undefined reference to `SHA1Init' Bug #1065184 [src:xwayland] xwayland:

Bug#1066398: xwayland: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): undefined reference to `SHA1Init'

2024-04-13 Thread Andreas Metzler
On 2024-03-23 Diederik de Haas wrote: [...] > 2) near the end of your build log is the following message: > "../os/meson.build:63:8: ERROR: Problem encountered: secure-rpc requested, > but > neither libtirpc or libc RPC support were found" > And that matches the build issue mentioned in

  1   2   >