[01:29] <ochosi> hi everyone, when i try to dput my source.changes to my ppa, i get Unable to import paramiko (required for sftp support): No module named paramiko
[01:29] <ochosi> does that mean that sftp doesn't work anymore in general with launchpad?
[01:29] <ochosi> or am i missing something?
[01:31] <TheEvilPhoenix> that seems to be on your end
[01:31] <TheEvilPhoenix> not sure what causes that though
[01:31]  * TheEvilPhoenix uses sftp to upload to ppas still
[01:31] <ochosi> strange. i used exactly the same setup in natty and it worked fine
[01:32] <ochosi> here's my dput.cf: http://pastebin.com/Y0hLPAm9
[01:33] <ochosi> TheEvilPhoenix: would you mind comparing that ^ to your dput.cf?
[01:33] <TheEvilPhoenix> actually i would mind
[01:33] <TheEvilPhoenix> because this system i'm on is Windows
[01:33] <ochosi> oh, i see :)
[01:33]  * TheEvilPhoenix doesnt have his dput.cf  in front of him
[01:33] <wgrant> ochosi: Sounds like python-paramiko isn't installed.
[01:33] <TheEvilPhoenix> the onyl reason i'm here is because of my ZNC :P
[01:33] <TheEvilPhoenix> but listen to wgrant
[01:33] <TheEvilPhoenix> he knows his things  ;P
[01:34] <ochosi> wgrant: ah, is that a new dependency for dput to work with sftp?
[01:34] <ochosi> now it works, thanks a bunch!
[01:36] <wgrant> ochosi: No, it's been the case since sftp was introduced in dput.
[01:36] <ochosi> wgrant: i see, guess i missed it when doing my clean install of oneiric
[01:39] <ochosi> anyway, thanks again and sorry to bother you with trivial stuff like this
[04:07] <odin_> is there allowed/disallowed branching names ?  ~user/<what1>/<what2>/<project>/<branch> ?
[04:08] <odin_> I can't seem to make arbitrary names  like ~user/<project>/<branch>/<branch1>/<branch2>
[04:09] <wgrant> odin_: ~USER/+junk/BRANCH, ~USER/PROJECT/BRANCH or ~USER/DISTRIBUTION/DISTROSERIES/SOURCEPACKAGE/BRANCH
[04:09] <odin_> what is the relation between PROJECT and SOURCEPACKAGE ?
[04:10] <wgrant> The last is for branches for a distribution.
[04:10] <odin_> ~user/ubuntu/natty/<project>/<branch>  is fine to use, but how does <project> relate to <SOURCEPACKAGE>
[04:11] <odin_> the debian/control  Source: line ?
[04:11] <wgrant> No, <project> is wrong. It's a source package name there, not a project name.
[04:11] <wgrant> Right.
[04:12] <odin_> so I have a dailydeb that works (i.e. I can build a source package on launchpad), how is the SOURCEPACKAGE resolved to my one ?
[04:14] <odin_> and how do I make a generic   DISTRIBUTION/DISTROSERIES   ubuntu/*/<project>/<branch>
[04:14] <wgrant> No relationship is enforced. Normally it will match the Source field in debian/control, however.
[04:17] <odin_> is there a defacto default name for the branch which contains only debian/** files ?
[04:17] <odin_> "packaging" or "debian" ?
[04:17] <odin_> I use recipe, that pulls in launchpad git=>bzr mirror of main project tree
[04:18] <odin_> then I "nest debian lp:~owner/project/branch debian" to overlay debian/** tree
[04:19] <odin_> the bzr branch at lp:~owner/project/branch is not the main tree, just the debian/** files
[04:20] <odin_> so do I call this: lp:~owner/project/packaging  or lp:~owner/project/debian  or lp:~owner/project  (is this possible?)  or lp:~owner/project/?????
[04:20] <wgrant> packaging and debian are both fairly common.
[06:53] <Crypticfortune> Hi, I'm trying to upload a package into a PPA (first time), and it came back with "Unable to find distroseries: unstable" what does does this mean and how do I specify something other than "unstable?" (the only place I know of that I specified "unstable" is in debian/changelog)
[06:55] <Crypticfortune> Oh, this may be relevant, if complicating... https://answers.launchpad.net/launchpad/+question/169630
[06:58] <Crypticfortune> Oh, it actually it seems to pull the distro out of the changelog...that's weird... the debian/changelog out of 'apt-get source samtools' uses "unstable" in the distro field and gets away with it...
[06:58] <Crypticfortune> I guess because they don't use launchpad =P
[06:59] <wgrant> Crypticfortune: Packages like that are copied straight from Debian. They don't go through the normal upload process, so the series in the changelog doesn't matter.
[07:00] <Crypticfortune> wgrant: Ya, I originally made my package for debian, but it works in Ubuntu unmodified so I was trying to make it available in a convenient way for Ubuntu users...
[07:01] <Crypticfortune> Any recommendations for a better way to do that (short of a search and replace before uploading to Launchpad)?
[07:02] <wgrant> Crypticfortune: "works in Ubuntu unmodified" <- the source or binaries?
[07:04] <Crypticfortune> wgrant: I meant source
[07:05] <wgrant> Crypticfortune: Can you reuse the binaries between versions? eg. build on lucid, reuse the binaries on maverick/natty/oneiric/precise?
[07:07] <Crypticfortune> wgrant: not sure, but that seems unlikely, because it depends on boost libraries (which include the version number in the name, like libboost_iostreams.so.1.42.0)
[07:07] <wgrant> Crypticfortune: Ah.
[07:07] <wgrant> So, in that case you'll need to upload a separate version for each Ubuntu release that you want to support.
[07:07] <wgrant> The convention is to append something like ~lucid1 to the version.;
[07:11] <Crypticfortune> Hmm... well, I don't see much of a need to support multiple Ubuntu releases... maybe I'll just automate retagging changelog for Ubuntu releases...
[11:33] <RunePhilosof> I'm trying to run the rocketfuel-setup script and I get this error:
[11:33] <RunePhilosof> Making local branch of Launchpad trunk, this may take a while...
[11:33] <RunePhilosof> Permission denied (publickey).
[11:33] <RunePhilosof> bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.
[11:33] <RunePhilosof> ERROR: Unable to create local copy of Rocketfuel trunk
[11:40] <jelmer> RunePhilosof: are you logged into launchpad on your local system?
[11:40] <RunePhilosof> no
[11:41] <jelmer> RunePhilosof: I think rocketfuel-setup assumes you are
[11:41] <jelmer> RunePhilosof: IIRC it also prompts for your launchpad username
[11:41] <RunePhilosof> the Launchpad.net login is not ## strictly necessary, and you can just hit Return there if you ## want; see below for an explanation.
[11:41] <RunePhilosof> Maybe that text should be clarified then
[11:42] <RunePhilosof> https://dev.launchpad.net/Getting
[11:42] <jelmer> yeah, that seems wrong.. as by default I think it uses $LOGNAME rather than not logging in at all
[11:45] <RunePhilosof> I loaded a ssh agent with my cert and now it runs properly
[11:47] <lifeless> it doesn't assume you are logged in
[11:47] <lifeless> but it assumes if you are, that your ssh setup is correct
[11:47] <lifeless> I thin thats a rasonable assumpton :)
[11:48] <wgrant> No.
[11:48] <wgrant> printf "What is your Launchpad username? [$whoami] "
[11:48] <wgrant> read lpusername
[11:48] <wgrant> if [ -z ${lpusername} ]; then lpusername=${whoami}
[11:48] <wgrant> fi
[11:48] <wgrant> bzr launchpad-login $lpusername
[11:49] <lifeless> garh
[11:49] <wgrant> Yes.
[11:49] <lifeless> okies diaf
[15:23] <danhg> Hey everyone at UDS, I'm Dan, the new Usability & Communications Specialist at Launchpad. I'm going to be doing lots of usability testing today, so please ping me if you're around, and would like to get involved!
[15:27] <danhg> All week actually - so let me know when you're free guys!
[16:21] <czajkowski> mrevell: danhg let me know when you want to get some feedback
[16:21] <czajkowski> :D
[16:26] <matsubara> czajkowski, mrevell's computer is locked up and can't reply to you
[16:27] <czajkowski> probably running some dodgey OS :)
[17:23] <buzz_> are i386 builders due back for ppa building soonish or ?
[18:13] <Ursinha> quick question: if I'm a member of a team and subscribe the team to a bug, any other members of the same team can unsubscribe it or only me?
[18:14] <tumbleweed> they can
[18:15] <Daviey> Ursinha: are you talking about a speicifc bug subscription, or a package subscription?
[18:15] <Ursinha> Daviey: specific bug subscription
[18:16] <Daviey> ah, ok
[18:31] <odin_> Syncing the system clock with the buildd NTP service....  4 Nov 15:01:52 ntpdate[3408]: step time server 10.211.37.1 offset -334888.07611 sec ?
[18:31] <odin_> what is the weather like there ?  on the 4th
[18:34] <odin_> maybe run /usr/sbin/ntpdc  "peers" and "sysinfo" on the buildd NTP service system at 10.211.37.1 ?
[18:43] <odin_> can I configure a requirement for at least XYZ ram and XYZ total virtual memory, to build my package  (512Mb / 1536Mb) ?
[18:44] <odin_> any idea what those params are for "lakoocha.ppa - Intel 386 (virtual)"  and "hassium.ppa - Intel 386 (virtual)" might be ?
[18:49] <shnatsel> hi everyone
[18:49] <shnatsel> I have a problem with recipes
[18:49] <shnatsel> looks like one of the builds has hung up
[18:49] <shnatsel> https://code.launchpad.net/~elementary-os/+recipe/beat-box-daily
[18:50] <shnatsel> there's no progress in days, while other recipes build fine
[18:50] <shnatsel> and I can't cancel it or request a new build
[18:50] <shnatsel> what shall I do?
[18:52] <odin_> maybe I make a pseudo-package which has pre/init scripts, that checks ram and virtual memory and reports and aborts
[18:53] <odin_> shnatsel, your control file?  has a blank line at an odd place ?
[18:53] <odin_> shnatsel, line 13 should be between line 15 and 16 ?
[18:54] <odin_> shnatsel, line 13 isn't actually blank, so it all looks like one block
[18:55] <shnatsel> odin_: looks like libgtk-3-dev has the line break at the wrong place
[18:56] <odin_> shnatsel, yeah I would not do that either, you can put 1 per line like " libfoo-dev (>= 1.0),"  with a leading space, but no blank line at the end before Standards-Version
[18:57] <shnatsel> odin_: OK, thanks, I'll fix this. Any suggestions about canceling the build or requesting a new one after I fix the packaging?
[18:57] <odin_> shnatsel, then a blank line before "Package: beatbox", since that is the binary package right ?  and separate, I am not 100% if you must have this blank line, but it seems right to me
[18:57] <odin_> shnatsel, apparently you can not cancel builds
[19:02] <geser> shnatsel: to cancel a hung build you need an LP admin. perhaps the current help contact (benji) can help to get in contact with an LP admin.
[19:03] <lifeless> if its a recipe build, it may be in swap death - will recover.
[19:03] <lifeless> unless its on the binary package build already
[19:04] <shnatsel> it's been there since the 26th
[19:04] <czajkowski> aloha
[19:04] <shnatsel> so... I doubt it somehow.
[19:05] <lifeless> shnatsel: thats in needs-build, not actually building
[19:05] <lifeless> shnatsel: I will confer with a developer that knows the innards of this part of the system; we have some buildd-manager bugs that create inconsistent state
[19:05] <lifeless> this may be an example of that
[19:05] <lifeless> StevenK: wgrant: ^
[19:06] <lifeless> https://code.launchpad.net/~elementary-os/+archive/daily/+recipebuild/107056
[19:14] <shnatsel> Oh, looks like I have one more mysterious thing for you to look into
[19:14] <shnatsel> https://launchpadlibrarian.net/84139675/buildlog.txt.gz
[19:14] <shnatsel> Building recipe:
[19:14] <shnatsel> # bzr-builder format 0.3 deb-version {debupstream}-0~{revno}
[19:14] <shnatsel> lp:egtk
[19:14] <shnatsel> merge packaging lp:~elementary-os/egtk/deb-packaging
[19:14] <shnatsel> bzr: ERROR: unknown command "dailydeb"
[19:15] <shnatsel> failed just now.
[19:17] <afranke> Hi. Can an admin of a moderated team change the status of an approved member to admin?
[19:19] <madnick> hehe, topic solved my question :)
[19:22] <shnatsel> afranke: yes. Click "all members" on the team page. You'll get a list of people in the team, with "edit" icon next to each of them. Click it and there will be the permissions setting.
[19:23] <afranke> shnatsel, that's the page where you change subscription date, right?
[19:24] <shnatsel> afranke: expiry date you mean?
[19:24] <afranke> Yes, sorry, that's what I meant.
[19:24] <shnatsel> afranke: yes
[19:24] <afranke> Ok… well I can't change the admin status.
[19:25] <shnatsel> afranke: there's an "Admin: (*) yes ( ) no" switcher
[19:25] <afranke> I have "Administrator:	No"
[19:25] <afranke> But that's just text.
[19:26] <shnatsel> afranke: hmm... no idea, I have it working for me. I'm not the team owner, just an admin, and I can change status of other people.
[19:28] <lifeless> afranke: what team, and whats your lp username ?
[19:28] <afranke> I'm the only admin of ubuntu-l10n-fr and my membership expires in 4 hours. I can't change it and the owner (seb128) is usually inactive (and even more now that he's at UDS). I contacted him one week ago to change my expiration date, but no news.
[19:29] <afranke> I'm afranke (Alexandre Franke).
[19:29] <lifeless> afranke: which user were you trying to promote to admin?
[19:30] <afranke> paroz
[19:30] <afranke> Claude Paroz
[19:31] <lifeless> shnatsel: I think you are the team owner
[19:31] <shnatsel> lifeless: no, I am not.
[19:31] <lifeless> afranke: please open a ticket on answers.launchpad.net/launchpad
[19:31] <lifeless> shnatsel: which team ?
[19:31] <shnatsel> lifeless: I used to be one for 2 hours
[19:31] <shnatsel> lifeless: https://launchpad.net/~elementary-os
[19:31] <lifeless> shnatsel: this could be a fun bug :)
[19:32] <shnatsel> lifeless: It's raining cats and bugs XD
[19:32] <afranke> lifeless, what should I open the ticket for? Not being able to promote, idle owner and my membership expiring, both, something else?
[19:33] <lifeless> shnatsel: and when you click on the edit link beside (say) cody, it will let you toggle the admin flag ?
[19:33] <lifeless> afranke: your membership I'd suggest
[19:33] <afranke> lifeless, ok.
[19:33] <lifeless> afranke: and admin can probably extend it without any issue, for a couple months
[19:33] <shnatsel> lifeless: yes
[19:33] <lifeless> shnatsel: weird
[19:33] <shnatsel> lifeless: never tried, but the switcher is active.
[19:34] <lifeless> shnatsel: that means the form thinks you can,
[19:34] <afranke> lifeless, how does ownership transfer work? Does the owner do it himself or does he ask someone else to do it?
[19:34] <lifeless> afranke: vastly prefer them to do it themselves
[19:34] <lifeless> afranke: which they can do
[19:34] <afranke> Ok.
[19:35] <lifeless> afranke: if they are nonresponsive and the person to whom the transfer should go is in good standing and there is some evidence that its appropriate, then we can do it, but thats the exception.
[19:36] <afranke> lifeless, I guess seb128 is still active enough to handle that.
[19:36] <shnatsel> afranke: the funny thing is that after I made an admin a commoner, I can't toggle it back.
[19:36] <lifeless> shnatsel: heh you tested on prod data did you?
[19:36] <shnatsel> lifeless: exactly.
[19:37] <shnatsel> lifeless: totally forgot about staging.
[19:37] <lifeless> :)
[19:37] <sinzui> lifeless, shnatsel I do not follow the conversation: I see ~seb128 is the owner of  ubuntu-l10n-fr andonlu he can appoint admins
[19:37] <shnatsel> lifeless: the funny thing is I'm developing a staging environment for desktop apps XD
[19:37] <lifeless> sinzui: shnatsel, admin not owner of another team, can promote other members to admin.
[19:38] <sinzui> admins cannot promote.
[19:38] <lifeless> sinzui: afranke, admin not owner of u-*fr cannot promote other members to admin.
[19:38] <shnatsel> yeah they can only defrock
[19:38] <lifeless> shnatsel: *oh* - you were looking at an admin were you ?
[19:39] <lifeless> sinzui: now I get it; admins can unadmin other admins, but not the reverse ?
[19:39] <sinzui> right
[19:39] <lifeless> shnatsel: I thought you were looking at a member
[19:39] <sinzui> and they cannot extend th membership either
[19:39] <lifeless> sinzui: sorry for the distraction then!
[19:39] <lifeless> sinzui: perhaps they should be able to do some of this ?
[19:40] <lifeless> sinzui: I'm thinking owner-is-not-in-team scenarios
[19:40] <sinzui> bug 206058 and bug 4744
[19:40] <sinzui> and bug 102180
[19:41] <afranke> question 177021
[19:41] <lifeless> sinzui: legend
[19:41] <lifeless> sinzui: ah, admins are only prohibited from changing their *own* date ?
[19:41] <afranke> ubot5, I wonder what keyword triggers "answers" links… :)
[19:43] <afranke> answer 177021
[19:43] <afranke> Anyway… https://answers.launchpad.net/launchpad/+question/177021
[19:43] <lifeless> if benji is still around, he'll look at it I'm sure, otherwise someone else will fairly soon
[19:43] <sinzui> lifeless, yes I think that is the case, but we have a few other bugs where users are blocked renewing and I suspect there are cases where the admin is blocked
[19:44] <afranke> Thank you all for your help.
[19:47] <benji> yep, I'm just off a phone call and about to do a CHR run
[19:50] <afranke> I have to go, see you!
[19:52]  * czajkowski hugs mrevell 
[19:52] <Pendulum> danhg: hey, I'm at UDS and would be more than happy to do some testing for you (I'm the woman in the wheelchair so pretty easy to spot ;) )
[19:53] <odin_> Syncing the system clock with the buildd NTP service....  4 Nov 15:01:52 ntpdate[3408]: step time server 10.211.37.1 offset -334888.07611 sec ?  maybe run /usr/sbin/ntpdc  "peers" and "sysinfo" on the buildd NTP service system at 10.211.37.1 ?
[20:03] <odin_> can I use pbuilder to build but then not cleanup, so I can --login and try commands myself ?
[20:05] <odin_> try --debug
[20:14] <geser> e.g. when a build failed to examine why it failed?
[20:15] <odin_> bzr: ERROR: unknown command "dailydeb", is this correct thing to see from a build worker ?
[20:16] <geser> sorry I've no experience with the recipe builds
[20:17] <tumbleweed> that sounds likea a problem with the daily build chroots, (assiming you are pasting that from a launchpad build log, not something local)
[20:17] <odin_> yup but its lucid, maybe it did not come with bzr-builder by default ?
[20:18] <lifeless> hats the build url
[20:19] <odin_> 84143266 (sorry different machine no c'n'p)
[20:19] <tumbleweed> no ubuntu release comes with bzr-builder by default
[20:19] <odin_> so I add to Build-Depends
[20:20] <lifeless> odin_: well, I suspect you've got something odd going on
[20:20] <odin_> can I run pbuilder locally (on oneiric, but not have it delete anything on failure)
[20:20] <lifeless> odin_: your build rules shouldn't be calling bzr dailydeb or anything like that
[20:20] <odin_> I think it picks it up from the recipe  "# bzr-builder ...."
[20:21] <lifeless> recipe builds are special, they run in an environment with bzr and bzr builder installed.
[20:21] <lifeless> your build deps won't affect recipe builds at all.
[20:23] <odin_> well I have one battle that some peoples VMs are too small, and initializing Java JDK errors, would be nice to configure minimum ram/virtual size hints into debian/control and/or blacklist some workers by name
[20:24] <lifeless> the intel VM's all have 2G, if you can't build in that I think its your software needs the fix :)
[20:24] <odin_> I have seen VMs with 512Mb RAM
[20:25] <odin_> unfortunately it is not my software/package that needs fixing, the install for a build dependency needs fixing and that is beyond my control
[20:25] <odin_> I'm not going to fork and maintain it just for that
[20:27] <odin_> the packages I have seen fail (due to lack of Java heap, is openjdk-6-jre-headless and ca-certificates-java both run the JVM, I guess without using -Xmx256 to place a heap restriction on it), but I don't know the real cause and I don't maintain those packages
[20:28] <odin_> the option -Xmx256M would restrict the max heap to 256Mb and would probably fix the problem if the pre/post/install/configure scripts were fixed
[20:29] <jelmer> lamont: ping
[20:29] <lamont> morning
[20:29] <jelmer> hi
[20:30] <jelmer> it seems like some builders now no longer have the dailydeb command (from bzr-builder) available
[20:30] <lamont> and how are you today?
[20:30] <lamont> jelmer: sorted.  see also bug 616878
[20:30] <jelmer> lamont: did you see my last comment on that bug?
[20:31] <jelmer> lamont: great, so the bzr-builder issue should now be fixed? was that just recently?
[20:32] <lamont> jelmer: read it now, and I suspect that the answer is "not yet" - the commit is occurring at the tail end of the late_command in debian-installer, before the reboot
[20:32] <lamont> the current user is root
[20:32] <lamont> if we really think it's limited to the d-i world, that'd be cool
[20:33] <jelmer> lamont: I don't think there is a regression of bug 616878, but this a situation we just didn't try to cover in our fix
[20:34] <lamont> jelmer: /etc/mailname was not present on the machine at the time of the commit
[20:34] <lamont>  cat /etc/mailname
[20:34] <lamont> cat: /etc/mailname: No such file or directory
[20:34] <lamont> yep.  definitely wasn't there at install time... it still isn't
[20:35] <jelmer> ok
[20:36] <lamont> and yeah, new case
[20:36] <lamont> sorry for not getting that one in initially
[20:36] <lamont> the ticket has a bit of my grumbling, fwiw
[20:42] <odin_> how do I stop pbuilder from deleting /var/cache/pbuilder/build/** on error ?
[20:43] <jelmer> lamont: Thanks I'll try to put as much info as I can in a new bug report
[20:44]  * jelmer spits out a comma
[20:45] <jelmer> odin_: #ubuntu-packaging is perhaps a better place for that sort of question
[20:45] <shnatsel> I have more of those recipe errors
[20:45] <shnatsel> https://launchpadlibrarian.net/84145718/buildlog.txt.gz
[20:47] <jelmer> lamont: ^
[20:47] <jelmer> lamont: I'm also still getting command not found errors
[20:47] <jelmer> most recently on dubnium
[20:48] <lamont> it would be good if you did a dpkg -l bzr-builder in there... maybe you already do
[20:49] <jelmer> lamont: I had the same though, I filed a bug against Launchpad about doing exactly that this morning.
[20:50] <lamont> ii  bzr            2.4.0-0ubuntu2 easy to use distributed version control syst
[20:50] <lamont> ii  bzr-builder    0.7.1-0ubuntu1 construct a bzr branch from a recipe
[20:50] <lamont> (dubnium)root@dubnium:~#
[20:50] <lamont> looks current to me...
[20:50] <shnatsel> jeblair: bug number?
[20:50] <lamont> machine has been up for 2:30
[20:50] <lamont> 150 minutes
[20:51] <jelmer> lamont: does 'bzr plugins' list 'builder' as one of the entries/
[20:51] <jelmer> ?
[20:52] <lamont> nope
[20:52] <lamont> http://paste.ubuntu.com/724693/
[20:53] <jelmer> lamont: those version numbers suggest it's not running one of the backports - is it using post-lucid, or did the version numbers change after the upload to the cat archive?
[20:53] <lamont> hrmpf
[20:54] <lamont> ii  bzr                                          2.4.0-0ubuntu2~11.IS.8.04                    easy to use distributed version control system
[20:54] <lamont> ii  bzr-builder                                  0.7.1-0ubuntu1~6.IS.8.04                     construct a bzr branch from a recipe
[20:54] <lamont> helps if dpkg -l doesn't make it fit
[20:54] <lamont> amusing place it chose to truncate the version at though
[20:55] <jelmer> ah, heh
[20:59] <jelmer> oh fuck. the hardy-cat bzr-builder package has a python namespace issue because it's using python-support rather than python-central
[21:00] <jelmer> so the plugin doesn't get picked up by bzr
[21:01] <lamont> jelmer: wonderful. :(
[21:02] <lamont> jelmer: I'll see if I can corner someone who might have a better answer than "sucks to be you".  meanwhile, wanna work on that python-central version?
[21:02] <jelmer> lamont: already on it
[21:06] <lamont> jelmer: the definitive answer is "use the same one as the distro does for namespace packages".  IOW, sucks to be you
[21:12] <jelmer> lamont: thanks, that does indeed mean switching bzr-builder to -central
[21:13] <jelmer> lamont: I wonder how this ever worked in QA though, or was that perhaps with an old version of the packages as well?
[21:14] <lamont> quite possibly.  dunno
[21:45] <odin_> when does the dailydeb fix go live across the workers ?
[21:54] <jelmer> lamont: still there?
[21:57] <lamont> sure
[22:10] <jelmer> lamont: see privmsg
[22:20] <jelmer> lamont: to summarize - there is a package with pycentral in the PPA, would it be possible to deploy that soon?
[23:07] <jelmer> lamont: ping?
[23:15] <wgrant> lifeless: Ah, that's from the build farm vs. dogfood incident last week.
[23:15] <wgrant> lifeless: We fixed binary builds, but not recipes.
[23:18] <lifeless> wgrant: thanks
[23:26] <lamont> jelmer: ack