Public bug reported:
Compare:
https://packages.ubuntu.com/eoan/libglfw3
with
https://packages.ubuntu.com/focal/libglfw3
--> the i386 version is missing.
** Affects: glfw3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
Public bug reported:
This is after doing a fresh Ubuntu 20.04 installation, on my machine
equipped with 3 monitors using an SLI of nvidia GTX 980. My 3 monitors
are 1 4k monitor in landscape mode, and 2 1080p monitors in portrait
mode. This used to work properly in Ubuntu 19.10, but is utterly bro
Yes - this is expected behavior for not passing down proper SSL
certificates to the constructor.
On Sat, Sep 8, 2018 at 12:27 PM, Elana Hashman
wrote:
> I have tested the steps with nodejs and nodejs-dev in bionic-proposed,
> however I get a different error. I am guessing that there is something
The official list of library dependency versions can be found here:
https://nodejs.org/dist/index.json
8.11.4 is listed as linked against OpenSSL 1.0.2p.
On Fri, Aug 31, 2018 at 12:37 PM, Dan Streetman wrote:
> re: cosmic debdiff, debian appears to have added code to 8.11 version
> that breaks
Apologies for the late reply.
My github repository is a quick effort in trying to expose the ABI problem,
but a more thorough (and straightforward) way to actually reproduce would
be to do the following:
First case, when using a module that ships with prebuilt binaries. With the
"nodejs" and "npm
ectly reasonable for people to also expect that doing npm
install just works too, and right now that's not the case.
On Tue, Aug 7, 2018 at 10:51 AM, Robie Basak <1779...@bugs.launchpad.net>
wrote:
> On Tue, Aug 07, 2018 at 03:59:27AM -, Nicolas Noble wrote:
> > So one anot
. And I personally don't really care what the actual solution is, as
long as my users stop reporting that doing npm install of my package fails
for them on Ubuntu. Please do engage with the actual nodejs developers in
order to resolve this.
On Tue, Aug 7, 2018 at 11:20 AM, Nicolas Noble
I must specify something from your statements. The fact the native
module doesn't load really is undesired behavior. The normal nodejs
behavior is make sure that the module is going to load while installing
it, by checking ABI compatibility using various tags. It is expected and
supported that node
While it's theorically possible to bypass node-gyp, I'm not aware of any
actively used method that would do so. The node-gyp is a bundled dependency
of npm, and is the code that parses the native module information (the
bindings.gyp file that is), in order to generate the Makefile that will
build t
I'm sorry, but I must heavily disagree with the assessment here, and I
am asking you to reconsider your "won't fix". No breakage is possible
since there can't be existing native modules built manually by people
due to this other bug, which is the corollary of this present one:
https://github.com/no
The template changes look good to me.
On Wed, Jul 25, 2018 at 9:21 AM, Ubuntu Foundations Team Bug Bot <
1779...@bugs.launchpad.net> wrote:
> ** Tags added: patch
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1779863
I can confirm that your nodejs from your ppa makes prebuilt binaries work
fine again, yes.
On Tue, Jul 24, 2018 at 2:35 PM, Dan Streetman
wrote:
> @ehashman, @grumpycoder, let me know if you're able to test with the deb
> from my ppa, so we can at least confirm it does fix this issue.
>
> --
>
There's also a "documentation" in nodejs' release database:
https://nodejs.org/dist/index.json
On Mon, Jul 23, 2018, 15:56 Elana Hashman <1779...@bugs.launchpad.net>
wrote:
> Oops, GitHub expanded that link to the full commit when I copied it.
> Here's demonstrating it's the same one as the 8.10.
Also if you want to reproduce it, you simply need to npm install grpc on
Ubuntu using Ubuntu's nodejs. Loading and using gRPC (I can build a
quick nodejs demo project if you want) will then fail with the symbol
mismatch I described initially.
Or you can also use the reproduction case I linked init
I've created an issue on nodejs' tracker to discuss this also:
https://github.com/nodejs/node/issues/21897
Let me rephrase what you just said a bit, because I think you're getting
it a bit incorrectly.
People are distributing binaries through npm, and these binaries are
expected to work directly
Public bug reported:
Background:
NodeJS has a native extension API: https://nodejs.org/api/addons.html
It's fairly understood by developers that NodeJS's ABI is stable, and that one
module built using a version of nodejs should work on another semantically
version compatible of nodejs.
NodeJS e
One (working ?) alternative we've successfully used here to workaround
this weird game of whack-a-mole is to stop relying on gcc-multilib, and
start using :i386 versions of packages. So for instance, we would
install for example the following list of packages on an amd64 machine:
build-essential g
17 matches
Mail list logo
