Re: [HELP] Unable to commit files with Maven release plugin
I don't really understand how the svn client does security but I had to manually log in to svn a couple times with my new password before it stuck and I could do a commit without logging in to svn. Have you tried a plain commit, not through the release plugin? thanks david jencks On Feb 19, 2010, at 7:56 PM, Delos wrote: Thanks David and Kevan! I have updated my password at https://svn.apache.org/change- password. But the error still occurs. Any suggestion? 2010/2/20 Kevan Miller kevan.mil...@gmail.com On Feb 19, 2010, at 2:35 PM, David Jencks wrote: You should have received an email from Tony Stephenson yesterday on the apache committers list explaining how you need to update your apache password so you can continue to use apache's nexus and svn. In case you aren't subscribed (all commiitters should be): On Feb 18, 2010, at 2:02 PM, Tony Stevenson wrote: Folks, On March 19th we will be changing the source of authentication for all SVN accounts. For most Committers, we suggest you update your paswords at: https://svn.apache.org/change-password This will then sync your passwords, and you will be able to continue after the cut-over without loss of service. If you already know your LDAP password, which is also used for logins to people.apache.org, you do not have to do this. After the cutover date, your old Subversion HTTP Authentication password will stop working. The technical details: At the moment all committers have a distinct SVN account. This is essentially an entry in a htpasswd file. As you should all know by now we have been working on migrating to LDAP, we have now completed phase 1 of this; we have imported shell/Posix users and groups. What we want to do next is remove this local SVN account, and use LDAP as the authentication provider. This is a simple change, but has some repercussions that may effect a large number of you. After we switch over, the password for SVN will be your current LDAP one. We expect that many of you dont remember your LDAP password, and so what we want you to do is go and reset your LDAP password now, to avoid being unable to commit to SVN. Also, shortly after the LDAP groups were imported Nexus (repository.apache.org) switched to using LDAP for it's authentication source. If you use this and discover you have been unable to login since the cut-over you should use the steps above to resolve your login issues. -- Best Regards, Delos
Re: [HELP] Unable to commit files with Maven release plugin
I just tried again, the problem disappeared. Seems there is delay to synchronize SVN credential.Plain commit and release plugin both work fine now. Thanks David! 2010/2/20 David Jencks david_jen...@yahoo.com I don't really understand how the svn client does security but I had to manually log in to svn a couple times with my new password before it stuck and I could do a commit without logging in to svn. Have you tried a plain commit, not through the release plugin? thanks david jencks On Feb 19, 2010, at 7:56 PM, Delos wrote: Thanks David and Kevan! I have updated my password at https://svn.apache.org/change-password. But the error still occurs. Any suggestion? 2010/2/20 Kevan Miller kevan.mil...@gmail.com On Feb 19, 2010, at 2:35 PM, David Jencks wrote: You should have received an email from Tony Stephenson yesterday on the apache committers list explaining how you need to update your apache password so you can continue to use apache's nexus and svn. In case you aren't subscribed (all commiitters should be): On Feb 18, 2010, at 2:02 PM, Tony Stevenson wrote: Folks, On March 19th we will be changing the source of authentication for all SVN accounts. For most Committers, we suggest you update your paswords at: https://svn.apache.org/change-password This will then sync your passwords, and you will be able to continue after the cut-over without loss of service. If you already know your LDAP password, which is also used for logins to people.apache.org, you do not have to do this. After the cutover date, your old Subversion HTTP Authentication password will stop working. The technical details: At the moment all committers have a distinct SVN account. This is essentially an entry in a htpasswd file. As you should all know by now we have been working on migrating to LDAP, we have now completed phase 1 of this; we have imported shell/Posix users and groups. What we want to do next is remove this local SVN account, and use LDAP as the authentication provider. This is a simple change, but has some repercussions that may effect a large number of you. After we switch over, the password for SVN will be your current LDAP one. We expect that many of you dont remember your LDAP password, and so what we want you to do is go and reset your LDAP password now, to avoid being unable to commit to SVN. Also, shortly after the LDAP groups were imported Nexus ( repository.apache.org) switched to using LDAP for it's authentication source. If you use this and discover you have been unable to login since the cut-over you should use the steps above to resolve your login issues. -- Best Regards, Delos -- Best Regards, Delos
[HELP] Unable to commit files with Maven release plugin
Hi, I'm trying to prepare the release for tomcat-parent-6.0.24 ( https://svn.apache.org/repos/asf/geronimo/external/trunk/tomcat-parent-6.0.24). But after I launched mvn release:prepare, I always get the error below in the end. Could anyone give any hints about this? Thanks in advance! [INFO] Unable to commit files Provider message: The svn command failed. Command output: svn: Commit failed (details follow): svn: MKACTIVITY of '/repos/asf/!svn/act/6feb0aa2-505c-4c06-92ec-f700066fd3ab': authorization failed: Could not authenticate to server: rejected Basic challenge ( https://svn.apache.org) -- Best Regards, Delos
Re: [HELP] Unable to commit files with Maven release plugin
You should have received an email from Tony Stephenson yesterday on the apache committers list explaining how you need to update your apache password so you can continue to use apache's nexus and svn. thanks david jencks On Feb 19, 2010, at 10:12 AM, Delos wrote: Hi, I'm trying to prepare the release for tomcat-parent-6.0.24 (https://svn.apache.org/repos/asf/geronimo/external/trunk/tomcat-parent-6.0.24 ). But after I launched mvn release:prepare, I always get the error below in the end. Could anyone give any hints about this? Thanks in advance! [INFO] Unable to commit files Provider message: The svn command failed. Command output: svn: Commit failed (details follow): svn: MKACTIVITY of '/repos/asf/!svn/act/6feb0aa2-505c-4c06-92ec- f700066fd3ab': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.apache.org) -- Best Regards, Delos
Re: [HELP] Unable to commit files with Maven release plugin
On Feb 19, 2010, at 2:35 PM, David Jencks wrote: You should have received an email from Tony Stephenson yesterday on the apache committers list explaining how you need to update your apache password so you can continue to use apache's nexus and svn. In case you aren't subscribed (all commiitters should be): On Feb 18, 2010, at 2:02 PM, Tony Stevenson wrote: Folks, On March 19th we will be changing the source of authentication for all SVN accounts. For most Committers, we suggest you update your paswords at: https://svn.apache.org/change-password This will then sync your passwords, and you will be able to continue after the cut-over without loss of service. If you already know your LDAP password, which is also used for logins to people.apache.org, you do not have to do this. After the cutover date, your old Subversion HTTP Authentication password will stop working. The technical details: At the moment all committers have a distinct SVN account. This is essentially an entry in a htpasswd file. As you should all know by now we have been working on migrating to LDAP, we have now completed phase 1 of this; we have imported shell/Posix users and groups. What we want to do next is remove this local SVN account, and use LDAP as the authentication provider. This is a simple change, but has some repercussions that may effect a large number of you. After we switch over, the password for SVN will be your current LDAP one. We expect that many of you dont remember your LDAP password, and so what we want you to do is go and reset your LDAP password now, to avoid being unable to commit to SVN. Also, shortly after the LDAP groups were imported Nexus (repository.apache.org) switched to using LDAP for it's authentication source. If you use this and discover you have been unable to login since the cut-over you should use the steps above to resolve your login issues.
Re: [HELP] Unable to commit files with Maven release plugin
Thanks David and Kevan! I have updated my password at https://svn.apache.org/change-password. But the error still occurs. Any suggestion? 2010/2/20 Kevan Miller kevan.mil...@gmail.com On Feb 19, 2010, at 2:35 PM, David Jencks wrote: You should have received an email from Tony Stephenson yesterday on the apache committers list explaining how you need to update your apache password so you can continue to use apache's nexus and svn. In case you aren't subscribed (all commiitters should be): On Feb 18, 2010, at 2:02 PM, Tony Stevenson wrote: Folks, On March 19th we will be changing the source of authentication for all SVN accounts. For most Committers, we suggest you update your paswords at: https://svn.apache.org/change-password This will then sync your passwords, and you will be able to continue after the cut-over without loss of service. If you already know your LDAP password, which is also used for logins to people.apache.org, you do not have to do this. After the cutover date, your old Subversion HTTP Authentication password will stop working. The technical details: At the moment all committers have a distinct SVN account. This is essentially an entry in a htpasswd file. As you should all know by now we have been working on migrating to LDAP, we have now completed phase 1 of this; we have imported shell/Posix users and groups. What we want to do next is remove this local SVN account, and use LDAP as the authentication provider. This is a simple change, but has some repercussions that may effect a large number of you. After we switch over, the password for SVN will be your current LDAP one. We expect that many of you dont remember your LDAP password, and so what we want you to do is go and reset your LDAP password now, to avoid being unable to commit to SVN. Also, shortly after the LDAP groups were imported Nexus ( repository.apache.org) switched to using LDAP for it's authentication source. If you use this and discover you have been unable to login since the cut-over you should use the steps above to resolve your login issues. -- Best Regards, Delos
Unable to commit
Folks, am unable to commit this morning. Does anyone know why? My password, I have not forgotten it, is not being accepted. Thanks Anita Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
Re: Unable to commit
Sorry for the fuss... I used a different user name :(. I need to wake up. Going to get some tea... Anita --- Anita Kulshreshtha [EMAIL PROTECTED] wrote: Folks, am unable to commit this morning. Does anyone know why? My password, I have not forgotten it, is not being accepted. Thanks Anita Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
