Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ Your package (python-lsp-server) Fails To Install in Fedora 39: can't install python3-lsp-server: - nothing provides python(abi) = 3.11 needed by python3-lsp-server-1.4.1-3.fc37.noarch - nothing provides python3.11dist(ujson) >= 3 needed by python3-lsp-server-1.4.1-3.fc37.noarch - nothing provides python3.11dist(pluggy) >= 1 needed by python3-lsp-server-1.4.1-3.fc37.noarch - nothing provides python3.11dist(setuptools) >= 39 needed by python3-lsp-server-1.4.1-3.fc37.noarch - nothing provides (python3.11dist(jedi) < 0.19~~ with python3.11dist(jedi) >= 0.17.2) needed by python3-lsp-server-1.4.1-3.fc37.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-39-x86_64 --config-opts mirrored=False install python3-lsp-server 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://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ 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 devel.org if you are unsure how to fix this bug.
I will try to fix this
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ 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.
*** Bug 2226235 has been marked as a duplicate of this bug. ***
I intend to orphan this package. https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org/thread/QBXLNWCN2LOFJMKCWW3KVSGFPG3WOTQY/ https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/QBXLNWCN2LOFJMKCWW3KVSGFPG3WOTQY/
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This package has been orphaned. You can pick it up at https://src.fedoraproject.org/rpms/python-lsp-server by clicking button "Take". If nobody picks it up, it will be retired and removed from a distribution.
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ 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.
We would likely want to bump to the latest version of this - 1.7.4 - but that's problematic as it needs newer versions of rope and yapf. I think bumping yapf to 0.33.0 would be simple (0.40.0 might be a bit tricker), but bumping rope is harder, because newer versions of rope require https://github.com/bagel897/pytoolconfig , which is not yet packaged for Fedora, so that will need to be added to the distro first.
(In reply to Adam Williamson from comment #11) > We would likely want to bump to the latest version of this - 1.7.4 - but > that's problematic as it needs newer versions of rope and yapf. > > I think bumping yapf to 0.33.0 would be simple (0.40.0 might be a bit > tricker), but bumping rope is harder, because newer versions of rope require > https://github.com/bagel897/pytoolconfig , which is not yet packaged for > Fedora, so that will need to be added to the distro first. I experimented with adopting python-rope and getting it up to date, ran into some test failures I did not feel like spending a lot of time on, and moved on. However, I did get python-pytoolconfig properly packaged locally, and I am happy to throw up a review request and maintain/co-maintain a python-pytoolconfig package if someone else wants to do the necessary work on python-rope.
Jonathan Wright, who took spyder (which depends on this), indicated to me in chat he wants to pick up the orphaned deps of spyder and ultimately get spyder working again, so I guess he'd be interested. Adding him to CC.
(In reply to Ben Beasley from comment #12) > I experimented with adopting python-rope and getting it up to date, ran into > some test failures I did not feel like spending a lot of time on, and moved > on. Did you try the latest release in combination with pytoolconfig? And that had test failures? > However, I did get python-pytoolconfig properly packaged locally, and I am > happy to throw up a review request and maintain/co-maintain a > python-pytoolconfig package if someone else wants to do the necessary work > on python-rope. Well, I guess I will be adopting another package then... ;-) (In reply to Adam Williamson from comment #11) > We would likely want to bump to the latest version of this - 1.7.4 - but > that's problematic as it needs newer versions of rope and yapf. > > I think bumping yapf to 0.33.0 would be simple (0.40.0 might be a bit > tricker), but bumping rope is harder, because newer versions of rope require > https://github.com/bagel897/pytoolconfig , which is not yet packaged for > Fedora, so that will need to be added to the distro first. Updating to the latest release is what I had in mind as well. Maybe not in one giant step, but eventually. I know the maintainer of yapf. Time for a nudge. (In reply to Adam Williamson from comment #13) > Jonathan Wright, who took spyder (which depends on this), indicated to me in > chat he wants to pick up the orphaned deps of spyder and ultimately get > spyder working again, so I guess he'd be interested. Adding him to CC. Well, I made him co-maintainer of all packages which are dependencies of Spyder and which I recently adopted for that reason. So he will be in Cc for any new bugs.
(In reply to Sandro from comment #14) > (In reply to Ben Beasley from comment #12) > > I experimented with adopting python-rope and getting it up to date, ran into > > some test failures I did not feel like spending a lot of time on, and moved > > on. > > Did you try the latest release in combination with pytoolconfig? And that > had test failures? I think so? But I will have to go back and look at my work in progress. I can also push my efforts to a fork and link to it. I imagine the problems are surmountable; I just didn’t have a very high annoyance quota for the package. It sounds like there’s enough interest backed by labor to bring this stack back to life, so I’ll go ahead and post the review request for python-pytoolconfig too.
(In reply to Ben Beasley from comment #15) > (In reply to Sandro from comment #14) > > Did you try the latest release in combination with pytoolconfig? And that > > had test failures? > > I think so? But I will have to go back and look at my work in progress. I > can also push my efforts to a fork and link to it. I imagine the problems > are surmountable; I just didn’t have a very high annoyance quota for the > package. If you could publish what you have in a fork, that would be great. I can pick up from there. > It sounds like there’s enough interest backed by labor to bring this stack > back to life, so I’ll go ahead and post the review request for > python-pytoolconfig too. Thank you! I can do the review. Ping me on Matrix/IRC when it's up.
I updated python-lsp-server to the latest release (1.7.4). That brought up another unpackaged dependency (bug 2236998, reviewers welcome) as well as two packaged dependencies (python-autopep8 and python3-pydocstyle) , which have not yet been fixed for Python3.12. The preliminary build is here: https://copr.fedorainfracloud.org/coprs/gui1ty/reviews/build/6366250/
This now builds with "fixed" autopep8 and pydocstyle in Copr: https://copr.fedorainfracloud.org/coprs/gui1ty/reviews/build/6367119/ I've submitted PRs for both autopep8 and pydocstyle to get this unblocked.
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ All subpackages of a package against which this bug was filled are now installable or removed from Fedora 40. Thanks for taking care of it!
Update is in testing (a whole bunch of them): https://bodhi.fedoraproject.org/updates/FEDORA-2023-58ed7d993b
FEDORA-2023-58ed7d993b has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-58ed7d993b
FEDORA-2023-58ed7d993b has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.