Re: Unstable release
On Wed, Oct 06, 1999 at 02:12:08PM +0200, Staffan Hämälä was heard to say: > > NO, NO, NO, this is not redhat.com! Do this on a Debian only if you really > > know what you are doing or you may destroy your system. > > As far as I can see there is often not another way to do it. > Ie., program complains over a lib that is too old. If you try > to install the lib it complains over that there is already an > old version there. That's one of the problems I've encountered > quite a lot of times with Debian, and one of the times I've had > to use the force options. Could you give an example? I'm vague here on what your problem is. > As for the problem with conflicting library versions or whatever > you risk getting into when using --force*, I find that to be > a smaller problem than the problems I get when dpkg complains > about old versions that risk being overwritten. > > Btw, is it possible to tell dpkg to install all dependencies > automagically? > > /Staffan apt is for dependency resolution. Use it. (if there's a reason you can't use it, file bug reports until you can :) ) Daniel -- DROP THE SCYTHE AND TURN AROUND SLOWLY. -- Terry Pratchett, "Reaper Man"
Re: Unstable release
On Tue, 05 Oct 1999, Stephane Bortzmeyer wrote: > > If I could just get it installed properly (I run it at home, > > but had to do a lot of manual tuning, and adding all packages > > I wanted using dpkg --force* > > NO, NO, NO, this is not redhat.com! Do this on a Debian only if you really > know what you are doing or you may destroy your system. As far as I can see there is often not another way to do it. Ie., program complains over a lib that is too old. If you try to install the lib it complains over that there is already an old version there. That's one of the problems I've encountered quite a lot of times with Debian, and one of the times I've had to use the force options. As for the problem with conflicting library versions or whatever you risk getting into when using --force*, I find that to be a smaller problem than the problems I get when dpkg complains about old versions that risk being overwritten. Btw, is it possible to tell dpkg to install all dependencies automagically? /Staffan
Re: Unstable release
apt-get update apt-get dist-upgrade These two lines should be run after you update your /etc/apt/source.list to point to unstable. Dave Bristel On Mon, 4 Oct 1999, [iso-8859-1] Staffan Hämälä wrote: > Date: Mon, 4 Oct 1999 20:44:48 +0200 > From: "[iso-8859-1] Staffan Hämälä" <[EMAIL PROTECTED]> > To: debian-devel@lists.debian.org > Subject: Unstable release > Resent-Date: 4 Oct 1999 18:45:06 - > Resent-From: debian-devel@lists.debian.org > Resent-cc: recipient list not shown: ; > > Hi, > > I'm just curious about how other people succeed in installing the > potato release. Myself, I have always had _lots_ of trouble when > trying that. First, I installed it at home, and dselect freaked > out and started complaining over files that didn't exist. This > was due to the fact that ftp downloads the softlinks that point > to slink packages instead of the actual files. That time I had > downloaded the whole lot with ncftp. I downloaded another time > using wget with the option to get real files. That worked better, > and dselect found all files. Still, the big problem was dselect > because it complained about so many things it flipped out and > refused to install any more packages (I barely got a working > system). > Last week I tried the same thing at work, installing over ftp, > and I thik the installer also downloaded just the links, but > not the actual files, so this time I wasn't even able to boot > the system after running dselect. After this I installed slink > instead, and it worked like a charm. > > Of course, I know that it's an unstable release, but is it really > this hard to install, or is it me doing something wrong? > If I could just get it installed properly (I run it at home, > but had to do a lot of manual tuning, and adding all packages > I wanted using dpkg --force* instead of dselect), I would > be glad to report problems, and also fix some, but as it > is now that the installation doesn't seem to work at all > for me I really don't feel like reporting problems because > the fault probably lies in my installation anyway. > > How are you installing potato? Is there some magic way > to make ftp install work when there are soft links on > the server? Is there a way to make dselect go on installing > other packages even though it finds ten faulty packages > first in the list? (This way I could add those ten manually > afterwards). > > Thanks, > > Staffan Hamala > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: Unstable release
On Monday 4 October 1999, at 20 h 44, the keyboard of =?iso-8859-1?Q?Staffan_H=E4m=E4l=E4?= <[EMAIL PROTECTED]> wrote: > I'm just curious about how other people succeed in installing the > potato release. As explained, almost nobody "installed" potato. They installed slink (may be only the base system) and upgraded. > trying that. First, I installed it at home, and dselect freaked > out and started complaining over files that didn't exist. The "unstable" (it is called unstable for a reason) archive is not always consistent (rsh/netbase, lyx/libforms, etc). > was due to the fact that ftp downloads the softlinks that point > to slink packages instead of the actual files. I always use apt, so I will no longer comment on dselect. > Of course, I know that it's an unstable release, but is it really > this hard to install, Install slink, the upgrade with apt. Simple as that. > If I could just get it installed properly (I run it at home, > but had to do a lot of manual tuning, and adding all packages > I wanted using dpkg --force* NO, NO, NO, this is not redhat.com! Do this on a Debian only if you really know what you are doing or you may destroy your system.
Re: Unstable release
On Mon, 04 Oct 1999, Daniel Burrows wrote: > I usually use apt to fetch via ftp, but pointing it at a source archive > should do the same thing. Are you using it as a dselect backend, or are > you doing something else entirely? I'm using it via dselect. I'll have to try that once more to be sure that it really didn't follow soft-links, but at least it looked like it didn't as I got exactly the same error-messages that I got when downloading manually with ncftp. > Wait, you mean you're trying to actually *install* potato? I didn't realize Yep.. =) > that boot-floppies even worked again! I think it's usually the case that a > from-scratch install doesn't work until the last minute. I know a Slink Ok, didn't know that. I haven't been using Debian for that long. Switched from Stampede (that I've been running since one of the first betas) in April or something. > I do it with a fairly simple approach. I install the base Slink system, but > on the reboot (after setting a root password :) ) I edit /etc/apt/sources.list > and change all references to "stable" to "unstable". I then proceed as > before. > It may be that the archive is in a weird state at the moment; I haven't done > this for a few months. I recommend just installing a small set of packages > and > then adding stuff by hand in dselect (but I recommend this when setting a new > stable system up as well -- the metapackage/task system is too broken) I'll try that next time. When I installed the last one (with slink), I actually did something similar. I installed the base system with slink, and downloaded the whole potato distribution via ftp, and started adding packages manually with dpkg. This has the drawback that I have to use various --force* options to make it replace the older versions of libraries and other things. Right now it runs ssh, perl, etc from the potato distribution. /Staffan
Re: Unstable release
On Mon, 4 Oct 1999, Daniel Burrows wrote: > On Mon, Oct 04, 1999 at 08:44:48PM +0200, Staffan Hämälä was heard to say: > > > I'm just curious about how other people succeed in installing the > > potato release. > > I do it with a fairly simple approach. I install the base Slink system, but > on the reboot (after setting a root password :) ) I edit /etc/apt/sources.list > and change all references to "stable" to "unstable". I then proceed as > before. This is exactly what I did and it worked perfectly. Although instead of editing /etc/apt/sources.list by hand I changed it from dselect during the install process. Laters, Rick ([EMAIL PROTECTED]) http://rick.chillin.org
Re: Unstable release
On Mon, Oct 04, 1999 at 08:44:48PM +0200, Staffan Hämälä was heard to say: > Hi, > > I'm just curious about how other people succeed in installing the > potato release. *raises hand* I've actually done two things -- the machine I'm typing on has been running unstable since before Slink was frozen, so it's been continuously upgraded for a while. However, I've also upgraded existing Slink systems and installed new systems (sort of, see below) > Myself, I have always had _lots_ of trouble when > trying that. First, I installed it at home, and dselect freaked > out and started complaining over files that didn't exist. This > was due to the fact that ftp downloads the softlinks that point > to slink packages instead of the actual files. That time I had > downloaded the whole lot with ncftp. I downloaded another time > using wget with the option to get real files. That worked better, > and dselect found all files. Still, the big problem was dselect > because it complained about so many things it flipped out and > refused to install any more packages (I barely got a working > system). I usually use apt to fetch via ftp, but pointing it at a source archive should do the same thing. Are you using it as a dselect backend, or are you doing something else entirely? > Last week I tried the same thing at work, installing over ftp, > and I thik the installer also downloaded just the links, but > not the actual files, so this time I wasn't even able to boot > the system after running dselect. After this I installed slink > instead, and it worked like a charm. ^^^ Wait, you mean you're trying to actually *install* potato? I didn't realize that boot-floppies even worked again! I think it's usually the case that a from-scratch install doesn't work until the last minute. I know a Slink installs I tried last January was totally screwed up (dbootstrap (?) didn't properly create fstab and I had to put it together by hand -- and that was the simplest problem. I got a working system though! :) ) > Of course, I know that it's an unstable release, but is it really > this hard to install, or is it me doing something wrong? Yes and yes :) I'll describe my methods below.. > How are you installing potato? Is there some magic way > to make ftp install work when there are soft links on > the server? Is there a way to make dselect go on installing > other packages even though it finds ten faulty packages > first in the list? (This way I could add those ten manually > afterwards). I'll say first that we may have slightly different takes on 'install'; I wouldn't say that installing potato has to be done with the standard boot-floppies as long as you end up with a potato system at the end :) I do it with a fairly simple approach. I install the base Slink system, but on the reboot (after setting a root password :) ) I edit /etc/apt/sources.list and change all references to "stable" to "unstable". I then proceed as before. It may be that the archive is in a weird state at the moment; I haven't done this for a few months. I recommend just installing a small set of packages and then adding stuff by hand in dselect (but I recommend this when setting a new stable system up as well -- the metapackage/task system is too broken) I've never run into problems with this (aside from the usual unstable weirdness); if you're doing this and encountering trouble, could you be more precise about what's going on? apt follows symlinks, as (I believe) does dpkg-ftp. Daniel -- "In the Course of my Observation, these disputing, contradicting & confuting People are generally unfortunate in their Affairs. They get Victory sometimes, but they never get Good Will, which would be of more use to them." -- from the autobiography of Benjamin Franklin
Unstable release
Hi, I'm just curious about how other people succeed in installing the potato release. Myself, I have always had _lots_ of trouble when trying that. First, I installed it at home, and dselect freaked out and started complaining over files that didn't exist. This was due to the fact that ftp downloads the softlinks that point to slink packages instead of the actual files. That time I had downloaded the whole lot with ncftp. I downloaded another time using wget with the option to get real files. That worked better, and dselect found all files. Still, the big problem was dselect because it complained about so many things it flipped out and refused to install any more packages (I barely got a working system). Last week I tried the same thing at work, installing over ftp, and I thik the installer also downloaded just the links, but not the actual files, so this time I wasn't even able to boot the system after running dselect. After this I installed slink instead, and it worked like a charm. Of course, I know that it's an unstable release, but is it really this hard to install, or is it me doing something wrong? If I could just get it installed properly (I run it at home, but had to do a lot of manual tuning, and adding all packages I wanted using dpkg --force* instead of dselect), I would be glad to report problems, and also fix some, but as it is now that the installation doesn't seem to work at all for me I really don't feel like reporting problems because the fault probably lies in my installation anyway. How are you installing potato? Is there some magic way to make ftp install work when there are soft links on the server? Is there a way to make dselect go on installing other packages even though it finds ten faulty packages first in the list? (This way I could add those ten manually afterwards). Thanks, Staffan Hamala
