[Pkg-javascript-devel] Bug#977963: node-commander ≥ 6

[Xavier]

Le 23/12/2020 à 13:28, Jonas Smedegaard a écrit :
> Quoting Jonas Smedegaard (2020-12-23 13:06:40)
>> Quoting Xavier (2020-12-23 12:28:53)
>>> Le 23/12/2020 à 12:19, Jonas Smedegaard a écrit :
>>>> Quoting Xavier (2020-12-23 11:34:41)
>>>>> node-commander 6 is ready in experimental. It seems that all is 
>>>>> OK, except a little change in uglifyjs.terser help output 
>>>>> detected by your Perl test.
>>>>> I posted a simple MR, could you see if this is acceptable 
>>>>> (compatible with node-commander 5)?
>>>>
>>>> Please attach proposed patch to an email.  Preferably as a 
>>>> bugreport.
>>
>>> With commander 6, uglifyjs.terser displays:
>>>
>>>   Usage: uglifyjs [options]...
>>>
>>> instead of:
>>>
>>>   Usage: uglifyjs.terser [options]...
>>>
>>> I don't know if my patch is useful here: it replaced your test regex 
>>> with a more tolerant one without fixing the real issue (if this is an 
>>> issue?).
>>
>> Ah, thanks - that is a helpful detail.
>>
>> No, I don't think that is an issue needed any further work than 
>> wriggling the terser test a bit.
>>
>> Please go ahead (assuming no issues elsewhere) with the node-commander 
>> upgrade - i.e. don't wait for terser, I will handle that from there.
> 
> Oh!  This still is just a mailinglist conversation, not a bugreport :-(
> 
> @Xavier, would you mind filing this as a proper bugreport, please?
> 
> Or tell me if that is too uch hassle for you, then I will do it, but 
> prefor to give you credit for your work.
> 
> In case you wonder: No, this is not just bureaucratic busywork: I am in 
> the middle of other work with the terser package (and a pile of other 
> work with other packages, including the mess I made with symlink-to-dir 
> removals), and tracking issues with the bugtracker truly helps.

Hi,

can I upload node-commander to unstable or do you prefer to push
node-terser first ?

Regards,
Xavier