I've uploaded aexpect 1.3.0 to pypi and built packages on COPR.
https://pypi.python.org/pypi/aexpect/1.3.0
https://copr.fedorainfracloud.org/coprs/lmr/Autotest/build/499015/
Let me know if you have any doubts,
Lucas
On 01/12/2017 12:28 PM, Lucas Meneghel Rodrigues wrote:
> That's a great idea. Is the upload of the docs made through ssh?
>
I've done the first upload through the main project a web page[1].
There may be other ways to do the push. Ideally, it'd all flow through
the usual setuptools commands
That's a great idea. Is the upload of the docs made through ssh?
On Thu, Jan 12, 2017 at 3:26 PM, Cleber Rosa wrote:
> Hi folks,
>
> While working on "Check/Work around PIP upload failures"[1], I noticed
> that the "http://pythonhosted.org/avocado-framework; URL is ours, and
>
Hi folks,
While working on "Check/Work around PIP upload failures"[1], I noticed
that the "http://pythonhosted.org/avocado-framework; URL is ours, and
PyPI let us host documentation there.
Instead of a 404, let's also upload the latest released docs[2] together
with the released (code) tarball
Dear maintainers,
After 3897ce39a00b1144d155e9651b58431675909506,
travis will fail in the post merge check if you don't include the
'Signed-off-by' in the Merge commit message. Please include it in your
merge script or add a `-s` in your merge command.
Thank you,
--
apahim