Archive for December, 2009
the emperor has new clothes bzr has just changed the base class for its test suite from ‘unittest.TestCase’ to ‘testtools.TestCase’. This change has cleaned up a bunch of test logic, deleted a significant amount of code (much of which was redundant with Python unittest) and added some useful and important features. bzr has only been […]
Filed under: Uncategorized | Leave a Comment
Tags: Bazaar, bzr, Python, testtools, unittest
Recently I’ve been working on the Python unittest API in my spare time, with a long term goal of making it possible to safely and sensibly glue many different plugins together into the core. Two important components of that goal are being able to extend the data included in a test result, and being able […]
Filed under: Uncategorized | 4 Comments
Tags: junit, Python, Subunit, testsupport, testtools, unittest
Bzr build-deb is very nice, but it can be very tricky to get started. I recently did a fresh debianisation of a project that is in bzr upstream, and I thought I’d record the recipe to make it work (at least until the various bugs making it hard re fixed). Assuming that the upstream uses […]
Filed under: Uncategorized | 2 Comments
Tags: Debian, packaging, ubuntu
As distributors we should not discourage upstreams that wish to generate binary packages themselves, rather we should cooperate with them, and ideally they will end up maintaining their stable release packages in our distributions. Currently the Debian and Ubuntu communities have a tendancy to actively discourage this by objecting when an upstream software author includes a debian/ directory in their shipped code. I don’t know if Redhat or Suse have similar concerns, but for the dpkg toolchain, the presence of an upstream debian directory can cause toolchain issues.
In this blog post, I hope to make a case that we should consider the toolchain issues bugs rather than just-the-way-it-is, or even features.
Filed under: Uncategorized | 14 Comments
Tags: packaging, ubuntu, upstream