Description of Problem: With the new obsoletes functionality, the expected behavior of up2date has changed in a way that was suprising, and could be problematic. Version-Release number of selected component (if applicable): up2date-2.7.61-7.x.1 How Reproducible: 100% Steps to Reproduce: 1. Install a 7.0 machine with LPRng 2. run the initial up2date -- note that cups is not offered 3. run another up2date with the new client -- note that cups is now offered Actual Results: with the 2.7.61-7.x.1 up2date, it tries to upgrade LPRng -> cups Expected Results: the previous behavior where LPRng was kept at errata release levels
working on some server side fixes for this... basically get to blacklist random packages from 6.2-7.3 with bogus useage of Obsoletes.
the server side changes, and the new obsoletes blacklist support should take care of this. Moving to modified.
The given test case works, and I'm going to assume that all instances of this issue have been fixed.