-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-10-09 00:53, Pagebao wrote:
> Hi,
> 
> I upgraded to Qubes 3.2 from 3.1 with a clean install.
> Trying to install software in the new fedora-23 template (as I did with 3.1 
> without no issues) but receiving the following error message.
> 
> Error: Failed to synchronize cache for repo 'updates'
> 
> Did you get the same? Any idea how I can fix that?
> 
> Can I 
> 
> Thanks
> 

I see this error commonly when downloading updates via Tor. Waiting and trying 
again later usually works. (Circuits are rebuilt automatically every 10 
minutes. If you'd prefer not to wait, you can request a new identity manually 
by pressing "n" in tor-arm in sys-whonix.)

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

iQIcBAEBCgAGBQJX+g6WAAoJENtN07w5UDAwDAMP/38h7uIXsYqG8+AXLzf1AQXD
WMCqIyDOGA/q5aQIrPadkHXxGo2vLIxSRmC97qcqg13+McCpKGPgBh9ScCeOugod
xdMIeYwdHXXKXna5hU//WxqiRX/nkoGLv1jzdbosEhYbiPrwprdq/fLFqU3H8B+1
atzmHp9u39Xt4mPpveYyh/Tnjatm3kwxPK0ClaeOErEBxka6MD1ylrU68Z0ZKRvx
S666dR6EW6XemRgVwSbMKmMPkrXYwnmVGE8yImjyO8Z4A4I5ohT3DLNTbbufsEEg
mvfcHDI259vTRrdyL4ktu5wxZmZuk5wNRimUD87PaJbhdAc1l+j84ROITv4or5La
vBJDSn72efU7O4X6ID0Us+1XquCbWhEqLEraF9+vGDE4UwGeyqaEMcb/ofKTQiUP
uBXCSFOFk9usBJgOIhuVDnxcAWzj6yrs8uRUOViGE3MIFLGU4t+ODAn5uWZrVUoY
kFO+qoD8svgEOrhjzq5bZuaM9PVyig4pchXV6QFrbS8c7KI3IA+aHru6jiV1cMaK
bhvo07iCfkfGAOCf+Z3TjZS+l4PZM/Rz8Q1kfRjRur5I+Lj+YJAQe9VSAdlhK5o2
sxy/V0SEyKBusnzMF3pgZTmImp6zWLQLeZua0lCmGXFA8BGbrfiqYNO/0huKwZrn
g3T4P2tHIwWgTR18q/9+
=/sRs
-----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/54062323-0577-a92a-ffee-be7519761207%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to