Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

install fails on Fedora 39+ #3008

Open
FBachofner opened this issue Apr 15, 2024 · 16 comments
Open

install fails on Fedora 39+ #3008

FBachofner opened this issue Apr 15, 2024 · 16 comments

Comments

@FBachofner
Copy link
Contributor

Ever since moving from Linux Mint to Fedora 39 (and in one case F40, beta) I can not get QOwnNotes to install.

I follow the either of the detailed instruction options (i.e. "config-manager" or "legacy"), attempt to install and promptly get an error message.

The error message begins:

error: Verifying a signature using certificate F2205FB121DF142B31450865A3BA514562A835DB (home:pbek OBS Project home:pbek@build.opensuse.org):

  1. Certificiate A3BA514562A835DB invalid: certificate is not alive
    because: The primary key is not live
    because: Expired on 2023-12-05T16:47:00Z
  2. Key A3BA514562A835DB invalid: key is not alive
    because: The primary key is not live
    because: Expired on 2023-12-05T16:47:00Z

This is followed by an apparently identical 2nd message (one seems to be for "qownnotes" the other for "qt5-qtwebsockets" )

Thanks in advance for ideas/help. In the meantime we have QON running as an appimage, but that is suboptimal due to concerns with staying updated.

Flatpak and (especially) Snap versions are not of interest to any of my users.

@pbek
Copy link
Owner

pbek commented Apr 15, 2024

The Fedora builds are done on opensuse build service (OBS). Usually people remove and add the certificate again if there are problems.

@FBachofner
Copy link
Contributor Author

FBachofner commented Apr 24, 2024

Hello @pbek

I have this sorted on at least one upgraded F40 (Cinnamon DE) host.

Your instructions should ideally be updated to point out that the "TIP" -- "accept the repo key" instructions and "legacy" installs NOT necessarily use the folder with "Fedora_36" in the name but rather explicitly point out the user input the version of Fedora s/he is using. [ I accidentally glossed over this in my rush to get QOwnNotes working earlier. ]

Also, you will need to publish a Fedora 40 repository considering F40 was released today. As a consequence of the update, all "variable"-based paths such as http://download.opensuse.org/repositories/home:/pbek:/QOwnNotes/Fedora_\$releasever do not currently resolve correctly.

Thanks for your excellent ongoing work with QOwnNotes! :-)

@pbek
Copy link
Owner

pbek commented Apr 24, 2024

Would you care to suggest changes in a pull request, @FBachofner? I have not much experience with the ins and outs of Fedora. 😉

@FBachofner
Copy link
Contributor Author

Hello @pbek

I would be glad to attempt this on the upcoming weekend Patrizio.

Beyond entering and responding to issues, I have precious little knowledge of how Github works, so it will be a learning experience!

Can a page be edited right in the browser or will I have to clone all or part of the repository to one of my machines?

@FBachofner
Copy link
Contributor Author

FBachofner commented Apr 24, 2024

Hi @pbek

Well, I decided I had a few moments and thus made the pull request right now as opposed to waiting for the weekend. It was remarkably straightforward to "fork" the project, edit fedora.md (from the website folder) in the browser and make the pull request.

I have only suggested very minor edits, but if you incorporate them you will definitely need to create the Fedora_40 repository (i.e. https://download.opensuse.org/repositories/home:/pbek:/QOwnNotes/Fedora_/ ) so the links resolve properly.

@pbek
Copy link
Owner

pbek commented Apr 25, 2024

Thank you!
Fedora 40 finally showed up on OBS! I've now added it too.

@pbek
Copy link
Owner

pbek commented Apr 25, 2024

I guess we can close this now, can we?

@pbek pbek closed this as completed Apr 25, 2024
@FBachofner
Copy link
Contributor Author

Hi @pbek

I guess we can close this now, can we?

Sorry, no.

I just uninstalled QOwnNotes 24.3 and performed various other system cleanup tasks.

Then: sudo dnf install qownnotes which I expected would install 24.4

Result:

The GPG keys listed for the "repository for QOwnNotes (Fedora 40 - x86_64)" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.. Failing package is: qownnotes-24.4.4-1.1.x86_64
GPG Keys are configured as: http://download.opensuse.org/repositories/home:/pbek:/QOwnNotes/Fedora_40/repodata/repomd.xml.key

@pbek
Copy link
Owner

pbek commented Apr 25, 2024

Dunno, what are Fedora people doing in that case? 😊
Remove the old key and add the new? ️🤷🏻
Key-management is done by OBS directly. I don't create the keys.

@pbek pbek reopened this Apr 25, 2024
@pbek
Copy link
Owner

pbek commented Apr 25, 2024

Does this also happen on a fresh installation of Fedora?

@FBachofner
Copy link
Contributor Author

FBachofner commented Apr 25, 2024

Hi @pbek

Remove the old key and add the new? ️🤷🏻 Key-management is done by OBS directly. I don't create the keys.

I would if I could! ;-)

The key(s) is(are) not found anywhere in the "passwords and keys" app. gpg --list-keys also shows nothing. Same thing with gpg --list-secret-keys

This is an enigma to me.

@pbek
Copy link
Owner

pbek commented Apr 26, 2024

This is what GPT-4 said 😊 :

The error message indicates that the GPG keys already installed on your system do not match the ones required for validating the QOwnNotes package you're attempting to install. This mismatch can happen for various reasons, such as an outdated key or a recent change in the repository's security setup.

Follow these steps to resolve the issue:

1. Remove the existing GPG key

First, you may want to remove the existing, incorrect GPG key to avoid conflicts. However, finding and removing the exact key can be tricky, especially for beginners. If you're sure about which key to remove and its impact, you could use the rpm command to delete it, otherwise, it might be safer to proceed to the next steps, as adding the correct key should not be interfered with by the presence of the old one in many cases.

2. Import the new GPG key

You can manually import the correct GPG key for the QOwnNotes repository. The error message you provided contains the URL for the key. You can import this key using sudo rpm --import [KEY_URL], replacing [KEY_URL] with the actual URL.

In your case, you would run:

sudo rpm --import http://download.opensuse.org/repositories/home:/pbek:/QOwnNotes/Fedora_40/repodata/repomd.xml.key

3. Clean DNF cache

Sometimes, your system's package manager cache can cause issues. Cleaning the cache can ensure that your system fetches the latest metadata from repositories. You can clean the DNF cache with the following command:

sudo dnf clean all

4. Try installing QOwnNotes again

Now that you have imported the correct GPG key and cleaned the cache, try installing QOwnNotes again:

sudo dnf install qownnotes

If you still encounter issues, there might be additional problems with the repository configuration or with the package itself. In such cases, consider checking the official QOwnNotes installation instructions for Fedora or seeking support from the QOwnNotes community. It’s also worth ensuring that your system is fully updated (sudo dnf update) in ca

@FBachofner
Copy link
Contributor Author

Hi @pbek

Thanks for your efforts. I had tried all these things. The real problem seems to be that the wrong key is installed, but there is no way to see it and (therefore) no way to remove it.

I'll ask about this on one of the Fedora forums in a moment. Hopefully I can get help from someone with more expertise in Fedora than I seem to have.

I'll report back soon.

@pbek
Copy link
Owner

pbek commented Apr 26, 2024

Or maybe it's a problem with OBS? 🤔

@FBachofner
Copy link
Contributor Author

Hi @pbek

When you say OBS, do you somehow mean https://obsproject.com/ ? I don't have that on any machines currently . . .

I got interrupted last week and hope to finally inquire on the forums this weekend regarding expired keys which don't show up anywhere I expect to find them.

@pbek
Copy link
Owner

pbek commented May 4, 2024

No, it's open build service, the repository you are downloading from 😁
https://openbuildservice.org/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants