- Devel - AlmaLinux List Archives

Re: Unreachable repos in AlmaLinux
by Retrogrid Tech 04 Apr '26

04 Apr '26

Hi Francesco, See the other thread to Jonathan for more details. If I install RPM https://repo.almalinux.org/almalinux/8.10/extras/x86_64/kickstart/Packages/… which is the only version of the package in the 8.10 folder, the repo file it installs contains a section [centos-advanced-virtualization] which has a URL that does not exist. There are a significant number of RPM files like this. Ben S On 4/3/26 2:53 PM, Francesco Di Nucci via Devel wrote: > Hi, > > for the links that point to centos.org consider that packages related > to EOL versions are moved to vault.centos.org (for example see > https://vault.centos.org/8.5.2111/storage/x86_64/ for some of the > repos that gave you issues like Gluster 6). If that's not enough > consider asking on CentOS mailing lists. > > For AlmaLinux repositories have a look at vault.almalinux.org and > nvidia.repo.almalinux.org > > Cheers > > Francesco > -- Time-Indexed Linux Infrastructure. Deterministic. Defensible.

1 0

Re: Unreachable repos in AlmaLinux
by Retrogrid Tech 03 Apr '26

03 Apr '26

Hi Jonathan, My apologies if this report format was unclear. I've laid out the report format below so it hopefully makes more sense. In the first example, the RPM "*centos-release-advanced-virtualization-1.0-4.el8.noarch.rpm*" contains yum.repos.d files with repos that reference address that, in our testing, did not resolve or download correctly. Specifically, repo section [centos-advanced-virtualization] has a mirrorlist URL: http://mirrorlist.centos.org/?release=$avstream&arch=$basearch&repo=virt-$a… ...which we interpreted to a literal URL: http://mirrorlist.centos.org/?release=$avstream&arch=x86_64&repo=virt-$avdir ... and this did not resolve. I do not know what $avdir was intended to reference, but we have deferred identifying it because the domain mirrorlist.centos.org does not have a DNS entry. The majority of these unresolvable URLs are at mirrorlist.centos.org, but there are others that aren't. (EG: [almalinux-nvidia-debuginfo]) Thanks, Ben S PS Format: (Sections repeat based on indenting, think: python) File: (path to RPM containing the failed .repo file/section) Failures: (Number of failed attempts to access URL, can be duplicative) [Title of Repo Section containing the failed URL] failures: (Number of failed attempts to access URL from subscan, usually (always?) matches prev) URL as specified in repo section URL of previous line as interpreted based on original RPM context Failures: (number of failed attempts within the attempt record, should be one) Status: (Internal error code designation) (http response code, EG: 404) /path/to/saved/file/if/saved On 4/3/26 6:13 AM, Jonathan Wright via Devel wrote: > Hi Benjamin, > > I don't understand what you're getting at exactly, or what represents > a "failure". > > I checked the first RPM in your output, which maps to > https://repo.almalinux.org/almalinux/8.10/extras/x86_64/kickstart/Packages/…, > which works just fine and doesn't throw any errors. What's the issue > here? > > On Thu, Apr 2, 2026 at 10:16 AM Retrogrid Tech via Devel > <devel(a)lists.almalinux.org> wrote: > > Hello everyone, > > We have identified a significant number of non-functioning-repo > RPMs and > need to know which of these are intentionally non-functional so we > can > map them correctly in our archive rather than propagating broken repo > definitions to enrolled systems. > > A simple "intentional" / "defect" next to each in the attached > list/report would be fully adequate. > > The attached report summary should make it straightforward either to > classify these as intentional or to address them as defects. > > > Thanks, > > Benjamin Smith > > PS: Apologies if this is not the correct place to report this - > Please > direct me to the most appropriate channel if this is not it. > > For context, we're establishing a temporal mirror of the Enterprise > Linux universe - something like a "Wayback Machine" for Linux OS. For > completeness, this historical archive includes the results of > metalink > and mirrorlist queries but many of these do not > resolve._______________________________________________ > Devel mailing list -- devel(a)lists.almalinux.org > To unsubscribe send an email to devel-leave(a)lists.almalinux.org > > > > -- > Jonathan Wright > AlmaLinux OS Foundation > Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan> > > _______________________________________________ > Devel mailing list --devel(a)lists.almalinux.org > To unsubscribe send an email todevel-leave(a)lists.almalinux.org -- Time-Indexed Linux Infrastructure. Deterministic. Defensible.

1 0

Re: Unreachable repos in AlmaLinux
by Jonathan Wright 03 Apr '26

03 Apr '26

Hi Benjamin, I don't understand what you're getting at exactly, or what represents a "failure". I checked the first RPM in your output, which maps to https://repo.almalinux.org/almalinux/8.10/extras/x86_64/kickstart/Packages/…, which works just fine and doesn't throw any errors. What's the issue here? On Thu, Apr 2, 2026 at 10:16 AM Retrogrid Tech via Devel < devel(a)lists.almalinux.org> wrote: > Hello everyone, > > We have identified a significant number of non-functioning-repo RPMs and > need to know which of these are intentionally non-functional so we can > map them correctly in our archive rather than propagating broken repo > definitions to enrolled systems. > > A simple "intentional" / "defect" next to each in the attached > list/report would be fully adequate. > > The attached report summary should make it straightforward either to > classify these as intentional or to address them as defects. > > > Thanks, > > Benjamin Smith > > PS: Apologies if this is not the correct place to report this - Please > direct me to the most appropriate channel if this is not it. > > For context, we're establishing a temporal mirror of the Enterprise > Linux universe - something like a "Wayback Machine" for Linux OS. For > completeness, this historical archive includes the results of metalink > and mirrorlist queries but many of these do not > resolve._______________________________________________ > Devel mailing list -- devel(a)lists.almalinux.org > To unsubscribe send an email to devel-leave(a)lists.almalinux.org > -- Jonathan Wright AlmaLinux OS Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>

1 0

Re: Unreachable repos in AlmaLinux
by Francesco Di Nucci 03 Apr '26

03 Apr '26

Hi, for the links that point to centos.org consider that packages related to EOL versions are moved to vault.centos.org (for example see https://vault.centos.org/8.5.2111/storage/x86_64/ for some of the repos that gave you issues like Gluster 6). If that's not enough consider asking on CentOS mailing lists. For AlmaLinux repositories have a look at vault.almalinux.org and nvidia.repo.almalinux.org Cheers Francesco -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci(a)na.infn.it On 2026-04-02 17:16, Retrogrid Tech via Devel wrote: > Hello everyone, > > We have identified a significant number of non-functioning-repo RPMs > and need to know which of these are intentionally non-functional so we > can map them correctly in our archive rather than propagating broken > repo definitions to enrolled systems. > > A simple "intentional" / "defect" next to each in the attached > list/report would be fully adequate. > > The attached report summary should make it straightforward either to > classify these as intentional or to address them as defects. > > > Thanks, > > Benjamin Smith > > PS: Apologies if this is not the correct place to report this - Please > direct me to the most appropriate channel if this is not it. > > For context, we're establishing a temporal mirror of the Enterprise > Linux universe - something like a "Wayback Machine" for Linux OS. For > completeness, this historical archive includes the results of metalink > and mirrorlist queries but many of these do not resolve. > > _______________________________________________ > Devel mailing list -- devel(a)lists.almalinux.org > To unsubscribe send an email to devel-leave(a)lists.almalinux.org

1 0

Unreachable repos in AlmaLinux
by Retrogrid Tech 28 Mar '26

28 Mar '26

Hello everyone, We have identified a significant number of non-functioning-repo RPMs and need to know which of these are intentionally non-functional so we can map them correctly in our archive rather than propagating broken repo definitions to enrolled systems. A simple "intentional" / "defect" next to each in the attached list/report would be fully adequate. The attached report summary should make it straightforward either to classify these as intentional or to address them as defects. Thanks, Benjamin Smith PS: Apologies if this is not the correct place to report this - Please direct me to the most appropriate channel if this is not it. For context, we're establishing a temporal mirror of the Enterprise Linux universe - something like a "Wayback Machine" for Linux OS. For completeness, this historical archive includes the results of metalink and mirrorlist queries but many of these do not resolve.

1 0

OpenStack RPMs - Call for packaging volunteers
by Francesco Di Nucci 16 Mar '26

16 Mar '26

Hi all, the RDO Project[0], that provided OpenStack RPM packages through the CentOS Cloud SIG, is switching to a container-based approach due to lack of maintainers.[1] This means *there will be no more RPM packages for OpenStack versions after 2025.1/Epoxy unless new maintainers come up*. *This is a call across the EL and OpenStack communities for volunteer maintainers of RPM build pipelines*. If you're interested you can: * Add your name to the dedicated Etherpad (https://etherpad.opendev.org/p/rdo-volunteers) * Register to the RDO devs mailing list (dev(a)lists.rdoproject.org) and ask for more information No previous experience with packaging/pipelines is required, just willingness to learn /Note: this email is being separately to different mailing lists. If you have subscribed to more than one and recieve it multiple times, sorry for the duplication./ Links [0] https://www.rdoproject.org/ [1] https://lists.rdoproject.org/archives/list/users@lists.rdoproject.org/threa… Francesco, another OpenStack on EL operator -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email:francesco.dinucci@na.infn.it

1 0

Re: OpenStack RPMs
by Neal Gompa 13 Mar '26

13 Mar '26

On Thu, Mar 12, 2026 at 8:08 PM Francesco Di Nucci via Devel <devel(a)lists.almalinux.org> wrote: > > Hi all, > > given that RDO will soon stop releasing RPMs of OpenStack, it has been > suggested on IRC etc that AlmaLinux and Rocky Linux communities might be > interested in building the RPMs instead, is there already a discussion > about it? > I think we'd generally prefer to see AlmaLinux contributors helping out in upstream RDO. If there are folks from the AlmaLinux community interested, please engage with RDO to help them. -- 真実はいつも一つ！/ Always, there's only one truth!

1 0

Re: [rdo-dev] Re: [rdo-users] Re: OpenStack RPMs
by Francesco Di Nucci 10 Mar '26

10 Mar '26

Why not, I'd like to try, at least with the call for volunteers. Just to have an idea, how much time roughly is required? I'd have to get a couple of authorizations Francesco On 09/03/26 22:37, Amy Marrich wrote: > If you all are willing to volunteer, and/or help find other > volunteers, I will try to find folks to mentor you to get you started > to keep the RPMs going. Unfortunately, I have already spoken to folks > in both Alma and Rocky, a year ago and again this weekend at a > conference, to see if they could assist and they do not have the > resources. > > There was previously a small team of 2-3 engineers working on RDO but > as mentioned in the release announcement email they moved on to other > positions. > > Amy > > > > > On Mon, Mar 9, 2026 at 2:42 PM Francesco Di Nucci > <francesco.dinucci(a)na.infn.it> wrote: > > Thank you, > > is it possible to try again to search for volunteers before > abandoning definitively the RPM packages? Less diversity is a loss > for everyone, and maybe people did not fully realize the situation > (me including, didn't read the announcement email as I'm still > running Caracal 😅). Cross-posting with other mailing > lists/IRC/ops meetings could be useful, and if the alternative is > RPM discontinuation, more people might be interested. > > If I can ask, how many people would (ideally) be necessary/how > many RPMs are around? > > Francesco > > On 06/03/26 17:14, Amy Marrich wrote: >> Francesco, Massimo, Jose, >> >> We would love help from the other communities to continue >> creating the RPMS. We put a call out for volunteers over a year >> ago[0]. and while folks replied that they wanted to help or >> attended a meeting no one actually started helping. As a result, >> we added an important note to the bottom of the Epoxy release >> announcement[1] explaining that internal developers had moved on >> and we again said we needed help and to reach out if interested. >> >> Amy >> >> 0 - >> https://lists.rdoproject.org/archives/list/dev@lists.rdoproject.org/thread/… >> 1 - >> https://lists.rdoproject.org/archives/list/users@lists.rdoproject.org/messa… >> >> I'll also send this to the OpenStack list but respecting Jeremy's >> decoupling of lists. >> >> On Fri, Mar 6, 2026 at 8:12 AM Francesco Di Nucci >> <francesco.dinucci(a)na.infn.it> wrote: >> >> Hi all, >> >> given that RDO will soon stop releasing RPMs of OpenStack, it >> has been >> suggested on IRC etc that AlmaLinux and Rocky Linux >> communities might be >> interested in building the RPMs instead, is there already a >> discussion >> about it? >> >> Best regards >> >> Francesco Di Nucci >> >> -- >> Francesco Di Nucci >> System Administrator >> Compute & Networking Service, INFN Naples >> >> Email: francesco.dinucci(a)na.infn.it >> >> >> >> _______________________________________________ >> users mailing list --users(a)lists.rdoproject.org >> To unsubscribe send an email tousers-leave(a)lists.rdoproject.org >> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >> >> To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s > > > _______________________________________________ > dev mailing list --dev(a)lists.rdoproject.org > To unsubscribe send an email todev-leave(a)lists.rdoproject.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > > To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s

1 0

Re: [rdo-users] Re: OpenStack RPMs
by Francesco Di Nucci 09 Mar '26

09 Mar '26

Thank you, is it possible to try again to search for volunteers before abandoning definitively the RPM packages? Less diversity is a loss for everyone, and maybe people did not fully realize the situation (me including, didn't read the announcement email as I'm still running Caracal 😅). Cross-posting with other mailing lists/IRC/ops meetings could be useful, and if the alternative is RPM discontinuation, more people might be interested. If I can ask, how many people would (ideally) be necessary/how many RPMs are around? Francesco On 06/03/26 17:14, Amy Marrich wrote: > Francesco, Massimo, Jose, > > We would love help from the other communities to continue creating the > RPMS. We put a call out for volunteers over a year ago[0]. and while > folks replied that they wanted to help or attended a meeting no one > actually started helping. As a result, we added an important note to > the bottom of the Epoxy release announcement[1] explaining that > internal developers had moved on and we again said we needed help and > to reach out if interested. > > Amy > > 0 - > https://lists.rdoproject.org/archives/list/dev@lists.rdoproject.org/thread/… > 1 - > https://lists.rdoproject.org/archives/list/users@lists.rdoproject.org/messa… > > I'll also send this to the OpenStack list but respecting Jeremy's > decoupling of lists. > > On Fri, Mar 6, 2026 at 8:12 AM Francesco Di Nucci > <francesco.dinucci(a)na.infn.it> wrote: > > Hi all, > > given that RDO will soon stop releasing RPMs of OpenStack, it has > been > suggested on IRC etc that AlmaLinux and Rocky Linux communities > might be > interested in building the RPMs instead, is there already a > discussion > about it? > > Best regards > > Francesco Di Nucci > > -- > Francesco Di Nucci > System Administrator > Compute & Networking Service, INFN Naples > > Email: francesco.dinucci(a)na.infn.it > > > > _______________________________________________ > users mailing list --users(a)lists.rdoproject.org > To unsubscribe send an email tousers-leave(a)lists.rdoproject.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > > To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s

1 0

OpenStack RPMs
by Francesco Di Nucci 06 Mar '26

06 Mar '26

Hi all, given that RDO will soon stop releasing RPMs of OpenStack, it has been suggested on IRC etc that AlmaLinux and Rocky Linux communities might be interested in building the RPMs instead, is there already a discussion about it? Best regards Francesco Di Nucci -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci(a)na.infn.it

1 0