[bug] Cannot install boost/1.69.0 RelWithDebInfo

Cannot install boost/1.69.0 RelWithDebInfo, Conan is failing to resolve dependencies and after explicitly trying to resolve the dependency conan is still failing.

This just started happening today. This seemed to work as of May 21 at 7AM and then starting at occuring at 8:30AM. I have no idea why…

Environment Details (include every applicable attribute)

• Operating System+version: Ubuntu 20.04
• Compiler+version: gcc9
• Conan version: conan 1.36.0
• Python version: N/A

Steps to reproduce (Include if Applicable)

1. install conan 1.36.0 from https://conan.io/downloads.html
2. create a conanfile.txt which contains:

[generators]
cmake

[requires]
boost/1.69.0

[options]
boost:shared=False
boost:fPIC=True

1. run

/bin/conan install . -s build_type=RelWithDebInfo -s compiler=gcc -s compiler.version=9 -s compiler.libcxx=libstdc++11 -s boost:compiler=gcc -s boost:compiler.version=9 -s boost:compiler.libcxx=libstdc++11 -g=cmake --build=missing

This fails with:

ERROR: Conflict in automake/1.16.3:
    'automake/1.16.3' requires 'autoconf/2.71' while 'libbacktrace/cci.20210118' requires 'autoconf/2.69'.
    To fix this conflict you need to override the package 'autoconf' in your root package.

1. Update the conanfile.txt to:

[generators]
cmake

[requires]
boost/1.69.0
autoconf/2.71

[options]
boost:shared=False
boost:fPIC=True

1. This still fails with the error

ERROR: Conflict in automake/1.16.3:
    'automake/1.16.3' requires 'autoconf/2.71' while 'libbacktrace/cci.20210118' requires 'autoconf/2.69'.
    To fix this conflict you need to override the package 'autoconf' in your root package.

Note that for whatever reason debug and release build types works fine

[SSE4]

yes, this unfortunately happens from time to time on CCI, as we are starting to have more complex dependency graphs and then we need to update some version used in multiple nodes of the graph. right now we don’t have an automated process to bump all the graph at once, and we need to submit N PRs to bump versions in N nodes of graph. as an example (simplified):

boost
├── libunwind
│   └── autoconf/2.69
└── libbacktrace
    └── autoconf/2.69

now, as soon as new version autoconf/1.71 is available, you have to update two nodes - libunwind and libbacktrace. unfortunately, we don’t have any tool to make such update in one shot for all nodes, so we make two PRs for libunwind and libbacktrace, which are reviewed and merged separately. as a result you may have an inconsistent intermediate graphs like:

boost
├── libunwind
│   └── autoconf/2.71
└── libbacktrace
    └── autoconf/2.69

which causes some conflicts.

[memsharded]

I assume there will be a profile for every build type, release, debug. asan, tsan, etc?

It depends, it is possible to have profiles for most of the settings, but you can always override individual settings on the command line. So for a profile that has build_type=Release you can do:

conan install . -pr=myprofile  # release
conan install . -pr=myprofile -s build_type=Debug  # debug

And that can avoid combinatoric of profile files. You can also do composition and inclusion of profiles if necessary.