=== Guest60473 is now known as medberry
=== almaisan-away is now known as al-maisan
[05:31] <micahg> tumbleweed: the botan1.8 upload should've been 1.8.13-1ubuntu0.1 instead of 1.8.13-1.1
[05:41] <micahg> 1.8.13-1.1 makes it look like a Debian upload
[06:11] <micahg> ScottK: when you get a chance bug 877074 looks fine to me, no rdepends except a suggests
[06:11] <ubottu> Launchpad bug 877074 in Oneiric Backports "Please backport workrave 1.9.4-2 to oneiric" [Wishlist,Confirmed] https://launchpad.net/bugs/877074
=== al-maisan is now known as almaisan-away
[07:01] <dholbach> Guten Morgen Berlin! :)
[08:04] <tumbleweed> micahg: thanks, /me blames dch
[08:05] <micahg> yep, makes sense
=== almaisan-away is now known as al-maisan
[09:28] <Laney> morning
[09:29] <Laney> today I try in earnest to recover from the lurgy before Saturday
[09:40] <nigelb> Laney: Flying out Saturday?
[09:40] <Laney> yep
[09:40] <nigelb> Nice.
[09:40] <nigelb> I'll miss you all.
[09:42] <Laney> :(
[09:42] <Laney> we need some nigelb!
[09:57] <nigelb> Laney: heh
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
[11:30] <cjwatson> Laney: beer helps with the lurgy </lie>
[11:41] <Rhonda> Laney, you had an issue with a changelog link from the packages site. Which package was that again?
[11:56] <Laney> Rhonda: I don't remember :( It was something to do with .../changelog (or .../package.changelog) not always existing, possibly to do with multiple binary packages
[11:57] <Rhonda> It might be that it was with an .xz compressed upstream tarball and too old dpkg-dev on the extraction host (which though isn't under my umbrella)
[11:58] <Rhonda> We noticed this issue with packages.debian just recently
[12:07] <AnAnt> Hello, is precise sync'ing from testing or unstable ?
[12:12] <\sh> AnAnt, testing
=== al-maisan is now known as almaisan-away
[12:30] <aboudreault> Hi ppl!
[12:33] <aboudreault> I currently build my packages in a VM (OpenVZ) of ubuntu lucid. I'm using cowbuilder right now. Unfortunately... I cannot build any packages for Debian SID (Unstable) since it is now multi-arch and things do not work anymore. Not sure why exactly.
[12:33] <aboudreault> I want to build another virtual machine on my laptop using LXC. Do you have a setup to recommend me?
[12:33] <aboudreault> is cowbuilder still the tool to use?
[12:52] <pmjdebruijn> aboudreault: doesn't cowbuilder build a chroot?
[12:52] <pmjdebruijn> each chroot has it's own libs, so multiarch shouldn't matter right
[12:52]  * pmjdebruijn might be completely wrong
[13:04] <aboudreault> pmjdebruijn, yes
[13:04] <aboudreault> pmjdebruijn, I'm getting this error:
[13:05] <aboudreault> http://pastebin.com/NR53n7PG
[13:05] <aboudreault> can't update/create new env anyhow
[13:05] <aboudreault> it might be not related to multi-arch etc.... but all other env works. (ubuntu)
[13:05] <aboudreault> and sid worked before.
[13:32] <pmjdebruijn> odd indeed
[13:40] <cjwatson> aboudreault: what does 'uname -r' say?
[13:40] <aboudreault> 2.6.24-28-openvz
[13:40] <cjwatson> aboudreault: then the message means exactly what it says and this has nothing to do with multiarch
[13:41] <cjwatson> "WARNING: this version of the GNU libc requires kernel version 2.6.26 or later"
[13:41] <cjwatson> that isn't the lucid kernel, it's from hardy
[13:42] <aboudreault> I don't think openvz is in lucid
[13:42] <cjwatson> I'm afraid you can't run sid on that kernel
[13:42] <aboudreault> ok, fine then... it should work properly in a new LXC vm.
[13:42] <cjwatson> yep
[13:42] <aboudreault> thanks for pointing that!
[13:42] <aboudreault> I thought this message was related to INSIDE the chroot.
[13:43] <cjwatson> well, it is
[13:43] <cjwatson> it relates to the libc inside the chroot and the running kernel installed outside the chroot
[13:43] <aboudreault> yeah
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
=== yofel_ is now known as yofel