Here's a thing:
$ tar tvf elilong.tar.gz
-rwxr-xr-x root/root 3124 2026-06-01 18:32 elilong/elilong.SlackBuild
-rw-r--r-- root/root 424 2026-06-01 17:32 elilong/README
-rw-r--r-- root/root 287 2026-05-03 09:16 elilong/doinst.sh
-rw-r--r-- root/root 307 2026-06-01 18:32 elilong/elilong.info
-rw-r--r-- root/root 917 2026-05-30 09:48 elilong/slack-desc
There's no entry in the tar file for the containing directory. Normally
the first archive member would be elilong/ (the dir itself). If I
extract your tarball and then recreate it with a regular "tar cvfz",
I get this:
$ tar cvfz elilong.tar.gz elilong/
elilong/
elilong/README
elilong/elilong.SlackBuild
elilong/doinst.sh
elilong/elilong.info
elilong/slack-desc
$ tar tvf elilong.tar.gz
drwxr-xr-x urchlay/users 0 2026-06-01 20:17 elilong/
-rw-r--r-- urchlay/users 424 2026-06-01 17:32 elilong/README
-rwxr-xr-x urchlay/users 3124 2026-06-01 18:32 elilong/elilong.SlackBuild
-rw-r--r-- urchlay/users 287 2026-05-03 09:16 elilong/doinst.sh
-rw-r--r-- urchlay/users 307 2026-06-01 18:32 elilong/elilong.info
-rw-r--r-- urchlay/users 917 2026-05-30 09:48 elilong/slack-desc
I can add a check to sbolint, when it's checking a tarball, which
will complain if the tarball's first member isn't a directory,
mode 755, named the same as PRGNAM/ (in this case, elilong/). This
will let submitters catch and identify (and fix) the problem before
submitting... but it's still not an ideal solution.
Currently I'm looking at the server-side submission processor, to see
why it fails when the enclosing dir isn't present in the tarball. It
really shouldn't care... but obviously it does.
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
