← Back to team overview

touch-packages team mailing list archive

[Bug 1446552] Re: Unattended upgrades handles new dependencies inconsistently

 

The attachment
"also_adjust_candidate_version_for_non_installed_packages.patch" seems
to be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1446552

Title:
  Unattended upgrades handles new dependencies inconsistently

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  When an installed package adds a dependency that is not yet installed
  on the system, this sometimes causes the package to not be installed,
  depending on the origin containing the original candidate version.

  I believe that the problem is in /usr/bin/unattended-upgrade, line
  102. Here a check is performed to prevent downgrades. However, as a
  side effect it also prevents adjusting the candidate version for
  packages that have not yet been installed (because pkg.is_upgradable
  is False for packages that have not been installed).

  This makes updating private packages using unattended-upgrades
  troublesome, especially when new dependencies have been added.
  Currently it requires repackaging the dependencies with a slightly
  higher version number than what is in the main repository, and then
  hosting them on the private repository, which is time consuming and
  error-prone. With the included patch, it is sufficient to just host
  the same version on the private repository.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1446552/+subscriptions


References