[00:06] slangasek and cprov: Thanks. === jamesh_ is now known as jamesh [00:41] doko: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38562 [00:41] gcc.gnu.org bug 38562 in c++ "mysql miscompiles and causes testsuite failures" [Normal,Unconfirmed] [00:45] kees: perhaps also useful to add the preprocessed log_event.cc as well [00:45] arthur-: good idea, I will add that [00:46] kees: please could you update the field keywords to wrong-code, known to work to 4.3.2 and known to fail to 4.3.3 4.4.0, and prefix the subject to [4.3/4-4 regression] ? [00:46] I'm not allowed to do so [00:46] doko: I note boost 1.3{6,7} don't exist in Jaunty currently. [00:47] doko: done [00:47] doko: I wanted a working schroot on armel, which is why I uploaded the workaround. Would you like me to revert it? [00:47] StevenK: yeah, maybe needs a sync after the alpha release [00:48] kees: 4.4 rather than 4-4 ;) [00:48] I didn't think it had updated in Debian ... [00:48] It hasn't [00:48] arthur-: I was wondering about that. :) [00:49] kees: yeah, doko does so much typos ;p [00:57] doko: However, schroot is universe, so we can just play now, if you want. [00:59] arthur-: no difference in -E output between -O1 and -O2 (as I suspected). is it still useful to attach the -E output? [01:03] kees: -E doesn't run compiler, so optimization level doesn not influ on it, and yes it is, much easier to check if the bug is fixed from it after or even to extract a testcase [01:04] okay, adding [01:30] * calc is at the LOCO meeting in a reasonably authentic british pub [01:32] * ogra wonders if "reasonable" means a union jack on the wall or guiness in bottles :) [01:34] they have beer and stuff and fish and chips that seem about like at morpeth [01:34] my wife got fish and chips at a regular seafood place here in the US and it wasn't anything like the pub stuff [01:34] heh, i was just kidding [01:34] :) [01:35] slangasek: Just did a kubuntu-meta upload that I think will get us back under the size limit. [01:35] kubuntu on diet :) [01:35] ScottK: great, I'll set the CD builder up to watch for it [01:36] what is the name of the gnome timekeeping app? [01:36] hamster [01:37] ogra: you sure about that? i don't see a package [01:37] ah hamster-applet [01:37] hamster-applet [01:37] ok thanks :) [01:37] :) [01:37] how... intuitive? [01:37] lol [01:38] i did a dpkg -p hamster instead of doing a apt-cache search [01:40] baah. I use Tomboy for that :-P [01:40] wow we have 8 people here so far, a record turn out i think ;-) === pgraner_ is now known as pgraner-lt [01:46] dumb pub moved us under speakers and then cranked the volume to max [01:46] can't even hear myself think [01:48] you got IRC who needs to hear ... just make the others fire up their laptops [01:49] there is only two other people with laptops i think [01:49] i think they aren't really geeks just pretend geeks ;-) [01:53] there is someone here giving out linux journal swag but apparently doesn't work for them [02:13] slangasek: Would you please remove kdeplasmoids kdeplasmoids-dbg kdeplasmoids-data - They are all transitional packages that can safely die. [02:14] ScottK: are they NBS? they aren't showing up in the latest report yt [02:14] yet [02:15] They are. The kdeplasma-addons upload I did a couple of hours ago was missing them (by design). [02:15] ok [02:15] You'll see the version they show up under uninstallable isn't the current one for that package. [02:16] done [02:17] slangasek: That will leave just plasmoid-quickaccess and libplasma2 uninstallable for KDE packages. Both those can be binary demoted to Universe. The libplasma2 -> libplasma3 transition will take a while to complete. [02:17] slangasek: Thanks. [02:18] hmm, are they uninstallable because they depend on universe packages, or non-existent packages? [02:18] I don't see the point in demoting them if they're uninstallable regardless [02:18] rsibreak is screaming at me. [02:19] If a vanish for half a minute, that's why [02:19] libplasma2 is uninstallable. [02:19] plasmoid-quickaccess will eventually get ported to libplasma3, so leaving it is probably best. [02:20] ok; I'd just as soon leave libplasma2 on the main uninstallables list as anywhere, then - or else NBS it out directly [02:20] Let's leave it then. [02:20] The NBS list currently makes me cry [02:21] StevenK: I've done a pass earlier today, I just haven't refreshed the list because I can never remember where to do it [02:40] flashplugin-nonfree seems to be broken [02:41] jcastro: i'm going to try to give your ontario speech but its really loud here so not sure if its going to work well :-\ [02:41] jcastro: and no projector [02:42] pitti: Something I forgot to suggest at UDS... It seems to me that Apport & Launchpad should conspire together, as appropriate, to set the "affects me" flag for people filing duplicate crash reports. This may not have to be Apport-specific, though, as it seems you'd want that for anyone saying, "yes, that's my bug". [02:43] rlaager: aiui it already does that [02:43] rlaager: at least if they are similar enough [02:43] Hmm. I don't recall seeing it do so, but I suppose I could've missed it. [02:43] rlaager: well no but it consolidates duplicates [02:43] rlaager: so you are correct [02:43] rlaager: so yea doing a me too instead would be better [02:44] calc: steal as much as you like [02:44] jcastro: heh :) [02:46] Well it doesn't even default to 'affects me' when you report the bug, so I doubt it does it for dupes. [02:49] slangasek: Any idea how long until there's a new Kubuntu CD image? [02:49] * ScottK isn't sure how to keep track of the process. [02:50] ScottK: alternate and livefs both building right now; so should be < 1h [02:50] slangasek: Thanks. [03:30] guys, is there is any ideas why /bin/sh is still a symlink to /bin/sh [03:30] to /bin/bash [03:30] instead of having regular sh, which is way faster [03:32] sarah@neptune:~% ls -la /bin/sh 2:32PM [03:32] lrwxrwxrwx 1 root root 4 2008-09-12 15:04 /bin/sh -> dash [03:33] $ ls -l /bin/sh [03:33] lrwxrwxrwx 1 root root 4 2008-02-06 19:02 /bin/sh -> bash [03:33] i was not changing nothing manually [03:33] avb: What release are you running? [03:33] 8.10 [03:33] i think you've done something to your system - the default changed a few releases ago [03:34] i case i was not making clean installs [03:34] avb: New install or upgraded from earlier? [03:34] for a couple of releases [03:34] That may be the reason. IIRC that change was made on install, not upgrade so stuff already there wouldn't get broken. [03:34] i see [03:34] # update-alternatives --config /bin/sh [03:34] No alternatives for /bin/sh [03:34] not sure if that started with dapper or edgy [03:34] thats another issue [03:35] should i fill a bug? [03:35] i just checked system dash is already there [03:35] but in postinst it havent made update-alternavites [03:35] avb: No, it's by design. /bin/sh is just a symlink. Change it. [03:36] thats a case, why new install have dash, and dist-upgrade dont [03:36] ScottK, but its realy looks like a bug, not like a design [03:36] probably lets change the design a bit? :) [03:37] i can submit patch if needed [03:37] not a big deal [03:37] avb: Because an existing system may have third party stuff on there we can't know about and we are conservative about breaking stuff on upgrades. [03:37] No, this is on purpose to be careful with not causing breakage on upgrade. This is a feature and no bug. [03:38] heh [03:38] thats realy weird behavoir. once we are moving from upgrades to reinstalls [03:38] smells like 2nd windows [03:39] anyway, any 3rdparties should be informed once they bashing once interpriter is set to /bin/sh [03:40] There's a lot of config stuff that doesn't get touched on upgrade. [03:40] Postfix configs for another one. [03:42] yes, i will be more then happy if it will be just bash [03:42] :) [03:43] i dont have my splash since breezy :) [03:43] anyway i disabled it, but still [03:43] then it was a network-manager and couple of other stuff [03:59] slangasek: Is 20081218.2 the one I should be looking at or is it not published yet? [04:00] slangasek: I'm likely to head to bed soonish and I'd really like to know if anything else needs to be whacked out of there. [05:06] ScottK: hrm, yes, .2 was the build in question [05:06] ScottK: for desktop, anyway [05:06] slangasek: OK. Then apparently I suck. [05:07] what went wrong? [05:08] http://cdimages.ubuntu.com/kubuntu/daily-live/20081218.2/ says still oversize. [05:08] no idea why, yet? [05:08] I know why some stuff got bigger. [05:09] the .1 and .2 builds have identical livefs on them [05:09] did the livefs build fail? [05:09] Dunno. I'm pretty new to this part of things. [05:10] http://people.ubuntu.com/~ubuntu-archive/livefs-build-logs/jaunty/kubuntu/ [05:10] full-sized build logs for 20081218.1 (yes, the livefs serials aren't guaranteed to match the CD serials) [05:11] OK. [05:11] so, the livefs build didn't fail at least [05:12] kubuntu-desktop 1.105 is present in all the images [05:12] slangasek: That one was built with kubuntu-meta 1.05, not 1.06, [05:12] 106 is what we wanted. [05:12] ... oh. [05:13] sorry, when I looked 106 wasn't visible in LP yet, I had assumed 105 was correct :/ [05:13] ok, re-triggering [05:13] Finding something that had a version number in it helped a lot. Thanks for the pointer. [05:14] slangasek: Next question: is getting proper builds on armel something worth uploading stuff for now? [05:14] yah, sorry for not checking the version number with you explicitly earlier :/ [05:14] NCommander is confident he finally has kde4bindings (which is the key to most of Kubuntu Desktop) figured. [05:15] It builds fine [05:15] I'm just tweaking some of the install rules [05:15] It'd take an upload of kde4libs, python-qt4, and kde4bindings to fix. [05:15] well, I didn't have any intention of releasing armel images for alpha-2 yet [05:15] OK. [05:15] ScottK, hold on, I'm still making rules changes [05:15] I'll hold it until after the milestone then. [05:15] sounds good [05:16] NCommander: No problem. That sounded like don't do it from the RM to me. [05:24] slangasek: The changes I did for that upload should save north of 40MB. They'll do for alpha2, but not for the long run. === hyperair1 is now known as hyperair [05:32] * slangasek nods [05:33] ScottK: amd64 alternate is still a hair oversized :( [05:34] Gumble. [05:34] 2624K, to be exact [05:36] slangasek: Are the others OK [05:36] alternate i386 [05:36] livecd always takes longer to build, so I don't know ye [05:36] t [05:36] OK. [05:45] slangasek: You didn't put the publisher on manual did you? [05:45] no [05:45] We got plasmoid-quickaccess fixed for libplasma3, but the binaries have been sitting unpublished for over an hour. [05:46] I was hoping to put that back (it's only 68K) [05:46] Grumble's more. [05:46] hmm [05:49] ScottK: looks like the hourly job from 2h ago overran and as a result, the last hourly job failed on the lock [05:49] Thanks. Patience then. [05:57] what's the new package queue url in launchpad? [05:57] /ubuntu/jaunty/+queue, I believe [05:57] slangasek: thx [06:03] ScottK: liveCD built, and the /only/ difference in the livefs contents is the kubuntu-desktop version [06:04] slangasek: Built fits? [06:04] oversized, since there was no other reduction to the livefs contents [06:05] slangasek: OK. So I found the 2624K for the amd64 alternate. [06:05] How much more do we need? [06:06] for desktop? were the previous changes not expected to have an effect on desktop CD size? [06:07] * ScottK is confused he thinks. [06:07] The amd64 alternate was 2624K over, but i386 fit. [06:07] yes [06:07] desktop just built, and the results are that nothing changed in the livefs except for the kubuntu-desktop version [06:08] so, still oversized by ~40MB [06:08] OK. That's odd. [06:08] So the alternate shrank, but live didn't? [06:08] correct [06:09] Odd [06:09] Did the task change as well as the metapackage? I seem to remember this sometimes taking an extra cycle for timing reasons. [06:10] appears to be an issue of the Task: field not having updated yet for these packages in the archive [06:10] * ScottK looks at the logs [06:11] it should right itself with the next publisher run; I guess we haven't had enough publisher runs yet, probably due to overruns [06:11] OK. [06:14] slangasek: I think I have enough shrinkage to cover the 2624K. If I upload that and go to be, can you just pitch language packs off the live until it fits if needed? [06:14] go to be/bed. [06:14] can do, yes [06:15] slangasek: OK. 107 uploaded. I'm off to bed. [06:15] 'night [06:33] In researching LP #305001, I noticed that python-elixir and python-sasync both ship versions that can't work with the python-sqlalchemy in Hardy. Should I fix this through -backports or try to get them SRU'd? [06:33] Launchpad bug 305001 in hardy-backports "Please backport sqlalchemy 0.4.8 from Jaunty to Hardy" [Undecided,New] https://launchpad.net/bugs/305001 [06:34] ebroder, If they truly can't work, it would be an SRU, although you should be seeking the minimal patch to make them work. [06:36] Oh wait...I may be lying about python-elixir. I need to do more research [06:37] persia: So I should try to do this by attempting to extract the necessary patch to add compatibility for sqlalchemy? That's substantially more work and more likely to regress than just pulling the newer version... [06:38] ebroder, I'll agree on the more work part. Whether it is more likely to regress is probably a matter of the final resulting patch size. I'm not in an SRU approval team, but if you're sure it's worse to make a patch, you'll want to state your argument very carefully, and be absolutely sure there isn't some small patch that works. [06:39] persia: Yeah...I'm not actually willing stand by that assertion. I don't use the packages myself, so I'll file the bug - maybe someone who cares will deal :-P [07:11] hi [07:39] doko_: looking at the changelog, there used to be a python-numpy-ext package split off, and you merged it in? [07:40] slangasek: can't remember ... looking ... [07:40] it was a while ago :-) [07:43] slangasek: hmm, have to look ... but probably not in time for the alpha [07:44] * slangasek nods [07:45] fwiw, I'm currently poking at it because I don't see anywhere else that I can claim back even close to that amount of space, and amd64 is oversized [07:45] so if nothing else, I may have a patch for consideration in the next hour or so [07:50] lapack_lite.so could be split off, but I'm unsure about _dotblas.so which is in core [07:50] splitting the .py and doc files doesn't save much === doko_ is now known as doko [07:52] slangasek: how do you get rid of _dotblas.so? [07:52] good morning [07:52] doko: dotblas.so is easy, it's only loaded opportunistically [07:52] # try to import blas optimized dot if available [07:52] try: [07:53] lapack_lite actually seems to be hooked deeper, there are a lot of references to linalg [07:55] omitting the tests or oldnumeric doesn't save much [07:56] well, getting rid of fortran will save a lot [07:57] why is setup.py packaged? [07:57] I... don't know :) [07:59] hrm, the hooks into lapack_lite/linalg are way too deep for this to be even a remotely "quick" fix [08:01] slangasek: maybe have an -ext package with the lapack_lite linked with fortran, which diverts the lapack_lite in a reduced -numpy package, and then build lapack_lite with the included *_lite.c files? [08:01] so lapack_lite is buildable in some reduced, non-lapack form? [08:03] hmm, looks like that could work, after all [08:03] but I don't think I would succeed in getting it to build at this hour === dholbach_ is now known as dholbach === fargiola` is now known as fargiolas [08:19] slangasek: hmm, maybe for a quick solution, just drop the b-d on lapack and blas and build it this way? [08:20] doko: ok with me; I guess we need to remember to revert that after the alpha? [08:25] slangasek: yes, bug report for the reminder should be fine. but I can only upload later today [08:25] * slangasek nods [08:36] slangasek: thanks for the fix in deskbar-applet! [08:36] mvo: n/p [08:54] ScottK: looks like we just need to drop the Japanese langpack from desktop/i386 and we're set [09:22] doko, DktrKranz: what do we do about bug 195407? [09:22] Launchpad bug 195407 in mingw32 "mingw-4.2 requires shared lib{gcc,stdc++} for cross-dll exceptions" [Low,Confirmed] https://launchpad.net/bugs/195407 [09:29] dholbach: I haven't tried, but there were some discussions on debian remote watch [09:30] DktrKranz: aha [09:34] dholbach: I'm unsure how to proceed, since Debian side stalled a bit (latest update was in early 2007, IIRC) [09:35] DktrKranz: maybe doko knows [09:38] dholbach: DktrKranz: morning gents! [09:39] hiya norsetto my friend :) [09:40] he's come to speak with you again [09:41] (that sound-of-silence reference was a bit too weak) [09:41] hi norsetto, Master of Rivers [09:42] highvoltage: hi to the other side of the globe too ;-) [09:43] norsetto: hi :D === fargiola` is now known as fargiolas [11:41] liw: at your convenience (and perhaps after alpha 2), could you cause there to be a new upload of system-cleaner to jaunty (even if it's no-change)? A Soyuz bug has meant the Architecture: all binaries have gone missing from armel's Packages files; we've encountered this before with binaries copied from -updates and it's been raised with the Soyuz team, but for now a reupload is the simplest solution [11:42] could somebody score up debian-installer a bit on armel? I'd like to know whether it'll build before Saturday [11:45] cjwatson, ack, will do [11:46] now would be a good time to re-visit the question of the software's name -- "Cruft Remover" turns out to be a bad name [11:48] I thought cruft was a non-jargon word too but apparently I was wrong. I think I was thinking of "lint", which is the stuff you pick off clothes [11:49] I'm in favour of (almost) anything that allows us to stop endlessly wasting time on naming arguments [11:49] liw: just call it lint remover [11:50] I'd like to change the word "remover" as well, since not everything the program does is remove things, sometimes it adds them too [11:50] just read cjwatson's reply like minds [11:50] the word "janitor" keeps bouncing inside my skull [11:50] but yeah, I would prefer to not re-visit this question, either [11:51] The last Kubuntu live CD came out slightly over-size on i386. I've adjusted language packs, so I think it's good. Would someone please kick off another CD build? [11:51] hey ScottK [11:52] ScottK: which seed(s) did you change? [11:52] oh, hey, I could just look [11:52] morning cjwatson [11:52] morning [11:53] cjwatson: Kubuntu live [11:53] Or more specifically, kubuntu.jaunty live. [11:53] NCommander: Heya. [11:53] how goes it this morning? [11:53] ScottK: hmm, when? last commit was 0855 UTC by Steve [11:54] cjwatson: OK. Or I didn't. [11:54] * ScottK looks. [11:55] cjwatson: It looks to me like he and I made the same change, but I hadn't updated. It also looks like he didn't respin the CD unless one is in progress now. [11:56] * ScottK doesn't know how to tell about that. [11:57] he may have had to wait for a publisher run [11:57] there's nothing in progress right now (the logs are published so in principle you could tell from that, but they're only mirrored hourly) [11:58] I've kicked off a build now [11:58] cjwatson: Thanks. [11:58] * ScottK sits back and tries to figure out how he got in charge of making Kubuntu fit on the CD during Riddell's vacation. [11:58] liw: (did "System Janitor" ever come up as a suggestion?) [11:59] ScottK: just lucky :-) [11:59] ;-) [11:59] liw: oh, https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2008-November/006139.html [11:59] cjwatson, someone did suggest System Janitor, but to me, it's uncomfortably close to System Cleaner [12:00] liw: I don't think you need to avoid "System X" [12:00] "System Cleanser" does seem too close for comfort [12:00] cjwatson, am I correct in thinking that we're almost out of alpha 2 freeze :-)? [12:00] System Decruftifier [12:00] NCommander: we'll be out of it when Steve sends the release announcement [12:00] decruftifier> oh god no :) [12:00] :-( [12:01] * NCommander listens to black hole sun [12:03] * NCommander pictures cjwatson with some sorta giant cruft bufter gun dressed as a terminator [12:03] .... [12:03] I'm not sure if thats scary or awesome :-P [12:03] s/bufter/buster/g [12:07] bryce: in your 'should be' diagram, the hal-addon-acpi line should be solid, not dashed [12:08] guys, one simple question... in order for someone who's been win based developer and would like to migrate to Linux development, which programming lang and ide would you suggest that he use? [12:11] that isn't a simple question because it depends on their experience and (perhaps much more strongly) on what they want to do. [12:12] ah... well, I can tell you some stuff, for example, I've been developing mostly with c#, for about 3-4years now [12:12] before c#, I used c,c++ and somewhat java [12:13] the logical answer would be c++, but I really do not know, how much c++ is used in linux development and linux apps development... [12:13] It's used a lot in KDE. [12:14] Qt is C++, GTK is C, but there are some C++ GTK apps as well [12:15] ScottK I read about c++ and KDE, but, since I'm using gnome and prefer my Linux not to look like Win... [12:16] Well C# is pretty much C# if you like such things. [12:17] I dont like c#, to be honest... I did like Visual Studio and stuff that it does and how it makes you less code... and I have to use it, for now, to make living... what about java and/or python? [12:17] I aint really familiar with python, heard only great stuff about it... and java is something I know already [12:17] ays: do you want to start a new project, or contribute to existing projects? [12:18] you can use all of those languages for writing GNOME applications, though I am not sure Java-based GNOME apps are accepted officially [12:19] well... at this point, I don't think Im good enough to contribute to ubuntu community in development ways... so... when I get somewhat better in linux based development, I'd like to try to help and contribute in any way, either with current on with new projects [12:19] In Ubuntu, Python tends to be the language of preference for internal projects. [12:19] or* [12:23] ScottK, is there any major Ubuntu tool that isn't written in python? [12:23] (aside from the wiki, which I believe is perl based) [12:24] NCommander: Upstart [12:24] right [12:24] But thats kinda out of necessity ;-) [12:25] basically... it all comes down to python... regarding ubuntu, but what about creating apps for all linux platforms, for example, pdf reader or something like that? [12:26] ays: see above [12:27] c++ and python then... I thought so, but had to check... thank you all for the help. :) [12:32] ays: for the most part you can carry on using languages you're comfortable with, but you will likely have to learn new sets of runtime libraries. As for IDEs, well personally I'm old-school and use vi and make, but I hear that things like eclipse and anjuta are popular. [12:33] * persia plugs netbeans [12:34] cjwatson and slangasek (when he wakes): It fit. So all 4 Kubuntu images fit now. [12:34] cjwatson: Thanks. [12:35] doko: I just tested jvm.cfg-default. It installs as /usr/lib/jvm/java-6-openjdk/jre/lib/$arch/jvm.cfg-default, is it by design ? Tools like keytool (ca-certificates-java) or jsvc (tomcat) apparently only look for "jvm.cfg" [12:35] cjwatson thanks mate, I'll check 'em out [12:36] ScottK: cool [12:37] Koon: there's a patch (debian/patches/default-jvm-cfg.diff) to look for this file (which is not installed as a config file) [12:38] NCommander: the wiki is not Perl [12:38] I thought it was [12:38] doko: ok, looking [12:40] doko: then we should probably also teach jsvc to look for this file [12:41] Koon: I see, the jdk has a second copy, which is still unpatched ... === andreas__ is now known as ahasenack [12:42] doko: jsvc (commons-daemon) directly parses what's on the filesystem and explicitely looks for jvm.cfg, so I guess it needs to be taught about jvm.cfg-default [12:43] I'll investigate that, there might be another way around it [12:44] Koon: in this case, maybe assume just a default configuration? [12:45] doko: yes, theorically jsvc accepts a -jvm parameter to explicitely set the libjvm.so without looking at the conf file [12:46] though that seems to be buggy. I need to go deeper into that [12:46] doko: otherwise that sounds like a great solution to our problem, thanks :) [12:47] Would whoever updates the iso qa tracker please add http://cdimages.ubuntu.com/kubuntu/daily-live/20081218.5/ i386 and amd64? [12:47] Koon: -server seems to be safe choice, it's available on every platform/architecture [12:47] doko: yes, and that's one of the few jsvc doesn't even try to find :) It tries client, classic... [12:48] NCommander: Could you be pursuaded to take a glance at libaio? It's failing on all but the official architectures, and I haven't a clue where to start fixing it. [12:49] link? [12:49] Well, I probably do, actually, but it's easier to pretend not to. [12:49] https://edge.launchpad.net/ubuntu/jaunty/+source/libaio/0.3.107-1ubuntu1 [12:50] soren, amazing, it built on the itatinic [12:50] NCommander: It'll probably fail at runtime. [12:51] NCommander: Most of the test cases fail. [12:51] * NCommander winces [12:51] I don't think I even want to look at the code that could generate that build failure [12:52] Of course you do. [12:52] You like pain. We all know that. [12:52] * NCommander hurts soren :-P [12:52] Yes, I like pain, too. It's just that I'm into a different kind of pain these days. [12:52] .... [12:53] * NCommander bleaches his brain [12:56] soren, I think the test suite busted [12:56] soren, amd64's test suite blew up miserably as well :-) [12:57] the test suite is obviously not 64-bit clean [12:58] anyway, any objections if I only test build on sparc once I fix it? [12:58] (well, sparc/release archs) [13:00] PRobably not. [13:03] * liw ponders "Janitor Service" as a name [13:04] Oh [13:04] * NCommander hits his head [13:04] I see what's going on [13:05] liw, But it's not a service : it's a one-time thing, right? [13:06] persia, that's a good point [13:07] ah [13:07] crud, if I'm right on this build failure, I'm going to hurt the author [13:08] perhaps the naming problem is an indication that mpt is right and the whole program shouldn't exist and the functionality should be part of, say, update-manager [13:09] soren, found your build failure [13:09] /#warning Not really sure where kernel memory is. Guessing. [13:09] ;.; [13:10] NCommander, *blink* [13:10] That's code you DON'T want to see in a test suite [13:11] oh I see [13:11] It wants an invalid pointer ... [13:16] soren, see -motu [13:16] saw it [13:16] Can we just be cheap and do the same fix :-) [13:19] NCommander: Feel free to do the merge. [13:19] I was just going to implement the change as ubuntu2 [13:19] That merge looks ugly [13:19] It probably is. [13:20] although merge-o-matic did give a merge that only had the usual control issue [13:20] hrm [13:20] * NCommander does the merge instead [13:21] Better fix [13:21] \o/ [13:23] soren, merged [13:23] That was easier than it looked :-) === LucidFox_ is now known as LucidFox === davmor2 is now known as davmor2-away [14:18] Is stgraber the right POC for iso tracker updates? [14:21] ScottK, mostly, although #ubuntu-testing may have others. [14:22] persia: Thanks. === thegodfather is now known as fabbione [15:35] hello I have a computer which has stopped working with the latest versions of many linux distros. When I looked into this it seems all the ones that don't work - including Ubuntu and Fedora use the same - probably current version of Xorg. What do I need to do about this? My offending hardware is Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01) [15:35] At least that's what grep reports [15:37] gardier: this is not a support channel [15:38] please file a bug report about it and define what you mean by "it doesn't work" in that report [15:38] unless you're able to hack X yourself, the best thing to do is to file a bug with as much information as you can; https://wiki.ubuntu.com/X/Debugging may help [15:38] see also https://wiki.ubuntu.com/X/Reporting linked from that [15:39] tseliot I mean X wont run from any medium live cd or installed [15:39] Until O go back to an older version of xorg [15:40] gardier: please follow cjwatson's instructions [15:40] So I report it to Ubuntu not Xorg? [15:41] That's what I needed to know [15:42] OK thanks tseliot and cjwatson [15:42] gradier: yes, report it against the package in Ubuntu. Then, if it's an upstream bug we'll add a link to the upstream report [15:42]