Problems with portupgrade && xscreensaver-gnome

Marcin Wisnicki mwisnicki+freebsd at gmail.com
Wed Jul 30 22:17:12 UTC 2008


On Wed, 30 Jul 2008 17:45:10 -0400, Bill Moran wrote:

> In response to Marcin Wisnicki <mwisnicki+freebsd at gmail.com>:
> 
>> On Wed, 30 Jul 2008 08:51:23 -0400, Bill Moran wrote:
>> 
>> > cvsupped my ports tree just this morning. #uname -a FreeBSD
>> > vanquish.ws.pitbpa0.priv.collaborativefusion.com 7.0-RELEASE FreeBSD
>> > 7.0-RELEASE #4: Wed Jun 25 09:16:13 EDT 2008
>> > root at vanquish.ws.pitbpa0.priv.collaborativefusion.com:/usr/obj/usr/
src/
>> sys/VANQUISH
>> >  i386 # pkg_info | grep portupgrade
>> > portupgrade-2.4.6,2 FreeBSD ports/packages administration and
>> > management tool s # portupgrade -a
>> > [...]
>> > ** Makefile possibly broken: x11/xscreensaver-gnome:
>> > 	"Makefile", line 106: warning: Option KEYRING needs PAM, but PAM
>> is
>> > 	disabled. xscreensaver-gnome-5.06_1
>> 
>> You need to either enable PAM (recommended) or disable KEYRING by
>> doing:
>>  cd /usr/ports/x11/xscreensaver-gnome/; make config
> 
> Are you saying that I can't portupgrade ANY ports on my system until
> such time as I make this strange decision?

Why do you think it is a strange decision?
You have set non-default options that don't make sense and the port is 
warning you about that. Fixing it is quick, easy and painless.



More information about the freebsd-ports mailing list