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

[Arto Jantunen]

Package: elpa-magit-forge
Version: 0.3.2+git20231227.1.299bbaa-1
Severity: serious
Justification: Policy 3.5

Upgrading to the new snapshot of magit-forge on testing results in the
following:

install/magit-forge-0.3.2.50snapshot: Handling install of emacsen flavor emacs
install/magit-forge-0.3.2.50snapshot: byte-compiling for emacs
../../elpa-src/treepy-0.1.1/treepy.el: Warning: Case 'node will match ‘quote’.  
If that’s intended, write (node quote) instead.  Otherwise, don’t quote ‘node’.
../../elpa-src/treepy-0.1.1/treepy.el: Warning: Case 'context will match 
‘quote’.  If that’s intended, write (context quote) instead.  Otherwise, don’t 
quote ‘context’.
../../elpa-src/treepy-0.1.1/treepy.el: Warning: Case ':preorder will match 
‘quote’.  If that’s intended, write (:preorder quote) instead.  Otherwise, 
don’t quote ‘:preorder’.
../../elpa-src/treepy-0.1.1/treepy.el: Warning: Case ':postorder will match 
‘quote’.  If that’s intended, write (:postorder quote) instead.  Otherwise, 
don’t quote ‘:postorder’.
../../elpa-src/treepy-0.1.1/treepy.el: Warning: Case ':preorder will match 
‘quote’.  If that’s intended, write (:preorder quote) instead.  Otherwise, 
don’t quote ‘:preorder’.
../../elpa-src/treepy-0.1.1/treepy.el: Warning: Case ':postorder will match 
‘quote’.  If that’s intended, write (:postorder quote) instead.  Otherwise, 
don’t quote ‘:postorder’.
Emergency (magit): Magit requires ‘transient’ >= 0.5.0,
but due to bad defaults, Emacs’ package manager, refuses to
upgrade this and other built-in packages to higher releases
from GNU Elpa.

To fix this, you have to add this to your init file:

  (setq package-install-upgrade-built-in t)

Then evaluate that expression by placing the cursor after it
and typing C-x C-e.

Once you have done that, you have to explicitly upgrade ‘transient’:

  M-x package-upgrade transient RET

Then you also must make sure the updated version is loaded,
by evaluating this form:

  (progn (unload-feature ’transient t) (require ’transient))

If you don’t use the ‘package’ package manager but still get
this warning, then your chosen package manager likely has a
similar defect.

In toplevel form:
forge-bitbucket.el:26:2: Error: Invalid slot name: "#", :inapt-face

In toplevel form:
forge-commands.el:25:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-gitea.el:26:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-github.el:27:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-gitlab.el:27:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-gogs.el:26:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-issue.el:25:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-list.el:28:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-notify.el:25:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-pkg.el:1:2: Warning: ‘define-package’ is an obsolete function (as of 
29.1).

In toplevel form:
forge-post.el:27:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-pullreq.el:25:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-repo.el:25:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-revnote.el:25:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-semi.el:25:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge-topic.el:30:2: Error: forge-topic-mark-read is already defined as 
something else than a generic function

In toplevel form:
forge.el:44:2: Error: forge-topic-mark-read is already defined as something 
else than a generic function

In toplevel form:
magit-forge-pkg.el:1:2: Warning: ‘define-package’ is an obsolete function (as 
of 29.1).
ERROR: install script from elpa-magit-forge package failed
dpkg: error processing package elpa-magit-forge (--configure):
 installed elpa-magit-forge package post-installation script subprocess 
returned error exit status 1
Processing triggers for install-info (7.1-3) ...
Errors were encountered while processing:
 elpa-magit-forge
Config is in use.
E: Sub-process /usr/bin/dpkg returned an error code (1)

Please add a versioned dependency on elpa-transient to prevent this from
getting out of sync in testing, and to keep partial upgrades working.

-- System Information:
Debian Release: t

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

[Steve Langasek]

Package: rakarrack
Followup-For: Bug #1068431
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue which has been uploaded to
Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru rakarrack-0.6.1/debian/control rakarrack-0.6.1/debian/control
--- rakarrack-0.6.1/debian/control  2024-03-12 00:01:51.0 -0700
+++ rakarrack-0.6.1/debian/control  2024-04-12 22:22:56.0 -0700
@@ -21,9 +21,6 @@
 Architecture: any
 Depends: ${misc:Depends},
  ${shlibs:Depends},
- libfltk1.3,
- libxpm4,
- libasound2,
  jackd
 Description: Simple and easy guitar effects processor for GNU/Linux
  Rakarrack is a guitar effects processor for GNU / Linux simple and easy to use

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1068431 [rakarrack] rakarrack dependencies unsatisfiable on 32-bit 
non-i386 architectures.
Added tag(s) patch.

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

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

[Debian Bug Tracking System]

Your message dated Sat, 13 Apr 2024 01:53:33 +
with message-id 
and subject line Bug#1056785: Removed package(s) from unstable
has caused the Debian Bug report #1013395,
regarding mpdecimal: FTBFS with Sphinx 5.0, docutils 0.18: make[1]: *** 
[debian/rules:60: override_dh_sphinxdoc] Error 255
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.)


-- 
1013395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013395
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpdecimal
Version: 2.5.1-2
Severity: important
Tags: ftbfs
User: mity...@debian.org
Usertags: sphinx5.0

Hi,

mpdecimal fails to build with Sphinx 5.0 and docutils 0.18, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -rf debian/tmp/usr/share/doc/mpdecimal/libmpdec++/_static
> ln -sf ../libmpdec/_static 
> debian/tmp/usr/share/doc/mpdecimal/libmpdec++/_static
> rm -f 
> debian/tmp/usr/share/doc/mpdecimal/libmpdec/_static/{doctools,jquery,searchtools,sidebar,underscore}.js
> cp -p 
> /usr/share/javascript/sphinxdoc/1.0/{doctools,jquery,searchtools,sidebar,underscore}.js
>  \
>   debian/tmp/usr/share/doc/mpdecimal/libmpdec/_static/.
> cp -a debian/tmp/usr/share/doc/mpdecimal/* \
>   debian/libmpdec-doc/usr/share/doc/libmpdec-doc
> rm -f debian/libmpdec-doc/usr/share/doc/libmpdec-doc/LICENSE*
> rm -f debian/libmpdec-doc/usr/share/doc/libmpdec-doc/INSTALL*
> dh_sphinxdoc
> unexpected end of string while parsing JSON string, at character offset 2 
> (before "ocnames:["arithmetic...") at /usr/bin/dh_sphinxdoc line 245.
> make[1]: *** [debian/rules:60: override_dh_sphinxdoc] Error 255


The full build log is available from:
http://qa-logs.debian.net/2022/06/23/mpdecimal_2.5.1-2_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.18.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx5.0;users=mity...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=sphinx5.0&fusertaguser=mity...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
--- End Message ---
--- Begin Message ---
Version: 2.5.1-2+rm

Dear submitter,

as the package mpdecimal has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1056785

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1067623 [src:acm] FTBFS: error: format ‘%ld’ expects argument of type 
‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’}
Added tag(s) patch.

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

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

[Steve Langasek]

Package: acm
Followup-For: Bug #1067623
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue which has been uploaded to
Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru acm-6.0+20200416/debian/patches/64-bit-time-t.patch 
acm-6.0+20200416/debian/patches/64-bit-time-t.patch
--- acm-6.0+20200416/debian/patches/64-bit-time-t.patch 1969-12-31 
16:00:00.0 -0800
+++ acm-6.0+20200416/debian/patches/64-bit-time-t.patch 2024-04-12 
17:30:16.0 -0700
@@ -0,0 +1,22 @@
+Description: use 64-bit-safe format string for time_t
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1067623
+Last-Update: 2024-04-12
+Forwarded: no
+
+Index: acm-6.0+20200416/src/dis/test/disscope.c
+===
+--- acm-6.0+20200416.orig/src/dis/test/disscope.c
 acm-6.0+20200416/src/dis/test/disscope.c
+@@ -239,8 +239,9 @@
+   printf ("Family   %d\n", pdu.hdr.protocol_family);
+   printf ("Exercise id  %d\n", pdu.hdr.exercise_id);
+   dis_timestampToTimeval (&pdu.hdr.time_stamp, &tm);
+-  printf ("Time stamp   %ld.%ld\n", tm.tv_sec,
+-  tm.tv_usec / 1000);
++  printf ("Time stamp   %lld.%lld\n",
++  (long long int)tm.tv_sec,
++  (long long int)tm.tv_usec / 1000);
+   switch (pdu.hdr.pdu_type) {
+   case PDUTypeEntityState:
+   printf ("Entity (sim.app.eid) : %d/%d/%d\n",
diff -Nru acm-6.0+20200416/debian/patches/series 
acm-6.0+20200416/debian/patches/series
--- acm-6.0+20200416/debian/patches/series  2022-10-17 08:51:57.0 
-0700
+++ acm-6.0+20200416/debian/patches/series  2024-04-12 17:28:43.0 
-0700
@@ -4,3 +4,4 @@
 fix_paths_in_acm_tcl.patch
 hardening1.patch
 fix_buffer_size.patch
+64-bit-time-t.patch

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

[Debian Bug Tracking System]

Your message dated Sat, 13 Apr 2024 00:36:02 +
with message-id 
and subject line Bug#1066612: fixed in prctl 1.6-2
has caused the Debian Bug report #1066612,
regarding prctl: FTBFS: prctl.c:82:31: error: implicit declaration of function 
‘prctl’ [-Werror=implicit-function-declaration]
to be 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.)


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

Hi,

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

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

Relevant part (hopefully):
> gcc -c -DHAVE_UNISTD_H=1 -DHAVE_STRERROR=1  -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection prctl.c
> prctl.c:53:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>53 | print_version(char *progname)
>   | ^
> prctl.c:58:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>58 | usage(char *progname)
>   | ^
> prctl.c: In function ‘set_unaligned’:
> prctl.c:82:31: error: implicit declaration of function ‘prctl’ 
> [-Werror=implicit-function-declaration]
>82 | if ((retval = prctl(PR_GET_UNALIGN, &alignval)) != 
> -1) {
>   |   ^
> cc1: some warnings being treated as errors
> make[1]: *** [Makefile:71: prctl.o] Error 1


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

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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: prctl
Source-Version: 1.6-2
Done: Khalid Aziz 

We believe that the bug you reported is fixed in the latest version of
prctl, 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.
Khalid Aziz  (supplier of updated prctl 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, 12 Apr 2024 16:57:21 -0600
Source: prctl
Architecture: source
Version: 1.6-2
Distribution: unstable
Urgency: low
Maintainer: Khalid Aziz 
Changed-By: Khalid Aziz 
Closes: 1066612
Changes:
 prctl (1.6-2) unstable; urgency=low
 .
   * Fix build warnings (closes: #1066612)
Checksums-Sha1:
 1005dbbb5627231379cbd4cc2f5f3f6cae7c1248 1648 prctl_1.6-2.dsc
 f39df2d06cd46b115591f83e1f30f3996bc8fe9b 2956 prctl_1.6-2.debian.tar.xz
 63c470fac4740e76d593da7c9675c59af4836d9f 6063 prctl_1.6-2_source.buildinfo
Checksums-Sha256:
 1a37a547b2ffe2713f87d539c046cb605d3daab2ff57ce594042209b8e9c2d25 1648 
prctl_1.6-2.dsc
 bbc99728da3f17178347aae33945ceb6e316d14cc528c90c606ae177181334ec 2956 
prctl_1.6-2.debian.tar.xz
 c742b1e3f10dbe19d73e8d19f2aa1f6eeacd9ca6513576784d53c7f8b164bb9f 6063 
prctl_1.6-2_source.buildinfo
Files:
 a6d87c8f114d70c74da5a8a9d9fc99bd 1648 devel optional prctl_1.6-2.dsc
 6d4f76712ce1f6230944792f6b64cd21 2956 devel optional prctl_1.6-2.debian.tar.xz
 c7201ad07

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066315 [src:kraptor] kraptor: FTBFS: src/main.c:57:5: error: implicit 
declaration of function ‘mkdir’ [-Werror=implicit-function-declaration]
Added tag(s) patch.

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

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

[Steve Langasek]

Package: kraptor
Followup-For: Bug #1066315
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue which has been uploaded to
Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru kraptor-0.0.20040403+ds/debian/patches/no-implicit-declarations.patch 
kraptor-0.0.20040403+ds/debian/patches/no-implicit-declarations.patch
--- kraptor-0.0.20040403+ds/debian/patches/no-implicit-declarations.patch   
1969-12-31 16:00:00.0 -0800
+++ kraptor-0.0.20040403+ds/debian/patches/no-implicit-declarations.patch   
2024-04-12 16:42:20.0 -0700
@@ -0,0 +1,18 @@
+Description: add missing include
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066315
+Last-Update: 2024-04-12
+Forwarded: no
+
+Index: kraptor-0.0.20040403+ds/src/main.c
+===
+--- kraptor-0.0.20040403+ds.orig/src/main.c
 kraptor-0.0.20040403+ds/src/main.c
+@@ -19,6 +19,7 @@
+ // 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include  /* DUMB: musica MOD, XM, etc */
diff -Nru kraptor-0.0.20040403+ds/debian/patches/series 
kraptor-0.0.20040403+ds/debian/patches/series
--- kraptor-0.0.20040403+ds/debian/patches/series   2024-01-04 
16:48:45.0 -0800
+++ kraptor-0.0.20040403+ds/debian/patches/series   2024-04-12 
16:40:54.0 -0700
@@ -14,3 +14,4 @@
 14_create-hidden-kraptor-directory-in-home.patch
 15_reproducible-build.patch
 fix_building_kraptor_with_fix_functions.patch
+no-implicit-declarations.patch

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

[Debian Bug Tracking System]

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

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


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

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I./.. -W 
> -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wall -g -Wl,-z,relro -Wl,-z,now 
> -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -MT buffer.o -MD -MP -MF .deps/buffer.Tpo 
> -c -o buffer.o buffer.c
> In file included from buffer.c:25:
> ../uucp.h:103:3: error: #error ANSI C compiler without void or unsigned char 
> or prototypes
>   103 |  #error ANSI C compiler without void or unsigned char or prototypes
>   |   ^
> make[4]: *** [Makefile:355: buffer.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/uucp_1.07-28_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&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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: uucp
Source-Version: 1.07-29
Done: Thorsten Alteholz 

We believe that the bug you reported is fixed in the latest version of
uucp, 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.
Thorsten Alteholz  (supplier of updated uucp 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, 12 Apr 2024 22:00:00 +0200
Source: uucp
Architecture: source
Version: 1.07-29
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Closes: 1066434
Changes:
 uucp (1.07-29) unstable; urgency=medium
 .
   * take care of implicit function declaration (Closes: #1066434)
 (this even affects the configure script)
Checksums-Sha1:
 3b2917e887c1a676147979ed5627a957a80a524e 2002 uucp_1.07-29.dsc
 e7c93c3aa6468f1b26dd4d9104dbbe8c2949e9ee 1013234 uucp_1.07.orig.tar.gz
 4611213b3e084d34562aa333aff0afa5818d7717 112912 uucp_1.07-29.debian.tar.xz
 0631837854b651f3e0e8c9200ebbb96fd8bb8a77 7347 uucp_1.07-29_amd64.buildinfo
Checksums-Sha256:
 8083c533c8533289bc0e22c1afe9ad1fc4b6ad0f7e0911c3efc3b7d933de743c 2002 
uucp_1.07-29.dsc
 060c15bfba6cfd1171ad81f782789032113e199a5aded8f8e0c1c5bd1385b62c 1013234 
uucp_1.07.orig.tar.gz
 7a9a36c413d5cd76aedd420ef0281774a8cb0eb87bc3ef6a92aafbe283eeb8cf 112912 
uucp_1.07-29.debian.tar.xz
 3c105753881c6f1bdf8cea1d9ab9b668fb4ad810d96f0c2665a8305c9b8e904d 7347 
uucp_1.07-29_amd64.buildinfo
Files:
 8819d9d5d4c2aa84d4db09d5a3cdb9c2 2002 comm optional uucp_1.07-29.dsc
 64c54d43787339a7cced48390eb3e1d0 1013234 comm optional uucp_1.07.orig.tar.gz
 833f95c317a8e2c0c46eaba200fe9e31 112912 comm optional 
uucp_1.07-29.debian.tar.xz
 936aff7e16aff65e233d047694ec9dfa 7347 c

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

[Peter Pentchev]

On Fri, Apr 12, 2024 at 02:56:02PM -0600, Zixing Liu wrote:
> Package: ucspi-tcp
> Followup-For: Bug #1066629
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu noble ubuntu-patch
> Control: tags -1 patch
> 
> Dear Maintainer,
> 
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * debian/patches/0006-implicit-declarations.patch: Add missing
> includes and prototypes.  Closes LP: #2061188.
>   * debian/ipv6-support.patch: Refresh deferred patch.

OK, this is a little creepy :) I am staring at my work-in-progress update of
the ucspi-tcp package and I see a patch named 0006-implicit-declarations.patch 
and
an update to the ipv6-support one :) But mine was not completely done yet,
while yours seems to be.

(and yes, of course, the patch naming is logical)

> Thanks for considering the patch.

Thanks! I will probably upload a new ucspi-tcp version in a couple of days.

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has 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.)


-- 
1068586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068586
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ghc
Version: 9.4.7-3
Severity: grave
Justification: renders package unusable

I recently uploaded a new version of GHC to unstable, in order to fix
#1068179. As a result, GHC got rebuilt taking into account the new size
for time_t on arm{el,hf}. This is evident from the build logs, where
we now see:

  
https://buildd.debian.org/status/fetch.php?pkg=ghc&arch=armel&ver=9.4.7-4&stamp=1712410679&raw=0

  checking Haskell type for time_t... Int64

whereas previously we had:

  
https://buildd.debian.org/status/fetch.php?pkg=ghc&arch=armel&ver=9.4.7-3&stamp=1708366014&raw=0

  checking Haskell type for time_t... Int32


After this change, a number of Haskell packages have started to FTBFS:

* 
https://buildd.debian.org/status/fetch.php?pkg=haskell-filestore&arch=armel&ver=0.6.5-3%2Bb2&stamp=1712457355&raw=0
* 
https://buildd.debian.org/status/fetch.php?pkg=haskell-fold-debounce&arch=armel&ver=0.2.0.11-1%2Bb2&stamp=1712466208&raw=0
* 
https://buildd.debian.org/status/fetch.php?pkg=haskell-hourglass&arch=armel&ver=0.2.12-5%2Bb2&stamp=1712462130&raw=0

Looking into this, I see that (at least) the getPOSIXTime method is
broken on arm{el,hf}. Compiling the following program on armel:

  $ cat Time.hs
  import Data.Time.Clock.POSIX

  main = do
t <- getPOSIXTime
print t

  $ ghc -o time Time.hs
  $ ./time
  3590884976642664859s

whereas on an amd64 system it returns:

  $ ./time
  1712499127.06215219s

This bug blocks the time_t transition (#1036884).

-- 
Ilias
--- End Message ---
--- Begin Message ---
Source: ghc
Source-Version: 9.4.7-5
Done: Ilias Tsitsimpis 

We believe that the bug you reported is fixed in the latest version of
ghc, 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.
Ilias Tsitsimpis  (supplier of updated ghc 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: Wed, 10 Apr 2024 14:24:01 +0300
Source: ghc
Architecture: source
Version: 9.4.7-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Closes: 1060196 1068586
Changes:
 ghc (9.4.7-5) unstable; urgency=medium
 .
   * Backport upstream patches to fix issues with 64-bit time_t (Closes:
 #1068586)
   * Build unregisterised on powerpc (Closes: #1060196)
Checksums-Sha1:
 b80c51e36619aad30f7514d97b9c29456457dd6f 2715 ghc_9.4.7-5.dsc
 ef69ede497d5085b98c1e4ec979d4bfda9d12acb 67972 ghc_9.4.7-5.debian.tar.xz
 4b9c76fdd1b4dd066ceb3e0c4d39f29076815fec 12818 ghc_9.4.7-5_source.buildinfo
Checksums-Sha256:
 d2c9d6c69d75d9050aa40035d6e4508a4b74982fc7e822cfdd8caa430368d39c 2715 
ghc_9.4.7-5.dsc
 708878390e8ea7edb0cede08d05decad4feefed64f4f83d7cb43e9232ef5053c 67972 
ghc_9.4.7-5.debian.tar.xz
 f5a6768e14c472445735122a030197bfe33655b459cb637aa0efedb48f42a536 12818 
ghc_9.4.7-5_source.buildinfo
Files:
 196da9fc666e5783c03183fb839dc250 2715 haskell optional ghc_9.4.7-5.dsc
 9c6e6c98609e6020590a70ff2e3f2305 67972 haskell optional 
ghc_9.4.7-5.debian.tar.xz
 01ef2c7532a7bbdd3694f7e9eca3aa5c 12818 haskell optional 
ghc_9.4.7-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmYZsuAUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDwzARAAmgr//9D5fpeImCMatt8cFAYwW9Mi
c5NoTnDAyqV5y892GX5CR7TuPt8khYKoPgrKG8DigWczPAB1Sti0D6kI8swx2WZL
Db58n7/kwikDr0AUMhSnIzFbbxoHh5Rcpu5R0WCXO5KF19pVT/G8G9N8iiW6Es9s
weoyz73XiOn6RZ32tAy/j2ALgOYsNI4OzkSzI5VLYSF9Gkbl7lKwGOM9o3S9hd7R
1isdbFeNgybjKIzC2NUKGyrxIjzKNYh/I/KY16uK1NxaGXhHHauhTV3sgHhL5seN
jbSnxzgDj6ydh0ukANG9cucRgk8xXoE6sFDrrk2xpsZ2pQKBweJmdbQSvI0jMPJq
9GaAyATlMIZLZiTkOYzZNhkphKdFhG/C2ZE2AUXdKx8SNFDYT1XKsUZCxjz9+YiR
WoxF5OcQsCmNkS1sGay8vr2J24C1wG2oLA+SnEQeYle4+SKYJbKQCQciGcH+DYg6

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

[Zixing Liu]

Package: scrollz
Followup-For: Bug #1066483
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

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

  * debian/patches/gcc13.patch: Fix build with GCC 13 and add missing
includes.  Closes LP: #2061184.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-26-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru scrollz-2.2.3/debian/patches/gcc13.patch 
scrollz-2.2.3/debian/patches/gcc13.patch
--- scrollz-2.2.3/debian/patches/gcc13.patch1969-12-31 17:00:00.0 
-0700
+++ scrollz-2.2.3/debian/patches/gcc13.patch2024-04-12 16:18:41.0 
-0600
@@ -0,0 +1,131 @@
+Description: Fix build with GCC 13 and add missing includes
+ Also included missing function prototypes
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066483
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/scrollz/+bug/2061184
+Forwarded: no
+Last-Update: 2024-04-12
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: scrollz/configure
+===
+--- scrollz.orig/configure
 scrollz/configure
+@@ -2317,6 +2317,7 @@ else
+ /* System header to define __stub macros and hopefully few prototypes,
+ which can conflict with char snprintf(); below.  */
+ #include 
++#include 
+ /* Override any gcc2 internal prototype to avoid an error.  */
+ /* We use char because int might match the return type of a gcc2
+ builtin and then its argument prototype would still apply.  */
+@@ -2368,6 +2369,7 @@ else
+ /* System header to define __stub macros and hopefully few prototypes,
+ which can conflict with char vsnprintf(); below.  */
+ #include 
++#include 
+ /* Override any gcc2 internal prototype to avoid an error.  */
+ /* We use char because int might match the return type of a gcc2
+ builtin and then its argument prototype would still apply.  */
+@@ -2536,6 +2538,7 @@ else
+ #line 2537 "configure"
+ #include "confdefs.h"
+ #include 
++#include 
+ #define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
+ #define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c))
+ #define XOR(e, f) (((e) && !(f)) || (!(e) && (f)))
+@@ -5472,6 +5475,7 @@ else
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ main()
+ {
+Index: scrollz/include/edit.h
+===
+--- scrollz.orig/include/edit.h
 scrollz/include/edit.h
+@@ -72,7 +72,7 @@ extern   u_char  *recv_nick;
+   voidcommand_completion _((u_int, char *));
+   voide_quit _((char *, char *, char *));
+   int check_wait_command _((char *));
+-  
++  int  GrabURL _((char *, char *, char *, char *));
+ #define AWAY_ONE 0
+ #define AWAY_ALL 1
+ 
+Index: scrollz/include/trace.h
+===
+--- scrollz.orig/include/trace.h
 scrollz/include/trace.h
+@@ -29,4 +29,6 @@ void TraceChannelInfo _((int indent, Cha
+ void TraceNickListInfo _((int indent, NickList *nicks));
+ void TraceWindowInfo _((int indent, Window *window));
+ 
++void Trace(long area, char *format, ...);
++
+ #endif
+Index: scrollz/source/edit.c
+===
+--- scrollz.orig/source/edit.c
 scrollz/source/edit.c
+@@ -101,6 +101,7 @@ static voidsend_action _((char *, char
+ 
+ TimerList *PendingTimers = (TimerList *) 0;
+ 
++extern void PopLine(void);
+ /* used with input_move_cursor */
+ #define RIGHT 1
+ #define LEFT 0
+Index: scrollz/source/edit2.c
+===
+--- scrollz.orig/source/edit2.c
 scrollz/source/edit2.c
+@@ -195,6 +195,8 @@ static char *celeawaystr=(char *) 0;
+ static time_t CeleAwayTime=0;
+ #endif
+ extern char *CelerityNtfy;
++extern int  DecryptMessage _((char *, char *));
++extern int  EncryptMessage _((char *, char *));
+ 
+ /* Kicks all unopped people from current channel */
+ void LameKick(command,args,subargs)
+Index: scrollz/source/edit3.c
+===
+--- scrollz.orig/source/edit3.c
 scrollz/source/edit3.c
+@@ -96,6 +96,7 @@ extern NickList * find_in_hash _((Channe
+ 
+ extern void dcc_chat _((char *));
+ extern void dcc_close _((char *));
++extern int  DecryptString _((char *, char *, char *, int, int));
+ 
+ extern char *ScrollZver

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066483 [src:scrollz] scrollz: FTBFS: configure: error: Fatal: You must 
get working getaddrinfo() function.
Added tag(s) patch.

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

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

[Debian Bug Tracking System]

Your message dated Fri, 12 Apr 2024 22:19:20 +
with message-id 
and subject line Bug#1068880: fixed in fwbuilder 5.3.7-8
has caused the Debian Bug report #1068880,
regarding fwbuilder FTBFS: error: debhelper compat level specified both in 
debian/compat and in debian/control
to be marked as 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.)


-- 
1068880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fwbuilder
Version: 5.3.7-7
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Jeremy Bícha 

https://buildd.debian.org/status/logs.php?pkg=fwbuilder&ver=5.3.7-7

...
 fakeroot debian/rules clean
dh clean
dh: warning: Please specify the debhelper compat level exactly once.
dh: warning:  * debian/compat requests compat 9.
dh: warning:  * debian/control requests compat 12 via "debhelper-compat (= 12)"
dh: warning: 
dh: warning: Hint: If you just added a build-dependency on debhelper-compat, 
then please remember to remove debian/compat
dh: warning: 
dh: error: debhelper compat level specified both in debian/compat and in 
debian/control
make: *** [debian/rules:13: clean] Error 255
--- End Message ---
--- Begin Message ---
Source: fwbuilder
Source-Version: 5.3.7-8
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
fwbuilder, 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.
Jeremy Bícha  (supplier of updated fwbuilder 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, 12 Apr 2024 17:37:28 -0400
Source: fwbuilder
Built-For-Profiles: noudeb
Architecture: source
Version: 5.3.7-8
Distribution: unstable
Urgency: medium
Maintainer: Sylvestre Ledru 
Changed-By: Jeremy Bícha 
Closes: 1068880
Changes:
 fwbuilder (5.3.7-8) unstable; urgency=medium
 .
   * Team upload
   * Revert bumping debhelper-compat to 9 (Closes: #1068880)
Checksums-Sha1:
 2af1f9a21e919a1d392c559a8c690b8f97d639e3 2068 fwbuilder_5.3.7-8.dsc
 8d87e6531c8641d1b633785ffddbc5b6e5a00b63 37412 fwbuilder_5.3.7-8.debian.tar.xz
 e1260f0322cc9e98adafed593f42cdec90cf1e0b 6133 
fwbuilder_5.3.7-8_source.buildinfo
Checksums-Sha256:
 eaed1b4b6bdb787579fab1bcf08cdd812a04a8d6f8d791a4146ba8454950de68 2068 
fwbuilder_5.3.7-8.dsc
 c05c2f331c65ec78f399350b42055f490572df943f4a435986557b3a16d88c39 37412 
fwbuilder_5.3.7-8.debian.tar.xz
 06788102500177d00e0dcdf736dcbd0ee72975395f7abe816b860aee43e244f3 6133 
fwbuilder_5.3.7-8_source.buildinfo
Files:
 a31f13ace09183551704723c43a36790 2068 net optional fwbuilder_5.3.7-8.dsc
 854be1092b1a4050a00824ceffe5c8dc 37412 net optional 
fwbuilder_5.3.7-8.debian.tar.xz
 721ff03cc49690acfb2b779166621e74 6133 net optional 
fwbuilder_5.3.7-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmYZsFoACgkQ5mx3Wuv+
bH0Z6hAAw3bk2n0Nf4NcFVIPxmYz6TIONMCaFkO2vPzxpgNmsBSHnl/O9sWd7g0r
4SZ/wtgkFTw75/UY2dWO3/nHcQ2q1Nr8gaNj9kcF5f2LtZhVQstvybn6jGMRKxjA
gYR9juh5E54qw6jkHmKzftIbtDfaZZqRCy3pGedq79aXItqa8y9Act5dL8eR3k2k
NEwST08MpxRcDLoCyzau7eAzsf14RlshuTHPnfGAXtZgq9BeeYdAedeCLqDVCqPl
Y2HWH6/L0lhP/wqp2n6nzk0W9ycxWX7bZWqHUm2aOBCG4Vd+gj23CVNmVHEVqGi+
55+4oeG9t2JDZTVlzUo3JFhS5i+67zUQte07zo6xW9L2snFUMDZAdc77mZTHl34Y
UMm2c07dgve4ywLnFzPJR7LeeRKYrpHirjzJNLDAhUmGIy24OqQn+++7YbAu55Zn
d7HITp5a2KO9qQmAx7Okva7pbcu9SvCzoMSyOsKqmyhcYldgy0krFHK9f7jq4ttc
HO9KPyqtIHM9WiCdiAQu6Gt/EYjD6GOTfc/0TtrHWT3ePfXW2Huen9Lf0TdueOqX
6WqITZE0mHAjiN8rUIU4uoTFU7gWnVCgMsQ6caYUBJnxSnU3U4KFgFl3tjFEOM4R
s4cJ7o1IJWxCB0nlJFk0cXdlAVF1w2W7/yfc9+/vKnBtArmXycQ=
=YYKV
-END PGP SIGNATURE-



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

Bug#1064061: CVE-2023-52160

[Bastien Roucariès]

control: tags -1 + patch

Hi,

You will find a merge request for fixing CVE-2023-52160

https://salsa.debian.org/debian/wpa/-/merge_requests/15

I can do a NMU if neeeded

Bastien


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

Processed: CVE-2023-52160

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1064061 [src:wpa] wpa: CVE-2023-52160
Added tag(s) patch.

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

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066529 [src:samhain] samhain: FTBFS: x_sh_prelude.c:840:42: error: 
implicit declaration of function ‘isblank’ 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

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

[Zixing Liu]

Package: samhain
Followup-For: Bug #1066529
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

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

  * debian/patches/gcc13.patch: Add missing includes and use va_copy
compiler builtin.  Closes LP: #2061192.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-26-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru samhain-4.1.4/debian/patches/gcc13.patch 
samhain-4.1.4/debian/patches/gcc13.patch
--- samhain-4.1.4/debian/patches/gcc13.patch1969-12-31 17:00:00.0 
-0700
+++ samhain-4.1.4/debian/patches/gcc13.patch2024-04-12 15:20:21.0 
-0600
@@ -0,0 +1,33 @@
+Description: Add missing includes and use va_copy compiler builtin
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066529
+Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/samhain/+bug/2061192
+Forwarded: no
+Last-Update: 2024-04-12
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: samhain/src/sh_error.c
+===
+--- samhain.orig/src/sh_error.c
 samhain/src/sh_error.c
+@@ -1584,7 +1584,7 @@ int sh_error_ehead (/*@null@*/const char
+ #if defined(__GNUC__) && defined(__PPC__) && (defined(_CALL_SYSV) || 
defined(_WIN32))
+ #define VA_COPY(ap1, ap2) (*(ap1) = *(ap2))
+ #elif defined(VA_COPY_AS_ARRAY)
+-#define VA_COPY(ap1, ap2) memmove ((ap1), (ap2), sizeof (va_list))
++#define VA_COPY(ap1, ap2) va_copy((ap1), (ap2))
+ #else /* va_list is a pointer */
+ #define VA_COPY(ap1, ap2) ((ap1) = (ap2))
+ #endif
+Index: samhain/src/sh_prelude.c
+===
+--- samhain.orig/src/sh_prelude.c
 samhain/src/sh_prelude.c
+@@ -35,6 +35,7 @@
+ 
+ #include "config_xor.h"
+ 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru samhain-4.1.4/debian/patches/series 
samhain-4.1.4/debian/patches/series
--- samhain-4.1.4/debian/patches/series 2023-08-15 14:46:14.0 -0600
+++ samhain-4.1.4/debian/patches/series 2024-04-12 15:17:16.0 -0600
@@ -1,2 +1,3 @@
 debian.patch
 configure.patch
+gcc13.patch

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

[Bastian Germann]

Source: ucommon
Version: 7.0.1-0.3
X-Debbugs-Cc: vor...@debian.org
Severity: serious

Hi Steve,

with your last ucommon NMU you have fixed the armel/armhf builds but you have 
introduced a symbol-based FTBFS on i386:
https://buildd.debian.org/status/fetch.php?pkg=ucommon&arch=i386&ver=7.0.1-0.3&stamp=1710782303&raw=0

Also, you have hijacked the package, which has also happened on coin3 and libvformat. It is obvious that this was not 
done intentionally. But please make sure that this does not happen so often. Maybe introduce a check on dput that checks 
the Maintainer field and if it is an upload to Debian and has the XSBC-Original-Maintainer field set, prevent the upload.


I have fixed the Maintainer field in git already. It would be nice if you could 
fix the i386 FTBFS.

Cheers,
Bastian

Processed: tagging 1061519

[Debian Bug Tracking System]

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

> tags 1061519 + fixed-upstream
Bug #1061519 [src:shim] shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 
CVE-2023-40549 CVE-2023-40550 CVE-2023-40551
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

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

[Zixing Liu]

Package: ucspi-tcp
Followup-For: Bug #1066629
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

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

  * debian/patches/0006-implicit-declarations.patch: Add missing
includes and prototypes.  Closes LP: #2061188.
  * debian/ipv6-support.patch: Refresh deferred patch.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-26-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ucspi-tcp-0.88/debian/ipv6-support.patch 
ucspi-tcp-0.88/debian/ipv6-support.patch
--- ucspi-tcp-0.88/debian/ipv6-support.patch2024-02-27 02:57:42.0 
-0700
+++ ucspi-tcp-0.88/debian/ipv6-support.patch2024-04-12 14:19:46.0 
-0600
@@ -741,7 +741,7 @@
 index 0948b1a..f06c5a8 100644
 --- a/dns.h
 +++ b/dns.h
-@@ -34,51 +34,60 @@ struct dns_transmit {
+@@ -34,51 +34,61 @@ struct dns_transmit {
unsigned int curserver;
struct taia deadline;
unsigned int pos;
@@ -812,6 +812,7 @@
 -extern int dns_mx_packet(stralloc *,char *,unsigned int);
 -extern int dns_mx(stralloc *,stralloc *);
 +extern int dns_name4(stralloc *,const char *);
++extern int dns_name6(stralloc *,char *);
 +extern int dns_txt_packet(stralloc *,const char *,unsigned int);
 +extern int dns_txt(stralloc *,const stralloc *);
 +extern int dns_mx_packet(stralloc *,const char *,unsigned int);
@@ -1330,11 +1331,6 @@
 index b9892b4..2158ed4 100644
 --- a/dns_random.c
 +++ b/dns_random.c
-@@ -1,3 +1,4 @@
-+#include 
- #include "dns.h"
- #include "taia.h"
- #include "uint32.h"
 @@ -29,7 +30,7 @@ static void surf(void)
}
  }
@@ -1433,8 +1429,8 @@
 index 6f215ac..b0c8e6d 100644
 --- a/dns_rcrw.c
 +++ b/dns_rcrw.c
-@@ -1,16 +1,17 @@
-+#include 
+@@ -1,16 +1,16 @@
+ #include 
  #include "taia.h"
 -#include "env.h"
  #include "byte.h"
@@ -1511,17 +1507,7 @@
 index df12826..9511511 100644
 --- a/dns_transmit.c
 +++ b/dns_transmit.c
-@@ -1,12 +1,15 @@
-+#include 
-+#include 
-+#include 
-+#include 
- #include "socket.h"
--#include "alloc.h"
--#include "error.h"
-+#include 
- #include "byte.h"
--#include "readwrite.h"
+@@ -7,7 +7,8 @@
  #include "uint16.h"
  #include "dns.h"
 +#include "ip6.h"
@@ -1985,7 +1971,7 @@
 +#include "byte.h"
 +
 +extern unsigned int scan_ip6(const char *src,char *ip);
-+extern unsigned int fmt_ip6(char *dest,const char *ip);
++extern unsigned int ip6_fmt(char *dest,char *ip);
 +
 +extern unsigned int scan_ip6_flat(const char *src,char *);
 +extern unsigned int fmt_ip6_flat(char *dest,const char *);
@@ -2357,7 +2343,8 @@
 index 000..cf3b7c1
 --- /dev/null
 +++ b/remoteinfo6.c
-@@ -0,0 +1,98 @@
+@@ -0,0 +1,99 @@
++#include 
 +#include "fmt.h"
 +#include "buffer.h"
 +#include "socket.h"
@@ -3065,7 +3052,8 @@
 index 000..74099e2
 --- /dev/null
 +++ b/socket_tcp6.c
-@@ -0,0 +1,44 @@
+@@ -0,0 +1,45 @@
++#include 
 +#include 
 +#include 
 +#include 
diff -Nru ucspi-tcp-0.88/debian/patches/0006-implicit-declarations.patch 
ucspi-tcp-0.88/debian/patches/0006-implicit-declarations.patch
--- ucspi-tcp-0.88/debian/patches/0006-implicit-declarations.patch  
1969-12-31 17:00:00.0 -0700
+++ ucspi-tcp-0.88/debian/patches/0006-implicit-declarations.patch  
2024-04-12 14:33:32.0 -0600
@@ -0,0 +1,356 @@
+Description: Add missing includes and prototypes
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066629
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ucspi-tcp/+bug/2061188
+Forwarded: no
+Last-Update: 2024-04-12
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: ucspi-tcp/dns_random.c
+===
+--- ucspi-tcp.orig/dns_random.c
 ucspi-tcp/dns_random.c
+@@ -1,3 +1,4 @@
++#include 
+ #include "dns.h"
+ #include "taia.h"
+ #include "uint32.h"
+Index: ucspi-tcp/dns_rcrw.c
+===
+--- ucspi-tcp.orig/dns_rcrw.c
 ucspi-tcp/dns_rcrw.c
+@@ -1,3 +1,4 @@
++#include 
+ #include "taia.h"
+ #include "env.h"
+ #include "byte.h"
+Index: ucspi-tcp/remoteinfo.c
+===
+--- ucspi-tcp.orig/remoteinfo.c
 ucspi-tcp/remoteinfo.c
+@@ -1,3 +1,4 @@
++#include 
+ #include "fmt.h"
+ #include "buffer.h"
+ #include "socket.h"
+Index: ucspi-tcp/tcpserver.c
+===
+--- ucspi-tcp.orig/tcpserver.c
 ucsp

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1066629 [src:ucspi-tcp] ucspi-tcp: FTBFS: tcpserver.c:143:29: error: 
implicit declaration of function ‘getpid’ 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

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

[Debian Bug Tracking System]

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


-- 
1064560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ucommon
Version: 7.0.1-0.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=ucommon&arch=armhf&ver=7.0.1-0.1%2Bb1&stamp=1707541460&raw=0

dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libucommon8/DEBIAN/symbols doesn't match 
completely debian/libucommon8.symbols
--- debian/libucommon8.symbols (libucommon8_7.0.1-0.1+b1_armhf)
+++ dpkg-gensymbolsGM5eIp   2024-02-10 05:04:15.347217924 +
@@ -287,8 +287,8 @@
  (c++|arch-bits=32)"ost::MappedFile::pageAligned(unsigned int)@Base" 7.0.0
  (c++|arch-bits=64)"ost::MappedFile::pageAligned(unsigned long)@Base" 7.0.0
  (c++)"ost::MemPager::alloc(char const*)@Base" 7.0.0
- (c++|optional)"ost::MemPager::~MemPager()@Base" 7.0.0
- (c++|optional)"ost::Mutex::Mutex()@Base" 7.0.0
+#MISSING: 7.0.1-0.1+b1# (c++|optional)"ost::MemPager::~MemPager()@Base" 7.0.0
+#MISSING: 7.0.1-0.1+b1# (c++|optional)"ost::Mutex::Mutex()@Base" 7.0.0
  (c++)"ost::Mutex::~Mutex()@Base" 7.0.0
  (c++)"ost::MutexCounter::MutexCounter()@Base" 7.0.0
  (c++)"ost::MutexCounter::MutexCounter(int)@Base" 7.0.0
@@ -358,7 +358,7 @@
  (c++)"ost::RefPointer::operator bool() const@Base" 7.0.0
  (c++)"ost::RefPointer::operator!() const@Base" 7.0.0
  (c++)"ost::RefPointer::~RefPointer()@Base" 7.0.0
- (c++)"ost::Semaphore::~Semaphore()@Base" 7.0.0
+#MISSING: 7.0.1-0.1+b1# (c++)"ost::Semaphore::~Semaphore()@Base" 7.0.0
  (c++)"ost::Serial::Serial(char const*)@Base" 7.0.0
  (c++)"ost::Serial::aRead(char*, int)@Base" 7.0.0
  (c++)"ost::Serial::aWrite(char const*, int)@Base" 7.0.0
@@ -708,22 +708,22 @@
  (c++)"ost::ttystream::ttystream()@Base" 7.0.0
  (c++)"ost::ttystream::ttystream(char const*)@Base" 7.0.0
  (c++)"ost::ttystream::~ttystream()@Base" 7.0.0
- (c++|optional=templinst)"std::_Rb_tree, 
std::_Select1st >, 
std::less, 
std::allocator > 
>::_M_erase(std::_Rb_tree_node 
>*)@Base" 7.0.0
- (c++|optional=templinst)"std::_Rb_tree, 
std::_Select1st >, 
std::less, 
std::allocator > 
>::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator >, ost::PersistObject const* const&)@Base" 7.0.0
- (c++|optional=templinst)"std::_Rb_tree, 
std::_Select1st >, 
std::less, 
std::allocator > 
>::_M_get_insert_unique_pos(ost::PersistObject const* const&)@Base" 7.0.0
- (c++|optional=templinst)"std::_Rb_tree, std::allocator >, 
std::pair, 
std::allocator > const, int>, 
std::_Select1st, std::allocator > const, int> >, 
std::less, 
std::allocator > >, 
std::allocator, std::allocator > const, int> > 
>::_M_erase(std::_Rb_tree_node, std::allocator > const, int> >*)@Base" 7.0.0
- (c++|optional=templinst)"std::_Rb_tree, std::allocator >, 
std::pair, 
std::allocator > const, int>, 
std::_Select1st, std::allocator > const, int> >, 
std::less, 
std::allocator > >, 
std::allocator, std::allocator > const, int> > 
>::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator, std::allocator > const, int> >, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 7.0.0
+#MISSING: 7.0.1-0.1+b1# 
(c++|optional=templinst)"std::_Rb_tree, 
std::_Select1st >, 
std::less, 
std::allocator > 
>::_M_erase(std::_Rb_tree_node 
>*)@Base" 7.0.0
+#MISSING: 7.0.1-0.1+b1# 
(c++|optional=templinst)"std::_Rb_tree, 
std::_Select1st >, 
std::less, 
std::allocator > 
>::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator >, ost::PersistObject const* const&)@Base" 7.0.0
+#MISSING: 7.0.1-0.1+b1# 
(c++|optional=templinst)"std::_Rb_tree, 
std::_Select1st >, 
std::less, 
std::allocator > 
>::_M_get_insert_unique_pos(ost::PersistObject const* const&)@Base" 7.0.0
+#MISSING: 7.0.1-0.1+b1# 
(c++|optional=templinst)"std::_Rb_tree, std::allocator >, 
std::pair, 
std::allocator > const, int>, 
std::_Select1st, std::allocator > const, int> >, 
std::less, 
std::allocator > >, 

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

[Debian Bug Tracking System]

Your message dated Fri, 12 Apr 2024 20:42:02 +
with message-id 
and subject line Bug#1058396: fixed in pdudaemon 0.0.8.109.gaa25f15-1
has caused the Debian Bug report #1058396,
regarding pdudaemon: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.12 3.11" returned exit code 13
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.)


-- 
1058396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pdudaemon
Version: 0.0.8.81.gaa63a79-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12/build/pdudaemon
> copying pdudaemon/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon
> copying pdudaemon/__about__.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon
> copying pdudaemon/pdurunner.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon
> copying pdudaemon/httplistener.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon
> copying pdudaemon/tcplistener.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon
> copying pdudaemon/listener.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon
> creating /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/ykush.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/__init__.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/netio4.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/synaccess.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/devantech.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/apc9218.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/esphome.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/hiddevice.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/test_numatousb.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/localcmdline.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/apc7932.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/apc7921.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/energenieusb.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/sainsmart.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/acmebase.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/tasmota.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/apc7900.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/strategies.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/apc7952.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/localbase.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/egpms.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/intellinet.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/ubiquity.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/bcu.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/acme.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/cleware.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/apcbase.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/drivers
> copying pdudaemon/drivers/servo.py -> 
> /<>/.pybuild/cpython3_3.12/build/pdudaemon/driv

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

[Debian Bug Tracking System]

Your message dated Fri, 12 Apr 2024 19:22:18 +
with message-id 
and subject line Bug#1068812: fixed in pcb-rnd 3.1.4-2
has caused the Debian Bug report #1068812,
regarding pcb-rnd: hardcoded librnd4 dependency
to be marked as done.

This means that you claim that the problem has been dealt with.
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.)


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

Package: pcb-rnd
Version: 3.1.4-1
Severity: serious
Tags: patch


Hello, I found that librnd4 is correctly evaluated from shlibs:Depends in the 
core library and then it can be dropped also on core reverse-dependencies.


Please drop it.


Thanks for considering the patch.

diff -Nru pcb-rnd-3.1.4/debian/control pcb-rnd-3.1.4/debian/control
--- pcb-rnd-3.1.4/debian/control2024-03-14 00:19:26.0 +0100
+++ pcb-rnd-3.1.4/debian/control2024-04-11 15:53:47.0 +0200
@@ -162,7 +162,7 @@
 
 Package: pcb-rnd-export

 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, pcb-rnd-core (= 
${binary:Version}), librnd4, librnd4-pixmap
+Depends: ${misc:Depends}, ${shlibs:Depends}, pcb-rnd-core (= 
${binary:Version}), librnd4-pixmap
 Description: Common export plugins.
  Export the board in vector graphics (svg, ps, eps), raster graphics
  (png, jpeg, etc.), gerber, 3d model in openscad, xy for pick and
@@ -192,7 +192,6 @@
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends},
pcb-rnd-core (= ${binary:Version}),
-   librnd4
 Replaces: pcb-rnd (<< 2.2.0-2)
 Breaks: pcb-rnd (<< 2.2.0-2)
 Description: Netlist/schematics import plugins.
@@ -203,7 +202,6 @@
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends},
pcb-rnd-core (= ${binary:Version}),
-   librnd4,
pcb-rnd-lib-io (= ${binary:Version}),
pcb-rnd-io-standard (= ${binary:Version})
 Description: Autoroute and autoplace.
@@ -238,7 +236,7 @@
 
 Package: pcb-rnd-core

 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, librnd4
+Depends: ${misc:Depends}, ${shlibs:Depends}
 Replaces: pcb-rnd (<< 2.2.0-2)
 Breaks: pcb-rnd (<< 2.2.0-2)
 Description: pcb-rnd executable with the core functionality
@@ -252,8 +250,7 @@
 Depends: ${misc:Depends}, ${shlibs:Depends},
pcb-rnd-core (= ${binary:Version}),
pcb-rnd-lib-io (= ${binary:Version}),
-   pcb-rnd-extra (= ${binary:Version}),
-   librnd4
+   pcb-rnd-extra (= ${binary:Version})
 Description: File format compatibility with other PCB layout designers.
  Load and/or save boards in file formats supported by other EDA tools,
  such as KiCAD, Eagle, protel/autotrax, etc.


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pcb-rnd
Source-Version: 3.1.4-2
Done: Bdale Garbee 

We believe that the bug you reported is fixed in the latest version of
pcb-rnd, 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.
Bdale Garbee  (supplier of updated pcb-rnd 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, 12 Apr 2024 12:50:16 -0600
Source: pcb-rnd
Architecture: source
Version: 3.1.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Bdale Garbee 
Closes: 1068812
Changes:
 pcb-rnd (3.1.4-2) unstable; urgency=medium
 .
   * remove extraneous librnd4 runtime dependencies, closes: #1068812
Checksums-Sha1:
 ca053c2131db3d1d8f3fa7aaaee2a246c31aa414 3121 pcb-rnd_3.1.4-2.dsc
 f3bd1ce4350209bb371884d950891c2cacb6f5c9 14172 pcb-rnd_3.1.4-2.debian.tar.xz
 136a70a9804c0ace641fbe04c4538f368d49e24a 17248 pcb-rnd_3.1.4-2_amd64.buildinfo
Checksums-Sha256:
 9a721fe4069b95e301daef09d2d3a4ad1777a960f633b4fc9ec36e678930d2c8 3121 
pcb-rnd_3.1.4-2.dsc
 f604a05c30c06e7a3def6bf44e7ce886eb06890f4692f9ce2e98866f78621310 14172 
pcb-rnd_3.1.4-2.debian.tar.xz
 e57f6162eb47e2e4c9a6a7ee67d5a9d25581d35be3408b32f7679aa7af6408a0 17248 
pcb-rnd_3.1.4-2_amd64.buildinfo
Files:
 d6205f5da5db460fc67b00e882bc78df 3121 electronics optional pcb-rnd_3.1.4-2.dsc
 21cc27e1f66593d54f9164de24729e35 14172 electronics op

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

[Jeremy Sowden]

On 2024-04-12, at 10:58:59 -0700, Xiyue Deng wrote:
> Jeremy Sowden  writes:
> > Control: tags -1 confirmed
> >
> > On 2024-04-12, at 16:56:25 +0200, Clément Calmels wrote:
> >> Package: mu4e
> >> Version: 1.12.3-2
> >> Severity: grave
> >> Justification: renders package unusable
> >> 
> >> Dear Maintainer,
> >> 
> >> I upgraded my Sid machine with the latest mu4e and maildir-utils
> >> packages : 1.12.3-2. Emacs isn't able to find the mu4e command
> >> anymore. From *Messages*: "Cannot open load file: No such file or
> >> directory, mu4e" when trying to load the mu4e library (using
> >> use-package).
> >> 
> >> It seems that some files are missing (mu4e.el at least).
> >
> > Confirmed.  Will get this fixed ASAP.  Thanks for the report.
>
> I made a MR[1] with a potential fix.  There is an alternative way to
> do this (where I left a comment[2]) so would like to hear your opinion
> before merging.  Thanks!

D'oh!  Somehow I missed the fact that meson was installing the .el
files, which is why I was copying them from the build directory.  Thank
you for your fresh eyes. :)

I pushed a different fix, so I will revert that and merge yours.

J.


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

Your message dated Fri, 12 Apr 2024 19:04:42 +
with message-id 
and subject line Bug#1068811: fixed in camv-rnd 1.1.4-3
has caused the Debian Bug report #1068811,
regarding camv-rnd: hardcoded librnd4 dependency
to be marked as done.

This means that you claim that the problem has been dealt 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.)


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

Package: camv-rnd
Version: 1.1.4-1
Severity: serious
Tags: patch


Hello, I found that librnd4 is correctly evaluated from shlibs:Depends in the 
core library and then it can be dropped also on core reverse-dependencies.


Please drop it.


Thanks for considering the patch.

diff -Nru camv-rnd-1.1.4/debian/control camv-rnd-1.1.4/debian/control
--- camv-rnd-1.1.4/debian/control   2023-11-30 16:53:21.0 +0100
+++ camv-rnd-1.1.4/debian/control   2024-04-11 15:44:20.0 +0200
@@ -47,7 +47,7 @@
 Architecture: any
 Replaces: camv-rnd (<< 1.1.0-1)
 Breaks: camv-rnd (<< 1.1.0-1)
-Depends: ${misc:Depends}, ${shlibs:Depends}, librnd4, librnd4-lib-gui
+Depends: ${misc:Depends}, ${shlibs:Depends}, librnd4-lib-gui
 Description: camv-rnd executable with the core functionality and boxsym-rnd
  Includes the data model, the most common action commands, the native
  file format. Can be used in headless mode or batch/scripted mode for
@@ -56,7 +56,7 @@
 
 Package: camv-rnd-export-vector

 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, camv-rnd-core (= 
${binary:Version}), librnd4
+Depends: ${misc:Depends}, ${shlibs:Depends}, camv-rnd-core (= 
${binary:Version})
 Description: Export formats: vector graphics
  Common vector graphic export formats: ps, eps, svg.
 


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: camv-rnd
Source-Version: 1.1.4-3
Done: Bdale Garbee 

We believe that the bug you reported is fixed in the latest version of
camv-rnd, 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.
Bdale Garbee  (supplier of updated camv-rnd 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, 12 Apr 2024 12:33:23 -0600
Source: camv-rnd
Architecture: source
Version: 1.1.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Bdale Garbee 
Closes: 1068811
Changes:
 camv-rnd (1.1.4-3) unstable; urgency=medium
 .
   * fix one more hard-coded librnd4 depdencency I missed, closes: #1068811
Checksums-Sha1:
 379819b443fc36b1ee033e93713c6af0ff637525 2492 camv-rnd_1.1.4-3.dsc
 6fcca1e67fe342dd95fa74095ab6517a0575c50f 4312 camv-rnd_1.1.4-3.debian.tar.xz
 104fc560a34b231858d27f7ae72964cf5e02a2bd 12231 camv-rnd_1.1.4-3_amd64.buildinfo
Checksums-Sha256:
 34338c80aa2fb2d0b8f0603e759232bb8bdf5f54dcacde9d40fb96be91aa90c9 2492 
camv-rnd_1.1.4-3.dsc
 cd06daaadda924bb95b036900b06f6d67ec925a3bfd2db4901ff7b3523fea80a 4312 
camv-rnd_1.1.4-3.debian.tar.xz
 22d3045de24d67663438f79c40dbd99d47c02d615ab8aee452eb8d4dfd3b8fe6 12231 
camv-rnd_1.1.4-3_amd64.buildinfo
Files:
 b2a64edef73ce3facc3740ba385bfd70 2492 electronics optional camv-rnd_1.1.4-3.dsc
 3c64646e596c7fc90a41c209f086c5a5 4312 electronics optional 
camv-rnd_1.1.4-3.debian.tar.xz
 44f3d97926f44851eb51fd981b3142cb 12231 electronics optional 
camv-rnd_1.1.4-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEHguq2FwiMqGzzpLrtwRxBYMLn6EFAmYZfz8ACgkQtwRxBYML
n6HJxA/9ESvoaYB23bsvS1QiHV9iBhE3XohtaHq9x+2r/yNNQlBTBeq62KzQjy18
MG4+Eqyf7ASSTa1tva67Zz40YpxKPZUz+JvI7XTOqT0Uz+MN+SgQG3tx3s78afXH
08B/cKoc+0HfXTr9ohtvULLmBSLV5A0ryZdrXnM1llYuEOScq8HskR7BZ/+6m2Qf
XSd8ZkAkEhnFg/HvwMY8pxx1nXVMb9V3C7VsGBfqwbWnH+9WnR1C4Yp5W6iDUrFc
740GeuhmKtcZpbqKE6l6wN6uzbwglFPpvfk4DeSartVB715c1BM96B0IlS/PycH+
U5NmahWImugXWyCObbr/TtVkkZiUFoGKFrQYk00R0IvGQarB48fN4iMvdvyyPppJ
b9FSLR5Z+3K3ICbWj0MJbD0lSlm1JcW1Jr/K8hls5/rx3oUpyq0JDWgQhbJecEaQ
yo3zpdePHNONa6sS5KD8fvtQqZLFTvNVNH6w8oYbkqMe3Y6PD2K/2Z97Vd9II67g
uS1r7Q7itUasSJPHSuLLg4LdADAS4zZEzki0gvaKiA01SPBExpIxhMaq9zx6TiML
+WKLBdspK37f/5oLP4fvuL/vN8VLDxLd/VrPNSIOk16JIv1g4tThvxnG82owJrXA
gCey8cZn9OfFDr/lV1

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

[Debian Bug Tracking System]

Your message dated Fri, 12 Apr 2024 19:05:38 +
with message-id 
and subject line Bug#1068810: fixed in sch-rnd 1.0.5-2
has caused the Debian Bug report #1068810,
regarding sch-rnd: hardcoded librnd4 dependency
to be marked as done.

This means that you claim that the problem has been dealt with.
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.)


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

Package: sch-rnd
Version: 1.0.5-1
Severity: normal
Tags: patch


Hello, I found that librnd4 is correctly evaluated from shlibs:Depends in the 
core library and then it can be dropped also on core reverse-dependencies.


Please drop it.


Thanks for considering the patch.

diff -Nru sch-rnd-1.0.5/debian/control sch-rnd-1.0.5/debian/control
--- sch-rnd-1.0.5/debian/control2024-04-11 06:59:15.0 +0200
+++ sch-rnd-1.0.5/debian/control2024-04-11 15:46:41.0 +0200
@@ -88,7 +88,7 @@
 
 Package: sch-rnd-core

 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, librnd4 (>= 4.1.0)
+Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: sch-rnd executable with the core functionality and boxsym-rnd
  Includes the data model, the most common action commands, the native
  file format. Can be used in headless mode or batch/scripted mode for
@@ -97,7 +97,7 @@
 
 Package: sch-rnd-export-vector

 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, sch-rnd-core (= ${binary:Version}), 
librnd4 (>= 4.1.0)
+Depends: ${misc:Depends}, ${shlibs:Depends}, sch-rnd-core (= ${binary:Version})
 Description: Export formats: vector graphics
  Common vector graphic export formats: ps, eps, svg.
 


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: sch-rnd
Source-Version: 1.0.5-2
Done: Bdale Garbee 

We believe that the bug you reported is fixed in the latest version of
sch-rnd, 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.
Bdale Garbee  (supplier of updated sch-rnd 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, 12 Apr 2024 12:39:36 -0600
Source: sch-rnd
Architecture: source
Version: 1.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Bdale Garbee 
Closes: 1068810
Changes:
 sch-rnd (1.0.5-2) unstable; urgency=medium
 .
   * remove erroneous librnd4 run-time dependencies, ok to do since the library
 in question was renamed for the t64 transition and the renamed library
 has not made it to testing yet, so only "new enough" versions of librnd4
 can possibly satisfy sch-rnd needs once it hits testing, closes: #1068810
Checksums-Sha1:
 825504648ca76ffcd4d506ac53e3388b1269b881 2593 sch-rnd_1.0.5-2.dsc
 a53bc75ba97feba26e232cb53d93ce6b03c0975d 6836 sch-rnd_1.0.5-2.debian.tar.xz
 5f33d6e5bd0bd80949380f9be0ab2da4e5f8d710 10758 sch-rnd_1.0.5-2_amd64.buildinfo
Checksums-Sha256:
 a8a86ac9d8f90137dbad406d39f41c936034004edbb5e299efd97e6110f9c6ae 2593 
sch-rnd_1.0.5-2.dsc
 e93aad1ae0d3281db12ef0703645b265719a61aa2cd58430b83758f2fb41bc2d 6836 
sch-rnd_1.0.5-2.debian.tar.xz
 98e0905a7f34a093e9b817057e07291bbb189ec055921371aa32a37e6d535e1c 10758 
sch-rnd_1.0.5-2_amd64.buildinfo
Files:
 c86fcc9a452b5ea9c327da7ab73c6d00 2593 electronics optional sch-rnd_1.0.5-2.dsc
 426f7fa6b98f689804a79e1cd5762ad1 6836 electronics optional 
sch-rnd_1.0.5-2.debian.tar.xz
 28e992a1d674100d6a7a930ec014bc63 10758 electronics optional 
sch-rnd_1.0.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEHguq2FwiMqGzzpLrtwRxBYMLn6EFAmYZgQoACgkQtwRxBYML
n6EbCw/9HiYWES4QKmM2c8lBdjSy9P/23h3s45wSs0c4GU2awUlG7ph17SdkQ+6r
5qZsBBtNdHGgvdECxnsu1OpuO0PzsNTkbiuaFh0DxCWCgIjjz2lZBtqAD1n6yoga
n9E6Kx2SvAqWNnRpAi8npogqteSLwCjaq+L2XWoavG7Ax/m9t8lNfoR7niaY+knS
8kKjshIn5reDvWv8CzEdl+VBSbwNPdjCzUpyh+EkHSsn5+EWCeVGHBcydj9g1CJz
cZKFckf+Mx7xCyzVHcyPL5c/3dS1uldobV+N1JwvGWC2/j6zo5Kmk+bV9gUdU273
6NFeQaq9ji/zAm/L8tmcx2rHxDC2iRLE61yW2qX8UQtyyfrsImogPuoE1EgUUNdN
pHORD5Ifqrzp7199dEJKUxW4inJnN2vM7SI4D0AQT9VVLmTaWUynAJANtiOfbqDS
JUltdF2U4liYb5JEzOdlnZol0C9b9lGNoK9Fs7qwD6ysY7K3oQm

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

[Debian Bug Tracking System]

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


-- 
1066243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bristol
Version: 0.60.11-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):
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/X11R6/include -pthread -Wall -g -I./../include/slab 
> -I./../include/bristol -I. -DBRISTOL_VOICECOUNT=32 
> -DBRISTOL_JACK_DEFAULT_MIDI -DBRISTOL_JACK_DEFAULT  
> -DBRISTOL_RAMP_RATE=10 -DBRISTOL_LIN_ATTACK -D_BRISTOL_DRAIN -D_BRISTOL_JACK 
> -D_BRISTOL_JACK_MIDI -D_BRISTOL_JACK_SESSION -DBRISTOL_HAS_ALSA=1   
> -ffast-math -fomit-frame-pointer -O2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -I/usr/X11R6/include -c -o 
> bristolmixer.o bristolmixer.c
> bristol.c: In function ‘main’:
> bristol.c:540:25: warning: this ‘if’ clause does not guard... 
> [-Wmisleading-indentation]
>   540 | if ((audiomain.iocount = atoi(argv[argCount + 
> 1]))
>   | ^~
> bristol.c:543:33: note: ...this statement, but the latter is misleadingly 
> indented as if it were guarded by the ‘if’
>   543 | argCount++;
>   | ^~~~
> bristolmemorymoog.c: In function ‘memorymoogController’:
> bristolmemorymoog.c:280:25: error: implicit declaration of function 
> ‘doPitchWheel’ [-Werror=implicit-function-declaration]
>   280 | doPitchWheel(baudio);
>   | ^~~~
> bristolmemorymoog.c: In function ‘operateOneMemoryMoog’:
> bristolmemorymoog.c:522: warning: ignoring ‘#pragma Need inverse’ 
> [-Wunknown-pragmas]
>   522 | #pragma Need inverse envelope here as well.
>   | 
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/X11R6/include -pthread -Wall -g -I./../include/slab 
> -I./../include/bristol -I. -DBRISTOL_VOICECOUNT=32 
> -DBRISTOL_JACK_DEFAULT_MIDI -DBRISTOL_JACK_DEFAULT  
> -DBRISTOL_RAMP_RATE=10 -DBRISTOL_LIN_ATTACK -D_BRISTOL_DRAIN -D_BRISTOL_JACK 
> -D_BRISTOL_JACK_MIDI -D_BRISTOL_JACK_SESSION -DBRISTOL_HAS_ALSA=1   
> -ffast-math -fomit-frame-pointer -O2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -I/usr/X11R6/include -c -o 
> bristolmm.o bristolmm.c
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/X11R6/include -pthread -Wall -g -I./../include/slab 
> -I./../include/bristol -I. -DBRISTOL_VOICECOUNT=32 
> -DBRISTOL_JACK_DEFAULT_MIDI -DBRISTOL_JACK_DEFAULT  
> -DBRISTOL_RAMP_RATE=10 -DBRISTOL_LIN_ATTACK -D_BRISTOL_DRAIN -D_BRISTOL_JACK 
> -D_BRISTOL_JACK_MIDI -D_BRISTOL_JACK_SESSION -DBRISTOL_HAS_ALSA=1   
> -ffast-math -fomit-frame-pointer -O2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -I/usr/X11R6/include -c -o 
> bristolobx.o bristolobx.c
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/X11R6/include -pthread -Wall -g -I./../include/slab 
> -I./../include/bristol -I. -DBRISTOL_VOICECOUNT=32 
> -DBRISTOL_JACK_DEFAULT_MIDI -DBRISTOL_JACK_DEFAULT  
> -DBRISTOL_RAMP_RATE=10 -DBRISTOL_LIN_ATTACK -D_BRISTOL_DRAIN -D_BRISTOL_JACK 
> -D_BRISTOL_JACK_MIDI -D_BRISTOL_JACK_SESSION -DBRISTOL_HAS_ALSA=1   
> -ffast-math -fomit-frame-pointer -O2 -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security 

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

[Debian Bug Tracking System]

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


-- 
1066223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ftpcopy
Version: 0.6.7-6
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[2]: Entering directory '/<>'
> ./package/compile
> Linking ./src/* into ./compile...
> Compiling everything in ./compile...
> gmake[3]: Entering directory '/<>/compile'
> cmp: auto-compiler-config.stamp: No such file or directory
> configuration has changed
> conftest-1663389.c: In function ‘main’:
> conftest-1663389.c:6:12: warning: format ‘%d’ expects argument of type ‘int’, 
> but argument 2 has type ‘long unsigned int’ [-Wformat=]
> 6 |   printf("%d\n",8*sizeof(x));
>   |   ~^~~~
>   |||
>   |int  long unsigned int
>   |   %ld
> gmake[4]: Entering directory '/<>/compile'
> gmake[4]: Leaving directory '/<>/compile'
> sh typesize.sh >typesize.t
> rm -f typesize.t
> touch auto-typesize.stamp
> sh find_socket_func.sh >auto-socket.t && mv auto-socket.t auto-socket.lib
> sh have_func.sh fsync "#include " "fsync(0)" "" "" 
> >auto-have_fsync.h.t && mv auto-have_fsync.h.t auto-have_fsync.h
> sh have_func.sh utimes "#include " "utimes(0,0)" "" "" 
> >auto-have_utimes.h.t && mv auto-have_utimes.h.t auto-have_utimes.h
> conftest1663576.c: In function ‘main’:
> conftest1663576.c:5:9: warning: argument 1 null where non-null expected 
> [-Wnonnull]
> 5 | utimes(0,0)
>   | ^~
> In file included from conftest1663576.c:2:
> /usr/include/x86_64-linux-gnu/sys/time.h:162:12: note: in a call to function 
> ‘utimes’ declared ‘nonnull’
>   162 | extern int utimes (const char *__file, const struct timeval __tvp[2])
>   |^~
> conftest1663576.c:7:9: error: implicit declaration of function ‘_exit’ 
> [-Werror=implicit-function-declaration]
> 7 | _exit(0);
>   | ^
> conftest1663576.c:7:9: warning: incompatible implicit declaration of built-in 
> function ‘_exit’ [-Wbuiltin-declaration-mismatch]
> cc1: some warnings being treated as errors
> sh gettimeofday.sh >gettimeofday.t && mv gettimeofday.t auto-gettimeofday.lib
> gmake[3]: *** [Makefile:100: auto-gettimeofday.lib] Error 1
> gmake[3]: Leaving directory '/<>/compile'
> make[2]: *** [Makefile:2: all] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/ftpcopy_0.6.7-6_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&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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: ftpcopy
Source-Version: 0.6.7-7
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
ftpcopy, 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 maintena

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

[Bdale Garbee]

Gianfranco Costamagna  writes:

> yes, but the library was renamed in librnd4t64, so either you need to
> depend on the new one, or drop it, to let the auto decrufter finish
> the time64_t transition and decruft it.

Ah, thank you, that's a useful observation.  Since the relevant version
hasn't made it into testing with the changed library names yet, the
easiest course of action is indeed to just drop this dependency, as any
version of librnd4t64 that's ever in testing will be "new enough" to
meet the new sch-rnd requirement.

> Depending on NBS packages is RC critical.

FWIW, I had to look up what "NBS" means in this context.  A new acronym
to me despite being part of Debian since 1994...

Bdale


signature.asc
Description: PGP signature

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

[Adrian Bunk]

Source: fwbuilder
Version: 5.3.7-7
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Jeremy Bícha 

https://buildd.debian.org/status/logs.php?pkg=fwbuilder&ver=5.3.7-7

...
 fakeroot debian/rules clean
dh clean
dh: warning: Please specify the debhelper compat level exactly once.
dh: warning:  * debian/compat requests compat 9.
dh: warning:  * debian/control requests compat 12 via "debhelper-compat (= 12)"
dh: warning: 
dh: warning: Hint: If you just added a build-dependency on debhelper-compat, 
then please remember to remove debian/compat
dh: warning: 
dh: error: debhelper compat level specified both in debian/compat and in 
debian/control
make: *** [debian/rules:13: clean] Error 255

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

[Xiyue Deng]

Jeremy Sowden  writes:

> Control: tags -1 confirmed
>
> On 2024-04-12, at 16:56:25 +0200, Clément Calmels wrote:
>> Package: mu4e
>> Version: 1.12.3-2
>> Severity: grave
>> Justification: renders package unusable
>> 
>> Dear Maintainer,
>> 
>> I upgraded my Sid machine with the latest mu4e and maildir-utils
>> packages : 1.12.3-2. Emacs isn't able to find the mu4e command
>> anymore. From *Messages*: "Cannot open load file: No such file or
>> directory, mu4e" when trying to load the mu4e library (using
>> use-package).
>> 
>> It seems that some files are missing (mu4e.el at least).
>
> Confirmed.  Will get this fixed ASAP.  Thanks for the report.
>
> J.
>

Hi Jeremy,

I made a MR[1] with a potential fix.  There is an alternative way to do
this (where I left a comment[2]) so would like to hear your opinion
before merging.  Thanks!

-- 
Xiyue Deng

[1] https://salsa.debian.org/emacsen-team/maildir-utils/-/merge_requests/6
[2] https://salsa.debian.org/emacsen-team/maildir-utils/-/merge_requests/6/diffs


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

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


-- 
1068134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Close using correct address
Forgot the hyphen in 1068134-d...@bugs.debian.org



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

Processed: Also set fixed...

[Debian Bug Tracking System]

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

> fixed 1068133 5.1-3
Bug #1068133 {Done: Mattias Ellert } 
[src:globus-gram-audit] globus-gram-audit: arch:all package depends on pre-t64 
library
Marked as fixed in versions globus-gram-audit/5.1-3.
> fixed 1068134 7.3-2
Bug #1068134 [src:globus-gram-job-manager-scripts] 
globus-gram-job-manager-scripts: arch:all package depends on pre-t64 library
Marked as fixed in versions globus-gram-job-manager-scripts/7.3-2.
>
End of message, stopping processing here.

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

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

[Debian Bug Tracking System]

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


-- 
1068133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Control: found 1068133 5.1-2
Control: notfound 1068133 5.1-3

The bug reported here is already fixed in the version for which the bug
was reported.

This bug was present in the previous version. The current version was
uploaded precisely to fix the problem reported.

Previous version (5.1-2) had

Depends: libglobus-common0 (>= 15)

Current version (5.1-3) has

Depends: libglobus-common0 (>= 15) | libglobus-common0t64 (>= 15)

I.e. it does not depend only on the old package name, but on either the
new or the old. The package is therefore not blocking the t64
transition.

Mattias

sön 2024-03-31 klockan 17:39 +0200 skrev 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
> 
> VARNING: Klicka inte på länkar och öppna inte bilagor om du inte
> känner igen avsändaren och vet att innehållet är säkert.
> CAUTION: Do not click on links or open attachments unless you
> recognise the sender and know the content is safe.



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

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

[Debian Bug Tracking System]

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

This means that you claim that 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.)


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

Package: src:circe
Version: 2.12-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh build --with elpa
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
skipping upstream build
make[1]: Leaving directory '/<>'
   dh_elpa_test
buttercup -L .
Loading /etc/emacs/site-start.d/00debian.el (source)...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Running 214 specs.

Circe chat mode
  creation function
should have circe-server-buffer set in the mode hook
should have circe-server-buffer set in the mode hook (1.93ms)

The `circe-version' command
  should display the current version
  should display the current version (0.07ms)

The `circe-duration-string' function
  should handle very short amounts of time
  should handle very short amounts of time (0.11ms)
  should support second granularity
  should support second granularity (0.17ms)
  should support minute granularity
  should support minute granularity (0.25ms)
  should support monthly granularity
  should support monthly granularity (0.11ms)

Circe's completion facility
  should complete nicks with colon at the beginning of the input
  should complete nicks with colon at the beginning of the input 
(10.16ms)
  should complete nicks without colon later in the input
  should complete nicks without colon later in the input (8.96ms)

Display of
  RPL_WHOISREPLY
should show idle time
should show idle time (0.15ms)
should show idle time and signon time
should show idle time and signon time (0.18ms)
  RPL_TOPICWHOTIME
should show current topic time
should show current topic time (0.19ms)
should show current topic time in a different channel
should show current topic time in a different channel (0.20ms)
  CTCP ACTION
should show a query in a query buffer
should show a query in a query buffer (0.12ms)
should show a query in the current buffer
should show a query in the current buffer (0.12ms)
should show a channel action
should show a channel action (0.12ms)
  CTCP PING
should display unknown seconds when passed nil for text
should display unknown seconds when passed nil for text (0.15ms)

The `irc-connect' function
  should return a process when using non-tls connections
  should return a process when using non-tls connections (0.12ms)
  should return a process when using tls connections
  should return a process when using tls connections (0.43ms)
  should not use nowait if it is not supported
  should not use nowait if it is not supported (0.21ms)
  should call the sentinel if nowait is not supported
  should call the sentinel if nowait is not supported (0.08ms)

Connection options
  should retrieve options set
  should retrieve options set (0.34ms)

The `irc--sentinel' function
  should emit conn.failed for a failed event
  should emit conn.failed for a failed event (0.12ms)
  should emit conn.connected on an open event
  should emit conn.connected on an open event (0.08ms)
  should emit conn.disconnected for a broken connection
  should emit conn.disconnected for a broken connection (0.08ms)
  should emit conn.disconnected for a finished process
  should emit conn.disconnected for a finished process (0.07ms)
  should emit conn.disconnected for an exiting process
  should emit conn.disconnected for an exiting process (0.07ms)
  should ignored killed processes
  should ignored killed processes (0.06ms)
  should ignore deleted processes
  should ignore deleted processes (0.06ms)
  should raise an error for unknown events
  should raise an error for unknown events (0.09ms)

The `irc--filter' function
  should handle single lines
  should handle 

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

[Debian Bug Tracking System]

Processing control commands:

> found 1068134 7.3-1
Bug #1068134 [src:globus-gram-job-manager-scripts] 
globus-gram-job-manager-scripts: arch:all package depends on pre-t64 library
Marked as found in versions globus-gram-job-manager-scripts/7.3-1.
> notfound 1068134 7.3-2
Bug #1068134 [src:globus-gram-job-manager-scripts] 
globus-gram-job-manager-scripts: arch:all package depends on pre-t64 library
No longer marked as found in versions globus-gram-job-manager-scripts/7.3-2.

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

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

[Mattias Ellert]

Control: found 1068134 7.3-1
Control: notfound 1068134 7.3-2

The bug reported here is already fixed in the version for which the bug
was reported.

This bug was present in the previous version. The current version was
uploaded precisely to fix the problem reported.

Previous version (7.3-1) had

Depends: libglobus-common0 (>= 15)

Current version (7.3-2) has

Depends: libglobus-common0 (>= 15) | libglobus-common0t64 (>= 15)

I.e. it does not depend only on the old package name, but on either the
new or the old. The package is therefore not blocking the t64
transition.

Mattias

sön 2024-03-31 klockan 17:41 +0200 skrev 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
> 
> VARNING: Klicka inte på länkar och öppna inte bilagor om du inte
> känner igen avsändaren och vet att innehållet är säkert.
> CAUTION: Do not click on links or open attachments unless you
> recognise the sender and know the content is safe.



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

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

[Debian Bug Tracking System]

Processing control commands:

> found 1068133 5.1-2
Bug #1068133 [src:globus-gram-audit] globus-gram-audit: arch:all package 
depends on pre-t64 library
Marked as found in versions globus-gram-audit/5.1-2.
> notfound 1068133 5.1-3
Bug #1068133 [src:globus-gram-audit] globus-gram-audit: arch:all package 
depends on pre-t64 library
No longer marked as found in versions globus-gram-audit/5.1-3.

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

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

[Mattias Ellert]

Control: found 1068133 5.1-2
Control: notfound 1068133 5.1-3

The bug reported here is already fixed in the version for which the bug
was reported.

This bug was present in the previous version. The current version was
uploaded precisely to fix the problem reported.

Previous version (5.1-2) had

Depends: libglobus-common0 (>= 15)

Current version (5.1-3) has

Depends: libglobus-common0 (>= 15) | libglobus-common0t64 (>= 15)

I.e. it does not depend only on the old package name, but on either the
new or the old. The package is therefore not blocking the t64
transition.

Mattias

sön 2024-03-31 klockan 17:39 +0200 skrev 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
> 
> VARNING: Klicka inte på länkar och öppna inte bilagor om du inte
> känner igen avsändaren och vet att innehållet är säkert.
> CAUTION: Do not click on links or open attachments unless you
> recognise the sender and know the content is safe.



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

Bug#1068757: marked as pending in python-musicpd

[Geoffroy Youri Berret]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-musicpd/-/commit/a9aca01159a41f0484456e19336d76cf6153fcf6


Remove obsolete dh option

Closes: #1068757


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1068757

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1068757 [src:python-musicpd] python-musicpd: FTBFS: dh_installchangelogs: 
error: could not find changelog
Added tag(s) pending.

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

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

[Debian Bug Tracking System]

Your message dated Fri, 12 Apr 2024 16:49:02 +
with message-id 
and subject line Bug#1066238: fixed in dvbackup 1:0.0.4-10
has caused the Debian Bug report #1066238,
regarding dvbackup: FTBFS: dvconnect.c:264:33: error: implicit declaration of 
function ‘memcpy’ [-Werror=implicit-function-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.)


-- 
1066238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dvbackup
Version: 1:0.0.4-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):
> gcc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -fPIE -pie -Wl,-z,relro -Wl,-z,now -D_FORTIFY_SOURCE=2 -DHAVE_LIBPOPT -o 
> dvconnect dvconnect.c -lpopt -lpthread
> dvconnect.c: In function ‘handle_packet’:
> dvconnect.c:264:33: error: implicit declaration of function ‘memcpy’ 
> [-Werror=implicit-function-declaration]
>   264 | memcpy(p_out, data + 12, 480);
>   | ^~
> dvconnect.c:22:1: note: include ‘’ or provide a declaration of 
> ‘memcpy’
>21 | #include 
>   +++ |+#include 
>22 | 
> dvconnect.c:264:33: warning: incompatible implicit declaration of built-in 
> function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   264 | memcpy(p_out, data + 12, 480);
>   | ^~
> dvconnect.c:264:33: note: include ‘’ or provide a declaration of 
> ‘memcpy’
> dvconnect.c: In function ‘capture_raw’:
> dvconnect.c:326:26: error: implicit declaration of function ‘strcmp’ 
> [-Werror=implicit-function-declaration]
>   326 | if (!filename || strcmp(filename, "-") == 0) {
>   |  ^~
> dvconnect.c:326:26: note: include ‘’ or provide a declaration of 
> ‘strcmp’
> dvconnect.c:401:25: error: implicit declaration of function ‘memset’ 
> [-Werror=implicit-function-declaration]
>   401 | memset(curr, 0, v.buf_size);
>   | ^~
> dvconnect.c:401:25: note: include ‘’ or provide a declaration of 
> ‘memset’
> dvconnect.c:401:25: warning: incompatible implicit declaration of built-in 
> function ‘memset’ [-Wbuiltin-declaration-mismatch]
> dvconnect.c:401:25: note: include ‘’ or provide a declaration of 
> ‘memset’
> dvconnect.c:426:41: warning: incompatible implicit declaration of built-in 
> function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   426 | memcpy(outbuf + outbuf_used, 
> curr+ofs,
>   | ^~
> dvconnect.c:426:41: note: include ‘’ or provide a declaration of 
> ‘memcpy’
> dvconnect.c:431:41: warning: incompatible implicit declaration of built-in 
> function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   431 | memcpy(outbuf + outbuf_used,
>   | ^~
> dvconnect.c:431:41: note: include ‘’ or provide a declaration of 
> ‘memcpy’
> dvconnect.c: In function ‘fill_buffer’:
> dvconnect.c:584:33: warning: incompatible implicit declaration of built-in 
> function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   584 | memcpy(f_node->data, 
> underrun_data_frame,
>   | ^~
> dvconnect.c:584:33: note: include ‘’ or provide a declaration of 
> ‘memcpy’
> dvconnect.c:633:25: warning: incompatible implicit declaration of built-in 
> function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   633 | memcpy(p, frame + vdata, 480);
>   | ^~
> dvconnect.c:633:25: note: include ‘’ or provide a declaration of 
> ‘memcpy’
> dvconnect.c: In function ‘send_raw’:
> dvconnect.c:782:9: warning: incompatible implicit declaration of built-in 
> function ‘memset’ [-Wbuiltin-declaration-mismatch]
>   782 | memset(packet_sizes, 0, sizeof(packet_sizes));
>   | ^~
> dvconnect.c:782:9: note

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

[Debian Bug Tracking System]

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


-- 
1066626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-svn
Version: 0.4.0-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):
> /<>/debian/.dh_lua-libtool/libtool --tag=CC --mode=compile 
> x86_64-linux-gnu-gcc -c -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 -I/usr/include/lua5.1  -I 
> /usr/include/subversion-1 -DLINUX -D_REENTRANT -D_GNU_SOURCE 
> -I/usr/include/apr-1.0  -Wall -Wextra -o 
> /<>/5.1-svn/src/luasvn.lo src/luasvn.c 
> libtool: compile:  x86_64-linux-gnu-gcc -c -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 
> -I/usr/include/lua5.1 -I /usr/include/subversion-1 -DLINUX -D_REENTRANT 
> -D_GNU_SOURCE -I/usr/include/apr-1.0 -Wall -Wextra src/luasvn.c  -fPIC -DPIC 
> -o /<>/5.1-svn/src/.libs/luasvn.o
> src/luasvn.c: In function ‘init_pool’:
> src/luasvn.c:58:9: warning: ‘svn_dso_initialize’ is deprecated 
> [-Wdeprecated-declarations]
>58 | svn_dso_initialize ();
>   | ^~
> In file included from src/luasvn.c:5:
> /usr/include/subversion-1/svn_dso.h:70:1: note: declared here
>70 | svn_dso_initialize(void);
>   | ^~
> src/luasvn.c: In function ‘init_function’:
> src/luasvn.c:96:9: warning: ‘svn_client_create_context’ is deprecated 
> [-Wdeprecated-declarations]
>96 | err = svn_client_create_context (ctx, *pool);
>   | ^~~
> In file included from src/luasvn.c:4:
> /usr/include/subversion-1/svn_client.h:1117:1: note: declared here
>  1117 | svn_client_create_context(svn_client_ctx_t **ctx,
>   | ^
> src/luasvn.c:105:9: warning: ‘svn_cmdline_setup_auth_baton’ is deprecated 
> [-Wdeprecated-declarations]
>   105 | err = svn_cmdline_setup_auth_baton(&ab,
>   | ^~~
> In file included from src/luasvn.c:8:
> /usr/include/subversion-1/svn_cmdline.h:405:1: note: declared here
>   405 | svn_cmdline_setup_auth_baton(svn_auth_baton_t **ab,
>   | ^~~~
> src/luasvn.c: In function ‘log_msg_func2’:
> src/luasvn.c:179:54: warning: unused parameter ‘commit_items’ 
> [-Wunused-parameter]
>   179 |const apr_array_header_t *commit_items,
>   |~~^~~~
> src/luasvn.c: In function ‘l_add’:
> src/luasvn.c:236:9: warning: ‘svn_path_canonicalize’ is deprecated 
> [-Wdeprecated-declarations]
>   236 | path = svn_path_canonicalize (path, pool);
>   | ^~~~
> In file included from src/luasvn.c:6:
> /usr/include/subversion-1/svn_path.h:284:1: note: declared here
>   284 | svn_path_canonicalize(const char *path, apr_pool_t *pool);
>   | ^
> src/luasvn.c:238:9: warning: ‘svn_client_add3’ is deprecated 
> [-Wdeprecated-declarations]
>   238 | err = svn_client_add3 (path, recursive, force, no_ignore, 
> ctx, pool);
>   | ^~~
> /usr/include/subversion-1/svn_client.h:1714:1: note: declared here
>  1714 | svn_client_add3(const char *path,
>   | ^~~
> src/luasvn.c: In function ‘l_cat’:
> src/luasvn.c:279:9: warning: ‘svn_path_canonicalize’ is deprecated 
> [-Wdeprecated-declarations]
>   279 | path = svn_path_canonicalize (path, pool);
>   | ^~~~
> /usr/include/subversion-1/svn_path.h:284:1: note: declared here
>   284 | svn_path_canonicalize(const char *path, apr_pool_t *pool);
>   

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #1068869 [mu4e] mu4e: Cannot open load file: No such file or directory, mu4e
Added tag(s) confirmed.

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

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

[Jeremy Sowden]

Control: tags -1 confirmed

On 2024-04-12, at 16:56:25 +0200, Clément Calmels wrote:
> Package: mu4e
> Version: 1.12.3-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> I upgraded my Sid machine with the latest mu4e and maildir-utils
> packages : 1.12.3-2. Emacs isn't able to find the mu4e command
> anymore. From *Messages*: "Cannot open load file: No such file or
> directory, mu4e" when trying to load the mu4e library (using
> use-package).
> 
> It seems that some files are missing (mu4e.el at least).

Confirmed.  Will get this fixed ASAP.  Thanks for the report.

J.

> Package version 1.12.3-2:
> $ dpkg -L mu4e
> /.
> /usr
> /usr/lib
> /usr/lib/emacsen-common
> /usr/lib/emacsen-common/packages
> /usr/lib/emacsen-common/packages/compat
> /usr/lib/emacsen-common/packages/compat/mu4e
> /usr/lib/emacsen-common/packages/install
> /usr/lib/emacsen-common/packages/install/mu4e
> /usr/lib/emacsen-common/packages/remove
> /usr/lib/emacsen-common/packages/remove/mu4e
> /usr/share
> /usr/share/doc
> /usr/share/doc/mu4e
> /usr/share/doc/mu4e/NEWS.Debian.gz
> /usr/share/doc/mu4e/changelog.Debian.gz
> /usr/share/doc/mu4e/copyright
> /usr/share/emacs
> /usr/share/emacs/site-lisp
> /usr/share/emacs/site-lisp/elpa-src
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3/mu4e-autoloads.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3/mu4e-config.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3/mu4e-pkg.el
> /usr/share/info
> /usr/share/info/mu4e.info.gz
> /usr/share/doc/mu4e/NEWS.org
> /usr/share/doc/mu4e/README.org.gz
> /usr/share/doc/mu4e/TODO.gz
> /etc/emacs/site-start.d/50mu4e.el
> 
> Package version 1.10.8-2:
> $ dpkg -L mu4e
> /.
> /usr
> /usr/lib
> /usr/lib/emacsen-common
> /usr/lib/emacsen-common/packages
> /usr/lib/emacsen-common/packages/compat
> /usr/lib/emacsen-common/packages/compat/mu4e
> /usr/lib/emacsen-common/packages/install
> /usr/lib/emacsen-common/packages/install/mu4e
> /usr/lib/emacsen-common/packages/remove
> /usr/lib/emacsen-common/packages/remove/mu4e
> /usr/share
> /usr/share/doc
> /usr/share/doc/mu4e
> /usr/share/doc/mu4e/NEWS.Debian.gz
> /usr/share/doc/mu4e/changelog.Debian.gz
> /usr/share/doc/mu4e/changelog.gz
> /usr/share/doc/mu4e/copyright
> /usr/share/emacs
> /usr/share/emacs/site-lisp
> /usr/share/emacs/site-lisp/elpa-src
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-actions.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-autoloads.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-bookmarks.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-compose.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-config.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-contacts.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-context.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-contrib.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-draft.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-folders.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-headers.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-helpers.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-icalendar.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-lists.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-main.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-mark.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-message.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-modeline.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-notification.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-obsolete.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-org.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-pkg.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-query-items.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-search.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-server.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-speedbar.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-update.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-vars.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-view.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-window.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e.el
> /usr/share/info
> /usr/share/info/mu4e.info.gz
> /usr/share/doc/mu4e/NEWS.org
> /usr/share/doc/mu4e/README.org.gz
> /usr/share/doc/mu4e/TODO.gz
> /etc/emacs/site-start.d/50mu4e.el
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 6.7.9-amd64 (SMP w/24 CPU threads; PREEMPT)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/

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

[Debian Bug Tracking System]

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

This means that you claim that the 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.)


-- 
1049951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fwbuilder
Version: 5.3.7-5
Severity: serious

Hi,

this package is maintained by ubuntu-devel-disc...@lists.ubuntu.com,
which is not a suitable contact point for Debian packages maintenance
according to https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

This is most likely due to generating the source package on an Ubuntu
machine. I think there's some magic that replaces the Maintainer field
in the Ubuntu tooling.
--- End Message ---
--- Begin Message ---
Source: fwbuilder
Source-Version: 5.3.7-7
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated fwbuilder 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, 12 Apr 2024 11:12:02 -0400
Source: fwbuilder
Built-For-Profiles: noudeb
Architecture: source
Version: 5.3.7-7
Distribution: unstable
Urgency: medium
Maintainer: Sylvestre Ledru 
Changed-By: Jeremy Bícha 
Closes: 972163 984144 1049951
Changes:
 fwbuilder (5.3.7-7) unstable; urgency=medium
 .
   * Team upload
   * Fix Maintainer field (Closes: #1049951)
 .
 fwbuilder (5.3.7-6) unstable; urgency=medium
 .
   [ Lukas Mardian ]
   * d/p/ed4db20ec6cabfaea9c36187b7ce40d9d93c6c79.patch: Cherry-pick upstream
 commit to fix FTBFS with C++17/GCC-11
 (Closes: #984144)
 .
 fwbuilder (5.3.7-5) unstable; urgency=medium
 .
   [ Lisandro Damián Nicanor Pérez Meyer ]
   * Remove qt5-default from build dependencies (Closes: #972163).
 - Export QT_SELECT in order to let qtchooser select the right version.
 .
   [ Sylvestre Ledru ]
   * Trim trailing whitespace.
   * Bump debhelper from deprecated 9 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Update standards version to 4.2.1, no changes needed.
Checksums-Sha1:
 02df819520365f58878cb3274652e3d0dfbcf31d 2113 fwbuilder_5.3.7-7.dsc
 e022feb071dbf3c324c77a521bddf98112aab598 37404 fwbuilder_5.3.7-7.debian.tar.xz
 ec7aa7ab0db8ccced083ed061724515aefe94e67 7755 
fwbuilder_5.3.7-7_source.buildinfo
Checksums-Sha256:
 29e1f2186ecc7fdf711092f3f744b45b0ca4b4bc3fe357bb2beaa1ea98a2e2aa 2113 
fwbuilder_5.3.7-7.dsc
 2d10d88bd696b2b6eec02b6c050259c59478764837db764ef76f684853a9118c 37404 
fwbuilder_5.3.7-7.debian.tar.xz
 606013d022f2b2ac72555f68e01f0a6976653d197e9f42c7d5a86696db6d0ee8 7755 
fwbuilder_5.3.7-7_source.buildinfo
Files:
 fe363f9be810537c3b24b564bdaa3733 2113 net optional fwbuilder_5.3.7-7.dsc
 a45cdfe775be235f93e83c1faae7ec4c 37404 net optional 
fwbuilder_5.3.7-7.debian.tar.xz
 993b86f8972747064bee69809185aa41 7755 net optional 
fwbuilder_5.3.7-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmYZT48ACgkQ5mx3Wuv+
bH1zkw//dTaLgHWj065S7ukHPDZpWkouAxPRZ1G03zbqDNnx4aZJ2UyQLN7mXGej
LsWb7DQ9toA7l8/iqVZne/VeMgty31FzVsuGplSeobZvqWde3y0CFyGa9stHXlLj
pJ3NbSLrMVTSzu547LlAI9/yhWArAO2Fa/8ZqOoIkByn5vpUUPjt5U2sEZqnkL1J
Y2VRt4u/u/dwHfmqw4na8xiTgSTWq+QYwYaDXY7eNKqtF8AFvWNbO1MbgYA/Nwrt
A0HoY8hfUPhHb7zumfVM75GLMoW/vuFyElUvFEHlefi0IZdeby31VUTckxJr5k8x
KtzVK6/+sKckt/jF1s8D8oC/210PqLZ55TOQSyRKLrRMCM/1i6UMGfUmcirWfOzd
7+X/bFi+Ki14x2gClrnZErkobBxKo/zB/fH4n0yAqi6z3ohWljUPMpUOlaebuTfw
oyXaZ3UdyF4t7+UGjrlkcNpHAU8M9Cyt2tJ+FdVeqMOtUvapsYTShimBFIaoztQR
hiPAmFRKug2eyN2rp/Kwa+I6cOs6bnUCDkSWgTkHrWudyb3y6NK/c5T/7XHd+K9a
CepDvO5jXDsB6LhE3+QdfCIE0Bb81on9u4YkdLZZeYXwFqooDBXgvDlUD70ezNEB
SeA1Y/EUMnjVcdUe3B9inYREsnRitEu8MVwgYZLO1dNZGTIHZho=
=bnX/
-END PGP SIGNATURE-



pgpOL69XS1U3t.pgp
Description: PGP signature
--- End

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

[Clément Calmels]

Package: mu4e
Version: 1.12.3-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I upgraded my Sid machine with the latest mu4e and maildir-utils
packages : 1.12.3-2. Emacs isn't able to find the mu4e command
anymore. From *Messages*: "Cannot open load file: No such file or
directory, mu4e" when trying to load the mu4e library (using
use-package).

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

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


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

Kernel: Linux 6.7.9-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 mu4e depends on:
ii  dh-elpa-helper  2.0.17
ii  emacsen-common  3.0.5
ii  maildir-utils   1.12.3-2

mu4e recommends no packages.

mu4e suggests no packages.

-- no debconf information

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

[Debian Bug Tracking System]

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

> reassign 1052197 xorgxrdp
Bug #1052197 {Done: Gürkan Myczko } [xrdp] xrdp: after 
bullseye-security upgrade, empty turquoise screen after logging in
Bug reassigned from package 'xrdp' to 'xorgxrdp'.
No longer marked as found in versions xrdp/0.9.21.1-1~deb11u1.
Ignoring request to alter fixed versions of bug #1052197 to the same values 
previously set
> affects 1052197 xrdp
Bug #1052197 {Done: Gürkan Myczko } [xorgxrdp] xrdp: after 
bullseye-security upgrade, empty turquoise screen after logging in
Added indication that 1052197 affects xrdp
> found 1052197 1:0.2.12-1
Bug #1052197 {Done: Gürkan Myczko } [xorgxrdp] xrdp: after 
bullseye-security upgrade, empty turquoise screen after logging in
Marked as found in versions xorgxrdp/1:0.2.12-1 and reopened.
> fixed 1052197 1:0.2.12-1+deb11u1
Bug #1052197 [xorgxrdp] xrdp: after bullseye-security upgrade, empty turquoise 
screen after logging in
Marked as fixed in versions xorgxrdp/1:0.2.12-1+deb11u1.
> fixed 1052197 1:0.9.19-1
Bug #1052197 [xorgxrdp] xrdp: after bullseye-security upgrade, empty turquoise 
screen after logging in
Marked as fixed in versions xorgxrdp/1:0.9.19-1.
> thanks
Stopping processing here.

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

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

[Thorsten Glaser]

reassign 1052197 xorgxrdp
affects 1052197 xrdp
found 1052197 1:0.2.12-1
fixed 1052197 1:0.2.12-1+deb11u1
fixed 1052197 1:0.9.19-1
thanks

Gürkan Myczko dixit:

> This bug has been closed upstream, and upstream packages have been in
> the archive for a while.

No, the bug has been fixed by binNMUing the affected package
(or, actually, no-change-uploading, with apo forgetting to close the bug)
so it got rebuilt against the upgraded other package. But,
yes, the bug can be closed.

bye,
//mirabilos
-- 
[16:04:33] bkix: "veni vidi violini"
[16:04:45] bkix: "ich kam, sah und vergeigte"...

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

[Guilhem Moulin]

On Fri, 12 Apr 2024 at 14:37:16 +0200, Guilhem Moulin wrote:
> What is that “GUI” view?  src:cryptsetup doesn't provide that, I wonder
> if it might be what needs libphtread.

FWIW, I later noticed you used a splash screen (plymouth) and thought it
might be because of that, but I still cannot reproduce the issue in a
bookworm VM upgraded to sid (using d-i's “encrypted LVM” layout + a
splash screen).

>> After a ctrl-alt-del, I got to the console and there it showed an error about
>> libgcc_s.so.1 not available and aborting.

What was that error message exactly?

> If you still have the broken initramfs image, please extract it with
> `unmkinitramfs /path/to/broken.initrd.img /path/to/destdir` and try to
> find which executable / shared library needs libphtread, for instance
> with
>
>cd /path/to/destdir
>for p in $(find -P {usr/,}lib/x86_64-linux-gnu  {usr/,}{,s}bin/ -type f); 
> do objdump -p "$p" 2>/dev/null | grep -q pthread && echo "$p"; done

Erm no, that likely won't work since pthread functions have moved from
libpthread.so.1 to libc.so.6 with glibc 2.34.  Otherwise copy_exec()
would have pulled in libgcc_s.  New attempt:

rm -rf /tmp/initramfs-destdir && \
mkdir -m0700 /tmp/initramfs-destdir && \
unmkinitramfs /path/to/broken.initrd.img /tmp/initramfs-destdir && \
for p in $(find /tmp/initramfs-destdir/main -type f | sort); do \
  objdump -T "$p" 2>&1 | grep pthread_exit && echo "^^ $p"; \
done

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#1067234: symfit: autopkgtest regression with NumPy 1.26

[Michael R. Crusoe]

On Mon, 8 Apr 2024 17:09:33 + Graham Inggs  wrote:
> Control: tags -1 + patch
>
> Hi Maintainer
>
> While asserting that no warnings are raised is a useful test for the
> upstream developers, I don't think it makes sense for downstreams.
>
> I propose to disable the assertion as follows:
>
> --- a/tests/test_minimizers.py
> +++ b/tests/test_minimizers.py
> @@ -117,7 +117,7 @@
> # Should no longer raise warnings, because internally we practice
> # what we preach.
> fit_custom = BFGS(chi_squared, [a, b])
> - assert len(recwarn) == 0
> +# assert len(recwarn) == 0
>
> fit_custom_result = fit_custom.execute()
>
> Please let me know if you are happy with a team upload and I will proceed.
> As a bonus, I attach a patch that fixes several SyntaxWarnings that
> occur with Python 3.12.


Hey Graham,

A team upload is fine, thanks for the fixes; please go ahead and upload them.



OpenPGP_signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + unreproducible moreinfo
Bug #1068849 [cryptsetup-initramfs] cryptsetup: Fails to unlock the filesystem 
with missing libgcc_s.so.1
Bug #1068848 [cryptsetup-initramfs] cryptsetup: Fails to unlock the filesystem 
with missing libgcc_s.so.1
Added tag(s) unreproducible and moreinfo.
Added tag(s) unreproducible and moreinfo.

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

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

[Guilhem Moulin]

Control: tag -1 + unreproducible moreinfo

On Fri, 12 Apr 2024 at 12:45:09 +0200, Milan Broz wrote:
> Just FYI (for upstream code): if cryptsetup/libcryptsetup is linked with 
> OpenSSL >= 3.2,
> it does not need libphtread (as threads are implemented in OpenSSL for Argon2 
> internally).

Thanks for confirming!  We're now linking with OpenSSL 3.2 indeed, and
our CI confirms that unlocking works in that environment.

2:2.7.2-1 builds with OpenSSL 3.2 *and* removes the libgcc_s/libargon2
workaround from the initramfs hook:
https://tracker.debian.org/news/1517996/accepted-cryptsetup-2272-1-source-into-unstable/

>> It would also be nice if the "gui" view could show the error or at
>> least tell the user to pres ctrl-alt-del to get to a more informative
>> view, took me ages to figure out that one :-(

What is that “GUI” view?  src:cryptsetup doesn't provide that, I wonder
if it might be what needs libphtread.

Otherwise, my guess is a race where the the initramfs image was somehow
rebuilt before libcryptsetup12 was upgraded, but AFAICT the dependencies
are properly set to avoid that.  Does the broken initramfs image contain
libargon2.so, if so does its libcryptsetup12 use it?

If you still have the broken initramfs image, please extract it with
`unmkinitramfs /path/to/broken.initrd.img /path/to/destdir` and try to
find which executable / shared library needs libphtread, for instance
with

cd /path/to/destdir
for p in $(find -P {usr/,}lib/x86_64-linux-gnu  {usr/,}{,s}bin/ -type f); 
do objdump -p "$p" 2>/dev/null | grep -q pthread && echo "$p"; done

This will hopefully shed some light on this.

-- 
Guilhem.


signature.asc
Description: PGP signature

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

[Jan Katins]

On Fri, 12 Apr 2024 at 14:00, Chris Hofstaedtler  wrote:
> Can you tell us which part was wanting libgcc_s.so.1?
> cryptsetup in the initramfs doesn't seem to be the (original)
> problem of that.

How would I find out? (I've never debugged such a problem, and have
basically no clue what is happening behind the scenes during encrypted
hd unlock and how to figure out "what wants it" :-( )

I basically inputted a password (both on the "UI" and the console
after ctrl-alt-del) and on the console it showed me that error after
pressing enter. It then showed the passwort entry box/line again.
Given that it was the password validation, I figured I should file a
bug here.

Jan

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

[Chris Hofstaedtler]

On Fri, Apr 12, 2024 at 09:11:51AM +0200, Jan Katins wrote:
> Package: cryptsetup
> Version: 2:2.7.2-1
> Severity: normal
> 
> Dear Maintainer,
> 
> After a recent apt upgrade on a debian sid system (installed about 3
> years ago with an installer, choosing to encrypt the filesystem, no
> idea what actually ended up on my system as a crypt setup. Since then,
> the laptop runs debian unstable), my system failed to unlock. After a
> ctrl-alt-del, I got to the console and there it showed an error about
> libgcc_s.so.1 not available and aborting.

Can you tell us which part was wanting libgcc_s.so.1? 
cryptsetup in the initramfs doesn't seem to be the (original)
problem of that.

Chris

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

[Debian Bug Tracking System]

Processing control commands:

> severity 1062383 important
Bug #1062383 [src:dolfinx-mpc] dolfinx-mpc: NMU diff for 64-bit time_t 
transition
Severity set to 'important' from 'serious'
> tags 1062383 moreinfo
Bug #1062383 [src:dolfinx-mpc] dolfinx-mpc: NMU diff for 64-bit time_t 
transition
Added tag(s) moreinfo.

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

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

[Drew Parsons]

Source: dolfinx-mpc
Followup-For: Bug #1062383
Control: severity 1062383 important
Control: tags 1062383 moreinfo

This patch was never applied.  Do we not need it after all?  Can we
close this bug now?

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

[Debian Bug Tracking System]

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

This means that you claim 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.)


-- 
1067294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pomegranate
Version: 0.14.8-4
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

your package has an autopkgtest regression with NumPy 1.26.
Hopefully relevent excerpt from the test log:

 52s >   ???
 52s E   ValueError: The truth value of an array with more than one element is 
ambiguous. Use a.any() or a.all()
 52s
 52s pomegranate/kmeans.pyx:232: ValueError
 52s === warnings summary 
===
 52s ../../../../usr/lib/python3/dist-packages/dateutil/tz/tz.py:37
 52s   /usr/lib/python3/dist-packages/dateutil/tz/tz.py:37: DeprecationWarning: 
datetime.datetime.utcfromtimestamp() is deprecated and scheduled for removal in 
a future version. Use timezone-aware objects to represent datetimes in UTC: 
datetime.datetime.fromtimestamp(timestamp, datetime.UTC).
 52s EPOCH = datetime.datetime.utcfromtimestamp(0)
 52s
 52s tests/test_custom_distributions.py: 29600 warnings
 52s tests/test_hmm.py: 375 warnings
 52s   /usr/lib/python3/dist-packages/joblib/parallel.py:1792: 
DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s res = func(*args, **kwargs)
 52s
 52s tests/test_custom_distributions.py: 40 warnings
 52s   
/tmp/autopkgtest-lxc.qczb1z7m/downtmp/autopkgtest_tmp/tests/test_custom_distributions.py:223:
 DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s assert_array_almost_equal(model1.log_probability(X), 
model2.log_probability(X))
 52s
 52s tests/test_custom_distributions.py: 400 warnings
 52s   
/tmp/autopkgtest-lxc.qczb1z7m/downtmp/autopkgtest_tmp/tests/test_custom_distributions.py:232:
 DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s assert_array_almost_equal(model1.log_probability(X), 
model2.log_probability(X))
 52s
 52s tests/test_custom_distributions.py: 200 warnings
 52s   
/tmp/autopkgtest-lxc.qczb1z7m/downtmp/autopkgtest_tmp/tests/test_custom_distributions.py:345:
 DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s assert_array_almost_equal(model1.log_probability(X), 
model2.log_probability(X))
 52s
 52s tests/test_custom_distributions.py: 200 warnings
 52s   
/tmp/autopkgtest-lxc.qczb1z7m/downtmp/autopkgtest_tmp/tests/test_custom_distributions.py:359:
 DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s assert_array_almost_equal(model1.predict(X), model2.predict(X))
 52s
 52s tests/test_custom_distributions.py: 200 warnings
 52s   
/tmp/autopkgtest-lxc.qczb1z7m/downtmp/autopkgtest_tmp/tests/test_custom_distributions.py:373:
 DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s assert_array_almost_equal(model1.predict_proba(X), 
model2.predict_proba(X))
 52s
 52s tests/test_custom_distributions.py: 200 warnings
 52s   
/tmp/autopkgtest-lxc.qczb1z7m/downtmp/autopkgtest_tmp/tests/test_custom_distributions.py:387:
 DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s assert_array_almost_equal(model1.predict_log_proba(X), 
model2.predict

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

[Debian Bug Tracking System]

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

This means that you claim 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.)


-- 
1067233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pomegranate
Version: 0.14.8-4
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

your package has an autopkgtest regression with NumPy 1.26.
Hopefully relevent excerpt from the test log:

 52s >   ???
 52s E   ValueError: The truth value of an array with more than one element is 
ambiguous. Use a.any() or a.all()
 52s
 52s pomegranate/kmeans.pyx:232: ValueError
 52s === warnings summary 
===
 52s ../../../../usr/lib/python3/dist-packages/dateutil/tz/tz.py:37
 52s   /usr/lib/python3/dist-packages/dateutil/tz/tz.py:37: DeprecationWarning: 
datetime.datetime.utcfromtimestamp() is deprecated and scheduled for removal in 
a future version. Use timezone-aware objects to represent datetimes in UTC: 
datetime.datetime.fromtimestamp(timestamp, datetime.UTC).
 52s EPOCH = datetime.datetime.utcfromtimestamp(0)
 52s
 52s tests/test_custom_distributions.py: 29600 warnings
 52s tests/test_hmm.py: 375 warnings
 52s   /usr/lib/python3/dist-packages/joblib/parallel.py:1792: 
DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s res = func(*args, **kwargs)
 52s
 52s tests/test_custom_distributions.py: 40 warnings
 52s   
/tmp/autopkgtest-lxc.qczb1z7m/downtmp/autopkgtest_tmp/tests/test_custom_distributions.py:223:
 DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s assert_array_almost_equal(model1.log_probability(X), 
model2.log_probability(X))
 52s
 52s tests/test_custom_distributions.py: 400 warnings
 52s   
/tmp/autopkgtest-lxc.qczb1z7m/downtmp/autopkgtest_tmp/tests/test_custom_distributions.py:232:
 DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s assert_array_almost_equal(model1.log_probability(X), 
model2.log_probability(X))
 52s
 52s tests/test_custom_distributions.py: 200 warnings
 52s   
/tmp/autopkgtest-lxc.qczb1z7m/downtmp/autopkgtest_tmp/tests/test_custom_distributions.py:345:
 DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s assert_array_almost_equal(model1.log_probability(X), 
model2.log_probability(X))
 52s
 52s tests/test_custom_distributions.py: 200 warnings
 52s   
/tmp/autopkgtest-lxc.qczb1z7m/downtmp/autopkgtest_tmp/tests/test_custom_distributions.py:359:
 DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s assert_array_almost_equal(model1.predict(X), model2.predict(X))
 52s
 52s tests/test_custom_distributions.py: 200 warnings
 52s   
/tmp/autopkgtest-lxc.qczb1z7m/downtmp/autopkgtest_tmp/tests/test_custom_distributions.py:373:
 DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s assert_array_almost_equal(model1.predict_proba(X), 
model2.predict_proba(X))
 52s
 52s tests/test_custom_distributions.py: 200 warnings
 52s   
/tmp/autopkgtest-lxc.qczb1z7m/downtmp/autopkgtest_tmp/tests/test_custom_distributions.py:387:
 DeprecationWarning: Conversion of an array with ndim > 0 to a scalar is 
deprecated, and will error in future. Ensure you extract a single element from 
your array before performing this operation. (Deprecated NumPy 1.25.)
 52s assert_array_almost_equal(model1.predict_log_proba(X), 
model2.predict

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

[Debian Bug Tracking System]

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

This means that you claim that the problem has 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.)


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

Package: src:ruby-magic
Version: 0.2.9-3
Severity: serious
Tags: sid trixie

the package build-depends on libmagic1, and depends on it. The name was 
recently changed to libmagic1t64.  Please don't hard-code it, but try to 
b-d on libmagic-dev, and derive the name of the shared library package 
from the libmagic-dev package.
--- End Message ---
--- Begin Message ---
Source: ruby-magic
Source-Version: 0.2.9-4
Done: Antonio Terceiro 

We believe that the bug you reported is fixed in the latest version of
ruby-magic, 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.
Antonio Terceiro  (supplier of updated ruby-magic 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: Fri, 12 Apr 2024 07:45:21 -0300
Source: ruby-magic
Architecture: source
Version: 0.2.9-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Antonio Terceiro 
Closes: 1066854
Changes:
 ruby-magic (0.2.9-4) unstable; urgency=medium
 .
   * Team upload
   * Use libmagic-dev in Build-Depends/Depends instead of libmagic1
 (Closes: #1066854)
   * Drop deprecated *-Ruby-Versions fields
Checksums-Sha1:
 89817b3c30d8ed7ca0cd59aa5279d5d150c587c3 2027 ruby-magic_0.2.9-4.dsc
 79d9fe83e1532f2f65c6841660a2cfddeb3c794c 4016 ruby-magic_0.2.9-4.debian.tar.xz
 cf7bdf863190363bf2ab4f14d508842d381a278b 13530 
ruby-magic_0.2.9-4_source.buildinfo
Checksums-Sha256:
 aa52e3c98e78a05380b6f510a96c19381816427acefee39e7a4b881143e0d201 2027 
ruby-magic_0.2.9-4.dsc
 8e7b329aded49cc16e0260ab6bc27d999d5cff76f16975be6535738e33035644 4016 
ruby-magic_0.2.9-4.debian.tar.xz
 c05d578ca648c238178c8a0fc4dfb26f500ec86b4e7d18d61fba800d1330c070 13530 
ruby-magic_0.2.9-4_source.buildinfo
Files:
 6cd88db90a765990738aade894c469cc 2027 ruby optional ruby-magic_0.2.9-4.dsc
 f42b6c0a1767fe14ae8d748ff1169df8 4016 ruby optional 
ruby-magic_0.2.9-4.debian.tar.xz
 6e842246a5115ec961cd029d5e073cc1 13530 ruby optional 
ruby-magic_0.2.9-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmYZFDIACgkQ/A2xu81G
C97yow/9GQwKRyZ3xjDpggfkx77wYttE+Hfu6K4oknRA5FjmlrE1+YaXF+ktWOEl
mdcV0lYLh5PrnuZ7YKGlVnKK5qEst7y1KuvbOLi59SLdyHuZVRpqZoaXI/Mh1EdE
3fEXQTAIptLfJGdKCG55uixBK9j8oMhWNrK1Qjtm18vyHA2dyh9hjiEuO7q5qH3O
fRMq/k6nUN6xUJN8E0GGbnXXSyHC/38ABjLVExH+KDOX+Z65u5ugIX3HBZW8uDBP
qkBzGbi9zK4kVvp6sOzCa/6xaZBDAVnb0dDUzTDA3vqXnQASkmYL8a4mmmFJhHz/
4gWo+/qlbIMJs6J0RnW2Ds/HlhUrIjEW+7FugY02DaWRBLPtRgdf2oxraWZLkgNq
HVEfUVYRpMqBxc0W/zU2CRgVobxrXw/KX55H1d1Lzpu7PXsE2Pm7O/uSlrkZeQ63
rWAiVYObk1NmXeOqC0Iye95AkYn3tkFDpUPjgW2bjwVRQVlBZW/4eOI+6o1HqesX
pt2z6cm+FgWtQxxmKpJxhbr8lWtLowQxlfJEArA7yU5hS7f83k2B/R//gAp9Swl6
MuCu3uSbJ2PRjSpRsfuwy8bREhb8YbNFl/pS46lkPZP2rELa0yo0MCJb8bqpRC7X
6digsijPo0esK5zZApWaAonsoVTP7Y3mPI2ABOvSN8tdeCHEc7I=
=POuB
-END PGP SIGNATURE-



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

Bug#1067294: marked as pending in python-pomegranate

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-pomegranate/-/commit/a9381a9a177cf18e72d60a67232f592744d3ac87


Add patch from Graham Inggs to fix compat with NumPy 1.26+, thank you Graham! 
Closes: #1067233, #1067294


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067294

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067294 [src:python-pomegranate] python-pomegranate: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned 
exit code 13
Bug #1067233 [src:python-pomegranate] python-pomegranate: autopkgtest 
regression with NumPy 1.26
Ignoring request to alter tags of bug #1067294 to the same tags previously set
Ignoring request to alter tags of bug #1067233 to the same tags previously set

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

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067233 [src:python-pomegranate] python-pomegranate: autopkgtest 
regression with NumPy 1.26
Bug #1067294 [src:python-pomegranate] python-pomegranate: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned 
exit code 13
Added tag(s) pending.
Added tag(s) pending.

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

Bug#1067233: marked as pending in python-pomegranate

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-pomegranate/-/commit/a9381a9a177cf18e72d60a67232f592744d3ac87


Add patch from Graham Inggs to fix compat with NumPy 1.26+, thank you Graham! 
Closes: #1067233, #1067294


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067233

Bug#1066854: marked as pending in ruby-magic

[Antonio Terceiro]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-magic/-/commit/3a95d42fa6ea9355487927f2c663a73bbad603ea


Use libmagic-dev in Build-Depends/Depends instead of libmagic1

Closes: #1066854


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066854

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066854 [src:ruby-magic] don't hard-code the name of the shared library
Added tag(s) pending.

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

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

[Debian Bug Tracking System]

Processing control commands:

> severity 1062587 important
Bug #1062587 [src:fenics-dolfinx] fenics-dolfinx: NMU diff for 64-bit time_t 
transition
Severity set to 'important' from 'serious'
> tags 1062587 moreinfo
Bug #1062587 [src:fenics-dolfinx] fenics-dolfinx: NMU diff for 64-bit time_t 
transition
Added tag(s) moreinfo.

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

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

[Drew Parsons]

Source: fenics-dolfinx
Followup-For: Bug #1062587
Control: severity 1062587 important
Control: tags 1062587 moreinfo

This time_t patch was never applied.  I presume it's not needed after
all and we can close this bug now?

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

[Milan Broz]

On 4/12/24 9:11 AM, Jan Katins wrote:

I snooped around in the source code a bit and found that libgcc_s
seems to be dlopened and is special cased:
https://salsa.debian.org/kernel-team/initramfs-tools/-/blob/master/hook-functions?ref_type=heads#L248-249
(original bugreport:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254). So my guess
is that nothing depends on libpthread anymore,


Just FYI (for upstream code): if cryptsetup/libcryptsetup is linked with OpenSSL 
>= 3.2,
it does not need libphtread (as threads are implemented in OpenSSL for Argon2 
internally).
Ditto for libargon2 and possible dependences of above (libgcc_s).

So if the reason is cryptsetup, all these dependences should be removed, we do 
not need it anymore.

Milan

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066223 [src:ftpcopy] ftpcopy: FTBFS: conftest1663576.c:7:9: error: 
implicit declaration of function ‘_exit’ [-Werror=implicit-function-declaration]
Added tag(s) pending.

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

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

[Andreas Beckmann]

Followup-For: Bug #1066223
X-Debbugs-Cc: Bastian Germann 
Control: tag -1 pending

Hi Bastian,

I've fixed the remaining implicit function declarations and related bugs
in GIT. Do you want to take it from here again?
We should probably fix the nonverbose build in this very special build
system, too.


Andreas

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1064531 [src:amberol] src:amberol: unsatisfied build dependency in 
testing: librust-lofty-0.17-dev
Added tag(s) patch.

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

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

[Emanuele Rocca]

Control: tags -1 + patch

Hi,

On 2024-02-23 08:33, Paul Gevers wrote:
> Dose [1] is reporting a build issue with your package, it's missing a
> build dependency.

It's actually two build deps that are missing: librust-lofty-0.17-dev
and librust-mpris-server-0.6-dev. Setting both to the versions currently
available in sid fixes the FTBFS. See attached patch.

  Emanuele
diff -Nru amberol-0.10.3/debian/changelog amberol-0.10.3/debian/changelog
--- amberol-0.10.3/debian/changelog	2024-01-06 12:12:15.0 +0100
+++ amberol-0.10.3/debian/changelog	2024-04-12 12:23:35.0 +0200
@@ -1,3 +1,11 @@
+amberol (0.10.3-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update build dependencies: librust-lofty-0.18-dev,
+librust-mpris-server-0.7-dev. (Closes: #1064531) 
+
+ -- Emanuele Rocca   Fri, 12 Apr 2024 12:23:35 +0200
+
 amberol (0.10.3-2) unstable; urgency=medium
 
   * d/control: depend on `gstreamer1.0-plugins-good`
diff -Nru amberol-0.10.3/debian/control amberol-0.10.3/debian/control
--- amberol-0.10.3/debian/control	2024-01-06 12:12:15.0 +0100
+++ amberol-0.10.3/debian/control	2024-04-12 12:23:35.0 +0200
@@ -21,9 +21,9 @@
  librust-gdk-pixbuf-0.18+v2-42-dev,
  librust-gtk4-0.7+v4-10-dev,
  librust-libadwaita-0.5+v1-4-dev,
- librust-lofty-0.17-dev,
+ librust-lofty-0.18-dev,
  librust-log-0.4-dev,
- librust-mpris-server-0.6-dev,
+ librust-mpris-server-0.7-dev,
  librust-pretty-env-logger-0.5-dev,
  librust-once-cell-1-dev,
  librust-rand-0.8-dev,
diff -Nru amberol-0.10.3/debian/patches/0002-Update-dependencies.patch amberol-0.10.3/debian/patches/0002-Update-dependencies.patch
--- amberol-0.10.3/debian/patches/0002-Update-dependencies.patch	2024-01-06 12:12:15.0 +0100
+++ amberol-0.10.3/debian/patches/0002-Update-dependencies.patch	2024-04-12 12:23:03.0 +0200
@@ -36,7 +36,7 @@
 -gtk = { version = "0.6.6", package = "gtk4", features = ["v4_10"] }
 -lofty = "0.11.0"
 +gtk = { version = "0.7", package = "gtk4", features = ["v4_10"] }
-+lofty = "0.17.0"
++lofty = "0.18.0"
  log = "0.4"
  mpris-player = "0.6"
  once_cell = "1.10"
diff -Nru amberol-0.10.3/debian/patches/0003-Replace-mpris_player-with-mpris_server-and-fix-MPRIS.patch amberol-0.10.3/debian/patches/0003-Replace-mpris_player-with-mpris_server-and-fix-MPRIS.patch
--- amberol-0.10.3/debian/patches/0003-Replace-mpris_player-with-mpris_server-and-fix-MPRIS.patch	2024-01-06 12:12:15.0 +0100
+++ amberol-0.10.3/debian/patches/0003-Replace-mpris_player-with-mpris_server-and-fix-MPRIS.patch	2024-04-12 12:23:35.0 +0200
@@ -17,23 +17,23 @@
  src/audio/waveform_generator.rs |   2 +-
  7 files changed, 199 insertions(+), 144 deletions(-)
 
-diff --git a/Cargo.toml b/Cargo.toml
-index e15d84b..4eadcfb 100644
 a/Cargo.toml
-+++ b/Cargo.toml
-@@ -14,7 +14,7 @@ gettext-rs = { version = "0.7", features = ["gettext-system"] }
+Index: amberol-0.10.3/Cargo.toml
+===
+--- amberol-0.10.3.orig/Cargo.toml
 amberol-0.10.3/Cargo.toml
+@@ -14,7 +14,7 @@ gettext-rs = { version = "0.7", features
  gtk = { version = "0.7", package = "gtk4", features = ["v4_10"] }
- lofty = "0.17.0"
+ lofty = "0.18.0"
  log = "0.4"
 -mpris-player = "0.6"
-+mpris-server = "0.6"
++mpris-server = "0.7"
  once_cell = "1.10"
  pretty_env_logger = "0.5"
  rand = "0.8.5"
-diff --git a/src/audio/controller.rs b/src/audio/controller.rs
-index 62f89e7..e1484ae 100644
 a/src/audio/controller.rs
-+++ b/src/audio/controller.rs
+Index: amberol-0.10.3/src/audio/controller.rs
+===
+--- amberol-0.10.3.orig/src/audio/controller.rs
 amberol-0.10.3/src/audio/controller.rs
 @@ -7,6 +7,6 @@ pub trait Controller {
  fn set_playback_state(&self, state: &PlaybackState);
  
@@ -42,10 +42,10 @@
 +fn set_position(&self, position: u64, notify: bool);
  fn set_repeat_mode(&self, repeat: RepeatMode);
  }
-diff --git a/src/audio/gst_backend.rs b/src/audio/gst_backend.rs
-index feb27c1..ff8c1c5 100644
 a/src/audio/gst_backend.rs
-+++ b/src/audio/gst_backend.rs
+Index: amberol-0.10.3/src/audio/gst_backend.rs
+===
+--- amberol-0.10.3.orig/src/audio/gst_backend.rs
 amberol-0.10.3/src/audio/gst_backend.rs
 @@ -21,6 +21,13 @@ pub struct GstReplayGain {
  rg_volume: gst::Element,
  }
@@ -82,10 +82,10 @@
  self.gst_player.connect_volume_changed(
  clone!(@strong self.sender as sender => move |player| {
  let volume = gst_audio::StreamVolume::convert_volume(
-diff --git a/src/audio/inhibit_controller.rs b/src/audio/inhibit_controller.rs
-index e532c74..01e36a0 100644
 a/src/audio/inhibit_controller.rs
-+++ b/src/audio/inhibit_controller.rs
+Index: amberol-0.10.3/src/audio/inhibit_controller.rs
+===
+--- amberol-0.10.3.orig/src/audio/in

Bug#1066275:

[Miriam Espana Acebal]

Hi,

In ubuntu we applied the upstream's fix at
https://github.com/rlancaste/stellarsolver/pull/139. I adapted it to a
patch that I attach here for fixing this FTBFS.

I am sending this for your consideration, and I hope it helps.

Best,

Miriam

-- 
[image: Canonical-20th-anniversary]

Miriam España Acebal

Software Engineer II - Ubuntu Public Cloud/Server

Email:

miriam.esp...@canonical.com

Location:

Spain  (GMT+2)

canonical.com

ubuntu.com
Description: Fix qsort warning implicit function declarations
 The qsort_r function comes with different prototypes on different
 systems. There are some tests around NEED_DECLARE_QSORT_R and
 NEED_SWAP_QSORT_R that try to work around that. However, they only
 work with compilers which accept implicit function declarations.

 The qsort_r fix is backported from astrometry.
Author: timsurber 
Origin: upstream, https://github.com/rlancaste/stellarsolver/pull/139
Bug: https://github.com/rlancaste/stellarsolver/issues/108
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066275
Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/stellarsolver/+bug/2060959
Forwarded: not-needed
Last-Update: 2024-04-11 
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/stellarsolver/astrometry/include/astrometry/ioutils.h
+++ b/stellarsolver/astrometry/include/astrometry/ioutils.h
@@ -31,6 +31,15 @@
 
 extern uint32_t ENDIAN_DETECTOR;
 
+void QSORT_R(void* base, size_t nmembers, size_t member_size,
+ void* token, int (*compar)(void *, const void *, const void *));
+
+/**
+   You should define the "comparison" function like this:
+   static int QSORT_COMPARISON_FUNCTION(my_comparison, void* token, const void* v1, const void* v2) {
+ */
+#define QSORT_COMPARISON_FUNCTION(func, thunk, v1, v2) func(thunk, v1, v2)
+
 int copy_file(const char* infn, const char* outfn);
 
 int pad_fid(FILE* fid, size_t len, char pad);
--- a/stellarsolver/astrometry/include/astrometry/os-features-config.h
+++ b/stellarsolver/astrometry/include/astrometry/os-features-config.h
@@ -1,4 +1,4 @@
-#define NEED_DECLARE_QSORT_R 0
-#define NEED_QSORT_R 1
+#define NEED_DECLARE_QSORT_R 1
+#define NEED_QSORT_R 0
 #define NEED_SWAP_QSORT_R 0
 #define HAVE_NETPBM 0
\ No newline at end of file
--- a/stellarsolver/astrometry/include/astrometry/permutedsort.h
+++ b/stellarsolver/astrometry/include/astrometry/permutedsort.h
@@ -7,7 +7,7 @@
 #define PERMUTED_SORT_H
 
 // for QSORT_COMPARISON_FUNCTION
-#include "os-features.h"
+#include "ioutils.h"
 
 /*
  Computes the permutation array that will cause the "realarray" to be
--- a/stellarsolver/astrometry/os-features.h
+++ b/stellarsolver/astrometry/os-features.h
@@ -108,22 +108,6 @@
-Ubuntu 8.10
 */
 
-#if NEED_DECLARE_QSORT_R
- NOTE: this declaration must match os-features-test.c .
-void qsort_r(void *base, size_t nmemb, size_t sz,
- void *userdata,
- int (*compar)(void *, const void *, const void *));
-#endif
-
-#if NEED_SWAP_QSORT_R
-#define QSORT_R(a,b,c,d,e) qsort_r(a,b,c,e,d)
-#define QSORT_COMPARISON_FUNCTION(func, thunk, v1, v2) func(v1, v2, thunk)
-
-#else
-#define QSORT_R qsort_r
-#define QSORT_COMPARISON_FUNCTION(func, thunk, v1, v2) func(thunk, v1, v2)
-
-#endif
 
 // As suggested in http://gcc.gnu.org/onlinedocs/gcc-4.3.0/gcc/Function-Names.html
 #if __STDC_VERSION__ < 199901L
--- a/stellarsolver/astrometry/util/bl-sort.c
+++ b/stellarsolver/astrometry/util/bl-sort.c
@@ -3,6 +3,8 @@
  # Licensed under a 3-clause BSD style license - see LICENSE
  */
 
+#include "ioutils.h" // for QSORT_R
+
 #include "bl-sort.h"
 // for qsort_r
 #include "os-features.h"
@@ -166,4 +168,3 @@
 void  pl_sort(pl* list, int (*compare)(const void* v1, const void* v2)) {
 bl_sort_with_userdata(list, sort_helper_pl, compare);
 }
-
--- a/stellarsolver/astrometry/util/fitstable.c
+++ b/stellarsolver/astrometry/util/fitstable.c
@@ -1227,7 +1227,11 @@
 else {
 tab->fid = fopen(fn, mode);
 if (!tab->fid) {
-SYSERROR("Couldn't open output file %s for writing", fn);
+if (fn != NULL) {
+SYSERROR("Couldn't open output file %s for writing", fn);
+} else {
+SYSERROR("Couldn't open output file because the filename is null");
+}
 goto bailout;
 }
 }
--- a/stellarsolver/astrometry/util/ioutils.c
+++ b/stellarsolver/astrometry/util/ioutils.c
@@ -43,7 +43,7 @@
 
 #include "os-features.h"
 #include "ioutils.h"
-//#include "os-features.h"
+#include "qsort_reentrant.c"
 #include "errors.h"
 #include "log.h"
 
--- a/stellarsolver/astrometry/util/os-features-test.c
+++ b/stellarsolver/astrometry/util/os-features-test.c
@@ -14,63 +14,6 @@
 }
 #endif
 
-#ifdef TEST_QSORT_R
-static int cmp(void* u, const void* a, const void* b) {
-return 0;
-}
-int main() {
-int array;
-int baton;
-qsort_r(&array, 1, sizeof(int), &baton, cmp);
-//printf("#define NEED_QSORT_R 0\n

Bug#1066213:

[Miriam Espana Acebal]

Hi,

In ubuntu we applied the upstream's fix at
https://github.com/jedsoft/slrn/pull/1 (with some refreshing action)  that
I'll attach here for fixing this FTBFS.

I am sending this for your consideration, and I hope that it helps.

Best,

Miriam

-- 
[image: Canonical-20th-anniversary]

Miriam España Acebal

Software Engineer II - Ubuntu Public Cloud/Server

Email:

miriam.esp...@canonical.com

Location:

Spain

canonical.com

ubuntu.com
Origin: upstream, https://github.com/jedsoft/slrn/pull/1/commits/f550d0ab9e1cd3cfe844022435c3d98af3c18441
From: Florian Weimer 
Date: Sat, 4 Feb 2023 15:04:36 +0100
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/slrn/+bug/2061030
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066213
Subject: [PATCH] autoconf: Fix C99 compatibility issue in the VA_COPY checks

The exit function is called without including , resulting
in an implicit function declarations.  Future compilers will not
support implicit function declarations by default.  This will lead
to build failures.
---
 autoconf/configure.ac | 3 +++
 configure | 3 +++
 2 files changed, 6 insertions(+)

--- a/autoconf/configure.ac
+++ b/autoconf/configure.ac
@@ -399,6 +399,7 @@
 AC_CACHE_VAL(slrn_cv_va_copy,[
 	AC_RUN_IFELSE([AC_LANG_SOURCE([[
 	#include 
+	#include 
 	void f (int i, ...) {
 	va_list args1, args2;
 	va_start (args1, i);
@@ -419,6 +420,7 @@
 AC_CACHE_VAL(slrn_cv___va_copy,[
 	AC_RUN_IFELSE([AC_LANG_SOURCE([[
 	#include 
+	#include 
 	void f (int i, ...) {
 	va_list args1, args2;
 	va_start (args1, i);
@@ -439,6 +441,7 @@
 AC_CACHE_VAL(slrn_cv_va_val_copy,[
 	AC_RUN_IFELSE([AC_LANG_SOURCE([[
 	#include 
+	#include 
 	void f (int i, ...) {
 	va_list args1, args2;
 	va_start (args1, i);
--- a/configure
+++ b/configure
@@ -8307,6 +8308,7 @@ else
 /* end confdefs.h.  */
 
 	#include 
+	#include 
 	void f (int i, ...) {
 	va_list args1, args2;
 	va_start (args1, i);
@@ -8353,6 +8354,7 @@ else
 /* end confdefs.h.  */
 
 	#include 
+	#include 
 	void f (int i, ...) {
 	va_list args1, args2;
 	va_start (args1, i);
@@ -8399,6 +8400,7 @@
 /* end confdefs.h.  */
 
 	#include 
+	#include 
 	void f (int i, ...) {
 	va_list args1, args2;
 	va_start (args1, i);

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

[Debian Bug Tracking System]

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


-- 
1068115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tardy
Version: 1.25-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=tardy&arch=armel&ver=1.25-2%2Bb2&stamp=1711746975&raw=0

g++ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -I. -c libtardy/version.cc
mv version.o libtardy/version.o
rm -f libtardy/libtardy.a
ar qc libtardy/libtardy.a libtardy/ac/stdio.o libtardy/ac/string.o 
libtardy/ac/zlib.o libtardy/arglex.o libtardy/cannonical.o libtardy/endian.o 
libtardy/file/input.o libtardy/file/input/factory.o 
libtardy/file/input/gunzip.o libtardy/file/input/normal.o 
libtardy/file/input/position.o libtardy/file/input/stdin.o 
libtardy/file/output.o libtardy/file/output/buffer.o 
libtardy/file/output/factory.o libtardy/file/output/gzip.o 
libtardy/file/output/hexdump.o libtardy/file/output/normal.o 
libtardy/file/output/stdout.o libtardy/filenamelist.o 
libtardy/filenamelist/file.o libtardy/filenamelist/filter.o 
libtardy/filenamelist/filter/progress.o libtardy/format_family.o 
libtardy/fstrcmp.o libtardy/gmatch.o libtardy/mprintf.o libtardy/rcstring.o 
libtardy/rcstring/accumulator.o libtardy/rcstring/accumulator/pop_front.o 
libtardy/rcstring/accumulator/printf.o libtardy/rcstring/basename.o 
libtardy/rcstring/clear.o libtardy/rcstring/dirname.o 
libtardy/rcstring/downcase.o libtardy/rcstring/ends_with.o 
libtardy/rcstring/eq.o libtardy/rcstring/hexdump.o 
libtardy/rcstring/list/appelistuniq.o libtardy/rcstring/list/append.o 
libtardy/rcstring/list/append_list.o libtardy/rcstring/list/append_uniqu.o 
libtardy/rcstring/list/assign_op.o libtardy/rcstring/list/clear.o 
libtardy/rcstring/list/constructor.o libtardy/rcstring/list/copy.o 
libtardy/rcstring/list/destructor.o libtardy/rcstring/list/equal.o 
libtardy/rcstring/list/intersection.o libtardy/rcstring/list/member.o 
libtardy/rcstring/list/member_nocas.o libtardy/rcstring/list/pop_back.o 
libtardy/rcstring/list/pop_front.o libtardy/rcstring/list/prepend.o 
libtardy/rcstring/list/prepend_list.o libtardy/rcstring/list/quote.o 
libtardy/rcstring/list/remove.o libtardy/rcstring/list/remove_list.o 
libtardy/rcstring/list/sort.o libtardy/rcstring/list/sort_long_short.o 
libtardy/rcstring/list/sort_nocase.o libtardy/rcstring/list/sort_vers.o 
libtardy/rcstring/list/str2wl.o libtardy/rcstring/list/subset.o 
libtardy/rcstring/list/validate.o libtardy/rcstring/list/wl2str.o 
libtardy/rcstring/list/xor.o libtardy/rcstring/printf.o 
libtardy/rcstring/quote_c.o libtardy/rcstring/substitute.o 
libtardy/rcstring/substring.o libtardy/rcstring/upcase.o 
libtardy/read_whole_directory.o libtardy/roff.o libtardy/symtab.o 
libtardy/tar/format.o libtardy/tar/header.o libtardy/tar/input.o 
libtardy/tar/input/ar.o libtardy/tar/input/ar/bsd.o 
libtardy/tar/input/ar/factory.o libtardy/tar/input/ar/pdp11.o 
libtardy/tar/input/ar/v7.o libtardy/tar/input/cpio.o 
libtardy/tar/input/cpio/binary.o libtardy/tar/input/cpio/crc.o 
libtardy/tar/input/cpio/factory.o libtardy/tar/input/cpio/new_ascii.o 
libtardy/tar/input/cpio/old_ascii.o libtardy/tar/input/directory.o 
libtardy/tar/input/factory.o libtardy/tar/input/filename.o 
libtardy/tar/input/filenamelist.o libtardy/tar/input/filter.o 
libtardy/tar/input/filter/ar_long_names.o 
libtardy/tar/input/filter/ar_long_names2.o libtardy/tar/input/filter/clean.o 
libtardy/tar/input/filter/exclude.o libtardy/tar/input/filter/group_name.o 
libtardy/tar/input/filter/group_numbr.o libtardy/tar/input/filter/gunzip.o 
libtardy/tar/input/filter/mode_clear.o libtardy/tar/input/filter/mode_set.o 
libtardy/tar/input/filter/mtime.o libtardy/tar/input/filter/prefix.o 
libtardy/tar/input/filter/relative_paths.o 
libtardy/tar/input/filter/remov_prefi.o 
libtardy/tar/input/filter/remove_prefix_count.o 
libtardy/tar/input/filter/suppr_direc.o libtardy/tar/input/filter/user_name.o 
libtardy/tar/input/filter/user_number.o libtardy/tar/input/ta

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

[Debian Bug Tracking System]

Your message dated Fri, 12 Apr 2024 09:51:31 +
with message-id 
and subject line Bug#1066651: fixed in spectools 201601r1-4
has caused the Debian Bug report #1066651,
regarding spectools: FTBFS: wispy_hw_gen1.c:296:15: error: implicit declaration 
of function ‘wispy24x_adler_checksum’; did you mean ‘wispy1_adler_checksum’? 
[-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.)


-- 
1066651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spectools
Version: 201601r1-3
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 -Wdate-time -D_FORTIFY_SOURCE=2 -D_DEBUG -I./ -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c spectool_net_server.c -o 
> spectool_net_server.o
> wispy_hw_dbx.c: In function ‘wispydbx_usb_setposition’:
> wispy_hw_dbx.c:1289:27: warning: assignment to ‘uint8_t *’ {aka ‘unsigned 
> char *’} from incompatible pointer type ‘wispydbx_rfsettings_v2 *’ {aka 
> ‘struct _wispydbx_rfsettings_v2 *’} [-Wincompatible-pointer-types]
>  1289 | use_rfset = &rfset2;
>   |   ^
> wispy_hw_dbx.c:1312:27: warning: assignment to ‘uint8_t *’ {aka ‘unsigned 
> char *’} from incompatible pointer type ‘wispydbx_rfsettings *’ {aka ‘struct 
> _wispydbx_rfsettings *’} [-Wincompatible-pointer-types]
>  1312 | use_rfset = &rfset;
>   |   ^
> spectool_net_client.c: In function ‘spectool_netcli_block_sweep’:
> spectool_net_client.c:367:62: warning: format ‘%u’ expects argument of type 
> ‘unsigned int’, but argument 6 has type ‘long unsigned int’ [-Wformat=]
>   367 | snprintf(errstr, SPECTOOL_ERROR_MAX, "Got 
> sweep frame too small to hold "
>   |  
> ^~~~
> spectool_net_client.c:368:99: note: format string is defined here
>   368 |  "indicated number of 
> samples, bailing - %u samples %u < %u",
>   |   
>~^
>   |   
> |
>   |   
> unsigned int
>   |   
>%lu
> wispy_hw_gen1.c: In function ‘wispy1_usb_init_path’:
> wispy_hw_gen1.c:296:15: error: implicit declaration of function 
> ‘wispy24x_adler_checksum’; did you mean ‘wispy1_adler_checksum’? 
> [-Werror=implicit-function-declaration]
>   296 | cid = wispy24x_adler_checksum(combopath, 128);
>   |   ^~~
>   |   wispy1_adler_checksum
> ubertooth_hw_u1.c: In function ‘ubertooth_u1_device_scan’:
> ubertooth_hw_u1.c:266:41: error: implicit declaration of function 
> ‘wispy24x_adler_checksum’ [-Werror=implicit-function-declaration]
>   266 | 
> wispy24x_adler_checksum(combopath, 128);
>   | ^~~
> spectool_net_client.c:426:17: warning: ignoring return value of ‘write’ 
> declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   426 | write(((spectool_net_dev_aux *) 
> (sni->phydev->auxptr))->spipe[1], "0", 1);
>   | 
> ^
> wispy_hw_gen1.c: In function ‘wispy1_usb_open’:
> wispy_hw_gen1.c:557:21: error: implicit declaration of function 
> ‘wispy24x_usb_detach_hack’; did you mean ‘wispy_usb_detach_hack’? 
> [-Werror=implicit-function-declaration]
>   557 | if (wispy24x_usb_detach_hack(auxptr->devhdl, 0, 
> phydev->errstr) < 0) {
>   | ^~

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

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/PythonOT/POT/issues/618
Bug #1068647 [src:python-pot] python-pot: autopkgtest regression on i386 with 
NumPy 1.26.4
Set Bug forwarded-to-address to 'https://github.com/PythonOT/POT/issues/618'.

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

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

[Gard Spreemann]

Control: forwarded -1 https://github.com/PythonOT/POT/issues/618

Thanks for the bug report.

This seems like a simple case of a missing floating point tolerance in
upstream's test. It's easy to patch, but I've sent a reproducible
example upstream [1] as they're likely to have better insight into the
appropriate floating point tolerance level for the test.

[1] https://github.com/PythonOT/POT/issues/618


 Best,
 Gard

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

[Debian Bug Tracking System]

Your message dated Fri, 12 Apr 2024 08:35:08 +
with message-id 
and subject line Bug#1065980: fixed in gfarm 2.7.20+dfsg-1.2
has caused the Debian Bug report #1065980,
regarding gfarm: FTBFS on arm{el,hf}:
to be marked as done.

This means that you claim that the problem has been dealt with.
If 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.)


-- 
1065980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gfarm
Version: 2.7.20+dfsg-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=gfarm&arch=armhf&ver=2.7.20%2Bdfsg-1.1&stamp=1709147793&raw=0

/bin/bash ../../../libtool --mode=compile cc -D_REENTRANT -pthread -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-I../../../include -I../../../include -DCOMPAT_GFARM_2_3 
-I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I.   
-I/usr/include/postgresql-DGFARM_CONFIG='"/etc/gfarm2.conf"' 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -c ./gfp_xdr_server.c
./gfp_xdr.c: In function ‘gfp_xdr_vsend’:
./gfp_xdr.c:484:25: error: implicit declaration of function ‘swab’ 
[-Werror=implicit-function-declaration]
  484 | swab(&d, &nd, sizeof(nd));
  | ^~~~
libtool: compile:  cc -D_REENTRANT -pthread -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-I../../../include -I../../../include -DCOMPAT_GFARM_2_3 
-I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I. 
-I/usr/include/postgresql -DGFARM_CONFIG=\"/etc/gfarm2.conf\" 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -c ./gfp_xdr_server.c  -fPIC -DPIC -o .libs/gfp_xdr_server.o
/bin/bash ../../../libtool --mode=compile cc -D_REENTRANT -pthread -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-I../../../include -I../../../include -DCOMPAT_GFARM_2_3 
-I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I.   
-I/usr/include/postgresql-DGFARM_CONFIG='"/etc/gfarm2.conf"' 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -c ./gfs_proto.c
/bin/bash ../../../libtool --mode=compile cc -D_REENTRANT -pthread -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-I../../../include -I../../../include -DCOMPAT_GFARM_2_3 
-I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I.   
-I/usr/include/postgresql-DGFARM_CONFIG='"/etc/gfarm2.conf"' 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -c ./io_fd.c
libtool: compile:  cc -D_REENTRANT -pthread -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-I../../../include -I../../../include -DCOMPAT_GFARM_2_3 
-I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I. 
-I/usr/include/postgresql -DGFARM_CONFIG=\"/etc/gfarm2.conf\" 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -c ./gfs_proto.c  -fPIC -DPIC -o .libs/gfs_proto.o
libtool: compile:  cc -D_REENTRANT -pthread -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-I../../../include -I../../../include -DCOMPAT_GFARM_2_3 
-I../../../lib/libgfarm/gfutil -I../../../lib/libgfarm/gfarm -I. 
-I/usr/include/postgresql -DGFARM_CONFIG=\"/etc/gfarm2.conf\" 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2 -c ./io_fd.c  -fPIC -DPIC -o .libs/io_fd.o
/bin/bash ../../../libtool --mode=compile cc -D_REENTRANT -pthread -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 

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

[Debian Bug Tracking System]

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

> merge 1068849 1068848
Bug #1068849 [cryptsetup] cryptsetup: Fails to unlock the filesystem with 
missing libgcc_s.so.1
Bug #1068848 [cryptsetup] cryptsetup: Fails to unlock the filesystem with 
missing libgcc_s.so.1
Merged 1068848 1068849
> reassign 1068848 cryptsetup-initramfs 2:2.7.2-1
Bug #1068848 [cryptsetup] cryptsetup: Fails to unlock the filesystem with 
missing libgcc_s.so.1
Bug #1068849 [cryptsetup] cryptsetup: Fails to unlock the filesystem with 
missing libgcc_s.so.1
Bug reassigned from package 'cryptsetup' to 'cryptsetup-initramfs'.
Bug reassigned from package 'cryptsetup' to 'cryptsetup-initramfs'.
No longer marked as found in versions cryptsetup/2:2.7.2-1.
No longer marked as found in versions cryptsetup/2:2.7.2-1.
Ignoring request to alter fixed versions of bug #1068848 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1068849 to the same values 
previously set
Bug #1068848 [cryptsetup-initramfs] cryptsetup: Fails to unlock the filesystem 
with missing libgcc_s.so.1
Bug #1068849 [cryptsetup-initramfs] cryptsetup: Fails to unlock the filesystem 
with missing libgcc_s.so.1
Marked as found in versions cryptsetup/2:2.7.2-1.
Marked as found in versions cryptsetup/2:2.7.2-1.
> severity 1068848 serious
Bug #1068848 [cryptsetup-initramfs] cryptsetup: Fails to unlock the filesystem 
with missing libgcc_s.so.1
Bug #1068849 [cryptsetup-initramfs] cryptsetup: Fails to unlock the filesystem 
with missing libgcc_s.so.1
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #1067957 [src:maude] FTBFS: error: call of overloaded 
‘__gmp_expr(__time64_t&)’ is ambiguous
Severity set to 'wishlist' from 'serious'

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

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

[Nilesh Patra]

Control: severity -1 wishlist

Hi,

maude has been -rm'ed on 32-bit archs as per 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068766
So this issue is now moot and I am downgrading the severity.

On Thu, Apr 11, 2024 at 07:53:08AM +0200, Andreas Tille wrote:
> Hi,
> 
> Am Wed, Apr 10, 2024 at 03:33:53PM -0700 schrieb Steven Eker:
> > I like that solution since I believe there are 64-bit platforms where long
> > is 32-bits. I've updated my development version thus:
> > 
> >   //
> >   //    timeValue.tv_sec is 64-bit since Linux kernel 5.6 but GMP doesn't
> > yet have support
> >   //    for long long which is a problem on platforms where long is less
> > than 8 bytes.
> >   //
> > #if SIZEOF_LONG < 8
> >   double seconds = timeValue.tv_sec;
> > #else
> >   long seconds = timeValue.tv_sec;
> > #endif
> >   mpz_class nanoSeconds(seconds);
> 
> Sounds like some working solution.  It would help if you could tag a new
> released to enable us fetching a fresh tarball incorporatinig this
> change.
>  
> > Of course I expect to drop support for 32-bit before 2038 - certainly when
> > one our dependencies drops support. But I've gotten a bug report for
> > building Maude on a Raspberry Pi.
> 
> Raspian is based on Debian and if the 32bit ARM architectures fail here
> Raspian people have a problem.
> 
> Kind regards
>Andreas. 
> 
> -- 
> https://fam-tille.de
> 
Best,
Nilesh


signature.asc
Description: PGP signature

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

[Sebastian Ramacher]

Control: tags 1065980 + patch


Dear maintainer,

I've prepared an NMU for gfarm (versioned as 2.7.20+dfsg-1.2). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru gfarm-2.7.20+dfsg/debian/changelog gfarm-2.7.20+dfsg/debian/changelog
--- gfarm-2.7.20+dfsg/debian/changelog	2024-02-28 18:35:22.0 +0100
+++ gfarm-2.7.20+dfsg/debian/changelog	2024-04-12 09:39:49.0 +0200
@@ -1,3 +1,13 @@
+gfarm (2.7.20+dfsg-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Peter Michael Green ]
+  * Add include of unistd.h to lib/libgfarm/gfarm/gfp_xdr.c to fix
+implicit declaration error. (Closes: #1065980)
+
+ -- Sebastian Ramacher   Fri, 12 Apr 2024 09:39:49 +0200
+
 gfarm (2.7.20+dfsg-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru gfarm-2.7.20+dfsg/debian/patches/missing-feature-test-macros.patch gfarm-2.7.20+dfsg/debian/patches/missing-feature-test-macros.patch
--- gfarm-2.7.20+dfsg/debian/patches/missing-feature-test-macros.patch	1970-01-01 01:00:00.0 +0100
+++ gfarm-2.7.20+dfsg/debian/patches/missing-feature-test-macros.patch	2024-04-12 09:39:36.0 +0200
@@ -0,0 +1,173 @@
+Index: gfarm-2.7.20+dfsg/lib/libgfarm/gfarm/gfp_xdr.c
+===
+--- gfarm-2.7.20+dfsg.orig/lib/libgfarm/gfarm/gfp_xdr.c
 gfarm-2.7.20+dfsg/lib/libgfarm/gfarm/gfp_xdr.c
+@@ -1,3 +1,4 @@
++#define _XOPEN_SOURCE 500
+ #include 
+ #include 
+ #include 
+Index: gfarm-2.7.20+dfsg/bench/gfperf/gfperf-autoreplica/gfperf-autoreplica-main.c
+===
+--- gfarm-2.7.20+dfsg.orig/bench/gfperf/gfperf-autoreplica/gfperf-autoreplica-main.c
 gfarm-2.7.20+dfsg/bench/gfperf/gfperf-autoreplica/gfperf-autoreplica-main.c
+@@ -2,6 +2,7 @@
+  * $Id$
+  */
+ 
++#define _GNU_SOURCE
+ #include "gfperf-lib.h"
+ #include 
+ #include 
+Index: gfarm-2.7.20+dfsg/bench/gfperf/gfperf-copy/gfperf-copy-gfarm2fs.c
+===
+--- gfarm-2.7.20+dfsg.orig/bench/gfperf/gfperf-copy/gfperf-copy-gfarm2fs.c
 gfarm-2.7.20+dfsg/bench/gfperf/gfperf-copy/gfperf-copy-gfarm2fs.c
+@@ -2,7 +2,7 @@
+  * $Id$
+  */
+ 
+-
++#define _GNU_SOURCE
+ #include 
+ #include 
+ #include 
+Index: gfarm-2.7.20+dfsg/bench/gfperf/gfperf-copy/gfperf-copy-main.c
+===
+--- gfarm-2.7.20+dfsg.orig/bench/gfperf/gfperf-copy/gfperf-copy-main.c
 gfarm-2.7.20+dfsg/bench/gfperf/gfperf-copy/gfperf-copy-main.c
+@@ -2,7 +2,7 @@
+  * $Id$
+  */
+ 
+-
++#define _GNU_SOURCE
+ #include "gfperf-lib.h"
+ #include 
+ #include 
+Index: gfarm-2.7.20+dfsg/bench/gfperf/gfperf-lib/gfperf-util.c
+===
+--- gfarm-2.7.20+dfsg.orig/bench/gfperf/gfperf-lib/gfperf-util.c
 gfarm-2.7.20+dfsg/bench/gfperf/gfperf-lib/gfperf-util.c
+@@ -2,7 +2,8 @@
+  * $Id$
+  */
+ 
+-
++#define _DEFAULT_SOURCE
++#define _XOPEN_SOURCE 500
+ #include 
+ #include 
+ #include 
+Index: gfarm-2.7.20+dfsg/bench/gfperf/gfperf-metadata/gfperf-metadata-main.c
+===
+--- gfarm-2.7.20+dfsg.orig/bench/gfperf/gfperf-metadata/gfperf-metadata-main.c
 gfarm-2.7.20+dfsg/bench/gfperf/gfperf-metadata/gfperf-metadata-main.c
+@@ -2,7 +2,7 @@
+  * $Id$
+  */
+ 
+-
++#define _GNU_SOURCE
+ #include "gfperf-lib.h"
+ #include 
+ #include 
+Index: gfarm-2.7.20+dfsg/bench/gfperf/gfperf-parallel-read/gfperf-parallel-read-main.c
+===
+--- gfarm-2.7.20+dfsg.orig/bench/gfperf/gfperf-parallel-read/gfperf-parallel-read-main.c
 gfarm-2.7.20+dfsg/bench/gfperf/gfperf-parallel-read/gfperf-parallel-read-main.c
+@@ -3,6 +3,7 @@
+  */
+ 
+ 
++#define _GNU_SOURCE
+ #include "gfperf-lib.h"
+ #include 
+ #include 
+Index: gfarm-2.7.20+dfsg/bench/gfperf/gfperf-parallel-write/gfperf-parallel-write-main.c
+===
+--- gfarm-2.7.20+dfsg.orig/bench/gfperf/gfperf-parallel-write/gfperf-parallel-write-main.c
 gfarm-2.7.20+dfsg/bench/gfperf/gfperf-parallel-write/gfperf-parallel-write-main.c
+@@ -3,6 +3,7 @@
+  */
+ 
+ 
++#define _GNU_SOURCE
+ #include "gfperf-lib.h"
+ #include 
+ #include 
+Index: gfarm-2.7.20+dfsg/bench/gfperf/gfperf-read/gfperf-read-main.c
+===
+--- gfarm-2.7.20+dfsg.orig/bench/gfperf/gfperf-read/gfperf-read-main.c
 gfarm-2.7.20+dfsg/bench/gfperf/gfperf-read/gfperf-read-main.c
+@@ -2,7 +2,7 @@
+  * $Id$
+  */
+ 
+-
++#define _GNU_SOURCE
+ #include "gfperf-lib.h"
+ #include 
+ #include 
+Index: gfarm-2.7.20+dfsg/bench/gfperf/gfperf-replica/gfperf-replica-main.c
+===
+--- gfarm-2.7.20+dfsg.orig/bench/gfperf/gfperf-replica/gfperf-replica-main.c
 gfarm-2.7.20+d

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

[Debian Bug Tracking System]

Processing control commands:

> tags 1065980 + patch
Bug #1065980 [src:gfarm] gfarm: FTBFS on arm{el,hf}:
Ignoring request to alter tags of bug #1065980 to the same tags previously set

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

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

[Debian Bug Tracking System]

Your message dated Fri, 12 Apr 2024 07:34:10 +
with message-id 
and subject line Bug#1065778: fixed in libcdio 2.1.0-4.2
has caused the Debian Bug report #1065778,
regarding libcdio: FTBFS on arm{el,hf}: _cdio_stdio.c:53:20: error: implicit 
declaration of function ‘fseeko64’; did you mean ‘fseeko’? 
[-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.)


-- 
1065778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcdio
Version: 2.1.0-4.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=libcdio&arch=armel&ver=2.1.0-4.1&stamp=1709540805&raw=0

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib/driver 
-I../../include -I../../include/ -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=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -Wbad-function-cast -Wcast-align 
-Wchar-subscripts -Wdeclaration-after-statement -Wdisabled-optimization 
-Wendif-labels -Winline -Wmissing-declarations -Wmissing-prototypes 
-Wnested-externs -Wno-sign-compare -Wpointer-arith -Wshadow -Wstrict-prototypes 
-Wundef -Wunused -Wwrite-strings -c cdio.c  -fPIC -DPIC -o .libs/cdio.o
_cdio_stdio.c: In function ‘_stdio_seek’:
_cdio_stdio.c:53:20: error: implicit declaration of function ‘fseeko64’; did 
you mean ‘fseeko’? [-Werror=implicit-function-declaration]
   53 | #define CDIO_FSEEK fseeko64
  |^~~~
_cdio_stdio.c:175:13: note: in expansion of macro ‘CDIO_FSEEK’
  175 |   if ( (ret=CDIO_FSEEK (ud->fd, i_offset, whence)) ) {
  | ^~
_cdio_stdio.c:53:20: warning: nested extern declaration of ‘fseeko64’ 
[-Wnested-externs]
   53 | #define CDIO_FSEEK fseeko64
  |^~~~
_cdio_stdio.c:175:13: note: in expansion of macro ‘CDIO_FSEEK’
  175 |   if ( (ret=CDIO_FSEEK (ud->fd, i_offset, whence)) ) {
  | ^~
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib/driver 
-I../../include -I../../include/ -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=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -Wall -Wbad-function-cast -Wcast-align 
-Wchar-subscripts -Wdeclaration-after-statement -Wdisabled-optimization 
-Wendif-labels -Winline -Wmissing-declarations -Wmissing-prototypes 
-Wnested-externs -Wno-sign-compare -Wpointer-arith -Wshadow -Wstrict-prototypes 
-Wundef -Wunused -Wwrite-strings -c aix.c -o aix.o >/dev/null 2>&1
_cdio_generic.c:73:1: warning: conflicting types for 
‘cdio_generic_unimplemented_eject_media’ due to enum/integer mismatch; have 
‘int(void *)’ [-Wenum-int-mismatch]
   73 | cdio_generic_unimplemented_eject_media (void *p_user_data) {
  | ^~
In file included from cdio_private.h:84,
 from _cdio_generic.c:50:
generic.h:96:24: note: previous declaration of 
‘cdio_generic_unimplemented_eject_media’ with type ‘driver_return_code_t(void 
*)’
   96 |   driver_return_code_t cdio_generic_unimplemented_eject_media (void 
*p_env);
  |^~
_cdio_generic.c:82:1: warning: conflicting types for 
‘cdio_generic_unimplemented_set_blocksize’ due to enum/integer mismatch; have 
‘int(void *, uint16_t)’ {aka ‘int(void *, short unsigned int)’} 
[-Wenum-int-mismatch]
   82 | cdio_generic_unimplemented_set_blocksize (void *p_user_data,
  | ^~~~
generic.h:104:3: note: previous declaration of 
‘cdio_generic_unimplemented_set_blocksize’ with type ‘driver_return_code_t(void 
*, uint16_t)’ {aka ‘driver_return_code_t(void *, short unsigned int)’}
  104 |   cdio_generic_unimplemented_set_blocksize (void *p_user_data,
  |   ^~~~
_cdio_generic.c:92:1: warning: conflicting types for 
‘cdio_generic_unimplemented_set_speed’ due to enum/integer mismatch; have 
‘int(void *, int)’ [-Wenum-int-mismatch]
   92 | cdio_generic_unimplemented_set_speed (void *p_user_data, int i_speed) {
  | ^~~~
generic.h:112:24: note: previous declaration of 
‘cdio_generic_unimplemente

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

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1068811 {Done: Bdale Garbee } [camv-rnd] camv-rnd: 
hardcoded librnd4 dependency
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions camv-rnd/1.1.4-2.
> notifxed -1 1.1.4-2
Unknown command or malformed arguments to command.

> severity -1 serious
Bug #1068811 [camv-rnd] camv-rnd: hardcoded librnd4 dependency
Ignoring request to change severity of Bug 1068811 to the same value.

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

Bug#1068811: reopening also camv-rnd

[Gianfranco Costamagna]

control: reopen -1
control: notifxed -1 1.1.4-2
control: severity -1 serious

there is one left...

 Package: camv-rnd-export-vector
 Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}, camv-rnd-core (= 
${binary:Version}), librnd4
+Depends: ${misc:Depends}, ${shlibs:Depends}, camv-rnd-core (= 
${binary:Version})
 Description: Export formats: vector graphics
  Common vector graphic export formats: ps, eps, svg.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: libcdio: diff for NMU version 2.1.0-4.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1065778 + patch
Bug #1065778 [src:libcdio] libcdio: FTBFS on arm{el,hf}: _cdio_stdio.c:53:20: 
error: implicit declaration of function ‘fseeko64’; did you mean ‘fseeko’? 
[-Werror=implicit-function-declaration]
Ignoring request to alter tags of bug #1065778 to the same tags previously set

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

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

[Sebastian Ramacher]

Control: tags 1065778 + patch

Dear maintainer,

I've prepared an NMU for libcdio (versioned as 2.1.0-4.2). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru libcdio-2.1.0/debian/changelog libcdio-2.1.0/debian/changelog
--- libcdio-2.1.0/debian/changelog	2024-02-29 11:35:17.0 +0100
+++ libcdio-2.1.0/debian/changelog	2024-04-12 09:09:50.0 +0200
@@ -1,3 +1,13 @@
+libcdio (2.1.0-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Zixing Liu ]
+  * debian/patches/arm-t64-redirect-fix.patch: Fix implicit declaration
+after armhf time_t transition. (Closes: #1065778)
+
+ -- Sebastian Ramacher   Fri, 12 Apr 2024 09:09:50 +0200
+
 libcdio (2.1.0-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libcdio-2.1.0/debian/patches/arm-t64-redirect-fix.patch libcdio-2.1.0/debian/patches/arm-t64-redirect-fix.patch
--- libcdio-2.1.0/debian/patches/arm-t64-redirect-fix.patch	1970-01-01 01:00:00.0 +0100
+++ libcdio-2.1.0/debian/patches/arm-t64-redirect-fix.patch	2024-04-12 09:08:57.0 +0200
@@ -0,0 +1,22 @@
+Description: Fix implicit declaration after armhf time_t transition
+Author: Zixing Liu 
+Forwarded: no
+Last-Update: 2024-04-03
+
+Index: libcdio/lib/driver/_cdio_stdio.h
+===
+--- libcdio.orig/lib/driver/_cdio_stdio.h
 libcdio/lib/driver/_cdio_stdio.h
+@@ -22,6 +22,12 @@
+ 
+ #include "_cdio_stream.h"
+ 
++#include 
++#if defined(_FILE_OFFSET_BITS) && defined(__REDIRECT) && (_FILE_OFFSET_BITS == 64)
++#define lseek64 lseek
++#define fseeko64 fseeko
++#endif
++
+ /*!
+   Initialize a new stdio stream reading from pathname.
+   A pointer to the stream is returned or NULL if there was an error.
diff -Nru libcdio-2.1.0/debian/patches/series libcdio-2.1.0/debian/patches/series
--- libcdio-2.1.0/debian/patches/series	2022-09-27 11:36:24.0 +0200
+++ libcdio-2.1.0/debian/patches/series	2024-04-12 09:08:57.0 +0200
@@ -3,3 +3,4 @@
 src-cdda-player.c-always-use-s-style-format-for-prin.patch
 Correct-realpath-test-failure.patch
 Use-getmntent-setmntent-for-reading-mounts.patch
+arm-t64-redirect-fix.patch

Processed: Re:

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1068810 {Done: Bdale Garbee } [sch-rnd] sch-rnd: hardcoded 
librnd4 dependency
Bug reopened
Ignoring request to alter fixed versions of bug #1068810 to the same values 
previously set
> severity -1 serious
Bug #1068810 [sch-rnd] sch-rnd: hardcoded librnd4 dependency
Ignoring request to change severity of Bug 1068810 to the same value.

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

Processed: Re:

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1068812 [pcb-rnd] pcb-rnd: hardcoded librnd4 dependency
Bug 1068812 is not marked as done; doing nothing.
> severity -1 serious
Bug #1068812 [pcb-rnd] pcb-rnd: hardcoded librnd4 dependency
Severity set to 'serious' from 'minor'

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

Bug#1068810:

[Gianfranco Costamagna]

control: reopen -1
control: severity -1 serious

On Thu, 11 Apr 2024 13:17:44 -0600 Bdale Garbee  wrote:

The librnd4 runtime dependency is needed to ensure at least a minimum
version of that library is available so required capability is present.
The "hard coded" dependency is not actually a bug, much less a
release-critical bug.



yes, but the library was renamed in librnd4t64, so either you need to depend on 
the new one,
or drop it, to let the auto decrufter finish the time64_t transition and 
decruft it.
Depending on NBS packages is RC critical.

Otherwise librnd wouldn't be able to migrate in testing, and the package be 
installable at all.

G.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#965837: tart: Change of debhelper compat

[Andrey Rakhmatullin]

On Fri, Jan 12, 2024 at 05:12:36PM +0800, i...@0w.al wrote:
> I have changed the compat version from 5 to 13 to fix the build error, and 
> fixed some lintian warnings
Hello. As the package is orphaned, it's not very useful to send patches to
its bug reports unless you want to do the upload yourself.
If you do, please either adopt the package or do a QA upload, filing an
RFS in either case.

-- 
WBR, wRAR


signature.asc
Description: PGP signature