similar to: Cannot update xiph repository

Hi Damian The main reason for this issue is the expired Multimedia signing key expired for openSUSE OBS Multimedia – aka xiph repository. The documentation has not been updated as mentioned in Step 2 : https://wiki.xiph.org/index.php?title=Icecast_Server/Installing_latest_version_(official_Xiph_repositories)

Thanks Marvin and Thomas, After Marvin updated the key, I tried again (without having to use Thomas’ suggested workaround). All is working properly again. Thanks for the help guys 🙏 Regards Damian > On 24 Feb 2020, at 01:23, Marvin Scholz <epirat07 at gmail.com> wrote: > > Hello, > >>> On 23 Feb 2020, at 14:34, Thomas Zumbrunnen wrote: >> Hi Damian

How do I compile Icecast 2.4.4 with openssl support?

On Fri, Nov 02, 2018 at 11:46:52AM +0000, Thomas B. Rücker wrote: > Usually that question comes from Ubuntu or Debian users. > In which case we recommend: > https://wiki.xiph.org/Icecast_Server/Installing_latest_version_(official_Xiph_repositories) > Those official Xiph.org packages are built against openSSL. Could someone kick the build process, please? 2.4.2-2 is the latest

Moro, On 5/14/19 4:36 PM, Oskar Vilkevuori wrote: > Hi there, > > Any idea? Please use these packages  https://wiki.xiph.org/Icecast_Server/Installing_latest_version_(official_Xiph_repositories) or rebuild the Debian package but with the openssl -dev package present on your machine. > > I found > from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744815 that >

El vie, 02-11-2018 a las 11:46 +0000, Thomas B. Rücker escribió: > Hi, > > On 11/01/2018 07:29 PM, Googe wrote: > > How do I compile Icecast 2.4.4 with openssl support? > > Usually that question comes from Ubuntu or Debian users. > In which case we recommend: > https://wiki.xiph.org/Icecast_Server/Installing_latest_version_(offic > ial_Xiph_repositories) > Those

Hi all, I have been struggling to setup icecast with ssl on port 443. I am running Debian Wheezy and installed icecast by downloading the source and compiling. This went all ok, including ssl support. When running ssl on a port >1024 and not chrooting ssl works fine, so the certificate is ok. But when enabling chroot everything works but ssl. Any ideas ? TIA! Paul This is (part of) my

Hello Goran, You must install Cerbot (for Let's Encrypt certificate) and then generate certificates (Icecast is not able to use the different Let’s Encrypt certificates generated by default, it is necessary to combine them). Then install the following dependencies : apt install git gcc build-essential automake autoconf libtool checkinstall and apt install libcurl4-openssl-dev libxslt1-dev

Hi, On 08/12/2018 02:04 AM, subscription at nextdial.com.br wrote: > Hello, >   > At a test VPS running Ubuntu 16.04 LTS I did this: > > 1. sudo apt-get update > 2. sudo add-apt-repository ppa:certbot/certbot > 3. sudo apt-get install certbot > You'll need an additional step at this point, see below. > 1. sudo apt-get install icecast2 > 2. sudo certbot

Hi All, I am building a Docker image that uses Ubuntu 22.04 and am having issues installing the latest version of R (R 4.4.1). The current R version is 4.1.2: :/# apt-cache policy r-base-core r-base-core: Installed: 4.1.2-1ubuntu2 Candidate: 4.1.2-1ubuntu2 Version table: *** 4.1.2-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100

I'm running Debian/Jessie on a server which is used as an AD DC. I'm getting errors like this: Hit http://ftp.ca.debian.org jessie InRelease Hit http://ftp.ca.debian.org jessie/main Sources Hit http://ftp.ca.debian.org jessie/main amd64 Packages Hit http://ftp.ca.debian.org jessie/main Translation-en Err http://ftp3.nrc.ca jessie InRelease Err http://ftp3.nrc.ca jessie-updates InRelease

Thanks! ?"jammy" made it work. ? For some reason, ?lsb_release -cs is returning "victoria" rather than "jammy", and $> sudo apt update Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Ign:2 http://packages.linuxmint.com victoria InRelease Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] Hit:4 http://packages.linuxmint.com victoria

Still something wrong. I've uncommented the deb-src lines in sources.list as you suggested (and I thought it couldn't hurt to try --allow-unauthenticated as well) and: root at limpet:/etc/apt# apt-get update --allow-unauthenticated Hit:1 http://nz.archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://repo.steampowered.com/steam precise InRelease Hit:3

he there is the entry of the pup key named in wiki still walid? becasue there stand [expires: 2020-01-30] maybe it should be renwed? https://wiki.xiph.org/index.php?title=Icecast_Server/Installing_latest_version_(official_Xiph_repositories)&mobileaction=toggle_view_desktop and the other question is can i use the ubuntu 18.04 things for 20.04?

Dear Robin and Tomas, By changing the CC, I'm hereby trying to move this to R-SIG-Debian (Ubuntu a flavor of Debian) where it belongs ... Martin >>>>> robin hankin >>>>> on Fri, 1 Mar 2019 21:43:07 +1300 writes: > Still something wrong. I've uncommented the deb-src lines in > sources.list as you suggested (and I thought it

I just upgraded from Linux Mint 20 to 21 and am no longer able to add the CRAN Ubuntu repository to my list of repositories. ?I am getting: $> sudo /usr/bin/add-apt-repository "deb https://cloud.r-project.org/bin/linux/ubuntu $(lsb_release -cs)-cran40/" $> sudo apt update Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy

Hi! Samba server set up for domain rufus.ada.de a proxy is reachable in proxy.ada.de. resolv.conf is configured to be: domain rufus.ada.de. search rufus.ada.de. miri.ada.de. ada.de. nameserver 127.0.0.1 Internal servers are handled (by an external DNS, our internal samba DNS forwards to): # host proxy.ada.de proxy.ada.de has address 10.169.16.3 For deb.debian.org: # host deb.debian.org

Hello, When doing "apt-get update" on Debian Stretch, I am experimenting the following error: # apt-get update Ign:1 http://ftp.fr.debian.org/debian stretch InRelease Ign:2 http://apt.van-belle.nl/debian stretch-backports InRelease Hit:3 http://security.debian.org/debian-security stretch/updates InRelease Hit:4 http://ftp.fr.debian.org/debian stretch-updates InRelease Hit:5

Thanks for the reply Mr. Eddelbuettel. However I somehow couldn't manage to solve the problem completely. So I cleaned the sources.list file so taht the output is this: sudo apt-get update Hit:1 http://tr.archive.ubuntu.com/ubuntu xenial InRelease Hit:2 http://tr.archive.ubuntu.com/ubuntu xenial-updates InRelease???????????????????????????????????????????????????????????????????? Hit:3

I ran into a problem installing R 3.5 on Ubuntu Bionic Beaver. In file /etc/apt/sources.list I added the repository entry "deb https://cloud.r-project.org/bin/linux/ubuntu bionic-cran35/". But "apt-get update" now produces an error message: W: Konflikt bei Distribution: https://cloud.r-project.org/bin/linux/ubuntu bionic-cran35/ InRelease (bionic-cran35/ erwartet, aber