[00:01] <Spirits-Sight> how do I start the gnome shell and exit safely?
[00:01] <bjsnider> gnome-shell --replace
[00:01] <bjsnider> metacity --replace
[00:01] <Spirits-Sight> thanks
[00:05] <Spirits-Sight> bjsnider: its saying some thing about Clutter requiring, version none I thought that 10.04 would have that and the user / tester would be able to test it with the command you said?
[00:05] <alex_mayorga> Is it a known problem like this: I get to the login screen on the live cd, click the default user and the screen flickers blank and I'm back at the login screen
[00:05] <bjsnider> Spirits-Sight, gnome-shell does not currently work in lucid AFAIK
[00:06] <Spirits-Sight> bjsnider: thanks
[00:06] <Spirits-Sight> OK I will have to wait to check out whats new huh? :(
[00:06] <bjsnider> it works in karmic
[00:07] <Spirits-Sight> I know, I used it before, I wanted to see if they had changed any thing :-)
[00:07] <bjsnider> in a couple of weeks it will be refreshed i'm sure
[00:07] <Spirits-Sight> coool
[00:07] <Spirits-Sight> thanks
[00:08] <bjsnider> these are the holidays so developers are out holidaying and whatnot
[00:08] <Spirits-Sight> true true
[00:14] <ubnuut> OMG why the hell doesn't Ubuntu come with an IRC client?!??!?!?
[00:15] <ubnuut> I have to use some silly webchat.
[00:15] <BUGabundo> ubuntulog: don't be even more stupid....
[00:16] <ubnuut> BUGabundo: I beg you're pardon?
[00:16] <BluesKaj> ubnuut, it does ..quassel
[00:16] <BUGabundo> there are so many IRC apps in the archive
[00:16] <ubnuut> There are no IRC clients on the ISO.
[00:16] <bjsnider> pidgin, xchat...
[00:17] <bjsnider> konversation
[00:17] <ubnuut> None of those come with Ubuntu.
[00:17] <bjsnider> irssi
[00:17] <BUGabundo> ubuntulog: install one
[00:17] <BUGabundo> so what?
[00:17] <alex_mayorga> ubnuut: theres empathy I believe
[00:17] <penguin42> does the pidgin replacement not do irc?
[00:17] <BUGabundo> it also doenst bring all languages
[00:17] <BUGabundo> or full OOo
[00:17] <BUGabundo> or codecs
[00:17] <BUGabundo> or many games
[00:18] <BUGabundo> so what's the prob?
[00:18] <alex_mayorga> empathy can be used as an IRC client
[00:18] <BUGabundo> install one of your choice
[00:18] <bjsnider> or any of the restricted extras
[00:18] <ubnuut> I don't want to install an IRC client on a Live CD.
[00:18] <ubnuut> It should be there.
[00:18] <BUGabundo> alex_mayorga: yes it can
[00:18] <alex_mayorga> or drivers that work with my video card =S
[00:18] <penguin42> hmm, there's an argument that if there isn't an obvious irc client on the livecd it's a problem
[00:18] <ubnuut> A Live CD should include all the basic tools.
[00:18] <BUGabundo> ubuntulog: I don't want to install Chromium, it should be there ... pfff
[00:18] <BUGabundo> IRC is NOT a basic tool
[00:19] <ubnuut> BUGabundo: Ubuntu comes with a web browser.
[00:19] <ubnuut> penguin42: It seems not to.
[00:19] <BluesKaj> ubnuut, quassel came with ky install, so dunno what install you used but....
[00:19] <ubnuut> Empathy SHOULD allow IRC.
[00:19] <BUGabundo> it does
[00:19] <BluesKaj> err my
[00:19] <penguin42> BUGabundo: It's pretty useful if people can get here or to #ubuntu if they're having a problem with an insta;;
[00:19] <ubnuut> BluesKaj: 9.10
[00:20] <BUGabundo> penguin42: most NEW users only know about Foruns
[00:20] <bjsnider> ubnuut, if you're on the livecd, and it does not have irc capability, then how are you in this room?
[00:20] <BUGabundo> or better, about GOOGLE
[00:20] <BUGabundo> and google will not point them to IRC
[00:20] <ubnuut> Does 10.04 alpha 1 bring anything new compared to 9.10?
[00:20] <ubnuut> bjsnider: Webchat
[00:20] <bjsnider> well, then i guess it kinda does have irc capability
[00:20] <BUGabundo> alpha1 is old
[00:20] <ubnuut> bjsnider: Sure, let's remove OpenOffice and use Google Docs
[00:20] <BUGabundo> check technical overview wiki page
[00:21] <penguin42> BUGabundo: Really? I agree not newbie computer users, but possibly newbie linux users; I know plenty of non-linux ircers, and if you are having a problem with an install or the other use of a live cd - a rescue - then irc is very useful
[00:21] <BUGabundo> ubuntulog: if you don't like , start a blueprint, purpose discussion, and take it to the UDS
[00:22] <bjsnider> BUGabundo, that's not his alias
[00:22] <BUGabundo> lol
[00:22] <BUGabundo> FAIL
[00:22] <BUGabundo> I better go to bed then
[00:22] <BUGabundo> I can't read my own screen
[00:23] <BUGabundo> ubnuut: : if you don't like , start a blueprint, purpose discussion, and take it to the UDS
[00:23] <ubnuut> Rather than download Alpha 1, what image should I download to test 10.04?
[00:23] <ubnuut> Daily?
[00:24] <alex_mayorga> ubnuut: I would think so
[00:24] <BUGabundo> !daily > ubnuut
[00:24] <alex_mayorga> as there are no hourly
[00:24] <BUGabundo> alex_mayorga: touché
[00:24] <alex_mayorga> !daily > alex_mayorga
[00:25] <ubnuut> Is 10.04 going to get RGBA transparency glass windows?
[00:26] <alex_mayorga> BUGabundo, how do I force VESA on the daily CD?
[00:26] <ubnuut> alex_mayorga: Safe graphics mode
[00:30] <alex_mayorga> ubnuut: thanks, I'll try that
[01:08] <crimsun> bjsnider: stop attempting to put words in my mouth
[01:11] <BUGabundo> lolol
[01:17] <bjsnider> crimsun, sorry, i didn't think i was doing that
[03:40] <ripps> My wacom graphire3 is acting funky. The hover over mouse stops working after I've clicked. Does anybody know how to fix this?
[03:42] <ripps> Does anybody think installing the xorg-xi2 ppa will help?
[04:38] <alex_mayorga> can anyone confirm https://bugs.edge.launchpad.net/ubuntu/+source/software-center/+bug/501208
[04:45] <IdleOne> alex_mayorga: confirmed
[04:46] <alex_mayorga> thanks
[04:47] <alex_mayorga> other than that and the broken nvidia lucid is rock solid here
[04:47]  * alex_mayorga knoks on wood
[04:47] <bjsnider> nvidia is not precisely broken
[04:48] <bjsnider> all 3 drivers in the nvidia-vdpau ppa work fine
[04:53] <alex_mayorga> bjsnider I believe my card calls for 195, would it be messy later if I use the ppa for now?
[04:54] <bjsnider> you mean jockey is recommending the 195?
[04:55] <alex_mayorga> now, the page manufacturer recommnds
[04:55] <bjsnider> what?
[04:56] <alex_mayorga> jockey icon didn't appear after some reboots
[04:56] <alex_mayorga> let me go in the menu, see what it says
[04:57] <alex_mayorga> jockey recommends 185
[04:57] <alex_mayorga> nvidia site says 195
[04:57] <bjsnider> no, i don't think so
[04:57] <bjsnider> you're probably looking at the windows site
[04:57] <alex_mayorga> this card http://www.nvidia.com/object/product_geforce_gt_230m_us.html
[04:58] <alex_mayorga> sorry is 190
[04:59] <alex_mayorga> http://www.nvidia.com/object/linux_display_ia32_190.53.html
[04:59] <bjsnider> that has a purevideo generation 4 chip
[05:00] <bjsnider> that can do vdpau on practically any video type that you'll run into
[05:00] <bjsnider> if vdpau is your primary concern, go with the 195. if not, stick with the safe 190 choice
[05:01] <bjsnider> that chip can accelerate all mpeg4 including vc1/h264 and divx/xvid and also wmv3 and all mpeg2
[05:01] <alex_mayorga> bjsnider, is it a bug that jockey suggests 185?
[05:02] <bjsnider> have you got an hdmi port on that laptop?
[05:02] <alex_mayorga> yes
[05:02] <bjsnider> awesome
[05:02] <alex_mayorga> 1 HDMI
[05:02] <bjsnider> so you could connect it to an hdtv and use it as an htpc
[05:02] <alex_mayorga> now I need a hdmi to rf adapter :)
[05:02] <bjsnider> no, you need an hdtv
[05:02] <alex_mayorga> that'd work too
[05:03] <bjsnider> does is have a bluray drive?
[05:04] <alex_mayorga> no, I don't think
[05:05] <alex_mayorga> here's some info http://3wg.blogspot.com/2009/12/either-vaio-vpccw1ffxl-lasts-one-month.html
[05:05] <bjsnider> well, anyway, add the ppa and update jockey and install the modaliases packages and then it will recommend the 195 driver
[05:06] <alex_mayorga> I don't support bluray or other encryption drmy stuff
[05:07] <alex_mayorga> bjsnider, I heard that would be on mainline on a couple of days, should I wait?
[05:07] <bjsnider> well it doesn't appear that you need to worry about that since i guess it doesn't have a bluray drive
[05:08] <bjsnider> it's up to you, if that's actually the case
[05:08] <alex_mayorga> bjsnider, do you have a win32 background?
[05:08] <bjsnider> how do you mean?
[05:08] <alex_mayorga> in the post to my blog there were a couple of problems I initally had with the machine on win7
[05:09] <alex_mayorga> is it possible wubi caused them?
[05:09] <bjsnider> i troubleshoot windows machines for a living
[05:10] <alex_mayorga> had I known that I wouldn't have lost my vacation pics :(
[05:11] <bjsnider> could wubi have caused the unmountable boot volume? is that the question?
[05:11] <bjsnider> you can recover deleted data, even data from previous partitions
[05:12] <alex_mayorga> yes, yes and enlighten me I'd be so happy to recover my pictures
[05:13] <alex_mayorga> is there a recovery tool I can run from ubuntu itself?
[05:13] <bjsnider> how soon after you installed wubi did you get the unmountable boot volume error?
[05:14] <alex_mayorga> 2-3 days
[05:14] <bjsnider> howo many times did you boot successfully after you installed it?
[05:15] <alex_mayorga> once, then it got screwed by one bug, let me dig
[05:18] <alex_mayorga> https://bugs.edge.launchpad.net/wubi/+bug/477169
[05:18] <alex_mayorga> that's the wubi bug that bit me
[05:19] <alex_mayorga> then some days after win7 got screwy too
[05:19] <alex_mayorga> bjsnider, is there a tool I can use inside ubuntu to try recover my files?
[05:20] <bjsnider> nott hat i know of
[05:20] <bjsnider> do you still have windows 7 on there?
[05:21] <alex_mayorga> Will lynx ship flash 10.1?
[05:21] <alex_mayorga> bjsnider: no I got rid of it and let ubuntu take the whole drive
[05:22] <bjsnider> ok, well we use a tool called diskinternals to recover data. it will cost you over $100 and you have to install it in windows
[05:24] <r00t_> Theres no free alternative or at least a torrent with a cracked app? 100$ is alot to spend on a program..
[05:24] <bjsnider> he still has the windows issue though
[05:25] <bjsnider> he has to install it there
[05:26] <bjsnider> plus he altered the nature of the warranty because the warranty guys will need windows there to do testing
[05:26] <bjsnider> those guys can't test for a live/dead lan card using linux. their decision trees are all using windows
[05:27] <bjsnider> ...and in all likelihood there was or is a ghost image on a hidden partition for recovery that he may have blown away by installing linux and repartitioning
[05:30] <alex_mayorga> is no big deal, I've already accepeted the loss
[05:31] <alex_mayorga> but in reality the files might be still "there"
[05:31] <alex_mayorga> testdisk maybe?
[05:32] <bjsnider> the files pretty much certainly are still there. they don't show up because the entries in the master file table, and indeed the entire mft itself is gone. but the ones and zeros on the drive itself are there
[05:33] <alex_mayorga> some sites suggest testdisk
[09:19] <BUGabundo_work> morning
[09:45] <cwillu_at_work> BUGabundo_work, here's one for ya :)
[09:45]  * cwillu_at_work huggles
[09:46] <cwillu_at_work> (that wasn't it)
[09:47] <cwillu_at_work> firefox, open a couple tabs, and kill it.  Reopen it, and open some new tabs in addition to the "restore session" tab, which you should ignore for now.  Kill it again
[09:47] <cwillu_at_work> Previously, you would get a 'nested' session restore on the next run:  restoring the session brings back the "restore session" tab with the session - 1 tabs.
[09:47] <cwillu_at_work> This is a good thing.
[09:48] <cwillu_at_work> Now, it seems to just repeat the outer session's tabs, which is definitely wrong.
[09:48] <cwillu_at_work> Glitch, or repeatable on machines other than mine?
[09:52] <cwillu_at_work> also, is there really no clock sync set up by default?
[09:53] <cwillu_at_work> The problem with upgrading one's main system since warty is that one's main system doesn't get all the new config brokenness :p
[10:38] <BUGabundo_work> hi cwillu_at_work
[10:38] <BUGabundo_work> well i dont know
[10:38] <BUGabundo_work> i dont use FF session manager
[10:39] <BUGabundo_work> i use tabmixplus
[10:39] <BUGabundo_work> never manage to get Session Manager stock to work jus ti like it
[10:40] <cwillu_at_work> tabmixplus is just a frontend on the session manager afaik
[10:40]  * cwillu_at_work is referring to the crash handler
[10:41] <cwillu_at_work> i.e., "kill" -> killall -KILL firefox
[10:45] <BUGabundo_work> cwillu_at_work: TMP has it own handler, and crash recover
[10:46] <BUGabundo_work> elky: LOLOL
[10:46] <BUGabundo_work> elky: venting too much?
[10:46] <cwillu_at_work> BUGabundo_work, intriguing.  I'm tempted to ask if it actually works, but I have a particular usecase in mind for "works"
[10:46] <cwillu_at_work> specifically, how does it handle 200-300 open tabs across a dozen or so windows?
[10:47] <cwillu_at_work> (the default just "goes away" for 5-10 seconds each time it saves state, which is less than ideal)
[10:50] <BUGabundo_work> cwillu_at_work: ?
[10:51] <cwillu_at_work> BUGabundo_work, typically a crash handler works by maintaining some state while things are working fine, such that it doesn't handle the crash so much as keep good records to allow rebuilding after a crash
[10:51] <cwillu_at_work> the default firefox one is very costly when you have lots of data to be stored, because it stores the entire state at each checkpoint
[10:52] <cwillu_at_work> ext3, by comparison, keeps both a full state and a running log, where things that aren't in the state are stored in the log until the full state can be updated (as opposed to completely rewritten)
[10:53] <cwillu_at_work> and I was curious how tmp handled that
[10:54] <cwillu_at_work> BUGabundo_work, and having checked the site, it's just using firefox's crash handler
[10:54] <cwillu_at_work> which makes me sad :(
[10:54] <cwillu_at_work> http://tmp.garyr.net/help/#Session_-_Restore
[10:56] <cwillu_at_work> it's basically like performing a full system backup every ten minutes in case your computer crashes.  Yes, it works, but it's horribly wasteful if you have a big system
[10:56]  * cwillu_at_work has a big firefox :)
[10:58]  * BUGabundo_work as a bigger FF and runs 3 3.5 and 2 3.7 profiles
[10:58]  * BUGabundo_work mouth ducks elky
[10:58] <BUGabundo_work> .p
[10:59] <BUGabundo_work> cwillu_at_work: well dear, start a new profile, install TMP, *set to use its own TMP crash handler*, open 5 wind, 20 tabs, kill it, reopen and watch wonders
[10:59] <cwillu_at_work> BUGabundo_work, the word in -offtopic is that the ubuntu ops are getting attacked by some dcc spam or some such
[11:00] <cwillu_at_work> BUGabundo_work, citation needed
[11:01] <cwillu_at_work> I see no evidence that tmp has its own crash handler
[11:01] <cwillu_at_work> in fact I'm now pretty certain it doesn't
[11:05] <BUGabundo_work> cwillu_at_work: ok...
[11:05] <BUGabundo_work> if so, nothing to do
[11:05] <BUGabundo_work> i never had much trouble with it
[11:06] <BUGabundo_work> chromium session manager is way suckier
[11:06] <cwillu_at_work> multiple sessions are about the only way of scaling large firefox sessions, I'm loath to do it though
[11:06] <cwillu_at_work> ah well
[11:42] <bbalajirao> Pidgin not able to connect to yahoo chat. any ideas?
[12:16] <om26er> !test
[12:26] <lepr> I see Lucid Lynx is scheduled to freeze about the same time as Squeeze.  Will or might Lucid Lynx incorporate packages based on Squeeze?
[13:15] <BUGabundo_work> lepr: AFAIK sync already happen , and just happens on request
[13:17] <cwillu_at_work> BUGabundo_work, can you check something for me?  In keyboard prefs | layouts | layout options | keys to change layout, select "both alt keys together", and tell me if your right alt key stops working (i.e., right-alt + f in firefox no longer pulls up the file menu, but left-alt + f does)
[13:30] <BUGabundo_work> cwillu_at_work: i'm at work. debian unstalbe here
[13:31]  * cwillu_at_work puts BUGabundo_work to work? :p
[14:25] <zer0x> Can anyone confirm there are problems with the nv driver and Xorg crashes on Alpha 1?
[14:27] <SwedeMike> zer0x: I haven't tested since the days before christmas, but my nvidia xorg (default conf) hasn't worked since beginning of december
[14:29] <zer0x> SwedeMike: ah, just to clarify thats the open nv driver, not the closed nvidia driver?
[14:30] <SwedeMike> zer0x: it's the one you get default without installing "restricted drivers"
[14:30] <zer0x> SwedeMike: cheers :D
[14:30] <SwedeMike> I haven't tried to install the nvidia drivers, it's just a lab machine
[14:33] <zer0x> I'll be testing them soon, I'm hoping rtl8192e wireless is working with 2.6.32+ (just got a nvidia ION enabled netbook to play with :)
[14:34] <BUGabundo_work> humm
[14:35] <BUGabundo_work> i may need newer drivers for ION then those in archive
[14:35] <zer0x> uh oh :)
[14:36] <zer0x> I read you need to use entire disk with the Alpha 1 install is this also true?
[14:36] <BUGabundo_work> entire disk !?
[14:37] <BUGabundo_work> why ??
[14:37] <BUGabundo_work> plus use dailies builds instead of alpha
[14:37] <BUGabundo_work> !daily
[14:37] <zer0x> lol, true! :)
[14:38] <zer0x> It was just something I read a while back, I thought it sounded a bit odd.. but hey..
[14:40] <bjsnider> BUGabundo_work, so you agree with me that there should not even _be_ alpha releases
[14:41] <bjsnider> because people test them when they should be testing the dailies
[14:42] <zer0x> I had totally forgotten about the daily builds, I usually keep away from the edge!
[14:43] <bjsnider> we get people coming in here a week after an alpha release reporting bugs that have been fixed already because they went back and installed the alpha, which is now old news
[14:45] <zer0x> I can imagine that is an annoyance, maybe as an alternative to no alphas there should be a link to the dailys on alpha page of the website?
[14:45] <ToxinPowe> if people do updates with their alphas no problem at all
[14:47] <bjsnider> zer0x, but then why offer an alpha at all, if you're just linking to the daily-livecd?
[14:47] <BUGabundo_work> bjsnider: milestones
[14:48] <zer0x> I guess, I like the OpenBSD setup, RELEASE, STABLE, CURRENT and SNAPSHOTS :)
[14:48] <SwedeMike> I'd say the daily livecd isn't guaranteed to boot at all, whereas the alpha1 actually has been a little tested :P
[14:48] <BUGabundo_work> to have a set point in time where we (not users but devs) know and can point (target) stuff
[14:48] <BUGabundo_work> "users" are not supposed to "test" until around beta
[14:48] <bjsnider> oh come on. that'snot true
[14:49] <BUGabundo_work> bjsnider: it is
[14:49] <bjsnider> they want more testing to find bugs
[14:49] <BUGabundo_work> just a bunch of "us" in +1 run the entire dev cycle
[14:49] <BUGabundo_work> "we" dont care about milestones
[14:49] <BUGabundo_work> SwedeMike: +1
[14:50] <bjsnider> i don't know why milestones are so important. just release the stuff when it is done
[14:50] <SwedeMike> bjsnider: ah, the old debian way, then you get 1 year delays
[14:50] <SwedeMike> if there is no rush, why not wait another week?
[14:50] <SwedeMike> milestones are good.
[14:51] <bjsnider> SwedeMike, if it doesn't boot, i guess you took that into account when you decided to install a development series, didn't you?
[14:51] <SwedeMike> bjsnider: yes. you're missing my point totally.
[15:01] <zer0x> Are there still PS3/Cell ports of ubuntu?
[15:04] <zer0x> oh yes, oops :) I can't believe sony disabled install other os on the new slim models :(
[15:09] <BUGabundo_work> eheh
[15:10] <BUGabundo_work> but i've read its still possible
[15:22] <zer0x> I like to think where theres a will theres a way! One day I'll try that cell port of Gnu backgammon! :D
[15:36] <benste> hi, does so else have no user on the daily live ? - no auto login and no login with user "ubuntu"
[15:41] <BUGabundo_work> no idea benste
[15:41] <BUGabundo_work> last time i used it , it worked
[15:41] <BUGabundo_work> did u check ISO md5?
[15:41] <benste> BUGabundo_work: no i didn't - I'm using zsync to get it so I persumed that it would be ok
[15:42] <benste> BUGabundo_work: how can I use md5sum to check ?
[15:42] <BUGabundo_work> oh ok
[15:42] <BUGabundo_work> yes zync should take care of that
[15:42] <BUGabundo_work> unless u try to do like i do, and get both kubuntu and ubuntu images at the same time
[15:42] <BUGabundo_work> to the same file :S
[15:43] <BUGabundo_work> benste: download the md5 file, put in the same dir, and $ md5sum -c md5sum.txt
[15:43] <benste> thx
[15:44] <benste> BUGabundo_work: by the way do you know when the daily build get build ? midnight CET ?
[15:44] <BUGabundo_work> no idea
[15:45] <BUGabundo_work> i may zsync to a previous one and test
[15:46] <benste> - md5 sum is ok
[15:46] <benste> may be kind of you if you'd sync the latest daily and try to get into GUI
[15:57] <BUGabundo_work> not at home
[15:57] <BUGabundo_work> no mirror here
[15:58] <zer0x> benste: I just installed the daily-live/current and it works fine for me
[15:58] <zer0x> now I just need to find that rtl8192e firmware!
[16:19] <benste> zer0x: did you install from text mode or GUI ?
[16:19] <benste> (choosing first or 2nd option in grub)
[16:20] <alex_mayorga> My laptop doesn't like the WPA network this morning, was working just fine last night, ideas?
[16:32] <BUGabundo_work> anyone whilling to do me a quick test?
[16:32] <BUGabundo_work> need to verify its not my kernel messing up
[16:33] <BUGabundo_work> hggdh: bjsnider: around
[16:33] <benste> alex_mayorga: you're using Lucid A1 ?
[16:33] <benste> what is stdin erorr0 ?
[16:33] <BUGabundo_work> yofel: ^^^^
[16:34] <bjsnider> yeah, what do you need?
[16:34] <BUGabundo_work> n2n test
[16:34] <yofel> BUGabundo_work: pong
[16:34] <BUGabundo_work> it was working up to one week ago
[16:34] <BUGabundo_work> now it doesnt
[16:34] <BUGabundo_work> one of you install n2n package
[16:35] <BUGabundo_work> launch server $ supernode -l 7777
[16:35] <BUGabundo_work> and client $ sudo /usr/sbin/edge -c f -a <IP_ADDRESS> -c f -k f -l <IP_ADDRESS>:7777
[16:35] <BUGabundo_work> see if it works
[16:35] <BUGabundo_work> my system fails with a c end file message
[16:35] <BUGabundo_work> in this debian machine works fine
[16:36] <yofel> ERROR: ioctl() [No such file or directory][2]
[16:37] <BUGabundo_work> DAMN IT
[16:37] <BUGabundo_work> what the heck changed last week that could affect that?!?
[16:39] <alex_mayorga1> benste: appologies, I just loaded the daily CD for today, will let you know if it happens once again
[16:40] <benste> thx that's nice
[16:40] <benste> alex_mayorga1 fyi download with zsync takes about 1 min !
[16:41] <alex_mayorga1> benste: thanks on the tip
[16:41] <benste> i've learned it some days agi :-) and blogged about it
[16:42] <alex_mayorga1> odd, I'm trying the 64 bit now and it just stalls after I entered my password on first boot, is that known, normal?
[16:42] <alex_mayorga1> 32 bit worked just fine
[16:43] <alex_mayorga1> never mind, is this lousy HD on my christmas laptop
[16:44] <alex_mayorga1> never buy Sony VAIOs with Toshiba HDs if you can help it
[16:45] <alex_mayorga1> anyne, clos to the Texas/Mexico border that want to help me make a warranty good?
[16:47] <alex_mayorga1> the thing is just 3 weeks old
[16:48] <alex_mayorga1> This is HD issue, firght? "error: {UNC}"
[16:50] <alex_mayorga1> I thought the installer checked for badblocks, doesn't it?
[16:52] <zer0x> benste: sorry afk, from GUI, I noticed the stdin error also
[16:54] <zer0x> alex_mayorga1: that would take it a long time :)
[16:56] <alex_mayorga1> how do I force a fsck -cc on the reboot?
[16:57] <benste> alex_mayorga1: wrote you a PM about your other problem
[17:01] <alex_mayorga1> benste: thanks!
[17:01] <alex_mayorga1> anyone on how to force fsck to makr badblocks on reboot?
[17:02] <alex_mayorga1> I seem to have booted, and I'm now in one of the tty, where's the GUI alt+ctrl+?
[17:02] <zer0x> alex_mayorga1: you can force a normal fsck at reboot with 'sudo touch /forcefsck'
[17:03] <zer0x> alex_mayorga1: but I think you will need to use the badblocks program to do a full check
[17:03] <alex_mayorga1> zer0x: thanks, do you happen to know how to go about doing it?
[17:05] <om26er> what kernel version(exactly) 2.6.32-9 is?
[17:05] <zer0x> alex_mayorga1: I would boot from a livecd and do it on the raw block device, check man badblocks though and make sure you don't do a destructive test! :D
[18:23] <zer0x> are wifi cards easy to brick?
[18:24] <guntbert> zer0x: with two bricks - yes ;-)
[18:24] <zer0x> guntbert: doh :D
[18:24] <guntbert> zer0x: scnr - but I have no idea at all
[18:25] <bjsnider> i wouldn't think so
[18:26] <zer0x> I've been trying to get a rtl8192e to work, there is a driver in staging for 2.6.32, so I installed a daily snapshot, and plugged in firmware from:
[18:26] <zer0x> http://article.gmane.org/gmane.linux.kernel/927872
[18:27] <zer0x> it loaded on first boot, but still wouldn't link, since first working the firmware no longer loads without error :(
[18:28] <zer0x> I guess I could try ndiswrapper and see if I can get it working again :/
[18:30] <zer0x> I really wish I hadn't nuked the win xp recovery partition so I could test it still works! :'(
[18:31] <genii> Hm. grub-install to an USB stick:  "Your embedding area is unusually small.  core.img won't fit in it."
[18:32] <genii> Then something about blocklists
[18:33] <zer0x> still I'd rather a brick than an XP machine :DD
[18:34]  * genii decides to use --force and see what happens
[18:47] <genii> Well, --force worked, it boots etc. I wonder if the blocklists thing will cause issues later though. Using ext3 not ext4 on there right now
[19:02] <alex_mayorga> anyone using virtualbox-ose?
[19:07] <alex_mayorga> I think https://bugs.edge.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/474625 is alive on lucid
[19:12] <alex_mayorga> how do I go about asking for virtualbox 3.0.12 to be included on lucid?
[19:18] <bjsnider> submit a launchpad bug as a packaging request
[19:20] <alex_mayorga> bjsnider: is there a wiki page?
[19:20] <alex_mayorga> !package
[19:21] <alex_mayorga> !request
[19:21] <Pici> !syncrequest
[19:21] <Pici> !newpackage
[19:21] <bjsnider> it will happen automatically if the version you mention is already in upstream debian
[19:22] <Pici> bjsnider: It is.
[19:23] <Pici> But there are Ubuntu changes.
[19:25] <bjsnider> cool
[19:41] <alex_mayorga> So do I file a bug or is it already "on its way"?
[19:57] <bjsnider> nothing bad will happen if you fie a bug
[19:58] <bjsnider> filing a bug would make sure to bring it to the attention of the maintainer
[19:58] <bjsnider> but isn't virtualbox up to 3.1 now?
[20:00] <alex_mayorga> yes, but that's commercial edition or something
[20:05] <alex_mayorga> sadly I can't seen to find what's the current "OSE" version
[20:06] <alex_mayorga> anyone on 64 bit having issues to install flash-plugin directly from Firefox?
[20:09] <guntbert> !info virtualbox-ose
[20:13] <alex_mayorga> that, from the changelog, won't work on 2.6.32 kernels http://www.virtualbox.org/wiki/Changelog-3.0
[20:17] <alex_mayorga> According to Launchpad the maintainer for it is MOTU, whatever that means
[20:17] <DanaG> !motu
[20:17] <DanaG> =þ
[20:17] <alex_mayorga> DanaG: hey, thanks! I'm a better human being now :)
[20:18] <alex_mayorga> it's on their list at http://people.ubuntuwire.com/~lucas/merges.html
[20:20] <bjsnider> alex_mayorga, that means presumably they would all be notified if you submitted a packaging request
[20:21] <alex_mayorga> https://bugs.edge.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/498219
[20:22] <alex_mayorga> guess that's the bug I didn't need to file ;)
[20:22] <alex_mayorga> What would happen if I nominate it for lucid?
[20:24] <bjsnider> i guess you_really_ want this thing in there
[20:25] <alex_mayorga> let's just say I *need* virtualboxes in order to get my paycheck ;)
[20:25] <alex_mayorga> and I'm a curious guy
[20:26] <bjsnider> well, you can nominate it for lucid, but it's the responsibility of whoever is packaging it. i'm sure it will handled either way
[20:32] <alex_mayorga> Karmic was the first release based on 2.6.32?
[20:33] <bjsnider> 32 didn't exist before karmic
[20:33] <bjsnider> there are roughly 4 new kernel releases per year
[20:33] <bjsnider> they're released quarterly at linus's discretion anyhow
[20:49] <alex_mayorga> asking to know if I should nominate to karmic too
[20:49] <alex_mayorga> :)
[20:51] <bjsnider> it probably won't be backported
[20:52] <bjsnider> too risky and so forth
[20:53] <alex_mayorga> never really understood the risk part, so it's better to have entirely broken features instead of backporting?
[20:53] <alex_mayorga> but I'm a daredevil ;)
[20:53] <bjsnider> if the current version is broken,t hat's a different story
[20:53] <bjsnider> that's a great candidate for backporting
[20:54] <bjsnider> what you should do is file a request. it's up to you to convince the maintainers that you're right
[20:54] <bjsnider> so be prepared to argue and present evidence
[20:55] <bjsnider> alex_mayorga, you never understood the risk part? lots of people updated ffmpeg from the openshot ppa, which then broke everything that uses ffmpeg, such as mplayer and vlc
[20:55] <alex_mayorga> there are plenty of bugs and duplicates on launchpad, and I've never been really asked to prove my point the times when I've nominated something so far
[20:56] <bjsnider> there's a huge bug report about it
[20:57] <alex_mayorga> I don't think much stuff depends on virtualbox as of now, that'd change as virtualization seems to be the buzzword of choice, at least I heard it a lot in 2009
[20:57] <penguin42> which reminds me, anyone running kvm on Lucid at the moment and have a working bridge setup?
[20:58] <bjsnider> it builds a kernel module, which means it runs in kernel space, which means if there's something wrong witht hat module it can take down the kernel
[20:59] <alex_mayorga> bjsnider, good point
[21:07] <alex_mayorga> IIRC I was talking with somebody on wether using the nvidia PPA might cause issues when the packages go into lucid mainline, any ideas?
[21:09] <bjsnider> the packaging scripts will be all different in the lucid version
[21:09] <bjsnider> the biggest issue is removing the diversions because the new scripts will use alternatives instead
[21:10] <alex_mayorga> I guess I'll stay in vesa for now, I don't need acceleration that bad
[21:10] <bjsnider> but there is a removal script in the ppa driver package so it should be ok
[21:10] <alex_mayorga> notifications look really funky, though
[21:10] <DanaG> gaah, stupid flickery wtitwchy flash!
[21:10] <DanaG> twitchy.
[21:11] <alex_mayorga> is that funkyness "reporteable"?
[21:11] <alex_mayorga> I guess notifications should look decent on vesa too, right?
[21:12] <bjsnider> the notifications thing happens because it's in debug mode or whatever
[21:12] <bjsnider> it's a known issue
[21:12] <DanaG> *twitch*
[21:12] <DanaG> *flicker*
[21:13] <DanaG> AAAGH, my eyes!
[21:13] <alex_mayorga> DanaG: what are you trying to watch?
[21:14] <bjsnider> it's not as bad as looking at the business end of a fiber optic cable while a signal is going through it
[21:14] <DanaG> http://www.hardocp.com/
[21:14] <bjsnider> not to say i've done that...
[21:14] <DanaG> any of the videos here.
[21:14] <DanaG> ... which are Youtube embeds.
[21:14] <DanaG> note: I'm using mozilla dailies.
[21:16] <alex_mayorga> DanaG: 3.7?
[21:16] <DanaG> 3.6.
[21:16] <DanaG> I try to stay only one major-version ahead, not two.  =þ
[21:17] <alex_mayorga> I've been on Minefield for quite sometime, very stable IMHO
[21:19] <Guest39526>  I read that Ubuntu 10.04 should boot in 10 seconds, on my laptop it takes 31 seconds. This is faster than 8.04, but not 10 seconds. Should I open a ticket with my laptop model ?
[21:19] <DanaG> hmm, what's new in 3.7, versus 3.6?
[21:19] <Guest39526> I just tried Alpha 1 of Ubuntu 10.04 lynx, I notice that the shutdown menu was moved. You need to make this more obvious cause users upgrading from 8.04 will be lost.
[21:20] <DanaG> For me, it boots relatively quickly... but then logs in slowly.
[21:20] <DanaG> And even during boot, there's quite a lot of disk thrashing going on,
[21:20] <DanaG> .
[21:20] <alex_mayorga> DanaG: latest tracemonkey I think, FWIW video doesn't flickr at all on FF 3.5 here and now you have to buy me a SE X10 :)
[21:20] <DanaG> SE X10?
[21:21] <Guest39526> it boots quickly, but not 10 seconds. So should I open a bug report on launchpad  ?
[21:21] <alex_mayorga> DanaG: The SonyEricsson Android phone they have on the video :)
[21:21] <DanaG> hmm, does googlegoggles work with regular-PC webcams?
[21:22] <bjsnider> Guest39526, there's no harm in doing that
[21:22] <bjsnider> why are people afraid of filing bugs?
[21:23] <alex_mayorga> because we're always told that devs are already overwhelmed and we should be grateful with things as good as they are, etc, etc
[21:23] <Guest39526> I have filde tonnes of reports, it's that I am not sure that this counts as a bug :P
[21:23] <bjsnider> who told you that?
[21:23] <bjsnider> Gesterr on the side of assuming that it is a bug
[21:23] <Guest39526> Which package is running the startup scripts?
[21:23] <Guest39526> back in the day it was init, but I am not sure now ...
[21:23] <bjsnider> Guest39526,  err on the side of assuming that it is a bug
[21:23] <Guest39526> ok
[21:24] <Guest39526> I filed a report about a kernel panic on a ma401 wireless card back on ubuntu 7.10 ( or 8.04) , that was clearly a bug
[21:24] <alex_mayorga> I used to report every single thing, that was the idea I got in the end, maybe it's just my broken perception
[21:24] <bjsnider> it can't be fixed if they don't know about it
[21:24] <Guest39526> bjsnider That's true
[21:26] <Guest39526> which package is handling the startup ?
[21:26] <bjsnider> the kubuntu dev i talked to about kaffeine said the reason they went with the pre-1 version in karmic is that nobody told them it was broken compared to 0.8.8
[21:26] <alex_mayorga> DanaG: seems like I'll need the X10 first to try the googles :(
[21:30] <alex_mayorga> I'll clock my next boot and file a bug if it's slow, would be certainly invalid due to my dying HD :D
[21:31]  * DanaG tries readahead-fedora.
[21:33] <alex_mayorga> bug 495035 is the funky notifications
[21:34] <alex_mayorga> is that video card dependant or you also see it?
[21:35] <bjsnider> it's happening because the app is running in debug mode
[21:35] <bjsnider> it's not a bug
[21:36] <Guest39526> Filed :d
[21:36] <alex_mayorga> I guess the bug would remind them to turn off debug ;)
[21:37] <Guest39526> hey, I want to mention that the change to the shutdown menu is sure to cause confusion to users ( confused me, and will definitely confuse my mother in law ) . You should like have a place holder that says it's moved or something.
[21:38] <alex_mayorga> Guest39526: what change?
[21:38] <alex_mayorga> you mean is no longer under system menu?
[21:45] <DanaG> hmm, readahead-fedora does exactly nothing.
[21:47] <hype_>
[21:48] <alex_mayorga> !info readahead-fedora
[21:52] <Guest39526> Good job on 10.04, so far in the few minutes I have used it, it seems well done
[21:52] <Guest39526> OpenOffice 3.1 opens 10 times faster on 10.04 compared to Windows XP :d
[21:54] <alex_mayorga> Guest39526: can you elaborate on the shutdown change?
[21:55] <Guest39526> Yes, in Ubuntu 8.04 the shutdown button was ni the system menu, now it is an icon at the right on the top bar. This is confusing for using going from 8.04 lts to 10.04 lts
[21:55] <penguin42> I think that happen in 9.04 or 9.10
[21:55] <Guest39526> yes
[21:55] <Guest39526> I think it was 9.04 between alpha 2 and alpha 3
[21:56] <Guest39526> cause that's when I went back to LTS cause I could not figure out how to turn the computer off
[22:03] <Guest39526> It would be handy to be able to prioritise tickets. A 30 second boot time, instead of 10, is minor. But a forgotten message advising the user to restart a software should be medium
[22:09] <Guest24663> I am back :d
[22:10] <Guest24663> the volume/mute buttons on my ibm t43 do not work out of the box like they did with ubuntu 8.04, is there any special config I gotta do or is it a bug ?
[22:10] <Guest24663> regression*
[22:12] <penguin42> get it reported
[22:12] <Guest24663> ok
[22:13] <Guest24663> Off to find more bugs :d


[15:32] <Brainstorm> 🌒 भूकंप! Earthquake! 5.0 M tremor, registered by EMSC,KOERI,alomax, occurred 11 minutes ago (15:20:36 UTC), during a crescent moon night, on land, Rangāpāra, India (27.31, 93.04) ± 93 km, ↓4 km likely felt 140 km away (in Itanagar…) by 5000 people (www.seismicportal.eu)


[21:35] <douglasawh-work> anybody looking for a job?  Our recruiters are bugging me about finding people
[22:32] <nickmoeck> douglasawh-work: What kind of work?
[22:33] <douglasawh-work> nickmoeck: http://careers.epic.com/ but specifically I was asked about CaTS and SS TS roles.  I don't know if they are named that on the site though. I'm looking.
[22:33] <nickmoeck> woah. didn't know you worked for Epic
[22:34] <nickmoeck> I'll take a look at the available positions. Thanks douglasawh-work
[22:34] <douglasawh-work> I believe this is the SS role but the internal vs. external role names are goofy sometimes: http://careers.epic.com/position-108
[22:34] <nickmoeck> Yeah
[22:35] <douglasawh-work> this is the one that would be on my team...well, depending on how you define that, but let's not get into technicalities: http://careers.epic.com/position-161
[22:37] <nickmoeck> Where are the positions located?
[22:47] <douglasawh-work> all of these would be in Madison
[22:47] <douglasawh-work> well, either Madison or Verona
[22:47] <douglasawh-work> SS TS is in Madison right now, but that could change
[22:48] <douglasawh-work> We have offices in Dubai and in The Netherlands but as of right now my team isn't over there and I'd bet SS TS isn't either
[22:48] <nickmoeck> Okay, thanks. Might apply for a spot. even though I dont have a BS
[22:49] <douglasawh-work> do you have a BA?
[22:49] <douglasawh-work> if you don't have a bachelors, I wouldn't waste your time
[22:49] <douglasawh-work> They are quite particular about that
[22:49] <douglasawh-work> I don't have a BS either...but I do have an MS
[22:49] <nickmoeck> Well then, I guess I won't be applying
[22:50] <douglasawh-work> yeah, it sucks.  I think they probably turn away alot of great candidates because of that, but that's the way it is
[22:51] <sgtd> real experience > diploma   any day
[22:52] <douglasawh-work> sgtd: the Epic MD-fueled world doesn't see it that way
[22:52] <douglasawh-work> generally I'd agree, but for the SS TS role there is a TON of training
[22:52] <douglasawh-work> they don't require *any* experience
[22:53] <douglasawh-work> training or brainwashing, hard to say having not gone through it
[22:53] <sgtd> i suppose the medical field would have a different mindset
[22:53] <douglasawh-work> I mean, I did a little, but my role is way, way different than anything else here because it's not customer-facing
[22:54] <sgtd> i know a guy who worked at abiomed and developed code for mechanical hearts.
[22:54] <sgtd> he had a degree
[22:54] <douglasawh-work> I suppose it'd be hard to say had I gone through it...such is the nature of brainwashing
[22:54] <sgtd> but it was way old
[22:55] <douglasawh-work> I don't think that matters.  They tend to higher young, but not always. They aren't going to turn down someone phenomal for being too old
[22:55] <douglasawh-work> also, I guess the same might be true of a degree, but unless nickmoeck has one a nobel prize, I stand by what I said. :)
[22:56] <nickmoeck> Well, I do have an associates degree
[22:56] <douglasawh-work> hmm, you could try
[22:56] <nickmoeck> and 5 years of experience with Linux
[22:56] <douglasawh-work> they are going to ask you for SAT scores and things like that
[22:56] <nickmoeck> ACT score was a 31
[22:57] <nickmoeck> Never took the SAT
[22:57] <douglasawh-work> not from the midwest == that means nothing to me
[22:57] <douglasawh-work> but it probably means something to them
[22:58] <douglasawh-work> actually, why don't you send me your resume
[22:58] <douglasawh-work> they tend to take employee recommendations pretty seriously
[22:58] <douglasawh-work><EMAIL_ADDRESS>[22:59] <douglasawh-work> I know the SS TS role is out, but the SysAdmin job probably has more wiggle room
[22:59] <nickmoeck> douglasawh-work: I'll think about it.  Not sure right at this moment because I'm still mulling over starting my own company.  I appreciate it though
[23:00] <nickmoeck> Plus I'd have to move to Madison, and I'm not sure I can do that right now
[23:00] <douglasawh-work> nickmoeck: where are you now?
[23:01] <nickmoeck> Milwaukee
[23:01] <douglasawh-work> yeah, that commute's not going to be pleasant...or economical


[15:52] <throstur> if I check out a bzr repository inside a folder which is in a bzr repository, how do I say "bzr update the repository I just checked out, not the `big one`" ?
[15:53] <LeoNerd> Uhhm... "inside" ?
[15:53] <throstur> imagine /foo/ is a bzr repo and CWD is /foo/bar/baz
[15:53] <throstur> and I check out a different bzr repository there
[15:53] <LeoNerd> Do you mean repository? I suspect you don't.
[15:53] <LeoNerd> You probably mean branch
[15:54] <throstur> I mean repository
[15:54] <LeoNerd> A "repository" is not a thing that one checks out.
[15:54] <LeoNerd> Branches are checked out
[15:55] <throstur> ok, whatever, it's something I 'bzr export'ed
[15:55] <LeoNerd> Uhm.
[15:55] <throstur> but now I want to bzr commit it
[15:55] <throstur> the changes I made
[15:55] <LeoNerd> OK well if it's exported, the exported copy lacks all of the metadata
[15:55] <LeoNerd> That being the point of an export :)
[15:55] <throstur> Ah, okay, I see
[15:55] <LeoNerd> 'bzr export' creates a snapshot of the controlled files at some moment in time, minus all the control information.
[15:55] <throstur> ahh, okay
[15:55] <LeoNerd> Useful for making release tarballs and such
[15:56] <throstur> okay, then I'm thinking about this the wrong way
[15:59] <LeoNerd> If you have some edited files, you could copy them into place over a new checkout, and then you'll see the differences by 'bzr diff', and you can commit as usual
[16:01] <throstur> yeah but then I have to actually check out the whole thing with metadata
[16:02] <throstur> I'm kind of afraid of doing that, last time I repacked I think I truncated some 30 GB away
[16:11] <throstur> or maybe that was with removing obsolete packs, I'll see what the boss wants
[17:39] <throstur> ok, so what if I want to check out the repository and update a single file?
[17:40] <LeoNerd> Surely: checkout, update, commit...?
[17:41] <LeoNerd> But again: it's "branches" that one checks out, not repositories
[17:41] <throstur> but how do I make sure I'm working on the right branch or whatever?
[17:41] <LeoNerd> By the URL you check out
[17:42] <LeoNerd> URLs specify a branch
[17:42] <throstur> ok, so normally I do "bzr export foo -r revno:-1 bzr://url.goes.here/path/to/repo"
[17:43] <throstur> instead I would replace export with checkout?
[17:43] <LeoNerd> bzr checkout bzr://....
[17:43] <throstur> (and leave out -r revno)
[17:43] <LeoNerd> Again, that's not a "repo". that's a branch
[17:43] <LeoNerd> You gave it a path to a *branch*
[17:43] <throstur> right
[17:43] <LeoNerd> If you happen to have named it using the word "repo" then that's just a bit confusing. ;) It is a branch.
[17:43] <throstur> roger that
[17:46] <LeoNerd> (the distinction lies in that normally, when you create a new branch somewhere, bzr will create a repository at the same location to store it in. So *normally* it's correct to say that both the branch and the repository live there)
[17:46] <LeoNerd> But nonetheless, it is the branch that almost all operations act on
[17:47] <throstur> so how do I specify that I'm working on THIS repository and branch and not the one that starts in ../../..
[17:49] <LeoNerd> Hrm?
[17:49] <LeoNerd> Branches don't nest
[17:49] <LeoNerd> If there's a branch at that location, then that's the branch. Period.
[17:50] <LeoNerd> It's not like e.g. in SVN, wherein you can check out any subtree of the (SVN) repository
[17:50] <LeoNerd> In bzr, if you've checked out the branch, then the branch arrives as one big atomic lump, with subdirectory structure of files. But that's still one atomic *thing* as far as bzr is concerned
[17:55] <throstur> does checkout always take much longer than export?
[17:56] <LeoNerd> It has to create the entire local copy of the branch in *addition* to a local snapshot of the files, so yes. that's expected
[17:56] <throstur> but LeoNerd, I've already checked out a branch. If I type bzr update, I start updating something. Now I type bzr checkout bzr://... and it starts checking something else out. Now if I type bzr update, what am I updating?
[17:57] <LeoNerd> Uhm..
[17:57] <throstur> is it not possible to push a single file to be merged remotely?
[17:57] <LeoNerd> bzr checkout   creates a branch new set of things locally on your disk
[17:57] <LeoNerd> You'd usually do that into a brand new empty directory
[17:57] <LeoNerd> *brand new
[17:57] <throstur> like I'm literally on the 4th GB fetching revisions and I'm trying to add a 4kb file
[17:58] <LeoNerd> If you already had it checked out, why are you checking it out a second time? :)
[17:58] <throstur> it was only exported
 but LeoNerd, I've already checked out a branch. If I type bzr update, I start updating something. Now I type bzr checkout bzr://...  <==  I see "checked out" at the beginning
[17:58] <LeoNerd> An export is not a checkout
[17:58] <throstur> yes, that's not the same branch
[17:58] <throstur> or repo
[17:59] <LeoNerd> Again: an export is a snapshot of the current content, minus all of the control information and any history and any metadata sufficient to create and commit new revisions
[17:59] <LeoNerd> If you want to create new revisions (which from "and I'm trying to add a 4kb file" it sounds like you do), then you will need a checkout. Not an export
[18:00] <throstur> I'm on server A that has repository A checked out in folder A. I'm actually in folder A/foo/bar/baz and if I bzr update I update *something* (in this case, definitely repo A). NOW I check out repository B (whatever branch I don't know there is only one branch afaiac) and I want to work with B, but if I type bzr update, *something* will get updated, but I have no idea what
[18:00] <LeoNerd> OK.. so if  bzr update  can do something,. then you do have a local checkout
[18:00] <LeoNerd> Just typ   bzr info   to see what you have
[18:01] <throstur> ah okay
[18:01] <throstur> so if I'm writing this as a part of a library (don't ask why) I can just parse bzr info for "branch root: ." to ensure I'm in the *right* bracnh
[18:02] <throstur> or rather, that i'm working in the bzr repository that I want to be working in, and not the one that I shouldn't be touching
[18:02] <throstur> or I could check the bound to branch thing... that might be smarter
[18:02] <LeoNerd> You could. (though also be aware of bzrlib, if you're writing this in python, as using the lib is nicer than trying to parse command output intended for humans)
[18:02] <throstur> gosh though... a full checkout... I'm only up to 6 GB :(
[18:03] <LeoNerd> You might be able to get away with a lightweight checkout. I forget quite what those involve and what they lack
[18:03] <throstur> does bzr lib work for python 2.6.6?
[18:03] <LeoNerd> I'd hope so
[18:04] <throstur> oh yeah
[18:04] <throstur> I remember that, no history
[18:04] <throstur> it's like 20Gb smaller
[18:04] <throstur> thanks for reminding me :D
[18:06] <throstur> wow that took so much less time, 1.6 GB and almost done
[18:06] <LeoNerd> History isn't cheap ;)
[18:29] <throstur> looks like when I commit from python it doesn't work but when I commit from bash it works
[18:30] <throstur> from python it tries to commit to "the other" repo
[18:30] <throstur> actually I'm wrong, it just things the file isn't versioned
[18:30] <throstur> but it is
[18:31] <throstur> oh lol
[18:31] <throstur> it's because I chdir one dir up
[18:31] <throstur> to be in the right repo
[18:32] <throstur> how do I bzr commit to ./this_thing instead of cd this_thing bzr commit ../path/to/file
[18:53] <throstur> thx4the help I g2g got a workaround going, will see if it breaks something overnight


[15:03] <lool> njpatel: Hey just a heads up on #433859
[15:10] <lool> njpatel: err sorry I meant #433386
[15:10] <lool> the d-s one is not very imporatnt
[15:12] <njpatel> lool: on call -- that's going to need a plugin (adding to sidebar)
[15:12] <lool> njpatel: Ok sounds like we need to make sure that's high enough on the list of prios then
[15:12] <njpatel> lool: I can make the plugin part of the launcher source code, though, not need for separate package
[15:15] <lool> njpatel: Ok it seems to be quite important for karmic so if it needs some special development we should look into that soon
[15:15] <lool> beta being in two days
[15:15] <lool> I mean beta freeze
[15:16] <njpatel> right, I've milestoned it in the upstream launcher for beta freeze
[15:16] <njpatel> lool: do we know where the button should go? i.e. below files and folders but above categories, or under favorites?
[15:18] <lool> njpatel: Well Ivanka suggested the possibility of having it in the main categories
[15:18] <lool> njpatel: forwarded the email to you
[15:18] <lool> njpatel: I think we should clarify ASAP, either saying that it's too late to develop this or asking for details on the implementaiton
[15:19] <lool> njpatel: I added it to the mobile agenda for the integration call, but dont think we have ivanka there
[15:19] <lool> plars, njpatel: Guys, I just did a bunch of changes to the UNR seed over the weekend to have to have it closed to the desktop one; I think you should pay particular attention to the new set of apps next time you look at UNR
[15:20] <njpatel> lool: I can't get it in between the categories that we make for menus. It'll have to be either at the top, between favorites and the first menu category, or right at the bottom
[15:20] <plars> lool: will do, thanks for the heads up
[15:20] <plars> GrueMaster: ^ also
[15:20] <njpatel> lool: right, I don't think we do...and this is really late wrt schedule, but let's see what we can do
[15:21] <lool> njpatel: I think that's what Ivanka wanted (presumably bottom)
[15:21] <lool> njpatel: since add/remove used to be at the bottom of the Applications menu in GNOME
[15:21] <njpatel> lool: that could be done pretty easily, could you please get confirmation for that (as I'm working on OEM stuff atm), and add it to the bug report?
[15:21] <lool> njpatel: Ok
[15:22] <njpatel> lool: thanks!
[17:52] <ian_brasil> is a meeting planned for tomorrow?
[17:55] <lool> ian_brasil: Yes
[17:56] <ian_brasil> lool, ok


[00:15] <qwebirc97871> wish I could get mine to even boot
[00:15] <qwebirc97871> ive tried cd, usb, external hdd all fail
[01:22] <rhpot1991> ComradeHaz`: verified the path to your optical drive is correct?
[01:24] <ComradeHaz`> um, nope....?
[01:30] <qwebirc97871> yea
[01:30] <qwebirc97871> Its correct
[01:30] <qwebirc97871> I get myth splash screen, then a cursor for a while, screen goes darker with cursor and it hangs there
[01:33] <qwebirc97871> vesamenu.32: not a valid com32 image
[01:34] <qwebirc97871> ive tried everything
[01:38] <rhpot1991> qwebirc97871: did the check on the cd when booting it?
[01:42] <qwebirc97871> did what check?
[01:42] <qwebirc97871> checking for burn errors?
[01:42] <qwebirc97871> Ive tried cd,usb,external hdd, any option you can think of with same result
[01:42] <rhpot1991> qwebirc97871: are you having problems booting the install cd, or something else?
[01:45] <qwebirc97871> yea
[01:45] <qwebirc97871> install cd
[01:45] <rhpot1991> when you boot it up there should be an option to check the disc
[01:45] <rhpot1991> I would do that
[01:45] <rhpot1991> could also check the md5sum for the iso as well
[01:45] <qwebirc97871> I dont get that option, I get a MythBuntu screen with what looks like a man and a usb stick, then a black screen with cursor
[01:46] <qwebirc97871> I dont get presented with any options
[01:46] <rhpot1991> and if you just let it go what happens?
[01:46] <qwebirc97871> nothing
[01:46] <rhpot1991> https://help.ubuntu.com/community/HowToMD5SUM
[01:46] <qwebirc97871> screen goes slightly darker
[01:46] <Zinn> [help.ubuntu.com] HowToMD5SUM - Community Ubuntu Documentation
[01:47] <rhpot1991> how long have you waited for something to happen?
[01:47] <qwebirc97871> 5 hours
[01:47] <rhpot1991> ya thats not good
[01:47] <rhpot1991> check the md5sum on your iso
[01:47] <qwebirc97871> the ISO is fine, as it boots in a VM
[01:47] <rhpot1991> I'd venture it might be an issue with your video card
[01:48] <rhpot1991> you could ask for help in #ubuntu and tell them the installer boots to a black screen
[01:49] <qwebirc97871> is there anything u can recomend I try
[02:38] <qwebirc97871> It was my video card
[02:38] <qwebirc97871> going to an older version at least semi boots
[02:39] <qwebirc97871> Does anyone know the switch I need to add to end of boot line to get ATI to work
[03:25] <mrand> qwebirc97871: you could try xforcevesa.  no guarantees, but I've seen it work sometimes
[06:04] <dpgraves> I'm having problems connecting to Mysql database after upgrade to 0.24 from 0.23.1 please help
[06:44] <Chaorain> hey all, I'm looking to have Mythvideo play specific titles with subtitles. Some would need track 1 or track 2.  I'm useing 0.23
[08:10] <qwebirc97871> anyone here
[08:10] <qwebirc97871> Can you install myth from a cd without booting into GUI as GUI is crashing on startup
[08:11] <qwebirc97871> I can boot into cli
[14:22] <mrand> qwebirc97871: did you try xforcevesa?
[14:22] <mrand> The short answer is no.


[03:32] <lamont> sigh.  that took _WAY_ too long
[04:06] <daniels> fabbione: which patch?
[04:07] <daniels> oh, I see
[04:07] <daniels> fabbione: got it
[04:47] <jbailey> doko: Around?
[06:09] <fabbione> morning
[06:09] <fabbione> daniels: ping?
[06:10] <daniels> pong
[06:10] <fabbione> daniels: did you see my patch on people?
[06:11] <daniels> yeah, already merged it
[06:11] <fabbione> thanks
[06:11] <fabbione> i am uploading -15 right now
[06:11] <daniels> no worries
[06:11] <daniels> -15 of what?
[06:11] <fabbione> as soon as i get the accepted you are free to go for -16 :)
[06:11] <fabbione> xorg
[06:11] <daniels> oh, for sparc
[06:11] <fabbione> yes
[06:11] <daniels> phew
[06:12] <fabbione> if you upload -16 before, the -15 bins will be rejected
[06:12] <daniels> sure
[06:13] <fabbione> finally i can start buildd again :)
[06:29] <fabbione> http://www.theregister.co.uk/2005/05/18/vibrating_knickers/
[06:29] <fabbione> AHAHHAHAHA
[06:56] <fabbione> daniels: ok you can go anytime
[06:56] <fabbione> -15 has been accepted
[06:56] <daniels> cool
[06:58] <fabbione> thanks dude
[06:59] <lamont-away> fabbione: are you uploading binaries that are non-virgin???  you bad man you.
[07:01] <fabbione> lamont-away: yeah it's cheating on a package :)
[07:01] <fabbione> aren't you supposed to be sleeping?
[07:01] <lamont-away> yeah - came out to check on the buildd, and change the laundry
[07:02] <lamont-away> anyway, g'night again
[07:02] <fabbione> btw kernel: i need updated chroots on concordia and davis otherwise i can't test build
[07:02] <lamont-away> yeah - saw that in -kernel.
[07:02] <fabbione> lamont-away: too lazy to change the version
[07:02] <fabbione> specially because -16 with the fix will hit archive soon
[07:03] <fabbione> lamont-away: before you go... xorg gcc -> buildd?
[07:03] <fabbione> is there anything else i need to take care of?
[07:03] <fabbione> lamont-away: i doubt... the fix was sparc specific
[07:03] <daniels> lamont-away: uhm no, it was a sunffb-specific fix :P
[07:03] <fabbione> sunffb driver compilation options
[07:03] <daniels> i didn't know what -mv8 was before I started on -15
[07:03] <daniels> and I still don't
[07:04] <daniels> unless it specifies the particular sparc revision or some shit
[07:04] <lamont-away> prior to unleashing the buildd: 1) cxxapps.txt -> @no_auto_build, 2) fresh versions of gcc-4.0, gcc-defaults, dpkg, xorg (and their build-deps, of course).
[07:04] <fabbione> i think it's some gcc optimization flag
[07:04] <lamont-away> ah, ok
[07:04] <fabbione> lamont-away: yeps.. all of that it's already in place
[07:04] <lamont-away> then you're _go_ for sparc buildd
[07:04] <fabbione> coolness
[07:04] <lamont-away> once those are in the archive, that is.
[07:04] <fabbione> they are
[07:04] <fabbione> i did build all of them manually
[07:05] <lamont-away> yeah
[07:05] <fabbione> yup
[07:05] <fabbione> good night lamont :)
[07:05] <fabbione> yeah i wonder how many i will get here
[07:06] <lamont-away> some of those are hppa specific (console-tools, ubuntu-meta)  But a bunch of them are /usr/include/X11 or gcc-4.0 or such
[07:06] <fabbione> + i still have some old craft to cleanup
[07:06] <lamont-away> 232 packages built, 151 of them uploaded... damn straws
[07:08] <fabbione> i guess i am going to hit some build-deps madness...
[07:08] <lamont-away> oh yeah, big time.
[07:08] <fabbione> ehhehe
[07:08] <lamont-away> not to mention lots of NEW packages, depending on how you have your overrides set up...
[07:09] <fabbione> i didn't setup overrides
[07:09] <lamont-away> there are still a few packages in universe that need to move to main to fix the archive.
[07:09] <fabbione> oh
[07:09] <fabbione> well i don't mix universe/main anymore
[07:09] <fabbione> after ports has been up
[07:09] <lamont-away> is in scrollback from doko just before he left.
[07:09] <lamont-away> that's good
[07:09] <fabbione> so the ogre model is complete again
[07:09] <fabbione> now the local pkg cache is down to 2 hours
[07:10] <fabbione> so possiblities to hit a mix are very very very low
[07:11] <lamont-away> anyrate, time to sleep again.  g'night
[07:11] <fabbione> night lamont
[07:14] <fabbione> daniels: btw.. elmo mentioned that xtrans had some .c files in /usr/include/X11
[07:14] <fabbione> dunno if you fixed that already
[07:14] <daniels> it's not fixable
[07:14] <daniels> that's how xtrans works
[07:14] <fabbione> eh?
[07:15] <daniels> you #define a bunch of crap and then #include the .c files
[07:15] <daniels> it's utterly, utterly disgusting
[07:15] <fabbione> JEEEEE
[07:15] <daniels> now you see why I have such a deep-seated hate for xtrans
[07:15] <fabbione> can't we move the .c files somewhere like /usr/share/ ?
[07:15] <fabbione> just for the goddam sake of it?
[07:16] <daniels> we've already had that argument upstream, the consensus was that we'd put it in /usr/include and try to kill xtrans
[07:16] <fabbione> BRRRRRRR
[07:17] <fabbione> we need to get an #u-x chan or something
[07:17] <daniels> this is the sort of shit I have to deal with upstream as well as downstream :P
[07:18] <fabbione> daniels: you are d00m3d
[07:19] <daniels> indeed
[07:20] <fabbione> omg! doko! another gcc-3* full set upload?
[07:21] <fabbione> i wonder if i will ever get to the point to actually build something else than toolchain
[07:34] <doko> morning all
[07:34] <fabbione> hey doko
[07:43] <fabbione> infinity: ping?
[12:16] <Kamion> doko: all those libraries are still in NEW - I'm leaving them to elmo
[12:19] <doko> hmm, getting all these renamed libraries into the archives is really suboptimal :-(
[12:26] <doko> Kamion: the debconf build needs kdebindings fixing for amd64 from Riddell
[12:27] <cartman> koffice will need http://janeway.no-ip.org/~cartman/filters_gcc4.patch btw
[12:27] <cartman> just in case
[12:29] <Riddell> might take a few hours
[12:29] <Riddell> cartman: which version of koffice is that against?
[12:29] <cartman> head
[12:29] <cartman> but filters rarely changed
[12:30] <cartman> should apply cleanly
[12:30] <Riddell> cartman: have you sent it back to the koffice developers?
[12:30] <cartman> Riddell: trying now, psn resisting ;)
[12:31] <Riddell> cartman: is that compiled on 64 bbit or 32 bit?
[12:31] <cartman> Riddell: only errors on amd64+gcc4
[12:31] <Riddell> cartman: ah, then you'll be adding errors to x86 :)
[12:32] <cartman> hmm no
[12:32] <cartman> similar fix went into kmail last week
[12:32] <cartman> :/
[12:32] <cartman> should be safe
[12:32] <cartman> you cast it to long before casting to something else to preserve precision
[12:32] <Kamion> doko: debconf hasn't built for ages anyway :(
[12:33] <Riddell> cartman: ok, maybe you're right
[12:33] <cartman> Riddell: I will wait for dfaure to be sure
[12:33] <Riddell> he's the man
[12:33] <cartman> yep
[12:36] <Riddell> out->fScratch = ((int)(long)in & 1);   is there really no better way?  just looks ugly
[12:37] <cartman> well I stole the solution from kmail where they were casting int* to int
[01:08] <Kamion> erm. what's the type of 'in'?
[01:09] <fabbione> ehy Kamion
[01:09] <fabbione> Kamion: do you still have katie suppah p0w3r? :)
[01:10] <cartman> Kamion: const char* I think
[01:10] <Kamion> cartman: EWWWW. so you're basically working around crappy typing elsewhere.
[01:10] <Kamion> fabbione: yes ...?
[01:10] <cartman> Kamion: its msword/mswrite filters, what do you expect? honest :)
[01:11] <fabbione> Kamion: just for curiosity... what is the status of knetworkconf 0.6.1-3ubuntu4 (hoary-updates)?
[01:11] <Kamion> fabbione: same as it was when the last two people asked about it :P
[01:11] <Kamion> fabbione: source is in the archive, but I don't think hoary-updates is building ...
[01:11] <fabbione> Kamion: i am asking becuase i could see the source and the sparc buildd got it in needs-build, but it was not taking it
[01:12] <fabbione> ah ok, but it is safe for me to upload it?
[01:12] <fabbione> sparc did built it fine
[01:12] <Kamion> I'm assuming it's turned off in w-b or something, I'm not actually sure
[01:12] <fabbione> ok, don't worry
[01:12] <Kamion> I don't know if it's safe or not - it probably is, but that's an elmo question
[01:12] <fabbione> ok, i will just keep it stand-by somewhere
[01:12] <fabbione> thanks a lot
[01:13] <Kamion> it might get rejected by the C++ transition check in jennifer
[01:13] <fabbione> uh right...
[01:13] <Kamion> which isn't distribution-guarded
[01:13] <fabbione> no it's banned as c++apps in buildd.conf
[01:13] <fabbione> i forgot that kde is all c++
[01:14] <fabbione> or almost :)
[01:14] <fabbione> so yeah.. it can be built, but it's not since @no_auto_build is not distro aware
[01:14] <fabbione> and the filter is applied
[01:23] <Kamion> ah, buildd.conf, ok
[01:24] <fabbione> yeah it was the simplest solution to filter apps
[01:24] <fabbione> i just forgot to look there before asking :)
[01:38] <Riddell> kdebindings doesn't want to compile
[01:39] <Riddell> it gets stuck on sipqtpart0.cpp and sits there chewing up CPU cycles forever
[01:39] <doko> Riddell: try to lower the optimization for that file
[01:42] <Riddell> doko: that did it
[01:42] <Kamion> elmo: I NEWed dbus_0.33-0ubuntu3, openh323_1.15.3-2ubuntu2, libtunepimp_0.3.0-2ubuntu7 for c2 changes
[01:42] <Riddell> not sure how to lower the optimisation other by hand though
[01:45] <doko> Riddell: please save the preprocessed file, and put it in a bug report, need the architecture and command line options as well
[02:56] <\sh> morning
[03:48] <lamont> jbailey:  g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../grove -g --pipe -O3 -ffunction-sections -D_REENTRANT -MT GroveApp.lo -MD -MP -MF .deps/GroveApp.Tpo -c GroveApp.cxx  -fPIC -DPIC -o .libs/GroveApp.o
[03:48] <lamont> /usr/include/OpenSP/RangeMap.cxx: In member function 'unsigned int OpenSP::RangeMap<From, To>::inverseMap(To, From&, OpenSP::ISet<OpenSP::WideChar>&, OpenSP::WideChar&) const':
[03:48] <lamont> /usr/include/OpenSP/RangeMap.cxx:50: error: 'wideCharMax' was not declared in this scope
[03:48] <lamont> wanna fix openjade?
[03:53] <doko> lamont: hi
[03:53] <doko> I'm looking at it
[03:54] <lamont> thansk
[03:54] <doko> lamont: kdebase needs some love, the deps are in main now
[03:56] <doko> lamont: openjade did build on all archs ...
[03:57] <lamont> that's from hppa - haven't double checked to make sure it dies on i386
[03:57] <lamont> ruby1.8. otoh is another dpkg victim
[04:00] <lamont> ruby1.8 => #11040
[04:09] <doko> it's ok, if you see the breakage, but there's silent breakage as well. hmm, maybe it's better to just revert this change until Debian switches to the new dpkg as well
[04:10] <lamont> interesting idea
[04:13] <fabbione> hey lamont
[04:15] <fabbione> lamont: it would be interesting to implement @no_auto_build per distro
[04:15] <lamont> fabbione: heh
[04:15] <fabbione> today digging in the w-b database i noticed a knetworkconf (hoary-updates) not taken for build
[04:15] <fabbione> because it's banned in breezy
[04:15] <lamont> it would also be good to to make SIGHUP re-read it
[04:16] <fabbione> hm?
[04:16] <fabbione> yeah
[04:18] <fabbione> it's too slow!
[04:18] <fabbione> doko: you must do something about it
[04:19] <lamont> doko: might be that doing a breezy-test world with dpkg changed might be the right answer.
[04:19] <doko> ifeq arch=sparc and bbuilder=fabbione, then fail. exit 0
[04:19] <doko> that's fast!
[04:19] <doko> fabbione: did I tell you that I need another 3.4?
[04:20] <fabbione> doko: i am still building gcc-3.3
[04:20] <fabbione> so i don't really care
[04:20] <fabbione> doko: did you fix that problem with libvtest thing?
[04:20] <fabbione> doko: so if you upload the new gcc-3.4 now it's ok
[04:20] <doko> well, 3.3 does have interesting libc dependencies now ...
[04:21] <fabbione> i am still building 3.3
[04:21] <fabbione> but i care more about 3.4
[04:21] <doko> fabbione: I don't know, I built it, and I don't see the failure
[04:21] <fabbione> since we build the kernel with 3.4
[04:21] <fabbione> doko: bah you suck :P
[04:21] <fabbione> i told you.. the target is not called
[04:21] <fabbione> come on dude...
[04:21] <fabbione> you can manage :)
[04:23] <fabbione> doko: i will see if it happens again with the next build
[04:23] <fabbione> if so i will put our buildd chroot somewhere so you can look at it
[04:24] <doko> fix ruby1.8 while you're waiting ;-)
[04:24] <fabbione> doko: are you going to do cleaning in my house in the meanwhile?
[04:24] <doko> lamont: could you remove the Dep-Wait for xerces25 and xerces26?
[04:24] <lamont> doko: sorry sure
[04:25] <lamont> done
[04:25] <doko> fabbione: hmm ...
[04:26] <fabbione> doko: trust me.. you will be more happy fixing ruby1.8 too :)
[04:26] <fabbione> + i hate c++
[04:26] <fabbione> with all myself
[04:27] <\sh> jesus
[04:27] <\sh> kdelibs4c2 is in
[04:27] <lamont> \sh: that was doko et. al., not jesus
[04:27] <fabbione> doko has short hair...
[04:27] <\sh> when doko uploaded it, he's jesus ;)
[04:27] <doko> \sh, call me as you like it ;-)
[04:28] <\sh> fabbione: and? in africa, jesus has a dark skin colour
[04:28] <doko> naa, Kamion did give it some love ...
[04:28] <fabbione> doko drinks beer... jesus doesn't
[04:28] <fabbione> or didn't...
[04:28] <fabbione> depends how you want to see it :)
[04:28] <lamont> fabbione: wine, beer, what's the diff?
[04:29] <fabbione> jesus was more for wine...
[04:29] <\sh> fabbione: we can't be sure
[04:29] <\sh> jesus had something with maria magdalena
[04:29] <fabbione> lamont: beer is like so... german.. wine is more italian :)
[04:29] <lamont> well, if the books are to be believed, he was of jewish descent...
[04:29] <doko> Riddell, amu: kdebase fails ...
[04:29] <doko> kate.la.o(.text+0xe): In function `main':
[04:29] <doko> collect2: ld returned 1 exit status
[04:29] <doko> make[4] : *** [kate]  Error 1
[04:30] <\sh> the life, the universe and the rest
[04:30] <fabbione> anyway... time to go and do some cleaning
[04:30] <\sh> let me finished libchasen
[04:30] <lamont>  /build/buildd/kdebase-3.4.0/obj-i386-linux-gnu/kate/app/kate.la.cpp:2: undefined reference to `kdemain'
[04:30] <\sh> -ed
[04:30] <lamont> doko: you forgot that line
[04:31] <doko> yes, xchat did grab it
[04:31] <lamont> yeah
[04:31] <doko> fabbione: one idea ...
[04:31] <fabbione> doko: ?
[04:31] <lamont> hppa's uploader is only 86 packages behind...  sigh.
[04:31] <doko> are there dangling symlinks in /usr/lib/gcc/3.4.4/sparc*/64/
[04:32] <doko> or in  /usr/lib/gcc/3.4.4/sparc*/
[04:32] <doko> to libgcc*
[04:32] <fabbione> doko: i dunno...
[04:32] <fabbione> and i can't really check
[04:32] <doko> fabbione, look and you will see ...
[04:32] <fabbione> do you want me to look if the build fails?
[04:32] <doko> it's a small miracle ;)
[04:33] <fabbione> one moment
[04:33] <doko> hmm, no, that can't be the reason, we don't use the stage1 compiler at this point
[04:34] <doko> just found out, why gcc-3.4 -m32 is broken on amd64, jbailey could be interested ...
[04:35] <doko> lamont: could you make sure, that all the buildd's get the current state of the archive, so that I could start uploading cxxapps from main?
[04:35] <fabbione> are all libs builded?
[04:35] <fabbione> doko: you should still be sure that the apps build-dep on a proper version of the libs
[04:36] <doko> fabbione: no, in this case we have to touch all 700 cxxapps packages.
[04:36] <fabbione> doko: dude.. that will make another breezy debootstrap impossible
[04:36] <fabbione> doko: you need to change the apps to versioned build-dep
[04:37] <doko> fabbione: why will it be impossible?
[04:38] <doko> apps which get synced from Debian don't have changed build-deps either
[04:38] <fabbione> because you can build packages on top of old libs if you are not extremely carefull
[04:38] <doko> I did always think, that the hppa and sparc buildd admins are careful, but I can be wrong ;-)
[04:38] <lamont> doko: you can upload cxxapps, but they won't get built until we change @no_auto_build... :-)
[04:39] <fabbione> doko: it's not just hppa and sparc..
[04:39] <fabbione> i think not changing the build-deps is just wrong
[04:39] <doko> lamont: elmo told me that I could upload anyway
[04:39] <lamont> fabbione: they build-dep on foo-dev, which is unchanged...
[04:39] <doko> fabbione: what do you make in case of the synced apps?
[04:39] <lamont> ISTR doko saying they might just work...
[04:40] <fabbione> usr/lib/gcc/sparc-linux/3.4.4 # ls -lR
[04:40] <fabbione> no dangling symlinks
[04:40] <lamont> fabbione: it can be handled as an archive event... painful, but it works...
[04:40] <fabbione> hmmm
[04:40] <fabbione> ok
[04:41] <doko> lamont: archive event?
[04:42] <lamont> doko: what we're doing.
[04:42] <fabbione> probably i am just too much of a purist
[04:42] <lamont> draw a line, and make sure that nothing on the right side needs anything that wasn't fixed on the left side.
[04:42] <doko> fabbione: we'll get these build-deps, when Debian is doing the transition
[04:42] <fabbione> given that sparc was out of hoary thanks to gcc-4.0 unversioned build-deps....
[04:42] <lamont> note that archive events are, by definition, a royal pain in the tail for any buildd admin
[04:43] <fabbione> lamont: oh yeah.. i agree
[04:44] <fabbione> i need to go.. doko: last offer to come and clean my house in exchange of kernel upload with mISDN
[04:44] <fabbione> (our kernel is really free like in beer ;))
[04:44] <fabbione> b180?
[04:44] <fabbione> is the slowest one?
[04:44] <doko> slow hppa ...
[04:44] <lamont> 180MHz 32-bit UP hppa
[04:44] <fabbione> amen
[04:44] <lamont> well, there's only 2 of them,.
[04:45] <doko> heh, and it fails ...
[04:45] <fabbione> lamont: why don't you add it to @no_auto_build ?
[04:45] <lamont> I just did
[04:45] <fabbione> a bit too late i guess :)
[04:45] <fabbione> lamont: you can still share the ccache between the 2 buildds
[04:45] <lamont> it had never built it (since it _was_ in n-a-b), so it didn't show up when I added all the really long build-time stuff to n-a-b
[04:45] <fabbione> it will be less painful when packages hit the slow one
[04:46] <lamont> fabbione: yeah, but that's so much like work
[04:46] <lamont> and disk I/O isn't exactly the fastest here...
[04:46] <fabbione> uh why?
[04:46] <fabbione> NFS my friend
[04:46] <lamont> well, for starters, the machines are 2-switches away from each other
[04:46] <fabbione> that's what i use here to share ccache all over
[04:46] <lamont> Not a File System
[04:46] <fabbione> lamont: OCFS2 with the next kernel upload :)
[04:47] <lamont> OCFS2?
[04:47] <fabbione> Oracle Cluster Filesystem2
[04:47] <fabbione> my wife is so going to kill me if i don't go and clean
[04:47] <fabbione> http://people.ubuntu.com/~fabbione/Screenshot.png
[04:48] <doko> lamont: does openoffice.org build?
[04:48] <lamont> on hppa? no
[04:48] <fabbione> me must go now
[04:48] <fabbione> cya later
[04:48] <doko> lamont: i386 and powerpc
[04:49] <lamont> it's in the @no_auto_build list
[04:49] <lamont> so it's not going to even try anywhere
[04:49] <\sh> hmmm...
[04:50] <lamont> ommmmm
[04:50] <\sh> i was just informed, that I'm now have a new portable 160gb usb2 hd
[04:50] <\sh> it's ready to pick up
[04:50] <\sh> strange thing is, i've never ordered one
[04:51] <\sh> and I don't have to pay it
[04:51] <\sh> weired
[04:51] <doko> lamont: are you able to change the @no_auto_build lists?
[04:51] <lamont> are we ready for me to?
[04:52] <lamont> and note that when I do, it'll be 'empty the list' on each buildd as it's done... I'm not going to do it one package at a time
[04:52] <doko> lamont: all cxxapps in main but KDE. but we can enable KDE as well, it will just fail, because kdebase isn't installable.
[04:52] <doko> yes, let's wait for kdebase, then we can do it
[04:55] <lamont> openjade is an hppa-specific issue.  sihg
[04:56] <\sh> hmm
[04:56] <\sh> think i will setup an ubuntu mirror
[05:01] <doko> lamont: could you report it upstream?
[05:02] <lamont> doko: will do, although I want to investigate it a bit first...
[05:03] <doko> jbailey: just noticed that gcc-3.4 -m32 didn't work
[05:04] <\sh> doko: u reviewed some of those debdiff outputs?
[05:04] <jbailey> doko: For which arch?
[05:05] <jbailey> (I'm lagging a bit at the moment, I updated to the new X and it won't start.  I'm just poking it a bit)
[05:05] <doko> \sh, ok, will do
[05:06] <doko> jbailey: -m32 ...
[05:06] <jbailey> doko: I think it worked fine for me the other day on amd64.  It may have been sparc, though.
[05:07] <\sh> doko: i saw some u reviewed :) u r working too much i think ;)
[05:07] <doko> hmm, the 32bit libgcc symlinks are dangling links
[05:09] <jbailey> doko: I'll take a look in a moment then.
[05:17] <Riddell> doko: I think kdebase just needs visibility turned off, checking now
[05:27] <doko> Riddell, yes, I did see this as well ... hope, that not every KDE packages has this check ...
[05:27] <jbailey> Ah, lovely.  got X again.
[05:27] <jbailey> *bounce*
[05:29] <jbailey> mps
[05:29] <Riddell> doko: compiles now, should I upload?
[05:31] <jbailey> doko: Now that I'm actually paying attention.. =)
[05:31] <jbailey> doko: I have 3 questions:
[05:31] <jbailey> 1) What was that about -m32?
[05:32] <jbailey> 2) I've confirmed that glibc builds with -g2 on ppc at least, so I'll set that for the next upload.
[05:32] <jbailey> 3) What would be good timing for me to do the i386/amd64 biarch stuff so that I don't interfere with you.
[05:33] <\sh> Riddell: that means we will have a running kdebase at least today? ,-)
[05:33] <Riddell> \sh: it means we should have a compiling kdebase
[05:33] <Riddell> running is a different matter
[05:44] <doko> Riddell: please do
[05:45] <doko> jbailey: 1) dangling symlinks
[05:45] <doko> 2) now ;) get the 0ubuntu2, that I did upload some minutes ago
[05:45] <doko> no, this was 3) ;)
[05:46] <jbailey> Does #3 also solve #1? =)
[05:46] <doko> yes
[05:47] <jbailey> Excellent! =)
[05:47] <Riddell> doko: that file that I said didn't compile did finish after two hours.  I innocently gave up hope after 1 hour
[05:47] <jbailey> doko: Do you have brainspace for me to ask you about biarch setups and ppc64?
[05:54] <Riddell> kdebase_3.4.0-0ubuntu21_source.changes ACCEPTED
[05:56] <jbailey> fabbione: If you're bored at some point, I had asked the main Splack guy about his throughts on requiring v9 or newer for a Sparc distro.  He says that he gots alot of requests for support from classparcs.
[05:57] <jbailey> fabbione: I Don't know if that's a good reason to support them, or a good reason to run screaming. =)
[05:57] <fabbione> jbailey: the latter :)
[05:57] <fabbione> jbailey: btw xorg did build fine with your fix
[06:02] <jbailey> fabbione: Yay!
[06:02] <jbailey> fabbione: Any other crazy blockers?
[06:03] <fabbione> jbailey: not right now.. util-linux did build as well
[06:11] <doko> Riddell: anyway, having the preprocessed source would be very useful
[06:12] <doko> jbailey, yes, why not
[06:13] <Riddell> doko: it's a 9MB file
[06:13] <jbailey> doko: Right now our bi-arch configs, i386, sparc, and s390 all succesfully build a biarch setup on a 32 bit kernel.
[06:13] <Riddell> KDE bindings is a bit crazy
[06:14] <doko> Riddell: doesn't matter
[06:14] <\sh> Riddell: do u want to disable the python qt/kde bindings in kdebindings?
[06:15] <doko> yes, do they? I did assume that the buildd's for s390 and sparc are 64bit
[06:15] <jbailey> doko: From looking at the logs, it looks like ppc is trying to actually run a built ppc64 binary.  Is that something in our packaging, or is that something upstream that needs to be poked?
[06:15] <Riddell> \sh: arn't they already apart from qt-dcop?
[06:15] <fabbione> doko: nope.. sparc userland is almost all at 32bit
[06:15] <fabbione> and it doesn't matter what kernel are you running to build
[06:16] <\sh> Riddell: i don't know...they're only disabled (in the last source tree i saw) I wanted to use the normal upstream packages...
[06:17] <Riddell> \sh: "do u want to disable" "they're only disabled" which are they?
[06:17] <doko> that should be coded in gcc/config.ml (guessing if the compiler works)
[06:18] <\sh> Riddell: I saw u complaining about python-qt sip things...I just wondered if they're enabled again
[06:18] <doko> config-ml.in in the toplevel directory
[06:19] <Riddell> \sh: right.  I suspect they're compiled and then no package is made of them
[06:19] <Riddell> which is a bit silly
[06:20] <\sh> Riddell: so remove them from configure.in and makefile.am ;)
[06:20] <\sh> I will come to python-sip4-qt and kde stuff later this day
[06:21] <\sh> patches are already there for pkde
[06:21] <Riddell> great
[06:22] <\sh> i don't like this "copy upstream packages into kdebindings"
[06:30] <jbailey> Heya Bastian.
[06:30] <waldi> hi
[06:31] <fabbione> hey waldi
[06:32] <doko> waldi: moin
[06:37] <jbailey> doko: When should we do the binutils update?
[06:41] <doko> 2.16.1 will be released next week. I didn't had a chance yet for testing on ia64 with glibc 2.3.5
[06:42] <jbailey> doko: Do you mean with the new bintuils or in general?
[06:42] <jbailey> ia64 with glibc 2.3.5 in general is working fine.
[06:42] <jbailey> I can give you access to my box with the breezy chroot if you'd like,.
[06:44] <doko> with 2.16, I see one regression in the binuitls testsuite (on unstable)
[06:44] <jbailey> Ah, drow message about releasing 2.16.1 I had missed it.  Cool.
[06:44] <doko> jbailey: no need, just build the package from experimental in this chroot
[06:44] <jbailey> doing
[07:00] <jbailey> Feh, getting false testsuite failures because it's failing to spawn and such.
[07:02] <jbailey> Lemme boot the box, there's some d-i build processes lying around probably tying up resources.
[07:03] <fabbione> doko: can i push you a clean breezy chroot somewhere, so you can test a gcc build?
[07:04] <Kamion> hm, not a good time for a debootstrap upload - aptitude needs to be rebuilt first
[07:04] <fabbione> uh?
[07:05] <Kamion> depends on libsigc++*c102
[07:05] <fabbione> Kamion: i have a diff for the buildd variant
[07:05] <fabbione> but i am waiting for the last c++ stuff to complete the transition
[07:05] <fabbione> or do you test that one too?
[07:05] <Kamion> mail it to me and I'll do it in one upload when everything else is done?
[07:06] <fabbione> Kamion: sure.. buildd isn't that important and can be done "anytime"
[07:07] <Kamion> but if you turn out to be in a hurry for it, then feel free
[07:07] <doko> fabbione: ok
[07:07] <fabbione> no no.. it's no hurry
[07:07] <Kamion> the main scripts just need unusual handling
[07:08] <doko> Kamion: mvo told me that he did test apt and aptitude on all four archs, so maybe I'll just build it
[07:15] <doko> Riddell: "Bash 3.0-14ubuntu1 hangs on amd64 after any command taking up 99% CPU cycles", I cannot reproduce this behaviour, the testsuite looks ok  as well
[07:16] <Riddell> doko: hmm, it's definatly very reproducable on amu's machine
[07:16] <Riddell> doko: old chroot and fresh one
[07:17] <doko> lamont: ^^^ maybe do not update the buildd's while we are working this out
[07:38] <fabbione> oh great
[07:38] <fabbione> doko: gcc-3.3 fails too
[07:38] <fabbione> mv debian/tmp/usr/lib64/lib*c++*.{a,so} debian/tmp/usr/lib/gcc-lib/sparc-linux-gnu/3.
[07:38] <fabbione> 3.6/64/.
[07:39] <fabbione> mv: when moving multiple files, last argument must be a directory
[07:39] <fabbione> Try `mv --help' for more information.
[07:39] <fabbione> make[1] : *** [stamps/08-binary-stamp-libstdcxx-dev]  Error 1
[07:39] <fabbione> btw.. it did start building gcc-3.4
[07:39] <fabbione> should i stop it?
[07:42] <fabbione> this is weird
[07:42] <fabbione> gcc-3.3 did create the debs and failed?
[07:44] <fabbione> oh yeah.. it was building the debs when it failed
[07:44] <doko> hmm, why is the target directory not present ... strange
[07:45] <fabbione> doko: i have almost done with the chroot :)
[07:57] <jbailey> Mmm.  It's not harmful to have packages in debian/control that are never built, is it?
[07:59] <fabbione> jbailey: given that you don't create the deb...
[07:59] <lamont> jbailey: not unless they ever were built
[07:59] <lamont> I think...
[07:59] <lamont> anyway, really running off now
[08:00] <fabbione> later lamont
[08:00] <jbailey> 'bye lamont
[08:00] <jbailey> 'k thanks.
[08:01] <doko> jbailey: no, that's ok
[08:02] <jbailey> I'm trying to reduce what I have to do to enable ppc64 in my build. =)
[08:04] <doko> debian/rules.defs: look for biarch
[08:05] <jbailey> Sorry, still on glibc.
[08:05] <doko> ;)
[08:12] <fabbione> guys when do you think i can start working on a ppc64 kernel?
[08:12] <fabbione> to do that i need the toolchain in place
[08:12] <fabbione> and breezy-ppc64 chroot is borked afaik
[08:12] <daniels> night folks
[08:13] <fabbione> configure: WARNING: I have to compile Test.class from scratch
[08:13] <fabbione> checking if java works... configure: error: The Java VM java failed (see config.log,
[08:13] <fabbione> check the CLASSPATH?)
[08:13] <fabbione> db4.2
[08:13] <fabbione> night kid
[08:14] <fabbione> ../dist/configure: line 21554: 28092 Bus error               $JAVA $JAVAFLAGS $TEST
[08:14] <fabbione> interesting :)
[08:14] <jbailey> g'n Daniel.
[08:15] <jbailey> fabbione: The ppc64 toolchain is blocked on the fact that it wants a ppc64 kernel to build.
[08:15] <jbailey> I'm trying to convince it otherwise.
[08:24] <jbailey> doko: Was it an ld failure?
[08:25] <jbailey> I see on unepxcted, but schwab posting something to the binutils list that I Can try.
[08:25] <jbailey> http://sourceware.org/ml/binutils/2005-05/msg00601.html
[08:28] <doko> jbailey: yes, that's the regression I did see
[09:33] <doko> ok, submitted #11050 for the dpkg behaviour
[09:44] <doko> lamont: where can I find the icu build? it's marked as uploaded, but not installed
[09:52] <jbailey> Wow.  The binutils patch system *doesn't fail* if a patch fails to apply.
[09:53] <doko> could be dpkg-breakage? ;-) sorry, couldn't resist
[09:54] <jbailey> If only/  I confirmed it with debian/rules patch =(
[09:54] <jbailey> So doing the ia64 test.
[09:54] <jbailey> +re
[09:55] <jbailey> I'm leaving in a moment, too, so I'll let you know how it goes later.
[09:55] <jbailey> I'm also building a ppc64 glibc.
[09:55] <elmo> jbailey: err, it so does?
[09:57] <jbailey> It didn't for me.  A lovely bit in debian/patched/123_ldwhatever_I_called it
[09:58] <jbailey> that nicely logged that the patch hadn't applied.
[09:58] <jbailey> And it merrily carried on.
[09:58] <jbailey> Anyhow, Angie's poking me to go, back in a few hours.
[10:00] <elmo> well, new dpatch might not, but new dpatch grew crackful maintainers :(
[10:05] <doko> elmo: packages from cxxapps cannot be built, even if I upload them signed with my key?
[10:10] <elmo> doko: I didn't restrict building of apps, that's lamont
[10:10] <elmo> I only restricted source uploads
[10:11] <elmo> well, you CERTAINLY can't upload binaries, signed by your key
[10:11] <doko> ;)
[10:12] <doko> where's icu currently stuck, is it buildd or new?
[10:12] <elmo>        icu | 2.1-2ubuntu1 | breezy/universe | source, amd64, ia64, powerpc
[10:13] <elmo> REJECT
[10:13] <elmo> Rejected: icu-doc_2.1-2ubuntu1_all.deb: old version (2.8-4) in breezy >= new version (2.1-2ubuntu1) targeted at breezy.
[10:13] <elmo> Rejected: icu-doc_2.1-2ubuntu1_all.deb: old version (2.8-4) in hoary >= new version (2.1-2ubuntu1) targeted at breezy.
[10:15] <doko> hmm, where can I see this?
[10:15] <elmo> you can't
[10:16] <elmo> the queue/REPORT stuff is not visible because it contains security uploads too
[10:16] <elmo> kamion/mdz can see it.  and lamont gets the REJECT mails
[10:17] <doko> hmm, well, something we should talk about
[10:18] <doko> anything else rejected from the cxx stuff?
[10:18] <elmo> I've no idea, I'm not trawling through all the possible rejects :P
[10:19] <elmo> as I said, the buildd admin gets the emails ...