New version of the client published in debian repo package list before it's really available
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
This happens to me pretty much every time a new version of the client is released in your debian repository: the package is marked as available in the package list but when I try to download it I get an error 404. Usually after some hours the problem disappear but this is somehow annoying as it breaks the update process when started from the desktop notify icon (in order to download the other upgrades I have to explicitly deselect the keybase one).
Could you make sure that you update the package list only after the new version of the package is really available?
Contributor guide
No contributing guide indexed for this repository
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 by tracing the Debian repository publishing workflow to compare when the package list is updated with when the new client package becomes downloadable. Done means the package list advertises the new version only after the package is available, so desktop-initiated updates no longer hit a 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, go
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100