Dirk Eddelbuettel: > [...] > On 19 August 2017 at 13:14, Dirk Eddelbuettel wrote: > | > | Dear release team, > |
Hi, Sorry for the slow up take on our part. > | Gentle poke. We still need this set of NMUs to get R 3.4.1 into testing. > | > | "Ask me anything" -- What (if anything) is missing? How can I help? > Before I schedule these binNMUs, then I need to understand if partial upgrades will be handled correctly. Notably, this case suggests that they will not be. If someone was to upgrade R and (for the sake of the example) a rebuilt r-cran-logspline, what will ensure that the rest of the affected R packages are upgraded (or removed)? In a regular ABI bump, everything is rebuilt against a new ABI package and the old one is (eventually) removed. As I understand it, we are not doing that here (nor a variant of it), so you would have to use "Breaks" to ensure this property holds. But while Breaks on binNMU versions is possible, it can give you headaches if binNMU versions are not in sync between architectures. * Once the above is clarified/resolved, then we can start binNMUs. > Setting severity to 'serious' which is what the one for r-base is tagged with > at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861333 > Generally, most release.d.o bug does not use severity so it does not really affect anything (except it splits our bug ordering up, and somebody will probably show up and fix that eventually). Thanks, ~Niels
