[9 RC][AMD64] ImageMagick failed to pass 'exceptions' self-test
mates, After the build, the ImageMagick port does not pass the 'exceptions' test: = ImageMagick 6.7.3: ./test-suite.log = 1 of 48 tests failed. .. contents:: :depth: 2 FAIL: Magick++/tests/exceptions.sh (exit: 139) == Segmentation fault (core dumped) --- A logfile and a 'warnings' file have been uploaded there: http://user.lamaiziere.net/david/bsd/ImageMagick.log http://user.lamaiziere.net/david/bsd/ImageMagick.warnings I also tried to use CLANG with the same result. I didn't find more explanations and/or log files regarding this issue. -- David Marec, mailto:david.ma...@davenulle.org http://user.lamaiziere.net/david/Site http://www.diablotins.org/ ___ 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: pr# for 9-10 problem?
On 9. Dec 2011, at 20:20 , Robert Huff wrote: Doug Barton writes: There is a problem building various ports caused by the FreeBSD major version number going from 9 to 10 (specifically, from single to double digits). My morning brain has been unable to find this in the PR database; would some kind soul please help? Read /usr/ports/UPDATING? If you mean 20110928 - that identifies the problem, and provides workarounds, but does not name the pr. Could it be that what you are looking for is one of the multiple threads like? http://lists.freebsd.org/pipermail/freebsd-ports/2011-October/thread.html#70765 -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. ___ 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: xapian-core-1.0.22,1
I noticed that xapian was held back to 1.0 while waiting for either dependant port maintainers to update to the newer version, or for a second copy of xapian to be added to ports. The last activity on the bug tracker seems to be from just over a year ago. Has there been any progress on getting xapian updated? I ask because I am trying to get notmuch (notmuchmail.org) going as a port. So far notmuch compiles, runs and functions just fine, but xapian 1.2 is said to be MUCH faster than 1.0, so I was hoping that you (being the maintainer) would be able to green-light the update. That is of course assuming the blocking packages/etc have been resolved. Thank You ~Doug Penner A.K.A. DarwinSurvivor ___ 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 unmaintained ports which are currently scheduled for deletion
lini...@freebsd.org wrote: portname: misc/gtkfind description:The program to use to have to remember all the options to find(1) maintainer: po...@freebsd.org deprecated because: No more public distfiles, no more upstream Looking at the Makefile, it appears that this port does not claim to have a MASTER_SITES other than MASTER_SITE_BACKUP, i.e. the FreeBSD servers. IOW, it looks as if we _are_ the upstream. expiration date:2011-12-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=miscportname=gtkfind ___ 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 unmaintained ports which are currently scheduled for deletion
On Sat, Dec 10, 2011 at 08:00:05AM -0800, per...@pluto.rain.com wrote: lini...@freebsd.org wrote: portname: misc/gtkfind description:The program to use to have to remember all the options to find(1) maintainer: po...@freebsd.org deprecated because: No more public distfiles, no more upstream Looking at the Makefile, it appears that this port does not claim to have a MASTER_SITES other than MASTER_SITE_BACKUP, i.e. the FreeBSD servers. IOW, it looks as if we _are_ the upstream. In other word all upstream died and as our mirror were the only place to find the distfiles $someone add it as a master_site. regards, Bapt pgpneaRhup29o.pgp Description: PGP signature
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/12/2011 16:00, per...@pluto.rain.com wrote: lini...@freebsd.org wrote: portname: misc/gtkfind description: The program to use to have to remember all the options to find(1) maintainer: po...@freebsd.org deprecated because: No more public distfiles, no more upstream Looking at the Makefile, it appears that this port does not claim to have a MASTER_SITES other than MASTER_SITE_BACKUP, i.e. the FreeBSD servers. IOW, it looks as if we _are_ the upstream. Hm. Are you interested in using it? I don't mind hosting it but it could do with a maintainer. Remember, we're only the upstream if someone is responsible for it. Also, its last update appears to be in 2003, and it's long dead Chris -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO4zY3AAoJELCEktHh68rElUMH/iMtb1V0gHjetuFWHwg4VQmU ozv9rXICbaQhDLOCsg9OWt/qDmEIV2YIP54924cdqPQ9C3tDJac3raGjdlva03NG i0eElsnNl5SiS2yDzkH63LWJN6lxQu/TmuzQjO03n+VaMLfxyPA6hVX7fl+a8tYS no8RZbzMTCEGM5C4qxMXM3X/30JXsLccUG6epTurp7cpmZRXvTx5P/JwyI2uoIrV sXq+I1KRy127nOzMl3gSJCNDNAGX7a5ItXCBJJDW6BTxs1FyAvuH2lXG8CMYK+cC zzEGC3FAQlDCVSjEpNZiUMG6lgep3+GjDXtrsloAi8CZtzIW4EMRT8uZrShfk6U= =4hlg -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pr# for 9-10 problem?
Doug Barton writes: Read /usr/ports/UPDATING? If you mean 20110928 - that identifies the problem, and provides workarounds, but does not name the pr. What are you trying to accomplish? I have some machines that I would like to update, but would prefer to hold off until a non-workaround solution is in place. (Understanding this may take some time.) I would like to see the pr(s?) so I can understand what obstacles remain and when an acceptable solution might happen. Robert Huff ___ 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: pr# for 9-10 problem?
Bjoern A. Zeeb writes: Read /usr/ports/UPDATING? If you mean 20110928 - that identifies the problem, and provides workarounds, but does not name the pr. Could it be that what you are looking for is one of the multiple threads like? http://lists.freebsd.org/pipermail/freebsd-ports/2011-October/thread.html#70765 I'm subscribed to ports@ (and current@ and questions@); I've seen those threads. I'm looking for what's behind the next curtain. Robert Huff ___ 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
security/putty on FreeBSD 9.0
Hi all, Has anyone here had any problems building security/putty on FreeBSD 9.0? If you do, please send me an email. I'd like to understand the problem a bit more and help resolve the issue. Unfortunately I cannot reproduce the problem on my 9.0 systems so I'm asking for volunteers to help test. -- Cheers, Cy Schubert cy.schub...@komquats.com FreeBSD UNIX: c...@freebsd.org Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ 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
dvdrip hang when PERL_VERSION=5.12.4
I just noticed that dvdrip does not work when PERL_VERSION=5.12.4. Ths symptom is a hang as soon as the user tries to create a new project. Here's the ps output: 150 5360 4704 1 40 0 236740 47116 umtxnI 20:00.88 /usr/local/bin/perl /usr/local/bin/dvdrip Note the umtxn. Forcing PERL_VERSION=5.8.9 and reinstalling dvdrip results in a working copy and creating a new project returns basically immediately and everything else also works. Just thought I'd report it for the archive. -- Gary Jennejohn ___ 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: xapian-core-1.0.22,1
Doug Penner writes: I noticed that xapian was held back to 1.0 while waiting for either dependant port maintainers to update to the newer version, or for a second copy of xapian to be added to ports. The last activity on the bug tracker seems to be from just over a year ago. Has there been any progress on getting xapian updated? I ask because I am trying to get notmuch (notmuchmail.org) going as a port. So far notmuch compiles, runs and functions just fine, but xapian 1.2 is said to be MUCH faster than 1.0, so I was hoping that you (being the maintainer) would be able to green-light the update. That is of course assuming the blocking packages/etc have been resolved. The Xapian 1.2 ports have been ready for a very long time, but there are apparently some strong reasons to stay with 1.0. All I can write is that I am ready to (re)-submit patches as soon as the way is cleared. Cheers, J.F. Dockes ___ 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: dvdrip hang when PERL_VERSION=5.12.4
On Sat, Dec 10, 2011 at 10:33 AM, Gary Jennejohn gljennj...@googlemail.com wrote: I just noticed that dvdrip does not work when PERL_VERSION=5.12.4. Ths symptom is a hang as soon as the user tries to create a new project. Here's the ps output: 150 5360 4704 1 40 0 236740 47116 umtxn I 2 0:00.88 /usr/local/bin/perl /usr/local/bin/dvdrip Note the umtxn. Forcing PERL_VERSION=5.8.9 and reinstalling dvdrip results in a working copy and creating a new project returns basically immediately and everything else also works. Just thought I'd report it for the archive. Ouch! umtxn is waiting on a kernel lock. This should NOT happen and it looks more like a kernel issue than a userland one. If you can still run dvdrip with 5.12.4, what does 'procstat -k PID show? It should provide some useful kernel stack information. Also, what version of FreeBSD and is it on i386, and64, or some other? -- 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: dvdrip hang when PERL_VERSION=5.12.4
On Sat, 10 Dec 2011 14:02:54 -0800 Kevin Oberman kob6...@gmail.com wrote: On Sat, Dec 10, 2011 at 10:33 AM, Gary Jennejohn gljennj...@googlemail.com wrote: I just noticed that dvdrip does not work when PERL_VERSION=5.12.4. Ths symptom is a hang as soon as the user tries to create a new project. Here's the ps output: 150 5360 4704 1 40 0 236740 47116 umtxn I 2 0:00.88 /usr/local/bin/perl /usr/local/bin/dvdrip Note the umtxn. Forcing PERL_VERSION=5.8.9 and reinstalling dvdrip results in a working copy and creating a new project returns basically immediately and everything else also works. Just thought I'd report it for the archive. Ouch! umtxn is waiting on a kernel lock. This should NOT happen and it looks more like a kernel issue than a userland one. If you can still run dvdrip with 5.12.4, what does 'procstat -k PID show? It should provide some useful kernel stack information. Also, what version of FreeBSD and is it on i386, and64, or some other? OK, just for you :) FreeBSD 10.0-CURRENT FreeBSD 10.0-CURRENT #160 r228349 amd64 procstat -k 3910 PIDTID COMM TDNAME KSTACK 3910 100157 perl5.12.4 -mi_switch sleepq_catch_signals sleepq_wait_sig _sleep _do_lock_umutex do_lock_umutex __umtx_op_wait_umutex amd64_syscall Xfast_syscall So actually, it's perl5.12.4 which is hanging. -- Gary Jennejohn ___ 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: xapian-core-1.0.22,1
Would it be possible to create a second port for the new (or old version)? Like databases/xapian12 or something? ~Doug Penner On Sat, 10 Dec 2011, j...@dockes.org wrote: Doug Penner writes: I noticed that xapian was held back to 1.0 while waiting for either dependant port maintainers to update to the newer version, or for a second copy of xapian to be added to ports. The last activity on the bug tracker seems to be from just over a year ago. Has there been any progress on getting xapian updated? I ask because I am trying to get notmuch (notmuchmail.org) going as a port. So far notmuch compiles, runs and functions just fine, but xapian 1.2 is said to be MUCH faster than 1.0, so I was hoping that you (being the maintainer) would be able to green-light the update. That is of course assuming the blocking packages/etc have been resolved. The Xapian 1.2 ports have been ready for a very long time, but there are apparently some strong reasons to stay with 1.0. All I can write is that I am ready to (re)-submit patches as soon as the way is cleared. Cheers, J.F. Dockes ___ 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: security/putty on FreeBSD 9.0
Am 10.12.2011 18:09, schrieb Cy Schubert: Hi all, Has anyone here had any problems building security/putty on FreeBSD 9.0? If you do, please send me an email. I'd like to understand the problem a bit more and help resolve the issue. Unfortunately I cannot reproduce the problem on my 9.0 systems so I'm asking for volunteers to help test. Greetings, Well - for me, too, security/putty builds properly, with all combination of OPTION-offered KNOBS, and appears to work in default configuration - including GSSAPI authentication and credential delegation for GSS-authenticated NFS4 mounts on Linux ssh hosts. Please Cc: me (I am the port maintainer) on reports you're mailing to Cy. Thank you. Best regards Matthias Andree ___ 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 unmaintained ports which are currently scheduled for deletion
Chris Rees cr...@freebsd.org wrote: portname: misc/gtkfind ... Looking at the Makefile, it appears that this port does not claim to have a MASTER_SITES other than MASTER_SITE_BACKUP, i.e. the FreeBSD servers. IOW, it looks as if we _are_ the upstream. Hm. Are you interested in using it? I don't mind hosting it but it could do with a maintainer. Remember, we're only the upstream if someone is responsible for it. I will maintain it if no one else comes forward. Also, its last update appears to be in 2003, and it's long dead s/long dead/in good enough shape to be useful/ :) ___ 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
Unable to build www/mediawiki
When I try to build www/mediawiki with built-in TeX rendering (WITH_TEXVC)
on, I get:
server% make
=== License check disabled, port has not defined LICENSE
=== Found saved configuration for mediawiki-1.18.0
=== Extracting for mediawiki-1.18.0
= SHA256 Checksum OK for mediawiki-1.18.0.tar.gz.
=== Patching for mediawiki-1.18.0
=== mediawiki-1.18.0 depends on executable: ocaml - found
=== mediawiki-1.18.0 depends on executable: gmake - found
=== mediawiki-1.18.0 depends on shared library: mysqlclient.16 - found
=== Configuring for mediawiki-1.18.0
=== Building for mediawiki-1.18.0
cd: can't cd to /tank/obj/usr/ports/www/mediawiki/work/mediawiki-1.18.0/math
*** Error code 2
Stop in /usr/ports/www/mediawiki.
*** Error code 1
Stop in /usr/ports/www/mediawiki.
server%
The cd fails because that directory doesn't exist (though the parent does).
This appears to be caused by:
# $FreeBSD: ports/www/mediawiki/Makefile,v 1.72 2011/12/08 01:56:00 wen Exp $
...
do-build:
.if defined(WITH_TEXVC)
@(cd ${WRKSRC}/math ${GMAKE})
.endif
Could you please look into this.
--
Peter Jeremy
pgpIPjZbf0zVb.pgp
Description: PGP signature
Re: again, ports that stop daemons
On Fri, Dec 09, 2011 at 01:25:25PM -0800, Doug Barton wrote: On 12/09/2011 13:18, Baptiste Daroussin wrote: On Sat, Dec 03, 2011 at 01:09:09AM +0200, Andriy Gapon wrote: on 02/12/2011 21:55 Baptiste Daroussin said the following: On Fri, Dec 02, 2011 at 08:38:05PM +0100, Torfinn Ingolfsen wrote: On Fri, Dec 2, 2011 at 1:13 PM, Andriy Gapon a...@freebsd.org wrote: Or that they simply quit doing that and instead print a message like Port X is deinstalled but it may have some processes running, please do Y and/or Z to find them and/or stop them. I prefer this suggestion. I also would prefer this. BTW, this part of my suggestion was inspired by the following: http://en.opensuse.org/SDB:Zypper_usage_11.3#Check_processes Not sure how that feature is implemented though. FYI, since a few minutes, pkgng handle rc scripts, disabled by default because I still consider this feature dangerous. to activate it is: HANDLE_RC_SCRIPTS=yes in pkg.conf I previously described what I thought was a pretty good way to handle this question that addressed the needs expressed by all of the posters on the previous thread, but my suggestion didn't get any responses. Since this has come up again, it would be helpful (to me at least) if people would think about my idea, and if nothing else tell me why I'm wrong. :) Quoting: Speaking only for myself I hate the idea of stopping/starting services automatically. However this feature is often requested, and is something that is provided by many other package systems. If we have people who are willing to do the work I think it's worth discussing how to do it properly. The way that I envision it working would be a 3-knob system. One knob to always restart the services, one to never do it; and then asking on a per-port basis, which should be the default. I can imagine portmaster detecting this option in the pre-build phase similarly to how it detects and warns about IS_INTERACTIVE now, and giving the user a menu of options for how to handle it. I'm happy to add more details if people are interested. Where this actually becomes interesting is not in the ports build/install process, which is pretty easy to deal with, but with package installs/deinstalls. I definitely think it's doable, what we probably want to do is put a knob for this in the port's Makefile, and handle the stop/start for both the port and the package with a little script that can be included in the package, and run with @exec and @unexec. Personally I think this is a little overboard... not your idea but the fact of trying to determine a function of restarting services for the user. If end-user is upgrading a package they should be prepared to take any neccesary action to start the services again after final actions are complete. Desperate services could have a periodic script that could handle the checks for these services and I strongly advise against taking any action whatsoever on starting or restarting or reloading. Stop the service if need be but never assume anything about starting a service without strict user interaction. If at all likelyness that this happens then I have one request... One simple knob that defaults to ``NO'' for restarting or starting or reloading. I think this is at least reasonable. pgpJw7e8whopf.pgp Description: PGP signature
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/11/2011 04:07 AM, per...@pluto.rain.com wrote: Chris Rees cr...@freebsd.org wrote: portname: misc/gtkfind ... Looking at the Makefile, it appears that this port does not claim to have a MASTER_SITES other than MASTER_SITE_BACKUP, i.e. the FreeBSD servers. IOW, it looks as if we _are_ the upstream. Hm. Are you interested in using it? I don't mind hosting it but it could do with a maintainer. Remember, we're only the upstream if someone is responsible for it. I can also reliably host this so there is more than one upstream. Lemme know if you need me. :) I will maintain it if no one else comes forward. Also, its last update appears to be in 2003, and it's long dead s/long dead/in good enough shape to be useful/ :) Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7kXc0ACgkQGK3MsUbJZn4MegCfVC/9DQ9hb9o2jcllu9tCQnMb N1sAnAxjmYLiTfDDnG1mMyWP+LAXmq01 =U2LH -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
