Le Sat, Apr 29, 2017 at 09:50:01AM -0500, Dirk Eddelbuettel a écrit :
> 
> I think I will cover these by hand now:
> 
>                package dotFortran  dotC recommended
>  1:       class-7.3-14      FALSE  TRUE        TRUE
>  2:      cluster-2.0.6       TRUE  TRUE        TRUE
>  3:     foreign-0.8.68      FALSE  TRUE        TRUE
>  4: KernSmooth-2.23-15       TRUE FALSE        TRUE
>  5:        MASS-7.3-47      FALSE  TRUE        TRUE
>  6:      Matrix-1.2-10      FALSE  TRUE        TRUE
>  7:        mgcv-1.8-17      FALSE  TRUE        TRUE
>  8:       nlme-3.1.131       TRUE  TRUE        TRUE
>  9:        nnet-7.3-12      FALSE  TRUE        TRUE
> 10:     spatial-7.3-11      FALSE  TRUE        TRUE
> 11:    survival-2.41-3      FALSE  TRUE        TRUE
> 
> and we should binNMU the remaining ones satisfying
> 
>   binary: any                           (ie applicable for Debian binNMUs)
>   has either .C() or .Fortran()
> 
> I have access to a fully expanded directory of CRAN sources of if we start we
> the reverse depends I can refine the script above to get a set of packages
> for which we can then set up binNMUs.
> 
> One caveat: the shell script does not (yet?) filter out those packages that
> already had a post R 3.3.3 update which includes eg several from the set 
> above.

Hi Dirk,

this is very neat to pinpoint which package needs to be rebuilt.  Related to
this I had one more reminder from a member of the Release team that r-base
should not be co-installable with the packages that it breaks.  This is related
to the support of partial upgrades that I was mentioning earlier.

At this point I see 3 options:

 - For each rebuild, insert a "Breaks" relationship in r-base's control file;

 - Increment r-api-3 to r-api-4 (or r-api-3.4, etc.) in order to not have to
   maintain a long list of "Breaks" declarations.  In that case, we have to
   rebuild everything.

 - Just rebuild what has to be rebuilt, and do not support partial upgrades,
   which is what has been done until now.

Not supporting partial upgrades puts the maintainers of the r-cran and r-bioc
packages between the hammer and the anvil.  This said, I think that we have
made constant progresses over the years, so I do not feel shy saying "not yet"
to the Release team again if needed.

Have a nice day,

Charles

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan

Reply via email to