On Wed, Mar 25, 2009 at 12:50:48AM +0000, Tristan Greaves wrote:
> I'll probably shy away from sid for now. Is it sufficient for me to fix
> the standard lintian warnings thrown by my system?
You can't avoid sid - your upload will be targetting it, and you must
build and test your package against it. That doesn't mean you have to
install it though, you can run lintian as part of a mixed system:
- add an unstable line to sources.list
- tell apt to stick with stable in /etc/apt/apt.conf:
APT::Default-Release "stable";
- install lintian from unstable:
aptitude install lintian/unstable
For building, look at pbuilder and its variant, cowbuilder (much
faster).
> This will be easier said than done -- the direct changes seem pretty
> horrific (all sorts of changes made to the build system). It might be
> something I tackle more in the next step, which is to bring in the
> latest version of siege from upstream.
If there's a new upstream available anyway, why not save an upload and
go straight to that? It's kinder to the buildds, the mirrors and the
users who will be downloading the package after each upload; on the
other hand, if you're fixing an urgent bug, I agree that getting it done
while you work on the new upstream is preferable.
> Thanks,
>
> Tris.
--
Jonathan Wiltshire
PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52
Attachment:
signature.asc
Description: Digital signature