Re: `Build-Depends` parsing problem for node-* packages

Hi Jonas, Le 17/03/2021 à 18:35, Jonas Smedegaard a écrit : > 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`

Re: `Build-Depends` parsing problem for node-* packages

Hi David, Le 17/03/2021 à 19:22, David Kalnischkies a écrit : > 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 `ap

Re: `Build-Depends` parsing problem for node-* packages

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

Re: `Build-Depends` parsing problem for node-* packages

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

`Build-Depends` parsing problem for node-* packages

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