/srv/irclogs.ubuntu.com/2016/10/11/#ubuntu-devel.txt

=== _salem is now known as salem_
=== salem_ is now known as _salem
cpaelzerpitti: thanks, successfully verified your fix for bug 1630963 against the autopkgtest git05:58
ubottubug 1630963 in autopkgtest (Ubuntu) "issues using user and password in adt-virt-qemu" [Medium,Fix committed] https://launchpad.net/bugs/163096305:58
pitticpaelzer: yay, thanks06:31
pittigood morning06:32
cpaelzergood morning pitti06:35
cpaelzerand good morning everybody else06:35
* cpaelzer feels embarrassed for forgetting his manners by working from home :-/06:35
ginggsmorning pitti! eso-midas has been failing autopkgtests on s390x for a while now, could you do something to let motif migrate please?06:43
pittiginggs: hints updated06:45
ginggspitti: danke!06:45
ricotzchrisccoulson, hi07:25
dokoapw: any update on xfsprogs?07:30
ricotzchrisccoulson, isn't thunderbird 45 effected by https://bugzilla.mozilla.org/show_bug.cgi?id=1251576 too? and please pick up thunderbird 45.4.007:31
ubottuMozilla bug 1251576 in General "GCC6 - TB crashes due to removed null pointer checks for "this"" [Normal,New]07:31
dokochrisccoulson: and please remove the hardening b-d ...07:33
=== jamespag` is now known as jamespage
apwdoko, oh thanks for the reminder, looking at it now08:44
=== King_InuYasha is now known as Son_Goku
=== LStrange1 is now known as LStranger
=== marcusto_ is now known as marcustomlinson
rbasakIs there a simple but non-hacky cross-distro way to determine whether to install to /usr/local/lib64 or /usr/local/lib by default? Currently an upstream is testing for the existence of /lib64, but we have that for a ld-linux-x86-64.so.2 symlink, so they install into /usr/local/lib64 which we don't have as a path in ld.so.conf.09:41
rbasakIt's a hand-rolled Makefile build system09:43
sladenrbasak: have a look what configure/autoconf do09:44
sladenrbasak: I expect it is just to check the presence of one and use the other if not09:45
rbasakI can't find the logic in autoconf :-/09:49
rbasakClearly it searches there when looking for libraries, but I can't find the bit that decides where to install stuff. Is that usually autoconf?09:50
cjwatsonThat's more likely to be automake, if it's detected at all rather than something that you tell it.09:53
cjwatsonEr, I think.09:53
rbasakI couldn't find a reference in automake, but I have just found something in libtool that looks promising09:54
cjwatsonMaybe I'm wrong there.  lib64 has always been a hideous hack, so I question the assumption that it will be handled well :-)09:55
cjwatsonI believe that RPM passes an appropriate --libdir to configure rather than expecting configure to detect it.09:56
cjwatson(Source: https://fedoraproject.org/wiki/Packaging:RPMMacros)09:56
cjwatsons/RPM/the Fedora packaging system/09:56
rbasakIt seems that libtool tries to parse ld.so.conf itself, though I can't get that to work locally. And it'd fail anyway since we use a .d.09:56
rbasakBut I think it'd fall back to not using a lib64, so that'd work for us anyway.09:57
cjwatsonIMO attempts to detect whether to install lib64 are best off being burned.09:57
rbasakI wonder how things work on RH-based systems when not using RPM.09:57
pitticjwatson: do you have an idea how to find out what pulls perl+rename into standard? (http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt) no package in standard depends on either of those, and it's not seeded09:58
pittiand we really don't want to make perl come back..09:58
cjwatsonpitti: Will look, give me a bit.09:58
pittiit's also not seeded anywhere09:58
rbasakcjwatson: I appreciate your response, thanks. Now I'm confident I'm not missing something that everyone knows :-)09:58
cjwatsonrbasak: ICBW of course, my attitude to lib64 has always been one of lofty indifference09:58
rbasakcjwatson: but the problem is: what do I send upstream to fix this, if they're already expecting to detect lib64? If I remove that, they'll (reasonably) worry about breaking something.09:58
cpaelzeroutside rpm isn't too far from rpm - at least looking at their recommendation "rpm --eval '%{_libdir}'"09:59
cjwatsonYeah, I don't know :-/09:59
cjwatsonpitti: germinate says (seeded) dnsutils Depends: libbind9-140 Depends: libdns162 Depends: libisc160 Depends: libxml2 Recommends: xml-core Depends: perl Recommends: rename10:01
rbasakcpaelzer: ah, thanks! So I could concoct something based on that call, and it it fails or doesn't have lib64 in the output, then lib64 isn't in use? That sounds like it might work.10:01
pitticjwatson: argh -- cheers10:01
cpaelzerrbasak: but be aware that on ubuntu that still gives you /usr/lib6410:01
pitticjwatson: so looking at germinate is the way to find out10:01
cjwatsonpitti: Yes, priority-mismatches is based on germinate output10:02
rbasakcpaelzer: you mean if rpm is installed on Ubuntu?10:02
cpaelzeryes10:02
pitticjwatson: ah, I see it in http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.yakkety/standard now; thanks!10:02
rbasakI wonder if one might consider that a bug in rpm's behavior on Debian/Ubuntu.10:03
rbasakIt'd still be better than what they're doing currently, since they're already assuming lib64 just because /lib64 exists10:03
cpaelzerrbasak: unfortunately you said non hacky10:05
cpaelzerrbasak: dirname $(ldd /bin/true | grep libc | awk '{print $3}')10:05
cpaelzerrbasak: would do on fedora, centos, ubuntu and probably others10:06
cpaelzerrbasak: but I understand you don't want to suggest such :-)10:06
cpaelzerrbasak: or maybe you want if it is less broken than the current -e test10:06
rbasakThat does sound like the most non-hacky and reliable suggestion so far, thank you :)10:06
rbasakGiven that it seems that there is no non-hacky solution10:06
cpaelzerrbasak: put the grep search into the awk to not get called stupid10:07
cpaelzerI always only realize that later :-)10:07
rbasakldd /bin/true|awk '/libc\.so/{print $3}'|grep lib64 >/dev/null 2>&1  # maybe?10:09
rbasakAs I need a test rather than the path.10:09
cpaelzerrbasak: how about: ldd /bin/true|awk '/libc\.so/{print $3}'|grep -q '^/lib64'10:11
cpaelzerrbasak: less redirections10:12
rbasakI didn't think "grep -q" was portable though - for example to BSD?10:12
cpaelzerrbasak: and some insurance from ...lib64... strings10:12
cpaelzerrbasak: is that your scope10:12
cpaelzerrbasak: ok then not -q10:12
cpaelzerrbasak: but I'd prefer the '^/lib64'10:12
rbasakAnd I figured that if lib64 appeared anywhere for libc, then we're in lib64 mode.10:12
=== buxy_bak is now known as buxy
cpaelzerrbasak: ok for me10:13
rbasakcjwatson, cpaelzer, sladen: thank you for your help! Now I just have about three other painful but now-offtopic related things to fix :-/10:14
=== hikiko is now known as hikiko|ln
=== hikiko|ln is now known as hikiko
dokohmm, iptraf doesn't show any interface besides lo in y ...11:08
=== _salem is now known as salem_
=== barry` is now known as barry
=== josepht` is now known as josepht
cpaelzerI beg a pardon if that it a faux pas by itself, but is there a reasonable way to get root permission in d/rules execution?13:42
cpaelzerI'd want to use that for a bit weird autotest requirement13:42
cjwatsoncpaelzer: it's not possible in general; use autopkgtests instead for that kind of thing13:45
cpaelzercjwatson: thanks13:45
cjwatsonyou can do "Restrictions: needs-root" there13:45
cpaelzercjwatson: yeah I have that for other tests already13:45
cpaelzerthe charm would ahve been to have that executed on the just built code - I'd like to avoid to build it just again for the adt13:46
cjwatsonyeah ideally you would have a test that you could run on the as-installed code instead13:47
cpaelzerin that sense I already have it covered in a test run that we use to verify package uploads (with far more tests)13:47
cpaelzercjwatson: actually that might be a great idea - for Z* I might tihnk on putting the test program into the -dev package13:47
cpaelzercjwatson: is that in general kind of "ok" ?^^13:48
cjwatsonpossibly, I don't know your specific situation13:48
cjwatsonyou could also consider building only the test program in the autopkgtest13:48
cjwatsonopenssh does a sort of partial build of itself in its autopkgtests in order to be able to build the regression tests13:48
rbasakThe link to the spec from http://dep.debian.net/deps/dep8/ appears broken13:49
rbasakpitti: ^13:49
cjwatsonthough possibly shipping them would be better13:49
rbasakBut IIRC there's a test restriction or something similar that specifies that the test needs a "built tree"13:49
cjwatsonright, you certainly *can* do that13:49
cjwatsonbut it's better design to avoid it if possible13:49
rbasakThat in theory will mean that no rebuild is required, but in practice we do I think?13:49
cjwatsonespecially if the build is slow13:49
=== jgrimm-out is now known as jgrimm
cariboubdmurray: rbasak: Regarding LP: #1629644, nothing came back from the bug reporter about the potential regression14:35
ubottuLaunchpad bug 1629644 in multipath-tools (Ubuntu) "Trusty: failure to detect device with 0.4.9-3ubuntu7.14" [High,Incomplete] https://launchpad.net/bugs/162964414:35
caribouI have another SRU to upload for multipath-tools, should I just disregard this bug & go on with the new SRU ?14:36
rbasakcaribou: I see no others claiming to be affected in that report or any other reports, so I'd go ahead and disregard.14:37
caribourbasak: thought so too; thanks!14:37
=== mjeanson_ is now known as mjeanson
pitticoreycb: what's the justification for the python-pycadf sync?15:06
coreycbpitti, hi, sorry for the late sync.  it's not critical but the pycadf sync aligns us with the version that upstream has been testing with.  it really just includes a minor typo fix of invalid chars in a config file.15:33
naccsmoser: re: LP: #1632340, we'll need a source patch like 75336788 added15:36
ubottuLaunchpad bug 1632340 in usd-importer "stacktrace fail import cloud-utils" [High,Confirmed] https://launchpad.net/bugs/163234015:36
stgraberpitti: hmm, so could it be that some of that user session work this cycle is causing me to loose all my open windows (as in, all processes die) when some bits of unity crash? it used to be that compiz would crash, respawn and all would be fine, but now it respawns with a clean desktop...15:38
=== masACC is now known as maswan
slangasekstgraber, mdeslaur, infinity, kees: TB meeting in 16; but I suspect infinity is not actually available to chair this week because release?15:44
jderoseinfinity: are you expecting another round of ISO spins now that 4.8.0-22 has landed?15:45
pittistgraber: certainly could be that this is missing some tweaks; the intention is that gnome-session.service is the "session leader", i. e. if that crashes everything is gone; but compiz/unity should actually restart by itself and not take everything else down with it15:55
pittistgraber: mind filing a bug with the details?15:55
xnoxstgraber, i guess unlike upstart, the cgroup is respawned and everything is scoped into the compiz one, instead of patiently waiting for it to come back.15:55
Laneypitti: Isn't it that unity7 is in ubuntu-session.target.requires/ ?15:55
Laney(Not exactly sure what that means with Restart=on-failure though)15:56
pittiyeah, that could be it -- maybe we need Wants=?15:56
stgraberpitti: what should I file that bug against? also not sure how much information I can provide. I suspect you can reproduce it by sending SIGSEG to compiz though.15:58
stgraberobviously, it'd be better if compiz didn't crash, but given that we've failed at making that happen in the past 4 years or so, dealing with it crashing is a good idea :)15:58
pitticoreycb: you're right, the diff is "fairly harmless"16:00
pittistgraber: unity for now (as that ships the file), please assign to me16:02
seb128stgraber, pitti, I doubt it's systemd session, that was reported before we started that transition16:02
* pitti will have a look later, just grabbing some dinner16:03
stgraberseb128: oh? still a yakkety regression though right? pretty sure my xenial desktop respawned compiz properly a couple of days ago16:03
seb128I don't think so16:03
stgrabermaybe a different bug then, I have compiz crashes every week or so and never lost all my windows as a result of it, so something definitely changed16:05
seb128stgraber, bug #1613297 is the one I know about, unsure if that's what you get16:05
ubottubug 1613297 in unity (Ubuntu) "unity --replace crashes/closes some applications (but not all) since 16.04" [High,Triaged] https://launchpad.net/bugs/161329716:05
stgraberseb128: I "think" it's unrelated as I explained in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1632386 just now16:12
ubottuLaunchpad bug 1632386 in unity (Ubuntu) "On yakkety, a unity crash and respawn kills all windows" [Undecided,New]16:12
seb128stgraber, could well be, I just mentioned it in case that was useful16:12
seb128stgraber, do you also have a report about the u-p-s taking compiz down issue?16:13
Pharaoh_AtemI'm getting a weird issue when I attempt to build uw-imap for Ubuntu 14.0416:15
seb128Trevinho, willcooke, ^ is that known? sounds like an annoying one16:15
stgraberseb128: I wish I did but for whatever reason, I don't see any crashes in /var/crash/16:15
Pharaoh_Atemhttps://paste.fedoraproject.org/448671/62025631/16:16
seb128stgraber, get a vt with gdb attached to compiz until next one?16:16
Pharaoh_Atemthe thing is, according to the full build log, the dev packages it's talking about are installed: http://kinginuyasha.enanocms.org/downloads/uw-imap-obsbuild.log16:16
willcookeseb128, not known to me.  But Trevinho is your man16:17
Trevinhoseb128: mhmh... Well it's all due about  the season being dependent on unity 716:17
stgraberseb128: yeah, I'll try to remember to keep that going (I unfortunately reboot this machine very frequently for kernel testing)16:17
Pharaoh_AtemI don't suppose anyone here knows how to fix d-shlib issues?16:18
seb128Trevinho, but unity segfaulting should lead to a respawn, not to a job stop, no?16:18
naccPharaoh_Atem: possibly it's related to: https://lists.debian.org/debian-user/2003/05/msg00029.html16:26
naccPharaoh_Atem: maybe the versions don't match between what is in the package deps and what is in trusty?16:26
Trevinhoseb128: yes....16:30
Pharaoh_Atemnacc: that makes no sense, since the package is rebuilt from trusty universe for trusty16:33
Pharaoh_Atemthe uw-imapd package seems to be broken out of the gate on trusty16:34
naccPharaoh_Atem: so you're just doing a rebuild?16:35
Pharaoh_Atemyes16:35
Pharaoh_Atemour system doesn't have access to ubuntu universe for trusty, so I did an import to rebuild them16:36
gQuigshi there, can someone on the SRU team please review the vlan upload?  (aka, https://launchpad.net/ubuntu/xenial/+queue?queue_state=1)16:39
gQuigsit's from bug - https://bugs.launchpad.net/debian/+source/vlan/+bug/122400716:41
ubottuLaunchpad bug 1224007 in vlan (Ubuntu Xenial) "mtu not always set properly on bond/vlan interface" [Medium,In progress]16:41
naccPharaoh_Atem: hrm, a test rebuild in a trusty schroot worked?16:51
Pharaoh_Atemnacc: that's weird16:51
Pharaoh_Atemit's not like the package set is any different16:51
naccPharaoh_Atem: did you try doing it in a PPA?16:51
Pharaoh_Atemno16:52
Pharaoh_Atemthe only difference between my environment and Launchpad's is probably the lack of updates being applied (because it needs to work with 14.04 base)16:53
infinityjderose: Yes.16:55
jderoseinfinity: okay, thanks! you expect a respin today then?16:56
infinityjderose: Very soon, yes.16:56
powersjinfinity, does that include the server iso?16:56
pittiacross the board, we got a new kernel16:57
pitti(plus other things which affect all flavors/images)16:57
powersjpitti, ok thanks!16:57
* infinity just spent the last half hour "debuggin" why his internet was broken until he realized it was his laptop that was acting up.16:59
infinityI feel smart today.16:59
dokoapw: xfsdump needs the same love as xfsprogs17:04
naccsmoser: did you see my MR feedback?17:53
smoserwhoops17:56
smoserdidn't change commit after i researchdd17:56
smoserfunny17:56
smoserwill fix17:56
smoserpushed17:57
smoserok, now pushed.17:58
naccsmoser: thanks17:58
naccsmoser: merged, with a fixup commit on top, check out master when you can18:01
smoserso what will uyou do about dpkg parsing ?18:01
smoserthat sucks.18:01
naccsmoser: not much i can do18:01
smoserone thing i thought is we could allow for manual18:01
naccwell, beyond the fixup i documented above18:01
smoserin event of parse fail, ask user18:01
naccthat's what hte fixup is, basically18:01
naccah18:01
naccthat won't work for cron :)18:01
smoserno it wont, but we expect it to only ever happen for first run18:02
smoseras new archive tools wont let crap in18:02
naccmaybe18:02
naccwe have a fixup method already, though18:02
nacci'd rather not add a second18:02
smoseroh?18:02
naccyes, i mentioned it above?18:02
naccsmoser: re: LP: #1632340, we'll need a source patch like 75336788 added18:03
ubottuLaunchpad bug 1632340 in usd-importer "stacktrace fail import cloud-utils" [High,Confirmed] https://launchpad.net/bugs/163234018:03
naccsmoser: we have a facility to patch the 'source' from a published version18:03
naccsmoser: and provide a range of versions to which that patch applies18:03
naccas typically it gets fixed eventually18:03
smosernacc, ok. yeah.18:06
naccsmoser: it's the most generic solution rbasak and i could could come up with :)18:06
naccsmoser: i need to run a quick errand, but i can look at what's needed for the source patch after that and hopefully get you something imported by EOD18:07
Pharaoh_Atemnacc: it doesn't seem to work even when OBS is building an Ubuntu VM to do the build: https://build.opensuse.org/package/live_build_log/home:Pharaoh_Atem:u1404_stuff/uw-imap/xUbuntu_14.04/x86_6418:33
Pharaoh_Atemdo you have a build log showing what was installed in the schroot?18:33
chilukthanks jderose for reporting back.19:08
jderosechiluk: np, thanks for the fix!19:08
chilukcyphermox can I get some upload lovin on https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/163147419:15
ubottuLaunchpad bug 1631474 in initramfs-tools (Ubuntu) "No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option" [Undecided,In progress]19:15
cyphermoxchiluk: that seems very wrong to me19:19
chilukok .. one sec..19:19
slangasekupload lovin seems wrong to you?19:19
cyphermoxno, that particular upload lovin'19:20
cyphermoxchiluk: it should be fine to do ip=eth0 or ip=BOOTIF19:20
chilukcorrect.19:21
cyphermoxdoesn't appear to work for me.19:21
chilukI think my fix still works with those.19:21
chilukcyphermox: I'll get back to this in 20 minutes or so.. sorry in a meeting.19:21
cyphermoxif you set ip=eth0, DEVICE is unset.19:21
cyphermoxyou also don't want to set DEVICE=BOOTIF if you got ip=*:...BOOTIF, as "BOOTIF" is just a placeholder for an actual device name19:23
cyphermoxoh, actually19:25
cyphermoxscrew ip=eth0; it's not in that case stanza19:25
cyphermoxbut this appears to break for ip=:::::BOOTIF, I think19:25
chilukright cyphermox.. that's why I doesn't apply.19:40
chiluks/I/it/19:40
chilukI'll look at BOOTIF.. although I don't know if that's a valid use case either.19:40
chilukreally I'd like to completely rewrite the whole configure_networking section at this point.19:41
chilukthere's a lot of failed use cases.19:41
cyphermoxwhich?19:41
cyphermoxI will do rewriting later19:41
chilukfor example :a:b:c:d:device:blah:yada: fails.19:41
chilukbecause it is missed by the ::::*) case statement19:42
chilukit should be :.*:.*:.*:.* o something like that.19:42
cyphermoxit's not meant to be caught by that19:42
chilukor there should be a separate if in the catchall.19:42
chilukalso previously ip=::::eth0:dhcp may have been failing since :dhcp wasn't being stripped.19:43
chilukI tried to keep the fix as minimal as possible so as not to introduce too much change all at once.19:43
cyphermoxI'm not sure that should be supported19:43
chilukI think all things in kernel docs should be supported.19:44
cyphermoxseems to me like all you really need in that case is19:44
cyphermoxif ! echo "${IP}" | grep -q 'BOOTIF\|dhcp$\|any$\|on$'; then19:44
cyphermoxDEVICE="${IP#*:*:*:*:*:*}";19:44
cyphermoxfi19:44
chilukmy kingdom for a bash shell during boot.19:45
chiluk=~ is your friend..19:45
jderosechiluk: hehe :)19:45
chilukcyphermox.. I was starting to look at the upstream debian project for this.. why is Ubuntu so diverged from debian?19:46
chiluklong story?19:46
chilukideally all our changes should go in there.. and then trickle back down.19:46
cyphermoxall we need to care about here is this particular switch case, where one does simple dhcp, until we look at everything else in Z and finish ripping out klibc19:48
cyphermoxthis divergence is because klibc/ipconfig doesn't do IPv6, and we need something that does19:49
cyphermoxso in that aspect, we don't overly need to care about ::::device:proto, because that does to another switch case which just does ipconfig as it did before19:49
cyphermoxmaybe we're missing one :19:50
chilukcyphermox this line NEW_DEVICE=${IP#*:*:*:*:*:*}   should be19:54
chilukNEW_DEVICE=${IP#*:*:*:*:*:}19:54
cyphermoxno19:54
cyphermoxor why?19:55
chilukbecause it's not regex matching right?19:55
chilukI could be wrong on this.19:55
chilukI did want to point it out though.19:55
chilukI checked both and both seem to function..19:55
chilukbut # = strip matching from front.19:56
chilukthe last * matches the device...19:56
chilukdo you know why both work.19:57
cyphermoxI don't20:03
cyphermoxbut we don't need to overthink it if it passes proper testing20:03
chilukyeah I think without the * is more correct in that I think the shell is just trying to be smarter than the user since the final * would match all remaining chars20:04
chilukjust saying.. something I noticed.20:04
cyphermoxwfm20:04
cyphermoxlooks like what you're missing is more or less just handling BOOTIF, and dropping the [ ] around your if20:04
cyphermoxchiluk: so something like this: http://paste.ubuntu.com/23309789/20:05
chilukok.20:06
chilukso that was another thing..20:06
chilukip=BOOTIF wouldn't hit that case stanza at all.20:06
chilukip=:::::BOOTIF would.20:06
cyphermoxyes20:06
chilukbut I'm not sure if that's valid... /me rtfm20:06
cyphermoxit most definitely is20:07
cyphermoxand if it wasn't in the doc, then it was supported before and needs to continue working20:07
nacc_jgrimm: can you or lamont verify LP: #1611923 for x?20:17
ubottuLaunchpad bug 1611923 in python-django (Ubuntu Xenial) "http.request does not support ipv6-formatted ipv4 addresses" [Medium,Fix committed] https://launchpad.net/bugs/161192320:17
chilukyeah cyphermox it's definitely not in the kernel documentation.20:27
chilukI'm checking debian docs now.20:27
=== nacc_ is now known as nacc
balloonsmicahg, you about?21:47
balloonsmwhudson, in order to upload the mongodb to trusty we'll need signoff from the backporter's team. I suspect micahg can help21:48
mwhudsonballoons: ok22:00
mwhudsonballoons: afaict the package meets all the criteria on https://wiki.ubuntu.com/UbuntuBackports so this shouldn't be too big a deal i hope22:00
balloonsmwhudson, ack. So we should mark the bug confirmed then.. Actually I think they may even just upload it22:01
Unit193Except the whole not-enough-backporters thing.22:01
balloonshey Unit193!22:01
Unit193Howdy22:01
mwhudsonballoons: i guess https://bugs.launchpad.net/trusty-backports/+bug/1583740 doesn't explain how it meets the criteria22:02
ubottuLaunchpad bug 1583740 in trusty-backports "mongo client is missing" [Undecided,New]22:02
mwhudsonballoons: might be better to file a fresh bug?22:02
balloonsmwhudson, did you run the backport tool against it?22:03
mwhudsonballoons: no22:03
balloonspresumably that's how the bug was filed eh?22:03
mwhudsonballoons: eh no, that's the same bug as was used for the SRU22:03
balloonsmwhudson, ahh.. Then I agree. File a new bug with the tool.22:03
mwhudsonballoons: i don't know how the trusty-backports task got added22:03
balloonsme neither ;-)22:04
balloonsunless I did it22:04
mwhudsonballoons: you added it!22:04
balloonslol, there it is!22:04
mwhudsonballoons: in june :)22:04
balloonsROFL22:04
mwhudsonballoons: so do you want me to run the requestbackport tool or will you?22:04
balloonsmwhudson, I assume I did which is how it happened, but.. I've no idea at htis point22:05
balloonsmwhudson, please run with it if you can. I really have to EOD22:05
balloonsmwhudson, a new bug, with the tool sounds sanest for everyone22:05
=== zigo is now known as Guest50630
balloonsit's simple to do22:05
mwhudsonballoons: ok22:05
mwhudsonuh why does requestbackport think i want to backport it to xenial as well22:08
mwhudsonheh i haven't actually installed the trusty packages, i guess i should do that :)22:09
* mwhudson afk for 1522:10
=== salem_ is now known as _salem
rbasak7/w #maas23:12

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