qubes-dom0-update results in HTTP Error 404

55 views
Skip to first unread message

Chris Grimmett

unread,
Jun 27, 2016, 7:28:26 PM6/27/16
to qubes...@googlegroups.com
I'm trying to install a Windows AppVM using this guide-- https://www.qubes-os.org/doc/windows-appvms

The problem is I cannot run this command-- `sudo qubes-dom0-update qubes-windows-tools`

In the output, there are four 404 errors, all with the same bad URL--

http://yum.qubes-os.org/r3.1/current/dom0/fc20/repodata/45f4890c7aa2937f1bc04bf43bb997ac8b86221a463a0348cf8bcb8c3066f2e7-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.

I visited that link in my web browser, and it really is a 404. It looks like Qubes is not using an up-to-date mirror URL? Is there a way I can get Qubes to find and use an up-to-date mirror?

Marek Marczykowski-Górecki

unread,
Jun 27, 2016, 7:34:54 PM6/27/16
to Chris Grimmett, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Probably yum local cache is outdated. You can force refresh with --clean
option.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXcbgVAAoJENuP0xzK19cs9a4H/iO/m2wXkD8zT0nvXWuuse5K
BQhQfEwRR5xhtyo1/mhn3NPy9aoiUwuJNhGiAtRzB57XgLrr8KXekl0iLCqi19UK
xneINd+zA1KtQztp4j3mbOIeyswXTTMIfbVkAAI1wwN5N79hIPctPGXXElrdqHvq
PNh0zCndV+xJrnQLEjHme9rL8+Y1Q/KCBqDXNpU4nHeDKa/6A3bD+FmXREcicbYI
m8r5S6keENLEpncBthoV4Kp2K6FV6whb/qLWC5muobJy+XnLcogADV7zNBmgqdHk
7QRbsdiA/1VN82e979d+XBPG0P24w4BhKwUlzB9nwxnmq9NQnxLaoIsq/doJ6Ng=
=b80y
-----END PGP SIGNATURE-----

Chris Grimmett

unread,
Jun 28, 2016, 8:05:54 AM6/28/16
to qubes-users, ch...@grimtech.net


Oops, sorry if I directly e-mailed you, Marek. I'm a mailing list noob and I think I need to reply-to-all when I did not. I did the command you suggested, then tried again. I saw the same 404 errors. It wasn't until I was working on another project, getting screenshots to save to AppVMs (https://jrruethe.github.io/blog/2015/09/17/screenshots-in-qubes/) when I was able to install a new package in Dom0. After that, I was able to get qubes-windows-tools updated. Here are the commands i ran:

* sudo qubes-dom0-update scrot
* sudo qubes-dom0-update qubes-windows-tools
* sudo qubes-dom0-update --enablerepo=qubes-*-testing qubes-windows-tools

Andrew David Wong

unread,
Jun 28, 2016, 9:02:16 AM6/28/16
to Chris Grimmett, qubes-users, ch...@grimtech.net
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-06-28 05:05, Chris Grimmett wrote:
> I did the command you suggested, then tried again. I saw the same
> 404 errors. It wasn't until I was working on another project,
> getting screenshots to save to AppVMs
> (https://jrruethe.github.io/blog/2015/09/17/screenshots-in-qubes/)
> when I was able to install a new package in Dom0. After that, I
> was able to get qubes-windows-tools updated. Here are the commands
> i ran:
>
> * sudo qubes-dom0-update scrot * sudo qubes-dom0-update
> qubes-windows-tools * sudo qubes-dom0-update
> --enablerepo=qubes-*-testing qubes-windows-tools
>

Are you downloading updates via Tor (sys-whonix)? If so, it's possible
that you just temporarily had a bad exit node.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXcnVIAAoJENtN07w5UDAwd3cP+wZetL9njcJULVO0VHW/Viqy
QVS+NQ1WJGFjKByocutM/vRUwueYke46SAEjH9UKyppM9GmdSvixdZFMLJikpQjS
CbJnDZtNutW2/37F8pju1hcuaQuhSc9Po6BP/4tFVxUku7a5GNwqcJoWYd9WmS3L
zrlPEr8/LEn+QT6vDpfszR266rcKkdFrpI9W3UlfrjPr5aDzAOWcvyex+B6yVcUF
5XWumaA+XnmMXypZsRze2rVNRg7NrV0BBSYbI4YSiVy1U7wuMp8215gDVNBF/Wxg
HRUzy7LNaHL/8Oi1I/NrSIizT65Lvy+/iqjRhWyAUvxmo7splPpf0aH9IsN+iNuP
R2/Uuo3SBtk9Osbtu+IMsOtRMX33yk3EW5xdj6jES2CHzAoKf8HyX4KxpBAJ/jNi
cl56ERhtrWjyY9Js+5nGv3UgIiBpvJuv1YzHPMM5jCbfBPa8qCLoPvWkKjZfd7MV
ttXHgNiw4ei2b8LwsKlhj6C5qZY8KSLUCYfOjrbiDnZY3NzKnIByYK7yYdvOScCy
6s0Ei3e9KDvjKv8Fo6IdpN6JklABcrxN+1tH7WYORAZS5XFjibXumfvr1mGdNLX1
DD108YhRIiyk91OTd/W+jpHje7JQcIFPX4BOs9d22ygB4OXzkTRSoqvV1185+fdv
vJ8B1Q5nC6dxouHfhFGf
=NGXE
-----END PGP SIGNATURE-----

Reply all
Reply to author
Forward
0 new messages