On Sat, Jul 04, 2009 at 03:18:48PM -0700, Russ Allbery wrote:
> Not that anyone gets this right in practice, but I think calling
> update-alternatives unconditionally in postinst is the correct way to
> handle the error rollback cases.
>
> You don't want to call it unconditionally in prerm because
Jonathan Wiltshire writes:
> I may be wrong, but you should probably test in your postinst what apt
> wants you to do (install, upgrade, abort etc). See
> /usr/share/debhelper/dh_make/debian/postinst.ex for an example. The
> summary at the top is useful. Blindly using 'update-alternatives
> --ins
(IANADD, so no upload from me - sorry)
On Sat, Jul 04, 2009 at 10:43:04PM +0100, Tony Houghton wrote:
> Lintian gave a couple of warnings because it thought I was trying to
> perform a NMU. Presumably a sponsor will update the system to list me as
> maintainer and that will be resolved?
At the mo
Acting on received advice I updated the previous maintainer's packaging
files and used a single package. roxterm 1.15.1-1 is ready for a
prospective sponsor to test and upload it.
Lintian gave a couple of warnings because it thought I was trying to
perform a NMU. Presumably a sponsor will update t
4 matches
Mail list logo
