[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

FW: rpm package without neon

From: Jeremy Mordkoff <jlm_at_ZeeVee.Com>
Date: Thu, 1 Oct 2009 10:02:30 -0400

-----Original Message-----
From: Hyrum K. Wright [mailto:hyrum_wright_at_mail.utexas.edu]
Sent: Thursday, October 01, 2009 9:49 AM
To: Jeremy Mordkoff
Cc: dev_at_subversion.tigris.org
Subject: Re: rpm package without neon

This question is about the usage of Subversion, and should be sent to users_at_subversion.tigris.org
.

-Hyrum

On Oct 1, 2009, at 9:41 AM, Jeremy Mordkoff wrote:

> Hi -
>
> I support about 20 linux systems. About ½ are still running fedora
> code 7, the other half are fedora core 10. Some users need to be
> able to manage one view from either OS.
>
> We recently upgraded the repository to subversion 1.6 and we are
> rolling out the new client. Since there is no subversion 1.6 binary
> distribution for fedora core 7, I decided to build it myself. I have
> built and tested subversion 1.6.4 on one system. Now I want to roll
> it out to the other 10 fedora core 7 machines. I tried to build an
> RPM file using 'cd packages/rpm/redhat-8+; make' but that died
> looking for neon-devel. The packaging system seems to want neon-
> devel but the build seemed happy without it.
>
> Any suggestions? Do I need to download and build neon from source?
>
> Is there a subversion 1.6.4 build for fedora core 7?
>
> JLM
>
>
>
>
> Jeremy Mordkoff
> Director, QA, IT & Release
> ZeeVee, Inc.
> One Monarch Drive | Littleton, MA 01460
> Office: 978.467.1395 x233 | Fax: 978.467.1404
> Mobile: 978-257-2183
> jlm_at_zeevee.com
> www.zeevee.com
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2402540

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-01 16:03:20 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.