=== wgrant changed the topic of #launchpad to: LP briefly offline for maintenance from 04:00 UTC | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [06:35] Anyone around that can help me take a look at why our new releases build is failing? From what I can tell all is fine up until one of the install files tries to move 2 binaries from usr/local/bin/ to usr/bin.. This has worked no problem in the past [06:38] https://launchpadlibrarian.net/357992526/buildlog_ubuntu-xenial-amd64.smartcash_1.1.1-0xenial1_BUILDING.txt.gz [06:40] One of our previous buildlogs (which was successful) https://launchpadlibrarian.net/353211128/buildlog_ubuntu-zesty-amd64.smartcash_1.1.0rc4-2zesty3_BUILDING.txt.gz [06:46] Pr0t3us: Have you tried to reproduce the problem locally? [06:46] Nothing jumps out at me. [06:47] Yea, I can't reproduce it locally. Seems to build fine.. Really don't know what I'm doing wrong on this one. [06:49] The smartcashd.install file seems to be where it's failing but that file hasn't changed at all and I can see it install the file to usr/local/bin/ in the build log, right? [06:58] Yeah, exactly. It's a bit weird. [06:58] Might be worth sticking a "find debian/tmp" in there, or turning on dh verbose mode, or similar. [07:03] do you think if i made it debian/tmp/usr/local/bin/smartcashd in the install file it would work ? [07:10] Pr0t3us: I don't think so. === trevorj_ is now known as trevorj === rmk` is now known as rmk === DalekSec_ is now known as DalekSec === cjwatson_ is now known as cjwatson === stub` is now known as stub [12:38] hi, I got 2 random launchpad emails this morning with the subject "Launchpad internal error" and the text "Launchpad encountered an internal error during the following operation: unspecified operation. It was logged with id OOPS-5a001bc4ef552abf7d00754f55a4dc0a. Sorry for the inconvenience." [12:38] https://oops.canonical.com/?oopsid=OOPS-5a001bc4ef552abf7d00754f55a4dc0a [12:38] the second one had a different oops code [12:38] I've got no idea what that was in response to [12:38] (it was before I started work) [12:49] Looks like that job has been running since aurora's reboot and is very confused. Let me get it restarted [13:06] cjwatson, thanks (I received a third similar message just before you responded) [13:07] Yeah, I saw that the OOPS had some more recent instances [13:08] Hello! Sorry to interrupt. Got a user that posts spam in bugs, being going on for a while already, question on LP Answers was ignored. User https://launchpad.net/~xxx-man82, sample comment https://bugs.launchpad.net/ubuntu-ru/+bug/358351/comments/31 . Thank you for attention! [13:08] Ubuntu bug 358351 in Russian Ubuntu Projects "Использовать рассылки в рабочих группах" [Medium,Fix released] [13:08] Forst: can you link to the question on LP answers for me? [13:09] chrisccoulson: kind of hard for me to tell what's going on though since some imports are super-slow. which reminds me, I had a branch somewhere to make the logging a bit more useful ... [13:09] cjwatson: https://answers.launchpad.net/launchpad/+question/615863 [13:10] Forst: I'll deal with that now, thanks. sorry for missing it [13:10] Thank you very much! [13:10] I really must see if we can turn off expiry of questions for our own answers area [14:16] hello, is is a bad time to upload long lasting builds currently? it seems some of mine just stopped without a log e.g. https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+build/14383177 [14:27] We had some network saturation recently, which may have killed a few builds. Just retry [14:30] ok, done, I hope it will work out again [16:14] Can anyone help me? I'm still unable to build.. Can't figure out what the problem is [16:14] https://launchpadlibrarian.net/358019047/buildlog_ubuntu-xenial-amd64.smartcash_1.1.1-3xenial4_BUILDING.txt.gz [16:25] Pr0t3us: Looks like you're installing /usr/local/bin/smartcashd etc., but your debian/smartcashd.install refers to /usr/local/smartcashd. Missing bin/ [16:26] Thanks, I just noticed that too which was me just trying anything I can. /usr/local/bin/smartcashd also does not work which it always has [16:26] Pr0t3us: Also, your build is likely to fail a bit later since we generally forbid packages installing into /usr/local. Should just use /usr/bin, --prefix=/usr etc. [16:27] We really didn't change anything that would mess that up. here's one with the file path correct and still failed - https://launchpadlibrarian.net/357992526/buildlog_ubuntu-xenial-amd64.smartcash_1.1.1-0xenial1_BUILDING.txt.gz [16:27] Well the install places it in usr/bin [16:27] right? [16:27] it really doesn't. look like 20 lines up! [16:27] libtool: install: /usr/bin/install -c smartcashd /<>/debian/tmp/usr/local/bin/smartcashd [16:29] hmm [16:29] I appreciate your help [16:30] one thing I would recommend is replacing the call to ./configure CPPFLAGS=... in debian/rules with dh_auto_configure -- CPPFLAGS=... [16:30] that way, you'll get all the usual defaults [16:30] I suspect that's a lot of your problem [16:30] Okay, I'll try that [16:30] you should then change debian/smartcashd.install to read as follows: [16:30] usr/bin/smartcashd [16:31] usr/bin/smartcash-cli [16:31] and similarly with your other .install files [16:31] the .install lines that don't relate to /usr/bin/ can stay as-is [16:32] So just remove the local like - [16:32] usr/bin/smartcashd usr/bin [16:32] no [16:32] or remove the usr/bin as well ? [16:32] you don't need the target directory if it's just the same as the source directory structure [16:33] so I mean "usr/bin/smartcashd usr/bin" would work, but it's redundant, "usr/bin/smartcashd" is all you need there [16:34] check for any other references to usr/local in your debian/ tree before you upload, and ideally try a test build locally first - you should have been able to reproduce this identical bug in sbuild [16:34] and iterating locally is generally less frustrating than iterating via even the best remote service, once you get it working [18:05] cjwatson: I tried your suggestions and unfortunately it's still not working. Still shows "not found" when trying to run the smartcashd.install and pull files [18:06] Wait, I think I may have just found something [18:07] tried locally I guess? I don't see it in your PPA yet [18:08] Tried locally and then tried on PPA but with what I pushed to PPA I still had /usr/local/bin/ and it looks like it was installing to usr/bin/ like you said (when using dh_auto_configure) [18:08] https://launchpadlibrarian.net/358071441/buildlog_ubuntu-artful-amd64.smartcash_1.1.1-1artful2_BUILDING.txt.gz [18:09] Putting in the right filepath now (usr/bin/smartcashd) and trying again [18:10] right, that just looks like you forgot the .install changes [18:10] the configure change has worked [18:10] Yea, trying again now with the .install changes. Thanks again for the help [18:10] np [18:10] You're the best, seriously. I have a panicked team and 9000+ nodes waiting to update using this PPA [18:10] I'm feeling the pressure lol [18:10] yikes [18:12] whoa, our build farm is not happy at the moment either [18:17] Overloaded ? [18:18] no, outage induced by a compute node reboot I think [18:20] cjwatson: not a good time to upload 140 packages then? [18:21] I'll wait..... [18:21] lol [18:21] actually 195 [18:21] * acheronuk_ hides === acheronuk_ is now known as acheronuk [18:22] acheronuk_: should be sorted soon hopefully, up to you === pbek_ is now known as pbek [18:41] * ricotz hopes this doesn't break the ones currently running [18:44] no, it won't [19:13] Still waiting for build to start, going to be a while? [19:13] it might, it might not. impossible to reliably guess I think. [19:14] eww [19:14] cjwatson: build farm exploded? [19:15] Pr0t3us: i'm going to err on the side of caution and say "Hes it will be a while" [19:15] Yes* [19:23] no need to highlight me, please, doing what I can amid cooking dinner [19:23] comments in scrollback still apply [19:25] i showed up and don't have scrollback, so my apologies :) [19:25] * teward kicks his ZNC for failing to send him scrollback [19:26] https://irclogs.ubuntu.com/2018/02/22/%23launchpad.html exists [20:02] builders coming back now [20:03] w00t :) [20:03] :D [20:29] Damn :/ still the same issue even with .installs updated.. https://launchpadlibrarian.net/358088709/buildlog_ubuntu-xenial-amd64.smartcash_1.1.1-5xenial6_BUILDING.txt.gz [20:30] When I build it locally it fails the same way but then has debian/tmp/usr/bin/ with all of the binaries there so I know it's completing the build, just not packaging the deb.. Makes no sense [21:17] Pr0t3us: ok, give me a few minutes [21:20] Thank you again cjwatson [21:35] just waiting for the build to get that far here [21:55] any luck? [21:56] still building - not the fastest in the world when my laptop's on battery and so throttled back [21:59] (it's nearly 10pm here, so I'm mostly doing housework) [22:03] I really don't know what else to try... wgrant mentioned trying to put a "find debian/tmp" in but where would I put that? in the .install files? [22:04] It's weird that we're having this problem. We never did previously and none of the src code changes should affect this part of the build process (packaging) [22:05] that'd go in debian/rules, but at this point it's probably faster to wait for my build to finish here ... [22:05] Okay, definitely. [22:17] sigh, really should've used -j4 [22:34] aha! [22:34] Pr0t3us: your problem is that most of the files in debian/ have mysteriously become executable [22:34] presumably Windows damage [22:35] Pr0t3us: in your case, only debian/rules should actually be executable; none of the other files are scripts. but if they're executable, recent versions of debhelper will try to execute them [22:36] wow i dont know how that happened. I don't use windows [22:36] Fixing now [22:36] Thank you so much again [22:36] so the reason it's saying that usr/bin/smartcashd doesn't exist is that it's trying to execute debian/smartcashd.install as a shell script, and that's the first word of the first line. but it's executed at the top level of the package, rather than using dh_install's logic for picking files out of debian/tmp/ [22:36] no problem, pesky +x bits can be hard to spot