Your message dated Sun, 13 Apr 2025 08:57:42 +0000
with message-id <e1u3t9q-00ekei...@fasolo.debian.org>
and subject line Bug#1102109: fixed in r-cran-bit64 4.6.0-1-2
has caused the Debian Bug report #1102109,
regarding src:r-cran-bit64: fails to migrate to testing for too long
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.)
--
1102109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-bit64
Version: 4.0.5-1
Severity: serious
Control: close -1 4.6.0-1-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-bit64 has been trying to migrate
for 33 days [2], hence this bug report. The current output of the
migration software for this package is copied to the bottom of this
report and should list the reason why the package is blocked.
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.
This bug submission immediately closes the bug with the version in
unstable, so if that version or a later version migrates, this bug will
no longer affect testing. This bug is also tagged 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.
This bug report has been automatically generated and has only been sent
manually. If you have any comments with regards to the content or the
process, please reach out to me.
Paul
[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=r-cran-bit64
Current text from [2]:
Migration status for r-cran-bit64 (4.0.5-1 to 4.6.0-1-1): BLOCKED:
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ autopkgtest for r-cran-bit64/4.6.0-1-1: amd64: Regression or new
test ♻ (reference ♻), arm64: Regression or new test ♻ (reference ♻),
armel: Regression or new test ♻ (reference ♻), armhf: Regression or new
test ♻ (reference ♻), i386: Regression or new test ♻ (reference ♻),
ppc64el: Regression or new test ♻ (reference ♻), riscv64: Regression or
new test ♻ (reference ♻), s390x: Regression or new test ♻ (reference ♻)
Additional info:
∙ ∙ Piuparts tested OK -
https://piuparts.debian.org/sid/source/r/r-cran-bit64.html
∙ ∙ Reproducible on amd64 - info ♻ ∙ ∙ Reproducible on arm64 - info ♻ ∙
∙ Waiting for reproducibility test results on armhf - info ♻ ∙ ∙
Reproducible on i386 - info ♻ ∙ ∙ 33 days old (needed 5 days)
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-bit64
Source-Version: 4.6.0-1-2
Done: Andreas Tille <ti...@debian.org>
We believe that the bug you reported is fixed in the latest version of
r-cran-bit64, 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 1102...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille <ti...@debian.org> (supplier of updated r-cran-bit64 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 13 Apr 2025 10:24:38 +0200
Source: r-cran-bit64
Architecture: source
Version: 4.6.0-1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers <r-pkg-t...@alioth-lists.debian.net>
Changed-By: Andreas Tille <ti...@debian.org>
Closes: 1102109
Changes:
r-cran-bit64 (4.6.0-1-2) unstable; urgency=medium
.
* Fix autopkgtest (Closes: #1102109)
Checksums-Sha1:
27a63417e65364397da44dce1cee762fe5d3c5bb 2118 r-cran-bit64_4.6.0-1-2.dsc
ac8ba7ff8f9385150888a21cede4361375e3e952 2804
r-cran-bit64_4.6.0-1-2.debian.tar.xz
c2026df6cbdc956180a981283ffe899a6f22b8ef 11460
r-cran-bit64_4.6.0-1-2_amd64.buildinfo
Checksums-Sha256:
44005d1b04dd503c75980bb41a6663b7ec614365a977c42fcef7ecf896ab3eee 2118
r-cran-bit64_4.6.0-1-2.dsc
7fd3f4d4646b547e254d5a7bb78bfd7961e3b854a3b2906589f49e8d01a49b51 2804
r-cran-bit64_4.6.0-1-2.debian.tar.xz
19281162d56cfdcd6917611bc077c2087a5d3357e03191e247a8cee820ebd867 11460
r-cran-bit64_4.6.0-1-2_amd64.buildinfo
Files:
dd11a710a04c81780cfa576c72693b1d 2118 gnu-r optional r-cran-bit64_4.6.0-1-2.dsc
d256448f128eaef56ab94d5834e8bcbc 2804 gnu-r optional
r-cran-bit64_4.6.0-1-2.debian.tar.xz
45c0546c439c5044fb6033bd5ffef4d5 11460 gnu-r optional
r-cran-bit64_4.6.0-1-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmf7dawRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtH3tg//ewCin3ohY630khMiOO9xroZy4W77PNH6
+gk07W/u7agZefpZdqCS9lJJhOHn9ttJxUWQdOfixAKC+gbMV+4kAm7AkoRUPIO3
dEscLAepD9rzWVY6BUoCxXRmhVIdERq4HQUXBCy9oz0+pWzc2quGKHH2GbndLKGO
86HtNwuyz6OBeuU3f+j8mcS1DgCM49nnU+50K9uPppAsyEix4qgSmHmgTF6ItYV/
4M8yBlG+lRf3JZ7ezqoEgxcH8ESndxylq5XvLB6dkoBNwsJtIHtsG511k4ATcLxR
iX/keYAaOv/RFwEOtb8IBuz9/q8/XQ/Th7Nj4/hJZxVvRbQ67opG86bco/RbIUbJ
RAJy0SojS3FrVtrg3x6KZ+Vgo1nV1dvxFG4deEkK66pkSfSeC2Eq89ZOKSuicvcl
BTtyv1M3QwscoQTuVh2vCkmwrZEGZes//YJxnRRhSuEAOFQ4fdDPe6s3MPL1yWu0
ZnKp3nf+2aXgyyq3XjmQxIN7yTbpfqRG+eYvocXkmCYHw4RTb3ZOEuP+adAMv96z
I9r66Ja1fgSranIh8mUHPD1xwyDMbxvYe5w4KUnH2J5zYrgP3FwM9HUxb5m3AfF8
xfKBUy6ce46V06w0crN1l38s2VtZARPEosA4vvalTlF7WOR6u9IeZaN6QSWiYL3p
cWSa5XvcXDA=
=YeX8
-----END PGP SIGNATURE-----
pgpnaJXksEYNG.pgp
Description: PGP signature
--- End Message ---
