[00:30] does hardy even exist yet? [00:33] ailean: not really... the toolchain is there, and i think they're starting to import packages from debian, but that would be about it [00:34] the topic suggests that there's something to work with :) [00:35] ailean, Yes, it does exist. Feel free to upgrade but I doubt it'll work, lol [00:35] (for long atleast) [00:35] i'll leave it a while :D [00:35] 210 packages, 180MB or so [00:36] wouldnt hurt to use it in a VM, test bugs and such [00:36] yeah, maybe . . . [01:26] so how much awesome is hardy than gutsy so far? [01:26] i doubt it even runs [01:27] so I should wait an hour or two before updating? [01:27] or even a month or 3 [01:29] check out the proposed features at www.fsckin.com [01:32] Is kde4 planned to be default for hardy kubuntu? [01:33] I can't wait for Hardy... I can't wait for Hardy! === Pici` is now known as Pici [01:58] Yo, what's are the repos for Hardy? [01:59] mm [01:59] is it just hardy or heron? :P [01:59] martalli: no [01:59] Sonicadvance1: its the same as every other release [01:59] Sonicadvance1: if you do not know the answer based on that upgrading is a really bad idea [01:59] I'm just trying to make sure! D:< [02:00] let me rephrase that [02:00] upgrading is a really bad idea [02:00] A lot of choices in life are bad ideas [02:01] right [02:01] that doesn't mean you should make them [02:01] sometimes you just have to [02:01] :D [02:01] and the rest of the time it just makes you an idiot [02:02] woo idiocy [02:41] hydrogen: Maybe it would be nicer just to remind people that early versions of any ubuntu+1 will be very unstable, with no guarantees of staility [02:41] s/staility/stability [02:41] martalli: thats what the topic is there for [02:41] :D [02:41] I'm here for when the topic just isn't enough [02:42] oh look, It's done installing all the packages [02:42] These days, apt-get is just a disappointment [02:43] Back before the final release, there were always new packages to install. Of course, now my audio works, so the trade off might be worthwhile [02:44] * Sonicadvance1 breaks martalli's audio and runs [05:11] Well, That was horrible :D [05:13] installed it? [05:13] Installed it, then reinstalled 7.10 :D [05:13] haha [05:13] X didn't work [05:13] oh well [05:13] no bulletproof X :{ [05:14] :D [05:14] I noticed [05:14] failed when falling back on the failsafe X [05:14] which made me laugh [05:15] :} [05:15] at least you could find some humor in it [05:15] eh [05:15] eh [05:16] eehh [05:16] eeeeehh [05:16] XD [05:16] :D [05:16] so [05:16] where can i find a link on how to creat a spec for migrating one package to another [05:18] aw, now I need to reinstall libgpod :P [05:55] is Xorg broken in hardy? [05:55] i am getting conflicts [05:55] probably [05:55] early reports say yes [05:55] :-( [05:55] lets fix it! [05:56] it's been like 2 weeks... [05:56] ill help -- what can i do [05:56] and failsafe x may fail [05:56] failed to load modules vesa, and kbd [05:57] interesting [05:57] what is the loading process? [05:57] and why did it fail? [05:58] hehe [05:58] early report from me! D:< [05:58] come back in a month :) [05:58] i think it is because xserver-xorg-core wont build [05:58] and also xserver-xorg-input is also not available in repos [05:59] had heard that tribe 1 will be end of this month [05:59] where can i request an update of one package (kdesvn) ? [05:59] #ubuntu-dev? [06:00] oo, tribe 1 at the end of the month? :D [06:00] i guess launchpad is good place to request also [06:00] * crdlb wonders where all the patience went :( [06:01] i search thru launchpad, but i can't find any information about requesting updates of packages [06:03] https://bugs.launchpad.net/debian/+source/attal/+bug/2596 - there's one request [06:03] Launchpad bug 2596 in attal "Attal in Ubuntu is almost not playable, 4 new attal versions (0.9.3, 0.9.4, 0.10, 0.10.1) released, please update" [High,Fix released] [06:03] it's like normal bug request === elkbuntu_ is now known as elkbuntu === lemonade is now known as lemo === Tomcat_` is now known as Tomcat_ [09:12] <`23meg> Hobbsee, ping ping [09:15] <`23meg> should I recommend people to use "update-manager -d" to start testing development versions, or to change their sources.list? AFAIK update-manager doesn't start notifying about development versions until a certain phase; when exactly is that? [09:27] `23meg: when it gets put in, i expect. cant see the point of putting it in yet, as testing is rather frought with danger atm. [09:28] `23meg: either should work fine at this point. i havent seen much breakage yet - although there's X stuff that looks fun. [09:29] <`23meg> Hobbsee, update-manager doesn't seem to be working atm [09:30] `23meg: then, recommend the sources list. [09:30] <`23meg> Hobbsee, I'm writing a "how to test" sticky for the forum, that will be up for the duration of the cycle [09:30] <`23meg> hence my asking [09:30] `23meg: don't do it till the autosyncs have finished, etc. [09:31] `23meg: pepole will just hose their X, by forcibly dist-upgrading. [09:31] <`23meg> Hobbsee, I know, I'll mention that [09:31] <`23meg> Hobbsee, so either will work all along the cycle and are equally recommendable? [09:31] `23meg: well, update-manager's sort of working now. [09:31] `23meg: the other, of course, always works. [09:31] <`23meg> Hobbsee, ok, thanks [09:32] there will be breakage, so it's probably safer to use the manual approach. [09:32] it's really not supposed to be used at this point. [09:32] although, i fixed gnome-hearts yesterday [09:32] so that actually starts now. [09:32] <`23meg> haha [09:33] <`23meg> Hobbsee, should I drop an approximate time that's safe an meaningful to start testing? [09:33] alpha 1 for the earliest adopters should be sufficient. [09:34] i'd be one of the few devs running it now, i think [09:34] <`23meg> yeah, I bet most don't [09:34] makes no real sense to run it [09:36] `23meg: better to try and get the forums people to do useful stuff - most bugs are getting fixed inadveratntly at the moment, so there's no poitn in filing them. or at least, as far as i've seen [09:38] <`23meg> Hobbsee, will do === Frogzoo_ is now known as frogzoo [09:40] `23meg: particularly about packages not there yet, or dependancies. [09:41] <`23meg> Hobbsee, yes, I'm mentioning that [09:41] cool [09:42] `23meg: getting there! https://edge.launchpad.net/ubuntu/hardy/i386/+builds?build_text=&build_state=pending&start=75&batch=75 [09:42] wow, less than 10000 now for all arches combined! [09:42] https://edge.launchpad.net/ubuntu/hardy/+builds?build_text=&build_state=pending [09:42] build build build! [09:44] <`23meg> Hobbsee, thanks for reminding; I'll link to the arch pages so that people can check the pending builds, dependency waits, etc. [09:45] `23meg: i doubt it'll help - it tends to be hard to understand. [09:45] but, it might be useful for some [09:45] <`23meg> Hobbsee, hard to understand what? [09:45] what those pages mean. [09:45] why some of the stuff that has built isnt in teh archives yet [09:45] etc [09:45] <`23meg> if people ask questions, I'll direct them to you :P [09:46] heh [09:46] i'll just not respond :P [09:50] Hobbsee: hey, can you explain the realtion between building and buildscore to me? :) [09:52] hellboy195: higher buildscore == get queued higher. [09:52] simple :) [09:52] Hobbsee: thx. and how high does the buildscore could go? [09:53] no idea [09:53] Hobbsee: ok ^^ anyway thx :) === marko-_-_ is now known as marko--- === marko--- is now known as marko-_- [11:47] update wants to remove 33 xserver packages [11:50] Oh Oh! here comes some serious breakage :/ [12:01] well not so much breakge that I can see . let;s hope it stays this way === blubbeer is now known as Kill_X [14:39] Hi all [14:40] just wondering as Herdy is going to be another LTS, will there be a document on upgrading 6.06LTS (server) to 8.04LTS Server without trailing through each release between? [14:40] That's the plan. [14:40] that is, once it's released... not for Alpha/beta [14:41] excellent [14:41] I normally do alot of testing and playing with the desktop releases, but i tend to leave my server be :) [14:42] so upgrading from LTS to another LTS would be great [14:53] Anyone good with solving 64-bit / 32-bit compilation issues, specifically, solving the macro-hell that is building qemus 32-bit targets on x86_64? [15:35] I truly can't wait until Alpha 1 [15:37] Hah, you will ;) [15:45] don't have much choice BUT to wait :D [15:46] I know lol, but it's seriously one of the few things to look forward to this year lol [15:59] <`23meg> Hobbsee, I ping you [15:59] `23meg: pong [16:00] <`23meg> I'm recommending against filing bugs from VM testing installs against anything that has low level relations with hardware [16:00] <`23meg> you think? [16:03] <`23meg> Hobbsee, like, people shouldn't file kernel or X bugs if testing in a VM, right? [16:03] um...probably not so useful. *shrug* [16:04] no point filing kernel bugs yet anyway - no new kernel [16:04] What about bugs (such as https://bugs.launchpad.net/ubuntu/+bug/157366) that are about Ubuntu not working correctly in a VM? [16:04] Launchpad bug 157366 in ubuntu "Gutsy freezes in VMware Workstation 6.0.2-59824" [Undecided,New] [16:04] <`23meg> Hobbsee, I'm not talking about yet, but in general [16:04] well, it can be useful [16:04] that's what people test installs on, etc. [16:04] but real h/w is more useful [16:06] <`23meg> Hobbsee, what should I list in the sticky thread as the "don't file bugs if..." cases? I'm thinking frankensteined installs with non-ubuntu libraries, binary drivers, etc. [16:07] `23meg: anything that's had automatix on it, anything from non-ubuntu packages. [16:07] binary drivers tend to be pointless, too [16:09] <`23meg> Hobbsee, k [16:09] I thought apport refused to file bugs if it detects .automatix files [16:10] Pici: it does === acuster is now known as avc_afk [16:25] don't file bugs if... you upgraded because it sounded fun [16:27] <`23meg> Hobbsee, that should be "binary drivers not supplied by Ubuntu", right? [16:27] `23meg: even if ubuntu supplies the binary drivers, by nature, they cant fix it. [16:29] <`23meg> Hobbsee, I know, but bugs -are- tracked for l-r-m, etc. [16:29] `23meg: sure, but nothing gets done about them. [16:30] for teh most part [16:33] <`23meg> Hobbsee, I'm just trying to get the wording right [16:33] <`23meg> Hobbsee, --> (For the kernel, X and other components that interact closely with hardware) If you're using binary drivers not supplied by Ubuntu === avc_afk is now known as acuster === Aishiko_ is now known as Aishiko [18:17] who is rockin' hardy? [18:18] people who don't need X [18:19] woo [18:20] i compile my own X [18:21] just use base system =) [18:32] where can i download hardy? i need something to mess around with === databuddy is now known as thebingwinnah [18:38] SpudDogg: cant u distro upgrade from the current === thebingwinnah is now known as thebigwinnah === kalpik is now known as kalpik|busy [19:15] Hey Hardyians [19:47] hello can someone point me to a download link for the beta? [19:51] Don't think there are any builds of Hardy yet [19:53] ok thanks Viper550 [19:53] I think we have a roadmap or something [19:54] I just figured since it said not to run hardy there was one, naturally I want to run it anyway [19:54] lol === awalton__ is now known as newtwalton === bmk789_ is now known as bmk789