On Fri, Aug 13, 2010 at 8:54 PM, Florian Pritz
<[email protected]> wrote:
> On 13.08.2010 20:42, Xavier Chantry wrote:
>> On Fri, Aug 13, 2010 at 1:46 PM, Allan McRae <[email protected]> wrote:
>>>>
>>>> I got a conflict too. pacman 3.4.0-2
>>>
>>> Great, I am not going mad. But not great, something strange is
>>> happening...
>>>
>>
>> Can you show debug output ?
>> And libelf is not in any of your sync repo, ie pacman -Si libelf does
>> not return anything ?
>
> According to my (some hours old) database it has been in core.
>
Well the code does this (sync.c) :
/* Search for literal then replacers in each sync database.
* If found, don't check other databases */
So if the literal (libelf) still exists in the db, the replacer
(elfutils) isn't even considered.
But it's then pulled as a dep for gcc, thus the conflict message.
