Pacman Update Problem

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Re: Pacman Update Problem

Postby WarheadsSE » Sat Jun 09, 2012 2:55 pm

Tomorrow, as I am at #SELF2012 today, I will put the instructions up.
Until then, please be patient.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Pacman Update Problem

Postby dito » Mon Jun 11, 2012 3:34 am

I figure since I am here, I'll post my experience.

I've also ran an update (don't remember when) and I lost SSHD, it doesn't listen (I scanned the device).
I have a pogoplug (no keyboard, mouse, video) and I am running cherokee, samba, cups, transimission, upnp, other goodies...

After the upgrade, I can reboot any time, all of those above mentioned services start up, but SSH doesn't.

I am not sure why it doesn't, I didn't find any "ssh" string in the logs.
All of those services are in read-only mode, SO the only way for me right now to do anything in "root" mode is to shut it off and plug the drive onto another linux device, grab my files, delete them and boot the pogoplug again. I have a 320WD passport attached to it, since everything is read-only mode, it gets full quickly with transmissions running.

anyway, what can I do?
dito
 
Posts: 4
Joined: Mon Aug 01, 2011 9:02 pm

Re: Pacman Update Problem

Postby TheWalt » Mon Jun 11, 2012 3:49 pm

Not sure if this is related but "pacman -Syu" on my GoFlex Home also errors with the following:

$this->bbcode_second_pass_code('', '
Targets (14): filesystem-2012.6-2 git-1.7.10.4-1 gnutls-3.0.20-1
initscripts-2012.06.1-1 krb5-1.10.2-1 libcups-1.5.3-4
libwbclient-3.6.5-3 linux-api-headers-3.3.8-1 openntpd-3.9p1-15
pacman-mirrorlist-20120608-1 psmisc-22.17-1 samba-3.6.5-3
smbclient-3.6.5-3 systemd-tools-185-1

Total Installed Size: 141.92 MiB
Net Upgrade Size: 0.12 MiB

Proceed with installation? [Y/n]
(14/14) checking package integrity [######################] 100%
(14/14) loading package files [######################] 100%
(14/14) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
filesystem: /var/lock exists in filesystem
filesystem: /var/run exists in filesystem
Errors occurred, no packages were upgraded.
')

EDIT: It seems this is an issue across the archlinux platform with a solution posted here.
TheWalt
 
Posts: 23
Joined: Fri Feb 17, 2012 12:22 am

Re: Pacman Update Problem

Postby sputnik » Mon Jun 11, 2012 6:18 pm

Good eyes TheWalt. Thank you, worked for me :)
sputnik
 
Posts: 14
Joined: Mon Jan 16, 2012 6:50 pm

Re: Pacman Update Problem

Postby dito » Mon Jun 11, 2012 9:25 pm

my problem now thou is that I don't have SSH, and that is the only way for me to access the server.
What can I do to fix it "offline" as plugged onto my linux desktop to make any changes so that I can plug it back to my pogoplug and boot it back on?
dito
 
Posts: 4
Joined: Mon Aug 01, 2011 9:02 pm

Re: Pacman Update Problem

Postby WarheadsSE » Wed Jun 13, 2012 5:11 pm

For those on oxnas, we're still digging.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Pacman Update Problem

Postby evilhomer » Fri Jun 22, 2012 10:26 pm

worked on my pogoplug v2 too. thanks!
evilhomer
 
Posts: 9
Joined: Mon Apr 30, 2012 10:29 pm

Re: Pacman Update Problem

Postby saiph » Sat Jul 07, 2012 9:50 am

Not for me though. Trying that, I get

$this->bbcode_second_pass_code('', '
pacman -Syu --ignore filesystem && pacman -S filesystem --force
:: Synchronizing package databases...
core 37.9 KiB 604K/s 00:00 [######################] 100%
extra 427.6 KiB 1602K/s 00:00 [######################] 100%
community 405.0 KiB 1655K/s 00:00 [######################] 100%
alarm 3.4 KiB 3.81M/s 00:00 [######################] 100%
aur 10.7 KiB 2.09M/s 00:00 [######################] 100%
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] y

resolving dependencies...
looking for inter-conflicts...

Targets (22): bash-4.2.029-1 ca-certificates-20120623-1 coreutils-8.17-1
curl-7.26.0-1 db-5.3.21-1 e2fsprogs-1.42.4-1 gcc-libs-4.7.0-6
glibc-2.15-10 gmp-5.0.5-1 libldap-2.4.31-4 libssh2-1.4.2-1
linux-api-headers-3.4.4-1 openssl-1.0.1.c-1
pacman-mirrorlist-20120608-1 pam-1.1.5-4 pambase-20120701-1
perl-5.16.0-2 pinentry-0.8.1-4 run-parts-4.3.2-1
util-linux-2.21.2-3 xz-5.0.4-1 pacman-4.0.3-1

Total Download Size: 3.78 MiB
Total Installed Size: 152.37 MiB
Net Upgrade Size: 2.62 MiB

Proceed with installation? [Y/n]
:: Retrieving packages from core...
linux-api-headers-3... 578.6 KiB 1487K/s 00:00 [######################] 100%
pambase-20120701-1-any 1044.0 B 2.78M/s 00:00 [######################] 100%
pam-1.1.5-4-arm 600.4 KiB 1787K/s 00:00 [######################] 100%
run-parts-4.3.2-1-arm 16.6 KiB 1968K/s 00:00 [######################] 100%
ca-certificates-201... 126.7 KiB 1804K/s 00:00 [######################] 100%
pacman-mirrorlist-2... 740.0 B 2047K/s 00:00 [######################] 100%
xz-5.0.4-1-arm 209.3 KiB 1794K/s 00:00 [######################] 100%
util-linux-2.21.2-3-arm 1353.2 KiB 1785K/s 00:01 [######################] 100%
e2fsprogs-1.42.4-1-arm 665.0 KiB 1789K/s 00:00 [######################] 100%
libldap-2.4.31-4-arm 319.0 KiB 1794K/s 00:00 [######################] 100%
(22/22) checking package integrity [######################] 100%
(22/22) loading package files [######################] 100%
(22/22) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
util-linux: /bin/login exists in filesystem
util-linux: /etc/pam.d/chfn exists in filesystem
util-linux: /etc/pam.d/chsh exists in filesystem
util-linux: /etc/pam.d/login exists in filesystem
util-linux: /usr/bin/chfn exists in filesystem
util-linux: /usr/bin/chsh exists in filesystem
util-linux: /usr/bin/newgrp exists in filesystem
util-linux: /usr/sbin/vigr exists in filesystem
util-linux: /usr/sbin/vipw exists in filesystem
util-linux: /usr/share/man/man1/chfn.1.gz exists in filesystem
util-linux: /usr/share/man/man1/chsh.1.gz exists in filesystem
util-linux: /usr/share/man/man1/login.1.gz exists in filesystem
util-linux: /usr/share/man/man1/newgrp.1.gz exists in filesystem
util-linux: /usr/share/man/man8/vigr.8.gz exists in filesystem
util-linux: /usr/share/man/man8/vipw.8.gz exists in filesystem
Errors occurred, no packages were upgraded.
')
saiph
 
Posts: 6
Joined: Thu Jun 07, 2012 11:57 pm

Re: Pacman Update Problem

Postby pepedog » Sat Jul 07, 2012 11:24 am

That soloution was for filesystem upgrade.
I can't test this but it should work
pacman -Syuf
Say n to "and upgrade these packages now? [Y/n]"
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Pacman Update Problem

Postby drankinatty » Mon Jul 09, 2012 4:18 pm

util-linux upgrade problem has affected all updates from normal (non-testing) repositories. On both i686 & x86_64 installs, I get:

(72/72) checking for file conflicts [###########################################] 100%
error: failed to commit transaction (conflicting files)
util-linux: /bin/login exists in filesystem
util-linux: /etc/pam.d/chfn exists in filesystem
util-linux: /etc/pam.d/chsh exists in filesystem
util-linux: /etc/pam.d/login exists in filesystem
util-linux: /usr/bin/chfn exists in filesystem
util-linux: /usr/bin/chsh exists in filesystem
util-linux: /usr/bin/newgrp exists in filesystem
util-linux: /usr/sbin/vigr exists in filesystem
util-linux: /usr/sbin/vipw exists in filesystem
util-linux: /usr/share/man/man1/chfn.1.gz exists in filesystem
util-linux: /usr/share/man/man1/chsh.1.gz exists in filesystem
util-linux: /usr/share/man/man1/login.1.gz exists in filesystem
util-linux: /usr/share/man/man1/newgrp.1.gz exists in filesystem
util-linux: /usr/share/man/man8/vigr.8.gz exists in filesystem
util-linux: /usr/share/man/man8/vipw.8.gz exists in filesystem
Errors occurred, no packages were upgraded.

We are waiting on confirmation that a --force is safe before borking /bin/login or some part of pam. If you can confirm a forced update is OK, drop a note here...
drankinatty
 
Posts: 2
Joined: Mon Jul 09, 2012 4:03 pm

PreviousNext

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 12 guests