Your message dated Wed, 30 Sep 2020 14:36:40 +0000
with message-id <[email protected]>
and subject line Bug#971233: fixed in r-cran-rstan 2.21.2-2
has caused the Debian Bug report #971233,
regarding src:r-cran-rstan: fails to migrate to testing for too long:
autopkgtest regression and missing build on armel
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.)
--
971233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971233
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: r-cran-rstan
Version: 2.19.3-1
Severity: serious
Control: close -1 2.21.2-1
Tags: sid bullseye
User: [email protected]
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:r-cran-rstan
in its current version in unstable has been trying to migrate for 62
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 bullseye, 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/2020/02/msg00005.html
[2] https://qa.debian.org/excuses.php?package=r-cran-rstan
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-rstan
Source-Version: 2.21.2-2
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
r-cran-rstan, 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-rstan 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: SHA256
Format: 1.8
Date: Wed, 30 Sep 2020 15:54:55 +0200
Source: r-cran-rstan
Architecture: source
Version: 2.21.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 971109 971233
Changes:
r-cran-rstan (2.21.2-2) unstable; urgency=medium
.
[ Shayan Doust ]
* Library locations are under /usr/share/R and not the relative directory
lib/
Closes: #971233
* Versioned Build-Depends: r-cran-rcppparallel (>= 5.0.2+dfsg-3)
Closes: #971109
Checksums-Sha1:
69e4e63c17d0085ea6dfb8282b510ca81be5db76 2347 r-cran-rstan_2.21.2-2.dsc
f69da2a5a24aaf4d87433105f8dbf4325a65adcf 4008
r-cran-rstan_2.21.2-2.debian.tar.xz
5f5386283765560e7d9e0f04d6ce59c230fa70eb 10799
r-cran-rstan_2.21.2-2_amd64.buildinfo
Checksums-Sha256:
cedf8f984304beb29d4c3d9c55b9f8880a980b35d6a86ba0958c63be6bee0c1b 2347
r-cran-rstan_2.21.2-2.dsc
d4338e86112a55c7c1745d9f776bbd96ba7b0370f73549ccc052bdab38b67531 4008
r-cran-rstan_2.21.2-2.debian.tar.xz
d0e883ab52d0ee74b955af9099a545c806c7bd80208ece27f0ee717ec3f7eada 10799
r-cran-rstan_2.21.2-2_amd64.buildinfo
Files:
1947df1ff9d652170d2a713d80865752 2347 gnu-r optional r-cran-rstan_2.21.2-2.dsc
b71887a46c0db03d3c8e4bc734825d76 4008 gnu-r optional
r-cran-rstan_2.21.2-2.debian.tar.xz
6dd51921f75fa2ca1ddd2e8da4e00c13 10799 gnu-r optional
r-cran-rstan_2.21.2-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl90klcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEWmg/+LX4nCJBURlDTR8e1hOVgix3w7qzOxmoB
RhiNaK5FeqOVu2/61yi4l2v2LLoSFIzTpWejxEZTavePKI+EGrNSuaLwmrJRyvrF
go1r1ISlbQBv5mqbwVDyYwx9EtyzVw7KraE8ZuFGQu6SxrwyBEE9Y3jf9Qru0jKM
dnbd/5koQosKdVDZXiSoyeNuM5aK9iD57Ig5OXMPeP541upWoASratoxz/RGEhum
5v+1WvuaVG79MA1qbh/UGmBvpnJg5jnTyS7AqF0ZG47N76RFj0JWlB+xp2K6L6r8
NuqHnLgj2XoioDUVaxhVd7lE5uh+/xSF8/CqnuljHNItE2CDWzvwLQYnV5PdJu0u
SY4k2B26TpMSa2ZZI4WKJ1A/65dYPVEsi36yup4SzaUT+xXYNo3qe1dUWlHiph58
zx4AmNJ5qbTeLRmKRDWcIcEwp+jyAPWxOe554jAvA4Y+BgFF9VjVefE7GZtoAy5E
FzLXo8vTH50Asgq+pExxzUqQFuTrDNDJfKfnHi6gpx6mTJu6rEN1xGju6L9Ws/jy
HqyArD7v09mSnDBF9oMOdc/Uf9qZhpehcZv+Q4Le9t5pP8ufQlaTzZO3nO1Z0U1v
C9SkXI/ckH26vsbRCaXV2Ftk6Oqv7BZ6GvdEK/6Dh/6FKjjw8fDQBz62liAwY3Yk
Vg0xs79IQI0=
=gbNF
-----END PGP SIGNATURE-----
--- End Message ---
