Mailing List Archive

I agree, it's weird :-)

I solved it by unmerging the package first.

On Wed, May 12, 2010 at 12:46 PM, Tanstaafl <tanstaafl@libertytrek.org>wrote:

> I started getting this yesterday:
>
> myhost : Tue May 11, 06:04:57 : ~
> # emerge -pvuDN world
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild NS ] media-libs/libpng-1.2.43-r2 [1.2.40] 527 kB [0]
> [ebuild U ] media-libs/libpng-1.2.43-r1 [1.2.40] 0 kB [0]
> [blocks B ] <media-libs/libpng-1.2.43-r2
> ("<media-libs/libpng-1.2.43-r2" is blocking media-libs/libpng-1.2.43-r2)
>
> How can a package be blocking itself?
>
> Should I just unmerge media-libs/libpng-1.2.43-r1?
>
>

On 12 May 2010 12:46, Tanstaafl <tanstaafl@libertytrek.org> wrote:
> I started getting this yesterday:
>
> myhost : Tue May 11, 06:04:57 : ~
>  # emerge -pvuDN world
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild  NS   ] media-libs/libpng-1.2.43-r2 [1.2.40] 527 kB [0]
> [ebuild     U ] media-libs/libpng-1.2.43-r1 [1.2.40] 0 kB [0]
> [blocks B     ] <media-libs/libpng-1.2.43-r2
> ("<media-libs/libpng-1.2.43-r2" is blocking media-libs/libpng-1.2.43-r2)
>
> How can a package be blocking itself?
>
> Should I just unmerge media-libs/libpng-1.2.43-r1?

Maybe helps you if you read the libnpng thread on gentoo-users list.
The libpng upgrade cause few problems.
Here is the bugzilla: http://bugs.gentoo.org/show_bug.cgi?id=319029
Here is the thread: http://news.gmane.org/gmane.linux.gentoo.user/cutoff=229714

--
- -
-- Csanyi Andras -- http://sayusi.hu -- Sayusi Ando
-- "Bízzál Istenben és tartsd szárazon a puskaport!".-- Cromwell

On 2010-05-12 7:33 AM, András Csányi wrote:
> On 12 May 2010 12:46, Tanstaafl <tanstaafl@libertytrek.org> wrote:
>> I started getting this yesterday:
>>
>> myhost : Tue May 11, 06:04:57 : ~
>> # emerge -pvuDN world
>>
>> These are the packages that would be merged, in order:
>>
>> Calculating dependencies... done!
>> [ebuild NS ] media-libs/libpng-1.2.43-r2 [1.2.40] 527 kB [0]
>> [ebuild U ] media-libs/libpng-1.2.43-r1 [1.2.40] 0 kB [0]
>> [blocks B ] <media-libs/libpng-1.2.43-r2
>> ("<media-libs/libpng-1.2.43-r2" is blocking media-libs/libpng-1.2.43-r2)
>>
>> How can a package be blocking itself?
>>
>> Should I just unmerge media-libs/libpng-1.2.43-r1?

> Maybe helps you if you read the libnpng thread on gentoo-users list.
> The libpng upgrade cause few problems.

I didn't upgrade and am not *trying* to upgrade to 1.4, so why would
those apply to this case?

> Here is the bugzilla: http://bugs.gentoo.org/show_bug.cgi?id=319029
> Here is the thread: http://news.gmane.org/gmane.linux.gentoo.user/cutoff=229714

Again, those don't seem pertinent.

If you look at my output, I currently have 1.2.40 installed, which I see
is now hard masked (M). The problem is portage wants to:

1. upgrade 1.2.40 to 1.2.43-r1

*and*

2. install 1.2.43-r2 in a NEW SLOT.

This appears to be plain wrong and a bug, no?

By the way,

The chromium-bin ebuild should be modified to use the new libpng version.
Because the ebuild states the dependency:

media-libs/libpng:1.2

So portage wants to install libpng-1.2.43-r1, that blocks libpng-1.2.43-r2.
This caused me a lot of troubles. But, I have created another chromium-bin
ebuild substituting that dependency to this one:

media-libs/libpng

Because, since the two versions are the same, that shouldn't be
incompatibilities. So, after this I removed libpng-1.2.43-r1, installed
libpng-1.2.43-r2 and re-emerged chromium-bin. Now everything seems to be
working right.

Regards,
--
Ronan Arraes Jardim Chagas
Control and Automation Engineer
Gentoo Foundation Member

Em Qua 12 Mai 2010, às 07:46:41, Tanstaafl escreveu:
> I started getting this yesterday:
>
> myhost : Tue May 11, 06:04:57 : ~
> # emerge -pvuDN world
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild NS ] media-libs/libpng-1.2.43-r2 [1.2.40] 527 kB [0]
> [ebuild U ] media-libs/libpng-1.2.43-r1 [1.2.40] 0 kB [0]
> [blocks B ] <media-libs/libpng-1.2.43-r2
> ("<media-libs/libpng-1.2.43-r2" is blocking media-libs/libpng-1.2.43-r2)
>
> How can a package be blocking itself?
>
> Should I just unmerge media-libs/libpng-1.2.43-r1?

On 2010-05-12 8:26 AM, Tanstaafl wrote:
> If you look at my output, I currently have 1.2.40 installed, which I see
> is now hard masked (M).

The actual bug for my problem is so I just added my comments/info:

http://bugs.gentoo.org/show_bug.cgi?id=319457

Apparently 1.2.43-r2 changed the slot for libpng from "1.2" to "0"...

Incidentally... can anyone give even a *semblance* of a good reason why
1.2.40 was hard masked on *the* same* *day* that the new/updated (and
slot changed in the case of ebuilds were made available? That is
apparently what is causing this breakage.

I eix-sync and then emerge -pvuDN world *daily*, so this happened on the
same day (can't blame this on a lazy sysadmin who only updates his
system every few months).

> The problem is portage wants to:
>
> 1. upgrade 1.2.40 to 1.2.43-r1
>
> *and*
>
> 2. install 1.2.43-r2 in a NEW SLOT.
>
> This appears to be plain wrong and a bug, no?