On 28 December 2025 at 21:00, Santiago Vila wrote: | On Sun, Dec 28, 2025 at 01:04:52PM -0600, Dirk Eddelbuettel wrote: | | > [...] | > | > It must have gotten pulled in by another package, which now longer depends on | > it. It is clearly a bug on my end as I should have a (Build-)Depends on it | > but do not. Will add one now. | | Hi. I did a debbisect and it says this: | | bisection finished successfully | last good timestamp: 20251216T083550Z | first bad timestamp: 20251216T203730Z | the following packages differ between the last good and first bad timestamp: | libjansson4:amd64 2.14-2+b3 -> 2.14-2+b4 | libyaml-0-2:amd64 0.2.5-2 -> 0.2.5-2+b1 | r-cran-scales 1.3.0-1 -> 1.4.0-1 | | I have not looked at the dependencies of r-cran-scales yet. | Does this explain why it worked in the past but not anymore? | | ( Should r-cran-scales maybe depend again on the package you plan to add as a BD ?)
Unsure: 'scales' (aka our r-cran-scales) is not listed as Dependency or even a Suggests now. It is also not in my debian/control possible as a leftover. How do we it ever mattered for Hmisc (aka r-cran-hmisc)? Maybe again a side-effect from another package? I often said that I prefer low-dependency packages. This is in fact a pretty good example why. :) Cheers, Dirk | Thanks. -- dirk.eddelbuettel.com | @eddelbuettel | [email protected]
