[06:49] <dholbach> good morning
[11:08] <MetalGodWin> Hello, (Hope i found the right place?) What section does my app belong to if it's a development tool? I need to fill that in in the control file during packaging.
[11:10] <JainAmber> MetalGodWin, The list of sections is here: http://packages.debian.org/stable/
[11:10] <MetalGodWin> JainAmber: Thank you
[11:14] <JainAmber> MetalGodWin, See description for line2: http://www.debian.org/doc/manuals/maint-guide/dreq.en.html#control
[11:15] <JainAmber> Also, http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections
[11:16] <MetalGodWin> JainAmber I came to the conclusion that my app belongs to devel. Thanks again :)
[11:21] <MechanisM> I'm did apt-get source somepackage, modified it and wanna generate deb from it. how to do it?
[11:21] <MechanisM> and also did apt-get build-dep somepackage
[11:23] <arand> MechanisM: Normally you'd use debuild (or dpkg-buildpackage)
[11:23] <MechanisM> which command I should pass?
[11:24] <MechanisM> ok did it
[11:26] <MechanisM> btw can I build on 32 bit ubuntu debs for all and for 64 bit ubuntu?
[11:27] <MechanisM> like I seen some packages called packagename-all.deb or packagename-amd64.deb etc
[11:28] <astraljava> MechanisM: You cannot build 64-bit packages on 32-bit systems. But the -all is another thing, it means that same package can be utilized on all archs, ie. it's arch independent.
[11:29] <MechanisM> okay, thanx a lot. btw currently I'm on 12.10 x32 but I have also 64bit 12.04 can I build 32/64 both on 64 bit os?
[11:30] <directhex> yes, but it needs a little bit of setting up
[11:30] <MechanisM> I have ia32libs and all related things
[11:31] <MechanisM> ok thank you guys I'll investigate on this issue later. just wanted to make sure.
[11:31] <directhex> you can't build a 32-bit version from "inside" the 64-bit os. you need a minimal 32-bit environment available, e.g. as provided by pbuilder-dist
[11:31] <directhex> it'll just create a 32-bit os tarball, and use that as a build environment. it's easy once you get it going
[11:31] <MechanisM> okay. I'll check this when I'll be booted into 64 bit os
[11:32] <directhex> remember that you only need different 32 bit or 64-bit packages if your code isn't cross-platform (i.e. it's C or C++ or similar)
[11:32] <directhex> python or perl or java or c#, you should only need one "all" package
[11:33] <MechanisM> mine is python with c bindings
[11:50] <MetalGodWin> I'm unable to start my app once i've installed it to my system. It's written in python, anything else I should think of than following the guide @http://developer.ubuntu.com/packaging/html/packaging-new-software.html
[11:51] <Zhenech> posting the error you see when you try to execute the app from the shell might hekp
[11:51] <Zhenech> help*
[11:51] <Laney> #ubuntu-app-devel is probably better
[11:53] <MetalGodWin> only a can't find msg if I run the command <appname>. Tried python <appname> then it says it cant find the__main__ class
[11:54] <MetalGodWin> could it be that i've used capital letters for the .py files? My app-name is installed with a lowercase name or how you should put it
[11:54] <MetalGodWin> Laney: thank i will try that
[13:06] <nhandler> Does anyone know where the little icons on https://apps.ubuntu.com/cat/search/?q=rhythmbox are pulled from?
[13:19] <chris_> i see a lot  prerequisite articles to read before becoming so immerged in this MOTU stuff :)
[14:49] <MetalGodWin> I don't get any answer from the logged in ones at app-devel..  I've been stuck at packaging my python app for hours now. Read and tried several how-to guides, nothing works. Could really use some help.
[16:10] <ScottK> It would be nice if someone would sponsor the fix for bug  958305 for precise.
[16:35] <stgraber> ScottK: done
[16:35] <ScottK> stgraber: Thanks.
[16:38] <lewtds> Hi, I'm trying to package a software that uses waf as the build system. But when using pbuilder to build, when it calls waf, the command fails with this message "ImportError: No module named tarfile" (Python module). What should I do?
[16:38] <ScottK> Accepted.
[16:38] <ScottK> lewtds: The best option is convince upstream not to use waf.
[16:39] <lewtds> that would be too extreme. Why is the tarfile module not imported? I thought that one is built
[16:39] <lewtds> -in
[16:41] <lewtds> it builds fine outside of pbuilder thouh
[16:43] <ScottK> waf is generally regarded as a less than sane build system.
[16:44] <ScottK> Do you build-depend on python?
[16:44] <ScottK> The tarfile module is part of python2.7/3.2.
[16:47] <lewtds> Thanks, I'd probably try adding it.
[16:48] <lewtds> The codebase is in Vala. Do you have any suggestion on which build system that goes well with Vala without too much hassle?
[16:50] <ScottK> No.  I've never done any vala, but !waf
[16:51] <tumbleweed> ewww, waf
[16:51] <lewtds> thanks, adding python2.7 dependency did the trick!
[16:51] <Laney> ScottK: fancy processing the backports waiting in $queues?
[16:52] <tumbleweed> err, you should rather be depending on python than python2.7
[17:05] <ScottK> Laney: Did precise.
[17:06] <Laney> I uploaded some to lucid too
[17:15] <ScottK> Laney: Those are done too.
[17:16] <Laney> thanks
[17:17] <Laney> ScottK: NEW too :-)
[17:17] <ScottK> OK.  I'll look there too.
[17:17] <Laney> Just because I know how much you like using this new tool
[17:18] <ScottK> Heh.
[20:43]  * tumbleweed 's INBOX is under a haskell seige today
[20:43] <Laney> ?!?!?!
[20:44] <Laney> that's me wondering what I missed
[20:44] <ajmitch> is laney breaking something again?
[20:44] <Laney> adconrad broke it. not me. nuh uh.
[21:59] <Laney> seems someone is doing a transition
[21:59] <Laney> this seems unwise.
[22:52] <directhex> doesn't ghc support linked libraries yet?
[22:56] <Laney> in a rudimentary way