Wrong install location for cmake config files on Ubuntu

[Krzmbrzl]

First off: I am not entirely sure whether this is an issue with Poco itself or only with the way it now gets packaged on recent versions of Ubuntu.

Trying to locate the Poco libraries via a regular find_package command fails starting from Ubuntu Groovy (20.10). It still works fine on Ubuntu focal (20.04).

find_package(Poco COMPONENTS Zip)

Presumably this is because in 20.04, the cmake config files are installed to e.g. /usr/lib/cmake/Poco/PocoConfig.cmake (source) whereas on 20.10, they are installed to /usr/lib/x86_64-linux-gnu/cmake/cmake/Poco/PocoConfig.cmake(source). Note the cmake/cmake part in that path, which I believe is one cmake dir too much for it to work.

Did you perhaps make any changes to the install locations that could have caused this issue or is this something the Ubuntu packagers have changed on their own?

[Bjoe]

@Krzmbrzl Right, this is the wrong directory

I must verify on which site this is going wrong....

[Bjoe]

It might be, this is the problem we set PocoConfigPackageLocation
We should not do this. The correct location is set by cmake. Cmake know on which platform it is building the project and put the config-moduls in the correct directory.
But I need to verify this. Btw. the debian package has also some interesting patches :-)

[jayvdb]

I've noted this problem in debian bugreport 1000656 along with another problem effecting Debian/Ubuntu/etc wrt cmake finding pcre.

[jspricke]

This should be fixed in 1.11.0-3 in Debian unstable. Sorry for the trouble.

[jayvdb]

@jspricke , I think the pcre problem reported in debian bugreport 1000656 is yet to be addressed. One solution is to install https://github.com/pocoproject/poco/blob/master/cmake/FindPCRE.cmake in the Poco cmake directory.

Also https://packages.debian.org/sid/libpoco-dev is still showing 1.11.0-2, containing the double cmake/cmake path in /usr/lib/x86_64-linux-gnu/cmake/cmake/Poco. Is that because of the pipeline failure at https://salsa.debian.org/debian/poco/-/pipelines/318257 , or just a usual delay in the new release propagating to all the various systems?

[jspricke]

***@***.*** , I think the pcre problem reported in [debian bugreport 1000656](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000656) is yet to be addressed. One solution is to install https://github.com/pocoproject/poco/blob/master/cmake/FindPCRE.cmake in the Poco cmake directory. It was addressed in the upload.

Also https://packages.debian.org/sid/libpoco-dev is still showing `1.11.0-2`, containing the double cmake/cmake path in `/usr/lib/x86_64-linux-gnu/cmake/cmake/Poco`.

Debian unstable is updated 4 times per day, it ran in the meantime and the page shows the new package now.

Is that because of the pipeline failure at https://salsa.debian.org/debian/poco/-/pipelines/318257 , or just a usual delay in the new release propagating to all the various systems?

CI is unrelated.

[jayvdb]

Tested. Both are now fixed! Thanks @jspricke !

[jayvdb]

Can we expect this might make it into stable(bullseye), where libpoco-dev is at 1.10.0-6?

[jspricke]

I've proposed a stable update in https://bugs.debian.org/1000736.

[jayvdb]

@jspricke , it looks like you have the green light.

[jspricke]

Yes, it was already accepted: https://release.debian.org/proposed-updates/stable.html
And will be part of the next stable release point release on the 18.: https://release.debian.org/

[jayvdb]

Thanks for the links - I'm slowly learning the debian processes ;-)

[jspricke]

Btw. as the initial bug report was for Ubuntu, maybe someone wants to fill a SRU: https://wiki.ubuntu.com/StableReleaseUpdates

[jayvdb]

Now in Debian stable and Ubuntu jammy.
I guess this can be closed now, unless this ticket also wants to track it drifting into a stable Ubuntu.