I want to install something with MacPorts. However, I have a port installed (let's call it badport) that consistently fails to update. Every time I do port install x-package it tries to update everything before installing x-package. It inevitably fails to do anything with x-package because it's all hung up about badport, even though badport cannot possibly be a dependency (it's an application, not a library or even a command-line tool).
Further, for some reason, MacPorts tries to run all of these updates every time I run the command, as though the number of updates that ran successfully were rolled back solely because this end application failed to update.
Is there any way that I can tell MacPorts to stop trying to be "helpful" and just install my damn packages?
Related
Im relatively new to python world.
Im trying to install wxpython on several computers and it keeps failing.
I use anaconda version 4.9.2 and use the prompt command:
conda install -c anaconda wxpython
I get the following error message:
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
I try updating python to latest version. I try a number of things. and still I get this pesky problem. What am I doing wrong?
Thanks!
Nothing wrong per se. Those messages are indicating that Conda can't install that package without changing the currently installed packages. Because the Anaconda distribution (!= Conda) has lots of packages this happens very frequently. Also, this particular package is not updated frequently and the anaconda channel doesn't even seem to keep pace with that.
In general, it is better practice is to create new environments for each project/task you have to work on, and only install the packages you require. Also, the conda-forge channel tends to be a more consistent provider for packages, but undergoes less interoperability testing and tuning than the Anaconda channel packages. That is, consider trying something like
conda create -n myenv -c conda-forge python=3.9 wxpython ...
where myenv is whatever you would like to refer to the environment as, and ... should be whatever other packages you know you would like to use.
So I downloaded ArangoDB via homebrew yesterday. The documentation said to use the following to get the server started:
/usr/local/Cellar/arangodb/<VERSION>/sbin/arangod &
I ended up using the prompt shown on the terminal
/usr/local/opt/arangodb/sbin/arangod
Don't know if that necessarily makes a difference. Nonetheless, I got the server working.
Then I wanted to set up authentication. The docs did not say how to stop a server. Since I didn't know how to, I just closed the terminal window
Then I ran
/usr/local/opt/arangodb/sbin/arango-secure-installation
This then gave me an error
FATAL [...] database is locked by process ..: please stop it first and check that the lockfile 'usr/local/var/lib/arangodb3/LOCK' goes away. If you are sure no other arangod process is running, please remove the lockfile '/usr/local/var/lib/arangodb3/LOCK' and try again
How do I fix this? I had the webgui running but closing that didn't make a difference.
Another stack overflow question said to use the following commands:
brew services stop arangod
brew services start arangod
brew services restart arangod
None of those worked?
So, two questions:
a) how do I solve this problem
b) and, in the future, how do I properly terminate a server?
Thanks
You can use "brew services start/stop/restart arangod". It is no longer necessary to start arangod explicitly. If it has been started explicitly just do a "killall arangod" to stop it gracefully and start it using "brew services start".
Can I get a tip for installing on rasp buster? Im hung up on the install directions to check the status of the rabbitMQ server. Traceback of bash console:
(volttron) pi#raspberry:~/Desktop/volttron $ echo 'export RABBITMQ_HOME=$HOME/rabbitmq_server/rabbitmq_server-3.7.7'|sudo tee --append ~/.bashrc
export RABBITMQ_HOME=$HOME/rabbitmq_server/rabbitmq_server-3.7.7
(volttron) pi#raspberry:~/Desktop/volttron $ source ~/.bashrc
pi#raspberry:~/Desktop/volttron $ RABBITMQ_HOME/sbin/rabbitmqctl status
bash: RABBITMQ_HOME/sbin/rabbitmqctl: No such file or directory
There are a few tracebacks earlier on the installation...
If it makes a difference or not here is the entire bash console process. The git gist link I just created the name install.py even though its just bash commands copied pasted per install directions...
`pi#raspberry:~/Desktop $ git clone https://github.com/VOLTTRON/volttron --branch releases/7.x`
It looks like there are a couple of different issues going on here:
The issue you quote above (RABBITMQ_HOME/sbin/rabbitmqctl: No such file or directory) is that your shell isn't finding the rabbitmqctl command. It looks like you added the RABBITMQ_HOME environment variable to your .bashrc, but used the string RABBITMQ_HOME instead of the variable expansion $RABBITMQ_HOME when you tried to run the command. Try running it as $RABBITMQ_HOME/sbin/rabbitmqctl status instead.
The rabbitmqctl status command will check the status of the rabbitmq application, but I don't think you've done anything to start it yet (that happens when you bootstrap the platform and/or start the platform configured to use the RMQ broker)
I think that the traces earlier in the installation process are problematic (appears to be the same error hit two different ways), but you just haven't run into them yet. I haven't seen any issues building gevent on the RPi 4 with buster (though it is pretty slow), but the ctypes error makes me wonder if there's an issue with the underlying c library it is trying to build on top of. I did notice that you're getting amd64 erlang packages, are you running Raspbian on an x86 processor? (if so this isn't a permutation we've tried and you may be hitting some package compatibility edge case we haven't seen)
One thing to try is to manually install cython into your virtualenvironment and then try running the bootstrap script again with the virtualenvironment activated. You could also try and pip install gevent==20.6.1 directly in that virtualenvironment (this is what the bootstrap script was doing at the failure point). VOLTTRON depends on gevent, so if that isn't installing the platform won't be able to run.
In submitting my R job to a cluster using the Rscript myscript.R command, I keep getting an error message saying the packages I have asked to load do not exist. However I have installed these packages onto a library on my profile. Do I have to set the working directory into the same pathway as the where the R packages are contained? I am genuinely puzzled by how to fix this error.
Thanks
Nikhail
try to add directly the install.packages command in your script. Like that, you're sure it will install properly:
for example add that at the beginning of your script (of course change "pacman;" for your real package and add one line per package):
if (!require("pacman")) install.packages("pacman")
I had this kind of problem before when the shell didn't call the good R for me (other version than the one I thought or 32 bits vs 64 bits). Don't know if it's your problem however...
I've been trying to install MacPorts on a new Mac Pro with a fresh, fully updated Yosemite OS. The installer hangs on 'Running package scripts'. So I tried to build it from source. That works, with the installer stating:
Congratulations, you have successfully installed the MacPorts system.
However, it seems unusable. When I do sudo port install apache2 I get the message:
Error: Port apache2 not found
Simply trying to do a 'self update' (as root):
sh-3.2# port -d selfupdate
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
---> Updating MacPorts base sources using rsync
receiving file list ... done
base.tar
...and then nothing... I've waited for half an hour, but it won't go any further. I can't find any logs either.
Again: there's nothing special about my setup, it's out-of-the-box Yosemite, only updated through the App store and, of course, I've installed Xcode with command line utilities and formally accepted the license, as is required according to the MacPorts site.
I've also tried uninstalling it, using the instructions from the MacPorts site, and reinstalling. But it does not make a difference.
I've read quite a few forum posts, but I can't find any post relating a problem like this. I hope someone can shed some light on this.
The installer hangs running package scripts because the last statement in these package scripts is exactly this "sudo port selfupdate" that you've been running manually afterwards.
Because this step did never run, your MacPorts installation lacks knowledge about the apache2 port (which is exactly why the installer runs selfupdate to give you a full-featured installation).
Unfortunately Apple's infrastructure (rsync.macports.org) seems to have connectivity problems at the moment, which is causing problems for quite a few people. You can try using one of the mirrors as outlined at https://trac.macports.org/wiki/Mirrors.