Hi Johannes,
thanks for your answer!
> with sbuild you can use --extra-package=package.deb or
> --extra-package=/path/to/debs and then sbuild will use those debs or all debs
> in the directory you specify, respectively, to satisfy dependencies and you
> don't need to manage an apt repository your
Hi,
On Wed, Mar 17, 2021 at 04:52:38PM +0100, Arnaud Ferraris wrote:
> I've been confronted with an issue affecting a number of node-* packages
> (and maybe others): apt is unable to parse the Build-Depends field,
> making `apt build-dep` effectively unusable with those packages.
>
> One good exa
Hi Arnaud,
Quoting Arnaud Ferraris (2021-03-17 16:52:38)
> I've been confronted with an issue affecting a number of node-*
> packages (and maybe others): apt is unable to parse the Build-Depends
> field, making `apt build-dep` effectively unusable with those
> packages.
You seem to be reportin
Hi,
I've been confronted with an issue affecting a number of node-* packages
(and maybe others): apt is unable to parse the Build-Depends field,
making `apt build-dep` effectively unusable with those packages.
One good example is node-ramda[1]: as the first non-space character apt
encounters when
Hi Norbert,
Quoting Norbert Preining (2021-03-17 03:55:53)
> in the Qt/KDE Team we use a script for test-building our groups of packages.
> Those groups need to be build in tiers (levels) so that later packages have
> access to the build of earlier levels. The script we currently use is based
> o
5 matches
Mail list logo