[18:29] <LocutusOfBorg1> I wish you a nice new year!
[19:14] <teward> stupid question, but is there a way to refer to the version string used in the Debian changelog during building in a rules file?  (such that a variable could extract the value of whatever the version string was on the changelog entry)
[19:15] <tumbleweed> teward: dpkg-parsechangelog
[19:16] <teward> tumbleweed: thank you!
[20:10] <teward> tumbleweed: is that able to be used during the actual building of the binaries in the rules file to extract the version for use in a later flag passed to 'go' for building?  From what testing I'm doing, I'm seeing nothing in that variable (I have the rules file echoing the output to the log during build, and it's showing nothign...(
[20:12] <tumbleweed> teward: it's a command, not a variable
[20:13] <teward> tumbleweed: i know this
[20:14] <teward> tumbleweed: trying to put it INTO a variable
[20:14] <teward> getting no output
[20:14] <tumbleweed> if you're in a source package, it should have output
[20:14] <teward> I.E. in makefile: export PACKAGE_VER_STRING=$(dpkg-parsechangelog --show-field Version)
[20:15] <teward> that to then later be referred to in arguments when the actual building of the binaries happens in sbuild
[20:15] <tumbleweed> --show-field is fairly recent. Is it available in the relase that you're building on?
[20:15] <tumbleweed> we used to have to pipe dpkg-parsechangelog to sed
[20:15] <teward> tumbleweed: building in both Debian stable (jessie) and Wily, both in sbuild schroots
[20:15] <teward> so it *should* be available in there?
[20:16] <tumbleweed> anything since dpkg 1.17.0
[20:16] <tumbleweed> according to the manpage
[20:17] <teward> yeah that's what I read too, for some reason it just does *not* want to do what i want it to :/
[20:18]  * teward tests something
[20:23] <teward> tumbleweed: only thing I can think of is that when we get to the dh_auto_install step which is overridden in the rules, it's no longer able to use dpkg-parsechangelog
[20:23] <teward> but I can't for the love of me figure out why
[20:27] <teward> going into the schroot, it *LOOKS* like it would work, but it's just not getting output how it should and providing it later on (i.e. empty string)
[20:27] <teward> which breaks things :/
[20:29] <tumbleweed> teward: show me your rules file
[20:34] <teward> tumbleweed: http://paste.ubuntu.com/14340616/
[20:34] <teward> oops
[20:34] <teward> wait
[20:34] <teward> that's the older one with git lol
[20:34] <tumbleweed> I can tell you what your problem there is :P
[20:34] <tumbleweed> each line of a rule gets executed in a seprate subshell
[20:35] <tumbleweed> if you want to export a variable for every subshell, you mustn't do it from a rule
[20:35] <teward> tumbleweed: so it should go out where GOPATH is defined, then?
[20:35] <teward> (in your mind replace that `git describe` line with the dpkg-parsechangelog stuff, i'm too lazy to repaste xD)
[20:37] <tumbleweed> yep
[20:37] <tumbleweed> and you probably don't need to export it - you can use a make variable, rather than a shell variable, for this
[20:38] <teward> will that get picked up later with variable substitution when it passes it to go in the flags?
[20:38] <tumbleweed> if you use the make syntax $(VARIABLE_NAME)
[20:44] <teward> tumbleweed: no dice :/
[20:44] <teward> no idea why it's still failing :?
[20:44] <teward> and I have an Echo line to echo what's there too, which is how I know it's failing
[20:45] <teward> about fed up with it right now and am just gonna hardcode the damn thing for now into place >.<
[20:45] <teward> THEN tackle variable sub
[20:48] <cjwatson> if you're setting it as a make variable, remember to use $(shell ...) not $(...)
[21:00] <teward> tumbleweed: cjwatson: I owe you both a beer/drink!
[21:00] <teward> tumbleweed: thank you for the guidance on where to get the string set
[21:00] <teward> cjwatson: thanks for reminding me about needing 'shell' there
[21:00] <teward> it's now behaving as it needs to :)
[21:00] <tumbleweed> excellent :)