how come I can't update my endless OS using command line?. It brings this error. Is there something wrong in my sources.list? - debian-based

Err:1 http://obs-master.endlessm-sf.com:82/shared/eos eos3.7 InRelease
Could not connect to obs-master.endlessm-sf.com:82 (52.25.213.40), connection timed out
Reading package lists... Done
Building dependency tree... Done
All packages are up to date.
W: Failed to fetch http://obs-master.endlessm-sf.com:82/shared/eos/dists/eos3.7/InRelease Could not connect to obs-master.endlessm-sf.com:82 (52.25.213.40), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.
These are the only repositories in my source.list folder and sources.list.d is empty:
deb http://obs-master.endlessm-sf.com:82/shared/eos eos3.7 core endless
deb-src http://obs-master.endlessm-sf.com:82/shared/eos eos3.7 core endless

Endless use a read-only root file system managed by OSTree with application installed using Flatpak. You can use commands like dpkg -l which do not make changes to the system, but you cannot use commands like apt-get install.
Try this in terminal.
( flatpak update --appstream && flatpak update -y )
endlessos debian-based

Related

opam init fails - unable to create temp file

I have installed opam 2.1.0 on a Linux Virtualbox VM. When I try opam init, I get the following error:
<><> Fetching repository information ><><><><><><><><><><><><><><><><><><><><><>
[ERROR] Could not update repository "default": OpamDownload.Download_fail(_, "Curl
failed: \"/snap/bin/curl --write-out %{http_code}\\\\n --retry 3
--retry-delay 2 --user-agent opam/2.1.0 -L -o
/tmp/opam-32196-d33843/index.tar.gz.part --
https://opam.ocaml.org/index.tar.gz\" exited with code 23")
[ERROR] Initial download of repository failed.
Running with --disable-sandboxing doesn't help. I know that its a problem creating/writing to /tmp/opam-... directory because if I replace that with my current directory or home directory the command by itself runs fine. It also runs fine with /tmp/opam-... if I use the --create-dirs option in curl but I don't have any way of getting opam init to use that option. Any ideas?
thanks
Update
The reason opam init failed for me was because curl was installed with snap on my system. This exactly what is going on with your VM.
Try to run opam init -verbose and that could reveal more about why you ran into an error.
In my case I needed to install other things with opam and it kept failing every time. So snap uninstall curl and then sudo apt install curl fixed things. (Was only able to figure this out with help from my professor)
Workaround
I ran into the same issue and I found a workaround on the OCaml forum: here. (Credits to UnixJunkie)
You can run:
opam init github git+https://github.com/ocaml/opam-repository.git
This should avoid the certificate issues. This worked for me.
I tried to fix the certificate issues using this answer as well. You could try doing that, but it seems complicated when the workaround is to simply point it to the github repo directly.
This question is similar to this one.

VOLTTRON install on rasbian buster

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.

apache2 installation on linux:Unable to correct problems, you have held broken packages

i'm trying to install Apache on my Linux via terminal. used commands like
"sudo apt-get update && sudo apt-get upgrade"
and
"sudo apt-get install apache2"
i'm getting the error
"Unable to correct problems, you have held broken packages."
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
apache2 : Depends: apache2-bin (= 2.4.18-2ubuntu3.8) but it is not going to be installed
Depends: apache2-utils (>= 2.4)
E: Unable to correct problems, you have held broken packages.

yum database is locked

When I do yum update I get the following error response:
One of the configured repositories failed (Unkown),
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:
Contact the upstream for the repository and get them to fix the problem.
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).
Run the command with the repository temporarily disabled
yum --disablerepo= ...
Disable the repository permanently, 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
or
subscription-manager repos --disable=
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=.skip_if_unavailable=true
database is locked
I already did yum clean all, rm -f /var/lib/rpm/__db* and rpm --rebuilddb without any change.
After spending couple of days, finally fixed this error by deleting the following folder
/var/lib/yum/history

Completely remove mssql linux

Someone Help Please:
My Ubuntu 14 Server has 1 GB Memory, Was trying installation but it didn't complete. It was a mistake but now I can't completely remove it. Any external package I try to install fails, such as
(apt-get install python-requests) I get this error
(
/var/cache/apt/archives/mssql-server_14.0.800.90-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
)
Tried Uninstall but doesn't work
root#root: sudo apt-get remove mssql-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libc++1 libjemalloc1 libsss-nss-idmap0
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
mssql-server
0 upgraded, 0 newly installed, 1 to remove and 172 not upgraded.
184 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
dpkg: error processing package mssql-server (--remove):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
Errors were encountered while processing:
mssql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
I don't wan't to lose my server
If other external packages are failing to install, try removing the /etc/apt/sources.list.d/mssql-server.list file that you downloaded to register the Microsoft repository. Run sudo apt-get update. Then try installing the other external packages again and see if you have problems. This won't remove the failing mssql-server package, but maybe it will get you back and running with other packages.

Resources