[00:58] <Grorco> Hello I have a question about python imports, I'm looking at some code and after the initial imports the use from .WhatEver import blahblahblah how does the . work?
[00:59] <Grorco> this is the specific part I'm having trouble with: from .SimpleGtkbuilderApp import SimpleGtkbuilderApp
[01:01] <Grorco> is it just pointing to the current directory?
[01:04] <sarnold> Grorco: it looks like "package-relative" rather than "directory relative" https://www.python.org/dev/peps/pep-0328/#guido-s-decision
[01:07] <Grorco> sarnold: thank you this is the first source package I've worked on and I had never seen that before could I get around this temporarily for testing by just importing the module
[01:18] <Grorco> I'm sorry if I posting this on the wrong channel to be asking I was working on a papercut so I came here, should I take questions like this to a python channel?
[01:19] <sarnold> a python channel is more likely to be active at this time, anyway :) heh
[01:42] <mwhudson> slangasek: if i want to make a snappy packaging change, where would be the best place to send it?
[01:42] <mwhudson> slangasek: snapcore/snapd? vorlonofportland/snapd?
[05:24] <cpaelzer> good morning
[06:13] <happyaron> cyphermox: I gave it a try moment ago and it works the way in your comment, not sure if split tunneling has more scenes I'm not aware of, though
[06:37] <pitti> nacc: no, Default-{Start,Stop} is a SysV init scripts' way to set the runlevel, that must be done if the service is to be started automatically
[06:38] <pitti> nacc: btw, Default-Stop: 1 is usually preferred, unless your service needs some special code other than just being killed at shutdown/restart
[09:05] <doko> infinity,  lintian merge would be appreciated
[09:16] <pitti> stgraber: https://images.linuxcontainers.org/ → I can haz Fedora 24?
[09:20] <seb128> does anyone has an idea how to debug issues like bug #1589097?
[09:21] <seb128> we seem to get some report of that one
[09:21] <seb128> bug #1590952
[09:21] <seb128> etc
[09:24] <Laney> You probably fix it by making bamfdaemon interest-noawait instead of interest
[09:27] <seb128> Trevinho, ^ can we get that done and SRUed?
[09:27] <seb128> Laney, how do you get that from the triggers list?
[09:28] <Trevinho> seb128: sure, but I can't upload it in the silo. Can you?
[09:28] <seb128> why not?
[09:28] <Laney> It said bamfdaemon was involved, so I checked its triggers file
[09:29] <Trevinho> seb128: I don't have powers AFAIK.
[09:29] <seb128> Trevinho, isn't bamf on standard CI train landing?
[09:29] <Trevinho> seb128: ahhhhh, sure. But I thought you meant the gnome menus thing
[09:30] <seb128> Trevinho, yes, that's an upgrade bug/triggers depends loop, Laney thinks changing bamf to use interest-noawait should fix it
[09:32] <jamespag`> pitti, hey - I added a reference to the OpenStack SRU wiki page to https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1585660
[09:32] <seb128> Laney, k, I guess I didn't look at triggers for look enough to not understand the issue or where gmenucache is coming from ... anyway, not important, thanks for the hint!
[09:32] <jamespag`> is that sufficient from your perspective as a regression test plan? its pretty much what we've done for the last 3 years for OpenStack bits in the archive
[09:34] <Laney> seb128: Would need to do more digging to find out exactly why, but it's my first guess and might be easier to do it and see if the reports drop off
[09:35] <seb128> Laney, k, makes sense, thanks
[09:35] <seb128> Trevinho, do you need help with that?
[09:40] <Trevinho> seb128: maybe, let me see :)
[10:03] <kilbith> people, there's no reason to stick on mesa 11.2.0 when mesa 11.2.1 and 11.2.2 contain only bugfixes and no new features..
[10:07] <tsimonq2> kilbith: could you be more specific about what release of Ubuntu?
[10:07] <kilbith> tsimonq2: 16.04
[10:07] <tsimonq2> kilbith: what's the package name?
[10:07] <kilbith> traditionally ubuntu always stick with the same mesa version until the next release..
[10:07] <kilbith> which is plain wrong
[10:08] <kilbith> tsimonq2: mesa, obviously
[10:08] <tsimonq2> !info mesa xenial
[10:08] <tsimonq2> !info mesa yakkety
[10:08] <tsimonq2> weird
[10:09] <tsimonq2> kilbith: so it's 11.2.0 in Xenial but 11.2.1 in Yakkety
[10:09] <tsimonq2> kilbith: https://launchpad.net/ubuntu/+source/mesa
[10:09] <kilbith> yes
[10:09] <kilbith> and 11.2.2 is supposedly stabler
[10:09] <tsimonq2> looks like 11.2.2 is in Debian Testing right now
[10:10] <tsimonq2> we should get it via automatic import soon in Yakkety
[10:10] <kilbith> and why not in Xenial ?
[10:10] <tsimonq2> kilbith: then we just need an SRU filled out to get it in Xenial
[10:10] <kilbith> so much administrative heaviness...
[10:11] <tsimonq2> because the development release gets all the new packages, and package updates for Xenial, an LTS and stable release, need to be checked out before it's released to those users to ensure stability
[10:11] <pitti> well, "supposedly more stable" is not a good enough bet for stable OS releases -- we must not break anything that currently works
[10:11] <tsimonq2> ^
[10:11] <pitti> and mesa is notoriously regression prone, verifying it on a lot of different hw is hard and expensive
[10:11] <kilbith> look, the upstream devs are better able to determine if their package is stable or not than some distro maintainers
[10:11] <kilbith> because it's their code
[10:12] <pitti> well, I wasn't saying that we won't do the update (we most probably will), but we don't just throw it over the  fence and hope that nothing breaks :)
[10:12] <tsimonq2> ^
[10:13] <tsimonq2> kilbith: if you really need it right away, you can install the debs manually from Debian
[10:13] <pitti> tjaalton: I guess at some point you guys were planning to update mesa in xenial, I figure?
[10:14] <tsimonq2> pitti: but like I said, maybe it should wait for the import from Debian before an SRU? *shrug*
[10:14] <kilbith> tsimonq2: if i use ubuntu, it's not for tinkering with the packages manually, otherwise i'd would return back on arch
[10:14] <tjaalton> pitti: yes
[10:14] <pitti> tsimonq2: yes, of course devel needs to be updated first, as usual
[10:15] <tsimonq2> kilbith: it's FLOSS, so what you wish with your system, just because it's Ubuntu doesn't mean you don't have the ability
[10:15] <pitti> kilbith: so, if there is something broken on your system, please file a bug about it (we can then use this for SRUing); if it's just "I want the new version just because", then there's no urgency and it will happen at some ponit
[10:15] <kilbith> that said, the maintainer on fedora is dave airlie himself (mesa dev) and often update the mesa packages to the latest version even within the current stable release
[10:15] <tjaalton> mesa has a standing MRE
[10:16] <tsimonq2> aha, there you go
[10:16] <tsimonq2> kilbith: so it's in the works, it's not like it won't happen :)
[10:16] <tsimonq2> it just might take a few weeks if not longer
[10:17] <tjaalton> i'm working on lts-xenial backport stack, mesa updates have lesser priority
[10:33] <ppisati> i'm passing net.ifnames=0 and i've created a dummy /etc/udev/rules.d/80-net-name-slot.rules file, but my nic's keep changing name
[10:33] <ppisati> any idea?
[10:39] <pitti> psivaa: is that an USB device?
[10:39] <stefanct> i am trying to build an ubuntu kernel with a single patch applied that should not change the ABI AFAICT (generic ID addition for a USB module)
[10:39] <ppisati> pitti: yes
[10:40] <pitti> psivaa: sorry, IRC nick fail, I meant ppisati
[10:40] <pitti> ppisati: known bug, let me find the #
[10:40] <psivaa> pitti: Yep. No problem. Hope you're doing well :)
[10:40] <stefanct> so i followed the (various) articles in the wiki... currently ending up in II: Checking modules for generic...previous or current modules file missing!
[10:40] <pitti> psivaa: I am, thanks! how's things in CI land?
[10:41] <psivaa> pitti: CI land has been obliterated. Now OLS. Doing good. Thanks
[10:42] <stefanct> i have created the <previous-version>/<arch>/ignore files as documented... although i am not 100% sure what previous-version refers to (i have used the ubuntu version string to which i have appended +bla for my own build)
[10:42] <pitti> ppisati: bug 1593379 (with linked Debian bug)
[10:48] <stefanct> adding skipabi=true skipmodule=true seems to help... unlike the ignore files (unlike documented here: https://wiki.ubuntu.com/KernelTeam/KernelMaintenance#Overriding_module_check_failures )
[10:51] <ppisati> pitti: thanks
[11:21] <flexiondotorg> Anyone here know if Cloud images for 16.10 alpha 1 will be published today?
[11:26] <Odd_Bloke> flexiondotorg: We're just going to participate as Ubuntu this time around (so no).  If you want what would have been the alpha1 image, just grab the latest daily. :)
[11:27] <flexiondotorg> Odd_Bloke, Thanks. Just wanted to know for the release announcement.
[11:30] <flexiondotorg> I don't appear to be able to edit the wiki.
[11:30] <flexiondotorg> I've got a vague memory about it, or parts of it, becoming read-only.
[11:30] <flexiondotorg> tsimonq2, Do you have the permission to add the required wiki pages?
[11:31] <tsimonq2> flexiondotorg: yes
[11:31] <tsimonq2> flexiondotorg: I would suggest making a Google Document so we can suggest stuff and make comments :)
[11:32] <flexiondotorg> tsimonq2, Traditionally the release notes for each flavour are posted on the wiki.
[11:32] <flexiondotorg> I can't do that anymore.
[11:32] <flexiondotorg> As for the release announcement, sure, a Google Doc is fine :-)
[11:35] <Trevinho> seb128: for that bamfdaemon change... what should I exactly do?
[11:36] <Trevinho> I didn't find much docs around
[11:39] <Laney> Trevinho: sed -i "s/interest/&-noawait/" debian/bamfdaemon.triggers
[11:39] <Trevinho> Laney: ah, ok simple as that..
[11:40] <Laney> Hopefully
[11:42] <Trevinho> Laney: that's in generating the index file only though.. So it would affect first-startup only. not when new stuff is added
[11:45] <Laney> Trevinho: Seems fine?
[11:45] <Trevinho> Laney: I hope so
[11:45] <Trevinho> Laney: is there a bug related to that, or just the same for gnome-menu?
[11:46] <Laney> Trevinho: I would reassign or add a task to one of those gnome-menus ones
[11:46] <Trevinho> ok, on that
[11:50] <Trevinho> Laney: do you also know why the new unity7 landing is sticking in proposed for so long?
[11:51] <Laney> Trevinho: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity this page does
[11:51] <Laney> I just retried that test
[11:52] <Trevinho> Mh, I really should land the changes I did so that we don't have this link with unity8
[11:54] <Trevinho> Laney: https://code.launchpad.net/~3v1n0/bamf/triggers-noawait/+merge/298765
[11:56] <Laney> Trevinho: no permissions to approve, but looks good
[11:58] <Laney> Trevinho: you linked a weird bug though
[12:00] <Trevinho> Laney: the name is not the nicest I agree
[12:00] <Laney> https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1589097
[12:01] <popey> flexiondotorg: you should be an Ubuntu Member, should you not?
[12:01] <popey> As you're a per package uploader?
[12:01] <Trevinho> Laney: well, that's better, but still related to gnome-menus.. .I add bamf then
[12:01] <popey> I don't know that process from the developer board / motu side. Dunno if someone else here does.
[12:01] <popey> But either way, if you're in ~ubuntumembers you get edit rights on the wiki.
[12:02] <flexiondotorg> popey, Thanks for approving my ~ubuntu-wiki-editors membership. I can now help tsimonq2.
[12:02] <tsimonq2> \o/
[12:02] <flexiondotorg> And yes, I "think" I might be eligible for Ubuntu Membership.
[12:03] <Laney> You should have been added to ~ubuntu-dev, unless the DMB decided not to give you membership
[12:03] <flexiondotorg> I was just reading the wiki and I seem like I might be able to get a nomination via the DMB because of my PPU.
[12:03] <flexiondotorg> Laney, Membership wasn't discussed. I didn't even know it was an option until a few days ago.
[12:04] <Laney> https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Teams_to_add_uploaders_to
[12:05] <Laney> A script to find people who aren't in either of those teams would be nice
[12:06] <flexiondotorg> jbicha, See above ^^^ I think you did that recently?
[12:07] <Laney> Suggest you contact the DMB and ask them to fix it, providing that link
[12:09]  * Laney lunch
[12:19] <rbasak> flexiondotorg: when did you originally get upload access?
[12:19] <flexiondotorg> rbasak, Ummm. April-ish.
[12:27] <rbasak> flexiondotorg: I think you not belonging to ~ubuntu-dev is an oversight. I reviewed https://irclogs.ubuntu.com/2016/05/09/%23ubuntu-meeting.html and https://irclogs.ubuntu.com/2016/04/25/%23ubuntu-meeting.html that don't suggest otherwise, and granting membership is our default position according to https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Teams_to_add_uploaders_to
[12:29] <flexiondotorg> rbasak, OK :-) So what happens next?
[12:29] <flexiondotorg> rbasak, Thanks for looking into this.
[12:30] <rbasak> flexiondotorg: I've added you :)
[12:30] <flexiondotorg> :-)
[12:31] <flexiondotorg> rbasak, So does being an ~ubuntu-dev member mean I can apply for ~ubuntu-member now?
[12:33] <rbasak> flexiondotorg: no need - the DMB implicitly granted that when granting you PPU (since we didn't say otherwise). So you're in ~ubuntu-member by virtue of being in ~ubuntu-dev - see https://launchpad.net/~flexiondotorg/+participation
[12:34] <rbasak> flexiondotorg: sorry this got missed before. And welcome :-P
[12:34] <rbasak> Oh, and not PPU, the packageset.
[12:35] <flexiondotorg> rbasak, No problem and thanks for sorting that so promptly :-)
[12:35] <rbasak> flexiondotorg: also, you quite obviously should be a member :-)
[12:35] <flexiondotorg> rbasak, So how do I get an @ubuntu.com email address?
[12:36] <rbasak> Good question. That I don't know, since as the email infrastructure is shared with Canonical it's different for me.
[12:36] <tsimonq2> flexiondotorg: If I remember correctly, vanguard at #canonical-sysadmin can assit
[12:36] <tsimonq2> *assist
[12:37] <flexiondotorg> rbasak, tsimonq2 Thanks.
[12:37] <rbasak> Some info at https://wiki.ubuntu.com/UbuntuEmail
[12:37] <flexiondotorg> popey, That got fixed then :-)
[12:37] <rbasak> But those pages don't seem to explain how to get one added.
[12:38] <tsimonq2> rbasak: I had a question relating my email one time and IS has the access to change whatever
[12:38] <tsimonq2> s/relating/relating to/
[12:38] <rbasak> Yeah I suspect the answer is "file an RT". We should document that in the wiki if so.
[12:38] <tsimonq2> good idea
[12:38] <popey> flexiondotorg: congrats ㋛
[12:39] <tsimonq2> \o/ ^
[12:39] <flexiondotorg> :-D
[12:39] <cjwatson> rbasak: I believe it does say; it says "wait at least 48 hours [after being added to ~ubuntumembers] before checking if the email is working"
[12:40] <tsimonq2> cjwatson: well no
[12:40] <cjwatson> says there's a script that creates the aliases that runs every two days
[12:40] <tsimonq2> when I got membership, I leanred that IS has to approve it
[12:40] <rbasak> cjwatson: but what email? ie. how do you get the script to create you, and what alias would it use?
[12:40] <tsimonq2> and that takes longer than 48 hours sometimes :)
[12:40] <tsimonq2> *learned
[12:40] <cjwatson> tsimonq2: it is possible that the page is wrong, but it does say :-)
[12:40] <cjwatson> rbasak: it's always your LP username
[12:40] <rbasak> Ah, I see.
[12:40] <tsimonq2> cjwatson: well 48 hours is probably the standard response time
[12:40] <cjwatson> rbasak: the page says that
[12:41] <rbasak> cjwatson: you're right. Thanks.
[12:43] <cjwatson> I guess it may be https://wiki.canonical.com/InformationInfrastructure/ISO/HowTo/LPMailMerge (internal only, sorry), which suggests that the alias file is generated automatically but a sysadmin has to sanity-check and commit it
[15:28] <nacc> pitti: thanks
[15:34] <stgraber> pitti: let me try
[15:50] <cjwatson> pitti: FYI I believe I've fixed ddeb-retriever (by getting Stéphane to make a team public)
[16:07] <slangasek> mwhudson: snappy packaging change> send it to both for right now?
[16:22] <nacc> mterry: would you have a link or reference to the tidy-html5 transition?
[16:29] <pitti> cjwatson: ooh -- was that the "permission denied"-thingy exception? thanks!
[16:32] <cjwatson> that's the one
[16:35] <semiosis> Odd_Bloke: just saw your comment.  i'm around if you want to chat
[16:39] <Odd_Bloke> semiosis: Sure; the install is failing to find the virtualbox bits and (chef|puppet).  I'm hoping an `apt-get update` will fix it.  If not, then it may be that we don't have the right components enabled.
[16:39] <Odd_Bloke> semiosis: But as this is failing in an environment I have access to and you don't, I figured it made more sense for me to iterate than to ask you to make changes you can't test. :p
[16:40] <semiosis> hmm.  that stuff all happens in the debootstrapped chroot.  why would your environment be any different from mine?  both create the same disk image, no?
[16:41] <semiosis> maybe those packages aren't in your apt mirror?
[16:45] <nacc> rbasak: confused a bit by the output in the DpkgTerminalLog.gz of LP: #1597597
[16:45] <nacc> it's one of those falsely attributed to php7 (afaict), as the underlying issue is perl warnings from debconf?
[16:46] <rbasak> nacc: I've seen that before but I never figured out what it is.
[16:47] <nacc> rbasak: do you have a default reply for such bugs handy? is it worth debugging?
[16:48] <rbasak> nacc: http://paste.ubuntu.com/18180857/ is my standard reply. As politely as possible, "need steps to reproduce otherwise we can't work on it".
[16:48] <nacc> rbasak: thanks
[16:48] <rbasak> And then I mark Incomplete.
[16:48] <Odd_Bloke> semiosis: Yeah, I'm not sure.  This is happening on the Launchpad builders though, which is where this eventually needs to work.
[16:49] <semiosis> Odd_Bloke: ok thanks for working on it.  i'm here if you need me for anything
[16:50] <Odd_Bloke> semiosis: Sure thing, thanks. :)
[16:51] <mterry> nacc, no I don't -- something started in Debian and affecting yakkety, that's all I know
[16:52] <nacc> mterry: ack, thanks
[16:55] <nacc> rbasak: i'm still waiting for responses to my bacula bug fixes (testing), although some of the various bugs have responded affirmatively, if you're able to review those too. Or, as discussed today, I can send a MR for it
[16:55] <pitti> doko: FYI, I'm fixing scour autopkgtest regression (one of the things blocking p-setuptools)
[16:56] <doko> ta
[16:57] <pitti> dinstall is in 3 hours, and LP takes ages to import these days, so won't go green until tomorrow; if it's urgent, I can hint
[16:57] <doko> no, don't think so
[16:58] <pitti> snapcraft is its own fault, not python's
[16:59] <cjwatson> pitti: it does?
[16:59] <pitti> cjwatson: yeah, something like 10 hours
[16:59] <cjwatson> pitti: *blink*
[16:59] <cjwatson> news to me
[16:59] <doko> python2.7 and python3.5 migrated, good news
[16:59] <doko> binutils still blocked on the lintian autopkg test. will try to merge that tonight or tomorrow morning
[17:01] <pitti> cjwatson: well, maybe 8 or so;
[17:02] <pitti> cjwatson: so, I uploaded https://tracker.debian.org/news/779188 on Tuesday night, it was dinstall'ed in Debian at 01:52 UTC
[17:02] <cjwatson> pitti: I think any time I've looked it's actually been that it takes a while to appear on the mirror that we use
[17:02] <pitti> and imported into LP https://launchpad.net/debian/+source/init-system-helpers/+publishinghistory at 12:13
[17:02] <pitti> so pretty well 10 hours, yes
[17:02] <pitti> cjwatson: ah, maybe it's that
[17:02] <pitti> I didn't actually consider it a bug, I thought I'm just impatient :)
[17:03] <cjwatson> pitti: but we try every six hours currently, maybe the cycle has got a bit out of sync
[17:13] <stgraber> pitti: we now have fedora 24 images, no idea if they work though :)
[17:15] <Odd_Bloke> semiosis: Looks like the `apt-get update` might have fixed the problem. :)
[17:17] <semiosis> nice!
[17:23] <jbicha> Laney: https://people.canonical.com/~ubuntu-archive/archive-permissions/
[17:25] <jbicha> it has false positives though so you need to cross-ref results with lp-check-membership username ubuntu-dev
[17:25] <jbicha> or make the script smarter
[17:48] <Odd_Bloke> semiosis: Could you test http://people.canonical.com/~dwatkins/livecd.ubuntu-cpc.vagrant.box for me?
[17:52] <Odd_Bloke> semiosis: (And I have to head off for the evening now, but if that looks good to you, could you post it on the bug and ask others to test?)
[19:03] <semiosis> Odd_Bloke: will test & comment soon.  thanks!!!
[19:34] <pitti> stgraber: yay, cool! is there some equivalent of "apt-get update" for the container list? I don't see them yet in lxc image list images:
[19:35] <pitti> arf, and now I do, sorry
[19:35] <stgraber> takes a little while between jenkins building it and it being imported, signed, packaged and published, so maybe you tried just before that happened
[19:36] <stgraber> will be even slower soon as the frontends will be running by Canonical on a periodic rsync kind of setup (rather than current push rsync as I have on my network)
[19:37] <pitti> and oh well, it boots :)
[19:37] <pitti>              ├─network.service
[19:38] <pitti>              │ ├─ 53 /bin/bash /etc/rc.d/init.d/network start
[19:38] <pitti>              │ ├─176 /bin/bash /etc/sysconfig/network-scripts/ifup-eth ifcfg-eth0 boot
[19:38] <pitti> shush :)
[19:39] <pitti> stgraber: merci beaucoup; man, this is magnitudes more convenient than downloading the iso and installing it into a VM!
[19:41] <stgraber> :)
[19:42] <stgraber> glad that all it took was adding "24" to the list of series on Jenkins, 23 was significantly more painful to get building
[19:55] <pitti> bdmurray: FYI, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#software-properties is stuck on a test regression  (.22 still works)
[20:11] <mwhudson> slangasek: ok
[20:42] <jderose> pitti: this is an extra weird one, wondering if you have any thoughts on it - https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597876
[22:15] <jderose> kirkland: when you have a chance, could you give this a look over (merge proposal submitted) - https://bugs.launchpad.net/ecryptfs/+bug/1597154
[22:23] <tyhicks> jderose, kirkland: that's on my todo list by EOW
[22:24] <jderose> tyhicks: awesome, music to me ears! :D Do you think this fix can land in time to be included on the 16.04.1 ISOs?
[22:27] <tyhicks> jderose: yes!
[22:29] <jderose> tyhicks: more sweet music to my ears! thanks!