upgrading ports with a lot of dependencies

2012-08-25 Thread Jim Pazarena

My question is a general one, with the following specific example.

I wanted to re-compile the latest phpmyadmin
but when I tried that, I get a "you must have the latest php5" (5.4.6)

when I try php5
I get a dependency of devel/pkgconf

when I compile pkgconf, it conflicts with devel/pkg-config

Upon investigation it looks like pkg-config is replaced with pkgconf
however attempting to remove it show dozens of dependencies preventing
the removal.

I find this series of challenges frequently as installs move along
in age, and usually wind up re-loading the entire server to beat the
challenge.

There must be an easier way. Advice would be greatly appreciated.
___
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: portmaster 3.13.13 real endless loop "Waiting on fetch & checksum.."

2012-08-25 Thread G. Paul Ziemba
Doug et al.,

I'm following up to the earlier posts from 10 Aug 2012 on this
list, as I am encountering this problem myself. I did not see
a resolution to the problem, so I assume it's still outstanding.

I'm going to provide data for two scenarios below. The first scenario
is the one you describe (portmaster -F). No problem occurs there.
I think this is everything you asked for, but if I missed something or
if you need additional information, please let me know.

The second scenario exhibits the problem. Here, I delete the distfile
and just run portmaster without -F. The fetch completes, but portmaster
does not seem to notice.

thanks for any input/updates,

 ~!paul

% portmaster --version

===>>> Version 3.13.13


== portmaster -F scenario (works OK) 

Doug wrote:
> Ok, so do this ... remove the file from /usr/ports/distfiles, then go to
> the port directory and type 'make checksum' and see if it works
> properly.

% sudo rm /usr/ports/distfiles/gsoap_2.8.8.zip
% cd /usr/ports/devel/gsoap
% sudo make checksum
===>  Found saved configuration for gsoap-2.8.8
=> gsoap_2.8.8.zip doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch 
http://heanet.dl.sourceforge.net/project/gsoap2/gSOAP/gsoap_2.8.8.zip
gsoap_2.8.8.zip   100% of   13 MB  148 kBps 00m00s
=> SHA256 Checksum OK for gsoap_2.8.8.zip.

> Then remove it again, and run 'portmaster -F'
> 
> While that's running in one window, keep an eye on /usr/ports/distfiles
> and see if the file is being downloaded, and also keep an eye on the log
> file in $TMPDIR to see if it is being appended to.
> 
> Also make sure that whatever directory you use for $TMPDIR (/tmp by
> default) has permissions 1777, and is not mounted with odd options.

% sudo rm /usr/ports/distfiles/gsoap_2.8.8.zip
% sudo portmaster -F devel/gsoap

===>>> Currently installed version: gsoap-2.7.15
===>>> Port directory: /usr/ports/devel/gsoap

===>>> Launching 'make checksum' for devel/gsoap in background
===>>> Gathering dependency list for devel/gsoap from ports
===>>> Initial dependency check complete for devel/gsoap


===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Waiting for 1 distfile fetch to finish
===>>> Distfile fetching is complete

[/usr/ports/distfiles/gsoap_2.8.8.zip was downloaded]
[/tmp/f-* appeared immediately, then stayed the same size for the
duration of the download, then were removed]

% while ( 1 )
while? ls -las /tmp/f-*
while? sleep 2
while? end
ls: No match.
ls: No match.
0 -rw---  1 root  wheel0 Aug 25 16:29 /tmp/f-84142-IPC_SAVE.78khxchE
2 -rw---  1 root  wheel  209 Aug 25 16:29 
/tmp/f-84142-fetchlog-gsoap.MyjTns6u
0 -rw---  1 root  wheel0 Aug 25 16:29 
/tmp/f-84142-gsoap_2.8.8.zip-gsoap.Xn4WsqOo
0 -rw---  1 root  wheel0 Aug 25 16:29 /tmp/f-84142-IPC_SAVE.78khxchE
2 -rw---  1 root  wheel  255 Aug 25 16:29 
/tmp/f-84142-fetchlog-gsoap.MyjTns6u
0 -rw---  1 root  wheel0 Aug 25 16:29 
/tmp/f-84142-gsoap_2.8.8.zip-gsoap.Xn4WsqOo

[...]

0 -rw---  1 root  wheel0 Aug 25 16:29 /tmp/f-84142-IPC_SAVE.78khxchE
2 -rw---  1 root  wheel  324 Aug 25 16:31 
/tmp/f-84142-fetchlog-gsoap.MyjTns6u
0 -rw---  1 root  wheel0 Aug 25 16:29 
/tmp/f-84142-gsoap_2.8.8.zip-gsoap.Xn4WsqOo
ls: No match.

[TMPDIR details follow]

% ls -las /tmp
0 lrwx--  1 root  wheel  8 Feb 15  2002 /tmp@ -> /var/tmp
% ls -ld /var/tmp
drwxrwxrwt  49 root  wheel  28160 Aug 25 16:35 /var/tmp/

== portmaster (no -F) scenario (doesn't work) 
[please also scroll to bottom, where I show the contents of /tmp/f-*]


% sudo rm /usr/ports/distfiles/gsoap_2.8.8.zip
% sudo portmaster devel/gsoap

===>>> Currently installed version: gsoap-2.7.15
===>>> Port directory: /usr/ports/devel/gsoap

===>>> Gathering distinfo list for installed ports

===>>> Launching 'make checksum' for devel/gsoap in background
===>>> Gathering dependency list for devel/gsoap from ports
===>>> Initial dependency check complete for devel/gsoap


===>>> Starting build for devel/gsoap <<<===

===>>> All dependencies are up to date

===>  Cleaning for gsoap-2.8.8
===>>> Waiting on fetch & checksum for devel/gsoap <<<===
===>  Found saved configuration for gsoap-2.8.8
=> gsoap_2.8.8.zip doesn't seem to exist in /usr/ports/distfiles//.
=> Attempting

Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap

2012-08-25 Thread CyberLeo Kitsana
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 08/24/2012 07:01 PM, Baptiste Daroussin wrote:
> Can anyone give me he details on the security related problem?

Off the top of my head, it seems to represent a break in the chain of
trust: how does the bootstrapper verify that the tarball it just
downloaded to bootstrap pkg is genuine, and not, for example, a
trojan? The source in usr.sbin/pkg/pkg.c[1] doesn't seem to suggest it
cares.

[1]
http://git.cyberleo.net/?p=FreeBSD/releng/9.1.git;a=blob;f=usr.sbin/pkg/pkg.c;hb=b96b623d8debed8fa8fd7df5af01a350344549c9

- -- 
Fuzzy love,
- -CyberLeo
Technical Administrator
CyberLeo.Net Webhosting
http://www.CyberLeo.Net


Furry Peace! - http://.fur.com/peace/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlA5YRMACgkQi7w8kEi1KHLZhwCgrGb8piGeNb07IryWvoc/JdzH
xfAAoNfxm+nLoXU7BUclKqnLGbkxgilX
=o9Br
-END PGP SIGNATURE-
___
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: patch to build spamass-milter with sendmail-sasl

2012-08-25 Thread Curtis Villamizar

In message 
Chris Rees writes:
 
> On 25 August 2012 21:38, Curtis Villamizar  wrote:
> >
> > In message 
> > 
> > Chris Rees writes:
> >
> >> On 23 August 2012 21:37, Lawrence K. Chen, P.Eng.  wrote:
> >> > Just the patch I was looking for.
> >> >
> >> > - Original Message -
> >> >>
> >> >> FYI-
> >> >>
> >> >> The mail/spamass-milter port won't build if the sendmail-sasl port
> >> >> has
> >> >> been built.  The patch below fixes this.
> >> >>
> >> >> The port maintainer is on the Cc.  No bug has been reported.
> >>
> >> Thanks for your patch Curtis; I've used it as a base for some further
> >> tweaks, and sent a PR [1].
> >>
> >> Unfortunately you hadn't CC'd the correct maintainer, but this is not
> >> a problem since the PR will email him for us.
> >>
> >> Chris
> >>
> >> [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=170943
> >
> >
> > There may be a better way to fix this - eliminate the need for the
> > sendmail-sasl and sendmail-ldap ports by using the options framework
> > in the sendmail port.  I used this diff to do that in a later build.
> > (the first was amd64, the second i386).
> >
> > Curtis
> >
> >
> > The following patch is to the Makefile in {/usr/ports/}mail/sendmail
> > and only makes use of the port options framework to set options rather
> > than having users either type them on the command line, or edit the
> > makefile, or use pseudo ports like sendmail-sasl and sendmail-ldap to
> > set a specific option.  The sendmail-sasl and sendmail-ldap should be
> > marked as depricated in their makefiles.
> >
>  
> [previous patch trimmed; can be found at [1]]
>  
> Ah... the use of slave ports (like -sasl) is to create handy packages
> for those who use packages, as well as meaning that people can put
> dependencies on certain OPTIONS.
>  
> Also, your code could be a little more brief;
>  
> # convert OPTIONS in WITH_* form to SENDMAIL_WITH_*
> .if defined(WITH_IPV6)
> SENDMAIL_WITH_IPV6=yes
> .else
> SENDMAIL_WITHOUT_IPV6=yes
> .endif
>  
> should be using OPTIONSng, and a for loop:
>  
> .for o in ${PORT_OPTIONS}
> .if ${PORT_OPTIONS:M$o}
> SENDMAIL_WITH_$o=yes
> .else
> SENDMAIL_WITHOUT_$o=yes
> .endif
>  
> To be honest, it's not really good enough to be hacking the Makefile
> like this; if you would like to try a conversion to new-style OPTIONS
> I would recommend reading [2], but before you put yourself through
> this CHECK WITH THE MAINTAINER (CC'd) that such a patch would be
> accepted!
>  
> I'm willing to help off-list if Dirk will accept a patch.
>  
> Chris
>  
> [1] http://lists.freebsd.org/pipermail/freebsd-ports/2012-August/05.html
>  
> [2] 
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-options.html#AEN2638


Chris,

Thanks.  I'll create an OPTIONSng patch for the mail/sendmail Makefile
and send it and just hope it gets accepted.  If not, I'll keep it as a
local patch.  Its not much work.

Curtis
___
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: patch to build spamass-milter with sendmail-sasl

2012-08-25 Thread Chris Rees
On 25 August 2012 21:38, Curtis Villamizar  wrote:
>
> In message 
> 
> Chris Rees writes:
>
>> On 23 August 2012 21:37, Lawrence K. Chen, P.Eng.  wrote:
>> > Just the patch I was looking for.
>> >
>> > - Original Message -
>> >>
>> >> FYI-
>> >>
>> >> The mail/spamass-milter port won't build if the sendmail-sasl port
>> >> has
>> >> been built.  The patch below fixes this.
>> >>
>> >> The port maintainer is on the Cc.  No bug has been reported.
>>
>> Thanks for your patch Curtis; I've used it as a base for some further
>> tweaks, and sent a PR [1].
>>
>> Unfortunately you hadn't CC'd the correct maintainer, but this is not
>> a problem since the PR will email him for us.
>>
>> Chris
>>
>> [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=170943
>
>
> There may be a better way to fix this - eliminate the need for the
> sendmail-sasl and sendmail-ldap ports by using the options framework
> in the sendmail port.  I used this diff to do that in a later build.
> (the first was amd64, the second i386).
>
> Curtis
>
>
> The following patch is to the Makefile in {/usr/ports/}mail/sendmail
> and only makes use of the port options framework to set options rather
> than having users either type them on the command line, or edit the
> makefile, or use pseudo ports like sendmail-sasl and sendmail-ldap to
> set a specific option.  The sendmail-sasl and sendmail-ldap should be
> marked as depricated in their makefiles.
>

[previous patch trimmed; can be found at [1]]

Ah... the use of slave ports (like -sasl) is to create handy packages
for those who use packages, as well as meaning that people can put
dependencies on certain OPTIONS.

Also, your code could be a little more brief;

# convert OPTIONS in WITH_* form to SENDMAIL_WITH_*
.if defined(WITH_IPV6)
SENDMAIL_WITH_IPV6=yes
.else
SENDMAIL_WITHOUT_IPV6=yes
.endif

should be using OPTIONSng, and a for loop:

.for o in ${PORT_OPTIONS}
.if ${PORT_OPTIONS:M$o}
SENDMAIL_WITH_$o=yes
.else
SENDMAIL_WITHOUT_$o=yes
.endif

To be honest, it's not really good enough to be hacking the Makefile
like this; if you would like to try a conversion to new-style OPTIONS
I would recommend reading [2], but before you put yourself through
this CHECK WITH THE MAINTAINER (CC'd) that such a patch would be
accepted!

I'm willing to help off-list if Dirk will accept a patch.

Chris

[1] http://lists.freebsd.org/pipermail/freebsd-ports/2012-August/05.html

[2] 
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-options.html#AEN2638
___
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: patch to build spamass-milter with sendmail-sasl

2012-08-25 Thread Curtis Villamizar

In message 
Chris Rees writes:
 
> On 23 August 2012 21:37, Lawrence K. Chen, P.Eng.  wrote:
> > Just the patch I was looking for.
> >
> > - Original Message -
> >>
> >> FYI-
> >>
> >> The mail/spamass-milter port won't build if the sendmail-sasl port
> >> has
> >> been built.  The patch below fixes this.
> >>
> >> The port maintainer is on the Cc.  No bug has been reported.
>  
> Thanks for your patch Curtis; I've used it as a base for some further
> tweaks, and sent a PR [1].
>  
> Unfortunately you hadn't CC'd the correct maintainer, but this is not
> a problem since the PR will email him for us.
>  
> Chris
>  
> [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=170943


There may be a better way to fix this - eliminate the need for the
sendmail-sasl and sendmail-ldap ports by using the options framework
in the sendmail port.  I used this diff to do that in a later build.
(the first was amd64, the second i386).

Curtis


The following patch is to the Makefile in {/usr/ports/}mail/sendmail
and only makes use of the port options framework to set options rather
than having users either type them on the command line, or edit the
makefile, or use pseudo ports like sendmail-sasl and sendmail-ldap to
set a specific option.  The sendmail-sasl and sendmail-ldap should be
marked as depricated in their makefiles.


--- Makefile.orig   2012-08-14 12:59:13.0 -0400
+++ Makefile2012-08-14 13:05:18.0 -0400
@@ -41,26 +41,113 @@
 PKGMESSAGE=${WRKSRC}/pkg-message
 MILTER_SOVER?= 4
 
-# Options to define Features:
-# SENDMAIL_WITHOUT_IPV6=yes
-# SENDMAIL_WITHOUT_MILTER=yes
-# SENDMAIL_WITHOUT_NIS=yes
-# SENDMAIL_WITHOUT_SHMEM=yes
-# SENDMAIL_WITHOUT_SEM=yes
-# SENDMAIL_WITHOUT_LA=yes
-# SENDMAIL_WITHOUT_MILTER_POOL
-# SENDMAIL_WITH_TLS=yes
-# SENDMAIL_WITH_SMTPS=yes
-# SENDMAIL_WITH_SASL=yes
-# SENDMAIL_WITH_SASL2=yes
-# SENDMAIL_WITH_LDAP=yes
-# SENDMAIL_WITH_BERKELEYDB=yes
-#   Set either WITH_BDB_VER or SENDMAIL_WITH_BDB_VER
-#   to the version of Berkeley DB to use.
-# SENDMAIL_WITH_SOCKETMAP=yes
-# SENDMAIL_WITH_CYRUSLOOKUP=yes
-# SENDMAIL_WITH_PICKY_HELO_CHECK=yes
-# SENDMAIL_WITH_SHARED_MILTER=yes
+OPTIONS=   IPV6"build with IPv6 support" on \
+   MILTER  "milter (mail filter plugin interface)" on \
+   MILTER_POOL "milter pool (allow worker pools)" on \
+   NIS "NIS (aka YP services)" off \
+   SHMEM   "SysV shared memory (SHMEM)" on \
+   SEM "SysV semaphores (SEM)" on \
+   LA  "Load average support" on \
+   TLS "transport layer security (TLS)" off \
+   SMTPS   "SMTP security" on \
+   SASL"SASL (version 2)" on \
+   SASLAUTHD   "SASL authorization daemon" off \
+   LDAP"LDAP" off \
+   BDB "Berle;ey database (DB4" on \
+   SOCKETMAP   "trivial SOCKETMAP query protocol" off \
+   CYRUSLOOKUP "SASL database lookup" off \
+   PICKY_HELO_CHECK"enable picky SMTP HELO check" off \
+   SHARED_MILTER   "shared milter" off
+
+.include 
+
+# convert OPTIONS in WITH_* form to SENDMAIL_WITH_*
+.if defined(WITH_IPV6)
+SENDMAIL_WITH_IPV6=yes
+.else
+SENDMAIL_WITHOUT_IPV6=yes
+.endif
+.if defined(WITH_MILTER)
+SENDMAIL_WITH_MILTER=yes
+.else
+SENDMAIL_WITHOUT_MILTER=yes
+.endif
+.if defined(WITH_MILTER_POOL)
+SENDMAIL_WITH_MILTER_POOL=yes
+.else
+SENDMAIL_WITHOUT_MILTER_POOL=yes
+.endif
+.if defined(WITH_NIS)
+SENDMAIL_WITH_NIS=yes
+.else
+SENDMAIL_WITHOUT_NIS=yes
+.endif
+.if defined(WITH_SHMEM)
+SENDMAIL_WITH_SHMEM=yes
+.else
+SENDMAIL_WITHOUT_SHMEM=yes
+.endif
+.if defined(WITH_SEM)
+SENDMAIL_WITH_SEM=yes
+.else
+SENDMAIL_WITHOUT_SEM=yes
+.endif
+.if defined(WITH_LA)
+SENDMAIL_WITH_LA=yes
+.else
+SENDMAIL_WITHOUT_LA=yes
+.endif
+.if defined(WITH_TLS)
+SENDMAIL_WITH_TLS=yes
+.else
+SENDMAIL_WITHOUT_TLS=yes
+.endif
+.if defined(WITH_SMTPS)
+SENDMAIL_WITH_SMTPS=yes
+.else
+SENDMAIL_WITHOUT_SMTPS=yes
+.endif
+.if defined(WITH_SASL)
+SENDMAIL_WITH_SASL=yes
+SENDMAIL_WITH_SASL2=yes
+.else
+SENDMAIL_WITHOUT_SASL=yes
+SENDMAIL_WITHOUT_SASL2=yes
+.endif
+.if defined(WITH_LDAP)
+SENDMAIL_WITH_LDAP=yes
+.else
+SENDMAIL_WITHOUT_LDAP=yes
+.endif
+.if defined(WITH_BDB)
+SENDMAIL_WITH_BDB=yes
+SENDMAIL_WITH_BDB_VER=4
+.endif
+.if defined(WITH_SOCKETMAP)
+SENDMAIL_WITH_SOCKETMAP=yes
+.else
+SENDMAIL_WITHOUT_SOCKETMAP=yes
+.endif
+.if defined(WITH_CYRUSLOOKUP)
+SENDMAIL_WITH_CYRUSLOOKUP=yes
+.else
+SENDMAIL_WITHOUT_CYRUSLOOKUP=yes
+.endif
+.if defined(WITH_PICKY_HELO_CHECK)
+SENDMAIL_WITH_PICKY_HELO_CHECK=yes
+.else
+SENDMAIL_WITHOUT_PICKY_HELO_CHECK=yes
+.endif
+.if defined(WITH_SHARED_MILTER)
+SENDMAIL_WITH_SHARED_MILTER=yes
+.else
+SENDMAIL_WITHOUT_SHARED_MILTER=yes
+.endif
+
+#
+#  Override some related defines.
+#  This should be changed to point out conflicts and s

Re: apcupsd compile fails on 9-stable amd64

2012-08-25 Thread Warren Block

On Sat, 25 Aug 2012, Oleg Ginzburg wrote:


On Saturday 25 August 2012 18:06:29 Warren Block wrote:

Discovered last night that sysutils/apcupsd will not compile on 9-stable
amd64 if the USB or SNMP options are enabled.  It does compile on
8.3-stable i386.  Stock gcc, not clang.  ccache is installed, but not
used for ports.  Any suggestions?

...
   CXX   src/apcupsd.c
   CXX   src/apcnis.c
   LDsrc/apcupsd
/usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(s
nmp.o): In function `Snmp::VarBindList::VarBindList(Asn::Sequence&)':
snmp.cpp:(.text+0x7a8): undefined reference to `operator new[](unsigned
long)'
/usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(
snmp.o): In function `Snmp::VarBindList::Append(Asn::ObjectId const&,
Snmp::Variable*)': snmp.cpp:(.text+0xdc9): undefined reference to
`operator new[](unsigned long)'
/usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(
snmp.o): In function `Snmp::VarBindList::VarBindList(Asn::Sequence&)':
snmp.cpp:(.text+0xec8): undefined reference to `operator new[](unsigned
long)'
/usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(
asn.o): In function `Asn::Sequence::assign(Asn::Sequence const&)':
asn.cpp:(.text+0x73d): undefined reference to `operator new[](unsigned
long)'
/usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(
asn.o): In function `Asn::ObjectId::demarshal(unsigned char*&, unsigned
int&)': asn.cpp:(.text+0x82b): undefined reference to `operator
new[](unsigned long)'
/usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(
asn.o):asn.cpp:(.text+0x934): more undefined references to `operator
new[](unsigned long)' follow


Ive already register PR for this: http://www.freebsd.org/cgi/query-
pr.cgi?pr=ports/170522


Sorry, saw that last night, but forgot about it.  The fix works for me. 
Thanks!

___
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"


FreeBSD port: stellarium 0.11.4

2012-08-25 Thread Alexander Wolf
Hello!

Today has been released Stellarium 0.11.4 with improvements for *BSD systems.

I'm write patch for FreeBSD port:
http://astro.uni-altai.ru/~aw/patches/FreeBSD-stellarium.patch

-- 
With best regards, Alexander
___
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: P2 testing of pkg

2012-08-25 Thread Lars Engels
On Fri, Aug 24, 2012 at 07:16:48PM -0700, Jeffrey Bouquet wrote:
> pkg2ng fails to register anything:
> Undefined symbol "_ThreadRuneLocale"
> It tries; Each port is attempted to be registered.
> ...
> Unknown if that is because of the p2 having an earlier version
> of 9-STABLE than upon which was built /pkg/
> ...
> As an aside, now that bsdstats.org has its port statistics back up,
> I see that /pkg/ is installed in only a small subset of reporting
> BSD/pc-bsd/etc/ machines... 
> portupgrade   4697
> portmaster2039
> portmanager322
> portupgrade-devel  185
> pkg 41
> As of earlier today anyway.

That's because PC-BSD has portupgrade installed and bsdstats activeated
by default. 
I guess only a few people are still running bsdstats, because it was
broken for so long...


pgp5GXYw3nYkn.pgp
Description: PGP signature


Re: optionsNG NLS description

2012-08-25 Thread Gabor Kovesdan

On 2012.08.25. 16:16, Alberto Villa wrote:

On Wed, Aug 1, 2012 at 3:32 AM, Alberto Villa  wrote:

>I'd like to do the change as well. Can we proceed with the commit
>since you got no objection?

Change committed in r303137.

Thanks!

Gabor
___
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: apcupsd compile fails on 9-stable amd64

2012-08-25 Thread Oleg Ginzburg
Hi

On Saturday 25 August 2012 18:06:29 Warren Block wrote:
> Discovered last night that sysutils/apcupsd will not compile on 9-stable
> amd64 if the USB or SNMP options are enabled.  It does compile on
> 8.3-stable i386.  Stock gcc, not clang.  ccache is installed, but not
> used for ports.  Any suggestions?
> 
> ...
>CXX   src/apcupsd.c
>CXX   src/apcnis.c
>LDsrc/apcupsd
> /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(s
> nmp.o): In function `Snmp::VarBindList::VarBindList(Asn::Sequence&)':
> snmp.cpp:(.text+0x7a8): undefined reference to `operator new[](unsigned
> long)'
> /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(
> snmp.o): In function `Snmp::VarBindList::Append(Asn::ObjectId const&,
> Snmp::Variable*)': snmp.cpp:(.text+0xdc9): undefined reference to
> `operator new[](unsigned long)'
> /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(
> snmp.o): In function `Snmp::VarBindList::VarBindList(Asn::Sequence&)':
> snmp.cpp:(.text+0xec8): undefined reference to `operator new[](unsigned
> long)'
> /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(
> asn.o): In function `Asn::Sequence::assign(Asn::Sequence const&)':
> asn.cpp:(.text+0x73d): undefined reference to `operator new[](unsigned
> long)'
> /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(
> asn.o): In function `Asn::ObjectId::demarshal(unsigned char*&, unsigned
> int&)': asn.cpp:(.text+0x82b): undefined reference to `operator
> new[](unsigned long)'
> /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(
> asn.o):asn.cpp:(.text+0x934): more undefined references to `operator
> new[](unsigned long)' follow
> ___
> 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"

Ive already register PR for this: http://www.freebsd.org/cgi/query-
pr.cgi?pr=ports/170522

-- 
С уважением, With respect,
Олег Гинзбург Oleg Ginzburg
=
E-mail: mailto: olev...@olevole.ru
Skype: olegginzburg
XMPP/Jabber: olev...@jabber.ru

___
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: optionsNG NLS description

2012-08-25 Thread Alberto Villa
On Wed, Aug 1, 2012 at 3:32 AM, Alberto Villa  wrote:
> I'd like to do the change as well. Can we proceed with the commit
> since you got no objection?

Change committed in r303137.
-- 
Alberto Villa, FreeBSD committer 
http://people.FreeBSD.org/~avilla
___
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"


apcupsd compile fails on 9-stable amd64

2012-08-25 Thread Warren Block
Discovered last night that sysutils/apcupsd will not compile on 9-stable 
amd64 if the USB or SNMP options are enabled.  It does compile on 
8.3-stable i386.  Stock gcc, not clang.  ccache is installed, but not 
used for ports.  Any suggestions?


...
  CXX   src/apcupsd.c
  CXX   src/apcnis.c
  LDsrc/apcupsd
/usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(snmp.o): 
In function `Snmp::VarBindList::VarBindList(Asn::Sequence&)':
snmp.cpp:(.text+0x7a8): undefined reference to `operator new[](unsigned long)'
/usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(snmp.o): 
In function `Snmp::VarBindList::Append(Asn::ObjectId const&, Snmp::Variable*)':
snmp.cpp:(.text+0xdc9): undefined reference to `operator new[](unsigned long)'
/usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(snmp.o): 
In function `Snmp::VarBindList::VarBindList(Asn::Sequence&)':
snmp.cpp:(.text+0xec8): undefined reference to `operator new[](unsigned long)'
/usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(asn.o): 
In function `Asn::Sequence::assign(Asn::Sequence const&)':
asn.cpp:(.text+0x73d): undefined reference to `operator new[](unsigned long)'
/usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(asn.o): In 
function `Asn::ObjectId::demarshal(unsigned char*&, unsigned int&)':
asn.cpp:(.text+0x82b): undefined reference to `operator new[](unsigned long)'
/usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(asn.o):asn.cpp:(.text+0x934):
 more undefined references to `operator new[](unsigned long)' follow
___
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: One more pkg non-default-please edge-case reasoning...

2012-08-25 Thread Patrick Lamaiziere
Le Fri, 24 Aug 2012 19:44:15 -0700 (PDT),
Jeffrey Bouquet  a écrit :

> This side of simple. (Additionally, a nice white-on-blue readability).
> Never got used to the search keys in "less" etc.  So the flat files
> here serve a purpose I surmise is not that common.
> And figuring out which  category /editors/ etc (the pkg-plist
> equivalent) is way slower in many cases.
> A reason to retain that particular usability... til/when I/someone
> notices a workaround.

I'm not sure to understand what you want to do, but listing the files
owned by an installed pkg packages is easy:
for zip:
# pkg info -l zip
zip-3.0 owns the following files:
/usr/local/bin/zip
...
/usr/local/share/doc/zip/WHERE

Please have a try with pkg, is really great.
___
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: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap

2012-08-25 Thread Julien Laffaye

On 8/24/2012 11:57 PM, Doug Barton wrote:

On 8/23/2012 8:03 PM, Eitan Adler wrote:

On 23 August 2012 22:59, Doug Barton  wrote:

I tend to agree with Steve here ... we can't be responsible for other
people's poorly written docs.

This isn't about poorly written docs. This is the user expecting a
tool to exist, which doesn't. Take another example of a sysadmin which
rarely installs new systems, installs FreeBSD for the third time, and
then gets confused when "pkg install vim" fails.

Aren't we going to install the pkg package on new systems when they are
installed? Isn't that (shouldn't that be?) part of the project plan? It
would be insane for us not to do that, at least for the releases where
pkg is the default.


True. But when you create jails without the installer, you have to 
install pkgng by hand. Hence the /usr/sbin/pkg bootstrap.





You bring up a valid point that we should
keep in mind for our own however. The bootstrapping issue will be the
smallest possible annoyance on a long road of the migration process.

The bootstrapping issue is a factor even after the migration :)

I think that the point I'm trying to make is that it shouldn't be.


note that I'm not talking about the mechanism here, I'm trying to
avoid "pkg doesn't seem to be installed on my fresh system" becoming a
FAQ.

The way that we avoid that problem is not to create it for ourselves in
the first place. :)

The role of pkg-bootstrap is for those users who have already-installed
systems that need to do the conversion, or if somehow pkg becomes
corrupted on the user's system and needs to be reinstalled. That's it.

I like that you're thinking through the related issues, but in this
particular case I think you're overthinking it.

Doug



___
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: P2 testing of pkg

2012-08-25 Thread Florian Smeets
On 25.08.12 04:16, Jeffrey Bouquet wrote:
> pkg2ng fails to register anything:
> Undefined symbol "_ThreadRuneLocale"
> It tries; Each port is attempted to be registered.
> ...
> Unknown if that is because of the p2 having an earlier version
> of 9-STABLE than upon which was built /pkg/
> ...

Yes it is, it has nothing to do with pkg itself. Rebuild pkg on "p2" or
upgrade to newer 9-STABLE.

Florian



signature.asc
Description: OpenPGP digital signature