Fails to build against up to date OpenSSL library (Bug 663966). No longer supported upstream. Use dev-db/pgadmin4.
commit 75d2eaa58ade1e8a5abe2fa5c0fda36d347dd3c3 (HEAD -> master, origin/master, origin/HEAD) Author: Aaron W. Swenson <titanofold@gentoo.org> Date: Thu Oct 25 19:31:56 2018 -0400 profiles/package.mask: Mask dev-db/pgadmin3 dev-db/pgadmin3 masked for removal in 30 days (2018-11-24). Signed-off-by: Aaron Swenson <titanofold@gentoo.org>
Using pgadmin4 isn't, for the moment, a solution as it rely on dev-python/pycrypto which is deprecated/dead project. So if you have applications like app-admin/salt, which have done the upgrade to dev-python/pycryptodome, emerge fails on a block like: [blocks B ] dev-python/pycrypto ("dev-python/pycrypto" is blocking dev-python/pycryptodome-3.4.6) Upstream issue: https://redmine.postgresql.org/issues/3272 (no target version)
(In reply to Aurelien Minet from comment #2) > Using pgadmin4 isn't, for the moment, a solution as it rely on > dev-python/pycrypto which is deprecated/dead project. > So if you have applications like app-admin/salt, which have done the upgrade > to dev-python/pycryptodome, emerge fails on a block like: > [blocks B ] dev-python/pycrypto ("dev-python/pycrypto" is blocking > dev-python/pycryptodome-3.4.6) > > Upstream issue: > https://redmine.postgresql.org/issues/3272 > (no target version) The pycrypto(dome) is a known issue (bug 669658). I've attempted to switch out pycrypto for pycryptodome, but pgadmin4 can't use it since pycrptodome is no longer a drop in replacement (if it ever was). However, this does not prevent the removal pgadmin3. Using pgadmin4 is just a suggestion.
(In reply to Aaron W. Swenson from comment #3) > > However, this does not prevent the removal pgadmin3. Using pgadmin4 is just > a suggestion. In practice, removal of pgadmin3 means people are without a solution. Because as-is, pgadmin4 is not actually installable by many of us, while pgadmin3 is. Please don't remove pgadmin3 until a viable way of installing pgadmin4 is provided.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c27c8dfa1bc0dd1371ce9cd0a1383a44965b0dc9 commit c27c8dfa1bc0dd1371ce9cd0a1383a44965b0dc9 Author: Brian Evans <grknight@gentoo.org> AuthorDate: 2019-01-23 18:35:50 +0000 Commit: Brian Evans <grknight@gentoo.org> CommitDate: 2019-01-23 18:35:50 +0000 dev-db/pgadmin3: Remove last rites package Closes: https://bugs.gentoo.org/show_bug.cgi?id=669650 Signed-off-by: Brian Evans <grknight@gentoo.org> dev-db/pgadmin3/Manifest | 1 - dev-db/pgadmin3/files/pgadmin3-desktop-r1.patch | 15 -------- .../files/pgadmin3-gcc6-null-pointer.patch | 11 ------ dev-db/pgadmin3/metadata.xml | 11 ------ dev-db/pgadmin3/pgadmin3-1.22.2.ebuild | 45 ---------------------- profiles/package.mask | 6 --- 6 files changed, 89 deletions(-)
Reverted change. Did not notice comments here
(In reply to Brian Evans from comment #6) > Reverted change. Did not notice comments here Thanks for trying to help! And, it did remind me to ack the last comment. I agree to leave it until upstream figures out how to move away from pycrypto. (Unless, somewhere can come up with a patch. I don't have the patience to learn Python right now.)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4a11134c8161f5d13a0218301f78b9206062ddc8 commit 4a11134c8161f5d13a0218301f78b9206062ddc8 Author: Aaron W. Swenson <titanofold@gentoo.org> AuthorDate: 2019-02-13 11:33:56 +0000 Commit: Aaron W. Swenson <titanofold@gentoo.org> CommitDate: 2019-02-13 11:34:19 +0000 dev-db/pgadmin4: Bump to 4.2 Among numerous other fixes, drops dependency on dev-python/pycrypto. Bug: https://bugs.gentoo.org/669658 Bug: https://bugs.gentoo.org/669650 Package-Manager: Portage-2.3.51, Repoman-2.3.11 Signed-off-by: Aaron W. Swenson <titanofold@gentoo.org> dev-db/pgadmin4/Manifest | 1 + dev-db/pgadmin4/pgadmin4-4.2.ebuild | 123 ++++++++++++++++++++++++++++++++++++ 2 files changed, 124 insertions(+)
Thanks Aaron for the bump as upstream done a pycrypto free version (https://redmine.postgresql.org/issues/3272#change-14856) I build this version (4.2) without problem (Python 3.6), the first tests look ok. It sounds like the end for pgadmin3.
So can this package finally go?
(In reply to Lars Wendler (Polynomial-C) from comment #10) > So can this package finally go? Not yet. pgadmin-4.2-r1 needs to be stabilized. Once that's done, I can get rid of all the things.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ba00bd4413d1043b56a08697877745e69d35a562 commit ba00bd4413d1043b56a08697877745e69d35a562 Author: Aaron W. Swenson <titanofold@gentoo.org> AuthorDate: 2019-06-21 11:45:34 +0000 Commit: Aaron W. Swenson <titanofold@gentoo.org> CommitDate: 2019-06-21 11:45:34 +0000 dev-db/pgadmin3,profiles/package.mask: Removal dev-db/pgadmin3 has been removed. Use dev-db/pgadmin4 instead. Closes: https://bugs.gentoo.org/669650 Closes: https://bugs.gentoo.org/663966 Signed-off-by: Aaron W. Swenson <titanofold@gentoo.org> dev-db/pgadmin3/Manifest | 1 - dev-db/pgadmin3/files/pgadmin3-desktop-r1.patch | 15 -------- .../files/pgadmin3-gcc6-null-pointer.patch | 11 ------ dev-db/pgadmin3/metadata.xml | 11 ------ dev-db/pgadmin3/pgadmin3-1.22.2.ebuild | 45 ---------------------- profiles/package.mask | 6 --- 6 files changed, 89 deletions(-)
