2010/12/5 Pascal Bleser <pascal.bleser@opensuse.org>:
On 2010-12-05 00:43:52 (+0100), Stephan Kleine <bitdealer@gmail.com> wrote:
On Saturday December 4 2010 11:28:26 Pascal Bleser wrote: [...]
(but it still consumes build power on our infrastructure and doesn't alleviate the problem of people using Packman for multimedia also getting updates for those)
If that happens then people are "doing it wrong" cause the vendor stickiness prevents that. If they disable the vendor stickiness they have no reason to moan cause it is their own fault, not?
Not sure I'd agree, because vendor stickiness still gets a lot of things wrong, especially in the sense that certain zypper actions don't behave as expected when vendor stickiness is enabled.
They behave as I expect.
Also, that vendor stickiness flag is global, not per-repository and, hence, while you might want to have everything updated from K:D:F, you might not want the claws-mail package from Packman.
Vendor stickness will disallow any of those if they aren't explicitly allowed. So do "zypper dup --from K:D:F" and manually select what you want to be updated from Packman (the explicit "allow")... and from now on "zypper up" will do its work.
Priorities might solve that, but they're a bit awkward and, sadly, rather undocumented.
Priorities are a *very* natural concept. "In any operation, if there is an option, packages from repos with a higher priority get preference" (and change vendor is not an option with anything but "zypper dup"). It's so simple, what's awkward with that? Only use Packman for multimedia is my user case, and I have no problems. Not for everybody, but with a ~30 lines lock file I can even use "zypper dup" to update my system, catching some problems in repos. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org