Hi there,

I have a HTPC running on Debian Stretch - current stable version.

The installer script, which I ran per the packagecloud instructions finished correctly:

curl -s https://packagecloud.io/install/repositories/Flirc/repo/script.deb.sh | sudo bash 

.......................................

user@system:~/flirc# curl -s https://packagecloud.io/install/repositories/Flirc/repo/script.deb.sh | sudo bash
Detected operating system as debian/stretch.
Checking for curl...
Detected curl...
Checking for gpg...
Detected gpg...
Running apt-get update... done.
Installing debian-archive-keyring which is needed for installing
apt-transport-https on many Debian systems.
Installing apt-transport-https... done.
Installing /etc/apt/sources.list.d/Flirc_repo.list...done.
Importing packagecloud gpg key... done.
Running apt-get update... done.

The repository is setup! You can now install packages.
..................................................

But that's not true. Because apt-get update returns this at the end:

Ign:9 https://packagecloud.io/Flirc/repo/debian stretch InRelease
Err:11 https://packagecloud.io/Flirc/repo/debian stretch Release
  404  Not Found
Reading package lists... Done
E: The repository 'https://packagecloud.io/Flirc/repo/debian stretch 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.
 

And apt install flirc returns: E: Unable to locate package flirc

Looking at the packagecloud repo in a browser, I can only see Ubuntu packages and none of the .debs will install with dpkg. Is bare Debian actually supported by FLIRC? How can I install?
 

 

It seems there's some misconfiguration of the repo. I think you can safely replace the repos manually to use ubuntu/trusty instead of debian/stretch.

I can confirm that with the following line in sources.list:

deb https://packagecloud.io/Flirc/repo/ubuntu/ trusty main
 

Apt correctly brings this in and offers to install flirc and one dependency, libqt5xmlpatterns5. This looks like it works.

I have not installed and verified, as I've been burned by apt tantrums and broken packages before when using PPA or other not-quite-debian repos. Don't intend to go down this road myself, but it looks promising if anyone else has this problem and can't work around.

Me,  I've configured Flirc on my windows box instead, and once plugged into the debian HTPC it's all peachy.

Hi,

I am running Debian testing (Debian Buster) and cannot install Flirc.

As Rounan, I have successfully run this command:

curl -s https://packagecloud.io/install/repositories/Flirc/repo/script.deb.sh | sudo bash
 

However when i run  sudo apt-get update I get the following error:

Err:16 https://packagecloud.io/Flirc/repo/debian buster Release
  404  Not Found [IP: 50.97.198.58 443]
Reading package lists... Done
E: The repository 'https://packagecloud.io/Flirc/repo/debian buster 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.
 

Details from the apt-secure man page:

REPOSITORY CONFIGURATION
       If you want to provide archive signatures in an archive under your maintenance you have to:

       ·   Create a toplevel Release file, if it does not exist already. You can do this by running apt-ftparchive release (provided in
           apt-utils).

       ·   Sign it. You can do this by running gpg --clearsign -o InRelease Release and gpg -abs -o Release.gpg Release.

       ·   Publish the key fingerprint, so that your users will know what key they need to import in order to authenticate the files in the
           archive. It is best to ship your key in its own keyring package like Debian does with debian-archive-keyring to be able to
           distribute updates and key transitions automatically later.

       ·   Provide instructions on how to add your archive and key. If your users can't acquire your key securely the chain of trust described
           above is broken. How you can help users add your key depends on your archive and target audience ranging from having your keyring
           package included in another archive users already have configured (like the default repositories of their distribution) to
           leveraging the web of trust.

       Whenever the contents of the archive change (new packages are added or removed) the archive maintainer has to follow the first two
       steps outlined above.

Could you please produce a release file for Buster? Or direct me on what I need to do to remedy this issue?

Many thanks

Edited March 28, 20188 yr by orion

@orion just edit the /etc/apt/sources.list and replace debian with ubuntu and buster with with xenial in the Flirc repo address. Then run apt-get update and apt-get install flirc again.

Thanks very much @yawor that worked!