Can't downgrade systemd using pacman -U

[ArchiMark]

Hope there's a relatively simple fix....

Installed arch on my little Zaurus SL-C3200 recently.....very cool to have arch on shirt pocket size laptop....
[ if interested, check it out at: http://www.oesf.org/forum/index.php?showtopic=34385 ]

Was warned on Zaurus forum not to upgrade systemd right now as it causes issues.

Thought I had put the systemd related pkg names in /etc/pacman.conf on the IgnorePkg line as instructed.

I did put the names there, but later came to realize I had forgot to uncomment that line..... rolleyes.gif

So, when I did 'pacman -Syu' I noticed midway that it was starting to update systemd......
panicked and did ctrl-C to stop process thinking it would not update it if process was halted.

However, it must have done some updating as I noticed strange behavior afterwards. For example, when I did 'poweroff' it failed.

So, thought I would downgrade systemd with files provided there.

Do 'pacman -U systemd-226-3-arm.pkg.tar.xz', then it starts process, but I get error messages:

$this->bbcode_second_pass_code('', '
# pacman -U systemd-226-3-arm.pkg.tar.xz
loading packages...
warning: downgrading package systemd (226-3.2 => 226-3)
resolving dependencies...
looking for conflicting packages....
error: could not open file /var/lib/pacman/local/systemd-226-3.2/desc: No such file or directory

Packages (1) systemd-226-3

Total Installed Size: 68.27 MiB

:: Proceed with installation? [Y/n]
')


If I say Yes, then it starts, but get error messages at each line saying that the item referred to 'exists in filesystem'
Then says at end 'Errors occurred, no packages were upgraded.'

I shutdown system by removing battery and restarted. Of course, won't boot up now with system on internal CF card.

So, put in my SD card with Arch install on it and have now booted up Z and chrooted into CF Card.

But still get same error messages when doing 'pacman - U systemd-226-3-arm.pkg.tar.xz'......

Any suggestions as to how to get pacman to do the downgrade?

Or have I borked system to where I need to start with fresh install again?

Thanks.

[moonman]

Use --force with pacman

[ArchiMark]

Thanks for your help.....

Had thought of this, but was hesitant to do this given some warnings I've read....

but per your suggestion just tried it....

Still problem as you can see.....

$this->bbcode_second_pass_code('', '
# pacman -U --force systemd-226-3-arm.pkg.tar.xz
loading packages...
warning: downgrading package systemd (226-3.2 => 226-3)
resolving dependencies...
looking for conflicting packages....
error: could not open file /var/lib/pacman/local/systemd-226-3.2/desc: No such file or directory

Packages (1) systemd-226-3

Total Installed Size: 68.27 MiB

:: Proceed with installation? [Y/n]
(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: could not open file: /etc/mtab: No such file or directory
error: could not determine filesystem mount points
error: not enough free disk space
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
')

Seeing the error about not enough disk space makes me wonder if I really chrooted into CF Card (it is 32GB ! and I just installed Arch on it the other day, so, can't be filled already...).

I booted up Zaurus with a 2GB SD card that I installed Arch onto to first test using it on the Zaurus. So, could understand getting the not enough free disk space if I was trying to install to it.

But the chroot seemed to work when I did it....

Any other suggestions?

Thanks.

[WarheadsSE]

Make sure you actually have a copy of that in your pkg cache, or get your hands on another copy of the file.

[ArchiMark]

Thank you for your help and input....

I copied over the systemd-226-3 file to the pkg cache directory and tried again, but get same error messages.....

So, tried installing the slightly newer version systemd file (226-3.2) that I found in the pkg cache, but it won't install either. Get the same error messages...even used --force.....

very odd......

[moonman]

Where are you chrooting from? Another option is copy all files manually from the package. Then when you can bootup run pacman -Suuyy. Take a look at post install section of install script and run those by hand as well https://github.com/archlinuxarm/PKGBUIL ... md.install

[ArchiMark]

Chrooted from a SD card that put an Arch install on it.

Umm...how do I know where to put all the files after uncompressing tar file?....

I see on the systemd page in Arch Wiki:

$this->bbcode_second_pass_quote('', 'T')he available unit files can be seen in /usr/lib/systemd/system/ and /etc/systemd/system/

[moonman]

Take a look at the package itself. It has the directory structure preserves

[ArchiMark]

Uncompressed file on another computer, I see the files are put in several directories....

So, just tried uncompressing file on my Zaurus and get error message:

$this->bbcode_second_pass_code('', '
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
')

;-/


Thought perhaps there is an issue with the chroot setup....so exited and tried to re-chroot in to CF card....
But so far no go.......

Get error message:

$this->bbcode_second_pass_code('', '# mount /dev/sda1 /mnt/cf
# arch-chroot /mnt/cf
unshare: unshare failed: Invalid argument')

;-/

[moonman]

Reboot your device and you will be able to arch-chroot again.

*.pkg.tar.xz has all dirs relative to the root of your rootfs. IF a file goes into /usr/bin/blah then pkg.tar.xz will have /usr/bin/blah

Use bsdtar -spf to not get the errors.

Easiest way:

$this->bbcode_second_pass_code('', 'arch-chroot /path/to/chroot /bin/bash
cd /
bsdtar -xpf /path/to/package
rm .INSTALL .MTREE .PKGINFO

# these may not work in chroot
systemd-sysusers
udevadm hwdb --update
journalctl --update-catalog')

then reboot with this rootfs and try pacman -Suuyy

Also, run fsck on the card before doing all this to make sure the filesystem is intact.