Hello, on Samstag, 2. April 2011, Greg KH wrote:
On Sat, Apr 02, 2011 at 01:03:24PM +0530, Anil Seth wrote:
Currently, a new package in tumbleweed is not automatically picked up;
What do you mean by this?
I guess Anil meant zypper up doesn't offer new tumbleweed packages, which is IMHO confirmed with mentioning zypper dup in the next sentence.
at least I could not find out how to do so. It would be desirable not to have to use 'dup' option after the initial conversion.
You don't, unless new packages are added. That's just the way zypper works.
zypper up doesn't do automatic vendor changes. However, my understanding of tumbleweed is that new packages are constantly added. Doesn't fit too good, right? ;-) zypper dup ignores the vendor change and therefore also picks new packages in tumbleweed - but unfortunately you might also get some "accidential" vendor changes if you are using additional repos. The good news is that there's a way to allow specific vendor changes with zypper up (zypper handles them as being the same vendor). Credits go to the Evergreen team, they recommend this way on http://en.opensuse.org/Evergreen#How_to_activate In short, create a file /etc/zypp/vendors.d/evergreen with the following two lines: [main] vendors = openSUSE Evergreen,suse,opensuse If you replace "openSUSE Evergreen" with tumbleweed (use the exact Vendor: tag!), zypper should pick up new tumbleweed packages when running zypper up. Regards, Christian Boltz -- wer Windows in irgendeiner Form verwendet (ausser als abschreckendes Beispiel) ist selbst schuld. [Carsten Becher in suse-linux] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org