Description of request: I have backported a fix to /etc/os-release to include the missing VERSION_ID field and the addition of macros.dist to mageia-release from Cauldron to mga5. I would appreciate some testing and validation to ensure this doesn't break anything. The changes center around the mageia-release-common subpackage generated by the mageia-release SRPM. Version-Release number of selected component (if applicable): 5-2.1.mga5 Reproducible: Steps to Reproduce:
Neal: to have the update tested, you need to assign this bug to QA and provide an advisory text, as described in the Updates Policy: https://wiki.mageia.org/en/Updates_policy#Maintainer_.28or_any_interested_packager.29
Advisory ========================= Updated mageia-release to add missing field in /etc/os-release and add macros.dist The /etc/os-release file provided by mageia-release was missing the VERSION_ID field, which some applications used for determining the version of a distribution. Additionally, the macros.dist file introduced in Cauldron was backported to Mageia 5. This file adds the following macros: %{dist}, defined as ".mga5" %{mageia}, defined as 5 %{mga5}, defined as 1 The addition of these macros do not affect the existing configuration of services, but is required for some build tools (such as Koji) to be able to sort built packages by distribution release.
Assignee: bugsquad => qa-bugs
Updated packages in core/updates_testing ======================================== mageia-release-Default-5-2.1.mga5 mageia-release-common-5-2.1.mga5 Source RPMs: mageia-release-5-2.1.mga5.src.rpm
And why should we do changes like this in a stable release ? Koji is not used in Mageia.
CC: (none) => tmb
It is true that Koji is not currently used by Mageia. However, it might be in the future on the new server running Mageia 5, and it doesn't have any effect on anything we do currently. Since it has no negative effects (or really any effect) on anything we currently do, it didn't seem like a problem to just bring it in.
(In reply to Neal Gompa from comment #0) > Description of request: > I have backported a fix to /etc/os-release to include the missing VERSION_ID > field and the addition of macros.dist to mageia-release from Cauldron to > mga5. Does your update also fix /etc/version? $ cat /etc/version 5 2 cauldron
CC: (none) => bittwister2
I didn't realize that was a problem. I looked into the spec and I know how to fix it, however, I don't know what to fix it with. Does Mageia 5 have a codename to replace it with?
No codenames really, "Thornicroft" has been used in previous releases but is a leftover and not intended as an actual codename. Please discuss these changes though on dev ML before making them in the stable release. Thanks. Adding feedback marker for now.
Whiteboard: (none) => feedback
(In reply to Neal Gompa from comment #7) > I didn't realize that was a problem. I looked into the spec and I know how > to fix it, however, I don't know what to fix it with. Does Mageia 5 have a > codename to replace it with? Rather than a codename I would rather it be devel, alpha1,2,3, beta1,2,3, rc, rc1,2 or official.
If you want to change it, go with "official" for stable releases as that matches media.cfg
Done. Revised advisory below. Advisory ========================= Updated mageia-release to correct release information files and add macros.dist The /etc/os-release file provided by mageia-release-common was missing the VERSION_ID field, which some applications used for determining the version of a distribution. The /etc/version file provided by mageia-release-common continued to declare it was "cauldron" in stable releases. Additionally, the macros.dist file introduced in Cauldron was backported to Mageia 5. This file adds the following macros: %{dist}, defined as ".mga5" %{mageia}, defined as 5 %{mga5}, defined as 1 The addition of these macros do not affect the existing configuration of services, but is required for some build tools (such as Koji) to be able to sort built packages by distribution release. Updated packages in core/updates_testing ======================================== mageia-release-Default-5-2.2.mga5 mageia-release-common-5-2.2.mga5 Source RPMs: mageia-release-5-2.2.mga5.src.rpm
Whiteboard: feedback => (none)
x86_64 Mate $ cat /etc/os-release NAME="Mageia" VERSION="5" ID=mageia ID_LIKE="mandriva fedora" PRETTY_NAME="Mageia 5" ANSI_COLOR="1;36" HOME_URL="http://www.mageia.org/" SUPPORT_URL="http://www.mageia.org/support/" BUG_REPORT_URL="https://bugs.mageia.org/" Updated the mageia-release packages: $ cat /etc/os-release NAME="Mageia" VERSION="5" ID=mageia VERSION_ID=5 ID_LIKE="mandriva fedora" PRETTY_NAME="Mageia 5" ANSI_COLOR="1;36" HOME_URL="http://www.mageia.org/" SUPPORT_URL="http://www.mageia.org/support/" BUG_REPORT_URL="https://bugs.mageia.org/"
CC: (none) => tarazed25
Whiteboard: (none) => MGA5-64-OK
i586 virtualbox Mate Upgraded the mageia-release packages from Core Updates Testing: [lcl@cursa ~]$ cat /etc/os-release NAME="Mageia" VERSION="5" ID=mageia VERSION_ID=5 ID_LIKE="mandriva fedora" PRETTY_NAME="Mageia 5" ANSI_COLOR="1;36" HOME_URL="http://www.mageia.org/" SUPPORT_URL="http://www.mageia.org/support/" BUG_REPORT_URL="https://bugs.mageia.org/"
Whiteboard: MGA5-64-OK => MGA5-64-OK MGA5-32-OK
Also confirmed: # rpm --eval '%{dist}' .mga5 # rpm --eval '%{mageia}' 5 # rpm --eval '%{mga5}' 1 Validating.
Keywords: (none) => validated_updateWhiteboard: MGA5-64-OK MGA5-32-OK => has_procedure MGA5-64-OK MGA5-32-OKCC: (none) => sysadmin-bugs
CC: (none) => davidwhodginsWhiteboard: has_procedure MGA5-64-OK MGA5-32-OK => has_procedure MGA5-64-OK MGA5-32-OK advisory
Source RPM: mageia-release-5-2.1.mga5.src.rpm => mageia-release-5-2.2.mga5.src.rpm
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0179.html
Status: NEW => RESOLVEDResolution: (none) => FIXED