[qubes-users] Re: Cannot Update Fedora-29 and Debian-9 on 4.0.1

2019-01-11 Thread John S.Recdep
On 1/11/19 8:08 AM,
scoobyscrappy-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> Hello,
> 
> I am a new user to Qubes and I like it very much.
> 
> I am on 4.0.1 and I am unable to update the Fedora-29 and Debian-9 templates. 
>  Below are the errors for both:
> 
> Fedora-29:
> 
> Fedora Modular 29 - x86_64
> Error: Failed to synchronize cache for repo 'fedora-modular'
> Done.
> 
> Debian-9 (snippet):
> 
> Err:3 http://deb.qubes-os.org/r4.0/vm stretch Release
>   500 Unable to connect
> Err:6 https://deb.debian.org/debian stretch Release
>   Received HTTP code 500 from proxy after CONNECT
> Err:7 https://deb.debian.org/debian-security stretch/updates Release
>   Received HTTP code 500 from proxy after CONNECT
> Err:8 https://deb.debian.org/debian jessie-backports Release
>   Received HTTP code 500 from proxy after CONNECT
> E: The repository 'http://deb.qubes-os.org/r4.0/vm stretch Release' does no 
> longer have a Release file.
> E: The repository 'https://deb.debian.org/debian stretch Release' does no 
> longer have a Release file.
> E: The repository 'https://deb.debian.org/debian-security stretch/updates 
> Release' does no longer have a Release file.
> E: The repository 'https://deb.debian.org/debian jessie-backports Release' 
> does no longer have a Release file.
> 
> TIA
> 

try doing it via a terminal in the templates

$sudo dnf update

$sudo apt-get update
sudo apt-get dist-upgrade

fwiw for myself, the qubes manager fails or is so slow I only use it to
make appvms or change/add applications  lately


so I guess this is a new install of yours?

-- 
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/cd0a9206-336a-3512-7124-b42d1607d69b%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Cannot Update Fedora-29 and Debian-9 on 4.0.1

2019-01-13 Thread scoobyscrappy
On Friday, January 11, 2019 at 10:35:11 AM UTC-8, John S.Recdep wrote:
> On 1/11/19 8:08 AM,
> scoobyscrappy-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> > Hello,
> > 
> > I am a new user to Qubes and I like it very much.
> > 
> > I am on 4.0.1 and I am unable to update the Fedora-29 and Debian-9 
> > templates.  Below are the errors for both:
> > 
> > Fedora-29:
> > 
> > Fedora Modular 29 - x86_64
> > Error: Failed to synchronize cache for repo 'fedora-modular'
> > Done.
> > 
> > Debian-9 (snippet):
> > 
> > Err:3 http://deb.qubes-os.org/r4.0/vm stretch Release
> >   500 Unable to connect
> > Err:6 https://deb.debian.org/debian stretch Release
> >   Received HTTP code 500 from proxy after CONNECT
> > Err:7 https://deb.debian.org/debian-security stretch/updates Release
> >   Received HTTP code 500 from proxy after CONNECT
> > Err:8 https://deb.debian.org/debian jessie-backports Release
> >   Received HTTP code 500 from proxy after CONNECT
> > E: The repository 'http://deb.qubes-os.org/r4.0/vm stretch Release' does no 
> > longer have a Release file.
> > E: The repository 'https://deb.debian.org/debian stretch Release' does no 
> > longer have a Release file.
> > E: The repository 'https://deb.debian.org/debian-security stretch/updates 
> > Release' does no longer have a Release file.
> > E: The repository 'https://deb.debian.org/debian jessie-backports Release' 
> > does no longer have a Release file.
> > 
> > TIA
> > 
> 
> try doing it via a terminal in the templates
> 
> $sudo dnf update
> 
> $sudo apt-get update
> sudo apt-get dist-upgrade
> 
> fwiw for myself, the qubes manager fails or is so slow I only use it to
> make appvms or change/add applications  lately
> 
> 
> so I guess this is a new install of yours?


This was a new install of 4.0.1.

I got the same errors when I terminal into the debian-9 and fedora-29 templates 
using your commands.

-- 
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/a3ea9cdf-2e51-44fc-bf46-d4ef2514025a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Cannot Update Fedora-29 and Debian-9 on 4.0.1

2019-01-13 Thread scoobyscrappy
On Friday, January 11, 2019 at 10:35:11 AM UTC-8, John S.Recdep wrote:
> On 1/11/19 8:08 AM,
> scoobyscrappy-re5jqeeqqe8avxtiumw...@public.gmane.org wrote:
> > Hello,
> > 
> > I am a new user to Qubes and I like it very much.
> > 
> > I am on 4.0.1 and I am unable to update the Fedora-29 and Debian-9 
> > templates.  Below are the errors for both:
> > 
> > Fedora-29:
> > 
> > Fedora Modular 29 - x86_64
> > Error: Failed to synchronize cache for repo 'fedora-modular'
> > Done.
> > 
> > Debian-9 (snippet):
> > 
> > Err:3 http://deb.qubes-os.org/r4.0/vm stretch Release
> >   500 Unable to connect
> > Err:6 https://deb.debian.org/debian stretch Release
> >   Received HTTP code 500 from proxy after CONNECT
> > Err:7 https://deb.debian.org/debian-security stretch/updates Release
> >   Received HTTP code 500 from proxy after CONNECT
> > Err:8 https://deb.debian.org/debian jessie-backports Release
> >   Received HTTP code 500 from proxy after CONNECT
> > E: The repository 'http://deb.qubes-os.org/r4.0/vm stretch Release' does no 
> > longer have a Release file.
> > E: The repository 'https://deb.debian.org/debian stretch Release' does no 
> > longer have a Release file.
> > E: The repository 'https://deb.debian.org/debian-security stretch/updates 
> > Release' does no longer have a Release file.
> > E: The repository 'https://deb.debian.org/debian jessie-backports Release' 
> > does no longer have a Release file.
> > 
> > TIA
> > 
> 
> try doing it via a terminal in the templates
> 
> $sudo dnf update
> 
> $sudo apt-get update
> sudo apt-get dist-upgrade
> 
> fwiw for myself, the qubes manager fails or is so slow I only use it to
> make appvms or change/add applications  lately
> 
> 
> so I guess this is a new install of yours?

This was a new install of 4.0.1.

I got the same errors when I terminal into the debian-9 and fedora-29 
templates.  

Here is the errors I got from the debian-9 update:

Jan 13 09:30:09 localhost systemd[1]: Started Forward connection to updates prox
y over Qubes RPC (127.0.0.1:59084).
Jan 13 09:30:09 localhost systemd[1]: Started Forward connection to updates prox
y over Qubes RPC (127.0.0.1:59086).
Jan 13 09:30:09 localhost systemd[1]: qubes-updates-proxy-forwarder@0-127.0.0.1:
8082-127.0.0.1:59082.service: Main process exited, code=exited, status=1/FAILURE
Jan 13 09:30:09 localhost systemd[1]: qubes-updates-proxy-forwarder@0-127.0.0.1:
8082-127.0.0.1:59082.service: Unit entered failed state.
Jan 13 09:30:09 localhost systemd[1]: qubes-updates-proxy-forwarder@0-127.0.0.1:
8082-127.0.0.1:59082.service: Failed with result 'exit-code'.

Here is the errors I get from fedora-29:

2019-01-13T17:34:39Z DEBUG Unknown configuration value: failovermethod=priority 
in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failoverm
ethod" does not exist
2019-01-13T17:34:39Z DEBUG repo: downloading from remote: fedora-modular
2019-01-13T17:34:39Z DEBUG error: Curl error (56): Failure when receiving data f
rom the peer for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-
29&arch=x86_64 [Received HTTP code 500 from proxy after CONNECT] (https://mirror
s.fedoraproject.org/metalink?repo=fedora-modular-29&arch=x86_64).
2019-01-13T17:34:39Z DEBUG Cannot download 'https://mirrors.fedoraproject.org/me
talink?repo=fedora-modular-29&arch=x86_64': Cannot prepare internal mirrorlist: 
Curl error (56): Failure when receiving data from the peer for https://mirrors.f
edoraproject.org/metalink?repo=fedora-modular-29&arch=x86_64 [Received HTTP code
 500 from proxy after CONNECT].
2019-01-13T17:34:39Z DDEBUG Cleaning up.
2019-01-13T17:34:39Z SUBDEBUG 
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/dnf/repo.py", line 566, in load
ret = self._repo.load()
  File "/usr/lib64/python3.7/site-packages/libdnf/repo.py", line 503, in load
return _repo.Repo_load(self)
RuntimeError: Failed to synchronize cache for repo 'fedora-modular'


TIA

-- 
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/a37d9151-8464-403b-a01b-d8d93a3c7d5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.