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

Adding openSUSE repo from YaST GUI fails #24

Open
bberberov opened this Issue Jan 5, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@bberberov
Contributor

bberberov commented Jan 5, 2018

Just tried to add the v5 repo and I'm getting the following error. This was the URL: http://downloads.rapiddisk.org/pub/releases/5/opensuse42/

An error occurred during repository initialization. [RapidDisk|http://downloads.rapiddisk.org/pub/releases/5/opensuse42/] Valid metadata not found at specified URL History: - File /var/tmp/TmpFile.iRC4XH doesn't contain public key data

@bberberov bberberov changed the title from Adding openSUSE repo for v5 fails to Adding openSUSE repo from YaST GUI fails Jan 5, 2018

@bberberov

This comment has been minimized.

Show comment
Hide comment
@bberberov

bberberov Jan 5, 2018

Contributor

Looks like you cannot disable the GPG check through the GUI. We should build a proper (YaST) openSUSE repo.

Contributor

bberberov commented Jan 5, 2018

Looks like you cannot disable the GPG check through the GUI. We should build a proper (YaST) openSUSE repo.

@pkoutoupis

This comment has been minimized.

Show comment
Hide comment
@pkoutoupis

pkoutoupis Jan 9, 2018

Owner

@bberberov,

I haven't commented on this issue yet but that is partly because I do not know if I want to continue supporting the package repos. The upkeep with every official release, especially as it pertains to the latest and greatest release of each respective distro, is quite consuming. So, I have been weighing the option recently, on whether I should continue doing this or just retire them.

Please note, this does not in any way, invalidate the build scripts included in the source code (i.e. the SPEC files). I will continue to maintain those for individuals to run local package builds.

Thoughts? I am also open to suggestions.

Owner

pkoutoupis commented Jan 9, 2018

@bberberov,

I haven't commented on this issue yet but that is partly because I do not know if I want to continue supporting the package repos. The upkeep with every official release, especially as it pertains to the latest and greatest release of each respective distro, is quite consuming. So, I have been weighing the option recently, on whether I should continue doing this or just retire them.

Please note, this does not in any way, invalidate the build scripts included in the source code (i.e. the SPEC files). I will continue to maintain those for individuals to run local package builds.

Thoughts? I am also open to suggestions.

@bberberov

This comment has been minimized.

Show comment
Hide comment
@bberberov

bberberov Jan 13, 2018

Contributor

I think having official packages helps with exposure/popularity/adoption. Yes, it is a lot of work. I'm just thinking, of the people interested in trying RapidDisk, how many don't try it because there isn't a ready built package available.

It'd be nice if third-party repos adopt the package, since those devs have more experience with their respective distros, but in the meantime, you may want to provide repos of your own. You'll have to choose winners and losers. For example, recently Solus has been picking up speed, but you don't have a Solus package/repo.

I think automating the build and repo maintenance process would be the way to go. I don't have experience with the CI tools, but this would be a reason to learn. GitLab provides free build capacity in their repos if needed.

I think I have figured out the openSUSE spec variant, but I haven't figured out the YaST repo structure fully yet to test it. WIP.

Contributor

bberberov commented Jan 13, 2018

I think having official packages helps with exposure/popularity/adoption. Yes, it is a lot of work. I'm just thinking, of the people interested in trying RapidDisk, how many don't try it because there isn't a ready built package available.

It'd be nice if third-party repos adopt the package, since those devs have more experience with their respective distros, but in the meantime, you may want to provide repos of your own. You'll have to choose winners and losers. For example, recently Solus has been picking up speed, but you don't have a Solus package/repo.

I think automating the build and repo maintenance process would be the way to go. I don't have experience with the CI tools, but this would be a reason to learn. GitLab provides free build capacity in their repos if needed.

I think I have figured out the openSUSE spec variant, but I haven't figured out the YaST repo structure fully yet to test it. WIP.

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