[00:15] <danilos> henninge, tomorrow at 9am, ack if you read this
[00:15] <henninge> danilos: ack ;)
[00:17] <danilos> henninge, thanks
[00:38] <cjwatson> mwhudson: any news on the openssh import ticket?
[00:39] <mwhudson> cjwatson: :(
[00:56] <mwhudson> cjwatson: so keep an eye on https://code.staging.launchpad.net/~vcs-imports/openssh/main ?
[00:58] <cjwatson> mwhudson: ok
[00:58]  * mwhudson lunches
[00:58] <mwhudson> about two hours later than i wanted to oh well
[00:59] <mwhudson> cjwatson: the patches will stay there for about 24 hours, so hopefully a failure can be triggered before then
[02:40] <mwhudson> cjohnston: i see the openssh import failed, did it help you at all?
[02:42] <spm> mwhudson: cjwatson perhaps?
[02:43] <mwhudson> spm: bah, yes
[02:43] <mwhudson> cjwatson: i posted a link to the question
[04:31] <quotemstr> Say I want to host a feature branch of emacs on launchpad. Can I just create ~/+junk/emacs-foo and bzr push my branch there?
[04:32] <lifeless> well, ~quotemstr/+junk/emacs-foo, yes
[04:32] <lifeless> but better to push to
[04:32] <lifeless> ~quotemstr/emacs/foo
[04:32] <quotemstr> Doesn't that copy the *whole* repository? Isn't that a little wasteful?
[04:33] <lifeless> no, and no
[04:33] <lifeless> pushing to +junk would copy the whole repository, and be a little wasteful
[04:33] <quotemstr> Ah -- what's special about +junk? Also, does it matter that my branch's parent is a local checkout of the Savannah emacs bzr trunk and *not* lp:emacs?
[04:34] <lifeless> nothing special about +junk in this context, just that +junk != emacs
[04:34] <quotemstr> Oh, so it's not that +junk is magical, but that ~quotemstr/emacs is?
[04:35] <lifeless> ~user/project/branch - the project dir has a control file that tells bzr to use lp:project for common history
[04:35] <quotemstr> Ahhh, I see.
[04:35] <lifeless> lp:emacs is savannah emacs bzr trunk
[04:35] <quotemstr> lifeless: I noticed. :-) But will bzr share history even though my branch is derived from Savannah instead of lp:emacs?
[04:35] <lifeless> yes
[04:36] <lifeless> because they are the same thing
[04:50] <quotemstr> Thanks. :-)
[04:57] <zooko> Hey folks I hit a bug in launchpad so I tried to use launchpad to report a bug in launchpad, but that same bug prevents me from opening the new ticket.
[04:57] <zooko> I'm guessing this channel is a reasonable backup method of letting you know.
[04:58] <wgrant> zooko: What's the issue?
[05:01] <zooko> http://codepad.org/NXWcQMNc
[05:01] <zooko> wgrant: --^
[05:01] <zooko> Hm, I wonder how that weird URL got in gthere.
[05:02] <zooko> Corrected my but report.
[05:02] <zooko> I mean my bug report.
[05:02] <spiv> zooko: that's possibly because your browser isn't sending a Referer header
[05:02] <wgrant> Very probably.
[05:03] <wgrant> The error message sucks at the moment, but that's the most common cause.
[05:06] <zooko> Ah. Yes I think I've disabled Referer on my browser for security reasons.
[05:06] <zooko> Thinking back, I can't recall any other breakage since then.
[05:07] <zooko> I wonder if I can tell my firefox to send Referer headers only to launchpad.net...
[05:07] <zooko> Thanks folks.
[07:30] <glen> i was thinking maybe you can tell me why the import hasn't been done yet: https://code.launchpad.net/~glen666/smarty-gettext/trunk
[08:25] <knielsen> Hi, I need help with maria-developers@lists.launchpad.net . I have the problem that some emails to the list got silently dropped
[08:25] <knielsen> (This is the main MariaDB development list, so silent drop of messages is really bad for us)
[08:25] <knielsen> I have the original message which got lost, don't know if there is anything else I can provide?
[08:29] <knielsen> https://knielsen-hq.org/maria/launchpad-email.txt
[08:30] <knielsen> this email was silently dropped, no request for moderation. Once the user added his email address in the launcpad account, a re-send was help for moderation (and subsequent messages went through without moderation)
[08:30] <knielsen> this seems wrong, we should have gotten a moderation message for the first message (when the correct email was not registrered), not a silent drop
[08:38] <buxy> wgrant: did you poke people about the support of new source formats?
[08:42] <buxy> and can you enable it for jaunty PPA too?
[08:44] <wgrant> buxy: It's been enabled in Karmic since yesterday.
[08:44] <buxy> cool :)
[08:45] <buxy> jaunty almost has the final version that went in lenny r0, I think is should be fine there too
[08:45] <buxy> s/is/it/
[08:46] <wgrant> buxy: Hmm, I guess.
[08:48] <buxy> (someone asked on debian-devel)
[08:49] <wgrant> Jaunty dies in a few months and we haven't tested is support, so it's less compelling. But it's trivial to enable and again will just result in build failures... so... hmm.
[08:49] <wgrant> s/is/its/
[08:51] <StevenK> buxy: And they didn't get killed for daring to mention Launchpad or PPAs?
[08:51] <buxy> StevenK: not yet (I did mention it first, but people are trying to kill me for other reasons)
[08:51] <wgrant> StevenK: Didn't you know we're all meant to use dak?
[08:51] <StevenK> wgrant: Oh. clearly
[09:05] <wgrant> buxy: Ah, so it was in *that* thread. I wasn't quite up to date there.
[09:06] <wgrant> bigjools: Morning.
[09:07] <wgrant> buxy says that Jaunty's dpkg isn't too bad either.
[09:07] <bigjools> moin
[09:44] <dspstv_> morgen
[09:45] <dspstv_> is theres a way to know the build times on the servers for today? i mean, i submitted a package 11hours ago and it still is in the queue
[09:46] <dspstv_> since this is my fisrt ever package i was wondering is those long waits are normal?
[09:49] <geser> dspstv_: see https://edge.launchpad.net/builders/, as several PPA buildds are being used for other tasks, it takes currently a little bit longer than usual
[09:50] <wgrant> dspstv_: Most of the build machines are currently testing the upcoming Ubuntu 10.04, so queues are much, much longer than normal. Normally things start building instantly, or within a few minutes.
[09:53] <dspstv_> https://help.launchpad.net/Packaging/BuildScores
[09:53] <dspstv_> thanks geser, wgrant
[11:51] <getxsick> in my debian/control file all packages have 'i386' or 'all' architecture, however PPA tries to build for amd64 and lpia. how to avoid it?
[15:39] <zookow> Dear people of #launchpad: I just get this pop-up dialog from http://launchpad.net: Error
[15:39] <zookow> The following errors were encountered:
[15:39] <zookow>  
[15:39] <zookow>     * Server error, please contact an administrator.
[16:01] <zookow> okay I opened a ticket about this. Thanks!
[16:50] <mtaylor> launchpad should have a javascript implementation of emacs that will allow people to make a branch, edit it, commit, and submit for merge all within their web browser
[17:05] <cjwatson> LOSA: is it possible to cause another import attempt to run on https://code.staging.launchpad.net/~vcs-imports/openssh/main on strawberry (which I think is the one that had a patch cowboyed onto it)?
[17:09] <chex> cjwatson: err, strawberry is (not/no longer one) of the importd's..
[17:10] <cjwatson> huh, it was last night
[17:10] <cjwatson> this is with regard to https://answers.edge.launchpad.net/launchpad-code/+question/105130
[17:47] <KdaG> my build process got stuck since few hours now:
[17:47] <KdaG> https://launchpad.net/~alejoduque/+archive/ppa-alejo/+build/1581509
[17:48] <KdaG> almost 19 hours for a very small package,,, wonder if i did something worng..
[17:48] <KdaG> wrong
[17:49] <bigjools> KdaG: it's only been building for 4 hours
[17:49] <bigjools> how long does it usually take?
[17:50] <KdaG> bigjools: that takes a minute on my local machine
[17:51] <KdaG> bigjools: its been stuck on the same point for 3 hours now
[17:51] <bigjools> ok I'll take a look
[17:51] <KdaG> thanks
[17:51] <KdaG> i386 built just fine
[17:54] <bigjools> KdaG: I've killed the old build, it'll restart in a moment on a new builder
[17:54] <KdaG> bigjools: tx
[17:54] <bigjools> happens sometimes, dunno why :/
[17:55] <KdaG> yes, well since is my first pakage i feel guilty inmedately
[17:55] <KdaG> :)
[17:57] <bigjools> how are you finding things?
[17:58] <KdaG> well, yesterday it took me a good deal to find out that debuild was not able to overwrite the files
[17:59] <KdaG> it was reporting success
[17:59] <KdaG> but dput was failing cause of a problem with the signature on debian/changelog
[18:00] <KdaG> now, it seems the servers are to tired with 10.4 so 19hours to see the packages on the PPA is a bit of a wait
[18:10] <KdaG> bigjools: thanks see
[18:10] <KdaG> amd64 build of din 1.0.5.2-0ubuntu0~alejoduque2 in ubuntu karmic RELEASE
[18:10] <KdaG> Build started 4 minutes ago on dubnium (virtual) and finished 1 minute ago taking three minutes
[18:10] <KdaG> ooh he quit
[18:38] <getxsick> in my debian/control file all packages have 'i386' or 'all'  architecture, however PPA tries to build for amd64 and lpia. how to  avoid it?
[18:52] <davidstrauss> Can I rename the URL for a project?
[19:36] <aapo> Hi, I just made my first PPA package for karmic. How I made same time for another releases too?
[19:37] <dspstv_> aapo: hi, i also finished one few hours ago
[19:38] <dspstv_> aapo: cant really understand your question
[19:39] <geser> aapo: you need to modify the version slightly (e.g. by appending ~jaunty or similar), update the distribution in debian/changelog and reupload
[19:40] <aapo> geser, ok. So there are no way to put hardy karmic lucid in same row on debian/changelog
[19:42] <geser> no
[19:43] <geser> as all build debs get stored in the same directory and the filename contains the version, but your upload with the same version to different releases will most likely produce different debs (e.g. linked against different library versions), this won't work
[19:44] <aapo> geser, ok. this is good reason why it doesn't work
[19:46] <aapo> Is there ready made script to handle this upstream code changing -> four different changelog/uploads
[19:47] <aapo> Or is somebody planning to change way how builder works? Maybe it could store files for different releases in own subdirectories?
[19:50] <geser> I don't know of any script for this
[19:50] <gnomefreak> was the "not sure what it is called" when you get upstream comments on Lp bugs turned off? or broken?
[19:50] <gnomefreak> nevermind
[19:52] <getxsick> geser: what about 'copy packages'?
[19:52] <getxsick> isn't a way to do it?
[19:54] <geser> you can only copy your own packages with source+binaries to a different release -> no rebuilds are done
[19:55] <getxsick> geser: right...i do only python packages, so mostly this is not a problem
[19:55] <geser> yes, for python packages this is an option
[19:56] <getxsick> however, i still have a problem with other architectures than i386, one of the package only supports i386..i set it in debian/control but PPA still tries to build for amd64 and lpia
[19:59] <geser> getxsick: what's the package and your PPA?
[19:59] <getxsick> geser: https://launchpad.net/~pypy/+archive/ppa
[20:05] <geser> getxsick: your debian/rules correctly only mentions i386 and all, yet the .dsc file contains "any" (which explains the build). But I don't know how the architecture field for the .dsc file is computed.
[20:06] <getxsick> geser: any idea where to investigate?
[20:06] <getxsick> geser: i run `debuild -S -sa` to build it
[20:07] <geser> which is correct, you might need to look at the source of dpkg-source
[20:28] <geser> lamont: it looks like the armel buildd "gourd" got hit by bug #1583047. The recent builds on this buildd for lucid failed with "dpkg-deb: control directory has bad permissions 700 (must be >=0755 and <=0775)"
[20:28] <lamont> geser: gar
[20:29] <geser> I mean bug #517802
[20:29] <lamont> geser: so, it's got the change in init.d to launch with 022
[20:30] <lamont> restarted the buildd, will retry the failed builds just to see
[20:38] <lamont> geser: not 700 now
[20:38] <geser> thanks
[20:39] <lamont> thank you.  brand new buildd and more reason for me to roll out a new launchpad-buildd package
[20:57] <aapo> I made initial script for modifying_changelog+debuild+dput for each release. At this moment all actual doing is only echo. Anybody interested in review it: http://cc.oulu.fi/~rantalai/for_ppa.txt ?
[20:58] <aapo> I know this has limited use, because releases have different libraries for dependencies and so on. But I think somebody else might use it too.
[21:06] <getxsick> depends from packages are not installed by buildbot right? only build-depends? i'm asking cause i would like to run testsuit and wondering if i should add some depends from packages straight to build-depends...
[21:07] <geser> right, only build-depends are installed
[21:32] <sirver_> Hi
[21:32] <sirver_> is there another way to upload files to launchpad than via web or ftp polling?
[21:32] <sirver_> web times persistently out for me (widelands packages are big...)
[21:33] <sirver_> and ftp polling can't be used because our versioning scheme is different then needed
[21:43] <aapo> sirver_, what you mean 'different than needed'? Can you use Build 15 rc 2 -> widelands_build15_rc2 ?
[21:45] <aapo> sirver, and I think widelands_bzr5123 is acceptable too
[21:49] <sirver_> aapo: I thought the versions would need to be 0.8.1 or therelike
[21:51] <aapo> I have only put 0.0.20100325-5~hardy to PPA, but with debuild -S -sa I can make build15_rc2 and bzr512 (just tested them)
[21:51] <sirver_> aapo: okay, thanks. So i'll try that ;)
[22:19] <aapo> Script for automating pushing sources for many releases: http://cc.oulu.fi/~rantalai/for_ppa.txt  It only needs your name and address of ppa.
[22:46] <snake007v> Prompt please, how to remove lauchpad project(ppa)?
[22:49] <wgrant> snake007v: A project, or a PPA? They are distinct entities.
[22:50] <snake007v> wgrant: project
[22:51] <wgrant> snake007v: Ask at https://answers.launchpad.net/launchpad/+addquestion, and an admin can do it for you.
[22:51] <snake007v> wgrant: thx