public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Fwd: [Bug 319061] media-libs/libfoo-1.4.2 update not 	handled by preserved-libs due to uninstall of older SLOT
Date: Fri, 28 May 2010 00:19:26 +0300	[thread overview]
Message-ID: <4BFEE1DE.2010609@gentoo.org> (raw)
In-Reply-To: <AANLkTilZzWeKt7cn27XXtSDZg4zgivk_L0JNNLBGI6BK@mail.gmail.com>

On 05/28/2010 12:09 AM, Ben de Groot wrote:
> On 27 May 2010 22:52, Samuli Suominen <ssuominen@gentoo.org> wrote:
>> On 05/27/2010 11:27 PM, Ben de Groot wrote:
>>> There is no libfoo. This bug is about libpng. Don't try to hide the
>>> problem by renaming it.
>>
>> No, the bug is about Portage 2.2 and @preserved-libs feature.
>>
>> It was restricted by Arfrever before, then you unrestricted it and the
>> (unrelated) bugspam continued because people wandered there by the
>> $summary and lack of knowledge what the bug is for.
>>
>> Marked as duplicate of bug 286714 now.
> 
> Then what is the bug for problems caused by the libpng-1.4 update?
> 
> Cheers,
> Ben
> 

If you have real bugs to report, open one per one package and make it
block the tracker 305095.  At the moment, there's none.

If you want to discuss about local upgrading problems, then use the
forums.  The ebuild already comes with the workaround script for the
broken .la files, and revdep-rebuild is in the gentoolkit package.




      reply	other threads:[~2010-05-27 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-319061-15115@http.bugs.gentoo.org/>
     [not found] ` <comment-1274949866-bug-319061-15115@http.bugs.gentoo.org/>
2010-05-27 20:27   ` [gentoo-dev] Fwd: [Bug 319061] media-libs/libfoo-1.4.2 update not handled by preserved-libs due to uninstall of older SLOT Ben de Groot
2010-05-27 20:52     ` Samuli Suominen
2010-05-27 21:09       ` Ben de Groot
2010-05-27 21:19         ` Samuli Suominen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BFEE1DE.2010609@gentoo.org \
    --to=ssuominen@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox