[Slackbuilds-users] Attn Maintainers: Is one of your SBs on this list?

B. Watson urchlay at slackware.uk
Thu Sep 17 02:28:28 UTC 2026



On Thu, 17 Sep 2026, Duncan Roe via SlackBuilds-users wrote:

> | redeclipse: ERR: redeclipse.info: github commit URL needs full 40-digit commit hash in filename
> | (+ 37 repeats)
> Why is this an ERR? The URLs download fine (at least the 2 I randomly tried did)

Because of the Content-disposition HTTP header.

Try "wget --no-content-disposition https://github.com/redeclipse/wicked/archive/5a5f64e/wicked-5a5f64e.tar.gz",
it will save the file as "wicked-5a5f64e.tar.gz".

Now try it with "wget --content-disposition" and the same URL. It saves as
"wicked-5a5f64ef53a54916ca29e2ea6ce8ffc5065a29b7.tar.gz".

Using the full 40-digit commit hash in the URL prevents this: the file
gets saved under the same name regardless.

See also: https://slackbuilds.org/GITHUB_URLs.txt

> | frogatto: NOTE: ./fbsd-fixes.patch has DOS-style CRLF line endings, git may mess it up unless you gzip it
> The source has DOS-style CRLF line endings so the patch has to have them.
> This might get mangled by some mailers, but not by git itself surely?

It's only a "note", not an error or a warning.

In the past (like, several years ago), we really did have problems
with git stripping off the CRs in files like this, so this was a
warning. Now it's just a 'note', and won't cause a sbolint to exit
with error status.

Possibly it's safe to completely remove this check. I downgraded it
to a 'note' in version 0.9.6.2 (about a month ago).

> | nexus: NOTE: nexus.SlackBuild:61: LIBDIRSUFFIX gets set, but never used.
> This is a false positive. LIBDIRSUFFIX is used in a sed command

Huh. You're right. I see the problem: sbolint is looking for the
string "$LIBDIRSUFFIX" and not finding it, because it was written as
"${LIBDIRSUFFIX}". I will make this check smarter.


More information about the SlackBuilds-users mailing list