Odd_Blokecjwatson: Can you remind me how a version passed to a livefs requestBuild call should manifest itself within the live-build?  I thought it was as $BUILDSTAMP, but I'm not seeing that...12:37
cjwatsonOdd_Bloke: It's $NOW in the environment of the build; live-build sanitises the environment, so livecd-rootfs stuffs BUILDSTAMP="$NOW" into config/binary13:14
cjwatsonSo depends where you're looking from13:14
Odd_Blokecjwatson: Ack, thanks; looks like a bug in our tooling which was throwing me off. :)13:29
=== coreycb` is now known as coreycb
Odd_BlokeNone of the builds for the latest upload (via recipe) in https://launchpad.net/~cloudware/+archive/ubuntu/cpc-livecd-rootfs/+packages are getting queued; anyone know what's up?15:10
Odd_BlokeAh, looks like they're getting queued now. :)15:14
cjwatsonLet me poke some builders a bit on general principles15:15
Odd_BlokeI requested livefs #50000, do I win a prize?17:00
Odd_Bloke"You've won a brand new ... <opens box> ... log describing your build failure!"17:00
Odd_Blokecjwatson: FWIW, I'm seeing the builds for that recipe (https://code.launchpad.net/~cloud-images-release-managers/+recipe/cloud-image-sauce) queued despite available builders again.17:48
Odd_Blokecjwatson: If that's just the way it is, that's not a problem at all; just flagging it up in case that indicates something being broken. :)17:48
cjwatsonOdd_Bloke: I can't see these, so are these builds using a private archive?17:51
cjwatsonor into a private archive, rather17:51
Odd_Blokecjwatson: Yes, they are.17:52
cjwatsonOdd_Bloke: right, so private PPA builds are special17:52
Odd_BlokeOK, cool.17:52
cjwatsonOdd_Bloke: we don't have the necessary things hooked up for them to be able to be granted tokens to access private files directly in the librarian; instead we have to wait for the source to be published in the PPA, and then we can start building them17:53
cjwatsonOdd_Bloke: so it all takes an extra publisher cycle vs. normal17:53
Odd_BlokeAhhh, OK.17:53
sergio-br2any news about git repo support on recipes?18:40
dobeysergio-br2: it's beta now18:51
sergio-br2dobey, how can I do a git-git import on launchpad?19:00
sergio-br2basically I want to clone a github repo, and maintain it sync19:02
sergio-br2or, is it possible to use recipes with external git repos? like github?19:07
dobeysergio-br2: i don't know19:25
cjwatsonsergio-br2: I'm afraid we don't do git-to-git imports yet, though we'd like to, it's on the wishlist.  at best you just have to mirror things manually21:00
sergio-br2hi cjwatson21:00
sergio-br2like git pull && git push ?21:00
cjwatsonsergio-br2: recipes only work with repositories hosted in LP (fairly fundamentally), so there's an obvious link there21:00
sergio-br2mirroring is what I'm looking21:01
cjwatsonsergio-br2: maybe push --mirror, but yes, that general idea.  acknowledge it's not great21:01
cjwatsonsergio-br2: we know roughly what we need to do to get mirroring going but it hasn't been started yet21:01
sergio-br2can I use a git repo, and nest it with a debian repo (bzr) ?21:02
sergio-br2or the debian repo needs to be git too ?21:03
cjwatsonthey all need to be the same VCS21:05
sergio-br2bzr: ERROR: unknown command "fast-export"21:33
sergio-br2bzr fast-export --export-marks=../marks.bzr ../old-bzr-branch | git fast-import --export-marks=../marks.git21:33
sergio-br2that tutorial is wrong i guess21:33
sergio-br2bzr: ERROR: no such option: --export-marks21:34
sergio-br2oh, it's missing a package21:37
sergio-br2failed to build :/22:58
sergio-br2and there's no log22:58
cjwatsonsergio-br2: Yes, just investigating that as soon as I get a sysadmin's attention - https://bugs.launchpad.net/launchpad/+bug/153827622:59
ubot5Launchpad bug 1538276 in Launchpad itself "git recipe failed to build without showing buildlog" [Undecided,New]22:59
sergio-br2I'm pretty sure it's right23:01
sergio-br2it's building here23:01
cjwatsonIt's just a problem with the base image being booted by the buildds you happened to hit23:02
cjwatsonWe can't see the logs for the process that updates those, unfortunately, so it's a bit of an arm's-length-guesswork game to make sure they're all updated23:02
sergio-br2I guess {revno:packaging} will not work for git right?23:04
sergio-br2could I do {revtime:packaging} ?23:04
cjwatsonrevno will work23:05
cjwatsonsee the docs23:05
cjwatsonit's a bit of a hack, but it does work23:05
sergio-br2what it'll get?23:05
cjwatsonwe take the length of the left-hand-parent history of the commit23:05
cjwatsonwhich is a decent emulation, and it's useful to have a simple monotonically-increasing value you can use there23:05
cjwatsonyou certainly can use {revtime:packaging} instead, it just gets rather long23:05
cjwatsonthis is documented near the end of https://help.launchpad.net/Packaging/SourceBuilds/Recipes#Version_numbers_and_substitution_variables23:06
sergio-br2so there's no way this number get less right?23:08
sergio-br2cjwatson, nest packaging lp:~dolphin-emu/+git/debian-master-trusty debian23:12
sergio-br2is it right?23:12
sergio-br2or do I need do this:23:12
sergio-br2nest packaging lp:~dolphin-emu/+git/debian-master-trusty master debian23:12
cjwatsonget less> revno will always increase unless you do a non-fast-forward push23:13
sergio-br2the main git repo needs the "master", the nest needs it too right?23:14
cjwatsonsergio-br2: if you need to specify a branch name, it needs to go at the end ("nest packaging lp:~dolphin-emu/+git/debian-master-trusty debian master") - slightly weird but a consequence of following the existing recipe format which put an optional commit identifier in that position.  But you can omit "master" and you'll get whatever HEAD for that repository is, which is usually master23:14
cjwatsonsergio-br2: this is true for the main repository as well, you can leave out the branch name and get HEAD, though I would say it's normally clearer to include a branch name23:15
sergio-br2yeah, for the main I saw it was optional23:15
cjwatsonsergio-br2: especially since "debian-master-trusty" is a very weird repository name - it implies that a future "debian-master-xenial" would be a separate repository, whereas surely you would want those to be different branches of the same repository23:16
cjwatsonputting series in git repository names is usually a mistake23:16
cjwatsonyou can if you like, it's just odd :)23:16
sergio-br2didn't understand cjwatson23:23
sergio-br2ok, the recipe is working now23:31
sergio-br2but I have this unmet deps23:32
cjwatsonsergio-br2: I was talking about lp:~dolphin-emu/+git/debian-master-trusty, not lp:~dolphin-emu/+git/dolphin23:32
sergio-br2I'm pretty sure I work-a-rounded it by changing the PPA deps, using the Security option23:32
cjwatsonunmet deps are entirely your problem, they work the exact same way for bzr/git23:33
sergio-br2the series you mean "trusty", cjwatson ? I need 3 different deb packages for dolphin23:33
sergio-br2but it was working with the other ppa23:33
cjwatsonsergio-br2: trusty is an example of a series, yes23:33
cjwatsonsergio-br2: my point is that trusty/xenial/etc. should normally be a branch within a git repository, not in the git repository name23:34
sergio-br2seriously, why they updated this gcc-4.9-base23:34
sergio-br2oh, right cjwatson23:34
sergio-br2yeah, I'm used to do it cjwatson23:34
sergio-br2with bazaar23:34
cjwatsoneh, I'm not sure that an update of gcc-4.9-base was your problem23:35
cjwatsonlet me look into it, modulo children's bedtime23:35
sergio-br2it's the problem23:35
sergio-br2someone thought it was a good idea to update it23:35
cjwatsonin YOUR PPA23:35
sergio-br2even if 14.04 has no full 4.9 support...23:36
cjwatsonI mean, that's kind of what it's complaining about ...23:36
sergio-br2It was working until this update cjwatson23:36
sergio-br2I noticed this update 2 weeks ago23:36
cjwatsonwhy did you put it in https://code.launchpad.net/~dolphin-emu/+archive/ubuntu/tmp2/+packages in the first place?23:36
sergio-br2because I'm testing23:36
cjwatsonwhat was the failure without that?23:36
sergio-br2there's was no failure at all, before23:37
cjwatsonthe update of gcc-4.9 in trusty-updates can't possibly be related, because this build log doesn't have -updates enabled23:38
sergio-br2yeah, I'm using security only23:39
cjwatsonso what update are you talking about that broke things?23:39
sergio-br2so from where this 4.9.3 is appearing?23:40
cjwatsonit's in your PPA23:41
cjwatsonyou put it there23:41
cjwatsonyour recipe points at it23:41
sergio-br2my PPA is using 4.9.223:41
cjwatsonhttps://code.launchpad.net/~dolphin-emu/+archive/ubuntu/tmp2/+packages disagrees23:42
sergio-br2it's getting from tmp2 ? why...23:42
cjwatsonthat's what https://code.launchpad.net/~dolphin-emu/+recipe/dolphin-daily-trusty points to23:42
cjwatsonunder "Daily build archive" (hover over the link)23:42
sergio-br2ok, tmp2 has 4.9.323:43
sergio-br2but I thought tmp2 can't get packages from its own23:43
cjwatsonand the reason it doesn't work is that you need to backport (at least) isl as well23:43
sergio-br2let's delete this23:43
cjwatsonor just point your recipe at the PPA you actually want to use for it23:44
sergio-br2ok, now it failed without log heh23:47

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