psusiso I have noticed that boot time is delayed due to friendly-recovery.service... it is conditioned on recovery being in the kernel command line, which it usually isn't so it doesn't run at all, but it is After=systemd-udev-settle.service and Before=systemd-fsck-root.service, so it delays fscking the root fs until after udev-settle, which takes quite some time01:21
psusicould this be resolved by splitting it into two services, one that is wanted by sysinit, and has the condition, and a second that has the ordering requirements, but is only Wanted by the first service, so if its conditions are evaluated early in boot and found to be false, won't pull in the second service at all, and thus its transitive ordering requirement won't be enforced?01:22
sarnoldpsusi: probably best to file a bug and add the tag systemd-boot, that'll get it to pitti's queue01:27
psusifiled bug, will add tag, thanks01:27
psusiare there plans to move to systemd for user session management ( instead of upstart ) and in the initramfs in wiley?01:28
=== marcusto_ is now known as mr_t_
=== mr_t_ is now known as marcustomlinson
micahgI'm hoping adequate was the last one to fix for perl to migrate from proposed, if not, I'll take another look later05:04
pittimicahg: oh, you fixed lintian? nice, thanks!05:11
pittiGood morning05:11
micahgpitti: good morning, it seems that the fix was in the new version in Debian, just undocumented, I figured to pull the pieces in and get perl migrated and then worry about merging05:12
pittiwgrant: do we have anything like build recipes for git already? I suppose not directly, but can that be faked with putting some shell commands into the recipe or so?05:19
pittiah no, that's just bzr-builder commands05:19
wgrantpitti: No recipes for git yet (they're currently implemented as a bzr plugin), and you can't execute arbitrary shell commands.05:20
wgrantFor some Git repositories you could register a code import to get them into a Bazaar branch, though.05:20
pittiwgrant: yeah, that'd be a fallback; I still need to mess around with the patches somehow, but I think that can be done in debian/rules too; I would mostly just need to change debian/source/format05:30
pitti... and hope that I can get bzr imports of upstream and Debian packaging of systemd05:30
wgrantimports fine05:31
pittiwgrant: other question, PPA buildds have all non-ancient kernels as they are in VMs, right?05:32
wgrantpitti: Yes, the virtual builders are all trusty with vivid sbuild05:32
pittiwgrant: cool, thanks05:34
pittimicahg: "Jenkins Fixed - wily-adt-adequate" \o/06:15
pittimicahg: ah, so that missing pkg-config depends affect Debian too, right?06:15
Unit193Debian #78704306:17
ubottuDebian bug 787043 in adequate "adequate: Adequate needs dependency on pkg-config for new missing-pkgconfig-dependency tag" [Important,Open] http://bugs.debian.org/78704306:17
pittidoko_: FYI, filed bug 1459526 and subscribed you06:23
ubottubug 1459526 in adt-cloud-worker "python2.7 test regression: Tunnel connection failed: 403 Forbidden" [Undecided,New] https://launchpad.net/bugs/145952606:23
dholbachgood morning07:04
dholbachlarsu, HAPPY BIRTHDAY! :-)07:41
* dholbach hugs larsu07:41
* dholbach hugs larsu07:41
* dholbach hugs larsu07:41
larsuthanks dholbach :)07:41
* larsu feels very hugged and hugs back07:41
* seb128 hugs larsu as well :-)07:47
larsuthanks :)07:48
=== davidcalle_ is now known as davidcalle
Laney@pilot in08:15
=== udevbot changed the topic of #ubuntu-devel to: Archive: wily open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> utopic | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: Laney
* dholbach hugs Laney08:16
Laneystill have some procrastination to do first, but the intention is there08:17
* Laney hugs dholbach back08:17
seb128Laney, let's see if didrocks let you some easy ones after his shift on tuesday ;-)08:19
didrocksseb128: I took them ALL! :)08:20
seb128Laney, you are out of luck there, sorry ;-)08:20
didrocksonly hard ones remaining for Laney08:20
didrockshe deserves this! :p08:20
LaneyI can take it!08:20
didrocks*challenge accepted*08:20
* Laney starts from the bottom :-)08:20
pittiI'm piloting tomorrow, don't just leave the sucky ones to me :)08:21
=== doko_ is now known as doko
dokostgraber, known, however I'm still unable to find the issue. not seen in unstable, only in vivid/wily. last known working version is the 5.1 release candidate. for now, I would suggest removing the powerpc binaries09:08
=== MacSlow is now known as MacSlow|lunch
=== mzanetti is now known as mzanetti|run
=== MacSlow|lunch is now known as MacSlow
=== _salem is now known as salem_
=== utlemming is now known as utlemming_away
=== greyback__ is now known as greyback
=== utlemming_away is now known as utlemming
=== utlemming is now known as utlemming_away
=== utlemming_away is now known as utlemming
=== mzanetti|run is now known as mzanetti
rbasakinfinity: around? I'm merging apache2. We've been carrying some changes you uploaded in http://launchpadlibrarian.net/124947541/apache2_2.2.22-6ubuntu3_2.2.22-6ubuntu4.diff.gz for a while. I have a suspicion these are not needed any more, but I don't know how to verify that.13:44
rbasakWhy did we need cross build for apache2 anyway?13:45
infinityrbasak: Because it was on someone's list of "packages that should be cross-buildable".13:47
rbasakinfinity: I think it's all bitrotted now anyway.13:48
infinityrbasak: What proof do you have for that statement? :P13:49
infinityrbasak: I should have forwarded that to Debian (and I thought I did), but there's no reason any of it would have suddenly stopped working.13:49
rbasakinfinity: "Fix cross-building by passing DEB_{HOST,BUILD}_GNU_TYPE to configure" no longer adds the environment variables you defined to the configure line.13:49
infinityrbasak: Hrm, indeed, looks like some bad merges along the way.13:50
* infinity looks at the whole source instead of the delta.13:51
rbasakinfinity: I can re-fix the configure line blindly if you'd like me to, and continue to maintain the delta if you wish. I don't recall ever seeing a merge conflict so it's not particularly awkward. I don't see anything relevant from a quick glance at Debian BTS though.13:52
rbasakinfinity: but if nobody wants it or is using it and it has rotted, maybe that's a reason to save us the trouble and drop the delta?13:52
infinityrbasak: It's not just the configure line.  Someone dropped pretty much my entire delta on a merge at some point.  Probably a blind "well, the hunks don't apply, drop 'em!"13:52
infinityrbasak: Oh, I guess that mpm/module bit got removed entirely...13:54
infinityrbasak: So, just maintaining the 'pass HOST/BUILD to configure' bit should be simple enough, but someone should probably test a cross build to see if it still works.13:54
infinityrbasak: Also a bit confused that debian/patches/086_svn_cross_compiles still applies, given how long ago I backported that from trunk...13:55
rbasakinfinity: 086_svn_cross_compiles still applies> yeah - given it was upstreamed I'd expect it to have arrived by now13:56
infinityrbasak: Anyhow, bad merges notwithstanding, we shouldn't drop the configure bit.  I'll (re-)forward that to Debian, but not until after I've tested that it actually still crosses.  Which I might not get to today, but we'll see.13:57
rbasakinfinity: OK. So for now, shall I fix the configure line and upload my merge?14:02
rbasakinfinity: anyway, I'll do that. Fancy writing a dep8 test to test your cross to stop future rot?14:04
infinityrbasak: I'm not sure DEP-8 tests in every single package to make sure it crosses is the right way to track that. :P14:05
infinityrbasak: A cross-build farm that attempts to cross the entire archive and watch for regressions is the right answer, but needs some tuits of varying roundness.14:05
rbasakinfinity: sure. You can do that instead if you like :)14:08
pittistgraber: ça va !14:29
pittistgraber: so I naïvely tried this:14:30
pittilxc-create -n wily-ppc64el -t download -- -d ubuntu -r wily -a ppc64el14:30
pittilxc-start -n wily-ppc64el -F14:30
pittistgraber: and it fails; but ISTR that LXC had some clever "run under qemu" integration? how do I make that work?14:30
stgraberpitti: oh, you tried that on x86?14:31
pittistgraber: yes, amd6414:31
stgraberyeah, not gonna work :)14:31
stgraberthe only one that vaguely works is armhf and that's when using the good old ubuntu template14:32
pittistgraber: ok; maybe I mixed that up with mk-sbuild or so? I know that we had some way of running a schroot or container or so under qemu14:32
pittistgraber: ah, ok14:32
pittistgraber: ok, so back to looking for a porter box I figure :)14:32
pitti(if only we had sensible schroots on them, but let's see..)14:32
stgraberqemu-user-static sort of works for armhf, so long as you don't use ptrace or netlink (which is already pretty restrictive)14:32
stgraberother arches tend to segfault earlier on14:32
pittistgraber: no, just want to reproduce a build failure14:32
pitti$ sudo apt-get build-dep umockdev14:35
pittiAttributeError: 'apt_pkg.SourceRecords' object has no attribute 'Lookup'14:35
pittimeh, porter box hates me today14:35
pitti(and it builds fine under Debian)14:36
LocutusOfBorg1what did happen to the ppa builders? all "cleaning" state14:37
LocutusOfBorg1are they cleaning the room? :p14:37
pittistgraber: ok, nevermind; abusing a temp container on the ppc64el CI machines; thanks for the explanation!14:39
seb128what should we do when packages are blocked proposed migration on "Boottest result: Regression"15:23
seb128where the error is "EnvironmentError: Unsupported device, autodetect fails device"15:23
seb128e.g https://jenkins.qa.ubuntu.com/job/wily-boottest-address-book-app/lastBuild/console15:24
pittiseb128: I think step 1 is to retry, step 1/2 yell at CI to fix it, step 3 to override15:24
seb128pitti, who in CI do you know?15:24
pittiseb128: ah, that would be "cihelp:" matter15:24
pittiseb128: just talk to the vanguard (they have rotational shifts)15:24
seb128pitti, thanks15:24
Laney@pilot out15:33
=== udevbot changed the topic of #ubuntu-devel to: Archive: wily open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> utopic | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
=== utlemming is now known as utlemming_away
* dholbach hugs Laney15:53
=== utlemming_away is now known as utlemming
LocutusOfBorg1dholbach, do you think I have chances to get sponsored curl and cmake?16:03
LocutusOfBorg1I had some spare time to look at them16:03
LocutusOfBorg1(if you have free time I can do some merges in the next few days)16:04
dholbachLocutusOfBorg1, not right now16:06
dholbachI'm in meeting until 20:00 my time16:06
LocutusOfBorg1no problem at all :)16:08
=== lamont changed the topic of #ubuntu-devel to: Critical components of launchpad are down. | Archive: wily open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> utopic | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
=== oSoMoN_ is now known as oSoMoN
smoserinfinity, what needs to be done to make a vivid-netboot appear at http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/18:27
smoserand then ultimately at all arches and then -updates ?18:27
zygaev: hi18:33
zygaev: canonical irc is down for me18:34
zygaev: have a look at the email I sent18:34
infinitysmoser: I need to upload it.18:34
zygaev: and if you want we can have a quick hangout if you have some questions but don't want to talk on irc18:34
smoserinfinity, can you do that ? and to -updates even ?18:35
infinitysmoser: I can't, since LP is broken. :P18:35
smoseroh yeah. that.18:35
infinitysmoser: But yes, I had planned to finish it off this week.18:35
zygaoh, lp is down too?18:35
sarnoldmuch of LP is down, among other services18:36
* zyga takes note not to trip over those cables the next time18:36
sarnoldirc.canonical.com was listed amont the affected services, but it has continued working for me and many others18:36
sarnoldperhaps just new connections are affected, ldap lookups and so forth18:36
zygasarnold: it doesn't work for me, so perhaps there's some round robin in the loop?18:36
infinitysmoser: The proposed upload will probably happen this afternoon/evening, then like any SRU, it should get some validation before moving it to updates.18:37
infinitysmoser: I'll subscribe you to the SRU bug, so you know when it's accepted, and can perhaps test an arch or two for me.18:39
smoserinfinity, yeah. i can.18:48
Unit193So what would it take to get another ISO built from a seed?21:03
=== salem_ is now known as _salem
=== a|wen is now known as a|wen-
=== a|wen- is now known as a|wen
zygahow can I talk to is while the IRC is down?21:52
Unit193robert_ancell: Re: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1295207 I've been running with those gst1.0 patches since posting my comment there, no crashes.  All else that would need be done is a patch for pidgin-sipe.  This would be a great effort in getting gst0.10 gone! ;)21:53
ubottuUbuntu bug 1295207 in pidgin (Ubuntu) "Migrate to farsight 0.2* / gstreamer 1.0" [Undecided,Confirmed]21:53
wgrantzyga: #canonical-sysadmin21:54
wgrantzyga: What issues are you seeing connecting to IRC?21:55
robert_ancellUnit193, is there a patch / branch for that?21:55
zygawgrant: I want to add a record to the incident report21:57
Unit193robert_ancell: There is, I linked to the Fedora one, and it's been merged into the unreleased upstream 2.x branch (who knows when they'll release), and I have a mostly-merged .11 with it from March(?): https://launchpad.net/~unit193/+archive/ubuntu/test/+sourcepub/4862307/+listing-archive-extra21:57
wgrantzyga: You should still be able to connect to irc.c.c21:58
Unit193robert_ancell: Need to go now though. :321:58
robert_ancellUnit193, ok21:58
zygawgrant: I cannot, since wednesday21:59
wgrantzyga: Uh21:59
wgrantHave you reported this?22:00
zygawgrant: I was super busy (demo day today) so I ignored the problem22:00
zygawgrant: then this happened and I assumed it was the cause22:00
zygawgrant: (no, I have not)22:00
robert_ancellUnit193, I can't seem to download your pidgin changes https://launchpadlibrarian.net/201273988/pidgin_2.10.11-1~vanir1~15.04.debian.tar.xz22:41
Unit193robert_ancell: Launchpad is/was having issues.23:05
robert_ancellUnit193, do you have the patch files? Can you attach to the bug report or send them to me / pastebin them?23:10
Unit193It's been a while, it's all now only on LP. :/23:15
Unit193I can refresh the Fedora one, but it applies with only offsets.23:15
Unit193Dang this is annoying.23:16
robert_ancellUnit193, I just pushed pidgin 2.10.11 so I just need a patch file that appies against that. The one from Fedora has some conflicts23:26
wgrantrobert_ancell, Unit193: It should be working now.23:40
Unit193wgrant: Fantastic, thanks.  Yes it does now. \o/23:41
robert_ancellwgrant, works here, thanks!23:41
robert_ancellUnit193, your package doesn't seem to have any patch for farsight 0.2 - does that seem correct?23:51
robert_ancellah, it is in the gstreamer1.patch. Sorry, missed that.23:53
Unit193robert_ancell: Right, not the best merge ever, but at the time I was doing a quick one to try it in a PPA.23:58
wgrantLaunchpad should be completely OK again. Let me know if anything looks awry.23:58

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