AlmaLinux List Archives
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview

Devel

Thread Start a new thread
Download
Threads by month
  • ----- 2025 -----
  • May
  • April
  • March
  • February
  • January
  • ----- 2024 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2023 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2022 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2021 -----
  • December
devel@lists.almalinux.org

September 2023

  • 1 participants
  • 1 discussions
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
0 0

HyperKitty Powered by HyperKitty version 1.3.9.