Your message dated Fri, 18 Dec 2020 22:59:06 +0100
with message-id <4e827dba-2d2c-ba6a-df36-ff294183c...@debian.org>
and subject line Re: [Pkg-javascript-devel] Bug#977685: node-jest: build
routines are too brittle: build failures go undetected
has caused the Debian Bug report #977685,
regarding node-jest: build routines are too brittle: build failures go
undetected
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
977685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-jest
Version: 26.6.3+repack+~cs61.38.31-3
Severity: serious
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
By accident I noticed that a release of node-jest with only changes to
package relations changed size from 8.5 megabytes to 500 kilobytes.
A closer examination of build logs seems to indicate failures to compile
TypeScript code into JavaScript.
Build logs are here:
https://buildd.debian.org/status/logs.php?pkg=node-jest&arch=all
wget
'https://buildd.debian.org/status/fetch.php?pkg=node-jest&arch=all&ver=26.6.3%2Brepack%2B%7Ecs61.38.31-2&stamp=1607423417&raw=0'
wget
'https://buildd.debian.org/status/fetch.php?pkg=node-jest&arch=all&ver=26.6.3%2Brepack%2B%7Ecs61.38.31-3&stamp=1608313404&raw=0'
git diff --no-index fetch.php*
Detail from log comparison which seems important:
- -dh_auto_install: warning: ### Missing char-regex/src, skipping
- -
- -dh_auto_install: warning: ### Missing char-regex/tsconfig.json, skipping
- -
- -dh_auto_install: warning: ### Missing char-regex/tsconfig.tsbuildinfo,
skipping
+ mkdir -p
/<<BUILDDIR>>/node-jest-26.6.3\+repack\+\~cs61.38.31/debian/tmp//usr/share/nodejs/\@bcoe/v8-coverage/src/test
+ cp --reflink=auto -a bcoe-v8-coverage/src/test/merge.spec.ts
/<<BUILDDIR>>/node-jest-26.6.3\+repack\+\~cs61.38.31/debian/tmp//usr/share/nodejs/\@bcoe/v8-coverage/src/test/
+ mkdir -p
/<<BUILDDIR>>/node-jest-26.6.3\+repack\+\~cs61.38.31/debian/tmp//usr/share/nodejs/\@bcoe/v8-coverage/src/lib
+ cp --reflink=auto -a bcoe-v8-coverage/src/lib/types.ts
/<<BUILDDIR>>/node-jest-26.6.3\+repack\+\~cs61.38.31/debian/tmp//usr/share/nodejs/\@bcoe/v8-coverage/src/lib/
+ cp --reflink=auto -a bcoe-v8-coverage/src/lib/range-tree.ts
/<<BUILDDIR>>/node-jest-26.6.3\+repack\+\~cs61.38.31/debian/tmp//usr/share/nodejs/\@bcoe/v8-coverage/src/lib/
+ cp --reflink=auto -a bcoe-v8-coverage/src/lib/normalize.ts
/<<BUILDDIR>>/node-jest-26.6.3\+repack\+\~cs61.38.31/debian/tmp//usr/share/nodejs/\@bcoe/v8-coverage/src/lib/
+ cp --reflink=auto -a bcoe-v8-coverage/src/lib/merge.ts
/<<BUILDDIR>>/node-jest-26.6.3\+repack\+\~cs61.38.31/debian/tmp//usr/share/nodejs/\@bcoe/v8-coverage/src/lib/
+ cp --reflink=auto -a bcoe-v8-coverage/src/lib/index.ts
/<<BUILDDIR>>/node-jest-26.6.3\+repack\+\~cs61.38.31/debian/tmp//usr/share/nodejs/\@bcoe/v8-coverage/src/lib/
+ cp --reflink=auto -a bcoe-v8-coverage/src/lib/compare.ts
/<<BUILDDIR>>/node-jest-26.6.3\+repack\+\~cs61.38.31/debian/tmp//usr/share/nodejs/\@bcoe/v8-coverage/src/lib/
+ cp --reflink=auto -a bcoe-v8-coverage/src/lib/clone.ts
/<<BUILDDIR>>/node-jest-26.6.3\+repack\+\~cs61.38.31/debian/tmp//usr/share/nodejs/\@bcoe/v8-coverage/src/lib/
+ cp --reflink=auto -a bcoe-v8-coverage/src/lib/ascii.ts
/<<BUILDDIR>>/node-jest-26.6.3\+repack\+\~cs61.38.31/debian/tmp//usr/share/nodejs/\@bcoe/v8-coverage/src/lib/
+dh_auto_install: warning: ### Missing char-regex/build/config.gypi, skipping
Setting severity=serious because packages should build reliably.
- Jonas
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/dHt0ACgkQLHwxRsGg
ASGPoA//QX21jbnWbz4sOzvXyt/Y4gL6IOhqCCRLbmZdUu7xbQwKAxa3fWajMh25
ZeT9XZltTrNxWY5Qr/3yuKrMigxIPvQoT8LVed2zE4tb77jR9b3l89lD3eHI64+J
UiVAoLG8PjRgCIaCi7Y92Y7K0sCMPEBatWevquPmuKSsfTa8UUgkrXJBNxFdmrFW
XsJymGiJ3ZAc1SJahHyqu4tIB2jD2JWkQ6RzG9WNhqXm+jsqWA1Zs1WuI5orP9lB
YJhM8qXkh0BKxf7TNWti0c+vKH4pzCWx/Md9gYbSGFbS1dKIzRKCziGvQ8RPrrGV
JKLM4/Y5ghs6quOBHRWxbZ42MrS341baC5kSThadxG09/dMePRy8iYYEA2Y2XX9H
jeie6spSPdo3+3d3+S9wF+QTBRF0/34gqFC0MsHqYCPIQDFSUMINNx6PxKkTUczx
J4HxuZ2LziQrB2mTP2frQbleKKDNQwRXw6T+OyMS6BAgSrw3jzxujIRcIOP0a70I
t8rjX4bfMt154q+nzuYQqMDSEwj2/1MrCf8HN1mOnLTJekfOQqY/P1eX9SX+D57X
daHDi2JoTTYPZ3q2JED4RsxKQZ1t6nSyWXtTqUmxeA2WJZMarxRNOdi1VzMyGvg9
0sqBxHwo2N3y3I+ubJNIOU+C3Huiq9Ywd/nRmi2TaprVxM/dcjs=
=UCxe
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Le 18/12/2020 à 22:28, Jonas Smedegaard a écrit :
> Source: node-jest
> Version: 26.6.3+repack+~cs61.38.31-3
> Severity: serious
>
> By accident I noticed that a release of node-jest with only changes to
> package relations changed size from 8.5 megabytes to 500 kilobytes.
>
> A closer examination of build logs seems to indicate failures to compile
> TypeScript code into JavaScript.
>
> Build logs are here:
> https://buildd.debian.org/status/logs.php?pkg=node-jest&arch=all
>
> wget
> 'https://buildd.debian.org/status/fetch.php?pkg=node-jest&arch=all&ver=26.6.3%2Brepack%2B%7Ecs61.38.31-2&stamp=1607423417&raw=0'
> wget
> 'https://buildd.debian.org/status/fetch.php?pkg=node-jest&arch=all&ver=26.6.3%2Brepack%2B%7Ecs61.38.31-3&stamp=1608313404&raw=0'
> git diff --no-index fetch.php*
>
> Detail from log comparison which seems important:
>
> -dh_auto_install: warning: ### Missing char-regex/src, skipping
> -
> -dh_auto_install: warning: ### Missing char-regex/tsconfig.json, skipping
> -
> -dh_auto_install: warning: ### Missing char-regex/tsconfig.tsbuildinfo,
> skipping
These message are false-positive bad warning when using default
.npmignore. I'll remove them in pkg-js-tools.
The difference comes from new pkg-js-tools feature: it reads now
.npmignore, then /usr/share/nodejs/jest-each/assets/ is now removed. I
didn't see that this directory contains 4 very big .gif!
So closing this bug, this is not a bug but an improvement of pkg-js-tools!
Thanks to have looked at this.
Cheers,
Xavier
--- End Message ---
