[01:14] <ogra> james_w, you if you would upload a fix for bug 269150, i can approve a new upstream (i'm release manager for ubuntu-mobile, netbook-launcher is pat of the seeds)
[01:15] <ogra> so new upstram would be appreciated :)
[01:15] <james_w> ogra: cool, thanks. I'll ask Neil what he would like to do.
[01:16] <ogra> i was planning to do that anyway ... i'll just add the FFe approval to the bug, if you dont come around to do it i'll do it next week before thursday
[01:16] <james_w> ogra: I tested your ubuntu-mobile image yesterday, it works nicely. I didn't test the installer though.
[01:17] <ogra> cool, thanks for that :)
[01:17] <ogra> wlan did work fine ?
[01:17] <james_w> um, probably not actually
[01:17] <james_w> I've forgotten actually.
[01:17] <james_w> I'll test again tomorrow
[01:18] <ogra> heh
[01:18] <ogra> ok
[01:28] <danbh_intrepid> is anyone aware of problems with the rarian-compat package?
[02:49] <andresmujica> hi motus!, one question where can i find the buildlog for a specific package?
[02:49] <StevenK> On Launchpad
[02:49] <andresmujica> ~builds ?
[02:49] <StevenK> On https://launchpad.net/ubuntu/+source/libtunepimp/0.5.3-7ubuntu2 ; there's links for the different arches
[02:50] <StevenK> For example
[02:50] <andresmujica> ok that's what i needed
[02:50] <andresmujica> thks
[05:38] <stefanlsd> Is there a place to view package history - im trying to find a package that may of been removed
[05:38] <StevenK> In Launchpad
[05:39] <StevenK> http://launchpad.net/ubuntu/+source/<source package>
[05:42] <stefanlsd> StevenK: thanks. LP doesnt know about it.   im looking for   libcgi-pm-perl
[05:43] <StevenK> Then that isn't the source package name
[05:44] <Flannel> I don't think thats the binary package name either.
[05:44] <persia> stefanlsd, If you know the binary appeared in an older release, try generating an apt-cache for the older release, and then running apt-cache showsrc libcgi-pm-perl against it.
[05:45] <persia> stefanlsd, Or, if you want to use a pregenerated apt-cache, use rmadison -S libcgi-pm-perl
[05:45] <persia> (and I'm tempted to agree with Flannel)
[05:47] <danbh_intrepid> stefanlsd: maybe libcgi-perl ?
[05:50] <stefanlsd> danbh_intrepid: thanks. that is probaly it. will install that and see if it gives me CGI.pm
[05:50] <stefanlsd> #  Removal requested  on 2008-06-20. - # Deleted on 2008-06-20 by Martin Pitt - (From Debian) ROM; obsolete; superseded years ago by libcgi-pm-perl
[05:51] <stefanlsd> mmm. seems like libcgi-pm-perl never made it in thou. will have to file a sync request.
[05:52] <stefanlsd> how do i search depends again and look for packages currently in the archive depending on libcgi-pm-perl.  I know bugzilla3 is one, thats how i found this (it doesnt build anymore)
[05:56] <StevenK> stefanlsd: http://paste.ubuntu.com/56890/
[05:57] <StevenK> If they depend on perl-modules | libcgi-pm-perl, they're fine
[05:58] <stefanlsd> StevenK: thanks. mm. not that many.  The main problem is that CGI.pm shipped with perl-modules is 3.29, while some applications require later. Like bugzilla needs 3.33, which debian says the user should install libcgi-pm-perl which repplaces CGI.pm. Do you think it becomes a candidate for a sync?
[06:00] <StevenK> Hmmm.
[06:00] <StevenK> % rmadison -u debian -s unstable libcgi-pm-perl
[06:00] <StevenK> libcgi-pm-perl |     3.42-1 |      unstable | source, all
[06:02] <stefanlsd> http://www.mail-archive.com/debian-bugs-closed@lists.debian.org/msg196892.html  - debian saying to use the seperate package.
[06:07] <persia> stefanlsd, Indeed.  The issue is that libcgi-perl was removed in favour of libcgi-pm-perl, but libcgi-pm-perl wasn't imported.
[06:08] <StevenK> I'll talk to pitti about it when he surfaces
[06:08] <StevenK> stefanlsd: Unfortunately, this will only fix it in intrepid
[06:09] <stefanlsd> persia: yeah. the question is, is it necessary, as perl-modules should provide it now. (which it does) - just an older version than what bugzilla3 expects
[06:09] <stefanlsd> StevenK:  bugzilla3 is only in intrepid
[06:09] <StevenK> Ah, then we are fine
[06:10] <persia> stefanlsd, I'll say "sometimes".  There are actually a number of the things in perl-modules lurking about, some more updated than others.  There's been not a small amount of discussion about this over the years, and much disagreement about how the maintainer of perl-modules should be doing things.
[06:10] <StevenK> perl-modules is still bod?
[06:11] <StevenK> Indeed.
[06:12] <stefanlsd> my feeling is we should sync it if possible. to say inline with debian, and any other packages now, and in the future that depend on CGI.pm > 3.29
[06:15] <persia> StevenK, won't it always be?
[06:21] <stefanlsd> StevenK: from the list of Depends - it looks like just bugzilla3 which needs a newer version. Gnatsweb needs CGI.pm >= 2.56.
[06:46] <dholbach> good morning
[06:51] <iulian> Good morning.
[06:52] <dholbach> hiya iulian
[06:52] <iulian> Hey Daniel.
[07:07] <highvoltage> morning iulian and dholbach
[07:08] <dholbach> hiya highvoltage
[07:08] <iulian> Hello highvoltage.
[07:10] <Burgundavia> 'ello highvoltage, dholbach
[07:10] <dholbach> hi Burgundavia
[07:10] <highvoltage> hey Burgundavia
[07:11] <highvoltage> shew, it's hot this morning.
[07:27] <jsgotangco> wow retro motu
[07:27] <jsgotangco> heh
[07:37] <highvoltage> jsgotangco: retro-motu?
[07:38] <ajmitch> highvoltage: I think he means 'old people'
[07:39] <Burgundavia> ajmitch: speak for yourself
[07:39] <highvoltage> ah :)
[07:39] <ajmitch> Burgundavia: I am
[07:39] <highvoltage> I thought someone walked into the channel with 80's day-glo clothes and a boombox and I missed it.
[07:40] <ajmitch> "can't touch this"
[07:42] <jsgotangco> you get a prize!
[08:22] <stefanlsd> StevenK: sync of libcgi-pm-perl actioned
[08:23] <StevenK> stefanlsd: I've already sync'd it
[08:23] <StevenK> stefanlsd: http://launchpad.net/ubuntu/+source/libcgi-pm-perl/3.42-1
[08:24] <stefanlsd> StevenK: thanks. thats great.  Was there any arguments against the sync of it?
[08:24] <StevenK> stefanlsd: Nope
[08:56] <stefanlsd> StevenK: how long does it normally take before the mirrors get the updates?
[09:04] <didrocks> morning everyone
[09:05] <stefanlsd> hihi
[09:09] <Laney> james_w: I submitted that debdiff from the library at uni :(
[09:23] <stefanlsd> Out of interest, why doesnt ubuntu use the debian maintainer way of working. adopting and orphaning packages?
[09:24] <persia> stefanlsd, It's a philosophical difference.  Essentially, Ubuntu is about teamwork and collaboration, and so it was decided not to have maintainers to avoid maintainer-lock.
[09:26] <persia> If you look at the changelogs in Ubuntu, you'll see a lot of variation in uploaders.  This is because people are working on various things, which often touch several packages.
[09:26] <persia> It's considered easier when e.g. updating a library, to be able to rebuild the rdepends directly, perhaps with API changes, rather than having to speak to each maintainer separately about that.
[09:27] <stefanlsd> persia: mm. yeah. that makes sense
[09:27] <stefanlsd> and i guess if you speak to the last uploaded, you are speaking to a 'maintainer'
[09:28] <persia> Sometimes.  Depends on the reason for the last upload.  Personally, I'm very much not a fan of the "contact last uploader" rule : I think it's better to contact known interested parties.
[09:28] <stefanlsd> although, sometimes it feels like there are too many packages to motu to know about and keep tabs on
[09:28] <persia> Often I'll upload things for a library transition or to add a .desktop file or to fix a trivial FTBFS.  That doesn't mean I have any understanding of the package, and I get confused when someone asks me about it several months later.
[09:29] <stefanlsd> persia: yeah. how do you find interested parties though?  i guess an LP team would be one way
[09:29] <persia> On the other hand, there are several packages I watch, and although I may rarely if ever upload them, I'm certainly able to comment about them, or provide suggestions.
[09:30] <stefanlsd> i quiet like the debian way though, with one person with an interest in a package completely dedicated to maintaining it, using it, watching mailing lists etc
[09:30] <persia> Generally I start by asking here.  If nobody seems interested, and I still have a question, I'll look around for likely groups.  If I don't find one, I'll send email asking about it to ubuntu-motu@.  If there is no response, then I presume I'm the only interested person, and will either make my best guess, or work closely with Debian.
[09:31] <persia> The changelog can be a hint, but depending on the specific changes, it may not be a good guideline of interest.
[09:32] <persia> Where there is a clear specific maintainer for a package, this is usually obvious by a long string of updates in the changelog, and that would be the person to contact, but this is maintenance by activity, rather than by documentation.
[09:33] <persia> So, in summary, if you know you're doing the right thing, just do it.  If you're not sure, ask here, ask people who have worked with the package (either in Ubuntu or Debian), etc.  If nobody can point you anywhere, you become the expert.
[09:34] <persia> stefanlsd, Yeah, there's a lot of value to that model also.  Without Debian using the Debian way, Ubuntu couldn't exist.  That said, there's a lot of teams in Debian also, where the work is often similar to Ubuntu.
[09:36] <stefanlsd> persia: yeah. ok. thanks :)
[09:54] <Koon> asac: about the -vpnc and -pptp updates, I can provide new snapshots and tests that they compile, but cannot really check that they are working / not regressing.
[09:54] <Koon> asac: also do you want them all at the 20081008 level ? -vpnc had no change between 0928 and 1008...
[09:55] <asac> Koon: well. thats ok
[09:55] <asac> Koon: i want all to be on the same date yes.
[09:55] <asac> Koon: otherwise it might get confusing
[09:56] <Koon> asac: I understand
[09:56] <asac> Koon: if you are sure they havent changed ... then well. :)
[09:56] <asac> if ther eis no interdiff then there wont be regressions at least ;)
[09:57] <Koon> asac: I'll provide all of them on chinstrap with the 1008 dates, you'll pick the one you prefer :)
[09:57] <asac> Koon: no need for chinstap
[09:57] <asac> Koon: chinstrap == private ,) ... either put them on people.ubuntu.com or just to the bug
[09:57] <Koon> asac: I'll attach them on the bug then, they are not that big.
[09:57] <asac> Koon: i will sponsor all in the row
[09:57] <asac> yeah
[09:57] <asac> cool
[09:57] <asac> thanks
[10:37] <Koon> asac: done
[10:38] <asac> Koon: whats the bug?
[10:38] <Koon> all in bug 275608
[10:38] <asac> thx
[10:39] <asac> Koon: so how did you produce the origs?
[10:39] <asac> just apt-get source network-manager (latest) and then tarring up the vpn-daemons dirs?
[10:39] <Koon> asac: from a svn checkout
[10:39] <Koon> at the revision used for 1008-224240
[10:40] <Koon> (which should give the same results)
[10:41] <Koon> asac: I'll be right back, I've to try switching cpu fans to kill the noise
[10:42] <asac> Kopfgeldjaeger: why didnt you use the tarball?
[10:42] <asac> or bzr?
[10:42] <asac> Kopfgeldjaeger: oops ignor ;)
[10:45] <freeflying> hi guys, gnome.asia conf will be held in beijing this weekend, if anyone would be there can drop me a mail more details: http://www.gnome.asia
[10:56] <Koon> asac: just received build failure notifications for n-m-openvpn on... hardy (?!)
[10:57] <asac_> Koon: ppa i guess
[10:57] <Koon> asac: ah yes
[10:57] <asac_> [PPA network-manager] [ubuntu/hardy] network-manager-openvpn
[10:57] <asac_> Koon: ppa is busted in hardy since a few days :(
[10:57] <asac_> somehow NM stopped to be able to install its build-depends
[10:57] <asac_> namely: intltool
[10:58] <asac_> (cannot be installed!!!)
[10:58] <Koon> beh
[10:58] <asac_> but maybe i am just blind ;)
[10:58] <asac_> Koon: uploaded everything now
[10:58] <asac_> Koon: next time please attach the .dsc
[10:59] <Koon> asac: ok
[10:59] <asac_> Koon: http://launchpadlibrarian.net/18452672/buildlog_ubuntu-hardy-amd64.network-manager_0.7~~svn20081008t224042-0ubuntu2~nm1~hardy1_FAILEDTOBUILD.txt.gz
[10:59] <asac_> Koon: if you see any reason why that shouldnt work let me know ;)
[10:59] <asac_> but i guess its a soyuz issue
[11:00] <glatzor> dholbach, james_w, hello the ffe of packagekit from 9/30 has not yet been replied.
[11:00] <glatzor> what can I do?
[11:00] <james_w> hey glatzor
[11:04] <dholbach> glatzor: ping somebody of https://launchpad.net/~motu-release/+members :)
[11:04] <glatzor> morning mvo!
[11:04] <dholbach> glatzor: mvo is not here :)
[11:04]  * dholbach hugs glatzor
[11:05] <glatzor> morning james_w and dholbach :)
[11:09] <glatzor> bye guys!
[12:49] <white> anyone here using openswan?
[12:49] <StevenK> Used to
[12:50] <white> StevenK: maybe you can clarify something for me
[12:51] <white> the scripts under /usr/lib/ipsec/, /usr/lib/ipsec/livetest in particular, when are they used?
[12:51] <StevenK> No idea about that, sorry
[12:51] <white> i'll keep looking :)
[13:35] <james_w> anybody want to take a look at fatsort? Apparently syncing the latest from Debian would be a good idea. I'd like to find out if there are any new features.
[14:02] <AnAnt> persia: sl-modem ?
[14:03] <persia> AnAnt, Just to make sure, you know that me playing with it will have absolutely no effect on it getting into Debian, and is unlikely to help it getting into intrepid, right?
[14:03] <AnAnt> persia: yeah, but I wanted an opinion
[14:04] <AnAnt> persia: probably you can give hints about adding dkms support to it
[14:04] <persia> I will, but based on what you've said, I suspect it works wonderfully :)
[14:05] <persia> I really don't know anything about dkms, except that it's supposed to compile modules locally on installation.
[14:05] <james_w> this is bug 269855?
[14:06] <persia> james_w, No, it's a complete repackaging to fix most of the outstanding issues with ls-modem.  Includes *lots* of patches.
[14:07] <persia> New upstream version, amd64 support, additional device support, proper ALSA integration, etc.
[14:07] <crimsun> james_w: that approach is fine with me (and sorry about not checking Debian; it was 0100 ;-), but I went the safe route
[14:08] <slytherin> AnAnt: you should talk with superm1 about dkms. And by the way, is dkms present in Debian?
[14:08] <slytherin> ﻿geser: Could you please do a rebuild for libxstream-java? pitti says there is no other way to retrieve the binary.
[14:09] <crimsun> slytherin: according to rmadison, no
[14:09] <AnAnt> slytherin: nope, not in debian yet
[14:09]  * persia does the libxstream-java build1 upload
[14:10] <james_w> crimsun: no problem, I just want to know if I can file a sync request, or it needs an FFe first.
[14:13] <slytherin> persia: thanks
[14:17] <superm1> AnAnt, there is an ITP filed for it, and a bunch of discussion that happened
[14:17] <superm1> I believe the person who was pushing to get it in is still looking for a sponsor though
[14:34] <AnAnt> superm1: that's me !
[14:34] <AnAnt> superm1: I filed the ITP I mean
[14:34] <AnAnt> superm1: what discussions you talking about ?
[14:34] <AnAnt> superm1: you talking about sl-modem or dkms ?
[14:36] <AnAnt> superm1: anyways, I meant the ITP for sl-modem
[14:43] <superm1> AnAnt, i mean for DKMS
[14:44] <superm1> AnAnt, dave palimino (sp) filed the ITP for DKMS
[14:46] <AnAnt> superm1: ok, I want to add dkms support to sl-modem, I noticed that sl-modem currently builds the modules in debian/rules, dunno how module-assistant uses that
[14:46] <AnAnt> superm1: it is in a binary-modules: target in debian/rules, so for dkms, shall I add the dkms commands there ?
[14:46] <persia> AnAnt, module-assistant needs you to build a -source package, and add m-a hooks.
[14:47] <AnAnt> superm1: or should they be in a postinst file ?
[14:47] <superm1> AnAnt, generally you do the dkms steps in the postinst
[14:47] <AnAnt> persia: yes, there is an sl-modem-source package
[14:47] <superm1> that way you don't ship a pre-compiled version
[14:48] <AnAnt> superm1: ok
[14:48] <AnAnt> superm1: so a package can support both m-i module-assitant and dkms, right ?
[14:49] <AnAnt> superm1: I mean, if I leave the debian/rules as is (except for adding install dkms.conf), and add a postinst to run dkms commands, then the package can work with both, right ?
[14:49] <superm1> AnAnt, yeah I suppose
[14:49] <superm1> AnAnt, i've always torn out the m-a stuff so as to not confuse people in Ubuntu
[14:49] <superm1> but that will work
[14:50] <AnAnt> cool
[14:50] <persia> If you can, it might make sense to try to detect if the build is happening in Debian or Ubuntu, and either do m-a or dkms hooks as a result.
[14:52] <AnAnt> persia: actually I will check for dkms instead of debian/ubuntu
[14:52] <AnAnt> that's what I thought of
[14:52] <persia> AnAnt, Remember to check if it's available, rather than if it's installed.
[14:53] <AnAnt> persia: [ -x /usr/sbin/dkms ] ?
[14:53] <persia> No, that checks if it is installed.  You need to see if the package could be installed.
[14:53] <persia> If you do that, you'd have to build-depend on dkms, and it would FTBFS in a distro without DKMS
[14:54] <superm1> persia, why not just recommend DKMS?
[14:54] <superm1> if it's available it shows up, and it runs in the postinst like AnAnt was suggesting
[14:54] <persia> superm1, Because there is no Build-Recommends:
[14:54] <superm1> persia, it's not needed to build
[14:54] <superm1> persia, just in the postinst
[14:55] <persia> superm1, The trick is to create a source package that uses m-a if built in a distro without DKMS, and uses DKMS if built in a distro that has it.
[14:55] <superm1> oh I see.
[14:55] <persia> Err.  create a source package that generates a binary package that ...
[14:55] <superm1> yeah
[14:55] <persia> Otherwise AnAnt has to maintain the source in two places, or maintain the delta, which is annoying.
[14:55] <superm1> well aside from clever trickery, maintaining the delta wouldn't be "horrible"
[14:56] <persia> No, but the clever trickery is better, no?
[14:56] <superm1> because sl-modem isn't rev'd too much I don't believe
[14:56] <superm1> clever trickery is ideal, but time consuming to come up with
[14:56] <persia> Actually, upstream is fairly active.  It's just that nobody was maintaining it, so it gave the impression of bing inactive.
[14:57] <persia> Well, it's unlikely to get uploaded anywhere until either squeeze or jaunty open, so there's time now.
[14:57] <AnAnt> it is active upstream
[14:57] <AnAnt> I think
[14:57] <persia> And we're *way* behind.
[14:58] <superm1> ah I see
[14:58] <AnAnt> to tell you the truth
[14:58] <persia> I think we last updated for Edgy or Feisty or something
[14:58] <AnAnt> the preivous maintainer seems that he didn't want to package 2.9.11 for copyright reasons
[14:58] <superm1> well AnAnt then for clever trickery, you'll need to have debian/control dynamically created.  Perhaps can you run something such as apt-cache policy from within debian/rules to query if DKMS is available?
[14:59] <superm1> buildd's should have a valid apt cache in their env
[15:00] <directhex> AnAnt, legitimate copyright reasons?
[15:00] <AnAnt> directhex: dunno
[15:00] <AnAnt> hang on
[15:00] <AnAnt> here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354216
[15:00] <directhex> see, this is why wikis are useful for team collab on packaging
[15:01] <AnAnt> superm1: ok, I got two modules slusb & slamr, both are built using same make command
[15:02] <AnAnt> superm1:  so shall I do BUILT_MODULE_NAME[0]="slusb slamr" ?
[15:02] <superm1> AnAnt, no you have separate built module name blocks for each
[15:02] <superm1> but only need the one build command
[15:02] <superm1> look at lirc
[15:03] <persia> Can't one relicense BSD code as GPL code, for recent BSD anyway?
[15:03] <superm1> it has a ton of modules, see how it did dkms.conf
[15:03] <AnAnt> superm1: ok, another problem
[15:03] <AnAnt> superm1: slusb cannot be built for kernel modules > 2.6.24 , how can I handle that ?
[15:04] <superm1> AnAnt, do you have a patch for it?, or it simply CANT be built for such modules?
[15:05] <AnAnt> superm1: upstream says that there's support for it for kernels > 2.6.24
[15:05] <superm1> so what's the problem then?
[15:05] <AnAnt> superm1: actually, in upstream's makefile he checks for kernel version > 2.6.24 before building slusb
[15:05] <superm1> oh less than 2.6.24
[15:05] <AnAnt> superm1: how should I handle that in dkms.conf ?
[15:05] <superm1> right
[15:06] <superm1> AnAnt, I wouldn't worry about it, the ubuntu release it's entering is going to be significantly further than 2.6.24
[15:06] <AnAnt> superm1: well, what if one wants to build for 2.6.24 for example ?
[15:07] <persia> AnAnt, Let's assume that everyone using this will be at least on 2.6.26 (lenny), if not 2.6.27 (intrepid).
[15:08] <persia> AnAnt, If you *really* care about backports to hardy, you might look at a source-changed-backport, but there's not exactly a lot of users complaining.
[15:08] <AnAnt> persia: will it be complex to assume otherwise ?
[15:08] <AnAnt> superm1: what's BUILT_MODULE_LOCATION ?
[15:09] <AnAnt> superm1: is that where to find the module after build ?
[15:09] <superm1> AnAnt, yeah
[15:09] <persia> AnAnt, hardy is 2.6.24.
[15:20] <AnAnt> hmmm, sl-modem-source package has the source files packed in a /usr/src/sl-modem.tar.bz2, does dkms support that ?
[15:22] <nhandler> Good morning Daniel
[15:24] <dholbach> hi nhandler
[15:31] <geser> slytherin: was libxstream-java the only affected package?
[15:31] <slytherin> geser: yes as per my analysis.
[15:31] <geser> persia: have you tried asking cprov if he can recover libxstream-java back from LP?
[15:32] <james_w> he uploaded a new version to build it again
[15:32] <cprov> geser: ubuntu primary archive ?
[15:33] <geser> cprov: yes, LP ate libxstream-java  (arch:all) after to many promotions/demotions
[15:33] <geser> cprov: persia "fixed" it by a new upload
[15:34] <cprov> geser: uhm, promotion + demotion in the same publishing cycle ?
[15:35] <persia> cprov, Something like that.  I think it was multiverse<->unverse
[15:35] <cprov> persia: uhm, is there a bug filed about it ?  (let me check)
[15:36] <persia> cprov, Not for that specifically.  pitti recommended an upload in -devel some time back.  I'll see if I can find context.
[15:37] <persia> No, that goes farther than my current backscroll.
[15:40] <james_w> lytherin> pitti: need some help. The binary for libxstream-java was eaten by LP when moving from multiverse to universe and back again. (bug #268538). Any idea how can it be restored?
 slytherin: hm, I guess we can only upload a build1 and shove it through NEW
[15:40] <james_w> cprov: persia ^
[15:41] <cprov> james_w: thanks, let me find the bug in soyuz context.
[17:34] <shahriar86> Hi I want to report a bug in Probhat (Bengali) Keyboard layout (Ubuntu 8.10 Intrepid Ibex Beta 1) how can I report a bug in such a way that a Bengali speaking Developer (tester) notices it?>?
[17:35] <shahriar86> I am aware of launchpad is the place to report bug. but the problem (bug) is of complex type that any developer won't understand it. Only Bengali speaking people will understand what I am saying
[17:35] <shahriar86> so is there any specific way I can approach the Bengali developers for Probhat layout?
[17:36] <shahriar86> I am more of looking for the people who packaged Probhat Keyboard layout in Intrepid (its almost close to imposible to make a non-Bengali understand the problem/bug)
[17:36] <shahriar86> any help?
[17:36] <AnAnt> shahriar86: isn't there a bengali loco team ?
[17:36] <AnAnt> shahriar86: and can an arab understand it ?
[17:37] <shahriar86> not really
[17:38] <shahriar86> yes there are few bengali loco team. But they are not active that much (funny thing is I am also part of a Bengali speaking Loco team)
[17:38] <shahriar86> I need to find out who have packaged the Bangladesh Probhat Keyboard layout
[17:38] <shahriar86> then It will be easier
[17:38] <AnAnt> shahriar86: what's the package name ?
[17:40] <shahriar86> its a keyboard layout
[17:40] <AnAnt> shahriar86: or do you  know what file is causing you the problem ?
[17:40] <shahriar86> Probhat
[17:40] <shahriar86> no sorry
[17:41] <shahriar86> the thing is in Bengali there are few complex words we write them in one go. like say স্ট we write it s+t in probhat we type s+/+t to join them
[17:41] <shahriar86> now it seems the key "/" is missing or omitted somehow
[17:42] <shahriar86> when ever I am typing s+/+t I only get "s" not "st"
[17:42] <shahriar86> Bangladesh Probhat Keyboard layout
[17:43] <AnAnt> shahriar86: are you using hardy or intrepid now ?
[17:43] <shahriar86> I am using hardy 8.04.1 kde 3.5
[17:44] <shahriar86> I run Intrepid in Virtual box 1.5.6
[17:44] <shahriar86> I installed Intrepid last Thursday
[17:44] <AnAnt> the problem is in hardy or intrepid ?
[17:45] <shahriar86> intrepid
[17:45] <shahriar86> in hardy it is working just fine
[17:45] <shahriar86> (the way it should work)
[17:45] <shahriar86> the problem is in Intrepid beta 1
[17:45] <AnAnt> shahriar86: is it in console or GUI ?
[17:45] <shahriar86> gui
[17:46] <shahriar86> ah can you rephrase last question about gui or cui
[17:46] <shahriar86> not sure about how a keyboard layout could be gui or cui
[17:49] <AnAnt> try asking in #ubuntu+1 about the package that contains keyboard layouts
[17:50] <AnAnt> in Intrepid
[17:50] <shahriar86> ok thanks
[17:52] <slytherin> shahriar86: all the indic related packages in Ubuntu are inherited from Debian. The package that contains keyboard layout seems to be scim-tables-additional and the file is probably /usr/share/scim/tables/Bengali-probhat.bin. Even if you file a bug in Ubuntu, chances are that it will get forwarded to Debian.
[17:53] <shahriar86> ok thanks I am checking with it
[17:53] <AnAnt> shahriar86: you are using scim ?
[17:54] <shahriar86> no
[17:54] <AnAnt> slytherin: I think it's something else
[17:54] <shahriar86> its an stand alone keyboard layout (more of a default keyboard for Bengali speaking users)
[17:54] <slytherin> shahriar86: how do you select keyboard layout?
[17:54] <shahriar86> I know who have developed the initial layout but not sure who have packaged it
[17:55] <shahriar86> from system>preferences>>keyboard>>layouts
[17:56] <shahriar86> Add (country Bangladesh)>> Variants Probhat Keyboard
[17:56] <slytherin> shahriar86: that is package xkb then or xkb-data
[17:56] <shahriar86> ok thanks
[17:56] <shahriar86> so how do I report the problem?
[17:57] <slytherin> ﻿shahriar86: First you can try sending mail to indlinux list to check if anyone else has faced the issue. If no one and it is specific to ubuntu then file a bug.
[17:57] <shahriar86> ok thanks
[18:40] <goshawk> hi
[18:40] <goshawk> if someone has free time
[18:40] <goshawk> can please review http://revu.ubuntuwire.com/details.py?package=dsss
[18:40] <goshawk> ?
[18:40] <goshawk> thanks
[18:41] <slytherin> goshawk: I believe at this point of time in release cycle people are busy with fixing build failures and bugs. :-)
[18:41] <goshawk> oops
[18:41] <goshawk> sorry
[18:41] <goshawk> i didn't thought about it
[18:42] <goshawk> :(
[18:46] <slytherin> persia: there?
[19:58] <AnAnt> superm1: hello, I added dkms support to sl-modem, but it only builds one module, not the other, and make.log is empty !
[19:59] <AnAnt> not really empty, but it doesn't show the CC lines at all, even for the compiled module
[20:01] <AnAnt> slytherin: about kbd, the special laptop keys (like web browser key, ...) are they defined in the kbd/kbd-data ?
[20:02] <slytherin> AnAnt: I don't think so.
[20:03] <AnAnt> ok
[20:21] <fabrice_sp> DktrKranz: thanks for acking Bug #242572! \o/  Any other motu-release here for the second ack? ;-)
[20:34] <rainct> Hi
[20:36] <rainct> Uhm.. I've installed Intrepid Beta (full format! :D) and now the computer *completely* hangs (ie, I can't raise elephants) when I try to enter GNOME (openbox wtf :P). Did anyone else experience the same problem?
[20:37] <geser> rainct: have you tried changing to the console and checking top and also perhaps dmesg?
[20:39] <rainct> geser: I can't. It's *dead* (with "raise elephants" I mean Alt+PetSis+R,S,E,I,U,B - even that doesn't work).
[20:39] <rainct> I looked at .xsession-errors after rebooting but that doesn't say anything interesting
[20:40]  * rainct will try again once has has finished upgrading everything
[20:40] <sebner> rainct: upgraded to intrepid?
[20:40]  * sebner hides
[20:40] <rainct> sebner: nope, clean install
[20:40] <ajmitch> well if it was a full kernel panic & everything went splat, then nothing would get logged
[20:40] <sebner> ^^
[20:41]  * ajmitch blames the circus midgets
[20:49] <DktrKranz> fabrice_sp, you're welcome ;)
[20:53] <rainct> (that's the .xsession-errors: http://paste.ubuntu.com/57126/plain/)
[21:42] <rainct> How can I get the MAC address of my ethernet card? (And why is nm-applet so complicated? :P)
[21:43] <DktrKranz> rainct, ifconfig | grep HWaddr
[21:43] <Laney> rainct: ifconfig or nm-applet both have it
[21:44] <Laney> "Connection information" in the latter
[21:44] <rainct> Laney: but you have to configure the connection first, and it asks you for the MAC address for that
[21:44] <rainct> DktrKranz: ah, of course. thanks :)
[21:44] <Laney> rainct: :O what kind of connection?
[21:44] <rainct> Laney: wired
[21:45] <Laney> I've not had to do that
[21:45] <DktrKranz> rainct, one non-obvious solution would be sorting skbuff linked list with a kernel module, I had a LKM which does that
[21:47] <leonel_> hello :   I'm trying to backport Django 1.0 from intrepid to hardy and need  python-sphinx   when doing  debuild -S -sa  I get this error :  dh_clean: Sorry, but 6 is the highest compatibility level supported by this debhelper.   with the package  sphinx
[21:47] <leonel_> even if I change the  debhelper version in   debian/control
[22:06] <geser> leonel_: check debian/compat
[22:07] <leonel_> geser: thank you
[22:30] <Adri2000> zul: so, what's up with fail2ban?
[22:43] <rainct> I suppose I can replace nm-applet with network-manager?
[22:43] <james_w> ScottK: hi, were you giving an ACK for a packagekit standing freeze exception?
[22:44] <RAOF> rainct: No; nm-applet is the applet that allows you to interact with network-manager
[22:44] <rainct> RAOF: uhm? but network-manager isn't installed on Intrepid
[22:44] <RAOF> ...?!
[22:44] <rainct> errr.. network-admin
[22:45] <RAOF> Aaah.  Yes.
[22:45] <rainct> but it is neither in the repos :(
[22:46] <rainct> well, can someone tell me how to configure the 3G connection
[22:46] <rainct> please?
[22:46] <rainct> ie, where do I choose which device the modem is?
[22:55] <rainct_> argh, finally it's working :P
[22:55] <rainct_> somehow nm-applet's configuration window and I aren't compatible, but now that's it's working it's actually pretty nice :P