[00:06] <Keybuk> slangasek: it's making patches now
[00:11] <slangasek> woohoo
[00:11] <Keybuk> don't know whether this is good or not
[00:11] <Keybuk> next she makes merges
[00:11] <Keybuk> then cookies
[00:20] <cowgarden> hi, why is there a new add/remove software dialog? (where are the advantages? I'm just missing the ratings which makes it useless for aimless lurking arround)
[00:21] <maco> yeah, lots of complaints about lack of ratings. its not done yet ;-)
[00:22] <maco> !softwarecenter
[00:22] <maco> boo!
[00:22] <maco> cowgarden: https://wiki.ubuntu.com/SoftwareCenter
[00:22] <cowgarden> but it will come I read from that :)
[00:22] <cowgarden> thank you!
[00:22] <cowgarden> 9.10 should boot faster, shouldn't it?
[00:23] <cowgarden> and how strict is the feature freeze, can I expect smaller features coming through updates or will there be bugfixes fpr 9.10 only?
[00:25] <Keybuk> cowgarden: 9.10 is done
[00:25] <Keybuk> out
[00:25] <Keybuk> finished
[00:25] <cowgarden> I know
[00:25] <Keybuk> you can this, because it's now November
[00:25] <Keybuk> and then it'd be Ubuntu 9.11
[00:25] <directhex> cowgarden, short version: very limited developer resources, devs like new & shiny, not arguing with the bureaucracy to get backports into old releases
[00:25] <Keybuk> which would upset people
[00:25] <Keybuk> ;)
[00:26] <cowgarden> ok :)
[00:26] <cowgarden> thank you
[00:26] <Keybuk> we only update releases with critical bug fixes and security fixes
[00:26] <Keybuk> (mostly)
[00:26] <directhex> cowgarden, new features in released releases are Bad(tm) - e.g. SLES10 changed its entire software update management stack twice now since release
[00:26] <cowgarden> and the "new software for easy application development" which one is that?
[00:27] <directhex> and their kernels have totally changed how they treat some devices
[00:27] <cowgarden> %/
[00:27] <directhex> cowgarden, probably "quickly" - although i like monodevelop personally for such things ;)
[00:28] <cowgarden> directhex, so which are the "fun, speedy and easy" tools?
[00:29] <directhex> Keybuk, don't think i can promise you more than a meg (if that) shaved off this release. still, 25% drop between intrepid & karmic
[00:29] <directhex> cowgarden, "quickly" is what the cool kids are talking about in that context
[00:30] <cowgarden>  directhex oh, thats the name *laughing*
[00:30] <Keybuk> directhex: a meg?
[00:31] <Keybuk> directhex: I'm missing context
[00:31] <directhex> Keybuk, I think we've pretty much exhausted ways to make f-spot/tomboy smaller on disk. intrepid->jaunty was 6 meg smaller, jaunty -> karmic was 6 meg further still
[00:32] <Keybuk> oh, I don't care about that ;)
[00:32] <Keybuk> I just want to see Mono to shared libraries in shared memory properly ;)
[00:55] <slangasek> Keybuk: how long should the MoM run be expected to take?
[00:55] <Keybuk> slangasek: usually a week ;)
[00:56] <slangasek> hmm
[00:56] <Keybuk> I've short-cutted some bits
[00:56] <slangasek> heh, ok
[00:56] <Keybuk> so a few days maybe
[00:56] <Keybuk> I've never had to restart it based on a whole new distribution before
[00:57] <slangasek> fwiw, I don't think it would have hurt to pick up where last cycle's unstable left off, assuming the code could handle that (i.e., the possibility of some packages going backwards at the source)
[02:41] <Keybuk> slangasek: https://merges.ubuntu.com/main.html
[02:43] <Keybuk> universe looks like it is genuinely days away
[05:20] <d3matt> hello
[05:20] <d3matt> anyone know the file format of the initrd.gz file?
[05:22] <geofft> it's a gzipped cpio archive, but... why?
[05:22] <d3matt> doesn't appear to be
[05:23] <geofft> (mkdir /tmp/initrd; cd /tmp/initrd; gunzip < /initrd.gz | cpio -id)
[05:23] <geofft> er, initrd.img. I assume initrd.gz is the same
[05:23] <d3matt> I get "not in gzip format"
[05:23] <d3matt> this is from the 9.10 live cd
[05:24] <d3matt> tried installing it to a USB key and it's looking to mount /dev/sr0
[05:24] <d3matt> was gonna dig into the init script but can't seem to find out how to extract the thing
[05:24] <geofft> I don't actually know if this changed in 9.10 but I'd be surprised. what does the file command say?
[05:24] <d3matt> date
[05:24] <d3matt> data*
[05:24] <geofft> er, you're aware of the magic bootable USB stick creator that uses a live CD, no?
[05:24] <wgrant> It's even on the live CD.
[05:24] <d3matt> yea
[05:24] <d3matt> usb-creator
[05:24] <d3matt> used the 9.04 one...
[05:26] <d3matt> I don't **have** to use a usb key, but I kinda like it
[06:03] <slangasek> Keybuk: yaaaaay thanks
[07:14] <\sh> moins
[07:25] <kees> slangasek: why do buildN packages show up in MoM?  shouldn't they auto merge?
[07:26] <ScottK> kees: They do, but until they are sync'ed they show up
[07:26] <kees> oh! okay.
[07:32] <\sh> MOM showing diffs between testing and lucid now? or still sid ?
[07:35] <ogra> testing
[07:39] <\sh> ogra, thx mate...starting up the engines ;)
[07:39] <ogra> :)
[07:44] <crypt-0> on upgrade fom 9.04> 9.10 : $ amarok
[07:44] <crypt-0> amarok: symbol lookup error: /usr/lib/libamaroklib.so.1: undefined symbol: _ZTIN6TagLib3MP44FileE
[07:44] <crypt-0> any idea to what the problem is?
[07:44] <crypt-0> i have seen it in a mailing list, but no solutions.
[07:47] <tsimpson> crypt-0: you seem to be missing libtag1c2a (which amarok depends on)
[07:48] <crypt-0> seem to be  however that is not the prolem.
[07:48] <tsimpson> well, that's where the symbol is defined
[07:48] <crypt-0> libtag1c2a is already the newest version.
[07:48] <tsimpson> then you're missing /usr/lib/libtag.so.1 and or /usr/lib/libtag.so.1.6.0
[07:48] <crypt-0> (and yes i ran apt-get update)
[07:48] <tsimpson> which are part of that package
[07:49] <crypt-0> strange why wouldn it be in the package?
[07:50] <tsimpson> well libtag1c2a depends on libtag1-vanilla or libtag1-rusxmms
[07:50] <tsimpson> and the lib is in both
[07:51] <tsimpson> I guess make sure one of them is installed, should be libtag1-vanilla by default I think
[07:51] <crypt-0> $ sudo touch /usr/lib/libtag.so.1.6.0
[07:51] <crypt-0> $ sudo touch /usr/lib/libtag.so.1
[07:52] <crypt-0>  
[07:52] <crypt-0> they are both intact.
[07:52] <crypt-0> libtag1-vanilla is already the newest version.
[07:52] <nxvl> hey, got some stupid packaging question
[07:52] <tsimpson> "nm -D /usr/lib/libtag.so.1.6.0 |grep _ZTIN6TagLib3MP44FileE" should output something like "0008e88c V _ZTIN6TagLib3MP44FileE"
[07:52] <nxvl> using cdbs and patchsys-quilt, what goes first, the patching, or the pre-build?
[07:53] <crypt-0> i dont know why the egacy"version of amarok is not supported.
[07:54] <crypt-0> 0008e88c V _ZTIN6TagLib3MP44FileE
[07:54] <tsimpson> nxvl: patch, then pre-build (configure et all)
[07:54] <crypt-0> and by the way, the upgrade broke  the wine package , however i do not care for it.
[07:55] <nxvl> tsimpson: mmm, ok, thank you
[07:56] <tsimpson> crypt-0: make sure "ldd /usr/bin/amarok" shows the the libs under /usr/lib
[07:56] <tsimpson> crypt-0: amarok (and wine) work here
[07:56] <siretart`> morning
[07:56] <nxvl> siretart`: night :D
[07:57] <siretart`> :)
[08:01] <nxvl> tsimpson: just re-checked, and it's the other way, first pre-build, then patch
[08:01] <nxvl> :S
[08:02] <tsimpson> it should be the other way round
[08:02] <tsimpson> unpatch should be before clean
[08:03] <nxvl> dunno, i'm trying to run some code in pre-build, that needs a patch to be applied and getting en error
[08:03] <nxvl> just checked and i get the code running before the patch is applied
[08:04] <nxvl> asac: ping
[08:24] <crypt-0> tsimpson, "ldd /usr/bin/amarok" shows all the libs
[08:24] <tsimpson> all in /usr/lib too?
[08:25] <crypt-0> http://pastebin.com/m63f5f5b
[08:26] <crypt-0> mostly under /usr/lib....
[08:27] <tsimpson> libtag.so.1 => /usr/local/lib/libtag.so.1
[08:27] <tsimpson> not in /usr/lib ;)
[08:27] <pitti> Good morning
[08:27] <geser> Guten Morgen pitti
[08:33] <crypt-0> $ ls /usr/lib/|grep tag
[08:34] <tsimpson> crypt-0: /usr/local/lib comes before /usr/lib when searching for libraries
[08:34] <crypt-0> http://pastebin.com/m2f2eb8a0
[08:34] <tsimpson> so /usr/local/lib/libtag.so.1 is being picked up before /usr/lib/libtag.so.1
[08:44] <dholbach> good morning
[08:51] <ikonia> morning
[08:52] <slangasek> kees: they should, dunno
[08:52] <slangasek> kees: which package (to confirm sync-source /is/ merging it)?
[09:03] <dholbach> james_w: you think we can move the DistributedDevelopment/Merging to UbuntuDevelopment/Merging?
[09:03] <dholbach> james_w: or at least add it in there?
[09:18] <kees> slangasek: specifically sharutils, but there are a ton in universe -- I will assume it's just not caught up yet
[09:23] <slangasek> kees: well, autosyncing is happening very slowly for the first pass; I have to keep restarting it because of all the orig.tar.gz mismatches that haven't been declared in the blacklist file yet
[09:24] <kees> ah, fun
[09:24] <kees> the testing vs unstable thing is going to throw me for a bit too
[09:25] <slangasek> someone definitely goofed somewhere, for the packages to be in a needs-sync state, but with mismatched orig.tar.gz that's not already documented in the blacklist from last time
[09:27] <dholbach> oh and james_w:
[09:27] <dholbach>  _   _    _    ____  ______   __  ____ ___ ____ _____ _   _ ____    _ __   ___
[09:27] <dholbach> | | | |  / \  |  _ \|  _ \ \ / / | __ )_ _|  _ \_   _| | | |  _ \  / \\ \ / / |
[09:27] <dholbach> | |_| | / _ \ | |_) | |_) \ V /  |  _ \| || |_) || | | |_| | | | |/ _ \\ V /| |
[09:27] <dholbach> |  _  |/ ___ \|  __/|  __/ | |   | |_) | ||  _ < | | |  _  | |_| / ___ \| | |_|
[09:27] <dholbach> |_| |_/_/   \_\_|   |_|    |_|   |____/___|_| \_\|_| |_| |_|____/_/   \_\_| (_)
[09:27] <dholbach>                                                                                
[09:28] <pitti> ooh! /me hugs james_w; happy birthday!
[09:32] <seb128> james_w, happy birthday
[09:33]  * dholbach hugs james_w too
[09:39] <\sh> james_w, congrats :) and nice work on the merging bzr stuff
[09:45] <nxvl> james_w: Happy Bday!
[09:50] <nxvl> cjwatson: happy bday to you aswell!
[09:51] <Laney> greetings to all oldies
[09:57] <siretart`> james_w: congratulations from my side as well!
[10:05] <jpds> james_w, cjwatson: Happy birthday!
[10:09] <davmor2> james_w: happybirthday dude
[10:09] <davmor2> oh and cjwatson
[10:17] <siretart`> oh collin as well? Congrats!
[10:17] <wgrant> slangasek: ISTM that sync-source.py shouldn't really crash when it finds a mismatch.
[10:29] <slangasek> wgrant: well, hmm; that's an idea :)
[10:49] <dholbach> happy birthday cjwatson! :)
[11:01] <mjr> where're the gnome-panel default applets configured?
[11:06] <geofft> /usr/share/gconf/defaults, I believe, which update-gconf-defaults turns into /var/lib/gconf/debian.defaults
[11:07] <mjr> right, there...
[11:08] <mjr> oh, debian.defaults indeed, I'll just mention that at least on 8.10 it appears to generate debian.defaults as world-unreadable if umask is 077, probably not ideal for when system umask is set that way...
[11:10] <pitti> did anyone else already use summit.u.c.? I can't dnd blueprints to the per-track view, just to the per-day view (but there I don't know which room to take)
[11:11] <geofft> mjr: that seems poor. but then, I'm vaguely impressed if that's the only thing that breaks
[11:15] <ion> dpkg probably should use umask 022 for all maintscripts.
[11:19] <Chipzz> happy birthday cjwatson! :)
[11:31] <vrodic> hello guys. I'm thinking about joining in for lucid. by testing the distro on various hardware at some point. which point would that be? during the developer sprint? earlier?
[11:31] <vrodic> where to propose additional drivers/pieces of firmware?
[11:34] <pitti> vrodic: the best time for testing are the alpha and beta releases
[11:37] <vrodic> pitti: thanks. i have another question about drivers. some hardware doesn't work without firmware, however, nowhere in the new 9.10 GUI can I find information that I should install a certain firmware package. are there any changes planned for that?
[11:37] <pitti> vrodic: we have some coverage in system -> admin -> hardware drivers
[11:37] <dholbach> the seahorse-agent bug is getting a bit out of control :)
[11:38] <dholbach> bug 467175
[11:38] <dholbach> err
[11:38] <vrodic> pitti: i know, but not about this particular broadcom b43 wlan card
[11:39] <vrodic> pitti: i'm not sure if there is a system to make the kernel notify the userspace about missing firmware, other than parsing the kernel logs, which seems ugly
[11:39] <pitti> there is no hotplug support yet
[11:39] <pitti> you have to call it manually, or have the device plugged in after first installation
[11:39] <pitti> s/after/at/
[11:40] <vrodic> pitti: this is not hotplug, this is a device that sits in the system all the time
[11:41] <vrodic> regarding the keychain management, i got bitten by that and i think that the keychain dialogs should include a "don't ever ask me for a password for this type of operation again"
[11:42] <vrodic> pitti: do you understand my scenario?
[11:44] <pitti> vrodic: yes, but not the details why it fails for you; please run it once and do "ubuntu-bug jockey-gtk", this will attach the necessary debug information
[11:47] <vrodic> pitti: does this command need the network? should I remove the firmware files before i do this? because I've got it working by manually installing b43-fwcutter package
[11:47] <pitti> vrodic: ubuntu-bug needs network, yes; jockey needs network for downloading the package and firmware
[11:50] <vrodic> pitti: okay, should i then remove the b43-fwcutter package, and run ubuntu-bug jockey-gtk? i'll connect it with ethernet cable
[11:51] <pitti> vrodic: that, and /lib/firmware/b43
[11:51] <pitti> vrodic: if the firmware is present, the driver will be shown as "enabledZ"
[11:51] <pitti> vrodic: but if your problem is that the driver doesn't appear at all in jockey, you don't need to remove anything
[11:51] <vrodic> okay, i'll do it now and let you know
[11:51] <pitti> vrodic: it should just show it as "enabled" for you
[11:53] <vrodic> pitti: the driver appears in jockey, but after i manually install it :)
[11:53] <pitti> vrodic: ok, then please remove firmware and package
[11:54] <vrodic> doing that now.
[11:58] <vrodic> pitti: alright i cant reproduce it anymore, maybe it got fixed when i did apt-get update, or where does jockey store the driver/hardware database?
[12:06] <geofft> I'm kind of disappointed patches.ubuntu.com isn't clever enough to compare firefox to iceweasel
[12:07] <dholbach> geofft: fix it: https://code.launchpad.net/merge-o-matic :)
[12:14] <pitti> vrodic: immediately after installation you won't see it; you first need to do an apt-get update (or wait until the cron job does it)
[12:14] <pitti> vrodic: that's a known bug
[12:14] <vrodic> pitti: okay great, where can i vote for it ?:)
[12:18] <vrodic> or whats the bug number?
[12:21] <pitti> vrodic: bug 439530
[12:21] <vrodic> thanks
[12:22] <pitti> siretart`: do you want to merge cryptsetup for lucid? (I need a never version for proper DK-Disks support; our 1.0.6+git snapshot doesn't yet support proper UUIDs)
[12:22] <pitti> or shall I look into merging it?
[12:22] <siretart`> depends how fast you need it. If you can do it before monday, please
[12:22] <siretart`> go for it
[12:23] <pitti> ah, I meant "by alpha-2" or so :)
[12:23] <pitti> I'm not even running lucid yet
[12:23] <siretart`> I've decided to participate early, and already upgraded my notebook to lucid
[12:24]  * pitti still needs to do some karmic SRUs
[12:24] <siretart`> I hope this wasn't a bad decision :)
[12:24] <pitti> siretart`: apw warned that the current lucid kernel has some serious ext4 corruption issues
[12:25] <pitti> siretart`: (and the fixed one doesn't build because of a gcc regression)
[12:25] <pitti> I didn't hear other reports yet
[12:25] <siretart`> the karmic kernel is pretty unusable for intel users. prety bad flickering
[12:26] <siretart`> so I'ver reverted to the karmic kernel
[12:26] <siretart`> for now
[12:28] <apw> siretart`, the ext4 issues are on crash, data can be lost.  the next lucid kernel has the fix but i can't build it
[12:48] <ttx> james_w: trying bzr-merge, I run into "bzr: ERROR: Unknown target distribution: lucid" when trying to mark-uploaded
[12:52] <vrodic> siretart`: what intel chip is not usable on karmic? it works for me on 915 and 945
[14:11] <Keybuk> slangasek: around?
[14:19] <cjwatson> nxvl,jpds,davmor2,siretart`,dholbach,Chipzz: thanks :)
[14:20] <pitti> hey cjwatson; happy birthday!
[14:20] <cjwatson> ta
[14:23] <vrodic> where can i see all nominated bugs for lucid?
[14:30] <Keybuk> cjwatson: sit-rep on MoM: looks like main is up to date
[14:30] <Keybuk> and universe is still catching up
[14:30] <Keybuk> main should be refreshing though
[14:31] <pitti> ooh, MoM back? thanks so much!
[14:31] <cjwatson> neat, thanks
[14:31] <Keybuk> the stuff that sends patches to Debian is down though
[14:31] <Keybuk> and probably will be until the whole v3 nightmare is figured out
[14:31] <Keybuk> now that LP is doing per-upload patches, it may be much simpler to port it over to that
[14:32] <zul> james_w: can you import bacula as well?
[14:37] <cjwatson> Keybuk: I still haven't grasped why 3.0 is a problem, aside from having a new enough dpkg-dev - does it not just use dpkg-source to unpack the packages?
[14:37] <Keybuk> cjwatson: that may be the only problem
[14:37] <Keybuk> I just haven't looked
[14:38]  * cjwatson nod
[14:38] <cjwatson> s
[14:38] <Keybuk> also obviously a package converting from v2 to v3 might have an enormous diff, across which merge-o-matic output isn't useful
[14:38] <Keybuk> but that's no worse than cdbsing a package, etc.
[14:40] <Keybuk> cjwatson: unrelated
[14:40] <Keybuk> I was having a bit of a think
[14:40] <Keybuk> you know GRUB2 has that whole "search" thing?
[14:41] <Keybuk> does it put the result of that anywhere
[14:42] <Keybuk> (other than being the filesystem it looks for kernels on)
[14:44] <cjwatson> Keybuk: it lands in GRUB's 'root' environment variable (or whichever variable you nominate), although right now I don't believe it passes that on to the kernel
[14:44] <cjwatson> and of course the device name inside GRUB has little to do with anything Linux understands
[14:45] <cjwatson> I imagine you could stick grubroot=${root} on the 'linux' line if you wanted to
[14:46] <Keybuk> yeah, that's what I was thinking ;)
[14:46] <Keybuk> if GRUB has already done the hard work, we could bypass initramfs entirely
[14:46] <cjwatson> what would it be useful for?
[14:46] <cjwatson> ah
[14:46] <Keybuk> (non-separate /boot obviously)
[14:47] <Keybuk> but it's a nice way of bypassing the initramfs without hardcoding root=/dev/sda1 ;)
[14:47] <cjwatson> device naming would probably be a killer
[14:47] <Keybuk> hmm?
[14:48] <Keybuk> if you could do root=${grubroottolinux} that'd be fun ;P
[14:48] <cjwatson> enumeration won't be the same
[14:48] <cjwatson> if there's one disk it's easy, obviously :)
[14:49] <Keybuk> wouldn't the device tree stuff partially solve that?
[14:50] <cjwatson> I confess I haven't looked at that
[14:56]  * Keybuk wonders what happens if he phones evand :p
[14:56] <evand> My iPhone melts.
[14:57] <Keybuk> such fun ;)
[15:01] <evand1> argh
[15:01] <evand1> faulty cable, which they can't replace until *the 16th*
[15:02] <Keybuk> evand1: but you're back online now?
[15:02] <evand1> yeah, that's the confusing part
[15:02] <evand1> I imagine not for long
[15:02] <evand1> as it's been up and down the past few days
[15:07] <siretart`> vrodic: I have a GM945, and with the current lucid kernel, I get spontanous but very annoying flickering
[15:07] <siretart`> vrodic:  sometime the screen becomes totally dark, and I need to suspend/resume the laptop to get the screen back
[15:07] <siretart`> very strange
[15:12] <vrodic> siretart`: i'm on debian 2.6.32-rc5 kernel, but i've briefly used karmic without problems. my mothers laptop with 915GM works fine on karmic too. lucid probably has 32-rc kernel with newer intel drm that has some bugs. my 32-rc5 has s2ram broken
[15:13] <vrodic> it's not really that strange that rc version of the kernel has issues, especially if intel drm is concerned
[15:13] <maco> yep -32 is not so happy on my 965 either
[15:33] <astechgeek> stupid question will visual basic work with ubuntu
[15:33] <astechgeek> i got my java stuff working
[15:34] <Chipzz> astechgeek: ask on #ubuntu; and next time, pls read the topic of a channel before asking random questions
[15:34] <maco> no
[15:37] <astechgeek> where would be the app development channel?
[15:37] <maco> AFAIK, there isnt one
[15:38] <Chipzz> there are various channels like #perl etc for various programming languages, but none of those are ubuntu-specific
[15:40] <astechgeek> okay well then I guess thats where I need to be thanks
[15:42] <slytherin> Can someone help me isolate this problem. I was upgrading my laptop yesterday to karmic using update-manager the machine rebooted halfway through upgrade and was in unbootable state (temporarily). How can I find out at the package that caused the problem?
[15:53] <kklimonda> where does sudo dependency in "bare" ubuntu install (for example the one created by debotstrap for pbuilder) come from?
[15:58] <jpds> kklimonda: ubuntu-minimal package?
[15:58] <kklimonda> hmm.. ubuntu-minimal is pulling it in..
[15:58] <kklimonda> jpds: yeah, looks like it
[16:02] <superm1> slangasek, re the fix to bug 441638, i suspect that this will cause some problems with the DKMS auto build of nvidia or fglrx when necessary.  if DKMS isn't done building by the time gdm tries to start, it wont try again I suspect
[16:02] <superm1> only solution that comes to mind will be to convert dkms to an upstart job and emit graphics-device-added or something of that nature
[16:23] <kklimonda> Is /dev/.blkid.tab only created when user uses "blkid" (or some program uses libblkid1) ?
[16:25] <kklimonda> shouldn't it be created empty at "start" so /etc/blkid.tab is pointing to something? right now it's a broken symlink before /dev/.blkid.tab is created.
[16:50] <popey> is there a way to grab the data that "ubuntu-bug foo" captures for manual attachment to a bug, where a machine has no net connection?
[16:50] <popey> there is nothing in /var/crash btw
[16:54] <pitti> popey: for a bug or a crash report?
[16:54] <popey> a bug
[16:55] <pitti> popey: "apport-cli packagename", and select "save report", then move the .apport file to another computer and doubleclick on it
[16:55] <popey> ah awesome
[16:55] <pitti> or say "report" and say "no" to open web brwoser, and c&p the URL
[16:55] <popey> thats great, thanks very much!
[16:55] <pitti> ah, no, you couldn't upload the blob then
[16:55] <pitti> so, first method
[16:56] <pitti> the second is nicer for servers with network, but no fancy browser
[16:57] <gigabytes> hello
[16:57] <gigabytes> anybody from the mactel support team here?
[16:57] <gigabytes> I've asked some days ago to join the launchpad team but no response yet
[17:44] <pitti> bigon: would you mind applying http://launchpadlibrarian.net/31716020/gupnp-igd_0.1.3-0ubuntu2_0.1.3-0ubuntu3.diff.gz in Debian (enable test suite) and upload, so that we can sync?
[18:26] <Caesar> slangasek: you got a minute to talk about PAM or are you up to your eyeballs in post-release stuff?
[18:37] <bigon> pitti: it's already done in the git branch of gupnp-igd pkg but the test fails in debian with last version of gupnp
[18:38] <_jer_> Hey all. Just wanted to say thank you. 9.10 was the version that tipped me from "ubuntu on side machines" to "ubuntu is now my primary os". You guys did an amazing job.
[18:40] <ziesemer> Can someone help me with a casper issue?  Had it working great on a USB drive.  However, I wanted to clean things up and move everything into a /ubuntu-live subdirectory.  My boot options are /ubuntu-live/casper/vmlinux boot=casper live-media-path=/ubuntu-live/casper .  This works great, but now fails with "persistent".
[18:40] <ziesemer> I get a "mounting /dev/sda1 on /cow failed: Device or resource busy".
[18:41] <ScottK> ziesemer: Support is in #ubuntu.
[18:41] <ziesemer> Including devel support?
[18:41] <ziesemer> I see this is coming from initrd/casper, using the return path from find_cow_device in casper-functions.
[18:42] <ziesemer> I'll try at #ubuntu, thx.
[19:46] <jcastro> mdke, 15 minute warning!
[19:58] <mdke> jcastro: thanks
[21:23]  * lamont thinks bug 476935 deserves a fix
[22:58] <crypt-0> amarok  issues over here
[22:59] <crypt-0> $ amarok
[22:59] <crypt-0> amarok: symbol lookup error: /usr/lib/libamaroklib.so.1: undefined symbol: _ZTIN6TagLib3MP44FileE
[23:39] <slangasek> Caesar: PAM> what's up?
[23:52] <ScottK> lamont: I think Prozac for the buildds.
[23:52] <lamont> ScottK: ??
[23:52] <ScottK> lamont: Since they are massively unhappy
[23:52] <lamont> heh
[23:53] <lamont> I'd prefer to address the root of the problem... apparently the default make -j value on armel is b0rked because /proc/cpuinfo is totally diff from the rest of the architectures, and make doesn't notice it.  that, or the default make -j value really is "infinity"
[23:55] <jdong> lamont: the latter is true
[23:55] <lamont> jdong: that was what I thought - we should really fix that to be NCPU*2 or NCPU+1 or some such
[23:55] <lamont> because "all of them" is just plain F*^*&^)^&_ING STUPID
[23:56] <jdong> If there is nothing looking like an integer after the `-j' option,
[23:56] <jdong> there is no limit on the number of job slots.
[23:56] <jdong> that's from info make
[23:56] <lamont> yeah - and it's flawed by design
[23:56] <jdong> lamont: totally agree with you
[23:56] <jdong> but is it really a Ubuntu-appropriate thing to do to "fix" it?
[23:56] <lamont> remember to patch the info docs when we patch the source. :-)
[23:57] <jdong> HAHAHA
[23:57] <jdong> and forward it upstream!
[23:57] <lamont> mebbe I'll go pester manoj about it
[23:57] <lamont> oh, always push upstream
[23:57] <slangasek> lamont is a pusher robot
[23:57] <slangasek> here to push upstream down the stairs
[23:58] <lamont> slangasek: only if there are no witnesses, you know that
[23:59] <lamont> slangasek: are there stairs at your house? :-D
[23:59] <Laney> I AM PROTECTED!