Re: Subversion in sid / QA page

[Farmbuyer]

Jochen Spieker wrote:
> > 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.
>
> This is expected behaviour:
> http://subversion.apache.org/docs/release-notes/1.7.html

Yep, I read through those when I went hunting for an updated package.  So far
there haven't been any surprises in this experience, except for the weirdness
trying to build from deb-src.


> > 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),
>
> True, and it should still be possible to do a checkout from an SVN 1.7
> server using a 1.6 client.

Dunno what was up, then.  If I try it again I'll do it inside a script(1)
session and keep the errors around.

Thanks all!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camk0gmocvm5j6faixp1kx9-kfxhiforsfyxoyedtfoq-1ds...@mail.gmail.com

Re: Re: Subversion in sid / QA page

[Jochen Spieker]

Farmbuyer:
> 
> 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.

This is expected behaviour:
http://subversion.apache.org/docs/release-notes/1.7.html

> 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.

Dito, and 1.7 is not the first version which makes working copies
unusable with older clients. It is (to my knowledge) the first SVN
version that makes the working copy upgrade an explicit command, though.
Older versions just quietly upgraded working copies without ever asking
you.

> 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),

True, and it should still be possible to do a checkout from an SVN 1.7
server using a 1.6 client.

> but now I don't have the error messages handy.  Figured a 1.7
> client would be the easiest solution.

Maybe, but it shouldn't be necessary.

J.
-- 
When I am at nightclubs I enjoy looking at other people and assessing
their imagined problems.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: Re: Subversion in sid / QA page

[Farmbuyer]

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.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMK0Gmrp=O=iz2rnu0wkkqe-nm8c162swh7oqhhbt-m5wp-...@mail.gmail.com

Re: Subversion in sid / QA page

[Bob Proulx]

Farmbuyer wrote:
> I've recently found myself with a need to upgrade my SVN client to 1.7,
> so I started poking around some.

As I recall 1.7 takes some major changes in direction of some of the
previous functionality.  For example the .svn directory is now only at
the top level and not in every directory.  Meaning that subdirectories
are not standalone anymore.  That will probably break some people and
break some applications that work with subversion in a large ripple
down cascade.  That might scare a distro maintainer into holding off
and waiting for dust to settle.  I could see something like that going
into experimental for a long while first.  However I haven't played
with that yet so don't know.

> And a meta-question:  where might I look for discussions about future SVN
> package plans?  Searching debian-user archives didn't find anything.  I'm
> hoping the maintainer is just on holiday for a bit.

You might file a wishlist bug requesting packaging the newer 1.7
against the subversion package.  If there isn't one already.

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.  Sometimes something in the build will change and there
will be no visible changes in the result at all and yet someone will
request a newer version anyway.

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.

Bob


signature.asc
Description: Digital signature

Re: Subversion in sid / QA page

[Sven Hoexter]

On Sat, Nov 26, 2011 at 01:52:30PM -0500, Farmbuyer wrote:

Hi,

> - Every release since 2006 has "dfsg" on it.  It's been too long since I used
>   Debian and I don't remember what is indicated by "dfsg" in a package name,
>   but I vaguely recall it being unusual.

DFSG == Debian Free Software Guidelines
Usually this tag in the name is a hint, that the upstream released tarball had
to be modified. Usually some files had to be remove whic are not distributable
under the DFSG.


> None of that especially worries me, but it does make me wonder:  has anyone
> tried building 1.7.* on a sid system?  Is there anything in the build rules 
> from
> 1.6.* that caused you trouble?  I'd love to avoid solving the same issues from
> scratch if I can.

Try it yourself and read the upstream release notes/changelogs. That's
the way to go in most cases.
 

> And a meta-question:  where might I look for discussions about future SVN
> package plans?  Searching debian-user archives didn't find anything.  I'm
> hoping the maintainer is just on holiday for a bit.

There are few people noted as uploaders in the current package but the
main maintainer is still Peter Samuelson as you can see here
http://packages.qa.debian.org/s/subversion.html

debian-user is still a user mailinglist so that's not the point to search
for packaging related issue.

Anyway if you use subversion, or just click yourself through the
webvc of the subversion packaging repo, you'll find a part of the repo
which looks like someone is working on 1.7.x packaging:
http://anonscm.debian.org/viewvc/pkg-subversion/src/1.7.x/

So I'd say checkout that repo and start to build the package to see
what the current state is.

HTH
Sven
-- 
And I don't know much, but I do know this:
With a golden heart comes a rebel fist.
 [ Streetlight Manifesto - Here's To Life ]


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2026192111.GB2183@marvin