Bug 2229991 - No option to pin version(s) to keep when using install_only feature
Summary: No option to pin version(s) to keep when using install_only feature
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 38
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jaroslav Rohel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-08 12:18 UTC by Arne Blankerts
Modified: 2023-08-09 09:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Arne Blankerts 2023-08-08 12:18:50 UTC
Description of problem:

Back with YUM and it's "famous" yumdb, one could mark a specific package to be kept, even when the respective install_only_limit was reached: `yumdb set installonly keep EXACT_PKG_AND_VERSION_TO_KEEP`.

That lead to the oldest non-marked version to be removed when installing a newer one after the install only limit was reached. Since the removal of YUMDB, there seems to be no such option anymore.

While DNF has explicit handling code to ensure the running kernel is never removed, there is no way to ensure the same for other packages installed/marked as "installonly". 

Additional Note:

- The general install-only feature works like charm

- This is NOT the same as `versionlock` as updates should still be installed, but the running version needs to be kept (hence, the use of the install-only feature and, previously, setting the appropriate key in yumdb).

- I looked into creating a plugin to provide this functionality but I cannot find a means to overrule the decision to simply remove the oldest variant of an installed package


Note You need to log in before you can comment on or make changes to this bug.