On Thu, 19 Nov 2020 23:50:24 +0530 Pirate Praveen
<prav...@onenetbeyond.org> wrote:
>
>
> On Thu, Nov 19, 2020 at 18:58, Xavier <y...@debian.org> wrote:
> > we opened bugs to upstream repo and are waiting for...
>
> I don't think upstream will make any significant changes to 1.x
branch
> any more. Someone who want to see yarn in debian bullseye will have
to
> fix it.
As per https://dev.to/arcanis/introducing-yarn-2-4eh1 yarn 1.x is
officially in maintenance mode.
Quoting from above:
"What will happen to the legacy codebase?
Yarn 1.22 will be released next week. Once done, the 1.x branch will
officially enter maintenance mode - meaning that it won't receive
further releases from me except when absolutely required to patch
vulnerabilities. New features will be developed exclusively against
Yarn 2."
And there is no way to separately install yarn 2, you have to install
yarn 1.x to get newer versions of yarn.
Quoting again,
"The yarn package on npm will not change; we will distribute further
version using the new yarn set version command."
So some options I can think,
1. Port yarn 1.x to build with babel 7 (but this has not been
successfull)
2. Try to run ES6 code directly somehow, may be with newer nodejs and
patches. I think Paolo tried this option, not sure what happened.
3. Build it using 'deb
https://snapshot.debian.org/archive/debian/20200502T085134Z sid main'
(the last version that builds in sid) and embed the built files in the
package (as two steps, like we bootstrap babel, rollup etc). This will
mean, we will have to move it to contrib. I prefer shipping yarn in
contrib to missing it in bullseye.
Also can someone help me with a patch for node-mkdirp 1.0? I tried but
could not figure it out, I looked at some of the packages ported by
yadd, but this one is using a different syntax.
We can't build it in current sid, but create a chroot from the above
snapshot and run dpkg-buildpackage.
sudo debootstrap sid /srv/chroot/debian-sid-20200502T085134Z
https://snapshot.debian.org/archive/debian/20200502T085134Z/
I manually installed node-mkdirp and reverse dependencies to test the
built package.
We will have to do a binary included upload (it can't migrate to
testing because of babel 6 requirement anyway).
