[00:44] <YokoZar> ScottK: Can I just make a straight upload of r-base since it's not a new package (but rather a replacement for the older one) or does that need a freeze exception too?
[03:16] <ScottK> YokoZar: It's a new upstream release that's not just bugfixes, so it needs to be included.
[03:17] <YokoZar> ScottK: so attached to the bug report then
[03:17] <ScottK> Yes.
[05:59] <lamalex> Can anyone see why lintian gives me this? http://lintian.debian.org/tags/manpage-has-bad-whatis-entry.html on http://paste2.org/p/402746
[06:00] <lamalex> I don't understand what's not right- it looks fine t me
[06:23] <dholbach> good morning
[06:23] <lamalex> :) just barely
[07:18] <lamalex> so can anyone help me fix this manpage?
[07:22] <binarymutant> lamalex, on line 27 should there be a "."?
[07:24] <lamalex> binarymutant: I dont think that would create the warning lintian gives, would it?
[07:25] <lamalex> i guess ill try it and see..
[07:26] <lamalex> nope, still get it
[07:27] <binarymutant> lamalex, no clue, it could be lacking escape characters or something. srry :/
[07:28] <lamalex> binarymutant: no problem
[07:31] <lamalex> ahha! got it
[07:32] <lamalex> the name should be the binary name, not the application name
[07:32] <lamalex> tictactoe instead of Tic Tac To
[11:17] <sluimers> Hi there, Ive got a build error of which I don't know what to do with: http://launchpadlibrarian.net/30927603/buildlog_ubuntu-jaunty-amd64.ika_0.62~21_FAILEDTOBUILD.txt.gz
[11:18] <sluimers> It seems the amd64 version wants to use a uint from <sys/types.h>, how do I prevent that
[11:18] <sluimers> ?
[11:24] <shiki-> hello everyone. I got a problem with one of my packages: http://launchpadlibrarian.net/30930407/buildlog_ubuntu-intrepid-amd64.mpg123_1.7.2-3ubuntu1~ppa2~intrepid1_FAILEDTOBUILD.txt.gz . here is the file which it refers to: http://pastebin.com/d5534de35
[11:27] <gnomefreak> does cupsddk replace cupsddk-drivers?
[12:07] <shakaran> hi, I need some help for create a .deb (exactly with signing gpg)
[12:08] <shakaran> I run dpkg-buildpackage -rfakeroot and get this:
[12:08] <shakaran> gpg: [stdin]: clearsign failed: secret key not available
[12:09] <shakaran> but gpg --list-secret-keys show me a key
[12:09] <shakaran> what I need for signing my .deb?
[12:10] <azeem_> shakaran: I think you need to specify which key you want to sign with via the -k option
[12:10] <azeem_> shakaran: however, it is usually better to pass the -us -uc options to dpkg-buildpackage in order to skip signing
[12:10] <azeem_> and do the signing later on using debsign
[12:11] <shakaran> how to use debsign?
[12:11] <shakaran> a guide? I search on google?
[12:11] <azeem_> it has a manpage I think
[12:11] <shakaran> ok, I search now, thanks
[12:20] <shakaran> I am doing wrong.
[12:20] <shakaran> debsign -k 1DEEE63D myprogram_0.0.1-0ubuntu1.dsc
[12:20] <shakaran> debsign: Only a .changes, .dsc or .commands file is allowed as argument!
[12:22] <azeem_> shakaran: remove the space between the -k and your keyid
[12:23] <shakaran> oh, was easy! thanks again
[12:51] <shakaran> another question, I have in the file rules a command for copy my binary to /usr/bin
[12:51] <shakaran> But the command dont work
[12:51] <shakaran> cp myapp $(CURDIR)/debian/usr/bin/myapp
[12:51] <shakaran> if I put with sudo dont work
[12:55] <shakaran> I need more privileges for copy in /usr/bin?
[12:59] <shakaran> some help please?
[13:00] <azeem_> what do you mean with dont work?
[13:01] <azeem_> do you get an error message?
[13:04] <shakaran> $ myapp
[13:04] <shakaran> bash: /usr/bin/myapp: No such file or directory
[13:04] <sebner> shakaran: where is myapp locatet?
[13:04] <sebner> *located
[13:05] <shakaran> I made a shell script for run in /usr/share/myapp/myapp.py
[13:05] <shakaran> /usr/bin/myapp invoque to /usr/share/myapp/myapp.py
[13:05] <azeem_> shakaran: just copying things under $(CURDIR)/debian is not enough, you need to make sure it is actually getting into the .deb at the end
[13:06] <sebner> shakaran: yeah and where is your shell script myapp currently?
[13:06] <shakaran> on myapp-0.0.1/myapp
[13:07] <sebner> shakaran: cp $(CURDIR)/myapp $(CURDIR)/debian/myapp/usr/bin/myapp
[13:07] <azeem_> shakaran: look into dh_install to install it properly so thata it ends up in the .deb
[13:08] <shakaran> oh, maybe is for $(CURDIR)
[13:08] <shakaran> My actual command is:
[13:08] <shakaran> cp ./myapp $(CURDIR)/debian/usr/bin/myapp
[13:09] <sebner> shakaran: your commend can't work. $(CURDIR) = myapp-0.0.1 and you have to use debian/myapp/usr/foo because debian/usr doesn't exist
[13:10] <shakaran> I do this before:
[13:10] <shakaran> mkdir -p $(CURDIR)/debian/usr/bin
[13:10] <shakaran> then /usr exists no?
[13:11] <sebner> shakaran: please don't do such weird stuff. For creating folders there is debian/dirs and it won't be in the archive. You want /debian/myapp/usr/bin
[13:12] <shakaran> ok, I gonna try
[13:15] <shakaran> yeah, it works ;) thanks
[13:15] <sebner> shakaran: installing the shell script should be done by makefile/python install though if it's in the upstreams tarball
[13:16] <shakaran> ok
[14:31] <sistpoty|work> hi folks
[14:31] <iulian> Hey.
[14:32] <DktrKranz> hey sistpoty|work
[14:32] <sistpoty|work> hi DktrKranz and iulian
[14:46] <qnix> hi, I forgot how to build a source package even if I can sign it (it's a packge from another dude)
[14:46] <lool> -kyou
[14:46] <lool> e.g. debuild -klool
[14:46] <lool> To disable signing, -us -uc
[14:46] <lool> qnix: Check the dpkg-bp and debuild man pages for the available options
[14:47] <qnix> ha, that's it. I had the -uc, but the -us was missing.
[14:47] <qnix> thanks a lot
[14:59] <bddebian> Heya gang
[15:00] <sistpoty|work> hi bddebian
[15:00] <bddebian> Hi sistpoty|work, congrats! :)
[15:00] <sistpoty|work> hm? what are you congratulating me for?
[15:01] <bddebian> Oh nevermind, wrong person, I'm not awake yet.  I was thinking you just got married but I was confusing you with someone else :)
[15:01] <sistpoty|work> heh, well, I know whom you confused me with ;)
[15:01] <bddebian> :)
[15:04] <qnix> Is it safe to rebuild the intrepid gcc 4.3.2 package for hardy, and install it ? Or it could be a few packages that could have be built against the old version ?
[16:25] <IntuitiveNipple> Is there an in-depth guide to python-support (for apps) or a mailing-list available somewhere?
[16:33] <DktrKranz> IntuitiveNipple: internals guide, or "How to implement stuff with pysupport" ?
[16:35] <IntuitiveNipple> I think 'internals' - I've got a package built using pysupport and the deb looks good and it installs fine. The problem is, python-support compiles to /var/lib/python-support/pythonX.Y/<package>/ and adds symlinks to the source in /usr/share/python-support/<package>, but it isn't linking any non-python supporting files. In this case, it is the application's Glade interface definitions in a sub-directory of one of the module directories.
[16:37] <DktrKranz> it does so for python only files, I see no reason for glade files to be under python directory
[16:37] <DktrKranz> IIRC there's a specific directory for glade files
[16:37] <IntuitiveNipple> I'm wondering if the way to do it is have the glade files installed to /usr/share/<package/glade/ - but if I do that, the upstream authors would have to refactor the existing source quite dramatically since it expects to find its glade files in a sub-dir of the application module
[16:38] <IntuitiveNipple> Locations the app expects to find things are hard-coded relative to the app's main() module
[16:38] <DktrKranz> hmm
[16:38] <IntuitiveNipple> indeed! :D
[16:39] <IntuitiveNipple> I've been humming for the last 24 hours trying to find documentation that describes this kind of scenario.
[16:39] <DktrKranz> http://svn.debian.org/viewsvn/collab-maint/deb-maint/python-support/trunk/README?revision=13985
[16:39] <DktrKranz> these are pysupport internals, but code is easy enough to be fully understandable
[16:40] <IntuitiveNipple> Yes, I've read the README several times but it doesn't provide any guidance for this kind of issue.
[16:41] <IntuitiveNipple> If there were something saying "python-support" enabled packages will separate python and non-python files to different paths, so the application may need to be patched, I at least know what is required :)
[16:41] <DktrKranz> and you won't find in pysupport as well
[16:42] <DktrKranz> but wait
[16:42] <DktrKranz> is it a standalone app?
[16:42] <DktrKranz> e.g. no public modules, or extensions?
[16:42] <IntuitiveNipple> define 'standalone' ? It's called "openshot" (a non linear video editor) and it depends on the MLT framework
[16:42] <DktrKranz> it's an application?
[16:43] <IntuitiveNipple> so no, nothing public or extensions and it is an application
[16:43] <DktrKranz> does any other part depend on one of its components?
[16:43] <IntuitiveNipple> I've already added a python-mlt package to 'mlt' which openshot depends on
[16:43] <DktrKranz> (part of Ubuntu archive)
[16:43] <IntuitiveNipple> no, openshot is new. I'm doing the packaging for the very first time
[16:44] <IntuitiveNipple> It depends on several mlt/ffmpeg/etc/ packages that are in my PPA since they need newer upstream releases than are in the archives so far
[16:44] <DktrKranz> good, so it can be self-contained in a private directory
[16:44] <IntuitiveNipple> Yes, it can
[16:45] <DktrKranz> so, things are getting easier
[16:45] <DktrKranz> does it use distutils?
[16:45] <IntuitiveNipple> I've created a distutils setup.py for generic cross-distro installations and added debian/unbuntu specific stuff in debian/openshot.{install,postinstall,postrm}
[16:46] <IntuitiveNipple> yes, it does... that bit and pysuport with CDBS works nicely
[16:46] <DktrKranz> you can instruct distutils to install things under /usr/share/pkgname
[16:46] <DktrKranz> and then provide a symlink in /usr/bin pointing to /usr/share/<app>/<applauncher>
[16:47] <DktrKranz> and you're in business!
[16:48] <IntuitiveNipple> hmmm... ok, how to tell distutils the install location when using CDBS? I've been looking at the CDBS web doc and it isn't clear there's a CDBS_ variable for that
[16:49] <IntuitiveNipple> The only one I thought might be it is "DEB_PYTHON_PRIVATE_MODULES_DIRS"
[16:49] <IntuitiveNipple> but the description isn't too precise on its intent
[16:49] <DktrKranz> mh... look at distutils.mk, it has something to pass to setup.py install
[16:50] <DktrKranz> I don't remember variable name, though
[16:50] <IntuitiveNipple> do you mean "python-distutils.mk" ?
[16:50] <pochu> to install a module in a private dir?
[16:50] <IntuitiveNipple> pochu: to install the entire app in a private dir :0
[16:51] <pochu> try --install-lib
[16:51] <pochu> if you're using CDBS: DEB_PYTHON_INSTALL_ARGS_ALL = --install-lib=usr/share/emesene
[16:52] <IntuitiveNipple> Does the 'lib' affect the fact it is an application in any way?
[16:53] <IntuitiveNipple> looking at python-distutils.mk I think I'd need to set DEB_PYTHON_INSTALL_ARGS_$(cdbs_curpkg)
[16:54] <IntuitiveNipple> because the CDBS script sets DEB_PYTHON_INSTALL_ARGS_ALL already
[16:54] <IntuitiveNipple> e.g.: DEB_PYTHON_INSTALL_ARGS_ALL = --no-compile -O0 --install-layout=deb
[16:55] <DktrKranz> it is DEB_PYTHON_INSTALL_ARGS_ALL += --install-lib=/usr/share/<app> --install-scripts=/usr/share/<app>
[16:57] <IntuitiveNipple> ahhh, I see the way you're thinking :)
[16:57] <IntuitiveNipple> I was forgetting about delayed evaluation of the variables in the makefile
[16:58] <IntuitiveNipple> I'm testing the build/install/execution now
[16:59] <DktrKranz> you have to provide symlinks as above, or adjusting sys.oath
[17:00] <DktrKranz> *path
[17:10] <IntuitiveNipple> Fab guys, thanks! the .deb shows the new locations... I just have to alter setup.py now to install the glade files in a sub-dir and it ought to start.
[17:19] <zooko`> k zooko_work
[17:20] <DktrKranz> IntuitiveNipple: check if your package has a .private file
[17:21] <IntuitiveNipple> I don't see one listed via Gdebi... let me check in the installed directory
[17:25] <IntuitiveNipple> DktrKranz: No .private file under /usr/share/openshot
[17:34]  * sistpoty|work heads home... cya
[17:45] <DktrKranz> IntuitiveNipple: it's not in /usr/share, do dpkg -c *.deb | grep private
[17:46] <IntuitiveNipple> DktrKranz: No, there is no 'private' file
[17:51] <IntuitiveNipple> DktrKranz: Thanks for all your help... the app is now partially starting although needs some changes to more path assumption in looking for files. I'll revisit the 'private' indicator another time. I assume that should be set by distutils ?
[18:17] <zooko`> I see a pair of tickets which are duplicates.
[18:17] <zooko`> Do I have the power to link them together?
[18:17] <zooko`> If not, what would it take to give me that authority?
[18:19] <andv> zooko, you need to be member of bug-control LP team
[18:19] <andv> zooko, which requires full understanding of how bugs reports works / priorities etc
[18:19] <zooko`> Sounds like a lot of authority.  Is there a way to give me such authority but only for bugs related to my projects?
[18:19] <james_w> no you don't
[18:20] <zooko`> Projects of which I'm the maintainer?
[18:20] <james_w> anyone can duplicate bugs can't they?
[18:20] <andv> zooko, I guess yes
[18:20] <zooko`> How doI do it?
[18:20] <zooko`> I explored the UI but didn't see it.
[18:20] <andv> james_w, not really sure
[18:20] <james_w> "Mark as duplicate" under the bug title
[18:20] <james_w> just above the package name
[18:20] <zooko`> james_w: thanks.
[18:21] <zooko`> How can I see what are the other duplicates already makred as duplicated of this ticket?
[18:21] <andv> at your right side
[18:21] <james_w> "Duplicates" list on the right
[18:21] <andv> yeah
[18:21] <zooko`> Thanks!
[18:21] <andv> yw
[18:22] <zooko`> Here's another question.  This package of which I'm the upstream maintainer -- pycryptopp -- was uploaded to REVU, but then it was instead synced from Debian.
[18:22] <zooko`> How do I mark the REVU item as "duplicate" of the please-sync ticket?
[18:22] <andv> what do you mean with REVU item?
[18:22] <zooko`> http://revu.ubuntuwire.com/p/pycryptopp
[18:23] <andv> you should ask to have it archived
[18:23] <james_w> done
[18:24] <zooko`> james_w: you archived the REVU page for pycryptopp?
[18:24] <james_w> yeah
[18:24] <zooko`> Thanks.
[18:24] <james_w> np
[18:28] <Laney> geser: do you know what changed in the LP API to break getSourcePackage?
[18:29] <geser> bug 418802?
[18:30] <james_w> I think I'm just going to re-upload the older python-wadllib
[18:31] <Laney> ValueError: Invalid value '"Published"' for parameter 'status': valid values are: "Pending", "Published", "Superseded", "Deleted", "Obsolete"
[18:31] <Laney> that error
[18:32] <Laney> is that the same thing?
[18:32] <geser> yes
[18:32] <Laney> ok
[18:32]  * Laney grabs the older wadlib then
[18:35] <geser> james_w: is the old python-launchpadlib also affect by the problem that keeps python-oauth out of main? as it embeds a copy of it (according to a comment on the MIR)
[18:36] <Laney> which version is the most recent unbugged one?
[18:36] <geser> current - 1
[18:36] <Laney> makes sense
[18:36]  * Laney should check timestamps
[18:36] <james_w> well, the old launchpadlib is in main
[18:36] <james_w> was, sorry
[18:37] <james_w> so python-oauth *could* be promoted based on that
[18:37] <james_w> however, ubuntuone also embeds a copy, and so we want to fix that
[18:37] <james_w> but they have some issues with it
[18:37] <james_w> so we're at a bit of an impasse
[18:37] <Laney> can't they continue to use their bundled one?
[18:38] <james_w> not for release
[18:38] <Laney> I mean, if that's what they're currently doing then there's no change right
[18:38] <geser> I can understand it but isn't the problematic code already in main (as part of python-launchpadlib (the old version as the new doesn't build currently))?
[18:38] <james_w> it's currently in main *twice*
[18:38]  * Laney has forgotten what he was initially doing
[18:39] <james_w> so having it in as a separate package is fine from that point of view
[18:44] <geser> and if the code is already in main (as embedded copies) it shouldn't block the MIR of a separate package for it IMHO
[18:46] <james_w> well, the issue is that we probably don't actually want the package in main by release
[18:46] <james_w> does putting it in now make that harder?
[18:46] <james_w> probably not
[18:47] <zooko`> How can I find a list of all packages that depend on python-foolscap?
[18:47] <geser> if the code is that problematic should launchpadlib be moved to universe instead till it's fixed?
[18:48] <james_w> it's not problematic for launchpadlib's usage
[18:48] <zooko`> james_w: could you please archive this REVU page, too: http://revu.ubuntuwire.com/p/zfec
[18:48] <james_w> rdepends:   python-apport
[18:48] <james_w> geser: ^that's why
[18:49] <slayton> how long after a package is accepted into debian unstable will it make it into the ubuntu repositories
[18:49] <james_w> zooko: it is already archived
[18:49] <zooko`> james_w: okay, thanks.
[18:49] <james_w> slayton: currently it won't get in until 10.04 opens for development at the start of November
[18:50] <geser> currently main has a source version of python-launchpadlib not matching the published binaries, this should be probably also fixed before release
[18:50] <james_w> it will be
[18:50] <slayton> is 10.04 a lts?
[18:50] <james_w> dobey is currently working on an alternative to python-oauth that he hopes to get everyone using in karmic
[18:50] <zooko`> Here is the package web page for python-foolscap, and I don't see any mention of other packages that depend on it: http://packages.ubuntu.com/karmic/python-foolscap
[18:50] <zooko`> Does that mean that there are none?
[18:50] <james_w> that could well be the  way we go
[18:51] <james_w> % apt-cache rdepends python-foolscap
[18:51] <james_w> python-foolscap
[18:51] <james_w> Reverse Depends:
[18:51] <james_w>   ipython
[18:51] <james_w> zooko`: ^
[18:52] <zooko`> james_w: thanks!
[18:55] <james_w> geser: ok, I have permission to put it in main and track it for release
[18:55] <james_w> geser: thanks for talking sense in to me :-)
[18:57] <geser> np :)
[19:32] <sluimers> Hi, I have a question. I've got a failedtobuild error and I don't know how to solve it. -> http://launchpadlibrarian.net/30927603/buildlog_ubuntu-jaunty-amd64.ika_0.62~21_FAILEDTOBUILD.txt.gz
[19:32] <sluimers> It's for PPA
[19:33] <sluimers> I want to put something on PPA
[19:34] <sluimers> and for some reason the program I'm trying to put on doesn't want to be built in amd64 because of a duplicate uint. Problem is, I don't want to use usr/include/sys/types.h at all
[19:35] <sluimers> Another thing is, for reason the program itself doesn't end up in the pacakage.
[19:37] <mzz> I suspect getting rid of that (indirect) sys/types.h include would be much harder than getting rid of the conflicting definition in the package, but c++ (or c for that matter) really isn't my strongest language
[20:30] <wildnfree_> !help register
[20:50] <sistpoty> crack... hard-coded dependencies against libraries... ffmpeg transition isn't as easy as I thought
[20:50]  * sistpoty admits to have missed dvdauthor's hardcoded one :(
[20:51] <sistpoty> dvdstyler even
[20:52] <sistpoty> btw.: if anyone wants to help out: apt-cache rdepends libavutil-unstripped-49
[20:53] <sistpoty> anything in that list needs to get rebuild to pick up the new shlibs dependencies. You can see if it worked out if there are no more -unstripped dependencies in the resulting binary
[20:53] <sistpoty> instead it should be "... | ...-extra"
[20:53]  * sistpoty walks the list from top to bottom right now, and I'm at zoneminder
[20:54] <sistpoty> oh, and if s.th. ftbfs, or the dependencies don't go away, please inform me, I'll add that to the trouble candidates lists
[21:13] <sluimers> !help packaging
[21:15] <sluimers> !help they're after me!
[21:15] <sluimers> okay :)
[21:15] <sluimers> Hi, I have a question. I've got a failedtobuild error when tryng to upload my PPA and I don't know how to solve it. -> http://launchpadlibrarian.net/30927603/buildlog_ubuntu-jaunty-amd64.ika_0.62~21_FAILEDTOBUILD.txt.gz
[21:16] <sluimers> For some reason the program I'm trying to put on doesn't want to be built in amd64 because of a duplicate uint. Problem is, I don't want to use usr/include/sys/types.h at all
[21:22] <sistpoty> sluimers: then don't include it? (or did a dependency include types.h?)
[21:23] <sluimers> I don't know how it gets included
[21:24] <sluimers> could be a dependency yes
[21:25] <sluimers> If I only knew where it was included
[21:25] <sistpoty> sluimers: I assume looking at ./common/port.h:44 might shed more light?
[21:27] <sluimers> It's just a bunch of typedefs
[21:28] <sistpoty> maybe grep for types.h?
[21:39] <sluimers> thanks, not sure if it'll work by turning "types.h" into "common/types.h" (because the program I'm trying to upload to the PPA also has a types.h), but I'll test it.
[22:04] <arvind_khadri> what does dpkg-source -x do??
[22:05] <geser> eXtracts a source package
[22:05] <arvind_khadri> ok, so it necessary to do before we do fakeroot debian/rules?
[22:07] <geser> yes
[22:20] <YokoZar> ScottK (or others): If I have a package that I uploaded a couple weeks ago but was rejected due to an incomplete copyright file, do I need a feature freeze exception to upload it?
[22:20] <YokoZar> (I've since fixed it)
[22:26] <sistpoty> YokoZar: if it was in the new queue before FF, you don't need an FFe
[22:26] <sistpoty> YokoZar: just make sure to find an archive admin to review it again
[23:21] <c_korn> I add a line 'm4_include([m4/intltool.m4])' in aclocal.m4 but after running autogen.sh the line is disappeard. any idea why ?
[23:21] <c_korn> I need that m4 file because a Makefile.am uses it
[23:22] <sistpoty> c_korn: afaik aclocal.m4 is autogenerated
[23:22] <sistpoty> c_korn: you could try acinclude.m4 though
[23:24] <c_korn> sistpoty: this file does not exist. I wonder why this m4 file is not included although it is required
[23:26] <sistpoty> c_korn: hm... actually on a second thought, the configure.{ac|in} should get this straight, given that you b-d on intltool
[23:27] <c_korn> b-d? build-depend ?
[23:27] <sistpoty> yep
[23:28] <c_korn> intltool is installed, yes
[23:28] <sistpoty> hm...
[23:29] <c_korn> is a line like "IT_PROG_INTLTOOL([0.35.0])" required in configure.ac to get it right ?
[23:31] <sistpoty> c_korn: that macro doesn't sound too wrong to me (maybe except for the version)... but I must admit that I'm a little bit clueless myself right now
[23:32] <sistpoty> let me look at the autoconf documentation for a second ;)
[23:32] <c_korn> hm, I added it. now I get this error http://pastebin.com/d5e22d5c3
[23:32] <c_korn> there is no po directory actually
[23:36] <sistpoty> but there's a directory with translations?
[23:51] <c_korn> I think I messed something up
[23:51] <c_korn> all I want to have is some code in Makefile.am to install a gconf schema
[23:54] <sistpoty> hm... sorry, can't really help you there, haven't done that myself yet
[23:55] <c_korn> ok, thanks anyway