You are not logged in.
Pages: 1
Hello, i'm trying to update an older archlinux installation. Is it possible?
After a lot of problem (solved), now i'm stuck here
pacman -Syu
--cut--
(1132/1132) controllo dei conflitti in corso [############################################################] 100%
errore: impossibile eseguire l'operazione richiesta (file in conflitto)
imath: /usr/lib/libImath.so exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/Iex.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IexBaseExc.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IexErrnoExc.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IexExport.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IexForward.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IexMacros.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IexMathExc.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IexMathFloatExc.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IexMathIeeeExc.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IexNamespace.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IexThrowErrnoExc.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IlmThread.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IlmThreadExport.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IlmThreadForward.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IlmThreadMutex.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IlmThreadNamespace.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IlmThreadPool.h exists in filesystem (owned by ilmbase)
openexr: /usr/include/OpenEXR/IlmThreadSemaphore.h exists in filesystem (owned by ilmbase)
openexr: /usr/lib/libIex.so exists in filesystem (owned by ilmbase)
openexr: /usr/lib/libIlmThread.so exists in filesystem (owned by ilmbase)
Si sono verificati degli errori, nessun pacchetto è stato aggiornato.Can someone help me?
Thanks
Last edited by dax79 (2022-01-01 13:18:57)
Offline
Use the Arch Linux Archive to update the system in steps and follow the news articles to apply manual interventions as required.
And please prepend commands with LC_ALL=C to make them output in English.
Jin, Jîyan, Azadî
Offline
For that specific error, I'd just remove ilmbase (and any packages that depend on it), upgrade, then reinstall any packages that you removed but still want.
How old is this system? When was the last successful upgrade?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
How old? To "properly" do it you'd want to do it with intermediate steps via the ALA: https://wiki.archlinux.org/title/Arch_Linux_Archive but this ilmbase package is more than 3 years old that this package existed, you might be faster just reinstalling at that point. There are a load of intermediate steps you'd have to take here.
Edit: Holy moly I'm slow
Last edited by V1del (2021-12-28 16:45:29)
Online
Thanks to everybody
.
And please prepend commands with LC_ALL=C to make them output in English.
Ok, sorry
For that specific error, I'd just remove ilmbase (and any packages that depend on it), upgrade, then reinstall any packages that you removed but still want.
How old is this system? When was the last successful upgrade?
The last succesful upgrade was on 19-02-2019. I have removed ilmbase, then upgrade and then reinstall all removed packages.
Unfortunately now the system is stuck at boot
error: file /boot/vmlinuz-linux not found
alloc magic is broken at...
abortedI think the best way is a new fresh installation
Offline
You could try chroot with a live disk and update from there. Did you manually sync the package database and upgrade the archlinux-keyring package before system upgrade?
Last edited by zpg443 (2021-12-30 16:43:10)
Offline
A bit of a guess, but I'd not be surprised if this wasn't due to the kernel no longer being installed to /boot/ but rather being copied there by a post install script which due to the age of your pacman might not have run. Assuming you now have an up-to-date pacman, reinstalling the kernel should fix that (this would require chrooting from a bootable medium as noted above).
That said, there could be other issues due to other changes over the past 3 years.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
https://archlinux.org/news/moving-to-zs … kinitcpio/
Seems quite likely.
Offline
Thanks again to all.
Did you manually sync the package database and upgrade the archlinux-keyring package before system upgrade?
Yes, I do.
But now the pc is running with a new fresh installation, (probably) more faster then repair the old one.
Davide
Offline
Please remember to mark your thread [SOLVED] (edit the title of your first post).
Offline
Please remember to mark your thread [SOLVED] (edit the title of your first post).
Ok, but is really correct to mark as solved? Because in this case I opt for a different solution
Offline
Do you want more replies? You chose to "solve" your problem by reinstalling. Marking it [SOLVED] indicates to other people that there is no point in replying further.
Offline
Pages: 1