[Pkg-javascript-devel] Bug#1003039: Bug#1003039: Bug#1003039: node-terser: Please update node-commander dependency to version 8

[Yadd]

On 06/02/2022 14:51, Jonas Smedegaard wrote:
> Quoting Yadd (2022-02-06 14:24:02)
>> On 06/02/2022 13:36, Jonas Smedegaard wrote:
>>> Quoting Yadd (2022-02-06 13:18:10)
>>>> On 06/02/2022 12:35, Jonas Smedegaard wrote:
>>>>> Quoting Yadd (2022-01-03 08:08:31)
>>>>>> node-commander 8 changed option parsing. Here is a proposed patch
>>>>>> to be used in replacement of 1001_use_commander_4.patch
>>>>>
>>>>> Thanks for the patch!
>>>>>
>>>>> If I understand correctly, the patch is not backwards-compatible
>>>>> with node-commander currently in Debian unstable/testing.  I will
>>>>> therefore do nothing until node-commander enters unstable.
>>>
>>>> Thanks to look at this. Yes, we have to coordinate this because I
>>>> have to add a 'Breaks: node-terser (<< XXX)'
>>>
>>> Only coordination needed is, I think, is to bump severity of this
>>> bugreport when new node-commander enters unstable.
>>>
>>>
>>>> I think the same patch should be applied to uglifyjs
>>>
>>> node-uglifyjs stopped using node-commander since release 3.10.1-1,
>>> so it seems to me that no new Breaks is needed compared to the one
>>> in node-commander 6.2.1-2, and that even that can be dropped when
>>> buster stops being supported.
>>>
>>>    - Jonas
>>
>> OK, for now node-commander breaks yarnpkg < 1.22.10+~cs22.25.14-6~ and
>> cleancss < 5.2.2+~5.5.0~. I'm ready to push these 3 packages. Do I
>> have to add "terser (<< 4.1.2-9~)" ?
> 
> I think this is better: "Breaks: uglifyjs.terser (<= 4.1.2-9+)"

This forbid 4.1.2-9 which doesn't exist yet, isn't it ?