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
[WIP] oslo-config: 4.13.2 -> 5.1.0 #32602
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
propagatedBuildInputs = [ pbr six pyyaml appdirs stevedore GitPython git ]; | ||
checkInputs = [ beautifulsoup4 oslosphinx testtools testscenarios | ||
testrepository fixtures mock ]; | ||
patchPhase = '' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
postPatch
is preferred so that one can still pass in patches
.
|
i am currently on it, i will have to bump a number of libs to get it running. changing Headline to WIP |
oh oh, it seems that bumping pyasn1 was not the wisest thing to do. it was for getting ldap to the latest version ... i will see how much stuff breaks with this. |
ec58565
to
7311f4c
Compare
can this PR be submitted to hydra for evaluation? i am afraid my pc is not hardcore enough to evaludate the PR in time. if it is not possible then i will probably have to revert and wait for pyasn1 be bumped by someone more adventurous than me. edit ok i will give up trying to bump ldap and pyasn1. i will keep put this in a separate PR |
7311f4c
to
be85337
Compare
5baadab
to
be85337
Compare
for python3Packages.oslo-config i get
however the package is building for |
That typically happens when Python 2 and 3 packages get mixed during a build. Both packages have the interpreter in |
When disabling tests, can you refer to the previous comment. |
@FRidh i think the package is update: yep it is the |
@makefu if its just an application, and we're not interested in the modules, then no, then its not the correct way to pull it into The correct way, but out of scope here, is to make sure Python applications don't show their |
fix cyclic dependency with fixtures by disabling checkPhase in fixtures
57aff7a
to
d1de6c1
Compare
d1de6c1
to
de05536
Compare
so many broken packages ... is it possible with |
A lot of (older) packages have an
Absolutely. Many of the packages you touch haven't been used in a while. It may therefore also be wise to evaluate whether they could instead be dropped. I would prefer to move this whole |
c146f33
to
d73a9bf
Compare
Moving What i could think of is using Edit: i just remembered why i started this in first place, which is |
Won't help, because we need a coherent set that works for Python 2.7, 3.4, 3.5, 3.6 and preferably also PyPI. With But I thought that certain openstack libraries were already marked as broken, so I wouldn't imagine you having to upgrade them then. |
Thing is, that the update resulted in more dependencies which resulted in new errors (and more update) and more dependencies. a never ending cycle. Regarding the overlay, i think only a single python version would be enough to provide the functionality of openstack. This however would not solve the issue if people would actually want to use certain libraries in their project. imho each module should come with a huge warning sign if it pulls dependencies from openstack ... |
Motivation for this change
bump oslo-config to 5.1.0 and enable tests 💯
For enabling tests i had to bump:
Waiting for @GrahamcOfBorg :3
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)