Hi Andrei, Am 22.11.2014 um 06:19 schrieb Andrei Borzenkov:
[moving to factory]
В Fri, 21 Nov 2014 19:13:08 -0500 Greg Freemyer <greg.freemyer@gmail.com> пишет:
On Fri, Nov 21, 2014 at 9:41 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On Fri, Nov 21, 2014 at 5:23 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
Before everyone puts arrows in you, tumbleweed mandates zypper dup be used.
Yes, it was true in the past because new TW version was based on different repository so you could not expect that it had higher RPM versions. Now, when we expect TW to stick to the same repo forever, this reason no more exists.
But "factory" has been using "zypper dup" for years as far as I know.
Surely the new tumbleweed requires it just as factory has.
Oh, new can of worms ...
If this is true and new rolling release model mandates zypper dup as standard way to update, this is even worse problem for most users than closed source drivers. Even I managed to collect dozen of various repositories from which I need just a couple of packages each. If every time I update I must play "random repo of the day" game I will never switch to factory.
I was under impression, that rolling release implies "zypper up". Am I wrong?
If you know what you are doing (and I have reasons to believe you do...), then "zypper up" will work just fine. I have the following setup since years: seife@susi:~> zypper lr # | Alias | Name | Enabled | Refresh ---+--------------------+--------------------+---------+-------- 1 | KOTD | KOTD | Yes | Yes 2 | cross-avr | cross-avr | Yes | Yes 3 | factory-debug | factory-debug | Yes | No 4 | factory-non-oss | factory-non-oss | Yes | Yes 5 | factory-oss | factory-oss | Yes | Yes 6 | home:seife:testing | home:seife:testing | Yes | Yes 7 | home:seife:vdrdev | home:seife:vdrdev | Yes | Yes 8 | libdvdcss | libdvdcss | Yes | No 9 | packman | packman | Yes | Yes 10 | repo-update | repo-update | No | Yes I played with the repo priorities and have packman with prio 100 and cross-avr with prio 101 I deliberately do not use "dup" for the following reasons: * kernel-default is from factory-oss * kenrel-desktop is from KOTD => if kernel-desktop-KOTD fails, I still have working kernel-default * I only installed selected stuff from packman. zypper dup would either bring too much stuff from packman which it provides for unknown reasons and which also is in factory (if it had the same priority 99 as the others) or nothing at all (prio 100) Now since "zypper up" does not do vendor changes, this all works out nicely. The downside is, that sometimes I have to manually check for "orphaned" packages and sometimes I have to find out why the update is not willing to update anything even though lots of new packages are available (usually because something requiring a downgrade or vendor change is blocking the update). But in general, this works out nicely without problems. Try it and have fun :-) seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org