Re: [qubes-devel] broken dom0 updates, shall I report this at qubes-issues?
On 3/19/21 6:35 PM, Marek Marczykowski-Górecki wrote: Ah, you probably have Debian-based updatevm, which doesn't support this option. Then, use --clean. I do & did. Thank you! /Sven -- public key: https://www.svensemmler.org/0x8F541FB6.asc fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/663cf5b5-5312-02a8-1f99-c1f4a3355c59%40SvenSemmler.org. OpenPGP_signature Description: OpenPGP digital signature
Re: [qubes-devel] broken dom0 updates, shall I report this at qubes-issues?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Mar 19, 2021 at 03:07:48PM -0500, Sven Semmler wrote: > On 3/19/21 2:03 PM, Marek Marczykowski-Górecki wrote: > > Are you sure you don't have security-testing or current-testing > > enabled? Those packages are currently only there. > > I had it enabled once to see which packages would update, but did not say > yes ... so they might have been cached in the updatevm? It is possible, yes (if you haven't restarted your updatevm since). - --clean option mentioned below will remove that cache too. > > You can retry with `qubes-dom0-update --refresh` > > That tells me "Command line error: no such option: --refresh" Ah, you probably have Debian-based updatevm, which doesn't support this option. Then, use --clean. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmBVNUAACgkQ24/THMrX 1yzuIQf+KBgA5ZzqIInCoCcJD7Lebm3d9Nymq4hLFBOprKe8yOj+N98diKBNDHg4 4x+yCAWlP5F4wXxSW1H5BoytweRVyCkJIWThXfj5Ci1aTLAuH2EK1P3BfVbtrgw1 9cR2kGOINlDsYPX7Yt7YXysjoADC25DnWgSn2NzMY19PgPNmb6F10GYATdABrypO 7vbgvGxmQ01UYBSkUp0ZwjQZAtXUI0SkInqHbCRybS/FZ1KWHyjJEVu0SPjbPeyq xyhQ3/dNlQexhTNyUwRx9HBKmc5JALUNA4xO7eO5yuN6PMNYcBo7NTzWBX50TKzE gmGHbhJbJh7dnkqvffbAcdE/BsPucA== =sSQe -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/YFU1QTsvO53ZNEM8%40mail-itl.
Re: [qubes-devel] broken dom0 updates, shall I report this at qubes-issues?
On 3/19/21 4:44 PM, Demi M. Obenour wrote: ‘qubes-dom0-update --clean’ should work. It did. Thank you! /Sven -- public key: https://www.svensemmler.org/0x8F541FB6.asc fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/8113febf-ca0c-4272-6149-b69d7d986d21%40SvenSemmler.org. OpenPGP_signature Description: OpenPGP digital signature
[qubes-devel] broken dom0 updates, shall I report this at qubes-issues?
On 3/19/21 4:07 PM, Sven Semmler wrote: > On 3/19/21 2:03 PM, Marek Marczykowski-Górecki wrote: >> Are you sure you don't have security-testing or current-testing >> enabled? Those packages are currently only there. > > I had it enabled once to see which packages would update, but did not say yes > ... so they might have been cached in the updatevm? > >> You can retry with `qubes-dom0-update --refresh` > > That tells me "Command line error: no such option: --refresh" > > I am actually fine with enabling security-testing, I just said "no" because > the dependency errors scared me. When I try again now, I still see the > errors. Either the dependencies or with the additional parameters the warning > that something critical will be removed. > > Is there another way I can force a --refresh? ... should I just wait? ‘qubes-dom0-update --clean’ should work. > Since this is the devel list and this not a bug but something I did, shall I > take it to qubes-users? > > Sorry for the noise. > > /Sven Sincerely, Demi Marie Obenour she/her/hers QubesOS Developer, Invisible Things Lab -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/d82d8e74-30d5-986a-e5ee-5e839a95ed84%40invisiblethingslab.com. OpenPGP_0xB288B55FFF9C22C1.asc Description: application/pgp-keys OpenPGP_0xB288B55FFF9C22C1.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature
Re: [qubes-devel] broken dom0 updates, shall I report this at qubes-issues?
On 3/19/21 2:03 PM, Marek Marczykowski-Górecki wrote: Are you sure you don't have security-testing or current-testing enabled? Those packages are currently only there. I had it enabled once to see which packages would update, but did not say yes ... so they might have been cached in the updatevm? You can retry with `qubes-dom0-update --refresh` That tells me "Command line error: no such option: --refresh" I am actually fine with enabling security-testing, I just said "no" because the dependency errors scared me. When I try again now, I still see the errors. Either the dependencies or with the additional parameters the warning that something critical will be removed. Is there another way I can force a --refresh? ... should I just wait? Since this is the devel list and this not a bug but something I did, shall I take it to qubes-users? Sorry for the noise. /Sven -- public key: https://www.svensemmler.org/0x8F541FB6.asc fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/25dd4fe2-8065-d760-1c3c-89a165898eff%40SvenSemmler.org. OpenPGP_signature Description: OpenPGP digital signature
Re: [qubes-devel] broken dom0 updates, shall I report this at qubes-issues?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Mar 19, 2021 at 01:03:17PM -0500, Sven Semmler wrote: > This is on a install from the 4.0.3 ISO running for several months. I always > only do sudo qubes-dom0-update (no security or other testing). > > Today I see this: (...) > Skipping packages with conflicts: > (add '--best --allowerasing' to command line to force their upgrade): > PackageKit-glib x86_64 1.1.5-1.1.fc25 qubes-dom0-cached 129 k > Skipping packages with broken dependencies: > PackageKit x86_64 1.1.5-1.1.fc25 qubes-dom0-cached 664 k > createrepo_c x86_64 0.10.0-6.1.fc25 qubes-dom0-cached 69 k > createrepo_c-libsx86_64 0.10.0-6.1.fc25 qubes-dom0-cached 95 k > deltarpm x86_64 3.6-17.1.fc25 qubes-dom0-cached 89 k > drpm x86_64 0.3.0-3.1.fc25 qubes-dom0-cached 67 k > hawkey x86_64 0.6.4-3.1.fc25 qubes-dom0-cached 64 k > libsolv x86_64 0.6.29-2.1.fc25 qubes-dom0-cached 361 k > python2-deltarpm x86_64 3.6-17.1.fc25 qubes-dom0-cached 36 k > python3-hawkey x86_64 0.6.4-3.1.fc25 qubes-dom0-cached 47 k > qubes-core-dom0-linuxx86_64 4.0.29-1.fc25 qubes-dom0-cached 54 k > satyrx86_64 0.21-2.1.fc25 qubes-dom0-cached 108 k Are you sure you don't have security-testing or current-testing enabled? Those packages are currently only there. There should be also "rpm" with version 4.14.2.1, and in fact I think its lack is responsible for those broken dependencies. Hmm, indeed it seems that one specific package failed to upload to security-testing, was only in current-testing. I've fixed it now: https://github.com/QubesOS/updates-status/issues/2385 You can retry with `qubes-dom0-update --refresh` - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmBU9XwACgkQ24/THMrX 1yxt8QgAg1RhRCww+/Z8t6JKyggrCx8L2ibVVGWfHokVxaddMHiHO60ee/8+lN7g xt+sLLyz3SYf/lBPngIwQFizKPT6/7D81vBenkEx0ZsKIsgN1/A4qR8lmo/EJIf8 B4zIm4orLCgFGFmwI+YAqs+3aZMdKnAxErw+qAhMVe70yOI5vklSQy2ASb9cR5Wl pei1KchKDkZ8SwkkdjTE7bN1dD78Z81lhX0A4oNJiFgsvrsB35/tbXn0w72ncNXW JGxcwH9dYQ5SCchKhz0TprBX0fhq3POxfx8QXBm8oPskgQfbOb7qgClvkqtWk0he WuaGc6VictrzodROrhMZEg5+UMgNiw== =ZOLG -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/YFT1fCzuLJ4odzp2%40mail-itl.
[qubes-devel] broken dom0 updates, shall I report this at qubes-issues?
This is on a install from the 4.0.3 ISO running for several months. I always only do sudo qubes-dom0-update (no security or other testing). Today I see this: Package Arch VersionRepository Size Upgrading: device-mapper-persistent-data x86_64 0.7.5-3.1.fc25 qubes-dom0-cached 435 k grub2-starfield-themex86_64 1:2.02-0.38.1.fc25 qubes-dom0-cached 2.2 M qubes-core-dom0-linux-kernel-install x86_64 4.0.29-1.fc25 qubes-dom0-cached 14 k qubes-mgmt-salt-dom0-update noarch 4.0.10-1.fc25 qubes-dom0-cached 55 k xorg-x11-drv-ati x86_64 18.0.1-1.1.fc25 qubes-dom0-cached 169 k xorg-x11-drv-nouveau x86_64 1:1.0.15-4.1.fc25 qubes-dom0-cached 100 k Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): PackageKit-glib x86_64 1.1.5-1.1.fc25 qubes-dom0-cached 129 k Skipping packages with broken dependencies: PackageKit x86_64 1.1.5-1.1.fc25 qubes-dom0-cached 664 k createrepo_c x86_64 0.10.0-6.1.fc25 qubes-dom0-cached 69 k createrepo_c-libsx86_64 0.10.0-6.1.fc25 qubes-dom0-cached 95 k deltarpm x86_64 3.6-17.1.fc25 qubes-dom0-cached 89 k drpm x86_64 0.3.0-3.1.fc25 qubes-dom0-cached 67 k hawkey x86_64 0.6.4-3.1.fc25 qubes-dom0-cached 64 k libsolv x86_64 0.6.29-2.1.fc25 qubes-dom0-cached 361 k python2-deltarpm x86_64 3.6-17.1.fc25 qubes-dom0-cached 36 k python3-hawkey x86_64 0.6.4-3.1.fc25 qubes-dom0-cached 47 k qubes-core-dom0-linuxx86_64 4.0.29-1.fc25 qubes-dom0-cached 54 k satyrx86_64 0.21-2.1.fc25 qubes-dom0-cached 108 k Transaction Summary Upgrade 6 Packages Skip 12 Packages So if I then try sudo qubes-dom0-update --best --allowerasing I get this error: "The operation would result in removing the following protected packages: qubes-core-dom0, dnf." /Sven -- public key: https://www.svensemmler.org/0x8F541FB6.asc fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/aa34f007-c4ad-749f-9457-5570c302a2b6%40SvenSemmler.org. OpenPGP_signature Description: OpenPGP digital signature
