I'm not missing anything right now.
Just want to know.
I notice that kernel 4.5.1 (14%) is using more RAM than 3.16 (3%).
And my auto shutdown cron jobs are working last night either.
-
-
Anyone using OMV 3 should definitely not upgrade to the new version 3.0.15. Stay on 3.0.13.
-
Anyone using OMV 3 should definitely not upgrade to the new version 3.0.15. Stay on 3.0.13.
New installation and plugins forcing me to a newer version so will have to upgrade to 3.0.15 anyway.
Too bad that everything stops working after the upgrade
I also need OMV 3 as of my hardware, no alternative there...
-
Upgrading is not forced. If you think you have to run OMV 3, you can manually install 3.0.13 and plugins until they are done being ported.
There is an alternative to running OMV 3. Install one of the 4.x kernels that you can find on this forum for OMV 2.x.
-
@Bramzi Look at LarsN post here to install 3.0.13.
[HOWTO] Downgrade to version 3.0.13 after accidentally upgrading to newer version (breaking things)
-
Found out that it is the clamav plugin that forces the upgrade:
CodeUnpacking clamdscan (0.99+dfsg-0+deb8u2) ... Preparing to unpack .../openmediavault_3.0.15_all.deb ... Unpacking openmediavault (3.0.15) over (3.0.13) ... >>> *************** Error *************** communication failure <<< *************************************Rollback
Happy with the new VM where I first try things out with a lot of snapshots. -
We convinced him to move to nginx in OMV 0.6 because of the noticeable speed increase.
It would be nice if github (as defacto standard) is used instead of sf.net for developing. At the moment there is to big burden to get something upstream - devs are lazy.
-
It would be nice if github (as defacto standard) is used instead of sf.net for developing. At the moment there is to big burden to get something upstream - devs are lazy.
We use github for all of the omv-extras plugins and I have a mirror of the omv code on github. But, Volker uses svn because that is what he prefers. svn is still a common standard and the tools are better in a lot of cases.What devs are lazy? Or are you just speaking in general? Volker is the only dev who works on core OMV. He does have bugtracker set up for requesting features.
-
What devs are lazy?
If I had an patch, for example, the barrier is much higher at sourceforge to get something done. Honestly I wouldn't even browse the code because sf is quit useless for this task nor would I follow the development because SF is horribly outdated in comparison to the other oss hosters.I'm not sure that it is the best to use outdated platform for development which "nobody" uses these days - but of course if Volker didn't want to change to git there is no real perspective to change this. Git is the gold standard - if you like it or not and the world keeps turning.
-
In my work team we switchted from SVN to Git, too. It's much more reliable. It's nearly impossible to get git hung up. Plus, it adds the possibility of pull requests. Which makes it possible for foreigners like me to send in patches. Plus it adds branching.
I know its hard to get used to it as SVN user. But it's really worth the effort.
-
I prefer git myself. Like I said, the plugins are on github. At work, I am an SVN admin for about 5000 developers. It is still used and not outdated.
If you want to follow OMV development on github, follow it here. I have git clone the svn repo and push it to github hourly. Then you could submit features/code to bugtracker. That is the best I can do until/if OMV code is moved to github.
-
-
Git vs. SVN is kinda off topic for this thread.
-
Git vs. SVN is kinda off topic for this thread.
Not really since having the source code in svn is keeping potential contributors from contributing to OMV3 (which may or may not speed up OMV 3 being stable). And we have closed most OMV3 threads so this is kind of a catchall (kernel, php version, plugins, git/svn, etc). -
Developers that could not create patches without GIT should not be called developers.
-
Maybe someone is lazy because they don't want to learn to use Subversion.
And that was an asinine statement about being lazy.
-
I disagree. Contributor does not equal developer. I should have said it isn't a protocol issue as much as hosting issue. Plenty of people can contribute who do not know svn/git/diff/patch/etc but know github. Creating and submitting a diff/patch on bugtracker is a deterrent for some. Forking a repo and submitting a pull request is very easy on github with good public visibility for review/comments and excellent tracking. If there was an svnhub, it would be just as easy.
-
I don't think implying Volker is lazy is the right approach to get his code on Github. Definitely not.... Volker is the only one with code on SF.
-
so question for today is, guys from debian dropped last week support of wheezy:
https://www.debian.org/News/20…rfeed&utm_medium=facebook
so i want to ask, what steps will be next?
-
Support isn't dropped. It is just called long term support now. This doesn't change anything with OMV 3. It still takes time and we are working on it.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!