[00:00] that's interesting, now why would gnome-screensaver be segfaulting on unlock when the disk is full... [00:01] hi [00:01] is it possible to get ubuntu working on my mac? [00:01] does ubuntu still have ppc support? [00:03] cathya: #ubuntu is for support, please [00:03] im there [00:03] and its a bloody spam [00:03] im in ubuntu power pc as well [00:03] it's pretty dead in there [00:03] I'm sorry to hear that, but this channel is for development of Ubuntu and developers need it to coordinate the alpha 5 release. It is not for support [00:04] tyo get your question noticed, i have to literally flood the channel else it's a bunhc of garb i keep getting responses from [00:04] i just need to know if it'll work on my mac [00:04] since i did hear some months ago that ubuntu stopped work on ppc [00:04] there is still a ppc port of Ubuntu, but I wouldn't be able to tell you whether or not it works on your mac's hardware completely [00:05] cathya, you asked the qn in ubuntu, someone immediately answered you with a two line answer and a link to the community port site. what more were you looking for? [00:06] ok jdong [00:06] thanks, that'll do [00:07] pkh: the two line was some community development as reference and some random user telling me bluntly NO [00:07] what you heard is that Ubuntu no longer offers ppc as an officially supported platform, though the community has continued to maintain it :) [00:07] while clearly it does have some form of support as jdong stated [00:07] ah ok [00:08] thanks [00:10] slangasek: it's taking a bit longer than expected. it's currently generating the LTSP chroot, then will compress it and finish the install [00:10] stgraber: ok; I'll still be here when you're done :) [00:35] slangasek: ok, installation completed. LTSP seems to work (I haven't tested with a client but nbd and tftp work) and I successfully installed edubuntu-desktop, inkscape, kalzium and kvoctrain from the Add-on CD [00:35] * slangasek pushes the plunger [00:36] I basically only saw one bug with this install and it's far from an critical one :) (bug 193902) [00:36] Launchpad bug 193902 in firefox-3.0 "[Hardy alpha5] Firefox launcher is broken (on the top menu)" [High,Confirmed] https://launchpad.net/bugs/193902 [00:36] probably the best alpha so far (at least for this computer) [00:38] cool === _stefan_ is now known as sistpoty [00:52] hello === slangasek changed the topic of #ubuntu-devel to: Archive: Feature freeze | Alpha 5 released | Development of Ubuntu (not support, not application development on Ubuntu) | #ubuntu for support and general discussion for dapper/edgy/feisty/gutsy, #ubuntu+1 for hardy | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs [00:52] okaratas: hi [00:52] slangasek, hi, how are you ? [00:52] well enough, and you? [00:52] i am fine, thanks. [00:52] i am a sleep, sorry :) [00:58] [reed], hello [00:58] <[reed]> "Alpha 5 includes several new features that are ready for large-scale testing. Please refer to http://www.ubuntu.com/testing/hardy/alpha5 for information on changes in Ubuntu" <-- except I get Access denied for that URL :) [00:58] <[reed]> hi, okaratas. [00:59] hmm [00:59] You are not authorized to access this page. [00:59] what is the ubuntu web site problem ? [00:59] [reed]: yes, the URL won't be live for another half hour or so; sorry, I ought to have held the mail until it was published [01:00] the ISOs themselves are available [01:42] are packages still accepted for universe for hardy? [01:44] ffm: if you can convince the motu-release team to grant an exception, yes (for new packages, that is) [01:45] pochu: we're on the front page of http://launchpad.net . [01:45] pochu: GASP. [01:47] never mind, we'll try with intrepid. [01:52] lamont: You said to remind you about requesting Postfix 2.5.1 sync. I'll take care of it. [02:02] lamont: Postfix 2.5.1-1 sync requested. [03:30] May I ask if we can introduce new packages in universe in hardy 8.04.1? [03:32] ffm: You've asked before. The same answer applies. Hardy is in feature-freeze, and it would need an approved exception. [03:32] (This is as true for 8.04 as for 8.04.1, although 8.04.1 needs much more justification for the exception) [03:33] persia: ah. Well, what I am working on is undergoing a major rewrite, so I'll submit it to ibex. [03:34] ffm: Thanks. The worry is that it will destabilise something. Once it gets into the Ibex, it can be backported to 8.04, so it could be available, but not in universe. [03:34] persia: can beta software be placed into universe? [03:34] persia: it is a _minor_ python package that won't really harm anything. [03:35] Yes, if considered of sufficient quality to be release-worthy. Something getting a major rewrite wouldn't be a good candidate. Also, the decisions aren't made on IRC (and I'm not one of the decision makers). You'd need a freeze exception. [03:36] persia: Ok. Thanks, === j_ack_ is now known as j_ack [04:15] ScottK2: rock on. thanks [04:15] * lamont messes with bind9 vs apparmor [04:26] autoheader: warning: missing template: CALL_PTHREAD_SETCONCURRENCY [04:26] * lamont hates auto* [04:34] autoheader: Use AC_DEFINE([HAS_PW_CLASS], [], [Description]) [04:34] anybody know what that actually means? === \sh is now known as \sh_away [04:44] Hello guys. :) [04:44] I am working on implementing stuff for Wine [04:45] I came across a page about things that Wine could do upstream to help you guys out [04:45] Let me see if I can find it again [04:55] https://wiki.ubuntu.com/BetterIntegratedWineSpec [04:55] ^^ In that page, it says you guys need some type of console configuration. [04:55] Would a re-implementation of the windows' 'reg' program be enough? [04:57] Something like: reg add 'hkcu\Wine\Direct3D' /v UseGLSL /d 'disabled' be enough? [04:57] (To disable GLSL and enable ARB shaders, for example) [05:05] jdstrand: was there a reason you re-autotool'ed bind9? [05:06] YokoZar, ping [05:06] Griswold: pong [05:06] YokoZar, Can you read the above and give me an answer? :) [05:08] Griswold: I think we discussed this before, yes? [05:08] YokoZar, Perhaps. I have been busy - can you give a quick summary just to job my memory? [05:08] *jog [05:08] Griswold: my only worry is that the interface to reg might change - or the registry itself. [05:09] The interface to 'reg' will never change once implemented [05:09] The interface to the registry itself might, but not reg [05:10] Griswold: Though, configuring GLSL is something we probably don't want to do (we're trying to cut down the interface, so accepting Wine's magic default should be best). Stuff that we'll keep needing to configure no matter how good Wine's defaults are would be stuff like mentioned in the spec - Windows version, whether apps contained in a window or separate (which is similar to managed/unmanaged/desktop) [05:10] YokoZar, Ok. :) [05:10] It was just an example though - quickest key I could think of that I know by heart [05:11] Yeah. Would your reg be able to do the uninstallation stuff? [05:11] I don't know. Is uninstallation stuff stored in the registry? [05:11] It should be yeah [05:11] Then yes, once implemented [05:11] Windows looks somewhere when you go to add/remove [05:12] So that's the other half of the puzzle, to spruce up gnome-app-install. [05:12] You will be able to query, add, delete, etc. registry keys [05:13] YokoZar, Ok. Are you able to write the code for Ubuntu once I get reg written? [05:13] reg will have a built-in help and you could ask me any questions you want about its interface [05:14] Griswold: Some of it. Gnome-app-install would be someone else's work. Adding a new applet for wine configuration I may be able to do. The trick is it's a bit too late to get that stuff in Gnome/Hardy. [05:14] Ahh, I see [05:14] Griswold: Anyway, thank you for taking up this feature request, it's very awesome of you and I'll help however I can. [05:14] Ok, awesome. :) [05:14] I did some talking in the past few days to see what is the best route for Wine [05:14] Griswold: It's quite plausible that it can still be done though, especially stuff that would be part of Wine (rather than part of Gnome) [05:15] Yeah [05:15] For instance Wine's configuration applet could be a part of Wine package. [05:15] So the uninstallation stuff would come later. [05:15] Hmm.. you could make a wine-ubuntu-config or something package [05:15] (I don't know the exact naming scheme, obviously) [05:17] Wouldn't really matter if it were a dependency. [05:18] Yeah. :) [05:41] lamont: You've got mail.... [05:44] * jdong locally backports mono 1.2.6 just to see what blows up :D [05:46] * ScottK still thinks of mono as the disease that wiped him out of an entire semester in college. [05:48] YokoZar, Hmm... Just thought up something else for you to think about [05:48] Some users expect a sort of GUI for Wine where you can browse for a .exe and run it, etc. [05:48] Maybe a little dialog box pop-up explaining how to use Wine might be useful. (When you install it for the first time) [05:48] ScottK: yeah... /usr/lib/sasl2 is (uh) wrong - it'll be nice of them to change it. [05:49] as for whether we should move from /etc/postfix/sasl to /etc/sasl, dunno.. [05:49] Well that part they don't seem to want to change [05:49] I'll worry about it when someone files a bug against postfix. :-) [05:49] lamont: It's a hard question. [05:50] If we did manage the move, it'd be one less Debian unique piece of config documentation to keep track of. [05:50] postfix grew the hooks and config directory specifically because the sasl package is wrong. [05:50] config files do not live in /usr [05:50] ever. [05:50] So if we can live in /etc/sasl2 are we happy? Is that somehow better? [05:50] Agreed. [05:50] I don't mind living in /etc/sasl2 [05:51] we just set the path to be $PATH:/etc/sasl2:/etc/postfix/sasl :) [05:51] then document the order of finding things [05:51] So something along the lines of sure, go for it, we might even move over there at some point. [05:51] yeah [05:51] that's my thinking, anyway [05:52] I just finished scripting maintainer scripts for a conffile move in one of my Debian packages, so I have some idea how much fun that is. [05:53] And if it breaks something we'll just get pitti to fix it anyway ... [05:53] ;-) [05:54] hehehe [05:55] yeah [05:55] pitti++ [05:56] ScottK: heh... actually, postfix doesn't actually deliver anything in /etc/postfix/sasl. :) [05:56] win! [06:00] Hmmm. Do I put smtpd.conf in there by hand each time? [06:00] I guess I must. [06:09] * Hobbsee waves [06:09] Heya Hobbsee [06:09] world blown up yet? [06:10] heya Hobbsee :) [06:10] Not so as I've noticed. [06:10] evening Hobbsee [06:11] heya lamont [06:11] I stormed off in a huff about 14 hours ago about ppaput claiming it's part of the Ubuntu sponsorship process (it's not). Came back and filed 10 bugs against ubuntu-dev-tools. [06:11] hey emgent [06:11] * Fujitsu waners in. [06:11] hah [06:11] * Fujitsu kicks his D key. [06:11] oh nice, someone's finally stepped up again about the LP real name policy [06:11] * ScottK2 thought it was Australian for something [06:12] Hobbsee: What's that? [06:12] i think our hardy heron looks a little sickly :) [06:13] ScottK: claiming _what_ was part of the sponsorship process? blowing up the world? or tickling Hobbsee ? [06:13] Some script that uses an LP PPA. [06:13] LOL [06:13] It's something it's author and I had discussed before and I thought had reached a clear understanding. [06:14] My favorite bug was noticing the the AUTHORS file for the package is executable. [06:14] it made less sense when I thought ppaput was an IRC ncik [06:14] Ah. [06:14] I'd be less annoyed about that [06:14] AUTHORS to be executed at daybreak. film at 11. [06:15] That's about right for some of the stuff in the package. Some of it's geniunely useful. [06:15] Unfortunately they're also improving some of the things to the point beyond utility [06:15] hah [06:16] heh [06:16] Stuff like improving requestsync to spawn into an editor, but then asking you if you want to edit the bug before they show you what's in it. [06:17] It's almost like they're trying to get hired as LP developers [06:17] ROTFL [06:17] just spawn the &^) editor, already [06:17] and _before_ the mail is signed, eh? [06:17] :-) [06:17] Yeah [06:18] There was another script in there that was a shebang and a copyright statement [06:18] heh [06:18] It appears the script was meant to do the same thing as dget -x withouth having to type the -x [06:18] ScottK2: the policy which *requires* all lp-beta users to have their real name set. [06:19] Ah. [06:19] apparently it makes them feel better, or something. [06:19] I get annoyed enough with the production quality LP. I can't imagine wanting to use it when it's less mature. [06:19] ScottK2: maybe it's just that they don't get to work on any other pacakges? [06:20] ScottK2: But using ege means you can see the braineadd features an complain about them before they're release. [06:20] Well they're all (I think) motu, so they've got several thousand choices handy. [06:20] An I hate my keyboar. [06:20] ScottK2: heh :) [06:20] ScottK2: at least you can scream faster, and htey tend to listen. [06:20] * lamont hands Fujitsu a 'd' key [06:21] lamont: Thanks. [06:21] ScottK2: lp-beta is love [06:21] Fujitsu: Sure. Then I file bugs and they tell me putting two little triangles in the UI fixes all the confusion. [06:21] I'll hopefully be able to get a new keyboar from Dell soon... [06:21] ScottK2: Correct. [06:21] there's also the trick of screaming about something and actually having the fix for a while _before_ it shows up in production [06:21] * Hobbsee hands Fujitsu another 'd' key, as the last one appears not to work [06:21] lamont: yeah, exactly [06:21] * jdong suggests Fujitsu map unused F12 key to d with xmodmap ;-) [06:21] * ScottK2 has been learning the email interface lately [06:21] I note the more braineadd features are those which we can't test on ege. [06:22] Like emailing, Soyuz... [06:22] heh [06:22] Any project that doesn't have a solid testbed is doomed [06:22] i'm not sure that soyuz is an accurate representation of the rest of the project's quality, though [06:22] The only exception is if you do a huge amount of up front engineering [06:23] ScottK2: It does have a good testbed, just not with users. [06:23] * Fujitsu has removed the mechanism from the d key. [06:23] Fujitsu: Ah, so it's a good internal test bed for developers? [06:23] there are certain issues that show up when a product is designed and built by people who never use it, other than in what _they_ believe is the normal use model [06:24] That's why edge is important. [06:24] An why specs shoul be public [06:24] lamont: this is where ScottK2's quote about the LP devs being very happy to show you how you should be using LP comes in, right? [06:25] lamont: But they all know exactly how it's going to be used and will be glad to tell us how we're doing it wrong. [06:25] * Hobbsee grins [06:25] ;-) [06:25] Hobbsee: yep [06:25] * lamont is reminded of a discussion on exactly how metacity keyboard focus should work [06:26] * ScottK2 suddenly remembers it's late and he has to wash his hair. [06:27] the most memorable comment from _that_ discussion was "Why do you even use gnome?" [06:27] Hahha. [06:27] * ScottK2 tends to wonder about that. [06:28] in the end, debian/patches/001_strict_focus.patch was born. [06:28] and then warty released a couple months later [06:28] * ScottK2 is also wondering about how long python-kde3 really takes to build. [06:29] ScottK2: 'kde' is in the name... figure a couple hours [06:29] minimum [06:29] Yeah, well. Probably [06:29] ScottK2: Why does it have it's own source package? [06:29] Fujitsu: I've no idea. I don't make this stuff up, I just try to fix it. [06:29] Isn't against KDE policy to have a source package that doesn't build 50 binaries? [06:29] Fujitsu: that's the python implementation of kde, dontcha know [06:30] or was it the kde implementation of python... I forget [06:30] Fujitsu: Probably, but that's less interesting the sylpheed-claws/claws-mail that seems to have a strict policy against have two releases with the same number of source packages. [06:30] Haha. [06:31] KDE python bindings. [06:31] Not kidding [06:31] We lost claws-mail-clamav in the last release. [06:32] Ironically due to their concerns about freeness of clamav unrar code that Debian removes [06:33] * lamont -> bed [06:33] Night lamont. [06:36] Fujitsu: Any idea what the [NEW] bit in bug mail is supposed to signify? [06:37] ScottK2: That it's the initial email for a bug. [06:37] Appeared with 1.2.1, IIRC. [06:38] Right. [06:38] I guess I don't get it. [06:38] I thought it was "Hey. This is a new bug." [06:38] It is. [06:39] Or it might be `Hey. This is a new bug task." [06:39] No. It's "Hey. This is the first time I've spammed you about this bug." [06:39] I'm not sure. [06:39] Bug may or may not be new. [06:39] I just assigned myself a 5 month old bug and it came in as [NEW] [06:39] You in't create a new task? [06:40] Gaah. [06:40] I've only seen it when the bug is new or the bug is newly non-private, or the bug has a new task, or the bug is against a new package/project/milestone, or the bug newness was unintentionally reset. [06:41] ScottK: For that, you got the NEW warning because the bugmail you received was the top part. Just add a comment when assigning to avoid it (and make the bug less new) [06:41] No. [06:41] Just assigned the bug [06:41] That woul be YALPB. [06:41] There were other comments in the bug? that's a NLPB for me. [06:42] I woul presume that [NEW] woul indicate newness. [06:42] Not newly-notifiedness. [06:42] Acutally I did include a comment [06:42] And there were other comments [06:43] It's Bug 144490 [06:43] Launchpad bug 144490 in python-kde3 "autopkgtest gutsy python-kde3: erroneous package!" [High,New] https://launchpad.net/bugs/144490 [06:43] Fujitsu: In my experience, it comes from the bug being "New", which doesn't mean recent. [06:43] Status is New. [06:43] I'm not sure why that needs bold blinky subject lines [06:43] Status oughtn't define newness for bug notification. That's a bug. [06:44] persia: I have no replies that are marked [NEW], other than those that are done through the email interface, so it's not marke by Status. [06:47] * ScottK2 has already filed his LP bug for the day. [06:47] * ScottK2 looks around for an LP developer... [06:48] !weekend [06:48] It's a weekend. Often on weekends, the paid developers, and a lot of the community, may not be around to answer your question. Please be patient, wait longer than you normally would, or try again during the working week. [06:49] its also like midnight or later in the us / euroland [06:49] though maybe germany's close to wake up time ;) [06:49] does keybuk hit irc much anymore? [06:55] Nevermind. I'll file the bug. It's even more annoying than I thought. [06:55] I get a copy of the entire bug marked new and then another mail with my comment. [06:55] That's what I'd expect, except without the [NEW] bit. [06:56] I don't need a copy of the ficking bug in my inbox. I already read it before I assigned it to myself. [06:56] Good morning [06:57] ScottK: That behaviour is a workaround for the previous issue that subscribing people after leaving a comment didn't send them an email notification (as I understand it) [06:58] persia: Not my problem. It's a bogus design [06:59] Sure, just sharing my impression of history hoping it might cause your use case to be better written to avoid being rejected out of hand. [06:59] Thanks. [07:17] I filed the bug. I managed to mostly contain my sarcasm. [07:19] Have a good night/day as your circumstances and timezone permit. [07:19] Good night ScottK [07:20] Good night persia [07:20] Night ScottK2. === Caesar_ is now known as Caesar [07:46] http://lists.gnu.org/archive/html/emacs-devel/2008-02/msg02140.html what! [07:48] Heh [07:49] Yeah, he switched to Vim. [07:49] finally took to his senses, huh! [07:49] I guess this is one of those "where were you when ..." things === hunger_t is now known as hunger [10:16] who is (coming to|at) FOSDEM? :) [12:10] https://bugs.edge.launchpad.net/ubuntu/+bug/190677 --> in this bug report, what does LUM stand for? [12:10] Launchpad bug 190677 in linux-ubuntu-modules-2.6.24 "Backport acer-wmi to hardy 2.6.24 kernel" [Low,Fix committed] [12:10] rohan: linux-ubuntu-modules [12:11] rohan: Also, #ubuntu-bugs is generally the best place to ask about bugs. [12:11] persia: i'm sorry! === cprov is now known as cprov-out === afflux_ is now known as afflux [13:15] pitti: could you have a look at bug 193533? It looks like the var/run/PolicyKit stuff in policykit's postinst script should be handled in policykit.init as var/run/PolicyKit is created first in the init script [13:15] Launchpad bug 193533 in policykit "mkdir /var/run/PolicyKit" [Low,Confirmed] https://launchpad.net/bugs/193533 === asac_ is now known as asac === vorian_ is now known as vorian [14:59] ScottK: hello, are you available ? [15:29] jeromeg: I'm here [15:30] ScottK2: what did you decied for the brasero backport ? [15:31] I didn't yet (I agreed about backporters for the maintainer) [15:31] * ScottK2 looks for the bug. [15:33] ScottK2: ok, I think this is really an important backport [15:34] unofficial repos are being created in a lot of places [15:34] OK. What's the impact of the dropped dependencies? [15:34] ScottK2: none [15:35] it just removes a feature that is not in gutsy [15:35] (it was added for hardy) [15:36] K [15:36] ScottK2: i'm also working on a backport for pidgin [15:36] which has even more unofficial buggy packages [15:36] jeromeg: I'm unlikely to touch that one without a lot of backing from jdong. [15:37] ScottK2: yep, yep I know it's a tough thing, that's why I set up a ppa to have some feedback [15:37] i'm testing all plugins at the moment, quite boring :) [15:38] Fair enough [15:43] jeromeg: Where do I find usr/share/gnome-pkg-tools/1/rules/uploaders.mk? [15:43] ScottK2: why do you need this ? [15:44] Because the source package won't build for me for the lack of it. [15:44] weird [15:44] in Gutsy ? [15:44] Yes [15:44] I'll have a look [15:45] you have gnome-pkg-tools installed right ? [15:46] No. [15:46] * ScottK2 neither uses nor develops for Gnome. [15:47] ScottK2: this is during build or during debuild ? [15:47] Building the source backage. That's probably what I need. [15:47] Yep. That was it. [15:47] yep you need to install gnome-pkg-tools [15:47] great [15:55] ScottK2: works ? [15:58] jeromeg: Your patch applied, the source package built and I'm doing a test build now. [15:58] ScottK2: thank you very much [16:07] jeromeg: For the future, use gutsy-backports as the target in debian/changelog, not gutsy. [16:07] ScottK2: oh yep, sorry for that [16:09] jeromeg: Uploaded. [16:10] ScottK2: great ! [16:10] thank you so much ! [16:10] Now we need to wait for an archive admin to publish it. [16:10] ok [16:10] ScottK2: the pidgin backport seems to work pretty well [16:10] only one plugin remaining to test [16:11] took me 1h and a half... [16:11] jeromeg: Convince jdong first. [16:11] ScottK2: yep :) [16:11] jeromeg: You should have gotten a waiting for approval mail on brasero (I think) [16:12] ScottK2: not yet [16:17] jeromeg: Maybe just the uploader gets that one. I'm not sure. I got it, so it's confirmed the upload made it. [16:18] thank you very much [16:51] is JFS supported? [16:52] Supported in what way? [16:53] I don't believe you can install to JFS with the standard installer, but the alternate will do it. The kernel certainly has support. [16:53] get bugfixes and all that in ubuntu [16:53] It's in the kernel, so yes [16:53] ok === afflux_ is now known as afflux === dmb__ is now known as dmb [20:02] Could somebody tell me which is the difference between MOTU and Ubuntu Developer, please? [20:03] Ubuntu Developer includes core developers [20:03] Ubuntu Developer := ( MOTU + Ubuntu Core Developer ) [20:05] Keybuk: thanks, but on Launchpad I see that MOTU is a member of ubuntu-dev [20:06] exactly [20:06] that isn't inconsistent with what I said :-) [20:06] oh, yeah [20:06] I read too quickly, sorry :D [20:07] thanks [21:34] har, no one commented on the fact that my feature freeze announcement linked to the gutsy list of blueprints [21:40] slangasek: everyone's already running intrepid ;) [21:41] ah, good. :) [21:46] btw, are we running intrepid or ibex? [21:47] Kopfgeldjaeger: we use the adjective [21:49] yeah, i know... but intrepid.. OK [21:49] it's a secret plot to get everyone to just call it "8.10" [21:50] does 'intrepid' sound strange to native speakers as well? [21:56] Keybuk: "it's a secret plot . . ." hehe [21:57] siretart: I think it's slightly less strange than the rest of the adjectives that have been use. [21:59] siretart: no, why should it sound strange? [22:53] siretart: it's better than hoary [23:57] n8