Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#3262 Unable to check out the trunk branch of the nst project

self-service
Chris Tsai
None
nst
2014-12-08
2013-03-22
No

We are encountering a strange subversion area when we try to check out the "trunk" area of our project (we are not hitting this error when checking out our current development area "dev"):

Using the instructions from the project code page (https://sourceforge.net/p/nst/code/4286/tree/):

[devel@dhcp134 tmp]$ svn checkout --username=pblankenbaker svn+ssh://pblankenbaker@svn.code.sf.net/p/nst/code/trunk nst-code
A    nst-code/test
A    nst-code/test/nst-additions
A    nst-code/test/nst-additions/test.bash
A    nst-code/test/jre
A    nst-code/test/jre/test.bash
A    nst-code/test/rpmdirs
A    nst-code/test/rpmdirs/test.bash
A    nst-code/test/aircrack-ng

...

A    nst-code/test/pcap2convxml/test.bash
svn: E160004: Filesystem is corrupt
svn: E200014: Checksum mismatch while reading representation:
   expected:  12cc505d0b7843c7b73032ea4af37fb7
     actual:  ff0f5d17478af89eb2ce64e9cbfc867c

Discussion

  • Chris Tsai
    Chris Tsai
    2013-03-26

    • status: unread --> pending
    • assigned_to: Chris Tsai
     
  • Chris Tsai
    Chris Tsai
    2013-03-26

    Greetings,

    It looks like the corruption was introduced in revision 4281. Perhaps removing and re-adding those files will help?

    Also, while I see your test checkouts are over svn+ssh, is it possible that the commit in question was made over https? We've been observing some issues with commits over https recently.

    Thanks,
    Chris Tsai, SourceForge.net Support

     
  • Chris Tsai
    Chris Tsai
    2013-04-02

    Any update?

    Thanks,
    Chris Tsai, SourceForge.net Support

     
  • Chris Tsai
    Chris Tsai
    2013-04-16

    • status: pending --> self-service
     
  • Sorry about that.

    We could not figure out a way to fix the "trunk" area. So we created a new top level "repo" area based off a older revision and have been using that as our new trunk.

    I guess you can close out this issue if you'd like (we have a work around but were unable to fix).