=== med_out is now known as med
=== med is now known as medberry
=== beerlogger is now known as winelogger
=== medberry is now known as med_out
[07:50] <dholbach> good morning
[08:09] <poolie> hi dholbach
[08:10] <dholbach> hey poolie
[08:14] <jmarsden> Who might know the status of the SAN upgrade that should provide more disk space for the Ubuntu ISO build machines, and so allow Lubuntu to use that build infrastructure this cycle?  Per UDS discussion this was going to happen "in a few weeks"... I don't know how to get updated status :)
[08:18] <micahg> dholbach: ^^
[08:19] <dholbach> micahg, no idea
[08:19] <dholbach> cjwatson or pitti might know - I never even heard of this being a problem
[08:20] <Rhonda> Someone good a good tool for producing a screencast? istanbul somehow is dysfunctional for me, recordmydesktop only is in sync when setting frame rate to 2 per second, …
[08:20]  * Rhonda . o O ( Rhonda: please ask in #ubuntu, this is off-topic here )
=== hannesw__ is now known as hannesw
[08:21] <dholbach> Rhonda, talk to popey or duanedesign in #ubuntu-community-team
[08:26] <jmarsden> dholbach: Thanks, I'll email cjwatson.  It is needed for Lubuntu to become really really "official" as a Ubuntu variant... or that was my understanding from the UDS session about https://blueprints.launchpad.net/ubuntu/+spec/other-lubuntu-o-integrate-ubuntu-ecosystem
[08:32] <dholbach> jmarsden, awesome - I'm sorry for not being more helpful, but I don't know anything about CD image creation
[08:53] <Laney> morning
[08:53] <micahg> hi Laney
[09:21] <cjwatson> jmarsden: it's making progress - hardware's been installed, waiting for a sysadmin to provision the storage, last I heard
[09:22] <StevenK>  /win 22
[10:14] <hrw> hi
[10:15] <hrw> if package got built and 'some binary packages for this source are not yet published in the repository.' is visible then it means that someone has to check and accept NEW binary packages? (source one passed NEW already)
[10:20] <geser> yes, someone == archive admin
[10:21] <geser> you can see the queue at https://launchpad.net/ubuntu/oneiric/+queue
=== winelogger is now known as omglogger
[10:37] <hrw> 12 NEW binary packages. nice set
[10:37] <hrw> 18 when amd64 and i386 counted
[10:51] <jtaylor> why is the latest thunderbird update a security update? https://launchpad.net/ubuntu/+source/thunderbird/3.1.10+build1+nobinonly-0ubuntu0.11.04.2
[10:51] <jtaylor> seems purely cosmetic
[10:54] <Laney> micahg: chrisccoulson: ^
[10:54] <soren> jtaylor: IIUIC, tt fixes a regression that was introduced in a security update.
[10:54] <micahg> jtaylor: yeah, see http://www.ubuntu.com/usn/usn-1122-3/
[10:55] <jtaylor> ah thx, overlooked the regression tag :/
=== ximion1 is now known as ximion
=== jibel_ is now known as jibel
=== ximion1 is now known as ximion
=== omglogger is now known as transitlogger
[12:34] <Restless> Hello!
[12:34] <Restless> can anybody help with advocating my package?
[12:34] <Restless> I need the second advocate: http://revu.ubuntuwire.com/p/rhash
[12:36] <Restless> (I'm new on the channel, so don't what is the shortest way into distro)
[12:43] <tumbleweed> Restless: this package doesn't look ubuntu-specific, please consider maintaining it in debian, and getting it into Ubuntu that way
[12:47] <Restless> tumbleweed: I'm not too familiar with debian, so it will take longer time
[12:49] <evaluate> Restless, if your package builds fine under ubuntu and doesn't depend on any ubuntu specific packages (which I don't think is the case for your application), it should have a fairly high chance of building fine in Debian too.
[12:51] <evaluate> You will need a couple of changes in the debian/changelog and possibly a couple of other places, but the rest should be fine. You then just need a mentor that uploads your package to the Debian repo and you're done. :-)
[12:51] <tumbleweed> Restless: we don't encourage bringing new packages into Ubuntu through REVU. Debian is better suited to maintaining most packages, as packages have explicit maintainers. In Ubuntu packages that nobody cares about can go unnoticed and uncared for for a long time
[12:52] <Restless> evaluate: I possibly need to install debian, get familiar with their bug-tracking and so on... :)
[12:53] <evaluate> Restless, yeah, you would need a sid box for building your package, but you could also use a VM or a chroot. Also, http://www.debian.org/doc/manuals/maint-guide/ should give you most of the information you need to know about packaging for Debian.
[12:55] <Restless> evaluate: ok, sounds like a plan
[12:55] <evaluate> Restless, also, for bugs there is 'reportbug', which is fairly easy to use IMHO, and the BTS itself isn't too complicated either.
[12:55] <Laney> the BTS is fine once you get used to it
[12:55] <Laney> I probably prefer it to malone
[12:59] <geser> for bug filing in Debian using reportbug is ok, but when I want to attach a patch, I find LP easier to use (unless I didn't figure out an easy workflow for it yet)
[12:59] <hrw> geser: reportbug allows to add patch
[12:59] <geser> hrw: to an existing bug?
[12:59] <hrw> geser: mailto:BUGNUMBER@bugs.debian.org?
[13:00] <evaluate> geser, there are also emails, y'know?
[13:00] <hrw> geser: attach patch to mail and done
[13:00] <hrw> geser: Debian BTS is mail centric
[13:00] <Laney> or bts --mbox show bugno if you want to reply to a specific mail
[13:01] <evaluate> geser, http://www.debian.org/Bugs/server-control might help...
[13:02] <geser> I know, but I need to remember to write a proper subject (for the maintainer who gets the mail; or copy&paste it from the existing bug), don't forget to really attach the diff to the mail when writing some explanation and perhaps even download the mbox for proper threading (I like to be nice to the maintainer)
[13:04] <Restless> evaluate: what debian version do I need to install?
[13:05] <Laney> you can make an unstable chroot
[13:05] <Restless> is debian-6.0.1a-*.iso ok?
[13:05] <evaluate> Restless, your package will first go into debian sid (also known as unstable) so you should best build against that one.
[13:06] <Laney> if you want a full install then get a testing image and upgrade it to unstable
[13:06] <evaluate> Restless, you can theoretically install any version and then just point your sources.list file to sid and do an upgrade (or dist-upgrade)
[13:06] <Restless> ok, I'll try http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-dvd/debian-testing-amd64-DVD-1.iso
[13:07] <Laney> you might want to use the net installer to download less stuff
[13:07] <Restless> sound better :)
[13:07] <tumbleweed> geser: bts --mbox show (it's awesome)
[13:07] <Laney> tumbleweed: beat you to that :-)
[13:07] <Laney> and yes it is great
[13:07] <geser> will try it out the next time
[13:07] <tumbleweed> Laney: he didn't seem to listen to you :)
[13:07]  * Laney sulks
[13:08] <Laney> what MUAs does that work with?
[13:08] <tumbleweed> mutt works well, obviously
[13:08] <Laney> that is all i've ever used it with
[13:08] <tumbleweed> I guess anything that you can feed an mbox to
[13:12] <Laney> wonder which ones those are
[13:16]  * ScottK would imagine any that run on *nix can read an mbox.
[13:20] <tumbleweed> there is of course a difference between being able to read an mbox and making it easy to view a random mbox. For many you'd probably have to "import" the mbox, even if it used mbox storage internally
[13:21] <Laney> indeed, it has to be able to take it on the commandline for this interface to work
[13:33]  * ScottK would have imagined wget + import would work, but OK.
[13:34] <Laney> does, but mildly more cumbersome
[14:14] <ScottK> chrisccoulson: You are TIL mongodb.  It needs to get off of boost1.42 and onto 1.46.  Debian has a much newer version.  Would you please look into updating it to the newer boost?
[14:33] <chrisccoulson> ScottK, is it urgent? i can take a look at it when i get some free time, but i only ever worked on mongodb before to port it to a newer jsapi
[14:33] <ScottK> chrisccoulson: Not urgent.
[14:33] <chrisccoulson> ok, that's fine then :)
[14:33] <ScottK> You might talk SpamapS into it.  IIRC he has some interest.
[15:30] <Laney> lucas: hey, how do you populate upload_* in UDD? Directly fed from somewhere or parsing -changes@?
[15:30] <Laney> (I'd quite like to add ubuntu counterparts for a DEX thing)
[15:30] <lucas> Laney: parsing of list archives
[15:31] <Laney> excellent
[15:31] <Laney> I'll likely be able to repurpose it then
[15:31] <lucas> would the DEX infra rely on UDD, or are you setting up something separate ?
[15:31] <Laney> it's just a query I want to run at the minute
[15:32] <Laney> measuring ubuntu uploads relative to debian
=== Rushless is now known as Restless
[15:34] <Laney> but I figure it may be more generally useful, hence wanting to smush it into UDD
[15:49] <tumbleweed> Laney: hrm, any chance of importing ubuntu upload history? that would be really handy for determining sponsorship
[15:50] <Laney> tumbleweed: yeah, that's what I was talking about
[15:50] <Laney> but what do you mean?
[15:51] <tumbleweed> Laney: list-sponsorships in lp:~stefanor/ubuntu-dev-tools/extra-scripts
[15:51] <Laney> quick summary?
[15:53] <tumbleweed> endorsements: it generates a list of sponsorships that you've done for someone. Also theoretically useful for sponsorees wanting to find who to contact for endorsements.
[15:53] <Laney> ah ok
[15:53] <tumbleweed> currently scrapes -changes archives, but a UDD table would make it a lot faster
[15:53] <Laney> shouldn't be too hard to do
=== cyphermox_ is now known as cyphermox
=== ximion1 is now known as ximion
=== ximion1 is now known as ximion
[18:14] <micahg> ScottK: chrisccoulson: I was going to take mongodb, but it needs porting to mozjs185, I also was going to as the Debian folk why they're using xulrunner-dev instead of libmozjs in Debian
[18:14] <micahg> *ask
[18:14] <chrisccoulson> i thought i already did mongodb?
[18:14] <micahg> chrisccoulson: it's ported to xulrunner 2.0 IIRC
[18:15] <chrisccoulson> ah, ok. that's probably 99% of the way there already then
[18:15] <micahg> chrisccoulson: yeah, it is
[18:16] <micahg> I'll try an actual merge over the weekend (short week this week)
[18:17] <micahg> chrisccoulson: unless you actually want to do it :), I figure you have a lot of other stuff you're working on
[18:17] <chrisccoulson> yeah, i've got a lot of other stuff to do first ;)
=== makl is now known as ximion
=== ximion1 is now known as ximion
[20:14] <jtaylor> concerning https://bugs.launchpad.net/ubuntu/+source/tahoe-lafs/+bug/782461
[20:14] <ubottu> Ubuntu bug 782461 in tahoe-lafs (Ubuntu) "too high version dependency on pycryptopp" [Undecided,New]
[20:15] <jtaylor> is it possible to upgrade pycryptopp via -updates, it only has two depends, one of which is broken by the current version
[20:15] <jtaylor> the current upstream is 12 releases newer than the debian pacakge, so I guess this would never be approved?
[20:18] <micahg> jtaylor: its only rdepend is tahoe-lafs, so that could probably be ok, what's the diff between the versions?
[20:19] <micahg> IANA ubuntu-sru member :)
[20:20] <jtaylor> 373 files changed, 83419 insertions(+), 76662 deletions(-)
[20:23] <micahg> jtaylor: oh, fun...
[20:23] <micahg> jtaylor: let's get it in oneiric first :)
[20:24] <micahg> preferably through Debian
[20:24] <jtaylor> I asked the maintainer to do so a month ago ._.
[20:27] <tumbleweed> jtaylor: considering the last 3 uploads were team uploads, I think you can add yourself to uploaders and go for it
[20:27] <tumbleweed> (assuming you'll be caring about it in the future)
[20:30] <jtaylor> I don't
[20:30] <tumbleweed> well just team upload it then
[20:30] <jtaylor> I jsut got drawn into it as tahoe is a rdep of one of my packages
[20:35] <jtaylor> oh nice, POX already started packaging the new version in svn
=== yofel_ is now known as yofel
=== jtechidna is now known as JontheEchidna
=== medberry is now known as med_out