Description of problem: "/usr/bin/alembic" points to "alembic-" instead of "alembic-3" Version-Release number of selected component (if applicable): python3-alembic-1.4.2-2.fc33.noarch reproduce with "ls -al /usr/bin/alembic". Should be trivial, "/usr/bin/alembic-3.9 -> alembic-3" is OK.
This was fixed: https://src.fedoraproject.org/rpms/python-alembic/c/109f346e2f17a3de2a48e18fbb644f17619f0949?branch=f33 But the build was never shipped in an update.
And that build is unfortunately deleted now. ;( I can definitely do a f33 build... but should I perhaps just push the latest at the same time? There's a few changes in 1.5.0 that are 'changes': https://alembic.sqlalchemy.org/en/latest/changelog.html#change-1.5.0-changed but they all seem pretty minor to me and there's a number of bugfixes. So, what do you think? 1.5.3 ? or just be conservative and do a 1.4.3 build?
Given the branches already diverged, I'd just build the f33 fix and don't worry about the upgrade for a stable Fedora release unless something needs it.
FEDORA-2021-072a05a18a has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-072a05a18a
Tested the new RPM, it is fixed.
FEDORA-2021-072a05a18a has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-072a05a18a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-072a05a18a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-072a05a18a has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.