Dne 27.4.2017 v 09:38 Miroslav Suchý napsal(a):
Dne 26.4.2017 v 20:35 Dennis Gilmore napsal(a):
> Please do not push this stable until there has been sufficient time to
> test in koji and possibly develop new features in koji to make
OK, I switched off "Auto-request stable" for now. Well kind off. I
discovered it cannot be switched off once set [1], but I raised the
karma treshold to very high number.
[1]
https://github.com/fedora-infra/bodhi/issues/1482
How many days you need for testing? Is one week enough?
> supporting chroot or systemd-nspawn configurable per tag/target
Why would you enable/disable nspawn per chroot? It does not make sense
to me.
You can even build EL5 build inside of nspawn. What is important is
the host, not the target.
To be honest, I experience some issues with RHEL6 buildroot on my
Rawhide. For example, this does not work:
~~~
$ mock -r rhel-6-x86_64 shell --unpriv --new-chroot
INFO: mock.py version 1.4.1 starting (python version = 3.6.1)...
Start: init plugins
INFO: selinux disabled
Finish: init plugins
Start: init plugins
INFO: selinux disabled
Finish: init plugins
Start: run
Start: chroot init
INFO: LVM plugin enabled. Allocated pool data: 51.41%. Allocated
metadata: 28.79%.
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled yum cache
Start: cleaning yum metadata
Finish: cleaning yum metadata
INFO: enabled HW Info plugin
Finish: chroot init
INFO: Installed packages:
Start: shell
Child died too early.
getent initgroups failed with error code 1.
Failed to parse group data from getent.
Finish: shell
~~~
while '--old-chroot' works just fine. I did not bothered too much to
analyze, but I'd be cautious.
Vít