Bug#1074166: erlang-dialyzer has an undeclared file conflict on /usr/bin/typer

[Helmut Grohne]

Package: erlang-dialyzer
Version: 1:27.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + typer

erlang-dialyzer has an undeclared file conflict. This may result in an
unpack error from dpkg.

The file /usr/bin/typer is contained in the packages
 * erlang-dialyzer/1:27.0+dfsg-1 as present in experimental
 * typer/0.12.3-1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Processed: erlang-dialyzer has an undeclared file conflict on /usr/bin/typer

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + typer
Bug #1074166 [erlang-dialyzer] erlang-dialyzer has an undeclared file conflict 
on /usr/bin/typer
Added indication that 1074166 affects typer

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

Bug#1074138: marked as done (librust-ammonia-dev: impossible to install)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jun 2024 06:52:04 +0200
with message-id <171920472432.255930.12129102047492893...@auryn.jones.dk>
and subject line Re: librust-ammonia-dev: impossible to install
has caused the Debian Bug report #1074138,
regarding librust-ammonia-dev: impossible to install
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.)


-- 
1074138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-ammonia-dev
Version: 3.3.0-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package is impossible to install: Depends on unavailable package
librust-html5ever-0.26+default-dev.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZ4TmoACgkQLHwxRsGg
ASGU4w//cweSyDILVPGoOwXubaHxdx1VZJ0TF8WidEaNyYMq2CTLglVfOMAGmwM5
rIPnbiYNapA0IerGfSC3svGaPNjMa6GT9gisEGKNuRwGjKT+/rKOhviCHtdfYvxy
WScCMR0M/IggXb+6CnP1QA/vlmRqI56JXiLVstN9Af3zeenmWrC7I2otmLiY1+/a
ci0kZ6EA6/1ZKsPZSecqUs3gRVYKwgWOMKwTKQwju1uD9DCGEFck2d8s/a7tpeY6
kf58BdYwao7hevubRJENNTO4hpqpzMY2p2sHka6pu6OGF79vJu6f5xV/rBC8e4zi
P2+7N7kMprHcuDV7xuPXBBuiK+MZxqEGhbEWQkgfQlzfFn/WlgyDfgRFldQBdMcI
mJ9XljVYUPLrwXAVVI7AhQndwJZ+hNlNGLU0rUJYgZ/OSXJHT/wYxBPR+FbBYi9m
sFKojJcjKRy4FJlwCPVVaBehLbHT+ikDPJWG8HfMdusVkse1LC4tZn91ftjOMmiY
7uJDRMh4s/pfHXWK13LvvGgBM+EYzgBJFv9sRwC9NDac8usC6qioqDqO6ipFyJLy
mhMgGMg+xTJVlxIIr4AmyFfLg8QB9S9PDUP+pA3YcBgqY2rlbAlQCXhxoao9ye2l
scXgesl8ibp+jTJevGXA9NuuwKzLB1i/RQDbwYl3j5SBW04b/pg=
=UlU+
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: librust-async-fs-dev/2.1.2-2

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

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

Processed: libkscreenlocker6 has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libkscreenlocker5
Bug #1074165 [libkscreenlocker6] libkscreenlocker6 has an undeclared file 
conflict on /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
Added indication that 1074165 affects libkscreenlocker5

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

Bug#1074165: libkscreenlocker6 has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet

[Helmut Grohne]

Package: libkscreenlocker6
Version: 6.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libkscreenlocker5

libkscreenlocker6 has an undeclared file conflict. This may result in an
unpack error from dpkg.

The file /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet is
contained in the packages
 * libkscreenlocker5
   * 5.20.5-1+deb11u1 as present in bullseye
   * 5.27.11-1 as present in trixie|unstable
   * 5.27.5-2 as present in bookworm
 * libkscreenlocker6/6.1.0-1 as present in experimental

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Bug#1074107: marked as done (librust-zbus-dev: please urgently patch to accept rust-async-fs)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jun 2024 04:19:32 +
with message-id 
and subject line Bug#1074107: fixed in rust-zbus 3.14.1-8
has caused the Debian Bug report #1074107,
regarding librust-zbus-dev: please urgently patch to accept rust-async-fs
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.)


-- 
1074107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-zbus-dev
Version: 3.14.1-7
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I have bumped rust-async-fs from v1 to v2, and only afterwards realized
that I had forgotten to check for reverse dependencies.  Seems there is
only one, rust-zbus.

Please patch rust-zbus to accept newer v2 of rust-async-fs.  If that is
not possible, then please tell, and I will do an ugly rollback of
rust-async-fs to v1, by use of messy versioning scheme 2+really.1, until
migration is possible (which may involve the whole async-* and smol
stack).

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZ35JwACgkQLHwxRsGg
ASHsvQ//TJ3U2fPlnXXSnxM6+jQ+e8pQm6E7QQdWRrIIbatLNjB/4iPKOC4hXVMi
Jmg8U3I/LtXOvP01VelsYAxezKfL8xbzewrCmQcQFLC6NF/o5wUtT1TuQNkB4q1K
Zjpr/JdKMyN+TSp0p1tJNtUUlkD4OzyA9taVB+poyONmqv+GaOkM1oesk5f0ldhT
okacREtqL/K66zWaoPC6BZG/tcchx3KZfmbA6ArPwxtUxTz26c5WPubW/dSX/55n
XedQhCvpbEppYAZotziDjXK7ofWEydnRC45LeChFKfLCDm9gXzoD3z2QWbCG9HQ0
A1oYfAWaP8eN0HMJ9JqNtniBrriVDlFJuXaujwFhq5E4W4xrHGOYNaFlk9/x0RVz
zym/hXuEgVgPW177v6kLF9rWV2gUScqyxEnm88sZQ+1/g+MnxH4WX1fnsdZqpqvT
Z80sBYFIRc0nbxiLnrp9iTVi7RCQF523I1TfhBxiYt/uE5Xs9XmOusAl2fdiCzxb
5czLJzWAKVL+E0KY9+CFRq30+LDN4KOJs3FUwUjaOR0Db4quToJ/8mhFtZtyZq45
MgpzQFktG4dapx0DU2kDUyP3o5W2BLGiNZa4CGWybMbKN29vAJN0JcIUi1Xb5OPH
RDNw4R14GM42eIXABd6Hylh426XA+JOUireeK4JZHSrU08qpsPc=
=lcWD
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-zbus
Source-Version: 3.14.1-8
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-zbus 
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, 24 Jun 2024 03:55:05 +
Source: rust-zbus
Architecture: source
Version: 3.14.1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1074107
Changes:
 rust-zbus (3.14.1-8) unstable; urgency=medium
 .
   * Team upload.
   * Package zbus 3.14.1 from crates.io using debcargo 2.6.1
   * Bump async-fs dependency (Closes: #1074107)
Checksums-Sha1:
 453655695e8f206b8aa4ebd59e490ed58195d5e2 4617 rust-zbus_3.14.1-8.dsc
 a7cb109da8c1b29bf01d4f91f093327feff1fd01 9472 rust-zbus_3.14.1-8.debian.tar.xz
 5826adbee344caf69fa38eceb0fb5ef3f8800614 16402 
rust-zbus_3.14.1-8_source.buildinfo
Checksums-Sha256:
 1d5a29d8bcaef893de21544650f9e4285d3483dfa9a90bb7ad10c6f1b7935bd9 4617 
rust-zbus_3.14.1-8.dsc
 5f2c39a26187c342729a58ca1f3a8cd35dd084118c6bc414aa80597de3a2818e 9472 
rust-zbus_3.14.1-8.debian.tar.xz
 f3408a3c8234b86a07e19738e686130965d98074586cb5446958f4937e13f04e 16402 
rust-zbus_3.14.1-8_source.buildinfo
Files:
 26dcbbdfb2af3b0d9bcf527b74b9ae0b 4617 rust optional rust-zbus_3.14.1-8.dsc
 bfdd752e2caeea90dd772bd3ed50b672 9472 rust optional 
rust-zbus_3.14.1-8.debian.tar.xz
 675760ce33e02c3ad88622043defdefb 16402 rust optional 
rust-zbus_3.14.1-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmZ47kAUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvEQA//aYHL/r/h2nqsm7fEys8odtAnHIzx
mT3PVucl9tz+e859UErsBhp2nanLMdmAHWfGZZlQP5iT2MCw2igsaacpuIRR+DcA
Qb8ZkH4w6B2F5ZZb5sDMSBthTMzmq+IloyH/FdY/bw8XX5Wx9w+k7friXq03dPji
DqeGBBO0tXz8roaSxfj35DdqRcVJTsyb2wnvREmXIQtMVYvtLMJT2JkLkRp2pMNC
Qg0+KlvwKyIJ0hoPyVbjldjx93h1qjAYjoRDimk6N5wvrZKyH9i/OiFkdfsv9LFU
TTMgWa/QrYQ1GEl57lyn2ZvHUQ5CoekGZkgWn/3Cf6ZvM5npZI7Xce/W3EsAGvRK
ksWbzXPB3jJqqd300Dhqgs/DGsOg1POkD8J6FpuqFqU9Gllon/MCSNMjh+beuDaO

Bug#1051556: marked as done (soapyaudio: FTBFS with RtAudio 6)

[Debian Bug Tracking System]

Your message dated Mon, 24 Jun 2024 03:04:35 +
with message-id 
and subject line Bug#1051556: fixed in soapyaudio 0.1.1-6
has caused the Debian Bug report #1051556,
regarding soapyaudio: FTBFS with RtAudio 6
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.)


-- 
1051556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: soapyaudio
Version: 0.1.1-5
Severity: important
Tags: ftbfs

Dear Maintainer,

soapyaudio ftbfs with RtAudio 6 (currently available in experimental):

```
[ 66%] Building CXX object CMakeFiles/audioSupport.dir/Streaming.cpp.o
/usr/lib/ccache/c++ -DUSE_HAMLIB -D_REENTRANT -D__LINUX_ALSA__ 
-D__LINUX_PULSE__ -D__UNIX_JACK__ -DaudioSupport_EXPORTS -I/<> 
-I/usr/include/rtaudio -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
-std=c++11 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden   
-Wno-unused-parameter -pthread -Wall -Wextra -Wnon-virtual-dtor -MD -MT 
CMakeFiles/audioSupport.dir/Streaming.cpp.o -MF 
CMakeFiles/audioSupport.dir/Streaming.cpp.o.d -o 
CMakeFiles/audioSupport.dir/Streaming.cpp.o -c /<>/Streaming.cpp
/<>/Streaming.cpp: In member function ‘virtual int 
SoapyAudio::activateStream(SoapySDR::Stream*, int, long long int, size_t)’:
/<>/Streaming.cpp:242:14: error: ‘RtAudioError’ does not name a 
type; did you mean ‘RtAudioErrorType’?
  242 | } catch (RtAudioError& e) {
  |  ^~~~
  |  RtAudioErrorType
/<>/Streaming.cpp:243:59: error: ‘e’ was not declared in this scope
  243 | throw std::runtime_error("RtAudio init error '" + 
e.getMessage());
  |   ^
make[3]: *** [CMakeFiles/audioSupport.dir/build.make:107: 
CMakeFiles/audioSupport.dir/Streaming.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs
/<>/Settings.cpp: In member function ‘virtual void 
SoapyAudio::writeSetting(const std::string&, const std::string&)’:
/<>/Settings.cpp:497:40: warning: catching polymorphic type ‘class 
std::invalid_argument’ by value [-Wcatch-value=]
  497 | } catch (std::invalid_argument e) { }
  |^
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
```

cheers
--- End Message ---
--- Begin Message ---
Source: soapyaudio
Source-Version: 0.1.1-6
Done: tony mancill 

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated soapyaudio package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Jun 2024 19:19:02 -0700
Source: soapyaudio
Architecture: source
Version: 0.1.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: tony mancill 
Closes: 1051556
Changes:
 soapyaudio (0.1.1-6) unstable; urgency=medium
 .
   * Team upload.
   * Fix FTBFS with RtAudio 6 (Closes: #1051556)
 Thank you to IOhannes m zmoelnig  for the patch.
Checksums-Sha1:
 7331d856c3914a72ef221ef55bf16f20ef747d93 2160 soapyaudio_0.1.1-6.dsc
 9f30709a26ecee30f1ba72a2c29529c5ca084473 3776 soapyaudio_0.1.1-6.debian.tar.xz
 89a022e81c82d314940e397f1b7ad68d28468926 9554 
soapyaudio_0.1.1-6_amd64.buildinfo
Checksums-Sha256:
 709927a0f9ad35c733471d74f2f15810b3f5faba212d2b34e1c4acb535c68181 2160 
soapyaudio_0.1.1-6.dsc
 bb643587b3e09ee0587a267abfa2e654b5ac46cdda4d0d876da071814d5d1c1b 3776 
soapyaudio_0.1.1-6.debian.tar.xz
 eb804a7dde67719042fc195e2806f4ec3e9b6cb84562b8dc1479ecb884e64727 9554 
soapyaudio_0.1.1-6_amd64.buildinfo
Files:
 0a62199dbb597b6e23317f06378be621 2160 hamradio optional soapyaudio_0.1.1-6.dsc
 2857ed1b49eb5ef3f06d6cd2147db50b 3776 hamradio optional 
soapyaudio_0.1.1-6.debian.tar.xz
 016adcf08c2d3c5ffcf5cde90beb2c94 9554 hamradio optional 
soapyaudio_0.1.1-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1051556: marked as pending in soapyaudio

[Tony Mancill]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-hamradio-team/soapysdr/soapyaudio/-/commit/499e87f20942754050e68e61b0d370c53d34bdcd


Fix FTBFS with RtAudio 6 (Closes: #1051556)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1051556

Processed: Bug#1051556 marked as pending in soapyaudio

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1051556 [src:soapyaudio] soapyaudio: FTBFS with RtAudio 6
Added tag(s) pending.

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

Processed: Re: #960638: too optimistic

[Debian Bug Tracking System]

Processing control commands:

> reopen 960638
Bug #960638 {Done: Chris Hofstaedtler } [login] login no 
longer needs to be essential
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions shadow/1:4.15.1-1.
> severity 960638 serious
Bug #960638 [login] login no longer needs to be essential
Severity set to 'serious' from 'wishlist'
> notfound 960638 shadow/1:4.8.1-1
Bug #960638 [login] login no longer needs to be essential
No longer marked as found in versions shadow/1:4.8.1-1.
> notfixed 960638 shadow/1:4.15.1-1
Bug #960638 [login] login no longer needs to be essential
Ignoring request to alter fixed versions of bug #960638 to the same values 
previously set
> found 960638 shadow/1:4.15.1-1
Bug #960638 [login] login no longer needs to be essential
Marked as found in versions shadow/1:4.15.1-1.

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

Bug#1074157: marked as done (non-essential login breaks runuser)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 23:51:20 +
with message-id 
and subject line Bug#1074157: fixed in util-linux 2.40.1-9
has caused the Debian Bug report #1074157,
regarding non-essential login breaks runuser
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.)


-- 
1074157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: login
Version: 1:4.15.1-1
Severity: grave
Control: affects -1 + util-linux

Hi Chris et al,

while I recommend making stuff non-essential, I think the process was
suboptimal for login. I already had to fix debvm without having seen an
advance notice and now I figured that it actually breaks runuser. The
following command used to work before login became non-essential:

mmdebstrap unstable /dev/null --variant=apt --chrooted-customize-hook="runuser 
-u nobody echo ok"

This now gives:

runuser: failed to establish user credentials: Permission denied

I think that util-linux must gain Depends: login before login can become
non-essential (and thereby it becomes transitively essential making the
exercise a little pointless, but maybe there is a different solution).
Hence, I request reverting the change for now and redoing it once its
implications are better understood and the fallout is handled more
proactively.

Helmut
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.40.1-9
Done: Chris Hofstaedtler 

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated util-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: Mon, 24 Jun 2024 01:31:42 +0200
Source: util-linux
Architecture: source
Version: 2.40.1-9
Distribution: unstable
Urgency: medium
Maintainer: util-linux packagers 
Changed-By: Chris Hofstaedtler 
Closes: 1074157
Changes:
 util-linux (2.40.1-9) unstable; urgency=medium
 .
   * (Pre-)Depend on libpam-{modules,runtime}, so runuser/su work
 (Closes: #1074157)
   * Ack NMU 2.40.1-8.1 by Helmu Grohne. Many thanks!
Checksums-Sha1:
 6a0900573b7c18df50a45d704fe625df9da0e654 4895 util-linux_2.40.1-9.dsc
 2f28d180d160da3a5b3c93ff459caf944564d7f3 106464 
util-linux_2.40.1-9.debian.tar.xz
 dcb7393461deba51387c5fb24308343f844918f9 21402 
util-linux_2.40.1-9_arm64.buildinfo
Checksums-Sha256:
 6415df79704168a92e6d8b2429b944463a366851919dab1509c726de11137ede 4895 
util-linux_2.40.1-9.dsc
 833173afa820e86765db1b8662d56318561afd7b4286bc7fcb6002f22a73f3fd 106464 
util-linux_2.40.1-9.debian.tar.xz
 97a99b229a8c654dbad8b88d7f0512d71b522689eaf4def904bdcb751629c2a0 21402 
util-linux_2.40.1-9_arm64.buildinfo
Files:
 76bf76384ed0576642ebb97efb80a256 4895 utils required util-linux_2.40.1-9.dsc
 59b9f71c1625b4e38f97a0f5ef3d4714 106464 utils required 
util-linux_2.40.1-9.debian.tar.xz
 b0ef3ed5f2fcb2e71aa786f147da62d3 21402 utils required 
util-linux_2.40.1-9_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmZ4s1wACgkQXBPW25MF
LgMlVw//Xh7K/8eD1dXb6tEDeAYKIe5y+e1PsjRXuJK2Kxm3pk8bPiHlI6Et68HR
eHYbP6ORBrbh7gUL/X58+LtzU+oo2pyyqJ6QEF4KkMmtE7TR+WA7TtsSqfbt8VvC
vCmm9YksftvL10ExUFk8cHkhXx+mq5xVjfNw25/B91LxMae+upECpBG3bkVQ/lEI
mdcsGgk/zn6eTcNRPAOAzuKGFk2mhIVqYj9GMA746G1eWYEwD9NElLtrzqvnRO1R
wJhZtHzxos/PGCJrz9H0ZeL2q7tYxbIxpwE1XOiAowQJUVCRU51BYcm63iem8P8E
KJddylmeYBFYkPLLTyYaiRFeuEUFAAZQaacyTCP6ZOnpQaVfGIdEp471Y5xjMszl
UY/StOxsD1y0+JjVdrCliQNwKNrHxdrass21h9l73cXbhlxY3YOQv9hjn+BO1NMy
u5wVh/OOlm2TVioMkIiGpRgOff6Tnlq9grA5Uzu4HlG53QlN22o0hfdJMrh+7q7R
GpxlUgzWOg1qflYs23aGw5mGFUNFnD667RleBSkES1IujUzypvWxF2AsmcL2+acR
VX5vAYSeY3RklOOT7jHFg/ZvVG5iy0REhMuErs1uTto2rvb6MjCkcBQ+gobBNA6K
3ruLdwvVz0n+jc3XpyHcqItWu2ten5URrj23sCOi9nxqJyfiU5Q=
=5+6l
-END PGP SIGNATURE-



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

Processed: bug 1069361 is forwarded to https://gitlab.gnome.org/GNOME/libgweather/-/merge_requests/311

[Debian Bug Tracking System]

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

> forwarded 1069361 
> https://gitlab.gnome.org/GNOME/libgweather/-/merge_requests/311
Bug #1069361 [src:libgweather4] libgweather4: FTBFS on arm64: Location 
'Greenland' has invalid timezone 'America/Godthab'
Bug #1073464 [src:libgweather4] libgweather4: FTBFS: # GLib-GIO-DEBUG: Failed 
to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could 
not connect: No such file or directory
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/libgweather/-/merge_requests/311'.
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/libgweather/-/merge_requests/311'.
> thanks
Stopping processing here.

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

Bug#1069361:

[Michael Hudson-Doyle]

This is because America/Godthab was renamed to America/Nuuk in tz 2020a and
the former is now only in tzdata-legacy.

Adding tzdata-legacy to build depends fixes the build but a better fix is
probably to update libgweather4's data to follow the tz database changes.

I filed https://gitlab.gnome.org/GNOME/libgweather/-/merge_requests/311
upstream about this.

Processed: merging 1069361 1073464

[Debian Bug Tracking System]

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

> merge 1069361 1073464
Bug #1069361 [src:libgweather4] libgweather4: FTBFS on arm64: Location 
'Greenland' has invalid timezone 'America/Godthab'
Bug #1073464 [src:libgweather4] libgweather4: FTBFS: # GLib-GIO-DEBUG: Failed 
to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: Could 
not connect: No such file or directory
Marked as found in versions libgweather4/4.4.0-1.
Merged 1069361 1073464
> thanks
Stopping processing here.

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

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

[Jonas Smedegaard]

Quoting Matthias Geiger (2024-06-23 20:20:59)
> 23.06.2024 17:11:51 Jonas Smedegaard :
> 
> > Quoting Jonas Smedegaard (2024-06-18 22:58:59)
> >> It seems these packages still need to be updated as well:
> > 
> > Here is a more complete list of branch transisioning entanglements for
> > async-broadcast, async-channel, async-lock, async-process, event-listener
> > and smol.
> > 
> > DONE for unstable:
> > 
> > * blocking
> >   * v1.4.1 accepts async-channel v1+2 in unstable
> >   * v1.4.1 accepts async-lock v2+3 in unstable
> > 
> > DONE for experimental, just need re-release for unstable:
> > 
> > * async-channel
> >   * involves branch transition: v1 -> v2
> >   * v2.3.1 accepts event-listener v5 in experimental
> >     (via event-listener-strategy)
> >   * v2.3.1 succeeds build-time testsuite in experimental
> > * async-executor
> >   * v1.12.0 stops needing async-lock v2 in experimental
> >   * v1.12.0 succeeds build-time testsuite in experimental
> > * async-lock
> >   * involves branch transition: v2 -> v3
> >   * v3.4.0 accepts event-listener v5 in experimental
> >   * v3.4.0 succeeds build-time testsuite in experimental
> > * async-process
> >   * involves branch transition: v1 -> v2
> >   * v2.2.3 accepts async-channel v2 in experimental
> >   * v2.2.3 accepts async-lock v2+3 in experimental
> >   * v2.2.3 accepts event-listener v5 in experimental
> >   * v2.2.3 succeeds build-time testsuite in experimental
> > * async-std
> >   * needs to accept async-channel v2 at least in experimental
> >   * needs to accept async-lock v3 at least in experimental
> >   * needs to accept async-process v2 at least in experimental
> >   * awaits librust-async-global-executor-dev
> > * event-listener
> >   * involves branch transition: v2 -> v5
> >   * v5.3.1 succeeds build-time testsuite in experimental
> > 
> > TODO:
> > 
> > * async-broadcast
> >   * involves branch transition: v0.5 -> v0.7
> >   * v0.7.0 accepts event-listener v5 in experimental
> >   * needs custom testing: package lacks build-time testing
> > * async-fs
> >   * v2.1.2 accepts async-lock v2+3 in unstable
> >   * v2.1.2 succeeds build-time testsuite in unstable
> >   * awaits possible revert if unstable zbus cannot fit new branch
> >     
> > * async-global-executor
> >   * needs to accept async-channel v2 at least in experimental
> >     
> >     
> >   * needs to accept async-lock v3 at least in experimental
> >   * needs custom testing: package lacks build-time testing
> > * async-io
> >   * v2.3.3 accepts async-lock v3 in experimental
> >   * needs custom testing: package lacks build-time testing
> > * async-mutex
> >   * v1.4.0 accepts event-listener v5 in experimental
> >   * needs custom testing: package lacks build-time testing
> > * blocking
> >   * v1.6.1 accepts async-channel v2 in experimental
> > * criterion
> >   * needs to accept smol v2 at least in experimental
> > * criterion-0.3
> >   * needs to accept smol v2 at least in experimental
> >     (or obsoletion: https://bugs.debian.org/1074104)
> > * crosstermion
> >   * v0.14.0 accepts async-channel v2 in experimental, sloppily
> >   * needs custom testing: package lacks build-time testing
> > * event-listener-strategy
> >   * v0.5.2 accepts event-listener v5 in experimental
> >   * needs custom testing: package lacks build-time testing
> > * fs4
> >   * needs to accept smol v2 at least in experimental
> >   * needs custom testing: package lacks build-time testing
> > * gst-plugin-gtk4
> >   * needs to accept async-channel v2 at least in experimental
> >   * needs custom testing: package lacks build-time testing
> > * if-watch
> >   * needs to accept smol v2 at least in experimental
> > * isahc
> >   * needs to accept async-channel v2 at least in experimental
> >   * needs to accept event-listener v5 at least in experimental
> > * sluice
> >   * needs to accept async-channel v2 at least in experimental
> >   * needs custom testing: package lacks build-time testing
> > * smol
> >   * involves branch transition: v1 -> v2
> >   * v2.0.0 accepts async-channel v1+2 in experimental
> >   * v2.0.0 accepts async-fs v1+2 in experimental
> >   * v2.0.0 accepts async-lock v3 in experimental
> >   * awaits blocking
> > * sqlx-core
> >   * v0.7.3 accepts event-listener v5 in experimental
> >   * needs custom testing: package lacks build-time testing
> > * zbus
> >   * needs to accept async-fs in unstable
> >     
> >   * needs to accept event-listener v5 at least in experimental
> >   * needs custom testing: package lacks build-time testing
> > 
> > My next tasks is to get smol working in experimental, and then the
> > packages depending on smol as well.
> > 
> > After that, I am ready to "flip the switch" and re-release all packages
> > now in experimental for unstable.  But I would be quite frustrated if it
> > turns out that the sloppy packaging style by the 

Processed: non-essential login breaks runuser

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + util-linux
Bug #1074157 [login] non-essential login breaks runuser
Added indication that 1074157 affects util-linux

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

Bug#1074157: non-essential login breaks runuser

[Helmut Grohne]

Package: login
Version: 1:4.15.1-1
Severity: grave
Control: affects -1 + util-linux

Hi Chris et al,

while I recommend making stuff non-essential, I think the process was
suboptimal for login. I already had to fix debvm without having seen an
advance notice and now I figured that it actually breaks runuser. The
following command used to work before login became non-essential:

mmdebstrap unstable /dev/null --variant=apt --chrooted-customize-hook="runuser 
-u nobody echo ok"

This now gives:

runuser: failed to establish user credentials: Permission denied

I think that util-linux must gain Depends: login before login can become
non-essential (and thereby it becomes transitively essential making the
exercise a little pointless, but maybe there is a different solution).
Hence, I request reverting the change for now and redoing it once its
implications are better understood and the fallout is handled more
proactively.

Helmut

Bug#1074147: marked as done (simgrid FTBFS with ns3 3.42)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 20:38:57 +
with message-id 
and subject line Bug#1074147: fixed in simgrid 3.35-2
has caused the Debian Bug report #1074147,
regarding simgrid FTBFS with ns3 3.42
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.)


-- 
1074147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simgrid
Version: 3.35-1.1
Severity: serious
Tags: ftbfs patch
Forwarded: 
https://framagit.org/simgrid/simgrid/-/commit/d94c8f645e5e2d9dca54ed65403a165408e95ef8

https://buildd.debian.org/status/logs.php?pkg=simgrid=3.35-1.1%2Bb2

...
In file included from /usr/include/ns3/core-module.h:88,
 from 
/<>/src/kernel/resource/models/network_ns3.cpp:20:
/usr/include/ns3/timer-impl.h: In function ‘ns3::internal::TimerImpl* 
ns3::internal::MakeTimerImpl(U (*)(Ts ...))’:
/usr/include/ns3/timer-impl.h:105:77: error: template argument 1 is invalid
  105 | struct FnTimerImpl : public TimerImplX&...>
  | 
^
/usr/include/ns3/timer-impl.h:112:38: error: ‘remove_cvref_t’ in namespace 
‘std’ does not name a template type
  112 | void SetArguments(const std::remove_cvref_t&... args) 
override
  |  ^~
/usr/include/ns3/timer-impl.h:112:33: note: ‘std::remove_cvref_t’ is only 
available from C++20 onwards
...
--- End Message ---
--- Begin Message ---
Source: simgrid
Source-Version: 3.35-2
Done: Martin Quinson 

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

Debian distribution maintenance software
pp.
Martin Quinson  (supplier of updated simgrid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Jun 2024 22:10:40 +0200
Source: simgrid
Architecture: source
Version: 3.35-2
Distribution: unstable
Urgency: medium
Maintainer: Martin Quinson 
Changed-By: Martin Quinson 
Closes: 1074147
Changes:
 simgrid (3.35-2) unstable; urgency=medium
 .
   * Acknowledge the t64 NMU.
   * d/p/ns3.42_needs_c++20: new patch picked upstream to cope with
 ns3.42 insisting on having C++20 (Closes: #1074147).
Checksums-Sha1:
 63bf4fc96c2ec4b3f9c84ee9243e611784add112 2218 simgrid_3.35-2.dsc
 771ef4de1097ffd038857f7942288ab23863b519 16052 simgrid_3.35-2.debian.tar.xz
 6b9822c2d8cdd571a8b45decd631ef95dbdc2aac 10086 simgrid_3.35-2_amd64.buildinfo
Checksums-Sha256:
 65f8eca48a33f5aa4afad55de36bb522a129827156899ac47310e6d2bfb88000 2218 
simgrid_3.35-2.dsc
 fc5cbd3e4b2a20392919da248aecd3eeb07dfeca8567453e56c9b1d9bda7dcf0 16052 
simgrid_3.35-2.debian.tar.xz
 e063e83b593521896e69c5c5e35cfc7cf4eb7b3677b3032fd3bc3a967c7ee263 10086 
simgrid_3.35-2_amd64.buildinfo
Files:
 e710050291276009fa04f4f8d240ffbd 2218 science optional simgrid_3.35-2.dsc
 d770762a28475b717f90ee80e72c1b95 16052 science optional 
simgrid_3.35-2.debian.tar.xz
 558877847b4808e75b23ebd271963345 10086 science optional 
simgrid_3.35-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEET76cTupS7xPVQWYSmL2XJE9zvqcFAmZ4gtQUHG1xdWluc29u
QGRlYmlhbi5vcmcACgkQmL2XJE9zvqfLsA/+LY4S3iocVbaVh9TduvwDe494tnhT
EFPM8hB8aXgPf2BxmaUsTwvqHgGYyfuNtLgpqBZfX2TiIkSz9w0yISxTzhmRtO7s
EWbmxcEnCb7gFRqT6i/g3tOFo0KH5F+odM7VxU5DXB874J5wz5wzDxRhVjhC5ORi
NWEcKNN4BEFKRNyZr4vcI1buNgck7kvroqLhcYUGMaesgQUk90BvZXtp//qOPUcV
VsgIQk7ITbzOKkVrleheaDMd1CLtX/wdOW3eHRNIgzjWNeYr5o+OzEBi9XvRI9/i
VQNsQCA5hhLnhLgpJF2q/sDuL1311D2/XfzuBwBQ9mp+UkYf1/v7A9CxnzL5tnbs
GjCOhZxah1zZ5dcXpIxFEm/FC3mc+XDDbJLH37ejT/KW9ErYZl4oq7PBcfvGh5zG
bMxzVwEXFD9Uzad4a9cPeF0cuCNMSer4SSaaAYNkLV/uI7lMHpFKn01eb0LfGcIg
WZWWev2GdQzyARFCHbx7V16nSGIejPlg8Opp7emQlGWmlxcVa+ZYvGIeHdhjeUCD
nDLqvp2Wuvvlte0Wo+W9gsYb2TdLz6Dbp37oZTEoo7D9zEC0CY+5qkQAh7tbR9w+
4q6UBJzbu59ZGx3AA+mcuqympsginRrElHfBrYGHfqBJ1FdAqNEPotavWIL+kHnH
VIKZS40Uk8zunM0=
=Qm42
-END PGP SIGNATURE-



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

Processed: Re: Bug#1068349: nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-nbconvert 6.5.3-4
Bug #1068349 {Done: "Rebecca N. Palmer" } 
[python3-nbconvert,python3-lxml] nbsphinx/nbconvert broken by lxml 5.2: 
lxml.html.clean
Bug reassigned from package 'python3-nbconvert,python3-lxml' to 
'python3-nbconvert'.
No longer marked as found in versions nbconvert/6.5.3-4 and lxml/5.2.1-1.
No longer marked as fixed in versions nbconvert/6.5.3-5.
Bug #1068349 {Done: "Rebecca N. Palmer" } 
[python3-nbconvert] nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean
Marked as found in versions nbconvert/6.5.3-4.
> fixed -1 6.5.3-5
Bug #1068349 {Done: "Rebecca N. Palmer" } 
[python3-nbconvert] nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean
Marked as fixed in versions nbconvert/6.5.3-5.
> affects -1 python3-lxml
Bug #1068349 {Done: "Rebecca N. Palmer" } 
[python3-nbconvert] nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean
Added indication that 1068349 affects python3-lxml

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

Bug#1068349: nbsphinx/nbconvert broken by lxml 5.2: lxml.html.clean

[Paul Gevers]

Control: reassign -1 python3-nbconvert 6.5.3-4
Control: fixed -1 6.5.3-5
Control: affects -1 python3-lxml

On Thu, 30 May 2024 22:36:05 +0200 Paul Gevers  wrote:
Are you saying that if lxml migrates to testing, everything is fine? 
Than the easiest thing to do is to assign this bug to the package that 
fixed it.


As there was no reply, I'm going to assume this is the correct 
interpretation to enable lxml to migrate.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:ktextaddons: fails to migrate to testing for too long: FTBFS

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.5.4-2
Bug #1074155 [src:ktextaddons] src:ktextaddons: fails to migrate to testing for 
too long: FTBFS
The source 'ktextaddons' and version '1.5.4-2' do not appear to match any 
binary packages
Marked as fixed in versions ktextaddons/1.5.4-2.
Bug #1074155 [src:ktextaddons] src:ktextaddons: fails to migrate to testing for 
too long: FTBFS
Marked Bug as done
> block -1 by 1073394
Bug #1074155 {Done: Paul Gevers } [src:ktextaddons] 
src:ktextaddons: fails to migrate to testing for too long: FTBFS
1074155 was not blocked by any bugs.
1074155 was not blocking any bugs.
Added blocking bug(s) of 1074155: 1073394

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

Bug#1074155: src:ktextaddons: fails to migrate to testing for too long: FTBFS

[Paul Gevers]

Source: ktextaddons
Version: 1.5.2-2.1
Severity: serious
Control: close -1 1.5.4-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1073394

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:ktextaddons has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable fails 
to build from source as reported in bug 1073394.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=ktextaddons



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:maxima: fails to migrate to testing for too long: unresolved RC issue

[Debian Bug Tracking System]

Processing control commands:

> close -1 5.47.0-2
Bug #1074154 [src:maxima] src:maxima: fails to migrate to testing for too long: 
unresolved RC issue
Marked as fixed in versions maxima/5.47.0-2.
Bug #1074154 [src:maxima] src:maxima: fails to migrate to testing for too long: 
unresolved RC issue
Marked Bug as done
> block -1 by 1066086
Bug #1074154 {Done: Paul Gevers } [src:maxima] src:maxima: 
fails to migrate to testing for too long: unresolved RC issue
1074154 was not blocked by any bugs.
1074154 was not blocking any bugs.
Added blocking bug(s) of 1074154: 1066086

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

Bug#1074154: src:maxima: fails to migrate to testing for too long: unresolved RC issue

[Paul Gevers]

Source: maxima
Version: 5.46.0-11
Severity: serious
Control: close -1 5.47.0-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1066086

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:maxima has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable has an 
unresolved RC bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=maxima



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:chromium: fails to migrate to testing for too long: stuck behind RC issue in libxml

[Debian Bug Tracking System]

Processing control commands:

> close -1 126.0.6478.114-1
Bug #1074153 [src:chromium] src:chromium: fails to migrate to testing for too 
long: stuck behind RC issue in libxml
Marked as fixed in versions chromium/126.0.6478.114-1.
Bug #1074153 [src:chromium] src:chromium: fails to migrate to testing for too 
long: stuck behind RC issue in libxml
Marked Bug as done
> block -1 by 1073508
Bug #1074153 {Done: Paul Gevers } [src:chromium] 
src:chromium: fails to migrate to testing for too long: stuck behind RC issue 
in libxml
1074153 was not blocked by any bugs.
1074153 was not blocking any bugs.
Added blocking bug(s) of 1074153: 1073508

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

Bug#1074153: src:chromium: fails to migrate to testing for too long: stuck behind RC issue in libxml

[Paul Gevers]

Source: chromium
Version: 125.0.6422.60-1
Severity: serious
Control: close -1 126.0.6478.114-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1073508

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:chromium has been trying to migrate for 32 
days [2]. Hence, I am filing this bug. The version in unstable has been 
build against an RC buggy version libxml, but can't migrate without 
libxml migrating. I see at least one CVE mentioned in the changelog 
since the version in stable. Maybe the tpu route is appropriate? If so, 
please reach out to the release team.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=chromium



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:quickml: fails to migrate to testing for too long: FTBFS

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.8-2
Bug #1074152 [src:quickml] src:quickml: fails to migrate to testing for too 
long: FTBFS
The source 'quickml' and version '0.8-2' do not appear to match any binary 
packages
Marked as fixed in versions quickml/0.8-2.
Bug #1074152 [src:quickml] src:quickml: fails to migrate to testing for too 
long: FTBFS
Marked Bug as done
> block -1 by 1073471
Bug #1074152 {Done: Paul Gevers } [src:quickml] src:quickml: 
fails to migrate to testing for too long: FTBFS
1074152 was not blocked by any bugs.
1074152 was not blocking any bugs.
Added blocking bug(s) of 1074152: 1073471

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

Bug#1074152: src:quickml: fails to migrate to testing for too long: FTBFS

[Paul Gevers]

Source: quickml
Version: 0.8-1
Severity: serious
Control: close -1 0.8-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1073471

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:quickml has been trying to migrate for 32 
days [2]. Hence, I am filing this bug. The version in unstable failed to 
build from source as reported in bug 1073471.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=quickml



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:gpscorrelate: fails to migrate to testing for too long: fails its new autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.1-1
Bug #1074151 [src:gpscorrelate] src:gpscorrelate: fails to migrate to testing 
for too long: fails its new autopkgtest
Marked as fixed in versions gpscorrelate/2.1-1.
Bug #1074151 [src:gpscorrelate] src:gpscorrelate: fails to migrate to testing 
for too long: fails its new autopkgtest
Marked Bug as done
> block -1 by 1071656
Bug #1074151 {Done: Paul Gevers } [src:gpscorrelate] 
src:gpscorrelate: fails to migrate to testing for too long: fails its new 
autopkgtest
1074151 was not blocked by any bugs.
1074151 was not blocking any bugs.
Added blocking bug(s) of 1074151: 1071656

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

Bug#1074151: src:gpscorrelate: fails to migrate to testing for too long: fails its new autopkgtest

[Paul Gevers]

Source: gpscorrelate
Version: 2.0-4
Severity: serious
Control: close -1 2.1-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1071656

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:gpscorrelate has been trying to migrate 
for 36 days [2]. Hence, I am filing this bug. The package fails its own 
autopkgtest as reported in bug 1071656.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=gpscorrelate



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1074147: simgrid FTBFS with ns3 3.42

[Adrian Bunk]

Source: simgrid
Version: 3.35-1.1
Severity: serious
Tags: ftbfs patch
Forwarded: 
https://framagit.org/simgrid/simgrid/-/commit/d94c8f645e5e2d9dca54ed65403a165408e95ef8

https://buildd.debian.org/status/logs.php?pkg=simgrid=3.35-1.1%2Bb2

...
In file included from /usr/include/ns3/core-module.h:88,
 from 
/<>/src/kernel/resource/models/network_ns3.cpp:20:
/usr/include/ns3/timer-impl.h: In function ‘ns3::internal::TimerImpl* 
ns3::internal::MakeTimerImpl(U (*)(Ts ...))’:
/usr/include/ns3/timer-impl.h:105:77: error: template argument 1 is invalid
  105 | struct FnTimerImpl : public TimerImplX&...>
  | 
^
/usr/include/ns3/timer-impl.h:112:38: error: ‘remove_cvref_t’ in namespace 
‘std’ does not name a template type
  112 | void SetArguments(const std::remove_cvref_t&... args) 
override
  |  ^~
/usr/include/ns3/timer-impl.h:112:33: note: ‘std::remove_cvref_t’ is only 
available from C++20 onwards
...

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

[Matthias Geiger]

23.06.2024 17:11:51 Jonas Smedegaard :


Quoting Jonas Smedegaard (2024-06-18 22:58:59)

It seems these packages still need to be updated as well:


Here is a more complete list of branch transisioning entanglements for
async-broadcast, async-channel, async-lock, async-process, event-listener
and smol.

DONE for unstable:

* blocking
  * v1.4.1 accepts async-channel v1+2 in unstable
  * v1.4.1 accepts async-lock v2+3 in unstable

DONE for experimental, just need re-release for unstable:

* async-channel
  * involves branch transition: v1 -> v2
  * v2.3.1 accepts event-listener v5 in experimental
    (via event-listener-strategy)
  * v2.3.1 succeeds build-time testsuite in experimental
* async-executor
  * v1.12.0 stops needing async-lock v2 in experimental
  * v1.12.0 succeeds build-time testsuite in experimental
* async-lock
  * involves branch transition: v2 -> v3
  * v3.4.0 accepts event-listener v5 in experimental
  * v3.4.0 succeeds build-time testsuite in experimental
* async-process
  * involves branch transition: v1 -> v2
  * v2.2.3 accepts async-channel v2 in experimental
  * v2.2.3 accepts async-lock v2+3 in experimental
  * v2.2.3 accepts event-listener v5 in experimental
  * v2.2.3 succeeds build-time testsuite in experimental
* async-std
  * needs to accept async-channel v2 at least in experimental
  * needs to accept async-lock v3 at least in experimental
  * needs to accept async-process v2 at least in experimental
  * awaits librust-async-global-executor-dev
* event-listener
  * involves branch transition: v2 -> v5
  * v5.3.1 succeeds build-time testsuite in experimental

TODO:

* async-broadcast
  * involves branch transition: v0.5 -> v0.7
  * v0.7.0 accepts event-listener v5 in experimental
  * needs custom testing: package lacks build-time testing
* async-fs
  * v2.1.2 accepts async-lock v2+3 in unstable
  * v2.1.2 succeeds build-time testsuite in unstable
  * awaits possible revert if unstable zbus cannot fit new branch
    
* async-global-executor
  * needs to accept async-channel v2 at least in experimental
    
    
  * needs to accept async-lock v3 at least in experimental
  * needs custom testing: package lacks build-time testing
* async-io
  * v2.3.3 accepts async-lock v3 in experimental
  * needs custom testing: package lacks build-time testing
* async-mutex
  * v1.4.0 accepts event-listener v5 in experimental
  * needs custom testing: package lacks build-time testing
* blocking
  * v1.6.1 accepts async-channel v2 in experimental
* criterion
  * needs to accept smol v2 at least in experimental
* criterion-0.3
  * needs to accept smol v2 at least in experimental
    (or obsoletion: https://bugs.debian.org/1074104)
* crosstermion
  * v0.14.0 accepts async-channel v2 in experimental, sloppily
  * needs custom testing: package lacks build-time testing
* event-listener-strategy
  * v0.5.2 accepts event-listener v5 in experimental
  * needs custom testing: package lacks build-time testing
* fs4
  * needs to accept smol v2 at least in experimental
  * needs custom testing: package lacks build-time testing
* gst-plugin-gtk4
  * needs to accept async-channel v2 at least in experimental
  * needs custom testing: package lacks build-time testing
* if-watch
  * needs to accept smol v2 at least in experimental
* isahc
  * needs to accept async-channel v2 at least in experimental
  * needs to accept event-listener v5 at least in experimental
* sluice
  * needs to accept async-channel v2 at least in experimental
  * needs custom testing: package lacks build-time testing
* smol
  * involves branch transition: v1 -> v2
  * v2.0.0 accepts async-channel v1+2 in experimental
  * v2.0.0 accepts async-fs v1+2 in experimental
  * v2.0.0 accepts async-lock v3 in experimental
  * awaits blocking
* sqlx-core
  * v0.7.3 accepts event-listener v5 in experimental
  * needs custom testing: package lacks build-time testing
* zbus
  * needs to accept async-fs in unstable
    
  * needs to accept event-listener v5 at least in experimental
  * needs custom testing: package lacks build-time testing

My next tasks is to get smol working in experimental, and then the
packages depending on smol as well.

After that, I am ready to "flip the switch" and re-release all packages
now in experimental for unstable.  But I would be quite frustrated if it
turns out that the sloppy packaging style by the Rust team has caused
some breakage goes undetected, so I will wait for your guys from the Rust
team to state explicitly here in this bugreport, that you believe that
all the packages listed above as "needs custom testing" are good to go.


Jonas,

thanks for the thorough analysis. For the packages I staged in 
experimental all tests passed (build + autopkgtest), so certainly no 
sloppy work ! I will upload a patched zbus, gst-plugin-gtk4 and the few 
remaining crates which haven't been patched 

Bug#1022311: marked as done (python-stdnum: FTBFS: AssertionError: Failed doctest test for test_no_fodselsnummer.doctest)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 18:17:31 +
with message-id 
and subject line Bug#1022311: fixed in python-stdnum 1.16-1+deb11u1
has caused the Debian Bug report #1022311,
regarding python-stdnum: FTBFS: AssertionError: Failed doctest test for 
test_no_fodselsnummer.doctest
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.)


-- 
1022311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-stdnum
Version: 1.17-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args='TZ=Europe/Amsterdam 
> {interpreter} setup.py nosetests'
> I: pybuild base:240: TZ=Europe/Amsterdam python3.10 setup.py nosetests
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: 
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use 
> license_files instead.
>   warnings.warn(msg, warning_class)
> running nosetests
> running egg_info
> writing python_stdnum.egg-info/PKG-INFO
> writing dependency_links to python_stdnum.egg-info/dependency_links.txt
> writing requirements to python_stdnum.egg-info/requires.txt
> writing top-level names to python_stdnum.egg-info/top_level.txt
> reading manifest file 'python_stdnum.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'COPYING'
> writing manifest file 'python_stdnum.egg-info/SOURCES.txt'
> nose.plugins.cover: ERROR: Coverage not available: unable to import coverage 
> module
> .SSS.S.SS...SS...F
> ==
> FAIL: Doctest: test_no_fodselsnummer.doctest
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3.10/doctest.py", line 2221, in runTest
> raise self.failureException(self.format_failure(new.getvalue()))
> AssertionError: Failed doctest test for test_no_fodselsnummer.doctest
>   File "/<>/tests/test_no_fodselsnummer.doctest", line 0
> 
> --
> File "/<>/tests/test_no_fodselsnummer.doctest", line 94, in 
> test_no_fodselsnummer.doctest
> Failed example:
> fodselsnummer.validate('19102270846')
> Expected:
> Traceback (most recent call last):
> ...
> InvalidComponent: The birth date information is valid, but this person 
> has not been born yet.
> Got:
> '19102270846'
> 
> 
> --
> Ran 342 tests in 1.408s
> 
> FAILED (SKIP=8, failures=1)
> E: pybuild pybuild:379: test: plugin custom failed with: exit code=1: 
> TZ=Europe/Amsterdam python3.10 setup.py nosetests
> dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.10 
> --system=custom "--test-args=TZ=Europe/Amsterdam {interpreter} setup.py 
> nosetests" returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/python-stdnum_1.17-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 marking 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: python-stdnum
Source-Version: 1.16-1+deb11u1
Done: Santiago Vila 

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

A summary of the changes between this version and 

Bug#1074138: librust-ammonia-dev: impossible to install

[Jonas Smedegaard]

Control: reassign -1 librust-smol-dev/1.3.0-6

Quoting Blair Noctis (2024-06-23 19:17:26)
> > Unsatisfied dependencies:
> >  librust-smol-dev : Depends: librust-async-fs-1+default-dev but it is not
> > installable Error: Unable to correct problems, you have held broken 
> > packages.

Yeah, thanks.  I realized it myself now (but slower than you, it seems).

I'll clean up my own mess :-/

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1074141: marked as done (razercfg_0.43-1_mips64el-buildd.changes REJECTED)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 17:35:25 +
with message-id 
and subject line Bug#1074141: fixed in razercfg 0.43-2
has caused the Debian Bug report #1074141,
regarding razercfg_0.43-1_mips64el-buildd.changes REJECTED
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.)


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

On 2024-06-23 16:05, Debian FTP Masters wrote:
> 
> 
> razercfg_0.43-1_mips64el.deb: has 7 file(s) with a timestamp too far in the 
> past:
>   etc/init.d/razerd (Thu Jan  1 00:00:00 1970)  etc/razer.conf (Thu Jan  1 
> 00:00:00 1970)  usr/bin/razer-gamewrapper (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/pyrazer/__init__.py (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/pyrazer/main.py (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/pyrazer/ui.py (Thu Jan  1 00:00:00 1970)  
> usr/lib/tmpfiles.d/razerd.conf (Thu Jan  1 00:00:00 1970)
> 
> 
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
--- End Message ---
--- Begin Message ---
Source: razercfg
Source-Version: 0.43-2
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated razercfg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Jun 2024 18:12:36 +0100
Source: razercfg
Architecture: source
Version: 0.43-2
Distribution: unstable
Urgency: medium
Maintainer: Luca Boccassi 
Changed-By: Luca Boccassi 
Closes: 1074141
Changes:
 razercfg (0.43-2) unstable; urgency=medium
 .
   * Reset mtime to changelog date for files at epoch (Closes: #1074141)
Checksums-Sha1:
 710cea67d4541973a7d27f278f4e8f4125bb184e 2273 razercfg_0.43-2.dsc
 c5032d0efbdc254b4456b90b14161423721e2ce2 11132 razercfg_0.43-2.debian.tar.xz
 b437b3fa45ebda1fdfb45667213afb2b379f2211 10082 razercfg_0.43-2_source.buildinfo
Checksums-Sha256:
 0c52776061e67622d0efa5193b99ada620930542256f72b3634ec43d6bec1990 2273 
razercfg_0.43-2.dsc
 25ddc8ba20352f81e7007fd3995b9d2ff37a4c2940c18514ded1f916f6723701 11132 
razercfg_0.43-2.debian.tar.xz
 7810073e4e86d5a7a879971928367286579c805481b85a08e754208ff432fc76 10082 
razercfg_0.43-2_source.buildinfo
Files:
 4095eaae1bd0bf8945b92ac6cfd6d737 2273 misc optional razercfg_0.43-2.dsc
 b1601ca03ea4a1ac1e69a31c0b8c4966 11132 misc optional 
razercfg_0.43-2.debian.tar.xz
 d3e5fcb175c21e89728eb4b33cbfa121 10082 misc optional 
razercfg_0.43-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmZ4WPYRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB4RVg//TSLgGbQfAgcx75O3fgpCBaTa9E8qspgv
EZPO+ZX6QEguu3iz479phjx91FOz1sL8Nol510EY/AHcVAnBKli2g57A5ogbcinf
eVoOeE0SaXKxAUW1b1HgyaC63u940Kq2Ozol14FT0e2zKf+s8BNIbG6YttNIisBE
uYacoC+e/10GDRTu+NCUkqrHsufG7pVQEPxOw7oLmQv+W+hVyXmfZNGr+gclsdeC
eOgqPq3KdNQw/wc27puTgEAnraduAiYH9XOpK+wyCMz7ucGF+vLWFD9tkdzQxOnZ
2FnvsNkAZgHz5E/B2bT4OkyNfNVUKFeM2MQgSkZ4xjP7wErZ7OIbD+fM/9ul4Ng8
rVU0xyVJ2CUJqh9w+zjGSqUeSZke48vh4UI2foEoMetNF2G+PV5ECgnz0Yy2cXJh
22fOqhQld4JNh+Ttwkrx1etT9lbOgEXCGHpWR/1HB4+OPJrxMwzbvvts5p9NyGmK
px2hH0YrM/IoOOKqO/y7tD5kD126Vm364am++DHhQDEFEPEW+3NEP9rJpcfNdbdU
JmDhXRJRFlqhwieCySdK2sefRrQMxPMaKiN/SjuzIVi36noufgFGIybZ890KTXAt
KypswEmmQCKn0opj4aU9QmzBE9zwHCezRkxd07feR2DPdqYvoTVH4AdINZYobGTn
lklTExjZD3U=
=ITLH
-END PGP SIGNATURE-



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

Bug#1074145: numexpr FTBFS with more than 8 cores

[Adrian Bunk]

Source: numexpr
Version: 2.10.1-1
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/pydata/numexpr/issues/490

https://buildd.debian.org/status/fetch.php?pkg=numexpr=loong64=2.10.1-1=1719162095=0
https://buildd.debian.org/status/fetch.php?pkg=numexpr=powerpc=2.10.1-1=1719162022=0

...
==
ERROR: test_max_threads_unset 
(numexpr.tests.test_numexpr.test_threading_config.test_max_threads_unset)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.11_numexpr/build/numexpr/tests/test_numexpr.py",
 line 1134, in test_max_threads_unset
subprocess.check_call([sys.executable, '-c', script])
  File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3.11', '-c', "import 
os\nif 'NUMEXPR_MAX_THREADS' in os.environ: 
os.environ.pop('NUMEXPR_MAX_THREADS')\nif 'OMP_NUM_THREADS' in os.environ: 
os.environ.pop('OMP_NUM_THREADS')\nimport numexpr\nassert(numexpr.nthreads <= 
8)\nexit(0)"]' returned non-zero exit status 1.

--
Ran 5538 tests in 7.326s

FAILED (errors=1)
...

Bug#1074141: razercfg_0.43-1_mips64el-buildd.changes REJECTED

[Aurelien Jarno]

Source: razercfg
Version: 0.43-1
Severity: serious

On 2024-06-23 16:05, Debian FTP Masters wrote:
> 
> 
> razercfg_0.43-1_mips64el.deb: has 7 file(s) with a timestamp too far in the 
> past:
>   etc/init.d/razerd (Thu Jan  1 00:00:00 1970)  etc/razer.conf (Thu Jan  1 
> 00:00:00 1970)  usr/bin/razer-gamewrapper (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/pyrazer/__init__.py (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/pyrazer/main.py (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/pyrazer/ui.py (Thu Jan  1 00:00:00 1970)  
> usr/lib/tmpfiles.d/razerd.conf (Thu Jan  1 00:00:00 1970)
> 
> 
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 

Bug#1073359: marked as done (python-jira: FTBFS: ModuleNotFoundError: No module named 'typing_extensions')

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 16:36:38 +
with message-id 
and subject line Bug#1073359: fixed in python-jira 3.5.2-3
has caused the Debian Bug report #1073359,
regarding python-jira: FTBFS: ModuleNotFoundError: No module named 
'typing_extensions'
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.)


-- 
1073359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-jira
Version: 3.5.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 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_auto_build
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
> module
> I: pybuild base:311: python3.12 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_jira  
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/tests
> copying tests/__init__.py -> build/lib/tests
> copying tests/tests.py -> build/lib/tests
> copying tests/test_client.py -> build/lib/tests
> copying tests/test_shell.py -> build/lib/tests
> copying tests/test_resilientsession.py -> build/lib/tests
> copying tests/conftest.py -> build/lib/tests
> copying tests/test_exceptions.py -> build/lib/tests
> copying tests/test_qsh.py -> build/lib/tests
> creating build/lib/jira
> copying jira/resources.py -> build/lib/jira
> copying jira/__init__.py -> build/lib/jira
> copying jira/exceptions.py -> build/lib/jira
> copying jira/jirashell.py -> build/lib/jira
> copying jira/resilientsession.py -> build/lib/jira
> copying jira/client.py -> build/lib/jira
> copying jira/config.py -> build/lib/jira
> creating build/lib/tests/resources
> copying tests/resources/test_issue_link_type.py -> build/lib/tests/resources
> copying tests/resources/test_generic_resource.py -> build/lib/tests/resources
> copying tests/resources/__init__.py -> build/lib/tests/resources
> copying tests/resources/test_group.py -> build/lib/tests/resources
> copying tests/resources/test_comment.py -> build/lib/tests/resources
> copying tests/resources/test_watchers.py -> build/lib/tests/resources
> copying tests/resources/test_role.py -> build/lib/tests/resources
> copying tests/resources/test_sprint.py -> build/lib/tests/resources
> copying tests/resources/test_attachment.py -> build/lib/tests/resources
> copying tests/resources/test_customer.py -> build/lib/tests/resources
> copying tests/resources/test_epic.py -> build/lib/tests/resources
> copying tests/resources/test_issue_type_scheme_associations.py -> 
> build/lib/tests/resources
> copying tests/resources/test_security_level.py -> build/lib/tests/resources
> copying tests/resources/test_filter.py -> build/lib/tests/resources
> copying tests/resources/test_component.py -> build/lib/tests/resources
> copying tests/resources/test_remote_link.py -> build/lib/tests/resources
> copying tests/resources/test_user.py -> build/lib/tests/resources
> copying tests/resources/test_project.py -> build/lib/tests/resources
> copying tests/resources/test_vote.py -> build/lib/tests/resources
> copying tests/resources/test_priority.py -> build/lib/tests/resources
> copying tests/resources/test_request_type.py -> build/lib/tests/resources
> copying tests/resources/test_dashboard.py -> build/lib/tests/resources
> copying tests/resources/test_version.py -> build/lib/tests/resources
> copying tests/resources/test_status_category.py -> build/lib/tests/resources
> copying tests/resources/test_issue_property.py -> build/lib/tests/resources
> copying tests/resources/test_issue.py -> build/lib/tests/resources
> copying tests/resources/test_custom_field_option.py -> 
> build/lib/tests/resources
> copying tests/resources/test_status.py -> build/lib/tests/resources
> copying tests/resources/test_board.py -> build/lib/tests/resources
> copying tests/resources/test_worklog.py -> build/lib/tests/resources
> copying tests/resources/test_resolution.py -> build/lib/tests/resources
> copying tests/resources/test_project_statuses.py -> build/lib/tests/resources
> copying tests/resources/test_issue_link.py -> build/lib/tests/resources
> copying tests/resources/test_service_desk.py -> build/lib/tests/resources
> creating build/lib/jira/utils
> copying jira/utils/__init__.py -> build/lib/jira/utils
> running egg_info
> creating jira.egg-info
> writing 

Bug#1074138: librust-ammonia-dev: impossible to install

[Jonas Smedegaard]

Package: librust-ammonia-dev
Version: 3.3.0-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package is impossible to install: Depends on unavailable package
librust-html5ever-0.26+default-dev.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZ4TmoACgkQLHwxRsGg
ASGU4w//cweSyDILVPGoOwXubaHxdx1VZJ0TF8WidEaNyYMq2CTLglVfOMAGmwM5
rIPnbiYNapA0IerGfSC3svGaPNjMa6GT9gisEGKNuRwGjKT+/rKOhviCHtdfYvxy
WScCMR0M/IggXb+6CnP1QA/vlmRqI56JXiLVstN9Af3zeenmWrC7I2otmLiY1+/a
ci0kZ6EA6/1ZKsPZSecqUs3gRVYKwgWOMKwTKQwju1uD9DCGEFck2d8s/a7tpeY6
kf58BdYwao7hevubRJENNTO4hpqpzMY2p2sHka6pu6OGF79vJu6f5xV/rBC8e4zi
P2+7N7kMprHcuDV7xuPXBBuiK+MZxqEGhbEWQkgfQlzfFn/WlgyDfgRFldQBdMcI
mJ9XljVYUPLrwXAVVI7AhQndwJZ+hNlNGLU0rUJYgZ/OSXJHT/wYxBPR+FbBYi9m
sFKojJcjKRy4FJlwCPVVaBehLbHT+ikDPJWG8HfMdusVkse1LC4tZn91ftjOMmiY
7uJDRMh4s/pfHXWK13LvvGgBM+EYzgBJFv9sRwC9NDac8usC6qioqDqO6ipFyJLy
mhMgGMg+xTJVlxIIr4AmyFfLg8QB9S9PDUP+pA3YcBgqY2rlbAlQCXhxoao9ye2l
scXgesl8ibp+jTJevGXA9NuuwKzLB1i/RQDbwYl3j5SBW04b/pg=
=UlU+
-END PGP SIGNATURE-

Bug#1073359: marked as pending in python-jira

[Jochen Sprickerhof]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-jira/-/commit/d287ce35aa6768d8ec324281bb2411d6d74faf5e


Add missing build dependency

Closes: #1073359


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073359

Processed: Bug#1073359 marked as pending in python-jira

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073359 [src:python-jira] python-jira: FTBFS: ModuleNotFoundError: No 
module named 'typing_extensions'
Added tag(s) pending.

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

Processed: org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1074136 [src:org-mode] org-link-expand-abbrev: Do not evaluate arbitrary 
unsafe Elisp code
Bug 1074136 cloned as bug 1074137
> reassign -2 src:emacs 1:29.3+1-3
Bug #1074137 [src:org-mode] org-link-expand-abbrev: Do not evaluate arbitrary 
unsafe Elisp code
Bug reassigned from package 'src:org-mode' to 'src:emacs'.
No longer marked as found in versions org-mode/9.6.28+dfsg-1.
Ignoring request to alter fixed versions of bug #1074137 to the same values 
previously set
Bug #1074137 [src:emacs] org-link-expand-abbrev: Do not evaluate arbitrary 
unsafe Elisp code
Marked as found in versions emacs/1:29.3+1-3.

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

Bug#1074136: org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code

[Salvatore Bonaccorso]

Source: org-mode
Version: 9.6.28+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: clone -1 -2
Control: reassign -2 src:emacs 1:29.3+1-3

Hi

There is a new vulnerability in Emacs Org mode. Details:

https://www.openwall.com/lists/oss-security/2024/06/23/1

Upstream fix (in org-mode);

https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f4cc61636947b5c2f0afc67174dd369fe3277aa8

Regards,
Salvatore

Bug#1073038: marked as done (po4a: Fails due to undefined subroutine Locale::Po4a::Pod::dgettext)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 15:37:43 +
with message-id 
and subject line Bug#1073038: fixed in po4a 0.73-1
has caused the Debian Bug report #1073038,
regarding po4a: Fails due to undefined subroutine Locale::Po4a::Pod::dgettext
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.)


-- 
1073038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: po4a
Version: 0.70
Severity: serious

Hi!

When building dpkg, it now fails with something like this:

  ,---
  Making check in man
  make[1]: Entering directory '/dpkg/man'
  /usr/bin/po4a --previous --srcdir . --destdir . --no-backups --porefs file 
--msgmerge-opt=--add-location=file --package-name dpkg-man --package-version 
1.22.6-80-gec07 --copyright-holder "Dpkg Developers" --msgid-bugs-address 
debian-d...@lists.debian.org  ./po/po4a.cfg
  Undefined subroutine ::Po4a::Pod::dgettext called at 
/usr/share/perl5/Locale/Po4a/Pod.pm line 94, <$fh> line 21.
  make[1]: *** [Makefile:902: man.stamp] Error 255
  make[1]: Leaving directory '/dpkg/man'
  `---

It seems the module is missing some import.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: po4a
Source-Version: 0.73-1
Done: Dr. Tobias Quathamer 

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated po4a 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, 23 Jun 2024 17:05:19 +0200
Source: po4a
Architecture: source
Version: 0.73-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Quinson 
Changed-By: Dr. Tobias Quathamer 
Closes: 1072643 1073038
Changes:
 po4a (0.73-1) unstable; urgency=medium
 .
   * New upstream version 0.73
 - Fix undefined subroutine Locale::Po4a::Pod::dgettext.
   Closes: #1073038
   * Add d/NEWS with an explanation about the stricter encoding rules
 since v0.70. Closes: #1072643
Checksums-Sha1:
 c0c19a47a2d7376461d2ad24bf218571e7d59c3f 2160 po4a_0.73-1.dsc
 e181a907915b19ae047883c95078c01c299a0834 4170054 po4a_0.73.orig.tar.gz
 41f5cb0f2d5d784faccbdef9fb9118d1fb5af1cd 14196 po4a_0.73-1.debian.tar.xz
 228e78cda21aa9a39af8d883f73d0e26148c3a43 7771 po4a_0.73-1_amd64.buildinfo
Checksums-Sha256:
 fb0518718fe26f3cbae17acd304ff58804e302c95276d478d44e0fb66181c8b9 2160 
po4a_0.73-1.dsc
 ad5edc38bf004807843622fddbf67bd5ac604fc16e14c2bfefa7b07718ad21f3 4170054 
po4a_0.73.orig.tar.gz
 20e4e78a87571b8cb1d5fde9fe9c6468e619b596ec7be4b3fc349516e20cf458 14196 
po4a_0.73-1.debian.tar.xz
 6c513db30d7800baeae95e6ac7bb5dc78dc2473f31ceaec5316528ae4dc89d78 7771 
po4a_0.73-1_amd64.buildinfo
Files:
 5db586d5505f2d05b2e4d0c95bd57ab0 2160 text optional po4a_0.73-1.dsc
 4c152abb9f445aefea78aaca654287b0 4170054 text optional po4a_0.73.orig.tar.gz
 ac86e73f4bbae83fdd6ca515142a7af8 14196 text optional po4a_0.73-1.debian.tar.xz
 ca5c22fb826627cb0a97143ff6cf4a1a 7771 text optional po4a_0.73-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAmZ4O4AACgkQEwLx8Dbr
6xl8Hg//airAnrbh9IrpxntOXPDlPYHmg8ZvVKD0VWTNEmqVi10RY7s1m8HALLWg
Nv4pxOALgt4wjNuxVpcsW+dgYlrZedGjeUEIDsDjVWTvDUfNWSa3KAQ0b9TMw16n
FDTgYtOprZgzkNUdfgXfUcL11U8cqAmOlt5LNa7uhRUElC22BhGfBzPcANu2Mf2j
cT96Edh7vDHB9I7UrKCDpjTFI+du5og7Iyfi6GH+6NIQZ623mEOh+E8P+sXPJ5gS
9ZbmnQFpSr2j6lXoS2p8VuSeCxWHBTTEwJkYg2cwh9W1ZJhMzROBQj8C6vMBIB0k
kOLsRwe4KPW9KmsNmWedSfLLu68nQsvtDB8JhJTExIaJ5nHGQm2xuW7T4R5q9e5q
FPvtta5rXRogbB6LG9fN3mL3oy/yh7+r+yaeQxVumMJ69cV4WLM9jZTpIrEAggv6
N4aAnLFQ9NVx6oZRDRMyQmFA9ihNSckG2LgDRa1LxJV1FywCEWmTNr+hGWSffwpi
XrhaXXdfNwT5DqQNHEIKotWND0zDsGPs+DkLMxLZ2QTHwXd41NXHB9GjvBwVAXv2
O78hujM76LgY3w+ND/7HnvU1gzKCpPwoGDPgwFztSYOCRlla8wcov9671YIFV065
Y69lzvCjbeehz04RImYIOTYfDQJ70jnIytkyZb7MtegGV7neBzo=
=Ck2w
-END PGP SIGNATURE-



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

Bug#1073264: marked as done (scapy: hardcoded dependencies on libpcap0.8)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 15:20:22 +
with message-id 
and subject line Bug#1073264: fixed in scapy 2.5.0+git20240324.2b58b51+dfsg-2
has caused the Debian Bug report #1073264,
regarding scapy: hardcoded dependencies on libpcap0.8
to be marked as done.

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

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


-- 
1073264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scapy
Version: 2.5.0+git20240324.2b58b51+dfsg-1
Severity: serious
Tags: patch

Hi Maintainer

Scapy has hardcoded dependencies on libpcap0.8, but since the time_t
transition, this library is now named libpcap0.8t64.

This can be seen in the failing autopkgtests of scapy on armel [1] and
armhf [2].

The patches below should be all that is required.

Regards
Graham


[1] https://ci.debian.net/packages/s/scapy/testing/armel/
[2] https://ci.debian.net/packages/s/scapy/testing/armhf/


--- a/debian/control
+++ b/debian/control
@@ -21,7 +22,7 @@
 Depends: netbase, ${misc:Depends}, ${python3:Depends}
 Breaks: python-scapy (<< 2.4.3-3~)
 Replaces: python-scapy (<< 2.4.3-3~)
-Recommends: ipython3, libpcap0.8, python3-cryptography
+Recommends: ipython3, libpcap0.8t64, python3-cryptography
 Suggests: graphviz,
   python-scapy-doc,
   python3-matplotlib,

--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,5 +1,5 @@
 Tests: run-upstream-tests
-Depends: libpcap0.8,
+Depends: libpcap0.8t64,
  netbase,
  python3-cryptography,
  python3-ipython,
--- End Message ---
--- Begin Message ---
Source: scapy
Source-Version: 2.5.0+git20240324.2b58b51+dfsg-2
Done: Carlos Henrique Lima Melara 

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

Debian distribution maintenance software
pp.
Carlos Henrique Lima Melara  (supplier of updated 
scapy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Jun 2024 11:30:12 -0300
Source: scapy
Architecture: source
Version: 2.5.0+git20240324.2b58b51+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Carlos Henrique Lima Melara 
Closes: 1073264
Changes:
 scapy (2.5.0+git20240324.2b58b51+dfsg-2) unstable; urgency=medium
 .
   * d/control:
   - Depends on libpcap0.8t64 so it works on armhf and armel.
 Thanks to Graham Inggs. (Closes: #1073264)
   - bump Standards-Version to 4.7.0 - no changes needed.
   * debian/gbp.conf: add upstream-branch field.
   * debian/tests/control: Depends on @recommends@ instead of hard-coding
 recommended packages.
Checksums-Sha1:
 1ad828977548b199f6ebf3f2690da1fb4f004596 2358 
scapy_2.5.0+git20240324.2b58b51+dfsg-2.dsc
 2367bc929b92c199b3211f111c942100eb97df11 12388 
scapy_2.5.0+git20240324.2b58b51+dfsg-2.debian.tar.xz
 460270917059ab4c5db350fce9b3f768fcdfc597 6892 
scapy_2.5.0+git20240324.2b58b51+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 cb9a7ed555f59651d328d41391eac3a7d3058c395e23e6ac4f5d932b6f1ee134 2358 
scapy_2.5.0+git20240324.2b58b51+dfsg-2.dsc
 aafb8937a9b8ea055c7068ae54204b2965b87190177c678d851221f7c020d7ab 12388 
scapy_2.5.0+git20240324.2b58b51+dfsg-2.debian.tar.xz
 395df7aee3290dfccb6d429f2fa3d0cc2b786240ee79261a9d0ddcd9381c5d4f 6892 
scapy_2.5.0+git20240324.2b58b51+dfsg-2_amd64.buildinfo
Files:
 b0ce938ad84a989eb69ddc225d8c9001 2358 python optional 
scapy_2.5.0+git20240324.2b58b51+dfsg-2.dsc
 97db3b34f986eb85c5ffa2ef39e25354 12388 python optional 
scapy_2.5.0+git20240324.2b58b51+dfsg-2.debian.tar.xz
 dc791e0d8df0626f6d6debb127bf51a3 6892 python optional 
scapy_2.5.0+git20240324.2b58b51+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJNBAEBCgA3FiEECgzx8d8+AINglLHJt4M9ggJ8mQsFAmZ4N14ZHGNoYXJsZXNt
ZWxhcmFAcmlzZXVwLm5ldAAKCRC3gz2CAnyZCzF0D/4p1/MWofkdx/rkkMA/N9MU
NXtQiZG0L2HUeMKUf7KnEN9TW6FFPWfx9GZm6+PLI50nM39Mx/edAex/6/TjUvRK
sUP3fxsuAuv263UwG0eW7jeKYqwbEZ/MOaNqKb+RdO9+LEwNvDqUwBKaXhI4nAr9
6OlKW6XZot6tZlg3rfZ84g8J9D/N6d9D5kn/6pTnnhHQ/6bTBrLSdfggLPem1NHq
aPYv/RqUxT2UWdW1luVNGmitSgOHm1kI3vtBvwfd5cFGJi5V0q5KveRbgHwY0kIH

Bug#1069621: rust-event-listener: no-default-features autopkgtest fails

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2024-06-18 22:58:59)
> It seems these packages still need to be updated as well:

Here is a more complete list of branch transisioning entanglements for
async-broadcast, async-channel, async-lock, async-process, event-listener
and smol.

DONE for unstable:

* blocking
  * v1.4.1 accepts async-channel v1+2 in unstable
  * v1.4.1 accepts async-lock v2+3 in unstable

DONE for experimental, just need re-release for unstable:

* async-channel
  * involves branch transition: v1 -> v2
  * v2.3.1 accepts event-listener v5 in experimental
(via event-listener-strategy)
  * v2.3.1 succeeds build-time testsuite in experimental
* async-executor
  * v1.12.0 stops needing async-lock v2 in experimental
  * v1.12.0 succeeds build-time testsuite in experimental
* async-lock
  * involves branch transition: v2 -> v3
  * v3.4.0 accepts event-listener v5 in experimental
  * v3.4.0 succeeds build-time testsuite in experimental
* async-process
  * involves branch transition: v1 -> v2
  * v2.2.3 accepts async-channel v2 in experimental
  * v2.2.3 accepts async-lock v2+3 in experimental
  * v2.2.3 accepts event-listener v5 in experimental
  * v2.2.3 succeeds build-time testsuite in experimental
* async-std
  * needs to accept async-channel v2 at least in experimental
  * needs to accept async-lock v3 at least in experimental
  * needs to accept async-process v2 at least in experimental
  * awaits librust-async-global-executor-dev
* event-listener
  * involves branch transition: v2 -> v5
  * v5.3.1 succeeds build-time testsuite in experimental

TODO:

* async-broadcast
  * involves branch transition: v0.5 -> v0.7
  * v0.7.0 accepts event-listener v5 in experimental
  * needs custom testing: package lacks build-time testing
* async-fs
  * v2.1.2 accepts async-lock v2+3 in unstable
  * v2.1.2 succeeds build-time testsuite in unstable
  * awaits possible revert if unstable zbus cannot fit new branch

* async-global-executor
  * needs to accept async-channel v2 at least in experimental


  * needs to accept async-lock v3 at least in experimental
  * needs custom testing: package lacks build-time testing
* async-io
  * v2.3.3 accepts async-lock v3 in experimental
  * needs custom testing: package lacks build-time testing
* async-mutex
  * v1.4.0 accepts event-listener v5 in experimental
  * needs custom testing: package lacks build-time testing
* blocking
  * v1.6.1 accepts async-channel v2 in experimental
* criterion
  * needs to accept smol v2 at least in experimental
* criterion-0.3
  * needs to accept smol v2 at least in experimental
(or obsoletion: https://bugs.debian.org/1074104)
* crosstermion
  * v0.14.0 accepts async-channel v2 in experimental, sloppily
  * needs custom testing: package lacks build-time testing
* event-listener-strategy
  * v0.5.2 accepts event-listener v5 in experimental
  * needs custom testing: package lacks build-time testing
* fs4
  * needs to accept smol v2 at least in experimental
  * needs custom testing: package lacks build-time testing
* gst-plugin-gtk4
  * needs to accept async-channel v2 at least in experimental
  * needs custom testing: package lacks build-time testing
* if-watch
  * needs to accept smol v2 at least in experimental
* isahc
  * needs to accept async-channel v2 at least in experimental
  * needs to accept event-listener v5 at least in experimental
* sluice
  * needs to accept async-channel v2 at least in experimental
  * needs custom testing: package lacks build-time testing
* smol
  * involves branch transition: v1 -> v2
  * v2.0.0 accepts async-channel v1+2 in experimental
  * v2.0.0 accepts async-fs v1+2 in experimental
  * v2.0.0 accepts async-lock v3 in experimental
  * awaits blocking
* sqlx-core
  * v0.7.3 accepts event-listener v5 in experimental
  * needs custom testing: package lacks build-time testing
* zbus
  * needs to accept async-fs in unstable

  * needs to accept event-listener v5 at least in experimental
  * needs custom testing: package lacks build-time testing

My next tasks is to get smol working in experimental, and then the
packages depending on smol as well.

After that, I am ready to "flip the switch" and re-release all packages
now in experimental for unstable.  But I would be quite frustrated if it
turns out that the sloppy packaging style by the Rust team has caused
some breakage goes undetected, so I will wait for your guys from the Rust
team to state explicitly here in this bugreport, that you believe that
all the packages listed above as "needs custom testing" are good to go.

Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1073922: marked as done (systemd-{container,cryptsetup,repart}: ineffective Replaces due to /usr-move (DEP17))

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 15:05:31 +
with message-id 
and subject line Bug#1073922: fixed in systemd 256.1-2
has caused the Debian Bug report #1073922,
regarding systemd-{container,cryptsetup,repart}: ineffective Replaces due to 
/usr-move (DEP17)
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.)


-- 
1073922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-container,systemd-cryptsetup,cryptsetup-repart
Version: 256.1-1
Severity: serious
Control: affects -1 + systemd
User: helm...@debian.org
Usertags: dep17p1

Hi,

Version 256.1-1 was restructured splitting a number of pieces from the
main systemd package into other packages. As far as I can see, the same
changes were already present in experimental and I need to investigate
why dumat did not flag them there.

Let me not go into details of this problem just yet and just install
this bug as a temporary migration blocker. I shall have an update within
three working days, ideally with a patch. Thanks for your patience.

The dumat report is not very human-readable, but available at
https://subdivi.de/~helmut/dumat.yaml.

Helmut
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 256.1-2
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated systemd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Jun 2024 13:33:33 +0100
Source: systemd
Architecture: source
Version: 256.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Luca Boccassi 
Closes: 1073922
Changes:
 systemd (256.1-2) unstable; urgency=medium
 .
   * Bump breaks/replaces to conflicts for DEP17. Breaks/replaces are not
 enough when moving files between packages and between locations as per
 DEP17, so bump to Conflicts. (Closes: #1073922)
   * autopkgtest: add dependency on libcryptsetup-dev in unit-tests suite
Checksums-Sha1:
 da9fd4da78dcc14b2de28563bed3e486a78de2d6 8094 systemd_256.1-2.dsc
 afa156ac11c3d400e475357775b1308869394671 170600 systemd_256.1-2.debian.tar.xz
 6c10bd7517e5447a1265f22e9f8eb2aded3fb3da 13114 systemd_256.1-2_source.buildinfo
Checksums-Sha256:
 3d26da59b10c86055a6d5f00e86eec8801ff3a339644f1a7d340791e2f142110 8094 
systemd_256.1-2.dsc
 8c24fe98b93bb26b5fdf2a25054afa511069e01d5297bad4f5c5f30d2dd377df 170600 
systemd_256.1-2.debian.tar.xz
 7596d9dafb8f8d527c9944f6ca20b2c79ebc12ba3ed190d70e50dd68312f232a 13114 
systemd_256.1-2_source.buildinfo
Files:
 603353205d2ff68d218d0eb1557311bd 8094 admin optional systemd_256.1-2.dsc
 972445990f03c389c1f81324dfa232ce 170600 admin optional 
systemd_256.1-2.debian.tar.xz
 56ec99db8fb5ac61d825c1b940793326 13114 admin optional 
systemd_256.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmZ4NMMRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB7KGg//VRYdatkBIiWIduipmOTKov9QFcht7E3l
Io5FxhkOtpvdVC0XgR9hgqzJS25o7IcjalGEwLoA0H3vOUKJXOAgM74HFGsouMvp
W7YMeX0myjpsT6UMAZPdYFV/o3B0Gs9CqOBVcZFT5LiNBANMwYF9VrQ/vg6fBC02
Y/DVKFSExqTpr87VS5OGKUI67W3RcH9brc4bhxAY+4EkvhLpkqZC73j3wGBL+eTs
1RAeeNbK1zvXLNQV+oiDHxXfuKI+1GwWUNfZpicMby0vy/RLk3ar00RJ/mtX4UHe
045P3tEFuKi1lPGQ15rYZDX7Lhz/0O/J3tQCUJWs6NMGCLrW1swUQB74IsiGvZGI
XSwkxtr01xfdDBA4l/+aaHOsJhqnnXpnTbgttd1bR6nocECmhkYZtq2tcdZFDo51
0lZoHZRwxaRFRAv8wkRe7Y4hvaPbyT8BgDqdaYOyoRS80yWZCpQvFbkS3+7lDl2T
LlrXCB+G8sEZ8z95vLZRVUUFde7faA/OJLugZUyT8xVbff/lFmM7D28cXW2g5myY
93rx5NiP0kvWSFjB5qVYI3cv7KnrXPEHhNp3rcdhXvQ+pu2bqwatIuKrocj/ppJp
338oshvtoZly3i9qYMCfXDqsdBSXv2oVGwtRu44lAVWCdv9Y69o2Vw4uFggdJHVz
bGd3iFsIeAI=
=3vjY
-END PGP SIGNATURE-



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

Processed: Bug#1073264 marked as pending in scapy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073264 [src:scapy] scapy: hardcoded dependencies on libpcap0.8
Added tag(s) pending.

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

Bug#1073264: marked as pending in scapy

[Carlos Henrique Lima Melara]

Control: tag -1 pending

Hello,

Bug #1073264 in scapy 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/scapy/-/commit/2b30d73ceb22e4c345f14fb64428f0eb43dfba6b


d/control: Depends on libpcap0.8t64 so it works on armhf and armel

Closes: #1073264
Thanks: Graham Inggs


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073264

Bug#1073922: marked as pending in systemd

[Luca Boccassi]

Control: tag -1 pending

Hello,

Bug #1073922 in systemd 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/systemd-team/systemd/-/commit/e220ce22f11e344910ef82c5a07b1c033ec66a6d


Bump breaks/replaces to conflicts for DEP17

Breaks/replaces are not enough when moving files between packages
and between locations as per DEP17, so bump to Conflicts.

Closes: #1073922


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073922

Processed: Bug#1073922 marked as pending in systemd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073922 [systemd-container,systemd-cryptsetup,systemd-repart] 
systemd-{container,cryptsetup,repart}: ineffective Replaces due to /usr-move 
(DEP17)
Ignoring request to alter tags of bug #1073922 to the same tags previously set

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

Bug#1022311: python-stdnum: FTBFS: AssertionError: Failed doctest test for test_no_fodselsnummer.doctest

[Santiago Vila]

El 23/6/24 a las 14:33, Arthur de Jong escribió:

On Thu, 2024-05-23 at 13:36 +0200, Santiago Vila wrote:

Arthur: Would be ok for you if I fix this in bullseye via team
upload?


Please do, thanks.

I only have limited time available at the moment and have quite a big
backlog of issues to pick up so any help is really welcome.


Ok, I've just made the upload, pushed the commits, and filed the report
against release.debian.org.

Hopefully in time for the next bullseye point release which closes this
weekend, but even if not, it will be probably in the next one anyway,
for posterity.

Thanks a lot.

Bug#1074130: gamescope has a fixed dependency on libwlroots11, only libwlroots12 available in Sid

[HardPenguin]

Package: gamescope
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: hardpengui...@gmail.com

Hi there, installing gamescope package on Sid amd64 is currently impossible.

The package has a fixed dependency on libwlroots11 while Sid only offers 
libwlroots12 (libwlroots12t64 at the moment to be precise).

Dear maintainer, please change the dependency to libwlroots12, rebuild and 
test. Thank you!


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

Kernel: Linux 6.8.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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 gamescope depends on:
ii  libc6 2.38-13
ii  libcap2   1:2.66-5
ii  libdisplay-info1  0.1.1-2+b1
ii  libdrm2   2.4.121-2
ii  libgcc-s1 14.1.0-2
ii  libliftoff0   0.4.1-1+b1
pn  libopenvr-api1
ii  libpipewire-0.3-0t64 [libpipewire-0.3-0]  1.0.7-1
ii  libsdl2-2.0-0 2.30.4+dfsg-1
ii  libstdc++614.1.0-2
ii  libvulkan11.3.283.0-1
ii  libwayland-client01.22.0-2.1+b1
ii  libwayland-server01.22.0-2.1+b1
pn  libwlroots11  
ii  libx11-6  2:1.8.7-1+b1
ii  libx11-xcb1   2:1.8.7-1+b1
ii  libxcb1   1.17.0-2
ii  libxcomposite11:0.4.5-1+b1
ii  libxdamage1   1:1.1.6-1+b1
ii  libxext6  2:1.3.4-1+b1
ii  libxfixes31:6.0.0-2+b1
ii  libxkbcommon0 1.6.0-1+b1
ii  libxmu6   2:1.1.3-3+b2
ii  libxrender1   1:0.9.10-1.1+b1
ii  libxres1  2:1.2.1-1+b1
ii  libxtst6  2:1.2.3-1.1+b1
ii  libxxf86vm1   1:1.1.4-1+b2
ii  xwayland  2:24.1.0-1

gamescope recommends no packages.

Versions of packages gamescope suggests:
ii  libcap2-bin  1:2.66-5

Bug#1022311: python-stdnum: FTBFS: AssertionError: Failed doctest test for test_no_fodselsnummer.doctest

[Arthur de Jong]

On Thu, 2024-05-23 at 13:36 +0200, Santiago Vila wrote:
> Arthur: Would be ok for you if I fix this in bullseye via team
> upload?

Please do, thanks.

I only have limited time available at the moment and have quite a big
backlog of issues to pick up so any help is really welcome.

Thanks,

-- 
-- arthur - adej...@debian.org - https://people.debian.org/~adejong --



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

Bug#1073922: systemd-{container,cryptsetup,repart}: ineffective Replaces due to /usr-move (DEP17)

[Luca Boccassi]

Control: tags -1 -patch
Control: tags -1 pending

On Fri, 21 Jun 2024 12:30:25 +0200 Helmut Grohne 
wrote:
> Control: reassign -1 systemd-container,systemd-cryptsetup,systemd-
repart
> Control: found -1 systemd/256.1-1
> Control: tags -1 + patch
> 
> On Thu, Jun 20, 2024 at 10:58:23AM +0200, Helmut Grohne wrote:
> > Package: systemd-container,systemd-cryptsetup,cryptsetup-repart
> 
> Fixed bad package cryptsetup-repart.
> 
> > Let me not go into details of this problem just yet and just
install
> > this bug as a temporary migration blocker. I shall have an update
within
> > three working days, ideally with a patch. Thanks for your patience.
> 
> The recurring theme is that systemd moved all of its files from / to
> /usr (expected via DEP17) and now moves components from the main
systemd
> package into systemd-container, systemd-cryptsetup and systemd-
repart.
> In all of these cases, affected files may be lost in upgrades from
> either bookworm or bookworm-backports to unstable and eventually
trixie.
> Users upgrading from trixie to sid, will likely not experience loss
> unless they skip systemd versions.
> 
> There are multiple mitigation techniques available. Upgrading
> Breaks+Replaces to Conflicts provides a relatively strong protection
as
> long as one uses an apt-based package management tool. However, the
CTTE
> advised that packages relevant to booting a system should also be
safe
> when installing packages directly with dpkg and in that scenario,
> Conflicts are insufficient, because dpkg allows a conflicting package
to
> be unpacked before the conflicted package is removed to facilitate a
> smooth handover. This is only exercised by apt when the relevant
> packages employ a mutual conflict, which is not the case here. As
such,
> I also add temporary diversions that exist from preinst to postinst
to
> protect the relevant files from loss.

Thank you for the bug report, analysis and patch.

Of the three affected packages, -cryptsetup and -repart are brand new,
were never and will never be in bookworm, not even in backports, so
they are actually unaffected by the potential issue that affects the
Conflicts workaround.
-container does ship in bookworm, but the affected files, the sd-
sysupdate units, did not exist at all in bookworm, as the sub-feature
was only enabled later, and they only shipped in backports, not in
bookworm proper. Moreover, the feature itself is experimental, wasn't
really in a good shape in the backports version, and even in the newer
it cannot actually be used with any Debian infrastructure: we just do
not build and publish any of the image formats it supports. The only
reason it was enabled, was to allow local experiments. It is most
definitely not "boot critical" in any sense of the term. Finally, if it
_is_ actually used, then it would be in an image-based system, that by
definition does not perform package upgrades at all, but exclusively
installs read-only images using A/B schemes or similar, so any system
actually making use of these units would not be affected by such
upgrade issues in the first place, as it would be read-only. Any system
affected by this hypothetical cycle-induce file loss would experience
no issue, as the units would not be in use, by definition, and would
just come back at the next point release update.

Given the likelihood of any impact is minimal, and the magnitude of any
impact is nil, and given that the fix requires a large and expensive to
maintain patch, my conclusion is that the costs are not worth the
benefits, and I am ok with the minimal and localized risk that comes
with just relying on the much simpler Conflicts-based solution, and
will hence opt to use that instead.

Thanks again for the input and the discussion.

-- 
Kind regards,
Luca Boccassi


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

Processed: Re: systemd-{container,cryptsetup,repart}: ineffective Replaces due to /usr-move (DEP17)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -patch
Bug #1073922 [systemd-container,systemd-cryptsetup,systemd-repart] 
systemd-{container,cryptsetup,repart}: ineffective Replaces due to /usr-move 
(DEP17)
Removed tag(s) patch.
> tags -1 pending
Bug #1073922 [systemd-container,systemd-cryptsetup,systemd-repart] 
systemd-{container,cryptsetup,repart}: ineffective Replaces due to /usr-move 
(DEP17)
Added tag(s) pending.

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

Bug#1071860: not fixed in 7.0-005-2 (was: Bug#1071860 closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#1071860: fixed in fis-gtm 7.0-005-

[Andreas Metzler]

Control: tags -1 patch
On 2024-06-23 Andreas Tille  wrote:
> Control: tags -1 help

> Hi Andreas,

> strange, it has build for me.

Very strange, perhaps you did not build against the libgcrypt package in
experimental.

> Am Sun, Jun 23, 2024 at 08:03:30AM +0200 schrieb Andreas Metzler:
> > Control: reopen 1071860
> > ...
> > CMake Error at CMakeLists.txt:529 (message):
> >   FATAL: libgcrypt-config not found (LIBGCRYPT_CONFIG_SCRIPT-NOTFOUND)
> > [...]

> I admit I currently have no time to track this down.  It might make
> sense to upgrade to latest upstream which might have been adapted to
> work without libgcrypt-config.   Tagging the bug help since I have no
> capacity to work on this.

Fair enough.

The respective part of the CMake setup is unchanged in 7.1-003.
Attached patch works for me.

Upstream's build system is rather strange. - It requires libgcrypt itself
to be in the standard search but allows the headers to be hidden away:

8X
# Iterate over the list of GPG related libraries
foreach(gpglib gpg-error gpgme gcrypt config)
  # For each library, we need a new CMake variable, hence GPGLIB_${gpglib}
  find_library(GPGLIB_${gpglib} NAME ${gpglib} PATHS ${CMAKE_LIBRARY_PATH})
  # Append the found library to the list
  set(GPG_LIBRARIES ${GPG_LIBRARIES} ${GPGLIB_${gpglib}})
endforeach()
[...]
# Locate libgcrypt's header files (assumption: all others headers are found in 
the same location)
find_program(LIBGCRYPT_CONFIG_SCRIPT NAMES libgcrypt-config)
if (LIBGCRYPT_CONFIG_SCRIPT MATCHES ".+-NOTFOUND")
message(FATAL_ERROR "FATAL: libgcrypt-config not found 
(${LIBGCRYPT_CONFIG_SCRIPT})")
else()
[...]
8X

A Debian specific patch could simply drop the whole block
find_program(LIBGCRYPT_CONFIG_SCRIPT NAMES libgcrypt-config)
if (LIBGCRYPT_CONFIG_SCRIPT MATCHES ".+-NOTFOUND")
[...]
endif()

I will give it a litte bit of time to check whether somebody else from
-med picks this up and will NMU otherwise.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
From: Andreas Metzler 
Date: Sun, 23 Jun 2024 13:26:46 +0200
Subject: Use pkg-config to locate gcrypt include path instead of
 libgcrypt-config

---
 CMakeLists.txt | 16 +++-
 1 file changed, 3 insertions(+), 13 deletions(-)

diff --git a/CMakeLists.txt b/CMakeLists.txt
index cd06044..c9e57f4 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -524,19 +524,9 @@ add_custom_target(gen_tls_options
   DEPENDS ${GTM_BINARY_DIR}/gen_tls_options.h ${GTM_BINARY_DIR}/gen_tls_verify_options.h)
 
 # Locate libgcrypt's header files (assumption: all others headers are found in the same location)
-find_program(LIBGCRYPT_CONFIG_SCRIPT NAMES libgcrypt-config)
-if (LIBGCRYPT_CONFIG_SCRIPT MATCHES ".+-NOTFOUND")
-	message(FATAL_ERROR "FATAL: libgcrypt-config not found (${LIBGCRYPT_CONFIG_SCRIPT})")
-else()
-	# libgcrypt-config --cflags returns "\n" when the includes are located in the default search path
-	exec_program(${LIBGCRYPT_CONFIG_SCRIPT} ARGS --cflags RETURN_VALUE _return_VALUE OUTPUT_VARIABLE LIBGCRYPT_CFLAGS)
-	# If a path is returned, it is preceded by '-I' for use as CFLAG directive
-	string(REGEX REPLACE "^-I" "" LIBGCRYPT_INCLUDES "${LIBGCRYPT_CFLAGS}")
-	if (NOT (${LIBGCRYPT_INCLUDES} MATCHES "\n"))
-		message("INFO: ${LIBGCRYPT_CONFIG_SCRIPT} ${_return_VALUE} '${LIBGCRYPT_INCLUDES}'")
-		include_directories(${LIBGCRYPT_INCLUDES})
-	endif()
-endif()
+include(FindPkgConfig)
+pkg_check_modules(LIBGCRYPT REQUIRED libgcrypt)
+include_directories(${LIBGCRYPT_INCLUDE_DIRS})
 
 # Building the three encryption libraries could by a loop of some sort, but
 # manually creating each target is way easier.

Processed: Re: Bug#1071860: not fixed in 7.0-005-2 (was: Bug#1071860 closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#1071860: fixed in f

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1071860 [src:fis-gtm] fis-gtm: Searches for libgcrypt with libgcrypt-config
Added tag(s) patch.

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

Bug#1071268: Patch

[Adrien CLERC]

I used the following patch to manage all cases, see attached.

Have fun,

Adrien
Description: Support Linux >= 6.8
 strlcpy was removed in Linux 6.8, and we should use strscpy.
 Returned value was not checked before, so we keep it like this.
Author: Adrien CLERC 
Last-Update: 2024-06-23
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
Index: nat-rtsp-0.7+5.3/nf_conntrack_rtsp.c
===
--- nat-rtsp-0.7+5.3.orig/nf_conntrack_rtsp.c
+++ nat-rtsp-0.7+5.3/nf_conntrack_rtsp.c
@@ -549,7 +549,12 @@ init(void)
 			sprintf(tmpname, "rtsp-%d", i);
 		}
 
-#if LINUX_VERSION_CODE >= KERNEL_VERSION(3,6,0)
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(6,8,0)
+		// strlcpy was removed from Linux from 6.8-rc1
+		// see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=57f22c8dab6b266ae36b89b073a4a33dea71e762
+		strscpy(hlpr->name, tmpname, sizeof(hlpr->name));
+#elif LINUX_VERSION_CODE >= KERNEL_VERSION(3,6,0)
+		// Keeping legacy code
 		strlcpy(hlpr->name, tmpname, sizeof(hlpr->name));
 #else
 		hlpr->name = tmpname;
linux_6_8.diff

Bug#1074086: marked as done (/usr/sbin/coldreboot is ineffectively diverted by bfh-container, molly-guard and progress-linux-container)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 11:19:50 +
with message-id 
and subject line Bug#1074086: fixed in kexec-tools 1:2.0.27-1.3
has caused the Debian Bug report #1074086,
regarding /usr/sbin/coldreboot is ineffectively diverted by bfh-container, 
molly-guard and progress-linux-container
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.)


-- 
1074086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kexec-tools
Version: 1:2.0.27-1.2
Severity: serious
User: helm...@debian.org
Usertags: dep17p3
Control: affects -1 + bfh-container molly-guard progress-linux-container
X-Debbugs-Cc: z...@debian.org

coldreboot is being moved from /bin to /usr/bin. Unfortunately,
bfh-container, molly-guard and progress-linux-container divert this
location causing problems.

I think we need the same (or similar) dance as with systemd-sysv. Each
of those packages needs to install mitigations and kexec-tools needs
versioned conflicts with unfixed versions of those.

Arguably, combining bfh-container or progress-linux-container with
kexec-tools is not a reasonable thing to do. In those cases, unversioned
conflicts may be applicable though they are not technically policy
compliant.

This bug serves as a migration blocker and helps apt-listbugs users with
not loosing their files.

Helmut
--- End Message ---
--- Begin Message ---
Source: kexec-tools
Source-Version: 1:2.0.27-1.3
Done: Chris Hofstaedtler 

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated kexec-tools 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, 23 Jun 2024 12:26:20 +0200
Source: kexec-tools
Architecture: source
Version: 1:2.0.27-1.3
Distribution: unstable
Urgency: medium
Maintainer: Khalid Aziz 
Changed-By: Chris Hofstaedtler 
Closes: 1074086
Changes:
 kexec-tools (1:2.0.27-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Conflict with DEP17-unmitigated versions of molly-guard, bfh-container,
 progress-linux-container. (Closes: #1074086)
Checksums-Sha1:
 1cbe457a7e236384c1ff5b74380ff42bfe426297 2005 kexec-tools_2.0.27-1.3.dsc
 6be8d0f32e9912121f0b6c5a124171d3b592a65f 27056 
kexec-tools_2.0.27-1.3.debian.tar.xz
 3eb4504736f2881b8ccf2c169997bfd41dbf1215 6665 
kexec-tools_2.0.27-1.3_arm64.buildinfo
Checksums-Sha256:
 c114fec79945dbfd2a44297a68589e6429a9e1f2a8ef2dac8338a2274b2947c1 2005 
kexec-tools_2.0.27-1.3.dsc
 4d5dd2ad67fad01c1be8fdb9bcade5db7a7199a3106acb8a0cf2fd9d7d27cc54 27056 
kexec-tools_2.0.27-1.3.debian.tar.xz
 8e74824950b86245cd7c184db34560751f1b4c8dd7cce07c297c603a3e6baa24 6665 
kexec-tools_2.0.27-1.3_arm64.buildinfo
Files:
 b87c2c1bd273c07903576b03ae6a0dc5 2005 admin optional kexec-tools_2.0.27-1.3.dsc
 2de701f0124eec002083f2490b68ea18 27056 admin optional 
kexec-tools_2.0.27-1.3.debian.tar.xz
 7096e8602ee4a0e3ffd4823bee2c73a3 6665 admin optional 
kexec-tools_2.0.27-1.3_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmZ3/1wACgkQXBPW25MF
LgPeyA//Z2HKQqg2tbc9qS6vkFDLeaObh1qlAYZ97793SPy+mGWYwAGcc1FBFYzE
h6kbrTaDtNKujPcXLYtj/qt0KRa2Pt0LHIBcW8GDjUFqd60B5FtFK3dXIqzcC4Hf
iMOj66VqWXT3fBPpLNW4hZ0gT3BKi0CEYcqxBhAGCjBm7xL5cYjZAbVrXLbXR+qm
uFYXR4HrOSh/0bLFYPdIeY+eYjsCifm4sOW0OjJH8P483M+XEZwN09JiehcgrYON
i6B6RM8SalJ89vLgV4s9fiuzTms6QRmbBvz+zGU+aZ+UnyyFn+3NYkx/g6BuYswm
XPELN7GjBoi5O4NGDq89ZoGEg9XxzTaI4YiA5ZFr0NbRoOH4KZutLA8GZxkNYbOn
5Z1yBunkN4/WNH77nEWcbLBJn9c0ikuAHoPD9zJPN8yH7ugXQw3usr6JGcXQ6vNc
FC0Us45wu1IufEulMRRvqOev6+Xcw/deu6ymewlGt7RPO7ydWeKKZrvUp6i9tUfk
njeQ9MAEOL1entWP9Nd+L27B9qWyyn2euQz/x06xfcL6HTTWBGul6igt4vqovrtT
XRALwLXlKMycCAjkkqoc7LlTdZOcfmrnB5Z+4qtuGrAIklyo39RxN17CXdfP9LPp
kVnR1LVwW7Dy0x677s6WeXQl1zsX4nKDdcfv8J6xTCImh42tr38=
=+8dV
-END PGP SIGNATURE-



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

Bug#1074086: kexec-tools: diff for NMU version 1:2.0.27-1.3

[Chris Hofstaedtler]

On Sun, Jun 23, 2024 at 12:56:13PM +0200, Chris Hofstaedtler wrote:
> I've prepared an NMU for kexec-tools (versioned as 1:2.0.27-1.3) and
> uploaded it to DELAYED/5.

Given I'm fixing my own NMU, I've rescheduled to immediate per
another DD's advice.

Sorry if that's surprising.

Chris

Processed: kexec-tools: diff for NMU version 1:2.0.27-1.3

[Debian Bug Tracking System]

Processing control commands:

> tags 1074086 + patch
Bug #1074086 [kexec-tools] /usr/sbin/coldreboot is ineffectively diverted by 
bfh-container, molly-guard and progress-linux-container
Added tag(s) patch.
> tags 1074086 + pending
Bug #1074086 [kexec-tools] /usr/sbin/coldreboot is ineffectively diverted by 
bfh-container, molly-guard and progress-linux-container
Added tag(s) pending.

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

Bug#1074086: kexec-tools: diff for NMU version 1:2.0.27-1.3

[Chris Hofstaedtler]

Control: tags 1074086 + patch
Control: tags 1074086 + pending


Dear maintainer,

I've prepared an NMU for kexec-tools (versioned as 1:2.0.27-1.3) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru kexec-tools-2.0.27/debian/changelog kexec-tools-2.0.27/debian/changelog
--- kexec-tools-2.0.27/debian/changelog	2024-06-12 00:36:59.0 +0200
+++ kexec-tools-2.0.27/debian/changelog	2024-06-23 12:26:20.0 +0200
@@ -1,3 +1,11 @@
+kexec-tools (1:2.0.27-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Conflict with DEP17-unmitigated versions of molly-guard, bfh-container,
+progress-linux-container. (Closes: #1074086)
+
+ -- Chris Hofstaedtler   Sun, 23 Jun 2024 12:26:20 +0200
+
 kexec-tools (1:2.0.27-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru kexec-tools-2.0.27/debian/control kexec-tools-2.0.27/debian/control
--- kexec-tools-2.0.27/debian/control	2023-10-04 23:20:54.0 +0200
+++ kexec-tools-2.0.27/debian/control	2024-06-23 12:26:20.0 +0200
@@ -10,6 +10,7 @@
 Package: kexec-tools
 Architecture: linux-any
 Depends: ${shlibs:Depends}, ${misc:Depends}, debconf, dpkg (>= 1.15.7.2)
+Conflicts: molly-guard (<< 0.8.4~), bfh-container (<< 20211009-22~), progress-linux-container (<< 20221002-11~)
 Description: tools to support fast kexec reboots
  This package provides tools to load a kernel into memory and then
  "reboot" directly into that kernel using the kexec system call,

Processed: Re: Bug#1074111: [arm64] boot stops at 'Starting kernel ...' without any further output when kernel built with recent binutils

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1074111 [src:linux] [arm64] boot stops at 'Starting kernel ...' without 
any further output when kernel built with recent binutils
Bug 1074111 cloned as bug 1074112
> reassign -2 src:binutils
Bug #1074112 [src:linux] [arm64] boot stops at 'Starting kernel ...' without 
any further output when kernel built with recent binutils
Bug reassigned from package 'src:linux' to 'src:binutils'.
No longer marked as found in versions linux/6.9.2-1~exp1.
Ignoring request to alter fixed versions of bug #1074112 to the same values 
previously set
> found -2 binutils/2.42.50.20240618-1
Bug #1074112 [src:binutils] [arm64] boot stops at 'Starting kernel ...' without 
any further output when kernel built with recent binutils
Marked as found in versions binutils/2.42.50.20240618-1.

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

Processed (with 1 error): Re: Bug#1074111: [arm64] boot stops at 'Starting kernel ...' without any further output when kernel built with recent binutils

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 binutils/2.42.50.20240618-1
Unknown command or malformed arguments to command.

> affects -1 src:linux
Bug #1074111 [src:linux] [arm64] boot stops at 'Starting kernel ...' without 
any further output when kernel built with recent binutils
Added indication that 1074111 affects src:linux

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

Bug#1074111: [arm64] boot stops at 'Starting kernel ...' without any further output when kernel built with recent binutils

[Bastian Blank]

Control: reassign -1 binutils/2.42.50.20240618-1
Control: affects -1 src:linux

On Sun, Jun 23, 2024 at 11:44:05AM +0200, Johannes Schauer Marin Rodrigues 
wrote:
> One of the differences in the build environment between good and bad builds is
> binutils-arm-linux-gnueabihf with version 2.42-4 in the good environment and
> version 2.42.50.20240618-1 in the bad environment. To test whether this indeed
> triggers the problem, we tested building our kernel with current unstable but
> with binutils (= 2.42-4) and gcc-13 (= 13.2.0-25). We also have to choose an
> older gcc from snapshot.d.o because recent gcc-13 requires recent binutils.
> This makes the kernel work again.

So for now binutils triggers the problem, lets reassign correctly to get
the attention of the correct people.

Bastian

-- 
Extreme feminine beauty is always disturbing.
-- Spock, "The Cloud Minders", stardate 5818.4

Bug#1074111: [arm64] boot stops at 'Starting kernel ...' without any further output when kernel built with recent binutils

[Chris Hofstaedtler]

Control: clone -1 -2
Control: reassign -2 src:binutils
Control: found -2 binutils/2.42.50.20240618-1

I'm cloning this to src:binutils as the problem is likely either
there or in gcc; as Johannes stated below, the newer gcc requires
the new binutils. If it's gcc, please reassign there.

CC-ed debian-arm@ to also reach the ARM64 porters.

On Sun, Jun 23, 2024 at 11:44:05AM +0200, Johannes Schauer Marin Rodrigues 
wrote:
> [..] Compiling the
> same kernel version 6.8.12 in *unstable* within a more recent build 
> environment
> results in a vmlinuz that just prints on boot:
> 
> Starting kernel ...
> 
> And then nothing else. Since neither the linux sources in debian unstable
> changed, nor our patch stack changed between these rebuilds, the culprit is
> likely in the build environment. [..]
> [..] We also observed how the good vmlinuz has a size of 31M and
> the bad vmlinuz a size of only 26M.
> This is with the same sources, just different build chroot environment. An
> old-enough build environment can be constructed using snapshot.d.o.

> One of the differences in the build environment between good and bad builds is
> binutils-arm-linux-gnueabihf with version 2.42-4 in the good environment and
> version 2.42.50.20240618-1 in the bad environment. To test whether this indeed
> triggers the problem, we tested building our kernel with current unstable but
> with binutils (= 2.42-4) and gcc-13 (= 13.2.0-25). We also have to choose an
> older gcc from snapshot.d.o because recent gcc-13 requires recent binutils.
> This makes the kernel work again.

> So, given that the problem affects linux in unstable *if* built with a more
> recent build environment, the problem might not be in src:linux but elsewhere
> (maybe binutils or gcc-13). I'm still filing it here as I lack the skills to
> investigate this problem further. Since the issue shows up with qemu, I'm sure
> that you can get to the bottom of it and can re-assign this bug to the package
> to which it belongs.

I think this also means rebuilding an existing kernel in unstable
or testing will also break.

Chris

Bug#1074111: [arm64] boot stops at 'Starting kernel ...' without any further output when kernel built with recent binutils

[Johannes Schauer Marin Rodrigues]

Source: linux
Version: 6.9.2-1~exp1
Severity: serious

Hi,

to reproduce this locally, on arm64, run the following:

$ debvm-create -- --include=linux-image-generic/experimental "deb 
http://deb.debian.org/debian unstable main" "deb http://deb.debian.org/debian 
experimental main"
$ debvm-run

The debvm-run output will stop at the point where it starts qemu and then print
nothing.  It works fine with kernel 6.8 in unstable.

Now comes my naive attempt to figure out what triggered this regression. Please
bear in mind that I'm far from an expert on this topic.

We observed this problem when we built the linux kernel for the MNT Reform
which is the Debian linux kernel plus some additional patches. Compiling the
same kernel version 6.8.12 in *unstable* within a more recent build environment
results in a vmlinuz that just prints on boot:

Starting kernel ...

And then nothing else. Since neither the linux sources in debian unstable
changed, nor our patch stack changed between these rebuilds, the culprit is
likely in the build environment. Kernel 6.9 from experimental exhibits the same
problems. We also observed that copying the vmlinuz from an earlier build in
the good chroot environment made the system boot fine again. We also observed
how the good vmlinuz has a size of 31M and the bad vmlinuz a size of only 26M.
This is with the same sources, just different build chroot environment. An
old-enough build environment can be constructed using snapshot.d.o.

One of the differences in the build environment between good and bad builds is
binutils-arm-linux-gnueabihf with version 2.42-4 in the good environment and
version 2.42.50.20240618-1 in the bad environment. To test whether this indeed
triggers the problem, we tested building our kernel with current unstable but
with binutils (= 2.42-4) and gcc-13 (= 13.2.0-25). We also have to choose an
older gcc from snapshot.d.o because recent gcc-13 requires recent binutils.
This makes the kernel work again.

So, given that the problem affects linux in unstable *if* built with a more
recent build environment, the problem might not be in src:linux but elsewhere
(maybe binutils or gcc-13). I'm still filing it here as I lack the skills to
investigate this problem further. Since the issue shows up with qemu, I'm sure
that you can get to the bottom of it and can re-assign this bug to the package
to which it belongs.

Gratitude is due to Chris Hofstaedtler who convinced me that maybe this is a
problem even with vanilla Debian kernel and not only with the Debian kernel
with our patches on top.

Thanks!

cheers, josch

Bug#1071860: not fixed in 7.0-005-2 (was: Bug#1071860 closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#1071860: fixed in fis-gtm 7.0-005-

[Andreas Tille]

Control: tags -1 help

Hi Andreas,

strange, it has build for me.

Am Sun, Jun 23, 2024 at 08:03:30AM +0200 schrieb Andreas Metzler:
> Control: reopen 1071860
> ...
> CMake Error at CMakeLists.txt:529 (message):
>   FATAL: libgcrypt-config not found (LIBGCRYPT_CONFIG_SCRIPT-NOTFOUND)
> [...]

I admit I currently have no time to track this down.  It might make
sense to upgrade to latest upstream which might have been adapted to
work without libgcrypt-config.   Tagging the bug help since I have no
capacity to work on this.

Kind regards
Andreas.

-- 
https://fam-tille.de

Processed: Re: Bug#1071860: not fixed in 7.0-005-2 (was: Bug#1071860 closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#1071860: fixed in f

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #1071860 [src:fis-gtm] fis-gtm: Searches for libgcrypt with libgcrypt-config
Added tag(s) help.

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

Processed: python-xarray: autopkgtest regression with pytest 8

[Debian Bug Tracking System]

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

> reassign 1063981 python3-xarray 2023.12.0-3
Bug #1063981 [src:python-xarray] python-xarray: autopkgtest regression with 
pytest 8
Bug reassigned from package 'src:python-xarray' to 'python3-xarray'.
No longer marked as found in versions python-xarray/2023.12.0-3.
Ignoring request to alter fixed versions of bug #1063981 to the same values 
previously set
Bug #1063981 [python3-xarray] python-xarray: autopkgtest regression with pytest 
8
Marked as found in versions python-xarray/2023.12.0-3.
> thanks
Stopping processing here.

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

Bug#1069357: marked as done (cpp-httplib: FTBFS: Test SSLClientServerTest.ClientCertPresent fails with timeout)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 09:00:11 +
with message-id 
and subject line Bug#1069357: fixed in cpp-httplib 0.15.3+ds-1
has caused the Debian Bug report #1069357,
regarding cpp-httplib: FTBFS: Test SSLClientServerTest.ClientCertPresent fails 
with timeout
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.)


-- 
1069357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpp-httplib
Version: 0.14.3+ds-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- \
>   --timeout-multiplier=3 \
>   --test-args='--gtest_filter=-*_Online'
>   cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb 
> LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3 
> --test-args=--gtest_filter=-\*_Online
> ninja: Entering directory `/<>/obj-aarch64-linux-gnu'
> ninja: no work to do.
> 1/1 main TIMEOUT900.12s   killed by signal 15 SIGTERM
> >>> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
> >>> MALLOC_PERTURB_=215 
> >>> LD_LIBRARY_PATH=/<>/obj-aarch64-linux-gnu/ 
> >>> UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
> >>>  /<>/obj-aarch64-linux-gnu/test/main 
> >>> '--gtest_filter=-*_Online'
> 
> 
> Ok: 0   
> Expected Fail:  0   
> Fail:   0   
> Unexpected Pass:0   
> Skipped:0   
> Timeout:1   
> 
> Full log written to 
> /<>/obj-aarch64-linux-gnu/meson-logs/testlog.txt
>   cd obj-aarch64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt
> ==> meson-logs/testlog.txt <==
> Log of Meson test suite run on 2024-04-20T04:04:32.461534
> 
> Inherited environment: SCHROOT_GID=1001 DEB_HOST_MULTIARCH=aarch64-linux-gnu 
> LC_ALL=C.UTF-8 DEB_HOST_GNU_SYSTEM=linux-gnu 
> DEB_BUILD_GNU_TYPE=aarch64-linux-gnu DEB_TARGET_ARCH_LIBC=gnu FFLAGS='-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -mbranch-protection=standard' 
> DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_GNU_SYSTEM=linux-gnu 
> CFLAGS_FOR_BUILD='-g -O2' OBJCXXFLAGS_FOR_BUILD='-g -O2' 
> DEB_BUILD_ARCH_BITS=64 DEB_BUILD_OPTIONS=parallel=4 DEB_HOST_ARCH=arm64 
> LDFLAGS_FOR_BUILD='' DEB_TARGET_ARCH_ENDIAN=little 
> SOURCE_DATE_EPOCH=1709141979 OBJCFLAGS_FOR_BUILD='-g -O2' OBJCXXFLAGS='-g -O2 
> -D__DEB_CANARY_OBJCXXFLAGS_8430b32b5bac908e765df8813d4405c5__ 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security 
> -mbranch-protection=standard' DEB_HOST_ARCH_BITS=64 LANG=C.UTF-8 MAKEFLAGS=w 
> SCHROOT_GROUP=user42 DEB_TARGET_ARCH=arm64 
> DH_INTERNAL_OPTIONS=-O--buildsystem=meson DEB_HOST_GNU_CPU=aarch64 
> DEB_BUILD_ARCH_LIBC=gnu MFLAGS=-w DEB_TARGET_ARCH_BITS=64 
> CXXFLAGS_FOR_BUILD='-g -O2' ASFLAGS='' DEB_BUILD_ARCH_CPU=arm64 
> LC_COLLATE=C.UTF-8 SCHROOT_ALIAS_NAME=unstable-arm64 DEB_HOST_ARCH_OS=linux 
> SHELL=/bin/sh FCFLAGS='-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection 
> -mbranch-protection=standard' DEB_HOST_ARCH_CPU=arm64 SCHROOT_USER=user42 
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games 
> DEB_BUILD_ARCH_ABI=base CPPFLAGS_FOR_BUILD='' DEB_BUILD_ARCH=arm64 
> DEB_CPPFLAGS_MAINT_APPEND=-DCPPHTTPLIB_USE_POLL FFLAGS_FOR_BUILD='-g -O2' 
> DEB_HOST_ARCH_LIBC=gnu 
> SCHROOT_SESSION_ID=sid-arm64-sbuild-76294e14-75b8-448e-84c9-dc36c894aeb5 
> DEB_TARGET_ARCH_CPU=arm64 DEB_HOST_GNU_TYPE=aarch64-linux-gnu 
> DEB_BUILD_ARCH_OS=linux FCFLAGS_FOR_BUILD='-g -O2' DFLAGS_FOR_BUILD=-frelease 
> LOGNAME=user42 
> CPPFLAGS='-D__DEB_CANARY_CPPFLAGS_8430b32b5bac908e765df8813d4405c5__ 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DCPPHTTPLIB_USE_POLL' 
> DEB_TARGET_MULTIARCH=aarch64-linux-gnu DEB_BUILD_GNU_CPU=aarch64 
> DEB_TARGET_ARCH_OS=linux USER=user42 DEB_HOST_ARCH_ABI=base 
> DEB_BUILD_MULTIARCH=aarch64-linux-gnu 
> LDFLAGS='-Wl,-z,deb-canary-8430b32b5bac908e765df8813d4405c5 -Wl,-z,relro 
> -Wl,-z,now' DEB_TARGET_GNU_TYPE=aarch64-linux-gnu DEB_TARGET_ARCH_ABI=base 
> CFLAGS='-g -O2 -Werror=implicit-function-declaration -Werror=array-bounds 
> -Werror=clobbered -Werror=volatile-register-var 
> -D__DEB_CANARY_CFLAGS_8430b32b5bac908e765df8813d4405c5__ 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat 

Bug#1073440: marked as done (cpp-httplib: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier=3 --te

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 09:00:11 +
with message-id 
and subject line Bug#1073440: fixed in cpp-httplib 0.15.3+ds-1
has caused the Debian Bug report #1073440,
regarding cpp-httplib: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && 
DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test 
--timeout-multiplier=3 --test-args=--gtest_filter=-\*_Online returned exit code 
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.)


-- 
1073440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpp-httplib
Version: 0.14.3+ds-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 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_auto_test -- \
>   --timeout-multiplier=3 \
>   --test-args='--gtest_filter=-*_Online'
>   cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 
> MESON_TESTTHREADS=8 meson test --timeout-multiplier=3 
> --test-args=--gtest_filter=-\*_Online
> ninja: Entering directory `/<>/obj-x86_64-linux-gnu'
> ninja: no work to do.
> 1/1 main TIMEOUT900.13s   killed by signal 15 SIGTERM
> >>> MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
> >>>  LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/ 
> >>> MALLOC_PERTURB_=233 
> >>> UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
> >>>  ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
> >>> /<>/obj-x86_64-linux-gnu/test/main '--gtest_filter=-*_Online'
> 
> 
> Ok: 0   
> Expected Fail:  0   
> Fail:   0   
> Unexpected Pass:0   
> Skipped:0   
> Timeout:1   
> 
> Full log written to 
> /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt
> ==> meson-logs/testlog.txt <==
> Log of Meson test suite run on 2024-06-16T12:06:54.721387
> 
> Inherited environment: SCHROOT_GID=1001 DEB_HOST_MULTIARCH=x86_64-linux-gnu 
> LC_ALL=C.UTF-8 DEB_HOST_GNU_SYSTEM=linux-gnu 
> DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_TARGET_ARCH_LIBC=gnu FFLAGS='-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection' DEB_BUILD_ARCH_ENDIAN=little 
> DEB_BUILD_GNU_SYSTEM=linux-gnu CFLAGS_FOR_BUILD='-g -O2' 
> OBJCXXFLAGS_FOR_BUILD='-g -O2' DEB_BUILD_ARCH_BITS=64 
> DEB_BUILD_OPTIONS=parallel=8 DEB_HOST_ARCH=amd64 LDFLAGS_FOR_BUILD='' 
> DEB_TARGET_ARCH_ENDIAN=little SOURCE_DATE_EPOCH=1709141979 
> OBJCFLAGS_FOR_BUILD='-g -O2' OBJCXXFLAGS='-g -O2 
> -D__DEB_CANARY_OBJCXXFLAGS_f499d34bd87b42948b3960b8f6b82e74__ 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' 
> DEB_HOST_ARCH_BITS=64 LANG=C.UTF-8 MAKEFLAGS=w SCHROOT_GROUP=user42 
> DEB_TARGET_ARCH=amd64 DH_INTERNAL_OPTIONS=-O--buildsystem=meson 
> DEB_HOST_GNU_CPU=x86_64 DEB_BUILD_ARCH_LIBC=gnu MFLAGS=-w 
> DEB_TARGET_ARCH_BITS=64 CXXFLAGS_FOR_BUILD='-g -O2' ASFLAGS='' 
> DEB_BUILD_ARCH_CPU=amd64 LC_COLLATE=C.UTF-8 SCHROOT_ALIAS_NAME=unstable 
> DEB_HOST_ARCH_OS=linux SHELL=/bin/sh FCFLAGS='-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -fcf-protection' DEB_HOST_ARCH_CPU=amd64 
> SCHROOT_USER=user42 
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games 
> DEB_BUILD_ARCH_ABI=base CPPFLAGS_FOR_BUILD='' DEB_BUILD_ARCH=amd64 
> DEB_CPPFLAGS_MAINT_APPEND=-DCPPHTTPLIB_USE_POLL FFLAGS_FOR_BUILD='-g -O2' 
> DEB_HOST_ARCH_LIBC=gnu 
> SCHROOT_SESSION_ID=sid-amd64-sbuild-cb07bbfa-b055-4786-8b93-89d3c6583cfe 
> DEB_TARGET_ARCH_CPU=amd64 DEB_HOST_GNU_TYPE=x86_64-linux-gnu 
> DEB_BUILD_ARCH_OS=linux FCFLAGS_FOR_BUILD='-g -O2' DFLAGS_FOR_BUILD=-frelease 
> LOGNAME=user42 
> CPPFLAGS='-D__DEB_CANARY_CPPFLAGS_f499d34bd87b42948b3960b8f6b82e74__ 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DCPPHTTPLIB_USE_POLL' 
> DEB_TARGET_MULTIARCH=x86_64-linux-gnu DEB_BUILD_GNU_CPU=x86_64 
> DEB_TARGET_ARCH_OS=linux USER=user42 DEB_HOST_ARCH_ABI=base 
> DEB_BUILD_MULTIARCH=x86_64-linux-gnu 
> LDFLAGS='-Wl,-z,deb-canary-f499d34bd87b42948b3960b8f6b82e74 -Wl,-z,relro 
> -Wl,-z,now' DEB_TARGET_GNU_TYPE=x86_64-linux-gnu DEB_TARGET_ARCH_ABI=base 
> CFLAGS='-g -O2 -Werror=implicit-function-declaration -Werror=array-bounds 
> -Werror=clobbered -Werror=volatile-register-var 
> 

Bug#1074107: librust-zbus-dev: please urgently patch to accept rust-async-fs

[Jonas Smedegaard]

Package: librust-zbus-dev
Version: 3.14.1-7
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I have bumped rust-async-fs from v1 to v2, and only afterwards realized
that I had forgotten to check for reverse dependencies.  Seems there is
only one, rust-zbus.

Please patch rust-zbus to accept newer v2 of rust-async-fs.  If that is
not possible, then please tell, and I will do an ugly rollback of
rust-async-fs to v1, by use of messy versioning scheme 2+really.1, until
migration is possible (which may involve the whole async-* and smol
stack).

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZ35JwACgkQLHwxRsGg
ASHsvQ//TJ3U2fPlnXXSnxM6+jQ+e8pQm6E7QQdWRrIIbatLNjB/4iPKOC4hXVMi
Jmg8U3I/LtXOvP01VelsYAxezKfL8xbzewrCmQcQFLC6NF/o5wUtT1TuQNkB4q1K
Zjpr/JdKMyN+TSp0p1tJNtUUlkD4OzyA9taVB+poyONmqv+GaOkM1oesk5f0ldhT
okacREtqL/K66zWaoPC6BZG/tcchx3KZfmbA6ArPwxtUxTz26c5WPubW/dSX/55n
XedQhCvpbEppYAZotziDjXK7ofWEydnRC45LeChFKfLCDm9gXzoD3z2QWbCG9HQ0
A1oYfAWaP8eN0HMJ9JqNtniBrriVDlFJuXaujwFhq5E4W4xrHGOYNaFlk9/x0RVz
zym/hXuEgVgPW177v6kLF9rWV2gUScqyxEnm88sZQ+1/g+MnxH4WX1fnsdZqpqvT
Z80sBYFIRc0nbxiLnrp9iTVi7RCQF523I1TfhBxiYt/uE5Xs9XmOusAl2fdiCzxb
5czLJzWAKVL+E0KY9+CFRq30+LDN4KOJs3FUwUjaOR0Db4quToJ/8mhFtZtyZq45
MgpzQFktG4dapx0DU2kDUyP3o5W2BLGiNZa4CGWybMbKN29vAJN0JcIUi1Xb5OPH
RDNw4R14GM42eIXABd6Hylh426XA+JOUireeK4JZHSrU08qpsPc=
=lcWD
-END PGP SIGNATURE-

Processed: python-xarray: autopkgtest regression with pytest 8

[Debian Bug Tracking System]

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

> reassign 1063981 src:python-xarray 2023.12.0-3
Bug #1063981 [src:python-xarray] python-xarray: autopkgtest regression with 
pytest 8
Ignoring request to reassign bug #1063981 to the same package
Bug #1063981 [src:python-xarray] python-xarray: autopkgtest regression with 
pytest 8
Marked as found in versions python-xarray/2023.12.0-3.
> thanks
Stopping processing here.

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

Bug#1074104: rust-criterion-0.3: drop package: outdated branch unmaintained upstream

[Jonas Smedegaard]

Source: rust-criterion-0.3
Version: 0.3.6-8
Severity: grave
Tags: upstream
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The branch v0.3 of rust crate criterion has last seen a release in 2022.
Newest branch v0.5 is also in Debian, last updated upstream in mid 2023.

All packages should migrate away from criterion v0.3, as that will *not*
be maintained in Debian any longer, and should therefore be dropped as
soon as possible.  One option is to migrate to criterion v0.5.  A better
option might be to package  codspeed-criterion-compat and migrate to
that, given that it is actively maintained upstream.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZ34BwACgkQLHwxRsGg
ASH24hAAqq9DapveQw4ELvQLkRhkR1+3KFSPseUPD/AOM9sWloGwU/0yhDuuZo6f
Fs0QEx7NcWgi+GVQr3OgS4Yh5SCMD9Ma9tKepEnTn9Bvz92whwYyFNZRbCP9BqRu
jIJV4tio1uVkbbYLf/X8FIkyURhipSqZVtEV8Db48I4XOP1/2AxTNUNxEEyWEZ1c
fzMlAmXwj8UIqQvf/QYaVmKkAgVjHAtGZAN8JqsfpqSjBVD33WNa32nxz8riUr1U
HcpikUQM44wc4ehE+cvkVUeaMKwVBD2O5Ysd9y024R1P1pKmMkg/cTy/KwkIits2
G/Wm0XhVFVtfmTjBYFsalTJc48vdomyC37xa1Bz+15Wj6z0n/hipiu1iO6Oj3iT8
3E1SCGEpDdPRC5U0HVw2isMru1rDxCnvgXyD4BSbdOgTO0TUF6L046CayoxDJvvM
d5tbRLf4G5sNeQ1xjG4lc3Rhc+lBkCJkgOjpvXiFDb/CewBTyM8XuNX/RnrtRQYT
QPf/Lvefd1AGKwBvbNIzoK2BIrP9madTl62Z6/jSELzMnUfamYHV0vOlnoy4Escg
niBbTSCydMWBZy1rYoWCepuev1JvEEkR82dxhwBw8t8RmbJPbw35+rfolcEEoFY3
uzfKJYaO3MSphzqMXZEfNPNCauP+ClFDdVvTpk8s9aMITjV5B+Y=
=T7ek
-END PGP SIGNATURE-

Bug#1074049: marked as done (nwg-hello: update dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 08:35:35 +
with message-id 
and subject line Bug#1074049: fixed in nwg-hello 0.2.2-1
has caused the Debian Bug report #1074049,
regarding nwg-hello: update dependencies
to be marked as done.

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

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


-- 
1074049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nwg-hello
Severity: serious

Should depend on gir1.2-* libs instead of development headers, and
should have python3-gi in Depends as well.

-- 
Maytham Alsudany
Debian Maintainer

maytham @ OFTC
maytha8 @ Libera



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: nwg-hello
Source-Version: 0.2.2-1
Done: Maytham Alsudany 

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

Debian distribution maintenance software
pp.
Maytham Alsudany  (supplier of updated nwg-hello 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Jun 2024 15:29:21 +0800
Source: nwg-hello
Architecture: source
Version: 0.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Maytham Alsudany 
Changed-By: Maytham Alsudany 
Closes: 1074048 1074049
Changes:
 nwg-hello (0.2.2-1) unstable; urgency=medium
 .
   * New upstream version 0.2.2 (Closes: #1074048)
   * Fix dependencies (Closes: #1074049)
Checksums-Sha1:
 e2c320f08eaefdd8a5775dfba101e0d96a40c0a9 1899 nwg-hello_0.2.2-1.dsc
 868a76c41309e59bc9d19e20f8fb21eabf2ed8bb 1462259 nwg-hello_0.2.2.orig.tar.gz
 3dd451ae7ac145ea571950472d594522cbe2987c 2920 nwg-hello_0.2.2-1.debian.tar.xz
 a6b77786aa0f12a4e1a5476e9208ad1e06711a7a 6378 nwg-hello_0.2.2-1_amd64.buildinfo
Checksums-Sha256:
 0396efa3eb7ff06b71905bcc6d1a6adfcf9ebbf44cadc4c402c3ef64d3a5a935 1899 
nwg-hello_0.2.2-1.dsc
 fe4ff972dfb1296e68e7648fc7ea9504870092c84aa997a9719c1db595f48924 1462259 
nwg-hello_0.2.2.orig.tar.gz
 602edbc1a83a929e77252b52433a3f80b720efe5641d2df3aa32a0184202fff4 2920 
nwg-hello_0.2.2-1.debian.tar.xz
 3a74a172a11c69e50f70c73e08b016c68cd6c70533362e60281f52227fdf980c 6378 
nwg-hello_0.2.2-1_amd64.buildinfo
Files:
 c60084ab10cfbd481c46f6fee3e8c399 1899 misc optional nwg-hello_0.2.2-1.dsc
 1d19a6b5c3c72ddcd994bf9616e67402 1462259 misc optional 
nwg-hello_0.2.2.orig.tar.gz
 409e0b7454f5e71ba72f1aefbc163f6a 2920 misc optional 
nwg-hello_0.2.2-1.debian.tar.xz
 1bb433326c53a75cefd48bf03bb44b66 6378 misc optional 
nwg-hello_0.2.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEESl/RzRFQh8wD3DXB1ZeJcgbF8H8FAmZ30NwACgkQ1ZeJcgbF
8H/kKg//YCfhOL8cnvgMJzB+Eiszx/Ls5uQy8qdDpOZH78rPgRfpExYnptcwVnAB
9g523ukEWk36cSKLKYWFRTWhomYzbWzCHRv/ZX47WW3hXCmWZLvjBh+bqQlef3rj
aCvQK6/BAdflaDGle85bmWxS44eqsR424jOF6vAJ6BdCRl/PkH7ZpFh/OaFQgBcj
Rqk5z3ns5nALQOACdnVYduFKg1+e3RZau/xFfLv0CHoMESsjXpqQwAeK99zVryg6
+wrEBkcPbCQW0RpogH1zHJ5H+9G1W7M+IfsGRF0xBCDvk902QvXgqoeSXfrfUguZ
xhV0y77fapoBqApJ15bh7whTeSm2N51xCPQ0WsJciR9gXcR6W2LfpY2OdPZ6BEsZ
3OKT+GJEB82jAwPb5VcLe8nSk//Rzsi/eDYOzy8JBXHHC+afoUBLP18p9hq+UzUK
MUoKA5J7EtKFB+vLwwBxwrXjEdKvDhB0VnTMFSu3/UlCEPms0HVC36uwzj8+Nd07
uUeB1LNwQ6KFVmsy8hjwePbtsDX6gloGiH4TjRTx5kp4wvTtIyz4Fhg/b1IAo9bh
YY/TKtzfwqpWSq8k1AFdzfJFSkZv1VioZuD8jAOzgrrpmB7EPvLaGXBWo9HMPuXi
lsPsRDFErqDH1Qv2regAYeqmToOmFoS0bdBqeaxPgSQ96sa+Uec=
=u6Cw
-END PGP SIGNATURE-



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

Processed: python-xarray: autopkgtest regression with pytest 8

[Debian Bug Tracking System]

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

> reassign 1063981 src:python-xarray
Bug #1063981 [python-xarray] python-xarray: autopkgtest regression with pytest 8
Bug reassigned from package 'python-xarray' to 'src:python-xarray'.
No longer marked as found in versions 2023.12.0-3.
Ignoring request to alter fixed versions of bug #1063981 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1074050: marked as done (nwg-clipman: update dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 23 Jun 2024 07:49:49 +
with message-id 
and subject line Bug#1074050: fixed in nwg-clipman 0.2.1-2
has caused the Debian Bug report #1074050,
regarding nwg-clipman: update dependencies
to be marked as done.

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

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


-- 
1074050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nwg-clipman
Severity: serious

Should depend on gir1.2-* libs instead of development headers, and
should have python3-gi in Depends as well.

-- 
Maytham Alsudany
Debian Maintainer

maytham @ OFTC
maytha8 @ Libera



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: nwg-clipman
Source-Version: 0.2.1-2
Done: Maytham Alsudany 

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

Debian distribution maintenance software
pp.
Maytham Alsudany  (supplier of updated nwg-clipman 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 23 Jun 2024 15:30:20 +0800
Source: nwg-clipman
Architecture: source
Version: 0.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Maytham Alsudany 
Changed-By: Maytham Alsudany 
Closes: 1074050
Changes:
 nwg-clipman (0.2.1-2) unstable; urgency=medium
 .
   * Fix dependencies (Closes: #1074050)
Checksums-Sha1:
 b1f3fb6ee9fbc6eaa65bd2c1b996c0ed2c546756 2004 nwg-clipman_0.2.1-2.dsc
 ff9097e82c58e0e81c8f53c67950b58112b2aeab 2780 nwg-clipman_0.2.1-2.debian.tar.xz
 d0c88c730af05e2950ff0d7f3a1f2a182c61eb19 6544 
nwg-clipman_0.2.1-2_amd64.buildinfo
Checksums-Sha256:
 f455e426385395f492b59257528c5333592de9700b5f60f3044913f78a889e93 2004 
nwg-clipman_0.2.1-2.dsc
 636e3191a207ae8e8e6c30229e86afe7f3f684b44eb012c94b373d0f0eaa47d8 2780 
nwg-clipman_0.2.1-2.debian.tar.xz
 ba56d8838729761b76ab9a643e3fc421ca4bf3a8b8c4bc8672d5954fe4d79d03 6544 
nwg-clipman_0.2.1-2_amd64.buildinfo
Files:
 115547148cb1f12e65085952ca258187 2004 utils optional nwg-clipman_0.2.1-2.dsc
 bb0fb4349cc7c6cc7adba9b74c99edf8 2780 utils optional 
nwg-clipman_0.2.1-2.debian.tar.xz
 c5e2174eb3bea299a2bbfd58abb47dbf 6544 utils optional 
nwg-clipman_0.2.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEESl/RzRFQh8wD3DXB1ZeJcgbF8H8FAmZ3z3MACgkQ1ZeJcgbF
8H+cWxAAgsZMHLTSi/2ymBREfrX9PPowvG6CZ1Q1cRCs77WVITqf5igsgsktTW39
dygyNwwpWWdPX3bWYvPOcLJRjF5b6IRfnGXP0pHOWDYClLnH2V8ERr1LQEmx0+LO
4sPkfMSODbB2zEAnrm0phXj65JwlPGppYXmlDVOf2YyzeYTLRXjYh/3GUlFLVyBQ
560Sezf77S3qecKUj/tGAoAHSfSGMgXmK1c/R9oAPg+YWT7KXyhtFbkDom5q2z2y
/oBvGYmkKhMBzin1pKB29ODSLIwcB5dWLwsBCg8QPIDLzxpB2Kx+m86fxQzltk6k
rXeXhvVFpr1CZKjvf7+tnVhS+LnW1D2cRHS0RNM7quaAEv80UZIrU3WGM81YBGod
Vht3gHgcXP3MWDLQWdM6LuPhwnOTwb4mTnZn7jjPDTE8pPXl+lRLmmfVcfRfAz72
O074xw+ebS91ijTFbOz5vae1tuiMalM36aYlqS3nAF8xbZlIVuuFRcMZMRMgC0zO
4IULpxLXcAd/QCXiMIW7n6H0UQ0eLnBoASCM0opXPFps/8xJlfnMFtCemYiFPvHb
56kgePI9IOABQtXQgr28v6Eqyfy9akKmBCN6bzzMHsEWpsVzJlHGxnXm49UvTc2i
1qRIJm94aFK7V9hn1CUFM9OCdZWrsIT2/ZG5EpxxS28KbfBJFhg=
=0zcD
-END PGP SIGNATURE-



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

Bug#1061212: Please upgrade to llvm-toolchain-17

[Michael Tokarev]

On Sat, 16 Mar 2024 15:05:34 +0100 Bastian Germann  wrote:

v3.1.44 should be the best upstream version for this.


why do you think this is the best version?

Thanks,

/mjt

--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key: rsa4096/61AD3D98ECDF2C8E  9D8B E14E 3F2A 9DD7 9199  28F1 61AD 3D98 
ECDF 2C8E
Old key: rsa2048/457CE0A0804465C5  6EE1 95D1 886E 8FFB 810D  4324 457C E0A0 
8044 65C5
Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

Processed: forcibly merging 1070971 1072315

[Debian Bug Tracking System]

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

> forcemerge 1070971 1072315
Bug #1070971 [puddletag] puddletag: Puddletag fails to start after upgrading 
python3-pyparsing to 3.1.2-1 (+ workaround)
Bug #1072315 [puddletag] puddletag 2.3.0-1
Severity set to 'grave' from 'normal'
Added tag(s) patch.
Merged 1070971 1072315
> thanks
Stopping processing here.

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

Bug#1071860: not fixed in 7.0-005-2 (was: Bug#1071860 closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#1071860: fixed in fis-gtm 7.0-005-

[Andreas Metzler]

Control: reopen 1071860

On 2024-06-22 Debian Bug Tracking System  wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:fis-gtm package:

> #1071860: fis-gtm: Searches for libgcrypt with libgcrypt-config

> It has been closed by Debian FTP Masters  
> (reply to Andreas Tille ).
[...]
>  fis-gtm (7.0-005-2) unstable; urgency=medium
>  .
>* Build-Depends: s/libgcrypt20-dev | //, pkgconf
>  Closes: #1071860
[...]

> From: Andreas Metzler 
> To: Debian Bug Tracking System 
> Subject: fis-gtm: Searches for libgcrypt with libgcrypt-config
> Message-ID: 
[...]
> fis-gtm relies on libgcrypt-config to locate libgcrypt. libgcrypt-config
> is scheduled for removal and will be dropped in libgcrypt 1.11. Please
> use pkg-config/pkgconf instead.

Hello,

This is unfixed, trying to rebuild fis-gtm (7.0-005-2) without
/usr/bin/libgcrypt-config results in:

make[1]: Entering directory '/tmp/fis-gtm-7.0-005'
dh_auto_configure -- -DCMAKE_INSTALL_PREFIX:PATH=/usr 
-DGTM_INSTALL_DIR=lib/x86_64-linux-gnu/fis-gtm/V7.0-005_x86_64 
-DCMAKE_BUILD_TYPE=Release
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
-DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DCMAKE_INSTALL_PREFIX:PATH=/usr 
-DGTM_INSTALL_DIR=lib/x86_64-linux-gnu/fis-gtm/V7.0-005_x86_64 
-DCMAKE_BUILD_TYPE=Release ..
-- The C compiler identification is GNU 13.3.0
-- The ASM compiler identification is GNU
-- Found assembler: /usr/lib/ccache/cc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/lib/ccache/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
--> OS = Linux / ARCH = x86_64
-- Bootstraping from pre-generated sources.
INFO: Using ssl.h /usr/include/openssl/ssl.h
CMake Error at CMakeLists.txt:529 (message):
  FATAL: libgcrypt-config not found (LIBGCRYPT_CONFIG_SCRIPT-NOTFOUND)
[...]

cu Andreas

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

Processed: not fixed in 7.0-005-2 (was: Bug#1071860 closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#1071860: fixed in fis-gtm 7.0-005-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen 1071860
Bug #1071860 {Done: Andreas Tille } [src:fis-gtm] fis-gtm: 
Searches for libgcrypt with libgcrypt-config
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions fis-gtm/7.0-005-2.

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

Bug#1074086: /usr/sbin/coldreboot is ineffectively diverted by bfh-container, molly-guard and progress-linux-container

[Helmut Grohne]

Package: kexec-tools
Version: 1:2.0.27-1.2
Severity: serious
User: helm...@debian.org
Usertags: dep17p3
Control: affects -1 + bfh-container molly-guard progress-linux-container
X-Debbugs-Cc: z...@debian.org

coldreboot is being moved from /bin to /usr/bin. Unfortunately,
bfh-container, molly-guard and progress-linux-container divert this
location causing problems.

I think we need the same (or similar) dance as with systemd-sysv. Each
of those packages needs to install mitigations and kexec-tools needs
versioned conflicts with unfixed versions of those.

Arguably, combining bfh-container or progress-linux-container with
kexec-tools is not a reasonable thing to do. In those cases, unversioned
conflicts may be applicable though they are not technically policy
compliant.

This bug serves as a migration blocker and helps apt-listbugs users with
not loosing their files.

Helmut

Processed: python3-proto-plus missing Breaks+Replaces with nanopb

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + nanopb
Bug #1074085 [python3-proto-plus] python3-proto-plus missing Breaks+Replaces 
with nanopb
Added indication that 1074085 affects nanopb

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

Processed: /usr/sbin/coldreboot is ineffectively diverted by bfh-container, molly-guard and progress-linux-container

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + bfh-container molly-guard progress-linux-container
Bug #1074086 [kexec-tools] /usr/sbin/coldreboot is ineffectively diverted by 
bfh-container, molly-guard and progress-linux-container
Added indication that 1074086 affects bfh-container, molly-guard, and 
progress-linux-container

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

Bug#1074085: python3-proto-plus missing Breaks+Replaces with nanopb

[Helmut Grohne]

Package: python3-proto-plus
Version: 1.23.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + nanopb

Hi,

we're almost done with the file conflict between python3-proto-plus and
nanopb. Thanks for taking the time to work on a proper solution. Now the
python3-proto-plus package still shares files with the nanopb package in
trixie and this breaks smooth upgrades. We really are taking over files
now. When you upgrade python3-proto-plus and have nanopb installed,
nanopb should be upgraded as well to avoid that file conflict. Thus
please add:

Breaks: nanopb (<< 0.4.8-2~)
Replaces: nanopb (<< 0.4.8-2~)

Helmut