On 02/04/2014 01:44 PM, László Böszörményi (GCS) wrote: > Hi Michael, Stephen, > > On Mon, Feb 3, 2014 at 1:56 PM, Michael Haggerty <mhag...@alum.mit.edu> wrote: >> On 01/30/2014 05:01 PM, Stephen Oberholtzer wrote: >>> Package: cvs2svn >>> Version: 2.4.0 >>> Severity: serious >>> Tags: patch > [...] >>> The cvs2svn package fails to build from source with recent versions of rcs >>> due to a failed internal test. This is caused by the rcs v5.9 'co' command >>> deprecating '-V' in favor of '--version'. When cvs2svn executes 'co -V' to >>> test for its existence, co outputs a warning on stderr, which cvs2svn >>> mistakes for a failure. >>> >>> Attached is a patch that corrects this problem, so that the package builds. > Maybe an other thing changed since then, but last time I tried your > patch cvs2svn self-tests still failed. > >> I am the upstream maintainer of cvs2svn. The change that you have >> proposed was made in cvs2svn "trunk" in December 2013. So I agree that >> it is OK. > Do you have a list what's changed since 2.4.0 in the trunk?
Just yesterday I pushed a commit to trunk that updates the CHANGES file with an up-to-date list of all of the significant changes since 2.4.0. >> If it would be helpful, I could make an upstream release from the >> current trunk version (i.e., including this change). > I'll retry building of cvs2svn with the proposed patch and report > back if I get a test failure and its details or simply upload a fixed > packaged with that change. > You don't have to make a new upstream release if it's not the time > yet. Ie not stable enough or just not really tested, etc. There's not a lot of activity in the project so it is relatively arbitrary when to make a release. But if you don't need one then I'll gratefully spare myself the effort :-) Michael -- Michael Haggerty mhag...@alum.mit.edu http://softwareswirl.blogspot.com/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
