Bug#745342: Bug#745347: Bug#745342: Status of twine in Debian
On Mon, Sep 1, 2014 at 9:55 PM, Gaudenz Steinlin <gaudenz@debian.org> wrote:
>
> [ As this is in large parts about python-releases I'm CCing the relevant
> ITP bug report. ]
>
> Hi Zygmunt
>
> Sorry, I haven't been able to catch you on IRC. Just ping me, I'm
> gaudenz on oftc.
I've just pinged you. I'm sorry my network was unreliable today and I closed IRC
> Zygmunt Krynicki <zygmunt.krynicki@canonical.com> writes:
>
>> Hi Gaudenz
>>
>> I've packaged twine and python-releases (a build dependency).
>> Python releases was rejected and thus I was unable to upload twine.
>
> You still don't mention why it was rejected. In bug #745347 there was
It was apparently rejected because the orig tarball didn't have the LICENSE file
> some discussion about the package name. Was that the reason? What does
> hold you from renaming it to python-sphinx-releases or even better first
> discussing this on the debian-python list as proposed in the bug.
>
> Looking at what's currently in the archive there does not seem to be a
> universal naming scheme for sphinx extensions. The following are
> possible names for releases with some precedent:
>
> - python-sphinx-releases
I think we can pick that one ^
> - python-sphinxcontrib-releases
> - python-sphinxcontrib.releases
>
>
>>
>> Twine and releases (not request!) are both in DPMT's SVN tree. Please
>> ping me on #debian-python (zyga) as I'd like someone to help me to
>> finish those and perhaps convert them to the new git world.
>
> I found the releases repository, but was unable to find the one for
> twine. Do you have an URL?
Sorry, I'm too used to DPMT, it's actually in PAPT
svn+ssh://svn.debian.org/svn/python-apps/packages/twine/trunk
>> I haven't uploaded them to mentors. as I was working with Piotr
>> Ożarowski and it seems that DPMT is not using mentors.
>
> That's fine, if the packages are in a source control repository there is
> not much point in uploading to mentors.
Let's talk on IRC : -)
Thanks
ZK
Reply to: