User1: User3 right, sorry, that's true as well :)
User2: 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?
User3: User2 It depends.  If you are working on packages for Ubuntu, it is.  If not, #ubuntu-packaging might be better.
User2: User3 I think this could be classified as a general packaging question
User3: I'd say ask then.
User2: 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.
User2: 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?
User3: "It depends"
User3: Sometimes the errors are due to packaging problems, sometimes it's an upstream issue.
User2: is being able to tell the difference something you gain with experience or is it usually pretty evident?
User3: Sometimes even if it's an upstream issue, a packager will figure out a fix and let upstream know.
User3: Yes.
User3: Sometimes it's pretty evident, sometimes it's stuff it takes experience to understand.
User2: I figured some of my troubles are because I am trying to figure it out.  Thanks for the clarification.  I do appreciate it.
User3: No problem.
User4: 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?
User5: It creates them
User4: 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
User5: hmm
User5: dpkg --info panoptes_*.deb  # does this list postrm/postinst?
User5: Maybe you do need a dummy file then which includes the #DEBHELPER# marker.
User4: It has postinst, preinst and prerm
User4: All autogenerated
User4: And inside postinst:
User4: # Automatically added by dh_installinit
User4: update-rc.d -f panoptes remove >/dev/null || exit $?
User4: ...remove?
User5: uh?
User4: I don't know why, but it calls update-rc.d remove in postinst! ????
User4: (using gdebi-gtk to look the scripts inside the .deb)
User4: 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
User4: Oh well I'll just revert the scripts from upstart to sysvinit again. Thanks :)
User6: good morning
User4: 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.
User4: 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)
User1: hi Q-FUNK, so have you sponsored bzr branches yet?
User1: 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
User7: ApOgEE: Howdy!
User7: (whoops)
User4: Which of those should I prefer to package a python app? http://www.debian.org/doc/packaging-manuals/python-policy/ap-packaging_tools.html
User4: Is distutils with debhelper a good choice, or should I go for CDBS?
User8: I'd go with debhelper
User4: Debhelper with plain distutils, right? Not dh_pysupport nor dh_pycentral... correct?
User9: --with python2
User4: Ah, thank you, /me reads about that ...
User4: Could someone suggest me a package that uses that, so that I could use it as a template?
User9: User4 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?
User4: User9 It's separated into 2 parts. One daemon is using twisted, and a client/GUI is contacting the daemon part.
User4: Neither of them will be useful to external apps
User9: User4 ok, I don't have any packages excatly like that, but upnp-inspector is a simple python app that installs privately
User9: User4 do you install any twisted plugins? (i.e. for the daemon)
User4: Thank you, I'll look into that
User4: User9 yes, but I'd prefer to run them manually instead of as plugins, if I manage to do it
User4: twistd -f path/to/my/file.py or however else it works
User9: User4 ok, if you install a plugin, you should activate the twisted-plugins-cache trigger
User3: If it's using twisted it'll need to use the same python helper as twisted.
User9: twisted uses dh_python2 these days
User4: Good, some good news at last :)
User10: I'm having some problems with a package that doesn't work anymore, can someone join me #ubuntu-packaging
User7: Unit193:  I mean the fact that you clued me in - thanks ...
User7: (whoops)
ubuntu-motu
Ubuntu IRC