This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Future of Software Anchors
- Previous message (by thread): [atlas] Future of Software Anchors
- Next message (by thread): [atlas] Future of Software Anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jared Mauch
jared at puck.nether.net
Sat May 28 17:23:03 CEST 2022
> On May 28, 2022, at 10:27 AM, Lukas Magauer via ripe-atlas <ripe-atlas at ripe.net> wrote: > > Hi everybody! > > I have been running a Software probe on CentOS 8 since mid 2020. (and since switched it to Rocky Linux 8) > It’s unsupported, but also didn’t really make any problems, just worked fine with the yum repo distributed package! > > Great that there are already plans to support newer versions as well! > > And has there something changed in the distribution of the package? > Because the latest changes of version 5070 don’t look like they appeared in the GitHub repo? > > Best regards, > Lukas I just made a new anchor the other day, and CentOS 7 is still the requirement, I also rebuilt one of the original VM anchors as well - it had a different partition scheme and I wasn’t asked to fix it, but apparently it was causing an issue on the back-end. I’m expecting they will do an OS upgrade, but also CentOS doesn’t really like providing upgrade paths, so I suspect the job will be to just re-image the VM with a newer CentOS ISO and kickstart file at some point, or they will find a repeatable series of dnf commands that will step the VM from 7 -> SomethingNewer - Jared
- Previous message (by thread): [atlas] Future of Software Anchors
- Next message (by thread): [atlas] Future of Software Anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]