Description of problem: I have achieved an updating of mageia 6 to mageia 7, using successively the commands: [root@mga6-64 alain4]# urpmi.removemedia -a [root@mga6-64 alain4]# urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.7.$ARCH.list' and finally: [root@mga6-64 alain4]# urpmi --auto-update --auto --force everything seem to normally work, but when the migration process (mga6 to mga7) was finished the package filesystem was not upgraded: typing once more the command urpmi --auto-update --auto --force yields: [root@mga6-64 alain4]# LANGUAGE=C urpmi --auto-update --auto --force medium "Core Release" is up-to-date medium "Core Updates" is up-to-date medium "Nonfree Release" is up-to-date medium "Nonfree Updates" is up-to-date medium "Tainted Release" is up-to-date medium "Tainted Updates" is up-to-date medium "Nonfree 32bit Release" is up-to-date medium "Nonfree 32bit Updates" is up-to-date medium "Tainted 32bit Release" is up-to-date medium "Tainted 32bit Updates" is up-to-date http://mirrors.mageia.org/api/mageia.7.x86_64.list: media/core/release/filesystem-2.1.9-30.mga7.x86_64.rpm installing filesystem-2.1.9-30.mga7.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ################################################################################################################################# 1/1: filesystem ################################################################################################################################# error: unpacking of archive failed on file /var/lock: cpio: File from package already exists as a directory in system ERROR: 'unpack' failed for filesystem-2.1.9-30.mga7.x86_64 error: filesystem-2.1.9-30.mga7.x86_64: install failed error: filesystem-2.1.9-28.mga6.x86_64: erase skipped furthermore, many mga6 packages remain after this migration; see the return of the command [root@mga6-64 alain4]# rpm -qa |grep mga6 in the file here attached; hence I consider that the upgrading is not complete and dolphin doesn't work too Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Created attachment 11255 [details] return of rpm -qa |grep mga6
I specify that the remaining mga6 pkgs in the attached file ARE NOT orphans
Hi Peter, Thanks for the report. Please attach log.txt that is the result of running, as root: journalctl -a --since="YYYY-MM-DD hh:mm" --until="YYYY-MM-DD hh:mm" > log.txt and adjust the --since time to right before you started to upgrade and the --until time to shortly after you finished the first upgrade attempt
CC: (none) => mageiatools, marja11Keywords: (none) => NEEDINFO
(In reply to Marja Van Waes from comment #3) > Hi Peter, > > Thanks for the report. > > Please attach log.txt that is the result of running, as root: > > journalctl -a --since="YYYY-MM-DD hh:mm" --until="YYYY-MM-DD hh:mm" > > log.txt > > and adjust the --since time to right before you started to upgrade and the > --until time to shortly after you finished the first upgrade attempt sorry, can't attach log.txt since attached files in bugzilla are limited to 1000 KB!! and it makes 3MB if you allow me, I can send to you this file log.txt at your private mail address marja11@xs4all.nl but it seems now that the pkg "filsystem" has completely disappeared: [root@mga6-64 alain4]# rpm -qa |grep filesystem fontpackages-filesystem-1.44-12.mga7 cups-filesystem-2.2.11-2.mga7 mozilla-filesystem-1.9-8.mga7 javapackages-filesystem-5.3.0-6.mga7 web-assets-filesystem-5-4.mga7 telepathy-filesystem-0.0.2-7.mga7 lib64boost_filesystem1.68.0-1.68.0-4.mga7 [root@mga6-64 alain4]# furthermore: [root@mga6-64 alain4]# LANGUAGE=C dnf install filesystem Last metadata expiration check: 0:04:13 ago on sam. 17 août 2019 12:15:17 CEST. Dependencies resolved. ==================================================================================================================================================================== Package Architecture Version Repository Size ==================================================================================================================================================================== Installing: filesystem x86_64 2.1.9-30.mga7 mageia-x86_64 16 k Transaction Summary ==================================================================================================================================================================== Install 1 Package Total download size: 16 k Installed size: 0 Is this ok [y/N]: y Downloading Packages: determining the fastest mirror (1 hosts).. done. [=== ] --- B/s | 0 B --:-- ETA filesystem-2.1.9-30.mga7.x86_64.rpm 1.2 MB/s | 16 kB 00:00 -------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 16 kB/s | 16 kB 00:00 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Running scriptlet: filesystem-2.1.9-30.mga7.x86_64 1/1 Preparing : 1/1 Installing : filesystem-2.1.9-30.mga7.x86_64 1/1 Error unpacking rpm package filesystem-2.1.9-30.mga7.x86_64 error: unpacking of archive failed on file /var/lock: cpio: File from package already exists as a directory in system Verifying : filesystem-2.1.9-30.mga7.x86_64 1/1 Failed: filesystem-2.1.9-30.mga7.x86_64 Error: Transaction failed [root@mga6-64 alain4]# but this result seems to contradict the return of [root@mga6-64 alain4]# LANGUAGE=C dnf --refresh upgrade created by dnf config-manager from http://dl.google.com/linux/chrome/rpm/stable/x86_64 49 kB/s | 1.3 kB 00:00 Mageia 7 - x86_64 - Nonfree 24 kB/s | 3.8 kB 00:00 Mageia 7 - x86_64 - Nonfree - Updates 20 kB/s | 3.3 kB 00:00 Mageia 7 - x86_64 - Tainted 13 kB/s | 4.2 kB 00:00 Mageia 7 - x86_64 - Tainted - Updates 22 kB/s | 3.3 kB 00:00 determining the fastest mirror (1 hosts).. done. [ === ] --- B/s | 0 B --:-- ETA Mageia 7 - x86_64 5.9 kB/s | 4.3 kB 00:00 Mageia 7 - x86_64 - Updates 26 kB/s | 3.3 kB 00:00 Opera packages 62 kB/s | 2.9 kB 00:00 skype (stable) 23 kB/s | 2.9 kB 00:00 vivaldi 84 kB/s | 2.9 kB 00:00 Dependencies resolved. Nothing to do. Complete! [root@mga6-64 alain4]# the latter shows that there is no pkg to upgrade, including "filesystem" I am really sorry, but I don't understand anything! wait for your reply about log.txt
Created attachment 11256 [details] 1st part of log.txt
Created attachment 11257 [details] 2nd part of log.txt
Created attachment 11258 [details] 3rd part of log.txt
Created attachment 11259 [details] 4th and last part of log.txt
thanks to the command head and tail, I could divide log.txt in 4 parts of size < 1000KB
@Peter Marja forgot in c3 to advise (as she normally does) compressing the log.txt file, normally with xz. Sorry for the hassle you had uploading the log, and thank you for doing that. It looks as if your system already had the new package: $ rpm -q filesystem [Can you please do this ?] filesystem-2.1.9-30.mga7 > cpio: File from package already exists as a directory in system which accounts for all the failures. But how? > but it seems now that the pkg "filsystem" has completely disappeared No. "The filesystem package is one of the basic packages that is installed on a Mageia Linux system." Because it is basic, I wonder whether somewhere during the upgrade it got done twice. If you indeed have the new version, I think there is nothing to worry about on that score. @Marja: do we keep this bug for this aspect only? This looks like a one-off, otherwise all upgrades would suffer it. To whom do we pass this aspect? For other problems: Residual Mageia 6 packages can be legitimate if they no longer exist in Mageia 7 - they are carried forward. However, your list https://bugs.mageia.org/attachment.cgi?id=11255 seems to include a lot of things which should not be there. > I specify that the remaining mga6 pkgs in the attached file ARE NOT orphans Do you routinely use the server kernel? @Marja: or do we change this bug to all those M6 packages? Or raise a new one for that? To whom do we pass this aspect? @Peter > and dolphin doesn't work too Please raise a separate bug for this. When you do so, please state: - the background (after an upgrade M6->M7) - the desktop(s) you have installed - which desktop has the problem - the version of the dolphin package - a fuller description of what does not work. Can you start dolphin - from an icon or the command line ? Does it start but crash, or not work properly ?
CC: (none) => lewyssmith
(In reply to Lewis Smith from comment #10) > @Peter > Marja forgot in c3 to advise (as she normally does) compressing the log.txt > file, normally with xz. Sorry for the hassle you had uploading the log, and > thank you for doing that. > > It looks as if your system already had the new package: > $ rpm -q filesystem [Can you please do this ?] > filesystem-2.1.9-30.mga7 [alain4@mga6-64 ~]$ LANGUAGE=C rpm -q filesystem package filesystem is not installed [alain4@mga6-64 ~]$ > > cpio: File from package already exists as a directory in system > which accounts for all the failures. But how? > > > but it seems now that the pkg "filsystem" has completely disappeared > No. "The filesystem package is one of the basic packages that is installed on > a Mageia Linux system." > Because it is basic, I wonder whether somewhere during the upgrade it got > done twice. If you indeed have the new version, I think there is nothing to > worry about on that score. > @Marja: do we keep this bug for this aspect only? This looks like a one-off, > otherwise all upgrades would suffer it. To whom do we pass this aspect? > > For other problems: > Residual Mageia 6 packages can be legitimate if they no longer exist in > Mageia 7 - they are carried forward. However, your list > https://bugs.mageia.org/attachment.cgi?id=11255 > seems to include a lot of things which should not be there. > > I specify that the remaining mga6 pkgs in the attached file ARE NOT orphans > Do you routinely use the server kernel? yes, I usually use the server kernel > @Marja: or do we change this bug to all those M6 packages? Or raise a new > one for that? To whom do we pass this aspect? > > @Peter > > and dolphin doesn't work too > Please raise a separate bug for this. When you do so, please state: > - the background (after an upgrade M6->M7) > - the desktop(s) you have installed > - which desktop has the problem > - the version of the dolphin package > - a fuller description of what does not work. Can you start dolphin - from > an icon or the command line ? Does it start but crash, or not work properly ? forget it, I was wrong, just after the upgrade kdelauncher didn't work; but it normally works now to resume, the problem of filesystem (mga6 or 7) subsists, and I actually don't know if it is installed or not; I don't know what to do with the residual pkgs mageia6; would be it dangerous to brutally remove them? I did that when migrating from mga5 to 6, and I didn't get any problem
by the way, I see that pkg gmusicbrowser no longer exists in mga7
Hallo! I recall you that this bug is not yet closed [root@mga6-64 alain4]# LANGUAGE=C dnf install filesystem Last metadata expiration check: 0:18:33 ago on lun. 19 août 2019 13:33:33 CEST. Dependencies resolved. ==================================================================================================================================================================== Package Architecture Version Repository Size ==================================================================================================================================================================== Installing: filesystem x86_64 2.1.9-30.mga7 mageia-x86_64 16 k Transaction Summary ==================================================================================================================================================================== Install 1 Package Total download size: 16 k Installed size: 0 Is this ok [y/N]: Y Downloading Packages: filesystem-2.1.9-30.mga7.x86_64.rpm 1.1 MB/s | 16 kB 00:00 -------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 87 kB/s | 16 kB 00:00 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Running scriptlet: filesystem-2.1.9-30.mga7.x86_64 1/1 Preparing : 1/1 Installing : filesystem-2.1.9-30.mga7.x86_64 1/1 Error unpacking rpm package filesystem-2.1.9-30.mga7.x86_64 error: unpacking of archive failed on file /var/lock: cpio: File from package already exists as a directory in system Verifying : filesystem-2.1.9-30.mga7.x86_64 1/1 Failed: filesystem-2.1.9-30.mga7.x86_64 Error: Transaction failed [root@mga6-64 alain4]# thank you for not forgetting
the same already happened a few months ago: see bug #24000
From c13: > I recall you that this bug is not yet closed But we *are* dealing with it. From c11: > $ LANGUAGE=C rpm -q filesystem > package filesystem is not installed This is important, thank you for confirming it. > the same already happened a few months ago: see bug #24000 In fact there was an even older one, bug 23996. We should have spotted these duplicates. I am closing the two earlier bugs, 5->6 upgrade, although the error message is slightly different. This latest one is what matters. If you knew about the earlier bug(s), why raise a new one? One can change the release from 5 to 6 to 7. Assigning this globally, and CC'ing Manuel because he looked at bug 24000.
Version: 6 => 7CC: lewyssmith => manuel.mageiaAssignee: bugsquad => pkg-bugs
*** Bug 23996 has been marked as a duplicate of this bug. ***
*** Bug 24000 has been marked as a duplicate of this bug. ***
I think this should be assigned to rpm group, not global. My error.
Assignee: pkg-bugs => rpmstack
How old is this initial install ? Something installed on the system has presumably changed the /var/lock symlink to a regular directory... /var/lock has been a symlink to /run/lock since Mageia 3 To confirm: ls -l /var
CC: (none) => tmb
BINGO!! Thomas Backlund is right! I have removed /var/lock, which content was the same as /run/lock and created a symlink: [root@mga6-64 var]# ln -s ../run/lock lock and installed filesystem-2.1.9-30.mga7.x86_64.rpm with dnf install (sorry, in french): [root@mga6-64 alain4]# dnf install filesystem Dernière vérification de l’expiration des métadonnées effectuée il y a 0:06:02 le mar. 20 août 2019 14:11:17 CEST. Dépendances résolues. ==================================================================================================================================================================== Paquet Architecture Version Dépôt Taille ==================================================================================================================================================================== Installation: filesystem x86_64 2.1.9-30.mga7 mageia-x86_64 16 k Résumé de la transaction ==================================================================================================================================================================== Installer 1 Paquet Taille totale des téléchargements : 16 k Taille des paquets installés : 0 Voulez-vous continuer ? [o/N] : o Téléchargement des paquets : filesystem-2.1.9-30.mga7.x86_64.rpm 601 kB/s | 16 kB 00:00 -------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 83 kB/s | 16 kB 00:00 Test de la transaction en cours La vérification de la transaction a réussi. Lancement de la transaction de test Transaction de test réussie. Exécution de la transaction Exécution du scriptlet: filesystem-2.1.9-30.mga7.x86_64 1/1 Préparation en cours : 1/1 Installation : filesystem-2.1.9-30.mga7.x86_64 1/1 Exécution du scriptlet: filesystem-2.1.9-30.mga7.x86_64 1/1 Vérification de : filesystem-2.1.9-30.mga7.x86_64 1/1 [root@mga6-64 alain4]# dnf install filesystem Dernière vérification de l’expiration des métadonnées effectuée il y a 0:06:02 le mar. 20 août 2019 14:11:17 CEST. Dépendances résolues. ==================================================================================================================================================================== Paquet Architecture Version Dépôt Taille ==================================================================================================================================================================== Installation: filesystem x86_64 2.1.9-30.mga7 mageia-x86_64 16 k Résumé de la transaction ==================================================================================================================================================================== Installer 1 Paquet Taille totale des téléchargements : 16 k Taille des paquets installés : 0 Voulez-vous continuer ? [o/N] : o Téléchargement des paquets : filesystem-2.1.9-30.mga7.x86_64.rpm 601 kB/s | 16 kB 00:00 -------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 83 kB/s | 16 kB 00:00 Test de la transaction en cours La vérification de la transaction a réussi. Lancement de la transaction de test Transaction de test réussie. Exécution de la transaction Exécution du scriptlet: filesystem-2.1.9-30.mga7.x86_64 1/1 Préparation en cours : 1/1 Installation : filesystem-2.1.9-30.mga7.x86_64 1/1 Exécution du scriptlet: filesystem-2.1.9-30.mga7.x86_64 1/1 Vérification de : filesystem-2.1.9-30.mga7.x86_64 1/1 Installé: filesystem-2.1.9-30.mga7.x86_64 Terminé ! [root@mga6-64 alain4]# and now: [root@mga6-64 alain4]# rpm -q filesystem filesystem-2.1.9-30.mga7 [root@mga6-64 alain4]#
(In reply to Thomas Backlund from comment #19) > How old is this initial install ? > > Something installed on the system has presumably changed the /var/lock > symlink to a regular directory... > > /var/lock has been a symlink to /run/lock since Mageia 3 > > To confirm: > > ls -l /var this bug is now solved (see comment 20); hope the change will remain permanent
Thanks for this last info. This bug should have been closed then.
Status: NEW => RESOLVEDResolution: (none) => FIXED