Subject: Re: [SM-Commit] mouldering development branches
Date: Wed, 26 Mar 2014 18:26:15 +0100
Am Wed, 26 Mar 2014 17:48:05 +0100
schrieb Florian Franzmann <siflfran AT hawo.net>:
> Honestly, I don't think that we will come up with a working migration
> path. We've had this situation for over a year now and nobody has
> has been able to solve it.
Just about any SMGL system update I did over the years needed manual
intervention and multiple tries to succeed. This may be just because of
missing upstream sources (deleting non-freshest release). Heck, we
still have the mandatory circular dependencies, haven't we? (thinking
of xorg and gs, gtk/pango/cairo cruft) So, for folks that are still
with us, a bumpy migration is nothing unexpected.
All I'm asking for is some instructions on how to get the migration
done with manual intervention. At least one should be warned before
going through with the update and an unattended update should result in
a state that still makes it possible to recover manually in the running
system. We have this nice system of important messages that get
repeated after the cast ... if there's some hint about how to get it
done, some manual labor is fine for the seasoned mages we still have
with us.