francois wrote:Nice to read that pacaur and cower are now in manjaro repo.
not much use without a functioning development module...
francois wrote:Replacing the old modules by the more recent ones and keeping my xfce installation with the additional modules and save changes folder, would you say that my nemesis installation will survive or do I have to build anew the complete desktop and modules?
there are ways and there are ways
depending on what is where... so not build anew but upgrade individually:
myself: how i do it: for example: (note i dont use changes at all)
when i do pacman -Syu
i stop(n) and cross check each module via /mnt/live/memory/images/<module>.xzm/var/lib/pacman/local/
to find which package belongs in which module...
eg.
<package(S)toupgrade> is in module foo.xzm
# xzm2dir /path/to/foo.xzm /tmp/foo (i keep each module extracted (in a dedicated partition) to apply the update to, before compressing it(good idea if you have big modules and small ram))
# cp /var/ib/pacman/local/ALPM_DB_VERSION /tmp/foo /var/ib/pacman/local/ (to enable package installation)
# pacman -Sw <package(s)toupgrade (this downloads to cache but doesnt install(make sure there are no other packages in there)
# pacman -Uddr /tmp/foo /var/cache/pacman/pkg/*.pkg.tar.xz (installs any package in the cache to /tmp/foo)
# rm /tmp/foo/var/ib/pacman/local/ALPM_DB_VERSION (not needed any more)
# cd /tmp
# dir2xzm tmp/foo foo.xzm (then replace your old modlue with this)
# rm /var/cache/pacman/pkg/* (clean the cache before doing the next module)
your changes folder should (mostly)only be a problem if it has programs installed into it, that are in other modules...
Code: Select all
cryptsetup: /usr/bin/cryptsetup exists in filesystem
# pacman -Qo /usr/bin/cryptsetup tells me: error: No package owns /usr/bin/cryptsetup
further investigation shows the it is in the kernel.xzm, unattached to a package...
https://www.archlinux.org/packages/core ... ryptsetup/ required by
make me wonder what you have installed that requires cryptsetup package...
# pacman -Qi cryptsetup should tell you in the 'Required By:" line
likewise, networkmanager is in the core module and should be up to date... find and remove it from your module or changes(but not core):
#pacman -Rddr /tmp/foo networkmanager (where /tmp/foo is your extracted module)
if its in changes, then boot without changes(alway fresh) and:
pacman -Rddr /path /to/changes networkmanager
in both cases you (may) need to copy the /var/ib/pacman/local/ALPM_DB_VERSION from your live system first...
as of today, the outstanding package upgrades are:
core: openvpn
gui: mhwd mhwd-db xterm
francois wrote:I do not bootup directry into the desktop environment as before. I have to enter login and password.
this could have something to do with elogind replacing consolekit
