On 05/30/2017 12:16 PM, Dusty Mabe wrote: > > > On 05/30/2017 10:58 AM, Jonathan Lebon wrote: >> Hi, >> >> If I understand correctly, in its current state, F26 AH will >> be shipping with the atomic package which added the >> rpm-build deps. The update that removes it again is blocked >> in testing: >> >> https://bodhi.fedoraproject.org/updates/FEDORA-2017-ac1919a04b >> >> Double-checking the current state: >> >> $ ostree remote add fedora-26 --no-gpg-verify >> https://kojipkgs.fedoraproject.org/atomic/26/ >> $ ostree pull fedora-26 --subpath=/usr/share/rpm --depth=0 >> fedora/26/x86_64/atomic-host >> >> $ ostree checkout -U --subpath=/usr/share/rpm >> fedora-26:fedora/26/x86_64/atomic-host tmp/rpmdb-26 >> >> >> $ rpm -qa --dbpath $PWD/tmp/rpmdb-26 | grep -E '(rpm-build|gdb)' >> gdb-headless-7.12.50.20170226-4.fc26.x86_64 >> rpm-build-libs-4.13.0.1-4.fc26.x86_64 >> rpm-build-4.13.0.1-4.fc26.x86_64 >> gdbm-1.13-1.fc26.x86_64 >> >> If this is what the F26 AH deliverables will be based on, >> then would it be possible to justify a freeze exception out >> of this? It's a pretty big wart on a new AH release, esp. >> since the motto is that we're a streamlined OS, though it's >> obviously not a critical release blocker. >> > > short answer: no, this is not what FAH 26 will ship with. There is a period > of > 'unfreeze' that happens after the rest of Fedora releases Beta and before > final > is released. > > longer answer: we can open a BZ to get this update excepted and into stable > sooner. > since it only affects atomic host it should be pretty easy to get it > approved. > > I opened a BZ [1] and proposed it as a freeze exception. > > Dusty > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1456901
Accepted as freeze exception. Need one more karma and then it can be pushed to stable on next stable push. Dusty
