Bug#1069753: libuv1: y2k38 known upstream issue on 32-bits archs

2024-04-24 Thread Dominique Dumont
On Wednesday, 24 April 2024 09:48:55 CEST you wrote:
> on 32-bits archs, nodejs fails some y2k38 tests.
> 
> It is a well-known issue that has been fixed in libuv master branch,
> https://github.com/libuv/libuv/issues/3864
> but might not be fixed anytime soon in 1.x branch.
> 
> Indeed, fixing it breaks API.
> 
> However, in Debian, I think we can just do that, as long as we patch
> reverse dependencies on libuv1.

I disagree. Some people may be using libuv1 in a program not handled by 
Debian.

Breaking the API means changing the SONAME of the lib. According to Debian 
policy, this means creating a libuv2 package.

> What do you think about that ?

We should wait for an upstream libuv v2.

All the best.



Bug#1069753: libuv1: y2k38 known upstream issue on 32-bits archs

2024-04-24 Thread Jérémy Lal
Potentially impacted packages...

Reverse Build-depends in testing/main:
--

ardour
bind9
chiark-utils
cmake
cowsql
csound-plugins
dnsjit
dnswire
dqlite
driftnet
getdns
golang-github-evanw-esbuild
h2o
haxe
hddemux
ipywidgets
janus
jupyterlab
kamailio
knot-resolver
libstorj
libwebsockets
lomiri-calculator-app
lua-luv
macaulay2
moarvm
mosquitto
node-emotion
node-fbjs
node-grunt-sass
node-gulp-sass
node-iconv
node-ipydatagrid
node-jasmine
node-jupyterlab
node-libpq
node-modern-syslog
node-nan
node-node-pty
node-node-sass
node-nouislider
node-opencv
node-pre-gyp
node-re2
node-react
node-react-toastify
node-rollup-plugin-sass
node-shiny-server
node-sqlite3
node-stdlib
node-vega-embed
node-vega-tooltip
node-ws
node-zx
nodejs
npm
nqp
ocaml-luv
passenger
pcp
pipewire
polybar
python-gevent
r-cran-fs
r-cran-httpuv
r-cran-v8
raft
rakudo
roc-toolkit
rtpengine
seafile
select2.js
siridb-server
swupdate
tensorpipe
uvloop

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

Le mer. 24 avr. 2024 à 09:51, Jérémy Lal  a écrit :

> Package: libuv1
> Version: 1.48.0-1
> Severity: important
>
> Hi Dominique,
>
> on 32-bits archs, nodejs fails some y2k38 tests.
>
> It is a well-known issue that has been fixed in libuv master branch,
> https://github.com/libuv/libuv/issues/3864
> but might not be fixed anytime soon in 1.x branch.
>
> Indeed, fixing it breaks API.
>
> However, in Debian, I think we can just do that, as long as we patch
> reverse dependencies on libuv1.
>
> What do you think about that ?
>
>
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
> Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages libuv1 depends on:
> ii  libc6  2.37-15
>
> libuv1 recommends no packages.
>
> libuv1 suggests no packages.
>
> -- no debconf information
>
>


Bug#1069753: libuv1: y2k38 known upstream issue on 32-bits archs

2024-04-24 Thread Jérémy Lal
Package: libuv1
Version: 1.48.0-1
Severity: important

Hi Dominique,

on 32-bits archs, nodejs fails some y2k38 tests.

It is a well-known issue that has been fixed in libuv master branch,
https://github.com/libuv/libuv/issues/3864
but might not be fixed anytime soon in 1.x branch.

Indeed, fixing it breaks API.

However, in Debian, I think we can just do that, as long as we patch
reverse dependencies on libuv1.

What do you think about that ? 


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libuv1 depends on:
ii  libc6  2.37-15

libuv1 recommends no packages.

libuv1 suggests no packages.

-- no debconf information