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

Can't install because of Sake dep instead of sake #370

Open
Altai-man opened this issue Dec 1, 2019 · 3 comments
Open

Can't install because of Sake dep instead of sake #370

Altai-man opened this issue Dec 1, 2019 · 3 comments

Comments

@Altai-man
Copy link
Member

Apparently, in META6.json of Sake sake is used as a name. Then:

➜  whateverable git:(sourceable) ✗ zef install --deps-only .
===> Searching for missing dependencies: App::GPTrixie, Config::INI, Cro, Cro::HTTP::Client, Digest, Digest::HMAC, Digest::SHA256::Native, File::Directory::Tree, File::Temp, HTTP::Server::Async, HTTP::UserAgent, IRC::Client, IRC::TextColor, JSON::Fast, Number::Denominate, Pastebin::Gist, SVG::Plot, Sake, Stats, Terminal::ANSIColor, Text::Diff::Sift4, CoreHackers::Sourcery
===> Updating cpan mirror: https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/cpan1.json
===> Updating p6c mirror: https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/p6c1.json
===> Updated p6c mirror: https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/p6c1.json
===> Updated cpan mirror: https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/cpan1.json
===> Failed to find dependencies: Sake
Failed to resolve some missing dependencies
@Altai-man
Copy link
Member Author

I am using 2019.11 and latest zef.

@AlexDaniel
Copy link
Member

Yeah, I've seen that. I'm not sure if it's a bug elsewhere or if META6.json should be simply tweaked. Should it know that sake and Sake are the same thing?
Ping @ugexe.

@ugexe
Copy link

ugexe commented Dec 1, 2019

I filed a zef bug report -- ugexe/zef#327 -- but this might be a bit tricky to fix. Looking at the grammar I expected escaping the < and > ala :auth<Foo \<a\@b.com\>> would avoid the issue, but apparently the grammar is not properly parsing escaped surrounding brackets.

This can be worked around by adding an auth field that doesn't contain < or > like :auth<First Last <[email protected]>>. Right now the author field is used as an auth since the auth field is missing, since that is just what was always done.

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

No branches or pull requests

3 participants