-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to download https://s3.amazonaws.com/lvfsbucket/downloads/firmware.xml.gz.asc: Not Found #831
Comments
It's Debian Stretch.
fwupdate 10-3~bpo9+1 (stretch-backports) |
0.7.4 is super old, what distro is this. We stopped mirroring to S3 a few weeks ago, as we've since moved CDNs. |
I think Debian needs to backport c1cc0aa |
You are right. Thank you for providing the solution. :-) |
The Debian package bug report for this Issue: |
Thanks for report here and on the Debian tracker. For someone having the same issue:
|
Aditional info: The next Debian (9/Buster) will have version 1.2.4 which isn't affected. |
FWIW, just changing the configuration file as described still doesn't work:
|
You're using a very old and unsupported fwupd version. |
I know that. But this issue is the first result after a google of the problem, so I'm leaving this comment so that people with servers stuck on Debian stretch know this solution isn't working. |
The cause reported above by @bestouff here is that LVFS grew quite a bit since the ancient fwupd release. The same thing happened in Ubuntu. You can reference this bug here: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813 A workaround is to backport this fix if it's impossible to move to a newer fwupd release: But I would highly encourage anyone affected by this to move to a newer fwupd release. |
Hi,
Seems to be related to #391. Will this be fixed in https://github.com/hughsie/lvfs-website/issues/138 ?
Is it possible to provide a workaround for now?
Please let me know if you need further information from my side.
fwupd version 0.7.4-2.
The text was updated successfully, but these errors were encountered: