Control: forwarded -1
https://github.com/lodash-archive/lodash-cli/pull/141
On Sun, Jul 26, 2020 at 16:12, Nicolas Mora
wrote:
I'm not sure yet if this would fix the bug but in all the build log
errors, I see that the file /usr/share/nodejs/lodash/_baseOrderBy.js
is
always the source of
Le 26/07/2020 à 18:54, Pirate Praveen a écrit :
>
>
> On Sun, Jul 26, 2020 at 19:35, Adrian Bunk wrote:
>> On Sun, Jul 26, 2020 at 09:55:47PM +0530, Pirate Praveen wrote:
>>> I'm wondering if this will require another bootstraping cycle as
>>> node-babel7
>>> autopkgtest is also broken and it
Le 20-07-26 à 18 h 01, Pirate Praveen a écrit :
>
>>
>> File in node-lodash unstable package:
>> 4.17.19+dfsg-1 _baseOrderBy.js https://paste.debian.net/1157886/
>>
I made a dirty hack to check my theory and it looks like if I patch this
file by replacing 'isArray' with 'Array.IsArray' or if I
Quoting Pirate Praveen (2020-07-26 21:07:19)
> Control: reopen -1
>
> On Mon, Jul 27, 2020 at 00:32, Pirate Praveen
> wrote:
> > This did not fix the issue :( So we have to reopen this bug once the
> > upload reaches the archive (which will close this bug as fixed).
>
> Thanks to the brave
On 2020, ജൂലൈ 27 1:42:32 AM IST, Nicolas Mora wrote:
>I'm not sure yet if this would fix the bug but in all the build log
>errors, I see that the file /usr/share/nodejs/lodash/_baseOrderBy.js is
>always the source of the error.
>
>The file _baseOrderBy.js in the package seems buggy for an
I'm not sure yet if this would fix the bug but in all the build log
errors, I see that the file /usr/share/nodejs/lodash/_baseOrderBy.js is
always the source of the error.
The file _baseOrderBy.js in the package seems buggy for an unresolved reson.
File in node-lodash unstable package:
Control: reopen -1
On Mon, Jul 27, 2020 at 00:32, Pirate Praveen
wrote:
This did not fix the issue :( So we have to reopen this bug once the
upload reaches the archive (which will close this bug as fixed).
Thanks to the brave new world of embedding eveything and reducing the
number of js
On Sun, Jul 26, 2020 at 22:43, Pirate Praveen
wrote:
On Sun, Jul 26, 2020 at 22:24, Pirate Praveen
wrote:
Babel build situation is indeed a mess.
It is even worse than I estimated. We can no longer build it with npm
DEB_BUILD_PROFILES=pkg.node-babel7.npm sbuild
...
HOME=`pwd` npm i
On Sun, Jul 26, 2020 at 22:24, Pirate Praveen
wrote:
Babel build situation is indeed a mess.
It is even worse than I estimated. We can no longer build it with npm
DEB_BUILD_PROFILES=pkg.node-babel7.npm sbuild
...
HOME=`pwd` npm i
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported
On Sun, Jul 26, 2020 at 19:35, Adrian Bunk wrote:
On Sun, Jul 26, 2020 at 09:55:47PM +0530, Pirate Praveen wrote:
I'm wondering if this will require another bootstraping cycle as
node-babel7
autopkgtest is also broken and it depends on itself.
If the problem is in node-lodash and gets
On Sun, Jul 26, 2020 at 09:55:47PM +0530, Pirate Praveen wrote:
> I'm wondering if this will require another bootstraping cycle as node-babel7
> autopkgtest is also broken and it depends on itself.
If the problem is in node-lodash and gets fixed there,
shouldn't this fix everything?
cu
Adrian
I'm wondering if this will require another bootstraping cycle as
node-babel7 autopkgtest is also broken and it depends on itself.
Source: node-babel7
Version: 7.10.5+~cs65.71.38-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=node-babel7=all=7.10.5%2B~cs65.71.38-2=1595148206=0
...
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -f node_modules/@babel/code-frame
cd
13 matches
Mail list logo
