[Pkg-javascript-devel] Bug#980316: Update on packaging corepack

Pirate Praveen praveen at onenetbeyond.org
Mon Mar 20 15:44:30 GMT 2023


On Thu, 16 Mar 2023 10:23:53 +0100 Israel Galadima 
<izzygaladima at gmail.com> wrote:
 > Hi,
 >
 > Michael and I have done some packaging work for corepack.
 > Of note, we have updated clipanion and packaged some dependencies of
 > proxy-agent.
 >
 > Although, some of our work is awaiting uploads because of the freeze.
 >
 > Regards.

We tried to update yarnpkg as part of an outreachy project (in two 
rounds), but we could not complete it in time for bookworm. As shared 
by Israel, we made some good progress and we hope to be able to do it 
in trixie. I request bookworm-ignore tags for these bugs (as such there 
is no immediate breakage, just unmaintained upstreams for these 
packages). Hopefully we can handle any security updates ourselves.

Additionally, even though yarnpkg itself is old, the presence of the 
package makes it easy to obtain a newer yarnpkg. In gitlab, I already 
use the packaged yarnpkg command to install a newer yarnpkg[1]. It is 
also very common in nodejs world to use specific version of yarnpkg for 
each project, these are typically installed in .yarn directory for each 
project.

yarnpkg: 980316,958686, 1002902, 980316
node-har-validator: 1024575
node-request: 956423
node-request-capture-har: 1002901

[1] 
https://salsa.debian.org/ruby-team/gitlab/-/blob/master/debian/rake-tasks.sh#L44
runuser -u ${gitlab_user} -- sh -c 'yarnpkg set version berry'



More information about the Pkg-javascript-devel mailing list