rBuilder Talk:How do you avoid package conflicts
From rPath Wiki
Trying to cook a combination of packages gave this error.
RuntimeError (Conflicts which couldn't be automatically corrected have occured:
openssl:lib=/conary.rpath.com@rpl:devel/0.9.8c-2-1[~!bootstrap,krb is: x86(~!i686)]
openssl:lib=/conary.rpath.com@rpl:devel//1/0.9.7f-10.6-1[~!bootstrap,krb is: x86(~!i686)]
pam:lib=/conary.rpath.com@rpl:devel/0.99.6.2-3-1[~!builddocs is: x86]
pam:lib=/conary.rpath.com@rpl:devel//1/0.79-5-0.1[~!builddocs,~!selinux is: x86] )
When selecting packages to add to a project how can you tell which ones will be compatible and which ones are not?
What are the package attributes to discern that from?
- Voipfc 09:11, 16 November 2006 (EST)
- For a full index of all existing discussion topics, see Forum Topics.
- For instructions on using the rPath Wiki forums, see Forum Usage Instructions.
- For information on all recommended methods of communicating with rPath, see How to Communicate with rPath.
Comments
Answer
These conflicts typically happen when you accidentally include package from both the stable conary.rpath.com@rpl:1 Conary label and the in-development conary.rpath.com@rpl:devel label.
To resolve package conflicts like this, ensure all of the packages you select are from the same label. The distinction may not be apparent, especially when searching for packages.
When searching for packages, select packages with versions that start with conary.rpath.com@rpl:1, and avoid those with the rpl@devel label.
When browsing a repository, be aware of the //1/ sequence after the @rpl:devel; this indicates that the package is a shadow from rpl:devel to rpl:1. If you add an @rpl:devel package without the //1/ sequence in its version string, you may have unresolvable conflicts. --TimGerla 10:40, 16 November 2006 (EST)