Re: ports/144142: sysutils/torque configuration issues
Synopsis: sysutils/torque configuration issues Responsible-Changed-From-To: trasz-ports Responsible-Changed-By: trasz Responsible-Changed-When: Fri Feb 26 08:22:09 UTC 2010 Responsible-Changed-Why: I'm no longer maintaining this. http://www.freebsd.org/cgi/query-pr.cgi?pr=144142 ___ 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/144142: sysutils/torque configuration issues
Synopsis: sysutils/torque configuration issues Responsible-Changed-From-To: ports-freebsd-ports-bugs Responsible-Changed-By: trasz Responsible-Changed-When: Fri Feb 26 08:23:53 UTC 2010 Responsible-Changed-Why: Fix 'responsible'. http://www.freebsd.org/cgi/query-pr.cgi?pr=144142 ___ 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: Bluefish 2.0.0 released!
On Thu, Feb 25, 2010 at 12:59:00PM -0800, Charlie Kester wrote: On Thu 25 Feb 2010 at 12:17:59 PST simp...@gmail.com wrote: News 2010 - February 15 - Bluefish 2.0.0 released! I can't find it in the latest ports collection. Others have explained how to contact the maintainer of a port, and how to determine that it has no maintainer. But perhaps some expectation-setting is needed here. Bluefish 2.0.0 was released a mere ten days ago. Before it will appear in the ports collection, two things have to happen. First the maintainer must modify the port as needed to get it to compile on FreeBSD. Sometimes that's trivially simple, sometimes it's diabolically complex. If the port is depended upon by others, for example, there might be a need to coordinate the update with them. So it's not unusual for the maintainer's part of the porting process to take several days or even weeks. That's true - and yes, there are port updates that take weeks sometimes. (although, well, some of *my* updates in the past have been known to take weeks for other reasons, not just the review and technical work) Second, after the maintainer has submitted a PR with the update, the committers need to test it. That takes time. Also, judging by what I can see in the list of currently-open PR's, many committers always have a dozen or more in process. It's not uncommon (or unreasonable) that this part of the porting process will take several days or even weeks in addition to the time the maintainer needed. Well, in this particular case, the maintainer of www/bluefish is a FreeBSD committer himself, so this part might take a bit less time :) But in general, it's true enough. G'luck, Peter -- Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 No language can express every thought unambiguously, least of all this one. pgplNcg82tj9f.pgp Description: PGP signature
Re: Checksum mismatch for ports/finance/homebank-4.2
On Fri, 26 Feb 2010 00:29:05 -0600, Doug Barton do...@freebsd.org wrote: On Fri, 26 Feb 2010, Ruslan Mahmatkhanov wrote: I've removed all the conversations from homebank author after patch from this PR was commited ). But he is released the new version (4.2.1) after i ask him if distfile was rerolled. Latter he is addmitted that reroll was the bad idea. There is only 4.2.1 and 4.0.2 and past versions: http://homebank.free.fr/public/ Original 4.2 distfile was removed. Since you're in contact with the author, perhaps he could provide a copy of the distfile that matches what's currently in ports? You need to relax... :-) He is author. Therefore, it makes no difference if he released new version or rerolled the tarball. If he said that he rerolled to fix the bug(s) then it's good enough. Same idea with new release version. Cheers, Mezz Doug -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.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
sysutils/syslog-ng3 processes
Hello, I've noticed that when I start syslog-ng3 daemon it starts two processes. I haven't seen this when running syslog-ng. Here are the processes: root 554 0.0 0.1 5320 2092 ?? I 4:46PM 0:00.00 /usr/local/sbin/syslog-ng -p /var/run/syslog.pid root 555 0.0 0.1 5320 2456 ?? Ss4:46PM 0:00.02 /usr/local/sbin/syslog-ng -p /var/run/syslog.pid I was wondering why it actually start two (identical?) processes? Anyone has an idea? Is this normal? Regards, -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT 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: sysutils/syslog-ng3 processes
On Fri, Feb 26, 2010 at 04:51:25PM +0200, Marin Atanasov wrote: Hello, I've noticed that when I start syslog-ng3 daemon it starts two processes. I haven't seen this when running syslog-ng. Here are the processes: root 554 0.0 0.1 5320 2092 ?? I 4:46PM 0:00.00 /usr/local/sbin/syslog-ng -p /var/run/syslog.pid root 555 0.0 0.1 5320 2456 ?? Ss4:46PM 0:00.02 /usr/local/sbin/syslog-ng -p /var/run/syslog.pid I was wondering why it actually start two (identical?) processes? Anyone has an idea? Is this normal? I think this would happen if you have two different scripts in /usr/local/etr/rc.d that launch the same daemon. I think the names of the scripts do not matter here. Do you have any stale rc.d scripts in /usr/local/etr/rc.d? HTH, Alexey. ___ 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: sysutils/syslog-ng3 processes
On Fri, Feb 26, 2010 at 5:16 PM, Alexey Shuvaev shuv...@physik.uni-wuerzburg.de wrote: On Fri, Feb 26, 2010 at 04:51:25PM +0200, Marin Atanasov wrote: Hello, I've noticed that when I start syslog-ng3 daemon it starts two processes. I haven't seen this when running syslog-ng. Here are the processes: root 554 0.0 0.1 5320 2092 ?? I 4:46PM 0:00.00 /usr/local/sbin/syslog-ng -p /var/run/syslog.pid root 555 0.0 0.1 5320 2456 ?? Ss4:46PM 0:00.02 /usr/local/sbin/syslog-ng -p /var/run/syslog.pid I was wondering why it actually start two (identical?) processes? Anyone has an idea? Is this normal? I think this would happen if you have two different scripts in /usr/local/etr/rc.d that launch the same daemon. I think the names of the scripts do not matter here. Do you have any stale rc.d scripts in /usr/local/etr/rc.d? HTH, Alexey. Hi, The system is a fresh 8.0 install. I've only syslog-ng rc.d script in /usr/local/etc/rc.d. Didn't find anything reported about this. Could it be a port bug or something? Regards, -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT 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: sysutils/syslog-ng3 processes
Marin Atanasov wrote: On Fri, Feb 26, 2010 at 5:16 PM, Alexey Shuvaev shuv...@physik.uni-wuerzburg.de wrote: On Fri, Feb 26, 2010 at 04:51:25PM +0200, Marin Atanasov wrote: Hello, I've noticed that when I start syslog-ng3 daemon it starts two processes. I haven't seen this when running syslog-ng. Here are the processes: root 554 0.0 0.1 5320 2092 ?? I 4:46PM 0:00.00 /usr/local/sbin/syslog-ng -p /var/run/syslog.pid root 555 0.0 0.1 5320 2456 ?? Ss4:46PM 0:00.02 /usr/local/sbin/syslog-ng -p /var/run/syslog.pid I was wondering why it actually start two (identical?) processes? Anyone has an idea? Is this normal? I think this would happen if you have two different scripts in /usr/local/etr/rc.d that launch the same daemon. I think the names of the scripts do not matter here. Do you have any stale rc.d scripts in /usr/local/etr/rc.d? HTH, Alexey. Hi, The system is a fresh 8.0 install. I've only syslog-ng rc.d script in /usr/local/etc/rc.d. Didn't find anything reported about this. Could it be a port bug or something? Regards, I can confirm this behavior on multiple clean 8.0 + syslog3 installs. I really didn't do any investigation and just chalked it up to a change in behavior in syslog 3.x. -- Sean McAfee Senior Systems Engineer ___ 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: Shoud devel port be RC or GIT based?
On Mon, 15 Feb 2010 00:45:27 + CeDeROM tomek.ce...@gmail.com wrote: Hello world! In a moments of hard testing just before a software release, releases of a RC (Release Candidate) packages are done to alow some final tests. I am wondering if it is convenient to create the devel port, to allow better testing for non-freebsd-aware users. Would that be more convenient to base such devel port on a RC releases, or directly the GIT repository? Depends on the target. RCs are usually more polished, but if what you want to test is the GIT at some points in time ... Generally we don't encourage ports that build from $VCS checked-out sources, but having a -devel port based on a tarball made from checked-out is OK. How would the dynamic pkg-plist file content look like in case of GIT build? Would files built from GIT repository are to be installed in /usr/local or some easry-to-remove specific location such as /tmp/devel/portname ? PREFIX (which default to /usr/local). Is it convenient at all to create GIT based devel port if the user needs to use standard git procedure anyway to upload the rewritten/updated files? Again it depend on what you want. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Shoud devel port be RC or GIT based?
On 15/02/2010 01:45, CeDeROM wrote: In a moments of hard testing just before a software release, releases of a RC (Release Candidate) packages are done to alow some final tests. I am wondering if it is convenient to create the devel port, to allow better testing for non-freebsd-aware users. Would that be more convenient to base such devel port on a RC releases, or directly the GIT repository? This approach is not very popular. An RC release is fine, but if you want to test builds right from a repository, you are well advised to create snapshots, package them and base your ports on these. An example for this is the games/ioquake3-devel port: ftp://deponie.yamagi.org/freebsd/distfiles/ioquake3/ I update that whenever significant changes occur on SVN. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: TLS(and by extension all threading) completely broken in Valgrind on i386/amd64
On Sun, 7 Feb 2010 14:06:18 -0500 Ryan Stone ryst...@gmail.com mentioned: I've been trying out valgrind on some threaded FreeBSD applications but they've been deadlocking at startup. I've identified that the root cause is that FreeBSD's thread local storage is not being emulated properly by valgrind. The problem on amd64 is obvious: valgrind gives an invalid opcode error when the program tries to execute any instruction that accesses the gs register. On i386 the problem is much more subtle. I've attached two test applications that demonstrate the problem. In pthread_self.c, I create one thread which periodically prints pthread_self(), and then 10 seconds later I create a second thread. After the second thread is created, the first thread believes that it is the second thread. Here's an example invocation: Thank you a lot for the information, I'll try to look into this soon and will followup in detail. Sorry for delay in replying. -- Stanislav Sedov ST4096-RIPE ___ 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
