date:20240415

Bug#1067916: marked as done (FTBFS: tests failed)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Tue, 16 Apr 2024 05:49:13 +
with message-id 
and subject line Bug#1067916: fixed in capnproto 1.0.1-4
has caused the Debian Bug report #1067916,
regarding FTBFS: tests failed
to be marked as done.

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

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


-- 
1067916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: capnproto
Version: 1.0.1-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=capnproto=armhf=1.0.1-3%2Bb2=1711652087=0

[ TEST ] kj/mutex-test.c++:262: legacy test: Mutex/WhenWithTimeout
kj/mutex-test.c++:321: failed: expected t >= 10 * kj::MILLISECONDS [20.039μs >=
10ms]; t = 20.039μs
stack: 74ee05 74b4a9 f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f
f76797d9 f767987d
kj/mutex-test.c++:329: failed: expected t >= 20 * kj::MILLISECONDS [92.405μs >=
20ms]; t = 92.405μs
stack: 74ee05 74b525 f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f
f76797d9 f767987d
kj/mutex-test.c++:373: failed: expected clock.now() - start >= 10 *
kj::MILLISECONDS [12.208μs >= 10ms]
stack: 74eacb 74b5b9 f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f
f76797d9 f767987d
[ FAIL ] kj/mutex-test.c++:262: legacy test: Mutex/WhenWithTimeout (47479 μs)
[ TEST ] kj/mutex-test.c++:391: legacy test: Mutex/WhenWithTimeoutPreciseTiming
kj/mutex-test.c++:412: failed: expected t >= 100 * kj::MILLISECONDS [11.64μs >=
100ms]
stack: 74a51d f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f f76797d9
f767987d
[ FAIL ] kj/mutex-test.c++:391: legacy test: Mutex/WhenWithTimeoutPreciseTiming
(40 μs)
[ TEST ] kj/mutex-test.c++:422: legacy test:
Mutex/WhenWithTimeoutPreciseTimingAfterInterrupt
kj/mutex-test.c++:446: failed: expected t >= 100 * kj::MILLISECONDS [12.647μs
>= 100ms]; t / kj::MILLISECONDS = 0
stack: 74eca3 74a27f f798e8b5 f798ee41 f798f313 f797481f f79761db f798db1f
f76797d9 f767987d
[ FAIL ] kj/mutex-test.c++:422: legacy test:
Mutex/WhenWithTimeoutPreciseTimingAfterInterrupt (10139 μs)


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: capnproto
Source-Version: 1.0.1-4
Done: tony mancill 

We believe that the bug you reported is fixed in the latest version of
capnproto, 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.
tony mancill  (supplier of updated capnproto 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: Mon, 15 Apr 2024 22:09:51 -0700
Source: capnproto
Architecture: source
Version: 1.0.1-4
Distribution: unstable
Urgency: medium
Maintainer: Tom Lee 
Changed-By: tony mancill 
Closes: 1067916
Changes:
 capnproto (1.0.1-4) unstable; urgency=medium
 .
   * Add patch for FTBFS on 32-bit ARM after the time_t 64 transition.
 Thank you to Arnd Bergmann, Wookey, Tom Lee, and Andrey Rakhmatullin
 for their for help resolving this bug.  (Closes: #1067916)
Checksums-Sha1:
 e6b4dfd714b3f83cd7bcb49b9462f27144a2488f 2225 capnproto_1.0.1-4.dsc
 9a448cf37935f4c0153f376d48f3cb22b242837a 17568 capnproto_1.0.1-4.debian.tar.xz
 f0dfd6784e75ae8373dda21ab41aa029614495ff 8912 capnproto_1.0.1-4_amd64.buildinfo
Checksums-Sha256:
 da18b35ab647231b2108bf376055a9c4cf300c95ce9a9caa346a9cf80f09 2225 
capnproto_1.0.1-4.dsc
 337b9ae1d2c20f8fa5462822fcc9973f142f4bf2b88d02445d68dcb42f20a6aa 17568 
capnproto_1.0.1-4.debian.tar.xz
 1176615659924fa0cbdb9869e8cbd6766999449a0bdb9c38f0aff665c04127b7 8912 
capnproto_1.0.1-4_amd64.buildinfo
Files:
 992c04e0af536be904a5bf8248333185 2225 devel optional

Processed: Re: Bug#1069073: lua-mode: FTBFS: failing tests

2024-04-15 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 pending
Bug #1069073 [src:lua-mode] lua-mode: FTBFS: failing tests
Added tag(s) pending.

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

Bug#1069073: lua-mode: FTBFS: failing tests

2024-04-15 Thread Xiyue Deng

Control: tags -1 pending

Hi,

I have committed a fix to the team repo (together with other tweaks) and
prepared a package on mentors.  See Bug#1069078[1] for the RFS request.
Please help sponsoring.  TIA!

-- 
Xiyue Deng

[1] https://bugs.debian.org/1069078

Bug#1057586: nvda2speechd: FTBFS: error: failed to run custom build command for `speech-dispatcher-sys v0.7.0`

2024-04-15 Thread Samuel Thibault

Sebastian Ramacher, le lun. 15 avril 2024 05:41:48 +0200, a ecrit:
> On 2024-04-14 14:19:18 +0200, Santiago Vila wrote:
> > El 14/4/24 a las 13:25, Sylvestre Ledru escribió:
> > > I am sorry but I am not sure to see how it is actionable.
> > > 
> > > Without a test case, i don't think there is much I can do here.
> > 
> > The test case is that nvda2speechd fails to build from source.
> > > With rust, cargo, custom build script, there are many things that can go 
> > > wrong before LLVM.
> > > 
> > > Sebastian, I think it could be move to normal. From LLVM perspective, it 
> > > isn't serious severity (many programs are built with LLVM 16).
> > 
> > We can release trixie with compilers having bugs, but I don't think it 
> > would be ok at
> > all to release trixie as stable with packages which do not build from 
> > source, that would
> > be against Release Policy.
> > 
> > So, in my opinion, this is still RC, either in the compiler or in the 
> > package failing
> > to build. If solving this in the compiler is too complex, then the bug 
> > should be reassigned back to src:nvda2speechd.
> 
> Given that nvda2speechd downloads rust and plenty of crates during the
> build, it will have to prevent odd interactions with the system provided
> LLVM. Let's keep this as RC bug against nvda2speechd.

The problem is that bindgen insists on interacting with the
system-provided LLVM:

https://github.com/rust-lang/rust-bindgen/blob/main/bindgen/lib.rs#L620

It force-loads libclang, and when that's libclang16, we get the bug.

For now I "fixed" the bug by dropping the rust/cargo/clang build-deps
entirely, and build-dep on libclang 14 rather than 16.

I don't know why the issue shows up only when building
speech-dispatcher-sys, perhaps that's just because it's the only crate
that uses bindgen.

Samuel

Bug#1067319: marked as done (gap-polymaking: FTBFS: Can't load '/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so' for module Polymake::Ext: libflint.so.18: cannot

2024-04-15 Thread Debian Bug Tracking System

Your message dated Tue, 16 Apr 2024 03:49:40 +
with message-id 
and subject line Bug#1067319: fixed in gap-polymaking 0.8.7-2
has caused the Debian Bug report #1067319,
regarding gap-polymaking: FTBFS: Can't load 
'/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so'
 for module Polymake::Ext: libflint.so.18: cannot open shared object file: No 
such file or directory at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm 
line 201.
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> gap -q -l "/<>/debian/gaproot;/usr/share/gap" < tst/testall.g | 
> tee debian/gap.tst
> true
> [ "visual.tst" ]
> Architecture: x86_64-pc-linux-gnu-default64-kv8
> 
> testing: /<>/debian/gaproot/pkg/\
> polymaking/tst/example.tst
> Can't load 
> '/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so'
>  for module Polymake::Ext: libflint.so.18: cannot open shared object file: No 
> such file or directory at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm 
> line 201.
>  at /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> Compilation failed in require at 
> /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> BEGIN failed--compilation aborted at 
> /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> Compilation failed in require at /usr/share/polymake/perllib/Polymake.pm line 
> 29.
> BEGIN failed--compilation aborted at /usr/share/polymake/perllib/Polymake.pm 
> line 29.
> Compilation failed in require at /usr/bin/polymake line 156.
> BEGIN failed--compilation aborted at /usr/bin/polymake line 156.
> Can't load 
> '/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so'
>  for module Polymake::Ext: libflint.so.18: cannot open shared object file: No 
> such file or directory at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm 
> line 201.
>  at /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> Compilation failed in require at 
> /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> BEGIN failed--compilation aborted at 
> /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> Compilation failed in require at /usr/share/polymake/perllib/Polymake.pm line 
> 29.
> BEGIN failed--compilation aborted at /usr/share/polymake/perllib/Polymake.pm 
> line 29.
> Compilation failed in require at /usr/bin/polymake line 156.
> BEGIN failed--compilation aborted at /usr/bin/polymake line 156.
> Can't load 
> '/usr/lib/polymake/perlx/5.38.2/x86_64-linux-gnu-thread-multi/auto/Polymake/Ext/Ext.so'
>  for module Polymake::Ext: libflint.so.18: cannot open shared object file: No 
> such file or directory at /usr/lib/x86_64-linux-gnu/perl-base/DynaLoader.pm 
> line 201.
>  at /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> Compilation failed in require at 
> /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> BEGIN failed--compilation aborted at 
> /usr/share/polymake/perllib/Polymake/Namespaces.pm line 18.
> Compilation failed in require at /usr/share/polymake/perllib/Polymake.pm line 
> 29.
> BEGIN failed--compilation aborted at /usr/share/polymake/perllib/Polymake.pm 
> line 29.
> Compilation failed in require at /usr/bin/polymake line 156.
> BEGIN failed--compilation aborted at /usr/bin/polymake line 156.
> [34m> Diff in /<>/debia\
> n/gaproot/pkg/polymaking/tst/example.tst:11[0m
> [34m# Input is:[0m
> Polymake(permutahedron,"VOLUME");
> [0m[2K[34m# Expected output:[0m
> [30m[42m3
> [0m[2K[34m# But found:[0m
> [37m[41mError, polymake returned an error (error code 2)
> [0m[2K[34m[0m
> [34m> Diff in /<>/debia\
> n/gaproot/pkg/polymaking/tst/example.tst:13[0m
> [34m# Input is:[0m
> Polymake(permutahedron,"N_VERTICES");
> [0m[2K[34m# Expected output:[0m
> [30m[42m6
> [0m[2K[34m# But found:[0m
> [37m[41mError, polymake returned an error (error code 2)
> [0m[2K[34m[0m
> [34m> Diff in /<>/debia\
> n/gaproot/pkg/polymaking/tst/example.tst:17[0m
> [34m# Input is:[0m
> NamesKnownPropertiesOfPolymakeObject(permutahedron);
> [0m[2K[34m# Expected

Bug#1067621: marked as done (FTBFS on 32-bit time64 architectures: error: implicit declaration of function ‘gzopen64’)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Tue, 16 Apr 2024 03:10:05 +
with message-id 
and subject line Bug#1069032: Removed package(s) from unstable
has caused the Debian Bug report #1067621,
regarding FTBFS on 32-bit time64 architectures: error: implicit declaration of 
function ‘gzopen64’
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.)


-- 
1067621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: berkeley-abc
Version: 1.01+20230625git01b1bd1+dfsg-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=berkeley-
abc=armel=1.01%2B20230625git01b1bd1%2Bdfsg-3%2Bb2=1711273244=0

In file included from src/base/io/ioReadBlifMv.c:21:
src/base/io/ioReadBlifMv.c: In function ‘Io_MvLoadFileGz’:
./src/misc/zlib/zlib.h:1583:18: error: implicit declaration of function
‘gzopen64’; did you mean ‘gzopen’? [-Werror=implicit-function-declaration]
 1583 | #  define gzopen gzopen64


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

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 1.01+20230625git01b1bd1+dfsg-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#999077: marked as done (msp430-libc: missing required debian/rules targets build-arch and/or build-indep)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Tue, 16 Apr 2024 03:03:34 +
with message-id 
and subject line Bug#1069021: Removed package(s) from unstable
has caused the Debian Bug report #999077,
regarding msp430-libc: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: msp430-libc
Version: 20120224-1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 20120224-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#965732: marked as done (msp430-libc: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Tue, 16 Apr 2024 03:03:34 +
with message-id 
and subject line Bug#1069021: Removed package(s) from unstable
has caused the Debian Bug report #965732,
regarding msp430-libc: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: msp430-libc
Version: 20120224-1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package msp430-libc uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 20120224-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#965541: marked as done (gcc-msp430: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Tue, 16 Apr 2024 03:04:21 +
with message-id 
and subject line Bug#1069021: Removed package(s) from unstable
has caused the Debian Bug report #965541,
regarding gcc-msp430: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-msp430
Version: 4.6.3~mspgcc-20120406-7.1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package gcc-msp430 uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 4.6.3~mspgcc-20120406-7.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#1062032: marked as done (c-ares: NMU diff for 64-bit time_t transition)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 23:34:27 +
with message-id 
and subject line Bug#1062032: fixed in c-ares 1.27.0-1.2
has caused the Debian Bug report #1062032,
regarding c-ares: NMU diff for 64-bit time_t transition
to be marked as done.

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

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


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

Dear maintainer,

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

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

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for c-ares
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

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



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

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru c-ares-1.26.0/debian/changelog c-ares-1.26.0/debian/changelog
--- c-ares-1.26.0/debian/changelog  2024-01-27 15:57:37.0 +
+++ c-ares-1.26.0/debian/changelog  2024-01-31 03:14:49.0 +
@@ -1,3 +1,10 @@
+c-ares (1.26.0-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Wed, 31 Jan 2024 03:14:49 +
+
 c-ares (1.26.0-1) unstable; urgency=low
 
   * Imported Upstream version 1.26.0
diff -Nru c-ares-1.26.0/debian/control c-ares-1.26.0/debian/control
--- c-ares-1.26.0/debian/control2023-12-17 14:41:52.0 +
+++ c-ares-1.26.0/debian/control2024-01-31 03:14:48.0 +
@@ -16,7 +16,7 @@
 Section: libdevel
 Architecture: any
 Conflicts: libares-dev
-Depends: libc-ares2 (= ${binary:Version}),
+Depends: libc-ares2t64 (= ${binary:Version}),
  ${shlibs:Depends},
  ${misc:Depends}
 Multi-Arch: same
@@ -31,10 +31,12 @@
  .
  This package contains development files (headers and static libraries).
 
-Package: libc-ares2
+Package: libc-ares2t64
+Provides: ${t64:Provides}
+Breaks: libc-ares2 (<< ${source:Version})
 Conflicts: libcares2
 Architecture: any
-Replaces: libc-ares1
+Replaces: libc-ares2, libc-ares1
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Pre-Depends: ${misc:Pre-Depends}
 Multi-Arch: same
diff -Nru c-ares-1.26.0/debian/libc-ares2.dirs 
c-ares-1.26.0/debian/libc-ares2.dirs
--- c-ares-1.26.0/debian/libc-ares2.dirs2023-05-22 15:13:13.0 
+
+++ c-ares-1.26.0/debian/libc-ares2.dirs1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib
diff -Nru c-ares-1.26.0/debian/libc-ares2.install 
c-ares-1.26.0/debian/libc-ares2.install
--- c-ares-1.26.0/debian/libc-ares2.install 2023-05-22 15:13:13.0 
+
+++ c-ares-1.26.0/debian/libc-ares2.install 1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
diff -Nru c-ares-1.26.0/debian/libc-ares2.lintian-overrides 
c-ares-1.26.0/debian/libc-ares2.lintian-overrides
---

Bug#1068072: marked as done (Hardcoded dependency on liblcmaps0)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 22:35:30 +
with message-id 
and subject line Bug#1068072: fixed in lcmaps-plugins-basic 1.7.1-2
has caused the Debian Bug report #1068072,
regarding Hardcoded dependency on liblcmaps0
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.)


-- 
1068072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
source: lcmaps-plugins-basic
version: 1.7.1-1
severity: serious

During the 64 bit time_t transition the package name liblcmaps0 was
changed to liblcmaps0t64. The old name is still provided by the new
package for architectures where this transition did not cause an ABI
break, but not for architectures like armel and armhf, where these
hardcoded dependency on the old package name are now not satisfiable.

Please change these to use either the new name or to depend on either
the old or the new name (liblcmaps0 | liblcmaps0t64).

Package: lcmaps-plugins-basic-dummy
Depends: ${misc:Depends}, ${shlibs:Depends}, liblcmaps0

Package: lcmaps-plugins-basic-localaccount
Depends: ${misc:Depends}, ${shlibs:Depends}, liblcmaps0

Package: lcmaps-plugins-basic-poolaccount
Depends: ${misc:Depends}, ${shlibs:Depends}, liblcmaps0

Package: lcmaps-plugins-basic-posixenf
Depends: ${misc:Depends},  ${shlibs:Depends}, liblcmaps0

Package: lcmaps-plugins-basic-ldap
Depends: ${misc:Depends},  ${shlibs:Depends}, liblcmaps0

Mattias



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: lcmaps-plugins-basic
Source-Version: 1.7.1-2
Done: Dennis van Dok 

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

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

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

Debian distribution maintenance software
pp.
Dennis van Dok  (supplier of updated lcmaps-plugins-basic 
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: Mon, 15 Apr 2024 23:57:46 +0200
Source: lcmaps-plugins-basic
Architecture: source
Version: 1.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Dennis van Dok 
Changed-By: Dennis van Dok 
Closes: 1068072
Changes:
 lcmaps-plugins-basic (1.7.1-2) unstable; urgency=medium
 .
   * Update to address 64 bit time_t transition (Closes: 1068072)
Checksums-Sha1:
 eb1ac8f15fdd768426682e52718355f3723c44df 2566 lcmaps-plugins-basic_1.7.1-2.dsc
 0c55a710fa56fe313edfa0b02414b3debad9b176 3196 
lcmaps-plugins-basic_1.7.1-2.debian.tar.xz
 0393887d847c18c980cf31c0939882e927c5d71b 6452 
lcmaps-plugins-basic_1.7.1-2_source.buildinfo
Checksums-Sha256:
 99506ced463e3fffec4f2ede5748982c3b522a171d578bdc4ef23c0ae04bb887 2566 
lcmaps-plugins-basic_1.7.1-2.dsc
 b579d1f81ec8b7b707f02c9f512058d9f357d114e4302f6a7940e734a7e13489 3196 
lcmaps-plugins-basic_1.7.1-2.debian.tar.xz
 5bfd164a043186d17cfaff481c24bdaa3ba9b03c69f002534e59601d6df21979 6452 
lcmaps-plugins-basic_1.7.1-2_source.buildinfo
Files:
 d428f349634fc2b8b39530afb41bdcd4 2566 libs optional 
lcmaps-plugins-basic_1.7.1-2.dsc
 4138120bd237c76c81eb515805322b7c 3196 libs optional 
lcmaps-plugins-basic_1.7.1-2.debian.tar.xz
 e9e750e21038552f9f075e440a7facb4 6452 libs optional 
lcmaps-plugins-basic_1.7.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWGm4u3eUE64rvBHj3/rYGXYX7xkFAmYdpesACgkQ3/rYGXYX
7xlYCRAAts+NWgMUlVPclvtMcwnSki2tD6oRf3yBRTI/8k2U0VIPhEZcmol9TNEU
Nd6nC4DjdVASvFnJgKO9Sw0czPejapnOL53Ze5jdJegFRjM9T9zQbS0qSeYYono0
Ko+MLXTT8ce6w56s29OfuO5D1ST3QVFGWyJ9RxWWxdQQ+MPaqrEsJJvFYsszN8Qk
7nO+YhNuO5D1dMAncY0TVTf7gJh+Dzrm942bUF2pHTP3nXRO7q+wK3idcaPEulEG
5sHz6m2/5Q8n09mWzs/jC4izNCohxjyc4q3LQNEdculXp68r0bQcAqXj3BUB3m/E
WjWCpHm96DRDuRH+icfC2+e3TDslB8lajyd3AgSjCJR7SKGBVkXnu1+wob8VCHLK
AJgyiE/ZxeulHPDYT7RUhgI8aoWtZ97hyo00Usa2rRGOrHwv+s5FPxv8dfH9Eslz
PuRfwILmKENO938/9ozI0gDoX+nwMgBYRUAVUP5vTXEKMLbMRlJd1vI2s1MTmBEn
Es61AJqOEccc0MYSJ3wN4zM4O7Y52ddGcf/WZlxy6ptGmAXN6+1vjjSfoOuJBeGD
ZI+FhkY+JpZMUc2pxkAlaevGp/lILNObCNkLvMqd9oHQ2Y+nrLHWioNX9GBybtzY
fqcEtI/79hmym6rUX29Hvx2rv8c4n8En0gT5seU+GNgum2VA4jE=
=fDsV
-END PGP SIGNATURE-



pgpcPyQIJ2wsC.pgp
Description: PGP signature

Bug#1064730: stdgpu: FTBFS: type_traits.h:736:1: error: expected type-specifier before ‘template’

2024-04-15 Thread Cordell Bloor


Hi Timo,

On Sat, 2 Mar 2024 09:21:43 +0100 Timo =?utf-8?Q?R=C3=B6hling?= 
 wrote:


>
> On Sun, 25 Feb 2024 20:28:53 +0100 Lucas Nussbaum 
> wrote:
> > > /usr/include/thrust/detail/type_traits.h:736:1: error: expected
> > > type-specifier before ‘template’
>
> This bug is caused by a #ifdef cascade for different
> THRUST_DEVICE_SYSTEM values, which sadly no longer works with
> THRUST_DEVICE_SYSTEM_OMP. This makes it effectively impossible to
> build the HIP backend and the OpenMP backend from the same source.

Am I understanding correctly that this was broken in a rocthrust update? 
Should this be treated as a rocthrust bug? [1]


Sincerely,
Cory Bloor

[1]: https://bugs.debian.org/1064730

Bug#1068417: marked as done (trafficserver: CVE-2024-31309: HTTP/2 CONTINUATION frames can be utilized for DoS attacks)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 21:50:27 +
with message-id 
and subject line Bug#1068417: fixed in trafficserver 9.2.4+ds-0+deb12u1
has caused the Debian Bug report #1068417,
regarding trafficserver: CVE-2024-31309: HTTP/2 CONTINUATION frames can be 
utilized for DoS attacks
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.)


-- 
1068417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trafficserver
Version: 9.2.3+ds-1+deb12u1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 8.1.9+ds-1~deb11u1

Hi,

The following vulnerability was published for trafficserver.

CVE-2024-31309[0].

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-31309
https://www.cve.org/CVERecord?id=CVE-2024-31309
[1] https://www.kb.cert.org/vuls/id/421644
[2] https://github.com/apache/trafficserver/pull/11207
[3] https://github.com/apache/trafficserver/pull/11206

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: trafficserver
Source-Version: 9.2.4+ds-0+deb12u1
Done: Jean Baptiste Favre 

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

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

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

Debian distribution maintenance software
pp.
Jean Baptiste Favre  (supplier of updated trafficserver 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 11:21:19 +0200
Source: trafficserver
Architecture: source
Version: 9.2.4+ds-0+deb12u1
Distribution: bookworm-security
Urgency: medium
Maintainer: Jean Baptiste Favre 
Changed-By: Jean Baptiste Favre 
Closes: 1068417
Changes:
 trafficserver (9.2.4+ds-0+deb12u1) bookworm-security; urgency=medium
 .
   * New upstream version 9.2.4+ds
   * Refresh d/patches for 9.2.4 release
   * CVEs fix (Closes: #1068417)
 - CVE-2024-31309: HTTP/2 CONTINUATION DoS attack
Checksums-Sha1:
 6e5ee8e9dcb447167fc51f205fc7aa4079d8bf9c 3024 
trafficserver_9.2.4+ds-0+deb12u1.dsc
 cd8b0489c081639feab09a8b6b2ee35187bc9237 8946216 
trafficserver_9.2.4+ds.orig.tar.xz
 07bb1879ce7bd25836ffa6e9f9bd69c1da79434b 35920 
trafficserver_9.2.4+ds-0+deb12u1.debian.tar.xz
 30a5558923240e4cbf8b0e5e5963df0d018f3605 12785 
trafficserver_9.2.4+ds-0+deb12u1_source.buildinfo
Checksums-Sha256:
 da6bc838544fb3a59f812a46dcfd3c88c9124c07591d287c9bd033e808c05bd5 3024 
trafficserver_9.2.4+ds-0+deb12u1.dsc
 9eb6089cfb91d07eb2b44d26c6f37ed1071fd1eb19113e6870afeefdc801cda7 8946216 
trafficserver_9.2.4+ds.orig.tar.xz
 ea1321713b68ae05f04256ecdd35e48e653f9415b4f073202b8e55fff42154f8 35920 
trafficserver_9.2.4+ds-0+deb12u1.debian.tar.xz
 f1e816ed062ca2d7c8907175270af614034dca1e40b4ac6db9d943804e131911 12785 
trafficserver_9.2.4+ds-0+deb12u1_source.buildinfo
Files:
 15e0de4e8662bc8879a922e803e8d77b 3024 web optional 
trafficserver_9.2.4+ds-0+deb12u1.dsc
 0e061f5cdca0150fb748ae34e6fb 8946216 web optional 
trafficserver_9.2.4+ds.orig.tar.xz
 83f96627c72a08dbc595e9bb1dc44db5 35920 web optional 
trafficserver_9.2.4+ds-0+deb12u1.debian.tar.xz
 a0a8f048d8e97ec67ab2ef40c384adbc 12785 web optional 
trafficserver_9.2.4+ds-0+deb12u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEToRbojDLTUSJBphHtN1Tas99hzcFAmYaVIZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRF
ODQ1QkEyMzBDQjRENDQ4OTA2OTg0N0I0REQ1MzZBQ0Y3RDg3MzcACgkQtN1Tas99
hze/vA//aaLprYJOSyqBGa7LIM2IUd+2hIbdiRWTN/6kHIzSngLbUF+I37bEgZcz
aFT4GrqXioBSwYyMrj2WipZR/tKDJbJpo+glzOqwLmCqFyNWe+TtEZ0pUfnd1gEW
m9r6XlftZXZ8yU9LeCtQQ5N9Z/KR1iYTrSKrq2ryq7yey2HdNfq4sYsgZoQ/yplv
D4iRfc2HvrAq3X3w5Ai9LlpXtavXuy9+17c8MgOXU9ZzQpmYZHDyXwS5yOcVqtUe
oO5lkjK6kZ8gD8DlXmz4wJpKgJ2mHyWdgvSMX6mn5VzGS40qIOxng025E5rvGDfw
y7fkJPhq1Yq6p3WEtV8ZWZ4xgdSJpx3ZzEuBKJakucBCTmRIHrpGPK5rVfsbZDId
x+x+vQvsoBl00wvh5j+aecDXfnBkfR+P0xytD4+tgJ+qI3J4UHsMB948bV1aOXmc

Bug#1068770: marked as done (linux-image-6.1.0-18-amd64: Local privilege escalation vulnerability in kernel n_gsm driver)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 21:47:22 +
with message-id 
and subject line Bug#1068770: fixed in linux 6.1.85-1
has caused the Debian Bug report #1068770,
regarding linux-image-6.1.0-18-amd64: Local privilege escalation vulnerability 
in kernel n_gsm driver
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.)


-- 
1068770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.1.76-1
Severity: critical
Tags: upstream security
Justification: root security hole
X-Debbugs-Cc: lw-deb-...@greyskydesigns.com, Debian Security Team 


Dear Maintainer,

A Reddit thread[1] linked to a Github page[2] with a local root escalation 
exploit.  This exploit works on the current "bookworm" stable kernel, 
6.1.0-18-amd64.

It can be worked around by blocking the n_gsm driver:

echo 'blacklist n_gsm' | sudo tee -a /etc/modprobe.d/blacklist-gsm.conf
sudo rmmod n_gsm


[1] https://old.reddit.com/r/linux/comments/1c0i7tx/someone_found_a_kernel_0day/
[2] https://github.com/YuriiCrimson/ExploitGSM/


-- Package-specific info:
** Version:
Linux version 6.1.0-18-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01)

** Command line:
BOOT_IMAGE=/@rootfs/boot/vmlinuz-6.1.0-18-amd64 root=UUID=403bad0f-[snip] ro 
rootflags=subvol=@rootfs panic=5

** Not tainted

** Kernel log:
[2.783100] at24 0-0051: supply vcc not found, using dummy regulator
[2.784137] at24 0-0051: 256 byte spd EEPROM, read-only
[2.789726] usb 2-1.3: FTDI USB Serial Device converter now attached to 
ttyUSB1
[2.806774] ipmi_si: IPMI System Interface driver
[2.810971] usbcore: registered new interface driver usbhid
[2.811095] usbhid: USB HID core driver
[2.811363] ipmi_si dmi-ipmi-si.0: ipmi_platform: probing via SMBIOS
[2.811489] ipmi_platform: ipmi_si: SMBIOS: io 0xca8 regsize 1 spacing 1 irq 0
[2.811630] ipmi_si: Adding SMBIOS-specified kcs state machine
[2.811813] ipmi_si IPI0001:00: ipmi_platform: probing via ACPI
[2.812069] ipmi_si IPI0001:00: ipmi_platform: [io  0x0ca8] regsize 1 
spacing 4 irq 0
[2.818248] ipmi_si dmi-ipmi-si.0: Removing SMBIOS-specified kcs state 
machine in favor of ACPI
[2.818400] ipmi_si: Adding ACPI-specified kcs state machine
[2.818581] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 
0xca8, slave address 0x20, irq 0
[2.825415] input: American Megatrends Inc. Virtual Keyboard and Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.0/0003:046B:FF10.0001/input/input3
[2.832623] hid-generic 0003:046B:FF10.0001: input,hidraw0: USB HID v1.10 
Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on 
usb-:00:1a.0-1.5.1/input0
[2.832950] input: American Megatrends Inc. Virtual Keyboard and Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5.1/1-1.5.1:1.1/0003:046B:FF10.0002/input/input4
[2.834908] hid-generic 0003:046B:FF10.0002: input,hidraw1: USB HID v1.10 
Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on 
usb-:00:1a.0-1.5.1/input1
[2.842988] ast :0a:00.0: vgaarb: deactivate vga console
[2.844608] Console: switching to colour dummy device 80x25
[2.846274] ast :0a:00.0: [drm] Using P2A bridge for configuration
[2.846281] ast :0a:00.0: [drm] AST 1100 detected
[2.846293] ast :0a:00.0: [drm] Using analog VGA
[2.846303] ast :0a:00.0: [drm] dram MCLK=204 Mhz type=0 bus_width=16
[2.850155] [drm] Initialized ast 0.1.0 20120228 for :0a:00.0 on minor 0
[2.855445] fbcon: astdrmfb (fb0) is primary device
[2.896398] ipmi_si IPI0001:00: IPMI message handler: Found new BMC (man_id: 
0x0019fd, prod_id: 0x1588, dev_id: 0x20)
[2.956975] RAPL PMU: API unit is 2^-32 Joules, 2 fixed counters, 163840 ms 
ovfl timer
[2.956979] RAPL PMU: hw unit of domain pp0-core 2^-16 Joules
[2.956980] RAPL PMU: hw unit of domain package 2^-16 Joules
[2.962273] cfg80211: Loading compiled-in X.509 certificates for regulatory 
database
[2.962515] cfg80211: Loaded X.509 cert 'b...@debian.org: 
577e021cb980e0e820821ba7b54b4961b8b4fadf'
[2.962782] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com: 
3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
[2.963083] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[2.963382] cfg80211: Loaded X.509 cert 'wens: 
61c038651aabdcf94bd0ac7ff06c7248db18c600'
[2.964803] platform

Bug#1065320: marked as done (linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters ACPI Error loop during boot & requires power cycle)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 21:47:22 +
with message-id 
and subject line Bug#1065320: fixed in linux 6.1.85-1
has caused the Debian Bug report #1065320,
regarding linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters ACPI Error loop 
during boot & requires power cycle
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.)


-- 
1065320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.1.76-1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: leeejobsacco...@mail.co.uk

Dear Maintainer,

   * What led up to the situation?

   Trying to boot the system with the 6.1.0-18 kernel

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

   I tried adding 'boot_delay=1000' boot option to slow the console
   scroll rate, to enable better recording of the error messages.

   I tried rebooting the previous 6.1.0-17 kernel.

   * What was the outcome of this action?

   After adding the 'boot_delay=1000' option the boot process
   progressed no further than "Loading initial ramdisk ..."
   (left for several minutes - required power cycle).

   The system boots sucessfully on the previous 6.1.0-17 kernel

   * What outcome did you expect instead?

   I expected the system to successfully boot.

   * Additional observations

   This system also normally includes 'hpet=disable' and
   'acpi_enforce_resources=lax' boot options but removing these
   made no difference.

   Although I was not able to boot the system with the
   'boot_delay=1000' option and obtain clear photographs of the
   console output - the ones I've attached suffer from
   'overprinting' - it does seem clear that ACPI errors are
   being reported.

   There appear to be two distinct phases to this problem.
   Initially, ACPI seems to be reporting errors for "GPE", as
   shown in the first attached photograph, but after ~10 seconds
   or so, ACPI then switches to continuously reporting an error
   for PM_TIMER, as shown in the second attached photograph. At
   this point a power cycle is required.

   Purging and reinstalling the package made no difference. Atm,
   only three kernels are installed on this system but I have
   had more in the past as I normally compile my own kernels
   from the corresponding Debian source package. My own 6.1.76-1
   kernel also suffers from the same problem, whereas my own
   6.1.69-1 kernel boots and runs Ok.

   Comparing the kernel configs for 6.1.0-17 and 6.1.0-18
   showed just one functional change - an additional
   Compile-time checks and compiler option, which did not seem
   relevant to this problem.


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

** Model information
sys_vendor: ASUSTeK COMPUTER INC.
product_name: E203NA
product_version: 1.0   
chassis_vendor: ASUSTeK COMPUTER INC.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: E203NA.312
board_vendor: ASUSTeK COMPUTER INC.
board_name: E203NA
board_version: 1.0   

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback


** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Celeron N3350/Pentium N4200/Atom 
E3900 Series Host Bridge [8086:5af0] (rev 0b)
Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 
Series Host Bridge [1043:1980]
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- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device_pci_legacy

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 500 
[8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. HD Graphics 500 [1043:1980]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+ FLReset+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta:

Bug#1068663: marked as done (zzuf: FTBFS on arm{el,hf}: /tmp/ccnMZahz.s:1620: Error: symbol `open64' is already defined)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 21:38:21 +
with message-id 
and subject line Bug#1068663: fixed in zzuf 0.15-4
has caused the Debian Bug report #1068663,
regarding zzuf: FTBFS on arm{el,hf}: /tmp/ccnMZahz.s:1620: Error: symbol 
`open64' is already defined
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.)


-- 
1068663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zzuf
Version: 0.15-3
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=zzuf=armhf=0.15-3=1712473020=0

In file included from /usr/include/arm-linux-gnueabihf/sys/cdefs.h:24,
 from libzzuf/lib-mem.c:24:
/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"
  |   ^~~
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
-DLIBZZUF -I./libzzuf -I./common -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -std=c99 -g -O2 -Wall 
-W -Wpointer-arith -Wcast-align -Wcast-qual -Wstrict-prototypes -Wshadow 
-Waggregate-return -Wmissing-prototypes -Wnested-externs -Wsign-compare -c 
libzzuf/lib-signal.c -o libzzuf/la-lib-signal.o >/dev/null 2>&1
/tmp/ccnMZahz.s: Assembler messages:
/tmp/ccnMZahz.s:1620: Error: symbol `open64' is already defined
/tmp/ccnMZahz.s:4926: Error: symbol `lseek64' is already defined
make[3]: *** [Makefile:708: libzzuf/la-lib-fd.lo] Error 1
make[3]: *** Waiting for unfinished jobs
/tmp/ccKhQeYR.s: Assembler messages:
/tmp/ccKhQeYR.s:1867: Error: symbol `mmap64' is already defined

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: zzuf
Source-Version: 0.15-4
Done: Andreas Beckmann 

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated zzuf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Apr 2024 23:12:17 +0200
Source: zzuf
Architecture: source
Version: 0.15-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1068663
Changes:
 zzuf (0.15-4) unstable; urgency=medium
 .
   * QA upload.
   * Undefine _FILE_OFFSET_BITS and _TIME_BITS for some files that want to
 provide replacements for both e.g. open() and open64(). (Closes: #1068663)
Checksums-Sha1:
 6df0c7d0f6e2777870dd4a53e9a36ec7d56fdd0a 1822 zzuf_0.15-4.dsc
 a377c8d4090ad985780061ceacd20b10abe8b10b 5540 zzuf_0.15-4.debian.tar.xz
 988ea0f5f38a4d05e6736938fd68098431fc43e8 5604 zzuf_0.15-4_source.buildinfo
Checksums-Sha256:
 8dec6637bafb148e3be768cef4a866365488e444725d9d119255a92ada84a927 1822 
zzuf_0.15-4.dsc
 c5f669388cb4b7ba5f9843d3bb721c6c4732d5b61cba6544318c8d428d5b2b21 5540 
zzuf_0.15-4.debian.tar.xz
 2ce4c9453bd77db2536fa364f9abe79e8825c020fede9d730597f2cdaba78413 5604 
zzuf_0.15-4_source.buildinfo
Files:
 c0b8e2ef1db0e0fd6011b11f66f7db3e 1822 devel optional zzuf_0.15-4.dsc
 57205e69c1a512cb282f401294e415f5 5540 devel optional zzuf_0.15-4.debian.tar.xz
 e3bd916968eb9359efaa1a270f874b6f 5604 devel optional 
zzuf_0.15-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYdmJUQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCMc/D/44LrvN+nxIUVOHDtwyKkTu2TRThNFJDwI8
ZkpE7GEhUz4uJKyLWno2z0SXUtkRVjiMsT+m7uc+9rc7AHvV4p1s6grho+qpdbrn
XwNLo4851Zhj/IX/vNjuIjA+HtpRkYDH2tO78lx4c1pKHzOx9x//wHt/h7Sh0vo7
wjki+MVq9r6iyy/m7d8LU87Zb0i+5k4MLFE/y0hV79Q/BJ3KtDjoaqZUMnAZyD8J
jQwwkNOsJyUED+1QNaMpEXZKL4eeCe7O2MOR6sIEml5NfoIZuvNKToXrtytZLVRz
sS4LakQRICeDSoUq3oJ91J7lVINVQ0IJsBizZ1Q/TgYg7sGACUGvzpB0VVIcjvbR

Bug#1066610: marked as done (gnomad2: FTBFS: jukebox.c:1979:13: error: implicit declaration of function ‘set_tag_for_file’; did you mean ‘set_tag_for_mp3file’? [-Werror=implicit-function-declaration])

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 21:36:53 +
with message-id 
and subject line Bug#1066610: fixed in gnomad2 2.9.6-9
has caused the Debian Bug report #1066610,
regarding gnomad2: FTBFS: jukebox.c:1979:13: error: implicit declaration of 
function ‘set_tag_for_file’; did you mean ‘set_tag_for_mp3file’? 
[-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.)


-- 
1066610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnomad2
Version: 2.9.6-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 -DPACKAGE_NAME=\"gnomad2\" -DPACKAGE_TARNAME=\"gnomad2\" 
> -DPACKAGE_VERSION=\"2.9.6\" -DPACKAGE_STRING=\"gnomad2\ 2.9.6\" 
> -DPACKAGE_BUGREPORT=\"tr...@df.lth.se\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"gnomad2\" -DVERSION=\"2.9.6\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 
> -DHAVE_TAGLIB=1 -DHAVE_LIBMTP=1 -DHAVE_LIBMTP_030=1 -DHAVE_GUDEV=1 
> -DGETTEXT_PACKAGE=\"gnomad2\" -DHAVE_LOCALE_H=1 -DHAVE_LC_MESSAGES=1 
> -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 
> -DENABLE_NLS=1 -DGNOMADLOCALEDIR=\"/usr/share/locale\" -DHAVE_DIRENT_H=1 
> -DHAVE_MALLOC_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_FCNTL_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_CHDIR=1 -I. -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/webp 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cloudproviders 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread 
> -I/usr/include/libusb-1.0 -I/usr/include/taglib -I/usr/include/gudev-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -DPREFIX=\"/usr\" -DSYSCONFDIR=\"/etc\" -DDATADIR=\"/usr/share\" 
> -DLIBDIR=\"/usr/lib/x86_64-linux-gnu\" -DPIXMAPSDIR=\""/usr/share/pixmaps"\"  
> -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -DGTK_DISABLE_SINGLE_INCLUDES -DG_DISABLE_SINGLE_INCLUDES -c -o editmeta.o 
> editmeta.c
> gnomad2.c: In function ‘scan_jukebox’:
> gnomad2.c:282:3: warning: ‘g_thread_create’ is deprecated: Use 'g_thread_new' 
> instead [-Wdeprecated-declarations]
>   282 |   g_thread_create(scan_thread,(gpointer) _thread_args, FALSE, 
> NULL);
>   |   ^~~
> In file included from /usr/include/glib-2.0/glib.h:115,
>  from /usr/include/gtk-3.0/gdk/gdkconfig.h:8,
>  from /usr/include/gtk-3.0/gdk/gdk.h:30,
>  from /usr/include/gtk-3.0/gtk/gtk.h:30,
>  from common.h:51,
>  from gnomad2.c:20:
> /usr/include/glib-2.0/glib/deprecated/gthread.h:102:10: note: declared here
>   102 | GThread *g_thread_create   (GThreadFunc   func,
>   |  ^~~
> gnomad2.c: In function ‘main’:
> gnomad2.c:456:3: warning: ‘g_thread_init’ is deprecated 
> [-Wdeprecated-declarations]
>   456 |   g_thread_init(NULL);
>   |   ^
> /usr/include/glib-2.0/glib/deprecated/gthread.h:267:10: note: declared here
>   267 | void g_thread_init   (gpointer vtable);
>   |  ^
> gnomad2.c:477:3: warning: ‘gtk_window_set_wmclass’ is deprecated 
> [-Wdeprecated-declarations]
>   477 |   gtk_window_set_wmclass(GTK_WINDOW(main_window), PACKAGE, "main");
>   |   ^~
> In file included from

Bug#1037914: cloud-initramfs-growroot: missing dependencies in initramfs

2024-04-15 Thread Timo Lindfors





On Tue, 16 Apr 2024, Timo Lindfors wrote:

I would very much like to have some sort of workaround to start moving some


I noticed that if I use



cmd = [
"virt-install",
"--connect", "qemu+ssh://ansi...@hypervisor.example.com/system",
"--name", "linditest",
"--cloud-init", 
"user-data=cloudinit-user-data.yml,network-config=cloudinit-network-config.yml",
"--os-variant", "debiantesting",
"--network", "bridge=br0,model=virtio",
"--disk", "size=20,backing_store=/srv/images/debian-12-generic-amd64.qcow2",
"--graphics", "none",
"--autostart"
]
subprocess.check_call(cmd)



I get the error messages about grep and sed being missing but still 
somehow the filesystem gets resized:




Warning: fsck not present, so skipping root file system
[2.993780] EXT4-fs (vda1): mounted filesystem with ordered data mode. 
Quota mode: none.

done.
Begin: Running /scripts/local-bottom ... GROWROOT: /sbin/growpart: 824: 
/sbin/growpart: grep: not found

GPT PMBR size mismatch (4194303 != 41943039) will be corrected by write.
The backup GPT table is not on the end of the device.
/sbin/growpart: 853: /sbin/growpart: sed: not found
WARN: unknown label
/sbin/growpart: 354: /sbin/growpart: sed: not found
FAILED: sed failed on dump output
/sbin/growpart: 83: /sbin/growpart: rm: not found
done.
Begin: Running /scripts/init-bottom ... done.

...

[  OK  ] Started session-1.scope - Session 1 of User ansible.

Debian GNU/Linux 12 linditest ttyS0

linditest login: ansible
Password:
Linux linditest 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 
(2024-04-11) x86_64


The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Apr 15 21:28:07 UTC 2024 from 80.242.28.204 on pts/0
ansible@linditest:~$ df -h
Filesystem  Size  Used Avail Use% Mounted on
udev462M 0  462M   0% /dev
tmpfs97M  624K   96M   1% /run
/dev/vda120G 1006M   18G   6% /
tmpfs   481M 0  481M   0% /dev/shm
tmpfs   5.0M 0  5.0M   0% /run/lock
/dev/vda15  124M   12M  113M  10% /boot/efi
tmpfs97M 0   97M   0% /run/user/1000

#

-Timo

Bug#1066479: opendnssec: FTBFS: ../../common/scheduler/task.c:137:25: error: implicit declaration of function ‘clamp’ [-Werror=implicit-function-declaration]

2024-04-15 Thread Mathieu Mirmont

On Tue, Mar 26, 2024 at 02:36:06PM +0100, Cyril Brulebois wrote:
> Control: tag -1 patch pending
> 
> Lucas Nussbaum  (2024-03-13):
> > 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):
> > > ../../common/scheduler/task.c: In function ‘task_perform’:
> > > ../../common/scheduler/task.c:137:25: error: implicit declaration of 
> > > function ‘clamp’ [-Werror=implicit-function-declaration]
> > >   137 | task->backoff = clamp(task->backoff * 2, 60, 
> > > ODS_SE_MAX_BACKOFF);
> > >   | ^
> > > cc1: some warnings being treated as errors
> > > make[4]: *** [Makefile:601: scheduler/task.o] Error 1
> 
> I thought there would be several things but apparently that's just the
> one. A quick look upstream shows there are more PRs and more fixups
> needed for even newer compilers, but I'm limiting my patch to the bare
> minimum.
> 
> Since that's been open for 10+ days, and since reverse dependencies
> could get kicked out of testing, I'm uploading an NMU right now so that
> I don't forget, but to DELAYED/2 so there's some room to do things
> differently if desired. I'm happy to reschedule/cancel if needed.

Thanks for the NMU.

I had a look at the new warnings and they all seem to be false
positives. I'd rather not introduce unnecessary changes in the
packaged version compared to upstream just to silence them. This
missing header will do.

-- 
Mathieu Mirmont 


signature.asc
Description: Digital signature

Bug#1037914: cloud-initramfs-growroot: missing dependencies in initramfs

2024-04-15 Thread Timo Lindfors


Hi,

I would very much like to have some sort of workaround to start moving 
some systems from proprietary clouds to libvirt. I don't quite understand 
how cloud-init works, does the workaround suggested in the first message 
basically require me to rebuild the image? If that is the case then maybe 
simply running virt-resize could be a workaround for now?


-Timo

Bug#1069073: lua-mode: FTBFS: failing tests

2024-04-15 Thread Santiago Vila


Package: src:lua-mode
Version: 20210802-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build
dh build --with elpa
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   dh_auto_build
make -j2
make[1]: Entering directory '/<>'
Loading /etc/emacs/site-start.d/00debian.el (source)...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Loading /etc/emacs/site-start.d/00debian.el (source)...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Loading /etc/emacs/site-start.d/00debian.el (source)...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Loading /etc/emacs/site-start.d/00debian.el (source)...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
version is 20210802
make[1]: Leaving directory '/<>'
   dh_elpa_test
buttercup -L .
Loading /etc/emacs/site-start.d/00debian.el (source)...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Warning (buttercup): Found duplicate spec names in suite: ("lua-skip-ws-and-comments-forward respects 
limit when escaping multi-line comment 1: limit=8 \"--[[<1>   <2> ]] \\n\"")
Running 392 out of 410 specs.

Test electric mode
  works with curly braces
[32m  works with curly braces[0m (3.66ms)
  works with parentheses
[32m  works with parentheses[0m (0.97ms)
  works with end
[32m  works with end[0m (1.13ms)
  works with else
[32m  works with else[0m (1.13ms)
  works with elseif
[32m  works with elseif[0m (1.16ms)

Electric pair mode
  skips parens when electric-pair-skip-self is t
[32m  skips parens when electric-pair-skip-self is t[0m (1.60ms)

Test fill-paragraph
  fills single-line comment
[32m  fills single-line comment[0m (0.45ms)
  fills comment after code
[32m  fills comment after code[0m (0.39ms)
  fills multiline comment
[33m  fills multiline comment[0m[33m  PENDING[0m (0.07ms)
  does not spill comments into code (issue #25)
[32m  does not spill comments into code (issue #25)[0m (0.38ms)

Test fill-paragraph preserves point position
  doesn't move point if nothing has changed
[32m  doesn't move point if nothing has changed[0m (0.96ms)
  doesn't move point in refilled region
[32m  doesn't move point in refilled region[0m (2.26ms)
  doesn't move point if nothing has changed (multi-line)
[32m  doesn't move point if nothing has changed (multi-line)[0m (0.71ms)

Fontification of built-ins
  fontifies built-ins
[32m  fontifies built-ins[0m (0.27ms)
  fontifies built-ins with spaces between members
[32m  fontifies built-ins with spaces between members[0m (0.26ms)
  doesn't fontify things that look like built-ins
[32m  doesn't fontify things that look like built-ins[0m (0.50ms)
  fontifies built-in class if method is not built-in
[32m  fontifies built-in class if method is not built-in[0m (0.24ms)
  fontifies built-ins after concatenation operator
[32m  fontifies built-ins after concatenation operator[0m (0.19ms)

Fontification of constants
  fontifies constants
[32m  fontifies constants[0m (0.20ms)
  fontifies constants used as attributes
[32m  fontifies constants used as attributes[0m (0.19ms)

Fontification of keywords
  fontifies keywords
[32m  fontifies keywords[0m (0.27ms)
  fontifies keywords used as attributes
[32m  fontifies keywords used as attributes[0m (0.24ms)

Fontification of variables
  fontifies "local foo, bar, baz = 1, 2, 3"
[32m  fontifies "local foo, bar, baz = 1, 2, 3"[0m (0.21ms)
  fontifies "local foo, bar, baz"
[32m  fontifies "local foo, bar, baz"[0m (0.20ms)
  fontifies "local x =" at end of buffer
[32m  fontifies "local x =" at end of buffer[0m (0.16ms)
  fontifies local "x =" at end of line
[32m  fontifies local "x =" at end of line[0m (0.18ms)
  does not fontify "for" inside strings
[32m  does not fontify "for" inside strings[0m (0.22ms)
  fontifies "for x123 ="
[32m  fontifies "for x123 ="[0m (0.16ms)
  fontifies "for x, y, z"
[32m  fontifies "for x, y, z"[0m (0.18ms)

Fontification of function headers
  fontifies function (...) headers
[32m  fontifies function (...) headers[0m (0.20ms)
  fontifies local function (...) headers
[32m  fontifies local function (...) headers[0m (0.21ms)
  fontifies  = function (...) headers
[32m  fontifies  = function (...) headers[0m (0.19ms)
  fontifies local  = function (...) headers
[32m  fontifies local  = function (...) headers[0m (0.20ms)
  fontifies parameters in function literals
[32m  fontifies parameters in function literals[0m (0.18ms)
  fontifies different variations of headers altogether
[32m  fontifies different variations of headers altogether[0m (0.41ms)
  fontifies headers inside tables
[32m  fontifies headers inside tables[0m (0.31ms)
  does not fail on issue #59 again
[32m  does not fail on issue #59 again[0m (0.30ms)
  does not choke on function names with underscores

Bug#1069074: totalopenstation: FTBFS: failing tests

2024-04-15 Thread Santiago Vila


Package: src:totalopenstation
Version: 0.5.2-4
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary
dh binary --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.11 setup.py config
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3 setup.py build
running build
running build_py
creating /<>/.pybuild/cpython3_3.11/build/totalopenstation
copying totalopenstation/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation
creating /<>/.pybuild/cpython3_3.11/build/totalopenstation/models
copying totalopenstation/models/trimble.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/models
copying totalopenstation/models/leica_tcr_705.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/models
copying totalopenstation/models/zeiss_elta_r55.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/models
copying totalopenstation/models/nikon_npl_350.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/models
copying totalopenstation/models/custom.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/models
copying totalopenstation/models/leica_tcr_1205.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/models
copying totalopenstation/models/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/models
creating /<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_polar.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_topcon_gts.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_trimble_are.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_leica_gsi.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_zeiss_r5.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_geojson.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_leica_tcr_705.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_csv.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_zeiss.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_nikon.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_rw5.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_leica_tcr_1205.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_sokkia_sdr33.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
copying totalopenstation/tests/test_dxf.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/tests
creating /<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/nikon_raw_v200.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/trimble_are.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/topcon_gts.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/sokkia_sdr33.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/conversion.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/zeiss_r5.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/leica_tcr_705.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/polar.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/leica_gsi.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/zeiss_rec_500.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/carlson_rw5.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/leica_tcr_1205.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
copying totalopenstation/formats/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/formats
creating /<>/.pybuild/cpython3_3.11/build/totalopenstation/output
copying totalopenstation/output/tops_sql.py -> 
/<>/.pybuild/cpython3_3.11/build/totalopenstation/output
copying

Bug#1065797: st: FTBFS on arm{el,hf}: res.c:115:12: error: implicit declaration of function ‘_getshort’; did you mean ‘__putshort’? [-Werror=implicit-function-declaration]

2024-04-15 Thread Zixing Liu

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

Dear Maintainer,

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

  * debian/patches/02-implicit-declarations.patch: Fix an improper macro
feature check.  (Closes #1065797, LP: #2060973).
  * debian/patches/1032955_riscv_support.patch: Add support for RISC-V
CPU.  Thanks to Steven Liu . (LP: #2061639).


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-27-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru st-1.9/debian/patches/02-implicit-declarations.patch 
st-1.9/debian/patches/02-implicit-declarations.patch
--- st-1.9/debian/patches/02-implicit-declarations.patch1969-12-31 
17:00:00.0 -0700
+++ st-1.9/debian/patches/02-implicit-declarations.patch2024-04-15 
10:06:57.0 -0600
@@ -0,0 +1,21 @@
+Description: Fix an improper macro feature check
+ This resolves the implicit declaration error on armhf
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065797
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/st/+bug/2060973
+Forwarded: no
+Last-Update: 2024-04-15
+---
+Index: st/examples/res.c
+===
+--- st.orig/examples/res.c
 st/examples/res.c
+@@ -82,7 +82,7 @@
+ #endif
+ 
+ /* New in Solaris 7 */
+-#if !defined(_getshort) && defined(ns_get16)
++#if !defined(_getshort) && defined(NS_GET16)
+ #define _getshort(cp) ns_get16(cp)
+ #endif
+ 
diff -Nru st-1.9/debian/patches/1032955_riscv_support.patch 
st-1.9/debian/patches/1032955_riscv_support.patch
--- st-1.9/debian/patches/1032955_riscv_support.patch   1969-12-31 
17:00:00.0 -0700
+++ st-1.9/debian/patches/1032955_riscv_support.patch   2024-04-15 
10:06:57.0 -0600
@@ -0,0 +1,111 @@
+Description: Add support for RISC-V CPU
+Author: Steven Liu 
+Origin: 
https://github.com/ossrs/state-threads/commit/c865500b8c1f4821cc77627094c1a30fef403dbb
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032955
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/st/+bug/2061639
+Applied-Upstream: 
https://github.com/ossrs/state-threads/commit/c865500b8c1f4821cc77627094c1a30fef403dbb
+Reviewed-by: Zixing Liu 
+Last-Update: 2022-07-20
+---
+Index: st-1.9/md.S
+===
+--- st-1.9.orig/md.S
 st-1.9/md.S
+@@ -431,5 +431,81 @@ _st_md_cxt_restore:
+ 
+ //
+ 
++#elif defined(__riscv)
++
++//
++/*
++ * Internal __jmp_buf layout
++ * riscv-asm: 
https://github.com/riscv/riscv-asm-manual/blob/master/riscv-asm.md
++ */
++#define JB_SP  0/* A0, SP, Stack pointer */
++#define JB_RA  1/* RA, Return address */
++#define JB_FP  2/* FP/S0 Frame pointer */
++#define JB_S1  3/* S1 Saved register*/
++#define JB_S2  4/* S2-S11,  Saved register */
++#define JB_S3  5/* S2-S11,  Saved register */
++#define JB_S4  6/* S2-S11,  Saved register */
++#define JB_S5  7/* S2-S11,  Saved register */
++#define JB_S6  8/* S2-S11,  Saved register */
++#define JB_S7  9/* S2-S11,  Saved register */
++#define JB_S8  10/* S2-S11,  Saved register */
++#define JB_S9  11   /* S2-S11,  Saved register */
++#define JB_S10 12   /* S2-S11,  Saved register */
++#define JB_S11 13   /* S2-S11,  Saved register */
++
++
++  .file "md.S"
++  .text
++
++  /* _st_md_cxt_save(__jmp_buf env) */ /* The env is $a0, 
https://en.wikipedia.org/wiki/RISC-V#Register_sets */
++  .globl _st_md_cxt_save
++  .type _st_md_cxt_save, %function
++  .align 2
++_st_md_cxt_save:
++  sdsp,  JB_SP  * 8(a0)
++  sdra,  JB_RA  * 8(a0)
++  sds0,  JB_FP  * 8(a0)
++  sds1,  JB_S1  * 8(a0)
++  sds2,  JB_S2  * 8(a0)
++  sds3,  JB_S3  * 8(a0)
++  sds4,  JB_S4  * 8(a0)
++  sds5,  JB_S5  * 8(a0)
++  sds6,  JB_S6  * 8(a0)
++  sds7,  JB_S7  * 8(a0)
++  sds8,  JB_S8  * 8(a0)
++  sds9,  JB_S9  * 8(a0)
++  sds10, JB_S10 * 8(a0)
++  sds11, JB_S11 * 8(a0)
++  lia0,  0
++  jrra
++  .size _st_md_cxt_save, .-_st_md_cxt_save
++
++

Bug#1067618: FTBFS: error: implicit declaration of function 'yyerror'; did you mean 'yyerrok'? [-Werror=implicit-function-declaration]

2024-04-15 Thread Zixing Liu

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

Dear Maintainer,

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

  * debian/patches/implicit-declarations.patch: Add missing includes and
function prototypes.  (LP: #2061038).


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-27-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru whitedune-0.30.10/debian/patches/implicit-declarations.patch 
whitedune-0.30.10/debian/patches/implicit-declarations.patch
--- whitedune-0.30.10/debian/patches/implicit-declarations.patch
1969-12-31 17:00:00.0 -0700
+++ whitedune-0.30.10/debian/patches/implicit-declarations.patch
2024-04-15 11:23:06.0 -0600
@@ -0,0 +1,60 @@
+Description: Add missing includes and function prototypes
+ This fixes FTBFS on armhf
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067618
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/whitedune/+bug/2061038
+Forwarded: no
+Last-Update: 2024-04-15
+---
+Index: whitedune/src/SDLjoystick/SDL_joystick_c.h
+===
+--- whitedune.orig/src/SDLjoystick/SDL_joystick_c.h
 whitedune/src/SDLjoystick/SDL_joystick_c.h
+@@ -2,3 +2,11 @@
+  * This Makefile is free software; the Free Software Foundation
+  * gives unlimited permission to copy, distribute and modify it.
+  */
++extern int SDL_PrivateJoystickButton(SDL_Joystick *joystick,
++ Uint8 button, Uint8 state);
++extern int SDL_PrivateJoystickAxis(SDL_Joystick *joystick,
++   Uint8 axis, Sint16 value);
++extern int SDL_PrivateJoystickBall(SDL_Joystick *joystick,
++   Uint8 ball, Sint16 xrel, Sint16 yrel);
++extern int SDL_PrivateJoystickHat(SDL_Joystick *joystick,
++  Uint8 hat, Uint8 value);
+Index: whitedune/src/swt/rc/rclex.l
+===
+--- whitedune.orig/src/swt/rc/rclex.l
 whitedune/src/swt/rc/rclex.l
+@@ -28,6 +28,7 @@
+ #include 
+ 
+ #include 
++#include 
+ #include "y.tab.h"
+ #include "rc.h"
+ 
+Index: whitedune/src/swt/rc/rcparse.y
+===
+--- whitedune.orig/src/swt/rc/rcparse.y
 whitedune/src/swt/rc/rcparse.y
+@@ -38,6 +38,7 @@ static RCNode *append(RCNode *node1, RCN
+ static RCBitmap *newBitmap(int id, const char *filename);
+ static void addAccelerator(int key, int modifiers, int command);
+ static int getVirtkey(const char *str);
++int yyerror(const char *s);
+ 
+ RCBitmap **bitmaps = NULL;
+ RCNode **nodes = NULL;
+Index: whitedune/src/pngLoad.c
+===
+--- whitedune.orig/src/pngLoad.c
 whitedune/src/pngLoad.c
+@@ -20,6 +20,7 @@
+ 
+ #include 
+ #include 
++#include 
+ 
+ #include "config.h"
+ 
diff -Nru whitedune-0.30.10/debian/patches/series 
whitedune-0.30.10/debian/patches/series
--- whitedune-0.30.10/debian/patches/series 2019-02-12 14:32:01.0 
-0700
+++ whitedune-0.30.10/debian/patches/series 2024-04-15 11:20:26.0 
-0600
@@ -1,3 +1,4 @@
 libxp-configure.patch
 png1.5.patch
 avoid-grep-binary.patch
+implicit-declarations.patch

Processed: Re: FTBFS: error: implicit declaration of function 'yyerror'; did you mean 'yyerrok'? [-Werror=implicit-function-declaration]

2024-04-15 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 patch
Bug #1067618 [src:whitedune] FTBFS: error: implicit declaration of function 
'yyerror'; did you mean 'yyerrok'? [-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Processed: Re: st: FTBFS on arm{el,hf}: res.c:115:12: error: implicit declaration of function ‘_getshort’; did you mean ‘__putshort’? [-Werror=implicit-function-declaration]

2024-04-15 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 patch
Bug #1065797 [src:st] st: FTBFS on arm{el,hf}: res.c:115:12: error: implicit 
declaration of function ‘_getshort’; did you mean ‘__putshort’? 
[-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Processed: Re: uhub: FTBFS: adcclient.c:178:33: error: implicit declaration of function ‘ADC_client_connect_internal’; did you mean ‘ADC_client_connect’? [-Werror=implicit-function-declaration]

2024-04-15 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 patch
Bug #1066247 [src:uhub] uhub: FTBFS: adcclient.c:178:33: error: implicit 
declaration of function ‘ADC_client_connect_internal’; did you mean 
‘ADC_client_connect’? [-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1066247: uhub: FTBFS: adcclient.c:178:33: error: implicit declaration of function ‘ADC_client_connect_internal’; did you mean ‘ADC_client_connect’? [-Werror=implicit-function-declaration]

2024-04-15 Thread Zixing Liu

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

Dear Maintainer,

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

  * debian/patches/implicit-declarations.patch: Add missing function
prototypes.  (LP: #2061039).
  * debian/patches/riscv64-fix-ftbfs.patch: Add RISC-V architecture to
CPU list.  Thanks to Eric Long .  (LP: #2061039).


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-27-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru uhub-0.4.1/debian/patches/implicit-declarations.patch 
uhub-0.4.1/debian/patches/implicit-declarations.patch
--- uhub-0.4.1/debian/patches/implicit-declarations.patch   1969-12-31 
17:00:00.0 -0700
+++ uhub-0.4.1/debian/patches/implicit-declarations.patch   2024-04-15 
12:08:31.0 -0600
@@ -0,0 +1,20 @@
+Description: Add missing function prototypes
+ This fixes FTBFS on armhf
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066247
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/uhub/+bug/2061039
+Forwarded: no
+Last-Update: 2024-04-15
+---
+Index: uhub/src/tools/adcclient.c
+===
+--- uhub.orig/src/tools/adcclient.c
 uhub/src/tools/adcclient.c
+@@ -88,6 +88,7 @@ static void ADC_client_on_login(struct A
+ static int ADC_client_parse_address(struct ADC_client* client, const char* 
arg);
+ static int ADC_client_on_recv_line(struct ADC_client* client, const char* 
line, size_t length);
+ static int ADC_client_send_queue(struct ADC_client* client);
++int ADC_client_connect_internal(struct ADC_client* client);
+ 
+ static void ADC_client_debug(struct ADC_client* client, const char* format, 
...)
+ {
diff -Nru uhub-0.4.1/debian/patches/riscv64-fix-ftbfs.patch 
uhub-0.4.1/debian/patches/riscv64-fix-ftbfs.patch
--- uhub-0.4.1/debian/patches/riscv64-fix-ftbfs.patch   1969-12-31 
17:00:00.0 -0700
+++ uhub-0.4.1/debian/patches/riscv64-fix-ftbfs.patch   2024-04-15 
12:09:00.0 -0600
@@ -0,0 +1,22 @@
+Description: Add RISC-V architecture to CPU list
+Author: Eric Long 
+Origin: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1020965;filename=riscv64-fix-ftbfs.patch;msg=5
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020965
+Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/uhub/+bug/2061039
+Forwarded: no
+Reviewed-by: Zixing Liu 
+Last-Update: 2022-09-30
+---
+--- a/src/system.h
 b/src/system.h
+@@ -242,6 +242,10 @@
+ #define CPUINFO "s390"
+ #endif
+ 
++#if defined(__riscv)
++#define CPUINFO "RISC-V"
++#endif
++
+ /* Misc */
+ #ifdef MSG_NOSIGNAL
+ #define UHUB_SEND_SIGNAL MSG_NOSIGNAL
diff -Nru uhub-0.4.1/debian/patches/series uhub-0.4.1/debian/patches/series
--- uhub-0.4.1/debian/patches/series2022-09-12 03:10:42.0 -0600
+++ uhub-0.4.1/debian/patches/series2024-04-15 12:09:00.0 -0600
@@ -1,3 +1,5 @@
 fix-build-on-hurd-i386
 openssl1.1.patch
 arm64-fix-ftbfs.patch
+implicit-declarations.patch
+riscv64-fix-ftbfs.patch

Processed: Re: tcpxtract: FTBFS: confy.c:494:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration]

2024-04-15 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 patch
Bug #1066484 [src:tcpxtract] tcpxtract: FTBFS: confy.c:494:16: error: implicit 
declaration of function ‘yylex’ [-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1066484: tcpxtract: FTBFS: confy.c:494:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration]

2024-04-15 Thread Zixing Liu

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

Dear Maintainer,

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

  * debian/patches/70_fix-implicit-declarations.patch: Add missing
includes and function prototypes.  Closes #1066484, LP: #2061589.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-27-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru tcpxtract-1.0.1/debian/patches/70_fix-implicit-declarations.patch 
tcpxtract-1.0.1/debian/patches/70_fix-implicit-declarations.patch
--- tcpxtract-1.0.1/debian/patches/70_fix-implicit-declarations.patch   
1969-12-31 17:00:00.0 -0700
+++ tcpxtract-1.0.1/debian/patches/70_fix-implicit-declarations.patch   
2024-04-15 10:41:14.0 -0600
@@ -0,0 +1,57 @@
+Description: Add missing includes and function prototypes
+ This fixes the FTBFS on armhf
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066484
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/2061589
+Forwarded: no
+Last-Update: 2024-04-15
+---
+Index: tcpxtract/conf.h
+===
+--- tcpxtract.orig/conf.h
 tcpxtract/conf.h
+@@ -24,5 +24,8 @@
+ #define CONF_H
+ 
+ extern void config_type(char *, char *, char *, char *);
++int yyparse (void);
++int yyerror(char *s);
++int yylex (void);
+ 
+ #endif /* CONF_H */
+Index: tcpxtract/confl.l
+===
+--- tcpxtract.orig/confl.l
 tcpxtract/confl.l
+@@ -20,6 +20,7 @@
+Tcpxtract, a sniffer that extracts files based on headers
+by Nick Harbour
+ */
++#include 
+ #include "confy.h"
+ %}
+ 
+Index: tcpxtract/confy.y
+===
+--- tcpxtract.orig/confy.y
 tcpxtract/confy.y
+@@ -23,6 +23,7 @@
+ 
+ #include 
+ #include "conf.h"
++#include "confy.h"
+ %}
+ 
+ %union {
+Index: tcpxtract/tcpxtract.c
+===
+--- tcpxtract.orig/tcpxtract.c
 tcpxtract/tcpxtract.c
+@@ -44,6 +44,7 @@
+ 
+ #include "sessionlist.h"
+ #include "util.h"
++#include "conf.h"
+ #include "confy.h"
+ #include "search.h"
+ 
diff -Nru tcpxtract-1.0.1/debian/patches/series 
tcpxtract-1.0.1/debian/patches/series
--- tcpxtract-1.0.1/debian/patches/series   2023-02-06 05:27:00.0 
-0700
+++ tcpxtract-1.0.1/debian/patches/series   2024-04-15 10:38:13.0 
-0600
@@ -4,3 +4,4 @@
 40_fix-png-header-bytes.patch
 50_fix-spelling-binary.patch
 60_libfl.patch
+70_fix-implicit-declarations.patch

Bug#1065944: squeak-plugins-scratch: FTBFS on arm{el,hf}: WeDoLinux.c:175:9: error: implicit declaration of function ‘close’; did you mean ‘pclose’? [-Werror=implicit-function-declaration]

2024-04-15 Thread Zixing Liu

Package: squeak-plugins-scratch
Followup-For: Bug #1065944
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

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

  * debian/patches/add-missing-include.patch: Add a missing header to
fix build on armhf.  (Closes #1065944, LP: #2061587).
  * debian/control: Add quilt to B-D as this is previously missing.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-27-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru squeak-plugins-scratch-1.4.0.2~svn.r83/debian/control 
squeak-plugins-scratch-1.4.0.2~svn.r83/debian/control
--- squeak-plugins-scratch-1.4.0.2~svn.r83/debian/control   2024-03-08 
00:00:18.0 -0700
+++ squeak-plugins-scratch-1.4.0.2~svn.r83/debian/control   2024-04-15 
10:23:53.0 -0600
@@ -1,8 +1,8 @@
 Source: squeak-plugins-scratch
 Section: devel
 Priority: optional
 Maintainer: Miriam Ruiz 
-Build-Depends: debhelper, dh-buildinfo,
+Build-Depends: debhelper, dh-buildinfo, quilt,
  libcairo2-dev (>= 1.8.6), libpango1.0-dev (>= 1.24.1),
  libglib2.0-dev (>= 2.20.1), libv4l-dev (>= 0.5.8)
 Standards-Version: 4.2.1.4
diff -Nru 
squeak-plugins-scratch-1.4.0.2~svn.r83/debian/patches/add-missing-include.patch 
squeak-plugins-scratch-1.4.0.2~svn.r83/debian/patches/add-missing-include.patch
--- 
squeak-plugins-scratch-1.4.0.2~svn.r83/debian/patches/add-missing-include.patch 
1969-12-31 17:00:00.0 -0700
+++ 
squeak-plugins-scratch-1.4.0.2~svn.r83/debian/patches/add-missing-include.patch 
2024-04-15 10:23:10.0 -0600
@@ -0,0 +1,19 @@
+Description: Add a missing header to fix build on armhf
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065944
+Bug-Ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/squeak-plugins-scratch/+bug/2061587
+Forwarded: no
+Last-Update: 2024-04-15
+---
+Index: squeak-plugins-scratch/wedo/WeDoLinux.c
+===
+--- squeak-plugins-scratch.orig/wedo/WeDoLinux.c
 squeak-plugins-scratch/wedo/WeDoLinux.c
+@@ -37,6 +37,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ 
+ 
diff -Nru squeak-plugins-scratch-1.4.0.2~svn.r83/debian/patches/series 
squeak-plugins-scratch-1.4.0.2~svn.r83/debian/patches/series
--- squeak-plugins-scratch-1.4.0.2~svn.r83/debian/patches/series
1969-12-31 17:00:00.0 -0700
+++ squeak-plugins-scratch-1.4.0.2~svn.r83/debian/patches/series
2024-04-15 10:17:28.0 -0600
@@ -0,0 +1 @@
+add-missing-include.patch

Processed: Re: squeak-plugins-scratch: FTBFS on arm{el,hf}: WeDoLinux.c:175:9: error: implicit declaration of function ‘close’; did you mean ‘pclose’? [-Werror=implicit-function-declaration]

2024-04-15 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 patch
Bug #1065944 [src:squeak-plugins-scratch] squeak-plugins-scratch: FTBFS on 
arm{el,hf}: WeDoLinux.c:175:9: error: implicit declaration of function ‘close’; 
did you mean ‘pclose’? [-Werror=implicit-function-declaration]
Added tag(s) patch.

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

Bug#1023971: marked as done (pantalaimon: Missing dependency on python3-pydbus)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 19:19:20 +
with message-id 
and subject line Bug#1023971: fixed in pantalaimon 0.10.5-2
has caused the Debian Bug report #1023971,
regarding pantalaimon: Missing dependency on python3-pydbus
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.)


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

Package: pantalaimon
Version: 0.9.1-1

Dear maintainers,


When python3-pydbus is not installed, panctl errors with this traceback:

$ panctl
Traceback (most recent call last):
  File "/usr/bin/panctl", line 33, in 
sys.exit(load_entry_point('pantalaimon==0.9.1', 'console_scripts', 
'panctl')())

  File "/usr/bin/panctl", line 25, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in 
import_module

return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1030, in _gcd_import
  File "", line 1007, in _find_and_load
  File "", line 986, in 
_find_and_load_unlocked

  File "", line 680, in _load_unlocked
  File "", line 790, in exec_module
  File "", line 228, in 
_call_with_frames_removed
  File "/usr/lib/python3/dist-packages/pantalaimon/panctl.py", line 32, 
in 

from pydbus import SessionBus
ModuleNotFoundError: No module named 'pydbus'


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pantalaimon
Source-Version: 0.10.5-2
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated pantalaimon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Apr 2024 20:49:27 +0200
Source: pantalaimon
Binary: pantalaimon python3-pantalaimon
Architecture: source all
Version: 0.10.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 pantalaimon - E2EE aware proxy daemon for matrix clients - daemon
 python3-pantalaimon - E2EE aware proxy daemon for matrix clients - python3 
module
Closes: 1023971
Changes:
 pantalaimon (0.10.5-2) unstable; urgency=medium
 .
   * QA upload. binary:all upload built with nocheck.
   * Add B-D: python3-logbook.
   * Add pantalaimon and panctl smoketests.
   * Add dependencies for panctl: python3-gi, python3-pydbus.
   * Add dependencies for pantalaimon: python3-dbus, python3-notify2.
 (Closes: #1023971)
Checksums-Sha1:
 e442c718bdb3b62cdaafe3f273b0f2ce285479f1 2441 pantalaimon_0.10.5-2.dsc
 7db7db42ab11c2b08884aa3e5aa37f841c874fc7 4540 
pantalaimon_0.10.5-2.debian.tar.xz
 12c2a458415774a2e82a894ac85589d10033bc11 16208 pantalaimon_0.10.5-2_all.deb
 a356851719314bbb7ba579cee7a1cac637ea88eb 9585 
pantalaimon_0.10.5-2_amd64.buildinfo
 f2251560c957e30b65844b1da22996c9c263eb5c 38908 
python3-pantalaimon_0.10.5-2_all.deb
Checksums-Sha256:
 7bc4184a52527f3ea6fb7d4817b5ed4d5fa9bf8e50080777de44fba930393dba 2441 
pantalaimon_0.10.5-2.dsc
 bfc24e9be69d8a3881368414aca69b8d23dd2c239bda2a923533afae513230e1 4540 
pantalaimon_0.10.5-2.debian.tar.xz
 d2f3d5068b380c8984048ac685fab9c21176d515d118739fa84e82dea83fec9b 16208 
pantalaimon_0.10.5-2_all.deb
 4ed389ed20d5419fe0979e01661b759f10f624d8f751f2752918fdb4d4385bdd 9585 
pantalaimon_0.10.5-2_amd64.buildinfo
 74b6ae4476667191c48937d1ff6e6b6d66c9a3255b67470870ae63a5dbd12850 38908 
python3-pantalaimon_0.10.5-2_all.deb
Files:
 9f39798579e47d132627338fa13be0e8 2441 net optional pantalaimon_0.10.5-2.dsc
 66185ea48bf7339c094ad21417fd65ca 4540 net optional 
pantalaimon_0.10.5-2.debian.tar.xz
 009541a1a605bbf782cfbf54054f1db3 16208 net optional 
pantalaimon_0.10.5-2_all.deb
 30ee0ee0ad2ccd7d1ae57584c30b919a 9585 net optional 
pantalaimon_0.10.5-2_amd64.buildinfo
 c3c16ba39c4d2e9d7ee029becb6f618f 38908 python optional

Bug#1069068: pantalaimon: FTBFS some tests fail with asyncio CancelledError

2024-04-15 Thread Andreas Beckmann

Source: pantalaimon
Version: 0.10.5-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

pantalaimon FTBFS in sid (but could be built successfully in bookworm):

   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd /build/pantalaimon-0.10.5/.pybuild/cpython3_3.11/build; 
python3.11 -m pytest tests
= test session starts ==
platform linux -- Python 3.11.9, pytest-8.1.1, pluggy-1.4.0
rootdir: /build/pantalaimon-0.10.5
plugins: Faker-24.4.0
collected 17 items

tests/pan_client_test.py .Fss.   [ 29%]
tests/proxy_test.py .E.E.E.E.E   [ 58%]
tests/store_test.py E...s..  [100%]

 ERRORS 
___ ERROR at teardown of TestClass.test_daemon_start[pyloop] ___

self = 
response_class = , method = 'GET'
path = 
'/_matrix/client/r0/sync?access_token=abc123_state=true=%7B%22room%22%3A%7B%22state%22%3A%7B%22lazy_load_members%22%3Atrue%7D%7D%7D'
data = None, response_data = None, content_type = None, trace_context = None
data_provider = None, timeout = 0, content_length = None, save_to = None

async def _send(
self,
response_class: Type,
method: str,
path: str,
data: Union[None, str, AsyncDataT] = None,
response_data: Optional[Tuple[Any, ...]] = None,
content_type: Optional[str] = None,
trace_context: Optional[Any] = None,
data_provider: Optional[DataProvider] = None,
timeout: Optional[float] = None,
content_length: Optional[int] = None,
save_to: Optional[os.PathLike] = None,
):
headers = (
{"Content-Type": content_type}
if content_type
else {"Content-Type": "application/json"}
)

if content_length is not None:
headers["Content-Length"] = str(content_length)

if self.config.custom_headers is not None:
headers.update(self.config.custom_headers)

got_429 = 0
max_429 = self.config.max_limit_exceeded

got_timeouts = 0
max_timeouts = self.config.max_timeouts

while True:
if data_provider:
# mypy expects an "Awaitable[Any]" but data_provider is a
# method generated during runtime that may or may not be
# Awaitable. The actual type is a union of the types that we
# can receive from reading files.
data = await data_provider(got_429, got_timeouts)  # type: 
ignore

try:
>   transport_resp = await self.send(
method,
path,
data,
headers,
trace_context,
timeout,
)

/usr/lib/python3/dist-packages/nio/client/async_client.py:777:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/nio/client/async_client.py:291: in wrapper
return await func(self, *args, **kwargs)
/usr/lib/python3/dist-packages/nio/client/async_client.py:855: in send
return await self.client_session.request(
/usr/lib/python3.11/unittest/mock.py:2251: in _execute_mock_call
result = await effect(*args, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = 
orig_self = 
method = 'GET'
url = 
URL('https://example.org/_matrix/client/r0/sync?access_token=abc123=%257B%2522room%2522%253A%257B%2522state%2522%253A%257B%2522lazy_load_members%2522%253Atrue%257D%257D%257D_state=true')
args = ()
kwargs = {'data': None, 'headers': {'Content-Type': 'application/json'}, 'ssl': 
False, 'timeout': 0, ...}
url_origin = 
'https://example.org/_matrix/client/r0/sync?access_token=abc123_state=true=%7B%22room%22%3A%7B%22state%22%3A%7B%22lazy_load_members%22%3Atrue%7D%7D%7D'
url_str = 
'https://example.org/_matrix/client/r0/sync?access_token=abc123=%257B%2522room%2522%253A%257B%2522state%2522%253A%257B%2522lazy_load_members%2522%253Atrue%257D%257D%257D_state=true'
prefix = 'http://127.0.0.1'
key = ('GET', 
URL('https://example.org/_matrix/client/r0/sync?access_token=abc123=%257B%2522room%2522%253A%257B%2522state%2522%253A%257B%2522lazy_load_members%2522%253Atrue%257D%257D%257D_state=true'))
request_call = RequestCall(args=(), kwargs={'data': None, 'ssl': False, 
'headers': {'Content-Type': 'application/json'}, 'trace_request_ctx': None, 
'timeout': 0, 'allow_redirects': True})
response = None

async def _request_mock(self, orig_self: ClientSession,
method: str, url: 'Union[URL, str]',
*args: Tuple,
**kwargs: Any) -> 'ClientResponse':
"""Return mocked response object or raise connection error."""
if

Processed: util-linux-extra: insufficient Replaces for util-linux due to /usr-move

2024-04-15 Thread Debian Bug Tracking System

Processing control commands:

> affects -1 + util-linux
Bug #1069064 [util-linux-extra] util-linux-extra: insufficient Replaces for 
util-linux due to /usr-move
Added indication that 1069064 affects util-linux

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

Bug#1069064: util-linux-extra: insufficient Replaces for util-linux due to /usr-move

2024-04-15 Thread Helmut Grohne

Package: util-linux-extra
Version: 2.40-6
Severity: serious
User: helm...@debian.org
Usertags: dep17p1
Control: affects -1 + util-linux

Hi Chris,

I think I mentioned this on IRC already and you intended to revert, but
nothing happened, so lets turn this into a bug for tracking purposes at
least.

util-linux-extra gained the utils ctrlaltdel, fsck.cramfs, fsck.minix,
mkfs.bfs, mkfs.cramfs, and mkfs.minix. In util-linux-extra, these now
reside below /usr/sbin while they used to reside in /sbin in util-linux
in bookworm and earlier. Hence upgrading from bookworm to sid can cause
these files to be lost.

I think we have three ways to address this:

 1. Revert the move and retry after trixie. I think you favoured this?
 2. Upgrade Breaks to Conflicts and issue a temporary protective
diversion from u-l-e.preinst to u-l-e.postinst. In theory, apt can
first unpack u-l, then unpack u-l-e and then configure both, so
there is a safe solution. However, there is a risk that apt could
decide to temporarily remove u-l and that would be really bad.
 3. Keep Breaks and issue temporary diversions to be removed in forky's
u-l-e.postinst.

Please let me know your choice and I can do a patch.

Helmut

Bug#1069059: cockpit update from DSA-5655-1 without binary builds (build failures)

2024-04-15 Thread Santiago Vila


found 1069059 239-1
found 1069059 287-1
tags 1069059 + bullseye bookworm
thanks

El 15/4/24 a las 19:28, Salvatore Bonaccorso escribió:

The update for cockpit in DSA 5655-1 had problems with the
test-sshbridge test, causing FTBFS:


For completeness: this was already happening in bullseye and bookworm
before the DSA. (Reminder for myself: report all the bugs I found
last week while rebuilding bullseye and bookworm).

Thanks.

Processed: Re: cockpit update from DSA-5655-1 without binary builds (build failures)

2024-04-15 Thread Debian Bug Tracking System

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

> found 1069059 239-1
Bug #1069059 [src:cockpit] cockpit update from DSA-5655-1 without binary builds 
(build failures)
Marked as found in versions cockpit/239-1.
> found 1069059 287-1
Bug #1069059 [src:cockpit] cockpit update from DSA-5655-1 without binary builds 
(build failures)
Marked as found in versions cockpit/287-1.
> tags 1069059 + bullseye bookworm
Bug #1069059 [src:cockpit] cockpit update from DSA-5655-1 without binary builds 
(build failures)
Added tag(s) bookworm and bullseye.
> thanks
Stopping processing here.

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

Bug#1068688: marked as done (tpm2-initramfs-tool dependencies unsatisfiable on 32-bit non-i386 architectures.)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 18:23:09 +
with message-id 
and subject line Bug#1068688: fixed in tpm2-initramfs-tool 0.2.2-2.1
has caused the Debian Bug report #1068688,
regarding tpm2-initramfs-tool dependencies unsatisfiable on 32-bit non-i386 
architectures.
to be marked as done.

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

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


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

Package: tpm2-initramfs-tool
Version: 1.0.1-1
Tags: trixie, sid
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, tpm2-initramfs-tool
depends on both libtss2-esys-3.0.2-0 and libtss2-esys-3.0.2-0t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
architectures).

Ubuntu has already fixed this issue by replacing the hardcoded
dependency on libtss2-esys-3.0.2-0 with code in debian/rules
that generates a dependency (not sure why they didn't just
remove it).

http://launchpadlibrarian.net/720835666/tpm2-initramfs-tool_0.2.2-2build1_0.2.2-2ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: tpm2-initramfs-tool
Source-Version: 0.2.2-2.1
Done: Sebastian Ramacher 

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

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

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated 
tpm2-initramfs-tool package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 19:49:00 +0200
Source: tpm2-initramfs-tool
Architecture: source
Version: 0.2.2-2.1
Distribution: unstable
Urgency: medium
Maintainer: Jian-Ding Chen (timchen119) 
Changed-By: Sebastian Ramacher 
Closes: 1068688
Changes:
 tpm2-initramfs-tool (0.2.2-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * debian/control: Remove hard-coded dependency on libtss2-esys-3.0.0-0
 (Closes: #1068688)
Checksums-Sha1:
 55e873f8f33c9109d927b40518eb447463a04cab 1514 tpm2-initramfs-tool_0.2.2-2.1.dsc
 b38622ca95abf502ddf82bf09c3dc52c6616d1c9 2020 
tpm2-initramfs-tool_0.2.2-2.1.debian.tar.xz
 2df820647f41be0bd1da14b81c55b887156c13ad 8077 
tpm2-initramfs-tool_0.2.2-2.1_amd64.buildinfo
Checksums-Sha256:
 3f469ab0c996b57a1db6d301733e1742d30077ff01cf07d879eb5a39d0143fce 1514 
tpm2-initramfs-tool_0.2.2-2.1.dsc
 bdd8d010bdbf2eae1a01eed621bc43df011797acadfcc142c1935a5cba3959fe 2020 
tpm2-initramfs-tool_0.2.2-2.1.debian.tar.xz
 e77ee72717d330e9f66d832a846e13a3a7b80b36de8496777a5b44ddecb59489 8077 
tpm2-initramfs-tool_0.2.2-2.1_amd64.buildinfo
Files:
 4e5ce0c8426db066aa0551f0e5244a53 1514 admin optional 
tpm2-initramfs-tool_0.2.2-2.1.dsc
 93d5296c2acc6d88b5b4a773c9b7c2e8 2020 admin optional 
tpm2-initramfs-tool_0.2.2-2.1.debian.tar.xz
 50bd0673da9cace852a445671ba6c08a 8077 admin optional 
tpm2-initramfs-tool_0.2.2-2.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZhrGNgAKCRAhk2s2YA/N
iddTAP95SUqm757jUoVi7m5h/7x++9fbMiguo2IaRSAE4Umb1wEAvGmLqG9b21ZJ
miMU+9zqEqKal8aOXMRKx1PIrWBd7wo=
=1QHt
-END PGP SIGNATURE-



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

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

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 18:20:37 +
with message-id 
and subject line Bug#1068217: fixed in atomes 1.1.14-1.1
has caused the Debian Bug report #1068217,
regarding atomes, dependencies unsatisfiable on 32-bit non-i386 architectures.
to be marked as done.

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

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


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

Package: atomes
Version: 1.1.12+repack-2
Severity: grave
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, atomes depends
on both libgtk-3-0t64 and .libgtk-3-0t64 As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
archictures).

This applies to both versions 1.1.12+repack-2 and 1.1.14-1
--- End Message ---
--- Begin Message ---
Source: atomes
Source-Version: 1.1.14-1.1
Done: Sebastian Ramacher 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Apr 2024 19:42:07 +0200
Source: atomes
Architecture: source
Version: 1.1.14-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Sebastian Ramacher 
Closes: 1068217
Changes:
 atomes (1.1.14-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Removed hard-coded dependency on libgtk-3-0 (Closes:
 #1068217)
Checksums-Sha1:
 bb95d71e1bc4a7a0121ca6b5538be845090aaa3f 1598 atomes_1.1.14-1.1.dsc
 2461f27342d4ff60863723fea3d2cf81b6e139ec 14252 atomes_1.1.14-1.1.debian.tar.xz
 1a38de2659345df7689a147cc468bae705bedb09 17295 
atomes_1.1.14-1.1_amd64.buildinfo
Checksums-Sha256:
 109b6276240c2966e5e6b79476c06cd80e65be6060820ca12c374f589e97 1598 
atomes_1.1.14-1.1.dsc
 b1f3259233834f3a424bacac66bd88699d380714f4aad998672f85678cd6 14252 
atomes_1.1.14-1.1.debian.tar.xz
 31080d198985619349b1adc05fad6272ad5701b2d3aa29355b6602e41869a55d 17295 
atomes_1.1.14-1.1_amd64.buildinfo
Files:
 f5878d6d163563e4962a2567f802aa0f 1598 science optional atomes_1.1.14-1.1.dsc
 76253fe154f106d9008a0ca238e3bede 14252 science optional 
atomes_1.1.14-1.1.debian.tar.xz
 95086fb2e727264945962d95f7cf1238 17295 science optional 
atomes_1.1.14-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZhrEoAAKCRAhk2s2YA/N
ibZ+AP95mTFtaD/rtpyRkdDm+KqyTlBV1NcD57j1EvxJFaguewD+O5e6LcN1siOz
1KaZ8Zpi1p8zfLe3VWbv42GqNAsDMAw=
=ey17
-END PGP SIGNATURE-



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

Bug#1066970: marked as done (FTBFS: error: implicit declaration of function 'InitNibbleMem' [-Werror=implicit-function-declaration])

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 17:50:05 +
with message-id 
and subject line Bug#1066970: fixed in esnacc 1.8.1-4
has caused the Debian Bug report #1066970,
regarding FTBFS: error: implicit declaration of function 'InitNibbleMem' 
[-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.)


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

Source: esnacc
Version: 1.8.1-3
Severity: serious
Justification: FTBFS
Tags: sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-impfuncdef

Hi,

esnacc FTBFS:

gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -I./asn1specs 
-I./asn1specs -I./c-lib/inc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/home/rene/esnacc-1.8.1=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -O0 -Wall -Wextra -c -o c-examples/simple/sbuf-sbuf-ex.o 
`test -f 'c-examples/simple/sbuf-ex.c' || echo 
'./'`c-examples/simple/sbuf-ex.c
/bin/bash ./libtool  --tag=CC   --mode=link gcc -I./asn1specs 
-I./asn1specs -I./c-lib/inc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/home/rene/esnacc-1.8.1=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -O0 -Wall -Wextra  -Wl,-z,relro -o 
c-examples/simple/sbuf asn1specs/c_examples_simple_sbuf-p-rec.o 
c-examples/simple/sbuf-sbuf-ex.o c-lib/libcasn1.la -lm
libtool: link: gcc -I./asn1specs -I./asn1specs -I./c-lib/inc -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/home/rene/esnacc-1.8.1=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -O0 -Wall -Wextra -Wl,-z -Wl,relro -o 
c-examples/simple/.libs/sbuf asn1specs/c_examples_simple_sbuf-p-rec.o 
c-examples/simple/sbuf-sbuf-ex.o  c-lib/.libs/libcasn1.so -lm -pthread
gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -I./c-lib/inc 
-g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/home/rene/esnacc-1.8.1=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -O0 -Wall -Wextra -c -o 
c-examples/test-lib/testlib-test-lib.o `test -f 
'c-examples/test-lib/test-lib.c' || echo './'`c-examples/test-lib/test-lib.c

c-examples/test-lib/test-lib.c: In function 'main':
c-examples/test-lib/test-lib.c:68:5: error: implicit declaration of 
function 'InitNibbleMem' [-Werror=implicit-function-declaration]

   68 | InitNibbleMem (256, 256);
  | ^
[...]

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

Indeed a build with export DEB_BUILD_MAINT_OPTIONS=qa=-bug-implicit-func 
works. But better than disabling it would be to fix it of course ;)


Regards,

Rene
--- End Message ---
--- Begin Message ---
Source: esnacc
Source-Version: 1.8.1-4
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
esnacc, 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.
Andreas Beckmann  (supplier of updated esnacc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Apr 2024 19:35:47 +0200
Source: esnacc
Architecture: source
Version: 1.8.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1011071 1044667 1066970
Changes:
 esnacc (1.8.1-4) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * QA upload.
   * Fix building with -Werror=implicit-function-declaration.
 (Closes: #1066970)
   * Fix building twice in a row.  (Closes: #1044667)
   * esnacc-doc: Do not recommend evince.  (Closes: #1011071)
   * Declare Rules-Requires-Root: no.
   * CI: Allow the reprotest to fail due to libeoffice #1065448.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Debian Janitor ]
   *

Bug#1058545: marked as done (esnacc: FTBFS: make: *** [debian/rules:13: binary] Error 25)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 19:29:57 +0200
with message-id <18f89cf6-16e4-9739-0711-f193711a6...@debian.org>
and subject line Re: due to #1058653
has caused the Debian Bug report #1058545,
regarding esnacc: FTBFS: make: *** [debian/rules:13: binary] Error 25
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.)

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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> dh_install: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
> rm -rf /<>/debian/esnacc/usr/share/doc/snacc-doc/ \
> /<>/debian/esnacc/usr/share/man/man1/snacced.1*
> make[1]: Leaving directory '/<>'
>dh_installdocs
> dh_installdocs: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> dh_installdocs: error: Cannot find (any matches for) "doc/Esnacc.pdf" (tried 
> in .)
> 
> make: *** [debian/rules:13: binary] Error 25

The full build log is available from:
http://qa-logs.debian.net/2023/12/12/esnacc_1.8.1-3_unstable.log

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

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

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

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

On Sat, 16 Mar 2024 11:07:30 +0100 Rene Engelhard  wrote:

Error: source file could not be loaded

(the last message is it, the javaldx warning is harmless)

Which is due to a bug in libreoffice which is fixed by

libreoffice (4:24.2.0-2) experimental; urgency=medium

Sid now has 4:24.2.2-3 and the problem is no longer reproducible, thus 
closing.

Andreas--- End Message ---

Bug#1069059: cockpit update from DSA-5655-1 without binary builds (build failures)

2024-04-15 Thread Salvatore Bonaccorso

Source: cockpit
Version: 287.1-0+deb12u1
Severity: serious
Justification: missing binary builds, FTBFS
X-Debbugs-Cc: t...@security.debian.org, a...@debian.org, car...@debian.org

Hi

The update for cockpit in DSA 5655-1 had problems with the
test-sshbridge test, causing FTBFS:

>From the tail of the test failure:

# cockpit-protocol-DEBUG: test-ssh: output queue empty

(cockpit-ssh:3731): cockpit-ssh-WARNING **: 20:51:17.702: 
(src/ssh/cockpitsshrelay.c:1423):cockpit_ssh_connect: runtime check failed: 
(ssh_options_set (data->session, SSH_OPTIONS_HOST, host) == 0)

(cockpit-ssh:3731): cockpit-ssh-WARNING **: 20:51:17.702: 
(src/ssh/cockpitsshrelay.c:1424):cockpit_ssh_connect: runtime check failed: 
(ssh_options_parse_config (data->session, NULL) == 0)
# cockpit-protocol-DEBUG: test-ssh: reading input 1
# cockpit-protocol-DEBUG: test-ssh: received a 82 byte payload
# cockpit-protocol-DEBUG: test-ssh: want more data
**
cockpit-ssh:ERROR:src/ssh/test-sshbridge.c:560:wait_until_transport_init: 
assertion failed (json_object_get_string_member (init, "command") == "init"): 
("authorize" == "init")
Bail out! 
cockpit-ssh:ERROR:src/ssh/test-sshbridge.c:560:wait_until_transport_init: 
assertion failed (json_object_get_string_member (init, "command") == "init"): 
("authorize" == "init")
cockpit-ssh-Message: 20:51:17.704: cockpit-ssh some_host: -1 couldn't connect: 
Hostname required 'some_host' '22'
cockpit-ssh-Message: 20:51:17.704: couldn't write control message: Broken pipe
cockpit-ssh-Message: 20:51:17.704: couldn't write authorize message: 
Inappropriate ioctl for device
FAIL test-sshbridge (exit status: 134)

Regards,
Salvatore

Bug#1069055: chr: Hardcode build-depends on library pkg libqt5concurrent5, blocks time_64 transition

2024-04-15 Thread Boyuan Yang

Source: chr
Version: 0.1.77-1
Severity: serious
X-Debbugs-CC: c...@istoph.de

Dear Debian chr package maintainer,

Your package builds-depends on library package libqt5concurrent5,
which does not exist in Debian Sid after Debian 64-bit time_t transition
since the library package was renamed.

In all occurrences, you shall not build-depends on the library package
directly. Please replace such build-dependency with the actual
development package behind it. If no development package is needed in
this case, such build-dependency shall be removed.

If you have any questions or do not know how to find the corresponding
development package, please feel free to let me know.

Thanks,
Boyuan Yang


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

Bug#1066347: marked as done (jskeus: FTBFS: jpegmemcd.c:29:3: error: implicit declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? [-Werror=implicit-function-declaration])

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 16:19:47 +
with message-id 
and subject line Bug#1066307: fixed in euslisp 9.29+dfsg-1
has caused the Debian Bug report #1066307,
regarding jskeus: FTBFS: jpegmemcd.c:29:3: error: implicit declaration of 
function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-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.)


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

Hi,

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

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

Relevant part (hopefully):
> cc -fPIC -fsigned-char -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 -DLinux -D_REENTRANT -DGCC 
> -I/usr/share/euslisp/include -DTHREADED -DPTHREAD -DSVNVERSION=\"\" -fPIC 
> -falign-functions=8 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o 
> /<>/irteus/Linux64/obj/jpegmemcd.o jpegmemcd.c
> (cd /<>/irteus; ln -sf ../irteus irteus)
> make[2]: git: No such file or directory
> make[2]: git: No such file or directory
> cp -f irtext.l /<>/irteus/lib
> make[2]: git: No such file or directory
> make[2]: git: No such file or directory
> ; [34;7mlu-decompose2[0;34m is assumed to be undefined function[0m
> ; [34;7mlu-decompose2[0;34m is assumed to be undefined function[0m
> ; [34;7mlu-solve2[0;34m is assumed to be undefined function[0m
> ; [34;7mmatrix-determinant[0;34m is assumed to be undefined function[0m
> ; [34;7mm-[0;34m is assumed to be undefined function[0m
> ; [34;7mm+[0;34m is assumed to be undefined function[0m
> ; [34;7meps=[0;34m is assumed to be undefined function[0m
> ; [34;7meps=[0;34m is assumed to be undefined function[0m
> ; [34;7meps=[0;34m is assumed to be undefined function[0m
> ; [34;7meps=[0;34m is assumed to be undefined function[0m
> ; [34;7meps=[0;34m is assumed to be undefined function[0m
> ; [34;7mm+[0;34m is assumed to be undefined function[0m
> ; [34;7mm+[0;34m is assumed to be undefined function[0m
> ; [34;7mpseudo-inverse2[0;34m is assumed to be undefined function[0m
> ; [34;7mpseudo-inverse2[0;34m is assumed to be undefined function[0m
> ; [34;7mpseudo-inverse2[0;34m is assumed to be undefined function[0m
> ; [34;7msv-decompose[0;34m is assumed to be undefined function[0m
> ; [34;7mm+[0;34m is assumed to be undefined function[0m
> ; [34;7mm+[0;34m is assumed to be undefined function[0m
> ; [34;7mmatrix-determinant[0;34m is assumed to be undefined function[0m
> ; [34;7mqr-decompose[0;34m is assumed to be undefined function[0m
> ; [34;7mm+[0;34m is assumed to be undefined function[0m
> ; [34;7meps=[0;34m is assumed to be undefined function[0m
> ; [34;7meps=[0;34m is assumed to be undefined function[0m
> ; [34;7mm+[0;34m is assumed to be undefined function[0m
> ; [34;7msv-decompose[0;34m is assumed to be undefined function[0m
> ; [34;7mqr-decompose[0;34m is assumed to be undefined function[0m
> ; [34;7mqr-decompose[0;34m is assumed to be undefined function[0m
> ; [34;7mm+[0;34m is assumed to be undefined function[0m
> ; [34;7mm+[0;34m is assumed to be undefined function[0m
> ; [34;7mmatrix-determinant[0;34m is assumed to be undefined function[0m
> ; [34;7meps=[0;34m is assumed to be undefined function[0m
> ; [34;7meps=[0;34m is assumed to be undefined function[0m
> ; [34;7meps=[0;34m is assumed to be undefined function[0m
> ; [34;7msv-decompose[0;34m is assumed to be undefined function[0m
> ; [34;7mvector-mean[0;34m is assumed to be undefined function[0m
> ; [34;7mfind-extream[0;34m is assumed to be undefined function[0m
> ; [34;7mc-matrix-row[0;34m is assumed to be undefined function[0m
> jpegmemcd.c: In function ‘JPEG_compress’:
> jpegmemcd.c:29:3: error: implicit declaration of function ‘jpeg_memio_dest’; 
> did you mean ‘jpeg_mem_dest’? [-Werror=implicit-function-declaration]
>29 |   jpeg_memio_dest(, jpeg_image_buffer, _count);
>   |   ^~~
>   |

Bug#1066307: marked as done (euslisp: FTBFS: jpegmemcd.c:29:3: error: implicit declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? [-Werror=implicit-function-declaration])

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 16:19:47 +
with message-id 
and subject line Bug#1066307: fixed in euslisp 9.29+dfsg-1
has caused the Debian Bug report #1066307,
regarding euslisp: FTBFS: jpegmemcd.c:29:3: error: implicit declaration of 
function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-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.)


-- 
1066307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: euslisp
Version: 9.27+dfsg-7
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 -fPIC -fsigned-char -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 -c -o 
> /<>/Linux64/obj/jpegmemcd.o jpegmemcd.c
> jpegmemcd.c: In function ‘JPEG_compress’:
> jpegmemcd.c:29:3: error: implicit declaration of function ‘jpeg_memio_dest’; 
> did you mean ‘jpeg_mem_dest’? [-Werror=implicit-function-declaration]
>29 |   jpeg_memio_dest(, jpeg_image_buffer, _count);
>   |   ^~~
>   |   jpeg_mem_dest
> jpegmemcd.c: In function ‘JPEG_header’:
> jpegmemcd.c:92:3: error: implicit declaration of function ‘jpeg_memio_src’; 
> did you mean ‘jpeg_mem_src’? [-Werror=implicit-function-declaration]
>92 |   jpeg_memio_src(, jpeg_image, jpeg_size);
>   |   ^~
>   |   jpeg_mem_src
> cc1: some warnings being treated as errors
> make[2]: *** [makefile:50: /<>/Linux64/obj/jpegmemcd.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/euslisp_9.27+dfsg-7_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: euslisp
Source-Version: 9.29+dfsg-1
Done: Kei Okada 

We believe that the bug you reported is fixed in the latest version of
euslisp, 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.
Kei Okada  (supplier of updated euslisp 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: Mon, 15 Apr 2024 17:55:06 +0900
Source: euslisp
Architecture: source
Version: 9.29+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Debian Science Maintainers 

Changed-By: Kei Okada 
Closes: 1066307
Changes:
 euslisp (9.29+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 9.29+dfsg
   * remove patches already applied in 9.29,
 see https://github.com/euslisp/EusLisp/pull/482
   * fix debian/patches/fix-jpegmemcd-compile-error.patch for 9.29
 (Closes: #1066307)
 .
 euslisp (9.28+dfsg-2) unstable; urgency=high
 .
   * https://github.com/euslisp/EusLisp/pull/441 update 
lisp/image/jpeg/makefile, update debian/patches/fix-for-hardening.patch
   * https://github.com/euslisp/EusLisp/pull/441 update source code to pass 
repotest
   * debian/tests/euslisp-all-test: run make command in test directory to build

Bug#1068120: marked as done (mergerfs: builds binary packages with hardcoded dependencies on pre-t64 libraries)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 15:50:23 +
with message-id 
and subject line Bug#1068120: fixed in mergerfs 2.33.5-2
has caused the Debian Bug report #1068120,
regarding mergerfs: builds binary packages with hardcoded dependencies on 
pre-t64 libraries
to be marked as done.

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

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


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

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

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: mergerfs
Source-Version: 2.33.5-2
Done: Ritesh Raj Sarraf 

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

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

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated mergerfs 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: Mon, 15 Apr 2024 20:27:59 +0530
Source: mergerfs
Architecture: source
Version: 2.33.5-2
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf 
Changed-By: Ritesh Raj Sarraf 
Closes: 1068120
Changes:
 mergerfs (2.33.5-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * debian/copyright: use spaces rather than tabs to start continuation lines.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
   * Update standards version to 4.6.1, no changes needed.
 .
   [ Ritesh Raj Sarraf ]
   * Drop hardcoded runtime dependency on libfuse2 (Closes: 1068120)
Checksums-Sha1:
 537cef32cacf653a69fe84898d5286a352931f36 1882 mergerfs_2.33.5-2.dsc
 c060449e72cdfb39a2f07ce1fcad0d058e7efe92 5484 mergerfs_2.33.5-2.debian.tar.xz
 2d4541b4a7c5c82448b5b77135ba9da03fa1306f 6222 
mergerfs_2.33.5-2_source.buildinfo
Checksums-Sha256:
 86e9eb2cb412fb49ee213f2255a8c59d0ee85e5313d7f8a99e8efb92d2e6169d 1882 
mergerfs_2.33.5-2.dsc
 ac56f1618e261fe1dca611a59a07fff8771b91ac9d665433c584f29b4e0e4c83 5484 
mergerfs_2.33.5-2.debian.tar.xz
 20529cf7a2bc2bf340ca959c48aca84d58f8bcc713beb07d2656cccbef434b18 6222 
mergerfs_2.33.5-2_source.buildinfo
Files:
 0d2e18973897666380527db327cbf18d 1882 utils optional mergerfs_2.33.5-2.dsc
 00c956ce2ae47b3f444f6d74408d04ba 5484 utils optional 
mergerfs_2.33.5-2.debian.tar.xz
 84b99e721ea4ce94713e0877e560aaab 6222 utils optional 
mergerfs_2.33.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAmYdS2sACgkQpjpYo/Lh
dWkXnhAAhcm3oi4S90LSZlrbhMOAir4yW9KebA0bKqoE+v+huggLJ4oUQwKoO4A7
CiR378Cszo3rzcThR20JAb/Ra+punsKYR1v5n/VYrWPbgYWdJBTy6EwRE6WUb5Qe
PJmfLWsGJCe6ysHwaEplcR3ULyhj2IVHXCwXQpcGLWehPPfBzMY7cKQy/uGFJW7/
d0fX/yTW45GOYBoImrrCeB/fR3gkyN0ck0Ou8MKrVKNeV6X7CtMawDOiYNr36T4a
zM/v8IDBOXhtHqQw1JwqJ+cted58UE4sRimMc6Rwq8wJqbT4rd6a9o62e8glL6BZ
d9iVm4KwdR5bUpzQ7wb5+O8ywNhssHegXHHyK5tr7OI7+1jevEz0rV2uFVDiLEsr
d/vvqDPgsoBpUqKPy/H5y59mMj72UMzlJBnl0XBrXa5txnL5uFN/nRIg4VhnwqOs
1CsyQZD31wmp7lQO0G4Pcc4NHEVzQ4G95OxOWPQnFYfoF54YYB9qYXi1X0CqOhDw
jStNxTPjoccS4dz3oIqeuHlZRkjdIEY7R41eoMx8c7as0MilmV4jFLEFvFVPcF8g
5PsxqYVzMTPCxOQocxgE6zixt7FTZvlMoQOD2FvddLfgbFzGfZ9dAJ1JiZCQ8K/Y
h/qwqwmFejGshnOtWNH1Z26F2t/qYImXHzmK1orwXKT0sQJv4ZU=
=kPre
-END PGP SIGNATURE-



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

Bug#1069051: r-cran-spatstat.model: autopkgtest regression in testing

2024-04-15 Thread Graham Inggs

Source: r-cran-spatstat.model
Version: 3.2-8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Sometime around 2023-12-01, r-cran-spatstat.model's autopkgtest
regressed in testing [1].  I've copied what I hope is the relevant
part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-spatstat.model/testing/amd64/


104s Error in check.nvector(weights, nX, vname = "weights") :
104s Some values of weights are NA or NaN
104s Calls: local ... diagnose.ppm.engine -> density.ppp ->
pointweights -> check.nvector
104s In addition: Warning messages:
104s 1: Values of the covariate ‘cv’ were NA or undefined at 96% (1774
out of 1845) of the quadrature points. Occurred while executing:
ppm.ppp(Q = Y, trend = ~cv + I(cv^2), data = list(list(c(1,
1.91953576453823,
104s 2: Some infinite, NA or NaN increments were removed
104s 3: Numerical underflow detected: sigma is probably too small
104s Execution halted

Bug#1061519: shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 CVE-2023-40549 CVE-2023-40550 CVE-2023-40551

2024-04-15 Thread Steve McIntyre

On Mon, Apr 15, 2024 at 11:33:14AM +, Bastien Roucariès wrote:
>Source: shim
>Followup-For: Bug #1061519
>Control: tags -1 + patch
>
>Dear Maintainer,
>
>Please find a MR here
>https://salsa.debian.org/efi-team/shim/-/merge_requests/13

ACK. Thanks for trying to help, but the merge isn't the hard bit here.

Tthe new upstream is a little problematic and I'm debugging some boot
failures in my local CI already.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Into the distance, a ribbon of black
Stretched to the point of no turning back

Bug#1068412: apache2: Missing Upgrade to Security Issues in bookworm

2024-04-15 Thread logo

Package: apache2
Version: 2.4.57-2
Followup-For: Bug #1068412

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Security Updates in unstable are not propagated to stable
   * What exactly did you do (or not do) that was effective (or
 ineffective)?A
Waited for the update to arrive in bookworm

   * What was the outcome of this action?
Well it's not there after almost two weeks
   * What outcome did you expect instead?
...

*** End of the template - remove these template lines ***

Apparently there are build issues in sid (maybe due to t64 migration).
However that is not a problem in bookworm and after.

Please consider to work around the issues and have a fix for "normal users". 
Ubuntu has provided the update to 2.4.59 last week already.

Thank you!
 
Bets regards

Peter

PS: below is only one of my systems. arm64, amd64 and armhf all miss this 
update!

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

Kernel: Linux 6.1.0-18-arm64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apache2 depends on:
pn  apache2-bin
pn  apache2-data   
pn  apache2-utils  
ii  init-system-helpers1.65.2
ii  lsb-base   11.6
ii  media-types10.0.0
ii  perl   5.36.0-7+deb12u1
ii  procps 2:4.0.2-3
ii  sysvinit-utils [lsb-base]  3.06-4

Versions of packages apache2 recommends:
ii  ssl-cert  1.1.2

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
pn  www-browser

Bug#1067088: marked as done (zfs-linux: missing B-D: libtirpc-dev)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 12:52:42 +
with message-id 
and subject line Bug#1067088: fixed in zfs-linux 2.2.3-2
has caused the Debian Bug report #1067088,
regarding zfs-linux: missing B-D: libtirpc-dev
to be marked as done.

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

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


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

Dear maintainer,

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

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

...
checking for blkid... no
checking for blkid/blkid.h... yes
checking for main in -lblkid... yes
checking for library containing xdrmem_create... no
checking for libtirpc... no
checking for rpc/xdr.h... no
checking for rpc/xdr.h... no
checking for rpc/xdr.h... no
checking for rpc/xdr.h... no
configure: WARNING: cannot find tirpc via pkg-config or in the standard 
locations
configure: error: in `/build/zfs-linux-2.2.3':
configure: error: neither libc sunrpc support nor libtirpc is available, try 
installing libtirpc-devel

This could be fixed by adding an explicit Build-Depends on libtirpc-dev.
The glibc change will likely be reverted in the short term, but given
its a change we want to do for Trixie, this will only lower the severity
of the bug.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: zfs-linux
Source-Version: 2.2.3-2
Done: Shengqi Chen 

We believe that the bug you reported is fixed in the latest version of
zfs-linux, 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.
Shengqi Chen  (supplier of updated zfs-linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 14 Apr 2024 10:59:52 +0800
Source: zfs-linux
Architecture: source
Version: 2.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian ZFS on Linux maintainers 

Changed-By: Shengqi Chen 
Closes: 1067088
Changes:
 zfs-linux (2.2.3-2) unstable; urgency=medium
 .
   [ Shengqi Chen ]
   * d/control: add Build-Depends on libtirpc-dev (closes: #1067088)
   * Add patch to fix path in man/zfs_prepare_disk.8
   * d/control: upgrade to std-ver 4.7.0 (no changes required)
   * Some improvements to autopkgtest (see: #1068559):
 - d/control: add more recommends for zfs-test to fix tests
 - split zfs-test-suite into four smaller parts
 - try to skip some tests that require large memory
 - use presistent tmpdir for zfs-test-suite
 .
   [ Benda Xu ]
   * OpenRC no longer breaks the ZFS initscripts on Debian.
   * Fix substitution behaviour in config/Substfiles.am
Checksums-Sha1:
 40fe2accc15491832137949684d5dbfdc0994475 3273 zfs-linux_2.2.3-2.dsc
 47a99f7950776d6b59f725201f37656d23d33c8d 110100 zfs-linux_2.2.3-2.debian.tar.xz
 b5508e5255c3b472bfad9fe71b499be4182202a7 8361 
zfs-linux_2.2.3-2_source.buildinfo
Checksums-Sha256:
 57e42930c3b975aa5c90b24875ab432e1315048b0e613c5f1c7facf7abd71336 3273 
zfs-linux_2.2.3-2.dsc
 6bdf3fc9292559bd819ea84a5a5d1103da3564398dd27aebdd7cbcc0046ae186 110100 
zfs-linux_2.2.3-2.debian.tar.xz
 307a86df3a44b915a5d7dbc73676ea7632b1b3d0e274cfa880dc690fb0cc6e2b 8361 
zfs-linux_2.2.3-2_source.buildinfo
Files:
 1e147f6b0787c8fb7d136b48bd468952 3273 contrib/kernel optional 
zfs-linux_2.2.3-2.dsc
 e7346a12cb72dd1011b2055450f04cc6 110100 contrib/kernel optional 
zfs-linux_2.2.3-2.debian.tar.xz
 13c690bf683f0b3d2f6efa62690d4d01 8361 contrib/kernel optional 
zfs-linux_2.2.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEBLHAyuu1xqoC2aJ5NP8o68vMTMgFAmYdGhAACgkQNP8o68vM

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

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 12:51:25 +
with message-id 
and subject line Bug#1067318: fixed in python-pint 0.23-1
has caused the Debian Bug report #1067318,
regarding python-pint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:305: python3.12 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> running config
> I: pybuild base:305: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/compat.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/converters.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/parser.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/testing.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/numpy_func.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/registry_helpers.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/errors.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/registry.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/context.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/pint_eval.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/systems.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/matplotlib.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/_typing.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/measurement.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/util.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/formatting.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/quantity.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/definitions.py -> 
> /<>/.pybuild/cpython3_3.12_pint/build/pint
> copying pint/babel_names.py -> 
>

Bug#1067229: marked as done (metpy: autopkgtest regression with NumPy 1.26)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 12:51:25 +
with message-id 
and subject line Bug#1067229: fixed in python-pint 0.23-1
has caused the Debian Bug report #1067229,
regarding metpy: autopkgtest regression with NumPy 1.26
to be marked as done.

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

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


-- 
1067229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: metpy
Version: 1.6.1+ds-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

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


  142s >   if np.any(np.max(pressure, axis=vertical_dim) < 950 
  * units.hectopascal):
  142s E   TypeError: no implementation found for 'numpy.max' on types that 
implement __array_function__: [.Quantity'>]
  142s
  142s /usr/lib/python3/dist-packages/metpy/calc/thermo.py:4589: TypeError
  142s === short test summary info 

  142s FAILED tests/calc/test_calc_tools.py::test_get_layer_heights_agl - 
TypeError:...
  142s FAILED 
tests/calc/test_calc_tools.py::test_get_layer_heights_agl_bottom_no_interp
  142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction - 
TypeError: no...
  142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_edge - 
TypeErro...
  142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_list - 
TypeErro...
  142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_arr - 
TypeError...
  142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_full - 
TypeErro...
  142s FAILED 
tests/calc/test_calc_tools.py::test_angle_to_direction_invalid_scalar
  142s FAILED 
tests/calc/test_calc_tools.py::test_angle_to_direction_invalid_arr - T...
  142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_level_3 - 
TypeE...
  142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_level_2 - 
TypeE...
  142s FAILED tests/calc/test_calc_tools.py::test_angle_to_direction_level_1 - 
TypeE...
  142s FAILED 
tests/calc/test_kinematics.py::test_storm_relative_helicity_no_storm_motion
  142s FAILED 
tests/calc/test_kinematics.py::test_storm_relative_helicity_storm_motion
  142s FAILED 
tests/calc/test_kinematics.py::test_storm_relative_helicity_with_interpolation
  142s FAILED tests/calc/test_kinematics.py::test_storm_relative_helicity - 
TypeErro...
  142s FAILED tests/calc/test_kinematics.py::test_storm_relative_helicity_agl - 
Type...
  142s FAILED 
tests/calc/test_kinematics.py::test_storm_relative_helicity_masked - T...
  142s FAILED tests/calc/test_thermo.py::test_lfc_ml2 - TypeError: no 
implementation...
  142s FAILED tests/calc/test_thermo.py::test_lfc_and_el_below_lcl - TypeError: 
no i...
  142s FAILED tests/calc/test_thermo.py::test_gdi - TypeError: no 
implementation fou...
  142s FAILED tests/calc/test_thermo.py::test_gdi_xarray - TypeError: no 
implementat...
  142s FAILED tests/calc/test_thermo.py::test_gdi_arrays - TypeError: no 
implementat...
  142s FAILED tests/calc/test_thermo.py::test_gdi_profile - TypeError: no 
implementa...
  142s FAILED tests/calc/test_thermo.py::test_gdi_no_950_raises_valueerror - 
TypeErr...
  142s = 25 failed, 937 passed, 25 skipped, 268 deselected in 21.69s 
==


Cheers
Timo



-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmX7B5EACgkQ+C8H+466
LVmokQv+OIpBqsgrDGYODgkQxUW/D+rWrkJtJehe8HjFXsCVtOViQjC4WaSGcvR3
vnLkRoeEPbNTCUmjMzOsoRtDqx2mQ4BPKGZboBc/64G6JPtgrB1WRAVrxDXeeHVT
HMFmIWnoKV3FmNxvMSujPPK3t0HoawppkGlnK/66GOHWmj4SBfkSud9YuHQEfqDa
2H6uXeBA5TcxDEz+5qy32zNwtdGAksX3HnMcpnPBnCpi8l/ouPVXoaqDY4y/tB9w
e6iGFTJ9pYvJrI9n8eKOZCg6odI/z1Yhl3pPT7dg//zwzOCM8dtNBHM/tQWV1wUd
DUBp2H05RqgF+tJsjJ+HnLYzRCFjK0trQRAcG48UlrJJoG8FDrVzyGjQ4UNj2D6J
3J+0UkTEi7lqLasBFLZl0XsQX/Hom/XWNq4LBM6oObCWWoa5b0i7T5sCtrWKASVl
/oT6t77ms6O/eyLb68BT73tMxIzWecWYA42y8vocSXrQnbF32OGqYHr3AvhQeui9
ImdiPbEZ
=qYXE
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: python-pint
Source-Version: 0.23-1
Done: Antonio Valentino 

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

Bug#1067278: marked as done (proxycheck: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 1)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 12:51:14 +
with message-id 
and subject line Bug#1067278: fixed in proxycheck 0.49a-8
has caused the Debian Bug report #1067278,
regarding proxycheck: FTBFS: make[1]: *** [debian/rules:13: 
override_dh_auto_clean] 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.)


-- 
1067278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proxycheck
Version: 0.49a-7
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> ./configure
> Configuring proxycheck 0.49a (2004-05-29)
> 
> checking for C compiler... gcc
> checking whenever C compiler (gcc) works... yes
> checking for socket routines... no
> checking for socket routines in -lsocket -lnsl... no
> configure: see config.log and conftest.* for possible explanation
> make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/19/proxycheck_0.49a-7_unstable.log

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

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

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

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

We believe that the bug you reported is fixed in the latest version of
proxycheck, 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 Beckmann  (supplier of updated proxycheck package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Apr 2024 13:46:34 +0200
Source: proxycheck
Architecture: source
Version: 0.49a-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1067278
Changes:
 proxycheck (0.49a-8) unstable; urgency=medium
 .
   * QA upload.
   * Fix building with -Werror=implicit-function-declaration.
 (Closes: #1067278)
   * Simplify cleaning.
Checksums-Sha1:
 db6112dfcccd5db34cd909ae3ca111810cfbb2d9 1878 proxycheck_0.49a-8.dsc
 569008ea966ea58957ab85be00f84f6ba5ed327e 6080 proxycheck_0.49a-8.debian.tar.xz
 688779f76f3c053b79784a048c32c6a528b46d09 5639 
proxycheck_0.49a-8_source.buildinfo
Checksums-Sha256:
 ba82257767ebddd0c0433fe0914946dd9c74addc7f512490bd52064956dab8e6 1878 
proxycheck_0.49a-8.dsc
 f243f2375a18bd657c60e0cf72dd27c31c46dc45c2a1648658596bdb003903dc 6080 
proxycheck_0.49a-8.debian.tar.xz
 15143e8abb28be221138a086da74564003e2228cf4b90367acab04df3f915534 5639 
proxycheck_0.49a-8_source.buildinfo
Files:
 54ec053366ca1d98b768e66a09dfcc5a 1878 net optional proxycheck_0.49a-8.dsc
 0c08920a78ade9d5122f0cc29f5b9442 6080 net optional 
proxycheck_0.49a-8.debian.tar.xz
 0bc8a1209efb2f5eca9250b87249ff14 5639 net optional 
proxycheck_0.49a-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYdFCoQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCDBfD/9q9eogC3ImTJqVtkvKOb8OgrIzdgHOEWuQ
WpbtxmFPHREpeCbOi8wQEaKFl/yDVxgKKZ0B1DOh80Hn+K0MkHCuu1H47TOlTGTL
b8TWyC846ntHp+JzIxov2e6L+1NQu4jD7va1XXuh3WuSEggNPbF+vfaozO6di1lL
4hAuPwhEd8+8RXyL6XBA8o38HKDPPyR1JC/emlXxOKF8Gm10/noSNtB6Jt1m5ENh
lVCphn8kBx4wL3TS1kqruuipaFb+/xWWh5Zh1SiVN+WxRCOl0kdJG2eqbjvpxYRa

Processed: closing 1054749

2024-04-15 Thread Debian Bug Tracking System

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

> close 1054749
Bug #1054749 [src:ruby-pry-byebug] ruby-android-key-attestation: FTBFS: ERROR: 
Test "ruby3.1" failed: Failure/Error: require "pry-byebug"
Bug #1054737 [src:ruby-pry-byebug] ruby-pry-byebug: FTBFS: ERROR: Test 
"ruby3.1" failed: 
:86:in 
`require': cannot load such file -- pry-byebug (LoadError)
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1066653: marked as done (prime-phylo: FTBFS: gb.tab.c:1096:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration])

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 13:32:29 +0200
with message-id 
and subject line Re: prime-phylo: FTBFS: gb.tab.c:1096:16: error: implicit 
declaration of function ‘yylex’ [-Werror=implicit-function-declaration]
has caused the Debian Bug report #1066653,
regarding prime-phylo: FTBFS: gb.tab.c:1096:16: error: implicit declaration of 
function ‘yylex’ [-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.)


-- 
1066653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prime-phylo
Version: 1.0.11-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):
> cd /<>/obj-x86_64-linux-gnu/src/cxx/libraries/sfile && 
> /usr/bin/cc -DONLY_ONE_TIMESAMPLE -DPERTURBED_NODE 
> -Dprime_phylo_sfile_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/src/cxx/libraries/sfile 
> -I/<>/src/cxx/libraries/sfile 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/ompi/mpi/cxx 
> -I/usr/include/libxml2 -I/<>/src/cxx/libraries/prime 
> -I/<>/obj-x86_64-linux-gnu/src/cxx/libraries/prime 
> -I/<>/src/cxx/libraries -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 -Wall 
> -fexceptions -g -fPIC -MD -MT 
> src/cxx/libraries/sfile/CMakeFiles/prime-phylo-sfile.dir/sfile.c.o -MF 
> CMakeFiles/prime-phylo-sfile.dir/sfile.c.o.d -o 
> CMakeFiles/prime-phylo-sfile.dir/sfile.c.o -c 
> /<>/src/cxx/libraries/sfile/sfile.c
> /<>/obj-x86_64-linux-gnu/src/cxx/libraries/sfile/gb.tab.c: In 
> function ‘yyparse’:
> /<>/obj-x86_64-linux-gnu/src/cxx/libraries/sfile/gb.tab.c:1096:16:
>  error: implicit declaration of function ‘yylex’ 
> [-Werror=implicit-function-declaration]
>  1096 |   yychar = yylex ();
>   |^
> gb.y: In function ‘yyerror’:
> gb.y:291:70: error: implicit declaration of function ‘linenumber’ 
> [-Werror=implicit-function-declaration]
> gb.y: In function ‘add_to_seq’:
> gb.y:402:9: warning: unused variable ‘new_buf’ [-Wunused-variable]
> /<>/src/cxx/libraries/sfile/gbread.c: In function ‘main’:
> /<>/src/cxx/libraries/sfile/gbread.c:17:10: error: implicit 
> declaration of function ‘strcmp’ [-Werror=implicit-function-declaration]
>17 | if (!strcmp(argv[opt], "-d")) {
>   |  ^~
> /<>/src/cxx/libraries/sfile/gbread.c:8:1: note: include 
> ‘’ or provide a declaration of ‘strcmp’
> 7 | #include "gb.tab.h"
>   +++ |+#include 
> 8 | 
> seqreader.l: In function ‘seq_read’:
> seqreader.l:270:9: warning: unused variable ‘code’ [-Wunused-variable]
> /<>/obj-x86_64-linux-gnu/src/cxx/libraries/sfile/lexer.c: At top 
> level:
> /<>/obj-x86_64-linux-gnu/src/cxx/libraries/sfile/lexer.c:1864:16:
>  warning: ‘input’ defined but not used [-Wunused-function]
>  1864 | static int input  (void)
>   |^
> /<>/obj-x86_64-linux-gnu/src/cxx/libraries/sfile/lexer.c:1821:17:
>  warning: ‘yyunput’ defined but not used [-Wunused-function]
>  1821 | static void yyunput (int c, char * yy_bp )
>   | ^~~
> /<>/src/cxx/libraries/sfile/sfile.c: In function ‘seq_print’:
> /<>/src/cxx/libraries/sfile/sfile.c:265:14: warning: format ‘%d’ 
> expects argument of type ‘int’, but argument 2 has type ‘long int’ [-Wformat=]
>   265 |   printf("%9d", char_counter + 1);
>   |  ^  
>   |  |
>   |  long int
> /<>/src/cxx/libraries/sfile/sfile.c:212:15: warning: variable 
> ‘date’ set but not used [-Wunused-but-set-variable]
>   212 |   char *top, *date;
>   |   ^~~~
> cc1: some warnings being treated as errors
> make[3]: *** 
> [src/cxx/libraries/sfile/CMakeFiles/prime-phylo-sfile.dir/build.make:90: 
> src/cxx/libraries/sfile/CMakeFiles/prime-phylo-sfile.dir/gbread.c.o] Error 1


The full build log is available from:

Processed: Re: shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 CVE-2023-40549 CVE-2023-40550 CVE-2023-40551

2024-04-15 Thread Debian Bug Tracking System

Processing control commands:

> tags -1 + patch
Bug #1061519 [src:shim] shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 
CVE-2023-40549 CVE-2023-40550 CVE-2023-40551
Added tag(s) patch.

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

Bug#1061519: shim: CVE-2023-40546 CVE-2023-40547 CVE-2023-40548 CVE-2023-40549 CVE-2023-40550 CVE-2023-40551

2024-04-15 Thread Bastien Roucariès

Source: shim
Followup-For: Bug #1061519
Control: tags -1 + patch

Dear Maintainer,

Please find a MR here
https://salsa.debian.org/efi-team/shim/-/merge_requests/13

Bastien


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

Bug#1069030: subread FTBFS on 32bit architectures: -Werror=implicit-function-declaration

2024-04-15 Thread Helmut Grohne

Source: subread
Version: 2.0.6+dfsg-2
Severity: serious
Tags: ftbfs

subread fails to build from source on 32bit architectures: A
non-parallel build contains:

| i686-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -mtune=generic -msse3 -O3 -fsigned-char -Wall 
-DMAKE_FOR_EXON  -D MAKE_STANDALONE -D SUBREAD_VERSION=\""2.0.6"\"  
-D_FILE_OFFSET_BITS=64  -fmessage-length=0 -ggdb -Wdate-time 
-D_FORTIFY_SOURCE=2  -c -o input-files.o input-files.c
| input-files.c: In function ‘f_subr_open’:
| input-files.c:54:24: error: implicit declaration of function ‘fopen64’; did 
you mean ‘gzopen64’? [-Werror=implicit-function-declaration]
|54 | return fopen64(fname, mode);
|   |^~~
|   |gzopen64

Helmut

Bug#1066271: marked as done (libdigidoc: FTBFS: DigiDocVerify.c:939:11: error: implicit declaration of function ‘ddocGetDNPartFromString’ [-Werror=implicit-function-declaration])

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 10:35:35 +
with message-id 
and subject line Bug#1066271: fixed in libdigidoc 3.10.5-5
has caused the Debian Bug report #1066271,
regarding libdigidoc: FTBFS: DigiDocVerify.c:939:11: error: implicit 
declaration of function ‘ddocGetDNPartFromString’ 
[-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.)


-- 
1066271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdigidoc
Version: 3.10.5-4.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):
> cd /<>/obj-x86_64-linux-gnu/libdigidoc && /usr/bin/cc 
> -DBUILD_DATE=\"28.02.2024\" -DBUILD_VER=0 -DMAJOR_VER=3 -DMINOR_VER=10 
> -DRELEASE_VER=5 -DVER_SUFFIX=\"\" -Ddigidoc_EXPORTS -I/<> 
> -I/<>/obj-x86_64-linux-gnu -I/usr/include/libxml2 -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 -fPIC 
> -fvisibility=hidden -MD -MT libdigidoc/CMakeFiles/digidoc.dir/DigiDocOCSP.c.o 
> -MF CMakeFiles/digidoc.dir/DigiDocOCSP.c.o.d -o 
> CMakeFiles/digidoc.dir/DigiDocOCSP.c.o -c 
> /<>/libdigidoc/DigiDocOCSP.c
> /<>/libdigidoc/DigiDocVerify.c:939:11: error: implicit 
> declaration of function ‘ddocGetDNPartFromString’ 
> [-Werror=implicit-function-declaration]
>   939 | err = ddocGetDNPartFromString(sDN, sId, );
>   |   ^~~
> /<>/libdigidoc/DigiDocVerify.c: In function 
> ‘verifyNotaryInfoCERT2’:
> /<>/libdigidoc/DigiDocVerify.c:1568:35: warning: passing 
> argument 1 of ‘ossl_check_X509_type’ discards ‘const’ qualifier from pointer 
> target type [-Wdiscarded-qualifiers]
>  1568 |   sk_X509_push(ver_certs, notCert);
>   |   ^~~
> In file included from /usr/include/openssl/types.h:33,
>  from /usr/include/openssl/x509.h:26:
> /usr/include/openssl/x509.h:78:1: note: expected ‘X509 *’ {aka ‘struct 
> x509_st *’} but argument is of type ‘const X509 *’ {aka ‘const struct x509_st 
> *’}
>78 | SKM_DEFINE_STACK_OF_INTERNAL(X509, X509, X509)
>   | ^
> In file included from /usr/include/string.h:535,
>  from /usr/include/openssl/ec.h:23,
>  from /usr/include/openssl/x509.h:33,
>  from /<>/libdigidoc/DigiDocLib.h:36,
>  from /<>/libdigidoc/DigiDocConvert.h:25,
>  from /<>/libdigidoc/DigiDocConvert.c:24:
> In function ‘strncat’,
> inlined from ‘breakToLinesOf64’ at 
> /<>/libdigidoc/DigiDocConvert.c:887:7:
> /usr/include/x86_64-linux-gnu/bits/string_fortified.h:138:10: warning: 
> ‘__builtin_strncat’ specified bound [9223372036854775811, 
> 18446744073709551615] exceeds maximum object size 9223372036854775807 
> [-Wstringop-overread]
>   138 |   return __builtin___strncat_chk (__dest, __src, __len,
>   |  ^~
>   139 |   __glibc_objsize (__dest));
>   |   ~
> /<>/libdigidoc/DigiDocOCSP.c: In function ‘WriteOCSPResponse’:
> /<>/libdigidoc/DigiDocOCSP.c:249:18: warning: passing argument 1 
> of ‘ASN1_i2d_bio’ from incompatible pointer type 
> [-Wincompatible-pointer-types]
>   249 | ASN1_i2d_bio((int (*)(void*, unsigned char**))i2d_OCSP_RESPONSE, 
> bout, (unsigned char*)resp);
>   |  ^~
>   |  |
>   |  int (*)(void *, unsigned char **)
> In file included from /usr/include/openssl/objects.h:21,
>  from /usr/include/openssl/evp.h:43,
>  from /usr/include/openssl/x509.h:29,
>  from /<>/libdigidoc/DigiDocLib.h:36,
>  from /<>/libdigidoc/DigiDocConfig.h:29,
>  from /<>/libdigidoc/DigiDocOCSP.c:23:
> /usr/include/openssl/asn1.h:967:31: note: expected ‘int (*)(const void *, 
> unsigned char **)’ but argument is of type ‘int (*)(void *,

Bug#1065774: marked as done (libdigidoc: FTBFS on arm{el,hf}: /<>/libdigidoc/DigiDocService.c:327:19: error: implicit declaration of function ‘ddocAddSignatureFromMemory’ [-Werror=implici

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 10:35:35 +
with message-id 
and subject line Bug#1065774: fixed in libdigidoc 3.10.5-5
has caused the Debian Bug report #1065774,
regarding libdigidoc: FTBFS on arm{el,hf}: 
/<>/libdigidoc/DigiDocService.c:327:19: error: implicit 
declaration of function ‘ddocAddSignatureFromMemory’ 
[-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.)


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

https://buildd.debian.org/status/fetch.php?pkg=libdigidoc=armel=3.10.5-4.1=1709133165=0

/<>/libdigidoc/DigiDocService.c:327:19: error: implicit 
declaration of function ‘ddocAddSignatureFromMemory’ 
[-Werror=implicit-function-declaration]
  327 | err = ddocAddSignatureFromMemory(pSigDoc, szFileName, 
(const void*)p1, strlen(p1));
  |   ^~
cc1: some warnings being treated as errors
make[3]: *** [libdigidoc/CMakeFiles/digidoc.dir/build.make:359: 
libdigidoc/CMakeFiles/digidoc.dir/DigiDocService.c.o] Error 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libdigidoc
Source-Version: 3.10.5-5
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
libdigidoc, 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.
Andreas Beckmann  (supplier of updated libdigidoc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Apr 2024 12:12:47 +0200
Source: libdigidoc
Architecture: source
Version: 3.10.5-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1065774 1066271
Changes:
 libdigidoc (3.10.5-5) unstable; urgency=medium
 .
   * QA upload.
   * Fix building with -Werror=implicit-function-declaration.
 (Closes: #1066271, #1065774)
Checksums-Sha1:
 b7cacb6f90edab58327d0a6b694df6ca5658d951 2233 libdigidoc_3.10.5-5.dsc
 65787b8b2461c57bc208b324f06e3b556a936b49 4652 libdigidoc_3.10.5-5.debian.tar.xz
 31d7fa4d3e4fb3b07ad36626abb4b2bee390d03f 7036 
libdigidoc_3.10.5-5_source.buildinfo
Checksums-Sha256:
 e6edd8df607f9aead6625c3e0a3aee65e3a90c9b351e8b3b255b9cd88b299a25 2233 
libdigidoc_3.10.5-5.dsc
 8160c7f51500213815ebac9a8d6b5b07449a870b0ae6c64c96ab10da4d63be1e 4652 
libdigidoc_3.10.5-5.debian.tar.xz
 5d056276648af5f2c512f09d5e40d08f030925057e8ff8ab3a81578d0166123b 7036 
libdigidoc_3.10.5-5_source.buildinfo
Files:
 dc036a6015487b6a6e9690624fd8b613 2233 libs optional libdigidoc_3.10.5-5.dsc
 bbcbd3fda191ef240794054e4246949f 4652 libs optional 
libdigidoc_3.10.5-5.debian.tar.xz
 073144d90fda2940909e3539f721d6f4 7036 libs optional 
libdigidoc_3.10.5-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmYc/eoQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCCEhD/9cNKDoqJ9e1e3CzsbkO5z+FWGm+PvTzswp
ZAGNjTk/5SOTYL2TNK9tQdFniPpyez5gIL8nkdchIVGQVSBwxD4DofUGnPgn4HrH
USUBLSHoIQzHj2fkN4PKC8xmtOO2U5bp7FYoOdnujthulAwTnl2+kfKWtD0uFXij
S7Ok39Z+3rldQbNDoeZBOlUsobP26jXjc2gguO/q2nkvRu9BTvOcuU+v03CZ4uL6
8mTVbRlIfiuwOvYg+uToxYX0KICU+jgG6nOiYGAnCCAXPQVvp/oeXRT/qzJLinZp
NrA1XWFyvf79EkItEoLcxrwyY7T1stzIB4rhotFcpLArJMqjfhUjhOZNWb+jPFYf
u2/vTYLMtlpG5kQuOLnadqHZK0YyEWR2QqjQC2a4c5IGOIZRn65rQdQU3R9ob2Rf
haBt3mKoB1HHb/swtz9AwmS/iFDTn9zcmCjpG75C2lsXpKn37fmMmxB2P/aWX4fP
FBcTbhGeXNY4TthRK7n1ILkEKtxDldg8RpsNefgm6B4ttzP3H6Ll/VZ8ccR87yN4
+Gy+ZcoeimDr+9HCpFn9WoXyNbotdKpubXs3WZBNRyTPRJXFPZ1hQT3SXeYRDpaK
eULiw00C26Bvnuvltwu7lHc1DYlKk9sSj/w9sIRp6CzT2ERDp5xL3iGtv/3MXfQc
24xjqaLexg==
=3MsA
-END PGP SIGNATURE-



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

Bug#1066489: marked as done (p0f: FTBFS: .build-609357.c:2:34: error: implicit declaration of function ‘printf’ [-Werror=implicit-function-declaration])

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 10:20:43 +
with message-id 
and subject line Bug#1066489: fixed in p0f 3.09b-4
has caused the Debian Bug report #1066489,
regarding p0f: FTBFS: .build-609357.c:2:34: error: implicit declaration of 
function ‘printf’ [-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.)


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

Hi,

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

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> Welcome to the build script for p0f 3.09b!
> Copyright (C) 2012 by Michal Zalewski 
> 
> [+] Configuring production build.
> [*] Checking for a sane build environment... OK
> [*] Checking for working GCC... OK
> [*] Checking for *modern* GCC... OK
> [*] Checking if memory alignment is required... FAIL
> 
> Well, something went horribly wrong, sorry. Here's the output from GCC:
> 
> .build-609357.c: In function ‘main’:
> .build-609357.c:2:34: error: implicit declaration of function ‘printf’ 
> [-Werror=implicit-function-declaration]
> 2 | volatile u8 tmp[6]; int main() { printf("%d\n", *(u32*)(tmp+1)); 
> return 0; }
>   |  ^~
> .build-609357.c:2:1: note: include ‘’ or provide a declaration of 
> ‘printf’
> 1 | #include "types.h"
>   +++ |+#include 
> 2 | volatile u8 tmp[6]; int main() { printf("%d\n", *(u32*)(tmp+1)); 
> return 0; }
> .build-609357.c:2:34: warning: incompatible implicit declaration of built-in 
> function ‘printf’ [-Wbuiltin-declaration-mismatch]
> 2 | volatile u8 tmp[6]; int main() { printf("%d\n", *(u32*)(tmp+1)); 
> return 0; }
>   |  ^~
> .build-609357.c:2:34: note: include ‘’ or provide a declaration of 
> ‘printf’
> cc1: some warnings being treated as errors
> 
> Sorry! You may want to ping  about this.
> 
> make[1]: *** [Makefile:11: all] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/p0f_3.09b-3_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: p0f
Source-Version: 3.09b-4
Done: Arnaud Rebillout 

We believe that the bug you reported is fixed in the latest version of
p0f, 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.
Arnaud Rebillout  (supplier of updated p0f 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: Mon, 15 Apr 2024 16:30:33 +0700
Source: p0f
Architecture: source
Version: 3.09b-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Arnaud Rebillout 
Closes: 1066489
Changes:
 p0f (3.09b-4) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure URI in Homepage field.
 .
   [ Arnaud Rebillout ]
   * Add patch to fix build with -Werror=implicit-function-declaration
 (Closes: #1066489)
   * Add smoke test
Checksums-Sha1:

Bug#1066246: marked as done (lcm: FTBFS: emit_cpp.c:306:19: error: implicit declaration of function ‘_exit’ [-Werror=implicit-function-declaration])

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 10:04:58 +
with message-id 
and subject line Bug#1066246: fixed in lcm 1.3.1+repack1-8
has caused the Debian Bug report #1066246,
regarding lcm: FTBFS: emit_cpp.c:306:19: error: implicit declaration of 
function ‘_exit’ [-Werror=implicit-function-declaration]
to be marked as done.

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

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


-- 
1066246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lcm
Version: 1.3.1+repack1-7
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 -DPACKAGE_NAME=\"lcm\" -DPACKAGE_TARNAME=\"lcm\" 
> -DPACKAGE_VERSION=\"1.3.1\" -DPACKAGE_STRING=\"lcm\ 1.3.1\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"lcm\" 
> -DVERSION=\"1.3.1\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 
> -DLT_OBJDIR=\".libs/\" -I.  -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread  -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -std=gnu99 -Wall -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -D_REENTRANT -Wno-unused-parameter 
> -Wno-format-zero-length -Wshadow -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> -o emit_csharp.o emit_csharp.c
> emit_cpp.c: In function ‘emit_header_start’:
> emit_cpp.c:306:19: error: implicit declaration of function ‘_exit’ 
> [-Werror=implicit-function-declaration]
>   306 |   _exit(1);
>   |   ^
> emit_cpp.c:306:19: warning: incompatible implicit declaration of built-in 
> function ‘_exit’ [-Wbuiltin-declaration-mismatch]
> In function ‘ensure_token_capacity’,
> inlined from ‘tokenize_next_internal’ at tokenize.c:325:14:
> tokenize.c:127:28: warning: argument 2 range [18446744071562067968, 
> 18446744073709551615] exceeds maximum object size 9223372036854775807 
> [-Walloc-size-larger-than=]
>   127 | t->token = (char*) realloc(t->token, t->token_capacity);
>   |^~~~
> In file included from tokenize.c:1:
> /usr/include/stdlib.h: In function ‘tokenize_next_internal’:
> /usr/include/stdlib.h:564:14: note: in a call to allocation function 
> ‘realloc’ declared here
>   564 | extern void *realloc (void *__ptr, size_t __size)
>   |  ^~~
> gcc -DPACKAGE_NAME=\"lcm\" -DPACKAGE_TARNAME=\"lcm\" 
> -DPACKAGE_VERSION=\"1.3.1\" -DPACKAGE_STRING=\"lcm\ 1.3.1\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"lcm\" 
> -DVERSION=\"1.3.1\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 
> -DLT_OBJDIR=\".libs/\" -I.  -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread  -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -std=gnu99 -Wall -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -D_REENTRANT -Wno-unused-parameter 
> -Wno-format-zero-length -Wshadow -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> -o emit_python.o emit_python.c
> gcc -DPACKAGE_NAME=\"lcm\" -DPACKAGE_TARNAME=\"lcm\" 
> -DPACKAGE_VERSION=\"1.3.1\" -DPACKAGE_STRING=\"lcm\ 1.3.1\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"lcm\" 
> -DVERSION=\"1.3.1\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_DLFCN_H=1 
> -DLT_OBJDIR=\".libs/\" -I.  -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread  -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -std=gnu99 -Wall -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -D_REENTRANT -Wno-unused-parameter 
>

Processed: Re: Bug#1065270: Unable to open VTK file with appended data that were fine with previous versions (invalid token in vtkXMLDataParser)

2024-04-15 Thread Debian Bug Tracking System

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

> block 1065270 by 1064762
Bug #1065270 [paraview] Unable to open VTK file with appended data that were 
fine with previous versions (invalid token in vtkXMLDataParser)
1065270 was not blocked by any bugs.
1065270 was not blocking any bugs.
Added blocking bug(s) of 1065270: 1064762
> thanks
Stopping processing here.

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

Bug#1069027: python3-notebook: Jupyter Notebook fails to start - wrong call to traitlets.warn

2024-04-15 Thread Christian Holm Christensen

Package: python3-notebook
X-Debbugs-Cc: chol...@gmail.com
Version: 6.4.12-2.2
Severity: grave
Justification: renders package unusable

When launching `jupyter notebook`, the following stack-trace is produced:

Begin stack-trace
```
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/notebook/traittypes.py", line 235, in
_resolve_classes
klass = self._resolve_string(klass)
^^^
  File "/usr/lib/python3/dist-packages/traitlets/traitlets.py", line 2015, in
_resolve_string
return import_item(string)
   ^^^
  File "/usr/lib/python3/dist-packages/traitlets/utils/importstring.py", line
33, in import_item
module = __import__(package, fromlist=[obj])
 ^^^
ModuleNotFoundError: No module named 'jupyter_server.contents'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/jupyter-notebook", line 33, in 
sys.exit(load_entry_point('notebook==6.4.12', 'console_scripts', 'jupyter-
notebook')())
^
  File "/usr/lib/python3/dist-packages/jupyter_core/application.py", line 282,
in launch_instance
super().launch_instance(argv=argv, **kwargs)
  File "/usr/lib/python3/dist-packages/traitlets/config/application.py", line
1073, in launch_instance
app = cls.instance(**kwargs)
  ^^
  File "/usr/lib/python3/dist-packages/traitlets/config/configurable.py", line
583, in instance
inst = cls(*args, **kwargs)
   
  File "/usr/lib/python3/dist-packages/traitlets/traitlets.py", line 1292, in
__new__
inst.setup_instance(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/traitlets/traitlets.py", line 1335, in
setup_instance
super(HasTraits, self).setup_instance(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/traitlets/traitlets.py", line 1311, in
setup_instance
init(self)
  File "/usr/lib/python3/dist-packages/notebook/traittypes.py", line 226, in
instance_init
self._resolve_classes()
  File "/usr/lib/python3/dist-packages/notebook/traittypes.py", line 238, in
_resolve_classes
warn(f"{klass} is not importable. Is it installed?", ImportWarning)
TypeError: warn() missing 1 required keyword-only argument: 'stacklevel'
```
End stack-trace

The offending line is line 238 of `/usr/lib/python3/dist-
packages/notebook/traittypes.py` where `traitlets.warn` is called

```
 warn(f"{klass} is not importable. Is it installed?", ImportWarning)
```

The call fails to provide the required keyword argument `stacklevel` as seen in
line 9 of

```
/usr/lib/python3/dist-packages/traitlets/utils/warnings.py
```

A solution could be to patch the `jypyter-notebook` sources, though that would
probably need to be done in many places, or perhaps and update to newer
sources.

Yours,
Christian



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

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

Versions of packages python3-notebook depends on:
ii  fonts-font-awesome 5.0.10+really4.7.0~dfsg-4.1
ii  libjs-backbone 1.4.1~dfsg+~1.4.15-3
ii  libjs-bootstrap3.4.1+dfsg-3
ii  libjs-bootstrap-tour   0.12.0+dfsg-5
ii  libjs-codemirror   5.65.0+~cs5.83.9-3
ii  libjs-es6-promise  4.2.8-12
ii  libjs-jed  1.1.1-4
ii  libjs-jquery   3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-typeahead 2.11.0+dfsg1-3
ii  libjs-jquery-ui1.13.2+dfsg-1
ii  libjs-marked   4.2.3+ds+~4.0.7-3
ii  libjs-mathjax  2.7.9+dfsg-1
ii  libjs-moment   2.29.4+ds-1
ii  libjs-requirejs2.3.6+ds+~2.1.34-2
ii  libjs-requirejs-text   2.0.12-1.1
ii  libjs-text-encoding0.7.0-5
ii  libjs-underscore   1.13.4~dfsg+~1.11.4-3
ii  libjs-xterm5.3.0-2
ii  python33.11.8-1
ii  python3-argon2 21.1.0-2
ii  python3-ipykernel  6.29.3-1
ii  python3-ipython-genutils   0.2.0-6
ii  python3-jinja2 3.1.3-1
ii  python3-jupyter-client 7.4.9-2
ii  python3-jupyter-core   5.3.2-1
ii  python3-nbconvert  6.5.3-5
ii  python3-nbformat   5.9.1-1
ii  python3-nest-asyncio   1.5.4-1
ii  python3-prometheus-client  0.19.0+ds1-1
ii  python3-send2trash 1.8.2-1
ii  python3-terminado  0.18.0-1
ii  python3-tornado6.4.0-1
ii  python3-traitlets  5.14.2-2
ii  python3-zmq24.0.1-5+b1

Versions of packages python3-notebook recommends:
ii  python3-ipywidgets

Processed: notfound 1068657

2024-04-15 Thread Debian Bug Tracking System

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

> notfound 1068657 0.3-1
Bug #1068657 {Done: Luca Boccassi } [src:pkcs11-provider] 
pkcs11-provider FTBFS with openssl 3.2.1-3
No longer marked as found in versions pkcs11-provider/0.3-1.
>
End of message, stopping processing here.

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

Processed: Bug#1066489 marked as pending in p0f

2024-04-15 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1066489 [src:p0f] p0f: FTBFS: .build-609357.c:2:34: error: implicit 
declaration of function ‘printf’ [-Werror=implicit-function-declaration]
Added tag(s) pending.

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

Bug#1066489: marked as pending in p0f

2024-04-15 Thread Arnaud Rebillout

Control: tag -1 pending

Hello,

Bug #1066489 in p0f 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/pkg-security-team/p0f/-/commit/83df5c38d86652c0f4b7501a682ba705dd443d75


Add patch to fix build with -Werror=implicit-function-declaration

Closes: #1066489


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1066489

Processed: found 1067264 in 7.0.3+git20221109.ee13eb9+dfsg-2, tagging 1067264, closing 1067264 ...

2024-04-15 Thread Debian Bug Tracking System

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

> found 1067264 7.0.3+git20221109.ee13eb9+dfsg-2
Bug #1067264 [node-node-sass] select2.js: FTBFS: make[1]: *** [debian/rules:7: 
override_dh_auto_build] Error 3
Bug #1067265 [node-node-sass] node-grunt-sass: FTBFS: dh_auto_test: error: 
/bin/sh -ex debian/tests/pkg-js/test returned exit code 3
Bug #1067268 [node-node-sass] node-vega-tooltip: FTBFS: make[1]: *** 
[debian/rules:11: override_dh_auto_build] Error 1
Bug #1067269 [node-node-sass] node-react-toastify: FTBFS: make[1]: *** 
[debian/rules:27: override_dh_auto_build] Error 1
Bug #1067340 [node-node-sass] node-rollup-plugin-sass: FTBFS: dh_auto_test: 
error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Bug #1067382 [node-node-sass] node-vega-embed: FTBFS: make: *** 
[debian/rules:8: binary] Error 25
Marked as found in versions node-node-sass/7.0.3+git20221109.ee13eb9+dfsg-2.
Marked as found in versions node-node-sass/7.0.3+git20221109.ee13eb9+dfsg-2.
Marked as found in versions node-node-sass/7.0.3+git20221109.ee13eb9+dfsg-2.
Marked as found in versions node-node-sass/7.0.3+git20221109.ee13eb9+dfsg-2.
Marked as found in versions node-node-sass/7.0.3+git20221109.ee13eb9+dfsg-2.
Marked as found in versions node-node-sass/7.0.3+git20221109.ee13eb9+dfsg-2.
> tags 1067264 + sid trixie
Bug #1067264 [node-node-sass] select2.js: FTBFS: make[1]: *** [debian/rules:7: 
override_dh_auto_build] Error 3
Bug #1067265 [node-node-sass] node-grunt-sass: FTBFS: dh_auto_test: error: 
/bin/sh -ex debian/tests/pkg-js/test returned exit code 3
Bug #1067268 [node-node-sass] node-vega-tooltip: FTBFS: make[1]: *** 
[debian/rules:11: override_dh_auto_build] Error 1
Bug #1067269 [node-node-sass] node-react-toastify: FTBFS: make[1]: *** 
[debian/rules:27: override_dh_auto_build] Error 1
Bug #1067340 [node-node-sass] node-rollup-plugin-sass: FTBFS: dh_auto_test: 
error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Bug #1067382 [node-node-sass] node-vega-embed: FTBFS: make: *** 
[debian/rules:8: binary] Error 25
Ignoring request to alter tags of bug #1067264 to the same tags previously set
Ignoring request to alter tags of bug #1067265 to the same tags previously set
Ignoring request to alter tags of bug #1067268 to the same tags previously set
Ignoring request to alter tags of bug #1067269 to the same tags previously set
Ignoring request to alter tags of bug #1067340 to the same tags previously set
Ignoring request to alter tags of bug #1067382 to the same tags previously set
> close 1067264
Bug #1067264 [node-node-sass] select2.js: FTBFS: make[1]: *** [debian/rules:7: 
override_dh_auto_build] Error 3
Bug #1067265 [node-node-sass] node-grunt-sass: FTBFS: dh_auto_test: error: 
/bin/sh -ex debian/tests/pkg-js/test returned exit code 3
Bug #1067268 [node-node-sass] node-vega-tooltip: FTBFS: make[1]: *** 
[debian/rules:11: override_dh_auto_build] Error 1
Bug #1067269 [node-node-sass] node-react-toastify: FTBFS: make[1]: *** 
[debian/rules:27: override_dh_auto_build] Error 1
Bug #1067340 [node-node-sass] node-rollup-plugin-sass: FTBFS: dh_auto_test: 
error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Bug #1067382 [node-node-sass] node-vega-embed: FTBFS: make: *** 
[debian/rules:8: binary] Error 25
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
Marked Bug as done
> found 1067254 7.0.3+git20221109.ee13eb9+dfsg-2
Bug #1067254 [node-node-sass] node-gulp-sass: FTBFS: dh_auto_test: error: 
/bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Marked as found in versions node-node-sass/7.0.3+git20221109.ee13eb9+dfsg-2.
> tags 1067254 + sid trixie
Bug #1067254 [node-node-sass] node-gulp-sass: FTBFS: dh_auto_test: error: 
/bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Ignoring request to alter tags of bug #1067254 to the same tags previously set
> close 1067254
Bug #1067254 [node-node-sass] node-gulp-sass: FTBFS: dh_auto_test: error: 
/bin/sh -ex debian/tests/pkg-js/test returned exit code 1
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1067254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067254
1067264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067264
1067265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067265
1067268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067268
1067269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067269
1067340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067340
1067382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1036596: python3-lldb-14: broken symlinks: /usr/lib/llvm-14/lib/python3/dist-packages/lldb/libLLVM-14.so.1 etc.

2024-04-15 Thread Sebastian Ramacher

On 2024-04-15 10:25:48 +0200, Andreas Beckmann wrote:
> On 14/04/2024 13.31, Sylvestre Ledru wrote:
> > Sorry for my lack of answer.
> > 
> > LLVM 14 was already deprecated when this bug has been filed. I don't
> > think we should spend much time on this issue.
> 
> Has this issue been fixed in newer releases, yet? I usually only file these
> bugs for the oldest version in sid, assuming fixes propagate to the newer
> ones.
> 
> > llvm 14 removal is #1050069
> 
> Was it really neccessary to start this transition (i.e. raising the
> corresponding "move away from 14" bugs to RC) while the 64bit time_t
> transition is ongoing?

llvm-toolchain-14 is long ongoing. Apart from the RM bug, which was
filed in August 2023, #1058822 was filed in December as serious.

Cheers
-- 
Sebastian Ramacher

Bug#1066368: marked as done (filter: FTBFS: actions.c:255:21: error: implicit declaration of function ‘wait’ [-Werror=implicit-function-declaration])

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 08:49:14 +
with message-id 
and subject line Bug#1066368: fixed in filter 2.6.3+ds1-4
has caused the Debian Bug report #1066368,
regarding filter: FTBFS: actions.c:255:21: error: implicit declaration of 
function ‘wait’ [-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.)


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

Hi,

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

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

Relevant part (hopefully):
> cc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2  -c 
> -o actions.o actions.c
> actions.c:200:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   200 | mail_message(address, fptr,resendflag)
>   | ^~~~
> actions.c: In function ‘mail_message’:
> actions.c:255:21: error: implicit declaration of function ‘wait’ 
> [-Werror=implicit-function-declaration]
>   255 | wait();
>   | ^~~~
> actions.c:292:14: error: implicit declaration of function ‘lock’; did you 
> mean ‘lockf’? [-Werror=implicit-function-declaration]
>   292 | if (!lock()) {
>   |  ^~~~
>   |  lockf
> actions.c:336:9: error: implicit declaration of function ‘unlock’; did you 
> mean ‘unlink’? [-Werror=implicit-function-declaration]
>   336 | unlock();   /* blamo or not?  Let it decide! */
>   | ^~
>   | unlink
> actions.c: In function ‘save_message’:
> actions.c:393:27: error: implicit declaration of function ‘save_to_folder’ 
> [-Werror=implicit-function-declaration]
>   393 | ret = save_to_folder(foldername,tmpfptr);
>   |   ^~
> actions.c: In function ‘mail_message’:
> actions.c:269:21: warning: ignoring return value of ‘setuid’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   269 | setuid(user_uid);
>   | ^~~~
> actions.c:270:21: warning: ignoring return value of ‘setgid’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   270 | setgid(user_gid);
>   | ^~~~
> actions.c: In function ‘execute’:
> actions.c:544:17: warning: ignoring return value of ‘setgid’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   544 | setgid(user_gid);
>   | ^~~~
> actions.c:545:17: warning: ignoring return value of ‘setuid’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   545 | setuid(user_uid);
>   | ^~~~
> actions.c:549:17: warning: ignoring return value of ‘dup’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   549 | dup(tmpfd);
>   | ^~
> cc1: some warnings being treated as errors
> make[1]: *** [: actions.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/filter_2.6.3+ds1-3_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: filter
Source-Version: 2.6.3+ds1-4
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
filter,

Bug#1065969: marked as done (ike-scan: FTBFS on arm{el,hf}: configure: error: cannot determine snprintf format string for long long int)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 08:49:48 +
with message-id 
and subject line Bug#1065969: fixed in ike-scan 1.9.5-2
has caused the Debian Bug report #1065969,
regarding ike-scan: FTBFS on arm{el,hf}: configure: error: cannot determine 
snprintf format string for long long int
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=ike-scan=armhf=1.9.5-1%2Bb2=1709990104=0

checking snprintf format for long long int... none
configure: error: cannot determine snprintf format string for long long int

...

configure:5765: checking snprintf format for long long int
configure:5803: gcc -o conftest -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -Wall -Wshadow 
-Wwrite-strings -Wextra -fstack-protector -D_FORTIFY_SOURCE=2 -Wformat 
-Wformat-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c  >&5
conftest.c: In function 'does_int64_snprintf_work':
conftest.c:58:7: error: implicit declaration of function 'strcmp' 
[-Werror=implicit-function-declaration]
   58 |   if (strcmp(buf, "8014005") != 0)
  |   ^~
conftest.c:42:1: note: include '' or provide a declaration of 'strcmp'
   41 | #include 
  +++ |+#include 
   42 | typedef long long int int64;
conftest.c: At top level:
conftest.c:62:1: warning: return type defaults to 'int' [-Wimplicit-int]
   62 | main() {
  | ^~~~
cc1: some warnings being treated as errors

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: ike-scan
Source-Version: 1.9.5-2
Done: Arnaud Rebillout 

We believe that the bug you reported is fixed in the latest version of
ike-scan, 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.
Arnaud Rebillout  (supplier of updated ike-scan 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: Mon, 15 Apr 2024 15:25:32 +0700
Source: ike-scan
Architecture: source
Version: 1.9.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Arnaud Rebillout 
Closes: 1065969
Changes:
 ike-scan (1.9.5-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Repository-Browse.
   * Fix day-of-week for changelog entry 1.7-2.
   * Update standards version to 4.6.1, no changes needed.
   * Set upstream metadata fields: Repository.
 .
   [ Arnaud Rebillout ]
   * Import a bunch of upstream patches
   * Add patch to fix acinclude.m4 with -Werror=implicit-function-declaration
 (Closes: #1065969)
   * Add smoke test
Checksums-Sha1:
 7f70c9d93f86771d1ad69b434e4ad469ac7e1bc2 1986 ike-scan_1.9.5-2.dsc
 8beb55bbd5ce5680a8e3454e55c39242d7c310b2 10300 ike-scan_1.9.5-2.debian.tar.xz
 4e40eaf45f30c4e007bc8966739100115dc62092 6482 ike-scan_1.9.5-2_source.buildinfo
Checksums-Sha256:
 809bcd1fba11a60e9acd1e5a755ff297141fbff61e3f7cccd9acb2bf4431e1d8 1986 
ike-scan_1.9.5-2.dsc
 756859fc6f5abcc2ffce782464cd3e894f953a3ec5ecd47e5031588317a13cb5 10300 
ike-scan_1.9.5-2.debian.tar.xz
 4f0d859320d33e913d79fc74f4caf4987129737ab372dcf13c46e5f1f3cd13d7 6482 
ike-scan_1.9.5-2_source.buildinfo
Files:
 e5642976261f1f4c6e8ade2f78c7e400 1986 net optional ike-scan_1.9.5-2.dsc
 d8a7ae6b6ea7ac075ebf221b8cbe52cd 10300 net optional 
ike-scan_1.9.5-2.debian.tar.xz
 a8bd9debd7246fa70840b6b838588109 6482 net optional 
ike-scan_1.9.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE0Kl7ndbut+9n4bYs5yXoeRRgAhYFAmYc5MERHGFybmF1ZHJA
a2FsaS5vcmcACgkQ5yXoeRRgAhYlgxAAiMgwQRbJI+IxTDvitTuorzW3Fq4XN1o9
ow6glzYMiGBSbF7OWCTMC/BijgjJ3/BMGzhwM5W7cPueOQF4u7P5/OwbSLFmzgYx

Bug#1066492: marked as done (tinydyndns: FTBFS: seek_set.c:7:7: error: implicit declaration of function ‘lseek’ [-Werror=implicit-function-declaration])

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 08:39:54 +
with message-id 
and subject line Bug#1066492: fixed in tinydyndns 0.4.2.debian1-3
has caused the Debian Bug report #1066492,
regarding tinydyndns: FTBFS: seek_set.c:7:7: error: implicit declaration of 
function ‘lseek’ [-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.)


-- 
1066492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tinydyndns
Version: 0.4.2.debian1-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):
> make[2]: Entering directory '/<>'
> ( cat warn-auto.sh; \
> echo 'main="$1"; shift'; \
> echo exec "`head -1 conf-ld`" \
> '-o "$main" "$main".o ${1+"$@"}' \
> ) > load
> ( cat warn-auto.sh; \
> echo exec "`head -1 conf-cc`" '-c ${1+"$@"}' \
> ) > compile
> chmod 755 load
> chmod 755 compile
> cat warn-auto.sh choose.sh \
> | sed s}HOME}"`head -1 conf-home`"}g \
> > choose
> ( cat warn-auto.sh; \
> echo CC=\'`head -1 conf-cc`\'; \
> echo LD=\'`head -1 conf-ld`\'; \
> cat find-systype.sh; \
> ) | sh > systype
> ./compile env.c
> ./compile alloc.c
> ./compile alloc_re.c
> ./compile getln.c
> chmod 755 choose
> ./compile getln2.c
> ./compile stralloc_cat.c
> ./compile stralloc_catb.c
> ./compile stralloc_cats.c
> ./compile stralloc_copy.c
> ./compile stralloc_eady.c
> ./compile stralloc_num.c
> ./compile stralloc_opyb.c
> ./compile stralloc_opys.c
> ./compile stralloc_pend.c
> ./compile buffer.c
> ./compile buffer_1.c
> ./compile buffer_2.c
> ./compile buffer_copy.c
> ./compile buffer_get.c
> ./compile buffer_put.c
> ./compile strerr_die.c
> ./compile strerr_sys.c
> ./compile buffer_read.c
> ./compile buffer_write.c
> ./compile error.c
> ./compile error_str.c
> ./compile ndelay_off.c
> ./compile ndelay_on.c
> ./compile open_read.c
> ./compile open_trunc.c
> ./compile openreadclose.c
> ./compile readclose.c
> ./compile seek_set.c
> ./compile socket_accept.c
> ./compile socket_bind.c
> seek_set.c: In function ‘seek_set’:
> seek_set.c:7:7: error: implicit declaration of function ‘lseek’ 
> [-Werror=implicit-function-declaration]
> 7 | { if (lseek(fd,(off_t) pos,SET) == -1) return -1; return 0; }
>   |   ^
> ./compile socket_conn.c
> ./compile socket_listen.c
> ./compile socket_recv.c
> ./compile socket_send.c
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile.djbdns:767: seek_set.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/tinydyndns_0.4.2.debian1-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: tinydyndns
Source-Version: 0.4.2.debian1-3
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
tinydyndns, 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.
Andreas Beckmann  (supplier of updated tinydyndns 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:

Bug#1066071: marked as done (mtdev: broken shlibs, leading to uninstallable udebs)

2024-04-15 Thread Debian Bug Tracking System

Your message dated Mon, 15 Apr 2024 08:39:15 +
with message-id 
and subject line Bug#1066071: fixed in mtdev 1.1.6-1.2
has caused the Debian Bug report #1066071,
regarding mtdev: broken shlibs, leading to uninstallable udebs
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.)


-- 
1066071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mtdev
Version: 1.1.6-1.1
Severity: serious
Tags: d-i
Justification: broken shlibs
X-Debbugs-Cc: debian-b...@lists.debian.org, Benjamin Drung 

Hi,

Your NMU broke this package's shlibs.

Before:

libmtdev 1 libmtdev1
udeb: libmtdev 1 libmtdev1-udeb

After:

libmtdev 1 libmtdev1t64

At the moment, at least the following package is broken:

The following packages have unmet dependencies:
 libinput10-udeb : Depends: libmtdev1t64 but it is not installable


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: mtdev
Source-Version: 1.1.6-1.2
Done: Cyril Brulebois 

We believe that the bug you reported is fixed in the latest version of
mtdev, 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.
Cyril Brulebois  (supplier of updated mtdev 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: Mon, 15 Apr 2024 09:51:44 +0200
Source: mtdev
Architecture: source
Version: 1.1.6-1.2
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Cyril Brulebois 
Closes: 1066071
Changes:
 mtdev (1.1.6-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix shlibs entry for the udeb: set DEB_DH_MAKESHLIBS_ARGS_libmtdev1t64
 instead of setting DEB_DH_MAKESHLIBS_ARGS_libmtdev1, to match the
 rename of the library (Closes: #1066071).
Checksums-Sha1:
 da0b2fda886d051206a07ac8bbac3abd18b0ce8c 2134 mtdev_1.1.6-1.2.dsc
 1d0b83177c056a260ead6e4cd5784efc234877b9 6412 mtdev_1.1.6-1.2.debian.tar.xz
 57809b31beaeaf9bae09ad31249b435b2dd9b34b 7372 mtdev_1.1.6-1.2_source.buildinfo
Checksums-Sha256:
 4bd994a1d771f45a3c53abe04ccea62ac9b90a03acccdc47b18b71fc181a784d 2134 
mtdev_1.1.6-1.2.dsc
 cc92d44b8824460a4c873d559c0818b0f27cdb069b8390826e3cad1d355861a4 6412 
mtdev_1.1.6-1.2.debian.tar.xz
 5c089cf7b28e59ab8a5d398aaadc281447a5a1c25544a39904c4186f82d2178e 7372 
mtdev_1.1.6-1.2_source.buildinfo
Files:
 0e80313f585b6ea3566399cb25cf4bc2 2134 libs optional mtdev_1.1.6-1.2.dsc
 5d553c856eb9a1d6c98ed90ff2b6f78d 6412 libs optional 
mtdev_1.1.6-1.2.debian.tar.xz
 9b89b6c4ff1220358c75cb2b3ba7f385 7372 libs optional 
mtdev_1.1.6-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmYc3iEQHGtpYmlAZGVi
aWFuLm9yZwAKCRD/kUrwwrNVIGTbEACUE9llJNfC4A55Hd4KVPKmqot6ng/4+drR
WMqTfFQu0sMybZQKq87EFK7nUtbFfjYpgltY4qyKQsQjdAZRvzeSmM0xzBmehpq0
jCl0gPhNMz9r7OiQBlR1Fdg0QhOnC7BVjWSQZmzXUfwn4XzinmcKkDcinhPMPUWg
dOUa0tBqJ1oTOhXf8+pSm3y/sgBaJccjpyyMBQgQL/caS4arXNzdedFYj+sEviyL
ZwMvzCe4DHgUvtYRGJNsfR+dQBJHkpbGTK+jIeCGTXronWBnTH4wENm0tD1KKCDQ
OAI2rslXI6QsfQ3OEc+fW8EgIfRsp/k/x7eDiWbN87njBOLhqi9EG11Pxe7/Q1Id
VECGtuk2ajAX5h8JQtFbEU6oVYZX5WyKMcn0sMVX4XiWOs2wSSlbKBBtlELBAzyS
82+EtwLrjvvIe8+yujjCZDECqyGdnwnWEwZD1S7UNK6HMsy6cLme77a7vWwiAW0q
OeklrlSb/i+p/9nuWor3Bva/TMxaeQc7HuSKD61a7hpFUGPLmwFPQWE/NLiS/KSJ
pBukkJyzDrnCIc/JeXtYf/f7AWp4weOYWPsBVND+dk0syBOI389Ik/F7zOML0mOY
LERvSk7DZf+chEL6FVAMMDtiL+4z8554G4HMIUvPEfgded5goB0aIVKiLeRXygcx
erhKm7mXgg==
=3GMS
-END PGP SIGNATURE-



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

Processed: reassign 1066347 to src:euslisp, affects 1066347, forcibly merging 1066307 1066347

2024-04-15 Thread Debian Bug Tracking System

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

> reassign 1066347 src:euslisp
Bug #1066347 [src:euslisp] jskeus: FTBFS: jpegmemcd.c:29:3: error: implicit 
declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-Werror=implicit-function-declaration]
Bug #1066307 [src:euslisp] euslisp: FTBFS: jpegmemcd.c:29:3: error: implicit 
declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-Werror=implicit-function-declaration]
Ignoring request to reassign bug #1066347 to the same package
Ignoring request to reassign bug #1066307 to the same package
> affects 1066347 src:jskeus
Bug #1066347 [src:euslisp] jskeus: FTBFS: jpegmemcd.c:29:3: error: implicit 
declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-Werror=implicit-function-declaration]
Bug #1066307 [src:euslisp] euslisp: FTBFS: jpegmemcd.c:29:3: error: implicit 
declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-Werror=implicit-function-declaration]
Added indication that 1066347 affects src:jskeus
Added indication that 1066307 affects src:jskeus
> forcemerge 1066307 1066347
Bug #1066307 [src:euslisp] euslisp: FTBFS: jpegmemcd.c:29:3: error: implicit 
declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-Werror=implicit-function-declaration]
Bug #1066347 [src:euslisp] jskeus: FTBFS: jpegmemcd.c:29:3: error: implicit 
declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-Werror=implicit-function-declaration]
Bug #1066347 [src:euslisp] jskeus: FTBFS: jpegmemcd.c:29:3: error: implicit 
declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-Werror=implicit-function-declaration]
Merged 1066307 1066347
> thanks
Stopping processing here.

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

Processed: reassign 1066347 to src:euslisp, affects 1066347, forcibly merging 1066307 1066347

2024-04-15 Thread Debian Bug Tracking System

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

> reassign 1066347 src:euslisp
Bug #1066347 [src:jskeus] jskeus: FTBFS: jpegmemcd.c:29:3: error: implicit 
declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-Werror=implicit-function-declaration]
Bug reassigned from package 'src:jskeus' to 'src:euslisp'.
No longer marked as found in versions jskeus/1.2.4+dfsg-3.
Ignoring request to alter fixed versions of bug #1066347 to the same values 
previously set
> affects 1066347 src:jskeus
Bug #1066347 [src:euslisp] jskeus: FTBFS: jpegmemcd.c:29:3: error: implicit 
declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-Werror=implicit-function-declaration]
Added indication that 1066347 affects src:jskeus
> forcemerge 1066307 1066347
Bug #1066307 [src:euslisp] euslisp: FTBFS: jpegmemcd.c:29:3: error: implicit 
declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-Werror=implicit-function-declaration]
Bug #1066347 [src:euslisp] jskeus: FTBFS: jpegmemcd.c:29:3: error: implicit 
declaration of function ‘jpeg_memio_dest’; did you mean ‘jpeg_mem_dest’? 
[-Werror=implicit-function-declaration]
Removed indication that 1066347 affects src:jskeus
Marked as found in versions euslisp/9.27+dfsg-7.
Merged 1066307 1066347
> thanks
Stopping processing here.

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

Processed: Bug#1065969 marked as pending in ike-scan

2024-04-15 Thread Debian Bug Tracking System

Processing control commands:

> tag -1 pending
Bug #1065969 [src:ike-scan] ike-scan: FTBFS on arm{el,hf}: configure: error: 
cannot determine snprintf format string for long long int
Added tag(s) pending.

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

Bug#1065969: marked as pending in ike-scan

2024-04-15 Thread Arnaud Rebillout

Control: tag -1 pending

Hello,

Bug #1065969 in ike-scan 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/pkg-security-team/ike-scan/-/commit/175d75e70040c11bc202b64125f684aa73913152


Add patch to fix acinclude.m4 with -Werror=implicit-function-declaration

Closes: #1065969


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065969

Bug#1036596: python3-lldb-14: broken symlinks: /usr/lib/llvm-14/lib/python3/dist-packages/lldb/libLLVM-14.so.1 etc.

2024-04-15 Thread Andreas Beckmann


On 14/04/2024 13.31, Sylvestre Ledru wrote:

Sorry for my lack of answer.

LLVM 14 was already deprecated when this bug has been filed. I don't 
think we should spend much time on this issue.


Has this issue been fixed in newer releases, yet? I usually only file 
these bugs for the oldest version in sid, assuming fixes propagate to 
the newer ones.



llvm 14 removal is #1050069


Was it really neccessary to start this transition (i.e. raising the 
corresponding "move away from 14" bugs to RC) while the 64bit time_t 
transition is ongoing?


Andreas

Bug#1066071: mtdev: broken shlibs, leading to uninstallable udebs

2024-04-15 Thread Cyril Brulebois

Hi,

Cyril Brulebois  (2024-03-12):
> Your NMU broke this package's shlibs.
> 
> Before:
> 
> libmtdev 1 libmtdev1
> udeb: libmtdev 1 libmtdev1-udeb
> 
> After:
> 
> libmtdev 1 libmtdev1t64
> 
> At the moment, at least the following package is broken:
> 
> The following packages have unmet dependencies:
>  libinput10-udeb : Depends: libmtdev1t64 but it is not installable

No response in 1+ month, the package isn't ready to migrate anyway since
it's waiting on dpkg but also regressing on 32-bit arms.

Source debdiff attached for the NMU, which I've verified to generate
appropriate shlibs, leading a rebuilt src:libinput10 to have appropriate
dependencies as far as libinput10-udeb is concerned.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
diff -Nru mtdev-1.1.6/debian/changelog mtdev-1.1.6/debian/changelog
--- mtdev-1.1.6/debian/changelog	2024-02-28 21:51:50.0 +0100
+++ mtdev-1.1.6/debian/changelog	2024-04-15 09:51:44.0 +0200
@@ -1,3 +1,12 @@
+mtdev (1.1.6-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix shlibs entry for the udeb: set DEB_DH_MAKESHLIBS_ARGS_libmtdev1t64
+instead of setting DEB_DH_MAKESHLIBS_ARGS_libmtdev1, to match the
+rename of the library (Closes: #1066071).
+
+ -- Cyril Brulebois   Mon, 15 Apr 2024 09:51:44 +0200
+
 mtdev (1.1.6-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru mtdev-1.1.6/debian/rules mtdev-1.1.6/debian/rules
--- mtdev-1.1.6/debian/rules	2020-05-24 06:38:08.0 +0200
+++ mtdev-1.1.6/debian/rules	2024-04-15 09:50:23.0 +0200
@@ -9,7 +9,7 @@
 distribution	:= $(shell lsb_release -is)
 LDFLAGS += -Wl,-z,defs -Wl,--as-needed
 
-DEB_DH_MAKESHLIBS_ARGS_libmtdev1 = --add-udeb=libmtdev1-udeb
+DEB_DH_MAKESHLIBS_ARGS_libmtdev1t64 = --add-udeb=libmtdev1-udeb
 
 DEB_INSTALL_MANPAGES_mtdev-tools = debian/mtdev-test.1
 


signature.asc
Description: PGP signature

Bug#1064762: Might be an incompatibility of vtk9 with expat/2.6.0

2024-04-15 Thread Markus Blatt


Hi.

I tried to follow this up a bit. Looking at the upstream expat bugs [1] [2] 
it might very well be that vtk9 was relying in internals of expat's xml

processing and their assumptions broke when moving to 2.6.0.

Hence this probably is an incompatibility on vtk9's side rather than a bug in
expat. At least upstream thinks that way in in [1] and closed the bug.

The stalled discussion about this in VTK9 can be found in [3].

Should we reassing this to vtk9?

Best,

Markus

[1] https://github.com/libexpat/libexpat/issues/857
[2] https://github.com/libexpat/libexpat/issues/840
[3] https://gitlab.kitware.com/vtk/vtk/-/issues/19258

Bug#1069017: rtags: FTBFS due to time64_t changes

2024-04-15 Thread Gianfranco Costamagna


Package: rtags
Version: 2.38-9
Severity: serious
Tags: patch

Hello maintainer, I fixed a FTBFS on armhf due to time64_t. The regex was causing 
"=64" to be stripped from _FILE_OFFSET_BITS, causing cmake to fail to build 
test code.

With this regex the example test code of clang fails in cmake, causing an error.
this is due to -I/usr/lib/llvm-18/include -std=c++17 -fno-exceptions 
-funwind-tables -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS 
-D__STDC_LIMIT_MACROS
becoming:
-I/usr/lib/llvm-18/include;-D_GNU_SOURCE;-D_FILE_OFFSET_BITS;-D_LARGEFILE_SOURCE;-D_FILE_OFFSET_BITS;-D__STDC_CONSTANT_MACROS;-D__STDC_FORMAT_MACROS;-D__STDC_LIMIT_MACROS

If you undefine _FILE_OFFSET_BITS and you enable _TIME_BITS=64 you get a FTBFS

/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"


  * Fix regex on find clang without stripping defines content.


Thanks for considering the patch.
diff -Nru rtags-2.38/debian/patches/fix-regex.patch 
rtags-2.38/debian/patches/fix-regex.patch
--- rtags-2.38/debian/patches/fix-regex.patch   1970-01-01 01:00:00.0 
+0100
+++ rtags-2.38/debian/patches/fix-regex.patch   2024-04-15 08:50:11.0 
+0200
@@ -0,0 +1,18 @@
+Description:
+   * Add -D_FILE_OFFSET_BITS=64 to fix FTBFS on armhf
+ (bad regex on find clang making build fail)
+Author: Gianfranco Costamagna 
+Forwarded: https://github.com/Andersbakken/rtags/pull/1439
+Last-Update: 2024-04-15
+
+--- rtags-2.38.orig/cmake/FindLibClang.cmake
 rtags-2.38/cmake/FindLibClang.cmake
+@@ -88,7 +88,7 @@ if (NOT LIBCLANG_CXXFLAGS)
+ endif ()
+ set(LIBCLANG_CXXFLAGS "-I${LIBCLANG_CXXFLAGS}")
+ endif ()
+-string(REGEX MATCHALL "-(D__?[a-zA-Z_]*|I([^\" ]+|\"[^\"]+\"))" LIBCLANG_CXXFLAGS 
"${LIBCLANG_CXXFLAGS}")
++string(REGEX MATCHALL "-(D__?[a-zA-Z_=0-9]*|I([^\" ]+|\"[^\"]+\"))" 
LIBCLANG_CXXFLAGS "${LIBCLANG_CXXFLAGS}")
+ string(REGEX REPLACE ";" " " LIBCLANG_CXXFLAGS "${LIBCLANG_CXXFLAGS}")
+ set(LIBCLANG_CXXFLAGS ${LIBCLANG_CXXFLAGS} CACHE STRING "The LLVM C++ compiler 
flags needed to compile LLVM based applications.")
+ unset(LIBCLANG_CXXFLAGS_HACK_CMAKECACHE_DOT_TEXT_BULLSHIT CACHE)
diff -Nru rtags-2.38/debian/patches/series rtags-2.38/debian/patches/series
--- rtags-2.38/debian/patches/series2023-08-29 19:36:08.0 +0200
+++ rtags-2.38/debian/patches/series2024-04-15 08:49:15.0 +0200
@@ -15,3 +15,4 @@
 0015-expand-range-of-llvm-versions.patch
 0016-always-finish-the-connection.patch
 0017-Add-when-argument-to-define-obsolete-function-alias.patch
+fix-regex.patch


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: merge duplicates

2024-04-15 Thread Debian Bug Tracking System

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

> reassign 1065046 src:ace-of-penguins
Bug #1065046 [ace-of-penguins] ace-of-penguins: FTBFS on armhf with implicit 
function declaration
Bug reassigned from package 'ace-of-penguins' to 'src:ace-of-penguins'.
No longer marked as found in versions ace-of-penguins/1.5~rc2-5.
Ignoring request to alter fixed versions of bug #1065046 to the same values 
previously set
> forcemerge 1066349 1065046
Bug #1066349 [src:ace-of-penguins] ace-of-penguins: FTBFS: 
./make-imglib.c:207:20: error: implicit declaration of function ‘isgraph’ 
[-Werror=implicit-function-declaration]
Bug #1066349 [src:ace-of-penguins] ace-of-penguins: FTBFS: 
./make-imglib.c:207:20: error: implicit declaration of function ‘isgraph’ 
[-Werror=implicit-function-declaration]
Added tag(s) patch.
Bug #1065046 [src:ace-of-penguins] ace-of-penguins: FTBFS on armhf with 
implicit function declaration
Marked as found in versions ace-of-penguins/1.5~rc2-5.
Merged 1065046 1066349
> thanks
Stopping processing here.

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

83 matches

Mail list logo