/srv/irclogs.ubuntu.com/2018/02/22/#launchpad.txt

=== 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
Pr0t3usAnyone 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 past06:35
Pr0t3ushttps://launchpadlibrarian.net/357992526/buildlog_ubuntu-xenial-amd64.smartcash_1.1.1-0xenial1_BUILDING.txt.gz06:38
Pr0t3usOne of our previous buildlogs (which was successful) https://launchpadlibrarian.net/353211128/buildlog_ubuntu-zesty-amd64.smartcash_1.1.0rc4-2zesty3_BUILDING.txt.gz06:40
wgrantPr0t3us: Have you tried to reproduce the problem locally?06:46
wgrantNothing jumps out at me.06:46
Pr0t3usYea, I can't reproduce it locally. Seems to build fine.. Really don't know what I'm doing wrong on this one.06:47
Pr0t3usThe 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:49
wgrantYeah, exactly. It's a bit weird.06:58
wgrantMight be worth sticking a "find debian/tmp" in there, or turning on dh verbose mode, or similar.06:58
Pr0t3usdo you think if i made it debian/tmp/usr/local/bin/smartcashd in the install file it would work ?07:03
wgrantPr0t3us: I don't think so.07:10
=== 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
chrisccoulsonhi, 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
ubot5https://oops.canonical.com/?oopsid=OOPS-5a001bc4ef552abf7d00754f55a4dc0a12:38
chrisccoulsonthe second one had a different oops code12:38
chrisccoulsonI've got no idea what that was in response to12:38
chrisccoulson(it was before I started work)12:38
cjwatsonLooks like that job has been running since aurora's reboot and is very confused.  Let me get it restarted12:49
chrisccoulsoncjwatson, thanks (I received a third similar message just before you responded)13:06
cjwatsonYeah, I saw that the OOPS had some more recent instances13:07
ForstHello! 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
ubot5Ubuntu bug 358351 in Russian Ubuntu Projects "Использовать рассылки в рабочих группах" [Medium,Fix released]13:08
cjwatsonForst: can you link to the question on LP answers for me?13:08
cjwatsonchrisccoulson: 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
Forstcjwatson: https://answers.launchpad.net/launchpad/+question/61586313:09
cjwatsonForst: I'll deal with that now, thanks.  sorry for missing it13:10
ForstThank you very much!13:10
cjwatsonI really must see if we can turn off expiry of questions for our own answers area13:10
ricotzhello, 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/1438317714:16
cjwatsonWe had some network saturation recently, which may have killed a few builds.  Just retry14:27
ricotzok, done, I hope it will work out again14:30
Pr0t3usCan anyone help me? I'm still unable to build.. Can't figure out what the problem is16:14
Pr0t3ushttps://launchpadlibrarian.net/358019047/buildlog_ubuntu-xenial-amd64.smartcash_1.1.1-3xenial4_BUILDING.txt.gz16:14
cjwatsonPr0t3us: Looks like you're installing /usr/local/bin/smartcashd etc., but your debian/smartcashd.install refers to /usr/local/smartcashd.  Missing bin/16:25
Pr0t3usThanks, I just noticed that too which was me just trying anything I can. /usr/local/bin/smartcashd also does not work which it always has16:26
cjwatsonPr0t3us: 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:26
Pr0t3usWe 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.gz16:27
Pr0t3usWell the install places it in usr/bin16:27
Pr0t3usright?16:27
cjwatsonit really doesn't.  look like 20 lines up!16:27
cjwatsonlibtool: install: /usr/bin/install -c smartcashd /<<PKGBUILDDIR>>/debian/tmp/usr/local/bin/smartcashd16:27
cjwatsonhmm16:29
Pr0t3usI appreciate your help16:29
cjwatsonone thing I would recommend is replacing the call to ./configure CPPFLAGS=... in debian/rules with dh_auto_configure -- CPPFLAGS=...16:30
cjwatsonthat way, you'll get all the usual defaults16:30
cjwatsonI suspect that's a lot of your problem16:30
Pr0t3usOkay, I'll try that16:30
cjwatsonyou should then change debian/smartcashd.install to read as follows:16:30
cjwatsonusr/bin/smartcashd16:30
cjwatsonusr/bin/smartcash-cli16:31
cjwatsonand similarly with your other .install files16:31
cjwatsonthe .install lines that don't relate to /usr/bin/ can stay as-is16:31
Pr0t3usSo just remove the local like -16:32
Pr0t3ususr/bin/smartcashd usr/bin16:32
cjwatsonno16:32
Pr0t3usor remove the usr/bin as well ?16:32
cjwatsonyou don't need the target directory if it's just the same as the source directory structure16:32
cjwatsonso I mean "usr/bin/smartcashd usr/bin" would work, but it's redundant, "usr/bin/smartcashd" is all you need there16:33
cjwatsoncheck 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 sbuild16:34
cjwatsonand iterating locally is generally less frustrating than iterating via even the best remote service, once you get it working16:34
Pr0t3uscjwatson: I tried your suggestions and unfortunately it's still not working. Still shows "not found" when trying to run the smartcashd.install and pull files18:05
Pr0t3usWait, I think I may have just found something18:06
cjwatsontried locally I guess?  I don't see it in your PPA yet18:07
Pr0t3usTried 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
Pr0t3ushttps://launchpadlibrarian.net/358071441/buildlog_ubuntu-artful-amd64.smartcash_1.1.1-1artful2_BUILDING.txt.gz18:08
Pr0t3usPutting in the right filepath now (usr/bin/smartcashd) and trying again18:09
cjwatsonright, that just looks like you forgot the .install changes18:10
cjwatsonthe configure change has worked18:10
Pr0t3usYea, trying again now with the .install changes. Thanks again for the help18:10
cjwatsonnp18:10
Pr0t3usYou're the best, seriously. I have a panicked team and 9000+ nodes waiting to update using this PPA18:10
Pr0t3usI'm feeling the pressure lol18:10
cjwatsonyikes18:10
cjwatsonwhoa, our build farm is not happy at the moment either18:12
Pr0t3usOverloaded ?18:17
cjwatsonno, outage induced by a compute node reboot I think18:18
acheronuk_cjwatson: not a good time to upload 140 packages then?18:20
acheronuk_I'll wait.....18:21
Pr0t3uslol18:21
acheronuk_actually 19518:21
* acheronuk_ hides18:21
=== acheronuk_ is now known as acheronuk
cjwatsonacheronuk_: should be sorted soon hopefully, up to you18:22
=== pbek_ is now known as pbek
* ricotz hopes this doesn't break the ones currently running18:41
cjwatsonno, it won't18:44
Pr0t3usStill waiting for build to start, going to be a while?19:13
tewardit might, it might not.  impossible to reliably guess I think.19:13
tewardeww19:14
tewardcjwatson: build farm exploded?19:14
tewardPr0t3us: i'm going to err on the side of caution and say "Hes it will be a while"19:15
tewardYes*19:15
cjwatsonno need to highlight me, please, doing what I can amid cooking dinner19:23
cjwatsoncomments in scrollback still apply19:23
tewardi showed up and don't have scrollback, so my apologies :)19:25
* teward kicks his ZNC for failing to send him scrollback19:25
cjwatsonhttps://irclogs.ubuntu.com/2018/02/22/%23launchpad.html exists19:26
cjwatsonbuilders coming back now20:02
Pr0t3usw00t :)20:03
acheronuk:D20:03
Pr0t3usDamn :/ still the same issue even with .installs updated.. https://launchpadlibrarian.net/358088709/buildlog_ubuntu-xenial-amd64.smartcash_1.1.1-5xenial6_BUILDING.txt.gz20:29
Pr0t3usWhen 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 sense20:30
cjwatsonPr0t3us: ok, give me a few minutes21:17
Pr0t3usThank you again cjwatson21:20
cjwatsonjust waiting for the build to get that far here21:35
Pr0t3usany luck?21:55
cjwatsonstill building - not the fastest in the world when my laptop's on battery and so throttled back21:56
cjwatson(it's nearly 10pm here, so I'm mostly doing housework)21:59
Pr0t3usI 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:03
Pr0t3usIt'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:04
cjwatsonthat'd go in debian/rules, but at this point it's probably faster to wait for my build to finish here ...22:05
Pr0t3usOkay, definitely.22:05
cjwatsonsigh, really should've used -j422:17
cjwatsonaha!22:34
cjwatsonPr0t3us: your problem is that most of the files in debian/ have mysteriously become executable22:34
cjwatsonpresumably Windows damage22:34
cjwatsonPr0t3us: 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 them22:35
Pr0t3uswow i dont know how that happened. I don't use windows22:36
Pr0t3usFixing now22:36
Pr0t3usThank you so much again22:36
cjwatsonso 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
cjwatsonno problem, pesky +x bits can be hard to spot22:36

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