flat default priorities missing upgrades

English Install/Boot/Login
#1

From openSUSE-12.1-update repo there are quiet a few packages having higher versions than Tumbleweed recently added packages. When having a flat repos layout regarding priorities you will miss a lot of Tumbleweed.

Sticky thread in this forum and other supporting resources recommend to leave priorities at default level 99. Is this a just too flat policy?

#2

ulenrich wrote:
>
> From openSUSE-12.1-update repo there are quiet a few packages having
> higher versions than Tumbleweed recently added packages.

The update repo carries security parches and bug fixes.
They may well sometimes be newer than the ones in the tumbleweed repo.

When having a
> flat repos layout regarding priorities you will miss a lot of
> Tumbleweed.

Could you elaborate “miss a lot of Tumbleweed”
What exactly do you mean?
>
> Sticky thread in this forum and other supporting resources recommend to
> leave priorities at default level 99. Is this a just too flat policy?

That’s the way it’s designed.

All this has been explained, asked, answered and discussed so many times
that if someone still needs to ask I just recommend to take it as a given.

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.3.0-17-desktop Tumbleweed in VirtualBox
openSUSE 12.1 (i586) 3.1.9-1.4-desktop in EeePC 900

#3

The whole lot of apparmor related files do have minor version than in openSUSE-12.1-update but are newer once. That is because of

zypper dup

is about versions not about dates of packages. You can test by doing:

zypper mr -p 88 Tumbleweed
zypper dup

#4

ulenrich wrote:
>
> zypper dup
>
> is about versions not about dates of packages.

And zypper dup is the way to go as for updating Tumbleweed.
With repos “current” and “tumbleweed” (+ “packman tumbleweed”)
With no priorities.

That’s how the designer says it’s been designed.

I’ve been running it that way since its day one, without any problems.

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.3.0-17-desktop Tumbleweed in VirtualBox
openSUSE 12.1 (i586) 3.1.9-1.4-desktop in EeePC 900

#5

Funny, I notice the same as ulenrich. But, my guess is that these “missed updates” appeared in Tumbleweed after doing the “switch” to this repo. I ran “zypper ref && zypper up” as usual, no updates. Of course the same in the Softwaremanager. Then invoked “switch system packages .” on the Tumbleweed repo, and there they were, about 30 updates. Checked some GNOME packages, versionnumber in Tumblweed repo was the highest,

#6

Curious: Why do you not use the recommended zypper dup?

#7

I thought I saw this when running zypper dup too, then ran zypper dup --from Tumbleweed, and got the packages moved to Tumbleweed. Have to check again.

#8

That’s interesting. I run zypper ref and zypper dup and I get the apparmor update packages that are in the openSUSE update repo, these here:


john@tumbleweed121:~> zypper se -s apparmor | grep "i |"
i | apparmor                       | pattern    | 12.1-25.21.1  | x86_64 | osCurrentOss    
i | apparmor                       | pattern    | 12.1-25.21.1  | i586   | osCurrentOss    
i | apparmor-docs                  | package    | 2.7.2-3.6.1   | noarch | osCurrentUpdates
i | apparmor-parser                | package    | 2.7.2-3.6.1   | x86_64 | osCurrentUpdates
i | apparmor-profiles              | package    | 2.7.2-3.6.1   | noarch | osCurrentUpdates
i | apparmor-utils                 | package    | 2.7.2-3.6.1   | noarch | osCurrentUpdates
i | libapparmor1                   | package    | 2.7.2-3.6.1   | x86_64 | osCurrentUpdates
i | pam_apparmor                   | package    | 2.7.2-3.6.1   | x86_64 | osCurrentUpdates
i | patterns-openSUSE-apparmor     | package    | 12.1-25.21.1  | x86_64 | osCurrentOss    
i | patterns-openSUSE-apparmor_opt | package    | 12.1-25.21.1  | x86_64 | osCurrentOss    
i | perl-apparmor                  | package    | 2.7.2-3.6.1   | x86_64 | osCurrentUpdates
i | yast2-apparmor                 | package    | 2.21.5-2.1.2  | noarch | osCurrentOss

The only apparmor stuff I can see in the Tumbleweed repo is this incidental stuff:

 apache2-mod_apparmor-2.7.2-2.1.x86_64.rpm                                 01-Apr-2012 19:00   20K   Details
 apache2-mod_apparmor-debuginfo-2.7.2-2.1.x86_64.rpm                       01-Apr-2012 19:00   23K   Details
 apparmor-debugsource-2.7.2-2.1.x86_64.rpm                                 01-Apr-2012 19:00  148K   Details
 apparmor-parser-2.7.2-2.1.x86_64.rpm                                      01-Apr-2012 19:00  265K   Details
 apparmor-parser-debuginfo-2.7.2-2.1.x86_64.rpm                            01-Apr-2012 19:00  1.2M   Details

I don’t know how you can get apparmor from Tumbleweed, I can’t see it in there.