glibc update refusing to proceed. File ownership problem

geekinthesticks · 2012-07-17 09:29:35

OK so now problems with a second system. I have followed the steps in the Wiki and the output of:

grep '^lib/' /var/lib/pacman/local/*/files

/var/lib/pacman/local/glibc-2.15-12/files:lib/
/var/lib/pacman/local/glibc-2.15-12/files:lib/ld-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/ld-linux-x86-64.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libBrokenLocale-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libBrokenLocale.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libSegFault.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libanl-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libanl.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libc-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libc.so.6
/var/lib/pacman/local/glibc-2.15-12/files:lib/libcidn-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libcidn.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libcrypt-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libcrypt.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libdl-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libdl.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libm-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libm.so.6
/var/lib/pacman/local/glibc-2.15-12/files:lib/libmemusage.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnsl-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnsl.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_compat-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_compat.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_db-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_db.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_dns-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_dns.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_files-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_files.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_hesiod-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_hesiod.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_nis-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_nis.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_nisplus-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_nisplus.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libpcprofile.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libpthread-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libpthread.so.0
/var/lib/pacman/local/glibc-2.15-12/files:lib/libresolv-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libresolv.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/librt-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/librt.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libthread_db-1.0.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libthread_db.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libutil-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libutil.so.1

which seems identical to the system where I removed gcc and libtool.

The directory /lib/modules is empty. I have uninstalled gcc and libtool and I don't have gcc-objc installed. However, glibc refuses to install. As far as I can tell I have removed any packages that put stuff in /lib, so I am now stuck:)

Allan · 2012-07-17 09:36:54

geekinthesticks wrote:

The directory /lib/modules is empty

Delete it.

geekinthesticks · 2012-07-17 09:57:41

Allan wrote:

geekinthesticks wrote:
The directory /lib/modules is empty
Delete it.

Thank you so much, that worked.

t0m5k1 · 2012-07-17 12:04:16

thanks to dev & others for all the advice given.
advice i can pass on to other archers who face issues
read the arch news (regularly)
DO NOT FORCE
follow the instructions on the wiki i repeat with details [read the news & the wiki linked therein, understand what has been said re-read & follow]
any issue's keep running
grep '^lib/' /var/lib/pacman/local/*/files & removing packages until glibc is the only owner of lib
if folders within /lib/modules are owned by packages no longer present on the system then move them out of /lib
rerun pacman -Su after each run grep '^lib/' /var/lib/pacman/local/*/files
do this 1 package at a time until it works then just re-install what you removed & finally reboot

I am sooooooo glad I chose to install Arch, I see each issue now as a challenge or way to learn more.
With a little research in the wiki & forums I am managing to fix more on my own & when I compare this experience with ubuntu I am glad I changed

Thanks again dev's & community

sinojos · 2012-07-17 13:21:30

Found my post - it was merged with existing post - thought it was deleted.

jasonwryan wrote:

Merging with the stickied glibc thread...
Also, I don't recall seeing any advice to rm -rf lib/

"From wiki:
Unpackaged files
This means that you have files or folders still in /lib or pacman thinks a package apart from glibc still own /lib. You can see which package own files in /lib by using:
$ find /lib -exec pacman -Qo -- {} +
If any package apart from glibc is listed as owning a file, that package needs to be updated to install its files in /usr/lib. Any files unowned by a package should either be deleted or moved to /usr/lib and any directories within /lib need deleted (after they are empty...).
One common source of files in /lib is left overs from running depmod on a kernel update. For example:

error: No package owns /lib/modules/3.1.9-2-ARCH/modules.*
If no other files are in /lib/modules, you can safely remove that directory.
As stated above "any files unowned by a package should either be deleted or moved".

I had the folder /lib/modules/3.1.9-2-ARCH/modules.* as well as a number of files owned by glibc in /lib. The reason I backup the /lib folder completely prior to removal of any files, as a later reference if needed.

The developers need to seriously rethink how they proceed with updates that can produce such a catastrophic result as I have experienced. It is a simple matter to do a clean install if a system becomes irreparable, one of the great advantages of Linux, but to produce a situation were every single file on on any attached drive is removed is reprehensible. I am sure such a situation was not intended by the developers, but unfortunately it has happened.

Updating is always a risk, but it is the duty of the developers to mitigate that risk as much as possible. The only reason for using a specific flavor of Linux is for the package manger, the only real difference between Linux flavors, if it were not for the convenience of a package manager I would simply use LFS. Every distro has dealt with this very scenario, and those that are driven by the command line, have implemented features within updating at the command line to warn of impending disaster or provide instructions at the time of update via the console. No website visit necessary, or you are at least warned to visit the website for full instructions.

As it is now with Arch Linux, users are expected to visit the website each and every time an update is done, that is unrealistic, as checking every single day looking for the one or two times a year for notices is unrealistic. I deal with numerous distro's on a daily basis, and not one other has this problem with updates. Updating numerous machines with numerous flavors of Linux daily, if I had to go to each and every website each and everyday, that is all I would be doing, no time left for any real work.

If Arch Linux is going to stay a primarily cli driven distro, a method to inform users during update at the cli to possible problems must be implemented, as has been done with other distro's. A simple yes or no question could easily be implemented for when those specific circumstances necessitate action prior to update. To allow people to complete updates when there is necessary prior action, is the fault of the developers, since that can be changed very easily.

I believe using the excuse you didn't check the website first, is simply a cop-out by the developers, this type of situation has been handled competently by every other distro I use, why cannot Arch Linux?

Last edited by sinojos (2012-07-17 13:22:43)

jakobcreutzfeldt · 2012-07-17 13:56:39

sinojos wrote:

As it is now with Arch Linux, users are expected to visit the website each and every time an update is done, that is unrealistic, as checking every single day looking for the one or two times a year for notices is unrealistic. I deal with numerous distro's on a daily basis, and not one other has this problem with updates. Updating numerous machines with numerous flavors of Linux daily, if I had to go to each and every website each and everyday, that is all I would be doing, no time left for any real work.

The news page has an RSS feed...

Last edited by jakobcreutzfeldt (2012-07-17 13:56:51)

chamber · 2012-07-17 15:10:53

sinojos wrote:

Found my post - it was merged with existing post - thought it was deleted.
"From wiki:
Unpackaged files
This means that you have files or folders still in /lib or pacman thinks a package apart from glibc still own /lib. You can see which package own files in /lib by using:
$ find /lib -exec pacman -Qo -- {} +
If any package apart from glibc is listed as owning a file, that package needs to be updated to install its files in /usr/lib. Any files unowned by a package should either be deleted or moved to /usr/lib and any directories within /lib need deleted (after they are empty...).
One common source of files in /lib is left overs from running depmod on a kernel update. For example:
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.*
If no other files are in /lib/modules, you can safely remove that directory.
As stated above "any files unowned by a package should either be deleted or moved".

safely remove that directory being the key word. rm -rf * is never the brightest of moves.

sinojos wrote:

The developers need to seriously rethink how they proceed with updates that can produce such a catastrophic result as I have experienced. It is a simple matter to do a clean install if a system becomes irreparable, one of the great advantages of Linux, but to produce a situation were every single file on on any attached drive is removed is reprehensible. I am sure such a situation was not intended by the developers, but unfortunately it has happened.

I believe it was you who removed all the files not the devs....

sinojos wrote:

Updating is always a risk, but it is the duty of the developers to mitigate that risk as much as possible.

They do this with updating the news on the front page and in the mailing lists.

sinojos wrote:

As it is now with Arch Linux, users are expected to visit the website each and every time an update is done, that is unrealistic, as checking every single day looking for the one or two times a year for notices is unrealistic.

As said previously rss feeds and mailing lists mean you don't have to go to the website if you don't want to.

sinojos wrote:

I believe using the excuse you didn't check the website first, is simply a cop-out by the developers, this type of situation has been handled competently by every other distro I use, why cannot Arch Linux?

Blaming the devs is a cop out for not checking for any news.

ewaller · 2012-07-17 15:40:02

Moderator comment. This thread is not a blog. It is not the place to make assertions about imaginary responsibilities of volunteers or features they must implement.
This thread is about a complex update that requires more than the usual amount of tender loving care. It is a technical thread.

I fully understand the frustration this migration is causing. Your moderators are loosing a lot of sleep and time with their families over this.
Let's get it back on topic.

Last edited by ewaller (2012-07-17 15:40:36)

Trilby · 2012-07-17 15:41:22

sinojos wrote:

As it is now with Arch Linux, users are expected to visit the website each and every time an update is done, that is unrealistic, as checking every single day looking for the one or two times a year for notices is unrealistic.

I'm pretty sure it was earlier in this thread where I said I'd agree with part of the point of view you just shared. I certainly don't check the news before every update. Most updates proceed without a hitch. However, at the first sign of a hitch, I do check to see if there is anything in the news about it. I check the news after entering `pacman -Syu` and seeing any unusual or unexpected prompt asking how I'd like to continue.

Pacman gives you the choice; the "devs" and community give you the information needed to make an intelligent choice. If you willfully ignore that information and plow ahead with a random-guess at one of pacman's prompts ... well, that is your choice, but why would you blame anyone else for the outcome.

killnine · 2012-07-17 16:07:19

Hello,

I am getting lib / glib conflict errrors, and I do not fully understand.

I am using this reference: https://wiki.archlinux.org/index.php/De … iki:usrlib
and focusing on issue 2 as

 pacman -Syu --ignore glibc

does complete successfully.

Result:

[root@clc ~]# grep '^lib/' /var/lib/pacman/local/*/files
/var/lib/pacman/local/glibc-2.15-12/files:lib/
/var/lib/pacman/local/glibc-2.15-12/files:lib/ld-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/ld-linux-x86-64.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libBrokenLocale-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libBrokenLocale.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libSegFault.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libanl-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libanl.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libc-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libc.so.6
/var/lib/pacman/local/glibc-2.15-12/files:lib/libcidn-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libcidn.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libcrypt-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libcrypt.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libdl-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libdl.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libm-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libm.so.6
/var/lib/pacman/local/glibc-2.15-12/files:lib/libmemusage.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnsl-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnsl.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_compat-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_compat.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_db-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_db.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_dns-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_dns.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_files-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_files.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_hesiod-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_hesiod.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_nis-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_nis.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_nisplus-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libnss_nisplus.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/libpcprofile.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libpthread-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libpthread.so.0
/var/lib/pacman/local/glibc-2.15-12/files:lib/libresolv-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libresolv.so.2
/var/lib/pacman/local/glibc-2.15-12/files:lib/librt-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/librt.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libthread_db-1.0.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libthread_db.so.1
/var/lib/pacman/local/glibc-2.15-12/files:lib/libutil-2.15.so
/var/lib/pacman/local/glibc-2.15-12/files:lib/libutil.so.1
/var/lib/pacman/local/lib32-glibc-2.14.1-2/files:lib/
/var/lib/pacman/local/lib32-glibc-2.14.1-2/files:lib/ld-linux.so.2

error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/bridge/netfilter/ebt_mark_m.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/bridge/netfilter/ebt_snat.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/bridge/netfilter/ebt_nflog.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/bridge/netfilter/ebt_pkttype.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/bridge/netfilter/ebt_802_3.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/rfkill'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/rfkill/rfkill.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/rfkill/rfkill-regulator.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/phonet'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/phonet/pn_pep.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/phonet/phonet.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/xfrm'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/xfrm/xfrm_ipcomp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/xfrm/xfrm_user.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/l2tp'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/l2tp/l2tp_netlink.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/l2tp/l2tp_ip.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/l2tp/l2tp_eth.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/l2tp/l2tp_ppp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/l2tp/l2tp_core.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/ipv4'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/tcp_bic.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/tcp_scalable.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/tcp_highspeed.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/xfrm4_mode_transport.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/esp4.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/ah4.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/ipip.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/tcp_vegas.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/tunnel4.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/tcp_westwood.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/tcp_veno.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/tcp_illinois.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/gre.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/xfrm4_mode_beet.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/tcp_lp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/ipcomp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/tcp_hybla.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/tcp_yeah.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/tcp_htcp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/ip_gre.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/ipt_CLUSTERIP.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat_proto_gre.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/ipt_ecn.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat_proto_udplite.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/ip_tables.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_conntrack_ipv4.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/ip_queue.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/iptable_nat.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat_pptp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_defrag_ipv4.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat_irc.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/ipt_ah.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/iptable_mangle.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/arpt_mangle.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/arp_tables.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat_tftp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/iptable_raw.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/arptable_filter.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/ipt_ULOG.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat_h323.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/ipt_NETMAP.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/iptable_security.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat_sip.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat_snmp_basic.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/iptable_filter.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat_proto_dccp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat_proto_sctp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/ipt_REDIRECT.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/ipt_LOG.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/ipt_ECN.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/ipt_REJECT.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/ipt_MASQUERADE.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat_ftp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/netfilter/nf_nat_amanda.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/xfrm4_tunnel.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv4/xfrm4_mode_tunnel.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/nfc'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/nfc/nfc.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/nfc/nci'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/nfc/nci/nci.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/wimax'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/wimax/wimax.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/ipx'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipx/ipx.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/wireless'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/wireless/lib80211_crypt_ccmp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/wireless/lib80211_crypt_tkip.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/wireless/lib80211_crypt_wep.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/wireless/lib80211.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/wireless/cfg80211.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/bluetooth'
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/bluetooth/hidp'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/bluetooth/hidp/hidp.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/bluetooth/rfcomm'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/bluetooth/rfcomm/rfcomm.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/bluetooth/bnep'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/bluetooth/bnep/bnep.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/bluetooth/bluetooth.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/8021q'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/8021q/8021q.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/sctp'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/sctp/sctp.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/mac80211'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/mac80211/mac80211.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/llc'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/llc/llc.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/llc/llc2.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/ipv6'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/sit.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/xfrm6_mode_beet.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/ip6_tunnel.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/ah6.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/xfrm6_mode_transport.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/mip6.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/tunnel6.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/xfrm6_mode_tunnel.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/ipcomp6.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/xfrm6_tunnel.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/xfrm6_mode_ro.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/esp6.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6t_frag.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6t_LOG.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6table_filter.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6_tables.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6t_ah.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/nf_conntrack_ipv6.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6t_REJECT.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6_queue.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6table_raw.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6t_eui64.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6table_mangle.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6t_ipv6header.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6t_mh.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6table_security.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/nf_defrag_ipv6.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6t_rt.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/ipv6/netfilter/ip6t_hbh.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/sunrpc'
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/sunrpc/auth_gss'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/sunrpc/auth_gss/rpcsec_gss_krb5.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/sunrpc/sunrpc.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/netfilter'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_connmark.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/x_tables.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_connbytes.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_broadcast.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_TPROXY.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_sip.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_amanda.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_hashlimit.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_dscp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_TRACE.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_tcpmss.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset/ip_set.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset/ip_set_hash_netport.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset/ip_set_hash_ipport.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset/ip_set_bitmap_ipmac.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset/ip_set_hash_net.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset/ip_set_bitmap_port.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset/ip_set_bitmap_ip.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset/ip_set_hash_ip.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset/ip_set_hash_netiface.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset/ip_set_list_set.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset/ip_set_hash_ipportip.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipset/ip_set_hash_ipportnet.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_realm.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_mark.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_NFQUEUE.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_NOTRACK.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_state.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_h323.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_conntrack.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_mac.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_time.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_TCPOPTSTRIP.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_addrtype.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_LED.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nfnetlink_queue.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_comment.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_sane.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_length.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_proto_udplite.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_DSCP.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_proto_sctp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_TEE.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_HL.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_physdev.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_rateest.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_connlimit.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_tftp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_helper.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_proto_gre.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_ipvs.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_tproxy_core.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nfnetlink_log.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_RATEEST.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_devgroup.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_cpu.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_CLASSIFY.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_SECMARK.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_snmp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_sctp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_pkttype.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_CT.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_policy.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_IDLETIMER.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_socket.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_esp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_netbios_ns.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_limit.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nfnetlink.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_AUDIT.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_TCPMSS.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_CONNSECMARK.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_quota.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_osf.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_hl.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_recent.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_u32.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_owner.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs_nq.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs_lblc.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs_wrr.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs_wlc.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs_lc.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs_pe_sip.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs_sh.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs_ftp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs_rr.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs_lblcr.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs_dh.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/ipvs/ip_vs_sed.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_dccp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_proto_dccp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_ftp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_NFLOG.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_tcpudp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_iprange.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_irc.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_set.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_string.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_statistic.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_pptp.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/nf_conntrack_netlink.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_CHECKSUM.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_cluster.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/netfilter/xt_multiport.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/core'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/core/pktgen.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/net/atm'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/atm/clip.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/atm/pppoatm.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/atm/br2684.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/atm/lec.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/atm/atm.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/net/atm/mpoa.ko.gz
error: cannot determine ownership of directory '/lib/modules/3.2.11-1-ARCH/kernel/mm'
error: No package owns /lib/modules/3.2.11-1-ARCH/kernel/mm/hwpoison-inject.ko.gz
error: No package owns /lib/modules/3.2.11-1-ARCH/build
error: No package owns /lib/modules/3.2.11-1-ARCH/extramodules
error: No package owns /lib/modules/3.2.11-1-ARCH/modules.alias
error: No package owns /lib/modules/3.2.11-1-ARCH/modules.symbols
error: No package owns /lib/modules/3.2.11-1-ARCH/modules.devname
error: No package owns /lib/modules/3.2.11-1-ARCH/modules.builtin
error: cannot determine ownership of directory '/lib/modules/3.2.6-2-ARCH'
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.softdep
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.dep
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.alias.bin
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.symbols.bin
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.builtin.bin
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.dep.bin
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.alias
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.symbols
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.devname
/lib/libc.so.6 is owned by glibc 2.15-12

So I am thinking I need to move /lib/modules/3.2.6-2-ARCH/ to /usr/lib/ ? Can someone verify that is the right move please?

I really can't afford to break this system and am hoping someone can help me out before I make a move that may ruin me.

Thanks in advance

Last edited by killnine (2012-07-17 16:12:30)

ebal · 2012-07-17 16:13:13

You can remove everything below /lib/modules

rm -rf /lib/modules/*

Then follow the wiki link

and after all these (before you reboot)

# pacman -S linux

killnine · 2012-07-17 17:01:37

ebal wrote:

You can remove everything below /lib/modules
rm -rf /lib/modules/* 
Then follow the wiki link
and after all these (before you reboot)
# pacman -S linux

Did the remove, then re did

pacman -Syu --ignore glibc

and get 'nothing to do'

but the -Su still fails on '/lib exists'

progandy · 2012-07-17 17:29:40

It seems you have an old lib32-glibc installed. Either enable the multilib repository and update or remove it. You should also remove the folder /lib/modules, but NOT /lib.

Last edited by progandy (2012-07-17 17:30:40)

jasonwryan · 2012-07-17 17:31:52

Merging with the Great glibc thread of '12...

Onyros · 2012-07-17 18:13:48

I actually did the same mistake many did, not because I didn't read or even receive an email with instructions on how to proceed - but because I was drunk when I read them. So, the following day, I did force the update, having forgotten everything.

At least recovery was easy enough, mostly thanks to mods and devs. It was an ugly update, you guys expected it, but I think it's fair to say *Congrats* on how you're dealing with this torrent of complaints... Mostly from dudes who don't even have the excuse of being drunk.

killnine · 2012-07-17 18:26:23

progandy wrote:

It seems you have an old lib32-glibc installed. Either enable the multilib repository and update or remove it. You should also remove the folder /lib/modules, but NOT /lib.

I enabled multilib and did

pacman -Syyu --ignore glibc

then

pacman -Su

and system is up to date.

Next I startx and gnome fails with a bunch of glibc output erros.

X.Org X Server 1.12.3
Release Date: 2012-07-09
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.4.4-3-ARCH x86_64 
Current Operating System: Linux clc 3.4.4-3-ARCH #1 SMP PREEMPT Tue Jul 3 14:36:44 UTC 2012 x86_64
Kernel command line: root=/dev/sda5 ro acpi=noirq i915.i915_enable_rc6=1
Build Date: 09 July 2012  03:59:39PM
 
Current version of pixman: 0.26.2
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 17 10:32:19 2012
(==) Using config directory: "/etc/X11/xorg.conf.d"
gnome-session[568]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name
gnome-session[568]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name
GNOME_KEYRING_CONTROL=/root/.cache/keyring-p2MtFh
GNOME_KEYRING_PID=593
GNOME_KEYRING_CONTROL=/root/.cache/keyring-p2MtFh
GPG_AGENT_INFO=/root/.cache/keyring-p2MtFh/gpg:0:1
GNOME_KEYRING_CONTROL=/root/.cache/keyring-p2MtFh
GPG_AGENT_INFO=/root/.cache/keyring-p2MtFh/gpg:0:1
SSH_AUTH_SOCK=/root/.cache/keyring-p2MtFh/ssh

(gnome-settings-daemon:585): libupower-glib-WARNING **: Couldn't enumerate devices: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success

(gnome-settings-daemon:585): power-plugin-WARNING **: failed to get device list: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success

** (gnome-settings-daemon:585): WARNING **: Failed to connect context: OK

** (gnome-settings-daemon:585): WARNING **: cannot connect to ConsoleKit: Error calling StartServiceByName for org.freedesktop.ConsoleKit: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success

(gnome-settings-daemon:585): color-plugin-WARNING **: failed to connect to colord: Error calling StartServiceByName for org.freedesktop.ColorManager: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Permission denied

(gnome-settings-daemon:585): power-plugin-WARNING **: Could not connect to UPower: Error calling StartServiceByName for org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success

(gnome-settings-daemon:585): power-plugin-WARNING **: Could not connect to UPower: Error calling StartServiceByName for org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success

** (gnome-settings-daemon:585): WARNING **: cannot connect to ConsoleKit: Error calling StartServiceByName for org.freedesktop.ConsoleKit: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success

(gnome-settings-daemon:585): media-keys-plugin-WARNING **: Failed to get proxy for upower: Error calling StartServiceByName for org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
Failed to play sound: Not available
Initializing tracker-store...
Tracker-Message: Setting up monitor for changes to config file:'/root/.config/tracker/tracker-store.cfg'
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
Initializing tracker-miner-fs...
Tracker-Message: Setting up monitor for changes to config file:'/root/.config/tracker/tracker-miner-fs.cfg'
W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).

** (nm-applet:643): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
** Message: applet now removed from the notification area

** (nm-applet:643): WARNING **: fetch_connections_done: error fetching connections: (23) Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success.

** (nm-applet:643): WARNING **: Failed to register as an agent: (23) Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
Starting log:
  File:'/root/.local/share/tracker/tracker-miner-fs.log'
Tracker-Message: Setting up monitor for changes to config file:'/root/.config/tracker/tracker-store.cfg'
Starting log:
  File:'/root/.local/share/tracker/tracker-store.log'

(gnome-shell:632): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
Window manager warning: Log level 16: Could not initialize NMClient /org/freedesktop/NetworkManager: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success

(gnome-shell:632): AccountsService-WARNING **: Failed to create accounts proxy: Error calling StartServiceByName for org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
Window manager warning: Log level 16: Error getting session for the process we are in: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success (g-dbus-error-quark 23)
** Message: applet now embedded in the notification area
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!

(tracker-miner-fs:640): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported

(gnome-shell:632): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion `G_IS_DBUS_PROXY (proxy)' failed
**
AccountsService:ERROR:act-user-manager.c:2156:load_users: assertion failed: (manager->priv->accounts_proxy != NULL)
** Message: applet now removed from the notification area
gnome-session[568]: WARNING: Application 'gnome-shell.desktop' killed by signal 6
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
(gnome-shell:750): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
Window manager warning: Log level 16: Could not initialize NMClient /org/freedesktop/NetworkManager: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
(gnome-shell:750): AccountsService-WARNING **: Failed to create accounts proxy: Error calling StartServiceByName for org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
Window manager warning: Log level 16: Error getting session for the process we are in: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success (g-dbus-error-quark 23)
** Message: applet now embedded in the notification area
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
(gnome-shell:750): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion `G_IS_DBUS_PROXY (proxy)' failed
**
AccountsService:ERROR:act-user-manager.c:2156:load_users: assertion failed: (manager->priv->accounts_proxy != NULL)
** Message: applet now removed from the notification area
gnome-session[568]: WARNING: Application 'gnome-shell.desktop' killed by signal 6
gnome-session[568]: WARNING: App 'gnome-shell.desktop' respawning too quickly
gnome-session[568]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name
** Message: Starting applet secret agent because GNOME Shell disappeared
** (nm-applet:643): WARNING **: Failed to register as an agent: (23) Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
gnome-session[568]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name
(gnome-settings-daemon:585): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(gnome-settings-daemon:585): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
[1342535546,000,xklavier.c:xkl_engine_start_listen/] 	The backend does not require manual layout management - but it is provided by the application
xinit: connection to X server lost

Received signal:1->'Hangup'
waiting for X server to shut down 
Received signal:1->'Hangup'
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Received signal:15->'Terminated'g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Received signal:15->'Terminated'
(tracker-miner-fs:640): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
(tracker-miner-fs:640): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
OK
cker-miner-fs:640): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
OK
Server terminated successfully (0). Closing log file.

I am also wondering, do I disable multilib in pacman.conf now ?

Last edited by killnine (2012-07-17 18:47:23)

Barrucadu · 2012-07-17 18:50:48

Those are glib errors, not glibc errors. Additionally, many of the messages seem dbus-related, do you have dbus running?

VisualPaul · 2012-07-17 18:54:09

Hello, everyone!
Accidentally I did the following thing

paul@paul-laptop-x86-64:~$ sudo pacman -Syu  --force
Password: 
Sorry, try again.
Password: 
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets (67): automake-1.12.2-1  bash-4.2.036-1  binutils-2.22-9  chromium-20.0.1132.57-1  eclipse-4.2-1  eclipse-cdt-8.1.0-2  git-1.7.11.2-1  glibc-2.16.0-2
              gnome-screensaver-3.4.3-1  gpm-1.20.6-10  gvim-7.3.600-1  hwids-20120711-1  hyphen-2.8.5-1  iputils-20101006-4  kdebase-workspace-4.8.4-3
              khrplatform-devel-8.0.4-1  kmod-9-2  lib32-glibc-2.16.0-2  lib32-libgl-8.0.4-1  lib32-libglapi-8.0.4-1  lib32-mesa-8.0.4-1  libegl-8.0.4-1
              libglapi-8.0.4-1  libgles-8.0.4-1  libreoffice-af-3.5.5-1  libreoffice-base-3.5.5-1  libreoffice-calc-3.5.5-1  libreoffice-common-3.5.5-1
              libreoffice-draw-3.5.5-1  libreoffice-en-US-3.5.5-1  libreoffice-gnome-3.5.5-1  libreoffice-impress-3.5.5-1  libreoffice-kde4-3.5.5-1
              libreoffice-math-3.5.5-1  libreoffice-postgresql-connector-3.5.5-1  libreoffice-sdk-3.5.5-1  libreoffice-sdk-doc-3.5.5-1  libreoffice-writer-3.5.5-1
              libsystemd-186-2  linux-3.4.4-3  linux-docs-3.4.4-3  linux-headers-3.4.4-3  lirc-utils-1:0.9.0-20  mesa-8.0.4-1  nettle-2.5-1  nvidia-302.17-2
              pcre-8.31-1  perl-error-0.17018-1  perl-xml-simple-2.20-1  phonon-gstreamer-4.6.1-1  pkg-config-0.27-1  pkgtools-24-2  poppler-0.20.2-1
              poppler-glib-0.20.2-1  poppler-qt-0.20.2-1  procps-ng-3.3.3-3  readline-6.2.003-2  syslog-ng-3.3.5-2  systemd-186-2  systemd-arch-units-20120704-1
              systemd-tools-186-2  twisted-12.1.0-1  usbutils-006-1  util-linux-2.21.2-5  vim-runtime-7.3.600-1  virtualbox-4.1.18-2  virtualbox-modules-4.1.18-2

Total Installed Size:   1319.41 MiB
Net Upgrade Size:       59.38 MiB

Proceed with installation? [Y/n] 
(67/67) checking package integrity                                                                   [############################################################] 100%
(67/67) loading package files                                                                        [############################################################] 100%
(67/67) checking available disk space                                                                [############################################################] 100%
( 1/67) upgrading glibc                                                                              [############################################################] 100%
error: extract: not overwriting dir with file lib
error: problem occurred while upgrading glibc
call to execv failed (No such file or directory)
error: command failed to execute correctly
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.

After that I typed 'ls' and got:

bash: /bin/ls: No such file or directory

Actually I cannot now start any program. Shell, coreutils, opera - all of them aren't starting. I've got a running python(I accidentally killed it), pypy, shell, and so one.
Both python and shell's echo /bin/* shows that /bin/ls exists
I did stat via python and found out that ls access mode is 0755 - looks correct. I am even possible to open /bin/ls and read the ELF header.
I don't want to reboot the computer because I am not sure it is going to work after the reboot. Also I'm using linux-bfs on amd64 which may be important.
Does anybody have any ideas?

Last edited by VisualPaul (2012-07-17 18:55:18)

jasonwryan · 2012-07-17 18:59:34

Read the news and the wiki page it links to.

(And never use -Syuf... )

Merging with the stickied glibc thread

Awebb · 2012-07-17 19:00:31

It seems to be mentionable, that one should update pacman, before one follows that two step program.

By the way: I used the force, Luke. I did something time critical and needed a package on my fileserver, so I --force'd the process. That was a bad idea. Never do that. Never ever.

Onyros · 2012-07-17 19:10:35

Awebb wrote:

It seems to be mentionable, that one should update pacman, before one follows that two step program.
By the way: I used the force, Luke. I did something time critical and needed a package on my fileserver, so I --force'd the process. That was a bad idea. Never do that. Never ever.

I feel your pain, brother. The dark side wasn't cool, at all. Gladly the recovery shell solution (break=postmount on kernel line) and lib symlinking (after emptying) were enough for me. All other Arch machines (even virtual) experienced very clean and informed updates after the first, and most important, production machine.

killnine · 2012-07-17 19:21:25

Barrucadu wrote:

Those are glib errors, not glibc errors. Additionally, many of the messages seem dbus-related, do you have dbus running?

I do... Other ideas?

progandy · 2012-07-17 19:23:48

Onyros wrote:

I feel your pain, brother. The dark side wasn't cool, at all. Gladly the recovery shell solution (break=postmount on kernel line) and lib symlinking (after emptying) were enough for me. All other Arch machines (even virtual) experienced very clean and informed updates after the first, and most important, production machine.

If you hate to shutdown a crippled system and you still have an open shell and busybox, you can use that, too.
You can also avoid the shutdown if you still have a shell and something to download and chmod files (e.g. file browser, python: os.chmod, ...) Then download busybox and make it executable.
Steps for busybox if the forced glibc install is only missing the symlink for /lib

# Start busybox in your shell
/bin/busybox sh
# Now open busybox as root
su -s /bin/busybox root sh"
# Now check if /usr/lib/ld-linux.so.2 exists (64bit with -x86-64)
ls -l /usr/lib/ld-*
# if not, have fun with manual extraction of pacakges
#...
# If yes, then move /lib to a backup and set a symlink 
mv /lib /lib.backup
ln -s usr/lib /lib
# Reinstall glibc, now everything should work again.
pacman -S glibc
# Check if any files are missing, if yes reinstall the listed packages
LC_ALL=C sudo pacman -Qk | grep -v ", 0 miss"

Last edited by progandy (2012-07-17 19:31:33)

stevepa · 2012-07-17 19:41:59

I think this entire /lib episode should at least drive home the importance of system backups.

mini · 2012-07-17 22:08:20

grep '^lib/' /var/lib/pacman/local/*/files
/var/lib/pacman/local/glibc-2.15-11/files:lib/
/var/lib/pacman/local/glibc-2.15-11/files:lib/ld-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/ld-linux-x86-64.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libBrokenLocale-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libBrokenLocale.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libSegFault.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libanl-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libanl.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libc-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libc.so.6
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcidn-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcidn.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcrypt-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libcrypt.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libdl-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libdl.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libm-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libm.so.6
/var/lib/pacman/local/glibc-2.15-11/files:lib/libmemusage.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnsl-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnsl.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_compat-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_compat.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_db-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_db.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_dns-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_dns.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_files-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_files.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_hesiod-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_hesiod.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nis-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nis.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nisplus-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libnss_nisplus.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/libpcprofile.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libpthread-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libpthread.so.0
/var/lib/pacman/local/glibc-2.15-11/files:lib/libresolv-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libresolv.so.2
/var/lib/pacman/local/glibc-2.15-11/files:lib/librt-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/librt.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libthread_db-1.0.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libthread_db.so.1
/var/lib/pacman/local/glibc-2.15-11/files:lib/libutil-2.15.so
/var/lib/pacman/local/glibc-2.15-11/files:lib/libutil.so.1

and still can not upgrade glibc

Arch Linux

#151 2012-07-17 09:29:35

Re: glibc update refusing to proceed. File ownership problem

#152 2012-07-17 09:36:54

Re: glibc update refusing to proceed. File ownership problem

#153 2012-07-17 09:57:41

Re: glibc update refusing to proceed. File ownership problem

#154 2012-07-17 12:04:16

Re: glibc update refusing to proceed. File ownership problem

#155 2012-07-17 13:21:30

Re: glibc update refusing to proceed. File ownership problem

#156 2012-07-17 13:56:39

Re: glibc update refusing to proceed. File ownership problem

#157 2012-07-17 15:10:53

Re: glibc update refusing to proceed. File ownership problem

#158 2012-07-17 15:40:02

Re: glibc update refusing to proceed. File ownership problem

#159 2012-07-17 15:41:22

Re: glibc update refusing to proceed. File ownership problem

#160 2012-07-17 16:07:19

Re: glibc update refusing to proceed. File ownership problem

#161 2012-07-17 16:13:13

Re: glibc update refusing to proceed. File ownership problem

#162 2012-07-17 17:01:37

Re: glibc update refusing to proceed. File ownership problem

#163 2012-07-17 17:29:40

Re: glibc update refusing to proceed. File ownership problem

#164 2012-07-17 17:31:52

Re: glibc update refusing to proceed. File ownership problem

#165 2012-07-17 18:13:48

Re: glibc update refusing to proceed. File ownership problem

#166 2012-07-17 18:26:23

Re: glibc update refusing to proceed. File ownership problem

#167 2012-07-17 18:50:48

Re: glibc update refusing to proceed. File ownership problem

#168 2012-07-17 18:54:09

Re: glibc update refusing to proceed. File ownership problem

#169 2012-07-17 18:59:34

Re: glibc update refusing to proceed. File ownership problem

#170 2012-07-17 19:00:31

Re: glibc update refusing to proceed. File ownership problem

#171 2012-07-17 19:10:35

Re: glibc update refusing to proceed. File ownership problem

#172 2012-07-17 19:21:25

Re: glibc update refusing to proceed. File ownership problem

#173 2012-07-17 19:23:48

Re: glibc update refusing to proceed. File ownership problem

#174 2012-07-17 19:41:59

Re: glibc update refusing to proceed. File ownership problem

#175 2012-07-17 22:08:20

Re: glibc update refusing to proceed. File ownership problem

Board footer