You are not logged in.
# pacman -Syu
:: Synchronizing package databases...
current is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies... done.
looking for inter-conflicts... done.
Targets: mercurial-0.9.4-2
Total Package Size: 0.68 MB
Proceed with installation? [Y/n] y
:: Retrieving packages from extra...
mercurial 694.7K 547.1K/s 00:00:01 [#####################] 100%
checking package integrity... done.
cleaning up... done.
(1/1) checking for file conflicts [#####################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
mercurial: /etc/bash_completion.d/hg exists in filesystem
errors occurred, no packages were upgraded.
openSUSE
Arch Linux
USALUG
Offline
That file was provided by bash_completion already. And the new release of mercurial now provides it as well.
So for now, move that /etc/bash_completion.d/hg out of the way, then choose the one you want to use and remove the other.
And you could report that problem to bugs.archlinux.org . Reporting doesn't help much usually.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Offline
Reporting doesn't help?
Hmmmm.
Oops, that was meant to be : reporting here.
Because, as far as I know, not all developers read the forums.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Before I report a bug, I post it in the forum. In this way I can find out, "stupid I am" or "it is a bug"
That is a good rule of thumb.
When you get conflict errors like that, it is sometimes helpful to see which package thinks it owns the file right now..
pacman -Qo /path/to/file
That can help with the bug report too.
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
That is a good rule of thumb.
When you get conflict errors like that, it is sometimes helpful to see which package thinks it owns the file right now..
pacman -Qo /path/to/file
That can help with the bug report too.
Thanks for this tip
openSUSE
Arch Linux
USALUG
Offline