Re: Call for testing: cvs2bzr

Ian Clatworthy wrote:
> According to https://wiki.ubuntu.com/KarmicReleaseSchedule, Feature
> Freeze is August 27. So I think you want to be releasing 2.3.0 by Monday
> at the *absolute latest* to give those doing the upload time to sort out
> any packaging issues. Even that is probably leaving things a bit late:
> getting 2.3.0 out today (Friday 21/Aug) would be preferable I feel.
> 
> Here are some links of interest:
> 
> http://packages.ubuntu.com/karmic/cvs2svn
> https://wiki.ubuntu.com/SponsorshipProcess
> 
> As soon as a source release is available, you should contact the Ubuntu
> MOTU Developers and find someone who can help get it uploaded.

Ian,

I made the cvs2svn release over the weekend, but I am not going to have
time to figure out the Ubuntu packaging process and get it kick started
in time for karmic.  Perhaps you have experience with this and could
contact the right person?

Regarding the build failures for cvs2svn release 2.2.0, my guess is that
the problem is deprecation warnings from a new Python version, but the
error log doesn't include enough information to be sure.  (The output
from "run-tests.py -v" would be helpful.)

There is a reasonable chance that the problem has already been fixed in
cvs2svn release 2.3.0, and if not I'd be happy to work with the packager
to iron out any wrinkles.  (But I don't have a karmic system to test on.)

As far as packaging is concerned, there are a couple of things that are
new in 2.3.0:

- Two new top-level scripts (cvs2git and cvs2bzr)
- The man pages are not included in the tarball but rather generated
using "<command-name> --man"

Thanks,
Michael

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2387295

To unsubscribe from this discussion, e-mail: [[email protected]].