If I understand aright you had to manually install the release package for 7.4 beta:
yum install http://packages.nethserver.org/nethserver/7.4.1708/updates/x86_64/Packages/nethserver-release-7-3.1.ge457d21.ns7.noarch.rpm
EDIT!!!
Now I have found the following:
It’s the same for 7.5. But why we get the updates automatically at the software center?
Isn’t it still the same? Nethserver alpha or beta packages are not installed automatically. The problem is that centos base packages and others get updated and don’t “fit” to the existing Nethserver packages.
There should be a warning, it’s not updated automatically.
That’s right, but at the softwarecenter you can only install all updates.
Yes you’re right, I only see Cent OS 7.5 upstream update.
Hi guys,
Depends of the updates of the NS modules.
Sometimes are only CentOS updates, sometimes are only NS updates and sometimes are both.
I thing the separate updates is the best solution.
I understand your frustration and all the rants around the recent update stability.
We are NethServer!
Where we can find a technical solution to an issue we can improve tirelessly.
See also my today’s reply here: Lock to “current release” enabled by default from 7.5?
Hi guys, thanks for taking this serious. I’m really frustated about this.
Could be a good approach and should be reachable in a short time.
Also a good idea,if possible. IIUC you mean 2 catogories like nethsverver-updates and upstream-updates to choose seperately.
This is only a solution for nethservians IMO. My concerns are about those who want to test and become new members or those who are not as deep in this software as some others.
Maybe you @davidep can hep to understand why we never had these problems with V6.
Is it only because of the subscruption?
PS: I deliberately opened this topic in plublic, because I think this is important for every one.
Yes.
I wrote about this for many times …
It’s not my idea, it’s from Zentyal. And I think it’s a good thing.
Anyway, I don’t think is about losing faith and trust in Nethserver!
Just some problems which will be solved!
I think your contribution to NS is worth taking into account and nobody will blame you!
I feel you. But the answer is absolutely NO.
Subscription is just an answer to a problem that has been around for a long time, we talked about this at our last NethServer Conference 8 months ago.
It’s a technical problem that we need to resolve or at least to minimise. As always TOGETHER
I choosed this titel to show how frutrated I am. 
Maybe a little to dramatic. 
No, #subscription has nothing to do with this!
I think I partially answered to this question here: Lock to "current release" enabled by default from 7.5?
About v6: it depends on RHEL lifecycle. ns6 started from 6.5 up to 6.9, whilst ns7 started from 7.3 and we’re now at 7.5! It corresponds to production phase 1 where upstream pushes more components updates at minor release points.
Furthermore ns6 has no customized kernel modules!
I understand you and I hope also all our friends from NS!
With this machine I started with V6.6 I think, so there were 3 updates of minor releases. Never had a problem. Always applied the update and everything was fine AFAIR and we also hadn’t had this problem with V7.3 to V7.4. That’s the reason why I’m wondering.
I understand this thing with the two layers, but can’t they be seperated to choose?
AFAIK the rpm of the “old” release of upstream goes to vault-repo when a new release is released by centos. Is it possible to change the upstream-repo to vault the moment a new release ist born?
Or maybe to manually enable/disable repos in GUI?
Are you kidding me? 7.3 to 7.4 was a mess too! Surely not for everyone…
About 6 hypothetical stability: you started at a more stable release: 6.6 was probably in RHEL production phase 2 that means less features
My point of view is that there are issues that needs to be solved.
Nethserver is flexible, powerful, feature-rich. Now it’s not stable.
Developers can help to regain the lost stability.
And the community can help to.
I am positive, anyway. It’ wont be easy, but i feel confident that the situation will evolve successfully.
Please may I butt-in to the conversation.
In my experience, no operating system is immune from updates which break things. All of the offerings from Redmond have had, or do have, problems with updates. Linux is no different. Every linux distro I’ve used has had problems with updates, Fedora, CentOS, Debian, Ubuntu, Mint, SuSe, Slackware…they all have the same problem a bad update with break the system. I’ve even broken an NT4 system by installing bad anti virus updates.
The only difference I see between different operating systems is how well they recover from bad updates. In Redmonds case this seems to be pot luck and Linux is much the same (for the average user). Every Linux problem I’ve ever had involves accessing the terminal, so if you have a broken system then most people are finished.
I think the problem is that people expect their IT systems to work all the time. They are much better now, but they used to be awfull! (See my comment about NT4 and a bad anti virus update).
May I suggest that for those people using free software (which Linux is) it’s presented with a statement that says there is no guarantee an update won’t break the system.
If you pay for updates, that should come with reasonable confidence they will work. But even then you can’t guarantee some odd system config won’t have a problem. In my experience its “user beware” on ANY operating system, and NethServer is no different.
The only Operating system I’ve found that can recover from bad updates is Solaris and ZFS, but even that isn’t a recovery, it’s a roll back to a working config (which is how Redmond operates with their latest system recovery tools).
Sorry for interrupting the discussion, but I just wanted to highlight that every operating system has problems with updates. It’s up to the user to have system data backed up so they can re-install and carry on.
Regards
Bob
Also we had a big problem with samba upstream update last year.
But if we can find a solution, it is a very good thing.
I’m completely with you and your comment is really welcome. You didn’t interrupt, you enriched this discussion.
What frustated me is, that it’s impossible to setup a stable machine. And that’s a difference to others.
You have the choice between an old maybe buggy and instable machine and a instable alpha-release machine. Nothing between. And that’s IMO the bad thing.
That updates can break something and that an admin has to decied what to install and that she/he is reposible for her/his work I’m absolutely aware.
@davidep sorry to bother you again, but I need your opinion.
I created a repo-file called “CentOS-temporary” with this content:
# CentOS temporary contains rpms from CentOS 7.4.1708
[C7.4.1708-extras]
name=CentOS-7.4.1708 - Extras
baseurl=http://mirror.centos.org/centos-7/7.4.1708/extras/x86_64
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=1
[C7.4.1708-base]
name=CentOS-7.4.1708 - CentOSPlus
baseurl=http://mirror.centos.org/centos-7/7.4.1708/os/x86_64/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=1
[C7.4.1708-updates]
name=CentOS-7.4.1708 - Base
baseurl=http://mirror.centos.org/centos-7/7.4.1708/updates/x86_64/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=1
[C7.4.1708-centosplus]
name=CentOS-7.4.1708 - Base
baseurl=http://mirror.centos.org/centos-7/7.4.1708/centosplus/x86_64/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
enabled=1
With the standard-centos repos disabled and this enabled, I can install the latest 7.4 stable version with kernel 3.10.0.693.21.
Is this compatibel with nethserver-repos-content?
Or in other words: Bad or good idea?
EDIT: This is no longer available. Repo moved to Centos-vault!