[Pkg-javascript-devel] node-buble_0.20.0+~0.19.2-1~bpo10+2_amd64.changes ACCEPTED into buster-backports

[Jonas Smedegaard]

Quoting Pirate Praveen (2021-01-14 14:43:12)
> 
> 
> On Thu, Jan 14, 2021 at 2:03 pm, Jonas Smedegaard <jonas at jones.dk> 
> wrote:
> > Quoting Debian FTP Masters (2021-01-14 13:04:22)
> >>  Description:
> >>   node-buble - Fast ES2015 compiler for Node.js
> >>  Changes:
> >>   node-buble (0.20.0+~0.19.2-1~bpo10+2) buster-backports; 
> >> urgency=medium
> >>   .
> >>     * Use node-debbundle-acorn instead of node-acorn as aptitude 
> >> fails to choose
> >>       the virtual package because there is a real node-acorn package
> > 
> > As I understand it, when a real and a virtual package exists, the real
> > package wins.  Virtual package should be possible to prioritize 
> > through
> > versioning.  That's one reason it is important to include version when
> > providing virtual packages.
> > 
> 
> No, that is not sufficient, it works in sid by accident because there 
> is no real package to compete.
> 
> node-bunble says node-acorn (>= 6~) in Build-Depends
> 
> and node-debbundle-acorn in buster-backports provides
>  node-acorn (= 8.0.4+ds+~cs19.19.27-1)
> > 
> 
> and node-acorn real package version in buster is 5.5.3+ds3-3
> 
> and this is the exact command I used (which works for every other 
> backport).
> 
> sbuild -A -s --force-orig-source -c buster-amd64-sbuild 
> --extra-repository='deb http://deb.debian.org/debian buster-backports 
> main' --extra-repository='deb http://incoming.debian.org/debian-buildd 
> buildd-buster-backports main' --build-dep-resolver=aptitude 
> --no-run-lintian
> 
> I also tried aspcud resolver instead of aptitude with same result 
> (failed to resolve).

When I say that virtual package should be possible to prioritize through 
versioning, I don't mean nudging build environment to use different 
hinting to their various resolvers, but explicit contraints in declared 
package relations.

If the real package is resolved as a solution then it means the package 
permit that other version (and because real is treated as better than 
virtual, it wins).

Try tighten (build-)dependencies to only possibly match the virtual 
package.

That should lead to the virtual package getting installed.

If it leads to no package being resolved or the unacceptably versioned 
real package getting resolved, then file a severe bug against the 
resoilver or build environment.


 - 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/20210114/0dff2b51/attachment.sig>