Hi Lars, [ Moving this to your RFS. ]
On Sat, 2026-11-14 at 12:41 +0100, Lars Uffmann wrote:
> Hi Maytham,
>
> you post some interesting points here for me as someone looking for a
> sponsor, that I thought "okay, I'll check myself against the list".
>
> And I noticed that I don't check some boxes and wonder if you would consider
> those non-compliances "acceptable":
>
> On 2026-11-14 01:49:33, Maytham Alsudany wrote:
> > I should also mention that, for me personally when I am looking through
> > RFS bugs, there are a handful of indicators that signal whether someone
> > is willing to actually maintain the package long-term. I don't know how
> > accurate they are, but it's the only heuristic I can use. It includes
> > stuff like:
> > - Properly formatted ITP and RFS bugs, with correct name
>
> [x]
The title on your bug is incorrect, which causes issues e.g. the scripts
I use to browse RFS bugs will not pick it up. It needs to be:
RFS: package-name/deb-version [one or more ITP/ITA/RC/NMU] --
description
e.g. RFS: miniflux/2.3.5-1 [ITP] -- minimalist and opinionated feed
reader
Things like "first time packaging" is unnecessary; many others are also
first time packagers.
> > - Packaged in a Git repo
>
> [x]
>
> > - Packaged in a team (if applicable) - much lower chance of abandonment
>
> No, being new to debian, I am on my own, for my first ever submission.
For me personally, ITP/new package RFS' are a red flag, especially for
first submissions, because many of them are low quality submissions
rather than real software people use. This does not really apply to your
RFS though.
> > - Upstream != downstream
>
> No, I am the main upstream maintainer (not the project author): I worked a
> long time (since 2024) on the project and saw that it has quite an active
> userbase, while also myself finding it as the *only* suitable C++ library for
> the purpose of manipulating OOXML spreadsheet (XLSX) files.
> Accordingly I thought it would be a valuable contribution to any linux distro
> - and with proper dependency management, the install process would be much
> easier for the users.
Usually libraries are packaged because of some other piece of software
being packaged needs it. At least that's the way I go about it. It would
have a stronger case for inclusion if some other package needed it.
[...]
>
> > - Genuinely useful
>
> [x] (Manipulating XLSX files from C++ - do I need to elaborate? :)
New packages should be able to stand up to scrutiny on why they should
be included. What makes libopenxlsx worth including in Debian when
alternatives already in the archive do the same thing, such as QXlsx or
Libxlsxwriter.
Keep in mind that software in Debian stable cannot be updated, barring
security fixes and important bugfixes. So, is the library, in its
current state, mature enough and suitable to sit for 2-3 years in a
release without ever getting a new feature or update? Will you consider
it "outdated" and tell users to avoid using the packaged library (which
some upstreams do)?
--
I've skimmed the actual packaging and found some things. I didn't do a
comprehensive review though:
See the manual page for debhelper-compat-upgrade-checklist. debhelper-
compat = 14 means no need for ${shlibs:Depends} and the like.
Add a comment to d/copyright explaining why those files are listed in
Files-Excluded.
Is there a reason your package includes a static library as well? Yes,
policy allows it, but it only makes sense if there's a good reason, as
it means that your package will need to be rebuilt every time a build-
dependency is updated. AFAICT if you keep this, you may need to declare
Static-Built-Using, see deb-control manpage.
--
Maytham
signature.asc
Description: This is a digitally signed message part

