Bug#721192: ITP: apostrophe -- a simple markdown editor
Control: unblock -1 by 960767
Control: forwarded -1 https://gitlab.gnome.org/somas/apostrophe/-/issues/189
Hi Birger,
Birger Schacht <birger@rantanplan.org> writes:
> Hi,
>
> I'd be also interested in getting apostrophe into Debian. I tried the
> flatpak version, but there seems to be a problem with missing fonts
> which makes the text harder to read.
>
Interesting you found this issue! I just imported the latest release
and found bundled woff2-format fonts (non dfsg-free). I've contacted
upstream about this. FYI, for fonts to be dfsg-free their source needs
to be included. If Apostrophe cannot be made to work with
fonts-firacode and/or texlive-fonts-extra, then our options are a) wait
for the maintainer[s] of that/those package[s] to provide woff2 format
fonts b) use missing-source to get those fonts' source and compile the
required woff2 fonts during Apostrophe's build, then bundle the
Apostrophe-specific font binaries with this package.
> I took a glance a the code and although pressagio is mentioned in
> `apostrophe/auto_correct.py` that file does not seem to be used in the
> app (yet?). Are you sure its a blocker?
>
It had set it as a blocker while I continued the copyright review,
because I had hoped that upstream would have reenabled this
functionality by now. It looks like they haven't yet, so I've unblocked
this bug. FYI, that discussion was moved here:
https://gitlab.gnome.org/somas/apostrophe/-/issues/200#note_742981
> I created a preliminary package (because, confused as I am, I didn't
> realize there is already an ITP ;)) and using that I did not encounter
> any problems (though its not in any way ready for release- I did not
> even look at the licenses for example...)
>
Sorry for your wasted time. For future reference, always check for an
ITP first, take a glance at the build system to verify it's something
you know how to package, and then do the copyright review before finally
proceeding with any work. Why? It doesn't make sense to spend all the
time packaging something for Debian just to learn that ftpmasters (or
your sponsor) will reject it. It's only happened to me once or twice,
but there have been times where upstream's unwillingness to make changes
made a package impossible to include in Debian (eg: "non" due to
waf...with waf-embedded py2 IIRC).
> Nicholas, if you push your repository to salsa I'd be happy to help with
> the remaining 20%!
>
Unfortunately the source repo is not yet DFSG-free and thus cannot be
redistributed on Debian infrastructure. Yeah, for two font files, but
this is one rule I will not bend.
Thank you for the offer! As soon as I'm able to I'll push to the PAPT :-)
Cheers,
Nicholas
Reply to: