[From nobody Sat Apr  4 15:45:05 2026
Received: (at submit) by bugs.debian.org; 3 Feb 2025 15:51:06 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
 (2021-04-09) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-115.7 required=4.0 tests=BAYES_00,
 BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
 DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,GENDER,HAS_PACKAGE,
 SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY,USER_IN_DKIM_WELCOMELIST,
 USER_IN_DKIM_WHITELIST autolearn=ham autolearn_force=no
 version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 21; hammy, 149; neutral, 48; spammy,
 1. spammytokens:0.935-+--receive
 hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
 0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
 0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: <smcv@debian.org>
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:49354)
 from C=NA, ST=NA, L=Ankh Morpork, O=Debian SMTP, OU=Debian SMTP CA,
 CN=stravinsky.debian.org, EMAIL=hostmaster@stravinsky.debian.org (verified)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.94.2) (envelope-from <smcv@debian.org>) id 1teyj3-00CHDS-UV
 for submit@bugs.debian.org; Mon, 03 Feb 2025 15:51:05 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; 
 s=smtpauto.stravinsky;
 h=X-Debian-User:Content-Type:MIME-Version:Message-ID:
 Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:
 Content-Description:In-Reply-To:References;
 bh=XpZlJUoF9gJoatsvb0kbyYJQtFD4YiCTWvkZGQev0dU=; b=TBgRaOA6XW6tBAeHjmtFy/nQS6
 wDmVl7BDAMO4abscrmncsSjOSD2R1z99zf4V6af9lYGKZXwJRk3Fb57T/cRco+HEBwRdbTOp7dqbo
 Y3RvP1EBaRVPTcQHIirY2igS7BhiUV3w7wYxeo4bXv+lzFoOGC7Z1wjfFeWqVUcWrDNo4+Vh989zX
 8rHtC2tsruT7kpsVu9iWmfr/DwGsNoyIBo/+/Cp1TLG/mwTj4iPEETY7iIpo3jT31Znz3tsNQAb65
 ChNitOijxCUQoDSIhYpdE8N84Bn8O96/l6C0JeVzLQGhVpFMyAHnmsFPtrKCp8rtiR+yUaMzCYbpA
 s2Fv91yQ==;
Received: from authenticated user by stravinsky.debian.org with esmtpsa
 (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.94.2) (envelope-from <smcv@debian.org>) id 1teyj1-000Kaw-U9
 for submit@bugs.debian.org; Mon, 03 Feb 2025 15:51:04 +0000
Date: Mon, 3 Feb 2025 15:51:02 +0000
From: Simon McVittie <smcv@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: libsdl3-doc: many warnings regarding man page syntax reported by
 lintian
Message-ID: <Z6Dl5hRY2pjVBsZB@remnant.pseudorandom.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Mutt-Fcc: =.lists.debian/
X-Reportbug-Version: 13.0.2
X-Debian-User: smcv
Delivered-To: submit@bugs.debian.org

Package: libsdl3-doc
Version: 3.2.0+ds-1
Severity: normal
Tags: upstream help

lintian reports many warnings for the SDL API reference man pages such as
SDL_Keycode(3type).

These man pages are generated from Doxygen doc-comments at build-time
by using SDL-specific tools (build-scripts/wikiheaders.pl, I think),
so patching individual man pages to resolve these warnings is not a
solution. Instead, the generating toolchain should be improved. This
should happen upstream or not at all: I don't consider a Debian-specific
solution to be helpful here, because it would regress as soon as upstream
change their documentation and tools.

Solving this issue is not a high priority for me personally and I am not
able to allocate time for it, but upstream is usually happy to receive
code contributions via Github pull requests. If someone feels strongly
about this issue, please help upstream to improve the situation.

If improvements land upstream but are only included in their development
releases, I would be willing to consider a Debian-specific backport of
those improvements into an older stable-branch if necessary, as long as
it doesn't impose a regression risk or interfere with the stable release
review process.

Thanks,
    smcv
]