Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #357821 > unrolled thread

Bug#1065338: src:r-cran-rpact: fails to migrate to testing for too long: autopkgtest failures

Back to article view | Back to linux.debian.bugs.rc

Contents

  Bug#1065338: src:r-cran-rpact: fails to migrate to testing for too long: autopkgtest failures Paul Gevers <elbrus@debian.org> - 2024-03-03 07:40 +0100
    Processed: src:r-cran-rpact: fails to migrate to testing for too  long: autopkgtest failures "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-03-03 07:40 +0100

#357821 — Bug#1065338: src:r-cran-rpact: fails to migrate to testing for too long: autopkgtest failures

[Multipart message — attachments visible in raw view] — view raw

Source: r-cran-rpact
Version: 3.4.0-1
Severity: serious
Control: close -1 3.5.0-1
Tags: sid trixie
User: release.debian.org@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-rpact has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version in unstable 
fails its own autopkgtest on some architectures: arm64, ppc64el and 
s390x (and i386, but that's not a regression).

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-rpact

[toc] | [next] | [standalone]

#357822 — Processed: src:r-cran-rpact: fails to migrate to testing for too long: autopkgtest failures

Processing control commands:

> close -1 3.5.0-1
Bug #1065338 [src:r-cran-rpact] src:r-cran-rpact: fails to migrate to testing for too long: autopkgtest failures
Marked as fixed in versions r-cran-rpact/3.5.0-1.
Bug #1065338 [src:r-cran-rpact] src:r-cran-rpact: fails to migrate to testing for too long: autopkgtest failures
Marked Bug as done

-- 
1065338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065338
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web