[6483] in Release_7.7_team
Re: Cluster repository for third-party software not in Ubuntu
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Fri Oct 23 15:39:21 2009
Date: Fri, 23 Oct 2009 15:39:13 -0400 (EDT)
From: Geoffrey Thomas <geofft@MIT.EDU>
To: debathena@mit.edu, release-team@mit.edu
In-Reply-To: <alpine.DEB.2.00.0910231510420.5891@beautiful-katamari.csail.mit.edu>
Message-ID: <alpine.DEB.2.00.0910231532180.5891@beautiful-katamari.csail.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Flag: NO
X-Spam-Score: 0.00
Er, I forgot to mention -- while it's true that Canonical packages
acroread in the partner repository <http://archive.canonical.com/ubuntu>,
I'm not sure how much I trust the partner repo to be timely about security
updates.
Also, Adobe's website seems to be fairly behind, in offering me 9.1.2. The
partner repository offers 9.1.3 (as of August 4), and alexp's current
source <ftp://ftp.adobe.com/pub/adobe/reader/unix/> offers 9.1.3 (as of
July 31) and 9.2 (as of October 13).
--
Geoffrey Thomas
geofft@mit.edu
On Fri, 23 Oct 2009, Geoffrey Thomas wrote:
> alexp wants us to be able to install Adobe's .debs for Acrobat locally on
> cluster machines. This will make Acrobat significantly faster than running it
> out of AFS. On old-Athena we did this by making the acro and infoagents
> locker local, but nobody is particularly interested in replicating the
> local-locker infrastructure.
>
> I don't really want to put Adobe's .debs in the current Debathena apt
> repository, so I propose that we create a second apt repository in the
> debathena locker with name "apt-cluster" or somesuch, and give alexp bits to
> it, so he can use reprepro to upload Adobe's .debs there. If there are other
> third-party .debs we want on cluster machines, they could also go there, and
> they could be dependencies of debathena-thirdparty. We'd then make something
> (possibly debathena-thirdparty) configure this repo on cluster machines in
> /etc/apt/sources.list.d.
>
> The other option here I can think of is making the athena-auto-update script
> also look at the Adobe web page / ftp directory for new .debs, and download
> and install them by hand outside of an apt repository, but I'm afraid of
> having that break in interesting ways. The apt-cluster repo gives a small
> level of manual control and awareness of what packages we're pulling in.
>
> Does creating this additional apt repo sound reasonable?
>
>
