[00:23] <lagunaloire> ok how can libharfbuzz-dev with source code about version 5.2 be put into ubuntu repositories
[00:40] <lagunaloire> and to make sure it has all the harfbuzz-support code
[00:41] <lagunaloire> there seems to be a direct attack on 32 bit intel pentium processors like the pentium 4 northwoods and the celeron's
[00:42] <lagunaloire> seems like people are trying to force intel 32 bit out of the business and move everyone to 64 bit
[00:43] <lagunaloire> i don't see how intel approved those chromium scumbags trying to obsolete intel...and moving to sse3 instructions with a patch that deliberately and drastically slows down sse2 processors
[00:44] <lagunaloire> that patch brings an intel pentium 4 to its knees
[00:45] <lagunaloire> those chromium scumbag trash need to be destroyed for trying to obsolete everyone's hardware prematurely
[00:45] <lagunaloire> i don't see how intel let this kind of shit slide
[00:48] <lagunaloire> instead of making the web more accessible to everyone...the bastards have tried to monopolize it for only latest hardware designs
[00:48] <lagunaloire> it is in direct violation of www standards and goals
[00:51] <lagunaloire> the web was supposed to be an avenue for the poor and needy to have the same learning opportunities that the rich disgusting and shameful have...and this bullshit of forcing people to throw their hardware into the trashcan just because of a web browser...is appalling
[00:51] <lagunaloire> poor people have older hardware...not the latest stuff from the most expensive sellers in the world
[00:52] <lagunaloire> this is a direct attempt to destroy the poor and their access to the web
[00:53] <lagunaloire> those greedy harware manufacturing sons of bitches and enemies of the poor need to be brought to justice
[09:17] <mitya57> sil2100: Hi! https://bileto.ubuntu.com/v2/metadata returns 500 error
[09:18] <sil2100> mitya57: yeah, see -release - I was made aware of that already. Still didn't get direct access to Bileto but I'll try to nudge it via IS later
[09:18] <mitya57> Okay, sorry. I searched in this channel but not in -release.
[09:19] <mitya57> Thanks!
[13:20] <jbicha> tjaalton: hi, have you seen Debian bug 1025312 ? it is making a lot of packages fail to build in Debian (those using Xvfb for build tests)
[13:20] -ubottu:#ubuntu-devel- Debian bug 1025312 in libgl1-mesa-dri "libgl1-mesa-dri: multiple packages FTBFS and have autopkgtest regressions running test programs under Xvfb" [Grave, Open] https://bugs.debian.org/1025312
[13:58] <tjaalton> jbicha: yes
[14:16] <tjaalton> jbicha: fixes available, I'll upload it to sid before EOD
[18:52] <bdmurray> FYI I just updated some code in the production autopkgtest environment if y'all see anything weird
[19:06] <nteodosio> https://autopkgtest.ubuntu.com/request.cgi?release=bionic&arch=arm64&package=chromium-browser&ppa=canonical-chromium-builds/stage&trigger=chromium-browser/108.0.5359.71-0ubuntu0.18.04.5
[19:06] <nteodosio> https://autopkgtest.ubuntu.com/request.cgi?release=bionic&arch=armhf&package=chromium-browser&ppa=canonical-chromium-builds/stage&trigger=chromium-browser/108.0.5359.71-0ubuntu0.18.04.5
[19:06] <nteodosio> https://autopkgtest.ubuntu.com/request.cgi?release=bionic&arch=i386&package=chromium-browser&ppa=canonical-chromium-builds/stage&trigger=chromium-browser/108.0.5359.71-0ubuntu0.18.04.5
[19:06] <nteodosio> Can someone please trigger those for me?
[19:10] <bdmurray> doing so
[19:16] <nteodosio> thanks
[21:39] <mwhudson> jdstrand: hey do you have the impending go 1.19.4 release on your radar?
[21:42] <jdstrand> mwhudson: I do, yes
[21:43] <mwhudson> jdstrand: great i do to, but depending on the interpretation of "us business hours" you may get to it first
[22:07] <bluca> schopin: there are 3 bugs in tpm2-openssl in jammy, affecting azure: https://bugs.launchpad.net/ubuntu/+source/tpm2-openssl/+bugs
[22:08] <bluca> I've done the legwork to add the sru template, backport, test - could you please sponsor an sru? branch is ready on salsa
[22:09] <bluca> all fixes are from upstream releases, and already available in lunar
[22:10] <bluca> i've got internal users hitting those on azure, so would be really great to get it sorted in jammy-p-u - TIA
[22:32] <kanashiro[m]> mwhudson: I tried to backport golang-1.18 from jammy to bionic but it was not that straightforward as I was expecting. I simply downgraded the debhelper compat level to 11 but then the generated deb package is "empty", you can check it out in bionic-proposed. Would you have some time to take a look and see if you could help me to fix that? For instance, it is using some debhelper >= 12 features which require some changes in d/rules
[22:32] <kanashiro[m]> to properly build with debhelper 11
[22:32] <mwhudson> kanashiro[m]: argh
[22:34] <mwhudson> kanashiro[m]: good news, we have dedicated go toolchain person starting soon :)
[22:35] <kanashiro[m]> that's good news indeed
[22:37] <mwhudson> hm i guess we only need to ignore this problem for like 5 months and then bionic is EOL?
[22:41] <mwhudson> yes i think i agree based on those build logs that something has gone wrong
[22:49] <kanashiro[m]> mwhudson: the server team is supposed to backport the container stack to bionic this cycle, that's why I am trying to do this hopefully final backport to bionic before it becomes EOL
[22:51] <kanashiro[m]> latest docker.io does not build with go 1.16 which is the greatest go version we have in bionic right now
[23:40] <mwhudson> yeah i agree in general that we should backport the go from the current lts to all supported ltses
[23:41] <mwhudson> can reproduce the issue locally, let's see what's going on