[10:56] <schopin> rbasak: regarding your OpenSSL/NodeJS question, I *think* this document answers the question: https://github.com/nodejs/TSC/blob/main/OpenSSL-Strategy.md#nodejs-version-16x-est-apr-2021-eol-apr-2024 (I'm not responding on the ML because I'm not a dev yet so I'm always stuck in moderation queue, which isn't great for conversations)
[10:59] <schopin> But I'm a bit confused. Does the nodeJS package link against a vendored OpenSSL in Ubuntu? And does the NodeJS ecosystem distribute pre-built binaries in npm?
[11:09] <xnox> tjaalton:  https://autopkgtest.ubuntu.com/packages/n/nvidia-graphics-drivers-390/impish/armhf looks like it FTBFS on armhf
[11:09] <xnox> /var/lib/dkms/nvidia/390.144/build/common/inc/nv-linux.h:467:43: error: implicit declaration of function ‘outer_sync’ [-Werror=implicit-function-declaration]
[11:09] <xnox>   467 | #define WRITE_COMBINE_FLUSH()    { dsb(); outer_sync(); }
[11:09] <xnox> and i'm failing to figure out how did it work before (if ever)
[11:15] <xnox> maybe arm_heavy_mb() needs to be used instead?
[11:15] <tjaalton> xnox: you probably meant tseliot?
[11:21] <xnox> yes, yes i do.
[11:21] <xnox> sorry =)
[11:21] <xnox> tseliot-:  ^^^
[11:25] <rbasak> schopin: AFAIK, the nodejs package links against a system provided openssl (via build-depends of the -dev package) and the ecosystem does distribute binaries. However I'm just going on what I've been told in bugs by people doing the actual work - I've not investigated myself.
[11:27] <rbasak> schopin: that doc is really helpful. Looks like there's not a clear answer for nodejs for us then, as they're expecting openssl 3 support only in Apr 2021? That's likely to be too late for us.
[11:28] <schopin> Erm. April 2021 is in the past :)
[11:30] <xnox> tseliot-:  https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642
[11:30] <ubottu> Launchpad bug 1946642 in nvidia-graphics-drivers-390 (Ubuntu) "nvidia-graphics-drivers-390 ftbfs on armhf" [Undecided, New]
[11:30] <rbasak> Oh
[11:30] <rbasak> https://github.com/nodejs/node/issues/29817 is still open though?
[11:30] <ubottu> Issue 29817 in nodejs/node "[Tracking Issue] OpenSSL 3" [Open]
[11:37] <xnox> also, if we go down the route of having both 1.1.1 and 3 openssl, i will want to make libssl-dev's be coinstallable this time around.
[11:38] <xnox> i.e. ship libssl1.1-dev in like /usr/include/libssl1.1/ssl/ path or some such with adjusted pc files etc.
[11:38] <xnox> cause then people will be able to build against 1.1.1 headers by forcing -I/usr/include/libssl1.1
[11:38] <xnox> obviously it is a downstream solution, for which there is no support anywhere yet.
[11:48] <schopin> xnox: yes, that'd be nice :)
=== sem2peie- is now known as sem2peie
[11:55] <cjwatson> schopin: I've added you to the ubuntu-devel accept list, so you shouldn't get stuck in moderation again
[11:56] <schopin> cjwatson: many thanks!
[13:24] <seb128> juliank, hey, is that known that packagekit still thinks it's offline on impish today?
[13:25] <seb128> bug #1946196 confirmed on a current pending daily iso install
[13:25] <ubottu> Bug 1946196 in packagekit (Ubuntu) "Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)" [High, Triaged] https://launchpad.net/bugs/1946196
[13:25] <seb128> pkmon states that the system offline despite being connected to wifi
[13:25] <seb128> and pkcon install fails stating it can't install offline
[13:34] <bdmurray> there was bug 1943189 about something similar
[13:34] <ubottu> Bug 1943189 in packagekit (Ubuntu Hirsute) "[SRU] 'cannot refresh whilst network offline'in plasma-discover" [Undecided, Confirmed] https://launchpad.net/bugs/1943189
[13:35] <bdmurray> oh but seb is talking about bug 1946196
[13:35] <ubottu> Bug 1946196 in packagekit (Ubuntu) "Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)" [High, Triaged] https://launchpad.net/bugs/1946196
[13:35] <bdmurray> Foundations has a meeting in a bit and I'll bring it up
[13:41] <seb128> bdmurray, thanks, and yes it does sound similar
[14:19] <paride> juliank, hi! if one has to install python-apt in a venv, is `pip install 'python-apt @ git+https://salsa.debian.org/apt-team/python-apt.git[@...]' the way of doing it, or is the package published in pypi with a name I wasn't able to guess? :)
[15:02] <juliank> paride: it is not published
[15:02] <juliank> paride: generally, python-apt A.B version should match apt's
[15:03] <juliank> seb128: I did expect there to be more to it, the fix likely works for some, but not everyone, and it needs to be fixed in glib properly presumably
[15:03] <paride> juliank, so you're saying it's not a good idea to have an arbitrary version of the python-apt on a given system
[15:03] <juliank> right
[15:04] <juliank> paride: like a future python-apt 2.9 might work with apt 2.8 or not, I can't say :D
[15:04] <seb128> juliank, it has more impact that the initial bug suggested though, it's not possible to install debs from snap-store atm on an new impish install
[15:04] <seb128> juliank, which I would consider it as a release blocker
[15:04] <juliank> paride: same for existing versions
[15:05] <paride> juliank, ack, makes sense, thanks.
[15:06] <juliank> seb128: IMO this is all desktop side magic in packagekit calling glib, I'm not deep into that. Do other glib-based daemons see the system as offline too, for example, is an interesting question
[15:07] <cjwatson> Launchpad has a slightly hilarious hack to allow using python-apt from a virtualenv without having to use --system-site-packages
[15:07] <juliank> seb128: So all it does is:
[15:07] <juliank> ▸   GNetworkMonitor *network_monitor;
[15:07] <cjwatson> https://git.launchpad.net/launchpad/tree/utilities/link-system-packages.py + https://git.launchpad.net/launchpad/tree/system-packages.txt
[15:07] <juliank> ▸   network_monitor = g_network_monitor_get_default ();
[15:07] <juliank> ▸   return g_network_monitor_get_network_available (network_monitor);
[15:08] <juliank> I wonder if you can have release series on pip
[15:08] <juliank> so you can say install python-apt for focal; or install python-apt 1.8.*
[15:08] <juliank> I don't know how that all works, so never published anything there
[15:08] <seb128> juliank, it's only a system start issue though, if you restart the service things are working, so it somehow fail to refresh on interfaces changes
[15:09] <cjwatson> juliank: not usefully; last I checked, none of the defined environment markers were relevant
[15:10] <juliank> seb128: Yeah, I guess glib does not pick up new interfaces or something?
[15:10] <juliank> seb128: We did not have the complaints in hirsute, so is this a regression between glib 2.68.0/1 and 2.68.4?
[15:11] <seb128> juliank, could be, but we are on the same glib stable serie than for hirsute, unsure if that changed in some point release?
[15:11] <seb128> juliank, I will try to download glib see if that makes things better
[15:18] <seb128> juliank, it's not glib, same issue with the hirsute deb installed
[15:19] <seb128> I need to drop offline, will poke at it more later
=== not_phunyguy is now known as phunyguy