[opensuse-factory] upGrading upcoming releases
Hi, As we're getting close to the feature freeze, maybe we should finally think about the statements below, what do you think about it? *---------------------------------------- Maybe I'm on the wrong place for this, but it might be interesting even here: Let's assume the following (I think a not so uncommon scenario): - A user installs a openSuSE Version 10.1 - He changes the installation repositories to something like ftp://mirror.suse.de/pub/SL-Stable/inst-source and adds also ftp://mirror.suse.de/pub/SL-Stable/non-oss-inst-source Now come's one of the trickier parts: The upudate repo is pointing to: ftp://mirror.suse.de/update/10.1 What will happen when openSUSE 10.2 get's the 'stable' Distribution an dwill thus be linked in place of 10.1? ZMD will most probably install many packages from 10.2 (maybe even wished by the user) but the link to the update repo will still point to 10.1. The same problem is with MOST external repos, as most of them also contain the version number in the path. Could there something be implemented to have it point to a URL like: ftp://mirror.suse.de/update /%OSS-VERSION%, thus updating the links upon a relink of the stable tree? The same would be great for external repos of course. Regards, Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Sep 18, 2006 at 04:54:43PM +0200, Dominique Leuenberger wrote:
Hi,
As we're getting close to the feature freeze, maybe we should finally think about the statements below, what do you think about it?
*---------------------------------------- Maybe I'm on the wrong place for this, but it might be interesting even here:
Let's assume the following (I think a not so uncommon scenario): - A user installs a openSuSE Version 10.1 - He changes the installation repositories to something like ftp://mirror.suse.de/pub/SL-Stable/inst-source and adds also ftp://mirror.suse.de/pub/SL-Stable/non-oss-inst-source
Now come's one of the trickier parts: The upudate repo is pointing to: ftp://mirror.suse.de/update/10.1
What will happen when openSUSE 10.2 get's the 'stable' Distribution an dwill thus be linked in place of 10.1?
ZMD will most probably install many packages from 10.2 (maybe even wished by the user) but the link to the update repo will still point to 10.1.
You should _never_ use those symbolic links for your installation sources but always use the version number in an explicit way. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."
"Dominique Leuenberger" <Dominique.Leuenberger@TMF-Group.com> writes:
Hi,
As we're getting close to the feature freeze, maybe we should finally think about the statements below, what do you think about it?
*---------------------------------------- Maybe I'm on the wrong place for this, but it might be interesting even here:
Let's assume the following (I think a not so uncommon scenario): - A user installs a openSuSE Version 10.1 - He changes the installation repositories to something like ftp://mirror.suse.de/pub/SL-Stable/inst-source and adds also ftp://mirror.suse.de/pub/SL-Stable/non-oss-inst-source
Now come's one of the trickier parts: The upudate repo is pointing to: ftp://mirror.suse.de/update/10.1
What will happen when openSUSE 10.2 get's the 'stable' Distribution an dwill thus be linked in place of 10.1?
Good question - Stano, have we taken care of this already?
ZMD will most probably install many packages from 10.2 (maybe even wished by the user) but the link to the update repo will still point to 10.1. The same problem is with MOST external repos, as most of them also contain the version number in the path.
Could there something be implemented to have it point to a URL like: ftp://mirror.suse.de/update /%OSS-VERSION%, thus updating the links upon a relink of the stable tree? The same would be great for external repos of course.
Sounds usefull, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Mon, Sep 18, 2006 at 05:25:03PM +0200, Andreas Jaeger wrote:
"Dominique Leuenberger" <Dominique.Leuenberger@TMF-Group.com> writes:
Hi,
As we're getting close to the feature freeze, maybe we should finally think about the statements below, what do you think about it?
*---------------------------------------- Maybe I'm on the wrong place for this, but it might be interesting even here:
Let's assume the following (I think a not so uncommon scenario): - A user installs a openSuSE Version 10.1 - He changes the installation repositories to something like ftp://mirror.suse.de/pub/SL-Stable/inst-source and adds also ftp://mirror.suse.de/pub/SL-Stable/non-oss-inst-source
Now come's one of the trickier parts: The upudate repo is pointing to: ftp://mirror.suse.de/update/10.1
What will happen when openSUSE 10.2 get's the 'stable' Distribution an dwill thus be linked in place of 10.1?
Good question - Stano, have we taken care of this already?
You expect an automatically triggered upgrade to a new major distribution version to work in a reliable way? If not then this use case is pointless anyway. If someone manages to kill his system that way it does not really matter afterwards whether the dead system has an online update path for the old or for the new distribution version.
Could there something be implemented to have it point to a URL like: ftp://mirror.suse.de/update /%OSS-VERSION%, thus updating the links upon a relink of the stable tree? The same would be great for external repos of course.
Sounds usefull,
As long as there is no reliable way to upgrade distribution versions with zmd I can't see that. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."
* Andreas Jaeger <aj@suse.de> [Sep 18. 2006 17:25]:
Now come's one of the trickier parts: The upudate repo is pointing to: ftp://mirror.suse.de/update/10.1
What will happen when openSUSE 10.2 get's the 'stable' Distribution an dwill thus be linked in place of 10.1?
Good question - Stano, have we taken care of this already?
No, we don't. The normal online update is for continuous updates of your _current_ system. If you want to upgrade to the next release, you must boot from CD1 and select 'upgrade distribution'. This will disable all current repos and register the new update repo. We _might_ publish an optional 'upgrade patch' on 10.1 which disables the update/10.1 repo and adds an update/10.2 repo. Selecting this patch will then switch you to the new repo. Klaus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi, On Tue, 19 Sep 2006, Klaus Kaempf wrote:
* Andreas Jaeger <aj@suse.de> [Sep 18. 2006 17:25]:
Now come's one of the trickier parts: The upudate repo is pointing to: ftp://mirror.suse.de/update/10.1
What will happen when openSUSE 10.2 get's the 'stable' Distribution an dwill thus be linked in place of 10.1?
Good question - Stano, have we taken care of this already?
No, we don't. The normal online update is for continuous updates of your _current_ system.
... but /pub/suse/update/10.1.42/ already exists (for 3 months now), with an empty rpm directory and a "formally filled" repodata directory: 138 2006-06-13 13:32 filelists.xml.gz 134 2006-06-13 13:32 other.xml.gz 116 2006-06-13 13:32 patches.xml 170 2006-06-13 13:32 primary.xml.gz 1231 2006-06-13 13:32 repomd.xml 189 2006-08-21 12:17 repomd.xml.asc 9055 2006-08-21 12:18 repomd.xml.key
If you want to upgrade to the next release, you must boot from CD1 and select 'upgrade distribution'. This will disable all current repos and register the new update repo.
Usually durinf the alpha/beta stage it is sufficient to select 'upgrade distribution' from within, without booting.
We _might_ publish an optional 'upgrade patch' on 10.1 which disables the update/10.1 repo and adds an update/10.2 repo. Selecting this patch will then switch you to the new repo.
Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, Sep 19, 2006 at 09:54:47AM +0200, Eberhard Moenkeberg wrote:
Hi,
On Tue, 19 Sep 2006, Klaus Kaempf wrote:
No, we don't. The normal online update is for continuous updates of your _current_ system.
... but /pub/suse/update/10.1.42/ already exists (for 3 months now), with an empty rpm directory and a "formally filled" repodata directory:
138 2006-06-13 13:32 filelists.xml.gz 134 2006-06-13 13:32 other.xml.gz 116 2006-06-13 13:32 patches.xml 170 2006-06-13 13:32 primary.xml.gz 1231 2006-06-13 13:32 repomd.xml 189 2006-08-21 12:17 repomd.xml.asc 9055 2006-08-21 12:18 repomd.xml.key
So what? I can't see what you want to say with that.
If you want to upgrade to the next release, you must boot from CD1 and select 'upgrade distribution'. This will disable all current repos and register the new update repo.
Usually durinf the alpha/beta stage it is sufficient to select 'upgrade distribution' from within, without booting.
Sure, but this is still more controlled than just registering a symbolic link as an installation repository for zmd so that zmd starts to automatically upgrade your distribution whenever your favourite mirror admin changes a link on the server. This could hurt you in a really bad way when you are not prepared. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."
Dňa Ut 19. September 2006 09:54 Eberhard Moenkeberg napísal:
Hi,
On Tue, 19 Sep 2006, Klaus Kaempf wrote:
* Andreas Jaeger <aj@suse.de> [Sep 18. 2006 17:25]:
Now come's one of the trickier parts: The upudate repo is pointing to: ftp://mirror.suse.de/update/10.1
What will happen when openSUSE 10.2 get's the 'stable' Distribution an dwill thus be linked in place of 10.1?
Good question - Stano, have we taken care of this already?
No, we don't. The normal online update is for continuous updates of your _current_ system.
... but /pub/suse/update/10.1.42/ already exists (for 3 months now), with an empty rpm directory and a "formally filled" repodata directory:
138 2006-06-13 13:32 filelists.xml.gz 134 2006-06-13 13:32 other.xml.gz 116 2006-06-13 13:32 patches.xml 170 2006-06-13 13:32 primary.xml.gz 1231 2006-06-13 13:32 repomd.xml 189 2006-08-21 12:17 repomd.xml.asc 9055 2006-08-21 12:18 repomd.xml.key
If you want to upgrade to the next release, you must boot from CD1 and select 'upgrade distribution'. This will disable all current repos and register the new update repo.
Usually durinf the alpha/beta stage it is sufficient to select 'upgrade distribution' from within, without booting.
Not really. It should be OK after beta1, when we are in the feature freeze, but until then, it might strike back badly and it will cost quite some effort to find out the root of the problem. Stano --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Usually durinf the alpha/beta stage it is sufficient to select 'upgrade distribution' from within, without booting.
Not really. It should be OK after beta1, when we are in the feature freeze, but until then, it might strike back badly and it will cost quite some effort to find out the root of the problem.
Stano
Do I have to file a bugreport that since 10.1 the upgrader will always complain about "a different version, own risk?" If there is a new version, just install fresh. Then you can check the installer for (translation)bugs to :P Azerion --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (7)
-
Andreas Jaeger -
Azerion -
Dominique Leuenberger -
Eberhard Moenkeberg -
Klaus Kaempf -
Robert Schiele -
Stanislav Visnovsky