Mailing-List: contact users-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@continuum.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Sender: Brett Porter <brett@porterclan.net>
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: Bug during release prepare
From: Brett Porter <brett@apache.org>
In-Reply-To: <1288065794.2398.6.camel@droopy-ubuntu>
Date: Tue, 26 Oct 2010 17:18:52 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4898BDB-66F0-4701-ABD5-6D7F90ED19A1@apache.org>
References: <1288065794.2398.6.camel@droopy-ubuntu>
To: users@continuum.apache.org

Good catch. If it's not there already, can you file this in JIRA?

Thanks,
Brett

On 26/10/2010, at 3:03 PM, Olivier Dehon wrote:

> Hi,
>=20
> On continuum 1.3.1, when preparing a release, if the user mistypes =
their
> subversion password and adds a backslash at the end, then the release
> prepare phase gets stuck in the =93update-working-copy=94 (the first) =
step.
> This is because the svn command issued by continuum is:
>=20
> svn --username xxxxx --password abcdef\ --non-interactive ...
>=20
> which means that the space between the password and the space before =
the
> --non-interactive option is escaped, which in turn means that this
> option is not seen at all, and since the password is incorrect, it =
goes
> ahead and tries to prompt the user for their correct password in the
> command line, so the process hangs (found that by running a:
> ps -edf | grep svn
> on the server).
>=20
> -Olivier
>=20

--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/