[Pkg-isocodes-devel] r771 - branches

Christian Perrier bubulle at debian.org
Mon Jan 15 07:08:38 CET 2007


Quoting Christian Perrier (bubulle at alioth.debian.org):
> Author: bubulle
> Date: 2007-01-14 20:15:47 +0100 (Sun, 14 Jan 2007)
> New Revision: 771
> 
> Added:
>    branches/etch/
> Log:
> Branch version 1.0 as "etch"


My intent is to upload a 1.0a-1 package which would be exactly 1.0-1
*without* the autogenerated files. This is the condition for the
package to be accepted by the release managers in etch.

The 1.0->1.0a change is motivated by the .orig.tar.gz tarball being
changed, hence the version "bump".

As a consequence, that would be the good moment to start a branch for
etch, given that Alastair committed, in trunk, changes that are not
suitable for etch.


While building the 1.0a package from the etch branch, I've been
surprised by the missing ./configure and all Mafefile.in missing files
in the SVN.

That means that the package can't be built from a SVN export, which is
IMHO infortunate.

Have there been any reasons for this or should I just add these files
to the SVN (both branches and trunk, actually)?

Waiting for your advices, Alastair and Tobias.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-isocodes-devel/attachments/20070115/b3f16fe2/attachment.pgp


More information about the Pkg-isocodes-devel mailing list