Docs: Update Ubuntu/Debian repo instructions #3050
+32
−6
Docs: Update Ubuntu/Debian repo instructions
Note that there wont be anything populated in 'stable' until we push the next tagged release
- Loading branch information
commit f39a6c0f88aacee5c33f84dcce96a11df1215c15
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -28,21 +28,26 @@ Ubuntu/Mint | |
| .. index:: Ubuntu Linux | ||
| .. index:: Mint | ||
|
|
||
| We maintain a `Ubuntu Repository <https://pkg.gerbera.io/>`__. | ||
|
|
||
| To install the latest tagged release (>=2.1.0): | ||
|
|
||
| .. code-block:: sh | ||
|
|
||
| wget -O - https://pkg.gerbera.io/public.asc 2>/dev/null | gpg --dearmor - | sudo tee /usr/share/keyrings/gerbera-keyring.gpg >/dev/null | ||
|
There was a problem hiding this comment. Don't know if this is "the usual thing" but still getting stdout on the binary gpg key here... it does however create it correctly in the target file. Logging might be a little messy if this is the norm. Misc Note: We use a variation on it... doesn't matter on curl or wget... but this doesn't generate stdout here: curl -fsSL $KEY | sudo gpg --batch --yes --dearmor -o $KEYRINGEDIT Retested this today (the next day) and it's not dumping the key to stdout anymore... weird... anywho... please ignore if you wish. :\ |
||
| echo "deb [signed-by=/usr/share/keyrings/gerbera-keyring.gpg] https://pkg.gerbera.io/debian/ $(lsb_release -c --short) main" | sudo tee /etc/apt/sources.list.d/gerbera.list >/dev/null | ||
|
|
||
| sudo apt-get update | ||
|
There was a problem hiding this comment. ... as you mentioned the release isn't there yet: Reading package lists... Done
E: The repository 'https://pkg.gerbera.io/debian jammy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details. |
||
| sudo apt-get install gerbera | ||
|
|
||
| Or for the latest code install git builds: | ||
|
|
||
| .. code-block:: sh | ||
|
|
||
| wget -O - https://pkg.gerbera.io/public.asc 2>/dev/null | gpg --dearmor - | sudo tee /usr/share/keyrings/gerbera-keyring.gpg >/dev/null | ||
| echo "deb [signed-by=/usr/share/keyrings/gerbera-keyring.gpg] https://pkg.gerbera.io/debian-git/ $(lsb_release -c --short) main" | sudo tee /etc/apt/sources.list.d/gerbera.list >/dev/null | ||
| sudo apt-get update | ||
| sudo apt-get install gerbera | ||
|
|
||
|
|
||
| Or Stephen Czetty maintains a `Ubuntu PPA <https://launchpad.net/~stephenczetty/+archive/ubuntu/gerbera-updates>`__. | ||
|
|
||
|
|
@@ -129,6 +134,27 @@ Gerbera is included in Buster_ and Sid_. | |
|
|
||
| Due to the stable nature of Debian, these packages are likely to be some versions behind the current Gerbera release. | ||
|
|
||
| We maintain a `Debian Repository <https://pkg.gerbera.io/>`__. | ||
|
|
||
| To install the latest tagged release (>=2.1.0): | ||
|
|
||
| .. code-block:: sh | ||
|
|
||
| wget -O - https://pkg.gerbera.io/public.asc 2>/dev/null | gpg --dearmor - | sudo tee /usr/share/keyrings/gerbera-keyring.gpg >/dev/null | ||
| echo "deb [signed-by=/usr/share/keyrings/gerbera-keyring.gpg] https://pkg.gerbera.io/debian/ $(lsb_release -c --short) main" | sudo tee /etc/apt/sources.list.d/gerbera.list >/dev/null | ||
| sudo apt-get update | ||
| sudo apt-get install gerbera | ||
|
|
||
| Or for the latest code install git builds: | ||
|
|
||
| .. code-block:: sh | ||
|
|
||
| wget -O - https://pkg.gerbera.io/public.asc 2>/dev/null | gpg --dearmor - | sudo tee /usr/share/keyrings/gerbera-keyring.gpg >/dev/null | ||
| echo "deb [signed-by=/usr/share/keyrings/gerbera-keyring.gpg] https://pkg.gerbera.io/debian-git/ $(lsb_release -c --short) main" | sudo tee /etc/apt/sources.list.d/gerbera.list >/dev/null | ||
|
There was a problem hiding this comment. See successful installation/start screenshot at #2988 (comment) |
||
| sudo apt-get update | ||
| sudo apt-get install gerbera | ||
|
|
||
|
|
||
| `Deb-Multimedia.org <https://www.deb-multimedia.org/>`__ also provide builds for Buster_ and Sid_. | ||
|
|
||
| .. _Buster: http://www.deb-multimedia.org/dists/buster/main/binary-amd64/package/gerbera | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm getting this friendly message for the page:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes a landing page there would be nice to have. Some sources don't though and makes finding if a release is available by directory read traversal a little harder to determine if a certain distro is supported yet.