[01:09] hey [01:10] is there something weird with xorg in hardy [01:10] sais it cannot be installed due to deps [01:13] yes, there is. [01:13] clusty: the fact that you're asking probably means you shouldnt be urnning it. [01:13] running just a virtual machine [01:13] so no harm done [01:13] wanted to see the new cutting edge features like bulletproof X [01:15] why not run gutsy, then? [01:15] features wont be in for a while yet anyway [01:15] have it already for quite some time already [01:15] ok. [01:16] any estimates as to when I should try back? [01:16] debian import freeze? [01:18] first alpha, or later [01:18] feature freeze it shoudl start being safe and interesting [01:21] thanks. will try it again after alpha 1 [02:13] does hardy have kde 4 in the repos? [02:15] without a working x, what would be the point? [02:15] so x is broke atm huh? [02:16] that is the consensus [02:19] well...once x is fixed.... is kde 4 in the repos? [02:19] that would likely be one of the last things to make it--best to try a livecd of it now [02:23] it's only broken if you break it yourself, by not looking [02:23] kde 4 beta 3 is in the repos [02:24] oops sorry Hobbsee [02:24] but, a lot of people are being idiots, and breaking it. === Hobbsee changed the topic of #ubuntu+1 to: Welcome to #ubuntu+1 "Home of the Hardy Heron" | This channel is for Hardy discussion only | If you need help with dapper/edgy/feisty/gutsy join #ubuntu | Release schedule not final yet | If you are here to ask questions such as "what repositories do i use?", "is hardy going to break for me?", or update without checking what is to be updated, DO NOT RUN HARDY === Hobbsee changed the topic of #ubuntu+1 to: Welcome to #ubuntu+1 "Home of the Hardy Heron" and X breakage| This channel is for Hardy discussion only | If you need help with dapper/edgy/feisty/gutsy join #ubuntu | Release schedule not final yet | If you are here to ask questions such as "what repositories do i use?", "is hardy going to break for me?", or update without checking what is to be updated, DO NOT RUN HARDY [02:25] Hobbsee: cool. thanks. I ran with fiesty and gutsy long before you were "supposed to" on a production system. Thikin about doin the same with hardy.... === Hobbsee changed the topic of #ubuntu+1 to: Welcome to #ubuntu+1 "Home of the Hardy Heron" and X breakage | This channel is for Hardy discussion only | If you need help with dapper/edgy/feisty/gutsy join #ubuntu | Release schedule not final yet | If you are here to ask questions such as "what repositories do i use?", "is hardy going to break for me?", or update without checking what is to be updated, DO NOT RUN HARDY [02:25] WorkingOnWise: yeah, but this early is fairly insane, unless you're actually doing development of it [02:26] Last I checked, there were still some 7000 builds to be done from debian imports. [02:26] + new [02:26] Oh, of course. [02:27] yeah....I figured....I'm gonna resist till herd 1...hopefully :) [02:27] Proabably "flock", unless there's something specific to herons. [02:27] I suppose there probably must be. We should have a rook release - then we could release parliaments :) [02:28] long wait for that one [02:28] no, it's alpha's this time. mdz's call [02:28] I'm an old Windows /DOS dog....x breaking is a total catastrophy! :-D [02:33] anyone here a member of the hardy mailing list? [02:35] which one? [02:35] hardy-changes? [02:35] gnomefreak mention it yesterday--any would be fine--just would like to subscribe [02:35] err mentioned [02:38] or devel mailing lists? [02:38] Hobbsee: that would be it. Thanks--will gooogle it [02:38] err google === elkbuntu_ is now known as elkbuntu === stephanie_ is now known as Tyler_Durdan [03:20] bazhang: it is hardy-changes at lists.ubuntu.com [03:22] gnomefreak: thanks so much--sorry to ping you. appreciate it. [03:22] its ok just working late getting ready for thursday meeting [03:22] cheers1 [03:22] err cheers! [04:07] What package do I need to install for Dolphin to show previews of video files? [04:08] Creationist: you want #kubuntu [04:09] bazhang: Well, I asked there and no one is around. But it is also relevant here since Hardy will have the same ability ;) [04:23] NO. [04:24] Err [04:24] bad caps [04:24] but [04:24] thats like asking for linux help in microsofts forums because they both can run on a pc [04:31] looks like mythtv will be even better in hardy. good news. [05:48] * cafuego runs NastyAccident through with a double-edged sword [05:48] owwh. [05:49] Oops ;-) [05:49] * NastyAccident stags cafuego with his claymore. [05:50] stabs* [05:50] dang nabbit. === Tomcat_` is now known as Tomcat_ === saispo is now known as saispoo === saispoo is now known as saispo|o === saispo|o is now known as saispo === chand[aw] is now known as chand [15:11] where is a good place to get some information about hardy?, like eta's on kernel/X updates, features, etc [15:11] the alpha release notes [15:11] when they happen [15:11] bardyr: https://wiki.ubuntu.com/HardyReleaseSchedule [15:12] Hobbsee, are there any "progress" blogs or something ? [15:12] bardyr: that's them. [15:12] bardyr: basically, people are busy getting stuff done, rather than blogging :) [15:12] Hobbsee, probably, i just want my 2.6.24rc2 kernel :) and other cool stuff [15:13] :) [15:13] so do i...so do i. [15:13] "whne it's done, and it all builds" [15:13] mailing lists are nice too at lists.ubuntu.com [15:14] bazhang, actually the mailinglists are great :D [15:14] bazhang, thansk [15:14] ks [15:15] anyone got an idea why a kvm guest using vde would pause for __long__ periods during an apt-get, but a simple 'ping' from another terminal immediately unpauses it? [15:18] IntuitiveNipple, some Interrupts or events are faulty and ping/network stack awakes them? [15:19] bardyr: Hmmm. Been looking for some clues in logs/stats on both guest and host and can't find anything. Starting to annoy me now since I have to hand-hold the all the guests when they do build-tests [15:22] bardyr: no problem I was told about them by these kind gentlefolk :} [17:21] Hi! [19:07] hi [19:07] I just installed lzma on ubuntu 7.10 [19:08] and seen than the version of the package is lzma 4.43 [19:08] but it's not a stable release [19:08] and the official site say to don't use it [19:08] the format can change [19:08] the production version is 4.32.3 [19:08] http://tukaani.org/lzma/download [19:09] Popolon, and what do you want us to do? [19:09] it could be bad for user to use not finished format :( [19:09] oops [19:09] the official site is not up to date ??? [19:09] there is not 4.43 [19:09] only 4.42 experimental [19:11] http://tukaani.org/lzma/download [19:12] where is this 4.43 ?? [19:13] even the sourceforge.net site doesn't contain 4.43 [19:13] Popolon, look under "Source Code" [19:13] that's what I looked [19:13] s/what/where [19:14] there is definitivly no 4.43 [19:14] I use lzma on my main computer (in linuxfromscratch, not ubuntu) [19:14] i have a second computer with ubuntu [19:15] slackware use lzma as default compression for its packages since at least 1 year [19:15] It is far better than bz2 [19:15] and reduce a lot usage of space disk and bandwidth [19:15] the compression is slower and need more ram [19:16] but the decompression is faster and lighter than bz2 [19:16] this really the ideal for distro [19:17] Popolon, its not ideal if packages takes +3 times as long to compress [19:19] but the package is only compressed one time by dev [19:19] and transfered decompressed lot of times by user [19:21] this could reduce bandwitdh from several petabytes of transfert [19:21] and save some megawatts around the world for decompression [19:21] gzip is much faster for decompression? [20:43] bardyr, sure gzip is faster, but don't compress very well [21:33] gn8@all === Mez|Away is now known as Mez === Mez|Away is now known as Mez === Mez|Away is now known as Mez === Mez|Away is now known as Mez === Mez|Away is now known as Mez