Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-12 Thread Alex
On 11/12/18 12:11 PM, unman wrote:
> On Sat, Nov 10, 2018 at 12:54:46PM +0100, Alex wrote:
>>[...]
>> Changed that with nano to read "4.0" instead of "$releasever" and voilà,
>> updates went through.
>>
> 
> Please bear in mind that if you do this you are breaking the logic of
> dnf, and will have to *manually* update that entry if you upgrade the
> system. You are almost bound to forget this.
> $releasever is part of yum/dnf, not Qubes.
I am well aware of this, both the fact that I'm gonna forget about it
and that $releasever is part of the yum workflow. Actually, since I hate
"fedup", it's the way I update my other computers to a newer fedora
version: dnf upgrade --releasever=29.

> You can pass in --releasever=4.0 as an option, which would be a better
> solution.
That's true; but as the time of writing my original response, I could
not figure out how $releasever was being catenated with both "25" and
"4", so I imagined something "fixed" was automatically appended and
decided not to brute-force the --releasever param.

I use Qubes as my main workstation, so I don't have much time to
extensively try and fix things... Still, I love it so much I thought I'd
jump into the thread and post my workaround.

> I havent encountered this bug myself,so cant account for it. It might be
> helpful if those who have could say if they have enabled testing repos,
> or are using plain 4.0 Qubes repositories. Any other detail would be
> helpful.
A very plain installation of R4.0, some couple of months after the
official release (I had to upgrade the CPU to install R4.0 from R3.2, so
I had to wait for it to arrive from an ebay seller in the UK).

Looking at the bug linked by Andrew (github issue 4477), seems like
Marek already found the cause.

I'll monitor the issue and, as soon as this is resolved (which may
involve a temporal link from yum.qubes-os.org/r25-4/ to
yum.qubes-os.org/r4.0?), will revert the repo files in /etc/yum.repos.d
to the original ones.

Thank you everybody,
-- 
Alex

-- 
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/d34197bb-8285-9faf-47a5-938574b46e51%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-12 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 11/12/18 5:11 AM, unman wrote:
> On Sat, Nov 10, 2018 at 12:54:46PM +0100, Alex wrote:
>> On 11/10/18 11:23 AM, hm...@tuta.io wrote:
>>> hello
>>>
>>> I have exactly the same problem on two of my x230 Lenovo notebooks with 
>>> Qubes version R4.0.1rc1.
>> Have had this very issue on R4.0.
>>
>> I checked by running, in dom0:
>> # qubes-dom0-update -v
>>
>> That runs the dnf updater with the "-v" verbose flag. With that, the URL
>> for the repositories will be printed on screen, in red (because it's
>> happening in the UpdateVM).
>>
>> I found that the URL being printed was
>> https://yum.qubes-os.org/r25-4/current/dom0/fc25/repodata/repomd.xml.metalink
>>
>> instead of the correct
>> https://yum.qubes-os.org/r4.0/current/dom0/fc25/repodata/repomd.xml.metalink
>>
>> (the yum.qubes-os.org domain can be navigated with a browser).
>>
>> I found that inside [dom0]/etc/yum.repos.d/qubes-dom0.repo the url is
>> saved as
>> https://yum.qubes-os.org/r$releasever/current/dom0/fc25/repodata/repomd.xml.metalink
>>
>> Changed that with nano to read "4.0" instead of "$releasever" and voilà,
>> updates went through.
>>
>> Check, try and let the list know ;)
>>
>> -- 
>> Alex
> 
> Please bear in mind that if you do this you are breaking the logic of
> dnf, and will have to *manually* update that entry if you upgrade the
> system. You are almost bound to forget this.
> $releasever is part of yum/dnf, not Qubes.
> 
> You can pass in --releasever=4.0 as an option, which would be a better
> solution.
> 
> I havent encountered this bug myself,so cant account for it. It might be
> helpful if those who have could say if they have enabled testing repos,
> or are using plain 4.0 Qubes repositories. Any other detail would be
> helpful.
> 
> unman
> 

This sounds like:

https://github.com/QubesOS/qubes-issues/issues/4477

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlvqaW4ACgkQ203TvDlQ
MDAAIQ/6A57l5meIGtBmpYGZgIwOzqE6LaOkfghfYot+pXVAdzAr+TXfkkAmy4fp
RmjagpufU2oVma2kwWAUjzVEZxgJI8KIQoBNN1vLiO3dH88KkDN4FJV5EJ1/QnBn
AsdVvhUSNz8l2x1qhDGlthpnNHXaho2laBXV6WLIhGl8WAgnvXCiLyT0PMm/+lPx
opnry33xATKxLBmvIuTVo0YtrHxIoaBicYdaZ3tCyefT3/MADfKjTG2kCMX6IExl
Ov9T2oyEnzkqeC4qOhDvhnLrwcfewt4hRCmsPV/Xv7Q8FBr3MyO/7CVbI38m9bkS
w7lq6uL5bS2HS4kseYOZQzqKEARjO83SEavwfyH+84uijDrfgoNqyFQcFVjpFyCo
bXc/Ncdo2HOflQxtVpuSJmsnSE9+BBzuXD+VXABxst6HGaHlP5Cy8566nJI9GEsk
8jb57cdg8lRHNHzy/uBw/tXyckhOfyjREdD7UG9tju/JYaECNoV+KsXNg2rCisCc
OH3OwS8aNDitvU8sH/J1JMgWh83HMyLH+8bJQoMbLVR6yALPdRyOUQcw15z0XIsG
NUJTr8tZVDVN+KECvVXgXs9LXrnEObyndPe4Mh9sXSZP6jsfDtBpDgTQfnEmXpJ0
yfQTU3hcgSvatqCRJy2DxroGpY8qk/r5vegUuytcuNhO6xo6yZo=
=TTVl
-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/36ea7dd7-65a7-7935-68b2-2a295a12424f%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-12 Thread unman
On Sat, Nov 10, 2018 at 12:54:46PM +0100, Alex wrote:
> On 11/10/18 11:23 AM, hm...@tuta.io wrote:
> > hello
> > 
> > I have exactly the same problem on two of my x230 Lenovo notebooks with 
> > Qubes version R4.0.1rc1.
> Have had this very issue on R4.0.
> 
> I checked by running, in dom0:
> # qubes-dom0-update -v
> 
> That runs the dnf updater with the "-v" verbose flag. With that, the URL
> for the repositories will be printed on screen, in red (because it's
> happening in the UpdateVM).
> 
> I found that the URL being printed was
> https://yum.qubes-os.org/r25-4/current/dom0/fc25/repodata/repomd.xml.metalink
> 
> instead of the correct
> https://yum.qubes-os.org/r4.0/current/dom0/fc25/repodata/repomd.xml.metalink
> 
> (the yum.qubes-os.org domain can be navigated with a browser).
> 
> I found that inside [dom0]/etc/yum.repos.d/qubes-dom0.repo the url is
> saved as
> https://yum.qubes-os.org/r$releasever/current/dom0/fc25/repodata/repomd.xml.metalink
> 
> Changed that with nano to read "4.0" instead of "$releasever" and voilà,
> updates went through.
> 
> Check, try and let the list know ;)
> 
> -- 
> Alex

Please bear in mind that if you do this you are breaking the logic of
dnf, and will have to *manually* update that entry if you upgrade the
system. You are almost bound to forget this.
$releasever is part of yum/dnf, not Qubes.

You can pass in --releasever=4.0 as an option, which would be a better
solution.

I havent encountered this bug myself,so cant account for it. It might be
helpful if those who have could say if they have enabled testing repos,
or are using plain 4.0 Qubes repositories. Any other detail would be
helpful.

unman

-- 
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/2018111209.nj6lj7dotaeegxvq%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-11 Thread liontren1
On Saturday, November 10, 2018 at 6:57:15 AM UTC-5, Alex wrote:
> On 11/10/18 11:23 AM, hm...@tuta.io wrote:
> > hello
> > 
> > I have exactly the same problem on two of my x230 Lenovo notebooks with 
> > Qubes version R4.0.1rc1.
> Have had this very issue on R4.0.
> 
> I checked by running, in dom0:
> # qubes-dom0-update -v
> 
> That runs the dnf updater with the "-v" verbose flag. With that, the URL
> for the repositories will be printed on screen, in red (because it's
> happening in the UpdateVM).
> 
> I found that the URL being printed was
> https://yum.qubes-os.org/r25-4/current/dom0/fc25/repodata/repomd.xml.metalink
> 
> instead of the correct
> https://yum.qubes-os.org/r4.0/current/dom0/fc25/repodata/repomd.xml.metalink
> 
> (the yum.qubes-os.org domain can be navigated with a browser).
> 
> I found that inside [dom0]/etc/yum.repos.d/qubes-dom0.repo the url is
> saved as
> https://yum.qubes-os.org/r$releasever/current/dom0/fc25/repodata/repomd.xml.metalink
> 
> Changed that with nano to read "4.0" instead of "$releasever" and voilà,
> updates went through.
> 
> Check, try and let the list know ;)
> 
> -- 
> Alex

Hi Alex ,

By any chance you can help or anyone on here i would really appreciate it.
I have no clue on how to go into nano to change the releasever to 4.0 ?
Can anyone tell me or guide me please on how this is done .

thank you so much 

-- 
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/e4de046d-3350-4026-a8cd-226dbcb73283%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-10 Thread hmiyc
Am Samstag, 10. November 2018 19:45:25 UTC+1 schrieb alrojs:
> On Saturday, November 10, 2018 at 8:29:04 AM UTC-8, hm...@tuta.io wrote:
> > @Alex - Thank you for pointing that out.
> > 
> > I just tried to install version R4.0.1rc1 on the x230 again, but the 
> > installation breaks off when configuring ext4.  It is probably due to the 
> > HW or Coreboot.
> > 
> > I will flash my x220 with Coreboot/SeaBios + Intel ME Cleaner and install 
> > R4.0.1rc1 again.  Then i let you know if your tip worked.
> > 
> > 
> > PS.  Under Qubes 3.0/3.1/3.2 i didn't have these problems.
> > 
> > 
> > Greetings
> > 
> > Sebi
> 
> We're you able to get it working? 
> 
> I will try this tip right now

@Alex - I tried the installation quickly on my HP x360 1030 G2. Your hint works 
fine. Thanks a lot Alex. 

HW specifications: HP Elitebook x360 1030 G2
Intel Core i7 vPro 7th Gen
16GB RAM
256GB SSd
OS - Qubes R4.0.1rc1

PS:Test it soon on my x220. 

Br
Sebi

-- 
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/dcbdc93f-1e96-495a-84b0-09ce56c55d4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-10 Thread alrojs

This worked! this pushed the update through!!!

-- 
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/4333bad3-a7a0-413c-85c6-7f2476630540%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-10 Thread alrojs
On Saturday, November 10, 2018 at 8:29:04 AM UTC-8, hm...@tuta.io wrote:
> @Alex - Thank you for pointing that out.
> 
> I just tried to install version R4.0.1rc1 on the x230 again, but the 
> installation breaks off when configuring ext4.  It is probably due to the HW 
> or Coreboot.
> 
> I will flash my x220 with Coreboot/SeaBios + Intel ME Cleaner and install 
> R4.0.1rc1 again.  Then i let you know if your tip worked.
> 
> 
> PS.  Under Qubes 3.0/3.1/3.2 i didn't have these problems.
> 
> 
> Greetings
> 
> Sebi

We're you able to get it working? 

I will try this tip right now 

-- 
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/77a32881-9c1b-4c96-8243-db532a9974af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-10 Thread hmiyc
@Alex - Thank you for pointing that out.

I just tried to install version R4.0.1rc1 on the x230 again, but the 
installation breaks off when configuring ext4.  It is probably due to the HW or 
Coreboot.

I will flash my x220 with Coreboot/SeaBios + Intel ME Cleaner and install 
R4.0.1rc1 again.  Then i let you know if your tip worked.


PS.  Under Qubes 3.0/3.1/3.2 i didn't have these problems.


Greetings

Sebi

-- 
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/84e80aa2-87b8-400a-88e5-5c72783b7c0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [solved] Re: Failed to synchronize cache for repo 'qubes-dom0-cached', disabling.

2018-11-10 Thread Alex
On 11/10/18 11:23 AM, hm...@tuta.io wrote:
> hello
> 
> I have exactly the same problem on two of my x230 Lenovo notebooks with Qubes 
> version R4.0.1rc1.
Have had this very issue on R4.0.

I checked by running, in dom0:
# qubes-dom0-update -v

That runs the dnf updater with the "-v" verbose flag. With that, the URL
for the repositories will be printed on screen, in red (because it's
happening in the UpdateVM).

I found that the URL being printed was
https://yum.qubes-os.org/r25-4/current/dom0/fc25/repodata/repomd.xml.metalink

instead of the correct
https://yum.qubes-os.org/r4.0/current/dom0/fc25/repodata/repomd.xml.metalink

(the yum.qubes-os.org domain can be navigated with a browser).

I found that inside [dom0]/etc/yum.repos.d/qubes-dom0.repo the url is
saved as
https://yum.qubes-os.org/r$releasever/current/dom0/fc25/repodata/repomd.xml.metalink

Changed that with nano to read "4.0" instead of "$releasever" and voilà,
updates went through.

Check, try and let the list know ;)

-- 
Alex

-- 
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/90d6b896-f532-519a-cffd-bcdafe509eb8%40gmx.com.
For more options, visit https://groups.google.com/d/optout.