[07:59] <gnomefreak> wgrant: thanks for the help last night, changing version worked. However i had to retry all of them a bunch of times due to build systems chroot failed a bunch of times on all packages. it was due to kernel version lower than the one needed.
[08:04] <wgrant> gnomefreak: Right, that's normal for Jaunty at this point.
[08:05] <wgrant> Things do break - that's why you're not meant to run it on your own machine just yet.
[08:05] <gnomefreak> ah ok
[08:06] <gnomefreak> it wasnt my fasult though it was the buildd on PPA that gave chroot errors jaunty here is running fine as main and chroot
[08:06] <wgrant> Chroot errors are never your fault.
[08:08] <gnomefreak> ah ok
[08:09] <wgrant> That could probably be described better.
[08:09] <wgrant> I wonder if there's documentation on all of those statuses.
[08:12] <Hobbsee> don't think so
[08:13] <Hobbsee> although I think there was talk about getting some documentation written.
[08:13] <Hobbsee> ages ago
[08:14] <wgrant> Maybe we can steal stuff from the dev wiki once more of it is public.
[08:17] <Hobbsee> that might be cool
[09:21] <wgrant> Is being a Chinese autoresponder that doesn't set a charset enough to get kicked off launchpad-users?
[09:23]  * mrevell looks
[09:23] <wgrant> They're not sent to the list itself.
[09:23] <wgrant> But you might have one from your email not too long ago.
[09:24] <mrevell> wgrant: Oh right. Wanna PM me the sender's email addr?
[09:24] <wgrant> In fact, it's a plaintext message followed by an HTML one, in the same part, without a charset, with content-type text/plain. Smart.
[09:24] <wgrant> Done.
[09:25] <mrevell> thanks
[12:07] <savvas> using launchpad's PPA, does anyone know if I copy the built binaries from intrepid to hardy, will they work properly?
[12:08] <geser> savvas: have you checked if the dependencies are available in hardy?
[12:08] <bigjools> savvas: depends on the binaries
[12:09] <geser> because even if it works you might not be able to install them
[12:09] <savvas> it's for secret maryo chronicles, 1.6 version: https://launchpad.net/~medigeek/+archive
[12:09] <savvas> I think they have the same package dependencies
[12:09] <savvas> let me check
[12:09] <savvas> thanks btw :)
[12:13] <savvas> well, it looks ok, I'll try it on a virtual machine later
[12:20] <savvas> geser, bigjools: in case it doesn't work, is there a way to use the already upload .orig.tar.gz, but make a build for hardy? (sorry for the highlight)
[12:20] <savvas> *uploaded
[12:24] <geser> savvas: I guess only uploading a new .diff.gz (with the matching .dsc) targeting hardy should work
[12:25] <savvas> ok, I'll give it a try afterwards, thanks!
[12:38]  * henninge -> lunch
[13:54] <mrevell> hey wgrant, still around?
[14:39] <kiko> mrevell, remind me who the user is that does the import of +text bug renderings periodically?
[14:40] <mrevell> kiko: Hmm, I don't know, I'm afraid.
[14:40] <awilkins> Are there any plans for wiki features in LP?
[14:41] <kiko> awilkins, plans but no dates :-/
[14:41] <awilkins> Does that include trac-style integration of the wiki processor into all the other modules like issue descriptions?
[14:42] <awilkins> Or is that something planned for a later date? ;-)
[14:43] <awilkins> kiko: I'm currently reviewing collaboration systems for my employer ; we've got at least three bespoke special-purpose issue trackers that I want to kill off and replace with a cusomization of something
[14:44] <kiko> awilkins, it would include trac-like intergration, yeah -- you'd be able to use a subset of wikitext more generically.
[14:44] <awilkins> kiko: Robert Collins may have sent you a mail about me ("The UK NHS wants us")
[14:44] <kiko> awilkins, I know, I am getting to your email in my inbox!
[14:44] <awilkins> kiko: Heh, backlog city
[14:44] <kiko> awilkins, 433 unread
[14:44] <kiko> travelling kills me
[14:45] <awilkins> kiko: I'm told that SFEE is one of the options on the table because a contracted project is using it... I've not so far been able to actually download it, our web proxies are being especially awful this week
[14:45] <awilkins> I have my doubts about being able to poke it's soft underbelly to see how it ticks though
[14:46] <kiko> awilkins, you'd really be crazy to use SFEE instead of Launchpad, though I guess it depends on whether you really need a self-hosted solution or not.
[14:46] <awilkins> I know it's PHP but the demo is a VM and I bet it's an encrypted FS or something
[14:46] <awilkins> kiko: I'm not sure we can justify not self-hosting
[14:47] <awilkins> kiko: I;m sure there would be a contingent that would find it politically unacceptable
[14:47] <kiko> awilkins, same contingent that uses salesforce for tracking contacts? :)
[14:48] <kiko> awilkins, or google for searching through enterprise content?
[14:48] <awilkins> I doubt it, this is a government agency ; I think salesforce would be a bit "advanced"
[14:48] <kiko> awilkins, or plaxo for managing business cards?
[14:48] <kiko> heh
[14:48] <kiko> maybe. I just used those examples to point out that people actually do use stuff that's "out there"..
[14:49] <kiko> it'll be hard to find a group producing a tool that is as eager to provide you with a good solution as launchpad, though.
[14:49] <awilkins> We do have atrociously bad internal solution
[14:50] <awilkins> kiko: I like LP, but I think it would need extending for our needs ; we'd probably need to put in some bridges to existing systems and support for different classes of issue with different workflows
[14:51] <awilkins> kiko: I think the same thing is probably true of anything we adopt
[14:51] <awilkins> When I get home I may actually be able to get a full download of this accursed SFEE VM.
[14:51] <awilkins> This allegedly has custom workflow
[14:52] <kiko> awilkins, it does depend on how custom you need to be, but launchpad does offer APIs and machine-readable exports to make integration easy
[14:54] <awilkins> kiko: I do like the fact that it's probably one of the few "forges" which started life in the web 2.0 era.
[14:54] <awilkins> kiko: This makes me more optimistic about the modularity of its internal design
[14:55] <awilkins> kiko: And using it has been a pleasant experience so far.
[14:55] <kiko> awilkins, that's cool to hear. if you want me to help you pitch it internally then we can try -- just keeping in mind that the non-self-hosted meme is a hard battle :)
[15:14] <Aron_> kiko: ping
[15:17] <savvas> for PPA, does the original .changes filename have to be used as 'smc_1.6-1.0_source.changes' or can I rename it to 'smc_1.6-1.0_hardy.changes' ?
[15:20] <cprov> savvas: they have to end up with '_source.changes'
[15:21] <cprov> savvas: why would you rename it, genchanges uses this convention.
[15:21] <thekorn> hi, is it possible to get a list of all bugs which have been converted into a question?
[15:22] <savvas> cprov: I've uploaded an intrepid build, and I want to rebuild it for hardy
[15:22] <savvas> cprov: so.. I just use dput -f to upload the source.changes again, but for hardy this time?
[15:23] <cprov> savvas: rebuilds require a new source version.
[15:23] <cprov> savvas: you will have to build a new source.
[15:24] <savvas> cprov: and re-upload smc_1.6_orig.tar.gz ?
[15:24] <savvas> * smc_1.6.orig.tar.gz
[15:46] <cprov> savvas: no, the orig.tar.gz is already there you don't need to upload it again
[15:46] <cprov> savvas: build the source with `debuild -S` only
[15:47] <savvas> ok I'll try
[15:52] <savvas> woohoo!
[15:52] <savvas> thanks cprov :)
[15:56] <cprov> savvas: you're welcome.
[16:13] <BjornT> thekorn: no, it's not easy to get a list of the converted questions. is this a one-time thing, or would you need this info regurarly?
[16:17] <simmerz> hi. i created a PPA before signing the code of conduct, but I now can't see where to activate it.
[16:21] <simmerz> anyone have any ideas?
[16:22] <persia> Whoever is responsible for debdiffs being two clicks away from the uploaded packages list: thank you very much.  I've a related feature request that closed bugs be clickable from the short-form publishing history.  Is that a bug against Malone?
[16:23] <persia> Or against Soyuz?
[16:23] <mrevell> simmerz: Have you tried https://launchpad.net/people/+me/+archive
[16:25] <savvas> handy shortcut
[16:25]  * savvas takes notes
[16:26] <simmerz> mrevell: yes. that page comes up. gives me deb and deb-src lines
[16:26] <simmerz> but I get a 404 clicking on the deb location
[16:27] <mrevell> simmerz: Have you uploaded anything yet?
[16:28] <bigjools> you need to upload something before the archive is created
[16:28] <simmerz> mrevell: just have about 5 mins ago. so hopefully that'll build and go in?
[16:29] <mrevell> simmerz: Should do. Give it a few minutes.
[16:29] <simmerz> ok
[16:29] <mrevell> simmerz: to an hour
[16:29] <simmerz> :) thanks.
[16:30] <simmerz> oh. rejected
[16:33] <simmerz> debuild -S -sa has apparently decided that the distribution is unstable and the error is that it couldn't find "unstable"
[16:41] <simmerz> https://launchpad.net/~tom+launchpad-initforthe/+archive :)
[16:46] <tgm4883_laptop> is there a way to clean out some cruft from a projects code section?  Seems we have some old cruft listed here that doesn't belong to us  https://code.edge.launchpad.net/mythbuntu
[16:53] <beuno> tgm4883_laptop, for the branches you own, you can go to the branch's page and click on the red icon next to the title to delete it
[16:54] <tgm4883_laptop> beuno, yea, but what about the branches that we dont'?
[16:54] <tgm4883_laptop> ie
[16:54] <tgm4883_laptop> https://code.edge.launchpad.net/~mrimbert/mythbuntu/documentation
[16:54] <tgm4883_laptop> we don't know this guy
[16:54] <beuno> tgm4883_laptop, those are owned by other people, so you can't delete them
[16:55] <tgm4883_laptop> ok, is there a reason for someone being able to do this then ^
[16:55] <beuno> tgm4883_laptop, actually, your comment makes me think we may want to distinguish "official" branhces from random branhces
[16:55] <beuno> tgm4883_laptop, yes, free software!
[16:55] <tgm4883_laptop> cause if there is a good reason for that i can get over it being there
[16:55] <beuno> anyone can push branches
[16:56] <tgm4883_laptop> I'm just a little OCD and like things clean
[16:56] <beuno> tgm4883_laptop, if the project's branches where highlighted, would that work for you?
[16:56] <tgm4883_laptop> yes
[16:57] <beuno> tgm4883_laptop, feel like filing a bug for it?   I think it's a good idea, and I'll talk to the right people to make it happen
[16:57] <tgm4883_laptop> yep, i'll file a bug about it
[16:57] <tgm4883_laptop> one question on bugs, then i'll leave
[16:57] <beuno> tgm4883_laptop, thanks. Point me to the bug # afterwards
[16:57] <beuno> sure, you can even stick around!
[16:57] <tgm4883_laptop> thanks ;)
[16:58] <tgm4883_laptop> bugs can be targeted to milestones, but as far as I can tell, once that milestone is reached you still have to manually change the bugs from "fix commited" to "fix released", is this the intent?
[16:59] <beuno> yes, although that is likely to change the in the future
[16:59] <beuno> when you can say "this milestone is released"
[17:00] <tgm4883_laptop> awesome
[17:00] <tgm4883_laptop> that will help a lot
[17:00] <tgm4883_laptop> ok, one more question
[17:00] <tgm4883_laptop> sorry I lied
[17:01] <tgm4883_laptop> Is there currently a way (or should I file a blueprint), that would make a release notes page that automatically grabs fixed bugs, blueprints, etc and puts them on a single page?
[17:02] <tgm4883_laptop> It would make release notes alot easier to make by auto grabbing everything that was targeted to a release.
[17:03] <beuno> tgm4883_laptop, there isn't anything like that
[17:03] <beuno> but, file a bug for it as well, it sounds like something we want to have
[17:03] <tgm4883_laptop> it's a blueprint then ;)
[17:03] <tgm4883_laptop> bug or blueprint?
[17:03] <kabotage> how come the bugs i filed got deleted? i filed two bugs and now its gone?
[17:04] <henninge> kabotage: do you have a project or even bug number?
[17:04] <beuno> tgm4883_laptop, bugs are better for us at the moment
[17:04] <henninge> kabotage: what is your lp  user name?
[17:05] <tgm4883_laptop> beuno, ok, will do
[17:05] <kabotage> i just reported a bug a couple of hours ago.
[17:05] <tgm4883_laptop> frick, one more thing
[17:05] <tgm4883_laptop> man, these just keep coming to me
[17:05] <beuno> tgm4883_laptop, keep them coming
[17:05] <kabotage> henninge: its kabotage
[17:06] <henninge> kabotage: and the project you filed the bug for?
[17:07] <kabotage> crashes on kmix and dolphin
[17:07] <tgm4883_laptop> is the launchpad janitor broken?  Our project has marked that we want bugs that autoexpire to actually expire, but they stay around and never expire.  We have 25 bugs that can autoexpire, but wont.  We have this that was set to autoexpire 125 days ago https://bugs.edge.launchpad.net/mythbuntu/+bug/151612
[17:08] <beuno> tgm4883_laptop, it's currently disabled
[17:08] <beuno> it will be fixed soon
[17:11] <tgm4883_laptop> beuno, ok, thanks
[17:11] <henninge> kabotage: hm, there must be some misunderstanding. There is no bug reported by you for dolphin.
[17:12] <tgm4883_laptop> dang it, one more
[17:12] <henninge> kabotage: and bugs are never deleted.
[17:12] <tgm4883_laptop> but this one isn't from me, but someone that hit our mailing list
[17:12] <henninge> kabotage: also there is no kmix project, only jackmix and jackmixer.
[17:13] <henninge> kabotage: Maybe you didn't complete the report?
[17:13] <tgm4883_laptop> Is it possible to have launchpad remind people (when reporting a bug) to include the version number that they are using?  It would be fine if it were a text field that could be left blank, or just a reminder that goes into the reporting text box which the user could erase or leave as is...
[17:14] <tgm4883_laptop> beuno, bug 297287
[17:14] <beuno> tgm4883_laptop, very much appreciate dfor the bug
[17:14] <beuno> tgm4883_laptop, there is something about that
[17:14] <beuno> allenap would know
[17:16] <kabotage> henninge: how come? i just filed two and i can still see the summary title that i put.
[17:16] <henninge> kabotage: what's the title?
[17:18] <allenap> tgm4883_laptop: For projects, project groups and distributions some bug reporting guidelines can be set.
[17:18] <allenap> tgm4883_laptop: These appear underneath the Further Information box when filing a bug.
[17:18] <kabotage> henninge: The application KMix (kmix) crashed and caused the signal 6 (SIGABRT) and Dolphin Crashed While transferring files to Flash drive
[17:18] <allenap> tgm4883_laptop: I'm currently working on making them appear for packages in distributions too.
[17:19] <tgm4883_laptop> ah I see now
[17:19] <tgm4883_laptop> question, would it be possible to have the bug report pre-filled with certain information?
[17:20] <tgm4883_laptop> It can be generic info such as {what happened} {what was expected} etc
[17:20] <tgm4883_laptop> I can see this being beneficial across all projects
[17:20] <allenap> tgm4883_laptop: Not right now afaik. Do you mean, like a template in the Further Information box?
[17:21] <henninge> kabotage: That is the bug title?
[17:22] <henninge> kabotage: if you still see it on your screen, you should also still see the URL in the browser. Can you please give me that?
[17:22] <tgm4883_laptop> no, more like when I file a bug I have the text area to say what happened.  This can be done two ways, either a) seperate text boxes for each part (what happened text box) (what was supposed to happen text box) or b)  Just have those words already in the single text box on seperate lines (what happened) (what was supposed to happen)
[17:22] <tgm4883_laptop> allenap, ^
[17:23] <allenap> tgm4883_laptop: Ah, okay, I think that's what I meant, I just didn't say it very well :)
[17:24] <tgm4883_laptop> ah ok, yes.  I see now.  I thought you were still talking about just the guidelines
[17:24] <tgm4883_laptop> so yes, a template would rock
[17:24] <allenap> tgm4883_laptop: Some bug trackers - the KDE one comes to mind - have wizard-like bug filing processes which take this a step further. That would be quite cool for Launchpad, but a *lot* of work too, and would confuse the user experience.
[17:24] <allenap> tgm4883_laptop: But I think that would be easy (or possible) for a committed project to add by hosting it themselves and hooking into the Launchpad API.
[17:27] <kabotage> henninge: its ok. i see that the bug has been marked as duplicate. thanks for replying though
[17:27] <allenap> tgm4883_laptop: Can you file a bug against malone for this? I can't promise we'll do it soon, but at least we won't forget about it :)
[17:27] <allenap> tgm4883_laptop: For the template idea I mean.
[17:27] <tgm4883_laptop> allenap, will do
[17:27] <allenap> tgm4883_laptop: Thanks!
[17:27] <tgm4883_laptop> beuno, heres that other bug we talked about bug 297291
[17:28] <henninge> kabotage: I am still wondering that you report bugs in two applications with one report.
[17:28] <tgm4883_laptop> allenap, am I filing the bug against the person malone?
[17:28] <tgm4883_laptop> or just subscribing him
[17:29] <allenap> tgm4883_laptop: No, the malone project, https://edge.launchpad.net/malone/+filebug
[17:29] <kabotage> henninge: sorry if i got you confused, but i filed it separately
[17:33] <henninge> kabotage: ok, I am glad we got that sorted out, then ;-)
[17:34] <tgm4883_laptop> allenap, bug 297294
[17:35] <kabotage> henninge: yea. thanks again.
[17:36] <allenap> tgm4883_laptop: Thanks, that's a good clear request.
[17:37] <tgm4883_laptop> I try to write good ones ;)
[17:50] <beuno> tgm4883_laptop, thanks
[18:07] <thekorn> BjornT: re list of converted questions: no, it's more a one time thing, today we found bug 297238 and I would like to know how many bugs/questions are affected
[18:31] <BjornT> thekorn: ok. according to my sql query, there are only two such bugs: bug 222569, bug 240637  (and bug 297006 on staging)
[18:32] <BjornT> thekorn: do you have any other example of such a bug?
[18:33] <thekorn> BjornT: ok, cool, I think we have no others so far, bug 222569 was the one where we found this issue
[18:34] <thekorn> bdmurray: ^^ this are converted questions where the status of the bug is other than invalid
[18:34] <thekorn> thanks BjornT !
[18:36] <bdmurray> BjornT: I reported bug 297238
[18:36] <bdmurray> BjornT: thanks for running query, could I see it for future use?
[18:39] <BjornT> bdmurray: https://pastebin.canonical.com/11096/
[18:46] <stgraber> who broke the lpia PPA builders ? :)
[18:50] <savvas> probably me
[18:51] <savvas> just kidding :p
[18:51] <savvas> what's an lpia architecture by the way?
[18:52] <savvas> hm.. ubuntu mobile arch?
[18:54] <bdmurray> BjornT: thanks
[19:05] <stgraber> savvas: yeah, Low Power on Intel Architecture
[19:06] <stgraber> it's one of the three archs the PPA build for
[19:07] <savvas> hm.. strange that there's no wikipedia article about it
[19:07] <savvas> (thanks btw :) )
[20:34] <PriceChild> Hey there. I'm thinking of changing a moderated team to a closed one. I'm wondering what will happen to the existing applicants. Will their applications just disappear, or will it let me continue going through them and approving/declining?
[20:41] <beuno> PriceChild, it will let you continue
[20:42] <PriceChild> beuno: Thanks.
[21:12] <lifeless> spm: what rev of pqm is praesiodymiumiumium running
[21:13] <spm> lifeless: bzr revno is 173 - sound useful?
[21:14] <spm> ps. praseomumble works for us :-)
[21:14] <lifeless> spm: I'm debugging a pqm issue for abentley; code wasn't lining up
[21:14] <lifeless> trunk is on 183
[21:14] <lifeless> mthaddon_: here by chance?
[21:15] <spm> I believe he's at lunch atm
[21:25] <mthaddon_> lifeless, here now - still need anything?
[21:25] <lifeless> mthaddon_: no, but I wanted to ask how the ubunet pqm stuff turned out
[21:26] <mthaddon> lifeless, all looking fine, except that for some reason in the web UI it shows "processing x from other project" or something rather than the actual message
[21:27] <lifeless> mthaddon: the project prefix is wrong
[21:33] <wgrant> You're not doing a very good job of keeping Ubunet quiet.
[21:35] <Ursinha> ?
[21:52] <teferi> hey guys, I have an awful problem with my new launchpad account and the old launchpad account I forgot I had
[21:52] <teferi> namely, I can't set my gpg key for the new account (adam-crossproduct) to the key that's still associated with the old account (teferi)
[21:53] <teferi> and I can't complete the merge of the two accounts because some of the email addresses on the old account are ones I don't have access to anymore
[21:53] <teferi> (presumably launchpad snaffled them from my gpg key)
[21:53] <teferi> can someone help me out?
[21:56] <wgrant> teferi: Ask a question at https://answers.launchpad.net/launchpad, and a Launchpad admin should be able to help you out.
[21:56] <wgrant> Particularly if you have access to the old OpenPGP key, I suppose
[21:56] <teferi> I do
[22:09] <teferi> well, question submitted, but wow is this a pain
[22:11] <wgrant> teferi: What is?
[22:11] <teferi> wgrant: getting my key associated with my account so that I can do an upload to my ppa of the software that I just spent three hours packaging
[22:12] <wgrant> It's quite trivial if you don't have multiple accounts.
[22:12] <teferi> right, but I *forgot* that I *had* the old account
[22:12] <teferi> it was from YEARS ago
[22:16] <xteejx> Can I have a supervisor or account maintainer please?
[22:16] <xteejx> I am a triager for Ubuntu. Please direct your attention to bug 297388. Can we get this account banned?
[22:17] <NfNit|oop> heh.
[22:17] <xteejx> A user is abusing the Launchpad system and the account needs banned before Launchpad is swarming with this "crap"
[22:17] <xteejx> I know... :)
[22:17] <wgrant> xteejx: File a ticket at https://answers.launchpad.net/launchpad
[22:18] <xteejx> I suppose it wouldn't be hard for someone with no brain hehe
[22:18] <xteejx> wgrant: Thanks
[22:18] <xteejx> :)
[22:28] <wgrant> Erm, that bug is now OOPSing.
[22:28] <wgrant> OOPS-1047EC184
[22:50] <flacoste> Mez: hi there
[23:20] <spm> wgrant: I was perhaps a tad too enthusiastic in my cleanup - either way - acct is disabled, and the comments removed
[23:21] <teferi> spm: hey, can you help me out with my account/gpg key issue from above?
[23:21] <wgrant> spm: You removed the initial Message or something similarly destructive?
[23:21] <spm> teferi: not right atm - but sure
[23:21] <rockstar> wgrant, spm is enthusiastic about everything.  You should keep that in a mental note.
[23:21] <spm> rockstar: :-)
[23:22] <teferi> spm: fantastic, thank you so much
[23:22] <rockstar> spm,  what issue are you having?
[23:22] <spm> rockstar: see #lp-code me/gmb
[23:22] <wgrant> rockstar: Sounds bad.
[23:23] <rockstar> spm, oh, I know what you did!  :)
[23:23] <wgrant> What did he do?
[23:23] <spm> wgrant: having raw db/sql access is not always a Good Thing(tm) :-)
[23:24] <spm> drop database :-P
[23:24] <wgrant> TRUNCATE BugTask;
[23:24] <wgrant> THat would fix most of our problems in Ubuntu.
[23:24] <spm> that was a *joke* in case anything suspects otherwise! :-)
[23:25] <rockstar> spm, I just did a dd of lots of urandom onto one of my live and mounted drives just now. Everyone gets excited sometimes.
[23:27] <spm> rockstar: but did you *mean* to do that? ;-)
[23:27] <rockstar> spm, no, not at all.  But I can laugh because I have good backups.
[23:28] <spm> I still think my PB was taking out an entire floor of Cobol programmers from working for 3-4 hours. Mainframes - they allow such *spectacular* messes to be made.
[23:28] <rockstar> I thought it was writing to a USB flash drive.  I only noticed when the music I was listening to went away.  :)
[23:29] <rockstar> spm, I have a friend who worked at Wikimedia, and he said that they have a box which has the sole purpose of being the single point of failure.
[23:29] <rockstar> Breaking it is like a rite of passage for the sysadmins there.  :)
[23:30] <spm> rockstar: aye. +1 to that!
[23:34] <teferi> well, when processing is centralized, so is failure, more or less by def'n
[23:54] <teferi> man, sure wish i'd remembered that that original account existed :/