[MacPorts] #63979: qca and subports: revisions have not been restored correctly

[MacPorts]

#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         |
-------------------------+----------------------

Old description:

> qca and subports were updated in
> [a971437a4529e72ff8d619adfbeec7ac8ea7b3b2/macports-ports]
>
> The update was reverted for some subports in
> [dad04b15bee6ca8f4d4f3e19ac1ed36c0e0282fb/macports-ports] but the port
> revisions were not returned to their previous values.
>
> Before a971437:
>
> {{{
> $ port info --name --version --revision {,subportof:}qca
> name: qca
> version: 2.2.1
> revision: 4
> --
> name: qca-cyrus-sasl
> version: 2.2.1
> revision: 0
> --
> name: qca-gnupg
> version: 2.2.1
> revision: 0
> --
> name: qca-ossl
> version: 2.2.1
> revision: 2
> --
> name: qca-pkcs11
> version: 2.2.1
> revision: 2
> --
> name: qca-qt5
> version: 2.2.1
> revision: 4
> --
> name: qca-qt5-cyrus-sasl
> version: 2.2.1
> revision: 0
> --
> name: qca-qt5-gnupg
> version: 2.2.1
> revision: 0
> --
> name: qca-qt5-ossl
> version: 2.2.1
> revision: 2
> --
> name: qca-qt5-pkcs11
> version: 2.2.1
> revision: 2
> }}}
>
> After dad04b1:
>
> {{{
> $ port info --name --version --revision {,subportof:}qca
> name: qca
> version: 2.2.1
> revision: 0
> --
> name: qca-cyrus-sasl
> version: 2.2.1
> revision: 0
> --
> name: qca-gnupg
> version: 2.2.1
> revision: 0
> --
> name: qca-ossl
> version: 2.2.1
> revision: 0
> --
> name: qca-pkcs11
> version: 2.2.1
> revision: 0
> --
> name: qca-qt5
> version: 2.3.4
> revision: 0
> --
> name: qca-qt5-cyrus-sasl
> version: 2.3.4
> revision: 0
> --
> name: qca-qt5-gnupg
> version: 2.3.4
> revision: 0
> --
> name: qca-qt5-ossl
> version: 2.3.4
> revision: 0
> --
> name: qca-qt5-pkcs11
> version: 2.3.4
> revision: 0
> }}}
>
> Note 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.)
>
> 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.

New description:

 qca and subports were updated in [a971437a4529e72ff8d619adfbeec7ac8ea7b3b2
 /macports-ports]

 The update was reverted for some subports in
 [dad04b15bee6ca8f4d4f3e19ac1ed36c0e0282fb/macports-ports] but the port
 revisions were not returned to their previous values.

 Before a971437:

 {{{
 $ port info --name --version --revision {,subportof:}qca
 name: qca
 version: 2.2.1
 revision: 4
 --
 name: qca-cyrus-sasl
 version: 2.2.1
 revision: 0
 --
 name: qca-gnupg
 version: 2.2.1
 revision: 0
 --
 name: qca-ossl
 version: 2.2.1
 revision: 2
 --
 name: qca-pkcs11
 version: 2.2.1
 revision: 2
 --
 name: qca-qt5
 version: 2.2.1
 revision: 4
 --
 name: qca-qt5-cyrus-sasl
 version: 2.2.1
 revision: 0
 --
 name: qca-qt5-gnupg
 version: 2.2.1
 revision: 0
 --
 name: qca-qt5-ossl
 version: 2.2.1
 revision: 2
 --
 name: qca-qt5-pkcs11
 version: 2.2.1
 revision: 2
 }}}

 After dad04b1:

 {{{
 $ port info --name --version --revision {,subportof:}qca
 name: qca
 version: 2.2.1
 revision: 0
 --
 name: qca-cyrus-sasl
 version: 2.2.1
 revision: 0
 --
 name: qca-gnupg
 version: 2.2.1
 revision: 0
 --
 name: qca-ossl
 version: 2.2.1
 revision: 0
 --
 name: qca-pkcs11
 version: 2.2.1
 revision: 0
 --
 name: qca-qt5
 version: 2.3.4
 revision: 0
 --
 name: qca-qt5-cyrus-sasl
 version: 2.3.4
 revision: 0
 --
 name: qca-qt5-gnupg
 version: 2.3.4
 revision: 0
 --
 name: qca-qt5-ossl
 version: 2.3.4
 revision: 0
 --
 name: qca-qt5-pkcs11
 version: 2.3.4
 revision: 0
 }}}

 Note 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.)

 ~~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.~~

--

Comment (by ryandesign):

 Replying to [comment:2 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.

-- 
Ticket URL: <https://trac.macports.org/ticket/63979#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS