Your message dated Fri, 05 Dec 2025 14:43:13 +0000
with message-id <[email protected]>
and subject line Bug#1064922: fixed in r-cran-gbm 2.2.2-2
has caused the Debian Bug report #1064922,
regarding src:r-cran-gbm: fails to migrate to testing for too long: 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 [email protected]
immediately.)
--
1064922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064922
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: r-cran-gbm
Version: 2.1.8.1-1
Severity: serious
Control: close -1 2.1.9-1
Tags: sid trixie
User: [email protected]
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-gbm has been trying to migrate for
31 days [2]. Hence, I am filing this bug. The version in unstable fails
its own autopkgtest everywhere except on amd64 and i386.
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/msg00001.html
[2] https://qa.debian.org/excuses.php?package=r-cran-gbm
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-gbm
Source-Version: 2.2.2-2
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
r-cran-gbm, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille <[email protected]> (supplier of updated r-cran-gbm 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 05 Dec 2025 14:29:46 +0100
Source: r-cran-gbm
Architecture: source
Version: 2.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1064922
Changes:
r-cran-gbm (2.2.2-2) unstable; urgency=medium
.
* Relax test conditions
Closes: #1064922
* d/watch: version=5
* Standards-Version: 4.7.2 (routine-update)
Checksums-Sha1:
6288ce22fdbbca4abd37a17dcb95e1e5d6419eff 2188 r-cran-gbm_2.2.2-2.dsc
75c5db5f00bab04b33e560de7ab7951e52f6e4ae 3844 r-cran-gbm_2.2.2-2.debian.tar.xz
8b9605d70f98636fead9c877226a15278c4cbf39 12375
r-cran-gbm_2.2.2-2_amd64.buildinfo
Checksums-Sha256:
1f77bf9ee74a3ed1a7e91f00338979e9e959c353f3421f9663db70169eb413fd 2188
r-cran-gbm_2.2.2-2.dsc
2bf3e0b2fce1016e8cf462d46124e5065bd5bb3ce8ddee04b7d560d06c765c0c 3844
r-cran-gbm_2.2.2-2.debian.tar.xz
18db96a0b988a0e5e24869ebce54d39f35ca3a545972c1bb608b48f661abebc7 12375
r-cran-gbm_2.2.2-2_amd64.buildinfo
Files:
7140bca838fb70be69e35c12b6aab220 2188 gnu-r optional r-cran-gbm_2.2.2-2.dsc
5fd2b64f39308ab36c1ef61bdbe0ce5d 3844 gnu-r optional
r-cran-gbm_2.2.2-2.debian.tar.xz
cc1c682764a3c5ad5fae7c95f61d9ffc 12375 gnu-r optional
r-cran-gbm_2.2.2-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmky3z8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHcNBAAjFF0OmHPIoMhOKU5Ey4+esNvKuzMKRxT
9WSxKb3iwgCp+hMbMfikcFNgj9EkWEdAhgVxAr8OHF2BYi6IGc0snB126cznzQIk
8t/RsnBEmHHanDsu6piyxwObWmQ86okrW5r5k+++Iw6zoWFHNOeoRk8Y7mvu0XRl
m1u8UQimYbxmv9wX3isGyNMxQ68hGL8WeykAO3+ZgIDFFMcRRdC6j4T5kKjhNZNC
+uR/w/hd6s4yvzoErD5WOqdB+yLkQw1xn29mdvT27CWWvA5zWaWuixWLjV7818RD
vsIpTR1yrqIMwicqYQZFJOaQVwMziAuUkbgKcTr6k+Nh6DXIA2hQLbOFSNGQRKTg
gFErxmT7J5iAPQW2CM12ImvsXNAT2eC5Ypqqah95xwLsBE6RT8oDebE0tyZ69Th4
816CT3AUnxET/h29gU0biPa8C4atCDFk2gDnTlD5lefXw6fAVkTPu3Y/B1UMzzGf
1xDnOT2HqGHOJSeZqttEcQjuYmUgBMXugtLcmCm4HL65aVT9N8BItTqCuapWaLQt
wZ0y2bSGvd7WW3sZZXWqZ0QvPBp9CBxA5IsMIAXIF750OZyRVgit/loCvgkDotgM
DyxwT9nYjAPLGPSB1HRaenW2Rk6R04TLXMXECPLJcMfLwjVf2zdc7JtMYFzj+3J3
6kXgmVMPkec=
=x+Yr
-----END PGP SIGNATURE-----
pgp3IhnaidVKa.pgp
Description: PGP signature
--- End Message ---
