On 13/08/10 18:34, Allan McRae wrote:
On 13/08/10 17:41, Allan McRae wrote:
Has something changed in the handling of provides/conflicts/replaces.
:: Synchronizing package databases... core 35.7K 30.4K/s 00:00:01 [######################] 100% extra 458.8K 52.5K/s 00:00:09 [######################] 100% community 380.4K 40.4K/s 00:00:09 [######################] 100% :: Starting full system upgrade... resolving dependencies... looking for inter-conflicts... :: elfutils and libelf are in conflict. Remove libelf? [y/N]
pacman -Si elfutils Repository : core Name : elfutils Version : 0.148-1 URL : https://fedorahosted.org/elfutils/ Licenses : GPL2 Groups : None Provides : libelf Depends On : glibc Optional Deps : None Conflicts With : libelf Replaces : libelf
So the elfutils PKGBUILD has provides/conflicts/replaces=libelf.
Didn't this use to replace the package rather than causing a conflict?
Hmm... is this because the gcc update is pulling in elfutils so the replaces never gets activated?
For some reason I am getting this but other people are getting the the usual replaces. So if no-one else replicates, just ignore this...