<p dir="ltr"><br>
On Sep 9, 2015 1:58 PM, "Paul Smith" <<a href="mailto:phhs80@gmail.com">phhs80@gmail.com</a>> wrote:<br>
><br>
> On Wed, Sep 9, 2015 at 7:26 PM, Joe Zeff <<a href="mailto:joe@zeff.us">joe@zeff.us</a>> wrote:<br>
> >><br>
> >> on a F21 machine, there occured a power cut. And now I cannot boot the<br>
> >> machine, and when I use the rescue mode and try to run again<br>
> >><br>
> >> yum update<br>
> ><br>
> ><br>
> > I know I'm coming in late, and judging from other replies this probably<br>
> > won't work, but have you tried yum-complete-transaction? I'd suggest using<br>
> > --skip-broken, but that only checks for certain errors in the files rather<br>
> > than doing what the name implies.<br>
> ><br>
> > Going off-topic for a moment, and presuming that dnf acts the same way (I<br>
> > don't, as yet, have a box using it.) should there be a bugzilla either<br>
> > complaining that the switch doesn't actually do what it says (e.g., skipping<br>
> > to the next package if this one is broken instead of only being able to pull<br>
> > it out of the transaction if the signature (I think it is.) doesn't match.)<br>
> > or requesting that it be renamed to something more appropriate, with the<br>
> > current switch being left as an alias for the correct one to keep scripts<br>
> > from breaking. I'm neutral on the subject, although I'd prefer that<br>
> > something be done to keep people from wasting time trying in cases where it<br>
> > doesn't apply.<br>
><br>
> Thanks, Joe. I have just tried<br>
><br>
> yum-complete-transaction<br>
><br>
> but with no success: the error message ("/lib64/libidn.so.11: file too short").<br>
><br>
> Paul<br>
> --<br>
> </p>
<p dir="ltr">Fix whatever is dropping you into rescue mode, *then* do package updates. One problem at a time, or you will get lost in the overlap.</p>
<p dir="ltr">--Pete</p>