This is needed for systemd. Any reason not to?
i don't recall any reason not to
amd64 stable
Stable for HPPA PPC64.
x86 stable
ia64 stable
sparc stable
arm stable
ppc stable
Alpha has a new test failure, see bug 564628.
(In reply to Tobias Klausmann from comment #9) seems like 2.25 also fails in this way which means it's not a regression and should not be considered a blocker for stabilization
(In reply to SpanKY from comment #10) > (In reply to Tobias Klausmann from comment #9) > > seems like 2.25 also fails in this way which means it's not a regression and > should not be considered a blocker for stabilization I'm actually considering masking all failing versions and possible resurrecting an old version just for alpha. It's not quite clear at the moment of the test failure correlates with an inability to edit disklabels during installation. If that is the case, we have installation media that are useless: for booting reasons (SRM can only read from disklabel slices), user have to be able to set up BSD disklabels when installing an alpha. I will try and figure this out by the weekend and then update this bug accordingly.
(In reply to Tobias Klausmann from comment #11) does the boot media not actually work, or are you extrapolating from the test failure ?
(In reply to Tobias Klausmann from comment #11) i think you should stabilize this since it's clearly not a regression and 2.26.2 does not negatively impact the status quo. independently, you can investigate the test failure via bug 564628.
(In reply to SpanKY from comment #12) > (In reply to Tobias Klausmann from comment #11) > > does the boot media not actually work, or are you extrapolating from the > test failure ? We've had users report that they are unable to create disklabels with later/latest versions of the utility, mattst88 asked upstream and there was some back and forth on how the *UI* changed. My plan is to do a test/mock install on the weekend to see if the new instructions actually work. If so, I'll make sure we update our docs. Either way, the test failure needs to be reported upstream. I'll see to that, too, unless someone already has done so.
(In reply to SpanKY from comment #13) > (In reply to Tobias Klausmann from comment #11) > > i think you should stabilize this since it's clearly not a regression and > 2.26.2 does not negatively impact the status quo. independently, you can > investigate the test failure via bug 564628. Will do.
2.26.2 is now stable on alpha.