[00:56] <Flakeparadigm> Hello, I have a question about something in Karmic.
[04:46] <sololxy>  hi,how can find the source code of getty? i just find the source of agetty. i guese that is the code.But, i want to know  whether someone change the name getty to agetty, and when and how he or she change it. i check the utli-linux source, but in configure.am and Makefile.am, there is no such information. can anyone help me? thx
[05:12] <Rocket2DMn> lol kees , i told you so :)  That guys changed the page back
[05:13] <kees> Rocket2DMn: I'm gonna wait until monday and talk to mdke about it.  "man sudo_root" is not as easily changed.  ;)
[05:14] <Rocket2DMn> kedars, ok, I'm curious to see what happens with this
[05:14] <Rocket2DMn> kees, ^
[05:17] <kees> me too; though I guess I don't really have a vested interest in it -- I just hate to see useful information disappear.  but if that's been the determination of the forums, I can see the point of removing it.  I don't believe it to be "insecure", though.  that's just silly -- sudo in ubuntu is one-credential-gets-you-root anyway, so no different realy.
[05:20] <Rocket2DMn> well, the debate is deeper than that, for instance, you can track sudo commands a lot easier than commands simply run as root
[05:20] <Rocket2DMn> but again, not here to discuss whether or not it should be there.  The point is that this guy won't listen to decisions made by official ubuntu teams
[06:01] <Dyllan> Hi all. I have written a script designed specifically for my company environemnt and would like to make the script available in a .deb file for easy installation by the staff. The script needs to be dumped into /usr/bin and in programs menu, all info i have found for making a .deb is too complicated for my needs, any ideas? - thanks
[08:38] <pitti> Good morning
[08:40] <pitti> slangasek, jdstrand: I didn't take a look at the sun-java* stuff yet, but will do; as per the recent discussion, they should be generally ok for hardy
[09:00] <Dyllan> When i install my custom .deb file, everything install and works 100%, however the gdebi app does not show the 'Re-Install' option or 'Installed' it only shows 'Install' so it's like it doesnt recognise it is installed, any ideas, do i have to add something to my control file? - thnkas
[09:01] <lifeless> Dyllan: to reinstall you need it listed in the repositories I think
[09:01] <pitti> Dyllan: "install" should just work, though
[09:01] <pitti> Dyllan: I don't think gdebi even has more complex UI cases than simply "install this .deb"
[09:02] <pitti> it's just a gui wrapper for sudo dpkg -i foo.deb
[09:02] <lifeless> pitti: I inferred 'gdebi app' as 'synaptic :P
[09:03] <Dyllan> Understood, so it is normal that i cannot 'Search' for the package in Snyaptic either? It IS there, but i have to scroll alphabetically do find it. This is normal behavious for both the gdebi and synaptic?
[09:03] <lifeless> Dyllan: the search works on the apt list of packages, not the dpkg list of installed packages.
[09:03] <lifeless> Dyllan: so yes, this is normal
[09:03] <Dyllan> I can settle for the fact that it doesnt get treated like a .deb in the repo, just want to make sure im doing everything correctly and that its ubuntu's way of working not something i have done wrong/
[09:03] <lifeless> but arguably a bug in the xapian search index creation/hooks.
[09:04] <Dyllan> Ok, excellent.
[09:04] <Dyllan> makes sense.
[09:05] <Dyllan> now i gotta try and get it into the repo ;P
[12:23] <LCID_Fire> Hello, I get a warning on a changed ABI when I try to build a kernelpackage from source. Can someone explain what the correct way to handle the ABI is?
[12:54] <sistpoty> statik: ubuntuone-client debdiff uploaded, thanks. please merge into bzr.
[13:23] <svarg> hi
[13:24] <svarg> why isnt the ubuntu release scheduled for october not have a long term support release?
[13:24] <pitti> svarg: 10.04 will most probably be LTS
[13:24] <Laney> why should it?
[13:24] <Laney> ;)
[13:24] <pitti> because we planned it that way :)
[13:25] <svarg> pitti but i'd been hearing earlier that 9.10 was to be LTS :(
[13:25] <pitti> svarg: not from anywhere officially for sure
[13:25] <pitti> no, 9.10 will definitively not be LTS
[13:25] <pitti> 9.10 (karmic) is a "latest crack and intrusive changes" release
[13:25] <svarg> before 9.04 was released, 9.10 was supposed to be LTS
[13:25] <pitti> no, it wasn't
[13:26] <pitti> where did you see this?
[13:27] <svarg> erm ok
[13:27] <svarg> good i came in here
[13:27] <svarg> friend of mine
[13:27] <sebner> pitti: still a 16 hour day? I don't want to annoy but hardware issues are annoying :\
[13:28] <pitti> it's 2nd on my list now
[13:29] <svarg> thakns for the info pitti
[13:31] <Amaranth> From the sound of it's still a bit up in the air whether or not 10.04 will be LTS too
[13:31] <pitti> Amaranth: it'll be official in less than a month
[13:31] <pitti> Mark traditionally introduces the new release name, theme, and LTSness around beta time
[13:34] <sistpoty> ludicrous llama :)
[13:34] <pitti> lazy lobster!
[13:34] <sistpoty> heh
[13:35] <pitti> lamenting lizard?
[13:36] <sistpoty> lusty leopard?
[13:42] <pitti> sebner: the workaround with moving the udev rules aside should still work, though?
[13:43] <sebner> pitti: sure
[13:44] <svarg> pitti: was under the impression that it was to be. which is why i hadnt upgraded my comp at home
[13:44] <svarg> guess i could now now that this is cleared
[13:44] <svarg> nyways, found an alternative so its ok
[14:18] <Madkiss> hi folks
[14:19] <Madkiss> just a little question; when I install Kubuntu 9.10 alpha, I get a very, very boring KDE4 standard theme after the installation; does anybody in here know whether this is the one that is going to ship with 9.10 or will there be some graphical tuning?
[14:23] <ScottK> Madkiss: Kubuntu tries to stick to upstream KDE pretty closely.  There was a plan to do some themeing work for this development cycle, but it didn't get done due to lack of volunteers to do the work.
[14:24] <Madkiss> I see, so 9.10 is indeed going to ship with the KDE 4.2 standard theme?
[14:24] <sebner> ScottK: You're free to look at a FTBFS (I'm not into kde/qt stuff), seems to be a libarts issue. Source package is twinkle
[14:24] <ScottK> Madkiss: 4.3, not 4.2, but yes.
[14:24] <ScottK> sebner: Thanks.
[14:24] <Madkiss> ohmigad.
[14:24] <Madkiss> ;-)
[14:25] <sebner> ScottK: O_o Thanks for what?
[14:25] <ScottK> sebner: For pointing it out.
[14:25] <ScottK> Madkiss: It takes people to do the work.  Please join #kubuntu-devel if you're interested in being part of the solution.
[14:26] <sebner> ScottK: heh, we can thank each other when it's fixed :)
[14:26] <Madkiss> ScottK: well. Given that I have maintained Qt3 for like two years or some such for Debian, I am at least not scared to the shit when seeing KDE/Qt-Stuff ... might be a good idea indeed
[14:26] <ScottK> sebner: If you wanted to look at vtk, that needs some love too.
[14:26] <ScottK> Madkiss: We'd love to have the help.
[14:28] <sebner> ScottK: what kind of love? Update to 5.4?
[14:29] <ScottK> sebner: Fix the build failures
[14:30] <sebner> ScottK: heh, you say that so easy. (Even so I only support i386 in my heart :P) I'll do my best
[14:31] <ScottK> I didn't say it was easy.
[14:31] <ScottK> sebner: There is a patch in Debian bts that may be relevant for the armel build failure.
[14:31] <ScottK> The rest, dunno.
[14:31] <sebner> ScottK: ah thanks for the hint. I'll take a look
[14:32] <sebner> ScottK: btw, some info what I've done with twinkle. Evidently it needs libarts-dev b-d so I tried with --without-arts but without a result :(
[14:32] <ScottK> OK.
[14:33] <ScottK> sebner: It's a voip client.  How much use will it be with no sound support?
[14:34] <sebner> ScottK: good point but more use than non-installable though
[14:34] <ScottK> I was thinking about removal.
[14:34] <sebner> ScottK: yeah, but that's more like the worst case aka the "last way"
[14:35] <ScottK> I know we aren't going to rewrite it to provide sound without arts.
[14:35] <ScottK> So I'll say again, what's the point in a voip client that has no sound?
[14:35] <sebner> ScottK: afaik it has 2 ways for sound?!
[14:36] <ScottK> OK
[14:36] <sebner> ScottK: I'm only wondering why it built in Debian. They still have libarts but it was not pulled in iirc (looking at the buildlog)
[14:40] <aladin_> hello, i have a big problem.. someone can tell to me the equivalent to "dpkg --force all" in apt?
[14:48] <maxb> From memory it's something along the lines of -oDPkg::Options::=--force-all but NEVER USE --force-all
[14:48] <maxb> There is always a more specific option you should be using instead
[14:49] <aladin_> [15:45] <aladin_> dpkg: error processing /var/cache/apt/archives/linux-image-2.6.30.5_2.6.30.5-10.00.Custom_i386.deb (--unpack):  trying to overwrite `/lib/firmware/whiteheat.fw', which is also in package linux-image-2.6.29.4 dpkg-deb: subprocess paste killed by signal (Broken pipe) [15:46] <aladin_> if i use dpkg -i --force all package.deb work all fine [15:46] <aladin_> but if i use apt-get -f install package.deb do not w
[14:49] <sebner> ScottK: I'm wondering where I can test the armel fix as I don't want to upload several times into the archive
[14:50] <ScottK> sebner: Talk to NCommander.
[14:50] <sebner> ScottK: Aye Aye, Sir
[14:50] <aladin_> ScottK-desktop:
[14:50] <aladin_> ScottK: able to help me ?
[14:50] <ScottK> aladin_: No
[15:13] <maxb> devicekit-power still fails to notice that I'm on battery unless I am when I boot - this has been the case for several alphas now. Is there anything I can/should be doing to ensure the issue doesn't slip and persist into Karmic release?
[16:11] <highvoltage> hey, I'm working on a man page for do-release-upgrade. It's --help says that you can use --frontend to choose a frontend, but what are they options?
[16:16] <Hobbsee> highvoltage: gtk and qt, i think
[16:16] <Hobbsee> not sure of syntax, etc
[17:23] <Dyllan> hi all.
[17:24] <Dyllan> Is there a way to install pre-deps from a .deb i have created? I specify the pre.dep in the control file, but gdebi just fails to install and complains that the pre-dep is needed which makes perfect sense, but i would like for it to be installed automatically if possible?
[17:36] <ScottK> sebner: Twinkle fixed.  'twas a build-dep problem.  Nothing to do with arts.
[17:37] <sebner> ScottK: O_o, what's the missing b-d?
[17:37] <ScottK> sebner: libccrtp needed a rebuild.
[17:39] <sebner> ScottK: wth O_o
[17:43] <sebner> ScottK: crazy. anyways, thx for your help. If I stumble over a kde/qt package that not build can I talk to you again?
[17:44] <ScottK> sebner: Sure or just ask in #kubuntu-devel.
[17:44] <sebner> great :)
[17:55] <Dyllan> Is there a way to install pre-deps from a .deb i have created? I specify the pre.dep in the control file, but gdebi just fails to install and complains that the pre-dep is needed which makes perfect sense, but i would like for it to be installed automatically if possible?
[18:01] <joaopinto> Dyllan, does dpkg -i fail ?
[18:02] <Dyllan> joaopinto: Well I am trying to avoid doing anything from the command line, this is a custom .deb that will be downloaded by others, non power users, who i want to be able to just download, double-click on .deb and it installs with dependencies.
[18:02] <joaopinto> anyway, probably #ubuntu-motu is a better place to ask
[20:40] <ulaas> irc through empathy... Hmm i must be going crazy.... Anyway, my notifications popup vertically in the middle of my screen. who to blame?
[20:54] <pitti> ulaas: please report a bug against notify-osd
[20:55] <ion> It’s supposed to be a feature, according to the changelog.
[20:55] <ion> No, i don’t like it either. :-P
[20:56] <ulaas> pitti, is there a way to pop it up with a debug message just to be sure?
[20:57] <pitti> bwah, I just got it, too now
[20:57] <pitti> I never saw it before
[20:57] <pitti> ulaas: notify-send in the libnotify-bin package
[20:57] <pitti> must have gotten a new version recently, too
[20:57] <pitti> this can't be deliberate, can it?
[20:57] <ulaas> pitti, please not
[20:58] <ion> /usr/share/doc/notify-osd/changelog.Debian.gz
[20:59] <ion> It’s a deliberate mistake, just like the blurry font rendering that has been the default in Ubuntu for a while. :-P
[21:13] <sebner> pitti: heh, and now my specific problem? Though my strace etc output looks nearly the same as the othres
[21:13] <sebner> *pthers
[21:13] <sebner> *others
[21:13] <sebner> arghs
[21:14] <ion> You just dereferenced a null pointer.
[22:19] <ScottK> pitti: The middle pop-up is by design.
[22:19] <ScottK> Lots of 'discussion' on the ayatana ML about it.
[22:25] <maxb> !info bzrtools karmic
[22:26] <maxb> ^^^ Unfortunately, that appears to actually contain bzrtools 2.0.0
[22:30] <ScottK> NCommander or pitti: I'd appreciate it if you'd rescore libccrtp ahead of the other Universe stuff as it needs to get built and published on ia64/sparc before twinkle or twinkle will fail.
[22:50] <wgrant> ScottK: Argh, what? It looks ridiculous.
[23:15] <ScottK> wgrant: Which looks ridiculous?
[23:17] <wgrant> ScottK: The not-quite-middle-aligned notify-osd.
[23:19] <ScottK> wgrant: Oh.  Right.  Well that's part of the benifit of using Ubuntu, you get most of the work the design team does.