filesystem Update Error /bin exists in filesystem

Hello,

everytime I try to update filesystem to 2013.05, I get this error. Does anyone know a solution to this. I would guess that it could be related to file corruption in pacman, as my system is otherwise working just fine.

Re: filesystem Update Error /bin exists in filesystem

Re: filesystem Update Error /bin exists in filesystem

Gusar wrote:

I was waiting for a thread like this to appear

It was surely inevitable. I was very shcoed to see how fast this move was actually done after Allan announced he was bored and wanted to get moving on it. I went through the update this morning and it went smooth as butter. But I first found all the AUR packages that I had that were still utilizing /usr/sbin, /bin, and /sbin and took care of those first. I was surprised to find I only had four that were potential conflicts (f2fs-tools-git, connman-git, hfsprogs, and hostsblock).

Re: filesystem Update Error /bin exists in filesystem

For anyone who's encountered this problem, do not use pacman's --force flag to install the filesystem update.

Check your AUR packages for updates, and update them. Remove or rebuild (after modifying the PKGBUILD) any unsupported packages that still place binaries in /bin, /sbin or /usr/sbin. If you have untracked files in those directories, remove them, or move them to /usr/local/bin.

Get a list of packages that owns files in /bin, /sbin, and /usr/sbin (tested in bash and zsh):

Re: filesystem Update Error /bin exists in filesystem

Moving to testing

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

Re: filesystem Update Error /bin exists in filesystem

WorMzy wrote:

For anyone who's encountered this problem, do not use pacman's --force flag to install the filesystem update....Again, do NOT use pacman's --force flag to install the filesystem update.

Though this is good advice, I would like to point out that pacman in its current form will not actually let you replace a directory with a file. The symlink coulnts as a file, so the force won't happen anyway. Of course this assumes that pacman itself is up to date.

Re: filesystem Update Error /bin exists in filesystem

I was very shcoed to see how fast this move was actually done after Allan announced he was bored and wanted to get moving on it.

Yeah, I too was surprised to see it already.

WonderWoofy wrote:

I went through the update this morning and it went smooth as butter.

I was actually sad at how uneventful it was . I expected my systems to explode. But nothing. Then I thought "ok, maybe they work now, but on a reboot things will surely go to hell". Nope, after the reboot the system came up as always. Boring

Re: filesystem Update Error /bin exists in filesystem

I recommend using su and update all trow pacman after return to normal user on terminalonly for safenessness

Allan announced he was bored

me too, I moved to testing temporally for the fact of /usr/bin-inessNow I only noticed any change only a sistem Megas more light... I was deceptionated, now make the same for usr/local/sbin (any can say that I give a +1 to that?)

Re: filesystem Update Error /bin exists in filesystem

What he means is that you need to update filesystem before you reboot. By moving everything into /usr/bin, and then not putting in place the symlinks necessary to resolve paths like /sbin, /bin, and /usr/bin you will render your system unbootable because it will not be able to find many of the necessary binaries to get your system going.

Whether you used sudo or su doesn't really matter as long as you do both steps.

Re: filesystem Update Error /bin exists in filesystem

What happens with post-install scripts if binaries cannot be found? There are absolute references to /usr/sbin, /sbin, /bin in some scripts I think.This was my updatepath:- sync databases- get list of pacakges with files in /bin, /sbin, /usr/sbin.- update packages from this list- make sure /bin, /sbin, /usr/sbin are clean.- update filesystem- reinstall packages from said list (make sure install scripts are executed properly)- update everything

Btw: As soon as I get a conflict during a normal update, I open a root busybox shell. This means I have a backup shell to fix a borked system without reboots and bootcds (worst case: use pacman cache and extract some old packages manually and delete broken upgrades)

Re: filesystem Update Error /bin exists in filesystem

WorMzy wrote:

For anyone who's encountered this problem, do not use pacman's --force flag to install the filesystem update.

And that should be enough... With pacman-4.1 (and the patched 4.0.xversions in our repos since the /lib move), anybody just doing a "pacman-Syu" will get a conflict. Using --force in pamcan-4.1 will not breakthings (I think...) as --force does not allow overwriting a directorywith a file. People using pacman-4.0.x and --force could still breaktheir system.