How to disable staging support in ports tree universally?

[Jeremy Chadwick]

(Please keep me CC'd, as I am not subscribed to any FreeBSD lists)

Plain, simple, obvious question: how do I disable staging support in the
latest ports tree?

Today I rebuilt a port (which had been upgraded to remove NO_STAGE=yes
from it Makefile) as follows:

# make deinstall
# make clean install

...and proceeded to watch my /usr/ports filesystem I/O go through
the roof with unnecessary crap, starting about here:

===  Staging for sudo-1.8.8
===   Generating temporary packing list

...which is normal, except I suddenly start tons of disk I/O involving
$WRKDIR/stage, proceeded by this:

===  Building package for sudo-1.8.8
Creating package /usr/ports/security/sudo/work/sudo-1.8.8.tbz
Registering depends:.
Creating bzip'd tar ball in '/usr/ports/security/sudo/work/sudo-1.8.8.tbz'

All of this comes from Mk/bsd.port.mk, per _STAGE_SEQ, which is preceded
by a plain and simple .if !defined(NO_STAGE).

I thought okay, so just put NO_STAGE=yes in /etc/make.conf but
make.conf(5) had no mention of this so I was wary.  Then I found these
two posts clearly stating this is not a make.conf variable and things
will bust if you do that:

http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086692.html
http://lists.freebsd.org/pipermail/freebsd-ports/2013-October/086697.html

I tried it anyway (in a VM) -- yup, it sure does leave quite a mess
laying around if you set it globally, so definitely don't do that.

So I read /usr/ports/UPDATING, and /usr/ports/CHANGES, and this:

https://wiki.freebsd.org/ports/StageDir

...to no avail.

So how do I stop this staging nonsense when it doesn't apply to any of
my systems/environments?  I install third-party software directly from
the ports tree, I DO NOT USE pkg, nor do I ever plan on using pkg given
that I customise ports individually (through make config and some
make.conf knobs) quite heavily.

I want to know how to stop this excess waste of disk I/O when it doesn't
apply to my environments/systems, and I'm sure many others do as well.

-- 
| Jeremy Chadwick   j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Making life hard for others since 1977. PGP 4BD6C0CB |

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

portupgrade and pkgng (again)

[Alexey Dokuchaev]

Hi there,

I have a remote -CURRENT box which i'd rather not src-update now (r248373,
ca. March).  Apparently it's recent enough to default to pkgng.

I wanted to upgrade some ports of mine today, and installed my favorite
portupgrade just to discover that it does not see any packages: it seems
to fail to parse /var/db/pkg/local.sqlite (convert it to its own pkgdb.db)
and reports that I have nothing installed.

Usual dances with adding WITH_PKGNG to make.conf, pkgdb -fu et al. did not
help.  Any clues?

One note: I have rather old version of pkg installed, pkg-1.0.7.  I may
try to forcibly deinstall it and reinstall from ports, but I want to be
sure doing so won't render my existing package database unusable.  Is it
safe (and worth) thing to do?

Thanks,

./danfe
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: How to disable staging support in ports tree universally?

[Matthew Seaman]

On 12/10/2013 06:59, Jeremy Chadwick wrote:
 So how do I stop this staging nonsense when it doesn't apply to any of
 my systems/environments?  I install third-party software directly from
 the ports tree, I DO NOT USE pkg, nor do I ever plan on using pkg given
 that I customise ports individually (through make config and some
 make.conf knobs) quite heavily.

Revert your ports tree to r327909 or earlier and stick with that.

I'm sorry that you find the recent large scale changes to the ports tree
to be beyond your comfort zone.  Unfortunately, these changes are
vitally necessary for the future of the FreeBSD project -- the ports
were revolutionary 20 odd years ago, but since then, structurally they
have stagnated and there has been no real strategic development for far
too long.

Yes, there are a lot of changes happening at the moment.  We're trying
to catch up with ten or more years of progress in a year or so.  The
technical reasoning behind our implementing these changes has been
discussed elsewhere so I'll not rehash it further here other than to say
that the vast majority of ports users and developers are behind where
we're going with this.

Staging is here to stay.  There's no way of turnng it off.  If the
amount of disk-IO involved in installing ported software really is a
limitation for you, then perhaps you should consider using pkg and
installing from binary packages -- you might think that staging involves
a lot of IO, but it's peanuts compared to *compiling*.

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature

Build failure - Licensing issue - libtool

[Dewayne-remote]

I came across a build issue that was associated with licencing changes. 
While trying to build libtool I experienced this failure during package
removal, in anticipation of a complete rebuild:

Another was pkg_delete: file
'/usr/local/share/licenses/libtool-2.4.2_1/LICENSE' doesn't exist
pkg_delete: file '/usr/local/share/licenses/libtool-2.4.2_1/GPLv2'
doesn't exist
pkg_delete: file '/usr/local/share/licenses/libtool-2.4.2_1' doesn't exist

which then prevented a build with the following messages
+ portmaster --no-term-title --no-confirm -H -D -g -G -B
--update-if-newer -v devel/libtool
tar: share/licenses/libtool-2.4.2_2/catalog.mk: Cannot stat: No such
file or directory
tar: share/licenses/libtool-2.4.2_2/LICENSE: Cannot stat: No such file
or directory
tar: share/licenses/libtool-2.4.2_2/GPLv2: Cannot stat: No such file or
directory

Do this.
echo DISABLE_LICENSES=yes  /etc/make.conf

Discovered by searching /usr/ports/Mk/*, specifically bsd.licenses.mk

Libtool was one of many ports that failed during the build.
Regards, Dewayne.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: portupgrade and pkgng (again)

[Matthew Seaman]

On 12/10/2013 08:36, Alexey Dokuchaev wrote:
 I have a remote -CURRENT box which i'd rather not src-update now (r248373,
 ca. March).  Apparently it's recent enough to default to pkgng.
 
 I wanted to upgrade some ports of mine today, and installed my favorite
 portupgrade just to discover that it does not see any packages: it seems
 to fail to parse /var/db/pkg/local.sqlite (convert it to its own pkgdb.db)
 and reports that I have nothing installed.

I believe that recent versions of portupgrade use the pkg database
directly, rather than maintaining a parallel pkgdb.db.

 Usual dances with adding WITH_PKGNG to make.conf, pkgdb -fu et al. did not
 help.  Any clues?
 
 One note: I have rather old version of pkg installed, pkg-1.0.7.  I may
 try to forcibly deinstall it and reinstall from ports, but I want to be
 sure doing so won't render my existing package database unusable.  Is it
 safe (and worth) thing to do?

Yes, you definitely should update to an up to date version of pkg.
There's lots of stuff that has changed in parallel with changes to the
ports, and keeping both in synch will produce the best results.

pkg should be able to update your local.sqlite to the current schema
versions -- obviously, backup your /var/db/pkg before you attempt the
update -- but I think it should go pretty smoothly for you.

If you're particularly worried -- use 'pkg create' to generate pkg
tarballs of everything you've got installed, and save the output of 'pkg
info -qoa' (which should just be a list of your installed ports, by
origin).  That means that even if your local.sqlite gets trashed, you
can simply re-install everything against an empty database.  But this
really shouldn't be necessary.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.

PGP: http://www.infracaninophile.co.uk/pgpkey
JID: matt...@infracaninophile.co.uk



signature.asc
Description: OpenPGP digital signature

cyrus-sasl2-saslauthd package failure.

[Dewayne-remote]

While attempting to rebuild all my 500+ ports for servers only, I came
across this issue with saslauthd.

The installation is successful, but the package assembly fails with:
tar: etc/rc.d/saslauthd: Cannot stat: No such file or directory

But the file is correctly installed in staging
# ls -l /staging/usr/local/etc/rc.d/saslauthd /usr/local/etc/rc.d/saslauthd
ls: /usr/local/etc/rc.d/saslauthd: No such file or directory
-r-xr-xr-x  1 root  wheel  940 Oct 12 19:28
/staging/usr/local/etc/rc.d/saslauthd

The command to build is:
make __MAKE_CONF=/dev/null DISTDIR=/distfiles WRKDIRPREFIX=/var/ports
PACKAGES= /packages STAGEDIR=/staging FAVORITE_COMPILER=gcc
DISABLE_LICENSES=yes -DBATCH DEFAULT_VERSIONS=perl5=5.16 python=2.7
python2=2.7 apache=22 clean deinstall package

The process succeeds with the build and installation into $STAGEDIR

The tail of the log follows:
cd
/var/ports/usr/ports/security/cyrus-sasl2-saslauthd/work/cyrus-sasl-2.1.26/saslauthd
 make saslcache
cc -DHAVE_CONFIG_H
-DSASLAUTHD_CONF_FILE_DEFAULT=\/usr/local/etc/saslauthd.conf\ -I. -I.
-I.. -I. -I./include -I./include -I./../include   -I/usr/include
-DKRB5_HEIMDAL  -O2 -pipe -nostdinc -I/usr/include -fno-strict-aliasing
-MT saslcache.o -MD -MP -MF .deps/saslcache.Tpo -c -o saslcache.o
saslcache.c
In file included from cache.h:44,
 from saslcache.c:52:
saslauthd.h:190:1: warning: KRB5_HEIMDAL redefined
command-line: warning: this is the location of the previous definition
mv -f .deps/saslcache.Tpo .deps/saslcache.Po
cc  -O2 -pipe -nostdinc -I/usr/include -fno-strict-aliasing 
-Wl,-rpath=/usr/lib:/usr/local/lib -L/usr/lib -o saslcache saslcache.o
cd
/var/ports/usr/ports/security/cyrus-sasl2-saslauthd/work/cyrus-sasl-2.1.26/saslauthd
 make testsaslauthd
`testsaslauthd' is up to date.
===  Installing for cyrus-sasl-saslauthd-2.1.26
===   Generating temporary packing list
===  Checking if security/cyrus-sasl2-saslauthd already installed
test -z /usr/local/sbin || /bin/mkdir -p /usr/local/sbin
  install  -s -o root -g wheel -m 555 saslauthd testsaslauthd
'/usr/local/sbin'
/bin/sh ./config/mkinstalldirs /usr/local/man/man8
install  -o root -g wheel -m 444 ./saslauthd.mdoc
/usr/local/man/man8/saslauthd.8
=== Staging rc.d startup script(s)
/bin/mkdir -p -m 770 /var/run/saslauthd
/usr/sbin/chown cyrus:mail /var/run/saslauthd


To run saslauthd from startup, add saslauthd_enable=YES in your
/etc/rc.conf.


===   Compressing manual pages for cyrus-sasl-saslauthd-2.1.26
===   Registering installation for cyrus-sasl-saslauthd-2.1.26
=== SECURITY REPORT:
  This port has installed the following files which may act as network
  servers and may therefore pose a remote security risk to the system.
/usr/local/sbin/saslauthd

  This port has installed the following startup scripts which may cause
  these network services to be started at boot time.
/usr/local/etc/rc.d/saslauthd

  If there are vulnerabilities in these programs there may be a security
  risk to the system. FreeBSD makes no guarantee about the security of
  ports included in the Ports Collection. Please type 'make deinstall'
  to deinstall the port if this is a concern.

  For more information, and contact details about the security
  status of this software, see the following webpage:
http://cyrusimap.web.cmu.edu/
===  Building package for cyrus-sasl-saslauthd-2.1.26
tar: etc/rc.d/saslauthd: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** [do-package] Error code 1

--End of saslauthd
log-
A similar result is achieved for samba36, samba4, isc-dhcp42-server; viz
===  Building package for isc-dhcp42-server-4.2.5
tar: etc/rc.d/isc-dhcpd: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** [do-package] Error code 1

# ls -l /staging/usr/local/etc/rc.d/isc-dhcpd /usr/local/etc/rc.d/isc-dhcpd
ls: /usr/local/etc/rc.d/isc-dhcpd: No such file or directory
-r-xr-xr-x  1 root  wheel  11816 Oct 12 19:39
/staging/usr/local/etc/rc.d/isc-dhcpd

I can't see what I need to workaround to avoid this issue?
Regards, Dewayne
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: security/gnupg installation failed

[Andriy Gapon]

[ping]

on 05/10/2013 15:03 Andriy Gapon said the following:
 
 I have the following configuration for the port:
 === The following configuration options are available for gnupg-2.0.22:
  PINENTRY=on: Use pinentry
  LDAP=off: LDAP keyserver interface
  SCDAEMON=off: Enable Smartcard daemon (with libusb)
  CURL=on: Use the real curl library (worked around if no)
  GPGSM=off: Enable GPGSM (requires LDAP)
  KDNS=off: Use DNS CERT helper
  STD_SOCKET=off: Use standard socket for agent
  NLS=off: Native Language Support
  DOCS=off: Build and/or install documentation
  SUID_GPG=off: Install GPG with suid
 === Use 'make config' to modify these settings
 
 
 Installation fails like this:
 ===  Checking if security/gnupg already installed
 ===   Registering installation for gnupg-2.0.22 as automatic
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/com-certs.pem):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.be.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.ca.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.cs.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.da.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.de.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.el.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.eo.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.es.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.et.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.fi.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.fr.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.gl.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.hu.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.id.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.it.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.ja.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.nb.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.pl.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.pt.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.pt_BR.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.ro.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.ru.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.sk.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.sv.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.tr.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.zh_CN.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/help.zh_TW.txt):
 No such file or directory
 pkg-static:
 lstat(/usr/obj/ports/usr/ports/security/gnupg/work/stage/usr/local/share/gnupg/qualified.txt):
 No such file or directory
 *** Error code 74
 


-- 
Andriy Gapon
___
freebsd-ports@freebsd.org mailing 

Re: How to disable staging support in ports tree universally?

[Torfinn Ingolfsen]

Hello,

On Sat, Oct 12, 2013 at 10:15 AM, Matthew Seaman matt...@freebsd.org wrote:

 Staging is here to stay.  There's no way of turnng it off.  If the

Why? Why can't it be turned off?
What is the technical reason / reasoning behind this design decision?
And why is staging special, compared to all other features that has
been introduced to FreeBSD in the last few years?

-- 
Regards,
Torfinn Ingolfsen
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Calling all ruby enthusiasts

[Thomas Abthorpe]

I have been working toward getting lang/ruby18 removed from the ports
tree, it is vulnerable, and no longer supported upstream.  If you have
been watching the commit logs, you will see the work I have already put
into it's removal.  My personal thanks to Steve Wills (swills@) for
helping me through much of the process.

I have made some contact with some of you already about updating some
ports, but more work has to be done to get ruby18 removed.  You are
being contacted because you are a maintainer of one of the ports listed
below.

The first column is a port that has a DEPRECATED dependency, the second column
is the port targeted for removal.

Mk/bsd.lua.mk   lang/ruby-lua4
devel/rubygem-rascutwww/rubygem-mongerl
devel/rubygem-rascutwww/rubygem-mongrel
devel/rubygem-ruby-debug-base   devel/rubygem-linecache
dns/dnsdoctor   lang/ruby18
games/magicmaze devel/ruby-sdl
japanese/gorua  x11-toolkits/ruby-gtk
security/flowtagx11-toolkits/ruby-tk
sysutils/puppet www/rubygem-mongerl
sysutils/puppet27   www/rubygem-mongerl
www/aswiki  textproc/ruby-amrita
www/rubygem-rails   www/rubygem-mongerl
www/rubygem-staticmatic www/rubygem-mongerl
www/tdiary  www/ruby-nora
www/typowww/rubygem-mongrel_cluster
www/typowww/rubygem-rails-app-installer

It would appear that making www/rubygem-mongerl* work with ruby19 would
be the biggest first step toward the final cleanup.

If you have some time, and want to help out, please find a port listed
above, fix it for ruby19, and file a PR to get it committed.

It is that easy :)

Thanks for all your help in advance.


Thomas

-- 
Thomas Abthorpe | FreeBSD Committer
tabtho...@freebsd.org   | http://people.freebsd.org/~tabthorpe


pgp6GrAhh3_75.pgp
Description: PGP signature

Re: portupgrade and pkgng (again)

[Bryan Drewery]

On 10/12/2013 2:36 AM, Alexey Dokuchaev wrote:
 Hi there,
 
 I have a remote -CURRENT box which i'd rather not src-update now (r248373,
 ca. March).  Apparently it's recent enough to default to pkgng.
 
 I wanted to upgrade some ports of mine today, and installed my favorite
 portupgrade just to discover that it does not see any packages: it seems
 to fail to parse /var/db/pkg/local.sqlite (convert it to its own pkgdb.db)
 and reports that I have nothing installed.

This doesn't happen anymore. It just reads directly from pkg-query now.

 
 Usual dances with adding WITH_PKGNG to make.conf, pkgdb -fu et al. did not
 help.  Any clues?
 
 One note: I have rather old version of pkg installed, pkg-1.0.7.  I may

This is the problem. Portmaster and Portupgrade do not support 1.0.x.
They require 1.x.x now due to using 'pkg info -x' to look for pkg or
pkg-devel installed.

 try to forcibly deinstall it and reinstall from ports, but I want to be
 sure doing so won't render my existing package database unusable.  Is it
 safe (and worth) thing to do?
 
 Thanks,
 
 ./danfe
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
 


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: How to disable staging support in ports tree universally?

[Daniel Nebdal]

On Sat, Oct 12, 2013 at 11:08 AM, Torfinn Ingolfsen tin...@gmail.com wrote:
 Hello,

 On Sat, Oct 12, 2013 at 10:15 AM, Matthew Seaman matt...@freebsd.org wrote:

 Staging is here to stay.  There's no way of turnng it off.  If the

 Why? Why can't it be turned off?
 What is the technical reason / reasoning behind this design decision?
 And why is staging special, compared to all other features that has
 been introduced to FreeBSD in the last few years?

 --
 Regards,
 Torfinn Ingolfsen

As I've understood it, it's not so much a feature as an
infrastructure *change* - asking to disable it is, from now on, about
as meaningful as asking if you could disable the fetch stage.


-- 
Daniel Nebdal
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: 10.0-hosted tinderbox: 8.4 builds broken?

[Chris Rees]

[cross posted to tinderbox-list]

On 2013-10-09 22:27, Alexey Dokuchaev wrote:

On Wed, Oct 09, 2013 at 09:11:10PM +0100, Chris Rees wrote:

Alexey, if you're interested, the patch hitting CVS is at:

http://www.bayofrum.net/~crees/patches/tinderbox-calculate-deps-in-chroot-9.diff


Ah, it seems you mean it's one of the patches recently committed, not 
the

proposed fix. ;-)

I've 'cvs up -A' again, and applied the patch in reverse mode.  
Strangely,
now every build log (inc. dependent packages) immediately ends with 
this

message:

  jexec: getpwnam: root: No such file or directory


OK, try cvs head with

http://www.bayofrum.net/~crees/patches/tinderbox-chroot-srcbase.diff

It appears that I may have been overexcited with my fix for Olli's 
problem, but this fixes it in a less drastic way with fewer assumptions.


This patch works for me, so if you confirm I'd like to ask Joe to 
approve please!


Also, Bernhard, I'm certain that redports will run as well as it did 
with patch7 if you apply this patch.


I'm really sorry for the breakage :(

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: How to disable staging support in ports tree universally?

[Kimmo Paasiala]

On Sat, Oct 12, 2013 at 2:35 PM, Daniel Nebdal dneb...@gmail.com wrote:
 On Sat, Oct 12, 2013 at 11:08 AM, Torfinn Ingolfsen tin...@gmail.com wrote:
 Hello,

 On Sat, Oct 12, 2013 at 10:15 AM, Matthew Seaman matt...@freebsd.org wrote:

 Staging is here to stay.  There's no way of turnng it off.  If the

 Why? Why can't it be turned off?
 What is the technical reason / reasoning behind this design decision?
 And why is staging special, compared to all other features that has
 been introduced to FreeBSD in the last few years?

 --
 Regards,
 Torfinn Ingolfsen

 As I've understood it, it's not so much a feature as an
 infrastructure *change* - asking to disable it is, from now on, about
 as meaningful as asking if you could disable the fetch stage.



Staging solves so many problems with the FreeBSD ports(7) system that
it's very worthwhile to go trough the bumpy road of fixing the
individual ports that don't play well with it. Looking at it now I
hope these developments had happened 5 years earlier but as they say,
better late than never.

-Kimmo
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: How to disable staging support in ports tree universally?

[Alexey Dokuchaev]

On Sat, Oct 12, 2013 at 09:15:25AM +0100, Matthew Seaman wrote:
 Yes, there are a lot of changes happening at the moment.  We're trying
 to catch up with ten or more years of progress in a year or so.  The
 technical reasoning behind our implementing these changes has been
 discussed elsewhere so I'll not rehash it further here other than to say
 that the vast majority of ports users and developers are behind where
 we're going with this.

One of the most annoying things about staging (for me) is that it broke
many ports make install from regular user.  E.g. audio/faad and misc/mc
are affected, just to name a few.

At a glance, it happens because they first install files with 444 perms,
and then try to do something on them.  Previously it was done after su(1)
had asked for root, but with staging, it's done as user, and thus fails.

./danfe
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: problems after installing ports-mgmt/portconf

[Matthias Apitz]

El día Friday, October 11, 2013 a las 06:16:23PM -0500, Matthew D. Fuller 
escribió:

 On Fri, Oct 11, 2013 at 09:37:13AM +0200 I heard the voice of
 Matthias Apitz, and lo! it spake thus:
  
  I have had to uninstall portconf again to be able to build more ports.
 
 Near's I can tell, portconf and bmake just flat out don't get along.
 With some squirreling around in make.conf, you can make _that_ warning
 shut up, but you just wind up with a different one for ports that you
 have portconf stuff for.  I stopped investigating at that point  :|

Maybe my English is poor, I do not understand your message. Please
clarify. Thx

matthias
-- 
Matthias Apitz   |  /\ ASCII Ribbon Campaign: www.asciiribbon.org
E-mail: g...@unixarea.de |  \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ |   X  - No proprietary attachments
phone: +49-170-4527211   |  / \ - Respect for open standards
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: How to disable staging support in ports tree universally?

[Matthew Seaman]

On 12/10/2013 14:44, Alexey Dokuchaev wrote:
 On Sat, Oct 12, 2013 at 09:15:25AM +0100, Matthew Seaman wrote:
 Yes, there are a lot of changes happening at the moment.  We're trying
 to catch up with ten or more years of progress in a year or so.  The
 technical reasoning behind our implementing these changes has been
 discussed elsewhere so I'll not rehash it further here other than to say
 that the vast majority of ports users and developers are behind where
 we're going with this.
 
 One of the most annoying things about staging (for me) is that it broke
 many ports make install from regular user.  E.g. audio/faad and misc/mc
 are affected, just to name a few.
 
 At a glance, it happens because they first install files with 444 perms,
 and then try to do something on them.  Previously it was done after su(1)
 had asked for root, but with staging, it's done as user, and thus fails.

That's what NEED_ROOT is intended for.  If a port changes ownership or
does privileged things with permissions on files then you can't 'make
stage' as an ordinary user.  Adding NEED_ROOT=yes to the port will cause
it to try and obtain rootly powers via su(1) in order to do that sort of
thing.

Looks like audio/faad has been stageified -- in which case a missing
NEED_ROOT is a bug, while misc/mc is still NO_STAGE=yes so shouldn't
have been affected at all yet.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature

Re: problems after installing ports-mgmt/portconf

[Eitan Adler]

On Sat, Oct 12, 2013 at 11:43 AM, Matthias Apitz g...@unixarea.de wrote:
 El día Friday, October 11, 2013 a las 06:16:23PM -0500, Matthew D. Fuller 
 escribió:

 On Fri, Oct 11, 2013 at 09:37:13AM +0200 I heard the voice of
 Matthias Apitz, and lo! it spake thus:
 
  I have had to uninstall portconf again to be able to build more ports.

 Near's I can tell, portconf and bmake just flat out don't get along.
 With some squirreling around in make.conf, you can make _that_ warning
 shut up, but you just wind up with a different one for ports that you
 have portconf stuff for.  I stopped investigating at that point  :|

 Maybe my English is poor, I do not understand your message. Please
 clarify. Thx

Translation:
bmake and portconf are not compatible. Once you fix the couldn't read
shell's output error, there are others.


-- 
Eitan Adler
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: cyrus-sasl2-saslauthd package failure.

[Scot Hetzel]

On Sat, Oct 12, 2013 at 3:44 AM, Dewayne-remote
dewayne.gerag...@heuristicsystems.com.au wrote:
 While attempting to rebuild all my 500+ ports for servers only, I came
 across this issue with saslauthd.

 The installation is successful, but the package assembly fails with:
 tar: etc/rc.d/saslauthd: Cannot stat: No such file or directory

 But the file is correctly installed in staging
 # ls -l /staging/usr/local/etc/rc.d/saslauthd /usr/local/etc/rc.d/saslauthd
 ls: /usr/local/etc/rc.d/saslauthd: No such file or directory
 -r-xr-xr-x  1 root  wheel  940 Oct 12 19:28
 /staging/usr/local/etc/rc.d/saslauthd

 The command to build is:
 make __MAKE_CONF=/dev/null DISTDIR=/distfiles WRKDIRPREFIX=/var/ports
 PACKAGES= /packages STAGEDIR=/staging FAVORITE_COMPILER=gcc
 DISABLE_LICENSES=yes -DBATCH DEFAULT_VERSIONS=perl5=5.16 python=2.7
 python2=2.7 apache=22 clean deinstall package

 The process succeeds with the build and installation into $STAGEDIR

 The tail of the log follows:
 cd
 /var/ports/usr/ports/security/cyrus-sasl2-saslauthd/work/cyrus-sasl-2.1.26/saslauthd
  make saslcache
 cc -DHAVE_CONFIG_H
 -DSASLAUTHD_CONF_FILE_DEFAULT=\/usr/local/etc/saslauthd.conf\ -I. -I.
 -I.. -I. -I./include -I./include -I./../include   -I/usr/include
 -DKRB5_HEIMDAL  -O2 -pipe -nostdinc -I/usr/include -fno-strict-aliasing
 -MT saslcache.o -MD -MP -MF .deps/saslcache.Tpo -c -o saslcache.o
 saslcache.c
 In file included from cache.h:44,
  from saslcache.c:52:
 saslauthd.h:190:1: warning: KRB5_HEIMDAL redefined
 command-line: warning: this is the location of the previous definition
 mv -f .deps/saslcache.Tpo .deps/saslcache.Po
 cc  -O2 -pipe -nostdinc -I/usr/include -fno-strict-aliasing
 -Wl,-rpath=/usr/lib:/usr/local/lib -L/usr/lib -o saslcache saslcache.o
 cd
 /var/ports/usr/ports/security/cyrus-sasl2-saslauthd/work/cyrus-sasl-2.1.26/saslauthd
  make testsaslauthd
 `testsaslauthd' is up to date.
 ===  Installing for cyrus-sasl-saslauthd-2.1.26
 ===   Generating temporary packing list
 ===  Checking if security/cyrus-sasl2-saslauthd already installed
 test -z /usr/local/sbin || /bin/mkdir -p /usr/local/sbin
   install  -s -o root -g wheel -m 555 saslauthd testsaslauthd
 '/usr/local/sbin'
 /bin/sh ./config/mkinstalldirs /usr/local/man/man8
 install  -o root -g wheel -m 444 ./saslauthd.mdoc
 /usr/local/man/man8/saslauthd.8
 === Staging rc.d startup script(s)
 /bin/mkdir -p -m 770 /var/run/saslauthd
 /usr/sbin/chown cyrus:mail /var/run/saslauthd
 

 To run saslauthd from startup, add saslauthd_enable=YES in your
 /etc/rc.conf.

 
 ===   Compressing manual pages for cyrus-sasl-saslauthd-2.1.26
 ===   Registering installation for cyrus-sasl-saslauthd-2.1.26
 === SECURITY REPORT:
   This port has installed the following files which may act as network
   servers and may therefore pose a remote security risk to the system.
 /usr/local/sbin/saslauthd

   This port has installed the following startup scripts which may cause
   these network services to be started at boot time.
 /usr/local/etc/rc.d/saslauthd

   If there are vulnerabilities in these programs there may be a security
   risk to the system. FreeBSD makes no guarantee about the security of
   ports included in the Ports Collection. Please type 'make deinstall'
   to deinstall the port if this is a concern.

   For more information, and contact details about the security
   status of this software, see the following webpage:
 http://cyrusimap.web.cmu.edu/
 ===  Building package for cyrus-sasl-saslauthd-2.1.26
 tar: etc/rc.d/saslauthd: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors.
 pkg_create: make_dist: tar command failed with code 256
 *** [do-package] Error code 1

 --End of saslauthd
 log-
 A similar result is achieved for samba36, samba4, isc-dhcp42-server; viz
 ===  Building package for isc-dhcp42-server-4.2.5
 tar: etc/rc.d/isc-dhcpd: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors.
 pkg_create: make_dist: tar command failed with code 256
 *** [do-package] Error code 1

 # ls -l /staging/usr/local/etc/rc.d/isc-dhcpd /usr/local/etc/rc.d/isc-dhcpd
 ls: /usr/local/etc/rc.d/isc-dhcpd: No such file or directory
 -r-xr-xr-x  1 root  wheel  11816 Oct 12 19:39
 /staging/usr/local/etc/rc.d/isc-dhcpd

 I can't see what I need to workaround to avoid this issue?

The problem is that you defined STAGEDIR, but these ports are marked NO_STAGE

I tried to add a .undef STAGEDIR to bsd.port.mk:

--- /usr/ports/Mk.bsd.port.mk
+++ /usr/ports/Mk.bsd.port.mk
@@ -1932,6 +1932,8 @@
 .if !defined(NO_STAGE)
 .include ${PORTSDIR}/Mk/bsd.stage.mk
+.else
+.undef STAGEDIR
 .endif

The above works, if you put STAGEDIR into /etc/make.conf.

# echo 

Re: cyrus-sasl2-saslauthd package failure.

[Scot Hetzel]

 I tried to add a .undef STAGEDIR to bsd.port.mk:

 --- /usr/ports/Mk.bsd.port.mk
 +++ /usr/ports/Mk.bsd.port.mk
 @@ -1932,6 +1932,8 @@
  .if !defined(NO_STAGE)
  .include ${PORTSDIR}/Mk/bsd.stage.mk
 +.else
 +.undef STAGEDIR
 +.if defined(STAGEDIR)
 +IGNORE= STAGEDIR defined on the command line, don't do that
 +.endif
  .endif


This change catches the use of STAGEDIR defined on the command line
and sets the IGNORE flag.  But I still can't undefined STAGEDIR when
it is defined on the command line.

 The above works, if you put STAGEDIR into /etc/make.conf.

 # echo 'STAGEDIR=/stagetest'  /etc/make.conf
 # make -V STAGEDIR

 But it doesn't work if you define STAGEDIR with the make command:

 # make STAGEDIR=/stage -V STAGEDIR
 /stage

 Does anyone know how to make this work?

 --
 DISCLAIMER:

 No electrons were maimed while sending this message. Only slightly bruised.



-- 
DISCLAIMER:

No electrons were maimed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

[QAT] r330177: 8x leftovers

[Ports-QAT]

avoid package name collisions.
-

  Build ID:  20131012190600-38561
  Job owner: u...@freebsd.org
  Buildtime: 63 minutes
  Enddate:   Sat, 12 Oct 2013 20:08:43 GMT

  Revision:  r330177
  Repository:
https://svnweb.freebsd.org/ports?view=revisionrevision=330177

-

Port:audio/gkrellmms2 2.1.22_9

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~u...@freebsd.org/20131012190600-38561-206416/gkrellmms2-2.1.22_9.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~u...@freebsd.org/20131012190600-38561-206417/gkrellmms2-2.1.22_9.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~u...@freebsd.org/20131012190600-38561-206418/gkrellmms2-2.1.22_9.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~u...@freebsd.org/20131012190600-38561-206419/gkrellmms2-2.1.22_9.log

-

Port:audio/gkrellmvolume2 2.1.13_9

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~u...@freebsd.org/20131012190600-38561-206420/gkrellmvolume2-2.1.13_9.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~u...@freebsd.org/20131012190600-38561-206421/gkrellmvolume2-2.1.13_9.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~u...@freebsd.org/20131012190600-38561-206422/gkrellmvolume2-2.1.13_9.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~u...@freebsd.org/20131012190600-38561-206423/gkrellmvolume2-2.1.13_9.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/20131012190600-38561
redports https://qat.redports.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: /usr/src/lib/msun errors

[Joe Nosay]

I don't have that entry.
Hold a sec.


On Sat, Oct 12, 2013 at 5:33 PM, Dimitry Andric d...@freebsd.org wrote:

 On Oct 12, 2013, at 23:27, Joe Nosay superbisq...@gmail.com wrote:
  $ lynx
  /usr/local/lib/libintl.so.9: Undefined symbol
 libiconv_set_relocation_prefix
  $
  $ firefox
  XPCOMGlueLoad error for file /usr/local/lib/firefox/libxpcom.so:
  /usr/local/lib/libglib-2.0.so.0: Undefined symbol libiconv
  Couldn't load XPCOM.

 Please read the 20130904 entry in /usr/ports/UPDATING.


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: /usr/src/lib/msun errors

[Joe Nosay]

Firefox will not start, lynx will not start, and Opera keeps crashing. I am
having trouble accessing ports.txz and the proper way for updating. I also
have a mixed system- I am emphasizing this- with older and newer /base and
/usr/src. I had hosed my system somewhat. It would be nice if someone was
here in person to see what is happening and to say, Hey, you fucked up;
but, here's how to fix that.





On Sat, Oct 12, 2013 at 5:38 PM, Joe Nosay superbisq...@gmail.com wrote:


 I don't have that entry.
 Hold a sec.


 On Sat, Oct 12, 2013 at 5:33 PM, Dimitry Andric d...@freebsd.org wrote:

 On Oct 12, 2013, at 23:27, Joe Nosay superbisq...@gmail.com wrote:
  $ lynx
  /usr/local/lib/libintl.so.9: Undefined symbol
 libiconv_set_relocation_prefix
  $
  $ firefox
  XPCOMGlueLoad error for file /usr/local/lib/firefox/libxpcom.so:
  /usr/local/lib/libglib-2.0.so.0: Undefined symbol libiconv
  Couldn't load XPCOM.

 Please read the 20130904 entry in /usr/ports/UPDATING.



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: cyrus-sasl2-saslauthd package failure.

[Dewayne]

On 13/10/2013 3:51 AM, Scot Hetzel wrote:
 On Sat, Oct 12, 2013 at 3:44 AM, Dewayne-remote
 dewayne.gerag...@heuristicsystems.com.au wrote:
 While attempting to rebuild all my 500+ ports for servers only, I came
 across this issue with saslauthd.

 The installation is successful, but the package assembly fails with:
 tar: etc/rc.d/saslauthd: Cannot stat: No such file or directory

 But the file is correctly installed in staging
 # ls -l /staging/usr/local/etc/rc.d/saslauthd /usr/local/etc/rc.d/saslauthd
 ls: /usr/local/etc/rc.d/saslauthd: No such file or directory
 -r-xr-xr-x  1 root  wheel  940 Oct 12 19:28
 /staging/usr/local/etc/rc.d/saslauthd

 The command to build is:
 make __MAKE_CONF=/dev/null DISTDIR=/distfiles WRKDIRPREFIX=/var/ports
 PACKAGES= /packages STAGEDIR=/staging FAVORITE_COMPILER=gcc
 DISABLE_LICENSES=yes -DBATCH DEFAULT_VERSIONS=perl5=5.16 python=2.7
 python2=2.7 apache=22 clean deinstall package

 The process succeeds with the build and installation into $STAGEDIR

 The tail of the log follows:
 cd
 /var/ports/usr/ports/security/cyrus-sasl2-saslauthd/work/cyrus-sasl-2.1.26/saslauthd
  make saslcache
 cc -DHAVE_CONFIG_H
 -DSASLAUTHD_CONF_FILE_DEFAULT=\/usr/local/etc/saslauthd.conf\ -I. -I.
 -I.. -I. -I./include -I./include -I./../include   -I/usr/include
 -DKRB5_HEIMDAL  -O2 -pipe -nostdinc -I/usr/include -fno-strict-aliasing
 -MT saslcache.o -MD -MP -MF .deps/saslcache.Tpo -c -o saslcache.o
 saslcache.c
 In file included from cache.h:44,
  from saslcache.c:52:
 saslauthd.h:190:1: warning: KRB5_HEIMDAL redefined
 command-line: warning: this is the location of the previous definition
 mv -f .deps/saslcache.Tpo .deps/saslcache.Po
 cc  -O2 -pipe -nostdinc -I/usr/include -fno-strict-aliasing
 -Wl,-rpath=/usr/lib:/usr/local/lib -L/usr/lib -o saslcache saslcache.o
 cd
 /var/ports/usr/ports/security/cyrus-sasl2-saslauthd/work/cyrus-sasl-2.1.26/saslauthd
  make testsaslauthd
 `testsaslauthd' is up to date.
 ===  Installing for cyrus-sasl-saslauthd-2.1.26
 ===   Generating temporary packing list
 ===  Checking if security/cyrus-sasl2-saslauthd already installed
 test -z /usr/local/sbin || /bin/mkdir -p /usr/local/sbin
   install  -s -o root -g wheel -m 555 saslauthd testsaslauthd
 '/usr/local/sbin'
 /bin/sh ./config/mkinstalldirs /usr/local/man/man8
 install  -o root -g wheel -m 444 ./saslauthd.mdoc
 /usr/local/man/man8/saslauthd.8
 === Staging rc.d startup script(s)
 /bin/mkdir -p -m 770 /var/run/saslauthd
 /usr/sbin/chown cyrus:mail /var/run/saslauthd
 

 To run saslauthd from startup, add saslauthd_enable=YES in your
 /etc/rc.conf.

 
 ===   Compressing manual pages for cyrus-sasl-saslauthd-2.1.26
 ===   Registering installation for cyrus-sasl-saslauthd-2.1.26
 === SECURITY REPORT:
   This port has installed the following files which may act as network
   servers and may therefore pose a remote security risk to the system.
 /usr/local/sbin/saslauthd

   This port has installed the following startup scripts which may cause
   these network services to be started at boot time.
 /usr/local/etc/rc.d/saslauthd

   If there are vulnerabilities in these programs there may be a security
   risk to the system. FreeBSD makes no guarantee about the security of
   ports included in the Ports Collection. Please type 'make deinstall'
   to deinstall the port if this is a concern.

   For more information, and contact details about the security
   status of this software, see the following webpage:
 http://cyrusimap.web.cmu.edu/
 ===  Building package for cyrus-sasl-saslauthd-2.1.26
 tar: etc/rc.d/saslauthd: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors.
 pkg_create: make_dist: tar command failed with code 256
 *** [do-package] Error code 1

 --End of saslauthd
 log-
 A similar result is achieved for samba36, samba4, isc-dhcp42-server; viz
 ===  Building package for isc-dhcp42-server-4.2.5
 tar: etc/rc.d/isc-dhcpd: Cannot stat: No such file or directory
 tar: Error exit delayed from previous errors.
 pkg_create: make_dist: tar command failed with code 256
 *** [do-package] Error code 1

 # ls -l /staging/usr/local/etc/rc.d/isc-dhcpd /usr/local/etc/rc.d/isc-dhcpd
 ls: /usr/local/etc/rc.d/isc-dhcpd: No such file or directory
 -r-xr-xr-x  1 root  wheel  11816 Oct 12 19:39
 /staging/usr/local/etc/rc.d/isc-dhcpd

 I can't see what I need to workaround to avoid this issue?
 The problem is that you defined STAGEDIR, but these ports are marked NO_STAGE

 I tried to add a .undef STAGEDIR to bsd.port.mk:

 --- /usr/ports/Mk.bsd.port.mk
 +++ /usr/ports/Mk.bsd.port.mk
 @@ -1932,6 +1932,8 @@
  .if !defined(NO_STAGE)
  .include ${PORTSDIR}/Mk/bsd.stage.mk
 +.else
 +.undef STAGEDIR
  .endif

 The above works, if you 

Re: How to disable staging support in ports tree universally?

[Dewayne]

My sincere apologies, I was writing a draft and did not intend to send. 
Its appears that my relocation from 13 years of outlook experience  to
thunderbird is not going well; as some timer or finger-sequence
triggered a unintended send.
Dewayne.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

[QAT] r330203: 4x leftovers

[Ports-QAT]

- Add new port: graphics/rubygem-fastimage

  FastImage finds the size or type of an image given its uri by
  fetching as little as needed.

  WWW: https://github.com/sdsykes/fastimage
-

  Build ID:  20131013035800-19588
  Job owner: t...@freebsd.org
  Buildtime: 4 minutes
  Enddate:   Sun, 13 Oct 2013 04:02:02 GMT

  Revision:  r330203
  Repository:
https://svnweb.freebsd.org/ports?view=revisionrevision=330203

-

Port:graphics/rubygem-fastimage 1.5.2

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~t...@freebsd.org/20131013035800-19588-206524/rubygem-fastimage-1.5.2.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~t...@freebsd.org/20131013035800-19588-206525/rubygem-fastimage-1.5.2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~t...@freebsd.org/20131013035800-19588-206526/rubygem-fastimage-1.5.2.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~t...@freebsd.org/20131013035800-19588-206527/rubygem-fastimage-1.5.2.log


--
Buildarchive URL: https://qat.redports.org/buildarchive/20131013035800-19588
redports https://qat.redports.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org