[Pkg-Cyrus-imapd-Debian-devel] Cyrus22 ready for release?

[Sven Mueller]

Henrique de Moraes Holschuh wrote on 29/11/2005 17:03:
> I was just trying to upload r218 to experimental, but unfortunately
> svn-buildpackage seems to not know how to tag and close the upload.

Oh well....
That's also a side effect of the repository layout I chose before
knowing exactly what svn-buildpackage would like to see.
Calling svn-buildpackage to _build_ a release works fine, but I never
tried tagging with svn-buildpackage before (or I did, but it destroyed
more for my other package than it saved in terms of work needed).

So: If you have experience with svn-buildpackage tagging (and using the
merge method), all I really need is a description of how the repository
should be layed out. Once I have that, I can dump the current repository
to a dumpfile, manipulate that dump and reload it so that it has that
layout (and we keep all the revision info). I would drop the old
branches then however.

Also, I would like to know how we can create the needed dpatch files in
the future. Currently I can simply run dpatch-edit-patch inside the
workingcopy's source tree to create such a patch. How would we do that
with svn-buildpackage's merge mode?

> Since what we have in SVN doesn't seem to match the crappy documentation of
> svn-buildpackage, I will proceed without tagging.

Fine.

> Sven, please tag r218 as 2.2.12-1, and tell us how to proceed in the future
> :-)

As said: I would convert the repository to whatever svn-buildpackage
would like to see, but like you said, the documentation on this aspect
is really crappy with svn-buildpackage.

cu,
sven
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 186 bytes
Desc: OpenPGP digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-imapd-debian-devel/attachments/20051129/6c6b928a/signature.pgp