Docs: Update Ubuntu/Debian repo instructions #3050
Conversation
Note that there wont be anything populated in 'stable' until we push the next tagged release
|
|
||
| .. code-block:: sh | ||
|
|
||
| curl -fsSL https://gerbera.jfrog.io/artifactory/api/gpg/key/public | sudo apt-key add - | ||
| sudo apt-add-repository https://gerbera.jfrog.io/artifactory/debian | ||
| 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. :\
| curl -fsSL https://gerbera.jfrog.io/artifactory/api/gpg/key/public | sudo apt-key add - | ||
| sudo apt-add-repository https://gerbera.jfrog.io/artifactory/debian | ||
| 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-add-repository https://gerbera.jfrog.io/artifactory/debian | ||
| 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 |
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.
| .. 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)
| @@ -28,21 +28,26 @@ Ubuntu/Mint | |||
| .. index:: Ubuntu Linux | |||
| .. index:: Mint | |||
|
|
|||
| We maintain a `Ubuntu Repository <https://gerbera.jfrog.io/>`__. | |||
| We maintain a `Ubuntu Repository <https://pkg.gerbera.io/>`__. | |||
There was a problem hiding this comment.
I'm getting this friendly message for the page:
There was a problem hiding this comment.
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.
|
Thanks for looking at this @Martii! Will look at getting something friendlier up on when you load it directly |
Note that there wont be anything populated in 'stable' until we push the next tagged release