Il giorno Wed, 6 Feb 2008 22:45:26 +0900
Charles Plessy <charles-debian-nospam@plessy.org> ha scritto:
> Le Wed, Feb 06, 2008 at 01:42:42PM +0000, hanska-guest@alioth.debian.org a
> écrit :
> > Log:
> > [svn-upgrade] Integrating new upstream version, t-coffee (5.57)
>
> Hi David,
Hi Charles,
> I should have fixed the watch file before: it checks for alpha versions!
> Upstream confirmed that we should stick to stable releases (5.56 for the
> moment).
Uhm... well, how are alpha versions recognized? This is uscan's output:
$ uscan
...
T-COFFEE_distribution_Version_5.54.tar.gz
T-COFFEE_distribution_Version_5.55.tar.gz
T-COFFEE_distribution_Version_5.56.tar.gz
T-COFFEE_distribution_Version_5.57.tar.gz
Newest version on remote site is 5.57, local version is 5.57
=> Package is up to date
-- Scan finished
$
Is it that (meaningless, to me) scheme that even numbers are "stable" and odd
numbers are "unstable"? (i.e. 5.54, 5.56 -> stable; 5.55, 5.57 -> unstable)
Anyways, I believe we could use branches for situations like this. I'll have to
check some subversion documentation though.
Thank you for noticing this.
David (who is doing some general work today :P)
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
Attachment:
signature.asc
Description: PGP signature