nextcloud / nextcloud/nextcloudpi
ncp-dist-upgrade should also `sed` `/etc/apt/apt.conf.d/20ncp-upgrades`
Open
Beginner friendly
Nobody has claimed this yet.
has-updates
- Dominant language
- Shell
- Stars
- 2.9k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
I today did my long postponed bookworm update and everything went well but I noticed a bullseye leftover:
root@nextcloud:~# cat /etc/apt/apt.conf.d/20ncp-upgrades
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Periodic::MaxAge "14";
APT::Periodic::AutocleanInterval "7";
Unattended-Upgrade::Automatic-Reboot "true";
Unattended-Upgrade::Automatic-Reboot-Time "04:00";
Unattended-Upgrade::Origins-Pattern {
o=Debian,n=bullseye-security;
o=deb.sury.org,n=bullseye-security;
o="Raspberry Pi Foundation",n=bullseye-security;
o="Raspbian",n=bullseye-security;
}
Dpkg::Options {
"--force-confdef";
"--force-confold";
};
// Enable the update/upgrade script, disabled by Armbian in 02-armbian-periodic
APT::Periodic::Enable "1";
root@nextcloud:~#
Merry 🎄
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 the ncp-dist-upgrade entry point and inspect how it updates distribution-specific configuration. Check the generated /etc/apt/apt.conf.d/20ncp-upgrades content during a Bullseye-to-Bookworm upgrade. Done means the configuration no longer retains bullseye references after the upgrade; use the existing upgrade checks or logs to verify the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, shell
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 67/100