Your message dated Mon, 28 Sep 2020 15:05:02 +0000
with message-id <e1kmui6-0002eo...@fasolo.debian.org>
and subject line Bug#971236: fixed in r-cran-fs 1.5.0+dfsg-1
has caused the Debian Bug report #971236,
regarding src:r-cran-fs: 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 ow...@bugs.debian.org
immediately.)


-- 
971236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-fs
Version: 1.4.1+dfsg-1
Severity: serious
Control: close -1 1.4.2+dfsg-1
Tags: sid bullseye
User: release.debian....@packages.debian.org
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-fs in
its current version in unstable has been trying to migrate for 60 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-fs


Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: r-cran-fs
Source-Version: 1.5.0+dfsg-1
Done: Andreas Tille <ti...@debian.org>

We believe that the bug you reported is fixed in the latest version of
r-cran-fs, 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 971...@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-fs 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: Mon, 28 Sep 2020 16:29:32 +0200
Source: r-cran-fs
Architecture: source
Version: 1.5.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers <r-pkg-t...@alioth-lists.debian.net>
Changed-By: Andreas Tille <ti...@debian.org>
Closes: 971236
Changes:
 r-cran-fs (1.5.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream version (exclude any version of libuv)
   * Test-Depends: r-cran-vctrs, r-cran-tibble, r-cran-pillar, r-cran-crayon,
                   r-cran-knitr, r-cran-withr, r-cran-covr, r-cran-rmarkdown
   * Rewrite run-unit-test script
     Closes: #971236
Checksums-Sha1:
 3e375796ee3d2cc31b9ef91337c397db76d56a6b 2204 r-cran-fs_1.5.0+dfsg-1.dsc
 9657495ec05668d7ea8525c077fc5f1148c171a9 77176 r-cran-fs_1.5.0+dfsg.orig.tar.xz
 0b632a55cb59b3de7ffaeff74c73a3dbafc483e7 3960 
r-cran-fs_1.5.0+dfsg-1.debian.tar.xz
 7a96fd293411e62a00d4136366cbdec1e38ba0b9 8816 
r-cran-fs_1.5.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 9aeeb429e8828c7993ae95ce5a8ad74cf37664247ab8735aa6b5ea37672447c0 2204 
r-cran-fs_1.5.0+dfsg-1.dsc
 a0bb16fbea340b5d77d79abb02ce885b32837e548e56fc1a371a196b38744477 77176 
r-cran-fs_1.5.0+dfsg.orig.tar.xz
 b5413aa00ae5ece836eee7f388f0da1c49c35c0bebd9a26ad4b0a9482850b6dd 3960 
r-cran-fs_1.5.0+dfsg-1.debian.tar.xz
 be62c09baf97bbc5026762686f3ee5357f52f96724808fd6a01bd1a0780ea4b5 8816 
r-cran-fs_1.5.0+dfsg-1_amd64.buildinfo
Files:
 c3d01c7c6fc634b6eedf7b68d52f0d67 2204 gnu-r optional r-cran-fs_1.5.0+dfsg-1.dsc
 3c4c39efd6699429b810729759dd1b64 77176 gnu-r optional 
r-cran-fs_1.5.0+dfsg.orig.tar.xz
 e79e81981f71b37d8e822f519dfa3ee9 3960 gnu-r optional 
r-cran-fs_1.5.0+dfsg-1.debian.tar.xz
 03d22e6ada8ea31aaf2c7bd933bcdc45 8816 gnu-r optional 
r-cran-fs_1.5.0+dfsg-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl9x9BURHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFOJA//dpBwo0uzDETUhrlimNt1+eO7N27wsPfM
fO8emMtaDgQ8/6c2NTKO61mZalHE7Wy2QTv8tKV+g72rraSie26hv7uswNW18uWr
XcYpq5Yyj18vxjC6R+PCqQDHtgvJIfkprBulc5Hbni8MDYUlEr6wO8EHVNbZdHi0
GPfVmP6QdhPnpU/4dIz2cNc1U7KNND7K466rN3hSlmCpKqiBjkXwkLOjlW+DM3mj
TzHn/TfqwtsNFlYcpkwcwYAzvb7xLiuzQvZj4ho6HdnT6Rp8+DHzbWdkoqO/AUlm
qkXQYUzDmfLAIpD+EDYL7s7q6P8eoGvrHE5p4KjjGuzs/pBnFcglLHDbJnLjUo8n
Xy7gHnunYMwwLIhtHITyMaAONxSJER6/YKYc0Jm9l9q6l86iTT+WSNNRd7QJu4Wt
x7jmOdu2wWqGvOQp8fXgdFoizCQAp04APd2k0ixhw5UE08IO+8e548pbSlMNge7/
Ja/wXUpM3ZASTuU451ama3bYZaw7ceanhTWZxM0MAsqbuviZtmOZ0IRBE+ZoFbUQ
NisUmSuuVQtpLZSAWkTTEUVOxiaYwTGKQPFs/ms7Oa2oDcgEI2KL7U7aDkceDMEX
4JEVwLpWNt8qwOqRjQELlPNPqRvVqTWmy5xvQ/Cso+jURHxuuUwcP3ypTiQBfitQ
X7dTSSqACaI=
=O0w4
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to