[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#990235: marked as done (RFS: python-pylatexenc/2.10-1 [ITP] -- Simple LaTeX parser providing conversion to/from unicode)

Your message dated Tue, 31 Aug 2021 19:30:28 +0200
with message-id <20210831193028.3f36afb7@vip.jcf.pm>
and subject line Re: Bug#990235: RFS: python-pylatexenc/2.10-1 [ITP] -- Simple LaTeX parser providing conversion to/from unicode
has caused the Debian Bug report #990235,
regarding RFS: python-pylatexenc/2.10-1 [ITP] -- Simple LaTeX parser providing conversion to/from unicode
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
990235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990235
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "python-pylatexenc":

 * Package name    : python-pylatexenc
   Version         : 2.10-1
   Upstream Author : Philippe Faist <philippe.faist@bluewin.ch>
 * URL             : https://github.com/phfaist/pylatexenc
 * License         : Expat, Expat and W3C, W3C
 * Vcs             :
https://salsa.debian.org/python-team/packages/python-pylatexenc
   Section         : python

For context, the issues that I most struggled with were:
1. declaring the d/copyright correctly: hopefully this is addressed
thanks to the help of the helpful folks of the debian-legal list [1],
which involved switching to using GitHub releases as upstream and
incorporating their suggestions.
2. including manpages for the 3 executables (as setup.py
console_scripts)in the package: initially I attempted to generate them
dynamically at build time, but I switched to using a custom target as
recommended in [2]. As a side effect of 1, I was able to include a
documentation package (rendered from sphinx sources) - I'm unsure if
rendering the full documentation as a manpage would be preferred over
having individual help2man-generated entries.

Any help and further review is more than welcome - the package is
maintained at salsa [3].

It builds those binary packages:

  python3-pylatexenc - Simple LaTeX parser providing conversion to/from
unicode
  python-pylatexenc-doc - Simple LaTeX parser providing conversion
to/from unicode (Documentation)

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/python-pylatexenc/

Alternatively, one can download the package with dget using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/p/python-pylatexenc/python-pylatexenc_2.10-1.dsc

Changes for the initial release:

 python-pylatexenc (2.10-1) UNRELEASED; urgency=medium
 .
   [ Diego M. Rodriguez ]
   * Initial release (Closes: #950664)
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
     contact address
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
     layout

Regards,

[1] https://lists.debian.org/debian-legal/2021/06/msg00006.html
[2] https://wiki.debian.org/ManualPage/help2man
[3] https://salsa.debian.org/python-team/packages/python-pylatexenc
-- 
Diego M. Rodriguez

--- End Message ---
--- Begin Message --- 
On Mon, 30 Aug 2021 20:23:25 +0200
"Diego M. Rodriguez" <diego@moreda.io> wrote:

> Control: tags 990235 - moreinfo
> [...] 
> Ditto - hopefully the latest version in salsa is ready for a new review.

Thanks you, uploaded with a minor change to the formatting of d/copyright.

Attachment: pgpVqj4GKXJj7.pgp
Description: OpenPGP digital signature


--- End Message ---
Reply to: