On Thu, Sep 20, 2018 at 04:20:49PM +0200, Adam Samalik wrote: > > > And when that module is EOL, what is the user experience? > > What I described in my reply earlier: the upgrade should not work and > > the user should be required to switch to a new stream on their current > > environment first. Which, of course, implies that we need a policy > > requiring overlap. > > Or a way of specifying a target stream during the update. One possibility would be to add "--upgrade-obsolete-modules". But I'm not liking that because we get into a circus of: 1. Trying dnf-upgrade download 2. Get errors 3. Add --allowerasing --best 4. Try again 5. Get errors 6. Seriously though, remove some i386 packages 7. Try again 8. Oh, now my modules are failing. 9. Add another option. 10. Try again? I mean, at this rate, we're never going to get to ???, let alone "profit!" -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
