Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libproxy: add libproxy/0.4.15 recipe #2866

Closed
wants to merge 2 commits into from

Conversation

madebr
Copy link
Contributor

@madebr madebr commented Sep 9, 2020

Specify library name and version: libproxy/0.4.15


  • I've read the guidelines for contributing.
  • I've followed the PEP8 style guides for Python code in the recipes.
  • I've used the latest Conan client version.
  • I've tried at least one configuration locally with the
    conan-center hook activated.

@conan-center-bot
Copy link
Collaborator

Failure in build 1 (28f078e9285983d66be29ff24ceb56866817dee6):

  • libproxy/0.4.15
    • Hooks errors detected:
      • [HOOK - conan-center.py] pre_export(): ERROR: [CMAKE VERBOSE MAKEFILE (KB-H046)] The CMake definition 'set(CMAKE_VERBOSE_MAKEFILE ON)' is not allowed. Remove it from recipes/libproxy/all/test_package/CMakeLists.txt. (https://github.com/conan-io/conan-center-index/blob/master/docs/error_knowledge_base.md#KB-H046)
      • [HOOK - conan-center.py] pre_export(): ERROR: [CMAKE VERSION REQUIRED (KB-H048)] The test_packages/CMakeLists.txt requires CMake 3.1 at least. Update to 'cmake_minimum_required(VERSION 3.1)'. (https://github.com/conan-io/conan-center-index/blob/master/docs/error_knowledge_base.md#KB-H048)

@conan-center-bot
Copy link
Collaborator

Failure in build 2 (7b74c6399c1d91fd0ee2bd0c072b404b9d37838d):

  • Error processing recipe (ref 'libproxy/0.4.15'): Linux x86_64, Release, gcc 4.9, libstdc++ . Options: libproxy:shared-False
    You are depending on 'libmodman/2.0.1' but it is not in the repository

@stale
Copy link

stale bot commented Dec 1, 2020

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Dec 1, 2020
@Croydon
Copy link
Contributor

Croydon commented Dec 1, 2020

@SSE4 Would the bot ignore this PR if this would have been marked as a draft? It is blocked by another PR

@stale stale bot removed the stale label Dec 1, 2020
@uilianries
Copy link
Member

It's a good opportunity to re-visit the cause of blocking. Even for drafts, we can look what is missing and offer support.

@stale
Copy link

stale bot commented Dec 31, 2020

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Dec 31, 2020
@stale
Copy link

stale bot commented Jan 30, 2021

This pull request has been automatically closed because it has not had recent activity. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants