I think it's a bug that linux_base thinks it conflicts with itself.
--petef
The problem occurs if you do
make install; make install FORCE_PKG_REGISTER=yes
which is somewhat supported, although [seldom] (never?) used.
--eik
Also record conflicts with cle_base.
Installation of linux_base-7.1_2 fails when linprocfs is
mounted. Unmounting linprocfs before installing works
around the issue.
At Lars' suggestion, this script also mounts the linprocfs after
installation. I assume that if the user has a linprocfs entry in
/etc/fstab, the user wants it to be mounted. It also seemed like
a good idea to un-mount it before de-installation.
PR: 46172
remotely exploitable RPC bug (Red Hat advisory RHSA-2003-089 and
CERT advisory CA-2003-10).
According to <URL:http://www.redhat.com/apps/support/errata/>, "all
errata support for Alpha products, Sparc products, and Powertools
products have reached end of life."
I didn't do any run-time testing of this, but it packages and
deinstalls cleanly.
by Netscape 6 and 7. With all of those (so far), Java only works
with this version of linux_base. The linux-gtk port is no longer
compatible with linux_base-6. Increment PORTREVISION.
warning about unknown owners. Add a reminder in the Makefile, because this
fix should be removed when a new release of the RPMS fixes the problem.
Specifically, the only affected file in the LINUXBASE hierarchy is
usr/man/man8/setserial.8 (-> root:wheel)
Approved by: marcel
settings and fails to install if the language is not C.
Override any locale settings when running rpm.
PR: 16621
Submitted by: Mikhail Teterin <mi@video-collage.com>
by the port had actual definitions with bogus values. Comment
out the definitions.
PR: 21554
Originator: Youki Kadobayashi <youki-k@is.aist-nara.ac.jp>
by the globally defined LINUXBASE. Setting DESTDIR on the
command line now does what one expects.
Also, don't download and install glib-1.2.5 when we're also
downloading and installing glib-1.2.6. It's now possible to
reinstall this port over itself.
independent packages that, despite the identical names, have
different contents.
This "feature" is currently implemented in a way that works
around a limitation in bsd.port.mk and can be considered a
hack.
versions are not the same as the i386 version, even though they
have the same name.
This fix does not have effect until the architecture specific md5
files are used.
