[Pkg-javascript-devel] Bug#979551: Bug#979551: Bug#979551: node-babel7: update-alternatives set up fails

Jonas Smedegaard jonas at jones.dk
Fri Jan 8 12:24:12 GMT 2021


Quoting Pirate Praveen (2021-01-08 12:48:06)
> 
> 
> On Fri, Jan 8, 2021 at 12:44 pm, Jonas Smedegaard <jonas at jones.dk> 
> wrote:
> > I don't understand - how is node-babel7 affected by how yarnpkg 
> > declares (build-)dependencies against it?
> > 
> 
> node-babel7 will still be affected by the update-alternatives bug when 
> manpages missing.
> 
> > What I suggest is to improve the package yarnpkg to replace any 
> > runtime and build-time package relations on node-babel7 to instead 
> > be on each actually needed node-$module package, virtual or not.
> > 
> > (and yes, it should work fine for autopkgtest as well - a previous 
> > failure I caused was due to lack of appending (>= 7) for a virtual 
> > package also provided by older babel6 package).
> 
> That is tangential to this particular bug. That is an improvement, 
> yes, but will not solve this bug without separate binary for 
> @babel/runtime module, as it will still pull in node-babel7 and 
> missing man pages will trigger this bug.

Ahh.  Yes, I agree that no changes to package yarnpkg can fix bugs in 
package node-babel7.

And I agree that the issue on topic for this bugreport is a bug in 
node-babel7.

That said, both you and I responsed to a _sidenote_ by Paolo:

Quoting Jonas Smedegaard (2021-01-08 12:06:21)
> Quoting Pirate Praveen (2021-01-08 11:55:14)
> > On 2021, ജനുവരി 8 1:16:36 PM IST, Paolo Greppi 
> > <paolo.greppi at libpf.com> wrote:
> > >BTW, why is node-babel7 a run-time dependency of yarnpkg ? Should 
> > >it not just be a build-dep ?
> > >
> > 
> > It needs @babel/runtime which is currently part of node-babel7. I 
> > think yadd already uploaded a version of node-babel7 with separate 
> > node-babel7-runtime binary package. But it has not cleared NEW yet.
> 
> You need not wait for NEW clearance to depend explicitly on required 
> packages - you need only have the required packages available as 
> virtual packages.

My point above is that regardless of the topic of this bugreport, that 
other issue on topic for the sidenote need not wait for NEW processing, 
but can be addressed (or at least prepared) in parallel by changing to 
declare explicit package relations in package yarnpkg.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20210108/4a65e9b7/attachment.sig>


More information about the Pkg-javascript-devel mailing list