Re: libreoffice-3.4.5.2 failing to build
On Thu, Mar 29, 2012 at 02:11:33PM +1000, Da Rock wrote: On 03/27/12 21:42, Da Rock wrote: I've been hunting down some info on why this is failing, but all I keep running into is the previous versions failings... :( I'm building libreoffice on 9.0-Release amd64, and I'm getting build errors qa testing(?) sd. I followed the instructions, but it still failed. It spits out this: scripting deliver deliver -- version: 275594 module 'scripting' delivered successfully. 0 files copied, 28 files unchanged terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' /usr/local/bin/bash: line 1: 2019 Abort trap: 6 (core dumped) [ a whole lot of code (I'm copying by hand, so it is a bit overwhelming) - involving clone/impress/sd/unxfbsd.pro, solver, and qa_unit ] dmake: Error code 134, while making 'test' gb_LinkTarget_add_library_objects,CppunitTest/libtest_sc_ucalc.so,sc gb_LinkTarget_add_linktarget_objects,CppunitTest/libtest_sc_ucalc.so,Library/libscfb.so [ build all ] top level modules: sc [ build all ] loaded modules: sc [ build cut ] sc_ucalc Abort trap (core dumped) terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' gmake[1]: *** [/usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/solver/340/unxfbsd.pro/workdir/CppunitTest/sc_ucalc.test] Error 1 dmake: Error code 2, while making 'all' [ build all ] top level modules: sw [ build all ] loaded modules: sw [ build all ] loaded modules: sw [ build log ] sw sw deliver deliver -- version: 275594 Module 'sw' delivered successfully. 0 files copied, 1 files unchanged - [ standard error message with webpage link to debug page ] internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sd/qa/unit ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sc/prj [ instructions to build sd part of the build to isolate the issue ] As I mentioned I followed the directions and still hit the same error filed above (if more of the data is needed I guess I'll have to find a way to post it...). I'm on a deadline for this one, so I have to get this to work. How should I further debug this to fix it? Or failing that (as an extreme last resort), will an older package already built work IF it is built for 8.2? After a portsnap update I still get core dumps in the calc/sc/cppunittester and the impress/sd/qa/unit/cppunittester. I've tried turning off make jobs, and I also checked the core files (when I finally found them). The only clue I have is this: #0 0x0008016bca7c in ?? This is in _both_ core files, and although its not very helpful it says its stopping in exactly the same place (duh). Seriously guys, where do I go from here? Googling isn't exactly offering up much - my searches can be as much as 7 results (usually my own stuff or duplicates of the same). Or, as my last resort, can I use the 8.2 package instead? Need some serious pointers, pleeease... :) is you 9.0-RELEASE a freshly built system? or installed installed from installers or upgraded? regards, Bapt pgp1okvA4mnYB.pgp Description: PGP signature
Re: libreoffice-3.4.5.2 failing to build
On 03/30/12 16:22, Baptiste Daroussin wrote: On Thu, Mar 29, 2012 at 02:11:33PM +1000, Da Rock wrote: On 03/27/12 21:42, Da Rock wrote: I've been hunting down some info on why this is failing, but all I keep running into is the previous versions failings... :( I'm building libreoffice on 9.0-Release amd64, and I'm getting build errors qa testing(?) sd. I followed the instructions, but it still failed. It spits out this: scripting deliver deliver -- version: 275594 module 'scripting' delivered successfully. 0 files copied, 28 files unchanged terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' /usr/local/bin/bash: line 1: 2019 Abort trap: 6 (core dumped) [ a whole lot of code (I'm copying by hand, so it is a bit overwhelming) - involving clone/impress/sd/unxfbsd.pro, solver, and qa_unit ] dmake: Error code 134, while making 'test' gb_LinkTarget_add_library_objects,CppunitTest/libtest_sc_ucalc.so,sc gb_LinkTarget_add_linktarget_objects,CppunitTest/libtest_sc_ucalc.so,Library/libscfb.so [ build all ] top level modules: sc [ build all ] loaded modules: sc [ build cut ] sc_ucalc Abort trap (core dumped) terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' gmake[1]: *** [/usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/solver/340/unxfbsd.pro/workdir/CppunitTest/sc_ucalc.test] Error 1 dmake: Error code 2, while making 'all' [ build all ] top level modules: sw [ build all ] loaded modules: sw [ build all ] loaded modules: sw [ build log ] sw sw deliver deliver -- version: 275594 Module 'sw' delivered successfully. 0 files copied, 1 files unchanged - [ standard error message with webpage link to debug page ] internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sd/qa/unit ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sc/prj [ instructions to build sd part of the build to isolate the issue ] As I mentioned I followed the directions and still hit the same error filed above (if more of the data is needed I guess I'll have to find a way to post it...). I'm on a deadline for this one, so I have to get this to work. How should I further debug this to fix it? Or failing that (as an extreme last resort), will an older package already built work IF it is built for 8.2? After a portsnap update I still get core dumps in the calc/sc/cppunittester and the impress/sd/qa/unit/cppunittester. I've tried turning off make jobs, and I also checked the core files (when I finally found them). The only clue I have is this: #0 0x0008016bca7c in ?? This is in _both_ core files, and although its not very helpful it says its stopping in exactly the same place (duh). Seriously guys, where do I go from here? Googling isn't exactly offering up much - my searches can be as much as 7 results (usually my own stuff or duplicates of the same). Or, as my last resort, can I use the 8.2 package instead? Need some serious pointers, pleeease... :) is you 9.0-RELEASE a freshly built system? or installed installed from installers or upgraded? Completely clean install last week, and ports tree refreshed since on wed. I've been on the libreoffice-dev lists and the only advice is to disable the tests - but if the test is failing it must be for a reason don't you think? So why? Thanks for these couple of responses, still need help though :) ___ 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
INDEX build failed for 7.x
INDEX build failed with errors: Generating INDEX-7 - please wait.. Done. Warning: Duplicate INDEX entry: lazarus-0.9.30 Committers on the hook: scheidell wen Most recent CVS update was: U editors/Makefile U editors/lazarus-gtk2/Makefile U editors/lazarus-gtk2/pkg-descr U textproc/p5-ODF-lpOD/Makefile U textproc/p5-ODF-lpOD/distinfo U www/mediawiki/Makefile U www/mediawiki/distinfo U www/py-pywebdav/Makefile U www/py-pywebdav/distinfo U www/py-pywebdav/pkg-plist U www/py-routes/Makefile U www/py-routes/distinfo U www/py-routes/pkg-plist ___ 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: jabberd port doesn't come with any certificates and is not allowing authorization?
On Thu, Mar 29, 2012 at 4:30 PM, Matthew Seaman matt...@freebsd.org wrote: On 29/03/2012 15:45, Kaya Saman wrote: I've recently built the jabberd port and upgraded to the latest version: 2.x Actually jabberd2 (net-im/jabberd) is a completely different different project to jabberd14 (net-im/jabber) -- it's not upgrading so much as switching to a different piece of software. In any case, jabberd2 is the correct choice: it is being actively developed and is keeping abreast of the various XMPP extensions that are being published. Ok so I'm on the right track then :-) I'm having major problems in configuring it though and was wondering if someone could either give me a hand or help me generate certificates for it which are mentioned in the config file but not within the /usr/local/etc/jabberd directory. I'm experiencing this issue: Mar 29 16:33:48 JABBER jabberd/c2s[1498]: [8] [10.0.0.10, port=59032] connect Mar 29 16:33:48 JABBER jabberd/c2s[1498]: [8] got pre STARTTLS packet, dropping Mar 29 16:33:48 JABBER jabberd/c2s[1498]: [8] [10.0.0.10, port=59032] disconnect jid=unbound, packets: 1 Your client is attempting to switch its connection to using TLS. This is good, especially if you are using a SASL method of LOGIN or PASSWORD -- otherwise it would send passwords across the net in plain test. Hmm... so I guess pidgin doesn't do non-encrypted connections then? I totally agree with using encryption however, I just want to learn how to setup jabberd first in its most basic state before getting more advanced. This is my realm information: id realm='jabber.com' pemfile='/usr/local/etc/jabberd/server.pem' verify-mode='0' cachain='/usr/local/etc/jabberd/client_ca_certs.pem' require-starttls='false' register-enable='true' instructions='Enter a username and password to register with this server.' register-oob='http://srv.jabber.com/register' password-change='true' jabber.com/id !-- or the default host id password-change='mu' / -- jabber.com may publicly exist however, this is a trial done in Vbox and totally offline just so I can understand the necessary mechanisms involved as to learn how the jabberd server functions! You've got both 'register-enable' and 'register-oob' -- you probably don't want both of those, unless you do have an out-of-band method to create user accounts. Actually to allow IM clients to register will be better, though later on when I do a full implementation I will need to authenticate to either PAM or AD. Presumably you have created the required server x509 certificate. If you're doing it on the cheap, that means a self-signed certificate. In which case there simply won't be a cain of CA certs to worry about. I'd also recommend require-starttls='true' I don't have an x509 cert, I discovered this though: http://www.stanbarber.com/freebsd/creating-self-signed-ssl-certificates-on-freebsd-with-openssl Is that what you mean or is the x509 different from the SSL self signed cert? Of course, there's a lot more to setting up jabberd than just this little section of one of the config files. Means a lot more to learn I'm using Pidgin as the IM client who is configured like: Username: user Domain: jabber.com Password: secret Local Alias: user_alias Use encrypted connections if available ---*** Allow plaintext auth over unencrypted streams ---*** Connect server: srv.jabber.com Those two marked items are not a good idea. If you're using login to authenticate the SASL libraries expect you to use TLS to secure the transaction, and the way of least resistance is to do so. Once cert has been created I will adjust accordingly! On the client I keep getting: Policy Violation error. It's really weird but there seems to be a lack of documentation as I managed to find the stuff for jabberd version 1.4, for version 2.x I've followed some URL's: http://www.jms1.net/jabberd2/ http://www.indiangnu.org/2009/how-to-configure-jabber-jabberd2-with-mysqlpam-as-auth-database/ http://bionicraptor.co/2011/07/25/how-to-encrypt-jabberd2-communications/ http://bionicraptor.co/2011/05/20/how-to-install-and-configure-japperd2-with-mysql/ But still nothing is working, I believe it's to do with the security as in using encrypted or unencrypted connections but I can't be certain... there doesn't seem to be any mysql DB creation script either that I could find?? Look in /usr/local/share/doc/jabberd I originally implemented jabberd2 using a MySQL database, but have switched to PostgreSQL. Which RDBMs you use won't make a whole lot of difference unless your traffic levels grow to pretty enormous levels. In fact, for a lightly used system, sqlite would be a reasonable choice. Is there a fix or am I stuck?? Well, I have jabberd2 up and running quite happily. I don't remember setting it up as being particularly
Can please with anybody sparc64 try to build devel/py-pylib?
Subj. This port is marked IGNORE on sparc64 for a long time, and I suspect that it's no more valid. Can please anybody with sparc64 provide me with a buildlog of devel/py-pylib (with IGNORE line removed). Thanks in advance. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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
[HEADSUP] pkgng 1.0-beta9 please test
Hi, On behalf of pkgng crew, I'm happy to announce pkg 1.0-beta9 - changes: * query -f has been replaced by query -F when querying a package (file) for consistency with pkg info * fix autoremove recursion * pkg set -o oldorigin:neworigin allow the user to modify the origin of a packages (useful for MOVED) * several fixes on powerpc * pkg query evaluation expression now accept != * pkg2ng is now able to migrate a local database without needed the ports tree * speed up pkg check by only loading the informations needed for the operation it will do * code cleanup in the library * fix uname/gname lookup when creating packages * new periodic script for pkg audit * new keyword shlib, pkgng is able to load information about the needed shlibs for a package (disable by default) * pkg info act as pkg info -a by default * new install timestamp in the package database, available using pkg query %t * pkg updating can now take a port name as argument to only show related UPDATING informations) * -q (quiet) for install, delete, upgrade, update and autoremove * new ABI detection string Concerning the new ABI, to be able to determine which package can be installed on which destination, pkgng couldn't rely on the simple: os version/machine, because some arches have incompatible ABIs. Can compute on its own the ABI, the string is the followin: OSNAME:OSMAJORVERSION:OSARCH:OSCLASS(:...) .. means the arch specific extensions. which means on: * amd64: freebsd:9:x86:64 * i386: freebsd:9:x86 * arm: freebsd:9:arm:eb:oabi:softvp etc Be careful all the packages (.txz) files have to be rebuilt!!! When binary upgradeing from pkg beta8, on amd64 do the following: UNAME_m=freebsd:9:x86:64 pkg install -f pkg on i386 UNAME_m=freebsd:9:x86:32 pkg install -f pkg Bonus when run on a chroot/jail where ABI is different from the host, pkgng will dynamically determine the destination ABI. Please note that normally this will be the last beta version, regards, Bapt pgpJrPgbcXtCG.pgp Description: PGP signature
Re: Can please with anybody sparc64 try to build devel/py-pylib?
On 3/30/12 4:11 AM, Ruslan Mahmatkhanov wrote: Subj. This port is marked IGNORE on sparc64 for a long time, and I suspect that it's no more valid. Can please anybody with sparc64 provide me with a buildlog of devel/py-pylib (with IGNORE line removed). Thanks in advance. I have a 6.4 box, that do any good? -- Michael Scheidell, CTO *| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ 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 10.0-CURRENT/amd64 and SSL connections to PostgreSQL 9.1.3: broken!
A couple of days ago I updated FreeBSD 10.0-CURRENT and deleted old libs and old files via make delete-old-XXX in /usr/src, as I saw that Kerberos5/Heimdal got an update. After that, several server/applications didn't work correctly anymore due to missing, already deleted libraries. So i recompiled nearly every port, especially Subversion, OpenLDAP (amongst Cyrus SASL, pam_ldap and nss_ldap). PostgreSQL has also got an update from 9.1.2 to 9.1.3 that time. My hurting problem is, that ALL FreeBSD 10.0-CURRENT based servers using OpenLDAP or SSL connections now fail. I can not exactly nail down the problem, but these (already completely with portmaster -f recompiled applications) ports fail connecting to PostgreSQL when using OpenLDAP/SSL: pgadmin3 (users in pg_hba are, except superuser, on OpenLDAP) refdb (refdb users are OpenLDAP backed) Mediawiki (Mediawiki users are OpenLDAP backed) These ports connect to PostgreSQL and use for user's authentication OpenLDAP. Our boxes also use OpenLDAP for user authentication, this works, so I assume PostgreSQL is the failing point. In the log I get that a pg_hba entry with SSL off is missing. Somehow, SSL doesn't work anymore or the certificate got invalidated (created with a CA on FreeBSD 9, now used on FBSD 10). Does anyone also experience this weird behaviour? Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: Can please with anybody sparc64 try to build devel/py-pylib?
On Fri, Mar 30, 2012 at 05:16:23AM -0400, Michael Scheidell wrote: On 3/30/12 4:11 AM, Ruslan Mahmatkhanov wrote: Subj. This port is marked IGNORE on sparc64 for a long time, and I suspect that it's no more valid. Can please anybody with sparc64 provide me with a buildlog of devel/py-pylib (with IGNORE line removed). Thanks in advance. Seems fine on sparc64 r230787M: Script started on Fri Mar 30 10:37:50 2012 make install package === License MIT accepted by the user === Extracting for py27-pylib-1.4.7 = SHA256 Checksum OK for py-1.4.7.zip. === py27-pylib-1.4.7 depends on file: /usr/local/bin/unzip - found === Patching for py27-pylib-1.4.7 === py27-pylib-1.4.7 depends on file: /usr/local/bin/easy_install-2.7 - found === py27-pylib-1.4.7 depends on file: /usr/local/bin/python2.7 - found === Configuring for py27-pylib-1.4.7 running config === Building for py27-pylib-1.4.7 running bdist_egg running egg_info writing py.egg-info/PKG-INFO writing top-level names to py.egg-info/top_level.txt writing dependency_links to py.egg-info/dependency_links.txt reading manifest file 'py.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'py.egg-info/SOURCES.txt' installing library code to build/bdist.freebsd-9.9-CURRENT-sparc64/egg running install_lib running build_py creating build creating build/lib creating build/lib/py copying py/__init__.py - build/lib/py copying py/__metainfo.py - build/lib/py copying py/_apipkg.py - build/lib/py copying py/_builtin.py - build/lib/py copying py/_error.py - build/lib/py copying py/_iniconfig.py - build/lib/py copying py/_std.py - build/lib/py copying py/_xmlgen.py - build/lib/py copying py/test.py - build/lib/py creating build/lib/py/_code copying py/_code/__init__.py - build/lib/py/_code copying py/_code/_assertionnew.py - build/lib/py/_code copying py/_code/_assertionold.py - build/lib/py/_code copying py/_code/assertion.py - build/lib/py/_code copying py/_code/code.py - build/lib/py/_code copying py/_code/source.py - build/lib/py/_code creating build/lib/py/_io copying py/_io/__init__.py - build/lib/py/_io copying py/_io/capture.py - build/lib/py/_io copying py/_io/saferepr.py - build/lib/py/_io copying py/_io/terminalwriter.py - build/lib/py/_io creating build/lib/py/_log copying py/_log/__init__.py - build/lib/py/_log copying py/_log/log.py - build/lib/py/_log copying py/_log/warning.py - build/lib/py/_log creating build/lib/py/_path copying py/_path/__init__.py - build/lib/py/_path copying py/_path/cacheutil.py - build/lib/py/_path copying py/_path/common.py - build/lib/py/_path copying py/_path/local.py - build/lib/py/_path copying py/_path/svnurl.py - build/lib/py/_path copying py/_path/svnwc.py - build/lib/py/_path creating build/lib/py/_process copying py/_process/__init__.py - build/lib/py/_process copying py/_process/cmdexec.py - build/lib/py/_process copying py/_process/forkedfunc.py - build/lib/py/_process copying py/_process/killproc.py - build/lib/py/_process creating build/bdist.freebsd-9.9-CURRENT-sparc64 creating build/bdist.freebsd-9.9-CURRENT-sparc64/egg creating build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py copying build/lib/py/__init__.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py copying build/lib/py/__metainfo.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py copying build/lib/py/_apipkg.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py copying build/lib/py/_builtin.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py copying build/lib/py/_error.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py copying build/lib/py/_iniconfig.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py copying build/lib/py/_std.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py copying build/lib/py/_xmlgen.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py copying build/lib/py/test.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py creating build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py/_code copying build/lib/py/_code/__init__.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py/_code copying build/lib/py/_code/_assertionnew.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py/_code copying build/lib/py/_code/_assertionold.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py/_code copying build/lib/py/_code/assertion.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py/_code copying build/lib/py/_code/code.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py/_code copying build/lib/py/_code/source.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py/_code creating build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py/_io copying build/lib/py/_io/__init__.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py/_io copying build/lib/py/_io/capture.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py/_io copying build/lib/py/_io/saferepr.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py/_io copying build/lib/py/_io/terminalwriter.py - build/bdist.freebsd-9.9-CURRENT-sparc64/egg/py/_io creating
Re: jabberd port doesn't come with any certificates and is not allowing authorization?
On 30/03/2012 08:57, Kaya Saman wrote: You've got both 'register-enable' and 'register-oob' -- you probably don't want both of those, unless you do have an out-of-band method to create user accounts. Actually to allow IM clients to register will be better, though later on when I do a full implementation I will need to authenticate to either PAM or AD. The point was that 'register-enable' turns on jabberd's internal account creation functions, whereas 'register-oob' says to go to a separate site in order to create the account. If you're using a user database from elsewhere (pam or AD for instance), then you'ld want neither of those options. Presumably you have created the required server x509 certificate. If you're doing it on the cheap, that means a self-signed certificate. In which case there simply won't be a cain of CA certs to worry about. I'd also recommend require-starttls='true' I don't have an x509 cert, I discovered this though: http://www.stanbarber.com/freebsd/creating-self-signed-ssl-certificates-on-freebsd-with-openssl Is that what you mean or is the x509 different from the SSL self signed cert? Hmmm... actually that article describes setting up your own Certification Authority. You certainly can do that if you want to -- but I'd recommend using security/tinyca rather than the fairly rudimentary setup using little more than what comes with openssl described above. A self-signed certificate is actually a bit different to what the above would get you. They're both x509 certificates (where x509 means it just adheres to a standard format published by the International Telecomunications Union) -- a certificate in cryptography-speak is simply a public key plus some other data describing how it is used, which has been digitally signed to prevent tampering. self-signed means that the /private/ key used to sign the certificate is the counterpart to the /public/ key contained in it. You can tell from a self-signed certificate that it hasn't been tampered with, but you have no prima-facie way of telling who the certificate belongs to and whether you should place any trust in it. So this sort of certificate is generally only useful for low value situations or within a small organization where you already know the people behind whatever it is that uses the certificate. Now, all normal certificates are actually self-signed. The difference is that a cert you would buy from a recognised CA is also signed by the CA's private key. This is a way of saying that the certification authority has gone through the due diligence of establishing that you are in fact who you say you are and that by signing the certificate they will vouch for you to third parties[*]. By setting up your own CA you can reliably identify certificates you issued yourself. That's all fine and dandy, but probably over the top for a throwaway key used in development and almost certainly not good enough for a service open to the general public. Anyhow, enough of this essay on public key cryptography. To create a self-signed certificate: 1) Create a new public/private key pair. openssl genrsa -out foo.key 1024 (note: this creates the key *without* a passphrase, which is what you usually want for services like jabber. Since it has no passphrase, it is particularly vulnerable to being stolen, so take care to keep it safe.) 2) Create a 'Certificate Signing Request' -- this is where you enter all the auxiliary data about what the key should be used for. openssl req -new -key foo.key -out foo.csr You'll be prompted for various identifying data. Fill them in as far as you can be bothered -- the only really important one is the 'Common Name' which should be the FQDN of your jabber server. You don't need to fill in 'Email Address' -- that's really only necessary for a certificate used for authentication by a person. Nor do you need to bother with any 'Challenge Password' or optional company name -- those can be used by some CAs as part of their authentication procedures. 3) Sign the public key (part of the contents of the CSR) with its own private key to generate the certificate openssl x509 -req -days 365 -in foo.csr -signkey foo.key -out foo.crt Adjust '-days 365' to taste, as you'll need to repeat this signing step to renew the cert once that period of validity has passed. 4) Specifically for jabberd2, concatenate the key and cert into one file: cat foo.key foo.crt foo.pem This is an application specific thing: some apps like key and cert together like this, others use separate files for key and cert. Cheers, Matthew [*] Which just begs the question of who is this CA and why should I trust them to vouch for anyone else? Well, there's a hierarchy of certification authorities. The CA can itself issue a certificate for its certificate-signing key that is itself
Re: Can please anybody with sparc64 try to build devel/py-pylib?
Anton Shterenlikht wrote on 30.03.2012 13:43: On Fri, Mar 30, 2012 at 05:16:23AM -0400, Michael Scheidell wrote: On 3/30/12 4:11 AM, Ruslan Mahmatkhanov wrote: Subj. This port is marked IGNORE on sparc64 for a long time, and I suspect that it's no more valid. Can please anybody with sparc64 provide me with a buildlog of devel/py-pylib (with IGNORE line removed). Thanks in advance. Seems fine on sparc64 r230787M: Ok, thanks a bunch, Anton! Michael, thanks you, I seems got all I need already. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: INDEX build failed for 7.x
On 3/30/12 3:36 AM, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX-7 - please wait.. Done. Warning: Duplicate INDEX entry: lazarus-0.9.30 Committers on the hook: scheidell wen mine. new port / lazarus-gtk2 slave port of lazarus. Worse yet, installs binary in same place as lazarus. Adding in CONFLICTS and fixes now. (but its 6am, need my first coffee.. haven't figured out how to fix this and the lazarus-qt4 slave port. I ASSUME I can 'maintainer (implicit) add a CONFLICTS to lazurus/Makefile? last pr timed out? or should I request that last committer do it? http://www.freebsd.org/cgi/query-pr.cgi?pr=165507 -- Michael Scheidell, CTO *| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ 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: INDEX build failed for 7.x
Michael Scheidell wrote on 30.03.2012 14:09: On 3/30/12 3:36 AM, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX-7 - please wait.. Done. Warning: Duplicate INDEX entry: lazarus-0.9.30 Committers on the hook: scheidell wen mine. new port / lazarus-gtk2 slave port of lazarus. Worse yet, installs binary in same place as lazarus. Adding in CONFLICTS and fixes now. (but its 6am, need my first coffee.. haven't figured out how to fix this and the lazarus-qt4 slave port. I ASSUME I can 'maintainer (implicit) add a CONFLICTS to lazurus/Makefile? last pr timed out? or should I request that last committer do it? http://www.freebsd.org/cgi/query-pr.cgi?pr=165507 I believe you do not need an approval to fix things you broke. :) -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: [HEADSUP] pkgng 1.0-beta9 please test
Baptiste Daroussin wrote: * pkg set -o oldorigin:neworigin allow the user to modify the origin of a packages (useful for MOVED) Can such things be tracked automatically? I.e. will pkg upgrade upgrade moved packages? ___ 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
INDEX build failed for 7.x
INDEX build failed with errors: Generating INDEX-7 - please wait.. Done. Warning: Duplicate INDEX entry: lazarus-0.9.30 Committers on the hook: bapt delphij pav scheidell wen Most recent CVS update was: U games/gnarr/Makefile U math/p5-Statistics-R/Makefile U math/p5-Statistics-R/distinfo U net/openldap24-server/Makefile U net/openldap24-server/files/slapd.sh.in U ports-mgmt/pkg/Makefile U ports-mgmt/pkg/distinfo U ports-mgmt/pkg/pkg-plist ___ 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: INDEX build failed for 7.x
On 3/30/12 6:12 AM, Ruslan Mahmatkhanov wrote: I believe you do not need an approval to fix things you broke. :) figured as much, but I didn't 'break' the master port, I wasn't committer.. in theory, eadler did by not considering the CONFLICTS. (don't blame him, but I wish I had seen his commit, and wish he would have followed through and taken the slaves) but, on to this port. silly slaves insist on lazarus-0.9.30 as their version, and I am trying things like PKGPREFIX, and the like to try to get it to change the PORTVERSION/NAME/ index. how do I see what it would use as INDEX name? (its 6:30 am, sun isn't up, haven't made coffee yet, hello there in russia. on a side note, I remember how thrilling it was in '94 to get emails from people with .ru email addresses when working on *BSD code for QNX. it was nice to see that engineers could cooperate, even then politicians could not.) can we tell jokes in ports@? or do I need to put it in my sig? we joke that politicians has its root in two words. poly, meaning many, and ticks, meaning little blood sucking insects. So, politicians means many little blood sucking insects. -- Michael Scheidell, CTO *| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ 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: INDEX build failed for 7.x
On 3/30/12 3:36 AM, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX-7 - please wait.. Done. Warning: Duplicate INDEX entry: lazarus-0.9.30 Committers on the hook: scheidell wen Most recent CVS update was: U editors/Makefile U editors/lazarus-gtk2/Makefile U editors/lazarus-gtk2/pkg-descr I marked port BROKEN for now so INDEX builds. Will get with submitter on his proposed fixes. (Master port needs CONFLICTS added for this and lazarus-qt4 also) -- Michael Scheidell, CTO *| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ 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: INDEX build failed for 7.x
Michael Scheidell wrote on 30.03.2012 14:41: On 3/30/12 6:12 AM, Ruslan Mahmatkhanov wrote: I believe you do not need an approval to fix things you broke. :) figured as much, but I didn't 'break' the master port, I wasn't committer.. in theory, eadler did by not considering the CONFLICTS. (don't blame him, but I wish I had seen his commit, and wish he would have followed through and taken the slaves) but, on to this port. silly slaves insist on lazarus-0.9.30 as their version, and I am trying things like PKGPREFIX, and the like to try to get it to change the PORTVERSION/NAME/ index. how do I see what it would use as INDEX name? To be honest, I'm not sure how to do this correctly, since I didn't faced with the slave ports yet. But I'd check an existing ports tree for examples and asked more experienced committers on #bsdports. As I understand you always can check if all is ok with an INDEX with `make index`. (its 6:30 am, sun isn't up, haven't made coffee yet, hello there in russia. on a side note, I remember how thrilling it was in '94 to get emails from people with .ru email addresses when working on *BSD code for QNX. it was nice to see that engineers could cooperate, even then politicians could not.) can we tell jokes in ports@? or do I need to put it in my sig? I believe there is nothing criminal when it's in context :). (this one not in the case) we joke that politicians has its root in two words. poly, meaning many, and ticks, meaning little blood sucking insects. So, politicians means many little blood sucking insects. Old, but good one. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: [HEADSUP] pkgng 1.0-beta9 please test
On Fri, Mar 30, 2012 at 11:12:42AM +0200, Baptiste Daroussin wrote: Hi, On behalf of pkgng crew, I'm happy to announce pkg 1.0-beta9 [...] Please note that normally this will be the last beta version, So we can expect an official package repository with the first RC? pgppiqvK9yYVo.pgp Description: PGP signature
Re: [HEADSUP] pkgng 1.0-beta9 please test
On 03/30/2012 01:10 PM, Lars Engels wrote: On Fri, Mar 30, 2012 at 11:12:42AM +0200, Baptiste Daroussin wrote: Hi, On behalf of pkgng crew, I'm happy to announce pkg 1.0-beta9 [...] Please note that normally this will be the last beta version, So we can expect an official package repository with the first RC? A public repo, maybe. An official repo endorsed by portmgr that's another story... :) ___ 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: databases/mysql55-client 5.5.22 fails to build on i386 WITH_OPENSSL
On 3/29/12 7:44 PM, John Marshall wrote: Attempts to build this port on i386 with WITH_OPENSSL (the default option) fail for me. I have tried four systems: 2 x 8.3-RC2 and 2 x 9.0-RELEASE. I don't have a 64-bit system available for test. All builds stop at the same place. Builds succeed on all systems if I set WITHOUT_OPENSSL. I could never get it to work, and google shows lots of issues. Also shows suggestions to NOT include ssl (yassl) in mysql itself, but wrap it in stunnel (for performance reasons) -- Michael Scheidell, CTO *| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ 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: INDEX build failed for 7.x
On 30 Mar 2012 12:04, Michael Scheidell scheid...@freebsd.org wrote: On 3/30/12 3:36 AM, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX-7 - please wait.. Done. Warning: Duplicate INDEX entry: lazarus-0.9.30 Committers on the hook: scheidell wen Most recent CVS update was: U editors/Makefile U editors/lazarus-gtk2/Makefile U editors/lazarus-gtk2/pkg-descr I marked port BROKEN for now so INDEX builds. Will get with submitter on his proposed fixes. (Master port needs CONFLICTS added for this and lazarus-qt4 also) BROKEN won't fix index build-- you need to remove the line from the category Makefile; disconnecting it from the build. 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: jabberd port doesn't come with any certificates and is not allowing authorization?
On Fri, Mar 30, 2012 at 10:47 AM, Matthew Seaman matt...@freebsd.org wrote: On 30/03/2012 08:57, Kaya Saman wrote: You've got both 'register-enable' and 'register-oob' -- you probably don't want both of those, unless you do have an out-of-band method to create user accounts. Actually to allow IM clients to register will be better, though later on when I do a full implementation I will need to authenticate to either PAM or AD. The point was that 'register-enable' turns on jabberd's internal account creation functions, whereas 'register-oob' says to go to a separate site in order to create the account. If you're using a user database from elsewhere (pam or AD for instance), then you'ld want neither of those options. That is for the future though, let me just get the base working in order to understand what I'm doing then I'll look at further options for authentication later. :-) snip cat foo.key foo.crt foo.pem This is an application specific thing: some apps like key and cert together like this, others use separate files for key and cert. I've got this done and referenced it within the c2s.xml file: [...] id realm='jabber.com' pemfile='/root/cert/server.pem' verify-mode='7' cachain='/root/cert/server.pem' require-starttls='true' register-enable='true' instructions='Enter a username and password to register with this server.' password-change='true' jabber.com/id [...] Is now this portion of the c2s.xml file however, I still get: [...] Mar 30 13:55:28 JABBER jabberd/sm[4580]: attempting connection to router at 127.0.0.1, port=5347 Mar 30 13:55:28 JABBER jabberd/router[4579]: [127.0.0.1, port=23777] connect Mar 30 13:55:28 JABBER jabberd/router[4579]: [127.0.0.1, port=19978] connect Mar 30 13:55:28 JABBER jabberd/s2s[4581]: connection to router established Mar 30 13:55:28 JABBER jabberd/router[4579]: [127.0.0.1, port=54420] authenticated as jabberd@jabberd-router Mar 30 13:55:28 JABBER jabberd/router[4579]: [s2s] set as default route Mar 30 13:55:28 JABBER jabberd/router[4579]: [s2s] online (bound to 127.0.0.1, port 54420) Mar 30 13:55:28 JABBER jabberd/c2s[4582]: connection to router established Mar 30 13:55:28 JABBER jabberd/router[4579]: [127.0.0.1, port=23777] authenticated as jabberd@jabberd-router Mar 30 13:55:28 JABBER jabberd/router[4579]: [c2s] online (bound to 127.0.0.1, port 23777) Mar 30 13:55:28 JABBER jabberd/sm[4580]: connection to router established Mar 30 13:55:28 JABBER jabberd/router[4579]: [127.0.0.1, port=19978] authenticated as jabberd@jabberd-router Mar 30 13:55:28 JABBER jabberd/router[4579]: [sm] online (bound to 127.0.0.1, port 19978) Mar 30 13:55:28 JABBER jabberd/sm[4580]: sm ready for sessions Mar 30 13:55:28 JABBER jabberd/router[4579]: [jabber.com] online (bound to 127.0.0.1, port 19978) Mar 30 13:55:28 JABBER jabberd/s2s[4581]: [0.0.0.0, port=5269] listening for connections Mar 30 13:55:28 JABBER jabberd/s2s[4581]: ready for connections Mar 30 13:55:28 JABBER jabberd/c2s[4582]: [0.0.0.0, port=5222] listening for connections Mar 30 13:55:28 JABBER jabberd/c2s[4582]: ready for connections Mar 30 13:55:42 JABBER jabberd/c2s[4582]: [8] [10.0.0.10, port=60660] connect Mar 30 13:55:42 JABBER jabberd/c2s[4582]: [8] [10.0.0.10, port=60660] disconnect jid=unbound, packets: 0 Mar 30 13:55:45 JABBER jabberd/c2s[4582]: [8] [10.0.0.10, port=60661] connect Mar 30 13:55:45 JABBER jabberd/c2s[4582]: [8] [10.0.0.10, port=60661] disconnect jid=unbound, packets: 0 The IM clients (Pidgin) settings are: Require Encryption Connection Port: 5222 Connection Server: srv.jabber.com Domain: jabber.com username: user password: passwd local alias: alias The Bind9 DNS zone looks like this: $TTL 1h ; default expiration time of all resource records without their own TTL value @ IN SOA ns1.jabber.com. info.jabber.com. ( 2012032802 ; serial number of this zone file 1d ; slave refresh (1 day) 2h ; slave retry time in case of a problem (2 hours) 4w ; slave expiration time (4 weeks) 1h ; maximum caching time in case of failed lookups (1 hour) ) ; @ IN NS ns1.jabber.com. ns1 IN A10.0.0.1 srv.jabber.com. IN A10.0.0.7 jabber.com. IN A10.0.0.7 _xmpp-server._tcp.jabber.com. IN SRV 0 0 5269 srv.jabber.com. _xmpp-client._tcp.jabber.com. IN SRV 0 0 5222 srv.jabber.com. _jabber._tcp.jabber.com. IN SRV 0 0 5269 srv.jabber.com. I'm guessing everything is setup properly but I don't get why the system isn't connecting? The jabberd service starts meaning that it's connecting to the MySQL DB. and looking at the config files everything else seems to be ok! Regards, Kaya Cheers, Matthew [*] Which just begs the question of who is this CA and why should I trust them to vouch for anyone else?
Re: [HEADSUP] pkgng 1.0-beta9 please test
On Fri, Mar 30, 2012 at 01:12:42PM +0200, Julien Laffaye wrote: On 03/30/2012 01:10 PM, Lars Engels wrote: On Fri, Mar 30, 2012 at 11:12:42AM +0200, Baptiste Daroussin wrote: Hi, On behalf of pkgng crew, I'm happy to announce pkg 1.0-beta9 [...] Please note that normally this will be the last beta version, So we can expect an official package repository with the first RC? A public repo, maybe. An official repo endorsed by portmgr that's another story... :) Actually this is the story we will provide a repo for RC for sure regards, Bapt pgpDoprDU1mzP.pgp Description: PGP signature
Re: FAQ on PORTREVISION bump?
On Fri, Mar 30, 2012 at 07:02:43AM +1100, Peter Jeremy wrote: On 2012-Mar-28 20:52:13 +, Philip M. Gollucci pgollu...@gmail.com wrote: Absolutely, b/c we maintain PORTREVISION for pointyhat not the end users This is completely backwards. The Project exists for end-users and end users need a way to determine when there's been a change to a port that needs them to re-install that port. Pointyhat provides automated testing facilities as a way to improve the quality of FreeBSD because not all committers are sufficiently careful. If PORTREVISION cannot adequately serve both end users pointyhat, then the ports system needs an additional, new flag to trigger pointyhat. I think Philip was wrong in his statement. PORTREVISION exists for the reason of telling the ports infrastructure (which pointyhat and the users use) of updates. End users and pointyhat use it constantly. -- WXS ___ 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: post-deinstall target is invalid
On Thu, Mar 29, 2012 at 01:40:16PM -0700, Jason Helfman wrote: On Thu, Mar 29, 2012 at 09:47:27PM +0200, Gabor Kovesdan thus spake: On 2012.03.29. 20:49, Jason Helfman wrote: I will work on a effort, as well, to get some supporting documentation into the Porter's Handbook. Jason, thanks for this cleanup work. Have you checked if there is any portlint check for this? It would also be very valuable. Gabor Your welcome, and thanks. I did consider it, however it was also noted to me that portlint shouldn't take the place of poor port coding. That doesn't mean it can't be done, but I also tend to agree with this. Perhaps adding logic to bpm would be a good way to wrap it up, as well. I'm not sure we should add anything to bpm. It's a legitimate name of a custom target which maintainers can use if they want. We should be vigilant of code which assumes it will be called though, but there's nothing wrong with it being a custom target that the maintainer wants for one reason or another. -- WXS ___ 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: FAQ on PORTREVISION bump?
On 3/30/12 9:16 AM, Wesley Shields wrote: On Fri, Mar 30, 2012 at 07:02:43AM +1100, Peter Jeremy wrote: On 2012-Mar-28 20:52:13 +, Philip M. Golluccipgollu...@gmail.com wrote: Absolutely, b/c we maintain PORTREVISION for pointyhat not the end users I think Philip was wrong in his statement. PORTREVISION exists for the maybe Philip forgot to put in the smilie face. and was making a joke. -- Michael Scheidell, CTO *| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ 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
INDEX build failed for 7.x
INDEX build failed with errors: Generating INDEX-7 - please wait.. Done. Warning: Duplicate INDEX entry: lazarus-0.9.30 Committers on the hook: bapt decke delphij ehaupt pav rm scheidell wen Most recent CVS update was: U Mk/bsd.sites.mk U devel/py-pylib/Makefile U devel/py-pylib/pkg-descr U editors/lazarus-gtk2/Makefile U emulators/virtualbox-ose/Makefile U emulators/virtualbox-ose-kmod/Makefile U net/Makefile U net/liferea/Makefile U net/liferea/distinfo U net/nyancat/Makefile U net/nyancat/distinfo U net/nyancat/pkg-descr U net/nyancat/files/pkg-message.in U ports-mgmt/pkg/Makefile U ports-mgmt/pkg/files/patch-pkg__check.c ___ 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
FW: [ast-users] Feature request: AST grep as shell built in
Just a heads up for everyone who may find this interesting... But
builtin grep and friends have now been added to ksh93...
- Forwarded message from Glenn Fowler g...@research.att.com -
Date: Fri, 30 Mar 2012 02:42:05 -0400
From: Glenn Fowler g...@research.att.com
To: g...@research.att.com, wendlin1...@googlemail.com
Cc: ast-us...@research.att.com, ast-develop...@research.att.com
Subject: Re: [ast-users] Feature request: AST grep as shell built in
X-Mailer: mailx (ATT/BSD) 9.9 2012-02-29
ast-cmdtst.2012-03-30.tgz md5 e84b44ba46bef61cf68c4d22dddf3b6b
source just posted to www.research.att.com/sw/download/beta/
it requires nmake to build so
you will need either the ast-base or ast-open package installed
download ast-cmdtst.2012-03-30.tgz lib/package/tgz
bin/package read
bin/package use # new ksh with viewpath env ready to build
cd cmdtst
nmake install
nmake test
then this line in a ksh script to test
builtin -f cmdtst grep egrep fgrep xargs
all of the standalone grep and xargs tests pass
but the builtin environment could introduce new bug vectors
--
don't ask me or the list how to build plugins without nmake
its encoded in the nmake rules and probe files
its portable to all target architectures (including linux hpux aix cygwin uwin
mvs macos)
it uses the same conditional-free makefile on all target architectures
it generates files using the native system file and directory naming conventions
in general ast { plugins, shared libraries, dlls } require nmake and
do not build with the bootstrap mamake/Mamfile
that's why bin/package always builds nmake first and then proceeds with the
remaining components
___
ast-users mailing list
ast-us...@research.att.com
https://mailman.research.att.com/mailman/listinfo/ast-users
- End forwarded message -
--
;s =;
pgpWcbGsYXnFi.pgp
Description: 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: INDEX build failed for 7.x
On 30 Mar 2012 12:04, Michael Scheidell scheid...@freebsd.org wrote: On 3/30/12 3:36 AM, Erwin Lansing wrote: INDEX build failed with errors: Generating INDEX-7 - please wait.. Done. Warning: Duplicate INDEX entry: lazarus-0.9.30 Committers on the hook: scheidell wen Most recent CVS update was: U editors/Makefile U editors/lazarus-gtk2/Makefile U editors/lazarus-gtk2/pkg-descr I marked port BROKEN for now so INDEX builds. Will get with submitter on his proposed fixes. (Master port needs CONFLICTS added for this and lazarus-qt4 also) If you tried PKGPREFIX I wouldn't be at all surprised :) Try PKGNAMESUFFIX=-qt4, and check it isn't clobbered in the master Makefile; using hyphens for this in PORTNAME isn't the way to go about it. make -V PKGNAME is your friend here, or even better make describe shows you what the INDEX line will look like (before it's transformed) 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: INDEX build failed for 7.x
On 3/30/12 11:42 AM, Chris Rees wrote: make -V PKGNAME is your friend here, or even better make describe shows you what the INDEX line will look like (before it's transformed) Think I tried that. if this was a minor mistake by a submitter, or even maybe a minor mistake by the maintainer, I might spend some time on it. But since this is a new port, and this person wants to be trusted at a maintainer, (and I have a day job), I'll see if he can't fix it first. -- Michael Scheidell, CTO *| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ 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
emulators/freebsd-kmod
Dear Ports Maintainers and kuriyama, emulators/freebsd-kmod has a typo in pkg-descr, where it says lodable instead of loadable. In addition, I have done the work necessary to port emulators/freebsd-kmod to Gentoo/FreeBSD. https://bugs.gentoo.org/show_bug.cgi?id=410199 The ebuild contains a few improvements on the original FreeBSD port where we copy only the parts of SYSDIR that we need to build the module. We also do hardlinks instead of copies when Gentoo Portage builds with user privileges. The NEEDSUBDIRS part of the ebuild was written by naota AT gentoo.org as part of Gentoo's review process. I have permission from him to upstream the improvements we made on the port. Feel free to adopt any improvements in the attachments in that bug report. Lastly, I have sent an email to gentoo-dev AT lists.gentoo.org and gentoo-bsd AT lists.gentoo.org requesting that the FreeBSD specific parts of the portage tree be relicensed under terms of the BSD-2 license. With a little luck, it will be possible to upstream improvements made in Gentoo/FreeBSD without any hassle in the future. Yours truly, Richard Yao signature.asc Description: OpenPGP digital signature
INDEX now builds successfully on 7.x
___ 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: FAQ on PORTREVISION bump?
On 03/30/12 13:16, Wesley Shields wrote: End users and pointyhat use it constantly. I might not agree with my statement myself; however its the way thing are. Historically even. If this was not the case, we would bump when the NON-DEFAULT packages change. (read OPTIONS or different versions of say perl) Rather than contradicting me, it would be great if a portmgr@ could chime in and say one way or the other. -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Director Operations, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. signature.asc Description: OpenPGP digital signature
Re: FAQ on PORTREVISION bump?
On 03/30/12 17:57, Philip M. Gollucci wrote: On 03/30/12 13:16, Wesley Shields wrote: End users and pointyhat use it constantly. I might not agree with my statement myself; however its the way thing are. Historically even. If this was not the case, we would bump when the NON-DEFAULT packages change. (read OPTIONS or different versions of say perl) Rather than contradicting me, it would be great if a portmgr@ could chime in and say one way or the other. I'm already knee deep in this thread, so let me say why we do it this way right now. If you bump it when you change a non-default setting but not the default one, you waste pointyhat resources for no reason. If you don't bump it, you save the resources on pointyhat, but you make end users life 'harder'. Personally, I don't care either way, b/c I know what changes result in a package change. Just having a formal policy is all thats needed. -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Director Operations, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. signature.asc Description: OpenPGP digital signature
Re: ports/166248: sendmail dies of signal 11 on freebsd in a virtualbox guest
Synopsis: sendmail dies of signal 11 on freebsd in a virtualbox guest Responsible-Changed-From-To: dougb-freebsd-ports Responsible-Changed-By: dougb Responsible-Changed-When: Fri Mar 30 19:49:02 UTC 2012 Responsible-Changed-Why: I have no connection to sendmail. You probably want to ask gshapiro. http://www.freebsd.org/cgi/query-pr.cgi?pr=166248 ___ 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: FAQ on PORTREVISION bump?
So, lets start: Am I the only one that finds he is too stupid to actually figure this out? I think it is still the most confusing aspect of committing/maintaining. When to bump PORTREVISION: * If you think the end user needs to rebuild the port. When not to bump PORTREVION: * If you think its a noop/waste of time/cpu for the end user to rebuild the port. Ok, flesh this out: examples When to bump PORTREVISION (when you want end user to build the port) * Mandatory: o When package changes (make package) o When dependencies change (Adding USE_PERL/BUILD_PERL/GETTEXT counts) o When pkg-plist changes (except for fixing .ifdef/NOPORT(DOCS|EXAMPLES)) o When the master port changes o When PORTVERSION CHANGES (must change back to 0, delete line) o When you want to force a relink with an updated (fixed) library o If a patch fixes something in the port o If you add new functionality o If you add/delete an OPTION o If you change the default for an OPTION * port committers have authority to bump PORTREVISION maintainer (implicit) if the master port/library port/dependency port requires any dependency to fit the list above. when NOT to * just fixing .ifdef/NOPORT(DOCS|EXAMPLES)) * if port was broken on any arch. (rebuilding on existing arch is a noop, and fixed arch didn't package anyway) * Fixing typo's in pkg-message, Comment * Updating port maintainer (new one or resetting port maintainer) * just petting portlint (space after name to tab), re-order sections (notice I left out pointyhat.. if it is overworked, lets send more hardware) -- Michael Scheidell, CTO *| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ 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/166248: sendmail dies of signal 11 on freebsd in a virtualbox guest
On 3/30/12 3:49 PM, do...@freebsd.org wrote: Synopsis: sendmail dies of signal 11 on freebsd in a virtualbox guest Responsible-Changed-From-To: dougb-freebsd-ports Responsible-Changed-By: dougb Responsible-Changed-When: Fri Mar 30 19:49:02 UTC 2012 Responsible-Changed-Why: I have no connection to sendmail. You probably want to ask gshapiro. http://www.freebsd.org/cgi/query-pr.cgi?pr=166248 shouldn't that be freebsd-ports-bugs? -- Michael Scheidell, CTO *| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell ___ 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: FAQ on PORTREVISION bump?
On 03/30/12 19:55, Michael Scheidell wrote: * Mandatory: o When package changes (make package) yes. Lets call this #1 o When dependencies change (Adding USE_PERL/BUILD_PERL/GETTEXT counts) #1 covers this. o When pkg-plist changes (except for fixing .ifdef/NOPORT(DOCS|EXAMPLES)) #1 covers this, this is the OPTIONS case (default vs not) o When the master port changes #1 covers this o When PORTVERSION CHANGES (must change back to 0, delete line) #1 covers this. o When you want to force a relink with an updated (fixed) library #1 covers this. This is in the library port itself. The dependencies figure this out. o If a patch fixes something in the port #1 covers this. o If you add new functionality #1 covers this. o If you add/delete an OPTION #1 covers this. (default vs not default OPTIONS). If you count the end user it doesn't matter if its off by default. o If you change the default for an OPTION #1 covers this. * port committers have authority to bump PORTREVISION maintainer (implicit) if the master port/library port/dependency port requires any dependency to fit the list above. not really relevant. * just fixing .ifdef/NOPORT(DOCS|EXAMPLES)) sure is relevant see above * if port was broken on any arch. (rebuilding on existing arch is a noop, and fixed arch didn't package anyway) removing IGNORE,BROKEN do not require this b/c there was previously no package. * Fixing typo's in pkg-message, Comment Yes, the package changes, but no the functionality doesn't, so this is correct. * Updating port maintainer (new one or resetting port maintainer) Correct. * just petting portlint (space after name to tab), re-order sections Correct. In short what you change is irrelevant. Does the resultant package change. Yes or No. The only question you need to answer is do we bump if the resultant package changes for configs other than default. -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Director Operations, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. signature.asc Description: OpenPGP digital signature
Re: ports/166248: sendmail dies of signal 11 on freebsd in a virtualbox guest
Synopsis: sendmail dies of signal 11 on freebsd in a virtualbox guest Responsible-Changed-From-To: freebsd-ports-freebsd-ports-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Fri Mar 30 23:04:27 UTC 2012 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=166248 ___ 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: post-deinstall target is invalid
On Thu, Mar 29, 2012 at 01:40:16PM -0700, Jason Helfman wrote: On Thu, Mar 29, 2012 at 09:47:27PM +0200, Gabor Kovesdan thus spake: On 2012.03.29. 20:49, Jason Helfman wrote: I will work on a effort, as well, to get some supporting documentation into the Porter's Handbook. Jason, thanks for this cleanup work. Have you checked if there is any portlint check for this? It would also be very valuable. Gabor Your welcome, and thanks. I did consider it, however it was also noted to me that portlint shouldn't take the place of poor port coding. That doesn't mean it can't be done, but I also tend to agree with this. Perhaps adding logic to bpm would be a good way to wrap it up, as well. I'm not sure we should add anything to bpm. It's a legitimate name of a custom target which maintainers can use if they want. We should be vigilant of code which assumes it will be called though, but there's nothing wrong with it being a custom target that the maintainer wants for one reason or another. -- WXS I don't completely disagree, however the target is never used, and in all cases it merely performed the actions that were already being done in a pkg-deinstall script, or the action wasn't done due to an assumption that the target was valid. -jgh ___ 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/166248: sendmail dies of signal 11 on freebsd in a virtualbox guest
On 3/30/12 3:49 PM, do...@freebsd.org wrote: Synopsis: sendmail dies of signal 11 on freebsd in a virtualbox guest Responsible-Changed-From-To: dougb-freebsd-ports Responsible-Changed-By: dougb Responsible-Changed-When: Fri Mar 30 19:49:02 UTC 2012 Responsible-Changed-Why: I have no connection to sendmail. You probably want to ask gshapiro. http://www.freebsd.org/cgi/query-pr.cgi?pr=166248 shouldn't that be freebsd-ports-bugs? it was reassigned, but yes. ___ 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
