Re: autoup.sh + deselect broke emacs
"Young, Ed" <[EMAIL PROTECTED]> writes: > Thanx for the fast replies. > > I'd like to have two emacsen if possible or one that will fit the bill for > both purposes. The machine I'm working on upgrading is going to be an > experimental Amateur radio packet machine and is somewhat minimalist. (486 > dx66 w 8Megs, ~600Megs HD) I want to be able to run emacs from the console > occasionaly and from X normaly. I've never used Xemacs but I doubt it will > run from the console, but I've heard good things about it. Currently, X > isn't working and until I get X working on this machine (a whole nother > thread) I'd like to try it as long as it will coexist with GNU Emacs. > Any comments or caveats or experiences here? Both emacs and xemacs run fine on both the console and under X-windows. Xemacs is somewhat spiffier under X, and comes with more packages pre- installed than emacs. All four of the emacsen packages can be installed simultaneously, thanks to the hard work of several Debian developers. HTH, Norris -- Norris Preyer (541) 962-3310 (office) Physics Program (541) 962-3873 (fax) Eastern Oregon University [EMAIL PROTECTED] La Grande, OR 97850http://physics.eou.edu/npreyer.html -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
RE: autoup.sh + deselect broke emacs
On Wed, 8 Jul 1998, Young, Ed wrote: > > > Ok, I'm still confused... > > Emacs? Not part of the current distribution? This is alarming. No, that's not what I meant. IIRC, there was once emacs and now there are emacs19 and emacs20 and no plain "emacs". If you have a bo "emacs" package, you could/should replace it by one of the hamm versions (I don't use it, so am not sure what differences there are between the two). > > I'm not sure what you mean by "not to worry" since the upgrade has broken > Emacs and now it is catagorized as "obsolete" meaning it is not part of the > current distrubution. > > I'm certain that there must be a way to fix emacs in hamm. Is it by using > Deselect, and just selecting it for upgrade? (a loathsome download > nightmare). Probably the safest thing to do would be to run dselect and select emacs19. This conflicts with emacs and the old version will be removed when the newer one is installed. According to the Packages file, emacs19 shows this conflict, while emacs20 does not and would not remove the older version. They don't appear to conflict with each other, so presumably one could have both. > > Perhaps I should get a clue on the use of dpkg or apt since it seems most on > this list avoid deselect in favor of dpkg if only one package is to be > installed, emacs in this case. I typically use dselect with the apt method or apt-get. apt-get can determine dependencies and will get the necessary packages, which is an improvement over dpkg. Bob Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
RE: autoup.sh + deselect broke emacs
Thanx for the fast replies. I'd like to have two emacsen if possible or one that will fit the bill for both purposes. The machine I'm working on upgrading is going to be an experimental Amateur radio packet machine and is somewhat minimalist. (486 dx66 w 8Megs, ~600Megs HD) I want to be able to run emacs from the console occasionaly and from X normaly. I've never used Xemacs but I doubt it will run from the console, but I've heard good things about it. Currently, X isn't working and until I get X working on this machine (a whole nother thread) I'd like to try it as long as it will coexist with GNU Emacs. Any comments or caveats or experiences here? My priorities: Emacs (of some variety) X AX25Utils. I also need to be able to compile and do some code development. Thanx, Ed > Subject: Re: autoup.sh + deselect broke emacs > > "Young, Ed" <[EMAIL PROTECTED]> writes: > > > Ok, I'm still confused... > > > > Emacs? Not part of the current distribution? This is alarming. > > There are now *four* emacsen in hamm: emacs-19.34, emacs-20.2, > xemacs-19.16, and xemacs-20.4, and you need to choose which you want. > The "emacs" package is obsolete because of the greater variety > provided in hamm. And yes, you do need up upgrade to use the new > libc6-based programs. > > > > > I'm not sure what you mean by "not to worry" since the upgrade has > broken > > Emacs and now it is catagorized as "obsolete" meaning it is not part of > the > > current distrubution. > > > > I'm certain that there must be a way to fix emacs in hamm. Is it by > using > > Deselect, and just selecting it for upgrade? (a loathsome download > > nightmare). > > On a 28.8k modem it doesn't take *that* long, just two or three hours :) > > > > > Perhaps I should get a clue on the use of dpkg or apt since it seems > most on > > this list avoid deselect in favor of dpkg if only one package is to be > > installed, emacs in this case. > > No, I think many debian-users use the apt method *inside* deslect: it > handles dependency ordering correctly, so you don't need multiple passes > of install/configure which the vanilla dselect sometimes requires. But > dselect will do just fine here. > > > > Norris > > -- > Norris Preyer (541) 962-3310 (office) > Physics Program (541) 962-3873 (fax) > Eastern Oregon University [EMAIL PROTECTED] > La Grande, OR 97850 http://physics.eou.edu/npreyer.html -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: autoup.sh + deselect broke emacs
"Young, Ed" <[EMAIL PROTECTED]> writes: > Ok, I'm still confused... > > Emacs? Not part of the current distribution? This is alarming. There are now *four* emacsen in hamm: emacs-19.34, emacs-20.2, xemacs-19.16, and xemacs-20.4, and you need to choose which you want. The "emacs" package is obsolete because of the greater variety provided in hamm. And yes, you do need up upgrade to use the new libc6-based programs. > > I'm not sure what you mean by "not to worry" since the upgrade has broken > Emacs and now it is catagorized as "obsolete" meaning it is not part of the > current distrubution. > > I'm certain that there must be a way to fix emacs in hamm. Is it by using > Deselect, and just selecting it for upgrade? (a loathsome download > nightmare). On a 28.8k modem it doesn't take *that* long, just two or three hours :) > > Perhaps I should get a clue on the use of dpkg or apt since it seems most on > this list avoid deselect in favor of dpkg if only one package is to be > installed, emacs in this case. No, I think many debian-users use the apt method *inside* deslect: it handles dependency ordering correctly, so you don't need multiple passes of install/configure which the vanilla dselect sometimes requires. But dselect will do just fine here. > > Ed > > * > Ed Young (303)706-5425 > [EMAIL PROTECTED] > Software Engineering > Echostar Technology Corporation > Denver, Colorado > * Norris -- Norris Preyer (541) 962-3310 (office) Physics Program (541) 962-3873 (fax) Eastern Oregon University [EMAIL PROTECTED] La Grande, OR 97850http://physics.eou.edu/npreyer.html -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
RE: autoup.sh + deselect broke emacs
Ok, I'm still confused... Emacs? Not part of the current distribution? This is alarming. I'm not sure what you mean by "not to worry" since the upgrade has broken Emacs and now it is catagorized as "obsolete" meaning it is not part of the current distrubution. I'm certain that there must be a way to fix emacs in hamm. Is it by using Deselect, and just selecting it for upgrade? (a loathsome download nightmare). Perhaps I should get a clue on the use of dpkg or apt since it seems most on this list avoid deselect in favor of dpkg if only one package is to be installed, emacs in this case. Ed * Ed Young (303)706-5425 [EMAIL PROTECTED] Software Engineering Echostar Technology Corporation Denver, Colorado * > -Original Message- > From: Bob Nielsen [SMTP:[EMAIL PROTECTED] > Sent: Wednesday, July 08, 1998 9:01 AM > To: Edward J. Young > Cc: debian list > Subject: Re: autoup.sh + deselect broke emacs > > On Wed, 8 Jul 1998, Edward J. Young wrote: > > > > > > > I should mention that in the deselect screen, there are headings for > > packages that are headed as "obsolete", one being emacs. Does this mean > > what I think: that emacs 19.34.? is now obsolete because I've upgraded > > around it and now it needs upgrading too? Probobly. > > > > There are some other packages labeled "obsolete" as well. > > > > How should this be handled? > > I don't know about emacs (not installed here), but any installed packages > not listed in a Packages file are displayed as "obsolete/local". This > only means that these packages are not part of the current distribution. > > I have several of these, such as apt, pine (the old pre-compiled version), > > my custom kernel-image, etc. Not to worry. > > Bob > > > Bob Nielsen Internet: [EMAIL PROTECTED] > Tucson, AZ AMPRnet: [EMAIL PROTECTED] > DM42nh http://www.primenet.com/~nielsen > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < > /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: autoup.sh + deselect broke emacs
On Wed, 8 Jul 1998, Edward J. Young wrote: > > > I should mention that in the deselect screen, there are headings for > packages that are headed as "obsolete", one being emacs. Does this mean > what I think: that emacs 19.34.? is now obsolete because I've upgraded > around it and now it needs upgrading too? Probobly. > > There are some other packages labeled "obsolete" as well. > > How should this be handled? I don't know about emacs (not installed here), but any installed packages not listed in a Packages file are displayed as "obsolete/local". This only means that these packages are not part of the current distribution. I have several of these, such as apt, pine (the old pre-compiled version), my custom kernel-image, etc. Not to worry. Bob Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: autoup.sh + deselect broke emacs
i had the same thing happen and i had selected to upgrade emacs to 20.xx...made a mess. it was the only really broken package. had been wanting to check out xemacs so ended up purging emacs and installing xemacs-20.whatever and like it. anyway, suspect you will need to purge emacs and do a clean install. i had to abandon dselect and use dpkg to remove emacs, then ftp'd xemacs packages and used dpkg to install them. best--c On Wed, 8 Jul 1998, Edward J. Young wrote: > > > I should mention that in the deselect screen, there are headings for > packages that are headed as "obsolete", one being emacs. Does this mean > what I think: that emacs 19.34.? is now obsolete because I've upgraded > around it and now it needs upgrading too? Probobly. > > There are some other packages labeled "obsolete" as well. > > How should this be handled? > > > One other question: > Where can I get a CD in the Denver area? I would order a CD of 2.0 but it > seems to still be in a state of flux and I don't want to have a CD which > may or may not have a fully stable Debian system. > > Thanx, > > Ed > > On Wed, 8 Jul 1998, Edward J. Young wrote: > > > > > > > I have upgraded from 1.3.1 to hamm with some difficulty, but feel like > > I'm getting there. My latest problem is that when invoking emacs from a > > console, I get "segmentation fault", and no emacs. > > > > I don't believe that emacs was upgraded during the deselect process so I > > suspect that the version I had (v19.34.?) requires the old libc, though I > > realy don't understand the issues here. > > > > How do I rectify this? By running deselect and upgrading Emacs. I'm loath > > to try that since emacs is huge and a download would be epic, but if > > absolutely necessary I will. > > > > If it matters, My upgrade went like this: > > -autoup.sh > > -deselect with ACCESS UPDATE, INSTALL (No SELECT) > > -several more iterations of INSTALL since the first ones resulted in > > brokenly uninstalled packages. > > -dselect and running SELECT to get X running (but that's another > > posting...) > > > > Now deselect reports no brokenly installed packages and I believe that all > > the necessary packages are now installed. > > > > So again, how do I fix emacs? > > > > Thanx in advance. > > > > Ed > > NL7FU > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > > > > > > > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > == The man PUBLIC DOMAIN, INC. Of virtuous soul commands not, nor obeys: P.O. Box 8899-0899 Power, like a desolating pestilence, Atlanta, GA 30306 Pollutes whate'er it touches, and obedience, VOX: 404.373.0980Bane of all genius, virtue, freedom, truth, FAX: 404.378.3607Makes slaves of men, and, of the human frame, [EMAIL PROTECTED] A mechanised automaton. --Percy Bysshe Shelley = -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: autoup.sh + deselect broke emacs
I should mention that in the deselect screen, there are headings for packages that are headed as "obsolete", one being emacs. Does this mean what I think: that emacs 19.34.? is now obsolete because I've upgraded around it and now it needs upgrading too? Probobly. There are some other packages labeled "obsolete" as well. How should this be handled? One other question: Where can I get a CD in the Denver area? I would order a CD of 2.0 but it seems to still be in a state of flux and I don't want to have a CD which may or may not have a fully stable Debian system. Thanx, Ed On Wed, 8 Jul 1998, Edward J. Young wrote: > > > I have upgraded from 1.3.1 to hamm with some difficulty, but feel like > I'm getting there. My latest problem is that when invoking emacs from a > console, I get "segmentation fault", and no emacs. > > I don't believe that emacs was upgraded during the deselect process so I > suspect that the version I had (v19.34.?) requires the old libc, though I > realy don't understand the issues here. > > How do I rectify this? By running deselect and upgrading Emacs. I'm loath > to try that since emacs is huge and a download would be epic, but if > absolutely necessary I will. > > If it matters, My upgrade went like this: > -autoup.sh > -deselect with ACCESS UPDATE, INSTALL (No SELECT) > -several more iterations of INSTALL since the first ones resulted in > brokenly uninstalled packages. > -dselect and running SELECT to get X running (but that's another > posting...) > > Now deselect reports no brokenly installed packages and I believe that all > the necessary packages are now installed. > > So again, how do I fix emacs? > > Thanx in advance. > > Ed > NL7FU > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > > > -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
autoup.sh + deselect broke emacs
I have upgraded from 1.3.1 to hamm with some difficulty, but feel like I'm getting there. My latest problem is that when invoking emacs from a console, I get "segmentation fault", and no emacs. I don't believe that emacs was upgraded during the deselect process so I suspect that the version I had (v19.34.?) requires the old libc, though I realy don't understand the issues here. How do I rectify this? By running deselect and upgrading Emacs. I'm loath to try that since emacs is huge and a download would be epic, but if absolutely necessary I will. If it matters, My upgrade went like this: -autoup.sh -deselect with ACCESS UPDATE, INSTALL (No SELECT) -several more iterations of INSTALL since the first ones resulted in brokenly uninstalled packages. -dselect and running SELECT to get X running (but that's another posting...) Now deselect reports no brokenly installed packages and I believe that all the necessary packages are now installed. So again, how do I fix emacs? Thanx in advance. Ed NL7FU [EMAIL PROTECTED] [EMAIL PROTECTED] -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
