Hello mentors,
I am getting a few lintian "source-is-missing" errors for some HTML
files. These HTML files are infact present in the source code but they
have too many lines which triggers a
"very-long-line-length-in-source-file" lintian tag and that in turn
causes the "source-is-missing" error.
Most of the info I could find in the policy manual and in the forums pertained to binary files that were included in the source, the strategy these resources suggested were
1. Repack upstream tar with the source code of these files
2. Add the source code to the d/missing-sources directory
I don't think either of these are viable options in my case. I was
wondering whether it would be okay to suppress these errors. Is there
any other way to solve this?
--
Shriram Ravindranathan
Thanks, Soren.
It looks like most of these files have just one or two lines that are extremely long.
These are mostly README files. Most of them seem to have this github-markdown.css <https://gist.github.com/jojoldu/9cb1b6a5110619e221dfd4603f30ddd4>
minified and pasted in them. While others have the sources that were
used to generate them listed in the same folder.
Should I copy these sources into the d/missing-sources directory?
Upon inspecting the embedded font, It seems to be a bespoke icon-font generated using a tool called "Fontello" from one of the icons of the octicons iconset from Atom <https://github.com/primer/octicons> (MIT Licensed SVGs)
The font has only 1 glyph, Would it suffice to add this source image to d/missing-souces and add that copyright info to d/copyright?
On 21/02/24 9:56 am, Soren Stoutner wrote:
Shriram,
1. For anything that has the unminified source in the upstream
tarball, I would just create a lintian override with a comment listing
the full path to the source for each file. You can see an example of
how this can be done here:
souhttps://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/blob/master/debian/
rce/lintian-overrides?ref_type=heads
Typically you only copy the source to the debian/missing-sources
directory when it is not included in the upstream tarball and you have
had to acquire it from another place.
2. The github link below includes an embedded font in woff format. Typically, fonts like this would be considered compiled, so a separate font source would be needed. However, I’m not sure what the Debian guidance for dealing with an HTML embedded font like this. If someone else on mentors doesn’t know, I would recommend you ask on debian-legal.
As these are mostly README files, and if it becomes difficult for you
to acquire the source for some of them, you might consider excluding
those you can’t get the source for, at least temporarily, using Files-Excluded in debian/copyright (and then running uscan, which will produce a modified tarball that does not include the problematic
files). For example, see:
copyrhttps://salsa.debian.org/cryptocoin-team/electrum/-/blob/master/debian/
ight?ref_type=heads
Whether this is a good option depends on how helpful those README
files are for the users of your package. If you go this route, you
should add +dfsg to the version of your package to indicate that the upstream tarball has been repackaged to remove files that are not free
(or for which the source is not available).
Soren
--
Shriram Ravindranathan
ters
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 15:05:05 |
Calls: | 6,706 |
Files: | 12,239 |
Messages: | 5,351,159 |