Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U6WkA-0002Lz-O1 for pgsql-pkg-debian@arkaria.postgresql.org; Sat, 16 Feb 2013 01:39:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1U6Wk9-0005Js-QI for pgsql-pkg-debian@arkaria.postgresql.org; Sat, 16 Feb 2013 01:39:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U6Wk5-0005GN-QV; Sat, 16 Feb 2013 01:39:05 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U6Wk2-0003LH-Ic; Sat, 16 Feb 2013 01:39:05 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1U6Wju-0002sS-4b; Fri, 15 Feb 2013 20:38:54 -0500 Date: Fri, 15 Feb 2013 20:38:54 -0500 From: Bruce Momjian To: Stefan Kaltenbrunner Cc: Josh Berkus , Christoph Berg , Martin Pitt , Magnus Hagander , PostgreSQL WWW , PostgreSQL in Debian , Tom Lane Subject: Re: Re: [pgsql-www] We should not transition to apt.postgresql.org until we have a PPA Message-ID: <20130216013854.GD12029@momjian.us> References: <20130214122643.GF30046@msgid.df7cb.de> <511D2E58.6010705@agliodbs.com> <511D4E61.5050808@kaltenbrunner.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <511D4E61.5050808@kaltenbrunner.cc> User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -1.9 (-) X-Mailing-List: pgsql-pkg-debian List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Precedence: bulk Sender: pgsql-pkg-debian-owner@postgresql.org On Thu, Feb 14, 2013 at 09:51:45PM +0100, Stefan Kaltenbrunner wrote: > > (2) Problem with general process > > > > The instructions expressed on the page involve 6 steps, three of which > > require editing text files with persnickety syntax, thus requiring an > > intimate knowledge of Debian packaging, and mapping your numerical > > release number to the "cute" release names, and rearranging lines of a > > large complex system-generated file, and messing with repository keys. > > > not sure what the "intimitate knowledge requirement" here is - pasting > exactly the strings proposed is enough and there is not a single > requirement on understanding debian packaging, though i have to admit > that NOT understanding it is kinda a sign that you should not have root > on the debian based box you are on and you are an admin for. I don't think "codename" is really good wording here: Edit the file /etc/apt/sources.list.d/pgdg.list, and add a line for the repository, substituting the proper "codename" for your release deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main Shouldn't we highlight where that name goes? I am running Squeeze and though I know "precise" is a code-name, I found out only by accident. I particularly think users will not recognize codenames of Debian release newer than their own. I suggest this wording: Edit the file /etc/apt/sources.list.d/pgdg.list, and add a line for the repository, substituting the proper Debian release name: http://apt.postgresql.org/pub/repos/apt/ release-name-pgdg main Also, we should tell users how to find their release name. I looked on Debian and I can't even find out how to find the name, though I know it is Squeeze. I am using Ubuntu 12.04 on my laptop and I don't know the release name of that, nor do I know how to find it. Also, can't we change this to use a shell? Package: * Pin: release o=apt.postgresql.org Pin-Priority: 500 as in: sudo cat > /etc/apt/preferences.d/pgdg.pref < http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-pkg-debian mailing list (pgsql-pkg-debian@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-pkg-debian