FreeBSD Port: samba-3.0.28a_2,1

2008-06-30 Thread Raffaele De Lorenzo

Hi,
i have some troubles with pam-winbind with this particular version 
ported. When i try to use the winbind pam authentication library i 
receive the error listed:


Jun 27 14:17:48 X sshd[84691]: in openpam_load_module(): no 
/usr/local/lib/pam_winbind.so found

Jun 27 14:17:48 X sshd[84691]: fatal: PAM: initialisation failed


I have another machine with an older version of samba (samba-3.0.28,1) 
and this work fine. At this time the workaround to solve the problem was 
to copy the "pam_winbind.so" library from the machine with the worked 
version of samba (samba-3.0.28,1) to the machine with the  samba version 
samba-3.0.28a_2,1. I have installed FreeBSD 7 STABLE and SAMBA was 
compiled from the official port.

Can you help me to solve this problem cleanly?

cheers

Raffaele
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD Port: samba-3.0.28a_2,1

2008-06-30 Thread Jeremy Chadwick
On Mon, Jun 30, 2008 at 10:09:39AM +0200, Raffaele De Lorenzo wrote:
> Hi,
> i have some troubles with pam-winbind with this particular version  
> ported. When i try to use the winbind pam authentication library i  
> receive the error listed:
>
> Jun 27 14:17:48 X sshd[84691]: in openpam_load_module(): no  
> /usr/local/lib/pam_winbind.so found
> Jun 27 14:17:48 X sshd[84691]: fatal: PAM: initialisation failed
>
> I have another machine with an older version of samba (samba-3.0.28,1)
> and this work fine. At this time the workaround to solve the problem
> was to copy the "pam_winbind.so" library from the machine with the
> worked version of samba (samba-3.0.28,1) to the machine with the
> samba version samba-3.0.28a_2,1. I have installed FreeBSD 7 STABLE and
> SAMBA was compiled from the official port.  Can you help me to solve
> this problem cleanly?

ports/net/samba3/Makefile shows the following:

  5 # $FreeBSD: ports/net/samba3/Makefile,v 1.171 2008/06/06 13:50:16 edwin Exp 
$

  8 PORTNAME=   samba
  9 PORTVERSION?=   3.0.28a
 10 PORTREVISION=   2
 11 PORTEPOCH?= 1

 43 SAMBA_LIB=  lib
 44 SAMBA_LIBDIR=   ${PREFIX}/${SAMBA_LIB}
 45 SAMBA_MODULEDIR=${SAMBA_LIBDIR}/samba

 49 CONFIGURE_ARGS+=--exec-prefix="${PREFIX}" \
 50 --localstatedir="${VARDIR}" \
 51 --with-configdir="${SAMBA_CONFDIR}" \
 52 --with-pammodulesdir="${SAMBA_LIBDIR}" \
 53 --with-libdir="${SAMBA_MODULEDIR}" \

438 # Winbind
439 .if !defined(WITHOUT_WINBIND)

446 ${INSTALL_PROGRAM} "${WRKSRC}/bin/pam_winbind.so" "${SAMBA_LIBDIR}"
447 @${ECHO_CMD} "${SAMBA_LIB}/pam_winbind.so" >> ${TMPPLIST};
448 .endif

The variables should expand to:

SAMBA_LIB=  lib
SAMBA_LIBDIR=   /usr/local/lib
SAMBA_MODULEDIR=/usr/local/lib/samba

So, based on the Makefile, the pam_winbind.so file should end up being
installed in /usr/local/lib.  I don't see anything wrong with this.

With regards to the machine running 3.0.28a_2,1:

1) Can you please provide the contents of /var/db/ports/samba3/options
2) Results of `find /usr/local -name "pam_winbind.so" -ls`, ***before***
you copied the file from another machine onto it.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| 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 "[EMAIL PROTECTED]"


Re: FreeBSD Port: samba-3.0.28a_2,1

2008-06-30 Thread Raffaele De Lorenzo

Hi,
here the compiled options for SAMBA:

# This file is auto-generated by 'make config'.
# No user-servicable parts inside!
# Options for samba-3.0.28a_2,1
_OPTIONS_READ=samba-3.0.28a_2,1
WITH_LDAP=true
WITH_ADS=true
WITH_CUPS=true
WITH_WINBIND=true
WITHOUT_ACL_SUPPORT=true
WITHOUT_FAM_SUPPORT=true
WITHOUT_SYSLOG=true
WITHOUT_QUOTAS=true
WITH_UTMP=true
WITH_MSDFS=true
WITH_PAM_SMBPASS=true
WITHOUT_CLUSTER=true
WITHOUT_DNSUPDATE=true
WITHOUT_EXP_MODULES=true
WITH_POPT=true
WITH_MAX_DEBUG=true
WITHOUT_SMBTORTURE=true

And this is the trouble "pam_winbind.so". Before the copy from the 
worked machine i renamed it in "pam_winbind.so.old" :


find /usr/local -name "pam_winbind.so*" -ls
924299 96 -rwxr-xr-x 1 root wheel 48836 Jun 27 14:59 
/usr/local/lib/pam_winbind.so
57317 1152 -rwxr-xr-x 1 root wheel 571176 Jun 27 11:04 
/usr/local/lib/pam_winbind.so.old


An older version of PAM/WINBIND could have the same troubles 
(*3.0.23c_2,1)* but i don't know if this is the same issue... see


http://www.freshports.org/net/samba3/


Raffaele






Jeremy Chadwick wrote:

On Mon, Jun 30, 2008 at 10:09:39AM +0200, Raffaele De Lorenzo wrote:
  

Hi,
i have some troubles with pam-winbind with this particular version  
ported. When i try to use the winbind pam authentication library i  
receive the error listed:


Jun 27 14:17:48 X sshd[84691]: in openpam_load_module(): no  
/usr/local/lib/pam_winbind.so found

Jun 27 14:17:48 X sshd[84691]: fatal: PAM: initialisation failed

I have another machine with an older version of samba (samba-3.0.28,1)
and this work fine. At this time the workaround to solve the problem
was to copy the "pam_winbind.so" library from the machine with the
worked version of samba (samba-3.0.28,1) to the machine with the
samba version samba-3.0.28a_2,1. I have installed FreeBSD 7 STABLE and
SAMBA was compiled from the official port.  Can you help me to solve
this problem cleanly?



ports/net/samba3/Makefile shows the following:

  5 # $FreeBSD: ports/net/samba3/Makefile,v 1.171 2008/06/06 13:50:16 edwin Exp 
$

  8 PORTNAME=   samba
  9 PORTVERSION?=   3.0.28a
 10 PORTREVISION=   2
 11 PORTEPOCH?= 1

 43 SAMBA_LIB=  lib
 44 SAMBA_LIBDIR=   ${PREFIX}/${SAMBA_LIB}
 45 SAMBA_MODULEDIR=${SAMBA_LIBDIR}/samba

 49 CONFIGURE_ARGS+=--exec-prefix="${PREFIX}" \
 50 --localstatedir="${VARDIR}" \
 51 --with-configdir="${SAMBA_CONFDIR}" \
 52 --with-pammodulesdir="${SAMBA_LIBDIR}" \
 53 --with-libdir="${SAMBA_MODULEDIR}" \

438 # Winbind
439 .if !defined(WITHOUT_WINBIND)

446 ${INSTALL_PROGRAM} "${WRKSRC}/bin/pam_winbind.so" "${SAMBA_LIBDIR}"
447 @${ECHO_CMD} "${SAMBA_LIB}/pam_winbind.so" >> ${TMPPLIST};
448 .endif

The variables should expand to:

SAMBA_LIB=  lib
SAMBA_LIBDIR=   /usr/local/lib
SAMBA_MODULEDIR=/usr/local/lib/samba

So, based on the Makefile, the pam_winbind.so file should end up being
installed in /usr/local/lib.  I don't see anything wrong with this.

With regards to the machine running 3.0.28a_2,1:

1) Can you please provide the contents of /var/db/ports/samba3/options
2) Results of `find /usr/local -name "pam_winbind.so" -ls`, ***before***
you copied the file from another machine onto it.

  


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Current unassigned ports problem reports

2008-06-30 Thread FreeBSD bugmaster
Current FreeBSD problem reports

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including\nexperimental 
development code and obsolete releases.\n
Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.

a - analyzed
The problem is understood and a solution is being sought.

f - feedback
Further work requires additional information from the
 originator or the community - possibly confirmation of
 the effectiveness of a proposed solution.

p - patched
A patch has been committed, but some issues (MFC and / or
 confirmation from originator) are still open.

r - repocopy
The resolution of the problem report is dependent on
 a repocopy operation within the CVS repository which
 is awaiting completion.

s - suspended
The problem is not being worked on, due to lack of information
 or resources.  This is a prime candidate
 for somebody who is looking for a project to do.
 If the problem cannot be solved at all,
 it will be closed, rather than suspended.

c - closed
A problem report is closed when any changes have been integrated,
 documented, and tested -- or when fixing the problem is abandoned.

Critical problems

S Tracker  Resp.  Description

f ports/124901[patch] sysutils/fusefs-kmod dataloss on write shortly

1 problem total.

Serious problems

S Tracker  Resp.  Description

f ports/112921x11-wm/Beryl not loading focus and keybinding settings
s ports/113144print/ghostscript-gnu dumps core with several output d
f ports/116385net/vnc using vnc.so crashes Xorg 7.3 when remote comp
f ports/116586net/isc-dhcp3-server does not work when compiled with 
o ports/117128security/ipsec-tools racoon.sh fails with /var on mfs
f ports/118877audio/streamripper does not detect song title from str
f ports/122276Compiled audio/musicpd segfaults on FreeBSD 7.0
o ports/122381net-mgmt/collectd in FreeBSD 7.0 i386 and sparc64 segf
f ports/122416deskutils/kmatrix3d and deskutils/ksmoothdock don't in
o ports/122676multimedia/mplayer: can't access dvd with any applicat
o ports/122907[patch] sysutils/fusefs-kmod dataloss on write shortly
f ports/122973textproc/xerces-c2: installed files do not have o+r bi
f ports/123655mail/postfix - I can't build port postfix-2.5.1 with p
a ports/124154mail/milter-bogom cores out intermittently
f ports/124401security/sshguard dumps core
o ports/124441sysutils/wmmemfree doesn't report swap changes
o ports/124864print/ghostscript-gpl fails to install if ESC/Page dri
f ports/125111[PATCH] graphics/gdal: cyclic dependency and wrong opt

18 problems total.

Non-critical problems

S Tracker  Resp.  Description

s ports/85513 Intel C++ compiler not 100% binary compatible with sys
o ports/108795ports/icc: Proposed update to icc port for intel compi
o ports/108856[mbone/sdr] make sdr usable again; patch appended
o ports/110144New port: math/Matlab7
o ports/110697New port: ports-mgmt/pkg_deps
o ports/112746[NEW PORT]: www/coldfusion: coldfusion7 Coldfusion 7.0
f ports/115304multimedia/gpac-mp4box cannot import files larger than
o ports/115336port multimedia/avifile on FreeBSD 7.0 not BROKEN with
o ports/116567[PATCH] net/vnc: patch x0vncserver to not give the sel
o ports/117521[new port] net/asterisk-res-bonjour Bonjour (Zeroconf)
o ports/117824CONFIGURE_LINE truncated to 2048 chars in [at least] m
f ports/118368New port: net/asterisk-agx AGX Extra Addons (including
o ports/119183[NEW PORT] net/freeradius-client: FreeRADIUS Client li
o ports/119556[PATCH] textproc/xerces-c2: Update to 2.8.0
f ports/119745www/linux-flashplugin7 - flashplayer does not work wit
o ports/120923www/squidguard does not work unless its UID/GID are mo
o ports/121126New port: science/caret Computerized Anatomical Recons
f ports/121149www/tomcat55 - www/tomcat* choaks on ip6
o ports/121194math/arpack - Patch to use ARPACK++ on modern compiler
o ports/121259New port: net/openamq OpenAMQ is a complete AMQP messa
f ports/121405Update graphics/gmt to newer version (4.2.1)
o ports/121834[patch] lang/lua: split AR into AR/ARFLAGS (for cross 
f ports/121836[PATCH] sysutils/ezjail: amd64 install problem
o ports/121

FreeBSD Port: clamav-0.93.1_2

2008-06-30 Thread Pieter Sybesma

Hi,

I'm getting this on compiling clamav:


cc -O -pipe -march=pentium4 -o .libs/clamscan output.o getopt.o cfgparser.o 
misc.o options.o clamscan.o others.o manager.o treewalk.o  -L/usr/local/lib 
../libclamav/.libs/libclamav.so 
/usr/ports/security/clamav/work/clamav-0.93.1/libclamunrar_iface/.libs/libclamunrar_iface.so
 
/usr/ports/security/clamav/work/clamav-0.93.1/libclamunrar/.libs/libclamunrar.so
 -lbz2 /usr/local/lib/libgmp.so -lz -lthr  -Wl,--rpath -Wl,/usr/local/lib
../libclamav/.libs/libclamav.so: undefined reference to `gethostbyname_r'
*** Error code 1

Stop in /usr/ports/security/clamav/work/clamav-0.93.1/clamscan.
*** Error code 1

Stop in /usr/ports/security/clamav/work/clamav-0.93.1.
*** Error code 1

Stop in /usr/ports/security/clamav/work/clamav-0.93.1.
*** Error code 1

Stop in /usr/ports/security/clamav.
*** Error code 1

Stop in /usr/ports/security/clamav.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.33714.0 
env UPGRADE_TOOL=portupgrade UPGRADE_PORT=clamav-0.93_1 UPGRADE_PORT_VER=0.93_1 
make
** Fix the problem and try again.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! security/clamav (clamav-0.93_1)   (linker error)


It seems it's a problem since you removed the following from the 
Makefile last in version 1.112 2008/06/09 16:13:25:



.if ${OSVERSION} < 601103
CONFIGURE_ARGS+=--disable-gethostbyname_r
.else 	 
CONFIGURE_ARGS+=--enable-gethostbyname_r
.endif 	 


I'm running the following version:


qmailin# uname -a
FreeBSD qmailin.gicom.nl 5.3-RELEASE-p37 FreeBSD 5.3-RELEASE-p37 #1: Mon Mar 12 
12:47:07 CET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL  i386


Greetings Pieter Sybesma

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD Port: clamav-0.93.1_2

2008-06-30 Thread Renato Botelho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Jun 30, 2008 at 01:35:59PM +0200, Pieter Sybesma wrote:
> Hi,
> 
> I'm getting this on compiling clamav:
> 
> > cc -O -pipe -march=pentium4 -o .libs/clamscan output.o getopt.o cfgparser.o 
> > misc.o options.o clamscan.o others.o manager.o treewalk.o  -L/usr/local/lib 
> > ../libclamav/.libs/libclamav.so 
> > /usr/ports/security/clamav/work/clamav-0.93.1/libclamunrar_iface/.libs/libclamunrar_iface.so
> >  
> > /usr/ports/security/clamav/work/clamav-0.93.1/libclamunrar/.libs/libclamunrar.so
> >  -lbz2 /usr/local/lib/libgmp.so -lz -lthr  -Wl,--rpath -Wl,/usr/local/lib
> > ../libclamav/.libs/libclamav.so: undefined reference to `gethostbyname_r'
> > *** Error code 1
> > 
> > Stop in /usr/ports/security/clamav/work/clamav-0.93.1/clamscan.
> > *** Error code 1
> > 
> > Stop in /usr/ports/security/clamav/work/clamav-0.93.1.
> > *** Error code 1
> > 
> > Stop in /usr/ports/security/clamav/work/clamav-0.93.1.
> > *** Error code 1
> > 
> > Stop in /usr/ports/security/clamav.
> > *** Error code 1
> > 
> > Stop in /usr/ports/security/clamav.
> > ** Command failed [exit code 1]: /usr/bin/script -qa 
> > /tmp/portupgrade.33714.0 env UPGRADE_TOOL=portupgrade 
> > UPGRADE_PORT=clamav-0.93_1 UPGRADE_PORT_VER=0.93_1 make
> > ** Fix the problem and try again.
> > ** Listing the failed packages (-:ignored / *:skipped / !:failed)
> > ! security/clamav (clamav-0.93_1)   (linker error)
> 
> It seems it's a problem since you removed the following from the 
> Makefile last in version 1.112 2008/06/09 16:13:25:
> 
> > .if ${OSVERSION} < 601103
> > CONFIGURE_ARGS+=--disable-gethostbyname_r
> > .else
> > CONFIGURE_ARGS+=--enable-gethostbyname_r
> > .endif   
> 
> I'm running the following version:
> 
> > qmailin# uname -a
> > FreeBSD qmailin.gicom.nl 5.3-RELEASE-p37 FreeBSD 5.3-RELEASE-p37 #1: Mon 
> > Mar 12 12:47:07 CET 2007 [EMAIL 
> > PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL  i386

Yes, the problem occours because i removed that lines. I removed them
because since Last May 31, any FreeBSD < 6.2 is no longer supported anymore.
This was announced one year before. Now, all "hackerisms" that made ports
build and work fine on these version will be removed from the tree.

FreeBSD project people strongly recommend to upgrade at least to 6.3.

Thanks
- -- 
Renato Botelho 
   
GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc

PAIN:
Falling out of a twenty story building,
and snagging your eyelid on a nail.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkho1hYACgkQ6CRbiSJE7amZkwCaAtVbC7hrk3JL7hEAWIs52TR4
0J4An3GxRPvGms38NkDooo/e8Xtf7hou
=LHv+
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: cfengine port update?

2008-06-30 Thread Boris Samorodov
On Fri, 27 Jun 2008 09:49:51 -0700 Jo Rhett wrote:

> So I pulled a fresh copy of the portsnap for cfengine port -- we are
> *STILL* on 2.2.3?  How many years does it take to get a port updated?

Well, imho you'd better CC: to the port maintainer. In a week there
will be a maintainer timeout for PR/124993 and you may speek here
once more.

> > On May 9, 2008, at 12:19 AM, Boris Samorodov wrote:
> >>> If there's something wrong
> >>> with them, someone needs to specify what is wrong.
> >>
> >> Seems that you shouldn't delete man pages from the Makefile.
> >
> > They were removed from the distribution, therefore they weren't
> > available to install.

> And I just went through the SVN, and confirmed that the current
> makefile for the product installs only a single man page.  Which is
> exactly what the port patches I sent you reflect.

> If you are saying that you'd like me to override the package
> maintainer and force the installation of man pages which are not
> installed by default, then you need to state that clearly.

> (although I disagree in principle with changing the product as
> delivered by the maintainer without putting those changes into
> OPTIONS)

If you ask me then I was totally satisfied by your answer.


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Resolution: Portmanager stuck in a loop

2008-06-30 Thread Josh Hanson
After some very helpful further discussions with Robert, I tried running
"portmanger -u -p -l -y" to re-build everything, with no success.
Further digging established that my pkg_info database was very confused.
(For example, pkg_info reported that cdrtools is required by xorg-server
and lots of x drivers, which it clearly is not.)

How it got that bad on such a fresh system is a mystery. I don't know
what I could have done to mess it up.

On a whim, I tried running "pkgdb -F" and "pkgdb -fU", but it didn't
make anything better.

Robert suggested that I run pkg_delete -a to start from scratch. I ran
it as an experiment, and it looks like it'd probably work, but as long
as I'm starting from scratch I might as well go all out and reinstall
FreeBSD. I don't yet have any data on this system, so I literally have
nothing to lose, and who knows what else I may have screwed up along the
way?  :)


-Original Message-
From: Robert Noland [mailto:[EMAIL PROTECTED] 
Sent: Friday, June 27, 2008 10:56 AM
To: Josh Hanson
Cc: freebsd-ports@freebsd.org
Subject: RE: Portmanager stuck in a loop

On Fri, 2008-06-27 at 10:46 -0400, Josh Hanson wrote:
> Ok, so I tried running "portmanager -u -p -l -y".
> 
> It built a lot of ports, then got stuck again on xorg-server over and
> over. The log file looks the same as my first post.

Is the options screen being presented repeatedly?  If so, the options
are corrupt and/or not being stored properly.  The dialog box should
only be shown once and use the stored options after that.  You are
running as a user with permission to update /var/db/ports?

robert.

> -- Josh
> 
> 
> -Original Message-
> From: Robert Noland [mailto:[EMAIL PROTECTED] 
> Sent: Friday, June 27, 2008 10:34 AM
> To: Josh Hanson
> Cc: freebsd-ports@freebsd.org
> Subject: Re: Portmanager stuck in a loop
> 
> On Thu, 2008-06-26 at 15:54 -0400, Josh Hanson wrote:
> > Hi,
> > 
> > I'm setting up a fresh installation of freebsd, and portmanager
keeps
> > getting stuck in a loop while trying to upgrade ports.
> > 
> > I ran "portmanager -u -l" with several dozen ports to upgrade. It
> seemed
> > to successfully upgrade quite a few ports; for several ports, it
> brought
> > up the menu with configuration options, and I always just left the
> > defaults.
> > 
> > Eventually, I noticed it brought up some familiar-looking
> configuration
> > screens. Soon, it was simply cycling through the same 3 ports'
> > configuration screens repeatedly. The log shows messages for each
port
> > (repeatedly) saying, "options changed so returning [port name] to
out
> of
> > date pool".
> 
> Some of the port system optimizations caused a situation where a port
> can be left dependent on multiple versions of the same origin.
(Through
> recursive dependencies)  As a result, portmanager will continue to try
> and update the port.  I need to do something of an overhaul of
> portmanager, but other projects are consuming most of my free time
> lately.
> 
> If you use the -p (pristine) flag, portmanager will avoid this issue
by
> ensuring that all ports are updated in order, no matter how deep in
the
> dependency tree.
> 
> FWIW, my usage of portmanager is "portmanager -u -p -l -y".
> 
> robert.
> 
> > I tried manually installing those 3 ports; each said it was already
> > installed, so I did a "make uninstall" then "make install" for each
> one,
> > and ran portmanager again. It continued to run just fine, upgrading
> more
> > ports, then hit the same sort of loop with another set of ports. I
> > upgraded those manually and tried again; each time I installed some
> > ports manually, portmanager would get stuck repeating one or more
> ports.
> > 
> > Background: I had just done a full install from the freebsd CDs,
> > including every standard package except the source code. I then ran
> > portsnap, then installed both portupgrade and portmanager, but after
a
> > bit of reading decided to use portmanager. Portmanager listed
several
> > dozen installed ports with updates available. When I ran it, I
> > encountered the above issues.
> > 
> > An excerpt from the most recent (odd-looking) log file is below.
> Notice
> > that it's repeating the same port over and over.
> > 
> > PS: I'm fairly new to FreeBSD, so if I'm missing something obvious
or
> > asking this question to the wrong place, please let me know.
(Though,
> > even if I'm doing something wrong, there seems to be a bug in
> > portmanager, which is clearly not exhibiting the intended behavior.)
> > 
> > -- Josh
> > 
> > 
> > Log file follows:
> >  
> >
>

> > portmanager 0.4.1_9
> > FreeBSD noc.caprio.corp 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb
24
> > 19:59:52 UTC 2008
> > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386
> >
>

> > autoConflicts  0  autoMoved  0
> > backUp 0  bu

parse the '+CONTENTS' file

2008-06-30 Thread Zane C.B.
When passing the '+CONTENTS' file for a installed package, what do
lines matching /[EMAIL PROTECTED]/ mean past the first one? I know the first one
is the base, but what the ones after that for?

On a similar note, what are the lines matching /[EMAIL PROTECTED]/ for?

I am seeing both in '+CONTENTS' file for 'py25-numeric-24.2'.

@cwd .
@ignore
+COMMENT
@comment MD5:c70b839c2aceba69d631d9bb9df1f872
@ignore
+DESC
@comment MD5:04328d9e04b5b3c5511b13284c7db166
@ignore
+MTREE_DIRS
@comment MD5:219b9fb84bdcc9c6d574c11ea5a3efd9
@mtree +MTREE_DIRS
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: parse the '+CONTENTS' file

2008-06-30 Thread Sergey Matveychuk

Zane C.B. wrote:

When passing the '+CONTENTS' file for a installed package, what do
lines matching /[EMAIL PROTECTED]/ mean past the first one? I know the first one
is the base, but what the ones after that for?

On a similar note, what are the lines matching /[EMAIL PROTECTED]/ for?

I am seeing both in '+CONTENTS' file for 'py25-numeric-24.2'.


Have you already read pkg_create(1) man page?

--
Dixi.
Sem.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Resolution: Portmanager stuck in a loop

2008-06-30 Thread RW
On Mon, 30 Jun 2008 12:25:26 -0400
"Josh Hanson" <[EMAIL PROTECTED]> wrote:

> After some very helpful further discussions with Robert, I tried
> running "portmanger -u -p -l -y" to re-build everything, with no
> success. Further digging established that my pkg_info database was
> very confused. (For example, pkg_info reported that cdrtools is
> required by xorg-server and lots of x drivers, which it clearly is
> not.)

No, that's probably correct, but out of date. A lot of xorg ports can
optionally depend on hal, and hal used to depend on cdrtools.

> How it got that bad on such a fresh system is a mystery. I don't know
> what I could have done to mess it up.

Assuming that it is messed-up.

> On a whim, I tried running "pkgdb -F" and "pkgdb -fU", but it didn't
> make anything better.
> 
> Robert suggested that I run pkg_delete -a to start from scratch.

Probably for the best, I think if you are planning to keep the ports
up to date, it's best to skip the on-disk packages and start from
scratch, that way you can skip many months of UPDATING entries. If you
are in a hurry you can start from the 7-stable packages instead.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Resolution: Portmanager stuck in a loop

2008-06-30 Thread Gerard
On Mon, 30 Jun 2008 12:25:26 -0400
"Josh Hanson" <[EMAIL PROTECTED]> wrote:

> After some very helpful further discussions with Robert, I tried
> running "portmanger -u -p -l -y" to re-build everything, with no
> success. Further digging established that my pkg_info database was
> very confused. (For example, pkg_info reported that cdrtools is
> required by xorg-server and lots of x drivers, which it clearly is
> not.)
> 
> How it got that bad on such a fresh system is a mystery. I don't know
> what I could have done to mess it up.
> 
> On a whim, I tried running "pkgdb -F" and "pkgdb -fU", but it didn't
> make anything better.
> 
> Robert suggested that I run pkg_delete -a to start from scratch. I ran
> it as an experiment, and it looks like it'd probably work, but as long
> as I'm starting from scratch I might as well go all out and reinstall
> FreeBSD. I don't yet have any data on this system, so I literally have
> nothing to lose, and who knows what else I may have screwed up along
> the way?  :)

Before going that route, update your ports tree. Next, run:

portmanager -u -f -l -y

That will rebuild your entire system. I did that once and it did
correct a lot of problems. The down side is that it will rebuild every
port that you have installed and consequently consume a considerable
amount of time if you have many ports installed; i.e. open office for
instance.

Since you have nothing to lose, I would try it out. Before you do it
though, clean out all of the 'portmanger' files in the '/tmp' directory
to insure that you get a fresh build, and be sure to start with the
latest ports updates.

-- 
Gerard
[EMAIL PROTECTED]

Two wrongs are only the beginning.

Kohn


signature.asc
Description: PGP signature


Re: parse the '+CONTENTS' file

2008-06-30 Thread Zane C.B.
On Mon, 30 Jun 2008 21:54:52 +0400
Sergey Matveychuk <[EMAIL PROTECTED]> wrote:

> Zane C.B. wrote:
> > When passing the '+CONTENTS' file for a installed package, what do
> > lines matching /[EMAIL PROTECTED]/ mean past the first one? I know the first
> > one is the base, but what the ones after that for?
> > 
> > On a similar note, what are the lines matching /[EMAIL PROTECTED]/ for?
> > 
> > I am seeing both in '+CONTENTS' file for 'py25-numeric-24.2'.
> 
> Have you already read pkg_create(1) man page?
> 
> -- 
> Dixi.
> Sem.

Thanks. Was not aware that it contained information for that.

Much thanks for the information.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


finance/gnucash won't build, www/gtkhtml38 DEPRECATED

2008-06-30 Thread Mark Ovens
Trying to build finance/gnucash (ports tree updated a couple of hours 
ago) but it depends on www/gtkhtml38 which is marked as DEPRECATED with 
the message to use www/gtkhtml3 instead.


Anyone know why gnucash hasn't been updated to deal with this? Is it OK 
to just hack the gnucash Makefile to use gtkhtml3 instead, or will 
gnucash not work with this.


Regards,

Mark
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Parking arranged

2008-06-30 Thread [EMAIL PROTECTED]
 Information to obtain and pass your k53 learners  test or drivers test is now 
available on a  new d.v.d.  Time and financial resources has been spent on 
fantastic animation so that you can learn through association while being 
entertained. 
The disc contains good music and is the most comprehensive video manual ever 
produced. See what will happen at the yard test. There is no more uncertainty 
and definitely no more fear of the unknown. We reveal it all .Watch this deevd 
and you will pass your learners and license on the first attempt.Send us your 
tel number at [EMAIL PROTECTED] 
One of representatives will then arrange that the manual is delivered to your 
door for  150.00.Should you wish not receive mail from us please send us a 
email at [EMAIL PROTECTED] It is the only tool you require to pass first time. 
I will leave you with one final thought,success is the perseverance of 
purpose.(benjamin disraeli) so I lied here is another two:One must realise that 
even a fool is sometimes correct.(winston-churchill). The only certainty in 
life is uncertainty.(president james munro) 
Kind regards
K53 D>V+D
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: CALL FOR TEST: Updates to pixmap, cairo, poppler, and firefox 3.0!

2008-06-30 Thread Jeremy Messenger
FYI: These have been committed in FreeBSD ports tree. You now can run  
'marcusmerge -U' to unmerge ports-stable and remove it. I will removing  
everything in ports-stable tonight.


Cheers,
Mezz


--
[EMAIL PROTECTED]  -  [EMAIL PROTECTED]
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  [EMAIL PROTECTED]
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"