| JZA | hi anyone know why launchpad is so slow | 00:26 |
|---|---|---|
| JZA | I am doing a checkout of a project | 00:26 |
| JZA | and is taking hours | 00:26 |
| JZA | I get.. Fetching revisions:Inserting stream:Estimate 589932/600665 | 00:27 |
| JZA | and only 43kbp/s transfer rate | 00:27 |
| wgrant | JZA: Which project? | 00:30 |
| wgrant | And how good is your ISP's connection to London? | 00:30 |
| JZA | they were supposed to be just scripts | 00:30 |
| JZA | but is a bit more than that | 00:30 |
| JZA | https://code.launchpad.net/~openerp-dev/openobject-addons/ | 00:31 |
| JZA | anyhow, still should take around 20 min, it's been downloading for hours now | 00:31 |
| JZA | I can downlaod a 1gb movie in 20min | 00:31 |
| JZA | usually less | 00:31 |
| wgrant | There's a bit of a difference between downloading a single large file from local peers, and downloading a complex VCS tree from another continent, I'm afraid. | 00:33 |
| wgrant | Lots of ISPs have pretty terrible connections to Europe. | 00:34 |
| wgrant | However | 00:34 |
| wgrant | Are you downloading over HTTP or SSH? | 00:34 |
| === thomi_ is now known as thomi | ||
| JZA | wgrant: I am downloading from bzr, I guess it would use ssh | 01:30 |
| JZA | wgrant: who says I am in europe? | 01:30 |
| wgrant | JZA: Launchpad is in Europe | 01:30 |
| JZA | wgrant: my bandwith is around 10mbps | 01:30 |
| wgrant | And that branch is more than just scripts; it's about 700MB | 01:30 |
| wgrant | JZA: bzr will use SSH if you've used 'bzr lp-login', HTTP otherwise. | 01:31 |
| JZA | oh | 01:31 |
| wgrant | I'm not quite sure what's in there | 01:32 |
| wgrant | But whatever it is, it's pretty huge... | 01:32 |
| JZA | wgrant: sucks... | 01:32 |
| JZA | I wonder why launchad cant zip the whole tree as a tarball | 01:32 |
| wgrant | Normally projects release tarballs/zips themselves, but Launchpad can generate them directly from a branch. http://bazaar.launchpad.net/+branch/openobject-addons/tarball might work, but I don't know how well it scales to several hundred megabytes... | 01:35 |
| JZA | welll it's definely going faster | 01:36 |
| JZA | would it only tar the main branch? | 01:37 |
| wgrant | JZA: That's for a single branch, yes. | 01:38 |
| JZA | I see | 01:40 |
| dobey | which branch are you downloading? | 01:49 |
| dobey | and why are there so many branches, sheesh | 01:50 |
| JZA | dobey: not sure, this was supposed to be only some scripts | 01:51 |
| JZA | but I guess this have to be compliat for each addon | 01:51 |
| dobey | what was? what bzr command did you use? | 01:51 |
| JZA | so they include the addons | 01:51 |
| JZA | bzr branch lp:openupgrade-addons | 01:52 |
| dobey | uhm | 01:53 |
| dobey | that is not openobject-addons | 01:53 |
| dobey | also, that is one heck of a lot of directories in a bzr branch | 01:54 |
| JZA | umm... ur right | 01:54 |
| JZA | too similar names | 01:54 |
| dobey | anyway, it looks like there also plenty of binary files in the tree | 01:56 |
| dobey | binary files make the size of the history to be quite large, if they are changed often | 01:56 |
| JZA | :S | 01:56 |
| lifeless | dobey: actually binary isn't a problem per se; it's files where when they change the majority of the file changes thats an issue - and many binary files have this characteristic (but many don't) | 02:00 |
| lifeless | for instance, running sqlite db's in bzr would be fine | 02:00 |
| dobey | well, i don't guess this branch is in that category of not having the problem | 02:03 |
| dobey | because i'm pulling that branch right now, and getting upwards of 7MB/s download at times, mostly it's around 3 MB/s. and it is taking quite a long while to pull it | 02:05 |
| dobey | it's been going > 10 minutes already | 02:05 |
| dobey | ah, just finished | 02:07 |
| dobey | and yeah, it's 898M | 02:07 |
| dobey | heh | 02:13 |
| dobey | oh well, it's late | 02:13 |
| === dpm_ is now known as dpm | ||
| === matsubara_ is now known as matsubara | ||
| === yofel_ is now known as yofel | ||
| === BradCrittenden is now known as bac | ||
| smoser | cjwatson, above, how do i do that ? | 19:50 |
| smoser | how does that stuff normally get crated ? | 19:51 |
| dobey | smoser: precise-proposed bzr branch of package in precise? | 19:53 |
| dobey | smoser: dput the proposed package to precise-proposed and it should get imported | 19:54 |
| smoser | dobey, well, well, | 19:55 |
| smoser | a.) i hope that works. i have very little success with the importer | 19:55 |
| smoser | b.) that looses interim commits that i wanted to preserve | 19:55 |
| smoser | s/well, well,/well.../ | 19:55 |
| smoser | oh. | 19:56 |
| smoser | c.) when does that occur ? on acceptance into -proposed ? (i've always been confused on that) | 19:56 |
| dobey | yes | 19:57 |
| dobey | it should occur when the package is accepted into proposed | 19:57 |
| dobey | though i'm not entirely sure what the expected interaction of imports is for Vcs-Bzr branches. that's always been a bit confusing | 19:59 |
| === _Hassen_ is now known as Hassen | ||
| philsf | how can I automatically close LP bugs from commits? bzr --fixes lp:number only links the branch, doesn't set "fix commited" neither "fix released" | 22:42 |
| dobey | commits to what? | 22:44 |
| dobey | anyone can bzr commit --fixes lp:number in any branch; doesn't mean it fixes it in the thing it was reported in | 22:44 |
| philsf | dobey, how can I close the bug then? I mean, appart from going to the bug itself and manually setting it to fixed. | 22:46 |
| dobey | philsf: are you using merge proposals as a way of getting changes into your trunk? | 22:48 |
| philsf | dobey, nope, just merging locally. is that what it's required? | 22:51 |
| === cinerama_ is now known as cinerama | ||
| dobey | it is required to use tarmac, which handles merging of branches, and has a plug-in to close bugs as fixed once the code is merged to trunk | 22:53 |
| dobey | maybe you should just write a script to close the bugs from the command line, using the launchpad api | 22:59 |
| philsf | https://launchpad.net/bzr-tarmacland ? | 23:07 |
| philsf | I can't find a package, with apt-cache search | 23:07 |
| philsf | my google-fu is failing me: I also can't find documentation on how to use it | 23:10 |
| dobey | lp:tarmac is tarmac | 23:30 |
| dobey | it's not packaged in ubuntu yet | 23:30 |
| dobey | i don't know what bzr-tarmacland is | 23:30 |
| dobey | it seems to be a plug-in useful for developers of launchpad itself | 23:31 |
| dobey | not generally useful to other people | 23:32 |
| philsf | oh, ok | 23:44 |
| philsf | dobey, what about "fix commited" -> "fix released"? I often see automatic LP comments in ubuntu bug reports, that a bug was fixed in a given release. How can I do that? | 23:46 |
| dobey | that is only in the packages in ubuntu | 23:47 |
| philsf | dobey, is it sufficient to include a "Closes: LP:number" in the pacakge changelog? | 23:47 |
| dobey | you need to do it manually for upstream releases | 23:47 |
| philsf | oh, that's a pitty. thanks for the info, anyway | 23:48 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!