Re: Re: Subversion in sid / QA page
Bob Proulx wrote:
> I always like to see included a reason for the request such as at
> least one specific feature that the new version provides that isn't
> available in the current version. Just requesting a newer version
> because there is a newer version available isn't enough and is a pet
> peeve of mine.
Heh, same here. :-)
I do some work on a few OSS projects whose site hosts have moved to 1.7.
All my SVN client operations stopped functioning with a message saying that
the working checkouts were "too old (format 10 created by Subversion 1.6)",
and that I needed to run 'svn upgrade' in my working copies. Did that, went
back to work, didn't think much of it at the time.
Now I've moved to a different workstation setup, using Debian, and of course
those 1.7 working copies won't fly under 1.6. I had no luck trying to get
fresh checkouts using 1.6 (under the theory that the server will notice and
downgrade its actions, which IIRC the subversion server was always good
about doing), but now I don't have the error messages handy. Figured a 1.7
client would be the easiest solution.
> In any case, list why you want the newer version in your bts request.
> Then that bug log could become the place for the discussion of the
> newer version and why and what problems exist with it.
I think I'll hold off on filing a ticket for a while, in case the maintainer
is just on holiday. In the meantime I'll see if I can build the source
via the standard *nix steps instead of trying to figure out the new package
build system; debian/rules has changed a lot since the last time I looked
at it some six years ago.
Reply to: