Differences

This shows you the differences between two versions of the page.

--- wiki:repositories:archives:debian [2017/11/23 03:44]
ionic Add extras component.
+++ wiki:repositories:archives:debian [2019/09/12 17:33] (current)
ionic Fix page.
@@ Line 3: / Line 3: @@
 Alongside with the instructions on [[wiki:repositories:debian|the main Debian repository page]], we provide a repository archive for archived X2Go Debian packages for deprecated Debian GNU/Linux releases. These are provided in the state they were in after their last successful build. This repository is not updated at all, other than when a new Debian GNU/Linux release version is deprecated.
-===== Adding this Repository to your Package System =====
+===== Adding this Repository to Your Package System =====
-==== Adding the Repository GPG Keys ====
+==== Bootstrapping the Repository GPG Keys ====
-Make sure to either install the ''x2go-keyring'' file or add the GPG key as described on [[wiki:repositories:debian#adding_the_repository_gpg_keys|the main Debian repository page]].
+Make sure to either have installed the ''x2go-keyring'' package previously or add the GPG key as described on [[wiki:repositories:debian#bootstrapping_the_repository_gpg_keys|the main Debian repository page]].
 ==== Adding the Actual Repository ====
@@ Line 21: / Line 21: @@
 Please add the file ''x2go-archive.list'' to the folder ''/etc/apt/sources.list.d/''.
 This can be done by using your preferred editor.
+<note>If you have not gotten a directory named ''/etc/apt/sources.list.d/'' add the lines to ''/etc/apt/sources.list''.</note>
 <code bash>
@@ Line 33: / Line 35: @@
 # Archived X2Go Packages Repository (sources of release builds)
 deb-src http://archives.packages.x2go.org/debian squeeze extras main
+# Archived X2Go Packages Repository (Saimaa ESR builds)
+#deb http://archives.packages.x2go.org/debian squeeze extras saimaa
+# Archived X2Go Packages Repository (sources of Saimaa ESR builds)
+#deb-src http://archives.packages.x2go.org/debian squeeze extras saimaa
 # Archived X2Go Packages Repository (nightly builds)
@@ Line 40: / Line 47: @@
 </file>
+**Edit this new data** and make sure to uncomment desired components and comment non-desired components. Only one group may be active at a given time.
-**Note:** If you have not got a folder ''/etc/apt/sources.list.d/'' add the lines to ''/etc/apt/sources.list''.
+<note warning>While we do offer pseudo-codenames like ''oldstable'', ''stable'', ''testing'' and ''unstable'' for convenience, you **should not use them**. Our pseudo-codename setup is not guaranteed to be in sync with Debian's releases, so using the ''stable'' codename might mean that you will actually get packages for what Debian calls ''oldstable'' after a new Debian distro release for a considerable amount of time.</note>
+<note warning>Switching between components usually requires uninstalling all X2Go packages first! The only upgrade path that is considered somewhat safe is main (release packages) to heuler (nightly packages), but there are no guarantees regarding the stability or usefulness of nightly packages.</note>
 ==== Synchronize the Newly Added or Changed Repository's Metadata ====
@@ Line 50: / Line 60: @@
 $ apt-get update
 </code>
+<note important>If you were unable to bootstrap the repository GPG key previously, apt-get will fail to validate the signatures and discard the downloaded repository metadata.
+\\ \\
+**Not being able to verify signatures means that any content downloaded from the remote location could be injected/offered by a malicious third party and need not come from the X2Go Project. This includes repository metadata and any packages downloaded from unauthenticated repositories. Installing the x2go-keyring package from an unauthenticated repository bears the chance that this is not our package but a malicious third-party one which will not contain our public keys. This holds for all packages installed from this repository, now and later.**
+\\ \\
+You can bypass apt's internal checks **if you understand the implications** and are ready to take the risk by **once** using:
+\\ \\
+<code bash>
+$ apt-get update --allow-insecure-repositories
+</code>
+Otherwise, please try to first fetch the key again as outlined in the bootstrapping instructions.
+</note>
 After the update you should be able to access the archived X2Go packages via the apt command family. As a first action you should install our ''x2go-keyring'' package and refresh the apt cache:

X2Go - everywhere@home

User Tools

Site Tools

Differences

Page Tools