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

Re: Wrong db version for src rpm rebuild

From: Kris Deugau <kdeugau_at_vianet.ca>
Date: 2005-01-07 15:55:35 CET

Kenneth Porter wrote:
> --On Thursday, January 06, 2005 3:08 PM -0500 "Martin J. Stumpf"
> <mjs@jhu.edu> wrote:
> > I just want to upgrade to 1.1.1 or 1.1.2 from rpms or even a build
> > from a tarball. I have many other clients that are FC2 so that is
> > why I was trying to rebuild a binary rpm.

> Same here. As a rule, RPM's for later Red Hat versions can be used if
> you build from the source RPM.

Usually, but not always due to versioned dependencies - which can often
be a massive pain to unravel. I've run into this a number of times on
past RH versions.

> > After 6 hours of messing with this (I
> > had already tried editing the spec file and that didn't work
> > because I need all the dependencies available to build a new rpm).
> > The tigris website downloads section doesn't even mention FC2 under
> > Redhat it just takes you to the summer site which has only
> > whitebox. I don't even know what whitebox is but it was the only
> > place I could find src rpms.

> whitebox probably means "any" distro, the way a whitebox PC is a box
> with no brand name built from generic parts.

In this case, it's actually White Box Linux, one of a number of projects
that have taken the Red Hat .src.rpm packages for RHEL and rebuilt them
without a lot of the Red Hat branding. The first release is based on
RHEL3, which in turn is pretty much the official server-oriented version
of Red Hat Linux 9.

-kgd

-- 
Get your mouse off of there!  You don't know where that email has been!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 7 15:58:50 2005

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.