[12:47] <theidiotthatisme> Howdy
[12:47] <vorian> branching out theidiotthatisme?
[12:47] <vorian> :)
[12:47] <theidiotthatisme> Yes
[12:48] <theidiotthatisme> vorian: Decided to try and check out other channels while writing a letter for the ET wiki
[12:48] <theidiotthatisme> I have bad comp ADD lol
[12:48] <vorian> ah
[12:49] <vorian> so, interested in marketing for ubuntu theidiotthatisme?
[12:52] <theidiotthatisme> vorian: I'd start in the ohio team on that first (hmmm... lol)
[12:52] <vorian> :)
[12:52] <vorian> great place to start!
[12:52] <theidiotthatisme> Was talking to Dan about the Education and Marketing teams in Ohio
[12:53] <theidiotthatisme> We really want to try and work together as much as possible, and probably the ET will work closely with NU by assocation :-)
[12:56] <vorian> I just want to get that moodle going!
[12:56] <theidiotthatisme> lol
[12:57] <theidiotthatisme> Hey I have no experience with that and no way to edit anything on there :-P
[12:57] <theidiotthatisme> But it's gonna be a part of Sunday's meeting, along with a *LOT* of other stuff
[12:58] <vorian> w00t!
[12:59] <theidiotthatisme> I'm happy to see Seekker again :-)
[01:04] <vorian> :)
[10:23] <jenda> Burgwork: Are you the admin of the ubuntu-marketing list?
[10:24] <jenda> Burgwork: if so... nixternal and I agreed (and poningru might, too) that the spam is not worth the trouble of moderating. Could we switch it to a bounce?
[11:40] <Burgundavia> nixternal: post meeting, I have a few ideas I would love to chat with you about
[11:40] <Burgundavia> elkbuntu: you too
[11:41] <elkbuntu> sure


[03:34] <DaCeige> yes
[03:35] <DaCeige> they're fine... they stopped serving them for a short while... many of them come from waters that the oil spil didn't effect...
[03:35] <DaCeige> katrina had a worse effect on them (and the water containamition) than the oil prob


[06:24] <jelmer> hi gour
[06:42] <gour> jell jelmer
[06:42] <gour> *hello
[06:53] <jelmer> Gour: just replied to your bug
[06:56] <gour> jelmer: me too ;)
[10:41] <gour> it seems that loggerhead is not very actively developed. should one be worried i nregardto brz & publishing repos on private servers?
[11:26] <gour> jelmer: now i did re-run fast-import process and, indeed, /tmp was left with no space, but i wonder how is it that fast-import does consume 7.9G of space to import git repo of 20M?
[11:42] <mgz> gour: probably not super worried, though loggerhead isn't great
[11:42] <gour> mgz: what is recommended instead?
[11:43] <mgz> there isn't, which is part of the point
[11:44] <mgz> have looked at making very minimal read-only views sometimes, but it's just quite a lot of work to make a vcs web client thingy
[11:44] <gour> ok
[11:44] <gour> btw, what is correct scheme for fetching git repos from github with bzr-git?
[11:46] <gour> (via ssh)
[11:54] <gour> i get: brz: ERROR: No module named git.mapping when using something like: brz branch git://git@github.com:restic/restic.git
[12:04] <mgz> have you got dulwich installed?
[12:39] <gour> yes, dulwuch is installed
[12:41] <gour> *dulwich
[12:50] <jelmer> gour: for breezy there is lp:~jelmer/loggerhead/breezy
[12:50] <jelmer> gour: but please note that all of these are still very much in flux at the moment, so expect things to be broken
[12:51] <jelmer> gour: can you file a bug for the bn
[12:51] <jelmer> Brz-git issue?
[13:17] <gour> jelmer: i did install breezy via pip...
[13:18] <jelmer> gour: that probably explains it
[13:20] <gour> jelmer: should i still submit ticket?
[13:22] <gour> the point is that bzr/brz brings some nice stuff in comparison with fossil - support for git format and proper pre/post hooks. it also does have simple model and great ui...hg, is, imho, plagued with the need for too many extensions and, git is, well, git
[13:23] <gour> jelmer: what about fast-import using so much space?
[16:11] <vila> gour: do you need fast-import vs git clone + bzr git ?
[16:35] <gour> vila: i'd like to try both
[16:37] <vila> gour: right. If one fails, try the other :-)
[16:38] <vila> AFAIK fast-import is not maintained so I would bet less on it than on brz-git
[16:46] <gour> ok, but bzr-git does not work as well considering my pip-based install. otoh, i wonder if there is some performance/feature-penalty using git format instead of the native one?


[04:09] <shubuntu> hi, I might be offbase asking here, but any chance you guys know how to get rid of -Djava.library.path ? I'm trying to run a runnable jar in the form java -jar game.jar
[14:55] <persia> Team meeting in #ubuntu-meeting in 5 minutes
[15:01] <persia> Hmm.  #ubuntu-meeting still seems active.  Who do we have for the meeting today?
[15:02] <persia> Koon: slytherin: robilad: You're all common attendees.  Is there anything important enough that we should interrupt the desktop meeting?
[15:03] <Koon> hm.
[15:03] <Koon> we can do the meeting here
[15:03] <Koon> I would like to discuss maven support
[15:04] <persia> Well, only if there's enough people here to make it matter.  Otherwise, we'll have to make a lot of noise again, as attendance has been dropping off.
[15:04] <persia> robilad: slytherin: opinions?  thoughts?
[15:04] <Koon> slytherin is not here
[15:05] <robilad> we can do it here, really
[15:05] <robilad> the only problem is logs
[15:05] <robilad> is the channel logged?
[15:06] <persia> http://irclogs.ubuntu.com/2008/09/25/%23ubuntu-java.html
[15:06] <robilad> great, thank you, that will help with the nminutes
[15:06] <robilad> do we have an agenda for today?
[15:07] <persia> Only roadmap review.
[15:07] <robilad> and maven
[15:07] <Koon> well, that's part of the roadmap
[15:07] <robilad> right, ok, let's roll.
[15:08] <persia> Actually, in the meantime, #ubuntu-meeting cleared out.  We may as well go there in case any of the onlookers want to comment.
[15:08] <robilad> ok, let's do that.
[15:08] <persia> OK.


[03:36] <FourDollars> rbasak: Could you help to SRU https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=systemd?
[05:16] -queuebot:#ubuntu-release- New binary: bitshuffle [amd64] (eoan-proposed/universe) [0.3.5-1] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: golang-github-hansrodtang-randomcolor [amd64] (eoan-proposed/universe) [0.0~git20160512.d27108b-1] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: bitshuffle [i386] (eoan-proposed/universe) [0.3.5-1] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: golang-gopkg-go-playground-colors.v1 [amd64] (eoan-proposed/universe) [1.2.0-1] (no packageset)
[05:17] -queuebot:#ubuntu-release- New binary: bitshuffle [s390x] (eoan-proposed/universe) [0.3.5-1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New: accepted python-networkx [amd64] (eoan-proposed) [2.2-1ubuntu2]
[05:23] -queuebot:#ubuntu-release- New binary: bitshuffle [arm64] (eoan-proposed/universe) [0.3.5-1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: bitshuffle [armhf] (eoan-proposed/universe) [0.3.5-1] (no packageset)
[05:37] <FourDollars> rbasak: Hi, could you help to approve https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=systemd?
[07:26] <RikMills> vorlon: ack. I thought someone told me the opposite once, but fair enough
[07:58] <GunnarHj> Anybody who can override the sane-backends autopkgtest regression? Given all the overrides already there, it looks like somebody just forgot to do it for gscan2pdf/armhf:
[07:58] <GunnarHj> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#sane-backends
[08:02] <Laney> cpaelzer: looks like it timed out eventually
[08:08] <cpaelzer> oh
[08:08] <cpaelzer> did the instance go away
[08:08] <cpaelzer> Laney: what you gave me for debugging still is good for me
[08:08] <cpaelzer> if you can leafe it up
[08:08] <cpaelzer> leave
[08:09] <cpaelzer> I submitted an RFC patch and a lot of text upstream and I assume that when they get back to me I will need to continue checking/testing things on this instance
[08:09] <Laney> it's timed out here
[08:09] <Laney> if the instance is still there, cool
[08:09] <cpaelzer> yeah, so far it is
[08:10] <cpaelzer> but ppc64 cleanup is slow
[08:10] <cpaelzer> if it dies I might get in touch with you once there is feedback from upstream
[08:10] <Laney> don't think it'll go down by my action
[08:10] <Laney> just tell me when you're finished
[08:10] <Laney> good that it helped
[08:11] <cpaelzer> it did, thanks ++
[08:52] -queuebot:#ubuntu-release- New binary: libgdata [s390x] (eoan-proposed/main) [0.17.10-1~ubuntu1] (ubuntu-desktop)
[09:02] -queuebot:#ubuntu-release- New binary: libgdata [arm64] (eoan-proposed/main) [0.17.10-1~ubuntu1] (ubuntu-desktop)
[09:07] -queuebot:#ubuntu-release- New binary: libgdata [armhf] (eoan-proposed/main) [0.17.10-1~ubuntu1] (ubuntu-desktop)
[09:08] -queuebot:#ubuntu-release- New sync: llvm-toolchain-9 (eoan-proposed/primary) [1:9~+rc2-1~exp1]
[09:09] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-9 [sync] (eoan-proposed) [1:9~+rc2-1~exp1]
[09:09] -queuebot:#ubuntu-release- New: rejected llvm-toolchain-9 [sync] (eoan-proposed) [1:9~+rc2-1~exp1]
[09:15] -queuebot:#ubuntu-release- New binary: libgdata [amd64] (eoan-proposed/main) [0.17.10-1~ubuntu1] (ubuntu-desktop)
[09:18] -queuebot:#ubuntu-release- New binary: libgdata [i386] (eoan-proposed/main) [0.17.10-1~ubuntu1] (ubuntu-desktop)
[09:44] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (disco-proposed/main) [5.0.0-27.28] (core, kernel)
[09:49] -queuebot:#ubuntu-release- New binary: libgdata [ppc64el] (eoan-proposed/main) [0.17.10-1~ubuntu1] (ubuntu-desktop)
[10:01] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (disco-proposed/main) [5.0.0-27.28] (core, kernel)
[10:04] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (disco-proposed/main) [5.0.0-27.28] (core, kernel)
[10:08] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (disco-proposed) [5.0.0-27.28]
[10:08] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (disco-proposed) [5.0.0-27.28]
[10:08] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (disco-proposed) [5.0.0-27.28]
[10:24] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (disco-proposed/main) [5.0.0-1018.19] (core, kernel)
[10:25] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (disco-proposed/main) [5.0.0-1015.15] (core, kernel)
[10:33] -queuebot:#ubuntu-release- Unapproved: shadow (bionic-proposed/main) [1:4.5-1ubuntu2 => 1:4.5-1ubuntu2.1] (core)
[10:33] -queuebot:#ubuntu-release- Unapproved: shadow (disco-proposed/main) [1:4.5-1.1ubuntu2 => 1:4.5-1.1ubuntu2.1] (core)
[10:38] -queuebot:#ubuntu-release- Unapproved: shadow (xenial-proposed/main) [1:4.2-3.1ubuntu5.4 => 1:4.2-3.1ubuntu5.5] (core)
[10:41] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (disco-proposed) [5.0.0-1018.19]
[10:41] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (disco-proposed) [5.0.0-1015.15]
[12:49] -queuebot:#ubuntu-release- Unapproved: lttng-modules (bionic-proposed/universe) [2.10.5-1ubuntu1.3 => 2.10.5-1ubuntu1.3] (no packageset)
[13:04] -queuebot:#ubuntu-release- New: accepted libgdata [amd64] (eoan-proposed) [0.17.10-1~ubuntu1]
[13:04] -queuebot:#ubuntu-release- New: accepted libgdata [armhf] (eoan-proposed) [0.17.10-1~ubuntu1]
[13:04] -queuebot:#ubuntu-release- New: accepted libgdata [ppc64el] (eoan-proposed) [0.17.10-1~ubuntu1]
[13:04] -queuebot:#ubuntu-release- New: accepted libgdata [arm64] (eoan-proposed) [0.17.10-1~ubuntu1]
[13:04] -queuebot:#ubuntu-release- New: accepted libgdata [s390x] (eoan-proposed) [0.17.10-1~ubuntu1]
[13:04] -queuebot:#ubuntu-release- New: accepted libgdata [i386] (eoan-proposed) [0.17.10-1~ubuntu1]
[13:11] -queuebot:#ubuntu-release- Unapproved: mesa (bionic-proposed/main) [19.0.8-0ubuntu0~18.04.1 => 19.0.8-0ubuntu0~18.04.2] (core, xorg)
[14:29] -queuebot:#ubuntu-release- New binary: gcc-9 [i386] (eoan-proposed/main) [9.2.1-3ubuntu1] (core)
[15:26] <lordcirth> Did the root-on-ZFS installer option make it into 19.10? I don't see it in the daily ISO
[15:29] <xnox> lordcirth:  if it's on phoronix, it must be true =))))) right?! =)))))
[15:30] <xnox> lordcirth:  we have canary images that do install desktop root-on-zfs, but that's not the default image, but rather an experiment of the underlying tech
[15:30] <lordcirth> xnox, ah, ok. So it definitely won't be in the official 19.10 ISO?
[15:31] <xnox> lordcirth:  i made no forward looking statements =) we do time based releases, so we will know what's on the official 19.10 iso.... when it is published in 2019 October.
[15:31] <xnox> lordcirth:  nobody has a time-machine )
[15:31] <xnox> lordcirth:  nobody has a time-machine =)
[15:32] <xnox> lordcirth:  i only explained to you why you don't see it on the current daily iso.... i have no idea the status of that work or plans otherwise.
[15:32] <lordcirth> xnox, but feature freeze is tomorrow according to: https://wiki.ubuntu.com/EoanErmine/ReleaseSchedule
[15:33] <xnox> lordcirth:  feel free to play with the canary image off cdimage
[15:33] <lordcirth> So isn't that the deadline for it to be merged?
[15:33] <xnox> lordcirth:  and then there are FFe
[15:33] <xnox> lordcirth:  featurefreeze does not mean that development and merging features stops, simply that one needs more reviews and featurefreezeexcpetion approval.
[15:34] <lordcirth> Ok, I see.
[15:34] <xnox> lordcirth:  most flagship things we ever shipped, always landed post FF =)))))
[15:34] <lordcirth> lol
[15:34] <xnox> lordcirth:  see https://wiki.ubuntu.com/FreezeExceptionProcess
[15:54] <doko> apw: linux-oem (4.15.0-1050.57 to 4.15.0-1051.60)
[15:54] <doko> linux-oem-tools-4.15.0-1051/amd64 unsatisfiable Depends: libbinutils (<< 2.30.1)
[16:00] <apw> doko, damn
[16:06] <xnox> doko:  apw: argh
[16:07] <xnox> doko:  apw: did we not get rid of that dep, by statically linking before?!
[16:07] <xnox> or was it something else.......
[16:07] <apw> it was a bug in something which meant we were using it for demangling in perf, when we should not
[16:08] <xnox> you lost me with that sentence
[16:08]  * xnox smiles and nods
[16:09] <doko> apw, xnox: it's only in this variant
[16:09] <apw> doko, ok so ... i am going to guess we have a missing build-dep
[16:12] <doko> apw: is this a package built on bionic, and then copied?
[16:22] <xnox> doko:  yes
[16:22] <xnox> intentionally
[20:20] <apw> doko, yes, and it is broken if it is using binutils for anything linking wise
[20:39] <vorlon> Locutusofborg: uh so mdeslaur has closed LP: #1839596 as wontfix, and you uploaded https://launchpad.net/ubuntu/+source/imagemagick/8:<IP_ADDRESS>+dfsg-2.1ubuntu5 which reverted the security update; please reconcile this with the security team
[20:39] <ubot5`> Launchpad bug 1839596 in imagemagick (Ubuntu Eoan) "imagemagick 8:<IP_ADDRESS>+dfsg-2.1ubuntu3 broke reverse-deps" [Critical,Won't fix] https://launchpad.net/bugs/1839596
[20:40] <vorlon> (the package is stuck in -proposed anyway due to an MIR right now, but we definitely don't want the MIR to unstick it and have it land unexpectedly in eoan release)
[21:43] -queuebot:#ubuntu-release- New binary: llvm-toolchain-9 [amd64] (eoan-proposed/universe) [1:9~+rc2-1~exp1] (no packageset)
[21:45] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-9 [amd64] (eoan-proposed) [1:9~+rc2-1~exp1]
[22:21] -queuebot:#ubuntu-release- Unapproved: net-snmp (disco-proposed/main) [5.7.3+dfsg-5ubuntu1 => 5.7.3+dfsg-5ubuntu1.1] (desktop-core, ubuntu-server)
[22:23] -queuebot:#ubuntu-release- Unapproved: net-snmp (bionic-proposed/main) [5.7.3+dfsg-1.8ubuntu3.1 => 5.7.3+dfsg-1.8ubuntu3.2] (desktop-core, ubuntu-server)
[22:23] -queuebot:#ubuntu-release- Unapproved: net-snmp (xenial-proposed/main) [5.7.3+dfsg-1ubuntu4.2 => 5.7.3+dfsg-1ubuntu4.3] (desktop-core, ubuntu-server)


[11:51] <stub> wgrant: new rev of the db patch up, https://pastebin.canonical.com/114208/ contains the before/after schema diff from a dev db.
[11:53] <stub> I need a new pastebin bookmark. Lost colorization somewhere.
[11:54] <wgrant> stub: I don't speak 1970
[11:54] <wgrant> But let me see.
[11:56] <stub> fab
[12:21] <wgrant> stub: That looks pretty sensible, I think.
[12:35] <stub> I'll approve and land it now then and we can start the ball rolling next week. Its all standard until we get to the last step.
[12:37] <stub> Things to confirm on staging are if adding the new column with a FK reference needs to do an unnecessary scan, and similarly that final primary key.
[12:38] <stub> wgrant: Or do you want to do a proper review first?
[13:40] <wgrant> stub: I know those two things don't require full scans; I've done them each several times. So we're pretty safe except for the pg_attribute hackery, but that looks fine.
[13:40] <wgrant> stub: I'll have another look at the patch on Monday before you awake, if you don't mind. Just to ensure it makes sense with a fresh mind.
[13:41] <wgrant> cprov, cjwatson: Thanks for the reviews.
[13:42] <cprov> wgrant: sorry for letting them slip until today
[13:44] <wgrant> cprov: No worries. Could you please also look at https://code.launchpad.net/~wgrant/launchpad/htaccess-in-archiveroot/+merge/225783 and https://code.launchpad.net/~wgrant/launchpad/delete-archiveroot/+merge/225797 soonish? I expect to get moving on migrating production early next week, if possible.
[13:44] <cprov> wgrant: will do
[14:21] <cjohnston> wgrant: in Malta we discussed increasing the scan timeout by a minute or two to see if that would help with LP branches... did you have thoughts on the possibility of actually implementing that?