Changed package requirements to include distro version 1.5.0

[DominikDeak]

Changelog: Fix: Changed requirements.txt to include distro package version 1.5.0.
Docs: Omit

Close #7455

• Refer to the issue that supports this Pull Request.
• If the issue has missing info, explain the purpose/use case/pain/need that covers this Pull Request.
• I've read the Contributing guide.
• I've followed the PEP8 style guides for Python code.
• I've opened another PR in the Conan docs repo to the develop branch, documenting this one.

^{Note: By default this PR will skip the slower tests and will use a limited set of python versions. Check here how to increase the testing level by writing some tags in the current PR body text.}

[CLAassistant]

All committers have signed the CLA.

[uilianries]

Hi @DominikDeak ! Thanks for your contribution! Could you please sign the CLA.

[jgsogo]

Hi! We need a policy for this kind of external dependencies. Changing the version can change the output of some Conan autodetect features. This is very related to the compiler detection @SSE4 implemented, almost same situation.

I agree to update this library, but maybe we should add a disclaimer to the docs associated with the affected functions to tell the users that we are using distro under the hood and, depending on the version used, the results can be different. If this is not ok, then we shouldn't add a range for these dependencies, but a fixed version.

We need to be aligned, wdyt @conan-io/barbarians ?

[uilianries]

depending on the version used, the results can be different

@jgsogo why not improving our regression tests instead? So we can predict any change from external packages.

[jgsogo]

depending on the version used, the results can be different

@jgsogo why not improving our regression tests instead? So we can predict any change from external packages.

Same problem as with the compiler detection, how many different docker images we need to run? How many different OS x platforms x ...? And those docker images... are they available or do we need to maintain them ourselves?

[memsharded]

I think we should work with this ideas in mind:

• Try to minimize the external dependencies and surface area. Embed when possible. Delegate to the user space when possible. Fork under different name when it makes sense. In general be more aware when introducing dependencies.

• Testing is indeed difficult. We will never cover all the cases with enough confidence, as the space is huge.

• Agree that it is necessary to document it correctly in the docs. I lean to accepting the range and documenting than being strict on the range and having users complaining because of conflicting distro versions.

[jgsogo]

I'm adding a warning to the docs here (almost a disclaimer)