From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-kernel v2] buildsys: add explicit DEB_VERSION variable in Makefile
Date: Thu, 23 Jan 2025 09:11:43 +0100 [thread overview]
Message-ID: <8f05af82-8536-481d-8232-d0ff8fb26d7a@proxmox.com> (raw)
In-Reply-To: <20250122172249.630549-1-s.ivanov@proxmox.com>
Am 22.01.25 um 18:22 schrieb Stoiko Ivanov:
> Can be used to generate a package for testing a particular bugfix, or
> new version, which can be shared with a small audience, without
> reusing the current package version, or bumping to a version that
> looks like our released kernels[0].
>
> previously this could be accomplished by setting the PKGREL variable
> to the revision and temporary suffix. PKGREL got dropped in:
> de1853080134 ("bump version to 6.2.16-8")
> as each new version we release needs to have a ABI bump anyways (due
> to module signing).
>
> [0] e.g. new versions of submodules (ZFS), or packages shared in the
> temp-dir of our CDN nodes
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> v1->v2:
> * drop mistakenly added KREL increment - thx @Thomas for noticing.
> replaces:
> https://lore.proxmox.com/pve-devel/20250120192712.1642091-1-s.ivanov@proxmox.com/
>
> Makefile | 17 +++++++++--------
> README | 5 +++++
> 2 files changed, 14 insertions(+), 8 deletions(-)
>
>
applied to both the master branch and the bookworm-6.8 branch, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-01-23 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 17:22 [pve-devel] [PATCH pve-kernel v2] buildsys: add explicit DEB_VERSION variable in Makefile Stoiko Ivanov
2025-01-23 8:11 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f05af82-8536-481d-8232-d0ff8fb26d7a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox