* Package name : pgadmin4 Version : 1.0 * URL : https://www.pgadmin.org/ * License : PostgreSQL (BSD) Programming Lang: python, javascript, jquery Description : graphical administration tool for PostgreSQL, generation 4 pgAdmin 4 is a complete rewrite of pgAdmin, built using Python and Javascript/jQuery. A desktop runtime written in C++ with Qt allows it to run standalone for individual users, or the web application code may be deployed directly on a webserver for use by one or more users through their web browser. The application has the look and feel of a modern desktop application whatever the runtime environment is, and vastly improves on pgAdmin 3 with improved user interface elements, multi-user/web deployment options, dashboards and a much more modern design. The PostgreSQL packaging team is looking for help creating and maintaining this package under the team umbrella. Please get in touch with us if you are interested. Christoph
I am using Stretch, and have installed PostgreSQL 9.6 (9.6.2-2) and pgAdmin3 (1.22.2-1) from the Stretch repo.
But it seems that pgAdmin3 doesn't work with PostgreSQL 9.6. I get errors when trying to add a primary key, both when creating a table and when trying to add it later:
An error has occurred:
09:04:41 AM: Error: ERROR: column "amgettuple" does not exist
LINE 1: ..._am WHERE EXISTS (SELECT 1 FROM pg_proc WHERE oid=amgettuple...
^
It's the same error described by someone else in this post:
http://stackoverflow.com/q/40904102/994153
where the solution was to switch from pgAdmin III to pgAdmin version 4.
So it seems important to update this key PostgreSQL tool to the version that supports the latest version of PostgreSQL that is also in Stretch.
I spent an hour trying to roll a barebones deb from pgadmin4.git.
I got stuck here:
Exception occurred:
File "/tmp/pgadmin4-X/web/pgadmin/__init__.py", line 19, in <module>
from flask_htmlmin import HTMLMIN
ImportError: No module named flask_htmlmin
According to apt-file, flask_htmlmin isn't in Stretch.
It appears to be this:
https://github.com/hamidfzm/Flask-HTMLmin
That puts pgadmin4 into my "too hard" basket for now.
Here's where I got to before giving up:
debian/changelog:pgadmin4 (1.6+53-ge506fa1-1) unstable; urgency=low
debian/changelog:
debian/changelog: * Initial release (Closes: #nnnn) <nnnn is the bug number of your ITP>
debian/changelog:
debian/changelog: -- root <root@unknown> Tue, 01 Aug 2017 11:56:36 +1000
debian/clean:# FIXME: remove after calling python3 properly
debian/clean:*/*.pyc
debian/clean:*/*/*.pyc
debian/clean:*/*/*/*.pyc
debian/compat:9
debian/control:Source: pgadmin4
debian/control:Section: unknown
debian/control:Priority: optional
debian/control:Maintainer: root <root@unknown>
debian/control:Build-Depends: debhelper (>= 9), python-flask, python-sphinx, python-flask-babel
debian/control:Standards-Version: 3.9.5
debian/control:Homepage: <insert the upstream URL, if relevant>
debian/control:
debian/control:Package: pgadmin4
debian/control:Architecture: any
debian/control:Depends: ${shlibs:Depends}, ${misc:Depends}
debian/control:Description: <insert up to 60 chars description>
debian/control: <insert long description, indented with spaces>
debian/docs:README
debian/docs:libraries.txt
debian/docs:requirements.txt
debian/rules:#!/usr/bin/make -f
debian/rules:DPKG_EXPORT_BUILDFLAGS = 1
debian/rules:include /usr/share/dpkg/default.mk
debian/rules:%:
debian/rules: dh $@
debian/source/format:3.0 (quilt)
| | | | | | | | | | | PostgreSQL: Linux downloads (Debian) | | | mpapet
Re: Michael Papet 2018-02-03 <19536.1836909.1517637583311@mail.yahoo.com> Right, we uploaded the package there. The missing bit for Debian is that the tarball contains JavaScript bundles. These bundles consist mostly of the pgAdmin4 source files, but also some external JS libraries. The list of these external libraries is documented, so getting this part DFSG-compliant is feasible. Missing however is the transpiler (minifier) used for creating the bundles, "yarn". (There is a yarn in Debian which is something completely different.) Getting yarn into Debian will probably require a lot more effort, so there is still a lot of work to be done before pgAdmin4 can enter Debian unstable. Help welcome. Christoph
-- Good day,I have a deal for your professional expertise. Reply to chensiiqugg@outlook.jp for further details Regards Chen Siqing (Secretary)
I wonder if pgadmin4 can assist with getting this into the debian repo. I let them know about the issue: https://redmine.postgresql.org/issues/5606
Though it has been renamed to yarnpkg - see https://packages.debian.org/buster/yarnpkg
Hi, the pgadmin4 developers have started distributing their own .deb and .rpm packages [*] which makes me wonder if we should continue shipping our own pgadmin4.deb packages. As a GUI application, it is naturally hard to test, so bugs like https://redmine.postgresql.org/issues/5692 are prone to happen. I'm not extensively using the package myself, so I'd be glad if someone else took over maintenance of it. Anyone interested? Otherwise I'd propose that we drop it. Christoph [*] They never contacted me about it, and I was pretty much disappointed when I found out. My motivation to continue working on the package is quite low. https://www.pgadmin.org/download/pgadmin-4-apt/
Hi Christoph, Dropping this package is a question that really makes sens. If the decision is to keep it, and as a postgresql and pgadmin user i would like to volunteer to takeover. Il will certainly have many question,including about the takerover procedure since it is the first time i apply for this. king regards, William
Re: William Bonnet Hi William, do you have experience with Debian packaging? You'll likely have to work on packaging or updating Python module packages in Debian as well. Plus debugging the whole stack on older Debian/Ubuntu releases. Christoph
Hi Christoph, First of all i do apologize for my late answer, something went wrong on my side with email delivery... :( Yes I do, I have often made packages either at office or as a hobby, i created a framework to automatically build Debian packages for kernel and uboot from upstream sources (https://github.com/wbonnet/dft). Since it's a different and long story i'll be happy to share and discuss about this, maybe in another email ;) I am not ( yet ;) ) a Debian maintainer, but i have been for several years a Solaris maintainer in OpenCSW and Blastwave for software like Firefox Thunder bird or Xfce, working with upstram communities and submitting portability patches to compile and work under solaris. Its a different platform and toolchain, but still a maintainer work. In short :) i know what i am doing by applying to maintain a PG tool package :) it is going to be a lot of work, and i have checked that enough free time time in the coming months to handle this. I was expecting to have this work to do and of course to with Ubuntu and Postgresql maintainers and community. I'll be really happy to collaborate with the other communities and share the effort. I propose to start on my side by upgrading your pckage to latest restarting from existing package definition and let you knwow and see how things are going. Let me know please what information you may need, and don't hesitate if you have advices on the steps to follow. I expect to start with upgrade and non regression tests. Kind regards, William PS: I'm sorry i hove to restart a new mail instead of a true reply, something went really bad on my email side :(
Hello, Did you create a Salsa repo where you have started your work and uploaded sources? That will make it easier for others to contribute to the package. Also, Yarn is not a minifier it's a package manager. AFAIK it can't be used during build. All dependencies must be Debian packages. There are many JS libs in Debian with the `libjs-` prefix. Probably some are missing, but I didn't check yet. Michel Le Bihan
Re: William Bonnet Hi William, the last week was very busy and I was just too tired to answer earlier, sorry for that. That sounds perfect. Thanks for volunteering. Ideally the package would be included in Debian and Ubuntu, but that needs the whole "Javascript needs packing and proper licenses" issue resolved first which will not be easy. Until that happens, we have the packages on apt.postgresql.org, where it is built for the Debian and Ubuntu distributions. Another question is if "our" package needs adjustments now that pgadmin4 upstream has published their own packages with a completely different layout. (At the very least we should probably "Conflict:" with their packages so users don't get into a mess when they have installed both. Or maybe that's not a problem and having both works.) The packaging repository is https://salsa.debian.org/postgresql/pgadmin4 . I suggest you get an account there, and clone the repository to work on. I can also get you privileges to trigger builds for https://pgdgbuild.dus.dg-i.net/job/pgadmin4/ and the related build jobs there. Christoph
This RFP has languished for almost 3 years now and was opened almost 7 years ago. The pgadmin4 package provided upstream works without issue on Trixie. Is the delay licencing-related or is there not interest in carrying this package in Debian's repos?