[00:01] <directhex> i need a no-change rebuild of antlr for the current mono transition. i lack upload powers for it, since it's only marginally monoish
[00:04] <Viper550> Does anyone know how exactly to change the gtk theme on lightdm?
[00:25] <Rioting_Pacifist> am i right in thinking pre-up and pre-down are no longer called in 11.04?
[00:25] <Laney> directhex: ajmitch can do such!
[00:26] <directhex> Laney: why hasn't he done it already? >8\/
[00:27] <TheMuso> directhex: I'll take care of it for you.
[00:27] <directhex> TheMuso: thanks
[00:27] <directhex> TheMuso: i've test-built it, so it should be fine & dandy with just a rebuild
[00:27] <TheMuso> directhex: What should I be mentioning in the changelog? You said its for the mono transition, but do you want anything more specific?
[00:28] <TheMuso> I'll test build again to be sure.
[00:29] <directhex> TheMuso: the Mono CLR 4.0 class library, more specifically. or something along those lines. just make sure it has "4.0" in it somewhere
[00:29] <TheMuso> urm ok. I'm trying to parse that with lttle success.
[00:29] <TheMuso> little
[00:29] <ajmitch> Laney: eh what?
[00:31] <Laney> ajmitch: just trolling you
[00:31] <Laney> carry on :)
[00:31] <ajmitch> :(
[00:31]  * Laney cuddles you
[00:31] <ajmitch> directhex: sorry I'm too slow to help you
[00:32] <directhex> clearly!
[00:32] <Laney> what in the world is going on
[00:32] <Laney> a huge crowd of people have descended upon the street
[00:33] <Laney> they appear to be filming something
[00:34] <TheMuso> directhex: Ok, I see what change with the rebuild, and your message makes sense now. Will upload.
[00:43] <TheMuso> directhex: Done.
[00:47] <Laney> cd ..
[00:47] <Laney> oops
[00:47] <directhex> TheMuso: thanks
[00:48] <directhex> TheMuso: that should make a dent on the transition
[00:48] <TheMuso> Cool.
[05:38] <pitti_> Good morning
[05:45] <maco> ev: can you re-review that merge proposal? i made the requested changes. users in bug report are getting all smart-alecky *sigh*
[05:47] <ScottK> Is smart alecky users going to slow him down or speed him up?
[05:50] <maco> ScottK: not sure. they're being smart alecky at me not him though
[05:50] <maco> "fix it or find someone smart enough to do so" they say
[05:51] <maco> zomg its been two whole weeks
[05:51] <maco> yeah yeah i closed a 4-digit bug 2 weeks ago
[05:51] <maco> sheesh, a bit of perspective...
[05:58] <ScottK> Right, so I'm confused how he's supposed to find that motivational?  He might just get popcorn and enjoy the show.
[06:00] <micahg> can I get an AA to reject the rdscli in the queue, smoser has made some changes that I asked for and I'm waiting for one more before uploading
[06:01] <micahg> it's in NEW for oneiric
[06:02] <ScottK> Looking.
[06:03] <ScottK> micahg: Done.
[06:03] <micahg> ScottK: thanks
[06:03] <ScottK> You're welcome.
[06:08] <RoAkSoAx> is the archive admin that rejected rdscli around?
[06:09] <RoAkSoAx> micahg: ideas.. you commented on it
[06:09] <ScottK> RoAkSoAx: Read the backscroll.
[06:09] <RoAkSoAx> ahh i just read
[06:10] <RoAkSoAx> micahg: well I reviewed it and IMHO it could have been accepted with the warnings
[06:10] <RoAkSoAx> ScottK: od you have time to review resource-agents and fence-agents
[06:10] <RoAkSoAx> please
[06:10] <RoAkSoAx> :)
[06:10] <ScottK> No.  Just about to go to bed.
[06:10] <RoAkSoAx> ScottK: no worries then, thanks ;)
[06:11] <micahg> RoAkSoAx: I didn't see a second ACK, so I thought I'd review it since you uploaded it already, it needed some fixing and we weren't near a freeze, so I thought fixing before hitting the archive was a good idea
[06:13] <RoAkSoAx> micahg: yeah well warnings are not a big of a deal atm .. I'm not in my main computer but they were only manpages and few spelling errors that seemed to not being fixable
[06:13] <RoAkSoAx> but from my point of view no reason to reject the upload
[06:13] <micahg> RoAkSoAx: right, some were debian/control fixes, also, no instructions on how to update the package
[06:14] <RoAkSoAx> micahg: yeah 1 spelling one description might be too short which I thought that the description couldn't get any bigger
[06:15] <RoAkSoAx> because there was nothing more to say
[06:15] <RoAkSoAx> but no deal breaker IMHO
[06:15] <RoAkSoAx> :)
[06:15] <micahg> RoAkSoAx: yeah, I wasn't worried about that one, more the duplicate depends fields, build-dep on quilt, and various other things, if we were near a freeze, I would agree, but it's good practice for the packager to learn these things :)
[06:17] <RoAkSoAx> micahg: the source format is 3.0 quilt, it doesn't need quilt as a dependency :)
[06:18] <micahg> RoAkSoAx: right, but it had one before :)
[06:19] <micahg> also, apparently the depends list was short, his second version has a lot more
[06:21] <RoAkSoAx> micahg: i guess the weird thing is that I dind't see all those warnings that were showed to you :S
[06:22] <micahg> RoAkSoAx: I have an alias called super_lintian that I run for new packages: lintian -iIEv --pedantic
[06:22] <micahg> I run it on the source and binary packages
[06:23] <RoAkSoAx> micahg: k, will recheck that tomorrow
[06:23] <micahg> RoAkSoAx: could you get it to build in a clean env on i386 oneiric?
[06:23] <micahg> that was the one thing troubling me, I got it to build on my amd64 machine, but in my oneiric i386 sbuild I get JavaVM initialization errors
[06:28] <RoAkSoAx> micahg: yeah it was working fine for me
[06:28] <micahg> k, I figured as much
[06:28] <RoAkSoAx> micahg: i'll recheck everything tomorrow on clean pbuilders
[06:28] <micahg> RoAkSoAx: k, ACK from me once it has README.source
[06:28] <RoAkSoAx> micahg: thanks for reviweing it btw... :)
[06:29] <micahg> RoAkSoAx: no problem
[06:31] <micahg> RoAkSoAx: and sorry, I should have subscribed you to the bug so you knew what was going on
[06:32] <RoAkSoAx> micahg: no worries :)
[06:33] <RoAkSoAx> micahg: i was just surprised of all those lintian warnings that you saw which i didn't
[06:34] <micahg> I also ran it with oneiric's lintian since that's where I built it, normally would've been on natty
[06:35] <RoAkSoAx> micahg: maybe that's the difference cause I did it in natty
[06:35] <RoAkSoAx> my external screens are kind amessed up with oneiric
[06:36] <RoAkSoAx> since I work from external monitors
[06:36] <micahg> ah, I'm on laptops at the moment
[06:36] <RoAkSoAx> micahg: yeah me too, one running natty and one oneiric
[06:36] <RoAkSoAx> and a thjird one as a oneiric home server
[06:36] <micahg> yep, that's what I have
[06:37] <RoAkSoAx> I usually work remotely since the oneiric one external display ability is broekn
[06:39] <RoAkSoAx> micahg: but anyways, im off to bed
[06:39] <RoAkSoAx> have a good one
[08:33] <diwic> doko_, apw asked me to ping you about bug 789031
[08:34] <apw> doko_, i have this odd feeling we've seen this either a fix in the kernel to work round it, or i saw it on a gcc upload, can you remember
[08:34] <apw> diwic, does the code work ok on the 4.6 compiler ?
[08:34] <diwic> apw, let me check
[08:35] <diwic> hmm, 4.6 does not ship with natty it seems
[08:35] <apw> diwic, sadly not, there are onieiric chroots on tangerine
[08:36] <diwic> apw, perhaps you could give it a shot quicker than I, there is a test.c in the bug
[08:41] <apw> diwic, i cannot trigger the error on any version of the compiler right now
[08:43] <apw> diwic, can you confirm you gcc-4.5 version for me ?
[08:43] <apw> Package: gcc 4:4.5.2-1ubuntu3
[08:43] <diwic> apw, really? It triggers here with gcc 4.5.2-8ubuntu4
[08:44] <apw> diwic, 64 or 32 bit ?
[08:44] <diwic> 32 bit
[08:44] <diwic> works fine on amd64
[08:44] <apw> diwic, better, ok
[08:44] <diwic> at least this example (amd64 has more registers)
[08:45] <diwic> apw, yeah, that's the same package version as I have here
[08:45] <apw> diwic, ok 4.6 shows the same behaviour
[08:46] <diwic> ok
[08:47] <apw> diwic, and gcc-4.4 in lucid too
[08:48] <diwic> seems doko_ is not around atm
[08:49] <diwic> doko_, actually in pulseaudio the problem was worse, it allocated one "r" and one "rm" into the same register, so it compiled it but generated faulty code :-(
[08:52] <diwic> apw, ok but I guess I've done what I can now? Just want to make sure that someone looks at the bug at some not too distant point in the future
[08:52] <apw> diwic, yep
[08:54] <dholbach> good morning
[08:56] <dholbach> RoAkSoAx, Happy Birthday! :)
[09:16] <seb128> slangasek, hi, could you copy the xerror message you get with that g-s-d issue?
[09:17] <seb128> oh, it's in the gtk bug you opened yesterday
[09:49] <ev> maco: sure thing, on it now
[09:54] <ev> maco: done. It'll go out with the next ubiqutiy
[11:25] <brendand_> does anyone know what NetworkManager state 'locally connected' 50 means
[11:25] <brendand_> i guessed at local ip available but no global ip
[11:25] <brendand_> but if i connect to my router when it has no internet connection i still get 70 back
[11:25] <brendand_> global connection
[12:39] <doko> jhunt_: libnih now built on armel. not sure if you want to build upstart with standard compiler flags too
[12:50]  * ogra_ hugs doko for that 
[13:08] <mr_pouit> cjwatson: looking at *.manifest files, xfce packages are here, so I guess your fix worked. Thanks!
[13:09] <aditya> hi there
[13:09] <aditya> e
[13:09] <aditya> unity geeks ther?
[13:12] <abhinav-> aditya: may be #ayatana will be a better place
[13:12] <aditya> no problems
[13:13] <aditya> thanx
[13:21] <cjwatson> mr_pouit: good good
[13:23] <aditya> any new issues guys?
[13:27] <abhinav-> aditya: what are you looking for ?
[13:28] <aditya> am new to this group , just want to get into ubuntu development
[13:28] <abhinav-> ah ok. Welcome :)
[13:29] <aditya> thanks
[13:29] <aditya> any group talks going on presently?
[13:30] <abhinav-> aditya: there will be Ubuntu Developer Week in July, that is very helpful for new comers to Ubuntu development
[13:30] <aditya> ok
[13:31] <aditya> are you abhinav upadhyay by any chance?
[13:31] <abhinav-> yes
[13:31] <aditya> k
[13:35] <abhinav-> aditya: you might want to go through this to set up your development environment. dholbach even did a video on ustream for this, you may search for it. It's a good place to start with
[13:36] <abhinav-> https://wiki.ubuntu.com/MeetingLogs/devweek1007/GetStarted
[13:36] <aditya> thanx
[13:37] <vish> !development | aditya
[13:37] <smoser> micahg, i'll add a README.source file.
[13:38] <aditya> thanx ubottu
[13:38] <smoser> if you, or anyone, can write a uscan that parses output of http://s3.amazonaws.com/rds-downloads/ that would be what needs to be done.
[13:39] <smoser> i think the issue i ran into before was that there are no line breaks.
[13:41] <bdrung> whom should i ask to get a proposed package accepted?
[13:42] <Laney> how long has it been?
[13:42] <persia> smoser: You could create a small AWS service that did XSLT on that to make it standard uscan input format :)
[13:42] <bdrung> Laney: a few days
[13:43] <bdrung> two to be precise
[13:43] <smoser> indeed.  i would think i could probably add support to uscan, but it would be very limited in use (other than the half a dozen or so packages from amazon that do this).
[13:44]  * mok0 is damned annoyed that installing drupal6 forces mysql to be installed. I use postgresql
[13:45] <persia> For sourceforge, I think the conclusion was that it was easier to create a translation service than to add parsing to uscan, but you may find the converse to be true.
[13:55] <doko> jamespage: just to clarify, were the fop dependencies included in the MIR review?
[14:01] <seb128> cjwatson, bug #797669, I'm just pointing it in case you didn't notice it, should probably be milestoned for the next alpha?
[14:13] <jamespage> doko: I've not reviewed the additional dependencies added to the MIR since SpamapS raised the original bug report
[14:14] <jamespage> thats batik, libsaxon-java and xmlgraphics-commons
[14:15] <doko> yes, set to incomplete for now
[14:23] <cjwatson> seb128: ok
[14:33] <ntr0py> I am trying to get proftpd to authenticate users against a postgresql db and i am missing "mod_sql_passwd.c" for "SQLPasswordEngine" directive... Does somebody know where it did go?
[14:34] <directhex> ntr0py, you have proftpd-mod-pgsql installed?
[14:35] <ntr0py> yes
[14:36] <directhex> mod_sql_passwd.so is in the proftpd-basic package
[14:38] <ntr0py> directhex: for maverick it is not in there...
[14:39] <directhex> this isn't an end-user support channel, and maverick isn't really something anyone's thinking about anymore in development terms
[14:40] <ntr0py> directhex: ok thanks i found it in natty package, i will try to compile it for maverick
[14:49] <maco> ev: thanks
[14:49] <RoAkSoAx> dholbach thank you!!!
[14:52] <bdrung> cjwatson: can you have a look at the vlc sru upload?
[14:52] <bdrung> cjwatson: and set this branch to merged: https://code.launchpad.net/~druke/ubuntu/natty/g15daemon/bug-657598/+merge/64168 ?
[14:53] <cjwatson> both will have to wait until this CD has synced so I have bearable bandwidth again
[14:54] <cjwatson> I'm doing minimal-bandwidth things in the meantime ...
[14:54] <bdrung> cjwatson: even for setting a merge proposal status?
[15:02] <cjwatson> bdrung: well, the page ain't loading, so apparently so
[15:03] <goof2092> pitti: when you have the please review Language Pack bug report #796591 for Bemba
[15:15] <mterry> poolie, heyo, are you still involved with librsync at all?
[15:16] <pitti> hello goof2092
[15:18] <pitti> goof2092: I replied in the bug
[15:37] <jcastro> ev: any chance you have screenshots the screens that come after each of the choices in the installer? Basically a step by step for each available choice a user can pic?
[16:04] <mterry> barry, to port a package to dh_python2, all packages that put files into the same toplevel module need to be ported at the same time?
[16:05] <barry> mterry: yep, all subpackages of the same namespace package must be ported at the same time.  e.g. all lazr.* or zope.*
[16:06] <mterry> barry, ok.  Then I need to do futz with the dependencies to make sure that a user doesn't only get half the upgrade?
[16:07] <barry> mterry: good question.  i think if you upload all the ported packages at the same time, there'll be only a small window where they could get screwed, which probably isn't enough to worry about.  but maybe i'm missing something
[16:07] <seb128> barry, yeah, you miss partial upgrades
[16:07] <mterry> seb128, you're saying we don't worry about those?
[16:07] <seb128> like users doing an apt-get install binary and not a dist-upgrade
[16:08] <barry> seb128: ah, yeah thanks
[16:08] <seb128> mterry, I'm not saying that ;-)
[16:08] <barry> seb128: how do you suggest we handle these upgrade dependencies?
[16:08] <seb128> well ideally you would Breaks:.... on all the things you actually break
[16:08] <mterry> seb128, that sounds more like you  :)
[16:09] <seb128> not sure how practical it is for that python transition
[16:09] <barry> mterry: i guess it's a good question to ask on ubuntu-devel and see what people think.  i'm working on a critical bug atm so don't have time to do that.  could you?
[16:10] <mterry> barry, sure
[16:10] <barry> mterry: thanks!
[16:18] <mterry> doko, the ubuntuone python package set is a big, lockstep upgrade to dh_python2.  How about I trade you 2 other packages for ubuntuone-couch?  :)
[16:25] <doko> mterry: I don't mind if it's now. just be aware that it stays on your radar
[16:26] <doko> barry, seb128: well, we don't support partial upgrades, or did that change?
[16:26] <seb128> I don't know if we have an official position on that
[16:27] <seb128> I usually try to get things to not break in partial upgrades for desktop but I'm not sure if we say that we support those or not
[16:44] <cjwatson> doko: I've never heard any official statement that we don't support partial upgrades.  IMO it's silly *not* to support partial upgrades to at least some extent because somebody's bound to run into it and file a bug and why wouldn't we want to avoid that?
[16:45] <cjwatson> not supporting systems that are half karmic and half maverick or something is a different matter, but that's a much weaker statement
[16:46] <cjwatson> bdrung: marked that g15daemon branch as merged now
[16:46] <bdrung> thanks
[16:46] <mterry> pitti, thanks for the awesome dh_python2 tip
[16:46] <cjwatson> bdrung: looks like somebody dealt with the vlc SRUs?
[16:46] <pitti> mterry: glad that I could recycle it :)
[16:48] <bdrung> cjwatson: no, i was talking about 1.1.9-1ubuntu1.2
[16:51] <cjwatson> bdrung: http://people.canonical.com/~ubuntu-archive/pending-sru.html isn't showing any vlc package in -proposed and nothing in any of the upload queues, so you're going to need to give me more detail if you want me to do something, I think
[16:52] <cjwatson> pitti: I'm reviewing the status of the grub2/lupin SRUs
[16:52] <bdrung> cjwatson: https://launchpad.net/ubuntu/natty/+queue?queue_state=1&queue_text=
[16:53] <cjwatson> pitti: bug 610898 has now been verified on both lucid and maverick, and I've marked it v-done
[16:53] <cjwatson> pitti: I think the testing there is almost certainly sufficient to cover bug 695290 and bug 742967 as well; do you agree?
[16:54] <cjwatson> pitti: then we can unblock bug 687501 and we're good to go
[16:56] <pitti> cjwatson: yes, for regression testing that's certainly more than we usually get, so I'm fine with moving this to -updates
[16:57] <cjwatson> excellent, I'll mark those bugs then
[16:57] <cjwatson> lupin has to move at the same time
[17:00] <cjwatson> bdrung: looking now, then
[17:01] <cyrildz> hi all
[17:01] <cyrildz> I'm new here
[17:01] <cyrildz> I'm an ubuntu user and I want to start programming
[17:02] <cyrildz> I don't know where  nor how to start
[17:02] <cyrildz> If I am on the wrong place , please let me know
[17:03] <cyrildz> I 'm very interested in C/C++
[17:04] <cjwatson> bdrung: OK, approved, thanks
[17:04] <cyrildz> I have learnt stuff on C/C++ , I like the Object Oriented approche of C++ and now I want to jump ahead a do something real
[17:05] <cyrildz> a bit of help to where to look  would be welcome
[17:07] <cjwatson> cyrildz: this isn't really a help-you-get-started-programming channel - perhaps try #ubuntu-app-devel, or a specialist C or C++ channel (though I can't recommend one)?
[17:08] <cyrildz> thanks , I will have a look a this
[17:10] <bdrung> cjwatson: thanks
[17:20] <jibel> cjwatson, latest alternate build failed to install see bug 798306. I filed it against debian-installer but from the error it looks more like debconf. It is reproducible.
[17:21] <smoser> persia, https://code.launchpad.net/~smoser/ubuntu/oneiric/devscripts/lp-798293/+merge/64857 is to add S3 bucket listing support to uscan
[17:21] <cjwatson> jibel: thanks, I'll have a look.  I think I probably need to seed debconf-i18n
[17:21] <persia> smoser, Heh.  That was fast.  Nice!
[17:40] <Daviey> ls
[17:40] <Quintasan> :D
[17:41]  * Quintasan does that way too often
[18:23] <jdstrand> Daviey: fyi, I am finalizing the patch to fix bug #795800. I should be uploading it to Ubuntu today (tomorrow at the latest) as well as submitting the patch upstream
[18:24] <Daviey> jdstrand: Ah super.. I understand zul was looking at the libvirt merge, but wanted you to peer review it? :)
[18:25] <jdstrand> Daviey: last I heard, I reviewed hallyn's merge, uploaded it and then zul was asked to test said merge against Ubuntu Cloud
[18:26] <zul> jdstrand: yeah there is a newer version in debian now though
[18:26] <jdstrand> Daviey: if he is doing an 0.9.2 merge, I can review it and add my patch to fix the bug to it during the review
[18:26] <Daviey> sounds like a plan!
[18:26] <zul> jdstrand: ill talk about it to you later, im kind of in a buffer overflow situation right now :)
[18:26]  * Daviey cycles zul 
[18:27] <jdstrand> zul: it is unlikely I could put real review time in until monday anyway, so no worries
[18:27] <zul> jdstrand: ack :)
[18:27] <Daviey> peer reviews rock my world.
[18:27] <jdstrand> I'll still get my upload in though
[18:35] <micahg> jdstrand: is there a reason why linux-any is dropped from the merge?  AFAIK launchpad understands that now
[18:50] <jdstrand> micahg: all I see in the merge from hallyn is 'remove [linux-any] from all dependencies'
[18:50] <jdstrand> zul: fyi ^
[18:50] <zul> no idea
[18:51] <pitti> cjwatson, kees, sabdfl, Keybuk: TB meeting reminder in 10 mins
[18:51] <micahg> jdstrand: right, was just wondering if you knew why, I guess I should talk to hallyn about it
[18:52] <jdstrand> zul: no I meant you may want to leave it in next time :)
[18:52] <zul> jdstrand: heh ok
[18:54] <micahg> zul: another thing to keep in mind is that we still have python2.6 in oneiric, even if not though, if the python-dev-all package doesn't have a python version, I don't think you need to worry about X-Python-Version being older
[19:17] <hrw> I have small C code which compiles on amd64 but fails on armel
[19:24] <ev> jcastro: Apols, somehow I didn't see your message until now
[19:24] <jcastro> no worries, it's not urgent or anything
[19:24] <ev> I don't have up to date ones, sadly. There are olds ones on people.c.c/~Evans
[19:24] <ev> Evand
[19:24] <ev> Damn iOS
[19:25] <jcastro> ta, that should put me on the right track
[20:14] <jdstrand> zul: what is happening with libxen-dev-- has it been approved in the MIR? your libvirt upload won't build cause it isn't available
[20:14] <zul> jdstrand: ill go check
[20:17] <zul> jdstrand: MIR has been aproved
[20:17] <zul> so i guess they need to be promoted
[20:17] <jdstrand> zul: ok, then I'll promote it. what is the bug number?
[20:18] <zul> 790854
[20:20] <jdstrand> zul: the bug states that the server team will do security support-- can Daviey or someone else comment in the bug that that will happen?
[20:20] <zul> jdstrand: sure
[20:20] <zul> Daviey: ^^^
[20:20] <jdstrand> support really means testing here, as I read it
[20:20] <zul> jdstrand: but that will probably end being me anyways
[20:20] <jdstrand> (like euca, iscsi, etc where we don't have the testing infrastructure for it)
[20:21] <zul> jdstrand: wha? you guys dont want to use xen? :)
[20:30] <bdmurray> slangasek: I've about 24 open bug reports where update-initramfs has failed due to lack of space and plan to open a new bug suggesting that update-initramfs should deal with this better (make the existing ones duplicates of that new one)  and write a bug pattern to prevent further reports.  Does that seem reasonable?
[20:31]  * Daviey looks
[20:32]  * Daviey is not having with oneiric desktop atm
[20:34] <Daviey> zul: is xenstore needed as a build dep?
[20:34] <zul> Daviey: yeah it pulls it in when you install libxen-dev
[20:34] <Daviey> ah
[20:34]  * micahg thought libxenX was renamed libxenstoreX
[20:41] <nxvl> cjwatson: ping
[20:41] <cjwatson> nxvl: yes?
[20:42] <nxvl> cjwatson: did you have somewhere a magic regexp that will match a valid ubuntu version?
[20:43] <cjwatson> nxvl: define "valid ubuntu version"?
[20:43] <nxvl> cjwatson: 0.8.4-1ubuntu2stuff4 will facil
[20:44] <nxvl> cjwatson: however 0.8.4-1ubuntu2 or 0.8.4-1 will pass
[20:44] <cjwatson> I don't understand why the first should fail
[20:44] <nxvl> cjwatson: because the use case i need, should fail
[20:44] <cjwatson> I do not have a magic regexp that matches requirements I do not have. :-)
[20:44] <nxvl> cjwatson: ok, thanks!
[20:46] <cjwatson> from Ubuntu's point of view, valid version numbers are those defined in policy 5.6.12, and version numbers with the substring 'ubuntu' inhibit autosync from Debian; that'sal
[20:46] <cjwatson> *that's all
[20:48] <nxvl> cjwatson: that will help, you surely have that on a regexp in a script somewhere, right?
[20:50] <cjwatson> buried in the archive somewhere, I can't remember when I last had to care
[20:50] <Daviey> the secret sauce. :)
[20:50] <cjwatson> re_valid_version = re.compile(r"^([0-9]+:)?[0-9A-Za-z\.\-\+~:]+$")
[20:50] <cjwatson> says Launchpad
[20:52] <nxvl> cjwatson: awesome!, thank you!
[20:52] <cjwatson> (that's in lib/lp/archiveuploader/utils.py)
[20:53] <slangasek> bdmurray: sounds great to me!
[20:53]  * nxvl HUGS cjwatson 
[20:57] <bdmurray> cjwatson: I found an announcement about not ps3 isos for natty was there a similar one for powerpc isos?
[20:57] <cjwatson> powerpc ISOs were never stopped
[20:57] <cjwatson> they weren't *released* because they didn't get tested, but the daily builds are still going
[20:58] <bdmurray> ah, thanks!
[21:00] <jdstrand> zul, Daviey: fyi, libxen-dev and libxenstore3.0 (and 'xen' source) have been promoted and I uploaded libvirt 0.9.1-1ubuntu4
[21:00] <zul> jdstrand: cool thanks
[21:00] <jdstrand> zul: fyi, one of the two patches can be dropped in 0.9.2, but the other not until 0.9.3 (see the cahngelog)
[21:01] <jdstrand> zul: ie, of the 2 I just uploaded
[21:01] <zul> jdstrand: gotya
[21:15] <Daviey> jdstrand: rocking!
[22:43] <poolie> mterry, hi, i haven't touched librsync for a long time
[22:44] <poolie> idon't know if it's very active at all
[22:44] <mterry> poolie, that's what I've gathered.  Last comment by an ex-maintainer was 2006
[22:45] <mterry> poolie, was in reference to a MIR (deja-dup->duplicity->librsync)
[22:45] <mterry> poolie, seems stable, just unmaintained
[23:09] <poolie> yeah, pretty much stable
[23:09] <poolie> i'd kind oflike to do something on it
[23:09] <poolie> i'm sure there is room for improvement, but not many bugs
[23:09] <poolie> remarkably few actually
[23:29] <bdmurray> slangasek: so there are a lot of dist-upgrades with this error too but update-manager has its own free space calculator for /boot.  I think those should probably be a separate bug.  Do you agree?
[23:32] <slangasek> bdmurray: the two bugs being 1) poor error message when you're out of space, 2) update-manager's free space calculator needing help?
[23:32] <bdmurray> slangasek: right - it looks to like update-manager just uses the following
[23:33] <bdmurray> KERNEL_INITRD_SIZE = 19 * 1024 * 1024
[23:33] <bdmurray> 19 seems kind of random to me
[23:34] <slangasek> heh, yes
[23:36] <broder> i don't know...
[23:36] <broder> ebroder@warwick:~$ ls -lh /boot/initrd.img-2.6.38-8-generic  | awk '{print $5}'
[23:36] <broder> 20M
[23:37] <broder> though i've thrown a bunch of random crap into my initrd
[23:37] <broder> looks like stock natty is 13M or so
[23:40] <slangasek> well, a much better predictor would be to check the size of the initrd for the current kernel
[23:41] <broder> yeah, sure. i was just surprised how close mine was to the magic number :)
[23:49] <directhex> how frequent is the pull from debian unstable?
[23:49] <cjwatson> daily
[23:50] <cjwatson> assuming I'm around anyway
[23:50] <cjwatson> (it's a cron.cjwatson kind of thing)
[23:50] <cjwatson> why, are you looking for something in particular?
[23:51] <directhex> cjwatson: i've been uploading fixes to sid which ought to also apply to the mono transition in oneiric
[23:51] <directhex> i wondered what time the cronjob runs, so i can check the ben page for added green ticks
[23:51] <cjwatson> right, it's not a cron job, it's "Colin usually runs this when he starts work in the morning"
[23:51] <cjwatson> I can run it now if you'd like
[23:52] <directhex> no, don't do it on my account. that's close enough to a number
[23:52] <directhex> i'm busy migrating from ejabberd to prosody tomorrow anyway, hopefully it means i won't have time to look at non-work things in work hours
[23:53] <cjwatson> actually, I think I'll do one now anyway - with the exception of powerpc, the buildds are fairly quiet and it's good to space things out so that they're more responsive when people need them
[23:55] <cjwatson> typing screen commands into firefox is not helpful
[23:57] <directhex> note to self: do packagecraft after less wine.