You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Barry Scott <ba...@barrys-emacs.org> on 2003/11/11 21:05:30 UTC

svn on Redhat 9 fails on co

While working on the pysvn extension. I setup svn on a Redhat 9 system
from the 0.32.1 rpms and have a reproducible error. The same command
on windows works fine. Do you need an issue logged?

Barry

$ svn co http://svn.collab.net/repos/svn/trunk subversion
...
svn: Input/output error
svn: svn_io_file_checksum: error reading from 
'subversion/www/.svn/tmp/text-base/subversion_logo_hor-468x64.png.svn-base'

$ svn --version
svn, version 0.32.1 (r7505)
    compiled Oct 23 2003, 15:15:07

Copyright (C) 2000-2003 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/

The following repository access (RA) modules are available:

* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
   - handles 'http' schema
   - handles 'https' schema
* ra_local : Module for accessing a repository on local disk.
   - handles 'file' schema
* ra_svn : Module for accessing a repository using the svn network protocol.
   - handles 'svn' schema



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Blessed Binary Release Numbers: WAS: svn on Redhat 9 fails on co

Posted by Files <fi...@poetryunlimited.com>.
Karl, Julian, Mike and anyone else

(Directed to Karl, since he gave me this answer originally).

A few weeks ago, in answer to a question, you informed me that the BLESSED
release number (rXXXX) for a particular release build of subversion (not a
'dev build') matches the rXXXX listed in the CHANGES file. That way, all
binaries for a release display the correct rXXXX in response to the --version
flag.

I am hoping that the release tarball has this information encoded already.

When building from the /tags directory, setting the rXXXX is a manual process.
Which means that package maintainers are likely to use the tag revision unless
otherwise instructed. I myself, until recently, had been doing so, until you
informed me otherwise (at which point I made the Mandrake build set extract
said information from the CHANGES file).

I feel that having the CHANGES file out of step makes tracking the problems of
a particular released version of subversion difficult. I feel that it is a
"bad thing" <tm>.

Should we encourage package maintainers to ensure their BLESSED binary builds
coincide w/ the rXXXX listed in the CHANGES file so that all subversion issues
can be correctly identified as being from a particular subversion revision? I
do not feel this is major enough to warrant stricter controls, but a uniform
policy on release numbers would go a long way to making our 1.0 and post-1.0
more professional and more acceptable to management.

Instead of generating a perpetual chicken and egg scenario w/ different
release numbers for the same binary?
-- 
Shamim Islam
BA BS

David Summers said:
>
> On Tue, 11 Nov 2003, Files wrote:
>> Barry Scott said:
>> > $ svn --version
>> > svn, version 0.32.1 (r7505)
>>
>> Is this the right number? I was under the impression that 0.32.1 was r7497.
>>
>> Was this a personal build? Sorry if this seems inapplicable, but I'm
>> wondering
>> if that might have something to do with your psvn error and such.
>>
>
> I'm just guessing but probably he is using my Subversion RPMs.  The r7505
> is the revision of the tag of the 0.32.1 release.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn on Redhat 9 fails on co

Posted by Frans Thamura <ja...@intercitra.com>.
Which one is the best?

using the David's RedHat RPM or from source?

Frans


> 
> On Tue, 11 Nov 2003, Files wrote:
> > Barry Scott said:
> > > $ svn --version
> > > svn, version 0.32.1 (r7505)
> > 
> > Is this the right number? I was under the impression that 0.32.1 was r7497.
> > 
> > Was this a personal build? Sorry if this seems inapplicable, but I'm wondering
> > if that might have something to do with your psvn error and such.
> > 
> 
> I'm just guessing but probably he is using my Subversion RPMs.  The r7505 
> is the revision of the tag of the 0.32.1 release.
> 
> -- 
> David Wayne Summers          "Linux: Because reboots are for hardware upgrades!"
> david@summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
> PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
> 

Regards,

Frans Thamura <fr...@intercitra.com>
Intercitra Innovation Center
+62 855 7888 699

We help you manage and control.

----------
Tertarik dengan Java Open Source Integration discussion?? bergabung ke JUG Indonesia mailing list, untuk subscribe email aja ke jug-indonesia-subscribe@yahoogroups.com

Website: http://jug-indonesia.dev.java.net



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn on Redhat 9 fails on co

Posted by David Summers <da...@summersoft.fay.ar.us>.
On Tue, 11 Nov 2003, Files wrote:
> Barry Scott said:
> > $ svn --version
> > svn, version 0.32.1 (r7505)
> 
> Is this the right number? I was under the impression that 0.32.1 was r7497.
> 
> Was this a personal build? Sorry if this seems inapplicable, but I'm wondering
> if that might have something to do with your psvn error and such.
> 

I'm just guessing but probably he is using my Subversion RPMs.  The r7505 
is the revision of the tag of the 0.32.1 release.

-- 
David Wayne Summers          "Linux: Because reboots are for hardware upgrades!"
david@summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn on Redhat 9 fails on co

Posted by Files <fi...@poetryunlimited.com>.
Barry Scott said:
> $ svn --version
> svn, version 0.32.1 (r7505)

Is this the right number? I was under the impression that 0.32.1 was r7497.

Was this a personal build? Sorry if this seems inapplicable, but I'm wondering
if that might have something to do with your psvn error and such.
-- 
Shamim Islam
BA BS

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn on Redhat 9 fails on co

Posted by Steve Williams <st...@kromestudios.com>.
I just used svn 0.32.1 (r7505) on RedHat 9 to checkout the latest from
svn.collab.net and it all worked fine.  No errors.  Stock RedHat 9 system
with all updates and Subversion 0.32.1.  The system is not used for anything
else but as a Subversion testbed.

Sly

> While working on the pysvn extension. I setup svn on a Redhat 9 system
> from the 0.32.1 rpms and have a reproducible error. The same command
> on windows works fine. Do you need an issue logged?
>
> Barry
>
> $ svn co http://svn.collab.net/repos/svn/trunk subversion
> ...
> svn: Input/output error
> svn: svn_io_file_checksum: error reading from
>
'subversion/www/.svn/tmp/text-base/subversion_logo_hor-468x64.png.svn-base'
>
> $ svn --version
> svn, version 0.32.1 (r7505)
>     compiled Oct 23 2003, 15:15:07


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org