On Thu, 2015-03-05 at 09:15 -0500, Samantha N. Bueno wrote: > On Wed, Mar 04, 2015 at 07:32:44PM -0800, Adam Williamson wrote: > > On Tue, 2015-03-03 at 23:51 -0800, Adam Williamson wrote: > > > Just in case folks don't see the update comment, there's two > > > import issues which result in the new anaconda/blivet being > > > completely broken: > > > > > > https://admin.fedoraproject.org/updates/anaconda-22.20.2-1.fc22 > > > ,python- blivet-1.0.1-1.fc22 > > > > > > Most notably, getPossiblePhysicalExtents() was removed from > > > blivet.devicelibs.lvm without anaconda being adjusted to not use > > > it any more. > > > > > > As we need the update to fix Alpha blockers, it'd be appreciated > > > if we could get fixed builds ASAP, thanks :) > > > > So after some more work on this today, I think it turns out that > > we didn't actually want to send python-blivet 1.0.1 to Alpha at > > all; it was intended to land after Alpha (according to dlehman). > > > > The good news is that, at least so far as I can see, none of the > > changes in anaconda-22.20.2 - the fixes we actually want to get > > into Alpha - depends on python-blivet 1.0.1. So I think for Alpha > > RC1 we can simply take anaconda-22.20.2-1.fc22 and keep python- > > blivet-1.0- 1.fc22 (which is currently in stable). All we need to > > do that is an update which only contains anaconda-22.20.2-1.fc22 > > (no python-blivet). > > Done, here you go: > https://admin.fedoraproject.org/updates/anaconda-22.20.2-1.fc22 > > > The big changes in blivet 1.0.1 can then land after Alpha and > > anaconda can continue adjusting to them. > > > > If we turn out to need further changes to anaconda and/or blivet > > for Alpha, I guess we could branch from anaconda 22.20.2 / blivet > > 1.0 for Alpha, and keep 22.20.3+ and 1.0.1+ as post-Alpha > > development branches. > > > > Does that all sound OK to everyone? If so, it'd be great if > > someone could submit the anaconda-22.20.2-1.fc22 update. Thanks! > > Sounds like a mess, but I guess there isn't a better way. Well, AFAICS the only alternative is to find and fix all the libblockdev bugs for Alpha, but it seemed pretty clear that dlehman didn't intend to land it till Beta. So obviously the lesson here is we should always update anaconda and blivet together, except for when we shouldn't. Easy, right?! :) Honestly I don't think it's too much of a mess, because we never pushed a blivet build post-1.0 stable, so we don't have to do any icky reverts or epoch bumps or anything. In the best case we won't need further builds for Alpha at all and can just carry on from blivet 1.0.2 / anaconda 22.20.3 after Alpha is signed off, and even the branching case isn't really horrible. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
