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


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

Bug#1016305: nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1

Started byDominique Dumont <domi.dumont@free.fr>
First post2022-07-30 19:30 +0200
Last post2022-07-31 19:20 +0200
Articles 4 — 2 participants

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#1016305: nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1 Dominique Dumont <domi.dumont@free.fr> - 2022-07-30 19:30 +0200
    Bug#1016305: nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1 Jérémy Lal <kapouer@melix.org> - 2022-07-30 19:40 +0200
      Bug#1016305: nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1 Dominique Dumont <domi.dumont@free.fr> - 2022-07-31 16:40 +0200
        Bug#1016305: nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1 Dominique Dumont <domi.dumont@free.fr> - 2022-07-31 19:20 +0200

#1111486 — Bug#1016305: nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1

FromDominique Dumont <domi.dumont@free.fr>
Date2022-07-30 19:30 +0200
SubjectBug#1016305: nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1
Message-ID<EOYrL-eRWC-1@gated-at.bofh.it>
On Saturday, 30 July 2022 17:25:29 CEST you wrote:
> libuv1 maintainer: please avoid uploading new versions when nodejs is
> in transition...

I package libuv1 because it's a dependency of moarvm.

I don't follow nodejs releases, so I was not aware of on-going transition and 
I did not expect problems because only the minor version number was increased. 

On the other hand, I have no problem with delaying uploads of libuv1 provided 
someone warns me of issues in other packages.

All the best

[toc] | [next] | [standalone]


#1111489

FromJérémy Lal <kapouer@melix.org>
Date2022-07-30 19:40 +0200
Message-ID<EOYBr-eRZI-7@gated-at.bofh.it>
In reply to#1111486

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

Le sam. 30 juil. 2022 à 19:24, Dominique Dumont <domi.dumont@free.fr> a
écrit :

> On Saturday, 30 July 2022 17:25:29 CEST you wrote:
> > libuv1 maintainer: please avoid uploading new versions when nodejs is
> > in transition...
>
> I package libuv1 because it's a dependency of moarvm.
>
> I don't follow nodejs releases, so I was not aware of on-going transition
> and
> I did not expect problems because only the minor version number was
> increased.
>
> On the other hand, I have no problem with delaying uploads of libuv1
> provided
> someone warns me of issues in other packages.



libuv1 is a library, you're supposed to manage the transition:
https://wiki.debian.org/Teams/ReleaseTeam/Transitions

In particular, rebuild all reverse build dependencies and check they won't
break is highly desirable.
There are tools and services in debian to do that (though honestly it's not
so easy to setup).

Reverse Build-depends in main:
------------------------------

ardour
bind9
cmake
csound-plugins
dnsjit
dnswire
dqlite
driftnet
forked-daapd
getdns
golang-github-evanw-esbuild
h2o
haxe
hddemux
janus
kamailio
knot-resolver
libstorj
libwebsockets
lua-luv
lua-nvim
macaulay2
moarvm
mosquitto
neovim
netdata
node-expat
node-fbjs
node-grunt-sass
node-iconv
node-jasmine
node-leveldown
node-modern-syslog
node-nan
node-node-sass
node-nouislider
node-opencv
node-pause
node-pre-gyp
node-re2
node-react
node-rollup-plugin-sass
node-shiny-server
node-sqlite3
node-websocket
node-ws
node-zx
nodejs
npm
nqp
ocaml-luv
passenger
pcp
polybar
python-gevent
r-cran-fs
r-cran-httpuv
r-cran-v8
radare2
radare2-cutter
raft
rakudo
rtpengine
select2.js
siridb-server
swupdate
tensorpipe
ttyd
uvloop

Found a total of 69 reverse build-depend(s) for libuv1-dev.


Jérémy

[toc] | [prev] | [next] | [standalone]


#1111566

FromDominique Dumont <domi.dumont@free.fr>
Date2022-07-31 16:40 +0200
Message-ID<EPigN-f3Jf-11@gated-at.bofh.it>
In reply to#1111489
On Saturday, 30 July 2022 19:36:26 CEST you wrote:
> libuv1 is a library, you're supposed to manage the transition:
> https://wiki.debian.org/Teams/ReleaseTeam/Transitions

This page applies when the new version breaks the ABI or API. This was not the 
case. There was no symbol change. The SO version of libuv1 has not changed 
since the transition between libuv and libuv1.

> In particular, rebuild all reverse build dependencies and check they won't 
break is highly desirable.
> There are tools and services in debian to do that (though honestly it's not 
so easy to setup).

I'm already stretched quite thin. I'll see what I can do.

In any case, I'd be happy to handover libuv1 to people willing to better 
maintain this package.

All the best.

[toc] | [prev] | [next] | [standalone]


#1111594

FromDominique Dumont <domi.dumont@free.fr>
Date2022-07-31 19:20 +0200
Message-ID<EPkLD-f5lk-3@gated-at.bofh.it>
In reply to#1111566
On Sunday, 31 July 2022 16:35:12 CEST Jérémy Lal wrote:
> Indeed, sorry for my somewhat irritated tone - it just happens that it was
> the second time libuv1 was updated during a nodejs transition, and the
> upstream bug it creates on nodejs hasn't been fixed yet, so it shoots the
> transition in the guts.
> Nodejs depends heavily on libuv1...

I understand your furstration. Sorry about the mess.

> Maybe a simple approach would be to upload libuv1 updates to experimental
> first, and wait a week to see how it scares the others :)

That I can do.

All the best.

[toc] | [prev] | [standalone]


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


csiph-web