A quick progress report and a few questions... I struggled a bit with autoppa, but I think I've finally whipped it into shape. I noticed that there were no entries in debian/control.autoppa for Natty or Oneiric. I added the latter and switch it to use dh_python2. I should probably add a Natty PPA as well. Is there a particular reason why autoppa isn't set up for Natty, or is it just that no one ever got around to updating the package?
Only a few of the packages actually build though. I did get the Oneiric build to succeed locally, but I had to disable the test suite to do this. Please correct me if I'm wrong, but there's a fair bit of manual setup needed for both PostgreSQL and MySQL to get the test suite to succeed. I think these tests should be skipped if the manual setup isn't done. I've filed bug 867878 about this. I'm still having some local build failures on other distroversions, and will continue to suss those out locally before I upload new packages to the PPA. Or I can just go ahead and do an upstream tarball release to PyPI and Launchpad and work on the PPA afterward (this actually makes it more convenient for package building). If there are no objections and I can't get all packages built by COB tomorrow, I will probably go ahead and do that. What else? I'd like to get 0.19 into Debian too. Is there an official statement as to what Ubuntu versions will be supported in the PPA? From the control.autoppa file, it looks like we intend to build dapper, hardy, karmic, and lucid. maverick support seems spotty (the rules file seems incomplete for maverick). Do we need to build all the way back to dapper? Would it be enough to build just back to the last LTS (i.e. lucid)? -Barry
signature.asc
Description: PGP signature
-- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
