[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#[bugid]: [package]: node-uglify is deprecated in favor of uglifyjs

Le 12/01/2021 à 15:38, Thomas Goirand a écrit :
> On 1/12/21 11:41 AM, yadd@debian.org wrote:
>> Package: [package]
>> Severity: important
>> [package] build depends on node-uglify which is deprecated and
>> will be removed from bullseye (#958117), please update your (build)
>> dependency in favor of uglifyjs or uglifyjs.terser
>> https://bugs.debian.org/<bugid>
> Hi,
> Don't you think it's a little bit too late in the development cycle of
> Bullseye to do this? Also, if you're doing a mass-bug-filling, why
> hasn't this discuss in debian-devel? Did I miss it? Has this been
> discussed with the release team? Why acting now when the bug was open
> last April?


sorry for the delay. In 99% of cases, you just have to
 * replace "node-uglify" by "uglifyjs" in debian/control
 * remove --source-map argument (automatically calculated now)

> I'm also surprised of the severity of #958117. The fact that a package
> has lost upstream doesn't have to be of severity "grave", and IMO
> shouldn't justify filling RC bugs on 84 packages (that's how many
> reverse-depends -b node-uglify reveals) a few weeks from the freeze.
> I'm afraid it's going to be ... ugly ! :)
> Your thoughts?

You're probably right, I tried to prevent that a Bullseye problem is
coming (I hadn't seen it before).

Best regards,

Reply to: