Your message dated Sun, 08 Nov 2026 21:16:19 +0800
with message-id <[email protected]>
and subject line Re: Bug#1153364: RFS: stoken/0.93-3 [ITA] -- Software Token 
for cryptographic authentication
has caused the Debian Bug report #1153364,
regarding RFS: stoken/0.93-3 [ITA] -- Software Token for cryptographic 
authentication
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 [email protected]
immediately.)


-- 
1153364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1153364
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "stoken":

 * Package name     : stoken
   Version          : 0.93-3
   Upstream contact : Kevin Cernekee <[email protected]>
 * URL              : https://github.com/stoken-dev/stoken
 * License          : LGPL-2.1-or-later
 * Vcs              : https://salsa.debian.org/debian/stoken
   Section          : utils

The source builds the following binary packages:

  stoken - Software Token for cryptographic authentication
  libstoken1t64 - Software Token for cryptographic authentication -
shared library
  libstoken-dev - Software Token for cryptographic authentication -
development files

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

  https://mentors.debian.net/package/stoken/

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

  dget -x
https://mentors.debian.net/debian/pool/main/s/stoken/stoken_0.93-3.dsc

Changes since the last upload:

stoken (0.93-3) unstable; urgency=medium

  * New maintainer (Closes: #1130510)
  * Bump debhelper compat level to 14.
  * Bump Standards-Version to 4.7.4, no changes needed.
  * Add debian/upstream/metadata.
  * Add autopkgtests: run the upstream test suite against the installed
    stoken and build the libstoken example program against libstoken-
dev.
  * libstoken-dev: Depend on libxml2-dev, needed by stoken.pc
    (Requires.private: libxml-2.0); without it pkg-config fails.

 -- Juan Pavon <[email protected]>  Sat, 07 Nov 2026 05:53:49 +0000

I am adopting stoken (ITA #1130510). It was orphaned in March 2026
and is currently maintained by the QA team.

I want to learn how to maintain packages in Debian, and stoken is a
good fit: it is small, in good shape, and its library is useful to
other software such as VPN clients. This is my first package in
Debian.

Notes on the changes above:

 * The libxml2-dev dependency fixes a real bug: stoken.pc declares
   "Requires.private: libxml-2.0", so on a clean system
   "pkg-config --libs stoken" fails and nothing can build against
   libstoken. The new build-libstoken autopkgtest found it.
 * The autopkgtests reuse upstream's own test suite (the 10
   tests/*.pipe tests, run against the installed stoken) and build
   the upstream example program against libstoken-dev.

Testing: built in a clean unstable environment with sbuild;
lintian clean (no errors, warnings or info tags); autopkgtest
2/2 pass; piuparts install/purge test passes.

Upstream (https://github.com/stoken-dev/stoken) is quiet: the last
release, 0.93, is from 2023, and it is already packaged.

The packaging is in my fork of the Salsa repository, one commit per
change:
  https://salsa.debian.org/pav0n/stoken
I don't have push access to salsa.debian.org/debian/stoken yet and
would be grateful for help with that.

Thanks for your time.

Regards,
-- 
  Juan Pavon

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message ---
Uploaded. I've also added you to the debian/ repo and pushed your
changes there.
--
Maytham

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to