On Thu, Apr 18, 2019 at 09:28:55AM +0200, Paul Gevers wrote:
> Source: r-base
> Severity: important
> User: debian...@lists.debian.org
> Usertags: breaks
> Control: affects -1 r-cran-permute
> Control: affects -1 r-cran-phangorn
> Control: affects -1 r-cran-popepi
> Control: affects -1 r-cran-recipes
> Control: affects -1 r-cran-sp
> Control: affects -1 r-cran-spam
> Control: affects -1 r-cran-units
> Control: affects -1 r-cran-vegan
> Control: affects -1 r-cran-zelig
>
> [X-Debbugs-CC: debian...@lists.debian.org,
> r-pkg-t...@alioth-lists.debian.net]
>
> Dear maintainers,
>
> With a recent upload of r-base the autopkgtest of 9 r-cran-* fail in
> testing (and unstable) when their autopkgtests are run with the binary
> packages of r-base from unstable. It passes in testing when run with
> only packages from testing.
>
> Apart from the freeze, this regression is blocking the migration of
> r-base to testing [1].
Well, "apart from freeze" is the keyword here. The problem is that the
r-base maintainer has a long record of ignoring freeze policy but the
r-pkg team is not updating packages to new upstream versions in freeze
time. So this will be fixed *after* the Stretch release when we start
to refresh all R packages with new upstream versions which we stopped
in Freeze time.
> Can you please investigate the situation?
I'm not motivated to react if others fail to understand freeze policy,
sorry.
> If the
> issue (also) needs to be solved in the packages with the regressing
> autopkgtest than please clone this bug and reassign to the right
> package. Because this uploads breaks so many autopkgtests, I filed this
> bug only against r-base, normally I file these kind of bugs against both
> packages that are involved, but I X-Debbugs-CC-ed the maintainers of the
> other packages.
Thanks for your work for autopkgtests in general
Andreas.
--
http://fam-tille.de
