Re: Bug#896667: It is safe to assume that source only uploads will build against the r-api-3.5? (Was: Bug#896667: transition: r-base-3.5)
On 1 June 2018 at 17:50, Andreas Tille wrote:
| On Fri, Jun 01, 2018 at 08:00:12AM -0500, Dirk Eddelbuettel wrote:
| >
| > | Depending on your definition of auto-rebuilt... I was the one who scheduled the
| > | rebuilds, and I picked all arch:any packages from the transition page, except
| > | for that set. The reason is that they didn't depend on r-base-3.4 (except on
| > | kbsd, probably because of old builds), so it seemed unnecessary to rebuild them.
| >
| > Strange. A lot of these are "mine" and both old and fairly central. Let's
| > follow-up when I have a moment. Ping me if forget / get distracted. But as a
| > "technical issue" this should have a technical solution.
|
| I bet a simple rebuild will do since the dh-r bug that has caused the
| issue is fixed. So in principle you do not need to do anything since
| the packages are scheduled for rebuild now.
|
| BTW, its not strange that the packages are "yours". As I explained in
| the bug log only packages that do not have the r-cran- prefix in the
Indeed, and good catch.
In the (draft) Debian R Policy from 2003 (!!) we may or may not have
suggested using r-cran-* for both -- that is indeed the commonality. These
are all pretty old package from before we standardized on r-cran-* for both.
| source package name were affected. I made some effort that this is
| not the case in r-pkg-team packages any more and so the team maintained
| packages were "by chance" / "luckily" not affected (and thus also the
| bug was not detected before).
Yep.
| Have fun at your conference
Thanks!
Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | edd@debian.org
Reply to: