Processed: merging bugs, take two

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1068166 manpages-dev 6.07-1
Bug #1068166 [src:manpages] manpages-dev: Fails to upgrade due to file conflict
Bug reassigned from package 'src:manpages' to 'manpages-dev'.
No longer marked as found in versions manpages/6.7-1.
Ignoring request to alter fixed versions of bug #1068166 to the same values 
previously set
Bug #1068166 [manpages-dev] manpages-dev: Fails to upgrade due to file conflict
There is no source info for the package 'manpages-dev' at version '6.07-1' with 
architecture ''
Unable to make a source version for version '6.07-1'
Marked as found in versions 6.07-1.
> forcemerge 1068166 1068167
Bug #1068166 [manpages-dev] manpages-dev: Fails to upgrade due to file conflict
Bug #1068167 [manpages-dev] manpages-dev: Update to 6.7-1 fails
Severity set to 'serious' from 'important'
There is no source info for the package 'manpages-dev' at version '6.07-1' with 
architecture ''
Unable to make a source version for version '6.07-1'
Marked as found in versions 6.07-1.
Merged 1068166 1068167
> thanks
Stopping processing here.

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

Processed (with 1 error): merging bugs

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 1068167 6.05.01-1
Bug #1068167 [manpages-dev] manpages-dev: Update to 6.7-1 fails
No longer marked as found in versions manpages/6.05.01-1.
> forcemerge 1068166 1068167
Bug #1068166 [src:manpages] manpages-dev: Fails to upgrade due to file conflict
Unable to merge bugs because:
package of #1068167 is 'manpages-dev' not 'src:manpages'
Failed to forcibly merge 1068166: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: Re: Bug#1068166: manpages-dev: Fails to upgrade due to file conflict

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 6.05.01-1
Bug #1068166 [src:manpages] manpages-dev: Fails to upgrade due to file conflict
No longer marked as found in versions manpages/6.05.01-1.
> found -1 6.7-1
Bug #1068166 [src:manpages] manpages-dev: Fails to upgrade due to file conflict
Marked as found in versions manpages/6.7-1.

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

Bug#1068166: manpages-dev: Fails to upgrade due to file conflict

[Sven Joachim]

Control: notfound -1 6.05.01-1
Control: found -1 6.7-1

On 2024-04-01 06:17 +0200, Bas Couwenberg wrote:

> Source: manpages
> Version: 6.05.01-1
> Severity: serious
> Justification: makes the package in question unusable or mostly so
>
> Dear Maintainer,
>
> manpages-dev failed to upgrade due to a conflict with glibc-doc:
>
>  Unpacking manpages-dev (6.7-1) over (6.05.01-1) ...
>  dpkg: error processing archive 
> /var/cache/apt/archives/manpages-dev_6.7-1_all.deb (--unpack):
>   trying to overwrite '/usr/share/man/man3/pthread_cond_init.3.gz', which is 
> also in package glibc-doc 2.37-15.1
>  Errors were encountered while processing:
>   /var/cache/apt/archives/manpages-dev_6.7-1_all.deb
>  E: Sub-process /usr/bin/dpkg returned an error code (1)

There are a few more conflicting files:

,
| # dpkg -i --force-overwrite /var/cache/apt/archives/manpages-dev_6.7-1_all.deb
| (Reading database ... 15705 files and directories currently installed.)
| Preparing to unpack .../manpages-dev_6.7-1_all.deb ...
| Unpacking manpages-dev (6.7-1) ...
| dpkg: warning: overriding problem because --force enabled:
| dpkg: warning: trying to overwrite 
'/usr/share/man/man3/pthread_cond_init.3.gz', which is also in package 
glibc-doc 2.37-15.1
| dpkg: warning: overriding problem because --force enabled:
| dpkg: warning: trying to overwrite 
'/usr/share/man/man3/pthread_condattr_init.3.gz', which is also in package 
glibc-doc 2.37-15.1
| dpkg: warning: overriding problem because --force enabled:
| dpkg: warning: trying to overwrite 
'/usr/share/man/man3/pthread_key_create.3.gz', which is also in package 
glibc-doc 2.37-15.1
| dpkg: warning: overriding problem because --force enabled:
| dpkg: warning: trying to overwrite 
'/usr/share/man/man3/pthread_mutex_init.3.gz', which is also in package 
glibc-doc 2.37-15.1
| dpkg: warning: overriding problem because --force enabled:
| dpkg: warning: trying to overwrite 
'/usr/share/man/man3/pthread_mutexattr_setkind_np.3.gz', which is also in 
package glibc-doc 2.37-15.1
| dpkg: warning: overriding problem because --force enabled:
| dpkg: warning: trying to overwrite '/usr/share/man/man3/pthread_once.3.gz', 
which is also in package glibc-doc 2.37-15.1
`

> Breaks/Replaces will need to be added if the file was moved, but it
> seems that only one of these packages should include this manpage.

There is a script debian/check-conflicts in the manpages source package
which is supposed to detect such clashing files, but it is buggy because
it only scans the contents of amd64 packages, while glibc-doc is an
arch:all package.

Cheers,
   Sven

Bug#1068166: manpages-dev: Fails to upgrade due to file conflict

[Bas Couwenberg]

Source: manpages
Version: 6.05.01-1
Severity: serious
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

manpages-dev failed to upgrade due to a conflict with glibc-doc:

 Unpacking manpages-dev (6.7-1) over (6.05.01-1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/manpages-dev_6.7-1_all.deb (--unpack):
  trying to overwrite '/usr/share/man/man3/pthread_cond_init.3.gz', which is 
also in package glibc-doc 2.37-15.1
 Errors were encountered while processing:
  /var/cache/apt/archives/manpages-dev_6.7-1_all.deb
 E: Sub-process /usr/bin/dpkg returned an error code (1)

Breaks/Replaces will need to be added if the file was moved, but it seems that 
only one of these packages should include this manpage.

Kind Regards,

Bas

Bug#1066674: gramophone2: FTBFS: GRAMophone.c:94:9: error: implicit declaration of function ‘usageError’; did you mean ‘strerror’? [-Werror=implicit-function-declaration]

[Ying-Chun Liu (PaulLiu)]

Hi,

I've fixed the bug. I plan to do NMU to fix this bug.

I'll wait for 10 days if no one says no.
And I'll upload it to delay/10 queue.

The attachment is the debdiff and build log.

Yours,
Paul
diff -Nru gramophone2-0.8.13a/debian/changelog 
gramophone2-0.8.13a/debian/changelog
--- gramophone2-0.8.13a/debian/changelog2022-12-13 05:48:33.0 
+0800
+++ gramophone2-0.8.13a/debian/changelog2024-04-01 05:23:29.0 
+0800
@@ -1,3 +1,14 @@
+gramophone2 (0.8.13a-3.3) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix FTBFS caused by -Werror=implicit-function-declaration
+(Closes: #1066674)
+- Add debian/patches/fix-ftbfs-implicit-function-declaration.patch
+- Update debian/patches/clang_FTBFS.patch
+- Update debian/patches/GRAMophone.y.diff
+
+ -- Ying-Chun Liu (PaulLiu)   Mon, 01 Apr 2024 05:23:29 
+0800
+
 gramophone2 (0.8.13a-3.2) unstable; urgency=low
 
   [ Ying-Chun Liu (PaulLiu)  ]
diff -Nru gramophone2-0.8.13a/debian/patches/clang_FTBFS.patch 
gramophone2-0.8.13a/debian/patches/clang_FTBFS.patch
--- gramophone2-0.8.13a/debian/patches/clang_FTBFS.patch2022-12-13 
05:48:33.0 +0800
+++ gramophone2-0.8.13a/debian/patches/clang_FTBFS.patch2024-04-01 
05:23:29.0 +0800
@@ -1,9 +1,29 @@
 Description: fix FTBFS with clang [-Wreturn-type]
 Author: Nicolas Sévelin-Radiguet 
 Last-Update: 2014-09-06
 a/midifile.c
-+++ b/midifile.c
-@@ -156,7 +156,7 @@
+Index: gramophone2-0.8.13a/midifile.c
+===
+--- gramophone2-0.8.13a.orig/midifile.c
 gramophone2-0.8.13a/midifile.c
+@@ -78,6 +78,17 @@ static int read16bit();
+ static int to16bit();
+ static char *msg();
+ 
++int mferror(char *);
++int readheader();
++int readtrack();
++int chanmessage(int, int, int);
++int msginit();
++int msgadd(int);
++int metaevent(int);
++int sysex();
++int msgleng();
++int badbyte(int);
++
+ /*
+  * Write multi-length bytes to MIDI format files
+  */
+@@ -156,7 +167,7 @@ readheader()   /* read a header chunk */
int format, ntrks, division;
  
if ( readmt("MThd") == EOF )
diff -Nru 
gramophone2-0.8.13a/debian/patches/fix-ftbfs-implicit-function-declaration.patch
 
gramophone2-0.8.13a/debian/patches/fix-ftbfs-implicit-function-declaration.patch
--- 
gramophone2-0.8.13a/debian/patches/fix-ftbfs-implicit-function-declaration.patch
1970-01-01 08:00:00.0 +0800
+++ 
gramophone2-0.8.13a/debian/patches/fix-ftbfs-implicit-function-declaration.patch
2024-04-01 05:23:29.0 +0800
@@ -0,0 +1,84 @@
+Description: Fix FTBFS caused by -Werror=implicit-function-declaration
+ In dpkg 1.22.6, it enabled -Werror=implicit-function-declaration.
+ Thus we need to make sure every function has its definition.
+Bug-Debian: http://bugs.debian.org/1066674
+Author: Ying-Chun Liu (PaulLiu) 
+Last-Update: 2024-04-01
+Index: gramophone2-0.8.13a/midifile.h
+===
+--- gramophone2-0.8.13a.orig/midifile.h
 gramophone2-0.8.13a/midifile.h
+@@ -32,6 +32,11 @@ extern int (*Mf_writetempotrack)();
+ float mf_ticks2sec();
+ unsigned long mf_sec2ticks();
+ void mfwrite();
++int mf_write_midi_event(unsigned long, unsigned int, unsigned int, unsigned 
char *, unsigned long);
++int mf_write_meta_event(unsigned long, unsigned char, unsigned char *, 
unsigned long);
++void mf_write_tempo(unsigned long);
++int eputc(unsigned char);
++int biggermsg();
+ 
+ /* MIDI status commands most significant bit is 1 */
+ #define note_off  0x80
+Index: gramophone2-0.8.13a/global.h
+===
+--- gramophone2-0.8.13a.orig/global.h
 gramophone2-0.8.13a/global.h
+@@ -181,3 +181,33 @@ typedef struct macro_data {
+ } macro;
+ 
+ macro macros[NUM_MACRO];
++
++void usageError(void);
++unsigned int hash(char *v, unsigned char sentinel);
++void initGRAMophone(void);
++void init_local_flag(void);
++void init_player(void);
++int grammyvm();
++void print_local_params(unsigned char i);
++void print_composition_info();
++void print_global_params();
++void sntx_err(unsigned int error, char *msg);
++void dhInsert(pnote_var noteVar, char *text, unsigned char sentinel, unsigned 
char created_by_body);
++pnote_var dhSearch(char *v, unsigned char sentinel);
++char *dhSearch2(char *v);
++void code_update(unsigned int cc, unsigned int _goto);
++void gen_code(unsigned int op, unsigned int op1);
++void gen_code2(unsigned int op);
++void gen_code3(unsigned int op, unsigned type, unsigned op1);
++void gen_code4(unsigned int op, unsigned op1, unsigned op2, unsigned type);
++void gen_note_code(unsigned int op, unsigned int note, unsigned int type1,
++ unsigned int op1, unsigned int type2, unsigned int op2,
++ unsigned int type3, unsigned int op3, unsigned int type4,
++ unsigned int op4);
++void gen_exp1_code(unsigned int op, unsigned int 

Bug#1065768: libauthen-krb5-perl: FTBFS on arm{el,hf}: Krb5.xs:1040:17: error: implicit declaration of function ‘krb5_free_address’; did you mean ‘krb5_free_addresses’? [-Werror=implicit-function-dec

[Russ Allbery]

gregor herrmann  writes:

> I'm by far not any expert on C code and gcc flags; but yes, given the
> above findings and unless someone more knowledgeable steps up in the
> next couple of week, I think we have to remove libauthen-krb5-perl (and
> libauthen-krb5-admin-perl).

Authen::Krb5 has a bunch of stuff that dates from the pre-GSS-API era of
Kerberos, and there were other things that at one point got me to start
writing my own version of the same idea (although alas I never finished).
In theory, one could delete the pieces of the module that try to do things
that no one should really be doing from Perl and the rest of it remains
somewhat useful, but given that upstream has archived the project, I would
go ahead and remove it.

Maybe someday I'll dust off and finish a proper Kerberos Perl module that
uses the modern C API.  In my copius free time.  :)

-- 
Russ Allbery (r...@debian.org)  

Bug#1065768: libauthen-krb5-perl: FTBFS on arm{el,hf}: Krb5.xs:1040:17: error: implicit declaration of function ‘krb5_free_address’; did you mean ‘krb5_free_addresses’? [-Werror=implicit-function-dec

[gregor herrmann]

On Fri, 29 Mar 2024 13:08:43 +0100, Sebastian Ramacher wrote:

> > Not sure there are many chances to fix this (short of disabling
> > -Werror=implicit-function-declaration). Cf. also in Fedora:
> > https://src.fedoraproject.org/rpms/perl-Authen-Krb5/commits/rawhide
> > https://bugzilla.redhat.com/show_bug.cgi?id=2172836
> 
> So should it be removed?

I'm by far not any expert on C code and gcc flags; but yes, given the
above findings and unless someone more knowledgeable steps up in the
next couple of week, I think we have to remove libauthen-krb5-perl
(and libauthen-krb5-admin-perl).

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe


signature.asc
Description: Digital Signature

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1068160 haskell-haskell-gi
Bug #1068160 [src:haskell-gi-glib] haskell-gi-glib: FTBFS on mips64el: couldn't 
find API description for GLib.time_t
Bug reassigned from package 'src:haskell-gi-glib' to 'haskell-haskell-gi'.
No longer marked as found in versions haskell-gi-glib/2.0.29-1.
Ignoring request to alter fixed versions of bug #1068160 to the same values 
previously set
> forcemerge 1067272 1068160
Bug #1067272 {Done: Ilias Tsitsimpis } 
[haskell-haskell-gi] haskell-gi-glib: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1
Bug #1068160 [haskell-haskell-gi] haskell-gi-glib: FTBFS on mips64el: couldn't 
find API description for GLib.time_t
Set Bug forwarded-to-address to 
'https://github.com/haskell-gi/haskell-gi/pull/430'.
1036884 was blocked by: 1067916 1067829 1067171 1067677 1067561 1065787 1065973 
1067189 1062847 1068068 1067193 1067458 1067288 1055352 1067272 1067192 1066049 
1065816 1055530 1067190 1067175 1067069 1067170 1066794 1066328 1067508 1067676 
1067494 1067509
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1068160
Marked Bug as done
Added indication that 1068160 affects haskell-gi-glib
Marked as fixed in versions haskell-haskell-gi/0.26.7-4.
There is no source info for the package 'haskell-haskell-gi' at version 
'0.26.7-2' with architecture ''
Unable to make a source version for version '0.26.7-2'
Marked as found in versions 0.26.7-2.
Added tag(s) trixie and sid.
Merged 1067272 1068160
> thanks
Stopping processing here.

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

Bug#1068062: marked as done (Update Build-Depends for the time64 library renames)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 22:52:04 +
with message-id 
and subject line Bug#1068062: fixed in workrave 1.10.52-2
has caused the Debian Bug report #1068062,
regarding Update Build-Depends for the time64 library renames
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.)


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

The package explicitly Build-Depends: libglib2.0-0, this needs to be changed to
libglib2.0-0t64 if it's needed at all.


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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
--- End Message ---
--- Begin Message ---
Source: workrave
Source-Version: 1.10.52-2
Done: Francois Marier 

We believe that the bug you reported is fixed in the latest version of
workrave, 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.
Francois Marier  (supplier of updated workrave 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, 31 Mar 2024 15:35:10 -0700
Source: workrave
Architecture: source
Version: 1.10.52-2
Distribution: unstable
Urgency: medium
Maintainer: Francois Marier 
Changed-By: Francois Marier 
Closes: 1052115 1068062
Changes:
 workrave (1.10.52-2) unstable; urgency=medium
 .
   * Update Build-Depends to libglib2.0-0t64 (closes: #1068062)
   * Add support for gnome-shell 46 (closes: #1052115)
Checksums-Sha1:
 fc46280f85a1c55d97272707e7afd9807eab00e8 2971 workrave_1.10.52-2.dsc
 268bd5b876ae42bcad5e977428098f09d5799567 20264 workrave_1.10.52-2.debian.tar.xz
 7bb69cf9acbbc9aa32775776a347438039bc3eb4 21060 
workrave_1.10.52-2_source.buildinfo
Checksums-Sha256:
 f52c252faa3423c1ee57362567ea022ece17de516726195da3e4b8b65ee8789a 2971 
workrave_1.10.52-2.dsc
 c4eb165941aa51877b2b72a5d98aa6ed63f60720cd8361d9f4dd26a599e63ac5 20264 
workrave_1.10.52-2.debian.tar.xz
 e29227e52e30ec9766397a5410aec4619c115ded5a30d663af669f2db6562ac9 21060 
workrave_1.10.52-2_source.buildinfo
Files:
 8d9dac28160451063e7c15b7737054b3 2971 gnome optional workrave_1.10.52-2.dsc
 9decc029bd49bdd08427afccd3f5 20264 gnome optional 
workrave_1.10.52-2.debian.tar.xz
 7729ed476222fc3ee8bebfb856599bdc 21060 gnome optional 
workrave_1.10.52-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEjEcLKgsxVo4RDUMlFigfLgB8mNEFAmYJ5yNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDhD
NDcwQjJBMEIzMTU2OEUxMTBENDMyNTE2MjgxRjJFMDA3Qzk4RDEACgkQFigfLgB8
mNEa8xAAnLz7jkFQvV+nf2luZ/VfOMs19yYin3g3IULVTc0VJbHYLPO+r2XgiH8S
6fXzQEjY8HgyWMkTM9tOGDozi3P+gxO3jHxZch7xisrPVH0nmubluO/DSo0hohkk
05VQVXxh6CRCmbnW2lxE2rwVH2HRe9SeORzu0WbALVFSOG7fGeAH1/vlFeI9KA3T
w3xRGDxVxvByrmVjT1s7IpPrhUKVOJnirX2uYh+Qt6Q0GEOms10I0KYT6LGSg4co
V+pxpMA6r3s9kYCc69CIoRo7MBrbgOjWNDM7DzXHNxBMan6qoKaFV/C6urJRUTlL
/0wDcTPZL1t6XjqBhmCfH4V9U9kfNvyr1vYz51eGwSI2jVst7W0DKo6V+Wzh4I4U
x2NyIRBRF/brjl2EjCi/r/QsCUlSnYp7MuP2r1rcDYJ3OU+W79vqTJ2WJtT+0fXC
4U7yxvTk8NSTJZsN+82ytiiAqtPIW5OGHlejFLhSXQ9vLGBwPw0EJgjGoJmFXKTF
ybDKH4uZFlHZiwUR2QRxqKMRkhnKZ373tiHAPWiYhKw83uCQPYnWekesOZ8hjJYY
DQcmz6WEDOh9IE8DXpRA8Krx3+Amz4mIkEnZd3SDNGK7DdryL6gU5b20uKhU7Tta
Jz/WUuOEYzX59eamk4RF729hN1GKvL/7JNjQzB6+82XE2STXi9g=
=9wt4
-END PGP SIGNATURE-



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

Bug#1066314: marked as done (regina-rexx: FTBFS: ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’; did you mean ‘popcallstack’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 22:51:36 +
with message-id 
and subject line Bug#1066314: fixed in regina-rexx 3.9.5+dfsg1-0.1
has caused the Debian Bug report #1066314,
regarding regina-rexx: FTBFS: ./rexxext.c:95:7: error: implicit declaration of 
function ‘getcallstack’; did you mean ‘popcallstack’? 
[-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.)


-- 
1066314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: regina-rexx
Version: 3.6-2.4
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 -DNDEBUG -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 
> -DREGINA_SHARE_DIRECTORY=\"//usr/share/regina-rexx\" -funsigned-char 
> -DREGINA_VERSION_DATE=\""31 Dec 2011"\" -DREGINA_VERSION_MAJOR=\"3\" 
> -DREGINA_VERSION_MINOR=\"6\" -DREGINA_VERSION_SUPP=\"\" -DHAVE_CONFIG_H
> -I. -I. -I./contrib-o rexxext.o -c ./rexxext.c
> ./rexxext.c: In function ‘__regina_rex_getcallstack’:
> ./rexxext.c:95:7: error: implicit declaration of function ‘getcallstack’; did 
> you mean ‘popcallstack’? [-Werror=implicit-function-declaration]
>95 |   getcallstack( TSD, parms->value );
>   |   ^~~~
>   |   popcallstack
> cc1: some warnings being treated as errors
> make[1]: *** [Makefile:427: rexxext.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/regina-rexx_3.6-2.4_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: regina-rexx
Source-Version: 3.9.5+dfsg1-0.1
Done: Agustin Martin Domingo 

We believe that the bug you reported is fixed in the latest version of
regina-rexx, 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.
Agustin Martin Domingo  (supplier of updated regina-rexx 
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: Mon, 01 Apr 2024 00:06:09 +0200
Source: regina-rexx
Architecture: source
Version: 3.9.5+dfsg1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Alen Zekulic 
Changed-By: Agustin Martin Domingo 
Closes: 1027405 1066314
Changes:
 regina-rexx (3.9.5+dfsg1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload with maintaner agreement.
 .
   [ Debian Janitor ]
   * Use secure URI in debian/watch.
   * Fix day-of-week for changelog entry 2.2-1.
   * Update standards version to 4.5.1, no changes needed.
   * Use secure URI in Homepage field.
   * Update standards version to 4.6.1, no changes needed.
 .
   [ Agustin Martin Domingo ]
   * New upstream version (Closes: #1066314).
 - Remove REGUTIL_TERM_LIB stuff (#930005). Fixed upstream in a
   simpler way.
 - _configures_fix-alpha-compilation.diff: renamed from
   _AZ_configures.diff for clarity.
 - 

Bug#1068160: haskell-gi-glib: FTBFS on mips64el: couldn't find API description for GLib.time_t

[Sebastian Ramacher]

Source: haskell-gi-glib
Version: 2.0.29-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=haskell-gi-glib=mips64el=2.0.29-1%2Bb2=1711923103=0

Running debian/hlibrary.setup configure --ghc -v2 
--package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
--libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
--builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
--haddockdir=/usr/lib/ghc-doc/haddock/gi-glib-2.0.29/ --datasubdir=gi-glib 
--htmldir=/usr/share/doc/libghc-gi-glib-doc/html/ --enable-library-profiling
Non-zero exit code 1.
Using Parsec parser
␛[1;91mERROR: ␛[97mcouldn't find API description for GLib.time_t␛[22;94m
Please report this at https://github.com/haskell-gi/haskell-gi/issues␛[0m
CallStack (from HasCallStack):
  error, called at lib/Data/GI/CodeGen/Util.hs:126:6 in 
haskell-gi-0.26.7-9datlXCg7xu2gIby3le2Cx:Data.GI.CodeGen.Util
  terror, called at lib/Data/GI/CodeGen/Code.hs:556:13 in 
haskell-gi-0.26.7-9datlXCg7xu2gIby3le2Cx:Data.GI.CodeGen.Code
  findAPIByName, called at lib/Data/GI/CodeGen/GObject.hs:17:44 in 
haskell-gi-0.26.7-9datlXCg7xu2gIby3le2Cx:Data.GI.CodeGen.GObject
 at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 109.

Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
 "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d", 
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib", 
"--libexecdir=/usr/lib", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 133

Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup", 
"configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d", 
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib", 
"--libexecdir=/usr/lib", ...) called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 637
Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe() 
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1067626: marked as done (FTBFS: fopen_fails test failed)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 22:09:52 +
with message-id 
and subject line Bug#1067626: fixed in pacemaker 2.1.7-1
has caused the Debian Bug report #1067626,
regarding FTBFS: fopen_fails test failed
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.)


-- 
1067626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pacemaker
Version: 2.1.6-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=pacemaker=armel=2.1.6-5=1711156223=0

PASS: pcmk__output_new_test 1 - empty_formatters
PASS: pcmk__output_new_test 2 - invalid_params
PASS: pcmk__output_new_test 3 - no_such_format
PASS: pcmk__output_new_test 4 - create_fails
PASS: pcmk__output_new_test 5 - init_fails
FAIL: pcmk__output_new_test 6 - fopen_fails
PASS: pcmk__output_new_test 7 - everything_succeeds
PASS: pcmk__output_new_test 8 - no_fmt_name_given
ERROR: pcmk__output_new_test - exited with status 1


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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
--- End Message ---
--- Begin Message ---
Source: pacemaker
Source-Version: 2.1.7-1
Done: Ferenc Wágner 

We believe that the bug you reported is fixed in the latest version of
pacemaker, 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.
Ferenc Wágner  (supplier of updated pacemaker 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, 31 Mar 2024 22:36:16 +0200
Source: pacemaker
Architecture: source
Version: 2.1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Ferenc Wágner 
Closes: 1067626
Changes:
 pacemaker (2.1.7-1) unstable; urgency=medium
 .
   * [09de5bf] New upstream release (2.1.7) (Closes: #1067626)
   * [ad97704] Refresh our patches
   * [e71f255] Update symbols files (all removed symbols were internal)
   * [13bce35] The cts Python directory is not installed anymore.
 Upstream migrated all of its contents into the _cts module of the
 pacemaker Python package (see commit 1fdea434).
Checksums-Sha1:
 6d54dbf79e559888cf3deeba7d7a41dc9f57c2ac 3646 pacemaker_2.1.7-1.dsc
 767c5c564a300ec096884ccc7dc469a0bab6e9d7 6056266 pacemaker_2.1.7.orig.tar.gz
 b3d0a89787d17d2e06ba1ea19cac5a2d4443c0d5 51612 pacemaker_2.1.7-1.debian.tar.xz
 0ac5e0c78ec1b3187a5c4dc11df9426921869bc1 25112 
pacemaker_2.1.7-1_amd64.buildinfo
Checksums-Sha256:
 29e7ca35ebe8a0b80c077a8ff0c7c764976a996e0ba3a07a1fe8dd4ba6373124 3646 
pacemaker_2.1.7-1.dsc
 17e18ec4d7ab138df641a22b812026c6f70cb7e2f7db6b3ded098de81b0b135a 6056266 
pacemaker_2.1.7.orig.tar.gz
 2adda8de501e043ea5c5ab75c5f2e0388cf5a0c019e804dc14faebc0b8c2b844 51612 
pacemaker_2.1.7-1.debian.tar.xz
 425ea8aac6cd55367c39038b0fc3277a2a15bde09c99f06855a831e4628c27bf 25112 
pacemaker_2.1.7-1_amd64.buildinfo
Files:
 33bb3d9bd3103a7c41988d960f061b22 3646 admin optional pacemaker_2.1.7-1.dsc
 f91bd46791c8b302e82e8eb608770238 6056266 admin optional 
pacemaker_2.1.7.orig.tar.gz
 2f24c3185cc8999458243d5ca3cf5b49 51612 admin optional 
pacemaker_2.1.7-1.debian.tar.xz
 8b0bb1b234ce7e8bb7441483b8538a45 25112 admin optional 
pacemaker_2.1.7-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEwddEx0RNIUL7eugtOsj3Fkd+2yMFAmYJ1KMACgkQOsj3Fkd+
2yOWoQ/+I5jCqxTKkDxGxY+mytpIZcKDMQiyGANzSe9JeKzgxC9DmmBcZCmkP0A3
uIWE0SaN1KXSR5MeG7NMhH4Qp7qIhSxo1iGjLHRzHhTowMxM6aryzPd/QXG3Sag9
Lj8Anmxecs6slv88XKAfmC4TupqpaGdnh1oCn4x09H607RWsZoxzo1oVmgCMkx8L
pBnrtuR0MOxFXsgM+GvX1NLDmigpyGmKfoDGgaXchDAT0La3w5Ogo74v5Gqy1L7I

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

[Sebastian Ramacher]

Source: openjfx
Version: 11.0.11+1-3.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=openjfx=armel=11.0.11%2B1-3.1%2Bb2=1711746481=0

gcc -fPIC -Wformat -Wextra -Wformat-security -fstack-protector 
-Werror=implicit-function-declaration -Werror=trampolines -D_GNU_SOURCE 
-DGST_REMOVE_DEPRECATED -DGSTREAMER_LITE -DHAVE_CONFIG_H -DOUTSIDE_SPEEX 
-DLINUX -DGST_DISABLE_GST_DEBUG -DGST_DISABLE_LOADSAVE -ffunction-sections 
-fdata-sections -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>/modules/javafx.media/src/main/native/gstreamer/projects/linux/gstreamer-lite=.
 -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -I../../../plugins 
-I../../../gstreamer-lite/projects/build/linux/common 
-I../../../gstreamer-lite/gstreamer -I../../../gstreamer-lite/gstreamer/libs 
-I../../../gstreamer-lite/gstreamer/gst/parse 
-I../../../gstreamer-lite/gst-plugins-base 
-I../../../gstreamer-lite/gst-plugins-base/gst-libs 
-I../../../gstreamer-lite/projects/plugins 
-I../../../gstreamer-lite/gst-plugins-base/gst-libs 
-I../../../gstreamer-lite/gst-plugins-good/gst-libs 
-I../../../gstreamer-lite/gst-plugins-good/gst/isomp4 
-I../../../gstreamer-lite/gst-plugins-bad/gst-libs -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabi/glib-2.0/include  -c 
../../../gstreamer-lite/gstreamer/gst/gst.c -o 
/<>/modules/javafx.media/build/native/linux/Release/obj/gstreamer-lite/gstreamer/gst/gst.o
In file included from /usr/include/features.h:393,
 from 
/usr/include/arm-linux-gnueabi/bits/libc-header-start.h:33,
 from /usr/include/limits.h:26,
 from /usr/lib/gcc/arm-linux-gnueabi/13/include/limits.h:205,
 from /usr/lib/gcc/arm-linux-gnueabi/13/include/syslimits.h:7,
 from /usr/lib/gcc/arm-linux-gnueabi/13/include/limits.h:34,
 from 
/usr/lib/arm-linux-gnueabi/glib-2.0/include/glibconfig.h:11,
 from /usr/include/glib-2.0/glib/gtypes.h:34,
 from /usr/include/glib-2.0/glib/galloca.h:34,
 from /usr/include/glib-2.0/glib.h:32,
 from ../../../gstreamer-lite/gstreamer/gst/gst_private.h:36,
 from ../../../gstreamer-lite/gstreamer/gst/gst.c:94:
/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
only with _FILE_OFFSET_BITS=64"
   26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
  | ^
gcc -fPIC -Wformat -Wextra -Wformat-security -fstack-protector 
-Werror=implicit-function-declaration -Werror=trampolines -D_GNU_SOURCE 
-DGST_REMOVE_DEPRECATED -DGSTREAMER_LITE -DHAVE_CONFIG_H -DOUTSIDE_SPEEX 
-DLINUX -DGST_DISABLE_GST_DEBUG -DGST_DISABLE_LOADSAVE -ffunction-sections 
-fdata-sections -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>/modules/javafx.media/src/main/native/gstreamer/projects/linux/gstreamer-lite=.
 -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -I../../../plugins 
-I../../../gstreamer-lite/projects/build/linux/common 
-I../../../gstreamer-lite/gstreamer -I../../../gstreamer-lite/gstreamer/libs 
-I../../../gstreamer-lite/gstreamer/gst/parse 
-I../../../gstreamer-lite/gst-plugins-base 
-I../../../gstreamer-lite/gst-plugins-base/gst-libs 
-I../../../gstreamer-lite/projects/plugins 
-I../../../gstreamer-lite/gst-plugins-base/gst-libs 
-I../../../gstreamer-lite/gst-plugins-good/gst-libs 
-I../../../gstreamer-lite/gst-plugins-good/gst/isomp4 
-I../../../gstreamer-lite/gst-plugins-bad/gst-libs -I/usr/include/glib-2.0 
-I/usr/lib/arm-linux-gnueabi/glib-2.0/include  -c 
../../../gstreamer-lite/gstreamer/gst/gstallocator.c -o 
/<>/modules/javafx.media/build/native/linux/Release/obj/gstreamer-lite/gstreamer/gst/gstallocator.o
../../../gstreamer-lite/gstreamer/gst/gst.c: In function ‘gst_init_check’:
../../../gstreamer-lite/gstreamer/gst/gst.c:411:22: warning: unused parameter 
‘argc’ [-Wunused-parameter]
  411 | gst_init_check (int *argc, char **argv[], GError ** err)
  | ~^~~~
../../../gstreamer-lite/gstreamer/gst/gst.c:411:35: warning: unused parameter 
‘argv’ [-Wunused-parameter]
  411 | gst_init_check (int *argc, char **argv[], GError ** err)
  |~~~^~
../../../gstreamer-lite/gstreamer/gst/gst.c:411:53: warning: unused parameter 
‘err’ [-Wunused-parameter]
  411 | gst_init_check (int *argc, char **argv[], GError ** err)
make[2]: Leaving directory 
'/<>/modules/javafx.media/src/main/native/gstreamer/projects/linux/gstreamer-lite'
  |   ~~^~~

Bug#1068158: python-escript: FTBFS: RuntimeError: We do not current support different different dpkg-buildflags for C vs C++:

[Sebastian Ramacher]

Source: python-escript
Version: 5.6-6
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=python-escript=arm64=5.6-6%2Bb3=1711889068=0

mkdir -p /<>/debian/stage3
scons  -j4   cc_optim=' -O3  '  build_dir=/<>/debian/tmp3 
verbose=on prefix=/<>/debian/stage3 
options_file=debian/sid_options.py docs
scons: Reading SConscript files ...
3.11.8 (main, Mar 26 2024, 12:04:57) [GCC 13.2.0]
RuntimeError: We do not current support different different dpkg-buildflags for 
C vs C++:
  File "/<>/SConstruct", line 172:
env = Environment(tools = ['default'], options = vars,
  File "/usr/lib/python3/dist-packages/SCons/Environment.py", line 1231:
variables.Update(self)
  File "/usr/lib/python3/dist-packages/SCons/Variables/__init__.py", line 187:
exec(contents, {}, values)
  File "", line 84:

  File "/<>/site_scons/extractdebbuild.py", line 61:
raise RuntimeError("We do not current support different different 
dpkg-buildflags for C vs C++")
make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2

Cheers
-- 
Sebastian Ramacher

Bug#1068157: siridb-server: FTBFS on armhf: ./test.sh: line 18: 3276877 Segmentation fault valgrind --tool=memcheck --error-exitcode=1 --leak-check=full -q ./$OUT

[Sebastian Ramacher]

Source: siridb-server
Version: 2.0.51-2
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=siridb-server=2.0.51-2%2Bb3=armhf=1711922161

Testing 
expr␛[32mOK␛[0m 
(8.519 ms)
==3276877== 
==3276877== Process terminating with default action of signal 11 (SIGSEGV)
==3276877==  Access not within mapped region at address 0xFEC4F704
==3276877==at 0x495F6F0: pcre2_compile_8 (in 
/usr/lib/arm-linux-gnueabihf/libpcre2-8.so.0.11.2)
==3276877==  If you believe this happened as a result of a stack
==3276877==  overflow in your program's main thread (unlikely but
==3276877==  possible), you can try to increase the size of the
==3276877==  main thread stack using the --main-stacksize= flag.
==3276877==  The main thread stack size used in this run was 8388608.
./test.sh: line 18: 3276877 Segmentation fault  valgrind --tool=memcheck 
--error-exitcode=1 --leak-check=full -q ./$OUT

Cheers
-- 
Sebastian Ramacher

Bug#1056893: uvloop: diff for NMU version 0.19.0+ds1-2.1

[Sebastian Ramacher]

Control: tags 1056893 + pending

Dear maintainer,

I've prepared an NMU for uvloop (versioned as 0.19.0+ds1-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 uvloop-0.19.0+ds1/debian/changelog uvloop-0.19.0+ds1/debian/changelog
--- uvloop-0.19.0+ds1/debian/changelog	2023-11-16 13:16:10.0 +0100
+++ uvloop-0.19.0+ds1/debian/changelog	2024-03-31 23:47:16.0 +0200
@@ -1,3 +1,14 @@
+uvloop (0.19.0+ds1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Graham Inggs ]
+  * Include proposed patch for compatibility with Cython 3 (Closes: #1056893)
+(LP: #2051150)
+  * Skip tests failing with libuv 1.48.0
+
+ -- Sebastian Ramacher   Sun, 31 Mar 2024 23:47:16 +0200
+
 uvloop (0.19.0+ds1-2) unstable; urgency=medium
 
   * Add 0003-Fix-unit-tests-on-IPv6-only-hosts patch. Thanks to Dale Richards!
diff -Nru uvloop-0.19.0+ds1/debian/patches/cython3.patch uvloop-0.19.0+ds1/debian/patches/cython3.patch
--- uvloop-0.19.0+ds1/debian/patches/cython3.patch	1970-01-01 01:00:00.0 +0100
+++ uvloop-0.19.0+ds1/debian/patches/cython3.patch	2024-03-26 18:29:47.0 +0100
@@ -0,0 +1,556 @@
+Description: Updates for Cython3
+ Remove SSL depreciation warnings
+Forwarded: https://github.com/MagicStack/uvloop/pull/587
+Author: Alan Brooks <12380017+alan-bro...@users.noreply.github.com>
+Last-Update: 2023-12-28
+
+--- a/Makefile
 b/Makefile
+@@ -9,7 +9,7 @@
+ 
+ 
+ clean:
+-	rm -fr dist/ doc/_build/ *.egg-info uvloop/loop.*.pyd
++	rm -fr dist/ doc/_build/ *.egg-info uvloop/loop.*.pyd uvloop/loop_d.*.pyd
+ 	rm -fr uvloop/*.c uvloop/*.html uvloop/*.so
+ 	rm -fr uvloop/handles/*.html uvloop/includes/*.html
+ 	find . -name '__pycache__' | xargs rm -rf
+--- a/setup.py
 b/setup.py
+@@ -144,7 +144,9 @@
+ self.distribution.ext_modules[:] = cythonize(
+ self.distribution.ext_modules,
+ compiler_directives=directives,
+-annotate=self.cython_annotate)
++annotate=self.cython_annotate,
++compile_time_env=dict(DEFAULT_FREELIST_SIZE=250, SSL_READ_MAX_SIZE=256 * 1024),
++emit_linenums=True)
+ 
+ super().finalize_options()
+ 
+--- a/tests/test_process.py
 b/tests/test_process.py
+@@ -912,7 +912,7 @@
+ stdin=subprocess.PIPE,
+ stdout=subprocess.PIPE,
+ stderr=subprocess.PIPE,
+-__uvloop_sleep_after_fork=True))
++uvloop_sleep_after_fork=True))
+ self.assertIsNot(transport, None)
+ self.assertEqual(transport.get_returncode(), 0)
+ self.assertEqual(
+@@ -931,7 +931,7 @@
+ stdin=None,
+ stdout=subprocess.PIPE,
+ stderr=subprocess.PIPE,
+-__uvloop_sleep_after_fork=True))
++uvloop_sleep_after_fork=True))
+ self.assertIsNot(transport, None)
+ self.assertEqual(transport.get_returncode(), 0)
+ self.assertEqual(
+--- a/tests/test_tcp.py
 b/tests/test_tcp.py
+@@ -1630,17 +1630,22 @@
+ self.fail("unexpected call to connection_made()")
+ 
+ def test_ssl_connect_accepted_socket(self):
+-if hasattr(ssl, 'PROTOCOL_TLS'):
+-proto = ssl.PROTOCOL_TLS
++if hasattr(ssl, 'PROTOCOL_TLS_SERVER'):
++server_proto = ssl.PROTOCOL_TLS_SERVER
++client_proto = ssl.PROTOCOL_TLS_CLIENT
+ else:
+-proto = ssl.PROTOCOL_SSLv23
+-server_context = ssl.SSLContext(proto)
++if hasattr(ssl, 'PROTOCOL_TLS'):
++client_proto = server_proto = ssl.PROTOCOL_TLS
++else:
++client_proto = server_proto = ssl.PROTOCOL_SSLv23
++
++server_context = ssl.SSLContext(server_proto)
+ server_context.load_cert_chain(self.ONLYCERT, self.ONLYKEY)
+ if hasattr(server_context, 'check_hostname'):
+ server_context.check_hostname = False
+ server_context.verify_mode = ssl.CERT_NONE
+ 
+-client_context = ssl.SSLContext(proto)
++client_context = ssl.SSLContext(client_proto)
+ if hasattr(server_context, 'check_hostname'):
+ client_context.check_hostname = False
+ client_context.verify_mode = ssl.CERT_NONE
+@@ -2233,7 +2238,7 @@
+ sslctx.use_privatekey_file(self.ONLYKEY)
+ sslctx.use_certificate_chain_file(self.ONLYCERT)
+ client_sslctx = self._create_client_ssl_context()
+-if hasattr(ssl, 'OP_NO_TLSv1_3'):
++if sys.version_info < (3, 8) and hasattr(ssl, 'OP_NO_TLSv1_3'):
+ client_sslctx.options |= ssl.OP_NO_TLSv1_3
+ 
+ def server(sock):
+@@ -2592,7 +2597,7 @@
+ sslctx_openssl.use_privatekey_file(self.ONLYKEY)
+ sslctx_openssl.use_certificate_chain_file(self.ONLYCERT)
+ client_sslctx = self._create_client_ssl_context()
+-if hasattr(ssl, 

Processed: uvloop: diff for NMU version 0.19.0+ds1-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1056893 + pending
Bug #1056893 [src:uvloop] uvloop: ftbfs with cython 3.0.x
Added tag(s) pending.

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

Bug#1066722: marked as done (xracer: FTBFS: spatscal.c:102:17: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 21:44:30 +
with message-id 
and subject line Bug#1066722: fixed in xracer 0.96.9.1-12
has caused the Debian Bug report #1066722,
regarding xracer: FTBFS: spatscal.c:102:17: error: implicit declaration of 
function ‘exit’ [-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.)


-- 
1066722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xracer
Version: 0.96.9.1-11
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 -DHAVE_CONFIG_H -I. -I../..  -I../../include  -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  
> -O3 -Wall -Wpointer-arith -Wmissing-prototypes -Wmissing-declarations 
> -Wcast-align -Wwrite-strings -c -o store.o store.c
> mpeg2dec.c:215:12: warning: ‘Decode_Bitstream’ defined but not used 
> [-Wunused-function]
>   215 | static int Decode_Bitstream(struct mpeg2obj *m)
>   |^~~~
> spatscal.c: In function ‘Read_Lower_Layer_Component_Framewise’:
> spatscal.c:102:17: error: implicit declaration of function ‘exit’ 
> [-Werror=implicit-function-declaration]
>   102 |   if (fd==NULL) exit(-1);
>   | ^~~~
> spatscal.c:12:1: note: include ‘’ or provide a declaration of ‘exit’
>11 | #include "global.h"
>   +++ |+#include 
>12 | 
> spatscal.c:102:17: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>   102 |   if (fd==NULL) exit(-1);
>   | ^~~~
> spatscal.c:102:17: note: include ‘’ or provide a declaration of 
> ‘exit’
> spatscal.c: In function ‘Read_Lower_Layer_Component_Fieldwise’:
> spatscal.c:130:17: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>   130 |   if (fd==NULL) exit(-1);
>   | ^~~~
> spatscal.c:130:17: note: include ‘’ or provide a declaration of 
> ‘exit’
> spatscal.c:140:19: warning: incompatible implicit declaration of built-in 
> function ‘exit’ [-Wbuiltin-declaration-mismatch]
>   140 | if (fd==NULL) exit(-1);
>   |   ^~~~
> spatscal.c:140:19: note: include ‘’ or provide a declaration of 
> ‘exit’
> store.c: In function ‘_mpeg2Write_Frame’:
> store.c:158:15: error: implicit declaration of function ‘memcpy’ 
> [-Werror=implicit-function-declaration]
>   158 |   memcpy (p, row_start, row_size);
>   |   ^~
> store.c:37:1: note: include ‘’ or provide a declaration of ‘memcpy’
>36 | #include "global.h"
>   +++ |+#include 
>37 | 
> store.c:158:15: warning: incompatible implicit declaration of built-in 
> function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   158 |   memcpy (p, row_start, row_size);
>   |   ^~
> store.c:158:15: note: include ‘’ or provide a declaration of 
> ‘memcpy’
> store.c:172:11: error: implicit declaration of function ‘memset’ 
> [-Werror=implicit-function-declaration]
>   172 |   memset (p, 0, row_size);
>   |   ^~
> store.c:172:11: note: include ‘’ or provide a declaration of 
> ‘memset’
> store.c:172:11: warning: incompatible implicit declaration of built-in 
> function ‘memset’ [-Wbuiltin-declaration-mismatch]
> store.c:172:11: note: include ‘’ or provide a declaration of 
> ‘memset’
> store.c:231:15: warning: incompatible implicit declaration of built-in 
> function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   231 |   memcpy (p, row_start, row_size);
>   |   ^~
> store.c:231:15: note: include ‘’ or provide a declaration of 
> ‘memcpy’
> store.c:245:11: warning: incompatible implicit declaration of built-in 
> function ‘memset’ [-Wbuiltin-declaration-mismatch]
>   245 |   memset (p, 0, row_size);
>   |   ^~
> store.c:245:11: note: include ‘’ or provide a declaration of 
> ‘memset’
> gcc -DHAVE_CONFIG_H -I. -I../..  -I../../include  

Bug#1068155: lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp)

[Sebastian Ramacher]

Source: lmms
Version: 1.2.2+dfsg1-6
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=lmms=i386=1.2.2%2Bdfsg1-6%2Bb3=1711724261=0

-- Installing: /<>/debian/tmp/usr/share/lmms/wavetables/tri.bin

Installing bash completion...

Bash completion for lmms has been installed to 
/<>/debian/tmp/usr/share/bash-completion/completions/lmms
make[1]: Leaving directory '/<>/obj-i686-linux-gnu'
   dh_install -a
dh_install: warning: Cannot find (any matches for) 
"usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp)

dh_install: warning: lmms-vst-server missing files: usr/lib/*/lmms/libvestige.so
dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvst*" 
(tried in ., debian/tmp)

dh_install: warning: lmms-vst-server missing files: usr/lib/*/lmms/libvst*
dh_install: warning: Cannot find (any matches for) 
"usr/lib/*/lmms/RemoteVstPlugin*" (tried in ., debian/tmp)

dh_install: warning: lmms-vst-server missing files: 
usr/lib/*/lmms/RemoteVstPlugin*
dh_install: error: missing files, aborting

Cheers
-- 
Sebastian Ramacher

Bug#1066722: xracer: FTBFS: spatscal.c:102:17: error: implicit declaration of function ‘exit’ [-Werror=implicit-function-declaration]

[Ying-Chun Liu (PaulLiu)]

Hi all,

I've fixed the bug. Will upload it soon. Patch as attachment.

Yours,
Paul
Description: Fix FTBFS caused by -Werror=implicit-function-declaration
Bug-Debian: http://bugs.debian.org/1066722
Author: Ying-Chun Liu (PaulLiu) 
Last-Update: 2024-03-29
Index: xracer-0.96.9.1/xracer-0.96.9/src/mpeg/spatscal.c
===
--- xracer-0.96.9.1.orig/xracer-0.96.9/src/mpeg/spatscal.c
+++ xracer-0.96.9.1/xracer-0.96.9/src/mpeg/spatscal.c
@@ -2,6 +2,7 @@
 #include "config.h"
 
 #include 
+#include 
 
 #ifdef HAVE_STRING_H
 #include 
Index: xracer-0.96.9.1/xracer-0.96.9/src/mpeg/store.c
===
--- xracer-0.96.9.1.orig/xracer-0.96.9/src/mpeg/store.c
+++ xracer-0.96.9.1/xracer-0.96.9/src/mpeg/store.c
@@ -31,6 +31,7 @@
 
 #include 
 #include 
+#include 
 
 #include "mpeg-config.h"
 #include "global.h"
Index: xracer-0.96.9.1/xracer-0.96.9/src/game.c
===
--- xracer-0.96.9.1.orig/xracer-0.96.9/src/game.c
+++ xracer-0.96.9.1/xracer-0.96.9/src/game.c
@@ -21,6 +21,7 @@
 
 #include 
 #include 
+#include 
 
 #include 
 
Index: xracer-0.96.9.1/xracer-0.96.9/src/math.c
===
--- xracer-0.96.9.1.orig/xracer-0.96.9/src/math.c
+++ xracer-0.96.9.1/xracer-0.96.9/src/math.c
@@ -21,6 +21,7 @@
 
 #include 
 #include 
+#include 
 #include 
 
 #include "xracer-math.h"
Index: xracer-0.96.9.1/xracer-0.96.9/src/video.c
===
--- xracer-0.96.9.1.orig/xracer-0.96.9/src/video.c
+++ xracer-0.96.9.1/xracer-0.96.9/src/video.c
@@ -21,6 +21,7 @@
 
 #include 
 #include 
+#include 
 
 #include 
 
Index: xracer-0.96.9.1/xracer-0.96.9/src/arch_posix.c
===
--- xracer-0.96.9.1.orig/xracer-0.96.9/src/arch_posix.c
+++ xracer-0.96.9.1/xracer-0.96.9/src/arch_posix.c
@@ -27,6 +27,7 @@
 
 #include 
 #include 
+#include 
 
 #ifdef HAVE_UNISTD_H
 #include 
Index: xracer-0.96.9.1/xracer-0.96.9/src/ws_x11.c
===
--- xracer-0.96.9.1.orig/xracer-0.96.9/src/ws_x11.c
+++ xracer-0.96.9.1/xracer-0.96.9/src/ws_x11.c
@@ -24,6 +24,8 @@
 #include 
 #include 
 
+#include 
+
 #include "xracer.h"
 #include "xracer-ws.h"
 #include "xracer-log.h"


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1066527: marked as done (xsystem35: FTBFS: sactcg.c:211:27: error: implicit declaration of function ‘sjis2euc’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 21:10:35 +
with message-id 
and subject line Bug#1066527: fixed in xsystem35 1.7.3-pre5-11
has caused the Debian Bug report #1066527,
regarding xsystem35: FTBFS: sactcg.c:211:27: error: implicit declaration of 
function ‘sjis2euc’ [-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.)


-- 
1066527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xsystem35
Version: 1.7.3-pre5-10
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../.. -I../../src -I../../src -I../../libltdl 
> -I../../libltdl -I../../modules/lib -I../../modules/lib 
> -I../../modules/NIGHTDLL -I../../modules/NIGHTDLL  -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -Wall -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o sprite_eupdate.lo 
> sprite_eupdate.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. 
> -I../../src -I../../src -I../../libltdl -I../../libltdl -I../../modules/lib 
> -I../../modules/lib -I../../modules/NIGHTDLL -I../../modules/NIGHTDLL 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c NIGHTDLL.c  -fPIC -DPIC -o 
> .libs/NIGHTDLL.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. 
> -I../../src -I../../src -I../../libltdl -I../../libltdl -I../../modules/lib 
> -I../../modules/lib -I../../modules/NIGHTDLL -I../../modules/NIGHTDLL 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c nt_scenario.c  -fPIC -DPIC -o 
> .libs/nt_scenario.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. 
> -I../../src -I../../src -I../../libltdl -I../../libltdl -I../../modules/lib 
> -I../../modules/lib -I../../modules/NIGHTDLL -I../../modules/NIGHTDLL 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c sprite_update.c  -fPIC -DPIC -o 
> .libs/sprite_update.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. 
> -I../../src -I../../src -I../../libltdl -I../../libltdl -I../../modules/lib 
> -I../../modules/lib -I../../modules/NIGHTDLL -I../../modules/NIGHTDLL 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c sprite_eupdate.c  -fPIC -DPIC -o 
> .libs/sprite_eupdate.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. 
> -I../../src -I../../src -I../../libltdl -I../../libltdl -I../../modules/lib 
> -I../../modules/lib -I../../modules/NIGHTDLL -I../../modules/NIGHTDLL 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c sactstring.c  -fPIC -DPIC -o 
> .libs/sactstring.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. 
> -I../../src -I../../src -I../../libltdl 

Bug#1064677: marked as done (puppetdb: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 21:10:09 +
with message-id 
and subject line Bug#1064677: fixed in puppetdb 8.4.1-1
has caused the Debian Bug report #1064677,
regarding puppetdb: FTBFS: make[1]: *** [debian/rules:26: 
override_dh_auto_test] Error 1
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.)


-- 
1064677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: puppetdb
Version: 7.12.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> export pg_ver=$(/usr/share/postgresql-common/supported-versions --installed); 
> \
> export PATH=$PATH:/<>/debian/bin && \
> ./ext/bin/with-pdbbox \
>   --box $(mktemp -d "core-test-XX")/box \
>   --pgbin /usr/lib/postgresql/$pg_ver/bin \
>   --pgport 5432 \
>   -- lein test
> ++ printf 'rm -rf %q' core-test-sruDNB/box
> + trap 'rm -rf core-test-sruDNB/box' EXIT
> + export PDBBOX=core-test-sruDNB/box
> + PDBBOX=core-test-sruDNB/box
> + /<>/ext/bin/pdbbox-init --sandbox core-test-sruDNB/box --pgbin 
> /usr/lib/postgresql/16/bin --pgport 5432 --bind-addr ip6-localhost 
> --bind-addr localhost
> The files belonging to this database system will be owned by user "user42".
> This user must also own the server process.
> 
> The database cluster will be initialized with locale "C".
> The default text search configuration will be set to "english".
> 
> Data page checksums are disabled.
> 
> creating directory /<>/core-test-sruDNB/box/pg/data ... ok
> creating subdirectories ... ok
> selecting dynamic shared memory implementation ... posix
> selecting default max_connections ... 100
> selecting default shared_buffers ... 128MB
> selecting default time zone ... Etc/UTC
> creating configuration files ... ok
> running bootstrap script ... ok
> performing post-bootstrap initialization ... ok
> syncing data to disk ... ok
> 
> Success. You can now start the database server using:
> 
> /usr/lib/postgresql/16/bin/pg_ctl -D 
> /<>/core-test-sruDNB/box/pg/data -l logfile start
> 
> waiting for server to start2024-02-24 22:51:08.895 UTC [1237302] LOG:  
> starting PostgreSQL 16.2 (Debian 16.2-1) on x86_64-pc-linux-gnu, compiled by 
> gcc (Debian 13.2.0-13) 13.2.0, 64-bit
> 2024-02-24 22:51:08.895 UTC [1237302] LOG:  listening on IPv4 address 
> "127.0.0.1", port 5432
> 2024-02-24 22:51:08.897 UTC [1237302] LOG:  could not bind IPv4 address 
> "127.0.0.1": Address already in use
> 2024-02-24 22:51:08.897 UTC [1237302] HINT:  Is another postmaster already 
> running on port 5432? If not, wait a few seconds and retry.
> 2024-02-24 22:51:08.897 UTC [1237302] LOG:  could not bind IPv4 address 
> "127.0.0.1": Address already in use
> 2024-02-24 22:51:08.897 UTC [1237302] HINT:  Is another postmaster already 
> running on port 5432? If not, wait a few seconds and retry.
> 2024-02-24 22:51:08.897 UTC [1237302] WARNING:  could not create listen 
> socket for "localhost"
> 2024-02-24 22:51:08.905 UTC [1237302] LOG:  listening on Unix socket 
> "sock/.s.PGSQL.5432"
> 2024-02-24 22:51:08.912 UTC [1237305] LOG:  database system was shut down at 
> 2024-02-24 22:51:08 UTC
> 2024-02-24 22:51:08.918 UTC [1237302] LOG:  database system is ready to 
> accept connections
>  done
> server started
> 32+0 records in
> 32+0 records out
> 32 bytes copied, 8.6944e-05 s, 368 kB/s
> 32+0 records in
> 32+0 records out
> 32 bytes copied, 0.00111872 s, 28.6 kB/s
> 32+0 records in
> 32+0 records out
> 32 bytes copied, 0.00010492 s, 305 kB/s
> 32+0 records in
> 32+0 records out
> 32 bytes copied, 8.9158e-05 s, 359 kB/s
> ALTER ROLE
> ALTER ROLE
> ALTER ROLE
> ALTER ROLE
> GRANT ROLE
> GRANT ROLE
> GRANT ROLE
> GRANT ROLE
> ALTER ROLE
> ALTER ROLE
> ALTER ROLE
> CREATE EXTENSION
> REVOKE
> GRANT
> ALTER DEFAULT PRIVILEGES
> REVOKE
> GRANT
> GRANT
> GRANT
> CREATE EXTENSION
> REVOKE
> GRANT
> ALTER DEFAULT PRIVILEGES
> REVOKE
> GRANT
> GRANT
> GRANT
> Certificate request self-signature ok
> subject=C = US, ST = confusion, L = unknown, O = none, CN = pdb.localhost
> waiting for server to shut down2024-02-24 22:51:11.154 UTC [1237302] LOG: 
>  received fast shutdown request
> 2024-02-24 22:51:11.159 UTC [1237302] LOG:  aborting any active transactions
> 2024-02-24 22:51:11.162 UTC [1237302] LOG:  background worker "logical 
> replication launcher" (PID 1237308) exited with exit code 1
> 

Processed: bug 1067626 is forwarded to https://bugs.clusterlabs.org/show_bug.cgi?id=5526 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1067626 https://bugs.clusterlabs.org/show_bug.cgi?id=5526
Bug #1067626 [src:pacemaker] FTBFS: fopen_fails test failed
Set Bug forwarded-to-address to 
'https://bugs.clusterlabs.org/show_bug.cgi?id=5526'.
> fixed 1067626 2.1.7-1
Bug #1067626 [src:pacemaker] FTBFS: fopen_fails test failed
The source 'pacemaker' and version '2.1.7-1' do not appear to match any binary 
packages
Marked as fixed in versions pacemaker/2.1.7-1.
> thanks
Stopping processing here.

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

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

[Andrey Rakhmatullin]

Source: porg
Version: 2:0.10-1.2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=porg=armel=2%3A0.10-1.2%2Bb2=1711746873=0

/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../..   -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-
time -D_FORTIFY_SOURCE=2 -W -ansi -Wshadow -Wmissing-declarations -Wall -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-
security -c -o libporg_log_la-log.lo `test -f 'log.c' || echo './'`log.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -W -ansi
-Wshadow -Wmissing-declarations -Wall -g -O2 -Werror=implicit-function-
declaration -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -c log.c  -fPIC -DPIC
-o .libs/libporg_log_la-log.o
log.c: In function ‘open’:
log.c:281:27: warning: ‘nonnull’ argument ‘path’ compared to NULL [-Wnonnull-
compare]
  281 | if (!porg_tmpfile && path && !strncmp(path, "/proc/", 6))
  | ~~^~~
log.c: In function ‘open64’:
log.c:385:27: warning: ‘nonnull’ argument ‘path’ compared to NULL [-Wnonnull-
compare]
  385 | if (!porg_tmpfile && path && !strncmp(path, "/proc/", 6))
  | ~~^~~
log.c: In function ‘porg_get_absolute_path’:
log.c:106:17: warning: ‘__builtin_strncpy’ output may be truncated copying 4095
bytes from a string of length 4095 [-Wstringop-truncation]
  106 | strncpy(abs_path, aux, PORG_BUFSIZE - 1);
  | ^
log.c:100:17: warning: ‘__builtin_strncpy’ output may be truncated copying 4095
bytes from a string of length 4095 [-Wstringop-truncation]
  100 | strncpy(abs_path, cwd, PORG_BUFSIZE - 1);
  | ^
/tmp/cc7rmZAz.s: Assembler messages:
/tmp/cc7rmZAz.s:2214: Error: symbol `open64' is already defined
/tmp/cc7rmZAz.s:2581: Error: symbol `openat64' is already defined
/tmp/cc7rmZAz.s:3220: Error: symbol `creat64' is already defined
/tmp/cc7rmZAz.s:3296: Error: symbol `fopen64' is already defined
/tmp/cc7rmZAz.s:3380: Error: symbol `freopen64' is already defined


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1066760: xine-ui: FTBFS: dh_install: error: missing files, aborting

[Andrey Rakhmatullin]

On Wed, Mar 13, 2024 at 03:54:42PM +0100, Lucas Nussbaum wrote:
> >dh_install
> > dh_install: warning: Cannot find (any matches for) "usr/bin/aaxine" (tried 
> > in ., debian/tmp)
The reason for this:

checking for AALIB version >= 1.2.0... no
*** Could not run AALIB test program, checking why...
*** The test program compiled, but did not run. This usually means
*** that the run-time linker is not finding AALIB or finding the wrong
*** version of AALIB. If it is not finding AALIB, you'll need to set your
*** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point
*** to the installed location  Also, make sure you have run ldconfig if that
*** is required on your system
***
*** If you have an old version installed, it is best to remove it, although
*** you may also be able to get things to work by modifying LD_LIBRARY_PATH
***

libaa1-dev is installed but I suspect the test fails with
-Werror=implicit-declaration.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1066527: xsystem35: FTBFS: sactcg.c:211:27: error: implicit declaration of function ‘sjis2euc’ [-Werror=implicit-function-declaration]

[Ying-Chun Liu (PaulLiu)]

Hi,

I fixed the bug. Will upload soon. Patch as attachment.

Yours,
Paul
Description: Fix FTBFS caused by -Werror=implicit-function-declaration
Bug-Debian: http://bugs.debian.org/1066527
Author: Ying-Chun Liu (PaulLiu) 
Last-Update: 2024-04-01
Index: xsystem35-1.7.3-pre5/modules/NIGHTDLL/sactcg.c
===
--- xsystem35-1.7.3-pre5.orig/modules/NIGHTDLL/sactcg.c
+++ xsystem35-1.7.3-pre5/modules/NIGHTDLL/sactcg.c
@@ -35,6 +35,7 @@
 #include "surface.h"
 #include "ngraph.h"
 #include "sactcg.h"
+#include "eucsjis.h"
 
 #define CGMAX 65536
 static cginfo_t *cgs[CGMAX];
Index: xsystem35-1.7.3-pre5/modules/NIGHTDLL/nt_msg.c
===
--- xsystem35-1.7.3-pre5.orig/modules/NIGHTDLL/nt_msg.c
+++ xsystem35-1.7.3-pre5/modules/NIGHTDLL/nt_msg.c
@@ -18,6 +18,7 @@
 #include "sactcg.h"
 #include "sjisname.h"
 #include "sactstring.h"
+#include "eucsjis.h"
 
 
 extern int ntsel_dosel(void);
Index: xsystem35-1.7.3-pre5/modules/NIGHTDLL/nt_event.c
===
--- xsystem35-1.7.3-pre5.orig/modules/NIGHTDLL/nt_event.c
+++ xsystem35-1.7.3-pre5/modules/NIGHTDLL/nt_event.c
@@ -13,6 +13,8 @@
 #include "night.h"
 #include "sprite.h"
 
+extern void cb_waitkey_sprite(agsevent_t *e);
+
 /*
   Messageキー入力待ち時の
 */


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

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

[Sebastian Andrzej Siewior]

On 2024-03-31 19:42:24 [+], tony mancill wrote:
> Given what has unfolded over the past few days regarding xz-utils and
> CVE-2024-3094 [0], should we revisit the patches applied here and for
> #1063252?  Are they still needed?

Not with the fallback to pre 5.4.x series but *I* don't think this will
remain forever.
The requirement for the change was different default value for the -T
parameter. Recording the -T parameter by default and relying on
defaults is good.

> Thank you,
> tony

Sebastian

Bug#1067121: marked as done (supysonic: flaky autopkgtest including times out)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 19:51:56 +
with message-id 
and subject line Bug#1067121: fixed in supysonic 0.7.6+ds-4
has caused the Debian Bug report #1067121,
regarding supysonic: flaky autopkgtest including times out
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.)


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

Source: supysonic
Version: 0.7.6+ds-3
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky timeout

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails. What's worse, sometimes that failure is due to 
it timing out after 2h47, while a normal run only takes minutes. It 
seems to hang. From a quick inspection, I didn't see this on amd64, but 
it happens on arm64, armel, armhf, i386 (failure but no timeout) ppc64el 
and s390x.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: supysonic
Source-Version: 0.7.6+ds-4
Done: Louis-Philippe Véronneau 

We believe that the bug you reported is fixed in the latest version of
supysonic, 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.
Louis-Philippe Véronneau  (supplier of updated supysonic 
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, 31 Mar 2024 15:30:11 -0400
Source: supysonic
Architecture: source
Version: 0.7.6+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Louis-Philippe Véronneau 
Closes: 1067121
Changes:
 supysonic (0.7.6+ds-4) unstable; urgency=medium
 .
   * d/patches: rename 0004_-test_user to 0010 to fix 'number' collision with
 the other 0004 patch.
   * d/patches: add 0011 to skip test_move_out, as it's flaky. (Closes:
 #1067121)
Checksums-Sha1:
 dd40d7c52198d458c77209e35c1d5011ca047d18 1826 supysonic_0.7.6+ds-4.dsc
 b8cd525a00b5ec1c6ea58a48225e4e47f1eeded7 19888 
supysonic_0.7.6+ds-4.debian.tar.xz
 76b581a45ed8d67145835ea0fa42aec1a93bf653 8617 
supysonic_0.7.6+ds-4_amd64.buildinfo
Checksums-Sha256:
 9500e1354f80993df8754dc329400d44d50b7d79e6b237be4a2d12c3831fe6ea 1826 
supysonic_0.7.6+ds-4.dsc
 32f8fab3dc982ee4683b6c9e32deb07d6de924114a5a29ab2a2204b0f6185b33 19888 
supysonic_0.7.6+ds-4.debian.tar.xz
 19ba963f2c11dcfe429de2b2b76b7fc6df61b70e3079438642af7045bc6e03f2 8617 
supysonic_0.7.6+ds-4_amd64.buildinfo
Files:
 bef865a69b25e0d23cf80d6a7b8f0799 1826 sound optional supysonic_0.7.6+ds-4.dsc
 761fbdb3d62cba3e5043fff4f58b1c4b 19888 sound optional 
supysonic_0.7.6+ds-4.debian.tar.xz
 db96503e705634afb619daffe41cc571 8617 sound optional 
supysonic_0.7.6+ds-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTKp0AHB6gWsCAvw830JXpQshz6hQUCZgm7wAAKCRD0JXpQshz6
hYQPAPsEd4HE7rP766mb7IrL2ZasiKnJz+ZCenIMflU2VL3hlAD/R3eceMTUhn8w
IuAk7lY+O1aH287qhDkEyUWNNoP06gY=
=MAhV
-END PGP SIGNATURE-



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

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

[Andrey Rakhmatullin]

Source: pesign
Version: 116-6
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=pesign=armhf=116-6%2Bb2=1711718501=0

In file included from pesign.h:18,
 from cms_common.c:21:
cms_common.c: In function ‘cms_set_pw_data’:
util.h:275:23: error: format ‘%ld’ expects argument of type ‘long int’, but
argument 2 has type ‘__time64_t’ {aka ‘long long int’} [-Werror=format=]
  275 | warnx("%ld.%lu %s:%s():%d: " fmt,   \
  |   ^~
util.h:286:25: note: in expansion of macro ‘dbgprintf_’
  286 |
dbgprintf_(CAT(CAT(CAT(tv_,__COUNTER__),__LINE__),_),   \
  | ^~
util.h:292:19: note: in expansion of macro ‘dbgprintf’
  292 | #define ingress() dbgprintf("ingress");
  |   ^
cms_common.c:302:9: note: in expansion of macro ‘ingress’
  302 | ingress();
  | ^~~


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Processed: Bug#1067121 marked as pending in supysonic

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067121 [src:supysonic] supysonic: flaky autopkgtest including times out
Added tag(s) pending.

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

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

[tony mancill]

On Wed, Mar 13, 2024 at 01:50:47PM -0400, Jeremy Bícha wrote:
> The 3 test cases pass for me now with the uploaded 1.50+nmu2. Maybe my
> earlier test build used the old version of xz-utils. Thank you for
> your upload!

Given what has unfolded over the past few days regarding xz-utils and
CVE-2024-3094 [0], should we revisit the patches applied here and for
#1063252?  Are they still needed?

I'm not making any assertions about the validity of the changes, only
suggesting that we should review changes made to accommodate the
xz-utils versions related to the CVE.

(It is still not clear why some gbp workflows using pristine-tar started
failing [1] around the same time that changes were being introduced to
xz-utils and pristine-tar.  Perhaps it is a coicidence, but it seems
potentially related.)

Thank you,
tony

[0] https://security-tracker.debian.org/tracker/CVE-2024-3094
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065445


signature.asc
Description: PGP signature

Bug#1067121: marked as pending in supysonic

[Louis-Philippe Véronneau]

Control: tag -1 pending

Hello,

Bug #1067121 in supysonic reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/supysonic/-/commit/7fc70468ecbb65857d31c162dc7940ae4d425624


d/rules: skip test_move_out to fix flaky test timing out. (Closes: #1067121)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067121

Bug#1068146: FTBFS: tests failed

[Andrey Rakhmatullin]

Source: dipy
Version: 1.9.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=dipy=armel=1.9.0-1=1711658317=0

=== short test summary info

FAILED dipy/reconst/tests/test_shore.py::test_shore_fitting_no_constrain_e0
FAILED dipy/viz/tests/test_util.py::test_check_img_shapes -
numpy.core._excep...


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Bug#1068145: FTBFS: chmod: cannot access 'debian/python-mpltoolkits.basemap-data/usr/share/basemap/data/*': No such file or directory

[Andrey Rakhmatullin]

Source: basemap
Version: 1.2.2+dfsg-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=basemap=amd64=1.2.2%2Bdfsg-4=1711493603=0

   debian/rules override_dh_python3
make[1]: Entering directory '/<>'
dh_python3
chmod -x debian/python-mpltoolkits.basemap-data/usr/share/basemap/data/*
chmod: cannot access 'debian/python-mpltoolkits.basemap-
data/usr/share/basemap/data/*': No such file or directory


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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

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

[Andrey Rakhmatullin]

On Sat, Mar 23, 2024 at 09:56:58PM +0500, Andrey Rakhmatullin wrote:
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc -Wall
> -Wstrict-prototypes  -Wnested-externs
> -Werror=missing-prototypes  -Werror=implicit-function-
> declaration  -Werror=pointer-arith
> -Werror=init-self  -Werror=format-security
> -Werror=format=2  -Werror=missing-include-dirs
> -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include
> -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include
> -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include -pthread
> -I/usr/include/libmount -I/usr/include/blkid  -I/usr/include/gio-unix-2.0
> -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include -pthread
> -I/usr/include/libmount -I/usr/include/blkid  -g -O2 
> -Werror=implicit-function-
> declaration -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -O0  -Wl,-z,relro
> -Wl,-z,now -Wl,-O1 -o Xvnc Xvnc-Xvnc.o Xvnc-x-authority.o Xvnc-x-common.o 
> Xvnc-
> x-server.o Xvnc-status.o -lgobject-2.0 -lglib-2.0  -lglib-2.0  -lgio-2.0
> -lgobject-2.0 -lglib-2.0  -lgio-2.0 -lgobject-2.0 -lglib-2.0
> /tmp/ccCHYR2t.s: Assembler messages:
> /tmp/ccCHYR2t.s:2779: Error: symbol `open64' is already defined
> /tmp/ccCHYR2t.s:3181: Error: symbol `creat64' is already defined
> /tmp/ccCHYR2t.s:3508: Error: symbol `__stat64_time64' is already defined
I assume the following patch from Ubuntu fixes this:

--- a/tests/src/libsystem.c
+++ b/tests/src/libsystem.c
@@ -1,6 +1,9 @@
 #define _GNU_SOURCE
 #define __USE_GNU

+#undef _FILE_OFFSET_BITS
+#undef _TIME_BITS
+
 #include 

 #include 

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Processed: add forwarded info to #1067121

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1067121 https://github.com/spl0k/supysonic/issues/263
Bug #1067121 [src:supysonic] supysonic: flaky autopkgtest including times out
Set Bug forwarded-to-address to 'https://github.com/spl0k/supysonic/issues/263'.
> thanks
Stopping processing here.

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

Bug#1068142: Build-Depends on missing librust-quick-xml-0.31+default-dev

[Andrey Rakhmatullin]

Source: rust-gsettings-macro
Version: 0.2.0-2
Severity: serious
Tags: ftbfs



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

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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

Processed: tagging 1064531

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1064531 + ftbfs
Bug #1064531 [src:amberol] src:amberol: unsatisfied build dependency in 
testing: librust-lofty-0.17-dev
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 1067676

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1067676 + ftbfs
Bug #1067676 [src:gpick] gpick: build-dependency on libglib2.0-0 is 
unsatisfiable on armel/armhf
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1066416: granite-7: FTBFS: ./obj-x86_64-linux-gnu/lib/libgranite-7.so.7.4.0.p/Widgets/DatePicker.c:248:(.text+0x70c): undefined reference to `gtk_calendar_get_year'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 valac
Bug #1066416 [src:granite-7] granite-7: FTBFS: 
./obj-x86_64-linux-gnu/lib/libgranite-7.so.7.4.0.p/Widgets/DatePicker.c:248:(.text+0x70c):
 undefined reference to `gtk_calendar_get_year'
Bug reassigned from package 'src:granite-7' to 'valac'.
No longer marked as found in versions granite-7/7.4.0-1.
Ignoring request to alter fixed versions of bug #1066416 to the same values 
previously set
> affects -1 src:granite-7
Bug #1066416 [valac] granite-7: FTBFS: 
./obj-x86_64-linux-gnu/lib/libgranite-7.so.7.4.0.p/Widgets/DatePicker.c:248:(.text+0x70c):
 undefined reference to `gtk_calendar_get_year'
Added indication that 1066416 affects src:granite-7

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

Bug#1066416: granite-7: FTBFS: ./obj-x86_64-linux-gnu/lib/libgranite-7.so.7.4.0.p/Widgets/DatePicker.c:248:(.text+0x70c): undefined reference to `gtk_calendar_get_year'

[Andrey Rakhmatullin]

Control: reassign -1 valac
Control: affects -1 src:granite-7

On Wed, Mar 13, 2024 at 01:03:07PM +0100, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > /usr/bin/ld: 
> > lib/libgranite-7.so.7.4.0.p/meson-generated_Widgets_DatePicker.c.o: in 
> > function `_granite_date_picker___lambda10_':
> > ./obj-x86_64-linux-gnu/lib/libgranite-7.so.7.4.0.p/Widgets/DatePicker.c:248:(.text+0x70c):
> >  undefined reference to `gtk_calendar_get_year'
> > /usr/bin/ld: 
> > ./obj-x86_64-linux-gnu/lib/libgranite-7.so.7.4.0.p/Widgets/DatePicker.c:251:(.text+0x71a):
> >  undefined reference to `gtk_calendar_get_month'
> > /usr/bin/ld: 
> > ./obj-x86_64-linux-gnu/lib/libgranite-7.so.7.4.0.p/Widgets/DatePicker.c:254:(.text+0x727):
> >  undefined reference to `gtk_calendar_get_day'
These functions are added in Gtk4 4.14 while we have 4.12. The code is
generated from lib/Widgets/DatePicker.vala which doesn't refer to them
directly and was built successfully before so I assume it's a bug in valac
code generation.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Processed: tagging 1067912

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1067912 + ftbfs
Bug #1067912 [src:nitrokey-app] Update Build-Depends for the time64 library 
renames
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1068089: FTBFS: error: cannot convert ‘long int*’ to ‘const time_t*’ {aka ‘const long long int*’}

[Andrey Rakhmatullin]

On Sat, Mar 30, 2024 at 05:25:21PM +0500, Andrey Rakhmatullin wrote:
> plugins/about/aboutinterface.cpp: In member function ‘char*
> AboutInterface::ntpdate(char*)’:
> plugins/about/aboutinterface.cpp:438:18: error: cannot convert ‘long int*’ to
> ‘const time_t*’ {aka ‘const long long int*’}
>   438 | return ctime();
The code talks to the network (implementing the NTP protocol I guess?) and
so it's probably fragile. The comment suggests tmit is explicitly not a
time_t.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1068140: polymake: FTBFS: dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)

[Sebastian Ramacher]

Source: polymake
Version: 4.11-2
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=polymake=amd64=4.11-2%2Bb4=1711743555=0

dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11)
Hint: check if the library actually comes from a package.
dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/libpolymake4.11.substvars 
debian/libpolymake4.11/usr/lib/polymake/lib/libpolymake-apps.so.4.11 
debian/libpolymake4.11/usr/lib/polymake/lib/libpolymake-apps-rt.so.4.11 
debian/libpolymake4.11/usr/lib/libpolymake.so.4.11 returned exit code 25
dpkg-shlibdeps: error: no dependency information found for 
/lib/x86_64-linux-gnu/libflint.so.19 (used by 
debian/polymake/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so)
Hint: check if the library actually comes from a package.
dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/polymake.substvars 
debian/polymake/usr/lib/polymake/lib/tropical.so 
debian/polymake/usr/lib/polymake/lib/topaz.so 
debian/polymake/usr/lib/polymake/lib/polytope.so 
debian/polymake/usr/lib/polymake/lib/matroid.so 
debian/polymake/usr/lib/polymake/lib/ideal.so 
debian/polymake/usr/lib/polymake/lib/group.so 
debian/polymake/usr/lib/polymake/lib/graph.so 
debian/polymake/usr/lib/polymake/lib/fulton.so 
debian/polymake/usr/lib/polymake/lib/fan.so 
debian/polymake/usr/lib/polymake/lib/common.so 
debian/polymake/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so
 returned exit code 25
dh_shlibdeps: error: Aborting due to earlier error
make: *** [debian/rules:35: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher

Bug#1068138: halide: FTBFS on amd64: 676 - python_correctness_atomics (Failed)

[Sebastian Ramacher]

Source: halide
Version: 17.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=halide=amd64=17.0.1-1%2Bb2=1711572233=0

The following tests FAILED:
676 - python_correctness_atomics (Failed)
677 - python_correctness_autodiff (Failed)
Errors while running CTest
make[2]: *** [debian/rules:118: perform_stage_build] Error 8

Cheers
-- 
Sebastian Ramacher

Bug#1066594: marked as done (octave-iso2mesh: FTBFS: nl_single_file.c:2505:26: error: implicit declaration of function ‘lsame_’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 17:41:47 +
with message-id 
and subject line Bug#1066594: fixed in octave-iso2mesh 1.9.6+ds-10
has caused the Debian Bug report #1066594,
regarding octave-iso2mesh: FTBFS: nl_single_file.c:2505:26: error: implicit 
declaration of function ‘lsame_’ [-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.)


-- 
1066594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-iso2mesh
Version: 1.9.6+ds-9
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):
> make[4]: Entering directory '/<>/meshfix'
> [ 37%] Building C object 
> CMakeFiles/meshfix.dir/contrib/jrs_predicates/jrs_predicates.c.o
> [ 39%] Building CXX object 
> CMakeFiles/meshfix.dir/src/detectIntersections.cpp.o
> [ 41%] Building CXX object CMakeFiles/meshfix.dir/src/holeFilling.cpp.o
> /<>/meshfix/src/holeFilling.cpp: In member function ‘void 
> ExtTriMesh::fairSelection(Triangle*)’:
> /<>/meshfix/src/holeFilling.cpp:378:31: warning: cast to pointer 
> from integer of different size [-Wint-to-pointer-cast]
>   378 |   ((Vertex *)n->data)->info = (void *)i;
>   |   ^
> [ 43%] Building CXX object CMakeFiles/meshfix.dir/src/sparseLSystem.cpp.o
> [ 45%] Building CXX object CMakeFiles/meshfix.dir/src/mwExtensions.cpp.o
> [ 47%] Building CXX object CMakeFiles/meshfix.dir/src/smoothing.cpp.o
> [ 50%] Building C object 
> CMakeFiles/meshfix.dir/contrib/OpenNL3.2.1/src/nl_single_file.c.o
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c: In 
> function ‘dtpsv_’:
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:2505:26: 
> error: implicit declaration of function ‘lsame_’ 
> [-Werror=implicit-function-declaration]
>  2505 | if (!NL_FORTRAN_WRAP(lsame)(uplo, "U") &&
>   |  ^
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:420:28: 
> note: in definition of macro ‘NL_FORTRAN_WRAP’
>   420 | #define NL_FORTRAN_WRAP(x) x##_
>   |^
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:2526:25: 
> error: implicit declaration of function ‘xerbla_’ 
> [-Werror=implicit-function-declaration]
>  2526 | NL_FORTRAN_WRAP(xerbla)("DTPSV ", );
>   | ^~
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:420:28: 
> note: in definition of macro ‘NL_FORTRAN_WRAP’
>   420 | #define NL_FORTRAN_WRAP(x) x##_
>   |^
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c: In 
> function ‘nlSolve_SUPERLU’:
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:3513:5: 
> error: implicit declaration of function ‘dCreate_CompCol_Matrix’; did you 
> mean ‘cCreate_CompCol_Matrix’? [-Werror=implicit-function-declaration]
>  3513 | dCreate_CompCol_Matrix(
>   | ^~
>   | cCreate_CompCol_Matrix
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:3521:5: 
> error: implicit declaration of function ‘dCreate_Dense_Matrix’; did you mean 
> ‘cCreate_Dense_Matrix’? [-Werror=implicit-function-declaration]
>  3521 | dCreate_Dense_Matrix(
>   | ^~~~
>   | cCreate_Dense_Matrix
> /<>/meshfix/contrib/OpenNL3.2.1/src/nl_single_file.c:3557:5: 
> error: implicit declaration of function ‘dgssv’; did you mean ‘cgssv’? 
> [-Werror=implicit-function-declaration]
>  3557 | dgssv(, , perm, perm_r, , , , , );
>   | ^
>   | cgssv
> cc1: some warnings being treated as errors
> make[4]: *** [CMakeFiles/meshfix.dir/build.make:160: 
> CMakeFiles/meshfix.dir/contrib/OpenNL3.2.1/src/nl_single_file.c.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/octave-iso2mesh_1.9.6+ds-9_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

Bug#1063989: marked as done (xonsh: autopkgtest regression with pytest 8)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 16:53:52 +
with message-id 
and subject line Bug#1063989: fixed in xonsh 0.15.1+dfsg-1
has caused the Debian Bug report #1063989,
regarding xonsh: autopkgtest regression with pytest 8
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.)


-- 
1063989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xonsh
Version: 0.14.4+dfsg-1
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: pytest-8

Dear maintainer,

your package has a autopkgtest regression with pytest 8.

Typically, packages will start failing if they

- have deprecation warnings of type PytestRemovedIn8Warning, or

- assume a particular pytest stdout/stderr output which might have
changed, or

- rely on implementation details of the pytest test collector, in
particular the pytest.Package class, which has been redesigned for
pytest 8.

Please refer to the upstream changelog [1] for a complete list of
breaking changes and the pytest (pseudo-)excuses [2] related to your
package for details of the regression.

It is possible that the autopkgtest regression is not directly caused
by xonsh, but by one of its dependencies. In that case, feel free to
reassign the bug and mark your package as affected, but do not close
the bug until the autopkgtest passes.

Cheers Timo

[1]
https://docs.pytest.org/en/8.0.x/changelog.html#pytest-8-0-0rc1-2023-
12-30 [2]
https://qa.debian.org/excuses.php?experimental=1=pytest
--- End Message ---
--- Begin Message ---
Source: xonsh
Source-Version: 0.15.1+dfsg-1
Done: Stefano Rivera 

We believe that the bug you reported is fixed in the latest version of
xonsh, 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 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated xonsh 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, 31 Mar 2024 12:30:13 -0400
Source: xonsh
Architecture: source
Version: 0.15.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 1063989
Changes:
 xonsh (0.15.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
 - Supports pytest 8. (Closes: #1063989)
   * Refresh patches.
   * Drop revert-pytest-8.patch, no longer needed.
   * Bump copyright years.
Checksums-Sha1:
 d72b9253bf1f1e3190d2cd498049f9b584cb4fdf 1877 xonsh_0.15.1+dfsg-1.dsc
 0d3a7f04f5eebcb01c649e782b0dfb18861f1571 545260 xonsh_0.15.1+dfsg.orig.tar.xz
 d4e2a085746ef82008720d593a04689a7baeb2b9 12936 
xonsh_0.15.1+dfsg-1.debian.tar.xz
 d6a94e1287f13ec176ea407f7b55fe0363702f59 8358 
xonsh_0.15.1+dfsg-1_source.buildinfo
Checksums-Sha256:
 f71791252941baf169784961dfaab9a2646b831b00ec57211fbc1131351ef2e8 1877 
xonsh_0.15.1+dfsg-1.dsc
 86a7e3dbe3cba04754dcb75aca522afbb32c4d2e269c565f6fe2320fe110e7f2 545260 
xonsh_0.15.1+dfsg.orig.tar.xz
 5c86b3c30e5206f97fe3ef0baa3b3221636d55354f560a79752158f176947517 12936 
xonsh_0.15.1+dfsg-1.debian.tar.xz
 88e7040854471e2cd5c0b3b0b82f9b6167957c9d7bd2980733b5b98142270901 8358 
xonsh_0.15.1+dfsg-1_source.buildinfo
Files:
 369edb1251a5152fd39d0721994bc5f8 1877 shells optional xonsh_0.15.1+dfsg-1.dsc
 ac656524c4ec6259f3ee01c215ffae74 545260 shells optional 
xonsh_0.15.1+dfsg.orig.tar.xz
 f36135afc37b3e0564d40dcee9a1fc5b 12936 shells optional 
xonsh_0.15.1+dfsg-1.debian.tar.xz
 adc1c58e19e11368ca1f4b5106711e17 8358 shells optional 
xonsh_0.15.1+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCZgmP3hQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2B8IAQDsRQs6qdSNXXBENXJIpGnGkGZr0wDP
hrefCQD56Z89xQEAnYbea+3xu00laNARESccFI3/k6BKdZOnISz0WMHbSQs=
=FHTK
-END PGP SIGNATURE-



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

Processed: Bug#1063989 marked as pending in xonsh

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1063989 [xonsh] xonsh: autopkgtest regression with pytest 8
Added tag(s) pending.

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

Bug#1063989: marked as pending in xonsh

[Stefano Rivera]

Control: tag -1 pending

Hello,

Bug #1063989 in xonsh reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/xonsh/-/commit/a6106cfef2c398408365d976bfde9efb1895b53f


New upstream release.

* New upstream release.
  - Supports pytest 8. (Closes: #1063989)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1063989

Bug#1068135: gtk-sharp3: arch:all package depends on pre-t64 library

[Sebastian Ramacher]

Source: gtk-sharp3
Version: 2.99.3-4.1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

gtk-sharp3 builds an Architecture: all packages depending on a  


library package involved in the time_t 64 transition. This dependency   

   
needs to be updated. 

Cheers
-- 
Sebastian Ramacher

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

[Sebastian Ramacher]

Source: globus-gram-job-manager-scripts
Version: 7.3-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

globus-gram-job-manager-scripts builds an Architecture: all packages
depending on a library package involved in the time_t 64 transition.
This dependency needs to be updated. 

Cheers
-- 
Sebastian Ramacher

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

[Sebastian Ramacher]

Source: globus-gram-audit
Version: 5.1-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

globus-gram-audit builds an Architecture: all packages depending on a
library package involved in the time_t 64 transition. This dependency
needs to be updated.

Cheers
-- 
Sebastian Ramacher

Bug#1067304: closing 1067304

[Sebastian Ramacher]

# this was a transient issues
close 1067304 
thanks


-- 
Sebastian Ramacher

Processed: closing 1067304

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # this was a transient issues
> close 1067304
Bug #1067304 [src:gmsh] gmsh: FTBFS: unsatisfiable build-dependencies
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1067494: marked as done (obs-studio: FTBFS on time64_t archs)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 13:39:07 +
with message-id 
and subject line Bug#1067494: fixed in obs-studio 30.0.2+dfsg-3
has caused the Debian Bug report #1067494,
regarding obs-studio: FTBFS on time64_t archs
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.)


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

Package: obs-studio
Version: 30.0.2+dfsg-2.1
Severity: serious



Hello, looks like we got a failure due to time64_t transition.

/usr/bin/cc -DENABLE_HEVC -DHAVE_OBSCONFIG_H -DHAVE_UDEV -Dlinux_v4l2_EXPORTS -I/<>/libobs 
-I/<>/obj-arm-linux-gnueabihf/config -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/obs-studio-30.0.2+dfsg-2.1build2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
-Wdate-time -D_FORTIFY_SOURCE=3 -DFFMPEG_MUX_FIXED=\"/usr/lib/arm-linux-gnueabihf/obs-plugins/obs-ffmpeg/obs-ffmpeg-mux\" 
-DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -fvisibility=hidden -Wno-error=deprecated-declarations -std=gnu17 -fPIC -Werror -Wextra -Wvla -Wno-error=vla 
-Wswitch -Wno-error=switch -Wformat -Wformat-security -Wunused-parameter -Wno-unused-function -Wno-missing-field-initializers -fno-strict-aliasing 
-Werror-implicit-function-declaration -Wno-missing-braces -Wno-error=maybe-uninitialized -DSIMDE_ENABLE_OPENMP -fopenmp-simd -MD -MT 
plugins/linux-v4l2/CMakeFiles/linux-v4l2.dir/v4l2-input.c.o -MF plugins/linux-v4l2/CMakeFiles/linux-v4l2.dir/v4l2-input.c.o.d -o 
plugins/linux-v4l2/CMakeFiles/linux-v4l2.dir/v4l2-input.c.o -c /<>/plugins/linux-v4l2/v4l2-input.c
/<>/plugins/linux-v4l2/v4l2-input.c: In function ‘v4l2_thread’:
/<>/plugins/linux-v4l2/v4l2-input.c:66:43: error: format ‘%ld’ 
expects argument of type ‘long int’, but argument 4 has type ‘__suseconds64_t’ {aka ‘long 
long int’} [-Werror=format=]
   66 | #define blog(level, msg, ...) blog(level, "v4l2-input: " msg, 
##__VA_ARGS__)
  |   ^~
/<>/plugins/linux-v4l2/v4l2-input.c:262:17: note: in expansion of 
macro ‘blog’
  262 | blog(LOG_DEBUG,
  | ^~~~
cc1: all warnings being treated as errors
[137/484] /usr/bin/cc -DENABLE_HEVC -DHAVE_OBSCONFIG_H -Dlinux_jack_EXPORTS -I/<>/libobs 
-I/<>/obj-arm-linux-gnueabihf/config -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/obs-studio-30.0.2+dfsg-2.1build2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
-Wdate-time -D_FORTIFY_SOURCE=3 -DFFMPEG_MUX_FIXED=\"/usr/lib/arm-linux-gnueabihf/obs-plugins/obs-ffmpeg/obs-ffmpeg-mux\" 
-DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -fvisibility=hidden -Wno-error=deprecated-declarations -std=gnu17 -fPIC -Werror -Wextra -Wvla -Wno-error=vla 
-Wswitch -Wno-error=switch -Wformat -Wformat-security -Wunused-parameter -Wno-unused-function -Wno-missing-field-initializers -fno-strict-aliasing 
-Werror-implicit-function-declaration -Wno-missing-braces -Wno-error=maybe-uninitialized -DSIMDE_ENABLE_OPENMP -fopenmp-simd -MD -MT 
plugins/linux-jack/CMakeFiles/linux-jack.dir/linux-jack.c.o -MF plugins/linux-jack/CMakeFiles/linux-jack.dir/linux-jack.c.o.d -o 
plugins/linux-jack/CMakeFiles/linux-jack.dir/linux-jack.c.o -c /<>/plugins/linux-jack/linux-jack.c


I did "fix" with an ugly hacky patch, just for armhf platform, but I don't know 
how to properly solve it.

diff -Nru obs-studio-30.0.2+dfsg/debian/patches/time64.patch 
obs-studio-30.0.2+dfsg/debian/patches/time64.patch
--- obs-studio-30.0.2+dfsg/debian/patches/time64.patch  1970-01-01 
01:00:00.0 +0100
+++ obs-studio-30.0.2+dfsg/debian/patches/time64.patch  2024-03-22 
13:31:40.0 +0100
@@ -0,0 +1,18 @@
+Description: Use time64_t everywhere
+Author: Gianfranco Costamagna 
+Last-Update: 2024-03-21
+
+--- obs-studio-30.0.2+dfsg.orig/plugins/linux-v4l2/v4l2-input.c
 obs-studio-30.0.2+dfsg/plugins/linux-v4l2/v4l2-input.c
+@@ -260,7 +260,11 @@ static void *v4l2_thread(void *vptr)
+   }
+
+   blog(LOG_DEBUG,
++#ifndef __arm__
+"%s: ts: %06ld buf id #%d, flags 0x%08X, seq #%d, len %d, used 
%d",
++#else
++   "%s: ts: %06lld buf id #%d, flags 0x%08X, seq #%d, len %d, used 
%d",
++#endif
+data->device_id, buf.timestamp.tv_usec, buf.index,
+

Processed: Bug#1067494 marked as pending in obs-studio

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067494 [obs-studio] obs-studio: FTBFS on time64_t archs
Added tag(s) pending.

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

Bug#1067494: marked as pending in obs-studio

[Benjamin Drung]

Control: tag -1 pending

Hello,

Bug #1067494 in obs-studio 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/multimedia-team/obs-studio/-/commit/d2e749f44f2ceae49bd606a1ca2920484a42be9f


Fix build on 32bit time64_t archs

Closes: #1067494
Thanks: Gianfranco Costamagna 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067494

Bug#1067942: marked as done (Depends on pre-t64 libglib2.0-0)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 12:50:08 +
with message-id 
and subject line Bug#1067942: fixed in ibus 1.5.29-2
has caused the Debian Bug report #1067942,
regarding Depends on pre-t64 libglib2.0-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.)


-- 
1067942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ibus
Version: 1.5.29-1+b1
Severity: serious

ibus has an explicit Depends: libglib2.0-0, this needs to be changed to
libglib2.0-0t64.


-- Package-specific info:
ibus is /usr/bin/ibus
ibus-setup is /usr/bin/ibus-setup
!
!!! im-config is missing.  Please install it. !!!
!!! Please also read usr/share/doc/im-config/README.Debian.gz !!!
!

XMODIFIERS=
GTK_IM_MODULE=
QT_IM_MODULE=
WAYLAND_DISPLAY=
XDG_CURRENT_DESKTOP=KDE
XDG_MENU_PREFIX=
XDG_RUNTIME_DIR=/run/user/1000
XDG_SEAT=seat0
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=KDE
XDG_SESSION_ID=3
XDG_SESSION_TYPE=x11

== ls -l /usr/lib/ibus/ibus-* /usr/libexec/ibus-* ==
/bin/ls: cannot access '/usr/lib/ibus/ibus-*': No such file or directory
-rwxr-xr-x 1 root root  22832 Mar 13 06:45 /usr/libexec/ibus-dconf
-rwxr-xr-x 1 root root  14640 Mar 13 06:45 /usr/libexec/ibus-engine-simple
-rwxr-xr-x 1 root root 170288 Mar 13 06:45 /usr/libexec/ibus-extension-gtk3
-rwxr-xr-x 1 root root  18736 Mar 13 06:45 /usr/libexec/ibus-memconf
-rwxr-xr-x 1 root root  96560 Mar 13 06:45 /usr/libexec/ibus-portal
-rwxr-xr-x 1 root root 121144 Mar 13 06:45 /usr/libexec/ibus-ui-emojier
-rwxr-xr-x 1 root root 371232 Mar 13 06:45 /usr/libexec/ibus-ui-gtk3
-rwxr-xr-x 1 root root 100280 Mar 13 06:45 /usr/libexec/ibus-x11

== dpkg-query -l 'ibus*' ==
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---==
ii  ibus   1.5.29-1+b1  amd64Intelligent Input Bus - core
un  ibus-clutter (no description available)
ii  ibus-data  1.5.29-1 all  Intelligent Input Bus - data files
un  ibus-doc (no description available)
un  ibus-gtk (no description available)
un  ibus-gtk3(no description available)
un  ibus-gtk4(no description available)

=== gsettings ===
org.freedesktop.ibus.general dconf-preserve-name-prefixes 
['/desktop/ibus/engine/pinyin', '/desktop/ibus/engine/bopomofo', 
'/desktop/ibus/engine/hangul']
org.freedesktop.ibus.general embed-preedit-text true
org.freedesktop.ibus.general enable-by-default false
org.freedesktop.ibus.general engines-order @as []
org.freedesktop.ibus.general preload-engines @as []
org.freedesktop.ibus.general switcher-delay-time 400
org.freedesktop.ibus.general use-global-engine true
org.freedesktop.ibus.general use-system-keyboard-layout false
org.freedesktop.ibus.general use-xmodmap true
org.freedesktop.ibus.general version ''
org.freedesktop.ibus.general xkb-latin-layouts ['af', 'af(fa-olpc)', 
'af(ps-olpc)', 'af(ps)', 'af(uz)', 'af(uz-olpc)', 'am', 'am(eastern)', 
'am(eastern-alt)', 'am(phonetic)', 'am(phonetic-alt)', 'am(western)', 'ara', 
'ara(azerty)', 'ara(azerty_digits)', 'ara(buckwalter)', 'ara(digits)', 
'ara(qwerty)', 'ara(qwerty_digits)', 'az(cyrillic)', 'bd', 'bd(probhat)', 'bg', 
'bg(bas_phonetic)', 'bg(phonetic)', 'brai', 'brai(left_hand)', 
'brai(right_hand)', 'bt', 'by', 'by(phonetic)', 'by(legacy)', 'ca(ike)', 
'cn(tib)', 'cn(tib_asciinum)', 'cn(ug)', 'cz', 'cz(ucw)', 'de(ru)', 'dev', 
'et', 'fr(geo)', 'ge', 'ge(os)', 'gr', 'gr(extended)', 'gr(nodeadkeys)', 
'gr(polytonic)', 'gr(simple)', 'gur', 'il', 'il(biblical)', 'il(lyx)', 
'il(phonetic)', 'id(melayu-phonetic)', 'id(melayu-phoneticx)', 
'id(pegon-phonetic)', 'in', 'in(ben)', 'in(ben_baishakhi)', 'in(ben_bornona)', 
'in(ben_gitanjali)', 'in(ben_inscript)', 'in(ben_probhat)', 'in(bolnagri)', 
'in(deva)', 'in(guj)', 'in(guj-kagapa)', 'in(guru)', 'in(hin-kagapa)', 
'in(hin-wx)', 'in(jhelum)', 'in(kan)', 'in(kan-kagapa)', 'in(mal)', 
'in(mal_enhanced)', 'in(mal_lalitha)', 'in(mar-kagapa)', 'in(ori)', 
'in(san-kagapa)', 'in(tam)', 'in(tamilnet)', 'in(tamilnet_TAB)', 
'in(tamilnet_TSCII)', 'in(tamilnet_tamilnumbers)', 'in(tam_tamilnumbers)', 
'in(tel)', 'in(tel-kagapa)', 'in(urd-phonetic)', 

Bug#1060407: gtkwave update for {bookworm,bullseye,buster}-security

[Moritz Mühlenhoff]

Hi Adrian,

> attached are proposed debdiffs for updating gtkwave to 3.3.118 in
> {bookworm,bullseye,buster}-security for review for a DSA
> (and as preview for buster).

Thanks!

> General notes:
> 
> I checked a handful CVEs, and they were also present in buster.
> If anyone insists that I check for every single CVE whether it is also
> in buster I can do that, but that would be a lot of work.

Nah, no need.

> As mentioned in #1060407 there are different tarballs for GTK 2 and GTK 3.
> Looking closer I realized that this is actually one tarball that 
> supports GTK 1+2, and one tarball that supports GTK 2+3.
> I did stay at the GTK 1+2 tarball that was already used before 
> for bullseye and buster since there was anyway a different upstream 
> tarball required for the +really version that is required to avoid 
> creating file conflicts with ghwdump when upgrading to bookworm.
> 
> What does the security team consider the best versioning for bullseye?
> In #1060407 I suggested 3.3.104+really3.3.118-0.1, but now I ended up
> preferring 3.3.104+really3.3.118-0+deb11u1

That's fine.

> debdiffs contain only changes to debian/

The bookworm/bullseye debdiffs looks good, please upload to security-master, 
thanks!

Note that both need -sa, but dak needs some special attention when
uploading to security-master. You'll need to wait for the ACCEPTED mail
before you can upload the next one.

Cheers,
Moritz

Bug#1068121: marked as done (python-fusepy: hard-coded dependencies on pre-t64 libraries)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 11:47:36 +
with message-id 
and subject line Bug#1068121: fixed in python-fusepy 3.0.1-5
has caused the Debian Bug report #1068121,
regarding python-fusepy: hard-coded dependencies on pre-t64 libraries
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.)


-- 
1068121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fusepy
Version: 3.0.1-4
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

python-fusepy builds binary packages with hardcoded dependencies on
shared library packages that were renamed as part of the time_t 64
transition. The dependencies need to be updated for this change - or if
possible - changed to be generated by debhelper.

There's a patch available from Ubuntu: 
https://patches.ubuntu.com/p/python-fusepy/python-fusepy_3.0.1-4ubuntu1.patch

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: python-fusepy
Source-Version: 3.0.1-5
Done: Sascha Steinbiss 

We believe that the bug you reported is fixed in the latest version of
python-fusepy, 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.
Sascha Steinbiss  (supplier of updated python-fusepy 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, 31 Mar 2024 12:32:20 +0200
Source: python-fusepy
Architecture: source
Version: 3.0.1-5
Distribution: unstable
Urgency: medium
Maintainer: Sascha Steinbiss 
Changed-By: Sascha Steinbiss 
Closes: 1068121
Changes:
 python-fusepy (3.0.1-5) unstable; urgency=medium
 .
   * Avoid hard-coding run-time dependency on shared library.
 Thanks to Matthias Klose for the patch from Ubuntu.
 Closes: #1068121
   * Bump copyright dates for debian/ directory.
   * Add Repository* to d/upstream/metadata.
   * Bump Standards-Version.
   * Add Rules-Requires-Root: no.
Checksums-Sha1:
 4d5acfa96a176a5b1cb01c1832c3af7e28316a5f 1981 python-fusepy_3.0.1-5.dsc
 c6230eaca1c9f7c3eb53b6b09d59b68522a8191f 2732 
python-fusepy_3.0.1-5.debian.tar.xz
 1cc8e2f969a09c78c2d67616c7ffe97dafe82334 6958 
python-fusepy_3.0.1-5_amd64.buildinfo
Checksums-Sha256:
 a394634761f8beb0319347d01cd68ccfc4f8c9198cdebdca40ab824e04ea670e 1981 
python-fusepy_3.0.1-5.dsc
 f280bcfe89560807d36f0e2c9751f744d4b84d2fa9227c3699b21ddd103b518c 2732 
python-fusepy_3.0.1-5.debian.tar.xz
 93c69301a675ba1962e98f221889aad820ef3d957c37a01e7f607df7c5a6b509 6958 
python-fusepy_3.0.1-5_amd64.buildinfo
Files:
 c0d3987f7301e2a80c67d847c6d08316 1981 python optional python-fusepy_3.0.1-5.dsc
 0f11fda3300f8995820ac52ff39670ff 2732 python optional 
python-fusepy_3.0.1-5.debian.tar.xz
 1921fc06c2425b045d00ed92f147b336 6958 python optional 
python-fusepy_3.0.1-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEWzS6WqtVB+kDQm6F6NN64vCfSHIFAmYJP68ACgkQ6NN64vCf
SHI4OQ//e8yh/9pomzbxZU1U+Zs81G4z8F/LsRaS5wRmEFm3jy1AyM1VEyu6kIWw
6FeKVZY621oOomVrQceNRvJySVmyUzT3Q1pXuAAVMUr8XBSfXxgxN+LJ0FwN3E7l
eZJocLrr32V+WxoR1jH4QJo/r5qCoToCIV5ltxCoUKSpduNGQCBVRz2mTQihRrWO
WDHYeC/aHPixbSEXcVr78fupmA6cegY0wAbSXHufXC7umwuAadeg/O+RNx933S87
RPTrNF72pgh/0khxi/npmbrTxGK77gNHSHqrxaLNhQrsxlb0qsockzkyCVv8GWy/
XgVDmoY5XIPstB5/j6sIb7suZYAFjZ/PNGeJVR0pj7KmPNLLUs6G1ocl4Qh9Nfgx
ucDVXeFw3c8k1FCd7xxyI7ymnOZ49qq4GBTZpJZtB3l6clhcfSnKKtjhbTpGx74l
g8iBgWZhwt2XwQJmfGqWHcOK+gIy+hKFJUNQHMN801IzI7jIaB8Ytiv6XrRDiNR4
Z1HT/Ye7AuKSn9rrTQYPyLtiMcpH8INr843Vxa1Vrz8cIHeOUAA8WoHDA63GKVnK
bgaPJprzNhgf6QEuo5Fshc8LR+JqRGwCVp+0mJWI78nC5skxCdtIYJsW2NgX/4jo
Vf6K10AksF7AOG4UQa+S13TtKfZj3W5x1RUSra5uu6/6vxQbgLs=
=R7n5
-END PGP SIGNATURE-



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

Bug#1056861: marked as done (python-llfuse: ftbfs with cython 3.0.x)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 11:08:51 +
with message-id 
and subject line Bug#1056861: fixed in python-llfuse 1.4.1+dfsg-3
has caused the Debian Bug report #1056861,
regarding python-llfuse: ftbfs with cython 3.0.x
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.)


-- 
1056861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-llfuse
Version: 1.4.1+dfsg-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: cython3

[This bug is targeted to the upcoming trixie release]

The package fails to build in a test rebuild on at least arm64 with
cython 3.0.5, but succeeds to build with cython 0.29.36.  Please
update the package to build with cython 3.0.5 (available in experimental).

If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable).  There is no replacement for cython3-dbg.

Build logs building with cython 3.0.5 can be found at
https://people.debian.org/~stefanor/cython3/cython-3.0.5/

See also https://lists.debian.org/debian-python/2023/11/msg00034.html
--- End Message ---
--- Begin Message ---
Source: python-llfuse
Source-Version: 1.4.1+dfsg-3
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
python-llfuse, 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 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated python-llfuse 
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, 31 Mar 2024 10:46:48 +0200
Source: python-llfuse
Built-For-Profiles: noudeb
Architecture: source
Version: 1.4.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Nikolaus Rath 
Changed-By: Sebastian Ramacher 
Closes: 1056861
Changes:
 python-llfuse (1.4.1+dfsg-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Debian Janitor ]
   * Update standards version to 4.6.1, no changes needed.
 .
   [ Bas Couwenberg ]
   * Switch to cython3-legacy. (Closes: #1056861)
 .
   [ Sebastian Ramacher ]
   * Remove left-overs from dbgsym migration
Checksums-Sha1:
 efaff444fa5c203b5d5ca877f8af29d0a9efaa87 1778 python-llfuse_1.4.1+dfsg-3.dsc
 437f3e17c1fcf23b363a81296f15cf8a44174b8f 144840 
python-llfuse_1.4.1+dfsg-3.debian.tar.xz
 595367339c42b4b8874852c0cfc86cc88a24d394 9420 
python-llfuse_1.4.1+dfsg-3_source.buildinfo
Checksums-Sha256:
 b2f45d5cf11aa1d2bd779ff4a1f02b8aedfc30b3c9ed272cf1e01a38c73660f7 1778 
python-llfuse_1.4.1+dfsg-3.dsc
 893cc4e80924996de0c7b9e163893a81fdc5cb5af8394f2a4941b9d7d490903d 144840 
python-llfuse_1.4.1+dfsg-3.debian.tar.xz
 d7d3a4ac687a4f56b9374dd39544911d2ac3493c21f2779f5f2dcd1fa5c19ba3 9420 
python-llfuse_1.4.1+dfsg-3_source.buildinfo
Files:
 ea9d69ade7503f2b468393e42bc6dc75 1778 python optional 
python-llfuse_1.4.1+dfsg-3.dsc
 851dd0f3979ca495f2a306fee59d6c81 144840 python optional 
python-llfuse_1.4.1+dfsg-3.debian.tar.xz
 ed956c868d0dfb9337084ad74a63a529 9420 python optional 
python-llfuse_1.4.1+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iIsEARYIADMWIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZgkjvhUcc3JhbWFjaGVy
QGRlYmlhbi5vcmcACgkQIZNrNmAPzYkj+wEA6LyKBSnIsgrRuD1r/CnrjNPABYx1
TfN0+hRnPHDDP98A/jUYVqtI0Ix9T3vftzU+CYJpAZyMWm/GJJPEVNBYa7kA
=fc0N
-END PGP SIGNATURE-



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

Bug#1062404: marked as done (orthanc-python: flaky autopkgtest: Test failed with)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 11:06:09 +
with message-id 
and subject line Bug#1062404: fixed in orthanc-python 4.1+ds-3
has caused the Debian Bug report #1062404,
regarding orthanc-python: flaky autopkgtest: Test failed with
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.)


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

Source: orthanc-python
Version: 4.1+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails on several architectures because it currently 
blocks glibc. Unfortunately the log seems to be missing the actual 
problem as it ends with:
 45s W0131 12:12:35.955520 MAIN FromDcmtkBridge.cpp:382] 
Loading external DICOM dictionary: "/usr/share/libdcmtk17/private.dic"

 45s Test failed with

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

E.g.
https://ci.debian.net/packages/o/orthanc-python/testing/amd64/42028712/
https://ci.debian.net/packages/o/orthanc-python/testing/s390x/42546158/
https://ci.debian.net/packages/o/orthanc-python/testing/ppc64el/42417046/


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: orthanc-python
Source-Version: 4.1+ds-3
Done: Sebastien Jodogne 

We believe that the bug you reported is fixed in the latest version of
orthanc-python, 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 1062...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Jodogne  (supplier of updated orthanc-python 
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, 30 Mar 2024 14:06:27 +0100
Source: orthanc-python
Architecture: source
Version: 4.1+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sebastien Jodogne 
Closes: 1062404
Changes:
 orthanc-python (4.1+ds-3) unstable; urgency=medium
 .
   * autopkgtest: Fix the waiting for Orthanc to start. Closes: #1062404
Checksums-Sha1:
 d4c0fd78fe94264fcf57badc7d41b01a9bc52d7a 2244 orthanc-python_4.1+ds-3.dsc
 c0f40ecf86e7e5c938ffc7050eef44fe3585043c 5348 
orthanc-python_4.1+ds-3.debian.tar.xz
 ec9edb757f2b45319097714ac6b7a0ca3dc7e474 15899 
orthanc-python_4.1+ds-3_source.buildinfo
Checksums-Sha256:
 78ca1192b4b53e92ef37dcc2780651f67c40f06290b96e7af291ba3d121e19ba 2244 
orthanc-python_4.1+ds-3.dsc
 7ba92e0785669ec42ee65abe035d6bbce1b68997493b34c711393c28853b6d0f 5348 
orthanc-python_4.1+ds-3.debian.tar.xz
 33607bf8402958328de04604acfd64e809810879de45682e986f7d94e779231c 15899 
orthanc-python_4.1+ds-3_source.buildinfo
Files:
 4d70c4c1d0adb58e0978ecfd8dba4ae8 2244 science optional 
orthanc-python_4.1+ds-3.dsc
 6d01dee147b14bfb9eea35f40945cd1f 5348 science optional 
orthanc-python_4.1+ds-3.debian.tar.xz
 863055c4c40dc0a4e88cac2d643af3bc 15899 science optional 
orthanc-python_4.1+ds-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAmYIIowUHHMuam9kb2du
ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw12vMw//SpWQ3Ku5wLGv693eTDInB+7CbHsX
JRFEFLwucBUe/dk7FcTXvxcCijBAdd397//BJIoUd+RN5pdQR4lPkYDbBmSRX5QU
ZLa61+mE/KfM55zht5yOfB8cW3tmcFMlWIrmCpFOnN/2JP3/UbJHhvf84W8IVQ/G
kcI+SGalV2OwczjIInxHFsRSw2hICejIEtzjC1gp3xD7pNINHealHqHO8F+calFC
km+MYR74hT8kZ6kFyL00nKts+cygBazdzXJehGyXnih//t2bWyMzxdC63zVWpyvS
sz7Fj+w59TYyrkVxArOWqQ3OqUtus+YIUJnJKYcGPzxQ5dh4zvnxikzm5O4GpI0G
lgvrl9H10Z1ZygGxPl35I2Fk98y2RH6j1fP8Eo+dBkTywsced7OV6Xa9gH13ItM4
eB58Ges7N7WUN2ph8a0EKEFm27H+VW8oX7o1NRjpmUAk/JEsXMxGFao/lNWpNFgT
evDL5dqsl6PzkW8sKS/UYUhCgnHCyxzANMkTojkpuxfruw3CJ/eJ1uQM3ghL6V2I
3H+Onsd7z3nqXOxBpG01fVVg6k2TX0goyOV3a5pz4FBHaU1IJhpXZfGGwY8qvs/q

Bug#1014781: marked as done (momd crashing due to error in HypervisorInterfaces/libvirtInterface.py)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 10:58:05 +
with message-id 
and subject line Bug#1014781: fixed in mom 0.6.4-0.1
has caused the Debian Bug report #1014781,
regarding momd crashing due to error in HypervisorInterfaces/libvirtInterface.py
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.)


-- 
1014781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mom
Version: 0.6.0-2
Severity: grave
Tags: patch
Justification: renders package unusable

Hello Dear Maintainer,

Looks like momd is "broken" in bullseye :-(
Service is failling every start with exception :
Jul 11 20:48:21 minas-anor momd[149966]:   File 
"/usr/lib/python3/dist-packages/mom/HypervisorInterfaces/libvirtInterface.py", 
line 128, in _domainGetPid
Jul 11 20:48:21 minas-anor momd[149966]: matches = 
re.findall(r"^\s*(\d+)\s+.*" + uuid, p1, re.M)
Jul 11 20:48:21 minas-anor momd[149966]:   File 
"/usr/lib/python3.9/re.py", line 241, in findall
Jul 11 20:48:21 minas-anor momd[149966]: return _compile(pattern, 
flags).findall(string)
Jul 11 20:48:21 minas-anor momd[149966]: TypeError: cannot use a string 
pattern on a bytes-like object

Comparing with current code for libvirtInterface.py in mom github 
https://github.com/oVirt/mom/blob/master/mom/HypervisorInterfaces/libvirtInterface.py
I made modification in libvirtInterface.py line 128
#p1 = Popen(["ps", "axww"], stdout=PIPE).communicate()[0]
p1 = Popen(["ps", "axww"], stdout=PIPE).communicate()[0].decode("utf-8")

Sorry for not attaching a patch file, not sure it is needed for this change

After this little change momd is now working correctly and tacking care of VM 
ballooning :-)

For the moment, i'm only using KVM + momd + balloning on test servers
(that's why i only discovered the issue now)
don't know if some other users are impacted in production.
I suppose bug is related to python 3.9, but not shure at all

Think a little "patch" release will be needed for debian package


Thank you for your time maintaining debian :-))




Here more complete log extract if needed
Jul 11 20:48:21 minas-anor momd[149966]: 2022-07-11 20:48:21,840 - 
mom.GuestManager - ERROR - Guest Manager crashed
Jul 11 20:48:21 minas-anor momd[149966]: Traceback (most recent call last):
Jul 11 20:48:21 minas-anor momd[149966]:   File 
"/usr/lib/python3/dist-packages/mom/GuestManager.py", line 86, in run
Jul 11 20:48:21 minas-anor momd[149966]: 
self._spawn_guest_monitors(domain_list)
Jul 11 20:48:21 minas-anor momd[149966]:   File 
"/usr/lib/python3/dist-packages/mom/GuestManager.py", line 112, in 
_spawn_guest_monitors
Jul 11 20:48:21 minas-anor momd[149966]: info = 
self.hypervisor_iface.getVmInfo(id)
Jul 11 20:48:21 minas-anor momd[149966]:   File 
"/usr/lib/python3/dist-packages/mom/HypervisorInterfaces/libvirtInterface.py", 
line 189, in getVmInfo
Jul 11 20:48:21 minas-anor momd[149966]: data['pid'] = 
self._domainGetPid(data['uuid'])
Jul 11 20:48:21 minas-anor momd[149966]:   File 
"/usr/lib/python3/dist-packages/mom/HypervisorInterfaces/libvirtInterface.py", 
line 128, in _domainGetPid
Jul 11 20:48:21 minas-anor momd[149966]: matches = 
re.findall(r"^\s*(\d+)\s+.*" + uuid, p1, re.M)
Jul 11 20:48:21 minas-anor momd[149966]:   File "/usr/lib/python3.9/re.py", 
line 241, in findall
Jul 11 20:48:21 minas-anor momd[149966]: return _compile(pattern, 
flags).findall(string)
Jul 11 20:48:21 minas-anor momd[149966]: TypeError: cannot use a string pattern 
on a bytes-like object
Jul 11 20:48:26 minas-anor momd[149966]: 2022-07-11 20:48:26,825 - mom - ERROR 
- Thread 'GuestManager' has exited



-- System Information:
Debian Release: 11.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/6 CPU threads)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mom depends on:
ii  libvirt-daemon 7.0.0-3
ii  libvirt-daemon-system  7.0.0-3
ii  procps 2:3.3.17-5
ii  python33.9.2-3
ii  python3-libvirt7.0.0-2
ii  python3-six1.16.0-2

mom recommends no packages.

mom suggests no packages.

-- Configuration Files:
/etc/momd.conf changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mom
Source-Version: 

Bug#1068047: marked as done (Suspicious commit merged in 2021 from account responsible for xz backdoor)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 10:46:58 +
with message-id 
and subject line Bug#1068047: fixed in libarchive 3.7.2-2
has caused the Debian Bug report #1068047,
regarding Suspicious commit merged in 2021 from account responsible for xz 
backdoor
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.)


-- 
1068047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libarchive13t64
Version: 3.7.2-1.1
Severity: important
X-Debbugs-Cc: r...@debian.org

So far it looks like no one has been able to figure out an obvious way
for this to be exploitable, but I wanted to make sure that you were
aware of this upstream issue:

https://github.com/libarchive/libarchive/pull/1609

The author of this commit is the same GitHub account that was used to
create the xz backdoor. Upstream has merged a revert of this change at:

https://github.com/libarchive/libarchive/pull/2101

It may be worth expediting getting this change into Debian in case the
potential attacker knows something that we don't. However, I don't have
any reason to currently believe that this is a security vulnerability,
so I've kept the severity at important and not applied the security tag.


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

Kernel: Linux 6.7.9-amd64 (SMP w/8 CPU threads; PREEMPT)
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

Versions of packages libarchive13t64 depends on:
ii  libacl12.3.2-1
ii  libbz2-1.0 1.0.8-5.1
ii  libc6  2.37-15.1
ii  liblz4-1   1.9.4-1+b2
ii  liblzma5   5.6.1+really5.4.5-1
ii  libnettle8t64  3.9.1-2.2
ii  libxml22.9.14+dfsg-1.3+b2
ii  libzstd1   1.5.5+dfsg2-2
ii  zlib1g 1:1.3.dfsg-3.1

libarchive13t64 recommends no packages.

Versions of packages libarchive13t64 suggests:
pn  lrzip  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libarchive
Source-Version: 3.7.2-2
Done: Peter Pentchev 

We believe that the bug you reported is fixed in the latest version of
libarchive, 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.
Peter Pentchev  (supplier of updated libarchive 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, 30 Mar 2024 20:11:06 +0200
Source: libarchive
Architecture: source
Version: 3.7.2-2
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev 
Changed-By: Peter Pentchev 
Closes: 1068047
Changes:
 libarchive (3.7.2-2) unstable; urgency=medium
 .
   [ Luca Boccassi ]
   * libarchive-dev: depend on -dev packages in an attempt to
 fix pkg-config --static --libs
 Addresses: 1056317; more work needed on libarchive's own
 configure tests
 .
   [ Peter Pentchev ]
   * Acknowledge Lukas Märdian 64-bit-time_t-related NMU. Thanks!
   * Add the year 2024 to my debian/* copyright notice.
   * Re-sort the dependencies lists in the debian/control file.
   * Switch the pkg-config dependency over to pkgconf.
   * Add the robust-error-reporting upstream patch. Closes: #1068047
Checksums-Sha1:
 a9840b89785c21b07962f5560890a62b70f17b54 2714 libarchive_3.7.2-2.dsc
 d8a0948b6814ee525e85ec44003af28470f84f15 27352 libarchive_3.7.2-2.debian.tar.xz
Checksums-Sha256:
 9fd4fe779a50bf73660bf59b3af0c6c8cbe32bcb48b4b8922eb23cd90d9bde9c 2714 
libarchive_3.7.2-2.dsc
 cb596068a92fe55060ea5e46a5da8c9e9cd37b03a17bff7bc3cea62baa1c455e 27352 
libarchive_3.7.2-2.debian.tar.xz
Files:
 dec84a91f32a212810d5a4072bc0fb15 2714 libs optional libarchive_3.7.2-2.dsc
 a09a0817264db40619efeacb80a8d304 27352 libs optional 
libarchive_3.7.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmYIWTYQHHJvYW1AZGVi
aWFuLm9yZwAKCRBlHu+wJSffE/3WD/0Y9dKqonT5upiqkcr2XIRTlKXOoPgQvh+T

Bug#1067272: marked as done (haskell-gi-glib: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 10:43:57 +
with message-id 
and subject line Bug#1067272: fixed in haskell-haskell-gi 0.26.7-4
has caused the Debian Bug report #1067272,
regarding haskell-gi-glib: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] Error 1
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.)


-- 
1067272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-gi-glib
Version: 2.0.29-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-gi-glib-doc.substvars
> dh_installdirs -plibghc-gi-glib-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.hs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe'
> Running find . ! -newer /tmp/CDluqVSv3P -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-gi-glib-dev
> libghc-gi-glib-prof
> libghc-gi-glib-doc
> Running dh_listpackages
> libghc-gi-glib-dev
> libghc-gi-glib-prof
> libghc-gi-glib-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/gi-glib-2.0.29/ --datasubdir=gi-glib 
> --htmldir=/usr/share/doc/libghc-gi-glib-doc/html/ --enable-library-profiling
> Non-zero exit code 1.
> Using Parsec parser
> ERROR: couldn't find API description for GLib.time_t
> Please report this at https://github.com/haskell-gi/haskell-gi/issues
> CallStack (from HasCallStack):
>   error, called at lib/Data/GI/CodeGen/Util.hs:126:6 in 
> haskell-gi-0.26.7-C46MepbmwZA1H8dt48knUn:Data.GI.CodeGen.Util
>   terror, called at lib/Data/GI/CodeGen/Code.hs:556:13 in 
> haskell-gi-0.26.7-C46MepbmwZA1H8dt48knUn:Data.GI.CodeGen.Code
>   findAPIByName, called at lib/Data/GI/CodeGen/GObject.hs:17:44 in 
> haskell-gi-0.26.7-C46MepbmwZA1H8dt48knUn:Data.GI.CodeGen.GObject
>  at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 109.
>   
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
>  "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d", 
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib", 
> "--libexecdir=/usr/lib", ...) called at 
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 133
>   
> Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
>  "configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d", 
> "--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib", 
> "--libexecdir=/usr/lib", ...) called at 
> /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 637
>   Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe() 
> called at -e line 1
> make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: configure-ghc-stamp] 
> Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/haskell-gi-glib_2.0.29-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240319;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240319=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.

Bug#1068043: marked as done (BinNMU 1.11-1+b1 depends on both, libmspack0 and libmspack0t64, and is hence uninstallable (at least on armhf))

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 10:36:56 +
with message-id 
and subject line Bug#1068043: fixed in cabextract 1.11-2
has caused the Debian Bug report #1068043,
regarding BinNMU 1.11-1+b1 depends on both, libmspack0 and libmspack0t64, and 
is hence uninstallable (at least on 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.)


-- 
1068043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cabextract
Version: 1.11-1
Severity: serious
X-Debbugs-Cc: a...@debian.org

>From aptitude's dependency view on armhf:

iFA (pin --\ cabextract   0   72.7 kB  1.11-1  1.11-1+b1
  --\ Depends (3)
--- libc6 (>= 2.34)
--- libmspack0 (>= 0.9.1-1)
--- libmspack0t64 (>= 0.4) (UNSATISFIED)

As libmspack0t64 breaks libmspack0 they can't be installed together.

This is likely caused by hardcoding a dependency on libmspack0 in
debian/control:

https://sources.debian.org/src/cabextract/1.11-1/debian/control/#L10

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'buildd-unstable'), (500, 'testing'), (110, 'experimental'), (1, 
'experimental-debug'), (1, 'buildd-experimental')
Architecture: armhf (armv7l)

Kernel: Linux 6.6.15-armmp-lpae (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages cabextract depends on:
ii  libc6   2.37-15.1
ii  libmspack0  0.11-1

cabextract recommends no packages.

cabextract suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cabextract
Source-Version: 1.11-2
Done: Eric Sharkey 

We believe that the bug you reported is fixed in the latest version of
cabextract, 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.
Eric Sharkey  (supplier of updated cabextract 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, 30 Mar 2024 20:21:18 -0400
Source: cabextract
Architecture: source
Version: 1.11-2
Distribution: unstable
Urgency: low
Maintainer: Eric Sharkey 
Changed-By: Eric Sharkey 
Closes: 1068043
Changes:
 cabextract (1.11-2) unstable; urgency=low
 .
   * Remove hard-coded versioned dependency on libmspack0 to resolve
 dependency problem on armhf architecture: Closes: #1068043
Checksums-Sha1:
 7ba445f8adb5d70028db0c8429e1a6392e612e51 1719 cabextract_1.11-2.dsc
 3d3841c7c09f2d91c564f5988f80a836744453a7 6728 cabextract_1.11-2.debian.tar.xz
 6c7133c946b36bd87b15260e4ab3872a623d592c 7818 cabextract_1.11-2_amd64.buildinfo
Checksums-Sha256:
 4ad4989b6c192b5f6e3929be4185e537fcfcdbce467b2c68206ffbb85dba3a63 1719 
cabextract_1.11-2.dsc
 4e39c5c1768035ccc7e25c0e67d82c5fe8cef4bc4a4fb87ae103ebc00ef6de64 6728 
cabextract_1.11-2.debian.tar.xz
 4e23d2a0f4c648ce94c9445d94f0208a3f21c8fb323916bcbcf92545e735a8e7 7818 
cabextract_1.11-2_amd64.buildinfo
Files:
 80ef693cf2cbca2306ad357e04d58ffc 1719 utils optional cabextract_1.11-2.dsc
 451d36d8132db020d00ff6152620ac74 6728 utils optional 
cabextract_1.11-2.debian.tar.xz
 37267223a4be6f18cd42ddb353a3e2c2 7818 utils optional 
cabextract_1.11-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEELpjU0Pi3I6H/MmtbReLNpaf9kPkFAmYIuUEACgkQReLNpaf9
kPkmWg//fdr9LaH4BgSvlS26Qy5/U0EP+wyzygMI3n000QbwtqI7LOnZ5CzfJLTI
2daMCi8Di7nbsh3Jk+TVeUlY3KMDjQNfY++FaCJ29TxU91NDFH9Zb4dqjL78epU5
JOiFAfmwZIdW9AN+HL4/so9vHj+sXxkVYY/9ObfvhKLNbNbb5GuJK/YgetefZG0b
BztOEvKf8jReKsJzTsKmlFlP5fjqJBRGkToZ3Lbfyr2F17VbIGQ6xYyvOPAZHt47
EGvJ5e11W3d8x6jQEfCVvvPOjqIhJ53wZdX5wcxSmhbihf/XAs3hJkwM15YLuILn
1kPeDizZwo8CRIAcVzrqUP8CV/2zzXMwEwNuaJdik4HvHj4e8PeYSOMZuAY3tpD2
474ds47OrrugPEeTJWrgF2neAYhBgiwRADb/bQowpt/eFSh4+DK6MO5F3Jv0LuiY
OGhntHiGZUi77Lj4gs2dye+4GqZtlSzKjERk18pbRldajyUb1LXA+dVSlETOidUG
cV2Cu1ISuu+oXlh7K0rQM+AfAHg4UCMwRHMLunsJgk2ZPe6RDFFGElVt7PJp2Jsd
CGi42/5H9mw0v4YfEfdfZJVDDLdNyhHx1P94DpBiRUNZHqGOjgy+eLoOYdIaxOW4

Bug#1067919: marked as done (Update Build-Depends for the time64 library renames)

[Debian Bug Tracking System]

Your message dated Sun, 31 Mar 2024 10:37:09 +
with message-id 
and subject line Bug#1067919: fixed in calindori 24.02.1-1
has caused the Debian Bug report #1067919,
regarding Update Build-Depends for the time64 library renames
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.)


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

The package explicitly Build-Depends: libqt5*, these need to be changed to
libqt5*t64 (where applicable) if these deps are needed at all.


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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
--- End Message ---
--- Begin Message ---
Source: calindori
Source-Version: 24.02.1-1
Done: Marco Mattiolo 

We believe that the bug you reported is fixed in the latest version of
calindori, 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.
Marco Mattiolo  (supplier of updated calindori 
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: Fri, 29 Mar 2024 10:06:56 +0100
Source: calindori
Architecture: source
Version: 24.02.1-1
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Marco Mattiolo 
Closes: 1067919
Changes:
 calindori (24.02.1-1) unstable; urgency=medium
 .
   * New upstream release
   * Update d/copyright after upstream changes
   * Update d/control for build-deps after time64 transition (Closes: #1067919)
   * Update d/control to make build-deps list transition-proof
Checksums-Sha1:
 7e8db2a9ceca9aadeef83bd2f17e33040734acb3 2711 calindori_24.02.1-1.dsc
 d248e12f3596f897171e2fa223ba10045c09c376 385320 calindori_24.02.1.orig.tar.xz
 a92c5742b236557b5a69748ba2d277726c085fc3 833 calindori_24.02.1.orig.tar.xz.asc
 7821cfc0835991af64e1543c830052df98cb9f63 24060 
calindori_24.02.1-1.debian.tar.xz
 a91640fd2b2a36bdf710726552c7d90ffa1a0f18 14305 
calindori_24.02.1-1_source.buildinfo
Checksums-Sha256:
 47884ed0aef669add7a95d04e2f6a75c9fd9bd5522b15f26120ce27b3191112e 2711 
calindori_24.02.1-1.dsc
 c4e97f344c6befe4b847f1162779ae914a40eea94f7487e7c87da0ecc886ec05 385320 
calindori_24.02.1.orig.tar.xz
 9553dbd487d3ce9667dd61a5502283bfb23c4bd093fffbcb594f1fd3f86d76c3 833 
calindori_24.02.1.orig.tar.xz.asc
 23e4a40d6a8640c1c995b813e08668eae4e468bfe0e0c478e8a9c571ac132307 24060 
calindori_24.02.1-1.debian.tar.xz
 04cd58b784eddf2ef083389242fd61c77be090ca7aab3bdbcee671637843616f 14305 
calindori_24.02.1-1_source.buildinfo
Files:
 652077b347b84b566009cc286e15ef1e 2711 kde optional calindori_24.02.1-1.dsc
 f16bba7d3e0d9aeb46cd7cf61683bd40 385320 kde optional 
calindori_24.02.1.orig.tar.xz
 acc984f9d9f36736c387776469fa2f69 833 kde optional 
calindori_24.02.1.orig.tar.xz.asc
 780c60ac2bf946299132a5c1a4d8513a 24060 kde optional 
calindori_24.02.1-1.debian.tar.xz
 d6531f210355158fb58318275072299c 14305 kde optional 
calindori_24.02.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEeW2zk9w/9AIituoi0+u1lmu5kZYFAmYIPuIACgkQ0+u1lmu5
kZbtahAAp/EwYlxTWGfePSuGxmpd/ucI7eQZk22zIgt0IWpMmz/bVQaH+ZM2o03Y
yEauDp6DVPGcMP61yjUpemOgxNQveMkUhzBiyVy5sXT5IbSZtD0ItzATySKX2XNF
HXVXQVftAURL5Bq4iAiX+KZBhk0LpMCHe9HzJL8mbW4xJkRn3Br04i5QlMuoMbpH
W9ul8lSdyfjPFlCE4XJU1v2XtfgtnTJKdO3hkp3hF7Z3J5+mVMoeJXkfS8eXkphw
zSGKvNUHyJJmYTLHsGjk445en5whU8j0wsu49h8v0yrcn5HnfK6ClZXjIdvlDPGs
1RbWnUx4f6FFv6Ypo5NFob54XUGh17TzQ64OJLsrkdyiC88UZZQIvG5Q0DESQQq5
ICvYCXZ3mUNoUZVkqhKrfKgKPQjQU0Qk7oMuU6bk1vXqO8ax+VKSiWIOx+QcZhDV

Processed: severity of 1068123 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1068123 grave
Bug #1068123 [gnome-session] Breaks phosh << 0.37.0-2
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#1068121: python-fusepy: hard-coded dependencies on pre-t64 libraries

[Sebastian Ramacher]

Source: python-fusepy
Version: 3.0.1-4
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

python-fusepy builds binary packages with hardcoded dependencies on
shared library packages that were renamed as part of the time_t 64
transition. The dependencies need to be updated for this change - or if
possible - changed to be generated by debhelper.

There's a patch available from Ubuntu: 
https://patches.ubuntu.com/p/python-fusepy/python-fusepy_3.0.1-4ubuntu1.patch

Cheers
-- 
Sebastian Ramacher

Bug#1068120: mergerfs: builds binary packages with hardcoded dependencies on pre-t64 libraries

[Sebastian Ramacher]

Source: mergerfs
Version: 2.33.5-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

mergerfs builds binary packages with hardcoded dependencies on shared
library packages that were renamed as part of the time_t 64 transition.
The dependencies need to be updated for this change - or if possible -
changed to be generated by debhelper.

Cheers
-- 
Sebastian Ramacher

Bug#1068119: s390-tools: FTBFS: ../../include/boot/s390.h:418:17: error: array subscript 0 is outside array bounds of ‘void[0]’ [-Werror=array-bounds=]

[Sebastian Ramacher]

Source: s390-tools
Version: 2.16.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=s390-tools=s390x=2.16.0-2%2Bb4=1711742603=0

gcc -I ../../include -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -fno-pie -Os 
-g -I../..//zipl/boot -I../..//zipl/include -I../..//include 
-DENABLE_SCLP_ASCII=1 -DS390_TOOLS_RELEASE=2.16.0-build-20240329 -fno-builtin 
-ffreestanding -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks 
-fno-stack-protector -fexec-charset=IBM1047 -m64 -mpacked-stack 
-mstack-size=4096 -mstack-guard=128 -msoft-float -Wall -Wformat-security 
-Wextra -Werror -c stage3a.c -o stage3a.o
In file included from stage3a.c:14:
In function ‘__test_facility’,
inlined from ‘test_facility’ at ../../include/boot/s390.h:428:9,
inlined from ‘start’ at stage3a.c:42:7:
../../include/boot/s390.h:418:17: error: array subscript 0 is outside array 
bounds of ‘void[0]’ [-Werror=array-bounds=]
  418 | return (*ptr & (0x80 >> (nr & 7))) != 0;
  | ^~~~
In function ‘start’:
cc1: note: source object is likely at address zero
cc1: all warnings being treated as errors
make[4]: *** [../../common.mak:253: stage3a.o] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1066630: Confirming the build problem

[Bill MacAllister]

This is a confirmed bug.  I am working on a solution.

Bill

Processed: Re: Bug#1067934: jameica: Jameica cannot load plugins | service "database" not found

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1067934 [jameica] jameica: Jameica cannot load plugins | service 
"database" not found
Severity set to 'normal' from 'grave'

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

Bug#1067934: jameica: Jameica cannot load plugins | service "database" not found

[Jochen Sprickerhof]

Control: severity -1 normal

Hi Ferdinand,

* Ferdinand Rau  [2024-03-29 08:51]:

  * What led up to the situation?
The plugin Hibiscus, arguably the most important plugin for jameica, was
updated.
Version 2.10.15 used to work fine and still does work fine with the jameica
packages in Debian Bookworm and Trixie. Versions 2.10.16 and the current
version 2.10.17 do not work with either Debian package, but do work fine with
the latest version of jameica (2.10.4) downloaded from the upstream source
willuhn.de: https://www.willuhn.de/products/hibiscus/download.php
Plugin-updates/installs were performed using the integrated plugin management
of jameica.


That is expected, software in stable is only supported with other 
software in stable, i.e. with the Hibiscus plugin in stable.



Staying with hibiscus 2.10.15 is not an option in the long term, because
updates introduce bug fixes and, most importantly, fix access for several
German banks that changed their online access to different servers and
protocols. Without the update to hibiscus 2.10.17, lots of bank accounts are
inaccessible for the users.


This is too unspecific to call for an update in stable. From my 
understanding all updates are configuration changes that can be done 
with the stable version as well. Downgrading the bug accordingly.

Note that Debian stable updates have a strict policy noted here:

https://lists.debian.org/debian-devel-announce/2019/08/msg0.html

* Ferdinand Rau  [2024-03-29 12:41]:

The upstream author suggests that the issue may be related to the "H2 Database 
Engine" (Debian package: jameica-h2database) in a similar, but not identical case 
here:
https://homebanking-hilfe.de/forum/topic.php?p=170111#real170111

Upstream H2 is at version 2.2.224, whereas Debian is at 1.4.197-7, which is 
approx. six years old.

An update of jameica-h2database will likely fix this issue?


Sadly no, while upstream H2 is at 2.2.224 and the Debian package 
(libh2-java) is at 2.2.220, Jameica ships 1.4.199, this is why the 
jameica-h2database was created in the first first place. I will update 
it to 1.4.199 together with Jameica in unstable.


Cheers Jochen


signature.asc
Description: PGP signature