There were several patches, which I had installed on my non-TW machine.
On a TW machine, I ran “zypper dup”. And I expected it to install those patches.
I was surprised when later, after login to Gnome, I was informed that there was an important update.
Checking, I could see that the “cryptsetup-mkinitrd” patch had not been installed by “zypper dup”.
Running “zypper dup” again, it said “nothing to do”.
I check Yast software management. The only versions for this were from the main 12.3 repo and the update repo. So there should not have been a repo conflict.
I installed with Yast online update. And “zypper dup” is still happy.
I am just a little puzzled about what happened, and why “zypper dup” did not install that patch.
On 05/28/2013 03:56 PM, nrickert pecked at the keyboard and wrote:
> There were several patches, which I had installed on my non-TW machine.
>
> On a TW machine, I ran “zypper dup”. And I expected it to install
> those patches.
>
> I was surprised when later, after login to Gnome, I was informed that
> there was an important update.
>
> Checking, I could see that the “cryptsetup-mkinitrd” patch had not been
> installed by “zypper dup”.
>
> Running “zypper dup” again, it said “nothing to do”.
>
> I check Yast software management. The only versions for this were from
> the main 12.3 repo and the update repo. So there should not have been a
> repo conflict.
>
> I installed with Yast online update. And “zypper dup” is still happy.
>
> I am just a little puzzled about what happened, and why “zypper dup”
> did not install that patch.
Don’t know.
But you don’t have to install all the patches, if you have all the latest packages anyway.
A patch doesn’t really get installed, it is not really in the repo (at least not as a package). It’s just some metadata with a description what got fixed and what packages are affected. So if you just install the fixed packages with zypper dup everything is OK.
[QUOTE=robin_listas;2561094Actually, the version in 12.3 is “0_201206151440-3.4.1”. The numbers on
the left are probably more important than the “3.4.1”.
Then you also have to consider what priority levels you use on your repo
mix.[/QUOTE]
That’s true, but there’s only cryptsetup-mkinitrd-0_201206151440-3.4.1 in Update and cryptsetup-mkinitrd-0_201206151440-3.1.1 in the standard Oss repo and none in Tumbleweed, so it should have got updated.
And I don’t think nrickert has a higher priority on Oss than on Update, since the other 5 patches wouldn’t have been installed then either by “zypper dup”…
@nrickert:
Sorry, I misunderstood you a bit. I thought all packages were installed in their highest version and you were just wondering why a “patch” wasn’t installed. That’s why I pointed out that those “patches” don’t really matter in this case.
Well, I have no idea then what happened. Maybe some repo was temporarily unreachable or something like that? Or a mirror was out of date for a short while?
Or maybe another cryptsetup-mkinitrd package was in one of your repos but got removed again?
I doubt that it is any of those. There’s probably a bug lurking somewhere, but I’m not sure where. It could be a bug in zypper, or it could be something in the way that patch was prepared. It just seemed wierd.
As for repo priorities, I have 98 for Tumbleweed and Packman Tumbleweed, and 99 for OSS, non-OSS and the corresponding update repos. So that shouldn’t have affected anything.
Yast online update did recognize and apply the patch. Presumably, “zypper patch” would have done that, too. If I see something similar cropping up in the future, I’ll experiment with dry runs of “zypper patch” and “zypper up” to see what they want to do.
The puzzle seems to be that “zypper dup” doesn’t always get the newest package.
On 2013-05-29 23:26, nrickert wrote:
>
> wolfi323;2561148 Wrote:
>> Well, difficult to say now.
>> But maybe the zypper logs tell something? Try grepping for
>> cryptsetup-mkinitrd…
>
> I can only find logs for the successful install that I forced.
You might consider sacrificing for science, undo the update, and try
again
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
