Change: Disable Vendor Change by Default #3643
Labels
No labels
document it
fast track
meeting
next release
nonresponsive maintainer
packager revocation
pending announcement
provenpackager
python 2 exception
self contained change
stalled
Status
Accepted
Status
Duplicate
Status
Insufficient data
Status
Invalid
Status
Rejected
system wide change
updates policy exception
vote-in-progress
No milestone
No project
No assignees
6 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
fesco/tickets#3643
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Change the default configuration of DNF5/libdnf5 by setting allow_vendor_change=False via the distribution defaults file /usr/share/dnf5/libdnf.conf.d/20-fedora-defaults.conf. This prevents libdnf5 from automatically replacing an installed package from one vendor with a package from another vendor during any transaction (such as upgrades, downgrades, or dependency resolution), unless explicitly requested by the user or allowed by VendorChangeManager rules.
Owners, do not implement this work until the FESCo vote has explicitly ended.
When a FESCo member has marked this ticket as APPROVED, you may proceed with the implementation. See the FESCo ticket policy and the Changes policy for more information.
If no decision has been rendered after 7 days from the filing of this ticket and no indication (such as a -1 vote) that this will be taken up at a FESCo meeting, please feel free to ping for a status update.
REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the Fedora Devel mailing list.
+1
+1
I think that there are some corner cases which might require some custom handling, but they should be figured out during implementation.
I think it would be better to exempt all Copr packages from this and allow individual projects that are shipping alternative content (e.g., Asahi Remix) to ship their own overrides, either via a configuration file override include in a
foo-releasepackage or a Copr setting that gets handled bydnf5 copr(if that gets implemented). It sounds like many people would find it surprising to get stuck forever on a Copr version, since Coprs are very often used for testing purposes.Such a default would break Fedora Asahi Remix, who currently configures DNF with sticky vendors by default and has since its inception. I think it would make more sense for the Copr plugin to create such configuration on demand when a copr is being enabled if the Copr is configured for this (maybe make it a new default so people can switch it back off).
+1
+1
After a week: APPROVED (+4, 0, 0)
I'll include the announcement in today's agenda.