You are not logged in.
So I recently installed Arch and performed a pacman -Syu for the first time. I think I angered the package manager gods:
klibc: /usr/lib/klibc/include/asm/poll.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/posix_types.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/posix_types_32.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/posix_types_64.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/prctl.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/processor-cyrix.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/processor-flags.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/processor.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/proto.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/ptrace-abi.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/ptrace.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/reboot.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/reboot_fixups.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/required-features.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/resource.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/resume-trace.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/rio.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/rtc.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/rwlock.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/rwsem.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/scatterlist.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/seccomp.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/seccomp_32.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/seccomp_64.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/sections.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/segment.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/semaphore.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/sembuf.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/serial.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/setup.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/shmbuf.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/shmparam.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/sigcontext.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/sigcontext32.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/siginfo.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/signal.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/smp.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/socket.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/sockios.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/sparsemem.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/spinlock.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/spinlock_types.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/srat.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/stacktrace.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/stat.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/statfs.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/string.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/string_32.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/string_64.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/suspend.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/suspend_32.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/suspend_64.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/swiotlb.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/sync_bitops.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/system.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/system_64.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/tce.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/termbits.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/termios.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/therm_throt.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/thread_info.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/thread_info_32.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/thread_info_64.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/time.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/timer.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/timex.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/tlb.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/tlbflush.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/topology.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/tsc.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/types.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/uaccess.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/uaccess_32.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/uaccess_64.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/ucontext.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/unaligned.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/unistd.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/unistd_32.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/unistd_64.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/unwind.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/user.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/user32.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/user_32.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/user_64.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/vga.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/vgtod.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/vic.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/vm86.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/vmi.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/vmi_time.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/voyager.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/vsyscall.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/xen/hypercall.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/xen/hypervisor.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/xen/interface.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/xor.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/xor_32.h exists in filesystem
klibc: /usr/lib/klibc/include/asm/xor_64.h exists in filesystem
Errors occurred, no packages were upgraded.
[joe@Arch X11]$
Pacman -Qo tells me that indeed, these files are owned by klibc 1.5-5. The "Filename exists in file system" sticky says now I should file a bug report. Is that really what I should do?
So, I'm just having trouble figuring out what exactly is happening here. Is it that pacman wants to update these files and it won't overrite them because klibc is using them? Is that it?
Last edited by Joe_Arch (2008-12-05 19:48:36)
Offline
Offline
Thats only one of the reasons the ftp installation is the prefered way to install Archlinux.
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
Thats only one of the reasons the ftp installation is the prefered way to install Archlinux.
I might disagree, if you pick a mirror that failes at first, you need to manually delete the db downloaded, and pick another mirror. And there is no info regarding the fix. I went on to believe for a while that I had a broken CD, but the problem was pacman.
But yes, CORE < FTP.
Birger
Offline
Nevermind..
Last edited by amranu (2008-12-05 13:42:54)
Offline
Just out of curiosity, does doing a pacman -Sfu for updating that package do any harm for that problem?
Offline
Allan wrote:Just out of curiosity, does doing a pacman -Sfu for updating that package do any harm for that problem?
Not sure but I heard pacman -STFU works quite well. Hahahahaha J/K!!!!!!!!!!
Sorry, I just couldn't resist, -Sfu was too close to -Stfu to let it pass.
Offline
Just out of curiosity, does doing a pacman -Sfu for updating that package do any harm for that problem?
ARCH|awesome3.0 powered by Pentium M 750 | 512MB DDR2-533 | Radeon X300 M
The journey is the reward.
Offline
Acecero wrote:Just out of curiosity, does doing a pacman -Sfu for updating that package do any harm for that problem?
Thanks.
Offline
Thanks guys! I had looked at the news, but I didn't look back far enough. From now on I'll search all the news headlines
-Joe
Offline