Bug 126436 - RFE: Package holds.
RFE: Package holds.
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2004-06-21 12:41 EDT by Josh Rollyson
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-21 15:20:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Josh Rollyson 2004-06-21 12:41:44 EDT
126394 was closed without an acceptable resolution. Resubmitting.

The entire *point* is to prevent automated processes and careless
administrators from touching a package that for whatever reason
shouldn't be touched. In order to be an effective policy tool, rpmlib
would be the place to implement, not in the automated upgrade tools.

Without package holds, the only way I know of to accomplish this is to
either render some of the files unwriteable, or create dummy packages
that prevent the undesireable situations with impossibly high version
numbers, or with conflicts, which is messy. 

 Opened by Josh Rollyson (jrollyson@2mbit.com) on 2004-06-21 03:16

One of the most useful features I've seen from dpkg is "package holds".

By setting a package hold, all package manager operations that change
the state of a package will fail without an override option on the
command line. This prevents inadvertant changes to a package that for
some reason or another should not be changed on a system, as decided
by the system's administrator.

I've used this functionality in the past on *.deb based distributions
to insure that packages that I've customized do not get replaced
during upgrades - while apt-rpm has its own hold mechinism, this
doesn't do anything to address other upgrade mechinisms, or other
administrators manually installing/updating a package.

I've also used this functionality on .deb based distributions to
insure that a package that breaks the system in some way or causes
some security problem doesn't get installed. 

I would suggest that a configuration file is the best way to go about
implementing package holds, since such a list is not likely to change
frequently on a production system.

------- Additional Comment #1 From Jeff Johnson (jbj@redhat.com) on
2004-06-21 09:28 -------

Sure, policy concepts like
    Never change this file.
    Never change this package.
provide a degree of comfort to to system administrators.

Both policies are implemented in up2date, which is largely
concerned with upgrades.

Neither policy is implemented in rpmlib, mainly because
"hold" eill stop anaconda from upgrading an end-user system,
thereby creating a support problem.
Comment 1 Jeff Johnson 2004-06-21 15:20:25 EDT
N-O, read both letters carefully.

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