[00:28] <micahg> ScottK: right, sorry, that's true as well :)
[01:45] <cdunlap> I am not sure this is the correct forum, but I have a quick question around packaging and expectations.  Would this be an appropriate place to ask?
[01:46] <ScottK> cdunlap: It depends.  If you are working on packages for Ubuntu, it is.  If not, #ubuntu-packaging might be better.
[01:46] <cdunlap> ScottK: I think this could be classified as a general packaging question
[01:47] <ScottK> I'd say ask then.
[01:47] <cdunlap> So I have been trying to learn how to package and I have been working through the information Daniel Holbach has been putting on OMGUbuntu.
[01:48] <cdunlap> When I try to 'make' the file it kicks back, what look to me, as errors with one of the files.  Is the expectation that the packager would fix these errors, or would the packager work with the developer of the application?
[01:49] <ScottK> "It depends"
[01:49] <ScottK> Sometimes the errors are due to packaging problems, sometimes it's an upstream issue.
[01:50] <cdunlap> is being able to tell the difference something you gain with experience or is it usually pretty evident?
[01:50] <ScottK> Sometimes even if it's an upstream issue, a packager will figure out a fix and let upstream know.
[01:50] <ScottK> Yes.
[01:50] <ScottK> Sometimes it's pretty evident, sometimes it's stuff it takes experience to understand.
[01:51] <cdunlap> I figured some of my troubles are because I am trying to figure it out.  Thanks for the clarification.  I do appreciate it.
[01:53] <ScottK> No problem.
[06:03] <alkisg> If I have a debian/upstart file, do I need to have debian/postinst and debian/postrm too? Or dh_installinit can create them for me?
[06:17] <Rhonda> It creates them
[06:25] <alkisg> Thank you, I was worried about this lintian warning: W: panoptes: script-in-etc-init.d-not-registered-via-update-rc.d /etc/init.d/panoptes
[06:26] <Rhonda> hmm
[06:27] <Rhonda> dpkg --info panoptes_*.deb  # does this list postrm/postinst?
[06:27] <Rhonda> Maybe you do need a dummy file then which includes the #DEBHELPER# marker.
[06:28] <alkisg> It has postinst, preinst and prerm
[06:28] <alkisg> All autogenerated
[06:28] <alkisg> And inside postinst:
[06:28] <alkisg> # Automatically added by dh_installinit
[06:28] <alkisg> update-rc.d -f panoptes remove >/dev/null || exit $?
[06:29] <alkisg> ...remove?
[06:30] <Rhonda> uh?
[06:30] <alkisg> I don't know why, but it calls update-rc.d remove in postinst! ????
[06:31] <alkisg> (using gdebi-gtk to look the scripts inside the .deb)
[06:42] <alkisg> It looks like dh_installinit only has this bug with upstart, if I put debian/init scripts instead, I get no lintian warnings and the automatically generated postinst is sane again
[06:43] <alkisg> Oh well I'll just revert the scripts from upstart to sysvinit again. Thanks :)
[07:14] <dholbach> good morning
[08:07] <alkisg> The "update-rc.d -f package remove" part earlier may there to remove the init.d links, as the upstart job should be used instead. I see it on packages that have a manual postinst too.
[08:08] <alkisg> And for the "script-in-etc-init.d-not-registered-via-update-rc.d" warning, I found a bug in launchpad, it was fixed in later lintian versions (I'm using lucid)
[08:15] <micahg> hi Q-FUNK, so have you sponsored bzr branches yet?
[08:15] <Q-FUNK> not that I can remember, no.
[08:16] <micahg> Q-FUNK: oh, well, if you're interested, I'm sure someone here can help you, https://code.launchpad.net/~jbicha/ubuntu/oneiric/gjs/1.29.18/+merge/76441, it's 3AM for me so I'm a little reluctant right now
[08:20] <Q-FUNK> ok
[13:34] <ScottSanbar> ApOgEE: Howdy!
[13:34] <ScottSanbar> (whoops)
[13:41] <alkisg> Which of those should I prefer to package a python app? http://www.debian.org/doc/packaging-manuals/python-policy/ap-packaging_tools.html
[13:41] <alkisg> Is distutils with debhelper a good choice, or should I go for CDBS?
[13:50] <geser> I'd go with debhelper
[13:52] <alkisg> Debhelper with plain distutils, right? Not dh_pysupport nor dh_pycentral... correct?
[13:53] <tumbleweed> --with python2
[13:53] <alkisg> Ah, thank you, /me reads about that ...
[13:56] <alkisg> Could someone suggest me a package that uses that, so that I could use it as a template?
[13:57] <tumbleweed> alkisg: so this is a simple python app. Does it also have a public python library? or is it not going to be useful for other python apps, and should be installed privatel?
[13:58] <alkisg> tumbleweed: It's separated into 2 parts. One daemon is using twisted, and a client/GUI is contacting the daemon part.
[13:58] <alkisg> Neither of them will be useful to external apps
[14:00] <tumbleweed> alkisg: ok, I don't have any packages excatly like that, but upnp-inspector is a simple python app that installs privately
[14:01] <tumbleweed> alkisg: do you install any twisted plugins? (i.e. for the daemon)
[14:01] <alkisg> Thank you, I'll look into that
[14:01] <alkisg> tumbleweed: yes, but I'd prefer to run them manually instead of as plugins, if I manage to do it
[14:02] <alkisg> twistd -f path/to/my/file.py or however else it works
[14:02] <tumbleweed> alkisg: ok, if you install a plugin, you should activate the twisted-plugins-cache trigger
[14:02] <ScottK> If it's using twisted it'll need to use the same python helper as twisted.
[14:02] <tumbleweed> twisted uses dh_python2 these days
[14:02] <alkisg> Good, some good news at last :)
[14:33] <ripps> I'm having some problems with a package that doesn't work anymore, can someone join me #ubuntu-packaging
[20:39] <ScottSanbar> Unit193:  I mean the fact that you clued me in - thanks ...
[20:39] <ScottSanbar> (whoops)