Bug#1017581: Please install documentation

[Jérémy Lal]

Le lun. 25 sept. 2023 à 19:21, Dominique Dumont  a écrit :

> Hi
>
> Sorry for the late reply.
>
> On Thu, 18 Aug 2022 00:01:36 +0100 Ian Jackson <
> ijack...@chiark.greenend.org.uk> wrote:
> > It would be ncie to install this documentation somewhere suitable.  As
> > manpages would be ideal, assuming the .rst files are suitable for
> > that, but HTML in /usr/share/doc/ would do nicely as well.
>
> libuv documentation can indeed be built as HTML files.
>
> However, lintian then complains about vendored js files and about privacy
> breach:
>
> W: libuv1-dev: embedded-javascript-library please use libjs-jquery
> [usr/share/doc/libuv1-dev/html/_static/jquery.js]
> N:
> N:   This package contains an embedded copy of JavaScript libraries that
> are
> N:   now available in their own packages (for example, JQuery, Prototype,
> N:   Mochikit or "Cropper"). Please depend on the appropriate package and
> N:   symlink the library into the appropriate location.
> N:
> N:   Please refer to Embedded code copies (Section 4.13) in the Debian
> Policy
> N:   Manual for details.
> N:
> N:   Visibility: warning
> N:   Show-Always: no
> N:   Check: languages/javascript/embedded
> N:
> N:
> W: libuv1-dev: embedded-javascript-library please use libjs-underscore
> [usr/share/doc/libuv1-dev/html/_static/underscore.js]
> N:
> W: libuv1-dev: embedded-javascript-library please use sphinx
> [usr/share/doc/libuv1-dev/html/_static/doctools.js]
> N:
> W: libuv1-dev: embedded-javascript-library please use sphinx
> [usr/share/doc/libuv1-dev/html/_static/language_data.js]
> N:
> W: libuv1-dev: embedded-javascript-library please use sphinx
> [usr/share/doc/libuv1-dev/html/_static/searchtools.js]
> N:
> W: libuv1-dev: privacy-breach-generic [ height="315"\nsrc="https://www.youtube-nocookie.com/embed/ngn60vdsxq4;
> frameborder="0"\nallowfullscreen>] (
> https://www.youtube-nocookie.com/embed/ngn60vdsxq4)
> [usr/share/doc/libuv1-dev/html/guide/basics.html]
> N:
> N:   This package creates a potential privacy breach by fetching data from
> an
> N:   external website at runtime. Please remove these scripts or external
> HTML
> N:   resources.
> N:
> N:   Please replace any scripts, images, or other remote resources with
> N:   non-remote resources. It is preferable to replace them with text and
> links
> N:   but local copies of the remote resources are also acceptable as long
> as
> N:   they don't also make calls to remote services. Please ensure that the
> N:   remote resources are suitable for Debian main before making local
> copies
> N:   of them.
> N:
> N:   Visibility: warning
> N:   Show-Always: no
> N:   Check: files/privacy-breach
> N:
>
> Since these docs are available online, I won't invest more time in fixing
> these issues and will continue to ship libuv1-dev without HTML doc.
>

Hi,

actually dh-sphinxdoc takes care of all this !

I made a merge request here, that adds a libuv1-doc package and patch a
small issue with privacy breach:
https://salsa.debian.org/debian/libuv1/-/merge_requests/2

Regards,
Jérémy

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

[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

[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

Bug#1069227: man-db: Please do not change MANWIDTH behavior just in Debian

[Jérémy Lal]

Control: retitle -1 setting MANWIDTH 80 gives different result in sid

Le jeu. 18 avr. 2024 à 12:29, Colin Watson  a écrit :

> On Thu, Apr 18, 2024 at 10:19:51AM +0200, Jérémy Lal wrote:
> > It seems that man-db debian maintainer decided on its own to make
> > some arbitrary change to how MANWIDTH is handled.
> >
> > This is probably going to break things, for no good reason besides a
> personal preference.
>
> Huh?
>
> 1) The man-db Debian maintainer is the same person as the upstream
>maintainer, i.e. me.
>

Ok, and sorry, I got frustrated by the "1 column space on the right" change
of
https://gitlab.com/man-db/man-db/-/merge_requests/11

2) The Debian packaging does not contain any changes to how MANWIDTH is
>handled.
>

Indeed, the upstream version changes how width is configured.
- man: match the display width to the configured width (closes:#1059537).

It's just making another package (node-marked-man) render man pages
differently,
and fail its tests, preventing some other package migration (nodejs) and it
would have
been nice not having that change during this t64 transition.

Bug#1069227: man-db: Please do not change MANWIDTH behavior just in Debian

[Jérémy Lal]

Package: man-db
Version: 2.12.1-1
Severity: normal

Hi,

It seems that man-db debian maintainer decided on its own to make
some arbitrary change to how MANWIDTH is handled.

This is probably going to break things, for no good reason besides a personal 
preference.

Please revert that.

Jérémy





-- 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 man-db depends on:
ii  bsdextrautils  2.39.3-6
ii  bsdmainutils   12.1.8
ii  debconf [debconf-2.0]  1.5.86
ii  groff-base 1.23.0-3
ii  libc6  2.37-15
ii  libgdbm6   1.23-5+b1
ii  libpipeline1   1.5.7-2
ii  libseccomp22.5.5-1
ii  zlib1g 1:1.3.dfsg-3+b1

man-db recommends no packages.

Versions of packages man-db suggests:
ii  apparmor3.0.13-2
ii  chromium [www-browser]  123.0.6312.105-1~deb13u1
ii  dillo [www-browser] 3.0.5-7+b1
ii  epiphany-browser [www-browser]  46~beta-1
ii  firefox-esr [www-browser]   115.8.0esr-1
ii  groff   1.23.0-3
ii  less590-2
ii  lynx [www-browser]  2.9.0rel.0-2
ii  w3m [www-browser]   0.5.3+git20230121-2+b2

-- debconf information:
  man-db/install-setuid: false
  man-db/auto-update: true

Bug#1068725: [Pkg-nginx-maintainers] Bug#1068725: libnginx-mod-http-js contains unnecessary dependency

[Jérémy Lal]

Le mar. 9 avr. 2024 à 21:30, Miao Wang  a écrit :

> Package: libnginx-mod-http-js
> Version: 0.8.2-1+b1
> Severity: normal
>
> Dear Maintainer,
>
> libnginx-mod-http-js contains a dependency on libnginx-mod-stream, which
> should be only necessary for libnginx-mod-stream-js.


Reassigned to nginx, because currently dh-nginx does this unconditionally:
$this->{has_stream} = $this->has_build_dep("libnginx-mod-stream");
../..
if ($this->{has_stream} == 1) {
  addsubstvar($cur, "misc:Depends", "libnginx-mod-stream (>= $ngx_ver),
libnginx-mod-stream (<< $ngx_ver.1~)");
}
../..

It should offer a better way.
Maybe shlibdeps picks that dependency ? so dh-nginx could add the
constraint on mod-stream versions only when the built binary is actually
linked to it ?

Bug#1068016: bookworm-pu: package node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u2

[Jérémy Lal]

Package: release.debian.org
Followup-For: Bug #1068016

node-babel7 needs node-undici 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4
(see release.d.o. #1068912).

Also, even with that, the current debdiff *will FTBFS*, see #1068933.

Please find attached another debdiff that addresses that issue.

Jérémy
(sorry for the very late reaction)
diff -Nru node-babel7-7.20.15+ds1+~cs214.269.168/debian/changelog 
node-babel7-7.20.15+ds1+~cs214.269.168/debian/changelog
--- node-babel7-7.20.15+ds1+~cs214.269.168/debian/changelog 2023-10-13 
16:02:05.0 +0200
+++ node-babel7-7.20.15+ds1+~cs214.269.168/debian/changelog 2024-03-29 
17:29:05.0 +0100
@@ -1,3 +1,18 @@
+node-babel7 (7.20.15+ds1+~cs214.269.168-3+deb12u2) bookworm; urgency=medium
+
+  * Team upload
+  * Improve tsc-workaround patch, fixing compilation against
+nodejs 18.19.0+dfsg-6~deb12u1. Closes: #1068933.
+
+  [ Andreas Beckmann ]
+  * Backport Breaks+Replaces fixes from 7.20.15+ds1+~cs214.269.168-4.
+
+  [ Yadd ]
+  * Add missing Breaks+Replaces against all node-babel-* that were in Debian 10
+(Closes: #1037234)
+
+ -- Andreas Beckmann   Fri, 29 Mar 2024 17:29:05 +0100
+
 node-babel7 (7.20.15+ds1+~cs214.269.168-3+deb12u1) bookworm-security; 
urgency=medium
 
   * Team upload
diff -Nru node-babel7-7.20.15+ds1+~cs214.269.168/debian/control 
node-babel7-7.20.15+ds1+~cs214.269.168/debian/control
--- node-babel7-7.20.15+ds1+~cs214.269.168/debian/control   2023-10-13 
16:02:05.0 +0200
+++ node-babel7-7.20.15+ds1+~cs214.269.168/debian/control   2024-03-29 
17:29:05.0 +0100
@@ -120,8 +120,92 @@
 Suggests: node-babel-plugin-polyfill-es-shims
  , node-babel7-debug
 Breaks: node-babel-core (<< 6.26.0+repack-3~)
+ , node-babel-cli (<< 7)
  , node-babel-code-frame (<< 7)
-Replaces: node-babel-code-frame (<< 7)
+ , node-babel-generator (<< 7)
+ , node-babel-helper-bindify-decorators (<< 7)
+ , node-babel-helper-builder-binary-assignment-operator-visitor (<< 7)
+ , node-babel-helper-builder-react-jsx (<< 7)
+ , node-babel-helper-call-delegate (<< 7)
+ , node-babel-helper-explode-assignable-expression (<< 7)
+ , node-babel-helper-explode-class (<< 7)
+ , node-babel-helper-function-name (<< 7)
+ , node-babel-helper-hoist-variables (<< 7)
+ , node-babel-helper-optimise-call-expression (<< 7)
+ , node-babel-helper-remap-async-to-generator (<< 7)
+ , node-babel-helper-replace-supers (<< 7)
+ , node-babel-helpers (<< 7)
+ , node-babel-plugin-external-helpers (<< 7)
+ , node-babel-plugin-syntax-async-generators (<< 7)
+ , node-babel-plugin-syntax-class-properties (<< 7)
+ , node-babel-plugin-syntax-decorators (<< 7)
+ , node-babel-plugin-syntax-do-expressions (<< 7)
+ , node-babel-plugin-syntax-dynamic-import (<< 7)
+ , node-babel-plugin-syntax-flow (<< 7)
+ , node-babel-plugin-syntax-function-bind (<< 7)
+ , node-babel-plugin-syntax-jsx (<< 7)
+ , node-babel-plugin-syntax-object-rest-spread (<< 7)
+ , node-babel-plugin-transform-async-to-generator (<< 7)
+ , node-babel-plugin-transform-exponentiation-operator (<< 7)
+ , node-babel-plugin-transform-flow-strip-types (<< 7)
+ , node-babel-plugin-transform-jscript (<< 7)
+ , node-babel-plugin-transform-proto-to-assign (<< 7)
+ , node-babel-plugin-transform-react-display-name (<< 7)
+ , node-babel-plugin-transform-react-jsx (<< 7)
+ , node-babel-plugin-transform-react-jsx-self (<< 7)
+ , node-babel-plugin-transform-react-jsx-source (<< 7)
+ , node-babel-plugin-transform-regenerator (<< 7)
+ , node-babel-plugin-transform-runtime (<< 7)
+ , node-babel-plugin-transform-strict-mode (<< 7)
+ , node-babel-preset-env (<< 7)
+ , node-babel-preset-flow (<< 7)
+ , node-babel-preset-react (<< 7)
+ , node-babel-register (<< 7)
+ , node-babel-template (<< 7)
+ , node-babel-traverse (<< 7)
+Replaces: node-babel-cli (<< 7)
+ , node-babel-code-frame (<< 7)
+ , node-babel-generator (<< 7)
+ , node-babel-helper-bindify-decorators (<< 7)
+ , node-babel-helper-builder-binary-assignment-operator-visitor (<< 7)
+ , node-babel-helper-builder-react-jsx (<< 7)
+ , node-babel-helper-call-delegate (<< 7)
+ , node-babel-helper-explode-assignable-expression (<< 7)
+ , node-babel-helper-explode-class (<< 7)
+ , node-babel-helper-function-name (<< 7)
+ , node-babel-helper-hoist-variables (<< 7)
+ , node-babel-helper-optimise-call-expression (<< 7)
+ , node-babel-helper-remap-async-to-generator (<< 7)
+ , node-babel-helper-replace-supers (<< 7)
+ , node-babel-helpers (<< 7)
+ , node-babel-plugin-external-helpers (<< 7)
+ , node-babel-plugin-syntax-async-generators (<< 7)
+ , node-babel-plugin-syntax-class-properties (<< 7)
+ , node-babel-plugin-syntax-decorators (<< 7)
+ , node-babel-plugin-syntax-do-expressions (<< 7)
+ , node-babel-plugin-syntax-dynamic-import (<< 7)
+ , node-babel-plugin-syntax-flow (<< 7)
+ , node-babel-plugin-syntax-function-bind (<< 7)
+ , node-babel-plugin-syntax-jsx (<< 7)
+ , node-babel-plugin-syntax-object-rest-spread (<< 7)
+ , node-babel-plugin-transform-async-to-generator (<< 7)
+ , 

Bug#1068933: node-babel7: FTBFS in bookworm against nodejs 18.19.0+dfsg-6~deb12u1

[Jérémy Lal]

Package: node-babel7
Version: 7.20.15+ds1+~cs214.269.168-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source

This package FTBFS When rebuilding it in bookworm, against
nodejs 18.19.0+dfsg-6~deb12u1
node-undici 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4
(not yet uploaded)

The way to fix it is by improving upon the existing patch tsc-workaround.

Error log:

tsc -b .
packages/babel-helper-transform-fixture-test-runner/src/index.ts(131,7): error 
TS2345: Argument of type '{ filename: string; displayErrors: boolean; 
lineOffset: number; cachedData: Buffer; }' is not assignable to parameter of 
type 'string | ScriptOptions'.
  Object literal may only specify known properties, and 'displayErrors' does 
not exist in type 'ScriptOptions'.
packages/babel-helper-transform-fixture-test-runner/src/index.ts(139,7): error 
TS2345: Argument of type '{ filename: string; displayErrors: boolean; 
lineOffset: number; cachedData: Buffer; produceCachedData: true; }' is not 
assignable to parameter of type 'string | ScriptOptions'.
  Object literal may only specify known properties, and 'displayErrors' does 
not exist in type 'ScriptOptions'.
make[1]: *** [debian/rules:68: override_dh_auto_build] Error 1



-- 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 node-babel7 depends on:
ii  node-ampproject-remapping   2.2.0+~cs5.15.37-1
ii  node-babel-plugin-add-module-exports1.0.4+dfsg1~cs5.8.0-4
ii  node-babel-plugin-polyfill-corejs2  0.3.3~0~20220913+ds1-1
ii  node-babel-plugin-polyfill-corejs3  0.6.0~0~20220913+ds1-1
ii  node-babel-plugin-polyfill-regenerator  0.4.1~0~20220913+ds1-1
ii  node-babel7-runtime 7.20.15+ds1+~cs214.269.168-6
ii  node-browserslist   4.22.1+~cs6.1.28-1
ii  node-chalk  5.3.0-1
ii  node-clone-deep 4.0.1+~cs7.0.2-1
ii  node-commander  9.4.1-1
ii  node-convert-source-map 1.9.0+~1.5.2-1
ii  node-core-js3.33.2-1
ii  node-core-js-compat 3.33.2-1
ii  node-core-js-pure   3.33.2-1
ii  node-debug  4.3.4+~cs4.1.7-1
ii  node-esutils2.0.3+~2.0.0-1
ii  node-find-cache-dir 3.3.2+~3.2.1-1
ii  node-fs-readdir-recursive   1.1.0+~1.1.0-1
ii  node-glob   8.1.0+~cs8.5.15-1
ii  node-globals13.23.0-1
ii  node-js-tokens  8.0.0-2
ii  node-jsesc  3.0.2+~3.0.1-1
ii  node-json5  2.2.3+dfsg-1
ii  node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-9
ii  node-lodash-packages4.17.21+dfsg+~cs8.31.198.20210220-9
ii  node-make-dir   3.1.0-3
ii  node-quick-lru  6.1.1-4
ii  node-regenerator-transform  0.15.2+~0.10.8-1
ii  node-regexpu-core   5.2.2-3
ii  node-resolve1.22.8+~cs5.34.15-2
ii  node-semver 7.5.4+~7.5.0-2
ii  node-slash  4.0.0-3
ii  node-source-map 0.7.0++dfsg2+really.0.6.1-15
ii  node-source-map-support 0.5.21+ds+~0.5.4-1
ii  node-to-fast-properties 3.0.1-3
ii  node-v8flags3.2.0+~3.1.1-1
ii  nodejs  18.19.1+dfsg-3

node-babel7 recommends no packages.

Versions of packages node-babel7 suggests:
pn  node-babel-plugin-polyfill-es-shims  
pn  node-babel7-debug

-- no debconf information

Bug#1068932: bookworm-pu: package node-v8-compile-cache/2.3.0-3+deb12u1

[Jérémy Lal]

Package: release.debian.org
Severity: normal
Tags: bookworm
X-Debbugs-Cc: node-v8-compile-ca...@packages.debian.org, Debian Javascript 
Maintainers 
Control: affects -1 + src:node-v8-compile-cache
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
FTBFS because of test failures, see #1068921
These are regressions caused by nodejs 18.19.0+dfsg-6~deb12u1

[ Impact ]
Only FTBFS

[ Tests ]
The tests are fixed, not skipped, so they will pass with
nodejs 18.19.0+dfsg-6~deb12u1 and node-undici 
5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4

[ Risks ]
Close to none

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
One patch that fixes the tests, consists of two commits cherr-picked,
and a small rewrite to allow the test to pass with nodejs 18.13 and 18.19.
diff -Nru node-v8-compile-cache-2.3.0/debian/changelog 
node-v8-compile-cache-2.3.0/debian/changelog
--- node-v8-compile-cache-2.3.0/debian/changelog2022-11-22 
13:06:02.0 +0100
+++ node-v8-compile-cache-2.3.0/debian/changelog2024-04-13 
17:52:45.0 +0200
@@ -1,3 +1,11 @@
+node-v8-compile-cache (2.3.0-3+deb12u1) UNRELEASED; urgency=medium
+
+  * Upload to bookworm-p-u
+  * patch: NativeCompileCache-test for Node 18.13 and 18.19
+and fix test mock. Closes: #1068921
+
+ -- Jérémy Lal   Sat, 13 Apr 2024 17:52:45 +0200
+
 node-v8-compile-cache (2.3.0-3) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru node-v8-compile-cache-2.3.0/debian/gbp.conf 
node-v8-compile-cache-2.3.0/debian/gbp.conf
--- node-v8-compile-cache-2.3.0/debian/gbp.conf 2022-11-22 13:06:02.0 
+0100
+++ node-v8-compile-cache-2.3.0/debian/gbp.conf 2024-04-13 15:00:41.0 
+0200
@@ -1,4 +1,5 @@
 [DEFAULT]
+debian-branch = debian/bookworm
 pristine-tar = True
 
 [import-orig]
diff -Nru 
node-v8-compile-cache-2.3.0/debian/patches/native-compile-cache-test.patch 
node-v8-compile-cache-2.3.0/debian/patches/native-compile-cache-test.patch
--- node-v8-compile-cache-2.3.0/debian/patches/native-compile-cache-test.patch  
1970-01-01 01:00:00.0 +0100
+++ node-v8-compile-cache-2.3.0/debian/patches/native-compile-cache-test.patch  
2024-04-13 17:51:42.0 +0200
@@ -0,0 +1,42 @@
+Description: fix this test to pass on nodejs 18.13 and 18.19
+Author: Jérémy Lal 
+Last-Update: 2024-04-13
+Forwarded: https://github.com/zertosh/v8-compile-cache/pull/49
+Origin: 
https://github.com/zertosh/v8-compile-cache/commit/de822a607c9dbe7cfc826a44c67fc5f82b03c9ca
+--- a/test/NativeCompileCache-test.js
 b/test/NativeCompileCache-test.js
+@@ -85,12 +85,14 @@
+ tap.test('deletes previously cached code when the cache is an invalid file', 
t => {
+   fakeCacheStore.has = () => true;
+   fakeCacheStore.get = () => Buffer.from('an invalid cache');
+-  let deleteWasCalledWith = null;
+-  fakeCacheStore.delete = arg => { deleteWasCalledWith = arg; };
++  let wasCalledWith = null;
++  fakeCacheStore.set = arg => { wasCalledWith = arg; };
++  // older v8 still calls delete, though
++  fakeCacheStore.delete = arg => { wasCalledWith = arg; };
+ 
+   const fn3 = require('./fixtures/file-3');
+ 
+-  t.equal(deleteWasCalledWith, require.resolve('./fixtures/file-3'));
++  t.equal(wasCalledWith, require.resolve('./fixtures/file-3'));
+   t.equal(fn3(), 3);
+ 
+   t.end();
+--- a/test/FileSystemBlobStore-mock.js
 b/test/FileSystemBlobStore-mock.js
+@@ -20,7 +20,14 @@
+   }
+ 
+   set(key, invalidationKey, buffer) {
++const entry = this._cachedFiles.find(
++  file => file.key === key && file.invalidationKey === invalidationKey
++);
++if (entry == null) {
+ this._cachedFiles.push({key, invalidationKey, buffer});
++} else {
++  entry.buffer = buffer;
++}
+ return buffer;
+   }
+ 
diff -Nru node-v8-compile-cache-2.3.0/debian/patches/series 
node-v8-compile-cache-2.3.0/debian/patches/series
--- node-v8-compile-cache-2.3.0/debian/patches/series   2022-11-22 
13:06:02.0 +0100
+++ node-v8-compile-cache-2.3.0/debian/patches/series   2024-04-13 
15:00:41.0 +0200
@@ -1 +1,2 @@
 latest-tap.patch
+native-compile-cache-test.patch

Bug#1068918: node-zx: FTBFS test suite failure

[Jérémy Lal]

Source: node-zx
Version: 7.1.1+~cs6.7.23-3
Followup-For: Bug #1068918
Control: tags -1 ftbfs

Failure:

make[1]: Leaving directory '/<>'
   dh_auto_test --buildsystem=nodejs
  ln -s ../. node_modules/zx
  /bin/sh -ex debian/tests/pkg-js/test
+ uvu -b -i extra.test.js|package.test.js test .*.test.js
^[[1m^[[4m^[[37mcli.test.js^[[22m^[[24m^[[39m
^[[47m^[[1m^[[30m cli ^[[39m^[[49m^[[22m ^[[90m• ^[[39m^[[90m• ^[[39m^[[90m• 
^[[39m^[[90m• ^[[39m^[[90m• ^[[39m^[[90m• ^[[39m^[[90m• ^[[39m^[[90m• 
^[[39m^[[90m• ^[[39m^[[90m• ^[[39m^[[90m• ^[[39m^[[90m• ^[[39m^[[90m• 
^[[39m^[[90m• ^[[39m^[[90m• ^[[39m^[[90m• ^[[39m^[[90m• ^[[39m^[[90m• 
^[[39m^[[31m✘ ^[[39m^[[90m• ^[[39m^[[31m  (19 / 20)
^[[39m
  ^[[1m^[[41m FAIL ^[[22m^[[49m^[[31m^[[47m^[[1m cli ^[[49m^[[22m^[[39m 
^[[2m"^[[22m^[[31m^[[1margv works with zx and node^[[39m^[[22m^[[2m"^[[22m
Expected values to be strictly equal:^[[3m^[[2m  (is)^[[23m^[[22m

^[[31m^[[4m^[[2m^[[3mActual:^[[22m^[[23m^[[39m^[[24m
^[[31m--[^[[2m·^[[22m^[[32m'baz'^[[39m^[[31m^[[2m·^[[22m]^[[39m
^[[32m^[[4m^[[2m^[[3mExpected:^[[22m^[[23m^[[39m^[[24m
^[[32m++[^[[2m·^[[22m'baz'^[[2m·^[[22m]^[[39m
^[[90m
at assert (file:///usr/share/nodejs/uvu/assert/index.mjs:33:8)
at Module.is (file:///usr/share/nodejs/uvu/assert/index.mjs:41:2)
at Object.handler (file:///<>/test/cli.test.js:166:10)
at async Number.runner (file:///usr/share/nodejs/uvu/dist/index.mjs:78:5)
at async Module.exec (file:///usr/share/nodejs/uvu/dist/index.mjs:141:33)
at async Module.run (file:///usr/share/nodejs/uvu/run/index.mjs:12:2)
at async /usr/share/nodejs/uvu/bin.js:26:5^[[39m


Exiting early before testing is finished.
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



-- 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

Bug#1068921: node-v8-compile-cache: FTBFS in bookworm, test suite fails

[Jérémy Lal]

Package: node-v8-compile-cache
Version: 2.4.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Even when built with node-undici 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4,
this package fails to build with:

not ok 2 - test/NativeCompileCache-test.js # time=149.066ms
  ---
  env: {}
  file: test/NativeCompileCache-test.js
  timeout: 3
  command: /usr/bin/node
  args:
- test/NativeCompileCache-test.js
  stdio:
- 0
- pipe
- 2
  cwd: /<>
  exitCode: 1
  ...



-- 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 node-v8-compile-cache depends on:
ii  nodejs  18.19.1+dfsg-3

node-v8-compile-cache recommends no packages.

node-v8-compile-cache suggests no packages.

-- no debconf information

Bug#1068920: bookworm-pu: package node-zx/7.1.1+~cs6.7.23-2+deb12u1

[Jérémy Lal]

Package: release.debian.org
Severity: normal
Tags: bookworm
X-Debbugs-Cc: node...@packages.debian.org, Debian Javascript Maintainers 

Control: affects -1 + src:node-zx
User: release.debian@packages.debian.org
Usertags: pu


[ Reason ]
Fix regression or just plain mistake.
node-zx currently FTBFS #1068918

[ Impact ]
None, it just fixes a test.

[ Tests ]
The test is run during build and autopkgtest:
"argv works with zx and node"

[ Risks ]
Very low risk, since it only affects a test.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
* patch: fix flaky test (upstream commit)

[ Other info ]
This requires node-undici 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4,
so should be part of the same bookworm-p-u

Bug#1068918: node-zx: FTBFS test suite failure

[Jérémy Lal]

Source: node-zx
Version: 7.1.1+~cs6.7.23-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

This package FTBFS in bookworm, even when using node-undici with fixed types.



-- 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

Bug#1068912: bookworm-pu: package node-undici/5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4

[Jérémy Lal]

Package: release.debian.org
Severity: normal
Tags: bookworm
X-Debbugs-Cc: node-und...@packages.debian.org, Debian Javascript Maintainers 

Control: affects -1 + src:node-undici
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
node-undici: FTBFS with nodejs 18.19.0+dfsg-6~deb12u1
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063530

[ Impact ]
node-undici FTBFS, also several other packages need node-undici
to properly export its typescript types, which it currently doesn't.

[ Tests ]
(What automated or manual tests cover the affected code?)
Rebuild+Autopkgtest should be enough to cover the affected code.
All this is caused by a regression introduced by nodejs 18.19.0+dfsg-6~deb12u1

[ Risks ]
No further risks.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
  * Import upstream patch that moves index.d.ts to types/ (closes #1063530)
  * Force @types/node to use local copy of undici-types
  * Fix build failures on lld 15+

[ Other info ]
node-zx, node-v8-compile-cache, node-babel7 will also be proposed,
to fix their tests suites w.r.t. the aforementioned regression.
diff -Nru node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/changelog 
node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/changelog
--- node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/changelog  2023-12-21 
11:14:59.0 +0100
+++ node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/changelog  2024-04-13 
11:22:02.0 +0200
@@ -1,3 +1,12 @@
+node-undici (5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4) UNRELEASED; urgency=medium
+
+  [ Ryan Gonzalez ]
+  * Import upstream patch that moves index.d.ts to types/ (closes #1063530)
+  * Force @types/node to use local copy of undici-types
+  * Fix build failures on lld 15+
+
+ -- Jérémy Lal   Sat, 13 Apr 2024 11:22:02 +0200
+
 node-undici (5.15.0+dfsg1+~cs20.10.9.3-1+deb12u3) bookworm-security; 
urgency=medium
 
   * Team upload.
diff -Nru node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/gbp.conf 
node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/gbp.conf
--- node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/gbp.conf   2023-12-21 
11:08:13.0 +0100
+++ node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/gbp.conf   2024-04-13 
11:19:52.0 +0200
@@ -1,4 +1,5 @@
 [DEFAULT]
+debian-branch = bookworm
 pristine-tar=True
 filter=[ '.gitignore', '.travis.yml', '.git*' ]
 component=['llhttp', 'llparse', 'llparse-frontend', 'llparse-builder', 
'binary-search']
diff -Nru node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/nodejs/build 
node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/nodejs/build
--- node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/nodejs/build   2023-12-21 
11:08:13.0 +0100
+++ node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/nodejs/build   2024-04-13 
11:18:29.0 +0200
@@ -10,7 +10,7 @@
 #  - direct clang call
 clang -nodefaultlibs --sysroot=/usr -target wasm32-unknown-wasi \
-Ofast -fno-exceptions -fvisibility=hidden \
-   -mexec-model=reactor -Wl,-lc -Wl,-error-limit=0 -Wl,-O3 \
+   -mexec-model=reactor -Wl,-lc -Wl,--error-limit=0 -Wl,-O3 \
-Wl,--lto-O3 -Wl,--strip-all -Wl,--allow-undefined \
-Wl,--export-dynamic -Wl,--export-table -Wl,--export=malloc \
-Wl,--export=free \
diff -Nru node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/nodejs/extcopies 
node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/nodejs/extcopies
--- node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/nodejs/extcopies   
1970-01-01 01:00:00.0 +0100
+++ node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/nodejs/extcopies   
2024-04-13 11:18:29.0 +0200
@@ -0,0 +1 @@
+@types/node
diff -Nru node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/nodejs/extlinks 
node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/nodejs/extlinks
--- node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/nodejs/extlinks
2022-10-22 13:28:40.0 +0200
+++ node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/nodejs/extlinks
2024-04-13 11:18:29.0 +0200
@@ -1,4 +1,3 @@
 busboy
 @types/debug
-@types/node
 @types/semver
diff -Nru 
node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/patches/Add-publish-types-script-2273.patch
 
node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/patches/Add-publish-types-script-2273.patch
--- 
node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/patches/Add-publish-types-script-2273.patch
1970-01-01 01:00:00.0 +0100
+++ 
node-undici-5.15.0+dfsg1+~cs20.10.9.3/debian/patches/Add-publish-types-script-2273.patch
2024-04-13 11:18:29.0 +0200
@@ -0,0 +1,341 @@
+From: Ethan Arrowood 
+Date: Wed, 20 Sep 2023 15:02:42 -0600
+Subject: Add publish types script (#2273)
+
+* add publish types script
+
+* use postpublish script
+
+* 5.24.0-test.0
+
+* 5.24.0-test.1
+
+* uncomment
+
+* 5.24.0-test.2
+
+* simplify automation
+
+* 5.24.0-test.3
+
+* fix script
+
+* 5.24.0-test.4
+
+* fix script
+
+* 5.24.0

Bug#1068842: Acknowledgement (node-undici: Fail upon being required)

[Jérémy Lal]

The problem is this line at
https://salsa.debian.org/js-team/node-undici/-/blame/master/debian/nodejs/build#L20
echo 'module.exports = "'`perl -MMIME::Base64 -000 -ne 'print
encode_base64($_,"")' lib/llhttp/llhttp-wasm`'";' >
lib/llhttp/llhttp-wasm.js

it doesn't do what it is supposed to do
node -r .
> Uncaught CompileError: WebAssembly.compile(): expected 48177 bytes, fell
off end @+1361

However it doesn't throw, when doing the same job with:
fs.writeFileSync('lib/llhttp/llhttp-wasm.js', `module.exports =
'${fs.readFileSync('lib/llhttp/llhttp-wasm').toString('base64')}'\n`)

I don't know perl... is MMIME::Base64 module broken in some weird and
suspicious way (i'm being paranoid) ?

Anyway I don't see the point in doing the compilation without using
build/wasm.js,
since node-undici requires nodejs to be built fully.
It is somewhat simpler to use the build-profiles / two-staged nodejs build
method,
only on nodejs, instead of requiring some other node module to be built in
two stages too.

For these reasons I'm reverting this back to using build/wasm.js

Jérémy

Bug#1068842: node-undici: Fail upon being required

[Jérémy Lal]

Package: node-undici
Version: 5.28.4+dfsg1+~cs23.12.11-1
Severity: important

Hi,

Building node-undici in unstable (with nodejs 18.20.1 / openssl 3.2),
then requiring it, fails with;
Uncaught CompileError: WebAssembly.compile(): expected 48120 bytes, fell off 
end @+1361

Works fine in same environment with node-undici-5.28.2+dfsg1+_cs23.11.12.3-6.

It's not a wasi-glibc regression. No idea what's happening, yet.

It would be nice to figure this out, since it's going to block a needed nodejs 
transition.

-- 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

-- no debconf information

Bug#1067636: nodejs: Testsuite fails with openssl 3.2

[Jérémy Lal]

Le dim. 24 mars 2024 à 21:51, Sebastian Andrzej Siewior <
sebast...@breakpoint.cc> a écrit :

> Package: nodejs
> Version: 18.19.1+dfsg-6
> Severity: important
> Tags: sid
> control: affects -1 src:openssl
> User: pkg-openssl-de...@lists.alioth.debian.org
> Usertags: openssl-3.2
>
> Hi,
>
> I rebuilt nodejs in unstable against openssl 3.2 in experimental an a
> few tests failed:
>
> | Failed tests:
> | ./node /<>/test/parallel/test-crypto-rsa-dsa.js
> | ./node /<>/test/parallel/test-tls-alert-handling.js
> | ./node /<>/test/parallel/test-tls-client-auth.js
> | ./node /<>/test/parallel/test-tls-empty-sni-context.js
> | ./node --expose-internals
> /<>/test/parallel/test-tls-enable-trace.js
> | ./node --expose-internals
> /<>/test/parallel/test-tls-enable-trace-cli.js
> | ./node /<>/test/parallel/test-tls-getcipher.js
> | ./node /<>/test/parallel/test-tls-junk-server.js
> | ./node /<>/test/parallel/test-tls-psk-circuit.js
> | ./node /<>/test/parallel/test-tls-set-ciphers.js
> | ./node /<>/test/parallel/test-tls-junk-closes-server.js

Any idea how to proceed?
> I've been reading https://github.com/nodejs/node/issues/51152 but I
> don't think 3.2 support has been integrated somewhere as they just
> discussed their fork part and so on.
>
> I've been looking at the errors and some are "error code changed". I
> *think* the trace errors changed also slightly. I don't know why
> get/set-ciphers failed.


Could you share the full build log ?

Bug#1067418: Tests fail on 32-bit t64 arches

[Jérémy Lal]

Source: tpm2-tss
Followup-For: Bug #1067418

Upstream will just skip those tests on 32-bit:
https://github.com/tpm2-software/tpm2-tss/commit/932b1e78047ed0ddc09fcb06bff2e7cf96406976


-- 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

Bug#1067409: scapy: Tests failures with python3-cryptography >= 42

[Jérémy Lal]

Source: scapy
Version: 2.5.0+dfsg-2
Severity: normal

Hi,

scapy tests fail against cryptography 42, preventing its migration.
Fix:
https://salsa.debian.org/pkg-security-team/scapy/-/merge_requests/3

Jérémy


-- 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

Bug#1067384: node-ajv: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 134

[Jérémy Lal]

Le mer. 20 mars 2024 à 22:14, Lucas Nussbaum  a écrit :

> Source: node-ajv
> Version: 8.12.0~ds+~2.1.1-4
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240319 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > tsc
> > cp -r lib/refs dist
> > rm dist/refs/json-schema-2019-09/index.ts
> > rm dist/refs/json-schema-2020-12/index.ts
> > rm dist/refs/jtd-schema.ts
> > dh_auto_build --buildsystem=nodejs
> > Found debian/nodejs/ajv-formats/build
> >   cd ./ajv-formats && sh -ex ../debian/nodejs/ajv-formats/build
> > + mkdir -p node_modules
> > + ln -s ../.. node_modules/ajv
> > + tsc
> > + rm -rf node_modules
> > make[1]: Leaving directory '/<>'
> >dh_auto_test --buildsystem=nodejs
> >   ln -s ../debian/tests/test_modules/fast-uri node_modules/fast-uri
> >   ln -s ../debian/tests/test_modules/json-schema-test
> node_modules/json-schema-test
> >   ln -s ../debian/tests/test_modules/module-from-string
> node_modules/module-from-string
> >   ln -s ../. node_modules/ajv
> >   /bin/sh -ex debian/tests/pkg-js/test
> > + rm -f spec/_json/*.js
> > + node scripts/jsontests
> > + test  !=
> > + TS_NODE_PROJECT=spec/tsconfig.json mocha --bail --exit --timeout
> 10 -r ts-node/register spec/**/*.spec.{ts,js}
> > Aborted
> > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit
> code 134
>

It's a crash when running
spec/issues/1683_re2_engine.spec.ts

Jérémy

Bug#1067389: scapy: please move scapy to python team

[Jérémy Lal]

Source: scapy
Version: 2.5.0+dfsg-2
Severity: wishlist

It would allow team uploads when other python modules
are upgraded. It makes sense, scapy being a python module.

Currently there's python-cryptography 42 that has been
uploaded too soon, and fixing scapy requires an upstream patch,
see merge request in salsa.

However, python team has no right to the scapy salsa repo,
and cannot team upload it, so it will somewhat slower at
a time it should have been quicker.

Jérémy




-- 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

Bug#1067027: python-cryptography build-dependencies unsatisfiable.

[Jérémy Lal]

Emmanuel,



Le dim. 17 mars 2024 à 04:39, Peter Michael Green  a
écrit :

> Package: python-cryptography
> Version: 41.0.7-5
> Severity: serious
> x-debbugs-cc: eam...@debian.org, kapo...@melix.org
>
>
> python-cryptography build-depends on python3-cryptography-vectors (<<
> 41.0.8~)
> but unstable has version 42.0.5-1
>

You uploaded that one...
Did you plan to upload matching python3-cryptography 42.0.5 in unstable
very soon ?
Now we have mismatched versions in unstable, and I didn't proceed with
python-cryptography 42
because it still wasn't working in unstable.
Now we must make it work :(


>
> If you need rust package updates to fix this issue, please tell me what
> they are and
> I will see what I can do.
>

The last missing piece seems to be version >= 3 of
https://tracker.debian.org/pkg/rust-pem

This is blocking the time64 transition for python-cryptography.
>


Jérémy

Bug#1066409: Linker fails to find libraries in unstable but succeeds in testing

[Jérémy Lal]

Le ven. 15 mars 2024 à 11:17, Jérémy Lal  a écrit :

>
>
> Le ven. 15 mars 2024 à 08:46, Jochen Sprickerhof  a
> écrit :
>
>> Hi Andreas,
>>
>> * Andreas Tille  [2024-03-15 07:31]:
>> >Hi,
>> >
>> >thanks to the next round of Lucas' FTBFS QA rebuilds (at least) one
>> >package of the R pkg team is affected by some strange linker issue
>> >
>> >#1066409 r-cran-v8: FTBFS: ld: cannot find -lv8: No such file or
>> directory
>> >which boils down to[1]
>> >
>> >g++ -std=gnu++17 -shared -L/usr/lib/R/lib -Wl,-z,relro -o V8.so
>> RcppExports.o bindings.o -lv8 -lv8_libplatform -L/usr/lib/R/lib -lR
>> >/usr/bin/ld: cannot find -lv8: No such file or directory
>> >/usr/bin/ld: cannot find -lv8_libplatform: No such file or directory
>> >
>> >The Build-Depends libnode-dev provides both libraries and when I try to
>> >build the package under testing all is fine.  Is there any linker issue
>> >involved that might be introduced in unstable?
>>
>> I guess that's the same as #1066399.
>>
>> libnode-dev:
>> libv8.so -> libnode.so
>> libnode.so -> libnode.so.108t64
>>
>> But libnode.so.108t64 does not exist
>>
>
> That's fixed in nodejs 18.19.1+dfsg-5
>

rejected, I forgot to not do a source upload. Rebuilding...

Instead of suffixing the soname (not compatible with node's toolchain) I
> just bumped the soname number to 109,
> while node 20 has 115 so there won't be any conflict.
>

Bug#1066409: Linker fails to find libraries in unstable but succeeds in testing

[Jérémy Lal]

Le ven. 15 mars 2024 à 08:46, Jochen Sprickerhof  a
écrit :

> Hi Andreas,
>
> * Andreas Tille  [2024-03-15 07:31]:
> >Hi,
> >
> >thanks to the next round of Lucas' FTBFS QA rebuilds (at least) one
> >package of the R pkg team is affected by some strange linker issue
> >
> >#1066409 r-cran-v8: FTBFS: ld: cannot find -lv8: No such file or directory
> >which boils down to[1]
> >
> >g++ -std=gnu++17 -shared -L/usr/lib/R/lib -Wl,-z,relro -o V8.so
> RcppExports.o bindings.o -lv8 -lv8_libplatform -L/usr/lib/R/lib -lR
> >/usr/bin/ld: cannot find -lv8: No such file or directory
> >/usr/bin/ld: cannot find -lv8_libplatform: No such file or directory
> >
> >The Build-Depends libnode-dev provides both libraries and when I try to
> >build the package under testing all is fine.  Is there any linker issue
> >involved that might be introduced in unstable?
>
> I guess that's the same as #1066399.
>
> libnode-dev:
> libv8.so -> libnode.so
> libnode.so -> libnode.so.108t64
>
> But libnode.so.108t64 does not exist
>

That's fixed in nodejs 18.19.1+dfsg-5
Instead of suffixing the soname (not compatible with node's toolchain) I
just bumped the soname number to 109,
while node 20 has 115 so there won't be any conflict.

Bug#1066038: node-glob: Please update to glob 10

[Jérémy Lal]

Le lun. 11 mars 2024 à 15:03, Jérémy Lal  a écrit :

> Package: node-glob
> Version: 8.1.0+~cs8.5.15-1
> Severity: wishlist
>
> glob 8 doesn't export ECMAScript module.
>
> glob 10 supports both, it would be very nice to have it in debian.
>

I've started working on it...

Bug#1066038: node-glob: Please update to glob 10

[Jérémy Lal]

Package: node-glob
Version: 8.1.0+~cs8.5.15-1
Severity: wishlist

glob 8 doesn't export ECMAScript module.

glob 10 supports both, it would be very nice to have it in debian.


-- 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 node-glob depends on:
ii  node-fs.realpath  1.0.0-3
ii  node-inflight 1.0.6-2
ii  node-inherits 2.0.4-6
ii  node-minimatch9.0.3-4
ii  node-once 1.4.1-1

node-glob recommends no packages.

node-glob suggests no packages.

-- no debconf information

Bug#1066027: ITP: node-import-meta-resolve -- Ponyfill for import.meta.resolve - Node.js module

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Javascript Maintainers 


* Package name: node-import-meta-resolve
  Version : 4.0.0-1
  Upstream Contact: Titus Wormer 
* URL : https://github.com/wooorm/import-meta-resolve
* License : Expat
  Programming Lang: JavaScript
  Description : Ponyfill for import.meta.resolve - Node.js module

 A module-relative resolution function scoped to each module,
 returning the URL string.
 This module backports an experimental Node.js 21 implementation
 of a standard ECMAScript modules feature.
 It will allow smoother transitions when upgrading Node.js.
 .
 Node.js is an event-based server-side JavaScript engine.

This module will be team-maintained.

It is an indirect dependency of a bundled front-end module of AWX,
however, I bet it will be needed in the coming months, since
it exposes an interface that is not available by default until
at least Node 22.

Bug#1065662: FTBFS: error: aborting due to unexpected upstream changes

[Jérémy Lal]

Source: ipywidgets
Version: 8.1.1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Rebuilding
https://deb.debian.org/debian/pool/main/i/ipywidgets/ipywidgets_8.1.1-4.dsc
in a clean sid chroot fails with
error: aborting due to unexpected upstream changes



-- 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

Bug#1065609: rust-openssl: Please update rust-openssl

[Jérémy Lal]

Package: rust-openssl
Version: 0.10.57-1
Severity: wishlist

python-cryptography actually buid-depends on a more recent version,
and I have not been able to workaround that.
Likewise for rust-openssl-sys...

Jérémy



-- 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

Bug#1064558: [Pkg-javascript-devel] Bug#1064558: node-leveldown: FTBFS on mips64el: not ok 1397 Error: batch(array) element must be an object and not `null`

[Jérémy Lal]

Le dim. 3 mars 2024 à 07:57, Yadd  a écrit :

> On 2/24/24 13:10, Sebastian Ramacher wrote:
> > Source: node-leveldown
> > Version: 5.6.0+dfsg-4
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source (but built successfully in the
> past)
> > X-Debbugs-Cc: sramac...@debian.org
> >
> >
> https://buildd.debian.org/status/fetch.php?pkg=node-leveldown=mips64el=5.6.0%2Bdfsg-4%2Bb1=1708632735=0
> >
> > not ok 1397 Error: batch(array) element must be an object and not `null`
> >---
> >  operator: error
> >  stack: |-
> >Error: batch(array) element must be an object and not `null`
> >at AbstractLevelDOWN.batch
> (/usr/share/nodejs/abstract-leveldown/abstract-leveldown.js:163:33)
> >at /<>/test/iterator-recursion-test.js:48:8
> >at
> /usr/share/nodejs/abstract-leveldown/abstract-leveldown.js:41:5
> >...
> >
> > Cheers
>
> Hi Jérémy,
>
> when trying to build on mips64el porterbox, i got this:
>
> make[1]: Entering directory '/home/yadd/node-leveldown'
> node-gyp clean
> node: error while loading shared libraries: libnode.so.108: cannot open
> shared object file: No such file or directory
>

In Sid, I am afraid it has been renamed to libnode108t64 or something like
that.
I'll have a look later today.

Jérémy

Bug#1065166: mpv: no sound when playing video

[Jérémy Lal]

Package: mpv
Version: 0.37.0-1
Severity: normal

There is no sound when playing a video (mkv or mp4).

This happened some time in the last week of february.

Playing a sound file still works, though.

Note: using debian/trixie, not sid

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (101, '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 mpv depends on:
ii  libarchive13  3.7.2-1
ii  libasound21.2.10-3
ii  libass9   1:0.17.1-2
ii  libavcodec60  7:6.1.1-1
ii  libavdevice60 7:6.1.1-1
ii  libavfilter9  7:6.1.1-1
ii  libavformat60 7:6.1.1-1
ii  libavutil58   7:6.1.1-1
ii  libbluray21:1.3.4-1
ii  libc6 2.37-15
ii  libcaca0  0.99.beta20-4
ii  libcdio-cdda2 10.2+2.0.1-1
ii  libcdio-paranoia2 10.2+2.0.1-1
ii  libcdio19 2.1.0-4
ii  libdrm2   2.4.120-2
ii  libdvdnav46.1.1-1
ii  libegl1   1.7.0-1
ii  libgbm1   23.3.5-1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-3+b1
ii  libjpeg62-turbo   1:2.1.5-2+b2
ii  liblcms2-22.14-2+b1
ii  liblua5.2-0   5.2.4-3+b1
ii  libmujs3  1.3.3-3+b1
ii  libpipewire-0.3-0 1.0.3-1
ii  libplacebo338 6.338.2-1
ii  libpulse0 16.1+dfsg1-3
ii  librubberband23.3.0+dfsg-2
ii  libsdl2-2.0-0 2.30.0+dfsg-1
ii  libsixel1 1.10.3-3
ii  libswresample47:6.1.1-1
ii  libswscale7   7:6.1.1-1
ii  libuchardet0  0.0.8-1+b1
ii  libva-drm22.20.0-2
ii  libva-wayland22.20.0-2
ii  libva-x11-2   2.20.0-2
ii  libva22.20.0-2
ii  libvdpau1 1.5-2
ii  libvulkan11.3.275.0-1
ii  libwayland-client01.22.0-2.1+b1
ii  libwayland-cursor01.22.0-2.1+b1
ii  libwayland-egl1   1.22.0-2.1+b1
ii  libx11-6  2:1.8.7-1
ii  libxext6  2:1.3.4-1+b1
ii  libxkbcommon0 1.6.0-1
ii  libxpresent1  1.0.0-2+b10
ii  libxrandr22:1.5.2-2+b1
ii  libxss1   1:1.2.3-1
ii  libxv12:1.0.11-1.1
ii  libzimg2  3.0.5+ds1-1+b1
ii  zlib1g1:1.3.dfsg-3+b1

Versions of packages mpv recommends:
ii  xdg-utils  1.1.3-4.1
ii  yt-dlp 2023.11.16-1

Versions of packages mpv suggests:
pn  libcuda1  

-- no debconf information

Bug#1064979: O: python-cryptography -- Python library exposing cryptographic recipes and primitives (documentation)

[Jérémy Lal]

Le jeu. 29 févr. 2024 à 12:06, Andreas Tille  a écrit :

> Hi,
>
> as per bug #1064979 python-cryptography was orphaned.  Actually the
> process of orphaninig is defined differently[1] by setting QA team as
> maintainer.  In this case DPT remains maintainer but there is no
> Uploader specified any more.  I personally will not add my ID as
> Uploader.  I have added those team members who did uploads in the last
> year in CC.
>

Good idea since I'm all right with helping to maintain it.
I did the 41 upgrade so I'm already familiar with it.

I'll AMAU unless someone is more motivated.
Source package python-cryptography-vectors needs the same treatment.

I tried to do some bug squashing anyway.  Since the latest version was
> requested in bug #1063771 and this new version also closes #1064778
> (CVE-2024-26130) (the other CVE-bug should have been closed in previous
> upload) I decided to inject latest upstream, adapted the patches and
> pushed to Git.  Unfortunately the package does not build as you can
> verify in Salsa CI[1].

I admit I have no clue how to fix this but I hope someone can take over
> from here.  I guess uploading to experimental first and see how it
> plays nicely with its lots of rdepends makes sense here.


Version 42 needs some rust deps to be updated as well, last time I checked,
and I was in wait-and-see mode about those.

Jérémy

Bug#1063530: node-undici: FTBFS with nodejs 18.19.0+dfsg-6~deb12u1

[Jérémy Lal]

Le ven. 9 févr. 2024 à 14:33, Dylan Aïssi  a écrit :

> Source: node-undici
> Version:  5.15.0+dfsg1+~cs20.10.9.3-1+deb12u3
> Severity: serious
> Tags: bookworm
> Usertags: apertis-ftbfs
> Justification: FTBFS
>
> Hello,
>
> While doing a rebuild of some node packages in Bookworm, it appears several
> packages (at least ~ 50 pkgs) no longer build with nodejs
> 18.19.0+dfsg-6~deb12u1
> (from bookworm-security repo) while they still successfully build with
> nodejs
> 18.13.0+dfsg1-1 (from the main bookworm repo). They all fail with the
> same error:
> error TS2307: Cannot find module 'undici-types' or its corresponding
> type declarations.
>
> Since, I am not sure which package need to be fixed (nodejs, node-undici or
> all of them), I fill this bug against the package referred by the error
> message,
> please reassign to the relevent package.


The latest nodejs (security | branch) update needs node-undici to export
its own "undici-types".
It seems that it doesn't, and that's probably my mistake.

Once that is fixed, three other packages need their test suites to be fixed
and uploaded to stable-proposed-updates.

> > > node-zx is a regression in the test suite only, fixed there:
> > https://salsa.debian.org/js-team/node
-zx/-/commit/a7d2861413480261890db147ea367a252192c9f2

> > > node-v8-compile-cache is a regression in the test suite only, fixed
> > there:
> > https://salsa.debian.org/js-team/node
-v8-compile-cache/-/commit/df42bdbfe84811e4da11d8c3d8ef3148d8a77bcc

> > > node-babel7 is a regression in the test suite, fixed there:
> > https://salsa.debian.org/js-team/node
-babel/-/commit/e5c88f4d765e4d64b60c9cf333dedb89abba39c5

Bug#1063771: Please update to version 42, needed for new dnspython

[Jérémy Lal]

Will do, but right now there are a bunch of rust dependencies that need to
be upgraded.

Bug#1059308: python-cryptography: CVE-2023-50782

[Jérémy Lal]

Shouldn't this be assigned to openssl ?

Bug#1061440: azure-cosmos-table-python: autopkgtest failure with Python 3.12

[Jérémy Lal]

Source: azure-cosmos-table-python
Followup-For: Bug #1061440

This package is deprecated, in favor of the python3-azure debian package.

Please don't fix this bug, and let's get this eventually autoremoved.


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

Kernel: Linux 6.6.13-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

Bug#1063345: python3.12: Segmentation fault in get_module_state_by_cls at ../Modules/itertoolsmodule.c

[Jérémy Lal]

Package: python3.12
Version: 3.12.1-2
Severity: normal

Hi,

python3-celery test suite crashes with python 3.12 during gc before exit (see 
attached stack trace).

It can be reproduced quickly with

apt build-dep celery
dget -xu https://deb.debian.org/debian/pool/main/c/celery/celery_5.3.4-2.dsc
cd celery-5.3.4
python3.12 -m pytest -v 
t/unit/tasks/test_canvas.py::test_group::test_apply_contains_chords_containing_empty_chain
 t/unit/tasks/test_canvas.py::test_group::test_apply
 
> Results (0.56s):
   1 passed
   1 xfailed
Erreur de segmentation (core dumped)

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

Kernel: Linux 6.6.13-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 python3.12 depends on:
ii  libpython3.12-stdlib  3.12.1-2
ii  media-types   10.1.0
ii  python3.12-minimal3.12.1-2
ii  tzdata2023d-1

Versions of packages python3.12 recommends:
ii  ca-certificates  20230311

Versions of packages python3.12 suggests:
ii  binutils 2.42-2
pn  python3.12-doc   
pn  python3.12-venv  

-- no debconf information
#0  0x7f9768de516c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f9768d97472 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x0069c0d0 in faulthandler_fatal_error (signum=6) at 
../Modules/faulthandler.c:329
#3  
#4  0x7f9768de516c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x7f9768d97472 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#6  0x7f9768d814b2 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x7f9768d813d5 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#8  0x7f9768d903a2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
#9  0x006d1f78 in _PyType_GetModuleState (type=) at 
../Include/internal/pycore_typeobject.h:105
#10 0x006d1f81 in get_module_state_by_cls (cls=) at 
../Modules/itertoolsmodule.c:52
#11 0x006d26ea in teedataobject_clear (tdo=tdo@entry=0x2e30800) at 
../Modules/itertoolsmodule.c:835
#12 0x006d3f4a in teedataobject_dealloc (tdo=0x2e30800) at 
../Modules/itertoolsmodule.c:845
#13 0x005026bd in _Py_Dealloc (op=op@entry=) at ../Objects/object.c:2625
#14 0x006d22f0 in Py_DECREF (filename=filename@entry=0x72c1d7 
"../Modules/itertoolsmodule.c", lineno=lineno@entry=1050, 
op=) at ../Include/object.h:691
#15 0x006d56dd in tee_clear (to=to@entry=0x7f97655226f0) at 
../Modules/itertoolsmodule.c:1050
#16 0x006d5707 in tee_dealloc (to=0x7f97655226f0) at 
../Modules/itertoolsmodule.c:1059
#17 0x005026bd in _Py_Dealloc (op=op@entry=) at ../Objects/object.c:2625
#18 0x004d53ee in Py_DECREF (filename=filename@entry=0x714e38 
"../Objects/frameobject.c", lineno=lineno@entry=911, op=) at ../Include/object.h:691
#19 0x004d66c1 in frame_dealloc (f=Python Exception : <__main__.PyCodeObjectPtr object at 0x7fbd68277bd0>
) at ../Objects/frameobject.c:911
#20 0x005026bd in _Py_Dealloc (op=op@entry=Python Exception : There is no member named f_frame.
) at ../Objects/object.c:2625
#21 0x0061acdc in Py_DECREF (filename=filename@entry=0x70d22f 
"../Include/object.h", lineno=lineno@entry=799, op=Python Exception : There is no member named f_frame.
) at ../Include/object.h:691
#22 0x0061ad7d in Py_XDECREF (op=) at 
../Include/object.h:799
#23 0x0061af2d in tb_dealloc (tb=0x7f9765a1fca0) at 
../Python/traceback.c:191
#24 0x005026bd in _Py_Dealloc (op=op@entry=) at ../Objects/object.c:2625
#25 0x0061acdc in Py_DECREF (filename=filename@entry=0x70d22f 
"../Include/object.h", lineno=lineno@entry=799, op=) at ../Include/object.h:691
#26 0x0061ad7d in Py_XDECREF (op=) at 
../Include/object.h:799
#27 0x0061af24 in tb_dealloc (tb=0x7f9765a1e350) at 
../Python/traceback.c:190
#28 0x005026bd in _Py_Dealloc (op=op@entry=) at ../Objects/object.c:2625
#29 0x0061acdc in Py_DECREF (filename=filename@entry=0x70d22f 
"../Include/object.h", lineno=lineno@entry=799, op=) at ../Include/object.h:691
#30 0x0061ad7d in Py_XDECREF (op=) at 
../Include/object.h:799
#31 0x0061af24 in tb_dealloc (tb=0x7f9765a1eee0) at 
../Python/traceback.c:190
#32 0x005026bd in _Py_Dealloc (op=op@entry=) at ../Objects/object.c:2625
#33 0x0061acdc in Py_DECREF (filename=filename@entry=0x70d22f 
"../Include/object.h", lineno=lineno@entry=799, op=) at ../Include/object.h:691
#34 0x0061ad7d in Py_XDECREF (op=) at 
../Include/object.h:799
#35 0x0061af24 in tb_dealloc (tb=0x7f9765aeb7a0) at 
../Python/traceback.c:190
#36 0x005026bd in _Py_Dealloc (op=op@entry=) at ../Objects/object.c:2625
#37 0x0061acdc in Py_DECREF 

Bug#1061620: autopkgtest: Ignores multiple comma-separated values in Testsuite

[Jérémy Lal]

Package: autopkgtest
Version: 5.32
Severity: normal

Having in debian/control:
Testsuite: autopkgtest-pkg-python, autopkgtest-pkg-pybuild

tests two different things, and having both is nice.

However it seems autopkgtest doesn't consider the field can have multiple 
values,
it only runs one of them - or actually it might fallback to a default test,
because it doesn't recognize the field value.

Code concerned is in lib/testdesc.py

This won't run:
https://sources.debian.org/src/python-keycloak/3.3.0+dfsg-2/debian/control/?hl=30#L30



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

Kernel: Linux 6.5.0-5-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 autopkgtest depends on:
ii  apt-utils   2.7.10
ii  libdpkg-perl1.22.2
ii  mawk1.3.4.20231126-1
ii  procps  2:4.0.4-2+b1
ii  python3 3.11.6-1
ii  python3-debian  0.1.49

Versions of packages autopkgtest recommends:
ii  autodep8  0.28
ii  fakeroot  1.33-1

Versions of packages autopkgtest suggests:
pn  docker.io
pn  fakemachine  
ii  genisoimage  9:1.1.11-3.4
pn  incus
ii  lxc  1:5.0.3-2
pn  lxd  
ii  ovmf 2023.11-5
pn  ovmf-ia32
ii  podman   4.8.3+ds1-2
ii  python3-distro-info  1.7
pn  qemu-efi-aarch64 
pn  qemu-efi-arm 
ii  qemu-system  1:8.2.0+ds-5
ii  qemu-utils   1:8.2.0+ds-5
ii  schroot  1.6.13-3+b3
ii  util-linux   2.39.3-6
ii  vmdb20.28-1
ii  zerofree 1.1.1-1

-- no debconf information

Bug#1058317: celery: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Jérémy Lal]

Source: celery
Followup-For: Bug #1058317

Note the segmentation fault at the end of python 3.12 pytest run.

Using export PYTHONFAULTHANDLER=1 before running the tests, I only got
an error in garbage-collector, no trace.

It is a bit like #1055717, which was closed by
https://salsa.debian.org/python-team/packages/python-multidict/-/commit/2d54ca0b

Also I tried with celery 5.3.6, and also with kombu 5.3.5 and vine 5.1.0, no 
luck.

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

Kernel: Linux 6.5.0-5-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

Bug#1060793: ITP: node-luxon -- Wrapper for JavaScript dates and times

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Javascript Maintainers 


* Package name: node-luxon
  Version : 3.4.4
  Upstream Contact: https://github.com/moment/luxon/issues
* URL : https://moment.github.io/luxon/
* License : Expat
  Programming Lang: JavaScript
  Description : Wrapper for JavaScript dates and times

 Luxon provides a set of powerful, modern, and friendly wrappers for
 DateTimes, Durations and Intervals. The API is immutable, chainable,
 and unambiguous. It uses native time zones and internationalization.

Luxon is often used in webapps.
It will be maintained within Javascript team.
In particular I need to upload to Debian to use it in the front-end of AWX 
package.

Bug#1060429: solo1-cli has an undeclared file conflict on /usr/lib/python3/dist-packages/solo/__init__.py

[Jérémy Lal]

I've reassigned it to solo1-cli,
because I thought it wasn't a library (and the start of the docs lead me to
it), but actually it is a library.

My mistake, re-reassigning to django_solo, the newcomer has to go elsewhere.

Bug#1060430: ITP: python-django-test-migrations -- Testing database migrations for Django

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Python Team 


* Package name: python-django-test-migrations
  Version : 1.3.0
  Upstream Contact: Nikita Sobolev 
* URL : https://github.com/wemake-services/django-test-migrations
* License : Expat
  Programming Lang: Python
  Description : Testing database migrations for Django

 This framework allows one to test migrations with respect to:
  * schema and data
  * forward and rollback
  * order, names
  * database configuration
 It also features fully typed annotations.
 .
 Django is a high-level Python web development framework.

This package will be maintained in python team.

It is a test dependency of awx.
It seems to be a nice piece for testing in Django, and is alive.

Bug#1060311: vitrage: Please Build-Depends: python3-asn1

[Jérémy Lal]

Package: vitrage
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Version 11 of vitrage depends on a package that I just uploaded to debian,
which is great !
But vitrage still needs to depend on it :)

Jérémy


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

Kernel: Linux 6.5.0-5-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

Bug#1060309: tpm2-pytss: please upgrade to version 2.2.0

[Jérémy Lal]

Package: tpm2-pytss
Version: 2.1.0-2
Severity: normal

For compatibility with python3-cryptography 41.0.7,
so it can migrate to testing.

Thanks,
Jérémy


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

Kernel: Linux 6.5.0-5-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

Bug#1060265: Acknowledgement (ITP: python-django-ansible-base -- Reusable base for Ansible applications using Django)

[Jérémy Lal]

django-ansible-base is not yet published on pypi, so for now it'll stay
embedded in awx.

Bug#1060265: ITP: python-django-ansible-base -- Reusable base for Ansible applications using Django

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Python Team 


* Package name: python-django-ansible-base
  Version : 0.1.0
  Upstream Contact: John Westcott IV 
* URL : https://github.com/ansible/django-ansible-base
* License : Apache-2.0
  Programming Lang: Python
  Description : Reusable base for Ansible applications using Django

 This Python library provides a set of classes for building
 Ansible applications using the extensible configurability of
 Django. It currently brings tools for authentication,
 filtering, validation, management commands, logging, models.
 .
 Django is a high-level Python web development framework.

This package is maintained by python team, and is a dependency of awx.

Bug#1060234: uwsgi: Please add debian/uwsgi.pydist for dh-python3 map

[Jérémy Lal]

Package: uwsgi
Version: 2.0.23-1
Severity: normal
X-Debbugs-Cc: Debian Python Team 

Hi,

A python module wanting uwsgi server would depend on "uWSGI",
but dh-python3 won't know what is the corresponding debian package name,
unless this file exists:

/usr/share/python3/dist/uwsgi.pydist

with this line in it:
uWSGI uwsgi; PEP386

it would be great if uwsgi installed that file.

Jérémy

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

Kernel: Linux 6.5.0-5-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 uwsgi depends on:
ii  sysvinit-utils [lsb-base]  3.08-5
ii  uwsgi-core 2.0.23-1

uwsgi recommends no packages.

uwsgi suggests no packages.

-- no debconf information

Bug#1004677: dh-golang: Please support skipping specific tests

[Jérémy Lal]

Package: dh-golang
Version: 1.62
Followup-For: Bug #1004677

This seems easy to do, since go1.20 it is possible to do
go test -skip 


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

Kernel: Linux 6.5.0-5-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 dh-golang depends on:
ii  debhelper 13.11.9
ii  libdpkg-perl  1.22.2
ii  perl  5.36.0-10+b1

dh-golang recommends no packages.

dh-golang suggests no packages.

-- no debconf information

Bug#1060223: receptor: Flaky tests TestCreatePing due to environment

[Jérémy Lal]

Package: receptor
Version: 1.4.3-3
Severity: important

These tests fail depending on the environment, for example
if the firewall policy is drop or reject, or perhaps depending on
how localhost resolves (ipv6 or ipv4).

--- FAIL: TestCreatePing (15.01s)
--- PASS: TestCreatePing/NetceptorShutdown_Error (2.00s)
--- FAIL: TestCreatePing/SubscribeUnreachable_Error (0.00s)
--- FAIL: TestCreatePing/CreatePing_Success (0.00s)
--- PASS: TestCreatePing/ListenPacket_Error (0.00s)
--- FAIL: TestCreatePing/ReadFrom_Error (2.00s)
--- PASS: TestCreatePing/WriteTo_Error (0.00s)
--- PASS: TestCreatePing/Timeout_Error (10.00s)
--- PASS: TestCreatePing/User_Cancel_Error (1.00s)

I'll disable them.




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

Kernel: Linux 6.5.0-5-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 receptor depends on:
ii  golang-github-creack-pty-dev  1.1.21-1
ii  golang-github-fortytw2-leaktest-dev   1.3.0-1.1
ii  golang-github-fsnotify-fsnotify-dev   1.7.0-1
ii  golang-github-ghjm-cmdline-dev0.1.2-3
ii  golang-github-golang-jwt-jwt-dev  5.0.0+really4.5.0-1
ii  golang-github-golang-mock-dev 1.6.0-2
ii  golang-github-google-shlex-dev0.0~git20191202.e7afc7f-1
ii  golang-github-gorilla-websocket-dev   1.5.1-1
ii  golang-github-lucas-clemente-quic-go-dev [golang  0.38.2-1
-github-quic-go-quic-go-dev]
ii  golang-github-minio-highwayhash-dev   1.0.2-2
ii  golang-github-pbnjay-memory-dev   0.0~git20210728.7b4eea6-2
ii  golang-github-rogpeppe-go-internal-dev1.12.0-1
ii  golang-github-songgao-water-dev   0.0~git20200317.2b4b6d7-1
ii  golang-github-vishvananda-netlink-dev 1.1.0.125.gf243826-4
ii  golang-golang-x-net-dev   1:0.19.0+dfsg-1
ii  golang-gopkg-yaml.v2-dev  2.4.0-4
ii  golang-k8s-api-dev0.29.0-1
ii  golang-k8s-apimachinery-dev   0.29.0-1
ii  golang-k8s-client-go-dev  0.29.0-1
ii  libc6 2.37-13

receptor recommends no packages.

receptor suggests no packages.

-- Configuration Files:
/etc/receptor/receptor.conf changed [not included]

Bug#1060216: ITP: python-django-solo -- Singleton objects helper for Django

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Python Team 


* Package name: python-django-solo
  Version : 2.1.0
  Upstream Contact: https://github.com/lazybird/django-solo/issues
* URL : https://github.com/lazybird/django-solo
* License : CC-BY-3.0
  Programming Lang: Python
  Description : Singleton objects helper for Django

 Solo helps to enforce instantiating only one instance of a model
 in Django. Singletons are database tables with only one row.
 .
 Django is a high-level Python web development framework.

This package will be maintained by python team, is used by awx.
Also seems to be a good django module.

Bug#1060210: ITP: python-djangorestframework-yaml -- YAML parser and renderer for Django REST Framework

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Python Team 


* Package name: python-djangorestframework-yaml
  Version : 3.0.1
  Upstream Contact: José Padilla , Xavier Francisco 

* URL : https://github.com/Qu4tro/drf-yaml
* License : BSD-3-clause
  Programming Lang: Python
  Description : YAML parser and renderer for Django REST Framework

 This library exports a parser class and a renderer for the
 Django REST Framework, allowing YAML parsing et serialization.
 .
 Django REST framework is a powerful and flexible toolkit for
 building Web APIs.

This package is maintained in python team.
It is a dependency of awx, and might also be useful for
django rest framework users.
I'm packaging the fork under the name of the original,
because the fork only did maintenance, and the original
has been inactive for four years.

Bug#1060157: librust-asn1-dev: please update to a more recent version

[Jérémy Lal]

Le dim. 7 janv. 2024 à 03:38, Peter Michael Green  a
écrit :

> a more recent version of librust-asn1-dev (>= 0.15) is needed
> to be able to update to python3-cryptography (>= 0.41) which
> in turn is required by some other package.
>
> I've uploaded the new versions of rust-asn1 and rust-asn1-derive
> to experimental,  python-cryptography seems to be the only reverse
> dependency so you should be ok to re-upload them to
> unstable at the same time as you upload the corresponding
> version of python-cryptography.
>

I don't understand how the salsa repository is managed by the rust team
(and I'm not a member anyway).
Will you update the changelog in the git repository after my two uploads ?

Bug#1060198: rust-pem: Please upgrade to 1.1.1

[Jérémy Lal]

Package: rust-pem
Version: 1.0.2
Severity: wishlist

Hi,

I'm trying to update python3-cryptography, and all tests pass except one,
because it depends on rust-pem 1.1.1, which supports parsing pem files
with headers.
It would be awesome to have at least that version in debian.

See also https://github.com/pyca/cryptography/issues/8035
and
https://github.com/jcreekmore/pem-rs/commit/83d91147

Jérémy


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

Kernel: Linux 6.5.0-5-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

Bug#1060184: ITP: python-django-guid -- Identify Django request logs

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Python Team 


* Package name: python-django-guid
  Version : 3.4.1
  Upstream Contact: Jonas Krüger Svensson 
* URL : https://github.com/snok/django-guid
* License : Expat
  Programming Lang: Python
  Description : Identify Django request logs

 This library allows one to attach a unique ID to all log outputs
 for every request, making debugging more simple.
 .
 Django is a high-level Python web development framework.

It will be maintained by python team and is a dependency of awx.

Bug#1060183: ITP: python3-django-crum -- Current request user capture middleware for Django

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Python Team 


* Package name: python3-django-crum
  Version : 0.7.9
  Upstream Contact: ch...@ninemoreminutes.com
* URL : https://github.com/ninemoreminutes/django-crum/
* License : BSD-3-clause
  Programming Lang: Python
  Description : Current request user capture middleware for Django

 This Python library enables apps to check permissions, capture
 audit trails or access the current request and user without
 requiring the request object to be passed directly.
 .
 Django is a high-level Python web development framework.

It will be maintained in Debian Python Team, and is a dependency
of awx.

Bug#1060168: ITP: python-json-log-formatter -- JSON formatter logging for Python

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Python Team 


* Package name: python-json-log-formatter
  Version : 0.5.2
  Upstream Contact: https://github.com/marselester/json-log-formatter/issues/new
* URL : https://github.com/marselester/json-log-formatter
* License : Expat
  Programming Lang: Python
  Description : JSON formatter logging for Python

 This library allows one to configure Python logging to
 use a JSON formatter.

This library will be under Debian Python Team 
maintenance, and is a dependency of awx.

Bug#1060157: librust-asn1-dev: please update to a more recent version

[Jérémy Lal]

Package: librust-asn1-dev
Version: 0.12.2
Severity: wishlist

Hi,

a more recent version of librust-asn1-dev (>= 0.15) is needed
to be able to update to python3-cryptography (>= 0.41) which
in turn is required by some other package.


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

Kernel: Linux 6.5.0-5-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

Bug#1060068: ITP: python3-asn1 -- Simple ASN.1 encoder and decoder for Python

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Python Team 


* Package name: python3-asn1
  Version : 2.7.0
  Upstream Contact: Sebastien Andrivet 
* URL : https://github.com/andrivet/python-asn1
* License : Expat
  Programming Lang: Python
  Description : Simple ASN.1 encoder and decoder for Python

 This pure Python library features:
 * a BER decoder
 * a DER decoder and encoder (except indefinite lengths)

This package has still an active upstream (contrary to pyasn1),
and is a dependency of awx.
Its maintenance will be done inside python-team.

Bug#1059860: ITP: golang-github-quic-go-quic-go -- A QUIC implementation in pure go

[Jérémy Lal]

Le mar. 2 janv. 2024 à 16:06, Jérémy Lal  a écrit :

>
>
> Le mar. 2 janv. 2024 à 15:27, Félix Sipma  a écrit :
>
>> Package: wnpp
>> Severity: wishlist
>> Owner: Félix Sipma 
>>
>> * Package name: golang-github-quic-go-quic-go
>>   Version : 0.40.0-1
>>   Upstream Author :
>> * URL : https://github.com/quic-go/quic-go
>> * License : Expat
>>   Programming Lang: Go
>>   Description : A QUIC implementation in pure go
>>
>>  A QUIC implementation in pure Go
>
>
> Already in debian.
> The upgrade will require more work, though.
>

Someone needs to deal with
https://github.com/golang/mock
being superseded by
https://github.com/uber-go/mock

Not sure of the right approach, asked on debian-go@lists.d.o

Bug#1059860: ITP: golang-github-quic-go-quic-go -- A QUIC implementation in pure go

[Jérémy Lal]

Le mar. 2 janv. 2024 à 15:27, Félix Sipma  a écrit :

> Package: wnpp
> Severity: wishlist
> Owner: Félix Sipma 
>
> * Package name: golang-github-quic-go-quic-go
>   Version : 0.40.0-1
>   Upstream Author :
> * URL : https://github.com/quic-go/quic-go
> * License : Expat
>   Programming Lang: Go
>   Description : A QUIC implementation in pure go
>
>  A QUIC implementation in pure Go


Already in debian.
The upgrade will require more work, though.

Bug#1059789: golang-github-google-gnostic-models-dev: Should depend on golang-github-golang-protobuf-1-5-dev

[Jérémy Lal]

Package: golang-github-google-gnostic-models-dev
Followup-For: Bug #1059789

Actually other packages depend on
golang-github-golang-protobuf-1-3-dev | golang-github-golang-protobuf-1-5-dev

which is the correct fix.

I will upload that fix.


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

Kernel: Linux 6.5.0-5-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 golang-github-google-gnostic-models-dev depends on:
ii  golang-github-golang-protobuf-1-5-dev  1.5.3-1
ii  golang-google-protobuf-dev 1.32.0-1
ii  golang-gopkg-check.v1-dev  0.0+git20200902.038fdea-1
ii  golang-gopkg-yaml.v3-dev   3.0.1-3

golang-github-google-gnostic-models-dev recommends no packages.

golang-github-google-gnostic-models-dev suggests no packages.

-- no debconf information

Bug#1059789: golang-github-google-gnostic-models-dev: Should depend on golang-github-golang-protobuf-1-5-dev

[Jérémy Lal]

Package: golang-github-google-gnostic-models-dev
Version: 0.6.8-2
Severity: important

Hi,

this new package has a dependency on golang-goprotobuf-dev, which
installs the old API through golang-github-golang-protobuf-1-3-dev;
however, other new packages depending on gnostic-models like k8s-client-go
do depend on golang-github-golang-protobuf-1-5-dev, which is the
new v2 API.
Since both packages (1-3 and 1-5) cannot be installed simultaneously,
it is a better choice to make gnostic-models depend on the new protobuf API
and not the old one.


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

Kernel: Linux 6.5.0-5-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 golang-github-google-gnostic-models-dev depends on:
ii  golang-google-protobuf-dev  1.32.0-1
ii  golang-gopkg-check.v1-dev   0.0+git20200902.038fdea-1
ii  golang-gopkg-yaml.v3-dev3.0.1-3
pn  golang-goprotobuf-dev   

golang-github-google-gnostic-models-dev recommends no packages.

golang-github-google-gnostic-models-dev suggests no packages.

-- no debconf information

Bug#1059762: ITP: golang-k8s-api -- Schema for Kubernetes server external API types

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 

* Package name: golang-k8s-api
  Version : 0.29.0
  Upstream Author : Kubernetes
* URL : https://github.com/kubernetes/api
* License : Apache-2.0
  Programming Lang: Go
  Description : Schema for Kubernetes server external API types

 This library primary consumer is k8s.io/client-go, and is published
 separately to avoid diamond dependency problems for users who depend on
 more than one of k8s.io/client-go, k8s.io/apimachinery, k8s.io/apiserver.
 .
 Kubernetes is a system for managing containerized applications across
 multiple hosts.

This package is go-team maintained and is needed by kubernetes, receptor.

Bug#1012720: ITP: golang-k8s-apimachinery -- Handle Kubernetes-like API objects

[Jérémy Lal]

Le dim. 31 déc. 2023 à 14:05, Nicolas Schier  a écrit :

> On Sat 30 Dec 2023 13:32:44 GMT, Jérémy Lal wrote:
> > Hi,
> >
> > is there any advance on
> > https://salsa.debian.org/go-team/packages/golang-k8s-apimachinery.git
> > ?
> >
> > I could help with it.
>
> thanks.  It seems to me that you took over already :)
>

Yes, I'm using some free time to do that.


> My latest version is at
> https://salsa.debian.org/nsc/golang-k8s-apimachinery/
> but your latest push to the official salsa repo looks better.
>
> Since the successful ITP of golang-github-google-gnostic-models, only
> an updated version of golang-github-kubernetes-gengo should be missing.


I updated some of the dependencies already (gengo included).
I will move on to k8s-client-go and k8s-api.

Jérémy

Bug#1059733: ITP: golang-k8s-client-go -- Go client for Kubernetes

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Go Packaging Team 


* Package name: golang-k8s-client-go
  Version : 0.29.0
  Upstream Contact: https://github.com/kubernetes/client-go/issues
* URL : https://github.com/kubernetes/client-go
* License : Apache-2.0
  Programming Lang: Golang
  Description : Go client for Kubernetes

 Go clients for talking to a kubernetes cluster.
  * The kubernetes package contains the clientset to access Kubernetes
API.
  * The discovery package is used to discover APIs supported by a
Kubernetes API server.
  * The dynamic package contains a dynamic client that can perform
generic operations on arbitrary Kubernetes API objects.
  * The plugin/pkg/client/auth packages contain optional authentication
plugins for obtaining credentials from external sources.
  * The transport package is used to set up auth and start a connection.
  * The tools/cache package is useful for writing controllers.

This package will be published in go-team.

It is needed by kubernetes, and other projects like receptor, which is a 
controller for awx.

Bug#1012720: ITP: golang-k8s-apimachinery -- Handle Kubernetes-like API objects

[Jérémy Lal]

Package: wnpp
Followup-For: Bug #1012720


Hi,

is there any advance on
https://salsa.debian.org/go-team/packages/golang-k8s-apimachinery.git
?

I could help with it.

Bug#1039990: [Pkg-javascript-devel] Bug#1039990: nodejs: CVE-2023-30581 CVE-2023-30588 CVE-2023-30589 CVE-2023-30590

[Jérémy Lal]

Le mer. 27 déc. 2023 à 17:16, Moritz Mühlenhoff  a écrit :

> [ Also adding Paul Gevers for awareness, for context we're bumping nodejs
>   in Bookworm to the latest 18.x security/LTS release ]
>
> On Wed, Dec 27, 2023 at 03:03:20PM +0100 Jérémy Lal wrote:
>
> > I don't think so, there are all either node-undici-related, or just test
> > suites regressions.
> > Here are the details:
> >
> > node-zx is a regression in the test suite only, fixed there:
> >
> https://salsa.debian.org/js-team/node-zx/-/commit/a7d2861413480261890db147ea367a252192c9f2
> >
> > node-yaml is caused by missing node-undici
> >
> > node-v8-compile-cache is a regression in the test suite only, fixed
> there:
> >
> https://salsa.debian.org/js-team/node-v8-compile-cache/-/commit/df42bdbfe84811e4da11d8c3d8ef3148d8a77bcc
> >
> > node-babel7 is a regression in the test suite, fixed there:
> >
> https://salsa.debian.org/js-team/node-babel/-/commit/e5c88f4d765e4d64b60c9cf333dedb89abba39c5
> >
> > node-re2 is caused by missing node-undici
>
> Great, thanks for the detailed analysis!
>
> This means the update to .19 will regress autopkgtests for node-zx,
> node-v8-compile-cache
> and node-babel7, but since these are all only test suite regressions, we
> can just go
> ahead and fix the tests in a subsequent bookworm point update, ok?
>

Ok, so I suppose js-team would need to upload those three packages to t-p-u
?

Bug#1039990: [Pkg-javascript-devel] Bug#1039990: nodejs: CVE-2023-30581 CVE-2023-30588 CVE-2023-30589 CVE-2023-30590

[Jérémy Lal]

Le mer. 27 déc. 2023 à 14:43, Moritz Mühlenhoff  a écrit :

> Am Thu, Dec 21, 2023 at 11:26:27PM +0100 schrieb Jérémy Lal:
> > Le jeu. 21 déc. 2023 à 20:34, Moritz Mühlenhoff  a
> écrit :
> >
> > > Am Thu, Dec 21, 2023 at 11:29:12AM +0100 schrieb Jérémy Lal:
> > > > Le jeu. 21 déc. 2023 à 10:54, Moritz Muehlenhoff  a
> > > écrit :
> > > >
> > > > > On Thu, Dec 21, 2023 at 06:43:35AM +0100, Salvatore Bonaccorso
> wrote:
> > > > > > Hi,
> > > > > >
> > > > > > [CC'ing node-undici uploader]
> > > > >
> > > >
> > > > [CC-ing the good email address for node-undici uploader]
> > > >
> > > > Attached is a debdiff for a node-undici update (which backports what
> has
> > > > been done in testing).
> > >
> > > Looks good to me, please build with -sa (since it's the first upload
> > > to bookworm-security) and upload to security-master.
> > >
> >
> > Note that nodejs 18.19.0 doesn't need this node-undici version to be
> built,
> > only typescript consumers need it (when rebuilding packages in bookworm,
> > or when simply using a typescript compiler in bookworm).
>
> I checked the autopkgtest results for 18.19 on bookworm (it's running
> on security-master and isn't public at this point) and there are
> five packages marked as regressing, for which I'm attaching the logs.
>
> Two have explicit references to the node-undici (but since the new
> node-undici isn't installed into the archive yet, these will only
> recover when it's out).
>
> Could you please do a quick pass over these if the other three are also
> related or whether we potentially also need to update other packages
> in bookworm?


I don't think so, there are all either node-undici-related, or just test
suites regressions.
Here are the details:

node-zx is a regression in the test suite only, fixed there:
https://salsa.debian.org/js-team/node-zx/-/commit/a7d2861413480261890db147ea367a252192c9f2

node-yaml is caused by missing node-undici

node-v8-compile-cache is a regression in the test suite only, fixed there:
https://salsa.debian.org/js-team/node-v8-compile-cache/-/commit/df42bdbfe84811e4da11d8c3d8ef3148d8a77bcc

node-babel7 is a regression in the test suite, fixed there:
https://salsa.debian.org/js-team/node-babel/-/commit/e5c88f4d765e4d64b60c9cf333dedb89abba39c5

node-re2 is caused by missing node-undici

Jérémy

Bug#1027779: ITP: receptor -- Link controllers with executors across a mesh of nodes

[Jérémy Lal]

Package: wnpp
Followup-For: Bug #1027779

ITP for golang-github-songgao-water: #1059399

Bug#1059399: ITP: golang-github-songgao-water -- A simple TUN/TAP library written in native Go.

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 

* Package name: golang-github-songgao-water
  Version : 0.0~git20200317.2b4b6d7-1
  Upstream Author : Song Gao
* URL : https://github.com/songgao/water
* License : BSD-3-clause
  Programming Lang: Go
  Description : Simple TUN/TAP library for Go language

 This library is designed to be simple and efficient. It
 .
  * wraps almost only syscalls and uses only Go standard types;
  * exposes standard interfaces; plays well with standard packages like
io, bufio, etc..
  * does not handle memory management (allocating/destructing slice).
It's up to user to decide whether/how to reuse buffers.
  * has partial support for MacOS or Windows

This package will be go-team maintained, and seems to be pretty popular.
This is a build-dependency for receptor, a meshed network daemon needed by awx.

Bug#1027779: ITP: receptor -- Link controllers with executors across a mesh of nodes

[Jérémy Lal]

Package: wnpp
Followup-For: Bug #1027779

Missing dependencies that I might bundle in a multiple upstream tarball,
because they look so specific:

- golang-github-prep-socketpair-dev
- golang-github-jupp0r-go-priority-queue-dev

Missing, needs to be packaged, some are already being worked on:

- golang-github-songgao-water (#inprocess)
- golang-github-k8s-io-api-dev
- golang-github-k8s-io-apimachinery-dev (#1012720)
- golang-github-k8s-io-client-go-dev

The k8s ones are missing golang-github-google-gnostic-models-dev,
which is in NEW, #1053000.

Bug#958682: [Pkg-javascript-devel] Bug#958682: node-jsonld: Remove dependency to node-request

[Jérémy Lal]

Le sam. 23 déc. 2023 à 20:15, Jonas Smedegaard  a écrit :

> Quoting Pirate Praveen (2023-12-22 20:53:46)
> > On Sun, 29 Oct 2023 21:37:08 +0100 Jonas Smedegaard  wrote:
> > > Yes, I still want to work on node-jsonld - I will make time to look at
> > > this soon...
> >
> > yarnpkg 4.0.2 was recently uploaded to unstable, so this and
> > node-matrix-js-sdk are the only remaining reverse dependencies for
> > node-request. We have an ack from its maintainer to remove it
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958692#42 so this is
> > the only real blocker remaining to remove node-request.
>
> You gave a second warning.  Only 24 hours but I guess I should be
> thankful.


Hi Jonas,

Is there some humor in this tone ?
This bug has been opened more than three years ago, and it's starting to
look as if you wanted to block it.

Jérémy

Bug#1039990: [Pkg-javascript-devel] Bug#1039990: Bug#1039990: nodejs: CVE-2023-30581 CVE-2023-30588 CVE-2023-30589 CVE-2023-30590

[Jérémy Lal]

Le jeu. 21 déc. 2023 à 23:30, Jérémy Lal  a écrit :

>
>
> Le jeu. 21 déc. 2023 à 20:34, Moritz Mühlenhoff  a écrit :
>
>> Am Thu, Dec 21, 2023 at 11:29:12AM +0100 schrieb Jérémy Lal:
>> > Le jeu. 21 déc. 2023 à 10:54, Moritz Muehlenhoff  a
>> écrit :
>> >
>> > > On Thu, Dec 21, 2023 at 06:43:35AM +0100, Salvatore Bonaccorso wrote:
>> > > > Hi,
>> > > >
>> > > > [CC'ing node-undici uploader]
>> > >
>> >
>> > [CC-ing the good email address for node-undici uploader]
>> >
>> > Attached is a debdiff for a node-undici update (which backports what has
>> > been done in testing).
>>
>> Looks good to me, please build with -sa (since it's the first upload
>> to bookworm-security) and upload to security-master.
>>
>
> Note that nodejs 18.19.0 doesn't need this node-undici version to be built,
> only typescript consumers need it (when rebuilding packages in bookworm,
> or when simply using a typescript compiler in bookworm).
>

nodejs (18.19.0+dfsg-6~deb11u1) is ready and built with -sa.

Jérémy

Bug#1039990: [Pkg-javascript-devel] Bug#1039990: nodejs: CVE-2023-30581 CVE-2023-30588 CVE-2023-30589 CVE-2023-30590

[Jérémy Lal]

Le jeu. 21 déc. 2023 à 20:34, Moritz Mühlenhoff  a écrit :

> Am Thu, Dec 21, 2023 at 11:29:12AM +0100 schrieb Jérémy Lal:
> > Le jeu. 21 déc. 2023 à 10:54, Moritz Muehlenhoff  a
> écrit :
> >
> > > On Thu, Dec 21, 2023 at 06:43:35AM +0100, Salvatore Bonaccorso wrote:
> > > > Hi,
> > > >
> > > > [CC'ing node-undici uploader]
> > >
> >
> > [CC-ing the good email address for node-undici uploader]
> >
> > Attached is a debdiff for a node-undici update (which backports what has
> > been done in testing).
>
> Looks good to me, please build with -sa (since it's the first upload
> to bookworm-security) and upload to security-master.
>

Note that nodejs 18.19.0 doesn't need this node-undici version to be built,
only typescript consumers need it (when rebuilding packages in bookworm,
or when simply using a typescript compiler in bookworm).

Jérémy

Bug#1039990: [Pkg-javascript-devel] Bug#1039990: nodejs: CVE-2023-30581 CVE-2023-30588 CVE-2023-30589 CVE-2023-30590

[Jérémy Lal]

Le jeu. 21 déc. 2023 à 10:54, Moritz Muehlenhoff  a écrit :

> On Thu, Dec 21, 2023 at 06:43:35AM +0100, Salvatore Bonaccorso wrote:
> > Hi,
> >
> > [CC'ing node-undici uploader]
>

[CC-ing the good email address for node-undici uploader]


> > > >> Ack, let's do that. Could you prepare bookworm-security updates
> > > >> based on 18.17.0 (after it has landed in unstable)?
> > > >
> > > nodejs 18.19.0 has landed in testing.
> > > It rebuilds fine in bookworm, and test-suite-during-build pass on
> amd64.
> > >
> > > It also requires "node-undici", precisely for that change:
> > >
> > > node-undici (5.28.2+dfsg1+~cs23.11.12.3-2) unstable; urgency=medium
> > >
> > >   * Build and publish undici-types, needed by new @types/node
> > >
> > > Is there a way to deal with this ?
> >
> > Then I guess we need this as pre-requisite upload to bookworm as well.
> >
> > Maybe Moritz has a better idea, but one option is to propose this
> > update regularly as bookworm-pu and once it's in proposed update ask
> > DSA to make the security chroots pick as well updates from
> > prpopsoed-updates if we plan to release nodejs via a DSA (or otherwise
> > via bookworm-pu as well).
> >
> > One other alternative is to make a non-security upload for
> > node-unidici containing that change to the security archive, which the
> > nodejs update can pick.
>
> I think we can handle it similar to what we recently did when OpenJDK
> bumped
> it's requirement for jtreg: When we have a suitable update for node-undici
>

Attached is a debdiff for a node-undici update (which backports what has
been done in testing).




> we upload it to security-master and the security buildds will be able to
> use it to build the new nodejs. And then it simply gets released along with
> the nodejs update.
>
> Cheers,
> Moritz
>


node-undici-deb12u2-to-deb12u3.debdiff
Description: Binary data

Bug#1059165: [Pkg-javascript-devel] Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

[Jérémy Lal]

Le jeu. 21 déc. 2023 à 08:59, Paul Gevers  a écrit :

> Hi,
>
> On 20-12-2023 23:08, Jérémy Lal wrote:
> > I did the one for burp.
>
> Thanks for that.
>
> > Dolfin has active maintainers, though.
>
> I think I need to file a "flaky autopkgtest" bug report against dolfin.


Thank you for https://bugs.debian.org/1059168

I noticed "Marked as found in versions nodejs/18.19.0+dfsg-6 and reopened."
while the test is flaky, retrying it will make it pass, so the bug is not
as important as it seems.
And indeed, https://tracker.debian.org/pkg/zlib is no longer blocked by
nodejs.

Jérémy

Bug#1059165: [Pkg-javascript-devel] Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

[Jérémy Lal]

Le mer. 20 déc. 2023 à 22:33, Mark Brown  a écrit :

> On Wed, Dec 20, 2023 at 10:14:44PM +0100, Jérémy Lal wrote:
>
> > BURP wrong zlib version check in the failing test - this could be NMUed
>
> > DOLFIN has a single test failure, that is odd and unrelated as well -
> this
> > could be NMUed
>
> For non-technical reasons I can't do these NMUs myself if they're
> warranted/needed.
>

I did the one for burp.
Dolfin has active maintainers, though.

Jérémy

Bug#1059165: [Pkg-javascript-devel] Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

[Jérémy Lal]

Le mer. 20 déc. 2023 à 21:18, Mark Brown  a écrit :

> clone 1059165 -1
> reassign -1 nodejs
> retitle -1 autopkgtest failures on i386
> found -1 18.19.0+dfsg-6
> block 1059165 by -1
> kthxbye
>
> On Wed, Dec 20, 2023 at 08:15:31PM +0100, Paul Gevers wrote:
>
> > The Release Team considers packages that are out-of-sync between testing
> and
> > unstable for more than 30 days as having a Release Critical bug in
> testing
> > [1]. Your package src:zlib has been trying to migrate for 32 days [2].
> > Hence, I am filing this bug. The version in unstable triggers autopkgtest
> > failures in multiple packages (although I suspect that the current dolfin
> > issues are due to it being flaky). The failure for burp has already a bug
> > report against that package, which leaves nodejs on i386.
>
> ...
>
> > This bug will trigger auto-removal when appropriate. As with all new
> bugs,
> > there will be at least 30 days before the package is auto-removed.
>
> Not sure that's likely in the case of zlib?
>
> > If you believe your package is unable to migrate to testing due to issues
> > beyond your control, don't hesitate to contact the Release Team.
>
> There are non-technical issues with me doing active work on nodejs
> package but from a quick glance the log does not seem particularly
> plausibly related to zlib, and I note that the failures are
>
>not ok 498 parallel/test-debugger-heap-profiler
>not ok 962 parallel/test-fs-utimes-y2K38 # TODO : Fix flaky test
>
> the second of which especially doesn't inspire confidence that this is
> due to zlib rather than general updates to unstable setting off an
> already flaky test (eg, the kernel changed timing?).  Full log is:
>
>https://ci.debian.net/packages/n/nodejs/testing/i386/41176091/
>
> and looking at:
>
>https://ci.debian.net/packages/n/nodejs/testing/i386/
>
> there seem to be a number of packages triggering what from spot checks
> look to be the same or similar issues in nodejs in testing.
>
> I frankly don't really know what I'm supposed to do with this, the test
> results look like noise as far as zlib is concerned so I don't see
> anything to fix or investigate in the package itself.  AFAICT bugs don't
> get filed for autopkgtest failures like they do for build failures so
> perhaps this was just missed up until now?


NODEJS will probably pass with a retry request
The only test that failed here was parallel/test-debugger-heap-profiler
and it doesn't depend on zlib. It is somewhat flaky but usually not on i386.
I sent a retry request for nodejs/i386 testing to debci. There is a good
chance it'll pass this time.
Meanwhile, next nodejs upload will mark that test as flaky on all platforms.

BURP wrong zlib version check in the failing test - this could be NMUed
./test-suite.log
99%: Checks: 252, Failures: 1, Errors: 0
utest/test_fzp.c:95:F:Core:test_fzp_gzseek:0: Assertion 'fzp_seek(fzp,
d->pos, SEEK_SET)==-1' failed
It fails because the condition is still fulfilled, but it shouldn't be:
  START_TEST(test_fzp_gzseek)
  {
if(version_to_long(ZLIB_VERSION) <= version_to_long("1.2.3"))
  fzp_gzopen_old_zlib_seek_hack=1;
do_seek_tests(fzp_gzopen);
  }
END_TEST

DOLFIN has a single test failure, that is odd and unrelated as well - this
could be NMUed
224s with Timer(task) as t:
4608 
5224s sleep(0.05)
4609 
5224s > assert t.elapsed()[0] >= 0.05
4610 
5224s E assert 0.04 >= 0.05

Jérémy

Bug#1039990: [Pkg-javascript-devel] Bug#1039990: nodejs: CVE-2023-30581 CVE-2023-30588 CVE-2023-30589 CVE-2023-30590

[Jérémy Lal]

Le mer. 19 juil. 2023 à 21:51, Jérémy Lal  a écrit :

>
>
> Le mer. 19 juil. 2023 à 14:18, Moritz Mühlenhoff  a
> écrit :
>
>> Am Fri, Jun 30, 2023 at 08:12:37PM +0200 schrieb Jérémy Lal:
>> > Hi,
>> >
>> > Le ven. 30 juin 2023 à 19:21, Salvatore Bonaccorso 
>> a
>> > écrit :
>> >
>> > > Source: nodejs
>> > > Version: 18.13.0+dfsg1-1
>> > > Severity: important
>> > > Tags: security upstream
>> > > X-Debbugs-Cc: car...@debian.org, Debian Security Team <
>> > > t...@security.debian.org>
>> > >
>> > > Hi,
>> > >
>> > > The following vulnerabilities were published for nodejs.
>> > >
>> > > CVE-2023-30581[0], CVE-2023-30588[1], CVE-2023-30589[2] and
>> > > CVE-2023-30590[3].
>> > >
>> > >
>> > > If you fix the vulnerabilities please also make sure to include the
>> > > CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
>> > >
>> >
>> > It would be interesting to know if we adopt the same plan we had with
>> > security team:
>> > full upstream updates in the same branch, 18.x here.
>>
>> Ack, let's do that. Could you prepare bookworm-security updates
>> based on 18.17.0 (after it has landed in unstable)?
>
>
nodejs 18.19.0 has landed in testing.
It rebuilds fine in bookworm, and test-suite-during-build pass on amd64.

It also requires "node-undici", precisely for that change:

node-undici (5.28.2+dfsg1+~cs23.11.12.3-2) unstable; urgency=medium

  * Build and publish undici-types, needed by new @types/node

Is there a way to deal with this ?

Jérémy

Bug#1058807: ITP: acme.sh -- Pure unix shell script implementing ACME client protocol

[Jérémy Lal]

Le dim. 17 déc. 2023 à 07:04, Andreas Metzler  a écrit :

> On 2023-12-16 Jérémy Lal  wrote:
> [...]
> > * Package name: acme.sh
> >   Version : 3.0.7
> >   Upstream Contact: w...@neilpang.com
> > * URL : https://acme.sh
> > * License : GPL-3
> >   Programming Lang: Shell
> >   Description : Pure unix shell script implementing ACME client
> protocol
> [...]
> > This acme.sh tool is a must-have for everyone who stumbled upon
> > certbot shotcomings. It is odd that it isn't already in debian.
>
> Good, morning,
>
> letsencrypt.org lists 6 bash-implementations of the acme protocol, I do
> not think it is surprising that not all of them are packaged
> (letsencrypt.sh/dehydrated has been available in Debian forever).
>
> Not trying to discourage you from packaging, at a first glance acme.sh
> seems to be very much alive project.


I'm still pondering if this was a good idea.
Acme.sh works pretty well and has great, out of the box, deployment
capabilities,
and minimal dependencies but the source code is not easy to understand, so
long-term
maintenance will be difficult.

Bug#1058807: ITP: acme.sh -- Pure unix shell script implementing ACME client protocol

[Jérémy Lal]

Le sam. 16 déc. 2023 à 20:42, Jérémy Lal  a écrit :

> Package: wnpp
> Severity: wishlist
> Owner: Jérémy Lal 
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: acme.sh
>   Version : 3.0.7
>   Upstream Contact: w...@neilpang.com
> * URL : https://acme.sh
> * License : GPL-3
>   Programming Lang: Shell
>   Description : Pure unix shell script implementing ACME client
> protocol
>
>  The acme.sh executable has minimal dependencies and maximal features:
>  - full ACME protocol implementation
>  - ECDSA certificates support
>  - SAN and wildcard certificates with many DNS providers support
>  - issue then renew and deploy automatically
>  - does not require privileged user
>
> This acme.sh tool is a must-have for everyone who stumbled upon
> certbot shotcomings. It is odd that it isn't already in debian.
>

Well maybe because there is lego.

Bug#1058807: ITP: acme.sh -- Pure unix shell script implementing ACME client protocol

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: acme.sh
  Version : 3.0.7
  Upstream Contact: w...@neilpang.com
* URL : https://acme.sh
* License : GPL-3
  Programming Lang: Shell
  Description : Pure unix shell script implementing ACME client protocol

 The acme.sh executable has minimal dependencies and maximal features:
 - full ACME protocol implementation
 - ECDSA certificates support
 - SAN and wildcard certificates with many DNS providers support
 - issue then renew and deploy automatically
 - does not require privileged user

This acme.sh tool is a must-have for everyone who stumbled upon
certbot shotcomings. It is odd that it isn't already in debian.

Bug#1057697: nodejs:please enable loong64

[Jérémy Lal]

Le sam. 9 déc. 2023 à 16:27, Bo YU  a écrit :

> Source: nodejs
> Followup-For: Bug #1057697
> Version: 18.19.0+dfsg-6
> Tags: patch
>
> >>It seems we need to merge the patch[0] from #1054259 to finish the first
> >>stage for bootstraping nodejs on any arches if based on 18.19.0.
>
> >>From my side it's like this.
>
> >Right, I overlooked those patches - because I only read the first one,
> which was very wrong.
> >The actual fixes those patches were proposing are now applied.
>
> >However now I'm a bit worried that this is all in vain, because nodejs
> unconditionally requires cjs-module-lexer,
> >so one cannot execute anything without it (that wasn't the case when only
> acorn was an external builtin).
> ^
> (Copied txt from #1054259)
>
> To be honest, I do not understand the first patch from #1054259.
> Based on past bootstrap riscv64 experiences, I easily bootstrap nodejs
> for loong64 following the debian/README.source.
>
> Just for your convenience, I attach the debdiff for bootstrap nodejs for
> loong64 after finishing the first stage bootstrap.


Good news, the first stage build now works pretty well,
meaning it produces a nodejs binary that can be useful.
It even pass most of its testsuite, except of course everything that needs
- the command line repl (acorn)
- fetch (undici)
- commonjs modules (cjs-module-lexer)

It is on current master-18.x branch, and i double-checked it builds fine.

Jérémy

Bug#1054259: Bug#1057697: nodejs:please enable loong64

[Jérémy Lal]

Le sam. 9 déc. 2023 à 04:12, Bo YU  a écrit :

> Source: nodejs
> Followup-For: Bug #1057697
>
> It seems we need to merge the patch[0] from #1054259 to finish the first
> stage for bootstraping nodejs on any arches if based on 18.19.0.
>
> From my side it's like this.
>
> [0]:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=3;bug=1054259;filename=0004-HACK-bootstrap-Don-t-attempt-to-install-node_builtin.patch;msg=15


Right, I overlooked those patches - because I only read the first one,
which was very wrong.
The actual fixes those patches were proposing are now applied.

However now I'm a bit worried that this is all in vain, because nodejs
unconditionally requires cjs-module-lexer,
so one cannot execute anything without it (that wasn't the case when only
acorn was an external builtin).

Jérémy

Bug#1057697: [Pkg-javascript-devel] Bug#1057697: Bug#1057697: nodejs:please enable loong64

[Jérémy Lal]

Le jeu. 7 déc. 2023 à 12:27, Jérémy Lal  a écrit :

> Le jeu. 7 déc. 2023 à 09:54, Shi Pujin  a écrit :
>
>> On Thu, 7 Dec 2023 08:30:09 +0800 Shi Pujin  wrote:
>>  > Package: nodejs
>>  > Version: 18.19.0
>>  > Severity: wishlist
>>  > Tags: patch
>>  > User: debian-loonga...@lists.debian.org
>>  > X-Debbugs-Cc: shipu...@loongson.cn
>>  > Usertags: loong64
>>  >
>>  > Hi,
>>  >
>>  > Nodejs upstream supports loong64 starting from nodejs-17.5.0 version,
>>  >
>>  > it'd be nice to have loong64 enabled，nodejs is in the Build-Depend
>> chain
>>  > for many packages.
>>
>
> Thanks, applied to
> https://salsa.debian.org/js-team/nodejs/-/commits/master-18.x
>
> Will be uploaded after current unstable nodejs has moved to testing.
>
>
>>  > I test compile nodejs locally, ignoring the build dependency
>>  > he(--no-check-builddeps), close the test phase,debian-nodejs was
>>  > successfully compiled.
>>  >
>>  > ```
>>  > debootstrap --no-check-gpg --arch=loong64 --variant=buildd
>>  > --extra-suites=unreleased unstable sid-loong64-rootfs
>>  > http://ftp.ports.debian.org/debian-ports
>
>
> The "correct" way to build nodejs on a new arch is documented in
>
> https://salsa.debian.org/js-team/nodejs/-/blob/master-18.x/debian/README.source
>


Also if you can give me access to a loong64 porterbox, I'll do that step
for you.

Bug#1057707: [Pkg-javascript-devel] Bug#1057707: eslint is incompatible with node-ajv >= 8

[Jérémy Lal]

Le jeu. 7 déc. 2023 à 12:45, Yadd  a écrit :

> Package: eslint
> Version: 6.4.0~dfsg+~6.1.9-7
> Severity: important
> Tags: ftbfs upstream
>
> Hi,
>
> eslint depends on node-ajv 6 and is incompatible with node-ajv 8
> (available in exeprimental branch). All is in lib/shared/ajv.js:
>
>  - eslint requires 'ajv/lib/refs/json-schema-draft-04.json' which is no
>more available
>  - eslint tries to set `ajv._opts.defaultMeta` which is
>`ajv.opts.defaultMeta` in node-ajv 8.
>
> Changing "ajv/lib/refs/json-schema-draft-04.json" to
> "ajv/lib/refs/json-schema-draft-06.json" doesn't work. I tried this
> patch which looks to work but 27 tests fail (not the good error string).
> It uses default ajv schemas.
>
> Help needed here ;-)


I suppose you tried
https://github.com/eslint/eslint/pull/13911/commits
?

Bug#1057697: [Pkg-javascript-devel] Bug#1057697: nodejs:please enable loong64

[Jérémy Lal]

Le jeu. 7 déc. 2023 à 09:54, Shi Pujin  a écrit :

> On Thu, 7 Dec 2023 08:30:09 +0800 Shi Pujin  wrote:
>  > Package: nodejs
>  > Version: 18.19.0
>  > Severity: wishlist
>  > Tags: patch
>  > User: debian-loonga...@lists.debian.org
>  > X-Debbugs-Cc: shipu...@loongson.cn
>  > Usertags: loong64
>  >
>  > Hi,
>  >
>  > Nodejs upstream supports loong64 starting from nodejs-17.5.0 version,
>  >
>  > it'd be nice to have loong64 enabled，nodejs is in the Build-Depend
> chain
>  > for many packages.
>

Thanks, applied to
https://salsa.debian.org/js-team/nodejs/-/commits/master-18.x

Will be uploaded after current unstable nodejs has moved to testing.


>  > I test compile nodejs locally, ignoring the build dependency
>  > he(--no-check-builddeps), close the test phase,debian-nodejs was
>  > successfully compiled.
>  >
>  > ```
>  > debootstrap --no-check-gpg --arch=loong64 --variant=buildd
>  > --extra-suites=unreleased unstable sid-loong64-rootfs
>  > http://ftp.ports.debian.org/debian-ports


The "correct" way to build nodejs on a new arch is documented in
https://salsa.debian.org/js-team/nodejs/-/blob/master-18.x/debian/README.source

Jérémy

Bug#1057616: ITP: golang-github-jupp0r-go-priority-queue -- A priority queue implementation on top of container/heap

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 

* Package name: golang-github-jupp0r-go-priority-queue
  Version : 0.0~git20160601.ab10738-1
  Upstream Author : Jupp Mueller
* URL : https://github.com/jupp0r/go-priority-queue
* License : Expat
  Programming Lang: Go
  Description :  A priority queue on top of container/heap for Go
 Besides regular operations, it allows updating items priority,
 allowing the queue to be used in graph search algorithms like
 Dijkstra's algorithm.

This package is a dependency of receptor, which is a go binary needed by awx.

Bug#1057415: ITP: golang-github-ghjm-cmdline -- Command line parser with multiple configurations for the Go language

[Jérémy Lal]

Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Go Packaging Team 


* Package name: golang-github-ghjm-cmdline
  Version : 0.1.2
  Upstream Contact: Graham Mainwaring
* URL : https://github.com/ghjm/cmdline
* License : Apache-2.0
  Programming Lang: Golang
  Description : Command line parser with multiple configurations for the Go 
language

 This package provides a parsing and execution framework based on
 the idea that structs define accepted fields, receiver functions,
 and execution phases.
 It is more general than the common Go language command line parser.

This is needed by receptor, a cli needed by awx.
I plan to team-maintain it within pkg-go team.

Jérémy

Bug#1057143: node-acorn: nodejs 18.19.0 seems to be expecting node-acorn 8.10.0

[Jérémy Lal]

Package: node-acorn
Version: 8.8.1+ds+~cs25.17.7-2
Severity: wishlist

Hi,

at the moment it seems there is no strong motivation for upgrading,
however, the fact nodejs expects acorn 8.10.0 means it will probably
use new features, if any.

So, no rush, but probably needed anytime soon.

Jérémy


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

Kernel: Linux 6.5.0-4-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 node-acorn depends on:
ii  node-xtend  4.0.2-3
ii  nodejs  18.14.2+dfsg-1

node-acorn recommends no packages.

node-acorn suggests no packages.

-- no debconf information

Bug#1054259: [Pkg-javascript-devel] Bug#1054259: nodejs: cannot bootstrap nodejs

[Jérémy Lal]

Le ven. 20 oct. 2023 à 10:33, Christopher Obbard 
a écrit :

> Control: retitle -1 nodejs: cannot bootstrap nodejs
>
> Hi Jérémy,
>
> On Fri, 2023-10-20 at 02:25 +0200, Jérémy Lal wrote:
> > https://salsa.debian.org/js-team/nodejs/-/blob/master-
> > 18.x/debian/README.source
>
> Thanks for your suggestion. I actually did follow those instructions to
> attempt to build nodejs 18.13.0+dfsg1-1.
>
> For nodejs 16.15.1+dfsg-1 following those instructions bootstraps the
> package
> just fine, I think because the "externalized builtin" JS files are present
> in
> the packaging.
>
> I have attached the three patches to debian/ to get _something_ bootstrap
> for
> 18x but it still fails with the error "Cannot load externalized builtin"
> when
> trying to launch bootstrapped node.
>

Maybe the README.source isn't clear enough.
The node package built at first stage is just good enough to build the
second stage.
It is not feature-complete. Typically you can't run node REPL with it.
Once you have first stage, you install the resulting deb, and use that as a
build-dependency
to build second stage (which is a normal build).



>
> I build the package using debuild --no-lintian in a chroot. In the build
> system I have no ability to build arch:all packages, just architecture
> dependant packages.
>
> Thanks!
>
> > Le ven. 20 oct. 2023 à 01:27, Christopher Obbard
> >  a écrit :
> > > Source: nodejs
> > > Version: 18.13.0+dfsg1-1
> > > Severity: important
> > > X-Debbugs-Cc: chris.obb...@collabora.com
> > >
> > > Dear Maintainer,
> > >
> > > Bootstrapping nodejs version 18 FTBFS for me. There seems to be a
> couple
> > > of different issues when bootstrapping:
> > >
> > > 1) The created node binary fails with an error about the externalized
> > > builtins not being found. This renders the binary useless. This also
> > > causes an error in the bootstrap process, override_dh_auto_build-arch
> > > fails with:
> > >
> > > Cannot load externalized builtin: "internal/deps/cjs-module-
> > > lexer/lexer:/usr/share/nodejs/cjs-module-lexer/lexer.js".
> > >  1: 0x7f06454026cc node::Abort() [/mnt/_build/nodejs-
> > > 18.13.0+dfsg1/out/Release/libnode.so.108]
> > >  2: 0x7f06453e1f1d  [/mnt/_build/nodejs-
> > > 18.13.0+dfsg1/out/Release/libnode.so.108]
> > >  3: 0x7f06453e2069 node::builtins::BuiltinLoader::BuiltinLoader()
> > > [/mnt/_build/nodejs-18.13.0+dfsg1/out/Release/libnode.so.108]
> > >  4: 0x7f064531db83  [/mnt/_build/nodejs-
> > > 18.13.0+dfsg1/out/Release/libnode.so.108]
> > >  5: 0x7f064782947e  [/lib64/ld-linux-x86-64.so.2]
> > >  6: 0x7f0647829568  [/lib64/ld-linux-x86-64.so.2]
> > >  7: 0x7f06478432ca  [/lib64/ld-linux-x86-64.so.2]
> > > Aborted (core dumped)
> > >
> > >
> > > 2) dh_install fails with:
> > >
> > > dh_install: warning: Cannot find (any matches for)
> > > "./<@(node_builtin_shareable_builtins)" (tried in ., debian/tmp)
> > > dh_install: warning: nodejs missing files:
> > > ./<@(node_builtin_shareable_builtins)
> > > dh_install: error: missing files, aborting
> > >
> > >
> > > I have a couple of patches which works around these issues and can
> create
> > > a bootstrapped nodejs (I can share my patches if that is useful); but
> the
> > > created binary is useless due to the "Cannot load externalized builtin"
> > > error.
> > >
> > > Thanks!
> > >
> > > -- System Information:
> > > Debian Release: trixie/sid
> > >   APT prefers unstable
> > >   APT policy: (500, 'unstable'), (1, 'experimental')
> > > Architecture: amd64 (x86_64)
> > >
> > > Kernel: Linux 6.5.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
> > > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
> > > LANGUAGE=en_GB:en
> > > Shell: /bin/sh linked to /usr/bin/dash
> > > Init: systemd (via /run/systemd/system)
> > > LSM: AppArmor: enabled
> > >
>
> Thanks!
>
> Chris
>

Bug#1054259: [Pkg-javascript-devel] Bug#1054259: nodejs: cannot bootstrapped nodejs

[Jérémy Lal]

https://salsa.debian.org/js-team/nodejs/-/blob/master-18.x/debian/README.source


Le ven. 20 oct. 2023 à 01:27, Christopher Obbard 
a écrit :

> Source: nodejs
> Version: 18.13.0+dfsg1-1
> Severity: important
> X-Debbugs-Cc: chris.obb...@collabora.com
>
> Dear Maintainer,
>
> Bootstrapping nodejs version 18 FTBFS for me. There seems to be a couple
> of different issues when bootstrapping:
>
> 1) The created node binary fails with an error about the externalized
> builtins not being found. This renders the binary useless. This also
> causes an error in the bootstrap process, override_dh_auto_build-arch
> fails with:
>
> Cannot load externalized builtin:
> "internal/deps/cjs-module-lexer/lexer:/usr/share/nodejs/cjs-module-lexer/lexer.js".
>  1: 0x7f06454026cc node::Abort()
> [/mnt/_build/nodejs-18.13.0+dfsg1/out/Release/libnode.so.108]
>  2: 0x7f06453e1f1d
> [/mnt/_build/nodejs-18.13.0+dfsg1/out/Release/libnode.so.108]
>  3: 0x7f06453e2069 node::builtins::BuiltinLoader::BuiltinLoader()
> [/mnt/_build/nodejs-18.13.0+dfsg1/out/Release/libnode.so.108]
>  4: 0x7f064531db83
> [/mnt/_build/nodejs-18.13.0+dfsg1/out/Release/libnode.so.108]
>  5: 0x7f064782947e  [/lib64/ld-linux-x86-64.so.2]
>  6: 0x7f0647829568  [/lib64/ld-linux-x86-64.so.2]
>  7: 0x7f06478432ca  [/lib64/ld-linux-x86-64.so.2]
> Aborted (core dumped)
>
>
> 2) dh_install fails with:
>
> dh_install: warning: Cannot find (any matches for)
> "./<@(node_builtin_shareable_builtins)" (tried in ., debian/tmp)
> dh_install: warning: nodejs missing files:
> ./<@(node_builtin_shareable_builtins)
> dh_install: error: missing files, aborting
>
>
> I have a couple of patches which works around these issues and can create
> a bootstrapped nodejs (I can share my patches if that is useful); but the
> created binary is useless due to the "Cannot load externalized builtin"
> error.
>
> Thanks!
>
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.5.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_GB:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> --
> Pkg-javascript-devel mailing list
> pkg-javascript-de...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
>

Bug#1052470: [Pkg-javascript-devel] Bug#1052470: nodejs: Please fix testsuite for openssl-3.1

[Jérémy Lal]

Le mar. 17 oct. 2023 à 21:37, Sebastian Andrzej Siewior <
sebast...@breakpoint.cc> a écrit :

> On 2023-09-22 22:52:48 [+0200], Jérémy Lal wrote:
> > Thanks, will include it soon.
>
> Thanks. Any update on this?
> I added two patches. The first one is a cherry-pick from upstream, the
> second has been forwarded upstream via
> https://github.com/nodejs/node/pull/49885
>
> but upstream has no interest in applying it. So you could apply it and
> drop it after new openssl migrated to testing. Another option would be
> to binNMU later on, don't want to cause too much trouble here ;)


I did not forget about this. Really sorry for the delay.
Currently I'd be more willing to help someone maintain nodejs than doing it
myself.
However, I'll probably deal with the next 18.x update very soon, including
your patch.

Jérémy

Bug#1052470: [Pkg-javascript-devel] Bug#1052470: nodejs: Please fix testsuite for openssl-3.1

[Jérémy Lal]

Le ven. 22 sept. 2023 à 22:18, Sebastian Andrzej Siewior <
sebast...@breakpoint.cc> a écrit :

> On 2023-09-22 17:59:51 [+0200], To sub...@bugs.debian.org wrote:
> > Now I'm about to test this… But it looks promising ;)
>
> Okay, builds.
>

Thanks, will include it soon.

Bug#1052428: node-minimatch: please update to 9.x

[Jérémy Lal]

Package: node-minimatch
Version: 5.1.1+~5.1.2-1
Severity: normal

Hi,

nodejs 18.18.0 depends on node-minimatch 9.0.3.

It'd be nice if someone could update that module.

Regards,
Jérémy



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

Kernel: Linux 6.4.0-4-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 node-minimatch depends on:
ii  node-brace-expansion  2.0.1-2

node-minimatch recommends no packages.

node-minimatch suggests no packages.

-- no debconf information

Bug#1052170: ITP: node-playwright -- JavaScript framework for Web Testing and Automation

[Jérémy Lal]

Le lun. 18 sept. 2023 à 19:15, Yadd  a écrit :

> Package: wnpp
> Severity: wishlist
> Owner: Yadd 
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: node-playwright
>   Version : 1.38.0
>   Upstream Contact: Microsoft Corporation
>   
> * URL : https://github.com/Microsoft/playwright
> * License : Apache-2.0
>   Programming Lang: JavaScript
>   Description : JavaScript framework for Web Testing and Automation
>
> node-playwright is a framework for Web Testing and Automation. It allows
> testing Chromium, Firefox and WebKit with a single API. Playwright is
> built to enable cross-browser web automation that is ever-green, capable,
> reliable and fast.
>

Hi, I am a heavy user of node-playwright, so this interests me.
Note that latest version of playwright stopped downloading automatically
the needed browser, which is a good thing.
Playwright is also able to use system-installed chromium, but maybe not
firefox,
and I'm pretty sure it won't work out of the box with webkitgtk.

Cheers,
Jérémy

Bug#1052145: gjs: Please upgrade gjs to >= 1.77.2

[Jérémy Lal]

Package: gjs
Version: 1.76.2-4
Severity: wishlist

gpaste for gnome 45 depends on gjs >= 1.77.2.

I didn't check but it might be the case for other extensions ?

Jérémy


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

Kernel: Linux 6.4.0-4-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 gjs depends on:
ii  gir1.2-gtk-3.0  3.24.38-5
ii  libc6   2.37-8
ii  libgcc-s1   13.2.0-3
ii  libgjs0g1.76.2-4
ii  libglib2.0-02.78.0-1
ii  libstdc++6  13.2.0-3

gjs recommends no packages.

gjs suggests no packages.

-- no debconf information

Bug#1050186: [Pkg-nginx-maintainers] Bug#1050186: Bug#1050186: Bug#1050186: libnginx-mod-http-lua: depends on obsolete pcre3 library

[Jérémy Lal]

Le mer. 30 août 2023 à 12:18, Jan Mojzis  a écrit :

> Hi,
> I've uploaded experimental version with the PCRE2 patch included
> 1:0.10.25-2~exp1 to the experimental.


Cool !
It seems three modules need to be patched:
https://github.com/swananan/lua-resty-core/tree/support_pcre2
https://github.com/swananan/lua-nginx-module/commits/support_pcre2
https://github.com/swananan/stream-lua-nginx-module/commits/support_pcre2

Jérémy

Bug#1050186: [Pkg-nginx-maintainers] Bug#1050186: Bug#1050186: libnginx-mod-http-lua: depends on obsolete pcre3 library

[Jérémy Lal]

Le mar. 29 août 2023 à 15:43, Thomas Ward  a écrit :

> I apoligize I was thinking Lua deps not PCRE.
>
> However, I did more digging. OpenResty has been on NGINX cofe version
> 1.21.4 for the longest time.  They do not have PCRE2 support in their
> system.  As this is an OpenResty-originating module the 4th requirement as
> stated in the linked GitHub issue is not met.
>
> I would not be so sure that "next update" will have a fix if OpenResty
> core does not support PRCE2 (1.21.5 nginx introduced PCRE2 core
> requirement/build fixes, OpenResty never inccuded that).  The reason PCRE3
> is still used here in the Lua module is the custom workaround of mixing
> PCRE2 nginx and PCRE3 Lua which use different build flags at compile time
> with the linking options.
>
> Therefore, we need to not make assumptions and watch this closely.  If
> there is not movement in a reasonable time period, then we may have to drop
> this module from Debian due to PCRE3 being obsolete.
>

Actually, openresty has started supporting nginx 1.25.1 recently:

[feature: upgrade nginx core to 1.25.1 which supports HTTP3](
https://github.com/openresty/openresty/commit/6278b1aeae0593b17d3143aeb60a216f73b6bb1d)[feature:
[upgrade nginx core to 1.25.1](
https://github.com/openresty/stream-lua-nginx-module/commit/d48f057f18eb1f33123bf62be49c735c5cb98f16
)
[upgrade nginx core to 1.25.1](
https://github.com/openresty/lua-nginx-module/commit/e69fd3de281f31804857aa6dc0b8e79055716138
)
>
>
Considering the work of the author of these patches, I'd be surprised if it
wasn't finished soon (right now, only stream-lua-nginx has no support for
pcre2).

Bug#1050186: [Pkg-nginx-maintainers] Bug#1050186: Bug#1050186: libnginx-mod-http-lua: depends on obsolete pcre3 library

[Jérémy Lal]

Le lun. 21 août 2023 à 19:09, Thomas Ward  a écrit :

> Bastian:
>
> As I understand the module, for over a year now the latest Lua module
> from OpenResty requires LuaJIT to actually compile.  See
>
> https://salsa.debian.org/nginx-team/libnginx-mod-http-lua/-/blob/main/debian/control#L8
> where this is in the build deps.


> I have not tested removing the PCRE3 build dependency here, but because
> OpenResty has refused to change the Lua library to be any Lua support
> other than 5.1, it requires LuaJIT in order to provide 'continued
> support' for Lua 5.1 bytecode.
>

These comments have no relation with this bug report.


> It is my understanding that the pcre2/pcre3 dependency may not be
> needed, but I have not deep dived into the Lua packaging recently.  I'm
> running a test build from the tagged data in Salsa locally to see if it
> builds without the pcre2/pcre3 devel libraries in build-deps.
>

pcre3 is *needed* by libnginx-mod-http-lua, which doesn't support pcre2 yet.
However someone involved worked on it a few days ago:
https://github.com/openresty/lua-nginx-module/pull/2221

so hopefully the situation will resolve itself in next update.

Jérémy