I took a look at the build log. It seems the RPM build fails, so
everything (swig, gsvn) fails. Now, this is not good :-), but it's
different from a failure to build Subversion directly from the master
sources on RedHat 8.x... Maybe you could dress the Subject line
to reflect this? Something like:
svn rev 3666 (rpm): FAIL (RedHat 8.x Snapshot)
or whatever. Basically, we need to be able to distinguish at a glance
the difference between native Subversion failing to build on a
supposedly supported platform (high-priority badness), and some
modified/packaged/ported/whatever Subversion failing to build (which
is not-quite-so-high-priority badness, as far as general development
is concerned, and is also possibly the responsibility of some package
maintainer who is already looking into it).
Thanks,
-K
behle@pipedreaminteractive.com writes:
> Build status for pullrpm.py
> ---------------------------
> Operations: update tarball rpms release
> Requested: subversion rapidsvn gsvn
> Attempted (dependencies included): httpd neon swig subversion rapidsvn pygtk gsvn
> Failed: subversion
> Skipped (dependency failed): rapidsvn gsvn
> Completed: httpd neon swig pygtk
> Build Log: ftp://ftp.pipedreaminteractive.com/pub/subversion/2002110604-0/rpmbuild.log
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: svn-breakage-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: svn-breakage-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 6 23:50:49 2002