Re: [qubes-users] Re: Errors updating Qubes 4: Unknown configuration value: failovermethod=priority (...) Status code: 404

2019-03-31 Thread 'awokd' via qubes-users

one7tw...@gmail.com:

On Sunday, 31 March 2019 12:37:52 UTC+2, one7...@gmail.com  wrote:

Hello,

I have trouble updating my Qubes 4 installtion as suddenly updates seems to be 
broken:



Additional comment:
I have looked at the output and found that I have no directory:
cachedir: /var/lib/qubes/dom0-updates/var/cache/yum/x86_64/4.0

Should this directory be present?

Loooking at:

Unknown configuration value: failovermethod=priority in 
/var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora.repo; Configuration: OptionBinding 
with id "failovermethod" does not exist

As this directory is not present, the fedora.repo file is also not located 
there.
The fedora.repo file can be found in /etc/yum.repos.d/fedora.repo and I tried to comment 
out the lines "failovermethod=priority" but then I get the following results:


You might try temporarily changing your updateVM to a debian based one. 
If it's sys-firewall, could easily change the template for it. Then once 
updates are processing normally again, change it back.


--
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/dac77d03-76d6-d777-4346-a900f87514a9%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Errors updating Qubes 4: Unknown configuration value: failovermethod=priority (...) Status code: 404

2019-03-31 Thread one7two99
On Sunday, 31 March 2019 12:37:52 UTC+2, one7...@gmail.com  wrote:
> Hello,
> 
> I have trouble updating my Qubes 4 installtion as suddenly updates seems to 
> be broken:
> 
> [USER@dom0 ~]$ sudo qubes-dom0-update --action="-v update --refresh"
> Using sys-firewall as UpdateVM to download updates for Dom0; this may take 
> some time...
> DNF version: 4.0.9
> cachedir: /var/lib/qubes/dom0-updates/var/cache/yum/x86_64/4.0
> Unknown configuration value: failovermethod=priority in 
> /var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora-updates.repo; 
> Configuration: OptionBinding with id "failovermethod" does not exist
> Unknown configuration value: failovermethod=priority in 
> /var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora-updates.repo; 
> Configuration: OptionBinding with id "failovermethod" does not exist
> [...]
> [MIRROR] curl-minimal-7.61.1-6.fc29.x86_64.rpm: Status code: 404 for 
> https://mirror.linux-ia64.org/fedora/linux/updates/29/Everything/x86_64/Packages/c/curl-minimal-7.61.1-6.fc29.x86_64.rpm
> 
> I have looked into /etc/yum.repos.d/fedora-updates.repo:
> 
> 
> [updates]
> name=Fedora 25 - x86_64 - Updates
> failovermethod=priority
> #baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/25/x86_64/
> metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f25=x86_64
> enabled=1
> enablegroups=0
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-primary
> 
> [updates-debuginfo]
> name=Fedora 25 - x86_64 - Updates - Debug
> failovermethod=priority
> #baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/25/x86_64/debug/
> metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-debug-f25=x86_64
> enabled=0
> enablegroups=0
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-primary
> 
> [updates-source]
> name=Fedora 25 - Updates Source
> failovermethod=priority
> #baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/25/SRPMS/
> metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-source-f25=x86_64
> enabled=0
> enablegroups=0
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-primary
> 
> What does this error message means:
> 
> Configuration: OptionBinding with id "failovermethod" does not exist
> 
> ... and even more important, how can I fix it.
> Updates were possible before but it seems something is broken which must have 
> happened through a regular update, as I didn't change the configuration.
> 
> - O

Additional comment:
I have looked at the output and found that I have no directory:
cachedir: /var/lib/qubes/dom0-updates/var/cache/yum/x86_64/4.0

Should this directory be present?

Loooking at:

Unknown configuration value: failovermethod=priority in 
/var/lib/qubes/dom0-updates/etc/yum.repos.d/fedora.repo; Configuration: 
OptionBinding with id "failovermethod" does not exist

As this directory is not present, the fedora.repo file is also not located 
there.
The fedora.repo file can be found in /etc/yum.repos.d/fedora.repo and I tried 
to comment out the lines "failovermethod=priority" but then I get the following 
results:

[USER@dom0 updates]$ sudo qubes-dom0-update --action="-v update --refresh> "
Using sys-firewall as UpdateVM to download updates for Dom0; this may take some 
time...
DNF version: 4.0.9
cachedir: /var/lib/qubes/dom0-updates/var/cache/yum/x86_64/4.0
Fedora 25 - x86_64 - Updates3.5 kB/s | 5.4 kB 00:01
reviving: 'updates' can be revived - metalink checksums match.
not found other for: Fedora 25 - x86_64 - Updates
not found modules for: Fedora 25 - x86_64 - Updates
updates: using metadata from Tue Dec 12 15:34:19 2017.
Fedora 25 - x86_64  3.8 kB/s | 5.8 kB 00:01
reviving: 'fedora' can be revived - metalink checksums match.
not found other for: Fedora 25 - x86_64
not found modules for: Fedora 25 - x86_64
not found updateinfo for: Fedora 25 - x86_64
fedora: using metadata from Tue Nov 15 20:49:18 2016.
Qubes Dom0 Repository (updates) 2.3 kB/s | 2.7 kB 00:01
reviving: 'qubes-dom0-current' can be revived - metalink checksums match.
not found other for: Qubes Dom0 Repository (updates)
not found modules for: Qubes Dom0 Repository (updates)
not found deltainfo for: Qubes Dom0 Repository (updates)
not found updateinfo for: Qubes Dom0 Repository (updates)
qubes-dom0-current: using metadata from Tue Mar 26 00:56:22 2019.
Qubes Templates repository  2.2 kB/s | 2.7 kB 00:01
reviving: 'qubes-templates-itl' can be revived - metalink checksums match.
not found other for: Qubes Templates repository
not found modules for: Qubes Templates repository
not found deltainfo for: Qubes Templates repository
not found updateinfo for: Qubes Templates repository
qubes-templates-itl: using metadata from Tue Feb 19 14:32:28 2019.
--> Starting dependency resolution
---> Package anaconda-core.x86_64 1000:25.20.9-14.fc25 will be reinstalled