You are not logged in.
Pages: 1
After attempting the pacstrap -i /mnt base I get some systemd conflicts with libsystemd and systemd-tools. systemd-syscompat also conflicts with sysvinit.
From what I've been reading this has to do with boot-up protocols and such so I'd rather not mess it up (plus saying yes to everything doesn't work lol).
Does pacstrap take pacman commands? If so can I force it like pacman to install without issue? Also do I need any of the items that are in conflict (sysvinit, libsystemd, and systemd-tools)? And I imagine by forcing it to install it would accept whatever I told it to keep and remove, right?
Last edited by Jonnothin (2013-05-22 19:12:23)
Offline
Wait, why is it trying to install sysvinit? Are you telling it to? Is this on an existing system? Sysvinit is deprecated and gone, so it is not in use at all on Arch Linux anymore. We now use systemd.
You should never force anything. It is not good practice. If you want to know exactly what pactrap does, you should check out the script itself. It is pretty simple, and is written in bash.
I think a better idea would be to simply chroot into the installation (I am assuming this is an existing installation) and then use pacman proper from there. There is the arch-chroot tool that you can use to make the chroot super stooopid simple, and it even bind mounts resolv.conf for you so that you have interwebs and everything from inside the chroot.
Offline
I'm sorry I didn't clarify enough.
This is a new installation and I'm following the instructions on the beginner's guide. The beginner's guide didn't specify whether to install everything (default=all) or not. So naturally I left it at the default. Which packages should I omit?
Last edited by Jonnothin (2013-05-22 18:14:15)
Offline
It's kind of confusing what you're doing. If you want advice about how to proceed, you'll need post exactly what commands and errors you're getting. But if you're following the guides in the wiki correctly I don't think you should be seeing these kinds of problems.
Offline
Do not use pacstrap on an existing installation.
Edit: Obviously i was 60 seconds too slow.
Last edited by teateawhy (2013-05-22 18:16:32)
Offline
You don't want to omit anything from base. I'm guessing you meant sysvinit-tools instead of sysvinit, which is where WW was getting confused.
We're going to need the exact error message to know what's going on.
Offline
teateawhy, apparently this is a new installation.... though I fail to see how.
@OP, there is no possible way that you should be pulling in sysvinit, as it is not even in the repos. So you must be trying to isntall on a partition that hasn't been reformatted... that is the only thing I can come up with. If you haven't actually installed anything to that partition yet (as I think is the case if you haven't been able to overcome the conflicts), can you chroot into /mnt? What does "ls /mnt" return? Is there a full filesystem heirarchy there?
Offline
What are you using as a mirror? libsystemd and systemd-tools haven't been separate packages for quite some time, and sysvinit was dropped from the repos earlier this year..
EDIT: I think Wonderwoofy's on to something there.
Last edited by WorMzy (2013-05-22 18:19:23)
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Arch isn't Manjaro/Bridge or whoever else it is still including sysvinit in their repos...
Offline
Actually, I think that jasonwryan is more onto something here...
Offline
Here's exactly what I get:
pacstrap -i /mnt base
::Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: there are 52 members in group base:
:: (list of all base files...)
Enter a selection (default=all):
warning:bzip-1.0.6-4 is up to date -- reinstalling
warning: heirloom-mailx-12.5-3 is up to date -- reinstalling
warning: jfsutils-1.1.15-3 is up to date -- reinstalling
warning: nanon-2.2.6-2 is up to date -- reinstalling
warning: sysfsutils-2.1.0-8 is up to date -- reinstalling
warning: usbutils-006-1 is up to date --reinstalling
resolving dependencies...
looking for inter-conflicts
:: util-linux and eject are in conflict. Remove eject? [y/N] y
:: systemd and libsystemd are in conflict. Remove libsystemd? [y/N] y
:: systemd and systemd-tools are in conflict. Remove systemd-tools? [y/N] y
:: systemd-sysvcompat and sysvinit are in conflict. Remove sysvinit? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
::gcc: requires gcc-libs=4.7.1-4
::initscripts: requires sysvinit
::virtualbox-modules: requires linux<3.5
==ERROR:Failed to install packages to new root
pacstrap -i /mnt base 10.52s user 0.08s system 46% cpu 22.94 total
1 root@archiso ~ # _
I have an idea of what it might be now. I'll let you guys know in a few minutes.
Offline
What source are you using for the packages? As virtualbox-modules is not in the official repos, at least not as that, it's split.
Offline
By the looks of things this is not a new installation, it is an old installation that you're trying to install over the top of. Is there a reason why you're doing this, instead of reformatting the partition first?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
I'm using the default mirrorlist. Also my idea didn't work. I thought that maybe somehow the old arch install that was there was somehow interfering, but that can't be it, I reformated it.
EDIT cfdisk didn't overwrite the old install. I'll try again.
Last edited by Jonnothin (2013-05-22 18:45:56)
Offline
What command/method did you use to reformat? As it appears to have not worked.
Offline
I'm using the default mirrorlist. Also my idea didn't work. I thought that maybe somehow the old arch install that was there was somehow interfering, but that can't be it, I reformated it.
Are you sure? Because this really doesn't look like a fresh install... See Opt1mus's comment above.
All the best,
-Sam
Last edited by HalosGhost (2013-05-22 18:46:08)
Offline
cfdisk didn't overwrite it. I'll try reformating again.
Offline
cfdisk *shoudn't* reformat it, that is jsut creating the partition. You need to make a new filesystem.
Offline
Okay, it works now.
It was the old arch install. I used cfdisk to delete the partition and put the table back the way it was and then used mkfs.ext4.
Thanks for all the help!
...Today must not be my day for computers...
Offline
[...] I used cfdisk to delete the partition and put the table back the way it was[...]
This was completely unnecessary/redundant, all you needed to do was use mkfs on the relevant partition/s.
-- edit spelling --
Last edited by opt1mus (2013-05-22 19:09:45)
Offline
Either way, if you have the problem worked out, please add [Solved] to the beginning of your thread title.
All the best,
-HG
Offline
@Opt1mus Thanks. I remember that next time hopefully.
@HalosGhost Will do.
Offline
Pages: 1