Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok). Your package (mkdocs) Fails To Install in Fedora 38: can't install mkdocs: - nothing provides (python3.11dist(markdown) < 3.4~~ with python3.11dist(markdown) >= 3.2.1) needed by mkdocs-1.3.1-2.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-38-x86_64 --config-opts mirrored=False install mkdocs 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, This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs). 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.
Hello, This is the second reminder (step 4 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs). 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.
@mhroncok Blocked on https://github.com/mkdocs/mkdocs/issues/2892#issuecomment-1200518008, I don't see any other option than retiring.
The other option is to package python-markdown3.3 compat package.
But it cannot be side-by-side installable with the current python-markdown? Or would mkdocs have to be patched to împort markdown33?
> But it cannot be side-by-side installable with the current python-markdown? That is the idea. See e.g. https://src.fedoraproject.org/rpms/python-sqlalchemy1.3 https://src.fedoraproject.org/rpms/python-pytest4 (f34 branch)
At this point pip in virtualenv is probably the better solution?
Of what problem? If you want mkdocs packaged as RPM, pip in virtualenv is not an option. If you want developers to use mkdocs for their Python projects in Fedroa, pip in virtualenv was always the better option.
Right, I think I just took over mkdocs last time it was getting retired - but I see that it is a leaf package, so no real reason for it to exist as an rpm.
mkdocs is now retired.