| Summary: | after a successfull upgrade mageia5 to 6 impossibility to install filesystem-2.1.9-28.mga6.x86_64 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | peter lawford <petlaw726> |
| Component: | RPM Packages | Assignee: | Base system maintainers <basesystem> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11 |
| Version: | 6 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | filesystem-2.1.9-28.mga6.x86_64 | CVE: | |
| Status comment: | |||
| Attachments: |
return of urpmi --auto-update --debug
return of rpm -qa |grep mga5 return of rpm -qa |grep mga6 some bugs encountered during the upgrade process |
||
Check your free space df -h If you lack of free space try free some space a good candidate is the journalctl logs, as root journalctl --vacuum-time=1s (In reply to katnatek from comment #1) > Check your free space > > df -h > > If you lack of free space try free some space a good candidate is the > journalctl logs, as root > > journalctl --vacuum-time=1s Thanks, katnatek! @ Peter Does freeing up space indeed solve the problem? CC:
(none) =>
marja11 (In reply to katnatek from comment #1) > Check your free space > > df -h > > If you lack of free space try free some space a good candidate is the > journalctl logs, as root > > journalctl --vacuum-time=1s thank you for your reply, but unfortunately, I have yet plenty free space: this distrib lies on 3 lv: /dev/vgmageia/lvbootmga5-64 /dev/vgmageia/lvrootmga5-64 /dev/vgmageia/lvhomemga5-64 after mounting these 3 volumes on the mounting points: /mnt/bootmga5-64 /mnt/rootmga5-64 /mnt/homemga5-64 of my actual mageia6 I use every day for my business, df returns (only the three last lines are relevant): [root@magaux alain4]# LC_ALL=C df Filesystem Size Used Avail Use% Mounted on devtmpfs 12G 0 12G 0% /dev tmpfs 12G 33M 12G 1% /dev/shm tmpfs 12G 1.9M 12G 1% /run /dev/mapper/vgmagaux-lvrootmagaux 27G 21G 5.1G 80% / tmpfs 12G 0 12G 0% /sys/fs/cgroup none 12G 8.0K 12G 1% /tmp /dev/mapper/vgmagaux-lvbootmagaux 1.2G 96M 978M 9% /boot /dev/mapper/vgmagaux-lvhomemagaux 16G 12G 2.8G 82% /home /dev/mapper/vghome-lvscratch 20G 121M 18G 1% /home/alain4/Téléchargements /dev/mapper/vghome-lvhomedoc 185G 115G 61G 66% /home/alain4/Documents tmpfs 2.4G 0 2.4G 0% /run/user/480 tmpfs 2.4G 28K 2.4G 1% /run/user/500 /dev/mapper/vgmageia-lvrootmga5--64 27G 18G 8.1G 69% /mnt/rootmga5-64 /dev/mapper/vgmageia-lvbootmga5--64 1.2G 83M 1008M 8% /mnt/bootmga5-64 /dev/mapper/vgmageia-lvhomemga5--64 16G 13G 1.5G 90% /mnt/homemga5-64 [root@magaux alain4]# (In reply to Marja Van Waes from comment #2) > (In reply to katnatek from comment #1) > > Check your free space > > > > df -h > > > > If you lack of free space try free some space a good candidate is the > > journalctl logs, as root > > > > journalctl --vacuum-time=1s > > Thanks, katnatek! > > @ Peter > > Does freeing up space indeed solve the problem? see comment 3, it doesn't unfortunately solve the problem I need this distrib (mga5-64), I don't use for my daily business, to make trials for migration from mageia6 to the future mageia7 and its beta versions: it is then necessary that mga5-64 had no bug and everything in the machinery be OK NOT YET SOLVED! this means that if somebody want to belatedly upgrade a mageia5 to 6, he can't! >after a successfull upgrade in command line of mageia5 to mageia6
if you have still the rpm filesystem-2.1.9-25.1.mga5.x86_64 the update was not sucessfull
what give:
rpm -qa | grep -c mga5
rpm -qa | grep -c mga6
rpm -q rpm
urpmi --auto-update --debug
Created attachment 10606 [details]
return of urpmi --auto-update --debug
Created attachment 10607 [details]
return of rpm -qa |grep mga5
Created attachment 10608 [details]
return of rpm -qa |grep mga6
Created attachment 10609 [details]
some bugs encountered during the upgrade process
(In reply to Manuel Hiebel from comment #6) > >after a successfull upgrade in command line of mageia5 to mageia6 > if you have still the rpm filesystem-2.1.9-25.1.mga5.x86_64 the update was > not sucessfull > > what give: > rpm -qa | grep -c mga5 > rpm -qa | grep -c mga6 > rpm -q rpm > urpmi --auto-update --debug here are the following attached files: returns of the above commands In fact this bug is the second of 3, the other two being bug 23996 (oldest) and bug 25320 (most recent) - although the error is slightly different. Closing this middle one because the latest bug is now the most relevant. *** This bug has been marked as a duplicate of bug 25320 *** Resolution:
(none) =>
DUPLICATE |
Description of problem:after a successfull upgrade in command line of mageia5 to mageia6, it is not possible to update the package filesystem-2.1.9-25.1.mga5.x86_64 to filesystem-2.1.9-28.mga6.x86_64 [root@mageia5_64 alain4]# LC_ALL=C urpmi filesystem http://mirrors.mageia.org/api/mageia.6.x86_64.list: media/core/release/filesystem-2.1.9-28.mga6.x86_64.rpm installing filesystem-2.1.9-28.mga6.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ################################################################################################################################ 1/1: filesystem ################################################################################################################################ error: unpacking of archive failed on file /var/lock: cpio: rename ERROR: 'unpack' failed for filesystem-2.1.9-28.mga6.x86_64 error: filesystem-2.1.9-28.mga6.x86_64: install failed error: filesystem-2.1.9-25.1.mga5.x86_64: erase skipped Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.