Bug#1063431: src:r-cran-future.apply: fails to migrate to testing for too long: autopkgtest failure

2024-02-08 Thread Andreas Tille
Control: tags -1 upstream
Control: forwarded -1 https://github.com/HenrikBengtsson/future.apply/issues/120

Hi Paul,

thanks a lot for all your work.  I have forwarded the problem upstream.

Kind regards
   Andreas.

-- 
http://fam-tille.de



Processed: Re: Bug#1063431: src:r-cran-future.apply: fails to migrate to testing for too long: autopkgtest failure

2024-02-08 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 upstream
Bug #1063431 {Done: Paul Gevers } [src:r-cran-future.apply] 
src:r-cran-future.apply: fails to migrate to testing for too long: autopkgtest 
failure
Added tag(s) upstream.
> forwarded -1 https://github.com/HenrikBengtsson/future.apply/issues/120
Bug #1063431 {Done: Paul Gevers } [src:r-cran-future.apply] 
src:r-cran-future.apply: fails to migrate to testing for too long: autopkgtest 
failure
Set Bug forwarded-to-address to 
'https://github.com/HenrikBengtsson/future.apply/issues/120'.

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



Bug#1063431: src:r-cran-future.apply: fails to migrate to testing for too long: autopkgtest failure

2024-02-07 Thread Paul Gevers

Source: r-cran-future.apply
Version: 1.11.0+dfsg-1
Severity: serious
Control: close -1 1.11.1+dfsg-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-future.apply has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug. The version in 
unstable fails its own autopkgtest on armel, armhf and i386 (our 32 bits 
architectures).


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/msg1.html
[2] https://qa.debian.org/excuses.php?package=r-cran-future.apply



OpenPGP_signature.asc
Description: OpenPGP digital signature