- 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

希望在almalinux10中提供dnf5
by 蓝天白云 26 Jan '26

26 Jan '26

 希望在almalinux10中提供dnf5，因为dnf5实在是比dnf4好用很多。蓝天白云 592453120(a)qq.com

3 2

almalinux10 中没有sshpass
by 蓝天白云 18 Dec '25

18 Dec '25

您好！     almalinux10 中没有sshpass软件包，almalinux9中是有sshpass软件包的。    安装epel-release，也没有remmina软件包。请支持，谢谢！蓝天白云 592453120(a)qq.com  

3 2

Mantis login page displaying warning.
by Phil Wyett 25 Oct '25

25 Oct '25

Hi all, The Mantis login page[1] is displaying the warning below. Warning: "path" was not defined in config_inc.php. Leaving it empty is a security risk, as the path will be set based on headers from the HTTP request, exposing your system to Host Header Injection attacks. [1] https://bugs.almalinux.org/login_page.php Regards Phil -- Independent Free/Open Source Contributor. Not affiliated with any GNU Linux Distribution. -- Blog: https://blog.kathenas.org Instagram: https://instagram.com/kathenasorg Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

1 0

No view for AlmaLinux 9 on Mantis
by Phil Wyett 25 Oct '25

25 Oct '25

Hi all, When logged in or not if you click on the 'AlmaLinux-9' link to view that project or in a new tab try go to the link below, you will be returned to the last project or default project at that time. https://bugs.almalinux.org/set_project.php?project_id=3 Regards Phil -- Independent Free/Open Source Contributor. Not affiliated with any GNU Linux Distribution. -- Blog: https://blog.kathenas.org Instagram: https://instagram.com/kathenasorg Buy Me A Coffee: https://buymeacoffee.com/kathenasorg

1 0

Re: Package submission
by Jonathan Wright 19 Aug '25

19 Aug '25

Howdy, Generally we suggest things be added to Fedora EPEL instead of AlmaLinux directly. Are the things you've packaged candidates for Fedora/EPEL or is something barring that? On Mon, Jun 16, 2025 at 1:47 PM code--- via Devel <devel(a)lists.almalinux.org> wrote: > Hi, > > I'm sorry for this stupid? question, but I've created and I maintain > some RPM packages for Fedora/openSUSE/Mageia, and I'd like to submit the > SPECs in AlmaLinux, is it possible? I couldn't find the howto, can > anyone help me? > > Thanks > _______________________________________________ > 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>

2 3

Re: Package submission
by Jonathan Wright 20 Jun '25

20 Jun '25

Yeah if this is your package in Fedora you can branch it for `epel10` and `epel10.0` for example :) On Mon, Jun 16, 2025 at 2:02 PM code--- via Devel <devel(a)lists.almalinux.org> wrote: > Oh, alright. > > So, the packages has been pushed to EPEL 9, for example > https://src.fedoraproject.org/rpms/human-theme-gtk > > Thank you > > Le 16/06/2025 20:57, Jonathan Wright a écrit : > > Howdy, > > Generally we suggest things be added to Fedora EPEL instead of AlmaLinux > directly. Are the things you've packaged candidates for Fedora/EPEL or is > something barring that? > > On Mon, Jun 16, 2025 at 1:47 PM code--- via Devel < > devel(a)lists.almalinux.org> wrote: > > Hi, > > I'm sorry for this stupid? question, but I've created and I maintain > some RPM packages for Fedora/openSUSE/Mageia, and I'd like to submit the > SPECs in AlmaLinux, is it possible? I couldn't find the howto, can > anyone help me? > > Thanks > _______________________________________________ > 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 to devel-leave(a)lists.almalinux.org > -- Jonathan Wright AlmaLinux OS Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>

2 2

Package submission
by code＠luigifab.fr 16 Jun '25

16 Jun '25

Hi, I'm sorry for this stupid? question, but I've created and I maintain some RPM packages for Fedora/openSUSE/Mageia, and I'd like to submit the SPECs in AlmaLinux, is it possible? I couldn't find the howto, can anyone help me? Thanks

1 0

安装出现错误提示
by 蓝天白云 03 Jun '25

03 Jun '25

您好！在centos-stream10中安装软件时，出现错误提示安装虚拟化时出现错误提示 dnf install libvirt-daemon-kvm virt-install virt-manager  Last metadata expiration check: 0:12:47 ago on Tue 25 Feb 2025 03:57:00 AM CST. Error:   Problem: cannot install both virt-manager-common-5.0.0-1.el10.noarch from appstream and virt-manager-common-4.1.0-8.el10.noarch from appstream   - package virt-manager-4.1.0-8.el10.noarch from appstream requires virt-manager-common = 4.1.0-8.el10, but none of the providers can be installed   - package virt-install-5.0.0-1.el10.noarch from appstream requires virt-manager-common = 5.0.0-1.el10, but none of the providers can be installed   - cannot install the best candidate for the job (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) 安装remmina时出现错误提示 dnf install remmina Last metadata expiration check: 0:13:55 ago on Tue 25 Feb 2025 03:57:00 AM CST. Error:   Problem: package remmina-1.4.39-3.el10_0.x86_64 from epel requires libappindicator3.so.1()(64bit), but none of the providers can be installed   - conflicting requests   - nothing provides libdbusmenu-glib.so.4()(64bit) needed by libappindicator-gtk3-12.10.1-7.el10_0.x86_64 from epel   - nothing provides libdbusmenu-gtk3.so.4()(64bit) needed by libappindicator-gtk3-12.10.1-7.el10_0.x86_64 from epel (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) 安装sshpass时出现错误提示 dnf install sshpass Last metadata expiration check: 0:16:07 ago on Tue 25 Feb 2025 03:57:00 AM CST. No match for argument: sshpass Error: Unable to find a match: sshpass 蓝天白云 592453120(a)qq.com  

2 1

我理想中的Almalinux
by 蓝天白云 25 Apr '25

25 Apr '25

我理想中的Almalinux10，在安装时，像debian那样提供多个图形界面选择，在一个iso文件中包含多个桌面环境，而不是对每个桌面环境提供一个iso文件。并且AlmaLinux10中使用dnf5. 蓝天白云 592453120(a)qq.com  

2 1

almalinux10 中没有sshpass
by 蓝天白云 24 Feb '25

24 Feb '25

您好！ almalinux10中没有sshpass，希望在almalinux10正式版中添加sshpass，谢谢！蓝天白云 592453120(a)qq.com  

1 0

Kernel Rebuild on Alma 9.4 for PXE Install on XEN domU PVH
by michael theurl 19 Feb '25

19 Feb '25

Hello List, i am working to enable the XEN PVH Feature on the stock Alma Linux 9.4 kernel for the PXE Boot image set. I was able to rebuild the kernel with rpm -ivh kernel-5.14.0-427.13.1.el9_4.src.rpm modified the kernel-x86_64-rhel.config from SOURCES <SNIP> CONFIG_XEN_PVH=y # CONFIG_XEN_DOM0 is not set <SNAP> rpmbuild -bb --target=x86_64 kernel.spec and after some time i got the needed rpms. To extract the parts who iam looking for. It does now boot proper as a XEN PVH domU but then the dracut exits because he can not load the kernel modules. So the stock kernel modules from initrd.img from the pxe boot will give me an error: BPF can not load modules and dracut exits. It Seem they are all signed (I am from the time who used Centos 5/6 for a lot of time and did back in time all the compiling and just copy the files in place pretty straight forward, seems things has changed a lot). If i extract the pxe initrd.img file and replace there the kernel modules to the newly compiled it works again. Everything was looking pretty good so far. But... And after i run successfully through the anaconda installer and the installers starts the tasks. Suddenly the installer crashes. it is after The mounting of the filesystem would begin. it fails because the install.img has the old set of kernel modules and the installer exits. He tried to load the xfs kernel module. So again lets change the kernel module but after the change the install.img seems broken. Dracut tells me the rootfs.img is missing. But it is there. Then i gave up and was thinking there must be an other way. I did an unsquashfs install.img mount -o loop rootfs.img /PATH copied the kernel modules unmount /PATH mksquashfs /PATH install.img Is this the only way to make this change happen ? Or is there a much easier way that i could recompile the kernel and still can use all the existing kernel modules ? So that i do not search and replace them in all the files ? If someone could give me some hints that would be amazing. many thanks cheers Michael

3 3

Security Patches
by dervish13＠tilda.center 10 Jun '24

10 Jun '24

Greetings, Is there a guide on how to publish security patches for packages? Or example of working code I can learn from is also useful. I have rpm repo using createrepo, and tried updating the security info with modifyrepo and updateinfo.xml but dnf --refresh update --security never picks it up. Thanks, Dervish

2 1

Maintenance of hpsa and qla2xxx
by Rainer Jung 27 Mar '24

27 Mar '24

Hi there, Thanks for your great work on Alma. I saw that Alma patched away the deprecation resp. unmaintained warnings for hpsa and qla2xxx (and others) for the forthcoming 8.10 and 9.4 as a result of the recent Hackathon in Rust. I wonder what it means in terms of ongoing maintenance for those drivers. Are they still maintained upstreams and will Alma pick up upstream changes even if RHEL drops them? Otherwise simply patching away the warnings might be misleading. Thanks and regards, Rainer

1 0

[PATCH] AlmaLinux 8: cronie 1.5.2-1.5.4 100% CPU usage bug
by Alexander Gerasimov 27 Feb '24

27 Feb '24

Hi All, We areusing AlmaLinux 8 docker image for docker-compose and one of the services is cron (using cronie). We faced 100% CPU load issue. The problem is described here: https://bugzilla.redhat.com/show_bug.cgi?id=1723106 I see there is a patch (fixed in 1.5.5). Patch: https://github.com/cronie-crond/cronie/commit/584911514ce6aa2f16e1d79431bac… Also we found that cronie 1.5.2-10 is used in CentOS 8 Stream, probably with similar patch (didn't found the way to get src rpm), but still 1.5.2-8 in AlmaLinux. Thus, I backported the patch and ask to include it or fix using Centos stream one. Fixed src rpm: https://repo.codeit.guru/packages/unsigned/cronie-1.5.2-9.codeit.el8.src.rpm (see patch10 in spec). Can you review this or point me where to send it? Thanks. Best regards, Alexander Gerasimov Chief Technical Officer CodeIT

1 1

Rebuilding the Almalinux leapp-upgrade-el7toel8-rpms
by Darrious 14 Sep '23

14 Sep '23

I would like to fork the almalinux/leapp-repositories repo, make some tweaks, rebuild the RPMs, and install them along side the leapp dependencies in the Almalinux elevate repo at http://repo.almalinux.org/elevate/elevate-release-latest-el7.noarch.rpm I understand how to rebuild the RPM. The problem I am running into is related to versioning. The yum repository I mentioned says that the leapp-upgrade-el7toel8-* rpm major versions are 0.16.0. I noticed also that there are a few of these RPMs in there with build numbers appended to the end (see attached image). The almalinux/leapp-repositories git repository does contain a v0.16.0 tag but that tag is on a commit from over a year ago and I see that the v.0.16.0 RPMs in the yum repository are receiving regular updates with these build numbers (one was uploaded this week). The RPM produced from the v0.16.0 tag locally does not work with the other dependencies in the yum repo although I am able to get it to work when I rebuild all of the leapp RPMs (which I want to avoid). I would like to understand how to build the newer v0.16.0 RPM with the updated build numbers present in the yum repos. I don't see any tagging or branches in the github repositories for these [image: image.png]

1 0

Zenbleed Patches Available for Testing
by Jonathan Wright 25 Jul '23

25 Jul '23

We are happy to announce that Zenbleed patches are available now for testing. You can apply the fix as follows: AlmaLinux 8: dnf update https://build.almalinux.org/pulp/content/builds/AlmaLinux-8-x86_64-7032-br/… AlmaLinux 9: dnf update https://build.almalinux.org/pulp/content/builds/AlmaLinux-9-x86_64-7033-br/… AlmaLinux 8/9: echo 1 > /sys/devices/system/cpu/microcode/reload For full details please see our blog post at https://almalinux.org/blog/zenbleed-patch-call-for-testing/ The updates are expected to hit the production repos in the coming days. -- Jonathan Wright AlmaLinux Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>

1 0

almalinux没有SUPPORT_END
by 蓝天白云 19 May '23

19 May '23

您好！ almalinux没有SUPPORT_END 谢谢！蓝天白云 592453120(a)qq.com  

2 1

为什么有的rpm文件的权限是-r-xr-xr-x，有的是-r--r--r
by 592453120＠qq.com 06 Jan '23

06 Jan '23

为什么almalinux9光盘中，有的rpm文件的权限是-r-xr-xr-x，有的是-r--r--r。我看了rhel9的rpm文件全部是-r--r--r.

1 0

git.almalinux.org Planned Outage
by Jonathan Wright 19 Dec '22

19 Dec '22

Tomorrow we have a planned outage on git.almalinux.org at 12PM EST / 5PM UTC for Gitea upgrades. The maintenance is anticipated to take less than an hour. -- Jonathan Wright AlmaLinux Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>

1 0

Fwd: [orca] AlmaLinux 9.1 released
by Luna Jernberg 19 Nov '22

19 Nov '22

---------- Forwarded message --------- From: Jude DaShiell <jdashiel(a)panix.com> Date: Sat, Nov 19, 2022 at 7:15 AM Subject: [orca] AlmaLinux 9.1 released To: <orca(a)freelists.org> For us screen reader users, you want the dvd images since these are the only ones with the accessibility stack immediately available. This after a bittorrent download turned out to be quick research since .manifest files for all three flavors of almalinux came as a result of the bittorrent download. Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) . _______________________________________________ orca mailing list orca(a)freelists.org https://www.freelists.org/list/orca Orca wiki: https://wiki.gnome.org/Projects/Orca Orca documentation: https://help.gnome.org/users/orca/stable/ GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html

1 0

Can I use the Elevate tool to migrate my CentOS 7.9 with Virtualmin/Webmin to AlmaLinux 9.0?
by Turritopsis Dohrnii Teo En Ming 16 Nov '22

16 Nov '22

Subject: Can I use the Elevate tool to migrate my CentOS 7.9 with Virtualmin/Webmin to AlmaLinux 9.0? Good day from Singapore, I understand both CentOS Linux and AlmaLinux follow Red Hat Enterprise Linux (RHEL). I have 2 CentOS 7.9 Linux virtual private servers (VPS) in Europe. They are running Virtualmin/Webmin web hosting control panel in master and slave configuration. Unfortunately, the end of life (EOL) date for CentOS 7.9 is 30 June 2024, which is less than 2 years away. Can I use the Elevate tool to migrate my CentOS 7.9 with Virtualmin/Webmin to AlmaLinux 9.0? Is it technically impossible or will result in too many complications? Should I install AlmaLinux 9.0 from fresh and then install Virtualmin instead? If I choose this route, I will need to ask Virtualmin developers how I can migrate the web hosting control panel from CentOS 7.9 to AlmaLinux 9.0. Please advise. Thank you. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore Blogs: https://tdtemcerts.blogspot.com https://tdtemcerts.wordpress.com

1 0

Status of certbot packages on Alma v9
by Bill Campbell 20 Jul '22

20 Jul '22

What is the status of the certbot packages? They can't be installed now as they all depend on python3.6. Thanks Bill -- INTERNET: bill(a)celestial.com Bill Campbell; Celestial Software LLC URL: http://www2.celestial.com/ 6641 E. Mercer Way Mobile: (206) 947-5591 PO Box 820 Mercer Island, WA 98040-0820

2 2

"virt" modules and discrepancies vs Rocky
by Nux 13 May '22

13 May '22

Hello, We've just been bit by some libvirt updates in our project (Apache Cloudstack) which basically broke basic functionality on AlmaLinux 8.4. I expected the same problem to happen on RockyLinux 8.4, however turns out the libvirt on this one was an older version and not even "yum update" changed this. On closer investigation I noticed Rocky actually ships 5 "virt" modules, according to "yum module info virt", my Alma test box only ships one, which is also very up to date. No actual complaints here, but can someone explain to me why the discrepancy? Didn't use EL8 much, but expected all "clones" to be more or less identical, but turns out there are differences that matter. Thanks -- Nux www.nux.ro

3 9

AlmaLinux Talk @ Linuxfest Northwest Online 2022
by Luna Jernberg 25 Apr '22

25 Apr '22

Hey! The talk that was held at Linuxfest Northwest Online 2022 in Online Bellingham is up on Youtube now: https://www.youtube.com/watch?v=fA4GM0qrD7E *watching*

1 0

Build/level numbers (?) like CentOS maybe
by Christopher Cox 27 Jan '22

27 Jan '22

We are converting from CentOS to AlmaLinux, but noticed that AlmaLinux versions are just 8.5, where CentOS adopted the idea of an extra qualifier representing a "level" within the version For example in CentOS 8, you see: CentOS Linux release 8.5.2111 Could something like that be done in AlmaLinux? It can help identify the "level" within the release with regards to updates. Wasn't sure the best place for this, I mean it's not a "bug", it's more like an enhancement, but not even that.

2 2

Alma Mailinglists
by Luna Jernberg 01 Dec '21

01 Dec '21

Hello! nice with some mailinglists for us that likes good old email and not only chat :)

1 0