=== Keybuk glances at licio's quit message [12:14] I knew there was something I was supposed to do today [12:15] replace shutdown by upstart? [12:15] right === Gman [i=gman@nat/sun/x-f6e296a9875a9d88] has joined #ubuntu-devel === shackan_ [n=shackan@host22-147.pool876.interbusiness.it] has joined #ubuntu-devel === jdong|coreduo wonders what would happen if he installed upstart on his dapper box === KaiL [n=KaiL@p548F7A93.dip.t-dialin.net] has joined #ubuntu-devel [12:23] jdong|coreduo: you'll need a libc update [12:23] it only builds on edgy [12:23] aww :( [12:23] Keybuk: you're ruining all my fun :) [12:24] excuse my complete lack of knowledge about upstart, but will all existing sysv init scripts need to be rewritten? === rleigh_ [n=rleigh@client-82-27-252-249.glfd.adsl.virgin.net] has joined #ubuntu-devel [12:25] jdong, no [12:25] jdong, before you ask any further questions, I suggest you read Keybuk's rather extensive blog post [12:25] this weeks UWN covers it [12:26] "need", no === jdong|coreduo must've skimmed the post too fast :-/ [12:28] would upstart result in any kind of bootup/shutdown speed improvement? === msw [n=msw@rdu-nat.rpath.com] has joined #ubuntu-devel === Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-devel [12:40] jdong|coreduo: eventually, yes [12:40] though that isn't its goal [12:40] k, gotcha [12:41] Keybuk, would it be fair to say that the archiecture makes such improvements easier to implement? === givre [n=flo@APuteaux-152-1-59-114.w82-120.abo.wanadoo.fr] has joined #ubuntu-devel === KaiL [n=KaiL@p548F7834.dip.t-dialin.net] has joined #ubuntu-devel [12:42] Burgwork: yes [12:43] Keybuk, i have a weird problem with my ltsp here ... apparently the NIC always starts in half duplex mode ... do you know how evil it would be to run mii-tool -F 100base-Tx-FD in my initscript of the client ? would NICs that dont have 100base-Tx-FD support break on that or just gracefully fall back to something sane [12:43] right. I am going to writing something about upstart as part of the Knot2 release thingy [12:44] i.e. how forcefully is the force switch ? :) [12:45] ogra: they'd break [12:45] gah [12:45] in particular, you'd break any NIC plugged into a hub [12:45] right [12:45] oh [12:45] as you'd force it into 100base-Tx-FD overriding whatever it had auto-sensed [12:45] RIGHT [12:45] (hubs are almost never FD :p) [12:45] i'm plugged into a hub [12:45] <- heavy headdesking [12:45] are you sure that it really should be at FD ? [12:46] if you're plugged into a hub, it would not surprise me that HD is the best you can get [12:46] if you set it to FD, do you get lots of errors? [12:47] well, if i force it to FD i can import my 10Gig of music from the usb disk on the thin client to rhythmbox and my session doesnt die ... [12:47] in HD that doesnt work [12:48] why doesn't it work? [12:48] the network gets saturated and the ssh session dies (locks up) [12:49] hmm [12:49] usually after 10-20 mins [12:50] i switched to FD more than 1h ago and the music still plays fine ... desktop is responsive etc [12:50] what's the error count in ifconfig? [12:50] RX: 1597 [12:50] the rest 0 [12:51] hmm [12:51] rising [12:51] 1601 now [12:52] then something isn't doing FD properly ;) [12:52] errors should always be 0 on a wired interface [12:52] well, close to it anyway [12:56] right === ompaul [n=ompaul@ubuntu/member/ompaul] has joined #ubuntu-devel [01:07] yay, finally ... 6M to go on i386 .... === ogra dances ... [01:26] hey ogra === eggauah [n=daniel@20845135.cps.virtua.com.br] has joined #ubuntu-devel [01:27] hey zul === profoX` [n=profox@d51A52303.access.telenet.be] has joined #ubuntu-devel [01:28] hey guys -- i wanted to apologise for not coming to the TB meeting yesterday -- i made a point on the agenda, but it slipped my mind (just wanted to say that) === WaterSevenUb [n=WaterSev@azevedo.astro.up.pt] has joined #ubuntu-devel === z\ [n=pjphem@unaffiliated/madsheep] has left #ubuntu-devel ["Leaving"] === jcole [n=jcole@palrel2.hp.com] has left #ubuntu-devel [] === j_ack [n=rudi@p508DB96E.dip0.t-ipconnect.de] has joined #ubuntu-devel === freeflying|away [n=freeflyi@ubuntu/member/freeflying] has joined #ubuntu-devel === Kr4t05 [n=andrew@dsl-66-59-121-30.dsl0.crls.pa.net] has joined #ubuntu-devel [02:08] Hey, guys. [02:08] hey k4 [02:08] I have a question about Edgy+1. Are there any plans to merge InitNG into Ubuntu? [02:08] Or, is that in line for Edgy? [02:08] no. [02:08] no [02:08] Mkay. [02:09] Just thought I would ask. :) [02:09] Kr4t05, got a link for you, just a sec [02:09] Allright. [02:09] Kr4t05, http://www.netsplit.com/blog/work/canonical/upstart.html [02:09] read that [02:09] it was answer all your initng questions [02:11] Ah, even from the intro, it sounds awesome. :) === doko [n=doko@dslb-088-073-066-130.pools.arcor-ip.net] has joined #ubuntu-devel [02:15] Ok, thanks. :) [02:15] So, is this upstart going to be seen any time soon? [02:15] Oh, oops. === Kr4t05 reads further. [02:16] Oh, neat. :) [02:16] Thanks. === Kr4t05 [n=andrew@dsl-66-59-121-30.dsl0.crls.pa.net] has left #ubuntu-devel ["Leaving"] [02:16] when you are done reading, then ask questions [02:16] or not [02:16] I think he's done :) [02:16] which is good [02:17] ogra: forcing full duplex assumes that the other end is directly connected to a wire-speed non-blocking device; a modern switch or direct PC<->PC connection [02:18] think I should add the upstart link to the topic? [02:23] Burgwork: as long as if that is done, the answer isn't RTFM [02:24] yep === freeflying [n=freeflyi@61.190.64.118] has joined #ubuntu-devel [02:26] sladen, have you installed the LAMP option? [02:26] https://launchpad.net/products/ubuntu-website/+bug/58161 [02:26] Malone bug 58161 in ubuntu-website "http://www.ubuntu.com/server incorrectly only mentions PHP for LAMP" [Untriaged,Unconfirmed] [02:27] Burgwork: The bug is invalid. We don't install mod_python or mod_perl, only mod_php, so the website is correct. === Keybuk [n=scott@syndicate.netsplit.com] has joined #ubuntu-devel [02:27] infinity, that is what I thought [02:27] And, 3rd party definitions don't much matter in this case. :) [02:28] yep. Rejected with extreme prejudice [02:28] LAMP used to stand for Linux/Apache/MySQL/PHP originally. Now it may be Linux, Apache and Many Possible database and scripting options. [02:28] But that's not what we install. :) [02:29] Burgwork: I haven't installed the LAMP option. Haven't got a clue how to---it never seemed to actually get mentioned. I presume it's a meta-package [02:29] sladen: It's (currently) a book option on the server CD. Will be a task in edgy. [02:29] s/book/boot/ [02:30] infinity: I thought LAMP meant perl ;) === Burgwork smacks lifeless ;) [02:30] lifeless: it used to [02:31] many years ago [02:31] lifeless: I'd be cool with that, mod_perl is great to use. But it's not what the average user who'd pick a "LAMP install" blindly is likely looking for either. :) === freeflying_ [n=freeflyi@61.190.64.118] has joined #ubuntu-devel [02:33] Anyhow, wikipedia claims the term was coined in a c't article in 1998, and that article claims it was PHP, so I win. :P [02:33] infinity, and wikipedia also claims elephant numbers are increasing... [02:34] Clearly visible by visiting a goth club. [02:34] or any fast food joint [02:36] it was probably mSQL instead of MySQL aswell... [02:36] sladen: Not according to the article in question, anyway. [02:36] trappist: seems like I missed your last message on bug 58002 before posting my comments; my second one might be a more general solution provided it causes no other problems...? [02:36] Malone bug 58002 in vim "vim should populate skel/.viminfo so ownership is not affected by initial sudo" [Wishlist,Confirmed] http://launchpad.net/bugs/58002 [02:39] JanC: simple question. what command would you run to edit /etc/apt/sources.list ? [02:40] 'sudo -e /etc/apt/sources.list' ? [02:41] why do we even ship vim and emacs? [02:41] aside from the screaming if we didn't? [02:41] because people use them all the time? [02:42] emacs you could potentially lose [02:42] since it's massive [02:42] "people" use irc all the time and we dropped that [02:42] JanC: okay, most people (including me) would do sudo emacs ... and we have to cope with that (even if export EDITOR=... and sudo -e would be better) [02:42] vim is massive too ;) [02:42] and people who use it are all insane [02:42] in fact, I would say that more people used xchat than vim or emacs [02:43] infinity, what is your gut feeling? should I suggest we not ship them? [02:43] I know less than a handful of people who use emacs [02:43] Burgwork: vim: so that people can edit files. Emacs is not installed by default, but it is a programmers editor and normally the first thing I install [02:43] sladen: but my second message was about the 'always_set_home' flag in sudoers [02:43] I know MANY people that use vim [02:43] people that use emacs are *ALL* "hardcore" [02:43] sladen, umm, nano? [02:43] not all people that use vim are [02:43] vim is awful to use [02:44] if you *just* need to edit a text file to get up and running again, you can use nano [02:44] Burgwork: We'r enot going to stop shipping some vi variant in -minimal. [02:44] Burgwork: Ubuntu is "awful" to use if you've used DOS all your life. People are comfortable using what they are familiar with... [02:44] Burgwork: It belongs there. [02:44] ok [02:44] then at least lets ship the smallest bloody vim we can [02:44] We've talked about vim-tiny, but it's still undecided. [02:44] I'd be happy with nvi, personally, but whatever. === scie [n=hermes@cust-39-174.dsl.versateladsl.be] has joined #ubuntu-devel [02:45] yeah [02:45] tbh as long as it came with 'viu' [02:45] I use 'nano' to add universe so I can install 'joe' :) [02:45] 'vi' [02:45] most people wouldn't care that vim had to be installed [02:45] Burgwork: that's a proposal/spec worth making. If I'm not getting my 'emacs' by default I want to ensure that the 'vi' nutters are penalised aswell [02:45] aside from infinity's "it belongs there" arguement. Why do we need it? I am not trolling. I am asking a serious question from a non0technical users standpoint [02:45] 'vim' not 'vi' [02:45] vi is a core unix util which has a reasonable expectation of being their [02:46] vim is not [02:46] HrdwrBoB: this is a valid point, can you write a spec? [02:46] are things going to break if it is not included? it is easily apt-getable? [02:46] I can see if somebody writes vim/vi into a script and thus it would silently fail, but I just don't see someone doing that [02:47] they'd use ed to do that [02:47] Burgwork: Nothing breaks, except the brains of thousand of old UNIX hacks. A small vi is not a size hit, and people who don't know what vi is will never rnu it, so there's no harm in having it there to satisfy old farts like me. [02:47] sladen: I can do that, can you point me in the right direction [02:48] infinity, ok. Installed size is 1.5mb [02:49] Burgwork: For vim? Bigger than that, you're missing vim-runtime and other scariness. [02:49] yes, I just saw vim-common at 21mb === bddebian [n=bdefrees@71.224.172.103] has joined #ubuntu-devel [02:49] HrdwrBoB: https://features.launchpad.net/distros/ubuntu/+addspec is a good place, it'll guide you through the specificaiton registration and give you the templated wiki page to fill in [02:49] at 21mb, that is insane [02:49] sladen: cheers [02:49] that is BIGGER. THAN. EMACS [02:50] HrdwrBoB, point me at the spec wiki page and I will add some commentary [02:50] anyway, got to go home [02:50] Burgwork: vim-tiny is small, though, and nvi is even smaller. [02:51] infinity: what does vim-tiny offer someone that they wouldn't install vim anyway [02:51] Howdy folks [02:51] HrdwrBoB: A useable 'vi'? [02:51] HrdwrBoB: it offers vi in significantly less space? [02:51] tseng: um [02:52] what I mean is if you install vim-tiny instead of nvi [02:52] would people actually care [02:52] that isnt what you said [02:52] or are all 'vim people' going to isntall vim anyway [02:52] I am [02:52] in which case, vim-tiny is not useful [02:52] but if i have no vi at all, I will be pissed [02:52] HrdwrBoB: vim-tiny sucks a bit less than nvi. Fewer irritating misfeatures (like resetting the editor mode when you hit the beginning of a line) and such. [02:52] this applies to 1000s of people [02:53] absolutely [02:53] which is why you would have nvi === rouzic [n=rouzic@32.Red-83-56-54.dynamicIP.rima-tde.net] has joined #ubuntu-devel [02:53] you can't not have vi [02:53] nano-tiny!! :-) [02:55] Keybuk: ping [02:55] dpkg -L vim vim-common vim-runtime | xargs -I'{}' find '{}' -type f -maxdepth 0 | xargs du -sch 23MB ... [02:55] bddebian: you mean we have to replace nano with nano-tiny to save some 100 KiB of disk space ? ;-) [02:56] sladen: Yes, this isn't news. [02:57] are dependency waits automatic or require intervention? [02:57] jdong: automatic [02:57] i.e. amarok backport needs libtunepimp3 backport [02:57] will amarok try again once libtunepimp3 is ready? [02:57] jdong: Assuming the build-deps are correctly versioned. [02:57] infinity: yeah, I doubled-checked it as I couldn't believe ^Installed-Size: [02:58] jdong: Yeah, looks like it did it right. Should work fine. [02:58] k, cool === robertj [n=robertj@66-188-77-153.dhcp.athn.ga.charter.com] has joined #ubuntu-devel === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-devel [02:59] jdong: I'll push all the libtunepimp stuff through dapper's NEW queue once powerpc has caught up. [02:59] JanC: Yep ;-P [02:59] cool, thanks for everything, infinity :) [03:00] Or you could alway just remove emacs from the archive and save even more space === bddebian ducks [03:00] hahaha [03:00] haha [03:00] bddebian: lol, you duck quite a bit :) [03:00] bddebian: we don't installed emacs by default "because it's too big" [03:00] bddebian: we could remove all editors except 'ed' ;-) [03:00] I know, I was being sarcastic sorry :-) [03:00] world bandwidth conservation day... :) [03:01] JanC: Why use ed, when you can just use dd? [03:01] JanC: I like it :-) [03:01] JanC: Seek for characters in a reference file and construct the target. [03:01] JanC: Alternately, there's always shipping tiny magnets and magnifying glasses alongside the shipit CDs. [03:01] And perhaps a screwdriver. [03:02] hm, at least that magnifying glass & screwdriver sound useful :-) [03:06] crimsun: 'sup? [03:06] Keybuk: hi, do you mind if I merge alsa-driver? I'd like to close bug 46996 and its dupes. [03:06] Malone bug 46996 in alsa-driver "Hotplugged sound devices get sound card index of 0 instead of PCI card" [Wishlist,In progress] http://launchpad.net/bugs/46996 === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-devel [03:07] crimsun: will you need a UVF? [03:08] Keybuk: for 1.0.11-3ubuntu1 -> 1.0.11-5ubuntu1 ? No, unless I misunderstand the exception process utterly. [03:08] hey Hobbsee [03:08] no, you don't then [03:08] hey all [03:08] go for it === cr3 [n=marc@pdpc/supporter/bronze/cr3] has joined #ubuntu-devel [03:08] Keybuk: thanks. [03:11] woo! syncs got done again :) [03:11] Hobbsee: yeah :) [03:11] jdong: backports too? [03:11] yeah [03:11] keybuk's been busy today :) [03:12] indeed :) [03:16] https://features.launchpad.net/distros/ubuntu/+spec/large-text-editor-removal [03:17] it's not complete, but it's a start [03:18] remove nano :P [03:18] Nooooo [03:19] as long as we keep vi.. === jdong looks through edgy-changes for things worth backporting :) [03:19] hangon let me get this straight [03:19] vim/emacs is in a default install? or just on the CD [03:19] I'm too stupid for a "real" editor, I need my nano ;-P [03:19] Hobbsee: i totally agree [03:19] HrdwrBoB: vi at least is in the default install [03:20] jdong: You can do the fix on firestarter for me [03:20] Hobbsee: not vi, vim [03:20] It's a security issue [03:20] bddebian: we really shouldn't be using dapper-backports for security issues :-/ [03:20] HrdwrBoB: true that. [03:20] but it sounds like it needs source changes anyway :) [03:21] bddebian: is it the version in edgy? [03:22] jdong: It is now [03:22] jdong: Should be same as dapper + some changes [03:22] !info firestarter edgy === jdong mumbles [03:22] firestarter (1.0.3-1.2ubuntu2) edgy; urgency=low [03:23] that one? [03:24] Yessir === Burgundavia [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-devel === jdong downloads sources [03:24] hey Burgundavia [03:24] Heya Burgundavia [03:24] I'd like to take this moment to complain a bit about why archive.ubuntu.com is so slow? [03:25] 5-20kb/s [03:25] hey Hobbsee, bddebian [03:25] jdong: the DC in london is having issue, afaik [03:25] ah, fascinating [03:25] HrdwrBoB: this yours: https://wiki.ubuntu.com/TextEditorCDRemoval [03:26] Burgundavia: yes [03:26] cool [03:26] ping me when you are done with it [03:26] I'm done with it for the moment [03:26] I have some actual work to do :) [03:26] right, will dig away [03:27] cool, cheers [03:29] bddebian: merry christmas, bug 58164 [03:29] Malone bug 58164 in dapper-backports "firestarter backport" [High,Confirmed] http://launchpad.net/bugs/58164 [03:29] jdong: Thx! [03:29] Wow, all those syncs brought down the merge list a little :-) === jdong marvels at how fast his core duo cranked out a firestarter deb :) === jdong grumbles at how slow XFS is at installing it since 2.6.17's write barriers [03:33] write barriers? [03:33] lifeless: yeah, flushing that annoying write cache to make sure nothing gets lost in abrupt shutdown [03:34] without it, even journaling FS'es can corrupt during bad shutdowns [03:34] XFS's aggressiveness makes it exceptionally vulnerable to this [03:34] ah [03:34] so, safety at the cost of performance :-/ [03:34] when does it flush now ? [03:34] not every write ? [03:34] it works ok for me :) [03:35] right now the hd is responsible for flushing its own cache [03:35] (though I have XFS setup with an external journal and my disks have a large write cache) [03:35] HrdwrBoB: extern journal turns off barriers on XFS [03:35] yeah [03:35] in 2.6.17, XFS team turned on write barriers by default [03:36] so the filesystem keeps track of what's currently in the hd's cache [03:36] ah, I see [03:36] from what I've heard, ext3 has been doing this for some time now [03:36] the goal was to address the xfs_repair-after-shutdown issues people have been complaining about [03:36] yeah, writing over whats in cache in the hd would be failure prone [03:37] writing over? [03:37] until now, the XFS team has been just blaming it on cheap PC hardware :P [03:37] lifeless: it's not writing over as much as it is losing... [03:37] not really, the cache is gone after no power === cr3_ [n=marc@Sherbrooke-HSE-ppp3611353.sympatico.ca] has joined #ubuntu-devel [03:37] jdong: which realistically is fair, since XFS was designed to run on real hardware [03:37] with persistant write buffers [03:37] HrdwrBoB: right, but I own cheap hardware but still want to run XFS :) [03:38] HrdwrBoB: it was also designed to run with a real operating system... ;-) [03:38] torrenting really blows on ext3/reiserfs [03:38] they also suck a lot for large filesystems [03:38] however, xfs delete times are awful. [03:38] I agree [03:39] so you can't win [03:39] a large journaling area + logbufs=8 helps a bit [03:39] but that's just a band-aid [03:39] I'm talking about a few hundred thousand files [03:39] I know, I feel the pain of cleaning out pbuilders every few hours [03:39] for what I gain from XFS, it's a trade-off I am willing to make [03:40] ext3 just simply does not work out for me [03:40] I use rsync+hardlinks to do backups [03:40] so I end up with LOTS of files [03:40] and after trying to repair two different reiserfs corruptions, I've learned that fsck.reiserfs might as well be symlinked to mkfs.reiserfs :) [03:41] lifeless: btw, bzr is just rocking recently.... handling my kernels superbly [03:41] thats fantastic nes [03:41] *news* [03:41] jdong: though I screwed XFS by trying to use it on an amd64 kernel [03:41] when it was made/used by a 32bit kernel [03:41] HrdwrBoB: ouch... yeah, that's a tough lesson to learn [03:42] HrdwrBoB: did you dodge the 2.6.17.6/7 directory corruption thing? [03:42] that sucked for XFS's reputation :-/ [03:42] yeah I managed to get around that, fortunately [03:43] :) [03:44] the other good thing about xfs, it provides me with xfs_fsr to entertain me when I'm bored [03:44] I can fit in with Windows users and say that I defrag my filesystem :P [03:45] heh === poningru [n=poningru@ip70-171-62-28.ga.at.cox.net] has joined #ubuntu-devel [03:47] HrdwrBoB: xfs doesn't work with 64 bit kernels, or is it a filesystem portabiity issue? === Gman is now known as GmanAFK [03:48] jdub: a xfs volume made in a 32-bit arch can't be used on a 64-bit arch [03:49] if you mount it, you'll corrupt it [03:49] that is so much bong [03:49] no kidding :-/ [03:49] is that a linux port issue, or an xfs-in-general issue? i can't imagine why xfs would have portability problems... crazy! [03:50] jdub: portability [03:50] yeah [03:50] linux port issue afaik [03:50] jdong: that's interesting, considering that I'm fairly sure I run that [03:50] (or did I run a 64-bit kernel all the time on that host perhaps?) [03:50] maswan: I've mounted one of my 32-bit xfs partitions under amd64 before, and it didn't seem to mess up [03:51] but so many people have reported problems and the XFS team has said not to do it... so.... yeah [03:51] "doctor, it hurts if i hold my hand above my head!" [03:51] "well, don't do that" [03:51] *bzzt* [03:52] jdub: i saw my doctor about something like that a week back [03:52] he sent me home with a bottle of vicodin [03:52] heh [03:53] the problem is, it's not obvious [03:53] and the documentation on it is sparse [03:53] no mention of it in the faq either [03:53] I didn't realise that was the problem until I found an xfs mailing list post saying "my data is toast!" [03:54] there's mention in XFS's wikipedia article [03:54] # [03:54] # On the Linux XFS implementations, compatibility issues between 64-bit and 32-bit environments exist. [03:55] that's a far cry from "you will frag all your data if you change to 64 bit" [03:55] I know, very vague and not the red bold warning it deserves === nictuku [n=yves@ubuntu/member/nictuku] has joined #ubuntu-devel [03:55] that's why wikipedia is a wiki tho :) [03:56] ah, reading some ml stuff, there are mentions of things like patches to fix log replay when changing bitness and so [03:56] maswan: yeah very recently iirc [03:57] so it might only be a "frag all data if you have change to 64 bit while having a dirty log"? === Burgundavia [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-devel [04:00] could be [04:00] any firestarter "experts" in here? [04:00] I like starting fires, but that's probably not what you're asking about. [04:01] heh [04:01] nvm, pseudo-answered my own question [04:01] when you open a port, it opens both tcp/udp [04:01] I was wondering why it didn't ask me which [04:01] good old iptables -L [04:02] but either way, the backport looks good, bddebian === jdong grumbles that he had to install a firewall on his laptop :P [04:02] jdong: Well I might duck a lot but you grumble alot ;-P [04:02] :) === jdong grumbles that azureus 2.5.0.0 isn't merged yet :P === jdong specifically grumbles at bddebian :) [04:04] jdong: I'm going to try to look tomorrow but it may be over my head and I don't want doko kicking my ass :-) [04:04] lol [04:04] but think of it this way: it can't be any less usable than the current azureus package that he made === jdong ducks, too :) [04:05] Well that's what everyone always says until I upload something ;-) === fsmw [n=Fernando@102-140-223-201.adsl.terra.cl] has joined #ubuntu-devel [04:06] lol [04:09] well, I'm calling it a night. take care, everyone :) [04:09] jdong: feel free to fix it :) [04:09] Gnight jdong, thanks again === Yagisan [n=Yagisan@doomsday/developer/Yagisan] has joined #ubuntu-devel [04:15] infinity: ping? :) could you please accept dbus from binary NEW for all archs? === freeflying_ [n=freeflyi@61.190.64.118] has joined #ubuntu-devel === _human_blip_ [n=mike@220.157.65.29] has joined #ubuntu-devel [04:29] mako: ping (planet debian) === freeflying_ [n=freeflyi@61.190.64.118] has joined #ubuntu-devel === TomB_ [n=tomb@AC8D3FAA.ipt.aol.com] has joined #ubuntu-devel === TomB| [n=ownthebo@AC8D3FAA.ipt.aol.com] has joined #ubuntu-devel === Hobbsee_ [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-devel [04:38] jdub: yes [04:39] mako: howdy - you should upgrade planet debian to planet 2.0 when you have a minute. it is much nicer, and handles some weird feeds better. [04:41] jdub: does planet 2 fix the phenomena by which broken feeds get almost every post reposted sequentially? [04:42] robertj: that was fixed much earlier than 2.0 [04:42] I just seem to recall seeing it alot on p.g.o. [04:42] robertj: not for aaaaaaages === wasabi [n=wasabi@ubuntu/member/wasabi] has joined #ubuntu-devel === wasabi [n=wasabi@ubuntu/member/wasabi] has joined #ubuntu-devel === CarlFK [n=carl@c-67-163-39-124.hsd1.il.comcast.net] has joined #ubuntu-devel === mayday_jay [n=maydayja@maydayjay.net] has joined #ubuntu-devel === freeflying|away [n=freeflyi@ubuntu/member/freeflying] has joined #ubuntu-devel === mayday_jay [n=maydayja@maydayjay.net] has joined #ubuntu-devel === Amaranth [n=travis@ubuntu/member/amaranth] has joined #ubuntu-devel === holycow [n=a@mail.wjsgroup.com] has joined #ubuntu-devel === nixternal [n=nixterna@ubuntu/member/nixternal] has joined #ubuntu-devel === LaserJock [n=mantha@ubuntu/member/laserjock] has joined #ubuntu-devel === slomo [n=slomo@ubuntu/member/slomo] has joined #ubuntu-devel === wubrgamer [n=chatzill@c-68-33-190-196.hsd1.va.comcast.net] has joined #ubuntu-devel === tainted- [n=tainted@adsl-69-230-201-74.dsl.irvnca.pacbell.net] has joined #ubuntu-devel [06:20] which user owns the apache daemon by default ? on ubuntu ? === tainted- [n=tainted@adsl-69-230-201-74.dsl.irvnca.pacbell.net] has left #ubuntu-devel ["Leaving"] === wubrgamer [n=chatzill@c-68-33-190-196.hsd1.va.comcast.net] has left #ubuntu-devel [] === dcstimm_ [n=dcstimm@ip68-8-230-16.sd.sd.cox.net] has joined #ubuntu-devel [06:31] hey guys, what is the difference between the 6.06.1 livecd and the 6.06 livecd for ppc? does it fix any of the imac issues? === nags [n=nags@125.16.129.16] has joined #ubuntu-devel [06:33] dcstimm_: imac issues? === basanta [n=basanta@202.79.37.177] has joined #ubuntu-devel [06:33] yeah the isight imac g5 boots to black video [06:34] the imac pre ALS goes crazy when you boot it up and the fans go on high and the console is broken [06:34] imac g4s do not boot and have graphic issues with usplash [06:35] so I was wondering the change log for 6.06.1 to see if anything was fixed [06:39] anyone know? [06:39] well, do you have a fully upgraded Dapper [06:40] i.e. are you using the dapper-security and dapper-updates repositories? [06:41] im talking about the livecd [06:42] hmm, well you could check for bug reports on Launchpad and see if they say anything [06:42] I just don't know of that specific problem [06:43] LaserJock, i am just looking for a changelog [06:43] there must be a change log between 6.06 and 6.06.1 [06:43] isnt there?1 [06:43] hmm, not sure === zenrox [n=zenrox@pool-71-120-239-162.spknwa.dsl-w.verizon.net] has joined #ubuntu-devel [06:45] standard documentation shouldnt be this hard to find [06:45] dcstimm_: the release announcement is at https://lists.ubuntu.com/archives/ubuntu-announce/2006-August/000088.html [06:47] I don't see anything about imacs but again, a bug report might be more useful [06:49] I see a few bug reports about g5 imacs having boot problems === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-devel === FliesLikeABrick [n=Ryan@about/rpi/rawdor] has joined #ubuntu-devel === mattn [n=mattn@p5483E039.dip.t-dialin.net] has joined #ubuntu-devel === raphink [n=raphink@ubuntu/member/raphink] has joined #ubuntu-devel === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-devel === apokryphos [n=apokryph@host-84-9-108-232.bulldogdsl.com] has joined #ubuntu-devel === apokryphos- [n=apokryph@host-84-9-109-192.bulldogdsl.com] has joined #ubuntu-devel [08:14]