July 3, 20179 yr comment_13909 The repository still doesn't have a release file (since 2016) and the static version will never connect. Could we please just get a deb file to download ASAP so I can use my TV? I really don't want to go through bypassing security just to install this app. I will, but I shouldn't have to. Report
July 3, 20179 yr Author comment_13910 Nevermind. Server was not working a while ago, it's up now. For anyone else with this problem (virtually everyone not using RPM) you can find the debs here -> http://apt.flirc.tv/arch/x64/binary/ Report
July 3, 20179 yr comment_13911 I'm sorry, although fairly easy, this is probably a good 2-3 days of effort. I'll get to this soon. I'm working on a major release. sorry for the trouble. Report
July 9, 20179 yr comment_13932 I added the apt repo per the Debian instructions at https://flirc.tv/ubuntu-software-installation-guide to my Ubuntu 16.04 system. Trying to run 'apt update' gives me the following error: Err:10 http://apt.flirc.tv/arch/x64 binary/ Release 404 Not Found E: The repository 'http://apt.flirc.tv/arch/x64 binary/ 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. I don't mean to be an ass but it shouldn't be 2-3 days of effort to properly set up an apt repo. https://blog.packagecloud.io/eng/2015/08/04/apt-repository-internals/ Report
July 10, 20179 yr comment_13933 Have to ask what a deb file is. Edited July 10, 20179 yr by msnow Report
July 11, 20179 yr comment_13934 21 hours ago, msnow said: Have to ask what a deb file is. If you have to ask, you more than likely don't need it. It's just the extension for packages used by Debian, and it's various forks. ( Ubuntu, Linux Mint, etc) Report
July 16, 20179 yr comment_13979 On 7/2/2017 at 11:24 PM, jason said: I'm sorry, although fairly easy, this is probably a good 2-3 days of effort. I'll get to this soon. I'm working on a major release. sorry for the trouble. You've been working on the major release for over a year? I get the same error with the apt repo: W: The repository 'http://apt.flirc.tv/arch/x64 binary/ Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. The distribution-independent binary also did not work for me: matt@host:/tmp/release/linux$ md5sum ~/Downloads/Linux_Release.zip 652ca37b1a68cd031689835a4a566b2a /home/matt/Downloads/Linux_Release.zip matt@host:/tmp$ unzip ~/Downloads/Linux_Release.zip Archive: /home/matt/Downloads/Linux_Release.zip creating: release/ inflating: release/51-flirc.rules inflating: release/index.html creating: release/linux/ inflating: release/linux/Flirc inflating: release/linux/flirc_util inflating: release/markdown.css inflating: release/release_notes.md creating: release/rpi/ inflating: release/rpi/flirc_util matt@host:/tmp$ cd release/linux/ matt@host:/tmp/release/linux$ ls Flirc flirc_util matt@host:/tmp/release/linux$ md5sum ./Flirc 67d51752dea950f8e7e0bd90c48fa88e ./Flirc matt@host:/tmp/release/linux$ ./Flirc -bash: ./Flirc: No such file or directory I'd argue it's bordering on false advertising when you say "Linux support"... Yet the Debian/Ubuntu repos don't work, and neither does the supposedly failsafe static build. Here's how I got this working, for anyone else who is similarly frustrated. I'm running Ubuntu LTS 16.04.2: $ cat /etc/os-release NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial $ cat /etc/debian_version stretch/sid I downloaded the deb file explicitly, specifically http://apt.flirc.tv/arch/x64/binary/flirc_2.5.1-1_amd64.deb There are a number of dependencies required. So I installed them all manually: $ sudo apt-get install libhidapi-hidraw0 libqt4-network libqt4-svg libqt4-xml libqtcore4 libqtgui4 libqtdbus4 libmng2 libqt4-declarative qtcore4-l10n libqt4-script libqt4-sql libqt4-xmlpatterns After the dependencies were installed, I could install the flirc deb directly: $ sudo dpkg -i flirc_2.5.1-1_amd64.deb I hope this info helps others. But I also hope it doesn't justify further delaying the fix for the repos. Edited July 16, 20179 yr by matt_garman fix typo Report
July 16, 20179 yr comment_13981 58 minutes ago, matt_garman said: You've been working on the major release for over a year? I get the same error with the apt repo: W: The repository 'http://apt.flirc.tv/arch/x64 binary/ Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. The distribution-independent binary also did not work for me: matt@host:/tmp/release/linux$ md5sum ~/Downloads/Linux_Release.zip 652ca37b1a68cd031689835a4a566b2a /home/matt/Downloads/Linux_Release.zip matt@host:/tmp$ unzip ~/Downloads/Linux_Release.zip Archive: /home/matt/Downloads/Linux_Release.zip creating: release/ inflating: release/51-flirc.rules inflating: release/index.html creating: release/linux/ inflating: release/linux/Flirc inflating: release/linux/flirc_util inflating: release/markdown.css inflating: release/release_notes.md creating: release/rpi/ inflating: release/rpi/flirc_util matt@host:/tmp$ cd release/linux/ matt@host:/tmp/release/linux$ ls Flirc flirc_util matt@host:/tmp/release/linux$ md5sum ./Flirc 67d51752dea950f8e7e0bd90c48fa88e ./Flirc matt@host:/tmp/release/linux$ ./Flirc -bash: ./Flirc: No such file or directory I'd argue it's bordering on false advertising when you say "Linux support"... Yet the Debian/Ubuntu repos don't work, and neither does the supposedly failsafe static build. Here's how I got this working, for anyone else who is similarly frustrated. I'm running Ubuntu LTS 16.04.2: $ cat /etc/os-release NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial $ cat /etc/debian_version stretch/sid I downloaded the deb file explicitly, specifically http://apt.flirc.tv/arch/x64/binary/flirc_2.5.1-1_amd64.deb There are a number of dependencies required. So I installed them all manually: $ sudo apt-get install libhidapi-hidraw0 libqt4-network libqt4-svg libqt4-xml libqtcore4 libqtgui4 libqtdbus4 libmng2 libqt4-declarative qtcore4-l10n libqt4-script libqt4-sql libqt4-xmlpatterns After the dependencies were installed, I could install the flirc deb directly: $ sudo dpkg -i flirc_2.5.1-1_amd64.deb I hope this info helps others. But I also hope it doesn't justify further delaying the fix for the repos. Sorry, I don't see this, and there is no reason to be so mean. No team here, just one person and I don't ever have 3 consecutive days. Filed tax extensions, haven't even filed yet. I work 7 days a week. (trusty_amd64)root@mint:/home/kotzin# sudo apt-get upgrade flirc Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: flirc 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 8302 kB of archives. After this operation, 42.0 kB of additional disk space will be used. Do you want to continue? [Y/n] WARNING: The following packages cannot be authenticated! flirc Install these packages without verification? [y/N] Y Get:1 http://apt.flirc.tv/arch/x64/ binary/ flirc 2.5.1-1 [8302 kB] Fetched 8302 kB in 2s (2780 kB/s) (Reading database ... 48402 files and directories currently installed.) Preparing to unpack .../flirc_2.5.1-1_amd64.deb ... Unpacking flirc (2.5.1-1) over (2.3.6-1) ... Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for mime-support (3.54ubuntu1) ... Setting up flirc (2.5.1-1) ... Tried several times, don't see the issue. This is in my source.list: deb http://apt.flirc.tv/arch/x64 binary/ Report
July 16, 20179 yr comment_13985 2 hours ago, jason said: Sorry, I don't see this, and there is no reason to be so mean. No team here, just one person and I don't ever have 3 consecutive days. Filed tax extensions, haven't even filed yet. I work 7 days a week. I don't think that was mean---I did show steps for others to use as a workaround until the repos are fixed. Clearly it's been an issue for some folks for over a year. For what it's worth, I have a close friend who had similar issues with the RPM packages. He told me he had a dialog with you via direct email, where he offered to help re-package your RPMs and fix your repos. You agreed to the help; he said, "OK, what next?" and you never replied. Point is, you did have an opportunity to have a team. I appreciate that you are busy. But my opinion remains: I am completely sympathetic if you don't have time to make the Linux experience as polished and turn-key as on Windows, but you owe it to your customers to advertise accordingly. As a 20-year Linux user I am used to this: with much hardware, Windows support is a given, and Linux support varies from "not at all" to "best-effort" or "community support only". But the way FLIRC is currently advertised, it comes across as Linux support being the same as Windows: you have both deb and rpm repos, and a failsafe distro-independent/statically-linked Linux failsafe program. According to my friend, the RPMs are broken; clearly the apt repos are broken for at least some of us; and the failsafe is not working for me either (see above). Anyway, in your example above you are doing an upgrade, which implies you already have a working flirc package on your system. Can you apt-get remove flirc, then comment out the line in your sources.list file, and then run "apt-get clean"? The latter will clean out your apt/dpkg cache. At this point I believe your system should be in a state similar to what mine is: effectively no knowledge of the flirc software. Now un-comment the line in sources.list, and just run "apt-get update". This command will just refresh the package index/cache. I suspect this should fail the same as it did for me and others in this thread. On the other hand, if it works, then I suspect it is a nuanced difference between various distributions' apt repository requirements. Can you tell me exactly what distribution and version you are using? I am guessing Linux Mint... I'm going to install 18.2 XFCE 64bit in a virtual machine and see if the repo works for me. Edit: I just did a fresh install of Linux Mint 18.2 XFCE 64bit. I added "deb http://apt.flirc.tv/arch/x64 binary/" to my /etc/apt/sources.list file. When I ran "apt-get update", I got the same error I posted above. I now have more confidence that if you do as I suggested above (remove flirc, remove flirc repo, clean your apt cache, then re-add the repo), you'll be able to reproduce this. Edited July 16, 20179 yr by matt_garman update with results of mint test Report
July 18, 20179 yr comment_14001 kotzin@mint default ~ ⚡ sudo apt-get remove --purge flirc Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: flirc* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 12.5 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 48402 files and directories currently installed.) Removing flirc (2.5.1-1) ... Purging configuration files for flirc (2.5.1-1) ... Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for mime-support (3.54ubuntu1) ... kotzin@mint default ~ ⚡ sudo apt-get clean kotzin@mint default ~ ⚡ sudo apt-get update Ign http://apt.flirc.tv binary/ InRelease Ign http://apt.flirc.tv binary/ Release.gpg Ign http://apt.flirc.tv binary/ Release Ign http://apt.flirc.tv binary/ Packages/DiffIndex Ign http://us.archive.ubuntu.com trusty InRelease Hit http://us.archive.ubuntu.com trusty-updates InRelease Ign http://old-releases.ubuntu.com raring InRelease Hit http://apt.flirc.tv binary/ Packages Ign http://apt.flirc.tv binary/ Translation-en Hit http://us.archive.ubuntu.com trusty Release.gpg Hit http://us.archive.ubuntu.com trusty-updates/multiverse Sources Hit http://old-releases.ubuntu.com raring Release.gpg Ign http://mirror.aarnet.edu.au trusty InRelease Hit http://us.archive.ubuntu.com trusty-updates/multiverse amd64 Packages Hit http://us.archive.ubuntu.com trusty-updates/multiverse Translation-en Hit http://old-releases.ubuntu.com raring Release Hit http://us.archive.ubuntu.com trusty Release Hit http://mirror.aarnet.edu.au trusty Release.gpg Hit http://us.archive.ubuntu.com trusty/multiverse Sources Hit http://mirror.aarnet.edu.au trusty Release Hit http://us.archive.ubuntu.com trusty/universe Sources Hit http://old-releases.ubuntu.com raring/main amd64 Packages Hit http://us.archive.ubuntu.com trusty/main amd64 Packages Hit http://old-releases.ubuntu.com raring/restricted amd64 Packages Hit http://us.archive.ubuntu.com trusty/multiverse amd64 Packages Hit http://mirror.aarnet.edu.au trusty/main amd64 Packages Hit http://us.archive.ubuntu.com trusty/universe amd64 Packages Hit http://mirror.aarnet.edu.au trusty/main Translation-en Hit http://us.archive.ubuntu.com trusty/main Translation-en Hit http://old-releases.ubuntu.com raring/universe amd64 Packages Hit http://us.archive.ubuntu.com trusty/multiverse Translation-en Hit http://old-releases.ubuntu.com raring/multiverse amd64 Packages Hit http://us.archive.ubuntu.com trusty/universe Translation-en Hit http://old-releases.ubuntu.com raring/main Translation-en Hit http://old-releases.ubuntu.com raring/multiverse Translation-en Hit http://old-releases.ubuntu.com raring/restricted Translation-en Hit http://old-releases.ubuntu.com raring/universe Translation-en Reading package lists... Done kotzin@mint default ~ ⚡ sudo apt-get upgrade flirc Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: flirc 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 8307 kB of archives. After this operation, 12.5 MB of additional disk space will be used. Do you want to continue? [Y/n] y WARNING: The following packages cannot be authenticated! flirc Install these packages without verification? [y/N] y Get:1 http://apt.flirc.tv/arch/x64/ binary/ flirc 2.5.2-1 [8307 kB] Fetched 8307 kB in 2s (3005 kB/s) Selecting previously unselected package flirc. (Reading database ... 48392 files and directories currently installed.) Preparing to unpack .../flirc_2.5.2-1_amd64.deb ... Unpacking flirc (2.5.2-1) ... Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for mime-support (3.54ubuntu1) ... Setting up flirc (2.5.2-1) ... kotzin@mint default ~ Report
July 18, 20179 yr comment_14002 What distribution and version are you running? Can you post the contents of /etc/os-release and /etc/debian_version? Can you also post the output of "apt-key list"? Thanks! Report
July 18, 20179 yr comment_14003 http://cl.flirc.io/lbOz http://cl.flirc.io/lbXw It's a chrooted environment in my debian distro. Yeah strange that it's not really complaining that hard about the security ID. I do sign the package. You want to try it again, I issued an update yesterday. Perhaps the last release wasn't good? Report
July 23, 20179 yr comment_14058 @jason - so it looks like the apt repo does work with ubuntu 14.04. But it does not work with ubuntu 16.04, nor mint 18.2. So my best guess it that debian/ubuntu introduced some kind of stricter checking on repos. Can you try again with a newer ubuntu, or upgrade your install? 14.04 is fairly old at this point. Report
August 4, 20179 yr comment_14080 Okay, this was a lot of work. https://flirc.tv/ubuntu-software-installation-guide No immediate plans to do a 32 bit version right now,. Verified the issue, and verified this should work. Report
August 5, 20179 yr Author comment_14082 Almost there. Missing a dependency - libhidapi-hidraw. On a fresh install, I get this on startup. flirc_util: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory After installing libhidapi-hidraw the Flirc gui does open and appears to work, but with a lot of shell noise like: Can't load 'test.ini' [D] lib/libflirc/flirc_driver.c fl_major_version(391): something bad happened [D] lib/libflirc/flirc_driver.c fl_minor_version(381): something bad happened [D] lib/libflirc/flirc_driver.c fl_patch_version(401): something bad happened [D] lib/libflirc/flirc_driver.c fl_major_version(391): something bad happened etc, etc, etc. Report
August 5, 20179 yr comment_14083 what version are you running? Ignore the noise, it work okay after the library? should have installed that as a dependency... Report
August 5, 20179 yr comment_14084 12 minutes ago, jason said: what version are you running? Ignore the noise, it work okay after the library? should have installed that as a dependency... okay, I think I fixed it. Version didn't change, so you'd have to do a remove and install again. Report
August 12, 20179 yr comment_14133 I tested the apt repos + install on my VMs, Mint 18.2 and Ubuntu 16.04, and they worked! Thanks Jason! Report
March 18, 20188 yr comment_15025 Just now, grkblood13 said: Running Ubuntu 17.10 64bit. Install script is not working. can you clarify, or post a log? Report
March 18, 20188 yr comment_15026 root@xubuntu-desktop:/tmp# curl -s https://packagecloud.io/install/repositories/Flirc/repo/script.deb.sh | bash Detected operating system as Ubuntu/artful. Checking for curl... Detected curl... Checking for gpg... Detected gpg... Running apt-get update... done. 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. root@xubuntu-desktop:/tmp# apt install flirc Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package flirc root@xubuntu-desktop:/tmp# Report
March 18, 20188 yr comment_15027 root@xubuntu-desktop:/tmp# wget https://packagecloud.io/Flirc/repo/packages/ubuntu/xenial/flirc_3.9.12_amd64.deb --2018-03-18 19:39:35-- https://packagecloud.io/Flirc/repo/packages/ubuntu/xenial/flirc_3.9.12_amd64.deb Resolving packagecloud.io (packagecloud.io)... 50.97.198.58, 2607:f0d0:2101:270::2 Connecting to packagecloud.io (packagecloud.io)|50.97.198.58|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘flirc_3.9.12_amd64.deb’ flirc_3.9.12_amd64.deb [ <=> ] 16.98K --.-KB/s in 0.001s 2018-03-18 19:39:36 (17.2 MB/s) - ‘flirc_3.9.12_amd64.deb’ saved [17388] root@xubuntu-desktop:/tmp# dpkg -i flirc_3.9.12_amd64.deb dpkg-deb: error: 'flirc_3.9.12_amd64.deb' is not a debian format archive dpkg: error processing archive flirc_3.9.12_amd64.deb (--install): subprocess dpkg-deb --control returned error exit status 2 Errors were encountered while processing: flirc_3.9.12_amd64.deb root@xubuntu-desktop:/tmp# Report
March 18, 20188 yr comment_15028 FYI I tried a manual install of xenial (ubuntu 16) because there is no version for 17. Report
March 18, 20188 yr comment_15029 Just now, grkblood13 said: FYI I tried a manual install of xenial (ubuntu 16) because there is no version for 17. okay, let me look into this. Report
March 19, 20188 yr comment_15030 Also, I can't install the generic version in the meantime either. I'm getting 404ed. :/ root@xubuntu-desktop:/tmp# wget http://apt.flirc.tv/arch/x64/binary/flirc.latest.x86_64.tar.gz --2018-03-18 20:37:08-- http://apt.flirc.tv/arch/x64/binary/flirc.latest.x86_64.tar.gz Resolving apt.flirc.tv (apt.flirc.tv)... 45.56.95.166 Connecting to apt.flirc.tv (apt.flirc.tv)|45.56.95.166|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2018-03-18 20:37:08 ERROR 404: Not Found. Report
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.