| [02:48] <candrews> Can someone help me complete this packaging process for geoclue? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505255 | |
| [02:48] <ubottu> Debian bug 505255 in wnpp "[needs-packaging] geoclue" [Wishlist,Open] | |
| [02:49] <candrews> https://bugs.launchpad.net/ubuntu/+bug/260977 | |
| [02:49] <ubottu> Launchpad bug 260977 in ubuntu "[needs-packaging] GeoClue - GIS Geospatial Information Service and API using D-Bus" [Wishlist,Confirmed] | |
| [05:51] * Hobbsee wonders at the general mess of https://bugs.edge.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746 | |
| [05:51] <ubottu> Launchpad bug 88746 in linux "ehci_hcd module causes I/O errors in USB 2.0 devices" [High,Confirmed] | |
| [07:10] <slangasek> superm1: looks like BuildLiveCD in livecd-rootfs still treats 'mythbuntu' as a bad project name | |
| [07:11] <superm1> slangasek, did you update livecd-rootfs? | |
| [07:11] <superm1> (0.74 is the newest) | |
| [07:12] <slangasek> I'm looking at current bzr, if that's what you mean | |
| [07:12] <slangasek> grep for 'bad project' | |
| [07:12] <superm1> current bzr should be able to do it, i updated bzr when i uploaded the latest too | |
| [07:17] <superm1> slangasek, oh i believe i see what you mean. i didn't realize BuildLiveCD was actually used- i thought it were just an example | |
| [07:19] <slangasek> it's an example for any other users of the package; for us, it's what infinity merges onto the buildds :) | |
| [07:19] <superm1> ah :) | |
| [07:22] <superm1> slangasek, i'd think just changing that *ubuntu to *buntu would take care of it then. do you want me to make the change or will you take care of it? | |
| [07:24] <slangasek> I was suggesting that you might want to do it, but I could do it | |
| [07:24] <slangasek> I'm not sure we want to relax it so far as *buntu though, maybe just add mythbuntu to the list? | |
| [07:26] <superm1> sure that seems fine to me | |
| [07:29] <slangasek> ok, committed | |
| [07:33] <superm1> cool thanks | |
| === gouki_ is now known as gouki | |
| [09:33] <alexander> I need help with SWIG, which works under ubuntu 7.04, and partially doesn't work with ubuntu 8.10. | |
| [09:33] <alexander> For example, wrapping an interface including "#include <climits>" give the error "test.h:3:22: error: climits: No such file or directory" in 8.10, while in 7.04 climits is found in the standard header directories. | |
| [09:33] <alexander> Of course I can fix this with a -I flag to SWIG, but there are more subtle problems indicating that SWIG uses different compiler settings than g++ in 8.10, although it worked in 7.04 without changes. | |
| [09:33] <alexander> Any ideas howto properly setup SWIG in 8.10, or suggestions for a better channel to ask in? | |
| [09:38] <Treenaks> alexander: what's SWIG (other than a google-polluting website), and I think it's better to ask in #ubuntu -- climits does exist if you use a C++ compiler and have libstdc++{version}-dev installed | |
| [09:39] <Treenaks> oh wait, the polluter is SWIK | |
| [09:41] <alexander> Treenaks: see swig.org It is an interface/wrapper generator | |
| [09:43] <alexander> climits is installed and works fine with g++. But SWIG must be configured differently in 8.10 than in 7.04, as it worked out of the box in 7.04, and now I have to give a lot of options and still can't solve a few problems. | |
| === tkamppeter__ is now known as tkamppeter | |
| [15:07] <asac> james_w: http://paste.ubuntu.com/72901/ ... want a bug? | |
| [15:09] <asac> james_w: ok. thats bug 174539 ? | |
| [15:09] <ubottu> Launchpad bug 174539 in bzr "export doesn't handle files going missing from working tree" [Low,Confirmed] https://launchpad.net/bugs/174539 | |
| [15:10] <tockitj> it would be nice for ubuntu to have some system wide detailed documentation :p | |
| [15:10] <tockitj> (both from user aspect and developers) | |
| [15:10] <persia> !docs | |
| [15:10] <asac> tockitj: what documentation would a developer want that isnt available right now? | |
| [15:10] <ubottu> documentation is to be found at http://help.ubuntu.com and http://wiki.ubuntu.com - General linux documentation: http://www.tldp.org - http://rute.2038bug.com | |
| [15:11] <persia> asac, Actually, I've a fair list of stuff in that category :) It's a slow process. | |
| [15:12] <persia> tockitj, Both are intended to exist at the links referenced. If those aren't complete, help is appreciated to address that. #ubuntu-docs is probably the right forum for such discussions. | |
| [15:12] <tockitj> i just think good docs would help greatly | |
| [15:13] <asac> persia: developer == packager? | |
| [15:13] <tockitj> i read tldp for greater part :p | |
| [15:13] <asac> aka ubuntu developer? | |
| [15:14] <persia> asac, developer == maintainer / ubuntu developer | |
| [15:14] <persia> tockitj, Most would agree, but it needs eyes and hands. Help is appreciated. | |
| [15:15] <tockitj> persia, i know :/ | |
| [15:15] <persia> asac, We've lots of docs, but it's not entirely well organised. Much of the interesting bits are buried in IRC log transcripts and examples. There's lots of places where two different pages say slightly different things that can be interpreted to contradict. | |
| [15:16] <tockitj> but 90% of my free time is allready dedicated to various comercial projects.. i dont see space there for software freedom fighting | |
| [15:16] <persia> asac, Anyway, most of the answers end up coming on on IRC, but ideally we'd have the answers all in the wiki. | |
| [15:16] <asac> persia: yeah | |
| [15:16] <asac> persia: i think wiki is a problem here | |
| [15:16] <asac> hard to keep up to date | |
| [15:16] <asac> and also hard to keep branches (e.g. gutsy, hardy, intrepid) | |
| [15:16] <persia> tockitj, Well, it's what you have time to do. The log of this conversation won't add much to docs though. | |
| [15:17] <tockitj> true :-) | |
| [15:17] <asac> what we would need is a documentation package with all the documentation and maybe a doc reader app | |
| [15:17] <tockitj> thanks for info, cu | |
| [15:17] <asac> so for each and every release, we can go through the complete documentation and remove rotting things | |
| [15:18] <persia> asac, That too. There's a cleanup effort around UDS every cycle, but sometimes useful stuff gets dropped (e.g. we still have patches from the Ubuntu X transition in Hardy/Breezy that haven't been uploaded again, but we no longer have the page explaining the point of the transition, which confuses some mergers). | |
| [15:18] <persia> (or at least there was during the Edgy, Feisty, Gutsy, Hardy, and Intrepid cycles, but that's mostly because the wiki didn7t get too messy until later Dapper) | |
| [15:18] <asac> persia: no clue about developer documentation. i just know that i never find anything in wiki ;) | |
| [15:19] <asac> persia: what i know though is that the user documentation for networking is kind of a mess ... and i just learned about that right before release | |
| [15:21] <persia> asac, Yeah. help.ubuntu.com needs a deep sweep. It's probably worth organising someting where a couple developers for each area work with the docteam to help get that area correct for Jaunty. | |
| [15:22] <asac> persia: hmm. Not really convinced. we need something to keep branches. afaik that isnt possible on help.ubuntu.com. | |
| [15:23] <asac> but yeah. we need dedicated resources for user doc | |
| [15:23] <asac> at least temporarily dedicated ;) | |
| [15:24] <persia> We have those. The docteam. It's just that as we've grown, the teams don't collaborate as much, so there's a bit of a disconnect between ubuntu-dev and docteam. docteam ends up playing catch-up. | |
| [15:24] <persia> Just having each dev spend three-four days reviewing and discussing issues with areas they know well with the docteam would be a *huge* benefit. | |
| [15:25] <persia> I don't think we need more than that really. | |
| [15:25] <persia> If it's repeated every cycle, we ought have first-class documentation again. | |
| === sepheebear is now known as Sepheebear | |
| === thegodfa1her is now known as fabbione | |
| [16:42] <mysteryc> Hi. | |
| [16:43] <mysteryc> Since last year you people developed a newer version of Xorg and since I downloaded it through the update manager, my screen is always messed up. Not it's totally messed up as it only has option for 800 x 600 resolution! :/ | |
| [16:45] <Treenaks> have you asked on #ubuntu ? | |
| [16:46] <mysteryc> Yes, Ive been askin for the past month, from the day that I booted and my screen was somehow set at 800x600 :s | |
| [16:46] <mysteryc> And it's still not fixed. | |
| [16:47] <mysteryc> And I had to get back on windows again cause it's SO annoying, and windows is all laggy and not responding and stuff cause I can't fix the resolution. | |
| [18:10] <jardi> hi all | |
| [18:13] <jardi> I have made some change to the guest session scripts in order ton make it use the /etc/skel dirrectory to create the new temp home folder | |
| [18:14] <jardi> I wanted to submit it to you guys and made a bug report with my patch | |
| [18:14] <jardi> but I have not received any response in a week, am I doing it wrong ? | |
| [18:16] <jardi> here is the link to this bug report : https://bugs.launchpad.net/ubuntu/+source/gdm-guest-session/+bug/296993 | |
| [18:16] <ubottu> Launchpad bug 296993 in gdm-guest-session "guest session doesn't use files in /etc/skel to create new user's home" [Undecided,Fix committed] | |
| [18:21] <jdong> jardi: no you aren't doing anything wrong; just Martin Pitt is a really busy guy :) | |
| [18:21] <jdong> jardi: it'll get looked at eventually. Did you set the bug to fix committed? | |
| [18:22] <jdong> (I wouldn't recommend doing this -- fix committed is for when the fix is actually put into Martin's bzr branch and pending upload) | |
| [18:27] <mophiax> Excuse, but when are there going to be the blueprints for 9.04? | |
| [18:40] <jardi> thanks jdong, I did but the bug status to fix commited, what state do you suggest, there is no state "fix proposed" | |
| [18:41] <jdong> jardi: Confirmed is probably the best status right now to put it as, or Triaged | |
| [18:43] <cjwatson> don't worry about the status, we track patches separately | |
| [18:53] <jardi> thanks all | |
| [20:04] <martikka> Would anyone know the current status of defoma? Is it still planned to be used in font (ttf) packaging? | |
| [20:05] <martikka> or is the "defoma-hints truetype" going to be fixed at some point? | |
| === geser_ is now known as geser | |
| [21:14] <dethklok> hi | |
| [21:15] <dethklok> I need help with my ubuntu install. | |
| [21:16] <dethklok> I am trying to run and assembly some assembly code but it won't work it needs the i386 | |
| [21:17] <dethklok> is there a way to emulate and run in 32bit mode on a 64 bit installation or do I need to reinstall 32 bit ubuntu? | |
| [21:26] <cjwatson> dethklok: sorry, this channel is for developing Ubuntu itself, not for offering help for people developing on Ubuntu. As a starting point, gcc -m32 is probably the kind of thing you're looking for, but please don't ask about it further here | |
| [22:02] <maco> Can anybody tell me what version of libusb will be in Jaunty? Version 0.9 is a requirement for some fairly common fingerprint readers' drivers, but it's not in sid yet, so... | |
| [22:04] <maco> bug 163156 is open on one of those fingerprint readers | |
| [22:04] <ubottu> Launchpad bug 163156 in linux-source-2.6.22 "UPEK TouchStrip 147e:2016 not supported at all" [Undecided,Won't fix] https://launchpad.net/bugs/163156 | |
| [22:06] <maco> uh, it's also on "linux" as "triaged"...ubottu just only showed the gutsy one | |
| [22:08] <maco> for clarity, libusb-1.0 is the official requirement, but 0.9 is what they called 1.0 beta, and it includes the hooks the driver needs | |
| [22:10] <maco> doh, im sorry, ignore me. i didnt realize there's a package name change when this occurs, so there's a libusb-1.0 package in jaunty already and i can go away and stop annoying you all | |
| === gouki_ is now known as gouki | |
| === RAOF_ is now known as RAOF__ | |
| === RAOF__ is now known as RAOF_298 | |
| [23:58] <andrews> I have an idea to start or help with a project to make partition clone software run in an easy to use gnome interface. I am new to developing and would need lots of help. Does anyone here now where I could start. | |