/srv/irclogs.ubuntu.com/2016/03/15/#ubuntu-release.txt

=== maclin1 is now known as maclin
ginggsWould someone look at an FFE for me please? LP: #155558608:46
ubot5Launchpad bug 1555586 in lazarus (Ubuntu) "FFe: Sync lazarus 1.6+dfsg-1 (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/155558608:46
dokoginggs, done. please close the issue once built08:49
ginggsdoko: danke08:50
dokowhen I'm looking at http://archive.ubuntu.com/ubuntu/dists/xenial/Contents-amd64.gz searching for vendor_ruby/2.2, I still see a lot of matches, while most of these packages were updated. why?09:06
ginggsWould someone please look at another FFe to fix FTBFS please? LP: #155752714:19
ubot5Launchpad bug 1557527 in doublecmd (Ubuntu) "FFe: Sync doublecmd 0.7.0-1 (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/155752714:19
mdeslaurcan someone please denew lynx? it's lynx-cur that got renamed16:14
mdeslaurjdstrand: perhaps you? ^16:14
jdstrandmdeslaur: looking16:36
mdeslaurjdstrand: thanks16:36
jdstrandmdeslaur: ok it is building in xenial-proposed: https://launchpad.net/ubuntu/+source/lynx/2.8.9dev8-4. I also moved it so main since lynx-cur was in main in wily16:39
mdeslaurjdstrand: great, thanks16:39
jdstrandidr if the binaries will have to be moved to main if the source already is. need to keep an eye on that. will need a binNEW as well16:39
jdstrandmdeslaur: hmm, it seems to be ftbfs16:40
mdeslaurjdstrand: ah crud, I'll take a look, thanks16:40
jdstrandnp16:41
seb128https://bugs.launchpad.net/ubuntu/+source/wxwidgets3.0/+bug/1329779 needs a ffe right?18:06
ubot5Launchpad bug 1329779 in wxwidgets3.0 (Ubuntu) "[ffe] Sync from Debian Unstable | Migrate to gstreamer 1.0" [High,Confirmed]18:06
seb128it's about migrating wxwidgets3 from gstreamer 0.10 to 1.018:06
seb128which is a non trivial change18:06
seb128Bryan Quigley argued on the bug that it's a "bugfix" change but it doesn't really sounds like one18:07
slangasekseb128: I would agree that it's FFe material18:23
seb128slangasek, thanks18:23
seb128I've updated it to be one18:25
tewardso, i've got a pending nginx bug that needs FFe review before I upload; it's been there for about a month, and appears stuck somewhere in the queue, can anyone look at it?20:12
infinityteward: #?20:13
tewardit'd help if i weren't putting all my RAM to pending sbuild runs, standby20:13
tewardhttps://bugs.launchpad.net/ubuntu/+source/nginx/+bug/154934720:13
ubot5Launchpad bug 1549347 in nginx (Ubuntu) "[FFe Requested] Please update nginx to 1.9.12" [Undecided,New]20:13
tewardupload is ready to go, but i didn't want to upload without a review done (to avoid getting yelled at).  WOuld have asked earlier, but was ill the past week or so, which prevented it,20:13
infinityteward: Commented.20:15
tewardinfinity: thanks, as soon as the three workflow scripts which are running sbuilds for other things here are done, and extra cycles and RAM released back to the system, i'll upload.  :)20:16
tewardhmm, that's new, infinity can you take a peek at this and give insights?  https://launchpadlibrarian.net/248257573/buildlog_ubuntu-xenial-s390x.nginx_1.9.12-0ubuntu1_BUILDING.txt.gz20:25
* infinity raises his eyebrow.20:25
* teward has never seen a "cannot fork" error in any nginx build on any arch, even in Debian archs20:26
cjwatsonI'd guess accidental forkbomb.20:26
tewardhmm20:26
infinityIndeed, but curious that it would accidentally bomb only one arch.20:26
infinityThe machine looks fine, though.20:26
cjwatsonLogic error in configure?20:27
infinityIma give it another try and hope for random luck.20:27
* teward starts scanning upstream redmine for weird arch config issues, just in case20:27
tewards/redmine/trac/20:27
infinitycjwatson: CANNOT UTIME.20:28
infinityI'm afraid that error message has forever ruined the word "cannot" for me.  At least, when it comes from a computer.20:29
infinityteward: Looks fine on a second pass, so whatever accidental bomb is in there, it's nondeterministic (and probably not arch-specific).20:31
infinityWhee.20:31
* teward shrugs20:32
tewardinfinity: it's odd, every other upload appears to get a nondeterministic failure for some odd reason20:32
tewardand it's never the same arch :/20:32
infinityThe sign of a quality upstream.20:32
tewardthe nondeterministic failures I've seen are all ddeb related :/20:32
tewardnever had it blow up in the configure stages20:32
infinityOh.  The sign of a quality distro? :)20:33
infinity(or you have improper recipe dependencies in your debian/rules, which is more likely)20:33
tewardpossibly, though it seems to be a recurring issue.  The debian/rules is essentially verbatim from Debian, minus http2 stuff per sec team request20:34
infinityOh look, that issue just hit your armhf build.20:34
tewardindeed20:34
* infinity doesn't retry it.20:34
tewardheheh20:34
infinityNot yet anyway.20:34
tewardi'm going to let the others finish first :)20:34
tewardthey'll either blow up, or succeed, then retry :)20:35
* teward appears to have a 'retry build' button :)20:35
infinityYeah, I'm intentionally not retrying, so I can sucker pitti into looking at it.20:36
infinityIt could well be a race in pkg-create-dbgsym.  Or it could be your fault.20:36
tewardI wonder if it's a race, or if it's in the way the system runs - at one point I think you said it may be a result of how the rules define how the build should run, but that was long enough ago I lost logs20:36
infinityteward: See #-devel.  It's a bug in pkg-create-dbgsym that it doesn't have better locking, but could be worked around by not attempting to be so agressively parallel.  *shrug*20:42
tewardinfinity: splitting time across five windows, standbly20:42
tewardinfinity: ack20:42
tewardI'm curious why Debian is being aggressive with parallel builds, that part's from them20:43
tewardi think I'll poke them, and see if there's a specific reason they did it that way, before adding to the delta further20:43
infinityteward: Nah, I wouldn't worry about it.  I think I'm getting a handle on why out tooling sucks.20:52
infinitys/out/our/20:52
tewardindeed.  *is watching #-devel himself*20:52
=== Guest93664 is now known as med_
flexiondotorginfinity, Any news on Base?23:10
infinityflexiondotorg: Not yet.  Patience (and slightly less pinging).23:11
flexiondotorginfinity, OK. I was only pinging because I thought that was the instruction. I'll back off.23:11

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