[00:00] <chrisccoulson> ah, ok, that might be more difficult to do then. i think flashplugin just uses wget
[00:08] <geser> it should be different than using wget as long as it prints just to stdout and doesn't do any fancy stuff (like a ncurses interface or such)
[00:10] <geser> the questioning should be better done with debconf and only the result of it passed directly to the updater to not break non-interactive updates
[00:16] <c_korn> I also want to use this script as normal application
[00:16] <c_korn> so the user can update the game data with it
[00:45] <c_korn> hm, can't I just execute the updater in xterm or something
[00:45] <c_korn> I can expect that X is installed, can't I?
[01:08] <jjardon> Hello, I'm not sure this is the correct channel to ask but: I'm editing https://wiki.ubuntu.com/Halsectomy Can I add gnome-pilot to the table ?
[01:52] <drdr> Hello?
[01:53] <drdr> is anyone here?
[01:53] <hyperair> !give drdr ask
[01:54] <hyperair> oops
[01:54] <hyperair> !ask | drdr
[01:54] <drdr> Anyone know when firefox 3.5 will be pushed as a update to the netbook spin?
[01:57] <hyperair> fta: ^^
[04:46] <stochastic> Is the Library General Public License forward compatible with the Lesser General Public License?
[04:53] <lifeless> stochastic: same thing
[05:12] <binarymutant> I keep getting debian-changelog-file-is-a-symlink from lintian, I've deleted the changelog and created a new one but it still didn't get rid of the warning :/
[05:13] <ScottK> binarymutant: This is almost certainly OK.
[05:13] <binarymutant> cool ty ScottK :D
[05:14] <ScottK> If it's a multi-binary package and the package depends on the one that ships the symlink it's OK.
[05:14] <jtimberman> any MOTU able to look at stompserver, merb and chef on REVU?
[05:15] <binarymutant> ScottK, awesome, it is multi-binary
[06:39] <dholbach> good morning
[06:43] <fabrice_sp> Good morning Daniel :-)
[06:44] <binarymutant> can reportbug work with debian's bts too?
[06:44] <fabrice_sp> binarymutant, yes: reportbug --bts=debian
[06:44] <dholbach> hey fabrice_sp!
[06:44] <binarymutant> fabrice_sp, ty :D
[06:49] <fabrice_sp> dholbach, what do you mean with "if you fix this for Karmic, I'm happy to ACK it" in bug #416262. Should I upload a new version in Debian with the translations and re-ask for the sync? Or do you mean having the po files in a temporary way in debian directory?
[06:49] <dholbach> just a sec
[06:50] <dholbach> it'd be nice to have translations back and investigate where they went
[06:50]  * RoAkSoAx off to bed, bye all
[06:53] <fabrice_sp> dholbach, upstream lost them. I can upload them again to the upstream repository (I have 'upstream' powers for aptoncd :-) ), and update debian then
[06:53] <dholbach> fabrice_sp: that'd be sweet!
[06:53] <fabrice_sp> here we go then :-) Thanks
[07:11] <iulian> Hello dholbach.
[07:12] <dholbach> hey iulian!
[07:24] <stochastic> Would a kind motu with a spare second or two be able to REVU http://revu.ubuntuwire.com/p/xjadeo
[07:35] <stochastic> This package has received two advocations http://revu.ubuntuwire.com/p/a2jmidid but they were on separate uploads, do I need them on the same upload for it to get pushed through?
[07:37] <stochastic> ^^ james_w I think you may need to re-advocate if that's what's stopping it.
[07:53] <jtimberman> stochastic: yes, you need to get a second advocate.
[07:58] <stochastic> don't you mean third ;)
[08:00] <jtimberman> stochastic: only if james_w is unavailable to advocate, i suppose.
[08:20] <lamalex> does anyone here know about python distutls?
[08:20] <lamalex> mine keeps installing to /usr/local/local
[08:20] <lamalex> cannot for the life of me figure out why
[09:03] <DktrKranz> lamalex: pass --install-layout=deb to setup.py install call
[09:14] <AnAnt> Hello, how usable is wine1.2 ?
[09:17] <james_w> stochastic: stefanlsd uploaded
[09:20] <stochastic> james_w, okay, I just haven't seen it appear here yet: https://launchpad.net/ubuntu/+source/a2jmidid and it was still listed in the new packages page on revu
[09:21] <james_w> it's in the NEW queue
[09:22] <stochastic> I don't follow. Maybe I'm still too NEW
[09:23] <directhex> stochastic, new source packages go into the NEW queue for approval by an archive admin
[09:23] <directhex> stochastic, then new binary packages go back into NEW
[09:24] <stochastic> okay, and where does feature freeze play on this? will that package be accepted?
[09:26] <james_w> yeah
[09:26] <james_w> unless it is rejected, in which case you may have to ask motu-release nicely to allow you to upload after Feature Freeze
[09:27] <stochastic> okay. thanks for the clarification.
[09:31] <stochastic> bdrung_, if you have a second, I've re-uploaded (with all earlier discussed changes) xjadeo to revu.  But I can't for the life of me figure out how to get rid of the executable-not-ELF-or-script lintian warning.
[09:45] <directhex> stochastic, i'm not seeing it
[09:45] <directhex> qjadeo:   ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped
[09:45] <directhex> xjadeo:   ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped
[09:45] <directhex> xjinfo:   ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped
[09:45] <directhex> xjremote: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped
[09:46] <stochastic> directhex my lintian reports ./usr/share/qjadeo/locale/qjadeo_fr.qm to be the culprit
[09:47] <stochastic> but as I browse through the source tree I can't find any place where the qjadeo_fr file becomes executable
[09:47] <directhex> hm, it IS executable isn't it
[09:48] <stochastic> directhex, it's probably from either the makefile or the debian/rules file (the debian folder is shipped from upstream so I didn't write debian/rules from scratch)
[10:17] <jussi01> dholbach: good morning. got time for a quick pm?
[10:18] <dholbach> jussi01: yep
[11:35] <\sh> siretart: pingeling you got the mail from mrfai?
[11:46] <siretart> \sh: yes, I did
[11:46] <\sh> siretart: would you like to review my comment...and eventually make a comment, too? :)
[11:56] <bdrung_> stochastic: why do you run "test -f configure || ./autogen.sh" in the clean target?
[12:00] <hyperair> i would guess that it's to autogen so that configure exists inside the source package, which is not a good idea
[12:03] <bdrung_> that's why i asked. clean is for cleaning, not for creating :)
[12:32] <sistpoty|work> any DD around, who could sponsor me an upgrade of min12xxw (preferred from svn - svn://svn.debian.org/svn/collab-maint/ext-maint/min12xxw/trunk/)?
[13:15] <slytherin> james_w: there? need to discuss something abuot cobertura package that you rejected last week.
[13:15] <james_w> hi
[13:17] <slytherin> james_w: Even after remocing the DTDs in xhtml folder there are still some DTDs etc/dtds/coverage*.dtd which do not have license header. Is that acceptable?
[13:17] <james_w> possibly
[13:18] <james_w> were they written for this project?
[13:18] <slytherin> juli_: Can you please answer james_w's question?
[13:21] <juli_> james_w, I think so but I didn't check it with authors
[13:30] <james_w> it that's the case then it moves them to a slightly (un)clearer license state
[13:35] <juli_> james_w, I'll contact them. But what about the package? I need it for the rest netbeans staff
[13:35] <ghostcube> packaging request.. would it be possible to package 64 bit packages for lighnting and enigmail working on TB3 :)
[13:35] <james_w> juli_: I can't say without looking really
[13:36] <james_w> I expect that it would be ok, but can't be sure
[13:36] <james_w> I suggest you upload again
[13:36] <juli_> james_w, ok, thank you.
[13:37] <slytherin> ghostcube: Is such a version available i.e. the one which works with TB3?
[13:37] <ghostcube> yes
[13:37] <juli_> slytherin, could you, please upload again. I will see what can I do about coverage*.dtd in the meantime
[13:37] <slytherin> juli_: Ok. Let me test build it.
[13:37] <juli_> slytherin, ok. Thank you
[13:38] <slytherin> ghostcube: but there is no TB3 in repository. Why would anyone want to package an extension for it?
[13:39] <ghostcube> there is an ppa daily i havent known there is no universe package oO
[13:40] <ghostcube> havent searched i thought with ff3.5 there was tb3 too
[13:40] <slytherin> ghostcube: TB3 has not been released yet.
[13:40] <ghostcube> oh ok ..
[13:41] <ghostcube> btw its a must have :D
[13:55] <james_w> jtimberman: hey, does merb need the embedded gems?
[14:03] <slytherin> juli_: uploaded cobertura. it is now at the mercy of archive admins. :-)
[14:04] <juli_> slytherin, thanks! I'm writing a letter to cobertura developers about the license)
[14:08] <jtimberman> james_w: what gem is embedded??
[14:09] <james_w> gem?
[14:09] <james_w> there's about 20 of them :-)
[14:09] <jtimberman> james_w: oh, stuff in the specs?
[14:09] <james_w> one second
[14:10] <james_w> ./merb-core/spec/public/core_ext/fixtures/gems/gems/
[14:10] <james_w> ./merb-core/spec10/public/webrat/test_app/gems/gems/
[14:13] <jtimberman> james_w: its not included in the resulting package.
[14:13] <james_w> still
[14:14] <jtimberman> it was fine for debian, merb was uploaded to NEW.
[14:15] <jtimberman> but i was told that it probably wouldn't get into an archive in time to make karmic feature freeze, hence packaging for universe as well.
[14:16] <jtimberman> and it wasn't a blocking issue in earlier reviews.
[14:21] <slytherin> jtimberman: 'NEW' is not equal to 'ACCEPTED'. :-)
[14:23] <james_w> sorry, plumber arrived
[14:26] <jtimberman> slytherin: sure, and Debian ruby packaging also does not include the source package.
[14:27] <james_w> jtimberman: at the least not all the gems are covered by the same license as the main code, and that is not documented in debian/copyright
[14:31] <jtimberman> james_w: so you want me to repackage the source tarball?
[14:32] <james_w> I think so, though I've no idea what they are there for
[14:35] <jtimberman> they're there for doing spec tests on the source.
[14:36] <directhex> even if things aren't in the final package, their distributability needs to be certain for them to be on the ubuntu archive
[14:37] <jtimberman> Perhaps this is why Debian doesn't include the original source tarball in the packaging.
[14:43] <james_w> juli_: those files look very much like they are written for the project, so would be covered by the dominant license. Therefore I have accepted the package. Clarifying the situation with upstream would still be appreciated.
[14:44] <jtimberman> where should removal of the source gems be mentioned?
[14:47] <jtimberman> james_w: should i note those were removed in README.source, or README.Debian ?
[14:47] <james_w> see debian policy
[14:47] <james_w> it's debian/copyright
[14:47] <james_w> and README.source I guess
[14:47] <james_w> plus the version number should change
[14:52] <Daviey> Does anyone know of an example package that generates debian/*.install etc files at source build time?
[14:53] <Laney> Surely you'd just call install manually instead?
[14:56] <jtimberman> james_w: http://paste.ubuntu.com/258692/ adding that to README.source, with the gems dirs removed, that good?
[14:57] <james_w> probably
[14:57] <james_w> I didn't review the whole package
[14:57] <james_w> you need to document it in debian/copyright as well, and change the version number as I said
[14:58] <jtimberman> as in a new dch entry, or modify the ubuntu version, 1ubuntu1
[14:58] <james_w> the upstream version number
[14:58] <james_w> so that it is clear the tarball has changed
[14:59] <jtimberman> i dont know what you mean
[15:00] <jtimberman> as in bump from merb-1.0.12 to merb-1.0.13 or something?
[15:01] <jtimberman> i don't think upstream isn't going to remove those gems from the source tarball, they're included on purpose for the spec tests.
[15:08] <james_w> jtimberman: no, merb-1.0.12+dfsg
[15:08] <james_w> so that it is clear that it is a modified tarball, and not the one that upstream calls 1.0.12
[15:09] <jtimberman> james_w: do i just change the name of the orig.tar.gz, or update the changelog?
[15:09] <james_w> both
[15:10] <jtimberman> ok
[15:11] <jtimberman> in changelog,  merb (1.0.12+dfsg-0ubuntu1) ?
[15:14] <james_w> yep
[15:18] <jtimberman> uploaded to revu.
[15:18] <juli_> james_w, thank you! I wrote a message to cobertura-devel. I hope they clarify the situation.
[15:18] <james_w> thanks juli_
[15:22] <bddebian> Heya gang
[15:22] <sistpoty|work> hi bddebian
[15:23] <bddebian> Heya sistpoty|work
[16:02] <juli_> james_w, cobertura developer said coverage* files are under W3C license (the same: http://changelogs.ubuntu.com/changelogs/pool/main/w/w3c-dtd-xhtml/w3c-dtd-xhtml_1.1-5ubuntu1/w3c-dtd-xhtml.copyright). They will add these info for next release. Should I update copyright file now and reupload?
[16:03] <james_w> yes please
[16:03] <james_w> if they can make that explicit in the headers of their next release that would be great as well
[16:04] <james_w> I'd be happy to sponsor that change
[16:04] <juli_> james_w, thank you:) I'll update copyright and upload an updated version to REVU
[16:05] <james_w> just a debdiff would do
[16:05] <james_w> or even a diff for that file and proposed changelog entry :-)
[16:06] <juli_> should I create a bug in LP?
[16:06] <juli_> I suppose yes:) I'll do this today
[16:08] <james_w> no need really
[16:08] <james_w> if you just pass the changes to me I can sponsor straight away
[16:08] <james_w> a bug is fine though
[16:09] <jtimberman> james_w: can you take another look at merb please? i uploaded w/ new orig.tar.gz
[16:12] <james_w> sorry, I've got to do something else today
[16:12] <james_w> I've already spent most of my day on archive-admin stuff
[16:14] <james_w> jtimberman: you uploaded to REVU?
[16:14] <jtimberman> james_w: i did
[16:14] <james_w> I can upload that to NEW for you
[16:15] <jtimberman> james_w: :-D
[16:15] <james_w> link please?
[16:15] <jtimberman> http://revu.ubuntuwire.com/details.py?upid=6771
[16:15] <jtimberman> or, http://revu.ubuntuwire.com/p/merb
[16:47] <lamalex> DktrKranz: my distutils doesn't appear to have that option
[16:57] <juli_> james_w, I created a bug and attache diff files for copyright and changelog there: https://bugs.launchpad.net/ubuntu/+source/cobertura/+bug/418181
[17:16] <DktrKranz> lamalex: sounds strange, which release are you running?
[17:16] <lamalex> DktrKranz: jaunty
[17:16] <jtimberman> james_w: I also fixed blocking issue with license in stompserver, which had 2 advocates: http://revu.ubuntuwire.com/p/stompserver
[17:16] <lamalex> er
[17:16] <lamalex> karmic
[17:18] <lamalex> DktrKranz: i think part of the problem is that I dont understand distutils at all
[17:19] <DktrKranz> lamalex: so it should definitely support it. how do you call setup.py?
[17:20] <lamalex> DktrKranz: sudo python setup.py --instal-layout=deb install
[17:21] <DktrKranz> it should be "sudo python setup.py install --install-layout=deb"
[17:22] <lamalex> DktrKranz: do I pass the same flag for bdist?
[17:23] <DktrKranz> --install-layout is common for install only
[17:24] <lamalex> hmm how do I generate the correctly layed out tar.gz
[17:24] <lamalex> ah, it's dsist
[17:24] <lamalex> s/dsist/sdist
[17:32] <POX_> DktrKranz: ?! NEVER SUGGEST TO "sudo pytohn setup.py install" or ez_instal something!!! I will break other parts of the system
[17:33] <POX_> if someone wants to test something, he should use some kind of sandbox (like virtualenv)
[18:19] <slytherin> fabrice_sp: ping
[18:22] <fabrice_sp> slytherin, pong
[18:22] <jtimberman> Chef just needs one more advocate, who wants to be the lucky MOTU? :-D http://revu.ubuntuwire.com/p/chef
[18:22] <slytherin> fabrice_sp: do you plan to file sync request for doxia and doxia-site-tools?
[18:23] <fabrice_sp> slytherin, not yet. I was planning to get them built, for the moment
[18:25] <slytherin> fabrice_sp: Ok. I am updating my pbuilder. It will take me an hour to get doxia built. If you are done before that then please let me know.
[18:27] <fabrice_sp> slytherin, I can go with doxia-site-tools first
[18:28] <slytherin> it has build-dep on libdoxia-java
[18:29] <fabrice_sp> oh
[18:47] <fabrice_sp> slytherin, doxia build depends on plexus-containers and plexus-containers needs the latest version of libgoogle...
[18:48] <slytherin> so where are you stuck at?
[18:48] <fabrice_sp> compiling plexus-containers, without libgoogle
[18:50] <fabrice_sp> have to go. bbl
[18:50] <highvoltage> plexus-containers sound like something from star trek
[19:05] <fabrice_sp> back
[19:05] <fabrice_sp> highvoltage, it's almost as complex as the Enterprise :-)
[19:07] <highvoltage> fabrice_sp: :)
[19:07] <slytherin> fabrice_sp: so libgoogle is one of those few libraries which will need to be modified to have complete maven stack right?
[19:08] <fabrice_sp> slytherin, yes: it's also blocking the 'plugin' path
[19:08] <fabrice_sp> maven-plugin-tools-java
[19:08] <slytherin> fabrice_sp: have you discussed this already with ttx by any chance?
[19:09] <fabrice_sp> yes, and it's a no go :-/
[19:09] <fabrice_sp> ttx is more of the opinion to let maven and plexus as-is
[19:09] <slytherin> Then he is probably using google-* libraries as build dep for some other work.
[19:13] <fabrice_sp> I didn't specifically spoke about libgoogle, but his last email is more this way (do not touch non plexus lib)
[19:18] <slytherin> fabrice_sp: reply to that mail and add details about the libraries that 'must' be modified. Let's see what he says.
[19:18] <jtimberman> kirkland: thanks for your comments on Chef :)
[19:19] <mathiaz> jtimberman: debian-changelog-file-is-a-symlink - I've seen that one often - but I have no clue how to fix these
[19:19] <kirkland> jtimberman: sure, i just advocated
[19:19] <mathiaz> kirkland: ^^
[19:19] <kirkland> mathiaz: hmm, i've never seen that one before
[19:19] <kirkland> mathiaz: let me have a look
[19:19] <mathiaz> kirkland: it seems to be something from cdbs
[19:19] <fabrice_sp> slytherin, ok. As I will be on holidays beginning tomorrow, I won't be able to follow up on that until post-FFE.
[19:20] <slytherin> ok
[19:20] <kirkland> mathiaz: fwiw, i did advocate, packaging looks good
[19:20] <geser> it's one of Ubuntu's cdbs features to symlink identical files
[19:20] <kirkland> ah, space savings
[19:20] <slytherin> It does not need fixing
[19:20] <mathiaz> geser: that makes lintian unhappy
[19:20] <jtimberman> kirkland: thanks!
[19:20] <kirkland> mathiaz: i don't use cdbs very much, which is why i haven't seen it
[19:20] <slytherin> It is warning, not error.
[19:20] <jtimberman> there's an element of danger in using magic.
[19:21] <jtimberman> :)
[19:22] <mathiaz> slytherin: https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews#Tips says Package should be lintian clean
[19:22] <mathiaz> slytherin: lintian clean means error free or warning free?
[19:22] <mathiaz> kirkland: do you look for lintian warnings as an AA?
[19:23] <kirkland> mathiaz: yes, but warnings are not necessarily blockers
[19:23] <jtimberman> kirkland: you're an AA?
[19:23] <slytherin> Ideally it means free from errors as well as warnings. But in this case lintian is not updated to ignore a warning caused by a feature.
[19:23] <mathiaz> kirkland: lintian errors are though?
[19:23] <kirkland> mathiaz: bonus points for lintian overrides (with inline comments as to why they may be safely ignored)
[19:24] <kirkland> mathiaz: yeah, i generally require lintian overrides (with comments) for lintian errors
[19:24] <kirkland> mathiaz: where comments provide an acceptable explanation
[19:24] <kirkland> jtimberman: y
[19:24] <jtimberman> kirkland: mathiaz got me to put that in for chef-server ;)
[19:24] <jtimberman> as you probably saw.
[19:24] <kirkland> jtimberman: right
[19:25] <kirkland> mathiaz: honestly, most of my AA work is ensuring that debian/copyrights is comprehensive and correct
[19:26] <mathiaz> kirkland: right - are you also looking at the debian/ directory in general (as an AA)?
[19:26] <kirkland> mathiaz: and mostly trusting that the uploading/advocating MOTUs did a good job with the packaging checks
[19:26] <kirkland> mathiaz: only lightly; see my last statement ^
[19:26] <kirkland> mathiaz: so i did the REVU with MOTU hat on, not AA hat
[19:26] <mathiaz> kirkland: ok :)
[19:27] <kirkland> mathiaz: as for debian/copyrights, I read/digest that
[19:27] <mathiaz> kirkland: and you MOTU hat covers more things than your AA hat?
[19:27] <kirkland> mathiaz: i consider my MOTU hat to cover packaging technical details
[19:28] <jtimberman> kirkland, mathiaz and it was a good reminder to discuss the lintian override, now we have an upstream ticket to use system-provided jquery if it exists.
[19:28] <kirkland> mathiaz: which any MOTU, I think, should be able to cover
[19:28] <kirkland> mathiaz: and as an AA, we put a lot of trust in MOTUs
[19:29] <kirkland> mathiaz: for stuff like package syncs, we have to "trust" that the MOTU ack'ing the package sync has done a good job reviewing "why" the diffs can be dropped from the package
[19:29] <kirkland> mathiaz: because we might have to process a hundred of those per day, and can't look at every one of those
[19:30]  * mathiaz nods
[19:30] <kirkland> mathiaz: if a MOTU ack'd that, it's on him/her ;-)
[19:30] <kirkland> mathiaz: as for the licensing ...
[19:30] <kirkland> mathiaz: run "licensecheck -r ." from the package source tree
[19:30] <kirkland> mathiaz: i see chef is Apache license
[19:31] <kirkland> mathiaz: so I'll start with "licensecheck -r . | grep -v Apache"
[19:31] <kirkland> mathiaz: looking for anything licensed differently
[19:31] <mathiaz> kirkland: right - what do you do about Unknown - no copyright files?
[19:31] <kirkland> mathiaz: for instance, maybe some GPL code slipped into here
[19:32] <kirkland> mathiaz: i try to make sure those are clearly covered otherwise
[19:32] <jtimberman> kirkland: such as with the debian/copyright mentioning those filepaths
[19:32] <kirkland> mathiaz: and when possible, I ask upstream to ensure that they have proper copyrights in their files, and provide them the list of files missing copyright/license headers
[19:33] <kirkland> mathiaz: usually projects are willing/able to get that into a future release
[19:33] <kirkland> jtimberman: right; sometimes it's a matter of a whole section (subdir) being licensed/copyrighted and mentioning that in debian/copyrights
[19:35] <jtimberman> kirkland: gotcha. ran into a bit of that with merb earlier today. merb's spec tests include some gems, and some of those are available as packages but the upstream isn't going to worry about which platform they're on for testing.
[19:35] <jtimberman> so they can't rely on say libfoo-ruby is installed to do a test.
[20:19] <sistpoty> superm1: would you like to act as motu-release delegate for mythbuntu again, or do you have someone else you'd like to recommend for the position?
[20:20] <superm1> sistpoty, yeah should be able to.  i sponsor everything within our small team anyway :)
[20:20] <sistpoty> excellent, thanks superm1
[20:24] <lamalex> does anyone know what happens when there's a name conflict between packages from different sources?
[20:24] <sistpoty> fta: would you like to act as motu-release delegate for the mozilla team this feature freeze again (together with asac, if he agrees)?
[20:25] <ScottK> lamalex: If the two don't do the same thing, one has to be renamed.
[20:25] <sistpoty> lamalex: it's not coinstallable? (and you'd need to declare conflicts: otherpackage in both)
[20:25] <lamalex> sistpoty: they dont conflict
[20:26] <lamalex> ScottK: but what /happens/. does apt just pick on arbitrarily to be used?
[20:26] <ScottK> sistpoty: conflicts are only appropriate if they are alternative implementations of the same functionality.
[20:26] <fta> sistpoty, sure
[20:26] <ScottK> lamalex: First one installed wins.
[20:26] <ScottK> Second one will get an install failure.
[20:26] <lamalex> ScottK: and before installation?
[20:26] <ScottK> That's why one needs to be renamed.
[20:26] <sebner> ScottK: the one with higher versionsnumber wins xD
[20:27] <ScottK> sebner: Nope.
[20:27] <lamalex> aptitutde search package
[20:27] <lamalex> who gets shown
[20:27] <lamalex> both?
[20:27] <sebner> ScottK: why not?
[20:27] <sistpoty> thanks fta
[20:27] <ScottK> Ah.
[20:27] <ScottK> I was talking about file name conflicts, not package names.
[20:27] <ScottK> Sorry.
[20:27] <ScottK> sebner is likely correct.
[20:27] <sebner> np
[20:27] <sistpoty> he, /me is well
[20:27]  * sebner ^5 sistpoty 
[20:28] <ScottK> lamalex: Only the binary with the higher version number will exist in the archive.
[20:30] <sistpoty> luisbg: up for ubuntustudio delegation for motu-release for karmic again together with _MMA_?
[20:31] <luisbg> sistpoty, yes
[20:31] <lamalex> ScottK: thanks
[20:31] <sistpoty> luisbg: excellent, thanks. can you also ask _MMA_ if he agrees?
[20:31] <luisbg> sistpoty, will do and will let you know
[20:31] <sistpoty> thanks a lot luisbg
[20:31] <luisbg> he is a little bit hard to contact now but still possible :)
[20:31] <sistpoty> heh
[21:17] <xnox> burnout. is when you answer to a user-request wine on a devel list and get tangled into a support thread.
[21:18] <xnox> Modern Support: http://xkcd.com/627/
[21:18] <jpds> No, I don't do that.
[21:21] <sistpoty> luisbg: btw.: read the mail about the request for audacity standing FFe? (https://lists.ubuntu.com/archives/ubuntu-motu/2009-August/006079.html) / I also cross-replied to ubuntu-studio-devel
[21:59] <ghostcube> fta, ping
[22:01] <fta> ghostcube, no contentless ping please
[22:01] <ghostcube> fta, ping http://bugzilla.songbirdnest.com/show_bug.cgi?id=17683 :)
[22:01] <ghostcube> sorry
[22:03] <binarymutant> does anyone use reportbug with gmail? It didn't send the mail for me :/
[22:03] <fta> ghostcube, no idea
[22:04] <ghostcube> i think it is an songbird bug or a missing lib maybe
[22:11] <ghostcube> fta, got it the problem is somehow a mising german loalisation
[22:11] <ghostcube> *c
[22:38] <stochastic> bdrung_ I've lost that last command you suggested I run, can you repost?
[22:39] <bdrung_> stochastic: run debuild twice
[22:40] <bdrung_> stochastic: and you will see, that the second run failes, because the clean target do not remove all generated files. you have to remove them in the clean target with "rm -f file1 file2" or "rm -rf dir1 dir2"
[22:41] <xnox> james_w: You are ubuntu top contributor ;-)
[22:41] <james_w> it's a lie!
[22:41] <xnox> https://edge.launchpad.net/debian/+topcontributors
[22:41]  * xnox lol
[22:42] <xnox> When people start using Distributed Development will Karma even out?
[22:42] <ScottK> That's Debian, not Ubuntu.
[22:42] <james_w> don't take karma as a proxy for worth :-)
[22:42] <bdrung_> stochastic: and why do you run "test -f configure || ./autogen.sh"?
[22:42] <bdrung_> in the clean target?
[22:43] <james_w> xnox: somewhat, though it may take some time
[22:43] <stochastic> bdrung_, I don't know why that's there, I inherited the debian packaging from upstream and am cleaning it up
[22:43] <xnox> james_w: I'm just jealous =) I was evaluating my chances for UniverseContributor and tried to weight my Ubuntu Karma to find this bob =)
[22:43] <xnox> s/bob/bomb
[22:43] <james_w> xnox: LP might subtract a large lump off me or something, as it's not at all fair
[22:43] <james_w> heh
[22:43] <bdrung_> stochastic: then remove this line
[22:44] <xnox> at least you now probably feel like poker tournament winner with a huge stake =)
[22:46] <xnox> james_w: anyhow by submitting Karmic recipes for daily-debs I was hoping to get nightly bzr for Karmic.... Will you update cron-jobs or however jw+dailydebs works
[22:47] <james_w> ah, Dmitrijs!
[22:47] <james_w> thanks
[22:47] <james_w> I'll do that now, thanks for the reminder
[22:47] <bdrung_> if you remove the 190000 from the bazaar branches of james_w, there will be only 451 karma points left
[22:48] <stochastic> bdrung_ I think the removal of xjadeo.desktop isn't happening, but that sill doesn't fix the elf binary warning...
[22:48] <xnox> james_w: your welcome =) scratching my itch really I've just moved to karmic and I can't live without my daily treats
[22:49] <james_w> feel free to send me any more packages you want added
[22:49] <james_w> well within reason ;-)
[22:49] <bdrung_> there must be something wrong with the karma points. i am listed as "top contributer", too. really strange.
[22:49] <xnox> james_w: I kind of trying to run my own as well ~crosswire-daily for my Debian/Ubuntu Packaging team of Crosswire stuff.
[22:50] <james_w> nice
[22:50] <james_w> what's crosswire?
[22:50] <bdrung_> stochastic: it complains about xjadeo-0.4.7/src/qt-gui/qjadeo_fr.qm
[22:51] <bdrung_> stochastic: you should remove this file on clean
[22:51] <xnox> james_w: I didn't know before I've signed up =) It's bible study library & front-ends + actual texts of hundreds of bibles/commentries etc.
[22:52] <xnox> a long the lines of making Ubuntu interesting without the internetz
[22:52] <james_w> ah, ok
[22:53] <SiDi> Hello. Is this a good place to look for someone who would accept to maintain the ubuntu package of an upstream project ?
[22:53] <bdrung_> xnox: if you need a helping hand for packaging Xiphos, feel free to contact me.
[22:53] <xnox> james_w: really didn't know how to get involved with Ubuntu/Debian and there was a team being formed in January so I joined =) Resurected from horrible QA state 2 packages in Debian and Ubuntu =)
[22:54] <xnox> bdrung_: I'm proud maintainer of Xiphos =) Hope it's in good shape in Karmic now
[22:54] <xnox> bdrung_: can you sponsor a fix though? I've forgot a "Provides:" in the latest version in Ubuntu
[22:55] <SiDi> (the package in question is exaile, which losts its maintainer for ubuntu)
[22:55] <xnox> bdrung_: lp:~dmitrij.ledkov/ubuntu/karmic/xiphos/fix-upgrades
[22:55] <bdrung_> xnox: not yet, in 3 day is my motu application :)
[22:56] <xnox> Aha =) well I wish you good luck
[22:56] <xnox> I'm noone yet. And I'm thinking whether I can make it into Contributors
[22:57] <bdrung_> xnox: being a contributor is the first step (you become ubuntu member and gain a nice email address)
[22:58] <bdrung_> xnox: i found a bug in your debian package :)
[22:58] <xnox> bdrung_: I'm listening =)
[22:58] <bdrung_> xnox: it's a native package
[22:58] <bdrung_> but it shouldn't be native
[23:00]  * xnox checking
[23:01] <xnox> bdrung_: how is 3.1.1-1 in Debian or the proposed fix 3.1.1-1ubuntu1 native?
[23:01]  * xnox is confused
[23:01] <bdrung_> the package in debian sid
[23:01] <bdrung_> 3.1.1-1
[23:03] <xnox> You are right! How did that happen
[23:04]  * xnox need to bash Debian Sponsor for mingling with my package!!!
[23:05] <bdrung_> it was the sponsors fault?
[23:05] <stochastic> bdrung_, I've added qjadeo_fr.qm to the files removed in clean, but lintian still gives me the elf-binary error
[23:06] <bdrung_> stochastic: that are different issues :)
[23:06] <xnox> bdrung_: thanks a lot =)
[23:06] <bdrung_> xnox: np
[23:06] <bdrung_> xnox: i will have a look at the package. let me see if i find more issues ;)
[23:08] <xnox> bdrung_: the previous DD who maintained it had tarball inside tarball so it was all native to him
[23:08] <xnox> And now I'm out-of sync with and the checksums will be different
[23:08] <xnox> crap
[23:08] <bdrung_> stochastic: the convert and install command should be moved to the install target (you see the correlation?)
[23:09] <bdrung_> xnox: tarballs inside tarballs are ugly
[23:10] <bdrung_> stochastic: after all the install command you could put a chmod 644 command for the qjadeo_fr.qm file
[23:10] <bdrung_> stochastic: the "$(MAKE) distclean" command should come before the "rm" commands
[23:11] <stochastic> bdrung_, so the binary-indep: build install target should be empty?
[23:11] <bdrung_> stochastic: yes
[23:11] <bdrung_> stochastic: i don't know why you have a "rm -f" command in the binary-indep target
[23:13] <stochastic> bdrung_, I believe it's because the convert command creates a temporary copy of those files, then it's copied to the right place, then the temporary files are removed
[23:13] <bdrung_> ok
[23:14] <bdrung_> stochastic: the convert command _could_ put the resulting files directly into the right place.
[23:14] <stochastic> bdrung_, yes that would seem cleaner
[23:14] <bdrung_> stochastic: after running debuild twice, run "zcat ../xjadeo_0.4.7-0ubuntu1.diff.gz |diffstat" and you will see that there are some files not cleaned
[23:15] <stochastic> bdrung_ I don't understand what you mean by "run debuild twice"  I've run it many times
[23:17] <bdrung_> stochastic: run debuild twice means, that you run it at least two times.
[23:17] <bdrung_> the diffstat command list all files in the diff file. in the diff file should only be the files of the debian/ directory
[23:20] <bdrung_> stochastic: http://paste.ubuntu.com/258969/ this fixes the copyright lintian warning
[23:21] <stochastic> I thought you mentioned we could safely ignore that warning
[23:22]  * stochastic changes it anyway
[23:22] <stochastic> the zcat |diffstat command only returns files in the debian directory for me
[23:22] <mzz> (if you don't mind me asking: is there an easy way to get lintian to *always* warn on changes outside of debian/, not only if it detects a patch system, which iirc is its default behavior?)
[23:23] <bdrung_> stochastic: ok, maybe i need your updates
[23:23] <stochastic> bdrung_, uploading to revu right now
[23:24] <stochastic> oops, forgot to debuild after that copyright file change
[23:24] <bdrung_> mzz: don't know. i normally use the zcat diff.gz | diffstat command
[23:24] <stochastic> next upload will include the copyright file changes
[23:24] <bdrung_> mzz: if you want everthing from lintian, run "lintian -iIE --pedantic ..."
[23:24] <mzz> bdrung_: sure, and that's a good habit anyway, I guess (since it'll also warn you about oddities inside debian/)
[23:25] <mzz> the diffstat, that is :) I haven't tried lintian in full pedantic mode yet...
[23:25] <bdrung_> mzz: some pedantic warnings are usefull
[23:26]  * mzz is beginning to get the hang of things, has managed to create a ppa with a few basic packages, might figure out how to get those in either debian or ubuntu proper in the future
[23:27] <bdrung_> mzz: new ones?
[23:27] <mzz> mostly backports
[23:27] <mzz> well, backports or fairly trivial version bumps
[23:29] <bdrung_> ok
[23:29] <mzz> so far my experience has been that it's not exactly hard, but that there are a great many layers of tools calling each other, with multiple choices on some of the layers, and I don't understand all the layers yet.
[23:30] <bdrung_> mzz: i know the feeling.
[23:30] <bdrung_> it will go away some day :)
[23:30] <mzz> (things like python-support versus python-central, pbuilder versus sbuild versus probably other things I haven't encountered yet, but also on a user level apt-get vs aptitude vs synaptic, which don't seem to be using exactly the same "marks" database)
[23:30] <stochastic> bdrung_, I get no lintian warnings on that latest upload.  Do you see any issues left?
[23:31] <bdrung_> stochastic: is the upload already on http://revu.ubuntuwire.com/p/xjadeo
[23:31]  * mzz shall stop distracting you now :)
[23:31] <bdrung_> the last upload date is 23:48
[23:32] <bdrung_> mzz: no problem. i am doing more thing parallel.
[23:32] <stochastic> bdrung_, oh, looks like that upload was rejected
[23:32] <mzz> this is generally the case on irc :)
[23:33] <bdrung_> mzz: yes.
[23:35] <bdrung_> stochastic: the revu page seams to be not up to date
[23:37] <bdrung_> mzz: it's good to have a choice, but on the beginning it could be confusing. sometimes you use more than one of them (e.g. i use apt-get and synaptic)
[23:38] <stochastic> bdrung_, okay revu is up to date now
[23:42] <bdrung_> stochastic: the second run of debuild failed. the patch could not applied. "1 out of 1 hunk FAILED -- saving rejects to file src/qt-gui/qjadeo.cpp.rej"
[23:43] <stochastic> bdrung_ how are you getting these errors?
[23:44] <stochastic> what options are you running debuild with?
[23:44] <stochastic> is it in a pbuilder environment?
[23:45] <bdrung_> stochastic: run this: http://paste.ubuntu.com/258979/
[23:46] <bdrung_> stochastic: no, you cannot reproduce it with pbuilder, because pbuilder do not rely on the clean target
[23:48] <stochastic> bdrung_, but for that I need to manually install the build deps?
[23:49] <bdrung_> stochastic: yes
[23:49] <stochastic> ugh, is there any way to do that without clogging my system up?
[23:51] <bdrung_> stochastic: setting up a virtual machine :)
[23:51] <xnox> stochastic: after playing around with a lot of pacakges a removed all -dev packages and then did an autoremove =)
[23:52] <xnox> "Developers spring cleaning"
[23:52] <bdrung_> xnox: i clean them once in a half year with reinstalling the current release. ;)
[23:52] <xnox> bdrung_: Ahh that's what you call install party =)
[23:52] <bdrung_> xnox: yes
[23:53] <bdrung_> xnox: but sometimes i install in between
[23:53] <bdrung_> last time was when i bought an ssd.
[23:53] <xnox> =) me too I've just upgraded to karmic alpha
[23:53] <bdrung_> the complete installation needs less than 10 minutes
[23:54] <bdrung_> karmic is on my previous hdd and in a vm
[23:54] <xnox> what about / etc?
[23:54] <xnox> and /var/cache/
[23:54] <stochastic> bdrung_, my apt-get doesn't want to install any of the last four dependencies because of broken sub dependencies, but pbuilder finds these just fine
[23:55] <stochastic> bdrung_ could you just pastebin the diffstat so I can see the result of the debuilds?
[23:55] <bdrung_> stochastic: strange
[23:56] <bdrung_> stochastic: http://paste.ubuntu.com/258982/
[23:57] <bdrung_> xnox: for /etc i have some scripts / patches that are making the required changes
[23:57] <bdrung_> xnox: but /var/cache?
[23:57] <xnox> ok /var/cache/pbuilder
[23:58] <xnox> and /var/cache/apt-cacher-ng
[23:58] <xnox> ~30 GB
[23:58] <bdrung_> xnox: i rebuilt them. that is not the problem. (i have mirrored jaunty and karmic with apt-mirror)
[23:58] <xnox> how much does that take space?
[23:58] <bdrung_> i have one pc without internet access
[23:59] <bdrung_> 44,8 GiB
[23:59] <xnox> ok not that bad
[23:59] <bdrung_> one distribution would use 22 - 25 GiB