Project

General

Profile

Housekeeping #2159

Updated by bill-auger about 5 years ago

I recently migrated my system (Chromebook C201) from ALARM to Parabola, using the guidelines "here":https://wiki.parabola.nu/Migration_from_Arch_ARM. I got through it, but experienced a handful of issues along the way:

# #1 The Parabola armv7 pacman package seems to depend on 'archlinux-keyring' and 'archlinux32-keyring'; however, the instructions do not say to install either of these before upgrading to the Parabola pacman. So, I had to switch the mirrors back to ALARM again, so I could install these. It seems strange that the Parabola version of pacman should depend on these, when the ALARM version doesn't.
#


#2
Before running 'pacman -Suu', pacman -Sy should be run first, after updating pacman.conf, as the database needs to be updated.
# When


#3
I installed linux-libre-chromebook, it was by default going to 'dd' the kernel image to my root partition (which would have been bad news), as opposed to the correct kernel partition. This is probably the most serious issue, imo.
# I
experienced dependency issues with both iceweasel and xmms2 during the migration:

iceweasel:
<pre>
# pacman -S iceweasel
resolving dependencies...
warning: cannot resolve "icu<62", a dependency of "iceweasel"
:: The following package cannot be upgraded due to unresolvable dependencies:
iceweasel
</pre>

xmms2:
<pre>
# pacman -S xmms2
warning: downgrading package xmms2 (0.8DrO_o.949.gca15e830-14 => 0.8DrO_o.949.gca15e830-7.parabola1)
resolving dependencies...
warning: cannot resolve "perl<5.27", a dependency of "xmms2"
:: The following package cannot be upgraded due to unresolvable dependencies:
xmms2
</pre>

#4 When I installed linux-libre-chromebook, it was by default going to 'dd' the kernel image to my root partition (which would have been bad news), as opposed to the correct kernel partition. This is probably the most serious issue, imo.


Perhaps it would be better to break these out into separate issues?

Back