[00:12] <rowinggolfer> I've just done my first dput.
[00:12] <rowinggolfer> how long before I see the good stuff in my ppa?
[00:13] <wgrant> rowinggolfer: You'll receive a message within 5 minutes if you signed it properly.
[00:14] <wgrant> If it's accepted, it'll appear on your PPA page and start building within five seconds.
[00:14] <wgrant> And be visible to apt within five minutes of the build completing successfully.
[00:15] <rowinggolfer> ah... I got a rejection.
[00:15] <wgrant> Of what variety?
[00:16] <rowinggolfer> I got the path wrong :(
[00:16] <wgrant> rowinggolfer: Ubuntu Jaunty and above don't need manual configuration.
[00:16] <wgrant> Just 'dput ppa:username/ppa blah_source.changes'
[00:17] <rowinggolfer> I did this
[00:17] <rowinggolfer> dput ppa:rowinggolfer/ppa openmolar_0.1.2-0ubuntu1_source.changes
[00:18] <wgrant> What was the error?
[00:19] <rowinggolfer> ould not find a PPA named 'openmolar' for 'rowinggolfer'.
[00:20] <rowinggolfer> I think my .dput.cf was incorrect
[00:20] <wgrant> You don't need anything in your .dput.cf.
[00:21] <rowinggolfer> ah.
[00:26] <rowinggolfer> wgrant - I think this needs updating then ??
[00:26] <rowinggolfer> https://help.launchpad.net/Packaging/PPA/Uploading
[00:27] <wgrant> rowinggolfer: Indeed, although there are now instructions directly on the PPA page.
[00:27] <rowinggolfer> true that.
[00:28] <wgrant> Jaunty is only a few months old, so it's not terribly surprising that the page hasn't been updated.
[00:30] <rowinggolfer> ok, so i _think_ I've uploaded it correctly
[00:30] <rowinggolfer> but nothing back yet.
[00:30] <rowinggolfer> no news is good news?
[00:31] <wgrant> Wait another few minutes.
[00:31] <wgrant> You probably just missed the last upload processor.
[00:32] <rowinggolfer> ok.
[00:32] <rowinggolfer> I wondered if I'd stuffed up because this is a new package?
[00:33] <rowinggolfer> missed some random "initial upload" variable off somewhere
[00:33] <wgrant> If you got a rejection message the first time, you should get something this time.
[00:33] <wgrant> THere's nothing like that.
[00:33] <rowinggolfer> ok. I'll go put the kettle on.
[00:33] <rowinggolfer> thanks wgrant
[00:36] <wgrant> rowinggolfer: Still nothing :(
[00:43] <rowinggolfer> wgrant: nope :(
[00:44] <wgrant> rowinggolfer: No email?
[00:44] <rowinggolfer> no.
[00:44] <rowinggolfer> and if I try uploading again, I get this
[00:44] <rowinggolfer> neil@neil-12inch:~/openmolar$ dput ppa:rowinggolfer/ppa openmolar_0.1.2-0ubuntu1_source.changes
[00:44] <rowinggolfer> Already uploaded to ppa on ppa.launchpad.net
[00:44] <rowinggolfer> Doing nothing for openmolar_0.1.2-0ubuntu1_source.changes
[00:45] <wgrant> rowinggolfer: That's just a local check; give dput '-f' to override.
[00:45] <rowinggolfer> ok
[00:54] <rowinggolfer> wgrant: getting there
[00:54] <rowinggolfer> different rejection message :(
[00:55] <wgrant> Section this time?
[00:57] <rowinggolfer> no, my changelog was duff
[00:57] <wgrant> Ah.
[00:57] <rowinggolfer> openmolar (0.1.2-0ubuntu1) unstable; urgency=low
[00:58] <wgrant> Are you using 'dch' to edit the changelog?
[00:58] <rowinggolfer> a little bit of debian in there ;)
[00:58] <rowinggolfer> my app is pretty agnostic
[00:58] <rowinggolfer> works on hardy and jaunty
[00:58] <rowinggolfer> do I have to be specific though?
[01:02] <wgrant> rowinggolfer: You do. But you would normally give the lowest series -- in this case 'hardy'
[01:02] <rowinggolfer> thanks.
[01:03] <wgrant> It gets a bit more complicated than that, but we'll get to that later.
[01:05] <rowinggolfer> ok, uploading again.
[01:13] <wgrant> rowinggolfer: What went wrong this time?
[01:14] <rowinggolfer> openmolar_0.1.2-0ubuntu1.dsc: Unknown section 'office'
[01:14] <rowinggolfer> grr
[01:14] <wgrant> Do you know where to find the list of valid sections?
[01:15] <rowinggolfer> nope
[01:16] <wgrant> rowinggolfer: Bottom of section 2.4 at http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections
[01:17] <rowinggolfer> just found that
[01:17] <rowinggolfer> gonna plump for "misc"
[01:18] <wgrant> Hard to say :(
[01:20] <rowinggolfer> I should be sectioned.
[01:20] <rowinggolfer> this is a chore.
[01:26] <rowinggolfer> accepted :)
[01:27] <wgrant> But will it build?
[01:28] <rowinggolfer> good question indeed.
[01:28] <rowinggolfer> wee clocky icon is spinning
[01:32] <wgrant> rowinggolfer: Did you try building the package locally?
[01:35] <rowinggolfer> yes
[01:36] <rowinggolfer> but success or fail, I need to get to bed.
[01:36] <rowinggolfer> thanks for your help again wgrant
[01:37] <rowinggolfer> (bum - it failed)
[01:37] <rowinggolfer> goodnight
[06:32] <poolie> is staging meant to be down?
[06:37] <wgrant> It has been down quite a bit lately :(
[06:38] <wgrant> Updates were off for three days, and it just updated for the first time a couple of hours ago, so something was up.
[06:54] <poolie> i guess it's no emergency
[07:55] <gour> recently i read  http://changelog.complete.org/archives/1123-free-software-project-hosting review which is git-oriented, i.e. looking for a hosting with good git support. i was playing a lot with bzr wanting to migrate (from darcs) but returned back and, considering there are no real hosting solutions with darcs-supported, wonder if LP could be a good one by using darcs-fast-export(import) which is recently merged into bzr-fastimport
[07:55] <gour> plugin?
[08:04] <gour> any chance of darcs-support be added to LP's import considering that darcs-fast-export(import) is now bundled?
[08:33] <gour> i.e. any chance that https://bugs.launchpad.net/launchpad-code/+bug/44455 gets higher priority?
[08:34] <spiv> gour: my guess is, simply because there isn't much demand for it.  You could do the conversion yourself and push the result to Launchpad, of course.
[08:35] <spiv> "my guess is no", I meant :)
[08:35] <spiv> (Clearly I should be avoiding my laptop on weekends!)
[08:35] <gour> spiv: yeah, i'm aware of it...still having automatic import would be nice, especially considering that darcs support is now bundled in bzr-fastimprt plugin
[08:36] <gour> it's kind of catch-22...there is no demand 'cause the feature isn't there...
[08:37] <gour> similar to support for other DVCS & other project hostings...e.g. SF got some support to late :-)
[08:37] <spiv> Well, there's also far fewer projects using darcs than cvs, svn and probably git.
[08:37] <gour> s/to late/too late
[08:38] <spiv> Also, it sounds like you want two-way conversions, not just one-way?
[08:38] <gour> that's right, but doesn't having fast-import support greatly simplifies the task
[08:39] <gour> well, darcs-fast-export(import) give opportunity for 2-way, but just having ability to push from darcs repo and provide public bzr branches on LP would be nice as well
[08:39] <spiv> It might, but I'd have to check with the guys that actually implement the vcs imports in Launchpad before assuming that the existence of the fastimport plugin is the bulk of the work.
[08:40] <spiv> I think 2-way would be a bit problematic unless roundtripping is 100% accurate.
[08:40] <gour> thank you for considering it. :-)
[08:40] <spiv> Well, it's not up to me :)
[08:42] <gour> vmiklos did a great work with his darcs-fast-export and ian bundled it - https://bugs.launchpad.net/bzr-fastimport/+bug/232177
[12:03] <rowinggolfer> I'm struggling to get a working deb of my project following the instructions https://wiki.ubuntu.com/PackagingGuide/Python
[12:03] <rowinggolfer> not sure where to look for help.
[12:04] <rowinggolfer> it seems to me that there are so many ways to bake a *.deb
[12:04] <rowinggolfer> that a lot of the information around online is contradictory.
[12:04] <rowinggolfer> that howto suggests python-central scripts in the debian/rules
[12:04] <ripps> Is the launchpad buildfarm frozen? I've had a package that takes about 5 minutes to build in there for almost 30 minutes
[12:05] <rowinggolfer> ripps: the launchpad guys are quite good at putting a warning in the room topic if that happens.
[12:05] <rowinggolfer> I don't see one there at the moment
[12:05] <rowinggolfer> although perhaps I broke the farm with my attempts??
[12:07] <micahg> I noticed the Add Comment button missing on edge
[12:07] <ripps> rowinggolfer: I doubt it, I've sent over 80 packages there in a matter of minutes it handle it without a problem
[12:18] <happyaron> PPA building machines seems not working properly
[12:41] <micahg> is an update happening on edge
[12:42] <micahg> I can no longer see subscribers or the Add Comment button
[12:44] <wgrant> cprov: Can you kick buildd-manager?
[12:45] <wgrant> It seems to have been dead for an hour, right after ripps' builds were dispatched.
[12:46] <wgrant> micahg: edge hasn't updated for many days, and is working fine for me.
[12:47] <micahg> ugh, so maybe my session is messed up?
[12:49] <happyaron> my small package is building for over an hour, it usually takes no more than 15 minutes
[12:51] <wgrant> happyaron: Right, things are broken.
[12:51] <wgrant> micahg: More likely your browser.
[12:52] <happyaron> wgrant: what we can do is just wait and wait, :)
[12:53] <wgrant> happyaron: I'm afraid so.
[13:01] <micahg> wgrant: restarted my browser and all is well
[13:08] <lfaraone> Would LP's distro functionality work for a mini-distro that used RPMs?
[13:11] <micahg> are the tags for bugs supposed to show all tags in other tags or just certain ones?
[13:16] <wgrant> lfaraone: No. LP both doesn't really support other distros at the moment, and certainly not RPM-based ones.
[13:16] <wgrant> micahg: In the tags list on the right of the bug listing?
[13:16] <micahg> yep
[13:16] <micahg> there are official tags
[13:16] <micahg> and other tags
[13:16] <micahg> I would expect other tags to show all other tags
[13:17] <wgrant> micahg: It only shows the most popular i-forget-how-many.
[13:17] <wgrant> micahg: It used to show all of them, but Ubuntu has many many thousands of tags.
[13:17] <micahg> 10
[13:17] <wgrant> So it was very, very unwieldy and long.
[13:18] <micahg> wasn't one of the new features of 2.2.7 to be able to search for tags with +tag in the search boxz?
[13:18] <wgrant> micahg: No. But 2.2.5 or 2.2.6 brought advanced tag searches. Let me find the blog post..
[13:19] <wgrant> http://blog.launchpad.net/bug-tracking/searching-bugs-with-tags-now-with-wings
[13:21] <micahg> ugh
[13:21] <micahg> I can't do *tag
[13:22] <micahg> I still have to use advanced search to search for a specific tag
[13:22] <wgrant> Or click on the link down the side.
[13:22] <micahg> yes, but they're not all down the side
[13:22] <micahg> is it possible to make tag* an official tag
[13:22] <wgrant> tag*?
[13:22] <micahg> like if I wanted fixed-*, is that possible?
[13:23] <wgrant> No. * is not a partial wildcard. *blah isn't possible.
[13:23] <micahg> how about at the end
[13:23] <micahg> fixed-*
[13:25] <wgrant> I don't think so.
[13:29] <micahg> is it possible to custommize how many tags I see on the side?
[13:29] <wgrant> No, but it will show you as many official tags as exist.
[13:34] <micahg> should I mark a bug confirmed if I have the same problem in malone?
[13:34] <wgrant> micahg: You should mark the bug as affecting you.
[13:34] <micahg> ok
[13:35] <micahg> did that already
[13:35] <micahg> that reminds me of another bug :)
[13:35] <lfaraone> Does apport require users to create a launchpad account?
[13:36] <lfaraone> I'm thinking of deploying it in an enviornment when it wouldn't be realistic for each user to have their own LP account. (collecting information on a product used in primary schools)
[13:37] <wgrant> lfaraone: apport's Launchpad backend does, but its backends are pluggable.
[13:48] <lfaraone> wgrant: Well, I'd want to use launchpad with apport.
[13:49] <wgrant> lfaraone: Then yes, each user needs a Launchpad account.
[13:49] <wgrant> So it is not well-suited to your situation.
[13:57] <cprov> wgrant: uhm, is buildd-manager still broken ? I've just seen a bunch of job dispatched.
[14:01]  * cprov brb
[14:01] <wgrant> cprov: A whole lot of buildds just reappeared, and things seem to be moving again.
[14:01] <wgrant> So somebody is poking around.
[14:01] <happyaron> wgrant: yes, I get three build failed mail, :(
[14:02] <cprov> wgrant: they is always someone using the builders shared with 'enablement' services.
[14:02] <cprov> anyway, I will be online again in 10.
[14:03] <wgrant> cprov: So, it all seems resolved, but it might be nice to look at why it was hung for a couple of hours.
[14:03] <happyaron> cprov: there will be chromium daily build, and it use up almost all resource in a time
[16:51] <rowinggolfer> wgrant: I am "dput-ing" again, and confident the thing will build this time.
[16:51] <rowinggolfer> but we all know that confidence comes before a fall :(
[18:34] <intellectronica> hi micahg
[18:35] <micahg> hi intellectronica
[18:35] <intellectronica> micahg: so, why do you think subscribing people automatically can be a problem? I think that it's quite rare for someone to comment on a bug and not want (or need) to stay in the discussion
[18:35] <micahg> well, because the person might already be subscribed to bug mail for that project/package
[18:36] <intellectronica> micahg: so? in that case nothing special will happen. they will still receive mail
[18:36] <micahg> yes, but the headers and reasons why they are subscribed will change
[18:36] <intellectronica> we just have to make sure that the headers reflect that. i'm pretty sure they already do
[18:37] <micahg> yes, but the user might not want that
[18:37] <micahg> user might already have filters set up
[18:37] <intellectronica> micahg: if they do change, then i think it's something we should fix. if you're subscribed to bug mail for a project, that should take precedence over a header for subscribing to an individual bug
[18:38] <micahg> no
[18:38] <intellectronica> ?
[18:38] <micahg> I think the current behavior is fine
[18:38] <micahg> and proper
[18:38] <micahg> I use individual bug subscription to show that I'm active in the bug
[18:39] <micahg> but my comment might not mean I'm active necessarily
[18:39] <micahg> what's wrong with 2 buttons?
[18:39] <intellectronica> micahg: too complicated. not very user friendly
[18:39]  * micahg liked the checkbox with submit
[18:40] <intellectronica> also, i have a bit of a problem with people commenting without subscribing. i think that it's extremely rare for someone to want to comment but not be aware of future discussion
[18:41] <micahg> yes, but if a person is getting thousands of e-mails a day and only NEEDS to see comments on a few, and the filters are set up to do that, this would trash their system
[18:41] <intellectronica> micahg: well, what i'm suggesting is quite similar, behaviour-wise, to what we had before. by default you subscribe to the bug, but if you don't want that, unsubscribing is one additional click
[18:41] <micahg> i.e. team leads in Ubuntu
[18:42] <micahg> intellectronica: you'd be adversely affect people that already don't have time for the extra click
[18:42] <intellectronica> micahg: but that's just like it used to be. people who wouldn't have time for an extra click wouldn't have had time for an extra click when it was a checkbox
[18:43] <micahg> exactly
[18:43] <micahg> and they didn't want it checked
[18:43] <intellectronica> also, it's better to incovenience a few users than to inconvenience most users
[18:43] <micahg> it's not the same to click while on the way down to submit, then to wait for the postback and click
[18:43] <micahg> intellectronica: you're talking about inconveniencing the heaviest users of LP
[18:43] <intellectronica> micahg: but it was checked by default. they would have had to make an extra click to not get subscribed
[18:44] <intellectronica> micahg: yes, that's definitely something to take into consideration. also, because i don't use filtering by headers (i use gmail) it's sometimes hard for me to get a feel for how people use them
[18:45]  * micahg uses it to separate passive and active bugs
[18:45] <intellectronica> micahg: still, i don't see how that in any way would be worse than what we used to have, which seems to have been working quite well
[18:45]  * micahg subscribes to bugmail for 4 or so packages in ubuntu
[18:46] <intellectronica> a refinement of that idea would be to provide a global, per-user, option. "[x] Automatically subscribe me to bugs I comment on"
[18:47] <micahg> intellectronica: much better
[18:47] <micahg> and you can enable that by default
[18:47] <intellectronica> i hate doing that, though. i think that ideally we should have one behaviour that works as best as possible for everyone
[18:47] <micahg> then it's one click for the maintainers
[18:47] <micahg> intellectronica: people use the system differently
[18:47]  * micahg used to have 1 bug folder
[18:47]  * micahg now has 2 bug folders
[18:48] <micahg> heavier users needs to filter whereas normal users do not
[18:49] <intellectronica> another thing we could do is provide the header twice. once for your structural subscription and once for the direct subscription. then it's up to you to set up the filters that work best for you
[18:50] <micahg> well, that would confuse current filters and make filtering more complicated
[18:50] <intellectronica> micahg: but still, what i don't manage to understand is how what i'm suggesting would be any worse than what we already have. in both cases you get subscribed by default and need one single additional click if you rather not subscribe
[18:51] <micahg> it's where the click is
[18:51] <micahg> one is before the postback and in the flow
[18:51] <micahg> one is after the postback and requires scrolling back up
[18:52] <intellectronica> ah no, i'm not suggesting you have to scroll back. i'm suggesting something like "Thank you for your comment. You have been subscribed to mail notifications for future comments on the bug. Click <a href='unsubscribe'>here</a> to unsubscribe."
[18:53] <hggdh> that might work as well, micahg
[18:53] <micahg> again, you have to wait for another postback
[18:54] <intellectronica> micahg: not really, since it can use XHR the interaction will be very fast
[18:55] <hggdh> and, in fact, although Status and Importance are now ajaxable, Assigned is not, and the option to add a comment and subscribe is there
[18:55] <micahg> post a comment now takes a few seconds to show up
[18:55] <intellectronica> hggdh: setting assignee (and changing bug target) will be ajaxified very shortly (as in, sometime early next week)
[18:56] <intellectronica> micahg: i know. there's a bug for that. it will most definitely be improved
[18:57] <intellectronica> it's because of a limitation of how we do rendering on the server and getting it using the webservice api. we know how to solve that but haven't gotten to it yet
[18:57] <intellectronica> anyway, gotta go
[18:58] <micahg> intellectronica: I suggest you talk to some of the package managers in ubuntu
[18:58] <micahg> they'll know best how they use it
[18:58] <intellectronica> micahg: if it's ok with you, i'd like to paste the above into the bug. i don't have time to summerisze right now and i think it was a very useful discussion
[18:58] <intellectronica> micahg: indeed, that's a good idea
[18:58]  * micahg doesn't need to speak for people that have no problem stating their own opinions :)
[23:11] <dsprenkels> Hello?
[23:23] <thumper> Hello
 there was a bug in reporting the bug
 so there was a timeout error
 forget it
[23:35] <exarkun> * jericho has quit (giving up on an attempt to help improve free software)
[23:36] <exarkun> hth, hand
[23:40] <wgrant> Probably the dupefinder, as usual...