Description of problem: Fabric is not ported to python3 yet, there is only a python2 package. Pelican upstream docs [1] recommend to use Fabric as deployment tool. This is currently not possible, as the python2 subpackage was removed. Version-Release number of selected component (if applicable): 3.7.1-5.fc28 How reproducible: always Steps to Reproduce: 1. Run pelican-quickstart 2. Answer with 'yes' when asked to generate a Fabfile 3. Configure Fabric 4. Run 'fab publish' Actual results: $ fab publish Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/fabric/main.py", line 667, in main docstring, callables, default = load_fabfile(fabfile) File "/usr/lib/python2.7/site-packages/fabric/main.py", line 168, in load_fabfile imported = importer(os.path.splitext(fabfile)[0]) File "/home/thofmann/Documents/website/fabfile.py", line 8, in <module> from pelican.server import ComplexHTTPRequestHandler ImportError: No module named pelican.server Expected results: No errors Additional info: This was caused by removing the python2 subpackage (https://bugzilla.redhat.com/show_bug.cgi?id=1487848) [1] http://docs.getpelican.com/en/stable/publish.html#automation
Pelican 3.8 is in planning phase, there were changes to exactly support that now https://github.com/getpelican/pelican/pull/2357
That's good to know! What's the schedule for the release? But even if there are plans to support Fabric 2 in the future, it's broken atm, and it's a regression compared to F27. Is there any reason why you can't add back the python2 package?
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.