Hi,
I'm following the recipe at the end of man portmaster for deleting and
reinstalling all my ports, which I have done many times in the
past. This time, I am getting errors on the portmaster -Faf step
involving deleted ports, and I'm not sure how to deal with this
easily.
What
On Mon, 14 Oct 2013, Scott Ballantyne wrote:
I'm following the recipe at the end of man portmaster for deleting and
reinstalling all my ports, which I have done many times in the
past. This time, I am getting errors on the portmaster -Faf step
involving deleted ports, and I'm not sure how
On Mon, 14 oct 2013, Warren Block wbl...@wonkity.com wrote:
On Mon, 14 Oct 2013, Scott Ballantyne wrote:
What errors, exactly?
Well, for example:
portmaster -Faf
it starts to fetch a bunch of files
it finds a port which has been deleted, such as
linux-base-fc4
and it says
On Mon, Oct 14, 2013 at 6:35 PM, Scott Ballantyne s...@ssr.com wrote:
I understand why portmaster quits that port.
Because it has no choice.
It does seem like a bit
of over-kill to quit updating ALL ports because one is long
gone. Seems like it could do the others.
So it should
On Mon, 14 Oct 2013, Scott Ballantyne wrote:
On Mon, 14 oct 2013, Warren Block wbl...@wonkity.com wrote:
On Mon, 14 Oct 2013, Scott Ballantyne wrote:
What errors, exactly?
Well, for example:
portmaster -Faf
it starts to fetch a bunch of files
it finds a port which has been deleted
tell it. Try it
out and see what fun you can create.
Not a single program on my system depended on that program being
rebuilt. Portmaster should certainly refuse to rebuild anything that
did, of course.
___
freebsd-questions@freebsd.org mailing list
the portmaster 'nuke all ports' method I was trying to
day. Since then, several dozen ports of been 'deleted' or 'renamed',
not just the linux_base-fc4. Seems in the case of ports which have
been renamed or replaced, this could in fact be simply automated in
most cases.
I think it does handle
? Then you build unsupported and faultly packages and complain
to the list when something doesn't work. Just follow /usr/ports/UPDATING
as advised instead of your shortcuts.
Portmaster should certainly refuse to rebuild anything that
did, of course.
Exactly what it did.
--
Adam Vande More
Hi,
I'm following the recipe at the end of man portmaster for deleting and
reinstalling all my ports, which I have done many times in the
past. This time, I am getting errors on the portmaster -Faf step
involving deleted ports, and I'm not sure how to deal with this
easily. If the ports aren't
On Sun, 13 Oct 2013, Scott Ballantyne wrote:
Hi,
I'm following the recipe at the end of man portmaster for deleting and
reinstalling all my ports, which I have done many times in the
past. This time, I am getting errors on the portmaster -Faf step
involving deleted ports, and I'm not sure how
On 10/03/2013 20:28, Antonio Olivares wrote:
Have tried that, but it rebuilds pixman, but then X bombs out blurting
out messages that libpixman.so is missing :(
I have tried to remove print/texlive-scheme-full; removed it, but then
run portmaster -R pixman, and portmaster -r pixman
On Thu, 3 Oct 2013, Antonio Olivares wrote:
Have tried that, but it rebuilds pixman, but then X bombs out blurting
out messages that libpixman.so is missing :(
I have tried to remove print/texlive-scheme-full; removed it, but then
run portmaster -R pixman, and portmaster -r pixman
; removed it, but then
run portmaster -R pixman, and portmaster -r pixman and the running of
it stops with message that !#/bin/sh .. argument too long and comes up
with texlive-?-?-_1 or similar. Have not been successful in
fixing this issue. I have 2 machines working and 2 not working
'texlive-*' but it does not work :(
I get
Could not execute shell
/usr/ports/Mk/bsd.port.mk, line 1192: warning /usr/bin/awk
'/^#define[[:blank:]]FreeBSD_version/ {print $3}
/usr/include/sys/param.h returned non-zero status
/usr/local/sbin/portmaster: rm: Argument list too long
and it justs
dependent ports. If you have external software that
depends on pixman, this software needs to be recompiled.
To recompile all software dependent on pixman, run:
# portmaster -r pixman
or
# portupgrade -rf pixman
The messages are that a pkg texlive-ub* and that #!/bin/sh list
[[:blank:]]FreeBSD_version/ {print $3}
/usr/include/sys/param.h returned non-zero status
/usr/local/sbin/portmaster: rm: Argument list too long
and it justs sits there. Out of 3 machines only 1 is working because
I overlooked the pixman update entry in /usr/src/UPDATING :(
Please advice me
1192: warning /usr/bin/awk
'/^#define[[:blank:]]FreeBSD_version/ {print $3}
/usr/include/sys/param.h returned non-zero status
/usr/local/sbin/portmaster: rm: Argument list too long
and it justs sits there. Out of 3 machines only 1 is working because
I overlooked the pixman update entry
that
depends on pixman, this software needs to be recompiled.
To recompile all software dependent on pixman, run:
# portmaster -r pixman
or
# portupgrade -rf pixman
The messages are that a pkg texlive-ub* and that #!/bin/sh list
too long. I try to run
# portmaster -d -r pixman -x 'texlive
On 05/12/2013 12:37 AM, Leslie Jensen wrote:
I do some work on remote machines and sometimes I have a need to execute
additional commands after for example a portmaster -a command.
Normally I use the to separate commands but this does not work when
portmaster displays pkg-messages.
I
I do some work on remote machines and sometimes I have a need to execute
additional commands after for example a portmaster -a command.
Normally I use the to separate commands but this does not work when
portmaster displays pkg-messages.
I cannot see in the portmaster manpage
I'm specifically thinking of the directories that has to be emptied or
deleted.
Thanks
/Leslie
Using portmaster to do a complete reinstallation of all your ports:
1. portmaster --list-origins ~/installed-port
When reading the portmaster man page I just came to wonder if this isn't
a typo?
[--force-config|-G] [-aftv] -F
fetch distfiles only
Shouldn't the -F be to the far left?
Thanks
/Leslie
___
freebsd-questions@freebsd.org mailing list
On 5/9/2013 3:25 AM, Leslie Jensen wrote:
When reading the portmaster man page I just came to wonder if this isn't
a typo?
[--force-config|-G] [-aftv] -F
fetch distfiles only
Shouldn't the -F be to the far left?
Thanks
/Leslie
It seems consistent with how the other
On Thu, 09 May 2013 06:06:42 -0500
Bryan Drewery articulated:
(I'm not the original author on portmaster). Personally the manpage
really confuses me. There's been bigger issues to tackle first though
so I have not touched the manpage much.
You do realize that the man in manpage is an acronym
- Original Message -
From: Jerry je...@seibercom.net
To: FreeBSD freebsd-questions@freebsd.org
Cc:
Sent: Thursday, 9 May 2013 5:15 PM
Subject: Re: Typo in portmaster man page?
On Thu, 09 May 2013 06:06:42 -0500
Bryan Drewery articulated:
(I'm not the original author
Does portmaster have a --noexecute flag like portupgrade?
Specifically, I want to run the following command and see exactly what
would be updated / modified sans actually doing it.
portmaster -o new_app old_app
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get
On Wed, 17 Apr 2013 16:34:24 -0400, Jerry wrote:
Does portmaster have a --noexecute flag like portupgrade?
Specifically, I want to run the following command and see exactly what
would be updated / modified sans actually doing it.
portmaster -o new_app old_app
Is the -n option what you
How do I tell portmaster -ad to ignore certain ports because they are
broken such as editors/libreoffice is currently marked as (I am sure this
will change soon)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
Just use -x switch
portmaster -ad -x libreoffice
2013/3/25 Aryeh Friedman aryeh.fried...@gmail.com:
How do I tell portmaster -ad to ignore certain ports because they are
broken such as editors/libreoffice is currently marked as (I am sure this
will change soon
On 03/25/2013 10:40, Aryeh Friedman wrote:
How do I tell portmaster -ad to ignore certain ports because they are
broken such as editors/libreoffice is currently marked as (I am sure this
will change soon)
___
freebsd-questions@freebsd.org mailing list
2013-03-25 10:40, Aryeh Friedman skrev:
How do I tell portmaster -ad to ignore certain ports because they are
broken such as editors/libreoffice is currently marked as (I am sure this
will change soon)
___
freebsd-questions@freebsd.org mailing list
How do I tell portmaster -ad to ignore certain ports because they are
broken such as editors/libreoffice is currently marked as (I am sure
this
will change soon)
-x avoid building or updating ports that match this pattern. Can be
specified more than once
Aryeh Friedman aryeh.fried...@gmail.com writes:
How do I tell portmaster -ad to ignore certain ports because they are
broken such as editors/libreoffice is currently marked as (I am sure this
will change soon)
Your direct question was already answered, but note that libreoffice is
not broken
On Mon, 25 Mar 2013 09:53:00 -0400, Lowell Gilbert wrote:
Aryeh Friedman aryeh.fried...@gmail.com writes:
How do I tell portmaster -ad to ignore certain ports because they are
broken such as editors/libreoffice is currently marked as (I am sure
this will change soon)
Your direct question
I started off portmaster on a massive update on Thursday evening. Everything
started off OK and I kept responding to all the make config screens until they
were all finished and the compilation was well underway then went to bed and
left it to get on with it.
The next morning I discovered
On 9 February 2013 05:45, Mike Clarke jmc-freeb...@milibyte.co.uk wrote:
I started off portmaster on a massive update on Thursday evening. Everything
started off OK and I kept responding to all the make config screens until they
were all finished and the compilation was well underway then went
with the
py-bittornado-core port. I do not need it. So I have deleted it:
# pkg_info | grep bittornado
#
Clearly, it is not installed. However, when I write in this command:
# portmaster -a
Then I get this error:
=== The net-p2p/py-bittornado-core port has been deleted: Has
expired: Depends
When running portmaster -d -w -r pcre because of the upgrade from
pcre-8.31 to pcre-8.32 I encountered the following inconveniences:
Upgrade to hal-0.5.14_20 failed with the message it needs intltool
0.40 which was installed at the time. First upgrading to intltool-0.41.1
solved this.
When
it. So I have deleted it:
# pkg_info | grep bittornado
#
Clearly, it is not installed. However, when I write in this command:
# portmaster -a
Then I get this error:
=== The net-p2p/py-bittornado-core port has been deleted: Has
expired: Depends on the deprecated wx 2.4
=== Aborting update
Hi,
I hit a problem today during a system update.
There were two libxul ports:
/usr/ports/www/libxul
/usr/ports/www/libxul19
of which the last one was installed:
/var/db/pkg/libxul-1.9.2.28_1/
There was a port to update which died on error:
# portmaster icedtea-web
...
=== The dependency for www
ports:
/usr/ports/www/libxul
/usr/ports/www/libxul19
of which the last one was installed:
/var/db/pkg/libxul-1.9.2.28_1/
There was a port to update which died on error:
# portmaster icedtea-web
...
=== The dependency for www/libxul
seems to be handled by libxul-1.9.2.28_1
uki ukaszg at gmail.com writes:
But theese are different packages (different names). since ports dont have
any equivalent of debian provides flag it is impossible to figure it out
in a safe way.
I have never built a port/package, so I could be wrong here.
This paragraph seems to contain
On Fri, 12 Oct 2012 04:35:43 + (UTC), jb wrote:
Hi,
what is the diff between
--index
and
--index-only
According to man portmaster there are some options that
control the behaviour regarding the use of INDEX:
--no-index-fetch
skip fetching the INDEX file
--index
to use /usr/ports. For updating ports when no /usr/ports
directory is present the -PP|--packages-only option is required. See
the ENVIRONMENT section below for additional requirements.
This means --index-only is to be used when using portmaster for
binary installs without
jb jb.1234abcd at gmail.com writes:
...
--index-only
do not try to use /usr/ports. For updating ports when no
/usr/ports
directory is present the -PP|--packages-only option is required.
See the ENVIRONMENT section below for additional
section below for additional requirements.
...
And -PP|--packages-only option implies index only entry behavior, so there
is redundancy here as well.
Does anybody know where this --index-only option really matter ?
jb
Well /usr/local/sbin/portmaster is a _big_ shell script
You could read
--index-only is to be used when using portmaster for
binary installs without an installed ports collection.
Well, yes, BUT they seem to be redundant (that's why I asked).
# portmaster -L --index-only | egrep '(ew|ort) version|total install'
=== New version available: smartmontools-5.43_1
Polytropon freebsd at edvax.de writes:
...
Well, yes, BUT they seem to be redundant (that's why I asked).
# portmaster -L --index-only | egrep '(ew|ort) version|total install'
=== New version available: smartmontools-5.43_1
=== 618 total installed ports
=== 1 has a new
On Fri, 12 Oct 2012 04:35:43 + (UTC)
jb wrote:
Hi,
what is the diff between
--index
and
--index-only
From a *very* quick look, it appears that --index-only means don't use
the the port-directory at all, so that the index file is downloaded
into /tmp, and some checks and optimizations
INDEX-9
-rw-r--r-- 1 root wheel 1658547 Oct 12 12:01 INDEX-9.bz2
...
#
# find /tmp -name *INDEX*
# portmaster -L --index-only | egrep '(ew|ort) version|total install'
=== New version available: smartmontools-5.43_1
=== 618 total installed ports
=== 1 has a new version
Oct 12 07:47 INDEX-8
-rw-r--r-- 1 root wheel 26715339 Oct 12 13:28 INDEX-9
-rw-r--r-- 1 root wheel 1658547 Oct 12 12:01 INDEX-9.bz2
...
#
# find /tmp -name *INDEX*
# portmaster -L --index-only | egrep '(ew|ort) version|total install'
=== New version available
Polytropon freebsd at edvax.de writes:
...
But this?
# portmaster -L --index | egrep '(ew|ort) version|total install'
/tmp/d-87852-index/INDEX-9.bz2100% of 1619 kB 125 kBps
00m00s
Terminated
This is with --index and _no_ ports collection in the default
location
jb jb.1234abcd at gmail.com writes:
...
I have doubts about these options use, so I filed a PR#:
http://www.freebsd.org/cgi/query-pr.cgi?pr=172651
jb
___
freebsd-questions@freebsd.org mailing list
Hi,
what is the diff between
--index
and
--index-only
jb
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Hi,
what to do with that backup package (-b option) after installation of new port
failed ?
jb
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
On Mon, 8 Oct 2012 16:18:20 + (UTC), jb wrote:
Hi,
what to do with that backup package (-b option) after installation of new port
failed ?
Install it with pkg_add? :-)
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
) was missing libarchive.so via
portmaster or via core dumping install(1). By installing on one box, my
home box, port security/cyrus-sasl2 manually, luckily install(1) and
mtree(1) didn't coredump and it worked - and this precedure rescued me.
But on my lab's development box, it doesn't work!
Don't
amd64, I had to recompile all requirements of port Apache22, since after
the port update it core dumped.
On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and
installation of all portmaster -f apache-2.2 requirements went perfect.
On both FreeBSD 10-CURRENT boxes it ended up
On Fri, Aug 17, 2012 at 09:44:40AM +0200, Hartmann, O. wrote:
An installation failed due to pkg(ng) was missing libarchive.so via
There is pkg-static for recovering in this type of situation.
Oh ... I'm new to pkg(ng).
No worries. It is a nice thing to know about, since after a big
.
On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and
installation of all portmaster -f apache-2.2 requirements went perfect.
On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a
sudden(!), while reinstalling port security/cyrus-sasl2, things started
to fail in a dramatik
requirements of port Apache22, since after
the port update it core dumped.
On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and
installation of all portmaster -f apache-2.2 requirements went perfect.
On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a
sudden(!), while
On 8/16/2012 10:33 AM, Hartmann, O. wrote:
I tried to find rescue images and a rescue DVD of a snap shot server,
but there is no way to crawl through the informations on the web pages
towards a snapshot. All folders end up in 2011 and highly outdated
(www.freebsd.org, I didn't look at mirrors
.
On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and
installation of all portmaster -f apache-2.2 requirements went perfect.
On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a
sudden(!), while reinstalling port security/cyrus-sasl2, things started
to fail in a dramatik
On Thu, Aug 16, 2012 at 11:33 AM, O. Hartmann
ohart...@zedat.fu-berlin.de wrote:
I ran into a very delicate and nasty situation.
Please don't cross-post / double-post.
Thanks,
-Garrett
___
freebsd-questions@freebsd.org mailing list
into multiuser mode is impossible, login core dumps
SIGNAL 11, many other daemons, too. The only way is to boot into single
user mode.
I'm not drawing a correlation between this and unrelated coredumping processes.
An installation failed due to pkg(ng) was missing libarchive.so via
portmaster
to specify with -y to automatically answer those?
I've tried --clean-distfiles, --clean-packages but it's not it.
It usually happens when doing portmaster --packages-build
--delete-build-only
build.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/portmaster-embarrassingly-simple
when doing portmaster --packages-build
--delete-build-only
build.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/portmaster-embarrassingly-simple-question-y-option-tp5723878.html
Sent from the freebsd-questions mailing list archive at Nabble.com
.tar.gz? y/n [n]
What option do I need to specify with -y to automatically answer those?
Hi
-d
I've tried --clean-distfiles, --clean-packages but it's not it.
It usually happens when doing portmaster --packages-build
--delete-build-only
build.
Disclaimer: http://www.ose.nl/email
those?
I've tried --clean-distfiles, --clean-packages but it's not it.
It usually happens when doing portmaster --packages-build
--delete-build-only
build.
usually I use: portmaster -dbg port
-b create and keep a backup package of an installed port
-g create a package of the new
Excellent, I knew I was missing something simple.
Thanks!
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/portmaster-embarrassingly-simple-question-y-option-tp5723878p5723916.html
Sent from the freebsd-questions mailing list archive at Nabble.com
Now I see that I even used -d in my own portupdating
wrapper, but forgot about it and it's meaning, embarrassing.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/portmaster-embarrassingly-simple-question-y-option-tp5723878p5723918.html
Sent from the freebsd-questions
On 03/07/2012 13:06, Bas Smeelen wrote:
On 07/03/2012 12:29 PM, Jakub Lach wrote:
What option do I need to specify with -y to automatically answer those?
-d
Add this to ${LOCALBASE}/etc/portmaster.rc
ALWAYS_SCRUB_DISTFILES=dopt
if that's something you're going to be doing all the time.
2012-06-04 16:10, Leslie Jensen skrev:
2012-06-04 15:54, Warren Block skrev:
% printf \033];Funny Title\007
Works!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send
that was already there.
Let me know what you think,
Doug
--
This .signature sanitized for your protection
Index: portmaster
===
--- portmaster (revision 236697)
+++ portmaster (working copy)
@@ -2208,6 +2208,8 @@
}
term_printf
protection
Index: portmaster
===
--- portmaster (revision 236697)
+++ portmaster (working copy)
@@ -2208,6 +2208,8 @@
}
term_printf () {
+ case $1 in *\\*) echo -e \n\t${PM_PARENT_PORT}${1} ;; esac
+
[ -n $PM_NO_TERM_TITLE
2012-06-03 18:18, Warren Block skrev:
On Sun, 3 Jun 2012, Warren Block wrote:
On Sun, 3 Jun 2012, Leslie Jensen wrote:
2012-06-02 19:18, Doug Barton skrev:
On 6/2/2012 8:09 AM, Leslie Jensen wrote:
I'm thinking about some kind of information on the build progress
Portmaster already
for you, I've done thousands of portmaster
upgrades over ssh.
Let me know how it goes,
Doug
--
This .signature sanitized for your protection
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
title?
Nope. Should work just fine for you, I've done thousands of portmaster
upgrades over ssh.
Let me know how it goes,
Doug
I've set that dynamic title should go before initial title. I've also
tried the setting that it should replace initial title. None of the
settings changes anything
and
maybe it's because of that I cannot see any title?
Nope. Should work just fine for you, I've done thousands of portmaster
upgrades over ssh.
Let me know how it goes,
Doug
I've set that dynamic title should go before initial title. I've also
tried the setting that it should replace initial title
and
maybe it's because of that I cannot see any title?
Nope. Should work just fine for you, I've done thousands of portmaster
upgrades over ssh.
I've set that dynamic title should go before initial title. I've also tried
the setting that it should replace initial title. None of the settings
changes
2012-06-04 15:54, Warren Block skrev:
% printf \033];Funny Title\007
Works!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
On Sun, 3 Jun 2012, Leslie Jensen wrote:
2012-06-02 19:18, Doug Barton skrev:
On 6/2/2012 8:09 AM, Leslie Jensen wrote:
I'm thinking about some kind of information on the build progress
Portmaster already has that if you're building in a terminal window,
look in the titlebar. I can take
On Sun, 3 Jun 2012, Warren Block wrote:
On Sun, 3 Jun 2012, Leslie Jensen wrote:
2012-06-02 19:18, Doug Barton skrev:
On 6/2/2012 8:09 AM, Leslie Jensen wrote:
I'm thinking about some kind of information on the build progress
Portmaster already has that if you're building in a terminal
I'm thinking about some kind of information on the build progress when
one does larger updates like the newly recommendation in
/usr/ports/UPDATING
portmaster -r png-
I myself have three machines with different capacity when it comes to
building ports.
How about a knobb one could choose
On 6/2/2012 8:09 AM, Leslie Jensen wrote:
I'm thinking about some kind of information on the build progress
Portmaster already has that if you're building in a terminal window,
look in the titlebar. I can take a look at printing that in line if
you're not in a terminal window though.
hope
2012-06-02 19:18, Doug Barton skrev:
On 6/2/2012 8:09 AM, Leslie Jensen wrote:
I'm thinking about some kind of information on the build progress
Portmaster already has that if you're building in a terminal window,
look in the titlebar. I can take a look at printing that in line if
you're
Hello,
is there a chance that portmaster can be only fetch all Source which need
update?
I mean make fetch-recursiv has helped in the ports collection, when i think
right,
but can portmaster that with all packages they need update?
Thanks for help.
Regards
Silvio
On Mon, 28 May 2012 23:12:31 +0200, Silvio Siefke wrote:
Hello,
is there a chance that portmaster can be only fetch all Source which need
update?
I mean make fetch-recursiv has helped in the ports collection, when i think
right,
but can portmaster that with all packages they need update
On 28 May 2012 14:12, Silvio Siefke siefke_lis...@web.de wrote:
Hello,
is there a chance that portmaster can be only fetch all Source which need
update?
I mean make fetch-recursiv has helped in the ports collection, when i think
right,
but can portmaster that with all packages they need
I'm happy to use the -P option to let portmaster use packages for most
of my ports but there's a few that must be compiled from the port
instead because I need to configure non default options, e.g. to enable
GIMP plugin support in graphics/xsane
Is there any way of forcing portmaster
--On May 8, 2012 9:33:59 PM +0100 Mike Clarke jmc-freeb...@milibyte.co.uk
wrote:
I'm happy to use the -P option to let portmaster use packages for most
of my ports but there's a few that must be compiled from the port
instead because I need to configure non default options, e.g. to enable
On Tuesday 08 May 2012, John Webster wrote:
Would this work for you? From the manpage:
For those who wish to be sure that specific ports are always
compiled instead of being installed from packages the
PT_NO_INSTALL_PACKAGE vari- able can be defined in the make(1)
environment, perhaps
--On May 8, 2012 10:51:16 PM +0100 Mike Clarke jmc-freeb...@milibyte.co.uk
wrote:
On Tuesday 08 May 2012, John Webster wrote:
Would this work for you? From the manpage:
For those who wish to be sure that specific ports are always
compiled instead of being installed from packages
When I run:
portmaster -a --no-confirm
I get the error
Installing updates: chflags...///lib/libc.so.7: Operation not permitted
Changing chflags (presumably schg, but I tried the others) doesn't
appear to make any difference.
I'm not running any servers in jails.
Any ideas?
Thanks
Jorge Luis =?iso-8859-1?Q?Gonz=E1lez?= writes:
When I run:
portmaster -a --no-confirm
I get the error
Installing updates: chflags...///lib/libc.so.7: Operation not permitted
Changing chflags (presumably schg, but I tried the others) doesn't
appear to make any difference
On Wed, 2 May 2012 10:03:44 -0400
Robert Huff roberth...@rcn.com wrote:
Jorge Luis =?iso-8859-1?Q?Gonz=E1lez?= writes:
When I run:
portmaster -a --no-confirm
I get the error
Installing updates: chflags...///lib/libc.so.7: Operation not
permitted
Changing chflags
On Wed, 2 May 2012, Conrad J. Sabatier wrote:
On Wed, 2 May 2012 10:03:44 -0400
Robert Huff roberth...@rcn.com wrote:
Jorge Luis =?iso-8859-1?Q?Gonz=E1lez?= writes:
When I run:
portmaster -a --no-confirm
I get the error
Installing updates: chflags...///lib/libc.so.7: Operation
On 02.05.2012 14:59, Warren Block wrote:
On Wed, 2 May 2012, Conrad J. Sabatier wrote:
On Wed, 2 May 2012 10:03:44 -0400
Robert Huff roberth...@rcn.com wrote:
Jorge Luis =?iso-8859-1?Q?Gonz=E1lez?= writes:
When I run:
portmaster -a --no-confirm
I get the error
Installing updates
Volodymyr Kostyrko wrote:
[dd]
NO_BACKUP means don't create a temporary package when deleting
something. This is unsuitable for me as /usr/ports in my network is
distributed via NFS ro.
I also share /usr/ports via NFS ro, but I have defined
PACKAGES=/var/tmp/packages in portmaster.rc to
. Anyway if you tell portmaster to update
port x it would try to update all ports it depends on.
Does it often screw things up when updating dependencies (both
ascending and descending ones)? Do you recommend to always update the
ascending dependencies (portmaster -r) also?
[dd]
The better way
1 - 100 of 325 matches
Mail list logo
