On 08/05/2015 01:39 PM, Takashi Iwai wrote:
On Wed, 2015-08-05 at 12:07 +0200, Jan Engelhardt wrote:
Why is everybody expecting 0 breakage at 0 work investment? TW must have looked differently to people when Greg ran the process. I somehow share that feeling, given the Greg-TW seemed hand-picked, and included reverts. The current TW on the other hand seems just like Factory with a bit of OpenQA
On Wednesday 2015-08-05 11:59, Dimstar / Dominique Leuenberger wrote: thrown in, and you won't see any reverts in the automated Nussel mails. Then you did not follow all the 'Nussel mails' close enough... I assure you: there have been reverts (most of the time though before a snapshot goes out, as most such reverts are spotted to be needed during the openQA phase... but reverts DO happen) I wonder whether we may have a proper way to revert the package installation locally for TW. We get usually multiple package updates in a shot. And if a breakage happens, usually this is only about a single or a part of the updated packages. An easy fix is to revert
On Wed, 05 Aug 2015 12:10:35 +0200, Dimstar / Dominique Leuenberger wrote: the affected package. But how? The previous packages are gone on TW.
The best would be to keep the old packages in our repo. Would it become too much in the end as we can't afford?
Another idea is to have backup locally: for example, make zypper keeping the old packages (as rpm) on disk for one or two versions back. Does it sound feasible?
................ { always expecting that mr jan will shout at me for something or other } one might use : Konsole output #yast2 clone_system and then save specific-dated versions of output in /root directory , of the file , such as : Konsole output #autoinst.xml autoinst_072715.xml autoinst_080515.xml .......... regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org