[Slackbuilds-users] issue submitting new slackbuild

[Ιωάννης]

The tarball has a broken directory permission  the execute bit is missing:

  drw-r--r-- root/root  0 ...  elilong/

Without the execute bit, no one can chdir into it, which is exactly what
sbolint tries to do  hence the "Permission denied".

The reason it works on your side is likely that you're running sbolint as
root, and root bypasses execute permission checks on directories. Running
it as a regular user reproduces the error immediately.

For SBo submissions, directories should be 755

sbolint elilong.tar.gz
sbolint: chdir(/tmp/sbolint.810376379/elilong): Permission denied
tar -tvzf elilong.tar.gz | head -3
drw-r--r-- root/root         0 2026-06-01 13:50 elilong/
-rw-r--r-- root/root       287 2026-05-03 16:16 elilong/doinst.sh
-rw-r--r-- root/root       404 2026-05-31 23:17 elilong/README

Also worth noting: the tarball was created in two steps (tar + gzip
separately) instead of the usual:

  tar -czf elilong.tar.gz elilong/

This suggests your packaging workflow may not be applying the correct
permissions before packing. It's worth double-checking how the tarball is
being created.

file elilong.tar.gz
elilong.tar.gz: gzip compressed data, was "elilong.tar", last modified: Mon
Jun  1 10:52:19 2026, from Unix, original size modulo 2^32 10240




Στις Δευ 1 Ιουν 2026 στις 4:29 μ.μ., ο/η Tim Dickson via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> έγραψε:

> that slackbuild is the project slackbuild, rather than sbo slackbuild.
> The significant differences are the tag and the file permissions
> the relevant output of the slackbuild for sbo are as follows.
>
> ~/elilong# ls -l
> total 20
> -rw-r--r-- 1 root root  404 May 31 21:17 README
> -rw-r--r-- 1 root root  287 May  3 14:16 doinst.sh
> -rwxr-xr-x 1 root root 2980 Jun  1 11:50 elilong.SlackBuild*
> -rw-r--r-- 1 root root  307 Jun  1 11:50 elilong.info
> -rw-r--r-- 1 root root  917 May 30 14:48 slack-desc
> sbolint
> elilong: NOTE: elilong.SlackBuild:55: LIBDIRSUFFIX gets set, but never
> used.
> sbolint: elilong checks out OK
>
> sbopkglint /tmp/elilong-0.1.9-x86_64-1_SBo.tgz
> Using tests from /usr/share/sbo-maintainer-tools/sbopkglint.d
> Exploding /tmp/changes/tmp/elilong-0.1.9-x86_64-1_SBo.tgz to
> /tmp/SBo/sbopkglint.3vZRYL ...OK
> Running pre-doinst test...OK
> Installing /tmp/changes/tmp/elilong-0.1.9-x86_64-1_SBo.tgz to
> /tmp/SBo/sbopkglint.3vZRYL ...OK
> Running test: 05-basic-sanity...OK
> Running test: 10-docs...OK
> Running test: 15-noarch...
> ___ note: package might be a good candidate for noarch
> OK
> Running test: 20-arch...OK
> Running test: 25-lafiles...OK
> Running test: 30-manpages...OK
> Running test: 35-desktop...OK
> Running test: 40-newconfig...OK
> Running test: 45-doinst...OK
> Running test: 50-icons...OK
> Running test: 60-usr_info...OK
> Running test: 65-python...OK
> Running test: 70-tmp_path...OK
> Running test: 75-static_libs...OK
> Running test: 85-perl...OK
> === elilong-0.1.9-x86_64-1_SBo.tgz: All tests passed
>
> as you can see, the permissions are ok, and both sbolint and sbopkglint
> pass.
>
> Regardless of all that, the submission form should not report
>
> Submission failed:
> Could not find elilong/elilong.info
> Could not find elilong/README
> Could not find elilong/elilong.SlackBuild
>
> as the tar.gz file is ok.
> I've uploaded the sbo slackbuild I am trying to submit (to
> slackbuilds.org) to the sbo subdirectory on the sourceforge site if you
> want to see the actual elilong.tar.gz sbo slackbuild archive
> https://sourceforge.net/projects/elilong/files/sbo/
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20260601/bf22e9d0/attachment-0001.htm>