Re: How to figure out why is Python 2 in critpath

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 25. 10. 19 16:54, Adam Williamson wrote:
On Fri, 2019-10-25 at 13:58 +0200, Miro Hrončok wrote:

The critpath.py script from the same place is quite more interesting, as it
actually resolves the critpath on various architectures instead of querying an
API where I already know python2 is listed in.

With this patch: https://pagure.io/releng/pull-request/8935

   $ python3 critpath.py --dnf branched

does not add python2 for any of the following architectures:

1145 packages for armhfp/armv7hl
1156 packages for aarch64
1176 packages for x86_64
1210 packages for ppc64le
1198 packages for s390x

I believe the background here is simply that generating the critical
path has been broken for ages, so fixing that is probably the way to
go. (And will mean all the critpath changes I did in comps finally
actually kick in, so yay for that...)

If those releng scripts are used for this, the PR might actually fix the problem.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux