[01:33] <james_w> ajmitch: mail won't be sent if there are no open tasks on the bug
[01:54] <ajmitch> james_w: I'll have to take a look at the ones I received it for then
[01:55] <james_w> please do, if you find a case where it shouldn't have happened then let us know
[01:56] <james_w> (I'm not totally satisfied with that solution, but it was something that was quick to do and reduced mails by probably two orders of magnitude while being generally applicable)
[01:56] <ajmitch> I just noticed them all from a single package that I've subscribed to bugmail for, it wasn't a large number of mails
[01:58] <ajmitch> james_w: it's ok, they appear to have a debian task open on them
[02:04] <james_w> yeah, the fact that a lot of bug watches haven't been updating exacerbates the problem
[02:04] <ajmitch> I just noticed that on one of the bugs I checked :)
[02:29] <kb9vqf_> ajmitch: Recompilation of everything succeeded; feel free to review it when you have time ;-)
[04:00] <cpscotti> Can anyone review this package http://revu.ubuntuwire.com/p/harpia?
[04:35] <ingenthr> hey all, question on packaging: if i want to put together a package which depends on two less-common-libraries which are only available static, is it acceptable to bundle them into the package i would like to contribute?
[04:36] <RAOF_> ingenthr: For some values of "acceptible", yes.
[04:36] <RAOF_> ingenthr: Why are they only available static?  That'll almost certainly break on AMD64, for example.
[04:37] <ingenthr> don't know for sure, i could check
[04:37] <ingenthr> i believe it's because they are considered of more limited utility
[04:37] <ingenthr> it's libstrophe, an XMPP library in C
[04:38] <RAOF_> That doesn't sound like a limited-utility library.
[04:38] <RAOF_> :)
[04:39] <ingenthr> doesn't sound like anyone's contributed it yet either :)
[04:39] <Hobbsee> directhex: looks like your box has fallenover again :(
[04:40] <RAOF_> ingenthr: That would mean that you need to package the lib as a part of packaging the app.
[04:41] <persia> Or rather, first package the library, and then package the application (rather than bundling them)
[04:41] <ingenthr> RAOF_: i have that done effectively, as a subdir
[04:41] <ingenthr> an automake SUBDIR
[04:42] <RAOF_> ingenthr: persia said it more clearly.  Package the library separately, then make your app depend on that package.
[04:43] <persia> Or rather, have it build-depend on the -dev binary package produced by the library package, and have done the shlibs stuff correctly so the dependency is automatic with ${shlibs:Depends}
[04:44] <RAOF_> Again with the clarity :)
[04:44] <ingenthr> i just pulled the latest source to see what it does by default, and sure enough it builds a .a file
[04:44]  * persia goes to find some oil to wipe on the screen
[04:45] <RAOF_> ingenthr: Well, that's unfortunate.  It probably needs to be fixed to build a shared object.  Also, as I said, that's likely to fail on AMD64.
[04:45] <RAOF_> Because of the wonders of PIC.
[04:46] <persia> Hasn't there been some effort underway to do PIC on i386 as well?
[04:47] <RAOF_> Yes, but it's not mandated by the buildchain; Non-PIC code will simply FTBFS on AMD64.
[04:47] <RAOF_> Well, will likely FTBFS, if it's linked anywhere near a library.
[04:48] <ingenthr> so, what's going on is AMD64 requires PIC, but i386 buildchain doesn't do PIC by default?
[04:48] <persia> Ah.  I thought that work was farther along.  I may be confused with another TLA beginning with P/
[04:49] <RAOF_> I didn't think we'd be ever mandating PIC no i386, anyway; the register it eats has a noticable (~10% for most stuff, IIRC) performance impact.
[04:49] <RAOF_> s/no/on/
[04:50] <persia> Oh my.  Yes, then it would make sense not to do that.  All the more reason for everyone to drop i386: 1) it doesn't handle very much ram, 2) it can't be made secure, etc.
[04:51] <persia> (mind you, that would have to start with HW vendors, so there's not much we can do about it directly)
[04:51] <RAOF_> Also, PIC buys you much less security on i386; there's still only a 4GiB address space, which you can apparently walk through in the order of seconds.
[04:51]  * RAOF_ draws on hazy memories of security discussions.
[04:53] <ingenthr> so, with that digression :)   if i want to have a package considered for universe, best thing to do is fixup and contribute it's dependencies
[04:54] <persia> ingenthr, Indeed.
[04:54] <ingenthr> and even if i want someone else to run my binaries on i386 running on amd64, i'll likely have to do this anyway due to the toolchain building non-PIC
[04:54] <ingenthr> though, if i build my binaries, i can control PIC or not
[04:55] <ingenthr> or is it more complicated than that
[04:55]  * ingenthr is familiar with position independent code, but not so much with this environment
[04:56] <persia> ingenthr, You'll want to build a source package.  The source package will be compiled for each architecture in the peculiar way best suited for that architecture.
[04:57] <persia> If you have an amd64 system, you can use pbuilder or sbuild to construct build environments for each of i386 and amd64.  For other architectures, you'll need to have them (or emulate, but that makes for slow compilation).
[05:04] <ingenthr> thanks for the help
[05:51]  * RAOF_ wonders whether he should respond to the rather incoherent "overgod" ubuntu-motu@ mail.
[05:54]  * kb9vqf_ would respond and ask for his bank account # to assist with the transfer of 10 million dollars out of the country ;)
[05:55] <kb9vqf_> That is, if it's the same spam I fight all the time
[05:55] <persia> It's not.  It's a complaint about the terms used in a specific piece of software.
[05:57] <RAOF_> It's hard to say "I think you're making an incoherent mountain out of a sub-atomic molehill" in a respectful way.  I shall therefore not try.
[05:58] <ScottK> RAOF_: I kind of shocked him when he was here when I pointed out that it was pretty well impossible to publish anything that touched religion that didn't offend someone and predicted the outcome of his request is we'd have to remove Bible study tools from the archive.  He didn't like that idea, but it didnt' deter him.
[05:59] <persia> It's interesting.  I believe he just wants a s/G/g/ somewhere, but I'm not convinced it can be provided.
[06:00] <RAOF_> That doesn't surprise me.  He comes across as being supremely confident that the only action reasonable individuals could take is to remove overgod from the archives.
[06:00] <ajmitch> he has a point, however badly he presents it :)
[06:01] <ScottK> ajmitch: He has a very, very small point, but if we start playing censor on such things there is no end to it.
[06:01] <ajmitch> oh certainly
[06:01] <RAOF_> I'm not sure that's the case.  I thought, rather, that the fact that it's (possibly - the font isn't exactly the most readable set of glyphs ever) spelt "OverGod" in the title screen is evidence that the author meant to denigrate God.
[06:01] <ajmitch> first up against the wall is the wallpapers package from long ago :)
[06:03] <RAOF_> I wonder what he thinks of the "god" package :)
[06:03] <persia> ajmitch, That appears to be gone (or at least I can't find it in karmic)
[06:03] <ScottK> RAOF_: If I were an ardent athiest (I'm actually not) I could make a much stronger argument that the presence of material in the Ubuntu archive that supports such silly superstitions as supernatural beings of any kind is deeply offensive to me and should be removed.
[06:03] <ajmitch> persia: oh well
[06:05]  * ajmitch has been around too long, I even considered cleaning up a hoary chroot to get some space back :)
[06:05]  * ScottK has been up too long and probably ought to go to bed.
[06:05] <ajmitch> heh
[06:05] <RAOF_> ScottK: I don't find that particular end of the athiest spectrum particularly convincing, either.  Particularly since there's nothing inherently evangelical about athiesm.
[06:06] <RAOF_> But yeah.
[06:07] <ScottK> Don't even get this hypothetical athiest evangelist started on the fact that there are two Ubuntu derivatives that have a specific religious focus and much of their stuff is in the official archive.
[06:08] <persia> ScottK, We've had that hypothetical individual present making that argument before.  Please don't recap by proxy :)
[06:09] <ScottK> Oh.  OK.  Nevermind then.  I missed that one.
[06:09]  * ajmitch missed it all too
[06:09] <ScottK> BTW, just backported 3 clamav packages with 18 rdepends total for dapper/hardy/intrepid and only one build failure (that on hppa, so I don't care).
[06:10] <ajmitch> I'm surprised we still get hppa build failures
[06:10] <persia> I thought there were some Dapper and Hardy hppa users.
[06:10] <ajmitch> I thought that port was being turned off
[06:11] <TheMuso> for karmic only
[06:11] <ajmitch> so *-backports still lives on for hppa?
[06:11] <ScottK> Certainly
[06:11] <RAOF_> Thinking of ports, I need to point out that PPC kernel headers don't work properly.
[06:11] <ScottK> -security/-proposed/-updates too
[06:11] <ajmitch> what a shame :)
[06:11] <TheMuso> RAOF_: For what version of Ubuntu?
[06:11] <ScottK> RAOF_: Did you point it out to TheMuso?
[06:11] <ScottK> Heh.
[06:12]  * ajmitch wouldn't mind having a PPC box to play with
[06:12] <RAOF_> TheMuso: For (at least) Jaunty onwards; nouveau-kernel-source fails to build against it, and it's due to... some code missing in the headers.
[06:12] <persia> RAOF_, which release?  I thought that was being sorted for karmic.
[06:12] <RAOF_> Let me russle up the bug.
[06:12] <TheMuso> RAOF_: Right, I am aware of that for jaunty
[06:12] <TheMuso> RAOF_: tis fine, I know of it.
[06:13] <RAOF_> Yay.
[06:13] <TheMuso> That reminds me, I need to fix that up for karmic, now that ports is being merged back into the main kernel source package.
[06:13] <RAOF_> Heh.
[06:13] <RAOF_> Then PPC users will get a mostly working nvidia driver!
[06:16]  * RAOF_ hits the road.
[06:32] <mrooney> Is there a build-dep for apt that gets the dependencies for a package, but not the package itself?
[06:33] <mrooney> It seems like what you'd want to run a python app from trunk
[06:33] <Hobbsee> apt-get build-dep foo?
[06:37] <mrooney> Hobbsee: no I want the depends not the build-depends
[06:38] <mrooney> I meant a build-dep equivalent for depends
[06:39] <mrooney> but, it should also do recommends
[06:40] <Hobbsee> oh, right
[06:40] <Hobbsee> i did wonder...
[06:41]  * Hobbsee spies dpkg-depcheck
[06:42] <Hobbsee> hm, that will only give you a list
[07:20] <dholbach> good morning
[07:39] <ajmitch> morning dholbach
[07:39] <dholbach> hi ajmitch
[07:49] <YokoZar> hmm if dholbach's waking up that means I need to put my blog post up sooner ;)
[07:51] <ajmitch> YokoZar: another dholbach appreciation post? :)
[07:52] <YokoZar> something like that ;)
[07:52] <YokoZar> Actually I was gonna write about branding
[07:52] <YokoZar> (apt-get install ubuntu-branding in karmic, then open solitaire)
[07:52] <ajmitch> when dholbach shows up I know that I've got to get back to sponsoring & uploading before I feel the whip ;)
[07:52] <YokoZar> Just put that together today
[07:52] <ajmitch> yeah, I saw the branding upload
[08:07] <geser> good morning
[08:09] <ajmitch> hi geser
[08:24] <gaspa> siretart: LOL.
[08:24] <gaspa> :)
[08:24] <gaspa> siretart: yes, it was a failed upload on my ppa. :)
[09:43] <gaspa> siretart`: hi.
[09:46] <siretart`> hi gaspa
[09:46] <gaspa> :)
[10:15] <Laney> anyone fancy approving the pidgin backport? bug 389322
[10:15] <Laney> (to hardy)
[10:15] <Laney> scroll to the end, there's a lot of noise in that bug
[10:17] <slytherin> Laney: is it backport or SRU?
[10:17] <Laney> backport
[10:18] <Laney> probably should be on another bug, but somebody already opened the task there
[10:19] <slytherin> Laney: somebody who? Was it one of the people who usually work on backports? If not then it makes sense to have separate bug.
[10:19] <Laney> it was chriscoulson who is a developer afaik
[10:20] <Laney> anyway the paperwork doesn't matter so much
[10:20] <Laney> i honestly can't be bothered to open a new bug, this problem has had enough of my time already
[10:22] <slytherin> In that case, I think you should make the backports task assigned to you. nit the SRU task. :-)
[10:23] <Laney> a backporter needs to take action on that task now
[10:34] <geser> Laney: have you seen that pidgin 2.5.8 is out? fixing CVE-2009-1889
[10:34] <Laney> geser: seb just told me
[10:34] <Laney> (bah)
[11:17] <Hew> Hi MOTUs. My attempt at revelation has FTBFS yet again, and this is getting quite frustrating. bug 387231. It looks like site-packages must be changed to dist-packages. How can I do this? I found references to site-packages in the configure file, can I find/replace those?
[11:26] <geser> Hew: have you a build log at hand?
[11:26] <DktrKranz> Hew: to test it, install pkgbinarymangler, so you can simulate buildd's behaviour
[11:26] <geser> and don't forget to enable it (don't know the defaults)
[11:27] <Hew> geser, http://launchpadlibrarian.net/28480488/buildlog_ubuntu-karmic-i386.revelation_0.4.11-4ubuntu2_FAILEDTOBUILD.txt.gz
[11:27] <DktrKranz> geser: IIRC, it's enabled
[11:28] <Hew> Thanks I'll take a look at pkgbinarymangler.
[11:31] <geser> Hew: you probably need to recreate the configure script so it knows about dist-packages when building for python 2.6
[11:34] <Hew> geser, how do I "recreate" the configure script? Is it sufficient to find/replace site-packages with dist-packages?
[11:34] <mok0> kees: ping
[11:37] <geser> Hew: no, as it will break it for python2.5 which still uses site-packages
[11:43] <runasand> how do you actually close a bug in launchpad?
[11:43] <Laney> you mean from an upload?
[11:43] <runasand> Laney: no, close it because it has been solved.
[11:43] <Laney> change the status
[11:44] <runasand> ah, found it. Thanks :)
[11:47] <stefanlsd> RainCT: when u get a sec, a revu of gears would be appreciated!  :)
[11:54] <RainCT> stefanlsd: License: MPL 1.1/GPL 2.0/LGPL 2.1
[11:55] <RainCT> stefanlsd: that field is wrong, should probably be something like (check the DEP as I'm just guessing):   mpl-1.1 or gpl-2 or lgpl-2.1
[11:55] <stefanlsd> RainCT: mm. yeah, i remember something like that... will check. thanks
[12:19] <A|i> is the package maintainer for openjdk around?
[12:23] <slytherin> A|i: probably not, but you can ask question.
[12:28] <A|i> slytherin, i'm trying to use openjdk on opensuse build system, but installation fails:
[12:28] <A|i> http://pastebin.com/d1b8d468b
[12:28] <A|i> slytherin, i get the same message for ubuntu 8.10/9.04 32/64 bit
[12:29] <slytherin> A|i: is your chroot updated? I believe this problem is fixed in last 2 days.
[12:29] <slytherin> *was fixed*
[12:30] <slytherin> A|i: or there is another error that the JAVA_HOME variable does not point to proper directory corresponding to openjdk
[12:30] <A|i> slytherin, we cannot have access to the virtual machines, how come this problem was only fixed 2 days ago?
[12:30] <A|i> let me try the JAVA_HOME approach..
[12:31] <slytherin> A|i: I guess I am mixing your problems. I first thought the issue was related to ca-certificate-java. But your JAVA_HOME seems wrong.
[12:31] <slytherin> A|i: What are you trying to build by the way?
[12:32] <A|i> slytherin, I'm just trying to install openjdk in order to build my own java package..
[12:32] <A|i> slytherin, there is no JAVA_HOME in the log?
[12:33] <A|i> slytherin, should it be set to /usr/lib/jvm/java-6-openjdk ?
[12:33] <slytherin> A|i: yes
[12:35] <slytherin> A|i: if this is first time you are installing openjdk and seeing this error then you should probably log a bug.
[12:36] <A|i> slytherin, yes, the virtual machines start from scratch everytime
[12:44] <directhex> the opensuse build system is sorta like the PPA thing, but suseier. and with support for buckets more distributions
[12:44] <directhex> i don't know if its buildds do any funnies to the environment
[12:45] <hyperair> directhex: i don't know if they do any funnies to the environment, but they don't allow you the freedom of editing your package locally and uploading a .dsc
[12:45] <hyperair> to summarize, it's incredibly stupid for debian-based systems.
[12:45] <hyperair> i hear they don't even have support for .install files or something =\
[12:45] <directhex> o noez, my freedoms! :(
[12:45] <hyperair> things may have changed since then
[12:46] <directhex> basically they have little experience with debian build systems, so there are bugs
[12:46] <cjwatson> that sounds impossible unless they're not using the debian/rules interface, in which case most packages would entirely fail to build
[12:46] <directhex> i've filed some, and had them fixed
[12:46] <cjwatson> (.install)
[12:46] <hyperair> well that's why i refused to move the banshee(-unstable)-team PPA to obs.
[12:46] <directhex> e.g. build-depends-indep are actually installed now
[12:46] <cjwatson> not that I have any reason to suggest people use the opensuse buildservice but that does sound like unsubstantiated rumour ...
[12:46] <hyperair> cjwatson: single binary packages work. and you can pass arguments to dh_install.
[12:47] <directhex> i built mono on OBS, so the mother of all splittypackages works.
[12:47] <cjwatson> if you can't upload a .dsc, how do you interact with it?
[12:47] <hyperair> i can't remember
[12:47] <hyperair> you upload each file individually i think
[12:47] <hyperair> in the debian/ directory
[12:47] <directhex> or upload the diff.gz
[12:48] <A|i> slytherin, with setting JAVA_HOME, i get this: http://pastebin.com/m77f36d02
[12:48] <hyperair> directhex: oh you can do that?
[12:48] <slytherin> A|i: You should file a bug. It is behaving like for installing openjdk it needs openjdk installed.
[12:48] <directhex> hyperair, sure
[12:49] <hyperair> directhex: i've never really tried it before; i looked at the docs and decided against even touching it
[12:49]  * ScottK thought you uploaded an rpm spec file and among other thing got .debs back.
[12:49] <ScottK> One can easily imagine how well that works.
[12:49] <hyperair> alien?
[12:50] <directhex> ScottK, nay
[12:50] <ScottK> OK.
[12:50] <savvas> dholbach: here? can you revert gnote back to 0.4.0 in karmic? there's a data corruption bug I missed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534969
[12:51] <hyperair> is that the one where gnote modifies the noets so they'er incompatible with tomboy so that you can't go back?
[12:51] <directhex> but there IS some magic for re-using patches and orig from an rpm build
[12:51] <directhex> see http://en.opensuse.org/Build_Service/Deb_builds
[12:52] <directhex> hyperair, no, tomboy was patched to support the gnote note format
[12:52] <hyperair> directhex: ah right.
[12:52] <directhex> hyperair, this one looks a lot like a problem i saw in 0.5.0 with a fresh install (no ~/.tomboy or ~/.gnote)
[12:52] <dholbach> savvas: no, sorry
[12:52] <savvas> hyperair: ah no, they made an sync plugin for that - this one is much worse unfortunately :\
[12:52] <hyperair> hmm
[12:53] <dholbach> savvas: and I didn't update - it was done already
[12:53] <dholbach> I just closed the bug
[12:53] <savvas> dholbach: ah, ok thanks :) I'll just wait for the update
[12:57] <stefanlsd> RainCT: i've fixed that dep5 problem up. anything else you've noticed before i push back to revu?
[12:58] <AnAnt> hello, has anyone seen the sl-modem issue that I sent by email ? any ideas ?
[13:05] <RainCT> stefanlsd: don't make lines longer than 80 characters in README.Debian
[13:06] <RainCT> stefanlsd: (personally I'd remove the "designed to be used o both Google and non-google" sentence and in the second paragraph list them all together; I'd also change the first word from "Gears" to "Google Gears".. but well that's just me, feel free to ignore)
[13:07] <RainCT> I'm test-building it now
[13:07] <A|i> slytherin, is it possible toinstall openjdk without ca-certificates-java? Debian Lenny does it
[13:07] <directhex> Google(tm)(r)(c) Gears(c)(r)(tm)
[13:09] <RainCT> directhex: ehm.. are you okay? :P
[13:10] <directhex> RainCT, delerious due to dieting, if that counts
[13:11] <jonnymind> hello all.
[13:11] <slytherin> A|i: that is because ca-certificates-java is recommends and not depends for openjdk in lenny.
[13:12] <stefanlsd> RainCT: i have a long line in README.debian of 92 chars, that doesnt make sense to wrap (its a string they need to remove) - would that could issues or should i wrap it anyways?
[13:13] <RainCT> stefanlsd: no, you can leave those. technically it doesn't make a difference at all, it's jsut that 80 char lines are easier to read from the terminal
[13:14] <stefanlsd> RainCT: thanks. changes done as suggested.
[13:24] <PecisDarbs> hi people, is there list of packages which are planned to package for next Ubuntu versions? I would like to find out if anyone plans to package fprintd
[13:29] <stefanlsd> PecisDarbs: typically search for a bug in launchpad and debian for fprintd
[13:30] <PecisDarbs> ahh, right
[13:31] <RainCT> PecisDarbs: For Debian, see http://www.debian.org/devel/wnpp/being_packaged and http://www.debian.org/devel/wnpp/requested
[13:31] <stefanlsd> PecisDarbs: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502138
[13:33] <slytherin> that bug is pretty old.
[13:36] <stefanlsd> PecisDarbs: yeah. you maybe wanna contact the reporter and ask if he still intends to package it, if he's done anything that you can use and you can do it together, or if you can take over doing it
[13:36] <PecisDarbs> I see
[13:36] <PecisDarbs> well, I will try to do that after exams
[13:52] <_ruben> bah .. cant wait for dhcp4 to hit the repos .. other dhcpv6 implementation just pretty much suck imo :p
[14:06] <joaopinto> vbox 3.0 is out today, hope it can be ready for karmic
[14:12] <joaopinto> is there an SRU pending for pidgin, regarding the yahoo problem ?
[14:19] <RainCT> stefanlsd: I'm uploading :)
[14:20] <stefanlsd> RainCT: i've got some changes...
[14:20] <stefanlsd> i havent pushed yet :)
[14:20] <RainCT> okay
[14:21] <RainCT> ah right, my suggestions aren't up yet
[14:21] <RainCT> stefanlsd: poke me once you've uploaded
[14:22] <stefanlsd> RainCT: awesome, pushing to revu now :)
[14:29] <iulian> joaopinto: Hmm, I think I saw a discussion regarding that issue.  If I remember correctly, pidgin is still under testing.
[14:30] <joaopinto> I saw someone metion it on the morning it would go into backports
[14:30] <joaopinto> but wasn't clear for me if that means there will be no SRU for the yahoo protocol problem
[14:30] <Laney> joaopinto: it went to jaunty-proposed today
[14:31] <iulian> Laney: Do you have a bug#?
[14:31] <Laney> iulian: not to hand, check LP
[14:31] <Laney> or the changelog for the upload
[14:34] <iulian> Laney: Ah, right.  I've just checked the changelog but I've somehow missed your upload :-)
[14:34] <Laney> it might not be published yet
[14:34] <iulian> It is.
[14:34] <iulian> Published in jaunty-proposed 4 hours ago
[14:35] <RainCT> stefanlsd: still uploading?
[14:39] <stefanlsd> RainCT: yeah. sorry. its running now. I had a bzr dev come to my office, so i was bugging him with bzr questions!  :)
[14:48] <stefanlsd> RainCT: Its up
[15:15] <RainCT> argh not again that bug, the gears upload to Ubuntu is hanging at the last KB :/
[15:19] <stefanlsd> garyvdm: https://wiki.ubuntu.com/PackagingGuide/Recipes/PackageUpdate
[15:27] <stefanlsd> RainCT: still stuck?
[15:27] <persia> porthose, Congratulations!
[15:27] <RainCT> stefanlsd: yep
[15:27] <porthose> persia: ty
[15:27] <RainCT> Uploading gears_0.5.21.0~svn3334+dfsg.orig.tar.gz: 13811k/13812k
[15:30] <stefanlsd> RainCT: heh. do we do anything, or just wait, or poke someone?
[15:32] <RainCT> stefanlsd: just wait
[15:36] <Rail> stefanlsd: congrats!
[15:37] <stefanlsd> Rail: heys! congrats to you to! thanks for all your help!
[15:37] <persia> It uploaded?  Cool!
[15:37] <Rail> stefanlsd: FF 3.5 is awaiting ;)
[15:38] <stefanlsd> persia: RainCT busy uploading it... :)   (its kinda sticking, but yeah. got someone upstream to fix that license issue!)
[15:39] <persia> It's *huge*, but nice work with the licensing.
[15:42] <stefanlsd> persia: thanks! (and thanks for all your help also!) i cant believe how long its taken.
[15:43] <persia> Well, it's a huge package.  Few people would have dared to tackle it.
[15:44] <stefanlsd> yeah, hindsight is 20/20  :)
[15:45] <stefanlsd> garyvdm: http://www.debian.org/doc/debian-policy/ch-relationships.html
[15:49] <c_korn> why does the package text say that it is scilab-5.1-0ubuntu2 but it is scilab-5.1.1-6 (see the files at the right)? http://packages.ubuntu.com/karmic/scilab
[15:54] <garyvdm> stefanlsd:https://bugs.launchpad.net/ubuntu/+source/qbzr/+bug/393890
[16:03] <RainCT> stefanlsd: I'm away for some hours, will leave dput running
[16:04] <stefanlsd> garyvdm: http://wiki.debian.org/DebianPython/NewPolicy
[16:04] <stefanlsd> RainCT: ok. thanks! :)
[16:26] <dholbach> Can I interest somebody in giving a Packaging Training session at 02nd July, 06:00 UTC? https://wiki.ubuntu.com/Packaging/Training has lots of ideas for sessions
[16:32] <Laney> # Dealing with hideously packaged packages hahaha
[16:32] <Laney> Serious tact needed there
[16:34] <dholbach> Laney: interested in something on the list?
[16:34] <Laney> dholbach: not this weekend I'm afraid, maybe one after
[16:35] <Laney> wait, it's even earlier than the weekend
[16:35] <Laney> even worse!
[16:35]  * Laney has to run now anyway, bye
[16:35] <dholbach> Laney: thanks for considering it :)
[16:35] <dholbach> take care
[17:00] <DktrKranz> dholbach: I could sign up for a Python packaging one, I need to match some times, though.
[17:01] <dholbach> DktrKranz: match some times?
[17:02] <DktrKranz> dholbach: 18 UTC should be fine if I manage to get home in time, other times are no-go for me
[17:04] <dholbach> DktrKranz: ah ok - that sounds like August then
[17:04] <dholbach> :-)
[17:04] <DktrKranz> yeah
[17:04] <DktrKranz> and probably have some holidays, then :P
[17:05] <dholbach> ## * 16th August, 18:00 UTC, '''Python Packaging''', `DktrKranz`
[17:05] <dholbach> thanks muchly Luca!
[17:06] <DktrKranz> dholbach: I could eventually split apps from modules or extensions, since they should be handled separately
[17:06] <DktrKranz> and double my sessions
[17:06] <dholbach> DktrKranz: sounds fantastic
[17:07] <dholbach> DktrKranz: do you just want to update Packaging/Training with that info?
[17:07] <DktrKranz> I'll do
[17:07]  * dholbach hugs DktrKranz!
[17:07]  * DktrKranz hugs dholbach back
[17:07]  * DktrKranz wanted to do a session on his birthday, but missed by four days :)
[17:08] <dholbach> ah damn
[17:08] <dholbach> which day is it?
[17:08] <DktrKranz> aug 12, but I'll probably be on holiday with limited internet access, 16th is fine
[17:11] <dholbach> cool
[17:11] <dholbach> :-)
[17:13] <RoAkSoAx> Is there a way to know which values should go under Depends when packaging a pure python app?
[17:15] <DktrKranz> RoAkSoAx: do you mean how to discover which modules it imports/requires?
[17:16] <RoAkSoAx> DktrKranz, yes
[17:26] <kees> mok0: hi! sup?
[17:35] <DktrKranz> RoAkSoAx: you can use http://svn.debian.org/viewsvn/python-modules/tools/, if pacakge is not complex, I use grep :)
[17:37] <RoAkSoAx> awesome thanks DktrKranz
[17:38] <DktrKranz> RoAkSoAx: if you have some Python related questions, ping ;)
[18:10] <Ampelbein> DktrKranz: hi. may I ask your opinion on bug #377871 ? Should we go with the debian way and don't specify the interpreter directly?
[18:29]  * POX marks 16th August in the calendar ("show up on #ubuntu-classroom and make DktrKranz sweat" ;)
[18:37] <pochu> DktrKranz: are you giving a session?
[18:37] <pochu> oh
[18:37]  * pochu just read backlog :)
[18:45] <CarlFK1> how do I use "cvs diff' to make a .dpatch ?
[18:46] <CarlFK1> it doesn't seem to like:  diff -u -r1.70 dvgrab.cc
[18:46] <CarlFK1> --- dvgrab.cc	15 Jan 2009 08:12:37 -0000	1.70
[18:46] <CarlFK1> missing header for unified diff at line 11 of patch; can't find file to patch at input line 11
[18:53] <DktrKranz> pochu: yep, do you want to co-host it?
[18:54] <CarlFK1> apparently it doesn't like the datetime format
[18:54] <DktrKranz> POX: erm... I cancelled it... go for a walk instead :D
[19:03] <pochu> DktrKranz: I wouldn't mind, but I don't know if I'll be available that day
[19:03] <pochu> DktrKranz: remind me about it a few days before it and I'll tell you ;)
[19:03] <DktrKranz> pochu: so we can be two to swarm at POX's expert eyes :)
[19:04] <DktrKranz> *sweat
[19:10] <cabrey> is firefox-3.5 being packaged and is the firefox meta package going to point to the new FF?
[19:11] <CarlFK1> cabrey: firefox-3.5 is in the repo - duh no the 2nd 1
[19:11] <CarlFK1> 2nd Question
[19:11] <cabrey> the firefox-3.5 in the repo right now is beta4
[19:12] <CarlFK1> oh so it is.  missed that
[19:12] <CarlFK1> never mind me :)
[19:12] <cabrey> i don't understand why it is so bad to upgrade to FF3.5
[19:13] <cabrey> will provide a better experience to users
[19:13] <directhex> cabrey, define "stable"
[19:14] <cabrey> software that is declared stable
[19:16] <Pici> !ff35 | cabrey
[19:16] <Pici> Doesnt answer #2, but clarifies #1
[19:16] <cabrey> :)
[19:30] <POX> DktrKranz: if you want me to proof read your speech or something, just ping me
[19:33] <RoAkSoAx> DktrKranz, what do you grep when searching python modules for Depends ?
[19:33] <quadrispro> hi devfil
[19:33] <devfil> quadrispro, o/
[19:34] <DktrKranz> RoAkSoAx, I do a grep * -lroie "import", this is good for small packages, or you'll be flooded
[19:35] <RoAkSoAx> DktrKranz, and what about for Build-Depends ?? Should I just try to install and add there the packages need while installing?
[19:37] <jpds> DktrKranz: Why not uniq it?
[19:38] <DktrKranz> RoAkSoAx, do as for normal packages, add them if you need them
[19:39] <POX> RainCT: if upstream is sane, you can search for setup_requires in setup.py (for build dependencies) and install_requires (or package-egg/requires.txt) for runtime dependencies
[19:39] <DktrKranz> jpds, it works, but you still have to remove spaces
[19:40] <POX> RainCT: sorry, wrong nick
[19:40] <POX> RoAkSoAx: ^^
[19:40] <RoAkSoAx> DktrKranz, ok thanks :)
[19:40] <RoAkSoAx> POX, cool thanks :)
[19:40] <quadrispro> jdstrand: are you around? :)
[20:17] <cpscotti> Hey... I'm running out of coffee here.. could someone please check my package (I thing I already cleaned it for all "machine detectable" errors).. Its a python GUI for computer vision code generation. here is it: http://revu.ubuntuwire.com/p/harpia
[20:20] <cpscotti> mok0 warp10: since you are from the science team, you could help even more!
[20:36] <DktrKranz> cpscotti, tag it as python, I usually process them
[20:40] <cpscotti> on motu?
[20:41] <cpscotti> DktrKranz: how can I tag the package at revu?
[20:58] <DktrKranz> cpscotti, Tags: [edit], at the bottom of the page
[21:11] <cpscotti> DktrKranz: I see "Tags: python" but no "edit" link. Have you added the python tag? Does everybody have permissions to do that?
[21:32] <gaspa> geser: are you expert of launchpadlib?
[21:42] <RoAkSoAx> DktrKranz, when packaging a python app that for example installs things in /etc/httpd/conf.d instead of /etc/apache2/conf.d, can I modify the setup.py to fix this things?
[21:48] <cpscotti> RoAkSoAx: are those "things" data files or py programs?
[21:49] <RoAkSoAx> cpscotti, config files that allow the app to be accessed via apache
[21:50] <cpscotti> RoAkSoAx: i think you can relate them on the data_files list of setup.py
[21:51] <cpscotti> something like: data_files=[ ('/etc/httpd/conf.d', 'path2Theconfig')),...]
[21:54] <RoAkSoAx> cpscotti, for example, I have this: (wwwconf,  ['config/cobbler.conf']), where wwwconf is /etc/httpd/conf.d
[21:58] <cpscotti> RoAkSoAx: yeah.. that will do it
[22:52] <RainCT> stefanlsd: omg it's still hanging on the last KB :/
[22:53] <stefanlsd> RainCT: heh. maybe u should just abort it and try again?
[22:53] <Laney> dput?
[22:54] <RainCT> Laney: yep
[22:54] <Laney> known bug, check lp :(
[23:02] <droolpal> I am trying to test the new Phatch version, but I can not upgrade because of unmet deps: phatch:
[23:02] <droolpal>  Depends: libtiff-tools  but it is not installable
[23:02] <droolpal>  Depends: libjpeg-progs  but it is not installable
[23:02] <droolpal> how do I find what is messing up these dependencies
[23:02] <droolpal> ?
[23:21] <cjwatson> droolpal: 'sudo apt-get install phatch libtiff-tools libjpeg-progs'. Repeat down the chain until you get a useful message.
[23:50] <RainCT> stefanlsd: same again :/
[23:52]  * ajmitch mutters about buggy insecure packages