-
Notifications
You must be signed in to change notification settings - Fork 47
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
uReport fails with a package version mismatching the expected regex #1025
Comments
Thanks for the bug report. I think this is a bug in faf as @mgrabovsky Do you know if simply adding the caret character to the regex here would be enough to fix this issue? |
@msrb From a quick glimpse, I'd say yes, that should fix the problem here. |
The [Fedora packaging guidelines][1] require a caret to be used in the version string for package snaphots. [1]: https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_snapshots Fixes #1025
The [Fedora packaging guidelines][1] require a caret to be used in the version string for package snaphots. [1]: https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_snapshots Fixes #1025
The [Fedora packaging guidelines][1] require a caret to be used in the version string for package snaphots. [1]: https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_snapshots Fixes #1025
The fix has now been deployed to retrace.fedoraproject.org. |
Thank you very much for this quick fix! I've already tested it and can confirm that it is working fine now (the exact same crash I wanted to report 3 days ago now can be reported just fine). |
When trying to report a bug on my current Fedora 37 installation, I see the following message (in GNOME Abrt):
It seems like the cause for this are the following binary packages:
which are built from the source package google-noto-fonts.
This should not happen. Either Fedora must not allow these strings as package versions (but it does, in reality) or libreport must accept this version string.
Version info:
This issue is seen by other users too, e.g. @mcatanzaro in this pagure ticket comment.
PS: I am not sure whether this is the correct place to report this issue. Please give me hints if you think this location is incorrect.
The text was updated successfully, but these errors were encountered: