[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Update on R 3.0.0 migration (Was: R 3.0.0 and required rebuilds of all reverse Depends: of R)

On 6 April 2013 at 21:55, Julian Gilbey wrote:
| > R> print(todo[ order(todo[,2]), ], row.names=FALSE)
| >                        pkg                                              maint
| >                 r-cran-erm                                     jdg@debian.org
| >        r-cran-raschsampler                                     jdg@debian.org
| I uploaded these to unstable on Friday lunchtime, and they were
| accepted into unstable on Friday afternoon; I'm unclear why they are
| still in your list?  Did I do something wrong?
| Oh yes, I clearly did.  Even though I built it in a chroot with
| r-base-dev 3.0.0-2 installed, I forgot to update the Depends lines in
| the control files.
| So something doesn't make sense somewhere: if my package doesn't care
| which version of R it's building against, but R itself cares, then
| surely there should be some way of querying r-base-dev during the

Dunno -- we only have one r-base-core / r-base-dev. I think if you had
updated you pbuilder chroot, you would have gotten the new R -- satisfying
both the Depends you had, and the Depends you should have had.

| build process to enquire which version is required?  It is almost
| certainly too late to do anything about this for wheezy, but it would
| be good to think about doing something for wheezy+1.  Ideally, this
| would be by creating a misc substvar so that instead of having to
| specify the version of r-base-core in the Depends: field, it could be
| specified just as ${misc:Depends} and then filled in automatically.

If someone could contribute this...
| Anyway, I'm rebuilding them now with the dependencies updated to
| 3.0.0-2.



Dirk Eddelbuettel | edd@debian.org | http://dirk.eddelbuettel.com

Reply to: