Your message dated Sat, 26 Nov 2022 19:37:49 +0000
with message-id <e1oz0zl-007gyu...@fasolo.debian.org>
and subject line Bug#1024828: fixed in r-cran-lexrankr 0.5.2-3
has caused the Debian Bug report #1024828,
regarding src:r-cran-igraph: fails to migrate to testing for too long:
autopkgtest regression on i386
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.)
--
1024828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-igraph
Version: 1.3.4-1
Severity: serious
Control: close -1 1.3.5-1
Tags: sid bookworm
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 60 days as having a Release Critical bug in
testing [1]. Your package src:r-cran-igraph has been trying to migrate
for 61 days [2]. Hence, I am filing this bug. Your package causes a
regression in r-cran-lexrankr on 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 bookworm, 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-igraph
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-lexrankr
Source-Version: 0.5.2-3
Done: Andreas Tille <ti...@debian.org>
We believe that the bug you reported is fixed in the latest version of
r-cran-lexrankr, 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 1024...@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-lexrankr 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: Sat, 26 Nov 2022 20:13:58 +0100
Source: r-cran-lexrankr
Architecture: source
Version: 0.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers <r-pkg-t...@alioth-lists.debian.net>
Changed-By: Andreas Tille <ti...@debian.org>
Closes: 1024828
Changes:
r-cran-lexrankr (0.5.2-3) unstable; urgency=medium
.
* Set tolerance for test
Closes: #1024828
* Standards-Version: 4.6.1 (routine-update)
* Reorder sequence of d/control fields by cme (routine-update)
* Set upstream metadata fields: Bug-Database, Bug-Submit.
* lintian-overrides (see lintian bug #1017966)
Checksums-Sha1:
3bfa7a517b15d01cf1eee7cb84b748cac96acb41 2157 r-cran-lexrankr_0.5.2-3.dsc
0d5f9791fe59d973ea27e362e8e7f091694db988 3824
r-cran-lexrankr_0.5.2-3.debian.tar.xz
7c97bbcc89a6e15b583c48bcb088d4b3f37eea91 11131
r-cran-lexrankr_0.5.2-3_amd64.buildinfo
Checksums-Sha256:
e4b1e4bf841050a2ff98431bca6c19899f1909393855c983f25f67e3bcb8a1e4 2157
r-cran-lexrankr_0.5.2-3.dsc
3ca0a14f916c6a89d62a77dec2ec3e19a810d39f89b23ca8a0fcb834e30dd17f 3824
r-cran-lexrankr_0.5.2-3.debian.tar.xz
2c6d83b6a522dd0d5bb20b65d8a31b18afd2bc7cd6c84d36c55780092f4a9363 11131
r-cran-lexrankr_0.5.2-3_amd64.buildinfo
Files:
bbf2160ee450340a7fdde84f54e37f90 2157 gnu-r optional
r-cran-lexrankr_0.5.2-3.dsc
9b9966e31cceba1f32cf1b33625ace84 3824 gnu-r optional
r-cran-lexrankr_0.5.2-3.debian.tar.xz
95cfd1df97a97cf517fb692f94d0505f 11131 gnu-r optional
r-cran-lexrankr_0.5.2-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmOCZfgRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE+pA//QYDNjUDw1TWto4Rri03tE5dtRTi6M8X1
ELXzJ8PAEv1NiAxkVdBWolrWKcQU1aqeiwabVO51X57HdHyH6986aOsPorsmLxRx
LaqJRQ7XOPP1e8haCl5pArLXXHdXUK3TL0QP8zevtGbmJ1PJsNVTrtJ9DWuNNoaR
ZtrwU2Z4KnsVFTlj2V+phSlIQ8i0NB2RaBW7H2XBwfSA+4P2bDwQrQp1fZ4c4HX8
fDDtXuSJct+aEWPF9sgEWEdWaqm0gxQz5FMe+MCEKEW3USRPoQiQ5agZuQ7rPVMc
nSPiyuNRjghXMAdbFAcne5G+zxuAunVf4po3vZVFLLT9S/LNl9dk3pzf3czIPq3J
S8PE3kglIXO3OxWCZzlJu7GBh/MwUC1QyVvuFnUVBjnWAIrF3eGDyu4N/Km/F+C1
vGJ4HR47eOvs92OvFHRqTweBhTkmuSUVy9iOUz2ensNYZrMxdO0fzlS8USK8dgM0
Wzp4PU22oPbJCee76YFiGJQ3r6zL2LktYMM/PQ2U+YhtyjPmu1zpJ/haKhlv1w5S
9iWIX4xirk1WupU+/gpq2Q6KiQ1syPMtvK5aheLw1emeYKCwtXSpe7iFAu3HybuH
ip5z3JrBBLNuZ5rhlZAnUllRh8U827ZbLxEhvnYCMK8YvfI7AUczRX2vMpBchhCl
kgzbFRfVca4=
=qItG
-----END PGP SIGNATURE-----
--- End Message ---
