Date: Sun, 9 Nov 2003 03:41:34 +0100 From: Erik Trulsson <ertr1013@student.uu.se> To: "F. Even" <freebsdlists@elitists.org> Cc: freebsd-questions@freebsd.org Subject: Re: revived ports collection, errors galore Message-ID: <20031109024134.GA69988@falcon.midgard.homeip.net> In-Reply-To: <BBD2F71A.1FCF9%freebsdlists@elitists.org> References: <20031108200114.DD94C16A521@hub.freebsd.org> <BBD2F71A.1FCF9%freebsdlists@elitists.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 08, 2003 at 07:40:10PM -0600, F. Even wrote: > On 11/8/03 2:01 PM, "freebsd-questions-request@freebsd.org" > <freebsd-questions-request@freebsd.org> wrote: > > > Date: Sat, 8 Nov 2003 00:00:09 -0800 > > From: Kris Kennaway <kris@obsecurity.org> > > Subject: Re: revived ports collection, errors galore > > To: "F. Even" <freebsdlists@elitists.org> > > Cc: freebsd-questions@freebsd.org > > Message-ID: <20031108080008.GA53815@xor.obsecurity.org> > > Content-Type: text/plain; charset="us-ascii" > > > > On Sat, Nov 08, 2003 at 12:36:04AM -0600, F. Even wrote: > >> I am running a FreeBSD 4.0 box. > > > > The ports collection does not support 4.0. See http://www.freebsd.org/ports/ > > > > Kris > > I don't see anything at the ports site to indicate that the ports collection > shouldn't work on 4.0R. Just vague pointers about how it "may not." You mean you missed the part that says: The Ports Collection supports the latest release on the FreeBSD-CURRENT and FreeBSD-STABLE branches. Older releases are not supported and may or may not work correctly with an up-to-date ports collection. Over time, changes to the ports collection may rely on features that are not present in older releases. That means the ports collection isn't supported for FreeBSD 4.0, and if it happens to work you just got lucky, and if it doesn't work you shouldn't expect anybody to fix it. > > And that still doesn't help me figure out why the packages are not > installing? I have not had problems installing packages up until I've tried > to update the ports collection. > > {error} > [root@cerebus:/apps/pkgs] pkg_add openssh-portable-3.7.1p2.tgz > pkg_add: bad command '@conflicts openssh-3.*' > > [root@cerebus:/apps/pkgs] pkg_add openssh-3.6.1_5.tgz > pkg_add: bad command '@conflicts openssh-portable-*' > {/error} Because the packages in question rely on a feature (the "@conflicts" directive in this case) that the pkg_add(1) command shipped with FreeBSD 4.0 does not know how to handle. To handle packages that have been built from an up-to-date ports collection, you usually need up-to-date versions of the pkg_* tools. (It seems as if you can get such via the sysutils/pkg_install port, but I haven't tested that myself, so I don't know how well it works.) -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031109024134.GA69988>