[00:17] <ubotu> New bug: #194576 in malone "e-mail reply from help@bugs.launchpad.net missing content" [Undecided,New] https://launchpad.net/bugs/194576
[02:36] <ubotu> New bug: #194601 in malone "Mailed bug attachments aren't attached, but in the bug itself" [Undecided,New] https://launchpad.net/bugs/194601
[03:30] <stdin> Odd_Bloke/Odd_Blok2: you need to fix your connection
[03:59] <harrisony> my emails arnt working at this moment so i thought this would be the next best place, OOPS-784EA12
[04:00] <jetsaredim> how do I go about using my PPA to build a new package for both gutsy and hardy?
[04:08] <jetsaredim> can someone help me figure this out? http://launchpadlibrarian.net/12160394/buildlog_ubuntu-hardy-i386.firebug_1.1.0%7Eb11%2Bsvn317-0ubuntu2_CHROOTWAIT.txt.gz
[04:11] <harrisony> jetsaredim:thats a bug with the launchpad ppa system "Failed to fetch http://ppa.launchpad.net/jetsaredim/ubuntu/dists/hardy/main/binary-i386/Packages.gz  404 Not Found"
[04:13] <jetsaredim> awesome
[04:13] <jetsaredim> so, how do i fix?
[04:14] <harrisony> you cant im sorry to say
[04:14] <harrisony> (i think)
[04:17] <jetsaredim> so, how do i get my package into my ppa?
[04:19] <harrisony> Odd_Blok2: please, fix your connection! 
[04:20] <harrisony> jetsaredim: hmm, thats the million dollar question. try do it again 
[04:20] <jetsaredim> i need to bump my package version then?
[04:20] <harrisony> hmm, just add ~ppa1 or something to the end
[04:21] <jetsaredim> or can i just dput -f or something?
[04:41] <jetsaredim> omfg
[04:42] <jetsaredim> ok - can someone tell me how to include another ppa in my build chroot?
[04:51] <ScottK> Don't think you can.
[04:51] <ScottK> You need to upload whatever it is to yours
[04:53] <jetsaredim> so upload the dep into my ppa and build it?
[05:11] <ScottK> Yep
[05:11] <jetsaredim> is there a way to do that from the source package?
[05:12] <jetsaredim> I can't seem to find the branch
[06:26] <XiXaQ> Hello everyone. I just received a question, which I've never thought of before. When you post a reply to a bug on launchpad, mail is sent out to other participants, and they can see your mail address. Is that normal behaviour? 
[06:27] <harrisony> XiXaQ: yes and yes
[06:28]  * Hobbsee watches the mails on lp users happily
[06:37] <XiXaQ> hmm. Isn't that abit strange in this day and age? 
[06:37] <Hobbsee> XiXaQ: it's a bug.
[06:37] <Hobbsee> well, it's a bug if you've set your email to be private
[06:37] <Hobbsee> otherwise, it's intended
[06:42] <XiXaQ> oh, so not hiding e-mail address is default then?
[06:44]  * Fujitsu has forgotten after 3 years.
[06:47]  * Hobbsee adds fuel to the fire.
[06:47]  * Fujitsu incinerates Hobbsee for common sense.
[06:47] <Hobbsee> heh
[06:52] <Hobbsee> Fujitsu: actually...to create some real fuel...it would be helpful to CC ubuntu-women@ and those kind of lists
[06:53] <Fujitsu> Hahahahahha.
[06:53] <Fujitsu> lp-users would exploe.
[06:53] <Fujitsu> With a few extra ds.
[06:56] <Hobbsee> Fujitsu: i look forward to the day where they force pictures too, so they feel more comfortable, then hear the outcry then
[07:18] <coolbhavi> hello all
[07:19] <coolbhavi> The Launchpad answer tracker support team channel is up.. #ubuntu-helpteam
[07:19] <Fujitsu> That sounds like the Ubuntu answer tracker.
[07:20] <coolbhavi> yes.. 
[07:20] <Fujitsu> Not the Launchpad one in general.
[07:20] <ubotu> New bug: #194647 in launchpad "Launchpad sends me multiple mails about bugs when I assign them to myself" [Undecided,New] https://launchpad.net/bugs/194647
[07:20] <ScottK> Fujitsu: ^^^ The bug we were discussing.
[07:21] <Fujitsu> Yep.
[08:11] <Hobbsee> Fujitsu: erm, what did cprov say a while ago?
[08:12] <Hobbsee> if it's showing as published...then where are my binaries?
[08:12] <Fujitsu> Which package?
[08:13] <Fujitsu> Hobbsee: There's probably a queue.
[08:13]  * Fujitsu checks /+buils
[08:13] <Fujitsu> +d
[08:13] <Fujitsu> Hm.
[08:13] <Hobbsee> Fujitsu: it's built
[08:14] <Hobbsee> oh neat.  adding teams to other teams is broken.
[08:14] <Fujitsu> I suspect they'll appear in a little under 6 minutes.
[08:14] <Fujitsu> Binaries still have to get publishe.
[08:14] <Hobbsee> if i don't have permissions to add one of my teams to that team, *why* are you giving me an option in the menu to do so, then bailing out?
[08:14] <Fujitsu> But it now builds from accepted, so sources on't have to be publishe.
[08:14] <Fujitsu> Because it wants you to file a bug on it.
[08:14] <Hobbsee> it must do.  it must do.
[08:16]  * Hobbsee wonders why this wasn't seen before.
[08:17] <Hobbsee> oh, it's only for restricted teams.  so, for restricted teams, hide the option.  simple, no?
[08:18] <Fujitsu> Aha.
[08:19] <Hobbsee> filed.
[08:19] <Fujitsu> Sehr gut.
[08:20] <Hobbsee> ja.
[08:26] <ubotu> New bug: #194657 in malone "don't show the "add one of my teams" menu when users don't have permission to do so" [Undecided,New] https://launchpad.net/bugs/194657
[11:32] <cprov> Hobbsee: Fujitsu: anything wrong ?
[11:35] <Fujitsu> cprov: Looks good to me.
[11:37] <cprov> Fujitsu: good.
[11:41] <Hobbsee> cprov: just confusion over when it says "published" and when teh binaries actually appear, i think
[11:42] <cprov> Hobbsee: uhm, bzr-team already complained about that, I have to investigate a UI solution.
[11:43] <Hobbsee> cprov: right
[11:43] <Fujitsu> I'm not sure how you can represent that better.
[11:43] <Hobbsee> cprov: obviously, i'ts talking about sources published, not binaries...but it's still confusing
[11:43]  * Fujitsu saw a bug on that.
[11:43] <Hobbsee> it'd probably be better to show whether the binary is published or not
[11:43] <cprov> Fujitsu: we could simply present the build & binary publication status 
[11:44] <cprov> build status & binary publication status, that's what I meant.
[11:44] <Fujitsu> Hmm...
[11:45] <cprov> Hobbsee: in the current code, the deb file link is only presented if it's published, but I think it's too subtle 
[11:45] <Fujitsu> Perhaps a table with a row for each architecture, showing build/publication status, inside the usual source rows.
[11:45]  * cprov goes towards the coffee machine ...
[11:46] <cprov> Fujitsu: yes ... i could be in binary section
[11:46] <Hobbsee> cprov: usually, people would want to know if the source was published, not the binary, no?
[11:47] <Hobbsee> cprov: hmmm...with the new fixes, does the ubuntu, etc, stuff get accepted straight away too?
[11:47] <Fujitsu> Hobbsee: Other way aroun, you mean? Most people don't care about sources.
[11:47] <Fujitsu> Hobbsee: Has for months now.
[11:47] <Hobbsee> Fujitsu: er, yes.
[11:48] <Hobbsee> Fujitsu: right, good.  i thought ti did, unless things were on manual
[11:48] <Fujitsu> Ubuntu has been builing from accepte for a long time, as far as I know.
[11:48] <Hobbsee> so, then why would anyone care about whether the source was published at all?
[11:48] <Fujitsu> It's the easiest thing to show. I can't see a way to cleanly show the binaries.
[11:50] <cprov> Hobbsee: Fujitsu: no, ubuntu sources still have to wait the queue-builder run to be dispatched.
[11:50] <Hobbsee> cprov: will that change anytime soon?
[11:50]  * Fujitsu didn't think that was what Hobbsee asked.
[11:51] <cprov> Hobbsee: yes, at some point in this milestone
[11:52] <Hobbsee> Fujitsu: it's what i meant to ask.  i may have phrased it badly
[11:52] <Fujitsu> Ah, sorry.
[11:53] <Hobbsee> Fujitsu: if the sources automatically, almost instantly get queued to build binaries, and all that remains is the build queue, then the only important "published" status is for the binaries, no?
[11:53] <Hobbsee> cprov: ah, good.
[11:53] <Fujitsu> Hobbsee: That's a good point.
[11:53] <Hobbsee> Fujitsu: which means the question of what information to show, in that box, is trivial.
[11:53] <Fujitsu> But how to show the multiple statuses?
[11:54] <Hobbsee> Fujitsu: what would the required statuses be?
[11:54] <Fujitsu> You've got a status for each of the three archs.
[11:55] <Hobbsee> oh.
[11:55] <Hobbsee> hm.  the first one, i think.
[11:55] <cprov> architectures built, as in i386, amd64, ***lpia***
[11:55] <Hobbsee> wouldn't be all of them, else ubuntu's stuff would rarely be published (thanks ppa)
[11:55] <Hobbsee> er, thanks *hppa*
[11:55] <Hobbsee> cprov: yeah
[11:55] <Fujitsu> hppa isn't bad these days.
[11:55] <Hobbsee> Fujitsu: i think if you had at least one of the arches built, it should be OK
[11:56] <Hobbsee> and should be listed as published
[11:56] <Hobbsee> either that, or requiring {amd64, i386} to be published, as those are the most common ones
[12:00] <Fujitsu> There must be a less ugly way to do that. Special-casing archs sounds very wrong.
[12:00] <cprov> Fujitsu: +1
[12:01] <Hobbsee> Fujitsu: which is why i'd go with "one arch is built.  mark as published"
[12:01] <cprov> we could simply present the archs being built and their status (as color) in a column
[12:01] <Fujitsu> Speaking of things like this, the build failures column on +packages needs to be made more useful.
[12:01] <Hobbsee> Fujitsu: and hope that the others are fairly fast
[12:01] <Fujitsu> cprov: I'd considered that. I suppose it would work with so few archs.
[12:01] <Hobbsee> (which, in practice, they tend to be)
[12:02] <cprov> yes, it's fairly limited.. [architectures domain]
[12:04] <Fujitsu> Having columns for each with the status progressing Pending->Builing->Accepted->Published could well work.
[12:07] <cprov> Fujitsu: I was thinking in a single columns, "Binaries" which would contains the architecture tags linking to the build page and representing their status with colors 
[12:08] <Fujitsu> I don't particularly like the idea of having status encoded exclusively by colour.
[12:08] <cprov> Fujitsu: we have the build icons, if you prefer
[12:08] <Fujitsu> Ooh, that's true.
[12:08] <Fujitsu> Still not ideal, but better.
[12:09] <cprov> Fujitsu: any other alternative to be considered ?
[12:10] <Fujitsu> It'd be nice to display the full status, but the icon would work, particularly as it seems to have a title.
[12:10] <Fujitsu> And an alt. Even better.
[12:11] <cprov> Fujitsu: yes, I guess, the icon will work fine.
[12:12] <cprov> Fujitsu: but it has to be besides the architecture-tag itself, otherwise it will continue to be confusing.
[12:13] <Fujitsu> Yes.
[12:16] <cprov> Fujitsu: it could solve https://bugs.edge.launchpad.net/soyuz/+bug/191703
[12:16] <ubotu> Launchpad bug 191703 in soyuz "ppa overview page doesn't make failed archive visible" [High,Triaged]  - Assigned to Celso Providelo (cprov)
[12:16] <Fujitsu> It would.
[12:25] <cprov> Fujitsu, Hobbsee: thanks for helping with this. i have to go now, see you later.
[12:25] <Fujitsu> Bye, cprov-out.
[14:31] <jetsaredim> how do I pull a package from someone else's ppa into my ppa?
[16:01] <_KAMI_> hi!
[16:02] <_KAMI_> I am the current hungarian Localizator of Seamonkey. How can I get my translations into Ubuntu?
[16:02] <_KAMI_> But https://translations.edge.launchpad.net/seamonkey says            Translation setup needed
[16:02] <_KAMI_> I have all translations in "mozilla form"
[16:04] <_KAMI_> Same apply for IceApe https://translations.edge.launchpad.net/iceape
[16:08] <arj> if I need someone else to commit to a branch I have on launchpad do I need to create a team to do that?
[16:10] <arj> and why can't I use an email I have already for a team?
[16:10] <arj> it says that email is used for my current user
[16:16] <arj> figured it out, but it wasn't very intuitive
[16:35] <afflux> how can I get the translations of my program marked as "synced", so the bar in rosetta becomes green?
[16:36] <afflux> (project translations, not ubuntu translations)
[16:37] <wbrady> Can someone please make intro2it into a super project? https://answers.launchpad.net/launchpad/+question/25435
[17:10] <wbrady> anyone home?
[17:30] <awilkins> Question : is it considered acceptable for someone unassociated with a project to ask for it's CVS/SVN repository to be imported into L=aunchpad?
[17:31] <Nafallo> !weekend
[17:31] <ubotu> It's a weekend.  Often on weekends, the paid developers, and a lot of the community, may not be around to answer your question.  Please be patient, wait longer than you normally would, or try again during the working week.
[17:32] <Nafallo> hopefully people are using their days off ;-)
[17:38] <Odd_Bloke> Not only is it a weekend, it's FOSDEM weekend! \o/
[17:39] <afflux> my connection broke down, did anyone answer on my translation/sync question?
[18:42] <kiko-afk> awilkins, no, it's perfectly fine to request any project be imported!
[18:43] <jetsaredim> how do I pull software from someone's ppa into mine?
[18:45] <Nafallo> hiya kiko
[18:59] <kiko-afk> jetsaredim, you can't -- yet.
[19:00] <jetsaredim> i mean - obviously there's no way to do it directly through lp, but i meant by some manual means 
[19:01] <ScottK> Download the source and then upload it to your PPA.
[19:02] <jetsaredim> I think I tried that
[19:03] <jetsaredim> so I should be able to download the source, debuild -S -sa, and then upload the source.changes to my ppa?
[19:04] <ScottK> debuild -S -sa -kYOURKEYID
[19:04] <ScottK> That or edit debian/changelog to have your name/address as the last entry
[19:05] <jetsaredim> ah ok
[19:54] <ffm> If I add a new email address and change it to the default, is the old default notified?
[19:55] <Toobaz> danilos: ehm... I'm still here... since my .po/.pot files still "need review"... evidently, there is the problem you said yesterday with the paths. I can delete them and reload them without any path, but will they integrate with translations already done?
[20:11] <luisbg> is launchpad's ssh down? it is giving me time out
[20:12] <tdoggette> I need to create a mailing list for the development team on a project. Is there a way to do this from within Launchpad?
[20:13] <ffm> tdoggette: you a beta tester?
[20:13] <tdoggette> Yes.
[20:13] <ffm> tdoggette: it was in a email sent to you on how to.
[20:14] <tdoggette> Great. Do I need to be a driver or group leader?
[20:14] <ffm> tdoggette: idk.
[20:14] <tdoggette> I'll check it out
[20:15] <ffm> tdoggette: what's your project name? GASP?
[20:15] <ffm> tdoggette: if so, its already set up. gasp-dev@lists.launchpad.net
[20:15] <ffm> tdoggette: see also https://help.launchpad.net/ListHelp
[20:37] <sayers> Hello! I just formed a new project and I'm wondering where I upload my code?
[20:37] <ffm> sayers: via bzr
[20:38] <sayers> ffm, Is there any howto with that? It seems rather complex to use
[20:39] <Toobaz> do you have an ssh key?
[20:39] <ffm> sayers: http://www.justuber.com/blog/2007/04/25/how-to-use-bazaar-and-launchpad-for-hosting-your-code/
[20:39] <sayers> yes
[20:49] <sayers> Alright ffm I got my local bzr set up
[20:50] <sayers> but where do I commit to
[20:50] <Amaranth> whoa, I seem to have access to https://code.edge.launchpad.net/awn/trunk/+source
[20:50] <ffm> you set one up on launchpad too.
[20:50] <ffm> and push
[20:50] <Amaranth> I don't think I should be able to get there
[20:50] <Amaranth> Or does it just error out after I try submitting the form?
[20:50] <sayers> ffed, bzr: ERROR: Transport operation not possible: http does not support mkdir() is my error
[20:50] <Toobaz> sayers: you have gutsy?
[20:50] <sayers> ffm*
[20:50] <sayers> yes
[20:51] <Toobaz> bzr version is too old
[20:51] <sayers> okay.
[20:51] <ffm> sayers: don't use http, use ssh+bzr://
[20:51] <sayers> So I need to compile
[20:51] <ffm> or just use lp:foo
[20:51] <Toobaz> ffm: there is not on gutsy, I think
[20:51] <Toobaz> is it?!
[20:52] <ffm> no idea
[20:52] <sayers> ffm, so what would an example command be then
[20:52] <Toobaz> it's several days I keep a virtual machine with debian testing inside just to give the "push" commands
[20:52] <Toobaz> bzr push lp:~sayers/nameofyourproject/trunk
[20:53] <Toobaz> but I don't think it will do
[20:53] <ffm>                  bzr push bzr+ssh://ffm@bazaar.launchpad.net/~ffm/gasp-code/gasp-0.x-stable
[20:53] <ffm> sayers: above
[20:54] <sayers> so /rateagirl/trunk 
[20:54] <Toobaz> right
[20:54] <sayers> bzr: ERROR: Generic bzr smart protocol error: Permission denied: "This method is only for creating branches: /rateagirl/trunk"
[20:54] <Toobaz> terrific
[20:54] <sayers> i need /trunk/sayers ?
[20:55] <Toobaz> no, ffm's command is the right one
[20:55] <Toobaz> (or: bzr push lp:~ffm/gasp-code/gasp-0.x-stable
[20:55] <Toobaz> )
[20:55] <sayers> Then what am I doing wrong iwth 
[20:55] <sayers> bzr push bzr+ssh://sjsayers93@bazaar.launchpad.net/rateagirl/trunk/sayers/
[20:55] <Toobaz> I think  - not sure, but it's several days I'm trying - Gutsy simply can't do it
[20:56] <sayers> then what do I do?
[20:57] <Toobaz> I can tell you what I did: virtualize a Debian. But what probably you should do is recompile bazaar. Or try to install the hardy package, but it has dependencies too. Or wait someone more expert gives you his advice.
[20:57] <ffm> enable backports
[20:58] <Toobaz> sayers: yeah, I think this will do
[20:58] <sayers> ah
[20:58] <sayers> i didnt have a branch made
[20:58] <sayers> it's uploading I gues
[20:58] <sayers> guess8
[20:58] <sayers> yep works
[20:58] <Toobaz> wow
[20:59] <Toobaz> in this case, I'm an idiot
[20:59] <sayers> http://bazaar.launchpad.net/~sjsayers93/rateagirl/main/files
[20:59] <sayers> well
[20:59] <sayers> I guess so :p
[21:08] <SteveM> I've had repeated failures trying to upload a fairly large (~30mb) file to a download area. Each has brought me to the "Please try again" page. Any advice?
[21:25] <Fujitsu> SteveM: Is it a normal Launchpad error page?
[21:26] <SteveM> Fujitsu: I believe so (though I haven't seen it before today).
[21:26] <SteveM> "Sorry, there was a problem connecting to the Launchpad server."
[21:27] <Fujitsu> Right, that's not the normal one.
[21:27] <Fujitsu> It came up yesterday too, and they're looking into it.
[21:30] <SteveM> Thanks. It's no hurry. I'll just try again later. Thanks.
[21:52] <Toobaz> Fujitsu: may I ask to you for pot/po upload problems?
[21:53] <ffm> can the pycon meeting/sprint be added to launchpad as a proposed discussion/implementation time for blueprints?
[21:54] <Fujitsu> Toobaz: I have no special privileges, but I may be able to answer questions.
[21:57] <Toobaz> Yesterday 2 files of mine (a .pot and a .po) where reviewed and approved. But... I uploaded them as I had them on my PC: the tarball contained the .pot and a folder "po" with the .po inside. Danilos, who approved them, said this could bring problems... and actually it does: I uploaded new versions of both but they are not automatically approved.
[21:58] <Toobaz> So I thought to just remove them and reupload without different paths... but do you think it shall give problems to already done (on LP) translations
[21:58] <Toobaz> ?
[22:00] <Fujitsu> Can't you just reupload them without deleting the old ones?
[22:00] <Toobaz> yep, and it doesn't matter if I have to wait days, but shall them integrate with the translations other people did on LP?
[22:01] <Toobaz> or shall they delete them? or appear as other available translations?
[22:01] <Fujitsu> Hmm, I thought they should be automatically approved.
[22:01] <Fujitsu> You'll have to talk to one of the Translations people.
[22:02] <Toobaz> ok
[22:02] <Toobaz> thanks
[22:03] <ffm> can the pycon meeting/sprint be added to launchpad as a proposed discussion/implementation time for blueprints?
[22:03] <Fujitsu> ffm: It's likely nobody here knows.
[22:03] <Fujitsu> !weeken
[22:03] <ubotu> Sorry, I don't know anything about weeken - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[22:03] <Fujitsu> !weekend
[22:03] <ubotu> It's a weekend.  Often on weekends, the paid developers, and a lot of the community, may not be around to answer your question.  Please be patient, wait longer than you normally would, or try again during the working week.
[22:03] <Fujitsu> Stupid keyboar.
[22:04] <Toobaz> wow. I think I'll have a chat with ubotu
[22:13] <ffm> any idea how long it takes launchpad notifications to arrive?
[22:20] <ffm> or how I can stop getting them? I often get notified when I do something, which  is just spam to me.
[22:20] <Fujitsu> Launchpad bug email notifications?
[22:22] <ffm> that, and blueprints.
[22:22] <ffm> "ffm changed the priority of blueprint foo!"
[22:22] <Fujitsu> Ah.
[22:22] <Fujitsu> Well, you could always not subscribe to them.
[22:25] <ffm> I am the creater of said blueprint.
[22:26] <Fujitsu> Ah. You're probably stuffed, then.
[22:27] <ffm> Fujitsu: hm?
[22:27] <Fujitsu> You could unsubscribe, I guess...
[22:27] <ffm> Fujitsu: I'm not subscribed.
[22:27] <Fujitsu> But there's no option to not recieve notifications about your own actions.
[22:28] <Fujitsu> Are you the assignee, drafter, approver, etc?
[22:28] <ffm> Fujitsu: Registrar, Drafter, and sometimes approver.
[22:28] <Fujitsu> They'll all probably get you notified.
[23:02] <awilkins> kiko-afk: Thanks
[23:05] <ffm> woot, my project is featured!
[23:05] <sayers> what is it?
[23:05] <ffm> sayers: GASP.
[23:06] <ffm> http://launchpad.net <-- It's in the list!
[23:10] <luisbg_> is launchpad's ssh down? it is giving me time out
[23:10] <luisbg_> when trying to bzr push bzr+ssh://...
[23:43] <RainCT> Hi
[23:43] <RainCT> just wanted to let you know that the message you get when sending a mail to help@bugs.launchpad.net says: " If you have questions or comments about this document, please
[23:43] <RainCT> address them to {{{" (note this last 3 characters)
[23:45] <RainCT> it also refers to https://wiki.launchpad.canonical.com/MaloneEmailInterfaceUserDoc, which doesn't work, at least not for me..
[23:46] <RainCT> well, good night