filesystem Update Error /bin exists in filesystem

Foxboron · 2013-06-10 00:49:18

cfr wrote:

You are getting those results with /bin, /sbin and /usr/sbin as symbolic links? That is not going to tell you what you need to know. That command was designed to identify problematic packages if run *before* commencing the upgrade.
Did you move things manually from those directories to /usr/bin? If so, you need to identify the problematic packages in some other way.
grep "$^usr\/sbin$\|$^sbin$\|$^bin$" /var/lib/pacman/local/*/files
should tell you which packages pacman thinks own files in those directories. Many of these will be in the official repos. You are looking for those which also appear in the list you posted above. So start off by figuring out which those are.
Then you will need to remove or update those packages. Some are obsolete e.g. netcfg should be replaced. Others should not appear in the new list e.g. psgrep. Others may need to be updated or replaced.
When you've done that, you can proceed with the rest of the upgrade. However, you will probably need to boot the install media to update filesystem since you are going to have to remove the symbolic links you've created manually in order to do that.

That line didn't reply anything:

$ grep "\(^usr\/sbin\)\|\(^sbin\)\|\(^bin\)" /var/lib/pacman/local/*/files
/var/lib/pacman/local/filesystem-2013.03-2/files:usr/sbin/

cfr · 2013-06-10 01:04:07

In that case, update the system ignoring filesystem and bash. Then update bash. Then boot using live media, remove the symbolic links you created manually and use pacstrap to update the filesystem package. Basically follow the first 2 commands from the news and then use the live media to do the final step.

However, that seems a weird result. I'd expect netcfg, at least, to show up in the listing. Did you alter the files under /var/lib/pacman/local at all?

WorMzy · 2013-06-10 01:17:34

Foxboron wrote:

Helluw.

Helluw?

Foxboron wrote:

So i borked my install by fucking over everything

Yeah, don't do that.

Foxboron wrote:

i cant even remember what i did

Check your ~/.bash_history or equivalent?

Foxboron wrote:

symlinked /usr/bin too /bin, /sbin and /usr/sbin.

Why did you do that? The filesystem packages provides those symlinks, now the filesystem package will fail because these symlinks (files) already exist.

Foxboron wrote:

if i remove any symlinks, i get:
 Error: `git` command not found 

Check your aliases/functions. Seems like you have one that makes 'rm' use git. Unless you're removing files in a different way?

Foxboron wrote:

the line from the fix outputs:

$ pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -

error: No package owns /bin
error: No package owns /sbin
error: No package owns /usr/sbin
...

You didn't actually use the command you posted above, right? You didn't include the trailing dash. The reasons why that dash is important is documented in the pacman manpage and this topic. The first three lines suggest that you don't have any problematic packages though.

Foxboron wrote:

I am not really sure what i should to fix this, any guidance?

Remove the symlinks you created and update/reinstall your filesystem package.

Last edited by WorMzy (2013-06-10 01:19:09)

bzzzap · 2013-06-10 01:59:05

pacman -Qo /bin /sbin /usr/sbin | awk '{print $(NF-1)}'| sort | uniq | grep -v filesystem | xargs -n9999 echo pacman -S
pacman -Syu filesystem

Completely utterly amazed that, seemingly every time I update arch, it craps itself. Dropping this distro as soon as I have the time...I feel like its devolved into another gentoo-esque mess

Last edited by bzzzap (2013-06-10 01:59:44)

WorMzy · 2013-06-10 02:02:07

bzzzap wrote:

pacman -Qo /bin /sbin /usr/sbin | awk '{print $(NF-1)}'| sort | uniq | grep -v filesystem | xargs -n9999 echo pacman -S

Where did you get that command? I don't see it in the news?

bzzzap wrote:

Dropping this distro as soon as I have the time...

So should we waste our time helping you fix the mess you caused, or is this just a rant post?

Last edited by WorMzy (2013-06-10 02:04:47)

bzzzap · 2013-06-10 02:04:17

WorMzy wrote:

bzzzap wrote:
pacman -Qo /bin /sbin /usr/sbin | awk '{print $(NF-1)}'| sort | uniq | grep -v filesystem | xargs -n9999 echo pacman -S
Where did you get that command? I don't see it in the news?

er....I guess I "created" it after skimming this thread?

Trilby · 2013-06-10 02:15:07

So, rather than follow the suggested method that will work, you come up with something different ... then you complain about it breaking? Here's hoping you find that time soon.

bzzzap · 2013-06-10 03:11:33

Trilby wrote:

So, rather than follow the suggested method that will work, you come up with something different ... then you complain about it breaking? Here's hoping you find that time soon.

Another shining example of the arch community.

You misunderstand. Suggested 'method' did not work for me. What I'm upset about is that it can break in this manner in the first place.

Last edited by bzzzap (2013-06-10 03:13:39)

Scimmia · 2013-06-10 03:13:38

Of course it can break in this manner. Arch give you control over your system. With control comes responsibility. If you don't want that responsibility, this isn't the right distro for you.

CKnight · 2013-06-10 04:46:08

I must admit, I agree with bzzaap. This is frustrating. In 18 years of using Linux, this is the most ridiculous upgrade process I've ever experienced. I'm still dead in the water after following the 'suggested' method (and yes I followed the announce EXACTLY), and following the suggested guidance splatterd here. Can someone post a definitive back-out, or fix from '/sbit/init does not exist"? All of the guidance has resulted in different iterations of this distro shitting the bed. As an example, following the guidance at one point got me to UUID not found at boot. No worries, regen initramfs. Back to 'sbin/init' problems.

And before anyone asks, the sym links point from /bin -> /usr/bin and /sbin -> /usr/sbin, and those targets are populated.

And bzzzap is right, this distro has become Gentoo-esque.

HalosGhost · 2013-06-10 04:48:54

CKnight wrote:

And bzzzap is right, this distro has become Gentoo-esque.

As many (and the Arch Way itself) have said, "if you don't like it, use something else." But ranting here about the upgrade process isn't helpful to anyone.

All the best,

-HG

Scimmia · 2013-06-10 04:52:54

CKnight wrote:

I must admit, I agree with bzzaap. This is frustrating. In 18 years of using Linux, this is the most ridiculous upgrade process I've ever experienced. I'm still dead in the water after following the 'suggested' method (and yes I followed the announce EXACTLY), and following the suggested guidance splatterd here. Can someone post a definitive back-out, or fix from '/sbit/init does not exist"? All of the guidance has resulted in different iterations of this distro shitting the bed. As an example, following the guidance at one point got me to UUID not found at boot. No worries, regen initramfs. Back to 'sbin/init' problems.
And before anyone asks, the sym links point from /bin -> /usr/bin and /sbin -> /usr/sbin, and those targets are populated.
And bzzzap is right, this distro has become Gentoo-esque.

If /sbin points to /usr/sbin, that could be a problem, it should point to usr/bin. Of course, /usr/sbin should point to bin (/usr/bin), so it *should* work.

Does /usr/bin/init exist? Do you have systemd-sysvcompat installed?

CKnight · 2013-06-10 04:57:48

HalosGhost wrote:

CKnight wrote:
And bzzzap is right, this distro has become Gentoo-esque.
As many (and the Arch Way itself) have said, "if you don't like it, use something else." But ranting here about the upgrade process isn't helpful to anyone.
All the best,
-HG

Yeah, well, I'm all for the Arch way. I am ranting, but there's a question in my rant that WILL be helpful to everyone, which I haven't seen you, or anyone else in this tired "sticky" answer.

That is,

what is the DEFINITIVE back-out, or fix, from '/sbin/init does not exist' after this broken upgrade? I'm not looking for "try this..." Is there a definitive fix that doesn't involve wipe and reload? That's not a fix. All I'm hearing here is, "Well, if you'd read <foo> BEFORE <foo> then this would have gone perfectly." And this is not the case, I assure you. I an no n00b and followed the guidance here, and READ the output, warnings <there weren't any>, blah, blah.

WonderWoofy · 2013-06-10 05:23:35

No one is telling anyone here to "wipe and reload" so I don't know where you are getting that. Arch Linux only supports what is in the current repos, so I'm not sure what backing-out of this update is going to achieve. Besides that fact that it would be pointless since you would be stuck at that point, I think you are closer to getting through the update than not anyway. But there is no real way to be sure of this since a majority of your post was rant and much less was any kind of actual desription of the situation.

jasonwryan · 2013-06-10 07:21:46

CKnight wrote:

Yeah, well, I'm all for the Arch way. I am ranting, but there's a question in my rant that WILL be helpful to everyone, which I haven't seen you, or anyone else in this tired "sticky" answer.

@CKnight & @bzzzap

There's a reason it hasn't appeared in this thread. Every case contained herein is the result of PEBKAC, in one form or another. So the variety of responses is the community attempting to divine the particular nature of each error, and then provide some assistance as to how to rectify the situation.

Showing up and blaming others is neither smart nor constructive.

mibadt · 2013-06-10 07:48:51

Hi,
I had a working BIOS sytem GRUB2 Arc'h.
While upgrading this morning, I got the "known" filesystem error. I chrooted and tried to fix that problem per the instructions on Arch main page.
Yet, ever since, the system won't boot as GRUB fails to find the root partition.
As can be seen my / resides on sda2 and grub.cfg uses the correct UUID.
The relevant data follows.

Please advise!

Thanks
Regards,
Michael Badt

-----------------------copy of terminal--------------------

# ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Jun 10 08:28 48B4B777B4B7665A -> ../../sda1
lrwxrwxrwx 1 root root 10 Jun 10 08:28 7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jun 10 08:28 9501e2aa-4efe-4497-9b55-db7ebc7afe5d -> ../../sda4
lrwxrwxrwx 1 root root 10 Jun 10 08:28 c1e2a1ee-e45c-49a7-8c9f-468c93ae20b1 -> ../../sda3
lrwxrwxrwx 1 root root 11 Jun 10 08:28 c776fcc3-95b6-4829-8186-b77810ac8f49 -> ../../zram0
lrwxrwxrwx 1 root root 10 Jun 10 08:28 EA0D-F36F -> ../../sdb1

--------------my fstab------------------

# cat fstab
# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/sda2
UUID=7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677	/         	ext4      	defaults,relatime	0 1

# /dev/sda3
UUID=c1e2a1ee-e45c-49a7-8c9f-468c93ae20b1	/home     	ext4      	noauto,x-systemd.automount,relatime	0 2

# /dev/sda1
UUID=48B4B777B4B7665A				/windows  	ntfs-3g   	defaults	0 0

# /dev/sda4
UUID=9501e2aa-4efe-4497-9b55-db7ebc7afe5d	none      	swap      	defaults  	0 0

root@Microknoppix:/media/sda2/boot/grub# cat grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677
else
  search --no-floppy --fs-uuid --set=root 7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677' {
#	acpi=off	
#	pcie_aspm=off
	load_video
	set gfxmode=auto
	#set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
        #systemd.unit=multi-user.target
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677
	else
	  search --no-floppy --fs-uuid --set=root 7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677
	fi
	echo	'Loading Linux core repo kernel ...'
	linux	/boot/vmlinuz-linux root=UUID=7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677 ro  quiet
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initramfs-linux.img
}
menuentry 'Arch GNU/Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677' {
	load_video
	setgfxmode=auto
	#set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
        #systemd.unit=multi-user.target
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677
	else
	  search --no-floppy --fs-uuid --set=root 7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677
	fi
	echo	'Loading Linux core repo kernel ...'
	linux	/boot/vmlinuz-linux root=UUID=7cbfd7ba-38ed-40b5-b5b6-041c1c0f2677 ro  quiet
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initramfs-linux-fallback.img
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows NT/2000/XP (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-48B4B777B4B7665A' {
	insmod part_msdos
	insmod ntfs
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  48B4B777B4B7665A
	else
	  search --no-floppy --fs-uuid --set=root 48B4B777B4B7665A
	fi
	drivemap -s (hd0) ${root}
	chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

jasonwryan · 2013-06-10 07:55:44

Merging with the stickied thread...

Foxboron · 2013-06-10 10:19:38

WorMzy wrote:

Helluw?

Helluw??

WorMzy wrote:

Yeah, don't do that.

Yeah i know, but sometimes people do dumb stuff. Right?

WorMzy wrote:

Check your ~/.bash_history or equivalent?

Nope, still nothing. That was sad.

WorMzy wrote:

Why did you do that? The filesystem packages provides those symlinks, now the filesystem package will fail because these symlinks (files) already exist.

Because i am in the middle of something called "exams", and i needed a damn quick fix instead of lurking about with the problem.

WorMzy wrote:

Check your aliases/functions. Seems like you have one that makes 'rm' use git. Unless you're removing files in a different way?

No, that is something that popsup AFTER the symlink is gone. Using oh-my-zsh which could explain that.

WorMzy wrote:

You didn't actually use the command you posted above, right? You didn't include the trailing dash. The reasons why that dash is important is documented in the pacman manpage and this topic. The first three lines suggest that you don't have any problematic packages though.

You know i copypastad that line directly into the shell? So yes, that output and that line 100% correct. Want a screenshot maybe?

WorMzy wrote:

Remove the symlinks you created and update/reinstall your filesystem package.

and i am not even sure why you bothered to write your post 10 times larger then what you did. Thanks.

Last edited by Foxboron (2013-06-10 10:20:58)

alextz · 2013-06-10 11:48:53

Same problem for me. Once I've upgraded the system I cannot login anymore(graphical or text).

Any ideeas on how to solve this?

ewaller · 2013-06-10 15:37:29

As moderator, I am getting annoyed with some of the attitudes in this thread. There seem to be an abundance of newcomers to the forums who apparently have managed to break their systems. These forums are generally ready to help, but for the amazing level of entitlement and hostility coming from members with zero posting history. Not a good way to endear oneself to the community while looking for assistance. The trollish behavior and the lack of respect for some of our more seasoned members will stop, now. Bans will be forthcoming.

Heema · 2013-06-10 16:25:43

fluffy wrote:

jasonwryan wrote:
Merging with the stickied thread...
Thanks for the assistance and moving to the correct place.
cfr wrote:
You don't need to create the symlinks. Install/reinstall the filesystem package and it will take care of them for you.
Thanks that did the trick ;-)

Thanks, i also had the same issue. chrooting and issueing a pacman -Sy filesystem did the trick

Scimmia · 2013-06-10 16:33:30

Heema wrote:

Thanks, i also had the same issue. chrooting and issueing a pacman -Sy filesystem did the trick

-Sy filesystem is bad. Make sure you run "pacman -Su" before doing anything else with pacman.

darkreaper476 · 2013-06-10 19:24:13

So, pacman -Su doesn't work because of original error... ??? Early in the thread it seems like people fixed this by temporarily moving to the "testing" repo? I just want to be clear before I break anything else. lol

Thanks

westy · 2013-06-10 19:34:32

Hi,

Haven't used the system for a while (since have been hooked on Neverwinter in Windows, sorry), but have now logged in and kicked off an upgrade.
Can't seem to get it to complete successfully...

At first was getting issues with gcc-libs and gcc-libs-multilib being in conflict, and selecting "y" to remove the conflicting one resulted in another, also a gcc package I think, and hitting "y" again didn't seem to get around it...

After a bit of digging around I enabled the multilib repo in pacman.conf and that issue seemed to have sorted itself (I think/hope).

I've tried a few other things I found in posts after searching for error messages, such as removing some libraries, ignoring deps, and re-installing, but I wasn't really sure why I was doing it, and it seemed that some of the posters in some of the threads had no idea either, but reported sucess.
As is often the case with linux, trying things you find in posts can get you into trouble.

A pacman -S pacman did yield an update to that though, so that got me hopeful.

To be honest though, I don't think I've exacerbated the problem, I just think I still have a conflict, but am having trouble finding out what it is...

Anyway, back to now.
I'm getting this:

[westy@Monty ~]$ sudo pacman -Syu
:: Synchronising 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...

Packages (171): alsa-utils-1.0.27.1-2  archlinux-keyring-20130525-2
                asciidoc-8.6.8-2  autofs-5.0.7-3  bash-4.2.045-4
                binutils-multilib-2.23.2-2  cairo-perl-1.103-2
                chromium-27.0.1453.110-1  coreutils-8.21-2  cryptsetup-1.6.1-2
                darktable-1.2.1-2  device-mapper-2.02.98-4  dhclient-4.2.5.p1-2
                dhcpcd-5.6.8-3  dialog-1.2_20130523-2  e2fsprogs-1.42.7-2
                filesystem-2013.05-2  flac-1.3.0-1  fuse-2.9.2-3  gconf-3.2.6-2
                gdk-pixbuf2-2.28.2-1  giflib-4.2.1-2  glib-perl-1.280-3
                glibc-2.17-6  gnutls-3.2.1-1  gparted-0.16.1-5
                grub-bios-2.00-2  grub-common-2.00-2  gtk2-perl-1.247-2
                gvfs-1.16.2-2  gvfs-afc-1.16.2-2  gvfs-smb-1.16.2-2
                harfbuzz-0.9.18-1  imagemagick-6.8.5.10-1  inetutils-1.9.1-6
                iproute2-3.9.0-2  iptables-1.4.19.1-1  keyutils-1.5.5-5
                kmod-13-2  lib32-alsa-lib-1.0.27.1-1  lib32-atk-2.8.0-1
                lib32-cairo-1.12.14-4  lib32-dbus-core-1.6.10-1
                lib32-flac-1.3.0-1  lib32-fontconfig-2.10.93-1
                lib32-freetype2-2.4.12-1  lib32-gdk-pixbuf2-2.28.1-2
                lib32-glib2-2.36.2-1  lib32-glibc-2.17-5  lib32-glu-9.0.0-2
                lib32-gtk2-2.24.18-1  lib32-harfbuzz-0.9.18-1  lib32-icu-51.2-1
                lib32-krb5-1.11.2-1  lib32-libcanberra-0.30-4
                lib32-libdrm-2.4.45-1  lib32-libgcrypt-1.5.2-1
                lib32-libjpeg-turbo-1.3.0-2  lib32-libldap-2.4.35-1
                lib32-libltdl-2.4.2-9  lib32-libogg-1.3.1-1
                lib32-libpng-1.6.2-1  lib32-libpulse-4.0-1
                lib32-libtiff-4.0.3-2  lib32-libtxc_dxtn-1.0.1-4
                lib32-libx11-1.6.0-1  lib32-libxau-1.0.8-1
                lib32-libxcb-1.9.1-1  lib32-libxcursor-1.1.14-1
                lib32-libxext-1.3.2-1  lib32-libxfixes-5.0.1-1
                lib32-libxi-1.7.1-1  lib32-libxinerama-1.1.3-1
                lib32-libxrandr-1.4.1-1  lib32-libxt-1.1.4-1
                lib32-libxtst-1.2.2-1  lib32-libxv-1.0.8-1
                lib32-libxxf86vm-1.1.3-1
                lib32-llvm-amdgpu-lib-snapshot-20130403-2  lib32-mesa-9.1.3-2
                lib32-nspr-4.9.6-1  lib32-nss-3.14.3-2
                lib32-nvidia-libgl-319.23-1  lib32-nvidia-utils-319.23-1
                lib32-pango-1.34.1-1  lib32-pcre-8.33-1  lib32-pixman-0.30.0-1
                lib32-sqlite-3.7.17-1  lib32-systemd-204-1
                lib32-util-linux-2.23.1-1  lib32-zlib-1.2.8-1
                libatasmart-0.19-2  libbluray-0.3.0-1  libburn-1.3.0.pl01-1
                libcanberra-0.30-4  libcanberra-pulse-0.30-4
                libedit-20130601_3.1-1  libffi-3.0.13-3  libjpeg-turbo-1.3.0-2
                libldap-2.4.35-4  libltdl-2.4.2-9  libmbim-1.0.0-1
                libogg-1.3.1-1  libproxy-0.4.11-2  libpulse-4.0-1
                libsasl-2.1.26-4  libtiff-4.0.3-2  libtool-2.4.2-9
                libx11-1.6.0-1  libxau-1.0.8-1  libxcb-1.9.1-1
                libxcursor-1.1.14-1  libxext-1.3.2-1  libxfixes-5.0.1-1
                libxinerama-1.1.3-1  libxml2-2.9.1-2  libxp-1.0.2-1
                libxrandr-1.4.1-1  libxres-1.0.7-1  libxt-1.1.4-1
                libxtst-1.2.2-1  libxv-1.0.8-1  libxxf86vm-1.1.3-1
                linux-3.9.5-1  linux-firmware-20130528-1
                llvm-amdgpu-lib-snapshot-20130403-3  lm_sensors-3.3.4-1
                lsof-4.87-2  lvm2-2.02.98-4  mesa-9.1.3-1
                modemmanager-0.7.991-1  net-tools-1.60.20130531git-1
                nettle-2.7.1-1  network-manager-applet-0.9.8.2-1
                networkmanager-0.9.8.2-1  nvidia-319.23-1
                nvidia-libgl-319.23-1  nvidia-utils-319.23-1
                opencl-nvidia-319.23-1  p11-kit-0.18.2-1
                pacman-mirrorlist-20130601-1  pango-perl-1.224-2  pcre-8.33-1
                perl-5.18.0-1  perl-gtk2-trayicon-0.06-10
                perl-html-parser-3.71-2  perl-xml-libxml-2.0018-1
                perl-xml-parser-2.41-4  pm-utils-1.4.1-6  ppp-2.4.5-6
                procps-ng-3.3.8-1  pulseaudio-4.0-1  reiserfsprogs-3.6.22-2
                rtmpdump-20121203-2  sed-4.2.2-3  shadow-4.1.5.1-6
                steam-1.0.0.39-2  systemd-204-3  systemd-sysvcompat-204-3
                sysvinit-tools-2.88-11  tar-1.26-4  udisks2-2.1.0-3
                usbmuxd-1.0.8-2  util-linux-2.23.1-2  v4l-utils-0.9.5-2
                vlc-2.0.7-2  wpa_supplicant-2.0-4  xfconf-4.10.0-3
                xkeyboard-config-2.9-1  xterm-293-1  zvbi-0.2.33-6

Total Installed Size:   965.03 MiB
Net Upgrade Size:       -152.83 MiB

:: Proceed with installation? [Y/n] 
(171/171) checking keys in keyring                 [######################] 100%
(171/171) checking package integrity               [######################] 100%
(171/171) loading package files                    [######################] 100%
(171/171) checking for file conflicts              [######################] 100%
error: failed to commit transaction (conflicting files)
filesystem: /bin exists in filesystem
filesystem: /sbin exists in filesystem
filesystem: /usr/sbin exists in filesystem
Errors occurred, no packages were upgraded.
[westy@Monty ~]$

As you can see, I can't tell what the conflict is.

Any ideas how I can find out.
Tried looking in /var/logs/pacman.log but wasn't anything of use; just that I had attempted a full upgrade.

Appreciate any help.

Regards,
Westy

Scimmia · 2013-06-10 19:34:45

darkreaper, this thread was originally in the testing forum, which is what you're seeing.

Did you follow the instructions on the front page? Nothing reported by the first three commands?

Arch Linux

#451 2013-06-10 00:49:18

Re: filesystem Update Error /bin exists in filesystem

#452 2013-06-10 01:04:07

Re: filesystem Update Error /bin exists in filesystem

#453 2013-06-10 01:17:34

Re: filesystem Update Error /bin exists in filesystem

#454 2013-06-10 01:59:05

Re: filesystem Update Error /bin exists in filesystem

#455 2013-06-10 02:02:07

Re: filesystem Update Error /bin exists in filesystem

#456 2013-06-10 02:04:17

Re: filesystem Update Error /bin exists in filesystem

#457 2013-06-10 02:15:07

Re: filesystem Update Error /bin exists in filesystem

#458 2013-06-10 03:11:33

Re: filesystem Update Error /bin exists in filesystem

#459 2013-06-10 03:13:38

Re: filesystem Update Error /bin exists in filesystem

#460 2013-06-10 04:46:08

Re: filesystem Update Error /bin exists in filesystem

#461 2013-06-10 04:48:54

Re: filesystem Update Error /bin exists in filesystem

#462 2013-06-10 04:52:54

Re: filesystem Update Error /bin exists in filesystem

#463 2013-06-10 04:57:48

Re: filesystem Update Error /bin exists in filesystem

#464 2013-06-10 05:23:35

Re: filesystem Update Error /bin exists in filesystem

#465 2013-06-10 07:21:46

Re: filesystem Update Error /bin exists in filesystem

#466 2013-06-10 07:48:51

Re: filesystem Update Error /bin exists in filesystem

#467 2013-06-10 07:55:44

Re: filesystem Update Error /bin exists in filesystem

#468 2013-06-10 10:19:38

Re: filesystem Update Error /bin exists in filesystem

#469 2013-06-10 11:48:53

Re: filesystem Update Error /bin exists in filesystem

#470 2013-06-10 15:37:29

Re: filesystem Update Error /bin exists in filesystem

#471 2013-06-10 16:25:43

Re: filesystem Update Error /bin exists in filesystem

#472 2013-06-10 16:33:30

Re: filesystem Update Error /bin exists in filesystem

#473 2013-06-10 19:24:13

Re: filesystem Update Error /bin exists in filesystem

#474 2013-06-10 19:34:32

Re: filesystem Update Error /bin exists in filesystem

#475 2013-06-10 19:34:45

Re: filesystem Update Error /bin exists in filesystem

Board footer