Re: EOL and Obsoletes in Modularity

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Oct 29, 2020 at 8:17 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
>
> On 10/29/20 12:43 PM, Petr Pisar wrote:
> >> OTOH If the EOL date is informational only (Anna keeps postgresql:9.5 but
> >> sees a warning during dnf upgrades) and the obsoletes only actually happen
> >> on a specific user action (and on release boundary), great.
>  >
> > That's how it is suspposed to work. Read "Proposed dnf behavior" in
> > <https://fedoraproject.org/wiki/Changes/Module_Obsoletes_and_EOL>.
>
> Indeed, in that case a mid-release EOL makes sense, sorry for the confusion.
>

Ideally, DNF could have different policy modes for EOLs. By default
it could throw warnings about using EOL content and still let you
install it, but in a mass-managed scenario, the policy could be
switched to enforcing (if you haven't already installed it, you
can't).




--
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux