Re: upgrading to slink 2.1r4
scratch wrote: > what is the correct way to upgrade to slink2.1r4 using apt? > > apt-get update; apt-get dist-upgrade?? > > Doing this only upgrades 12 minor packages on my original 2.1 system. Yes, that's quite right. This is a minor release, fixing only security holes and some y2k problems. -- see shy jo
upgrading to slink 2.1r4
Hi, what is the correct way to upgrade to slink2.1r4 using apt? apt-get update; apt-get dist-upgrade?? Doing this only upgrades 12 minor packages on my original 2.1 system. Please cc: any replies to me, as i'm not on the list. --nico :: Nico Galoppo :: Linux - Free power for the masses : :: :. :: :: :: scratch at ace.ulyssis.student.kuleuven.ac.be :: : http://scratchor.dhs.org :: . .::
upgrading to Slink
Hello all. As subject says, I'm thinking about upgrading to 2.1 system from 2.0.36 I don't want to use apt to do an automatic upgrade while I'm gone, just because of the ISP issues. I was wondering if there was a list of packages that have been modified at the hamm->slink transition, and that are crucial to the system (like glibc, kernel, etc?), and if so, where would I find one. Thanks in advance, Andrew
Re: lost telnet after upgrading to slink
*- On 14 May, Eugene Sevinian wrote about "lost telnet after upgrading to slink" > Hi, > recently I got Debian 2.1 from CheapBytes. Upgrading from hamm was > done without any warnings, errors. However, it seems that new system had > lost telnet...:( (No such file!). At the same time everything is ok with > ftp. Should I reinstall netbase or whatever else which contains telnet? > > TIA, > > Eugene Sevinian > > > CRD, YerPhI, 375036, Armenia > URL: http://crdlx5.yerphi.am/ > Phone: 374-2-344873 > > Read the Release notes file on the cd. In section 4.3 you will find: net/netstd_3.07-2.deb split into 10 packages: mail/vrfy net/bwnfsd net/netstd net/nfs-server net/rexec net/talk net/talkd net/telnet net/telnetd non-free/net/pcnfsd Thus telnet is now in its own package. -- Brian - Mechanical Engineering [EMAIL PROTECTED] Purdue University http://www.ecn.purdue.edu/~servis -
lost telnet after upgrading to slink
Hi, recently I got Debian 2.1 from CheapBytes. Upgrading from hamm was done without any warnings, errors. However, it seems that new system had lost telnet...:( (No such file!). At the same time everything is ok with ftp. Should I reinstall netbase or whatever else which contains telnet? TIA, Eugene Sevinian CRD, YerPhI, 375036, Armenia URL: http://crdlx5.yerphi.am/ Phone: 374-2-344873
RE: StarOffice no longer works after upgrading to Slink
On 11-May-99 Daniel Mashao wrote: > Any help? Unlike the tough guys who have problems with SO in potato, I > have a problem with SO in slink. It worked fine in my previous hamm/slink > setting, now it just Aborts. I have tried some of the suggestions I have > seen for potato but they do not work. Any ideas? Have you tried reinstalling SO ? That usually fixes this problem. -- Andrew [PGP5.0 KeyID 0x5EE61C37]
StarOffice no longer works after upgrading to Slink
Any help? Unlike the tough guys who have problems with SO in potato, I have a problem with SO in slink. It worked fine in my previous hamm/slink setting, now it just Aborts. I have tried some of the suggestions I have seen for potato but they do not work. Any ideas? /--/ Daniel J. Mashao Electrical Engineering [EMAIL PROTECTED] University of Cape Town http://www.ee.uct.ac.za/~daniel Rondebosch, 7700, S. Africa (w) 27+21+650 2816 (h) 27+21+705 8469 /--/
Re: upgrading to slink from hamm
Pere Camps wrote: > > Hi! > > What update procedure should I use in order to upgrade to slink > from hamm? Just point dftp to the new ftp directory and upgrade? > > What are the main differences between the two releases (ie: smail > vs exim), that I need to look up to make sure they work after upgrading? > > I'm running a server for 400 people here and if something goes > wrong, I'll get beheaded... ;) A) If the system is important, then wait for slink to be released as stable. If you have another system, upgrade on that machine and see if there are any problems, before upgrading your server. B) If you haven't already, get apt and either use it from the command line, or from dselect (what I do). Apt is a little smarter about the order of packages to be installed. C) Hamm had a complicated upgrade because hamm introduced the new system lib (libc6). hamm to slink should be much easier. -- Ed C.
upgrading to slink from hamm
Hi! What update procedure should I use in order to upgrade to slink from hamm? Just point dftp to the new ftp directory and upgrade? What are the main differences between the two releases (ie: smail vs exim), that I need to look up to make sure they work after upgrading? I'm running a server for 400 people here and if something goes wrong, I'll get beheaded... ;) TIA! -- p.
RE: upgrading to slink
On 05-Feb-99 [EMAIL PROTECTED] wrote: > Just out of curiosity, as I upgrade to slink, I'm wondering if I need to > upgrade all my packages as well. For example, if there is a package in hamm > and slink with the same name and version, are they in fact the same exact > package? Or is one only for slink, the other for hamm? My guess is they are > the same - am I correct? If so, why would there be copies in both the hamm > and slink distribution sites? > If they are the exact same version, the package is actually in the older ditribution and a link exists in the newer one pointing to it. base/admin_5.1-0.1.deb -> ../.../dists/hamm/base/admin_5.1-0.1.deb
Re: upgrading to slink
[EMAIL PROTECTED] wrote: > > Just out of curiosity, as I upgrade to slink, I'm wondering if I need to > upgrade all my packages as well. For example, if there is a package in hamm > and slink with the same name and version, are they in fact the same exact > package? Or is one only for slink, the other for hamm? My guess is they are > the same - am I correct? If so, why would there be copies in both the hamm > and slink distribution sites? > > -Jay The packages with the same version number, are in fact identical; they are the same package. Take a look in the dirs that hold the packages on ftp.debian.org or mirror. You'll notice that packages who haven't changed between releases are not copied, but a symlink is used to point to the older version in the older release. -- Ed C.
upgrading to slink
Just out of curiosity, as I upgrade to slink, I'm wondering if I need to upgrade all my packages as well. For example, if there is a package in hamm and slink with the same name and version, are they in fact the same exact package? Or is one only for slink, the other for hamm? My guess is they are the same - am I correct? If so, why would there be copies in both the hamm and slink distribution sites? -Jay
Re: upgrading to slink
On Thu, Dec 03, 1998 at 06:10:44 -0500, David Randall wrote: > Here are the broken packages: > size broken Next "unbroken" release > 93182 libstdc++2.8_2.90.29-1.deb ??? libstdc++2.8_2.90.29-2, which should be on most mirrors by now has been recompiled with the fixed libc6. > 95086 libstdc++2.9_2.91.58-5.deb libstdc++2.9_2.91.59-1.deb -1 never made it out of Incoming; libstdc++2.9_2.91.59-2 is starting to appear on the mirrors now. Ray -- Obsig: developing a new sig
Re: upgrading to slink
On Wed, 2 Dec 1998, E.L. Meijer (Eric) wrote: > > > > I see no upgrade notes for slink. > > That's right, it is not released yet. > > > For hamm, these upgrade notes reside in > >.../hamm/hamm/upgrade-i386/README-upgrade > > Usually, I just use dpkg to install whatever packages I want from the > > upgrade distribution. For example, I might install a newer gimp from slink. > > Since I wouldn't have upgraded the base packages, I learned that using > > dpkg prematurely can cause little problems. > > Upgrading from rex to bo: I EVENTUALLY HAD TO REINSTALL FROM SCRATCH. > > I did this, without problems, but only after bo had been released. > > > Upgrading from bo to hamm: I EVENTUALLY HAD TO REINSTALL FROM SCRATCH. > > I did this too, and had to fix some bugs in the upgrade script by > hand, but eventually succeeded. I agree that this upgrade procedure was > by no means easy for someone without more extensive debian/unix > knowledge. > I chose to install from scratch because I had a good idea of how Debian Linux worked and wanted to change some things; partitions mainly, moved HD to another computer. > > Upgrading from hamm to slink: WHAT CAN I EXPECT. > > If you had trouble upgrading before, and could not fix it yourself or > with help from this list THEN DONT TRY TO UPGRADE TO AN UNSTABLE/FROZEN > DISTRIBUTION. > I started to download the slink distribution and install parts as I downloaded them. There were some dependency problems, but mainly a problem with libstdc++2.* packages. I thought installing other packages would work, but it only made the matters worse. There are other e-mails in this list about "libstdc++ : __register_frame_info" breaking many packages. Since I have Netscape that uses the old 2.8 libs, I installed both 2.8 and 2.9 packages. Both had problems. After ftp'ing older packages, I had to dpkg --install both since dselect was broken! Moral of the story... If you are new and can't work around problems, then wait until it becomes stable. Here are the broken packages: size broken Next "unbroken" release 93182 libstdc++2.8_2.90.29-1.deb ??? 95086 libstdc++2.9_2.91.58-5.deb libstdc++2.9_2.91.59-1.deb If you look on the bug list, there is a write-up from the maintainer. If you have a problem, check the bug list and see if it's been reported. If not, then report it. > > With no instructions, I certainly will not use raw dpkg to add packages > > from slink to my current hamm distribution -- > > unless of course "dependencies" prevent this (do they now?). dselect works fine for me, except when it doesn't work. Then I had to use dpkg. > > Dependencies do not protect you from broken packages. Slink has not > been announced as being stable, so it is known to contain broken > packages. In other words: upgrade now and be assured of getting some > broken packages (well, almost assured). I think if there is no real > compelling reason to upgrade, it is best to wait for slink to be > released, and then wait a little longer after that and watch this list > carefully to see what problems could be expected. And please don't > shout on this list, we're all fellow users and volunteers. > > HTH, > Eric, who is typing this on a bo system, since it is perfectly capable > of what he needs it for. > > > -- > E.L. Meijer ([EMAIL PROTECTED]) | tel. office +31 40 2472189 > Eindhoven Univ. of Technology | tel. lab. +31 40 2475032 > Lab. for Catalysis and Inorg. Chem. (TAK) | tel. fax+31 40 2455054 >
Re: upgrading to slink
On Wed, 2 Dec 1998, Jameson Burt wrote: : I see no upgrade notes for slink. : For hamm, these upgrade notes reside in :.../hamm/hamm/upgrade-i386/README-upgrade : Usually, I just use dpkg to install whatever packages I want from the : upgrade distribution. For example, I might install a newer gimp from slink. : Since I wouldn't have upgraded the base packages, I learned that using : dpkg prematurely can cause little problems. : Upgrading from rex to bo: I EVENTUALLY HAD TO REINSTALL FROM SCRATCH. : Upgrading from bo to hamm: I EVENTUALLY HAD TO REINSTALL FROM SCRATCH. : : Upgrading from hamm to slink: WHAT CAN I EXPECT. : With no instructions, I certainly will not use raw dpkg to add packages : from slink to my current hamm distribution -- : unless of course "dependencies" prevent this (do they now?). You're always taking a risk when you use unstable or frozen. Having said that, I've found that using `apt-get install ' to be very good about not hosing dependencies. If you ever use `dpkg --force' you get what you deserve. -- Nathan Norman MidcoNet 410 South Phillips Avenue Sioux Falls, SD mailto:[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)
Re: upgrading to slink
> > I see no upgrade notes for slink. That's right, it is not released yet. > For hamm, these upgrade notes reside in >.../hamm/hamm/upgrade-i386/README-upgrade > Usually, I just use dpkg to install whatever packages I want from the > upgrade distribution. For example, I might install a newer gimp from slink. > Since I wouldn't have upgraded the base packages, I learned that using > dpkg prematurely can cause little problems. > Upgrading from rex to bo: I EVENTUALLY HAD TO REINSTALL FROM SCRATCH. I did this, without problems, but only after bo had been released. > Upgrading from bo to hamm: I EVENTUALLY HAD TO REINSTALL FROM SCRATCH. I did this too, and had to fix some bugs in the upgrade script by hand, but eventually succeeded. I agree that this upgrade procedure was by no means easy for someone without more extensive debian/unix knowledge. > Upgrading from hamm to slink: WHAT CAN I EXPECT. If you had trouble upgrading before, and could not fix it yourself or with help from this list THEN DONT TRY TO UPGRADE TO AN UNSTABLE/FROZEN DISTRIBUTION. > With no instructions, I certainly will not use raw dpkg to add packages > from slink to my current hamm distribution -- > unless of course "dependencies" prevent this (do they now?). Dependencies do not protect you from broken packages. Slink has not been announced as being stable, so it is known to contain broken packages. In other words: upgrade now and be assured of getting some broken packages (well, almost assured). I think if there is no real compelling reason to upgrade, it is best to wait for slink to be released, and then wait a little longer after that and watch this list carefully to see what problems could be expected. And please don't shout on this list, we're all fellow users and volunteers. HTH, Eric, who is typing this on a bo system, since it is perfectly capable of what he needs it for. -- E.L. Meijer ([EMAIL PROTECTED]) | tel. office +31 40 2472189 Eindhoven Univ. of Technology | tel. lab. +31 40 2475032 Lab. for Catalysis and Inorg. Chem. (TAK) | tel. fax+31 40 2455054
Re: upgrading to slink
I have written a page for how to upgrade from HAMM to SLINK. It goes from a stock non apt-get HAMM distro to installing apt-get to upgrading to SLINK. It's located at http://www.tdyc.com/archive/slinkup.html/index.html I wrote it for a friend who kept asking me how to do the upgrade and he never remembered what I told him. This stoped the questions. :) I have successfully upgraded to SLINK 7 seperate machines with no problems (except when problems arise in the actual distro which usually get fixed within 24-48 hours). This document should help you...if not answer any questions you might have about upgrading to SLINK. Ivan Quoting Jameson Burt <[EMAIL PROTECTED]>: > I see no upgrade notes for slink. > For hamm, these upgrade notes reside in >.../hamm/hamm/upgrade-i386/README-upgrade > Usually, I just use dpkg to install whatever packages I want from the > upgrade distribution. For example, I might install a newer gimp from > slink. > Since I wouldn't have upgraded the base packages, I learned that using > dpkg prematurely can cause little problems. > Upgrading from rex to bo: I EVENTUALLY HAD TO REINSTALL FROM SCRATCH. > Upgrading from bo to hamm: I EVENTUALLY HAD TO REINSTALL FROM SCRATCH. > > Upgrading from hamm to slink: WHAT CAN I EXPECT. > With no instructions, I certainly will not use raw dpkg to add packages > from slink to my current hamm distribution -- > unless of course "dependencies" prevent this (do they now?). > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < > /dev/null > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ivan E. Moore IIRev. Krusty http://www.tdyc.com[EMAIL PROTECTED] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Imagination is more important than knowledge - Albert Einstien =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
upgrading to slink
I see no upgrade notes for slink. For hamm, these upgrade notes reside in .../hamm/hamm/upgrade-i386/README-upgrade Usually, I just use dpkg to install whatever packages I want from the upgrade distribution. For example, I might install a newer gimp from slink. Since I wouldn't have upgraded the base packages, I learned that using dpkg prematurely can cause little problems. Upgrading from rex to bo: I EVENTUALLY HAD TO REINSTALL FROM SCRATCH. Upgrading from bo to hamm: I EVENTUALLY HAD TO REINSTALL FROM SCRATCH. Upgrading from hamm to slink: WHAT CAN I EXPECT. With no instructions, I certainly will not use raw dpkg to add packages from slink to my current hamm distribution -- unless of course "dependencies" prevent this (do they now?).
