[opensuse-factory] Tumbleweed really needed for rolling release?
I see the repos named "current" are just a link to the current available openSUSE release. Let´s assume I install openSUSE 12.3 and after installation I change the 12.3 repos to "current", won´t I get a rolling release this way? I mean, once e.g. 13.1 is out, it will be put in "current" and thus I get the whole distribution updated? So I would have a rolling release without adding the Tumbleweed repo? Is this thought correct? Just change the repos to "current" and you automatically get the lates distribution on your harddrive? Malte -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Jun 4, 2013 at 3:38 AM, Malte Gell <malte.gell@gmail.com> wrote:
I see the repos named "current" are just a link to the current available openSUSE release. Let´s assume I install openSUSE 12.3 and after installation I change the 12.3 repos to "current", won´t I get a rolling release this way?
I mean, once e.g. 13.1 is out, it will be put in "current" and thus I get the whole distribution updated? So I would have a rolling release without adding the Tumbleweed repo? Is this thought correct? Just change the repos to "current" and you automatically get the lates distribution on your harddrive?
It may depend on what you mean by "rolling release", but what you describe would work and a simple zypper up shortly after each release would update you from release to release. But during the 8 months between releases you would see very little in the way of major feature updates. Here's the list of packages you get in tumbleweed right now, but older releases are in 12.3 https://build.opensuse.org/project/show?project=openSUSE%3ATumbleweed http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/x86_... Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-06-04 at 09:38 +0200, Malte Gell wrote:
I see the repos named "current" are just a link to the current available openSUSE release. Let´s assume I install openSUSE 12.3 and after installation I change the 12.3 repos to "current", won´t I get a rolling release this way?
Kiind of, but a rolling release that only gets updated once every 8 months. Not what is normally understood.
I mean, once e.g. 13.1 is out, it will be put in "current" and thus I get the whole distribution updated?
Not automatically. Even a "zypper up" would not suffice, you'd need a dup. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGucdQACgkQtTMYHG2NR9XVOACdHohwiKpJfdd3Wmd+FQqK/Jup GiQAn1RKfuJz7Cp27xcn+kJtmm+TpzUC =vaiz -----END PGP SIGNATURE-----
On Tue, Jun 4, 2013 at 7:01 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
I mean, once e.g. 13.1 is out, it will be put in "current" and thus I get the whole distribution updated?
Not automatically. Even a "zypper up" would not suffice, you'd need a dup.
Are you sure? The official repo's all have the same publisher I think so they are considered one big family and zypper up should have no issues with it being a change of repo. Tumbleweed is a different publisher, so it requires a zyppper dup. I tried setting Tumbleweed the same as the main repos once. zypper up would then do the job, but there were issues with that I don't recall, so I put it back the way it was. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2013-06-04 at 19:09 -0400, Greg Freemyer wrote:
On Tue, Jun 4, 2013 at 7:01 PM, Carlos E. R. <> wrote:
I mean, once e.g. 13.1 is out, it will be put in "current" and thus I get the whole distribution updated?
Not automatically. Even a "zypper up" would not suffice, you'd need a dup.
Are you sure?
Absolutely. You are upgrading the distribution, so you need to use dup. Same as if you intentionally upgrade from 12.1 to 12.2. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGulTgACgkQtTMYHG2NR9U4hwCdE2HMSvP1mYuNLOM+UsknfYVA aeMAn099/dWFh1weFOpQ+fkBaIFLh72d =Wxe4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Wed, 5 Jun 2013 03:32:40 +0200 (CEST) "Carlos E. R." <robin.listas@telefonica.net> пишет:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday, 2013-06-04 at 19:09 -0400, Greg Freemyer wrote:
On Tue, Jun 4, 2013 at 7:01 PM, Carlos E. R. <> wrote:
I mean, once e.g. 13.1 is out, it will be put in "current" and thus I get the whole distribution updated?
Not automatically. Even a "zypper up" would not suffice, you'd need a dup.
Are you sure?
Absolutely.
You are upgrading the distribution, so you need to use dup.
What is the difference between up and dup besides allowing to change package provider and allowing to downgrade packages? Does dup run some extra pre/post scripts or performs some actions beyond package installation? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlGupMkACgkQR6LMutpd94yN1QCgpopmABTmvHHtNmmhAqtln1kA LC0Anj/ZbqwwbzuGlxebtBMz+kyuJlhu =o95N -----END PGP SIGNATURE----- N▀╖╡ФЛr╦⌡yИ ┼Z)z{.╠Гзrз+кК╖╡ФЛr╦⌡z┼^·к╛z┼ЮN┤(·ж°╤ь^ё ч╜И ┼Z)z{.╠Гзrз+кЙ0²ЙХ╔ИЛ╨г╗╝
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2013-06-05 at 06:39 +0400, Andrey Borzenkov wrote:
В Wed, 5 Jun 2013 03:32:40 +0200 (CEST) "Carlos E. R." <> пишет:
You are upgrading the distribution, so you need to use dup.
What is the difference between up and dup besides allowing to change package provider and allowing to downgrade packages? Does dup run some extra pre/post scripts or performs some actions beyond package installation?
That I do not know, but it might. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGuqk4ACgkQtTMYHG2NR9XJQgCfdwso2cxg3Rx1ne3KOmSQwLYE dK8An0pAjtcdcDAoYmg1LRBfQvxSgll7 =BTzx -----END PGP SIGNATURE-----
On 06/04/2013 11:02 PM, Carlos E. R. pecked at the keyboard and wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday, 2013-06-05 at 06:39 +0400, Andrey Borzenkov wrote:
В Wed, 5 Jun 2013 03:32:40 +0200 (CEST) "Carlos E. R." <> пишет:
You are upgrading the distribution, so you need to use dup.
What is the difference between up and dup besides allowing to change package provider and allowing to downgrade packages? Does dup run some extra pre/post scripts or performs some actions beyond package installation?
That I do not know, but it might.
Keep in mind here that to the user there is no repo change just newer packages showing up in the same repo so zypper up should work. The only change is to the internal links that the path points to. Just my viewpoint. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-05 05:16, Ken Schneider - openSUSE wrote:
Keep in mind here that to the user there is no repo change just newer packages showing up in the same repo so zypper up should work. The only change is to the internal links that the path points to. Just my viewpoint.
Not enough. At one point the link is moved to a totally different repo. There are new packages that should be installed, and packages that disappear and have to be removed. Packages that are replaced with other packages. Packages that go backwards in versions. All that, a "zypper dup" is designed to take care off. A "zypper up" is not. What a dup does, basically, is replicate the repo on your computer, not just update... Not exactly that, but closer than "update". - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlGusDwACgkQIvFNjefEBxogrACfbLXZF7jqNp0Qjdo47/BGVp2v jukAn1kCoLTgQYL/7v8Vzi/xy42j+J2x =d66U -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 05.06.2013 01:01, schrieb Carlos E. R.:
On Tuesday, 2013-06-04 at 09:38 +0200, Malte Gell wrote:
I see the repos named "current" are just a link to the current available openSUSE release. Let´s assume I install openSUSE 12.3 and after installation I change the 12.3 repos to "current", won´t I get a rolling release this way?
Kiind of, but a rolling release that only gets updated once every 8 months. Not what is normally understood.
Ok, I see. It would not be a rolling release, but would install the current stable distribution. Just the Tumbleweed repo adds rolling release software. But, it would be a way to update the distribution, to change e.g. the 12.3 repos to "current", once 13.1 is out? This way you can update the whole distribution to the current version? Thanx Malte
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-05 08:37, Malte Gell wrote:
Am 05.06.2013 01:01, schrieb Carlos E. R.:
On Tuesday, 2013-06-04 at 09:38 +0200, Malte Gell wrote:
I see the repos named "current" are just a link to the current available openSUSE release. Let´s assume I install openSUSE 12.3 and after installation I change the 12.3 repos to "current", won´t I get a rolling release this way?
Kiind of, but a rolling release that only gets updated once every 8 months. Not what is normally understood.
Ok, I see. It would not be a rolling release, but would install the current stable distribution. Just the Tumbleweed repo adds rolling release software.
Yep.
But, it would be a way to update the distribution, to change e.g. the 12.3 repos to "current", once 13.1 is out? This way you can update the whole distribution to the current version?
But why? You loose the advantages of either method. You neither have a rolling release with the most recent software, neither a stable one (because the stable release is not really stable till about a month after release). You don't choose the day of upgrade, they do. And that day you have to do a 'dup', not an 'up', or you don't do it fully... Better keep track of dates, and zypper dup it the day you choose, when you can spare a few hours, not forgetting to do a backup first. No nasty surprises, thankyou ;-) - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlGvCegACgkQIvFNjefEBxq1QwCdG1vQkAKaQMH5cD/bsiLzuYKh liUAnio0KXC1nb6FgxFYMCXL33Aw3TYI =sS3u -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Andrey Borzenkov -
Carlos E. R. -
Greg Freemyer -
Ken Schneider - openSUSE -
Malte Gell