01.10.2012 21:33, Jerry wrote:
I just finished installing linux-f10-flashplugin-11.2r202.238. For
some inexplicable reason, it is no longer working. I followed the
directions in UPDATING but without success. I even cleared out the
entries in the ~/.mozilla/plugins directory and reran the command
I have on one system:
# ls /var/db/pkg
apr-1.4.6.1.4.1_1 help2man-1.40.10pkgconf-0.8.4
auditfile help2man-1.40.11pkgconf-0.8.5
autoconf-2.69 help2man-1.40.12pkgconf-0.8.6
automake-1.12.2
From mexas Mon Oct 1 10:51:13 2012
To: freebsd-ports@freebsd.org, w...@freebsd.org
Subject: security/sudo *** [pre-install] Signal 11
Reply-To: me...@bristol.ac.uk
# make install FORCE_PKG_REGISTER=1
=== Installing for sudo-1.8.6.p3_1
===
On 02/10/2012 09:08, Anton Shterenlikht wrote:
I have on one system:
# ls /var/db/pkg
apr-1.4.6.1.4.1_1 help2man-1.40.10pkgconf-0.8.4
auditfile help2man-1.40.11pkgconf-0.8.5
autoconf-2.69 help2man-1.40.12
from Bas Smeelen b.smee...@ose.nl:
Below it looks like the creation of the backup package fails, which get's
deleted by default after the new port is installed.
I Just update ports on a CURRENT server with csup from cvsup4.nl.FreeBSD.org
and the help2man version is still 1.40.12
I will go
[ Matthew Seaman wrote on Tue 2.Oct'12 at 10:32:56 +0100 ]
On 02/10/2012 09:08, Anton Shterenlikht wrote:
I have on one system:
# ls /var/db/pkg
apr-1.4.6.1.4.1_1 help2man-1.40.10
pkgconf-0.8.4
auditfile help2man-1.40.11
On 02/10/2012 11:33, Jamie Paul Griffin wrote:
Hi Matthew and Anton, so in the meantime what is the best way to
clear this old stuff out? I do like to clear out code and files that
are redundant, where possible. What would you suggest?
At the moment, the only way to clear up is to manually
I updated from sudo-1.8.5.p3 to sudo-1.8.6.p3_1
on ia64 r235474. The new version segfaults all
the time. I'm in a hurry to get a working sudo
back, because it's required for the portscluster
builds. Please advise what svn revision I need
to go back to get to sudo-1.8.5p3.
Thanks
Anton
On Tue, 2 Oct 2012 12:30:26 +0100 (BST)
Anton Shterenlikht me...@bristol.ac.uk wrote:
I updated from sudo-1.8.5.p3 to sudo-1.8.6.p3_1
on ia64 r235474. The new version segfaults all
the time. I'm in a hurry to get a working sudo
back, because it's required for the portscluster
builds.
[ Matthew Seaman wrote on Tue 2.Oct'12 at 12:13:05 +0100 ]
At the moment, the only way to clear up is to manually remove the
outdated subdirectories from /var/db/ports. You can work out what is
out of date by comparing the list of sub-dirs to the list of installed
ports obtained by
From mexas Tue Oct 2 10:21:10 2012
From mexas Mon Oct 1 10:51:13 2012
# make install FORCE_PKG_REGISTER=1
=== Installing for sudo-1.8.6.p3_1
=== Generating temporary packing list
if test -d ./.hg cd .;
Are we supposed to be using cvs or svn to check out ports now? If cvs, I'm
getting prompted for a password which fails.
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It
On Tue, Oct 02, 2012 at 11:23:23AM -0500, Paul Schmehl wrote:
Are we supposed to be using cvs or svn to check out ports now? If cvs, I'm
getting prompted for a password which fails.
That depends on the nature of the repository you are using.
What I do is maintain local private mirrors of the
On 10/02/12 11:23, Paul Schmehl wrote:
Are we supposed to be using cvs or svn to check out ports now? If cvs,
I'm getting prompted for a password which fails.
I think you are supposed to use *csup* or svn. But use svn - it is
easy, and csup is going to be phased out very soon.
Paul Schmehl pschmehl_li...@tx.rr.com writes:
Are we supposed to be using cvs or svn to check out ports now? If
cvs, I'm getting prompted for a password which fails.
If you rarely need more than the latest version of the ports tree, then
portsnap(8) is worth strong consideration. If you have
--On October 2, 2012 1:00:52 PM -0400 Lowell Gilbert
freebsd-ports-lo...@be-well.ilk.org wrote:
Paul Schmehl pschmehl_li...@tx.rr.com writes:
Are we supposed to be using cvs or svn to check out ports now? If
cvs, I'm getting prompted for a password which fails.
If you rarely need more
On 2 October 2012 14:37, Paul Schmehl pschmehl_li...@tx.rr.com wrote:
I obviously wasn't very clear. I'm a port maintainer. I need to update one
of my ports. I used to do this by checking out the port into a
purpose-created directory in which I would use cvs to make changes and test.
After
--On October 2, 2012 2:44:46 PM -0400 Eitan Adler li...@eitanadler.com
wrote:
On 2 October 2012 14:37, Paul Schmehl pschmehl_li...@tx.rr.com wrote:
I obviously wasn't very clear. I'm a port maintainer. I need to update
one of my ports. I used to do this by checking out the port into a
I found a situation where gcc v4.2 compiles a i386 working binary and
v4.6 doesn't. (Currently 4.7 and 4.8 fail to build this code) I have
verified that this happens with 8.2/8.3/9.0 i386 systems. x86_64
versions build without issue as does clang i386/x86_64.
It appears that the x86_64 target of
From: Matthew Seaman m.sea...@infracaninophile.co.uk
On 02/10/2012 12:38, Jamie Paul Griffin wrote:
[ Matthew Seaman wrote on Tue 2.Oct'12 at 12:13:05 +0100 ]
=20
=20
At the moment, the only way to clear up is to manually remove the
--On October 2, 2012 11:28:12 PM +0200 Michael Gmelin free...@grem.de
wrote:
On Tue, 02 Oct 2012 14:14:26 -0500
Paul Schmehl pschmehl_li...@tx.rr.com wrote:
--On October 2, 2012 2:44:46 PM -0400 Eitan Adler
li...@eitanadler.com wrote:
On 2 October 2012 14:37, Paul Schmehl
On 2 October 2012 22:54, Paul Schmehl pschmehl_li...@tx.rr.com wrote:
--On October 2, 2012 11:28:12 PM +0200 Michael Gmelin free...@grem.de
wrote:
On Tue, 02 Oct 2012 14:14:26 -0500
Paul Schmehl pschmehl_li...@tx.rr.com wrote:
--On October 2, 2012 2:44:46 PM -0400 Eitan Adler
On 10/2/2012 10:54 PM, Paul Schmehl wrote:
How do I handle this?
firnsy-barnyard2-v2-1.10-0-g2f5d496.tar.gz
Is the string at the end (g2f5d496) auto-generated? If so, that's
another problem.
I guess something like this? Sheesh. What a PITA.
PORTNAME= barnyard2-v2
PORTVERSION=
23 matches
Mail list logo