Re: usrmerge -- plan B?
- Date: Fri, 23 Nov 2018 09:26:59 -0700
- From: Daniele Nicolodi <daniele@xxxxxxxxxx>
- Subject: Re: usrmerge -- plan B?
On 23/11/2018 08:19, Adam Borowski wrote:
> On Fri, Nov 23, 2018 at 03:14:44PM +0100, Matthias Klumpp wrote:
>> Am Fr., 23. Nov. 2018 um 14:47 Uhr schrieb Stephan Seitz
>>> On Fr, Nov 23, 2018 at 02:04:05 +0100, Matthias Klumpp wrote:
>>>> If there are actual issues encountered, we can always revert a change
>>> And how do you revert this change? As far as I have understand you can’t
>>> remove the usrmerge package and have your system in the old state again.
>> You don't - it's unstable, for testing these things. If it breaks, you
>> file a bug and fix the system.
> Fix -- not completely restore from backups. This is not an option with
> usrmerge; we have severity:critical for bugs with such a fallout.
I've seen this repeated multiple times in this thread, where does your
assessment that the usrmerge package can leave the system in a non
working state comes from?
In my experience, usrmerge stops the merge if it encounters some
unforeseen difficulty and hints to how to resolve the problem. Once the
problem has been resolved, usrmerge can be run again and it will pick up
from where it left.
Is your experience different? Can you be more precise on the kind of
errors or system breakage you encountered?