unattended-upgrades and debconf
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 200
- Forks
- 253
- Avg merge
- 5h 19m
- Merged PRs (30d)
- 1
Description
If the unattended_upgrades package is already installed, the debconf seed never gets seeded and auto-updates will never get enabled:
https://github.com/chef-cookbooks/apt/blob/master/recipes/unattended-upgrades.rb#L27
Systems initially provisioned by cloud-init (like recently at DigitalOcean) already have unattended_upgrades installed and auto-update disabled.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with recipes/unattended-upgrades.rb at the linked section and inspect how the cookbook handles an already-installed unattended_upgrades package and debconf seeding. Reproduce the cloud-init scenario with automatic updates disabled, then verify that the debconf seed is applied and auto-updates become enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, ruby
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100