Arch Linux

bmentink

Member

From: New Zealand

Registered: 2009-08-23

Posts: 442

[SOLVED] Upgrade results in conflicting files for iproute2

Hi All,

Latest upgrade failed on iproute2 with a heap of conflicting files, is it safe to delete them?

error: failed to commit transaction (conflicting files)
iproute2: /etc/iproute2/bpf_pinning exists in filesystem
iproute2: /etc/iproute2/group exists in filesystem
iproute2: /etc/iproute2/nl_protos exists in filesystem
iproute2: /usr/bin/arpd exists in filesystem
iproute2: /usr/bin/bridge exists in filesystem
iproute2: /usr/bin/ctstat exists in filesystem
iproute2: /usr/bin/devlink exists in filesystem
iproute2: /usr/bin/genl exists in filesystem
iproute2: /usr/bin/ifcfg exists in filesystem
iproute2: /usr/bin/ifstat exists in filesystem
iproute2: /usr/bin/ip exists in filesystem
iproute2: /usr/bin/lnstat exists in filesystem
iproute2: /usr/bin/nstat exists in filesystem
iproute2: /usr/bin/routef exists in filesystem
iproute2: /usr/bin/routel exists in filesystem
iproute2: /usr/bin/rtacct exists in filesystem
iproute2: /usr/bin/rtmon exists in filesystem
iproute2: /usr/bin/rtpr exists in filesystem
iproute2: /usr/bin/rtstat exists in filesystem
iproute2: /usr/bin/ss exists in filesystem
iproute2: /usr/bin/tc exists in filesystem
iproute2: /usr/bin/tipc exists in filesystem
iproute2: /usr/include/libnetlink.h exists in filesystem
iproute2: /usr/lib/libnetlink.a exists in filesystem
iproute2: /usr/lib/tc/m_ipt.so exists in filesystem
iproute2: /usr/lib/tc/m_xt.so exists in filesystem
iproute2: /usr/lib/tc/q_atm.so exists in filesystem
iproute2: /usr/share/bash-completion/completions/tc exists in filesystem
iproute2: /usr/share/man/man3/libnetlink.3.gz exists in filesystem
iproute2: /usr/share/man/man7/tc-hfsc.7.gz exists in filesystem
iproute2: /usr/share/man/man8/arpd.8.gz exists in filesystem
iproute2: /usr/share/man/man8/bridge.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ctstat.8.gz exists in filesystem
iproute2: /usr/share/man/man8/devlink-dev.8.gz exists in filesystem
iproute2: /usr/share/man/man8/devlink-monitor.8.gz exists in filesystem
iproute2: /usr/share/man/man8/devlink-port.8.gz exists in filesystem
iproute2: /usr/share/man/man8/devlink-sb.8.gz exists in filesystem
iproute2: /usr/share/man/man8/devlink.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-address.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-addrlabel.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-fou.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-gue.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-l2tp.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-link.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-macsec.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-maddress.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-monitor.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-mroute.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-neighbour.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-netconf.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-netns.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-ntable.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-route.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-rule.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-tcp_metrics.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-token.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-tunnel.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip-xfrm.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ip.8.gz exists in filesystem
iproute2: /usr/share/man/man8/lnstat.8.gz exists in filesystem
iproute2: /usr/share/man/man8/nstat.8.gz exists in filesystem
iproute2: /usr/share/man/man8/routef.8.gz exists in filesystem
iproute2: /usr/share/man/man8/routel.8.gz exists in filesystem
iproute2: /usr/share/man/man8/rtacct.8.gz exists in filesystem
iproute2: /usr/share/man/man8/rtmon.8.gz exists in filesystem
iproute2: /usr/share/man/man8/rtpr.8.gz exists in filesystem
iproute2: /usr/share/man/man8/rtstat.8.gz exists in filesystem
iproute2: /usr/share/man/man8/ss.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-basic.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-bfifo.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-bpf.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-cbq-details.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-cbq.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-cgroup.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-choke.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-codel.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-connmark.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-csum.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-drr.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-ematch.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-flow.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-flower.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-fq.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-fq_codel.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-fw.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-hfsc.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-htb.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-matchall.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-mirred.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-mqprio.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-nat.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-netem.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-pedit.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-pfifo.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-pfifo_fast.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-pie.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-police.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-prio.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-red.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-route.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-sfb.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-sfq.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-simple.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-skbedit.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-stab.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-tbf.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-tcindex.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-u32.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-vlan.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc-xt.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tc.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tipc-bearer.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tipc-link.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tipc-media.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tipc-nametable.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tipc-node.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tipc-socket.8.gz exists in filesystem
iproute2: /usr/share/man/man8/tipc.8.gz exists in filesystem
iproute2: /usr/share/tc/experimental.dist exists in filesystem
iproute2: /usr/share/tc/normal.dist exists in filesystem
iproute2: /usr/share/tc/pareto.dist exists in filesystem
iproute2: /usr/share/tc/paretonormal.dist exists in filesystem
Errors occurred, no packages were upgraded.

.. or do all these belong to net-tools, so do I uninstall net-tools?
Does iproute2 now conflict with net-tools?

Last edited by bmentink (2017-01-15 22:51:39)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 29,525

Website

Re: [SOLVED] Upgrade results in conflicting files for iproute2

https://wiki.archlinux.org/index.php/Pa … 9.22_error

---

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

bmentink

Member

From: New Zealand

Registered: 2009-08-23

Posts: 442

Re: [SOLVED] Upgrade results in conflicting files for iproute2

so you are saying I need to do:

A safe way is to first check if another package owns the file (pacman -Qo /path/to/file).

for every one of those files? What the heck is broken with pacman ...

Last edited by bmentink (2017-01-15 18:23:49)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 29,525

Website

Re: [SOLVED] Upgrade results in conflicting files for iproute2

No one can possibly know what is going on in your system but you.  The wiki gives you instructions on how to gather information to diagnose the problem - but you must follow those instructions and share the results, or there's not a thing that anyone can do for you.

As for your final comment, nothing is broken with pacman (except the user).  Something is broken on your system and odds are strongly in favor of it being something you broke.  I'd prefer to focus on the issue and how to fix it, but if you want to point fingers and cast blame, then don't expect me to hold back on doing the same.

But no, you probably don't need to run that command for all the files, though it certainly wouldn't be hard: copy the list, and pass the whole list to pacman -Qo.  But if you `pacman -Qo ...` on a handful of those files we'd have infinitely more information than we currently do.

EDIT: I may be overinterpreting your "what's broken with pacman" comment.  It seems there are a lot of people on the forums over the last day or two that insist everything they've done wrong is someone else's fault and I picked up that vibe from your post.  I see you don't have a history of such posts and that may not have been your intent here at all.  But just the same, please consider how such statements come across.

---

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

bmentink

Member

From: New Zealand

Registered: 2009-08-23

Posts: 442

Re: [SOLVED] Upgrade results in conflicting files for iproute2

Steady on ... no one is casting blame, I was simply asking a question, don't get so defensive ..

I have done nothing to my system except update with "pacman -Syu" from time to time .... no manual installations, nothing! This is a clean system ..

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 29,525

Website

Re: [SOLVED] Upgrade results in conflicting files for iproute2

OK ... so are you going to show any pacman -Qo output or not?

---

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

bmentink

Member

From: New Zealand

Registered: 2009-08-23

Posts: 442

Re: [SOLVED] Upgrade results in conflicting files for iproute2

error: No package owns /etc/iproute2/bpf_pinning
error: No package owns /etc/iproute2/group
error: No package owns /etc/iproute2/nl_protos
error: No package owns /usr/bin/arpd
error: No package owns /usr/bin/bridge
error: No package owns /usr/bin/ctstat
error: No package owns /usr/bin/devlink
error: No package owns /usr/bin/genl
error: No package owns /usr/bin/ifcfg
error: No package owns /usr/bin/ifstat
error: No package owns /usr/bin/ip
error: No package owns /usr/bin/lnstat
error: No package owns /usr/bin/nstat
error: No package owns /usr/bin/routef
error: No package owns /usr/bin/routel
error: No package owns /usr/bin/rtacct
error: No package owns /usr/bin/rtmon
error: No package owns /usr/bin/rtpr
error: No package owns /usr/bin/rtstat
error: No package owns /usr/bin/ss
error: No package owns /usr/bin/tc
error: No package owns /usr/bin/tipc
error: No package owns /usr/include/libnetlink.h
error: No package owns /usr/lib/libnetlink.a
error: No package owns /usr/lib/tc/m_ipt.so
error: No package owns /usr/lib/tc/m_xt.so
error: No package owns /usr/lib/tc/q_atm.so
error: No package owns /usr/share/bash-completion/completions/tc
error: No package owns /usr/share/man/man3/libnetlink.3.gz
error: No package owns /usr/share/man/man7/tc-hfsc.7.gz
error: No package owns /usr/share/man/man8/arpd.8.gz
error: No package owns /usr/share/man/man8/bridge.8.gz
error: No package owns /usr/share/man/man8/ctstat.8.gz
error: No package owns /usr/share/man/man8/devlink-dev.8.gz
error: No package owns /usr/share/man/man8/devlink-monitor.8.gz
error: No package owns /usr/share/man/man8/devlink-port.8.gz
error: No package owns /usr/share/man/man8/devlink-sb.8.gz
error: No package owns /usr/share/man/man8/devlink.8.gz
error: No package owns /usr/share/man/man8/ip-address.8.gz
error: No package owns /usr/share/man/man8/ip-addrlabel.8.gz
error: No package owns /usr/share/man/man8/ip-fou.8.gz
error: No package owns /usr/share/man/man8/ip-gue.8.gz
error: No package owns /usr/share/man/man8/ip-l2tp.8.gz
error: No package owns /usr/share/man/man8/ip-link.8.gz
error: No package owns /usr/share/man/man8/ip-macsec.8.gz
error: No package owns /usr/share/man/man8/ip-maddress.8.gz
error: No package owns /usr/share/man/man8/ip-monitor.8.gz
error: No package owns /usr/share/man/man8/ip-mroute.8.gz
error: No package owns /usr/share/man/man8/ip-neighbour.8.gz
error: No package owns /usr/share/man/man8/ip-netconf.8.gz
error: No package owns /usr/share/man/man8/ip-netns.8.gz
error: No package owns /usr/share/man/man8/ip-ntable.8.gz
error: No package owns /usr/share/man/man8/ip-route.8.gz
error: No package owns /usr/share/man/man8/ip-rule.8.gz
error: No package owns /usr/share/man/man8/ip-tcp_metrics.8.gz
error: No package owns /usr/share/man/man8/ip-token.8.gz
error: No package owns /usr/share/man/man8/ip-tunnel.8.gz
error: No package owns /usr/share/man/man8/ip-xfrm.8.gz
error: No package owns /usr/share/man/man8/ip.8.gz
error: No package owns /usr/share/man/man8/lnstat.8.gz
error: No package owns /usr/share/man/man8/nstat.8.gz
error: No package owns /usr/share/man/man8/routef.8.gz
error: No package owns /usr/share/man/man8/routel.8.gz
error: No package owns /usr/share/man/man8/rtacct.8.gz
error: No package owns /usr/share/man/man8/rtmon.8.gz
error: No package owns /usr/share/man/man8/rtpr.8.gz
error: No package owns /usr/share/man/man8/rtstat.8.gz
error: No package owns /usr/share/man/man8/ss.8.gz
error: No package owns /usr/share/man/man8/tc-basic.8.gz
error: No package owns /usr/share/man/man8/tc-bfifo.8.gz
error: No package owns /usr/share/man/man8/tc-bpf.8.gz
error: No package owns /usr/share/man/man8/tc-cbq-details.8.gz
error: No package owns /usr/share/man/man8/tc-cbq.8.gz
error: No package owns /usr/share/man/man8/tc-cgroup.8.gz
error: No package owns /usr/share/man/man8/tc-choke.8.gz
error: No package owns /usr/share/man/man8/tc-codel.8.gz
error: No package owns /usr/share/man/man8/tc-connmark.8.gz
error: No package owns /usr/share/man/man8/tc-csum.8.gz
error: No package owns /usr/share/man/man8/tc-drr.8.gz
error: No package owns /usr/share/man/man8/tc-ematch.8.gz
error: No package owns /usr/share/man/man8/tc-flow.8.gz
error: No package owns /usr/share/man/man8/tc-flower.8.gz
error: No package owns /usr/share/man/man8/tc-fq.8.gz
error: No package owns /usr/share/man/man8/tc-fq_codel.8.gz
error: No package owns /usr/share/man/man8/tc-fw.8.gz
error: No package owns /usr/share/man/man8/tc-hfsc.8.gz
error: No package owns /usr/share/man/man8/tc-htb.8.gz
error: No package owns /usr/share/man/man8/tc-matchall.8.gz
error: No package owns /usr/share/man/man8/tc-mirred.8.gz
error: No package owns /usr/share/man/man8/tc-mqprio.8.gz
error: No package owns /usr/share/man/man8/tc-nat.8.gz
error: No package owns /usr/share/man/man8/tc-netem.8.gz
error: No package owns /usr/share/man/man8/tc-pedit.8.gz
error: No package owns /usr/share/man/man8/tc-pfifo.8.gz
error: No package owns /usr/share/man/man8/tc-pfifo_fast.8.gz
error: No package owns /usr/share/man/man8/tc-pie.8.gz
error: No package owns /usr/share/man/man8/tc-police.8.gz
error: No package owns /usr/share/man/man8/tc-prio.8.gz
error: No package owns /usr/share/man/man8/tc-red.8.gz
error: No package owns /usr/share/man/man8/tc-route.8.gz
error: No package owns /usr/share/man/man8/tc-sfb.8.gz
error: No package owns /usr/share/man/man8/tc-sfq.8.gz
error: No package owns /usr/share/man/man8/tc-simple.8.gz
error: No package owns /usr/share/man/man8/tc-skbedit.8.gz
error: No package owns /usr/share/man/man8/tc-stab.8.gz
error: No package owns /usr/share/man/man8/tc-tbf.8.gz
error: No package owns /usr/share/man/man8/tc-tcindex.8.gz
error: No package owns /usr/share/man/man8/tc-u32.8.gz
error: No package owns /usr/share/man/man8/tc-vlan.8.gz
error: No package owns /usr/share/man/man8/tc-xt.8.gz
error: No package owns /usr/share/man/man8/tc.8.gz
error: No package owns /usr/share/man/man8/tipc-bearer.8.gz
error: No package owns /usr/share/man/man8/tipc-link.8.gz
error: No package owns /usr/share/man/man8/tipc-media.8.gz
error: No package owns /usr/share/man/man8/tipc-nametable.8.gz
error: No package owns /usr/share/man/man8/tipc-node.8.gz
error: No package owns /usr/share/man/man8/tipc-socket.8.gz
error: No package owns /usr/share/man/man8/tipc.8.gz
error: No package owns /usr/share/tc/experimental.dist
error: No package owns /usr/share/tc/normal.dist
error: No package owns /usr/share/tc/pareto.dist
error: No package owns /usr/share/tc/paretonormal.dist

.. so my question remains, is it safe to delete these? ..

Last edited by bmentink (2017-01-15 18:42:08)

bmentink

Member

From: New Zealand

Registered: 2009-08-23

Posts: 442

Re: [SOLVED] Upgrade results in conflicting files for iproute2

OK ... so are you going to show any pacman -Qo output or not?

I did, at least give me a chance to do it in a script and post it, what's the hurry ...

My the way, my comment about "what the heck is broken with Pacman" was a bit  tongue-in-cheek" , we all aknow that pacman can't be at fault, software never has bugs, we never have to update software, it all just works ....

Last edited by bmentink (2017-01-15 18:48:00)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,785

Re: [SOLVED] Upgrade results in conflicting files for iproute2

Did you check the BUGS section of man pacman   

Come on everyone, I think we are all being reasonable -- we're just not communicating well.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

bmentink

Member

From: New Zealand

Registered: 2009-08-23

Posts: 442

Re: [SOLVED] Upgrade results in conflicting files for iproute2

You mean this:

BUGS
       Bugs? You must be kidding; there are no bugs in this software. But if we happen
       to be wrong, send us an email with as much detail as possible to
       pacman-dev@archlinux.org.

.. sure, good to see they have the same sense of humour ..
Still would like my question answered ..

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,785

Re: [SOLVED] Upgrade results in conflicting files for iproute2

Do you want iproute2 installed?

On my system

ewaller@turing ~ 1001 %pacman -Qo /etc/iproute2/bpf_pinning                                             
/etc/iproute2/bpf_pinning is owned by iproute2 4.9.0-1
ewaller@turing ~ 1002 %

What does pacman -Qi iproute2 say now?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

bmentink

Member

From: New Zealand

Registered: 2009-08-23

Posts: 442

Re: [SOLVED] Upgrade results in conflicting files for iproute2

 pacman -Qi iproute2
Name            : iproute2
Version         : 4.8.0-1
Description     : None
Architecture    : None
URL             : None
Licenses        : None
Groups          : None
Provides        : None
Depends On      : None
Optional Deps   : None
Required By     : netctl  networkmanager
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 0.00 B
Packager        : None
Build Date      : None
Install Date    : None
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Unknown

Looks like networkmanager needs it and Deepin needs network manager ..

Last edited by bmentink (2017-01-15 19:29:18)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 19,785

Re: [SOLVED] Upgrade results in conflicting files for iproute2

That is just wrong.   Reinstall iproute2 and, in this case, use the --force switch.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

bmentink

Member

From: New Zealand

Registered: 2009-08-23

Posts: 442

Re: [SOLVED] Upgrade results in conflicting files for iproute2

That is just wrong.   Reinstall iproute2 and, in this case, use the --force switch.

Awesome, that did the trick, upgrading as I type

... many thanks for the help