The following files in Manifest are missing SHA512 and WHIRLPOOL digests: install-crossover-standard-6.0.0.sh install-crossover-standard-6.0.1.sh install-crossover-standard-6.1.0.sh install-crossover-standard-6.2.0.sh
I don't have access to any of those binaries to regenerate digests. If someone else in the project has access, maybe they can tackle it. If no one is able, what do you propose as a course of action?
(In reply to NP-Hardass from comment #1) > If no one is able, what do you propose as a course of action? Somebody in the project should have these binaries, or how else would you be able to maintain the package? Portage supports SHA512 since more than 5 years (portage-2.1.10.44, stable in Feb. 2012), and there are discussions in the QA team if we could finally drop SHA256.
# NP-Hardassr <NP-Hardass@gentoo.org> (03 Apr 2017) # Masked for removal in 30 days. Unable to generate new # hashes for the manifest, per Bug #612720, Bug #612718 # Upstream has also deprecated these in favor of # app-emulation/crossover-bin app-emulation/crossover-office-bin app-emulation/crossover-office-pro-bin
I just saw about this bug in the last rites email. I have access to these binaries (plus the ones in bug #612720 too) and can generate the digests. Here are the ones for this bug: $ sha512sum install-crossover-standard-6.* cc24ed70362359123921eb23509e63facbb5f873f50210677dfdde040d43194805d378f6f473f439797aac40b90a98e33ab8648eae11bec31b00c998219a3d0c install-crossover-standard-6.0.0.sh a179d07cb7190befae020b220e0f3743e0f17a4cc0c717d4d07a99957dac6c23c63e12615fab26bd79e6d9b42027defe46e65ff73ce0b2502f686a8c5fbf54da install-crossover-standard-6.0.1.sh 5873e2197efc863e31031d6ef299b6d12864f635d756fe71b30df3626353a45003170130600be13880b2bd10256ab17729706a75e0a2847d0d33d350dbd6876e install-crossover-standard-6.1.0.sh de1562bade6cb6530d878fcec21c744bcef4c902b6900b14aee23b1ed163ea9dd5608cdcef3134edd672f22e643e61850422d916a53d6fa826f2140e15bc77be install-crossover-standard-6.2.0.sh $ whirlpooldeep -l install-crossover-standard-6.* 1fd3de391f0c888d7439c106397b6a86475d76d3f4f00310455ba3ce28a532d22bf5025ce4e3c49a76c32184eb54905a271a373859314802c4d9689f8afaa576 install-crossover-standard-6.0.0.sh 7ebf5dee84d3f76413f7ea59989c8f677eb012448fd127e70aeb8635ea35f83f606bbac4b4fdece6044f1e776313562bfe59b7bd7c8201906a9f7a19c76dcb13 install-crossover-standard-6.0.1.sh 18a7da528f4cacd111e7311a8f4487af07368e9de938c78bd115961f5edfbd77906ba9146d3f4d9b3f58282c9608985a487744bfd7211ef78a79eae08e81d67b install-crossover-standard-6.2.0.sh ae32ae9378aa89baf4518d7ee69874b06d78e01495f1b198e088b4bc92c48788b83a7d2f153e960daca6d82a28d03333b7b9b22d1f1390b32c67f1b68f71a045 install-crossover-standard-6.1.0.sh Please let me know whether or not this is useful for this bug or for bug #612720.
(In reply to Luke Bratch from comment #4) > I just saw about this bug in the last rites email. > > I have access to these binaries (plus the ones in bug #612720 too) and can > generate the digests. Here are the ones for this bug: > > $ sha512sum install-crossover-standard-6.* > cc24ed70362359123921eb23509e63facbb5f873f50210677dfdde040d43194805d378f6f473f > 439797aac40b90a98e33ab8648eae11bec31b00c998219a3d0c > install-crossover-standard-6.0.0.sh > a179d07cb7190befae020b220e0f3743e0f17a4cc0c717d4d07a99957dac6c23c63e12615fab2 > 6bd79e6d9b42027defe46e65ff73ce0b2502f686a8c5fbf54da > install-crossover-standard-6.0.1.sh > 5873e2197efc863e31031d6ef299b6d12864f635d756fe71b30df3626353a45003170130600be > 13880b2bd10256ab17729706a75e0a2847d0d33d350dbd6876e > install-crossover-standard-6.1.0.sh > de1562bade6cb6530d878fcec21c744bcef4c902b6900b14aee23b1ed163ea9dd5608cdcef313 > 4edd672f22e643e61850422d916a53d6fa826f2140e15bc77be > install-crossover-standard-6.2.0.sh > > $ whirlpooldeep -l install-crossover-standard-6.* > 1fd3de391f0c888d7439c106397b6a86475d76d3f4f00310455ba3ce28a532d22bf5025ce4e3c > 49a76c32184eb54905a271a373859314802c4d9689f8afaa576 > install-crossover-standard-6.0.0.sh > 7ebf5dee84d3f76413f7ea59989c8f677eb012448fd127e70aeb8635ea35f83f606bbac4b4fde > ce6044f1e776313562bfe59b7bd7c8201906a9f7a19c76dcb13 > install-crossover-standard-6.0.1.sh > 18a7da528f4cacd111e7311a8f4487af07368e9de938c78bd115961f5edfbd77906ba9146d3f4 > d9b3f58282c9608985a487744bfd7211ef78a79eae08e81d67b > install-crossover-standard-6.2.0.sh > ae32ae9378aa89baf4518d7ee69874b06d78e01495f1b198e088b4bc92c48788b83a7d2f153e9 > 60daca6d82a28d03333b7b9b22d1f1390b32c67f1b68f71a045 > install-crossover-standard-6.1.0.sh > > Please let me know whether or not this is useful for this bug or for bug > #612720. Thank you for the hashes Luke. It is greatly appreciated that you stepped up and submitted hashes for these ebuilds. I think the point that Ulrich made is still pertinent though. None of the other project members stepped up with the sources, so presumably no one on the maintenance team has the sources or interest to continue maintaining this package. Couple that with the versions being 10 years old and upstream having newer versions available (app-emulation/crossover-bin) I think it is probably best to remove this package from the repo. This shouldn't stop you from maintaining it locally in your own repository or in taking over maintenance if you want to take over full responsibility for the package (but as stated previously, I think it is probably best to remove the package from ::gentoo at this time).
Makes sense to me - let app-emulation/crossover-office-bin and app-emulation/crossover-office-pro-bin die in ::gentoo. Was just checking. Thanks!
commit d8471c0fb16afaf5699b827fc8f2db5c67a0a55f Author: Michał Górny <mgorny@gentoo.org> AuthorDate: Mon May 15 11:15:48 2017 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: Mon May 15 11:42:22 2017 app-emulation/crossover-office-bin: Remove last-rited pkg, #612718
