Re: Ports woes.
> > I'm obviously getting into this very late, but I'll hazard a couple of > suggestions. Apologies if they've already been discussed/discarded. > > 1. If you haven't already, run portsdb -uU and pkgdb -F. > > 2. If it isn't among the "portupgrade stuff" you've already tried, the > -fRN options in combination may work. > > Jud Thanks to all who offered assistance and guidance. I'll give these offerings a try and if all else fails, uninstal and try again. :) TTFN ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports woes.
On Fri, 26 Sep 2003 07:32:43 -0700, "Kent Stewart" <[EMAIL PROTECTED]> said: > On Thursday 25 September 2003 04:12 pm, K Anderson wrote: > > Kent Stewart wrote: > > > On Monday 22 September 2003 08:45 pm, cuddlesomebunny wrote: > > >>Could anybody explain to me what is up with ports? > > >> > > >>I am using FreeBSD 5.x-p2 and I am using ports and am having one > > >> hell of a time installing things. > > >> > > >>Here's what is happeng. > > >> > > >>I go to install ports and if it needs to get a dependency it goes > > >> and fetches it and becomes the usual compile process. Except that > > >> the dependency might already be installed with the exact version > > >> required and so most of the time the ports error out telling me I > > >> need to make deinstall on some dependency then make reinstall on > > >> it. [snip] > > >>I tried using the portupgrade stuffs but that just seems to make > > >>things worse overall. > > >> > > >>Anybody got any hints as to why it seems ports is having these > > >> sorts of problems? > > > > > > I don't have any idea what you problem is; however, there is an > > > ongoing discussion on -current with people having port problems. > > > What I remember is that the freeze has them locked and they can't > > > patch the ports to build and install on -current until the port > > > freeze is over. You might be caught by this problem or something > > > entirely different. I'm obviously getting into this very late, but I'll hazard a couple of suggestions. Apologies if they've already been discussed/discarded. 1. If you haven't already, run portsdb -uU and pkgdb -F. 2. If it isn't among the "portupgrade stuff" you've already tried, the -fRN options in combination may work. Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports woes.
On Thursday 25 September 2003 04:12 pm, K Anderson wrote: > Kent Stewart wrote: > > On Monday 22 September 2003 08:45 pm, cuddlesomebunny wrote: > >>Could anybody explain to me what is up with ports? > >> > >>I am using FreeBSD 5.x-p2 and I am using ports and am having one > >> hell of a time installing things. > >> > >>Here's what is happeng. > >> > >>I go to install ports and if it needs to get a dependency it goes > >> and fetches it and becomes the usual compile process. Except that > >> the dependency might already be installed with the exact version > >> required and so most of the time the ports error out telling me I > >> need to make deinstall on some dependency then make reinstall on > >> it. > >> > >>And don't even get me started on installing Apache. I tried > >>installing mod_php4 but before hand installed apache+ssl and so > >> then mod_php4 doesn't even see that apache is already installed > >> and then fetches the version it wants thus blowing out the > >> apache+ssl and I have to then reinstall that package to get ssl > >> and apache. > >> > >>If I do things with /stand/sysinstall it errors out on a dependency > >>if it is already installed instead of ignoring the fact that it is > >>already there and errors out. This particular behavour started > >> around 4.8 or so. Maybe earlier but I don't seem to recall exactly > >> when this started to happen. > >> > >>I tried using the portupgrade stuffs but that just seems to make > >>things worse overall. > >> > >>Anybody got any hints as to why it seems ports is having these > >> sorts of problems? > > > > I don't have any idea what you problem is; however, there is an > > ongoing discussion on -current with people having port problems. > > What I remember is that the freeze has them locked and they can't > > patch the ports to build and install on -current until the port > > freeze is over. You might be caught by this problem or something > > entirely different. > > > > Kent > > M, could be. But would that explain why /stand/sysinstall can't > install something just because a given dependency exists already on > the system? No, idea. I don't use sysinstall after the initial install and I only do minimal initial installs of the packages. There is one exception and that is I use it to add new HDs. Once the system is installed, I use the port system to do everything. That begins with cvsuping ports-all, making both INDEXs in the cvsup script that I use, and portupgrade to maintain the ports I have installed. You can add packages from the CD-ROMS using pkg_add. You can also have it fetch packages for you but in that case, I usually build them from scratch and have never had it fetch a package for me. I think that everything you download that has been built, is basically out of date by the time you download it. For example, the ports have been tagged and are being built for 4.9's release based on the tagging but updates are going on as I write this. What you will find on the CD is consistant with the initial build of the system but any of the ports that have been fixed or updated are already out of date. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports woes.
On Thu, Sep 25, 2003 at 04:05:59PM -0700, K Anderson wrote: > Does this possibly clear up things? Yeah, that's all expected behaviour.. 1) when upgrading ports you have to upgrade ports in the correct order, i.e. if X depends on Y then you have to update Y before you update X. sysinstall doesn't do this, ports will at least notice that you have tried to install a new version of Y on top of an old version or have tried to update X when you should have first updated Y. The easiest way to update ports in the correct order is to use the portupgrade port. 2) packages depend explicitly on other packages, in particular if you have apache-X installed and it's looking for apache-Y then it will try to install it, and won't be satisfied by the apache-X installation. Kris pgp0.pgp Description: PGP signature
Re: Ports woes.
Kent Stewart wrote: On Monday 22 September 2003 08:45 pm, cuddlesomebunny wrote: Could anybody explain to me what is up with ports? I am using FreeBSD 5.x-p2 and I am using ports and am having one hell of a time installing things. Here's what is happeng. I go to install ports and if it needs to get a dependency it goes and fetches it and becomes the usual compile process. Except that the dependency might already be installed with the exact version required and so most of the time the ports error out telling me I need to make deinstall on some dependency then make reinstall on it. And don't even get me started on installing Apache. I tried installing mod_php4 but before hand installed apache+ssl and so then mod_php4 doesn't even see that apache is already installed and then fetches the version it wants thus blowing out the apache+ssl and I have to then reinstall that package to get ssl and apache. If I do things with /stand/sysinstall it errors out on a dependency if it is already installed instead of ignoring the fact that it is already there and errors out. This particular behavour started around 4.8 or so. Maybe earlier but I don't seem to recall exactly when this started to happen. I tried using the portupgrade stuffs but that just seems to make things worse overall. Anybody got any hints as to why it seems ports is having these sorts of problems? I don't have any idea what you problem is; however, there is an ongoing discussion on -current with people having port problems. What I remember is that the freeze has them locked and they can't patch the ports to build and install on -current until the port freeze is over. You might be caught by this problem or something entirely different. Kent M, could be. But would that explain why /stand/sysinstall can't install something just because a given dependency exists already on the system? CS. Bunny. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports woes.
Kris Kennaway wrote: On Mon, Sep 22, 2003 at 08:45:29PM -0700, cuddlesomebunny wrote: Could anybody explain to me what is up with ports? You'll have to provide specifics before we can diagnose what is going wrong (or not, as the case may be) on your system. It could be user error, a known problem, or something else. Kris Well, it looks like the message was cut off either by yourself or something else. But here's what happens. I go to /stand/sysinstall and pick a port, for example some port that relies on fontconfig. Since I already have fontconfig installed on my system when I select a given port it goes to fetch fontconfig then errors out (fontconfig is already installed so pkg_add freaks) and then I can not install the port. If I uninstall fontconfig then the given package succeeds in the installation (the fontconfigs appear to be the same versions being offered). Then I figure, go to /usr/ports and then select the same package and the make processes doen't notice that fontconfig is installed then goes to make it and again errors out and tells me to deinstall fontconfig. For some reason /stand/sysinstall or the make from ports is sometimes not recognizing dependencies that are already installed. Another hang, as already mentioned in the email (and seems to be missing) was I talked about the /stand/sysinstall of Apache and mod_php. I for example would install Apache+ssl and then want to install mod_php4. php4 would select the generic apache and install that over Apache+ssl and thus resolting in having to uninstall Apache and go and reinstall Apache+ssl. Also I got some error from an Apache install that said it needed to be compiled in a certain way so that modules like mod_auth_mysql would work. So after going in to /usr/ports/ww/apache+ssl I managed to get Apache up and running. Does this possibly clear up things? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports woes.
On Mon, Sep 22, 2003 at 08:45:29PM -0700, cuddlesomebunny wrote: > Could anybody explain to me what is up with ports? You'll have to provide specifics before we can diagnose what is going wrong (or not, as the case may be) on your system. It could be user error, a known problem, or something else. Kris pgp0.pgp Description: PGP signature
Re: Ports woes.
On Monday 22 September 2003 08:45 pm, cuddlesomebunny wrote: > Could anybody explain to me what is up with ports? > > I am using FreeBSD 5.x-p2 and I am using ports and am having one hell > of a time installing things. > > Here's what is happeng. > > I go to install ports and if it needs to get a dependency it goes and > fetches it and becomes the usual compile process. Except that the > dependency might already be installed with the exact version required > and so most of the time the ports error out telling me I need to make > deinstall on some dependency then make reinstall on it. > > And don't even get me started on installing Apache. I tried > installing mod_php4 but before hand installed apache+ssl and so then > mod_php4 doesn't even see that apache is already installed and then > fetches the version it wants thus blowing out the apache+ssl and I > have to then reinstall that package to get ssl and apache. > > If I do things with /stand/sysinstall it errors out on a dependency > if it is already installed instead of ignoring the fact that it is > already there and errors out. This particular behavour started around > 4.8 or so. Maybe earlier but I don't seem to recall exactly when this > started to happen. > > I tried using the portupgrade stuffs but that just seems to make > things worse overall. > > Anybody got any hints as to why it seems ports is having these sorts > of problems? I don't have any idea what you problem is; however, there is an ongoing discussion on -current with people having port problems. What I remember is that the freeze has them locked and they can't patch the ports to build and install on -current until the port freeze is over. You might be caught by this problem or something entirely different. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
