Your message dated Mon, 12 May 2025 04:34:13 +0000
with message-id <e1uekrl-003kkd...@fasolo.debian.org>
and subject line Bug#1064135: fixed in r-cran-bigmemory 4.6.4-2
has caused the Debian Bug report #1064135,
regarding src:r-cran-bigmemory: fails to migrate to testing for too long:
autopkgtest fails on arm*, ppc64el and s390x
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.)
--
1064135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-bigmemory
Version: 4.6.1-1
Severity: serious
Control: close -1 4.6.4-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-bigmemory has been trying to
migrate for 31 days [2]. Hence, I am filing this bug. The version in
unstable added an autopkgtest (thanks for that), but it fails 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-bigmemory
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-bigmemory
Source-Version: 4.6.4-2
Done: Charles Plessy <ple...@debian.org>
We believe that the bug you reported is fixed in the latest version of
r-cran-bigmemory, 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 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Charles Plessy <ple...@debian.org> (supplier of updated r-cran-bigmemory
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 12 May 2025 11:58:25 +0900
Source: r-cran-bigmemory
Architecture: source
Version: 4.6.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers <r-pkg-t...@alioth-lists.debian.net>
Changed-By: Charles Plessy <ple...@debian.org>
Closes: 1064135
Changes:
r-cran-bigmemory (4.6.4-2) unstable; urgency=medium
.
* Team upload.
* Force the use of signed chars on all architectures (Closes: #1064135)
Checksums-Sha1:
e61c4e0e384eae92c253b5332c3e5ac3f271969d 2219 r-cran-bigmemory_4.6.4-2.dsc
b25c77782d0a00885e772e2a2a2d1e6520f4c287 3516
r-cran-bigmemory_4.6.4-2.debian.tar.xz
5d0e07ed32655f8d4fc843cd9840f0a42124058f 11764
r-cran-bigmemory_4.6.4-2_amd64.buildinfo
Checksums-Sha256:
f6cd1eb114ca7f5646e1ea9589335e75a94b4f95f3f16aec780da5816daae835 2219
r-cran-bigmemory_4.6.4-2.dsc
6af5b363e9721472c8cdce15d93a98be9f7a61deaa5acb4f2765134dac8a0b48 3516
r-cran-bigmemory_4.6.4-2.debian.tar.xz
3a1e17ba30737da7504be9159d5adc52af8858ad85ce3d156b7f4bff00c36f2f 11764
r-cran-bigmemory_4.6.4-2_amd64.buildinfo
Files:
800621cdb01a7e750fc4144188c8380c 2219 gnu-r optional
r-cran-bigmemory_4.6.4-2.dsc
3fc4d9db2574819ea53765cf02f85129 3516 gnu-r optional
r-cran-bigmemory_4.6.4-2.debian.tar.xz
519801b1d4dc5d10ae85ee76d178ecae 11764 gnu-r optional
r-cran-bigmemory_4.6.4-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCgAwFiEEc0cUmcxg7Z7ugFlGxb1sjyKV1QIFAmghdesSHHBsZXNzeUBk
ZWJpYW4ub3JnAAoJEMW9bI8ildUCuaEQALQDjHUTwdLzUIvhp/pjWobTLnZJduxE
zhaYXgMw0BVDk0n4vQd1oDhIghLHVce93+ra9rXkRTXrBxU+92LeorvPISIOkjH2
6DFw/ubfXzwifBMyYah1FWnyhUOJNsfy0eiS2myYva9tKI4MkKmu32O/a5Cwhetm
X9jIvtYK5YZVl/P3pu3LoE8VKQY2Q43Oa65o8KH8CmcuRH9evDRT0VKzkZ19HlNx
InmQzQMTVn8lUSJYBbJSWACMNWeJORNknSg5Jd0hxnQAwVhBD5kqB6RNEwagaK4a
oRLoO8ihHRA8bBuvKDDsoePWy+hJojpHi8AtNM09ifi99f064eq6v8g8nf0mXYrj
yBARh7JfEiGXzSHluNWKDXIyumSYJ3KcoPwcexCtCsHjT5EgPmKNCdRxdT3yWQPL
QWZB2TPUAgaT1E5gkqWiwcZ5aqCVvKF58a/BOKWX3VkfTzNye7zwuhvfcf4Py/EV
7v/YEaxvx5q0P/TDCY8FH158ykubGDI/HNR+mpZ3Qdegs8C/RzpGjP4APNNQqfvH
52dwJhoVw3Iyuk59nLV/OvaxFoBw8q9nMSoFUYrM8yNFT4QB+ak7dSUDxrLQP6BX
rNuBIxeRKeRfpjlgJOskbWbpa+1B3/drCs4+erg15XLZGh4V0nTJAl5uRzeElJju
dMXOUfpWzPNe
=KXWN
-----END PGP SIGNATURE-----
pgpJlvS9GCF5P.pgp
Description: PGP signature
--- End Message ---
