[master] deb: move packaging revision before distro information#818
Conversation
|
For good measure, as I keep zooming in myself each time to spot |
|
/cc @tianon @crazy-max |
|
Somewhat related, I recall I had created an issue on buildx-packaging repo about this: docker/packaging#85
|
|
Ah! |
4ecda83 to
b14cc05
Compare
| # docker-ce_23.0.0~beta.0-0~ubuntu.22.04~jammy_amd64.deb | ||
| cat > "debian/changelog" <<-EOF | ||
| $debSource (${EPOCH}${EPOCH_SEP}${DEB_VERSION}-0~${DISTRO}.${VERSION_ID}.${pkgRevision}~${SUITE}) $SUITE; urgency=low | ||
| $debSource (${EPOCH}${EPOCH_SEP}${DEB_VERSION}-${pkgRevision}~${DISTRO}.${VERSION_ID}~${SUITE}) $SUITE; urgency=low |
There was a problem hiding this comment.
Discussing with Tianon; we can use 1 as default, which would align with the _release in the RPM packages (which are 1-based)
|
replacing the 0 with 1 is also 100% sane and reasonable here ie, |
b14cc05 to
6d88305
Compare
Commit f8299f2 introduced the `$pkgRevision` in the package version, but we now actually had two separate escape hatches for when we needed to do a packaging-only update; one before the packaging version, and one after the distro-ID (VERSION_ID). The latter one was confusing, as it appeared to be part of the distro-version (e.g. `22.04.0`). This patch removes the additional version, and moves it to the start, and updates the default to use "1", which aligns with the "_release" used for RPM packages, and may help with warnings that the package version is not an "upstream" (debian) version. Comparing same version old vs new (works because we now use 1 as default): dpkg --compare-versions "23.0.0~rc.1-1~ubuntu.22.04~jammy" ">>" "23.0.0~rc.1-0~ubuntu.22.04.0~jammy" && echo "OK" || echo "KO" OK Comparing newer version (new format) vs older version (old format) is ok: dpkg --compare-versions "23.0.0~rc.2-1~ubuntu.22.04~jammy" ">>" "23.0.0~rc.1-0~ubuntu.22.04.0~jammy" && echo "OK" || echo "KO" OK Comparing same version, but newer $pkgRevision (either new format <-> old-format, or new-format <-> new-format) is also ok: dpkg --compare-versions "23.0.0~rc.1-2~ubuntu.22.04~jammy" ">>" "23.0.0~rc.1-1~ubuntu.22.04~jammy" && echo "OK" || echo "KO" OK dpkg --compare-versions "23.0.0~rc.1-2~ubuntu.22.04~jammy" ">>" "23.0.0~rc.1-1~ubuntu.22.04.0~jammy" && echo "OK" || echo "KO" OK Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
6d88305 to
39772a7
Compare
|
@tianon updated 👍 |
|
Let me bring this one in; I'll push the same changes for plugins later |
|
Ah! Looks like I need to make some changes in our release-verify step in the release pipeline; |
Commit f8299f2 introduced the
$pkgRevisionin the package version, but we now actually had two separate escape hatches
for when we needed to do a packaging-only update; one before the packaging
version, and one after the distro-ID (VERSION_ID). The latter one was confusing,
as it appeared to be part of the distro-version (e.g.
22.04.0).This patch removes the additional version, and moves it to the start, and updates
the default to use "1", which aligns with the "_release" used for RPM packages,
and may help with warnings that the package version is not an "upstream" (debian)
version.
Comparing same version old vs new (works because we now use 1 as default):
Comparing newer version (new format) vs older version (old format) is ok:
Comparing same version, but newer $pkgRevision (either new format <-> old-format,
or new-format <-> new-format) is also ok: