Bug 145604 - Mesa and xorg-x11-Mesa (and -devel) packages have file conflicts
Summary: Mesa and xorg-x11-Mesa (and -devel) packages have file conflicts
Status: RESOLVED INVALID
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Beta 1
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-25 18:19 UTC by Peter Bowen
Modified: 2006-01-30 20:18 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Bowen 2006-01-25 18:19:55 UTC 
There are file conflicts between the xorg-x11-Mesa and Mesa packages, but they don't conflict with each other in their deps
Comment 1 Stefan Dirsch 2006-01-25 22:12:39 UTC 
Exactly, Mesa obsoletes/provides xorg-x11-Mesa.

Provides:     xorg-x11-Mesa XFree86-Mesa
Obsoletes:    xorg-x11-Mesa XFree86-Mesa
Comment 2 Peter Bowen 2006-01-25 22:20:16 UTC 
It also needs
Conflicts: xorg-x11-Mesa XFree86-Mesa

and Mesa-devel needs
Conflicts: xorg-x11-Mesa-devel XFree86-Mesa-devel

Otherwise issues come up
Comment 3 Stefan Dirsch 2006-01-25 22:29:36 UTC 
> > Provides:     xorg-x11-Mesa XFree86-Mesa
> It also needs
> Conflicts: xorg-x11-Mesa XFree86-Mesa

Are you serious?

http://w3.suse.de/~kkaempf/specifications/how-to-specify-dependencies/dep.html#rename
Comment 4 Peter Bowen 2006-01-25 22:37:56 UTC 
There is the problem with that spec.  Using the example, if you try to do an rpm install of pac.rpm after upgrading to package.rpm, there is nothing preventing it,  other the probable file conflicts.  

Obsoletes says "move to this name", but does not say "error if installing the old name".  rpm quirk yes, but still a problem.  Klaus, what do your recommend?
Comment 5 Stefan Dirsch 2006-01-25 22:53:21 UTC 
Why the hell do you want to go back to xorg-x11-Mesa? It's obsoleted by Mesa now. The provides/obsolete is required for the package update by YAST. Adding a conflicts for the same package won't work and would be silly.
Comment 6 Peter Bowen 2006-01-25 23:20:00 UTC 
I don't want to go back.  The situation was that I was trying to build package "q" which buildrequires x11-xorg-Mesa-devel.  I tried to run 'rug in x11-xorg-Mesa-devel' which appeared to succeed, until the rpm transaction failed due to conflicting files.  An explicit conflict dependency would prevent this from happening.
Comment 7 Stefan Dirsch 2006-01-25 23:27:11 UTC 
> The situation was that I was trying to build package "q" which buildrequires > x11-xorg-Mesa-devel.

This is broken and needs to get fixed in the specfile. Which package is this?

> I tried to run 'rug in x11-xorg-Mesa-devel' which appeared to succeed, until > the rpm transaction failed due to conflicting files.  An explicit conflict 
> dependency would prevent this from happening.

'Fixing' a bug by introducing another bug? IMHO not a good idea ...
Comment 8 Stefan Dirsch 2006-01-27 15:19:57 UTC 
> The situation was that I was trying to build package "q" which buildrequires > x11-xorg-Mesa-devel.

This is broken and needs to get fixed in the specfile. Which package is this?
Comment 9 Stefan Dirsch 2006-01-30 20:18:05 UTC 
Anyway, I still can't follow your arguments. Closing as INVALID.