FS#71246 - [snappy] stale version in pkgconfig file

Attached to Project: Arch Linux
Opened by George Rawlinson (rawlinsong) - Sunday, 13 June 2021, 09:43 GMT
Last edited by David Runge (dvzrv) - Monday, 04 September 2023, 01:00 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Anatol Pomozov (anatolik)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

The pkgconfig file (snappy.pc) states version is 1.1.4, not sure if this is intended or not.

The correct version could be set using sed in prepare().
This task depends upon

Closed by  David Runge (dvzrv)
Monday, 04 September 2023, 01:00 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with snappy 1.1.9-2
Comment by Biswapriyo Nath (Biswa96) - Saturday, 04 September 2021, 05:25 GMT
I have fixed the issue with a patch file and a pkgconfig input file (snappy.pc.in). The patch file adds configure_file() in CMakeLists.txt to generate the pkgconfig file and install() to install it. Here are the two files attached.
Comment by Anatol Pomozov (anatolik) - Tuesday, 07 September 2021, 11:38 GMT
@Biswapriyo had you chance to send your patches upstream? It would be beneficial to other distros to have snappy.pc in the upstream source tree.
Comment by Biswapriyo Nath (Biswa96) - Tuesday, 07 September 2021, 13:32 GMT
No. Because the PKGBUILD already says "upstream dropped the pkgconfig file and isn't interested in adding it back".
Comment by Anatol Pomozov (anatolik) - Tuesday, 07 September 2021, 23:44 GMT
Thanks, the patch has been added at SVN 423515. Please test current master and let me know if it works for you.
Comment by George Rawlinson (rawlinsong) - Wednesday, 08 September 2021, 01:55 GMT
LGTM. Just signed off the package in testing.
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...