groff import fails (worked around by repeating import for filler revisions)
Bug #326971 reported by
Colin Watson
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad CSCVS |
Triaged
|
Low
|
Unassigned |
Bug Description
https:/
2009-02-08 04:59:32 INFO sending checkout request: root = '/sources/groff', file = 'groff/
2009-02-08 04:59:32 CRITICAL checkout did not give file data and did not indicate file was removed.
However, that revision of that file seems to check out OK by hand, so I'm not sure what's happening. Do you have any clues? Michael Hudson professed bafflement on IRC.
summary: |
- groff import fails + groff import fails (worked around by repeating import for filler + revisions) |
tags: | added: cvs |
To post a comment you must log in.
I've wiresharked the conversation involved in running "cvs -d :pserver:<email address hidden> :/sources/ groff -q co -N -P -r 1.1 groff/src/ libs/libxutil/ xmalloc. c", which is, I think, the request that causes confusion in the import and it looks normal to the limited extent of my knowledge of the CVS protocol. The log suggests that the server is not sending a full response at all, but it may be that cscvs is mangling the request somehow. Or maybe it's the 1024'th request we send and the server gives up at that point or something?
As you can probably tell, I don't really have any idea how to fix this. Sprinkling debugging prints all over the code and rerunning the import might lead to more clues, though I have the depressing intuition that all it would do is reveal the exact way in which the remote server/repo is broken.
Not very encouraging, sorry.