[Pkg-javascript-devel] nodejs-12 transition

Jérémy Lal kapouer at melix.org
Sun Jan 19 17:44:28 GMT 2020


Le dim. 19 janv. 2020 à 16:38, Pirate Praveen <praveen at onenetbeyond.org> a
écrit :

>
>
> On ഞാ, Jan 19, 2020 at 11:33, Jérémy Lal <kapouer at melix.org>
> wrote:
> >
> >
> > Le dim. 19 janv. 2020 à 07:54, Pirate Praveen
> > <praveen at onenetbeyond.org> a écrit :
> >>
> >>
> >>  On 2020, ജനുവരി 19 2:32:01 AM IST, "Jérémy Lal"
> >> <kapouer at melix.org> wrote:
> >>
> >>  >The problem is the "build-dep-resolver" here.
> >>
> >>  Did you reproduce the error with aptitude and not with aspcud?
> >> aptitude was working even in cases where aspcud failed so most of us
> >> switched to aptitude.
> >
> > Yes, exactly. You need the resolver to pull build-deps from
> > expertimental, not from sid.
> >
>
> May be I'm missing something here (did you really get two different
> results when changing aptitude with aspcud?).
>

YES

aptitude does pull package from experimental if build dependency cannot
> be satisfied from unstable, and that is how we are expected to build in
> experimental. I use aptitude build-resolver always for building
> packages in experimental that needs build dependencies from
> experimental and never faced an issue till now.
>

Well, I don't know about that. I just used another resolver and it didn't
fail.
Maybe it builds using node 12 and test using node 10 ?

Jérémy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20200119/d0faed9a/attachment.html>


More information about the Pkg-javascript-devel mailing list