jira-importer commented on issue #550: URL: https://github.com/apache/maven-scm/issues/550#issuecomment-2964603569
**[Geert Pante](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=greyfairer)** commented We're having the same issue, also in Continuum. We're using cvs native provider. When we start a release:prepare from continuum, we always pass in a CVS user name and passwd. But when that passwd is changed, and we pass the new passwd, CVS rejects the login. We fixed it by removing the cvs user login from .cvspasswd in continuum's home dir. Changing DNS name by IP number had also the same effect, since this will also result in ignoring the .cvspasswd entry. I think that CVS will ask for a user login if it's not in .cvspasswd, or the one in .cvspasswd is incorrect. Apparently the native cvs provider only handles the first case. Greets, Geert. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
