-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 22 Jan 2015 15:15:48 +0100 Miroslav Suchý <msuchy@xxxxxxxxxx> wrote: > I just spoke with two members of DNF team about default usage of DNF > in mock. I would like to share outcomes of this meeting. > > First I would like to state that you can already optionally use DNF > in your mock by setting: config_opts['package_manager'] = 'dnf' > in your > /etc/mock/site-defaults.cfg > It is present in mock for half a year and all known problems have > been resolved for some time. You can even set this option per chroot > target. E.g. put this line only in /etc/mock/fedora-rawhide-x86_64.cfg > and then only rawhide-x86_64 builds will use dnf while everything > else will use yum. > > DNF should be default packager manager in Fedora 22, so I started > thinking how it affects mock. > > I have a notion, that after branching of Fedora 22 I will change > /etc/mock/fedora-rawhide-*.cfg > to use DNF by default. I.e. everything build for Fedora 23 would use > DNF for building. This is not really true. Koji write out its own mock configs and will not be using dnf for any operations. for anytime soon. koji hass no way to use different tools to install chroots we will continue to use yum to install the buildroots for the foreseeable future. so it would mean that locally your builds would use dnf but in koji they will use yum. > > At the outset I thought that we use yum for older targets (epel-7, > fedora-22..) indefinitely. Or to be precise until those targets will > be EOLed. But that would imply that yum have to be present in Fedora > until Fedora 40 [1]. This is very unlikely to happen. More realistic > expectation is that yum will disappear around Fedora 27 [2]. Which > means that in Fedora 27 you either will be unable to build packages > for epel-7 or you will have to use DNF. This is quite distant future > and we will try our best to make this transition as much flawless as > possible. I just want to make you aware in advance. Of course if you > want to help, you are very welcome. we use the same builders in fedora to go all the way back to epel5 and we need to ensure things still work. > > I expect that we will be building Fedora 22- always by yum due to > short Fedora life cycle. Yum will be still present in Fedora 24 for > sure. I am happy to sit down with you at devconf and talk about how things work for building fedora to make sure that you keep the use cases we have in releng in mind when developing mock as right now we feel like we are being served very poorly by upstream mock. There is many things to keep in mind and we need to move forward. we just need to do better about not breaking existing things that work today. > [1] > https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates > [2] It’s Difficult to Make Predictions, Especially About the Future > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUwRAjAAoJEH7ltONmPFDR9TsQAJYzaq/fMNJXbCJxFiI6kFV5 PJeBkbkI6o+1Wib0Anrpw1J+uU91i4WF+z796Xj4Y9EEace42T6w3v1Ax3FLyw7j KNs4paRpSIgw/UCDXXGFh0MuOHt+CS7eTnLFCct/cxKE2Uqe5/33VSETw0H3DfzV qN/WARnSfFzreGIgxID/VoYsHmtxLtpbA49SbPbzk9gkXPOcDkzbJiG9lprVYmpx U43pREU795V5K4GMtyR+3Mmju4i3ep1lq4amP634Tm8nlBoTPBYdSmv5P+ppxQDr CCwDiUbc6GLUqei9jnu9MkzK8uh2pQU2p4EXUDicz3CfnDWINpILem/ZX+rb2zxf WV877UDTpOacwdvuCbEqvV4a6J3uILgpsmGUyVjbOx1Cuw82UyAbgIijMVfk2bEu eB7R24hCYmpPvWmATqFzY+kC8+FYw4TvHSWoPBqxc5D6lzyRZlJ2eUfNrpr0uy0K iOssP9bmfIFeTOlA8nsCoLA7MdTJpHqcAQW8wZmZSxWNubXM8Y+3PNgm6YpzTvJW lY4rPz3g4j0o24f6dIjomg7xKJZ/5Or6zTEFDZ4tO2MUygg/CVJVrxgoN2bcU2c+ sGbkQ/w10gs/ZTCLe2z0cGMRzWxUxKbAE5GCt4PLnIDpOt9+CnEPCqgQmJPZxba+ ORownjw1ZLrUPl9dkTsq =Ckmm -----END PGP SIGNATURE----- -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
