I have followed all there is to follow tried all i can find to try yet
i am still getting
error: failed to commit transaction (conflicting files)
glibc: /lib exists in filesystem
glibc: /usr/lib/ld-2.16.so exists in filesystem
glibc: /usr/lib/ld-linux-x86-64.so.2 exists in filesystem
glibc: /usr/lib/libBrokenLocale-2.16.so exists in filesystem
glibc: /usr/lib/libBrokenLocale.so.1 exists in filesystem
glibc: /usr/lib/libSegFault.so exists in filesystem
glibc: /usr/lib/libanl-2.16.so exists in filesystem
glibc: /usr/lib/libanl.so.1 exists in filesystem
glibc: /usr/lib/libc-2.16.so exists in filesystem
glibc: /usr/lib/libc.so.6 exists in filesystem
glibc: /usr/lib/libcidn-2.16.so exists in filesystem
glibc: /usr/lib/libcidn.so.1 exists in filesystem
glibc: /usr/lib/libcrypt-2.16.so exists in filesystem
glibc: /usr/lib/libcrypt.so.1 exists in filesystem
glibc: /usr/lib/libdl-2.16.so exists in filesystem
glibc: /usr/lib/libdl.so.2 exists in filesystem
glibc: /usr/lib/libm-2.16.so exists in filesystem
glibc: /usr/lib/libm.so.6 exists in filesystem
glibc: /usr/lib/libmemusage.so exists in filesystem
glibc: /usr/lib/libnsl-2.16.so exists in filesystem
glibc: /usr/lib/libnsl.so.1 exists in filesystem
glibc: /usr/lib/libnss_compat-2.16.so exists in filesystem
glibc: /usr/lib/libnss_compat.so.2 exists in filesystem
glibc: /usr/lib/libnss_db-2.16.so exists in filesystem
glibc: /usr/lib/libnss_db.so.2 exists in filesystem
glibc: /usr/lib/libnss_dns-2.16.so exists in filesystem
glibc: /usr/lib/libnss_dns.so.2 exists in filesystem
glibc: /usr/lib/libnss_files-2.16.so exists in filesystem
glibc: /usr/lib/libnss_files.so.2 exists in filesystem
glibc: /usr/lib/libnss_hesiod-2.16.so exists in filesystem
glibc: /usr/lib/libnss_hesiod.so.2 exists in filesystem
glibc: /usr/lib/libnss_nis-2.16.so exists in filesystem
glibc: /usr/lib/libnss_nis.so.2 exists in filesystem
glibc: /usr/lib/libnss_nisplus-2.16.so exists in filesystem
glibc: /usr/lib/libnss_nisplus.so.2 exists in filesystem
glibc: /usr/lib/libpcprofile.so exists in filesystem
glibc: /usr/lib/libpthread-2.16.so exists in filesystem
glibc: /usr/lib/libpthread.so.0 exists in filesystem
glibc: /usr/lib/libresolv-2.16.so exists in filesystem
glibc: /usr/lib/libresolv.so.2 exists in filesystem
glibc: /usr/lib/librt-2.16.so exists in filesystem
glibc: /usr/lib/librt.so.1 exists in filesystem
glibc: /usr/lib/libthread_db-1.0.so exists in filesystem
glibc: /usr/lib/libthread_db.so.1 exists in filesystem
glibc: /usr/lib/libutil-2.16.so exists in filesystem
glibc: /usr/lib/libutil.so.1 exists in filesystem
Errors occurred, no packages were upgraded.
What has got to be done to solve this once and for all ..
lib is a symlink to usr/lib..
error: cannot determine ownership of directory '/lib/akonadi'
error: cannot determine ownership of directory '/lib/alsa-lib'
error: cannot determine ownership of directory '/lib/ao'
/lib/apr.exp is owned by apr 1.4.6-1
error: cannot determine ownership of directory '/lib/apr-util-1'
/lib/aprutil.exp is owned by apr-util 1.4.1-1
/lib/aspell is owned by aspell 0.60.6.1-1
error: cannot determine ownership of directory '/lib/aspell-0.60'
error: cannot determine ownership of directory '/lib/atkmm-1.6'
/lib/attica_kde.so is owned by kdebase-runtime 4.8.4-2
And
grep '^lib/' /var/lib/pacman/local/*/files | grep -v glibc
Generates absolutely nothing
so what gives ..
Pete .
--
Linux 7-of-9 3.4.4-3-ARCH #1 SMP PREEMPT Tue Jul 3 14:36:44 UTC 2012
x86_64 GNU/Linux
07-17-2012, 03:27 PM
Tom Gundersen
Still Glibc problems
On Tue, Jul 17, 2012 at 5:19 PM, P .NIKOLIC <p.nikolic1@btinternet.com> wrote:
> I have followed all there is to follow tried all i can find to try yet
> i am still getting
>
> error: failed to commit transaction (conflicting files)
> glibc: /lib exists in filesystem
> glibc: /usr/lib/ld-2.16.so exists in filesystem
> glibc: /usr/lib/ld-linux-x86-64.so.2 exists in filesystem
> glibc: /usr/lib/libBrokenLocale-2.16.so exists in filesystem
> glibc: /usr/lib/libBrokenLocale.so.1 exists in filesystem
> glibc: /usr/lib/libSegFault.so exists in filesystem
> glibc: /usr/lib/libanl-2.16.so exists in filesystem
> glibc: /usr/lib/libanl.so.1 exists in filesystem
> glibc: /usr/lib/libc-2.16.so exists in filesystem
> glibc: /usr/lib/libc.so.6 exists in filesystem
> glibc: /usr/lib/libcidn-2.16.so exists in filesystem
> glibc: /usr/lib/libcidn.so.1 exists in filesystem
> glibc: /usr/lib/libcrypt-2.16.so exists in filesystem
> glibc: /usr/lib/libcrypt.so.1 exists in filesystem
> glibc: /usr/lib/libdl-2.16.so exists in filesystem
> glibc: /usr/lib/libdl.so.2 exists in filesystem
> glibc: /usr/lib/libm-2.16.so exists in filesystem
> glibc: /usr/lib/libm.so.6 exists in filesystem
> glibc: /usr/lib/libmemusage.so exists in filesystem
> glibc: /usr/lib/libnsl-2.16.so exists in filesystem
> glibc: /usr/lib/libnsl.so.1 exists in filesystem
> glibc: /usr/lib/libnss_compat-2.16.so exists in filesystem
> glibc: /usr/lib/libnss_compat.so.2 exists in filesystem
> glibc: /usr/lib/libnss_db-2.16.so exists in filesystem
> glibc: /usr/lib/libnss_db.so.2 exists in filesystem
> glibc: /usr/lib/libnss_dns-2.16.so exists in filesystem
> glibc: /usr/lib/libnss_dns.so.2 exists in filesystem
> glibc: /usr/lib/libnss_files-2.16.so exists in filesystem
> glibc: /usr/lib/libnss_files.so.2 exists in filesystem
> glibc: /usr/lib/libnss_hesiod-2.16.so exists in filesystem
> glibc: /usr/lib/libnss_hesiod.so.2 exists in filesystem
> glibc: /usr/lib/libnss_nis-2.16.so exists in filesystem
> glibc: /usr/lib/libnss_nis.so.2 exists in filesystem
> glibc: /usr/lib/libnss_nisplus-2.16.so exists in filesystem
> glibc: /usr/lib/libnss_nisplus.so.2 exists in filesystem
> glibc: /usr/lib/libpcprofile.so exists in filesystem
> glibc: /usr/lib/libpthread-2.16.so exists in filesystem
> glibc: /usr/lib/libpthread.so.0 exists in filesystem
> glibc: /usr/lib/libresolv-2.16.so exists in filesystem
> glibc: /usr/lib/libresolv.so.2 exists in filesystem
> glibc: /usr/lib/librt-2.16.so exists in filesystem
> glibc: /usr/lib/librt.so.1 exists in filesystem
> glibc: /usr/lib/libthread_db-1.0.so exists in filesystem
> glibc: /usr/lib/libthread_db.so.1 exists in filesystem
> glibc: /usr/lib/libutil-2.16.so exists in filesystem
> glibc: /usr/lib/libutil.so.1 exists in filesystem
> Errors occurred, no packages were upgraded.
>
> What has got to be done to solve this once and for all ..
> lib is a symlink to usr/lib..
Hm.... how did /lib end up as a symlink to /usr/lib without those
files being owned by glibc? Did you just copy it over manually and
create the link yourself?
-t
07-17-2012, 04:01 PM
"P .NIKOLIC"
Still Glibc problems
On Tue, 17 Jul 2012 17:27:35 +0200
Tom Gundersen <teg@jklm.no> wrote:
Pruned
>
> Hm.... how did /lib end up as a symlink to /usr/lib without those
> files being owned by glibc? Did you just copy it over manually and
> create the link yourself?
>
> -t
Quite easily
I followed what was on the Arch web site and the links therein
nothing fancy
Pete .
--
Linux 7-of-9 3.4.4-3-ARCH #1 SMP PREEMPT Tue Jul 3 14:36:44 UTC 2012
x86_64 GNU/Linux
07-17-2012, 04:27 PM
Guus Snijders
Still Glibc problems
Op 17 jul. 2012 18:01 schreef "P .NIKOLIC" <p.nikolic1@btinternet.com> het
volgende:
>
> On Tue, 17 Jul 2012 17:27:35 +0200
> Tom Gundersen <teg@jklm.no> wrote:
>
> Pruned
> >
> > Hm.... how did /lib end up as a symlink to /usr/lib without those
> > files being owned by glibc? Did you just copy it over manually and
> > create the link yourself?
> >
> > -t
>
> Quite easily
>
> I followed what was on the Arch web site and the links therein
> nothing fancy
;-)
It might help to know which steps you took.
Afaik, the instructions were to check if any files were still in /lib
-other then glibc's- and to rebuild those packages. But maybe you took some
other steps?
Checking the ownership of files in the symlinked /lib has little purpose.
> Op 17 jul. 2012 18:01 schreef "P .NIKOLIC"
> <p.nikolic1@btinternet.com> het volgende:
> >
> > On Tue, 17 Jul 2012 17:27:35 +0200
> > Tom Gundersen <teg@jklm.no> wrote:
> >
> > Pruned
> > >
> > > Hm.... how did /lib end up as a symlink to /usr/lib without those
> > > files being owned by glibc? Did you just copy it over manually and
> > > create the link yourself?
> > >
> > > -t
> >
> > Quite easily
> >
> > I followed what was on the Arch web site and the links therein
> > nothing fancy
>
> ;-)
> It might help to know which steps you took.
>
> Afaik, the instructions were to check if any files were still in /lib
> -other then glibc's- and to rebuild those packages. But maybe you
> took some other steps?
>
> Checking the ownership of files in the symlinked /lib has little
> purpose.
>
> Just my two cents.
>
> mvg, Guus
Hi ..
this is the link that got the box running again ..
https://bbs.archlinux.org/viewtopic.php?pid=1127251#p1127251
Pete ..
--
Linux 7-of-9 3.4.4-3-ARCH #1 SMP PREEMPT Tue Jul 3 14:36:44 UTC 2012
x86_64 GNU/Linux
07-17-2012, 10:19 PM
"P .NIKOLIC"
Still Glibc problems
On Tue, 17 Jul 2012 17:27:35 +0200
Tom Gundersen <teg@jklm.no> wrote:
>
> Hm.... how did /lib end up as a symlink to /usr/lib without those
> files being owned by glibc? Did you just copy it over manually and
> create the link yourself?
>
> -t
Right after much faffing about i now have the box back to
# pacman -Qo /lib/*
/lib/ld-2.16.so is owned by glibc 2.16.0-1
/lib/ld-linux-x86-64.so.2 is owned by glibc 2.16.0-1
/lib/libanl-2.16.so is owned by glibc 2.16.0-1
/lib/libanl.so.1 is owned by glibc 2.16.0-1
/lib/libBrokenLocale-2.16.so is owned by glibc 2.16.0-1
/lib/libBrokenLocale.so.1 is owned by glibc 2.16.0-1
/lib/libc-2.16.so is owned by glibc 2.16.0-1
/lib/libcidn-2.16.so is owned by glibc 2.16.0-1
/lib/libcidn.so.1 is owned by glibc 2.16.0-1
/lib/libcrypt-2.16.so is owned by glibc 2.16.0-1
/lib/libcrypt.so.1 is owned by glibc 2.16.0-1
/lib/libc.so.6 is owned by glibc 2.16.0-1
/lib/libdl-2.16.so is owned by glibc 2.16.0-1
/lib/libdl.so.2 is owned by glibc 2.16.0-1
/lib/libm-2.16.so is owned by glibc 2.16.0-1
/lib/libmemusage.so is owned by glibc 2.16.0-1
/lib/libm.so.6 is owned by glibc 2.16.0-1
/lib/libnsl-2.16.so is owned by glibc 2.16.0-1
/lib/libnsl.so.1 is owned by glibc 2.16.0-1
/lib/libnss_compat-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_compat.so.2 is owned by glibc 2.16.0-1
/lib/libnss_db-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_db.so.2 is owned by glibc 2.16.0-1
/lib/libnss_dns-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_dns.so.2 is owned by glibc 2.16.0-1
/lib/libnss_files-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_files.so.2 is owned by glibc 2.16.0-1
/lib/libnss_hesiod-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_hesiod.so.2 is owned by glibc 2.16.0-1
/lib/libnss_nis-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nisplus-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nisplus.so.2 is owned by glibc 2.16.0-1
/lib/libnss_nis.so.2 is owned by glibc 2.16.0-1
/lib/libpcprofile.so is owned by glibc 2.16.0-1
/lib/libpthread-2.16.so is owned by glibc 2.16.0-1
/lib/libpthread.so.0 is owned by glibc 2.16.0-1
/lib/libresolv-2.16.so is owned by glibc 2.16.0-1
/lib/libresolv.so.2 is owned by glibc 2.16.0-1
/lib/librt-2.16.so is owned by glibc 2.16.0-1
/lib/librt.so.1 is owned by glibc 2.16.0-1
/lib/libSegFault.so is owned by glibc 2.16.0-1
/lib/libthread_db-1.0.so is owned by glibc 2.16.0-1
/lib/libthread_db.so.1 is owned by glibc 2.16.0-1
/lib/libutil-2.16.so is owned by glibc 2.16.0-1
/lib/libutil.so.1 is owned by glibc 2.16.0-1
error: failed to commit transaction (conflicting files)
glibc: /usr/lib/ld-2.16.so exists in filesystem
glibc: /usr/lib/ld-linux-x86-64.so.2 exists in filesystem
glibc: /usr/lib/libBrokenLocale-2.16.so exists in filesystem
glibc: /usr/lib/libBrokenLocale.so.1 exists in filesystem
glibc: /usr/lib/libSegFault.so exists in filesystem
glibc: /usr/lib/libanl-2.16.so exists in filesystem
glibc: /usr/lib/libanl.so.1 exists in filesystem
glibc: /usr/lib/libc-2.16.so exists in filesystem
glibc: /usr/lib/libc.so.6 exists in filesystem
glibc: /usr/lib/libcidn-2.16.so exists in filesystem
glibc: /usr/lib/libcidn.so.1 exists in filesystem
glibc: /usr/lib/libcrypt-2.16.so exists in filesystem
glibc: /usr/lib/libcrypt.so.1 exists in filesystem
glibc: /usr/lib/libdl-2.16.so exists in filesystem
glibc: /usr/lib/libdl.so.2 exists in filesystem
glibc: /usr/lib/libm-2.16.so exists in filesystem
glibc: /usr/lib/libm.so.6 exists in filesystem
glibc: /usr/lib/libmemusage.so exists in filesystem
glibc: /usr/lib/libnsl-2.16.so exists in filesystem
glibc: /usr/lib/libnsl.so.1 exists in filesystem
glibc: /usr/lib/libnss_compat-2.16.so exists in filesystem
glibc: /usr/lib/libnss_compat.so.2 exists in filesystem
glibc: /usr/lib/libnss_db-2.16.so exists in filesystem
glibc: /usr/lib/libnss_db.so.2 exists in filesystem
glibc: /usr/lib/libnss_dns-2.16.so exists in filesystem
glibc: /usr/lib/libnss_dns.so.2 exists in filesystem
glibc: /usr/lib/libnss_files-2.16.so exists in filesystem
glibc: /usr/lib/libnss_files.so.2 exists in filesystem
glibc: /usr/lib/libnss_hesiod-2.16.so exists in filesystem
glibc: /usr/lib/libnss_hesiod.so.2 exists in filesystem
glibc: /usr/lib/libnss_nis-2.16.so exists in filesystem
glibc: /usr/lib/libnss_nis.so.2 exists in filesystem
glibc: /usr/lib/libnss_nisplus-2.16.so exists in filesystem
glibc: /usr/lib/libnss_nisplus.so.2 exists in filesystem
glibc: /usr/lib/libpcprofile.so exists in filesystem
glibc: /usr/lib/libpthread-2.16.so exists in filesystem
glibc: /usr/lib/libpthread.so.0 exists in filesystem
glibc: /usr/lib/libresolv-2.16.so exists in filesystem
glibc: /usr/lib/libresolv.so.2 exists in filesystem
glibc: /usr/lib/librt-2.16.so exists in filesystem
glibc: /usr/lib/librt.so.1 exists in filesystem
glibc: /usr/lib/libthread_db-1.0.so exists in filesystem
glibc: /usr/lib/libthread_db.so.1 exists in filesystem
glibc: /usr/lib/libutil-2.16.so exists in filesystem
glibc: /usr/lib/libutil.so.1 exists in filesystem
Errors occurred, no packages were upgraded.
Pete .
--
Linux 7-of-9 3.4.4-3-ARCH #1 SMP PREEMPT Tue Jul 3 14:36:44 UTC 2012
x86_64 GNU/Linux
07-17-2012, 10:46 PM
Tom Gundersen
Still Glibc problems
On Wed, Jul 18, 2012 at 12:19 AM, P .NIKOLIC <p.nikolic1@btinternet.com> wrote:
> Right after much faffing about i now have the box back to
So if /lib is NOT a symlink, then all you should need is to delete all
the files in /usr/lib that are not owned by any package. Then you
should be able to upgrade.
grep -v glibc is too simple actually and will filter out lib32-glibc for
example.
--
дамјан
07-18-2012, 01:11 AM
Andrew Hills
Still Glibc problems
On Tue, Jul 17, 2012 at 6:46 PM, Tom Gundersen <teg@jklm.no> wrote:
> So if /lib is NOT a symlink, then all you should need is to delete all
> the files in /usr/lib that are not owned by any package. Then you
> should be able to upgrade.
And if /lib IS a symbolic link, delete it and let the glibc sync create it.
--Andrew Hills
07-18-2012, 07:09 AM
Tom Gundersen
Still Glibc problems
On Wed, Jul 18, 2012 at 3:11 AM, Andrew Hills <hills.as@gmail.com> wrote:
> On Tue, Jul 17, 2012 at 6:46 PM, Tom Gundersen <teg@jklm.no> wrote:
>> So if /lib is NOT a symlink, then all you should need is to delete all
>> the files in /usr/lib that are not owned by any package. Then you
>> should be able to upgrade.
>
> And if /lib IS a symbolic link, delete it and let the glibc sync create it.
No. Then you'll lose your loader and can't do anything...