Just wondering if the change suggested in the Subject line
of this message can result in the following scenario of
something like it:
installed gettext10
installed gettext8
if gettext bumps from so.8 to so.10, both installed
and any port which relies upon them uses the
lesser until it is bumped "n
On Fri, Jun 27, 2008 at 05:03:38PM -0400, Frank Tavenner wrote:
> Hello Jarrod,
>
>
> When I read the long description from freebsd.org it said Nagios 3.0.2_1
> was here "Port description for net-mgmt/nagios-devel" but when I went
> there on my freebsd 7.0 and installed it, I ended up with Nagio
Hello Jarrod,
When I read the long description from freebsd.org it said Nagios 3.0.2_1
was here "Port description for net-mgmt/nagios-devel" but when I went
there on my freebsd 7.0 and installed it, I ended up with Nagios 3.0b5
which is not what I really wanted, because things are different.
I
So I pulled a fresh copy of the portsnap for cfengine port -- we are
*STILL* on 2.2.3? How many years does it take to get a port updated?
On May 9, 2008, at 12:19 AM, Boris Samorodov wrote:
If there's something wrong
with them, someone needs to specify what is wrong.
Seems that you shouldn
On Fri, 2008-06-27 at 17:21 +0100, RW wrote:
> On Fri, 27 Jun 2008 10:55:57 -0400
> Robert Noland <[EMAIL PROTECTED]> wrote:
>
> > On Fri, 2008-06-27 at 10:46 -0400, Josh Hanson wrote:
> > > Ok, so I tried running "portmanager -u -p -l -y".
> > >
> > > It built a lot of ports, then got stuck agai
On Fri, 27 Jun 2008 10:55:57 -0400
Robert Noland <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-06-27 at 10:46 -0400, Josh Hanson wrote:
> > Ok, so I tried running "portmanager -u -p -l -y".
> >
> > It built a lot of ports, then got stuck again on xorg-server over
> > and over. The log file looks the
Mikhail Teterin wrote:
If foo chokes on that, you should be contacting foo's maintainer, but that's
not me (nor do I maintain imagemagic or ghostscript, BTW). In case of
I ask you don't commit things that break something.
Thank you.
--
Dixi.
Sem.
__
On Fri, 2008-06-27 at 10:46 -0400, Josh Hanson wrote:
> Ok, so I tried running "portmanager -u -p -l -y".
>
> It built a lot of ports, then got stuck again on xorg-server over and
> over. The log file looks the same as my first post.
Is the options screen being presented repeatedly? If so, the o
Ok, so I tried running "portmanager -u -p -l -y".
It built a lot of ports, then got stuck again on xorg-server over and
over. The log file looks the same as my first post.
-- Josh
-Original Message-
From: Robert Noland [mailto:[EMAIL PROTECTED]
Sent: Friday, June 27, 2008 10:34 AM
To:
On Thu, 2008-06-26 at 15:54 -0400, Josh Hanson wrote:
> Hi,
>
> I'm setting up a fresh installation of freebsd, and portmanager keeps
> getting stuck in a loop while trying to upgrade ports.
>
> I ran "portmanager -u -l" with several dozen ports to upgrade. It seemed
> to successfully upgrade qui
(please skip down to the line of if you just want the Call for
Testers)
Hi Scott, Giovanni and all,
In message <[EMAIL PROTECTED]>, Scott Lambert
<[EMAIL PROTECTED]> writes
On Thu, Jun 26, 2008 at 11:25:48PM +0200, Giovanni Venturi wrote:
Hello,
what is the difference between freeradius
On Thu, Jun 26, 2008 at 7:36 PM, Pietro Cerutti <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Schiz0 wrote:
> | Hey,
> |
> | I'm attempting to create a new port for btsh:
> | http://btsh.sourceforge.net/
> | The website isn't finished yet, but it's a command-lin
On Wed, Jun 25, 2008 at 04:51:02PM +0200, Alexey Shuvaev wrote:
> Hello!
>
> On Wed, Jun 25, 2008 at 07:10:14AM -0700, Mark Atkinson wrote:
> > Hi,
> >
> > Is anyone else running freebsd-current with kde3 (and has rebuilt both
> > recently)? I can only suspect this is related to recent changes
On п'ятниця 27 червень 2008, Sergey Matveychuk wrote:
= Mikhail Teterin wrote:
= >
= >> But I'd like remind .warning directive pollutes stderr
= > Warnings are NOT pollution...
= >> and discouraged portupgrade which was designed to catch messages from
= >> stderr and rises errors.
= > I'd say, th
Use a ports-supported version of FreeBSD. 6.3 and above.
-aDe
On Jun 25, 2008, at 20:25 , email wrote:
How to fix this?
'`; fi; rm -rf $backupdir; exit $rc
./automake-1.9.texi:9821: Unknown command `headitem'.
makeinfo: Removing output file `./automake-1.9.info' due to errors;
use --force
Mikhail Teterin wrote:
But I'd like remind .warning directive pollutes stderr
Warnings are NOT pollution...
and discouraged portupgrade which was designed to catch messages from
stderr and rises errors.
I'd say, the portupgrade needs fixing, if it does, indeed, choke on
Well, only imagemag
16 matches
Mail list logo
