From: | "Car(dot)cuevas" <car(dot)cuevas(at)protonmail(dot)com> |
---|---|
To: | "pgsql-pkg-yum(at)lists(dot)postgresql(dot)org" <pgsql-pkg-yum(at)lists(dot)postgresql(dot)org> |
Subject: | New Repo and AMI AWS |
Date: | 2019-04-17 09:24:17 |
Message-ID: | vnqFsRT9omXaYnP8euZ9NWgETfiSDwA3DNJ9M9j-oUn15lI32ToZPpm8c18aOmuJWUhdnQfyhDVxRl4taSBKvYpmOSeUANCioYCtRqJFkLg=@protonmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-yum |
Hi guys,
I saw the announcement of the new repository merged:
https://www.postgresql.org/message-id/6f1e601300d575195d4f0d8a066ef4abf4c90c99.camel%40gunduz.org
We were using actually pgdg-redhat10-10-2.noarch.rpm or pgdg-centos10-10-2.noarch.rpm for some EC2 instances in AWS, running Amazon AMI2, but now since the merge, it broke for AWS AMI since this distro lacks the /etc/redhat-release:
yum install https://download.postgresql.org/pub/repos/yum/10/redhat/rhel-7-x86_64/pgdg-centos10-10-2.noarch.rpm
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
pgdg-centos10-10-2.noarch.rpm | 5.6 kB 00:00:00
Examining /var/tmp/yum-root-CLDEec/pgdg-centos10-10-2.noarch.rpm: pgdg-redhat-repo-42.0-4.noarch
Marking /var/tmp/yum-root-CLDEec/pgdg-centos10-10-2.noarch.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package pgdg-redhat-repo.noarch 0:42.0-4 will be installed
--> Processing Dependency: /etc/redhat-release for package: pgdg-redhat-repo-42.0-4.noarch
amzn2-core | 2.4 kB 00:00:00
amzn2extra-docker | 1.3 kB 00:00:00
epel/x86_64/metalink | 18 kB 00:00:00
(1/3): amzn2-core/2/x86_64/group_gz | 2.4 kB 00:00:00
(2/3): amzn2-core/2/x86_64/updateinfo | 99 kB 00:00:00
(3/3): amzn2-core/2/x86_64/primary_db | 28 MB 00:00:00
175 packages excluded due to repository priority protections
--> Processing Dependency: /etc/redhat-release for package: pgdg-redhat-repo-42.0-4.noarch
--> Finished Dependency Resolution
Error: Package: pgdg-redhat-repo-42.0-4.noarch (/pgdg-centos10-10-2.noarch)
Requires: /etc/redhat-release
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
So now it is not possible to use this repository in new machines... Is it there anyway around this?
Thanks very much,
Carlos Cuevas
From | Date | Subject | |
---|---|---|---|
Next Message | GOLLET Nicolas | 2019-04-17 10:20:38 | [bug] New repo RPMS on Centos7 and ppc64le platform |
Previous Message | John Harvey | 2019-04-16 22:17:09 | Re: Splitting libpq into a separate package |