text
stringlengths
15
499
[09:45] <guruprasad> StevenK, cjwatson and I were able to verify the signed message that you sent us, thereby confirming that you are indeed the owner of the account. I have requested the SSO team to help you regain access to your account. I will let you know once this is done.
=== kiska39 is now known as kiska3
=== gurupras- is now known as guruprasad
[12:13] <marenz> g'day. I am part of a team that creates some ppa automated ppa builds every now and then. Sometimes the fail and then I get 10 or more email notifications about that
[12:13] <marenz> As i am not responsible or interested in that, how can I turn those off?
[12:14] <marenz> I found no way to unsubscribe
[12:15] <cjwatson> I'm afraid there's no mechanism for that short of not being in that team. We can help you with email filtering though, if that helps?
[12:18] <marenz> i'll manage that part, but thanks :)
=== axino` is now known as axino
=== meetingology` is now known as meetingology
=== maxj_ is now known as maxj
=== ilasc_ is now known as ilasc
=== maxime is now known as EmixamPP
=== EmixamPP is now known as maxime
=== maxime is now known as EmixamPP
=== mup_ is now known as mup
=== lan3y is now known as Laney
=== Laney is now known as laney
=== mup_ is now known as mup
[11:42] <jelmer> cjwatson: If you have chance, another review of either https://code.launchpad.net/~jelmer/loggerhead/drop-python3/+merge/426103 or https://code.launchpad.net/~jelmer/loggerhead/no-file-ids/+merge/426375 would be great
[11:43] <jelmer> (the latter is larger, but supersedes the former)
[12:10] <cjwatson> jelmer: does this break old rev-id-ful links?
[12:10] <cjwatson> jelmer: I guess there may ultimately be not much choice if so ...
[12:11] <jelmer> cjwatson: It doesn't break rev-id-ful links, but would break old links that include filter_file_id arguments
[12:12] <jelmer> revid are still fully supported, fileids are becoming more of an implementation detail
[12:13] <cjwatson> Sorry, I meant file-id indeed
[12:14] <cjwatson> https://www.google.com/search?channel=fs&client=ubuntu&q=%22bazaar.launchpad.net%22+%22filter_file_id%22 finds a few such old links, but doesn't seem like catastrophically many, and I agree it seems ultimately necessary
[12:14] <cjwatson> (also those URLs really were horrible)
[12:15] <cjwatson> jelmer: I've approved the larger MP - let's see what the test job does
[12:17] <jelmer> cjwatson: we could potentially keep the support for filter_file_id around where the version of breezy / format supports it
[12:21] <cjwatson> I'm not sure that's worth it, since we'll want to upgrade breezy at some point anyway
[13:09] <cjwatson> jelmer: I hate xenial so much. https://code.launchpad.net/~cjwatson/loggerhead/py35-workarounds/+merge/426630 ?
[13:09] <cjwatson> jelmer: (deals with the test failure on your branch)
[13:14] <jelmer> cjwatson: LGTM
[13:14] <jelmer> cjwatson: is launchpad still on xenial or is it just the test runner for loggerhead?
[13:18] <jugmac00> jelmer: still - but we are working on it
[13:21] <cjwatson> Yeah, the migration got set back quite a bit by needing to move out of an old datacentre
[13:26] <cjwatson> Tests pass on bionic, but we're trying to see if we can jump straight to focal in order to make more economical use of scarce SRE time. We have solid progress on 2/3 of the remaining known blockers for running on focal.
[13:31] <cjwatson> jelmer: I assume you'd like us to upgrade bazaar.launchpad.net to this? (Or you can propose a merge yourself - it's still `utilities/sourcedeps.{conf,cache}` with a `utilities/update-sourcecode` script for managing the latter, though it's in git these days and it's been almost a decade since your last commit so I don't imagine you still have a development environment handy ...)
[13:34] <cjwatson> jelmer: and should we reject https://code.launchpad.net/~jelmer/loggerhead/drop-python3/+merge/426103 now?
[13:35] <jelmer> cjwatson: yeah, it'd be good to upgrade - though there's no hurry until you also update to Breezy >= 3.3
[13:35] <jelmer> cjwatson: Yeah, I'll remove that MP - thanks for the merge
[13:39] <cjwatson> jelmer: OK, I filed https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/426634 since I figure we may as well stay current
[18:42] <cjwatson> jelmer: Would you mind having a quick look at https://code.launchpad.net/~cjwatson/difftacular/breezy-3.2/+merge/427045 and https://code.launchpad.net/~cjwatson/difftacular/py3-unicode/+merge/427046, please?
[20:00] <jelmer> cjwatson: yep
[22:46] <jelmer> cjwatson: both LGTM
[22:47] <jelmer> (not near my Launchpad credentials atm, but should be tomorrow)
[11:36] <jelmer> cjwatson: what is it that powers the CI that e.g. launchpad uses?
[11:46] <cjwatson> jelmer: buildbot.net
[11:46] <cjwatson> jelmer: we don't use that anywhere else though, and will probably eventually move away from it since it's kinda crufty
[11:47] <cjwatson> jelmer: for a bunch of other things we have a complicated pile of Jenkins jobs, which is no better really ... eventually we hope to use Launchpad's newish built-in CI system for this
[12:39] <jelmer> cjwatson: that sounds interesting
[12:39] <jelmer> Would it work for bzr too, or just git?
[12:58] <cjwatson> jelmer: at present just git
[12:59] <cjwatson> adding bzr would probably be possible, though it's mostly hard to justify spending very much time on new features there at the moment
[12:59] <cjwatson> but maybe
[12:59] <jelmer> I might be able to chip in a little, since it seems breezy's current CI will be going away in a while
[12:59] <jelmer> depending on how much work it would be
[13:19] <cjwatson> jelmer: I think it'd basically be changes to lpbuildd.ci and lpbuildd.target.run_ci in launchpad-buildd, a DB patch to RevisionStatusReport and CIBuild in LP, corresponding code patches, something in CIBuildBehaviour, maybe something in the branch scanner to trigger builds, probably bits of UI. But maybe first look at https://lpcraft.readthedocs.io/ to see whether it's suitable for you (you can
[13:20] <cjwatson> "snap install lpcraft" and try it out locally)
[13:30] <jelmer> cjwatson: is it ubuntu-specific?
[13:30] <jelmer> (a first glance suggests it is)
[13:32] <cjwatson> jelmer: it doesn't have to be in principle, but at present yes
[13:33] <cjwatson> we've been developing it mainly for a customer project in the first instance, so you know how it is, anything not on the critical path tends to get pushed aside
=== jelmer_ is now known as jelmer
[23:27] <cjwatson> jelmer: Would you be able to review https://code.launchpad.net/~cjwatson/difftacular/python-packaging/+merge/427995 please? I also wonder if it might be possible to get brz-builder and brz-loom onto PyPI, maybe
[23:27] <cjwatson> jelmer: (I'm trying to finally eradicate Launchpad's horrible old pre-pip "sourcedeps" mechanism, which you may distantly remember)
[04:22] <jelmer> cjwatson: that MR LGTM
[04:23] <jelmer> I'm currently traveling without my launchpad credentials so can't formally +1 it in the web UI (back in a week)
[09:12] <cjwatson> jelmer: fair enough, thanks!
=== madhens_ is now known as madhens
[12:28] <jelmer> cjwatson: the MR changing simpletal to chameleon LGTM
[12:29] <jelmer> We can probably drop byov.conf and Travis now that there is a landing bot you're running
=== cjwatson_ is now known as cjwatson
[12:29] <cjwatson> I thought the latter might be the case, but didn't want to step on your toes. Are those other two systems running anywhere at the moment?
[12:30] <cjwatson> Our landing bot has the issue that you can't see the output
[12:34] <cjwatson> On the chameleon MP: I picked that up recently, motivated by trying to get things pip-installable. Worked on it for a bit, explored a couple of different approaches, got things roughly working, belatedly decided to make an actual branch for it. Then I discovered that I already had a branch called "chameleon" with nearly-identical changes, dating from 2020. *facepalm*
[12:35] <jelmer> Travis is no longer running, and byov still running but will go way in the near future (and doesn't have access to lp:loggerhead, just the ~breezy user)
[12:35] <cjwatson> (I hadn't dealt with all the TAL changes, which is probably why I hadn't pursued it any further at the time)
[12:35] <jelmer> cjwatson: lol
[12:35] <cjwatson> Well, I'll delete the Travis config at least then, that much sounds like a no-brainer
[12:35] <jelmer> At least you're consistent in what alternative to pursue :-)
[12:36] <cjwatson> I do like it when my past and present selves agree
[12:36] <cjwatson> Almost spookily so though
=== lifeless_ is now known as lifeless
=== lan3y is now known as Laney
=== Laney is now known as laney
[08:08] <cjwatson> jelmer: I don't think there's any merge bot that might land https://code.launchpad.net/~cjwatson/brz-loom/rename-python-package/+merge/428034. Could you merge it manually?
[08:11] <cjwatson> jelmer: Also I'm inclined to release loggerhead as 2.0.0 (due to the removal of file-id support and dropping Python 2). Any objections?
[08:12] <jelmer> cjwatson: Yeah, there's no bot - merging it is on my todo list :)
[08:12] <jelmer> cjwatson: A 2.0.0 release makes sense to me!
[13:54] <cjwatson> Huh, weird, I had to do https://github.com/cdent/paste/pull/70 to get pip-installed loggerhead working properly. Can't quite see why that wasn't a problem before.
[16:04] <jelmer> cjwatson: brz-loom branch landed
[16:12] <cjwatson> jelmer: Ooh, thanks. Any chance we might get brz-loom and brz-builder onto PyPI then?
[16:13] <cjwatson> I think that would let me finally renounce https://git.launchpad.net/launchpad/tree/utilities/sourcedeps.conf, all its works, and all its empty promises
[16:14] <cjwatson> (or something)
[16:15] <cjwatson> Might also allow removing a whole bunch of complexity around setting the plugin path
[17:41] <jelmer> cjwatson: yup!
[17:41] <jelmer> I've uploaded brz-loom, will upload brz-builder shortly
[17:41] <jelmer> there's 4 failing tests in brz-loom that I need to take another look at at some point (they've been there for a while)