Hi,
I'd like to completely rewrite the $SUBJECT in installation and you have an opportunity to say how do you think it could look and what could it offer to do or how.
I've filed a blog entry about the $SUBJECT at http://kobliha-suse.blogspot.com/2009/01/system-ugrade-previously-used.html
Bye Lukas
Lukas Ocilka wrote:
Hi,
I'd like to completely rewrite the $SUBJECT in installation and you have an opportunity to say how do you think it could look and what could it offer to do or how.
I've filed a blog entry about the $SUBJECT at http://kobliha-suse.blogspot.com/2009/01/system-ugrade-previously-used.html
Bye Lukas
A solution worth to explore is to start using variables like $releasever in the .repo files.
So repos with 11.1 would automaitcally be 11.2 afterwards. Of course still there is the need to check that those repos are valid.
Duncan
2009/1/13 Duncan Mac-Vicar Prett dmacvicar@suse.de:
A solution worth to explore is to start using variables like $releasever in the .repo files.
So repos with 11.1 would automaitcally be 11.2 afterwards. Of course still there is the need to check that those repos are valid.
Another possibility would be on upgrade to check for a file in each repository that would provide the URI of the equivalent repository in the new distro version.
This could allow the repository publisher to provide an upgrade path for their repository without being tied to a specific URI format, moving to alternative locations, consolodation of multiple repositories into one and so on.
-- Benjamin Weber
Duncan Mac-Vicar Prett wrote:
A solution worth to explore is to start using variables like $releasever in the .repo files.
So repos with 11.1 would automaitcally be 11.2 afterwards. Of course still there is the need to check that those repos are valid.
Yes, it sounds reasonable for this case. Of course, that would have to be changed on several places (community repositories, one click install files, ... zypper, YaST).
L.
Benji Weber wrote:
2009/1/13 Duncan Mac-Vicar Prett dmacvicar@suse.de:
A solution worth to explore is to start using variables like $releasever in the .repo files.
So repos with 11.1 would automaitcally be 11.2 afterwards. Of course still there is the need to check that those repos are valid.
Another possibility would be on upgrade to check for a file in each repository that would provide the URI of the equivalent repository in the new distro version.
That would require to initialize the repository at first and then download an optional file from there, then delete the repository again and register a new one provided by that file. Which also means we would have to setup the network before all this.
This could allow the repository publisher to provide an upgrade path for their repository without being tied to a specific URI format, moving to alternative locations, consolodation of multiple repositories into one and so on.
Anyway, these ideas could be also used for a running system as well (zypper, YaST repositories, ...).
Lukas
Lukas Ocilka napsal(a):
I'd like to completely rewrite the $SUBJECT in installation and you have an opportunity to say how do you think it could look and what could it offer to do or how.
Ignoring the technical details ;), a cool feature would be detecting and automatically deleting the old distros main and update repository (and non-oss, src, debuginfo, etc), because these are going to be obsoleted by the new distro in all cases. The user would then only need to decide about the repositories which were added manually. BTW I also like Benji's idea of self-upgrading repositories.
Michal
On Wed, Jan 14, 2009 at 9:45 AM, Michal Marek mmarek@suse.cz wrote:
Lukas Ocilka napsal(a):
I'd like to completely rewrite the $SUBJECT in installation and you have an opportunity to say how do you think it could look and what could it offer to do or how.
Ignoring the technical details ;), a cool feature would be detecting and automatically deleting the old distros main and update repository (and non-oss, src, debuginfo, etc), because these are going to be obsoleted by the new distro in all cases. The user would then only need to decide about the repositories which were added manually. BTW I also like Benji's idea of self-upgrading repositories.
Michal
Agreed, it would be nice if each repository had the ability to say
"applies to 10.3-11.1" ie. 10.3,11,0,11.1 "applies to 10.3" ie. 10.3 only "applies to 10.3-" ie. 10.3 or higher "applies to -11.1" ie. 11.1 or lower
And then when one expires, yast would somehow give the user a way to say:
disable, delete, search for newer
Or functionality to that effect.
Greg
On 1/13/2009 at 5:30 PM, Duncan Mac-Vicar Prett dmacvicar@suse.de wrote:
Lukas Ocilka wrote:
Hi,
I'd like to completely rewrite the $SUBJECT in installation and you have an opportunity to say how do you think it could look and what could it offer to do or how.
I've filed a blog entry about the $SUBJECT at http://kobliha-suse.blogspot.com/2009/01/system-ugrade-previously-used.html
Bye Lukas
A solution worth to explore is to start using variables like $releasever in the .repo files.
So repos with 11.1 would automaitcally be 11.2 afterwards. Of course still there is the need to check that those repos are valid.
I remember having this requested once (basically having the openSUSE version as a varibale in the URL). https://bugzilla.novell.com/show_bug.cgi?id=264862
It got 'closed / fixed' for openSUSE 10.3... I never got around to test that though.
Dominique
Am Dienstag, 13. Januar 2009 13:59:17 schrieb Lukas Ocilka:
Hi,
I'd like to completely rewrite the $SUBJECT in installation and you have an opportunity to say how do you think it could look and what could it offer to do or how.
Nice idea,
There is a Yast-Module named Yast2-update-factory,
Why not place a Yast2-update-"current- version"+1 in the Update repo?
Daniel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Maybe I totally misunderstood this, but I understood this blog entry as a feature request. If I'm correct, then this is almost done. Except the automatism it is working already. I used this to upgrade from 10.3 to 11.0. I checked the repos before upgrade and than I changed the repo URIs manually to the new ones and re-enabled those. Then I ran the upgrade process and it did what it had to do.
I have a bug report for this feature (#398315), it is solved in 11.1, but I wasn't be able to test that.
Cheers Tamas
PS: I subscribed to yast-devel list just now, so I haven't read the replies there.
Lukas Ocilka wrote:
Hi,
I'd like to completely rewrite the $SUBJECT in installation and you have an opportunity to say how do you think it could look and what could it offer to do or how.
I've filed a blog entry about the $SUBJECT at http://kobliha-suse.blogspot.com/2009/01/system-ugrade-previously-used.html
Bye Lukas
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I'm very sorry to send it again, but I forgot about the confirmation of my subscription to the yast-devel list, so it wasn't sent there. Sorry again.
Hi,
Maybe I totally misunderstood this, but I understood this blog entry as a feature request. If I'm correct, then this is almost done. Except the automatism it is working already. I used this to upgrade from 10.3 to 11.0. I checked the repos before upgrade and than I changed the repo URIs manually to the new ones and re-enabled those. Then I ran the upgrade process and it did what it had to do.
I have a bug report for this feature (#398315), it is solved in 11.1, but I wasn't be able to test that.
Cheers Tamas
PS: I subscribed to yast-devel list just now, so I haven't read the replies there.
Lukas Ocilka wrote:
Hi,
I'd like to completely rewrite the $SUBJECT in installation and you have an opportunity to say how do you think it could look and what could it offer to do or how.
I've filed a blog entry about the $SUBJECT at http://kobliha-suse.blogspot.com/2009/01/system-ugrade-previously-used.html
Bye Lukas
Greg Freemyer napsal(a):
On Wed, Jan 14, 2009 at 9:45 AM, Michal Marek mmarek@suse.cz wrote:
Lukas Ocilka napsal(a):
I'd like to completely rewrite the $SUBJECT in installation and you have an opportunity to say how do you think it could look and what could it offer to do or how.
Ignoring the technical details ;), a cool feature would be detecting and automatically deleting the old distros main and update repository (and non-oss, src, debuginfo, etc), because these are going to be obsoleted by the new distro in all cases. The user would then only need to decide about the repositories which were added manually. BTW I also like Benji's idea of self-upgrading repositories.
Michal
Agreed, it would be nice if each repository had the ability to say
"applies to 10.3-11.1" ie. 10.3,11,0,11.1 "applies to 10.3" ie. 10.3 only "applies to 10.3-" ie. 10.3 or higher "applies to -11.1" ie. 11.1 or lower
That's not what I had in mind (repositories usually only apply to one version of the distribution). My suggestion was: If you are updating from 11.1 to 11.2, then these repositories
http://download.opensuse.org/distribution/11.1/repo/oss/ http://download.opensuse.org/distribution/11.1/repo/non-oss/ http://download.opensuse.org/update/11.1/ http://download.opensuse.org/debug/distribution/11.1/repo/oss/ http://download.opensuse.org/source/distribution/11.1/repo/oss/
should be deleted automatically, because the installation of 11.2 will add it's own oss, non-oss, update and so on repos. Maybe repositories could obsolete other repositories just like packages obsolete other packages.
BTW: Lukas, why do you cross-post to opensuse-factory and yast-devel, when both lists reject posts from non-subscribers?
Michal
-
Benji Weber -
Daniel Fuhrmann -
Dominique Leuenberger -
Duncan Mac-Vicar Prett -
Greg Freemyer -
Lukas Ocilka -
Michal Marek -
Tamas Sarga