Devuan Trinity Repository Installation Instructions

From Trinity Desktop Project Wiki
Revision as of 16:39, 1 May 2022 by Blu256 (talk | contribs) (More heading adjustments)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This page provides instructions on how to install, upgrade or remove Trinity Desktop Environment on Devuan systems.

Available versions and architectures

R14.0.x series

Official TDE packages are available for the following versions of Devuan:

Version Architectures Notes
4.x - chimaera amd64, i386, ppc64el, arm64, armhf
3.x - beowulf amd64, i386, ppc64el, arm64, armhf, armel
2.x - ascii amd64, i386, ppc64el, arm64, armhf, armel
1.x - jessie amd64, i386, ppc64el, arm64, armhf, armel up to R14.0.11 only


Additionally, unofficial but well-trusted rolling-release packages are available for Devuan ascii and all later versions, i.e., including 5.x (daedalus) and ceres:

These packages are built and maintained by Slávek Banko.

v3.5.13.2

There is no support for this TDE version in Devuan.

Configuring the package manager

Importing the package signing key

The best way to import TDE's package signing key is to manually download and install the package trinity-keyring. The advantage is that this method of installation is not dependent on the availability of a key server. Another advantage is that the key is not integrated into the global apt keyring, but is installed as a separate file:

$ wget https://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-keyring.deb
$ sudo dpkg -i trinity-keyring.deb

Adding the TDE repository

Add the following lines to your /etc/apt/sources.list file.

Messagebox warning.png
Warning!
Make sure to replace <your-distribution-release-name> with your actual distribution release name (for example 'bullseye' or 'buster')
Messagebox info.png
Note
deb-src lines following are optional.

TDE R14.0.x series

deb http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x               <your-distribution-release-name> main
deb http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-builddeps-r14.0.x     <your-distribution-release-name> main
deb-src http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x           <your-distribution-release-name> main
deb-src http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-builddeps-r14.0.x <your-distribution-release-name> main

Installing Trinity

Fresh R14.0.x installation

The following steps are suggested for installing the latest R14.0.x version. If you want to upgrade from an older R14.0.x version, please follow the instructions in the next section.

Messagebox warning.png
Warning!
tde-trinity package is a comprehensive meta-package. To install only a basic environment, replace tde-trinity with tdebase-trinity in the instructions below.
$ sudo apt-get update
$ sudo apt-get install tde-trinity
Messagebox info.png
Tip
After installing the environment, it is also a good idea to install the localization packages so that you can switch the environment to your native language. For example, for Czech you would run:
$ sudo apt-get install tde-i18n-cs-trinity

Upgrading from an existing R14.0.x installation

The following steps are suggested for upgrading to the latest R14.0.x version.

$ sudo apt-get update
$ sudo aptitude full-upgrade

This will upgrade TDE to the newer version and should complete smoothly.

Removing Trinity

Messagebox info.png
Note
Please read the following instructions completely before starting the removal process.

Removing the Trinity Desktop Environment involves the following four steps:

  1. Uninstalling packages
  2. Removing the Trinity repository from the list of available package sources
  3. Cleaning up the package cache
  4. Removing left-over files from your home directory

Uninstalling packages

Using aptitude

If you have aptitude installed, you can simply run

$ sudo aptitude purge '~i~Otrinitydesktop'

Using apt-get

Using the standard apt-get utility to uninstall TDE and its dependencies involves the following three steps:

  1. Generating a list of all packages available from the Trinity repository
  2. Using that list to uninstall all installed packages originating from that repository
  3. Uninstalling all packages that were installed as dependencies of Trinity

To generate a list of all packages available from the Trinity repository, you will need to filter out just the package names from two files in /var/lib/apt/lists and write the result to a new file. The names of these files depend on three factors: The Devuan release in use, the processor type the system is running on, and whether you're using the R14.0.x series of TDE or the unofficial rolling-release packages. So, for example, when running the R14.0.x series on the i386 variant of Devuan 4.x/chimaera, the names are as follows:

  • mirror.ppa.trinitydesktop.org_trinity_deb_trinity-r14.0.x_dists_chimaera_main_binary-i386_Packages
  • mirror.ppa.trinitydesktop.org_trinity_deb_trinity-builddeps-r14.0.x_dists_chimaera_main_binary-i386_Packages

First, let's create a new empty file in /tmp, using mktemp:

$ mktemp /tmp/tde.XXXX
/tmp/tde.fB6B

Generating a list of all Trinity packages and writing it to that file now works as follows:

$ sed -n '/^Package: / s/^Package: //p' /var/lib/apt/lists/mirror.ppa.trinitydesktop.org_trinity_deb_trinity-*Packages > /tmp/tde.fB6B

Be sure to replace the output file's name with the actual name of the file mktemp created on your system.

Now that we have a list of all TDE packages, we can hand that to apt-get for uninstallation:

$ sudo apt-get remove $(cat /tmp/tde.fB6B)

Replace apt-get remove with apt-get purge to also remove the configuration files that came with those packages. And, as above, be sure to replace the output file's name with the actual name of the file mktemp created on your system.

Apt will figure out which of the packages in the list are actually installed and present them for uninstallation. It will also already notify the user of a bunch of packages that "were automatically installed and are not longer required" and suggest using apt autoremove to uninstall them. We will take care of that in the next step. So, for now, just confirm the uninstallation of the TDE packages.

If Apt asks whether to stop the tdm deamon, say yes. We're removing TDE, after all. This will land you on the TTY that TDM was running on before. Need to switch back to the one you ran apt-get from using Ctrl + F1..7.

Finally, to uninstall all remaining Trinity dependencies, you will need to run

$ sudo apt-get autoremove

In case you also want to remove the configuration files that came with these packages, append --purge to the autoremove command.

Messagebox warning.png
CAUTION
Beware that running apt-get autoremove without care can leave certain software on your system or the system as a whole in an unusable state. The command simply uninstalls all packages that were installed as dependencies of packages that are no longer installed, which might lead to the uninstallation of packages that you wanted to keep.

Be sure to read the list of packages that Apt will want to uninstall, carefully. If you want to continue to use any of the packages in that list, abort the operation, mark that package as manually installed, and then run the command again.

If you're not sure how to handle the situation, ask in the Trinity IRC channel or on the mailing list.

Removing the Trinity repository from package sources

Open /etc/apt/sources.list and either remove the Trinity repository lines or comment them by adding a hash symbol (#) at the beginning of each line. Then save the file and run sudo apt-get update.

Cleaning up the package cache

If you deactivated/removed the repo from source.list, at least run

$ sudo apt-get autoclean

This will remove all Trinity packages from the local cache.

To get rid of other packages as well, you'll have to clean out the whole package cache using

$ sudo apt-get clean

Removing left-over files from your home directory

Remove TDE files in $HOME. Usually these are the .tderc file and the .trinity and .qt directories. (The latter is still mistakenly used by some applications.)