On 2020-07-11 11:00, Jonas Smedegaard wrote:
> Reason I suspect upstream-only tracking is wrong is that also Debian 
> changes can change ABI - either deliberately or accidentally.  Most 
> notibly by adding/changing patches, but possibly also through changes to 
> build-dependencies.

Agree.

> I thought with node-expat I had mimiced the dpkg-shlibdeps resolved hint 
> for libnodeXX but I see now that I did that wrong: Currently that 
> dependency is upstream-only, but that is because the current 
> relationship is for a -1 release where the Debian part is stripped.
>
> I now issued a new node-expat with an improved logic.  Thanks!

I saw your changes in node-expat 2.3.18+ds-3. This is definitely an 
improvement, but having no upper bound on nodejs version will not prevent 
#963060 from happening again once in a while.

Best wishes,
Andrius


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to