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

[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)

[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] -- ROM; cannot build on 32-bit archs 
due to missing builddeps
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quorum
Severity: serious
Tags: ftbfs
Control: found -1 1.1.2-2
X-Debbugs-Cc: ken...@xdump.org

Dear Maintainer,

quorum fails to build on armel, armhf, i386.

FYI:

https://buildd.debian.org/status/fetch.php?pkg=quorum=armel=1.1.2-2=1701603381=0
https://buildd.debian.org/status/fetch.php?pkg=quorum=armhf=1.1.2-2=1701603270=0
https://buildd.debian.org/status/fetch.php?pkg=quorum=i386=1.1.2-2=1701603340=0

Regards,
--- End Message ---
--- Begin Message ---
On Sun, 14 Apr 2024 03:26:27 +0530 Nilesh Patra  wrote:
> 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].
> There is already some concensus in -med team to prune 32-bit arch support 
for
> end-user applications (like quorum) if it is not straightfwd to maintain the
> support. It should make it to policy soonish.
> 
> [1]: 
> https://tracker.debian.org/news/1513470/accepted-jellyfish-231-3-source-into-unstable/

Package does not exist on these architectures in unstable, so closing the bug.

Scott K

signature.asc
Description: This is a digitally signed message part.
--- End Message ---

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])

[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 ‘ldap_search_ext’? 
[-Werror=implicit-function-declaration]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ldap2dns
Version: 0.3.1-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -g -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection  
> -DVERSION='"0.3.1"' -Wdate-time -D_FORTIFY_SOURCE=2 -c ldap2dns.c -o 
> ldap2dns.o-dbg
> ldap2dns.c: In function ‘read_resourcerecords’:
> ldap2dns.c:477:25: error: implicit declaration of function ‘ldap_search_s’; 
> did you mean ‘ldap_search_ext’? [-Werror=implicit-function-declaration]
>   477 | if ( (ldaperr = ldap_search_s(ldap_con, dn, 
> LDAP_SCOPE_SUBTREE, "objectclass=DNSrrset", NULL, 0, ))!=LDAP_SUCCESS )
>   | ^
>   | ldap_search_ext
> ldap2dns.c:558:82: warning: format ‘%s’ expects argument of type ‘char *’, 
> but argument 3 has type ‘char (*)[20]’ [-Wformat=]
>   558 | if 
> (sscanf(bvals[0]->bv_val, "%16s", )!=1)
>   |   
> ~~~^   ~
>   |   
>|   |
>   |   
>|   char (*)[20]
>   |   
>char *
> ldap2dns.c: In function ‘read_dnszones’:
> ldap2dns.c:714:98: warning: format ‘%s’ expects argument of type ‘char *’, 
> but argument 3 has type ‘char (*)[64]’ [-Wformat=]
>   714 | if 
> (sscanf(bvals[zonenames]->bv_val, "%64s", [zonenames])!=1)
>   |   
> ~~~^   ~~~
>   |   
>|   |
>   |   
>|   char (*)[64]
>   |   
>char *
> ldap2dns.c: In function ‘connect’:
> ldap2dns.c:801:28: error: implicit declaration of function ‘ldap_init’ 
> [-Werror=implicit-function-declaration]
>   801 | ldap_con = ldap_init(options.hostname[i], 
> options.port[i]);
>   |^
> ldap2dns.c:801:26: warning: assignment to ‘LDAP *’ {aka ‘struct ldap *’} from 
> ‘int’ makes pointer from integer without a cast [-Wint-conversion]
>   801 | ldap_con = ldap_init(options.hostname[i], 
> options.port[i]);
>   |  ^
> ldap2dns.c:802:21: error: implicit declaration of function 
> ‘ldap_simple_bind_s’; did you mean ‘ldap_sasl_bind_s’? 
> [-Werror=implicit-function-declaration]
>   802 | if (ldap_simple_bind_s(ldap_con, options.binddn, 
> options.password)==LDAP_SUCCESS) {
>   | ^~
>   | ldap_sasl_bind_s
> ldap2dns.c: In function ‘main’:
> ldap2dns.c:818:9: error: implicit declaration of function ‘umask’ 
> [-Werror=implicit-function-declaration]
>   818 | umask(022);
>   | ^
> ldap2dns.c:858:17: error: implicit declaration of function ‘time’ 
> [-Werror=implicit-function-declaration]
>   858 | time(_now);
>   | ^~~~
> ldap2dns.c:15:1: note: ‘time’ is defined in header ‘’; did 

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

[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 background on the original post:
https://trac.macports.org/ticket/61842. On this thread, the maintainer
prefers to fix it in a correct way as you said. But given upstream of
dx, maybe this is very thorny.

BR,
Bo
>
> Regards
> Graham

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

[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 that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: lua-lxc
Version: 1:3.0.2-2
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, lua-lxc
depends on both liblxc1 and libliblxc1t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
architectures).
--- End Message ---
--- Begin Message ---
Source: lua-lxc
Source-Version: 1:3.0.2-3
Done: Mathias Gibbens 

We believe that the bug you reported is fixed in the latest version of
lua-lxc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathias Gibbens  (supplier of updated lua-lxc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Apr 2024 01:26:26 +
Source: lua-lxc
Architecture: source
Version: 1:3.0.2-3
Distribution: unstable
Urgency: medium
Maintainer: pkg-lxc 
Changed-By: Mathias Gibbens 
Closes: 1068402
Changes:
 lua-lxc (1:3.0.2-3) unstable; urgency=medium
 .
   * Team upload
   * d/control:
 - Update Standards-Version to 4.7.0 (no changes needed)
 - Update Build-Depends pkg-config => pkgconf
 - Removed hard-coded Depends on liblxc1 (Closes: #1068402)
Checksums-Sha1:
 6745cffa7d5747604ce4d8d048746a4d4f8aa754 1955 lua-lxc_3.0.2-3.dsc
 bb958257c86b70f9bde90c604f7fbe7de971d61f 353927 lua-lxc_3.0.2.orig.tar.gz
 52d3b76a0bc128576e586b71eca5e4cb90a809dc 57304 lua-lxc_3.0.2-3.debian.tar.xz
 9fab527e72e3ac211cb08f1b8320dc3a78244d4b 7859 lua-lxc_3.0.2-3_amd64.buildinfo
Checksums-Sha256:
 63f55775f6d8afbfb99c7d88cc76016632cf162ce77f16981e06359cf8dd560f 1955 
lua-lxc_3.0.2-3.dsc
 5faf1c87db7e0ade5635c72cfed9e0434d26477721a791dbe56c0a99350ce448 353927 
lua-lxc_3.0.2.orig.tar.gz
 b4ee91bbf99b2c0187049253d59c3eea3c6ec81c9c80f3a7e01d04b8d2e0ffbc 57304 
lua-lxc_3.0.2-3.debian.tar.xz
 e84c0716793a15091eeb9902b406677881a9dd6e66e9e8e82106a2902b49e214 7859 
lua-lxc_3.0.2-3_amd64.buildinfo
Files:
 b5340f22abb47ddb7fc4eda532d02d8c 1955 interpreters optional lua-lxc_3.0.2-3.dsc
 6c7a25c78d7ffc1589c93e9fcba9a000 353927 interpreters optional 
lua-lxc_3.0.2.orig.tar.gz
 58fe5dc63fd96a32dc75ce91bc071496 57304 interpreters optional 
lua-lxc_3.0.2-3.debian.tar.xz
 63a40af90749314cec440a367dee7802 7859 interpreters optional 
lua-lxc_3.0.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE1Bp60H32xfynSJ8cKe7i1uz0QvkFAmYbMgwSHGdpYm1hdEBk
ZWJpYW4ub3JnAAoJECnu4tbs9EL5MxEQAIEJtPnwJso82w/ufjr4yVYM5nmEs593
mPfIUW+6Yp/90gGjLhVO7C3R7521hmrh5/36yKgMr5qlTyoD4JPXI+ElOGiiYO06
sFflUxd19ooZr0s1QGSNc9xA4ZyUl/JkQdOohgaPbpYnO8Ro5qrCxMlmBIUwsLNh
9ErrYH0ss/S3fbwoZps7jn0yP+DZWOB/yLqPYzfpi7ngj+NfjwXA4TMpH8SYuQ0w
6Y/0Dqnm3SbaTFKIV7yl/UhVniBIRi3iRqpvllRSwnlPz5Cb9UtUOK1nXo27q51G
7v+RNp6GPHwmj54Vu/vNMpDAevPfYF0hvp2/1ihpu+60uWApgHARwd09Ey5EgBHY
BcfX8VHqXGrSlTxOrDrdUUOoE+lMUUCRSULFFBMRUkK9St+R2OBTswFsh+/FH6UY
zkzAFz4B8oaiiRDqWU63ELGpaJGzxb/Ju67LAvEciMVPktE8fC0WsKUAkDGH1HjG
As7GgrDtuk+ofTx5jFK3GfI4XyTFEGrHyy/XuHdZTRz9tdbazcLlI5EiHjerIIlu
fkwXZ06y/AaojYQx4z2/oTF8GHECjw/CgY2EexJs1MXjh4y474sPRUmylwOQb9Kd
JDqA9oI6OGQmXCBtryJT/tsCtJ0vgHMME5jbhklJhHyHVog4+XoHxi8r8edF04s1
kIkXu6js6UpY
=FOUq
-END PGP SIGNATURE-



pgpvuebUhlZVQ.pgp
Description: PGP signature
--- End Message ---

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

[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 been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: python3-lxc
Source-Version: 1:5.0.0-2
Done: Mathias Gibbens 

We believe that the bug you reported is fixed in the latest version of
python3-lxc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathias Gibbens  (supplier of updated python3-lxc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Apr 2024 01:13:37 +
Source: python3-lxc
Architecture: source
Version: 1:5.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: pkg-lxc 
Changed-By: Mathias Gibbens 
Closes: 1068937
Changes:
 python3-lxc (1:5.0.0-2) unstable; urgency=medium
 .
   * d/control:
 - Update Standards-Version to 4.7.0 (no changes needed)
 - Update Build-Depends pkg-config => pkgconf
 - Removed hard-coded Depends on liblxc1 (Closes: #1068937)
   * Update years in d/copyright
Checksums-Sha1:
 971977bbadebe1e114990e8bfcf2b82037de8ce1 2388 python3-lxc_5.0.0-2.dsc
 31386cacea2700e6b85c779b6f74670934c7af2f 28013 python3-lxc_5.0.0.orig.tar.gz
 c456112604d9fe1670c301edc51dba9de4767815 833 python3-lxc_5.0.0.orig.tar.gz.asc
 6cba97243b53efe7e375985daa8d43e530f0af8d 6748 python3-lxc_5.0.0-2.debian.tar.xz
 5b9a851248213e8efe0d4245e120f4187fc20659 8921 
python3-lxc_5.0.0-2_amd64.buildinfo
Checksums-Sha256:
 1f2b31e3a407e7ee1821340e191f7e53f6dc0bac6feff9ab9dc5885ed97e6bbd 2388 
python3-lxc_5.0.0-2.dsc
 59c2d46106621df40eb3de331521c5664a71fe35a43ec1d640ec3a88d4e4730e 28013 
python3-lxc_5.0.0.orig.tar.gz
 8e1ba948615adbfe469aeac3b58ff5df7512a43ddb75ba6402534229994d01b0 833 
python3-lxc_5.0.0.orig.tar.gz.asc
 8786c16d445dbac79f463f6ec65ee25d6fbf5bad9a841e78b7a9620a1acf07fc 6748 
python3-lxc_5.0.0-2.debian.tar.xz
 e6e9433e4b3223bb5cebec02e15bfe163ee73e61a86025a0598dfa30654d4f40 8921 
python3-lxc_5.0.0-2_amd64.buildinfo
Files:
 ecd1ee5b44ba2a1faf1fb21826e55544 2388 python optional python3-lxc_5.0.0-2.dsc
 99e303f464d943dda09680976a9c4a84 28013 python optional 
python3-lxc_5.0.0.orig.tar.gz
 845b8058f8d6688f485ed065c9fa7594 833 python optional 
python3-lxc_5.0.0.orig.tar.gz.asc
 2039daad75433e34a36e381b293746e3 6748 python optional 
python3-lxc_5.0.0-2.debian.tar.xz
 ae1fdb62cda177feed818d15b9105943 8921 python optional 
python3-lxc_5.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE1Bp60H32xfynSJ8cKe7i1uz0QvkFAmYbLroSHGdpYm1hdEBk
ZWJpYW4ub3JnAAoJECnu4tbs9EL5ClQP/RHLS0Xs2e4q0cwNhQJiG89peLKgocsA
QWsjA/EnzrGY+HDX0TI2ZPXD2OHSqbCFaRkBy5lEDMbZ18iVvTMeCyzuv+amXSTS
G2r3jegUrMqkkRT9XKaqH2mUWjaFGftPTW4+jAQc331FkTGkZ1P/l1U+i1uCi4UT
SV1fAUtm4DwRb06i+Lvd4T9iq3lIBZ98r6HyEsLVbX06sJXciSeWyXM6Rqw7iePL
dyuM/cC7tb5X5JFYKn7mob2iJg+QMDjNqboVkF2xKR0QRe4tModXlCZU8Nxh+T8z
JqVwaaUmBRKp+/+YUuk09Hx5bVIY/Lsbg5+NOLCCPH+Fq8SeXMGYsVX6ktQf8YdO
V3dEfJr+TjRDxtwXftztYGHXE8LqhEakYh9zorZIJjk/jgsTm0PnKUFi+3g3nqAV
IBTH7qgm5YdG3W8EsUlEkYpwnSxOTw+6svSkXIe8QNwGCNvzpR5DkxQNbKjZAm2M
zvDLU9S0+70247L8dzh5ZGwuIkY2Nacav3auyljKneExzEBSlglq+Gu7J1gAWRf3
SWYlSVY8HzcZoD9UTr829GaZCvepDh0ttTE1MHuzAPxLVLEIUjKW7z+4CuDhpB5s
rSWPCRV3h60xJJbzc5G2gUtT5pV6IE/UlIKJvlvdmclJSHO8LLt1kAnoMzYHfCGL
JTuUfE5KgsOa
=NHAI
-END PGP SIGNATURE-



pgpN4Qr4MO3RP.pgp
Description: PGP signature
--- End Message ---

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

[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 Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru eterm-0.9.6/debian/patches/no-implicit-declarations.patch 
eterm-0.9.6/debian/patches/no-implicit-declarations.patch
--- eterm-0.9.6/debian/patches/no-implicit-declarations.patch   1969-12-31 
16:00:00.0 -0800
+++ eterm-0.9.6/debian/patches/no-implicit-declarations.patch   2024-04-13 
16:46:57.0 -0700
@@ -0,0 +1,18 @@
+Description: add missing include
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066342
+Last-Update: 2024-04-13
+Forwarded: no
+
+Index: eterm-0.9.6/src/libscream.c
+===
+--- eterm-0.9.6.orig/src/libscream.c
 eterm-0.9.6/src/libscream.c
+@@ -44,6 +44,7 @@
+ 
+ #include "config.h"
+ #include "feature.h"
++#include "misc.h"
+ 
+ /* use libast if we have it */
+ #ifdef DEBUG_ESCREEN
diff -Nru eterm-0.9.6/debian/patches/series eterm-0.9.6/debian/patches/series
--- eterm-0.9.6/debian/patches/series   2023-03-10 12:03:30.0 -0800
+++ eterm-0.9.6/debian/patches/series   2024-04-13 16:45:35.0 -0700
@@ -6,3 +6,4 @@
 fix-esetroot-on-pseudocolor.patch
 CVE-2021-33477.patch
 fix-fail-to-build-with-imlib2.patch
+no-implicit-declarations.patch

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

[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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-magit
Version: 3.3.0+git20231219.1.c7ab6931-1
Severity: serious

After loading magit Emacs displayed the following message in the
*Warnings* buffer:

,
| Emergency (magit): Magit requires ‘transient’ >= 0.5.0,
| but due to bad defaults, Emacs’ package manager, refuses to
| upgrade this and other built-in packages to higher releases
| from GNU Elpa.
`

Emacs' builtin version of transient is 0.4.3 which is too old,
installing the elpa-transient package fixed the problem.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.85-nouveau (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages elpa-magit depends on:
ii  dh-elpa-helper  2.0.17
ii  elpa-compat 29.1.4.5+dfsg-1
ii  elpa-dash   2.19.1+git20220608.1.0ac1ecf+dfsg-1
ii  elpa-git-commit 3.3.0+git20231219.1.c7ab6931-1
ii  elpa-magit-section  3.3.0+git20231219.1.c7ab6931-1
ii  elpa-seq2.24-1
ii  elpa-with-editor3.3.2-1
ii  emacsen-common  3.0.5
ii  git 1:2.43.0-1+b1

elpa-magit recommends no packages.

elpa-magit suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: magit
Source-Version: 3.3.0+git20240412.1.da14749d-1
Done: Aymeric Agon-Rambosson 

We believe that the bug you reported is fixed in the latest version of
magit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aymeric Agon-Rambosson  (supplier of updated magit 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 14 Apr 2024 00:52:46 +0200
Source: magit
Architecture: source
Version: 3.3.0+git20240412.1.da14749d-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Aymeric Agon-Rambosson 
Closes: 1068875 1068903
Changes:
 magit (3.3.0+git20240412.1.da14749d-1) unstable; urgency=medium
 .
   * New upstream snapshot (Closes: #1068875).
   * Refresh patches.
   * d/control: Add explicit versioned dependency on elpa-transient for
 elpa-magit and elpa-git-commit. This is temporary, pending changes to
 dh-elpa. (Closes: #1068903).
Checksums-Sha1:
 39804fd02edfe74798c8daf10aae20c1e19c9c81 2561 
magit_3.3.0+git20240412.1.da14749d-1.dsc
 4543588864e36038446ff94725e8a94c70e679fa 432884 
magit_3.3.0+git20240412.1.da14749d.orig.tar.xz
 11937f0469dc6e56864ca30c9e44f7776ba3c307 9828 
magit_3.3.0+git20240412.1.da14749d-1.debian.tar.xz
Checksums-Sha256:
 2b393dddbdfd129528a88acd5c76ed7bc76398f07e7a8cf039ba0250e501c6bf 2561 
magit_3.3.0+git20240412.1.da14749d-1.dsc
 180d05eb08fb529cbb09858722e6d2c25e8cdf56487483ed67535ce1be19159a 432884 
magit_3.3.0+git20240412.1.da14749d.orig.tar.xz
 1bb91bd7cb0317d95eb130e3fcf0a90a56362ad119b1bc102e70f4f5444d599a 9828 
magit_3.3.0+git20240412.1.da14749d-1.debian.tar.xz
Files:
 0ffe134a5bca8bb7993802c9eb2bfe44 2561 vcs optional 
magit_3.3.0+git20240412.1.da14749d-1.dsc
 b5771bfcd385aaa47722b196c131f1a2 432884 vcs optional 
magit_3.3.0+git20240412.1.da14749d.orig.tar.xz
 255094ba276b12185541886b471f550a 9828 vcs optional 
magit_3.3.0+git20240412.1.da14749d-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJMBAEBCgA2FiEEn7AKhFUciKVyzk7dN19hUwLeWCgFAmYbDdgYHGF5bWVyaWMu
YWdvbkB5YW5kZXguY29tAAoJEDdfYVMC3lgowx8P/ikyj1Jb6HEBfTDdY3IB9Sfz
JRYX0uYboDaoC3W3nUB6DUbaSU4z9MFeUvXyQN/bPYOhpmodswLalkFhFxF2Ygzs

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

[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
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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  to src/mrtdreader.c to fix build with
-Werror=implicit-function-declaration.

Thanks for considering the patch.


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-27-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru mrtdreader-0.1.6/debian/control mrtdreader-0.1.6/debian/control
--- mrtdreader-0.1.6/debian/control 2024-04-01 09:10:39.0 +1300
+++ mrtdreader-0.1.6/debian/control 2024-04-14 11:19:27.0 +1200
@@ -1,6 +1,5 @@
 Source: mrtdreader
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Ruben Undheim 
+Maintainer: Ruben Undheim 
 Section: utils
 Priority: optional
 Build-Depends: dpkg-dev (>= 1.22.5), debhelper (>= 11),
diff -Nru mrtdreader-0.1.6/debian/patches/missing-include.patch 
mrtdreader-0.1.6/debian/patches/missing-include.patch
--- mrtdreader-0.1.6/debian/patches/missing-include.patch   1970-01-01 
12:00:00.0 +1200
+++ mrtdreader-0.1.6/debian/patches/missing-include.patch   2024-04-14 
11:19:27.0 +1200
@@ -0,0 +1,10 @@
+--- a/src/mrtdreader.c
 b/src/mrtdreader.c
+@@ -19,6 +19,7 @@
+  */
+ 
+ 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru mrtdreader-0.1.6/debian/patches/series 
mrtdreader-0.1.6/debian/patches/series
--- mrtdreader-0.1.6/debian/patches/series  1970-01-01 12:00:00.0 
+1200
+++ mrtdreader-0.1.6/debian/patches/series  2024-04-14 11:18:28.0 
+1200
@@ -0,0 +1 @@
+missing-include.patch

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])

[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’? 
[-Werror=implicit-function-declaration]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: easyh10
Version: 1.5-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
> -I.. -I../include -I.  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o ucs2char_iconv.lo 
> ucs2char_iconv.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I. 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> ucs2char.c  -fPIC -DPIC -o .libs/ucs2char.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I. 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g 
> -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> ucs2char_iconv.c  -fPIC -DPIC -o .libs/ucs2char_iconv.o
> ucs2char.c: In function ‘print_ucs2’:
> ucs2char.c:284:28: warning: format ‘%c’ expects a matching ‘int’ argument 
> [-Wformat=]
>   284 | fprintf(stderr, "0x%X %c ", *str);
>   |   ~^
>   ||
>   |int
> ucs2char_iconv.c: In function ‘print_ucs2’:
> ucs2char_iconv.c:57:28: warning: format ‘%c’ expects a matching ‘int’ 
> argument [-Wformat=]
>57 | fprintf(stderr, "0x%X %c ", *str);
>   |   ~^
>   ||
>   |int
> ucs2char_iconv.c: In function ‘iconv_convert’:
> ucs2char_iconv.c:169:27: warning: passing argument 2 of ‘iconv’ from 
> incompatible pointer type [-Wincompatible-pointer-types]
>   169 | iconv(cd, (const char **)inbuf, , (char 
> **)outbuf, );
>   |   ^~~~
>   |   |
>   |   const char **
> In file included from ucs2char_iconv.c:40:
> /usr/include/iconv.h:49:54: note: expected ‘char ** restrict’ but argument is 
> of type ‘const char **’
>49 | extern size_t iconv (iconv_t __cd, char **__restrict __inbuf,
>   |~~^~~
> ucs2char_iconv.c:177:50: warning: passing argument 2 of ‘iconv’ from 
> incompatible pointer type [-Wincompatible-pointer-types]
>   177 | int iconvret = iconv(cd, (const char 
> **)inbuf, , , );
>   |  ^~~~
>   |  |
>   |  const char **
> /usr/include/iconv.h:49:54: note: expected ‘char ** restrict’ but argument is 
> of type ‘const char **’
>49 | extern size_t iconv (iconv_t __cd, char **__restrict __inbuf,
>   |~~^~~
> 

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

[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 you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: mariadb-plugin-s3
Version: 1:10.11.7-3
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, mariadb-plugin-s3
depends on both libcurl4 and libcurl4t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
architectures).
--- End Message ---
--- Begin Message ---
Source: mariadb
Source-Version: 1:10.11.7-4
Done: Otto Kekäläinen 

We believe that the bug you reported is fixed in the latest version of
mariadb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 11:07:08 -0700
Source: mariadb
Architecture: source
Version: 1:10.11.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Closes: 1067491 1068403 1068404
Changes:
 mariadb (1:10.11.7-4) unstable; urgency=medium
 .
   [ Michael Biebl ]
   * Drop unnecessary mariadb-server.prerm (Closes: #1067491)
   * Rely on dh_installsystemd to stop the service in postrm
 .
   [ Otto Kekäläinen ]
   * Remove direct dependencies on libcurl4 (Closes: #1068403, #1068404)
   * Make tests compatible with OpenSSL 3.2.0
Checksums-Sha1:
 feea4b8d4857344ba075ef0b003fc71d89115544 5078 mariadb_10.11.7-4.dsc
 f2da7ddfda894932cc213b891e28fd4095507634 279328 mariadb_10.11.7-4.debian.tar.xz
 4f3995e33fa19c1f90e101518bfc427b1394f572 9010 
mariadb_10.11.7-4_source.buildinfo
Checksums-Sha256:
 152e15c08bf60e7eae2a433a9344ac5b8a1e55dab80d932854e48bc98cc64fc0 5078 
mariadb_10.11.7-4.dsc
 c321165b783d41fa14e87d1cadd85a9241a2aabe8a389f4e9a2f9bd5658a2065 279328 
mariadb_10.11.7-4.debian.tar.xz
 c5af8b4288ec0e18646654f0a8a9464c60900827a9a33a67046a16a15e9beb36 9010 
mariadb_10.11.7-4_source.buildinfo
Files:
 0faa2f828edcff597749795d73df5405 5078 database optional mariadb_10.11.7-4.dsc
 36fee5f73f1c7c340cff23d68fc41b3d 279328 database optional 
mariadb_10.11.7-4.debian.tar.xz
 5cea57926b88de1df2ebe73fd6a8b3f3 9010 database optional 
mariadb_10.11.7-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAmYbAeIACgkQvthEn87o
2ohTlw/+PzGjSNYQFOtKujvRwZ6RuGJDSnAEp76Hraj1ioFEC5fs5ptr03F/mNRp
8+A+Zd2ncscFSeJLPdKwt0y+xYVYd49vtKTofSYyGVNR4QKf/SlafHJy+lWv8cs7
qTDzpVBMh9vHc/vBZMsRHgH314EQSZ0tzJTpFy4USEdQbK4NToWnuuxGMHMPaLMW
kXhd15y4u1nQ7xT7RL+Azapd6SsjvlnPcPa4QVmz+7aWQ/E4lQ/at1hgcRCxwffj
3kQbqup38S1y0ku/iQiaVOEMRpwBQA0aOrx7b7aOsXF3403QwbO/29AFvGrMUO4W
5ePPHNldhQKpFgNYFOPANMMMaMBw08gh5NCSF3Ycc7BgRv9W+jLxJUf8+RLe61ox
3mfb3DOOf8irfxh0hU4XdsOTIzuD9OFG2KdeIK/7jGAZNRXuWUUnezU741XUloWz
9yewlq/tbEIMZ5tdjdIaaHKyIUnGVlyogpgm68NULKk5Kne5QkjDSThry5tGpDZx
qSLQ6csaWeXNNguA2eFtfXerYXbblikGykPeLfVafY5tmz9yjzXcGBHJLg2dKPc1
3jMYexkc5LoJoRc/lz+KvjAkPw0VL7NJbUIMrN5OAD3JqAEpjo6E1wc1W7IoyFEp
dSvh3dy1v+M8oLd5HJk9wjkc99vd9lXLtThKJQ5b6kLrLsjckXc=
=p0Cp
-END PGP SIGNATURE-



pgpsTqCGT2daZ.pgp
Description: PGP signature
--- End Message ---

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

[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 done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: mariadb-plugin-hashicorp-key-management
Version: 1:10.11.7-3
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, 
mariadb-plugin-hashicorp-key-management
depends on both libcurl4 and libcurl4t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
architectures).
--- End Message ---
--- Begin Message ---
Source: mariadb
Source-Version: 1:10.11.7-4
Done: Otto Kekäläinen 

We believe that the bug you reported is fixed in the latest version of
mariadb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 11:07:08 -0700
Source: mariadb
Architecture: source
Version: 1:10.11.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Closes: 1067491 1068403 1068404
Changes:
 mariadb (1:10.11.7-4) unstable; urgency=medium
 .
   [ Michael Biebl ]
   * Drop unnecessary mariadb-server.prerm (Closes: #1067491)
   * Rely on dh_installsystemd to stop the service in postrm
 .
   [ Otto Kekäläinen ]
   * Remove direct dependencies on libcurl4 (Closes: #1068403, #1068404)
   * Make tests compatible with OpenSSL 3.2.0
Checksums-Sha1:
 feea4b8d4857344ba075ef0b003fc71d89115544 5078 mariadb_10.11.7-4.dsc
 f2da7ddfda894932cc213b891e28fd4095507634 279328 mariadb_10.11.7-4.debian.tar.xz
 4f3995e33fa19c1f90e101518bfc427b1394f572 9010 
mariadb_10.11.7-4_source.buildinfo
Checksums-Sha256:
 152e15c08bf60e7eae2a433a9344ac5b8a1e55dab80d932854e48bc98cc64fc0 5078 
mariadb_10.11.7-4.dsc
 c321165b783d41fa14e87d1cadd85a9241a2aabe8a389f4e9a2f9bd5658a2065 279328 
mariadb_10.11.7-4.debian.tar.xz
 c5af8b4288ec0e18646654f0a8a9464c60900827a9a33a67046a16a15e9beb36 9010 
mariadb_10.11.7-4_source.buildinfo
Files:
 0faa2f828edcff597749795d73df5405 5078 database optional mariadb_10.11.7-4.dsc
 36fee5f73f1c7c340cff23d68fc41b3d 279328 database optional 
mariadb_10.11.7-4.debian.tar.xz
 5cea57926b88de1df2ebe73fd6a8b3f3 9010 database optional 
mariadb_10.11.7-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAmYbAeIACgkQvthEn87o
2ohTlw/+PzGjSNYQFOtKujvRwZ6RuGJDSnAEp76Hraj1ioFEC5fs5ptr03F/mNRp
8+A+Zd2ncscFSeJLPdKwt0y+xYVYd49vtKTofSYyGVNR4QKf/SlafHJy+lWv8cs7
qTDzpVBMh9vHc/vBZMsRHgH314EQSZ0tzJTpFy4USEdQbK4NToWnuuxGMHMPaLMW
kXhd15y4u1nQ7xT7RL+Azapd6SsjvlnPcPa4QVmz+7aWQ/E4lQ/at1hgcRCxwffj
3kQbqup38S1y0ku/iQiaVOEMRpwBQA0aOrx7b7aOsXF3403QwbO/29AFvGrMUO4W
5ePPHNldhQKpFgNYFOPANMMMaMBw08gh5NCSF3Ycc7BgRv9W+jLxJUf8+RLe61ox
3mfb3DOOf8irfxh0hU4XdsOTIzuD9OFG2KdeIK/7jGAZNRXuWUUnezU741XUloWz
9yewlq/tbEIMZ5tdjdIaaHKyIUnGVlyogpgm68NULKk5Kne5QkjDSThry5tGpDZx
qSLQ6csaWeXNNguA2eFtfXerYXbblikGykPeLfVafY5tmz9yjzXcGBHJLg2dKPc1
3jMYexkc5LoJoRc/lz+KvjAkPw0VL7NJbUIMrN5OAD3JqAEpjo6E1wc1W7IoyFEp
dSvh3dy1v+M8oLd5HJk9wjkc99vd9lXLtThKJQ5b6kLrLsjckXc=
=p0Cp
-END PGP SIGNATURE-



pgpqvhfN3ksPU.pgp
Description: PGP signature
--- End Message ---

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

[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.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mariadb-server
Version: 1:10.11.7-3
Severity: serious

I did a 2G "apt dist-upgrade" to get my way through the time_t
transition. This failed halfway through with the following messages:

Uitpakken van .../10-mariadb-server_1%3a10.11.7-3_amd64.deb wordt voorbereid...
systemctl: error while loading shared libraries: libcrypto.so.3: cannot open 
shared object file: No such file or directory
dpkg: waarschuwing: subproces van het verouderd pakket mariadb-server het 
script pre-removal gaf de foutwaarde 127 terug
dpkg: script uit het nieuwe pakket wordt geprobeerd als alternatief...
systemctl: error while loading shared libraries: libcrypto.so.3: cannot open 
shared object file: No such file or directory
dpkg: fout bij verwerken van archief 
/tmp/apt-dpkg-install-IuQoIO/10-mariadb-server_1%3a10.11.7-3_amd64.deb 
(--unpack):
 subproces van het nieuwe pakket mariadb-server het script pre-removal gaf de 
foutwaarde 127 terug

Here, the Dutch terms translate (approximately) to:

"Unpacking .../10-mariadb-..."

dpkg: warning: subproces of the old package mariadb-server pre-removal script 
return error value 127
dpkg: trying script from the new package as alternative...

i.e., the prerm script tries to call systemctl, which fails because
libcrypto.so.3 is not on the filesystem. The new package's prerm script
tries the same, which fails for the same reason.

Checking dpkg.log, I see:

2024-03-22 12:12:24 remove libssl3:i386 3.1.5-1 
2024-03-22 12:12:24 status half-configured libssl3:i386 3.1.5-1
2024-03-22 12:12:24 status half-installed libssl3:i386 3.1.5-1
2024-03-22 12:12:24 status config-files libssl3:i386 3.1.5-1
2024-03-22 12:12:24 status not-installed libssl3:i386 
2024-03-22 12:12:24 remove libssl3:amd64 3.1.5-1 
2024-03-22 12:12:24 status half-configured libssl3:amd64 3.1.5-1
2024-03-22 12:12:24 status half-installed libssl3:amd64 3.1.5-1
2024-03-22 12:12:24 status config-files libssl3:amd64 3.1.5-1
2024-03-22 12:12:24 status not-installed libssl3:amd64 
2024-03-22 12:12:24 startup archives unpack
2024-03-22 12:12:25 install libssl3t64:i386  3.1.5-1.1
2024-03-22 12:12:25 status half-installed libssl3t64:i386 3.1.5-1.1
2024-03-22 12:12:25 status unpacked libssl3t64:i386 3.1.5-1.1

[...]

2024-03-22 12:18:20 upgrade mariadb-server:amd64 1:10.11.7-1 1:10.11.7-3
2024-03-22 12:18:20 status half-configured mariadb-server:amd64 1:10.11.7-1
2024-03-22 12:18:20 status installed mariadb-server:amd64 1:10.11.7-1
2024-03-22 12:18:20 upgrade mariadb-server-core:amd64 1:10.11.7-1 1:10.11.7-3
2024-03-22 12:18:20 status half-configured mariadb-server-core:amd64 1:10.11.7-1
2024-03-22 12:18:20 status unpacked mariadb-server-core:amd64 1:10.11.7-1
2024-03-22 12:18:20 status half-installed mariadb-server-core:amd64 1:10.11.7-1
2024-03-22 12:18:21 status unpacked mariadb-server-core:amd64 1:10.11.7-3

Full dpkg.log of this run attached.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=nl_BE:nl
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mariadb-server depends on:
ii  adduser3.137
ii  debconf [debconf-2.0]  1.5.86
ii  galera-4   26.4.16-2+b1
ii  gawk   1:5.2.1-2
ii  init-system-helpers1.66
ii  iproute2   6.8.0-1
ii  libc6  2.37-15.1
ii  libdbi-perl1.643-4+b1
ii  libpam0g   1.5.3-6
ii  libssl3t64 3.1.5-1.1
ii  libstdc++6 14-20240315-1
ii  lsof   4.95.0-1
ii  mariadb-client 1:10.11.7-3
ii  mariadb-common 1:10.11.7-3
ii  mariadb-server-core1:10.11.7-3
ii  passwd 1:4.13+dfsg1-4
ii  perl   5.38.2-3.2
ii  procps 2:4.0.4-4
ii  psmisc 23.7-1
ii  

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

[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’ [-Werror=implicit-function-declaration]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-fusefs
Version: 0.7.0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=ruby-fusefs=amd64=0.7.0-5%2Bb3=1710696156=0

make[1]: Entering directory '/<>/ext'
gcc -fdebug-prefix-map=/<>=. -I. 
-I/usr/include/x86_64-linux-gnu/ruby-3.1.0 
-I/usr/include/ruby-3.1.0/ruby/backward -I/usr/include/ruby-3.1.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=BUILDDIR=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -fPIC  -o fusefs_fuse.o -c fusefs_fuse.c
fusefs_fuse.c: In function ‘fusefs_fd’:
fusefs_fuse.c:31:10: error: implicit declaration of function ‘fuse_chan_fd’ 
[-Werror=implicit-function-declaration]
   31 |   return fuse_chan_fd(fusech);
  |  ^~~~
fusefs_fuse.c: In function ‘fusefs_unmount’:
fusefs_fuse.c:41:5: warning: ignoring return value of ‘system’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
   41 | system(buf);
  | ^~~
cc1: some warnings being treated as errors
make[1]: *** [Makefile:246: fusefs_fuse.o] Error 1
make[1]: Leaving directory '/<>/ext'

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: ruby-fusefs
Source-Version: 0.7.0-6
Done: Cédric Boutillier 

We believe that the bug you reported is fixed in the latest version of
ruby-fusefs, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-fusefs package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 23:27:54 +0200
Source: ruby-fusefs
Architecture: source
Version: 0.7.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 1067066
Changes:
 ruby-fusefs (0.7.0-6) unstable; urgency=medium
 .
   * Add patch to add missing includes. Thanks Zixing Liu (Closes: #1067066)
   * Move debian/watch to gemwatch.debian.net
   * Remove X?-Ruby-Versions fields from d/control
   * update years in d/copyright
   * Set Rules-Requires-Root to no
   * Use ${ruby:Depends}, drop explicit dependency on ruby interpreter
   * Bump Standards-Version to 4.7.0 (no changes needed)
Checksums-Sha1:
 2aa3b9d3566340804ad93abf61da90c16e6bcf78 1397 ruby-fusefs_0.7.0-6.dsc
 1d4a93e365ee9488bee468661eff756a83d5e4a2 23477 ruby-fusefs_0.7.0.orig.tar.gz
 bb0acae7b0d503175bde29f84916d20462b96e99 5040 ruby-fusefs_0.7.0-6.debian.tar.xz
 c6bd7e89b48d6deb3e867a63d7093f4e654ce398 9591 
ruby-fusefs_0.7.0-6_amd64.buildinfo
Checksums-Sha256:
 99560ef88da59bbb0fa05ac0a29effc2c0c29f45f11984b049d26761f81bf1ab 1397 
ruby-fusefs_0.7.0-6.dsc
 dcaf8623d7592f0cbc4b967a959dfa43dce4a0305596fe63019185e25e7c596a 23477 
ruby-fusefs_0.7.0.orig.tar.gz
 4b08a0cb08b8a524fb7aed81e68c742e9921158132514e8fff72ff608cf262d5 5040 
ruby-fusefs_0.7.0-6.debian.tar.xz
 d77bca1ea901c308f294e381eb63e6ce84de6f632ca32caa58bf5df2b0976223 9591 
ruby-fusefs_0.7.0-6_amd64.buildinfo
Files:
 02e80391a47cb098ab41f670fc8aeeff 1397 ruby optional ruby-fusefs_0.7.0-6.dsc
 e10c7da38fd4bfa356e441e6f992385a 23477 ruby optional 
ruby-fusefs_0.7.0.orig.tar.gz
 f6f21c1ad8ac90d52123eb6a431dcb4e 5040 ruby optional 
ruby-fusefs_0.7.0-6.debian.tar.xz
 4290e2b734b9c276f87df4e80777 9591 ruby optional 
ruby-fusefs_0.7.0-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQSEz/3CFSD4gwbsKdFSaZq2P58rwwUCZhr6zAAKCRBSaZq2P58r

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

[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 int&, unsigned 
int)’)
Changed Bug title to 'RM: quorum [armhf i386 armel] -- ROM; cannot build on 
32-bit archs due to missing builddeps' from 'quorum: FTBFS on armel, armhf,i386 
(error: no matching function for call to ‘min(const long long unsigned int&, 
unsigned int)’)'.
> reassign 1068065 ftp.debian.org
Bug #1068065 [src:quorum] RM: quorum [armhf i386 armel] -- ROM; cannot build on 
32-bit archs due to missing builddeps
Bug reassigned from package 'src:quorum' to 'ftp.debian.org'.
No longer marked as found in versions quorum/1.1.2-2.
Ignoring request to alter fixed versions of bug #1068065 to the same values 
previously set
> user ftp.debian@packages.debian.org
Setting user to ftp.debian@packages.debian.org (was nil...@debian.org).
> usertags 1068065 remove
There were no usertags set.
Usertags are now: remove.
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
1068065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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].
There is already some concensus in -med team to prune 32-bit arch support for
end-user applications (like quorum) if it is not straightfwd to maintain the
support. It should make it to policy soonish.

[1]: 
https://tracker.debian.org/news/1513470/accepted-jellyfish-231-3-source-into-unstable/

Best,
Nilesh


signature.asc
Description: PGP signature

Processed: closing 1053839

[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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1053839: closing 1053839

[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)

[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 has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blimps
Version: 3.9+ds-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source

Hi,

blimps FTBFS with -Werror=implicit-function-declaration which was
recently enabled by default in dpkg 1.22.6 to support the 64-bit time_t
transition. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

/usr/bin/gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/blimps-3.9+ds=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wuninitialized -O2  -I../include -fpic -Wdate-time -D_FORTI
FY_SOURCE=2  -c -o biassed_blocks_finder.o biassed_blocks_finder.c
biassed_blocks_finder.c: In function 'parse':
biassed_blocks_finder.c:101:6: error: implicit declaration of function 
'plustospace' [-Werror=implicit-function-declaration]
  101 |  plustospace(entries[i].val);
  |  ^~~
biassed_blocks_finder.c:102:6: error: implicit declaration of function 
'unescape_url' [-Werror=implicit-function-declaration]
  102 |  unescape_url(entries[i].val);
  |  ^~~~
biassed_blocks_finder.c: In function 'clean_temp_files':
biassed_blocks_finder.c:120:3: warning: ignoring return value of 'system' 
declared with attribute 'warn_unused_result' [-Wunused-result]
  120 |   system(buf);
  |   ^~~
...

Andreas
--- End Message ---
--- Begin Message ---
Source: blimps
Source-Version: 3.9+ds-2
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
blimps, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated blimps package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 14 Apr 2024 03:07:00 +0530
Source: blimps
Binary: blimps-examples blimps-utils blimps-utils-dbgsym libblimps3 
libblimps3-dbgsym libblimps3-dev
Architecture: source amd64
Version: 3.9+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Description:
 blimps-examples - blocks database improved searcher (example data)
 blimps-utils - blocks database improved searcher
 libblimps3 - blocks database improved searcher library
 libblimps3-dev - blocks database improved searcher library (development)
Closes: 1066956
Changes:
 blimps (3.9+ds-2) unstable; urgency=medium
 .
   * Team Upload.
   * Add patch to fix FTBFS with
 implicit-function-declaration (Closes: #1066956)
Checksums-Sha1:
 01137de1dc0383aed0abf13c34e1fc386520dd8b 1641 blimps_3.9+ds-2.dsc
 934f8ffc677cfaabea6132771e5e035f83631930 702420 blimps_3.9+ds.orig.tar.xz
 46f02a4caffa9bd9d82959aa1ec4c4852b9eb32e 26176 blimps_3.9+ds-2.debian.tar.xz
 fc231661d6d26661f429be1a6929e078574e15ac 218148 
blimps-examples_3.9+ds-2_amd64.deb
 78f26b6c44f57be5f3066925514fc2dfc5059053 6840 
blimps-utils-dbgsym_3.9+ds-2_amd64.deb
 f13adacf8bbe5f2de02a1bee6bfabf3981c6c543 235456 blimps-utils_3.9+ds-2_amd64.deb
 9cd831c2435fb15effb71412013cf1cadd392d1b 7048 blimps_3.9+ds-2_amd64.buildinfo
 287b2599264dd3c1d736741f545daa68a5eaa93c 154964 
libblimps3-dbgsym_3.9+ds-2_amd64.deb
 21f60cd49e6b2d68e3685c6de34308e2bbab57ff 93272 
libblimps3-dev_3.9+ds-2_amd64.deb
 64d4f6c8e99c355262ae98402c1d005548a9b2ec 64064 libblimps3_3.9+ds-2_amd64.deb
Checksums-Sha256:
 27cb901573811e304147a5e95feedfa2ccbe4b1a6595b1bba643411590ecdc23 1641 
blimps_3.9+ds-2.dsc
 8d3906a83538c5ff77c28e09b17765043f572c9ac69d2027b5b7279a7454ff0c 702420 
blimps_3.9+ds.orig.tar.xz
 4de6c2512652e96d4b3b7ad8285d82a2a3f126f0beac264392dda314e42a590d 26176 
blimps_3.9+ds-2.debian.tar.xz
 

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

[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 adding some
> >#include 
> > but I have no idea how to accomplish this.  The Salsa CI build log[1] says:
> > 
> > ...
> > y.tab.c: In function 'yyparse':
> > y.tab.c:1409:16: error: implicit declaration of function 'yylex' 
> > [-Werror=implicit-function-declaration]
> > y.tab.c:2185:7: error: implicit declaration of function 'yyerror'; did you 
> > mean 'YYerror'? [-Werror=implicit-function-declaration]
> > In file included from aqlparse.y:335:
> > aqlparse.l: In function 'yylex':
> > ...
> > 
> > Any help would be welcome
> > Andreas.
> 
> You are missing declarations:
> 
>  * `yylex`   - this needs to be added to the yacc source
>  * `yyerror` - this is present but hidden by a CPP conditional
>  * `yywrap`  - this is not needed (grep for "YY_SKIP_YYWRAP") and can be
>disabled
> 
> Patch attached.

I attach a fix for the next error:

  gcc -g -Wall  -DACEDB4 `../w3rdparty/include-config glib-2.0 gtk+-2.0`  -I.. 
-I../wh -I../wstaden -DACEDB_GTK -DLINUX -c -o sigsubs.o sigsubs.c
  sigsubs.c: In function 'getSignalText':
  sigsubs.c:486:30: error: '_sys_siglist' undeclared (first use in this 
function)
486 |   char **signal_textlist = &(_sys_siglist[0]) ;
|  ^~~~
  sigsubs.c:486:30: note: each undeclared identifier is reported only once for 
each function it appears in

The one after this looks like a GTK problem, and that's the point at
which I bow out.

J.
diff --git a/w4/sigsubs.c b/w4/sigsubs.c
index 2fd0c6ce9155..9d2942df1642 100644
--- a/w4/sigsubs.c
+++ b/w4/sigsubs.c
@@ -467,6 +467,10 @@ static char *getSignalText(int sig_num)
 
   return "unknown";
 
+#elif defined(LINUX)
+
+  return strsignal(sig_num);
+
 #else
 
   char *sig_text = NULL ;
@@ -485,7 +489,7 @@ static char *getSignalText(int sig_num)
 
   char **signal_textlist = &(_sys_siglist[0]) ;
 
-#if defined(LINUX) || defined(OPTERON) || defined(HP)
+#if defined(OPTERON) || defined(HP)
   int   signal_max= _NSIG ;
 #else
   int   signal_max= _sys_nsig ;


signature.asc
Description: PGP signature

Processed: Bug#1066956 marked as pending in blimps

[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

[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:

https://salsa.debian.org/med-team/blimps/-/commit/e0ea8796d5e68b19beb9fae642b3f35d803dd3e6


Add patch to fix FTBFS with implicit-function-declaration (Closes: #1066956)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066956

Bug#1068433: marked as done (riseup-vpn dependencies unsatisfiable on 32-bit non-i386 architectures.)

[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 you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: riseup-vpn
Version: 0.21.11+ds1-5
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, riseup-vpn
depends on both libqt5widgets5 and libqt5widgets5t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
architectures).

Ubuntu has already fixed this issue by removing the hardcoded
dependency on shared libraries.

http://launchpadlibrarian.net/720831431/riseup-vpn_0.21.11+ds1-5build3_0.21.11+ds1-5ubuntu1.diff.gz

--- End Message ---
--- Begin Message ---
Source: riseup-vpn
Source-Version: 0.21.11+ds1-5.1
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
riseup-vpn, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated riseup-vpn 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 22:46:43 +0200
Source: riseup-vpn
Architecture: source
Version: 0.21.11+ds1-5.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Sebastian Ramacher 
Closes: 1068433
Changes:
 riseup-vpn (0.21.11+ds1-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Matthias Klose ]
   * Drop hard-coded dependencies on shared libraries, ${shlibs:Depends}
 is working these days. (Closes: #1068433)
Checksums-Sha1:
 82b9fb4a7241c30e52898836bda2d80c6acd7a37 2428 riseup-vpn_0.21.11+ds1-5.1.dsc
 89a1a79f982d6e165708940b016fbd768d59540d 9064 
riseup-vpn_0.21.11+ds1-5.1.debian.tar.xz
 5e1d8dffa9ac701fa2d8f625426f871110595f15 9136 
riseup-vpn_0.21.11+ds1-5.1_source.buildinfo
Checksums-Sha256:
 43b0a63b910518d11c63ac08c06f1bef7f9b2783619ead95c4f8539c774abd8a 2428 
riseup-vpn_0.21.11+ds1-5.1.dsc
 b047ffa00b76d5db9bfe8c8a1dca012299a4832ce41ac4eb8d73be9783f7ce71 9064 
riseup-vpn_0.21.11+ds1-5.1.debian.tar.xz
 b5db3b3f049a8a9c089bcd7ef0c2eb5f7c9c95d2171fb93d634414f6589e20d5 9136 
riseup-vpn_0.21.11+ds1-5.1_source.buildinfo
Files:
 7264a320b57b2b5852375dbc4661 2428 net optional 
riseup-vpn_0.21.11+ds1-5.1.dsc
 b6d069addb51c6de6b8321a931a15601 9064 net optional 
riseup-vpn_0.21.11+ds1-5.1.debian.tar.xz
 6bfb653a274d89d7d72c13f178f0252e 9136 net optional 
riseup-vpn_0.21.11+ds1-5.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZhrwDAAKCRAhk2s2YA/N
iW2YAQC7tUBsYSSsOjeG2CWl1z/D5GrFcxhJtHDeVKTZj+viCQEA0reO547YFIpA
E6eJctzrWYHlzHddfjvNVWCWqBKHpQE=
=8YaC
-END PGP SIGNATURE-



pgpWYPa1Mehmc.pgp
Description: PGP signature
--- End Message ---

Bug#1067066: marked as pending in ruby-fusefs

[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:

https://salsa.debian.org/ruby-team/ruby-fusefs/-/commit/9e38b361d1949b09ba40e6dbcbe0d777db86f2f8


Add patch to add missing includes. Thanks Zixing Liu (Closes: #1067066)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067066

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

[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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1062558 is serious

[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 need assistance.
-- 
1062558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 given
> > its a change we want to do for Trixie, this will only lower the severity
> > of the bug.
> >
> 
> This has been fixed in git and will be addressed in the next upload.
> 
> https://salsa.debian.org/zfsonlinux-team/zfs/-/commit/f2ca97fdca7a35d63a3bae1af106bc3c238ca95f

The package is involved in the time_t transition. So please upload the
fix.

Cheers
-- 
Sebastian Ramacher

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

[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 promotion to testing is held up by weird 
dependency issues.

I'm downgrading the bug to prevent removal from testing.  I see no reason to 
remove a package that does build properly in unstable.

-Steve


signature.asc
Description: This is a digitally signed message part.

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

[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 *)’
Severity set to 'normal' from 'serious'

-- 
1065721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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.

Cheers
-- 
Sebastian Ramacher

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

[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 done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dhcp-probe
Version: 1.3.0-10.1
Severity: serious
Tags: patch
X-Debbugs-Cc: juli...@ubuntu.com
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch




*** /tmp/tmp9u3imu66/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

  * Remove hardcoded libpcap0.8, libnet1 dependencies; shlibs adds right ones

libpcap0.8 becomes libpcap0.8t64, hence it fails to install and the
package is not binNMUable.

Thanks for considering the patch.

*** /tmp/tmp9u3imu66/dhcp-probe_1.3.0-10.1ubuntu1.debdiff
diff -Nru dhcp-probe-1.3.0/debian/control dhcp-probe-1.3.0/debian/control
--- dhcp-probe-1.3.0/debian/control 2018-04-03 14:19:19.0 +0200
+++ dhcp-probe-1.3.0/debian/control 2024-03-23 20:16:10.0 +0100
@@ -1,15 +1,14 @@
 Source: dhcp-probe
 Section: net
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Laurent Guignard 
+Maintainer: Laurent Guignard 
 Build-Depends: debhelper (>= 7), quilt, autotools-dev, libpcap-dev (>= 0.9), 
libnet1-dev (>= 1.1.2.1-3), dpkg-dev (>=1.15.4), dh-autoreconf
 Standards-Version: 3.9.2
 Homepage: http://www.net.princeton.edu/software/dhcp_probe/
 
 Package: dhcp-probe
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, ucf, libpcap0.8 (>= 0.9), libnet1 
(>= 1.1.2.1-3), net-tools
+Depends: ${shlibs:Depends}, ${misc:Depends}, ucf, net-tools
 Description: network DHCP or BootP server discover
  dhcp_probe attempts to discover DHCP and BootP servers on a directly-attached
  Ethernet network. A network administrator can use this tool to locate un-


-- System Information:
Debian Release: trixie/sid
  APT prefers noble
  APT policy: (500, 'noble'), (500, 'mantic-security')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.8.0-11-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
--- End Message ---
--- Begin Message ---
Source: dhcp-probe
Source-Version: 1.3.0-10.2
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
dhcp-probe, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated dhcp-probe 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 22:39:00 +0200
Source: dhcp-probe
Architecture: source
Version: 1.3.0-10.2
Distribution: unstable
Urgency: medium
Maintainer: Laurent Guignard 
Changed-By: Sebastian Ramacher 
Closes: 1067567
Changes:
 dhcp-probe (1.3.0-10.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Julian Andres Klode ]
   * Remove hardcoded libpcap0.8, libnet1 dependencies; shlibs adds right ones
 (Closes: #1067567)
Checksums-Sha1:
 f7dab7614c99d2f31a5e0805cd5eb89d2df5286f 1269 dhcp-probe_1.3.0-10.2.dsc
 9bb99237d5a23dca91497c92f303542c3a07b82a 10580 
dhcp-probe_1.3.0-10.2.debian.tar.xz
 0817c52b5d39afcc2d7148f02bf479896be860a3 6371 
dhcp-probe_1.3.0-10.2_amd64.buildinfo
Checksums-Sha256:
 813b0adbe4c1e7aa2019c20d919a9c4c9c0c8e11dc3791ca867c8cff92715f36 1269 
dhcp-probe_1.3.0-10.2.dsc
 2e83eb3b26829d2ed814285bdf9dcee06d5fb142828ab8704b98d026c770b4a1 10580 
dhcp-probe_1.3.0-10.2.debian.tar.xz
 

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])

[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 ‘g_sprintf’? 
[-Werror=implicit-function-declaration]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: createrepo-c
Version: 0.17.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc 
> -DCR_DELTA_RPM_SUPPORT -DENABLE_LEGACY_WEAKDEPS=1 
> -DG_LOG_DOMAIN=\"C_CREATEREPOLIB\" -Dlibcreaterepo_c_EXPORTS 
> -I/<> -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 
> -I/usr/include/modulemd-2.0 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu99 -DWITH_ZCHUNK -DWITH_LIBMODULEMD 
> -fPIC -MD -MT src/CMakeFiles/libcreaterepo_c.dir/xml_parser_other.c.o -MF 
> CMakeFiles/libcreaterepo_c.dir/xml_parser_other.c.o.d -o 
> CMakeFiles/libcreaterepo_c.dir/xml_parser_other.c.o -c 
> /<>/src/xml_parser_other.c
> /<>/src/xml_file.c: In function ‘write_modified_header’:
> /<>/src/xml_file.c:338:36: error: implicit declaration of 
> function ‘rasprintf’; did you mean ‘g_sprintf’? 
> [-Werror=implicit-function-declaration]
>   338 | int package_count_string_len = rasprintf(_count_string, 
> "packages=\"%i\"", package_count);
>   |^
>   |g_sprintf
> [ 44%] Building C object 
> src/CMakeFiles/libcreaterepo_c.dir/xml_parser_primary.c.o
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc 
> -DCR_DELTA_RPM_SUPPORT -DENABLE_LEGACY_WEAKDEPS=1 
> -DG_LOG_DOMAIN=\"C_CREATEREPOLIB\" -Dlibcreaterepo_c_EXPORTS 
> -I/<> -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 
> -I/usr/include/modulemd-2.0 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu99 -DWITH_ZCHUNK -DWITH_LIBMODULEMD 
> -fPIC -MD -MT src/CMakeFiles/libcreaterepo_c.dir/xml_parser_primary.c.o -MF 
> CMakeFiles/libcreaterepo_c.dir/xml_parser_primary.c.o.d -o 
> CMakeFiles/libcreaterepo_c.dir/xml_parser_primary.c.o -c 
> /<>/src/xml_parser_primary.c
> [ 46%] Building C object 
> src/CMakeFiles/libcreaterepo_c.dir/xml_parser_repomd.c.o
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc 
> -DCR_DELTA_RPM_SUPPORT -DENABLE_LEGACY_WEAKDEPS=1 
> -DG_LOG_DOMAIN=\"C_CREATEREPOLIB\" -Dlibcreaterepo_c_EXPORTS 
> -I/<> -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 
> -I/usr/include/modulemd-2.0 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu99 -DWITH_ZCHUNK -DWITH_LIBMODULEMD 
> -fPIC -MD -MT src/CMakeFiles/libcreaterepo_c.dir/xml_parser_repomd.c.o -MF 
> CMakeFiles/libcreaterepo_c.dir/xml_parser_repomd.c.o.d -o 
> CMakeFiles/libcreaterepo_c.dir/xml_parser_repomd.c.o -c 
> /<>/src/xml_parser_repomd.c
> [ 47%] Building C object 
> src/CMakeFiles/libcreaterepo_c.dir/xml_parser_updateinfo.c.o
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cc 
> -DCR_DELTA_RPM_SUPPORT -DENABLE_LEGACY_WEAKDEPS=1 
> -DG_LOG_DOMAIN=\"C_CREATEREPOLIB\" -Dlibcreaterepo_c_EXPORTS 
> -I/<> -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 
> -I/usr/include/modulemd-2.0 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time 

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

[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 that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: comet-ms
Version: 2019015+cleaned1-4
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, comet-ms depends
on both libmstoolkit82 and libmstoolkit82t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
archictures).
--- End Message ---
--- Begin Message ---
Source: comet-ms
Source-Version: 2019015+cleaned1-4.1
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
comet-ms, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated comet-ms package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 22:27:15 +0200
Source: comet-ms
Architecture: source
Version: 2019015+cleaned1-4.1
Distribution: unstable
Urgency: medium
Maintainer: The Debichem Group 
Changed-By: Sebastian Ramacher 
Closes: 1068221
Changes:
 comet-ms (2019015+cleaned1-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Remove hard-coded dependency on libmstoolkit82. (Closes:
 #1068221)
Checksums-Sha1:
 13aa3aebbe4e22ba61c7d9c23959c7fc632f89e6 1484 comet-ms_2019015+cleaned1-4.1.dsc
 a104367afb14167d5c6727a659ebabd93e414987 6788 
comet-ms_2019015+cleaned1-4.1.debian.tar.xz
 8635548fc2eb1f1cb311b7054f6523633d83ed4d 6421 
comet-ms_2019015+cleaned1-4.1_amd64.buildinfo
Checksums-Sha256:
 907589a7a4f096c27f1fbfc79b88c1ca7996dcfdeb11037d9c1092e950801919 1484 
comet-ms_2019015+cleaned1-4.1.dsc
 05004bda0b5db500dff1d6be91d477dc0b4d97b6bf1715b433b9cb15a787a8f9 6788 
comet-ms_2019015+cleaned1-4.1.debian.tar.xz
 f373f07ae9a9adc14e764a7663a2d2ed3f6c09fc8e927fc3e7602f782cc76b5d 6421 
comet-ms_2019015+cleaned1-4.1_amd64.buildinfo
Files:
 06915dc80fbbc186c5e8b56e92bbabf4 1484 science optional 
comet-ms_2019015+cleaned1-4.1.dsc
 60aaa0e3839d39e2e84ce79171d188bf 6788 science optional 
comet-ms_2019015+cleaned1-4.1.debian.tar.xz
 59fa2625b07605f5917e3ceebbbddd9b 6421 science optional 
comet-ms_2019015+cleaned1-4.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZhrrKQAKCRAhk2s2YA/N
iUCgAQDZnNiPWQh+Msh1n8i2vryJy6Z3WmlLq4Iq6Q2BsBhR8wD+LAnhrfkBT5v2
w/3KhCDBebb+03KRqbdRlrp+ei7itwA=
=OBXt
-END PGP SIGNATURE-



pgpO9IQQB_W_Q.pgp
Description: PGP signature
--- End Message ---

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

[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 that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: chatty
Version: 0.8.2-1
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, chatty depends
on both libpurple0 and libpurple0t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
archictures).
--- End Message ---
--- Begin Message ---
Source: chatty
Source-Version: 0.8.2-1.1
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
chatty, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated chatty package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 23:05:24 +0200
Source: chatty
Architecture: source
Version: 0.8.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Sebastian Ramacher 
Closes: 1068219
Changes:
 chatty (0.8.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Julian Andres Klode ]
   * Bump local shlibs for libpurple0t64. (Closes: #1068219)
Checksums-Sha1:
 2511b9a0d6b1720f9a5413faa3e5c9eaefab2ae4 2012 chatty_0.8.2-1.1.dsc
 a1048b56e73dcdb983a60e823a0b3171f293d6cd 13016 chatty_0.8.2-1.1.debian.tar.xz
 2a8d39a7b493a66227ad0385d12190c17cc4a970 20863 chatty_0.8.2-1.1_amd64.buildinfo
Checksums-Sha256:
 9bbd58b3158854eed30ab2f07345a93b12b69cc1487e8f3e4f046c1d73b4209a 2012 
chatty_0.8.2-1.1.dsc
 9b183d174ef4dbd8b340ab686944ebef765b261d458d9d57d376335088ec346e 13016 
chatty_0.8.2-1.1.debian.tar.xz
 929ce7e4061b9409a550160384774f6f674f27f495f097d7818a5198a207f8fc 20863 
chatty_0.8.2-1.1_amd64.buildinfo
Files:
 9d6c9a783d546633c2375bf805a65a64 2012 net optional chatty_0.8.2-1.1.dsc
 4fb62f414e2e5736779c1569a51fe814 13016 net optional 
chatty_0.8.2-1.1.debian.tar.xz
 89467e11127f256f11fb982127e6c67b 20863 net optional 
chatty_0.8.2-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZhr0ZgAKCRAhk2s2YA/N
iXapAQCNySgppjWmCTgnOdrwAF58esSL6HGyjtbJVWSfKYM7DwEAlk2+89zebzuv
D6VnTnbXp5QLfzhbNbav9MV+7qTxtAs=
=vhq1
-END PGP SIGNATURE-



pgpFx_l1Vr9ch.pgp
Description: PGP signature
--- End Message ---

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

[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.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cpupower-gui
Version: 0.7.2-2.1
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t

cpupower-gui is an Architecture: all package, but has a direct dependency
on libgtk-3-0, as well as an indirect dependency on libgtk-3-0t64 via
gir1.2-gtk-3.0.

On the architectures affected by the 64-bit time_t transition (notably
armel and armhf), this is an impossible dependency, because libgtk-3-0 and
libgtk-3-0t64 conflict.

Please remove the explicit dependency on libgtk-3-0. For Python code
that uses GTK via GObject-Introspection, it is sufficient to depend
on gir1.2-gtk-3.0.

(This is mostly a theoretical concern because cpupower-gui is already
excluded from testing as a result of an unrelated RC bug #102.)

More information about this transition is available on
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: cpupower-gui
Source-Version: 0.7.2-2.2
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
cpupower-gui, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated cpupower-gui 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 22:20:07 +0200
Source: cpupower-gui
Architecture: source
Version: 0.7.2-2.2
Distribution: unstable
Urgency: medium
Maintainer: Evangelos Rigas 
Changed-By: Sebastian Ramacher 
Closes: 1067174
Changes:
 cpupower-gui (0.7.2-2.2) unstable; urgency=medium
 .
   [ Julian Andres Klode ]
   * Drop unnecessary libgtk-3-0 dependency, gir1.2-gtk-3.0 pulls it in.
 (Closes: #1067174)
Checksums-Sha1:
 1e2aeb3f1fa1b8a12cf1fd137f9780a3486b55e4 1671 cpupower-gui_0.7.2-2.2.dsc
 676e0b675074b5bf6ab99c48579669f8d3e45587 5620 
cpupower-gui_0.7.2-2.2.debian.tar.xz
 8361e78c7f5a4c16e48c2f2661e84169f696cf6c 6998 
cpupower-gui_0.7.2-2.2_amd64.buildinfo
Checksums-Sha256:
 232ed3e90462911a8451d266a22a0fd21194b1439af7ce0e7c24709ea92908ec 1671 
cpupower-gui_0.7.2-2.2.dsc
 d9af4f9eef30c0cf3966ec9cde586ecc819dbae277bad44a094e9f3122129d97 5620 
cpupower-gui_0.7.2-2.2.debian.tar.xz
 43a139a2d5f2bcff8a9e0f667b5d9c5d0c527b51c1a5e1cfd6273969860cb9e5 6998 
cpupower-gui_0.7.2-2.2_amd64.buildinfo
Files:
 c6cc2b9f807e113a5a98bf958d04380a 1671 admin optional cpupower-gui_0.7.2-2.2.dsc
 093cf1d583acd93403dba3e1d3b6e88c 5620 admin optional 
cpupower-gui_0.7.2-2.2.debian.tar.xz
 3b6b470f00f7c8a44be2cd0a87b8c0a2 6998 admin optional 
cpupower-gui_0.7.2-2.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZhrpRwAKCRAhk2s2YA/N
idBKAP900c4XSagrLSPhhX7OgIRlss/iXQhd9vmIMBUy6Rf9BwEAuVCgKra38ox+
VHoB4wgkl/nX6XT7EsCTf2iFI+t3HQM=
=xYw6
-END PGP SIGNATURE-



pgpEu5AWJylwW.pgp
Description: PGP signature
--- End Message ---

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

[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.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1065633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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

[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
+++ chatty-0.8.2/debian/changelog	2024-04-13 23:05:24.0 +0200
@@ -1,3 +1,12 @@
+chatty (0.8.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Julian Andres Klode ]
+  * Bump local shlibs for libpurple0t64. (Closes: #1068219)
+
+ -- Sebastian Ramacher   Sat, 13 Apr 2024 23:05:24 +0200
+
 chatty (0.8.2-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru chatty-0.8.2/debian/shlibs.local chatty-0.8.2/debian/shlibs.local
--- chatty-0.8.2/debian/shlibs.local	2023-05-14 11:49:24.0 +0200
+++ chatty-0.8.2/debian/shlibs.local	2024-04-13 23:04:49.0 +0200
@@ -1 +1 @@
-libjabber 0 libpurple0
+libjabber 0 libpurple0t64

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

[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 ow...@bugs.debian.org with problems

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

[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 Salsa CI build log[1] says:
> 
> ...
> y.tab.c: In function 'yyparse':
> y.tab.c:1409:16: error: implicit declaration of function 'yylex' 
> [-Werror=implicit-function-declaration]
> y.tab.c:2185:7: error: implicit declaration of function 'yyerror'; did you 
> mean 'YYerror'? [-Werror=implicit-function-declaration]
> In file included from aqlparse.y:335:
> aqlparse.l: In function 'yylex':
> ...
> 
> Any help would be welcome
> Andreas.

You are missing declarations:

 * `yylex`   - this needs to be added to the yacc source
 * `yyerror` - this is present but hidden by a CPP conditional
 * `yywrap`  - this is not needed (grep for "YY_SKIP_YYWRAP") and can be
   disabled

Patch attached.

You can find more info about all three in the flex and bison manuals.

J.
diff --git a/waql/aql_.h b/waql/aql_.h
index cde94a97896b..dd3b89116280 100644
--- a/waql/aql_.h
+++ b/waql/aql_.h
@@ -448,7 +448,7 @@ char* aqlNodeTypeName (AqlNodeType inType);
 char* aqlOpTypeName (AqlOpType inType);
 char* aqlLocSourceTypeName (AqlLocSourceType inType);
 
-#if defined(IBM)
+#if defined(IBM) || defined(LINUX)
 /* predeclare lex.yy.c fns */
 void yyerror (char *s);
 #endif
diff --git a/waql/aqlparse.l b/waql/aqlparse.l
index 313375027957..bc232e0a4c48 100644
--- a/waql/aqlparse.l
+++ b/waql/aqlparse.l
@@ -102,6 +102,8 @@
 
 %}
 
+%option			noyywrap
+
 letter			[A-Za-z]
 digit			[0-9]
 id			{letter}({letter}|{digit}|"_")*
diff --git a/waql/aqlparse.y b/waql/aqlparse.y
index 9989831a4838..975ae325c14c 100644
--- a/waql/aqlparse.y
+++ b/waql/aqlparse.y
@@ -77,6 +77,8 @@ static int tokPos[1024];
 
 /**/
 
+int yylex(void);
+
 %}
  
 %union  {


signature.asc
Description: PGP signature

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

[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
--- riseup-vpn-0.21.11+ds1/debian/changelog	2023-03-09 05:21:22.0 +0100
+++ riseup-vpn-0.21.11+ds1/debian/changelog	2024-04-13 22:46:43.0 +0200
@@ -1,3 +1,13 @@
+riseup-vpn (0.21.11+ds1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Matthias Klose ]
+  * Drop hard-coded dependencies on shared libraries, ${shlibs:Depends}
+is working these days. (Closes: #1068433)
+
+ -- Sebastian Ramacher   Sat, 13 Apr 2024 22:46:43 +0200
+
 riseup-vpn (0.21.11+ds1-5) unstable; urgency=medium
 
   * Add procps, iproute2 and iptables to Depends (Closes: #1031905)
diff -Nru riseup-vpn-0.21.11+ds1/debian/control riseup-vpn-0.21.11+ds1/debian/control
--- riseup-vpn-0.21.11+ds1/debian/control	2023-03-09 05:21:22.0 +0100
+++ riseup-vpn-0.21.11+ds1/debian/control	2024-04-13 22:46:39.0 +0200
@@ -57,10 +57,6 @@
  pkexec,
  procps,
  python3:any,
- libqt5core5a,
- libqt5gui5 | libqt5gui5-gles,
- libqt5qml5,
- libqt5widgets5,
  qml-module-qtquick2,
  qml-module-qtquick-controls2,
  qml-module-qtquick-controls,

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

[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 enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libosmo-netif-1.2.0/debian/patches/64-bit-time-t.patch 
libosmo-netif-1.2.0/debian/patches/64-bit-time-t.patch
--- libosmo-netif-1.2.0/debian/patches/64-bit-time-t.patch  1969-12-31 
16:00:00.0 -0800
+++ libosmo-netif-1.2.0/debian/patches/64-bit-time-t.patch  2024-04-13 
12:31:32.0 -0700
@@ -0,0 +1,136 @@
+Description: use a 64-bit safe format string for time_t.
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1065790
+Last-Update: 2024-04-13
+Forwarded: no
+
+Index: libosmo-netif-1.2.0/examples/ipa-stream-client.c
+===
+--- libosmo-netif-1.2.0.orig/examples/ipa-stream-client.c
 libosmo-netif-1.2.0/examples/ipa-stream-client.c
+@@ -143,7 +143,8 @@
+   timersub(, >tv, );
+ 
+   LOGP(DLINP, LOGL_NOTICE, "message %d replied "
+-  "in %lu.%.6lu\n", num, diff.tv_sec, diff.tv_usec);
++  "in %lld.%.6lld\n", num, (long long int)diff.tv_sec,
++  (long long int)diff.tv_usec);
+   talloc_free(found);
+   } else {
+   LOGP(DLINP, LOGL_ERROR,
+Index: libosmo-netif-1.2.0/src/jibuf.c
+===
+--- libosmo-netif-1.2.0.orig/src/jibuf.c
 libosmo-netif-1.2.0/src/jibuf.c
+@@ -385,10 +385,10 @@
+   timeradd(>last_enqueue_time, _ts, _ts);
+ 
+   LOGP(DLJIBUF, LOGL_DEBUG, "enqueuing packet seq=%"PRIu16" rel=%d 
delay=%d" \
+-  " skew=%d thres=%d {%lu.%06lu -> %lu.%06lu} %s\n",
++  " skew=%d thres=%d {%lld.%06lld -> %lld.%06lld} %s\n",
+   msg_get_sequence(msg), rel_delay, delay, jb->skew_us, 
jb->threshold_delay,
+-  jb->last_enqueue_time.tv_sec, jb->last_enqueue_time.tv_usec,
+-  sched_ts.tv_sec, sched_ts.tv_usec, msg_get_marker(msg)? "M" : 
"");
++  (long long int)jb->last_enqueue_time.tv_sec, (long long 
int)jb->last_enqueue_time.tv_usec,
++  (long long int)sched_ts.tv_sec, (long long 
int)sched_ts.tv_usec, msg_get_marker(msg)? "M" : "");
+ 
+   /* Add scheduled dequeue time in msg->cb so we can check it later */
+   unsigned long *old_cb = talloc_memdup(jb->talloc_ctx, msg->cb, 
sizeof(msg->cb));
+Index: libosmo-netif-1.2.0/tests/osmux/osmux_test.c
+===
+--- libosmo-netif-1.2.0.orig/tests/osmux/osmux_test.c
 libosmo-netif-1.2.0/tests/osmux/osmux_test.c
+@@ -69,8 +69,10 @@
+   struct timeval tv; \
+   osmo_clock_gettime(CLOCK_MONOTONIC, ); \
+   osmo_gettimeofday(, NULL); \
+-  fprintf(stderr, "sys={%lu.%06lu}, mono={%lu.%06lu}: " fmt, \
+-  tv.tv_sec, tv.tv_usec, ts.tv_sec, ts.tv_nsec/1000, 
##args); \
++  fprintf(stderr, "sys={%lld.%06lld}, mono={%lld.%06lld}: " fmt, \
++  (long long int)tv.tv_sec, (long long int)tv.tv_usec, \
++  (long long int)ts.tv_sec, \
++  (long long int)ts.tv_nsec/1000, ##args); \
+   } while(0)
+ 
+ static void clock_override_enable(bool enable)
+Index: libosmo-netif-1.2.0/tests/stream/stream_test.c
+===
+--- libosmo-netif-1.2.0.orig/tests/stream/stream_test.c
 libosmo-netif-1.2.0/tests/stream/stream_test.c
+@@ -60,7 +60,7 @@
+ #define LOGCLI(cli, fmt, args...) do { \
+   struct timeval tv; \
+   osmo_gettimeofday(, NULL); \
+-  printf("{%lu.%06lu} [%s] Client's %s(): " fmt, tv.tv_sec, 
tv.tv_usec, \
++  printf("{%lld.%06lld} [%s] Client's %s(): " fmt, (long long 
int)tv.tv_sec, (long long int)tv.tv_usec, \
+  osmo_stream_cli_get_data(cli) ? "OK" : "NA", __func__, 
##args); \
+   } while (0)
+ 
+@@ -235,7 +235,7 @@
+ #define LOGSRV(srv, fmt, args...) do { \
+   struct timeval tv; \
+   osmo_gettimeofday(, NULL); \
+-  printf("{%lu.%06lu} [%s|%s] Server's %s(): " fmt,  tv.tv_sec, 
tv.tv_usec, \
++  printf("{%lld.%06lld} [%s|%s] Server's %s(): " fmt,  (long long 
int)tv.tv_sec, (long long int)tv.tv_usec, \
+  osmo_stream_srv_get_data(srv) ? "OK" : "NA", \
+  
osmo_stream_srv_link_get_data(osmo_stream_srv_get_master(srv)) ? "OK" : "NA", \
+  

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

[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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 +0200
+++ dhcp-probe-1.3.0/debian/changelog	2024-04-13 22:39:00.0 +0200
@@ -1,3 +1,13 @@
+dhcp-probe (1.3.0-10.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Julian Andres Klode ]
+  * Remove hardcoded libpcap0.8, libnet1 dependencies; shlibs adds right ones
+(Closes: #1067567)
+
+ -- Sebastian Ramacher   Sat, 13 Apr 2024 22:39:00 +0200
+
 dhcp-probe (1.3.0-10.1) unstable; urgency=low
 
   * NMU
diff -Nru dhcp-probe-1.3.0/debian/control dhcp-probe-1.3.0/debian/control
--- dhcp-probe-1.3.0/debian/control	2014-10-15 14:21:32.0 +0200
+++ dhcp-probe-1.3.0/debian/control	2024-04-13 22:38:18.0 +0200
@@ -8,7 +8,7 @@
 
 Package: dhcp-probe
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, ucf, libpcap0.8 (>= 0.9), libnet1 (>= 1.1.2.1-3), net-tools
+Depends: ${shlibs:Depends}, ${misc:Depends}, ucf, net-tools
 Description: network DHCP or BootP server discover
  dhcp_probe attempts to discover DHCP and BootP servers on a directly-attached
  Ethernet network. A network administrator can use this tool to locate un-

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

[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 with problems

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

[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
--- comet-ms-2019015+cleaned1/debian/changelog	2023-11-24 15:11:18.0 +0100
+++ comet-ms-2019015+cleaned1/debian/changelog	2024-04-13 22:27:15.0 +0200
@@ -1,3 +1,11 @@
+comet-ms (2019015+cleaned1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Remove hard-coded dependency on libmstoolkit82. (Closes:
+#1068221)
+
+ -- Sebastian Ramacher   Sat, 13 Apr 2024 22:27:15 +0200
+
 comet-ms (2019015+cleaned1-4) unstable; urgency=low
 
   * Fix the Bug#1043799: comet-ms: Fails to build source after successful
diff -Nru comet-ms-2019015+cleaned1/debian/control comet-ms-2019015+cleaned1/debian/control
--- comet-ms-2019015+cleaned1/debian/control	2023-11-24 15:11:18.0 +0100
+++ comet-ms-2019015+cleaned1/debian/control	2024-04-13 22:26:37.0 +0200
@@ -15,8 +15,7 @@
 
 Package: comet-ms
 Architecture: any
-Depends: libmstoolkit82 (>= 82),
- ${shlibs:Depends},
+Depends: ${shlibs:Depends},
  ${misc:Depends}
 Description: Tandem mass spectrometry (MS/MS) search engine
  Comet is an open source tandem mass spectrometry (MS/MS) sequence

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

[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’ [-Werror=implicit-function-declaration]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thesias
Version: 3.1.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -fPIC 
> -I/usr/lib/jvm/default-java/include 
> -I/usr/lib/jvm/default-java/include/linux/ -c src/*.c
> javac -d class java/*.java
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
> src/newthesias3d.c: In function ‘thesiasRun’:
> src/newthesias3d.c:6122:49: warning: too many arguments for format 
> [-Wformat-extra-args]
>  6122 |  
> fprintf(outres,"\t%f\t%f\n\n",effest[0],valse,effest[0]/valse);
>   | ^~
> src/newthesias3d.c:6268:50: warning: too many arguments for format 
> [-Wformat-extra-args]
>  6268 |   
> fprintf(outres,"\t%f\t%f\n\n",effest[nc],valse,effest[nc]/valse);
>   |  ^~
> src/newthesias3d.c: In function ‘nbhapo0’:
> src/newthesias3d.c:4084:4: warning: ignoring return value of ‘scanf’ declared 
> with attribute ‘warn_unused_result’ [-Wunused-result]
>  4084 |scanf("%c",);
>   |^~~~
> src/newthesias3d.c: In function ‘lecteffe’:
> src/newthesias3d.c:4299:17: warning: ignoring return value of ‘fscanf’ 
> declared with attribute ‘warn_unused_result’ [-Wunused-result]
>  4299 | fscanf(readParam,"%c",);
>   | ^~~
> src/newthesias3d.c:4312:25: warning: ignoring return value of ‘fscanf’ 
> declared with attribute ‘warn_unused_result’ [-Wunused-result]
>  4312 | fscanf(readParam,"%c",);
>   | ^~~
> src/newthesias3d.c:4318:25: warning: ignoring return value of ‘fscanf’ 
> declared with attribute ‘warn_unused_result’ [-Wunused-result]
>  4318 | fscanf(readParam,"%d",);
>   | ^~
> src/newthesias3d.c:4327:33: warning: ignoring return value of ‘fscanf’ 
> declared with attribute ‘warn_unused_result’ [-Wunused-result]
>  4327 | fscanf(readParam,"%d %d",,);
>   | ^
> src/newthesias3d.c:4336:25: warning: ignoring return value of ‘fscanf’ 
> declared with attribute ‘warn_unused_result’ [-Wunused-result]
>  4336 | fscanf(readParam,"%c",);
>   | ^~~
> src/newthesias3d.c:4345:33: warning: ignoring return value of ‘fscanf’ 
> declared with attribute ‘warn_unused_result’ [-Wunused-result]
>  4345 | fscanf(readParam,"%d",);
>   | ^~~
> src/newthesias3d.c:4357:41: warning: ignoring return value of ‘fscanf’ 
> declared with attribute ‘warn_unused_result’ [-Wunused-result]
>  4357 | fscanf(readParam,"%d",);
>   | ^~
> src/newthesias3d.c:4369:41: warning: ignoring return value of ‘fscanf’ 
> declared with attribute ‘warn_unused_result’ [-Wunused-result]
>  4369 | fscanf(readParam,"%d 
> %d",,);
>   | 
> ^
> src/newthesias3d.c:4392:25: warning: ignoring return value of ‘fscanf’ 
> declared with attribute 

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

[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 22:43:45.0 +0200
+++ cpupower-gui-0.7.2/debian/changelog	2024-04-13 22:20:07.0 +0200
@@ -1,3 +1,11 @@
+cpupower-gui (0.7.2-2.2) unstable; urgency=medium
+
+  [ Julian Andres Klode ]
+  * Drop unnecessary libgtk-3-0 dependency, gir1.2-gtk-3.0 pulls it in.
+(Closes: #1067174)
+
+ -- Sebastian Ramacher   Sat, 13 Apr 2024 22:20:07 +0200
+
 cpupower-gui (0.7.2-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru cpupower-gui-0.7.2/debian/control cpupower-gui-0.7.2/debian/control
--- cpupower-gui-0.7.2/debian/control	2019-11-29 23:40:57.0 +0100
+++ cpupower-gui-0.7.2/debian/control	2024-04-13 22:19:38.0 +0200
@@ -19,7 +19,7 @@
 
 Package: cpupower-gui
 Architecture: any
-Depends: libgtk-3-0, gir1.2-gtk-3.0, python3-gi, hicolor-icon-theme,
+Depends: gir1.2-gtk-3.0, python3-gi, hicolor-icon-theme,
  policykit-1, python3-dbus, ${misc:Depends}, ${python3:Depends}
 Suggests: policykit-1-gnome, lxqt-policykit, mate-polkit, lxsession
 Description: GUI utility to change the CPU frequency

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

[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
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature.asc
Description: OpenPGP digital signature

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

[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 from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature.asc
Description: OpenPGP digital signature

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

[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, or was there a reason why it 
was deemed unnecessary?

Thanks
Adrian

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

[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 with
removing the reverse-dependency chain.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libosmo-netif-1.2.0/debian/patches/64-bit-time-t.patch 
libosmo-netif-1.2.0/debian/patches/64-bit-time-t.patch
--- libosmo-netif-1.2.0/debian/patches/64-bit-time-t.patch  1969-12-31 
16:00:00.0 -0800
+++ libosmo-netif-1.2.0/debian/patches/64-bit-time-t.patch  2024-04-13 
12:30:35.0 -0700
@@ -0,0 +1,142 @@
+Description: use a 64-bit safe format string for time_t.
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1065790
+Last-Update: 2024-04-13
+Forwarded: no
+
+Index: libosmo-netif-1.2.0/examples/ipa-stream-client.c
+===
+--- libosmo-netif-1.2.0.orig/examples/ipa-stream-client.c
 libosmo-netif-1.2.0/examples/ipa-stream-client.c
+@@ -143,7 +143,8 @@
+   timersub(, >tv, );
+ 
+   LOGP(DLINP, LOGL_NOTICE, "message %d replied "
+-  "in %lu.%.6lu\n", num, diff.tv_sec, diff.tv_usec);
++  "in %lld.%.6lld\n", num, (long long int)diff.tv_sec,
++  (long long int)diff.tv_usec);
+   talloc_free(found);
+   } else {
+   LOGP(DLINP, LOGL_ERROR,
+Index: libosmo-netif-1.2.0/src/jibuf.c
+===
+--- libosmo-netif-1.2.0.orig/src/jibuf.c
 libosmo-netif-1.2.0/src/jibuf.c
+@@ -385,10 +385,10 @@
+   timeradd(>last_enqueue_time, _ts, _ts);
+ 
+   LOGP(DLJIBUF, LOGL_DEBUG, "enqueuing packet seq=%"PRIu16" rel=%d 
delay=%d" \
+-  " skew=%d thres=%d {%lu.%06lu -> %lu.%06lu} %s\n",
++  " skew=%d thres=%d {%lld.%06lld -> %lld.%06lld} %s\n",
+   msg_get_sequence(msg), rel_delay, delay, jb->skew_us, 
jb->threshold_delay,
+-  jb->last_enqueue_time.tv_sec, jb->last_enqueue_time.tv_usec,
+-  sched_ts.tv_sec, sched_ts.tv_usec, msg_get_marker(msg)? "M" : 
"");
++  (long long int)jb->last_enqueue_time.tv_sec, (long long 
int)jb->last_enqueue_time.tv_usec,
++  (long long int)sched_ts.tv_sec, (long long 
int)sched_ts.tv_usec, msg_get_marker(msg)? "M" : "");
+ 
+   /* Add scheduled dequeue time in msg->cb so we can check it later */
+   unsigned long *old_cb = talloc_memdup(jb->talloc_ctx, msg->cb, 
sizeof(msg->cb));
+Index: libosmo-netif-1.2.0/tests/osmux/osmux_test.c
+===
+--- libosmo-netif-1.2.0.orig/tests/osmux/osmux_test.c
 libosmo-netif-1.2.0/tests/osmux/osmux_test.c
+@@ -1,4 +1,4 @@
+-/*
++y/*
+  * (C) 2013 by Pablo Neira Ayuso 
+  * (C) 2013 by On Waves ehf 
+  *
+@@ -69,8 +69,10 @@
+   struct timeval tv; \
+   osmo_clock_gettime(CLOCK_MONOTONIC, ); \
+   osmo_gettimeofday(, NULL); \
+-  fprintf(stderr, "sys={%lu.%06lu}, mono={%lu.%06lu}: " fmt, \
+-  tv.tv_sec, tv.tv_usec, ts.tv_sec, ts.tv_nsec/1000, 
##args); \
++  fprintf(stderr, "sys={%lld.%06lld}, mono={%lld.%06lld}: " fmt, \
++  (long long int)tv.tv_sec, (long long int)tv.tv_usec, \
++  (long long int)ts.tv_sec, \
++  (long long int)ts.tv_nsec/1000, ##args); \
+   } while(0)
+ 
+ static void clock_override_enable(bool enable)
+Index: libosmo-netif-1.2.0/tests/stream/stream_test.c
+===
+--- libosmo-netif-1.2.0.orig/tests/stream/stream_test.c
 libosmo-netif-1.2.0/tests/stream/stream_test.c
+@@ -60,7 +60,7 @@
+ #define LOGCLI(cli, fmt, args...) do { \
+   struct timeval tv; \
+   osmo_gettimeofday(, NULL); \
+-  printf("{%lu.%06lu} [%s] Client's %s(): " fmt, tv.tv_sec, 
tv.tv_usec, \
++  printf("{%lld.%06lld} [%s] Client's %s(): " fmt, (long long 
int)tv.tv_sec, (long long int)tv.tv_usec, \
+  osmo_stream_cli_get_data(cli) ? "OK" : "NA", __func__, 
##args); \
+   } while (0)
+ 
+@@ -235,7 +235,7 @@
+ #define LOGSRV(srv, fmt, args...) do { \
+   struct timeval tv; \
+   osmo_gettimeofday(, NULL); \
+-  printf("{%lu.%06lu} [%s|%s] Server's %s(): " fmt,  tv.tv_sec, 
tv.tv_usec, \
++  printf("{%lld.%06lld} [%s|%s] Server's %s(): " fmt,  (long long 

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

[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 ow...@bugs.debian.org with problems

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

[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 #1068387 [src:ncl] ncl: FTBFS with HDF 4.3.0.
Marked as fixed in versions ncl/6.6.2.dfsg.1-6.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1066408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066408
1068387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1050313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kde-spectacle
Version: 23.04.2-2
Severity: important


specatecle needs "libqt5quickshapes5" & "qml-module-qtquick-shapes" installed.

without these it will crash:


$ spectacle
kf.kirigami: Failed to find a Kirigami platform plugin
qrc:/src/Gui/ScreenshotView.qml:167:9: Type AnnotationEditor unavailable
qrc:/src/Gui/Annotations/AnnotationEditor.qml:31:9: Type TextTool unavailable
qrc:/src/Gui/Annotations/TextTool.qml:162:21: Type SelectionBackground 
unavailable
qrc:/src/Gui/Annotations/SelectionBackground.qml:6:1: module "QtQuick.Shapes" 
is not installed
qrc:/src/Gui/ImageCaptureOverlay.qml:36:5: Type AnnotationEditor unavailable
 AnnotationEditor {
 ^
qrc:/src/Gui/Annotations/AnnotationEditor.qml:31:9: Type TextTool unavailable
 TextTool {
 ^
qrc:/src/Gui/Annotations/TextTool.qml:162:21: Type SelectionBackground 
unavailable
 background: SelectionBackground { zoom: root.viewport.zoom }
 ^
qrc:/src/Gui/Annotations/SelectionBackground.qml:6:1: module "QtQuick.Shapes" 
is not installed
 import QtQuick.Shapes 1.15
 ^




-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.0-2-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kde-spectacle depends on:
ii  kio5.107.0-1
ii  libc6  2.37-7
ii  libkf5configcore5  5.107.0-1
ii  libkf5configgui5   5.107.0-1
ii  libkf5configwidgets5   5.107.0-2
ii  libkf5coreaddons5  5.107.0-1
ii  libkf5dbusaddons5  5.107.0-1
ii  libkf5globalaccel-bin  5.107.0-2
ii  libkf5globalaccel5 5.107.0-2
ii  libkf5guiaddons5   5.107.0-1
ii  libkf5i18n55.107.0-1+b1
ii  libkf5kiocore5 5.107.0-1
ii  libkf5kiogui5  5.107.0-1
ii  libkf5kiowidgets5  5.107.0-1
ii  libkf5kirigami2-5  5.107.0-1+b1
ii  libkf5notifications5   5.107.0-1
ii  libkf5purpose-bin  5.107.0-1
ii  libkf5purpose5 5.107.0-1
ii  libkf5service-bin  5.107.0-1
ii  libkf5service5 5.107.0-1
ii  libkf5widgetsaddons5   5.107.0-1
ii  libkf5windowsystem55.107.0-1
ii  libkf5xmlgui5  5.107.0-1+b1
ii  libkpipewirerecord55.27.7-1
ii  libqt5core5a   5.15.10+dfsg-3
ii  libqt5dbus55.15.10+dfsg-3
ii  libqt5gui5 5.15.10+dfsg-3
ii  libqt5printsupport55.15.10+dfsg-3
ii  libqt5qml5 5.15.10+dfsg-2
ii  libqt5quick5   5.15.10+dfsg-2
ii  libqt5waylandclient5   5.15.10-2
ii  libqt5widgets5 5.15.10+dfsg-3
ii  libqt5x11extras5   5.15.10-2
ii  libstdc++6 13.2.0-2
ii  libwayland-client0 1.22.0-2
ii  libxcb-cursor0 0.1.4-1
ii  libxcb-image0  0.4.0-2
ii  libxcb-util1   0.4.0-1+b1
ii  libxcb-xfixes0 1.15-1
ii  libxcb11.15-1
ii  qdbus-qt5  5.15.10-3

kde-spectacle recommends no packages.

kde-spectacle suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: kde-spectacle
Source-Version: 23.08.5-1
Done: Patrick Franz 

We believe that the bug you reported is fixed in the latest version of
kde-spectacle, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1050...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Patrick Franz  (supplier of updated kde-spectacle package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 

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

[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.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1053351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: filelight
Version: 4:23.04.2-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: pepijnleon...@gmail.com

Dear Maintainer,

When launching filelight, it crashes with the following error:

$ filelight
kf.kirigami: Failed to find a Kirigami platform plugin
Segmentation fault

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages filelight depends on:
ii  kio 5.107.0-1
ii  libc6   2.37-10
ii  libkf5configcore5   5.107.0-1
ii  libkf5coreaddons5   5.107.0-1
ii  libkf5i18n5 5.107.0-1+b1
ii  libkf5kiocore5  5.107.0-1
ii  libkf5kiogui5   5.107.0-1
ii  libkf5kiowidgets5   5.107.0-1
ii  libkf5widgetsaddons55.107.0-1
ii  libkf5xmlgui5   5.107.0-1+b1
ii  libqt5core5a5.15.10+dfsg-3
ii  libqt5gui5  5.15.10+dfsg-3
ii  libqt5qml5  5.15.10+dfsg-2
ii  libqt5quick55.15.10+dfsg-2
ii  libqt5quickcontrols2-5  5.15.10+dfsg-2
ii  libqt5widgets5  5.15.10+dfsg-3
ii  libstdc++6  13.2.0-4
ii  qml-module-org-kde-kcoreaddons  5.107.0-1
ii  qml-module-org-kde-kirigami25.107.0-1+b1
ii  qml-module-org-kde-quickcharts  5.107.0-1
ii  qml-module-qt-labs-platform 5.15.10+dfsg-2

filelight recommends no packages.

filelight suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: filelight
Source-Version: 4:23.08.5-1
Done: Patrick Franz 

We believe that the bug you reported is fixed in the latest version of
filelight, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1053...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Patrick Franz  (supplier of updated filelight package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 21:01:09 +0200
Source: filelight
Architecture: source
Version: 4:23.08.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Patrick Franz 
Closes: 1053351
Changes:
 filelight (4:23.08.5-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Jesse Rhodes ]
   * New upstream release (23.08.5).
   * Update runtime dependencies with info from cmake. (Closes: #1053351)
   * Clean up build artifact.
Checksums-Sha1:
 1e1571596cbe57fedb64bf1c68d029587428faac 2551 filelight_23.08.5-1.dsc
 11d6eb2bafc6275699ef661b39a6366b75e11b83 700500 filelight_23.08.5.orig.tar.xz
 9bbdd7c563be175eb07132b4d1cb779148dc20e5 833 filelight_23.08.5.orig.tar.xz.asc
 9b4d327b2237ae1a549649ce171f2d3c96454b9a 14992 
filelight_23.08.5-1.debian.tar.xz
 1a6fcecef2fe45ea72e09606b314a670b14d8f36 12972 
filelight_23.08.5-1_source.buildinfo
Checksums-Sha256:
 b64972e57963fbc6657a7814deeb023d5b347caec08ef95cf1727dbaee8186da 2551 
filelight_23.08.5-1.dsc
 b7fc4daefc0985dc4b0deeb3c25e09a1b85ff896560340e79cca5093d3f07522 700500 
filelight_23.08.5.orig.tar.xz
 f044d4ccff1fc26e946bda35c36bf015ef55281fafc4221db2d59249e5e4a801 833 
filelight_23.08.5.orig.tar.xz.asc
 a1b33cd5231d3e75b7817188fcde968dac9af9801ccabe9a83c4e167fc1c5df6 14992 
filelight_23.08.5-1.debian.tar.xz
 

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

[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.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1057565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:kalzium
Version: 4:22.12.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with kf5
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=kf5
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON ..
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
-- Could not set up the appstream test. appstreamcli is missing.
-- Found Gettext: /usr/bin/msgmerge (found version "0.21")
CMake Warning (dev) at CMakeLists.txt:39 (find_package):
  Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules
  are removed.  Run "cmake --help-policy CMP0148" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

This warning is for project developers.  Use -Wno-dev to suppress it.

-- Found PythonInterp: /usr/bin/python3 (found version "3.11.7")
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.1")
-- Found OCaml: /usr/bin/ocamlc
-- Found Libfacile: /usr/lib/ocaml/facile
-- Checking for module 'chemical-mime-data'
--   Found chemical-mime-data, version 0.1.94
-- Looking for include file ieeefp.h
-- Looking for include file ieeefp.h - not found
-- Found KF5Archive: /usr/lib/x86_64-linux-gnu/cmake/KF5Archive/KF5ArchiveConfig.cmake 
(found version "5.107.0")
-- Found KF5Config: /usr/lib/x86_64-linux-gnu/cmake/KF5Config/KF5ConfigConfig.cmake 
(found version "5.107.0")
-- Found KF5CoreAddons: 
/usr/lib/x86_64-linux-gnu/cmake/KF5CoreAddons/KF5CoreAddonsConfig.cmake (found version 
"5.107.0")
-- Found KF5DocTools: /usr/lib/x86_64-linux-gnu/cmake/KF5DocTools/KF5DocToolsConfig.cmake 
(found version "5.107.0")
-- Found KF5I18n: /usr/lib/x86_64-linux-gnu/cmake/KF5I18n/KF5I18nConfig.cmake (found 
version "5.107.0")
-- Found X11: /usr/include
-- Looking for XOpenDisplay in 
/usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so
-- Looking for XOpenDisplay in 
/usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so - found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Found KF5Parts: /usr/lib/x86_64-linux-gnu/cmake/KF5Parts/KF5PartsConfig.cmake (found 
version "5.107.0")
-- Found KF5Plotting: /usr/lib/x86_64-linux-gnu/cmake/KF5Plotting/KF5PlottingConfig.cmake 
(found version "5.107.0")
-- Found KF5UnitConversion: 
/usr/lib/x86_64-linux-gnu/cmake/KF5UnitConversion/KF5UnitConversionConfig.cmake (found 
version "5.107.0")
-- Found KF5WidgetsAddons: 
/usr/lib/x86_64-linux-gnu/cmake/KF5WidgetsAddons/KF5WidgetsAddonsConfig.cmake (found 
version "5.107.0")
-- Found KF5: success (found suitable version "5.107.0", minimum required is 
"5.90.0") found 

Processed: reassign 1068666 to ghc, forcibly merging 1068586 1068666

[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 haskell-fold-debounce/0.2.0.11-1.
Ignoring request to alter fixed versions of bug #1068666 to the same values 
previously set
> forcemerge 1068586 1068666
Bug #1068586 {Done: Ilias Tsitsimpis } [ghc] ghc: Broken 
on arm{el,hf} because of time_t transition
Bug #1068664 {Done: Ilias Tsitsimpis } [ghc] 
haskell-filestore: FTBFS on arm{el,hf}: Total Cases: 42  Tried: 42  Errors: 1  
Failures: 1
Bug #1068666 [ghc] haskell-fold-debounce: FTBFS on arm{el,hf}: 14 examples, 2 
failures
Severity set to 'grave' from 'serious'
1036884 was blocked by: 1067508 1067175 1067676 1055530 1067494 1065790 1065940 
1067190 1067069 1067677 1068664 1067170 1067458 1067916 1067509 1068068 1067561 
1066134 1068327 1066049 1065787 1065816 1067189 1062847 1067829 1065725 1067192 
1067171 1068325 1067288 1066328 1055352 1068078 1068160 1068586 1067272 1065973 
1067193 1066794
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1068666
Marked Bug as done
Marked as fixed in versions ghc/9.4.7-5.
Marked as found in versions ghc/9.4.7-4.
Bug #1068664 {Done: Ilias Tsitsimpis } [ghc] 
haskell-filestore: FTBFS on arm{el,hf}: Total Cases: 42  Tried: 42  Errors: 1  
Failures: 1
Merged 1068586 1068664 1068666
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1036884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884
1068586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068586
1068664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068664
1068666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pkcs11-provider
Version: 0.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=pkcs11-provider=ppc64el=0.3-1%2Bb2=1712517987=0

...
FAIL: basic-softhsm
===

Executing ./tbasic

## Raw Sign check error
 openssl 
pkeyutl -sign -inkey "${BASEURI}"
  -pkeyopt pad-mode:none
  -in ${TMPPDIR}/64Brandom.bin
  -out ${TMPPDIR}/raw-sig.bin
Public Key operation error
00493C8EFF7F:error:027A:rsa routines:p11prov_sig_operate:data too small 
for key size:signature.c:894:


## Sign and Verify with provided Hash and RSA
 openssl dgst -sha256 -binary -out ${TMPPDIR}/sha256.bin ${SEEDFILE}

 openssl 
pkeyutl -sign -inkey "${PRIURI}"
  -in ${TMPPDIR}/sha256.bin
  -out ${TMPPDIR}/sha256-sig.bin

 openssl 
pkeyutl -verify -inkey "${PUBURI}"
-pubin
-in ${TMPPDIR}/sha256.bin
-sigfile ${TMPPDIR}/sha256-sig.bin
Signature Verified Successfully

## Sign and Verify with provided Hash and RSA with DigestInfo struct
 openssl dgst -sha256 -binary -out ${TMPPDIR}/sha256.bin ${SEEDFILE}

 openssl 
pkeyutl -sign -inkey "${PRIURI}" -pkeyopt digest:sha256
  -in ${TMPPDIR}/sha256.bin
  -out ${TMPPDIR}/sha256-sig.bin

 openssl 
pkeyutl -verify -inkey "${PUBURI}" -pkeyopt digest:sha256
-pubin
-in ${TMPPDIR}/sha256.bin
-sigfile ${TMPPDIR}/sha256-sig.bin
Signature Verified Successfully

## DigestSign and DigestVerify with RSA
 openssl 
pkeyutl -sign -inkey "${BASEURI}"
  -digest sha256
  -in ${RAND64FILE}
  -rawin
  -out ${TMPPDIR}/sha256-dgstsig.bin

 openssl 
pkeyutl -verify -inkey "${BASEURI}" -pubin
-digest sha256
-in ${RAND64FILE}
-rawin
-sigfile ${TMPPDIR}/sha256-dgstsig.bin
Signature Verified Successfully
 openssl 
pkeyutl -verify -inkey "${PUBURI}"
-pubin
-digest sha256
-in ${RAND64FILE}
-rawin
-sigfile ${TMPPDIR}/sha256-dgstsig.bin
Signature Verified Successfully
RSA basic encrypt and decrypt
 openssl 
pkeyutl -encrypt -inkey "${PUBURI}" -pubin
 -in ${SECRETFILE}
 -out ${SECRETFILE}.enc

 openssl 
pkeyutl -decrypt -inkey "${PRIURI}"
 -in ${SECRETFILE}.enc
 -out ${SECRETFILE}.dec


## Test Disallow Public Export
 openssl pkey -in $PUBURI -pubin -pubout -text

## Test CSR generation from RSA private keys
 openssl 
req -new -batch -key "${PRIURI}" -out ${TMPPDIR}/rsa_csr.pem

 openssl 
req -in ${TMPPDIR}/rsa_csr.pem -verify -noout
Certificate request self-signature verify OK

## Test fetching public keys without PIN in config files
 openssl pkey -in $PUBURI -pubin -pubout -out ${TMPPDIR}/rsa.pub.nopin.pem

 openssl pkey -in $ECPUBURI -pubin -pubout -out ${TMPPDIR}/ec.pub.nopin.pem

 openssl pkey -in $ECXPUBURI -pubin -pubout -out ${TMPPDIR}/ecx.pub.nopin.pem


## Test fetching public keys with a PIN in URI
 openssl pkey -in $BASEURIWITHPIN -pubin -pubout -out 
${TMPPDIR}/rsa.pub.uripin.pem

 openssl pkey -in $ECBASEURIWITHPIN -pubin -pubout -out 
${TMPPDIR}/ec.pub.uripin.pem

 openssl pkey -in $ECXBASEURIWITHPIN -pubin -pubout -out 
${TMPPDIR}/ecx.pub.uripin.pem


## Test prompting without PIN in config files

## Test EVP_PKEY_eq on public RSA key both on token

## Test EVP_PKEY_eq on public EC key both on token

## Test EVP_PKEY_eq on public explicit EC key both on token
Failed to load key from URI: pkcs11:type=public;id=%00%07

FAIL basic-softhsm.t (exit status: 1)
...

Testsuite summary for pkcs11-provider 0.3

# TOTAL: 34
# PASS:  15
# SKIP:  18
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to s...@redhat.com

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

[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 dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1067636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nodejs
Version: 18.19.1+dfsg-6
Severity: important
Tags: sid
control: affects -1 src:openssl
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-3.2

Hi,

I rebuilt nodejs in unstable against openssl 3.2 in experimental an a
few tests failed:

| Failed tests:
| ./node /<>/test/parallel/test-crypto-rsa-dsa.js
| ./node /<>/test/parallel/test-tls-alert-handling.js
| ./node /<>/test/parallel/test-tls-client-auth.js
| ./node /<>/test/parallel/test-tls-empty-sni-context.js
| ./node --expose-internals 
/<>/test/parallel/test-tls-enable-trace.js
| ./node --expose-internals 
/<>/test/parallel/test-tls-enable-trace-cli.js
| ./node /<>/test/parallel/test-tls-getcipher.js
| ./node /<>/test/parallel/test-tls-junk-server.js
| ./node /<>/test/parallel/test-tls-psk-circuit.js
| ./node /<>/test/parallel/test-tls-set-ciphers.js
| ./node /<>/test/parallel/test-tls-junk-closes-server.js

Any idea how to proceed?
I've been reading https://github.com/nodejs/node/issues/51152 but I
don't think 3.2 support has been integrated somewhere as they just
discussed their fork part and so on.

I've been looking at the errors and some are "error code changed". I
*think* the trace errors changed also slightly. I don't know why
get/set-ciphers failed.

Sebastian
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 18.20.1+dfsg-2
Done: Jérémy Lal 

We believe that the bug you reported is fixed in the latest version of
nodejs, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated nodejs package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 13 Apr 2024 19:42:32 +0200
Source: nodejs
Architecture: source
Version: 18.20.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Closes: 1067636
Changes:
 nodejs (18.20.1+dfsg-2) unstable; urgency=medium
 .
   * openssl 3.2 compatibility patch (Closes: #1067636)
 TLS server no longer closes client connection when client
 writes junk.
Checksums-Sha1:
 12d1f54b33f3fa0e3828758122c4eec868d258d8 4359 nodejs_18.20.1+dfsg-2.dsc
 dc5f999d73ac66e253c5af7595fb8398dfafe9ef 164524 
nodejs_18.20.1+dfsg-2.debian.tar.xz
 25161775d02f26f7dd5f6a2cfedf1b438f152274 10910 
nodejs_18.20.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 4b14b510b04c3dd3e44deb9719651260c4e99ac545018e74c52840e56ab97f6c 4359 
nodejs_18.20.1+dfsg-2.dsc
 154a9e978b1d0ec5f48f9481932748b40ee0c32b7bd029a32cdc514ba79bc700 164524 
nodejs_18.20.1+dfsg-2.debian.tar.xz
 cabbef030b017c9a237177d4c8e90b9a9c0401080843313a07d63aeddcd14f2a 10910 
nodejs_18.20.1+dfsg-2_source.buildinfo
Files:
 01713eab07d531491e9401956d2b2b4d 4359 javascript optional 
nodejs_18.20.1+dfsg-2.dsc
 34596891d820f011aa801abaf65b5492 164524 javascript optional 
nodejs_18.20.1+dfsg-2.debian.tar.xz
 bee0a56235fc784f010620af4c6fcf27 10910 javascript optional 
nodejs_18.20.1+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmYaxDQSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0eLMP/jPfsGpQWDiyKKuJdhhA1lyLzBTbK5Cc
x0jtY0Jsj239NCJTjHHS+h30mfg8uSgUjte1M2xbBVwFeK3YBgNLyiQzR0K5jSyb
f/P2H5mqL+Lu7KbmeFISBwhkC27DsrNGGSUF+53f8X37d5JL7/6cfkn0lsP9nlaA
tEmgA6OfWjHiEXHOODls2OjsAdYv/y/k51lfWmRqdN79YeUyXYjCQKL1h2QDJKiG
9+z6EpxsfJXqKKmklYdy+pGXsKgQl5yD5kWE+NS8bznqenduCrsJmo1HkmRc3a63
71Pm/JrZDl5WPuc4my8AdMCRngx+Ggwn8rZhBc6IWwHAMZk+tGEAhWQsDpawGT/x
t5KKVzgmDbRtRmfyYa6Hbahqhp9ix6/4hZG04+ElTW6OiP2X0Ovds9LT+p1ghVXr
/pycDELhdF1/Ss63fk5VGdhi+xMoQonYs1/I9Aov4bzN5J/3FGcthVBpGtI3mvZS
zKxsLEAnBlfMlpQGgu+/Lafucp2qX69xm0uokUqhmzwspDzjNmbzsovS0qv8yZB2

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

[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 the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 or
directory, mu4e" when trying to load the mu4e library (using
use-package).

It seems that some files are missing (mu4e.el at least).
Package version 1.12.3-2:
$ dpkg -L mu4e
/.
/usr
/usr/lib
/usr/lib/emacsen-common
/usr/lib/emacsen-common/packages
/usr/lib/emacsen-common/packages/compat
/usr/lib/emacsen-common/packages/compat/mu4e
/usr/lib/emacsen-common/packages/install
/usr/lib/emacsen-common/packages/install/mu4e
/usr/lib/emacsen-common/packages/remove
/usr/lib/emacsen-common/packages/remove/mu4e
/usr/share
/usr/share/doc
/usr/share/doc/mu4e
/usr/share/doc/mu4e/NEWS.Debian.gz
/usr/share/doc/mu4e/changelog.Debian.gz
/usr/share/doc/mu4e/copyright
/usr/share/emacs
/usr/share/emacs/site-lisp
/usr/share/emacs/site-lisp/elpa-src
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3/mu4e-autoloads.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3/mu4e-config.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3/mu4e-pkg.el
/usr/share/info
/usr/share/info/mu4e.info.gz
/usr/share/doc/mu4e/NEWS.org
/usr/share/doc/mu4e/README.org.gz
/usr/share/doc/mu4e/TODO.gz
/etc/emacs/site-start.d/50mu4e.el

Package version 1.10.8-2:
$ dpkg -L mu4e
/.
/usr
/usr/lib
/usr/lib/emacsen-common
/usr/lib/emacsen-common/packages
/usr/lib/emacsen-common/packages/compat
/usr/lib/emacsen-common/packages/compat/mu4e
/usr/lib/emacsen-common/packages/install
/usr/lib/emacsen-common/packages/install/mu4e
/usr/lib/emacsen-common/packages/remove
/usr/lib/emacsen-common/packages/remove/mu4e
/usr/share
/usr/share/doc
/usr/share/doc/mu4e
/usr/share/doc/mu4e/NEWS.Debian.gz
/usr/share/doc/mu4e/changelog.Debian.gz
/usr/share/doc/mu4e/changelog.gz
/usr/share/doc/mu4e/copyright
/usr/share/emacs
/usr/share/emacs/site-lisp
/usr/share/emacs/site-lisp/elpa-src
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-actions.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-autoloads.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-bookmarks.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-compose.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-config.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-contacts.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-context.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-contrib.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-draft.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-folders.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-headers.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-helpers.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-icalendar.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-lists.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-main.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-mark.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-message.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-modeline.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-notification.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-obsolete.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-org.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-pkg.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-query-items.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-search.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-server.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-speedbar.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-update.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-vars.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-view.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-window.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e.el
/usr/share/info
/usr/share/info/mu4e.info.gz

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

[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 Tracking System
Contact ow...@bugs.debian.org with problems

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

[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:

https://salsa.debian.org/go-team/packages/golang-github-antonini-golibjpegturbo/-/commit/89752d43ce3b10f0eb71d96c4cec77b5b97b3937


Use local image for decode_encode_test

Closes: #1068497


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068497

Processed: Bug#1068403 marked as pending in mariadb

[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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#1068403 marked as pending in mariadb

[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
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#1068404 marked as pending in mariadb

[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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#1068404 marked as pending in mariadb

[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 ow...@bugs.debian.org with problems

Bug#1068404: marked as pending in mariadb

[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:

https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/cd90d81520fd2211bd4b47c11ad51bac9618b8e2


Remove direct dependencies on libcurl4 (Closes: #1068403, #1068404)

There is no libcurl4 package in Debian anymore since the transition to
libcurl4t64. Instead of updating the dependency to new package name,
remove it completely and rely on automatic shlibs:Depends to include it.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068404

Bug#1068404: marked as pending in mariadb

[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:

https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/cd90d81520fd2211bd4b47c11ad51bac9618b8e2


Remove direct dependencies on libcurl4 (Closes: #1068403, #1068404)

There is no libcurl4 package in Debian anymore since the transition to
libcurl4t64. Instead of updating the dependency to new package name,
remove it completely and rely on automatic shlibs:Depends to include it.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068404

Bug#1068403: marked as pending in mariadb

[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:

https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/cd90d81520fd2211bd4b47c11ad51bac9618b8e2


Remove direct dependencies on libcurl4 (Closes: #1068403, #1068404)

There is no libcurl4 package in Debian anymore since the transition to
libcurl4t64. Instead of updating the dependency to new package name,
remove it completely and rely on automatic shlibs:Depends to include it.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068403

Bug#1068403: marked as pending in mariadb

[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:

https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/cd90d81520fd2211bd4b47c11ad51bac9618b8e2


Remove direct dependencies on libcurl4 (Closes: #1068403, #1068404)

There is no libcurl4 package in Debian anymore since the transition to
libcurl4t64. Instead of updating the dependency to new package name,
remove it completely and rely on automatic shlibs:Depends to include it.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068403

Bug#1068217: [Debichem-devel] Bug#1068217: atomes: diff for NMU version 1.1.14-1.1

[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.


Thanks for looking at it. I'm glad you could build successfully without 
this dependency, thanks for uploading.




Cheers




Best,

--
Pierre


OpenPGP_signature.asc
Description: OpenPGP digital signature

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

[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
-- 
Sebastian Ramacher

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

[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 problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1068646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyorbital
Version: 1.8.2-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

the pyorbital package has an autopkgtest regression on i386 only with
NumPy 1.26.4. Hopefully relevant excerpt from test log at
https://ci.debian.net/data/autopkgtest/testing/i386/p/pyorbital/45030100/log.gz
follows:


  127s === FAILURES 
  ===
  127s _ TestGetObserverLook.test_basic_dask 
__
  127s
  127s self = 
  127s
  127s def test_basic_dask(self):
  127s """Test with dask array inputs"""
  127s from pyorbital import orbital
  127s import dask.array as da
  127s sat_lon = da.from_array(self.sat_lon, chunks=2)
  127s sat_lat = da.from_array(self.sat_lat, chunks=2)
  127s sat_alt = da.from_array(self.sat_alt, chunks=2)
  127s lon = da.from_array(self.lon, chunks=2)
  127s lat = da.from_array(self.lat, chunks=2)
  127s alt = da.from_array(self.alt, chunks=2)
  127s azi, elev = orbital.get_observer_look(sat_lon, sat_lat,
  127s   sat_alt, self.t,
  127s   lon, lat, alt)
  127s >   np.testing.assert_allclose(azi.compute(), self.exp_azi)
  127s
  127s /usr/lib/python3/dist-packages/pyorbital/tests/test_orbital.py:259:
  127s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _
  127s
  127s args = (.compare at 0xf0c0cf28>, 
array([[331.00275902, 330.95954165, 180.,  86.4354...00275902, 
330.95954165, 180.,  86.435411  ],
  127s[330.91642994, 180.,   0., 273.232073  ]]))
  127s kwds = {'equal_nan': True, 'err_msg': '', 'header': 'Not equal to 
tolerance rtol=1e-07, atol=0', 'verbose': True}
  127s
  127s @wraps(func)
  127s def inner(*args, **kwds):
  127s with self._recreate_cm():
  127s >   return func(*args, **kwds)
  127s E   AssertionError:
  127s E   Not equal to tolerance rtol=1e-07, atol=0
  127s E
  127s E   Mismatched elements: 1 / 8 (12.5%)
  127s E   Max absolute difference: 14.03624347
  127s E   Max relative difference: 0.07797913
  127s Ex: array([[331.002759, 330.959542, 180.  ,  86.435411],
  127s E  [330.91643 , 165.963757,   0.  , 273.232073]])
  127s Ey: array([[331.002759, 330.959542, 180.  ,  86.435411],
  127s E  [330.91643 , 180.  ,   0.  , 273.232073]])
  127s
  127s /usr/lib/python3.11/contextlib.py:81: AssertionError
  127s _ TestGetObserverLook.test_basic_numpy 
_
  127s
  127s self = 
  127s
  127s def test_basic_numpy(self):
  127s """Test with numpy array inputs"""
  127s from pyorbital import orbital
  127s azi, elev = orbital.get_observer_look(self.sat_lon, self.sat_lat,
  127s   self.sat_alt, self.t,
  127s   self.lon, self.lat, 
self.alt)
  127s >   np.testing.assert_allclose(azi, self.exp_azi)
  127s
  127s /usr/lib/python3/dist-packages/pyorbital/tests/test_orbital.py:243:
  127s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _
  127s
  127s args = (.compare at 0xf0abaf28>, 
array([[331.00275902, 330.95954165, 180.,  86.4354...00275902, 
330.95954165, 180.,  86.435411  ],
  127s[330.91642994, 180.,   0., 273.232073  ]]))
  127s kwds = {'equal_nan': True, 'err_msg': '', 'header': 'Not equal to 
tolerance rtol=1e-07, atol=0', 'verbose': True}
  127s
  127s @wraps(func)
  127s def inner(*args, **kwds):
  127s with self._recreate_cm():
  127s >   return func(*args, **kwds)
  127s E   AssertionError:
  127s E   Not equal to tolerance rtol=1e-07, atol=0
  127s E
  127s E   Mismatched elements: 1 / 8 (12.5%)
  127s E   Max absolute difference: 14.03624347
  127s E   Max 

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

[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 enough version of
GTK 3.

Cheers
-- 
Sebastian Ramacher

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

[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.

  https://ci.debian.net/packages/p/perl/unstable/amd64/45047732/

autopkgtest [15:18:55]: test control: prove debian/t/control.t
autopkgtest [15:18:55]: test control: [---
control.t: warning: can't parse dependency ${t64:Provides}

#   Failed test 'Breaks for libfilter-perl in libperl5.38t64 implies 
Provides'
#   at debian/t/control.t line 267.

#   Failed test 'Breaks for libfilter-perl in libperl5.38t64 implies 
Replaces'
#   at debian/t/control.t line 269.
Use of uninitialized value $replaced_version in substitution (s///) at 
debian/t/control.t line 273.

[...]

The main issue is solved with just a

  sed -i 's/libperl5.38//' debian/t/control.t

but there's also the "can't parse dependency ${t64:Provides}" warning
coming from Dpkg::Deps which cannot handle unsubstituted substvars. We
already fix a similar ${perlapi:Provides} case, so that can be extended
to tackle this as well.

Patch attached. The test passes for me with this on amd64 at least.
-- 
Niko Tyni   nt...@debian.org
>From 81649053d3b4ecf857977c797100c024a25c04de Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Sat, 13 Apr 2024 20:51:17 +0300
Subject: [PATCH] Fix autopkgtest test after t64 changes

---
 debian/t/control.t | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/debian/t/control.t b/debian/t/control.t
index 977338ee5..56608ea4e 100755
--- a/debian/t/control.t
+++ b/debian/t/control.t
@@ -77,7 +77,7 @@ my %known_epochs = (
 # Replaces+Provides
 my %triplet_check_skip = (
 	"perl-base" => [ "libfile-spec-perl" ],
-	"libperl5.38" => [ "libfilter-perl" ],
+	"libperl5.38t64" => [ "libfilter-perl" ],
 );
 
 # list special cases where the name of the Debian package does not
@@ -162,8 +162,8 @@ for my $perl_package_info ($control->get_packages) {
 	for my $deptype ($breaksname, "Replaces", "Provides") {
 		next if !exists $perl_package_info->{$deptype};
 
-		# Dpkg::Deps cannot parse unsubstituted substvars so remove this
-		$perl_package_info->{$deptype} =~ s/\$\{perlapi:Provides}//;
+		# Dpkg::Deps cannot parse unsubstituted substvars so remove those
+		$perl_package_info->{$deptype} =~ s/\$\{\w+:Provides}//;
 
 		my $parsed = deps_parse($perl_package_info->{$deptype});
 		next if !defined $parsed;
-- 
2.39.2

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

[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 on 32-bit non-i386 architectures.
Added tag(s) pending.

-- 
1068688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 tpm2-initramfs-tool-0.2.2/debian/changelog tpm2-initramfs-tool-0.2.2/debian/changelog
--- tpm2-initramfs-tool-0.2.2/debian/changelog	2020-12-28 08:26:11.0 +0100
+++ tpm2-initramfs-tool-0.2.2/debian/changelog	2024-04-13 19:49:00.0 +0200
@@ -1,3 +1,11 @@
+tpm2-initramfs-tool (0.2.2-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * debian/control: Remove hard-coded dependency on libtss2-esys-3.0.0-0
+(Closes: #1068688)
+
+ -- Sebastian Ramacher   Sat, 13 Apr 2024 19:49:00 +0200
+
 tpm2-initramfs-tool (0.2.2-2) unstable; urgency=medium
 
   * Bump version and bump standards-version to 4.5.1.
diff -Nru tpm2-initramfs-tool-0.2.2/debian/control tpm2-initramfs-tool-0.2.2/debian/control
--- tpm2-initramfs-tool-0.2.2/debian/control	2020-12-28 08:26:11.0 +0100
+++ tpm2-initramfs-tool-0.2.2/debian/control	2024-04-13 19:48:43.0 +0200
@@ -22,7 +22,7 @@
 Architecture: linux-any
 Depends: ${misc:Depends},
  ${shlibs:Depends},
- libtss2-esys-3.0.2-0 (>= 3.0.3-1)
+ ${lib:Depends}
 Description: Tool used in initramfs to seal/unseal FDE key to the TPM
  This package provides the TPM tool used by the initramfs.
  Its purpose is to generate/seal/unseal the FDE encrypytion key into

Processed: atomes: diff for NMU version 1.1.14-1.1

[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) pending.

-- 
1068217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 atomes-1.1.14/debian/changelog
--- atomes-1.1.14/debian/changelog	2024-03-20 15:40:00.0 +0100
+++ atomes-1.1.14/debian/changelog	2024-04-13 19:42:07.0 +0200
@@ -1,3 +1,11 @@
+atomes (1.1.14-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Removed hard-coded dependency on libgtk-3-0 (Closes:
+#1068217)
+
+ -- Sebastian Ramacher   Sat, 13 Apr 2024 19:42:07 +0200
+
 atomes (1.1.14-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru atomes-1.1.14/debian/control atomes-1.1.14/debian/control
--- atomes-1.1.14/debian/control	2024-03-20 15:40:00.0 +0100
+++ atomes-1.1.14/debian/control	2024-04-13 19:41:16.0 +0200
@@ -30,7 +30,6 @@
 Architecture: any
 Depends: atomes-data (= ${source:Version}),
  ${shlibs:Depends}, ${misc:Depends},
- libgtk-3-0,
  libglu1-mesa,
  bash-completion
 Description: atomic-scale 3D modeling toolbox

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

[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 the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: supercollider
Version: 1:3.13.0+repack-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
supercollider as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

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 in time.  Therefore I have prepared a 0-day NMU for supercollider
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru supercollider-3.13.0+repack/debian/changelog 
supercollider-3.13.0+repack/debian/changelog
--- supercollider-3.13.0+repack/debian/changelog2023-02-27 
10:22:05.0 +
+++ supercollider-3.13.0+repack/debian/changelog2024-02-05 
16:28:18.0 +
@@ -1,3 +1,10 @@
+supercollider (1:3.13.0+repack-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Mon, 05 Feb 2024 16:28:18 +
+
 supercollider (1:3.13.0+repack-1) unstable; urgency=medium
 
   * New upstream version 3.13.0+repack
diff -Nru supercollider-3.13.0+repack/debian/control 
supercollider-3.13.0+repack/debian/control
--- supercollider-3.13.0+repack/debian/control  2023-02-27 10:03:45.0 
+
+++ supercollider-3.13.0+repack/debian/control  2024-02-05 16:28:18.0 
+
@@ -148,7 +148,10 @@
  Server.supernova call before starting the server. This server does not work
  on i486 or i586 processors.
 
-Package: libscsynth1
+Package: libscsynth1t64
+Provides: ${t64:Provides}
+Replaces: libscsynth1
+Breaks: libscsynth1 (<< ${source:Version})
 Architecture: any
 Depends:
  ${misc:Depends},
diff -Nru supercollider-3.13.0+repack/debian/libscsynth1.install 
supercollider-3.13.0+repack/debian/libscsynth1.install
--- supercollider-3.13.0+repack/debian/libscsynth1.install  2022-11-27 
12:28:26.0 +
+++ supercollider-3.13.0+repack/debian/libscsynth1.install  1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/libscsynth.so.1*
diff -Nru supercollider-3.13.0+repack/debian/libscsynth1t64.install 
supercollider-3.13.0+repack/debian/libscsynth1t64.install
--- supercollider-3.13.0+repack/debian/libscsynth1t64.install   1970-01-01 
00:00:00.0 +
+++ supercollider-3.13.0+repack/debian/libscsynth1t64.install   2022-11-27 
12:28:26.0 +
@@ -0,0 +1 @@
+usr/lib/libscsynth.so.1*
diff -Nru supercollider-3.13.0+repack/debian/libscsynth1t64.lintian-overrides 

Processed: 1068420

[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 processing here.

Please contact me if you need assistance.
-- 
1068420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 it can't be autoremoved from
testing, making it a blocker the time64 transition.

Is there someone who can step up and fix kalzium? or should
it be dropped from the metapackages so it can be removed from testing?

Metapackages built from the meta-kde source (key, hard dependencies)

* kdeedu

Metapackages built from the debian-edu source (key, but only reccomends):

* education-chemistry
* education-highschool
* education-primaryschool
* education-secondaryschool

Metapackages built from the debian-science source (not key, only reccomends):

* science-chemistry

Metapackages built from the debichem source (not key, only reccomends):

* debichem-visualisation

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

[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 Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ramond-0.5/debian/patches/0001-Daemonize-ramond-by-default.patch 
ramond-0.5/debian/patches/0001-Daemonize-ramond-by-default.patch
--- ramond-0.5/debian/patches/0001-Daemonize-ramond-by-default.patch
2020-09-09 13:09:14.0 -0700
+++ ramond-0.5/debian/patches/0001-Daemonize-ramond-by-default.patch
2024-04-13 09:50:06.0 -0700
@@ -8,10 +8,10 @@
  src/main.h |1 +
  2 files changed, 80 insertions(+), 2 deletions(-)
 
-diff --git a/src/main.c b/src/main.c
-index 0cb6e8a..3c4543d 100644
 a/src/main.c
-+++ b/src/main.c
+Index: ramond-0.5/src/main.c
+===
+--- ramond-0.5.orig/src/main.c
 ramond-0.5/src/main.c
 @@ -1,6 +1,5 @@
  #include "main.h"
  #include "log.h"
@@ -19,7 +19,7 @@
  apr_pool_t *masterPool;
  struct configuration *config;
  
-@@ -14,8 +13,9 @@ void listRules(void);
+@@ -14,8 +13,9 @@
  
  void usage(char *prog_name)
  {
@@ -30,7 +30,7 @@
fprintf(stderr, "   -c : path to config file.\n");
  }
  
-@@ -824,11 +824,74 @@ void rafixd_clearRoute(struct ra_info *data)
+@@ -824,11 +824,74 @@
pcap_close(fd);
  }
  
@@ -81,7 +81,7 @@
 +  pidfile = open("/var/run/ramond.pid", O_RDWR|O_CREAT, 0640);
 +  if(pidfile < 0)
 +  exit(EXIT_FAILURE);
-+  if(flock(pidfile, F_TLOCK, 0) < 0)
++  if(lockf(pidfile, F_TLOCK, 0) < 0)
 +  exit(EXIT_SUCCESS);
 +
 +  sprintf(pidstr, "%d\n", getpid());
@@ -105,7 +105,7 @@
if(argc > 6)
{
usage(argv[0]);
-@@ -842,6 +905,20 @@ int main(int argc, char *argv[])
+@@ -842,6 +905,20 @@
  
signal(SIGCHLD, sigchld_handler);
  
@@ -126,10 +126,10 @@
/* Find the config file */
if(!parseConfigFile(argc,argv))
{
-diff --git a/src/main.h b/src/main.h
-index 26de811..6552d5b 100644
 a/src/main.h
-+++ b/src/main.h
+Index: ramond-0.5/src/main.h
+===
+--- ramond-0.5.orig/src/main.h
 ramond-0.5/src/main.h
 @@ -1,5 +1,6 @@
  #include 
  #include 
diff -Nru ramond-0.5/debian/patches/no-implicit-declarations.patch 
ramond-0.5/debian/patches/no-implicit-declarations.patch
--- ramond-0.5/debian/patches/no-implicit-declarations.patch1969-12-31 
16:00:00.0 -0800
+++ ramond-0.5/debian/patches/no-implicit-declarations.patch2024-04-13 
09:50:06.0 -0700
@@ -0,0 +1,29 @@
+Description: fix missing function declarations.
+Author: Steve Langasek 
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/2061024
+Bug-Debian: https://bugs.debian.org/1066551
+Last-Update: 2024-04-13
+Forwarded: no
+
+Index: ramond-0.5/src/log.h
+===
+--- ramond-0.5.orig/src/log.h
 ramond-0.5/src/log.h
+@@ -25,4 +25,6 @@
+ 
+ FILE *log_file;
+ 
++void LOG(const char *fmt, ...);
++
+ #endif
+Index: ramond-0.5/src/main.c
+===
+--- ramond-0.5.orig/src/main.c
 ramond-0.5/src/main.c
+@@ -1,3 +1,6 @@
++#include 
++#include 
++
+ #include "main.h"
+ #include "log.h"
+ apr_pool_t *masterPool;
diff -Nru ramond-0.5/debian/patches/series ramond-0.5/debian/patches/series
--- ramond-0.5/debian/patches/series2022-04-20 16:48:49.0 -0700
+++ ramond-0.5/debian/patches/series2024-04-13 09:48:15.0 -0700
@@ -4,3 +4,4 @@
 0004-Honor-CFLAGS-CPPFLAGS-and-LDFLAGS.patch
 compiler.patch
 libxml2.patch
+no-implicit-declarations.patch

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

[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 Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 doesn't use libargon2 anymore, so that shouldn't be
needed.

-- 
Guilhem.


signature.asc
Description: PGP signature

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

[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 to fix it is by improving upon the existing patch tsc-workaround.

Error log:

tsc -b .
packages/babel-helper-transform-fixture-test-runner/src/index.ts(131,7): error 
TS2345: Argument of type '{ filename: string; displayErrors: boolean; 
lineOffset: number; cachedData: Buffer; }' is not assignable to parameter of 
type 'string | ScriptOptions'.
  Object literal may only specify known properties, and 'displayErrors' does 
not exist in type 'ScriptOptions'.
packages/babel-helper-transform-fixture-test-runner/src/index.ts(139,7): error 
TS2345: Argument of type '{ filename: string; displayErrors: boolean; 
lineOffset: number; cachedData: Buffer; produceCachedData: true; }' is not 
assignable to parameter of type 'string | ScriptOptions'.
  Object literal may only specify known properties, and 'displayErrors' does 
not exist in type 'ScriptOptions'.
make[1]: *** [debian/rules:68: override_dh_auto_build] Error 1



-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages node-babel7 depends on:
ii  node-ampproject-remapping   2.2.0+~cs5.15.37-1
ii  node-babel-plugin-add-module-exports1.0.4+dfsg1~cs5.8.0-4
ii  node-babel-plugin-polyfill-corejs2  0.3.3~0~20220913+ds1-1
ii  node-babel-plugin-polyfill-corejs3  0.6.0~0~20220913+ds1-1
ii  node-babel-plugin-polyfill-regenerator  0.4.1~0~20220913+ds1-1
ii  node-babel7-runtime 7.20.15+ds1+~cs214.269.168-6
ii  node-browserslist   4.22.1+~cs6.1.28-1
ii  node-chalk  5.3.0-1
ii  node-clone-deep 4.0.1+~cs7.0.2-1
ii  node-commander  9.4.1-1
ii  node-convert-source-map 1.9.0+~1.5.2-1
ii  node-core-js3.33.2-1
ii  node-core-js-compat 3.33.2-1
ii  node-core-js-pure   3.33.2-1
ii  node-debug  4.3.4+~cs4.1.7-1
ii  node-esutils2.0.3+~2.0.0-1
ii  node-find-cache-dir 3.3.2+~3.2.1-1
ii  node-fs-readdir-recursive   1.1.0+~1.1.0-1
ii  node-glob   8.1.0+~cs8.5.15-1
ii  node-globals13.23.0-1
ii  node-js-tokens  8.0.0-2
ii  node-jsesc  3.0.2+~3.0.1-1
ii  node-json5  2.2.3+dfsg-1
ii  node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-9
ii  node-lodash-packages4.17.21+dfsg+~cs8.31.198.20210220-9
ii  node-make-dir   3.1.0-3
ii  node-quick-lru  6.1.1-4
ii  node-regenerator-transform  0.15.2+~0.10.8-1
ii  node-regexpu-core   5.2.2-3
ii  node-resolve1.22.8+~cs5.34.15-2
ii  node-semver 7.5.4+~7.5.0-2
ii  node-slash  4.0.0-3
ii  node-source-map 0.7.0++dfsg2+really.0.6.1-15
ii  node-source-map-support 0.5.21+ds+~0.5.4-1
ii  node-to-fast-properties 3.0.1-3
ii  node-v8flags3.2.0+~3.1.1-1
ii  nodejs  18.19.1+dfsg-3

node-babel7 recommends no packages.

Versions of packages node-babel7 suggests:
pn  node-babel-plugin-polyfill-es-shims  
pn  node-babel7-debug

-- no debconf information

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

[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 dependency.

> The reason why we do so is that libuv has some changes between version
> that don’t propagate to ABI. I might be able to drop this in unstable
> though and just keep it for backports.

Hello,

does the reported issue actually exist?

I just cannot find the hardcoded dependency in the source package.

ametzler@argenau:/dev/shm//bind9-9.19.21$ dpkg-parsechangelog -SVersion
1:9.19.21-1
ametzler@argenau:/dev/shm//bind9-9.19.21$ grep -r libuv1 debian/
debian/changelog:  * Add libuv1-dev, libcmocka-dev, libedit-dev and zlib1g-dev 
to B-D
debian/control:   libuv1-dev,
(sid)ametzler@argenau:/dev/shm//bind9-9.19.21$ apt-cache show bind9-libs | 
grep -E '^Version|^Dep'
Version: 1:9.19.21-1+b1
Depends: libc6 (>= 2.34), libfstrm0 (>= 0.2.0), libgssapi-krb5-2 (>= 1.17), 
libjemalloc2 (>= 4.0.0), libjson-c5 (>= 0.15), libkrb5-3 (>= 1.6.dfsg.2), 
liblmdb0 (>= 0.9.7), libmaxminddb0 (>= 1.3.0), libnghttp2-14 (>= 1.12.0), 
libprotobuf-c1 (>= 1.0.1), libssl3t64 (>= 3.0.0), liburcu8t64 (>= 0.13.0), 
libuv1t64 (>= 1.38.0), libxml2 (>= 2.7.4), zlib1g (>= 1:1.1.4)

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Processed: fixed 1066454 in 2.44.1-1

[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 Mutex = std::mutex]’: 
recursive inlining
Marked as fixed in versions wpewebkit/2.44.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1066454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1058552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: science.js
Version: 1.9.3+dfsg-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> cat src/core/core.js src/core/ascending.js src/core/constants.js 
> src/core/expm1.js src/core/functor.js src/core/hypot.js src/core/quadratic.js 
> src/core/zeroes.js >> science.core.js
> cat src/lin/lin.js src/lin/decompose.js src/lin/cross.js src/lin/dot.js 
> src/lin/length.js src/lin/normalize.js src/lin/determinant.js 
> src/lin/gaussjordan.js src/lin/inverse.js src/lin/multiply.js 
> src/lin/transpose.js src/lin/tridag.js >> science.lin.js
> cat src/stats/stats.js src/stats/bandwidth.js src/stats/distance.js 
> src/stats/erf.js src/stats/phi.js src/stats/kernel.js src/stats/kde.js 
> src/stats/kmeans.js src/stats/hcluster.js src/stats/iqr.js src/stats/loess.js 
> src/stats/mean.js src/stats/median.js src/stats/mode.js 
> src/stats/quantiles.js src/stats/variance.js src/stats/distribution.js 
> src/stats/distribution/gaussian.js >> science.stats.js
> cat science.core.js science.lin.js science.stats.js >> science.v1.js
> uglifyjs < science.v1.js > science.v1.min.js
> node src/package.js > package.json
> node:internal/modules/package_json_reader:92
> throw error;
> ^
> 
> SyntaxError: Error parsing /<>/package.json: Unexpected end of 
> JSON input
> at parse ()
> at read (node:internal/modules/package_json_reader:79:16)
> at readPackage (node:internal/modules/package_json_reader:140:10)
> at readPackageScope (node:internal/modules/package_json_reader:157:19)
> at shouldUseESMLoader (node:internal/modules/run_main:77:15)
> at Function.executeUserEntryPoint [as runMain] 
> (node:internal/modules/run_main:122:24)
> at node:internal/main/run_main_module:28:49 {
>   path: '/<>/package.json'
> }
> 
> Node.js v18.19.0
> make[2]: *** [Makefile:80: package.json] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/science.js_1.9.3+dfsg-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: science.js
Source-Version: 1.9.3+dfsg-4
Done: Petter Reinholdtsen 

We believe that the bug you reported is fixed in the latest version of
science.js, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1058...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated science.js package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 13 Apr 2024 17:00:11 +0200
Source: science.js
Architecture: source
Version: 1.9.3+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Petter Reinholdtsen 
Closes: 1058552
Changes:
 science.js (1.9.3+dfsg-4) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Update standards version to 

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

[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 used to substitute the standard file
handling types and functions with versions that use 64-bit file
offsets. Similarly _TIME_BITS=64 is used to susbstitute time handling
types and functions with versions that use 64-bit seconds counts.

All of this only applies to 32-bit architectures, on 64-bit
architectures the default types in glibc are 64-bit.

The "time64" transition was implemented by defining _TIME_BITS=64 and
_FILE_OFFSET_BITS=64 by default in both dpkg-buildflags and the compiler.

That's fine for normal code, but tests/src/libsystem.c is not normal
code, it's a file of "test mocks" that override functions in glibc
for testing purposes. If _FILE_OFFSET_BITS=64 is defined, it ends up
trying to override "open64" twice, rather than trying to override both
"open" and "open64"

If we undef _FILE_OFFSET_BITS then we must also undef _TIME_BITS,
otherwise the glibc headers will refuse to compile.

So the patch seems reasonable to me, and since this is only test
code, it appears to be pretty low risk. We would appreciate having
this fix in unstable so the time_t transition can move forward.

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

[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: 
./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'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xwayland
Version: 2:23.2.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> /usr/bin/ld: /tmp/ccL8lXZd.o: in function `main':
> ./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'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/xwayland_23.2.4-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: xwayland
Source-Version: 2:23.2.6-1
Done: Timo Aaltonen 

We believe that the bug you reported is fixed in the latest version of
xwayland, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated xwayland package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 16:58:45 +0300
Source: xwayland
Built-For-Profiles: noudeb
Architecture: source
Version: 2:23.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 1065184
Changes:
 xwayland (2:23.2.6-1) unstable; urgency=medium
 .
   * New upstream release.
 - CVE-2024-31080
 - CVE-2024-31081
 - CVE-2024-31083
   * control: Add libtirpc-dev to build-depends. (Closes: #1065184)
Checksums-Sha1:
 6f803a9969d399ec777d9bf016715807b3bdd2da 2530 xwayland_23.2.6-1.dsc
 8c45b889051bdea66fba51f267374a38b1fd1f49 1300092 xwayland_23.2.6.orig.tar.xz
 f9765cfd191e9210e0669e848075589800316c21 195 xwayland_23.2.6.orig.tar.xz.asc
 eee62a6e27ab952d3e5fd09af1e67f58b192 35864 xwayland_23.2.6-1.debian.tar.xz
 5f6515cae9b5a99b8c0ccba25ab39e198eb87c56 10357 
xwayland_23.2.6-1_source.buildinfo
Checksums-Sha256:
 85bec8f2eb913c3b9494102521154ce3b98edfba646a6c1b49e872d3042d9f8b 2530 
xwayland_23.2.6-1.dsc
 1c9a366b4e7ccadba0f9bd313c59eae12d23bd72543b22a26eaf8b20835cfc6d 1300092 
xwayland_23.2.6.orig.tar.xz
 65d51108cc57f7cd282c86dbc71fa78e1365b738536e5b38847ef08d5dfb8c96 195 
xwayland_23.2.6.orig.tar.xz.asc
 537251328f7c7dad8c804fcb911ae9f784ba6d9cde91de236e898e5379e0297e 35864 
xwayland_23.2.6-1.debian.tar.xz
 3b0c06c46eb764de8233a85d36fa3b539e2a01e078a82773d6e749b3f662692c 10357 
xwayland_23.2.6-1_source.buildinfo
Files:
 24b64125796ac61b40e744de0a66d849 2530 x11 optional xwayland_23.2.6-1.dsc
 8f2bb6789e22b5ea1f1f19694267e539 1300092 x11 optional 
xwayland_23.2.6.orig.tar.xz
 b5091809677b5c57107c6a92f1d34f05 195 x11 optional 
xwayland_23.2.6.orig.tar.xz.asc
 3e91428c04ebd21c1c61fa53ca7abc8c 35864 x11 optional 
xwayland_23.2.6-1.debian.tar.xz
 905dcafe3c1775c7b0f542f1c3bbbc32 10357 x11 optional 
xwayland_23.2.6-1_source.buildinfo

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

[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 been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xwayland
Version: 2:23.2.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-gl...@lists.debian.org
Usertags: libtirpc-dev

Dear maintainer,

Starting with glibc 2.31, support for NIS (libnsl library) has been
moved to a separate libnsl2 package. In order to allow a smooth
transition, a libnsl-dev, which depends on libtirpc-dev, has been added
to the libc6-dev package.

The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1
NMU, as part of the 64-bit time_t transition. This causes xwayland to
FTBFS in sid with:

| Configuring version-config.h using configuration
| Configuring xkb-config.h using configuration
| Configuring xwayland-config.h using configuration
| Run-time dependency glproto found: YES 1.4.17
| Run-time dependency gl found: YES 1.2
| Dependency glproto found: YES 1.4.17 (cached)
| Dependency gl found: YES 1.2 (cached)
| Run-time dependency libtirpc found: NO (tried pkgconfig and cmake)
| Has header "rpc/rpc.h" : NO
| 
| ../os/meson.build:63:8: ERROR: Problem encountered: secure-rpc requested, but 
neither libtirpc or libc RPC support were found
| 
| A full log can be found at 
/<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
| cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt

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 given
its a change we want to do for Trixie, this will only lower the severity
of the bug.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: xwayland
Source-Version: 2:23.2.6-1
Done: Timo Aaltonen 

We believe that the bug you reported is fixed in the latest version of
xwayland, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated xwayland package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 16:58:45 +0300
Source: xwayland
Built-For-Profiles: noudeb
Architecture: source
Version: 2:23.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 1065184
Changes:
 xwayland (2:23.2.6-1) unstable; urgency=medium
 .
   * New upstream release.
 - CVE-2024-31080
 - CVE-2024-31081
 - CVE-2024-31083
   * control: Add libtirpc-dev to build-depends. (Closes: #1065184)
Checksums-Sha1:
 6f803a9969d399ec777d9bf016715807b3bdd2da 2530 xwayland_23.2.6-1.dsc
 8c45b889051bdea66fba51f267374a38b1fd1f49 1300092 xwayland_23.2.6.orig.tar.xz
 f9765cfd191e9210e0669e848075589800316c21 195 xwayland_23.2.6.orig.tar.xz.asc
 eee62a6e27ab952d3e5fd09af1e67f58b192 35864 xwayland_23.2.6-1.debian.tar.xz
 5f6515cae9b5a99b8c0ccba25ab39e198eb87c56 10357 
xwayland_23.2.6-1_source.buildinfo
Checksums-Sha256:
 85bec8f2eb913c3b9494102521154ce3b98edfba646a6c1b49e872d3042d9f8b 2530 
xwayland_23.2.6-1.dsc
 1c9a366b4e7ccadba0f9bd313c59eae12d23bd72543b22a26eaf8b20835cfc6d 1300092 
xwayland_23.2.6.orig.tar.xz
 65d51108cc57f7cd282c86dbc71fa78e1365b738536e5b38847ef08d5dfb8c96 195 
xwayland_23.2.6.orig.tar.xz.asc
 537251328f7c7dad8c804fcb911ae9f784ba6d9cde91de236e898e5379e0297e 35864 
xwayland_23.2.6-1.debian.tar.xz
 3b0c06c46eb764de8233a85d36fa3b539e2a01e078a82773d6e749b3f662692c 10357 
xwayland_23.2.6-1_source.buildinfo
Files:
 24b64125796ac61b40e744de0a66d849 2530 x11 optional xwayland_23.2.6-1.dsc
 8f2bb6789e22b5ea1f1f19694267e539 1300092 x11 optional 
xwayland_23.2.6.orig.tar.xz
 b5091809677b5c57107c6a92f1d34f05 195 x11 optional 
xwayland_23.2.6.orig.tar.xz.asc
 3e91428c04ebd21c1c61fa53ca7abc8c 35864 x11 optional 

Bug#1058552: marked as pending in science.js

[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:

https://salsa.debian.org/js-team/science.js/-/commit/72d4064d48ae6a0f2c0886ea43cf99b1b2ac5754


Fixed build race condition problem.

Patch from James Valleroy.

Closes: #1058552


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058552

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

[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
Contact ow...@bugs.debian.org with problems

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'

[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 merging the bugs. Today a "release to sid" commit was made, 
so this bug will be closed/fixed real soon now.

signature.asc
Description: This is a digitally signed message part.

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

[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: missing build-dep on libtirpc-dev 
Added tag(s) trixie and sid.
Merged 1065184 1066398

-- 
1065184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065184
1066398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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'

[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 #1065184.

> 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.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'