Hi folks,
Holger Wansing <linux@wansing-online.de> (2018-06-08):
> We had the same situation in 2016 with jessie/stretch manual.
> I have already adapted the lessoften cron script in
> https://salsa.debian.org/webmaster-team/cron/commit/f02a61c6d43c3b2f141ad64a837c33fbd0f56fb8
>
> Today I found the relevant mailinglist entries, here:
> https://lists.debian.org/debian-boot/2016/03/msg00200.html
> where I read that some more action is needed.
>
> Laura: could you help us again with this?
> In above mailinglist entry you have posted the commands needed back
> in 2016...
I'm wondering whether we shouldn't be trying to look at specific
versions of installation-guide based on the target suite, rather than
hoping for the best with ls -t|head -1.
For stretch, it can be obtained with:
| kibi@wolkenstein:~$ rmadison installation-guide -s stretch | awk '{print $3}'
| 20170614
For buster, there's currently no version available in testing, so we
could try to use whatever is in testing, and fall back to unstable if
there's no such version?
(If we implement checking several suites with a fallback, we could even
check stretch-proposed-updates in addition to stretch, which would let
us merge things in advance when a point release is being prepared.)
What do you (-boot & -www) think?
Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature