[04:03] Would anyone (cjwatson?) happen to know how lp:ubuntu-sponsoring is deployed? [04:03] I'd like to convert it to Git. === benonsoftware is now known as bdw [06:06] tsimonq2: Haven't the foggiest [06:08] cjwatson: Do you know where I can find who knows? :P [06:10] tsimonq2: Nope [06:11] cjwatson: Mkay, thanks anyway. [06:11] Achievement unlocked: Found something cjwatson doesn't know. [06:12] ^ [06:13] Heh [06:13] I'd start by asking people who've committed to that branch [06:14] (and who are still around) [06:16] If Laney or bdmurray don't know, I *think* I still have a way to contact dholbach, if he remembers. [06:19] Otherwise I just about cut the sponsoring queue in half, and I plan on going further tomorrowish, but I want to eventually (but slowly, ELITTLETIME) work on refining the queue in general. [06:31] smoser: wow, huge thanks for pdftk snap, and thanks to command-not-found patchers who have added snap support :D [06:31] whoa pdftk snap. cool. [06:31] I was like "nooo, gone in bionic" [06:31] but snap saved [06:32] apparently it doesn't build with GCC 7 [06:32] but in my use case I have a note that eg pdfjoin tool breaks hyperlinks, pdftk does what I want === Ionic is now known as Guest12666 [08:15] tsimonq2: Well done on your work there. It's probably a cron script on some machine. I could find out if necessary - but is it that important to switch it? [08:18] Laney: bzr is painfully slow, even with a wrapper. [08:18] And thanks. [08:19] what is painfully slow about it? [08:19] Pushing/pulling. [08:19] You plan to do a lot of that on the sponsoring queue? [08:19] I plan on working on it a bit, yeah. [08:21] And pushing it *that* often? [08:21] We're talking five seconds vs 30. [08:22] I push frequently enough to make it annoying. [08:22] But even at a 25 second deficit, how often are you planning to push the spnosor queue's branch? [08:22] It's probably pulled from trunk with each run, so you should only be pushing things you actually want to deploy ... [08:22] I don't know if I can give you a quantitative value. [08:23] And that's yet another advantage of Git, multiple branches. [08:23] I understand the differences between the two. [08:24] I'm challenging the benefit gained by someone having to go find out how this is deployed and update that to work with git, when the project is not active at all. [08:25] I guess I personally see the ROI for someone taking maybe 5 minutes to reclone a repo and sed a crontab. [08:25] It costs more overhead to continue using Bazaar than to switch it. [10:14] It does make it easier for others to contribute to [10:15] It's much more of a pain trying to remember how to do things with bzr at least. And then there are all the things that you can't do easily (eg. squash) [10:15] But rbasak! Brz is cool. [10:15] !info brz [10:15] brz (source: breezy): easy to use distributed version control system. In component universe, is optional. Version 3.0.0~bzr6852-1 (bionic), package size 36 kB, installed size 72 kB [10:16] There is one feature I like in bzr, lp-propose. Though it is known to have unexpected results. [10:20] IIRC sparkiegeek (not here) has a git replacement equivalent for LP for that? [10:31] That sounds shiny. [10:38] rbasak: snap info gitlptools [10:40] Thanks! [10:40] Unit193: ^ [10:40] Is there a source for that? [10:40] https://launchpad.net/gitlptools it loos like [10:42] Hmm, no tags.. [10:45] tsimonq2: Looks like something you might want to know about, and package. [12:17] Mirv: thanks for sharing. Would you upvote https://askubuntu.com/questions/1028522/how-can-i-install-pdftk-in-ubuntu-18-04-bionic ? [12:18] unless you honestly think that shell-script-blob (currently the top aswer) is a better way of distributing software :) [13:07] smoser: upvoted the snap one, yes I think it should be on the top... === Ionic_ is now known as Ionic [14:56] tsimonq2: What was the original question? [17:12] rbasak: Are you familiar with postgresql or is there somebody else on the server team I should ping? [17:58] bdmurray: what's up? Maybe I can help, rbasak and cpaelzer are eod [17:59] cpaelzer prepared the recent postgresql sru [18:00] ahasenack: its about postgresql and release upgrades. postgresql is in the release upgrader blacklist b/c of bug 871893 and I wonder if its still relevant. [18:00] bug 871893 in update-manager (Ubuntu Oneiric) "After upgrading postgresql-databases are not accessible any more" [Critical,Fix released] https://launchpad.net/bugs/871893 [18:01] see also bug 1787349 [18:01] bug 1787349 in ubuntu-release-upgrader (Ubuntu) "postgresql-plperl-9.5 blocks do-release-upgrade from 16.04 to 18.04" [Undecided,New] https://launchpad.net/bugs/1787349 [18:01] that's from 2011 [18:02] I have no idea [18:03] Okay, I'll email ubuntu-devel [18:03] slangasek: https://autopkgtest.ubuntu.com/running is outdated, I triggered those cmake/gnutls runs last night [18:34] bdmurray: I neither hae background on this postgres thing [18:34] this was all in the time pitti cared for it [18:35] bdmurray: you should set him to CC on this mail [18:35] maybe he can shed some light [20:15] sbeattie: Thanks for the sponsorship. [20:49] Unit193: you're welcome, thanks for preparing the update! [22:09] bdmurray: Where's lp:ubuntu-sponsoring deployed? [22:13] tsimonq2: you mean the name of the server? [22:14] bdmurray: Right; that, and how it's deployed. I'd like to convert it to Git. [22:15] bdmurray: I can do the conversion, I just need someone with access to button push. [22:20] tsimonq2: Its on cranberry and laney and I, and some others, have access. [22:24] Are you sure it's on cranberry? [22:25] Not rootstock? [22:26] There, it's converted: https://git.launchpad.net/ubuntu-sponsoring [22:26] rbasak: yes [22:26] Oh. OK [22:27] bdmurray: what does it run as, OOI? [22:27] Ah [22:27] ubuntureports [22:27] I see it. Nice to know, thanks. [22:28] rbasak: Yeah, I guess you have access too. [22:28] Yes [22:29] Though I won't push any buttons without others telling me that's OK :) [22:30] (since my access is only incidental to other stuff) [22:30] I guess not being a Canonical employee there's no way for me to have access, correct? [22:30] Though I was left with co-adminship of ~ubuntu-sponsors at one point [22:31] I haven't looked at it in so long as it is... [22:31] tsimonq2: I assume so, since it's shell access on some Canonical infrastructure. [22:31] Though presumably all the actual code that's running is in the public repo [22:32] I would even argue that https://launchpad.net/ubuntu-sponsoring should be "maintained" by ~ubuntu-sponsors, not ~ubuntu-dev, because anyone from ~ubuntu-dev can join ~ubuntu-sponsors, and I'd argue that you should be sponsoring things to get commit access to the associated infra. [22:33] bdmurray, rbasak: If you both agree, it's a flip of a switch. Otherwise I can ask for more wider feedback on e.g. ubuntu-devel. [22:33] rbasak: Canonical infra> ack. [22:34] tsimonq2: I have no objection. Though I think peer review might be a good idea (or at least the opportunity; if nobody objects after a while then we shouldn't cause policy to enforce blocking progress) [22:35] rbasak: Peer review on the policy change or code changes in general? [22:35] On code changes in general [22:35] Sure. [22:36] I know dholbach drove that for a while, but I've just been making commits that seem useful. [22:36] With Git, this will become much easier to just put commits in feature branches. :)