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

The case of a distribution name: CGI-Simple or Cgi-Simple ? #356

Closed
szabgab opened this issue Oct 29, 2014 · 6 comments
Closed

The case of a distribution name: CGI-Simple or Cgi-Simple ? #356

szabgab opened this issue Oct 29, 2014 · 6 comments

Comments

@szabgab
Copy link
Contributor

szabgab commented Oct 29, 2014

There is a distribution which is AFAIK called CGI-Simple.
https://metacpan.org/release/CGI-Simple works

But when I try to fetch the bug count http://api.metacpan.org/v0/distribution/CGI-Simple only returns the name of the distribution.
If I fetch http://api.metacpan.org/v0/distribution/Cgi-Simple (lower case gi) then I get the number.

OTOH https://metacpan.org/release/Cgi-Simple is "Not Found".

Why is the difference? How can I know which case to use where?

@rwstauner
Copy link
Contributor

I think this is because the file we get from RT spells is "Cgi-Simple":

screenshot - 10292014 - 08 29 00 am

@tsibley
Copy link
Contributor

tsibley commented Oct 29, 2014

Which is because it was Cgi-Simple at one point and RT's queues are case-insensitive. If you file a ticket with rt-cpan-admin@bestpractical.com you can get the case changed.

@szabgab
Copy link
Contributor Author

szabgab commented Nov 1, 2014

@tsibley thanks, I followed your suggestion and https://rt.cpan.org/Dist/Display.html?Name=CGI-Simple is now CGI in upper case.

How long till MetaCPAN will fetch the bug count?

@ranguard
Copy link
Member

ranguard commented Nov 1, 2014

@ranguard ranguard closed this as completed Nov 1, 2014
@szabgab
Copy link
Contributor Author

szabgab commented Nov 1, 2014

Then I don't understand why is it still the old data. I think the Cgi => CGI change on RT was made 3 days ago.

@oalders
Copy link
Member

oalders commented Nov 3, 2014

I think this will clear up once #354 has been fixed and deployed.

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

No branches or pull requests

5 participants