So I saw that the rpm-ostreed-automatic.service was failing so I manually tried to upgrade but when i run rpm-ostree upgrade, I am getting an error Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: A signature was required, but no signature exists. Is this some error at my side or is this some key related issue at uBlue’s side?

    • Sentau@discuss.tchncs.deOP
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 month ago

      Yeah I think it is. Especially because the error got resolved on its own. Thanks

      What’s weird is that I did not run into these results when I searched for the error. What search engine do you use¿?

      • j0rge@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        This was a server issue, you can always report an issue in github and we’ll take a look, it took 10m to fix. But crucially it found an edge case that we hadn’t accounted for and haven’t run into so far, so we’ll work on making sure this won’t happen again: https://github.com/ublue-os/main/issues/643

        • Sentau@discuss.tchncs.deOP
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          1 month ago

          Cheers man. Thank you for all your hard work on uBlue and all the images. You are doing amazing work.

          I would have reported it but I wasn’t sure whether it was a local issue or a server issue and didn’t want to burden you with an issue without the proper information. Also no worries bugs happen and I have seen no group or organisation react as openly and promptly to bugs as you people do. I hope that sometime in the future, you open donations for uBlue so that people like me who can’t code can show our appreciation for this incredible project

      • thayerw@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        I used DDG for the first link, but then searched Google with a portion of the error message in quotes. Either way, I’m glad it sorted itself out!