-
Notifications
You must be signed in to change notification settings - Fork 239
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
python2.7, python3.6 and python3.8 still in ELN #162
Comments
Two answers. First - marking something as unwanted does not automatically remove it. It marks it as unwanted. Second - You have shown me I have a bug in my buildroot-generator script. |
Yes, I am aware of that. That's why I've said (in the email thread):
I am not sure I follow what "duplicate packages" means here.
As build dependencies of what packages? https://tiny.distro.builders/view-unwanted--view-eln--x86_64.html doesn't show python3.6 and python3.8 as depended on. |
That page shows:
So that seems like it's reporting that we're no longer including it in the list. That said, clearly it's still getting picked up by the rebuild automation, so that's a bug. |
Sorry, I guess I should have linked to the content with the buildroot. It's the buildroot dependencies that are pulling them in. |
I don't see how python3-devel or python3-setuptools is related. They are not provided by |
For completeness:
|
If repoquery worked without problems, I'd be using it. It doesn't. But I've had to re-write "dnf builddep" so that it will run without having to install. dnf builddep python-ldap You'll see that it tries to install all the python3.* |
Oh. It has to do with recommends. Tox recommends all the pythons. |
So, it looks like somewhere in all my edits, I dropped my "...install_weak_deps = False" line. I am putting the script into the pipeline, but it takes a while for everything to funnel through. So, hopefully tomorrow Content Resolver will have them dropped, and they will come out of ELN shortly after that. |
So, apparently also python3.7, python3.5, pypy and pypy3 is built for ELN. I'll make sure to mark them as unwanted. |
My code fix worked, and the resulting buildroot has gone through the Content Resolver.. |
python2.7 is still in ELN, but it is pulled into it by some dependents. The other packages are not. |
Hey ELN people.
Despite my efforts to block python2.7, python3.6 and python3.8 from ELN, I still see that the packages are built there.
Could you please help me understand what needs to be done to prevent that from happening?
I've tried to communicate this in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/U4TY26R3S65E474FUKGKB6H4JOCIEITY/ but there was no useful info except one private reply by @sgallagher who suggested that the proper communication channel for this are PRs in this repo.
The relevant PRs were:
Later moved around by #68.
The text was updated successfully, but these errors were encountered: