Trouble installing GNU Ring on Flidas
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
Installed Ring, using the same method for Ubuntu 16.04 at
https://ring.cx/en/download/gnu-linux
These instructions (minus the one referring to "universe") worked on the experimental install I did on a USB stick. But I did a fresh install to the internal drive yesterday, and it's not working.
Here's what I did:
* fresh install on Flidas on internal drive
* sudo apt-get update && sudo apt-get upgrade
* sudo apt-get update && sudo apt-get dist-upgrade
* autoremove, autoclean, clan
* followed the instructions at the link above for installing Ring on 16.04
Here's the output I got back:
strypey@Bishop:~$ sudo apt-get install ring
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:
ring : Depends: libayatana-appindicator3-1 (>= 0.4.90) but it is not installable
Depends: libebook-1.2-19 (>= 3.17) but it is not installable
Depends: libedataserver-1.2-23 (>= 3.17) but it is not installable
Depends: libgtk-3-0 (>= 3.21.5) but 3.18.9-1ubuntu3.3 is to be installed
Depends: libqt5core5a (>= 5.9.0~beta) but 5.5.1+dfsg-16ubuntu7.5 is to be installed
Depends: ring-daemon (= 20180816.2.e26b79f~dfsg1-1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Any suggestions?
Output of: cat /etc/apt/sources.list.d/ring-nightly-main.list
> deb https://dl.ring.cx/ring-nightly/ubuntu_18.04/ ring main
Hmm. Perhaps this is a case of user error? ;-P
If I have accidentally followed the instructions for 18.04, instead of 16.04, what's the best way to undo what I did, so I can try again with the correct instructions?
Yes, it seems like I accidentally followed the instructions for 18.04, instead of 16.04. I tried again, following the 16.04 instructions, and it seems to be working now. Is there anything I need to do to undo the things I did when I followed the wrong set of instructions?
EDIT: as I remember from last time, my systems seems to be having a lot of trouble download files from the Ring repos. I'm having to run the install command over and over with --fix-missing. Now that Ring has reached a 1.0 release, it would be great to see it packaged into Debian, then Ubuntu, then Trisquel ;)
> Is there anything I need to do to undo the things I
> did when I followed the wrong set of instructions?
If apt no longer says you have broken packages, and if /etc/apt/sources.list.d/ring-nightly-main.list now says "16.04" instead of "18.04", I don't think you need to do anything else.
Thanks for helping me identify my initial error :)
Current output of: cat /etc/apt/sources.list.d/ring-nightly-main.list
deb https://dl.ring.cx/ring-nightly/ubuntu_16.04/ ring main
However, after a number of tries, I noticed I kept getting this error:
Get:1 https://dl.ring.cx/ring-nightly/ubuntu_16.04 ring/main i386 ring-daemon i386 20180816.2.e26b79f~dfsg1-1 [6,188 kB]
Err:1 https://dl.ring.cx/ring-nightly/ubuntu_16.04 ring/main i386 ring-daemon i386 20180816.2.e26b79f~dfsg1-1
GnuTLS recv error (-9): A TLS packet with unexpected length was received.
Unable to correct missing packages.
E: Failed to fetch https://dl.ring.cx/ring-nightly/ubuntu_16.04/pool/main/r/ring/ring-daemon_20180816.2.e26b79f~dfsg1-1_i386.deb GnuTLS recv error (-9): A TLS packet with unexpected length was received.
Then, just on a hunch, I tried it again without the --fix-missing ... and now it's installed!
My username is 'strypey', if anyone wants to test it with me. Hit me up by email or on the fediverse to arrange a time:
https://www.coactivate.org/projects/disintermedia/danyl-strype
- Vous devez vous identifier ou créer un compte pour écrire des commentaires