Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 109010: Ignore dpkg hold on upgrade #127

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Bug 109010: Ignore dpkg hold on upgrade #127

wants to merge 1 commit into from

Conversation

mss
Copy link
Contributor

@mss mss commented Jul 13, 2018

This is a suggested change to improve the handling of upgrades on systems where the Zimbra packages are pinned/marked for hold.

To avoid accidental updates of Zimbra packages together with regular system updates, these can be marked for hold via the command
apt-mark hold 'zimbra-*'

Zimbra updates can be installed via an explicit
apt-get upgrade --ignore-hold --only-upgrade 'zimbra-*'

Upgrading using the installer will fail though unless an explicit
apt-mark unhold 'zimbra-*'
was executed beforehand.

This patch makes the installer ignore the hold states so updates go more smoothly.

This only affects Debian/Ubuntu for Red Hat/CentOS a similar logic would have to be implemented.

I tested this on Ubuntu 16.04 and via the manpages I verified that the added options --ignore-hold for apt-get and --force-hold for dpkg are available on Ubuntu 14.04 as well.

To avoid accidental updates of Zimbra packages together with regular
system updates, these can be marked for hold via the command
  apt-mark hold 'zimbra-*'

Zimbra updates can be installed via an explicit
  apt-get upgrade --ignore-hold --only-upgrade 'zimbra-*'

Upgrading using the installer will fail though unless an explicit
  apt-mark unhold 'zimbra-*'
was executed beforehand.

This patch makes the installer ignore the hold states so updates go more
smoothly.

This only affects Debian/Ubuntu for Red Hat/CentOS a similar logic would
have to be implemented.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant