[MacPorts] #63979: qca and subports: revisions have not been restored correctly
MacPorts
noreply at macports.org
Sun Nov 21 17:09:24 UTC 2021
#63979: qca and subports: revisions have not been restored correctly
-------------------------+----------------------
Reporter: ryandesign | Owner: RJVB
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: qca |
-------------------------+----------------------
Comment (by RJVB):
I checked the history on my Mac, and can no longer say with certainty what
happened there; it turns out the main port was NOT updated (`port:qca was
at 2.2.1_1) but the subports were.
HOWEVER, I simulated the botched upgrade to 2.3.4 by increasing the
version and removing the epoch after doing a `port destroot` and copying a
file from one of the qca-qt5 subports. That caused the upgrade to fail
like it failed for everyone using the stock port:qca : at the activation
stage after the actual installation of the "new" version.
Then, I reverted the version back to 2.2.1 and restored the epoch. The
port upgraded perfectly to 2.2.1_0, as predicted by my previous post.
I think thus that there is indeed no reason to restore the revisions as
they were before any upgrade to 2.3.4 .
If somehow there are a few users for whom the old qca/Qt4 2.2.1_0 port(s)
get reactivated instead of a fresh install, they should get rev-upgrade
errors or else runtime issues in the dependents. Normally I'd prefer to
avoid exposing even a few users to that, but in this case I prefer not
exposing everyone else to a probably unnecessary upgrade (no matter how
trivial that may seem).
--
Ticket URL: <https://trac.macports.org/ticket/63979#comment:16>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list