Bill Allombert wrote:
>> This is very strange and I doubt it has anything to do with mit-scheme.
>> If you look at the maintainer scripts, you'll see that the code to
>> manipulate the emacs files is boilerplate, automatically generated by
>> debhelper. The mit-scheme package doesn't do any expli
On Mon, Sep 18, 2006 at 09:31:15PM -0400, Chris Hanson wrote:
> Bill Allombert wrote:
>
> > Yes, I know, this is why I wrote exactly what command I was using.
> > I ddes not occur if you omit a single package.
>
> This is very strange and I doubt it has anything to do with mit-scheme.
> If you l
Bill Allombert wrote:
> Yes, I know, this is why I wrote exactly what command I was using.
> I ddes not occur if you omit a single package.
This is very strange and I doubt it has anything to do with mit-scheme.
If you look at the maintainer scripts, you'll see that the code to
manipulate the em
On Mon, Sep 18, 2006 at 01:23:26AM -0400, Chris Hanson wrote:
> Bill Allombert wrote:
> > Package: mit-scheme
> > Version: 7.7.90+20060414-1
> > Severity: serious
> >
> > Hello Chris,
> >
> > when upgrading from sarge to etch in some circumstances, the following
> > problem occur:
>
> > This is
Package: mit-scheme
Version: 7.7.90+20060414-1
Severity: serious
Hello Chris,
when upgrading from sarge to etch in some circumstances, the following
problem occur:
Preparing to replace emacs21-bin-common 21.4a-1 (using
.../emacs21-bin-common_21.4a-6_i386.deb) ...
Unpacking replacement emacs
5 matches
Mail list logo
