Patch Manager does not honor apt priority
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 357
- PR merge metrics
- No merged PRs in 30d
Description
This is specifically about backport packages and how mindlessly installing backports gets into a dependency hell, along with broken functionality.
By default Debian sets backports to priority 100, whereas regular repos are at 500. So backport packages are not candidates for install in apt. Yet SSM patch manager will gleefully install these backports.
The only workaround is to add a wildcard reject for anything that's got `~bpoX+Y`, so that's multiple entries for Debian9 and 10 (11 when?) and +1,2,3,etc... Haven't checked ubuntu yet.
Contributor guide
Research direction
Start by reproducing the issue with Debian backports enabled and compare the repository priorities with the packages selected by SSM Patch Manager. Trace the patch-selection path in the Go agent; done means backport packages are not selected when apt gives them lower priority, without requiring wildcard rejects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100