I've been publishing subversion updates to Repoforge.
Build your Subversion package in "mock", not in a local shell environment that contains subversion itself. The presence of alternative versions of core libraries or alternative, manually installed versions of those libraries or your PATH can cause real configuration adventures.On Sun, Oct 20, 2013 at 1:46 PM, Martin Gansser <linux4martin@xxxxxx> wrote:
Hi,
hi I'm working on the packet guayadeque, when creating the rpm package
on Fedora 20 you get the following error message:
bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=853553
There is a problem during the fedora 19+ package building related to svn:
-- Found Subversion: /usr/bin/svn (found version "1.8.3")
CMake Error at /usr/share/cmake/Modules/FindSubversion.cmake:83 (message):
Command "/usr/bin/svn info /builddir/build/BUILD/guayadeque-svn1885" failed
with output:
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at
'/builddir/build/BUILD/guayadeque-svn1885'
is too old (format 29) to work with client version '1.8.3 (r1516576)'
(expects format 31). You need to upgrade the working copy first.
You need to upgrade the working copy with a 'svn upgrade' command in the %prep section if you build the package in fedora >= 20, otherwise building fails.
I don't know if this issue can be fixed only inside the RPM building or can be done even outside.
have somebody a idea to resolve this problem ?
regards
Martin
--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging
-- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/packaging
