Re: [HEADS-UP] Announcing the end of port CVS
On 9 Sep 2012 00:11, Jeffrey Bouquet jeffreybouq...@yahoo.com wrote: --- On Sat, 9/8/12, Kevin Oberman kob6...@gmail.com wrote: From: Kevin Oberman kob6...@gmail.com Subject: Re: [HEADS-UP] Announcing the end of port CVS To: Jamie Paul Griffin ja...@osx.kode5.net Cc: freebsd-ports@freebsd.org Date: Saturday, September 8, 2012, 2:42 PM On Sat, Sep 8, 2012 at 3:09 AM, Jamie Paul Griffin ja...@osx.kode5.net wrote: [ Lars Eighner wrote on Fri 7.Sep'12 at 10:00:45 -0500 ] On Fri, 7 Sep 2012, Beat Gaetzi wrote: The development of FreeBSD ports is done in Subversion nowadays. For the sake of compatibility a Subversion to CVS exporter is in place which has some limitations. For CVSup mirroring cvsup based on Ezm3 is used which breaks regularly especially on amd64 and with Clang and becomes more and more unmaintainable. What exactly is the motivation again for moving from things which work like cvsup and gcc to things that are broken or lame like subversion and clang? They're not broken. I've recently been using them and they're fine. There has been plenty of discussion about the reasons for the changes so have a read from the various sites and list archives. Looks like a troll to me. No one who has worked with subversion for a project of any size would ever want to go back to CVS. While still having some of CVS's limitations, it does far, far more and is much easier to work with for most things. I really miss the forced commit and, for one application, RANCiD, I use CVS so I can grep through the ,v files easily. But I can't see any reason for FreeBSD not to move the the more advanced system. As to clang, there is no choice there. The license on newer version of gcc (GPLv3) is simply not acceptable to the community, so gcc is stuck forever at 4.2 which is getting very old. clang has excellent development support, an acceptable license, and early tests show that it generally compiles faster and MAY even generate better, faster code. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ 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 I'd not go so far as to label it trolling ... I searched quite a bit upon this announcement to find csup svn equivalent guides and found little applying to ports... hopefully they will appear prior to the changeover?, something easily learned? (disregarding portsnap for the moment, and I apologize...) (the .htm I saved from the web searches (svn) appear too complex and irrelevant to this use case to be of use here...) For end users portsnap has been a better solution for a long time; it's faster and also secure; the snapshots are signed. Perhaps you should give it a try, sine you correctly point out that Subversion is a pain to install. Chris ___ 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 port
Olli Hauer: Hi Jos, it's easy, even quickly overseen DBD != BDB AUTHN_DBD and DBD are SQL modules and this apache options are only valid if APR was build with MYSQL, PGSQL or SQLITE support. In the past we ask the user to specify if APR was build with SQL support, now the port checks the existence of lib/apr-util-1/apr_dbd_(mysql|pgsql|sqlite).so to see if APR was really build with SQL support. http://httpd.apache.org/docs/2.2/mod/mod_dbd.html http://httpd.apache.org/docs/2.2/mod/mod_authn_dbd.html I am not a programmer, but what should I do to get rid of this situation? I do use Apache with MySQL and have recompiled APR with the right options. kind regards, Jos ___ 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 port
Olli, This is my current setup of Apache: === The following configuration options are available for apache22-2.2.22_8: AUTH_BASIC=on: mod_auth_basic AUTH_DIGEST=on: mod_auth_digest AUTHN_ALIAS=on: mod_authn_alias AUTHN_ANON=on: mod_authn_anon AUTHN_DBD=on: mod_authn_dbd AUTHN_DBM=on: mod_authn_dbm AUTHN_DEFAULT=on: mod_authn_default AUTHN_FILE=on: mod_authn_file AUTHZ_DBM=off: mod_authz_dbm AUTHZ_DEFAULT=on: mod_authz_default AUTHZ_GROUPFILE=on: mod_authz_groupfile AUTHZ_HOST=on: mod_authz_host AUTHZ_OWNER=on: mod_authz_owner AUTHZ_USER=on: mod_authz_user AUTHNZ_LDAP=off: mod_authnz_ldap LDAP=off: connection pooling, result caching DBD=on: Manages SQL database connections CACHE=on: mod_cache DISK_CACHE=on: mod_disk_cache FILE_CACHE=on: mod_file_cache --- cut --- and this for APR: _OPTIONS_READ=apr-1.4.6.1.4.1_1 _FILE_COMPLETE_OPTIONS_LIST= THREADS IPV6 DEVRANDOM BDB GDBM LDAP MYSQL NDBM PGSQL SQLITE OPTIONS_FILE_SET+=THREADS OPTIONS_FILE_SET+=IPV6 OPTIONS_FILE_SET+=DEVRANDOM OPTIONS_FILE_SET+=BDB OPTIONS_FILE_SET+=GDBM OPTIONS_FILE_UNSET+=LDAP OPTIONS_FILE_UNSET+=MYSQL OPTIONS_FILE_UNSET+=NDBM OPTIONS_FILE_UNSET+=PGSQL OPTIONS_FILE_UNSET+=SQLITE and I still get the error. This is the content of the key folder your are scanning on for the check: Aegir[/usr/local/lib/apr-util-1] -rwxr-xr-x 1 root wheel 57719 Sep 9 12:38 apr_dbd_mysql-1.so -rw-r--r-- 1 root wheel 60214 Sep 9 12:38 apr_dbd_mysql.a -rwxr-xr-x 1 root wheel 1073 Sep 9 12:38 apr_dbd_mysql.la lrwxr-xr-x 1 root wheel 18 Sep 9 12:38 apr_dbd_mysql.so - apr_dbd_mysql-1.so -rwxr-xr-x 1 root wheel 43272 Sep 9 12:38 apr_dbm_db-1.so -rw-r--r-- 1 root wheel 49894 Sep 9 12:38 apr_dbm_db.a -rwxr-xr-x 1 root wheel 1005 Sep 9 12:38 apr_dbm_db.la lrwxr-xr-x 1 root wheel 15 Sep 9 12:38 apr_dbm_db.so - apr_dbm_db-1.so -rwxr-xr-x 1 root wheel 13722 Sep 9 12:38 apr_dbm_gdbm-1.so -rw-r--r-- 1 root wheel 11466 Sep 9 12:38 apr_dbm_gdbm.a -rwxr-xr-x 1 root wheel 1036 Sep 9 12:38 apr_dbm_gdbm.la lrwxr-xr-x 1 root wheel 17 Sep 9 12:38 apr_dbm_gdbm.so - apr_dbm_gdbm-1.so -rwxr-xr-x 1 root wheel 42080 Sep 9 12:38 apr_dbm_ndbm-1.so -rw-r--r-- 1 root wheel 47762 Sep 9 12:38 apr_dbm_ndbm.a -rwxr-xr-x 1 root wheel 1010 Sep 9 12:38 apr_dbm_ndbm.la lrwxr-xr-x 1 root wheel 17 Sep 9 12:38 apr_dbm_ndbm.so - apr_dbm_ndbm-1.so -rwxr-xr-x 1 root wheel 20666 Sep 9 12:38 apr_ldap-1.so -rw-r--r-- 1 root wheel 24112 Sep 9 12:38 apr_ldap.a -rwxr-xr-x 1 root wheel 1049 Sep 9 12:38 apr_ldap.la lrwxr-xr-x 1 root wheel 13 Sep 9 12:38 apr_ldap.so - apr_ldap-1.so the files you are scanning for are not there as they have a complete different name. apr_dbd_mysql-1.so apr_dbm_db-1.so Perhaps that is the cause I can't install the apache22 upgrade? Olli Hauer: On 2012-09-08 17:58, Warren Block wrote: On Sat, 8 Sep 2012, Olli Hauer wrote: On 2012-09-08 16:22, Jos Chrispijn wrote: Just updating Apache22 (apache-2.2.22_6) and get this error: Port marked as IGNORE: www/apache22: AUTHN_DBD and DBD requires APR-util to have DBD support build in. Please rebuild APR at last with one DBD backend The issue is that I did config APR with DBD support. Currently have installed: apr-1.4.6.1.4.1_1 Apache Portability Library My /var/db/ports/apr/options file contains: # Options for apr-1.4.6.1.4.1_1 _OPTIONS_READ=apr-1.4.6.1.4.1_1 _FILE_COMPLETE_OPTIONS_LIST= THREADS IPV6 DEVRANDOM BDB GDBM LDAP MYSQL NDBM PGSQL SQLITE OPTIONS_FILE_SET+=THREADS OPTIONS_FILE_SET+=IPV6 OPTIONS_FILE_SET+=DEVRANDOM OPTIONS_FILE_SET+=BDB OPTIONS_FILE_SET+=GDBM OPTIONS_FILE_UNSET+=LDAP OPTIONS_FILE_UNSET+=MYSQL OPTIONS_FILE_UNSET+=NDBM OPTIONS_FILE_UNSET+=PGSQL OPTIONS_FILE_UNSET+=SQLITE Can someone tell me how what I do wrong here? Hi Jos, it's easy, even quickly overseen DBD != BDB AUTHN_DBD and DBD are SQL modules and this apache options are only valid if APR was build with MYSQL, PGSQL or SQLITE support. In the past we ask the user to specify if APR was build with SQL support, now the port checks the existence of lib/apr-util-1/apr_dbd_(mysql|pgsql|sqlite).so to see if APR was really build with SQL support. http://httpd.apache.org/docs/2.2/mod/mod_dbd.html http://httpd.apache.org/docs/2.2/mod/mod_authn_dbd.html How about adding mention of SQL in the IGNORE message? I will rewrite the message to Please rebuild APR at last with one DBD backend (MYSQL, PGSQL or SQLITE) Hope then is is more clear. ___ 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 port
Sorry, it should work as there is a symbolic link for the one you are searching for... Really don't understand why I still get the port is IGNORED line on portupgrade -a Jos Jos Chrispijn: Olli, This is my current setup of Apache: === The following configuration options are available for apache22-2.2.22_8: AUTH_BASIC=on: mod_auth_basic AUTH_DIGEST=on: mod_auth_digest AUTHN_ALIAS=on: mod_authn_alias AUTHN_ANON=on: mod_authn_anon AUTHN_DBD=on: mod_authn_dbd AUTHN_DBM=on: mod_authn_dbm AUTHN_DEFAULT=on: mod_authn_default AUTHN_FILE=on: mod_authn_file AUTHZ_DBM=off: mod_authz_dbm AUTHZ_DEFAULT=on: mod_authz_default AUTHZ_GROUPFILE=on: mod_authz_groupfile AUTHZ_HOST=on: mod_authz_host AUTHZ_OWNER=on: mod_authz_owner AUTHZ_USER=on: mod_authz_user AUTHNZ_LDAP=off: mod_authnz_ldap LDAP=off: connection pooling, result caching DBD=on: Manages SQL database connections CACHE=on: mod_cache DISK_CACHE=on: mod_disk_cache FILE_CACHE=on: mod_file_cache --- cut --- and this for APR: _OPTIONS_READ=apr-1.4.6.1.4.1_1 _FILE_COMPLETE_OPTIONS_LIST= THREADS IPV6 DEVRANDOM BDB GDBM LDAP MYSQL NDBM PGSQL SQLITE OPTIONS_FILE_SET+=THREADS OPTIONS_FILE_SET+=IPV6 OPTIONS_FILE_SET+=DEVRANDOM OPTIONS_FILE_SET+=BDB OPTIONS_FILE_SET+=GDBM OPTIONS_FILE_UNSET+=LDAP OPTIONS_FILE_UNSET+=MYSQL OPTIONS_FILE_UNSET+=NDBM OPTIONS_FILE_UNSET+=PGSQL OPTIONS_FILE_UNSET+=SQLITE and I still get the error. This is the content of the key folder your are scanning on for the check: Aegir[/usr/local/lib/apr-util-1] -rwxr-xr-x 1 root wheel 57719 Sep 9 12:38 apr_dbd_mysql-1.so -rw-r--r-- 1 root wheel 60214 Sep 9 12:38 apr_dbd_mysql.a -rwxr-xr-x 1 root wheel 1073 Sep 9 12:38 apr_dbd_mysql.la lrwxr-xr-x 1 root wheel 18 Sep 9 12:38 apr_dbd_mysql.so - apr_dbd_mysql-1.so -rwxr-xr-x 1 root wheel 43272 Sep 9 12:38 apr_dbm_db-1.so -rw-r--r-- 1 root wheel 49894 Sep 9 12:38 apr_dbm_db.a -rwxr-xr-x 1 root wheel 1005 Sep 9 12:38 apr_dbm_db.la lrwxr-xr-x 1 root wheel 15 Sep 9 12:38 apr_dbm_db.so - apr_dbm_db-1.so -rwxr-xr-x 1 root wheel 13722 Sep 9 12:38 apr_dbm_gdbm-1.so -rw-r--r-- 1 root wheel 11466 Sep 9 12:38 apr_dbm_gdbm.a -rwxr-xr-x 1 root wheel 1036 Sep 9 12:38 apr_dbm_gdbm.la lrwxr-xr-x 1 root wheel 17 Sep 9 12:38 apr_dbm_gdbm.so - apr_dbm_gdbm-1.so -rwxr-xr-x 1 root wheel 42080 Sep 9 12:38 apr_dbm_ndbm-1.so -rw-r--r-- 1 root wheel 47762 Sep 9 12:38 apr_dbm_ndbm.a -rwxr-xr-x 1 root wheel 1010 Sep 9 12:38 apr_dbm_ndbm.la lrwxr-xr-x 1 root wheel 17 Sep 9 12:38 apr_dbm_ndbm.so - apr_dbm_ndbm-1.so -rwxr-xr-x 1 root wheel 20666 Sep 9 12:38 apr_ldap-1.so -rw-r--r-- 1 root wheel 24112 Sep 9 12:38 apr_ldap.a -rwxr-xr-x 1 root wheel 1049 Sep 9 12:38 apr_ldap.la lrwxr-xr-x 1 root wheel 13 Sep 9 12:38 apr_ldap.so - apr_ldap-1.so the files you are scanning for are not there as they have a complete different name. apr_dbd_mysql-1.so apr_dbm_db-1.so Perhaps that is the cause I can't install the apache22 upgrade? Olli Hauer: On 2012-09-08 17:58, Warren Block wrote: On Sat, 8 Sep 2012, Olli Hauer wrote: On 2012-09-08 16:22, Jos Chrispijn wrote: Just updating Apache22 (apache-2.2.22_6) and get this error: Port marked as IGNORE: www/apache22: AUTHN_DBD and DBD requires APR-util to have DBD support build in. Please rebuild APR at last with one DBD backend The issue is that I did config APR with DBD support. Currently have installed: apr-1.4.6.1.4.1_1 Apache Portability Library My /var/db/ports/apr/options file contains: # Options for apr-1.4.6.1.4.1_1 _OPTIONS_READ=apr-1.4.6.1.4.1_1 _FILE_COMPLETE_OPTIONS_LIST= THREADS IPV6 DEVRANDOM BDB GDBM LDAP MYSQL NDBM PGSQL SQLITE OPTIONS_FILE_SET+=THREADS OPTIONS_FILE_SET+=IPV6 OPTIONS_FILE_SET+=DEVRANDOM OPTIONS_FILE_SET+=BDB OPTIONS_FILE_SET+=GDBM OPTIONS_FILE_UNSET+=LDAP OPTIONS_FILE_UNSET+=MYSQL OPTIONS_FILE_UNSET+=NDBM OPTIONS_FILE_UNSET+=PGSQL OPTIONS_FILE_UNSET+=SQLITE Can someone tell me how what I do wrong here? Hi Jos, it's easy, even quickly overseen DBD != BDB AUTHN_DBD and DBD are SQL modules and this apache options are only valid if APR was build with MYSQL, PGSQL or SQLITE support. In the past we ask the user to specify if APR was build with SQL support, now the port checks the existence of lib/apr-util-1/apr_dbd_(mysql|pgsql|sqlite).so to see if APR was really build with SQL support. http://httpd.apache.org/docs/2.2/mod/mod_dbd.html http://httpd.apache.org/docs/2.2/mod/mod_authn_dbd.html How about adding mention of SQL in the IGNORE message? I will rewrite the message to Please rebuild APR at last with one DBD backend (MYSQL, PGSQL or SQLITE) Hope then is is more clear. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to
Re: Apache port
On 2012-09-09 12:58, Jos Chrispijn wrote:
Sorry, it should work as there is a symbolic link for the one you are
searching for...
Really don't understand why I still get the port is IGNORED line on
portupgrade -a
Jos
Jos Chrispijn:
Olli,
This is my current setup of Apache:
=== The following configuration options are available for apache22-2.2.22_8:
AUTH_BASIC=on: mod_auth_basic
AUTH_DIGEST=on: mod_auth_digest
AUTHN_ALIAS=on: mod_authn_alias
AUTHN_ANON=on: mod_authn_anon
AUTHN_DBD=on: mod_authn_dbd
AUTHN_DBM=on: mod_authn_dbm
AUTHN_DEFAULT=on: mod_authn_default
AUTHN_FILE=on: mod_authn_file
AUTHZ_DBM=off: mod_authz_dbm
AUTHZ_DEFAULT=on: mod_authz_default
AUTHZ_GROUPFILE=on: mod_authz_groupfile
AUTHZ_HOST=on: mod_authz_host
AUTHZ_OWNER=on: mod_authz_owner
AUTHZ_USER=on: mod_authz_user
AUTHNZ_LDAP=off: mod_authnz_ldap
LDAP=off: connection pooling, result caching
DBD=on: Manages SQL database connections
CACHE=on: mod_cache
DISK_CACHE=on: mod_disk_cache
FILE_CACHE=on: mod_file_cache
--- cut ---
and this for APR:
_OPTIONS_READ=apr-1.4.6.1.4.1_1
_FILE_COMPLETE_OPTIONS_LIST= THREADS IPV6 DEVRANDOM BDB GDBM LDAP MYSQL NDBM
PGSQL SQLITE
OPTIONS_FILE_SET+=THREADS
OPTIONS_FILE_SET+=IPV6
OPTIONS_FILE_SET+=DEVRANDOM
OPTIONS_FILE_SET+=BDB
OPTIONS_FILE_SET+=GDBM
OPTIONS_FILE_UNSET+=LDAP
OPTIONS_FILE_UNSET+=MYSQL
OPTIONS_FILE_UNSET+=NDBM
OPTIONS_FILE_UNSET+=PGSQL
OPTIONS_FILE_UNSET+=SQLITE
and I still get the error.
This is the content of the key folder your are scanning on for the check:
Aegir[/usr/local/lib/apr-util-1]
-rwxr-xr-x 1 root wheel 57719 Sep 9 12:38 apr_dbd_mysql-1.so
-rw-r--r-- 1 root wheel 60214 Sep 9 12:38 apr_dbd_mysql.a
-rwxr-xr-x 1 root wheel 1073 Sep 9 12:38 apr_dbd_mysql.la
lrwxr-xr-x 1 root wheel 18 Sep 9 12:38 apr_dbd_mysql.so -
apr_dbd_mysql-1.so
-rwxr-xr-x 1 root wheel 43272 Sep 9 12:38 apr_dbm_db-1.so
-rw-r--r-- 1 root wheel 49894 Sep 9 12:38 apr_dbm_db.a
-rwxr-xr-x 1 root wheel 1005 Sep 9 12:38 apr_dbm_db.la
lrwxr-xr-x 1 root wheel 15 Sep 9 12:38 apr_dbm_db.so -
apr_dbm_db-1.so
-rwxr-xr-x 1 root wheel 13722 Sep 9 12:38 apr_dbm_gdbm-1.so
-rw-r--r-- 1 root wheel 11466 Sep 9 12:38 apr_dbm_gdbm.a
-rwxr-xr-x 1 root wheel 1036 Sep 9 12:38 apr_dbm_gdbm.la
lrwxr-xr-x 1 root wheel 17 Sep 9 12:38 apr_dbm_gdbm.so -
apr_dbm_gdbm-1.so
-rwxr-xr-x 1 root wheel 42080 Sep 9 12:38 apr_dbm_ndbm-1.so
-rw-r--r-- 1 root wheel 47762 Sep 9 12:38 apr_dbm_ndbm.a
-rwxr-xr-x 1 root wheel 1010 Sep 9 12:38 apr_dbm_ndbm.la
lrwxr-xr-x 1 root wheel 17 Sep 9 12:38 apr_dbm_ndbm.so -
apr_dbm_ndbm-1.so
-rwxr-xr-x 1 root wheel 20666 Sep 9 12:38 apr_ldap-1.so
-rw-r--r-- 1 root wheel 24112 Sep 9 12:38 apr_ldap.a
-rwxr-xr-x 1 root wheel 1049 Sep 9 12:38 apr_ldap.la
lrwxr-xr-x 1 root wheel 13 Sep 9 12:38 apr_ldap.so - apr_ldap-1.so
the files you are scanning for are not there as they have a complete
different name.
apr_dbd_mysql-1.so
apr_dbm_db-1.so
Perhaps that is the cause I can't install the apache22 upgrade?
Hi Jos,
I just look into this.
Do you get the error message, or does the build not finish?
- apache22-2.2.22_8 AUTHN_DBD and DBD requires APR-util to ...
I really don't know why, maybe the make exists check gives on your machine a
different result for softlinks back ...
Please test with the following workaround until I find out what went wrong
( Replace IGNOR= with .warning )
===
--- Makefile.modules(revision 303958)
+++ Makefile.modules(working copy)
@@ -42,7 +42,7 @@
. if ${PORT_OPTIONS:MDBD} || ${PORT_OPTIONS:MAUTHN_DBD}
.if !exists(${APU_DBD_MYSQL}) !exists(${APU_DBD_PGSQL})
!exists(${APU_DBD_SQLITE3})
-IGNORE=AUTHN_DBD and DBD requires APR-util to have DBD support build
in.\
+.warning AUTHN_DBD and DBD requires APR-util to have DBD support build in.\
Please rebuild APR at last with one DBD backend (MYSQL, PGSQL or SQLITE)
.endif
. 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: Upgrade java/icedtea-web from 1.2_2 - 1.3 fails: tar: Pathname in pax header can't be converted to current locale
On Sat, Sep 08, 2012 at 07:00:24PM +0300, Kimmo Paasiala wrote: ... I can extract the tar file on 9-STABLE, my locale settings are the defaults for root: # locale LANG= LC_CTYPE=C LC_COLLATE=C LC_TIME=C LC_NUMERIC=C LC_MONETARY=C LC_MESSAGES=C LC_ALL= Try unsetting LANG and LC_ALL. I just tried a further experiment, while running head (@r240235): I issued tar tvf /usr/ports/distfiles/icedtea-web-1.3.tar.gz The error messages are worded slightly differently: g1-227(10.0-C)[4] tar -tvf /usr/ports/distfiles/icedtea-web-1.3.tar.gz drwxrwxr-x 0 dbhole dbhole 0 Aug 27 12:37 icedtea-web-1.3/ ... drwxrwxr-x 0 dbhole dbhole 0 Aug 27 12:36 icedtea-web-1.3/tests/reproducers/signed/Spaces can be everywhere signed/resources/ tar: Pathname can't be converted from UTF-8 to current locale. -rw-rw-r-- 0 dbhole dbhole 2421 Aug 27 12:36 icedtea-web-1.3/tests/reproducers/signed/Spaces can be everywhere signed/resources/NotOnly spaces can kill \304\233\305\241\304\215\305\231\305\276 too signed.jnlp ... drwxrwxr-x 0 dbhole dbhole 0 Aug 27 12:36 icedtea-web-1.3/tests/reproducers/simple/Spaces can be everywhere/resources/ tar: Pathname can't be converted from UTF-8 to current locale. -rw-rw-r-- 0 dbhole dbhole 2388 Aug 27 12:36 icedtea-web-1.3/tests/reproducers/simple/Spaces can be everywhere/resources/NotOnly spaces can kill \304\233\305\241\304\215\305\231\305\276 too.jnlp ... -rw-rw-r-- 0 dbhole dbhole 5756 Aug 27 12:36 icedtea-web-1.3/README tar: Error exit delayed from previous errors. g1-227(10.0-C)[5] So the issue appears to be how to handle UTF-8 pathnames on the file system in question. I'm using a fairly plain UFS with soft updates. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpH0GHg20XZZ.pgp Description: PGP signature
Re: [HEADS-UP] Announcing the end of port CVS
On Sun, Sep 9, 2012 at 8:15 AM, Kevin Oberman kob6...@gmail.com wrote: 2. Select US east coast or US west as your server. Pick at random or pick the one closer to you. What if neither is close to me (there are other countries in the world, not only USA, some are even on the other side of the planet, btw, did you know?) ? -- Alexandr Kovalenko ___ 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: Upgrade java/icedtea-web from 1.2_2 - 1.3 fails: tar: Pathname in pax header can't be converted to current locale
On Sun, Sep 9, 2012 at 3:33 PM, David Wolfskill da...@catwhisker.org wrote: On Sat, Sep 08, 2012 at 07:00:24PM +0300, Kimmo Paasiala wrote: ... I can extract the tar file on 9-STABLE, my locale settings are the defaults for root: # locale LANG= LC_CTYPE=C LC_COLLATE=C LC_TIME=C LC_NUMERIC=C LC_MONETARY=C LC_MESSAGES=C LC_ALL= Try unsetting LANG and LC_ALL. I just tried a further experiment, while running head (@r240235): I issued tar tvf /usr/ports/distfiles/icedtea-web-1.3.tar.gz The error messages are worded slightly differently: g1-227(10.0-C)[4] tar -tvf /usr/ports/distfiles/icedtea-web-1.3.tar.gz drwxrwxr-x 0 dbhole dbhole 0 Aug 27 12:37 icedtea-web-1.3/ ... drwxrwxr-x 0 dbhole dbhole 0 Aug 27 12:36 icedtea-web-1.3/tests/reproducers/signed/Spaces can be everywhere signed/resources/ tar: Pathname can't be converted from UTF-8 to current locale. -rw-rw-r-- 0 dbhole dbhole 2421 Aug 27 12:36 icedtea-web-1.3/tests/reproducers/signed/Spaces can be everywhere signed/resources/NotOnly spaces can kill \304\233\305\241\304\215\305\231\305\276 too signed.jnlp ... drwxrwxr-x 0 dbhole dbhole 0 Aug 27 12:36 icedtea-web-1.3/tests/reproducers/simple/Spaces can be everywhere/resources/ tar: Pathname can't be converted from UTF-8 to current locale. -rw-rw-r-- 0 dbhole dbhole 2388 Aug 27 12:36 icedtea-web-1.3/tests/reproducers/simple/Spaces can be everywhere/resources/NotOnly spaces can kill \304\233\305\241\304\215\305\231\305\276 too.jnlp ... -rw-rw-r-- 0 dbhole dbhole 5756 Aug 27 12:36 icedtea-web-1.3/README tar: Error exit delayed from previous errors. g1-227(10.0-C)[5] So the issue appears to be how to handle UTF-8 pathnames on the file system in question. I'm using a fairly plain UFS with soft updates. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. See if the the file with a UTF-8 filename gets extracted despite the error message. I have three different FreeBSD 9 system, one is ZFS and other two are UFS. I can do 'make extract patch' on all of them for java/icedtea-web without an error. They all report the same error though if I manually view or extract the tar file, the files extract fine despite the error message. ___ 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: [HEADS-UP] Announcing the end of port CVS
On 09/07/2012 07:36 AM, Beat Gaetzi wrote: For those reasons by February 28th 2013 the FreeBSD ports tree will no longer be exported to CVS. This question is curiosity more than anything else. What will happen to the existing ports cvs. Will it merely stagnate, or will it be removed? What I mean by this is if my cvsup-file is *default host=cvsup11.freebsd.org *default prefix=/usr/home/library/ctm/FreeBSD/FreeBSD-CVS *default base=/usr/home/library/ctm/FreeBSD/FreeBSD-CVS *default release=cvs delete use-rel-suffix cvs-all then when I run this in Feb 28, will the ports subdirectory merely be unchanged, or will it be deleted in its entirety? ___ 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: Upgrade java/icedtea-web from 1.2_2 - 1.3 fails: tar: Pathname in pax header can't be converted to current locale
On Sun, Sep 09, 2012 at 04:44:08PM +0300, Kimmo Paasiala wrote: $... So the issue appears to be how to handle UTF-8 pathnames on the file system in question. I'm using a fairly plain UFS with soft updates. ... See if the the file with a UTF-8 filename gets extracted despite the error message. Huh; interesting point. Yes, it appears that they do: g1-227(8.3-S)[12] ls -Fs icedtea-web-1.3/tests/reproducers/signed/Spaces\ can\ be\ everywhere\ signed/resources/ 4 NotOnly spaces can kill ?? too signed.jnlp 4 Spaces can be everywhere1 signed.jnlp 4 Spaces can be everywhere2 signed.jnlp 4 SpacesCanBeEverywhere1signed.jnlp 4 spaces applet Tests signed.html g1-227(8.3-S)[13] ls -Fs icedtea-web-1.3/tests/reproducers/simple/Spaces\ can\ be\ everywhere/resources/ 4 NotOnly spaces can kill ?? too.jnlp 4 Spaces can be everywhere1.jnlp 4 Spaces can be everywhere2.jnlp 4 SpacesCanBeEverywhere1.jnlp 4 spaces applet Tests.html g1-227(8.3-S)[14] (The files with names that display as having '?' in their names would be the files in question.) I have three different FreeBSD 9 system, one is ZFS and other two are UFS. I can do 'make extract patch' on all of them for java/icedtea-web without an error. They all report the same error though if I manually view or extract the tar file, the files extract fine despite the error message. Hmmm. How do you do that? :-} Even trying a simple approach: g1-227(8.3-S)[1] cd /usr/ports/java/icedtea-web/ g1-227(8.3-S)[2] sudo make Password: === License GPLv2 accepted by the user === Found saved configuration for icedtea-web-1.2_2 === Extracting for icedtea-web-1.3 = SHA256 Checksum OK for icedtea-web-1.3.tar.gz. IMPORTANT: To build IcedTea-Web 1.3, you have to turn on 'ICEDTEA' option for java/openjdk6 (default). Otherwise, it will neither build nor work. tar: Pathname in pax header can't be converted to current locale. tar: Pathname in pax header can't be converted to current locale. tar: Error exit delayed from previous errors. *** Error code 1 Stop in /common/ports/java/icedtea-web. *** Error code 1 Stop in /common/ports/java/icedtea-web. g1-227(8.3-S)[3] I *suppose* I could try manually extracting it, then -- using the observation that the files actually are extracted -- hack the work/.* files to convince the ports infrastructure that the extraction is already completed OK, but that's just... wrong. Thanks for your help so far! Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpBm1ujknYw8.pgp Description: PGP signature
Re: Upgrade java/icedtea-web from 1.2_2 - 1.3 fails: tar: Pathname in pax header can't be converted to current locale
On Sun, Sep 9, 2012 at 6:12 PM, David Wolfskill da...@catwhisker.org wrote: On Sun, Sep 09, 2012 at 04:44:08PM +0300, Kimmo Paasiala wrote: $... So the issue appears to be how to handle UTF-8 pathnames on the file system in question. I'm using a fairly plain UFS with soft updates. ... See if the the file with a UTF-8 filename gets extracted despite the error message. Huh; interesting point. Yes, it appears that they do: g1-227(8.3-S)[12] ls -Fs icedtea-web-1.3/tests/reproducers/signed/Spaces\ can\ be\ everywhere\ signed/resources/ 4 NotOnly spaces can kill ?? too signed.jnlp 4 Spaces can be everywhere1 signed.jnlp 4 Spaces can be everywhere2 signed.jnlp 4 SpacesCanBeEverywhere1signed.jnlp 4 spaces applet Tests signed.html g1-227(8.3-S)[13] ls -Fs icedtea-web-1.3/tests/reproducers/simple/Spaces\ can\ be\ everywhere/resources/ 4 NotOnly spaces can kill ?? too.jnlp 4 Spaces can be everywhere1.jnlp 4 Spaces can be everywhere2.jnlp 4 SpacesCanBeEverywhere1.jnlp 4 spaces applet Tests.html g1-227(8.3-S)[14] (The files with names that display as having '?' in their names would be the files in question.) I have three different FreeBSD 9 system, one is ZFS and other two are UFS. I can do 'make extract patch' on all of them for java/icedtea-web without an error. They all report the same error though if I manually view or extract the tar file, the files extract fine despite the error message. Hmmm. How do you do that? :-} Even trying a simple approach: g1-227(8.3-S)[1] cd /usr/ports/java/icedtea-web/ g1-227(8.3-S)[2] sudo make Password: === License GPLv2 accepted by the user === Found saved configuration for icedtea-web-1.2_2 === Extracting for icedtea-web-1.3 = SHA256 Checksum OK for icedtea-web-1.3.tar.gz. IMPORTANT: To build IcedTea-Web 1.3, you have to turn on 'ICEDTEA' option for java/openjdk6 (default). Otherwise, it will neither build nor work. tar: Pathname in pax header can't be converted to current locale. tar: Pathname in pax header can't be converted to current locale. tar: Error exit delayed from previous errors. *** Error code 1 Stop in /common/ports/java/icedtea-web. *** Error code 1 Stop in /common/ports/java/icedtea-web. g1-227(8.3-S)[3] I *suppose* I could try manually extracting it, then -- using the observation that the files actually are extracted -- hack the work/.* files to convince the ports infrastructure that the extraction is already completed OK, but that's just... wrong. Thanks for your help so far! Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. Hmm, you're using sudo(1) and that means you enviroment may not be completely clean. Log on as root using 'su -l' and see if it makes a difference. ___ 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: Upgrade java/icedtea-web from 1.2_2 - 1.3 fails: tar: Pathname in pax header can't be converted to current locale
On Sun, Sep 09, 2012 at 06:16:20PM +0300, Kimmo Paasiala wrote: ... Hmm, you're using sudo(1) and that means you enviroment may not be completely clean. Log on as root using 'su -l' and see if it makes a difference. Well, despite my earlier experiments with LC_ALL friends, su - allows the make to complete. I'll research the environment differences to see if there's anything I can learn from that. Thanks again! Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpVPFBeQhHS6.pgp Description: PGP signature
Re: apache 2.2.22_6 to _8 fails
Helmut Schneider wrote:
Hi Olli,
olli hauer wrote:
On 2012-09-08 14:28, Helmut Schneider wrote:
** Detected a package name change: apache (www/apache22) -
'apache22' (www/apache22)
--- Upgrading 'apache-2.2.22_6' to 'apache22-2.2.22_8'
(www/apache22) --- Building '/usr/ports/www/apache22' with make
flags: -DWITH_PROXY -DWITH_PROXY_CONNECT -DWITH_PROXY_FTP
-DWITH_PROXY_HTTP -DWITH_LDAP -DWITH_AUTHNZ_LDAP -DWITH_BDB
-DWITH_APR_FROM_PORTS === Cleaning for apache22-2.2.22_8
You must check at least one option in the PROXY multi
*** Error code 1
The options worked fine up to 2.2.22_6 and I'm not sure how to
read the error message.
with options NG the WITH... parameters do no longer work.
If you want to specify them in make.conf you have to do it this way
I'm using pkgtools.conf, removing -DWITH_PROXY seems to do the trick
(I also removed the typo of DBD and the obsolete
DWITH_APR_FROM_PORTS, but they are not related).
apache22_SET=PROXY PROXY_CONNECT PROXY_FTP ...
The downside with options NG is if you already have an OPTIONSFILE
the make.conf parameters will have a lower priority.
Please note this in UPDATING.
Thanks!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Upgrade java/icedtea-web from 1.2_2 - 1.3 fails: tar: Pathname in pax header can't be converted to current locale
On Sun, Sep 09, 2012 at 08:34:35AM -0700, David Wolfskill wrote: On Sun, Sep 09, 2012 at 06:16:20PM +0300, Kimmo Paasiala wrote: ... Hmm, you're using sudo(1) and that means you enviroment may not be completely clean. Log on as root using 'su -l' and see if it makes a difference. Well, despite my earlier experiments with LC_ALL friends, su - allows the make to complete. I'll research the environment differences to see if there's anything I can learn from that. ... OK; I managed to get portmaster to upgrade the port. I normally perform such upgrades within script(1). This time, after invoking script, I issued: unsetenv LC* LANG before invoking portmaster, and that worked. (I noticed that after su -, output of env did not include any of the LC* variables or LANG.) There would thus appear to be a functional difference between setting the above-cited environment variables to default values vs. not having them set at all. (And after the upgrade, browsing to http://javatester.org/version.html with Firefox still shows Java Version: 1.6.0_32 from Sun Microsystems Inc.) Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgp9OOcxFvq5r.pgp Description: PGP signature
Re: [HEADS-UP] Announcing the end of port CVS
On Sun, Sep 9, 2012 at 6:26 AM, Alexandr Kovalenko ne...@nevermind.kiev.ua wrote: On Sun, Sep 9, 2012 at 8:15 AM, Kevin Oberman kob6...@gmail.com wrote: 2. Select US east coast or US west as your server. Pick at random or pick the one closer to you. What if neither is close to me (there are other countries in the world, not only USA, some are even on the other side of the planet, btw, did you know?) ? Yes, I am quite aware of it, but I am merely the messenger. Until other subversion mirrors are made available in other parts of the world, only the two in the US are available. I'm sure that will change in time, but for the moment, only the two US mirrors have been announced. For now, if it is not clear which is closer, you can ping to see which has the faster response. In my case, us-west is about 20 ms away while us-east is 100. If you have a well connected server in another part of the world, I assume the project would be happy to have another mirror made available. Note that the full repository is quite large. There are clearly security issues, too. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ 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
poudriere building for .
Hello, I have a quick question about poudriere and building for HEAD (AKA . AKA 10.0-CURRENT). When I created my buildjail, I used . to specify version and method csup. The funny thing is that now I get (please note . instead of 10.0): checking build system type... i386-portbld-freebsd. checking host system type... i386-portbld-freebsd. in all package builds. Most of packages do not dislike this, but there is at least one, which does - namely lsof - it fails to detect FreeBSD version. Could you please advise a solution for this? Thanks in advance! -- Alexandr Kovalenko http://uafug.org.ua/ ___ 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: [HEADS-UP] Announcing the end of port CVS
On Sun, Sep 9, 2012 at 7:35 PM, Kevin Oberman kob6...@gmail.com wrote: On Sun, Sep 9, 2012 at 6:26 AM, Alexandr Kovalenko ne...@nevermind.kiev.ua wrote: On Sun, Sep 9, 2012 at 8:15 AM, Kevin Oberman kob6...@gmail.com wrote: 2. Select US east coast or US west as your server. Pick at random or pick the one closer to you. What if neither is close to me (there are other countries in the world, not only USA, some are even on the other side of the planet, btw, did you know?) ? Yes, I am quite aware of it, but I am merely the messenger. Until other subversion mirrors are made available in other parts of the world, only the two in the US are available. I'm sure that will change in time, but for the moment, only the two US mirrors have been announced. For now, if it is not clear which is closer, you can ping to see which has the faster response. In my case, us-west is about 20 ms away while us-east is 100. If you have a well connected server in another part of the world, I assume the project would be happy to have another mirror made available. Note that the full repository is quite large. There are clearly security issues, too. JFYI, I'm already running ftp/cvsup.ua.freebsd.org (primary Ukrainian mirror) for about 8 years. But the recent changes to policies, which were discussed behind the closed doors by some group of people in The FreeBSD Project, effectively makes all efforts, money and so on, which were invested to support project, unnecessary. Current (semi-official) statements say that project is going to abandon practice of non-project managed mirrors and will do everything on it's own. As for now my mirror serves full CVS[up] repo from SSD, and have full FTP archive avaliable, which is synced every hour. You may have read the situation with Australian SVN mirror - when project officials officially prohibited guys, who set it up to use *.freebsd.org name for that. -- Alexandr Kovalenko ftp/cvsup.ua.freebsd.org maintainer. ___ 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: [HEADS-UP] Announcing the end of port CVS
--- On Fri, 9/7/12, Lars Eighner portsu...@larseighner.com wrote: From: Lars Eighner portsu...@larseighner.com Subject: Re: [HEADS-UP] Announcing the end of port CVS To: Beat Gaetzi b...@freebsd.org Cc: freebsd-ports@freebsd.org Date: Friday, September 7, 2012, 8:00 AM On Fri, 7 Sep 2012, Beat Gaetzi wrote: The development of FreeBSD ports is done in Subversion nowadays. For the sake of compatibility a Subversion to CVS exporter is in place which has some limitations. For CVSup mirroring cvsup based on Ezm3 is used which breaks regularly especially on amd64 and with Clang and becomes more and more unmaintainable. The svn-book: ...you can edit files at will, but you must tell Subversion about everything else that you do... Empirically, to a newbie, this appears quite confusing. Are the files in, say, /usr/ports/devel/boost-libs owned in some manner by svn? The extra files I've placed there (automatically generated copies of work/.PList_flattened..)(etc) are ignored/accidentally erased? Lock files are no longer supposed to be placed in the directory by scripts? ... I had intended to simply restore an older copy of /usr/ports over the new one, and have the two combined, as it were, but it appears many unwanted effects (... only certain svn commands from now on? Procedure to only .svn one of the port categories as can be done with csup? Which svn commands transfer files from where to where etc.?) Perhaps it would be better if I practice on the new ports tree before restoring over it, re-restore after practice, etc... Or even better, print out the online documentation, print out the forum svn examples, and spend several weeks practicing for csup equivalents and procedures... (That is what I am maybe wondering. Has anyone done the same and written it all up in a more detailed scenario? Which svn command subsets put files not deeper in .svn at risk? Is there only one .svn or multiple ones? Which svn commands should be run just once, and which routinely? Which to update just one parts of the ports tree? ... Even commands to copy the ports tree elsewhere with a lesser volume of files (no .svn... ) (Subversion appears more of an administrative tool rather than an end-user tool; requiring more complex configuration maybe, though maybe not if just for the ports tree. Possible configuration files to examine/copy persons may have already working for user/ports?) I'd rather use portsnap only on an older laptop... otherwise I would defer to it instead (for now anyway, since there is still time left...) BTW in replies to a question on the freebsd-questions list, I surmise there are many server farm administrators who are comfortable with csup/cvsup and not yet familiar with svn, and may also be thrown a learning curve with this change. Apologies for asking here, but trying to save many hours (or even minutes) of web searching, trial and error, etc... J. Bouquet ___ 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: [HEADS-UP] Announcing the end of port CVS
Kevin Oberman kob6...@gmail.com writes: On Sat, Sep 8, 2012 at 4:08 PM, Jeffrey Bouquet jeffreybouq...@yahoo.com wrote: I searched quite a bit upon this announcement to find csup svn equivalent guides and found little applying to ports... hopefully they will appear prior to the changeover?, something easily learned? Good point. I found the handbook information adequate, but not as easy to follow as it might be. Guess I'll write one. It's really quite easy and much faster then csup. 1. Install devel/subversion 2. Select US east coast or US west as your server. Pick at random or pick the one closer to you. 3. Rename (mv) ports/distfiles and ports/packages out of /usr/ports 4. rm -r /usr/ports/* 5. svn co http://svn0.us-west.freebsd.org/ports/head /usr/ports OR svn co http://svn0.us-east.freebsd.org/ports/head /usr/ports Ports will now be checked out of the repository and written to /usr/ports 6. make -f /usr/ports/Makefile fetchindex 7. Move ports/distfiles and ports/packages back into /usr/ports. Since these directories are not in the repository, they will be ignored by updates. 7. Update ports as needed with 'svn up /usr/ports' and 'make -f /usr/ports/Makefile fetchindex' This step does the equivalent of csup. 8. Use the Subversion manual from http://svnbook.red-bean.com/ to learn how to other things with svn. Of particular interest is 'svn info /usr/ports and setting up the .subversion file to do things like ignore some directories. If you add private ports to /usr/ports, they will be ignored by svn as they don't exist in the repository. If anyone has suggestions on other things that belong in this list, please let me know. I submitted some changes for the Handbook, but they really only covered the things that I thought were now Wrong. Your descriptions are certainly of higher quality. ___ 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: poudriere building for .
On Sun, Sep 09, 2012 at 07:48:37PM +0300, Alexandr Kovalenko wrote: Hello, I have a quick question about poudriere and building for HEAD (AKA . AKA 10.0-CURRENT). When I created my buildjail, I used . to specify version and method csup. The funny thing is that now I get (please note . instead of 10.0): checking build system type... i386-portbld-freebsd. checking host system type... i386-portbld-freebsd. in all package builds. Most of packages do not dislike this, but there is at least one, which does - namely lsof - it fails to detect FreeBSD version. Could you please advise a solution for this? This should normally have been fixed in 2.0 and -devel, but it would needs you to destroy/recreate your jail. Can you tell me which version of poudriere you were using when creating your jail? Another way and simpler way to deal with package building on HEAD, is to use the new allbsd method, which will fetch the latest current sets build by allbsd.org people. regards, Bapt pgpU1gthMKEQc.pgp Description: PGP signature
Re: poudriere building for .
On Sun, Sep 9, 2012 at 10:24 PM, Baptiste Daroussin b...@freebsd.org wrote: On Sun, Sep 09, 2012 at 07:48:37PM +0300, Alexandr Kovalenko wrote: I have a quick question about poudriere and building for HEAD (AKA . AKA 10.0-CURRENT). When I created my buildjail, I used . to specify version and method csup. The funny thing is that now I get (please note . instead of 10.0): checking build system type... i386-portbld-freebsd. checking host system type... i386-portbld-freebsd. in all package builds. Most of packages do not dislike this, but there is at least one, which does - namely lsof - it fails to detect FreeBSD version. Could you please advise a solution for this? This should normally have been fixed in 2.0 and -devel, but it would needs you to destroy/recreate your jail. Can you tell me which version of poudriere you were using when creating your jail? poudriere-1.5.4_1 Port build and test system Another way and simpler way to deal with package building on HEAD, is to use the new allbsd method, which will fetch the latest current sets build by allbsd.org people. Not quite sure I understand what you are talking about, could you, please, be more precise? :) -- Alexandr Kovalenko ___ 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: poudriere building for .
On Sun, Sep 09, 2012 at 11:25:01PM +0300, Alexandr Kovalenko wrote: On Sun, Sep 9, 2012 at 10:24 PM, Baptiste Daroussin b...@freebsd.org wrote: On Sun, Sep 09, 2012 at 07:48:37PM +0300, Alexandr Kovalenko wrote: I have a quick question about poudriere and building for HEAD (AKA . AKA 10.0-CURRENT). When I created my buildjail, I used . to specify version and method csup. The funny thing is that now I get (please note . instead of 10.0): checking build system type... i386-portbld-freebsd. checking host system type... i386-portbld-freebsd. in all package builds. Most of packages do not dislike this, but there is at least one, which does - namely lsof - it fails to detect FreeBSD version. Could you please advise a solution for this? This should normally have been fixed in 2.0 and -devel, but it would needs you to destroy/recreate your jail. Can you tell me which version of poudriere you were using when creating your jail? poudriere-1.5.4_1 Port build and test system Using poudriere 2.0 should help on this :) (but need destroy/create the jail) Another way and simpler way to deal with package building on HEAD, is to use the new allbsd method, which will fetch the latest current sets build by allbsd.org people. Not quite sure I understand what you are talking about, could you, please, be more precise? :) https://www.allbsd.org/ is providing recent snapshots sets, in 2.0 we provide a method called allbsd which will feth the prebuilt sets from allbsd (including for head) which will allow you to have a 10.0 jail without compiling :) regards, Bapt pgp6SCmWqJohY.pgp Description: PGP signature
Re: [HEADS-UP] Announcing the end of port CVS
On Sun, Sep 9, 2012 at 11:57 AM, Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org wrote: Kevin Oberman kob6...@gmail.com writes: On Sat, Sep 8, 2012 at 4:08 PM, Jeffrey Bouquet jeffreybouq...@yahoo.com wrote: I searched quite a bit upon this announcement to find csup svn equivalent guides and found little applying to ports... hopefully they will appear prior to the changeover?, something easily learned? Good point. I found the handbook information adequate, but not as easy to follow as it might be. Guess I'll write one. It's really quite easy and much faster then csup. 1. Install devel/subversion 2. Select US east coast or US west as your server. Pick at random or pick the one closer to you. 3. Rename (mv) ports/distfiles and ports/packages out of /usr/ports 4. rm -r /usr/ports/* 5. svn co http://svn0.us-west.freebsd.org/ports/head /usr/ports OR svn co http://svn0.us-east.freebsd.org/ports/head /usr/ports Ports will now be checked out of the repository and written to /usr/ports 6. make -f /usr/ports/Makefile fetchindex 7. Move ports/distfiles and ports/packages back into /usr/ports. Since these directories are not in the repository, they will be ignored by updates. 7. Update ports as needed with 'svn up /usr/ports' and 'make -f /usr/ports/Makefile fetchindex' This step does the equivalent of csup. 8. Use the Subversion manual from http://svnbook.red-bean.com/ to learn how to other things with svn. Of particular interest is 'svn info /usr/ports and setting up the .subversion file to do things like ignore some directories. If you add private ports to /usr/ports, they will be ignored by svn as they don't exist in the repository. If anyone has suggestions on other things that belong in this list, please let me know. I submitted some changes for the Handbook, but they really only covered the things that I thought were now Wrong. Your descriptions are certainly of higher quality. But I am still learning to count without a computer to help. 1, 2, 3, 4, 5, 6, 7, 7, 8??? **Sigh** Oh, well, I think everyone knows what I meant. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ 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: poudriere building for .
On Sun, Sep 9, 2012 at 1:37 PM, Baptiste Daroussin b...@freebsd.org wrote: On Sun, Sep 09, 2012 at 11:25:01PM +0300, Alexandr Kovalenko wrote: On Sun, Sep 9, 2012 at 10:24 PM, Baptiste Daroussin b...@freebsd.org wrote: On Sun, Sep 09, 2012 at 07:48:37PM +0300, Alexandr Kovalenko wrote: I have a quick question about poudriere and building for HEAD (AKA . AKA 10.0-CURRENT). When I created my buildjail, I used . to specify version and method csup. The funny thing is that now I get (please note . instead of 10.0): checking build system type... i386-portbld-freebsd. checking host system type... i386-portbld-freebsd. in all package builds. Most of packages do not dislike this, but there is at least one, which does - namely lsof - it fails to detect FreeBSD version. Could you please advise a solution for this? This should normally have been fixed in 2.0 and -devel, but it would needs you to destroy/recreate your jail. Can you tell me which version of poudriere you were using when creating your jail? poudriere-1.5.4_1 Port build and test system Using poudriere 2.0 should help on this :) (but need destroy/create the jail) Another way and simpler way to deal with package building on HEAD, is to use the new allbsd method, which will fetch the latest current sets build by allbsd.org people. Not quite sure I understand what you are talking about, could you, please, be more precise? :) https://www.allbsd.org/ is providing recent snapshots sets, in 2.0 we provide a method called allbsd which will feth the prebuilt sets from allbsd (including for head) which will allow you to have a 10.0 jail without compiling :) One of the ugliest web pages I've seen in a long time! Great tool! (I never much cared about eye candy.) I hope this gets more publicity as it looks extremely useful, though I need to look into security issues a bit. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ 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: [HEADS-UP] Announcing the end of port CVS
On 9 September 2012 17:30, Kevin Oberman kob6...@gmail.com wrote: On Sun, Sep 9, 2012 at 11:57 AM, Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org wrote: Kevin Oberman kob6...@gmail.com writes: On Sat, Sep 8, 2012 at 4:08 PM, Jeffrey Bouquet jeffreybouq...@yahoo.com wrote: I searched quite a bit upon this announcement to find csup svn equivalent guides and found little applying to ports... hopefully they will appear prior to the changeover?, something easily learned? Good point. I found the handbook information adequate, but not as easy to follow as it might be. Guess I'll write one. It's really quite easy and much faster then csup. 1. Install devel/subversion 2. Select US east coast or US west as your server. Pick at random or pick the one closer to you. 3. Rename (mv) ports/distfiles and ports/packages out of /usr/ports 4. rm -r /usr/ports/* 5. svn co http://svn0.us-west.freebsd.org/ports/head /usr/ports OR svn co http://svn0.us-east.freebsd.org/ports/head /usr/ports Ports will now be checked out of the repository and written to /usr/ports 6. make -f /usr/ports/Makefile fetchindex 7. Move ports/distfiles and ports/packages back into /usr/ports. Since these directories are not in the repository, they will be ignored by updates. 7. Update ports as needed with 'svn up /usr/ports' and 'make -f /usr/ports/Makefile fetchindex' This step does the equivalent of csup. 8. Use the Subversion manual from http://svnbook.red-bean.com/ to learn how to other things with svn. Of particular interest is 'svn info /usr/ports and setting up the .subversion file to do things like ignore some directories. If you add private ports to /usr/ports, they will be ignored by svn as they don't exist in the repository. If anyone has suggestions on other things that belong in this list, please let me know. I submitted some changes for the Handbook, but they really only covered the things that I thought were now Wrong. Your descriptions are certainly of higher quality. But I am still learning to count without a computer to help. 1, 2, 3, 4, 5, 6, 7, 7, 8??? **Sigh** I think you messed up because you didn't start from the basics: 0, 1, 2, 3 ... -- Eitan Adler ___ 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: [HEADS-UP] Announcing the end of port CVS
--- On Sun, 9/9/12, Eitan Adler li...@eitanadler.com wrote: From: Eitan Adler li...@eitanadler.com Subject: Re: [HEADS-UP] Announcing the end of port CVS To: Kevin Oberman kob6...@gmail.com Cc: Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org, freebsd-ports@freebsd.org Date: Sunday, September 9, 2012, 2:41 PM On 9 September 2012 17:30, Kevin Oberman kob6...@gmail.com wrote: On Sun, Sep 9, 2012 at 11:57 AM, Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org wrote: Kevin Oberman kob6...@gmail.com writes: On Sat, Sep 8, 2012 at 4:08 PM, Jeffrey Bouquet jeffreybouq...@yahoo.com wrote: I searched quite a bit upon this announcement to find csup svn equivalent guides and found little applying to ports... hopefully they will appear prior to the changeover?, something easily learned? Good point. I found the handbook information adequate, but not as easy to follow as it might be. Guess I'll write one. It's really quite easy and much faster then csup. 1. Install devel/subversion 2. Select US east coast or US west as your server. Pick at random or pick the one closer to you. 3. Rename (mv) ports/distfiles and ports/packages out of /usr/ports 4. rm -r /usr/ports/* 5. svn co http://svn0.us-west.freebsd.org/ports/head /usr/ports OR svn co http://svn0.us-east.freebsd.org/ports/head /usr/ports Ports will now be checked out of the repository and written to /usr/ports 6. make -f /usr/ports/Makefile fetchindex 7. Move ports/distfiles and ports/packages back into /usr/ports. Since these directories are not in the repository, they will be ignored by updates. 7. Update ports as needed with 'svn up /usr/ports' and 'make -f /usr/ports/Makefile fetchindex' This step does the equivalent of csup. 8. Use the Subversion manual from http://svnbook.red-bean.com/ to learn how to other things with svn. Of particular interest is 'svn info /usr/ports and setting up the .subversion file to do things like ignore some directories. If you add private ports to /usr/ports, they will be ignored by svn as they don't exist in the repository. If anyone has suggestions on other things that belong in this list, please let me know. I submitted some changes for the Handbook, but they really only covered the things that I thought were now Wrong. Your descriptions are certainly of higher quality. But I am still learning to count without a computer to help. 1, 2, 3, 4, 5, 6, 7, 7, 8??? **Sigh** I think you messed up because you didn't start from the basics: 0, 1, 2, 3 ... -- Eitan Adler ___ 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 Initial attempts with svn[1] suggest one may skip step 4 (making the svn command more like csup), if that is the case, anyone know of a workaround (easier method) than restoring /usr/ports/distfiles and /usr/ports/packages from backup? Or skipping those steps altogether, svn does extra/unwanted work or? [1] on only x11-themes, for example J. Bouquet ___ 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: [HEADS-UP] Announcing the end of port CVS
--- On Sun, 9/9/12, Jeffrey Bouquet jeffreybouq...@yahoo.com wrote: From: Jeffrey Bouquet jeffreybouq...@yahoo.com Subject: Re: [HEADS-UP] Announcing the end of port CVS To: Kevin Oberman kob6...@gmail.com, Eitan Adler li...@eitanadler.com Cc: Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org, freebsd-ports@freebsd.org Date: Sunday, September 9, 2012, 3:47 PM --- On Sun, 9/9/12, Eitan Adler li...@eitanadler.com wrote: From: Eitan Adler li...@eitanadler.com Subject: Re: [HEADS-UP] Announcing the end of port CVS To: Kevin Oberman kob6...@gmail.com Cc: Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org, freebsd-ports@freebsd.org Date: Sunday, September 9, 2012, 2:41 PM On 9 September 2012 17:30, Kevin Oberman kob6...@gmail.com wrote: On Sun, Sep 9, 2012 at 11:57 AM, Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org wrote: Kevin Oberman kob6...@gmail.com writes: On Sat, Sep 8, 2012 at 4:08 PM, Jeffrey Bouquet jeffreybouq...@yahoo.com wrote: I searched quite a bit upon this announcement to find csup svn equivalent guides and found little applying to ports... hopefully they will appear prior to the changeover?, something easily learned? Good point. I found the handbook information adequate, but not as easy to follow as it might be. Guess I'll write one. It's really quite easy and much faster then csup. 1. Install devel/subversion 2. Select US east coast or US west as your server. Pick at random or pick the one closer to you. 3. Rename (mv) ports/distfiles and ports/packages out of /usr/ports 4. rm -r /usr/ports/* 5. svn co http://svn0.us-west.freebsd.org/ports/head /usr/ports OR svn co http://svn0.us-east.freebsd.org/ports/head /usr/ports Ports will now be checked out of the repository and written to /usr/ports 6. make -f /usr/ports/Makefile fetchindex 7. Move ports/distfiles and ports/packages back into /usr/ports. Since these directories are not in the repository, they will be ignored by updates. 7. Update ports as needed with 'svn up /usr/ports' and 'make -f /usr/ports/Makefile fetchindex' This step does the equivalent of csup. 8. Use the Subversion manual from http://svnbook.red-bean.com/ to learn how to other things with svn. Of particular interest is 'svn info /usr/ports and setting up the .subversion file to do things like ignore some directories. If you add private ports to /usr/ports, they will be ignored by svn as they don't exist in the repository. If anyone has suggestions on other things that belong in this list, please let me know. I submitted some changes for the Handbook, but they really only covered the things that I thought were now Wrong. Your descriptions are certainly of higher quality. But I am still learning to count without a computer to help. 1, 2, 3, 4, 5, 6, 7, 7, 8??? **Sigh** I think you messed up because you didn't start from the basics: 0, 1, 2, 3 ... -- Eitan Adler ___ 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 Initial attempts with svn[1] suggest one may skip step 4 (making the svn command more like csup), if that is the case, anyone know of a workaround (easier method) than restoring /usr/ports/distfiles and /usr/ports/packages from backup? Or skipping those steps altogether, svn does extra/unwanted work or? [1] on only x11-themes, for example J. Bouquet ___ 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 Sorry to reply to my own email. These CLI worked... mv /usr/ports/distfiles /usr/distfiles mv /usr/ports/packages /usr/packages... (Haven't gotten to the svn part yet...) J. Bouquet ___ 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: [HEADS-UP] Announcing the end of port CVS
Hi, On Sun, 9 Sep 2012 16:26:06 +0300 Alexandr Kovalenko ne...@nevermind.kiev.ua wrote: On Sun, Sep 9, 2012 at 8:15 AM, Kevin Oberman kob6...@gmail.com wrote: 2. Select US east coast or US west as your server. Pick at random or pick the one closer to you. What if neither is close to me (there are other countries in the world, not only USA, some are even on the other side of the planet, btw, did you know?) ? Planet? What happened to the disk? Yes, ignorance rules. Erich ___ 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: [HEADS-UP] Announcing the end of port CVS
Hi, On Sun, 9 Sep 2012 09:35:21 -0700 Kevin Oberman kob6...@gmail.com wrote: On Sun, Sep 9, 2012 at 6:26 AM, Alexandr Kovalenko ne...@nevermind.kiev.ua wrote: On Sun, Sep 9, 2012 at 8:15 AM, Kevin Oberman kob6...@gmail.com wrote: 2. Select US east coast or US west as your server. Pick at random or pick the one closer to you. What if neither is close to me (there are other countries in the world, not only USA, some are even on the other side of the planet, btw, did you know?) ? Yes, I am quite aware of it, but I am merely the messenger. Until other subversion mirrors are made available in other parts of the world, only the two in the US are available. I'm sure that will change in time, but for the moment, only the two US mirrors have been announced. why stop a system then when the replacement is not up and running? Do you want to kill the infrastructure to distribute FreeBSD? Erich ___ 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: [HEADS-UP] Announcing the end of port CVS
Hi, On Sun, 9 Sep 2012 19:54:06 +0300 Alexandr Kovalenko ne...@nevermind.kiev.ua wrote: On Sun, Sep 9, 2012 at 7:35 PM, Kevin Oberman kob6...@gmail.com wrote: On Sun, Sep 9, 2012 at 6:26 AM, Alexandr Kovalenko ne...@nevermind.kiev.ua wrote: On Sun, Sep 9, 2012 at 8:15 AM, Kevin Oberman kob6...@gmail.com wrote: 2. Select US east coast or US west as your server. Pick at random or pick the one closer to you. What if neither is close to me (there are other countries in the world, not only USA, some are even on the other side of the planet, btw, did you know?) ? Yes, I am quite aware of it, but I am merely the messenger. Until other subversion mirrors are made available in other parts of the world, only the two in the US are available. I'm sure that will change in time, but for the moment, only the two US mirrors have been announced. For now, if it is not clear which is closer, you can ping to see which has the faster response. In my case, us-west is about 20 ms away while us-east is 100. If you have a well connected server in another part of the world, I assume the project would be happy to have another mirror made available. Note that the full repository is quite large. There are clearly security issues, too. JFYI, I'm already running ftp/cvsup.ua.freebsd.org (primary Ukrainian mirror) for about 8 years. But the recent changes to policies, which were discussed behind the closed doors by some group of people in The FreeBSD Project, effectively makes all efforts, money and so on, which were invested to support project, unnecessary. Current (semi-official) statements say that project is going to abandon practice of non-project managed mirrors and will do everything on it's own. As for now my mirror serves full CVS[up] repo from SSD, and have full FTP archive avaliable, which is synced every hour. You may have read the situation with Australian SVN mirror - when project officials officially prohibited guys, who set it up to use *.freebsd.org name for that. this all sounds like a inside job to kill FreeBSD. I just wrote the other message saying that it seems to me that the huge user base outside the USA is ignored. What will happen to the project when all non-US servers cannot be used anymore? Erich ___ 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: [HEADS-UP] Announcing the end of port CVS
- Original Message - From: Erich Dollansky erichfreebsdl...@ovitrap.com What if neither is close to me (there are other countries in the world, not only USA, some are even on the other side of the planet, btw, did you know?) ? Yes, I am quite aware of it, but I am merely the messenger. Until other subversion mirrors are made available in other parts of the world, only the two in the US are available. I'm sure that will change in time, but for the moment, only the two US mirrors have been announced. why stop a system then when the replacement is not up and running? Do you want to kill the infrastructure to distribute FreeBSD? Looking at it from the practical side if the replacement architecture isn't ready yet then it sounds like this needs to be delayed until such a time that it is. Only having two mirrors and both in the US is not really practical, many of us, in other parts of the globe, will suffer from stupidly long update times; BDP would really have a bad effect on updates, and that's assuming the two servers don't just die under the load of everyone using them. So again please consider delaying the switch over until a decent mirror set is available, in order to prevent serious amounts of frustration from your user base. Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: net-p2p/bitcoin
I'm new to creating/maintain ports., I created a simple startup script and conf file for this port. I am wondering how I can submit my improvements? ___ 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: net-p2p/bitcoin
On Sun, Sep 9, 2012 at 6:33 PM, Daniel Morante dan...@morante.net wrote: I'm new to creating/maintain ports., I created a simple startup script and conf file for this port. I am wondering how I can submit my improvements? Have you looked at the Porter's Handbook? http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook It describes the process in some detail. At the moment the port has no maintainer. If you want to take care of it, feel free to request maintainership on this list. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ 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
