[00:03] <gelph> In launchpad, is the blueprints feature the fullness of where you do software designs?  Or do people usually use UML modeling tools or just plain wikis or something instead for designs, outside of launchpad space?
[00:12] <gelph> I ask because I'm interested in about 4 people collaborating on a design and hoping to use launchpad
[00:13] <gelph> At work, we use whatever tool and upload finished UML class diagrams as PNG files to our wiki, and write text around it to defend the design
[01:25] <facundobatista> Hello!
[01:25] <facundobatista> lp-project-upload is uploading my tarball incorrectly
[01:25] <facundobatista> I mean, the uploaded file has other md5sum
[01:26] <facundobatista> I detected it because when tried to download and open it, gunzip complains it's not a valid format
[01:26] <facundobatista> it's this one: https://launchpad.net/launcherposta/trunk/0.9/+download/launcherposta-0.9.tar.gz
[01:26] <facundobatista> should I debug something or just open a bug? thanks!
[01:34] <fully_human> Hello.  I'd like to get involved with bug tacking.  I'm to the point of running through this tutorial (https://developer.ubuntu.com/packaging/html/fixing-a-bug-example.html) but I'm a bit confused when I try to find a bug in launchpad to tackle.  I see the bug sometimes assigned to a user even though the bug is labeled "NEW" and they date back to 2010.
[01:37] <TheLordOfTime> fully_human:  you mean bug tracking/fixing in Ubuntu, correct?
[01:37] <fully_human> Yes.
[01:37] <TheLordOfTime> not for some other project that runs on Launchpad?
[01:37] <TheLordOfTime> fully_human:  you may want to ask your questions in #ubuntu-bugs
[01:38] <fully_human> Ah, thanks.
[01:38] <TheLordOfTime> since that's where most ubuntu bugs questions regarding triaging/etc end up
[01:47] <wgrant> facundobatista: I've reported that as bug #1113932. It's a regression from a code change we pushed out on Friday, and appears to only affect files uploaded using the API.
[01:47] <wgrant> I'm reverting the problematic change.
[01:48] <wgrant> Should be fixed on production on Monday. Thanks for letting us know.
[02:00] <facundobatista> wgrant, thank you!!!
[04:20] <nesthib> Hi everyone!
[04:20] <nesthib> I'd like to report spam on launchpad → https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/602071/comments/52
[04:21] <nesthib> looks like this user also spammed other threads
[04:36] <facundobatista> wgrant, confirmed, upload through normal POST is ok
[04:37] <facundobatista> wgrant, thanks for working on this!
[04:52] <Logan_> Spam here as well: https://bugs.launchpad.net/ubuntu/+bug/153328
[04:52] <Logan_> (From the same guy).
[05:59] <StevenK> nesthib, Logan_: Those two spam comments have been hidden, thanks for reporting.
[06:01] <nesthib> no problem
[13:59] <xkernel> is it possible to associate or merge Launchpad accounts created by 2 openIDs?
[20:40] <george_e> I need GCC 4.7 in a daily build recipe for Precise - the package is in the precise-updates archive if that helps.
[20:40] <george_e> Is there any way of making that available to the recipe?
[20:47] <lifeless> george_e: the recipe needs an upstream source to pull from
[20:48] <lifeless> george_e: you can enable precise-updates (I think its on by default) for the PPA
[20:48] <george_e> It is?
[20:48] <george_e> This build here seems to have failed: https://launchpadlibrarian.net/130257909/buildlog_ubuntu-precise-i386.nitroshare_0.3-0~201302030357~precise1_FAILEDTOBUILD.txt.gz
[20:48] <george_e> It seems to have pulled in GCC 4.6.
[20:54] <tsimpson> george_e: I don't see gcc-4.7 in precise
[20:54] <george_e> tsimpson: http://packages.ubuntu.com/search?suite=precise-updates&searchon=names&keywords=gcc
[20:54] <george_e> It's in precise-updates.
[20:55] <tsimpson> george_e: that's just gcc-4.7-base, not gcc-4.7
[20:56] <george_e> tsimpson: Ooooooooh. Okay. Sorry for the mixup then.
[20:56] <tsimpson> note sure why it would be in precise-updates, seems pretty useless
[20:57] <george_e> So then obviously what I need to do is backport GCC 4.7 and add it to the PPA.
[20:57] <george_e> I already did that with CMake since I needed the latest version in the PPA.
[23:21] <george_e> Great. I can't seem to sign anything with my GPG key.
[23:21] <george_e> I just get: "gpg: skipped "... <...@...>": secret key not available"
[23:22] <george_e> But the key shows up in gpg --list-secret-keys
[23:22] <wgrant> george_e: The name+email line in debian/changelog needs to exactly match an identity on your OpenPGP key, including any comment on the identity, or you need to use the -kKEYID option
[23:23] <george_e> wgrant: I haven't touched debian/changelog - if it helps, I'm running 'backportpackage'.
[23:24] <wgrant> george_e: Do you have DEBEMAIL set correctly? backportpackage probably uses that to construct the changelog entry
[23:24] <wgrant> But backportpackage is an Ubuntu thing
[23:25] <george_e> AHA!
[23:25] <george_e> wgrant: You were right.
[23:25] <george_e> DEBEMAIL (for some reason) was not set correctly.
[23:25] <george_e> Now it's signing the package. Thank you for your help!
[23:25] <wgrant> Great :)