Fedora Account System
Red Hat Associate
Red Hat Customer
Hello, Please note that this comment was generated automatically by https://forge.fedoraproject.org/releng/tooling/src/branch/main/release-process/bug-filing/follow-policy/follow_policy.py If you feel that this output has mistakes, please open an issue at https://forge.fedoraproject.org/releng/tickets/issues Your package (python-vcstool) Fails To Install in Fedora 45: can't install python3-vcstool: - nothing provides python3.14dist(setuptools) needed by python3-vcstool-0.3.0-16.fc44.noarch - nothing provides python3.14dist(pyyaml) needed by python3-vcstool-0.3.0-16.fc44.noarch - nothing provides python(abi) = 3.14 needed by python3-vcstool-0.3.0-16.fc44.noarch If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock: $ mock -r fedora-45-x86_64 --config-opts mirrored=False install python3-vcstool P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages Thanks!
Hello, Please note that this comment was generated automatically by https://forge.fedoraproject.org/releng/tooling/src/branch/main/release-process/bug-filing/follow-policy/follow_policy.py If you feel that this output has mistakes, please open an issue at https://forge.fedoraproject.org/releng/tickets/issues This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 7+ weeks. This is the first reminder (step 3) from the policy. Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.
This is failing to build because of a use of pkg_resources which was removed in 3.15, I think. We hit this in the test suite: stdout = b'Traceback (most recent call last):\n File "/builddir/build/BUILD/python-vcstool-0.3.0-build/vcstool-0.3.0/scripts/v... in <module>\n from pkg_resources import load_entry_point\nModuleNotFoundError: No module named \'pkg_resources\'\n'
Sorry, it was removed from setuptools in 82. There's an upstream issue - https://github.com/dirk-thomas/vcstool/issues/292 - which refers to a "friendly fork" - https://github.com/ros-infrastructure/vcs2l . We could possibly switch to that, I guess. Note this issue prevents the Robotics spin from building.
Note that there is a PR https://github.com/dirk-thomas/vcstool/pull/288 : this rescues python3.15 pkg_resources removal. As Adam says, currrently this prevents Robotics LiveSpin compose: https://koji.fedoraproject.org/koji/taskinfo?taskID=147297268
That looks sane, so I'll just go ahead and backport it, since this has been open for some time.
FTR we opened https://src.fedoraproject.org/rpms/python-vcstool/pull-request/2 2 months ago. Obviously, https://github.com/dirk-thomas/vcstool/pull/288 is a better solution. But either way, wouldn't it make more sense to let this be orphaned instead?
yeah, I saw the downstream PR but like the upstream one more. orphaning it is a possibility, but we need to look at the dep chain(s) on affected image(s) and see if they're important enough that it'd be better to save the package.
OK, it looks like it's just directly included in robotics suite (and nothing else), and it's not really fundamental to robotics, so sent a PR to remove it: https://forge.fedoraproject.org/releng/fedora-comps/pulls/1296
Hello, Please note that this comment was generated automatically by https://forge.fedoraproject.org/releng/tooling/src/branch/main/release-process/bug-filing/follow-policy/follow_policy.py If you feel that this output has mistakes, please open an issue at https://forge.fedoraproject.org/releng/tickets/issues This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 4+ weeks. This is the second reminder (step 4) from the policy. Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.