/srv/irclogs.ubuntu.com/2016/06/30/#ubuntu-devel.txt

=== _salem is now known as salem_
GrorcoHello 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:58
Grorcothis is the specific part I'm having trouble with: from .SimpleGtkbuilderApp import SimpleGtkbuilderApp00:59
Grorcois it just pointing to the current directory?01:01
sarnoldGrorco: it looks like "package-relative" rather than "directory relative" https://www.python.org/dev/peps/pep-0328/#guido-s-decision01:04
Grorcosarnold: 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 module01:07
GrorcoI'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:18
sarnolda python channel is more likely to be active at this time, anyway :) heh01:19
mwhudsonslangasek: if i want to make a snappy packaging change, where would be the best place to send it?01:42
mwhudsonslangasek: snapcore/snapd? vorlonofportland/snapd?01:42
=== salem_ is now known as _salem
=== _salem is now known as salem_
cpaelzergood morning05:24
happyaroncyphermox: 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, though06:13
pittinacc: 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 automatically06:37
pittinacc: btw, Default-Stop: 1 is usually preferred, unless your service needs some special code other than just being killed at shutdown/restart06:38
=== ljp is now known as lpotter
dokoinfinity,  lintian merge would be appreciated09:05
=== nobuto_ is now known as nobuto
=== davmor2_ is now known as davmor2
=== zyga_ is now known as zyga
pittistgraber: https://images.linuxcontainers.org/ → I can haz Fedora 24?09:16
seb128does anyone has an idea how to debug issues like bug #1589097?09:20
ubottubug 1589097 in gnome-menus (Ubuntu) "package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: triggers looping, abandoned" [High,Confirmed] https://launchpad.net/bugs/158909709:20
seb128we seem to get some report of that one09:21
seb128bug #159095209:21
ubottubug 1590952 in gnome-menus (Ubuntu) "package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: triggers looping, abandoned" [High,Confirmed] https://launchpad.net/bugs/159095209:21
seb128etc09:21
LaneyYou probably fix it by making bamfdaemon interest-noawait instead of interest09:24
seb128Trevinho, ^ can we get that done and SRUed?09:27
seb128Laney, how do you get that from the triggers list?09:27
Trevinhoseb128: sure, but I can't upload it in the silo. Can you?09:28
seb128why not?09:28
LaneyIt said bamfdaemon was involved, so I checked its triggers file09:28
Trevinhoseb128: I don't have powers AFAIK.09:29
seb128Trevinho, isn't bamf on standard CI train landing?09:29
Trevinhoseb128: ahhhhh, sure. But I thought you meant the gnome menus thing09:29
seb128Trevinho, yes, that's an upgrade bug/triggers depends loop, Laney thinks changing bamf to use interest-noawait should fix it09:30
jamespag`pitti, hey - I added a reference to the OpenStack SRU wiki page to https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/158566009:32
ubottuLaunchpad bug 1585660 in ceph (Ubuntu Xenial) "[SRU] ceph 10.2.2" [High,New]09:32
seb128Laney, 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 archive09:32
Laneyseb128: 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 off09:34
seb128Laney, k, makes sense, thanks09:35
seb128Trevinho, do you need help with that?09:35
Trevinhoseb128: maybe, let me see :)09:40
kilbithpeople, 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:03
tsimonq2kilbith: could you be more specific about what release of Ubuntu?10:07
kilbithtsimonq2: 16.0410:07
tsimonq2kilbith: what's the package name?10:07
kilbithtraditionally ubuntu always stick with the same mesa version until the next release..10:07
kilbithwhich is plain wrong10:07
kilbithtsimonq2: mesa, obviously10:08
tsimonq2!info mesa xenial10:08
ubottuPackage mesa does not exist in xenial10:08
tsimonq2!info mesa yakkety10:08
ubottuPackage mesa does not exist in yakkety10:08
tsimonq2weird10:08
tsimonq2kilbith: so it's 11.2.0 in Xenial but 11.2.1 in Yakkety10:09
tsimonq2kilbith: https://launchpad.net/ubuntu/+source/mesa10:09
kilbithyes10:09
kilbithand 11.2.2 is supposedly stabler10:09
tsimonq2looks like 11.2.2 is in Debian Testing right now10:09
tsimonq2we should get it via automatic import soon in Yakkety10:10
kilbithand why not in Xenial ?10:10
tsimonq2kilbith: then we just need an SRU filled out to get it in Xenial10:10
kilbithso much administrative heaviness...10:10
tsimonq2because 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 stability10:11
pittiwell, "supposedly more stable" is not a good enough bet for stable OS releases -- we must not break anything that currently works10:11
tsimonq2^10:11
pittiand mesa is notoriously regression prone, verifying it on a lot of different hw is hard and expensive10:11
kilbithlook, the upstream devs are better able to determine if their package is stable or not than some distro maintainers10:11
kilbithbecause it's their code10:11
pittiwell, 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:12
tsimonq2kilbith: if you really need it right away, you can install the debs manually from Debian10:13
pittitjaalton: I guess at some point you guys were planning to update mesa in xenial, I figure?10:13
tsimonq2pitti: but like I said, maybe it should wait for the import from Debian before an SRU? *shrug*10:14
kilbithtsimonq2: if i use ubuntu, it's not for tinkering with the packages manually, otherwise i'd would return back on arch10:14
tjaaltonpitti: yes10:14
pittitsimonq2: yes, of course devel needs to be updated first, as usual10:14
tsimonq2kilbith: it's FLOSS, so what you wish with your system, just because it's Ubuntu doesn't mean you don't have the ability10:15
pittikilbith: 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 ponit10:15
kilbiththat 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 release10:15
tjaaltonmesa has a standing MRE10:15
tsimonq2aha, there you go10:16
tsimonq2kilbith: so it's in the works, it's not like it won't happen :)10:16
tsimonq2it just might take a few weeks if not longer10:16
tjaaltoni'm working on lts-xenial backport stack, mesa updates have lesser priority10:17
ppisatii'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 name10:33
ppisatiany idea?10:33
pittipsivaa: is that an USB device?10:39
stefancti 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
ppisatipitti: yes10:39
pittipsivaa: sorry, IRC nick fail, I meant ppisati10:40
pittippisati: known bug, let me find the #10:40
psivaapitti: Yep. No problem. Hope you're doing well :)10:40
stefanctso 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
pittipsivaa: I am, thanks! how's things in CI land?10:40
psivaapitti: CI land has been obliterated. Now OLS. Doing good. Thanks10:41
stefancti 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
pittippisati: bug 1593379 (with linked Debian bug)10:42
ubottubug 1593379 in systemd (Ubuntu) "systemd 229-4ubuntu6 ignores net.ifnames=0 on USB" [Undecided,In progress] https://launchpad.net/bugs/159337910:42
stefanctadding 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:48
ppisatipitti: thanks10:51
=== jamespag` is now known as jamespge
=== jamespge is now known as jamespage
=== hikiko is now known as hikiko|bbl
=== salem_ is now known as _salem
flexiondotorgAnyone here know if Cloud images for 16.10 alpha 1 will be published today?11:21
Odd_Blokeflexiondotorg: 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:26
flexiondotorgOdd_Bloke, Thanks. Just wanted to know for the release announcement.11:27
=== PaulW2U_ is now known as PaulW2U
flexiondotorgI don't appear to be able to edit the wiki.11:30
flexiondotorgI've got a vague memory about it, or parts of it, becoming read-only.11:30
flexiondotorgtsimonq2, Do you have the permission to add the required wiki pages?11:30
tsimonq2flexiondotorg: yes11:31
tsimonq2flexiondotorg: I would suggest making a Google Document so we can suggest stuff and make comments :)11:31
flexiondotorgtsimonq2, Traditionally the release notes for each flavour are posted on the wiki.11:32
flexiondotorgI can't do that anymore.11:32
flexiondotorgAs for the release announcement, sure, a Google Doc is fine :-)11:32
Trevinhoseb128: for that bamfdaemon change... what should I exactly do?11:35
TrevinhoI didn't find much docs around11:36
LaneyTrevinho: sed -i "s/interest/&-noawait/" debian/bamfdaemon.triggers11:39
TrevinhoLaney: ah, ok simple as that..11:39
LaneyHopefully11:40
TrevinhoLaney: that's in generating the index file only though.. So it would affect first-startup only. not when new stuff is added11:42
LaneyTrevinho: Seems fine?11:45
TrevinhoLaney: I hope so11:45
TrevinhoLaney: is there a bug related to that, or just the same for gnome-menu?11:45
LaneyTrevinho: I would reassign or add a task to one of those gnome-menus ones11:46
Trevinhook, on that11:46
=== _salem is now known as salem_
TrevinhoLaney: do you also know why the new unity7 landing is sticking in proposed for so long?11:50
LaneyTrevinho: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity this page does11:51
LaneyI just retried that test11:51
TrevinhoMh, I really should land the changes I did so that we don't have this link with unity811:52
TrevinhoLaney: https://code.launchpad.net/~3v1n0/bamf/triggers-noawait/+merge/29876511:54
LaneyTrevinho: no permissions to approve, but looks good11:56
LaneyTrevinho: you linked a weird bug though11:58
TrevinhoLaney: the name is not the nicest I agree12:00
Laneyhttps://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/158909712:00
ubottuLaunchpad bug 1589097 in gnome-menus (Ubuntu) "package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: triggers looping, abandoned" [High,Confirmed]12:00
popeyflexiondotorg: you should be an Ubuntu Member, should you not?12:01
popeyAs you're a per package uploader?12:01
TrevinhoLaney: well, that's better, but still related to gnome-menus.. .I add bamf then12:01
popeyI don't know that process from the developer board / motu side. Dunno if someone else here does.12:01
popeyBut either way, if you're in ~ubuntumembers you get edit rights on the wiki.12:01
flexiondotorgpopey, Thanks for approving my ~ubuntu-wiki-editors membership. I can now help tsimonq2.12:02
tsimonq2\o/12:02
flexiondotorgAnd yes, I "think" I might be eligible for Ubuntu Membership.12:02
LaneyYou should have been added to ~ubuntu-dev, unless the DMB decided not to give you membership12:03
flexiondotorgI 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
flexiondotorgLaney, Membership wasn't discussed. I didn't even know it was an option until a few days ago.12:03
Laneyhttps://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Teams_to_add_uploaders_to12:04
LaneyA script to find people who aren't in either of those teams would be nice12:05
flexiondotorgjbicha, See above ^^^ I think you did that recently?12:06
LaneySuggest you contact the DMB and ask them to fix it, providing that link12:07
* Laney lunch12:09
rbasakflexiondotorg: when did you originally get upload access?12:19
flexiondotorgrbasak, Ummm. April-ish.12:19
rbasakflexiondotorg: 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_to12:27
flexiondotorgrbasak, OK :-) So what happens next?12:29
flexiondotorgrbasak, Thanks for looking into this.12:29
rbasakflexiondotorg: I've added you :)12:30
flexiondotorg:-)12:30
flexiondotorgrbasak, So does being an ~ubuntu-dev member mean I can apply for ~ubuntu-member now?12:31
rbasakflexiondotorg: 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/+participation12:33
rbasakflexiondotorg: sorry this got missed before. And welcome :-P12:34
rbasakOh, and not PPU, the packageset.12:34
flexiondotorgrbasak, No problem and thanks for sorting that so promptly :-)12:35
rbasakflexiondotorg: also, you quite obviously should be a member :-)12:35
flexiondotorgrbasak, So how do I get an @ubuntu.com email address?12:35
rbasakGood question. That I don't know, since as the email infrastructure is shared with Canonical it's different for me.12:36
tsimonq2flexiondotorg: If I remember correctly, vanguard at #canonical-sysadmin can assit12:36
tsimonq2*assist12:36
flexiondotorgrbasak, tsimonq2 Thanks.12:37
rbasakSome info at https://wiki.ubuntu.com/UbuntuEmail12:37
flexiondotorgpopey, That got fixed then :-)12:37
rbasakBut those pages don't seem to explain how to get one added.12:37
tsimonq2rbasak: I had a question relating my email one time and IS has the access to change whatever12:38
tsimonq2s/relating/relating to/12:38
rbasakYeah I suspect the answer is "file an RT". We should document that in the wiki if so.12:38
tsimonq2good idea12:38
popeyflexiondotorg: congrats ㋛12:38
tsimonq2\o/ ^12:39
flexiondotorg:-D12:39
cjwatsonrbasak: 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:39
tsimonq2cjwatson: well no12:40
cjwatsonsays there's a script that creates the aliases that runs every two days12:40
tsimonq2when I got membership, I leanred that IS has to approve it12:40
rbasakcjwatson: but what email? ie. how do you get the script to create you, and what alias would it use?12:40
tsimonq2and that takes longer than 48 hours sometimes :)12:40
tsimonq2*learned12:40
cjwatsontsimonq2: it is possible that the page is wrong, but it does say :-)12:40
cjwatsonrbasak: it's always your LP username12:40
rbasakAh, I see.12:40
tsimonq2cjwatson: well 48 hours is probably the standard response time12:40
cjwatsonrbasak: the page says that12:40
rbasakcjwatson: you're right. Thanks.12:41
cjwatsonI 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 it12:43
=== josepht` is now known as josepht
=== hikiko|bbl is now known as hikiko
=== caribou_ is now known as caribou
naccpitti: thanks15:28
stgraberpitti: let me try15:34
cjwatsonpitti: FYI I believe I've fixed ddeb-retriever (by getting Stéphane to make a team public)15:50
slangasekmwhudson: snappy packaging change> send it to both for right now?16:07
naccmterry: would you have a link or reference to the tidy-html5 transition?16:22
pitticjwatson: ooh -- was that the "permission denied"-thingy exception? thanks!16:29
cjwatsonthat's the one16:32
=== tarpman_ is now known as tarpman
semiosisOdd_Bloke: just saw your comment.  i'm around if you want to chat16:35
Odd_Blokesemiosis: 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_Blokesemiosis: 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. :p16:39
semiosishmm.  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:40
semiosismaybe those packages aren't in your apt mirror?16:41
naccrbasak: confused a bit by the output in the DpkgTerminalLog.gz of LP: #159759716:45
ubottuLaunchpad bug 1597597 in php7.0 (Ubuntu) "package libapache2-mod-php7.0 7.0.8-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128" [Undecided,New] https://launchpad.net/bugs/159759716:45
naccit's one of those falsely attributed to php7 (afaict), as the underlying issue is perl warnings from debconf?16:45
rbasaknacc: I've seen that before but I never figured out what it is.16:46
naccrbasak: do you have a default reply for such bugs handy? is it worth debugging?16:47
rbasaknacc: 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
naccrbasak: thanks16:48
rbasakAnd then I mark Incomplete.16:48
Odd_Blokesemiosis: Yeah, I'm not sure.  This is happening on the Launchpad builders though, which is where this eventually needs to work.16:48
semiosisOdd_Bloke: ok thanks for working on it.  i'm here if you need me for anything16:49
Odd_Blokesemiosis: Sure thing, thanks. :)16:50
mterrynacc, no I don't -- something started in Debian and affecting yakkety, that's all I know16:51
naccmterry: ack, thanks16:52
naccrbasak: 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 it16:55
pittidoko: FYI, I'm fixing scour autopkgtest regression (one of the things blocking p-setuptools)16:55
dokota16:56
pittidinstall 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 hint16:57
dokono, don't think so16:57
pittisnapcraft is its own fault, not python's16:58
cjwatsonpitti: it does?16:59
pitticjwatson: yeah, something like 10 hours16:59
cjwatsonpitti: *blink*16:59
cjwatsonnews to me16:59
dokopython2.7 and python3.5 migrated, good news16:59
dokobinutils still blocked on the lintian autopkg test. will try to merge that tonight or tomorrow morning16:59
pitticjwatson: well, maybe 8 or so;17:01
pitticjwatson: so, I uploaded https://tracker.debian.org/news/779188 on Tuesday night, it was dinstall'ed in Debian at 01:52 UTC17:02
cjwatsonpitti: I think any time I've looked it's actually been that it takes a while to appear on the mirror that we use17:02
pittiand imported into LP https://launchpad.net/debian/+source/init-system-helpers/+publishinghistory at 12:1317:02
pittiso pretty well 10 hours, yes17:02
pitticjwatson: ah, maybe it's that17:02
pittiI didn't actually consider it a bug, I thought I'm just impatient :)17:02
cjwatsonpitti: but we try every six hours currently, maybe the cycle has got a bit out of sync17:03
stgraberpitti: we now have fedora 24 images, no idea if they work though :)17:13
Odd_Blokesemiosis: Looks like the `apt-get update` might have fixed the problem. :)17:15
semiosisnice!17:17
jbichaLaney: https://people.canonical.com/~ubuntu-archive/archive-permissions/17:23
jbichait has false positives though so you need to cross-ref results with lp-check-membership username ubuntu-dev17:25
jbichaor make the script smarter17:25
=== sarnold_ is now known as sarnold
Odd_Blokesemiosis: Could you test http://people.canonical.com/~dwatkins/livecd.ubuntu-cpc.vagrant.box for me?17:48
Odd_Blokesemiosis: (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?)17:52
semiosisOdd_Bloke: will test & comment soon.  thanks!!!19:03
pittistgraber: 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:34
pittiarf, and now I do, sorry19:35
stgrabertakes a little while between jenkins building it and it being imported, signed, packaged and published, so maybe you tried just before that happened19:35
stgraberwill 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:36
pittiand oh well, it boots :)19:37
pitti             ├─network.service19:37
pitti             │ ├─ 53 /bin/bash /etc/rc.d/init.d/network start19:38
pitti             │ ├─176 /bin/bash /etc/sysconfig/network-scripts/ifup-eth ifcfg-eth0 boot19:38
pittishush :)19:38
pittistgraber: merci beaucoup; man, this is magnitudes more convenient than downloading the iso and installing it into a VM!19:39
stgraber:)19:41
stgraberglad that all it took was adding "24" to the list of series on Jenkins, 23 was significantly more painful to get building19:42
pittibdmurray: FYI, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#software-properties is stuck on a test regression  (.22 still works)19:55
mwhudsonslangasek: ok20:11
jderosepitti: this is an extra weird one, wondering if you have any thoughts on it - https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/159787620:42
ubottuLaunchpad bug 1597876 in systemd (Ubuntu) "installing/upgrading packages containing systemd services results in prompt for cryptoswap passphrase [xenial]" [Undecided,New]20:42
=== ivoks_ is now known as ivoks
jderosekirkland: when you have a chance, could you give this a look over (merge proposal submitted) - https://bugs.launchpad.net/ecryptfs/+bug/159715422:15
ubottuLaunchpad bug 1597154 in System76 "ecryptfs-setup-swap fails with GPT partitioning + NVMe/MMC drives" [Critical,In progress]22:15
tyhicksjderose, kirkland: that's on my todo list by EOW22:23
jderosetyhicks: 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:24
tyhicksjderose: yes!22:27
jderosetyhicks: more sweet music to my ears! thanks!22:29
=== salem_ is now known as _salem

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!