[02:34] <jpan_> robr, ping
[02:36] <robr> jpan_: pong
[02:36] <jpan_> robr, do you know how do we generate modules.dep file for each kernel?
[02:37] <robr> jpan_: this a #moblin topic, but image-creator runs depmods at target image creation time for each kernel installed into /boot
[02:39] <jpan_> robr, it seems modules.dep file is different than what i run depmod -a on the target fs
[02:41] <robr> jpan_: how so?
[02:43] <jpan_> robr, let me double check. but i put the new psb.ko in with dependecy on firmware class then i recreate a new image, the modules.dep does not show that new dependency.
[02:44] <jpan_> robr, so it should rerun depmod each time i create a new image, right?
[02:45] <robr> jpan_: that is correct ... this sounds like the same problem that rustyl ran into
[02:45] <rustyl> what are we talking about?
[02:46] <robr> rustyl: did you ever figure out the issue with depmod that you were seeing where the module dependencies were not getting updated?
[02:46] <robr> rustyl: read jpan_  's comments above
[02:47] <jpan_> robr, rustyl , the problem is that modules.dep is not updated when i create a new image with a newly loaded kernel driver.
[02:49] <rustyl> robr, i fixed a bug where we were updating the project root instead of the target root
[02:49] <rustyl> this is handled at image creation time
[02:50] <robr> jpan_: are you using the latest and greatest image-creator?
[02:51] <jpan_> robr, mine is sometime last week of days old
[02:52] <jpan_> robr, i will update to the latest and try again
[02:52] <robr> jpan_: rusty's fix has been there for a couple of weeks...but update to the latest and see if this fixes the issue
=== Inuka_ is now known as Inuka
[06:47] <dholbach> good morning
=== doko_ is now known as doko
=== Blackgoth is now known as blackgoth
=== blackgoth is now known as Blackgoth
=== bspencer_ is now known as bspencer
[08:09] <simoncpu> hello
[08:09] <simoncpu> Have you guys had any luck running with WPA on iPAQ H5550?
[08:10] <Mithrandir> I don't think anybody has tried to do anything on the iPAQs at all.
[08:10] <Mithrandir> they're ARM-based, aren't they?
[08:13] <simoncpu> yepp yepp
[08:14] <simoncpu> i'm actually using familiar linux on my ipaq, but familiar's support channel seems to be very quiet
[08:14] <simoncpu> hehehe
[08:14] <Mithrandir> people keep asking about ARM stuff, but nobody has so far picked up the challenge to begin porting to ARM.
[08:14] <Mithrandir> we're targetting lpia initially.
[08:15] <simoncpu> do you guys use openembedded build env too?
[08:15] <Mithrandir> no
[08:15] <Mithrandir> we use Ubuntu packages
[08:17] <simoncpu> ubuntu mobile looks very promising
[08:17] <simoncpu> i hope i can play with it on my ipaq later
[08:17] <simoncpu> hehe
=== Blackgoth is now known as blackgoth
=== blackgoth is now known as Blackgoth
=== agoliveira is now known as agoliveira_brb
=== agoliveira_brb is now known as agoliveira
=== dholbach_ is now known as dholbach
=== agoliveira is now known as agoliveira_lunch
=== cprov is now known as cprov-lunch
=== agoliveira_lunch is now known as agoliveira
=== cprov-lunch is now known as cprov
=== viviji1 is now known as vivijim
=== agoliveir1 is now known as agoliveira
=== javamaniac_ is now known as javamaniac
=== cprov is now known as cprov-out
[20:59] <smagoun> debian n00b question: can I rename a package simply by changing the package name in the control + changelog files? I don't care if it installs cleanly over an old version.
[21:14] <smagoun> Mithrandir: ping
[21:30] <ian_brasil> smagoun: you will need the orig.tar.gz and then run dh_make ..make your changes then run debuild -S -sa ..i might be mistaken on this however
[21:31] <smagoun> ian_brasil: I don't have an orig.tar.gz (it's a 'native' package I think?).
[21:31] <ian_brasil> can't you apt-get source?
[21:32] <smagoun> I'm the upstream for the package (it's only a handful of files), so I just have a bzr project with the files and a debian subdirectory. I build directly from there
[21:34] <ian_brasil> move the debian folder somewhere else and then run dh_make ?
[21:35] <ian_brasil> this will create the 5 files you need copyright, control, rules, and changelog
[21:35] <jonnylamb> smagoun: Are you sure you want to rename the source package, and not the binary package?
[21:36] <smagoun> ian_brasil: So I can't just use sed to update my existing debian dir?
[21:36] <smagoun> jonnylamb: Eventually I want to rename everything, bzr repo included. binary is most interesting to me at this point though
[21:37] <jonnylamb> If you just want to change the binary package name then change the appropriate entry in control.
[21:39] <smagoun> jonnylamb: ok, that's what I hoped. I assume I need to update the package name in the changelog too
[21:39] <jonnylamb> Nope. Make sure you change "Package: foo" and not "Source: foo".
[21:40] <jonnylamb> A source package can be "bananadotcom", and still contain binary packages called "libc6"..
[21:40] <smagoun> so the changelog keys off source package. gotcha.
[21:41] <jonnylamb> Jep.
[21:41] <smagoun> supposing I did want to rename the source package as well, I would change the changelog and Source: in control?
[21:41] <jonnylamb> ..of course my example would be just wrong though.
[21:41] <smagoun> :)
=== asac_ is now known as asac
[21:42] <jonnylamb> Well, you should only have to change "Source: foo" and the changelog entry, but there might be some other stuff in the debian/ directory that needs changing. grep is your friend though.
[21:44] <smagoun> yup
[21:44] <smagoun> thanks for the help
=== sabotage is now known as sabotage_afk