As noted in a previous post, I had to restore the root portion of my system after a failed attempt to upgrade to F16 Beta. I'm now reinstalling some software I use, and was trying to install gtk3-devel so I can continue working on GXml this weekend.
I encountered this error message:
"Error: Protected multilib versions: libXi-1.4.3-2.fc15.i686 != libXi-1.4.3-3.fc15.x86_64"
One of the first Google search results is on Fedora Forum, titled "[SOLVED] Issues installing wine (FC15) - FedoraForum.org". Sadly, the solutions that worked for others didn't apply to me. Instead, my problem results because, for some reason, after installing from the live USB key, the two software repositories that Fedora was looking for software in were "fedora" and "updates-testing" rather than "fedora" and "updates". I switched it to the latter two, but now I have some packages installed from "updates-testing" that are too new.
I realised this when I re-read the message and realised that they were different version numbers, and that the latest one wasn't in "updates". So, I downgraded it with
# yum downgrade libXi
Yay!
2011-10-14
2011-10-13
Catastrophic failures while upgrading to beta releases
Posted by
Richard
um
11:16
Labels: #GNOME, #Technology, catastrophe, data loss, disaster, fedora, fedora 16, gnome, oh the humanity
Labels: #GNOME, #Technology, catastrophe, data loss, disaster, fedora, fedora 16, gnome, oh the humanity
GNOME 3.2 was released last month, for which I attended a release party and met cool people. I've wanted to upgrade to it from GNOME 3.0 for a little while, but I use Fedora and Fedora's next release including GNOME 3.2 comes out on November 8th. Obviously, I'm not that patient.
One way I could start using GNOME 3.2 would be to build it locally using jhbuild. That might be fun, but I'd like to ensure that the surrounding distribution played well with it, so my intent had been to upgrade to a Fedora 16 Beta. A beta release: what could go wrong? I mean, it's not an alpha! For the record, I usually wait until one of the release candidates comes out before prematurely upgrading to a new Fedora. On the weekend, I used preupgrade with a Fedora 15 installation on a tablet to successfully upgrade to Fedora 16 Beta. (Yay for an on-screen keyboard, though I have to file bugs for when using it eventually prevents mouse clicks somehow?) So, I thought upgrading on my main laptop should go just as smoothly!
So yah, one of the core packages, util-linux, failed to upgrade, and the installer could not roll back, and my hybrid Fedora installation could not boot afterwards, stuck in its half-upgraded, inconsistent state. OH NO.
How I've avoided disaster
If you have any advice or tips of your own for recovering from system upgrades gone awry, please share :D
One way I could start using GNOME 3.2 would be to build it locally using jhbuild. That might be fun, but I'd like to ensure that the surrounding distribution played well with it, so my intent had been to upgrade to a Fedora 16 Beta. A beta release: what could go wrong? I mean, it's not an alpha! For the record, I usually wait until one of the release candidates comes out before prematurely upgrading to a new Fedora. On the weekend, I used preupgrade with a Fedora 15 installation on a tablet to successfully upgrade to Fedora 16 Beta. (Yay for an on-screen keyboard, though I have to file bugs for when using it eventually prevents mouse clicks somehow?) So, I thought upgrading on my main laptop should go just as smoothly!
Basically says there was a catastrophic failure and installation can't continue |
So yah, one of the core packages, util-linux, failed to upgrade, and the installer could not roll back, and my hybrid Fedora installation could not boot afterwards, stuck in its half-upgraded, inconsistent state. OH NO.
How I've avoided disaster
- backed up: All my personal data is backed up regularly, even in another city. Two back-ups, different locations, and backed up before trying the upgrade. Phew.
- separate system and data partitions: My personal data is on a separate partition. On a 500GB HD, I had half for the system (of which only 12GB were actually used) and half for my personal data (of which about 100GB is in use). This would let me re-install my system without reformatting everything and losing my personal data.
- recovery live USB key: I have a nifty Live USB key with Fedora 15 on it that my laptop can boot from, so I can still access my files and use my computer.
- creating redundant system partitions:
- I don't actually want to get rid of my old system set-up: if possible, I want to figure out what went wrong, and I want to have access to the list of packages I previously had installed so I can let them reinstall overnight, so I can use resize2fs and lvreduce to first resize the system's file system down to something petite (25GB), resize the partition (logical volume in my case) down to the size of the file system it holds, and then create a new system partition with the left over space (actually, I just used another 25GB for that).
- Now I have one large partition with personal data (which is safe), and
two smaller partitions for system installations: I can actually install
two systems and switch between them if I like (dual-boot between two
Fedora Linux installations? :D). I'll keep this layout for a while, so
if things go wrong in future upgrades, I'll always have a safe
installation to boot from without needing a Live USB key.
If you have any advice or tips of your own for recovering from system upgrades gone awry, please share :D
Abonnieren
Posts (Atom)
Dieses Blog durchsuchen
Labels
#Technology
#GNOME
gnome
gxml
fedora
bugs
linux
vala
google
#General
firefox
security
gsoc
GUADEC
android
bug
xml
fedora 18
javascript
libxml2
programming
web
blogger
encryption
fedora 17
gdom
git
emacs
libgdata
memory
mozilla
open source
serialisation
upgrade
web development
API
Spain
containers
design
evolution
fedora 16
fedora 20
fedora 22
fedup
file systems
friends
future
glib
gnome shell
internet
luks
music
performance
phone
photos
php
podman
preupgrade
tablet
testing
typescript
yum
#Microblog
Network Manager
adb
apache
art
automation
bash
brno
catastrophe
css
data loss
debian
debugging
deja-dup
disaster
docker
emusic
errors
ext4
facebook
fedora 19
gee
gir
gitlab
gitorious
gmail
gobject
google talk
google+
gtk
html
libxml
mail
microsoft
mtp
mysql
namespaces
nautilus
nextcloud
owncloud
picasaweb
pitivi
ptp
python
raspberry pi
resizing
rpm
school
selinux
signal
sms
speech dispatcher
systemd
technology
texting
time management
uoguelph
usability
video
web design
youtube
#Tech
Air Canada
C
Electron
Element
Empathy
Europe
GError
GNOME 3
GNOME Files
Go
Google Play Music
Grimes
IRC
Mac OS X
Mario Kart
Memento
Nintendo
Nintendo Switch
PEAP
Selenium
Splatoon
UI
VPN
Xiki
accessibility
advertising
ai
albums
anaconda
anonymity
apple
ask
asus eee top
automake
autonomous automobiles
b43
backup
battery
berlin
bit rot
broadcom
browsers
browsing
canada
canadian english
cars
chrome
clarity
comments
communication
compiler
complaints
computer
computers
configuration
console
constructive criticism
cron
cropping
customisation
dataloss
dconf
debug symbols
design patterns
desktop summit
development
discoverability
distribution
diy
dnf
documentation
drm
duplicity
e-mail
efficiency
email
english
environment
estate
experimenting
ext3
fedora 11
festival
file formats
firejail
flac
flatpak
forgottotagit
freedom
friendship
fuse
galaxy nexus
galton
gay rights
gdb
german
germany
gimp
gio
gjs
gnome software
gnome-control-center
google assistant
google calendar
google chrome
google hangouts
google reader
gqe
graphviz
growth
gtest
gtg
gvfs
gvfs metadata
hard drive
hard drives
hardware
help
hp
humour
ide
identity
instagram
installation
instant messaging
integration
intel
interactivity
introspection
jabber
java
java 13
jobs
kernel
keyboard
language
language servers
languages
law
learning
lenovo
letsencrypt
libreoffice
librpm
life
livecd
liveusb
login
lsp
macbook
maintainership
mariadb
mario
matrix
memory leaks
messaging
mounting
mouse
netflix
new zealand
node
nodelist
numix
obama
oci
ogg
oggenc
oh the humanity
open
open standards
openoffice
optimisation
org-mode
organisation
package management
packagekit
paint shedding
parallelism
pdo
perl
pipelight
privacy
productivity
progress
progressive web apps
pumpkin
pwa
pyright
quality
recursion
redhat
refactoring
repairs
report
rhythmbox
rust
sandboxes
scheduling
screenshots
self-navigating car
shell
sleep
smartphones
software
software engineering
speed
sql
ssd
synergy
tabs
test
tests
themes
thesis
tracker
travel
triumf
turtles
tv
tweak
twist
typing
university
update
usb
user experience
valadoc
video editing
volunteering
vpnc
waf
warm
wayland
weather
web apps
website
wifi
wiki
wireless
wishes
work
xinput
xmpp
xorg
xpath
Powered by Blogger.