/srv/irclogs.ubuntu.com/2023/07/27/#ubuntu-devel.txt

tsimonq2_ephemer@pilot out00:35
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A
tsimonq2_ephemerI'm always happy to help with sponsoring. :)00:35
* tsimonq2_ephemer will be back to @pilot in later00:35
tsimonq2_ephemer(I might not be the only one experiencing Matrix interruptions Soon; worth looking into if you depend on that platform.)00:36
mdeslaurtsimonq2_ephemer: nope! you didn't drop the patch, that's the important part :)01:15
=== sammy12 is now known as bomtom
blucadid something change in jammy tonight w.r.t. llvm? on github actions jammy images, installing lldb-15 started failing in the systemd CI with:10:49
blucaThe following packages have unmet dependencies:10:50
blucapython3-lldb-14 : Conflicts: python3-lldb-x.y10:50
blucapython3-lldb-15 : Conflicts: python3-lldb-x.y10:50
blucanothing is pulling in python3-lldb-x.y, it doesn't even exist, as far as I can tell10:50
blucahttps://github.com/systemd/systemd/actions/runs/5678852202/job/15391861406#step:3:49010:58
bdrung@pilot in11:24
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: bdrung
rbasakbdrung: o/ I've been looking at apport dep8 failures12:34
rbasakBut now I see that it FTBFS with a pylint problem. pylint has been updated since it last built on Mantic so that might be the reason.12:34
rbasakCan we just stop running pylint as part of the package build? It's inappropriate as it causes regressions in the archive when pylint implements new checks, for no benefit to the distribution. Linting belongs in development workflow, not in production builds.12:35
rbasakSame for black --check, etc.12:37
bdrungrbasak, but then security updates are not checked12:38
bdrungwe have the linters run on every upstream commit12:38
rbasakThat's up to the security team's development workflow. The downside is that if there's been a pylint update since the last build, causing an unrelated lint regression it's going to _slow down_ issuing security updates while it's worked around.12:39
rbasakBy all means have a mechanism in there to run linting, but in production it should be informative only, and not cause a failure.12:40
bdrungpylint and mypy found issues in the past. could we tone down pylint during the package build to maybe only errors?12:41
bdrungcan you open a bug against apport?12:42
rbasakMaybe this should have a wider discussion12:42
rbasakIMHO the same applies to things like -Werror but I don't know what we do there.12:42
bdrungfor -Werror the consensus is that we do not want it12:43
rbasakAh OK. So yeah, I think the same principle applies here.12:43
bdrungmove the linter to an autopkgtest instead?12:43
rbasakNo, not even autopkgtest.12:43
rbasakAgain, we'd get regressions in the archive as pylint moves12:44
rbasak(or black, etc)12:44
rbasakIt should be something to check before upload, and then not blocked on again in archive workflow following upload.12:44
rbasakI don't know of a good tooling solution for that.12:45
rbasakIt'd be nice if DEB_BUILD_OPTIONS had some defined parameter for this purpose but I don't think it does.12:45
bdrungDEB_BUILD_OPTIONS would be a good idea. i.e. having a strict mode that enables -Werror and all the linters12:46
bdrungthen you can build with strict mode before upload12:46
rbasakStrict mode is a good term12:46
rbasakThe usefulness of that might be limited to native and native-type packages though. Where there's an out-of-distro upstream, the packager would never want strict mode.12:47
ahasenack_jbicha: regarding mutter and gnome-shell 44.3 in lunar, first mutter, let it phase?13:03
ginggsahasenack_: from # ubuntu-release13:08
ginggs<jbicha> rbasak: mutter and gnome-shell at once is fine since there isn't a phasing issue with this update13:08
ahasenack_I saw the note in the bug even, but it also said it was ok to wait for phasing13:08
ahasenack_hm, I must have been offline when jbicha answered13:09
ahasenack_and my nick is wrong13:09
=== ahasenack_ is now known as ahasenack
jbichaahasenack: yes, you could let mutter phase first but it's not necessary13:15
ahasenackok13:17
cjwatsonIME https://pre-commit.com/ is a better way to handle linting for anything maintained in git - that way you can control what versions of linters you're using, and you aren't at the mercy of distribution-wide changes13:22
cjwatsonAnd it's hooked in at a much more appropriate stage of development13:22
mitchdzAnyone know what's going on with livecd-rootfs in Mantic? autopkgtests are failing and it's keeping my package (multipath-tools) in -proposed14:08
rbasakpre-commit> oooh, nice!14:23
rbasakI see it's packaged in Debian, too.14:23
bdrung@pilot out15:00
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A
enr0nbluca: there were security updates for llvm-toolchain-14 and llvm-toolchain-15 (at least). Not sure if those caused it. But python3-lldb-{14,15} both Provides:/Conflicts:/Replaces: Provides: python3-lldb-x.y15:19
blucaour ci is installing clang-15 lldb-15 lld-15 clangd-15, and somehow that started pulling in both python3-lld-14 and -1515:22
blucawe solved it by explicitly pulling in python3-lld-1515:22
blucait has been running jammy with that same configuration for over a year, this issue appeared this morning15:24
enr0nbluca: okay. Not sure what happened there. I tried to reproduce it quickly in a new jammy container, but I didn't hit the issue.15:29
blucavery weird15:39
rbasakhttps://autopkgtest.ubuntu.com/results/autopkgtest-mantic-racb-experimental/?format=plain15:49
rbasakThis server could not verify that you are authorized to access the document you requested.15:49
rbasakWhat am I missing?15:49
rbasakI saw the test appear in /running and it's gone now, so presumably it finished15:50
rbasakIs there a delay expected?15:50
cjwatsonrbasak: pre-commit> yeah, we use it extensively in Launchpad, for instance - https://git.launchpad.net/launchpad/tree/.pre-commit-config.yaml15:56
xnoxmwhudson: yes.... i got scared to upload  2.90015:56
=== rharper_ is now known as rharper
bdmurraythe autopkgtest-cloud code is also using pre-commit.16:04
ahasenackbdmurray: up for a quick verification for lunar on https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984? Then I could release it16:18
-ubottu:#ubuntu-devel- Launchpad bug 1971984 in pcsc-lite (Ubuntu Lunar) "pcscd.socket is disabled after installation" [High, Fix Committed]16:18
ahasenackit's install + systemctl status16:18
ahasenackand install old, upgrade, systemctl status16:18
rbasakIs there a delay expected> apparently so16:28
rbasakI have results available now.16:28
bdmurrayahasenack: I can fit that verification in16:37
ahasenackthx16:37
shadeslayerHi, I'm trying to build perf for my devel machine that's running the mainline 6.5-rc3 kernel, but I'm confused between all the different instructions on the wiki, the existence of a git bundle and not being able to clone the git repo mentioned on the web page. Could someone point me towards how I can obtain the source for the mainline debs? thanks!16:37
shadeslayerahhh ... I guess it's just git bundle unbundle16:50
kanashiro[m]@pilot in17:02
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: kanashiro[m]
=== orndorffgrant5 is now known as orndorffgrant
ahasenackcoreycb: hi, do you think for future openstack-component SRUs, for the verification step, you could add something that shows that the package from proposed was used?18:53
ahasenackcoreycb: perhaps like peter sabaini did for ceph in https://bugs.launchpad.net/cloud-archive/+bug/2018929/comments/1318:54
-ubottu:#ubuntu-devel- Launchpad bug 2018929 in Ubuntu Cloud Archive "[SRU] ceph 17.2.6" [Undecided, New]18:55
rbasakbdrung: I filed bug 2028879 and bug 2028881 rather than uploading since both of my proposed fixes are a bit questionable. Would you be happy with me dropping the lint tests from debian/rules, and to add vim to the autopkgtest dependencies for now?19:33
-ubottu:#ubuntu-devel- Bug 2028879 in apport (Ubuntu) "Lack of default dpkg diverts causes autopkgtest failure" [High, Triaged] https://launchpad.net/bugs/202887919:33
-ubottu:#ubuntu-devel- Bug 2028881 in apport (Ubuntu) "apport FTBFS" [High, Triaged] https://launchpad.net/bugs/202888119:33
bdmurrayahasenack: I've verified bug 1971984 for Lunar19:40
-ubottu:#ubuntu-devel- Bug 1971984 in pcsc-lite (Ubuntu Lunar) "pcscd.socket is disabled after installation" [High, Fix Committed] https://launchpad.net/bugs/197198419:40
ahasenackbdmurray: thanks20:09
kanashiro[m]@pilot out21:07
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A
tsimonq2_@pilot in21:40
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: tsimonq2_
bdrungrbasak, i would be fine with adding "|| true" to the lint call (to still have the output) and to add vim. for the upstream fix i have to have a deeper look into the test to make it more robust.21:57
rbasakOK thanks. I'll do it tomorrow.22:05

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!