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#60242 - [libspatialindex] Conflict with spatialindex
Attached to Project:
Community Packages
Opened by Alex Seiler (aexl) - Saturday, 29 September 2018, 12:16 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 14 October 2018, 04:18 GMT
Opened by Alex Seiler (aexl) - Saturday, 29 September 2018, 12:16 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 14 October 2018, 04:18 GMT
|
DetailsDescription: This package seems to conflict with the package spatialindex (https://www.archlinux.org/packages/community/x86_64/spatialindex/). But the conflict is not mentioned in the PKGBUILD. Why are there two different packages of the same software?
Additional info: * spatialindex 1.8.5-2 * libspatialindex 1.8.5-1 Steps to reproduce: Assume you have spatialindex installed on your system. sudo pacman -S libspatialindex resolving dependencies... looking for conflicting packages... Packages (1) libspatialindex-1.8.5-1 Total Installed Size: 1.09 MiB :: Proceed with installation? [Y/n] (1/1) checking keys in keyring [#####################################] 100% (1/1) checking package integrity [#####################################] 100% (1/1) loading package files [#####################################] 100% (1/1) checking for file conflicts [#####################################] 100% error: failed to commit transaction (conflicting files) libspatialindex: /usr/include/spatialindex/LineSegment.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/MVRTree.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/MovingPoint.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/MovingRegion.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/Point.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/RTree.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/Region.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/SpatialIndex.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/TPRTree.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/TimePoint.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/TimeRegion.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/Version.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/BoundsQuery.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/CountVisitor.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/CustomStorage.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/DataStream.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/Error.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/IdVisitor.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/Index.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/LeafQuery.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/ObjVisitor.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/Utility.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/sidx_api.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/sidx_config.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/sidx_export.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/capi/sidx_impl.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/tools/PointerPool.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/tools/PoolPointer.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/tools/SmartPointer.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/tools/Tools.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/include/spatialindex/tools/rand48.h exists in filesystem (owned by spatialindex) libspatialindex: /usr/lib/libspatialindex.so exists in filesystem (owned by spatialindex) libspatialindex: /usr/lib/libspatialindex.so.4 exists in filesystem (owned by spatialindex) libspatialindex: /usr/lib/libspatialindex.so.4.0.1 exists in filesystem (owned by spatialindex) libspatialindex: /usr/lib/libspatialindex_c.so exists in filesystem (owned by spatialindex) libspatialindex: /usr/lib/libspatialindex_c.so.4 exists in filesystem (owned by spatialindex) libspatialindex: /usr/lib/libspatialindex_c.so.4.0.1 exists in filesystem (owned by spatialindex) libspatialindex: /usr/lib/pkgconfig/libspatialindex.pc exists in filesystem (owned by spatialindex) Errors occurred, no packages were upgraded. |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Sunday, 14 October 2018, 04:18 GMT
Reason for closing: Fixed
Additional comments about closing: package removed from repos
Sunday, 14 October 2018, 04:18 GMT
Reason for closing: Fixed
Additional comments about closing: package removed from repos
However, I guess libspatialindex should be the correct name as it's used as name more in upstream. I don't feel strong here though.
@Ballo Would like to know your suggestion here.