[R-pkg-team] Bug#1039510: mvtnorm breaks r-cran-pammtools autopkgtest: missing Breaks and/or versioned (test) Depends?

Dirk Eddelbuettel edd at debian.org
Tue Jun 27 20:02:43 BST 2023


Hi Paul,

On 27 June 2023 at 20:08, Paul Gevers wrote:
| Hi Dirk,
| 
| On 26-06-2023 22:21, Dirk Eddelbuettel wrote:
| > I really appreciate the diligence and detail you put into this.
| > 
| > But I would like to offer a simple shortcut.  I am also CCing debian-r again
| > as this has come up time and time again, is guaranteed to come up again for
| > as long as combine autopkgtests with letting packages go stake.
| 
| Somehow I feel you missed my point. In Debian we also care about 
| preventing partial upgrades doing the wrong thing. I explicitly noted 
| that in unstable everything is fine, so I think I acknowledge what you 
| said. However, for the migration to automatically happen and to 
| (possibly, I leave that for you (packages maintainers) to judge) prevent 
| issues with partial upgrades there needs to be some *versioned* package 
| relation somewhere.

I am not a fan of accomodating outdated packages in Debian by means of
imposed constraints _which then differ from perfectly viable and sane
upstream uses_ and am not here for it.  Life is too short: just under 20k
CRAN packages, (last I checked) just over 1k in Debian -- and once you allow
for "random" package combination (which, I repeat, are untested upstream in
these combinations) you essentially get yourself an infinity of possible
combinations.  There lies madness.

Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org



More information about the R-pkg-team mailing list