You are not logged in.
Rebuilding everything from source using abs with customized compiler flags and I stumbled across this issue.
==> WARNING: cryptsetup conflicts with those packages:
- mkinitcpio
==> Do you want to remove them with "pacman -Rd" ? [y/N]
==> -----------------------------------------------------
==>This only comes up when installing cryptsetup after mkinitcpio is already installed. If I install mkinitcpio after cryptsetup theres no warning.
So basically what should I do? Why does cryptsetup conflict with mkinitcpio? It it safe to ignore the warning and keep mkinitcpio anyway? Should I remove mkinitcpio with -Rd first then reinstall it afterwards?
Last edited by tjwoosta (2010-07-27 18:40:24)
Offline
Whats the version of your mkinitcpio? Cryptsetup has this in its PKGBUILD:
conflicts=('mkinitcpio<0.5.99')Offline
I noticed that, and that would make sense, but why is mkinitcpio 0.6.7-1 in core when cryptsetup 1.1.3-1, which is part of base, conflicts with it? Theres no warning or anything if you install cryptsetup with base then add mkinitcpio afterwards when recompiling your kernel or something, becasue the mkinitcpio pkgbuild doesnt specify it as a conflict. The only reason I noticed was because Im recompiling everything and cryptsetup came up.
Is there any chance that the < is supposed to be a > ?
Last edited by tjwoosta (2010-07-27 17:38:47)
Offline
"<" means less than, so it seems fine. Cryptsetup conflicts with mkinitcpio less than version 0.5.99.
Offline
Offline
Ahh, ok I see now, your right it works with makepkg and pacman. It seems yaourt isnt interpreting the inequality symbols for conflicts properly. The same thing just happened with another package (device-mapper).
It would also appear that you're not using Pacman. Use Pacman.
I would just use pacman and makepkg but its much easier to use yaourt for rebuilding the whole system.
for i in $(pacman -Q); do yaourt -Sb $i; doneA bit sloppy but it does the job, I just have to start ignoring the screwed up conflicts.
Offline