Re: failure building Thunderbird: libnss3.so: No such file or directory

[Perry Hutchison]

Per olof Ljungmark  wrote:

> '/usr/ports/mail/thunderbird/work/thunderbird-45.3.0'
> ===> Compilation failed unexpectedly.
> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
  ^^^
> the maintainer.

Did you try that?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: unexpected package dependency

[Perry Hutchison]

Andriy Gapon <a...@freebsd.org> wrote:
> On 17/02/2016 11:28, Perry Hutchison wrote:
> > I had not expected to find gcc listed (in packagesite.yaml) as a
> > dependency of the sysutils/cpuburn package.  I can understand a
> > _port_ needing gcc (at build time), but does the cpuburn _package_
> > actually require gcc at _runtime_?
>
> I don't believe so.  AFAIR, it builds static binaries.

So would the inclusion of gcc in the "deps" for sysutils/cpuburn (in
packagesite.yaml) be caused by a problem with the way the dependencies
are specified in the port, or with the way they are handled by the
package-generation mechanism?  (I'm trying to figure out which to file
a PR against -- and I'm not all that familiar with pkgng details.)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

unexpected package dependency

[Perry Hutchison]

I had not expected to find gcc listed (in packagesite.yaml) as a
dependency of the sysutils/cpuburn package.  I can understand a
_port_ needing gcc (at build time), but does the cpuburn _package_
actually require gcc at _runtime_?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [package - head-i386-default][sysutils/diskcheckd] Failed for diskcheckd-20110729 in build

[Perry Hutchison]

pkg-fall...@freebsd.org wrote:
 You are receiving this mail as a port that you maintain
 is failing to build on the FreeBSD package build server.
 Please investigate the failure and submit a PR to fix
 build.

PR#197841 was submitted about a week ago.  Is there a way to get
off the nag list temporarily while waiting for it to be committed?
___
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 use mkntfs, I get not a block device

[Perry Hutchison]

O'Connor, Daniel dar...@dons.net.au wrote:
  On 3 Feb 2015, at 22:59, Thomas Mueller mueller6...@bellsouth.net wrote:
  I can't format a partition for NTFS with fusefs-ntfs port, using mkntfs.
...
  root@amelia:~ # mkntfs /dev/gpt/SeaExp1-03
  /dev/gpt/SeaExp1-03 is not a block device.
  Refusing to make a filesystem here!

 The port should really patch this out (IMO) - it doesn't make
 sense on FreeBSD since it doesn't _have_ block devices.

Better yet, patch the port to accept either a block or a char
device and push the fix upstream.  Even Unixen that have both
types normally allow FS to be made on either the block or the
char device.
___
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

misconfigured package-build server causing bogus pkg-fallout messages

[Perry Hutchison]

Immediately after Poudriere reports the OSVERSIONs:

!!! Jail is newer than host. (Jail: 1100052, Host: 1100050) !!!
!!! This is not supported. !!!
!!! Host kernel must be same or newer than jail. !!!
!!! Expect build failures. !!!

Given that, I suppose the rest of the error report is bogus, right?

Shouldn't stuff like this get filtered out, so that only genuine
failures get sent to the maintainers?

Message below, with emails altered to reduce spam.



From: pkg-fallout [at] freebsd.org
Date: Fri, 16 Jan 2015 06:45:55 GMT
To: perryh [at] pluto.rain.com
Subject: [package - head-amd64-default][sysutils/diskcheckd] Failed for 
diskcheckd-20110729 in build
Cc: pkg-fallout [at] freebsd.org

You are receiving this mail as a port that you maintain
is failing to build on the FreeBSD package build server.
Please investigate the failure and submit a PR to fix
build.

Maintainer: perryh [at] pluto.rain.com
Last committer: vanilla [at] FreeBSD.org
Ident:  $FreeBSD: head/sysutils/diskcheckd/Makefile 359383 2014-06-26 
16:00:00Z vanilla $
Log URL:
http://beefy2.isc.freebsd.org/data/head-amd64-default/2015-01-15_15h59m45s/logs/diskcheckd-20110729.log
Build URL:  
http://beefy2.isc.freebsd.org/build.html?mastername=head-amd64-defaultbuild=2015-01-15_15h59m45s
Log:

 Building sysutils/diskcheckd
build started at Fri Jan 16 06:45:52 UTC 2015
port directory: /usr/ports/sysutils/diskcheckd
building for: FreeBSD head-amd64-default-job-23 11.0-CURRENT FreeBSD 
11.0-CURRENT r276772 amd64
maintained by: perryh [at] pluto.rain.com
Makefile ident:  $FreeBSD: head/sysutils/diskcheckd/Makefile 359383 
2014-06-26 16:00:00Z vanilla $
Poudriere version: 3.1.1
Host OSVERSION: 1100050
Jail OSVERSION: 1100052




!!! Jail is newer than host. (Jail: 1100052, Host: 1100050) !!!
!!! This is not supported. !!!
!!! Host kernel must be same or newer than jail. !!!
!!! Expect build failures. !!!



---Begin Environment---
OSVERSION=1100052
UNAME_v=FreeBSD 11.0-CURRENT r276772
UNAME_r=11.0-CURRENT
BLOCKSIZE=K
MAIL=/var/mail/root
STATUS=1
SAVED_TERM=
MASTERMNT=/usr/local/poudriere/data/.m/head-amd64-default/ref
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin
POUDRIERE_BUILD_TYPE=bulk
PKGNAME=diskcheckd-20110729
OLDPWD=/
PWD=/usr/local/poudriere/data/.m/head-amd64-default/ref/.p/pool
MASTERNAME=head-amd64-default
USER=root
HOME=/root
POUDRIERE_VERSION=3.1.1
LOCALBASE=/usr/local
PACKAGE_BUILDING=yes
---End Environment---

---Begin OPTIONS List---
---End OPTIONS List---

--CONFIGURE_ARGS--

--End CONFIGURE_ARGS--

--CONFIGURE_ENV--
XDG_DATA_HOME=/wrkdirs/usr/ports/sysutils/diskcheckd/work  
XDG_CONFIG_HOME=/wrkdirs/usr/ports/sysutils/diskcheckd/work  
HOME=/wrkdirs/usr/ports/sysutils/diskcheckd/work TMPDIR=/tmp SHELL=/bin/sh 
CONFIG_SHELL=/bin/sh
--End CONFIGURE_ENV--

--MAKE_ENV--
XDG_DATA_HOME=/wrkdirs/usr/ports/sysutils/diskcheckd/work  
XDG_CONFIG_HOME=/wrkdirs/usr/ports/sysutils/diskcheckd/work  
HOME=/wrkdirs/usr/ports/sysutils/diskcheckd/work TMPDIR=/tmp NO_PIE=yes 
SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local  LOCALBASE=/usr/local  
LIBDIR=/usr/lib  CC=cc CFLAGS=-O2 -pipe  
-D_PATH_CONF='\/usr/local/etc/diskcheckd.conf\' -fstack-protector 
-fno-strict-aliasing  CPP=cpp CPPFLAGS=  LDFLAGS= -fstack-protector 
LIBS=  CXX=c++ CXXFLAGS=-O2 -pipe 
-D_PATH_CONF='\/usr/local/etc/diskcheckd.conf\' -fstack-protector 
-fno-strict-aliasing   MANPREFIX=/usr/local BSD_INSTALL_PROGRAM=install  -s 
-o root -g wheel -m 555  BSD_INSTALL_LIB=install  -s -o root -g wheel -m 444 
 BSD_INSTALL_SCRIPT=install  -o root -g wheel -m 555  
BSD_INSTALL_DATA=install  -o root -g wheel -m 0644  BSD_INSTALL_MAN=install  
-o root -g wheel -m 444
--End MAKE_ENV--

--PLIST_SUB--
OSREL=11.0
PREFIX=%D
LOCALBASE=/usr/local
RESETPREFIX=/usr/local
PORTDOCS=
PORTEXAMPLES=
LIB32DIR=lib
DOCSDIR=share/doc/diskcheckd
EXAMPLESDIR=share/examples/diskcheckd
DATADIR=share/diskcheckd
WWWDIR=www/diskcheckd
ETCDIR=etc/diskcheckd
--End PLIST_SUB--

--SUB_LIST--
PREFIX=/usr/local
LOCALBASE=/usr/local
DATADIR=/usr/local/share/diskcheckd
DOCSDIR=/usr/local/share/doc/diskcheckd
EXAMPLESDIR=/usr/local/share/examples/diskcheckd
WWWDIR=/usr/local/www/diskcheckd
ETCDIR=/usr/local/etc/diskcheckd
--End SUB_LIST--

---Begin make.conf---
USE_PACKAGE_DEPENDS=yes
BATCH=yes
WRKDIRPREFIX=/wrkdirs
USE_PACKAGE_DEPENDS=yes
BATCH=yes
WRKDIRPREFIX=/wrkdirs
PORTSDIR=/usr/ports
PACKAGES=/packages
DISTDIR=/distfiles
 /usr/local/etc/poudriere.d/make.conf 
WITH_PKGNG=yes
#WITH_PKGNG=devel
# clean-restricted ran via poudriere.conf NO_RESTRICTED
#NO_RESTRICTED=yes
DISABLE_MAKE_JOBS=poudriere
---End make.conf---
===phase: check-sanity   
===  License BSD2CLAUSE accepted by the user
===
===phase: pkg-depends

Re: value of maintaining emacs-mode packages in ports

[Perry Hutchison]

Christopher J. Ruwe c...@cruwe.de wrote:

 ... Emacs, the very good operating system
 missing only a decent editor ...

Perhaps someone should port vi to it?

[dons flame-proof suit]
___
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

staging mail/heirloom-mailx [for review]

[Perry Hutchison]

I noticed that mail/heirloom-mailx is no longer maintained, and has
not been staged.

It looks straightforward.  Did I miss anything?

--- Makefile2014-05-31 21:58:23.0 -0700
+++ Makefile-staged 2014-06-03 00:34:03.0 -0700
@@ -8,7 +8,7 @@
 MASTER_SITES=  SF/heirloom/heirloom-${PORTNAME}/${PORTVERSION}
 PKGNAMEPREFIX= heirloom-
 
-MAINTAINER=po...@freebsd.org
+MAINTAINER=per...@pluto.rain.com
 COMMENT=   BSD mail utility with MIME, IMAP, POP3, SMTP, and S/MIME 
extensions
 
 OPTIONS_DEFINE=IPV6 DOCS
@@ -25,10 +25,10 @@
CPPFLAGS=${CPPFLAGS} \
LDFLAGS=${LDFLAGS}
 
-MAN1=  ${PORTNAME}.1
 PORTDOCS=  AUTHORS COPYING ChangeLog README TODO
 
 PLIST_FILES=   bin/${PORTNAME} \
+   man/man1/${PORTNAME}.1 \
@unexec if cmp -s %D/etc/nail.rc %D/etc/nail.rc.default; then 
${RM} -f %D/etc/nail.rc; fi  \
etc/nail.rc.default \
@exec [ -f %B/nail.rc ] || ${CP} %B/%f %B/nail.rc
@@ -36,7 +36,6 @@
 CPPFLAGS+= -I${LOCALBASE}/include
 LDFLAGS+=  -L${LOCALBASE}/lib
 
-NO_STAGE=  yes
 .include bsd.port.options.mk
 
 .if ${PORT_OPTIONS:MIPV6}
@@ -44,16 +43,13 @@
 .endif
 
 do-install:
-   ${INSTALL_PROGRAM} ${WRKSRC}/${PORTNAME} ${PREFIX}/bin
-   ${INSTALL_MAN} ${WRKSRC}/${MAN1} ${MAN1PREFIX}/man/man1
-   ${INSTALL_DATA} ${WRKSRC}/nail.rc ${PREFIX}/etc/nail.rc.default
-.if !exists(${PREFIX}/etc/nail.rc)
-   ${INSTALL_DATA} ${WRKSRC}/nail.rc ${PREFIX}/etc
-.endif
+   ${INSTALL_PROGRAM} ${WRKSRC}/${PORTNAME} ${STAGEDIR}${PREFIX}/bin
+   ${INSTALL_MAN} ${WRKSRC}/${PORTNAME}.1 ${STAGEDIR}${MAN1PREFIX}/man/man1
+   ${INSTALL_DATA} ${WRKSRC}/nail.rc 
${STAGEDIR}${PREFIX}/etc/nail.rc.default
 .if ${PORT_OPTIONS:MDOCS}
-   @${MKDIR} ${DOCSDIR}
+   @${MKDIR} ${STAGEDIR}${DOCSDIR}
 .for i in ${PORTDOCS}
-   ${INSTALL_DATA} ${WRKSRC}/${i} ${DOCSDIR}
+   ${INSTALL_DATA} ${WRKSRC}/${i} ${STAGEDIR}${DOCSDIR}
 .endfor
 .endif
 
___
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: Is staging a port really this simple?

[Perry Hutchison]

John Marino freebsd.cont...@marino.st wrote:
 You didn't miss much -- except adding the man page to the
 pkg-plist and removing the MAN* definitions from the makefile.

...

 On 5/25/2014 09:09, Zsolt Udvari wrote:
  Your condition is unneeded.
  You don't need check the existence of
  ${STAGEDIR}${PREFIX}/etc/distcheckd.conf because you'll copy it, the
  ${STAGEDIR} are empty

 no, the @sample keyword in pkg-plist does that (replacing other lines
 there).  pkg doesn't do this by itself, it needs to be told.

So, like this? (diffs against the originals, not the previous iteration)
[and I don't follow how, or if, @sample should be used in diskcheckd
since it delivers the sample named as such, and also installs it as
the live config file if the live config file does not already exist]

--- misc/gtkfind/Makefile
+++ misc/gtkfind/Makefile-staged
@@ -18,15 +18,13 @@
 USE_GNOME= gtk12
 GNU_CONFIGURE= yes
 
-MAN1=  gtkfind.1
-PLIST_FILES=   bin/gtkfind
+PLIST_FILES=   bin/gtkfind man/man1/gtkfind.1
 
-NO_STAGE=  yes
 post-patch:
${REINPLACE_CMD} -e s,-O2,${CFLAGS}, ${WRKSRC}/configure 
${WRKSRC}/Makefile.in
 
 do-install:
-   ${INSTALL_PROGRAM} ${WRKSRC}/gtkfind ${PREFIX}/bin
-   ${INSTALL_MAN} ${WRKSRC}/gtkfind.1 ${MANPREFIX}/man/man1
+   ${INSTALL_PROGRAM} ${WRKSRC}/gtkfind ${STAGEDIR}${PREFIX}/bin
+   ${INSTALL_MAN} ${WRKSRC}/gtkfind.1 ${STAGEDIR}${MANPREFIX}/man/man1
 
 .include bsd.port.mk
--- sysutils/diskcheckd/Makefile
+++ sysutils/diskcheckd/Makefile-staged
@@ -11,15 +11,13 @@
 MAINTAINER=per...@pluto.rain.com
 COMMENT=   Daemon to check for disk read errors
 
-MAN8=  diskcheckd.8
 MLINKS=diskcheckd.8 diskcheckd.conf.5
 
 USE_RC_SUBR=   diskcheckd
 CFLAGS+=   -D_PATH_CONF='\${PREFIX}/etc/diskcheckd.conf\'
 MAKEFILE=  /usr/share/mk/bsd.prog.mk
-MAKE_ARGS= PROG=diskcheckd MAN8=${MAN8}
+MAKE_ARGS= PROG=diskcheckd MAN8=diskcheckd.8
 
-NO_STAGE=  yes
 do-extract:
@${MKDIR} ${WRKSRC}
 .for f in diskcheckd.c diskcheckd.8
@@ -30,13 +28,13 @@
@${REINPLACE_CMD} -e 
's|/usr/local/etc/diskcheckd.conf|${PREFIX}/etc/diskcheckd.conf|g' 
${WRKSRC}/diskcheckd.8
 
 do-install:
-   ${INSTALL_PROGRAM} ${WRKSRC}/diskcheckd ${PREFIX}/sbin
-   ${INSTALL_DATA} ${FILESDIR}/diskcheckd.conf 
${PREFIX}/etc/diskcheckd.conf.sample
-   ${INSTALL_MAN} ${WRKSRC}/diskcheckd.8 ${MAN8PREFIX}/man/man8
+   ${INSTALL_PROGRAM} ${WRKSRC}/diskcheckd ${STAGEDIR}${PREFIX}/sbin
+   ${INSTALL_DATA} ${FILESDIR}/diskcheckd.conf \
+   ${STAGEDIR}${PREFIX}/etc/diskcheckd.conf.sample
+   ${INSTALL_MAN} ${WRKSRC}/diskcheckd.8 ${STAGEDIR}${MAN8PREFIX}/man/man8
 
 post-install:
-   @[ -f ${PREFIX}/etc/diskcheckd.conf ] \
-   || ${CP} -p ${PREFIX}/etc/diskcheckd.conf.sample \
-   ${PREFIX}/etc/diskcheckd.conf
+   @${CP} -p ${STAGEDIR}${PREFIX}/etc/diskcheckd.conf.sample \
+   ${STAGEDIR}${PREFIX}/etc/diskcheckd.conf
 
 .include bsd.port.mk
--- sysutils/diskcheckd/pkg-plist
+++ sysutils/diskcheckd/pkg-plist-staged
@@ -1,4 +1,6 @@
 sbin/diskcheckd
+man/man8/diskcheckd.8
+man/man5/diskcheckd.conf.5
 @unexec if cmp -s %D/etc/diskcheckd.conf.sample %D/etc/diskcheckd.conf; then 
rm -f %D/etc/diskcheckd.conf; fi
 etc/diskcheckd.conf.sample
 @exec if [ ! -f %D/etc/diskcheckd.conf ]; then cp %D/%F %B/diskcheckd.conf; fi
___
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

Is staging a port really this simple?

[Perry Hutchison]

Some months ago, Baptiste Daroussin b...@freebsd.org wrote:

 ... if you need any help staging your ports I can provide reviews.

I have a couple of ports that need staging support added, and I've
finally managed to find time to look into it.  Having read such
documentation as I could easily find using Google, and looked at
the ports, I am feeling as if I must have overlooked something
-- because the only changes that seem to be needed are to insert
${STAGEDIR} into a few lines in the Makefiles.

Granted these are not complex ports, but if it really is this easy
I have to wonder what all the uproar has been about :)

What-all have I missed?

--- misc/gtkfind/Makefile
+++ misc/gtkfind/Makefile-staged
@@ -26,7 +26,7 @@
${REINPLACE_CMD} -e s,-O2,${CFLAGS}, ${WRKSRC}/configure 
${WRKSRC}/Makefile.in
 
 do-install:
-   ${INSTALL_PROGRAM} ${WRKSRC}/gtkfind ${PREFIX}/bin
-   ${INSTALL_MAN} ${WRKSRC}/gtkfind.1 ${MANPREFIX}/man/man1
+   ${INSTALL_PROGRAM} ${WRKSRC}/gtkfind ${STAGEDIR}${PREFIX}/bin
+   ${INSTALL_MAN} ${WRKSRC}/gtkfind.1 ${STAGEDIR}${MANPREFIX}/man/man1
 
 .include bsd.port.mk
--- sysutils/diskcheckd/Makefile
+++ sysutils/diskcheckd/Makefile-staged
@@ -19,7 +19,6 @@
 MAKEFILE=  /usr/share/mk/bsd.prog.mk
 MAKE_ARGS= PROG=diskcheckd MAN8=${MAN8}
 
-NO_STAGE=  yes
 do-extract:
@${MKDIR} ${WRKSRC}
 .for f in diskcheckd.c diskcheckd.8
@@ -30,13 +29,14 @@
@${REINPLACE_CMD} -e 
's|/usr/local/etc/diskcheckd.conf|${PREFIX}/etc/diskcheckd.conf|g' 
${WRKSRC}/diskcheckd.8
 
 do-install:
-   ${INSTALL_PROGRAM} ${WRKSRC}/diskcheckd ${PREFIX}/sbin
-   ${INSTALL_DATA} ${FILESDIR}/diskcheckd.conf 
${PREFIX}/etc/diskcheckd.conf.sample
-   ${INSTALL_MAN} ${WRKSRC}/diskcheckd.8 ${MAN8PREFIX}/man/man8
+   ${INSTALL_PROGRAM} ${WRKSRC}/diskcheckd ${STAGEDIR}${PREFIX}/sbin
+   ${INSTALL_DATA} ${FILESDIR}/diskcheckd.conf \
+   ${STAGEDIR}${PREFIX}/etc/diskcheckd.conf.sample
+   ${INSTALL_MAN} ${WRKSRC}/diskcheckd.8 ${STAGEDIR}${MAN8PREFIX}/man/man8
 
 post-install:
-   @[ -f ${PREFIX}/etc/diskcheckd.conf ] \
-   || ${CP} -p ${PREFIX}/etc/diskcheckd.conf.sample \
-   ${PREFIX}/etc/diskcheckd.conf
+   @[ -f ${STAGEDIR}${PREFIX}/etc/diskcheckd.conf ] \
+   || ${CP} -p ${STAGEDIR}${PREFIX}/etc/diskcheckd.conf.sample \
+   ${STAGEDIR}${PREFIX}/etc/diskcheckd.conf
 
 .include bsd.port.mk
___
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

opvp support in ghostscript

[Perry Hutchison]

What do I need to do, to get ghostscript's opvp support to work?

GS works fine displaying to the screen, but when I specify
-sDEVICE=opvp I get

   Unable to open the initial device, quitting.

If I also specify -dINITDEBUG=1 to turn on debug output during
gs_init.ps, I get a lot of messages showing progress through
the initialization process -- none of which seem to have anything
to do with device choice, nor to be much different from what
INITDEBUG produces when displaying to the screen -- until

  END FONTS 219 2605656 1227805 1417680 125870 true 1166 4 0
  Unrecoverable error: unknownerror in setdevice
  Operand stack:
  --nostringval--

which is not a whole lot more informative than the original message.
(When displaying to the screen, which works, the next line after
END FONTS ... is END DEVICE ...)

Is there any way to turn on debug or tracing, or otherwise get more
detail, re what is going on in setdevice and exactly what failed?

This is with the 8.3-RELEASE package of Ghostscript 9.05.
___
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

opvp support seems broken in ghostscript port

[Perry Hutchison]

Has anyone been able to use the opvp support in ghostscript?

It works fine displaying to the screen, but when I specify
-sDEVICE=opvp I get

   Unable to open the initial device, quitting.

If I also specify -dINITDEBUG=1 (which turns on debug output in the
initialization file, gs_init.ps) I get a lot of messages showing
progress through the initialization process -- none of which seem
to have anything to do with device choice, nor to be much different
from what INITDEBUG produces when displaying to the screen -- until

  END FONTS 219 2605656 1227805 1417680 125870 true 1166 4 0
  Unrecoverable error: unknownerror in setdevice
  Operand stack:
  --nostringval--

which is not a whole lot more informative than the original message.
(When displaying to the screen, the next line after END FONTS ...
is END DEVICE ...)

Is there any way to turn on debug or tracing, or otherwise get more
detail, re what is going on in setdevice and exactly what failed?

So far I haven't found anything particularly helpful using Google.
___
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

Where are the package links?

[Perry Hutchison]

In the last paragraph on http://www.freebsd.org/ports/index.html

 ... For most ports, a precompiled package also exists ...
 each port contains a link to its corresponding package ...

I must be blind, because I haven't been able to find those links
on any of several ports' pages.  Where should I be looking?
___
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: setting the password of a automatically created account

[Perry Hutchison]

Aryeh Friedman aryeh.fried...@gmail.com wrote:

 1. How do I add the user to wheel (has it's own group but needs
to be in wheel for reason number #2)?
 2. How do I modify (in the safest possible way) an other port's
installed config file(s) (namely I need to in the case of this
port modify /usr/local/etc/sudoers to allow the no password
option for wheel members)?

Others may disagree, but I would be very hesitant to make this a
requirement for the port.  Whether all wheel-group members (not
just this port) should have no-password access to sudo is very
much a policy decision, and a port -- like the rest of the system
-- should provide mechanism rather than dictating policy.

What are you trying to accomplish?  Could you, for example, provide
no-password sudo privilege to this port's unique user or group,
instead of changing a global policy?

As far as how to go about modifying sudoers, perhaps the sudo port
docs have some suggestions?

 Since the account's shell that is created is a custom shell for
 the port there is no security wholes we know about.. even so what
 kind of (if any) security warnings should we put on the port?

For it to require no-password sudo privilege is a huge red flag.
If that's truly necessary, it should be noted very prominently.
___
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: setting the password of a automatically created account

[Perry Hutchison]

Aryeh Friedman aryeh.fried...@mail.com wrote:

 I have a port that needs to create a a user of a given name and a
 given default password... I found in the porters guide how to make
 the account but not set the password

This is one of the canonical uses of lang/expect.
___
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: non-destructive ports/packages update

[Perry Hutchison]

Chris Rees cr...@freebsd.org wrote:

 On 23 April 2013 20:41, Peter Jeremy pe...@rulingia.com wrote:
  On 2013-Apr-20 18:03:17 -0700, Perry Hutchison per...@pluto.rain.com 
  wrote:
 The question is, what (if anything) else -- besides /usr/ports,
 /usr/local, /var/db/ports, and /var/db/pkg -- needs to be checkpointed?
 
  If you're running any Linux compatibility packages: /compat/linux
  BOINC packages: /var/db/boinc
 
  Unless you've moved to pkgng,
  $ grep @cwd /var/db/pkg/*/+CONTENTS | grep -v /usr/local
  will give you an overview of what unusual locations have been
  installed to.

 Actually grep ^@cw*d, because @cd is an equivalent syntax that is
 sometimes used.

A further refinement:

  grep ^@cw*d . /var/db/pkg/*/+CONTENTS | egrep -v '/usr/local|:@cwd \.$'

The ^@cw*d . excludes ports (like graphviz) that have an @cwd
without an operand.  The :@cwd \.$ alternative excludes . as
the operand -- a construct which seems to be fairly common.
___
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: non-destructive ports/packages update

[Perry Hutchison]

Chris Rees utis...@gmail.com wrote:
 On 21 Apr 2013 02:13, Perry Hutchison per...@pluto.rain.com wrote:
  ...
  The question is, what (if anything) else -- besides /usr/ports,
  /usr/local, /var/db/ports, and /var/db/pkg -- needs to be checkpointed?

 Are you installing any drivers?  You may need to back up /boot too.

No drivers from ports here (nor any ports which overwrite base), but
good to note this for the archives :)
___
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: non-destructive ports/packages update

[Perry Hutchison]

Peter Pentchev r...@ringlet.net wrote:

 Some ports might store run state in /var/db/portname or a similarly
 named directory.  The thing is, the decision whether to save this and
 restore it or to keep it across runs actually depends on the port: for
 database management systems such as MySQL, PostgreSQL, etc, you'll
 probably want to keep the databases even if the ports themselves are
 reinstalled, rolled back, restored, whatever.  For some other systems,
 you might want to remove the current state information of the version
 that you are about to replace.

Good catch.  No DBMS on this system, so no problem there, but there
are two non-empty X11-related directories under /var/db:  dbus and
fontconfig.  (The machine does have some X client apps, but not the
X server.)
___
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

non-destructive ports/packages update

[Perry Hutchison]

I'm looking for a way to move everything connected with ports and
packages aside, so that I can start fresh but with the ability to
easily roll it back when things go badly (as they surely will).

I have in mind to something like this:

# cd /usr
# mkdir old
# mv ports local old
# mkdir ports local
# cd /var/db
# mkdir old
# mv ports pkg old
# mkdir ports pkg

Is there anything else that needs to be saved before fetching a
new ports tree and starting to build things (or install prebuilt
packages)?

This is on 8.1, although I suspect the answer does not depend on
the OS version.  And yes, there's plenty of space in /usr and /var.
___
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: non-destructive ports/packages update

[Perry Hutchison]

Xin Li delp...@delphij.net wrote:

 On 4/19/13 11:34 PM, Perry Hutchison wrote:
  I'm looking for a way to move everything connected with ports and 
  packages aside, so that I can start fresh but with the ability to 
  easily roll it back when things go badly (as they surely will).
  
  I have in mind to something like this:
  
  # cd /usr
  # mkdir old
  # mv ports local old
  # mkdir ports local
  # cd /var/db
  # mkdir old
  # mv ports pkg old
  # mkdir ports pkg
  
  Is there anything else that needs to be saved before fetching a
  new ports tree and starting to build things (or install prebuilt 
  packages)?

 If you use ZFS, it's possible to take snapshot, then install new
 ports, then if something blows up, you can rollback.

 With UFS, it's still possible to take snapshot but rollback is not
 atomic.

I'm aware of filesystem snapshots, but I only want to checkpoint the
ports and packages, not the whole filesystem -- a rollback needs to
be fast, easy, and obviously correct; preserve the failure logs; and
not undo changes that may have been made elsewhere in the meantime.
(BTW I don't use ZFS:  the machine doesn't have enough memory, and to
me ZFS -- especially on 8.x -- doesn't yet seem sufficiently proven.)

 If you use portmaster, it can save packages (I think portupgrade
 can do it too).  But this approach depends on the fact that the
 port is well written, and is not atomic in terms of package set.

And then a rollback requires re-installing the saved packages, which
is surely slower than moving a few directories and/or files around.

The question is, what (if anything) else -- besides /usr/ports,
/usr/local, /var/db/ports, and /var/db/pkg -- needs to be checkpointed?
___
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: Ports request

[Perry Hutchison]

Paul Pathiakis pathia...@yahoo.com wrote:

 The StEam platform from ValVe corp is a large step in gaming at
 this point ...  StEam is in the process of moving over to Linux.
 Please don't fall behind in the effort of bringing this platform
 to BSD.

Had you considered trying to run their Linux version on FreeBSD
under Linux emulation?  (Having no interest at all in gaming,
I'm personally not motivated.)
___
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