Launchpad itself

vcs-import request form does not check CVS repository accessiblity

Bug #363084 reported by Samuel Bronson
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

If I enter an invalid CVSROOT on https://code.edge.launchpad.net/+code-imports/+new, I won't know until someone tries to process the import request. Verifying that the CVS server indicated does indeed allow access to the repository and module entered would allow users to correct these errors much sooner and save time for the vcs-import admins. (It would probably also help if there was a password field, to enter the appropriate password for "anonymous" on the server in question?)

Tags: lp-code
William Grant (wgrant)
affects: launchpad → launchpad-code
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

We could maybe do this via some kind of jobby ajaxy thing when we have the infrastructure.

There's no way we'll have the appservers making connections to arbitrary hosts on the internet.

Changed in launchpad-code:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Samuel Bronson (naesten) wrote :

I don't care how it works, so long as, upon determining that the user-supplied information does not point to a CVS module that it can actually access, it allows the user to try again with new information.

Thanks for looking at this.

Robert Collins (lifeless)
Changed in launchpad:
importance: Wishlist → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.