[opensuse-factory] Tumbleweed: /etc/zypp/vendors.d/tumbleweed
On Sun, Apr 3, 2011 at 2:09 AM, Anil Seth
Hi,
Thanks very much.
On 3 April 2011 03:53, Christian Boltz
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. 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. ==> details It's been working good for Evergreen as far as I know. (I'm on the Evergreen list.) Based on the Evergreen wiki page, the Tumbleweed wiki page would just get the below update: (Hopefully without the "obs://build.opensuse.org/openSUSE:" part. ====== create a file /etc/zypp/vendors.d/tumbleweed with the following content [main] vendors = obs://build.opensuse.org/openSUSE:Tumbleweed,suse,opensuse You can do this from the command line by cutting and pasting the below. You will need to enter the root password for sudo to complete. cat > /tmp/tmp.tumbleweed << EOF [main] vendors = obs://build.opensuse.org/openSUSE:Tumbleweed,suse,opensuse EOF sudo mkdir /etc/zypp/vendors.d sudo cp /tmp/tmp.tumbleweed /etc/zypp/vendors.d/tumbleweed Afterward you should get available updates when you use sudo zypper up. ====== Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 04/15/2011 05:15 PM, Greg Freemyer wrote:
On Sun, Apr 3, 2011 at 2:09 AM, Anil Seth
wrote: Hi,
Thanks very much.
On 3 April 2011 03:53, Christian Boltz
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@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
<snip>
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.
remember for tumbleweed it's not just the "first" time you have to dup. Because it is continuously adding packages, it's basically everytime. And because dup is so powerful, I always use the "--from tumbleweed" option. IF the policies and version conflicts allow for the vendor change to be recommended for tumbleweed users in general, I think there is a net benefit to the tumbleweed project. But I don't know the answer to the IF part of the logic. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
And because dup is so powerful, I always use the "--from tumbleweed"
On 04/18/2011 03:24 PM, Greg Freemyer wrote: option.
IF the policies and version conflicts allow for the vendor change to be recommended for tumbleweed users in general, I think there is a net benefit to the tumbleweed project.
But I don't know the answer to the IF part of the logic.
Greg
When I mentioned policies I meant the project policies, and not the local system policies. If Tumbleweed allows for package renames, etc, which happen when you upgrade KDE's, Gnome's major versions, then no matter if you have a equivalent vendor local policy, zypper up will not suggest to uninstall a package to make place for a conflicting one: you still need dup. -- 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@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Apr 18, 2011 at 01:28:47PM +0200, Duncan Mac-Vicar P. wrote:
On 04/18/2011 03:24 PM, Greg Freemyer wrote:
And because dup is so powerful, I always use the "--from tumbleweed" option.
IF the policies and version conflicts allow for the vendor change to be recommended for tumbleweed users in general, I think there is a net benefit to the tumbleweed project.
But I don't know the answer to the IF part of the logic.
Greg
When I mentioned policies I meant the project policies, and not the local system policies.
If Tumbleweed allows for package renames, etc, which happen when you upgrade KDE's, Gnome's major versions, then no matter if you have a equivalent vendor local policy, zypper up will not suggest to uninstall a package to make place for a conflicting one: you still need dup.
Yes, that's why I always say you need to use 'zypper dup' when using tumbleweed. And I'm a bit leary of adding Tumbleweed to the zypper vendors list. I like to know what packages are changing to be managed under Tumbleweed. So if you want, you can do so, but it's not something that I feel is for everyone. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Duncan Mac-Vicar P.
-
Greg Freemyer
-
Greg KH