Bug 206927

*** Bug 206928 has been marked as a duplicate of this bug. ***

Anja, could you please remove patch-kernel-1836 from the update repos for 10.1, to work around this problem.

i see the same.

Created attachment 99182 [details]
YaST2.tar.bz2

What is the version of libzypp that gives you the conflict?

the 10.1 released version of libzypp.

1.3.2-0.6

patch-kernel-1836.xml removed from euklid staging area for 10.1

*** Bug 208151 has been marked as a duplicate of this bug. ***

Both patches will be selected for installation in the package-bindings and zmd:

2006-09-20 13:17:48 <1> westernhagen(7036) [wfm] Resolvable.cc(ResolvableSetPatches):583 Setting 'UITh_[S2:0][patch]kernel-1836-0.noarch
2006-09-20 13:17:48 <1> westernhagen(7036) [wfm] Resolvable.cc(ResolvableSetPatches):583 Setting 'UITh_[S2:0][patch]kernel-2036-0.noarch

Each patch requires the message with the same name but different versions. 
A parallel installation of resolvables are not allowed. So the error is correct.

Solutions:

Take another name for the messages. E.G. put the version number in name of the 
message

OR

Do not select patches with the same name and different versions at the same time. Package bindings AND zmd would have to take care about it.

I would prefer the second one and will have a look to the package bindings meanwhile.

Any other opinions ?

I have fixed/tested it in the package bindings in (Revision 33183/SLES10_SP1).
Only the newest patch which is needed will be preselected.
Ladislav could you please check it again ?

Jawaad you are the project manager of zmd. Could you please help here in order solving it on the zmd side ? Thanks  !

comment #10: "Each patch requires the message with the same name but different versions."
Does the patch require an explicit version of the message ? Shouldn't it require a minimum version (message >= x.y) instead ?

comment #10: "parallel installation of resolvables are not allowed."
It is allowed for some resolvables, i.e. explicitly flagged packages like the kernel and for atoms. Maybe scripts and messages should also be allowed ?

comment #12 (comment #10)
Question 1: 
In that case the patch require an explicit version of the message.
Question 2: 
Not really, cause a message could belong to that patch only. If you use ">=" you could get a message from a newer patch while installing an older explizit.
So the better way would be to give the message a special name. In our case Rudi has nameed the message "message-<patchID>"

comment #12 (comment #10)
Currently only atoms are allowed parallel instalation. Kernel are distinguished by the name (kernen-<flavour>).
I prefer not making additional exception for other resolveables. I our case two kernel patches has been selected for installation ( not by the user, but by the package bindings). If we would allow parallel installation of messages the next step would have been that we would have gotten an error message that parallel installation of patches are not allowed.
So we can avoid these conflicts by not allowing pararallel installation of patches at the same time with the same name but different versions. 
BUT selecting a desired patch with a special version, down- or upgrading is allowed at every time.

Stano - is this still and issue?  If so can you comment here to help Guru and team know what we are looking for here?  

Thanks - Tim

My understanding is that that more than one version of a patch was
selected at the same time by ZMD.

Guru, could you, please, double-check, if that might be the case and 
select only the newest one?

Apparently, a patch with an older version was selected although a newer already exists.

Afaik, messages are parallel installable in zypp now. Stefan, please confirm.

"Afaik, messages are parallel installable in zypp now."
No, only Atoms are parallel installable. See comment #13


"Apparently, a patch with an older version was selected although a newer already
exists."

already fixed. See comment #11 ( fixed in package bindings). 
There is still the question if it is also fixed on the ZMD side.
So I do not understand why this bug has come back to me.
Stano, could you please check it ?

Messages and scripts should be parallel installable. Is there any reason to prevent this ?

counterquestion: Is there any reason for allowing it ? ;-)
Parallel installed objects always produce problems.
An example: What should happen while an update of parallel installed object ?
Update all ? Update the latest, the oldest ? Shall I ask the user ?
Currently there is no need for allowing parallel installation of messages or scripts.
Sometime ago I had a discussion concerning that point with Michl and we came to following result:
- script/messages are a part of a patch and should not be a single object.
  The problem with installation order should be handle in the patch description
- We do not want the Atoms anymore.
- The decision if an object can be installed parallel should not be taken by 
  the solver. The information if it is possible or not should be stored in the 
  object. So the solver can ask the concerning object.

Preventing parallel installs is fine on the resolver level since RPM behaves identically.

We do have "is parallel installable" as a flag in the atoms. Is this also valid for scripts and messages ? If yes, then we're fine.

I agree that upgrading/removing parallel installed objects poses a problem - but is this real ?
Ihmo this bug shows a more severe problem which is rather easily fixable.

comment #18
"There is still the question if it is also fixed on the ZMD side.
....
Stano, could you please check it ?"

Guru, could anyone please check the question from comment #18?

Jinu, can you please check this.

rug and zen-installer are flexible in the case when there are multiple versions of same patch are available.

if 'rug in <patchname>' command is issued then it will take the latest patch.
if 'rug in <patchname-version>' command is issued then it will take that particular version of patch.

Similarily in zen-installer by default the latest version of the patch is displayed. So the user can install only the latest version.
But in the preference if 'Show version details' checkbox is selected then it will display all versions of the patches. Then user can select whichever version he wants.

Schubi, I hope that's all you need to know.

Yes, thank you.

*** Bug 202633 has been marked as a duplicate of this bug. ***