Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1017537 > unrolled thread

Bug#963761: [Pkg-javascript-devel] Bug#963761: Bug#963761: Bug#963761: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment

Started byJonas Smedegaard <jonas@jones.dk>
First post2020-07-11 10:10 +0200
Last post2020-07-11 10:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#963761: [Pkg-javascript-devel] Bug#963761: Bug#963761: Bug#963761: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment Jonas Smedegaard <jonas@jones.dk> - 2020-07-11 10:10 +0200

#1017537 — Bug#963761: [Pkg-javascript-devel] Bug#963761: Bug#963761: Bug#963761: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment

FromJonas Smedegaard <jonas@jones.dk>
Date2020-07-11 10:10 +0200
SubjectBug#963761: [Pkg-javascript-devel] Bug#963761: Bug#963761: Bug#963761: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment
Message-ID<AriK5-421-9@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Quoting Andrius Merkys (2020-07-10 11:52:40)
> On 2020-07-10 12:38, Jonas Smedegaard wrote:
> > I suspect you are wrong about relaxing lower bounds to only upstream 
> > part.
> 
> I got this idea from the way the issue was fixed in node-expat [1].
> Could you explain why you think this is a bad idea?
> 
> [1]
> https://salsa.debian.org/js-team/node-expat/-/commit/fbea3d7cae693f4bd6b7a5a0d7adfbb25792a6a1

Whoops, looks like I am contradicting myself :-)

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.

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!


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

[toc] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web