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

Close

#126737 CVS repository cleanup: netbsd-soc

closed
5
2008-06-13
2008-06-12
Hubert Feyrer
No

In the netbsd-soc project, we have a problem with the CVS repository: one of our students has imported code into netbsd-soc/hurdt/src, and a checkout of that directory now leads to an internal CVS error:

% cvs -z5 -d :ext:hubertf@netbsd-soc.cvs.sf.net:/cvsroot/netbsd-soc co hurdt
...
U hurdt/src/usr.bin/msgc/msg_sys.def
U hurdt/src/usr.bin/msgc/msgc.1
cvs [checkout aborted]: internal error: bad branch tag in checkout
%

I wonder if you can just nuke the netbsd-soc/hurdt/src directory and all its contents from the CVS repository, and we'd start over again?

The sources there are imported from a developer's harddisk, and no version history is currently present that can be lost - the trouble apparently started on the initial import.

For any questions, please send email to hubertf@NetBSD.org.

Thanks!

- Hubert

Discussion

  • Logged In: YES
    user_id=1795569
    Originator: NO

    Greetings,

    This canned response is used by the SourceForge.net team to convey information about how this Support Request will be handled. Please read the entirety of this comment before taking any further action; information enclosed in this comment will help you to ensure that you have an excellent support experience.

    The SourceForge.net team takes all reported issues seriously; we will work to provide you a complete, accurate, and timely response to your inquiry. Information about our support policies and procedures may be found here:
    https://sourceforge.net/docs/C01

    ABOUT THIS ISSUE: Based on the initial review of this request, we have determined that this issue will be considered to have High Priority. Issues within this category typically include high-priority issues related to the SourceForge.net site or services, such as CVS repository clean up, CVS stale locks, CVS import requests, user account issues, and support inquiries. A description of our issue priorities may be found here:
    https://sourceforge.net/docs/C01#issue_priorities

    TRIAGE PROCESS: The initial review of this issue has resulted in a member of the SourceForge.net staff determining who should process this issue, and a change in the Priority, Summary, Assignee, Group and Category settings for this request.

    WHAT TO EXPECT: Issues of this nature will typically be reviewed again by the assigned member of the SourceForge.net team within 3 business days (the SourceForge.net team works at least Monday through Friday, 9am to 5pm Pacific, excepting holidays), though most issues of this nature are handled within 24 hours of submission. Within our next response, we will make a determination regarding your request, or ask for clarification of this issue report. Please wait patiently for our next review of, and response to, this request.

    INQUIRING ABOUT THE STATUS OF THIS ISSUE: Should you have questions or concerns regarding the status of this issue, simply add a comment to this support request. All comments you post to this support request will be received by the SourceForge.net team member who has been assigned this issue. Please do not submit a second support request about this issue (add a comment to this request instead), and do not attempt to contact the assignee of this request via email; all additional information or comments about this request should be posted as a comment to this request.

    Thank you,

    SourceForge.net support

     
    • milestone: 104419 --> Second Level Support
    • assigned_to: nobody --> sog
    • summary: cvs update: internal error: bad branch tag in checkout --> CVS repository cleanup: netbsd-soc
     
  • Jeremy Fincher
    Jeremy Fincher
    2008-06-13

    Logged In: YES
    user_id=1019020
    Originator: NO

    Greetings,

    Per your request, the specified directories (and their contents) have been removed from your project CVS repository. Should you require further assistance from the SourceForge.net team, please submit a new support request.

    NOTE: In rare circumstances, some of the changes that we make to your repository may not synchronize with the pserver repository until you check-in a change to your developer repository. Be sure to make such a change and wait up to an hour before reporting any anomalies regarding actions we performed for you, unless you have verified the problem using developer CVS or the web interface.

    Thank you,

    SourceForge.net support

     
  • Jeremy Fincher
    Jeremy Fincher
    2008-06-13

    • status: open --> closed