Re: openldap-server exit on signal 6 on 11.1 (and not in 10.3)

[Xin LI]

Hi,


On Fri, Feb 9, 2018 at 12:33 AM joris dedieu  wrote:

> Dear porters,
>
> While moving from 10.3 to 11.1, I get an issue on openldap execution.
> slapd dies (pid 29087 (slapd), uid 389: exited on signal 6) on some
> complex but reproducible operations.
>
> We worked around this bug by returning less elements from the request.
> While my dear colleges are trying to write a script to reproduce the
> issue, I investigate system side.
>
>
> In /var/log/messages, I got slapd[4909]: stack overflow detected;
> terminated
>
> The only trace I get
>
> #0  0x000801f7a71a in kill () from /lib/libc.so.7
> #1  0x000801f7a6d0 in __stack_chk_fail () from /lib/libc.so.7
> #2  0x000801f7a640 in __stack_chk_fail () from /lib/libc.so.7
> #3  0x004466e6 in do_modify ()
> #4  0x004308d5 in connection_assign_nextid ()
> #5  0x004300dd in connection_read_activate ()
> #6  0x000800956ffa in ldap_pvt_thread_pool_submit () from
> /usr/local/lib/libldap_r-2.4.so.2
> #7  0x000801c71bc5 in pthread_create () from /lib/libthr.so.3
> #8  0x in ?? ()
>

​I have never seen this on my own systems.


> I suspect it's relative to -fstack-protector-strong  which is the
> default since FreeBSD 11.0. Do you think I should rebuild all the
> world this opion ?
>

Is the slapd binary from 10.3 (still considered a bug in this case), or
have you rebuilt it?  If you have coredumps, please try to collect
additional information on do_modify() as this might indicate a security
issue as well.  Reporting this to upstream (openldap.org) would usually be
helpful if you believe it's an OpenLDAP bug.

Cheers,​



>
> I also thought on fdatasync
>
>  .if ${OSVERSION} < 1101000
> CFLAGS+=-DMDB_DSYNC=O_SYNC -Dfdatasync=fsync
> .endif
>
> I'm currently investigating on this changes.
>
> The issue disappear when slapd is compiled with debugging symbols
> (WITH_DEBUG=YES). As far as I understand, this only cause -g flag to
> be added to CFLAGS. Does WITH_DEBUG also disable some compiler
> optimization  ?
>
> Any thought on all this is welcomed
>
> Joris
>
>
> Openldap options :
> Name   : openldap-sasl-server
> Version: 2.4.45_4
> Installed on   : Thu Feb  8 16:16:45 2018 CET
> Origin : net/openldap24-server
> Architecture   : FreeBSD:11:amd64
> Prefix : /usr/local
> Categories : databases net
> Licenses   : OPENLDAP
> Maintainer : delp...@freebsd.org
> WWW: http://www.OpenLDAP.org/
> Comment: Open source LDAP server implementation
> Options:
> ACCESSLOG  : on
> ACI: off
> AUDITLOG   : off
> BDB: off
> COLLECT: off
> CONSTRAINT : off
> DDS: off
> DEBUG  : off
> DEREF  : off
> DNSSRV : off
> DYNACL : off
> DYNAMIC_BACKENDS: on
> DYNGROUP   : off
> DYNLIST: off
> FETCH  : off
> GSSAPI : on
> KQUEUE : off
> LASTBIND   : off
> LMPASSWD   : off
> MDB: on
> MEMBEROF   : off
> ODBC   : off
> OUTLOOK: off
> PASSWD : off
> PERL   : off
> PPOLICY: on
> PROXYCACHE : off
> REFINT : off
> RELAY  : off
> RETCODE: off
> RLOOKUPS   : off
> RWM: off
> SASL   : on
> SEQMOD : off
> SHA2   : off
> SHELL  : off
> SLAPI  : off
> SLP: off
> SMBPWD : off
> SOCK   : off
> SSSVLV : off
> SYNCPROV   : on
> TCP_WRAPPERS   : off
> TRANSLUCENT: off
> UNIQUE : off
> VALSORT: off
>
___
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: svn commit: r424112 - in head/www/fcgiwrap: . files

[Xin LI]

Hi, Mathieu,

Sorry for catching this late, but is there any reason not to simply
run the daemon under the desired credentials, instead of doing this
chown/chmod dance afterward?

Not all systems start fcgiwrap daemon quick enough for the socket to
show up (a race condition, with potential of not setting it correctly,
which is observed about 3/5 times on my server).  Moreover, this will
also encourage using unneeded privileges (assuming fcgiwrap runs under
root credentials, which is the default fcgiwrap_user).

Cheers,

On Mon, Oct 17, 2016 at 5:03 AM, Mathieu Arnold  wrote:
> Author: mat
> Date: Mon Oct 17 12:03:08 2016
> New Revision: 424112
> URL: https://svnweb.freebsd.org/changeset/ports/424112
>
> Log:
>   Add changing the owner/group/mode for the socket.
>
>   PR:   213385
>   Submitted by: mat
>   Approved by:  maintainer
>   Sponsored by: Absolight
>
> Modified:
>   head/www/fcgiwrap/Makefile   (contents, props changed)
>   head/www/fcgiwrap/files/fcgiwrap.in
>
> Modified: head/www/fcgiwrap/Makefile
> ==
> --- head/www/fcgiwrap/Makefile  Mon Oct 17 12:03:03 2016(r424111)
> +++ head/www/fcgiwrap/Makefile  Mon Oct 17 12:03:08 2016(r424112)
> @@ -2,7 +2,7 @@
>
>  PORTNAME=  fcgiwrap
>  PORTVERSION=   1.1.0
> -PORTREVISION=  3
> +PORTREVISION=  4
>  CATEGORIES=www
>  MASTER_SITES=  http://www.skysmurf.nl/comp/FreeBSD/distfiles/
>
>
> Modified: head/www/fcgiwrap/files/fcgiwrap.in
> ==
> --- head/www/fcgiwrap/files/fcgiwrap.in Mon Oct 17 12:03:03 2016
> (r424111)
> +++ head/www/fcgiwrap/files/fcgiwrap.in Mon Oct 17 12:03:08 2016
> (r424112)
> @@ -19,6 +19,9 @@
>  # - tcp6:[ipv6_addr]:port (for ipv6)
>  # fcgiwrap_flags=
>  # Use fcgiwrap_user to run fcgiwrap as user
> +# Use fcgiwrap_socket_mode to change the mode of the socket
> +# Use fcgiwrap_socket_owner to change the owner of the socket
> +# Use fcgiwrap_socket_group to change the group of the socket
>
>  # fcgiwrap rc.d script supports multiple profiles (a-la rc.d/nginx)
>  # When profiles are specified, the non-profile specific parameters become 
> defaults.
> @@ -29,10 +32,12 @@
>  # fcgiwrap_enable="YES"
>  # fcgiwrap_profiles="myserver myotherserver"
>  # fcgiwrap_flags="-c 4"
> +# fcgiwrap_socket_owner="www"
>  # fcgiwrap_myserver_socket="unix:/var/run/fcgiwrap.myserver.socket"
>  # fcgiwrap_myserver_user="myuser"
>  # fcgiwrap_myotherserver_socket="unix:/var/run/fcgiwrap.myotherserver.socket"
>  # fcgiwrap_myotherserver_user="myotheruser"
> +# fcgiwrap_myserver_socket_mode="0775"
>  # fcgiwrap_myotherserver_flags=""  # No flags for this profile.
>
>  . /etc/rc.subr
> @@ -62,6 +67,26 @@ fcgiwrap_precmd() {
> install -d -o root -g wheel -m 1777 /var/run/fcgiwrap
>  }
>
> +fcgiwrap_postcmd() {
> +   # This is only for unix sockets
> +   case "${fcgiwrap_socket}" in
> +   unix:*)
> +   ;;
> +   *)
> +   return
> +   ;;
> +   esac
> +   if [ -n "${fcgiwrap_socket_mode}" ]; then
> +   chmod ${fcgiwrap_socket_mode} ${fcgiwrap_socket#unix:}
> +   fi
> +   if [ -n "${fcgiwrap_socket_owner}" ]; then
> +   chown ${fcgiwrap_socket_owner} ${fcgiwrap_socket#unix:}
> +   fi
> +   if [ -n "${fcgiwrap_socket_group}" ]; then
> +   chgrp ${fcgiwrap_socket_group} ${fcgiwrap_socket#unix:}
> +   fi
> +}
> +
>  fcgiwrap_cleansocket() {
> # Workaround the fact that fcgiwrap doesn't cleanup his socket at 
> stopping
> case ${fcgiwrap_socket} in
> @@ -78,6 +103,7 @@ pidfile="${pidprefix}.pid"  # May be a d
>  procname="%%PREFIX%%/sbin/${name}"
>  command="/usr/sbin/daemon"
>  start_precmd="fcgiwrap_precmd"
> +start_postcmd="fcgiwrap_postcmd"
>  stop_postcmd="fcgiwrap_cleansocket"
>
>  load_rc_config $name
> @@ -86,6 +112,9 @@ load_rc_config $name
>  fcgiwrap_enable=${fcgiwrap_enable:-"NO"}
>  fcgiwrap_user=${fcgiwrap_user:-"root"}
>  fcgiwrap_socket=${fcgiwrap_socket:-"unix:/var/run/fcgiwrap/fcgiwrap.sock"}
> +fcgiwrap_socket_mode=${fcgiwrap_socket_mode:-"0755"}
> +fcgiwrap_socket_owner=${fcgiwrap_socket_owner:-"root"}
> +fcgiwrap_socket_group=${fcgiwrap_socket_group:-"wheel"}
>
>  # This handles profile specific vars.
>  if [ -n "$2" ]; then
> @@ -96,6 +125,9 @@ if [ -n "$2" ]; then
> eval 
> fcgiwrap_fib="\${fcgiwrap_${profile}_fib:-${fcgiwrap_fib}}"
> eval 
> fcgiwrap_user="\${fcgiwrap_${profile}_user:-${fcgiwrap_user}}"
> eval fcgiwrap_socket="\${fcgiwrap_${profile}_socket:?}"
> +   eval 
> fcgiwrap_socket_mode="\${fcgiwrap_${profile}_socket_mode:-${fcgiwrap_socket_mode}}"
> +   eval 
> fcgiwrap_socket_owner="\${fcgiwrap_${profile}_socket_owner:-${fcgiwrap_socket_owner}}"
> +   eval 
> 

Re: portsnap temporary files

[Xin LI]

Because the files are still being used?  What makes you believe they are
unused, by the way?

On Fri, Jan 6, 2017 at 3:34 PM, Dave Horsfall  wrote:

> (Many responses)
>
> I note that no-one has answered the question which caused me to post the
> message in the first place viz: why weren't the files being removed
> automatically?  Everyone appears to have missed this point...
>
> --
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
> suffer."
> ___
> 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"
>
___
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: Welcome to our new portmgr members

[Xin LI]

Congratulations Adam and Mark!

On Thu, Dec 22, 2016 at 4:04 AM, René Ladan  wrote:

> Hello,
>
> last week the Ports Management Team (portmgr) gained two new members:
> Adam Weinberger (adamw@) and Mark Felder (feld@). Both have been a ports
> committer for many years and Mark is also quite active on the Ports
> Security Team.
>
> Yours truly has also been promoted to a full member.
>
> Please join me in welcoming Adam and Mark.
>
> René
> with portmgr-secretary hat
>
>
___
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: ec2-eu-west-1.portsnap.freebsd.org is not up to date

[Xin Li]

On 9/5/16 13:19, Henk van Oers wrote:
> 
> On Mon, 5 Sep 2016, Martin Waschb?sch wrote:
>>> Am 05.09.2016 um 09:44 schrieb Henk van Oers :
>>>
>>>
>>> The portsnap.FreeBSD.org on IP-nr 46.137.83.240
>>> is not serving updates anymore.
>>>
>>> What other server can I use?
>>
>> The list of mirrors is updated by portsnap and stored in
>> /var/db/portsnap/serverlist
> 
> Ah, thanks for the pointer.
> 
>> You can try any of them to see if they respond...
> 
> Mmmm: ""Latest snapshot on server matches what we already have.""
> 
> Maybe the feed to portsnap.FreeBSD.org is down.
> I'll wait an other day.

Please try again, this should have been fixed now (the outage was
related to the monthly update, which is unknown to the builder itself
and makes it to refrain from doing further update and required a manual
intervention).

Cheers,



signature.asc
Description: OpenPGP digital signature

Re: base components should always be default (Re: change in default openssl coming)

[Xin Li]

On 7/8/16 12:20, Grzegorz Junka wrote:
> 
> The only reason I heard why base isn't updated with the proper package
> from ports is because of security implications. Older versions are more
> security-tested and therefore safer. If there is a vulnerability in the
> base it's much more hassle to update the base than ports.

Not necessarily safer -- for instance on FreeBSD 9.x the base system
OpenSSL is EoL'ed by upstream, and therefore the security fixes are
backported by secteam@ in a case-by-case manner.  Generally speaking,
newer code is safer and supports newer standards, and we recommend ALL
users who are still on FreeBSD 9.x to use port version of OpenSSL.

The only possible problem with defaulting to port OpenSSL that I can
think of is some DLL hell style issue.  If a base system library links
against OpenSSL, then gets linked into port binary which links to port
OpenSSL, we may see problems.  For instance, some utilities depends on
libarchive, libarchive depends on libcrypto (OpenSSL).  If it loads a
OpenLDAP client (i.e. through a NSS module), that depends on port
version of libcrypto, there _may_ be problems.

Cheers,



signature.asc
Description: OpenPGP digital signature

Re: package version scheme

[Xin Li]

On 09/01/15 14:11, Larry Rosenman wrote:
> On 2015-09-01 16:08, Xin Li wrote:
[...]
> I, as sysutils/lsof maintainer, depend on the behavior you see (the >).
> 
> Vic Abell uses the letters as "fixup" releases, until a full release,
> for example;
> 
> 4.89A -> 4.89B -> 4.89C -> 4.89 -> 4.90A -> 4.90B -> 4.90

Yes (note that this is not what I have seen, but what I expect and
documented in the porters' handbook).  For instance:

$ pkg version -t 4.89A 4.89
>
$ pkg version -t 4.89a 4.89
>

Cheers,
-- 
Xin LI <delp...@delphij.net>https://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die



signature.asc
Description: OpenPGP digital signature

Re: package version scheme

[Xin Li]

On 09/01/15 14:16, Xin Li wrote:
> On 09/01/15 14:11, Larry Rosenman wrote:
>> On 2015-09-01 16:08, Xin Li wrote:
> [...]
>> I, as sysutils/lsof maintainer, depend on the behavior you see (the >).
>>
>> Vic Abell uses the letters as "fixup" releases, until a full release,
>> for example;
>>
>> 4.89A -> 4.89B -> 4.89C -> 4.89 -> 4.90A -> 4.90B -> 4.90
> 
> Yes (note that this is not what I have seen, but what I expect and
> documented in the porters' handbook).  For instance:
> 
> $ pkg version -t 4.89A 4.89
>>
> $ pkg version -t 4.89a 4.89

Sorry I misread your email.  Yes, the behavior of DISTVERSION ->
PORTVERSION derivation was correct for lsof case, and the . in porters'
handbook is for this exact usage.

Cheers,
-- 
Xin LI <delp...@delphij.net>https://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die



signature.asc
Description: OpenPGP digital signature

package version scheme

[Xin Li]

Hi,

I hit a conflict between pkg behavior and the Porters' handbook, it
confused me.

In this example:

https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-distfiles.html#idp59327440

The handbook suggested that the right PORTVERSION should be 0.7.1.d if
DISTVERSION is 0.7.1d.

However, pkg version -t 0.7.1 0.7.1.d gives me >, suggesting that 0.7.1
-> 0.7.1.d would be considered as a downgrade.

I'm asking mainly because www/dokuwiki's upstream have a habit of using
a letter to denote patchlevel, for instance, 20150810a means first
service pack of 20150810, so it's expected to be greater.

pkg version -t 20150810 20150810a gives me '<', which is pretty much
what I'm expecting, but this sounds wrong based on my previous
experience with package tools and the porters handbook.

Could you please clarify what would be the correct approach?  For now
I'm going to continue using PORTREVISION for this port as it's done
historically.

Thanks in advance!

Cheers,
-- 
Xin LI <delp...@delphij.net>https://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die



signature.asc
Description: OpenPGP digital signature

Re: please merge www/speedtest-mini quarterly

[Xin Li]

On 8/27/15 19:54, Koichiro IWAO wrote:
 Hi,
 
 I'm receiving notification of distfile checksum mismatch from pkg-fallout.
 This is already fixed at head. Please apply the fix to quarterly.

It's done now (r395451), thanks for pointing this out.

Is there any specific reason that the upstream are not willing to use
versioned distfiles?  It could be challenging for those who have never
installed this to figure out what have been changed, etc.

Cheers,



signature.asc
Description: OpenPGP digital signature

Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 08/07/15 08:50, Jamie Landeg-Jones wrote:
 Xin Li delp...@delphij.net wrote:
 
 On 8/6/15 22:24, Kevin Oberman wrote:
 Or the code in portsnap could be modified to get the current 
 running version.
 
 I thought about this today but it won't work as advertised:
 someone (currently me) still have to tweak the portsnap builder
 configuration to announce new major version (9, 10, 11 now, and
 we would need 12 when 11.0-STABLE appears).  However,
 freebsd-update or mergemaster would take care for this.
 
 I was going to suggest this too. Isn't this information available 
 using /bin/freebsd-version -u ?

Client side: yes.

Server side: someone has to tell the server to start building for new
- -CURRENT or stop building for old -STABLE.

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.1.6 (FreeBSD)

iQIcBAEBCgAGBQJVxNcgAAoJEJW2GBstM+ns2HQP/iQfmSjJ853Aj4Bs+0qed7Ya
UoE4LDaX1PJSIpqswyWir34mSgqZ5jHC8wuEkNrT3dlXaSnuxBmjvZfm23T/AUFH
9b/ytjJGlZWT0Db88AOnIeiMKKKX786m9mkDxiY2C747Q0L+KqLzQx6Ltrgl7DEm
9arRlB3nQcix9u7badVgP+B3CRfspUwtqmL9m+4LFIlJQA3OPsMxySdKoJlCQD8H
E1rJNV/6NOxIIX2Y+/6EBhtNnhQwbXyKT74B/4UKFaGNaKfw7XIjB5T4yGBaWhPL
4VXqzDRU2g0YGY8VM3/uXA3AfSVuVYi9kmm2R3W/91TFwOVqGH31OQQczeK78Gpn
dx8+kOfC7OLGWaQ9Xb9H3bNcPUknRuUVusb4+Wbe8qXk5cWfeyIJLTK7GC4Vvq4i
dGf+rYpEMls/0t+W+6e1re+XTlZtgepLfWQMuuhCbOQf8egKktClbJ++Th6krc1B
Aob62BmfgNgq4mS8t21Ee2heBTTrjNwp+openjPv9+ffvhmDngshNrdp+z4umQ3G
uryURepM9YYmrRWVmD9ZOei81R2QIpzdFh/Xv4w8bwTAoiV3oJfNIavbJWuhsEsk
sAKU2Kk0oBiTDwOqe4ZEVfF1HWbOZe6X6gBWjwO0f/RG7Rtn9pexU9TRzBL1SmeE
qUix6Wbx6VfCB+7QiQgg
=LDxP
-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: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512



On 8/6/15 22:24, Kevin Oberman wrote:
 Or the code in portsnap could be modified to get the current
 running version.

I thought about this today but it won't work as advertised: someone
(currently me) still have to tweak the portsnap builder configuration
to announce new major version (9, 10, 11 now, and we would need 12
when 11.0-STABLE appears).  However, freebsd-update or mergemaster
would take care for this.

Cheers,
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJVxEYEAAoJEJW2GBstM+ns6wkP/AoQS/GX6RfJ0r5KBzHJzo1Z
1sFGkqULBYbiS4DNV8Svt1+mMdg0IwK7t5vYhkiQI/RrkeddvU1btDiVPjNGbC3K
Wm5wKAD2uMRLczz9EhKCZehDRq88ckvUMefPdT5R3b+DTo4VKdCXoPC4AqZnu7bb
60wnOL6cyKw8fwKTHhVyui6zcbg9uj7VtGj9MGK+03jHDmekJ6sXZO/0fp/TGju6
ruPVf9yImi9o/T5IUaKlj2D3xfDtwEhjI7Q96K4C5y88Tl5+PXQBh/07SQOKIu59
nalLbAH8eoxITWEAOBFjM/e1KOLH5Hyk+TfR0GXDZVLyL4mi8eIpch0eLFHp3e94
PEbsE1lUN3R3/4IFTmPDj1WYF9dE/AUgV4gzQKBboieVYNLfuL/esI0VOCFa/3r3
3rSW9RAj8MOH3GA3un14eUrWg5prvDcjMq9cJUO5Pebc3cD0CxlKCJ+yNAMlTo4Q
07u8dxBXsZcO//xknW5Gx9rKl+fJxvwy2klLmsiR3+bM2PCd1bt4bvSkOTgv1ZOt
qJZ4g/sDpF2jx3UYj2PF5vnBLkI6RrWer379q8ZqAwVRGE4Z9glnzo9BNUpQoQDy
PXzf3Nsj/qWkvnXXIWxI71rLTsKNejiXpBiYYjZV2eYz9dCveNJEMRFmHQ+xthHz
VrdB3J9EBHa17p5Xlt2y
=nN8J
-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

Proposal: make portsnap generate INDEX-${OSREL:R} only by default

[Xin Li]

Hi,

Currently the default portsnap.conf would generate INDEX-11, INDEX-10
and INDEX-9.  The INDEX file is only used for searching ports, and only
one (INDEX-${OSREL:R}) file is actually used.

Traditionally, we create all supported INDEX-* files by default, but the
only users who would benefit from this default are the ones who shares
ports tree across many systems that runs different FreeBSD releases.
 And even in these scenario, it's likely that they would still want to
tweak the configuration, as we may be creating more than needed INDEX-*
files.

So for simplicity and to reduce cycles wasted on everyone's system, I'd
propose the attached change to head/'s portsnap.conf and similar changes
to stable/9 and stable/10's portsnap.conf so that only INDEX-${OSREL:R}
is created by default.  Users who want additional INDEX files can
uncomment the corresponding lines.

Any objections/concerns?  I'll commit the change if no objection is
raised in a week.

Cheers,
-- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
Index: etc/portsnap.conf
===
--- etc/portsnap.conf	(revision 286392)
+++ etc/portsnap.conf	(working copy)
@@ -30,6 +30,6 @@
 # REFUSE korean polish portuguese russian ukrainian vietnamese
 
 # List of INDEX files to build and the DESCRIBE file to use for each
-INDEX INDEX-9 DESCRIBE.9
-INDEX INDEX-10 DESCRIBE.10
+#INDEX INDEX-9 DESCRIBE.9
+#INDEX INDEX-10 DESCRIBE.10
 INDEX INDEX-11 DESCRIBE.11


signature.asc
Description: OpenPGP digital signature

Re: Any ports that download whole trees with git?

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 06/16/15 16:33, kpn...@pobox.com wrote:
 Are there any ports that download entire source trees using git?
 
 I'm looking at doing a port, but the only source for the source is 
 a tree in git. Are there any examples I can crib from?

You would have to export the tree and upload it to somewhere that can
host it if it's not already done by the Git service provider.

For instance, services like github already have download services when
a tag or SHA1 hash is specified, see code blocks related to USE_GITHUB
in ports/Mk/bsd.sites.mk for additional details.

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.1.5 (FreeBSD)

iQIcBAEBCgAGBQJVgLdPAAoJEJW2GBstM+nsTekP/1dXjiUZKMsNIVbSn3zCXMcP
bk0hwOaoxv33uNDt5+q9g9DOv6mPwWJjAsEHFvwqaN40jUP9cPcJfvWjcLMac2RP
KHzVJkJhvm1Lcitwb5izWQnyQAOJOYErfirZKoI9/pM6D7ny6q6h84bEPgzY7YNZ
ythV4lJ0IahzOoeNxaKfvCohxaI2DOy90ffy/7RwQi/dlPHPuheUMINt42hCGNQe
x50Yviydd7cXn+kD+TZkyE/yR7NSXlKk97xTTbNQs398V5dYeePwCYHv+etQWege
k/O99cY95iofMZkSwyxNzWOHEEPr8bNwZsdSo9dESkrs13OPMJAKr1frWYfazcU9
Rd/VUWbH5BOqdAiWoATz6KDyV4XTXAEhzF36W9iSYcqIYoiIqEk3/XzKaFLUF85r
KWDZwOk0lAIhvtt+i7r0oMe+Ge3BAeaxH3UwbeTac5E6TcnG2A80peOUCNf6bxPz
5LxzVwfwwgSzsMEUxNkWL3mIIkZjtElJL4TYSHaJG1KJwtEY8wZEqEeyWRoi0nkK
g2RbuNvDPIimPAbpQEw6aEUH6SXBGnXoQLaIB0ZJ7Taa3zMCATvo6kCRaeddY69Y
f8YmBKSBCVKC0Ym8EUqI5nQ47/Ff8Zqo5oEAbp2K13OfgiHJtNFlbNv6AkVllAXm
jEdq63B1wmRIuajOK+dQ
=AE9K
-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: OpenSSL Security Advisory [11 Jun 2015]

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 06/11/15 16:34, Michelle Sullivan wrote:
 Roger Marquis wrote:
 The ports-secteam knows about this but posting here in case
 someone wants to update ahead of the port, from this morning's
 Hackernews:
 
 https://www.openssl.org/news/secadv_20150611.txt
 
 
 *wonders how this will affect 8.x  9.x* (seems to be no fix for
 0.9.8 which 8.4 and 9.3 has 0.9.8zd in base - i expect 8.4 to get
 ignored as it EoLs on Jun 30, 2015, but 9.3 EoLs on Dec 31, 2016)

Well, by supported we mean supported at least up until the EoL date
and they will never be dropped before that date.

Actually we are working on the update right now (first round of tests
done, patches going to build and writing advisories, etc.) so it would
be out sometime today or tomorrow.

Additionally we are considering issuing another EN for all supported
releases at a later time to do a full upgrade after the current batch
of -STABLE OpenSSL upgrades gets enough exposure.

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.1.4 (FreeBSD)

iQIcBAEBCgAGBQJVeixMAAoJEJW2GBstM+nslxIP/jh1wWjo6KSqhjwdkoKIfqix
FHR+xT+FduFjMvku84TaOIBI+EgyBetnOIT9Lovg8BhUvFqGQh+bN5KleRiUjpPf
vees9pvZ/r0GmpJfDbKX3kbTc+QfumO7W2yu8xaPeL4UJIo7OnzUmmcfjbWHvfLk
W7MaLUA3NR1I1H6YBNCydaPOafDqk1SjUuZTN4jrgSWPAeRA8TWKnx0Cd62VN3u/
0a0pMDFJmEMZodKcfsleZA2TrtSX4SC8xqQVxB8Rg5+YKahb1dOJC3+im1DqN9tM
4xuDvDLzEw/ilWIVIa0EyIxwW+8eIhKFgSr7a6hj+anBxkFYzsMClRdzJc7snQtQ
QfscsxXbH4rx2zW1IvT+UrLUUlpdRjp77BR1nSTZ7voKRSQf46bTWduaZfK2SIe9
SUxMazajJtzV6ovgRGQWOhBhAD3hU95Yt4lWAW0HOcf40Wzp/ZKslpA5pP7a00KS
101eQ5AaAax44GcN5sY/dzvbmw9NLtBK4r9w2e6GsDUYiOXEPRLr3G4NExU2J85m
Ke2ktTPKjc2mhq9P4T2hjgqHrJB36SBr7Nu7FXAVHDTG7wQVO+a5CUpq6toA7c4f
AKhg+3pb8A8V35i4rEbMEo+Grdj0nMiGXafYEBRGYo+YKKmboxY9PYnary2wOpz5
J5Gm6w/kfxKUHfFjx7FJ
=oJDs
-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: no dedicated maintainer for cups-base?

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 06/08/15 22:28, Paul Beard wrote:
 Having some weird issues that may not be worth tackling otherwise.
 Something hosed up between avahi and encryption/authentication for
 wireless/AirPrint printing that I can’t work out. It used to work.
 
Unfortunately it seems there is no one showing the willingness of
maintaining it, and the port version is pretty old.  I have done a
drive by commit today because there is a security release, which
have received some limited testing in during the past week with the
previous release (2.0.2) against various dependencies, and you may
want to check it out.

BTW.  Is there any specific reason that you using avahi and not
mDNSresponder?

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.1.4 (FreeBSD)

iQIcBAEBCgAGBQJVd3cPAAoJEJW2GBstM+nso2oQAKdzRVVbwU2Bd+8/kPSk7hVx
ZdSPSgaZqL0zNu5uwRMgo/oWKOtBV7kupF6MjcVfvgJ684EZAKNPhYhSIz3MS8VD
ePaDDdvqGtsLj8SpTXKe+uKU7SzrOQhiOkO+R043rAURpjj0U3pHzkuHchRh/yvG
cgSntI/oN8/5kHpvJiAzn0rcHbkw4VkfUS+pZBdoznW3L2HaEUW3nGYgJZLXYF/3
j18d+cjmslQ+U8m0nc0iPTtyFX7Md2QAwpYHOwKA2XSeLKyzewIXEJdaB5paZtVk
qvPR7i7k5AQhvJdUy6Vm/axmzOQ68yTIj2bcmOti9N7nga+Zg9PbBDfZophhHcrH
JNoilGeCKBLYp2RzHzlNMSwAky3VGWC/wZm/U6j3nmYjHN8zUTAwHtZxAjy7zivO
vraxPZ5JAKxbowf2EtQtPRvnS61tZxKCO3e3NWDmWdWPFVpPSIC9AcH0wi/hbzvA
cRFAVWN6f3TryGgAaJRlAxnYsCTjDgpjfdzx/aSMejN/ec5JHLmc8kbzgSzvUO8Q
ZwRl2RkqnVcliL1fGtc8hmIClgtbnkLL88qP0CKCJDga2cR3MUJ6enoRsHXCI5tN
AKUHvvalywupocujCyDP/mJIJmayLmIkH/E9PKPsJG2dTybaGBrVcXv7Kw26reM/
SHqk1/Z6fzeDVg3HyrP8
=TB99
-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: no dedicated maintainer for cups-base?

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512



On 6/9/15 21:47, Paul Beard wrote:
 
 On Jun 9, 2015, at 4:30 PM, Xin Li delp...@delphij.net 
 mailto:delp...@delphij.net wrote:
 
 BTW.  Is there any specific reason that you using avahi and not 
 mDNSresponder?
 
 How’s this?
[...]
 cc -L../cgi-bin -L../cups -L../filter -L../ppdc -L../scheduler 
 -L/usr/local/lib  -Wl,-R/usr/local/lib  -fPIE -pie -Wall
 -Wno-format-y2k -Wunused -fPIC -Os -g -fstack-protector -o
 ippserver ippserver.o ../cups/libcups.a \ -lssl -lcrypto -ldns_sd
 -lpthread -lm -lcrypt -lssp_nonshared -liconv

This is mDNSresponder library

 -lz -lz ../cups/libcups.a(http-support.o)(.text+0x6a9): In
 function `http_client_cb': 
 /usr/ports/print/cups-client/work/cups-1.7.3/cups/http-support.c:1871:

 
undefined reference to `avahi_simple_poll_quit'
 ../cups/libcups.a(http-support.o)(.text+0x12b7): In function

And avahi...   I'm confused, the first thing I would look at would be
if your cups-client is built with Avahi, but the cups-base built with
mDNSresponder?  Can you confirm?

Cheers,
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJVd8t8AAoJEJW2GBstM+nsC28P/iduVGwTnPSlBGbwfCJAmIop
UUsYYX4veYwJH5aQyoxzYr6LCyM/VHsEQHojqO2c6jDTkkTaIblH6tqlZnTPPi0v
gNVTLiE9xmWCJsIwhavpx+QgEGPFdDvJRRR2sdqIUI0Siwmh7rDUoh3GmJbPthFL
a6HNhupzJD9W6HsOyvgr6dusn6A7WjAdZQGVi+g8iwfUg28iXO3HHthm2LKSjsb2
gd/6uLHN57nI9yoM6moIvMXMlZwKWMqjT9QyOqk9zgvwjx/RdPB6mFR9X4iftNWf
GCuv9tv2amvQhOawO691ve/PMvH2sHI38atLWBTj5cj+RYrKLwCUwuXY520yS6uW
dLK99vipUHyFpK9MGlWhXcE759+MGHqpvgYjz/whNJjXXr1vBX6Jw9sN26RkX/MY
URnb+SFkTVQD3nSOwWn67S0FiCFcW7tIFwXtgO53wkR1KWTef6Hp/Xr4SteoMsp2
qgLg9kdf6F2kyqhYe+I8LY9ltHDHTqSXaC6Psv71p9b6a3L+dzsluKhjAmDq/2lX
vgALdABf2tz7K0J3VxefGFNJTSgcfNLfV92lqjDDV8j5qzj6/pFXkbXc7CyImLVI
0WxHcjJO5DChzDObawWIS84F9rHrH86EjYodEiUuDSVMFHlaTJnhA4RU8nUoS3K1
3VYPKNa8reW8hb/TuGj8
=RI3O
-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: Port Fetch Failing

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 06/01/15 16:33, Tim Daneliuk wrote:
 Recently, I switched a web server here to to rewriting and force
 every access to go over https.   This is a machine using
 self-signed certs and a fairly conservative set of protocol
 support.  Apache's cipher suite is set to this:
 
 SSLCipherSuite
 ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+EXP:+eNULL:-SSLv3:-SSLv
2

  These settings were derived from doing some reading and testing
 with SSL Labs test site and - thus far - I have seen no complaints
 except from the FreeBSD ports fetch.  I am getting grumpy emails
 from the master ports sites:
 
 = tsshbatch-1.212.tar.gz doesn't seem to exist in
 /portdistfiles/. = Attempting to fetch
 http://distcache.FreeBSD.org/ports-distfiles/tsshbatch-1.212.tar.gz

 
fetch:
http://distcache.FreeBSD.org/ports-distfiles/tsshbatch-1.212.tar.gz: Not
Found
 = Attempting to fetch
 http://www.tundraware.com/Software/tsshbatch/tsshbatch-1.212.tar.gz

 
72047:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert
handshake
failure:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_clnt.
c:593:
 fetch:
 http://www.tundraware.com/Software/tsshbatch/tsshbatch-1.212.tar.gz:
 Authentication error = Couldn't fetch it - please try to retrieve
 this = port manually into /portdistfiles/ and try again. ***
 [do-fetch] Error code 1
 
 Stop in /usr/ports/security/tsshbatch.
 
 
 Interestingly, (and strangely) no other port is reporting this
 problem, only this one.

You seem to be using FreeBSD 9.x which does not support TLSv1.1 and
TLSv1.2.  They support up to TLSv1 only and there is no plan to add
TLSv1.1+ support for FreeBSD 9.x base system as we can't upgrade
OpenSSL there due to ABI change.

Disabling SSLv3 ciphers means there would be no cipher available for
TLSv1 negotiation:

% openssl ciphers 'TLSv1:-SSLv3'
Error in cipher list
34379234072:error:1410D0B9:SSL routines:SSL_CTX_set_cipher_list:no
cipher
match:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ssl_lib.c:1
294:

So, no negotiation would succeed in this case.

I find your CipherSuite quite problematic, by the way.  Why do you
enable eNULL there for instance?

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.1.4 (FreeBSD)

iQIcBAEBCgAGBQJVbO64AAoJEJW2GBstM+nsVEQP+wZrco8vDXzLRcVJ6xVJ/exo
PGFJwW6EwllssPvgt7wtayCKtlNY4olnD/r4n6Z80B2VbfXiKtOYXGjv2BNc1Dys
/L1+fMV5TcGeO7lcUD19CO/WZf2Bqnmno/frWpV/6uCAwcIYhkY/JCEeist6HgNN
wrYInVAxbV062AZiD5GKgifjSSARUg819p3/QiQ00v+uGG5U9xMMQWDnkMCvY4Wu
xijiybU+OWI4EWeNQTQzNFXKP76A4ONs5YKeIgrWe4CXtSLgcJO1PE7k/OHxvrca
3IEsfyeXh7Z3yzcsREwAU47E/qfzd+K1Miya2Svt1yRi9oeBg6HpnXEh/WjcqLWe
0fEncBPfegFKvkuADewkDSL4V32+sG0rd2qRWLnsi9BGWzmtQ2pMo/nJkuuWU6Vm
H9Am8DGMr3u+In/v/DrwHdk5vQnjzxoseyPf8stttvk9QgEEWZRYSALAb0x1uw8q
c/5m3HXsMDe4O9w4iw5QzjFsG7eSXrbCqLkNOnrC34RCTBQiAOAtwa7+Jv9Xcwsp
ET+vXdJ76OoSBY9FHNLMKrJC0rfGzC704K90vvMeKlZxCZZzxrf4ZPe64mvuircI
2DJHdN+0TkxarrC+lx2dV8avSjtOvAn1XH/aq++tmX1zsMrsQ4BtHWxjz/phQ3Nf
Pn+BrSCIhn4hv0i5vTO8
=oL1C
-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: New pkg audit / vuln.xml failures (php55, unzoo)

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

On 5/23/15 09:14, Jason Unovitch wrote:
 On Sat, May 23, 2015 at 11:30 AM, Roger Marquis marq...@roble.com
 wrote:
 If you find a vulnerability such as a new CVE or mailing list 
 announcement please send it to the port maintainer and 
 ports-sect...@freebsd.org as quickly as possible.  They are
 whoefully understaffed and need our help.  Though freebsd.org
 indicates that security alerts should be sent to
 sect...@freebsd.org this is incorrect.  If the vulnerability is
 in a port or package send an alert to ports-secteam@ and NOT
 secteam@ as the secteam will generally not reply to your email or
 forward the alerts to ports-secteam.
 
 Roger
 
 
 I've attempted to knock out a couple of these over the past 2
 days. There's certainly a non-trivial amount of PRs stuck in
 Bugzilla that mention security or CVE that need some care and
 attention.  Here's a few that are now ready for the taking.
 
 vuxml patch ready: emulators/virtualbox-ose --
 https://bugs.freebsd.org/200311

I've added the information to the main entry and discarded virtualbox
specific text from Oracle.  Since Xen is also affected I have applied
the fix to xen-tools; the 2015Q2 branch version is not affected as
Dom0 support is not there so I haven't merged the change there.

 databases/cassandra -- https://bugs.freebsd.org/199091

Committed, thanks!  I've assigned the PR to the maintainer for the
port update.

 databases/cassandra2 -- https://bugs.freebsd.org/200414 (refers to 
 vuxml patch in PR 199091)

I've assigned the PR to the maintainer.

We should probably mark the above two ports as FORBIDDEN and/or
DEPRECATED.

 sysutils/py-salt -- https://bugs.freebsd.org/200172

This was already done by xmj@.  This one seems serious, can the fix be
backported or should the port merged to 2015Q2 branch?

 vuxml previously done and update patch ready: net/chrony --
 https://bugs.freebsd.org/199508

The vuxml entry was committed by jbeich@ and port updated by pi@.  I
think the update should be merged to quarterly branch.

 both vuxml and update patch ready: mail/davmail --
 https://bugs.freebsd.org/198297

This was done by pi@.  I think this fix should also go to 2015Q2 branch?

Thanks everyone working on these issues and thanks for taking time
preparing the patches.

Cheers,
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJVYYOGAAoJEJW2GBstM+nsmeoP+wVfw1Uw7YYGqhLXMEsFgQ/E
CtWD9LfDgia9ffQIANXi61nUKJ8ex0QZHEFborUMoUMGxPMic5fILFIsKY/FeaLq
Rq6jkVfHlelvHgi4XXf4v9u9JWFISu0jnYqafQiiOc4CK5a3d/JiouC9DJX74fau
jaDZ2snv4VjVnbZHwO35hWTQiN5iCJFt9bkdMV5iQkd/jU1waSDTVuzv9zstaVcQ
jJadqLCNX8ENhNwTZt0SbBBsRNL9mwRMEKbdYcCtxLJoKyQ+GYjbd5UEERajGSLv
H8TaO/wYIrMdeOMFjBe1ppNp+2mX8pn1AnxZx//N9am8dKhTiI+itV2FGonRluzs
aJJmzOHFYUSxwmSkyrcEm/XC0+BEAsTq24fxggJWNKFpD8brCd5ENt8oiA/uOkPR
fkCr1wG8dCW3OV2TYeiFW1XWGmA41J57wP/9WRRLmYTbBqUGTmLsNtnFT0KcdJwQ
G7tbd86xiHQjeF+Al1XAwL/9WgzIsrwjjQ7NO4737yNqvlAMyME30qtmCTwv1beX
3VQWqxJQ82FzI2x7OZgX5NAwyp0InaEI3j+cgTuJY5a6uMd49IMj+Wj+u3E52G/U
wTtp4D3FzaxH4ZCs9pxLM8glvmoCmH6E11+G/WPESFxOXbxw/mkjD+wus5HyCsa7
M7b0T5Y6hN425BmaPaeA
=tvL9
-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: LogJam exploit can force TLS down to 512 bytes, does it affect us? ?

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 05/20/15 14:40, Julian H. Stacey wrote:
 Hi secur...@freebsd.org

Please note that secur...@freebsd.org = sect...@freebsd.org.  Since
this is posted to ports@ which is public, I'm assuming it's not
intended to be in private.

 ( bcc'd a couple of friends)
 
 Refa: http://www.bbc.com/news/technology-32814309 (posted 5 hours
 before Wed May 20 23:01:22 CEST 2015) 
 http://www.theregister.co.uk/2015/05/20/logjam_impact/ 20 May 2015
 at 16:29
 
 Does it affect FreeBSD ?  If so, I guess security-officer@ will 
 already be drafting a notification; If not, might it be good PR 
 anyway to put out a brief summary / statement on a mail list or web
 page ?

Well, currently OpenSSL do accept weak DH so _arguably_ it does affect
FreeBSD, and it's likely to break existing applications if we enforce
such restrictions (namely, Java 6).

However, system administrator should always follow best practices,
like disabling export grade ciphers, use ECDHE and generate their own
DH parameters when they implemented PFS.

Recommended for system administrators:

1. Check if any of export grade cipher is enabled (here we used port
443, https as example, and it can be used for other TLS enabled
services).  This can be checked by doing:

openssl s_client -connect www.example.com:443 -cipher 'EXPORT'

If the connection was successful, then the server supports export
grade cipher should be disabled immediately.

2. Make sure that ECDHE is supported.

openssl s_client -connect www.example.com:443 -cipher 'ECDH'

And the connection should succeed.

3. Make sure you are using unique DH parameters, and configure it in
the server.

To generate a 2048-bit DH parameter and save as dhparams.pem:

openssl dhparam -out dhparams.pem 2048

The document at https://weakdh.org/sysadmin.html gives additional
information for individual daemons, including Apache (mod_ssl), nginx,
lighttpd, Tomcat, postfix, sendmail, dovecot and HAProxy.

I personally find Qualys SSL Labs' SSL/TLS Deployment Best Practices a
good reading, by the way.  It can be found at:

https://www.ssllabs.com/projects/best-practices/

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.1.4 (FreeBSD)

iQIcBAEBCgAGBQJVXQ83AAoJEJW2GBstM+nsrWMP/3ewU18rj/imD8s2ATtgWFMD
WmmaHgGyjqrVd8RyZBRIvsgPYlS2G0gPL2KP3GoeOeyU2dEkGEhvI4cvvpWoqUFW
rpY7AxtXQWOKRxY5PVtpU1siuczJ1Na/ypy28y1Dw0CGTf1Ul8rEzrent0kNsQ7b
NXD0hZojAhBiMO0XLb3bJqElviz11yDXPou1X12ZkueStP7DGquN081oLWZ4y8+j
19qSqdwkx8OsNLpnD9IUo5RoY5TvxNG53ZgDoGXwKWda8BnswRpDgSs3H2M/OKya
cKO7B9VWtIyJnbH5oVsv3VLi7o1n8weitGg1rWpKewZ1caiG+G1c9SmgAeSG1Egm
cuy4HV2btCxqSvLJRwAQ7Jbpc/SVnUTWZNrrI8YP7ug3/tzRTat0RpbdhxF3bqbM
hK8Pe2zpK6nIBNFhcoJ+CkhE3fW1IOEthSLBkJPgcb0U7mET0Z8kpWNLeJOuh5yJ
5o3ooLap+UtVlv25nQOODQecuNuvBFr0Mx67S4+jgmtUYqe9nFp1AjmPPvntN1GQ
sUzqMB7eAtSsxoQbHHGqF74zKk8BbfgqROUbEvcZ4kOsInN/GZ/iaPMUPu8KtieE
/ASdpwpxUfbZtu+Vs5fveWSiWmtiz3k1n7JzCWenXkLYW9KUn40fxv/mh7j76lYs
Am30LtLxtiZNw59cn2H6
=KtLx
-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: FreeBSD Port: pkg-1.5.2 - link error on FreeBSD 11.0-CURRENT r282802

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 05/14/15 17:46, David P. Discher wrote:
 Just setting up a poudriere builder for 11 (my 10-stable poudriere
 works great, with pkg 1.5.2 ) - and of course, pkg is the first
 thing to build, and I’m getting a link error.  Everything is
 standard, running GENERIC-NODEBUG kernel.

Is that head@r282808 or newer?  If not, please update the head/ jail
(this is a known issue that we are still working on, in short the
pkg-static needs to link against libmd).

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.1.2 (FreeBSD)

iQIcBAEBCgAGBQJVVURvAAoJEJW2GBstM+nsoQ0P/0vBQl6ENlb15Uc8olP2iLrx
VfusEsdiT/4R3vjDtK2T3tWKEcR5HbLlGJaPbvW4UDsjFugcRDUlDutPM3GhzZVP
WYkERC4pdEvjQDWKemDqUhjgu6pu15iax/SxFtftvoquCf/b/qcpZ6Cu2iilaI1V
FLNEerSuO56bJr4bYMYYRdWOp+D7Av4Fk/jbqBiru3dD/aSBT6Xg6vsG50d8v4/1
mbLC9WoIcLxvCeoHO7VvDtOS8dMygVuhzB9IC7vRvUQfTobzejSeQQKQsQhQnlEn
enkhFTEZ49Dt1u1je8NzL+dPm6t7WSNUA2Ml7OYCplcUa5fTcE9kF1B4TOEsgz4E
UtKnDe09cx6d138Zzl8TYjaRNIvVHRAzXUjsNEXxhAL4z9lwT/DNivE4a7jgKQjz
Cn9fGj7E2Q8k89gdF5CGoggLrVuLbQN8X2fmsTlIckRT4tpFmas3oMOSXlR2WzRF
SutWVqAzBeWgCAoxtIaKCbTpZdZDBCCyOjSrhfbVKVAnOESu+TJsMvc1VPaOigRY
FkicrMR2LNDvKNBFwpO2zRDCdIgexmQw5AeQ9fcB9WrO49lny2Wuckcnhe2UU0k9
/vAB6Ci989tHTBfSoFFRH+G7m9w0TsoNvXFGZcR9e0IRUkjTcpQIUiitaoqfqc6I
5OxUB0N2kRDBYfkB2HAS
=Jpnl
-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: Apache 2.2.7?

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 03/25/14 11:45, Matthias Andree wrote:
 Am 25.03.2014 19:22, schrieb Olli Hauer:
 
 The update is ready to push out but we have to wait for the
 official upstream announcement ...
 
 This is nonsense. The packages are downloadable, so is the
 changelog:
 
 http://apache.mirrors.lucidnetworks.net//httpd/CHANGES_2.2.27
 
 All the information is public. There is no reason to wait.

Technically it's only tagged but not yet released:

http://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x/STATUS

But no, I don't think we should wait, the tarball from Apache site
shows a good PGP signature from William A. Rowe, Jr. (9088F565) made
Thu Mar 13 13:47:45 2014 PDT, ~2 weeks ago.

Even if we don't want to take the risk of reroll, we should apply
r1576716 and r1576706 (probably also r1576709).

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (FreeBSD)

iQIcBAEBCgAGBQJTMdlVAAoJEJW2GBstM+nshzAP/2fl2b8Mq2zwQ3WAoHbnBi7s
E3W/5xFxbNa7lSdifP0bTc4sHGRnHIsxW9i+FC5ExpZK61MR8qjQVCJmZBwkO2u8
SHQix1iXzN0imI73TrEv08B4fgKkllSBFYL673lxciD0gr62XRP2Zv6X4KbafWmG
t1rHohD5tLHcYKB9stg5LQw1mEkLmcvDpllxr08GhLIUDz6nUJ9r0yvgUmSaauNd
GT0wd9PTXmY4D/0ZO2mGmrJYtoyW7RFocaHDSyasjJYs5R0+1pewhWmwnkR/TUtk
oXBxo/CxeUxULqVUQUBxU8k7+Y6poNKMRa9xZdhbZYqkedWgjP85Nh4qnooSqReZ
TPyOtk+GlpYhu3+p/luXXsZFHWYTYeKSwlTlE8J85HiRwUaIXPHSHDMwP3dZ61rD
25OmzrpJBwo9p9Crz9J1HQZuGzt2q1K5ZnOCeTWmW0z+hG14WB6DqCDuu7E2XMVu
hhPHcXShlqYdiFsfg8ZGfEQ6VxsgqX/eY5m75MEA8A5PyaTg5B/8ifzoKzjyHMkp
HN60JhfaqVbhHxSa/JgyRDm566hl37YsmgND5oPyoDgAGd4CMU0dhC5PQVHyMss5
7IKez35xBfgWbriO3c9rskH7AnQFaoBXS96y1FTw0jwWf9n/PXD0ZAg9MgLRIILJ
H4M1yjCY9KFqEZ0VtFIy
=0iEc
-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: Massive ports update?

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2/3/14, 9:59 PM, Nikola Pavlović wrote:
 Was there a *huge* update to ports tree tonight between around
 00:20 and 06:30 CET?  Portsnap just fetched 24720 patches (this is
 more or less every port I guess), but I can't find anything in 
 http://svnweb.freebsd.org/ports/head/ that would correspond to
 this. I'm a bit worried. :)

This may be related to my upgrade operation on the portsnap builder,
which happened around UTC midnight, right after a new snap snapshot
is taken.

I'll do a full tree audit just in case.

Cheers,

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJS8IcTAAoJEJW2GBstM+ns5p8P/ithwkITd4lodSXF+fU8BnWC
LmQ3i3wav6wpWEaAj9mN0OwrGYhGlxbwLW8uNCk1VjIGmyhf6aD3cjtWNI0ImHq9
GXqgIFpwk/fxTcvKSjkFQ4JPbWwqetUjMfveIxst2Pt8aqjrQfpUzRA61pvUs17m
99NOPxNkGQEqvx2AHqVOGKQHm/JJ+BHPSdSEd2IDKVZMlnXotJ8Jr/ctnZlR8A7d
RShG8GTIF8fQ6cki35p9KzKancdjk6YWdiCeMWTIwAOs4iePS2Smmd7h5M3xZ0HV
Akk9/6PtX3srcxrPPEhny9A0Ct68DOdSS3LpE51NcjaWkvUq8+foS+rzq4DwjFSu
OwXkF/prt4Xma7G6XsdSpCOuwaZs4Ux5PcMtFLkF0gJ6aS1VFfLXQdodHy2AEXtj
GRzIPlTrHtyVzqgNMfK41cA9FBpWggoW1ufCzwe5J0X09bWM6ZOiVBpuep9vHibp
jhj6hf4itcghOrCqCYrvM8cZmQZRPPU4NyoUElV1YpCz8cGteG5D3pfuLA6QOp/X
Dw1ZbnOqrHCqj9QDG0UES16D4sIHQKWK1aOGLEr0AvD2PJBdjoZiChtH/vGGOTGT
4UHa+tN/wNCiesHTWixexFeSmjtBfIH7o8wPwYqgZ64X4FBN0/SH4ykNAIWZ6dmx
HDuk70cVLqvmm8rlqDA9
=d5Wd
-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: Massive ports update?

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

On 2/3/14, 10:22 PM, Xin Li wrote:
 On 2/3/14, 9:59 PM, Nikola Pavlović wrote:
 Was there a *huge* update to ports tree tonight between around 
 00:20 and 06:30 CET?  Portsnap just fetched 24720 patches (this
 is more or less every port I guess), but I can't find anything
 in http://svnweb.freebsd.org/ports/head/ that would correspond
 to this. I'm a bit worried. :)
 
 This may be related to my upgrade operation on the portsnap
 builder, which happened around UTC midnight, right after a new
 snap snapshot is taken.
 
 I'll do a full tree audit just in case.

I've compared and can now confirm that the portsnap tree matches from
a SSH checkout of svn tree.

Cheers,
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJS8JLyAAoJEJW2GBstM+nsg30P/2yYn6l2Fj2UCVFZ21Ik6o4c
G7pfKRteqyeaBEIk/H+ue4z5qBhccTi0+zYcGyhahUh42P+TIhqroIvw2aD+psNS
aAfc9WTZ4z9Q8QhO2zw2hSwG5hHj8jaq+VBmHgAVxD75S+oY5BTTdH81UiVIfROy
xTF0Bn5Zz2aNrT7xXQmDIw+tBp4jHW5NRq7aIHtDTZpYB91bh7v/nN6qsxPciCHh
cw6s9AzeWZBZuovjU8ZWf5kehkYf+2kmd86NpfpD7wi/ifGzIJvmyOAItUV/J8il
PJPLpaR5gQmYU3aQqp/phX6u1j5VbxvVe+xY9xeCLuLA4+iXN587LBnTezNanTQA
qqUfbR/MYEh8ghTonbE7lA6be8zywy3Gy6hXPigJAhKEAzTXHC7WTvIuGx8j3LQ2
Jma3PXl+oWCYt7MXho9jechDwrMakLHjtjfRsaEwY3/VPtr17LupPvDogLoNeXBt
KbUoFGDsCkN8CrcryqToAFtjAFn6zMNB0Rh5KYDiBYAuCxtRDD961IGRmnRC9YNI
CP/UZgX3YvgiXpTWbPwx+3hpt7BmgB2np+BEdO/sE0ae7XpfzjOxzxOHXpHFdHwn
zT2eDRGvGlWNNGgghwITYWi7nAd+SuUEI5afTdw0tKH1IYSZmxA2c7Y0t8Q37jbI
0RQEG/Gk8C2UJ+Yf01WV
=IQQj
-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: ftp/curl: FAILURE due to configure: using CFLAGS: -DLDAP_DEPRECATED

[Xin LI]

I think someone have submitted a bsd.ldap.mk change to portmgr@ to
remove that DEPRECATED definition for a pointyhat build but I am not
sure what happen then.  Will ask.

Cheers,

On Thu, Aug 8, 2013 at 11:02 AM, O. Hartmann
ohart...@zedat.fu-berlin.de wrote:
 On several most recently update FreeBSD 10.0-CURRENT machines the
 update of port ftp/curl went smoothly, but on exactly one box the
 portbuild fails with a very strange error:

 [...]
 configure: using CFLAGS: -O2 -pipe -O3 -march=native -DLDAP_DEPRECATED
 -fno-strict-aliasing configure: CFLAGS error: CFLAGS may only be used
 to specify C compiler flags, not macro definitions. Use CPPFLAGS for:
 -DLDAP_DEPRECATED configure: error: Can not continue. Fix errors
 mentioned immediately above this line.
 [...]

 I haven't set -DLDAP_DEPRECATED nor in /etc/make.conf neither
 in /etc/src.conf nor can I find in /etc or //usr/local/etc any settings
 of such a flag for CFLAGS! I delete /usr/ports/Mk
 and /usr/ports/Templates and checked them out again via subversion, but
 this mysterious CFLAGS  setting is sticky like hell.

 How can I trace the settings of CFLAGS in the port?

 Since this happens on only one box,I guess it has to do with some
 settings in ports. I already tried to build curl via

 portmaster -f curl

 but that doesn't help much.

 Does anybody has any suggestions?


 Oliver



-- 
Xin LI delp...@delphij.net https://www.delphij.net/
FreeBSD - The Power to Serve! Live free or die
___
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

pkg_info -W equivalent in pkgng?

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Is there an equivalent of pkg_info -W with pkgng?  (Or let's say,
given a file /usr/local/bin/X, how do I find the corresponding package
that installs it?)

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJR//adAAoJEG80Jeu8UPuzsTUIALkvHHkxlpCcuBp4PRtCiC/U
AATOufv7E2uGUUbQCCWwx7JoQ2c7QpnxgIhMIVbcveFfoJ27Pik5Qfnmaip5ozCD
m6WKjk1OhJcDosshfpSU3nSJet5AeB501oFg9y31/3s+TDqZr+Cu9LFx85Ktyzhu
M7IObwY76XKUC/s1xU1SkEz4NO74afhoejnCQxMkCteYFZNEZGvToZH+ckLoqljZ
IyLpBSYZybooV9Ei29+qGIRnbmdR7uEcdzTiRjLKHPqDaotnbhxRYjiVcLHrHxZ2
U/hwmEO7RYbJa9fIfykZGKcrHTEigzeiR6VDqwGExR847XFZ70o/XsBbpl7PjZQ=
=2KHr
-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: FreeBSD Port: curl-7.24.0_3

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The maintainer have a patch submitted to portmgr@ for exp-run already,
and miwi@ is already working on it:

http://www.freebsd.org/cgi/query-pr.cgi?pr=172325

An exp-run is desirable because this change would touch many dependencies.

Since this have been brought up so many times, I have just committed
r322159 so users can install a patched version of curl without
recompiling everything for now.

Cheers,

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJR0oiuAAoJEG80Jeu8UPuzNJIIAKUq83TYK/RZTINBDyAUiPu1
jvAYe1gV2O06ac8jPWcvhGoLnDVKbJ8hflKvMK8rdkPp7DmgI9BdslcfVVRd5U17
E7x7dc4f5ZL0RPxgoX1hcfiszQeganLCeQSUSoi5jP2obBfZZk4KiopXSDETrtcH
M7d/FtLEnIKbl8kK5TM6885iMLRz/vyufN2AWCsG0F/MCGd8t4Umu0OCPo9u9BlE
Cf68i9X6vEM68uFlJolJv6XJw5/7dPu0MR7Tc+LTdvjIoFnNr/xkVh3Z5K7bPDP5
eDu4T7WARd6B80aV8wj2Tn7LA17EOkQPKoMw9RDy9vCitGoJhyuGNrJDHu//ZFI=
=2uy7
-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: Why was the ventrilo-server port removed?

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 06/04/13 14:34, Bob Willcox wrote:
 I just noticed that the port for audio/ventrilo-server has been
 removed.  The 'depricated because' reason says No more public
 distfiles, yet as far as I can tell the distfile for the freebsd
 version is still available from www.ventrilo.com. It requires a
 manual download as you have to accept the license agreement, but I
 don't think that has changed from when I first downloaded it.
 
 So, anyone know if there some other reason for its removal?

I think it's marked DEPRECATED in r317244 (bapt@) a month ago and then
removed.  Are you interested in maintaining the port?

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJRrngmAAoJEG80Jeu8UPuzyb0H/0PFf06OnOGrGQPmqByXigpW
O0duWPYr/M7pqAeFDxzpciVeEPnrn+SsWBvOUSwyjtk7dZcSIYlhI3ffT0dUU8co
kQFEOZmjaWL1ZjVAruaY3EkwcuKM4oqkUWXKspsDu9scFlKmdpX+YiQl6/8iXyfi
8abL2DJl9yes5fdGMgqIOZqotPM+Tzca5vnqoEVlRxUeLi8IeiCPfquUhHtYBPOd
kn1I+SDy+4rbq4soqcLx6NMUxfTp7DKxhVEnoaIB/AJhP7SBcLXY15LxF9iTlN/h
lU0rk6VtBOm7PhQKijZGESVT8jRIU7HIJzBoVxHxgZpiRsISe6DIcPW4QC6O6B4=
=0CNW
-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: CURRENT: system crashing while shuting down - files system corruption

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 05/24/13 06:50, O. Hartmann wrote:
 Since r250670 (last known stable) I face a lot of problems.
 
 On systems with SSD, after a couple of seconds the box is crashing
 and rebooting, showing up a lot of CAM/SCSI stuff on the console.
 
 A system with traditional disks I get while shutdown in progress
 (via ACPI power button or shutdown -p now command) corrupt
 filesystems (UFS disk).
 
 Below an error message after such a crahs, /usr/ports is a
 partition and while the shutdown was in effect, there were no
 activities on that partition, but is has been repaired while the
 box then powered up again. Now it seems to be corrupted in the way
 that I can not svn update the ports tree anymore.
 
 What happened?
 
 
 root@thor:/usr/ports # make update 
 --
 Updating /usr/ports using Subversion
 -- cd
 /usr/ports; /usr/local/bin/svn update svn: E155036: Please see the
 'svn upgrade' command svn: E155036: Working copy '/usr/ports' is an
 old development version (format 12); to upgrade it, use a format 18
 client, then use 'tools/dev/wc-ng/bump-to-19.py', then use the
 current client *** Error code 1

Have you tried 'svn upgrade' by chance?

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJRn+oaAAoJEG80Jeu8UPuzukkIAKadxoGeM+9QiJim5QIV6uWx
GgY2Doz04R3+Ow89IRCQdrrlgsG/lJkR7hV7XD9H4dfbD8Fkh1X79vnRcJ/CSSPg
OZu3FgVHE4CVVJZLMFv+4wM9VIPeGMVBV8wnbP2CcleqJlJWDoI4OUddHhEeOHoU
8qqjylxUUcvijWj6c4P3MZloiopE8L9mHZmyuhh85LYszr/2lRCPeFjXQh/b+9C0
RsC0fZoJtCr/X+8ekvj4SIGwOTIvyJyXCfeNaHEhlGFj86bjuEA3OIwG1UOMebMv
y9hTeNrso0eB32BDNOPqwpL6pxnTS7rKS2Wxp/16zb9Lh/Hiui8UILRhwwbPcy4=
=HGvA
-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: Proposal: do not show up the dialog(1) by default?

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 5/22/13 10:45 PM, Baptiste Daroussin wrote:
 hi,
 
 A lot of people seems to be complaining about the configuration
 dialog popping up all the time.
 
 What if we change the default behaviour to not pop up the dialog
 each time there is a changed option but only when the user
 explicitly type make config?
 
 Just a proposal, please give your opinion.
 
 Of course make config-recursive behaviour won't change.

I think this would be a good idea.  If the a majority of users need to
change default options, then the default should be changed.

Not really related to the dialog, but maybe, I mean maybe, we can
teach package tools to just go ahead download and install package, if
the options being chosen matches the package options, if the host
system meets certain criteria (e.g. is a supported release or
- -CURRENT) and the package is available?

Another idea is to collect the options from user, and send it as a
feedback (the user have reviewed the default and either accepted it,
or have changed).  This would help port maintainers to decide which
options should be made default, etc.

Cheers,

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJRnbkEAAoJEG80Jeu8UPuzMakH/A9nMM9Q+ndHEEikjaln/zlM
80xGdMqHMObk9nfoz8xY2xIMbTHdTox3FHtFwTEKEuQjGj9rRbMj16sSrPJG1V0Z
P/WtIxdBoR7E4ApHIvdE2qBnN3XLTGIDMsk71ZqWPV2z7jUlPkrsUs5sc0shNQkt
GcqYIv/teb0QHVlki++RlxYvh/OvFblXJ1K8GTSh0EZ+5LoFvxtuA1pas82BMSCL
otlA4kdNb2B6y/FjyRKZ3DULo+Lq95p216WiWKR7P89XidiKF/CJznRHEmC/XpvP
cm3v8lj4Vwr7Fp9cA5k/khAU/GBYYZMbQrY6yRuy9x7t6T0emuQbdPMeyX87KdE=
=74VA
-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: Portaudit claims nginx 1.2.x vulnerable

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi, Michael,

On 05/16/13 15:04, Michael Gmelin wrote:
 Hi,
 
 I just noticed that portaudit considers www/nginx =1.2.0,1
 1.4.1,1 to be affected by CVE-2013-2028, creating noise and
 preventing installation:
 
 http://portaudit.freebsd.org/efaa4071-b700-11e2-b1b9-f0def16c5c1b.html

  According to the announcement on the nginx mailing list, only
 versions of nginx = 1.3.9  1.4.1,1 should be affected:
 
 http://mailman.nginx.org/pipermail/nginx-announce/2013/000112.html 
 and the fix in nginx trac 
 http://trac.nginx.org/nginx/changeset/5189/nginx
 
 I just checked the source of 1.2.8 (the current version in ports, 
 www/nginx) and it doesn't even contain the affected functionality,
 nor the affected function implementing it (ngx_http_parse_chunked).
 This is in line with additional media and bugtracker coverage:
 
 https://bugzilla.redhat.com/show_bug.cgi?id=960605 
 http://www.openwall.com/lists/oss-security/2013/05/07/3 
 http://www.ehackingnews.com/2013/05/cve-2013-2028-buffer-overflow.html

 
http://www.h-online.com/open/news/item/NGINX-patches-major-security-flaw-1858438.html
 
 Long story short: I would kindly ask you to correct the entry in
 the portaudit database to match only affected versions of nginx.

I have took a look at these and found this:

http://mailman.nginx.org/pipermail/nginx-announce/2013/000114.html

I'll update the vuxml entry to include these information.

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJRlV9sAAoJEG80Jeu8UPuzmM4H/i66ifeXHOJX8cle5cf9ATXt
Y5G74TCLqLlxEv+1DCGh8Wks/JvN7KVsLNieXkf+jVonuXr4O5LCV7Pgj3SQ6EQK
TISbHwDDnwBqIvNncO4uZxOs6JbuTKWh43YdoPG7Rfpb0AJWJl/N8LFtxEckohyu
jWfyK6n1ftnjtaHoXZ63hF3daMHJwxtj8nJmHOqD1O7LbI+UCTPDwuYDb6BJGq9h
1JNt/NUyuANupRHftKa42+NLBa8zeGSggu7nYFhjuhcQN1ts31klKC/ReUIoUrTI
09+6Eu6AwpTvVa+rSRv6WUvLuG2srEKHS8zS+toFINAcY5EUO0zdqTglXGL8/E8=
=fQL9
-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: openldap-2.4.35: failed to start slapd

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 04/29/13 11:26, Jerry wrote:
 Thanks Matthew, I was wondering if I would have to rebuild the 
 database.

Yes, you do.  What I would recommend is that you do a slapcat before
everything, upgrade and move /var/db/openldap-data to
/var/db/openldap-data.old, copy the DB configuration to the new
openldap-data directory, then slapadd.

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJRfsXhAAoJEG80Jeu8UPuzjFEH/0SiOoibaFk5i6srAhoLSxwX
NnTvqRR+UwcKpsVymfH6dj7ubFuvwl6jv4+dH14pgndXtfCxuQPW0q9qIRlKv64g
LalxFdpv0+wOgj9Mp6JijCu1gZE3DoIx0VKSk3roTW5+s+eS5z8M1BeqEuGIAlWQ
pA45MEDA4lpNdNaSFQyEp0zx28JCRPYVaBWVsRebDDGsNTrcnxH188gxmPY51ICZ
hVvcMiOnynCtwwDB4TqzsAjCMCSTvrN/yAU2WXacjACVP+nS6Y0hW/z3X8r+2O8j
KyzAeTLrjsc/1g131MlMn9PFm2sFQoXEEbFawEPjHMLTLKf0+3H10NVIK31daY0=
=RXDa
-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: openldap-2.4.35: failed to start slapd

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 4/28/13 10:30 AM, Chris Rees wrote:
 On 28 April 2013 18:17, Jerry je...@seibercom.net wrote:
 On Sun, 28 Apr 2013 16:48:33 +0100 Chris Rees articulated:
 
 Have you tried getting the older version and installing that?
 
 Ports-mgmt/portdowngrade will help you do that.
 
 Not a proper solution, but it'll get it working again if
 you're desperate.
 
 Actually, the database log got corrupted. Even the db-recover
 would not correct it. Luckily, I had a semi-recent backup of the
 directory. I had to run  /usr/local/libexec/slapd via GDB to
 find out what the problem was. I have no idea what caused the
 corruption though. The only thing that comes to mind is that I
 DID NOT shut down openldap prior to updating it. That never
 caused a problem before though.
 
 I'm really glad you had backups.  I'd be surprised if the in-place 
 upgrade broke things, but it might cause a problem.  I've never had
 an issue with any daemons like that.
 
 Xin Li, do you know if corruption due to this is possible?  Would
 a @stopdaemon line be appropriate here?

This is weird.  We do have some similar construct for the server
package -- if the package is being removed, the daemon would be stopped.

I haven't seen similar issue in the past, what's the BDB version used
with OpenLDAP?

Cheers,

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJRfgRDAAoJEG80Jeu8UPuz3D0IAIVthtvgUOT2+jhyJ3I1uZXp
7xmvKQXUfHXHvsEmu8eLlkjWGaHjuPgE0Ssvap4nkl5NcEENw9YlIIrm8GDCwsC5
uPphCjLhR+RcX0Z6QOjaoHGR3hj29e1nG/Ei9O4pRxiHnPqJz+sZSbIyzrmaeb1v
BAl7df88vlE45e40WuCm9W6QPbaAPqXi9ZMzk9YN9crdB3YKvGMgZT89liS40zQN
uBNRE2sBXJUPhtqjEVE04o9QdIYYIuP9zNH1BFqup4XMybIxdrKCtYbW5iKfkDtB
6cRG014/YxhZRvgRvriaifP6SLXu6pTMIuuFWeC8MQn5uEz9mrczrB5RaHIgwPU=
=FQom
-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: non-destructive ports/packages update

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

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)?
 
 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.

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.

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.

BTW. Speaking for 8.1, it's past EoL, please consider upgrading to a
supported release.

Cheers,

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJRcjpRAAoJEG80Jeu8UPuzdjkIAICtMrOW87AWrtE+3FCGbG9d
4XOPZD6fgFw0eOJ4KpaxyW//e4wqILofyoLmpepYTkiZQG+fzQ8sdHLO6WNdqRo8
ilzpzwpmu3rAaI6YvPj90Oz5Er4Q+yGG1u/1jFfWPDpiWOtVlaYC3HdERqoSQCfo
NCfjEk6UYjRiRSGfw9qynf87WCinhi8su71+/A0RusuDHXeLQWkgfOPrTerm77KM
HBFXKg2F7DlLx9ZdXxv0Tk+8QwHSlYB249oC047MLx/dT0KBOfD2nWK1xhB4pDJo
RRbWKUmb0B/aT0FLLD/swWSbx/59menyHDJBG/ZMmxB58vAhSrkPXtu7SNOlZwU=
=OSk7
-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

Why portlint require MASTER_SITE to end with /?

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

While working on a project hosted at gitorious, I end up with
something like this:

MASTER_SITES=
https://gitorious.org/${GO_ACCOUNT}/${GO_PROJECT}/archive-tarball/${GO_TAGNAME}?dummy=
[...]
GO_ACCOUNT= mdb
GO_PROJECT= mdb
GO_TAGNAME= ${PORTNAME:U}_${PORTVERSION:S/./_/g}
FETCH_ARGS?=-o -  ${DISTDIR}/${DISTFILES}

However, portlint gives the following warning, which I think is wrong:

FATAL: Makefile: URL
https://gitorious.org/${GO_ACCOUNT}/${GO_PROJECT}/archive-tarball/${GO_TAGNAME}?dummy=;
should end with / or a group name (e.g. :something).

Can this be made a non-fatal one, or do we have better way to handle
gitorious source packages?

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-

iQEcBAEBCgAGBQJRPir9AAoJEG80Jeu8UPuzqwsH/1RjMZ7/qYlhM2f5vhydywmY
8nPb11SuNYNHLn99aKkScmrojGc30UmWccGb9KGYHshQyIjxAxJW+0Bm/86bA7UU
aK5cobispF61sOoIwAboBj7yNO6zeXx336L/kbd3LAEQ+nzmmKhqJ7jAtQKM0Sdk
C1tZOr0tDYMrbs4ylPQrBsk5SYrYTJbR6cUNKVg7cJxIUEq1h3MMRHjuZK3oGdFZ
7zjEdwuqoV+zqmLn450HAl3etw+8pt49o/rWoOZneSwaov+aNdOdONrO/5ka/Ri7
EfEkx+c17rE8Vc8DvlpGb6XuKINLYBH8tBnEQeWxFtIk43paJ5x7rS5Zz7SpGTc=
=pLZj
-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: FreeBSD Port: samba36-3.6.5

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 08/14/12 16:00, Michael wrote:
 Upgrade request samba to version samba36-3.6.7 because
 
 of bugfixes.
 
 
 
 * BUG 9057: Fix bugs in SMB2 credit handling code.
 
 * Fix resolving our own Domain Local groups (bug #9052).
 
 * Fix migrating printers while upgrading from 3.5.x (bug #9026).

A patch is available at:

http://www.freebsd.org/cgi/query-pr.cgi?pr=170446

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCAAGBQJQKtowAAoJEG80Jeu8UPuzd/0H/15NMkLLsq0V72Bsp7hEYPfq
6PHirur3oXGrAEKhK3qMNJZZTR0C+0o5dSEFGKa05JBtU+EQU0bV2curUJABL/8Y
K88QiOHh3Bl46VJ7/VyVCriC3LO5l67Lyu/kMkcvPdtkeERwVGtyf9E3eL1YVhxT
drMSqtxrJWVyFAiEoDQCbVoLwZmGJsiXD+XKxlBJjoKHfsKNcM1TSHCVQCgADjEX
M1CloMtl/fy+EIPq/H5bfDsqy92wL+sqrGHLaWNt1D1iX3qdZmP7TlWK1LXOTEet
5gasOHVFUcIsH7GU4WspOgirFMcJs17gcHZvSWOURgnGTBUV7BqOb4vYhpCF6GE=
=6dUF
-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: Right LICENSE* values for a GPLv2 port with a licensing exception

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 08/10/12 15:28, Raphael Kubo da Costa wrote:
 Hello there,
 
 I'm currently working on porting xsd [1], which is a GPLv2-licensed
 with an exception that allows the distribution of derivative works
 under other free software licenses.  The contents of this exception
 can be found in [2].
 
 In this case, how am I supposed to set the LICENSE* variables in
 the Makefile?  Should I use LICENSE_COMB=dual and consider FLOSSE a
 separate license that must be agreed to besides the GPLv2?
 
 [1] http://www.codesynthesis.com/projects/xsd/ [2]
 http://www.codesynthesis.com/projects/xsd/FLOSSE

Disclaimer: I am not a lawyer and this is only my personal understanding.

With the exception, it is possible to build and redistribute binaries
that e.g. statically links the xsd runtime library when using an
incompatible license (for example, GPLv3 licensed software as xsd is
GPLv2 only).

The exception text is ambiguous on what can be done because its
wording.  For instance, the ports tree is licensed under BSD license,
can that be _reasonably considered_ as a FLOSS base for other
applications and thus apply a BSD license to the software?

Therefore the exception sounds like a trap so I'd just say GPLv2 for
the LICENSE.  Downstream with incompatible license (e.g. GPLv3) who
distributes the code does not need this port anyway if they do follow
the exception.

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCAAGBQJQJZplAAoJEG80Jeu8UPuzlSwH/j2z7nUrfMuJ28f/omIUOEwo
s/19v4v5dSbWSEJSK4VGUyN9T8iSmyGgG5aiG4VjajFi/D4ev92TWRAYApnAbdk0
vF8vyHGoJrRCipRAMVuSIRgNhbcvrIYMFKEeGH5qahNI4Fuvc3mF7wQaZ7bv5ZiR
m0ePA+LJ8XMiMqf8qMoI0gzxzRy2NsSY25qSi/2BDy5XxsL10u4dobOXEnCNkklK
UhnESBOVxtZd+N80TOozBACYcUL22iNd22tmdNbh2KGzn7DSkSLBHwEekgSEBSq2
fYWtPWQZs2CbXPUSYkvfsXieakYGPP3LGKNfHQvEBszO5ISROoxsi0FC2xW06s4=
=A/US
-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: FreeBSD-SA-11:07.chroot and ProFTPD 1.3.3g

[Xin LI]

On Wed, Jan 4, 2012 at 2:18 AM, Henk van Oers h...@signature.nl wrote:

 Hi,

 My 7.4 is up to date and I have the latest proftpd

It's not.  Have you done a 'make buildworld' and 'make installworld'
after updating the source?  If yes then try another cvsup server and
report to the administrator.

 But still it's not working :(

 What can I do?
 Any hint welcome.

 -- henk

 FreeBSD dee.signature.nl 7.4-STABLE FreeBSD 7.4-STABLE #1: Wed Jan  4
 04:54:11 CET 2012     r...@bep.signature.nl:/usr/obj/usr/src/sys/BEP  i386

 BEP = GENERIC + IPFIREWALL_DEFAULT_TO_ACCEPT

 Jan  4 05:31:54 dee proftpd[22094]: 81.18.162.68 - ProFTPD 1.3.3g (maint)
 (built Wed Jan 4 2012 05:30:17 CET) standalone mode STARTUP
 Jan  4 05:32:21 dee proftpd[22131]: 81.18.162.68
 (81.18.162.68[81.18.162.68]) - error: FreeBSD with vulnerable chroot
 (FreeBSD-SA-11:07.chroot)
 Jan  4 05:32:21 dee proftpd[22131]: 81.18.162.68
 (81.18.162.68[81.18.162.68]) - chroot to '/home/henk' failed for user
 'henk': Operation not permitted
 Jan  4 05:32:21 dee proftpd[22131]: 81.18.162.68
 (81.18.162.68[81.18.162.68]) - error: unable to set default root directory

 ___
 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



-- 
Xin LI delp...@delphij.net https://www.delphij.net/
FreeBSD - The Power to Serve! Live free or die
___
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: FreeBSD-SA-11:07.chroot and ProFTPD 1.3.3g

[Xin Li]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

On 01/04/12 10:10, Henk van Oers wrote:
 
 On Wed, 4 Jan 2012, Xin LI wrote:
 On Wed, Jan 4, 2012 at 2:18 AM, Henk van Oers h...@signature.nl
 wrote:
 
 My 7.4 is up to date and I have the latest proftpd
 
 It's not.  Have you done a 'make buildworld' and 'make
 installworld' after updating the source?
 
 Yes, and 'ezjail-admin update -i' to 'installworld' in the jales 
 and 'ezjail-admin update -P' for the proftpd port in the jail.
 
 If yes then try another cvsup server and report to the
 administrator.
 
 diff stable-supfile~ stable-supfile 68c68  *default
 host=cvsup.nl.FreeBSD.org ---
 *default host=cvsup.de.FreeBSD.org
 
 
 But still it's not working :(

Could you please do:

grep __FreeBSD_libc_enter_restricted_mode /usr/lib/libc.so

And see if the output would be:

Binary file /usr/lib/libc.so matches

?

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8E/EsACgkQOfuToMruuMAE/gCfR9xV0yPKP3SF/7FuYChzf+ut
rT0An0O82shFe+/dDLCxlVjcKy7dBR6f
=i0lk
-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] lang/gcc -- Fix build on freebsd-current

[Xin LI]

Hi,

Actually you can add a dot (.) to these matches, e.g. freebsd[123]* -
freebsd[123].*, etc...  Have you contacted the maintainer
(ger...@freebsd.org) by the way?

Cheers,
-- 
Xin LI delp...@delphij.net https://www.delphij.net/
FreeBSD - The Power to Serve! Live free or die
___
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: Recent ports removal

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

(I just picked one message to do a reply-all, not specific to any one
single message but all of them).

Technically speaking the current approach's problem is that the user
might have no chance of seeing it before the port is removed.  By its
nature, deprecated ports tends not to be updated for long time, port
tools like portmaster, portupgrade will not even see it because no
PORTREVISION bump happen.  For users who install from packages, there
is no deprecation message at all, and it's pretty likely that these
user when updating to a new version suddenly find the software missing.

I think if we want to deprecate ports in a constant manner, we need to
do a better job of letting the user (or let's say potential
contributor) know it.  My own server in China have went offline for a
few months before my friend rebuild and install one for me, and I
suddenly noticed that some of previous ports maintained by someone
else have been marked as DEPRECATED because upstream gone.

Think about this: FreeBSD is not just a product, it's also a project
and a community.  It's never an overkill to do more things to keep
developers, contributors and potential contributors happy and continue
to contribute.  Making them happy is not do whatever they want us to
do but to think more about what they would think, and how we can
improve.

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (FreeBSD)

iQEcBAEBCAAGBQJOvZ5uAAoJEATO+BI/yjfBkxYIAKwfR3KRGr4l0AY1fV8Os0MR
+0GTUlOnTtaIybk81NcmLhyonSr1GsKAbqyAz5D9hsVFWdNOIeP6G/AnYRIak9Gs
ffrFCIN6WjiFmYORQVSTOl3noQmAC4E066vl2PceOUL8sHyHI6O85SuraY0noaVQ
p3AV58sQqIuUTpV4f3gPG1nFiDrJT1ZxtLANWjveSNNKDrdcalgjPtPbv1DUYPgp
10me7cVkqp5rrCs2fVUP92037x7XljAZjDi8AaEPf/LtV7Rb+IgC9bE1erk8u8w5
RHoWp2er6szTi70v3CUH7YI7WV31wpphBCY75w/kcvJ4FW1OmUOMjXksVfvLZo8=
=xhBR
-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 for ports on 10-current

[Xin LI]

On Mon, Oct 10, 2011 at 1:59 PM, Doug Barton do...@freebsd.org wrote:
 Until the pointy-haireds come up with a better solution, here is a patch
 that incorporates work that others have done into a manageable form so
 that those interested in working with ports on 10-current have some
 tools to work with:

 http://dougbarton.us/bam.patch

 You need to do the equivalent of 'portmaster -o devel/libtool-fixed
 libtool' to get the fixed version. In addition to the OSVERSION check I
 added knobs to selectively disable the 2 parts of the fix to aid in
 development and testing. Also, make sure that you have the latest
 /usr/share/mk/bsd.port.mk with the similar fix backed out.

 Hopefully there will be a better fix soon, but until there is, I hope
 that this helps.

Thanks!  This is better than nothing at very least.

(By the way Python seems to be using a different way of getting
FreeBSD version and for some reason that causes problem for certain
applications)

Cheers,
-- 
Xin LI delp...@delphij.net https://www.delphij.net/
FreeBSD - The Power to Serve! Live free or die
___
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: Instafix for FreeBSD ports brokenness on 10.0?

[Xin LI]

On Thu, Sep 29, 2011 at 1:47 AM, Ed Schouten e...@80386.nl wrote:
 Hi folks,

 Why can't we simply fix the entire ports tree at once by doing something
 like this?

 find ${WRKSRC} -type f \( -name config.libpath -o \
        -name config.rpath -o -name configure -o -name libtool.m4 \) \
        -exec sed -i 's/freebsd1\*)/SHOULDNOTMATCHANYTHING)/' {} +

 Just to be safe, we can only execute this when OSVERSION is 10.0.

This is not sufficient since some places it's freebsd[123],
freebsd[[123]], etc...

Cheers,
-- 
Xin LI delp...@delphij.net https://www.delphij.net/
FreeBSD - The Power to Serve! Live free or die
___
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: Shared libs problem with ports under 10-CURRENT

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 09/26/11 11:25, Chris Rees wrote:
 On 26 September 2011 11:55, Rainer Hurling rhur...@gwdg.de
 wrote:
 This morning I tried to upgrade my ports after installing the new
 10-CURRENT (amd64).
 
 Unfortunately now I am not able to build ports using shared
 libraries like ports/libXext any more. They only build .a and .la
 files, but not .so ones.
 
 Is it possible that there is something wrong now with libtool-2.4
 (or the linker /usr/bin/ld)?
 
 #libtool --features host: amd64-portbld-freebsd10.0 disable
 shared libraries enable static libraries
 
 
 Does anyone else observes this behaviour? I would really
 appreciate some help.
 
 
 Excerpt from libtool configure script:
 
 dgux*) archive_cmds='$LD -G -h $soname -o $lib $libobjs $deplibs
 $linker_flags' hardcode_libdir_flag_spec='-L$libdir' 
 hardcode_shlibpath_var=no ;;
 
 freebsd1*) ld_shlibs=no ;;
 
 # FreeBSD 2.2.[012] allows us to include c++rt0.o to get C++
 constructor # support.  Future versions do this automatically, but
 an explicit c++rt0.o # does not break anything, and helps
 significantly (at the cost of a little # extra space). 
 freebsd2.2*)
 
 I've mentioned this to an autotools member, who has offered to fix
 it fairly soon :)

I'm thinking this needs a full audit as well.  A lot of ports hardcode
knowledge about freebsd 1.x and mistakenly use 'freebsd1*' to match
them, due to copy of GNU autotools code.

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (FreeBSD)

iQEcBAEBCAAGBQJOgOfKAAoJEATO+BI/yjfB2+0IALXGpsdosAqZg5qzrFXfyJcx
aOX48azLOZSMcPiDU9jJfHzR2bseB0EWbeclWJ8kcC+A3tIkIwqFLiU5YB81pfi1
cy9f1ow0ZF4F/76Me2N1OtnzuexvcWRnL9EJ7Mk5TdIkWlp5uFtFP5QvIgcBDj25
ejgfSiZDO7xOHku1yvZvNYKwSc5MfGEHKeozeIGyRiSu3TUhB3f/dQ0lpbxLPXJC
IaDfefeNAARHUna5Hr8gJs8rGhy6fZoTiSm4NgDz5/yEiS/4dXr7E1mufooEsgtn
+7RQ0KvVycCfB/WjoxrCyIOvHWKbi5debcdS+ANBeW06su8nmuG78+dRT4l/q6w=
=nBye
-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: net/openldap24-server won't start after bdb5 upgrade

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 09/25/11 14:59, John Marshall wrote:
 If net/openldap24-server is built WITH_BDB_VER=5, the server will
 fail to load the bdb backend at startup and will fail.
 
  @(#) $OpenLDAP: slapd 2.4.26 (Sep 26 2011
 06:13:10) lt_dlopenext failed: (back_bdb) file not found config
 error processing cn=module{0},cn=config: olcModuleLoad handler
 exited with 1 slapd stopped. 
 
 This is because the port doesn't include the BDB backend in the
 build. The BDB backend is excluded from the build because the port
 doesn't recognize the new BDB version numbering now used in
 bsd.database.mk.
 
 About a month ago I submitted a simple patch to work around this
 but I guess the maintainer has been too busy to look at it.  I just
 got bitten again with the recent bdb 5.2.28 -- 5.2.36 upgrade and
 thought I'd mention it here.
 
 See ports/160270 for Makefile patch.

Oh actually I should have sent some email about this to BDB
maintainers but that never got sent (I've hit some issue that I can
not really solve without their help).  I've added them in Cc so maybe
they can chim in on this topic.

Basically the problem was I saw a drastic policy change beginning from
Berkeley DB 5.x and didn't know yet where we are going.  Long story
short, in the past we can specify specific version 47, 48 or
least version like 47+, or as compatibility shim (as I
understood), use 1 and 4 for base system bdb 1.85 or 40 (which
is actually databases/db4).

By the way, beginning from databases/db5, older Berkeley DB versions,
like 5.0.x, 5.1.x, is no longer provided by ports collection.  This
might be because 5.2.x's file format is backward compatible?

If we have decided NOT to support 5.0.x and 5.1.x at all, and intend
to have only BerkeleyDB 5.x, and future Berkeley DB releases, then
your patch might be good to have;

If, however, we still need to support older Berkeley 5.0.x and 5.1.x
series, I'd recommend that we deprecate using single digit version
numbers like 5 and use 52 or 50+ instead.  Using single digit
version numbers would require more logic in individual ports and is
doesn't seem a good idea...

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (FreeBSD)

iQEcBAEBCAAGBQJOgAvHAAoJEATO+BI/yjfBmR0H/iZ3KqEuRYM0k5ecck5v8dXJ
+RAKexu59aqkX/M9JKWuE/UFVRaYhD8qNtqC4Z4Hqxe22VR6TLVyBWqJVkA7KjFv
8QhrinfGG6SH1o/D1VfZjDQhnNzDqMnzbuj0zkjjIJc0u6+73UUA7+RMPnBWOyDF
qjSVOvKxsdTkMxEi/1RF1FGhNYFfnx7O9tGzvRu8RIERUwAn0Ec9Z8FX1gMmM3lA
1W0TPYCp92ey0MbYTvJibpzBt54IDG/ze2aOaSc82AG5tQ++CYcEeoO1fPq3ZB3v
a+H2QAtSzsN+PBoc9fkJ6hGLmLVIk8cyNXYnaNinmtLQsbwZeLv7oIqcyV0Sf7Y=
=2QEQ
-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: Thank you (for making the ports less boring).

[Xin LI]

On Thu, Sep 15, 2011 at 1:08 PM, Chris Rees utis...@gmail.com wrote:
 On 15 Sep 2011 20:52, Matthias Andree matthias.and...@gmx.de wrote:

 Am 15.09.2011 21:36, schrieb Łukasz Wąsikowski:

  BTW: You hate having a software update break your software. I hate when
  software updates turn off services on my servers. That's another thing
  portage do better - update won't turn off any service. You are supposed
  to restart services manually after doing etc-update. Speaking of which -
  another good idea worth adopting.

 Few ports stop services when getting deinstalled/upgraded, so it may be
 worth pinging the affected ports' maintainers about it.

 Really? I thought it was supposed to be standard behaviour- the @stopdaemon
 line in pkg-plist facilitates that.

While I totally understand why we do this, I have to say it's VERY
VERY annoying behavior especially when one upgrading a remote system
with multiple server daemon ports.  One have to watch the whole
process carefully and restart the daemon manually.

As part of symmetry, I think a reasonable behavior should be at least,
if pkg_delete kills the daemon, pkg_add or make install should start
it, and the user can optionally disable this behavior.

Cheers,
-- 
Xin LI delp...@delphij.net https://www.delphij.net/
FreeBSD - The Power to Serve! Live free or die
___
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: The cost of a source based package system

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 09/07/11 23:26, Erich Dollansky wrote:
 Hi,
 
 On Thursday 08 September 2011 11:53:28 Stefan Schaeckeler wrote:
 Hi all, please don't take this posting too serious. I was just 
 curious ...
 
 your are talking about a serious problem.
 
 Using source based ports is with almost 5 US cents 6.19 times
 (case 1 vs case 2a) or 1.73 times (case 1 vs case 2b) more
 expensive than using binary packages :)
 
 Yes, but:
 
 You are moving the cost from you to the the hosting companies. If 
 more people use packages, they will need more capacity to supply
 all the different variants.
 
 Does anybody know what takes more capacity? The sources or the 
 binaries? I would believe that the sources would take more space
 and bandwidth but the different variants of the binaries could be
 much bigger at the end.
 
 I remember some articles about the electricity bill Google gets
 every month. It is not that low.
 
 So, to paint a more complete picture, we must see both sides of
 the fence.
 
 To make matters worse, people like me do both. I upgrade via the 
 packages and then compile while I am already able to work with the 
 new ports. At least, if the packages worked.

Both portmaster and portupgrade have 'package' mode, which uses
packages when available.  If one can live with default optimization
(which is usually good anyways) and if most times the default options
would satisfy his/her need, or if the port doesn't provide any
options, binary packages would save a lot of time.

The real problem for FreeBSD's packaging system is, in my opinion, we
do not maintain branches and ports tree is a fast moving target,
making it impractical to build packages and push to mirrors.

My $0.02: It might be worthy to experiment a branched development
model and only pull up changes at a much lower pace to branch (e.g.
create a branch near a release and drop the branch after a few weeks
once a new one is created, and only pullup changes when there is need,
like because security vulnerability or serious reliability/performance
issue), it would be easier to produce binary package and sync them
across mirrors.

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (FreeBSD)

iQEcBAEBCAAGBQJOaVOaAAoJEATO+BI/yjfBWmkH/RRpJWJQn4Gqv7WL/HMsX/4Y
kXZjVwS5uRF1hey3kf768P0Z1KcFeWNjyMx/B7VkV30tZzqs6Y/5EDqIEKrbrHJ/
Cq6tJGojG6k58dZPPRmCAo97FNbMYO2Xn4pj4+vz2hy/s0YRpPY9Ry+1yGMW0N2W
Z55Xoko51Y5e1ZDtMjXTe+AqW1N+Gt/S/5HNAqTY9znpMADmeTyON+37wd069x+E
WDd1oHLGadTt123KBU0NMhAMXGhWZWhQh6u6YRQP9Xkog3k9mNnAO+gHY/xiUG0h
2vlDhbZ5WFbeuw7eLd7sWgfgl77j42TFSFq0PUR9gdEBPkBJSjjJkk+B0Wb+A5E=
=V1Bg
-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: Why do we not mark vulnerable ports DEPRECATED?

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 08/30/11 01:17, Doug Barton wrote:
 On 08/29/2011 23:25, Mark Linimon wrote:
 So, the right answer may be it depends.
 
 I think my point is, it shouldn't. If a port is important/popular
 than it will be quickly fixed. If not, it goes away. Everyone
 wins.

Personally I do support this idea.

By the way vuxml is essentially a BROKEN if portaudit is installed.
Perhaps we should have that in base system or the build cluster?

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (FreeBSD)

iQEcBAEBCAAGBQJOXKFYAAoJEATO+BI/yjfBwkYH/2hDRqHEHztCDybJ4pE6u682
tURpASOWJgxkFn0xT1GF0VL9iwULWbboPdKVhWWPKAZiOWezJbepPeQv4Lcvbqqs
GB28I6DPyRIDES1eqAVJ9RbjP8LgUCTMBu2LU8YCkB1Zrbg9fXD5I0amEXaDTVoc
vBPM2uiWjx49/vgBRjSYKo2KG4MxOAt0PS+SlxXD5eeNodJmMLq8ipL6nA0ptA03
/l8ymf5wbNIWTmBm98CY1bIzxtVb1zcvkHPZRe4fPPXCFElrh6qCou09XJxoWg3P
sTaf6kIpCxTcPsKCdAipo5OvcnXh66Kn4hlKpvc3mKwYr5jMN69d9KqSaLw0HM4=
=02aU
-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: apps in ports by license

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 08/18/11 01:33, Jindřich Káňa wrote:
 Dear All,
 
 Maybe stupid question but is there any possibility to search,
 sort apps by license?

Not currently.  This would need a change to INDEX format I think...

Cheers,
- -- 
Xin LI delp...@delphij.nethttps://www.delphij.net/
FreeBSD - The Power to Serve!   Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (FreeBSD)

iQEcBAEBCAAGBQJOTNWaAAoJEATO+BI/yjfBgUQH/3t33gZKSD9G3TWfsAYQBscY
HfGxsW82K9Gsn9WTpdtQh7G0fwxE0ZuH01r4IHmwneBjGCcv+n9VGep6FSag1h3+
JkFcG3xe+XxqhTc/qjRk5tdqR8miShQ6XN1cLSaWnQKH2yM4OCenrXcM9s6ieGmu
iipHHeKVAyg705EbRAQXhzZUM9B8Zq2lDELJmwYIQVdNsiiG9WO6blWRpA2yNNPx
JoaCS3BimjO/Zmxj6oZZ/lzD+cyRetYKJq0SuQOcMQ6F2sbfoSh/DP+vRpSS7ozy
AwBLiFhDH+DfP9o22DnwKWZK4t+yZ3pgf0iRZNVpfJg+3Tw1UrFHgbSEyr58eTc=
=fg/A
-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: archivers/unzip vs tar -xf

[Xin LI]

On Mon, Jun 6, 2011 at 10:20 AM, Eir Nym eir...@gmail.com wrote:
 Since FreeBSD 5.4.0-Release libarchive(3) support to unpack zip files.
 Why not to use it to unpack distributives to workdir?

 I've downloaded all distros and tried to unpack them all with tar(1)
 with no problems. I use FreeBSD 9.0-CURRENT r222717.

I think the reason is that at the beginning tar(1) does not work for a
little fraction of distfiles, but yes, I think it's reasonable to take
a step forward and add a new option to force using the info-zip
implementation.

Cheers,
-- 
Xin LI delp...@delphij.net http://www.delphij.net
___
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: Problem using devel/apr1 with OpenLDAP 2.4.25_1

[Xin LI]

On Sat, Apr 2, 2011 at 1:46 PM, Jim Trigg jtr...@spamcop.net wrote:
 checking for ldap support...
 checking for ldap_init in -lldap... no
 checking for ldap_init in -lldap... no
 checking for ldap_init in -lldap... no
 checking for ldap_init in -lldap... no
 configure: error: could not find an LDAP library

This is caused by 'FETCH' option which wants to drag libfetch(3) in
(it doesn't show the expected message though, you may have to open the
apr-util's config.log to see that).

Cheers,
-- 
Xin LI delp...@delphij.net http://www.delphij.net
___
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: Problem using devel/apr1 with OpenLDAP 2.4.25_1

[Xin LI]

On Sat, Apr 2, 2011 at 3:06 PM, Xin LI delp...@gmail.com wrote:
 On Sat, Apr 2, 2011 at 1:46 PM, Jim Trigg jtr...@spamcop.net wrote:
 checking for ldap support...
 checking for ldap_init in -lldap... no
 checking for ldap_init in -lldap... no
 checking for ldap_init in -lldap... no
 checking for ldap_init in -lldap... no
 configure: error: could not find an LDAP library

 This is caused by 'FETCH' option which wants to drag libfetch(3) in
 (it doesn't show the expected message though, you may have to open the
 apr-util's config.log to see that).

I have committed a better fix for the problem, please update to
openldap24-client 2.4.25_2 and see if that helps.

Cheers,
-- 
Xin LI delp...@delphij.net http://www.delphij.net
___
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: Unable to configure dirmngr after openldap upgrade

[Xin LI]

Hi, Kostik,

On Tue, Mar 29, 2011 at 1:18 AM, Kostik Belousov kostik...@gmail.com wrote:
[...]
 I did not verified it, but suspect that libldap.so linking line
 missed -lfetch. Note, that I mean the libldap.so linking, and not
 linking of the utilities depended on libldap.

Looking at the build log, I think you are right.  I have put in a fix to that.

Cheers,
-- 
Xin LI delp...@delphij.net http://www.delphij.net
___
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: Unable to configure dirmngr after openldap upgrade

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 03/28/11 12:42, Kevin Oberman wrote:
 Yup. openldap-client-2.4.24 does fine. Looks like a bug in 2.4.25. I'll
 take a look at CHANGES and see if I can figure out what broke the
 inclusion of fetch(3) support if I get a bit of time.

It seems that libldif now referenced the fetch support, and ironically
it seem be a bug but a feature :(

I have decided to disable FETCH support from now on, since it's likely
to bring more problems.

(If you would prefer to fix the problem for this specific problem, I
think adding a '-lfetch' would be sufficient; but, it seems to be
undesirable to depend fetch(3) unconditionally for all programs that
uses openldap).

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (FreeBSD)

iQEcBAEBCAAGBQJNkPQ6AAoJEATO+BI/yjfBGi8IAJ/3o2sVhal0i7982PNuCZXW
gI2aH/e7dWDM2NfL8dSKZlmF8vH/Q0aZHHvlVpQ4o0tCYSk4Iouk8BM6MEVS1Upc
3JLmHVR12D0FBblLpetTstcdx2w2390efPrTI+j+YrJn5yz218Ypu53k1d4F4D/L
IbM3t96FwulS/vSara6pb4m1H28FMpEs7+0jqEDdeJxm26cWWe++z48Lg5yUcnwW
uh2aiDpll7ep7vEuWQGw7pfG+IBd3tsTKm1rqXJ4hgZirYI5lXg18tL2W702P0Ez
kyeye7uY7nsWqR0f7nWCBF5GMPidCQ1/fzAz/WwHtoTkbw4vPpDxiNxwox59H7I=
=m6q3
-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: Unable to configure dirmngr after openldap upgrade

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 03/28/11 13:57, Doug Barton wrote:
 On 03/28/2011 13:48, Xin LI wrote:
 On 03/28/11 12:42, Kevin Oberman wrote:
 Yup. openldap-client-2.4.24 does fine. Looks like a bug in 2.4.25. I'll
 take a look at CHANGES and see if I can figure out what broke the
 inclusion of fetch(3) support if I get a bit of time.

 It seems that libldif now referenced the fetch support, and ironically
 it seem be a bug but a feature :(

 I have decided to disable FETCH support from now on, since it's likely
 to bring more problems.

 (If you would prefer to fix the problem for this specific problem, I
 think adding a '-lfetch' would be sufficient; but, it seems to be
 undesirable to depend fetch(3) unconditionally for all programs that
 uses openldap).
 
 I know next to nothing about how the openldap-client stuff works, so I'm
 sorry if these questions are silly. :) The biggest question is, does
 dirmngr compile after your change? The other question is that the only
 reason I have openldap installed at all is so that gnupg can use it to
 fetch keys from ldap keyservers. Will this still work when the FETCH
 option is no longer present?

hmm... how do I test fetching from an ldap keyserver?

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (FreeBSD)

iQEcBAEBCAAGBQJNkPuXAAoJEATO+BI/yjfBIfQH/0eDvRuE5BTRr/lpMhKgsLQf
8m18MN+52TXNV1xDGvsPU9Z4fRRFfIgm90mVXVeKGwAvTa9xJdLygybPtvsbh6OJ
AIlLa7N1JBF9G7BxD8Mzg8T43Ho5UgpZDsFCnd/K1CkjDFuvCMO8SEUWRdNGY23T
6j83Zdb+8rhlbq3nL3+2oejYGRR/QzoqTwGBLvHYZD0NFmcDuR6qUddHxfN7+94h
rYzw03GHlSu734PWfuqR5i8+tgrvv2eAte0flhrXU+ukMbZKFB8HBJRHAsylRRs/
SYxoDjO441GpEjGS51ZRlXdyx+cWoDa15lXO9G26y270DE7YmOScXzF1sp/wKQI=
=H2fm
-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: Unable to configure dirmngr after openldap upgrade

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 03/28/11 16:30, Doug Barton wrote:
 On 03/28/2011 14:20, Xin LI wrote:
 On 03/28/11 13:57, Doug Barton wrote:
 On 03/28/2011 13:48, Xin LI wrote:
 On 03/28/11 12:42, Kevin Oberman wrote:
 Yup. openldap-client-2.4.24 does fine. Looks like a bug in 2.4.25.
 I'll
 take a look at CHANGES and see if I can figure out what broke the
 inclusion of fetch(3) support if I get a bit of time.

 It seems that libldif now referenced the fetch support, and ironically
 it seem be a bug but a feature :(

 I have decided to disable FETCH support from now on, since it's likely
 to bring more problems.

 (If you would prefer to fix the problem for this specific problem, I
 think adding a '-lfetch' would be sufficient; but, it seems to be
 undesirable to depend fetch(3) unconditionally for all programs that
 uses openldap).

 I know next to nothing about how the openldap-client stuff works, so I'm
 sorry if these questions are silly. :) The biggest question is, does
 dirmngr compile after your change? The other question is that the only
 reason I have openldap installed at all is so that gnupg can use it to
 fetch keys from ldap keyservers. Will this still work when the FETCH
 option is no longer present?

 hmm... how do I test fetching from an ldap keyserver?
 
 I'll save you the trouble. :)  I got your latest update and tested both
 scenarios myself, and the answer is that they both work.
 
 So now the question is, should the FETCH OPTION be removed altogether? I
 imagine that a lot of users will be at least as confused as I, and word
 is that PRs for other ports are already showing up.

I think that's being used in some ldap utilities so it might broke some
applications that makes use of that?

I'll add a note in UPDATING to document this.

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (FreeBSD)

iQEcBAEBCAAGBQJNkR1YAAoJEATO+BI/yjfBqaoH/0fOftHLInATGWxi9/JxTrv2
K0/SViPM7z9QRhPs8bpb1OnsQQvD7gwp/siz6TRkGMmTQcRc41ezmHmmX3wyhC27
mWQ6dx2BXNHJDATBcwiqAvQnUlIv5BBLwWqHRqiVvPc1k4ecqzoWSVACPzWNL4c0
LwlOgnE0dXwShB8ML5/4EJhAAsrtaaOveEDGT+WL6CmeDZzh/bc5K1g3qYHcmeBb
qUD/crMrE3CfZAOd6qYY6L4gMw1A2Ed30DrjtKiW/4F807zBnmKVmH+5+YheIe9p
McsHlHpxNtbN49A6pXTsYOhLD8ZyJIm6O/Znm6a1UcOi2pXBC7FWVuzcot/LJ1I=
=a5f5
-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: PHP52 vulnerability

[Xin LI]

Hi,

On Thu, Mar 3, 2011 at 12:09 PM, Andrea Venturoli m...@netfence.it wrote:
 Hello.

 As you probably know, it looks like php52 is vulnerable:

 Affected package: php52-5.2.17
 Type of problem: php -- NULL byte poisoning.
 Reference:
 http://portaudit.FreeBSD.org/3761df02-0f9c-11e0-becc-0022156e8794.html

 Is there any news on the horizon?

I think PHP developers haven't get that patched for 5.2.x (yet), as
the branch is considered to be obsolete.  We may have to patch the
port ourselves.

Note that FreeBSD PHP port comes with Suhosin by default, which
_could_ have mitigated the attack (disclaimer: I'm not very confident
that this solves all problems, though, as it requires a more through
code review).

Cheers,
-- 
Xin LI delp...@delphij.net http://www.delphij.net
___
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: openldap-sasl-client ports

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 01/27/11 13:44, Yuri Pankov wrote:
 Hi,
 
 Looks like dependency recording for openldap2{3,4}-sasl-client ports is
 broken again (I tried to fix it in ports/135664). I can take a look at

How do I reproduce this?  (so I would be able to test before commit? Or
it's someone else broken it?)

 fixing it again, but the real question here is - do we really need them
 now, when options are the same for -client and -server ports?

I'm not sure if I understood what you mean -- do you mean that now that
we have OPTIONS menu for both -client ports?

Speaking about the two different ports, I believe the real reason for
having both is to make it easier to install binary packages (we build at
FreeBSD cluster).  Note that we have no preconfigured ports that uses
them though.

I do not personally use SASL'ed OpenLDAP but I am not really sure if
it's Okay to just axe the package...

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (FreeBSD)

iQEcBAEBCAAGBQJNQfexAAoJEATO+BI/yjfB+1IIAJuIU5F9hhTPUY+Im0+JwGip
LshjR4l2sM/Mx31xhgMv3rC8MVP3+yjvM4M49+dKSK3XwZmDVf9TM8R7OJ86dVuJ
kVcIqkX5JMDm/3sv+TfIH31jFhuOf7foiVd5g86p+Ll81RAh6QoLTl1zYiCaRo6p
CJfuU/t5d1sZ7iMk245vP9ueOWiuf66OwdPyxJ8C6D8Ux0jqAJPLmZXpKFCiqQk/
KSei8wp/KfC7Yxgf94xVc+smKOsLllFBv+RezNZ97CusYBhVHmBd0UMKmg/RHrrv
Knop881BsgFFmgu3bfzZcndnTbfUfXZda5h1hHo2lpns6gWEUheq5Jh1vGKdkno=
=pbte
-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: Returning with question about SELECTIVELY updating ports tree

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 01/18/11 15:00, Mark Terribile wrote:
[...]
 So: How do I upgrade my ports system selectively, without wiping out 
 everything?

You can actually portsnap extract a part of the ports tree.  e.g.:

portsnap extract net/openldap24-server

BUT, keep in mind that this might be more tricky than a normal portsnap
update, as you may miss certain dependency.

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (FreeBSD)

iQEcBAEBCAAGBQJNNiI+AAoJEATO+BI/yjfBCkAH/0Mt16k9KKYi0aBYq0pfoKRT
cze8LkOiSDqYQ3Do4WOUsxvcLQnQLWd2yNq+81aZhU0H6P/F8sQzL8nffcv7Iiv9
xSLosM52jlBzcmmyhmz142iVDuC7jjfkncnA0p2zGt/mZErauPL70o44xgw2zcD2
70aqztMHcuIDt4bmnT/qoWIoOFou1n9EjamdmINhDd38AKj6qlp0dPKkvtX6LQgD
l5RXoDVtt1inVp1N8ELo+gweipJgj0B+nwM82ENxy+33xdOkpliUnRo9fX+AOvAO
SAZBmlgl+4KHkIi9FZLb72WqlXIyzo9YUhjkuBYsHXREquncH5LvHsJmmdj2/ug=
=Qo6/
-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: Returning with question about SELECTIVELY updating ports tree

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 01/18/11 15:43, Mark Terribile wrote:
 From: Xin LI delp...@delphij.net
 Subject: Re: Returning with question about SELECTIVELY updating ports tree
 
 On 01/18/11 15:00, Mark Terribile wrote:
 [...]
 So: How do I upgrade my ports system selectively,
 without wiping out everything?
 You can actually portsnap extract a part of the ports
 tree.  e.g.:

 portsnap extract net/openldap24-server

 BUT, keep in mind that this might be more tricky than a
 normal portsnap
 update, as you may miss certain dependency.
 
 Xin LI delp...@delphij.net   
 
 Xin,
 
 Will that work on the first extract?  If not, am I back to the original 
 problem: wiping things out at random?

As long as you do 'portsnap extract category/portname' it will only
affect directories matching that.  E.g. 'net/openldap' would match
net/openldap*.  There is no first extract when you do it this way.

 Is that what I really want to achieve?  Or do I want to extract the control 
 files (INDEX?) and then update the ports one at a time?

INDEX is not a critical file, if you really need that, you should
probably generate it manually.

 It sounds like the only sane way to use portsnap is to run portsnap when the 
 OS is first installed, before even building the first port.

Not quite but I (personally) always do that.  'portsnap extract' is
required before 'portsnap update' but not a partial extract nor fetching
update.

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (FreeBSD)

iQEcBAEBCAAGBQJNNjcTAAoJEATO+BI/yjfBhgsIAJ4Atudcot6L+rSHM/uR3dpu
KQ3sGHOAV0f/T0384w1I8IT06oRmTNx7xk0FoLfMQzw2aX8qpbH1L5ZylDvKSKOy
Hh7S0y4QHkjbL0pcPMFp3mi606WdmHWobRPsWqSzOJB7l9zGHLAcT5yp6b2mwiMP
MupmW8GDbbphWzZ3HcQkC/VEmR1ifQ5m9LBpvOuvY77AUnElBoYfbcSF4xiBB3oV
RdtRkYfnQczjq0pZa0wsj4OWjj1HaHwzDDqSb0GvUSHV7z+98WY/yVq0XaVYUf7s
F64pvgBUUpk+ubIPwSv7E1KdyTJzEfY3+52tInZMzIaUs5ehgCxz7cGp3AtlhkE=
=vACb
-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: Commit ports/147840:

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

On 2010/06/25 03:31, Jerry wrote:
 I realize that everyone is busy with the soon to be released 8.1
 update, etc; however, could ports/147840 please be committed. It is
 required to correct a bug in the last released version of the program
 that prevented it from running under certain conditions.

Quick question - files/default.sample now have an empty CLAMAV_DB, is
that intentional?

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.15 (FreeBSD)

iQEcBAEBCAAGBQJMJQN1AAoJEATO+BI/yjfBLeIH/iNvBxjzLVQQyjX2vcfbJYtT
NQTu9LZRvws1npPDoV90utZ8+VlfTaciQimxYMWeJbL3yAgTQ5dv8IID8tAcrYW+
KJ8j0bzrpnCFluwloEEItgaNmGYE0mSZbeZNN/9+GETS7l2nFDbc3jea/P8xUzbi
TZ3DdBjmpawzyxPBv5pLgowYW+PelPFguE1Go5mJbo2bzFNa7pKQQb58eSOXvY2q
hrRjXyfVP6axzU1Kr9gzujiVI3WVSRAyLtL77x34oW0POJq/w963FniybWt4qs0l
lnBDEeMZA6fC5j7K20v4oVMksBCjU1zcQcwi8al4Nx7mSF8rdz8AUsNtM383IOk=
=Bcgz
-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: FreeBSD ports USE_XZ critical issue on low-RAM computers

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 2010/06/18 09:54, Matthias Andree wrote:
 So for FreeBSD, I propose to patch this Mk/bsd.port.mk line #2382 (as of
 CVS rev. 1.642)
 
 EXTRACT_CMD?=   ${XZ_CMD}
 
 to
 
 EXTRACT_CMD?=   ${XZ_CMD} $$(getconf LLONG_MAX)
 
 
 Other proposals?

Will ${XZ_CMD} -M max work for you?  This should have the same effect I
think (assuming the ports xz version supports it)

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.15 (FreeBSD)

iQEcBAEBCAAGBQJMHBKWAAoJEATO+BI/yjfBqukIALoVYkI17tqAIsJ7OTne4dRL
Jk+VYgNawha4Db9KRKOyjG6u+t0UpV+5gJl+mTvf0FWqh4WcReVfTBGMibjn7HHq
n43ufR9dcHj1AD1LxBHu6UQRlGgb93AEqoQv+gj7cNYtxz6pxaNhGIxwW2gDRaT9
umAnuqIwBvZP8T1j3FYPYixZyrfxOtwEJ9OehkdAkRI7Ip4JPp8nf23Lv1oagzU9
UCCaosFgbqXDUV8O7RREkJm2brQuSBLdQiaojg/ZlV1V8UHjRn30qOkA6yGSZHd3
ydPSDMl4P8rqSwo7LHoJSHOezjfc3y5ZA+ZTRQiiglVxPXp3nm8aEJqMJv4KIvA=
=0vOp
-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: FreeBSD Port: openldap-server-2.4.22

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, Marc,

On 2010/05/05 12:53, Marc Hunter wrote:
 Just installed this port and I'm running into this problem  starting slapd:
 /libexec/ld-elf.so.1: /usr/local/libexec/slapd: Undefined symbol
 ldap_pvt_csnstr

This is a symbol from OpenLDAP's library.  I can't seem to be able to
reproduce your problem, though.

What's your output from:

ldd /usr/local/libexec/slapd

And

echo /var/db/pkg/openldap*

?

 I know this is not much info, I can provide more if this is not a known
 issue or a known stupid question.  I only broach it because I see recent
 changes to the port and another comment online of a similar problem and
 the suggestion that it should be mentioned to the port maintainers.
 
 I was attempting to follow the steps listed here, and had an up-to-date
 ports tree:
 
 http://forums.freebsd.org/showthread.php?t=770
 
 Thanks!
 
 Marc
 


- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJL4dYeAAoJEATO+BI/yjfBJ8YH/3K9YdcGmxJfY1K9/QTo6de0
CL0EDOL1pf8hl1J7BDTyLqlRyU+M47vwbQCGOEHgKDmn3f25hTWAxbLgReSnRDDZ
c1xwzcWQx7KmH9vgMTnu229NVtM+nBF3GJlfJ0ui8pyJAbiB+5XUSaZ7uNNHOwh8
8/lzNm2BGcPi56b0Xy2WC6AwmpK+XG5fwcOVFNi/6A83eNnm6l7UPwXql/SQ1Dya
RRO5KdT+CjRYML8Y3Uw8ZnEsmmrcwZl+0I43VR/f8jWwdbfep0xPSZ0ychfIHLde
LXLx0m1d+Ln0+yNtZ2r/vVexbEAaPXQvxBe6NtuF4OodLaHr4OfK5WhtwM7s2yg=
=Xyu2
-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

Recent nc(1) changes

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Thanks to Dima Panov, we have now figured out a behavior change that
could break some ports.  I'd like to give some more details for the record.

In the past, nc(1) would give a message like Connection to xxx xxx port
[tcp/*] succeeded if either -v or -z is specified in stdout.  In newer
nc(1) from OpenBSD, this has been changed to stderr.  In -CURRENT, we
have followed OpenBSD's behavior.  I think, that this behavior is more
sensible since one can, say, filter stdout and stderr to two
programs/logs to fill their need.

This unfortunately would break some ports that uses nc -z's standard
output as an indicator of whether the connection is succeeded.  To solve
this, one can modify the script to use 21 when getting the output,
which is compatible to the old nc(1) as well.

Another change is that nc(1) now considers '-o' as deprecated.  My plan
is to remove this option before 9.0-RELEASE.  Will this removal be a
problem for anyone?

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLx2f+AAoJEATO+BI/yjfBkKMH/2R4J82mJkWJkddZ/XjlmoQq
VruKRMu06w3pXpqzMyqt0MXMII8v5x1jRrhusrZnNJ3dLXjpBHj9WqBYLVCskDdf
3etDE4gKK4DH2hhLuK4HOT4fM70OSN/18fDcpbZ7zrIRWoSheQXESZKy9po99y69
ENUhuxgyzDKzOqccArttJbiz6+jrcoDOjRf7ULnegIKaE4B58fAcpqO9A+6UZBHc
Rh2OdnQgYI2wpKxihZiklgK7VDQx09Qvl+4UacDC08uu7rBh3cD09UziQHGjnicV
MLhFSN/LGNNc2BVb0z4mFOtaP4efYu9Rxuyy1idOJCPg/HD/+2CECNlZm2BWRe8=
=azZK
-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: Recent nc(1) changes

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2010/04/15 12:41, Dominic Fandrey wrote:
 On 15/04/2010 21:24, Xin LI wrote:
 ...
 
 I'd say that the data loss (~1%) when I tried to use nc with UNIX sockets
 (on both ends) is much more troublesome than your changes.
 Even when I used lockf to synchronize socket access this loss occured
 and I have fallen back to using files for messaging in my scripts.

Data loss?  Sounds like a bug to me.  Do you have any reproduction scripts?

 Back then I thought I must have done something wrong, but I cannot think
 of anything.
 
 Obviously an option with disadvantages.

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLx22mAAoJEATO+BI/yjfBZ+0H/0bHxu91FXiU7vP89M9c16Vo
OcImtJKlbJRwIszZtGgQW880/ePnMPS+YV0qhvGm7RAAjZBUf3L6xL/lFkEYjIfK
YZCoq9SUT5TJNeLixeQZLdispIxYntFcBABwt61GXjDfvfBzm2CZXxFHE2gMYcbd
gOpoIZ6ZsoULdJMQ8EEwQQtAegRL9uUBtv/49gJ010JUSye+8rVawlxXT1mNoMU4
vrFqMmosIP+NOm+Blm0F/BSh4FTUL+XgLfSZFEWzzzwMreQwM6cFUmMZEsc/0IjW
DF4epM5J7VoV+xxWIw7aM6ojSHSrgIl7OXcAT9TSzdbJt44/iy/MP5G35JCCFsM=
=uxnX
-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: Ports breakage since r205471

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2010/04/05 01:50, Erwin Lansing wrote:
 On Sun, Apr 04, 2010 at 03:06:15PM -0700, Garrett Cooper wrote:
 Hi all,
 I realize that this is most suitable for current@ and I'm
 cross-posting, but I wanted to jot down all of the ports broken since
 the zlib version bump so that we can keep track of what's going on and
 what needs to be fixed.
 
 I have just started a new package build against todays HEAD on pointyhat
 , actually before seeing this thread, so these, and any others, will be
 picked up there.  I'll update the list with the results when it finishes
 in a day or two.

Which svn revision is currently using on the build cluster?

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLuac2AAoJEATO+BI/yjfBusMH/jAc2pH439rkteRRX5oK+IXo
hV3qXE0pMNkrGDDciVbYuJ9r/niqdkBIqaaw2te8K97YwBAdpikheHV0NaHoOzYT
J+OiKmTu2o96J7FV7ORSRmPUcKhHHTjXwLMF2Kz9MeoRvYJqyVk1m33wMuDdIGEe
57Pxq3sXpbfmUoOq5S7ITLXSPqE+l5Xh0j4wM7wULQWhabTw1akliDGxvwr1XqrU
8r+3dbLASzV8hitIXk92MLCfomJNDgsW3VV3nqlzmiLlwBOfGrGowZblKlgHUWO4
VEJ6qCXpRPGpelIVSDyguR3BCEl2m9tyQ3xQ8MEznjwuOJGpp8vwNrwAUOB0PpE=
=g4ur
-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: Ports breakage since r205471

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2010/04/04 18:58, Garrett Cooper wrote:
[...]
 As jsa@ so kindly pointed out, upgrading to r206057 temporarily

I think you really want = 206058 :(

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLuWZhAAoJEATO+BI/yjfBkrwH/iQTvZQJkYPCRXbqBPVqhTi2
5XMri6IMV7rEij2HIFd5X8IAbts+6YvzIEwEZnkNboBGvhHruwu3Jsip5B3dcNx/
vNPavaqm9p56RgM8Dkl8mg+zZ6VN0rTf9p4eJ1EsL1EuQF4HtiDWugK746CLI6Xa
FH7LEXOEHYfEkLoqWMR2nFjGqpBi65g7H6BoT/hj3egTmNHZsMKck+TdViKwsY6X
P4wqzlSQJ6u0Ri1k8GPeGgUiSyL8djG2DVXsbhMkWTfi6QS/YBy150tqqVT0ggjL
9pZ2e3jDcU3jrp+9iOrLLQUU5MgPdyz70OgnI2ZLTfiocAtXiVb5Z5xIp4F2BDM=
=TKt/
-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: multimedia/gpac-libgpac fails with zlib problem on -current

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

In order to prevent further damage, I have hardcoded FreeBSD's
configuration as unifdef'ed in zlib.h:

 -D_FILE_OFFSET_BITS=64 -U_LFS64_LARGEFILE -U_LARGEFILE64_SOURCE

Hope this helps.  I'm still in discussion with upstream author about a
better solution.

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLtQ/cAAoJEATO+BI/yjfBATgIAMXvA0OdOUYwL72uAIRV7V9M
2Ebjfw7rFSoKahf2A/8qaY3i5eG1Lrw9PqztJgJCXdRxsN9OXIRrqwooYepJtFyt
8RibBxNXGNt5nawG7tZxYTh1uOi7hASrLARvIkOvHYcdQ3rJrzu+2iKlg7uvQO/M
CbPV7CcfD/pBYgAm1RgrurTXL2XnsvYJdQgmNQipQ4h48IuF21wAA3+isxfHRhrV
5kY3Ml3zE4yYALWSACRUbd1ylPEEWTwLTrReLLRXAiDJtA6m0Cm+1mfSaPSsF6+w
ZqIX2nE9saGGzrxmWjHBe+wuAGrruNDSa4SLOYSGmdh6EOONsdB82rbq97NsXKg=
=WdlL
-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: [RFC] Reduce namespace pollution on zlib.h

[Xin LI]

I will merge an upstream change from zlib, which basically unexpose LFS
stuff on FreeBSD, and I plan to keep the off_t bits == 64.  However, I would
highly recommend ports maintainers to push upstream fix for LFS64 definition
removal since they are wrong on FreeBSD

On Mar 31, 2010 3:30 AM, Pietro Cerutti g...@gahr.ch wrote:

On 2010-Mar-27, 02:51, Dag-Erling Smørgrav wrote:
 Xin LI delp...@delphij.net writes:
  So... ...
Just to make it clear so that everyone knows how we're going to handle
this: are you (src people) going to commit a fix to unexpose LFS crap
or are we (ports people) supposed to fix each and every single port
that supposes to be on Linux?

The attentive reader will note a bias towards the former :)

--
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org

PGP Public Key:
http://gahr.ch/pgp
___
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: x11-toolkits/qt4-gui fails with zlib.h off64_t

[Xin LI]

On Tue, Mar 30, 2010 at 11:14 PM, Doug Barton do...@freebsd.org wrote:
 I can now confirm that with Xin's patch for zlib that all the qt4 stuff
 builds, I updated virtualbox, and that builds and runs just fine.

Just a quick update: zlib has been updated to 1.2.4.1 (beta) on -HEAD.
 I have tried qt4-gui and it seems the compilation issue has gone.

Note that port maintainers are still encouraged to have upstream fix
the _LARGEFILE64_SOURCE issue.

Cheers,
-- 
Xin LI delp...@delphij.net http://www.delphij.net
___
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: x11-toolkits/qt4-gui fails with png and/or zlib.h off64_t

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2010/03/30 12:22, Doug Barton wrote:
 Testing it again I see that I didn't go far enough up to find the real
 error, sorry Dirk.
 
 The actual problem seems to be with zlib.h. This is from qt4-gui:
[...]
 -DQ_INTERNAL_QAPP_SRC -DQT_CORE_LIB -D_LARGEFILE64_SOURCE
 -D_LARGEFILE_SOURCE -I/usr/local/share/qt4/mkspecs/freebsd-g++ -I.

There are some discussion about these _LARGEFILE64_SOURCE usage on zlib
developers' mailing list.

To put it short, it's now believed that the usage of _LARGEFILE64_SOURCE
on FreeBSD is wrong.  I'm not quite sure though, if I should use some
workaround over this, like Mac OS X did (newer zlib has a similar change
by requiring _LFS64_SOURCE):

Index: zconf.h
===
- --- zconf.h   (revision 205883)
+++ zconf.h (working copy)
@@ -375,7 +375,7 @@
 #  endif
 #endif

- -#ifdef _LARGEFILE64_SOURCE
+#if defined(_LARGEFILE64_SOURCE)  !defined(__FreeBSD__)
 #  include sys/types.h
 #endif

Index: zlib.h
===
- --- zlib.h(revision 205883)
+++ zlib.h  (working copy)
@@ -1556,7 +1556,7 @@
 inflateBackInit_((strm), (windowBits), (window), \
 ZLIB_VERSION, sizeof(z_stream))

- -#ifdef _LARGEFILE64_SOURCE
+#if defined(_LARGEFILE64_SOURCE)  !defined(__FreeBSD__)
ZEXTERN gzFile ZEXPORT gzopen64 OF((const char *, const char *));
ZEXTERN off64_t ZEXPORT gzseek64 OF((gzFile, off64_t, int));
ZEXTERN off64_t ZEXPORT gztell64 OF((gzFile));

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLslHRAAoJEATO+BI/yjfBXOUIAKW6UkjU8JGw2CQyNWVhqxXg
dz1OKJVk5iS1abpPANZPPWRnl/XK2MiDIVdkc5HQCCbFIuodR4nWlbZN21yGMJvf
DZX3L15nhXE7LSMLxOgrfzqlgIRxnu6P/7mjlZq/y/TERrpHh48lN7HcHfRrWZd4
H/dFdSQbL81T7/LGPmrHOsR9uXPOmlaa1hUMCgJhNl2S6AahfyfcEj5hQeCBXqHd
ms9gORkFuMb9LStS3kaTSpb6/D81ci+WbGpHozIA1zGyTazyj9AJjFkYHhC9VZLF
9kSGF3yuD95pGHrOrZJQSyTNBMtWFAoLm1qMMZu+D8b1vpP3AnVdSGVhTR8QrM8=
=vFcJ
-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: Be careful with fdopendir() on RELENG_7

[Xin LI]

Perhaps as an errata?

On Mar 29, 2010 7:42 PM, Garrett Cooper yanef...@gmail.com wrote:

On Mon, Mar 29, 2010 at 6:07 PM, Xin LI delp...@gmail.com wrote:
 On Mon, Mar 29, 2010 at 5:45 PM...
   Hmm... is it possible to release note it after the fact (or at
least release note all major / outstanding items discovered shortly
after the release, like the accidental zfs bootloader breakage)?
Thanks,
-Garrett
___
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

[RFC] Reduce namespace pollution on zlib.h

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

The recent zlib import has added some assumption that
_LARGEFILE_64_SOURCE is only defined on systems with System V style *64
interface.  Moreover, I have added _FILE_OFFSET_BITS = 64 definition
into zconf.h so that it would pick up the 64 bit interface properly.

This unfortunately could cause some namespace pollution.  As such, I
would propose the attached changes to zlib headers:

zconf.h:
 * If _LARGEFILE_64_SOURCE is defined, set __FreeBSD_LARGEFILE_64_SOURCE
and undefine it, as it would break zlib.h
 * If _FILE_OFFSET_BITS is undefined, set __FreeBSD_FILE_OFFSET_BITS and
define it as 64.

zlib.h:
 * If __FreeBSD_LARGEFILE_64_SOURCE is defined and _LARGEFILE_64_SOURCE
undefined, undefine __FreeBSD_LARGEFILE_64_SOURCE and define
_LARGEFILE_64_SOURCE.
 * If __FreeBSD_FILE_OFFSET_BITS is defined and _FILE_OFFSET_BITS is
defined, undefine both.

This approach is kind of mess, though, but would avoid massive changes
which I'd propose for next zlib release.

Comments?  Objections?

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLrP4XAAoJEATO+BI/yjfBk2YH/Ag38kdtjxAk0l2kdgnHPnZ7
Wf9uk+0ixgE8X2uHfkOeiVO99Ma47aFU/thS1qgXRIWqP/iQEMqOiUayubYnsCJk
K8quwzEuifM0hlIPzHxgzo5/e1O6GhUdIkJVJj+T//twG2BGXziYHMye/aph0iRa
kW5DEq469jBoz62N8FDn4iatZoXT5boBc0bE3GQCKJhUADbpC84vjCCHfdVx50mu
x5hEO88TNaWSn4AkPgs0xPBYQNM+w6t2g/CLNfylumIUVHcSs+v8sLKrxdqqvKNx
hn97KmDagy5BVaWaAFAqFclgfAVbjfa8NIaOr8egxnuVHXTzEzjHFUD7fS22Oqo=
=eOpg
-END PGP SIGNATURE-
Index: lib/libz/zconf.h
===
--- lib/libz/zconf.h(revision 205651)
+++ lib/libz/zconf.h(working copy)
@@ -375,6 +375,13 @@
 #  endif
 #endif
 
+#if defined(__FreeBSD__)  defined(_LARGEFILE64_SOURCE)
+#if !defined(__FreeBSD_LARGEFILE64_SOURCE)
+#define __FreeBSD_LARGEFILE64_SOURCE
+#endif
+#undef _LARGEFILE64_SOURCE
+#endif
+
 #ifdef _LARGEFILE64_SOURCE
 #  include sys/types.h
 #endif
@@ -391,6 +398,9 @@
 #include sys/types.h
 #definez_off_t off_t
 #ifndef _FILE_OFFSET_BITS
+#if !defined(__FreeBSD_FILE_OFFSET_BITS)
+#define __FreeBSD_FILE_OFFSET_BITS
+#endif
 #define _FILE_OFFSET_BITS 64
 #endif
 
Index: lib/libz/zlib.h
===
--- lib/libz/zlib.h (revision 205651)
+++ lib/libz/zlib.h (working copy)
@@ -1597,6 +1597,20 @@
 ZEXTERN const uLongf * ZEXPORT get_crc_tableOF((void));
 ZEXTERN intZEXPORT inflateUndermine OF((z_streamp, int));
 
+#if defined(__FreeBSD_LARGEFILE64_SOURCE)
+#undef __FreeBSD_LARGEFILE64_SOURCE
+#if !defined(_LARGEFILE64_SOURCE)
+#define _LARGEFILE64_SOURCE
+#endif
+#endif
+
+#if defined(__FreeBSD_FILE_OFFSET_BITS)
+#undef __FreeBSD_FILE_OFFSET_BITS
+#if defined(_FILE_OFFSET_BITS)
+#undef _FILE_OFFSET_BITS
+#endif
+#endif
+
 #ifdef __cplusplus
 }
 #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: [RFC] Reduce namespace pollution on zlib.h

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2010/03/26 17:02, Dag-Erling Smørgrav wrote:
 Xin LI delp...@delphij.net writes:
 The recent zlib import has added some assumption that
 _LARGEFILE_64_SOURCE is only defined on systems with System V style *64
 interface.  Moreover, I have added _FILE_OFFSET_BITS = 64 definition
 into zconf.h so that it would pick up the 64 bit interface properly.
 
 This is wrong, FreeBSD has native 64-bit stat() etc. and does not need
 _LARGEFILE_WHATEVER.

Yes we do not need that and it just cause compilation errors.

The problem is that some third party software thinks that they need to
define _LARGEFILE64_*, which will break zlib.h on FreeBSD :(

I'm inclined to adopt a solution similar to what Apple (pointed out by
Jkim@) is currently having by disabling the _LARGEFILE64_SOURCE if
__FreeBSD__ is defined.

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLrVCbAAoJEATO+BI/yjfBj4AIAMcUAjLIZpNW2sGD0/Z9XLU3
SBevqjvR9iwGANTXOKiB3aofvUygmTfG+8KrxlZTJ51O8vlYgA28eGT0iiDpfoLz
yUtpAN1MIitPp/VtNwHpTpfJcfP+AX060G4MGdxUWCHjoJWhbWMv7OnLbquGdglZ
8bbvQR9EDxm8gM2OT9/b14WOsilYwFBpNlNvxl+Q9d0oWNIi08xWmwvC2aWF7L/6
oTFp2tCKXfi++RCxPU5v+q5SaogKjx1bw612UWvetEhHylcXQpQxqjtyL5WA5IAd
bRYJquOjt3+3mziE0VLlQSQgUSCSYMXls6LqmQSfe3W1sU7wG1rFlZG5BfD/UyM=
=DDry
-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: [RFC] Reduce namespace pollution on zlib.h

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2010/03/26 17:46, Dag-Erling Smørgrav wrote:
 Xin LI delp...@delphij.net writes:
 The problem is that some third party software thinks that they need to
 define _LARGEFILE64_*, which will break zlib.h on FreeBSD :(
 
 Then that third-party software is broken and needs to be fixed.
 
 _LARGEFILE64_SOURCE is (supposed to be) used to expose the stat64() API.
 FreeBSD does not have stat64().  Any application that defines it and
 then calls stat() instead of stat64() is broken to begin with.  Any
 application that defines it and then calls stat64() will not compile on
 FreeBSD.
 
 See sections 3.3.2 and 3.1 of this document:
 
 http://www.unix.org/version2/whatsnew/lfs20mar.html
 
 On Linux, it's a no-op, because while the kernel has separate 32-bit
 stat() and 64-bit stat64() syscalls, glibc aliases stat() to stat64().

So...  May I consider my import just exposed some existing bugs in other
applications and we don't want to workaround these issues?  I'm sort of
feeling guilty for making the transition path hard, though...

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLrWLPAAoJEATO+BI/yjfBJAcH/0WLPx5wiV/5ue4ZmmdPojMi
bxK0XneEwO56bJMOJHg6qxBqwwBm3egabq1abkRYLdOVwoXc9hiGAdVJjjymJ3lz
xJWV23XpLHzso9z3Ev33virj32+Br++zsucdh5aEmC0YvdpvFDQUiU9LUNIErf/g
bjqzrapugiEkrL8xD2Maq5F+OdeMPOV3HXMjU39RpyRKVTfIkG4tfL8wDmBD/KAI
7byS1syUqDP2uvIvHmO2R3lFrto6cjwRhn38Y51XOQpu/Wvrp6KEKX47/vFBUjwE
JHPIGlbkoo3LezPjE+Sv6I4+MAsNncmyol5jKGAxmfe9wNjkHs3Br/AyPGbNCyI=
=00ta
-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: Enlightenment build failure

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2010/03/18 06:01, Piotrek wrote:
 On Thu, 18 Mar 2010 12:38:05 +
 RW rwmailli...@googlemail.com wrote:
 
 On Thu, 18 Mar 2010 12:47:58 +0100
 Piotrek pioku...@gmail.com wrote:


 When i try to install /usr/ports/x11-wm/enlightenment i end up with
 following message:

 Even when it builds, it's an E17 development snapshot from over 2 years
 ago. I found it too buggy and incomplete to be any practical use.
 ___
 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
 
 So my question to maintainer now, is it going to be updated to newest
 svn version soon or do people have to wait until it will hit stable ??

Cc'ing to maintainer...

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLqm/qAAoJEATO+BI/yjfBR5EH/1mw/Tmdn19vptZvLFaw0/ym
7ukqwqtORQ0u31x3RjlotIb7ouDvZdkY6NS/Wk+8e13MzWYsrDTozdMB/Z6nwX3w
xKDnp+DPqmWPrIcv/pru/+DT7sYKfMpsiS3xKmm620860B/2dV2fvJUHB8+D4zhi
0oOP0HrpUKlKpeaHahU5LjDnQqLd/ldEXDUDwesAGe0GrJKQb7tXMOP+yyGrm8pD
5TjjqRyyoz1bX+rg3eqxJtGYpn66kX9c/v6AqY0BbQ1uZku72gQtbSnxtbAfOCi4
GZQB25g1QMpbpnYakajTtbx9IlYO8ZclzWkzQhbp9QZqNu69sYuND0wBlQgj2YQ=
=WtjR
-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: python and HUGE_STACK_SIZE

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

[freebsd-python@ cc'ed]

On 2010/03/24 15:20, Steven Kreuzer wrote:
 A coworker of mine got bit by this bug on and off for the last few weeks and 
 it appears he might not
 be the only one as documented in this blog:
 
 http://tomster.org/blog/archive/2006/09/27/size-does-matter
 
 If python needs to be compiled with HUGE_STACK_SIZE on FreeBSD, is there a 
 reason
 to provide the option to not compile python with it, or at the very least, 
 should it default to
 being on?

Ah, yes this is the thing I turn on on all systems I have myself...  I'd
vote for enabling it by default.

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLqpwyAAoJEATO+BI/yjfBrwwIAJfEAeJ9QXTvgOeMRyAdekcU
teYGqTVP1W3qE7adxvM/2MMQm4ogyJtAJBu9UQVAwiYtckNd1mpaIuQdfDvuc1fD
vD5OT+8Sy+TXqxLi2A29HZkOCvOoYuZ03WwyF5YMpMU6uPHGa0fnx+gNtXGuOxSN
V45ZWxlEwNNKv+WYZzehF5jJvIPLXadrPYP/y53loIXqxA5htV+ZPpiGeidwTDun
u+o5AjLrcRKRM+hrf10X6gfCgJZpQyqeL88fDqhUX6uL1QIQJHg1nBHQ+6DbZrR9
R2cCadkhCF2X3nC3stTDi/KvuAZ4rZZo02lUf8MdxK7PX8T9cd4A7brHCltxoOU=
=UaWe
-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: FreeBSD Ports Problem - Please help

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2010/02/11 20:22, M M wrote:
 My last idea is to install jpeg-8 and then cp the existing libjpeg.so.10
 file to the same directory as libjpeg.so.11 and run this command:
 
 ln -s /usr/local/lib/libjpeg.so.10 /usr/local/lib/libjpeg.so.11
 
 I found out this might be a possible solution from doing research through
 google.com
 
 But I understand this may not be work and/or it may not be the best road to
 take. And advice and/or instructions would greatly be appreciated!

Hmm...  If you have ONLY updated jpeg, you will be able to use a tool
called 'portdowngrade' to checkout and install a older version of jpeg.

Otherwise you may have to, end up with reinstalling all ports
(portmaster -a or portupgrade -ar would do it for you since the port
version bump).

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLdOhvAAoJEATO+BI/yjfB8McIAL1kjLy0+102VAt5O5+lDFfH
LJGYI8KjjPxH+YOH3dOpkvGu3u030UGqaktT9ciaW1Z/Eb9MrdxLDjyjg7MRvX0A
yFhMH+LhoL07MseTNwz1Tyja6Z5DAmjBRvePxt5PDNj1ARHWpkU1h5HU14ChbQmG
KNIhk/BhmipT8Zh7PEh9vJhR2RGJ6gs2TihS6Wo+/sQO5VuQaZc67VL68qiOAh4O
SZ8f1s7HhsF9Rbz9SUviFY6TOYUjb1AqAONV+D0bJ4liypcN4ERcjQaQ2Whvlath
4jAk2Y5S4EMJYHvPyg7R64uuk4sD/JfHQ0rpsZNXSOS1UyE8KOKAAiOLX7nGyiE=
=hpXp
-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 upgrade for port committers?

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2010/01/28 11:46, Stephen Montgomery-Smith wrote:
 When an update to a port is committed, it is likely to contain
 
 (a)  lines like Only in : 
 
 or (b) patches that are created against empty files using the -N
 option for diff.
 
 Cannot patch honor these cases?  As a port maintainer, I have been
 caught quite a few times by committers not adding or removing files from
 the files directory in a port.

For patch to remove files one can specify -E;

I think ports committers are responsible to take care for
adding/removing files.  It's advisable for committers to do 'portlint
- -C' and a full 'port test' (porttools) run at minimum...

Cheers,
- -- 
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (FreeBSD)

iQEcBAEBAgAGBQJLYf67AAoJEATO+BI/yjfB830H/il+N/9xzGfECkPYdErNhHIF
yCRgvrXWqcRv8fy8O2cg0I3reXacxADj9ex+sl4o8wVKBuAJJQv0zSvhBTVIaxyl
bsWThyqf523AE70qmfew2vtsH8nCf4lZVwI9relVpvOOgcCAZcC5Tjj04HU+nbcl
9c/HJJdQmfZcIsYOEU7K38aX7Ip7hgX/JzkZ1gPQWwLH+XdKAkruChjk3vKbbBFy
ZG2EnevcZDwC4e1/354x+1imTg2Jh2BYDuU0eXHnaVfkYInmjHEvE12w5Mtxy8H1
SLQw4mEz1F51TedgUd2uWSY7j91K24AQzo/q99D2C2GYlA/ZX/AJyBVPP2bFXRY=
=/7DD
-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: latest MySql?

[Xin LI]

On Tue, Jan 12, 2010 at 11:09 PM, Robert Huff roberth...@rcn.com wrote:

        MySql-6.* is no longer in the ports tree.  Things depend on it.
        Is there information on what happened and what the alternatives
 are?

PostgreSQL? :-)

For now MySQL 6.x development has been ceased for now [1] and new
development happens on 5.5 series.  You may need to consult their
website to get a more useful big picture stuff.

http://dev.mysql.com/doc/refman/6.0/en/index.html

Cheers,
-- 
Xin LI delp...@delphij.net http://www.delphij.net
___
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: [Announce] Maintained TeXLive (2009 and devel) binaries for FreeBSD-6, 7, 8 available

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, Nikola,

Nikola Lečić wrote:
 Dear all,
 
 The TeXLive binaries for FreeBSD 6, 7 and 8, for i386 and amd64 each,
 are available for download. I will maintain binary sets for TeXLive
 2009; I will also regularly release binaries built from the current SVN
 TeXLive sources:

I don't use TeX much nowadays but still want to say it loudly:

Thank you!!

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.13 (FreeBSD)

iEYEARECAAYFAksmg+4ACgkQi+vbBBjt66AVngCcCCreWjebXo/f8nRcVhHcuGIG
5I8AoIGVNYz2pO7pnoEAecYqt/mOX9vI
=Ad0e
-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: [RFC] Tools/ script for automatically making a tar out of svn sources

[Xin LI]

On Thu, Dec 10, 2009 at 1:58 PM, Eitan Adler eitanadlerl...@gmail.com wrote:
 I don't see the script.

 The attachment never made it through (not sure why: in my MUA it looks
 like it was sent) and after some more looking I decided I was probably
 a bit to fast. I'll send a repost when I improve it

Try sending it inline.  Certain attachment mime types are being
filtered by the list program.

Cheers,
-- 
Xin LI delp...@delphij.net http://www.delphij.net
___
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: RFC: svn for make fetch

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Eitan Adler wrote:
 Correct me if I'm wrong but I thought that svn did its own checksumming.
 If so why do we need to our own?

In God we trust, everyone else must have an X.509 certificate.

Well, that's not necessarily be a X.509 certificate but it must be some
form of signature, as it's not too hard to replace a specific revision
in svn if the server gets compromised.

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.13 (FreeBSD)

iEYEARECAAYFAkr5tssACgkQi+vbBBjt66BdpACdH5+RSlwKN10x8MiGFYiuX0dL
L94An1N1uYCFUYJo0f0U2jZgqRK7emo1
=jFoS
-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: RFC: svn for make fetch

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Eitan Adler wrote:
 I was hoping to get a bit more of a response to a recent posting of
 mine with regard to using svn to fetch files for ports
 My proposal: 
 http://www.mail-archive.com/freebsd-ports@freebsd.org/msg23776.html
 A summary of what has been going on:
 http://wiki.freebsd.org/EitanAdler/ports-svn
 
 This is something that more than 2 people should have an input on

Just my $0.02 but I think it would be great if we can do:

 - make fetch would prefer using a pre-packaged tarball, but fallback
to a svn/whatever checkout with a specific revision number, then
generate a tarball from the export.
 - make checksum would check the tarball's checksum.

Maybe we can also have some variables to control that we actually want
the 'HEAD' revision without checking any checksum.  However, I think it
would be nice if we can do a checksum'ed checkout for specific SCM
revision, especially if we want to have ports to work not only for
*-devel ports where we would prefer signed source code.

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!  Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.13 (FreeBSD)

iEYEARECAAYFAkr4l6QACgkQi+vbBBjt66CD/wCbBcIFcfbK4a0533PAcNxbZuV5
WXAAnjQfl07w/vcHicVS0s+FOrOs5CMS
=1Hly
-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: FreeBSD Port: openldap-server-2.4.17

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Matthew Hambley wrote:
 I've been banging my head on the wall which is OpenLDAP and Kerberos for
 a week now. As far as I can tell I need to create the environment
 variable KRB5_KTNAME to specify the keytab I want to use. If I do this
 and start slapd manually things work.
 
 Unfortunately there seems no way of specifying this so the slapd startup
 script does so. I've tried hacking the script myself but to no avail. I
 see one person out there once had the same problem but got no replies
 explaining how this was best resolved.
 
 Given that this hadn't been fixed in the years of the ports lifetime I
 imagine there must be a good reason for its continued absence. I just
 can't work out what it is.

I think this is a bug and has to be fixed.  Could you please try the
attached patch?  It will add a new knob to rc.conf (slapd_krb5_ktname)
which will emulate the export.

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (FreeBSD)

iEYEARECAAYFAkqYXO4ACgkQi+vbBBjt66B6bwCgpY/2IvykApKITgL/pmsJL8XQ
MeQAoIcoySbNG9nrpYdJAIgHa2PS/r+9
=k4WO
-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: BIND help

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Albert Thiel wrote:
 I know you don't support Version 7.0 release since April, but the BIND patch
 on freebsd.org's main site... will it work?

Yes, the fix do work for 7.0.

 I tried compiling the 9.4.3-P3 on a 7.0 box and it does compile but will not
 run.  Zero day exploits are not fun..
 
 My opinion is that you should support this on v6 and up due to the extremity
 of the flaw.
 
 Any help would be appreciated.  I have newer boxes with patches applied but
 a few are older and I really don't have time to up them all right at the
 moment... ver6 and ver7 mixed.

However, it would be good to upgrade to a supported release according to
your maintenance plan, when possible.  You can use freebsd-update to do
the upgrade.

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (FreeBSD)

iEYEARECAAYFAkpw9ocACgkQi+vbBBjt66D2EQCdFEadtHLQWLezA36S3YvGC91M
PrEAni/cdKOx7546YQzEN42t51NxDBOg
=pEF3
-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: port net/openldap24-sasl-client fails to register as dependency

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Panagiotis Christias wrote:
 Hello,
 
 (I am adding freebsd-ports@ to the thread as you suggested)
 
 
 Xin LI wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi, Panagiotis,

 Panagiotis Christias wrote:
 Hello,

 I came across another dependency bug. It looks like packages that depend
 on net/openldap24-client (e.g. mail/sendmail-ldap, mail/dovecot with
 WITH_LDAP=true etc) fail to register the openldap dependency in systems
 that have net/openldap24-sasl-client port installed.

 I am aware of this problem but I don't have a good solution for it (at
 hand), this is an infrastructural issue with the ports dependency
 tracking - if two ports installs exactly the same files, there is no way
 to distinguish between the two without forcing to install one even if a
 conflicting one is already installed.
 
 Hm.. messy. How does lang/perl5.[6,8,10] handle such problems?

Install an entry into /etc/make.conf, I think it's Ok for perl (since
there are a lot of ports depends on it) but not for OpenLDAP...

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)

iEYEARECAAYFAkoUjvoACgkQi+vbBBjt66CxQgCgt5nbavwhqigC0olet1AJWO30
xVsAn28lB+20KTGRjKg1cSo3rjFL2aEq
=tTlz
-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: An enquiry about valgrind porting to FreeBSD

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Alexander Churanov wrote:
 Hi all!
 
 I am also interested in it. I have lots of questions about valgrind:
 
 1) Is it working at all? I always receive SIGBUS on 7x.
 2) Is our valgrind from http://valgrind.org/ or valgrind.kde.org?
 3) valgrind.org lists 3.4.1 as latest release, but there is 3.52 in
 ports, how is it possible?

That's Revision 352 and not 3.52 nor 3.5.2...

As far as I am aware Peter Wemm worked on a valgrind port which is
available on p4.  Haven't give it a twist yet as it seems that we need
more work for amd64...

 I am teaching people C, C++ and UNIX API using FreeBSD at university.
 There is a need for memory-checking tool. Does anybody know any
 alternatives for FreeBSD 7?
 
 Alexander Churanov


- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)

iEYEARECAAYFAkoDY4AACgkQi+vbBBjt66BmzgCfSA8k0n6iRFwBv/t6NdzqRSWT
Lo4AnRA0KiArezFOt5e429rafycoxDym
=JQif
-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: FREEORION port

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Gonzalo Martinez-Sanjuan Sanchez wrote:
 is someone working on fixing it?
 its marked as broken

The port seems to be unmaintained.  It looks like that there is a new
release, are you interested in updating the port?

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)

iEYEARECAAYFAknLvLEACgkQi+vbBBjt66CZJwCfcVrccJHAfHfdPD+nvCzDEuVA
xagAoJ/bkdTl0TThdS/LRB1EUBp2HdW5
=H7GS
-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: plees submit my ports/132555

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Vasiliy P. Melnik wrote:
 Hi.
 
 Plees submit my port ports/132555. Fixes only

Committed, thanks!

- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.11 (FreeBSD)

iEYEARECAAYFAkm5scEACgkQi+vbBBjt66Dp9ACgpmrEUaAt4jkaiRI4KriMBroY
pDMAmwXc8xP/GhLrmpnMEIMlx6kspkPn
=Z3nm
-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

[KDE4] Binaries not stripped

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

It looks like that the installed binaries are not stripped for all KDE4
related ports, is this intentional?

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.10 (FreeBSD)

iEYEARECAAYFAkmR1zUACgkQi+vbBBjt66Cp7QCcDDv0iez6DMsUOPMSoV3CnN6H
n0YAoIOQvBj0FKtLGB2RhHqC9pzG1Sj9
=JMdO
-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

Xorg strange behavior

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Is there anybody noticing that Xorg, when there is no mouse event, would
not respond to keyboard events?  Sometimes application would stall and
moving mouse would make it resume...

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.10 (FreeBSD)

iEYEARECAAYFAkmJWOYACgkQi+vbBBjt66C57gCdFZC1B2GcT/wyOoILtt1KHX3+
G1EAmgM8FXots2v4EfjuQAfAF5o981cc
=bSgJ
-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: Xorg strange behavior

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jung-uk Kim wrote:
 On Wednesday 04 February 2009 01:45 pm, Glen Barber wrote:
 On Wed, Feb 4, 2009 at 8:13 AM, L Campbell ll...@virginia.edu 
 wrote:
 I experienced the same symptoms after the recent upgrade. I found
 that rebuilding x11-servers/xorg-server without HAL fixed the
 problem. I think there are a couple of other ways to fix it, but
 AFAIK the root of the problem is HAL not playing nicely with
 other components (ie, moused).
 Interestingly, this solution did *not* work for me yesterday.  The
 only solution was to install the binary xorg-server and
 xorg-drivers.
 
 Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and 
 xorg-server-1.5.3_4,1, which I just committed.  If the problem does 
 not go away, please send us /var/log/Xorg.0.log.

I think it greatly improved the situation but not resolved completely.
By chance, it seems that the system would stop responding to keyboard
until I move mouse or the pointer stick.

This is a ThinkPad T61 with Logitech mouse plugged into USB.

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.10 (FreeBSD)

iEYEARECAAYFAkmKJvQACgkQi+vbBBjt66A6EQCfSFjj4pHhuTyxSeVm4a6fMCty
1+UAnA/UGe026Tz5b7RZ5Xy75gMEDy6I
=QsRL
-END PGP SIGNATURE-

X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 8.0-CURRENT amd64 
Current Operating System: FreeBSD charlie.delphij.net 8.0-CURRENT FreeBSD 
8.0-CURRENT #6 r188063MS: Tue Feb  3 00:24:29 PST 2009 
delp...@charlie.delphij.net:/download/obj/data/src/sys/CHARLIE amd64
Build Date: 04 February 2009  03:18:32PM
 
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Wed Feb  4 15:29:22 2009
(==) Using config file: /etc/X11/xorg.conf
(==) ServerLayout X.org Configured
(**) |--Screen Screen0 (0)
(**) |   |--Monitor Monitor0
(**) |   |--Device Card0
(**) |--Input Device Mouse0
(**) |--Input Device Keyboard0
(**) Option AllowEmptyInput off
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) `fonts.dir' not found (or not valid) in /usr/local/lib/X11/fonts/dejavu/.
Entry deleted from font path.
(Run 'mkfontdir' on /usr/local/lib/X11/fonts/dejavu/).
(==) Including the default font path 
/usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/.
(**) FontPath set to:
/usr/local/lib/X11/fonts/misc/,
/usr/local/lib/X11/fonts/TTF/,
/usr/local/lib/X11/fonts/TrueType/,
/usr/local/lib/X11/fonts/OTF,
/usr/local/lib/X11/fonts/Type1/,
/usr/local/lib/X11/fonts/100dpi/,
/usr/local/lib/X11/fonts/75dpi/,
/usr/local/lib/X11/fonts/misc/,
/usr/local/lib/X11/fonts/TTF/,
/usr/local/lib/X11/fonts/OTF,
/usr/local/lib/X11/fonts/Type1/,
/usr/local/lib/X11/fonts/100dpi/,
/usr/local/lib/X11/fonts/75dpi/
(**) ModulePath set to /usr/local/lib/xorg/modules
(II) Loader magic: 0x671d80
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on freebsd
(--) Using syscons driver with X support (version 2.0)
(--) using VT number 9

(--) PCI:*(0...@1:0:0) nVidia Corporation Quadro NVS 140M rev 161, Mem @ 
0xd600/16777216, 0xe000/268435456, 0xd400/33554432, I/O @ 
0x2000/128, BIOS @ 0x/65536
(II) System resource ranges:
[0] -1  0   0x0010 - 0x3fff (0x3ff0) MX[B]E(B)
[1] -1  0   0x000f - 0x000f (0x1) MX[B]
[2] -1  0   0x000c - 0x000e (0x3) MX[B]
[3] -1  0   0x - 0x0009 (0xa) MX[B]
[4] -1  0   0x - 0x (0x1) IX[B]
[5] -1  0   0x - 0x00ff (0x100) IX[B]
(II) extmod will be loaded. This was enabled by default and also specified in 
the config file.
(II) dbe will be loaded. This was enabled by default and also specified in 
the config file.
(II) glx will be loaded. This was enabled by default and also specified in 
the config file.
(II) freetype will be loaded. This was enabled by default and also specified 
in the config file.
(II) record will be loaded. This was enabled by default and also specified in 
the config file.
(II) dri will be loaded. This was enabled by default and also specified in 
the config file.
(II) LoadModule: record

(II) Loading /usr/local/lib

[RESOLVED] Re: Xorg strange behavior

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jung-uk Kim wrote:
 On Wednesday 04 February 2009 06:38 pm, Xin LI wrote:
 Jung-uk Kim wrote:
 On Wednesday 04 February 2009 01:45 pm, Glen Barber wrote:
 On Wed, Feb 4, 2009 at 8:13 AM, L Campbell ll...@virginia.edu
 wrote:
 I experienced the same symptoms after the recent upgrade. I
 found that rebuilding x11-servers/xorg-server without HAL fixed
 the problem. I think there are a couple of other ways to fix
 it, but AFAIK the root of the problem is HAL not playing nicely
 with other components (ie, moused).
 Interestingly, this solution did *not* work for me yesterday. 
 The only solution was to install the binary xorg-server and
 xorg-drivers.
 Please try hal-0.5.11_17, xf86-input-mouse-1.4.0_3, and
 xorg-server-1.5.3_4,1, which I just committed.  If the problem
 does not go away, please send us /var/log/Xorg.0.log.
 I think it greatly improved the situation but not resolved
 completely. By chance, it seems that the system would stop
 responding to keyboard until I move mouse or the pointer stick.

 This is a ThinkPad T61 with Logitech mouse plugged into USB.
 
 This is a symptom of openning /dev/sysmouse multiple times.  You have
 
 Option AllowEmptyInput off
 
 and there is a mouse section pointing to /dev/sysmouse in xorg.conf, 
 i.e., /dev/sysmouse is configured via your static configuration AND 
 via hald.
 
 - If you don't have to keep AllowEmptyInput, then just remove the 
 option.  The mouse section will be ignored and hald will do the right 
 thing now.
 
 - If you really have to keep AllowEmptyInput for some reason, then 
 you should remove mouse section from xorg.conf OR you may add 
 AutoAddDevices off in the server layout section.
 
 I hope it helps.

By removing Option AllowEmptyInput off the problem goes away (this
time, completely).  Thanks a lot!

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.10 (FreeBSD)

iEYEARECAAYFAkmKL3kACgkQi+vbBBjt66C+xwCfby4oj/VHKkc9hb4rcaNs6LaP
JxMAoJLNM9OPMbbpc7Z3zsHl9kdifvsa
=eUp3
-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: Source-upgrading FreeBSD breaks postfix+dovecot?

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Darren Pilgrim wrote:
 Tonight I source-upgraded a FreeBSD system from i386 6.3p5 to i386
 6.4-R.  I have postfix 2.5.5 and dovecot 1.1.7 installed with postfix
 using dovecot for SASL and dovecot LDA for mailbox delivery.  After
 installing 6.4-R, postfix refused to work until I recompiled and
 reinstalled both it and dovecot.  Dovecot itself (i.e., the IMAP server)
 worked fine.  Postfix worked fine if I set smtpd_sasl_auth_enable=no and
 defer_transports=dovecot, effectively preventing postfix from using any
 dovecot bits.  Examples of the logged errors:
 
 Before reinstalling anything:
 
 postfix/pipe[36617]: fatal: get_service_attr: unknown group: vmail

Sounds like that you have did something really bad during mergemaster?
(i.e. installed /etc/group without actually doing merge) and in turn the
group gets removed...

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAklimJ8ACgkQi+vbBBjt66DjLgCfRA6BkYJNlWm61kwhlLnuTPIV
A30AoJiUO62LHLxh1580eUqIK1I2YsZC
=f5gB
-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: OpenLDAP induced PORTREVISION bumps

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Jan Henrik Sylvester wrote:
 I just face many large ports requiring updates, although mine depend on
 openldap23-client, which have not been updated. Thus, I decided to
 investigate changing openldap23-client to openldap24-client.
 
 According to 'libchk -v', only 10 of 29 of my ports bumped actually link
 to one of the openldap libraries. (For example kdesdk3 does not link to
 it.) Do I miss something? Why have all these ports been bumped?
 
 devel/gconf2 did not get bumped, although it automatically picks up the
 dependency if openldap*-client is installed, which probably affects many
 people. Why? Because it does not affect the default package?

That's a good question.  In practice we bump PORTREVISION by parsing the
INDEX file which indicates the dependency relationship from package
build environment.  This way is effective if ports does not do things
like devel/gconf2 which picks up dependencies that has been installed,
as compared to doing 'grep WITH_LDAP */*/Makefile' or something similar,
as dependencies can be represented in different ways.

My (personal) opinion is that PORTREVISION should not be done at all and
the task of rebuilding depending ports should be done by more automated
tools, however currently our ports infrastructure is lacking of more
finer grained dependency describing information store that can act as
hint to port tools to make correct decisions :(

 If I update openldap23-client to openldap24-client, is it advisable to
 rebuild all packages depending on it (81) or just the 29 that got bumped
 plus gconf2? (According to UPDATING, it probably should be all.
 According to 'libchk -v', 10+1 should be enough.)

Some ports tools can keep old shared libraries into
/usr/local/lib/compat/; this way is likely to cause some problem in the
future if you mix different versions so it's advisable to rebuild *all*
packages that depends on it (81).

Cheers,
- --
Xin LI delp...@delphij.nethttp://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAklite0ACgkQi+vbBBjt66ClAACeIhsPUT8qGHVopcD0QoAJUAPZ
a0IAoMEZ4xAIAbfZ6Rr+L76EkLpWFk3F
=iXdM
-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

kde4 ports: installing non-stripped binaries?

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

It looks like we are installing non-stripped binaries of KDE4 ports:

[EMAIL PROTECTED] /usr/local/kde4/bin file /usr/local/kde4/bin/kfind
/usr/local/kde4/bin/kfind: ELF 64-bit LSB executable, x86-64, version 1
(FreeBSD), for FreeBSD 8.0 (800053), dynamically linked (uses shared
libs), FreeBSD-style, not stripped
[EMAIL PROTECTED] /usr/local/kde4/bin pkg_info -W /usr/local/kde4/bin/kfind
/usr/local/kde4/bin/kfind was installed by package kdebase-4.1.1

Is this intentional?

Cheers,
- --
Xin LI [EMAIL PROTECTED]  http://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkkhP98ACgkQi+vbBBjt66DbcQCgsvlpV7FNmSvOpfV9iMbLGQn3
iyAAn2C+6b+lch1tVNGVisR2iYTfYCgr
=JD6R
-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: Perl-5.8.10 release date?

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, Jerry,

Jerry wrote:
 I am assuming that Perl-5.8.10 is not going to be in the soon to be
 released FBSD-7.1; however, is there any word as to when it might
 actually be released? Unless I am mistaken, this version of Perl was
 released on Dec. 18, 2007. I realize that porting Perl to FBSD is no
 trivial task; all I was inquiring about is when it might get into the
 ports system.

Currently the ports tree is under a 'slush' state.  For this case I
think the most likely case is that we will not ship Perl 5.8.10 with
FreeBSD 7.1, but if someone would get a patch by that moment and gets
tested against the current ports collection, it would have its way into
7.2-RELEASE.

The most important thing is that someone :) do the porting work and
submit it to portmgr@ for a pointyhat twist.

Cheers,
- --
Xin LI [EMAIL PROTECTED]  http://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjtJYYACgkQi+vbBBjt66AhsQCfbe/V3mbGT5dN4nlKnsKkSwih
GQYAn2BJPefBwMn+fUVC9H4MUIsVrF9R
=TwNX
-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: textproc/flex (/usr/local/bin/flex) shadowed by /usr/bin/flex after install

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Steve Franks wrote:
 In maintaining devel/urjtag, I've added a dependancy to textproc/flex.
  On some systems, however, I've found that when textproc/flex gets
 installed, it lands in /usr/local/bin, as expected, but there's a
 /usr/bin/flex which precedes it in the path - is there a canonical way
 to resolve this?  I've just been mv'ing my /usr/bin/flex, but clearly,
 I can't add a patch to a port to do that to other people's systems...

Ah...  I feel astonished that flex lives in textproc/ as bison lived in
devel/...

I think what you have to do is:

BUILD_DEPENDS=  ${LOCALBASE}/bin/flex:${PORTSDIR}/textproc/flex

and do a post-patch action of
@${REINPLACE_CMD} -e 's, flex, ${LOCALBASE}/bin/flex,g'

or similar where necessary...

Cheers,
- --
Xin LI [EMAIL PROTECTED]  http://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjr2FwACgkQi+vbBBjt66DZsgCfYR0gtZuLNMHiKA4DWz4FuRbb
0M0AmwbnyP6yAPW9YeU/CMWNS1uCx/Ds
=WDK4
-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: feasibility of updating databases/mysql41-server?

[Xin LI]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Andrew Daugherity wrote:
 I still have a server running mysql 4.1.22, and it's marked as having the 
 MyISAM table privileges secuity [sic] bypass vulnerability.  According to 
 CVE-2008-2079 (linked from portaudit), this is fixed in 4.1.24.
 
 I was going to file a PR asking for an update to 4.1.24, but then I 
 discovered that MySQL 4.1 is in the extended support phase where they 
 aren't releasing tarballs any more (and of course no binaries).  The source 
 *is* still available, but it's in the bazaar repo (see: 
 http://blogs.sun.com/datacharmer/entry/hidden_jevewls_in_mysql_bazaar ).  
 This can be checked out and built, but having a build-dep of bzr is probably 
 not wanted.
 
 Is it feasible (both license-wise and technically) to have a mirror of  a 
 4.1.24 bzr checkout in tarball form somewhere, so the port can be built?

Yes, but for this case I think the more preferred way would be to obtain
the fix from repository and apply it in files/ as a patch.  This makes
reviewing the code much easier.

Cheers,
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkjd5C0ACgkQi+vbBBjt66CQ6wCbBYJAysE7YzcCaHwRyvcVfuya
GnMAnjAIHEgf5ABw2/57dmWnIy1I+ocn
=WZdp
-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]