Jump to content
Flirc Forums

orion

Members
  • Content count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About orion

  • Rank
    Curious Flirc-er
  1. Thanks very much @yawor that worked!
  2. 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
×