Skip to content

Conversation

@iliaross
Copy link
Collaborator

@jcameron
Copy link
Collaborator

Does this change mean we'll need to create a new repo on download.webmin.com ?

@iliaross
Copy link
Collaborator Author

Does this change mean we'll need to create a new repo on download.webmin.com ?

Yeah, check this thread out:

https://forum.virtualmin.com/t/warning-use-the-name-of-the-stable-distribution-instead-of-stable/122043/20?u=ilia

@jcameron
Copy link
Collaborator

I really don't want to maintain another repo to fix a cosmetic issue. Because users can take a long time to upgrade, anytime we add a new repo we still have to maintain the old one for potentially years..

@iliaross
Copy link
Collaborator Author

Jamie, but I already described the process. You don't need to support multiple repos, right? Because you do it only once! The installed Webmin version 2.102 will switch any user to the very new repo. All you will need to support is the new repo. You do it this time for all 3 repos. And later then support only the latest (i.e webmin main ) repo!

I'd really want to see repos done immaculately! Besides it's easy to do!

@jcameron
Copy link
Collaborator

Doesn't that mean that users on versions older than 2.102 won't be able to upgrade beyond that release until they fix the repo, unless we maintain new versions in all 3 repos?

@iliaross
Copy link
Collaborator Author

iliaross commented Aug 20, 2023

Doesn't that mean that users on versions older than 2.102 won't be able to upgrade beyond that release until they fix the repo, unless we maintain new versions in all 3 repos?

No. And why do you think that you'd need to support all three repos?

A repo 1,2 and 3 will get Webmin 2.102 (once). Webmin 2.102, when installed will switch all those old repos to the new one. And in the future, repos 1 and 2 cab be abandoned and only the new repo 3, i.e. webmin main would need to be supported ... right ... ?

@jcameron
Copy link
Collaborator

Yes, but only if we can assume that users of repos 1 and 2 will click the button to fix their local repositories. Otherwise they'll be stuck on the old version..

@iliaross
Copy link
Collaborator Author

Yes, but only if we can assume that users of repos 1 and 2 will click the button to fix their local repositories. Otherwise they'll be stuck on the old version..

Considering that a user cannot dismiss this warning, we could expect with a high probability that Webmin repos will be fixed eventually..

@jcameron
Copy link
Collaborator

Let's hold off on this change until we get a new webmin release out ..

@iliaross
Copy link
Collaborator Author

Alright, I wouldn't mind ..

@iliaross
Copy link
Collaborator Author

Are we moving on with this... ?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants