Mailinglist Archive: opensuse-factory (379 mails)

["Duncan Mac-Vicar P." <dmacvicar@xxxxxxx>]

On 04/15/2011 05:15 PM, Greg Freemyer wrote:
> On Sun, Apr 3, 2011 at 2:09 AM, Anil Seth<seth.anil@xxxxxxxxx>  wrote:
> > Hi,
> >
> > Thanks very much.
> >
> > On 3 April 2011 03:53, Christian Boltz<opensuse@xxxxxxxxx>  wrote:
> > > 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.
> >
> > I hope I got the vendor tag right - obs://build.opensuse.org/openSUSE:Tumbleweed
> >
> > I will wait for additional packages in Tumbleweed to be sure that I
> > got it right.
> >
> > Regards
> > Anil
>
> So is the above going to be Tumbleweed standard practice?
>
> ie. update user's machine config to allow "zypper up" to update from
> OSS to Tumbleweed packages without making a big deal of it to the
> user.
>
> If so, I can update the wiki page, but it would be nice to get a
> better repo designator for Tumbleweed than the current one.
>
> I believe it's currently:
>      obs://build.opensuse.org/openSUSE:Tumbleweed
> The Evergreen project has it as just Evergreen without the prefix.
>
> But a big negative is that it also means packages can be "upgraded"
> from tumbleweed to a online update without the user being notified
> that something unusual is happening.

Well, changing your package vendor is something unusual :-)

> In particular, a issue like the virtual-box one where the online
> update had a larger version number than the one in tumbleweed would
> cause problems / failures without even asking the user if it was okay.
>
> It's not clear to me if the version number conflict issue was resolved
> or not.  If resolved, I like the "zypper up" approach instead of the
> "zypper dup --from Tumbleweed" approach.

Whether you can replace the (first) dup with an up depends on the 
repository policies and what is allowed to be done there.

That would not work for some KDE updates for example.

--
Duncan Mac-Vicar P. - Novell® Making IT Work As One™
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)

--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx