You are not logged in.

#1 2013-07-04 00:06:35

drayle
Member
Registered: 2013-07-03
Posts: 10

[SOLVED] Unable to Update Filesystem Package

I've been looking through all of the threads/posts about the filesystem update to see if they mentioned the precise issue I'm having, but they don't.

I did a full system upgrade and saw a bunch of errors due to filesystem, so I just ignored it via --ignore and went ahead and installed everything else.

The output explains the problem well enough.

pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community                                                                                                1976.3 KiB   161K/s 00:12 [#######################################################################################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Packages (1): filesystem-2013.05-2

Total Installed Size:   0.01 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: /etc/arch-release exists in filesystem
filesystem: /etc/mtab exists in filesystem
filesystem: /etc/os-release exists in filesystem
filesystem: /etc/profile.d/locale.sh exists in filesystem
filesystem: /lib exists in filesystem
filesystem: /lib64 exists in filesystem
filesystem: /usr/lib/modprobe.d/usb-load-ehci-first.conf exists in filesystem
filesystem: /usr/lib64 exists in filesystem
filesystem: /usr/local/share/man exists in filesystem
filesystem: /usr/share/man/man7/archlinux.7.gz exists in filesystem
filesystem: /var/lock exists in filesystem
filesystem: /var/mail exists in filesystem
filesystem: /var/run exists in filesystem
Errors occurred, no packages were upgraded.

Here is my root directory:

[root@jmtksrv /]# ls
boot  dev  etc  home  lib  lib64  lost+found  mnt  opt  proc  root  run  srv  sys  tmp  usr  var

So as you can see all of the /bin /usr/bin business has been taken care of as far as I know.
Any help would be much appreciated.

Last edited by drayle (2013-07-04 12:25:47)

Offline

#2 2013-07-04 00:26:08

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] Unable to Update Filesystem Package

When did you last update your system?
https://www.archlinux.org/news/filesyst … equired-1/
https://www.archlinux.org/news/filesyst … -required/
https://www.archlinux.org/news/initscri … -required/

/bin should exist - as a symlink to /usr/bin.

$ ls /
bin  boot  dev	etc  home  lib	lost+found  media  mnt	opt  proc  root  run  sbin  share  srv	sys  tmp  usr  var
$ ls -l /bin
lrwxrwxrwx 1 root root 7 May 31 20:40 /bin -> usr/bin


When pasting code or command output, please use [ code ] tags, not [ quote ] tags https://bbs.archlinux.org/help.php#bbcode

like this

It makes the code more readable and - in case of longer listings - more convenient to scroll through.

Last edited by karol (2013-07-04 00:27:07)

Offline

#3 2013-07-04 00:57:20

drayle
Member
Registered: 2013-07-03
Posts: 10

Re: [SOLVED] Unable to Update Filesystem Package

Sorry about the formatting. I last updated earlier this year, so I wouldn't think that other file system manual intervention would apply.

Offline

#4 2013-07-04 01:13:58

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,140

Re: [SOLVED] Unable to Update Filesystem Package

drayle wrote:

Sorry about the formatting. I last updated earlier this year, so I wouldn't think that other file system manual intervention would apply.

It should not but you are seeing conflicts which suggests that it does. Notice the files which you have conflicting.

However, we also need to know exactly what you have done to remove /bin, /sbin etc. because that is going to cause trouble and we cannot advise you if we do not know exactly what that trouble is.

Please post the exact sequence of commands you used when trying to update your system and the output you received. /var/log/pacman.log is likely to be helpful if you cannot remember.

Do not reboot your machine.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#5 2013-07-04 04:05:01

drayle
Member
Registered: 2013-07-03
Posts: 10

Re: [SOLVED] Unable to Update Filesystem Package

I ran

pacman -Syu --ignore filesystem

and below is the result in pacman.log

[2013-07-03 18:54] [PACMAN] Running 'pacman -Syu --ignore filesystem'
[2013-07-03 18:54] [PACMAN] synchronizing package lists
[2013-07-03 18:54] [PACMAN] starting full system upgrade
[2013-07-03 18:54] [ALPM-SCRIPTLET] Generating locales...
[2013-07-03 18:54] [ALPM-SCRIPTLET]   en_US.UTF-8... done
[2013-07-03 18:54] [ALPM-SCRIPTLET] Generation complete.
[2013-07-03 18:54] [PACMAN] upgraded glibc (2.17-5 -> 2.17-6)
[2013-07-03 18:54] [PACMAN] upgraded attr (2.4.46-2 -> 2.4.47-1)
[2013-07-03 18:54] [PACMAN] upgraded acl (2.2.51-3 -> 2.2.52-1)
[2013-07-03 18:54] [PACMAN] upgraded gcc-libs (4.8.0-4 -> 4.8.1-1)
[2013-07-03 18:54] [PACMAN] upgraded pcre (8.32-1 -> 8.33-1)
[2013-07-03 18:54] [PACMAN] upgraded bash (4.2.045-1 -> 4.2.045-4)
[2013-07-03 18:54] [PACMAN] upgraded gmp (5.1.1-1 -> 5.1.2-1)
[2013-07-03 18:54] [PACMAN] upgraded libcap (2.22-4 -> 2.22-5)
[2013-07-03 18:54] [PACMAN] upgraded coreutils (8.21-1 -> 8.21-2)
[2013-07-03 18:54] [PACMAN] upgraded dbus (1.6.10-1 -> 1.6.12-1)
[2013-07-03 18:54] [PACMAN] upgraded libffi (3.0.13-1 -> 3.0.13-3)
[2013-07-03 18:54] [PACMAN] upgraded glib2 (2.36.1-3 -> 2.36.3-2)
[2013-07-03 18:54] [PACMAN] upgraded kbd (1.15.5-3 -> 1.15.5-4)
[2013-07-03 18:54] [PACMAN] upgraded kmod (13-1 -> 13-2)
[2013-07-03 18:54] [PACMAN] upgraded hwids (20130228-1 -> 20130607-1)
[2013-07-03 18:54] [ALPM-SCRIPTLET] ==> Warning: /etc/group or /etc/gshadow are inconsistent.
[2013-07-03 18:54] [ALPM-SCRIPTLET]     Run 'grpck' to correct this.
[2013-07-03 18:54] [PACMAN] upgraded shadow (4.1.5.1-5 -> 4.1.5.1-6)
[2013-07-03 18:54] [PACMAN] upgraded util-linux (2.23-1 -> 2.23.1-2)
[2013-07-03 18:54] [ALPM-SCRIPTLET] ==> The /bin/systemd symlink has been removed. Any references in your
[2013-07-03 18:54] [ALPM-SCRIPTLET]     bootloader (or elsewhere) must be updated to /usr/lib/systemd/systemd.
[2013-07-03 18:54] [PACMAN] upgraded systemd (203-2 -> 204-3)
[2013-07-03 18:54] [ALPM] warning: /etc/httpd/conf/httpd.conf installed as /etc/httpd/conf/httpd.conf.pacnew
[2013-07-03 18:54] [ALPM] warning: /etc/httpd/conf/extra/httpd-ssl.conf installed as /etc/httpd/conf/extra/httpd-ssl.conf.pacnew
[2013-07-03 18:54] [PACMAN] upgraded apache (2.2.24-1 -> 2.2.24-3)
[2013-07-03 18:54] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2013-07-03 18:54] [ALPM-SCRIPTLET] gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
[2013-07-03 18:54] [ALPM-SCRIPTLET] gpg: depth: 0  valid:   1  signed:   5  trust: 0-, 0q, 0n, 0m, 0f, 1u
[2013-07-03 18:54] [ALPM-SCRIPTLET] gpg: depth: 1  valid:   5  signed:  64  trust: 0-, 0q, 0n, 5m, 0f, 0u
[2013-07-03 18:54] [ALPM-SCRIPTLET] gpg: depth: 2  valid:  63  signed:   3  trust: 63-, 0q, 0n, 0m, 0f, 0u
[2013-07-03 18:54] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2014-01-22
[2013-07-03 18:54] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
[2013-07-03 18:54] [ALPM-SCRIPTLET]   -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
[2013-07-03 18:54] [ALPM-SCRIPTLET]   -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
[2013-07-03 18:54] [ALPM-SCRIPTLET]   -> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
[2013-07-03 18:54] [ALPM-SCRIPTLET]   -> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
[2013-07-03 18:54] [ALPM-SCRIPTLET]   -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
[2013-07-03 18:54] [ALPM-SCRIPTLET] ==> Importing owner trust values...
[2013-07-03 18:54] [ALPM-SCRIPTLET] ==> Disabling revoked keys in keyring...
[2013-07-03 18:54] [ALPM-SCRIPTLET]   -> Disabling key 1390420191...
[2013-07-03 18:54] [ALPM-SCRIPTLET]   -> Disabling key E2539214C6C11350...
[2013-07-03 18:54] [ALPM-SCRIPTLET]   -> Disabling key 8544EA82113502DE...
[2013-07-03 18:54] [ALPM-SCRIPTLET] ==> Updating trust database...
[2013-07-03 18:54] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2014-01-22
[2013-07-03 18:54] [PACMAN] upgraded archlinux-keyring (20130406-1 -> 20130525-2)
[2013-07-03 18:54] [PACMAN] upgraded perl (5.16.3-3 -> 5.18.0-1)
[2013-07-03 18:54] [PACMAN] upgraded automake (1.13.1-1 -> 1.14-1)
[2013-07-03 18:54] [PACMAN] upgraded sed (4.2.2-2 -> 4.2.2-3)
[2013-07-03 18:54] [PACMAN] upgraded ca-certificates (20130119-1 -> 20130610-1)
[2013-07-03 18:54] [PACMAN] upgraded isl (0.11.2-1 -> 0.12-1)
[2013-07-03 18:54] [PACMAN] upgraded cloog (0.18.0-1 -> 0.18.0-2)
[2013-07-03 18:54] [PACMAN] upgraded cracklib (2.8.22-1 -> 2.8.22-3)
[2013-07-03 18:54] [PACMAN] upgraded cronie (1.4.9-2 -> 1.4.9-5)
[2013-07-03 18:54] [PACMAN] upgraded device-mapper (2.02.98-3 -> 2.02.98-4)
[2013-07-03 18:54] [PACMAN] upgraded popt (1.16-5 -> 1.16-6)
[2013-07-03 18:54] [PACMAN] upgraded cryptsetup (1.6.1-1 -> 1.6.1-2)
[2013-07-03 18:54] [PACMAN] upgraded curl (7.30.0-1 -> 7.31.0-1)
[2013-07-03 18:54] [PACMAN] upgraded dhcpcd (5.6.8-1 -> 5.6.8-3)
[2013-07-03 18:54] [PACMAN] upgraded e2fsprogs (1.42.7-1 -> 1.42.8-1)
[2013-07-03 18:54] [ALPM-SCRIPTLET] /tmp/alpm_4kSSUS/.INSTALL: line 9: sbin/ldconfig: No such file or directory
[2013-07-03 18:54] [PACMAN] upgraded fakeroot (1.18.4-1 -> 1.19-1)
[2013-07-03 18:54] [PACMAN] upgraded gawk (4.0.2-1 -> 4.1.0-1)
[2013-07-03 18:54] [PACMAN] upgraded gcc (4.8.0-4 -> 4.8.1-1)
[2013-07-03 18:54] [PACMAN] upgraded perl-error (0.17019-1 -> 0.17020-1)
[2013-07-03 18:54] [PACMAN] upgraded git (1.8.2.2-1 -> 1.8.3.2-1)
[2013-07-03 18:54] [PACMAN] upgraded gnupg (2.0.19-7 -> 2.0.20-2)
[2013-07-03 18:54] [PACMAN] upgraded gpm (1.20.7-2 -> 1.20.7-3)
[2013-07-03 18:54] [PACMAN] upgraded groff (1.22.2-2 -> 1.22.2-3)
[2013-07-03 18:54] [PACMAN] upgraded gzip (1.5-3 -> 1.6-1)
[2013-07-03 18:54] [PACMAN] upgraded icu (51.1-1 -> 51.2-1)
[2013-07-03 18:54] [PACMAN] upgraded inetutils (1.9.1-4 -> 1.9.1-6)
[2013-07-03 18:54] [PACMAN] upgraded iptables (1.4.18-1 -> 1.4.19.1-1)
[2013-07-03 18:54] [PACMAN] upgraded iproute2 (3.9.0-1 -> 3.9.0-2)
[2013-07-03 18:54] [PACMAN] upgraded iputils (20121221-1 -> 20121221-2)
[2013-07-03 18:54] [PACMAN] upgraded keyutils (1.5.5-3 -> 1.5.5-5)
[2013-07-03 18:54] [PACMAN] upgraded libsasl (2.1.23-10 -> 2.1.26-4)
[2013-07-03 18:54] [PACMAN] upgraded libldap (2.4.35-2 -> 2.4.35-4)
[2013-07-03 18:54] [PACMAN] upgraded krb5 (1.11.2-1 -> 1.11.3-1)
[2013-07-03 18:54] [PACMAN] upgraded libedit (20120601_3.0-1 -> 20130601_3.1-1)
[2013-07-03 18:54] [PACMAN] upgraded libltdl (2.4.2-8 -> 2.4.2-10)
[2013-07-03 18:54] [PACMAN] upgraded libmariadbclient (5.5.30-2 -> 5.5.31-1)
[2013-07-03 18:54] [PACMAN] upgraded libpcap (1.3.0-3 -> 1.4.0-1)
[2013-07-03 18:54] [PACMAN] upgraded libpipeline (1.2.2-1 -> 1.2.4-1)
[2013-07-03 18:54] [PACMAN] upgraded libtirpc (0.2.2-4 -> 0.2.3-1)
[2013-07-03 18:54] [PACMAN] upgraded tar (1.26-3 -> 1.26-4)
[2013-07-03 18:54] [PACMAN] upgraded libtool (2.4.2-8 -> 2.4.2-10)
[2013-07-03 18:54] [PACMAN] upgraded libxml2 (2.8.0-1 -> 2.9.1-2)
[2013-07-03 18:54] [PACMAN] upgraded linux-firmware (20130430-1 -> 20130610-1)
[2013-07-03 18:54] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-07-03 18:55] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2013-07-03 18:55] [ALPM-SCRIPTLET] /tmp/alpm_Qh1AX5/.INSTALL: /usr/bin/mkinitcpio: /bin/bash: bad interpreter: No such file or directory
[2013-07-03 18:55] [PACMAN] upgraded linux (3.8.11-1 -> 3.9.8-1)
[2013-07-03 18:55] [PACMAN] upgraded logrotate (3.8.4-1 -> 3.8.5-1)
[2013-07-03 18:55] [PACMAN] upgraded lvm2 (2.02.98-3 -> 2.02.98-4)
[2013-07-03 18:55] [PACMAN] upgraded make (3.82-5 -> 3.82-6)
[2013-07-03 18:55] [PACMAN] upgraded man-db (2.6.3-1 -> 2.6.5-1)
[2013-07-03 18:55] [PACMAN] upgraded mdadm (3.2.6-3 -> 3.2.6-4)
[2013-07-03 18:55] [PACMAN] upgraded net-tools (1.60.20120804git-2 -> 1.60.20130531git-1)
[2013-07-03 18:55] [PACMAN] upgraded nodejs (0.10.5-1 -> 0.10.12-1)
[2013-07-03 18:55] [ALPM-SCRIPTLET]
[2013-07-03 18:55] [ALPM-SCRIPTLET] ==> The sshd daemon has been moved to /usr/bin alongside all binaries.
[2013-07-03 18:55] [ALPM-SCRIPTLET] ==> Please update this path in your scripts if applicable.
[2013-07-03 18:55] [ALPM-SCRIPTLET]
[2013-07-03 18:55] [PACMAN] upgraded openssh (6.2p1-1 -> 6.2p2-1)
[2013-07-03 18:55] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2013-07-03 18:55] [PACMAN] upgraded pacman-mirrorlist (20130323-1 -> 20130626-1)
[2013-07-03 18:55] [PACMAN] upgraded pacman (4.1.1-1 -> 4.1.2-1)
[2013-07-03 18:55] [PACMAN] upgraded pciutils (3.2.0-2 -> 3.2.0-3)
[2013-07-03 18:55] [PACMAN] upgraded pcmciautils (018-6 -> 018-7)
[2013-07-03 18:55] [PACMAN] upgraded php (5.4.14-2 -> 5.4.16-1)
[2013-07-03 18:55] [PACMAN] upgraded php-apache (5.4.14-2 -> 5.4.16-1)
[2013-07-03 18:55] [PACMAN] upgraded phpmyadmin (4.0.3-1 -> 4.0.4.1-1)
[2013-07-03 18:55] [PACMAN] upgraded postgresql-libs (9.2.4-1 -> 9.2.4-2)
[2013-07-03 18:55] [PACMAN] upgraded sqlite (3.7.16.2-1 -> 3.7.17-1)
[2013-07-03 18:55] [ALPM] warning: /etc/postfix/main.cf installed as /etc/postfix/main.cf.pacnew
[2013-07-03 18:55] [ALPM-SCRIPTLET] /tmp/alpm_GoiZR3/.INSTALL: /usr/lib/postfix/post-install: /bin/sh: bad interpreter: No such file or directory
[2013-07-03 18:55] [PACMAN] upgraded postfix (2.10.0-4 -> 2.10.1-1)
[2013-07-03 18:55] [ALPM] warning: /etc/ppp/ip-down.d/00-dns.sh installed as /etc/ppp/ip-down.d/00-dns.sh.pacnew
[2013-07-03 18:55] [ALPM] warning: /etc/ppp/ip-up.d/00-dns.sh installed as /etc/ppp/ip-up.d/00-dns.sh.pacnew
[2013-07-03 18:55] [PACMAN] upgraded ppp (2.4.5-5 -> 2.4.5-8)
[2013-07-03 18:55] [ALPM] warning: /etc/sysctl.conf installed as /etc/sysctl.conf.pacnew
[2013-07-03 18:55] [PACMAN] upgraded procps-ng (3.3.7-1 -> 3.3.8-2)
[2013-07-03 18:55] [PACMAN] upgraded python2 (2.7.4-1 -> 2.7.5-1)
[2013-07-03 18:55] [PACMAN] upgraded redis (2.6.13-1 -> 2.6.14-1)
[2013-07-03 18:55] [PACMAN] upgraded serf (1.2.0-1 -> 1.2.1-1)
[2013-07-03 18:55] [PACMAN] upgraded stunnel (4.56-1 -> 4.56-3)
[2013-07-03 18:55] [PACMAN] upgraded subversion (1.7.9-1 -> 1.7.10-1)
[2013-07-03 18:55] [PACMAN] upgraded sudo (1.8.6.p8-1 -> 1.8.7-1)
[2013-07-03 18:55] [ALPM-SCRIPTLET] /tmp/alpm_W7SPJw/.INSTALL: /usr/bin/syslinux-install_update: /bin/bash: bad interpreter: No such file or directory
[2013-07-03 18:55] [PACMAN] upgraded syslinux (4.06-1 -> 4.06-2)
[2013-07-03 18:55] [PACMAN] upgraded syslog-ng (3.4.1-2 -> 3.4.2-1)
[2013-07-03 18:55] [PACMAN] upgraded sysvinit-tools (2.88-9 -> 2.88-11)
[2013-07-03 18:55] [PACMAN] upgraded systemd-sysvcompat (203-2 -> 204-3)
[2013-07-03 18:55] [PACMAN] upgraded usbutils (006-1 -> 007-1)
[2013-07-03 18:55] [PACMAN] upgraded vim-runtime (7.3.918-1 -> 7.3.918-2)
[2013-07-03 18:55] [PACMAN] upgraded vim (7.3.918-1 -> 7.3.918-2)
[2013-07-03 18:55] [PACMAN] upgraded xfsprogs (3.1.10-1 -> 3.1.11-1)

After that, /bin was gone, as was /sbin. I had to edit /etc/passwd to change /bin/bash references to use /usr/bin/bash as well.

Hopefully this is helpful, and thanks a ton for helping me out with this.

Offline

#6 2013-07-04 04:10:30

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,599

Re: [SOLVED] Unable to Update Filesystem Package

drayle wrote:

After that, /bin was gone, as was /sbin. I had to edit /etc/passwd to change /bin/bash references to use /usr/bin/bash as well.

Well that's wrong, undo it.

The files in question should belong to the old filesystem package. If they don't your pacman database is probably damaged. Take a look at /var/lib/pacman/local/filesystem*/files.

Offline

#7 2013-07-04 04:15:50

drayle
Member
Registered: 2013-07-03
Posts: 10

Re: [SOLVED] Unable to Update Filesystem Package

cat /var/lib/pacman/local/filesystem-2013.03-2/files

gives no output.

And what did you say to undo? If I undo the /etc/passwd change then I can't login because /bin/bash is gone.

Offline

#8 2013-07-04 04:18:18

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,599

Re: [SOLVED] Unable to Update Filesystem Package

Why the hell would you log out in the middle of this in the first place!

Yeah, your pacman database is damaged. The easiest fix may be to use --force on the *OLD* package, Note that's NOT ON THE NEW ONE, THE OLD ONE. Even that is a bit risky, but it's the best I can come up with at this point.

Hopefully someone else has a better solution.

Last edited by Scimmia (2013-07-04 04:21:34)

Offline

#9 2013-07-04 04:19:04

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED] Unable to Update Filesystem Package

@Scimmia
drayle has no /bin at all - no symlink, nothing - so pointing bash to /bin/bash doesn't help atm.

Offline

#10 2013-07-04 04:20:39

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,599

Re: [SOLVED] Unable to Update Filesystem Package

karol wrote:

@Scimmia
drayle has no /bin at all - no symlink, nothing - so pointing bash to /bin/bash doesn't help atm.

Right, but unless you close your terminal, it's already in memory and working, you shouldn't need to change the shell.

And since /usr/bin/bash isn't in /etc/shells, he won't be able to log in with it set that way once he fixes this and reboots.

Last edited by Scimmia (2013-07-04 04:24:06)

Offline

#11 2013-07-04 04:40:19

drayle
Member
Registered: 2013-07-03
Posts: 10

Re: [SOLVED] Unable to Update Filesystem Package

This is a remote server (I only have ssh access right now) and I was at work when this issue cropped up. That is why I had to logout.

Offline

#12 2013-07-04 04:58:04

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,599

Re: [SOLVED] Unable to Update Filesystem Package

Just make sure to change it back when you're done or you could end up with even more problems.

Offline

#13 2013-07-04 05:09:18

drayle
Member
Registered: 2013-07-03
Posts: 10

Re: [SOLVED] Unable to Update Filesystem Package

I'm still a bit unclear on what I should do to fix this. You've suggested install/reinstall the past version of filesystem? But you didn't sound too sure about that.

Offline

#14 2013-07-04 05:16:11

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,599

Re: [SOLVED] Unable to Update Filesystem Package

The pacman entry for that package is damaged. The best way to fix that is to reinstall the package in question, but because of the damage, pacman doesn't realize that those files already belong to the filesystem package and will refuse to overwrite them. This is where --force comes in.

The problem is that --force is dangerous, bypassing pacman's safeguards. Installing the same version that's already install _should_ be safe because it's only overwriting things that the filesystem package of the same version put there in the first place, but since you're in the middle of a major update, I can't say that with certainty. Normally I would suggest temporarily moving the problem files, but that's not really possible with the filesystem package. Moving them would leave many things non-function, including the dynamic linker.

Like I said, I'm hoping someone comes by with a better solution.

Offline

#15 2013-07-04 05:22:24

drayle
Member
Registered: 2013-07-03
Posts: 10

Re: [SOLVED] Unable to Update Filesystem Package

Alright. I think I'll wait a little bit to see if someone else has any other advice. But I really appreciate your input Scimmia (and everyone else). Thank you.

Offline

#16 2013-07-04 09:43:36

apg
Developer
Registered: 2012-11-10
Posts: 211

Re: [SOLVED] Unable to Update Filesystem Package

Based on what you've posted, you should be safe to reinstall the old filesystem package with --force.  If you'd rather not do that, you could reinstall the previous version of filesystem with --dbonly.  That will correct pacman's filelist for the filesystem package and get rid of the conflicts, but it won't include the md5's for the backup files, so when you upgrade filesystem it will save all of the backup files as .pacnew's, but that shouldn't hurt anything.

Offline

#17 2013-07-04 10:01:43

drayle
Member
Registered: 2013-07-03
Posts: 10

Re: [SOLVED] Unable to Update Filesystem Package

I just ran the following and now the /var/lib/pacman/filesystem-2013.05-2/files are there, and pacman says my system is up to date.

pacman -Syu --dbonly
:: Synchronizing package databases...
 core is up to date
 extra                                                                                                                                   1435.8 KiB   659K/s 00:02 [#####################################################################################################] 100%
 community                                                                                                                               1976.3 KiB   708K/s 00:03 [#####################################################################################################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Packages (1): filesystem-2013.05-2

Total Installed Size:   0.01 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%

I think I'm missing something though. Sorry if I seem lost, I just don't fully understand how pacman works, I'm sad to admit.

Offline

#18 2013-07-04 10:28:53

apg
Developer
Registered: 2012-11-10
Posts: 211

Re: [SOLVED] Unable to Update Filesystem Package

You just installed the db entry (just the db entry, the actual package still isn't installed) for the new filesystem package instead of the old one.  Look in your package cache (/var/cache/pacman/pkg by default) for the previous version of filesystem and install its db entry with:

# pacman -U --dbonly <path to pkg file>

That should get pacman's db back in sync with what's actually on your system.  After that, try to upgrade to the new filesystem:

# pacman -S filesystem

If that is successful, you still need to reinstall several packages whose install scripts failed because you upgraded bash too soon.  Looking at your log output, the relevant packages are:

fakeroot
linux
postfix
syslinux

Do not reboot until you have reinstalled these packages without getting errors.

Offline

#19 2013-07-04 12:14:15

drayle
Member
Registered: 2013-07-03
Posts: 10

Re: [SOLVED] Unable to Update Filesystem Package

Well I followed your steps and reinstalled the conflicted packages and everything went smoothly. So I guess it's all worked out.

Thanks again everyone.

Last edited by drayle (2013-07-04 12:26:16)

Offline

Board footer

Powered by FluxBB