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.

Share this post

Link to post

Share on other sites

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.

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.

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.

Share this post

Link to post

Share on other sites

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.