Skip to content
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

Closed
kaufholdr opened this issue Nov 4, 2018 · 11 comments

Comments

@kaufholdr
Copy link

Hi,

# fwupdmgr refresh
Failed to download https://s3.amazonaws.com/lvfsbucket/downloads/firmware.xml.gz.asc: Not Found

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.

@kaufholdr
Copy link
Author

kaufholdr commented Nov 4, 2018

It's Debian Stretch.

# cat /etc/issue
Debian GNU/Linux 9 \n \l

fwupdate 10-3~bpo9+1 (stretch-backports)

@hughsie
Copy link
Member

hughsie commented Nov 4, 2018

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.

@hughsie
Copy link
Member

hughsie commented Nov 4, 2018

I think Debian needs to backport c1cc0aa

@kaufholdr
Copy link
Author

You are right. Thank you for providing the solution. :-)

@kaufholdr
Copy link
Author

The Debian package bug report for this Issue:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912414

@tuxayo
Copy link

tuxayo commented Mar 4, 2019

Thanks for report here and on the Debian tracker. For someone having the same issue:

It's possible to change the config file "/etc/fwupd.conf" and replace:
DownloadURI=https://s3.amazonaws.com/lvfsbucket/downloads/firmware.xml.gz
with:
DownloadURI=https://cdn.fwupd.org/downloads/firmware.xml.gz
as a workaround.

@tuxayo
Copy link

tuxayo commented Mar 4, 2019

Aditional info: The next Debian (9/Buster) will have version 1.2.4 which isn't affected.

@bestouff
Copy link

FWIW, just changing the configuration file as described still doesn't work:

failed to update metadata: Failed to parse XML: Mismatched XML

@hughsie
Copy link
Member

hughsie commented Jul 29, 2019

Failed to parse XML: Mismatched XML

You're using a very old and unsupported fwupd version.

@bestouff
Copy link

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.

@superm1
Copy link
Member

superm1 commented Jul 29, 2019

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:
a1e6e7f

But I would highly encourage anyone affected by this to move to a newer fwupd release.

@fwupd fwupd locked as resolved and limited conversation to collaborators Jul 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

5 participants