So wolfi explained to me in another thread about tumbleweed repos, but I don’t know why libreoffice doesn’t change vendor to factory automatically when I do “zypper dup”, as I even set it at a higher priority.
Priority is used to determine which repo a new package is installed from
but to change vendors, you have to tell it to do that - priority isn’t
used for that reason (because you could break dependencies by doing that,
among other things).
There are circumstances where automating that could cause an update
loop, for example, if a newer version of ‘a’ depends on an older version
of ‘b’. If a repo has a newer version of ‘b’ in that case, it might
downgrade ‘a’ to match (in order to meet dependency requirements), which
on the next update would upgrade ‘a’ and downgrade ‘b’, and so on.
On 2014-08-04 22:30, Jim Henderson wrote:
> On Mon, 04 Aug 2014 20:06:01 +0000, bonedriven wrote:
>
>> libreoffice doesn’t change vendor to factory automatically when I do
>> “zypper dup”, as I even set it at a higher priority.
> Priority is used to determine which repo a new package is installed from
> - but to change vendors, you have to tell it to do that - priority isn’t
On Mon, 04 Aug 2014 23:54:10 +0000, Carlos E. R. wrote:
> On 2014-08-04 22:30, Jim Henderson wrote:
>> On Mon, 04 Aug 2014 20:06:01 +0000, bonedriven wrote:
>>
>>> libreoffice doesn’t change vendor to factory automatically when I do
>>> “zypper dup”, as I even set it at a higher priority.
>
>
>> Priority is used to determine which repo a new package is installed
>> from - but to change vendors, you have to tell it to do that - priority
>> isn’t
>
> AFAIK, “zypper dup” does not respect vendor lock.
On Tue, 05 Aug 2014 01:10:43 +0000, Jim Henderson wrote:
> On Mon, 04 Aug 2014 23:54:10 +0000, Carlos E. R. wrote:
>
>> On 2014-08-04 22:30, Jim Henderson wrote:
>>> On Mon, 04 Aug 2014 20:06:01 +0000, bonedriven wrote:
>>>
>>>> libreoffice doesn’t change vendor to factory automatically when I do
>>>> “zypper dup”, as I even set it at a higher priority.
>>
>>
>>> Priority is used to determine which repo a new package is installed
>>> from - but to change vendors, you have to tell it to do that -
>>> priority isn’t
>>
>> AFAIK, “zypper dup” does not respect vendor lock.
>
> That is correct, as I recall.
And apparently I missed that the OP was doing that rather than an ‘up’.
>> 1) v2.40.0-0.2.9 from opensuse:Tumbleweed (currently installed)
>> 2) v2.38.0-0.6.1 from opensuse:stable_updates
>> 3) v2.38.0-0.1.1 from opensuse:stable_OSS
>>
>> What’s the difference between “stable_updates” and “stable_OSS”. Do I
>> have conflicting repos?
>
> Hi, can anyone answer this question?
“Stable oss” is a link, at the moment, to 13.1, and “stable updates”
should be a link to the 13.1 official updates. You absolutely need those
repos while using Tumbleweed. And then, of course, you need the
tumbleweed repo.
That’s the way tumbleweed is designed to work.
> Can I get rid of the repo “stable_updates”? “stable_OSS” covers what
> “stable updates” covers?
No, and no.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)