Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"No single root directory found, all dists must extract to a single directory" when running "mi6 release" command #166

Closed
sdondley opened this issue Jan 21, 2023 · 8 comments · Fixed by #168

Comments

@sdondley
Copy link

Could someone kindly take a look at the question at:

https://stackoverflow.com/questions/75190418/no-single-root-directory-found-all-dists-must-extract-to-a-single-directory-e

I can't figure out what is wrong. I'm on macOS running raku 2022.12

@skaji
Copy link
Owner

skaji commented Jan 21, 2023

The error message comes from fez.

Please execute the following commands, and paste the output here.

❯ which pax

❯ pax -c -z -f Directory-0.0.1.tar.gz

@sdondley
Copy link
Author

which pax reports /bin/pax

I rolled raku version back to 2022.07 and everything worked again so I don't have the tar.gz file in my directory anymore. How do I generate the tarball? mi6 build didn't do it nor did zef build.

@sdondley
Copy link
Author

OK, had to generate the tarball manully. pax command shows this:

> $ pax -c -z -f Directory.tar.gz                                                                                                                                                                                                             [±main ●●]
.github/workflows/._test.yml
pax: Unrecognized header keyword: LIBARCHIVE.xattr.com.apple.provenance
pax: Unrecognized header keyword: SCHILY.xattr.com.apple.provenance
.github/workflows/test.yml
._.gitignore
pax: Unrecognized header keyword: LIBARCHIVE.xattr.com.apple.provenance
pax: Unrecognized header keyword: SCHILY.xattr.com.apple.provenance
.gitignore
._Changes
pax: Unrecognized header keyword: LIBARCHIVE.xattr.com.apple.provenance
pax: Unrecognized header keyword: SCHILY.xattr.com.apple.provenance
Changes
._LICENSE
pax: Unrecognized header keyword: LIBARCHIVE.xattr.com.apple.provenance
pax: Unrecognized header keyword: SCHILY.xattr.com.apple.provenance
LICENSE
._META6.json
pax: Unrecognized header keyword: LIBARCHIVE.xattr.com.apple.provenance
pax: Unrecognized header keyword: SCHILY.xattr.com.apple.provenance
META6.json
._README.md
pax: Unrecognized header keyword: LIBARCHIVE.xattr.com.apple.provenance
pax: Unrecognized header keyword: SCHILY.xattr.com.apple.provenance
README.md
._dist.ini
pax: Unrecognized header keyword: LIBARCHIVE.xattr.com.apple.provenance
pax: Unrecognized header keyword: SCHILY.xattr.com.apple.provenance
dist.ini
lib/._Directory.rakumod
pax: Unrecognized header keyword: LIBARCHIVE.xattr.com.apple.provenance
pax: Unrecognized header keyword: SCHILY.xattr.com.apple.provenance
lib/Directory.rakumod
t/._01-basic.rakutest
pax: Unrecognized header keyword: LIBARCHIVE.xattr.com.apple.provenance
pax: Unrecognized header keyword: SCHILY.xattr.com.apple.provenance
t/01-basic.rakutest
xt/Author-Tests.rakutest

@sdondley
Copy link
Author

OK, same command on a different mac:

> $ pax -c -z -f Directory.tar.gz                                                                                                            [±main ●]
.github/workflows/test.yml
.gitignore
Changes
LICENSE
META6.json
README.md
dist.ini
lib/Directory.rakumod
t/01-basic.rakutest
xt/Author-Tests.rakutest

@sdondley
Copy link
Author

@2colours
Copy link

Again, disclaimer: of course these mimicked distros actually have no root folder but the problem arises from the ._ files that appear even when the root folder does exist.

Seems to me that tony-o/raku-fez#72 @masukomi did chase this down fair and square...

@skaji
Copy link
Owner

skaji commented Jan 22, 2023

@sdondley I think this issue is fixed in App-Mi6 3.0.2.

@sdondley
Copy link
Author

Ok, thanks. Yeah, just saw there was a new release. I'll check it out when I get chance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants