[Pkg-javascript-devel] trying to fix salsa-ci job for nodejs 14: uscan warn: unknown ctype nodejs

[Santiago Ruano Rincón]

(FYI: we a mailing list now:  debian-salsa-ci at alioth-lists.debian.net)

El 11/03/22 a las 10:05, Yadd escribió:
> On 11/03/2022 09:44, Iñaki Malerba wrote:
> > Hello Nilesh ,
> > 
> > On Fri, Mar 11, 2022 at 12:43:56PM +0530, Nilesh Patra wrote:
> > > Hi Iñaki/Santiago,
> > > 
> > > On 3/11/22 10:34 AM, Yadd wrote:
> > > > On 11/03/2022 01:28, Jérémy Lal wrote:
> > > > > Hi,
> > > > > 
> > > > > i tried to get salsa-ci pass the first step of ci job for nodejs,
> > > > > by adapting a little debian/watch:
> > > > > https://salsa.debian.org/js-team/nodejs/-/jobs/2549349 <https://salsa.debian.org/js-team/nodejs/-/jobs/2549349>
> > > > > 
> > > > > However this warning happens:
> > > > > uscan warn: unknown ctype nodejs
> > > > > 
> > > > > After that, the component tarballs are not generated.
> > > > > Is it possible that salsa-ci is running an "old" uscan that don't know about "ctype nodejs" ?
> > > > 
> > > > Sadly yes...
> > > 
> > > Is it possible to get this fixed in the CI image?
> > 
> > I just checked the image that was used on that job, and the uscan
> > version seems to be the latest one available.
> > 
> > # apt-cache policy devscripts
> > devscripts:
> >    Installed: 2.22.1
> > 
> > # uscan --version
> > This is uscan, from the Debian devscripts package, version 2.22.1
> > 
> > Could it be that there's a dependency missing for js? I'm sorry
> > but I have no experience building js packages.
> 
> Hi,
> 
> this is not related to JS packages, ctype is an uscan option introduced in
> version 2.20.5. Looking at https://udd.debian.org/dmd/?email1=pkg-javascript-devel%40lists.alioth.debian.org&format=html,
> it seems that only a few requests report this error (28 report / more than
> 450 packages which have this option in their debian/watch file). Maybe some
> machines aren't updated ?

I don't think so. At least, not in the Salsa CI context. All the jobs
run on the same image.

Are you sure you have pushed all the pristine-tar commits?:

    ~/d/p/t/n/nodejs (master-14.x)> origtargz
    pristine-tar: successfully generated ../nodejs_14.19.0~dfsg.orig-types-node.tar.xz
    pristine-tar: successfully generated ../nodejs_14.19.0~dfsg.orig-node-acorn.tar.xz
    fatal: ambiguous argument 'ad5417c34ff48ec0d85cbed196b36ed1f858f1eb^{tree}': unknown revision or path not in the working tree.
    Use '--' to separate paths from revisions, like this:
    'git <command> [<revision>...] -- [<file>...]'
    fatal: not a valid object name: ad5417c34ff48ec0d85cbed196b36ed1f858f1eb^{tree}
    tar: This does not look like a tar archive
    tar: Exiting with failure status due to previous errors
    pristine-tar: command failed: git archive --format=tar ad5417c34ff48ec0d85cbed196b36ed1f858f1eb\^\{tree\} | (cd '/tmp/pristine-tar.NUYv1HwthO' && tar x)

Cheers,

 -- Santiago
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20220311/538af72b/attachment.sig>