Open toge opened 4 days ago
All green in build 1 (718287b98e9dffbe7604120f7111c9d5a2a6a405
):
octo-logger-cpp/1.12.0: All packages built successfully! (All logs)
octo-logger-cpp/1.5.0: All packages built successfully! (All logs)
octo-logger-cpp/1.9.0: All packages built successfully! (All logs)
octo-logger-cpp/1.4.0: All packages built successfully! (All logs)
octo-logger-cpp/1.6.1: All packages built successfully! (All logs)
octo-logger-cpp/1.2.0: All packages built successfully! (All logs)
octo-logger-cpp/1.11.0: All packages built successfully! (All logs)
octo-logger-cpp/1.1.0: All packages built successfully! (All logs)
Note: Conan v2 builds are now mandatory. Please read our discussion about it.
All green in build 1 (718287b98e9dffbe7604120f7111c9d5a2a6a405
):
octo-logger-cpp/1.12.0: All packages built successfully! (All logs)
octo-logger-cpp/1.11.0: All packages built successfully! (All logs)
octo-logger-cpp/1.2.0: All packages built successfully! (All logs)
octo-logger-cpp/1.9.0: All packages built successfully! (All logs)
octo-logger-cpp/1.6.1: All packages built successfully! (All logs)
octo-logger-cpp/1.5.0: All packages built successfully! (All logs)
octo-logger-cpp/1.4.0: All packages built successfully! (All logs)
octo-logger-cpp/1.1.0: All packages built successfully! (All logs)
Please note that it 1.12.0 does not appear to be a release yet: https://github.com/ofiriluz/octo-logger-cpp/releases
so maybe the maintainers are updating the tag until it is.
furthermore, this is the second time we have a checksum issue: https://github.com/conan-io/conan-center-index/pull/24308
I can see that this will continue being a problem until 1.12.0 is actually released. Under what conditions was 1.12.0 considered a release? The presence of the tag?
@jcar87 @RubenRBS Thank you for your deep dive.
I have updated this recipe as the 1.12.0 tag has been added. I understand that this is an inconvenient situation for cci. I will keep the use of 1.12.0 in my private environment. Is there any way to make this clear to users that it will be difficult to use 1.12.0 on cci until an official release is made?
Is there any way to make this clear to users that it will be difficult to use 1.12.0 on cci until an official release is made?
Thanks @toge ! We can probably invalidate all packages in the validate()
method and point users to use an older version? Until a new recipe revision is published that has the actual release.
Or we can publish these as 1.12.0-pre1
etc - but point to the actual commit rather than the 1.12.0 tag - but the 1.12.0
will still remain published
Any ideas @RubenRBS ??
Summary
Changes to recipe: octo-logger-cpp/1.12.0
Motivation
tar ball of 1.12.0 is updated.
Details