#1013357 ITP: rust-nom-bibtex -- BibTeX parser using nom

Package:
wnpp
Source:
wnpp
Submitter:
Jonas Smedegaard
Date:
2025-11-29 16:51:08 UTC
Severity:
wishlist
#1013357#5
Date:
2022-06-22 17:10:49 UTC
From:
To:
* Package name    : rust-nom-bibtex
  Version         : 0.3.0
  Upstream Author : Charles Vandevoorde <charles.vandevoorde@hotmail.be>
* URL             : https://github.com/charlesvdv/nom-bibtex
* License         : Expat
  Programming Lang: Rust
  Description     : BibTeX parser using nom

 nom-bibtex is a feature complete *BibTeX* parser using nom.
 It can parse the four differents types of entries
 listed in the BibTeX format description:
  * Preambles which allows to call *LaTeX* command inside your *BibTeX*.
  * Strings which defines abbreviations in a key-value format.
  * Comments.
  * Bibliography entries.

This package is needed by zola (bug#976052).
It will be maintained in the Debian section of Salsa, here:
<https://salsa.debian.org/debian/rust-nom-bibtex>.

 - Jonas
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKzTRYACgkQLHwxRsGg
ASFS3g/+NPoL99pdIz1lkldvL+/s/EUl1CG4DJxjqnIw9aIITVAhG5bIauZg2VO3
PS9q5LBi5oKbBK4SZRFT3O64J88ftO3sX+4uSrzlgleAb3sF+WXjAmtlsQtuHEGH
wlpTkM+TEhs8qgtchh4LgsbJjgdzJUB+fYFmxRG8yAp2BC1fNA26kLXgkketDt1n
dau5KQ5sjIYoGgewnF4ZbcX3Bphum9wLDNEmf1/jkiwAM9qHtq0jBWwPnckMoLdB
5LtW9WugH6K6+FZR995QuZmRmJ7uiF3YMP9M2GRGzJuVI8HqAECDFvwLZGTkk/Fa
1DthGSCt92LZhiZRo+0u1t4OBf0+fniO8ZARbB2Tyz5p8Y8LoM76c8r9cM1L+716
1lPrL+kbDz3AzlE1AXpuJUaa61d0agziFwmky5D9+YRh1S4n27YbnRJ32XWkNA4m
wxrUu3g1FzRKyVmo606TYYOnEIl8IiMouibD4XEarLXumGShP+mzGpruxIDfuNYt
gRCx+w+SJf5WUXEClp/PEs55qq6faFnJrE/ViL/TXH7XadCuzJ2HGmMKlGbnm1Eg
lCfYHNJlwxK9PAnFYT414bTrnq+FXzIi47IH2Wniuo/2XIp7ctzhZ5BSV2e0C53+
acos8wVT+xhGXcM90WlEwYaBXRgwBLG7qfv1eyOIr4iEHEhYIko=
=842g
-----END PGP SIGNATURE-----
#1013357#10
Date:
2022-06-22 17:21:15 UTC
From:
To:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Thanks for your work, Jonas. I was just curious to know if there is a reason
that you are not maintaining it in the rust-team itself (given that there is a team)?
BTW, I am not (actively) a part of the team, myself - I might package $something rust in near future and
hence the question.
#1013357#15
Date:
2022-06-22 17:57:48 UTC
From:
To:
Quoting Nilesh Patra (2022-06-22 19:21:15)
I disagree with that approach and am far more comfortable with
maintaining packages as one git per upstream project - as I do with the
other 500+ packages I maintain (which includes packages I maintain in
the Haskell team which has a similar approach but only by default: They
are open to some packages being maintained differently).

They also don't use Debbugs - but hopefully that's a thing of the past:
Recently at least one team member actively responds to bugs I file (but
there are still RC bugs hanging for *years* with zero response from the
team).

Oh, and their odd packaging style also means you may upset them if you
do a source-full NMU, seemingly because they need the source tarball to
fit exactly their custom setup (i.e. *not* a Github release but what is
distributed at crates.io).

If you decide to maintain Rust packages outside of the Rust team as
well, then I would be happy to form another team if that might be
interesting.  Otherwise you might want to consider reusing my fork of
dh-cargo which I adapted to behave more like general debhelper snippets,
less hardcoding of how the Rust team does packaging.

...Or if my whining here didn't scare you, then join the Rust team! :-)

Thanks for asking,

 - Jonas