Re: What should we do about the "Install only newly recommended packages on upgrades" F36 change?

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

 



On 07. 02. 22 15:17, Miro Hrončok wrote:
Hello,

this is about the following Fedora change:

https://fedoraproject.org/wiki/Changes/ExcludeFromWeakAutodetect

In the tracking bugzilla, the relevant comment is:

https://bugzilla.redhat.com/show_bug.cgi?id=2013327#c4

If I understand this correctly, the current implementation is not doing what the change described and the change owner says the feature cannot be implemented as described.

There are several options and we should probably decide what to do before beta freeze. Hence opening this discussion.

The change summarizes as "We would like to change a default behavior dnf/PackageKit/microdnf to install only newly recommended packages on upgrades." however the current impementation disbales weak depndencies in various other scenarios, as reported by various of our packagers e.g. in

Bug 2048394 - dnf should pull weak dependencies in install transaction
Bug 2033130 - exclude_from_weak_autodetect=true effectively renders rich weak dependencies useless
Bug 2042808 - weakdeps not working on rawhide system

The change owner proposed 4 options to move forward. I understand them as follows:

And here I am to reply to myself.

1. do nothing, keep it broken

I pretty much dislike this option. Clearly, the current behavior is not what was approved in this change proposal. For me, it's a bad option.

2. disable this behavior by default, keep it optional, but keep it broken

This only makes sense if it's likely to get fixed and enabled again in later Fedora release. If the plan is to disable it by default and never touch it again, I suppose we might as well revert it entirely. I would very much to see the change happening as it was advertised, even if we cannot make ti to Fedora 36.

For the sake of an open minded discussion, I am ignoring the fact that the change owners themselves don't consider it doable (I think that it is doable, but I honestly don't know if it is realistic with the current resources).

3. do not ignore already broken weak rich deps (partially reverts the change)

This sounds like a possible path forward -- it would probably still be an improvement over the the Fedora 35 status quo, however the results might be quite surprising for the users. If we decide to do this, I think we should postpone to Fedora 37 neverthelss to see it in action and figure out if it's actually a good idea or an UX nightmare.

4. change the behavior on dynamically depending on the dnf command used (discouraged)

As stated by the change owner in the bugzilla, this is probably not a good idea. Even when the user types `dnf install` it sometimes upgrades some already installed packages and even if they type `dnf upgrade` it sometimes installs some new packages.

(Go see the linked comment for details.)

Please let us know what you think is best or if there is a better solution.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[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