Re: Bug#1038812: ITP: sexp -- S-expressions parser and generator C++ library and command-line tool

2023-06-22 Thread Alexander Sulfrian
Hi,

On Wed, Jun 21, 2023 at 12:20:52PM -0400, Daniel Kahn Gillmor wrote:
> * URL : https://github.com/rnp/sexp

this URL is 404, maybe you meant https://github.com/rnpgp/sexp ?


Thanks,
Alex



Bug#1054182: ITP: python-scramp -- Python implementation of the SCRAM protocol

2023-10-18 Thread Alexander Sulfrian
Package: wnpp
Severity: wishlist
Owner: Alexander Sulfrian 
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org

* Package name: python-scramp
  Version : 1.4.4
  Upstream Author : Tony Locke 
* URL : https://github.com/tlocke/scramp
* License : MIT-0
  Programming Lang: Python
  Description : Python implementation of the SCRAM protocol

A Python implementation of the SCRAM authentication protocol.

python-scramp is a dependency for recent versions of python-pg8000.

I plan to package it inside the Debian Python Team, but I will need a
sponsor.



Re: reference Debian package of multiple binaries sharing one man page

2023-11-11 Thread Alexander Sulfrian
Hello,

On Fri, Nov 10, 2023 at 08:20:35PM +0100, Norwid Behrnd wrote:
> However, there still is some detail I did not understand well enough; the
> additional line
> 
> .so man1/mdl.1
> 
> in my file /debian/markdownlint.1

I think you missunderstodd the instructions:

> Here is how to do it: If you want to have your man page available under the
> names `foo' and `bar' in section 1, then put the man page in foo.1 and have
> bar.1 look like this:
> 
> .so man1/foo.1

You will need a file mdl.1 with the following content:

.so man1/markdownlint.1

and markdownlint.1 should be the normal manpage without a .so line.


Alex



Re: Is an autogenerated configure shell script non-editable source (Was: Bug#1025739: hmmer2: missing source for configure)

2022-12-09 Thread Alexander Sulfrian
Hi,

On Fri, Dec 09, 2022 at 01:14:40PM +0100, Andreas Tille wrote:
> I would consider asking upstream about this for sure but the code is in
> maintenance mode and there is no Git repository to step back in history.
> The only way to go would be to take configure.ac from a later version
> and find out how it can be tweaked to create some working configure
> file from it.  I do not consider my time well spent in doing so except
> if there is some consensus here on the list that configure files without
> configure.ac are "missing source".

isn't the matching configure.ac available here?

https://github.com/MichiganTech/hmmer/blob/2.3.2/configure.ac

This repository is at least referenced in debian/upstream/metadata and
the package version seems to match the git tag.


Alex