<div class="gmail_quote">On Sun, Apr 18, 2010 at 5:43 PM, Daniel Burrows <span dir="ltr"><<a href="mailto:dburrows@debian.org">dburrows@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi all,<br>
<br>
*PLEASE NOTE: this email only concerns the repository used to create<br>
Debian packages, which is separate from the repository where active<br>
aptitude development takes place. Most of you won't be affected at<br>
all.*<br>
<br>
I just noticed that hg-buildpackage has been removed from Debian (as<br>
the result of setting up a new development workstation that hadn't been<br>
linearly upgraded from the days of etch). I could switch to<br>
mercurial-buildpackage, but it looks like there's no way to save my<br>
history anyway, so there's no particular reason to stay with mercurial.<br>
And I actually would prefer git to mercurial these days.<br>
<br>
So, I'm currently considering moving to git-buildpackage. The whole<br>
git toolchain feels a little cleaner to me and appears to have more<br>
support from the community at large. I'm hoping that it'll be a long<br>
time before I have to switch VCSes because the tools I use were<br>
abandoned.<br>
<br>
<br>
<br>
The 0.6.2 release is going to be created without any VCS for the<br>
Debian package, as a stopgap measure until I figure out exactly what to<br>
do and get a new toolchain set up.<br><br></blockquote><div><br></div><div>git-buildpackage works pretty well for me and is flexible enough to let me abuse it in various ways. Importing the mercurial history shouldn't be too hard.</div>
<div><br></div><div>Cheers</div><div><br></div><div>Arthur</div></div><br>