Those following changes must be made before 2016/09/30

All the package with the suffix -nosystemd are renamed to the same name but without the suffix, it means e.g foo-nosystemd become foo.

A special repository named staging was made to permit the change smoothly.This repository must be placed before all other repo onto your pacman.conf. It will be erased at the end of this month. To enable it, add this entry onto your pacman.conf
[staging]
SigLevel = PackageRequired
Server = https://www.obarun.org/src/$arch/staging
After the date 2016/09/30, all the package from staging will be pushed on obarun repository, then the repository staging will be removed and all the packages from obarun repository with the suffix -nosystemd will be erased.
Do not forget, pacman choose a package in function of the first repository where it found him, so always place obarun-testing and obarun repositories before all other if you do not want trouble on your system.

How to

Firstly, you need to be sure that your system is up to date. Some packages were rebuild to avoid troubles with the change, in particular package service.
$ sudo pacman -Syy
The filesystem-obarun was renamed to filesystem. You must udpate this package before all other. You MUST install the package with root user (not root privilege), so don't use sudo but change you user by root user :
 $ su root
then update the package
$ pacman -S filesystem
Pacman ask you if you want to replace the package filesystem-obarun, answer yes.

Pacman make a backup of the following files if you have modified it (e.g. if you have not changing the file hosts, the package do not create hosts.pacsave) :
/etc/fstab
/etc/crypttab
/etc/group
/etc/hosts
/etc/ld.so.conf
/etc/passwd
/etc/shadow
/etc/gshadow
/etc/resolv.conf
/etc/motd
/etc/nsswitch.conf
/etc/shells
/etc/host.conf
/etc/securetty
/etc/profile
/etc/issue

rename all finding xxx.pacsave to xxx e.g. /etc/fstab.pacsave become /etc/fstab. All the change must be made before exit from root user or reboot in particular the file passwd gshadow shadow group fstab.

Then deconnect from root user
$ exit
Now you are ready to update all other package. A multiple way can be apply to make the change , depends of your preference, your skill, your system etc. For example to make it automaticaly, try this:
$ for i in $(pacman -Slq staging); do trap exit_ INT ERR QUIT KILL STOP TERM;exit_(){ break };export exit_;sudo pacman -S $i;done
pacman ask you if you want to replace package e.g. foo-nosystemd by foo. Answer yes for all.
In general way, If you have a trouble concerning dependencies just remove the package which cause trouble and replace it e.g:
$ sudo pacman -Rdd foo-nosystemd
$ sudo pacman -S foo
Don't hesitate to post any question before make the change if you are not sure :)

Note : all these new packages were build with obarun-build build features ( ho yes, we can make now : $ obarun-build build foo :) ). It means, a fresh container is created with the base group and base-devel group installed on it, then the package is builded on it and the resulting package is saved e.g. lt /var/cache/obarun/pkg. Very, very safe for the host and to found dependencies trouble ( last example is sddm with libdbus)
ok.. seemed to get through that in one piece..
but.. did end up with some stuff i didnt have before....
eg networkmanager, pulseaudio, udisks/2, qt4, qt5, sddm, nouveau, + :O
thought maybe something going on with dependency resolution there?
but now realise that the command provided just grabs everything from staging regardless of being installed or not
no biggie just did some -Rsc ing that cleaned up most of it...

am gettting this:
:: Replace procps-ng with staging/procps-ng? [Y/n] y
resolving dependencies...
looking for conflicting packages...

Packages (2) procps-ng-3.3.12-1  procps-ng-3.3.12-1 [removal]

Total Installed Size:   1.16 MiB
Net Upgrade Size:      -1.16 MiB

:: Proceed with installation? [Y/n] y
(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%
(2/2) checking available disk space                [# #####################] 100%
:: Processing package changes...
(1/1) removing procps-ng                           [# #####################] 100%
error: could not remove database entry procps-ng-3.3.12-1
error: could not remove entry 'procps-ng' from cache
(1/1) reinstalling procps-ng                       [# #####################] 100%
after pacman -R it and removing the cached package then installing still getting
:: Replace procps-ng with staging/procps-ng? [Y/n]
even though it looks like its your version
% pacman -Qi procps-ng
Name            : procps-ng
Version         : 3.3.12-1
Description     : Utilities for monitoring your system and its processes
Architecture    : x86_64
URL             : https://gitlab.com/procps-ng/procps
Licenses        : GPL  LGPL
Groups          : base
Provides        : procps-ng=3.3.12  sysvinit-tools
Depends On      : ncurses
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : procps-ng  sysvinit-tools  sysctl-default-conf
Replaces        : procps-ng  sysvinit-tools  sysctl-default-conf
Installed Size  : 1185.00 KiB
Packager        : Eric Vidal <eric@ obarun.org>
Build Date      : Wed 07 Sep 2016 22:48:17 AEST
Install Date    : Sat 10 Sep 2016 12:24:49 AEST
Install Reason  : Explicitly installed
Install Script  : Yes
Validated By    : Signature
eric wrote
$ for i in $(pacman -Slq staging); do trap exit_ INT ERR QUIT KILL STOP TERM;exit_(){ break };export exit_;sudo pacman -S $i;done
ncmprhnsbl wrotebut now realise that the command provided just grabs everything from staging regardless of being installed or not
A better approach is to do this instead:
pacman -S $(pacman -Qqs nosystemd | sed -e s,-nosystemd\,, | tr '\n' ' ') 
Precaution: It is advised to perform the above command as root in a tty console (ergo, not xorg/wayland)

What this command does:
First pacman (-Qqs) will quietly output every nosystemd package installed on the system, (sed -e) will then remove the -nosystemd suffix from the pacman output , next (tr) will reorder the (sed) result in a clean fashion to be [re]installed, Finally pacman (-S) would ask to replace each package with its new varient from obarun [0] [1]. Consequentially pacman will backup altered files from the old (-nosystemd) packages in /etc/ as *.pacsave.

What this command does not:
Other than pacman interactively prompting you to replace each package, it doesn't hand hold. at all. This means you are solely responsible to move pacsave files to their original just as you did for filesystem-obarun. I'm not held liable if pacman fails in any way (e.g fails to install a dependency before/after another, or not at all).

For safety measures, to make sure it will come from the obarun repo before proceeding to migrate (if you haven't already resynced and reordered obarun first in pacman.conf), add a 'p' after -S (without spaces or quotes). -p will output the url of each package, verify that its obarun.org.

NOTICE: The above method works best for minimal systems, it is strongly advised to manually migrate each package group with bloated dependencies instead. As some packages may need to be reinstalled before any other packages.
ncmprhnsbl wrote
Replace procps-ng with staging/procps-ng?
Edit: I can reproduce your issue, But do not worry about about it, it is trying to replace procps from the local database, perhaps an issue with the procps-ng package by obarun [2]. or libalpm [3]. However I'm sure it's the former. commit pushed, waiting for repackaging. In the meantime select "no" at this prompt unless addressed otherwise by eric.
taco@ zen ~ % pacman -Sl staging| grep procps 
staging procps-ng 3.3.12-1 [installed]
taco@ zen ~ % 
Also be advised, The staging repo is only for migration. Nothing more. after 09/30 its safe to remove from pacman.conf if: pacman -Qs nosystemd returns 1


[0] https://www.archlinux.org/pacman/pacman.8.html
[1] http://explainshell.com/explain?cmd=sed+-e+s%2C-nosystemd\%2C%2C+|+tr+%27\n%27+%27+%27
[2] https://github.com/Obarun/obarun-pkgbuild/commit/c9d059f300b550a14cd5573666b9d5d12a715473
[3] https://github.com/anthraxx/pacman/blob/master/lib/libalpm/remove.c# L710
@ ncmprhnsbl
thanks for the report, the trouble shoulb de solved.

@ bit
that is a real post, thanks you to taking the time to do it. :)
13 days later
Hello Eric,
What is the reason for the file name changes that happens this month?
Will you create new ISOs after the file name changes?
I plan to setup a laptop with obarun after the name change.

Thank you for your devotion to obarun.
klaatu
@ What is the reason for the file name changes that happens this month?

to facilitate the dependencies intallation process, example if you want to install accountsservice you need to install first polkit-nosystemd. With the new names of packages you don't need to take care about dependencies, when you install accountsservice pacman take automaticaly polkit from obarun repo.

@ Will you create new ISOs after the file name changes?
yes, i will make a new ISO version after the 2016/09/30
Looking forward to the new ISO! Me and two computers can hardly wait till October...

Powered by Obarun