[Slackbuilds-users] issue submitting new slackbuild

[B. Watson]

On Mon, 1 Jun 2026, Tim Dickson via SlackBuilds-users wrote:

> it is. that is why it is odd. i haven't had issues before. this tar.gz was created slightly differently from the usual ones I submit, to ensure correct permissions.
> in my project build script I have
> 
> tar --mode='644' --exclude="$PKGNAME/$PKGNAME.SlackBuild" -cf $PKGNAME.tar $PKGNAME
> tar --mode='755' -rf $PKGNAME.tar "$PKGNAME/$PKGNAME.SlackBuild"
> gzip -f $PKGNAME.tar

OK, I am able to reproduce this: I created a tarball using exactly
these commands (except for a different SlackBuild; I chose alsacap
since it's small).

$ tar tvf alsacap.tar.gz 
drw-r--r-- urchlay/users     0 2026-06-02 23:46 alsacap/
-rw-r--r-- urchlay/users   114 2026-06-02 23:39 alsacap/README
-rw-r--r-- urchlay/users   102 2025-01-23 16:48 alsacap/doinst.sh
-rw-r--r-- urchlay/users    72 2025-01-23 16:48 alsacap/douninst.sh
-rw-r--r-- urchlay/users   292 2026-06-02 23:46 alsacap/alsacap.info
-rw-r--r-- urchlay/users   788 2024-11-29 18:14 alsacap/slack-desc
-rwxr-xr-x urchlay/users  2259 2026-06-02 23:46 alsacap/alsacap.SlackBuild

The directory does exist in the tarball as the first member, but it
has invalid permissions for a directory (0644, aka drw-r--r-). This
explains why the submission form can't find the README, .info,
.SlackBuild files: it extracts the tarball, then tries to cd into
the dir, which files because you need +x permission to cd into a
directory.

When I submit this file, I get exactly the same errors you got:

    Submission failed:
    Could not find alsacap/alsacap.info
    Could not find alsacap/README
    Could not find alsacap/alsacap.SlackBuild

(your errors of course said "elilong", not "alsacap"...)

So now I know what to add to sbolint, to catch this specific problem.

Also I may add a more specific error message to the submission form,
it could actually say "Permission on alsacap/ directory is invalid
(should be 755, not <whatever>)".