conan-center-index: [package] clipper/4.10.0: Error in source() method
Package and Environment Details
- Package Name/Version: clipper/4.10.0
- Operating System+version: Linux Ubuntu 20.04.4 LTS and Microsoft Windows Server 2022 10.0.20348 Datacenter
- Compiler+version: Clang 13
- Conan version: conan 1.51.0
Conan profile
I use the default profile.
Steps to reproduce
- My Conanfile->assimp->cliper.
- Run script, Full github workflow file.
I have tried to run the workflow again, but the problem still exists. This problem has not occurred before.
Logs
Click to expand log
Ubuntu:
WARN: Remotes registry file missing, creating default one in /home/runner/.conan/remotes.json
WARN: imguizmo/cci.20210223: requirement imgui/1.82 overridden by your conanfile to imgui/cci.20220621+1.88.docking
ERROR: clipper/4.10.0: Error in source() method, line 50
tools.get(**self.conan_data["sources"][self.version], destination=self._source_subfolder)
NotFoundException: Not found: https://sourceforge.net/projects/polyclipping/files/Older%20versions/clipper_ver4.10.0.zip
Windows:
WARN: Remotes registry file missing, creating default one in C:\Users\runneradmin\.conan\remotes.json
WARN: imguizmo/cci.20210223: requirement imgui/1.82 overridden by your conanfile to imgui/cci.20220621+1.88.docking
-- Compiler is not EMSCRIPTEN
CMake Warning:
Manually-specified variables were not used by the project:
CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMake Warning:
Manually-specified variables were not used by the project:
CMAKE_EXPORT_NO_PACKAGE_REGISTRY
ERROR: clipper/4.10.0: Error in source() method, line 50
tools.get(**self.conan_data["sources"][self.version], destination=self._source_subfolder)
NotFoundException: Not found: https://sourceforge.net/projects/polyclipping/files/Older%20versions/clipper_ver4.10.0.zip
Full workflow log files:
- Ubuntu: logs_1892.zip.
- Windows: logs_1893.zip.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 24 (19 by maintainers)
There is still an issue in 5.1.6, source code is different than previous tarball downloaded by conan-center: https://github.com/conan-io/conan-center-index/pull/13530#issuecomment-1280072668
I had a closely related issue, so I’m posting the workaround here for anyone else who might stumble upon it.
The root cause is that I still had a bad clipper package in local cache. I had to purge that with
conan removebefore I could benefit from the fix discussed here.Thanks for the fix!
Should be solved now. Ping if not! 😃
Yeah, maybe the old 5.1.6 zip wasn’t from the same revision that I pulled (it wasn’t explicitly tagged, so I made an educated guess based on contents and commit comment). So, to get 5.1.6 back the conan recipe and/or the zip needs to be tweaked further, but I don’t know how to proceed, and 4.10.0 is what assimp needs, so I’m happy with getting that running.
Someone added the 5.1.6 support to conan, so at onetime, someone was using that.
The SHA256 of my zip doesn’t match the one in conan’s recipe index, so I’ve resurrected my PR and am waiting for build access.
Thanks a lot, @AngusJohnson. Just adding some background about ConanCenter: here we are building the binaries using an internal CI so, every time there is a change in the Conan recipe we need to recreate all the binaries again (the recipe might be modifying the build systems and binaries might change even if it is a small change), hence we need to retrieve the sources to build the binaries again. Of course, we are allowed to remove old versions (just from this repo, not from ConanCenter itself) when they are superseded by new versions. Some users are also building always their binaries from sources, they can’t consume pre-created binaries, so sources have to be accessible to them.
We know that the only way to guarantee that sources will always be there is to mirror them ourselves internally, it is a development we’ve been thinking about several times, but we’ve never started implementing, there is always something more important or with higher priority. I’m sure it will popup again this time, and probably the migration to v2 will grab all our attention 😞 So far, this situation doesn’t happen too often.
As soon as you upload those sources again, we will prepare a PR to fix our recipe.
Thanks!
OK, it’s there now (but may take time to propagate around SF servers).
Btw, no worries @AngusJohnson 😃 I’m not sure you had any way of knowing, and thanks for your time.
Packages/recipe won’t be removed from CCI, so consumers will keep working (only for existing configurations aka package-ids). The problem is that we won’t be able to build that reference from sources and consumers will be blocked if we create a PR that triggers new configurations 🧨
If we manage to get the sources from those versions, we can store them as we do with
gsoap(check https://github.com/conan-io/conan-center-index/blob/master/recipes/gsoap/all/conandata.yml) so everything keeps working.So please, @ShenMian , if you manage to talk with the library maintainer, it would be great to restore those files.
https://sourceforge.net/p/polyclipping/bugs/214/
assimp depends on clipper 4.x only, therefore 4.10.0 can’t be removed in cci.