Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#72750 - [krb5] do not provide `libverto`
Attached to Project:
Arch Linux
Opened by Vladimir (_v_l) - Monday, 15 November 2021, 02:27 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 09 June 2022, 05:46 GMT
Opened by Vladimir (_v_l) - Monday, 15 November 2021, 02:27 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 09 June 2022, 05:46 GMT
|
DetailsInstead, use dedicated package.
I'm filling this bug report against `krb5` package though `gssproxy` is the affected one. For some time now (the first error message appeared on 9 Sep) I see following message in journal: ``` gssproxy[429]: free(): invalid pointer ``` I searched a bit and found this issue: https://github.com/gssapi/gssproxy/issues/36. According to comment there, they advise to use dedicated `libverto` package instead of using one from `krb5`. |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Thursday, 09 June 2022, 05:46 GMT
Reason for closing: Fixed
Additional comments about closing: libverto package has been added.
Thursday, 09 June 2022, 05:46 GMT
Reason for closing: Fixed
Additional comments about closing: libverto package has been added.
I removed the builtin libverto and rebuilt krb5 and gssproxy against it.
The crash is gone.
Updated krb5 to 1.20 and used that as a conflict condition for libverto. Adjusted krb5 and gssproxy to use libverto. I did not do create a lib32-libverto or adjust lib32-krb5.
[1] https://aur.archlinux.org/packages/libverto