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

(alldup) Failing Validator due to invalid URL's #2171

Open
Tracked by #2187
pauby opened this issue Mar 10, 2023 · 5 comments
Open
Tracked by #2187

(alldup) Failing Validator due to invalid URL's #2171

pauby opened this issue Mar 10, 2023 · 5 comments

Comments

@pauby
Copy link
Member

pauby commented Mar 10, 2023

Chocolatey Version

1.3.0

Chocolatey License

None

Package Version

4.5.28

Current Behaviour

Package is failing Validator due to invalid licenseUrl. The releaseNotes URL is also invalid.

Expected Behaviour

Package passes Validator.

Steps To Reproduce

See moderation message on the package page.

Environment

Package Validator.

Chocolatey Log

N/A

Anything else?

No response

@pauby pauby added the Bug label Mar 10, 2023
pauby added a commit to pauby/chocolatey-coreteampackages that referenced this issue Mar 10, 2023
…inary name

Ensured links used https, pointed to the English site and removed the licenseUrl link as it is no longer available.
pauby added a commit to pauby/chocolatey-coreteampackages that referenced this issue Mar 10, 2023
pauby added a commit to pauby/chocolatey-coreteampackages that referenced this issue Mar 10, 2023
Ensured links used https, pointed to the English site and removed the licenseUrl link as it is no longer available. Package did not uninstall at all and the install script wasn't clear.
@github-actions
Copy link

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue will be closed in 14 days if it continues to be inactive.

@pauby pauby changed the title (alldup) Failing Validator due ot invalid URL's (alldup) Failing Validator due to invalid URL's May 10, 2023
@github-actions
Copy link

Dear contributor,

As this issue seems to have been inactive for quite some time now, I've automatically closed it.
If you feel this is a valid issue, please feel free to re-open the issue if/when a pull request
has been added.
Thank you for your contribution.

@AdmiringWorm
Copy link
Member

Re-Opening as this issue is known as a issue that needs to be fixed, and is tracked in a parent issue.

@michael-franck
Copy link
Contributor

@pauby I see you have commits on this issue. To me they are looking good so I would like to know if this still up for grabs?

@pauby
Copy link
Member Author

pauby commented Sep 26, 2023

There is a PR up for it and I think there is an unresolved comment on there that I've not had time to get back to.

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

Successfully merging a pull request may close this issue.

4 participants