[Pkg-javascript-devel] Bug#1007267: Bug#1007267: node-eslint-scope: FTBFS while updating with webpack5: Error: Invalid webpack options

[Jonas Smedegaard]

[ Re-added bugreport as email recipient ]

Quoting Ayoyimika Ajibade (2022-03-15 11:26:28)
> >Uhm, I am confused here.  Are you aware that upstream version 7.1.1 
> >is in Debian unstable since February 28th?
> 
> You are right,  I verified that with (apt policy node-eslint-scope)
> but until yesterday or today the gitlab repo was in version 5.1.1,

Beware that Debian is not (the "Salsa" instance of) Gitlab!

Salsa is a helper tool, but if Debian and Salsa is not in sync then 
Debian is what counts.

Fine that you use Salsa if that is more convenient for you, but then try 
limit confusion by comparing with officially released package when you 
file bugreports - because Debian bugreports tracks the officially 
released packages, not Salsa.

My point here is *not* that you should repeat Salsa tests with official 
packages - just that it is confusing if you assume that NPM and Salsa 
and Debian are in sync.

A good place to get an overview of official Debian releases for a 
package is tracker.debian.org - e.g. 
https://tracker.debian.org/pkg/node-eslint-scope


> I asked questions didn't get a response,

Where did you ask those questions?

On our IRC channel?  At our mailinglist?  In a bugreport?

If you used one of those channels, then I am sorry that I missed it, and 
I would appreciate if you could tell me more details - e.g. time and 
place - so I can try investigate why I failed to see it.

Please beware that if you used Salsa for conversations, then it might 
work fine if those you want to reach also use that, but Salsa is an 
*optional* set of tools and the JavaScript team (same as most teams in 
Debian) only generally use IRC and mailinglists and official Debian 
bugreports.


> so I decided to update it as it was failing most reverse dependencies 
> of webpack5(hence the confusion, smiles), and no the new update made 
> didn't solve the problem
> 
> here is an example of the prevalent error message from CI log
> https://salsa.debian.org/Ayoyimika/node-axios/-/jobs/2563777
> webpack5 depends on node-eslint-scope so both webpack and
> node-eslint-scope needs to be patched to fix the error
> 
> here is webpack patch:
> https://salsa.debian.org/Ayoyimika/node-webpack/-/commit/1b33b3505358ba411be0a1188cbcf5fe24b879fb.patch
> here is eslint-scope patch:
> https://salsa.debian.org/Ayoyimika/node-eslint-scope/-/commit/feaf8a8ffb7a1b4794d04323b5e265ce058494a0.patch

Ah right, looking at that last patch above, that is clearly unrelated to 
the fix released earlier today.

Do you understand what that change does, more specifically?

Is it backwards compatible?  What is the risk of breaking something?

I am hesitant to change this, and would prefer to either understand it 
better, or (much better) that you report this issue upstream to the 
developers of eslint-scope and we have their opinion on the matter.


Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20220315/3777237b/attachment.sig>