#63552 closed defect (fixed)
gnupg2 2.3.2 Please revert from TEST branch to STABLE
Reported by: | jmarshallidau | Owned by: | roederja |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.1 |
Keywords: | Cc: | Ionic (Mihai Moldovan), cjones051073 (Chris Jones), neverpanic (Clemens Lang) | |
Port: | gnupg2 |
Description
Looks like this port may have been unintentionally updated to 'a later version' without regard to the details.
2.3.2 is in the test-release branch (which will become 2.4 stable). There are changes which will likely break things for the un-prepared. Please revert this port to the release branch, i.e. back to 2.2.31 (unless there's a later 2.2.n by the time this ticket is processed).
The 2.3.0 announcement makes it plain this branch is not (yet) for production consumption:
https://lists.gnupg.org/pipermail/gnupg-announce/2021q2/000458.html
and the GnuPG home page shows that 2.2.31 is the current release:
Change History (5)
comment:1 Changed 3 years ago by jmroot (Joshua Root)
Cc: | Ionic cjones051073 added |
---|---|
Owner: | set to roederja |
Status: | new → assigned |
comment:2 Changed 3 years ago by neverpanic (Clemens Lang)
Cc: | neverpanic added |
---|
comment:3 Changed 3 years ago by roederja
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:4 Changed 3 years ago by cjones051073 (Chris Jones)
The epoch HAS to be bumped if you wish to force a port to rollback to an older version....
comment:5 Changed 3 years ago by cjones051073 (Chris Jones)
Note: See
TracTickets for help on using
tickets.
I have now rolled it back. Obviously people who have already upgraded need to downgrade manually. Not sure I want to set epoch on the port.