Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1awTrL-0007gQ-D7 for pgsql-pkg-yum@arkaria.postgresql.org; Sat, 30 Apr 2016 12:18:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1awTrK-0001qo-1Z for pgsql-pkg-yum@arkaria.postgresql.org; Sat, 30 Apr 2016 12:18:54 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1awTrG-0001nJ-CU for pgsql-pkg-yum@postgresql.org; Sat, 30 Apr 2016 12:18:50 +0000 Received: from ns3.gunduz.org ([107.170.88.27] helo=ns1.gunduz.org) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1awTrB-000623-HR for pgsql-pkg-yum@postgresql.org; Sat, 30 Apr 2016 12:18:48 +0000 Received: from [10.108.77.93] (unknown [178.241.97.69]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ns1.gunduz.org (Postfix) with ESMTPSA id B8D4446324; Sat, 30 Apr 2016 15:18:41 +0300 (EEST) User-Agent: K-9 Mail for Android In-Reply-To: References: <4B763CD0-331F-426E-B28F-23A9CF84C148@gunduz.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----PF3UXW04O3S67O5ZDL52VS9NUFPNPI" Content-Transfer-Encoding: 8bit Subject: Re: Postgres yum links currently have 404 errors From: =?ISO-8859-1?Q?Devrim_G=FCnd=FCz?= Date: Sat, 30 Apr 2016 15:18:38 +0300 To: David Micallef CC: pgsql-pkg-yum@postgresql.org Message-ID: <2F83D442-EF54-485F-9914-7CFD8D83F8F7@gunduz.org> X-Pg-Spam-Score: -2.9 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-pkg-yum Precedence: bulk Sender: pgsql-pkg-yum-owner@postgresql.org ------PF3UXW04O3S67O5ZDL52VS9NUFPNPI Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Hi, Oh, it seems we don't have symlink to "latest". I will add it once I will be back to laptop. Regards, Devrim On April 29, 2016 11:47:09 PM GMT+03:00, David Micallef wrote: >Half asleep this morning. I did get past that last night and tried > > sudo yum install postgresql95-server postgresql95 > > >Loaded plugins: priorities, update-motd, upgrade-helper >amzn-main/latest | 2.1 kB >00:00 >amzn-updates/latest | 2.3 kB >00:00 >pgdg93/latest/x86_64 | 3.6 kB >00:00 >https://download.postgresql.org/pub/repos/yum/9.5/redhat/rhel-latest-x86_64/repodata/repomd.xml: >[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not >Found" >Trying other mirror. > > >One of the configured repositories failed (PostgreSQL 9.5 latest - >x86_64), >and yum doesn't have enough cached data to continue. At this point the >only >safe thing yum can do is fail. There are a few ways to work "fix" this: > > 1. Contact the upstream for the repository and get them to fix the >problem. > > 2. Reconfigure the baseurl/etc. for the repository, to point to a >working > upstream. This is most often useful if you are using a newer > distribution release than is supported by the repository (and the > packages for the previous distribution release still work). > > 3. Disable the repository, so yum won't use it by default. Yum will >then > just ignore the repository until you permanently enable it again or >use > --enablerepo for temporary usage: > > yum-config-manager --disable pgdg95 > > 4. Configure the failing repository to be skipped, if it is >unavailable. > Note that yum will try to contact the repo. when it runs most >commands, > so will have to try and fail each time (and thus. yum will be be >much > slower). If it is a very temporary problem though, this is often a >nice > compromise: > > yum-config-manager --save >--setopt=pgdg95.skip_if_unavailable=true > >failure: repodata/repomd.xml from pgdg95: [Errno 256] No more mirrors >to >try. > > >David >+61 3 9036 2788 > > >On 30 April 2016 at 06:34, Devrim Gündüz wrote: > >> Hi David, >> >> Blog post has a .rpm suffix at the end of the file. Please use the >exact >> URL there. That is why you get 404. >> >> Regards, Devrim >> >> >> On April 29, 2016 11:28:49 PM GMT+03:00, David Micallef < >> dave@montagesoftware.com.au> wrote: >>> >>> Hi >>> >>> Currently trying to update to 9.5.2 from 9.4.5 on a test web server >with >>> amazon linux and unfortunately the rpm links seem to have 404. >>> >>> sudo rpm -Uvh >>> >http://yum.postgresql.org/9.5/redhat/rhel-6-x86_64/pgdg-redhat95-9.5-2.noarch >>> >>> Error >>> >>Retrieving >>> >http://yum.postgresql.org/9.5/redhat/rhel-6-x86_64/pgdg-redhat95-9.5-2.noarch >>> curl: (22) The requested URL returned error: 404 Not Found >>> error: skipping >>> >http://yum.postgresql.org/9.5/redhat/rhel-6-x86_64/pgdg-redhat95-9.5-2.noarch >>> - transfer failed >>> >>> I was following instructions from this link]( >>> http://tecadmin.net/install-postgresql-9-5-on-centos/) >>> >>> Cheers >>> >>> Dave >>> >>> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ------PF3UXW04O3S67O5ZDL52VS9NUFPNPI Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Hi,

Oh, it seems we don't have symlink to "latest". I will add it once I will be back to laptop.

Regards, Devrim

On April 29, 2016 11:47:09 PM GMT+03:00, David Micallef <dave@montagesoftware.com.au> wrote:
Half asleep this morning. I did get past that last night and tried

     sudo yum install postgresql95-server postgresql95


Loaded plugins: priorities, update-motd, upgrade-helper
amzn-main/latest                                         | 2.1 kB     00:00
amzn-updates/latest                                      | 2.3 kB     00:00
pgdg93/latest/x86_64                                     | 3.6 kB     00:00
https://download.postgresql.org/pub/repos/yum/9.5/redhat/rhel-latest-x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.


 One of the configured repositories failed (PostgreSQL 9.5 latest - x86_64),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:

            yum-config-manager --disable pgdg95

     4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=pgdg95.skip_if_unavailable=true

failure: repodata/repomd.xml from pgdg95: [Errno 256] No more mirrors to try.


David
+61 3 9036 2788


On 30 April 2016 at 06:34, Devrim Gündüz <devrim@gunduz.org> wrote:
Hi David,

Blog post has a .rpm suffix at the end of the file. Please use the exact URL there. That is why you get 404.

Regards, Devrim


On April 29, 2016 11:28:49 PM GMT+03:00, David Micallef <dave@montagesoftware.com.au> wrote:
Hi

Currently trying to update to 9.5.2 from 9.4.5 on a test web server with amazon linux and unfortunately the rpm links seem to have 404.


Cheers

Dave


--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


--
Sent from my Android device with K-9 Mail. Please excuse my brevity. ------PF3UXW04O3S67O5ZDL52VS9NUFPNPI--