Hi Thomas,

On Tue, Jul 23, 2013 at 04:20:05PM +0800, Thomas Goirand wrote:
> It looks like upstream isn't using code.google.com anymore, and has moved
> to pypi. Also, they renamed the upstream name from "mimeparse" to
> "python-mimeparse", and release version 0.1.4. It's a bit weird because
> on pypi, both https://pypi.python.org/pypi/python-mimeparse and
> https://pypi.python.org/pypi/mimeparse exist, though the former seems
> to be the most up-to-date repository.
> 
> I need (in a timely maner) the version 0.1.4. Therefore, I have prepared
> a debdiff for your package. This debdiff also adds support for python3,
> since upstream package also supports that, and that other packages also
> need python3-mimeparse.
> 
> Could you please upload this new version, or alternatively, allow me to
> NMU it, as per attached debdiff?

I will look into both issues in the evening and update the git repository
accordingly. I will update you and the bugreport on everything.

About the pypi situation: I did talk with upstream about the matter, and
this seems to be mostly a mistake, but python-mimeparse will receive future
updates.

> Also, it would be nice if you decided to team-maintain the package. The
> python team is mostly welcoming everyone.

I am 100% pro team maintenance, even if I am not entirely sure of all the
consequences :-)

cheers,

Mathias Ertl (Mati)

-- 
I only read plain text mail! I prefer pgp|gpg signed & encrypted mails!

Attachment: signature.asc
Description: Digital signature

Reply via email to