Changes between Version 1 and Version 5 of Ticket #63979


Ignore:
Timestamp:
Nov 18, 2021, 9:20:17 AM (3 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Replying to RJVB:

Something is off here, maybe you missed an update?

No.

  • I did not change the revision numbers of the Qt5 subports, nor did I change the version which was already at 2.3.4

And I have no complaint about that.

  • The epoch of the Qt4 (v2.2.1) subports *is* changed,

You're right, I missed that part of your update. Disregard what I wrote about the epoch.

and the *upgrade* of their version (in the previous commit of this port) is REVERTED.

Yes, but the revisions have not been restored to (or above) their prior values, as is required.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #63979

    • Property Cc mascguy added

  • Ticket #63979 – Description

    v1 v5  
    9595Note how the subports qca, qca-ossl, and qca-pkcs11 now have lesser revisions than they used to. This must be corrected by increasing the revisions to the same value as before (if the ports install the same exact files as before) or higher than they were before (if the ports now install different files than before, for example if you are now linking with a different openssl version than before). (And the revisions of the subports whose revisions remained at 0 would need to be increased if they are now different than before.)
    9696
    97 Also, the epoch was not increased. This might be ok: If the update to 2.3.4 was unbuildable for all users, then the epoch should not be increased. However if any users were able to install the 2.3.4 subports that you have now reverted to 2.2.1, the epoch must be increased, otherwise those users will not see the downgrade available in `port outdated` and `sudo port upgrade outdated` will not perform the downgrade.
     97~~Also, the epoch was not increased. This might be ok: If the update to 2.3.4 was unbuildable for all users, then the epoch should not be increased. However if any users were able to install the 2.3.4 subports that you have now reverted to 2.2.1, the epoch must be increased, otherwise those users will not see the downgrade available in `port outdated` and `sudo port upgrade outdated` will not perform the downgrade.~~