/etc/update-manager/release-upgrades.d configs ignored
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-manager (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
In my tests the /etc/update-
/etc/update-
Testing on trusty, I have tried this file:
[DEFAULT]
# Override prompting behavior to 'never' check for new release
Prompt=never
With these names:
/etc/update-
&
/etc/update-
And:
rm /var/lib/
root@trelease:~# /usr/lib/
Will always reproduce the output:
New release '16.04.1 LTS' available.
Run 'do-release-
While changing /etc/update-
| Brian Murray (brian-murray) wrote | #1 |
| Changed in update-manager (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: trusty yakkety |
| Björn (bjmi) wrote | #2 |
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/
- enable apport crash capturing during upgrades
* DistUpgrade/
- create /var/lib/
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-
for local overrides of the upgrade process. Useful to force
certain site-specific options (like third party repository
handling)