[00:03] <micahg> so is empathy now the default or just avialable?
[00:08] <directhex> it should be the default afaik
[00:08] <micahg> ok
[00:08] <micahg> is pidgin staying in universe?
[00:08] <directhex> of course
[00:08] <micahg> cool
[00:08] <micahg> maybe I'll try empathy when I switch to karmic
[02:07] <rgreening> ScottK-desktop: ping
[04:09] <taggart> if a package is already in Debian, how does it get included in Universe?
[04:11] <StevenK> taggart: If the current development releases Debian Import Freeze hasn't occured yet, automatically, if it doesn't have Ubuntu changes.
[04:12] <taggart> ok cool, but that is for the current development right? are there backports to previous?
[04:13] <taggart> in particular LTS releases
[04:13] <StevenK> No, backports have to be requested and approved by a member of the backports team
[04:14] <taggart> "Karmic entered DebianImportFreeze on June 30, 2009."
[04:14] <taggart> hmm, looks like I might need to send a special request...
[04:14] <StevenK> taggart: What are you looking at getting synced from Debian?
[04:14] <taggart> fossology
[04:15] <taggart> I uploaded 1.1.0-1 a couple days ago
[04:15] <taggart> I'm the debian maintainer, but also on the upstream team
[04:15] <StevenK> Ah. Yes, you'll need to file a sync request or get a MOTU to file one.
[04:15]  * StevenK can probably just handwave and sync it
[04:15] <taggart> and rather than setup my own apt source for various ubuntu releases, I figured it would be better to do it the proper way
[04:16] <taggart> I don't have a launchpad account, so if you wouldn't mind that would be great (or I can register for one if you prefer too)
[04:17] <StevenK> However, that only gets 1.1.0 into Karmic
[04:18] <taggart> ok, where do I submit the backport request?
[04:19] <StevenK> taggart: See https://help.ubuntu.com/community/UbuntuBackports#How to request new packages
[04:20] <taggart> yeah I just found that :)
[04:20] <StevenK> taggart: Which requires a Launchpad account, but you have an unactivated one, see https://launchpad.net/~taggart
[04:21] <taggart> cool, claiming that now
[04:21] <taggart> so I guess I need to wait till it goes in Karmic before I submit the backport bugs
[04:23] <StevenK> taggart: https://launchpad.net/ubuntu/+source/fossology :-)
[04:23] <taggart> once something has been backported, is there anything that keeps it being backported or do I need to ping for new versions?
[04:23] <StevenK> taggart: The latter
[04:23] <taggart> ok
[04:23] <taggart> StevenK: sweet!
[04:23] <micahg> speaking of packaging import requests, if there is a request in debian to update from upstream, is there any benefit in me maknig a request in LP and linking to the debian reqeust?
[04:30] <ScottK> rgreening: Pong
[04:30] <rgreening> hey ScottK, how are you
[04:30] <ScottK> Craptastic.
[04:31] <rgreening> heh. bad day?
[04:32] <rgreening> I'm writing a 150 line man page for the tac_plus server.
[04:32] <ScottK> Not horrible, but the forecast for the week ahead is not good.
[04:32] <rgreening> ah
[04:32] <ScottK> Bah.  You can manage in just the nroff preamble stuff.
[04:33] <rgreening> ?
[04:33] <rgreening> I meant the details I have amount to 150 lines
[04:33] <rgreening> :)
[04:33] <rgreening> it's details, like my changelog entries
[04:33] <rgreening> hah
[04:36] <ScottK> rgreening: I was wrong.  Mine is only 127 lines, including the following comment: .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
[04:36] <rgreening> lol
[04:44] <StevenK> ScottK: You forgot "Abandon all hope ye who read this"
[04:46] <ScottK> StevenK: It's not the reading that will get you.  It's if you think you can change it and make it better.
[04:47] <jmarsden> ScottK: Hmmm, so you're writing the man page for a perfect package... one that cannot be improved? :)
[04:48] <rgreening> hahah
[04:49] <rgreening> ScottK: I just uploaded ~ppa8 of my tac-plus package. Maybe tomorrow you could review (assuming you do not have time tonight)
[04:50] <rgreening> ScottK: I need some help reviewing the depends, to ensure that are tight enough.
[04:53] <ScottK-desktop> jmarsden: That was in the nroff.  That's a twisty, turny maze that touching only leads to tears.  The actual man page content is merely adequate.
[05:30] <ScottK> rgreening: I'll mostly be offline tomorrow.  Dunno.
[05:30] <ScottK> Doesn't seem likely.
[07:15] <stochastic> If a package requires a new mime type file installed, to associate its new extension, is there a proper way to do this in debian/rules?
[07:22] <jmarsden> stochastic: man 8 update-mime may help?  I don't think there is a dh_mimetype script...
[07:22] <fabrice_sp> stochastic, dh_installmime
[07:22] <jmarsden> Ah, there *is* one :)
[07:22] <fabrice_sp> yes :-)
[07:26] <stochastic> hmm, there's no place in the current debian/rules with any dh_install rules etc... can I just shove one in?
[07:27] <simon-o> stochastic: does the package use cdbs?
[07:27] <stochastic> simon-o: people keep asking me this but I'm still a beginner packager and don't understand that term
[07:28] <stochastic> the package I'm trying to update is denemo
[07:29] <simon-o> stochastic: https://wiki.ubuntu.com/PackagingGuide/Howtos/CDBS
[07:29] <stochastic> here's the current debian/rules file: http://pastebin.ubuntu.com/222447/
[07:29] <simon-o> stochastic: that uses cdbs (look at the includes)
[07:30] <stochastic> simon-o: okay thanks.  I'll do some reading
[07:31] <simon-o> stochastic: i think you can just call debhelper in the rules file, because cdbs does nothing else. but I'm quite sure that cdbs can handle mime types
[07:32] <stochastic> simon-o: so just at the bottom of the file run dh_installmime
[07:33] <jmarsden> stochastic: For more general help with packaging and the helpers, etc, see https://wiki.ubuntu.com/PackagingGuide/Complete
[07:34] <simon-o> stochastic: this is what cdbs call in debhelper.mk: dh_installmime -p$(cdbs_curpkg) $(DEB_DH_INSTALLMIME_ARGS)
[07:34] <simon-o> stochastic: so you don't need to do that manually
[07:36] <stochastic> simon-o: wonderful, so all that needs to occur is the mime file needs to exist in the correct place (debian/denemo.mime)
[07:37] <simon-o> stochastic: I think so, just give it a try and see if it gets included in the deb
[08:07] <StevenK> taggart: Whee, it failed due to fallout to a transition we haven't done and Debian has.
[08:07] <StevenK> taggart: (I'm fixing it)
[08:30] <Zhenech> bdrung_, done
[08:31] <Zhenech> bdrung_, do you know why the arc-* gdm themes come up in my xfce "appearance" settings  (where I'd select shiki-foo usually)
[09:39] <slytherin> hyperair: ping
[09:45] <hyperair> slytherin: pong
[09:45] <slytherin> hyperair: did you come up with build.xml for microemu?
[09:49] <hyperair> slytherin: no i didn't.
[09:50] <hyperair> slytherin: i'm considering just leaving it alone actually @_@
[09:54] <slytherin> hyperair: I have come up with with very basic build.xml which will give you midp.jar and cldc.jar. These jars should be sufficient for compilation of remuco client. Do you wish to take the build.xml and work on packaging microemu?
[09:55] <kamaln> Hi..can i discuss ubuntu package development here?
[09:55] <directhex> here is the place
[09:56] <kamaln> directhex: "here is the place"..is it meant for me?
[09:56] <directhex> yes
[09:56] <AnAnt> kamaln: I think so
[09:56] <kamaln> directhex and AnAnt ...ok..thanks..:-)
[09:58] <AnAnt> is everyone @ Debconf ?
[09:58] <hyperair> slytherin: i don't think i know quite enough to do that. perhaps it'd be better if you do the packaging for that.
[09:58] <hyperair> i'm not
[09:59] <directhex> AnAnt, a few people
[09:59] <AnAnt> oh btw debhelper 7.3.4 (currently in experimental) supports ant build system !
[10:00] <slytherin> hyperair: Ok. I will try once I am finished with jmeter. Hopefully by then we will have complete maven2 stack in unstable. :-)
[10:00] <slytherin> AnAnt: I am not interested. I love CDBS. :-P
[10:00] <directhex> slytherin, did you see life on the banshee/ppc bug? seems to be a type conversion problem from sqlite
[10:01] <AnAnt> slytherin: I don't feel comfortable with CDBS
[10:01] <ttx> I don't really like CDBS, but it works very well with ant-based builds :)
[10:01] <kamaln> i am new to Ubuntu packaging...can someone tell me how to get started with it?
[10:01] <Laney> see links in the topic
[10:01] <AnAnt> kamaln: package training logs are nice: https://wiki.ubuntu.com/Packaging/Training/Logs
[10:02] <slytherin> directhex: Was there a comment in the bug? My internet connection was down almost for 2 days.
[10:02] <directhex> slytherin, this is on upstream's bugzilla
[10:02] <slytherin> directhex: let me check.
[10:02] <AnAnt> slytherin: can you confirm a sync request ?
[10:02] <directhex> http://bugzilla.gnome.org/show_bug.cgi?id=547218 - slowest bugzilla evar
[10:03] <directhex> yes, i just said that hanks ubottu
[10:03] <slytherin> AnAnt: I don't have karmic chroot setup at office. Can not confirm until I test build the package.
[10:03] <AnAnt> slytherin: ok
[10:04] <slytherin> AnAnt: let me know which bug. If no one else does I will do it in evening
[10:04] <AnAnt> slytherin: LP 399123
[10:04] <kamaln> AnAnt: but the link that you sent seems to be some chat log..isnt there any simple and quick tutorial?
[10:05] <AnAnt> kamaln: umm, I dont remember, maybe the link in the title ?
[10:06] <kamaln> AnAnt: "link in the title"? what does it mean? Infact I am new to IRC as well..
[10:06] <AnAnt> kamaln: https://wiki.ubuntu.com/MOTU/Contributing
[10:06] <directhex> kamaln, type "/topic" then click some of the links
[10:09] <directhex> slytherin, aha, one of the main banshee contributors has a g4 powebook now
[10:09] <kamaln> typing "/topic " doesnt do anything..
[10:09] <maxb> kamaln: https://wiki.ubuntu.com/MOTU/GettingStarted is probably a good point to start reading
[10:09] <directhex> "Here's the reason :
[10:09] <directhex> DbConnection.Execute ("INSERT ...") is supposed to return the ID of the row that was inserted, but it would always return 0. The value of this id is retrieved through sqlite3_last_insert_rowid : http://www.sqlite.org/c3ref/last_insert_rowid.html
[10:09] <directhex> The value is cast from int64 into int32, which works on x86 but not on PowerPC (big endian ?)."
[10:10] <slytherin> AnAnt: Sorry buddy. I stay away from python apps/libs. You have to look for someone else.
[10:10] <AnAnt> slytherin: no problem
[10:10] <slytherin> directhex: I thought it had something to do with endianness
[10:10] <AnAnt> what happened to packages.ubuntu.com ?
[10:11] <kamaln> maxb: how is this one..seems similar to the link you just recommended..
[10:11] <kamaln> maxb: https://help.ubuntu.com/6.10/ubuntu/packagingguide/C/basic-scratch.html
[10:12] <maxb> Anything meant for 6.10 will be incredibly out of date by this point
[10:13] <maxb> Try here https://wiki.ubuntu.com/PackagingGuide/Basic
[10:13] <bdrung_> Zhenech: the arc-* are only suggestions, so they shouldn't be pulled in.
[10:14] <Zhenech> bdrung_, nah, what I mean is: when they are installed I see them in the xfce config for selection, even when that are gdm themes only which do not work in xfwm
[10:15] <kamaln> maxb: seems good..whats the diff between basic and complete..i think the "complete" one includes "basic" too..
[10:15] <bdrung_> Zhenech: hm, then i have no idea
[10:15] <Zhenech> ok, will have a look myself then
[10:15] <kamaln> maxb: thanks for the link...
[10:29] <bdrung_> Zhenech: thanks for uploading
[10:29] <bdrung_> Zhenech: now the waiting begins again :)
[10:31] <Zhenech> yepp
[10:31] <Zhenech> you have tooo much binary packages :)
[11:26] <slytherin> AnAnt: bddebian gave +1 to monajat, but forgot to actually advocate it.
[11:33] <AnAnt> slytherin: he didn't forget, he didn't know how to do so
[11:33] <AnAnt> slytherin: I think he's not used to the new look of REVU
[11:34] <slytherin> AnAnt: Really? I wonder how could he miss the checkbox right below the comment field.
[11:34] <AnAnt> slytherin: ok, I'll tell him, actually I told him that probably there is a button
[11:36] <AnAnt> geser: thanks
[11:46] <noodles> Hi! Are there any MOTU around who could take a peak at the following for me?
[11:46] <noodles> http://revu.ubuntuwire.com/p/sphinxbase
[11:51] <bdrung_> Zhenech: it's not my fault, that upstream created the themes in so many diffent colors ;)
[11:54] <Zhenech> bdrung_, heh :)
[12:21] <geser> noodles: commented
[12:21] <noodles> geser: Just saw the email. Thank you, I'll get those updated.
[12:22] <noodles> geser: with your last point - I would have thought the pbuilder build would have failed if that had been the case?
[12:24] <geser> noodles: it's not about during build, but about using the libsphinxbase-dev package for building other packages
[12:24] <noodles> Ah ok.
[12:24] <geser> if you try to include ad.h in that other package it will fail as alsa/asoundlib.h (needed by ad.h) can be included
[12:25] <geser> so you have to take care that any users of the -dev package get all of its dependencies (other -dev packages)
[12:26] <noodles> Got it. Great, I'll update the (dev?) dependencies.
[13:28] <dstansby> Has anyone got any idea where is a good place to look if I want to package something for ubuntu?
[13:29] <Laney> do you have any experience with deb-format packaging?
[13:29] <dstansby> Laney: No, but I have been patching stuff in ubuntu for a while if that helps
[13:30] <Laney> well my humble suggestion is to do some smaller changes first
[13:30] <Laney> creating your own package from scratch is fairly complicated and I wouldn't advise it for people without experience
[13:30] <Laney> otherwise there are guides on the wiki
[13:31] <dstansby> Laney: Smaller changes to what?
[13:31] <Laney> fix some existing bugs, get to know how all the pieces fit together
[13:31] <dstansby> Laney: Such as how the files in /debian work?
[13:32] <Laney> yeah
[13:32] <dstansby> I think I'm fairly sure what's going on there, and I have uploaded around 5 patches to ubuntu that have been accepted
[13:33] <Laney> alright, then you do have experience with deb-format packaging :)
[13:33] <Laney> there are some guides on the wiki, and the Debian new maintainers' guide which are helpful
[13:35] <dstansby> I've looked at http://ow.ly/hFSs , but that guide seems awfully specific to 'hello' I'll give it a go though, and see what comes out
[13:36] <Laney> also try "man dh"
[13:36] <Laney> If you really understand what's going on, then there's no magic to creating a new package
[13:36] <directhex> Laney, dh7 isn't magic?
[13:37] <dstansby> I've found the same to be true of patching. Easy when you know how :)
[13:37] <Laney> vim $(which dh) ;)
[13:37] <dstansby> At least there's plenty of [needs-packaging] bugs to choose from
[13:38] <Laney> hm
[13:38] <Laney> I suggest to package something that you actually use, otherwise it's hard to keep motivation
[13:38] <Laney> and we don't need any more unmaintained packages, really
[13:52] <geser> jdong: Hi. re python-repoze.who-plugins: I've read your response. it looks like all reason for the rejection are resolved now. do I need to do something to get it included in Ubuntu?
[13:54] <geser> jdong: sorry, wrong tab-completion
[13:54] <geser> jdstrand: Hi. re python-repoze.who-plugins: I've read your response. it looks like all reason for the rejection are resolved now. do I need to do something to get it included in Ubuntu?
[13:58] <RainCT> OT, anyone got some LaTeX template to create Ubuntu-styled presentations?
[14:05] <jdstrand> geser: just upload it :)
[14:13] <geser> jdstrand: I've reopened bug 396101 for that
[14:13] <geser> crap wrong bug :(
[14:17] <geser> jdstrand: reopened now the correct bug: bug 395437
[14:18] <jdstrand> geser: ok, thanks
[14:37] <slytherin> RainCT: What do you mean by Ubuntu styles presentations?
[15:20] <bddebian> Heya gang
[15:26] <james_w> I don't think documenting repacking in README.Debian is the correct thing is it?
[15:30] <iulian> Hello bddebian.
[15:30] <bddebian> Hi iulian
[15:33] <Zhenech> james_w, in README.source please
[15:33] <james_w> debian/copyright actually
[15:33] <james_w> just looked it up
[15:34] <Zhenech> if thats dfsg-related repackaging prolly
[15:36] <james_w> nope, it appears to suggest if for any repacking
[15:36] <ScottK> Zhenech: The rule used to be document repacking in some README.foo (I don't recall which), but debian/copyright is the place now.
[15:55] <Zhenech> ScottK, debian policy says readme.source, no idea about ubuntu :)
[15:56] <Zhenech> http://www.debian.org/doc/debian-policy/ch-source.html#s-readmesource
[16:01] <ScottK> Hmmm.
[16:02] <ScottK> Debian/Ubuntu are the same in this regard.
[16:05] <ScottK> Zhenech: That's about modifying an existing Debian package, not repacking tarballs.
[16:36] <james_w> highvoltage: the license situation of ltsp-cluster-lbserver is a little unclear
[16:36] <james_w> the only file that has a statement is the external one
[16:36] <james_w> am I missing something?
[16:44] <ScottK> Anyone here involved in the Perl modules team in Debian?
[16:45]  * ScottK needs to package up a new module and is looking for someone to push it into Debian.
[16:45] <DktrKranz> ScottK: nhanlder is
[16:45] <ScottK> DktrKranz: Thanks.
[16:45] <DktrKranz> np
[17:07] <ledina> would be useful (if someone is free) if new exiftool could be sponsored to karmic
[17:07] <ledina> https://bugs.launchpad.net/ubuntu/+source/libimage-exiftool-perl/+bug/399759
[17:08] <Laney> ledina: subscribe the sponsors and it will be looked at
[17:08] <highvoltage> james_w: I'll get back to you on that in a few moments
[17:08] <ledina> thanks
[17:22] <RainCT_> Adri2000 and whoever may care, comments? http://revu.ubuntuwire.com/~rainct/mom.html
[17:25] <ogra> RainCT, awesome ! only one merge left :P
[17:28] <RainCT> lol
[17:28] <ogra> looks cool
[17:37] <kamalnandan> Hi Guys..
[17:48] <juli_> Hello MOTUs. Could someone answer my question, please. There is a package fee with version 1.1-0ubuntu1 in the repo. I want to set up a dependency from my own package on the package fee according to the rule: (>=1.1 && < 2.0). The goal is not to allow a user to use updated version of the fee package (I know it will be updated soon).
[18:00] <kamalnandan> I am new to Ubuntu packaging and was just reading the basic guide..I have a query about a statement in the guide..
[18:01] <kamalnandan> in this link:
[18:01] <kamalnandan> https://wiki.ubuntu.com/PackagingGuide/Basic
[18:01] <kamalnandan> there is this statement:
[18:01] <kamalnandan> For the purpose of this example, we will also compare our package (hello) to one that is already packaged in the Ubuntu repository (called hello-debhelper). For now, we will place it in the ubuntu directory so we can look at it later. This will unpack the source:
[18:01] <kamalnandan> in the first few lines from top..
[18:02] <kamalnandan> I want to know where do we need to create the directory Ubuntu?
[18:02] <bluekuja> kamalnandan, sorry, where do you read in this statement that you need to create that dir?
[18:03] <bluekuja> I mean the "ubuntu" one
[18:03] <bluekuja> kamalnandan, I see a "in the Ubuntu repository"
[18:03] <bluekuja> kamalnandan, which is something different
[18:04] <kamalnandan> not in this statement; if you follow the link that I have mentioned before that; there is an expression "mkdir ubuntu"
[18:04] <kamalnandan> bluekuja: https://wiki.ubuntu.com/PackagingGuide/Basic
[18:05] <bluekuja> kamalnandan, it says they placed it for later use
[18:05] <bluekuja> kamalnandan, you could have called that dir kamalnandan too
[18:06] <highvoltage> james_w: I just spoke to my mentor on the package, he also believes that it is clear that the rest of the package is gpl-2
[18:06] <bluekuja> kamalnandan, in the guide, you just have an example compared to another one available on the repo
[18:06] <highvoltage> james_w: I'm more than happy to make improvements if you have any suggestions/examples
[18:06] <james_w> highvoltage: gpl-2 or gpl-2+?
[18:06] <bluekuja> highvoltage, do you have karmic?
[18:06] <kamalnandan> ok..thats fine..but where do we create that directory? inside "hello" directory or parallel to "hello" directory..?
[18:06] <kamalnandan> infact, i want to learn from a basic example first..
[18:07] <james_w> there's the GPL2 embedded, and the only statement is in a file that is explicitly called out as being different
[18:07] <james_w> so it's not clear
[18:07] <bluekuja> kamalnandan, in the example, they are comparing hello package to hello-debhelper, right?
[18:07] <james_w> I have no problem believing that this is all supposed to be GPL-2+, but it's not an area where you want ambiguity
[18:07] <james_w> highvoltage: ^
[18:07] <highvoltage> james_w: got it, will sort it out, thanks
[18:08] <bluekuja> kamalnandan, so they first get hello source files on one dir and then hello-debhelper source files in another
[18:08] <bluekuja> so you can understand the difference between them
[18:08] <james_w> highvoltage: thanks
[18:08] <bluekuja> it's an example against another one to let you understand it better
[18:09] <kamalnandan> bluekuja: so how should i go abt it; its getting quite confusing to me..
[18:09] <kamalnandan> the things are not really so clear as it seems..
[18:09] <bluekuja> kamalnandan, what do you wanna do?
[18:10] <kamalnandan> I am learning to create a bsic ubuntu package; and I want to learn that by following a basic example..
[18:11] <bluekuja> kamalnandan, wget http://ftp.gnu.org/gnu/hello/hello-2.4.tar.gz
[18:12] <bluekuja> kamalnandan, get the source, unpack it
[18:12] <bluekuja> kamalnandan, get into your working dir
[18:12] <bluekuja> kamalnandan, run dh_make and start finding out what the "debian" dir is
[18:12] <bluekuja> which files you can find in it
[18:12] <bluekuja> how they work
[18:13] <kamalnandan> bluekuja: I have already done the 1st three steps..
[18:13] <kamalnandan> bluekuja: thanks for the help you are providing me..
[18:13] <bluekuja> kamalnandan, np
[18:14] <bluekuja> kamalnandan, if u are into your working dir, dh_make it
[18:15] <kamalnandan> bluekuja: what i did is: I created a directory called "hello_prj", inside my home dir; then I got inside the dirctory "hello_prj"
[18:15] <kamalnandan> and then did "wget hello-2.4.tar.gz"
[18:16] <kamalnandan> then unpacked that
[18:17] <bluekuja> then?
[18:17] <kamalnandan> now where do i need to do dh_make? inside directory "hello_prj", or in the parent dir of "hello_prj"
[18:17] <bluekuja> into source files
[18:17] <bluekuja> cd hello-2.4
[18:17] <bluekuja> and dh_make it
[18:18] <kamalnandan> ok..i need to get into hello-2.4 and then do dh_make..if i am getting it right..
[18:18] <bluekuja> yep
[18:20] <kamalnandan> infact, it is asking for "hello_2.4.orig.tar.gz"..should I make a copy of that immediately inside "hello_prj" i.e. parallel to "hello-2.4.tar.gz"
[18:21] <bluekuja> kamalnandan, rename it to orig
[18:22] <bluekuja> kamalnandan, don't need to create two of them
[18:22] <bluekuja> kamalnandan, rename hello-2.4.tar.gz to what dh_make asks you
[18:24] <kamalnandan> done that..and then moved to hello-2.4 and ran "dh_make -e kamal.nandan@gmail.com"; it created a folder called debian
[18:24] <kamalnandan> inside the folder "debian" there are lots of files..
[18:25] <kamalnandan> the packaging guide asks me to remove all the *.ex or *.EX files..
[18:26] <kamalnandan> because the "Hello" package is not so complicated..
[18:26] <bluekuja> yep
[18:26] <kamalnandan> I am going ahead to do so..
[18:28] <kamalnandan> the guide also telle me to delete all other files too apart from the follwing:
[18:29] <kamalnandan> i.e. the statement says:
[18:29] <kamalnandan> At this point, you should have only changelog, compat, control, copyright, and rules files in the debian directory.
[18:29] <kamalnandan> so, I am going to remove all the other files apart from the ones mentioned above..
[18:29] <bluekuja> yeah, in this case, remove them
[18:30] <bluekuja> but remember you don't have to do it everytime
[18:30] <bluekuja> some other packages may need other maint scripts
[18:31] <kamalnandan> bluekuja: yes, i understand, for this very packaging only I am removing the other files..once I have a basic idea of the basic packaging, then I will feel more confident of going for advanced ones...:-)
[18:32] <bluekuja> kamalnandan, remember that you won't alwais package something from the beginning
[18:33] <bluekuja> kamalnandan, I mean in the future, if you wanna improve, you'll have to work on some packages that got packaged by someone else
[18:33] <bluekuja> kamalnandan, what you are doing now, it's what you should do with NEW packages only
[18:34] <bluekuja> kamalnandan, but anyway that's a good way to start learning
[18:35] <bluekuja> kamalnandan, ask to get into the mentoring program
[18:36] <bluekuja> when you improve a little bit more
[18:36] <kamalnandan> oh..ok...infact, i have been assigned to create an ubuntu package for a big project; the red hat package of which already exists...but when I sat down to work on that packaging, it appeared quite cryptic to me; so i thought of learning a very basic packaging first so that I can get to know the basics and then I can build upon that..
[18:37] <kamalnandan> bluekuja: whats a mentoring program?
[18:37] <bluekuja> kamalnandan, actually they will assign u a mentor
[18:37] <bluekuja> that will help you fixing your packaging problems
[18:37] <bluekuja> plus he will sponsor stuff for you
[18:38] <kamalnandan> ok..so whom should I contact for this?
[18:38] <bluekuja> but if you gonna do one package then leave it's pretty bad
[18:38] <kamalnandan> sounds great..
[18:38] <bluekuja> kamalnandan, actually the mentoring program is for ppl who wanna learn and stay into the ubuntu community
[18:39] <AnAnt> Hello, guile-1.8 is in main, right ?
[18:39] <kamalnandan> ok..whats expected from a a mentee..?
[18:39] <bluekuja> kamalnandan, you first need to know basic rules for packaging
[18:39] <bluekuja> kamalnandan, you need to have a little more experience
[18:39] <kamalnandan> ok..
[18:40] <bluekuja> kamalnandan, then when you know basic stuff ask for a mentor
[18:40] <bluekuja> only if you gonna stay
[18:40] <bluekuja> around and not leaving after having that package in
[18:41] <kamalnandan> ok..
[18:43] <kamalnandan> what am i supposed to do after that; infact  I want to know what is expected froma mentee after he/she has learnt or has been guided by a mentor..? should the mentee provide mentoring to other people in future..?
[18:43] <slytherin> bddebian: You put +1 for monajat on revu. Can you please add your advocation to it?
[18:44] <AnAnt> bddebian: oh, you're here !
[18:44] <bluekuja> kamalnandan, if you are good, you will be asked to become an ubuntu developer
[18:44] <slytherin> geser: got some time for review?
[18:44] <AnAnt> I didn't know that there is mentorship in Ubuntu ?
[18:45] <bluekuja> AnAnt, there is
[18:45] <AnAnt> since when ?
[18:45] <bluekuja> AnAnt, quite near two years
[18:45] <kamalnandan> what kind of developer? package developer..or some other stuff like C/C++ or shell/python/perl scripting developer..?
[18:45] <bluekuja> kamalnandan, package developer
[18:46] <bluekuja> kamalnandan, but you'll have to know some scripting stuff
[18:49] <pfein> hi, I'm overseeing a small ubuntu cluster & I'm trying to package everything (including in house code) as .debs
[18:49] <kamalnandan> bluekuja: ok..thats a good idea..infact the current packaging that I am doing is also for an open src project..
[18:49] <pfein> we're a python shop, and have dependencies on some setuptools/easy_install packages that aren't in ubuntu
[18:49] <pfein> what's the recommended way for .debifying such things?
[18:50] <bluekuja> kamalnandan, g8
[18:50] <kamalnandan> will just be back...a phone call..
[18:51] <bddebian> slytherin, AnAnt: I don't have that checkbox on REVU
[18:51] <slytherin> bddebian: You are MOTU, right?
[18:51] <bddebian> afaik, I still am
[18:52] <bddebian> Maybe they finally kicked my worthless ass out :)
[18:52] <slytherin> bddebian: Then I am wondering why you don't see that checkbox. If you are sure you are still MOTU, then ask revu hackers to look into it.
[19:29] <slytherin> persia: got some time for review?
[20:02] <bdrung_> Zhenech: wow, that was fast. ;)
[20:03] <kamalnandan> bluekuja: thanks for your help...am logging off now..its 12.35 am here...may catch you again tomorrow...:-)
[20:04] <kamalnandan> bye for now..
[20:04] <bluekuja> cya
[20:04] <bluekuja> and np
[20:04] <bluekuja> have
[20:04] <bluekuja> fun
[20:04] <kamalnandan> thanks & same to you..:-)
[20:04] <bluekuja> ;)
[20:05] <kamalnandan> :-)...
[20:08] <norsetto> if any kind soul has nothing better to do, please check this out: http://revu.ubuntuwire.com/details.py?upid=6421
[20:20] <arand> I'm trying to wrap my head around some packaging, so I have the .dsc .orig.tar.gz and diff.gz how do I make the .deb out of it? Have tried dpkg-source -b, dpkg-source -x && renaming /debian/DEBIAN && dpkg-deb -b but no luck so far... _?_
[20:29] <Zhenech> bdrung_, well, old new packages are usually faster then new new :)
[20:32] <Elbrus> arand: after dpkg-source -x you have several options. I always use pdebuild, but I think that is a little bit involved. I think if you run "debian/rules binary" in the source dir your fine.
[20:33] <Elbrus> reading the dpkg-source man I would also say that -b AFTER the -x should do the trick
[20:33] <Elbrus> oh, no, that is the source package...
[20:33] <Elbrus> never mind
[20:34] <azeem> arand: use dpkg-buildpackage or debuild to build .debs
[20:34] <azeem> dpkg-deb and dpkg-source are low-level tools
[20:34] <bdrung_> Zhenech: how fast must it be, if the packages are some years old :)
[20:35] <arand> azeem: ok
[20:37] <bluekuja> arand, dpkg-source -x them
[20:37] <bluekuja> arand, to extract the working folder
[20:37] <bluekuja> arand, then dpkg-buildpackage for the .deb
[20:38] <bluekuja> arand, of if u use pbuilder, use it on the .dsc file
[20:38] <bluekuja> you have
[20:43] <Zhenech> bdrung_, longer *gg*
[20:47] <bannaN> Anyone here? I was wondering what sort of skill level, you'll need to have to contribute to the ubuntu development? How much time you have to put in, and whats the requirements in general? Could someone who has some knowledge about this please pm me, would really appriciate it :)
[20:48] <bluekuja> bannaN, you need to be good packaging-side plus knowing a bit of any language (bash, python, whatever) will be help you
[20:49] <bluekuja> bannaN, about the time you have to spend...depends...
[20:49] <bluekuja> bannaN, usually packaging takes a lot of time
[20:49] <bluekuja> bannaN, and well you need to prove you know packaging tools
[20:50] <bluekuja> bannaN, how they works, how can you use them
[20:51] <bluekuja> bannaN, but I guess we have a lot of wiki pages about it
[20:51] <bluekuja> bannaN, get to http://wiki.ubuntu.com/MOTU
[20:51] <bluekuja> bannaN, and you'll find what you need
[20:52] <bannaN> hm, packaging isnt my strongest field, but i have som programming experience
[20:54] <bluekuja> bannaN, if you wanna get started with packaging, try taking a look at the packaging guide
[20:54] <bluekuja> bannaN, and any other MOTU wiki page
[20:55] <bannaN> will do
[21:08] <Laney> anyone have any recommendations for software to run a local repo?
[21:15] <fabrice_sp> Hi. I'm trying to fix a FTBFS of vips (cdbs + autotools), and I'm not able to get configure use dist-package, even after aclocal/autoconf/automake. Any clue?
[21:16] <fabrice_sp> this is the line that I'm trying to fix: checking for python extension module directory... ${exec_prefix}/lib/python2.6/site-packages
[21:29] <mrooney> Is there any way or standard to list packages necessary for running the application tests?
[21:34] <maxb> Laney: for anything complex, reprepro. For something trivial just to inject a few packages into a local pbuilder, https://code.launchpad.net/~maxb/+junk/apt-generate
[21:39] <mzz> ooh, thanks, I bet that answers a question I was going to ask later :)
[21:42]  * maxb has far too many subtley different flavours of that code
[22:02] <gaspa> geser, Laney: shouldn't we request a sync for ocaml 3.11.1-somewhat?
[22:03] <Laney> there are issues there
[22:04] <gaspa> Laney: any pointers?
[22:05] <Laney> see u-d-d
[22:05] <Laney> also why do you think I'm interested in ocaml ¬_¬
[22:06] <gaspa> :) because of your reply to u-d-d ? :)
[22:07] <fabrice_sp> just in case someone is interested: I've been able to get the correct python path by adding --exec_prefix=/usr to configure call (needed by automake to detect correct path) and running automake/autoconf/aclocal . Now, I have  to do the patch...
[22:08] <fta> are H.264 codecs considered acceptable for main/universe? or are they for multiverse?
[22:08] <Laney> I'm just a generally helpful chap
[22:42] <Adri2000> RainCT: looks good :)
[23:04] <RoAkSoAx> Hey guys is it possible to request a sync but at the same time to make a change, so that sync+change are done in one upload?
[23:06] <bluekuja> RoAkSoAx, I guess you're missing what a sync is then
[23:07] <soren> RoAkSoAx: If you want to make a change, you just upload the new version. No need to sync the vanilla package from Debian first and then make the changes.
[23:09] <bluekuja> soren, depends from what kind of changes debian has ready
[23:10] <bluekuja> soren, usually it's good to not do useless changes preventing to merge them
[23:10] <RoAkSoAx> bluekuja, soren . I've dropped all the changes in Ubuntu since they are now included upstream, however I still need to make a change to the .install file
[23:10] <soren> bluekuja: Eh?
[23:11] <soren> RoAkSoAx: Changes are changes.
[23:11] <RoAkSoAx> so it would not actually be a merge, just a sync, but applying a change
[23:11] <soren> RoAkSoAx: That's what a merge is :)
[23:12] <RoAkSoAx> soren, right but I've been explained before that if there are *no remaining changes* and I'm introducing new changes, it would first sync, and then apply my new changes
[23:12] <bluekuja> soren, my point was to not change the package for an useless change
[23:12] <bluekuja> soren, but I wanted RoAkSoAx to keep in touch with debian
[23:13] <bluekuja> RoAkSoAx, yeah
[23:13] <bluekuja> RoAkSoAx, ask the sync
[23:13] <bluekuja> and then do your changes
[23:14] <soren> ?!? When did we start doing this? What's the point?
[23:14] <DktrKranz> what's the point asking for a sync, then apply changes again?
[23:14] <bluekuja> DktrKranz, he wanted to apply new changes
[23:14] <soren> So?
[23:15] <bluekuja> new debian package included upstream changes
[23:15] <RoAkSoAx> right but i've told before that I could do something like:
[23:15] <RoAkSoAx> Sync from debian unstable (LP: #XXXXX)
[23:15] <RoAkSoAx> debian/quodlibet-ext.install: Change from '/site-packages/' to '/*-packages/'.
[23:15] <DktrKranz> proceed as you are trying to merge, instead of "merge from debian" use something like "resync from Debian"
[23:15] <DktrKranz> and then add a new bullet point describing change you're going to make
[23:15] <Ampelbein> RoAkSoAx: thats a merge.
[23:15] <Ampelbein> RoAkSoAx: you take the debian packaging and change what's needed.
[23:16] <DktrKranz> that way you can state no ubuntu changes left to be merged, but a new one to be made
[23:16] <bluekuja> soren, he said debian introduced the new upstream release
[23:16] <bluekuja> soren, so ubuntu remaining changes can be deleted right?
[23:16] <soren> bluekuja: Depends.
[23:17] <bluekuja> soren, yes, but if for istance they can be dropped
[23:17] <soren> bluekuja: Yes..
[23:17] <bluekuja> soren, he wants to add a new change to the package
[23:17] <DktrKranz> bluekuja, no need to sync. you waste buildd and archive-administrator time jus to process something it won't fit ubuntu
[23:17] <soren> bluekuja: Yes...
[23:18] <bluekuja> soren, what do you do?
[23:18] <bluekuja> DktrKranz, and what about debian changes then?
[23:18] <soren> bluekuja: If they can all be dropped and I don't have any other changes? I'd sync. If I have other changes, I'll just apply them and upload.
[23:18] <bluekuja> soren, apply them where?
[23:18] <DktrKranz> debian changes come in as a normal merge
[23:18] <bluekuja> soren, to debian package or to latest ubuntu revision?
[23:19] <bluekuja> DktrKranz, yeah, so he do the change
[23:19] <bluekuja> DktrKranz, and then resync with debian
[23:19] <soren> bluekuja: That will lose the changes!
[23:19] <bluekuja> soren, don't misunderstand me
[23:19] <DktrKranz> bluekuja, if Debian includes *all* ubuntu changes, including the new one, agreed
[23:20] <soren> Sync with Debian == Take whatever is in Debian and put it as is in to Ubuntu.
[23:20] <bluekuja> soren, I was talking about what DktrKranz said before
 proceed as you are trying to merge, instead of "merge from debian" use something like "resync from Debian"
[23:20] <DktrKranz> but if we have to add another one on top of the current Debian package, just take Debian package, apply new ubuntu change and then upload
[23:20] <DktrKranz> no need to sync
[23:21] <bluekuja> DktrKranz, exactly
[23:21] <bluekuja> DktrKranz, you get latest debian, apply ubuntu changes
[23:21] <bluekuja> and done
[23:21] <soren> bluekuja: Yes! That's what a merge is.
[23:21] <soren> bluekuja: Syncing the pristine debian package first is pointless.
[23:22] <bluekuja> soren, I know
[23:22] <bluekuja> soren, I didnt explain what I wanted in the right way
[23:22] <bluekuja> ^^
[23:22] <RoAkSoAx> OK so changelog would be something like: * Sync from debian unstable (LP: #XXXXX)
[23:22] <RoAkSoAx> * debian/quodlibet-ext.install: Change from '/site-packages/' to '/*-packages/'.
[23:23] <bluekuja> RoAkSoAx, nope
[23:23] <soren> RoAkSoAx: What would that LP ref be?
[23:23] <bluekuja> RoAkSoAx, as we stated now it's a merge
[23:23] <bluekuja> soren, LP bug for sponsors
[23:23] <RoAkSoAx> soren, Yes I would be filling a bug to request sponsorship
[23:24] <RoAkSoAx> that's what I was actually asking
[23:24] <soren> Oh.
[23:24] <RoAkSoAx> If I should request a sync bug, and apply my change
[23:25] <bluekuja> soren, what I understood from you, was taking the ubuntu package, apply the change, then merge again
[23:25] <bluekuja> soren, so I was a bit confused of that
[23:26] <bluekuja> e.g doing things two times
[23:26] <soren> Well... That's not what I meant at all.
[23:26] <bluekuja> yeah, I understood it wrong
[23:26] <soren> Alright :)
[23:26] <bluekuja> soren, sorry ;)
[23:27] <RoAkSoAx> ok so should I just file a sync bug, and provide my debdiff with the change right?
[23:27] <bluekuja> RoAkSoAx, a merge bug
[23:27]  * soren wanders off
[23:28] <RoAkSoAx> so changelog would be:
[23:28] <RoAkSoAx> * Merge from debian unstable (LP: #), no remaining changes.
[23:28] <RoAkSoAx> * debian/quodlibet-ext.install: Change from '/site-packages/' to '/*-packages/'.
[23:28] <bluekuja> RoAkSoAx, first of all explain why remaining changes can be dropped
[23:28] <bluekuja> RoAkSoAx, than explain your change
[23:29] <taggart> StevenK: hey you included fossology in karmic yesterday, but I am wondering why I am seeing 1.0.0-2 on packages.u.c instead of 1.1.0-1
[23:29] <DktrKranz> RoAkSoAx, in such a case, I usually adopt this form of changelog entry: https://bugs.launchpad.net/ubuntu/+source/starplot/+bug/197033/comments/6
[23:30] <RoAkSoAx> DktrKranz, That's exactly what I wanted to know then :).
[23:30] <RoAkSoAx> thanks a lot to all of you guys
[23:30] <nellery> taggart: p.u.c probably wasn't updated yet, but it's at http://launchpad.net/ubuntu/+source/fossology
[23:31] <DktrKranz> nice times when I sponsored sebner ;)
[23:31] <RoAkSoAx> DktrKranz, btw, thanks for reviewing lekhonee package, I've made the changes and posted my doubts on how to proceed on revu.ubuntuwire.com :)
[23:31] <DktrKranz> cool
[23:31] <bluekuja> RoAkSoAx, np
[23:31] <bluekuja> ;)
[23:32] <RoAkSoAx> bluekuja, :)
[23:33] <DktrKranz> RoAkSoAx,  remember me to look again, with the hope that the annoying bug I've just discovered in cdbs is fixed in the meantime
[23:33] <RoAkSoAx> DktrKranz, will do :)
[23:36] <taggart> nellery: sweet thanks
[23:59] <jayteeuk> Good evening all.  Just.