[01:24] <robert_ancell> ogasawara, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498667
[06:22] <pitti> Good morning
[06:28] <doko> pitti, promoting the python-systemd source (binaries were already in main), subscribed foundations-bugs
[06:28] <pitti> doko: ah, thanks; it got split out of the systemd source some time ago
[06:28] <pitti> doko: I subscribe myself as well
[06:57] <pitti> doko: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#python-setuptools → python-setuptools-whl still has rdepends, will that now built by another source or will virtualenv and python-pip stop using it?
[06:57] <pitti> doko: i. e. I wonder whether to NBS-remove it from -proposed to unstick it
[06:59] <doko> pitti, python-pip builds it on its own now
[07:00] <pitti> doko: oh! then I guess it's because the current version from -setuptools is higher (20.0-2) than the one now built from -pip (8.0.2-7)
[07:00] <doko> however virtualenv breaks tox tests and doesn't migrate
[07:00] <pitti> ah no, setuptools-whl vs. pip-whl
[07:01] <pitti> so virtualenv needs to drop its python-setuptools-whl dep
[07:02] <pitti> doko: tox is something for barry, I suppose
[07:02] <doko> yes
[07:02] <pitti> doko: I'll look at the apport failure with gdb, apparently it slightly changed behaviour
[07:02] <doko> ta, just wanted to have the new upstream there before FF
[07:03] <pitti> apparently a null pointer does not show "Cannot access memory at address 0x0" any more
[07:03] <doko> http://people.canonical.com/~ubuntu-archive/component-mismatches.svg  looks interesting ...
[07:03] <doko> so what should we do with php? including the 7.0 transition?
[07:09] <pitti> doko: server team started too look at it, but no followup to https://lists.ubuntu.com/archives/ubuntu-devel/2016-January/039117.html yet
[07:23] <cyphermox> good morning pitti, doko :)
[07:24] <pitti> salut cyphermox, comment ça va ?
[07:24] <cyphermox> ca va bien
[07:24] <cyphermox> il est tres tard :)
[07:24] <cyphermox> (or very early, depends on the viewpoint :)
[07:29] <highvoltage> late night ubiquity hacking eh? :)
[07:29] <cyphermox> ja
[07:29] <cyphermox> I was in the zone.
[07:29] <highvoltage> ^_^
[07:29] <cyphermox> except now too many ideas for refactoring that I can't do
[07:37] <dholbach> good morning
[08:12] <doko> cyphermox, working in parallel n libnftl?
[08:14] <doko> hmm, big endian targets fail
[08:20] <cyphermox> ugh
[08:24] <cyphermox> doko: want to fix the tests?
[08:25] <cyphermox> doko: or I'd disable them again and file a bug in debian :/
[08:25] <doko> cyphermox, who touched the package last? ;) no, just ignore the results on these targets then, if we can't fix it
[08:25] <cyphermox> ah, that too
[08:27] <cyphermox> it's not that we couldn't fix it, but that it would take time and I've been awake for too many hours
[09:12] <mardy> seb128: hi! I need some ubuntu/kde dev to look at bug 1451728, do you have some names handy?
[09:15] <seb128> mardy, hey, not really, maybe Laney or dholbach can help though
[09:16] <Laney> #kubuntu-devel ?
[09:17] <dholbach> yofel, ^ can you suggest somebody?
[09:17] <seb128> Laney, dholbach, thanks
[09:17]  * Laney would just go ask in there
[09:18] <mardy> Laney: good idea
[09:18] <dholbach> ^ debfx, Quintasan should maybe able to help with that as well - they're in ~kubuntu-dev
[09:18] <Quintasan> hm
[09:37] <flexiondotorg> Laney, morning.
[09:37] <Laney> hello
[09:37] <flexiondotorg> Laney, I've merged the changes we were discussing.
[09:37] <flexiondotorg> Laney, But have one issue.
[09:37] <flexiondotorg> Laney, an existing patch, in both the Debian and Ubuntu packages, is slightly modified in the updated Debian packaging.
[09:38] <flexiondotorg> I've read how to use quilt to update an existing patch, but I can't get the patch to update.
[09:38] <flexiondotorg> Laney, some help with that?
[09:40] <Laney> Can't we use the new version from Debian?
[09:41] <caribou> rbasak: just uploaded clamav with the (unsigned long) cast added & kept the armhf exception as it doesn't build on armhf w/o it
[09:41] <rbasak> caribou: OK. Thank you!
[09:42] <caribou> rbasak: trying to upload the git repo now
[09:44] <flexiondotorg> Laney, that is what I want to do.
[09:44] <Laney> Then there's no need to quilt update anything
[09:44] <Laney> or am I missing something?
[09:44] <flexiondotorg> But when I just copy the revised patch from Debian building the package says the a new changes.
[09:45] <flexiondotorg> *there are new changes.
[09:45] <Laney> did you add it to debian/patches/series?
[09:45] <Laney> or use quilt import to copy it in
[09:48] <flexiondotorg> Laney, The patch (by name) already exists in the existing Ubuntu and new Debian packaging. The new Debian package has a revised version of the patch.
[09:48] <flexiondotorg> I could not get quilt to import it.
[09:49] <flexiondotorg> I am not sure exactly how to use quilt to import.
[09:49] <flexiondotorg> I read about using quilt to update an existing patch but it didn't work.
[09:49] <Laney> Start from the Debian package and import the *Ubuntu* ones from our old package
[09:49] <Laney> You don't need to touch this new one
[09:49] <flexiondotorg> Ahhh.
[09:50] <flexiondotorg> So, I was going the other way. Taking the existing Ubuntu and adding the new bits form Debian.
[09:50] <flexiondotorg> Right. I'll try what you suggested. Thanks.
[09:53] <Laney> https://paste.debian.net/391176/
[09:53] <Laney> flexiondotorg: I would do something like that
[09:53] <Laney> then at the end you look at the debdiff to see if it is just the things we need to keep from the old package
[09:54] <Laney> (the version change and the patches?)
[09:54] <caribou> rbasak: do you think that I got the proper rights to upload to lpusdp: Y
[09:54] <caribou> ?
[09:54] <Laney> the epoch thing messes up merge-changelog - that's annoying
[09:54] <Laney> Maybe don't merge-changelog then
[09:54] <rbasak> caribou: you should do I think.
[09:54] <caribou> rbasak: I'll try
[09:55] <rbasak> caribou: you're a member of ~ubuntu-server-dev by virtue of being a core dev.
[10:00] <rbasak> cpaelzer: I noticed in your vblade merge that you renamed the Vcs field. This leads me to think - we can also put in our own Vcs field now, poitning to https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/vblade?h=ubuntu%2Fdevel for example now, since that's where we're maintaining it.
[10:00] <rbasak> cpaelzer: I don't think we need to bother until we have some tooling though.
[10:01] <rbasak> cpaelzer: perhaps we should have something to wrap update-maintainer and also both sets of Vcs-* changes and put that into ubuntu-git-tools?
[10:06] <cpaelzer> rbasak: I can surely add our VCS field
[10:07] <cpaelzer> do you want me to do that and resubmit, or just for the next upload?
[10:08] <rbasak> cpaelzer: next upload is fine.
[10:08] <rbasak> Not worth redoing
[10:08] <rbasak> cpaelzer: I'm also fine with delaying until we have tooling. No need to spend extra effort until then IMHO.
[10:19] <mardy> Laney: sorry to bother you again :-) I've filed bug 1546020 and attached a patch, but AFAIU the package is maintained in debian; how should I proceed?
[10:20] <caribou> rbasak: https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/clamav
[10:20] <caribou> works fine !
[10:23] <Laney> mardy: You could send the patch to the Debian BTS https://www.debian.org/Bugs/Reporting
[10:26] <seb128> Laney, mardy, Debian doesn't ship that apparmor profile so it doesn't make sense to forward the patch
[10:27] <seb128> we could try to get them to include the profile though
[10:27] <Laney> ok I didn't check
[10:27] <seb128> urg sorry
[10:27] <seb128> they do
[10:27] <Laney> what
[10:27] <seb128> I looked at the wrong dir
[10:27] <seb128> http://anonscm.debian.org/cgit/pkg-telepathy/telepathy-mission-control-5.git/tree/debian/apparmor-profile
[10:27] <Laney> haha
[10:27] <seb128> bigon added it in decembre
[10:29] <rbasak> caribou: thanks!
[10:29] <rbasak> caribou: a couple of notes for next time
[10:30] <rbasak> caribou: I'm trying to keep the imports clean parent-wise. So "Import version 0.99+dfsg-1" shouldn't have "Import version 0.98.7+dfsg-0ubuntu5" as its parent, since it doesn't have any connection to that.
[10:31] <rbasak> Instead it should be an orphan commit in this case, or have a parent of the previous Debian import next time.
[10:31] <rbasak> caribou: with that, I'm trying to keep the "debian/sid" branch pointer pointing to the latest Debian import.
[10:31] <caribou> rbasak: ok, noted
[10:46] <caribou> rbasak: another question about your workflow :
[10:47] <caribou> rbasak: what I just pushed in the ubuntu/devel branch only has one tag; all the working tags are in my lpmep: personal branch
[10:47] <caribou> how is the next person doing the merge going to get the working environment ?
[10:56] <mardy> Laney, seb128: so the correct thing to do is to open a bug in the debian BTS?
[10:56] <rbasak> caribou: please see https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/logwatch as an example of what I intend.
[10:56] <caribou> rbasak: k
[10:56] <rbasak> caribou: when a new logwatch arrives in sid, either a sponsor or a future automatic importer will dsc-commit the new Debian upload to the debian/sid branch and tag it.
[10:57] <Laney> mardy: if you want to forward something there then yes
[10:57] <Laney> mardy: could also be uploaded in ubuntu of course if necessary
[10:59] <caribou> rbasak: ok, I see
[11:00] <caribou> rbasak: In my case, I could push a new debian/sid branch that points to the new/debian tag of my git-dsc-commit import ?
[11:01] <rbasak> caribou: you'd check out the debian/sid branch, git-dsc-commit the new Debian upload, tag it import/<version> instead of just <version> (the tooling needs a bit of tweaking here) then push the branch back with the tag.
[11:02] <rbasak> caribou: then you'd check out the ubuntu/devel branch, branch that as local "logical" branch or something, and rebase to squash to come up with the logical tag.
[11:02] <rbasak> caribou: the logical/<version> tag that is.
[11:02] <rbasak> caribou: you'd be able to push or otherwise share the logical/<version> tag (without pushing the local logical branch) at this stage.
[11:03] <rbasak> caribou: then you'd branch the logical/<version> tag as a local "merge" branch, and rebase --onto debian/sid.
[11:03] <rbasak> caribou: then you have the same MP capability as current.
[11:03] <rbasak> A complication is that others might upload without pushing to ubuntu/devel, so we'd need to dsc-commit to catch that up too if necessary.
[11:03] <caribou> ok, I'll guess it'll become clearer the next time
[11:04] <caribou> rbasak: that will happen with SRU since debdiffs are used most of the time
[11:05] <rbasak> Yeah
[11:05] <rbasak> Eventually LP will deprecate dput and require a git push instead. Then that'll go away :)
[11:06] <caribou> Laney: thanks for the backport !
[11:37] <flexiondotorg> Laney, could you cast an eye over this diff please? - http://paste.ubuntu.com/15090421/
[11:38] <flexiondotorg> Laney, I haven't used merge-changelog in this diff.
[11:38] <flexiondotorg> If is looks good to you, is I bug with this debdiff attached the correct way to proceed?
[11:39] <Laney> flexiondotorg: Fix the versions in the .symbols file to have the epoch
[11:39] <flexiondotorg> Wilco
[11:39] <Laney> Say which changes you kept in the changelog (Merge with Debian. Remaining Ubuntu changes - a - b - c)
[11:39] <Laney> and please give the diff on top of Debian too
[11:43] <flexiondotorg> OK
[11:43] <flexiondotorg> I've found another version requiring epoch in debian/control too.
[11:51] <flexiondotorg> Laney, This the the merge from Debian diff - http://paste.ubuntu.com/15090488/
[11:51] <Laney> flexiondotorg: lies
[11:51] <Laney> that's a diff from the old ubuntu version
[11:52] <Laney> s/old/current/
[11:52] <flexiondotorg> Ag.
[11:52] <flexiondotorg> Sec...
[11:55] <flexiondotorg> Laney, Bad explanation from me.
[11:55] <flexiondotorg> This is the intended merge - http://paste.ubuntu.com/15090488/
[11:56] <flexiondotorg> This is the comparison with current Debian - http://paste.ubuntu.com/15090498/
[11:57] <Laney> flexiondotorg: cool, looks plausible right now
[11:57] <Laney> toss them on a sponsnoring bug?
[11:58] <flexiondotorg> Both diff in the bug?
[12:00] <Laney> ye
[12:01]  * flexiondotorg is doing it...
[12:07] <flexiondotorg> Laney, https://bugs.launchpad.net/ubuntu/+source/libwnck/+bug/1546066
[12:07] <Laney> ty
[12:07] <Laney> I am supposed to sponsor later (although I've got to leave early), will try to look
[12:10] <flexiondotorg> Laney, many thanks for your help and tutoring.
[12:10] <flexiondotorg> I really appreciate it.
[12:25] <Laney> flexiondotorg: no worries
[12:37] <inaddy> slangasek: you mentioned that instead of merging/sync mstflint for trusty we should create a mstflint4 package (probably universe). what is the best procedure for this ? to follow the request for inclusion (as described in [MIR] procedure) ? creating a PPA with full source + bzr branch ?
[12:38] <inaddy> (LP: #1470167) btw. i was working on SRU instead of a request for inclusion (probably the needed step now)
[12:39] <inaddy> hum. slangasek is away, if anyone else can help ^
[12:39] <inaddy> caribou: ^
[12:45] <rbasak> inaddy: an uploader will be able to upload any source package. I suggest you follow normal SRU procedure and link to a source package upload from the bug somehow. A PPA would be fine.
[12:45] <rbasak> (and detail the exception in the bug)
[12:46] <inaddy> rbasak: cool. will do. tks
[13:05] <rbasak> kickinz1: the merge target is meant to be ubuntu/devel, not debian/sid. Then when the uploader uploads and pushes to ubuntu/devel, the MP conveniently notices.
[13:06] <kickinz1> rbasak, sorry.
[13:06] <kickinz1> rbasak, You want me to redo the MP?
[13:07] <rbasak> No, it's fine.
[13:08] <rbasak> kickinz1: also, I expect you to have a tag called logical/1_2.10.1-1ubuntu1
[13:09] <rbasak> kickinz1: is this what you called logical/ubuntu-2.10.1-1?
[13:09] <kickinz1> rbasak, yes.
[13:09] <rbasak> OK
[13:23] <coreycb> bdmurray, I commented on bug 1318721
[13:29] <mdeslaur> @pilot in
[13:37] <pitti> cd
[13:38] <didrocks> ~
[13:39] <pitti> didrocks: ~, sweet ~!
[13:39]  * didrocks hugs pitti
[13:39]  * pitti hugs didrocks back
[14:11] <Odd_Bloke> xnox: We just saw "sosreport : Depends: python3.4:any but it is not installable" in a livefs build for s390x cloud images (but other arches seem to be happy); any ideas?
[14:32] <xnox> Odd_Bloke, it's weird as nothing should depend on python3.4 anymore.
[14:33] <xnox> Odd_Bloke, yet it clearly is.
[14:33] <xnox> Odd_Bloke, let me analyze the scope here.
[14:33] <jdstrand> pitti: re apparmor merge-- sure, we'll figure it out. not sure if I personally will do it, but we can get someone on it
[14:41] <xnox> Odd_Bloke, we have a few http://paste.ubuntu.com/15091848/
[14:41] <xnox> doko, pre-mature removal of python3.4 ^
[14:50] <xnox> actually less.
[14:51] <xnox> doko, Odd_Bloke: uploaded 7 packages, which should resolve python3.4, or lack of, for good.
[14:52] <Odd_Bloke> xnox: Thanks. :)
[14:55] <caribou> Does someone have a few spare cycles to review the mstflint -> mstflint4 package creation for me ? Rather simple leaf package
[14:55] <caribou> http://paste.ubuntu.com/15092039/
[14:56] <rharper> rbasak: hoping to wrap up the strongswan stuff today but I've a general question;  as we've been testing the proposed package we've identified a number of fixes and some features that are helpful;  should I leave those to the side of the merge and apply them after the merge or is it OK to bring in the additional bug fixes and ubuntu changes in the merge itself (as part of the new ubuntu delta) ?
[14:56] <doko> xnox, ta, reverse-depends didn't show any ...
[14:56] <xnox> doko, yeah, weird. Usually things like that are picked up by the transition tracker, but that too has false positives/negatives.
[14:57] <xnox> doko, anyway, i've dputed the remaining 7 packages, and will rerun the chdist test ones they migrate, across all 7 arches, to check that we are all good.
[14:57] <doko> the only one I saw was sigil, but a recommends only
[14:57] <xnox> at first i have suspected an arch-skew (given that s390x was a bootstrapped one)
[15:00] <rbasak> rharper: up to you. It's fine to add them to the merge upload if you wish. Or do it later if you think it's unnecessarily blocking the merge. We probably shouldn't regress anything big that is known in the merge upload though.
[15:00] <rharper> rbasak: ok; I don't think anything is blocking; they've all been easy fixes or updates.
[15:04] <rbasak> rharper: OK that's fine - just add extra commits and extra top level bullet points in d/changelog for each change.
[15:05] <ginggs> doko, xnox: one i happened to see on that list is mine, python-ase, FTBFS with new numpy
[15:05] <rbasak> (d/changelog probably via git-reconstruct-changelog)
[15:05] <xnox> ginggs, oh.
[15:05] <xnox> ginggs, well.
[15:05]  * rbasak wonders if that should be renamed to git-construct-changelog as it's not really redoing anything
[15:06] <xnox> ginggs, if it's uninstallable and FTBFS we will need to demote it to -proposed, such that it is not uninstallable in release.
[15:06] <ginggs> xnox: remove it if you must, i'll upload it when it is fixed (waiting for response from upstream)
[15:06] <xnox> until fixesd.
[15:06] <ginggs> xnox: ack
[15:06] <xnox> ginggs, demote to proposed is the new "remove from release"
[15:07] <xnox> doko, do you have powers to demote-to-proposed python-ase?
[15:07] <xnox> there is a script to do that in archive-tools repository i think.
[15:08] <rharper> rbasak: thanks
[15:17] <mdeslaur> @pilot out
[15:20] <doko> xnox, gpaw still depends on it
[15:24] <xnox> doko, it's python2 only?
[15:24] <doko> xnox, both demoted
[15:26] <xnox> doko, i don't see gpaw using python3 at all. So if it's demoted it will probably just migrate back. https://launchpadlibrarian.net/236788889/buildlog_ubuntu-xenial-amd64.gpaw_0.11.0.13004-3build2_BUILDING.txt.gz
[15:27] <xnox> it build-depends on python3 but i don't see it building python3 anything.
[15:29] <damascene> hi, this packagefonts-hosny-amiri have been updated but I find the old version in 16.04 https://github.com/khaledhosny/amiri-font/releases
[15:29] <damascene> fonts-hosny-amiri how to get it in 16.04 before feature freeze?
[15:30] <rharper> question on FFEs since it's that time and I've never filed one;  if there is an existing merge bug, would I just add the justification to the existing merge bug or file a new bug just for the FFE and reference the merge bug ?
[15:32] <ginggs> rharper: just change the bug title
[15:32] <rharper> ginggs: ok
[15:34] <ginggs> rharper: and edit the bug description to include the justification
[15:34] <rharper> gotcha; no need for a new bug, update title and include the justification .  Thanks!
[15:58] <seb128> pitti, can you override the libreoffice-l10n autopkg as well? it seems to still be grumpy about libreoffice which blocks libreoffice itself because they need to go together
[16:04] <Laney> vila: flexiondotorg: I didn't make it to sponsoring today, sorry - will start with that tomorrow so I don't get on to anything else
[16:04]  * Laney waves
[16:06] <vila> Laney: looks like mdeslaur did ! Thanks to both !
[16:07] <smoser> pitti, around ?
[16:18] <pitti> seb128: hm, I actually did, but britney doesn't get along with hints with multiple versions apparently; I'll apply a +1 force then :)
[16:18] <pitti> smoser: Im' back
[16:19] <smoser> pitti, so the open-iscsi... you thought our delta had all been taken into debian ?
[16:19] <seb128> pitti, thanks
[16:19] <pitti> smoser: yes, except the autopkgtest
[16:19] <smoser> such that we should re-sync with much smaller delta
[16:20] <smoser> but sync woudl still be necessary, right ? for the auto pkg test
[16:20] <smoser> annoying that we have to carry package delta for that, but seemingly fairly easiliy synced if that is in fact it
[16:21] <pitti> smoser: right, "re-merge"
[16:21] <smoser> ok. i will look to see if i can't get that merged.
[16:22] <Odd_Bloke> Are there any plans to replace bzr packaging branches (i.e. UDD) with git equivalents?
[16:23] <cjwatson> Odd_Bloke: https://lists.ubuntu.com/archives/ubuntu-devel/2015-November/039010.html   but not much in the way of updates since then unfortunately
[16:24] <pitti> Odd_Bloke: note that it's fairly easy to create your own (or better yet, branch from Debian's) for packages you work on often
[16:25] <pitti> Odd_Bloke: I find that the vast majority of packages I happen to look at in Debian already have a git, and that will always be better than some synthetically imported one
[16:25] <Odd_Bloke> cjwatson: Aha, cool, I thought I had seen something about it.  Any sense of when it might end up happening, or is it a someday thing for now?
[16:25] <pitti> it's most convenient to have an ubuntu git branch in the Debian git repo, or at least mirror it in LP
[16:25] <cjwatson> Odd_Bloke: I really hope to manage it this year but realistically can't promise anything definite
[16:26] <pitti> but if not, "gbp import-dsc foo.dsc" et voilà :)
[16:26] <rbasak> Odd_Bloke: the server team is doing it now. We'll have an interim importer for packages we follow soon.
[16:26] <rbasak> (not using gbp import-dsc as not doing an upstream/debian split)
[16:26] <Odd_Bloke> cjwatson: Ack; we just didn't want to spend time working on something that would be easier with it if it were right around the corner. :)
[16:27] <rbasak> Odd_Bloke: once we have the importer, perhaps we can track your packages for you too.
[16:27] <pitti> Odd_Bloke: so the thing you want to work on has no VCS in debian?
[16:27] <Odd_Bloke> pitti: The thing we want is livecd-rootfs. :)
[16:27] <pitti> asrcs-Bzr: http://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk
[16:28] <pitti> eek, s/ssrc/V/
[16:28] <pitti> Odd_Bloke: perhaps it's  time to convert that to git and use that from now on?
[16:28] <Odd_Bloke> We have been using that.
[16:29] <pitti> then you have all the history, and not just the coarse-grained one from auto-imports
[16:29] <Odd_Bloke> But ran in to problems for two reasons: (a) a refactor happened over multiple commits (without a release, so not an actual problem) and we started a build in the middle, breaking our images.
[16:29] <pitti> I don't want to diminish cjwatson's work, but I've never found such synthetic VCSes particularly useful
[16:29] <Odd_Bloke> (b) once xenial is released, we will want to track xenial's livecd-rootfs for xenial.
[16:30] <pitti> Odd_Bloke: right, so for (b) you'd branch off /xenial (instad of /trunk) at some appropriate point, and for (a) you'd use a branch as well
[16:30] <Odd_Bloke> (The use-case here is building a private livecd-rootfs package which contains private bits for partner clouds; we want to build on top of whatever the latest _released_ version of livecd-rootfs package is in a specific suite)
[16:30] <pitti> (in both bzr and git)
[16:30] <cjwatson> pitti: dgit actually looks like it could be a much better compromise there than UDD ever was
[16:31] <Odd_Bloke> pitti: But /xenial branches weren't created a la cjwatson's email above (right?).
[16:31] <cjwatson> pitti: because it's easier to stitch in history from different places, and we don't have the file-id problem
[16:31] <pitti> Odd_Bloke: the above Vcs-Bzr: is a manually maintained "real" branch, it's got nothing to do with UDD or the above Launchpad work
[16:31] <cjwatson> I tend to agree we should just convert livecd-rootfs to git and be done
[16:31] <pitti> cjwatson: yeah, true
[16:31] <pitti> I guess it'd be polite to ask ogra_ if he's okay with git migration
[16:32] <pitti> as he's working on it a lot, and it's also his birthday :)
[16:32] <pitti> (so don't make him grumpy today)
[16:32] <ogra_> eek, git ?!?
[16:32] <Odd_Bloke> pitti: Ack, but if I s/trunk/wily/ that URL, there isn't anything there.
[16:32] <pitti> but it's hard to avoid git these days :)
[16:32] <rbasak> pitti: synthetic VCS is better than no VCS, which is the situation with many Ubuntu-deltified packages right now.
[16:32] <ogra_> pitti, up to now i managed to :)
[16:32] <pitti> Odd_Bloke: right, as long as nobody makes those branches they won't :) but easy enough to create it once you need it, by branching off the tag corresponding to the wily version
[16:32] <pitti> ogra_: wow, congrats
[16:32] <rbasak> That's why an importer is useful. As long as Ubuntu uploaders aren't required to commit to VCS, we need an importer if we want to use VCS tooling to help us with our work.
[16:33] <Odd_Bloke> Yeah, this ^
[16:33] <pitti> rbasak: right, but branching off Debian's VCS is still better IMHO :)
[16:33] <pitti> right for the "catch up with dput"
[16:33] <rbasak> pitti: unfortunately that's really tricky to do reliably, _and_ have a single workflow across all the packages we look after.
[16:33] <ogra_> pitti, i dont really want to be the blocker though ...
[16:34] <pitti> well, I just wanted to mention gbp import-dsc, which might speed things up until this lands in LP
[16:34] <cjwatson> rbasak: you could probably use bits of dgit as the importer
[16:34] <pitti> or that ^
[16:34] <rbasak> How do we match up the Debian VCS commit with a Debian upload, for example. What if a Debian NMU means that the VCS is missing an upload?
[16:34] <rbasak> Etc.
[16:34] <rbasak> nacc: ^
[16:34] <cjwatson> since its raison d'être is doing repeatable imports
[16:34] <pitti> ogra_: I'm truly amazed that you managed to stay away from git until now :)
[16:35] <rbasak> Currently we're using https://github.com/basak/ubuntu-git-tools/blob/master/git-dsc-commit, which just blats a .dsc as a commit.
[16:35] <cjwatson> rbasak: the point of dgit for that is that it doesn't matter, it'll construct an appropriate commit on the fly
[16:35] <ogra_> pitti, well, beyond git clone indeed ... the majority of stuff i work on is still using bzr ... and upstreams i work with are often enough fine with patches :)
[16:35] <cjwatson> in a deterministic way so that if different people do it they get the same answer
[16:35] <rbasak> That sounds neat.
[16:36] <nacc> dgit does look handy
[16:37] <smoser> Trevinho, just curious... bug 1521302 is terribly annoying to me.  do you think this is something fixed sometime soon ?
[16:37] <Trevinho> smoser: yes, but it's something we can delay for now...
[16:38] <Trevinho> willcooke: can you please add that to our list ^
[16:38] <smoser> is there some work around ?
[16:39] <Trevinho> smoser: not that I know, maybe you can force with soemthing like wnckprop or other scripts, but... Nothing inside compiz AFAIK
[16:41] <willcooke> hrm, odd.  Doesn't do it it 14.04, does in 16.04
[16:41] <willcooke> I'll add it to the backlog now
[16:41] <smoser> thanks.
[16:45] <Odd_Bloke> rbasak: What time frame are you looking at for your importer work?
[16:46] <rbasak> nacc: ^
[16:46] <nacc> Odd_Bloke: i'll hopefully get it done/working next week
[16:47] <Odd_Bloke> OK, nice.
[17:00] <pitti> stgraber, kees, infinity, mdeslaur: TB meeting now? (or not?)
[17:01] <mdeslaur> pitti: thanks
[17:01] <stgraber> cyphermox: hey, how am I supposed to talk to for NM nowadays?
[17:02] <stgraber> just installed a clean Xenial box and opened the connection editor, I see lxcbr0 in there...
[17:02] <stgraber> I thought we made it so that NM would stop messing with this...
[17:03] <stgraber> doesn't look like it actually generated any config in /etc/NetworkManager but it's one click away from breaking lxcbr0 and having confused users waste hours of my team's time again...
[17:03] <stgraber> (did I mention I hate Network Manager)
[17:03] <cyphermox> I suppose it's still me
[17:05] <cyphermox> stgraber: NM will always show the devices in nmcli
[17:05] <cyphermox> or in the connection editor device list for that matter
[17:05] <cyphermox> that doesn't mean nm-applet will show anything
[17:07] <smoser> infinity, around ?
[17:07] <smoser> we're seeing regressed behavior (tests started failing) https://platform-qa-jenkins.ubuntu.com/user/smoser/my-views/view/trusty%20amd64/job/ubuntu-trusty-server-amd64-smoke-minimal-virtual/
[17:07] <smoser> that seem to match up time-wise with at least your debian-installer upload https://lists.ubuntu.com/archives/trusty-changes/2016-February/021231.html
[17:08] <smoser> the point of that test is to install linux-virtual and then verifiy that the installed system is generally smaller (and that it has linux-virtual) installed.
[17:08] <stgraber> cyphermox: and there's still no magic .d directory I can have lxc dump a file into to make sure our stuff never shows in NM is there?
[17:09] <infinity> smoser: What log am I looking at?
[17:09] <cyphermox> sure there is
[17:09] <stgraber> cyphermox: last I checked there was something close to it, but any key set in there would fully overwrite the previous value
[17:09] <cyphermox> stgraber: /etc/NetworkManager/conf.d
[17:09] <stgraber> cyphermox: so if I was to ship one with the lxc and lxd package, the lxd one (alphabetical order) would override the key set by the lxc one, not append to it
[17:09] <cyphermox> *shrugs(
[17:09] <stgraber> right, that's the broken thing I looked at last time
[17:09] <smoser> that test above (platform-qa-jenkins) . tries to seed installation of linux-virtual metapackage via:
[17:10] <cyphermox> I don't think you can have NM never show the devices
[17:10] <smoser>  d-i base-installer/kernel/override-image string linux-virtual
[17:10] <cyphermox> it's doing what it's supposed to do, let you handle network devices. we already go out of our way to make sure people can't break lxc by clicking in nm-applet
[17:10] <smoser> and then basically verifiesd that it got installed. it did not when that test ran with media
[17:10] <smoser>  Ubuntu-Server 14.04.4 LTS Trusty Tahr - Beta amd64 (20160212)
[17:10] <smoser> err.. ^ it passed
[17:10] <cyphermox> stgraber: but it should still show devices, just like ifconfig should.
[17:10] <smoser> failed with: Ubuntu-Server 14.04.4 LTS Trusty Tahr - Beta amd64 (20160212)
[17:11] <cyphermox> stgraber: ie. if someone goes out of their way to do something stupid, too bad.
[17:11] <stgraber> cyphermox: I seem to remember I tried using keyfile with unmanaged-devices and it kinda worked except that it couldn't be appended to, just overriden
[17:11] <cyphermox> it's already unmanaged
[17:12] <cyphermox> we patched that in
[17:12] <stgraber> ok, kinda weird that unmanaged means that NM still lets you manage it though :)
[17:12] <cyphermox> stgraber: unmanaged means NM won't touch it automatically
[17:13] <stgraber> anyway, I guess we'll see how things turn out with 16.04, but I'm getting 2-3 reports of broken lxcbr0 a day due to NM and I'm getting sick of it
[17:13] <cyphermox> stgraber: you can still poke things if you really wanted to
[17:13] <stgraber> most of them get fixed by asking the user to "grep -r lxcbr0 /etc/NetworkManager" and remove any file that turns up
[17:13] <infinity> smoser: Okay, but I'm not seeing a log that tells me what happened.
[17:13] <cyphermox> I think we should take another look at the reports, and make sure it's not people doing something that should be pretty obvious one shouldn't do
[17:14] <smoser> infinity, well, yeah, they're burried in the artifcats
[17:14] <cyphermox> stgraber: that sounds a lot like someone going in to edit random things without knowing what they're for
[17:14] <stgraber> there's also still a race somewhere in there where NM yanks the IPv4 address from our bridge at cration time. We fixed the most obvious one of those back in Wily (was hitting 90% of the time) but there still seems to be one (hits < 1%), still trying to get some kind of reproducer though...
[17:15] <stgraber> cyphermox: my best guess so far si: connection editor -> edit lxcbr0 -> don't change anything -> save
[17:15] <cyphermox> stgraber: I'm not against apply a patch to hide things if the patch makes sense and isn't going to break stuff, but people can already break things by editing random files
[17:15] <stgraber> which isn't obviously wrong, they didn't change anything, they just went to look at it clicked save instead of close
[17:16] <cyphermox> right
[17:16] <cyphermox> I would suggest filing bugs upstream for some of these
[17:17] <infinity> smoser: Right, can you tell me what bug you're reporting?  "I have a test that does a thing and my test fails" isn't a bug, unless you can tell me *why* your test is failing.
[17:18] <stgraber> yeah, will look into that at some point after FF I guess, or just distro patch nm-connection-editor and the gnome control center components to hide unmanaged devices too (so they match nm-applet)
[17:18] <smoser> infinity, well, we pre-seed installation of linux-virtual with:
[17:18] <cyphermox> stgraber: well, that won't work
[17:18] <smoser> infinity, well, we pre-seed installation of linux-virtual with:
[17:18] <smoser>  d-i base-installer/kernel/override-image string linux-virtual
[17:18] <stgraber> cyphermox: btw, any chance of getting 1.1 in xenial? I'd really like the 1.1 openvpn plugin, seems to fix a ton of stuff compared to our broken 0.9* version
[17:18] <cyphermox> stgraber: connections are separate from devices
[17:19] <stgraber> cyphermox: how was it done in the applet then?
[17:19] <smoser> that used to result in installation of linux-virtual and then durint a stable release, that behavior changed.
[17:19] <cyphermox> stgraber: per-device, not connections
[17:19] <cyphermox> stgraber: I suppose what could be done is to explicitly hide connections that start in /lxc.*/
[17:20] <smoser> i'm not 100% certain that the 'base-installer/kernel/override-image' actually did anything (rather than something realizing we're "virtual" and installing -virtual magically) , but even without that... we changed behavior in a stable release.
[17:20] <xnox> cyphermox, couldn't udev rules, or some such set variables on the NIC to hint to network manager "don't touch this"?
[17:20] <cyphermox> but even that is bound to fail at some point, people might actually want to create a connection named "lxc" for some other reason
[17:20] <cyphermox> xnox: devices are already being unmanaged, that is already fine.
[17:20] <cyphermox> xnox: I think there is a udev rule, but this isn't the problem
[17:20] <xnox> cyphermox, that way, e.g. autocreated/managed things can do "NETWORK_MANAGER_HIDE_ME_HARDER=1" =)
[17:21] <cyphermox> stgraber: I suppose we could probably already update the VPN plugins
[17:22] <smoser> i dont really understand how the change i'm pointing to there could have caused this by looking at its diff, but something worked on the 20160212 and started failing on 20160215.
[17:22] <cyphermox> stgraber: as for NM 1.1, it's always a huge thing to update... I'll look a bit see if that could go with a FFE
[17:22] <cyphermox> morphis: did you look at updating NM yet?
[17:25] <stgraber> cyphermox: I did try building the 1.1 openvpn plugin last night against current xenial and it wasn't very happy with our NM version. May be doable with more work though.
[17:26] <cyphermox> err
[17:26] <cyphermox> there isn't a 1.1
[17:26] <cyphermox> 1.0.8?
[17:27] <stgraber> Debian has NM 1.1.90-6 and nm-openvpn 1.1.90-3
[17:27] <stgraber> I tried building the latter against Ubuntu's NM 1.0.4
[17:28] <cyphermox> ok that might be 1.2-beta1 I suppose
[17:28] <cyphermox> yup
[17:28] <cyphermox> *sigh*
[17:32] <stgraber> oh, why didn't they call it that? kinda confusing when looking at the version number :)
[17:32] <cyphermox> yeah
[17:32] <cyphermox> that was upstream's doing
[17:32] <cyphermox> I think the minimum version is wrong, this should already build
[17:33]  * cyphermox tries updating n-m-openvpn
[17:37] <Odd_Bloke> nacc: rbasak: Would your importer give us a trusty tag/branch that would point at what's released in trusty?  (Or s/trusty/trusty-updates/g maybe)
[17:37] <nacc> Odd_Bloke: initially it's only targetted at merges, but it'd be relatively easy to do that, i think
[17:38] <Odd_Bloke> nacc: OK, cool.
[17:43] <cyphermox> stgraber: ok, yeah, we'll need to update just about everything for it to work
[17:43] <infinity> smoser: The difference between the working one and the failing one is that the failing one doesn't have archive.ubuntu.com available.
[17:44] <smoser> where'd you see that infinity  ?
[17:44] <xnox> doko, python3.4 rebuilds appear to have all migrated and/or you demoted borked things, so release is looking good now.
[17:44] <doko> ta
[17:45] <infinity> smoser: Search both syslogs for configure_apt and see the update there hits archive *and* the CD on the working one, and only the CD on the failing one.
[17:45] <infinity> Now to sort out why that might be...
[17:49] <smoser> hm.. so possibly related, i started seeing very bad network performance on a system we use for qa tests.
[17:49] <smoser> where download of a 18M kernel package would take > 180 seconds
[17:49] <infinity> smoser: Probably doesn't relate, but I can't see why this would break either.  We didn't change any of these bits.
[17:49]  * infinity runs a test here.
[17:50] <smoser> infinity, thanks. i'll leave you to poke at it
[17:54] <rbasak> Odd_Bloke: yeah, our scheme will allow us to do that when the importer can support it. Not an initial goal, but I don't imagine it'll be particularly hard to get the importer to do that too when it's ready, since it'd use mostly the same code and logic.
[17:55] <Odd_Bloke> rbasak: Ack.  Thanks for all the info!  (You too, nacc :)
[18:14] <Emanuel> Hi
[18:15] <Emanuel> There are only 2 days left https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule until https://wiki.ubuntu.com/FeatureFreeze
[18:16] <Emanuel> And no one step up to solve the lz4 situation.
[18:17] <Emanuel> bug 1531923
[18:22] <rbasak> Emanuel: MIRs aren't dependent on FF. A new apt release might be though.
[18:23] <xnox> tedg, you did read the docs prior to like hacking your own unique solution right?
[18:23] <xnox> tedg, looks like https://wiki.ubuntu.com/citrain/LandingProcess#Dual-landing_and_handling_symbols documents how to do dual-landing symbols et.al.
[18:27] <tedg> xnox: Eh, I just went with shlibs for everything. After I found the Debian docs for C++ and symbols that basically said "give up and use shlibs"
[18:27] <Emanuel> rbasak: lz4 is in debian, how hard cant it be to import ?
[18:28] <juliank> Emanuel: It's waiting for sarnold's security review
[18:29] <tedg> After the abigail stuff is done for scopes-api I'll probably steal that as a in tree test.
[18:29] <juliank> It's not only APT that is affected, squashfs-tools has not been updated since October
[18:31] <rbasak> Emanuel: it is imported. It's just not in main.
[18:31] <dasjoe> cking: cmiller tries to fix grub not finding a zpool's devices by adding some script to search for pools. I proposed to parse zdb's output, this may be of interest to you: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727/comments/15
[18:34] <juliank> It's hilarious that the inclusion of lz4 takes such a long time, given the modified copy/copies swirling around in main already (at least one in Linux)
[18:35] <dasjoe> (zfs comes with lz4, too)
[18:36] <juliank> mvo: It's feature freeze and the lz4 MIR request is still not through, meaning APT 1.2 continues to wait in proposed :(
[18:37] <juliank> 1.2.3 now detects I/O errors in rred
[18:37] <mvo> juliank: nice!
[18:38] <mvo> juliank: I'm at a sprint right now, but I will poke some people about the lz4 MIR request
[19:37] <Emanuel> https://github.com/fjserna/CVE-2015-7547/pull/1
[19:38] <Emanuel> https://github.com/fjserna/CVE-2015-7547/pull/1
[19:39] <sladen> CVEs are going to need 5 digits shortly
[19:40] <Emanuel> https://twitter.com/RichFelker
[19:40] <sarnold> in fact mitre plans on issuing a CVE with five digits potentially before it's needed just to ensure that tooling has adapted
[19:40] <Emanuel> just read it
[19:41] <sladen> https://googleonlinesecurity.blogspot.com/2016/02/cve-2015-7547-glibc-getaddrinfo-stack.html  was what I read earlier in the day
[19:41] <sladen> CVE-2015-12345
[19:42] <sladen> sarnold: I think we can start with ubottu...
[19:42] <sarnold> hehe
[19:44] <kirkland> okay, I'm at a loss...  can someone help me identify why this keeps failing to build?  https://launchpadlibrarian.net/239090418/buildlog_ubuntu-xenial-amd64.ssh-import-id_5.2-0ubuntu1_BUILDING.txt.gz
[19:46] <nacc> kirkland: "file ssh_import_id.py (for module ssh_import_id) not found" ?
[19:46] <nacc> kirkland: just a guess
[19:46] <kirkland> nacc: hmm
[19:47] <sarnold> __version__ = pkg_resources.get_distribution('ssh_import_id').version   -- you've got an odd one on your hands, that's for sure :)
[19:49] <kirkland> sarnold: is there a better way to print the current version a python package, from within the code of the package itself?
[19:50] <sarnold> kirkland: no idea :/
[20:17] <nacc> infinity: would you ahve time after (my) lunch to go over the php7 stuff?
[20:22] <barry> kirkland: there are several approaches that won't require pkg_resources, but it depends on whether you want to do an import to get the version number or not.  for a lot of simple packages, they put the __version__ in a separate module (or mypkg/__init__.py) and you can just import it from there.  another popular non-import alternative is to put the version number in a .txt file and parse it out of there.  i have a common helper for
[20:22] <barry> that, but it's also fairly easy to write.  to avoid putting a version number in multiple places, you'd use the same parse-or-import scheme in your setup.py and in whatever prints --version
[20:24] <kirkland> barry: I think I might have found it...
[20:24] <barry> kirkland: cool
[20:24] <kirkland> barry: maybe :-)  new build sent
[20:24] <kirkland> barry: what's odd is it builds fine here, on my xenial desktop, in a clean sandbox
[20:24] <kirkland> barry: but not on LP
[20:25] <barry> kirkland: in an sbuild?
[20:25] <kirkland> barry: no, a pristine lxd container :-)
[20:25] <kirkland> barry: the new sbuild :-)
[20:25] <barry> kirkland: neat!  unfortunately lp is still the old sbuild :)
[20:26] <kirkland> barry: :-D
[21:31] <infinity> nacc: Possibly, I'm in the middle of a sprint right now, so it depends on if I can get away.
[21:43] <smoser> pitti, if your'e still around. would you do the merge of open-iscsi?
[21:44] <smoser> i'm quite loaded before thursday and would like to see that land before FF rather htan after.
[22:41] <nacc> infinity: ok, so maybe it's best for you to ping me if/when you're free
[23:19]  * tsimonq2 still can't figure out what sprint infinity is at :)
[23:34] <nacc> jamespage: how do correclty update, e.g., eclipse's dependencyManifests directory? to point at the tomcat8 versions of the jars, etc.
[23:34] <nacc> how do *I*, rather :)