|
Bugzilla – Full Text Bug Listing |
| Summary: | Mesa and xorg-x11-Mesa (and -devel) packages have file conflicts | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Peter Bowen <pzb> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED INVALID | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | kkaempf |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Peter Bowen
2006-01-25 18:19:55 UTC
Exactly, Mesa obsoletes/provides xorg-x11-Mesa. Provides: xorg-x11-Mesa XFree86-Mesa Obsoletes: xorg-x11-Mesa XFree86-Mesa 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 > > 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 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? 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. 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. > 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 ... > 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?
Anyway, I still can't follow your arguments. Closing as INVALID. |