On Wed, Nov 23, 2016 at 01:30:52PM -0500, Matthew Miller wrote:
Unfortunately, an update to RPM got pushed out to F24 and hasn't hit F25 yet, resulting in this temporary bug. (Ironically, would have been fine on a *not* fully-updated system.)
Update: Adam from QA tells me that Release Engineering just pushed out the F25 update, so... in a few hours as mirrors catch up, this problem will go away.