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.

Sign up for GitHub

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

Jump to bottom

Repology and others metadata should be moved from Bintray #6350

Closed
ghost opened this issue Feb 4, 2021 · 2 comments
Closed

Repology and others metadata should be moved from Bintray #6350

ghost opened this issue Feb 4, 2021 · 2 comments
Labels
information Informational post packaging Issue related to building packages, not affecting end users directly

Comments

@ghost
Copy link

ghost commented Feb 4, 2021

Everything from https://bintray.com/termux/metadata should be moved somewhere, preferably with automatic uploads possible. Once will be done, a pull request with new link will be needed for https://github.com/repology/repology-updater.

Related: #6348
@ghost ghost added packaging Issue related to building packages, not affecting end users directly information Informational post labels Feb 4, 2021
@ghost ghost locked and limited conversation to collaborators Feb 4, 2021
@ghost
Copy link
Author

ghost commented Feb 4, 2021

Locking issue as informational/TODO. All discussion about Bintray deprecation in #6348.

@ghost
Copy link
Author

ghost commented Feb 12, 2021

Repology data is now in separate repo: https://github.com/termux/repology-metadata

whatprovides database is currently stored at https://github.com/termux/whatprovides/releases/tag/2.2.0 and has to be manually rebuilt periodically.

@ghost ghost closed this as completed Feb 12, 2021
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
information Informational post packaging Issue related to building packages, not affecting end users directly
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants