| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Roy Wright wrote: |
| 5 |
|
| 6 |
> Howdy, |
| 7 |
> |
| 8 |
> While attempting to try the latest version of ruby-gnome2 (0.19.1), I |
| 9 |
> copied the 0.19.0 ebuilds to my local overlay then renamed them to the |
| 10 |
> new version. I then downloaded the ruby-gnome2-all-0.19.1.tar.gz, |
| 11 |
> placed it in /usr/portage/distfiles, then used "ebuild ruby-... |
| 12 |
> digest" for each of the packages to create the Manifest file. |
| 13 |
> |
| 14 |
> When I attempt to emerge the updated packages, the first package, ruby- |
| 15 |
> glib2-0.19.1, errors with a detected file collision on /usr/lib/ |
| 16 |
> pkgconfig. This is a directory and thus emerge finds every package |
| 17 |
> that has installed a file in it. |
| 18 |
> |
| 19 |
> Now my guess is that some code that attempts to check for conflicts |
| 20 |
> within the /usr/lib/pkgconfig directory is being given an blank |
| 21 |
> package name, thus is checking the directory. My problem is I don't |
| 22 |
> see where the conflict code is even called. Anyone have any hints or |
| 23 |
> know where the documentation is? |
| 24 |
> |
| 25 |
> TIA, |
| 26 |
> Roy |
| 27 |
|
| 28 |
My first guess is that, for some reason, the package is trying to install a |
| 29 |
*file* named /usr/lib/pkgconfig: if this is the case, you can find out by |
| 30 |
checking in /var/tmp/portage/${CATEGORY}/${PF}/image/ (herein called |
| 31 |
"${D}"), which contains the full tree that the package is trying to install. |
| 32 |
If usr/lib/pkgconfig under that directory is a file, then it would collide |
| 33 |
with every package that installs a directory named /usr/lib/pkgconfig. |
| 34 |
|
| 35 |
- -- |
| 36 |
ABCD |
| 37 |
-----BEGIN PGP SIGNATURE----- |
| 38 |
Version: GnuPG v2.0.11 (GNU/Linux) |
| 39 |
|
| 40 |
iEYEARECAAYFAkp1b0wACgkQOypDUo0oQOpXtwCdF5wJNLH934Bvf9DySe7MP/rO |
| 41 |
2xoAoNsnQ13Mmv3FL3ofr2FKe0VD5T/h |
| 42 |
=OfYF |
| 43 |
-----END PGP SIGNATURE----- |
Archives