Bug#932884: release.debian.org: What is the good way to update rollup ?
Hi Xavier,
On 24-07-2019 09:07, Xavier Guimard wrote:
> For the next release, we (pkg-js team) would like to update rollup. Like
^^^^^^^^^^^^
You're talking about bullseye here, or the first point release of
buster. I assume you mean the former.
> many compilers, it build-depends on itself. Current version in Buster is
> 0.50.0, The last published upstream is 1.17.0.
> We would also like to provide a Buster-backports package
>
> Here are the upgrade constraints:
>
> * 0.50.0 can build any version until 0.53.3
> * 0.51.7 can build any version until 0.56.3
> * 0.56.1 can build any version until 0.65.2
> * 0.58.1 can build any version until 0.67.2
> * 0.59.1 can build any version until 1.12.0
> * 1.12.0 can build any version until 1.17.0
>
> This needs 6 steps (at least 4 to be able to update some important JS
> component with rollup 0.67.2).
>
> There are no major break changes in rollup. At worst some function name
> changed, easy to patch.
>
> ====== MAIN QUESTION ======
>
> Is it recommended or required to provide a Buster-buildable rollup
> package for next release ?
I don't believe this requirement exist, nor is it a recommendation. If
there is security risks in this package (I haven't heard them before) it
would be a slight advantage I guess.
> ==== IF NO ====
>
> Then we will simply update rollup step by step but there could be
> problems with Buster-Backports?
Why? I may be missing something, but why are you not just going step by
step. First step one in unstable, wait for migration to testing, upload
to backports and do step two. It takes some time, but it doesn't need
coordination with anybody.
Paul
Reply to: