On Tue, Dec 6, 2011 at 2:46 AM, Ionut Biru wrote:

On 12/06/2011 09:27 AM, Eric Bélanger wrote:

...

Hi,

I just pushed an upstream update (1.7.2) for subversion in the [testing] repo.

There should be no compatibility problems when updating from 1.6.X. The only minor issue is that existing working copies created with Subversion 1.6 and earlier need to be upgraded before they can be used with a Subversion 1.7 client.  Running 'svn upgrade' in the checkout copies fixes this.

does "svn upgrade" require the server to run 1.7 ?

no.

...

The major packaging changes  is that  the ruby bindings are now disabled. Because of issues with the binding tests, upstream is disabling the build of ruby bindings with Ruby 1.9 or later. As we have ruby 1.9 in the repo, I took the easy way out and simply disabled them.  We could readd them later when it'll have support for ruby 1.9. I'm not sure how many people were using these bindings.

I also did other minor change to the package: - Update license, Add file depends, Add missing hook scripts, Add python2 and ruby optdepends for the hook scripts, Clean up PKGBUILD, Remove old patches

As we use subversion for the repos, please test it and sign it off on the signoff page (or report any problems).

Eric

-- Ionuț

On Tue, Dec 6, 2011 at 9:01 AM, Dan McGee wrote:

On Tue, Dec 6, 2011 at 1:27 AM, Eric Bélanger wrote:

...

I also did other minor change to the package: - Update license, Add file depends, Add missing hook scripts, Add python2 and ruby optdepends for the hook scripts, Clean up PKGBUILD, Remove old patches

What about svnmerge.py? This has been dead upstream for some time; we needed it for our repo scripts at one time but that ship sailed long ago [1]. Can we stop shipping it?

Sure unless there are some objections. Should I release a new -2 package with that change or just remove it from trunk so it'll get remove next time the package is updated? Eric

-Dan

[1] http://projects.archlinux.org/devtools.git/commit/?id=f09baea3922d6c9365d267...