date:20230819

Processing control commands:

> reopen -1
Bug #1047718 {Done: Gianfranco Costamagna } 
[liblld-16-dev] liblld-X-dev should probably depend on zlib1g-dev/libzstd-dev
'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 llvm-toolchain-16/1:16.0.6-11.
> severity -1 serious
Bug #1047718 [liblld-16-dev] liblld-X-dev should probably depend on 
zlib1g-dev/libzstd-dev
Severity set to 'serious' from 'normal'

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

Processed: found 1050031 in 4.1.5-2

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

> found 1050031 4.1.5-2
Bug #1050031 [src:openmpi] Needs a rebuild against new default gcc (13)
Marked as found in versions openmpi/4.1.5-2.
> thanks
Stopping processing here.

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

Processed: Reaffecting to src:openmpi which needs a rebuild

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

> reassign 1050031 src:openmpi
Bug #1050031 [src:coinor-bonmin] coinor-bonmin: FTBFS with /usr/bin/ld: cannot 
find -lgfortran
Bug reassigned from package 'src:coinor-bonmin' to 'src:openmpi'.
No longer marked as found in versions coinor-bonmin/1.8.9-1.
Ignoring request to alter fixed versions of bug #1050031 to the same values 
previously set
> affects 1050031 src:coinor-bonmin
Bug #1050031 [src:openmpi] coinor-bonmin: FTBFS with /usr/bin/ld: cannot find 
-lgfortran
Added indication that 1050031 affects src:coinor-bonmin
> retitle 1050031 Needs a rebuild against new default gcc (13)
Bug #1050031 [src:openmpi] coinor-bonmin: FTBFS with /usr/bin/ld: cannot find 
-lgfortran
Changed Bug title to 'Needs a rebuild against new default gcc (13)' from 
'coinor-bonmin: FTBFS with /usr/bin/ld: cannot find -lgfortran'.
> thanks
Stopping processing here.

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

Bug#1050031: Reaffecting to src:openmpi which needs a rebuild

2023-08-19 Thread Pierre Gruet


reassign 1050031 src:openmpi
affects 1050031 src:coinor-bonmin
retitle 1050031 Needs a rebuild against new default gcc (13)
thanks


Hi,

This build failure in coinor-bonmin is due to openmpi having been built 
against gcc-12 although unstable now uses gcc-13. I guess openmpi should 
have been included in some default-gcc transition or whatever, but it 
has not.


Building coinor-bonmin against a locally rebuilt openmpi solves the 
reported issue, so I guess a binNMU of openmpi is needed.


Cheers,

--
Pierre


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1041810: librsvg: CVE-2023-38633

On Sat, 19 Aug 2023 at 18:57:29 +0200, Salvatore Bonaccorso wrote:
> If you are happy with the results and coverage from unstable, would
> you be open to prepare/finalize next the respective updates for
> bookworm-security and bullseye-security?

I already had them in what I believe to be an uploadable state, so I've
uploaded them to security-master. Please do whatever testing you feel is
appropriate and approve or reject.

librsvg_2.54.7+dfsg-1~deb12u1 is a trivial backport of what's in unstable,

(diff vs. unstable below, debdiff vs. bookworm attached). I've been
using it on a bookworm GNOME desktop for the last few weeks with no
apparent regressions, and I haven't seen any regression reports from
testing/unstable users either.

librsvg_2.50.3+dfsg-1+deb11u1 is

(debdiff vs. bullseye attached). I don't have bullseye on actual hardware
any more, so this has only been tested on a GNOME VM.

smcv

diff --git a/debian/changelog b/debian/changelog
index d58c430b1..825f50e1e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+librsvg (2.54.7+dfsg-1~deb12u1) bookworm-security; urgency=medium
+
+  * Team upload
+  * Rebuild for bookworm-security
+
+ -- Simon McVittie   Sun, 30 Jul 2023 17:13:13 +0100
+
 librsvg (2.54.7+dfsg-1) unstable; urgency=high

   * Team upload
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 4ed071a96..098b7f22b 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,7 +1,7 @@
 [DEFAULT]
 pristine-tar = True
-debian-branch = debian/master
-upstream-branch = upstream/latest
+debian-branch = debian/bookworm
+upstream-branch = upstream/2.54.x

 [buildpackage]
 sign-tags = True

librsvg_2.50.3+dfsg-1+deb11u1.debdiff.gz
Description: application/gzip

librsvg_2.54.7+dfsg-1~deb12u1.debdiff.gz
Description: application/gzip

Bug#1050027: closed by Debian FTP Masters (reply to Julien Puydt ) (Bug#1050027: fixed in mathcomp-analysis 0.6.4-2)

2023-08-19 Thread julien . puydt

Le samedi 19 août 2023 à 20:58 +0200, Helmut Grohne a écrit :
> Control: reopen -1
> Control: found -1 mathcomp-analysis/0.6.4-2
> 
> On Sat, Aug 19, 2023 at 05:33:11PM +, Debian Bug Tracking System
> wrote:
> > It has been closed by Debian FTP Masters
> >  (reply to Julien Puydt
> > ).
> 
> I'm sorry. Adding Breaks is necessary but insufficient. You also need
> Replaces.

What is in libcoq-mathcomp-analysis << 0.6.4 is now in two packages:
- libcoq-mathcomp-classical (a small part) ;
- libcoq-mathcomp-analysis (the most part -- and that binary package
depends on libcoq-mathcomp-classical with a strong version constraint).

The problem you pointed was that a user with an old libcoq-mathcomp-
analysis asking to install libcoq-mathcomp-classical would lead dpkg to
a conflict of files.

 The breaks I added prevents that, and in fact a user with an old
licoq-mathcomp-analysis should have no issue in those situations:

(1) try to install a newer libcoq-mathcomp-classical -- with my Breaks
dpkg will refuse because of the conflict which is a sane answer :
system not broken, features not broken ;

(2) try to upgrade - dpkg will see the new libcoq-mathcomp-analysis
needs libcoq-mathcomp-classical and that it breaks the outgoing libcoq-
mathcomp-analysis, but it's able to handle the situation ;

If I declare libcoq-mathcomp-classical Replaces libcoq-mathcomp-
analysis << 0.6.4, then in situation (1), dpkg will install libcoq-
mathcomp-classical and drop that old libcoq-mathcomp-analysis. The
system is not broken, but the user just lost most of the functionality,
and that is bad.

So I think the change I made is sound.

Do you have another problem in mind? Or a better fix?

Cheers,

J.Puydt

Bug#1050028: marked as done (rust-tokio-rustls: recent upgrade breaks reverse dependencies: keep from testing till resolved)

Your message dated Sat, 19 Aug 2023 19:12:48 +
with message-id 
and subject line Bug#1050028: fixed in rust-rustls 0.21.6-3
has caused the Debian Bug report #1050028,
regarding rust-tokio-rustls: recent upgrade breaks reverse dependencies: keep 
from testing till resolved
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.)


-- 
1050028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-tokio-rustls
Version: 0.24.1-1
Severity: serious
Justification: reverse dependencies

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: affects -1 rust-hyper-rustls

Breaks reverse dependencies: keep from testing till resolved.

See bug#1049977 for related discussion.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTfcg0ACgkQLHwxRsGg
ASFNUxAAj105Of/nLfE9QqYVaJY6xXpSw5P1XO0a9BTC6L0WnFjZXkLP2HJONUXi
mHMQ3nXrdKVAB4SfCB674NZXs4kR6bhsJeFwkjMx/WEMxv83GRBEfCe2d2YVJjJq
O+mcDQLxiSnzkOsixvNboAGeeBBwwz02nSvcYFhH8Kj6zNHVHhtitjeG13atpqGd
/3uZ7nVl8vwAWhf3QzySgFfhWfdkCw3ltZR3adb14NNLFKcQnht5XEqiwoiZTqkN
ipi0OI+cfA4EWfzLOJq0Ph9cbRfD3BJTUfCVfNFe/+xUEIDtViYeJeWO6ROvxZ8i
8DD1FsZqJFIQLn2Zg6nQ41sShgmV08hM25BLtznTxcN9i3X+EtnDqgGePkbvzqb6
abQuKvuyx1zWW6RiN/XwlWCGtLnWYfpe3pchlkMEp/hjEE00BNrN484LWRjUcnVo
5zUa5PBKfFleZMs9zB+SFrcz+S2RaEn1Jj8DHjzl4k35rWBEy4FfEZT9X4fkERxA
mLVGlUaYlhe59oOajkmsVcEOAN4aHlXiVFOUUiV5jPH7uzbPy0Y74fG81PCFwbUa
Dg1mtCEOo7zqymdSOV+dGOI6YTDSew6jNhzNEe0GjHRSzCTfN1hr3VoWwztQEVZF
p18AmR/IijkhU3hStZAUtPt3s8nqc9MXZyKzUMfR0RNKvv4cKZw=
=YGQr
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-rustls
Source-Version: 0.21.6-3
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-rustls package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Aug 2023 19:28:42 +0200
Source: rust-rustls
Binary: librust-rustls-dev
Architecture: source all
Version: 0.21.6-3
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Description:
 librust-rustls-dev - modern TLS library written in Rust - Rust source code
Closes: 1047861 1049977 1050028
Changes:
 rust-rustls (0.21.6-3) unstable; urgency=medium
 .
   * re-release targeted unstable;
 closes: bug#1049977, #1050028, thanks to Peter Green
   * update DEP-3 patch headers
   * update dh-cargo fork;
 closes: bug#1047861, thanks to Lucas Nussbaum
Checksums-Sha1:
 3bf588dd5972b5719354bb32e77dd01cde2b4940 3462 rust-rustls_0.21.6-3.dsc
 a6e8192522e6edeb8d31dea3376a49fe26ed74d4 23356 
rust-rustls_0.21.6-3.debian.tar.xz
 e8b10827b6ee75906b139bf8fd0c928791781f27 346388 
librust-rustls-dev_0.21.6-3_all.deb
 4f6913a4c138f76ee53b0b85b58198daaac67bdd 10491 
rust-rustls_0.21.6-3_amd64.buildinfo
Checksums-Sha256:
 25942325c53ad3c0b50f69cfe775207787c008e1a13d4bf1e0950b57c1526250 3462 
rust-rustls_0.21.6-3.dsc
 4ac8ff763099141336dd287d1694a40298b5c6519c7d80eeacd74ad9c26947e0 23356 
rust-rustls_0.21.6-3.debian.tar.xz
 a477c33d5419a096859e2230122582d5b957c83774f19eb98e634b6a3a8c936a 346388 
librust-rustls-dev_0.21.6-3_all.deb
 a4dc33e3dd310bd2b8ec07500c37744deba15f6874c945a310f62024e5c4b65c 10491 
rust-rustls_0.21.6-3_amd64.buildinfo
Files:
 f8f9b6048fe94e6617b5050b81fa7d98 3462 rust optional rust-rustls_0.21.6-3.dsc
 ad14eee2f58306c78fc1061831f91566 23356 rust optional 
rust-rustls_0.21.6-3.debian.tar.xz
 ffe42a24f879e9f73f8fe112e2268a64 346388 rust optional 
librust-rustls-dev_0.21.6-3_all.deb
 0619d90fb4451270c87d6640c876d722 10491 rust optional 
rust-rustls_0.21.6-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTg/OEACgkQLHwxRsGg
ASGnUBAAilR64Axv6QrOwftYgoBnAkqnJGssMYHN8CvFYei/JIEzfGLBFG2fnzdx
tzAwA0HSXuil4jCS4koRiXNyDygmC/h1ppGjFkSjRs7f5fT6KGHEfHOWXG9aU7SK
JMT1YzsN6G+j1Ua6rpMQ9mQMLelker829ZxnDQy32uP2gt/MrpsLbMNX5H4E+7n+

Bug#1050028: marked as done (rust-tokio-rustls: recent upgrade breaks reverse dependencies: keep from testing till resolved)

Your message dated Sat, 19 Aug 2023 19:12:32 +
with message-id 
and subject line Bug#1050028: fixed in rust-hyper-rustls 0.24.1-2
has caused the Debian Bug report #1050028,
regarding rust-tokio-rustls: recent upgrade breaks reverse dependencies: keep 
from testing till resolved
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.)


-- 
1050028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-tokio-rustls
Version: 0.24.1-1
Severity: serious
Justification: reverse dependencies

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Control: affects -1 rust-hyper-rustls

Breaks reverse dependencies: keep from testing till resolved.

See bug#1049977 for related discussion.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTfcg0ACgkQLHwxRsGg
ASFNUxAAj105Of/nLfE9QqYVaJY6xXpSw5P1XO0a9BTC6L0WnFjZXkLP2HJONUXi
mHMQ3nXrdKVAB4SfCB674NZXs4kR6bhsJeFwkjMx/WEMxv83GRBEfCe2d2YVJjJq
O+mcDQLxiSnzkOsixvNboAGeeBBwwz02nSvcYFhH8Kj6zNHVHhtitjeG13atpqGd
/3uZ7nVl8vwAWhf3QzySgFfhWfdkCw3ltZR3adb14NNLFKcQnht5XEqiwoiZTqkN
ipi0OI+cfA4EWfzLOJq0Ph9cbRfD3BJTUfCVfNFe/+xUEIDtViYeJeWO6ROvxZ8i
8DD1FsZqJFIQLn2Zg6nQ41sShgmV08hM25BLtznTxcN9i3X+EtnDqgGePkbvzqb6
abQuKvuyx1zWW6RiN/XwlWCGtLnWYfpe3pchlkMEp/hjEE00BNrN484LWRjUcnVo
5zUa5PBKfFleZMs9zB+SFrcz+S2RaEn1Jj8DHjzl4k35rWBEy4FfEZT9X4fkERxA
mLVGlUaYlhe59oOajkmsVcEOAN4aHlXiVFOUUiV5jPH7uzbPy0Y74fG81PCFwbUa
Dg1mtCEOo7zqymdSOV+dGOI6YTDSew6jNhzNEe0GjHRSzCTfN1hr3VoWwztQEVZF
p18AmR/IijkhU3hStZAUtPt3s8nqc9MXZyKzUMfR0RNKvv4cKZw=
=YGQr
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-hyper-rustls
Source-Version: 0.24.1-2
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-hyper-rustls package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Aug 2023 19:35:39 +0200
Source: rust-hyper-rustls
Architecture: source
Version: 0.24.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1049977 1050028
Changes:
 rust-hyper-rustls (0.24.1-2) unstable; urgency=medium
 .
   * re-release targeted unstable;
 closes: bug#1049977, #1050028, thanks to Peter Green
Checksums-Sha1:
 ec1338c6fcd3cce163de0cf55baeed6f23427eff 3586 rust-hyper-rustls_0.24.1-2.dsc
 a7f50896c0b434863a70c7f71c53f7ebd6ba84a0 13472 
rust-hyper-rustls_0.24.1-2.debian.tar.xz
 292e2f84d63af63e16e4341cd7019f7438df293e 13046 
rust-hyper-rustls_0.24.1-2_amd64.buildinfo
Checksums-Sha256:
 08df83f0dcea8374ebb8f2cc1ffb6caad6bb4b7e7afc21f481a65bc594cc67a7 3586 
rust-hyper-rustls_0.24.1-2.dsc
 f54e78e5a9077253c3f274368bddf01b6631ef7e25f12387024fc3ca811e7788 13472 
rust-hyper-rustls_0.24.1-2.debian.tar.xz
 18257d21a6ff27b82c0401093fd6d04b9979b2214bab1c2c242058186b6e470d 13046 
rust-hyper-rustls_0.24.1-2_amd64.buildinfo
Files:
 03bc6b57cdb38c582659217dd107b49d 3586 rust optional 
rust-hyper-rustls_0.24.1-2.dsc
 159721cef60df08dcf32e0dd5574f302 13472 rust optional 
rust-hyper-rustls_0.24.1-2.debian.tar.xz
 e3bb99854d4785a97dcf5e1b88b3ffee 13046 rust optional 
rust-hyper-rustls_0.24.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTg/dgACgkQLHwxRsGg
ASGu/w//TN5OIengwpEnOcgvV9f/2bIK8bWjZSDKeSTRtYtN1L/kQn9FZ3Ke/dhb
RGjiLfva4QplBfEXnbIX1uP+uogtJjCyq4CJSXpv8//C3klzmpvdxZePlx0lfhu/
04scg5T4OboqCXgwSLDrhms6kGTE/0LoqOpG0g/4Oqw2bI2QoSvuId4MnsjN6qhX
L7AiQK5ZlpjToA2zWqvFf9/8RGp4xcIFTun65kAPFOC9PxEMMG7mys6pGsAZzcR5
5GOzPlMShh6KziL2DruWU2QdgC44QLZc45pLS8RmDvu04BSqharFBYavxhDW9uq5
mXRdFhZMxPgFqF0UHXT2LyuClbV4fCfnn5jiPZSedg5epssPYHKwRtyekyviCdD7
fFjiqlTiYzeXk/jNik7LjrJux25PRxSe2XdaTKbyS3/aZzbdr+SprIROf+UZu6al
TJsLJ0OUpRxVxBR7Z37x6w6knIXWoLvhSlfwk7MvJpnuVGapSBkVdcj6HxBwdJ3U
2hd6FztVQIfQ9EzJwmMKpo6yLzXYJ5VVqe7Y4kIHN8pUbr40zLP/CitBwasD63+k
q4fsRuo6afEPthY+dX7zcWXyKVDoIWNrpWvRIAZwqueKinCTNePM5HUD/I6nu7U5

Bug#1049977: marked as done (rust-hyper-rustls - please update to match new rust-tokio-rustls)

Your message dated Sat, 19 Aug 2023 19:12:48 +
with message-id 
and subject line Bug#1049977: fixed in rust-rustls 0.21.6-3
has caused the Debian Bug report #1049977,
regarding rust-hyper-rustls - please update to match new rust-tokio-rustls
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.)


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

Package: rust-hyper-rustls
Version: 0.23.2-4
Severity: serious

I just updated tokio-rustls to 0.24.1, hyper-rustls needs updating to 0.24.1
to match.
--- End Message ---
--- Begin Message ---
Source: rust-rustls
Source-Version: 0.21.6-3
Done: Jonas Smedegaard 

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-rustls package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Aug 2023 19:28:42 +0200
Source: rust-rustls
Binary: librust-rustls-dev
Architecture: source all
Version: 0.21.6-3
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Description:
 librust-rustls-dev - modern TLS library written in Rust - Rust source code
Closes: 1047861 1049977 1050028
Changes:
 rust-rustls (0.21.6-3) unstable; urgency=medium
 .
   * re-release targeted unstable;
 closes: bug#1049977, #1050028, thanks to Peter Green
   * update DEP-3 patch headers
   * update dh-cargo fork;
 closes: bug#1047861, thanks to Lucas Nussbaum
Checksums-Sha1:
 3bf588dd5972b5719354bb32e77dd01cde2b4940 3462 rust-rustls_0.21.6-3.dsc
 a6e8192522e6edeb8d31dea3376a49fe26ed74d4 23356 
rust-rustls_0.21.6-3.debian.tar.xz
 e8b10827b6ee75906b139bf8fd0c928791781f27 346388 
librust-rustls-dev_0.21.6-3_all.deb
 4f6913a4c138f76ee53b0b85b58198daaac67bdd 10491 
rust-rustls_0.21.6-3_amd64.buildinfo
Checksums-Sha256:
 25942325c53ad3c0b50f69cfe775207787c008e1a13d4bf1e0950b57c1526250 3462 
rust-rustls_0.21.6-3.dsc
 4ac8ff763099141336dd287d1694a40298b5c6519c7d80eeacd74ad9c26947e0 23356 
rust-rustls_0.21.6-3.debian.tar.xz
 a477c33d5419a096859e2230122582d5b957c83774f19eb98e634b6a3a8c936a 346388 
librust-rustls-dev_0.21.6-3_all.deb
 a4dc33e3dd310bd2b8ec07500c37744deba15f6874c945a310f62024e5c4b65c 10491 
rust-rustls_0.21.6-3_amd64.buildinfo
Files:
 f8f9b6048fe94e6617b5050b81fa7d98 3462 rust optional rust-rustls_0.21.6-3.dsc
 ad14eee2f58306c78fc1061831f91566 23356 rust optional 
rust-rustls_0.21.6-3.debian.tar.xz
 ffe42a24f879e9f73f8fe112e2268a64 346388 rust optional 
librust-rustls-dev_0.21.6-3_all.deb
 0619d90fb4451270c87d6640c876d722 10491 rust optional 
rust-rustls_0.21.6-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTg/OEACgkQLHwxRsGg
ASGnUBAAilR64Axv6QrOwftYgoBnAkqnJGssMYHN8CvFYei/JIEzfGLBFG2fnzdx
tzAwA0HSXuil4jCS4koRiXNyDygmC/h1ppGjFkSjRs7f5fT6KGHEfHOWXG9aU7SK
JMT1YzsN6G+j1Ua6rpMQ9mQMLelker829ZxnDQy32uP2gt/MrpsLbMNX5H4E+7n+
2UNyRA7sRA1sdlDcvuf6Ppa262peA1Vx4ZGmdKRmM2jjAcNtLcTi6WccUgc4Hu6l
yF8VYeyFyci0VTfQUhlN9kUueuRI6J0UsN/rJvBC/UHUilDmBot6y5qYBFu75wwL
Aubjz5c+xjjhVVhNQuEPpmYKv/nOPBeKgLOPkVhrL+HGO9CEjO9ZMJcol5hp8fQu
jqpaa2XzF5Q2XME57y2qClWvn/I3OCA8EUMaLjNJQ5BObq7dOOvKpfeYSh3ELMYm
GpNfBBtnzkVagDXB5YzLHL1KTb69w6JQdineXcCPjlllkzzSD4JJ0VLIECjuNA/E
RreyKwUdo4eTnm69PKThrb7TmKgnQ8600DRW8nq6i7McHDJUzDoVF8fL0Zitq/Dk
FwOS1zAnhbgxkmtntYcJsGT8lcqp3Wc/FodwfQ4cvvRyvUe9WI1ze8l9ggKDbsLn
TPAoYnisMcrFH3iRItnrMh/2ryV9J7oAVIkwNAitL6UCh8S2IOY=
=V4Il
-END PGP SIGNATURE End Message ---

Bug#1049977: marked as done (rust-hyper-rustls - please update to match new rust-tokio-rustls)

Your message dated Sat, 19 Aug 2023 19:12:32 +
with message-id 
and subject line Bug#1049977: fixed in rust-hyper-rustls 0.24.1-2
has caused the Debian Bug report #1049977,
regarding rust-hyper-rustls - please update to match new rust-tokio-rustls
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.)


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

Package: rust-hyper-rustls
Version: 0.23.2-4
Severity: serious

I just updated tokio-rustls to 0.24.1, hyper-rustls needs updating to 0.24.1
to match.
--- End Message ---
--- Begin Message ---
Source: rust-hyper-rustls
Source-Version: 0.24.1-2
Done: Jonas Smedegaard 

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-hyper-rustls package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Aug 2023 19:35:39 +0200
Source: rust-hyper-rustls
Architecture: source
Version: 0.24.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1049977 1050028
Changes:
 rust-hyper-rustls (0.24.1-2) unstable; urgency=medium
 .
   * re-release targeted unstable;
 closes: bug#1049977, #1050028, thanks to Peter Green
Checksums-Sha1:
 ec1338c6fcd3cce163de0cf55baeed6f23427eff 3586 rust-hyper-rustls_0.24.1-2.dsc
 a7f50896c0b434863a70c7f71c53f7ebd6ba84a0 13472 
rust-hyper-rustls_0.24.1-2.debian.tar.xz
 292e2f84d63af63e16e4341cd7019f7438df293e 13046 
rust-hyper-rustls_0.24.1-2_amd64.buildinfo
Checksums-Sha256:
 08df83f0dcea8374ebb8f2cc1ffb6caad6bb4b7e7afc21f481a65bc594cc67a7 3586 
rust-hyper-rustls_0.24.1-2.dsc
 f54e78e5a9077253c3f274368bddf01b6631ef7e25f12387024fc3ca811e7788 13472 
rust-hyper-rustls_0.24.1-2.debian.tar.xz
 18257d21a6ff27b82c0401093fd6d04b9979b2214bab1c2c242058186b6e470d 13046 
rust-hyper-rustls_0.24.1-2_amd64.buildinfo
Files:
 03bc6b57cdb38c582659217dd107b49d 3586 rust optional 
rust-hyper-rustls_0.24.1-2.dsc
 159721cef60df08dcf32e0dd5574f302 13472 rust optional 
rust-hyper-rustls_0.24.1-2.debian.tar.xz
 e3bb99854d4785a97dcf5e1b88b3ffee 13046 rust optional 
rust-hyper-rustls_0.24.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTg/dgACgkQLHwxRsGg
ASGu/w//TN5OIengwpEnOcgvV9f/2bIK8bWjZSDKeSTRtYtN1L/kQn9FZ3Ke/dhb
RGjiLfva4QplBfEXnbIX1uP+uogtJjCyq4CJSXpv8//C3klzmpvdxZePlx0lfhu/
04scg5T4OboqCXgwSLDrhms6kGTE/0LoqOpG0g/4Oqw2bI2QoSvuId4MnsjN6qhX
L7AiQK5ZlpjToA2zWqvFf9/8RGp4xcIFTun65kAPFOC9PxEMMG7mys6pGsAZzcR5
5GOzPlMShh6KziL2DruWU2QdgC44QLZc45pLS8RmDvu04BSqharFBYavxhDW9uq5
mXRdFhZMxPgFqF0UHXT2LyuClbV4fCfnn5jiPZSedg5epssPYHKwRtyekyviCdD7
fFjiqlTiYzeXk/jNik7LjrJux25PRxSe2XdaTKbyS3/aZzbdr+SprIROf+UZu6al
TJsLJ0OUpRxVxBR7Z37x6w6knIXWoLvhSlfwk7MvJpnuVGapSBkVdcj6HxBwdJ3U
2hd6FztVQIfQ9EzJwmMKpo6yLzXYJ5VVqe7Y4kIHN8pUbr40zLP/CitBwasD63+k
q4fsRuo6afEPthY+dX7zcWXyKVDoIWNrpWvRIAZwqueKinCTNePM5HUD/I6nu7U5
BaxkYXIRZw0i5b2F0LB6QjWsilMJdiV3g5DcIqRIvCjEHDprcQs=
=4bmt
-END PGP SIGNATURE End Message ---

Bug#1037667: marked as done (freeorion: ftbfs with GCC-13)

Your message dated Sat, 19 Aug 2023 19:00:42 +
with message-id 
and subject line Bug#1037667: fixed in freeorion 0.5-1
has caused the Debian Bug report #1037667,
regarding freeorion: ftbfs with GCC-13
to be marked as done.

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

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


-- 
1037667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:freeorion
Version: 0.4.10.2-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/freeorion_0.4.10.2-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
/usr/include/c++/13/bits/std_function.h:469:33: note:   no known conversion for 
argument 1 from ‘ValueRef::ComplexVariable::Eval(const 
ScriptingContext&) const::’ to ‘const 
std::function&(const Empire&)>&’
  469 |   operator=(const function& __x)
  | ^~~
/usr/include/c++/13/bits/std_function.h:487:7: note: candidate: 
‘std::function<_Res(_ArgTypes ...)>& std::function<_Res(_ArgTypes 
...)>::operator=(std::function<_Res(_ArgTypes ...)>&&) [with _Res = const 
std::map&; _ArgTypes = {const Empire&}]’
  487 |   operator=(function&& __x) noexcept
  |   ^~~~
/usr/include/c++/13/bits/std_function.h:487:28: note:   no known conversion for 
argument 1 from ‘ValueRef::ComplexVariable::Eval(const 
ScriptingContext&) const::’ to ‘std::function&(const Empire&)>&&’
  487 |   operator=(function&& __x) noexcept
  | ~~~^~~
/usr/include/c++/13/bits/std_function.h:501:7: note: candidate: 
‘std::function<_Res(_ArgTypes ...)>& std::function<_Res(_ArgTypes 
...)>::operator=(std::nullptr_t) [with _Res = const std::map&; 
_ArgTypes = {const Empire&}; std::nullptr_t = std::nullptr_t]’
  501 |   operator=(nullptr_t) noexcept
  |   ^~~~
/usr/include/c++/13/bits/std_function.h:501:17: note:   no known conversion for 
argument 1 from ‘ValueRef::ComplexVariable::Eval(const 
ScriptingContext&) const::’ to ‘std::nullptr_t’
  501 |   operator=(nullptr_t) noexcept
  | ^
/<>/universe/ValueRefs.cpp:1813:125: error: no match for 
‘operator=’ (operand types are ‘std::function&(const 
Empire&)>’ and ‘ValueRef::ComplexVariable::Eval(const 
ScriptingContext&) const::’)
 1813 | empire_property = [](const Empire& empire){ return 
GetSupplyManager().PropagatedSupplyDistances(empire.EmpireID()); };
  | 
^
/usr/include/c++/13/bits/std_function.h:531:9: note: candidate: ‘template std::function<_Res(_ArgTypes 
...)>::_Requires::_Callable<_Functor>, 
std::function<_Res(_ArgTypes ...)>&> std::function<_Res(_ArgTypes 
...)>::operator=(_Functor&&) [with _Res = const std::map&; 
_ArgTypes = {const Empire&}]’
  531 | operator=(_Functor&& __f)
  | ^~~~
/usr/include/c++/13/bits/std_function.h:531:9: note:   template argument 
deduction/substitution failed:
/usr/include/c++/13/bits/std_function.h:541:9: note: candidate: ‘template std::function<_Res(_ArgTypes ...)>& std::function<_Res(_ArgTypes 
...)>::operator=(std::reference_wrapper<_Functor>) [with _Res = const 
std::map&; _ArgTypes = {const Empire&}]’
  541 | operator=(reference_wrapper<_Functor> __f) noexcept
  | ^~~~
/usr/include/c++/13/bits/std_function.h:541:9: note:   template argument 
deduction/substitution failed:

Bug#1050027: closed by Debian FTP Masters (reply to Julien Puydt ) (Bug#1050027: fixed in mathcomp-analysis 0.6.4-2)

2023-08-19 Thread Helmut Grohne

Control: reopen -1
Control: found -1 mathcomp-analysis/0.6.4-2

On Sat, Aug 19, 2023 at 05:33:11PM +, Debian Bug Tracking System wrote:
> It has been closed by Debian FTP Masters  
> (reply to Julien Puydt ).

I'm sorry. Adding Breaks is necessary but insufficient. You also need
Replaces.

Helmut

Processed: Re: Bug#1050027 closed by Debian FTP Masters (reply to Julien Puydt ) (Bug#1050027: fixed in mathcomp-analysis 0.6.4-2)

Processing control commands:

> reopen -1
Bug #1050027 {Done: Julien Puydt } 
[libcoq-mathcomp-classical] libcoq-mathcomp-classical: undeclared file conflict 
with libcoq-mathcomp-analysis/bookworm+trixie
'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 mathcomp-analysis/0.6.4-2.
> found -1 mathcomp-analysis/0.6.4-2
Bug #1050027 [libcoq-mathcomp-classical] libcoq-mathcomp-classical: undeclared 
file conflict with libcoq-mathcomp-analysis/bookworm+trixie
The source mathcomp-analysis and version 0.6.4-2 do not appear to match any 
binary packages
Marked as found in versions mathcomp-analysis/0.6.4-2.

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

Bug#1033907: numba crashes on non-x86

2023-08-19 Thread Diane Trout

On Sat, 2023-08-19 at 18:21 +0100, Rebecca N. Palmer wrote:
> numba also crashes on mips64el, mipsel and armhf (and s390x but that
> was 
> already known; not amd64, i386 or ppc64el).  However, I agree that
> arm64 
> is a good place to start trying to fix this, given how common it is.
> 

Also given how popular Apple arm chips are upstream has some motivation
to fix numba on arm64.

Bug#1050096: Maybe related to bug 1049350

2023-08-19 Thread Michael Rasmussen

Hi,

If I apply the fix from bug 1049350 then it builds on 6.4.0-3 but will
no longer build on 6.4.0-2

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
https://keys.openpgp.org/vks/v1/by-fingerprint/A1306C5094B5E31B7721A3A66F4844C7CA7501AA
mir  datanom  net
https://keys.openpgp.org/vks/v1/by-fingerprint/0C14CD9479667E848770C8F98417B6C5E1BB093F
mir  miras  org
https://keys.openpgp.org/vks/v1/by-fingerprint/5F71405B571CB8EE2A414A4FC77C11E049A06E66
--

'During times of universal deceit, telling the truth becomes a
revolutionary act.' -George Orwell

/usr/games/fortune -es says:
A prig is a fellow who is always making you a present of his opinions.
-- George Eliot


pgpHksxSnfyej.pgp
Description: OpenPGP digital signature

Bug#1049977: rust-hyper-rustls - please update to match new rust-tokio-rustls

2023-08-19 Thread Jonas Smedegaard

Quoting Jeremy Bícha (2023-08-19 19:56:29)
> In this case, britney noticed an increase in uninstallability which
> would also have prevented the migration of rust-tokio-rustls to
> Testing.
> 
> https://tracker.debian.org/pkg/rust-tokio-rustls

Ah, right - I forgot about those tests.

So I was wrong that it would have a real risk in this case of wrecking
havoc in testing if only a severe bugreport was filed against this
package.

My argument stands, however, that it is the wrong package to file that
severe bugreport against.

 - 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#1049977: rust-hyper-rustls - please update to match new rust-tokio-rustls

In this case, britney noticed an increase in uninstallability which
would also have prevented the migration of rust-tokio-rustls to
Testing.

https://tracker.debian.org/pkg/rust-tokio-rustls

Thank you for the quick fix though!

Jeremy Bícha

Bug#1049977: rust-hyper-rustls - please update to match new rust-tokio-rustls

2023-08-19 Thread Jonas Smedegaard

Hi Jeremy,

Quoting Jeremy Bícha (2023-08-19 17:45:20)
> I am bumping the severity since rust-hyper-rustls fails to build from
> source in Unstable. This is true regardless of whether this situation
> should have been coordinated better.

It is but academic now that I have uploaded a fix for this, but I
disagree with your raising severity:

This package is not broken *in itself* but is instead *affected* by
breakage in rust-tokio-rustls.  The difference is not merely nitpicking
but has an effect on whether this package can migrate or not to testing:
Since this package is not broken, it is not problematic to let it
migrate to testing, but if rust-tokio-rustls had not had a severe bug
reported against it (and Peter had not been so quick at convincing me to
release a fix this soon) then it would have migrated to testing and
caused breakage there as well.

 - 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#1050097: scrcpy: fails to build from source on arch:indep

2023-08-19 Thread Gianfranco Costamagna


Package: scrcpy
Version: 1.25-1
Severity: serious
Tags: patch


Dear Maintainer,

For some reasons now the package FTBFS due to missing dx java tool.
I don't know if dalvik-exchange should be pulled in by java automatically, or 
an external additional dependency is needed.
   dh_auto_test -a
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 
MESON_TESTTHREADS=3 meson test
No tests defined.
   create-stamp debian/debhelper-build-stamp
dh build-indep --buildsystem=makefile
   dh_update_autotools_config -i -O--buildsystem=makefile
   dh_autoreconf -i -O--buildsystem=makefile
   dh_auto_configure -i -O--buildsystem=makefile
   debian/rules override_dh_auto_build-indep
make[2]: Entering directory '/build/scrcpy-1.25'
BUILD_DIR=build_manual ANDROID_PLATFORM=23 ANDROID_BUILD_TOOLS=debian 
server/build_without_gradle.sh
Platform: android-23
Build-tools: debian
Build dir: /build/scrcpy-1.25/build_manual
Generating java from aidl...
Compiling java sources...
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
Dexing...
server/build_without_gradle.sh: line 62: 
/usr/lib/android-sdk/build-tools/debian/dx: No such file or directory
make[2]: *** [debian/rules:41: override_dh_auto_build-indep] Error 127
make[2]: Leaving directory '/build/scrcpy-1.25'
make[1]: *** [debian/rules:22: build] Error 2
make[1]: Leaving directory '/build/scrcpy-1.25'
make: *** [debian/rules:18: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


Adding the dependency works

Thanks for considering the patch.

diff -Nru scrcpy-1.25/debian/control scrcpy-1.25/debian/control
--- scrcpy-1.25/debian/control  2023-01-20 11:28:52.0 +0100
+++ scrcpy-1.25/debian/control  2023-08-19 19:38:24.0 +0200
@@ -16,6 +16,7 @@
  android-sdk,
  android-sdk-platform-23,
  default-jdk,
+ dalvik-exchange,
  unzip,
  zip,
 Rules-Requires-Root: no

Bug#1049438: marked as done (r-cran-rgdal: autopkgtest needs update for new version of r-cran-sp)

Your message dated Sat, 19 Aug 2023 17:35:50 +
with message-id 
and subject line Bug#1049438: fixed in r-cran-sp 1:2.0-0+dfsg-2
has caused the Debian Bug report #1049438,
regarding r-cran-rgdal: autopkgtest needs update for new version of r-cran-sp
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.)


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

Source: r-cran-rgdal
Version: 1.6-7+dfsg-1
Severity: serious
X-Debbugs-CC: r-cran...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:r-cran-sp

Dear maintainer(s),

With a recent upload of r-cran-sp the autopkgtest of r-cran-rgdal fails 
in testing when that autopkgtest is run with the binary packages of 
r-cran-sp from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
r-cran-sp  from testing1:2.0-0+dfsg-1
r-cran-rgdal   from testing1.6-7+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of r-cran-sp to 
testing [1]. Of course, r-cran-sp shouldn't just break your autopkgtest 
(or even worse, your package), but your package needs to update to the 
new situation (or you have to help r-cran-sp maintainers to fix the 
issue in their package).


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from r-cran-sp should really 
add a versioned Breaks on the unfixed version of (one of your) 
package(s). Note: the Breaks is nice even if the issue is only in the 
autopkgtest as it helps the migration software to figure out the right 
versions to combine in the tests.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=r-cran-sp

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-rgdal/36836475/log.gz

 44s BEGIN TEST test_enforce_xy.R
 44s  44s R version 4.3.1 (2023-06-16) -- "Beagle Scouts"
 44s Copyright (C) 2023 The R Foundation for Statistical Computing
 44s Platform: x86_64-pc-linux-gnu (64-bit)
 44s  44s R is free software and comes with ABSOLUTELY NO WARRANTY.
 44s You are welcome to redistribute it under certain conditions.
 44s Type 'license()' or 'licence()' for distribution details.
 44s  44s R is a collaborative project with many contributors.
 44s Type 'contributors()' for more information and
 44s 'citation()' on how to cite R or R packages in publications.
 44s  44s Type 'demo()' for some demos, 'help()' for on-line help, or
 44s 'help.start()' for an HTML browser interface to help.
 44s Type 'q()' to quit R.
 44s  44s > suppressPackageStartupMessages(library(rgdal))
 44s > set_thin_PROJ6_warnings(TRUE)
 44s > if (new_proj_and_gdal()) {
 44s + get_enforce_xy()
 44s + x0 <- showSRID("EPSG:4326", multiline=TRUE, EPSG_to_init=FALSE)
 44s + cat(x0, "\n")
 44s + set_enforce_xy(FALSE)
 44s + x1 <- showSRID("EPSG:4326", multiline=TRUE, EPSG_to_init=FALSE)
 44s + cat(x1, "\n")
 44s + set_enforce_xy(TRUE)
 44s + x2 <- showSRID("EPSG:4326", multiline=TRUE, EPSG_to_init=FALSE)
 44s + cat(x2, "\n")
 44s + get_enforce_xy()
 44s + y0 <- showSRID("EPSG:4326", multiline=TRUE, EPSG_to_init=FALSE, 
prefer_proj=TRUE)

 44s + cat(y0, "\n")
 44s + showSRID("EPSG:4326", format="PROJ", EPSG_to_init=FALSE, 
prefer_proj=TRUE)

 44s + set_enforce_xy(FALSE)
 44s + y1 <- showSRID("EPSG:4326", multiline=TRUE, EPSG_to_init=FALSE, 
prefer_proj=TRUE)

 44s + cat(y1, "\n")
 44s + showSRID("EPSG:4326", format="PROJ", EPSG_to_init=FALSE, 
prefer_proj=TRUE)

 44s + set_enforce_xy(TRUE)
 44s + y2 <- showSRID("EPSG:4326", multiline=TRUE, EPSG_to_init=FALSE, 
prefer_proj=TRUE)

 44s + cat(y2, "\n")
 44s + showSRID("EPSG:4326", format="PROJ", EPSG_to_init=FALSE, 
prefer_proj=TRUE)

 44s + }
 44s GEOGCRS["WGS 84 (with axis order normalized for visualization)",
 44s ENSEMBLE["World Geodetic System 1984 ensemble",
 44s MEMBER["World Geodetic System 1984 (Transit)",
 44s ID["EPSG",1166]],
 44s MEMBER["World Geodetic System 1984 (G730)",
 44s ID["EPSG",1152]],
 44s MEMBER["World Geodetic System 1984 (G873)",
 44s ID["EPSG",1153]],
 44s MEMBER["World Geodetic System 1984 (G1150)",
 44s ID["EPSG",1154]],
 44s MEMBER["World

Bug#1042426: marked as done (src:r-cran-sp: fails to migrate to testing for too long: triggers autopkgtest regression)

Your message dated Sat, 19 Aug 2023 17:35:50 +
with message-id 
and subject line Bug#1042426: fixed in r-cran-sp 1:2.0-0+dfsg-2
has caused the Debian Bug report #1042426,
regarding src:r-cran-sp: fails to migrate to testing for too long: triggers 
autopkgtest regression
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.)


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

Source: r-cran-sp
Version: 1:1.6-0+dfsg-1
Severity: serious
Control: close -1 1:2.0-0+dfsg-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

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:r-cran-sp has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable 
triggers an autopkgtest failure in r-cran-rgdal.


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=r-cran-sp



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-sp
Source-Version: 1:2.0-0+dfsg-2
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-sp 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: Sat, 19 Aug 2023 17:55:38 +0200
Source: r-cran-sp
Architecture: source
Version: 1:2.0-0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1042426 1049438
Changes:
 r-cran-sp (1:2.0-0+dfsg-2) unstable; urgency=medium
 .
   * Drop rgdal from Test-Depends
 Closes: #1042426, #1049438
Checksums-Sha1:
 27ec6f61e29ef70b785356b1efc7b79ad5089971 2200 r-cran-sp_2.0-0+dfsg-2.dsc
 bd3dab4082a98cb6d0daae28c3f6e322dc8cb983 4984 
r-cran-sp_2.0-0+dfsg-2.debian.tar.xz
 e8408cff9992ab57558993930c069c4324351e83 10681 
r-cran-sp_2.0-0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 e840e18a8931c56a73b6845f726b8478832eabf4345cbed31281589f2a9a1055 2200 
r-cran-sp_2.0-0+dfsg-2.dsc
 193b5045b3676f8ce601a4629ad812b4ced3b883dd1322daf72488da736eb649 4984 
r-cran-sp_2.0-0+dfsg-2.debian.tar.xz
 911e82fed8cdade727f13f8819460035cbc00e2dfb87262702c5c616cfa652f5 10681 
r-cran-sp_2.0-0+dfsg-2_amd64.buildinfo
Files:
 b1c77478b02adc96889aa8ff31b2124c 2200 gnu-r optional r-cran-sp_2.0-0+dfsg-2.dsc
 84b4959719201192ff562e4e560c5dfc 4984 gnu-r optional 
r-cran-sp_2.0-0+dfsg-2.debian.tar.xz
 088cdf3cd8e234d27fcaca7cf1fa295b 10681 gnu-r optional 
r-cran-sp_2.0-0+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmTg7PIRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHy0A//VMJTN85fQZi8hcUiKn7FLbocaJTpI6aM
kfPp7wf05pz04UetxLaggUur15OXIzX4J2j1viAbSXU6Kk/AC8iYiyhft7LdUN8L

Bug#1033907: numba crashes on non-x86

2023-08-19 Thread Rebecca N. Palmer

numba also crashes on mips64el, mipsel and armhf (and s390x but that was 
already known; not amd64, i386 or ppc64el).  However, I agree that arm64 
is a good place to start trying to fix this, given how common it is.


For examples, see the pandas 2.0.3+dfsg-3 / 1.5.3+dfsg-5 build logs. 
Given the different error messages, there may be more than one bug here.

Bug#1050027: marked as done (libcoq-mathcomp-classical: undeclared file conflict with libcoq-mathcomp-analysis/bookworm+trixie)

Your message dated Sat, 19 Aug 2023 17:29:26 +
with message-id 
and subject line Bug#1050027: fixed in mathcomp-analysis 0.6.4-2
has caused the Debian Bug report #1050027,
regarding libcoq-mathcomp-classical: undeclared file conflict with 
libcoq-mathcomp-analysis/bookworm+trixie
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.)


-- 
1050027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcoq-mathcomp-classical
Version: 0.6.4-1+b1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libcoq-mathcomp-analysis

libcoq-mathcomp-classical starts to ship the following files:

/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/boolp.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/boolp.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/boolp.vo
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/cardinality.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/cardinality.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/cardinality.vo
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/classical_sets.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/classical_sets.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/classical_sets.vo
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/fsbigop.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/fsbigop.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/fsbigop.vo
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/functions.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/functions.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/functions.vo
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/mathcomp_extra.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/mathcomp_extra.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/mathcomp_extra.vo
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/set_interval.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/set_interval.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/set_interval.vo

They happen to also be part of libcoq-mathcomp-analysis as part of
bookworm and trixie. There is no Conflicts nor Replaces relation
addressing this conflict nor are there any diversions. As such, this
situation can result in unpack errors in an upgrade scenario.

Judging from the changelog (saying "package split") you mean to
restructure and therefore replace these files. If you agree, please add
the necessary Breaks+Replaces relations.

Helmut
--- End Message ---
--- Begin Message ---
Source: mathcomp-analysis
Source-Version: 0.6.4-2
Done: Julien Puydt 

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated mathcomp-analysis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Aug 2023 17:43:17 +0200
Source: mathcomp-analysis
Architecture: source
Version: 0.6.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Julien Puydt 
Closes: 1050027
Changes:
 mathcomp-analysis (0.6.4-2) unstable; urgency=medium
 .
   * Add missing Breaks (Closes: #1050027).
Checksums-Sha1:
 e0f02fd8f8a4e2da7d6b4f86adc5a8bb32a72142 2425 mathcomp-analysis_0.6.4-2.dsc
 d41aa73dc997fd2129904a43e07baa8b27109767 9092 
mathcomp-analysis_0.6.4-2.debian.tar.xz
 de23cbbe0bae1468588e12c3ec331589c438c0a2 8327 
mathcomp-analysis_0.6.4-2_source.buildinfo
Checksums-Sha256:
 969584b762ec94d4291e36c2f0c8e2a6478e6ab97a7d164c7a870f52adc3dddb 2425 
mathcomp-analysis_0.6.4-2.dsc
 beadba78be8b42c9206530a3cc224a78c4b70385ff88e8f6b2406b7a444f60c8 9092 
mathcomp-analysis_0.6.4-2.debian.tar.xz
 7fa489459dbf58a91f40658a43c3730a2d2e5fea18d7c4989bcb7ca2264897af 8327 
mathcomp-analysis_0.6.4-2_source.buildinfo
Files:
 3f8e1a4b4b97ae63c0e245d59761e2ec 2425 ocaml optional 
mathcomp-analysis_0.6.4-2.dsc
 63e7e3131d3be6cc5289b7054730fdbc 9092 ocaml optional 
mathcomp-analysis_0.6.4-2.debian.tar.xz

Bug#1050096: virtualbox-dkms: Does not build on 6.4.0-3-amd64

2023-08-19 Thread Michael Rasmussen

Package: virtualbox-dkms
Version: 7.0.10-dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

DKMS make.log for virtualbox-7.0.10 for kernel 6.4.0-3-amd64 (x86_64)
2023-08-19T19:17:04 CEST
make: Entering directory '/usr/src/linux-headers-6.4.0-3-amd64'
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPLibAll.o
  CC [M]  
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/common/string/strformatrt.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-agnostic1.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-agnostic2.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-os-specific.o
  LD [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool: 
SUPR0TracerFireProbe+0x7: indirect jump found in RETPOLINE build
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool: 
supdrvTracerProbeFireStub+0x0: 'naked' return found in RETHUNK build
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool: 
rtThreadCtxHooksLnxSchedOut+0x23: call to {dynamic}() with UACCESS enabled
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool: 
rtThreadCtxHooksLnxSchedIn+0x2d: call to {dynamic}() with UACCESS enabled
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool: 
VBoxHost_RTR0MemKernelCopyFrom+0x17: redundant CLD
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool: 
VBoxHost_RTR0MemKernelCopyTo+0x17: redundant CLD
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool: 
supdrvTracerCommonDeregisterImpl+0x3c: relocation to !ENDBR: 
supdrvTracerProbeFireStub+0x0
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool: 
___ksymtab+SUPR0TracerFireProbe+0x0: data relocation to !ENDBR: 
SUPR0TracerFireProbe+0x0
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool: 
g_aFunctions+0xea0: data relocation to !ENDBR: SUPR0TracerFireProbe+0x0
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool: 
g_pfnSupdrvProbeFireKernel+0x0: data relocation to !ENDBR: 
supdrvTracerProbeFireStub+0x0
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool: 
SUPR0TracerFireProbe+0x7: missing int3 after indirect jump
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o: warning: objtool: 
supdrvTracerProbeFireStub+0x0: missing int3 after ret
  CC [M]  
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/VBoxNetFlt.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/SUPR0IdcClient.o
  CC [M]  
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/SUPR0IdcClientComponent.o
  CC [M]  
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/SUPR0IdcClient-linux.o
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c: In 
function ‘vboxNetFltLinuxForwardToIntNetInner’:
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:1570:40:
 error: implicit declaration of function ‘skb_gso_segment’; did you mean 
‘skb_gso_reset’? [-Werror=implicit-function-declaration]
 1570 | struct sk_buff *pSegment = skb_gso_segment(pBuf, 0 
/*supported features*/);
  |^~~
  |skb_gso_reset
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:1570:40:
 warning: initialization of ‘struct sk_buff *’ from ‘int’ makes pointer from 
integer without a cast [-Wint-conversion]
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-6.4.0-3-common/scripts/Makefile.build:257: 
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.o] 
Error 1
make[1]: *** [/usr/src/linux-headers-6.4.0-3-common/scripts/Makefile.build:502: 
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt] Error 2
make: *** [/usr/src/linux-headers-6.4.0-3-common/Makefile:2057: 
/var/lib/dkms/virtualbox/7.0.10/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.4.0-3-amd64'


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

Kernel: Linux 6.4.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_DK.UTF-8
Shell: /bin/sh linked to

Processed: Re: cron-daemon-common: the /etc/cron.hourly line in /etc/crontab is broken

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

> retitle 1049969 cron: /etc/crontab should include /bin and /sbin in PATH for 
> non-usrmerge systems
Bug #1049969 {Done: Georges Khaznadar } 
[cron-daemon-common] trixie/sid system ended up with split-usr
Changed Bug title to 'cron: /etc/crontab should include /bin and /sbin in PATH 
for non-usrmerge systems' from 'trixie/sid system ended up with split-usr'.
> reopen 1049969
Bug #1049969 {Done: Georges Khaznadar } 
[cron-daemon-common] cron: /etc/crontab should include /bin and /sbin in PATH 
for non-usrmerge systems
'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 cron/3.0pl1-168.
> notfixed 1049969 cron/3.0pl1-168
Bug #1049969 [cron-daemon-common] cron: /etc/crontab should include /bin and 
/sbin in PATH for non-usrmerge systems
Ignoring request to alter fixed versions of bug #1049969 to the same values 
previously set
> severity 1049969 normal
Bug #1049969 [cron-daemon-common] cron: /etc/crontab should include /bin and 
/sbin in PATH for non-usrmerge systems
Severity set to 'normal' from 'serious'
> forcemerge 1049964 1049969
Bug #1049964 [cron-daemon-common] Crontab should include /bin and /sbin in path
Bug #1049964 [cron-daemon-common] Crontab should include /bin and /sbin in path
Marked as found in versions cron/3.0pl1-166.
Bug #1049969 [cron-daemon-common] cron: /etc/crontab should include /bin and 
/sbin in PATH for non-usrmerge systems
Marked as found in versions cron/3.0pl1-165.
Merged 1049964 1049969
> thanks
Stopping processing here.

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

Bug#1049977: rust-hyper-rustls - please update to match new rust-tokio-rustls

2023-08-19 Thread Jonas Smedegaard

Quoting Peter Green (2023-08-19 14:30:22)
> > Since rust-hyper-rustls has reverse dependencies as well, its move
> > to to v0.24 will involve NEW queue and potentially take some time.
> 
> According to my searches the only direct reverse dependency of
> rust-hyper-rustls is rust-reqwest.

Indeed - I made the error of taking into account indirect reverse
dependencies.


I have the new version of that (which is not semver-breaking) ready to
> upload as soon as hyper-rustls is uploaded to unstable.

Excellent: Then I'll re-release to unstable now.

 - 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#1041810: librsvg: CVE-2023-38633

2023-08-19 Thread Salvatore Bonaccorso

Hi Simon,

On Sun, Jul 30, 2023 at 09:48:57PM +0100, Simon McVittie wrote:
> On Sun, 30 Jul 2023 at 22:04:24 +0200, Salvatore Bonaccorso wrote:
> > For bullseye I think we should simply pick the upstream commit?
> 
> Yes: we didn't keep up with upstream 2.50.x so there are a bunch of
> unrelated fixes (2.50.4 up to .7) which would be out of scope for a
> security update. If it was a package I knew better then I might be
> advocating the new upstream release, but I can't really assess risk vs
> benefit for librsvg, so cherry-picking the equivalent of .8 and .9 seems
> more conservative.
> 
> 
> compiles successfully, I'll try it in a bullseye VM next.

If you are happy with the results and coverage from unstable, would
you be open to prepare/finalize next the respective updates for
bookworm-security and bullseye-security?

Thanks a lot for your work so far on it!

Regards,
Salvatore

Bug#1040475: marked as pending in apache-directory-server

2023-08-19 Thread Markus Koschany

Control: tag -1 pending

Hello,

Bug #1040475 in apache-directory-server 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/java-team/apache-directory-server/-/commit/02bd89466cb54bcf1e41e5dbc48a421a7fd1be0c


Fix broken symlinks by explicitly depending on

libapache-directory-api-java, libbcprov-java, libcaffeine-java, libmavibot-java
and libapache-directory-jdbm-java.

Closes: #1040475
Thanks: Andreas Beckmann for the report.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040475

Processed: Bug#1040475 marked as pending in apache-directory-server

Processing control commands:

> tag -1 pending
Bug #1040475 [apacheds] apacheds: broken symlinks: 
/usr/share/apacheds/lib/*.jar -> ../../java/*.jar
Added tag(s) pending.

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

Bug#1040475: Broken symlinks cause Apache Directory Server to not work at all out-of-the-box

2023-08-19 Thread Markus Koschany

I believe the symlink problem is fixed in version 2.0.0~M26-2 but I'd like to
test the apacheds server component more before I'm going to close this bug
report.

Markus


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

Processed: fixed

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

> close 1042234 8.5.3-1
Bug #1042234 [src:dtrx] dtrx: FTBFS: make: *** [debian/rules:8: clean] Error 25
Marked as fixed in versions dtrx/8.5.3-1.
Bug #1042234 [src:dtrx] dtrx: FTBFS: make: *** [debian/rules:8: clean] Error 25
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#1049977: rust-hyper-rustls - please update to match new rust-tokio-rustls

Processing control commands:

> severity -1 serious
Bug #1049977 [rust-hyper-rustls] rust-hyper-rustls - please update to match new 
rust-tokio-rustls
Severity set to 'serious' from 'important'
> tags -1 +ftbfs
Bug #1049977 [rust-hyper-rustls] rust-hyper-rustls - please update to match new 
rust-tokio-rustls
Added tag(s) ftbfs.

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

Bug#1050088: rust-cargo-mutants: Unknown section 'FIXME-IN-THE-SOURCE-SECTION'

Source: rust-cargo-mutants
Version: 23.6.0-1
Severity: serious

rust-cargo-mutants ended up with an invalid Section field in its
debian/control . Perhaps this is a debcargo bug? This can be handled
in the package debian/debcargo.toml

This error is basically an autoreject in Ubuntu:
https://launchpad.net/ubuntu/+source/rust-cargo-mutants/23.6.0-1/+latestbuild/amd64

Thank you,
Jeremy Bícha

Bug#1050086: rust-ahash: Fails to build

Source: rust-ahash
Version: 0.8.3-7
Severity: serious
Tags: ftbfs

rust-ahash fails to build. Here's a build log excerpt:

error[E0432]: unresolved import `criterion`
 --> tests/map_tests.rs:6:5
  |
6 | use criterion::*;
  | ^ use of undeclared crate or module `criterion`

error[E0432]: unresolved import `fxhash`
 --> tests/map_tests.rs:7:5
  |
7 | use fxhash::FxHasher;
  | ^^ use of undeclared crate or module `fxhash`
  |
help: there is a crate or module with a similar name
  |
7 | use ahash::FxHasher;
  | ~

error: cannot find macro `criterion_main` in this scope
   --> tests/map_tests.rs:233:1
|
233 | criterion_main!(benches);
| ^^

error: cannot find macro `criterion_group` in this scope
   --> tests/map_tests.rs:234:1
|
234 | criterion_group!(benches, bench_ahash_words, bench_fx_words,);
| ^^^

error[E0412]: cannot find type `Criterion` in this scope
   --> tests/map_tests.rs:223:30
|
223 | fn bench_ahash_words(c:  Criterion) {
|  ^ not found in this scope

error[E0425]: cannot find function `black_box` in this scope


Full build log
==
https://buildd.debian.org/status/package.php?p=rust-ahash

Thank you,
Jeremy Bícha

Bug#1050087: rust-microformats: Fails to build

Source: rust-microformats
Version: 0.4.2-1
Severity: serious
Tags: ftbfs

rust-microformats fails to build from source with several test failures.

https://buildd.debian.org/status/package.php?p=rust-microformats

Thank you,
Jeremy Bícha

Bug#1042904: marked as done (libvirt-clients: fail to start VM 'file' driver requires '/dev/vg0/UTM' to be a regular file)

Your message dated Sat, 19 Aug 2023 17:08:37 +0200
with message-id 
and subject line Re: Bug#1042904: SOLVED: Acknowledgement (libvirt-clients: 
fail to start VM 'file' driver requires '/dev/vg0/UTM' to be a regular file)
has caused the Debian Bug report #1042904,
regarding libvirt-clients: fail to start VM 'file' driver requires 
'/dev/vg0/UTM' to be a regular file
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.)

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

Package: libvirt-clients
Version: 9.0.0-4
Severity: grave
Justification: renders package unusable

The xml configuration file was working well on Debian 11. After 
upgrading to Bookworm I get this error, VM doesn't start:

virsh # start UTM
erreur :Failed to start domain 'UTM'
erreur :internal error: process exited while connecting to monitor: 
2023-08-02T14:13:20.203465Z kvm: -blockdev 
{"driver":"file","filename":"/dev/vg0/UTM","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}: 
'file' driver requires '/dev/vg0/UTM' to be a regular file

Changing driver file to block give on xml validation:

erreur :XML document failed to validate against schema: Unable to 
validate doc against /usr/share/libvirt/schemas/domain.rng

Extra element devices in interleave
Element domain failed to validate content

Attached is the VM xml configuration file. All of our VMs are based on 
LVM disk, we can't use anymore VMs from this server !

-- System Information:
Debian Release: 12.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')

Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libvirt-clients depends on:
ii libc6 2.36-9+deb12u1
ii libgcc-s1 12.2.0-14
ii libglib2.0-0 2.74.6-2
ii libgnutls30 3.7.9-2
ii libreadline8 8.2-1.3
ii libvirt0 9.0.0-4
ii libxml2 2.9.14+dfsg-1.3~deb12u1
ii sensible-utils 0.0.17+nmu1

libvirt-clients recommends no packages.

Versions of packages libvirt-clients suggests:
pn libvirt-clients-qemu 
ii libvirt-daemon 9.0.0-4
pn libvirt-login-shell 

-- no debconf information

  UTM
  9dda06a5-689a-4656-9476-145897ede125
  4194304
  4194304
  2

hvm

  destroy
  restart
  restart

/usr/bin/kvm

--- End Message ---
--- Begin Message ---
Package: libvirt
Version: 9.0.0-4

On Wed, Aug 02, 2023 at 06:09:27PM +0200, Daniel wrote:
> in xml files not only 'disk type' have to be changed to 'block' but also
> 'source' to 'dev'

Yeah, libvirt/QEMU might have gotten more strict in term of which
configurations they will accept between bullseye and bookworm but it
sounds like disk.type=block and source.dev=/dev/foo was always the
correct combination for using LVM volumes as backing store for VM
disks.

> Can be closed as not a bug

Done, thanks a lot for following up!

-- 
Andrea Bolognani 
Resistance is futile, you will be garbage collected.

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

Bug#1031363: marked as done (librnp0 from experimental breaks thunderbird openpgp feature)

Your message dated Sat, 19 Aug 2023 16:00:15 +0200
with message-id 
and subject line Fixed in unstable with actual packages
has caused the Debian Bug report #1031363,
regarding librnp0 from experimental breaks thunderbird openpgp feature
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.)


-- 
1031363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librnp0
Version: 0.17.0~git20220428-1
Severity: serious
Justification: makes unrelated software on the system

Thre is no dependency and the packages installs but thunderbird do not manage 
to dlopen the dddl and it breaks opengpg.

Downgrading to unstable version fixes the problem.


-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

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

Versions of packages librnp0 depends on:
ii  libbotan-2-19  2.19.3+dfsg-1
ii  libbz2-1.0 1.0.8-5+b1
ii  libc6  2.36-8
ii  libgcc-s1  12.2.0-14
ii  libjson-c5 0.16-2
ii  libstdc++6 12.2.0-14
ii  zlib1g 1:1.2.13.dfsg-1

librnp0 recommends no packages.

librnp0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
The 0.17 in unstable and the thunderbird version that use the external 
lib are happily working together.


Closing as experimental version is now behind unstable version.

--eric--- End Message ---

Bug#1041388: marked as done (libclang-rt-17-dev: ships /usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm.a, already in libclang-rt-17-dev-wasm)

Your message dated Sat, 19 Aug 2023 12:04:12 +
with message-id 
and subject line Bug#1041388: fixed in llvm-toolchain-17 1:17.0.0~+rc2-1~exp1
has caused the Debian Bug report #1041388,
regarding libclang-rt-17-dev: ships 
/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm*.a, already in 
libclang-rt-17-dev-wasm*
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.)


-- 
1041388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libclang-rt-17-dev
Version: 1:17~++20230709044550+c54ff51be9c1-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package libclang-rt-17-dev:amd64.
  Preparing to unpack 
.../libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb ...
  Unpacking libclang-rt-17-dev:amd64 
(1:17~++20230709044550+c54ff51be9c1-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm64.a', which 
is also in package libclang-rt-17-dev-wasm64 
1:17~++20230709044550+c54ff51be9c1-1~exp1
  Errors were encountered while processing:
   
/var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb

  Selecting previously unselected package libclang-rt-17-dev:amd64.
  Preparing to unpack 
.../libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb ...
  Unpacking libclang-rt-17-dev:amd64 
(1:17~++20230709044550+c54ff51be9c1-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm32.a', which 
is also in package libclang-rt-17-dev-wasm32 
1:17~++20230709044550+c54ff51be9c1-1~exp1
  Errors were encountered while processing:
   
/var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb


cheers,

Andreas


libclang-rt-17-dev-wasm64=1:17~++20230709044550+c54ff51be9c1-1~exp1_libclang-rt-17-dev=1:17~++20230709044550+c54ff51be9c1-1~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-17
Source-Version: 1:17.0.0~+rc2-1~exp1
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-17 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Aug 2023 19:25:12 +
Source: llvm-toolchain-17
Binary: bolt-17 bolt-17-dbgsym clang-17 clang-17-dbgsym clang-17-doc 
clang-17-examples clang-format-17 clang-format-17-dbgsym clang-tidy-17 
clang-tidy-17-dbgsym clang-tools-17 clang-tools-17-dbgsym clangd-17 
clangd-17-dbgsym flang-17 flang-17-dbgsym libbolt-17-dev libc++-17-dev 
libc++-17-dev-wasm32 libc++1-17 libc++1-17-dbgsym libc++abi-17-dev 
libc++abi-17-dev-wasm32 libc++abi1-17 libc++abi1-17-dbgsym libclang-17-dev 
libclang-common-17-dev libclang-cpp17 libclang-cpp17-dbgsym libclang-cpp17-dev 
libclang-rt-17-dev libclang-rt-17-dev-dbgsym libclang-rt-17-dev-wasm32 
libclang-rt-17-dev-wasm64 libclang1-17 libclang1-17-dbgsym libclc-17 
libclc-17-dev libflang-17-dev libfuzzer-17-dev liblld-17 liblld-17-dev 
liblldb-17 liblldb-17-dbgsym liblldb-17-dev libllvm-17-ocaml-dev libllvm17 
libllvm17-dbgsym libmlir-17 libmlir-17-dbgsym libmlir-17-dev libomp-17-dev 
libomp-17-dev-dbgsym libomp-17-doc libomp5-17 libomp5-17-dbgsym libpolly-17-dev 
libunwind-17 libunwind-17-dbgsym
 libunwind-17-dev lld-17 lld-17-dbgsym lldb-17 lldb-17-dbgsym llvm-17 
llvm-17-dbgsym llvm-17-dev

Bug#1043418: marked as done (rust-rustls-webpki - autopkgtest failure, file not found errors.)

Your message dated Sat, 19 Aug 2023 11:56:28 +
with message-id 
and subject line Bug#1043418: fixed in rust-rustls-webpki 0.101.3-1.1
has caused the Debian Bug report #1043418,
regarding rust-rustls-webpki - autopkgtest failure, file not found errors.
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.)


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

Package: rust-rustls-webpki
Version: 0.101.2-2
Severity: serious

The autopkgtest for rust-rustls-webpki is failing with a bunch of file not 
found errors.
the first of which is pasted below.


199s error: couldn't read 
src/../third-party/chromium/data/verify_signed_data/ecdsa-prime256v1-sha512-spki-params-null.pem:
 No such file or directory (os error 2)
199s--> src/signed_data.rs:443:13
199s |
199s 443 | / include_bytes!(concat!(
199s 444 | | "../third-party/chromium/data/verify_signed_data/",
199s 445 | | $file_name
199s 446 | | ))
199s | |__^
199s ...
199s 573 | / test_verify_signed_data!(
199s 574 | | test_ecdsa_prime256v1_sha512_spki_params_null,
199s 575 | | "ecdsa-prime256v1-sha512-spki-params-null.pem",
199s 576 | | Err(Error::UnsupportedSignatureAlgorithm)
199s 577 | | );
199s | |_- in this macro invocation
199s |
199s = note: this error originates in the macro `include_bytes` which comes 
from the expansion of the macro `test_verify_signed_data` (in Nightly builds, 
run with -Z macro-backtrace for more info)
--- End Message ---
--- Begin Message ---
Source: rust-rustls-webpki
Source-Version: 0.101.3-1.1
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-rustls-webpki, 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 1043...@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-rustls-webpki 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: Sat, 19 Aug 2023 10:07:40 +
Source: rust-rustls-webpki
Architecture: source
Version: 0.101.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Peter Michael Green 
Closes: 1043418
Changes:
 rust-rustls-webpki (0.101.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch 2004 and alter debian/tests/control to use test data from the 
source
 package during autopkgtest as the test data is not included in the binary
 package (Closes: #1043418)
   * Extend patch 2001 to add autobenches=false so that the benches
 are really disabled
Checksums-Sha1:
 7bfe4081cd97386be5e56cdc94c51922dd9d1796 2686 
rust-rustls-webpki_0.101.3-1.1.dsc
 8faaeeea94becdc1d002e17a10e2406d48a5 15012 
rust-rustls-webpki_0.101.3-1.1.debian.tar.xz
 c9e794af2c9147da89a1cc68e77df67e6147f0fd 11056 
rust-rustls-webpki_0.101.3-1.1_source.buildinfo
Checksums-Sha256:
 6b986a5c4ffa8cb65e6af700886991849503a64bab928c15b3e91408416ce1f6 2686 
rust-rustls-webpki_0.101.3-1.1.dsc
 600a1400fb8c39eeca6549284baeb9bd8028f66fd56d3b908a48dd230158f54a 15012 
rust-rustls-webpki_0.101.3-1.1.debian.tar.xz
 d28fe6c8619a418f6b4f2a091754c1ac108c85b9190fae84636019c2b2991a23 11056 
rust-rustls-webpki_0.101.3-1.1_source.buildinfo
Files:
 3fe2bbcf51081cf2dd69a13d93d32c6f 2686 rust optional 
rust-rustls-webpki_0.101.3-1.1.dsc
 a0753b73f4f476487e4013458f14eb84 15012 rust optional 
rust-rustls-webpki_0.101.3-1.1.debian.tar.xz
 50923269c5d873b15690190b602972dc 11056 rust optional 
rust-rustls-webpki_0.101.3-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmTglRYUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvszQ/8ChkTnq8inv3yET04Bj1QZPy39f/S
ov4fqyET2u1L6+o+VnF1RRxO3FC7zFOdAdzrBIy3ILkI4l3EVr6BXKb17FTzDHIv
g1DrYOWctdZ1ESKoUQaALgapl0c55UApAgeJwup9sakG96p65a1iT9zC6DyAjUvf
FnDdPLJpVBEG6c+rWijF2jFDbn8ECvrpUM3ESGovMOD6VqHmpkF4VVTxms+3fNq9
7MUJRT4c70PR6KUPQYYL4ut+o6DiwYqqw+90Qv3sXb/dbYztECM9wol4cxyVhqbb
qcsvvmcFSplJNS1wDZzC7Ah2hXt7BuBeqreJhE27C2KdSwX2GLa8C5mrO1fAeJWl

Bug#1050059: marked as done (src:libconfig-model-perl: fails to migrate to testing for too long: autopgktest regression)

Your message dated Sat, 19 Aug 2023 11:50:58 +
with message-id 
and subject line Bug#1050059: fixed in libconfig-model-perl 2.153-3
has caused the Debian Bug report #1050059,
regarding src:libconfig-model-perl: fails to migrate to testing for too long: 
autopgktest regression
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.)


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

Source: libconfig-model-perl
Version: 2.152-1
Severity: serious
Control: close -1 2.153-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

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:libconfig-model-perl has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug. The version in 
unstable doesn't pass it's own autopkgtest.


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=libconfig-model-perl



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libconfig-model-perl
Source-Version: 2.153-3
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libconfig-model-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Aug 2023 12:02:51 +0200
Source: libconfig-model-perl
Architecture: source
Version: 2.153-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1050059
Changes:
 libconfig-model-perl (2.153-3) unstable; urgency=medium
 .
   * Add patch to fix autopkgtest failure. (Closes: #1050059)
   * Update years of packaging copyright.
Checksums-Sha1:
 a857085bc523e5b65e75b72d9a15aa7f61e4fec6 3168 libconfig-model-perl_2.153-3.dsc
 2cf7bbc5e63cc3c18e112ce0a41fc2d1ff55ac77 25040 
libconfig-model-perl_2.153-3.debian.tar.xz
Checksums-Sha256:
 1217229b6672acb2008c64b8912c5e2bf2b211749d3cf1190ce03ee6abb79596 3168 
libconfig-model-perl_2.153-3.dsc
 ab2bfcb14603b6bf153960f7e179878b2cf2c8fe2647b5436e0ecf5946cd79cb 25040 
libconfig-model-perl_2.153-3.debian.tar.xz
Files:
 63c688e404aee2cf53a84d4805c61d45 3168 perl optional 
libconfig-model-perl_2.153-3.dsc
 99a5189e974614091dcb88f402517b07 25040 perl optional 
libconfig-model-perl_2.153-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmTglDZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgabHRAAp0mEYAUOu71ZfmsfcInjTSoGHYyyoxaeK51f+rpki7SDrjpkP1jKTlyQ
366SO/DualXKJomjkEC6atu3BbPi/0L+FkNHD74SKY2bCLiFSgHQlEbrB8G3lPmd
foidnpGooNdsFphkCFOEWSBTG/hhrPM5Q20e3nWoSYRhSV7RRb3Bj+JNZCh1fLR1

Bug#1042270: marked as done (gnome-browser-connector: FTBFS: dh_usrlocal: error: debian/gnome-browser-connector/usr/local/lib/python3.11/dist-packages/gnome_browser_connector/init.py is not a dire

Your message dated Sat, 19 Aug 2023 07:41:30 -0400
with message-id 

and subject line Re: gnome-browser-connector: FTBFS: dh_usrlocal: error: 
debian/gnome-browser-connector/usr/local/lib/python3.11/dist-packages/gnome_browser_connector/__init__.py
 is not a directory
has caused the Debian Bug report #1042270,
regarding gnome-browser-connector: FTBFS: dh_usrlocal: error: 
debian/gnome-browser-connector/usr/local/lib/python3.11/dist-packages/gnome_browser_connector/__init__.py
 is not a directory
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.)


-- 
1042270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-browser-connector
Version: 42.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 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 '/<>'
> mkdir -p debian/gnome-browser-connector/usr/share/gnome-browser-connector
> mv 
> debian/gnome-browser-connector/etc/opt/chrome/native-messaging-hosts/org.gnome.chrome_gnome_shell.json
>  \
>   
> debian/gnome-browser-connector/usr/share/gnome-browser-connector/org.gnome.chrome_gnome_shell.json
> mv 
> debian/gnome-browser-connector/etc/opt/chrome/native-messaging-hosts/org.gnome.browser_connector.json
>  \
>   
> debian/gnome-browser-connector/usr/share/gnome-browser-connector/org.gnome.browser_connector.json
> rm -rf debian/gnome-browser-connector/etc/opt
> make[1]: Leaving directory '/<>'
>dh_installdocs
>dh_installchangelogs
>dh_gnome
>dh_icons
>dh_perl
>dh_usrlocal
> dh_usrlocal: error: 
> debian/gnome-browser-connector/usr/local/lib/python3.11/dist-packages/gnome_browser_connector/__init__.py
>  is not a directory
> make: *** [debian/rules:4: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/gnome-browser-connector_42.1-3_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Not reproducible now. I assume this was fixed with debhelper 13.11.5

Thank you,
Jeremy Bícha--- End Message ---

Bug#1050077: gtk4: 4.12 regression: FTBFS on mips(64)el: multiple test failures

Source: gtk4
Version: 4.12.0+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-m...@lists.debian.org
User: debian-m...@lists.debian.org
Usertags: mips64el mipsel

gtk4 4.12.0 in experimental has test failures on multiple buildds.
Of those, mips64el and mipsel seem to have the same failure mode:
failure mode:

  72/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-flipped-gl / gl 
border-one-rounded flipped   FAIL   
  5.47s   exit status 1
 315/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl / gl opacity-overdraw   
 FAIL   
  4.89s   exit status 1
 316/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-flipped-gl / gl 
opacity-overdraw flipped FAIL   
  4.94s   exit status 1
 317/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-repeated-gl / 
gl opacity-overdraw repeated   FAIL 
5.05s   exit status 1
 318/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-rotated-gl / gl 
opacity-overdraw rotated FAIL   
  4.95s   exit status 1
 319/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-masked-gl / gl 
opacity-overdraw masked   FAIL  
   5.02s   exit status 1
1406/1464 gtk:reftest / reftest label-sizing.ui 
 FAIL   
 19.29s   0/1 subtests passed
1422/1464 gtk:reftest / reftest opacity.ui  
 FAIL   
  6.79s   0/1 subtests passed

These are "reftests", which work by rendering the same image in two
different ways and then doing a pixel-by-pixel comparison. Because
Debian buildds do not give us a way to capture test artifacts, the images
are output into the log with uuencode, for example these:

begin-base64 644 testsuite/gsk/compare/opacity-overdraw.png
iVBORw0KGgoNSUhEUgAAAB4eCAY7MK6iRklEQVRIie3WMQ4AIAxCUWo8uDev
B7BjYwc+I8tLmAgpjwayJlDgr9lVmYpWJJRP5zc1MDAwMDAwsDFcfq7qI3XHb2o/+AJ0lQS/vZJx
GQBJRU5ErkJggg==


begin-base64 644 
debian/build/deb/testsuite/gsk/compare/gl/x11/opacity-overdraw.out.png
iVBORw0KGgoNSUhEUgAAAB4eCAY7MK6iS0lEQVRIie3WMQ4AIAhD0aIe3Isb
vACDA5GB35HlJWWpSb5VkFGBAn/Nio5HlopM+Rv8o4Z+PwYGBgYGBgauh8PpY8FGyk6/qvvBF6Er
BMOKG8HLAElFTkSuQmCC


begin-base64 644 
debian/build/deb/testsuite/gsk/compare/gl/x11/opacity-overdraw.diff.png
iVBORw0KGgoNSUhEUgAAAB4eCAY7MK6iKklEQVRIie3NoQEAIAzEwGdvZPeG
BUBR3J2MSQKfjFOsZHVO5uUDAAC82WlIAgJv9eZaAElFTkSuQmCC


The way these work is that they are output in sets of three: a reference
image, an actual output, and an artifically-enhanced diff image to
highlight what the difference is. See #1024391, #993550, #1003348 for
previous examples of architecture-specific rendering differences (#1024391
was not on mips*, but has details of how to run individual tests which
might be useful, while the other two were on mips*el).

I haven't reconstructed the actual images for a visual comparison yet.
If the mis-rendering doesn't seem release-critically bad then we'll work
around this by ignoring those particular test failures on mips*el.

mips*el are the only architectures where we are using the softpipe GL
driver (because llvmpipe appears to be otherwise broken there) so that is a
possible root cause.

Having to investigate and work around failing tests in GL-dependent
packages on mips*el is becoming a significant time sink for the GNOME team,
so I would appreciate it if mips porters could fix its llvmpipe so that it
can be back in the same situation as every other release architecture.

smcv

Bug#1050026: r-bioc-metagenomeseq: autopkgtest regression

2023-08-19 Thread Andreas Tille

Control: tags -1 upstream
Control: forwarded -1 https://github.com/HCBravoLab/metagenomeSeq/issues/87


-- 
http://fam-tille.de

Processed: Re: Bug#1050026: r-bioc-metagenomeseq: autopkgtest regression

Processing control commands:

> tags -1 upstream
Bug #1050026 [src:r-bioc-metagenomeseq] r-bioc-metagenomeseq: autopkgtest 
regression
Added tag(s) upstream.
> forwarded -1 https://github.com/HCBravoLab/metagenomeSeq/issues/87
Bug #1050026 [src:r-bioc-metagenomeseq] r-bioc-metagenomeseq: autopkgtest 
regression
Set Bug forwarded-to-address to 
'https://github.com/HCBravoLab/metagenomeSeq/issues/87'.

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

Bug#1050076: gtk4: 4.12 regression: FTBFS on i386: assertion failed (r == tests[i].r (+/- FLT_EPSILON))

Source: gtk4
Version: 4.12.0+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Usertags: i387

gtk4 4.12.0 in experimental has test failures on multiple buildds.
On i386 there is this failure:

not ok /color/roundtrips - 
ERROR:../../../testsuite/gtk/colorutils.c:43:test_roundtrips: assertion failed 
(r == tests[i].r (+/- FLT_EPSILON)): (1.1920929e-07 == 0)

I think this is our old enemy, the legacy i387 FPU and its 80-bit
extended precision, and the test will need to apply more fuzz to its
acceptable result.

If our i386 port had a baseline that included SSE2 so that we could
build everything with -mfpmath=sse, this class of bug would probably
go away; but at the moment our baseline is officially a not-quite-i686
(i686 with one missing opcode, to accommodate certain Geode CPUs) so
we cannot assume MMX, SSE or SSE2, and various developers have resisted
suggestions to raise the baseline. I'm going to start tracking bugs in
this class with a usertag to get an idea of how many of them there are.

smcv

Bug#1050075: gtk4: 4.12 regression: FTBFS on arm*|ppc64el|s390x: several checkerboard tests failing

Source: gtk4
Version: 4.12.0+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

gtk4 4.12.0 in experimental has test failures on multiple buildds.
Of those, arm64, armel, armhf, ppc64el and s390x all seem to have the same
failure mode:

  36/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+wayland_gles_failing / gl 
big-checkerboard-scaled-down2  FAIL 
   3.48s   exit status 1
  37/1464 
gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+wayland_gles_failing+gsk-compare-flipped-gl
 / gl big-checkerboard-scaled-down2 flipped   FAIL3.50s 
  exit status 1
  38/1464 
gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+wayland_gles_failing+gsk-compare-repeated-gl
 / gl big-checkerboard-scaled-down2 repeated FAIL3.78s  
 exit status 1
  39/1464 
gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+wayland_gles_failing+gsk-compare-rotated-gl
 / gl big-checkerboard-scaled-down2 rotated   FAIL3.62s 
  exit status 1
  42/1464 
gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+wayland_gles_failing+gsk-compare-masked-gl
 / gl big-checkerboard-scaled-down2 masked FAIL
4.00s   exit status 1

I'm unsure why we are running tests that appear to be flagged as "failing".
Perhaps it just needs some --no-suite=failing added?

Test failures on i386 and mips64el are out of scope for this bug report.

smcv

Bug#1031363: Fixed with 0.17.0-3 and thunderbird 1:115.1.1-1

2023-08-19 Thread Eric Valette

The 0.17 in unstable and the thunderbird version that use the external 
lib are happily working together.


But can be closed.

-- eric

Bug#1031363: librnp0 from experimental breaks thunderbird openpgp feature

2023-08-19 Thread Jean-Marc


Hi Eric,

On Wed, 15 Feb 2023 18:59:23 +0100 Eric Valette  
wrote:

> Package: librnp0
> Version: 0.17.0~git20220428-1
> Severity: serious
> Justification: makes unrelated software on the system
>
> Thre is no dependency and the packages installs but thunderbird do 
not manage to dlopen the dddl and it breaks opengpg.

>
> Downgrading to unstable version fixes the problem.
>

Can you confirm you are still facing this issue with the last version of 
thunderbird ?


And, please, update this bug report accordingly.

Thank you so much.

Regards,

---
Jean-Marc 


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: libesmtp: diff for NMU version 1.1.0-3.1

Processing control commands:

> tags 1043058 + patch
Bug #1043058 [libesmtp6] libesmtp6: missing Breaks: libesmtp5
Added tag(s) patch.
> tags 1043058 + pending
Bug #1043058 [libesmtp6] libesmtp6: missing Breaks: libesmtp5
Added tag(s) pending.

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

Bug#1043058: libesmtp: diff for NMU version 1.1.0-3.1

2023-08-19 Thread Salvatore Bonaccorso

Control: tags 1043058 + patch
Control: tags 1043058 + pending


Dear maintainer,

I've prepared an NMU for libesmtp (versioned as 1.1.0-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,
Salvatore
diff -Nru libesmtp-1.1.0/debian/changelog libesmtp-1.1.0/debian/changelog
--- libesmtp-1.1.0/debian/changelog	2021-10-24 19:55:32.0 +0200
+++ libesmtp-1.1.0/debian/changelog	2023-08-19 12:04:32.0 +0200
@@ -1,3 +1,11 @@
+libesmtp (1.1.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * libesmtp6: Add versioned Replaces and Breaks against
+libesmtp5 (<< 1.0.6-1~) (Closes: #1043058)
+
+ -- Salvatore Bonaccorso   Sat, 19 Aug 2023 12:04:32 +0200
+
 libesmtp (1.1.0-3) unstable; urgency=medium
 
   * debian: Clean up build environment
diff -Nru libesmtp-1.1.0/debian/control libesmtp-1.1.0/debian/control
--- libesmtp-1.1.0/debian/control	2021-10-24 19:34:07.0 +0200
+++ libesmtp-1.1.0/debian/control	2023-08-19 12:04:32.0 +0200
@@ -17,7 +17,8 @@
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Replaces: libesmtp5
+Replaces: libesmtp5 (<< 1.0.6-1~)
+Breaks: libesmtp5 (<< 1.0.6-1~)
 Description: LibESMTP SMTP client library
  LibESMTP is a library to manage posting (or submission of) electronic
  mail using SMTP to a preconfigured Mail Transport Agent (MTA) such as

Bug#1043127: marked as done (creduce: switch to current llvm default version)

Your message dated Sat, 19 Aug 2023 09:50:44 +
with message-id 
and subject line Bug#1043127: fixed in creduce 2.11.0~20230819-1
has caused the Debian Bug report #1043127,
regarding creduce: switch to current llvm default version
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.)


-- 
1043127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: creduce
Version: 2.10.0+20220116-1
Severity: serious
Control: block 1017679 by -1
X-Debbugs-Cc: sramac...@debian.org

creduce currently blocks removal of llvm-toolchain-13. Please move to
the current default version (14) or newer. See #1017679 for the removal
bug.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: creduce
Source-Version: 2.11.0~20230819-1
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated creduce package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Aug 2023 10:30:41 +0200
Source: creduce
Architecture: source
Version: 2.11.0~20230819-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 1043127 1045055
Changes:
 creduce (2.11.0~20230819-1) unstable; urgency=medium
 .
   * New upstream snapshot, taken from master branch.
   * Build using LLVM 16. Closes: #1043127.
   * Build in a separate builddir. Closes: #1045055.
   * Bump standards version.
Checksums-Sha1:
 df48aa5d12d5f3d43350d5574d1af010906fcdd2 2162 creduce_2.11.0~20230819-1.dsc
 c05237e98fc6d3c84d799adf8b1d3dff61ddb686 487292 
creduce_2.11.0~20230819.orig.tar.xz
 7da4fe2e4892a552bfae1e0363dc018b6d1b5117 7372 
creduce_2.11.0~20230819-1.debian.tar.xz
 b37a796cc3c7582d95891543d534434ac5ca9341 12224 
creduce_2.11.0~20230819-1_source.buildinfo
Checksums-Sha256:
 1a342174d0deed9866d32817ba2719d0e169b3d5ae9a2740a9c65e86805af146 2162 
creduce_2.11.0~20230819-1.dsc
 8be92d2f637d73c27ed1a33cd4df7c550c478893a5009cf6654126fa6134b33a 487292 
creduce_2.11.0~20230819.orig.tar.xz
 a3c0da2f8be3b01f4e7b405ef749fad9a078b35b46e856724a650fb00b85c0df 7372 
creduce_2.11.0~20230819-1.debian.tar.xz
 c3aba5eccd49598c11b25bac01fee13e07f5a0f1375ef54af7870a295fb5540b 12224 
creduce_2.11.0~20230819-1_source.buildinfo
Files:
 3dc7b8d91002042f7ac819097012625b 2162 devel optional 
creduce_2.11.0~20230819-1.dsc
 c0568d6c1bce9e3ec79a7d65452a9ead 487292 devel optional 
creduce_2.11.0~20230819.orig.tar.xz
 b636161f977349dd7225d97d8ed2b23b 7372 devel optional 
creduce_2.11.0~20230819-1.debian.tar.xz
 ae9747441370946a6b393d03027ed28f 12224 devel optional 
creduce_2.11.0~20230819-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmTghGoQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9VCTD/sFCeAlCCLe4PQ9ggnAA9nJvl1prjDn7Z5A
Gb5p791DfiFzcUK/aXUGBCjx481ZJvxSA28OmKWzEBoFnICii024ksx98oIYI9BO
S9wZ7MdeeTznesl+R2JjvLxcaHa2ZfnDMVNYDnlJqM+mGQET92dKlVV8yJB0S0Mh
qXIgVbiViEPBndRy7I6hBw/G0hbTLW0C3eXd7bS0WtmE3RceJKV4pgK5AgugnW3q
pWsdevoOppX/35MoKVlw/VT7uFd7hrezs7gQFxs8bGwZTB73uqUAukLffsoxwXEV
sDikM/rFLVm/ujFi6Uy/RdRaXsbfdqWU8nVqvkQmsWFAwm4YYQTCX1rFBkeF3x6S
8HqL4uGd21EodKGCOwOA6dQ99KiZvvjpC3y5jUh+/FTBvY0EC1+hrxbExQYOXh5c
BcUF5lKygo+UWo0xRZEGLFG+XiV0X/elJ6b+B9OPmb6hGjrsqe3l0ZzeyPi/KLWq
kVPk7yAMb9XTvA/+dgHT0F1w1Osw3o75lKxx9dKPVgto5nKx2HCfmUOxCP5Hemnb
mtS3rILwHtiBFhZI7+gYS8VlPc0yq8v714QttZWEWshfHyJ+xH/VwawZy/hxBrZ0
XGsty3XpIxsASVt+0fH7KAaIEHeGic1Mmb0PflQUlLbsyAd1JjZfHvWzeA5Jv46n
J5Tk7Txxow==
=knhL
-END PGP SIGNATURE End Message ---

Bug#1049969: cron-daemon-common: the /etc/cron.hourly line in /etc/crontab is broken

2023-08-19 Thread Vincent Lefevre

On 2023-08-19 07:39:24 +0200, Ansgar wrote:
> On Fri, 2023-08-18 at 22:45 +0200, Vincent Lefevre wrote:
> > On 2023-08-18 07:35:33 +0200, Ansgar wrote:
> > > Please investigate why "usrmerge" is not installed (I assume this is an
> > > upgraded system).  Or, if it is installed, why /bin, /sbin, /lib* are
> > > not symlinks to their respective counterparts in /usr.
> > 
> > I've not upgraded init-system-helpers to 1.65.2 yet
> 
> Please don't file RC bugs if you intentionally break your system.
> Probably not non-RC bugs either.

First, I initially wasn't aware that this was assuming usrmerge:
there was no announce at all. Moreover, doing partial upgrades
is not breaking the system. This is perfectly allowed. That's why
there is a dependency system, and here, no Depends or Recommends
was broken.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1042757: ublock-origin: embded javascript lib

2023-08-19 Thread Markus Koschany

Am Samstag, dem 19.08.2023 um 06:13 + schrieb Bastien Roucariès:
> [...]
> No unfortunatly this is transpiled aka compiled by webpack
> see the first line
> export default (function() {
> 
> This is make by webpack or rollup that are automated tools. This means that
> this code is transpiled and I do not know the extend of transpiling.
> 
> it may be only the es6 upstream code:
> https://sources.debian.org/src/node-punycode/2.2.3-2/scripts/prepublish.js/
> or something worst that replace the constant by something else.
> 
> if you see the original code here:
> https://sources.debian.org/src/node-punycode/2.2.3-2/punycode.js/
> 
> you do not see the export default (function() { 
> line
> 
> Javascript is strange you could edit generated file and min.js is not the
> only problem

Ok, I see. I don't think this a problem though. This is still reasonably
modifiable and human readable.

Markus


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

Processed: ghc: Please upgrade to llvm-toolchain-14

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

> retitle 1017663 Please upgrade to llvm-toolchain-16
Bug #1017663 [src:ghc] ghc: Please upgrade to llvm-toolchain-14
Changed Bug title to 'Please upgrade to llvm-toolchain-16' from 'ghc: Please 
upgrade to llvm-toolchain-14'.
> thanks
Stopping processing here.

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

Bug#1041270: marked as done (dynarmic: broke ABI without SONAME bump)

Your message dated Sat, 19 Aug 2023 08:10:10 +
with message-id 
and subject line Bug#1041270: fixed in dynarmic 6.5.0+ds-1
has caused the Debian Bug report #1041270,
regarding dynarmic: broke ABI without SONAME bump
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.)


-- 
1041270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dynarmic
Version: 6.4.8+ds-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/y/yuzu/35884387/log.gz

 60s yuzu-cmd: symbol lookup error: yuzu-cmd: undefined symbol: 
_ZN8Dynarmic3A327Context4RegsEv

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: dynarmic
Source-Version: 6.5.0+ds-1
Done: Andrea Pappacoda 

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

Debian distribution maintenance software
pp.
Andrea Pappacoda  (supplier of updated dynarmic package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 21 Jul 2023 11:44:38 +0200
Source: dynarmic
Binary: libdynarmic-dev libdynarmic6.5 libdynarmic6.5-dbgsym
Architecture: source amd64
Version: 6.5.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Andrea Pappacoda 
Changed-By: Andrea Pappacoda 
Description:
 libdynarmic-dev - ARM dynamic recompiler - development
 libdynarmic6.5 - ARM dynamic recompiler
Closes: 1041270
Changes:
 dynarmic (6.5.0+ds-1) unstable; urgency=medium
 .
   * New upstream version 6.5.0+ds
 - Closes: #1041270
   * d/control: libdynarmic6 -> libdynarmic6.5
Checksums-Sha1:
 4a3ee42fbe6e7b6008233fcdba8aa1b523f80144 2330 dynarmic_6.5.0+ds-1.dsc
 e9a5e948bf001e52474a9fcf0c0330dfd3a6ed25 441324 dynarmic_6.5.0+ds.orig.tar.xz
 0f927383e0056b0197c25383791ea4b98161d62e 7048 dynarmic_6.5.0+ds-1.debian.tar.xz
 13e02566142dbc4863e95a1ba48593fbb03eacbe 8567 
dynarmic_6.5.0+ds-1_amd64.buildinfo
 dcf55229db4096446447c4296c5981ef28742d48 79848 
libdynarmic-dev_6.5.0+ds-1_amd64.deb
 9258434e1acf76dbafd30e02366e1a64a5bf596a 16560664 
libdynarmic6.5-dbgsym_6.5.0+ds-1_amd64.deb
 dcb70014f6a5e45e73b16f034ba22b43be2ce08d 1065368 
libdynarmic6.5_6.5.0+ds-1_amd64.deb
Checksums-Sha256:
 b1ea07d263e0b37aa9f965a0f81d49ce8ee3a31fdc50749bf9201c84a8de3c0b 2330 
dynarmic_6.5.0+ds-1.dsc
 46a18274c7d15c9bcc9eced74d050af412728ebf03083b76fb650b70acf8 441324 
dynarmic_6.5.0+ds.orig.tar.xz
 29aeb239a4cfba7248818dbbf1a7080bae61f9f960a8409aaafbe0cd93b507bb 7048 
dynarmic_6.5.0+ds-1.debian.tar.xz
 fd2d867a23f3c0bf568679af565549d2cb4aefd7722a9468ec50527607c014f5 8567 
dynarmic_6.5.0+ds-1_amd64.buildinfo
 2f7e34f21cd1dfde04ad7efe4b3e1fd71a2f0f83ec72b9ca5ed9619a1a2184fa 79848 
libdynarmic-dev_6.5.0+ds-1_amd64.deb
 36a125443965071436a26feffe267dae716416b6e2c9adf5f06e956848218c4d 16560664 
libdynarmic6.5-dbgsym_6.5.0+ds-1_amd64.deb
 69a87554f727f3499b66e4edf7bac1a8af3627522cf87bcb9f38e463095739d6 1065368 
libdynarmic6.5_6.5.0+ds-1_amd64.deb
Files:
 0bac49e6defc3bfc3dea90d9560912a8 2330 libs optional dynarmic_6.5.0+ds-1.dsc
 1a6c0b681687ce8ff2fbd67534dcaeba 441324 libs optional 
dynarmic_6.5.0+ds.orig.tar.xz
 8520cbd8bba719b7516d7c2424800e56 7048 libs optional 
dynarmic_6.5.0+ds-1.debian.tar.xz
 1e47cf2065ffdd6ff55b1b1470111738 8567 libs optional 
dynarmic_6.5.0+ds-1_amd64.buildinfo
 40e6f05e105eac7c943353f8ca827de3 79848 libdevel optional 
libdynarmic-dev_6.5.0+ds-1_amd64.deb
 24a3ea5c13f04e775c329be026530b27 16560664 debug optional 
libdynarmic6.5-dbgsym_6.5.0+ds-1_amd64.deb
 0d7c778a9fa9ee353ae8a66821520b5f 1065368 libs optional 
libdynarmic6.5_6.5.0+ds-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTfeM4QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFP3uDADDSKr1xuCRNoY2/sQpNu4cu4bRWuWnf7mE
09EzRmId/7OzsGJGPihvBgTFTsbfqvxy7SsPjTxWBDEVcshfsJD6u5Y5BT/WSKXu
7+D7lTr8sfB+3BT48Bgxc3vmHm1H1e3dO2KOPrKjM7EvnC9ujOEKvsUXBTtGOZNN
g7erEviCUHN0V3CFGl2WAogXi+BcGfOrmr9jAfCtXg+0rWwcUn5sGC+8hkpixZbC
KbOPrBfmvw72mxLEbwBZwsa0WoDBHSEk3ecEexe9vUqR93yGFqwtcZsHjO8M09tK

Processed: moc: FTBFS with ffmpeg 6.0

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

> forwarded 1041504 https://moc.daper.net/node/3644
Bug #1041504 [src:moc] moc: FTBFS with ffmpeg 6.0
Set Bug forwarded-to-address to 'https://moc.daper.net/node/3644'.
> --
Stopping processing here.

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

Bug#1041116: marked as done (orthanc-postgresql FTBFS with googletest 1.13.0)

Your message dated Sat, 19 Aug 2023 08:36:25 +0200
with message-id <7e6b685b-7254-0540-9116-9923da7ab...@orthanc-labs.com>
and subject line Re: orthanc-postgresql FTBFS with googletest 1.13.0
has caused the Debian Bug report #1041116,
regarding orthanc-postgresql FTBFS with googletest 1.13.0
to be marked as done.

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

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

--
1041116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orthanc-postgresql
Version: 4.0-7
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/orthanc-postgresql.html

...
In file included from /usr/include/gtest/gtest-message.h:57,
from /usr/include/gtest/gtest-assertion-result.h:46,
from /usr/include/gtest/gtest.h:64,
from
/build/1st/orthanc-postgresql-4.0/PostgreSQL/UnitTests/PostgreSQLTests.cpp:22:
/usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less
than C++14 are not supported.
270 | #error C++ versions less than C++14 are not supported.
| ^
...

This can be fixed by changing -std=gnu++11 to -std=gnu++14
in Resources/Orthanc/CMake/DownloadOrthancFramework.cmake
--- End Message ---
--- Begin Message ---

Package: orthanc-postgresql
Version: 5.0+dfsg-1

This bug was filed against an old version of the "orthanc-postgresql"
package version that now corresponds the "stable" Debian distribution
(i.e. orthanc-postgresql/4.0-7).

But, this issue was fixed in the "orthanc-postgresql/5.0+dfsg-1" version
that was uploaded almost simultaneously to this bug report. I have just
checked that the FTBFS is not present anymore with the new version
inside the "unstable" distribution.--- End Message ---

Bug#1050066: adequate: autopkgtest fails on !amd64


Source: adequate
Version: 0.15.7
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails on all 
architectures but amd64. Can you please investigate the situation and 
fix it? I copied some of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing.


More information about this bug and the reason for filing it can be 
found on 
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/arm64/a/adequate/36619533/log.gz

 65s check adequate-testpkg-symbol-size-mismatch ... FAIL
 65s -adequate-testpkg-symbol-size-mismatch: symbol-size-mismatch 
/usr/bin/adequate-test-symsize => this_symbol_size_varies




OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1042757: ublock-origin: embded javascript lib

2023-08-19 Thread Bastien Roucariès

Le vendredi 18 août 2023, 23:16:04 UTC Markus Koschany a écrit :
> Am Montag, dem 31.07.2023 um 11:56 + schrieb Bastien Roucariès:
> > Source: ublock-origin
> > Severity: serious
> > Justification: not prefered form of modification
> > 
> > Dear Maintainer,
> > 
> > src/lib include a few library that are already packaged for debian.
> > 
> > per se it is not a serious bug, but we should try if possible after testing
> > to
> > use packaged version
> > 
> > The serious bug is due that for instance punycode was not in prefered form 
> > of
> > modification due to being wepackaged (transpiled) in order to be an ES
> > module.
> > 
> > They may be other transpiled package in this subdirectory
> 
> Hello Bastien,
> 
> thanks for the report. I have reviewed the src/lib directory and replaced the
> embedded Javascript libraries of csstree and js-beautify with Debian's system
> libraries. I also added the source file of hsluv to debian/missing-sources and
> documented the licenses of these three Javascript libraries in
> debian/copyright.
> 
> I decided against replacing punycode because punycode.js in ublock-origin 
> looks
> like the preferred form for me.

No unfortunatly this is transpiled aka compiled by webpack
see the first line
export default (function() {

This is make by webpack or rollup that are automated tools. This means that 
this code is transpiled and I do not know the extend of transpiling.

it may be only the es6 upstream code:
https://sources.debian.org/src/node-punycode/2.2.3-2/scripts/prepublish.js/
or something worst that replace the constant by something else.

if you see the original code here:
https://sources.debian.org/src/node-punycode/2.2.3-2/punycode.js/

you do not see the export default (function() { 
line

Javascript is strange you could edit generated file and min.js is not the only 
problem

Thanks

Bastien

> The file is not minified and can be edited
> without problems. I believe you were referring to hsluv instead. I believe 
> this
> issue is fixed in version 1.51.0+dfsg-2 soon.
> 
> Regards,
> 
> Markus
> 
> 



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

Processed: src:rust-async-executor: fails to migrate to testing for too long: autopkgtest regression

Processing control commands:

> close -1 1.5.1-3
Bug #1050064 [src:rust-async-executor] src:rust-async-executor: fails to 
migrate to testing for too long: autopkgtest regression
Marked as fixed in versions rust-async-executor/1.5.1-3.
Bug #1050064 [src:rust-async-executor] src:rust-async-executor: fails to 
migrate to testing for too long: autopkgtest regression
Marked Bug as done

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

Bug#1050064: src:rust-async-executor: fails to migrate to testing for too long: autopkgtest regression


Source: rust-async-executor
Version: 1.5.0-3
Severity: serious
Control: close -1 1.5.1-3
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

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:rust-async-executor has been trying to 
migrate for 34 days [2]. Hence, I am filing this bug. The version in 
unstable fails its own autopkgtest.


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=rust-async-executor



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:gcc-11-cross-mipsen: fails to migrate to testing for too long: uploader built arch:all binaries

Processing control commands:

> close -1 6+c1
Bug #1050063 [src:gcc-11-cross-mipsen] src:gcc-11-cross-mipsen: fails to 
migrate to testing for too long: uploader built arch:all binaries
Marked as fixed in versions gcc-11-cross-mipsen/6+c1.
Bug #1050063 [src:gcc-11-cross-mipsen] src:gcc-11-cross-mipsen: fails to 
migrate to testing for too long: uploader built arch:all binaries
Marked Bug as done

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

Bug#1050063: src:gcc-11-cross-mipsen: fails to migrate to testing for too long: uploader built arch:all binaries


Source: gcc-11-cross-mipsen
Version: 5+c3
Severity: serious
Control: close -1 6+c1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

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:gcc-11-cross-mipsen has been trying to 
migrate for 35 days [2]. Hence, I am filing this 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.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1050061: src:rust-rustls: fails to migrate to testing for too long: blocked by RC buggy package


Source: rust-rustls
Version: 0.20.8-4.1
Severity: serious
Control: close -1 0.21.6-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

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:rust-rustls has been trying to migrate for 
32 days [2]. Hence, I am filing this bug. The version in unstable build 
depends on a package that doesn't exist in testing but that won't 
migrate because it's RC buggy (fails its own autopkgtests).


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=rust-rustls



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:node-lib0: fails to migrate to testing for too long: autopkgtest regression on armel

Processing control commands:

> close -1 0.2.77-1
Bug #1050062 [src:node-lib0] src:node-lib0: fails to migrate to testing for too 
long: autopkgtest regression on armel
Marked as fixed in versions node-lib0/0.2.77-1.
Bug #1050062 [src:node-lib0] src:node-lib0: fails to migrate to testing for too 
long: autopkgtest regression on armel
Marked Bug as done

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

Bug#1050062: src:node-lib0: fails to migrate to testing for too long: autopkgtest regression on armel


Source: node-lib0
Version: 0.2.58-1
Severity: serious
Control: close -1 0.2.77-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

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:node-lib0 has been trying to migrate for 
34 days [2]. Hence, I am filing this bug. The version in unstable fails 
its own autopkgtests on armel.


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=node-lib0



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:rust-rustls: fails to migrate to testing for too long: blocked by RC buggy package