Closed achiang closed 13 years ago
Hi Alex, Unfortunately it failed to build for me on my build machines. Ideally I'd like it to be buildable right back to Jaunty, but at the very least we should support Lucid. There appear to be two problems: 1/ The build requires python-all >= 2.6.6-3 ( this is not available from the standard repos on anything less than Natty) 2/ The Natty build failed with a quilt error 'no orig.tar file found'
:-( Thanks
Ok, the initial target was debian sid aka unstable aka the latest and greatest. It should build fine on older ubuntu, but will take a little bit of backporting for the packaging.
1) Since Lucid is essentially stable now, I need to see if we can get new packages into it via the SRU process. Additionally, we'd need to think about whether it makes sense for upstream (here, github) to maintain the Lucid packaging or whether it makes more sense to host it in a PPA for Lucid (if the SRU route is unavailable to us).
2) You need to either download or create the .orig.tar.gz file. If you create it (which makes more sense); you can do so simply by tarring up the source directory and naming it: python-messaging_0.5.11.orig.tar.gz
Following on from discussions with Pablo and Alex, I think we now have a good solution where we move the debian directory out of the root, which was complicating things for alternative debian build procedures. For our upstream purposes we use a makefile which copies either a generic debian directory, or one to suit a certain target at package build time. e.g. make deb or make deb TARGET=ubuntu-lucid
The pure debian directory is being maintained outside of the repository by Alex and is used as a git submodule in his build process.
If everyone is happy let me know and I'll close this pull request, thanks
Yup, this sounds fine to me.
Please go ahead and close.
python-messaging has finally been accepted into the Debian archive:
http://packages.qa.debian.org/p/python-messaging.html http://packages.qa.debian.org/p/python-messaging/news/20111003T221750Z.html
The version that was accepted uses the packaging in my current branch. I've tried to document each change and the reasoning why it was necessary, so feel free to browse the commits and let me know if you have any questions.
Now, I request that you pull my changes into master so that we may remain sync'ed up from this point on. I'm happy to try and maintain the debian packaging in your tree and review any changes you may wish to make.
Let me know.
Thanks.