Please update lp:xine-lib for new VCS location

Asked by Reinhard Tartler

xine has moved from CVS to hg in April 2007. I've put the new url in the whiteboard of the branch.

http://anonscm.debian.org/hg/xine-lib/xine-lib/

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
William Grant (wgrant) said :
#1

I've registered the new import at https://code.launchpad.net/~vcs-imports/xine-lib/trunk, and adjusted lp:xine-lib to point at it.

Revision history for this message
Reinhard Tartler (siretart) said :
#2

It seems that the import fails. Is this a configuration issue or a bug in launchpad/bzr-hg?

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

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

Revision history for this message
Reinhard Tartler (siretart) said :
#4

Any idea why the import fails?

Revision history for this message
Julian Edwards (julian-edwards) said :
#5

None - since it's been a while I've re-tried it so we can see if it is still failing. Please re-open here if it fails again.

Revision history for this message
Reinhard Tartler (siretart) said :
#6

It has just failed again, just a few hours ago.

Revision history for this message
Julian Edwards (julian-edwards) said :
#7

Ok can you see the attached bug, Jelmer is attempting a workaround in code for their flakey server.

Revision history for this message
Reinhard Tartler (siretart) said :
#8

Are you sure the fix applies to this import?

The comment on the source code change specifically talks about svn. However, lp:xine-lib
  a) imports mercurial (hg, as opposed to svn) and
  b) from alioth, not sourceforge and
  c) uses http:// not https://.

Revision history for this message
Jelmer Vernooij (jelmer) said :
#9

I think Julian's comment was probably meant as an answer for another question.

Unfortunately the hg imports aren't very reliable yet at the moment (unlike the SVN and git imports which work in all but a handful of cases), and we're looking at marking them alpha or beta in the web site.

Can you help with this problem?

Provide an answer of your own, or ask Reinhard Tartler for more information if necessary.

To post a message you must log in.