Description of problem: when trying to use yum to install into a directory, yum complains that there is no enabled repo and suggests to use yum-config-manager to enable one. yum-config-manager cannot be found in any Mageia 4 package. Version-Release number of selected component (if applicable): yum-3.4.3-8.mga4 How reproducible: always Steps to Reproduce: 1. yum --installroot=/opt/LXC/yum-guest install bash 2. 3. There are no enabled repos. Run "yum repolist all" to see the repos you have. You can enable repos with yum-config-manager --enable <repo> Reproducible: Steps to Reproduce:
Assignee: bugsquad => bruno
that tool is provided in the yum-utils package: > rpm -ql yum-utils-1.1.31-1.mga3 [...] /usr/bin/yum-groups-manager [...] That package wasn't regenerated for mga4.
Status: NEW => RESOLVEDResolution: (none) => INVALID
yum-groups-manager != yum-config-manager
Status: RESOLVED => REOPENEDCC: (none) => herbertResolution: INVALID => (none)
Le popié/collé était mauvais mais c'est quand même fourni ! > rpm -ql yum-utils| grep config-manager /usr/bin/yum-config-manager /usr/share/man/man1/yum-config-manager.1.xz
Status: REOPENED => RESOLVEDResolution: (none) => INVALID
The copy/paste was wrong, but the tool is however there: > rpm -ql yum-utils| grep config-manager /usr/bin/yum-config-manager /usr/share/man/man1/yum-config-manager.1.xz
> cat /etc/mageia-release Mageia release 4 (Official) for x86_64 > urpmi.update -a > urpmi yum-utils No package named yum-utils
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
I don't know why the package which was in mga3 has not been made available in mga4. We would need probably a sysadmin feedback on this. I have updated it in mga5 so you'll get it back.
Trying to involve sysadmins by putting their ML in the assign field.
Assignee: bruno => sysadmin-bugsTarget Milestone: --- => Mageia 4
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: REOPENED => RESOLVEDResolution: (none) => OLD
CC: (none) => perrymasterson1
CC: (none) => mageia