--As of January 15, 2012 10:09:06 AM -0500, freebsd-questions@freebsd.org
is alleged to have said:
I was trying out portmaster to see if it worked better than my current
tool of choice for keeping my ports up to date (portmanager) and when I
went back to portmanager I can no longer get it to g
--As of January 15, 2012 3:35:20 PM -0500, Jerry is alleged to have said:
You don't have to manually erase the tree. I believe that:
"portsnap fetch extract"
is all you need to do to replace the ports tree with a fresh copy. It
won't hurt anything since it doesn't touch the configurati
On Sun, 15 Jan 2012 13:01:23 -0500
Daniel Staal articulated:
> I have csup set to run once a week in cron. I don't think that
> corrupted anything: `portmanager -s -y` ran fine before I ran
> portmaster, and I didn't update the tree in between. But blowing
> away the tree and re-creating it
--As of January 15, 2012 12:25:47 PM -0500, Jerry is alleged to have said:
Well, you might try and deinstall and then reinstall "portmanager".
Perhaps something got corrupted, although I don't know why that might
have happened.
No joy. Worth a try though. ;)
My suspicion is that it's a perm
On Sun, 15 Jan 2012 11:48:55 -0500
Daniel Staal articulated:
Well, you might try and deinstall and then reinstall "portmanager".
Perhaps something got corrupted, although I don't know why that might
have happened.
I have "BATCH=yes" set in the "/etc/make.conf" file to avoid receiving
those annoyi
--As of January 15, 2012 10:33:32 AM -0500, Jerry is alleged to have said:
Exactly how are you invoking "portmanager"? Usually, just give it it the
"-s" flag will get you a list of port and there status as you probably
know.
Yep. I have that in a weekly cron command, so I know what's out of d
On Sun, 15 Jan 2012 10:09:06 -0500
Daniel Staal articulated:
> I was trying out portmaster to see if it worked better than my
> current tool of choice for keeping my ports up to date (portmanager)
> and when I went back to portmanager I can no longer get it to give me
> a 'Port Status Report', or
On Tue, 3 Mar 2009 08:32:10 -0900 Mel
wrote:
> On Sunday 01 March 2009 14:02:19 per...@pluto.rain.com wrote:
> > Mel wrote:
> > > On Saturday 28 February 2009 23:06:10 Fbsd1 wrote:
> > > > I am looking for software like portmanager/portmaster but works
> > > > on the package system instead
On Sunday 01 March 2009 14:02:19 per...@pluto.rain.com wrote:
> Mel wrote:
> > On Saturday 28 February 2009 23:06:10 Fbsd1 wrote:
> > > I am looking for software like portmanager/portmaster but works
> > > on the package system instead of the port system. Is there such
> > > am application availab
Mel wrote:
> On Saturday 28 February 2009 23:06:10 Fbsd1 wrote:
> > I am looking for software like portmanager/portmaster but works
> > on the package system instead of the port system. Is there such
> > am application available?
>
> Not (yet). Without /usr/ports it's impossible to find out what
Fbsd1 wrote:
Aryeh M. Friedman wrote:
Fbsd1 wrote:
I am looking for software like portmanager/portmaster but works on
the package system instead of the port system. Is there such am
application available?
___
freebsd-questions@freebsd.org mailing li
On Saturday 28 February 2009 23:06:10 Fbsd1 wrote:
> I am looking for software like portmanager/portmaster but works on the
> package system instead of the port system. Is there such am application
> available?
Not (yet). Without /usr/ports it's impossible to find out what software needs
updating
Aryeh M. Friedman wrote:
Fbsd1 wrote:
I am looking for software like portmanager/portmaster but works on the
package system instead of the port system. Is there such am
application available?
___
freebsd-questions@freebsd.org mailing list
http://list
Fbsd1 wrote:
I am looking for software like portmanager/portmaster but works on the
package system instead of the port system. Is there such am
application available?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
Chris Whitehouse wrote:
Chris Whitehouse wrote:
Eduardo Cerejo wrote:
On Fri, 23 Jan 2009 17:04:03 +
Chris Whitehouse wrote:
Eduardo Cerejo wrote:
I'm trying to upgrade any port with portmanager because portupgrade
keeps failing all the time. No matter what port I try to upgrade I
get
Chris Whitehouse wrote:
Eduardo Cerejo wrote:
On Fri, 23 Jan 2009 17:04:03 +
Chris Whitehouse wrote:
Eduardo Cerejo wrote:
I'm trying to upgrade any port with portmanager because portupgrade
keeps failing all the time. No matter what port I try to upgrade I
get this error:
sudo portm
Eduardo Cerejo wrote:
On Fri, 23 Jan 2009 17:04:03 +
Chris Whitehouse wrote:
Eduardo Cerejo wrote:
I'm trying to upgrade any port with portmanager because portupgrade keeps
failing all the time. No matter what port I try to upgrade I get this error:
sudo portmanager x11/xterm -l -u
Acc
On Fri, 23 Jan 2009 17:04:03 +
Chris Whitehouse wrote:
> Eduardo Cerejo wrote:
> > I'm trying to upgrade any port with portmanager because portupgrade keeps
> > failing all the time. No matter what port I try to upgrade I get this
> > error:
> >
> > sudo portmanager x11/xterm -l -u
>
> A
On Fri, 23 Jan 2009 06:28:19 -0500
Jerry wrote:
> On Thu, 22 Jan 2009 20:00:26 -0500
> Eduardo Cerejo wrote:
>
> >I'm trying to upgrade any port with portmanager because portupgrade
> >keeps failing all the time. No matter what port I try to upgrade I
> >get this error:
> >
> >sudo portmanager
Eduardo Cerejo wrote:
I'm trying to upgrade any port with portmanager because portupgrade keeps
failing all the time. No matter what port I try to upgrade I get this error:
sudo portmanager x11/xterm -l -u
According to the man page you don't need the -u when doing a single
port, see EXAMPLE
On Thu, 22 Jan 2009 20:00:26 -0500
Eduardo Cerejo wrote:
>I'm trying to upgrade any port with portmanager because portupgrade
>keeps failing all the time. No matter what port I try to upgrade I
>get this error:
>
>sudo portmanager x11/xterm -l -u
>Password:
>MGrStrlen error: NULL marker not foun
Titus Barik wrote:
What do I do to fix this and any ideas on what could have caused this
problem in the first place?
Replying to myself, but the problem seems to have been resolved by
re-building the ports tree. I did a 'portsnap extract' instead of the
usual 'portsnap update'.
Titus
--
Ti
rd <[EMAIL PROTECTED]> wrote:
> From: Gerard <[EMAIL PROTECTED]>
> Subject: Re: portmanager errors
> To: freebsd-questions@freebsd.org
> Date: Thursday, September 11, 2008, 7:07 AM
> On Wed, 10 Sep 2008 18:05:47 -0700 (PDT)
> gahn <[EMAIL PROTECTED]> wrote:
>
>
On Thu, 11 Sep 2008 14:27:24 -0700 (PDT)
gahn <[EMAIL PROTECTED]> wrote:
> no, i had the same errors. could portmanager bypass the failed
> package and install rest of other packages? checked with manpage and
> don't seem to the case.
>
> the only packages i didn't install are "games".
First, lo
TECTED]> wrote:
> From: Gerard <[EMAIL PROTECTED]>
> Subject: Re: portmanager errors
> To: freebsd-questions@freebsd.org
> Date: Thursday, September 11, 2008, 7:07 AM
> On Wed, 10 Sep 2008 18:05:47 -0700 (PDT)
> gahn <[EMAIL PROTECTED]> wrote:
>
>
> > ---
On Wed, 10 Sep 2008 18:05:47 -0700 (PDT)
gahn <[EMAIL PROTECTED]> wrote:
> --- On Wed, 9/10/08, Gerard <[EMAIL PROTECTED]> wrote:
>
> > From: Gerard <[EMAIL PROTECTED]>
> > Subject: Re: portmanager errors
> > To: freebsd-questions@freebsd.org
> &
yes:
lab2# portmanager -v
rParseCommandLine 0.4.1_9
--- On Wed, 9/10/08, Gerard <[EMAIL PROTECTED]> wrote:
> From: Gerard <[EMAIL PROTECTED]>
> Subject: Re: portmanager errors
> To: freebsd-questions@freebsd.org
> Date: Wednesday, September 10, 2008, 4:15 AM
> O
On Tue, Sep 9, 2008 at 11:04 PM, gahn <[EMAIL PROTECTED]> wrote:
> Hello:
>
> I run into errors when i run "portmanager -u":
>
> 00344 luit-1.0.2_2 /x11/luit
> "Makefile", line 85: Could not find
> /usr/ports/x11/xorg-clients/../../x11-servers/xorg-server/Makefile.inc
> "Makefile", line 92: Malfor
* Gerard <[EMAIL PROTECTED]> [2008-05-03 14:47:56 -0400]:
> On Sat, 3 May 2008 13:35:10 -0400
> Sahil Tandon <[EMAIL PROTECTED]> wrote:
>
> > Hi. I'm running FreeBSD 6.1. I have never had a problem with
> > portmanager until today. I was trying to update amavisd-new. When I
> > issued the upg
On Sat, 3 May 2008 13:35:10 -0400
Sahil Tandon <[EMAIL PROTECTED]> wrote:
> Hi. I'm running FreeBSD 6.1. I have never had a problem with
> portmanager until today. I was trying to update amavisd-new. When I
> issued the upgrade command, portmanager started to update perl5.8.
> Everything was g
> On November 15, 2007 at 10:54PM Noah wrote:
> > Gerard wrote:
> >> On November 15, 2007 at 06:54PM Noah wrote:
> >
> >> access1# grep apache pm-020.conf
> >> IGNORE|www/apache13*|
> >> IGNORE|www/apache13|
> >> IGNORE|www/apache13-*|
> >> IGNORE|www/apache13*-*|
> >> IGNORE|www/apache-1.3*|
> >
Hi there,
I could not find anything in the portmanager.log
how can I make sure it is ignored in the portmanager configuratino file
to make sure it is not built at all?
is there any other way to figure out what has a dependency to install it?
Cheers,
Noah
Gerard wrote:
On November 15, 2
On November 15, 2007 at 06:54PM Noah wrote:
> access1# grep apache pm-020.conf
> IGNORE|www/apache13*|
> IGNORE|www/apache13|
> IGNORE|www/apache13-*|
> IGNORE|www/apache13*-*|
> IGNORE|www/apache-1.3*|
> IGNORE|www/apache20|
> IGNORE|www/apache20*|
> IGNORE|www/apache21|
> IGNORE|www/apache21*|
On Tue, 29 May 2007 21:08:23 -0700
Matthew Navarre <[EMAIL PROTECTED]> wrote:
> From the portmanager(1) man page:
> -s or --status
> status of installed ports
>
> Says *nothing* about even the possibility of removing installed
> ports. Just status. If -s is removing installed ports
On May 23, 2007, at 10:19 AM, RW wrote:
On Thu, 24 May 2007 00:25:31 +1000
Norberto Meijome <[EMAIL PROTECTED]> wrote:
On Wed, 23 May 2007 09:53:39 +0200
Heinrich Rebehn <[EMAIL PROTECTED]> wrote:
This is weird! A program that is supposed to show the *status* of
installed ports should never
Norberto Meijome wrote:
On Wed, 23 May 2007 09:53:39 +0200
Heinrich Rebehn <[EMAIL PROTECTED]> wrote:
This is weird! A program that is supposed to show the *status* of
installed ports should never arbitrarily *remove* ports.
I agree that is not clear why it is removing ports without warning.
On Thursday 24 May 2007, Garrett Cooper wrote:
> Pieter de Goeje wrote:
> > On Wednesday 23 May 2007, [EMAIL PROTECTED] wrote:
> >> On 23/05/07, Norberto Meijome <[EMAIL PROTECTED]> wrote:
> >>> On Wed, 23 May 2007 03:15:05 +0100
> >>>
> >>> RW <[EMAIL PROTECTED]> wrote:
> pkg_version -vl"<" w
Pieter de Goeje wrote:
On Wednesday 23 May 2007, [EMAIL PROTECTED] wrote:
On 23/05/07, Norberto Meijome <[EMAIL PROTECTED]> wrote:
On Wed, 23 May 2007 03:15:05 +0100
RW <[EMAIL PROTECTED]> wrote:
pkg_version -vl"<" will give you a list of out of date ports.
Alternatively,
portversion -v | g
On Wednesday May 23, 2007 at 01:19:43 (PM) RW wrote:
> > On Wed, 23 May 2007 09:53:39 +0200
> > Heinrich Rebehn <[EMAIL PROTECTED]> wrote:
> >
> > > This is weird! A program that is supposed to show the *status* of
> > > installed ports should never arbitrarily *remove* ports.
> >
> > I agree
On Thu, 24 May 2007 00:25:31 +1000
Norberto Meijome <[EMAIL PROTECTED]> wrote:
> On Wed, 23 May 2007 09:53:39 +0200
> Heinrich Rebehn <[EMAIL PROTECTED]> wrote:
>
> > This is weird! A program that is supposed to show the *status* of
> > installed ports should never arbitrarily *remove* ports.
>
On Wed, 23 May 2007 09:53:39 +0200
Heinrich Rebehn <[EMAIL PROTECTED]> wrote:
> This is weird! A program that is supposed to show the *status* of
> installed ports should never arbitrarily *remove* ports.
I agree that is not clear why it is removing ports without warning.
> I consider this
>
On Wednesday 23 May 2007, [EMAIL PROTECTED] wrote:
> On 23/05/07, Norberto Meijome <[EMAIL PROTECTED]> wrote:
> > On Wed, 23 May 2007 03:15:05 +0100
> >
> > RW <[EMAIL PROTECTED]> wrote:
> > > pkg_version -vl"<" will give you a list of out of date ports.
> >
> > Alternatively,
> >
> > portversion -
RW wrote:
On Tue, 22 May 2007 09:39:33 +0200
Heinrich Rebehn <[EMAIL PROTECTED]> wrote:
Hi list,
i use
# portmanager -s|grep OLD | sort -t: -k2
occasionally to see which ports need upgrading. Ports tree is
cvsup'ed each night.
I then noticed that almost *all* X11 manpages had been deleted.
On 23/05/07, Norberto Meijome <[EMAIL PROTECTED]> wrote:
On Wed, 23 May 2007 03:15:05 +0100
RW <[EMAIL PROTECTED]> wrote:
> pkg_version -vl"<" will give you a list of out of date ports.
Alternatively,
portversion -v | grep \<
eg:
[EMAIL PROTECTED] [Wed May 23 17:26:33 2007]
/usr/home/betom
$
On Wed, 23 May 2007 03:15:05 +0100
RW <[EMAIL PROTECTED]> wrote:
> pkg_version -vl"<" will give you a list of out of date ports.
Alternatively,
portversion -v | grep \<
eg:
[EMAIL PROTECTED] [Wed May 23 17:26:33 2007]
/usr/home/betom
$ portversion -v | grep \<
[Updating the portsdb in /var/tm
On Tue, 22 May 2007 09:39:33 +0200
Heinrich Rebehn <[EMAIL PROTECTED]> wrote:
> Hi list,
>
> i use
>
> # portmanager -s|grep OLD | sort -t: -k2
>
> occasionally to see which ports need upgrading. Ports tree is
> cvsup'ed each night.
>
> I then noticed that almost *all* X11 manpages had been d
On Wed, 21 Mar 2007 07:45:54 -0500
Eric <[EMAIL PROTECTED]> wrote:
> n j wrote:
> > Hello,
> >
> > first off, I'm looking for a ports upgrading solution on my box, not
> > trying to start a religious debate over which one is better. I'm
> > interested in hearing what other FreeBSD admins are usin
On Wed, Mar 21, 2007 at 07:45:54AM -0500, Eric wrote:
> n j wrote:
> >first off, I'm looking for a ports upgrading solution on my box, not
> >trying to start a religious debate over which one is better. I'm
> >interested in hearing what other FreeBSD admins are using and, if
> >possible, why they
n j wrote:
Hello,
first off, I'm looking for a ports upgrading solution on my box, not
trying to start a religious debate over which one is better. I'm
interested in hearing what other FreeBSD admins are using and, if
possible, why they prefer one over the other. I have some experience
with port
On Wednesday March 21, 2007 at 08:19:38 (AM) n j wrote:
> first off, I'm looking for a ports upgrading solution on my box, not
> trying to start a religious debate over which one is better. I'm
> interested in hearing what other FreeBSD admins are using and, if
> possible, why they prefer one ove
On Sun, 04 Mar 2007 20:41:55 -0800
Noah <[EMAIL PROTECTED]> wrote:
> So at times I run portmanager on many of my servers but I want to
> make sure that the perl installed is the port and not the system
> version.
Are you aware that 5.x and 6.x releases don't have perl in the base
system, and that
Gerard Seibert wrote:
On Sun, 04 Mar 2007 20:41:55 -0800
Noah <[EMAIL PROTECTED]> wrote:
So at times I run portmanager on many of my servers but I want to
make sure that the perl installed is the port and not the system
version.
The only option I new about was to IGNORE building it.
# grep
On Sun, 04 Mar 2007 20:41:55 -0800
Noah <[EMAIL PROTECTED]> wrote:
> So at times I run portmanager on many of my servers but I want to
> make sure that the perl installed is the port and not the system
> version.
>
> The only option I new about was to IGNORE building it.
>
> # grep perl /usr/loc
On Wed, 7 Feb 2007, pete wright wrote:
hi all, i was wondering if anyone else ran into a problem recently
when portmanager was moved to /usr/ports/ports-mgt/portmanger. i have
a nightly cron which runs a "portmanager -s" to give me a status
report in the morning on outdated ports. i believe wh
On Wednesday February 07, 2007 at 12:44:30 (PM) pete wright wrote:
> hi all, i was wondering if anyone else ran into a problem recently
> when portmanager was moved to /usr/ports/ports-mgt/portmanger. i have
> a nightly cron which runs a "portmanager -s" to give me a status
> report in the morni
On Tue, 06 Feb 2007 08:37:15 -0500
Gerard Seibert <[EMAIL PROTECTED]> wrote:
> I reported this problem around 10 am. yesterday. Sometime around 2
> pm. a patch was submitted. An updated version of 'portmanager' was in
> the port's system by 4 pm. Personally, I consider that a rather quick
> fix.
On Tuesday February 06, 2007 at 08:19:27 (AM) RW wrote:
> Probably it's just that someone need to patch it to change
> "sysutils/portmanager" to "ports-mgmt/portmanager" in the source.
>
> As a workaround try linking portmanager's new port directory to where
> its old one was. As there will be a
On Mon, 5 Feb 2007 09:14:16 -0800 (PST)
White Hat <[EMAIL PROTECTED]> wrote:
> There was a change in the ports system -
> /usr/ports/UPDATING 20070205 - which now renders
> portmanager unable to run correctly. While it is
> possible to update a single port; i.e., "portmanager
> /path/to-port/", if
Gerard Seibert wrote:
On Monday February 05, 2007 at 01:33:25 (PM) Eric wrote:
i recommend switching to portmaster. its actively maintained and a lot
better than portmanager
I tried portmaster once, and found it slower and not as through as
portmanager at fully updating a system.
I
On Monday February 05, 2007 at 01:33:25 (PM) Eric wrote:
> i recommend switching to portmaster. its actively maintained and a lot
> better than portmanager
I tried portmaster once, and found it slower and not as through as
portmanager at fully updating a system.
I just discovered the same prob
White Hat wrote:
There was a change in the ports system -
/usr/ports/UPDATING 20070205 - which now renders
portmanager unable to run correctly. While it is
possible to update a single port; i.e., "portmanager
/path/to-port/", if I attempt to do a general ports
update; i.e., "portmanager -u", I re
On Friday 01 December 2006 12:18, Willem Hendriks wrote:
> When i install any port with portmanager, i get the following
> error-message:
>
>
> ** Error occured reading /usr/local/etc/pkgtools.conf:
pkgtools.conf is the configuration file for portupgrade. Unfortunately the
developer of portmanag
Gerard wrote:
> On Friday December 01, 2006 at 07:18:16 (AM) Willem Hendriks wrote:
>
>
>> When i install any port with portmanager, i get the following error-message:
>>
>>
>> ** Error occured reading /usr/local/etc/pkgtools.conf:
>> undefined method `x11base' for nil:NilClass
>> ** Err
On Sunday November 05, 2006 at 12:16:52 (PM) Tsu-Fan Cheng wrote:
> Hi people,
> as recently i have problem with firefox, i thought i will try to upgrade
> my port by my way...
>as i first run "portmanager -s > log" to see what ports are outdated, and
> if that port seem critical, I will
On Wednesday 20 September 2006 19:07, Greg Groth wrote:
> > What does "make -V FETCH_CMD" say? The default is "fetch -ApRr" where -p
> > means passive.
>
> /usr/bin/fetch -ARr
Check that you don't have this defined in the environment, or make.conf.
Updating your ports tree should bring in the new
What does "make -V FETCH_CMD" say? The default is "fetch -ApRr" where -p means
passive.
/usr/bin/fetch -ARr
Best regards,
Greg Groth
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscr
On Wednesday 20 September 2006 18:13, Greg Groth wrote:
> Here's the situation, I have 3 BSD servers sitting behind a pfsense
> firewall. When I run portmanager on any of the 3 servers, inevitably it
> runs into a distfile that can't be downloaded from an FTP site.
> Although I haven't checked the
Boris Samorodov wrote:
> > Personally, why a new source was not created so that anyone downloading
>
> Which type of source are you speaking of?
When a new, or not, user downloads an image file for FBSD, he/she is
getting an image file with this obsoleted version. They must then use
'portupgrade
On Tue, 05 Sep 2006 05:56:03 -0400 Gerard Seibert wrote:
> Boris Samorodov wrote:
> > > Can anyon tell me why this port is marked ignore? Has it been superseeded?
> >
> > You may consider reading /usr/ports/UPDATING.
> >
> > BTW, it's the right file to read from time to time and especially if
>
Boris Samorodov wrote:
> > Can anyon tell me why this port is marked ignore? Has it been superseeded?
>
> You may consider reading /usr/ports/UPDATING.
>
> BTW, it's the right file to read from time to time and especially if
> you have questions about the port system. ;-)
The info you are searc
On Mon, 4 Sep 2006 17:44:43 -0400 stan wrote:
> I'm trying to upgrade a machine, which was built only about 2 weeks agao.
Seems that either you didn't upgrade the portstree or installed a
deprecated linux_base port by hands.
> linux_base-8-8.0_16 /emulators/linux_base-8
> mar
On 04/09/06, stan <[EMAIL PROTECTED]> wrote:
I'm trying to upgrade a machine, which was built only about 2 weeks agao.
portmanager reprts the following:
portmanager 0.4.1_6
FreeBSD brown.fas.com 6.1-STABLE FreeBSD 6.1-STABL
On Sunday 20 August 2006 19:31, Noah wrote:
> Okay I am looking at these files. I am looking for something that
> automatically executes a 'use.perl port' after upgrading or reinstalling
> perl. It is most probable that I will always want the latest perl port
> active.
>
> I cant figure out how t
Gerard Seibert wrote:
On Sunday 20 August 2006 17:40, Noah wrote:
am running portmanager with the following switches "portmanager -u -f
-l -y"
which is building all the dependencies. I find that perl is set to the
system version of 5.003 . I do not want this behavior.
I want to keep upd
On Sunday 20 August 2006 17:40, Noah wrote:
> am running portmanager with the following switches "portmanager -u -f
> -l -y"
> which is building all the dependencies. I find that perl is set to the
> system version of 5.003 . I do not want this behavior.
>
> I want to keep updating Perl to the
Gerard Seibert wrote:
Noah wrote:
I am running portmanager and updating all dependencies along the way. I
am finding that perl gets updated to the system version. I want to keep
it to version 5.8. . FreeBSD4-11 is my OS.
so in order to get portmanager to stop updating perl do I add the
Noah wrote:
> I am running portmanager and updating all dependencies along the way. I
> am finding that perl gets updated to the system version. I want to keep
> it to version 5.8. . FreeBSD4-11 is my OS.
>
> so in order to get portmanager to stop updating perl do I add the
> following to /us
Micah wrote:
Chris Whitehouse wrote:
Lowell Gilbert wrote:
Chris Whitehouse <[EMAIL PROTECTED]> writes:
Searching for portmanager in the online man pages doesn't get
anything. Should it?
Sure.
http://www.freebsd.org/cgi/man.cgi?query=portmanager&manpath=FreeBSD+Ports+6.1-RELEASE
___
Chris Whitehouse wrote:
Lowell Gilbert wrote:
Chris Whitehouse <[EMAIL PROTECTED]> writes:
Searching for portmanager in the online man pages doesn't get
anything. Should it?
Sure.
http://www.freebsd.org/cgi/man.cgi?query=portmanager&manpath=FreeBSD+Ports+6.1-RELEASE
_
Lowell Gilbert wrote:
Chris Whitehouse <[EMAIL PROTECTED]> writes:
Searching for portmanager in the online man pages doesn't get
anything. Should it?
Sure.
http://www.freebsd.org/cgi/man.cgi?query=portmanager&manpath=FreeBSD+Ports+6.1-RELEASE
___
f
Chris Whitehouse <[EMAIL PROTECTED]> writes:
> Searching for portmanager in the online man pages doesn't get
> anything. Should it?
Sure.
http://www.freebsd.org/cgi/man.cgi?query=portmanager&manpath=FreeBSD+Ports+6.1-RELEASE
___
freebsd-questions@freeb
On Friday 04 August 2006 20:33, Chris Whitehouse wrote:
> Hi,
>
> Searching for portmanager in the online man pages doesn't get anything.
> Should it?
portmanager isn't part of the freebsd base system
___
freebsd-questions@freebsd.org mailing list
http:/
jan gestre wrote:
> sorry for this newbie question, i've been upgrading my box using portupgrade
> but recently i'm experiencing some wierd logs that can't be explained nor
> solved but luckily my box does not appear to be broken, i have a question
> though regarding portmanager, someone on this l
On Sun, 2006-06-04 at 17:42 -0400, Gerard wrote:
[...]
> >
> I am not sure, but here is where yo could start.
>
> Clear out your /tmp and /var/tmp directory. Next, remove all of the
> special flags in the /etc/make.conf file. Actually, I am not sure if
> that will make a difference, but you have
On Sun, 2006-06-04 at 08:06 -0400, Gerard Seibert wrote:
> On Sunday 04 June 2006 04:34, Yousef Raffah wrote:
> > On Sat, 2006-06-03 at 12:55 -0400, Gerard Seibert wrote:
> > [...]
> >
> > > Well, it seems that you have a problem here:
> > >
> > > skipping openssl-0.9.8b_1 /security/openssl marked
On Sunday 04 June 2006 04:34, Yousef Raffah wrote:
> On Sat, 2006-06-03 at 12:55 -0400, Gerard Seibert wrote:
> [...]
>
> > Well, it seems that you have a problem here:
> >
> > skipping openssl-0.9.8b_1 /security/openssl marked IGNORE reason:
> > conflicts with another installed port
>
> I resolved
On Sat, 2006-06-03 at 12:55 -0400, Gerard Seibert wrote:
[...]
>
> Well, it seems that you have a problem here:
>
> skipping openssl-0.9.8b_1 /security/openssl marked IGNORE reason:
> conflicts with another installed port
>
I resolved the conflict and now I have one openssl installation.
> You
Yousef Raffah wrote:
> On Sat, 2006-06-03 at 07:44 -0400, Gerard Seibert wrote:
> > Yousef Raffah wrote:
> >
> > > excuse the n00b in me but I'm trying to install a port using portmanager
> > > as installing it the traditional (make install clean) way failed and the
> > > one of the cool guys on
On Sat, 2006-06-03 at 07:44 -0400, Gerard Seibert wrote:
> Yousef Raffah wrote:
>
> > excuse the n00b in me but I'm trying to install a port using portmanager
> > as installing it the traditional (make install clean) way failed and the
> > one of the cool guys on the list here suggested to use por
Yousef Raffah wrote:
> excuse the n00b in me but I'm trying to install a port using portmanager
> as installing it the traditional (make install clean) way failed and the
> one of the cool guys on the list here suggested to use portmanager to
> resolve the problem.
>
> I have synced my ports as o
--- Gerard Seibert <[EMAIL PROTECTED]> wrote:
> Jim Angstadt wrote:
>
> > Hi All,
> >
> > Having run "portmanager -u" several times now, I
> am
> > very pleased to say that my times have decreased
> from
> > an initial 38 hours to about 2 hours, per run.
> >
> > Along the way, I have cleaned
Jim Angstadt wrote:
> Hi All,
>
> Having run "portmanager -u" several times now, I am
> very pleased to say that my times have decreased from
> an initial 38 hours to about 2 hours, per run.
>
> Along the way, I have cleaned up "conflicts" and did
> "pkg_delete" on several applications that were
Jim Angstadt wrote:
--- Aaron Holmes <[EMAIL PROTECTED]> wrote:
Jim Angstadt wrote:
Hi All,
Having run "portmanager -u" several times now, I
am
very pleased to say that my times have decreased
from
an initial 38 hours to about 2 hours, per run.
Along the w
--- Aaron Holmes <[EMAIL PROTECTED]> wrote:
> Jim Angstadt wrote:
> > Hi All,
> >
> > Having run "portmanager -u" several times now, I
> am
> > very pleased to say that my times have decreased
> from
> > an initial 38 hours to about 2 hours, per run.
> >
> > Along the way, I have cleaned up "con
Jim Angstadt wrote:
Hi All,
Having run "portmanager -u" several times now, I am
very pleased to say that my times have decreased from
an initial 38 hours to about 2 hours, per run.
Along the way, I have cleaned up "conflicts" and did
"pkg_delete" on several applications that were
"included in b
Hi Gerard,
On Fri, 05 May 2006 20:48:40 -0400, Gerard Seibert wrote:
>
>Have you tried contacting "Michael C. Shultz" <[EMAIL PROTECTED]> in
>regards to this matter?
No, I haven't - at present, the port Makefile lists:
MAINTAINER= [EMAIL PROTECTED]
I thought it best to start there.
cheers,
Joel Hatton wrote:
> Hi,
>
> I've lately been using portmanager on my build host, instead of
> portupgrade, to rebuild ports and produce packages and I'm impressed. But
> now I want more...
>
> It seems to me that one of the greatest benefits of portmanager is that
> it is a compiled executable,
RW wrote:
On Thursday 20 April 2006 22:25, Chris Whitehouse wrote:
Hi
I've just cvsup'ed ports and run portmanager -s. Part way through it
asks me if it can remove linux-flashplugin-6.0r79_3 because of the
licencing issue. When I say no portmanager quits. Actual output below.
1) Would it be po
On Thursday 20 April 2006 22:25, Chris Whitehouse wrote:
> Hi
>
> I've just cvsup'ed ports and run portmanager -s. Part way through it
> asks me if it can remove linux-flashplugin-6.0r79_3 because of the
> licencing issue. When I say no portmanager quits. Actual output below.
>
> 1) Would it be pos
On Saturday 25 March 2006 02:21, RW wrote:
> On Friday 24 March 2006 17:13, Noah wrote:
> > Hi there,
> >
> > I am trying to figure out the proper options and configuration syntax for
> > the portmanager configuration file - pm-020.conf . I cant figure out
> > what the proper stunnel switches to
1 - 100 of 194 matches
Mail list logo