consultation on Tumbleweed

On 2012-03-11 17:25, Vahis wrote:
> Carlos E. R. wrote:
>> On 2012-03-11 05:26, Vahis wrote:
>>> Also, it’s officially recommended to not have priorities at all.
>>
>> I know, but I do not agree.
>>
>
> O.K. :slight_smile:
>
> I do stuff myself which sometimes is not officially recommended.

It would be better if the recommendation to not have priorities were
reasoned and not absolute, then I might believe it. As it is, I believe
doing several dups with the same priorities for all repos will in the end
mix packages beyond recognition, because dup does not respect vendor change
prohibition. This is what happens with the normal distro or factory, the
behaviour of zypper dup on tumbleweed would be the same.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Carlos E. R. wrote:
> On 2012-03-11 17:25, Vahis wrote:
>> Carlos E. R. wrote:
>>> On 2012-03-11 05:26, Vahis wrote:
>>>> Also, it’s officially recommended to not have priorities at all.
>>>
>>> I know, but I do not agree.
>>>
>>
>> O.K. :slight_smile:
>>
>> I do stuff myself which sometimes is not officially recommended.
>
> It would be better if the recommendation to not have priorities were
> reasoned and not absolute, then I might believe it.

I’ve just taken it from Greg KH, as a given.

As it is, I believe
> doing several dups with the same priorities for all repos will in the end
> mix packages beyond recognition, because dup does not respect vendor change
> prohibition. This is what happens with the normal distro or factory, the
> behaviour of zypper dup on tumbleweed would be the same.

My current tumbleweed has gone all the way since day one.
I had the normal priorities in the beginning, what else would one do
when one is customed with the openSUSE way :slight_smile:

Then I removed the priorities, as advised.

Never had a problem because of that. (some others, yes, but not this)

I’ll be looking forward to see what will happen with 12.2.

When 11.4 went to 12.1 I was amazed (and disapointed) when everything
in Tumbleweed got upgraded.

I thought Tumbleweed would have grown to 12.1 during its development
cycle, but it hadn’t. Everything was upgraded to my big surprise.

I thought “rolling” would mean constant change towards the next release,
that’s why I started with in the first place.

I thought, if we think of a single package, that

  1. first it would be in Factory
  2. Later it would go to Tumbleweed

During these periods it would possibly get changed somewhat, and just
before the next release it would go to

  1. Next release

Once everything would be ready for the next release, it would be
released and

  1. The newly released and Tumbleweed would be identical.

  2. Current would be changed to point to the newly released

then,

  1. again

I guess I thought it all wrong then…

Vahis

http://waxborg.servepics.com
openSUSE 11.4 (x86_64) 2.6.37.6-0.11-default main host
openSUSE 12.1 (x86_64) 3.2.9-13-desktop Tumbleweed in VirtualBox
openSUSE 12.1 (i586) 3.1.9-1.4-desktop in EeePC 900

Same here wrt priorities on tumbleweed, although I keep the same priorities for tumbleweed, update, oss, and non-oss repos. However the reasoning breaks down for Packman so it’s at a higher priority (lower number) here. If you rely on Packman packages for a variety of multimedia apps, as I have reliably done since early openSUSE 10.x series, you don’t really want to have any of those replaced by openSUSE packages on a zypper dup.

I fail to see the logic of using Packman if flip-flopping is facilitated on upgrade from another repo containing restricted apps. It makes no operational sense!

As far as I know, Tumbleweed wasn’t complete when 11.4 rolled around. Tumbleweed was finalized with 12.1 so I guess it makes sense that things changed drastically going into the 12.1 release. I have yet to see what happens to my installation when 12.2 rolls around but I doubt it’ll be as crazy as 11.4 to 12.1 was.

On Mon, 12 Mar 2012 12:36:03 +0000, silverslimer wrote:

> As far as I know, Tumbleweed wasn’t complete when 11.4 rolled around.
> Tumbleweed was finalized with 12.1 so I guess it makes sense that things
> changed drastically going into the 12.1 release. I have yet to see what
> happens to my installation when 12.2 rolls around but I doubt it’ll be
> as crazy as 11.4 to 12.1 was.

It will happen the same exact way, what was so “crazy” about it?

Remember, Tumbleweed is only an add-on repo to the main base openSUSE
repo. It does not contain all packages in the openSUSE repo for a
variety of reasons.

greg k-h

On Sun, 11 Mar 2012 13:26:03 +0000, jony127 wrote:

> I added the 4 repo Tumbleweed and Packman Tumbleweed, run a zypper dup
> but has not been updated to version 4.8 kde.

That’s because KDE 4.8 is not in Tumbleweed yet, it is still being worked
on.

You can follow along if you like by looking at the
openSUSE:Tumbleweed:Testing repo as to how it is progressing, but it’s
not ready just yet, give it time…

greg k-h

> That’s because KDE 4.8 is not in Tumbleweed yet, it is still being worked
> on.

I have manually added the KDE 4.8 repos. What is recommended to do
when KDE 4.8 is added to Tumbleweed? Thanks.

On Wed, 21 Mar 2012 18:06:04 +0000, afshine wrote:

>> That’s because KDE 4.8 is not in Tumbleweed yet, it is still being
> worked
>> on.
>
> I have manually added the KDE 4.8 repos. What is recommended to do when
> KDE 4.8 is added to Tumbleweed? Thanks.

Remove the KDE 4.8 repo from your system.

>> That’s because KDE 4.8 is not in Tumbleweed yet, it is still being worked
>> on.

> I have manually added the KDE 4.8 repos. What is recommended to do when
> KDE 4.8 is added to Tumbleweed? Thanks.

>> Remove the KDE 4.8 repo from your system.

Thank you. :smile: