On Tue, Sep 11, 2012 at 04:13:00PM +0200, Lars Marowsky-Bree wrote:
On 2012-09-07T10:09:52, Greg KH <gregkh@linux.com> wrote:
We've had that discussion before, haven't we? ;-)
Yes, and as before, I don't want to keep any other Tumbleweed repo than the current one.
That's why I recommend using the "current" symlinks for zypper as well, that way everything upgrades together all correctly.
I'm doing that. And am now on adequate bandwidth to go ahead ;-)
But it'd be nice if there was a Tumbleweed current link (perhaps the one without a version number?) pointing to the versioned repository, so that the last state can, if needed, be restored.
Given the way that obs is set up, I don't know how we could do that, unless I start versioning the main Tumbleweed repo itself (12.1, 12.2, etc.) And I really don't want to do that for the reasons given a while ago (people will start to want to stay on older versions, duplicated work on my end, etc.)
I really value the effort you put into tumbleweed; I'm not actually asking you to do more work, just keep the work of the past around as fall-back if something goes wrong or someone needs to take a look at the legacy Tumbleweed N-1 state for a migration period for whatever reason.
I understand the reluctance here, and look forward to the topic coming up evern 8 months or so :) thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org