Repository navigation
chore: standardise coding - #1546
Merged
philclifford merged 34 commits intoMar 21, 2026
Merged
Conversation
philclifford
force-pushed
the
chore-standardise-coding
branch
3 times, most recently
from
October 19, 2025 23:39
38c93f2 to
02851a4
Compare
philclifford
marked this pull request as ready for review
October 20, 2025 00:55
missed a few over-zealous sed edits
…tern substitution
Signed-off-by: Phil Clifford <philip.clifford@gmail.com>
philclifford
force-pushed
the
chore-standardise-coding
branch
from
February 11, 2026 23:55
e19ae51 to
02cbb10
Compare
This was referenced Feb 13, 2026
Signed-off-by: Phil Clifford <philip.clifford@gmail.com>
Signed-off-by: Phil Clifford <philip.clifford@gmail.com>
This finds the last deb package assets. The later release has confusing nested archive assets and no deb packages. Likely we'll need to de-support if they cannot or will not work out releasing debs again. Signed-off-by: Phil Clifford <philip.clifford@gmail.com>
Contributor
There was a problem hiding this comment.
2 issues found across 1 file (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="01-main/packages/input-leap">
<violation number="1" location="01-main/packages/input-leap:2">
P2: Keep using the GitHub `latest` endpoint here; removing it can make this definition resolve a prerelease asset instead of the latest stable release.</violation>
<violation number="2" location="01-main/packages/input-leap:15">
P2: This fallback URL matcher is broken: `${ARCH}` is undefined in this file, and `browser_download_url.` should be `browser_download_url.*`, so the grep will not find any asset.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
Contributor
|
@philclifford Since you removed Is that some kind of bug triggered by a package that previously existed being removed? |
Member
Author
|
Yes @snoack - |
philclifford
added a commit
to philclifford/deb-get
that referenced
this pull request
Jun 17, 2026
* chore: standardise code - unquote "$()" - remove echoes , tr and sed where feasible - shellcheck linting, typos etc * fix(ipscan): fix typo in case * docs(EXTREPO.md): further align example definitions with standards --------- Signed-off-by: Phil Clifford <philip.clifford@gmail.com> Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
philclifford
pushed a commit
that referenced
this pull request
Aug 20, 2026
Both URL and VERSION_PUBLISHED extraction currently fail, so the package errors out with "Missing required information" and is skipped. VERSION_PUBLISHED used awk's three-argument match(), a gawk extension that errors under mawk, the default awk on Debian and Ubuntu. This regressed in 753bfac (#1546), which reverted the grep -oP fix from 204423e (#1528). The scraped URL was also malformed: a greedy match across the release-notes markup dropped a path separator, producing .../amd64236836/... which 403s. Switch to the appcast Docker Desktop's own updater consumes, which provides the version, build number and artifact URL as data rather than markup. Select on highest BuildNumber, since entries are ordered oldest-first and carry a staged-rollout Visibility percentage, so neither document order nor Visibility==100 identifies the newest build. VERSION_PUBLISHED is now AppVersion-BuildNumber, matching the .deb's own Version field. The previous bare version compared as older than an installed build under dpkg --compare-versions, so rebuilds of the same version were silently missed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B6S1VtnD2yAkAXYsrfR1Kp
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #1507
replaces #1492
closes #1509
A lot of slightly-different implementations have arisen because of many valuable contributions re-using prior art at the same time as many other valuable contributions have
improved style, functionality, performance.
This is an attempt to standardise the majority of "similar" definitions. Besides conforming white-space styling to the model set out in the EXTREPO.md the main changes have been
echo "${URL}"| ... | tr -d vwith<<< "${URL/v/}"sedinvocations with similar variable substitutions$( )invocations .The CI test is failing to install all the changed packages. This has identified a couple of issues but some that fall over in CI install OK locally. Looks like either a long wade through breaking changes to get to a squashable PR, a hard look at the CI to try and fix some issues there and improve behaviour or parking and splitting this PR into a lot of individual changes for each definition (excluding the deprecations and ones where pending PRs (most of which have been aligned with this work) might apply.