From: Leon Romanovsky <leon@kernel.org>
To: Nicolas Schier <nicolas@fjasle.eu>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nick Terrell <terrelln@fb.com>
Subject: Re: [PATCH 0/6] kbuild: fix some packaging issues, and use git-archive for source package
Date: Thu, 16 Mar 2023 14:50:39 +0200 [thread overview]
Message-ID: <20230316125039.GW36557@unreal> (raw)
In-Reply-To: <ZBL8d1odNuLPs4zy@bergen.fjasle.eu>
On Thu, Mar 16, 2023 at 12:24:39PM +0100, Nicolas Schier wrote:
> On Thu 16 Mar 2023 12:22:15 GMT, Leon Romanovsky wrote:
> > On Mon, Mar 13, 2023 at 05:07:25AM +0900, Masahiro Yamada wrote:
> > > This series fixes some bugs, then switch to 'git archive'
> > > for source package creation as suggested by Linus.
> > >
> > >
> > >
> > > Masahiro Yamada (6):
> > > kbuild: deb-pkg: make debian source package working again
> > > kbuild: deb-pkg: do not take KERNELRELEASE from the source version
> > > kbuild: deb-pkg: set CROSS_COMPILE only when undefined
> > > kbuild: deb-pkg: split image and debug objects staging out into
> > > functions
> > > kbuild: deb-pkg: use dh_listpackages to know enabled packages
> > > kbuild: use git-archive for source package creation
> >
> >
> > I tried this series and got the following error:
> > 11:05:53 Install lsb-release or set $KDEB_CHANGELOG_DIST explicitly
> > 11:05:53 dpkg-buildpackage: info: source package linux-upstream
> > 11:05:53 dpkg-buildpackage: info: source version 6.3.0-rc2-gdc71b1b23e6d-1
> > 11:05:53 dpkg-buildpackage: info: source distribution unstable
> > 11:05:53 dpkg-buildpackage: info: source changed by root <root@5621c2cf448d>
> > 11:05:53 dpkg-buildpackage: info: host architecture arm64
> > 11:05:53 dpkg-source --before-build .
> > 11:05:53 dpkg-source: info: using options from linux/debian/source/local-options: --diff-ignore --extend-diff-ignore=.*
> > 11:05:53 dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper
> > 11:05:53 dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
> > 11:05:53 dpkg-buildpackage: warning: (Use -d flag to override.)
> > 11:05:53 make[1]: *** [scripts/Makefile.package:117: deb-pkg] Error 3
> > 11:05:53 make: *** [Makefile:1656: deb-pkg] Error 2
> >
> > Thanks
>
> Do you have debhelper available on your system? As debhelper is a
> build dependency, such a fail is expected if debhelper is not
> available.
Yes, we don't have debhelper in our build container. The thing is that
we are using same container as we used before this series and never needed
debhelper.
Thanks
>
> Kind regards,
> Nicolas
next prev parent reply other threads:[~2023-03-16 12:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 20:07 [PATCH 0/6] kbuild: fix some packaging issues, and use git-archive for source package Masahiro Yamada
2023-03-12 20:07 ` [PATCH 1/6] kbuild: deb-pkg: make debian source package working again Masahiro Yamada
2023-03-12 20:07 ` [PATCH 2/6] kbuild: deb-pkg: do not take KERNELRELEASE from the source version Masahiro Yamada
2023-03-13 11:31 ` Péter Ujfalusi
2023-03-12 20:07 ` [PATCH 3/6] kbuild: deb-pkg: set CROSS_COMPILE only when undefined Masahiro Yamada
2023-03-12 20:07 ` [PATCH 4/6] kbuild: deb-pkg: split image and debug objects staging out into functions Masahiro Yamada
2023-03-12 20:07 ` [PATCH 5/6] kbuild: deb-pkg: use dh_listpackages to know enabled packages Masahiro Yamada
2023-03-12 20:07 ` [PATCH 6/6] kbuild: use git-archive for source package creation Masahiro Yamada
2023-04-06 15:25 ` youling257
2023-04-07 12:04 ` Masahiro Yamada
2023-03-12 23:26 ` [PATCH 0/6] kbuild: fix some packaging issues, and use git-archive for source package Linus Torvalds
2023-03-13 0:52 ` Masahiro Yamada
2023-03-13 17:33 ` Linus Torvalds
2023-03-16 10:22 ` Leon Romanovsky
2023-03-16 11:24 ` Nicolas Schier
2023-03-16 12:50 ` Leon Romanovsky [this message]
2023-03-19 1:12 ` Steev Klimaszewski
2023-03-19 2:19 ` Masahiro Yamada
2023-03-19 3:21 ` Steev Klimaszewski
2023-03-19 6:45 ` Steev Klimaszewski
2023-03-19 7:06 ` Masahiro Yamada
2023-03-19 7:57 ` Steev Klimaszewski
2023-03-19 7:02 ` Leon Romanovsky
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=20230316125039.GW36557@unreal \
--to=leon@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=terrelln@fb.com \
--cc=torvalds@linux-foundation.org \
/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