R SIG Debian - May 2022 - Installing R 4.1.2 doesn't work as it did a week ago

Chad,

I think you have a fundamental disconnect.  "In general" both at CRAN
and in
distros like Ubuntu and Debian you just get rolling releases that will
feature the most current version of packages (with the exception of release
snapshot time at which point a demarcation line is drawn).

So you generally cannot assume you can just randomly impose version constraint.
There are some expections (as the date-snapshots by first MRAN and now RSPM),
but they are generally _not_ integrated with apt.

In short, methinks you cannot assume you can just run a Dockerfile today as
if were a random day you liked between R 4.1.2 and 4.1.3. The repos, and
package management software, are designed for that use case.

Hope this helps,  Dirk

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

Okay, thanks for all your help.

Chad Young
Bioinformatics Scientist
TwinStrand Biosciences <https://twinstrandbio.com/>


On Mon, May 9, 2022 at 8:02 AM Dirk Eddelbuettel <edd at debian.org>
wrote:
>
> Chad,
>
> I think you have a fundamental disconnect.  "In general" both at
CRAN and
> in
> distros like Ubuntu and Debian you just get rolling releases that will
> feature the most current version of packages (with the exception of release
> snapshot time at which point a demarcation line is drawn).
>
> So you generally cannot assume you can just randomly impose version
> constraint.
> There are some expections (as the date-snapshots by first MRAN and now
> RSPM),
> but they are generally _not_ integrated with apt.
>
> In short, methinks you cannot assume you can just run a Dockerfile today as
> if were a random day you liked between R 4.1.2 and 4.1.3. The repos, and
> package management software, are designed for that use case.
>
> Hope this helps,  Dirk
>
> --
> dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
>
	[[alternative HTML version deleted]]