2008/05/26/#launchpad.txt

=== asac_ is now known as asac
=== asac_ is now known as asac
[04:48] <jamesh> is the branch scanner stuck?
[04:48] <jamesh> or just busy
[04:49] <mwh> jamesh: stuck :/
=== ^Gonzo^ is now known as [PUPPETS]Gonzo
[07:55] <emgent> SteveA, kiko_ : I think that there is a problem with auto mail alias (ubuntu.com) activation. I'm in ubuntumembers launchpad team and alias is not active. Sebner was wait 14 day and dont work too. Some idea?
[07:55] <emgent> stub: and you? :)
[07:57] <Hobbsee> sabdfl: er, how does one access a backport ppa.  Last i knew, that didn't exist.
[07:57] <sabdfl> every ppa is a backport ppa ;-)
[07:58] <sabdfl> emgent: that's something elmo handles
[07:59] <Hobbsee> sabdfl: okay, so "The Official Backports" as a ppa...
[08:01] <emgent> oh ok thanks sabdfl 
[08:01] <sabdfl> Hobbsee: why not?
[08:02] <Hobbsee> sabdfl: no, this is not a question of why.  this is a question of 'where is it, and how is it accessed from ppa'?
[08:03] <sabdfl> Hobbsee: i don't know how they set it up. it was done before they had ppa's so it's probably not configured as a ppa
[08:03] <Hobbsee> sabdfl: i'ts a component of the regular archive.
[08:03] <Hobbsee> sabdfl: so i'm somewhat confused as to your response about how to build against -backports
[08:04] <Hobbsee> (is there a way that most people don't know about?  As far as i know, the answer to building against backports is that it's not possible, without rebuilding all the packages that you want from -backports in your ppa)
[08:05] <sabdfl> offs
[08:05] <sabdfl> there is a standard way to specify dependencies
[08:05] <sabdfl> you should ask the soyuz team to make it possible to specify backports
[08:05] <sabdfl> nicely
[08:07]  * Hobbsee did not intend to piss you off - only to ask for a clarification on your answer
[08:10] <Hobbsee> sabdfl: i asked about the case now, to check that the generally given answer was correct, seeing as your answer had been contrary to it.  i did not make suggestions about how it should be fixed in future.  I'm unsure why you should be annoyed with me as a result.
[08:12] <Hobbsee> morning cprov 
[08:12] <cprov> Hobbsee: good morning.
[08:28] <stub> emgent: I think you need to email rt@admin.canonical.com still to get that looked at. 
[08:40] <sabdfl> cprov: Hobbsee had a question i could not answer, about specifying backports as a dependency for a PPA
[08:41] <sabdfl> stub: did you see that db patch?
[08:43] <cprov> sabdfl: I see 
[08:44] <cprov> Hobbsee: how do you see it working ? 
[08:46] <cprov> Hobbsee: please correct me if I'm wrong, but ubuntu itself never build packages using -backports, unless they are in -backports, right ?
[08:46] <Hobbsee> cprov: correct.
[08:47] <cprov> Hobbsee: so, if we allow you to say, this PPA should use -backports to build packages it surely compromise the ordinary packages you normally build
[08:47] <Hobbsee> cprov: i presume that for ppa, you'd want to allow an option for people to build against !release pockets - which you should be doing anyway.
[08:47] <Hobbsee> cprov: w.r.t packages that get put in -updates
[08:48] <cprov> Hobbsee: it already use -updates + -security (as you can see in the build logs)
[08:48] <Hobbsee> oh, so it does.
[08:49] <Hobbsee> cprov: add an option that says "build against backports" or something, and add that line into the sbuild repositories, update, and build the package?
[08:49] <cprov> Hobbsee: yes, the infrastructure would support it fine, but PPA-wide
[08:50] <Hobbsee> cprov: you can't specify per ppa?
[08:50] <Hobbsee> cprov: have a backports-enabled tarball, and a non-backports-enabled tarball, perhaps.
[08:50] <cprov> Hobbsee: are you sure people would like to build every package using  backported build-deps ?
[08:50] <Hobbsee> this is a good question.
[08:51] <cprov> Hobbsee: yes, I am afraid it's a per-package, not a per-PPA decision.
[08:51] <Hobbsee> i'd think for the most part, yes they would.  if they specifically didn't, then they could just not enable backports in their ppa, and rebuild packages that are in backports that they wanted to use
[08:52] <cprov> Hobbsee: yes, as they can do for other archive-dependencies, currently.
[08:52] <Hobbsee> yes, of course.
[08:52] <Hobbsee> hmm
[08:52] <cprov> Hobbsee: that's my plan for the future, make PRIMARY archive dependencies explicit
[08:53]  * Hobbsee desoyuzifies
[08:53] <Hobbsee> er, what?
[08:54] <Hobbsee> you want to make the standard ubuntu archive dependancies explicit....how is that different from what you do now?
[08:54] <cprov> Hobbsee: so a PPA-owner would be able to specify something else then 'user PRIMARY release + updates + security'
[08:54] <cprov> Hobbsee: well, now there is not choice, PPA packages always depend on those pockets (and only those)
[08:55] <cprov> s/is not/is no/
[08:55] <Hobbsee> right, yes, i see.
[08:55] <Hobbsee> which then presumably generalises to building for debian...
[08:55] <cprov> Hobbsee: wow, hold on ;) that's a looooong path.
[08:56] <Hobbsee> well, yes, i know.
[08:56] <cprov> Hobbsee: but yes, debian PPAs are in our plans. Have you followed the conversations in UDS ?
[08:56] <Hobbsee> but as in, the infrastructure will therefore be there that you can build for any debian or debian-based distro
[08:57] <Hobbsee> cprov: no, how could i have?
[08:57] <cprov> Hobbsee: irc, I presume
[08:57]  * Hobbsee was not aware of any icecasts.
[08:57] <Hobbsee> oh, i didn't see a launchpad specific one.
[08:57] <cprov> anyway, there will be news in this area soon.
[08:58] <Hobbsee> nice
[08:58] <Hobbsee> so, in the case of the future plan, that's also per-ppa, not per-package?
[08:58] <Hobbsee> oh.
[08:58] <Hobbsee> duh.
[08:58] <Hobbsee> cprov: why not change the upload target field, depending on whether they want to allow backports or not, per package?
[08:59] <cprov> Hobbsee: so, summing up, do you think there will be valid use-cases for using generalised PRIMARY archive dependencies, right ?
[08:59] <Hobbsee> that already ahppens for different ubuntu releasese.
[08:59] <cprov> Hobbsee: well, that's pretty much like 'enabling pockets in PPAs'
[08:59]  * Hobbsee desoyuzifies again.
[08:59] <Hobbsee> well, yeah.
[08:59] <Hobbsee> er, yes, i think there would be valid use cases for it
[09:03] <cprov> Hobbsee: nice, probably there is use cases for both. Let's see what we can do post-2.0. Can you file a bug, please ?
[09:04] <soren> Hobbsee: There were icecasts from every room at UDS.
[09:04] <jamesh> the use cases for depending on backports seem to be the same use cases for depending on other PPAs
[09:04] <jamesh> (unless I'm missing something)
[09:04] <soren> Hobbsee: Actually, both icecast and VoIP.
[09:04] <Hobbsee> soren: i wasn't aware that included launchpad rooms.  do you know where the launchpad ones were publicised?  i didn't see them on scott's uds schedule
[09:05] <Hobbsee> jamesh: yeah, i think so
[09:05] <soren> Hobbsee: Oh.. I'm not sure about those.
[09:05] <soren> Hobbsee: I thought you weren't aware of the general availability of icecast/voip streams.
[09:06] <jamesh> most of the LP hacking at the sprint was in the lounge area
[09:06] <jamesh> rather than explicit sessions
[09:06] <Hobbsee> soren: nah :)
[09:07] <Hobbsee> soren: i was on some of the icecasts, and the voip wasn't behaving for me.   besides, i hate talking on those things anyway, due to the high pitched voice (in comparison)
[09:07] <jamesh> (some of us were involved in relevant UDS sessions though)
[09:07] <soren> Hobbsee: Yeah. Phones suck.
[09:07] <jamesh> Hobbsee: clearly we need vocoder support integrated into Ubuntu's VoIP software
[09:08] <Hobbsee> jamesh: :D
[09:20] <jaromil> to compile for multiple series on the PPA, can i specify a comma separated list of ubuntu releases in the debian/changelog?
[09:22] <jamesh> jaromil: nope.
[09:22] <jamesh> you'll need to submit multiple builds
[09:23] <jamesh> (preferably with version numbers that'll trigger an upgrade when upgrading OS versions)
[09:33] <jaromil> jamesh: is it recommendable that i use the same version number or different version numbers for different series?
[09:34] <jaromil> or something like 0.10-hardy 0.10-feisty and so on
[09:34] <jamesh> jaromil: for the releases in my PPA, I've used the Ubuntu version number as part of the release
[09:34] <jamesh> see https://edge.launchpad.net/~jamesh/+archive
[09:35] <jamesh> I used the numeric version number rather than code name
[09:35] <jaromil> i see. the ~ is sexy :)
[09:35] <jaromil> thanks for the suggestion
[09:36] <jamesh> while they have been lexically sorted since breezy, it probably won't always be
[09:36] <jamesh> (what happens after Z?)
[09:37] <jaromil> so then the debian/changelog will have multiple entries for multiple series, where i must update the latest between every build
[09:38] <jaromil> or can i change the entry directly somewhere outside the debian/build of source package?
[09:39] <jaromil> i guess it will be a slow process to compile the same package on more series... but ok then, seems worth :)
[10:04] <jamesh> jaromil: I'm not sure of what the best practice is.  I just changed the version number + release codename in the changelog and generated a second upload
[10:42] <jaromil> jamesh: i just found out that the best way to have the same source packaged for different series seems to be copying packages in your PPA
[10:44] <cprov> jaromil: you mean, same sources and binaries, right ? because you can't rebuild sources within the same archive.
[10:44] <jamesh> jaromil: as mentioned above, that is problematic when doing distro upgrades
[10:45] <jamesh> jaromil: e.g. your package might depend on different shared library versions when built against gutsy and hardy
[10:45] <jamesh> jaromil: if you publish binaries with the same version number for each release and the user upgrades from gutsy to hardy, then the user won't be prompted to upgrade your package
[10:45] <jaromil> cprov: ack. i wanted to rebuild already uploaded sources in my PPA for multiple series
[10:45] <jamesh> since they already have the latest version
[10:45] <jaromil> i see
[10:46] <jaromil> yea, i just noticed for instance gutsy hasn't libfftw3 while hardy has
[10:47] <jaromil> can i handle such dependencies making them "recommended" other than required - so that the build doesn't stops? i contemplate the case fftw3 is not present in the configure script, should be no problem
[10:47] <cprov> jaromil: you only need to rebuild a source in another suite when it depends on new features, in this case the solution is indeed to upload a new source and ideally with a higher version, so upgrades will work as expected. 
[10:48] <jaromil> ok. so i'll keep on doing that
[10:48] <cprov> jaromil: when you depend on constant features across different suites it's okay to copy source & binaries built in the oldest suite.
[10:49] <jamesh> when in doubt, it is probably better to do separate packages
[10:49] <cprov> jamesh: agreed.
[10:50]  * jaromil getting a clearer picture
[10:50] <jaromil> any comment about "recommending" dependencies? something i'm missing in the control file?
[10:51] <jaromil> debian policy manual lists only build-depend(-indep)
[10:52]  * jaromil feels like an olive in a plate of 'spaghetti a la debian'
[11:27] <lightyear> good morning
[11:27] <lightyear> is there an easy way to reassign all the bugs of a certain person to another person?
=== Ng_ is now known as Ng
=== stgraber1 is now known as stgraber
[12:53] <aantn> Hello
[12:54] <aantn> I've noticed that launchpad hasn't been sending out commit emails and updating the code pages with the latest revisions
[12:54] <aantn> I assume that the issue is already known, but I wanted to make sure
[13:28] <jprieur> hey guys
[13:28] <jprieur> when do you think lp's behavior will be back to normal?
[13:29] <beuno> jprieur, what specifically?
[13:30] <jprieur> beuno, all the web visualization stuff for branches are out of sync.
[13:31] <jprieur> code browsing is OK but the listing of branches and the online log per branches is out of sync.
[13:31] <beuno> jprieur, ah, right. Well, I don't know any specifics, just that it's stuck in a "very big branch", and it should unblock soon
[13:31] <beuno> jml, any ideas con specific?
[13:32] <jprieur> beuno, it's like that since yesterday
[13:32] <jprieur> more than a day, I'd say
[13:32] <beuno> jprieur, my last branch was scanned ~13 hours ago
[13:32] <beuno> and LP admins already know about it, so it shouldn't be long
[13:33] <jprieur> https://code.launchpad.net/~people-project/people-project/people-trunk shows revision 266 and the branch is actually at revision 285
[13:33] <jprieur> well, ok, thanks for the answer :)
[13:34] <beuno> sorry I couldn't do better  :)
[13:34] <beuno> I'd expect it to be fixed in the following hours, but it's just a hunch
=== fdd-0 is now known as fdd
=== kiko_ is now known as kiko
[15:06] <KleinerPinguin> hi
[15:11] <afflux> morning
[15:12] <afflux> LP currently sorts the releases of my project in a wrong order: Releases: 0.7.2, 0.7.2.1, 0.7.1, 0.6, 0.7, 0.5, 0.3, 0.2, 0.1  
[15:12] <afflux> esp. note that 0.7.2.1 is not the latest
[15:12] <afflux> should I open a bugreport for that?
[15:17] <beuno> afflux, there should be a bug open for that already
[15:17] <afflux> beuno: can you point me to it?
[15:18] <beuno> afflux, #73094
[15:19] <afflux> thanks
[15:19] <beuno> np
[15:19] <KleinerPinguin> Hi.Im a newcomer to launchpad and tried to get started by contributing to the translation of miro-guide. Im looking for a hint  for a work flow. To me it seems the only way translation is done in launchpad is the Web. Am I right ?
[15:19] <kiko> KleinerPinguin, well, you can also translate offline and upload the translation files.
[15:20] <KleinerPinguin> kiko, yes. i thought there would be a better way 
[15:20] <philn> i closed a lp bug using bzr commit, but when i pushed my branch, the state of the bug wasn't changed... is that normal?
[15:22] <kiko> philn, hmmm, not really -- abentley do you know how the branch scanner checks metadata there?
[15:22] <philn> no clue, but i know it worked at least once
[15:22] <KleinerPinguin> kiko, i thought it would be possible to just open a branch from miroguide and would be ready to go. but no luck there
[15:23] <kiko> KleinerPinguin, yeah, not yet! we'll be working on this after july :)
[15:23] <abentley> kiko: The branch scanner is currently tied up dealing with these large branches.
[15:24] <abentley> So whatever it normally does won't be happening.
[15:24] <beuno> and, afaik, you can only close bugs with changelogs, not commits
[15:25] <philn> beuno: bzr --fixes lp:1234
[15:25] <philn> +ci
[15:26] <philn> where is the syntax to close bugs from changelog explained?
[15:26] <beuno> hrm, I wonder what that does...
[15:26] <beuno> philn, I don't know, but it's only for uploading packaged to main or universe
[15:26] <beuno> s/packaged/packages
[15:27] <KleinerPinguin> kiko, after all its just one file with 120 strings....maybe im im just procastinating :- ) 
[15:27] <philn> i see... well i want an automatized way to track bugfixes and eventually revisions... and it seems to be lacking in LP
[15:27] <kiko> philn, as far as I know we do handle commits -- but as abentley said the branch scanner seems tied up
[15:28] <philn> for a given bug i want to know when and by whom it was fixed, e.g: a link between the bug and the commit
[15:28] <philn> ok...
[15:29] <abentley> philn: The changelog bug handling is only done for package uploads, not for branches.
[15:29] <philn> is it planned to fix that? it's quite annoying IMO :(
[15:30] <kiko> abentley, hang on -- we do support --fixes, though, right?
[15:30] <kiko> abentley, I mean, we don't scan changelogs, but we do scan metadata
[15:30] <abentley> kiko: That's my understanding.
[15:30] <kiko> so what philn is doing should worn
[15:30] <kiko> work too :)
[15:30] <abentley> will work, too, once his branch is scanned.
[15:30] <philn> well i remember it worked at least once for me
[15:31] <kiko> philn, as abentley and I said before, it will work -- it's just that the scanner process is a bit busy right now.
[15:31] <KleinerPinguin> kiko, sorry to bug you again. Do you have a pointer where to track that spefic feature. I assume its somewhere in blueprints but i cant think of a search query right now
[15:31] <philn> ok so it's just a question of time 
[15:31] <philn> good then
[15:31] <kiko> (and will need to be optimized, it appears! guess we don't have enough big branches to try it yet :)
[15:31] <kiko> KleinerPinguin, best person to ask is jt1, who runs the translations project
[15:32] <abentley> philn: No, we don't have a plan to support scanning changelogs for branches.  It's a wishlist bug at the moment.
[15:32] <kiko> abentley, did philn mention changelogs anywhere?
[15:32] <kiko> ah
[15:32] <kiko> close bugs from changelogs
[15:32] <kiko> philn, that feature is for package upload changelogs :)
[15:33] <philn> i understood that
[15:33] <philn> but i used to like that feature in Trac
[15:33] <kiko> philn, why not use --fixes, which is much more explicit?
[15:33] <abentley> trac uses the commit messages.  I wasn't aware it also used changelogs.
[15:34] <philn> i find --fixes easy to forget.. i guess i need to get used to it
[15:34] <philn> abentley: oops, yes you're right
[15:36] <philn> so i do bzr uncommit and commit again when i forget --fixes... anyway, nevermind
[15:39] <cperrin88> Hi, I'm trying to put my software into my PPA. Is there a delay in this process or did I do something wrong?
[15:52] <kiko> cperrin88, if you did something wrong in packaging, you'll get emailed, as long as you signed the package right 
[15:52] <kiko> cperrin88, there is a delay in building, but upload processing is pretty quick 
[15:52] <cperrin88> Thakns
[15:53] <cperrin88> about 10 seconds before your answeer i got an e-mail :D
[15:54] <Hobbsee> does this include intrepid now?
[15:58] <cperrin88> who did you ask?
[15:58] <Hobbsee> kiko
[16:01] <emgent> uhm
[16:01] <kiko> Hobbsee, not sure if the chroots are set up -- right people to ask would be infinity or elmo 
[16:01] <emgent> why launchpad PPA dont show building status?
[16:02] <cprov> emgent: it does. Which page are you viewing ?
[16:03] <emgent> pmb
[16:06] <cperrin88> doesn't the server delete file when the build didn't work?
[16:07] <cperrin88> *the files
[16:07] <emgent> no
[16:07] <cperrin88> can I delete them?
[16:08] <emgent> sure
[16:08] <cperrin88> how?
[16:11] <emgent> cperrin88: https://edge.launchpad.net/~user/+archive/+delete-packages
[16:11] <kiko> there's a delete packages link on your PPA page
[16:11] <cperrin88> This PPA does not contain any source packages published.
[16:14] <cprov> cperrin88: you have never uploaded any sources to https://edge.launchpad.net/~cperrin88/+archive, that's why. Or do you mean another PPA ?
[16:15] <cperrin88> i did uplaod sources but they were rejected
[16:15] <kiko> cperrin88, so there was no build either
[16:15] <cperrin88> right
[16:16] <cperrin88> but dput tells me that the file is already there
[16:16] <kiko> cperrin88, if you do succeed in uploading and the build fails, you'll be able to delete packages (sometimes -- read the help text :)
[16:16] <kiko> cperrin88, that's not possible -- we don't reuse ftp directories
[16:16] <Hobbsee> cperrin88: use dput -f
[16:16] <cperrin88> ah
[16:16] <cperrin88> okay
[16:16] <Hobbsee> kiko: it's whinging about the fact that it's already been uploaded somewhere, from that system.
[16:17] <Hobbsee> kiko: it's a local error.
[16:17] <kiko> interesting -- yeah, dput has no way of knowing if it failed!
[16:17] <Hobbsee> cperrin88: or remove the .upload file
[16:17] <cperrin88> okay :)
[16:17] <cperrin88> thanks
[16:18] <cperrin88> in which file do I have to set the distribution before using debuild .... just in th changelog file?
[16:19] <Hobbsee> yes
[16:25] <emgent> cprov: news about building status?
[16:27] <cprov> emgent: no, you haven't pointed me to the page that makes you think that there is no build-status, have you ? ;)
[16:28] <Hobbsee> emgent: if you're looking for a global build queue for ppa, there isn't one.
[16:31] <cperrin88> where can i find the right values for section in the control file
[16:33] <KaZeR> hello there
[16:33] <cperrin88> hi
[16:34] <KaZeR> what should i do to request the import of our project's svn?
[16:34] <KaZeR> simply ask the question in the question tracker?
[16:57] <cperrin88> the i386 builder seems to be quite busy ^^ 3 hours ... that's some time ^^
[16:58] <bobbo> cperrin88: heh, Ubuntu has almost 1200 builds queued for all builders :/
[16:58] <cperrin88> yeah
[16:59] <cperrin88> amd64 and lpia are on idle .... the problem is .. I don't have such a platform :D
[16:59] <geser> looks like the autosync was turned on
[17:02] <geser> looks like someone is building languagepacks, they need some time, so be patient
[17:02] <cperrin88> I have time
[17:05] <cperrin88> a lot of intrepid builds
[17:08] <cperrin88> what is the build score?
[17:12] <bobbo> is anyone else having problems with Launchpad not updating for new bzr revisions?
[17:12] <kiko> bobbo, yeah, the branch scanner is tied up apparently - some massive branches are in
[17:13] <bobbo> kiko: heh, thanks :)
[17:13] <Hobbsee> cperrin88: what's the location of your ppa, and which package?
[17:16] <cperrin88> http://ppa.launchpad.net/cperrin88/ubuntu/ , package bcv4 - 0.5.0-0ubuntu1~ppa1
[17:44] <cperrin88> I thought the service would build for all architectures ... but atm it's just qeued for i368 and is already built for amd64 and lpia ...
=== kiko is now known as kiko-fud
[17:45] <geser> PPA build only for i386, amd64 and lpia as only those arch are supported by Xen
[17:45] <kiko-fud> right -- it's a security issue, mainly, cperrin88 
[17:45] <cperrin88> ahh .. okay :)
[17:46] <cperrin88> I need i368 so ... i have to wait ^^
[17:47] <cperrin88> But there are builders for the other architectures but they are not virtualized?
[17:47] <geser> yes, but only for the "official" uploads to the Ubuntu archive
[17:48] <cperrin88> are there plans to virtualize them somhow, too?
[17:48] <geser> the i386 buildd is also responsible for building arch:all packages, so it has more to do then the other buildds
[17:49] <cperrin88> I can wait :)
[17:49] <cperrin88> I have to wait ^^
=== matsubara is now known as matsubara-lunch
[18:22] <cperrin88> the open suse build service was definately faster ....
[18:25] <jaromil> open suse build service?
[18:25] <cperrin88> Yeah
[18:25] <cperrin88> It can build even Ubunut packages
[18:25] <cperrin88> *Ubuntu
[18:26] <jaromil> wow. thanks for the tip. never knew about that.
[18:26] <jaromil> even doe, launchpad works OK.
[18:26] <cperrin88> Yeah
[18:26] <jaromil> i just finished automating all my scripts to upload new versions and such
[18:26] <jaromil> but well. i need more :)
[18:26] <cperrin88> Well
[18:26] <jaromil> sorry, gotta go, bbl()
[18:26] <cperrin88> bye
=== matsubara-lunch is now known as matsubara
=== kiko-fud is now known as kiko
[19:06] <cperrin88> is buidl score my current place in the qeue?
[19:06] <nosrednaekim> the PPA's are very very slow...
[19:06] <nosrednaekim> downloading from them that is
[19:19] <kiko> cperrin88, no, it's a score calculated on attributes of your package itself. it's used to calculate the position you should be in the queue, though there is an ETA you should be able to rely on for the build
[19:21]  * bobbo wishes there was a dedicated PPA builder
[19:21] <kiko> bobbo, there are dedicated PPA builders. what do you mean?
[19:22] <bobbo> kiko: so how are the auto-sync'd ubuntu packages slowing down the PPA builds?
[19:23] <kiko> bobbo, they aren't.
[19:23] <kiko> everything's running a bit slow today, though, it seems.
[19:23] <bobbo> kiko: ah ok, i though it was the Ubuntu packages slowing the PPA builds
=== fta_ is now known as fta
[19:24] <bobbo> thanks for clearing that up :)
[19:24] <kiko> sure thing :)
[19:25] <cperrin88> A list for the PPA builds would be great
[19:26] <kiko> it's being worked on (by al-maisan, btw)
[19:26] <cperrin88> that's good :)
[20:03] <cperrin88> wooohoo .. my package is building ^^
[20:04] <bobbo> cperrin88: mine just built :D properly happy
[20:08] <cperrin88> mine is done, too :)
[20:11] <asabil_> hi all
[20:11] <cperrin88> hi
[20:11] <asabil_> seems like LP branch scanning is completely broken these days
[20:11] <asabil_> is that a known issue ?
[20:11] <kiko> yeah, it's currently blocked on some gigantic branches apparently
[20:12] <kiko> abentley might know more
[20:12] <asabil_> :/
[20:13] <asabil_> I see
[20:13] <asabil_> thanks
[20:14] <cperrin88> it seems like LP needs more servers ....
[20:15] <abentley> kiko, asabil_: AFAIK the last thing that happened was a recommendation to increase the timeout.
[20:16] <asabil_> hmm ?
[20:16] <asabil_> timeout for what ?
[20:22] <abentley> asabil_: timeout for the script that scans the branches for new revisions.
[20:24] <asabil_> oh ok
[20:29] <\sh> now I know why you launchpadders don't opensource launchpad...you are not allowed to talk about it...because it's da "Phyt" club... as seen yesterday during a fair in karlsruhe ;) http://www.sourcecode.de/content/phyton-world ;)
[20:31] <kiko> heh
=== kiko is now known as kiko-afk
[21:10] <ahasenack> does launchpad have something like bugzilla's "saved searches"?
[21:11] <\sh> ahasenack, browser bookmarks 
[21:11] <ahasenack> ok, thanks
=== mwhudson is now known as mwh
=== mwhudson_ is now known as mwhudson