[08:08] <dholbach> good morning
[08:08] <vibhav> hi dholbach
[08:08] <dholbach> hi vibhav
[08:18] <ajmitch> hi
[08:40] <tumbleweed> blueyed: the tests are mocking out urllib calls. They'll need to be extended to mock the stuff you added
[08:44] <tumbleweed> blueyed: although, arguably, if we now have proxy support, we can avoid a lot of mocking and provide an HTTP proxy instead
[09:07] <vibhav> Is the pad down?
[09:09] <vibhav> (Ubuntu Uk Etherpad)
[09:21] <sladen> vibhav: it's not responding for me either ( http://pad.ubuntu-uk.org/ )
[09:21] <sladen> vibhav: however, the good question is how would be able to fix that, and unfortunately I'm not sure
[09:22] <vibhav> sladen: Isnt there any backup for it
[09:22] <vibhav> (pad.ubuntu.com)
[09:22] <micahg> Daviey: ^^
[09:22] <vibhav> I forgot the link
[09:23] <sladen> vibhav: I'm inquiring to see who the contact person is for Ubuntu-UK but perhaps you might be quicker
[09:24] <vibhav> सु
[09:24] <vibhav> sure
[09:24] <Daviey> sladen / vibhav: give me 10 mins
[09:24] <vibhav> okay
[09:24] <sladen> Daviey: is it you?
[09:25] <Daviey> sladen: yes
[09:28] <Daviey> vibhav / sladen: should be back alive.
[09:28] <vibhav> Daviey: Thanks!
[09:32] <sladen> groovy
[09:32]  * sladen will remember who to pester next time
[13:55] <Pikkachu> why wouldn't ./configure && make work for a package fetched through apt-get source?
[13:56] <Zhenech> it would, most of the time, what's the real question? :)
[13:57] <Laney> you don't have the build deps installed / not all packages are built like that / some patches need to be applied / some options need to be passed to the build system
[13:57] <Pikkachu> also, iirc upstream docs say to use apt-get build-dep for getting build dependencies, but the most up-to-date upstream version is not available and I have no idea where to start for having the correct build dep, because the local one does not work
[13:58] <Pikkachu> Zhenech: the question is real, the error was iirc something like missing .Tpo files. I think I'm asking because I wasted many hours in poor docs
[13:59] <Pikkachu> Laney: first option, no
[13:59] <Pikkachu> Laney: second, how so?
[13:59] <Laney> basically I am saying that you should be more specific if you want any chance of getting reasonable help, the same as Zhenech did.
[13:59] <Pikkachu> Laney: third, how so?
[14:00] <Pikkachu> I am fine
[14:00] <Pikkachu> I was just curious, because docs are poor the reason why I wasted so many hours with no one knowing what to do except trying to look cool
[14:01] <Zhenech> Pikkachu, as upstream packages *usually* do not gain additional build-deps, it's usually safe to do a apt-get build-dep on the old package
[14:01] <Zhenech> and the use that as a "start"
[14:01] <Laney> attempting to insult the people who you're asking for help isn't going to get you very far
[14:01] <Pikkachu> Laney: it's you who's including yourself in the group
[14:02] <Pikkachu> I don't really remember talking with 'Laney' in that long hours of pain
[14:03] <Zhenech> Pikkachu, do you have a build log resulting in an error?
[14:05] <Pikkachu> Zhenech: I had while I was trying to fix the problem, but not anymore.
[14:06] <Pikkachu> Zhenech: let me be clear as this may get confusing, I was curious about two separate things...
[14:08] <Pikkachu> Zhenech: 1. how c&m would fail for an apt-get source pkg (ok it may fail and you should debuild or like, just curious because the error was crazy and far away from "you should debuild instead")
[14:09] <Zhenech> Pikkachu, if you c&m in the unpacked ubuntu source, it may have patches, that result in failing when not used with the rest of the build system
[14:09] <Zhenech> or you might miss patches (pre 3.0 packages) which are needed to build on recent ubuntu
[14:10] <Zhenech> or the default configure wants to do something that is not in the build-deps, because it's disabled in debian/rules
[14:10] <Zhenech> or …
[14:10] <Zhenech> plenty of possibilities
[14:10] <Zhenech> but I'd say it should work in most of the cases
[14:11] <Pikkachu> Zhenech: 2. how to figure out the right deps for c&m'ing a source upstream tarball for which there's no corresponding package (local one is outdated version). I think build-dep is a big start but the error message was not self-guiding to me (something crazy like letter P unknown or like...)
[14:12] <Pikkachu> Zhenech: thanks for clarification about (1)
[14:13] <Zhenech> Pikkachu, w/o the real error message, no idea
[14:13] <Zhenech> best poke upstream?
[14:15] <Pikkachu> Zhenech: ok...
[14:16] <tumbleweed> Pikkachu: please be more respectful towards people who are trying to help you.
[14:17] <Pikkachu> quote me where I disrespected
[14:17] <Pikkachu> please
[14:17] <tumbleweed> Pikkachu: I really don't want to have to
[14:18] <Pikkachu> and I really don't care, but operators always have the last word
[14:18] <Pikkachu> either way I already got actual practical good help
[14:18] <tumbleweed> yeah, and I'd rather not have to call on them. or discuss this any further
[14:19] <Pikkachu> ah this is so boring...  thanks Zhenech
[16:04] <brainstorm> hello, I have a problem with debian/watch:
[16:04] <brainstorm> # watch control file for uscan
[16:04] <brainstorm> version=3
[16:04] <brainstorm> ftp://ftp.broadinstitute.org/pub/gsa/GenomeAnalysisTK/GenomeAnalysisTK-(.+)\.tar\.bz2
[16:04] <brainstorm> uscan warning: In debian/watch no matching files for watch line
[16:04] <brainstorm>   ftp://ftp.broadinstitute.org/pub/gsa/GenomeAnalysisTK/GenomeAnalysisTK-(.+)\.tar\.bz2
[16:05] <brainstorm> lftp reads "GenomeAnalysisTK-1.4.tar.bz2", for example, so it should match, isn't it ?
[16:10] <brainstorm> tumbleweed: any ideas ? :)
[16:10] <tumbleweed> brainstorm: worksforme: Newest version on remote site is 1.0.3148:3150M,
[16:11] <tumbleweed> it also timed out the first time I tried
[16:11] <tumbleweed> yay ftp...
[16:11] <Zhenech> tumbleweed, didnt for me funnily
[16:12] <tumbleweed> --verbose --report is usually helpful in debugging
[16:14] <brainstorm> vagrant@vagrant-ubuntu-oneiric:~/gatk/gatk$ uscan --verbose --report
[16:14] <brainstorm> -- Scanning for watchfiles in .
[16:14] <brainstorm> -- Found watchfile in ./debian
[16:14] <brainstorm> -- In debian/watch, processing watchfile line:
[16:14] <brainstorm>    ftp://ftp.broadinstitute.org/pub/gsa/GenomeAnalysisTK/GenomeAnalysisTK-(.+)\.tar\.bz2
[16:14] <brainstorm> uscan warning: In debian/watch no matching files for watch line
[16:14] <brainstorm>   ftp://ftp.broadinstitute.org/pub/gsa/GenomeAnalysisTK/GenomeAnalysisTK-(.+)\.tar\.bz2
[16:14] <brainstorm> -- Scan finished
[16:15] <brainstorm> worked for you ?? how ?
[16:15] <brainstorm> vagrant@vagrant-ubuntu-oneiric:~/gatk/gatk$ uscan --version
[16:15] <brainstorm> This is uscan, from the Debian devscripts package, version 2.11.1ubuntu3.1
[16:16] <tumbleweed> brainstorm: plase use a pastebin rather than spamming the channel
[16:17] <tumbleweed> http://paste.debian.net/160528/ <- devscripts 2.11.4. Ignore the warnings about VERSION, I'd just done a dch --create.
[16:21] <brainstorm> :-!?
[16:21] <brainstorm> does your debian/watch file look like mine ?
[16:22] <tumbleweed> yes
[16:28] <brainstorm> tumbleweed: can you run —debug ? mine: http://paste.debian.net/160529/
[16:30] <tumbleweed> brainstorm: http://paste.debian.net/160530/
[16:30] <tumbleweed> you sure you don't have a crazy firewall in the way?
[16:34] <brainstorm> nope, I can login via lftp normally :_/
[16:35] <tumbleweed> don't forget that FTP has multiple modes (active and passive) lftp may not use the same default as uscan
[16:35]  * tumbleweed feels obliged to point at http://mywiki.wooledge.org/FtpMustDie
[16:35]  * tumbleweed now has to run off
[16:39] <brainstorm> tumbleweed: thanks !
[17:39] <PaoloRotolo> Hi all!
[17:59] <jtaylor> anyone know how to get libtool to link with mpicc and not gcc'?
[18:00] <jtaylor> ./libtool --tag=CC   --mode=link mpicc does not do it
[18:24] <astraljava> Hey gang, where is pbuilder supposed to write the logfile I specify with --logfile to? I'm not seeing it anywhere on my system.
[18:26] <jtaylor> the option takes a path
[18:26] <astraljava> jtaylor: Ahh... and if it isn't provided one, then it won't create the file at all?
[18:27] <jtaylor> don'T know
[18:28] <astraljava> jtaylor: Ok, thanks.
[18:34] <astraljava> Hmm... well, even with path, it won't get created.
[20:00] <astraljava> jtaylor: Right, it was just a case of confusing documentation. The --logfile <file> option needs to go in between --build option and the <filename.dsc> argument. :-/
[20:01] <jtaylor> weird, is not necessary for me
[20:01] <jtaylor> but I'm using cowbuilder
[20:02] <astraljava> Well yeah, the UI is slightly different for that.
[20:07] <jtaylor> pbuilder-dist will always create a logfile for you
[20:18] <adam_g> y/win 4
[21:33] <ajmitch> Laney: how late can I get a new upstream release of something in? :)
[21:33] <ajmitch> it's mostly bugfixes, but just filling in the info for bug 961662
[21:33] <ajmitch> haven't subscribed ubuntu-release just yet
[22:33] <ajmitch> ScottK: thanks for the quick approvals
[22:33] <ScottK> ajmitch: You're welcome.
[22:36] <ajmitch> & now synced, will close bugs after they're published
[22:37] <ScottK> You can close them using syncpackage.
[22:37] <ScottK> (FYI)
[22:38] <ScottK> Then you get debian/changelog from the sync shoved into the bug for reference.
[22:38] <ScottK> (as if it were closed in changelog)
[22:40] <ajmitch> right, will do that for next time, sorry :)