Launchpad itself

Import from @rpm5.org cvs is failing

Asked by Jeff Johnson

Hi --

I've just started receiving (or noticing) import failure msgs like here

     https://code.launchpad.net/~rpm5/rpm/trunk

While the ability to import cvs -> bar isn't critically important,
I would like to know whether there is something that can
be done to resolve the issue.

Is the import from @rpm5.org cvs -> bar fixable?

Is there snaything that I should do (in cvs) to help work around
whatever issue is causing the failure?

Thanks for help!

73 de Jeff

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was reopened

Revision history for this message
Launchpad Janitor (janitor) said : 		#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Jeff Johnson (n3npq) said : 		#2

I still need an answer.

Revision history for this message
Deryck Hodge (deryck) said : 		#3

I'm not sure why it ever failed. It's working fine for me locally, so I started it up again. Let's see if this gets it going again.

Revision history for this message
Jeff Johnson (n3npq) said : 		#4

Note that the CVS repository @rpm5.org goes back more than 15y
and there may be some (insoluble without a time machine ;-) issues.

If there's anything that needs doing in @rpm5.org CVS to make
the import from CVS -> BZR, please feel free to ask.

While I'm not interested in using BZR @rpm5.org per-se, having
a secondary VCS system in place for @rpm5.org CVS is quite useful
(yes we have off-site backups in place too ;-)

(aside)
Hmmm ... I've got 2 e-mail notices of import failure and the only
exit from this input screen is
    This solved my problem
which may not be the case.

Revision history for this message
Jeff Johnson (n3npq) said : 		#5

Ah there's the UI: I still breed an answer. Sorry for the inline n00b noise.

Revision history for this message
Steve McInerney (spm) said : 		#6

Hi Jeff,

this one's all a bit funky.
I've created the linked bug as a starter to help track a fix. There doesn't appear to be anything directly obvious ops-wise broken at least.

Cheers!

Revision history for this message
Laura Czajkowski (czajkowski) said : 		#7

There is a bug opened to track this issue.

Can you help with this problem?

Provide an answer of your own, or ask Jeff Johnson for more information if necessary.

To post a message you must log in.