Re: [PATCH 0/6] kbuild: fix some packaging issues, and use git-archive for source package

Leon Romanovsky
2023-03-16T12:50:54Z

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