|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Tue, 14 Apr 2009 02:01:07 -0400 (EDT) From: Geoffrey Thomas <geofft@MIT.EDU> To: release-team@mit.edu cc: debathena@mit.edu In-Reply-To: <alpine.DEB.2.00.0903201820070.15223@w20-575-72.mit.edu> Message-ID: <alpine.DEB.2.00.0904140155210.6367@corndog.mit.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Flag: NO X-Spam-Score: 0.00 Since the SRU for getting a working mit-scheme on Intrepid seems to be going nowhere, I haven't seen the guy who said he'd deal with the bug on IRC, and I imagine the entire Ubuntu project has more pressing things than SRUs for Intrepid to deal with this weak, I've uploaded a version of debathena-thirdparty-languages that doesn't have mit-scheme to -proposed. If/when mit-scheme works on Intrepid (or when we move our focus to Jaunty), we can re-add it trivially. Tomorrow, after the existing debathena-cluster in -proposed gets released, I intend to upload a version that has debathena-thirdparty as a dependency, and move that to production by the end of the week. This means that all the cluster Debathena machines will install debathena-thirdparty and its dependencies when they take that update. I don't believe there were objections to this when I raised it a few weeks back, other than that we should make sure that mit-scheme eventually gets to clusters. If any others have developed, please let me know soon. On a tangential note, if anyone has a Jaunty system sufficiently close to what clusters are like, I'd be interested in knowing how well debathena-thirdparty's dependencies are satisfied or if we need to do any wrestling. (`aptitude -s install debathena-thirdparty` should do this.) -- Geoffrey Thomas geofft@mit.edu On Fri, 20 Mar 2009, Geoffrey Thomas wrote: > I just moved my most recent fixes to debathena-thirdparty to production as > discussed in yesterday's -proposed report, and debathena-thirdparty is now > installable on cluster machines. mit-scheme remains uninstallable, but should > be fixed Real Soon Now, per https://bugs.launchpad.net/bugs/341832 , and at > that point we can make the package a dependency instead of a recommendation. > The rest of the uninstallable packages are libraries that I think we > discussed already and have decided we're fine with ignoring for now. > > I've pasted the output of aptitude below: the important point is that the > package is now installable. Can we go ahead and add -thirdparty as a > dependency of cluster, so this software is installed the next time cluster > systems update? > > [aptitude output snipped]
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |