[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNATrzAWiu36=-JXXjSt48O12OAQG4ZAtLABd_PyiE2f_VQ@mail.gmail.com>
Date: Sun, 19 Mar 2023 11:19:17 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Steev Klimaszewski <steev@...i.org>
Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
nathan@...nel.org, ndesaulniers@...gle.com, nicolas@...sle.eu,
terrelln@...com
Subject: Re: [PATCH 0/6] kbuild: fix some packaging issues, and use
git-archive for source package
On Sun, Mar 19, 2023 at 10:12 AM Steev Klimaszewski <steev@...i.org> wrote:
>
> Hi Masahiro,
>
> On Sun, Mar 12, 2023 at 1:07 PM Masahiro Yamada <masahiroy@...nel.org> wrote:
> >
> > This series fixes some bugs, then switch to 'git archive'
> > for source package creation as suggested by Linus.
>
> I apologize if this is a stupid question, but it's not immediately apparent to
> me...
>
> Previously, I was overriding the deb file output name by the setting of
> LOCALVERSION_AUTO; but with this series applied, that seems to be ignored?
>
> Now if I pass LOCALVERSION="" I end up with e.g. linux-image-6.3.0-rc2_6.3.0-rc2-00575-g46c71cad996d-100_arm64.deb
> whereas previously, I would end up with linux-image-6.3.0-rc2_6.3.0-rc2-100_arm64.deb
>
> How would I restore the old naming behaviour?
>
> -- steev
The same string "6.3.0-rc2" is repeated in the file name.
The first one is what Debian calls the ABI version, and the
second one is the version of the package.
They are usually different on real Debian kernels.
LOCALVERSION affects the former, and KDEB_PKGVERSION
the second.
My recommendation is "just let it be"
because "linux-upstream_6.3.0-rc2.orig.tar.gz"
you would generate is not the real 6.3.0-rc2.
If you want to restore what you previously did,
make deb-pkg KDEB_PKGVERSION=6.3.0-rc2-100
will create such a file name.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists