You are not logged in.
Offline
Did you read Binaries move to /usr/bin requiring update intervention ?
Offline
beat me to it
Offline
Merging with main thread
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes 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
Offline
Ugh.. Refrasing:
I uninstalled _everything_ that this complains about:
[root@faparch doxid]# pacman -Q | pacman -Qk | grep warning
Gives nothing after i've uninstalled android-sdk etc.. so all should be good.
However..
[root@faparch doxid]# pacman -Syu
:: 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...
Packages (1): filesystem-2013.05-2
Total Installed Size: 0.01 MiB
Net Upgrade Size: -0.30 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [##############################################] 100%
(1/1) checking package integrity [##############################################] 100%
(1/1) loading package files [##############################################] 100%
(1/1) checking for file conflicts [##############################################] 100%
error: failed to commit transaction (conflicting files)
filesystem: /sbin exists in filesystem
Errors occurred, no packages were upgraded.
So i checked what's in there:
Doing: [root@faparch doxid]# ls -ln /sbin
total 152
-rwxr-xr-x 1 0 0 36144 Jun 3 23:15 kpartx
-rwxr-xr-x 1 0 0 23712 Jun 3 23:15 mpathpersist
-rwxr-xr-x 1 0 0 19088 Jun 3 23:15 multipath
-rwxr-xr-x 1 0 0 73512 Jun 3 23:15 multipathd
Knowing i just installed this 5 min before doing the system install.
I just did pacman -Rs mutlipath-tools-git and did another pacman -Syu and everything works great.
Note: If filesystem doesn't go through, sudo will not be a thing, among a few other things so be careful!
Last edited by Torxed (2013-06-03 22:06:13)
Offline
Hello,
I tried to update my Arch before reading a news on archlinux.org. I run 'pacman -Syu --ignore filesystem'. All was fine until reboot. Now I can't run system or anything. When Arch is starting there is following message:
ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own.
sh: can't access tty; job control turned off
[rootfs/]#
I tried to chroot to my Arch installation from BackTrack booted from USB, but there is:
chroot: cannot run command `/bin/bash' : No such file or directory
Is there any way to recover current Arch installation or I have to reinstall ?
Offline
Merging with the stickied thread (which you should have read before posting...)
Offline
Torxed, I may have missed something - but it looks like you have not read the front page news item, nor any of the posts in this thread.
What you are seeing is expected - but you do need to take the proper steps carefully. Those steps are best enumerated in the front page news item.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Ok so, ?. I've no issue with the solutions I can handle that. On the logic though, in an environment where a structural change (Its my own fault for not following the dev ML) wouldn't necessarily be something easy to argue in a 24 hour period, is there/was there a direct change towards many packages that forceably point them to /usr/lib, or are those packages just pointed to the /lib symlink and left to stupidly follow the symlink instead?
In other words, if I want a kernel update is it going to put it in /usr/lib OR forceably depend on whichever particular package actaully organized the initial change to begin with... or can I selectively update packages while I throw poo at beaurocrats?
Last edited by offbeatadam (2013-06-03 22:47:54)
"Never attribute to malice that which is adequately explained by stupidity." - Hanlon's Razor
Offline
"selectively update package" = partial update = NOT SUPPORTED.
the packages themselves will put the files in /usr/lib, but many things will still access it through the /lib symlink.
Last edited by Scimmia (2013-06-03 22:52:16)
Offline
"selectively update package" = partial update = NOT SUPPORTED.
the packages themselves will put the files in /usr/lib, but many things will still access it through the /lib symlink.
Not supported was kind of irrelevant to me, I wasn't trying to do something supported, I was trying to do something I would support myself. The question was answered by the secondary sentence though.
It's not totally a huge deal, just means that I have some work to do in automating doing something unsupported myself until the bridges are crossed that allow this sort of change to go through in an environment that handles more than looking pretty. That has nothing to do with anything here at Arch, its just the compliance policy here. It's my problem, I just wanted to see if I had to work at it or if I can avoid it. Arch may not be directed towards server purposes necessarily, but it doesn't avoid them entirely. Assuming that I don't know what I'm doing simply because I asked if I could do a partial update, isn't exactly constructive, especially when I already insinuated that I have compliance issues to deal with and unfortunately throwing poo at beaurocrats once is hardly the only time I'm going to have to do it to make the bobbleheads go up and down instead of left to right.
"Never attribute to malice that which is adequately explained by stupidity." - Hanlon's Razor
Offline
@Kamillo, I see you forgot to install that package just after updating, hence your filesystem hasn't got some symbolic links to your /usr directory. If so, do fix it manually by running on your pen drive.
ln -s usr/bin /<mount_point>/bin
ln -s usr/bin /<mount_point>/sbin
Bear in mind your currently AUR packages, btw.
Offline
Don't do that, you won't be able to install the filesystem on top of those symlinks. Just install it with pacman -S filesystem --root <mountpoint>
Offline
@Scimmia, as far as I know @kamillo will be unable to run `pacman -Sy filesystem --root <mount_point>` on that other distro; moreover, there is no chroot environment anywhere. How to do it then?
Therefore, pragmatically speaking, he can make those symlinks and remove them after if he cannot install filesystem package when running on Arch Linux. So I see no reason to overdramatize that minor issue, after all, he should be able to fix it as an Arch user.
Last edited by akanski (2013-06-05 17:25:29)
Offline
Ah, I didn't see that he was using "BackTrack" on the USB. You can try chrooting with chroot /usr/bin/bash, you *may* be able to do enough to install the filesystem package.
Offline
Offline
With pacman 4.1, it's ok (not good, but it'll work). It's looking like pacman 4.2 will throw an error.
Offline
What happens when a package would want to install binary in one of the symlinked folders? Some of the AUR packages are yet to be updated and might take some time.
Currently it works, but if possible you should try to fix it yourself. In many cases, there should be an option for configure or make to set the directories. If it is not possible, you could create the symlink in the PKGBUILD, install and remove it again.
package() {
ln -s usr/lib ${pkgdir}/lib
make install --DESTDIR=${pkgdir}
rm ${pkgdir}/lib
}
source: https://mailman.archlinux.org/pipermail … 16488.html
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Online
@Scimmia,
If my memory serves me well, I didn't face any issue during '/lib' merging despite the fact that I already had '/usr/lib64' as symlink to '/usr/lib', which I made to test ekopath compiler. So I see no reason why it should fail now (i.e. OK for filesystem 2013.01-1 and not 2013.05-1)
By the way, everything was fine and dandy to me when updating, so I'm just trying to give practical assistance to @kamillo like you
Last edited by akanski (2013-06-05 03:30:17)
Offline
ERROR: Root device mounted successfully, but /sbin/init does not exist. Bailing out, you are on your own. Good luck.
I have followed multiple posts about this particular error, but nothing is helping. I tried adding the init=/bin/systemd to my grub2 to no avail.
The closest I got to something different was init=/usr/lib/systemd/systemd in my grub2, still no boot, but different errors
Offline
akanski, without using --force, pacman won't overwrite files it doesn't think are already owned by the package being upgraded. If you make those symlinks, they won't be owned by any package and pacman will just throw the error that /bin and /sbin already exist. I'm not sure why you were able to do it with 2013.01.
Believe me, everyone appreciate people helping out, it's been a hell of a day with this update both here and on IRC.
Offline
I'm guessing you ran into problems updating and instead of checking the front page, you just ignored filesystem?
Offline
... still no boot, but different errors
And, what were they?
Do you have systemd-sysvcompat installed?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Yeah I didnt check the front page, never claimed to be a genius. I do use 'safepac' but Im guessing it missed this one. I am unsure if I have systemd-sysvcompat installed.
I cant type anything at rootfs:
Heres the new errors:
http://i.imgur.com/lS4ZA97.jpg
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Offline
I really think it sounds like Scimmia is right here.
Edit: Wow... I was a bit too slow here.
Last edited by WonderWoofy (2013-06-04 03:40:59)
Offline