[00:12] <Andphe> hi, how long can take bzr import-dsc ?
[00:12] <Andphe> hours ?
[02:15] <vorian> cody-somerville: nice job on the multiple ppa blog post.
[02:16] <vorian> it reduced my dput 3mb
[02:30] <ausimage> vorian: what do you know of conspiracy to modify distutils and break packages that use install files build mulitiple packages :/
[02:31]  * ausimage think vorian uses python and might have a few answers for him :S
[02:32] <popey> directhex: dont suppose you can put a space after those urls in comment 3? :) they get added to the end of the url and result in 404s in some crappy environments
[02:32] <popey> (the end bracket gets added I mean)
[02:33] <ausimage> any python packages around?
[02:34] <ausimage> er packager
[02:34] <StevenK> They don't tend to sit on IRC
[02:34] <ausimage> :S
[02:34] <StevenK> Python packages, that is
[02:34] <ausimage> StevenK: I am looking to get some help with my python package....
[02:35] <ausimage> http://revu.ubuntuwire.com/details.py?upid=6026
[02:35] <ausimage> supposedly I seem to find the sledge hammers to make my packages work... I need help to find the right dentle pick instead :)
[02:37] <ausimage> I would greatly appreciate some advice on best practices for my soovee package
[04:40] <ScottK> JontheEchidna and  nixternal: New packages are fine for backports.
[05:02] <Laibsch> Hi
[05:02] <persia> hey Laibsch
[05:02] <Laibsch> I have a script that I'm packaging.  On the host it is installed without the x bit for execution
[05:03] <Laibsch> How do I get the package built with the script being marked as executable?
[05:03] <persia> Laibsch, To which directory is the script installed?
[05:03] <Laibsch> /usr/bin
[05:05] <persia> and it's marked executable in the source package?
[05:12] <Laibsch> actually, it's not part of orig.tar.gz
[05:12] <Laibsch> it is marked executable in the unpacked source directory
[05:13] <persia> Laibsch, Ah.  diff.gz can't represent the executable bit (or masks it, or something).  chmod+x it in rules.
[05:14] <persia> Er, hrm.  No.  dh_fixperms is supposed to fix that.
[05:15] <persia> So, make sure you're running dh_fixperms, and if you are, check your logs carefully (DH_VERBOSE might help)
[05:15] <Laibsch> OK, thank you
[05:57] <\sh> moins
[06:08] <fabrice_sp_> moins \sh
[06:11] <fabrice_sp> ScottK, can I take the shogun merge?
[06:11] <ScottK> fabrice_sp: Yes.  Please.
[06:11] <fabrice_sp> thanks ;-)
[06:12] <\sh> zend-framework_1.8.3-0ubuntu1 just uploaded...
[06:12] <persia> \sh, You know zend.  Do you want to make a call on how to make gaphor work again?
[06:12] <persia> Should it not depend on zend?
[06:13] <\sh> gaphor? you mean this http://gaphor.sourceforge.net/ gaphor?
[06:14] <persia> I do.  It's a package that works about once per three or four Ubuntu releases.
[06:14] <StevenK> So it's doing better than PHP, then
[06:14] <persia> Err.  Nevermind.  Ignore that.
[06:15] <\sh> persia: I'm wondering what gaphor should do with Zend?
[06:15]  * persia confused "zend" and "zope"
[06:15] <\sh> hehe...
[06:16] <\sh> persia: but sounds like it depends on a working zope stack in ubuntu then ... (ajmitch could help here...remembering he did some zope work in the past)
[06:16] <\sh> StevenK: hmmm? php worked always...(not regarding the quality of php, though)
[06:17] <persia> \sh, well, some say it should, and some say it shouldn't, and I haven't used it since dapper, so my interest level in making it work is waning.
[06:18] <dholbach> good morning
[06:18] <fabrice_sp> good morning dholbach
[06:18] <\sh> moins dholbach ... looks like that most .de people are up early ;)
[06:18] <dholbach> hiya \sh, hey fabrice_sp
[06:22] <\sh> persia: looks like it only uses zope.component (pre-deps: zope.interface, zope.event)...dunno if we do have them as single package in our archives
[06:27] <persia> \sh, Don't worry about it.  Maybe ajmitch remembers enough zope.  Maybe someone will write a UML tool that doesn't require nearly so much coddling.
[06:27] <ajmitch> what are we talking about here?
[06:27] <\sh> persia: umbrello (kde)
[06:27] <persia> ajmitch, That gaphor worked in hoary, dapper, and gutsy, and it might be nice to make it work for karmic.
[06:28] <persia> But that making it work requires untangling the relationship to zope, messing with python transitions, etc.
[06:28] <ajmitch> persia: OK, I can't say I've really heard of it :)
[06:28] <ajmitch> sounds like a bundle of fun
[06:28] <persia> Yeah.  Packages that only rarely work don't tend to be so popular :)
[06:29] <ajmitch> what's its current state of breakage?
[06:29] <persia> I used it in hoary, breezy (until it broke), and dapper, and found it useful then, but there may be better alternatives now.
[06:29] <persia> Last I knew it was having issues with python versions related to zope, and having discussions as to whether the zope bits belonged how they were.
[06:30] <ajmitch> I'm installing it now & it has a dependency on zope3
[06:30] <ajmitch> which is interesting :)
[06:30] <persia> (there's a few bugs that explain the situation in more detail, but I can't say I've been great about the bugmail for the past year or so)
[06:30] <\sh> ajmitch: as said...it needs zope.component
[06:30] <persia> And it installs some zope extensions, I think.
[06:31] <\sh> (as stated on the homepage and hopefully with the correct infos)
[06:31]  * ajmitch sees no mention of zope on the new homepage
[06:32] <ajmitch> just that it'll fetch dependencies as needed when you install with setuptools
[06:32] <\sh> ajmitch: http://gaphor.devjavu.com/wiki/Tech last headline
[06:32] <ajmitch> well the version in karmic at least loads for me
[06:33] <persia> Cool!  I wouldn't have expected it to work, given some of the comments in some of the bugs in late jaunty timeframe.
[06:36] <ajmitch> It should be updated to the latest version at least
[06:36] <persia> The person in Debian who has been trying not to maintain it for the past while tends to be good about doing stuff, but probably wouldn't complain if someone else wanted to take it over.
[06:37] <ajmitch> I doubt I'd use it enough to want to take over maintenance
[06:37] <persia> That seems to be a general consensus :)
[06:38] <ajmitch> it's a pity that zope eggs aren't packaged separately in debian at the moment for this
[07:03] <\sh> directhex: good post about mono...congrats
[07:17] <ScottK> directhex: I'm a little curious about the 100 times faster than Python comment though?
[07:18]  * persia assumed that was in the "some workloads" category, in the same way that shell scripts are faster than C for some workloads.
[07:18] <persia> (without any specific intended mapping as to which language would be C and which would be shell scripts)
[07:19] <ScottK> Yes, it was 'some'.
[07:19] <ScottK> I'm curious about the circumstances where that would pertain.
[07:47] <dholbach> persia, geser, soren, jpds, nhandler, nixternal: who of you is around? :)
[07:48]  * persia is about 50% present
[07:49] <dholbach> that's a good start :)
[07:54] <dholbach> geser, soren, jpds, nhandler, nixternal: anybody else? :-)
[07:55] <slytherin> what is the poll about?
[07:56] <persia> slytherin, We have a meeting in about 4 minutes.
[07:57] <slytherin> in #ubuntu-meeting?
[07:57] <nixternal> yo yo
[07:57] <dholbach> hey nixternal!
[07:57] <slytherin> Is it MOTU meeting or MC meating?
[07:57] <dholbach> MC
[07:57]  * dholbach hugs nixternal and persia
[07:57] <nixternal> hehe
[07:58] <nixternal> I just finished watching a movie :)
[07:58] <dholbach> perfect fit then :)
[07:59]  * dholbach tries texting soren
[08:00] <soren> I'm here.
[08:01] <soren> Just now.
[08:01] <soren> :)
[08:01] <dholbach> awesome
[08:17] <\sh> nixternal: kmail was always crashing since kde3 times...so it's kdes crap not kubuntus or opensuses...I should write something on your blog ;)
[08:18] <nixternal> hehe
[08:18] <nixternal> I had a long drawn up response, but I went with the more PC/CoC friendly version with humor and sarcasm :)
[08:19] <\sh> nixternal: that's exactly what I did this morning when I read jriddells post about the kde hire of C. ;) I thought I appoint you for that position ;)
[08:20] <nixternal> you and everyone else...I want to know more about it
[08:20] <nixternal> not going to waste time if it is more x, opengl type stuff that I have 0 clue about
[08:20] <\sh> nixternal: imho more the ubuntu one client for kde?
[08:20] <nixternal> if it is general kde love, then I am down, but I think someone has it out for me anyways ;)
[08:20] <\sh> s/kde/qt+kde/
[08:21] <nixternal> they already have someone working on it I thought
[08:21] <\sh> nixternal: regarding online services
[08:21] <nixternal> I was looking through the server/cloud computing thing but it seems it is more server than anything, and my cloud experience is all with storage anyways
[08:21] <nixternal> don't know if i really want to develop any more on the cloud, but i won't say no :)
[08:23] <enyc> security updates in universe -- how does tnis work?   debian have patched their 'nsd' pacakge.... but this hasn't filtered through into ubuntu -- whats' going on?   is somebody supposed to post a bug?  does something happen automatically to notify tha maintaner that hasn't happened?
[08:23] <\sh> nixternal: money money money...must be funny...in the rich man's world ;)
[08:24] <nixternal> I have 0 money
[08:24] <nixternal> been jobless since february, the job market here sucks, but I did just get an offer
[08:24] <nixternal> Microsoft!
[08:26] <enyc> please will someboy point me in the right directon ??
[08:26] <\sh> enyc: file a bug with the CVE, eventually add the patch from debian to the report, add debians bug report to it, and provide a debdiff , please read https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures :)
[08:27] <\sh> nixternal: why not MS? They soled 200Mio SLES licenses ,-)
[08:27] <\sh> s/soled/sold/
[08:27] <nixternal> MS is the largest distributor and support of Linux based solutions too
[08:27] <directhex> nixternal, you've been running windows for ages haven't you? :p
[08:27] <nixternal> haha
[08:28] <nixternal> actually no
[08:28] <nixternal> I haven't run windows since around 1998
[08:28] <\sh> "MS wants YOU ! Go get the job, Cowboy"
[08:29] <vorian> i'd love a job like that, if it didn't have a crazy contract
[08:29]  * vorian is content, however, to run a farm store
[08:30] <persia> vorian, The nice thing about your job is that it doesn't occupy the same part of your brain as this stuff :)
[08:30] <\sh> there is always a crazy contract..."your salary is XXXX Cents, for 40h per week, and all overtime, too"
[08:30] <vorian> persia: exactly!
[08:33] <e-jat> nixternal: go go go MS go :)
[08:33] <e-jat> opsss my bad ..
[08:35] <geser> dholbach: sorry, totally forgot about the meeting :(
[08:36] <dholbach> geser: no worries - you're only half an hour late
[08:38] <al-maisan> Good morning, how does one add annotations to the entries in https://merges.ubuntu.com/universe.html#updated ?
[08:38] <al-maisan> I have merged the fbreader package and added a LP bug (request for sponsorship) and would like to make that fact known by annotating the fbreader entry in the list
[08:39] <\sh> al-maisan: at the end of the line the cursor changes into an "textinput" cursor...just click there...and add your text
[08:40] <al-maisan> \sh: "at the end of the line" of what ..?
[08:41] <dholbach> al-maisan: just click or doubleclick on a field in the comment column
[08:41] <\sh> al-maisan: on merges.ubuntu.com -> you'll find the package fbreader on the list...you move your mouse to the right side (comment column)
[08:42] <dholbach> it's not directly obvious if you're looking at the page :)
[08:42] <dholbach> looks like it's read-only :)
[08:42] <al-maisan> ah, OK, thanks!
[08:45] <\sh> thekorn: ping what do you think of that snippet instead of the old working Config()._get() methods in leonov?
[08:47] <\sh> thekorn: having all sort of configuration stuff as class attributes (<section>_<option> syntax)
[08:47] <thekorn> \sh, sorry, but which snippet?
[08:47] <\sh> thekorn: sorry...forgot the link: http://paste.ubuntu.com/194112/
[08:49]  * \sh needs a coffee...tea is not enough this morning
[08:51] <thekorn> \sh, I personaly don't like this syntax, why not just using the get method of the ConfigParser()
[08:51] <thekorn> \sh, what about discussing this in good old #leonov ?
[08:53] <\sh> thekorn: right :)
[08:54] <nixternal> it is going on 03:00 here, still need to take the garbage out and get to bed...I am bushed
[09:32] <dholbach> porthose, nxvl: do you know about e-jat's mentoring request?
[09:34] <e-jat> or should i resubmit ?
[09:44] <iulian> dholbach: Thanks for looking at ndoc.  This patch should apply cleanly now: http://launchpadlibrarian.net/27810993/debdiff
[09:45] <dholbach> iulian: cool, I'll take a look later on
[09:45] <iulian> dholbach: OK, thanks.
[09:59] <jpds> dholbach: Eeek, missed it by a few minutes.
[10:20] <dholbach> jpds: no worries, it's all good
[10:35] <andrew_sayers> #ubuntu-mozillateam
[10:35]  * andrew_sayers can't type today
[11:08] <LucidFox> I'm updating a package in Ubuntu that's orphaned in Debian - would it make sense to make it lintian-clean?
[11:10] <persia> LucidFox, Not really, but it might make sense to do a Debian QA team upload that was (and the QA team is nearly always happy to have help)
[11:14] <slytherin> LucidFox: it would make sense if you plan to push the package to Debian soon.
[11:20] <james_w> oops
[11:21] <james_w> forgot to comment on nellery's application, glad that he made it anyway :-)
[11:28] <soc> hi
[11:29] <soc> does anyone have an idea, when texlive will be updated?
[11:30] <soc> version 2007 is still in the repos, but version 2008 is available since september 2008 ... i guess we could update to texlive 2009 now ...
[11:31] <Laney> soc:  you should contact the debian tex maintainers
[11:32] <soc> mh ok
[11:32] <soc> so it's their decision if we will get a newer version?
[11:33] <persia> soc, Rather, it's our decison, and we defer to their greater expertise.
[11:35] <Laney> I would imagine that this update has some fiddly bits that require intimate familiarity with the package, and that group is where you will find this familiarity.
[11:35] <Laney> So unless someone on the MOTU team either knows the package well or is willing to put the work in to figure it out then we're going to get the update from Debian
[12:26] <Hew> what's the best way to update a generated .patch from merges.ubuntu.com?
[12:30] <slytherin> Hew: what are you trying to do exactly?
[12:31] <Hew> slytherin: merge transmission, which requires the changelog to be updated. I could do it manually but that seems messy and I'll probably make an invalid diff anyway. https://merges.ubuntu.com/t/transmission/transmission_1.71-1ubuntu1.patch
[12:32] <Hew> bug 384215
[12:33] <slytherin> Hew: did you try 'grab-merge transmission'?
[12:34] <Hew> slytherin: That sounds like a useful command, I'll give it a go! Thanks :-)
[12:35] <slytherin> Hew: The command is available on jaunty in ubuntu-dev-tools package.
[12:35] <Hew> slytherin: Already have it, it seems to be getting things now
[12:38] <Hew> slytherin: It has given me a warning after downloading everything - "It looks like this package is maintained in revision control"
[12:39] <slytherin> Hew: that is fine, it gives that warning when debian/control file has VCS-* fields.
[12:39] <dholbach> iulian: uploaded
[12:52] <slytherin> Does anyone know how well evolution-mapi works in jaunty?
[12:57] <directhex> slytherin, not at all IME
[12:58] <slytherin> directhex: So I think it is time to try it. :-D
[12:58] <slytherin> And file loads of bugs if possible. :-P
[12:59] <directhex> slytherin, PPA? i had a look upstream, most bugs were of a "fixed in latest release" form
[13:08] <slytherin> directhex: I will first try the plugin and then check at the bug supstream.
[13:17] <Hew> slytherin: I think I have finished with the transmission merge! I now have a .diff.gz, .dsc, and .changes files. Which should I attach to the merge bug report?
[13:19] <iulian> dholbach: Thank you.
[13:24] <mok0> What targets are being called when dpkg-buildpackage builds a package?
[13:24] <mok0> Can't get that indep build to work properly.
[13:27] <soren> mok0: http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules
[13:27] <mok0> soren: ah thanks for the ref
[13:27] <soren> mok0: Sure :)
[13:30] <mok0> rainct!
[13:30] <RainCT> Hey mok0
[13:30] <mok0> hi
[13:30] <Laney> rawr
[13:39] <mok0> soren, am I right in saying that the primary entry point into debian/rules is binary-arch for the -B flag, binary-indep for the -A flag and binary for the -b flag?
[13:40] <mok0> soren: and that the other "required" targets are not used explicitly?
[13:41] <soren> mok0: dpkg-buildpackage runs "debian/rules clean" first.
[13:42] <mok0> soren: right, ok
[13:45] <mok0> soren, hm, dpkg-buildpackage calls rules/build: after clean
[13:46] <persia> It calls clean, build, binary|binary-arch|binary-indep depending on how it's called.
[13:46] <mok0> persia: that's why most packages build both arch and indep always
[13:47] <mok0> persia: I am trying to achieve that the -B and -A flags actually *work*
[13:48] <mok0> persia: which they do when I have an empty build: target
[13:48] <persia> mok0, It's supposed to be depending on which of binary, binary-arch, or binary-indep is called, but yeah, not every package is so nice about it.
[13:48] <slytherin> Hew: add debdiff between debian version and ubuntu version
[13:49] <mok0> persia: when this package builds the -indep documentation package, all it needs to do is to run doxygen, I don't need it to do configure make and all that
[13:50]  * mok0 suspects many packages are doing it wrong because the dh_make templates are screwy
[13:50] <persia> mok0, Then don't have binary-indep depend on build
[13:51] <mok0> persia: err, no, because then it will go ahead and do the arch preparations
[13:51] <persia> mok0, That's only an implementation issue with dpkg-buildpackage: not a problem with the package.
[13:52] <mok0> persia: hm ok :-)
[13:52] <persia> quoting from policy "Both binary-* targets should depend on the build target, or on the appropriate build-arch or build-indep target, if provided, so that the package is built if it has not been already"
[13:52] <persia> So, you would provide a build that depended on build-arch and build-indep, but binary-indep would only depend on build-indep (which wouldn't do anything).
[13:52] <persia> If dpkg-buildpackage doesn'T work like this, consider filing a bug.
[13:53] <mok0> persia: lemme check...
[13:54] <mok0> -A calls build, binary-indep
[13:54] <mok0> -B calls build, binary-arch
[13:55] <mok0> -b calls build, binary
[13:55] <mok0> clean first of course in all 3 cases
[13:57] <persia> Well, read policy carefully.  I believe it's permitted to have build do nothing.
[13:57] <mok0> persia: i can recast it so build-indep does nothing
[13:58] <mok0> eerrr no
[13:58]  * mok0 thinks policy and dpkg-buildpackage don't match up
[14:01] <mok0> persia: quoting from policy: "For some packages, notably ones where the same source tree is compiled in different ways to produce two binary packages, the build target does not make much sense.  For these packages it is good enough to provide two (or more) targets (build-a and build-b or whatever) for each of the ways of building the package, and a build target that does nothing"
[14:01] <persia> mok0, build-indep should run doxygen, and binary-indep should package the results of that run.
[14:01] <mok0> persia: yes, that's what it's doing now
[14:01] <persia> Right.  That's the bit that makes me think you can have an empty build: if you do build-arch and build-indep, and set the right dependencies for binary-arch and binary-indep.
[14:02] <mok0> persia: then that's clarified. So I am in fact correct in saying that the dh_make templates are screwy
[14:02] <mok0> persia: because that template splits up arch and indep, but not fully
[14:03] <mok0> persia: it will always build at least one target twice
[14:04] <persia> Indeed.  I'm of the opinion that the archive would be a better place if dh_make didn't exist.
[14:06] <mok0> heh yeah
[14:11] <soren> mok0: Yes, that's what I said: "dpkg-buildpackage runs "debian/rules clean" *first*." (emphasis added after the fact)
[14:19] <Hew> Is a 4.2MB debdiff too large? If so, would a 0.8MB debdiff.gz be more appropriate?
[14:21] <slytherin> Hew: yes it is too large. What is the command you used for debdiff?
[14:21] <geser> what's inside the debdiff that it's so big?
[14:21] <Hew> it's a merge debdiff between transmission 1.61-2ubuntu1 and 1.71-1ubuntu1
[14:22] <Hew> the debdiff for the ubuntu changes only is fine
[14:22] <Hew> Should I just leave a comment saying "debdiff available if required"?
[14:23] <Laney> just do a diff over 1.71-1
[14:25] <Hew> Thanks, will do.
[14:38] <slytherin> Hew: we need debdiff between debian version and ubuntu version, not between two ubuntu versions
[14:38] <slytherin> Hew: When you provide debdiff, someone will take Debian version apply the debdiff to it to create Ubuntu version.
[14:39] <Hew> slytherin: I have done that also. The wiki page says to do two.
[14:39] <slytherin> Hew: The wiki needs update. :-)
[14:39] <Hew> slytherin: I have attached that one now at bug 384215
[14:40] <Hew> slytherin: Well I was following this which was otherwise quite helpful :-) https://wiki.ubuntu.com/UbuntuDevelopment/Merging
[14:41] <persia> slytherin, The bit about the ubuntu->ubuntu debdiff was added in a later edit: the rationale being that it was apparently easier to track that someone was maintaining Ubuntu variance correctly.  It fails miserably for new upstreams.
[14:42] <slytherin> persia: right. Usually I trust people to keep changelog in sync with what they actually updated, specifically in case of merges.
[14:42] <slytherin> Hew: Now you have to wait till someone form core team sponsors it. :-)
[14:42] <Hew> slytherin: Yep! I eagerly await a reply :-)
[14:43] <persia> slytherin, Usually I generate the ubuntu -> ubuntu myself, if I want it.  I feel that those seeking sponsoring should only attach sufficeint material for the sponsor to regerate the candidate package as it existed on the sponosoree's disk.
[14:44] <persia> At one point, the docs requested posting of build logs!
[14:45] <slytherin> I know, I have been through that. :-)
[14:54] <gaspa> slytherin: hi. remember about w3c-stuff-package, please! :)
[14:55] <gaspa> (just a reminder ;) )
[14:55] <slytherin> gaspa: Sure. Will definitely today.
[15:05] <trip0-nb> what's the best way to create a src package to upload to launchpad's ppa, with files that aren't code.  ie, theme files
[15:06] <slytherin> trip0-nb: take a look at existing theme packages.
[15:07] <persia> trip0-nb, u.com/MOTU/School/PackagingWithoutCompiling
[15:12] <vorian> persia: may I please join the uninverse sponosrs?
[15:14] <persia> vorian, Welcome back!
[15:14] <vorian> I promise i will look at things that start with letters other than 'k' too :)
[15:14] <binarymutant> ah is revu down?  :(
[15:14] <vorian> thanks :)
[15:17] <binarymutant> anyone know when revu will be operational again?
[15:21] <trip0-nb> i've just uploaded a package to launchpad and it was rejected
[15:22] <trip0-nb> how do I increment the package version?
[15:22] <binarymutant> trip0-nb, for a ppa?
[15:22] <trip0-nb> is there some sort of debuild switch
[15:22] <trip0-nb> yes, for ppa
[15:22] <binarymutant> trip0-nb, you could always use `dch -i` but I'm not sure if the version really matters on a ppa
[15:23] <gaspa> binarymutant: yes, it matters.
[15:23] <gaspa> must be increasing.
[15:23] <gaspa> ie: after uploading 1.2.3-4 you must upload something with a greater revision number
[15:24] <binarymutant> gaspa, I thought you could put anything on a ppa, like -0ubuntu1 or -20091105, etc
[15:24] <gaspa> yes, you could.
[15:24] <gaspa> but _after_  -0ubuntu1 you have to upload for example -0ubuntu2, -1 or 0ubuntu2something...
[15:25] <trip0-nb> okay, trying that...
[15:25] <vorian> you can, but if you upload 20091105 you would need to up it to 20091105.1 or something on the next upload
[15:25] <trip0-nb> if the dist in the changefile is karmic, can I still expect jaunty to be built?
[15:33] <binarymutant> trip0-nb, You can still install it on jaunty if that's what you mean
[16:23] <binarymutant> I miss revu :(
[17:14] <jacob> could anyone point me towards a tutorial/example on packaging a library?
[17:14] <binarymutant> jacob, what kind of lib? like a python one?
[17:15] <jacob> binarymutant: C/GTK. it's gtksourcecompletion
[17:15] <binarymutant> jacob, https://wiki.ubuntu.com/PackagingGuide/Complete#Packaging%20Shared%20Libraries
[17:15] <jacob> binarymutant: I saw that, but it ends rather abruptly when explaining symbols
[17:16] <binarymutant> jacob, did you see the IRC classroom session too?
[17:17] <jacob> binarymutant: no, actually, though i just found the link :-!
[17:17] <binarymutant> jacob, how about this one: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
[17:17] <jacob> binarymutant: ooh, that one looks good
[17:17] <jacob> thanks
[17:17] <binarymutant> its old though so be careful :)
[17:19]  * DBO pokes directhex 
[17:19] <DBO> where can I get one of those banshee t-shirts? the XL is way big on me and I want an L
[17:26] <AnAnt> Hello, what tool do you use to log IRC channels ?
[17:34] <binarymutant> is anyone else having problems with http://revu.ubuntuwire.org/ ?
[17:36] <MTecknology> Why does network-manager depend on update-notifier-common.....
[17:37] <MTecknology> makes no[n, ]sense
[17:38] <AnAnt> LP 255844
[17:41] <AnAnt> MTecknology: so, postinst of update-notifier needs to call a binary in update-notifier-common
[17:41] <AnAnt>   * dont restart NetworkManager in postinst, but use restart-notifier to
[17:41] <AnAnt>     ask users for reboot
[17:41] <AnAnt> that's from the changelog of network-manager
[17:41] <AnAnt> and restart-notifier is in update-notifier-command
[17:41] <AnAnt> s/-command/-common
[17:42] <MTecknology> AnAnt: so the dependency will be removed?
[17:42] <AnAnt> ?!
[17:42] <AnAnt> how did you understand it that way ?
[17:42] <MTecknology> sorry, I'm tired
[17:43] <MTecknology> I read it again
[17:43] <MTecknology> thanks
[17:44] <AnAnt> no problem
[17:54] <savvas> hm..
[17:55] <savvas> I recently installed the game package cuyo and the .sh scripts have an entry (and set to default) to open with it
[17:56] <savvas> really weird
[18:06] <nhandler> StevenK: You don't work for TMobile, do you?
[18:24] <pan1nx> hhi
[18:28] <pan1nx> how do I announce a new updated package?
[18:30] <pan1nx> for the MOTU?
[18:34] <Ampelbein> pan1nx: what is it you are trying to do? have you packaged a new upstream version and want it to go in karmic?
[18:38] <fabrice_sp_> binarymutant, you can use irclogs.ubuntu.com
[18:39] <fabrice_sp_> sorry, it was AnAnt
[18:41] <asomething> Any one know where to find the list of packages in Universe but not in Debian? I know I've seen something like that before, but can't remember where...
[18:42] <JontheEchidna> asomething: http://qa.ubuntuwire.com/multidistrotools/universe.html
[18:42] <asomething> JontheEchidna, thanks!
[18:50] <pan1nx> yes Ampelbein. bug #383499
[18:54] <Ampelbein> pan1nx: just attach the diff.gz of the version you would like to have sponsored and subscribe the sponsors team.
[18:54] <pan1nx> The diff is there
[18:54] <pan1nx> in the bug report
[18:55] <pan1nx> I subscribed the ubuntu-universe-sponsors to the bug, Ampelbein
[18:55] <pan1nx> Ampelbein, is there anything else I should announce? like a list?
[18:57] <Ampelbein> pan1nx: you linked to a diff to your ppa-version. this will not be accepted in the archives. you should create a package ready to get into the archives and attach the diff.gz of that package.
[18:57] <fabrice_sp_> pan1nx, you should put it as confirmed, and unassign yourself
[18:59] <fabrice_sp_> and give a link to download the orig tarball
[19:02] <pan1nx> Ampelbein, how do I create a package rady to get into archives? I have the bzr of the debian directory linked to the bug, the DEB that is build in the PPA, the diff between the new version and the Ubuntu version... I don't understand, please help...
[19:04] <fabrice_sp_> pan1nx, see my previous comment
[19:04] <Ampelbein> pan1nx: kflickr (20081222-0ubuntu1~ppa1) is the topmost version of your bzr branch
[19:05] <Ampelbein> pan1nx: is there no newer tarball available than 0.9.1?
[19:05] <pan1nx> fabrice_sp_ will do that as soon as i get clear Ampelbein
[19:06] <pan1nx> Ampelbein, yes, I will give the link to the tarbal. But again, why is that needed if I have added the watch file. uscan answers the question :D
[19:07] <Ampelbein> pan1nx: the point is that 20081222 is no good version.
[19:08] <pan1nx> Ampelbei, that is what the upstream calls it...
[19:09] <azeem> sanitize
[19:09] <azeem> it
[19:09] <azeem> e.g. by calling it 0.0.20081222-0ubuntu1~ppa1
[19:09] <azeem> or 0.0~20081222-0ubuntu1~ppa1
[19:11] <pan1nx> ok, the previous was 0.9.1
[19:11] <pan1nx> so, azeem, should I sanitize it by calling it 0.9.2~20081222-0ubuntu1~ppa1
[19:12] <azeem> 0.9.1+20081222-0ubuntu1~ppa1 looks better to me
[19:12] <azeem> not sure which one is preferred, really
[19:12] <ivoks> is it svn on top of 0.9.2 or 0.9.1?
[19:12] <ivoks> 0.9.1+20081222
[19:13] <pan1nx> no svn
[19:13] <pan1nx> ivoks, it is just a change in versioning (by just making the date instead of a version number)
[19:14] <ivoks> so, upstream changed versioning?
[19:15] <pan1nx> yes, ivoks
[19:16] <pan1nx> i think what azeem said,  0.9.1+20081222-0ubuntu1~ppa1, looks quite good
[19:19] <Ampelbein> pan1nx: without the ~ppa1 for the official repositories
[19:36] <pan1nx> ok, Ampelbein, azeem and ivoks, thanks for the help! I pushed all the changes, the archives, the sanitized version and added the link to the orig.tar.gz to the bugreport. Removed myself and confirmed the bug. Thanks for you help!
[20:10] <dupondje> https://bugs.launchpad.net/ubuntu/+source/audacious-plugins/+bug/383307
[20:10] <dupondje> this should be accepted asap :) audacious is already in the repo's, but its not working with the plugins :(
[20:42] <Nyquist333> Are there any developers working with GRUB 2 and USB support?
[21:27] <pan1nx> today is a REVU day?
[22:06] <james_w> why 404 in 404main?
[22:24] <jacob> is it okay to be using .install files in library packaging to split the main library and -dev packages? or is there a more "proper" way of doing things
[22:26] <RainCT> jacob: it's the most common way, afaik. Installing everything into debian/tmp and then using .install files to put the files where they are supposed to go
[22:27] <jacob> RainCT: okay, cool. also.. is cdbs frowned upon in this situation? (working fine so far)
[22:28] <RainCT> jacob: Why should it be? :)
[22:28] <jacob> RainCT: not sure, all of the examples i've seen have just been using debhelper
[22:28] <jacob> anyway, thanks :)
[22:29] <RainCT> jacob: well, then write an example with CDBS ;)
[22:29] <jacob> heh heh
[22:40] <directhex> jacob, cdbs is frowned upon because it is evil personified, compared to the purity and light of dh!
[22:43] <superm1> why?
[22:43] <superm1> they're both easy to use
[22:44] <ajmitch> cdbs is more of a black box
[22:45] <superm1> it's open source, just poorly documented
[22:45] <ajmitch> and slightly hard to read at times :)