Upgrade qtox to version 1.18.4

[nickolay168]

Hi, @sergiomb2,
The new version of qTox was released several days ago. Could you please review the spec-changing PR?

[sergiomb2]

Do you want to become a contributor to RPM Fusion? I can add you to the committers group so you’ll have permissions to update the package yourself.

You’ll need to follow the guidelines at https://rpmfusion.org/Contributors#Contributing_to_RPM_Fusion
, specifically the “Becoming a RPM Fusion contributor” section.

[sergiomb2]

Merged and built on Fedora 44+.

Which branches should be updated?

[nickolay168]

Merged and built on Fedora 44+.

Which branches should be updated?

I think, we need to merge it also into 42 and 43 branch.
Created two corresponding PRs:
Fedora 43
Fedora 42

Thank you!

[nickolay168]

Do you want to become a contributor to RPM Fusion? I can add you to the committers group so you’ll have permissions to update the package yourself.

You’ll need to follow the guidelines at https://rpmfusion.org/Contributors#Contributing_to_RPM_Fusion , specifically the “Becoming a RPM Fusion contributor” section.

Sure! I have created the account nick975 (as mentioned in the PRs) I have created a thread with introduction.

[sergiomb2]

you have created account nick974

[sergiomb2]

I think you need to login at https://admin.rpmfusion.org/pkgdb/
to have an account there. I’ve already sponsored you as a packager on RPMFusion.

Once your user appears in the pkgdb application, I may add you as the maintainer of qTox.

[nickolay168]

I think you need to login at https://admin.rpmfusion.org/pkgdb/ to have an account there. I’ve already sponsored you as a packager on RPMFusion.

Once your user appears in the pkgdb application, I may add you as the maintainer of qTox.

I have logged in https://admin.rpmfusion.org/pkgdb/ as nick974 (though in the mailing lists I have nick975 account). Should I request an access there? It looks like There are some ACL-s on the package page.

[sergiomb2]

After that, if it still does not work, try adding your SSH keys.

We noticed that you do not have any public SSH key configured in your account. Having a public SSH key set is mandatory to get access to our Git packages, so that may be the reason for the issue.

[nickolay168]

After that, if it still does not work, try adding your SSH keys.

We noticed that you do not have any public SSH key configured in your account. Having a public SSH key set is mandatory to get access to our Git packages, so that may be the reason for the issue.

I have added my rsa key to the profile, but still cannot clone the repository yet:

rfpkg clone free/qtox
# notebk@pkgs.rpmfusion.org: Permission denied (publickey).

Does it needs to be registered elsewhere?

[sergiomb2]

Does it needs to be registered elsewhere?

No. As you can see at https://admin.rpmfusion.org/pkgdb/package/free/qtox/ you are now Package Administrator of qTox.
Your user has finally appeared in the https://admin.rpmfusion.org/pkgdb, and we were able to grant you the required permissions.
Based on the timestamps in the logs, when you wrote your last comment we had not granted you the permissions yet.
Let me know if it’s working now.

[nickolay168]

Does it needs to be registered elsewhere?

No. As you can see at https://admin.rpmfusion.org/pkgdb/package/free/qtox/ you are now Package Administrator of qTox. Your user has finally appeared in the https://admin.rpmfusion.org/pkgdb, and we were able to grant you the required permissions. Based on the timestamps in the logs, when you wrote your last comment we had not granted you the permissions yet. Let me know if it’s working now.

Thank you! I think, I can now push the changes. I will look more into building tomorrow. Does the koji server require the same credentials as pkgdb?

[nickolay168]

The build fails with the error "BuildrootError: could not init mock buildroot, mock exited with status 30; see root.log for more information", however, I cannot get to web interface to see if root.log contains more information. Do I need to have a permission to run builds or to access koji?

[sergiomb2]

No, you already have all the permissions required to build RPM Fusion packages, Koji access is rpmfusion (both pass and login)

About the mock error 30, I will add an entry about it to the FAQ.

Unfortunately, it is quite common for builds to fail with mock error 30
because the Fedora repositories have been updated while the RPM Fusion ones
have not. To fix this, it is necessary to run koji-rpmfusion regen-repo <target>, for example f42-free-build. However, only Koji administrators have
the privileges to do this.

The issue is a bit annoying. The kojira service should handle this, but it
fails quite often. Recently I have been improving a script using python3-koji
to monitor builds that fail for this reason and perform the required tasks:
running the repo regeneration for the affected target and, once the repository
is updated, resubmitting the build.

[nickolay168]

Thank you! I was worried, it has been caused some unforeseen dependency issues.