Bug#1066486: marked as done (icom: FTBFS: icom.c:108:24: error: implicit declaration of function ‘getopt’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Wed, 20 Mar 2024 05:47:47 +
with message-id 
and subject line Bug#1066486: fixed in icom 20120228-5
has caused the Debian Bug report #1066486,
regarding icom: FTBFS: icom.c:108:24: error: implicit declaration of function 
‘getopt’ [-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.)


-- 
1066486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icom
Version: 20120228-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 -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g 
> -O   -I../include -Wdate-time -D_FORTIFY_SOURCE=2  -c -o tables.o tables.c
> packet.c: In function ‘sndoctet’:
> packet.c:339:9: warning: ignoring return value of ‘write’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   339 | write(fd_icom, , 1);
>   | ^
> icom.c: In function ‘main’:
> icom.c:108:24: error: implicit declaration of function ‘getopt’ 
> [-Werror=implicit-function-declaration]
>   108 | while ((temp = getopt(argc, argcv, "c:df:g:km:o:r:")) != -1) {
>   |^~
> icom.c:314:32: error: implicit declaration of function ‘command’ 
> [-Werror=implicit-function-declaration]
>   314 | temp = command(rptr, key);
>   |^~~
> icom.c:326:41: error: implicit declaration of function ‘close’; did you mean 
> ‘pclose’? [-Werror=implicit-function-declaration]
>   326 | close(fp_cmd[fp]);
>   | ^
>   | pclose
> icom.c:335:37: error: implicit declaration of function ‘gets’; did you mean 
> ‘fgets’? [-Werror=implicit-function-declaration]
>   335 | if (gets(args) == NULL)
>   | ^~~~
>   | fgets
> icom.c:335:48: warning: comparison between pointer and integer
>   335 | if (gets(args) == NULL)
>   |^~
> icom.c: In function ‘qqsv’:
> icom.c:628:17: error: implicit declaration of function ‘gettimeofday’ 
> [-Werror=implicit-function-declaration]
>   628 | gettimeofday(, NULL);
>   | ^~~~
> radio.c: In function ‘select_radio’:
> radio.c:168:17: error: implicit declaration of function ‘capkey’ 
> [-Werror=implicit-function-declaration]
>   168 | temp1 = capkey("lsb", rp->modetab);
>   | ^~
> icom.c:637:33: error: implicit declaration of function ‘dtohex’ 
> [-Werror=implicit-function-declaration]
>   637 | dtohex(tm->tm_year + 1900,
>   | ^~
> radio.c: In function ‘readchan’:
> radio.c:329:17: error: implicit declaration of function ‘readvfo’ 
> [-Werror=implicit-function-declaration]
>   329 | return (readvfo(rp));
>   | ^~~
> icom.c:886:25: error: implicit declaration of function ‘emptyvfo’ 
> [-Werror=implicit-function-declaration]
>   886 | emptyvfo(cp);
>   | ^~~~
> icom.c:1002:32: error: implicit declaration of function ‘emptychan’; did you 
> mean ‘empty_chan’? [-Werror=implicit-function-declaration]
>  1002 | rval = emptychan(rp->ident, cp);
>   |^
>   |empty_chan
> icom.c:1171:33: error: implicit declaration of function ‘readvfo’ 
> [-Werror=implicit-function-declaration]
>  1171 | readvfo(rp);
>   | ^~~
> icom.c:1247:32: error: implicit declaration of function ‘readoffset’; did you 
> mean ‘loadoffset’? [-Werror=implicit-function-declaration]
>  1247 |   

Processed: Bug#1066486 marked as pending in icom

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066486 [src:icom] icom: FTBFS: icom.c:108:24: error: implicit declaration 
of function ‘getopt’ [-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1066486: marked as pending in icom

[Tony Mancill]

Control: tag -1 pending

Hello,

Bug #1066486 in icom 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/debian-hamradio-team/icom/-/commit/6202780aa55b0c7c2a7039777e7d298bc7a4d85c


Clean-up compiler warnings (Closes: #1066486)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066486

Bug#1066356: marked as done (ncbi-tools6: FTBFS: asn2gnb2.c:3409:14: error: implicit declaration of function ‘PrintDate’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Wed, 20 Mar 2024 05:00:49 +
with message-id 
and subject line Bug#1066356: fixed in ncbi-tools6 6.1.20170106+dfsg2-2
has caused the Debian Bug report #1066356,
regarding ncbi-tools6: FTBFS: asn2gnb2.c:3409:14: error: implicit declaration 
of function ‘PrintDate’ [-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.)


-- 
1066356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncbi-tools6
Version: 6.1.20170106+dfsg2-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):
> 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 
> -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_PNG -I../include -DWIN_MOTIF 
> asn2gnb2.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from ../include/ncbilcl.h:150,
>  from ../include/ncbi.h:57,
>  from asn2gnb2.c:42:
> /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> asn2gnb2.c: In function ‘s_LocusAddSuffix’:
> asn2gnb2.c:217:11: warning: variable ‘ch’ set but not used 
> [-Wunused-but-set-variable]
>   217 |   Charch;
>   |   ^~
> asn2gnb2.c: In function ‘AddLocusBlock’:
> asn2gnb2.c:1361:66: warning: suggest parentheses around ‘&&’ within ‘||’ 
> [-Wparentheses]
>  1361 |   } else if ((moltype >= 2 && moltype <= 8) || moltype >= 10 && 
> moltype <= 11) {
>   |
> ~~^~~~
> asn2gnb2.c: In function ‘IsSuccessor’:
> asn2gnb2.c:1742:15: warning: comparison between pointer and zero character 
> constant [-Wpointer-compare]
>  1742 |   while (accp != '\0'  &&  prevp != '\0') {
>   |   ^~
> asn2gnb2.c:1742:10: note: did you mean to dereference the pointer?
>  1742 |   while (accp != '\0'  &&  prevp != '\0') {
>   |  ^
> asn2gnb2.c:1742:34: warning: comparison between pointer and zero character 
> constant [-Wpointer-compare]
>  1742 |   while (accp != '\0'  &&  prevp != '\0') {
>   |  ^~
> asn2gnb2.c:1742:28: note: did you mean to dereference the pointer?
>  1742 |   while (accp != '\0'  &&  prevp != '\0') {
>   |^
> asn2gnb2.c: In function ‘IsProjectAccn’:
> asn2gnb2.c:1767:38: warning: comparison between pointer and zero character 
> constant [-Wpointer-compare]
>  1767 | for (ptr = acc, letters = 0; ptr != '\0'  &&  IS_ALPHA(*ptr); 
> ++ptr, ++letters) continue;
>   |  ^~
> asn2gnb2.c:1767:34: note: did you mean to dereference the pointer?
>  1767 | for (ptr = acc, letters = 0; ptr != '\0'  &&  IS_ALPHA(*ptr); 
> ++ptr, ++letters) continue;
>   |  ^
> asn2gnb2.c: In function ‘AddDblinkBlock’:
> asn2gnb2.c:2892:22: warning: variable ‘parentID’ set but not used 
> [-Wunused-but-set-variable]
>  2892 |   Int4   parentID;
>   |  ^~~~
> asn2gnb2.c: In function ‘AddSPBlock’:
> asn2gnb2.c:3409:14: error: implicit declaration of function ‘PrintDate’ 
> [-Werror=implicit-function-declaration]
>  3409 | string = PrintDate (spb->created);
>   |  ^
> asn2gnb2.c:3409:12: warning: assignment to ‘Nlm_CharPtr’ {aka ‘char *’} from 
> ‘int’ makes pointer from integer without a cast [-Wint-conversion]
>  3409 | string = PrintDate (spb->created);
>   |^
> asn2gnb2.c:3417:12: warning: assignment to ‘Nlm_CharPtr’ {aka ‘char *’} from 
> ‘int’ makes pointer from integer without a cast [-Wint-conversion]
>  3417 | string = PrintDate (spb->sequpd);
>   |^
> asn2gnb2.c:3424:12: warning: assignment to ‘Nlm_CharPtr’ {aka ‘char *’} from 
> ‘int’ makes pointer from integer 

Bug#1067208: umockdev: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"

[Thorsten Glaser]

Source: umockdev
Version: 0.18.0-1
Severity: serious
Justification: FTBFS on t64-affected archs
X-Debbugs-Cc: t...@mirbsd.de
Tags: ftbfs

cc -Ilibumockdev-preload.so.0.0.0.p -I. -I.. -fdiagnostics-color=always -Wall 
-Winvalid-pch -std=gnu11 -Werror=missing-prototypes -Werror=strict-prototypes 
-Werror=nested-externs -Werror=pointer-arith 
-Werror=implicit-function-declaration -Werror=implicit-int 
-Werror=int-conversion -Werror=old-style-definition -Werror=pointer-arith 
-Werror=init-self -Werror=format-security -Werror=format=2 -Werror=return-type 
-Werror=uninitialized -Wcast-align -Wno-error=pragmas 
-Wno-error=discarded-qualifiers -Wno-error=incompatible-pointer-types 
-Wno-error=pointer-sign -Wno-unused-but-set-variable -Wno-unused-function 
-Wno-unused-label -Wno-unused-value -Wno-unused-variable -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=default -MD 
-MQ libumockdev-preload.so.0.0.0.p/src_libumockdev-preload.c.o -MF 
libumockdev-preload.so.0.0.0.p/src_libumockdev-preload.c.o.d -o 
libumockdev-preload.so.0.0.0.p/src_libumockdev-preload.c.o -c 
../src/libumockdev-preload.c
In file included from /usr/include/features.h:393,
 from /usr/include/assert.h:35,
 from ../src/libumockdev-preload.c:31:
/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed 
only with _FILE_OFFSET_BITS=64"
   26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
  | ^


I admit I don’t exactly see what’s going on here. Does it
maybe #unset _FILE_OFFSET_BITS or something?

Bug#1054770: marked as done (pandoc-citeproc-preamble: FTBFS: make[1]: *** [debian/rules:32: override_dh_auto_test] Error 2)

[Debian Bug Tracking System]

Your message dated Wed, 20 Mar 2024 10:34:30 +0800
with message-id <87cyrp7hs9@melete.silentflame.com>
and subject line Re: Bug#1054770: pandoc-citeproc-preamble: FTBFS: make[1]: *** 
[debian/rules:32: override_dh_auto_test] Error 2
has caused the Debian Bug report #1054770,
regarding pandoc-citeproc-preamble: FTBFS: make[1]: *** [debian/rules:32: 
override_dh_auto_test] Error 2
to be marked as done.

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

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


-- 
1054770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pandoc-citeproc-preamble
Version: 1.7-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> test/test
> testing with pandoc 2.17.1.1
> pandoc-citeproc-preamble: Error in $: Incompatible API versions: encoded with 
> [1,22,2,1] but attempted to decode with [1,23,1].
> CallStack (from HasCallStack):
>   error, called at src/Text/Pandoc/JSON.hs:120:27 in 
> pandoc-types-1.23.1-DyTGyibh0ilGLrNoO8Eh1n:Text.Pandoc.JSON
> Error running filter 
> ../dist/build/pandoc-citeproc-preamble/pandoc-citeproc-preamble:
> Filter returned error status 1
> readline() on closed filehandle $fh at test/test line 46.
> neither preamble nor references found!
> make[1]: *** [debian/rules:32: override_dh_auto_test] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/pandoc-citeproc-preamble_1.7-1_unstable.log

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

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

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

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

Hello,

On Fri 27 Oct 2023 at 09:31pm +02, Lucas Nussbaum wrote:

> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
>> make[1]: Entering directory '/<>'
>> test/test
>> testing with pandoc 2.17.1.1
>> pandoc-citeproc-preamble: Error in $: Incompatible API versions: encoded
>> with [1,22,2,1] but attempted to decode with [1,23,1].
>> CallStack (from HasCallStack):
>>   error, called at src/Text/Pandoc/JSON.hs:120:27 in
>> pandoc-types-1.23.1-DyTGyibh0ilGLrNoO8Eh1n:Text.Pandoc.JSON
>> Error running filter 
>> ../dist/build/pandoc-citeproc-preamble/pandoc-citeproc-preamble:
>> Filter returned error status 1
>> readline() on closed filehandle $fh at test/test line 46.
>> neither preamble nor references found!
>> make[1]: *** [debian/rules:32: override_dh_auto_test] Error 2

This is no longer reproducible.  I think that it probably occurred due
to skew between pandoc and pandoc-types.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---

Bug#1065436: cyrus-sasl2 accesses resources from the network during the build

[Thorsten Glaser]

Matthias Klose dixit:

> the Debian build log doesn't show this error message, so this sphinx
> inventory is fetched from the website during the build.

Huh? Does sbuild/buildd not unshare the network?

I added that to pbuilder some time ago and vaguely recall
that there was an expectation that the buildds do that as
well, and a bit of back and forth leading to the loopback
interface being initialised in the separate namespace but
nothing more.

bye,
//mirabilos
-- 
 den AGP stecker anfeilen, damit er in den slot aufm 440BX board passt…
oder netzteile, an die man auch den monitor angeschlossen hat und die dann für
ein elektrisch aufgeladenes gehäuse gesorgt haben […] für lacher gut auf jeder
LAN party │  damals, als der pizzateig noch auf dem monior "gegangen" ist

Bug#1066794:

[Michael Hudson-Doyle]

It's hard to see from the log but the failures that are causing issues are
the "path_info" gitweb tests such as

expecting success of 9500.70 'path_info: project': gitweb_run "" "/.git"
not ok 70 - path_info: project
# gitweb_run "" "/.git"

It's *impossible* to see from the log afaict but the reason this fails is
because something has caused gitweb.perl to emit warnings like

[Wed Mar 20 02:04:51 2024] gitweb.perl: Use of uninitialized value $my_url
in substitution (s///) at /build/git-VGz7d1/git-2.43.0/gitweb/gitweb.perl
line 70.

This might be because of a new version of libcgi-pm-perl, but downgrading
that package does not make every failure go, leaving warnings like

[Wed Mar 20 02:07:53 2024] gitweb.perl: Use of uninitialized value $base in
open at /build/git-VGz7d1/git-2.43.0/gitweb/gitweb.perl line 2886.

Which still cause a failure. Has perl itself changed in behaviour here?

Bug#1064772: pymupdf: FTBFS: fitz.i.c:3343:5: error: conflicting types for ‘fz_pixmap_size’; have ‘int(fz_context *, fz_pixmap *)’

[Michael Hudson-Doyle]

Package: pymupdf
Followup-For: Bug #1064772
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Control: tags -1 patch

Dear Maintainer,

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

  * Remove prototype that now clashes with version in mupdf's headers.

Thanks for considering the patch.


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

Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru pymupdf-1.23.7+ds1/debian/patches/fz_pixmap_size 
pymupdf-1.23.7+ds1/debian/patches/fz_pixmap_size
--- pymupdf-1.23.7+ds1/debian/patches/fz_pixmap_size1970-01-01 
12:00:00.0 +1200
+++ pymupdf-1.23.7+ds1/debian/patches/fz_pixmap_size2024-03-20 
14:23:27.0 +1300
@@ -0,0 +1,17 @@
+Description: Remove incorrect prototype for function now declared in mupdf's 
headers.
+Author: Michael Hudson-Doyle 
+Origin: vendor
+Forwarded: no
+Last-Update: 2024-03-20
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/fitz/fitz.i
 b/fitz/fitz.i
+@@ -155,7 +155,6 @@
+ // additional headers --
+ pdf_obj *pdf_lookup_page_loc(fz_context *ctx, pdf_document *doc, int needle, 
pdf_obj **parentp, int *indexp);
+ fz_pixmap *fz_scale_pixmap(fz_context *ctx, fz_pixmap *src, float x, float y, 
float w, float h, const fz_irect *clip);
+-int fz_pixmap_size(fz_context *ctx, fz_pixmap *src);
+ void fz_subsample_pixmap(fz_context *ctx, fz_pixmap *tile, int factor);
+ void fz_copy_pixmap_rect(fz_context *ctx, fz_pixmap *dest, fz_pixmap *src, 
fz_irect b, const fz_default_colorspaces *default_cs);
+ static const float JM_font_ascender(fz_context *ctx, fz_font *font);
diff -Nru pymupdf-1.23.7+ds1/debian/patches/series 
pymupdf-1.23.7+ds1/debian/patches/series
--- pymupdf-1.23.7+ds1/debian/patches/series2023-12-17 03:32:08.0 
+1300
+++ pymupdf-1.23.7+ds1/debian/patches/series2024-03-20 14:22:54.0 
+1300
@@ -1,2 +1,3 @@
 docs
 fiximport
+fz_pixmap_size

Processed: Re: pymupdf: FTBFS: fitz.i.c:3343:5: error: conflicting types for ‘fz_pixmap_size’; have ‘int(fz_context *, fz_pixmap *)’

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1064772 [src:pymupdf] pymupdf: FTBFS: fitz.i.c:3343:5: error: conflicting 
types for ‘fz_pixmap_size’; have ‘int(fz_context *, fz_pixmap *)’
Added tag(s) patch.

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

Processed: Re: libspf2: FTBFS on arm{el,hf}: spf_utils.c:207:9: error: implicit declaration of function ‘memset’ [-Werror=implicit-function-declaration]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1065792 [src:libspf2] libspf2: FTBFS on arm{el,hf}: spf_utils.c:207:9: 
error: implicit declaration of function ‘memset’ 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1065792: libspf2: FTBFS on arm{el,hf}: spf_utils.c:207:9: error: implicit declaration of function ‘memset’ [-Werror=implicit-function-declaration]

[Michael Hudson-Doyle]

Package: libspf2
Followup-For: Bug #1065792
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Control: tags -1 patch

Dear Maintainer,


In Ubuntu, I just uploaded the following rather than try to be in any
way clever:


  * d/patches/fix-include.patch: Include string.h in spf_utils.c to get a
declaration for memset(). (Closes: #1065792, #1066276)


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libspf2-1.2.10/debian/patches/fix-include.patch 
libspf2-1.2.10/debian/patches/fix-include.patch
--- libspf2-1.2.10/debian/patches/fix-include.patch 1970-01-01 
12:00:00.0 +1200
+++ libspf2-1.2.10/debian/patches/fix-include.patch 2024-03-20 
13:27:19.0 +1300
@@ -0,0 +1,10 @@
+--- a/src/libspf2/spf_utils.c
 b/src/libspf2/spf_utils.c
+@@ -19,6 +19,7 @@
+ #ifdef STDC_HEADERS
+ # include  /* malloc / free */
+ # include/* isupper / tolower */
++# include/* memset */
+ #endif
+ 
+ #ifdef HAVE_MEMORY_H
diff -Nru libspf2-1.2.10/debian/patches/series 
libspf2-1.2.10/debian/patches/series
--- libspf2-1.2.10/debian/patches/series2023-10-23 05:33:14.0 
+1300
+++ libspf2-1.2.10/debian/patches/series2024-03-20 13:27:01.0 
+1300
@@ -7,3 +7,4 @@
 Fixed-reverse-macro-modifier.patch
 no-libreplace.patch
 spf_compile.c-more-correct-size-of-ds_avail.patch
+fix-include.patch

Bug#1067203: user-session-migration: fix ftbfs on architectures affected by t64 transition

[Michael Hudson-Doyle]

Package: user-session-migration
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com

Dear Maintainer,

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

  * Do not use "%ld" specifier to print time_t timestamp.

This fixes a test failure (and misbehaviour) on systems where time_t is
64-bit and long is 32-bit.

Thanks for considering the patch.


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

Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru user-session-migration-0.4.1ubuntu1/src/user-session-migration.c 
user-session-migration-0.4.1ubuntu2/src/user-session-migration.c
--- user-session-migration-0.4.1ubuntu1/src/user-session-migration.c
2023-04-10 06:06:15.0 +1200
+++ user-session-migration-0.4.1ubuntu2/src/user-session-migration.c
2024-03-20 12:29:27.0 +1300
@@ -277,7 +277,7 @@
   filename = get_migration_filename();
   keyfile = g_key_file_new ();
 
-  str = g_strdup_printf ("%ld", time (NULL));
+  str = g_strdup_printf ("%lld", (long long)time (NULL));
   g_key_file_set_string (keyfile,
  "State", "timestamp", str);
   g_free (str);

Bug#1066952: marked as done (Defaulting to -Werror=implicit-function-declaration might not be a good idea)

[Debian Bug Tracking System]

Your message dated Wed, 20 Mar 2024 00:06:15 +0100
with message-id 
and subject line Re: Bug#1066952: Defaulting to 
-Werror=implicit-function-declaration might not be a good idea
has caused the Debian Bug report #1066952,
regarding Defaulting to -Werror=implicit-function-declaration might not be a 
good idea
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.)


-- 
1066952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.22.6
Severity: serious
X-Debbugs-Cc: Steve Langasek 

There are at least 3 different ways how -Werror=implicit-function-declaration
breaks packages:

1. Code that did emit implicit-function-declaration warnings during
   compilation before and does FTBFS now

2. Code that does FTBFS now due to other breakage caused by
   -Werror=implicit-function-declaration, e.g. in autoconf tests

3. Code that does still compile with -Werror=implicit-function-declaration
   but behaves differently, e.g. due to failing autoconf tests silently
   disabling features


Cases from point 1 were always(?) bugs and it is good that
they get fixed.

The real-world effect of these bugs can be everywhere from
"completely harmless" to "that was always broken".

Debian has automation listing implicit-function-declaration warnings
in all packages already running for several years:
https://qa.debian.org/bls/bytag/W-implicit-declaration.html


My main worry is point 3, issues like #1066394.

#1066394 was found due to causing a FTBFS in a different package,
but the more common case is likely that a program has some
feature/plugin disabled and this won't be spotted until much later.

"Much later" might be after the release of trixie a user upgrading
to bookworm who uses this feature.

Or it might result in a program silently using an insecure legacy codepath,
e.g. after a test for getentropy() failed.


A large part of the packages in unstable might not get recompiled
between now and the release of trixie, creating the additional
issue that any such problem might occur only after a security update
or point release update if this is the next rebuild of the package
in trixie.
--- End Message ---
--- Begin Message ---
Hi!

On Sat, 2024-03-16 at 01:57:16 +0100, Guillem Jover wrote:
> On Sat, 2024-03-16 at 02:18:22 +0200, Adrian Bunk wrote:
> > Package: dpkg-dev
> > Version: 1.22.6
> > Severity: serious
> > X-Debbugs-Cc: Steve Langasek 
> 
> > 3. Code that does still compile with -Werror=implicit-function-declaration
> >but behaves differently, e.g. due to failing autoconf tests silently
> >disabling features
> 
> > Debian has automation listing implicit-function-declaration warnings
> > in all packages already running for several years:
> > https://qa.debian.org/bls/bytag/W-implicit-declaration.html
> 
> > My main worry is point 3, issues like #1066394.
> > 
> > #1066394 was found due to causing a FTBFS in a different package,
> > but the more common case is likely that a program has some
> > feature/plugin disabled and this won't be spotted until much later.
> > 
> > "Much later" might be after the release of trixie a user upgrading
> > to bookworm who uses this feature.
> > 
> > Or it might result in a program silently using an insecure legacy codepath,
> > e.g. after a test for getentropy() failed.
> 
> Not enabling this -Werror might imply ABI breakage for the time64
> transition, which seems pretty terrible too. The way I see it, and
> given the timing, effort and preparation necessary for this transition,
> both options (enabling or not enabling the fatal warning) are potentially
> bad in their own way.
> 
> But given that these are clearly bugs, that not enabling them can imply
> ABI breakage, that if things go according to plan (AFAIK) this will be
> made the default anyway with gcc-14, that we can track those down, and
> people have already been doing that for the Modern-C effort, see:
> 
>   https://fedoraproject.org/wiki/Changes/PortingToModernC
>   https://wiki.gentoo.org/wiki/Modern_C_porting
> 
> I think we might as well just cope with this anyway right away.
> 
> > A large part of the packages in unstable might not get recompiled
> > between now and the release of trixie, creating the additional
> > issue that any such problem might occur only after a security update
> > or point release update if this is the next rebuild of the package
> > in trixie.
> 
> AFAIUI (and I'd expect) the whole distribution needs to be rebuilt
> anyway as part of the time64 transition, otherwise the 32-bit ports
> that are 

Bug#1067142: marked as done (python-av: missing depend on python3-all for autopkgtest)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 23:07:05 +
with message-id 
and subject line Bug#1067142: fixed in python-av 11.0.0-4
has caused the Debian Bug report #1067142,
regarding python-av: missing depend on python3-all for autopkgtest
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.)


-- 
1067142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-av
Version: 11.0.0-3
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

your package has an autopkgtest regression due to changes in NumPy.
The python3-numpy package no longer depends on all supported Python 
versions. You need to depend on python3-all if you want to run your 
tests against all supported Python releases.

Cheers
Timo

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmX5ZJkACgkQ+C8H+466
LVlbzgwAsNQR0D8jal0Wq22h2IiJ/2wCN1ZfvkOic8bS+6n5dXkWt7uynYqaDFxl
PI1AeZg/aKujIO+cMWp+rft4RLNEOhGze98Y5kP01L5yYj6K/pscZpLfYloVJVcU
a/ByHVVgXKAoBD/JsDDeV4Xi/zPFs8IyXWTeOkO5c1l4PBycHlZ+rnlObp0lb/Rr
1UqJKprMqJSO1FStx3S6p9kO/MTz2O+UDweC+zsnEerEXUbqXr7Qgafeco0XiHs1
+BvTgGvzpHIUa+1tWFOyQqeYNpUpEtNkOCd787D56vvA/rZQ9pnWsKrexvCpzkMh
kgrx2N1Mv6sY5y2Fplis5rigdi36PqD/pF8ATD7C6CHFV2sk4dxt4DTQpAY72a3m
ac1dj0N7EoTip/ky0ecOGUCGjFT5zYfanEnhZYk4BUO6GThx1a4H/S1ewZMTLiuC
6qghvXv4yi3zqkUATpD8vhlHp+Gm12pwWdQ48aDLDtFFSh7okK/aYyLJRr66NnAT
3kl6+x+n
=Ui1t
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: python-av
Source-Version: 11.0.0-4
Done: Jonas Smedegaard 

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated python-av 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: Tue, 19 Mar 2024 23:38:16 +0100
Source: python-av
Architecture: source
Version: 11.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1067142
Changes:
 python-av (11.0.0-4) unstable; urgency=medium
 .
   * autopkgtest-depend on python3-all;
 closes: bug#1067142, thanks to Timo Röhling
Checksums-Sha1:
 8d11295f54d066c56c174aeebefca549fb93ee3a 2191 python-av_11.0.0-4.dsc
 a09e24c4d9ddf410fb395d3efda11c1a0c6c40ac 7224 python-av_11.0.0-4.debian.tar.xz
 72c858a0372f7fed01169f59aa14cf03b05952f3 14133 
python-av_11.0.0-4_amd64.buildinfo
Checksums-Sha256:
 6bc60ad37edf58120c79b708e6e46ebaded24e099ff3d19d2caffc8aeede415a 2191 
python-av_11.0.0-4.dsc
 e9f40244beda32d6f23c8b1e7d0d83d23e67ac9113b3eb27b3c753d81c43b865 7224 
python-av_11.0.0-4.debian.tar.xz
 0230742edf91cda31383c50d1c7fd0de60db43503b7630d1b75d9176cc545156 14133 
python-av_11.0.0-4_amd64.buildinfo
Files:
 4da030535950d28beb538d3c21388e4e 2191 python optional python-av_11.0.0-4.dsc
 cfbf740ef1014ca9da70df4397c75280 7224 python optional 
python-av_11.0.0-4.debian.tar.xz
 f1f590c6402eaea95579ab51db46892d 14133 python optional 
python-av_11.0.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmX6FroACgkQLHwxRsGg
ASHNig/+PDqwYNTmDsgQ4je64paQ4tK0qCfcT/Yz6RrTs54W1TCWIbwBgDIQItw5
6z0KIibkwrHcj+sWOW22WdPHS/HZdM6NwGUg28+JIqDvUq01NCwkosKWtrv40+jD
IhuMS3BTvHdoHhwpO85mSA0x8dpSa4nHjIGbC948Zn4gWa9Vjg29SFeOM+DhI2A4
txe1ufwEcWcgnGmxLRIhapkOsmcfBp64Eqjw9IYjPIV6c+Ox3us0hRcVFLZA67Bq
I+8bQ78YHuN44D+k2FTDRNZQMnEhoO10O2Khpy69RLW4r0cXpXYePwEmvpjkOL1q
lyDgmaFpnB6OcBrI4cUYIVSnCKAUKDWpp5IZHg2wWyMFhayCExFBvQmQcl2uFAJi
fQavJA5/QDF54ziPf6fGq06ka7aBwiy1w/wvfLS3QJE595cPtzE+n57ExtSn/HkW
z6qwFWOIgUYzWnjsuJQgTMHiepXdvxiEDfUR+51LWwB8QLDrq36oSIEdNqIo116o
v18G3LLxckr6880Ly5nvY+2/qDcGkow4myEVdvVgdIo5sMlKBOqCPfwEgd96e4nz
QF1Usap8DeC9GiWII3x3iAzpJTLBtLS0NilcRfapeuDB947KcLhcrVqHskl0suUu
aIZ4jR69X54xawvShMPe7D10Mv0A/ZpTFd3LvEQOi9PDWQeo/84=
=mZzo
-END PGP SIGNATURE-



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

Bug#1066811: cyrus-sasl2: assumes time_t fits into long for printf and scanf(!), will break on big endian

[Bastian Germann]

Control: forwarded -1 https://github.com/cyrusimap/cyrus-sasl/issues/484

Processed: Re: cyrus-sasl2: assumes time_t fits into long for printf and scanf(!), will break on big endian

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/cyrusimap/cyrus-sasl/issues/484
Bug #1066811 [src:cyrus-sasl2] cyrus-sasl2: assumes time_t fits into long for 
printf and scanf(!), will break on big endian
Set Bug forwarded-to-address to 
'https://github.com/cyrusimap/cyrus-sasl/issues/484'.

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

Processed: found 1064737 in 3.12.1-1, tagging 1067170, tagging 1067190, tagging 1067191, tagging 1067189 ...

[Debian Bug Tracking System]

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

> found 1064737 3.12.1-1
Bug #1064737 {Done: Matthias Klose } [src:python3-defaults] 
python3-defaults: FTBFS: make: *** [debian/rules:64: stamp-doc-policy] Error 1
Marked as found in versions python3-defaults/3.12.1-1 and reopened.
> tags 1067170 + sid trixie
Bug #1067170 [0install] 0install: hard-coded dependency on libgtk-3-0 will 
become uninstallable on armel/armhf
Added tag(s) trixie and sid.
> tags 1067190 + sid trixie
Bug #1067190 [timekpr-next] timekpr-next: hard-coded dependency on libgtk-3-0 
will become uninstallable on armel/armhf
Added tag(s) sid and trixie.
> tags 1067191 + sid trixie
Bug #1067191 [gnome-subtitles] gnome-subtitles: hard-coded dependency on 
libgtk-3-0 will become uninstallable on armel/armhf
Added tag(s) trixie and sid.
> tags 1067189 + sid trixie
Bug #1067189 {Done: Andrej Shadura } [syncthing-gtk] 
syncthing-gtk: hard-coded dependency on libgtk-3-0 will become uninstallable on 
armel/armhf
Added tag(s) trixie and sid.
> tags 1067192 + sid trixie
Bug #1067192 [src:gtk-d] gtk-d: hard-coded dependency on libgtk-3-0 will become 
uninstallable on armel/armhf
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Processed: NMU pending for #1066136

[Debian Bug Tracking System]

Processing control commands:

> tags 1066136 + pending
Bug #1066136 [python3-xapian-haystack] python3-xapian-haystack: unusable on 
stable due to use of deprecated module django.utils.six
Ignoring request to alter tags of bug #1066136 to the same tags previously set

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

Bug#1066269: marked as done (autolog: FTBFS: autolog.c:613:9: error: implicit declaration of function ‘re_comp’; did you mean ‘regcomp’? [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 22:49:30 +
with message-id 
and subject line Bug#1066269: fixed in autolog 0.42.1-1
has caused the Debian Bug report #1066269,
regarding autolog: FTBFS: autolog.c:613:9: error: implicit declaration of 
function ‘re_comp’; did you mean ‘regcomp’? 
[-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.)


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

Hi,

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

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

Relevant part (hopefully):
> cc -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 -Wl,-z,relro -Wl,-z,now -o autolog autolog.c
> autolog.c: In function ‘check_utmp’:
> autolog.c:320:38: warning: passing argument 1 of ‘ctime’ from incompatible 
> pointer type [-Wincompatible-pointer-types]
>   320 |ctime(>ut_time));
>   |  ^
>   |  |
>   |  int32_t * {aka int *}
> In file included from autolog.c:64:
> /usr/include/time.h:183:35: note: expected ‘const time_t *’ {aka ‘const long 
> int *’} but argument is of type ‘int32_t *’ {aka ‘int *’}
>   183 | extern char *ctime (const time_t *__timer) __THROW;
>   | ~~^~~
> autolog.c:346:30: warning: passing argument 1 of ‘ctime’ from incompatible 
> pointer type [-Wincompatible-pointer-types]
>   346 |ctime(>ut_time));
>   |  ^
>   |  |
>   |  int32_t * {aka int *}
> /usr/include/time.h:183:35: note: expected ‘const time_t *’ {aka ‘const long 
> int *’} but argument is of type ‘int32_t *’ {aka ‘int *’}
>   183 | extern char *ctime (const time_t *__timer) __THROW;
>   | ~~^~~
> autolog.c: In function ‘pat_match’:
> autolog.c:613:9: error: implicit declaration of function ‘re_comp’; did you 
> mean ‘regcomp’? [-Werror=implicit-function-declaration]
>   613 | re_comp(pattern);
>   | ^~~
>   | regcomp
> autolog.c:614:16: error: implicit declaration of function ‘re_exec’; did you 
> mean ‘regexec’? [-Werror=implicit-function-declaration]
>   614 | return re_exec(strg);
>   |^~~
>   |regexec
> autolog.c: In function ‘load_users’:
> autolog.c:441:9: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   441 | fscanf(f, "%d", );
>   | ^~
> autolog.c:451:17: warning: ignoring return value of ‘fscanf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   451 | fscanf(f, " %s %d %s %d %d %d %d",
>   | ^~
>   452 |userlst[userpos].Name,
>   |~~
>   453 |[userpos].UserID,
>   |~
>   454 |userlst[userpos].Device,
>   |
>   455 |[userpos].IdleTime,
>   |~~~
>   456 |[userpos].SessStrt,
>   |~~~
>   457 |[userpos].Ban_Ends,
>   |~~~
>   458 |[userpos].WarnEnds);
>   |~~~
> autolog.c: In function ‘get_PIDs’:
> autolog.c:839:9: warning: ignoring return value of ‘fgets’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   839 | fgets(iline, LINELEN, ps);   /* get header-line */
>

Processed: NMU pending for #1066136

[Debian Bug Tracking System]

Processing control commands:

> tags 1066136 + pending
Bug #1066136 [python3-xapian-haystack] python3-xapian-haystack: unusable on 
stable due to use of deprecated module django.utils.six
Added tag(s) pending.

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

Bug#1066136: NMU pending for #1066136

[Steinar H. Gunderson]

Control: tags 1066136 + pending

Hi,

I've prepared an NMU for python-xapian-haystack (versioned as
2.1.1-1+deb12u0.1) and uploaded it to DELAYED/14-day. (The unusually
long delay is since this is a stable upload.)

NMU diff is attached.

/* Steinar */
-- 
Homepage: https://www.sesse.net/
diff -Nru python-xapian-haystack-2.1.1/debian/changelog python-xapian-haystack-2.1.1/debian/changelog
--- python-xapian-haystack-2.1.1/debian/changelog	2021-10-19 22:10:20.0 +0200
+++ python-xapian-haystack-2.1.1/debian/changelog	2024-03-19 23:35:19.0 +0100
@@ -1,3 +1,12 @@
+python-xapian-haystack (2.1.1-1+deb12u0.1) bookworm; urgency=medium
+
+  * Non-maintainer upload, to stable.
+  * Remove dependency on the django.utils.six module, which no longer exists,
+causing the package to be completely broken. Patch by Ole Peder Brandtzæg,
+based on reducing a patch from upstream. (Closes: #1066136)
+
+ -- Steinar H. Gunderson   Tue, 19 Mar 2024 23:35:19 +0100
+
 python-xapian-haystack (2.1.1-1) unstable; urgency=low
 
   [ Debian Janitor ]
diff -Nru python-xapian-haystack-2.1.1/debian/patches/0002-Remove-dependency-on-six.patch python-xapian-haystack-2.1.1/debian/patches/0002-Remove-dependency-on-six.patch
--- python-xapian-haystack-2.1.1/debian/patches/0002-Remove-dependency-on-six.patch	1970-01-01 01:00:00.0 +0100
+++ python-xapian-haystack-2.1.1/debian/patches/0002-Remove-dependency-on-six.patch	2024-03-19 23:35:19.0 +0100
@@ -0,0 +1,32 @@
+Index: python-xapian-haystack-2.1.1/xapian_backend.py
+===
+--- python-xapian-haystack-2.1.1.orig/xapian_backend.py
 python-xapian-haystack-2.1.1/xapian_backend.py
+@@ -7,7 +7,6 @@ import re
+ import shutil
+ import sys
+ 
+-from django.utils import six
+ from django.conf import settings
+ from django.core.exceptions import ImproperlyConfigured
+ from django.utils.encoding import force_text
+@@ -346,7 +345,7 @@ class XapianSearchBackend(BaseSearchBack
+ def _get_ngram_lengths(value):
+ values = value.split()
+ for item in values:
+-for ngram_length in six.moves.range(NGRAM_MIN_LENGTH, NGRAM_MAX_LENGTH + 1):
++for ngram_length in range(NGRAM_MIN_LENGTH, NGRAM_MAX_LENGTH + 1):
+ yield item, ngram_length
+ 
+ for obj in iterable:
+@@ -356,8 +355,8 @@ class XapianSearchBackend(BaseSearchBack
+ def ngram_terms(value):
+ for item, length in _get_ngram_lengths(value):
+ item_length = len(item)
+-for start in six.moves.range(0, item_length - length + 1):
+-for size in six.moves.range(length, length + 1):
++for start in range(0, item_length - length + 1):
++for size in range(length, length + 1):
+ end = start + size
+ if end > item_length:
+ continue
diff -Nru python-xapian-haystack-2.1.1/debian/patches/series python-xapian-haystack-2.1.1/debian/patches/series
--- python-xapian-haystack-2.1.1/debian/patches/series	2021-10-19 22:10:20.0 +0200
+++ python-xapian-haystack-2.1.1/debian/patches/series	2024-03-19 23:35:19.0 +0100
@@ -1 +1,2 @@
 0001-Use-io.open-to-read-UTF-8-encoded-README-file.patch
+0002-Remove-dependency-on-six.patch

Bug#1067192: gtk-d: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Simon McVittie]

On Tue, 19 Mar 2024 at 22:55:31 +0100, Matthias Klumpp wrote:
> Am Di., 19. März 2024 um 22:25 Uhr schrieb Simon McVittie :
> > Yes, the library is renamed on all architectures. (On architectures where
> > the ABI didn't actually break, like amd64, it Provides the old name.)
>
> So, in that case the most straightforward way to fix this would just
> be to rename the dependency to libgtk-3-0t64?

Yes, that'll be the simplest approach.

smcv

Bug#1067144: [3dprinter-general] Bug#1067144: uranium: missing depend on python3-all for autopkgtest

[Gregor Riepl]

Hi Timo,


your package has an autopkgtest regression due to changes in NumPy.
The python3-numpy package no longer depends on all supported Python
versions. You need to depend on python3-all if you want to run your
tests against all supported Python releases.


Can you elaborate why this dependency is needed in the first place?

It's the first time I heard that a python3 module package needs such an 
explicit dependency outside the Build-Depends.


I also don't think it makes sense to always install python3-all on every 
system that installs python3-uranium, just because autopkgtest needs it.
Shouldn't autopkgtest figure out by itself that this package is needed 
to run tests against all python versions?


(and if this is about Build-Depends - src:uranium has depended on 
python3-all since it existed)


Regards,
Gregor

Bug#1067197: xserver-xorg-video-nouveau ftbfs

[Sven Joachim]

Control: severity -1 normal

Am 19.03.2024 um 22:15 schrieb Helge Deller:

> Source: xserver-xorg-video-nouveau
> Version: 1:1.0.17-3
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: del...@debian.org
>
> Failure can be seen on hppa architecture, but I assume it will show up on 
> armel too:

I don't think so, it has already been built on armhf.

> https://buildd.debian.org/status/fetch.php?pkg=xserver-xorg-video-nouveau=hppa=1%3A1.0.17-3=1710537593=0
>
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src
> -I.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
> -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/xorg
> -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri
> -I/usr/include/libdrm -I/usr/include/libdrm
> -I/usr/include/libdrm/nouveau -I/usr/include/libdrm -g -O2
> -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -Wformat -Werror=format-security
> -Wall -I/usr/include/xorg -fvisibility=hidden -I/usr/include/pixman-1
> -I/usr/include/X11/dri -I/usr/include/libdrm -c ../../src/nv_shadow.c
> -fPIC -DPIC -o .libs/nv_shadow.o
> ../../src/nv_driver.c: In function ‘NVScreenInit’:
> ../../src/nv_driver.c:1451:23: error: implicit declaration of function
> ‘wfbScreenInit’; did you mean ‘fbScreenInit’?
> [-Werror=implicit-function-declaration]
>  1451 | ret = wfbScreenInit(pScreen, FBStart, pScrn->virtualX,
>   |   ^
>   |   fbScreenInit
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:674: nv_driver.lo] Error 1

The problem is that the hppa and powerpc buildds have an outdated
version of dpkg-dev installed, although a newer one has been available
for over a week.  I could and maybe should add dpkg-dev (>= 1.22.6) to
Build-Depends, but that is one more thing that needs to be reverted when
#1066968 gets fixed.

Cheers,
   Sven

Processed: Re: Bug#1067197: xserver-xorg-video-nouveau ftbfs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1067197 [src:xserver-xorg-video-nouveau] xserver-xorg-video-nouveau ftbfs
Severity set to 'normal' from 'serious'

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

Bug#1067192: gtk-d: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Matthias Klumpp]

Am Di., 19. März 2024 um 22:25 Uhr schrieb Simon McVittie :
>
> On Tue, 19 Mar 2024 at 22:14:12 +0100, Matthias Klumpp wrote:
> > Am Di., 19. März 2024 um 21:42 Uhr schrieb Simon McVittie :
> > > libgtkd-3-0 has a hard-coded dependency on libgtk-3-0, which will need
> > > to be replaced by libgtk-3-0t64 after checking that the functions that
> > > interact with time_t (methods of GtkRecentInfo) are handled correctly.
> >
> > Will this be the new name on all platforms?
>
> Yes, the library is renamed on all architectures. (On architectures where
> the ABI didn't actually break, like amd64, it Provides the old name.)
>
> The same is true for essentially all of the libraries involved in this
> transition: there are hundreds of them.
>
> > Annoyingly, libgtkd does not depend on
> > libgtk properly on its own via linking it, and instead will dlopen it
> > at runtime.
>
> One way I've sometimes seen this handled is by making a list of the
> SONAMEs that will be dlopen'd, linking them into a dummy C executable
> with -Wl,--no-as-needed, and letting dpkg-shlibdeps inspect that executable
> and generate dependencies.

So, in that case the most straightforward way to fix this would just
be to rename the dependency to libgtk-3-0t64?
(making a mock library is possible, but I'd prefer the easiest way in
this case, as it's just one library...)

Bug#1067189: marked as done (syncthing-gtk: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 21:43:23 +
with message-id 
and subject line Bug#1067189: fixed in syncthing-gtk 
0.9.4.4+ds+git20221205+12a9702d29ab-3
has caused the Debian Bug report #1067189,
regarding syncthing-gtk: hard-coded dependency on libgtk-3-0 will become 
uninstallable on armel/armhf
to be marked as done.

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

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


-- 
1067189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: syncthing-gtk
Version: 0.9.4.4+ds+git20221205+12a9702d29ab-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1

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

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

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

More information about this transition is available on
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: syncthing-gtk
Source-Version: 0.9.4.4+ds+git20221205+12a9702d29ab-3
Done: Andrej Shadura 

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

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

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated syncthing-gtk 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: Tue, 19 Mar 2024 22:07:54 +0100
Source: syncthing-gtk
Architecture: source
Version: 0.9.4.4+ds+git20221205+12a9702d29ab-3
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 1067189
Changes:
 syncthing-gtk (0.9.4.4+ds+git20221205+12a9702d29ab-3) unstable; urgency=medium
 .
   * Remove explicit dependency on libgtk-3-0 (Closes: #1067189).
   * Set Rules-Requires-Root: no.
Checksums-Sha1:
 5b13abab732468d2fd11d1e3c6e2445c264d56c4 1733 
syncthing-gtk_0.9.4.4+ds+git20221205+12a9702d29ab-3.dsc
 7c74e259d8a526cfe81d671d468b2b17b4f75818 3688 
syncthing-gtk_0.9.4.4+ds+git20221205+12a9702d29ab-3.debian.tar.xz
Checksums-Sha256:
 2309aa026fdcf9ce23574cc028ddd84c8513b9a010948cefac3d5f44a96cba30 1733 
syncthing-gtk_0.9.4.4+ds+git20221205+12a9702d29ab-3.dsc
 97d155351b61fbf1a377a0f328afb94b51d15125e7b3bd984d0389350ed75d3e 3688 
syncthing-gtk_0.9.4.4+ds+git20221205+12a9702d29ab-3.debian.tar.xz
Files:
 9b2fb920592320800a785ab7fae6d015 1733 net optional 
syncthing-gtk_0.9.4.4+ds+git20221205+12a9702d29ab-3.dsc
 4a8b18538fc913785720a43eab5dc14b 3688 net optional 
syncthing-gtk_0.9.4.4+ds+git20221205+12a9702d29ab-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCZfn+wwAKCRDoRGtKyMdy
YVZPAP9ViV2p7Li5tc39YXfJjgLfH5l683mOjlwHUjiLhzRfRQD/R6fCD/u58+mV
vBU8awoYMgSDFww2Edi4inrlYyhjxgQ=
=2npp
-END PGP SIGNATURE-



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

Processed: libgts-0.7-5t64: emits shlib dependencies on libgts-0.7-5

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:graphviz libgvc6
Bug #1067198 [libgts-0.7-5t64] libgts-0.7-5t64: emits shlib dependencies on 
libgts-0.7-5
Added indication that 1067198 affects src:graphviz and libgvc6

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

Bug#1067198: libgts-0.7-5t64: emits shlib dependencies on libgts-0.7-5

[Thorsten Glaser]

Package: libgts-0.7-5t64
Version: 0.7.6+darcs121130-5.1
Severity: grave
Justification: uninstallable
X-Debbugs-Cc: t...@mirbsd.de, vor...@debian.org
Control: affects -1 src:graphviz libgvc6

When building against libgts-0.7-5t64, the generated packages
get a shlib:Depends of 'libgts-0.7-5 (>= 0.7.6)' instead of
the expected libgts-0.7-5t64.

This is probably because the shlibs…

| libgts-0.7 5 libgts-0.7-5t64 (>= 0.7.6+darcs121130)

… and symbols…

| libgts-0.7.so.5 libgts-0.7-5 #MINVER#
|  gts_allow_floating_edges@Base 0.7.6
[…]

… control files disagree.

This is a t64 transition showstopper (vala B-D graphviz).

Bug#1067192: gtk-d: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Simon McVittie]

On Tue, 19 Mar 2024 at 22:14:12 +0100, Matthias Klumpp wrote:
> Am Di., 19. März 2024 um 21:42 Uhr schrieb Simon McVittie :
> > libgtkd-3-0 has a hard-coded dependency on libgtk-3-0, which will need
> > to be replaced by libgtk-3-0t64 after checking that the functions that
> > interact with time_t (methods of GtkRecentInfo) are handled correctly.
> 
> Will this be the new name on all platforms?

Yes, the library is renamed on all architectures. (On architectures where
the ABI didn't actually break, like amd64, it Provides the old name.)

The same is true for essentially all of the libraries involved in this
transition: there are hundreds of them.

> Annoyingly, libgtkd does not depend on
> libgtk properly on its own via linking it, and instead will dlopen it
> at runtime.

One way I've sometimes seen this handled is by making a list of the
SONAMEs that will be dlopen'd, linking them into a dummy C executable
with -Wl,--no-as-needed, and letting dpkg-shlibdeps inspect that executable
and generate dependencies.

smcv

Bug#1067197: xserver-xorg-video-nouveau ftbfs

[Helge Deller]

Source: xserver-xorg-video-nouveau
Version: 1:1.0.17-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: del...@debian.org

Failure can be seen on hppa architecture, but I assume it will show up on armel 
too:

https://buildd.debian.org/status/fetch.php?pkg=xserver-xorg-video-nouveau=hppa=1%3A1.0.17-3=1710537593=0

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/xorg 
-fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm 
-I/usr/include/libdrm -I/usr/include/libdrm/nouveau -I/usr/include/libdrm -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-Wformat -Werror=format-security -Wall -I/usr/include/xorg -fvisibility=hidden 
-I/usr/include/pixman-1 -I/usr/include/X11/dri -I/usr/include/libdrm -c 
../../src/nv_shadow.c  -fPIC -DPIC -o .libs/nv_shadow.o
../../src/nv_driver.c: In function ‘NVScreenInit’:
../../src/nv_driver.c:1451:23: error: implicit declaration of function 
‘wfbScreenInit’; did you mean ‘fbScreenInit’? 
[-Werror=implicit-function-declaration]
 1451 | ret = wfbScreenInit(pScreen, FBStart, pScrn->virtualX,
  |   ^
  |   fbScreenInit
cc1: some warnings being treated as errors
make[3]: *** [Makefile:674: nv_driver.lo] Error 1

Bug#1067192: gtk-d: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Matthias Klumpp]

Hi Simon!

Am Di., 19. März 2024 um 21:42 Uhr schrieb Simon McVittie :
> libgtkd-3-0 has a hard-coded dependency on libgtk-3-0, which will need
> to be replaced by libgtk-3-0t64 after checking that the functions that
> interact with time_t (methods of GtkRecentInfo) are handled correctly.

Will this be the new name on all platforms? If not, can we detect the
name automatically somehow? Annoyingly, libgtkd does not depend on
libgtk properly on its own via linking it, and instead will dlopen it
at runtime. So that dependency has to be added manually for the Debian
package.

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#1063879: marked as done (linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile against linux-image 6.1.0-18)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 21:08:38 +
with message-id 
and subject line Bug#1062932: fixed in nvidia-graphics-drivers 530.41.03-4
has caused the Debian Bug report #1062932,
regarding linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile 
against linux-image 6.1.0-18
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.)


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

Package: src:linux
Version: 6.1.76-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the 
past)


Dear Maintainer,

Upgrading from linux-image 6.1.0-17 to 6.1.0-18 fails to complete due to 
nvidia

compile error.

ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_lock'
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_unlock'

* What led up to the situation?
routine kernel upgrade using meta package linux-image-amd64
* What exactly did you do (or not do) that was effective (or
ineffective)?
used synaptic. Also attempted on commandline
$ apt install linux-image-amd64
* What was the outcome of this action?
Cleaning build area...
env NV_VERBOSE=1 make -j8 modules
KERNEL_UNAME=6.1.0-18-amd64..(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more
information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
...
dpkg: error processing package linux-image-amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-image-6.1.0-18-amd64
linux-headers-6.1.0-18-amd64
linux-image-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
* What outcome did you expect instead?
kernel upgraded


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: HP
product_name: HP Pavilion Laptop 15-cs3xxx
product_version: Type1ProductConfigId
chassis_vendor: HP
chassis_version: Chassis Version
bios_vendor: Insyde
bios_version: F.21
board_vendor: HP
board_name: 86E2
board_version: 95.36

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Ice Lake-LP Processor Host 
Bridge/DRAM Registers [8086:8a12] (rev 03)
Subsystem: Hewlett-Packard Company Ice Lake-LP Processor Host 
Bridge/DRAM Registers [103c:86e2]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Latency: 0
IOMMU group: 1
Capabilities: 
Kernel driver in use: icl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Plus 
Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller])

Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86e2]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 139
IOMMU group: 0
Region 0: Memory at 601600 (64-bit, non-prefetchable) [size=16M]
Region 2: Memory at 40 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at 8000 [size=64]
Expansion ROM at 000c [virtual] [disabled] [size=128K]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Processor 
Power and Thermal Controller [8086:8a03] (rev 03)
Subsystem: Hewlett-Packard Company Processor Power and Thermal 
Controller [103c:86e2]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Latency: 0
Interrupt: pin A routed to IRQ 16
IOMMU group: 2
Region 0: Memory at 601710 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device_pci_legacy

00:14.0 USB controller [0c03]: Intel Corporation Ice Lake-LP USB 3.1 
xHCI Host Controller [8086:34ed] (rev 30) (prog-if 30 [XHCI])
Subsystem: Hewlett-Packard Company Ice Lake-LP USB 3.1 xHCI Host 
Controller [103c:86e2]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Latency: 0
Interrupt: pin A routed to IRQ 127

Bug#1065428: marked as done (librocsolver-doc: missing Breaks+Replaces: librocsolver-dev (<< 5.5.1-5~))

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 15:04:41 -0600
with message-id 
and subject line Re: librocsolver-doc: missing Breaks+Replaces
has caused the Debian Bug report #1065428,
regarding librocsolver-doc: missing Breaks+Replaces: librocsolver-dev (<< 
5.5.1-5~)
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.)


-- 
1065428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librocsolver-doc
Version: 5.5.1-5~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts file-conflict

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid' installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../librocsolver-doc_5.5.1-5~exp1_all.deb ...
  Unpacking librocsolver-doc (5.5.1-5~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/librocsolver-doc_5.5.1-5~exp1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/librocsolver-dev/examples/example_basic.c', which is also in 
package librocsolver-dev 5.5.1-4
  Errors were encountered while processing:
   /var/cache/apt/archives/librocsolver-doc_5.5.1-5~exp1_all.deb


cheers,

Andreas


librocsolver-dev=5.5.1-4_librocsolver-doc=5.5.1-5~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---

Version: 5.5.1-5

Breaks+Replaces has been added to librocsolver-doc in the package 
uploaded to unstable.


Sincerely,
Cory Bloor--- End Message ---

Bug#1063729: marked as done (Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 21:08:38 +
with message-id 
and subject line Bug#1062932: fixed in nvidia-graphics-drivers 530.41.03-4
has caused the Debian Bug report #1062932,
regarding Kernel panic after update from Debian 12.4 to 12.5 in command line 
and reboot
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.)


-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-6.1.0-18-amd64
Version: 6.1.76-1: amd64
Severity: critical

Bug Description:

Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot.
Look "Kernel panic after update.txt" in attachment for details.
Look message booting display in attachment for more details.
Please correct this urgently !!!
Regards.

Philipperoot@station:~# apt update && apt dist-upgrade
Atteint :1 https://security.debian.org/debian-security bookworm-security 
InRelease
Atteint :2 http://ppa.launchpad.net/vincent-vandevyvre/vvv/ubuntu focal 
InRelease
Atteint :3 https://deb.debian.org/debian bookworm InRelease
Atteint :4 https://deb.debian.org/debian bookworm-updates InRelease
Atteint :5 https://deb.debian.org/debian-security bookworm-security InRelease
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait  
Tous les paquets sont à jour.
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait  
Calcul de la mise à jour... Fait
Le paquet suivant a été installé automatiquement et n'est plus nécessaire :
  linux-headers-6.1.0-16-common
Veuillez utiliser « apt autoremove » pour le supprimer.
Les paquets suivants seront ENLEVÉS :
  linux-headers-6.1.0-16-amd64 linux-image-6.1.0-16-amd64
0 mis à jour, 0 nouvellement installés, 2 à enlever et 0 non mis à jour.
4 partiellement installés ou enlevés.
Après cette opération, 412 Mo d'espace disque seront libérés.
Souhaitez-vous continuer ? [O/n] o
(Lecture de la base de données... 416726 fichiers et répertoires déjà installés.
)
Suppression de linux-headers-6.1.0-16-amd64 (6.1.67-1) ...
Suppression de linux-image-6.1.0-16-amd64 (6.1.67-1) ...
/etc/kernel/prerm.d/dkms:
dkms: removing: nvidia-current 525.147.05 (6.1.0-16-amd64) (x86_64)
Module nvidia-current-525.147.05 for kernel 6.1.0-16-amd64 (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

nvidia-current.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

nvidia-current-modeset.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

nvidia-current-drm.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

nvidia-current-uvm.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

nvidia-current-peermem.ko:
 - Uninstallation
   - Deleting from: /lib/modules/6.1.0-16-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.
depmod...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-16-amd64
/etc/kernel/postrm.d/zz-update-grub:
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-6.1.0-18-amd64
Found linux image: /boot/vmlinuz-6.1.0-17-amd64
Found initrd image: /boot/initrd.img-6.1.0-17-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot 
entries.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
Paramétrage de linux-image-6.1.0-18-amd64 (6.1.76-1) ...
I: /initrd.img 

Bug#1063689: marked as done (linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 21:08:38 +
with message-id 
and subject line Bug#1062932: fixed in nvidia-graphics-drivers 530.41.03-4
has caused the Debian Bug report #1062932,
regarding linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU
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.)


-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.1.76-1
Severity: important
X-Debbugs-Cc: s...@weilnetz.de

Dear Maintainer,

on a server with NVIDIA GPU, nvidia-kernel-dkms fails to build the required 
kernel modules
after a kernel update with linux-image-6.1.0-18-amd64 and 
linux-headers-6.1.0-18-amd64.

It looks like the new kernel includes changes that cause a conflict between the 
non-GPL
NVIDIA code and two GPL'ed functions which are now used, but were not used with 
the previous
kernel from Debian stable.

Best regards
Stefan Weil

-- Package-specific info:
** Model information
sys_vendor: primeLine Solutions
product_name: egino s-Series egino BTO
product_version: 0123456789
chassis_vendor: Supermicro
chassis_version: 0123456789
bios_vendor: American Megatrends Inc.
bios_version: 2.1
board_vendor: Supermicro
board_name: H11SSL-i
board_version: 2.00

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
Root Complex [1022:1480]
Subsystem: Super Micro Computer Inc Starship/Matisse Root Complex 
[15d9:1a03]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 61)
Subsystem: Super Micro Computer Inc H12SSL-i [15d9:790b]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 

01:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse PTDMA [1022:1498]
Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PTDMA 
[1022:1498]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

02:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. 
[AMD] Starship/Matisse Reserved SPP [1022:1485]
Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved 
SPP [1022:1485]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

02:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse PTDMA [1022:1498]
Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PTDMA 
[1022:1498]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

02:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 
3.0 Host Controller [1022:148c] (prog-if 30 [XHCI])
Subsystem: Super Micro Computer Inc H12SSL-i 

Bug#1063717: marked as done (cuda-drivers: Build of module nvidia.ko fails)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 21:08:38 +
with message-id 
and subject line Bug#1062932: fixed in nvidia-graphics-drivers 530.41.03-4
has caused the Debian Bug report #1062932,
regarding cuda-drivers: Build of module nvidia.ko fails
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.)


-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cuda-drivers
Version: 545.23.08-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: matte.mb2006.9...@gmail.com

Dear Maintainer,
Compiling the cuda driver for kernel 6.1.0-18 fails with this error:
"
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_lock'
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'__rcu_read_unlock'
"

-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-17-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 cuda-drivers depends on:
ii  cuda-drivers-545  545.23.08-1

cuda-drivers recommends no packages.

cuda-drivers suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 530.41.03-4
Done: Andreas Beckmann 

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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: Tue, 19 Mar 2024 21:02:39 +0100
Source: nvidia-graphics-drivers
Architecture: source
Version: 530.41.03-4
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1062932 1063363
Changes:
 nvidia-graphics-drivers (530.41.03-4) unstable; urgency=medium
 .
   * Merge changes from 525.147.05-10.
   * Backport drm_unlocked_ioctl_flag_present changes from 470.239.06 to fix
 kernel module build for Linux 6.8.
   * Backport screen_info changes from 470.182.03 and 470.239.06 to fix kernel
 module build for Linux 6.7 on arm64.
   * Apply pfn_valid patch from gentoo to fix kernel module build for
 Linux 6.1.76, 6.6.15, 6.7.3, 6.8.  (Closes: #1063363, #1062932)
   * Backport drm_gem_prime_handle_to_fd changes from 470.223.02 to fix kernel
 module build for Linux 6.6.
   * Restrict watch file to releases from the 530.xx new feature branch.
   * Upload to unstable.
Checksums-Sha1:
 f46387fd47e9c92230cf4a6f5387a3624b42c0af 7449 
nvidia-graphics-drivers_530.41.03-4.dsc
 5fd05345e025cb281e9cb1a99ee66c4a0100fa8b 343127210 
nvidia-graphics-drivers_530.41.03.orig-amd64.tar.gz
 317229a79089eff0be1ebd375ebb49c515c3a80f 218368435 
nvidia-graphics-drivers_530.41.03.orig-arm64.tar.gz
 09687633d73b184ab16c83f87809a9831548fcff 139 
nvidia-graphics-drivers_530.41.03.orig.tar.gz
 ac2c911ba0685de4e67dcd28388f1d67a89dedfb 229024 
nvidia-graphics-drivers_530.41.03-4.debian.tar.xz
 0947296f063dc0b70412c211f9a6a5c9035eb2de 5726 
nvidia-graphics-drivers_530.41.03-4_source.buildinfo
Checksums-Sha256:
 ee890eb19a1944016659a0e76a42a3b6037c684548a5f7b55b8b271f6b93c5ad 7449 
nvidia-graphics-drivers_530.41.03-4.dsc
 a3c22b98b11e103d2d080f57b5250347556ec835944379c2aa8d180f556f5d53 343127210 
nvidia-graphics-drivers_530.41.03.orig-amd64.tar.gz
 4b5ea4053556347454625d6762661736b2de0231811ca1cb6ad7487ec9f6d9c4 218368435 
nvidia-graphics-drivers_530.41.03.orig-arm64.tar.gz
 3892a9c970df8d3ae6feccdad017445b4cb1c70dda314da1fb8320e40df6d5e5 139 
nvidia-graphics-drivers_530.41.03.orig.tar.gz
 

Bug#1063713: marked as done (linux-image-6.1.0-18-amd64: apt fails to install the kernel version, reports problem with building modules)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 21:08:38 +
with message-id 
and subject line Bug#1062932: fixed in nvidia-graphics-drivers 530.41.03-4
has caused the Debian Bug report #1062932,
regarding linux-image-6.1.0-18-amd64: apt fails to install the kernel version, 
reports problem with building modules
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.)


-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.1.76-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: gnomedeu...@gmail.com


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUSTeK COMPUTER INC.
product_name: VivoBook S13 X330FN_S330FN
product_version: 1.0   
chassis_vendor: ASUSTeK COMPUTER INC.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: X330FN.304
board_vendor: ASUSTeK COMPUTER INC.
board_name: X330FN
board_version: 1.0   

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Coffee Lake HOST and DRAM 
Controller [8086:3e34] (rev 0c)
Subsystem: ASUSTeK Computer Inc. Coffee Lake HOST and DRAM Controller 
[1043:1631]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation WhiskeyLake-U GT2 
[UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller])
DeviceName: VGA
Subsystem: ASUSTeK Computer Inc. WhiskeyLake-U GT2 [UHD Graphics 620] 
[1043:1d1e]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/E3-1500 v5/6th Gen 
Core Processor Thermal Subsystem [1043:1631]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device_pci_legacy

00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / 
E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/v6 / E3-1500 v5 / 
6th/7th/8th Gen Core Processor Gaussian Mixture Model [1043:1631]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Point-LP 
Thermal Controller [8086:9df9] (rev 30)
Subsystem: ASUSTeK Computer Inc. Cannon Point-LP Thermal Controller 
[1043:1631]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal

00:14.0 USB controller [0c03]: Intel Corporation Cannon Point-LP USB 3.1 xHCI 
Controller [8086:9ded] (rev 30) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Cannon Point-LP USB 3.1 xHCI 
Controller [1043:201f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM 
[8086:9def] (rev 30)
Subsystem: Intel Corporation Cannon Point-LP Shared SRAM [8086:7270]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:14.3 Network controller [0280]: Intel Corporation Cannon Point-LP CNVi 
[Wireless-AC] [8086:9df0] (rev 30)
DeviceName: WLAN
Subsystem: 

Bug#1063668: marked as done (linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 21:08:38 +
with message-id 
and subject line Bug#1062932: fixed in nvidia-graphics-drivers 530.41.03-4
has caused the Debian Bug report #1062932,
regarding linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues
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.)


-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-6.1.0-18-amd64
Version: linux-image-6.1.0-18
Severity: important
X-Debbugs-Cc: joshua.beckwith@gmail.com

Dear Maintainer,

I have noticed some issues pertaining to both packages, namely linux-
image-6.1.0-18-amd64 & linux-headers-6.1.0-18-amd64-common. The repository
Nvidia Driver 525.147.05-4 fails to build the module for this Kernel with exit
code: 10.

I hope this isn't too much of a problem.

Kind regards

Joshua Beckwith



-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages linux-image-6.1.0-18-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod30+20221128-1
ii  linux-base  4.9

Versions of packages linux-image-6.1.0-18-amd64 recommends:
ii  apparmor 3.0.8-3
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-6.1.0-18-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.06-13+deb12u1
pn  linux-doc-6.1   
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 530.41.03-4
Done: Andreas Beckmann 

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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: Tue, 19 Mar 2024 21:02:39 +0100
Source: nvidia-graphics-drivers
Architecture: source
Version: 530.41.03-4
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1062932 1063363
Changes:
 nvidia-graphics-drivers (530.41.03-4) unstable; urgency=medium
 .
   * Merge changes from 525.147.05-10.
   * Backport drm_unlocked_ioctl_flag_present changes from 470.239.06 to fix
 kernel module build for Linux 6.8.
   * Backport screen_info changes from 470.182.03 and 470.239.06 to fix kernel
 module build for Linux 6.7 on arm64.
   * Apply pfn_valid patch from gentoo to fix kernel module build for
 Linux 6.1.76, 6.6.15, 6.7.3, 6.8.  (Closes: #1063363, #1062932)
   * Backport drm_gem_prime_handle_to_fd changes from 470.223.02 to fix kernel
 module build for Linux 6.6.
   * Restrict watch file to releases from the 530.xx new feature branch.
   * Upload to unstable.
Checksums-Sha1:
 f46387fd47e9c92230cf4a6f5387a3624b42c0af 7449 
nvidia-graphics-drivers_530.41.03-4.dsc
 5fd05345e025cb281e9cb1a99ee66c4a0100fa8b 343127210 
nvidia-graphics-drivers_530.41.03.orig-amd64.tar.gz
 317229a79089eff0be1ebd375ebb49c515c3a80f 218368435 
nvidia-graphics-drivers_530.41.03.orig-arm64.tar.gz
 09687633d73b184ab16c83f87809a9831548fcff 139 
nvidia-graphics-drivers_530.41.03.orig.tar.gz
 ac2c911ba0685de4e67dcd28388f1d67a89dedfb 229024 
nvidia-graphics-drivers_530.41.03-4.debian.tar.xz
 0947296f063dc0b70412c211f9a6a5c9035eb2de 5726 
nvidia-graphics-drivers_530.41.03-4_source.buildinfo
Checksums-Sha256:
 ee890eb19a1944016659a0e76a42a3b6037c684548a5f7b55b8b271f6b93c5ad 7449 
nvidia-graphics-drivers_530.41.03-4.dsc
 a3c22b98b11e103d2d080f57b5250347556ec835944379c2aa8d180f556f5d53 

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

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 21:06:26 +
with message-id 
and subject line Bug#1067193: fixed in meld 3.22.1-2
has caused the Debian Bug report #1067193,
regarding meld: hard-coded dependency on libgtk-3-0 will become uninstallable 
on armel/armhf
to be marked as done.

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

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


-- 
1067193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: meld
Version: 3.22.1-1
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1

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

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

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

More information about this transition is available on
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: meld
Source-Version: 3.22.1-2
Done: Jeremy Bícha 

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated meld 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: Tue, 19 Mar 2024 16:52:04 -0400
Source: meld
Built-For-Profiles: noudeb
Architecture: source
Version: 3.22.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1067193
Changes:
 meld (3.22.1-2) unstable; urgency=medium
 .
   * Replace Depends: libgtk-3-0 with gir1.2-gtk-3.0 (Closes: #1067193)
Checksums-Sha1:
 589228d5742294ab00cf01a6ecb2d605605afd3c 2082 meld_3.22.1-2.dsc
 ec2fb5508f2e5dae76945b4f81af51d24e9726ac 12824 meld_3.22.1-2.debian.tar.xz
 b009554d37fe6031822b5dcb525d8f68f1090601 18134 meld_3.22.1-2_source.buildinfo
Checksums-Sha256:
 1d6ebb2bffa48fb40909b44949e2d26e93d87dee1654d2516e9487729f6daec7 2082 
meld_3.22.1-2.dsc
 350e9089acfa51b8d0b462b3873dbde7c8c713eb7d9325fbf5fc9680a516a65d 12824 
meld_3.22.1-2.debian.tar.xz
 a5a27f9e01c95cab82cd69ce8c5757ecc6dd377365117f1ce9ab6776c3aa47fc 18134 
meld_3.22.1-2_source.buildinfo
Files:
 40b116df971d2cda9b9712cb2379674f 2082 gnome optional meld_3.22.1-2.dsc
 a1eebfd004058cc02ceccf4a27bf7820 12824 gnome optional 
meld_3.22.1-2.debian.tar.xz
 4ff90c3f7cf635f03a6dbe50aecfc3f5 18134 gnome optional 
meld_3.22.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmX5+xEACgkQ5mx3Wuv+
bH0IbhAArOJN8H8a/60j/YU+TnSz1GiVCh5uBn/jhKxwjckW5hqK59JzMQwwylES
cKtp23xrbLADlLkrV1oGRp8IX1ezc4cE0Y+oOAce+Z/mC0wcJ+lej1EPsQmpxic8
b26/a7MQMTmGvqu0ptjQglLORixRd7DrAKQ6KqwnvHQeimQ+82DPwrrL/B3h7u5N
/IZMdqnJyPYUNjiwL/nrKxHhOykOZLC2wtvixsvw2Izs/6u7N6TkzHTkNiev+43C
aEQrJrywg7gKh5aLRuJkZgHWO1HufycwKiVsa6w63sowSoM70DNwGuff/AT4K6F5
9HwJpK6FmFZwbbCgY7kq9FUqapUiger0YahWDJ7bUi2uZ5ToWQBqxnWQbPwPNhfx
bFb1QLvC7HE1J4Pdh0XUE9DNTTSvTmAw0BvVOLl1ximF6V0SxJYAOrtnsV1nBGq7
q2VKwZvElEf0mWJVoib6nQJPAONfAYkIv/DhzpJ5pcQY5V2ji6CvLXbQwRakdv/Y
xfYRc+ipEuJOiXlQKZ8NJRkgaLd/h+fr2A+sfVOKbi40+j4H3qrpCS4mm4foMiD9
WDdEWcgHEH8lhsKlJnXL/ITJszMQjMMqAYjt3/EH11D3HS6G4E0iKFDqWsC8bSbP
JLpmU8gjdJhQIr799TwED4i8+JQiqVY4BdsbJRtBNxZ7PI4klso=
=z5JA
-END PGP SIGNATURE-



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

Processed: Bug#1067193 marked as pending in meld

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067193 [meld] meld: hard-coded dependency on libgtk-3-0 will become 
uninstallable on armel/armhf
Added tag(s) pending.

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

Bug#1067193: marked as pending in meld

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1067193 in meld 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/gnome-team/meld/-/commit/60c41f4e96ec776b260c2b72575382efc0591595


Replace Depends: libgtk-3-0 with gir1.2-gtk-3.0

Closes: #1067193


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067193

Bug#1064967: fontforge DSA (was: Re: Bug#1064967: fontforge: diff for NMU version 1:20230101~dfsg-1.1)

[Salvatore Bonaccorso]

Hi Adrian,

On Sat, Mar 16, 2024 at 12:12:01AM +0200, Adrian Bunk wrote:
> On Wed, Mar 13, 2024 at 08:39:47PM +0100, Salvatore Bonaccorso wrote:
> > Hi Adrian,
> 
> Hi Salvatore,
> 
> > On Fri, Mar 08, 2024 at 02:03:55AM +0200, Adrian Bunk wrote:
> > > Control: tags 1064967 + patch
> > > Control: tags 1064967 + pending
> > > 
> > > Dear maintainer,
> > > 
> > > I've prepared an NMU for fontforge (versioned as 1:20230101~dfsg-1.1) and
> > > uploaded it to DELAYED/2. Please feel free to tell me if I should cancel 
> > > it.
> > > 
> > > @Security team:
> > > If wanted, I could afterwards also prepare (pu or DSA) updates for 
> > > bookworm and bullseye.
> > 
> > We came to the conclusion that it warrants a DSA. Could you prepare
> > debdiffs for bookworm-security and bulseye-security?
> 
> the debdiffs are attached.
> 
> Tested on both releases with the PoCs from [1] and that opening a normal 
> compressed font still works.

DSA for your work released.

Thanks for your contribution!

Regards,
Salvatore

Processed: closing 1037802

[Debian Bug Tracking System]

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

> close 1037802 0.12.0-1
Bug #1037802 [src:openfpgaloader] openfpgaloader: ftbfs with GCC-13
Marked as fixed in versions openfpgaloader/0.12.0-1.
Bug #1037802 [src:openfpgaloader] openfpgaloader: ftbfs with GCC-13
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1065951: vde: FTBFS on arm{el,hf}: /tmp/ccwOo5J4.s:341: Error: symbol `open64' is already defined

[Michael Hudson-Doyle]

Package: vde2
Version: 2.3.2+r586-9.1
Followup-For: Bug #1065951
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
X-Debbugs-Cc: michael.hud...@ubuntu.com
Control: tags -1 patch

Dear Maintainer,

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

  * Undefine _FILE_OFFSET_BITS and _TIME_BITS in libvdetap.c so the library's
interposition of open/open64 still works.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-25-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru vde2-2.3.2+r586/debian/patches/interposition-vs-lfs.patch 
vde2-2.3.2+r586/debian/patches/interposition-vs-lfs.patch
--- vde2-2.3.2+r586/debian/patches/interposition-vs-lfs.patch   1970-01-01 
12:00:00.0 +1200
+++ vde2-2.3.2+r586/debian/patches/interposition-vs-lfs.patch   2024-03-20 
09:33:55.0 +1300
@@ -0,0 +1,22 @@
+Description: Undo lfs/time64 defines in libvdetap.c
+ Building with these macros defines interferes with this files attempt to
+ interpose both open and open64
+Author: Michael Hudson-Doyle 
+Forwarded: no
+Last-Update: 2024-03-20
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/vdetaplib/libvdetap.c
 b/src/vdetaplib/libvdetap.c
+@@ -1,6 +1,11 @@
+ /* Copyright 2004 Renzo Davoli
+  * Reseased under the GPLv2 */
+ 
++/* Building with these macros defines interferes with this files attempt to
++   interpose both open and open64 */
++#undef _FILE_OFFSET_BITS
++#undef _TIME_BITS
++
+ #define _GNU_SOURCE
+ #include 
+ #include 
diff -Nru vde2-2.3.2+r586/debian/patches/series 
vde2-2.3.2+r586/debian/patches/series
--- vde2-2.3.2+r586/debian/patches/series   2020-01-31 00:43:23.0 
+1300
+++ vde2-2.3.2+r586/debian/patches/series   2024-03-20 09:33:55.0 
+1300
@@ -5,3 +5,4 @@
 vdeterm_terminal_reset.patch
 fix_qtime_hash_gc_race_condition.patch
 vde_cryptcab-compile-against-openssl-1.1.0.patch
+interposition-vs-lfs.patch

Processed: Re: vde: FTBFS on arm{el,hf}: /tmp/ccwOo5J4.s:341: Error: symbol `open64' is already defined

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1065951 [src:vde2] vde: FTBFS on arm{el,hf}: /tmp/ccwOo5J4.s:341: Error: 
symbol `open64' is already defined
Added tag(s) patch.

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

Processed: meld: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Debian Bug Tracking System]

Processing control commands:

> block 1036884 by -1
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1066794 1065787 1067069 1065816 1067175 1067189 1067192 
1065973 1055352 1067171 1067190 1062847 1067170 1055530 1066049
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1067193

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

Bug#1067193: meld: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Simon McVittie]

Package: meld
Version: 3.22.1-1
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1

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

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

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

More information about this transition is available on
.

Thanks,
smcv

Bug#1067192: gtk-d: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Simon McVittie]

Source: gtk-d
Version: 3.10.0-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1

libgtkd-3-0 has a hard-coded dependency on libgtk-3-0, which will need
to be replaced by libgtk-3-0t64 after checking that the functions that
interact with time_t (methods of GtkRecentInfo) are handled correctly.

There might be other library dependencies in a similar situation: I suggest
using this bug report to represent all of them, rather than having multiple
bugs to track this.

More information about this transition is available on
.

Thanks,
smcv

Processed: gtk-d: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Debian Bug Tracking System]

Processing control commands:

> block 1036884 by -1
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1055352 1067171 1066049 1067175 1067170 1055530 1062847 
1066794 1065816 1067189 1067190 1067069 1065787 1065973
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1067192

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

Bug#1067191: gnome-subtitles: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Simon McVittie]

Package: gnome-subtitles
Version: 1.8-1
Severity: serious
Justification: 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t

gnome-subtitles has a hard-coded dependency on libgtk-3-0, which needs to
be replaced with libgtk-3-0t64 as part of the 64-bit time_t transition.
When doing this, please check that it doesn't call any functions from
GTK that take a time_t argument or return a time_t (the affected methods
all involve GtkRecentInfo, please see
https://adrien.dcln.fr/misc/armhf-time_t/2024-02-26T12%3A07%3A00/compat_reports/libgtk-3-dev/lfs_to_time_t/compat_report.html
for full details).

This is mostly a theoretical concern because gnome-subtitles is already
excluded from testing as a result of an unrelated RC bug #1053529.

More information about this transition is available on
.

Thanks,
smcv

Processed: timekpr-next: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Debian Bug Tracking System]

Processing control commands:

> block 1036884 by -1
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1065787 1067189 1062847 1067175 1065816 1066049 1067069 
1067171 1055530 1065973 1066794 1055352 1067170
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1067190

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

Bug#1067190: timekpr-next: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Simon McVittie]

Package: timekpr-next
Version: 0.5.4-1
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1

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

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

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

More information about this transition is available on
.

Thanks,
smcv

Processed: syncthing-gtk: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Debian Bug Tracking System]

Processing control commands:

> block 1036884 by -1
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1066049 1055530 1065816 1067175 1066794 1067170 1067069 
1065787 1067171 1055352 1065973 1062847
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1067189

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

Bug#1067189: syncthing-gtk: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Simon McVittie]

Package: syncthing-gtk
Version: 0.9.4.4+ds+git20221205+12a9702d29ab-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1

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

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

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

More information about this transition is available on
.

Thanks,
smcv

Bug#1067188: gdb-mingw-w64: FTBFS in trixie

[Santiago Vila]

Package: src:gdb-mingw-w64
Version: 13.1
Severity: serious
Tags: ftbfs

Dear maintainer:

This package FTBFS in trixie with internal compiler error, and that
has been the case for several months now.

https://tests.reproducible-builds.org/debian/rb-pkg/trixie/amd64/gdb-mingw-w64.html

Naturally, the bug is probably in one of the build-dependencies, maybe 
gcc-mingw-w64
but I'm not 100% sure.

So, this bug needs a reassign, please use "affects  src:gdb-mingw-w64" after
reassign, as the purpose of this report is to make sure that the bug appears 
here:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gdb-mingw-w64

(That way, anybody doing QA work in trixie will know that the fact that this
package ftbfs in trixie is already known)

Thanks.

Processed: fixed 1067027 in 42.0.5-1

[Debian Bug Tracking System]

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

> fixed 1067027 42.0.5-1
Bug #1067027 [python-cryptography] python-cryptography build-dependencies 
unsatisfiable.
There is no source info for the package 'python-cryptography' at version 
'42.0.5-1' with architecture ''
Unable to make a source version for version '42.0.5-1'
Marked as fixed in versions 42.0.5-1.
> thanks
Stopping processing here.

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

Processed: Bug#1066574 marked as pending in xbill

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066574 [src:xbill] xbill: FTBFS: Game.c:258:21: error: implicit 
declaration of function ‘strncasecmp’ [-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1066574: marked as pending in xbill

[Reiner Herrmann]

Control: tag -1 pending

Hello,

Bug #1066574 in xbill 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/games-team/xbill/-/commit/2ec49d952acc56ff8b138aa7761c03657f0dc013


Fix FTBFS because of implicit declaration

Closes: #1066574


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066574

Bug#1067171: marked as pending in bleachbit

[Fabio Fantoni]

Control: tag -1 pending

Hello,

Bug #1067171 in bleachbit 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/bleachbit/-/commit/70ff0b682a0d402ce1e972cb7f45311066527477


Remove libgtk-3-0 from depends

Remove the explicit dependency on libgtk-3-0. For Python code that uses
GTK via GObject-Introspection, it is sufficient to depend on
gir1.2-gtk-3.0.
This solves a blocking issue for 64-bit time_t transition.

Closes: #1067171


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1067171

Processed: Bug#1067171 marked as pending in bleachbit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1067171 [bleachbit] bleachbit: hard-coded dependency on libgtk-3-0 will 
become uninstallable on armel/armhf
Added tag(s) pending.

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

Bug#1066794: git: FTBFS: tests failed

[Andrey Rakhmatullin]

Not sure which tests actually failed (it's really hard to understand the
output) but also I cannot reproduce this locally in sbuild, with -j1 or
-j4 and with or without --no-arch-any.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1067175: exaile: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Simon McVittie]

Package: exaile
Version: 4.1.3+dfsg-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1

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

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

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

More information about this transition is available on
.

Thanks,
smcv

Processed: exaile: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Debian Bug Tracking System]

Processing control commands:

> block 1036884 by -1
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1065816 1055530 1065973 1066794 1055352 1067171 1062847 
1067170 1065787 1066049 1067069
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1067175

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

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

[Simon McVittie]

Package: cpupower-gui
Version: 0.7.2-2.1
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t

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

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

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

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

More information about this transition is available on
.

Thanks,
smcv

Bug#1067173: clearlooks-phenix-theme: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Simon McVittie]

Package: clearlooks-phenix-theme
Version: 7.0.1-3
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t

clearlooks-phenix-theme is an Architecture: all package, but has a
direct (versioned) dependency on libgtk-3-0.

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

Please remove the explicit dependency on libgtk-3-0, or swap it for
libgtk-3-0t64. Perhaps it could become a Recommends: libgtk-3-0t64,
Breaks: libgtk-3-0 (<< 3.20)?

(This is mainly a theoretical concern because clearlooks-phenix-theme
was removed from testing as a result of an unrelated RC bug.)

Thanks,
smcv

Processed: bleachbit: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Debian Bug Tracking System]

Processing control commands:

> block 1036884 by -1
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1067170 1065787 1065973 1067069 1055352 1065816 1066049 
1066794 1055530 1062847
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1067171

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

Bug#1067171: bleachbit: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Simon McVittie]

Package: bleachbit
Version: 4.6.0-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1

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

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

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

More information about this transition is available on
.

Thanks,
smcv

Processed: 0install: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Debian Bug Tracking System]

Processing control commands:

> block 1036884 by -1
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1062847 1066794 1067069 1065787 1055352 1055530 1066049 
1065816 1065973
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1067170

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

Bug#1067170: 0install: hard-coded dependency on libgtk-3-0 will become uninstallable on armel/armhf

[Simon McVittie]

Package: 0install
Version: 2.18-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1

Versions of 0install that have been rebuilt for the 64-bit time_t
transition (for example on amd64) have dependencies on both libgtk-3-0
and libgtk-3-0t64. On the architectures where the ABI transition took
place (for example armel and armhf) this will be an impossible dependency.

It looks as though 0install is correctly picking up a dependency on GTK
from ${shlibs:Depends}, so please remove the explicit dependency on
libgtk-3-0.

Thanks,
smcv

Bug#1066345: marked as done (libgdchart-gd2: FTBFS: ../gdc.c:284:74: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 16:49:24 +
with message-id 
and subject line Bug#1066345: fixed in libgdchart-gd2 0.11.5-11
has caused the Debian Bug report #1066345,
regarding libgdchart-gd2: FTBFS: ../gdc.c:284:74: error: implicit declaration 
of function ‘strlen’ [-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.)


-- 
1066345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgdchart-gd2
Version: 0.11.5-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):
> x86_64-linux-gnu-gcc -I. -I.. -I/usr/include/freetype2 
> -I/usr/include/freetype2/freetype -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -D_REENTRANT -pipe -DHAVE_LIBPNG 
> -DHAVE_LIBFREETYPE -DHAVE_LIBJPEG -fsigned-char -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o gdc.o ../gdc.c
> ../gdc.c: In function ‘out_err’:
> ../gdc.c:284:74: error: implicit declaration of function ‘strlen’ 
> [-Werror=implicit-function-declaration]
>   284 |IMGWIDTH/2 - 
> GDC_fontc[GDC_MEDBOLD].w*strlen(err_str)/2,
>   |   
>^~
> ../gdc.c:8:1: note: include ‘’ or provide a declaration of ‘strlen’
> 7 | #include "gdc.h"
>   +++ |+#include 
> 8 | 
> ../gdc.c:284:74: warning: incompatible implicit declaration of built-in 
> function ‘strlen’ [-Wbuiltin-declaration-mismatch]
>   284 |IMGWIDTH/2 - 
> GDC_fontc[GDC_MEDBOLD].w*strlen(err_str)/2,
>   |   
>^~
> ../gdc.c:284:74: note: include ‘’ or provide a declaration of 
> ‘strlen’
> cc1: some warnings being treated as errors
> make[1]: *** [: gdc.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/libgdchart-gd2_0.11.5-10_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: libgdchart-gd2
Source-Version: 0.11.5-11
Done: Michael R. Crusoe 

We believe that the bug you reported is fixed in the latest version of
libgdchart-gd2, 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.
Michael R. Crusoe  (supplier of updated libgdchart-gd2 
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: Tue, 19 Mar 2024 17:31:08 +0100
Source: libgdchart-gd2
Architecture: source
Version: 0.11.5-11
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Michael R. Crusoe 
Closes: 1065971 1066345
Changes:
 libgdchart-gd2 (0.11.5-11) unstable; urgency=medium
 .
   * Team upload
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces
 .
   [ Michael R. Crusoe ]
   * d/patches/1003_string_include.patch: add missing include. Closes:

Bug#1065971: marked as done (libgdchart-gd2: FTBFS on arm{el,hf}: ../gdc.c:284:74: error: implicit declaration of function ‘strlen’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 16:49:24 +
with message-id 
and subject line Bug#1065971: fixed in libgdchart-gd2 0.11.5-11
has caused the Debian Bug report #1065971,
regarding libgdchart-gd2: FTBFS on arm{el,hf}: ../gdc.c:284:74: error: implicit 
declaration of function ‘strlen’ [-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.)


-- 
1065971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgdchart-gd2
Version: 0.11.5-10
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=libgdchart-gd2=armhf=0.11.5-10%2Bb1=1709991773=0

arm-linux-gnueabihf-gcc -I. -I.. -I/usr/include/freetype2 
-I/usr/include/freetype2/freetype -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -D_REENTRANT -pipe 
-DHAVE_LIBPNG -DHAVE_LIBFREETYPE -DHAVE_LIBJPEG -fsigned-char 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
-D_FORTIFY_SOURCE=2  -c -o gdc.o ../gdc.c
../gdc.c: In function ‘out_err’:
../gdc.c:284:74: error: implicit declaration of function ‘strlen’ 
[-Werror=implicit-function-declaration]
  284 |IMGWIDTH/2 - 
GDC_fontc[GDC_MEDBOLD].w*strlen(err_str)/2,
  | 
 ^~
../gdc.c:8:1: note: include ‘’ or provide a declaration of ‘strlen’
7 | #include "gdc.h"
  +++ |+#include 
8 | 
../gdc.c:284:74: warning: incompatible implicit declaration of built-in 
function ‘strlen’ [-Wbuiltin-declaration-mismatch]
  284 |IMGWIDTH/2 - 
GDC_fontc[GDC_MEDBOLD].w*strlen(err_str)/2,
  | 
 ^~
../gdc.c:284:74: note: include ‘’ or provide a declaration of ‘strlen’
cc1: some warnings being treated as errors
make[1]: *** [: gdc.o] Error 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libgdchart-gd2
Source-Version: 0.11.5-11
Done: Michael R. Crusoe 

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

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

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated libgdchart-gd2 
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: Tue, 19 Mar 2024 17:31:08 +0100
Source: libgdchart-gd2
Architecture: source
Version: 0.11.5-11
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Michael R. Crusoe 
Closes: 1065971 1066345
Changes:
 libgdchart-gd2 (0.11.5-11) unstable; urgency=medium
 .
   * Team upload
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces
 .
   [ Michael R. Crusoe ]
   * d/patches/1003_string_include.patch: add missing include. Closes:
 #1066345, #1065971
   * Remove trailing whitespace in debian/copyright (routine-update)
   * Remove trailing whitespace in debian/rules (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * Trim trailing whitespace.
   * d/control: remove obsolete references to the binary packages
 libgdchart & libgdchart-gd2-dev.
Checksums-Sha1:
 a4584dfefdbf28af4733bb03ff546655bd9dd7db 2238 libgdchart-gd2_0.11.5-11.dsc
 0bb619180e74696cb49e9389ac6d84d4161c93cf 8948 
libgdchart-gd2_0.11.5-11.debian.tar.xz
 b0b68dbe26d2892d1aa784bccc7d196fa5377a7e 8964 
libgdchart-gd2_0.11.5-11_source.buildinfo
Checksums-Sha256:
 6090da9db7e4ce0fcda0688c47a7018d83b1f5479273e022f2b89067fde66bd7 2238 
libgdchart-gd2_0.11.5-11.dsc
 2708bcb0acae53d6dbf269fc50f7db7277d85618caea09ac3860128fb3139bfb 8948 
libgdchart-gd2_0.11.5-11.debian.tar.xz
 67791f40c2144020512f7b636dfcd2947a32e6878d67761d2833b84b02203799 8964 
libgdchart-gd2_0.11.5-11_source.buildinfo
Files:
 0e638fa974a4548140cb52726c319909 2238 libs optional 

Bug#1067017: marked as done (jupyterlab: Use node-long package)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 16:34:49 +
with message-id 
and subject line Bug#1067017: fixed in jupyterlab 4.0.11+ds1-2
has caused the Debian Bug report #1067017,
regarding jupyterlab: Use node-long package
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.)


-- 
1067017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jupyterlab
Version: 4.0.11+ds1-1
Severity: serious
Justification: duplicate code source not build from source

Dear Maintainer,

Your package include the following file packaged elsewhere
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/LICENSE
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/README.md
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/dist/long.js
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/dist/long.js.map
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/index.d.ts
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/index.js
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/package.json
python3-jupyterlab:
/usr/share/jupyter/lab/staging/node_modules/@xtuc/long/src/long.js


Moreover, it was hard for debian to get this files builded and @xtuc ones does
not build from source

Bastien


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

Kernel: Linux 6.6.15-rt-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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
--- End Message ---
--- Begin Message ---
Source: jupyterlab
Source-Version: 4.0.11+ds1-2
Done: Roland Mas 

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

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

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

Debian distribution maintenance software
pp.
Roland Mas  (supplier of updated jupyterlab 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: Tue, 19 Mar 2024 16:49:20 +0100
Source: jupyterlab
Architecture: source
Version: 4.0.11+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Roland Mas 
Closes: 1067017 1067019 1067020
Changes:
 jupyterlab (4.0.11+ds1-2) unstable; urgency=medium
 .
   * Improve error detection in d/rules.
   * Bug fix: "Use node-long package", thanks to Bastien Roucariès (Closes:
 #1067017).
   * Bug fix: "use pacckaged node-call-bind (provided package)", thanks to
 Bastien Roucariès (Closes: #1067019).
   * Bug fix: "please use node-get-intrinsic", thanks to Bastien Roucariès
 (Closes: #1067020).
Checksums-Sha1:
 43c89b2297d639e38099ef1432ffbd87a9ae0193 2725 jupyterlab_4.0.11+ds1-2.dsc
 4d29f2a8983c4b02ab14188ea4710b376d289948 5960 
jupyterlab_4.0.11+ds1-2.debian.tar.xz
 08a1e32bdf886c4b2a2efe7a4b23b0a82b838574 35124 
jupyterlab_4.0.11+ds1-2_amd64.buildinfo
Checksums-Sha256:
 9b51935d0d8e75cff18609d69f05a6e659ad0afc1d0f73f519bc66a4c68fada6 2725 
jupyterlab_4.0.11+ds1-2.dsc
 89196b7dc1b22b29c72812ed96016bf6dd11e7ebf9a270dd640ba37f1d65fd92 5960 
jupyterlab_4.0.11+ds1-2.debian.tar.xz
 0f7f724967ca8651dba47e7060843277d8c00240ae93210bf02eac898e2fc097 35124 
jupyterlab_4.0.11+ds1-2_amd64.buildinfo
Files:
 403d1fa40cf67739b4412798b77f2667 2725 python optional 
jupyterlab_4.0.11+ds1-2.dsc
 9bb8187bf7705cd5301ded74056c650b 5960 python optional 
jupyterlab_4.0.11+ds1-2.debian.tar.xz
 6a03a98aac03211e6de053b64bf91029 35124 python optional 
jupyterlab_4.0.11+ds1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtBU2D1kett1zr/uD0w3s0lmTIvwFAmX5uOMACgkQ0w3s0lmT
IvwfLA/+L+NubTKkatFy5lrB4MQ9OPRd0eUYPrc5iPBBaPaK865Hi2+3anG3rsLP
91Khv5cltC0k2bcQG2cacqg2sX9B3Ye/2nGbJ3TLla+erLWNNhKFcv7CTPsoEmQI

Bug#1067141: kcemu: FTBFS with -Werror=implicit-function-declaration

[Bo YU]

Package: kcemu
Version: 0.5.2+dfsg-1
Followup-For: Bug #1067141
Tags: patch

Hi, 

I just test the patch and it seems it works.


-- 
Regards,
--
  Bo YU

diff -Nru kcemu-0.5.2+dfsg/debian/changelog kcemu-0.5.2+dfsg/debian/changelog
--- kcemu-0.5.2+dfsg/debian/changelog   2022-11-30 05:53:48.0 -0500
+++ kcemu-0.5.2+dfsg/debian/changelog   2024-03-19 11:32:12.0 -0400
@@ -1,3 +1,10 @@
+kcemu (0.5.2+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix implicit-function-declaration issue. (Closes: #1067141) 
+
+ -- a   Tue, 19 Mar 2024 11:32:12 -0400
+
 kcemu (0.5.2+dfsg-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru 
kcemu-0.5.2+dfsg/debian/patches/fix-error-implicit-function-declaration.patch 
kcemu-0.5.2+dfsg/debian/patches/fix-error-implicit-function-declaration.patch
--- 
kcemu-0.5.2+dfsg/debian/patches/fix-error-implicit-function-declaration.patch   
1969-12-31 19:00:00.0 -0500
+++ 
kcemu-0.5.2+dfsg/debian/patches/fix-error-implicit-function-declaration.patch   
2024-03-19 11:32:02.0 -0400
@@ -0,0 +1,28 @@
+Description: fix implicit-function-declaration error
+Author: Bo YU 
+Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067141
+Forwarded: https://github.com/t-paul/kcemu/issues/6
+Last-Update: 2024-03-19
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/sys/mingw/sys_socket_create.c
 b/src/sys/mingw/sys_socket_create.c
+@@ -18,6 +18,7 @@
+  */
+ 
+ #include 
++#include 
+ 
+ #include "kc/config.h"
+ #include "sys/sysdep.h"
+--- a/src/sys/unix/sys_socket_create.c
 b/src/sys/unix/sys_socket_create.c
+@@ -23,6 +23,8 @@
+ #include 
+ #include 
+ #include 
++#include 
++
+ 
+ #include "kc/config.h"
+ #include "sys/sysdep.h"
diff -Nru kcemu-0.5.2+dfsg/debian/patches/series 
kcemu-0.5.2+dfsg/debian/patches/series
--- kcemu-0.5.2+dfsg/debian/patches/series  1969-12-31 19:00:00.0 
-0500
+++ kcemu-0.5.2+dfsg/debian/patches/series  2024-03-19 05:37:35.0 
-0400
@@ -0,0 +1 @@
+fix-error-implicit-function-declaration.patch


signature.asc
Description: PGP signature

Bug#1066422: marked as done (libdcmtk-dev: missing dependency on libnsl-dev)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 15:20:15 +
with message-id 
and subject line Bug#1066422: fixed in dcmtk 3.6.7-13
has caused the Debian Bug report #1066422,
regarding libdcmtk-dev: missing dependency on libnsl-dev
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2  
> -fno-sized-deallocation -O3 -DNDEBUG -Wl,-z,relro -Wl,-z,now  -rdynamic 
> -fopenmp CMakeFiles/landmark_diff.dir/landmark_diff_main.cxx.o -o 
> ../../../landmark_diff   
> -L/<>/obj-x86_64-linux-gnu/libs/liblbfgs-1.9  
> -L/<>/obj-x86_64-linux-gnu/libs/specfun  
> -L/usr/lib/x86_64-linux-gnu/lib  -L/<>/obj-x86_64-linux-gnu  
> -L/usr/lib/x86_64-linux-gnu/cmake/dcmtk/lib/x86_64-linux-gnu  -L/usr/include  
> ../clp/libplmclp.a ../../../libplmsegment.so.1.9 
> ../../../libplmregister.so.1.9 ../../../libplmreconstruct.so.1.9 
> ../../../libplmdose.so.1.9 ../../../libplmutil.so.1.9 
> ../../../libplmbase.so.1.9 ../../../libplmsys.so.1.9 -lz -ljpeg -lexpat -lpng 
> /usr/lib/x86_64-linux-gnu/libITKTestKernel-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKConvolution-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKColormap-5.3.so.1 -lofstd -loflog -ldcmdata 
> -li2d -ldcmimgle -ldcmimage -ldcmjpeg -lijg8 -lijg12 -lijg16 -ldcmjpls 
> -ldcmtkcharls -ldcmtls -ldcmnet -ldcmsr -lcmr -ldcmdsig -ldcmwlm -ldcmqrdb 
> -ldcmpstat -ldcmrt -ldcmiod -ldcmfg -ldcmseg -ldcmtract -ldcmpmap -ldcmect 
> /usr/lib/x86_64-linux-gnu/libITKDICOMParser-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKDenoising-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5_cpp.so 
> /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.so 
> /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5_hl.so 
> /usr/lib/x86_64-linux-gnu/libITKIOBruker-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOCSV-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOHDF5-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOJPEG2000-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOLSM-5.3.so.1 -lminc2 -lm -lz -lm -ldl 
> -lnetcdf /usr/lib/x86_64-linux-gnu/libITKIOMINC-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOMRC-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKRegistrationMethodsv4-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKReview-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKVideoIO-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKVtkGlue-5.3.so.1 ../../../libdevillard.a 
> ../../../libnkidecompress.a -lm 
> /usr/lib/x86_64-linux-gnu/libdcmdata.so.17.3.6.7 
> /usr/lib/x86_64-linux-gnu/libdlib.so.19.24.0 -lfftw3f -lfftw3 -ldl 
> ../../../libspecfun.a ../../../liblbfgs.a 
> /usr/lib/x86_64-linux-gnu/libITKIOMeshBYU-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOMeshFreeSurfer-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOMeshGifti-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKgiftiio-5.3.so.1 -lexpat 
> /usr/lib/x86_64-linux-gnu/libITKIOMeshOBJ-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOMeshOFF-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOMeshVTK-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOMeshBase-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKOptimizersv4-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libitklbfgs-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOBMP-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOGDCM-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libgdcmMSFF.so.3.0.22 
> /usr/lib/x86_64-linux-gnu/libgdcmDICT.so.3.0.22 
> /usr/lib/x86_64-linux-gnu/libgdcmIOD.so.3.0.22 
> /usr/lib/x86_64-linux-gnu/libgdcmDSED.so.3.0.22 
> /usr/lib/x86_64-linux-gnu/libgdcmCommon.so.3.0.22 
> /usr/lib/x86_64-linux-gnu/libITKIOGIPL-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOJPEG-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKQuadEdgeMesh-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOMeta-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKMetaIO-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIONIFTI-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKniftiio-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKznz-5.3.so.1 -lm 
> /usr/lib/x86_64-linux-gnu/libITKIONRRD-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKNrrdIO-5.3.so.1 
> /usr/lib/x86_64-linux-gnu/libITKIOPNG-5.3.so.1 
> 

Bug#1066423: marked as done (libdcmtk-dev: missing dependency on libnsl-dev)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 15:20:15 +
with message-id 
and subject line Bug#1066422: fixed in dcmtk 3.6.7-13
has caused the Debian Bug report #1066422,
regarding libdcmtk-dev: missing dependency on libnsl-dev
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -O3 
> -DNDEBUG -fuse-ld=gold -Wl,--as-needed -Wl,--sort-common -Wl,-O2 -Wl,-z,relro 
> -Wl,-z,now -shared -Wl,-soname,libsight_io_dimse.so.23.1 -o 
> ../../../lib/x86_64-linux-gnu/libsight_io_dimse.so.23.1.0 
> CMakeFiles/io_dimse.dir/SeriesEnquirer.cpp.o 
> CMakeFiles/io_dimse.dir/SeriesRetriever.cpp.o 
> CMakeFiles/io_dimse.dir/data/PacsConfiguration.cpp.o 
> CMakeFiles/io_dimse.dir/exceptions/Base.cpp.o 
> CMakeFiles/io_dimse.dir/exceptions/NegociateAssociationFailure.cpp.o 
> CMakeFiles/io_dimse.dir/exceptions/NetworkInitializationFailure.cpp.o 
> CMakeFiles/io_dimse.dir/exceptions/PresentationContextMissing.cpp.o 
> CMakeFiles/io_dimse.dir/exceptions/RequestFailure.cpp.o 
> CMakeFiles/io_dimse.dir/exceptions/TagMissing.cpp.o 
> CMakeFiles/io_dimse.dir/helper/Series.cpp.o  
> -Wl,-rpath,/<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu: 
> /usr/lib/x86_64-linux-gnu/libdcmnet.so.17.3.6.7 
> ../../../lib/x86_64-linux-gnu/libsight_data.so.23.1.0 
> /usr/lib/x86_64-linux-gnu/libdcmdata.so.17.3.6.7 
> /usr/lib/x86_64-linux-gnu/liboflog.so.17.3.6.7 
> /usr/lib/x86_64-linux-gnu/libofstd.so.17.3.6.7 -lnsl -lpthread -lrt 
> /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libxml2.so 
> /usr/lib/x86_64-linux-gnu/libwrap.so 
> ../../../lib/x86_64-linux-gnu/libsight_core.so.23.1.0 
> /usr/lib/x86_64-linux-gnu/libboost_date_time.so.1.83.0 
> /usr/lib/x86_64-linux-gnu/libboost_log_setup.so.1.83.0 
> /usr/lib/x86_64-linux-gnu/libboost_log.so.1.83.0 
> /usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.83.0 
> /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.83.0 
> /usr/lib/x86_64-linux-gnu/libboost_regex.so.1.83.0 
> /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.83.0 
> /usr/lib/x86_64-linux-gnu/libboost_atomic.so.1.83.0 
> /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.83.0 
> /usr/lib/x86_64-linux-gnu/libxml2.so /usr/lib/x86_64-linux-gnu/libicuuc.so 
> /usr/lib/x86_64-linux-gnu/libcrypto.so -ldl 
> /usr/lib/gcc/x86_64-linux-gnu/13/libgomp.so 
> /usr/lib/x86_64-linux-gnu/libpthread.a 
> /usr/bin/ld.gold: error: cannot find -lnsl
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/sight_23.1.0-2_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: dcmtk
Source-Version: 3.6.7-13
Done: Michael R. Crusoe 

We believe that the bug you reported is fixed in the latest version of
dcmtk, 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.
Michael R. Crusoe  (supplier of updated dcmtk 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 

Processed: block 1036884 with 1066794

[Debian Bug Tracking System]

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

> block 1036884 with 1066794
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1065973 1065816 1067069 1062847 1055352 1066049 1055530 
1065787
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1066794
> thanks
Stopping processing here.

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

Bug#1067134: marked as done (Try to remove i386 packages)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 15:45:40 +0100
with message-id <20240319144540.ga2975...@subdivi.de>
and subject line Re: Bug#1067134: Try to remove i386 packages
has caused the Debian Bug report #1067134,
regarding Try to remove i386 packages
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.)


-- 
1067134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: comerr-dev
Version: 2.1-1.47.0-2.4
Severity: serious

Dear Maintainer,

I'm unable to install comerr-dev under a multiarch amd64/i386
machine.

Here is a simple example :

,
| $ sudo apt-get install comerr-dev 
| Reading package lists... Done
| Building dependency tree... Done
| Reading state information... Done
| 
| [...]
| 
| The following additional packages will be installed:
|   libcom-err2
| Suggested packages:
|   doc-base
| The following packages will be REMOVED:
|   inetutils-telnet:i386
| The following NEW packages will be installed:
|   comerr-dev libcom-err2
| 0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
`

Christian


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

Kernel: Linux 6.8.1-1-custom (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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)
--- End Message ---
--- Begin Message ---
Control: tags -1 - moreinfo + wontfix

On Tue, Mar 19, 2024 at 02:21:59PM +0100, Christian Marillat wrote:
> On 19 mars 2024 13:28, Helmut Grohne  wrote:
> 
> 
> [...]
> 
> > I agree that the experience is a little messed up, but this is
> > resolvable with apt and it only affects unstable users. Do you agree
> > with closing this bug with no action?
> 
> Yes, if you think that this bug is only related to unstable...

Yes. libcom-err2t64 (which is what is require to experience the problem)
has never gotten beyond unstable and experimental. Thus closing the bug.

Helmut--- End Message ---

Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

[Andreas Tille]

Hi Emanuele.

Am Tue, Mar 19, 2024 at 12:16:16PM +0100 schrieb Emanuele Rocca:
> I've uploaded a NMU to DELAYED/2: https://bugs.debian.org/1067147

Thanks a lot for your attempt to help.  In principle we have a team wide
low threshold NMU - so undelayed NMUs are fine.  The kind of race
condition in uploads might imply that some ping in advance might be
helpful to avoid duplicated work.
 
> With those changes dcmtk builds fine on both armel and armhf. I've
> dropped the graphviz build-depend on those arches too, it can of course
> be reintroduced once graphviz become installable again.

Meanwhile your patch is imported and was uploaded by Michael - thanks to
all who helped solving this.

Kind regards
Andreas.

-- 
http://fam-tille.de

Bug#1066422: marked as pending in dcmtk

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/dcmtk/-/commit/7378bd088ea12ea28c1b716bc6a46561597c03b1


d/control: add explicit dependency on libnsl-dev. Closes: #1066422.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066422

Processed: Bug#1066422 marked as pending in dcmtk

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066422 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev
Bug #1066423 [libdcmtk-dev] libdcmtk-dev: missing dependency on libnsl-dev
Added tag(s) pending.
Added tag(s) pending.

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

Processed: workaround uploaded to unstable

[Debian Bug Tracking System]

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

> fixed 1060104 3.6.7-11
Bug #1060104 [src:dcmtk] dcmtk: FTBFS on armel: Error: bad immediate value for 
offset (4100)
Marked as fixed in versions dcmtk/3.6.7-11.
> --
Stopping processing here.

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

Bug#1065375: marked as done (bc fails to build with abi=time64)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 13:49:34 +
with message-id 
and subject line Bug#1065375: fixed in bc 1.07.1-4
has caused the Debian Bug report #1065375,
regarding bc fails to build with abi=time64
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.)


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

Package: src:bc
Version: bc 1.07.1-3
Severity: serious
Tags: sid trixie patch

bc fails to build with abi=time64, which turns on 
-Werror=implicit-function-declaration.
  * Avoid -Wimplicit-function-declaration warnings.
 
diff -Nru bc-1.07.1/debian/patches/no-implicit-function-declaration.diff bc-1.07.1/debian/patches/no-implicit-function-declaration.diff
--- bc-1.07.1/debian/patches/no-implicit-function-declaration.diff	1970-01-01 01:00:00.0 +0100
+++ bc-1.07.1/debian/patches/no-implicit-function-declaration.diff	2024-03-03 13:40:56.0 +0100
@@ -0,0 +1,50 @@
+--- a/dc/dc.c
 b/dc/dc.c
+@@ -47,6 +47,7 @@
+ #include 
+ #include "dc.h"
+ #include "dc-proto.h"
++#include "number.h"
+ 
+ #ifndef EXIT_SUCCESS	/* C89  */
+ # define EXIT_SUCCESS	0
+--- a/dc/eval.c
 b/dc/eval.c
+@@ -41,6 +41,7 @@
+ #endif
+ #include "dc.h"
+ #include "dc-proto.h"
++#include "number.h"
+ 
+ typedef enum {DC_FALSE, DC_TRUE} dc_boolean;
+ 
+--- a/dc/misc.c
 b/dc/misc.c
+@@ -47,6 +47,7 @@
+ #include 
+ #include "dc.h"
+ #include "dc-proto.h"
++#include "number.h"
+ 
+ #ifndef EXIT_FAILURE	/* C89  */
+ # define EXIT_FAILURE	1
+--- a/dc/stack.c
 b/dc/stack.c
+@@ -33,6 +33,7 @@
+ #include "dc.h"
+ #include "dc-proto.h"
+ #include "dc-regdef.h"
++#include "number.h"
+ 
+ /* an oft-used error message: */
+ #define Empty_Stack do{	\
+--- a/dc/string.c
 b/dc/string.c
+@@ -45,6 +45,7 @@
+ #endif
+ #include "dc.h"
+ #include "dc-proto.h"
++#include "number.h"
+ 
+ /* here is the completion of the dc_string type: */
+ struct dc_string {
diff -Nru bc-1.07.1/debian/patches/series bc-1.07.1/debian/patches/series
--- bc-1.07.1/debian/patches/series	2019-12-05 20:35:54.0 +0100
+++ bc-1.07.1/debian/patches/series	2024-03-03 13:38:34.0 +0100
@@ -5,3 +5,4 @@
 06_read_dcrc.diff
 07_bc_man.diff
 08_no-make-circular-dependencies.diff
+no-implicit-function-declaration.diff
--- End Message ---
--- Begin Message ---
Source: bc
Source-Version: 1.07.1-4
Done: Ryan Kavanagh 

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

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

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

Debian distribution maintenance software
pp.
Ryan Kavanagh  (supplier of updated bc 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, 13 Mar 2024 14:06:49 -0400
Source: bc
Architecture: source
Version: 1.07.1-4
Distribution: unstable
Urgency: medium
Maintainer: Ryan Kavanagh 
Changed-By: Ryan Kavanagh 
Closes: 1043703 1065375
Changes:
 bc (1.07.1-4) unstable; urgency=medium
 .
   [ Gürkan Myczko ]
   * add d/clean so one can debuild several times (say with CC=clang)
 (Closes: #1043703)
 .
   [ Ryan Kavanagh ]
   * Mark all patches as forwarded
   * wrap-and-sort packaging
   * Bump compat level to 13
   * Switch to gbp-pq
   * Fix implicit declarations in 05_notice_read_write_errors.diff that cause
 FTBFS (Closes: #1065375)
   * Bump standards version to 4.6.2, no changes required
   * Bump copyright years
   * Fix 04_info_dircategory.diff to actually set the info dircategory for dc
 to Math
Checksums-Sha1:
 63634608e7c238e698868909084e6896c2e3d341 1884 bc_1.07.1-4.dsc
 56a05afa0ffda2e5f8d83be7584afda9a87ee37d 25140 bc_1.07.1-4.debian.tar.xz
 bec65d838b00a6263378a08cad180a94549e75df 7473 bc_1.07.1-4_amd64.buildinfo
Checksums-Sha256:
 bd9acd6ac43d7729c02e6d362b1d5601c1733ad4fa6ac64d8b317d98135a4f5b 1884 
bc_1.07.1-4.dsc
 3d73fa24dfc196df0d3d45fa5feede4108bd8442c256a40159db28131008abe9 25140 
bc_1.07.1-4.debian.tar.xz
 013822f406e227496fd9d84a9e431b9dca9ed132a46110bbf8f207562e4522e6 7473 
bc_1.07.1-4_amd64.buildinfo
Files:
 c6e1565a15e7e2c2afac807ec48b9fd5 1884 math standard bc_1.07.1-4.dsc
 

Bug#1067134: Try to remove i386 packages

[Christian Marillat]

On 19 mars 2024 13:28, Helmut Grohne  wrote:


[...]

> I agree that the experience is a little messed up, but this is
> resolvable with apt and it only affects unstable users. Do you agree
> with closing this bug with no action?

Yes, if you think that this bug is only related to unstable...

Christian

Bug#1067134: Try to remove i386 packages

[Helmut Grohne]

On Tue, Mar 19, 2024 at 10:45:44AM +0100, Christian Marillat wrote:
> ,
> | $ dpkg -l | grep libcom-err
> | ii  libcom-err2t64:amd64   1.47.0-2.3+b1
>amd64common error description library
> | ii  libcom-err2t64:i3861.47.0-2.3+b1
>i386 common error description library

This is the bumpy unstable state that should never migrate to trixie.

> upgrading libcom-err2 to 1.47.0-2.4 remove all i386 packages

Consider guiding apt by asking it to install both libcom-err2:amd64 and
libcom-err2:i386.

> ,
> | $ dpkg -l |grep libcom-err2  
> | ii  libcom-err2:amd64  1.47.0-2.4   
>amd64common error description library
> `
> 
> but now I can reinstall i386 packages again :
> 
> ,
> | $ dpkg -l |grep libcom-err2
> | ii  libcom-err2:amd64  1.47.0-2.4   
>amd64common error description library
> | ii  libcom-err2:i386   1.47.0-2.4   
>i386 common error description library
> `

I agree that the experience is a little messed up, but this is
resolvable with apt and it only affects unstable users. Do you agree
with closing this bug with no action?

Helmut

Bug#1042703: marked as done (python-pgpy: FTBFS with Sphinx 7.1, docutils 0.20: make[2]: *** [Makefile:53: html] Error 2)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 12:20:19 +
with message-id 
and subject line Bug#1042703: fixed in python-pgpy 0.6.0-1.1
has caused the Debian Bug report #1042703,
regarding python-pgpy: FTBFS with Sphinx 7.1, docutils 0.20: make[2]: *** 
[Makefile:53: html] Error 2
to be marked as done.

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

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


-- 
1042703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pgpy
Version: 0.6.0-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

python-pgpy fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d build/doctrees   source build/html
> Running Sphinx v7.1.1
> /<>/docs/source/conf.py:27: SetuptoolsDeprecationWarning: 
> Deprecated API usage.
> !!
> 
> 
> 
> As setuptools moves its configuration towards `pyproject.toml`,
> `setuptools.config.read_configuration` became deprecated.
> 
> For the time being, you can use the `setuptools.config.setupcfg` 
> module
> to access a backward compatible API, but this module is provisional
> and might be removed in the future.
> 
> To read project metadata, consider using
> ``build.util.project_wheel_metadata`` 
> (https://pypi.org/project/build/).
> For simple scenarios, you can also try parsing the file directly
> with the help of ``configparser``.
> 
> 
> 
> !!
>   __version__ = read_configuration(os.path.join('..', '..', 
> 'setup.cfg'))['metadata']['version']
> making output directory... done
> 
> Configuration error:
> HTML 4 is no longer supported by Sphinx. ("html4_writer=True" detected in 
> configuration options)
> make[2]: *** [Makefile:53: html] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/python-pgpy_0.6.0-1_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.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

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.20.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=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=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 ---
Source: python-pgpy
Source-Version: 0.6.0-1.1
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated python-pgpy 
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: Tue, 19 Mar 2024 20:03:20 +0800
Source: python-pgpy
Architecture: source
Version: 

Bug#1054816: marked as done (git-repair: FTBFS: make[1]: *** [Makefile:17: Build/SysConfig.hs] Error 1)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 12:05:03 +
with message-id 
and subject line Bug#1054816: fixed in git-repair 1.20230814-1
has caused the Debian Bug report #1054816,
regarding git-repair: FTBFS: make[1]: *** [Makefile:17: Build/SysConfig.hs] 
Error 1
to be marked as done.

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

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


-- 
1054816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-repair
Version: 1.20200102-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> if [ "./Setup" = ./Setup ]; then ghc --make Setup; fi
> [ 1 of 26] Compiling Utility.Applicative ( Utility/Applicative.hs, 
> Utility/Applicative.o )
> [ 2 of 26] Compiling Utility.Data ( Utility/Data.hs, Utility/Data.o )
> [ 3 of 26] Compiling Utility.Exception ( Utility/Exception.hs, 
> Utility/Exception.o )
> [ 4 of 26] Compiling Utility.Env.Basic ( Utility/Env/Basic.hs, 
> Utility/Env/Basic.o )
> [ 5 of 26] Compiling Utility.FileSize ( Utility/FileSize.hs, 
> Utility/FileSize.o )
> [ 6 of 26] Compiling Utility.Misc ( Utility/Misc.hs, Utility/Misc.o )
> [ 7 of 26] Compiling Utility.Monad( Utility/Monad.hs, Utility/Monad.o )
> [ 8 of 26] Compiling Utility.PartialPrelude ( Utility/PartialPrelude.hs, 
> Utility/PartialPrelude.o )
> [ 9 of 26] Compiling Utility.Process.Shim ( Utility/Process/Shim.hs, 
> Utility/Process/Shim.o )
> [10 of 26] Compiling Utility.Process  ( Utility/Process.hs, Utility/Process.o 
> )
> [11 of 26] Compiling Utility.Split( Utility/Split.hs, Utility/Split.o )
> [12 of 26] Compiling Utility.SafeCommand ( Utility/SafeCommand.hs, 
> Utility/SafeCommand.o )
> [13 of 26] Compiling Utility.FileSystemEncoding ( 
> Utility/FileSystemEncoding.hs, Utility/FileSystemEncoding.o )
> [14 of 26] Compiling Utility.SystemDirectory ( Utility/SystemDirectory.hs, 
> Utility/SystemDirectory.o )
> [15 of 26] Compiling Utility.Tmp  ( Utility/Tmp.hs, Utility/Tmp.o )
> [16 of 26] Compiling Utility.Directory ( Utility/Directory.hs, 
> Utility/Directory.o )
> [17 of 26] Compiling Build.Version( Build/Version.hs, Build/Version.o )
> [18 of 26] Compiling Utility.UserInfo ( Utility/UserInfo.hs, 
> Utility/UserInfo.o )
> 
> Utility/UserInfo.hs:57:23: error:
> Not in scope: type constructor or class ‘UserEntry’
>|
> 57 | myVal :: [String] -> (UserEntry -> String) -> IO (Either String String)
>|   ^
> make[1]: *** [Makefile:17: Build/SysConfig.hs] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/git-repair_1.20200102-2_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: git-repair
Source-Version: 1.20230814-1
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated git-repair 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: Tue, 19 Mar 2024 19:48:32 +0800
Source: git-repair
Architecture: source
Version: 1.20230814-1
Distribution: unstable
Urgency: medium
Maintainer: Sean Whitton 
Changed-By: Sean 

Processed: bug 1067141 is forwarded to https://github.com/t-paul/kcemu/issues/6

[Debian Bug Tracking System]

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

> forwarded 1067141 https://github.com/t-paul/kcemu/issues/6
Bug #1067141 [src:kcemu] kcemu: FTBFS with -Werror=implicit-function-declaration
Set Bug forwarded-to-address to 'https://github.com/t-paul/kcemu/issues/6'.
> thanks
Stopping processing here.

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

Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

[Michael R. Crusoe]

On Tue, 19 Mar 2024 12:16:16 +0100 Emanuele Rocca  wrote:
> Hi Andreas,
>
> On 2024-03-19 10:40, Andreas Tille wrote:
> > Since you all pinged that bug we now have another 4 weeks of time before
> > anything gets removed from testing. So we just need to bear the noise
> > from testing removal warnings of quite some packages (which I'd love to
> > get rid of thus uploading a fix would be great).
>
> I've uploaded a NMU to DELAYED/2: https://bugs.debian.org/1067147
>
> With those changes dcmtk builds fine on both armel and armhf. I've
> dropped the graphviz build-depend on those arches too, it can of course
> be reintroduced once graphviz become installable again.

Thanks, Emanuele; I've incorporated your changes on top of Sébastien Jodogne's 
very recent upload and will be uploading that shortly.

>

--
Michael R. Crusoe



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

[Emanuele Rocca]

Hi Andreas,

On 2024-03-19 10:40, Andreas Tille wrote:
> Since you all pinged that bug we now have another 4 weeks of time before
> anything gets removed from testing.  So we just need to bear the noise
> from testing removal warnings of quite some packages (which I'd love to
> get rid of thus uploading a fix would be great). 

I've uploaded a NMU to DELAYED/2: https://bugs.debian.org/1067147

With those changes dcmtk builds fine on both armel and armhf. I've
dropped the graphviz build-depend on those arches too, it can of course
be reintroduced once graphviz become installable again.

  Emanuele

Bug#1066798: marked as done (python-djangosaml2: FTBFS: ModuleNotFoundError: No module named 'saml2')

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 11:06:57 +
with message-id 
and subject line Bug#1066798: fixed in python-pysaml2 7.4.2-3
has caused the Debian Bug report #1066798,
regarding python-djangosaml2: FTBFS: ModuleNotFoundError: No module named 
'saml2'
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> debian/rules:16: warning: overriding recipe for target 'override_dh_auto_test'
> debian/rules:14: warning: ignoring old recipe for target 
> 'override_dh_auto_test'
> dh_auto_test -- --system=custom --test-args="cd {build_dir}; 
> DJANGO_SETTINGS_MODULE=tests.settings {interpreter} -m django test 
> djangosaml2.tests testprofiles"
> I: pybuild pybuild:308: cp -r /<>/tests 
> /<>/.pybuild/cpython3_3.12_django-saml2/build/; mv 
> /<>/.pybuild/cpython3_3.12_django-saml2/build/tests/testprofiles 
> /<>/.pybuild/cpython3_3.12_django-saml2/build/
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.12_django-saml2/build; 
> DJANGO_SETTINGS_MODULE=tests.settings python3.12 -m django test 
> djangosaml2.tests testprofiles
> Creating test database for alias 'default'...
> Found 52 test(s).
> Destroying test database for alias 'default'...
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/django/template/backends/django.py", 
> line 128, in get_package_libraries
> module = import_module(entry[1])
>  ^^^
>   File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>
>   File "", line 1387, in _gcd_import
>   File "", line 1360, in _find_and_load
>   File "", line 1331, in _find_and_load_unlocked
>   File "", line 935, in _load_unlocked
>   File "", line 995, in exec_module
>   File "", line 488, in _call_with_frames_removed
>   File 
> "/<>/.pybuild/cpython3_3.12_django-saml2/build/djangosaml2/templatetags/idplist.py",
>  line 17, in 
> from djangosaml2.conf import config_settings_loader
>   File 
> "/<>/.pybuild/cpython3_3.12_django-saml2/build/djangosaml2/conf.py",
>  line 24, in 
> from saml2.config import SPConfig
> ModuleNotFoundError: No module named 'saml2'
> 
> The above exception was the direct cause of the following exception:
> 
> Traceback (most recent call last):
>   File "", line 198, in _run_module_as_main
>   File "", line 88, in _run_code
>   File "/usr/lib/python3/dist-packages/django/__main__.py", line 9, in 
> 
> management.execute_from_command_line()
>   File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
> line 442, in execute_from_command_line
> utility.execute()
>   File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
> line 436, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File 
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py", 
> line 24, in run_from_argv
> super().run_from_argv(argv)
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
> 412, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
> 458, in execute
> output = self.handle(*args, **options)
>  ^
>   File 
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py", 
> line 68, in handle
> failures = test_runner.run_tests(test_labels)
>^^
>   File "/usr/lib/python3/dist-packages/django/test/runner.py", line 1060, in 
> run_tests
> self.run_checks(databases)
>   File "/usr/lib/python3/dist-packages/django/test/runner.py", line 977, in 
> run_checks
> call_command("check", verbosity=self.verbosity, databases=databases)
>   File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
> line 194, in call_command
> return command.execute(*args, **defaults)
>^^
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
> 458, in execute
> output = 

Bug#1067111: marked as done (python3-pysaml2: Python source files missing)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 11:06:57 +
with message-id 
and subject line Bug#1066798: fixed in python-pysaml2 7.4.2-3
has caused the Debian Bug report #1066798,
regarding python3-pysaml2: Python source files missing
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.)


-- 
1066798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pysaml2
Version: 7.4.2-1
Severity: serious
Justification: 10

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

starting with 7.4.2-1 all the Python source files for saml2 package are missing
in python3-pysaml2 binary package.

Regards,
Michael


- -- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 5.10.110-rockchip-rk3588 (SMP w/8 CPU threads)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_DK.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-pysaml2 depends on:
ii  python3  3.11.8-1
ii  python3-cffi 1.16.0-2
ii  python3-cffi-backend 1.16.0-2+b1
ii  python3-cryptography 41.0.7-5
ii  python3-dateutil 2.8.2-3
ii  python3-defusedxml   0.7.1-2
ii  python3-importlib-resources  6.0.1-1
ii  python3-mako 1.3.2-1
ii  python3-memcache 1.59-8
ii  python3-pyasn1   0.4.8-4
ii  python3-repoze.who   2.2-4
ii  python3-responses0.24.1-1
ii  python3-setuptools   68.1.2-2
ii  python3-xmlschema1.10.0-7
ii  xmlsec1  1.2.39-5+b1

python3-pysaml2 recommends no packages.

python3-pysaml2 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQFPBAEBCgA5FiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmX4VFsbHGZsYWRpc2No
ZXJtaWNoYWVsQGZsYWRpLmF0AAoJEP/TyIuZfdFqtJQH/AsZok55cBnZ1Mc5u1+b
pkmEj7IRvQBCPeiWmxF/WGmZTCJJKhzjb7jlWLqmLiI9gMg5R/QhgFXyVVXfbxWR
8pdh+fhYbDr0rp5uTP37R/8Agup0wMS5uJqVSTKEuGcXEb/n6UDoOqcnfGAGutN8
HJ/0U2ZbvAAUKYhqjsMaDD2pR/VFmHQozbF6tyvpUFmcg/mW0UPQBaWMfME7irwD
wvArzATaSMF5ufVe1++BKF1h4bpysO6/YlhFWNbbREICJASky7RO5veerveOlMm6
YkJ6gg1nazHqltL/V+cuSGBiChyEuu43ODZN1hgA+HMZyou9rQxFvrD/lMkdSvu+
M1A=
=VOju
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: python-pysaml2
Source-Version: 7.4.2-3
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
python-pysaml2, 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.
Thomas Goirand  (supplier of updated python-pysaml2 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: Tue, 19 Mar 2024 11:24:05 +0100
Source: python-pysaml2
Architecture: source
Version: 7.4.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1066798
Changes:
 python-pysaml2 (7.4.2-3) unstable; urgency=medium
 .
   * Correctly use export when setting PYBUILD_NAME (Closes: #1066798).
   * Copy scripts from .pybuild/cpython3_3.11_pysaml2, not just
 .pybuild/cpython3_3.11.
Checksums-Sha1:
 cf4ca503c2c9b8e31c72c1fea3ad4ee7bcc023fa 2628 python-pysaml2_7.4.2-3.dsc
 3ed5fa7a23e03b733e83ca8113e92a5c138ea9c2 7776 
python-pysaml2_7.4.2-3.debian.tar.xz
 db74c127d5047950558583fc0030db9b57bb7410 9767 
python-pysaml2_7.4.2-3_amd64.buildinfo
Checksums-Sha256:
 f8bff43df0e5ac975e52e1fc35085ce8e98ed540a8b030bf03f9064946a5ffac 2628 
python-pysaml2_7.4.2-3.dsc
 cbb1eb4f129ae8f7c0fbb594e78451767d1a4d6a8bf8b9d959d9da1045f612d4 7776 
python-pysaml2_7.4.2-3.debian.tar.xz
 25ee2ee01b0d575d8b7d9fc4d8c5a1e3912c10ad3c4d8ae9ab0c082aab5e95f1 9767 
python-pysaml2_7.4.2-3_amd64.buildinfo
Files:
 ec5a163102877b50f4f6d9173461bc31 2628 python optional 
python-pysaml2_7.4.2-3.dsc
 16a39b2260d06fad657acdba5c9b73be 7776 python optional 
python-pysaml2_7.4.2-3.debian.tar.xz
 942c72e15f1f00f95629311e6c94a5f8 9767 

Bug#1066317: marked as done (montage: FTBFS: two_plane.c:680:8: error: implicit declaration of function ‘isnan’ [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 11:04:38 +
with message-id 
and subject line Bug#1066317: fixed in montage 6.0+dfsg-9
has caused the Debian Bug report #1066317,
regarding montage: FTBFS: two_plane.c:680:8: error: implicit declaration of 
function ‘isnan’ [-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.)


-- 
1066317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: montage
Version: 6.0+dfsg-8
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 
> -fcommon -fPIC -ansi -I. -I../../include -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/wcstools -I/usr/include/freetype2  -c -o two_plane.o 
> two_plane.c
> two_plane.c: In function ‘Initialize_TwoPlane’:
> two_plane.c:680:8: error: implicit declaration of function ‘isnan’ 
> [-Werror=implicit-function-declaration]
>   680 | if(isnan(invdet)){
>   |^
> cc1: some warnings being treated as errors
> make[4]: *** [: two_plane.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/montage_6.0+dfsg-8_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: montage
Source-Version: 6.0+dfsg-9
Done: Ole Streicher 

We believe that the bug you reported is fixed in the latest version of
montage, 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.
Ole Streicher  (supplier of updated montage 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: Tue, 19 Mar 2024 11:36:18 +0100
Source: montage
Architecture: source
Version: 6.0+dfsg-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 1066317
Changes:
 montage (6.0+dfsg-9) unstable; urgency=medium
 .
   * Include string.h in mPresentation.c to declare strcpy() (Closes: #1066317)
Checksums-Sha1:
 9c0f5adae1c4a962ab54e12e3eee113010ab54eb 2258 montage_6.0+dfsg-9.dsc
 6b17ff6bf803495b46485f5ca3907209254056a6 55380 montage_6.0+dfsg-9.debian.tar.xz
Checksums-Sha256:
 81a6c35a7e1ae5d025104ba227de2e0dd0c1ceff8fc217bd5a1b97f97d8eeef4 2258 
montage_6.0+dfsg-9.dsc
 ec242efc72eb7d40fe96361d12e4dfe7544d123d8553890de71f37d96df5a744 55380 
montage_6.0+dfsg-9.debian.tar.xz
Files:
 1f4ded8e006e1678a23784fcfb289e9a 2258 science optional montage_6.0+dfsg-9.dsc
 706fe85f0cde7497c58cfa12724bd94f 55380 science optional 
montage_6.0+dfsg-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmX5a7EACgkQcRWv0HcQ
3Pc8SxAAhFf9QM7ApeyEIFd+rTjyhji3EtHS6WPwDuN8vH0mvvVjf/D8oQ5mqNJz
HPL6Mm/V/ep2RoX37RsRk7YYLrH3CmO44E6ibIj6vrpoN3uAoWhVEvJgoEiNpU9i
GPXNCzaUumUlBCjkOrQmRlUWF4ym6CmLBhG5opT7VvdBD0YqWTNrpVyd185qcMBi

Processed: bookworm-pu: package hovercraft/2.7-6~deb12u1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:hovercraft
Bug #1067149 [release.debian.org] bookworm-pu: package hovercraft/2.7-6~deb12u1
Added indication that 1067149 affects src:hovercraft
> block 1025655 with -1
Bug #1025655 {Done: Andreas Beckmann } [hovercraft] 
hovercraft: requires python3-setuptools
1025655 was not blocked by any bugs.
1025655 was not blocking any bugs.
Added blocking bug(s) of 1025655: 1067149
> affects 1067148 + src:hovercraft
Bug #1067148 [release.debian.org] bullseye-pu: package hovercraft/2.7-2+deb11u1
Added indication that 1067148 affects src:hovercraft
> block 1025655 with 1067148
Bug #1025655 {Done: Andreas Beckmann } [hovercraft] 
hovercraft: requires python3-setuptools
1025655 was blocked by: 1067149
1025655 was not blocking any bugs.
Added blocking bug(s) of 1025655: 1067148

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

Bug#1067137: marked as done (harmonypy: missing depend on python3-all for autopkgtest)

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 10:49:20 +
with message-id 
and subject line Bug#1067137: fixed in harmonypy 0.0.9-3
has caused the Debian Bug report #1067137,
regarding harmonypy: missing depend on python3-all for autopkgtest
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.)


-- 
1067137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: harmonypy
Version: 0.0.9-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

your package has an autopkgtest regression due to changes in NumPy.
The python3-numpy package no longer depends on all supported Python 
versions. You need to depend on python3-all if you want to run your 
tests against all supported Python releases.

Cheers
Timo



-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmX5Ya8ACgkQ+C8H+466
LVnbFgwAgMo8/cuq3/uIEV1LUQXPgfGWveb3mRN1bViYSEc7xIiRR0Sv3AhV4L5g
4CuLL6aRE6X46l83Q+56DgCAgNQ8O53O0a0kzpYfnXMNiNeU9XBP8+CH6yqyyq4V
rCvFyVxjVPuDFE+Lq1JQq+INNtYzHoPGRWbh0Fxz7ax1XsihNBp4QjxrHSLUsELK
PaLJZTrUr4G0LFKaDWXKb7Vo8j9em+di6S7Jbh67YMmoeDKSx4+Ly9m6kkx+wDUM
qoLWd1c0Jj2ArHB1sGx4abqNE36T0knbJRIFFi8izyZoNGYOmYG1H3jPKpVo7jxA
EFA2sl2dW/GH9LvOearHynBlK/pYn1yi6ghgouV8lGi3TZkYKeo8Ih8NM3yfRpZ3
RvPx8ZKJeh59eLo09hlOysRohJKDC7uT109701iTy7mzZZJ8LzWMIfOHwnvvYmgy
/pgmYwgYBMHYYoZTSVsbxsORtmbyRg44JKrxt0gSV3xHx98weWGY1tzTatdX7vvw
14yLQvNU
=9kzA
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: harmonypy
Source-Version: 0.0.9-3
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated harmonypy 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: Tue, 19 Mar 2024 11:15:32 +0100
Source: harmonypy
Architecture: source
Version: 0.0.9-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 1067137
Changes:
 harmonypy (0.0.9-3) unstable; urgency=medium
 .
   * Team upload.
   * Test-Depends: python3-all
 Closes: #1067137
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
Checksums-Sha1:
 65938ed87a261c8f4999775635c98d21984f579d 2136 harmonypy_0.0.9-3.dsc
 478bb13c1a46aa514bbdad0e1f043614ce58134f 2956 harmonypy_0.0.9-3.debian.tar.xz
 1a19ec81bfecd20802c4459557a2a2c93d7e15c1 7310 harmonypy_0.0.9-3_amd64.buildinfo
Checksums-Sha256:
 7a7d62b513073f7d61acfb08489154d2fab8f64b632e03a56eca698e14a8030f 2136 
harmonypy_0.0.9-3.dsc
 3a03d9c323a515d1b6cd51c3beb1f8a3bc11f04c0fb4bc8015a53718bed28d30 2956 
harmonypy_0.0.9-3.debian.tar.xz
 6e564a6b88513dbce7fd868e30644f1cb288b38ec3cd2ce1abecd1100bf852a7 7310 
harmonypy_0.0.9-3_amd64.buildinfo
Files:
 6c89abbbe875d70f43aeb363b9976f97 2136 science optional harmonypy_0.0.9-3.dsc
 5bf96f288ac4fee31d02e09c06ebb439 2956 science optional 
harmonypy_0.0.9-3.debian.tar.xz
 0ca12f7cfef15047d19368cc1a1011e0 7310 science optional 
harmonypy_0.0.9-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmX5ZzoRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEWNw//S0+nvN2g5jJwKiP2qW9A8SxAClz8qHja
3dYfcC1EJlU4t5Ou/cXXVoFt72dWb/YwJm5r4M9Trhg+yBqWX3IMj+Eh4KCd2Cbo
BVL/bWUP3OLxt0xy2EwAzTXkINnuc8AAkAxUAr28UhiXVfyImgWykpnWbCRia/sJ
29wAzxMWDz35gtPf8j6lHwFnMcT58hb7XboD8FZMLvTmOtc+0BTpcbEOGT1SCFNc
tZR3LCYa2T5Acds/rFE3nvfKDbX4Lw5hMAaYEi8oYm3JmBqK1Mcud3ZPUZp22JaY
co6KNBetz+CpJOzwgSnsu2I1K/EHTRq1RNgRllIFQLJlGIbRBlleyrx4KtwzW3Gl
AMvDNvFL0uXuRpYa2xBUPQhC0XSkGgKvDj9IqcaEiQLbJts7lxjkB6hBqVOYi0GX
6MY8KjdXuS1isgpafmTrXiajUqHn+3HIjUQ4dcwOVY0HasvAF3tiN8RgW4uTsodj
QwXv1IK2ze1lGFeKZByydKt+jWlPvEAVB7xEj6m+2gf6ZftMjyegq3AIgc95g/Ew
3uA6TGSixReNdEAqZdVAhdkEiRYKJF+uGh+tQ60xDdLty7qc2PMLfx2R6bRR+0lc
jj8e0COhqe4N6qAUpQx5Dq65QJffRbTZNyY8Ro3Ns9w+Yf1VEIsmfrHhZnxgEE2d
YtiyKBADL0s=
=wra8
-END PGP SIGNATURE-



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

Processed: Bug#1066798 marked as pending in python-pysaml2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1066798 [python3-pysaml2] python-djangosaml2: FTBFS: ModuleNotFoundError: 
No module named 'saml2'
Bug #1067111 [python3-pysaml2] python3-pysaml2: Python source files missing
Added tag(s) pending.
Added tag(s) pending.

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

Bug#1066798: marked as pending in python-pysaml2

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1066798 in python-pysaml2 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/openstack-team/python/python-pysaml2/-/commit/c1d074447eaf36234d55229952479afc4d496a1b


Correctly use export when setting PYBUILD_NAME (Closes: #1066798).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066798

Bug#1064086: marked as done (libapache2-mod-netcgi-apache: breaks apache (undefined symbols))

[Debian Bug Tracking System]

Your message dated Tue, 19 Mar 2024 10:37:09 +
with message-id 
and subject line Bug#1064086: fixed in ocamlnet 4.1.9-5
has caused the Debian Bug report #1064086,
regarding libapache2-mod-netcgi-apache: breaks apache (undefined symbols)
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.)


-- 
1064086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-netcgi-apache
Version: 4.1.9-1+b1
Severity: grave
File: /usr/share/doc/libapache2-mod-netcgi-apache/changelog.gz
Justification: renders package unusable

Dear Maintainer,

After installing libapache2-mod-netcgi-apache, apache can't start again.

The following error is produced:

netcgi_apache.load: Can't locate API module structure `netcgi_apache_module' in 
file /usr/lib/apache2/modules/mod_netcgi_apache.so: 
/usr/lib/apache2/modules/mod_netcgi_apache.so: undefined symbol: 
netcgi_apache_module
Action 'restart' failed.

The Apache server must be restarted after disabling the module.

(the same behaviour is also seen in Debian 11.9)


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

Kernel: Linux 6.1.0-18-amd64 (SMP w/12 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 libapache2-mod-netcgi-apache depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.57-2
ii  libc6   2.36-9+deb12u4
ii  libocamlnet-ocaml-dev   4.1.9-1+b1

libapache2-mod-netcgi-apache recommends no packages.

libapache2-mod-netcgi-apache suggests no packages.

-- Configuration Files:
/etc/apache2/mods-available/netcgi_apache.load changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ocamlnet
Source-Version: 4.1.9-5
Done: Stéphane Glondu 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated ocamlnet 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: Tue, 19 Mar 2024 11:11:20 +0100
Source: ocamlnet
Architecture: source
Version: 4.1.9-5
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 1064086
Changes:
 ocamlnet (4.1.9-5) unstable; urgency=medium
 .
   * Fix netcgi loading in Apache (Closes: #1064086)
Checksums-Sha1:
 23cf66d1b26e38e14504acddd5f973e2de9d 2417 ocamlnet_4.1.9-5.dsc
 63ed7dede0a4e3abe77bcee47994f6b0ece66468 16624 ocamlnet_4.1.9-5.debian.tar.xz
Checksums-Sha256:
 33472071f0b64dd7f6fff282ffb0d40f50791494ca0b1f19ff5c0ea72d5b4f4c 2417 
ocamlnet_4.1.9-5.dsc
 839076e3bc5884f936ad6e01e20f75122a11d555c020aeba04be322b9e010470 16624 
ocamlnet_4.1.9-5.debian.tar.xz
Files:
 07e274ca8222822643d20049a382e02e 2417 ocaml optional ocamlnet_4.1.9-5.dsc
 aff3d5eb3d973b5447018bab5e872c72 16624 ocaml optional 
ocamlnet_4.1.9-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmX5ZpASHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCB3XUIAKNQ/PrT0WxAC0iTKYw4W98UJpYm/DsQ
r9UkUPuZ+3XrB2qCLHIN2hxgCjeTOgX/nEhXQN+lnt9OFaZXwc8bDL+mbpLYfNHK
S6Sc8RAubD9KUoTUSzG+R7bRgyejm+NBuTpJt7zTJNjD0rrrIqOLO1LmNnH8YWX2
yeEskRsu6HgBSelmu6/jd7y2r367YrUcwBmUG+tVUxN/bEtSfm6Dw5HiiHHzCckm
lY215TKD3VCVuLhUDZ8iVpo6BZ4GF8deLFW6fjvwHHU7bENFPsUQPKD385Mi2w6j
oRAOOvk1eO3CgoIgUZlVnZ+k6tMXt0FmA7W0M+Li+QydDDrsQIf4GmY=
=8epD
-END PGP SIGNATURE-



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

Bug#1066440: librep: FTBFS with -Werror=implicit-function-declaration

[Andreas Beckmann]

Followup-For: Bug #1066440
Control: found -1 0.92.7-1
Control: retitle -1 librep: FTBFS with -Werror=implicit-function-declaration

The relevant part from the log seems to be this:

...
checking for aclocal directory... /usr/share/aclocal
checking for data type to store Lisp values... configure: error: cannot find 
Lisp value type; set --with-value-type (see README)


configure:15875: checking for data type to store Lisp values
configure:15898: gcc -o conftest -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 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
conftest.c  -lcrypt >&5
conftest.c:93:1: warning: return type defaults to 'int' [-Wimplicit-int]
   93 | main () { exit (!(sizeof (int) >= sizeof (void *)));}
  | ^~~~
conftest.c: In function 'main':
conftest.c:93:11: error: implicit declaration of function 'exit' 
[-Werror=implicit-function-declaration]
   93 | main () { exit (!(sizeof (int) >= sizeof (void *)));}
  |   ^~~~
conftest.c:1:1: note: include '' or provide a declaration of 'exit'
  +++ |+#include 
1 | /* confdefs.h */
conftest.c:93:11: warning: incompatible implicit declaration of built-in 
function 'exit' [-Wbuiltin-declaration-mismatch]
   93 | main () { exit (!(sizeof (int) >= sizeof (void *)));}
  |   ^~~~
conftest.c:93:11: note: include '' or provide a declaration of 'exit'
cc1: some warnings being treated as errors
configure:15898: $? = 1
configure: program exited with status 1


For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration


Andreas