On Mon, Apr 24, 2017 at 11:15 AM, Adrian Klaver <adrian.kla...@aklaver.com> wrote:
> On 04/24/2017 05:06 AM, Clodoaldo Neto wrote: > Please reply to list also > Ccing list > > On Sun, Apr 23, 2017 at 4:58 PM, Adrian Klaver >> <adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>> wrote: >> > > >> I disabled the priorities plugin and got no excluded packages but still >> the same failed dependencies. >> >> >> Installed Packages >> pgadmin4-python-beautifulsoup4.noarch >> 4.5.1-2.rhel7 @pgdg96 >> pgadmin4-python-fixtures.noarch >> 3.0.0-4.rhel7 @pgdg96 >> pgadmin4-python-flask-principal.noarch >> 0.4.0-13.rhel7 @pgdg96 >> pgadmin4-python-itsdangerous.noarch >> 0.24-9.rhel7 @pgdg96 >> >> # yum install pgadmin4-v1-web >> >> >> Do you have the PGDG repos installed on your machine?: >> >> https://www.postgresql.org/download/linux/redhat/ >> <https://www.postgresql.org/download/linux/redhat/> >> >> Or did you install the pgadmin4* packages above directly? >> >> >> I have the pgdg-96 repo installed. >> >> The first problem is that the four packages above have the "pgadmin4" >> string prefixed to their names whereas the spec file aks for the name >> without the prefix like in "pgadmin4-python-fixtures" vs >> "python-fixtures". >> > > To be clear I am not a Yum/RPM expert. > > Where is the spec file coming from? > > >From the pgadmin4-v1-web package: https://yum.postgresql.org/srpms/9.6/redhat/rhel-7-x86_64/pgadmin4-v1-1.4-1.rhel7.src.rpm > >> The second problem is that the other packages do not exist in pgdg-96 in >> either form. >> > > Looks to me they do: > > https://yum.postgresql.org/9.6/redhat/rhel-7-x86_64/ > > Missing packages: python-dateutil, python-mimeparse, python-flask-security, python-flask-wtf Clodoaldo > >> IMHO prefixing the package names with "pgadmin4" just adds confusion as >> there will be different packages installing the same file names in the >> same places. The different repo sources can be managed with priorities >> if necessary. >> >> Clodoaldo >> >> > > > -- > Adrian Klaver > adrian.kla...@aklaver.com >
