It seems that over the years I have taken over maintenance for too many packages and I cannot really give all of them the care that they deserve. Thus, I request an adopter for the microsocks package. The package description is: MicroSocks - multithreaded, small, efficient SOCKS5 server, is a SOCKS5 service that you can run on your remote boxes to tunnel connections through them, if for some reason SSH doesn't cut it for you. . - It's very lightweight, and very light on resources too. - It's also designed to be robust: it handles resource exhaustion gracefully by simply denying new connections, instead of calling abort() as most other programs do these days. - Another plus is ease-of-use: no config file necessary, everything can be done from the command line and doesn't even need any parameters for quick setup.
Hi Peter, I am interested in possibly adopting the Debian microsocks package following your RFA #1143447, but I have not filed an ITA yet. I have reviewed the current Debian packaging and the small upstream codebase, checked the BTS, tracker, Salsa repository/CI, upstream status, reverse dependencies, popcon, and the security tracker, and rebuilt the unchanged 1.0.5-3 package in an updated unstable sbuild environment. The source and binary builds, the nocheck profile, lintian, autopkgtest, uscan, and the test-tunnel functional tests all passed; Debian's reproducibility status and the current Salsa pipeline are also green. I also found a few upstream-facing robustness points around SOCKS-over-TCP framing, handshake timeouts, and cleanup when pthread_create() fails that I would like to discuss rather than change without coordination. Could you tell me what you would expect from the handover and whether there is any pending work or preferred maintenance workflow I should know about? If I decide to proceed, would you be willing to accompany me through the handover and, explicitly, to review and sponsor my first upload? Best regards, Federico
Hi Peter, I am interested in possibly adopting the Debian microsocks package following your RFA #1143447, but I have not filed an ITA yet. I have reviewed the current Debian packaging and the small upstream codebase, checked the BTS, tracker, Salsa repository/CI, upstream status, reverse dependencies, popcon, and the security tracker, and rebuilt the unchanged 1.0.5-3 package in an updated unstable sbuild environment. The source and binary builds, the nocheck profile, lintian, autopkgtest, uscan, and the test-tunnel functional tests all passed; Debian's reproducibility status and the current Salsa pipeline are also green. I also found a few upstream-facing robustness points around SOCKS-over-TCP framing, handshake timeouts, and cleanup when pthread_create() fails that I would like to discuss rather than change without coordination. Could you tell me what you would expect from the handover and whether there is any pending work or preferred maintenance workflow I should know about? If I decide to proceed, would you be willing to accompany me through the handover and, explicitly, to review and sponsor my first upload? Best regards, Federico
Yeah, I do try to leave packages in good shape :) But thanks for making sure! That would better be discussed with upstream, yes. Over the years I have found that different upstream authors have vastly different ideas about how far a packager should be expected to diverge, and I myself have, once or twice, done something that other DDs have called "developing in debian/" (extensive patches that change the way the software behaves), and sometimes this is really not a good idea once you realize you have to *maintain* those patches as the upstream source changes over the years :) But sometimes it is necessary because the authors simply won't accept a change that really, really makes sense at least in the Debian context. Pending work - not right now, I can't think of anything. Pretty much wait for the next upstream release or, if a Debian build tool gets some new shiny functionality, see if it will simplify the packaging even further. Maintenance workflow - I personally have used the "quilt with patches unapplied" way until now. Import a new upstream version with `gbp import-orig`, then `quilt push -a` and `quilt push -f`, edit, `quilt refresh -p ab` until I get the patches right for the new release. For the actual upload to the Debian archive I use `dgit push-source` for a new upstream release (although that might change now that tag2upload seems to be learning about pristine-tar) and `git debpush` for the later Debian-only revisions. But yeah, if you do not have upload rights, you would need sponsoring for at least the first couple of uploads; in that case, nothing unusual again - `dch -r`, commit, push, request sponsorship, and only add a signed tag once the package is actually uploaded (or let the sponsor do that). And of course, none of the steps I listed above are set in stone - a new maintainer may do things in a completely different way, and that's fine :) Sure, no problem! And thank you for your interest in this package! G'luck, Peter
Hi Peter, Thank you for the detailed handover notes and for offering to review and sponsor my first uploads. I followed your advice and discussed the first robustness finding with upstream. The pthread_create() failure cleanup was reported as upstream issue #103, reproduced and tested, and fixed promptly in master. Upstream also accepted the suggested resource-exhaustion backoff; the final commits are 7e83778978c7901ae7ba1a00986a6dd912cc77fd and 69f004aeb7c4ed7da3bf538d60a2d705c5a618df. The issue is now closed. This confirmed that upstream is active and receptive to focused fixes, so I have decided to proceed with the adoption and am marking #1143447 as an ITA. For the first upload I intend to keep the changes narrowly scoped: the maintainer handover and, unless a new upstream release appears first, a backport of those accepted upstream fixes, followed by the full build and test set. I will avoid cosmetic changes and send you the exact result for review and sponsorship once it is ready. Best regards, Federico
Hi Peter, Thank you for the detailed handover notes and for offering to review and sponsor my first uploads. I followed your advice and discussed the first robustness finding with upstream. The pthread_create() failure cleanup was reported as upstream issue #103, reproduced and tested, and fixed promptly in master. Upstream also accepted the suggested resource-exhaustion backoff; the final commits are 7e83778978c7901ae7ba1a00986a6dd912cc77fd and 69f004aeb7c4ed7da3bf538d60a2d705c5a618df. The issue is now closed. This confirmed that upstream is active and receptive to focused fixes, so I have decided to proceed with the adoption and am marking #1143447 as an ITA. For the first upload I intend to keep the changes narrowly scoped: the maintainer handover and, unless a new upstream release appears first, a backport of those accepted upstream fixes, followed by the full build and test set. I will avoid cosmetic changes and send you the exact result for review and sponsorship once it is ready. Best regards, Federico
We believe that the bug you reported is fixed in the latest version of
microsocks, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1143447@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Federico Molara <federico@molara.net> (supplier of updated microsocks package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Tue, 11 Aug 2026 14:07:49 +0200
Source: microsocks
Architecture: source
Version: 1.0.5-4
Distribution: unstable
Urgency: medium
Maintainer: Federico Molara <federico@molara.net>
Changed-By: Federico Molara <federico@molara.net>
Closes: 1143447
Changes:
microsocks (1.0.5-4) unstable; urgency=medium
.
* New maintainer. Thanks to Peter Pentchev for his work on microsocks and
for his help with the handover. (Closes: #1143447)
* Add two upstream patches for pthread_create() failure handling:
- clean up the accepted client resources;
- apply the resource-exhaustion backoff.
Checksums-Sha1:
eee16870bc6837f191718683bc892725577a0762 2306 microsocks_1.0.5-4.dsc
e9d7e42e14cd4328220b90b3ded6348dd9d142ab 5656 microsocks_1.0.5-4.debian.tar.xz
c65c389b972cb3d42637bce7e5ee18318b141f09 47124 microsocks_1.0.5-4.git.tar.xz
415caa8e2281865b3a572cc8483232c1c93b112a 17564 microsocks_1.0.5-4_source.buildinfo
Checksums-Sha256:
f6f22d5a418cce48f84c10ea0024b6a62083a8ab7c8401f49ed532a36d50750c 2306 microsocks_1.0.5-4.dsc
dceb3fffa7c57ee42a429277c44c40c14c9b84c33f0f1cfc267659f8a5028cd3 5656 microsocks_1.0.5-4.debian.tar.xz
41071d9d0df4078eafe55da83f717bd9802977b76446ac0a14ceb2af1ff3b114 47124 microsocks_1.0.5-4.git.tar.xz
7262bff90d4a45e2116195b1e3bc1d5fcb7c8b254db19740f40f74d99975d08f 17564 microsocks_1.0.5-4_source.buildinfo
Files:
011844b0c3161695c039d1f76785debb 2306 utils optional microsocks_1.0.5-4.dsc
f0b158955d7ea989627b556c6b23b1ab 5656 utils optional microsocks_1.0.5-4.debian.tar.xz
b22f3967f21764f1ac0645aedb11d9e2 47124 utils None microsocks_1.0.5-4.git.tar.xz
4d0c2d2cf4dd4de49fc15e9a6321e4cd 17564 utils optional microsocks_1.0.5-4_source.buildinfo
Git-Tag-Info: tag=399442b8fdbc546e1ff80e0b13f6f5570c20c51d fp=2ee7a7a517fc124cf115c354651eefb02527df13
Git-Tag-Tagger: Peter Pentchev <roam@debian.org>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmp+8M8ACgkQYG0ITkaD
wHkB6BAAsGL+RcGV3g0/IFAyOyFucEsw6j0o2/aHdmdivGxBcdgr3dnnCmzV5ixp
jpPpou1fjSNmlOCapxHb8niElWj6nKVFDqanLdENH65x2oGlO0i01x7mjkwHAFrc
slvOt7JPRgTnTuZerAmZabOHOCySZVAHwF1ZAGw11f6z7p0g89+1AuiS6kgDIJ9x
1oKcca0UHihjIB4Czl+gpTBsHCo5ypRK+EX3vSj8yMdt+6DZ0h8Cq0bTBiaDsfya
65jV/Ex4iQ2XNG03TBctOchEKEjtm5Ghe8MfTen/kOuyDguK+2ZcS/Vcy0h/COog
E6gzMB854kJFQ8yPCT3tq9OGvw/+IbFse6q5WkgmO/PcuzVObmQstGOAyCrObG/o
uw9PBM1MgZ6GSzEl5C4ev3TxpYM4moIssPAQYU5y9zzW8jQa88J8iWXocICOhsoi
lRDMadcYjhOaF+UHUD81KXM15VacrtFVRkdbC5qNtOUBXOXR2C5jXa4YAI+q8XH3
RxZKxhjSJHwA/UoLTvxeshO9zuzjX8CUR0O8f/6V+3E763ge6R5WQDRjIAnVwooe
9gFpq9iCIFDKB3Oj/yUroCTRDc7U4YhvKdkbvXReDwsfIdWo2XfXp1i9uxAtakUU
v6NzjFlxenJgUG+S5voxRgmGLFtnkOFw8xu4Ay0HpA4Pt1fLM7o=
=XiAi
-----END PGP SIGNATURE-----