El jue, 27-04-2017 a las 10:16 +0200, Vít Ondruch escribió: > > 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? Probably we will need 3-4 weeks at least.
> > > 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. There may be various reasons why. we have a flag for run root tasks to use --new-chroot or not currently because some of the tasks work just fine in a chroot and not in a nspawn container while others do not run at all in chroot and need to be run in a container of some form. It is messy and the change needs to be coordinated and its more than just Fedora rel-eng but koji devs as well. > To be honest, I experience some issues with RHEL6 buildroot on my > Rawhide. For example, this does not work: > weird cases like Vit experienced is why. Dennis
signature.asc
Description: This is a digitally signed message part
_______________________________________________ buildsys mailing list -- [email protected] To unsubscribe send an email to [email protected]
