[00:17] <squeak5> hi is it possible to rename junk
[00:17] <keithy> lets try that question again
[00:18] <keithy> is it possible to have some other name for +junk
[00:18] <keithy> i.e. stuff for the groups use
[00:18] <keithy> that is non project specific
[00:18] <poolie> keithy, squeak5, at the moment no
[00:18] <lifeless> not at the moment
[00:18] <poolie> just register a project
[00:19] <keithy> k
[00:19] <keithy> lol another one!
[00:21] <keithy> ty
[03:05] <MTecknology> I just copied my packages from own ppa to another and it seems that it'si386 and lpia but not amd64... how can I see if that's teh case?
[03:06] <MTecknology> nevermind - I found it
[04:02] <_Andrew> I'm trying to copy my package over to jaunty however I get the following error "The following source cannot be copied: * cegui 0.7.1~ogredev2 in hardy (binaries conflicting with the existing ones)"
[04:02] <_Andrew> https://launchpad.net/~andrewfenn/+archive/ogredev/+packages
[04:03] <_Andrew> Anyone know what I've done wrong?
[04:04] <lifeless> yes
[04:04] <lifeless> you have to use unique version numbers if you do a source copy, because the rebuild will collide
[04:04] <wgrant> Not quite.
[04:04] <wgrant> That error mesage mans you tried to copy some binaries over an existing set.
[04:05]  * lifeless deferrs
[04:05] <wgrant> _Andrew: Where are you copying from?
[04:06] <_Andrew> I tick "cegui - 0.7.1~ogredev2" in my ppa from the hardy series and select jaunty, copy binaries
[04:07] <wgrant> Er. that error shouldn't be possible for intra-archive copies, unless your PPA is already in a bad state.
[04:07]  * wgrant looks.
[04:07] <wgrant> Your PPA is indeed in a bad state :/
[04:08] <_Andrew> oh :(
[04:08] <wgrant> Notice the two instances of 0.7.1~ogredev2 -- the original one with sucessful i386 and amd64 builds, but a failed lpia build; and the second one with just a successful lpia build.
[04:08] <wgrant> It should have rejected that copy attempt.
[04:09] <wgrant> You should never have been allowed to copy it to intrepid.
[04:09] <_Andrew> Also this is something weird
[04:10] <_Andrew> My build for lpia never failed before but now it says the package libicu-dev for lpia is gone which libboost depends on
[04:10] <_Andrew> Did libicu-dev for lpia disappear?
[04:11] <kris928> I am applying a patch to an existing package from another PPA and attempting to then submit the new package source to my own ppa. Do I need to specify any dependencies on the other PPA?
[04:13] <kris928> I'm guessing no, unless the other package had dependencies on things only available in the original PPA
[04:14] <wgrant> _Andrew: That's interesting. I suspect it was a transient issue, since Hardy should just about never be broken.
[04:14] <wgrant> _Andrew: I've identified the bug which caused the bad data, so you should now fix your PPA. The easiest way is to just upload a new version to Hardy, wait for it build on all three archs, and then copy to Intrepid and Jaunty.
[04:15] <wgrant> With any luck lpia will succeed this time.
[04:15]  * wgrant files the bug.
[04:15] <_Andrew> thanks
[04:20] <kris928> is there anyways to estimate the time until a package starts building?
[04:21] <wgrant> kris928: You'll see an estimate if you click on the architecture name in the "Build Status" column.
[04:21] <kris928> wgrant, thanks
[04:30] <tlyu> where should i check for updates on the state of debbugs synchronization?
[04:33] <_Andrew> wgrant, I haven't tried but I think the actual lpia package is missing from ubuntu repo. http://packages.ubuntu.com/hardy/libicu-dev
[04:33] <persia> There's a bunch of different bits to that: https://blueprints.edge.launchpad.net/malone/+spec/debian-bug-import-continuous-imports https://blueprints.launchpad.net/malone/+spec/debian-bug-import-on-demand https://blueprints.launchpad.net/malone/+spec/upstream-bug-searching-and-filing
[04:33] <_Andrew> Not sure why, maybe it's not valid
[04:34] <persia> In gutsy through intrepid there was a lot of ugly substvars stuff done with lpia which may well have broken a number of packages that weren't in the Ubuntu MID flavour.
[04:35] <wgrant> _Andrew: Urgh. OK, try copying from Intrepid to Jaunty instead.
[04:39] <tlyu> persia: thanks. i should have been more specific... remote bug watches for Debian aren't updating automatically. is there something tracking the status of that issue? also, i can't seem to view the wiki page for debian-bug-import-continuous-imports.
[04:41] <persia> Ah, looks like the page for debian-bug-import-continuous-imports is on the old server.  You'd have to get someone with access to get it out.  Wait for a help contact.
[04:42] <persia> I don't know about any issue with updating: I just noticed those URLs when looking for something else.  Maybe someone else knows.
[05:55] <philien> Hi where can I become an Ubuntu devloper ?
[05:56] <poolie> philien: try in #ubuntu-motu
[06:39] <MTecknology> how do I format dput to put to different PPA's ?
[06:40] <cody-somerville> dput ppa:<team>/<ppa name> <changesfile>
[06:41] <MTecknology> cody-somerville: oh, I must have named mine "ppa" then - thanks
[07:53] <GaryvdM> Hi. This page says my ppa upload is going to build in 6 hours: https://edge.launchpad.net/~bzr-beta-ppa/+archive/ppa/+build/1530274
[07:54] <GaryvdM> Is that real, and how come such a long wait?
[07:54] <persia> That's an estimate that can be off by several hundred percent, depending on a wide variety of conditions.
[07:54] <persia> (but is usually roughly accurate)
[07:55] <persia> Why is because there's lots of jobs in the queue, some of which are estimated to be long-building, and so not many buildds today :https://launchpad.net/builders
[07:55] <wgrant> GaryvdM: Lots of the builders are currently being used for other purposes.
[07:55] <wgrant> I've no idea when they'll be back.
[07:55] <GaryvdM> ok thanks.
[07:57] <persia> Err, "not so many" rather than "so not many".  No implication between long build queues and small numbers of buildds was intended.
[07:58] <wgrant> persia: There is an implication between them. Just not the way you said it.
[07:59] <GaryvdM> https://edge.launchpad.net/builders is interesting.  It makes one realize that there is alot going on behind the scenes.
[07:59] <wgrant> GaryvdM: There are normally around 17 builders for each of the PPA architectures.
[07:59] <wgrant> There will soon be lots more.
[07:59] <wgrant> But now there are only four.
[07:59] <GaryvdM> Rather then just dput and a .deb magically pops
[08:00] <GaryvdM> *pops out
[08:00] <wgrant> There's a lot of code and computing power hidden behind everything.
[08:00] <GaryvdM> :-)
[08:15] <albertca> Hi!
[08:15] <albertca> Since yesterday I'm having problems uploading a file of almost 40 Mb
[08:16] <albertca> I've tried it about 5 times but it returns:
[08:16] <albertca> "Sorry, there was a problem connecting to the Launchpad server." when it has finished
[08:16] <albertca> is there anything I can do?
[09:27] <dnjl> hi. what happens with the builders - there are so many jobs on so few builders, but many others are idling. Atm i have to wait a whole working day! :(
[09:33] <dnjl> 12h now
[09:42] <persia> dnjl: There are two separate classes of buildds: distribution buildds and PPA buildds.  The distribution buildds are mostly idle because of the upcoming milestone release (should be in the next 24 hours or so), so people are not uploading to Ubuntu (and LP doesn't currently build for any other distributions).
[09:42] <persia> The PPA buildds seem to be very low in number today.  They may grow or shrink in the future.
[09:42] <persia> But most of the distribution buildds are for other architectures anyway, so wouldn't help populate your PPA even if your job was dispatched there.
[09:43] <dnjl> yes is see
[09:43] <bigjools> the PPA builders are usually only borrowed for short periods
[09:43] <dnjl> but the ppa builders are really low in number - to low i think
[09:43] <bigjools> they get pooled in the build farm when not being otherwised used
[09:44] <bigjools> they are not strictly PPA builders
[09:45] <dnjl> bigjools: just for info, are these non-x86 builders really non-x86 machines or are these emulations?
[09:46] <bigjools> I don't know
[09:46] <dnjl> k :)
[09:46] <bigjools> they run Xen, that's all I know :)
[09:47] <wgrant> The non-x86 builders are not emulated.
[09:47] <wgrant> nor do they use Xen.
[09:48] <wgrant> They are the real thing.
[09:48] <dnjl> oh, wow
[09:52] <persia> Well, for some value of real.  I remember a bug once that one of the i386 buildds was actually x86_64 (and some code inspected too closely during build).
[09:52] <lifeless> they are all x86_64 I believe
[09:52] <persia> They are?  Didn't used to be.
[09:53] <lifeless> possibly not installed as such
[09:53] <persia> Well, no, the i386 buildds are installed as i386.  I just thought some of the processors were real i386 (i686 actually).
[09:55] <wgrant> The non-x86 builders are the real arch.
[09:56] <wgrant> The x86 machines vary.
[09:57] <dnjl> does someone now if its planned to provide such non-x86 builders for ppa builds?
[09:58] <dnjl> know
[09:58] <lifeless> dnjl: we already do, but only for arches which virtualise properly.
[10:00] <persia> dnjl: It essentially depends on porting Xen right now.  If you have hardware for the other architectures and time for a project, it'd be welcome.
[10:01]  * persia would especially like to see it for sparc and powerpc
[10:01] <persia> (well, and armel, but there exists no useful server hardware in retail channels, so it's pointless right now)
[10:01] <dnjl> persia: i thought as much :)
[10:02] <lifeless> dnjl: specifically, we're not putting effort ourselves into fixing xen or kvm for these platforms
[10:03] <lifeless> dnjl: if someone else were to do so, we could look at expanding PPA builds.
[10:04] <persia> lifeless: Is KVM now considered sufficient?  I thought Xen was a requirement.
[10:04] <lifeless> persia: wgrant or another soyuz head will know more; AFAIK it just needs a solid VM layer.
[10:04] <dnjl> sure, its not really your job - as far I see xen-arm is under progress
[10:05] <lifeless> and we used xen atm; if someone had kvm-arm or whatever working, I doubt adapting the setup and teardown scripts would be very hard.
[10:05] <persia> Well, but there's no available hardware, so that doesn't matter so much.
[10:05] <dnjl> but I think kvm whould have more future
[10:05] <lifeless> right. though there is for ppc and sparc
[10:07] <persia> KVM for powerpc seems available (although it requires specialised hardware).
[10:07] <lifeless> Huh.
[10:07] <lifeless> well if someone is very motivated it might be worth digging into.
[10:07] <persia> Well, needs hardware.
[10:07] <lifeless> I have no idea if we have sufficient hardware, or if someone would need to donate/whatever.
[10:08] <lifeless> or even if there is lp interest in PPC; its a fairly niche platform
[10:08] <persia> From what I see, it only works on XBox360 and PS3 right now.  The KVM crew isn't targeting the IBM servers because they ship with an even better hypervisor.
[10:08] <persia> (but that requires big iron)
[10:08] <lifeless> m series?
[10:08] <lifeless> sorry, pSeries
[10:09]  * persia tries to figure out which servers support PowerVM
[10:10] <persia> The Power 750 seems to be the current low-end server providing it (for some values of low-end)
[10:11] <persia> p510 has a different (cruder) VM layer
[10:18] <bilalakhtar> there is a really long queue in the PPA builders
[10:18] <persia> There's a shortage of PPA buildds.
[10:19] <bilalakhtar> yes
[10:21] <persia> So, because there aren't so many buildds, there's a long queue.
[10:21] <persia> This happens occasionally, when some machines get reassigned to other purposes.
[11:24] <dnjl> ah, now there are more ppa builders online again...
[12:18] <gord> hey guys, its *really* hard to select lp:~ links in launchpad code reviews, we do quite a lot of these a week so it would be nice if it were easier to select those ;)
[12:18] <persia> something like making them not hyperlinked and providing a little eyeball icon next to them to view them?
[12:19] <persia> So double-click middle-click just does the right thing?
[12:59] <james_w> gord: +1 I use the address bar currently
[13:00] <gord> persia, yeah something like that, rarely do we need to click them to get to the launchpad.net link, but we *always* need to select them so we can bzr branch them
[13:01] <persia> gord: I actually click on them a lot because I find it's faster for LP to make me diffs or show me a log than to branch for a lot of my operations, but agree it's incredibly annoying when I want a local branch.
[13:01] <persia> james_w: Do you know if there is already a bug for this?
[13:05] <james_w> I don't think there is
[13:06] <soren> I usually just mark it from right-to-left. That's easy enough.
[13:06] <soren> Plenty of space to the right of it to not have to aim all that accurately.
[13:07] <gord> soren, not on any browser i have, there is maybe like a pixel of space to select it, but yes i have to do it right to left too
[13:07] <soren> Sorry, which kind of pages are we talking about?
[13:07] <gord> soren, lp code merge reviews
[13:08] <soren> The one I'm looking at has a wide open space to the right of the link.
[13:08] <gord> soren, yes there is lots of space, but you can't select that space without most browsers selecting everything below it upto the Diff against Target line
[13:09] <Daviey> gord: I've experienced the same issue and find it frustrating
[13:09] <Daviey> although i now work around it.
[13:09] <soren> gord: Do you have an example page?
[13:10] <gord> soren, sorry no the merges i work on are private but any merge request would show it
[13:10] <soren> https://code.edge.launchpad.net/~bart-jukie/vmbuilder/fixes/+merge/4042
[13:11] <soren> Which of those links are we talking about?
[13:11] <gord> soren, "Proposed branch:	lp:~bart-jukie/vmbuilder/fixes"
[13:11] <gord> i just want to select the lp:~bart-jukie/vmbuilder/fixes part
[13:12] <soren> Right.
[13:13] <soren> If you click a couple of inches to the right of that link and drag all the way over to "lp:", what happens?
[13:13] <Daviey> "copy to clipboard"++
[13:13] <soren> I can start all the way over at "Subscribers".
[13:14] <soren> Daviey: Hm?
[13:14] <Daviey> Having a button to copy to clipboard would be pretty useful :)
[13:14] <soren> Sorry, /almost/ all the way over at "Subscribers". Perhaps 30 pixels from it.
[13:14] <gord> soren, it selects the Merge Into: line as well
[13:14] <soren> Daviey: Oh, sure, no argument there.
[13:15] <soren> gord: Weird. I use firefox 3.6?
[13:15] <Daviey> soren: such as http://github.com/scrum8/django-wmd-editor the little "copy" button
[13:16] <soren> Daviey: It's a good idea. I don't like their implementation, though.
[13:16] <gord> soren, chromium-browser here, lets see what firefox does
[13:16] <Daviey> soren: In chromium it selects Merge into aswell
[13:16] <gord> okay so it works fine in firefox but not chromium
[13:17] <soren> Oh, yeah, so it does. :(
[13:17] <soren> That's annoying.
[13:18] <persia> I think it's general webkit.  I have the same issue with epiphany
[13:18] <aboudreault> Hi ppl
[13:19] <aboudreault> Have anyone already seen this "bug" in cowbuilder? http://launchpadlibrarian.net/39753922/buildlog_ubuntu-hardy-amd64.gdal_1.7.1-1~hardy1_FAILEDTOBUILD.txt.gz
[13:19] <aboudreault> search for "- L / b u i l d / b u i l d d"
[13:26] <maxb> aboudreault: What do you consider to be a bug?
[13:26] <aboudreault> maxb: check the library path given to g++
[13:26] <aboudreault> there are spaces throughout it
[13:27] <maxb> well, I'm more inclined to blame the package's buildsystem than cowbuilder
[13:27] <aboudreault> possible too
[13:30] <aboudreault> maxb: any idea what could be done to fix this?
[13:30] <aboudreault> (it's only happen on hardy)
[13:30] <aboudreault> I don't really where to check... or how to debug
[13:30] <aboudreault> *know*
[13:31] <maxb> Use cowbuilder --login, reproduce the problem interactively, and try to figure out where the spaces are coming from
[13:32] <aboudreault> will try that
[13:55] <mathrick> hey guys, is there a "fork this" option a'la github?
[13:56] <mathrick> or else what's the shortest way to have a patch merged upstream?
[13:56] <mathrick> ideally I'd like to branch the project, put it on my launchpad, then send a merge request
[13:57] <james_w> do that? :-)
[13:57] <mathrick> ahh, there is one, only not on the main page
[13:57] <james_w> bzr branch lp:project; cd project; hack; bzr commit; bzr push lp:~your-lp-user/project/fix-12345; bzr lp-open; click "Propose for merging"
[13:59]  * persia reads about bzr lp-open with great pleasure
[14:00] <mathrick> james_w: oh, that's kinda cute
[14:01]  * Daviey didn't know about lp-open either.
[14:01] <mathrick> james_w: it'd be easier to find if the main page for the project showed the [(+) Register a branch] button too
[14:01] <mathrick> at least for logged-in users
[14:02] <wgrant> You're not meant to register a branch.
[14:02] <wgrant> You should just push -- it will create it if it doesn't already exist.
[14:02] <mathrick> as much as I despise git, github makes it really, really obvious what to do to fork a project
[14:02] <mathrick> lpad sadly isn't as obvious, even though I've used it for longer
[14:03] <mathrick> wgrant: so make the button show that instruction instead
[14:03] <mathrick> but it should be there in a visible place under "Get involved"
[14:03] <james_w> +1
[14:04] <mathrick> should I just file a bug against lpad?
[14:06] <persia> Please
[14:15] <mathrick> https://bugs.edge.launchpad.net/launchpad/+bug/527794
[14:15] <mathrick> don
[14:15] <mathrick> +e
[14:16] <soren> Uh.. when I look at https://code.edge.launchpad.net/rhythmbox-ubuntuone-music-store I see two different branches with the same "lp:blah" shortcut.
[14:16] <soren> I think.
[14:17]  * soren stares at the shortcuts..
[14:17] <soren> Yes, I do believe they are identical.
[14:18] <wgrant> soren: ... impressive.
[14:18] <wgrant> The second one doesn't know its alias.
[14:18] <soren> "bzr branch lp:rhythmbox-ubuntuone-music-store" doesn't hesitate, though.
[14:18] <wgrant> If you go to its page, it lists the full URL.
[14:19] <soren> Indeed.
[14:22] <soren> bug #527797
[14:22] <soren> Oh, should I perhaps not have filed it directly against launchpad-code?
[14:23] <wgrant> It's a launchpad-code bug.
[14:27] <soren> Ok. I just wasn't sure if I was supposed to file it against launchpad and then let someone else reassign.
[14:27] <soren> (since that process might include assignment and setting importance and whatnot)
[14:28] <mars> rockstar or sinzui, question: please remind me again why I would want to register a branch?  The help wiki is not being helpful enough.
[14:28]  * persia thinks one never wants to do that manually
[14:29] <wgrant> mars: You don't want to.
[14:29] <wgrant> mars: Just about everyone wants to remove the option to register a non-mirrored branch.
[14:29] <idnar> isn't that useful for external branches?
[14:30] <persia> Oh, I have a use case.  One might want to register a branch, mark it private, and then push.
[14:30] <persia> But I'd think it'd be more interesting to just mark all branches on a project private.
[14:30] <persia> idnar: That can be done when setting up the mirror though, rather than as a separate step, which would make it nicer.
[14:30] <idnar> persia: do you have to mirror it?
[14:31] <persia> For external, wouldn't you want to do so?
[14:31] <idnar> well, I've never actually worked with external branches before, but it seems like mirroring it would just cause confusion
[14:32] <idnar> maybe external branches like that are just impractical
[14:32] <mars> wgrant, yeah, that's the "remind me again" part.  I asked this a year and a half ago maybe?, and didn't see the point then either.
[14:33] <persia> mars: Did you file the bug already?
[14:33] <persia> Add a "usability" tag :)
[14:33] <idnar> persia: I think you can bzr init lp:whatever to create the branch
[14:33] <persia> idnar: I don't see the point of that either, but I suppose one could.
[14:34] <idnar> persia: I was referring to the use case you mentioned
[14:34] <persia> Oh, yeah, but I still think it's better to mark the project private by default, or someone will make a mistake, which, given common reasons projects are private, probably exposes LP to licensing violation risk.
[14:35] <mars> wondering if the "Register branch" button adds to the confusion for users coming from github: they want to know how to fork a branch server-side, and "Register branch" is the only similar option.
[14:35] <idnar> I wish there was a way to see merge proposals for all of the teams I'm in
[14:35] <idnar> having to check each of them separately is annoying
[14:36] <mars> persia, no bug yet, I bet there is one already...
[14:36]  * mars heads off to look
[14:36] <persia> mars: If not, please file.
[14:36] <mars> :)
[14:44] <aboudreault> maxb: looks like setuptools is broken. inside the  the setup.py, I've added a line to display the lib paths... and it is the correct one. once setuptools try to build, there come spaces
[14:53] <mathrick> mars: that's exactly why I filed the bug a moment ago
[14:53] <mathrick> because it's useful as a starting point for someone just starting
[14:54] <mathrick> having the button pop up an explanation of why you don't want to register a branch before pushing is enough, but it should be there
[14:55] <mars> mathrick, yes, that is the bug I was looking for.  Unfortunately, this is two large UX issues:
[14:55] <mars> 1) an obvious branch/patch workflow
[14:55] <mars> 2) removing features that confuse said workflow
[14:56] <mathrick> "this" meaning "removing the [Register a branch] button"?
[14:56] <mathrick> s/this/that/
[14:56] <mathrick> no wait, this was correct
[14:57] <mars> mathrick, yes, killing the button, and putting a big "Here is how you fork the code" box on the right pages, a-la github.
[14:57] <mars> Users have to be shown that server-side forks are not necessary with bzr
[14:57] <mathrick> mars: I'm okay with it, as long as it's blindingly obvious from the main page
[14:58] <mars> yep! :)
[14:58] <mathrick> speaking of which
[14:58]  * mathrick files a wishlist for richer main pages for projects
[14:58] <mars> ah! no!
[14:58] <mathrick> right now I find the overview terribly confusing at best
[14:58] <mars> can of worms there
[14:58] <mars> ok, yes, the project page right now is confusing
[14:58] <mathrick> at least a github-style markdown readme would be good
[14:59] <mars> but adding to it isn't the answer.  Gardening, maybe :)
[14:59] <mathrick> because it makes it easier to put an explanation than not
[14:59] <mathrick> mars: but there are tonnes of projects with not a word of "WTF do I do with that thing?"
[14:59] <mathrick> and that's a big problem
[15:00] <mathrick> there should be an option to have a basic landing page-style thing where you can put an explanation of your project without having to register myproject.net
[15:00] <mathrick> also, wiki
[15:00] <mars> mathrick, oh yes, and Curtis, the team lead who works on those pages, is keenly aware of the Project page issues.
[15:00] <mars> where is the wishlist link....
[15:01] <mathrick> mars: good, but there don't seem to be any bugs open right now
[15:01] <mathrick> at least lpad doesn't admit having any bugs open
[15:01] <mars> mathrick, we went over this a few months ago actually.  November I think?
[15:01] <mathrick> good
[15:02] <mathrick> lagging behind a git-centered site in terms of obviousness is Not A Good Thing
[15:03] <mars> mathrick, true, but it is a bit more complicated that simply "make project code hosting better".  We are by and large here for the Ubuntu community, not just Github for Bazaar.
[15:04] <mars> The Project homepage, for instance, has a few different uses, quite a few more that Github has to worry about
[15:04] <mars> that makes design harder
[15:05] <mathrick> I'm aware of it, but there's still a marked lack of place to put written text for people and projects who *aren't* a part of ubuntu
[15:06] <mathrick> and lpad is supposed to be a project hub for everyone in open source, not just ubuntu
[15:06] <mathrick> as I understand it at least
[15:06] <mars> mathrick, yes, and the markdown/ReST README is on the wishlist.  As is having a wiki.  Wiki is really high on the user request list, maybe #1?
[15:07] <mathrick> good
[15:10] <mars> mathrick, finally, found it:  https://dev.launchpad.net/Wishes
[15:11] <mars> that cover's idnar's wish for a dashboard as well: #2 on the list, in fact :)
[15:12] <mathrick> that it took you so long is probably a good indication the current structure is not really obvious :)
[15:13] <mathrick> 1. Wiki, backed by Bazaar preferably. Defintely not MoinMoin :)
[15:13]  * mathrick agrees so hard
[15:13] <mathrick> MoinMoin is horrible
[15:15] <mars> you are right
[15:15] <mars> I looked on the dev.launchpad.net frontpage, and didn't find anything
[15:17] <mars> kfogel, around?
[15:21] <kfogel> mars: around for a few more minutes, what's up?
[15:30] <mathrick> https://dev.launchpad.net/Wishes/Git <-- meh, I don't like the idea of making yet another git project hosting site
[15:31] <albertca> Since yesterday I'm having problems uploading a file of almost 40 Mb
[15:31] <albertca> I've tried it about 5 times but it returns:
[15:31] <albertca> "Sorry, there was a problem connecting to the Launchpad server." when it has finished
[15:31] <albertca> is there anything I can do?
[15:35] <mathrick> albertca: it might be limiting the size of allowed uploads, and if so, it means the error code is wrong and should be clearer
[15:35] <mathrick> s/code/message/
[15:35] <albertca> in theory maximum size is 200Mb so that should not be the problem.
[15:36] <albertca> I've uploaded files of the same size previously...
[15:36] <mathrick> ah
[15:36] <mathrick> filing a bug sounds like the best course then
[16:20] <eagles0513875> hey guys i have a question i have a back up of an ssh key i did on another install on another machine i just setup another dual boot partition on a different machine. what do i need to do to get that to be used by bzr so i dont have to change my ssh key on lp
[16:24] <nigelb> eagles0513875: copy the .ssh folder to your new system
[16:24] <nigelb> I would suggest using 2 keys though
[16:25] <eagles0513875> nigelb: ok and that is all i need to do is copy it to my new system. and why 2 keys
[16:25] <nigelb> well, thats just personal preference
[16:26] <eagles0513875> so when i come to use bzr i should be ok like that
[17:14] <CardinalFang> Hi all.  Please tell me if this is a decent feature request:
[17:15] <CardinalFang> On  https://code.edge.launchpad.net/~cmiller/desktopcouch/get_port_through_dbus/+merge/20066
[17:16] <CardinalFang> I would like to be able to hilight/select/copy the  lp:~....  text.
[17:17] <james_w> CardinalFang: see about 5 hours ago where someone else requested the same thing :-)
[17:17] <CardinalFang> Ha.
[17:18] <james_w> everyone seemed to be in agreement it was a good idea
[17:19] <CardinalFang> Roger.  Geez, james_w, you're omnipresent.  I half expect to find you in my pantry.  "Hi Chad!  If you're looking for ingredients, I've already made some dinner.  Here, have some."
[17:20] <james_w> CardinalFang: I'd never give food away that easily ;-)
[17:28] <sshaw> I'm completely new to ppas etc,  I need to copy at-spi from lucid to my team's ppa for karmic
[17:29] <sshaw> is there a good reference on how to do this?
[17:37] <CardinalFang> sshaw, I suspect you'll have to "apt-get source foo" to get source, update the debian/changelog , and "dpkg-buildpackage -S" and "dput foo.changes", at the very least.
[17:38] <sshaw> CardinalFang: cool... I'm slowly picking more and more of this up
[17:39] <CardinalFang> sshaw, I'd build the binary package with "pbuilder" also, to make sure you can backport it.
[17:45] <sshaw> CardinalFang: thanks for the tip
[18:02] <ubuntujenkins> Hi guys I am working with the ubuntu manual project and we are going to capture screen shots for all 40 languages that it is translated in. We are in the process of devleoping a program to deal with them. We were thinking of setting up a bzr branch to with subfolders for each language and within those one for each chapter. How ever we would like our program (quickshot) to only pull the folder for the relevant languag
[18:02] <ubuntujenkins> e. is this possible?
[18:03] <CardinalFang> ubuntujenkins, #bzr will answer better, but I think the answer is that you can not branch/pull a subtree of a branch.  All or nothing.
[18:05] <CardinalFang> ubuntujenkins, You could make a master branch, then branch from that for language XX, then add stuff to it and push it up as a sister tree to the master.  Then later merge them.
[18:14] <ubuntujenkins> Hi guys I am working with the ubuntu manual project and we are going to capture screen shots for all 40 languages that it is translated in. We are in the process of devleoping a program to deal with them. We were thinking of setting up a bzr branch to with subfolders for each language and within those one for each chapter. How ever we would like our program (quickshot) to only pull the folder for the relevant langua
[18:14] <ubuntujenkins> ge. is this possible? Or will I have to make forty branches?
[18:15] <ubuntujenkins> sorry wrong channel please ignore it
[18:17] <ghedo> hi
[18:58] <realbadapple> gnome is removing the ability to have icons in menus completely go to "http://poll.fm/1n2n1" and vote to get it back.
[18:59] <beuno> realbadapple, please don't spam the channel
[19:00] <realbadapple> I'm not spamming the channel I sent one message that pertains to all gnome user
[19:02] <beuno> right, not launchpad users
[19:04] <realbadapple> half of the people using launchpad are using gnome!
[19:11] <sshaw> how long after running dput does it take for packages to show up on the website
[19:26] <sshaw> ls
[19:26] <sshaw> oops, sorry
[21:42] <wgrant> sshaw: You will receive an email in less than 5 minutes, unless you didn't sign the package or there is something catastrophically wrong with it.
[21:43] <sshaw> wgrant: thanks
[22:10] <GaryvdM> Hi. If you have requested a package to be deleted from a ppa, and it has not yet been deleted, can you undo the delete?
[22:10] <wgrant> GaryvdM: If you deleted it within the last week;
[22:10] <wgrant> GaryvdM: Click 'Copy packages', and filter for Superseded packages.
[22:11] <wgrant> You should find your package there.
[22:13] <GaryvdM> wgrant: Ah, cool. thanks.
[22:14] <kirkland> can someone point me to a regex or something for what valid launchpad usernames look like?
[22:16] <wgrant> kirkland: r"^[a-z0-9][a-z0-9\+\.\-]*\Z"
[22:16] <kirkland> wgrant: cool, thanks.
[22:16] <wgrant> (taken from the DB constraint)
[22:16] <kirkland> wgrant: so a username *cannot* start with a -
[22:16] <wgrant> kirkland: No.
[22:16] <kirkland> wgrant: perfect, thanks
[22:27] <mwhudson> for a while you could create a launchpad name that *ended* with \n
[22:27] <wgrant> Heh.
[22:27] <mwhudson> because of what $ means
[22:28] <james_w> ooh, good one to know
[22:45] <lifeless> mwhudson: ouch!
[22:45] <lifeless> mwhudson: there is an re flag for that
[22:51] <mwhudson> lifeless: yes, that's why you can't any more :)
[22:52] <lifeless> me wanna ;P
[23:28] <Lord-Readman> Anyone here that can approve my ubuntu translation imports ? https://translations.edge.launchpad.net/~robert-readman/+imports
[23:28] <Lord-Readman> its just its been going slow lately