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

Use fuse-sshfs from a proper repo for minishift-centos-iso #109

Open
LalatenduMohanty opened this issue Mar 13, 2017 · 9 comments
Open

Use fuse-sshfs from a proper repo for minishift-centos-iso #109

LalatenduMohanty opened this issue Mar 13, 2017 · 9 comments

Comments

@LalatenduMohanty
Copy link
Member

LalatenduMohanty commented Mar 13, 2017

We should not use http://mirror.centos.org/centos/7/atomic/x86_64/adb/ as it is not not maintained, the workaround will be to use a COPR repo or the new Minishift repo in CentOS PaaS SIG (when it is ready).
[1] https://github.com/minishift/minishift-centos-iso/pull/108/files
[2] https://copr.fedoraproject.org/

@praveenkumar
Copy link
Collaborator

@LalatenduMohanty Do we already took any step for CentOS PaaS SIG side (at least a request to have minishift tag)? I am in favor of PaaS sig instead COPR because COPR is not something which contain official packages.

@LalatenduMohanty
Copy link
Member Author

@praveenkumar The first step we are doing in PaaS SIG is to package Minishift RPM then the ISO will follow. I will request for a tag asap.

@hferentschik
Copy link
Member

@praveenkumar @LalatenduMohanty - Is this anything we can do right away? Otherwise I suggest we move this into 1.1.0 and release 1.0.0.

@praveenkumar
Copy link
Collaborator

@hferentschik I would suggest to move it for 1.1.0 release because right now we don't have much time to do needful.

@hferentschik hferentschik modified the milestones: v1.1.0, v1.0.0 Apr 25, 2017
@hferentschik
Copy link
Member

I would suggest to move it for 1.1.0 release because right now we don't have much time to do needful.

+1 That was my thinking as well.

Let's do that, and then cut 1.0.0 of this repo. I think there are no actual changes since the last rc release, so it is more of a formality.

@praveenkumar
Copy link
Collaborator

Let's do that, and then cut 1.0.0 of this repo.

+1

@LalatenduMohanty LalatenduMohanty modified the milestones: v1.2.0, v1.1.0 Jul 20, 2017
@hferentschik
Copy link
Member

@praveenkumar @LalatenduMohanty what is the state here. Is there another repo we could get it from? Or should we keep deferring it?

@gbraad
Copy link
Member

gbraad commented Aug 30, 2017

fuse-sshfs is in EPEL.

@LalatenduMohanty
Copy link
Member Author

Yes, we can try using the EPEL repository.

@LalatenduMohanty LalatenduMohanty modified the milestones: v1.3.0, v1.2.0 Aug 30, 2017
@LalatenduMohanty LalatenduMohanty modified the milestones: v1.3.0, v1.4.0, v1.5.0 Oct 9, 2017
@LalatenduMohanty LalatenduMohanty modified the milestones: v1.5.0, v1.6.0 Dec 13, 2017
@coolbrg coolbrg modified the milestones: v1.6.0, v1.7.0 Feb 12, 2018
@LalatenduMohanty LalatenduMohanty modified the milestones: v1.7.0, v1.8.0 Feb 15, 2018
@LalatenduMohanty LalatenduMohanty modified the milestones: v1.7.0, v1.8.0 Feb 16, 2018
@anjannath anjannath modified the milestones: v1.8.0, v1.9.0 Mar 26, 2018
@LalatenduMohanty LalatenduMohanty modified the milestones: v1.9.0, v1.10.0 Mar 28, 2018
@LalatenduMohanty LalatenduMohanty modified the milestones: v1.10.0, v1.11.0 May 31, 2018
@coolbrg coolbrg modified the milestones: v1.11.0, v1.12.0 Jul 6, 2018
@LalatenduMohanty LalatenduMohanty modified the milestones: v1.12.0, v1.13.0 Jul 10, 2018
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

6 participants