Your message dated Sat, 29 Aug 2026 18:40:55 +0500
with message-id <[email protected]>
and subject line Re: Bug#1134929: RFS: tinyserve/0.3.1-1 [ITP] -- tiny
multi-worker HTTP server built on libuv
has caused the Debian Bug report #1134907,
regarding ITP: tinyserve -- minimal multi-worker HTTP server built on libuv
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.)
--
1134907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1134907
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Derrity <[email protected]>
X-Debbugs-Cc: [email protected]
* Package name : tinyserve
Version : 0.3.1
Upstream Author : Derrity <[email protected]>
* URL : https://github.com/Derrity/TinyServe
* License : MIT (Expat)
Programming Lang: C
Description : minimal multi-worker HTTP server built on libuv
TinyServe is a small static-file and reverse-proxy HTTP/1.1 server
written in C on top of libuv. Notable features:
* Multi-worker model via fork() + SO_REUSEPORT (Linux) or a
single-process fast path elsewhere.
* Static file serving with byte-range requests, ETag and
Last-Modified validation, 304 Not Modified.
* Asynchronous directory listings (uv_queue_work).
* Basic-auth, reverse proxy, and a JSON-driven route table.
* Hardened HTTP parser (rejects CL+TE smuggling, non-tchar
header names, NUL/CRLF in the request-target) plus
log-injection sanitisation.
* Per-connection idle and request timeouts; SOMAXCONN backlog;
bounded concurrent connections (503 on excess).
* Hardened Release build: PIE, RELRO, BIND_NOW,
_FORTIFY_SOURCE=2, -fstack-protector-strong, stack-clash
protection (Linux).
* Cryptographically strong multipart-range boundaries
(getrandom() / arc4random_buf / /dev/urandom).
* Unit-test suite under CTest; man page tinyserve(1).
Why does Debian want it?
Existing static-file servers in the archive (lighttpd, nginx,
apache2, busybox-httpd, webfs) are either heavyweight, lack
hardening defaults, or are not multi-worker. TinyServe fills
the niche of a sub-100KB, hardening-by-default, libuv-based
single-binary HTTP server suitable for kiosks, embedded
appliances, CI artefact servers, and quick file dumps.
I plan to maintain this package myself and look for a sponsor to
upload it.https://proton.me/mail/home
--- End Message ---
--- Begin Message ---
On Sat, May 30, 2026 at 11:49:12PM +0500, Andrey Rakhmatullin wrote:
This is the third toy web server packaged by the upstream that
currently has an open RFS. This one has a better justification though,
because the coding agent prompt included writing one. It also has a
better packaging (it looks like a better model was used, though it
still doesn't know that dh_auto_test handles nocheck directly).
Closing, together with the ITP.
--
WBR, wRAR
signature.asc
Description: PGP signature
--- End Message ---
