/etc/update-manager/release-upgrades.d configs ignored

Bug #1628891 reported by Jose L. VG on 2016-09-29
This bug affects 2 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)

Bug Description

In my tests the /etc/update-manager/release-upgrades.d directory does not seem to be taken into account for overriding the configuration at:

Testing on trusty, I have tried this file:
# Override prompting behavior to 'never' check for new release

With these names:

rm /var/lib/ubuntu-release-upgrader/release-upgrade-available
root@trelease:~# /usr/lib/ubuntu-release-upgrader/release-upgrade-motd
Will always reproduce the output:
New release '16.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.

While changing /etc/update-manager/release-upgrades does work as expected

Brian Murray (brian-murray) wrote :

Well, the changelog leads one to believe it should work although I haven't found any code that actually checks that directory.

update-manager (1:0.99) jaunty; urgency=low

  [ Michael Vogt ]
  * DistUpgrade/DistUpgradeController.py:
    - enable apport crash capturing during upgrades
  * DistUpgrade/DistUpgradeView.py:
    - create /var/lib/pycentral/pkgremove before the upgrade to
      help pycentral transition to the new python policy (thanks
      to doko)
  * ensure pidgin-libnotify is upgraded (LP: #332328)
  * better wording for aborts (thanks to Gabor Kelemen and
    Jean-Baptiste Lallement), LP: #289303
  * wording fixes, thanks to Brian Murray and Gabor Kelemen
    LP: #269583
  * i18n fix, thanks to Gabor Kelemen, LP: #331821
  * support /etc/update-manager/release-upgrades.d/ directory
    for local overrides of the upgrade process. Useful to force
    certain site-specific options (like third party repository

Changed in update-manager (Ubuntu):
status: New → Triaged
importance: Undecided → Low
tags: added: trusty yakkety
Björn (bjmi) wrote :

This issue still exists in Ubuntu Bionic.

After several tries to override
with a file placed in
this issue come to my resuce let me stop searching for an error on my side.

Maybe this issue could be planned for the next release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers