[RSS:MirDebianWTFapt] 2025-08-06
- Open up a trixie suite; the wtf component is pretty much what sid is at the time of the Debian release (or a few days shy of it as we’re at now); an lts component (shipping amd64, i386 and armel here) with mc, openjdk-8, screen, tomcat9 and uw-imap is also provided; this is because I need it for work (though $employer does not sponsor it) and does not indicate support of any level; caveats: screen is not present yet; i386 is EOL’d in trixie (still present as architecture, but neither kernel nor d-i are available, so it’s only good for chroots), and as such, new builds for trixie/{wtf,lts} won’t include i386 any more (case in point, openjdk-8)
- Note armel is enabled for the lts component as there are chances forky may drop armel entirely; I hope they’ll actually E?LTS it if that happens…
- Updated openjdk-8 for wheezy, jessie, buster, bullseye, bookworm as well (stretch is handled via Freexian ELTS)
- jessie is now desupported like wheezy as its ELTS has ended
- Prolong the repo signing PGP key and update wtf-debian-keyring.gpg and sources.txt/*.sources accordingly; users, please update as well!
- (Note these changes are very fresh, and many more are coming, treat with care; in particular, wtf-debian-keyring and m-s-data need updating but I ran out of time)
- Update hookdir/, pbuilderrc from CVS
- Updated wtf
@wouter heh, yes of course I’ll be sending one in, but let me test it a bit (abd work through the other changes I need to do that piled up) first ;)
Also late last night but didn’t make the cut for the RSS day:
- Updated tomcat9 (new upstream release plus a post-release integer overflow fix)
@wouter I also wonder if I can get my keyring package to do the key rollover automatically (and need to split it between an apt-key and a nōn-apt-key
version anyway)… hmmhmm… I procrastinated that problem for so long users now have apt-key
, /etc/apt/trusted.gpg.d/
and /etc/apt/sources.list.d/*.sources
files…
{D,How d}oes extrepo
handle key rollovers? (At least it only has to bother with supported Debian releases ^^
)
@mirabilos
Extrepo requires a new merge request and then an 'extrepo update' by the user. There is still some room for improvement there, though.
Extrepo requires a new merge request and then an 'extrepo update' by the user. There is still some room for improvement there, though.