[12:53] <kiko> synic, the OSD is pretty neat.
[12:53] <kiko> moving it and remembering where it should stay
[12:53] <synic> kiko: it's even spiffier in bzr, it has the progress bar on it
[12:54] <kiko> what does that measure progress of?
[12:56] <synic> the position in the track.  It's only useful if it's brought up by hovering over the tray icon
[01:02] <kiko> ah
[01:40] <kiko> can anyone load this page? http://lyme.media.mit.edu/teleporter
[01:42] <synic> kiko: doing a whole lot of hanging.
[01:42] <kiko> same here
[01:42] <kiko> it's hanging the mirror prober.
[01:43] <Fujitsu> Hah.
[04:06] <nealmcb> Should I expect a build on my PPA package?  Background: I thought I'd take a stab at testing ppa, so I took an old bit of authtool source and banged away at following the instructions in https://help.launchpad.net/PPAQuickStart with it.  Being even less than a noob at packaging, I was surprised to relatively quickly succeed with "Successfully uploaded packages.  It also said "Not running dinstall" which I don't understand.  But after 6 hours I don't se
[04:35] <Fujitsu> nealmcb: You are nealmcb on LP/
[04:36] <Fujitsu> *?
[04:36] <Fujitsu> I can't see any uploads... are you sure you are signing them with the right key, and uploading them to the right place? The `Not running dinstall' is perfectly normal.
[04:40] <ubotu> New bug: #136510 in malone "hard to see that a bug page is of a duplicate bug" [Undecided,New]  https://launchpad.net/bugs/136510
[04:43] <nealmcb> Fujitsu: thanks.  I can check the key, but not sure how to check the "right place" offhand
[04:43] <nealmcb> but would I not expect some errors if one of those was wrong?
[04:44] <Fujitsu> If the key isn't known by Launchpad, the package will be dropped silently to avoid spamming people.
[04:44] <nealmcb> ahh
[04:45] <Fujitsu> Otherwise people could maliciously upload things and get LP to spam people, without any way of tracking it.
[04:45] <ubotu> New bug: #136511 in malone "Clicking on the background of a bug target row should open that row" [Undecided,New]  https://launchpad.net/bugs/136511
[04:49] <nealmcb> active keys: 1024D/2C9EBA60   gpg -v --verify *dsc == good signature; Signature made Fri 31 Aug 2007 02:22:13 PM MDT using DSA key ID 2C9EBA60
[04:51] <nealmcb> so the keys and sigs look fine to me.  and *upload says "Successfully uploaded ../authtool_0.2.2~ppa1.dsc to ppa.launchpad.net." and 2 other messages like that
[04:51] <nealmcb> Fujitsu: Is that what you mean by "right place"?
[04:52] <nealmcb> but my changelog lines don't match my pgp key - is that necessary?
[04:52] <nealmcb> I used a web url in the changlog signature
[04:52] <nealmcb> (avoiding spam)
[05:00] <mpt> Gooooooooooooooooood afternoon Launchpadders!
[05:04] <Fujitsu> nealmcb: Are you uploading to ~nealmcb/ubuntu/?
[05:05] <nealmcb> well, in .dput.cf I have   incoming = ~nealmcb/ubuntu/
[05:05] <nealmcb> I'm not sure what effect "Section: universe/devel" has
[05:05] <nealmcb> (in the control file)
[05:07] <nealmcb> Note that I don't want to waste your time teaching me the rudiments of packaging if you tire of this :-)  I'm just trying to report what I see when giving a shot at testing, and letting you know what I can figure out from the error messages or lack thereof.
[05:08] <nealmcb> e.g. I'd think that the dput should complain if the signature check fails - is that possible?
[05:10] <nealmcb> does it figure out what key to use based on the .dput.cf file (~nealmcb) or the changelog entries?
[05:10] <Fujitsu> dput doesn't have anything to do with the signing.
[05:11] <nealmcb> cause my changelog doesn't have an email in it, so I had to use the "-k" option to dput to specify the key   -- Neal McBurnett <http://mcburnett.org/neal/>  Fri, 27 Apr 2007 14:21:04 -0600  
[05:11] <Fujitsu> When you debuild/dpkg-buildpackage/debsign, it will sign with a key.
[05:11] <Fujitsu> Right, if you sign with the right key there, it should work...
[05:11] <nealmcb> I signed via dpkg-buildpackage 
[05:11] <nealmcb> ahh - right - not dput...
[05:12] <Fujitsu> dput will verify the signature matches, but can't tell if it's the right key or not.
[05:12] <nealmcb> and how does it define "right key"?
[05:12] <nealmcb> it == the system....
[05:12] <Fujitsu> The one assigned to your LP account.
[05:13] <nealmcb> which it looks up based on .dput.cf "incoming"?
[05:13] <Fujitsu> It looks at the directory you upload it so, so yes.
[05:14] <nealmcb> ok.  so the 2nd upload was 12 minutes ago, and I see nothing at https://launchpad.net/~nealmcb/+archive/+builds?build_state=all&build_text=
[05:15] <Fujitsu> Builds won't appear for probably 30 or so minutes afterwards.
[05:15] <nealmcb> but I don't think I changed anything other than the control section - would that make a difference?
[05:16] <Fujitsu> The content of the package is irrelevant if you don't get an accepted/rejected message.
[05:18] <nealmcb> ok - now I do another dput, and it says Already uploaded to ppa.launchpad.net  Doing nothing for ../authtool_0.2.2~ppa1_source.changes
[05:18] <nealmcb> (I had done the build, but not the dput 12 minutes ago... so just did the dput...)
[05:21] <nealmcb> So is it still waiting for something to be done about the dput from 7 hours ago, which is still not showing up in the launchpad status
[05:29] <Fujitsu> Use dput -f to force it to reupload... the `Already uploaded' is only dput seeing the .upload file. (sorry, was at lunch)
[05:29] <Fujitsu> nealmcb: ^^
[05:34] <nealmcb> Fujitsu: cool  - so I once again get "Successfully uploaded packages." - should that start a build?
[05:36] <Fujitsu> nealmcb: No, that's just dput. You will get an email indicating whether it accepted or rejected it after the next */5, then builds will start soon after the next */20
[05:40] <nealmcb> Fujitsu: OK, I'll keep an eye out.  but I haven't gotten any email about the last upload.
[06:05] <nealmcb> Fujitsu: still nothing.   is there a way to track what happens between the dput and the emails?
[08:55] <Fujitsu> nealmcb: Sorry, had to go out for a couple of hours. You'll have to ask cprov or similar to track what has gone wrong.
[09:45] <ubotu> New bug: #136535 in malone "`Latest Bugs Reported' for Distro(Series) doesn't mention the source package, if any" [Undecided,New]  https://launchpad.net/bugs/136535
[10:00] <ubotu> New bug: #136536 in launchpad "Launchpad needs to read more fables, such as `The Launchpad who cried Click Here For Help'" [Undecided,New]  https://launchpad.net/bugs/136536
[10:56] <ubotu> New bug: #136542 in soyuz "Binary descriptions don't have any . stripped on display" [Undecided,New]  https://launchpad.net/bugs/136542
[11:47] <gouki> Isn't it possible to close a PPA?
[01:27] <_gpg_> I can see the message i sent in 1991 :)
[02:25] <ubotu> New bug: #136570 in malone "Can't unsubscribe 121439" [Undecided,New]  https://launchpad.net/bugs/136570
[02:37] <nealmcb> Fujitsu: thanks.
[03:59] <nealmcb> Fujitsu: I reported my ppa "lack of status" problem as bug 136593
[03:59] <ubotu> Launchpad bug 136593 in soyuz "no status update after dput for ppa package" [Undecided,New]  https://launchpad.net/bugs/136593
[04:05] <ubotu> New bug: #136593 in soyuz "no status update after dput for ppa package" [Undecided,New]  https://launchpad.net/bugs/136593
[07:20] <rafael> hi
[07:21] <rafael> i would like to see all changes from a branch to its original project, is it possible?
[07:21] <rafael> (not see them per revision)
[11:38] <keturn> how do I get an external bug tracker added to my launchpad project?