| 1 |
By the way, |
| 2 |
|
| 3 |
The chromium-bin ebuild should be modified to use the new libpng version. |
| 4 |
Because the ebuild states the dependency: |
| 5 |
|
| 6 |
media-libs/libpng:1.2 |
| 7 |
|
| 8 |
So portage wants to install libpng-1.2.43-r1, that blocks libpng-1.2.43-r2. |
| 9 |
This caused me a lot of troubles. But, I have created another chromium-bin |
| 10 |
ebuild substituting that dependency to this one: |
| 11 |
|
| 12 |
media-libs/libpng |
| 13 |
|
| 14 |
Because, since the two versions are the same, that shouldn't be |
| 15 |
incompatibilities. So, after this I removed libpng-1.2.43-r1, installed |
| 16 |
libpng-1.2.43-r2 and re-emerged chromium-bin. Now everything seems to be |
| 17 |
working right. |
| 18 |
|
| 19 |
Regards, |
| 20 |
-- |
| 21 |
Ronan Arraes Jardim Chagas |
| 22 |
Control and Automation Engineer |
| 23 |
Gentoo Foundation Member |
| 24 |
|
| 25 |
Em Qua 12 Mai 2010, às 07:46:41, Tanstaafl escreveu: |
| 26 |
> I started getting this yesterday: |
| 27 |
> |
| 28 |
> myhost : Tue May 11, 06:04:57 : ~ |
| 29 |
> # emerge -pvuDN world |
| 30 |
> |
| 31 |
> These are the packages that would be merged, in order: |
| 32 |
> |
| 33 |
> Calculating dependencies... done! |
| 34 |
> [ebuild NS ] media-libs/libpng-1.2.43-r2 [1.2.40] 527 kB [0] |
| 35 |
> [ebuild U ] media-libs/libpng-1.2.43-r1 [1.2.40] 0 kB [0] |
| 36 |
> [blocks B ] <media-libs/libpng-1.2.43-r2 |
| 37 |
> ("<media-libs/libpng-1.2.43-r2" is blocking media-libs/libpng-1.2.43-r2) |
| 38 |
> |
| 39 |
> How can a package be blocking itself? |
| 40 |
> |
| 41 |
> Should I just unmerge media-libs/libpng-1.2.43-r1? |
Archives