I've added the build service samba repo to my config, and of course it doesn't show any updates when executing 'zypper lu', because it's not the same vendor as the base system.. Running 'zypper lu -a' shows them.. So, I looked at some options, and I should be able to add valid vendors to a file in /etc/zypp/vendors.d that is supposed to validate them to zypper. If I'm not mistaken.. Looking at 'zypper if samba' gives that 'Vendor: openSUSE Build Service' which isn't surprising, so I made a file in /etc/zypp/vendors.d that has this in it: [main] vendors = opensuse,open,suse But zypper still won't show samba updates as valid... Am I doing things wrong, or do I have to make a manual update to get the vendor change in place? Anders. (-16.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Feb 13, 2009 at 09:13:17AM +0100, Anders Norrbring wrote:
I've added the build service samba repo to my config, and of course it doesn't show any updates when executing 'zypper lu', because it's not the same vendor as the base system..
Please modify the priority of the samba repo you added.[1] Yes, this needs documentation at http://en.openSUSE.org/Samba or better in general. [1] I expect there is a Samba from the openSUSE 11.1 update channel which is preferred. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Fri, Feb 13, 2009 at 09:13:17AM +0100, Anders Norrbring wrote:
I've added the build service samba repo to my config, and of course it doesn't show any updates when executing 'zypper lu', because it's not the same vendor as the base system..
Please modify the priority of the samba repo you added.[1]
Yes, this needs documentation at http://en.openSUSE.org/Samba or better in general.
[1] I expect there is a Samba from the openSUSE 11.1 update channel which is preferred.
Lars
Thanks Lars, But what priority do I need to set it to? Currently it's the lowest number in the list.. # | Alias | Name | Enabled | Refresh | Priority | Type --+-----------------------+-----------------------+---------+---------+----------+------- 1 | Samba_Stable_1 | Samba Stable | Yes | Yes | 98 | rpm-md 2 | openSUSE 11.1-0 | openSUSE 11.1-0 | No | No | 99 | yast2 3 | openSUSE-11.1-Updates | openSUSE-11.1-Updates | Yes | Yes | 99 | rpm-md Also, the Samba Stable version usually serves good, and it's more a bit of experiment than a production server.. I normally go with only the distribution and update repos for machines at production level. ;-) Anders. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 14 February 2009 03:07:33 am Anders Norrbring wrote: ...
Please modify the priority of the samba repo you added.[1] ...
Thanks Lars, But what priority do I need to set it to? Currently it's the lowest number in the list.
Lower number -- higher priority. Lower number will put repo higher in the list. Package manager will read the list from top to bottom. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 14 February 2009 03:07:33 am Anders Norrbring wrote: ...
Please modify the priority of the samba repo you added.[1] ...
Thanks Lars, But what priority do I need to set it to? Currently it's the lowest number in the list.
Lower number -- higher priority.
Lower number will put repo higher in the list. Package manager will read the list from top to bottom.
Yes Rajko, I know that.. But the question is more of the nature that how can I make zypper actually USE the repo? After all, I've added to vendors.d/allowed file, the repo has the highest priority, still zypper won't use it to update the system. Anders. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-02-14 at 12:06 +0100, Anders Norrbring wrote:
Lower number -- higher priority.
Lower number will put repo higher in the list. Package manager will read the list from top to bottom.
Yes Rajko, I know that.. But the question is more of the nature that how can I make zypper actually USE the repo? After all, I've added to vendors.d/allowed file, the repo has the highest priority, still zypper won't use it to update the system.
I think that only "update" repo is used to update the system. :-? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmWqVoACgkQtTMYHG2NR9VjrgCeMWjNerNmD/XE9gl5Exdev/3u FwcAnjorL4bFt+PV99MjT2z74d1aAD/0 =eUd2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday, 2009-02-14 at 12:06 +0100, Anders Norrbring wrote:
Lower number -- higher priority.
Lower number will put repo higher in the list. Package manager will read the list from top to bottom.
Yes Rajko, I know that.. But the question is more of the nature that how can I make zypper actually USE the repo? After all, I've added to vendors.d/allowed file, the repo has the highest priority, still zypper won't use it to update the system.
I think that only "update" repo is used to update the system. :-?
- -- Cheers, Carlos E. R.
If so, that must be completely new from 11.1... I've used all kinds of repos before, and if there's a new version available anywhere, it'll show up when issuing 'zypper lu' or 'zypper lu -t package'. Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-02-14 at 12:28 +0100, Anders Norrbring wrote:
I think that only "update" repo is used to update the system. :-?
If so, that must be completely new from 11.1... I've used all kinds of repos before, and if there's a new version available anywhere, it'll show up when issuing 'zypper lu' or 'zypper lu -t package'.
New? No, zypper up does not update anything in my systems, just security patches, as far as I can see. It ignores the extra kde repos. I thought that was to be expected, I use Yast to update those. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmWt2cACgkQtTMYHG2NR9XXbQCgjSDo8rkw6v5I0zAMiM/Y+wjN oQYAn2L6tusxlUK4ZuuCsjFYyOA0UMxB =+M+0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. pecked at the keyboard and wrote:
On Saturday, 2009-02-14 at 12:28 +0100, Anders Norrbring wrote:
I think that only "update" repo is used to update the system. :-?
If so, that must be completely new from 11.1... I've used all kinds of repos before, and if there's a new version available anywhere, it'll show up when issuing 'zypper lu' or 'zypper lu -t package'.
New? No, zypper up does not update anything in my systems, just security patches, as far as I can see. It ignores the extra kde repos. I thought that was to be expected, I use Yast to update those.
-- Cheers, Carlos E. R.
No it is not new, but you do need to set zypper to update third party repo's when the backend allows (in the settings menu). -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. pecked at the keyboard and wrote:
On Saturday, 2009-02-14 at 12:28 +0100, Anders Norrbring wrote:
I think that only "update" repo is used to update the system. :-?
If so, that must be completely new from 11.1... I've used all kinds
repos before, and if there's a new version available anywhere, it'll show up when issuing 'zypper lu' or 'zypper lu -t package'.
New? No, zypper up does not update anything in my systems, just security patches, as far as I can see. It ignores the extra kde repos. I
of thought
that was to be expected, I use Yast to update those.
-- Cheers, Carlos E. R.
No it is not new, but you do need to set zypper to update third party repo's when the backend allows (in the settings menu).
-- Ken Schneider SuSe since Version 5.2, June 1998
Hmm.. I'm sorry Ken, but I've never seen a menu in zypper? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Norrbring pecked at the keyboard and wrote:
Carlos E. R. pecked at the keyboard and wrote:
On Saturday, 2009-02-14 at 12:28 +0100, Anders Norrbring wrote:
I think that only "update" repo is used to update the system. :-?
If so, that must be completely new from 11.1... I've used all kinds
repos before, and if there's a new version available anywhere, it'll show up when issuing 'zypper lu' or 'zypper lu -t package'. New? No, zypper up does not update anything in my systems, just security patches, as far as I can see. It ignores the extra kde repos. I
of thought
that was to be expected, I use Yast to update those.
-- Cheers, Carlos E. R. No it is not new, but you do need to set zypper to update third party repo's when the backend allows (in the settings menu).
-- Ken Schneider SuSe since Version 5.2, June 1998
Hmm.. I'm sorry Ken, but I've never seen a menu in zypper?
Sorry, it's available in kupdateapplet. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. pecked at the keyboard and wrote:
On Saturday, 2009-02-14 at 12:28 +0100, Anders Norrbring wrote:
I think that only "update" repo is used to update the system. :-?
If so, that must be completely new from 11.1... I've used all
repos before, and if there's a new version available anywhere, it'll show up when issuing 'zypper lu' or 'zypper lu -t package'. New? No, zypper up does not update anything in my systems, just security patches, as far as I can see. It ignores the extra kde repos. I
kinds of thought
that was to be expected, I use Yast to update those.
-- Cheers, Carlos E. R. No it is not new, but you do need to set zypper to update third
Anders Norrbring pecked at the keyboard and wrote: party
repo's when the backend allows (in the settings menu).
-- Ken Schneider SuSe since Version 5.2, June 1998
Hmm.. I'm sorry Ken, but I've never seen a menu in zypper?
Sorry, it's available in kupdateapplet.
-- Ken Schneider SuSe since Version 5.2, June 1998
Ah, that explains.. ;-) I don't have any graphic environment on this box, it's a minimalistic server config. Oh well, I'll keep trying things to see if I can find something out. It sure would be nice with some pointers from somebody that knows the inner workings of the zypp configuration options.. Anders. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, Feb 14, 2009 at 01:21:50PM +0100, Carlos E. R. wrote:
New? No, zypper up does not update anything in my systems, just security patches, as far as I can see. It ignores the extra kde repos. I thought that was to be expected, I use Yast to update those.
The behaviour changed between 11.0 and 11.1. 11.0: zypper up -> install official patches zypper up -t package -> install newest versions (considering vendor and repo priority) 11.1: zypper patch -> install official patches zypper up -> install newest versions Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2009-02-16 at 12:35 +0100, Michael Schroeder wrote:
On Sat, Feb 14, 2009 at 01:21:50PM +0100, Carlos E. R. wrote:
New? No, zypper up does not update anything in my systems, just security patches, as far as I can see. It ignores the extra kde repos. I thought that was to be expected, I use Yast to update those.
The behaviour changed between 11.0 and 11.1.
11.0: zypper up -> install official patches zypper up -t package -> install newest versions (considering vendor and repo priority)
11.1: zypper patch -> install official patches zypper up -> install newest versions
Ah! :-O That does explain some things, yes. And poses new problems! Look: NOT_nimrodel:~ # zypper patch Retrieving repository 'update' metadata [done] Building repository 'update' cache [done] Loading repository data... Reading installed packages... Resolving package dependencies... Problem: evolution-2.24.1.1-4.11.i586 requires mono(Novell.IceDesktop) = 1.0.3259.23515, but this requirement cannot be provided Solution 1: Following actions will be done: deinstallation of evolution-2.24.1.1-4.11.i586 deinstallation of evolution-lang-2.24.1.1-4.11.i586 deinstallation of evolution-pilot-2.24.1.1-4.11.i586 Solution 2: do not install patch:dice-522.noarch Solution 3: Ignore some dependencies of evolution Choose from above solutions by number or cancel [1/2/3/C]: - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmZalwACgkQtTMYHG2NR9WkCwCeKwyOKx/G9L0TNeRdMkqfg2eH d10AnizO1Ll/atNO95EwAvompk2PA+jG =Ay9F -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Feb 16, 2009 at 02:30:00PM +0100, Carlos E. R. wrote:
And poses new problems! Look:
NOT_nimrodel:~ # zypper patch Retrieving repository 'update' metadata [done] Building repository 'update' cache [done] Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: evolution-2.24.1.1-4.11.i586 requires mono(Novell.IceDesktop) = 1.0.3259.23515, but this requirement cannot be provided Solution 1: Following actions will be done: deinstallation of evolution-2.24.1.1-4.11.i586 deinstallation of evolution-lang-2.24.1.1-4.11.i586 deinstallation of evolution-pilot-2.24.1.1-4.11.i586 Solution 2: do not install patch:dice-522.noarch Solution 3: Ignore some dependencies of evolution
Choose from above solutions by number or cancel [1/2/3/C]:
I just asked the maintenance team and they said that the dice update is broken and was just removed from the update channel. It'll get re-released together with an evolution update. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2009-02-16 at 14:43 +0100, Michael Schroeder wrote:
Solution 2: do not install patch:dice-522.noarch Solution 3: Ignore some dependencies of evolution
Choose from above solutions by number or cancel [1/2/3/C]:
I just asked the maintenance team and they said that the dice update is broken and was just removed from the update channel.
It'll get re-released together with an evolution update.
Ah, yes, its changed now: The following packages are going to be upgraded: aaa_base libQtWebKit4 libqt4 libqt4-qt3support libqt4-sql libqt4-sql-mysql libqt4-x11 sysvinit The following NEW patches are going to be installed: aaa_base libQtWebKit-devel - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmZen8ACgkQtTMYHG2NR9V85QCcCJboQvrvAd6Bh/npfsyYcz37 oIYAoIz+X85xh6U8KaVX+nFUjqVhcdxr =xMc9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Norrbring wrote:
Thanks Lars, But what priority do I need to set it to? Currently it's the lowest number in the list.. # | Alias | Name | Enabled | Refresh | Priority | Type --+-----------------------+-----------------------+---------+---------+----------+------- 1 | Samba_Stable_1 | Samba Stable | Yes | Yes | 98 | rpm-md 2 | openSUSE 11.1-0 | openSUSE 11.1-0 | No | No | 99 | yast2 3 | openSUSE-11.1-Updates | openSUSE-11.1-Updates | Yes | Yes | 99 | rpm-md
Also, the Samba Stable version usually serves good, and it's more a bit of experiment than a production server.. I normally go with only the distribution and update repos for machines at production level. ;-)
Anders.
Try zypper dup -r 1 which will change the vendor and update your packages. Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thanks Lars, But what priority do I need to set it to? Currently it's the lowest number in the list.. # | Alias | Name | Enabled | Refresh | Priority | Type --+-----------------------+-----------------------+---------+-------- -+----------+------- 1 | Samba_Stable_1 | Samba Stable | Yes | Yes | 98 | rpm-md 2 | openSUSE 11.1-0 | openSUSE 11.1-0 | No | No | 99 | yast2 3 | openSUSE-11.1-Updates | openSUSE-11.1-Updates | Yes | Yes | 99 | rpm-md
Also, the Samba Stable version usually serves good, and it's more a bit of experiment than a production server.. I normally go with only
Anders Norrbring wrote: the distribution and update repos for machines at production level. ;-)
Anders.
Try zypper dup -r 1 which will change the vendor and update your packages. Regards Dave P
True Dave, it will do that.. But I'm still hanging on to that vendors.d configuration option.. If I change vendors with the dup command, zypper will use that new vendor. What if the official update repo then presents a newer release than the one in the "other" vendor repo? Then I need to change back manually again. And so on... That's why I started to look at the vendors.d config option in the first place, it would then pull from any of the repos, no matter what the vendor is. Anders. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Feb 13, 2009 at 11:34:23PM +0100, Lars Müller wrote:
On Fri, Feb 13, 2009 at 09:13:17AM +0100, Anders Norrbring wrote:
I've added the build service samba repo to my config, and of course it doesn't show any updates when executing 'zypper lu', because it's not the same vendor as the base system..
Please modify the priority of the samba repo you added.[1]
Yes, this needs documentation at http://en.openSUSE.org/Samba or better in general.
Changing priorities can't help here. The package manager works like this: If a package is already installed, all packages with different vendor(*) or architecture are pruned from the update candidate list. Afterwards the highest version gets selected considering the repo priority. (*) different vendor means vendor not in the same equivalence class. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 16 Feb 2009 22:11:02 Michael Schroeder wrote:
[...]
(*) different vendor means vendor not in the same equivalence class.
Can you please define what you mean by "equivalence class"? Perhaps give examples of vendors that are or are not equivalent (or preferably both)? Thanks, Rodney. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================
On Mon, Feb 16, 2009 at 10:24:03PM +1030, Rodney Baker wrote:
On Mon, 16 Feb 2009 22:11:02 Michael Schroeder wrote:
[...]
(*) different vendor means vendor not in the same equivalence class.
Can you please define what you mean by "equivalence class"? Perhaps give examples of vendors that are or are not equivalent (or preferably both)?
I don't know the exact details, sorry. I think you have to create a file in /etc/zypp/vendors.d for each equivalence class. /etc/zypp/zypp.conf contains this: ## ## Defining directory which contains vendor description files. ## ## One file in this directory reflects a group of equivalent vendors. e.G.: ## (filename is "nvidia" but could be any other name): ## ------------------------- file contains begin ----------------------- ## [main] ## ## vendors = nvidia,suse,opensuse ## ## ------------------------- file contains end ----------------------- ## Libzypp makes an string comparision (like strncmp, case-insensitive) ## whereas the beginning of the strings are compared only. ## e.G. vendor "opensuse11.0" is compatible to "openSuSE". ## ## Valid values: A directory ## Default value: {configdir}/vendors.d ## # vendordir = /etc/zypp/vendors.d Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Feb 16, 2009 at 10:24:03PM +1030, Rodney Baker wrote:
On Mon, 16 Feb 2009 22:11:02 Michael Schroeder wrote:
[...]
(*) different vendor means vendor not in the same equivalence class.
Can you please define what you mean by "equivalence class"? Perhaps give examples of vendors that are or are not equivalent (or preferably both)?
I don't know the exact details, sorry. I think you have to create a file in /etc/zypp/vendors.d for each equivalence class. /etc/zypp/zypp.conf contains this:
## ## Defining directory which contains vendor description files. ## ## One file in this directory reflects a group of equivalent vendors. e.G.: ## (filename is "nvidia" but could be any other name): ## ------------------------- file contains begin ---------------------- - ## [main] ## ## vendors = nvidia,suse,opensuse ## ## ------------------------- file contains end ----------------------- ## Libzypp makes an string comparision (like strncmp, case-insensitive) ## whereas the beginning of the strings are compared only. ## e.G. vendor "opensuse11.0" is compatible to "openSuSE". ## ## Valid values: A directory ## Default value: {configdir}/vendors.d ## # vendordir = /etc/zypp/vendors.d
Cheers, Michael.
That's what I originally did, but it doesn't seem to do any good... Anders. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Feb 16, 2009 at 01:41:54PM +0100, Anders Norrbring wrote:
That's what I originally did, but it doesn't seem to do any good...
Btw, zypper seems to log the equivalent vendors in /etc/log/zypper.log: [zypp::VendorAttr] VendorAttr.cc(addVendorDirectory):212 /etc/zypp/vendors.d not found. [zypp::VendorAttr] VendorAttr.cc(VendorAttr):150 Equivalent vendors: [zypp::VendorAttr] VendorAttr.cc(VendorAttr):154 opensuse (group 2) [zypp::VendorAttr] VendorAttr.cc(VendorAttr):154 suse (group 2) Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Feb 16, 2009 at 01:41:54PM +0100, Anders Norrbring wrote:
That's what I originally did, but it doesn't seem to do any good...
Btw, zypper seems to log the equivalent vendors in /etc/log/zypper.log:
[zypp::VendorAttr] VendorAttr.cc(addVendorDirectory):212 /etc/zypp/vendors.d not found. [zypp::VendorAttr] VendorAttr.cc(VendorAttr):150 Equivalent vendors: [zypp::VendorAttr] VendorAttr.cc(VendorAttr):154 opensuse (group 2) [zypp::VendorAttr] VendorAttr.cc(VendorAttr):154 suse (group 2)
Cheers, Michael.
True, I have this in my log: 2009-02-16 07:30:25 <1> beata(13200) [zypp::VendorAttr] VendorAttr.cc(addVendorDirectory):222 Adding file /etc/zypp/vendors.d/vendors 2009-02-16 07:30:25 <1> beata(13200) [zypp::VendorAttr] VendorAttr.cc(VendorAttr):150 Equivalent vendors: 2009-02-16 07:30:25 <1> beata(13200) [zypp::VendorAttr] VendorAttr.cc(VendorAttr):154 open (group 2) 2009-02-16 07:30:25 <1> beata(13200) [zypp::VendorAttr] VendorAttr.cc(VendorAttr):154 opensuse (group 2) 2009-02-16 07:30:25 <1> beata(13200) [zypp::VendorAttr] VendorAttr.cc(VendorAttr):154 suse (group 2) My repos look like this: beata:/var/log # zypper sl -p # | Alias | Name | Enabled | Refresh | Priority | Type --+-----------------------+-----------------------+---------+---------+----------+------- 1 | Samba_Stable_1 | Samba Stable | Yes | Yes | 98 | rpm-md 2 | openSUSE 11.1-0 | openSUSE 11.1-0 | No | No | 99 | yast2 3 | openSUSE-11.1-Updates | openSUSE-11.1-Updates | Yes | Yes | 99 | rpm-md 4 | repo-debug | openSUSE-11.1-Debug | No | Yes | 100 | NONE 5 | repo-non-oss | openSUSE-11.1-Non-Oss | Yes | Yes | 100 | yast2 6 | repo-oss | openSUSE-11.1-Oss | Yes | Yes | 100 | yast2 7 | repo-source | openSUSE-11.1-Source | No | Yes | 100 | NONE 8 | repo-update | openSUSE-11.1-Update | Yes | Yes | 20 | rpm-md Checking status for 'samba': beata:/var/log # zypper if samba Retrieving repository 'openSUSE-11.1-Updates' metadata [done] Building repository 'openSUSE-11.1-Updates' cache [done] Retrieving repository 'openSUSE-11.1-Update' metadata [done] Building repository 'openSUSE-11.1-Update' cache [done] Loading repository data... Reading installed packages... Information for package samba: Repository: Samba Stable Name: samba Version: 3.2.8-2.1 Arch: x86_64 Vendor: openSUSE Build Service Installed: Yes Status: out-of-date (version 3.2.6-0.3.1 installed) Installed Size: 15.1 M Summary: A SMB/CIFS File, Print, and Authentication Server Description: Samba is a suite of programs that allows SMB/CIFS clients to use the Unix file space, printers, and authentication subsystem. Says 'out of date', but when running zypper lu: beata:/var/log # zypper lu Loading repository data... Reading installed packages... S | Repository | Name | Version | Arch --+----------------------+----------+-----------------+------- v | openSUSE-11.1-Update | aaa_base | 11.1-10007.12.1 | x86_64 v | openSUSE-11.1-Update | sysvinit | 2.86-186.15.1 | x86_64 No samba... But when running with dup -r 1, I get the samba related packages in the list. beata:/var/log # zypper dup -D -r 1 Loading repository data... Reading installed packages... Computing distribution upgrade... The following packages are going to be upgraded: cifs-mount libsmbclient0 libtalloc1 libtdb1 libwbclient0 samba samba-client The following packages are going to change vendor: cifs-mount libsmbclient0 libtalloc1 libtdb1 libwbclient0 samba samba-client I got the impression that the file in vendors.d should enable different vendors "automatically", but that doesn't seem to be the case. Anders. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Feb 16, 2009 at 02:47:31PM +0100, Anders Norrbring wrote:
I got the impression that the file in vendors.d should enable different vendors "automatically", but that doesn't seem to be the case.
I think this is because of a hack the libzypp guys added to make "opensuse build service" not match "opensuse". Try adding an explict "opensuse build service" to your list of equivalent vendors. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Feb 16, 2009 at 02:47:31PM +0100, Anders Norrbring wrote:
I got the impression that the file in vendors.d should enable different vendors "automatically", but that doesn't seem to be the case.
I think this is because of a hack the libzypp guys added to make "opensuse build service" not match "opensuse". Try adding an explict "opensuse build service" to your list of equivalent vendors.
Cheers, Michael.
I just did, still the same depressing result.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Anders Norrbring -
Carlos E. R. -
Dave Plater -
Ken Schneider -
Lars Müller -
Michael Schroeder -
Rajko M. -
Rodney Baker