On ഞാ, Jan 19, 2020 at 11:33, Jérémy Lal <kapo...@melix.org>
wrote:
Le dim. 19 janv. 2020 à 07:54, Pirate Praveen
<prav...@onenetbeyond.org> a écrit :
On 2020, ജനുവരി 19 2:32:01 AM IST, "Jérémy Lal"
<kapo...@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?).
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.
Jérémy
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
