Bug 18017 - It is not possible to install a Mageia 5 chroot from Cauldron
Summary: It is not possible to install a Mageia 5 chroot from Cauldron
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-15 22:44 CET by Pascal Terjan
Modified: 2016-11-07 14:55 CET (History)
1 user (show)

See Also:
Source RPM: filesystem
CVE:
Status comment:


Attachments

Description Pascal Terjan 2016-03-15 22:44:59 CET
I tried using iurt but when it tried to create the chroot using --urpmi-root it failed with:

installing dash-static-0.5.7-6.mga5.x86_64.rpm bash-4.3-33.1.mga5.x86_64.rpm libstdc++6-4.9.2-4.mga5.x86_64.rpm ncurses-5.9-21.mga5.x86_64.rpm libgcc1-4.9.2-4.mga5.x86_64.rpm glibc-2.20-20.mga5.x86_64.rpm filesystem-2.1.9-25.mga5.x86_64.rpm run-parts-4.4-4.mga5.x86_64.rpm lib64ncurses5-5.9-21.mga5.x86_64.rpm setup-2.7.21-5.mga5.noarch.rpm from /home/pterjan/chroot_5.x86_64.tmp.YZiFlq/var/cache/urpmi/rpms
starting installing packages
created transaction for installing on /home/pterjan/chroot_5.x86_64.tmp.YZiFlq (remove=0, install=0, upgrade=10)
Installation failed:
        rpmlib(X-CheckUnifiedSystemdir) is needed by filesystem-2.1.9-25.mga5.x86_64

Given that it was still required in Mageia 5, should it still be kept in Mageia 6?
Comment 1 David Walser 2016-03-17 21:18:55 CET
I thought we were going to issue an update for the filesystem package for Mageia 5, dropping that requirement.  I remember this being discussed before.
Comment 2 Marja Van Waes 2016-03-18 08:47:34 CET
assigning to rpm maintainer

CC: (none) => marja11
Assignee: bugsquad => thierry.vignaud

Comment 3 Thierry Vignaud 2016-11-07 14:54:52 CET
We won't carry such a patch in rpm for years after /usrMove whereas other distros have dropped it.
Also it now works.

Source RPM: rpm => filesystem

Comment 4 Thierry Vignaud 2016-11-07 14:55:00 CET
Closing

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.