Normally you'd expect to fix bugs with a new version, in this case while trying 
to update node-define-property 1.0.0-1 -> 2.0.2 the failing tests actually 
increased from 1 to 4.

What puzzled me was that no tests fail on upstream's CI (travis), which also 
tests nodejs version 8.

Turns out that we have upgraded node-is-descriptor to version 2.0.0, but the 
npm registry only has 1.0.2.

I have forwarded the issue upstream, and I expect upstream to answer that 
define-property correctly pins the major version of is-descriptor with ^1.0.2 
(, stating that it won't work with 2.x.

^1.0.2 should be translated with >= 1.0.2 && < 2.0.0 but we can't encode that 
in debian/control.

So how can we check reverse dependencies for this type of issues in the future ?


Pkg-javascript-devel mailing list

Reply via email to