[Pkg-javascript-devel] Proposing to upload webpack 5 to unstable

[Pirate Praveen]

2022, മേയ് 20 3:32:06 PM IST, Jonas Smedegaard <jonas at jones.dk>ൽ എഴുതി
>Quoting Pirate Praveen (2022-05-20 11:03:15)
>> 
>> 
>> On വെ, മേയ് 20 2022 at 07:18:41 രാവിലെ 
>> +02:00:00 +02:00:00, Jonas Smedegaard <jonas at jones.dk> wrote:
>> > Please provide more detail:
>> > 
>> > Which packages fail to work with webpack 4, and how?
>> > 
>> 
>> webpack 4 itself is broken, I don't think the effort to fix webpack 4 
>> is really worth it as we won't be able to support in bullseye anyway 
>> and webpack 5 was in experimental long enough.
>> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011097
>> 
>> > Which packages listed as failing with webpack 5 is easy peasy to 
>> > simply
>> > upgrade (without collateral damage to reverse dependencies)?
>> > 
>> 
>> Bugs were filed long time ago for all failing packages and most of them 
>> are fixed. 
>> https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-javascript-devel%40alioth-lists.debian.net&tag=webpack5 
>>  has full list. For bigger transitions, we can't really wait for every 
>> package to be fixed, we can only realistically give a good heads up for 
>> people to fix things. You can see how we did not even get any notice 
>> for openssl, we only got a bug after it was broken. But for webpack5 
>> all affected packages have bugs for a long time.
>> 
>> > The last major upgrade of chalk has lef eslint broken, so I am *not*
>> > happy if you push webpack upgrade forward without properly weighing
>> > the collaterals!
>> > 
>> I agree with this sentiment in general for breaking without sufficient 
>> notice. But I don't think webpack 5 transition was any surprice, at 
>> least 3 full months of outreachy work happened on the transition and 
>> two people worked full time on it. So I don't think asking for more 
>> time is reasonable.
>
>For the record, it is not time I ask for, only clarity.  I don't try to
>stall unnecessarily.
>
>My point is that "current package is broken too" is not in itself an
>argument to move to major new upstream release.
>
>Thanks for the link to the bug in webpack4, I agree with moving to
>webpack5.

Thanks, I will upload webpack 5 to unstable now.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.