[00:01] <keescook> mjg59: looks like the code is the same on gutsy -- I assume this will be meaningful under gutsy still?  (person with nvidia is running gutsy...)
[00:01] <emgent> keescook: https://code.edge.launchpad.net/~emgent/+junk/security-tools
[00:01] <mjg59> keescook: Yup
[00:11] <keescook> mjg59: are the "outside process range" changes in 0.99-1.2ubuntu2 needed for this?  (i.e. should I migrate your debug changes on top of that before attempting my debugging?)
[00:11] <mjg59> keescook: Nope
[00:11] <mjg59> Something similar would be useful at some point, but a misery to get right
[00:18] <blueyed> mjg59: fix attached to #199888, can you sponsor it?
[00:18] <keescook> mjg59: in your blog you talked about discovering missing opcodes.  was that related to this?
[00:18] <mjg59> blueyed: Afraid not
[00:19] <mjg59> keescook: That was thinking about emulating all the branch instructions, but I figured out that that was unnecessary
[00:19] <blueyed> mjg59: ok, subscribed u-m-s. Thanks for notifying and explaining it to me.
[00:19] <mjg59> blueyed: No problem
[00:19] <slangasek> blueyed: assign it to me, please; I'm happy to follow through on that
[00:20] <slangasek> I still want the isAnyWirelessPoweredOn() function fixed too :)
[01:14] <keescook> mjg59: where is the upstream x86emu in X.org?  I just want to make double-sure everything is up to date...
[01:15] <keescook> mjg59: nm, I knew if I asked you, I'd find it.  ;)  xorg/xserver/hw/xfree86/x86emu whee
[01:19] <keescook> mjg59: I'm going to try a fork-lift upgrade of x86emu first -- several opcodes were implemented and a few fixes added
[01:21] <slangasek> \o/
[01:22] <bddebian>  /0\
[01:24] <jdong> *gasp*
[01:25] <j1mc> \0/
[01:27] <bddebian> heh
[01:30] <Fujitsu> Beta freeze still in effect, but beta released?
[01:30] <slangasek> yes
[01:31] <slangasek> elmo: care to twiddle the archive status, since I still don't have the bit for it? :)
[01:31] <elmo> slangasek: done
[01:32] <slangasek> thanks
[01:51] <mthaddon> if anyone's listening, just wanted to say that I just upgraded to hardy, and it was completely flawless - no issues, and very smooth. Nice!
[01:54] <slangasek> hurray :)
[01:58] <mneptok> mthaddon: next time we'll make sure to overwrite your smug sense of self-satisfaction >;)
[01:59] <sabdfl> well done all
[01:59] <mthaddon> mneptok, please do - it scared me how smug I felt
[02:00] <mneptok> mthaddon: i upgraded last night. it went very well. so much so, i decided that i drop acid after work any more. just in case.
[02:00] <mneptok> s/i/i\ won't/
[02:00] <mthaddon> :)
[02:00] <mneptok> but yeah, it was a nice upgrade. some network issues at the office, but the home connection sorted those without intervention
[02:01] <mneptok> sabdfl: how're the slopes?
[02:01] <sabdfl> mneptok: full of fast-moving trees :-) am now up in BC
[02:02] <mneptok> sabdfl: BC is noted for its angry ent population.
[02:02] <mneptok> (like jkakar)
[02:02] <sabdfl> :-)
[02:03] <thom> sabdfl: boarding in canada?
[02:03] <sabdfl> mmmmuuuuussstttt hhaaaaavvveeeee dddddiiiinnnneeeerrrr ;-)
[02:03] <sabdfl> thom: indeed!
[02:03] <thom> nice!
[02:03] <mneptok> sabdfl: when you say it like that, you have to add "BRAAAAAAAAAAAAAAAAAAAAAAAAAAIIIIIIIIIINS!!!!" at the end
[02:04] <emgent> keescook: ping
[02:04] <sabdfl> only when Ng is around
[02:04] <sabdfl> cheers all, and conrats again
[02:04] <emgent> I found a security issue on launchpad
[02:04] <sabdfl> errr
[02:04] <sabdfl> congrats
[02:04] <mneptok> enjoy the rest of the downtime
[02:04] <j1mc> thanks, sabdfl
[02:04] <emgent> hi sabdfl :)
[02:05] <sabdfl> emgent: might be worth taking to #launchpad
[02:05] <sabdfl> night
[02:05] <emgent> sabdfl: I'm thinking to open security bug on LP
[02:05] <mneptok> emgent: i would recommend to talk to kees on a more secure channel about it.
[02:05] <emgent> mneptok: sure np, i know method to work. :)
[02:05] <mneptok> emgent: public IRC is probablt not the best approach vector, unless kees ahs asked you to handle things this way.
[02:06] <emgent> mneptok: i'm just ping him for see if he is up
[02:06] <emgent> canonical dont search new security personal for auditing ?
[02:06] <mneptok> emgent: ah, capisco
[02:07] <emgent> :)
[02:12] <pwnguin> mthaddon: you upgraded, from dapper or gutsy?
[02:12] <mthaddon> pwnguin, gutsy
[02:12] <pwnguin> ah, that's not nearly as impressive ;)
[02:12] <pwnguin> or daring
[02:17] <mneptok> pwnguin: i upgraded from PDP-OS
[04:25] <compbrain> Anyone doing kernel flavor builds that gocould lend me a hand for a minute?
[04:25] <compbrain> I'm having issues with the abi build step
[09:01] <Hobbsee> slangasek: one of the users doing a dist-upgrade with adept got http://pastebin.com/m1018a09c.  The dist upgrade is effectively the same, at http://paste.ubuntu-nl.org/60389/ (gutsy --> hardy upgrade).  Has anyone else reproduced that?
[09:07] <slangasek> Hobbsee: I don't believe so; none of mvo's upgrade tests indicated any upgrade problems from gutsy, and I haven't heard anyone else reporting this
[09:11] <slangasek>   libc6-i686: PreDepends: libc6 (= 2.7-5ubuntu2) but 2.7-9ubuntu2 is installed
[09:12] <slangasek> Hobbsee: that's very suspect; the user seems to have a libc6-i686 installed that's not from either gutsy or hardy
[09:15] <Hobbsee> slangasek: oh, it's a very old hardy version.  nvm.
[09:15] <Hobbsee> strange.
[09:28] <Fujitsu> slangasek: Are upgrade tests run by you guys for universe too? If not, how do we run them?
[09:31] <slangasek> Fujitsu: I'm not sure whether mvo's upgrade tests include universe, that's a question to ask him
[09:32] <Fujitsu> slangasek: Thanks, I'll poke him when he appears.
[09:59] <lool> pitti: I consider adding a -include langpack.mk in Debian's avahi; ok for you?
[09:59] <lool> Hmm it's probably a Feiertag in Germany
[10:00] <siretart> lool: it is.
[10:00] <lool> Hey siretart
[10:01]  * siretart hugs lool 
[10:01]  * lool crushes under the pressure
[10:01] <siretart> lol
[10:03]  * siretart sighs at gstreamer-ffmpeg using the removed imgres feature of ffmpeg :/
[10:04] <lool> Eh, it wouldn't be ffmpeg if it didn't break API
[10:08] <siretart> lool: well, yes, but gstreamer-ffmpeg could also at least try to track ffmpeg upstream
[10:09] <lool> siretart: Perhaps they do in CVS, but they prefer staging with a ffmpeg snapshot
[10:10] <lool> siretart: As they need to QA/stabilize this ffmpeg tree before outputting a gst-ffmpeg
[10:18] <smurf> Does anybody know why there seems to be no libglade2.*dbg package?
[10:31] <TomaszD> pitti, I see you've uploaded avahi with po template, but you missed one thing https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/198859
[10:31] <ubotu> Launchpad bug 198859 in avahi "Make .desktop files translatable (diffs included to fix this)" [Undecided,New]
[10:31] <TomaszD> bbl
[10:31] <seb128> TomaszD: the cdbs magic does update the desktop files automatically
[10:32] <seb128> TomaszD: didn't read the bug, hint if you want somebody to read your issue you could describe it on launchpad rather pointing to an another bug tracker
[10:35] <geser> Hobbsee, Mithrandir or pitti: please give-back ldtp. Thanks.
[10:39] <pitti> lool: hi
[10:39] <pitti> lool: include langpack.mk in Debian's avahi> won't work, Debian's cdbs doesn't have that
[10:39] <pitti> lool: if you want to do that in Debian, you should add sth like
[10:39] <pitti> common-post-build-arch::
[10:39] <pitti>      cd po; intltool-update -p --verbose
[10:40] <pitti> TomaszD: hm, langpack.mk should take care of this; it didn't?
[10:40] <pitti> geser: done
[10:41] <seb128> TomaszD: in fact the bug is about the desktop not being listed in POTFILES.in
[10:41] <seb128> pitti: ^
[10:42] <pitti> ah, I see
[10:42] <pitti> I wasn't aware of that bug, sorry
[10:43] <seb128> pitti, lool: not as easy as calling intltool-update because you likely want to add the X-Ubuntu-Gettext-Domain to the desktops too
[10:43] <pitti> but not to Debian
[10:44] <pitti> since they don't have our 'use gettext for .desktop' patches?
[10:44] <seb128> pitti: right, but the question was about being in sync with debian no?
[10:44] <pitti> I suppose so, yes
[10:45] <seb128> so we need something doing that
[10:45] <seb128> pitti: btw lool merged the gettext patch to glib
[10:45] <pitti> gosh, maybe we should start another attempt to convinve the fd.o guys to add an optional "Gettext-Domain:" to the spec
[10:45] <seb128> and theorically adding this to the debian desktops doesn't hurt, it just do nothing there
[10:45] <pitti> it wouldn't cost them much, and doesn't require other distros to change their implementation
[10:45] <pitti> right
[10:52] <pitti> lool: hm, e-p-bad is now depwaiting on python-elisa (>= 0.3.5); hardy has 0.3.4-2
[10:52] <pitti> lool: looks like we shuold just sync this unless it has new features?
[10:53] <Fujitsu> pitti: lool requested a sync of that earlier, I believe.
[10:53] <pitti> ah, bug 204555
[10:53] <ubotu> Launchpad bug 204555 in elisa "Please sync misc elisa* packages from unstable (or incoming)" [Undecided,New] https://launchpad.net/bugs/204555
[10:59] <TomaszD> How about this pet peeve https://bugs.launchpad.net/nautilus-sendto/+bug/197145 :]
[10:59] <ubotu> Launchpad bug 197145 in bluez-gnome "REGRESSION [hardy] nautilus-sendto not compatible with bluetooth-sendto" [Low,Confirmed]
[10:59] <TomaszD> there's a patch available from Bastien tha applies cleanly to hardy's source package
[10:59] <TomaszD> *that
[11:02] <seb128> TomaszD: that patch is far to be trivial
[11:02] <TomaszD> seb128, I'm certainly aware that it isn't trivial,  but it's used in Fedora, I've tested it myself and it doesn't break anything
[11:03] <seb128> lool: ^ do you think you could have a look to this bluez change? you have bluetooth devices to try I think? Mithrandir has not been responsive on the sponsoring request
[11:03] <lool> Mithrandir is in leave ATM
[11:04] <lool> I can have a look
[11:04] <seb128> lool: thanks
[11:05] <Hobbsee> geser: given back
[11:07] <geser> Hobbsee: pitti was faster. I guess I should send an un-ping next time.
[11:07] <pitti> geser: or I should send the 'done' to hobbsee as wel
[11:07] <pitti> l
[11:11] <lucas> who wrote the code for patches.ubuntu.com? the patches are directly taken from MoM?
[11:11] <pitti> lucas: Keybuk; yes, it's part of the MoM output
[11:18] <Hobbsee> pitti: yeah, that'd be nice :)
[11:18]  * Hobbsee tried, anyway
[11:23] <cody-somerville> Hobbsee, Can you take care of merge #166 for me?
[11:27] <cody-somerville> or anyone else who wants to for that matter
[11:33] <slomo__> slangasek: ping? :)
[11:34] <Hobbsee> cody-somerville: ?
[11:35] <cody-somerville> Hobbsee, Can you merge the xubuntu seeds?
[11:35] <cody-somerville> https://code.edge.launchpad.net/~xubuntu-devel/ubuntu-seeds/xubuntu.hardy/+merge/166
[12:41] <pitti> yay, suspend-to-ram works so mindbogglingly perfect now
[12:43] <ompaul> pitti, that is worth at least yippee not a yay ;-)
[12:43] <pitti> YIPPEEEE!
[12:43]  * pitti will upload that new hal soon
[12:44]  * seb128_ hugs pitti
[12:46] <sjoerd> pitti: Could you forward the patchset ubuntu has in hal-info to upstream/debian ? :)
[12:46] <pitti> sjoerd: hi
[12:46] <sjoerd> morning :)
[12:46] <pitti> sjoerd: I did that already when I applied them
[12:46] <pitti> sjoerd: they should all be upstream
[12:46] <sjoerd> hmm
[12:47] <pitti> sjoerd: well, at least the music players are
[12:47] <pitti> sjoerd: I forwarded a few quirks, too, but they haven't been applied
[12:47] <sjoerd> aah, the ubuntu version is still the old one
[12:47] <sjoerd> that explains :)
[12:47] <pitti> sjoerd: if you mean above suspend patches, I'm just sending a followup with the patches to my mail from yesterday
[12:47] <pitti> sjoerd: yes, haven't updated yet; still on my list
[12:48] <sjoerd> I should learn to read :)
[12:48] <pitti> but this suspend stuff was nagging my brain since yesterday, I had to resolve this (even if it's holiday and all that)
[12:48] <sjoerd> cool
[12:48] <sjoerd> i'll commit them upstream if they aren't controversial
[12:53] <pitti> sjoerd: ok; they should all be on hal@, but I'll merge hal-info now and see what's left
[12:54] <sjoerd> thanks
[12:55] <elmargol> Hi I try to create a vlc pakage using the --enable-mediacontrol-python-bindings setting... and i get a permission problem for /usr/lib/python2.5/site-packages/vlc.so any ideas?
[13:01] <\sh> pitti: it's karfreitag...you should not be sitting in front of IRC ;)
[13:01] <pitti> \sh: see above, had to get that out of my brain :)
[13:02] <\sh> pitti: right...I know that feeling ;)
[13:15] <Kopfgeldjaeger> aloha
[13:16] <pitti> sjoerd: ok, down to 2 patches again :)
[13:17] <sjoerd> \o/
[13:17] <pitti> sjoerd: both are on hal@, BTW
[13:18] <pitti> http://lists.freedesktop.org/archives/hal/2007-November/009903.html
[13:18] <pitti> http://lists.freedesktop.org/archives/hal/2008-February/010897.html
[13:18] <pitti> sjoerd: shall I send you the actual patches again, or the debdiff, or are those ^ enough?
[13:20] <sjoerd> should be enough
[13:24] <pitti> seb128_: you are in a sync-y mood today :)
[13:26] <seb128_> pitti: yes, GNOME 2.22 has been uploaded to debian while we were frozen so I'm syncing what we can now that we are unfrozen ;-)
[13:26] <\sh> oh sync time :)
[13:27] <sjoerd> pitti: hummm, syncing on sysfs_paths is a bit nasty.. can't 02_laptop_panel_brightness_in_hardware.patch be done by matching on linux.subsystem instead ?
[13:27] <pitti> sjoerd: I really don't know, it was mjg59's patch
[13:27] <sjoerd> mjg59: ^^
[13:27] <pitti> mjg59: ^ any idea?
[13:29] <pitti> sjoerd: BTW, the Dell CD-ROM problem is bug 48499
[13:29] <ubotu> Launchpad bug 48499 in hal-info "hald blocks ide bus if cdrom on same bus with harddisk(was:Extremly slow IO performance with dapper, high wa% on Dell Inspiron 8200)" [Medium,Fix released] https://launchpad.net/bugs/48499
[13:29] <sjoerd> I remember that one :)
[13:30] <pitti> it got reverted upstream without explanation
[13:32] <emgent> heya sabdfl :)
[13:35]  * pitti -> holiday mode again, cu all
[13:35] <seb128_> pitti: enjoy
[13:35] <pitti> and you!
[13:43] <ubuntu> hi everyone - may I ask here for problems in installing hardy beta 1 from live cd?
[13:43] <DRebellion> ubuntu, you probs want #ubuntu+1
[13:46] <ubuntu> thx
[13:48] <cody-somerville> Fujitsu, Can you setup a mdt thinger for Xubuntu?
[13:50] <jdong> mdt thinger
[13:50] <jdong> why does that sound X-rated?
[13:51] <cody-somerville> multi distro tool
[13:51] <cody-somerville> could be lethal
[13:53] <persia> jdong: http://people.ubuntuwire.com/~fujitsu/mdt/
[13:55] <jdong> cool!
[14:21] <mjg59> pitti: Heard from Intel - the resume code doesn't like i855 right now
[14:22] <mjg59> pitti: They suggest that the easiest thing to do is to look at the PCI IDs for i830 and i855 - there's only 4 of them
[14:22] <mjg59> And then if we have one of those, perform the quirks
[14:49] <wasabi> Does wubi use ntfs-3g?
[14:51] <mjg59> Yes
[14:55] <wasabi> Hmm. Does Fuse do file->device mappings or does each read require traversing through the daemon?
[14:55] <wasabi> (ntfs3g is fuse, right?)
[14:55] <mjg59> It's fuse, yes
[14:55] <mjg59> I've no idea about the implementation details
[15:06] <jdstrand> hi seb128_!
[15:06] <jdstrand> seb128_: are you working today?
[15:07] <seb128_> hey jdstrand, sort of, it's officially an holiday day for me but I'm around and doing some desktop cleanup now than hardy is unfrozen
[15:08] <seb128_> jdstrand: if you have a question feel free to ask ;-)
[15:08] <jdstrand> seb128_: well, I don't want to give you any more work, but you can always say 'no' :)
[15:08] <seb128_> right
[15:08] <jdstrand> seb128_: can you look at my last comment on bug #58171 ?
[15:08] <ubotu> Launchpad bug 58171 in gnome-session "Connection to ICE-unix/.. socket times out so programs take minutes to start" [Medium,Confirmed] https://launchpad.net/bugs/58171
[15:09] <jdstrand> seb128_: it started biting me lately
[15:11] <jdstrand> seb128_: when this happened the other day, I had these syslog entries too (I believe), but I didn't note them
[15:12] <jdstrand> since I can control vnet1, I'll work on a reproducer
[15:13] <seb128_> jdstrand: that's a weird issue and I've no real clue about IPv6, I don't think I'll be of real help there
[15:14] <jdstrand> seb128_: I thought it odd too
[15:14] <jdstrand> seb128_: but it just started happening to me lately
[15:15] <jdstrand> and it is *extrememly* annoying as I have to restart X
[15:15] <jdstrand> extremely even
[15:15] <jdstrand> seb128_: perhaps it'll be more interesting with a reproducer?
[15:15] <seb128_> jdstrand: does it happen without using ipv6?
[15:15] <seb128_> jdstrand: for sure it would yes
[15:15] <jdstrand> seb128_: I don't know yet
[15:15] <jdstrand> ;)
[15:15] <jdstrand> seb128_: I just found the bug today
[15:15] <seb128_> comments seem to suggest it's ipv6 specific
[15:16]  * jdstrand nods
[15:17] <jdstrand> seb128_: you know, it was only recently that I enabled ipv6 (for my ufw work)
[15:17] <jdstrand> seb128_: I'll play with it
[15:18] <seb128_> jdstrand: let me know if you figure an easy way to trigger the issue
[15:18] <seb128_> jdstrand: btw would also be nice to try the avahi bug without ipv6
[15:35] <mdke> seb128_: do you happen to know what happened the the Multimedia tab on "System->Preferences->Removable Drives and Media"? I can't find a way to change the default application for playing DVDs, and we need to amend the documentation
[15:36] <mdke> (we don't recommend totem-gstreamer for playing dvds as it doesn't seem to support menus)
[15:38] <seb128_> mdke: nautilus, preferences, media tab
[15:39] <seb128_> mdke: what do you recommend?
[15:39] <mdke> seb128_: gxine...
[15:40] <mdke> seb128_: thanks for the nautilus tip - is there a reason that has disappeared from the Removable Drives and Media tool? It's a bit hidden in nautilus
[15:41] <mdke> ah, can't specify to open gxine in nautilus anyway
[15:41] <seb128_> mdke: implementation details let's say
[15:41] <mdke> it's only totem, do nothing or open folder
[15:41] <seb128_> mdke: it was handled by an external software and it's handled by gvfs now
[15:41] <seb128_> mdke: the gxine desktop needs to list the mimetypes
[15:42] <mdke> hmm.
[15:43] <mdke> seb128_: do you think we should recommend totem-gstreamer for DVDs anyway, given that it will open automatically for the user even if they install gxine?
[15:43] <seb128_> yes
[15:43] <seb128_> and you have the chapters in the playlist
[15:43] <seb128_> which is not that bad
[15:43] <mdke> do you happen to know if menu support is far away?
[15:44] <seb128_> no
[15:44] <seb128_> it's not that far away for quite a while
[15:45] <mdke> heh
[15:45] <seb128_> it "just" require somebody doing the work
[15:47] <mdke> the alternative is to recommend gxine and tell users how to set "Do nothing" in nautilus
[15:47] <mdke> then start gxine manually
[15:47] <seb128_> what do you mean?
[15:47] <seb128_> they should select gxine there if they want to use it
[15:47] <mdke> but it isn't there...
[15:48] <seb128_> mdke:  mdke: the gxine desktop needs to list the mimetypes
[15:48] <seb128_> mdke: that's a 1 line fix
[15:48] <seb128_> I'll fix it today
[15:48] <Chokes> hi all
[15:49] <mdke> seb128_: aha! Thanks. In that case I'll document how to add it to the nautilus dialog
[15:49] <Chokes> i have a goog question
[15:50] <Chokes> good*
[15:50] <mdke> seb128_: do you know if there are plans for gnome to move that preferences back to the capplet maybe for the next release?
[15:50] <Chokes> will the fakeraid be supported someday?
[15:51] <seb128_> mdke: I doubt of it, this "capplet" is a separate thing running for no real need now and we should rather get ride of it
[15:52] <seb128_> mdke: we can discuss an improved location for the UI next cycle if required though
[15:52] <Chokes> ???
[15:53] <mdke> seb128_: yes, that's what I mean. It should be accessible from System/Preferences or control-center or whatever
[15:59] <Chokes> can someone respond to me please?
[16:02] <caci> Chokes: maybe.
[16:02] <jdong> I see great fortune in your future.
[16:03] <Chokes> so when the fakeraid will be supported?
[16:03] <superm1> slangasek, might you recommend a good way to test improvements to seeds aside from the daily disk generation?  laga wanted to fix the -diskless stuff inside the alt disk, but waiting a day each time ends up not being a very good solution
[16:04] <laga> slangasek: i can test the diskless stuff better now (wget the udeb from somewhere and install it).
[16:04] <laga> slangasek: we're more concerned about adding 'tasks' to the alternate disk..
[16:05] <jdong> Chokes: to answer your question, I don't think there is any active work going towards supporting fakeraid at the moment
[16:05]  * xhaker enters fortune on the terminal after reading what jdong wrote
[16:06] <Chokes> ok....
[16:06] <superm1> jdong, would you mind looking over the mythstream backport on gutsy-backports?  been getting bugged about it several times this week
[16:06] <Chokes> so the bes distro cant support the fakeraid
[16:06] <Chokes> best*
[16:07] <jdong> Chokes: fakeraid can be used on Ubuntu by post-install configuration, but there doesn't seem to be anyone interested enough in fakeraid support to implement it into the installer
[16:07] <mdke> seb128_: ok, this is what I've written (a middle ground) - http://mdke.org/tmp/DVD.png
[16:07] <jdong> Chokes: nobody is stopping anyone from doing it. If you want to implement fakeraid support you are more than welcome to
[16:07] <Chokes> yeah but im not a dev.....
[16:08] <mdke> seb128_: I'll leave the gxine bit to you :D
[16:08] <jdong> superm1: *grumble* packing up for a plane ride this afternoon currently; bug#?
[16:08] <superm1> jdong, bug 202988
[16:08] <ubotu> Launchpad bug 202988 in gutsy-backports "Please backport mythstream 0.18.1 from hardy" [Undecided,New] https://launchpad.net/bugs/202988
[16:08] <Chokes> i can say "Wow" on all the features
[16:08] <xhaker> Chokes: just file a bug and get enough subscriber to that bug, it will be noticed then.
[16:08] <jdong> Chokes: what do you need with fakeraid, out of curiousity?
[16:09] <Chokes> jdong : i want to install ubuntu on my fakeraid setup
[16:09] <jdong> Chokes: have you seen https://help.ubuntu.com/community/FakeRaidHowto, by the way? It's not pretty but it'll work
[16:10] <Chokes> maybe load a script or something that we can coose on the boot menu coulb be great
[16:10] <Chokes> that what ill retry later
[16:10] <Chokes> it didnt work for me
[16:11] <seb128_> mdke: alright
[16:11] <jdong> I'm not sure if GRUB would boot directly off fakeraid
[16:11] <jdong> somehow I doubt it. At which point you should be begging $other_people for fakeraid support :)
[16:11] <Chokes> it should
[16:11] <Chokes> mmm
[16:12] <Chokes> the problem her is ubuntu is supposed to be easy to use and install ok?
[16:12] <jdong> I don't know nearly enough about fakeraid implementations on hardware to know if it provides enough block device emulation for booting to be successful with GRUB
[16:12] <Chokes> so take the one who dont know about linux
[16:13] <Chokes> he want to install linux on his fakeraid setup
[16:13] <jdong> the last I heard about fakeraid is that it's essentially a couple bit flags that say "oh yeah treat this as a RAID please"
[16:13] <laga> they probably wont have a rakeraid then ;)
[16:13] <Chokes> maybe
[16:13] <Chokes> but they will see that they dont see the raid...
[16:14] <jdong> because it's not really a RAID.
[16:14] <Chokes> yeah i know
[16:14] <Chokes> its fake
[16:14] <laga> Chokes: i'd hope that.. otherwise they'd be desyncing their array if they installed on just one disk
[16:14] <xhaker> jdong: what is your stance about transmission? 1.10 for FFe?
[16:15] <Chokes> when i install dmraid
[16:15] <Chokes> the i start the installer
[16:15] <Chokes> then*
[16:15] <jdong> xhaker: I am not very comfortable with the idea, but it will depend on the final diff size
[16:15] <Chokes> the installer see the fakeraid config
[16:15] <jdong> xhaker: I've been tracking trunk on subversion and it all looks quite invasive
[16:16] <jdong> but it won't boot because the installed system won't know about fakeraid.
[16:16] <Chokes> =_=
[16:17] <xhaker> jdong: my take exactly, but looking at the NEWS file it gets pretty interesting
[16:17] <jdong> bug 191557 has the official position on it, Chokes
[16:17] <ubotu> Launchpad bug 191557 in dmraid "Main inclusion report." [Undecided,Won't fix] https://launchpad.net/bugs/191557
[16:17] <Chokes> it wont install at all
[16:17] <jdong> please read the last comment on that bug
[16:18] <jdong> xhaker: if transmission were still just another azureus or deluge in Universe, I'd be more willing to consider it. But it's not. It's the main torrent client that comes associated by default for all Hardy installs. Way too risky
[16:19] <jdong> xhaker: at this point, we've got like 2 or 3 crasher bugs unresolved in our 1.06, I'd say fix via backporting specific patches from this point forward, and defer 1.10+ for backporting possiblity.
[16:19] <jdong>    + Stop torrents when downloading and the disk becomes full
[16:19] <jdong> on a side note.... how would that help?
[16:20] <Chokes> jdong its a mac osx bug......
[16:20] <jdong> when the disk becomes full, stopping the torrent isn't gonna fix much.
[16:21] <Chokes> ok
[16:21] <Chokes> now i got it
[16:21] <xhaker> jdong: might avoid the application to crash
[16:21] <jdong> superm1: myth done
[16:21] <jdong> superm1: rather, myth confirmed :)
[16:21] <superm1> jdong, now the interesting situation here is that mythstream was already backported once
[16:22] <superm1> same upstream version
[16:22] <superm1> just different ubuntuX revision
[16:22] <superm1> this one has a patch to allow it to now FTBFS against the new libmyth
[16:22] <jdong> superm1: well it was a soyuz bug in 2005, 2007 is congruent to 2005 mod 2.......
[16:22] <superm1> so could a sourceful upload be done one it since its not a new version, and won't go through NEW?
[16:22] <jdong> superm1: so by that logic it's probably going to be a soyuz bug that the backport gets rejected post-build :D
[16:23] <superm1> argh, that won't be good
[16:23] <jdong> superm1: wait. Clarify that again?
[16:23] <superm1> jdong, so earlier in gutsy's cycle, we backported this version of mythstream
[16:23] <superm1> this upstream version
[16:24] <superm1> but it needed to be rebuilt after the libmyth backport
[16:24] <superm1> in order to rebuild, it needs a patch present in the hardy version (hence the new backport)
[16:25] <jdong> superm1: barring the old soyuz bug, a direct backport from hardy should work as long as the libmyth backport is done first, correct?
[16:25] <superm1> which is was
[16:26] <superm1> so i was just wondering if we'd still need to go through an archive admin for this
[16:26] <superm1> or if just upload directly to gutsy-backports
[16:26] <superm1> since it was already backported once
[16:26] <jdong> superm1: no all uploads to gutsy-backports land in the queue
[16:26] <jdong> superm1: regardless of if it's NEW
[16:27] <superm1> jdong, ah okay then normal process it is :)
[16:27] <jdong> yay :)
[16:28] <jdong> barring the soyuz bug mod 2 :)
[16:28] <jdong> I think I've found a working model of soyuz regressions! :D
[16:31] <cody-somerville> slangasek, Did you start the rebuild for Xubuntu? :)
[17:01] <orbisvicis> i have this ubuntu package i changed, how can i increment the version number ?
[17:02] <jdong> dch -i
[17:08] <orbisvicis> so what am i seeing here ?
[17:09] <thesurvivorman> the matrix
[17:09] <orbisvicis> lol
[17:09] <orbisvicis> and which file does dch -i change ?
[17:09] <james_w> debian/changelog
[17:09] <slangasek> slomo: pong
[17:10] <james_w> it should have spawned an editor to allow you to add a changelog entry.
[17:11] <orbisvicis> yeah it did
[17:11] <slangasek> superm1, laga: sorry, I'm not sure of a good way to test seed changes besides running them through the image generation
[17:11] <orbisvicis> just wasnt sure what to change till i compared dch with dch -i
[17:11] <orbisvicis> but thanks, got it
[17:12] <slomo> slangasek: hi, just wanted to ask you about a FF exception that needs some discussion :)  we currently have gtkhtml3.8 in main just because of f-spot->gnome-sharp2 which is bad... now the solution could be, to get gtk# 2.12.0, gnome# 2.20, gnome-desktop# 2.20 (packages in debian/unstable, just need trivial merging), get the latter into main and build f-spot against it (required patches in debian too). in debian there are no known problems with th
[17:12] <slomo> e new versions yet, they're part of the gnome 2.22 release (so iirc covered by the general gnome exception) but unfortunately introduce some new features :)
[17:12] <slangasek> cody-somerville: I hadn't started an xubuntu rebuild; everything is in place such that you're ready for me to do so?
[17:12] <cody-somerville> slangasek, Uno momento
[17:13] <slangasek> slomo: if they're part of the gnome 2.22 release, that covers FFe
[17:13] <cody-somerville> slangasek, can you take care of this? https://code.edge.launchpad.net/~xubuntu-dev/ubuntu-seeds/xubuntu.hardy/+merge/166
[17:14] <slomo> slangasek: ok, even now after beta was released and considering the changes?
[17:17] <slomo> dashua: ping? regarding banshee svn building... --enable-external-boo (and all the other --enable-external-* parameters) for configure will fix it
[17:17] <slangasek> slomo: if you do it right away and don't make me think too much about what I'm saying... :/
[17:18] <slomo> ok ;)
[17:20] <dashua> slomo, Hello
[17:20] <dashua> Ok, thx
[17:25] <slangasek> cody-somerville: merged
[17:26] <cody-somerville> slangasek, Okay. Those merged seeds should be good to go
[17:27] <cody-somerville> slangasek, did you push it after merging it?
[17:28] <slangasek> I merged it into the relevant branch, yes
[17:29] <cody-somerville> Launchpad must be slow. I usually get an e-mail notification by now.
[17:29] <cody-somerville> Ah, there we go
[17:29] <cody-somerville> slangasek, should be all good :)
[17:32] <dashua> slomo, Built rev. 3505 and it's still not recognizing the device.
[17:33] <hefe_bia> cjwatson: Do you know whether somebody is working on bug #54776? It's marked "In Progress" but not assigned to anyone.
[17:33] <ubotu> Launchpad bug 54776 in openoffice.org "[Ubuntu] [hardy] font hinting does not work with libfreetype6 v. 2.2.1" [High,In progress] https://launchpad.net/bugs/54776
[17:33] <slomo> dashua: ok, so it's at least not my fault :) anything useful printed when starting it? could you pastebin the complete output from starting banshee until everything is done?
[17:34] <dashua> Sure, I know this device definitely works and I help gabaug test it in #banshee.
[17:41] <dashua> slomo, http://paste.ubuntu-nl.org/60426/
[17:43] <slomo> dashua: no idea, better file upstream :)
[17:43] <slomo> dashua: or talk with scottp in #banshee (iirc he wrote the mtp support)
[17:44] <dashua> slomo, Will do thx.  I'm not sure if something changed in the past month or not. Thx.
[17:44] <slomo> dashua: yes, something changed ;)
[17:47] <james_w> hefe_bia: you're probably best asking calc about that.
[17:53] <cody-somerville> I'm definitely recreating the branch for Intrepid
[17:54] <slangasek> slomo: heh, why does gtk-doc build-conflict with openjade and build-depend on docbook-dsssl?
[17:55] <slomo> slangasek: because it needs exactly these two... it can't work with openjade but needs docbook-dsssl which shouldn't be a problem as the latter depends on all 3 jade packages conditionally
[17:55] <slangasek> slomo: right, well, the buildd didn't see it that way http://launchpadlibrarian.net/12784304/buildlog_ubuntu-hardy-i386.gtk-doc_1.10-1_FAILEDTOBUILD.txt.gz
[17:56] <slangasek> seb128: and why are you uploading packages that has slomo's name in the changelog, OMG confusing. :)
[17:56] <seb128> slangasek: those are called "syncs" ;-)
[17:56] <slangasek> seb128: heh, true
[17:57] <slangasek> slomo, seb128: so I guess an explict build-dependency on jade would fix this...
[17:59] <slomo> slangasek: like "Build-Depends-Indep: jade (>= 1.2.1-35)"?
[18:00] <slomo> slangasek: the buildd doesn't like it because it's in b-d-i maybe
[18:01] <seb128> slomo: those didn't change in the new version right?
[18:01] <seb128> seems to be a soyuz issue
[18:01] <slomo> no, that didn't change
[18:03] <slangasek> slomo: mmm, yes :)
[18:08] <theunixgeek> Where can I download all the docs at http://library.gnome.org/devel/gtk/stable/, preferably in a PDF?
[18:19] <Festor> Would it be possible to add transmission 1.10 to 8.04 Ubuntu repositories?
[18:19] <Festor> It launched the first beta
[18:20] <Festor> http://forum.transmissionbt.com/viewtopic.php?t=4365
[18:20] <Festor> added libnotify support
[18:20] <Festor> more translations
[18:20] <Festor> and more bugfix
[18:20] <Festor> complete changelog
[18:20] <Festor> http://trac.transmissionbt.com/query?status=closed&milestone=1.10
[18:21] <Festor> hi?
[18:24] <seb128> Festor: are you upstream for it?
[18:26] <Festor> sorry seb128? I do not understand what you mean
[18:26] <seb128> Festor: are you working on this software or just an user asking for a new version?
[18:26] <jessica> do you know when the realtek RTL8187B wireless driver will be incuded
[18:26] <Festor> ehh
[18:26] <Festor> I am a packager
[18:27] <Festor> but not a official packager of ubuntu
[18:27] <Festor> I work for GetDeb
[18:27] <Festor> But I would like to know if that was possible
[18:28] <jessica> dose anyne know when the realtek RTL8187B driver will be incuded in ubuntu
[18:28] <Festor> The current version of the program which comes in hardy is perhaps something old
[18:28] <Festor> jessica, i think that this first in vanilla kernel
[18:28] <james_w> jessica: do you know what package provides the RTL8187 driver, it seems like they should be the same driver.
[18:28] <james_w> or at least the 8187 could be made to support the 8187B
[18:29] <jessica> i dont know much about it im a linux noobie
[18:29] <seb128> Festor: no it's not old, but if the new version is a bug fix one there should be no problem
[18:29] <Festor> http://trac.transmissionbt.com/query?status=closed&milestone=1.10
[18:29] <seb128> Festor: maybe it would benefit to everybody if you were working to get those new versions in Ubuntu rather than on GtkDeb?
[18:30] <seb128> s/GtkDeb/GetDeb
[18:30] <jdong> Festor: I just talked to someone 2 hours ago about this
[18:30] <jdong> xhaker: ^^
[18:31] <seb128> btw could anybody talk to upstream about fixing the menu item to give an idea of what the program is doing?
[18:31] <Festor> seb128, It is not easy to be part of MOTU
[18:31] <jdong> Festor: as the administrator of the MOTU P2P team, it's my opinion that this is too late in the release cycle to introduce a new upstream version of the default Ubuntu torrent client
[18:31] <seb128> Festor: that's not true
[18:31] <jdong> Festor: you do not have to be MOTU at all to contribute
[18:31] <seb128> Festor: did you try?
[18:32] <jdong> Festor: I did fine as a contributor for over 2 years before becoming a MOTU.
[18:32] <seb128> Festor: and you don't need to be a MOTU to send update diff on launchpad and subscribe the sponsor team
[18:32] <jessica> i want to start helping ubuntu do i need to learn a programming language if so which ?
[18:32] <seb128> jessica: no
[18:32] <jdong> Festor: at this point, any defects in transmission 1.06 should be handled as an isolated patch backport
[18:32] <seb128> jessica: you can do user support, fix or triage bugs, do translations, etc no need to code
[18:33] <jdong> (of course if any core-devs/ubuntu-release folks want to override this opinion they are more than welcome!)
[18:33] <seb128> jdong: no, new bug fix versions are welcome
[18:33] <jessica> how do i like because part of it
[18:33] <seb128> jdong: there is no UVF now, only FF
[18:33] <jdong> seb128: 1.10 is not a bufix version though, from what I see
[18:33] <jessica> at the moment im just helping on the forum but i want to do more
[18:33] <seb128> jdong: that was my question
[18:33] <jdong> seb128: even the GUI has been rearranged/redesigned
[18:34] <bobbo> jessica; bugs in Launchpad tagged with 'bitesize' are often useful for getting started
[18:34] <Positronic> there is no data
[18:34] <Positronic> only XUL
[18:34] <jdong> seb128: there *are*, however, mentions of some bugfixes, which I would be interested in isolating :)
[18:34] <seb128> jessica: try on #ubuntu-motu maybe, that's where people start usually
[18:34] <james_w> jessica: that's useful, thanks. If there is a certain area that you would like to do more in you can tell us and we can try and point you in the correct direction.
[18:34] <james_w> jessica: also, for your driver question it doesn't seem like it will be anytime soon I'm afraid.
[18:35] <jessica> i dont really mind and ok i will just complie the driver
[18:35] <steveire> Hi. I just tried a s/gusty/hardy/g and an update, and I got an unmet dependancy: 'librdf0-dev: Depends: libdb-dev but it is not installable' Is this a missing metapackage or a librdf packaging bug?
[18:35] <jessica> i just want to do more for ubuntu
[18:35] <steveire> http://packages.ubuntu.com/search?suite=all&searchon=names&keywords=libdb-dev
[18:35] <jessica> i dont mind learning a coding language or something
[18:36] <jdong> Festor: as soon as Intrepid opens, I'd be happy to put transmission in backports
[18:36] <Festor> jdong, Sorry but I believe that almost 40 errors corrected is a bubfix release
[18:36] <jdong> Festor: please don't resort to getdeb packages for this, at least not without consulting one of us MOTU-P2P folks. We don't need to diverge packaging.
[18:36] <jdong> Festor: it has bugfixes but is *NOT* a bugfix *ONLY* release
[18:36] <Festor> ehhh
[18:36] <Festor> ok
[18:36] <jdong> Festor: I have been tracking and watching subversion trunk on transmission these weeks
[18:37] <jdong> Festor: if I have some time this weekend I'll look at backporting all the bugfix-only fixes, but charles_ and I agreed that 1.06 would be the last version to go into Hardy
[18:37] <seb128> GetDeb is grrrrrr
[18:37] <Festor> I dont understand " please don't resort to getdeb packages for this"
[18:37] <seb128> why people need to fork efforts rather than contributing
[18:37] <seb128> s/contributing/contribute
[18:38] <jdong> and I'm frankly a bit disappointed that Transmission team decided to make bugfixes ONLY for a brand new branch.
[18:38] <jdong> Festor: I meant, Ubuntu and Debian have a coordinated effort and infrastructure for packaging Transmission. There is no reason to fork from this infrastructure and diverge packaging
[18:38] <jdong> unless it's in your interest to risk introducing incompatible transmission packaging.
[18:39] <Festor> I dont like backports
[18:39] <jdong> let's work together to achieve some solution on this. Nobody's going to fall over and die if they do not get the latest transmission in the next 24 hours.
[18:39] <Festor> is not the same use a repositorie
[18:39] <Festor> than download only a deb package
[18:39] <jdong> backports *is* a repository.
[18:39] <jdong> you can download single debs from backports off packages.ubuntu.com
[18:39] <Festor> and libs?
[18:39] <Festor> ~~
[18:40] <jdong> Festor: if you don't want to use the backports repository, at least use the backports *packaging*
[18:40] <Festor> what?
[18:40] <jdong> uupdate from Debian/Ubuntu packaging of Transmission
[18:40] <jdong> do not go reinventing these packages
[18:40] <steveire> Here's the rest of the errors. It looks like libc6, libdb and tzdata have issues.
[18:40] <steveire> http://kde.pastey.net/84190
[18:41]  * YokoZar notices the mirrors are really slow today due to beta release and begins having crazy ideas about apt-torrent
[18:42] <jdong> YokoZar: indeed
[18:42] <steveire> YokoZar: I think apt-torrent is a brilliant idea
[18:42] <jdong> YokoZar: I did my best... I seeded 150GB onto the two desktop torrents
[18:42] <Festor> "at least use the backports *packaging*"  <- why?
[18:42] <jdong> steveire: the downfall is it needs to daemonize
[18:42] <jdong> Festor: I just told you. Otherwise you risk introducing breakage and incompatibility once Ubuntu officially releases transmission 1.10 packaging.
[18:42] <steveire> downfall of apt-torrent or my update attempt?
[18:42] <jdong> steveire: apt-torrent
[18:43] <steveire> What does it mean to daemonize?
[18:43] <jdong> steveire: apt-torrent must go into background and continue running beyond the duration of getting the update
[18:44] <jdong> steveire: otherwise the swarms are going to be total crap health if everyone just grabs enough to get the package and runs off
[18:44] <YokoZar> It also means abstracting the torrent engine out of the torrent client if we don't want to duplicate things
[18:44] <jdong> YokoZar: we could theoretically use a transmission-daemon for doing that :)
[18:45] <YokoZar> Actually, it'd be pretty nice if I could check a box or slider in transmission that said "use my bandwidth to share updates with other Ubuntu users" and it communicated using DBus calls
[18:45] <jdong> :)
[18:45] <jdong> Festor: so are you interested in helping get the bugfixes from transmission 1.10 into Hardy?
[18:46] <Festor> http://pastebin.ubuntu.com/5975/
[18:46] <Festor> only added libnotify-dev
[18:46] <jdong> that is not helpful to us
[18:47] <Festor> sorry
[18:47] <jdong> that's 100% different from Ubuntu's packaging in Hardy
[18:47] <jdong> that's what I meant, not to reinvent the packaging
[18:47] <Festor> what?
[18:47] <Festor> only changes Debian Policy
[18:47] <Festor> 3.7.2 -> 3.7.3
[18:47] <Festor> not?
[18:47] <jdong> where's transmission-cli, transmission-common and transmission-gtk?
[18:47] <Festor> ahhh
[18:47] <Festor> ok, ok
[18:48] <jdong> we don't need to reinvent the packaging from scratch, because we have existing packaging for it
[18:48] <Festor> but, only changes are add libnotify-dev
[18:48]  * jdong nods
[18:48] <Festor> jdong, getdeb is not a repos
[18:48] <Festor> is a web
[18:49] <Festor> more packages -> not good
[18:49] <jdong> yes but installing your package right now will cause dpkg overwrite errors on transmission-gtk and transmission-common
[18:49] <jdong> you are causing dpkg breakage by distributing these packages
[18:49] <Festor> only if you had installed those packages before
[18:49] <jdong> also, 1.10b1 is > 1.10
[18:50] <jdong> which means even final ubuntu 1.10 package will be overridden by these packages
[18:50] <Festor> 1.10b1 is temporaly
[18:50] <Festor> it is not will publisehd
[18:50] <jdong> Festor: it is getdeb's responsibility to ensure previous packages are not installed, then.
[18:50] <Festor> sorry for my bad English
[18:51] <jdong> Festor: if you would like to help with getting these bugfixes into Hardy, please file a launchpad bug on transmission, including that Trac link from earlier detailing all the bugfixes
[18:51] <YokoZar> Festor: Please use 1.10~whatever for any packages you publish.  The ~ means they'll be "lower" than anything that's the same before the ~ and will upgrade cleanly.  So 1.10 > 1.10~b1
[18:52] <jdong> Festor: I will lookthat over once I get back in town and make a decision on whether to isolate all the bugfixes or request that 1.10 in its entirety be put in Hardy.
[18:52] <Festor> ok, thanks YokoZar :D
[18:52] <jdong> Festor: does that sound reasonable?
[18:52] <YokoZar> Festor: Thanks :)  I do this with the unofficial Wine packages I make, by the way.  Works really well
[18:53] <Festor> yeah! I am a unofficial deb packager of aMule
[18:53] <Festor> http://forum.amule.org/index.php?topic=13836.0
[18:57] <emgent> hello people
[19:01] <YokoZar> Festor: do you do more amule development or just packaging?
[19:02] <Festor> packaging, translations, and a few patches
[19:03] <Festor> https://bugs.launchpad.net/ubuntu/+source/amule/+bug/204600
[19:03] <ubotu> Launchpad bug 204600 in amule "[hardy] Fix Spanish translation of aMule" [Undecided,Fix committed]
[19:03] <Festor> https://bugs.launchpad.net/ubuntu/+source/amule/+bug/197332
[19:03] <ubotu> Launchpad bug 197332 in amule "[hardy] aMule SVN warning on first run" [Undecided,Fix committed]
[19:04] <Festor> I like ubotu :D
[19:09] <slomo> dependency-wait is handled automatically, right?
[19:11] <ScottK2> slomo: Unless there's a soyuz bug.
[19:12] <slomo> ok, let's see what happens ;)
[19:13] <Festor> Well ... I will try to enter the MOTU again... xD
[19:15] <slytherin> Can anyone give me any pointers about OOo build failure on powerpc?
[19:19] <LaserJock> what's the best way to debug Network Manager?
[19:20] <\sh> gdb and attaching to NM pid?
[19:20] <slangasek> aptitude purge network-manager ;)
[19:20] <LaserJock> slangasek: not a bad idea, but I was hoping to be more helpful :-)
[19:21] <LaserJock> it seems like after the post-Beta update blitz NM no longer works for me
[19:21] <cody-somerville> slangasek, for some odd reason, I lost network connectivity when I ran that command.
[19:22] <slangasek> LaserJock: mm, I don't think network-manager was part of that blitz... hal and udev were though?
[19:22] <slangasek> (not sure if either of those is relevant either)
[19:23] <LaserJock> yeah, I first looked to see if somebody had uploaded a new NM and there wasn't
[19:23] <slangasek> slytherin: that build failure may point to an issue with debian/control listing different packages for powerpc than are actually being built
[19:23] <LaserJock> so I'm trying to figure out what it's having a problem with
[19:24] <slytherin> slangasek: Oh. I will check diff.gz But how come there is no problem in Debian? Or is it failing in Debian too?
[19:24] <slangasek> slytherin: the packaging is not the same between Debian and Ubuntu
[19:25] <slytherin> ahh
[19:25] <LaserJock> ok ... so NM dies a horrible death when it tries to connect but leaves a process eating up 99% of my cpu
[19:25] <Griswold> Is it possible to internationalize Gtk labels found in a .glade file?
[19:25] <slangasek> or rather, most of the packaging *is* the same, but the build takes very different paths through the packaging depending on which platform it's building fore
[19:25] <slangasek> s/e$//
[19:25] <LaserJock> I gotta run to lunch but if people have ideas I'll read the scrollback
[19:26] <slytherin> slangasek: is there anyone whom I can bug about this if I myself can't figure out?
[19:26] <slangasek> slytherin: calc, I imagine
[19:26] <slytherin> slangasek: Ok Thanks.
[19:38] <seb128> slangasek: I know it's really late in the cycle now, but do you think installing nautilus-share by default is still doable?
[19:38] <stgraber> I have the same problem as LaserJock with NM (taking 99%)
[19:38] <stgraber> the bug only appeared a few hours ago
[19:38] <slangasek> seb128: it's sufficiently limited in scope that I'm comfortable with that, yes
[19:38] <slangasek> seb128: do we also get to ditch shares-admin?
[19:39] <seb128> slangasek: ok, good
[19:39] <stgraber> asac: around ?
[19:39] <seb128> slangasek: yes, it's not working for anybody anyway
[19:39] <seb128> slangasek: it requires people to use smbpasswd from the command line to get anything shared
[19:40] <seb128> slangasek: for nautilus-share we should fix bug #204703 though
[19:40] <ubotu> Launchpad bug 204703 in samba "usershare: insuffisant permissions for anonymous login" [High,Triaged] https://launchpad.net/bugs/204703
[19:41] <slangasek> seb128: hmm?  I'm confused; didn't I just see (...reassign) a bug report /complaining/ that shares-admin makes all shares available anonymously?
[19:41] <slangasek> for that matter, nautilus-share manages usershares, and the default is to disallow anonymous access to usershares
[19:42] <seb128> oh, so it's not a bug?
[19:42] <seb128> mathiaz: ^
[19:42] <slangasek> I didn't think that it was a bug...
[19:42] <ScottK2> This is from Bug #204768: "The latest HAL update has changed the keys for checking for suspend and hibernation support." - Would someone please assure me we aren't uploading crack that changes function names after the beta without testing what it breaks?
[19:42] <ubotu> Launchpad bug 204768 in kde-guidance "[hardy] Latest HAL breaks guidance powermanager" [Undecided,New] https://launchpad.net/bugs/204768
[19:43] <seb128> slangasek: well, from a desktop point of view I'm looking for a way to share things over smb easily for user, and it looks like there is no way to do that at the moment
[19:43] <seb128> slangasek: we don't allow anonymous share and don't sync the user database on samba
[19:43] <ScottK2> slangasek: Do I patch Guidance to learn HAL's new language or is the above ^^^ some kind of mistake?
[19:44] <seb128> slangasek: which means it's not possible to share folder anonymously nor by using the user login setting
[19:44] <mathiaz> slangasek: even if the default is to disallow anonymous share, even if you define an anonymous share it doesn't work
[19:44] <slangasek> seb128: yes, but the plan discussed at UDS was "make it easy to integrate pam_smbpasswd so that all users have samba passwords by default"
[19:45] <seb128> slangasek: well looks like that didn't happen and mathiaz told me he thinks that's late now for hardy
[19:45] <slangasek> seb128: "let people share stuff anonymously" is a huge step back from that; I understand desktop users need sharing, but anonymous sharing gives me the hives
[19:45] <seb128> slangasek: I'm trying to limite damages there, if there is no way we should just remove any GUI doing smb sharing
[19:45] <slangasek> mathiaz: it's the smb.conf policy; you don't want to let usershare users override the global policy on anonymous sharing
[19:46] <mathiaz> slangasek: hm - so if smb.conf doesn't allow guests, then usershare with gest_ok = yes are not respected ?
[19:47] <seb128> slangasek: I think there is really a difference between user expectations and what we provide right now
[19:47] <slangasek> mathiaz: correct; you have to explicitly enable anonymous usershares before guest_ok=yes will work
[19:47] <seb128> slangasek: most of them want to share thing easily, which means they don't want to have to give login informations to let people browse their shares
[19:48] <slangasek> seb128: I agree; I'm just reluctant to address this by giving users an easy way to do anonymous shares with no way to do password-protected shares
[19:48] <seb128> slangasek: if we don't want to provide that I think we should just remove any sharing facility
[19:48] <seb128> slangasek: the way nautilus-share works is that shares are password protected unless you click on the anonymous option
[19:49] <slangasek> which everyone will have to do because we don't have the smbpasswd integration right :/
[19:49] <seb128> slangasek: but right, the pam integration didn't happen and we have to graphical way to add users to the smb database
[19:49] <slangasek> but yes, I concede that this is better than nothing
[19:49] <slangasek> mathiaz: usershare allow guests = yes
[19:49] <slangasek> let me see if I don't have a samba upload pending already, that I can add that to
[19:50] <seb128> the smbpasswd integration is not going to happen for hardy, right?
[19:50] <slangasek> I expect not
[19:51] <slangasek> I think the only option we had available for right now was auth-client-config
[19:51] <seb128> what is that?
[19:52] <mathiaz> jdstrand: ^^
[19:52] <slangasek> jdstrand's tool for swapping out pre-made PAM config settings
[19:52] <jdstrand> actually, it is pam and nss
[19:53] <slangasek> ScottK2: I didn't upload the hal change, and I don't believe it was cleared via FFe before upload; I guess you should check with pitti
[19:53] <seb128> the hal update is just a git snapshot to a stable candidate
[19:53] <ScottK2> slangasek: OK.  I'll check with him on Monday I guess.  Thanks.
[19:53] <seb128> which is likely a good thing
[19:53] <seb128> monday is an holiday
[19:53] <ScottK2> Tuesday then.
[19:54] <seb128> yes
[19:54] <seb128> but expect the current version to be a wanted change rather than a mistake
[19:54] <slangasek> ScottK2: in the source, I see a fdi/information/10freedesktop/01-deprecated-k
[19:54] <seb128> that's a git version to stable candidate one as said
[19:54] <slangasek> ... eys.fdi that lists both keys
[19:55] <slangasek> ScottK2: so it looks like this wasn't supposed to break
[19:55] <ScottK2> slangasek: OK.  I haven't looked into it beyond being annoyed at post-beta interface changes.  Thanks.
[19:56] <slangasek> seb128: if it's *wanted* to break interfaces post-beta, I agree with ScottK2 that this is not a good thing...
[19:56] <jdstrand> slangasek: on the topic of auth-client-config-- do you think a fix for this is appropriate for hardy-- https://bugs.launchpad.net/auth-client-config/+bug/179919 ?
[19:56] <ubotu> Launchpad bug 179919 in auth-client-config "No netgroup support" [Wishlist,In progress]
[19:56] <ScottK2> The rdepends for HAL, excluding meta packages is ~ two dozen, so I guess some testing is needed.
[19:57] <jdstrand> slangasek: I haven't done anything with the patch, as I thought this was a 'feature'
[19:57] <jdstrand> but maybe it's a bug...
[19:57] <slangasek> jdstrand: doesn't look appropriate to me
[19:57] <jdstrand> slangasek: that is what I thought.  thanks for looking at it :)
[19:57] <slangasek> looks like a feature enhancement, not a bugfix :)
[19:58] <jdstrand> tomato, tomato... wait...
[19:58] <seb128> slangasek, ScottK2: can_hibernate is the right interface for ages
[19:59] <slangasek> seb128: so?  you don't go deprecating interfaces post-beta without some kind of testing.  Anyway, I think this is just a packaging error, the new fdi file needs to be added to the Debian packaging
[19:59] <seb128> right, I think so
[19:59] <seb128> just pointing that upstream didn't change it between the git snapshot and the new update
[19:59] <seb128> that's just a compatibility patch not applied correctly most likely
[20:00] <seb128> but still, would be better to fix KDE to not use things deprecated for ages
[20:00] <seb128> and to fix hal to still have the compatibility thing in case something else is using it ;-)
[20:00] <slangasek> yes
[20:03] <seb128> ScottK2: those keys have been deprecated in 2006 btw, just for information
[20:03] <seb128> ScottK2: is this applications maintained?
[20:12] <seb128> slangasek: btw do you think it'd would be unreasonable to have samba installed but not running by default at some points? out of the CD space issue
[20:13] <slangasek> "at some point" meaning intrepid, right? :)
[20:13] <seb128> yes
[20:13] <slangasek> seems possible
[20:13] <seb128> at the moment we have this "you need to install samba to share this folder, do you want to install that now" dialog
[20:13] <seb128> but that requires people to have internet access, download it, etc
[20:14] <seb128> well, that's a one time thing, but still would be better to just have to enable something already installed
[20:16] <slangasek> yes
[20:21] <ScottK2> seb128: It's slightly maintained, but will not transitionto KDE4.
[20:21] <ScottK2> seb128: It's just awfully late in the process to be breaking stuff.
[20:25] <seb128> ScottK2: it doesn't seem to be a wanted breakage and as written those key are deprecated for years, anyway will like be fixed next week but you should still update your broken software to not use deprecated things
[20:25] <seb128> s/like/likely
[20:27] <slangasek> ScottK2: hal uploaded
[20:28] <seb128> slangasek: that was quick ;-)
[20:28] <LaserJock> stgraber: find anything about NM yet?
[20:28] <slangasek> why wait? :)
[20:28] <seb128> slangasek: right ;-)
[20:28] <slangasek> cody-somerville: xubuntu alternates are built and right-sized, 20080321; would you like me to put these on the ISO tracker for consideration as beta candidates?
[20:29] <stgraber> LaserJock: not really, I tried a rebuild of the package (in case it was related to the new hal) but that didn't help
[20:29] <cody-somerville> slangasek, yes please
[20:29] <cody-somerville> link?
[20:30] <LaserJock> where are the -dbg packages located? I don't see them on LP
[20:31] <ScottK2> slangasek: Thanks
[20:31] <stgraber> LaserJock: ddebs.ubuntu.com
[20:31] <LaserJock> nvm, found them on archive.u.c
[20:32] <ScottK2> seb128: The software is unlikely to exist past Hardy, so more fixing that is absolutely needed is a waste of time.
[20:32]  * ScottK2 is busy enough fixing python-central related breakage.
[20:33] <stgraber> LaserJock: the dbg package doesn't help that much here
[20:33] <slangasek> cody-somerville: added
[20:33] <stgraber> LaserJock: the missing symbol was just 0x00007f01beb02cc6 in poll () from /lib/libc.so.6
[20:33] <LaserJock> I see
[20:33] <LaserJock> no indication of why it crashes?
[20:34] <stgraber> not really, if only it crashed completely, that would help :)
[20:34] <LaserJock> yeah
[20:34] <slangasek> stgraber: strace?  lsof?
[20:35] <stgraber> in my opinion it crashes exactly when it's supposed to start wpa_supplicant
[20:35] <slangasek> (to find out what it's polling so urgently)
[20:35] <LaserJock> I don't have wpa
[20:37] <LaserJock> I do have a funky device showing up though, wlan0_rename
[20:38] <stgraber> it enters some kind of segfault loop here
[20:38] <stgraber> [pid 14801] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
[20:38] <stgraber> [pid 14801] rt_sigreturn(0xb)           = 0
[20:47] <LaserJock> stgraber: you don't suppose it's a HAL issue do you?
[20:47] <stgraber> well, I checked hardy-changes between the time NM was working and the time it was not working
[20:47] <stgraber> then I had a look at NM's build-dep and only found hal
[20:48] <ScottK2> Maybe NM uses one of the deprecated keys too?
[20:48] <LaserJock> that's what I'm wondering
[20:48] <\sh> .oO(surprise surprise?)
[20:49] <ScottK2> LaserJock: You could grab the source for the latest upload build it and see if it helps (or just wait for it to appear on your local mirror).
[20:49] <stgraber> I shouldn't break my whole system by downgrading hal right ?
[20:51] <LaserJock> ScottK2: if I'm lucky and have all the build deps on my machine. I have to build it on the one with no network
[20:51] <ScottK2> Yeah.
[20:51] <ScottK2> LaserJock: What architecture?
[20:52] <stgraber> I'm uploading to my local builder, starting with amd64
[20:53] <LaserJock> ScottK2: amd64
[20:53] <ScottK2> LaserJock: OK.  Can't help you there.  Sorry.
[20:53] <LaserJock> stgraber: you're building an amd64 .deb?
[20:53] <stgraber> LaserJock: yep
[20:53] <LaserJock> stgraber: mind sharing the love :-)
[20:54] <stgraber> sure, will upload that somewhere
[20:54] <LaserJock> awesome, thanks
[21:00] <stgraber> LaserJock: http://www.stgraber.org/download/ubuntu/hal/
[21:01] <YokoZar> Will Hardy be available on DVD for things like shipit?  On Gutsy the DVD image seemed less official in a way since there was no packaged version.
[21:05] <stgraber> LaserJock: it works here !!!
[21:12] <LaserJock> stgraber: what kind of wifi card do you have?
[21:12] <stgraber> LaserJock: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection
[21:12] <stgraber> that's a ABGN card
[21:13] <LaserJock> ah, mine is an intel 4945 I think
[21:13] <seb128> what is the issue?
[21:13] <LaserJock> so because of the hal thing NM couldn't find the driver
[21:13] <LaserJock> in syslog it said the driver was 'null'
[21:14] <LaserJock> now it says 'ipw3945'
[21:14] <stgraber> seb128: NM entering in a segfault loop with pitti's hal
[21:14] <ScottK2> stgraber: Pretty please make the 4965 work.  My production laptop (that's still on Gutsy) has that one.
[21:15] <stgraber> ScottK2: works just fine here :) (when hal is not broken)
[21:15] <seb128> stgraber: what version it's pitti's one?
[21:15] <seb128> stgraber: or you mean current hardy one?
[21:15] <stgraber> hal (0.5.11~rc2-1ubuntu1)
[21:15] <LaserJock> seb128: right, the one before slangasek fixed it :-)
[21:16] <stgraber> hal (0.5.11~rc2-1ubuntu2) from slangasek fixes it
[21:16] <seb128> ok
[21:16] <seb128> so it's already fixed ;-)
[21:17] <LaserJock> so I guess NM needs to be fixed to not use the deprecated keys :-)
[21:17] <ScottK2> stgraber: Thanks for setting my mind at ease.
[21:17] <ScottK2> LaserJock: For Intrepid, I agree.
[21:17] <slangasek> oh, -1ubuntu2 fixes NM as well?
[21:18] <slangasek> interesting
[21:18] <LaserJock> slangasek: yep
[21:19] <ScottK2> slangasek: You're way more of a hal fixing genius than you even knew.
[21:19] <\sh> or NM is far beyond time ;)
[21:19] <seb128> slangasek: network-manager seems to be using net.physical_device which is a 01-deprecated-keys.fdi thing
[21:20] <slangasek> aha
[21:20] <seb128>       <!-- *.physical_device - finally removed: 2008-03-03 -->
[21:20] <seb128> that is a recent thing
[21:20] <seb128> compared to the can_suspend and can_hibernate
[21:21] <seb128> slangasek: anyway well done for the quick fixing ;-)
[21:22] <slangasek> :)
[21:22] <seb128> asac: ^ you might want to update network-manager to use the new net.originating_device
[21:22] <LaserJock> slangasek: yeah, I would have had to work  in OS X all day if you hadn't of :-)
[21:24] <slangasek> heh
[21:24] <Kopfgeldjaeger> affili.net reflink?
[21:31] <sebner> slangasek: still around?
[21:35] <slangasek> sebner: yes
[21:35] <sebner> slangasek: would you mind unsubscribing ubuntu-release from bug #203298 and bug #203314 ?
[21:35] <ubotu> Launchpad bug 203298 in gtk-sharp2 "[FFe] Merge gtk-sharp2 2.12.0-2 from Debian(Unstable)" [Undecided,Fix released] https://launchpad.net/bugs/203298
[21:35] <ubotu> Launchpad bug 203314 in gnome-sharp2 "[FFe] Merge gnome-sharp2 2.20.0-2 from Debian(Unstable)" [Undecided,Fix released] https://launchpad.net/bugs/203314
[21:35] <slangasek> sebner: if it's "fix released", it doesn't matter?
[21:36] <sebner> slangasek: though I set it to Fix Released? ^^
[21:45] <cjwatson> hefe_bia_: calc (Launchpad id ccheney) has been marking OOo bugs in-progress to indicate that he's planning to work on them for hardy
[21:47] <hefe_bia_> cjwatson: thanks, good to know :)
[21:48] <cr3> might it be possible that python-lxml has been removed from the hardy repositories? I can't seem to find it under: http://archive.ubuntu.com/ubuntu/pool/(main|universe|multiverse)/p/
[21:49] <slangasek> cr3: because the source package name is lxml
[21:49]  * ScottK hands cr3 https://launchpad.net/ubuntu/+source/lxml
[21:49] <cr3> not that I'm sure it was ever there
[21:50] <cr3> slangasek: cheers man, my repo cache seems b0rked :(
[21:52] <cr3> all good now, always helps to know what's supposed to work :)
[22:01] <ion_> I wonder what has added commit=360 to my root partition's mount options? Didn't find the string under /etc/init.d or /usr/share/initramfs-tools.
[22:10] <ion_> Ah, laptop-mode-tools.
[22:23] <sistpoty> doko: please give back missingh on sparc, thanks!
[22:32] <mi> can i do upgrade 7.10 to 8.04 with envy driver or i must first uninstall evny ?
[22:33] <ScottK> You should ask wherever you got envy or in #ubuntu+1
[22:33] <mi> tq
[22:34] <emgent> heya imbrandon :)
[22:57] <slomo> hrm, can someone tell me why mono fails to build in ubuntu but builds fine in debian with the same source? see http://launchpadlibrarian.net/12799642/buildlog_ubuntu-hardy-i386.mono_1.2.6%2Bdfsg-6ubuntu2_FAILEDTOBUILD.txt.gz for example, only happens on x86/amd64/lpia
[23:02] <doko> why doesn't mono use the system boehm-gc?
[23:04] <slomo> doko: because of mono specific changes... one can build it with the system one but it's very unreliable then
[23:28] <Kopfgeldjaeger> n8
[23:37] <rhineheart_m> hello. is this bug has been fixed already and added to the repo? Bug #156748
[23:37] <ubotu> Launchpad bug 156748 in iperf "Thread library bug for kernel >= 2.6.21" [Unknown,Fix released] https://launchpad.net/bugs/156748