[05:14] <vadi2> How can I run the `source` command in a PPA? I'm trying to add Qt 5.6 via https://launchpad.net/~beineri/+archive/ubuntu/opt-qt562-trusty/+packages and that requires me to source a script to setup some environment variables before any of the Qt commands are found.
[05:15] <wgrant> vadi2: You'll need to adjust your debian/rules to set any required environment variables.
[05:16] <vadi2> oh, set them manually instead of using the script?
[05:17] <wgrant> vadi2: You can use any means to set them from within debian/rules, but it's not possible to run anything custom before debian/rules is invoked (eg. source in the containing shell).
[05:17] <caraka> When I use the beineri qt PPAs, I'm doing it inside a docker build container, so I can use a RUN command to source the script that sets the path correctly
[05:19] <vadi2> Yeah I'm doing it in a Launchpad build here and it just dies with "/bin/sh: 1: source: not found"
[05:19] <caraka> if you are doing it at launchpad, wgrant is your man
[05:19] <wgrant> vadi2: /bin/sh is dash, not bash, on Ubuntu.
[05:19] <vadi2> So I think I'll have to replicate what the script is doing instead of using source
[05:20] <wgrant> source is a bashism.
[05:20] <vadi2> All I know is that qmake is not found and running source on qt56-env.sh makes it work in Travis
[05:21] <wgrant> You also can't even use "." in a Makefile like you might in a shell script, because the naïve approach would just set the environment variables in the subshell for that one line.
[05:21] <wgrant> If there's a build command that needs the makefile set, prefixing that line with ". qt56-env.sh && " or whatever might work.
[05:21] <wgrant> You can experiment with this locally; Launchpad does nothing special here.
[05:22] <vadi2> okay! I'll try that
[05:37] <vadi2> Perhaps it would have worked but "/bin/sh: 7: /opt/qt56/bin/qt56-env.sh: [[: not found" suggests that script has the said "bashism" you speak of
[05:38] <vadi2> I have to wonder how do people get Qt 5.6 on Ubuntu 14.04 in a PPA build then
[05:47] <wgrant> vadi2: They could just set the environment variables manually in debian/rules, but you might have more like talking to KDE types.
[06:17] <vadi2> I'll look further. Appreciate your prompt help today!
[07:27] <cjwatson> ahoneybun: use git clone git+ssh://aaronhoneycutt@git.launchpad.net/... then, or https://help.launchpad.net/Code/Git#Configuring_Git to abbreviate that; you can also configure the default username for connections to git.launchpad.net in ~/.ssh/config
[15:18] <mapreri> Now, why did sinzui unassigned himself from so many "Fix released" bugs and caused such (imho inappropriate) mail flood?
[15:18] <mapreri> (and also if they are not "Fix released" they are all either "Invalid" or "Won't fix" so anyway "closed")
[19:12] <ahoneybun> cjwatson: I have nothing about config in ~/.ssh
[20:31] <cjwatson> ahoneybun: Sure, but you could if you wanted
[21:37] <ahoneybun> cjwatson: http://pastebin.ubuntu.com/24583149/
[21:37] <ahoneybun> http://pastebin.ubuntu.com/24583150/
[21:37] <ahoneybun> that one
[21:41] <nacc> ahoneybun: but you're not using the lp: insteadof
[21:41] <nacc> ahoneybun: so it's using (ssh is) your username (aaron)
[21:41] <ahoneybun> oh username on the machine
[21:41] <nacc> ahoneybun: i think it'd work if you did lp:~kubuntu-packagers/kubuntu-packaging/+git/kubuntu-settings
[21:42] <ahoneybun> \o/
[21:42] <ahoneybun> thanks nacc
[21:49] <nacc> ahoneybun: np
[22:07] <cjwatson> right, and you could also put this in ~/.ssh/config in order for plain git+ssh://git.launchpad.net/... to work:
[22:07] <cjwatson> Host git.launchpad.net
[22:07] <cjwatson>         User aaronhoneycutt
[22:07] <cjwatson> (creating that file if it doesn't already exist)
[22:08] <nacc> cjwatson: good point :)