Hi,
>This was done roughly for the same reason as with GnuPG, that has the "gpg"
>executable. Also I'm not quite a fan of using crypto without reading the
>manual >thoroughly :]
indeed :)
>Anyway, is there some best place (other than documentations) to notify the
>users? Possibly create a sym
Thanks a lot for the review, I've fixed the license issues, libs and build
deps. New uploaded version should appear on mentors in no time.
The code with `make dist' and `mk-orig-source' is a fossil from first
packaging attempt (trying to get both GBP and development in one repo). Now
the package r
control: owner -1 !
control: tags -1 moreinfo
Hi, lets review:
control:
autotools-dev, dh-autoreconf,
I think autoreconf alone should be enough.
libgmp10, libcrypto++9v5, libfftw3-double3
on noes! shlibs:Depends should do that automatically. If not, it means your
binaries are not
linking corr
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "codecrypt"
* Package name: codecrypt
Version : 1.7.3-1
Upstream Author : Mirek Kratochvil
* URL : https://github.com/exaexa/codecrypt
* License : LGPL
4 matches
Mail list logo
