[08:08] <mrevell> Good morning
[09:00] <dpm> morning henninge. We need to schedule a full oneiric export so that we can build the langpacks in time for beta-1. There is an export already scheduled for today, but it is at 14:00UTC. Since full exports seem to take ~24h lately, I'd like to schedule the export earlier than that today. Could you help me or point me to someone who could?
[09:00] <dpm> Current schedule: https://dev.launchpad.net/Translations/LanguagePackSchedule
[09:02] <jincreator> dpm, do you know what happens to language-support-fonts-** packages at Oneiric?
[09:04] <dpm> jincreator, I know there were some changes there, but the best person to talk to is pitti on the #ubuntu-devel channel
[09:04] <jincreator> I see. Thank you!
[09:26] <henninge> dpm: sorry, missed your ping
[09:31] <dpm> henninge, no worries
[09:33] <henninge> dpm: maybe it would be safer to deactivated tomorrow's run for lucid?
[09:33] <henninge> dpm: Couldn't lucid do a week without an update?
[09:34] <henninge> or move lucid to saturday
[09:34] <dpm> henninge, yeah, we can do that. I'd still like to advance the oneiric one to earlier on today
[09:35] <henninge> dpm: can do taht since we'll be messing with the crontabs anyway.
[09:35] <henninge> dpm, so there was no run yesterday, so the field should be clear to start the run any time
[09:36] <henninge> dpm: is that okay or do we need to wait for anything before kicking it off?
[09:37] <dpm> henninge, sounds good. We can start the oneiric run already, if that's possible
[09:40] <henninge> dpm: it seems there was a full pack created in the last run?
[09:42] <dpm> henninge, the last one was this week and it was a delta one IIRC, but let me check...
[09:43] <henninge> dpm: they are scheduled for 22h UTC, btw.
[09:44] <henninge> dpm: so the last full run took about 16 hours.
[09:44] <dpm> henninge, ah, I see what happened: pitti requested the export already before Tuesday, but I thought it would be exported until Thursday (I mistakenly thought exports started at 14:00, not 22:00)
[09:45] <dpm> it would *not be exported, I meant
[09:45] <henninge> dpm: ok, so no need for action ;-)
[09:46] <al-maisan> hello there, is there a way to copy a package from the primary archive to a ppa?
[09:47] <bigjools> hey al-maisan
[09:47] <bigjools> yes, use the syncSource() call on the API
[09:47] <dpm> henninge, hm yeah, I think we'll leave it like this. I wanted the full export to happen on Thursday, but I guess the Tuesday one will do, since it will mean less work.
[09:47] <bigjools> it's kinda discouraged though as it wastes resources, and you can depend on the one in the main archive
[09:48] <al-maisan> hello bigjools, ah, I see, I was looking for a "point-and-click" way ..
[09:48] <al-maisan> yeah .. the package I am interested was uploaded to oneiric ..
[09:48] <bigjools> al-maisan: there's nothing "supported" although you may stumble across a way :)
[09:49] <al-maisan> he-he :) I see
[09:55] <henninge> dpm: you can schedule another one today if you want. Since it is still well below 24 hours, it should be fine.
[09:57] <dpm> henninge, yeah, good point, I think I'll do this anyway. However, the last one took ~18 h and was not available until ~16:30 on the next day, which would be quite late on a Friday
[09:58] <bigjools> ScottK: https://launchpad.net/ubuntu/+source/teeworlds/0.6.0-2~natty1/+build/2623704 is endlessly retrying because it seems to have a broken dependency-wait of "None", I'm going to kill it unless you can upload a newer version with a fix
[09:58] <henninge> dpm: yes, 16:30 CEST
[09:59] <henninge> dpm: which is 16.5 hours from 22 UTC ;-)
[10:09] <dpm> henninge, good point :P
[11:27] <karlp> I'm having problems getting a password reset email from login.launchpad, is this a known issue?
[11:29] <karlp> I've been waiting on emails for a few hours now
[11:29] <wgrant> karlp: Could you file a support request using the link at the bottom of login.launchpad.net?
[11:29] <wgrant> The SSO support team will help you sort it out.
[11:29] <karlp> the one that says, "our service might be having a problem"
[11:30] <karlp> yeah, that seems like a viable solution, you get a form saying, "I'm having problems with [resetting]" [submit]
[11:30] <karlp> A member of the Global Support Services team will be in touch shortly to discuss your needs.
[11:30] <karlp> how exactly will they do that?
[11:31] <wgrant> Didn't you enter your email address?
[11:31] <karlp> sure,
[11:31] <karlp> but they seem to be having problems sending me a mail, I don't have much faith that they will be able to do any more
[11:31] <karlp> and only if the email was cached in a cookie from earlier
[11:31] <karlp> it certainly isn't on that form
[11:32] <wgrant> There is an email address field on https://forms.canonical.com/lp-login-support/
[11:32] <karlp> not on my page
[11:32] <karlp> anyway, more to the point, I just want the password reset email to arrive.
[11:32] <danilos> karlp, have you tried using https://login.ubuntu.com/+forgot_password as well?
[11:33] <wgrant> karlp: Huh, interesting. In Firefox the email address input only appears when you select Other.
[11:33] <karlp> danilos: I have now, but it looks like all the other canonical SSO password resets.
[11:33] <wgrant> karlp: Try selecting Other and entering your address there. GSS will hopefully be in contact with you.
[11:33] <wgrant> SSO isn't managed by the LP team, so we can't do much.
[11:34] <karlp> enter your email, and captcha, and they say, "check your email!"
[11:34] <wgrant> Alternatively, you might be able to track someone down in #canonical-isd.
[11:34] <danilos> karlp, I believe LP login is just a re-branded Ubuntu SSO
[11:52] <ScottK> bigjools: It's an LP bug.  How about you fix that.  The depencies are satisfied in backports, but Soyuz isn't pulling from there correctly due to it being NotAutomatic.
[11:58] <danilos> this channel is now 7 years and 1 day old! wow, it's been a while
[12:04] <nigelb> danilos: \o/
[12:22] <al-maisan> danilo_: how do you know ?
[12:22] <danilos> al-maisan, hey-hey, /msg chanserv info #channel tells me that
[12:23] <al-maisan> ah, nice :)
[14:35] <bigjools> Laney or tumbleweed, should that bug closing work on all change logs for versions between the last publication and the one being synced, or just the one being synced?
[15:01] <Laney> bigjools: all bugs in the generated changelog
[15:01] <bigjools> Laney: not sure that answers the question!
[15:01] <bigjools> it doesn't generate a changelog
[15:02] <Laney> you generate the changelog from the last published version, right?
[15:02] <Laney> all lp bugs mentioned in that changelog should be closed
[15:02] <bigjools> not quite
[15:02] <bigjools> we have the change log in the debian package we're syncing
[15:03] <bigjools> the question is do we *only* look at the changelog for that version?
[15:03] <Laney> no, all intermediate versions too
[15:03] <bigjools> ok, thanks
[15:04] <Laney> that's what you'd get if you passed -v to dpkg-genchanges
[15:04] <Laney> which is what we're trying to emulate here
[15:04] <bigjools> right - the web UI will only show each version's changelog, which I think is an improvement on the old way
[20:15] <nxvl> hi
[20:15] <nxvl> i have a script that uses this line to connect to LP:
[20:16] <nxvl> LP.login_with(sys.argv[0], 'production', version='1.0')
[20:16] <nxvl> if i change 'production' for 'staging' (i need to test a new feature) i get a cert missmatch error
[20:17] <ahasenack> hi, if a launchpad recipe uses nesting to fetch debian/* from another branch, what
[20:17] <nxvl> http://paste.ubuntu.com/674778/
[20:17] <ahasenack> happens if the current branch already has debian/*?
[20:17] <nxvl> that's what i get ^^
[20:45] <CarlFK> https://launchpad.net/~carlfk/+archive/ppa/+build/2745281  "Start in 3 hours.  Build score:2505"
[20:45] <CarlFK> I think I started 3+ hours ago, so 6 hours total
[20:45] <CarlFK> is this typical?
[20:47] <ahasenack> I would say yes
[20:47] <ahasenack> specially on freeze day, I bet several packages are being rushed through
[20:47] <ahasenack> mine took 8h or so yesterday
[20:52] <CarlFK> k - thanks.
[20:58] <micahg> ahasenack: PPA and main archive builders are separate
[20:58] <ahasenack> ok, then I don't know why it took so long yesterday, maybe I as just unlucky and there were several ppa builds
[20:58] <ahasenack> was
[20:59] <micahg> ahasenack: see /topic :)
[20:59] <ahasenack> it too long to fit in my xchat topic bar :)
[20:59] <micahg> ahasenack: archive rebuild in progress
[20:59] <ahasenack> micahg: ah, well, that's what I meant somehow, it's slow because something else related to a release is going on
[22:21] <nigelb> Hey
[22:21] <nigelb> so there was a buildbot failure.
[22:21] <nigelb> How do I know if I caused it?
[22:23] <lifeless> nigelb: a) ECHANNEL. b) you don't.
[22:23] <lifeless> but we can make buildbot public now.
[22:24]  * lifeless rt's it
[22:24] <nigelb> sorry, just got reconnected. My channels are a mess :)
[22:32] <ahasenack> hi, if a launchpad recipe uses nesting to fetch debian/* from another branch, what happens if the current branch already has debian/*? "no defined"? Or is the existing debian directory removed before nest puts the new one in place?
[22:32] <lifeless> boom
[22:32] <lifeless> I think
[22:53] <jelmer> ahasenack: yeah, you'll get a conflict and the build will be aborted
[22:55] <james_w> will it?
[22:56] <james_w> it looks to me like it does a bzrdir.sprout to the existing dir, does that fail if there are files already in that dir?
[23:07] <lifeless> yes