Closed jefmes closed 6 years ago
Just to follow up, when using --skip-broken as it suggests, it fails differently.
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.pac-12.org
* epel: mirror.sfo12.us.leaseweb.net
* extras: mirror.lax.hugeserver.com
* updates: mirrors.psychz.net
Resolving Dependencies
--> Running transaction check
---> Package Minecraft-Overviewer.x86_64 0:0.12.31-1.el6 will be installed
--> Processing Dependency: python(abi) = 2.6 for package: Minecraft-Overviewer-0 .12.31-1.el6.x86_64
--> Processing Dependency: libpython2.6.so.1.0()(64bit) for package: Minecraft-O verviewer-0.12.31-1.el6.x86_64
http://overviewer.org/rpms/7/x86_64/repodata/filelists.xml.gz: [Errno 14] HTTP E rror 404 - Not Found
Trying other mirror.
One of the configured repositories failed (Minecraft-Overviewer - 7 - x86_64),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:
yum-config-manager --disable overviewer
4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=overviewer.skip_if_unavailable=tr ue
failure: repodata/filelists.xml.gz from overviewer: [Errno 256] No more mirrors to try.
http://overviewer.org/rpms/7/x86_64/repodata/filelists.xml.gz: [Errno 14] HTTP E rror 404 - Not Found
Sorry for the ignorance, I'm still getting familiar with GitHub. :) So how does this work? I imagine not anyone can jump in and fix this, because there is likely a limited number of people who have access to update the RPM repodata. Is there anything I can do to help, or is there more data that needs to be provided? I noticed there isn't even a directory for 7. If someone can take care of that, I'd be happy to try it again and see if I get different results.
I think what we need to do is setup a new rpm builder for CentOS7. @aheadley should hopefully look at this soon. You're right, this isn't really an Overviewer code issue, something needs to change in our backend build infrastructure. If someone really wants to get their hands dirty, I think what we need is an investigation about why this python26 dependency is coming from. Ultimately I think we need a new spec file for CentOS/RHEL 7. @aheadley can yell at me if I'm off track, though.
In the meantime, you should be able to easily build Overviewer from source. Check the docs for details and let us know if you run into any issues
Thanks, greatly appreciate the response! I'll go ahead and recompile it for my server for now then and check in later.
I was able to install on CentOS 7 using the Fedora 19 repo.
Can someone maybe tell me how I can install overviewer on my VPS with centOS 7 activated??
I tried this out: http://docs.overviewer.org/en/latest/building/#centos-5
But when I try the command python setup.py build.
I get this error:
[root@play Minecraft-Overviewer]# python setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/util.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/nbt.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/logger.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/rendermodes.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/progressbar.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/items.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/optimizeimages.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/cache.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/__init__.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/observer.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/overviewer_version.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/settingsValidators.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/tileset.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/textures.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/configParser.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/settingsDefinition.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/files.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/assetmanager.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/rcon.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/world.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/signals.py -> build/lib.linux-x86_64-2.7/overviewer_core
copying overviewer_core/dispatcher.py -> build/lib.linux-x86_64-2.7/overviewer_core
creating build/lib.linux-x86_64-2.7/overviewer_core/aux_files
copying overviewer_core/aux_files/genPOI.py -> build/lib.linux-x86_64-2.7/overviewer_core/aux_files
copying overviewer_core/aux_files/__init__.py -> build/lib.linux-x86_64-2.7/overviewer_core/aux_files
creating build/lib.linux-x86_64-2.7/overviewer_core/data
creating build/lib.linux-x86_64-2.7/overviewer_core/data/textures
copying overviewer_core/data/textures/grass.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/textures
copying overviewer_core/data/textures/portal.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/textures
copying overviewer_core/data/textures/lava.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/textures
copying overviewer_core/data/textures/foliage.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/textures
copying overviewer_core/data/textures/ender.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/textures
copying overviewer_core/data/textures/normal_double.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/textures
copying overviewer_core/data/textures/fire.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/textures
copying overviewer_core/data/textures/light_normal.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/textures
copying overviewer_core/data/textures/watercolor.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/textures
copying overviewer_core/data/textures/chest.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/textures
copying overviewer_core/data/textures/water.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/textures
creating build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
creating build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_tower_red.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_anvil.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_hoe.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_base_plain.svg -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_ship.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_town.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_hoe_red.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_town_red.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_anvil_red.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_factory.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_factory_red.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_ship_red.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_base_plain_red.svg -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_tower.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_mine.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/icons/marker_mine_red.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets/icons
copying overviewer_core/data/web_assets/compass_upper-right.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/signpost-shadow.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/backbone.js -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/overviewer.css -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/control-bg-active.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/regions.js -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/index.html -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/control-bg.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/bed.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/compass_lower-right.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/underscore.js -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/compass_lower-left.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/compass_upper-left.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/signpost_icon.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
copying overviewer_core/data/web_assets/signpost.png -> build/lib.linux-x86_64-2.7/overviewer_core/data/web_assets
creating build/lib.linux-x86_64-2.7/overviewer_core/data/js_src
copying overviewer_core/data/js_src/overviewer.js -> build/lib.linux-x86_64-2.7/overviewer_core/data/js_src
copying overviewer_core/data/js_src/util.js -> build/lib.linux-x86_64-2.7/overviewer_core/data/js_src
copying overviewer_core/data/js_src/views.js -> build/lib.linux-x86_64-2.7/overviewer_core/data/js_src
copying overviewer_core/data/js_src/models.js -> build/lib.linux-x86_64-2.7/overviewer_core/data/js_src
running build_ext
building 'overviewer_core.c_overviewer' extension
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/overviewer_core
creating build/temp.linux-x86_64-2.7/overviewer_core/src
creating build/temp.linux-x86_64-2.7/overviewer_core/src/primitives
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I. -I/usr/lib64/python2.7/site-packages/numpy/core/include -I/usr/include/python2.7 -c overviewer_core/src/main.c -o build/temp.linux-x86_64-2.7/overviewer_core/src/main.o -Wno-unused-variable -Wno-unused-function -Wdeclaration-after-statement -Werror=declaration-after-statement
In file included from /usr/lib64/python2.7/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728:0,
from /usr/lib64/python2.7/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
from /usr/lib64/python2.7/site-packages/numpy/core/include/numpy/arrayobject.h:15,
from overviewer_core/src/overviewer.h:33,
from overviewer_core/src/main.c:18:
/usr/lib64/python2.7/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: warning: #warning "Using deprecated NumPy API, disable it by #defining NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
#warning "Using deprecated NumPy API, disable it by #defining NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
^
In file included from overviewer_core/src/main.c:18:0:
overviewer_core/src/overviewer.h:34:21: fatal error: Imaging.h: No such file or directory
#include <Imaging.h>
^
compilation terminated.
Traceback (most recent call last):
File "setup.py", line 273, in run
build.run(self)
CompileError: command 'gcc' failed with exit status 1
``
Failed to build Overviewer!
Please review the errors printed above and the build instructions
at <http://docs.overviewer.org/en/latest/building/>. If you are
still having build problems, file an incident on the github tracker
or find us in IRC.
This error (Imaging.h: No such file or directory) means you're missing the python-imaging-devel
package
And how can I use the correct one??
Install the package python-pillow-devel
with yum.
Alright gone try that right now. thnx for the tip
wow thanks it worked. Thank you so much!
Fedora 22 / EL7 rpm directories would be highly appreciated! :+1:
EL7 rpm directories would be greatly appreciated.
I managed to get overviewer installed in January 2015, but am unable to update.
I've even tried to consume the EL6 rpm directories with the same resulting installation failures.
Your best bet is to install it from source (ugh)
Like so...
yum install -y python-imaging python-pillow-devel python-devel numpy
cd /usr/local/src
git clone git://github.com/overviewer/Minecraft-Overviewer.git
# Give this a bit to grab the repo, you will find it easier to update if you grab the repo and not just a zip from github
cd Minecraft-Overviewer
python setup.py build
I did setup a copr repository for Fedora!
https://copr.fedorainfracloud.org/coprs/enaut/minecraft-overviewer-weekly/
As I cannot test CentOS I did not enable those so far but as soon as someone is up to do the Testing and debugging I'm happy to enable epel builds (I did it).
I'm doing the updates manually whenever something is committed to overviewer. The tito branch with the specfile source is here: https://github.com/enaut/Minecraft-Overviewer/tree/weekly-tito
I used the rep @enaut setup and I'll let you know how it works. Running CentOS 7.
Still no sane path for el7 users... I just wont go Ubuntu for this, so I suppose I'm stuck on el6, and will have to restore my backup image.
Given the date I assume it's past an effort. Wanted to keep my minecraft server OS up to date, but hardly think el7 is bleeding edge ...
Manual install does not work as expected either, using the exact same process described above, however doubly frustrating as this is a dependency of sandain's mscs script hosted elsewhere here... which equally does not play nice on el7.
@rrimc69 just build from source, no need to get all melodramatic.
@rrimc69 Did you try the repos from copr I created? https://copr.fedorainfracloud.org/coprs/enaut/minecraft-overviewer-weekly/
@enaut, no I haven't, but thanks for the suggestion. I'm only now starting migration of all EL5/6 kit at work to El7, so worth the hunt & fix, and kind of fun looking at newer documentation with systemctl too.
I did find the root cause of my issues with mscs and overviewer, during an further re-build. The cause is EL7 sudo's path re-interpretation behavior and overviewers' manual scripted install location, along with the way mscs calls it.
For further details see here: https://github.com/MinecraftServerControl/mscs/issues/142
@CounterPillow I accept I may not have been very clear with my text, 'Manual install' ~ 'install from source'. I did build my initial VM from source and overviewer clearly has EL7 issues, as does the mscs script.
You may wish to review the link above, and reflect on the content. It may assist with bringing overviewer.py in line with the practices adhered to by the vast majority of the code I've deployed at work, or home, be it Windows, Linux or BSD, that just work 'out of the box' for the intended use, by the right user.
It is interesting you find 'Articulate' is synonymous with 'Melodramatic' ... User frustration is clearly lost in translation for you. I'm not a kid learning coding, so by all means ... play the man not the ball, and continue to complain about my felicity of style. You'll only further expose your intellect by doing so.
Cheers,
Rory
@CounterPillow I wouldn't say that was melodramatic.. it's frustrating. As I'm sure you've realised.
CentOS 6 is actually stopping its full updates next year and moving to maintenance updates only. CentOS 5 stopped receiving full updates in 2014 and is currently on maintenance updates.. and those end early next year. 😨
I think we should come back to the original issue of this ticket and simply add a package for CentOS 7. If preferred, I'm happy to help do that. 😃
What are the chances that symlinking a CentOS 7 directory would work? Can somebody on CentOS 7 try the most recent CentOS 6 RPM?
@rrimc69
I did build my initial VM from source and overviewer clearly has EL7 issues
Mind sharing what those issues are then, if they're unrelated to third-party scripts and missing binary packages from our side? Because as far as I can see, overviewer should run just fine from source. If you're having trouble with a third party script making improper assumptions about installation paths, then that's not an overviewer issue.
Ok.. -bash-4.2$ whoami minecraft -bash-4.2$ which /usr/local/bin/mscs /usr/local/bin/mscs -bash-4.2$ which /usr/local/bin/msctl /usr/local/bin/msctl -bash-4.2$ mscs create wembledon 25567 10.0.0.99 which: no overviewer.py in (/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin) Creating Minecraft world: wembledon. -bash-4.2$ mscs status which: no overviewer.py in (/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin) Minecraft Server Status: wembledon: not running. wombledon: not running. -bash-4.2$ exit
@rrimc69 could you show me the steps where you actually build and install overviewer from source? I don't know what mscs is, and just because mscs can't find overviewer doesn't mean the problem lies with overviewer.
Sudo behaviour as described here in un-related works: http://serverfault.com/questions/528096/sudo-passenger-memory-stats-command-not-found
My Host: [root@mine2 worlds]# sudo sh -c 'echo $PATH' /sbin:/bin:/usr/sbin:/usr/bin [root@mine2 worlds]# which sudo /usr/bin/sudo [root@mine2 worlds]# cat /etc/redhat-release CentOS Linux release 7.2.1511 (Core) [root@mine2 worlds]#
Here.. OverviewerBuildOutput.txt
You've clearly not followed the link... or read the text.
@rrimc69 you have built Overviewer, but not installed it, technically. You would need to run setup.py install
to do that, but I don't recommend it (it could conflict with the CentOS 7 RPMs when we fix those).
Overviewer will happily run from /opt/Minecraft-Overviewer
. You just have to add that to your $PATH
.
I don't know why, but mscs
is running Overviewer as root. So you'll need to add /opt/Minecraft-Overviewer
to root's $PATH
as well. I would stick it at the end of your $PATH
, so that when the RPMs are fixed, the RPM version will take precedence.
I suppose I could sudo run the installer but that is not the advice up the stream.
Review your documentation ... right now.. http://docs.overviewer.org/en/latest/building/#linux
No example of .. 'install' given. Nor in the the mention of source build above. Shan't be accused of not reading the manual now...
@rrimc69 we do not mention install
because we don't recommend doing it. Like I said, it can break actual prebuilt packages.
When you build from source, you're expected to run it from the place you extracted it. As mentioned in the next section, Running the Overviewer...
For Mac or Linux builds from source, you would run something like this with the current directory in the top level of the source tree:
./overviewer.py /opt/minecraft/server/world /opt/minecraft/mcmap
The confusion seems to be coming from the fact that mscs
doesn't do that, or provide a way to do that. That's not something in our control (you'll have to take it up with the mscs guys) but it is something you can fix by putting the Overviewer source directory in your $PATH
.
@agrif Granted it works if directly called, you will see I've already stated that it commenced for me as a sudo path issue, and offered that feedback to the mscs author. Still an issue for EL7 overview users however who may well expect the installation binary to be in one of the standard PATH locations.
Your OP user may well have bumped that issue and not commented. I have, at least if they read this thread they'll 'get it' if they're regular EL6/7 users.
It may well be I've not 'installed' it, but it appears the documentation for a Linux manual install does not show this step, and it is clearly not inherent knowledge that it requires an install invocation. A job for the installer, yes I do see your point. However, in fairness, I'm on Linux not OSX so not likely to read OSX install text.. nor would most time poor sysadmins with bad habits, and .. language issues .. :)
It was not our intention that the "Build from Source" section of our documentation be seen as an installation guide. We deliberately chose to use "install" to refer to the prebuilt binaries, and only say "build" for the source-based method, since no install actually ever happens.
I'm sorry if this caused confusion.
@agrif thanks for your measured input. I reviewed what you said, yes I have not installed it. It may be In the absence of a packaged solution, the install from source documentation is the eventual outcome, so may be more focus is needed there.
I generate the openproject work packages for all ICT in my org, and that tool has a workflow functionality. (Beats server built/admin tasks at the moment..) One particular tool used in that documentation review is 'use case' focused reviews. I normally schedule documentation review after code review in my project plans, It works and normally, this finds holes and weaknesses in the existing documentation. An automated process that, or something similar, if git hub supports it, may be useful to you.
You may still wish to reflect on or consider the sudo behavior as part of your EL7 packaging effort, the /usr/local/bin location will not be found by sudo, either, if used for your package.
To test, I removed my symlink and ran `python setup.py install' it completed OK as far as I can see, can't provide the text output, I accidently dropped the shell and lost the buffer, sorry. Binary is available afterwards to user, and 3rd party script alike:
[rory@mine2 ~]$ which overviewer.py /usr/local/bin/overviewer.py [rory@mine2 ~]$ sudo mscs status [sudo] password for rory: Minecraft Server Status: 2ring: running. Process ID: 24400. Memory used: 529924 kB. landoffun: running. Process ID: 24570. Memory used: 428836 kB. oblivion: running. Process ID: 24749. Memory used: 534480 kB. r3dbird: running. Process ID: 24928. Memory used: 442248 kB. wembledon: running version 1.11 (0 of 20 users online). Process ID: 25216. Memory used: 577140 kB. wombledon: running version 1.11 (0 of 20 users online). Process ID: 25514. Memory used: 974928 kB. [rory@mine2 ~]$
Cheers,
Rory.
Oh .. and thanks belatedly.
setup.py install
will default to /usr/local/bin
, in rather the same way any GNU autotools packages do. However, the rpm packages (IIRC) will install to /usr/bin
, as you would expect from a proper package.
Not having a package for CentOS 7 sucks, we know. Most of us have been terrifically busy (for instance, I started grad school) and don't have time to work on Overviewer like we used to. That said, a fix is coming down the pipes, so bear with us.
lol.. thats fine agrif, I get busy and complex, I do it for a living, I can relate.
I've no personal expectation of instant fix though, my box works now, and I can build host and populate worlds from backup, using scripts/pxe menu in about 20 minutes. Think I'll leave automated renders till there is an rpm though.
I hope this discussion helps in some small way to get your EL7 solution closer to done.
Note for @jefmes, if your still tuned in, hope this helps, my eventual working build was brutally minimal no desktop, epel was required for other reasons, below are the just python related rpms as at Nov '17, I note there is no 2.6 in there, with full rpm attached if you need to dive deeper. Mine2-rpm-list.txt
Just the python kit:
[rory@mine2 ~]$ yum list installed | grep python
dbus-python.x86_64 1.1.1-9.el7 @anaconda
libselinux-python.x86_64 2.2.2-6.el7 @anaconda
newt-python.x86_64 0.52.15-4.el7 @anaconda
python.x86_64 2.7.5-39.el7_2 @updates
python-backports.x86_64 1.0-8.el7 @base
python-backports-ssl_match_hostname.noarch
python-configobj.noarch 4.7.2-7.el7 @anaconda
python-decorator.noarch 3.4.0-3.el7 @anaconda
python-devel.x86_64 2.7.5-39.el7_2 @updates
python-iniparse.noarch 0.4-9.el7 @anaconda
python-javapackages.noarch 3.4.1-11.el7 @base
python-libs.x86_64 2.7.5-39.el7_2 @updates
python-lxml.x86_64 3.2.1-4.el7 @base
python-nose.noarch 1.3.0-3.el7 @base
python-perf.x86_64 3.10.0-327.36.3.el7 @updates
python-pillow.x86_64 2.0.0-19.gitd1c6db8.el7 @base
python-pillow-devel.x86_64 2.0.0-19.gitd1c6db8.el7 @base
python-pip.noarch 7.1.0-1.el7 @epel
python-pycurl.x86_64 7.19.0-17.el7 @anaconda
python-pyudev.noarch 0.15-7.el7_2.1 @updates
python-setuptools.noarch 0.9.8-4.el7 @base
python-slip.noarch 0.4.0-2.el7 @anaconda
python-slip-dbus.noarch 0.4.0-2.el7 @anaconda
python-urlgrabber.noarch 3.10-7.el7 @anaconda
rpm-python.x86_64 4.11.3-17.el7 @anaconda
[rory@mine2 ~]$
Cheers,
Rory.
We've been making slow but steady progress on this, and we are now building RPMs for centos7. A RPM repository is not yet set up yet, but you can find the latest RPM for centos7 here:
This corresponds to the latest master (at the time of this writing, 63df7976814e297175ad0b17ebb4112557d9235b)
Great to hear!
Awsome. sounds great, now all I need is time to go test :) employer has had me full capacity for 2 months now .. holidays soon !!
On 23 March 2017 at 12:39, Mark Hughes notifications@github.com wrote:
Great to hear!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/overviewer/Minecraft-Overviewer/issues/1204#issuecomment-288591934, or mute the thread https://github.com/notifications/unsubscribe-auth/AIU33DIR3NqBorOiATmZDok5dlXOwoQHks5roc1tgaJpZM4DdJQX .
Soooooooooo are you guys supporting EL7 yet?
@seifer44 there's no problem with the code, you can run Overviewer on EL7 right now, and have been able to for years.
There's just no repo of prebuilt binary packages.
@seifer44 was asking about support for EL7 not the code @CounterPillow
Isn't the RPM being created already, or at least it's trying to copy it over?
Who is actually in charge of the repository? Maybe someone should ask them as it's quite a simple task. It's simply just not being published to https://overviewer.org/rpms/
On another - I do not understand why you are being so incredibly stubborn on this topic. Do you have some kind of weird awkward hate for EL that you leave everyone who uses it to manually update and build it themselves? Why?
@Markehme nailed it. I see EL6 is supported, and on another thread somewhere around here, EL7 is supported by subscribing to latest for the version instead of 7. Also, this page makes it seem like EL7 isn't supported at all.
On top of that, the packages in the latest repository don't even include the 1.12 version support. I had to go find the package manually here.
With all of that in mind, it doesn't seem very supported to me.
@MarkehMe I'm not being stubborn, I just don't use any RPM-based distros and have nothing to do with the build infrastructure and direct people to the appropriate solution for the time being, which is building from source, which is really not all that hard.
Please stop acting like this is somehow a big company's product you're paying for and can make demands to, because this is really just a bunch of dudes doing stuff in their free time, and you're basically telling them to use their free time in a way that benefits you without spending any of your own free time on this.
@CounterPillow sure we won't call it stubborn 😉 - however if you reread your past comments you sure don't sound like you even want to even push for it.
No one is acting like it's a big company product we're paying for. It doesn't benefit me anymore, we're all just getting impatient.
When an easy fix issue like this goes on for over 2 and a half years people are going to be annoyed - obviously - and complain, and you're the only one responding so yes, you're going to cop a mouthful from people. Your efforts are appreciated, but our responses are nothing but human.
¯\_(ツ)_/¯
Then here's things you can do:
anything else (including shitty reaction GIFs in github issues) is a waste of time.
I think you may be mistaken. CentOS is part of the Enterprise Linux (EL) definition. CentOS, being free, is used by a lot of individuals running servers (including me).
This got toxic. How about I offer to help, instead. Is there an automation tool that you guys use? It might not be that hard to push stuff to all of those places that I mentioned. Also, is there any serious difference to the package for the other RPM supported distributions? If not, maybe remove the distro part of the package name in the SPEC file.
I'm running a pretty standard VM on DigitalOcean with CentOS 7, and I managed to get Overviewer working for a few months after building it myself. I was hoping by now there would be a CentOS 7 repo available and I'd really rather keep Overviewer updated via yum than have to use my kludgy mess. CentOS 7 ships with Python 2.7 also, so I'm getting the following message when I try to add the current repo from the CentOS instructions here:
http://docs.overviewer.org/en/latest/installing/
Here is the output I'm getting when attempting to install Overviewer via yum right now. Maybe I'm just missing something, but I thought someone might want to clean up the behavior for CentOS/RHEL 7 users.