openssl port - patch file
Hi, you've changed the PATCHFILES to dtls-bugs-2009-05-18.patch for openssl - but I'm not able to fetch this file nor does google found it... so where can I get it from? Greetings, Oliver ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: openssl port - patch file
On Fri, Aug 14, 2009 at 10:19:27AM +0200, Oliver Lehmann wrote:
Hi,
you've changed the PATCHFILES to dtls-bugs-2009-05-18.patch for openssl -
but I'm not able to fetch this file nor does google found it... so where
can I get it from?
I think that there are two problems here.
First, Dirk Meyer has placed this file in his local distfiles directory
on the FreeBSD cluster, but it has not yet propagated to the FTP servers.
This should take a couple of hours, a day at most.
Second, the security/openssl/Makefile is indeed referring to
${MASTER_SITE_LOCAL} in PATCH_SITES, but it is missing a subdirectory
there. Thus, even after the patch propagates to the FreeBSD FTP mirrors,
the port's Makefile will still be looking for it in the wrong place.
The following trivial patch should fix that; Dirk, I could commit it
if you are busy.
Index: ports/security/openssl/Makefile
===
RCS file: /fs/ncvs/ports/security/openssl/Makefile,v
retrieving revision 1.153
diff -u -r1.153 Makefile
--- ports/security/openssl/Makefile 14 Aug 2009 06:32:22 - 1.153
+++ ports/security/openssl/Makefile 14 Aug 2009 08:29:53 -
@@ -16,6 +16,7 @@
MASTER_SITE_SUBDIR=source
#PATCH_SITES= http://sctp.fh-muenster.de/dtls/
PATCH_SITES= ${MASTER_SITE_LOCAL}
+PATCH_SITE_SUBDIR= dinoex
PATCHFILES=dtls-bugs-2009-05-18.patch
DISTNAME= ${PORTNAME}-${PORTVERSION}
G'luck,
Peter
--
Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553
This inert sentence is my body, but my soul is alive, dancing in the sparks of
your brain.
pgpckqXSNpFpu.pgp
Description: PGP signature
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
how can I write a whitespace into a MASTER_SITE_SUBDIR?
Hi, all: How can I write a whitespace into a MASTER_SITE_SUBDIR? Because a package's fetch address is something like: http://../atutor 1.6.3/atutor-1.6.3.tar.gz Thanks at advance. wen ___ 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: how can I write a whitespace into a MASTER_SITE_SUBDIR?
On Fri, Aug 14, 2009 at 07:36:17PM +0800, wen heping wrote: Hi, all: Hi Wen, How can I write a whitespace into a MASTER_SITE_SUBDIR? Because a package's fetch address is something like: http://../atutor 1.6.3/atutor-1.6.3.tar.gz Usually a whitespace in a URL can be encoded by %20, does this help for this port? Cheers, -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org pgpKQZRQEDNLe.pgp Description: PGP signature
Re: Updating the Mailscanner port
Mike Jakubik wrote: On Mon, March 30, 2009 9:49 pm, Mark Linimon wrote: On Thu, Mar 26, 2009 at 09:04:30PM +1100, Peter Jeremy wrote: If the existing maintainer has disappeared, one option would be for you to take over maintainership: Upgrade mailscanner yourself and submit the upgrade as a PR that also transfers maintainership to youself. If there's no response after about 2 weeks, the port is yours. Actually, there is a 2-week timeout on updates, but a 3-month timeout on maintainer inactivity for transferring maintainership. Vacations can last more than 2 weeks :-) I've just submitted a patch that updates this port to the latest version, perhaps we can squeeze it in before the freeze. http://www.freebsd.org/cgi/query-pr.cgi?pr=137747 Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org I noticed a couple of things here. The 4.78.9 version is still listed as Beta according to the MailScanner site, though the site may just not have updated yet. Second, the patch submitted forces perl 5.10+ as a requirement. I've seen nothing on the MailScanner site that says that this is a requirement, and have had no problems myself using any of the Beta versions with perl 5.8.9_3. Given that upgrading perl is not something to be done lightly, I was wondering what issues people were seeing that 5.10 fixed. Thanks ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
RE: Updating the Mailscanner port
Mike Jakubik wrote: On Mon, March 30, 2009 9:49 pm, Mark Linimon wrote: On Thu, Mar 26, 2009 at 09:04:30PM +1100, Peter Jeremy wrote: If the existing maintainer has disappeared, one option would be for you to take over maintainership: Upgrade mailscanner yourself and submit the upgrade as a PR that also transfers maintainership to youself. If there's no response after about 2 weeks, the port is yours. Actually, there is a 2-week timeout on updates, but a 3-month timeout on maintainer inactivity for transferring maintainership. Vacations can last more than 2 weeks :-) I've just submitted a patch that updates this port to the latest version, perhaps we can squeeze it in before the freeze. http://www.freebsd.org/cgi/query-pr.cgi?pr=137747 Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org I noticed a couple of things here. The 4.78.9 version is still listed as Beta according to the MailScanner site, though the site may just not have updated yet. Second, the patch submitted forces perl 5.10+ as a requirement. I've seen nothing on the MailScanner site that says that this is a requirement, and have had no problems myself using any of the Beta versions with perl 5.8.9_3. Given that upgrading perl is not something to be done lightly, I was wondering what issues people were seeing that 5.10 fixed. Thanks I am running quit a few Mailscanner servers, and they all failed under perl 5.8.9 This was on FreeBSD 6.x, 7.x and 8-Current that time, when i switched to 5.10.x or back to 5.8.8 my problems went away. if you google on FreeBSD perl 5.8.9 and mailscanner there are a lot of people reporting issues. Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.55/2301 - Release Date: 08/13/09 18:16:00 ___ 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: Updating the Mailscanner port
Johan Hendriks wrote: Mike Jakubik wrote: On Mon, March 30, 2009 9:49 pm, Mark Linimon wrote: On Thu, Mar 26, 2009 at 09:04:30PM +1100, Peter Jeremy wrote: If the existing maintainer has disappeared, one option would be for you to take over maintainership: Upgrade mailscanner yourself and submit the upgrade as a PR that also transfers maintainership to youself. If there's no response after about 2 weeks, the port is yours. Actually, there is a 2-week timeout on updates, but a 3-month timeout on maintainer inactivity for transferring maintainership. Vacations can last more than 2 weeks :-) I've just submitted a patch that updates this port to the latest version, perhaps we can squeeze it in before the freeze. http://www.freebsd.org/cgi/query-pr.cgi?pr=137747 Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org I noticed a couple of things here. The 4.78.9 version is still listed as Beta according to the MailScanner site, though the site may just not have updated yet. Second, the patch submitted forces perl 5.10+ as a requirement. I've seen nothing on the MailScanner site that says that this is a requirement, and have had no problems myself using any of the Beta versions with perl 5.8.9_3. Given that upgrading perl is not something to be done lightly, I was wondering what issues people were seeing that 5.10 fixed. Thanks I am running quit a few Mailscanner servers, and they all failed under perl 5.8.9 This was on FreeBSD 6.x, 7.x and 8-Current that time, when i switched to 5.10.x or back to 5.8.8 my problems went away. if you google on FreeBSD perl 5.8.9 and mailscanner there are a lot of people reporting issues. Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.55/2301 - Release Date: 08/13/09 18:16:00 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org I do remember seeing these problems reported, but for the life of me, I can not reproduce them. I use 5.8.9 in production, and get 20 to 40 thousand messages a day scanned without a problem. I am setting up a new server, and I will try 5.10 on that and see how things go. ___ 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: Updating the Mailscanner port
On Fri, 14 Aug 2009 11:18:13 -0400 Kevin Kobb kk...@skylinecorp.com wrote: Johan Hendriks wrote: Mike Jakubik wrote: On Mon, March 30, 2009 9:49 pm, Mark Linimon wrote: On Thu, Mar 26, 2009 at 09:04:30PM +1100, Peter Jeremy wrote: If the existing maintainer has disappeared, one option would be for you to take over maintainership: Upgrade mailscanner yourself and submit the upgrade as a PR that also transfers maintainership to youself. If there's no response after about 2 weeks, the port is yours. Actually, there is a 2-week timeout on updates, but a 3-month timeout on maintainer inactivity for transferring maintainership. Vacations can last more than 2 weeks :-) I've just submitted a patch that updates this port to the latest version, perhaps we can squeeze it in before the freeze. http://www.freebsd.org/cgi/query-pr.cgi?pr=137747 Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org I noticed a couple of things here. The 4.78.9 version is still listed as Beta according to the MailScanner site, though the site may just not have updated yet. Second, the patch submitted forces perl 5.10+ as a requirement. I've seen nothing on the MailScanner site that says that this is a requirement, and have had no problems myself using any of the Beta versions with perl 5.8.9_3. Given that upgrading perl is not something to be done lightly, I was wondering what issues people were seeing that 5.10 fixed. Thanks I am running quit a few Mailscanner servers, and they all failed under perl 5.8.9 This was on FreeBSD 6.x, 7.x and 8-Current that time, when i switched to 5.10.x or back to 5.8.8 my problems went away. if you google on FreeBSD perl 5.8.9 and mailscanner there are a lot of people reporting issues. Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.55/2301 - Release Date: 08/13/09 18:16:00 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org I do remember seeing these problems reported, but for the life of me, I can not reproduce them. I use 5.8.9 in production, and get 20 to 40 thousand messages a day scanned without a problem. I am setting up a new server, and I will try 5.10 on that and see how things go. ___ 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 This is most likely the common problem. ports/UPDATING states: 20090113: AFFECTS: users of lang/perl5.8 AUTHOR: s...@freebsd.org lang/perl5.8 has been updated to 5.8.9. You should update everything that depends on perl. The easiest way to do that is to use perl-after-upgrade script supplied with lang/perl5.8. Please see its manual page for details. Please check UPDATING after to follow up on any other updates for perl that you might have to perform. This explains why going back to 5.8.8 works for you. Best regards. -- Jason J. Hellenthal +1.616.403.8065 jas...@dataix.net I pledge Allegiance to the Flag of the United States of America, and to the Republic for which it stands; one Nation under God, Indivisible, with Liberty and Justice for all. ___ 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: Updating the Mailscanner port
On Fri, August 14, 2009 11:18 am, Kevin Kobb wrote: I do remember seeing these problems reported, but for the life of me, I can not reproduce them. I use 5.8.9 in production, and get 20 to 40 thousand messages a day scanned without a problem. I am setting up a new server, and I will try 5.10 on that and see how things go. There seems to be some kind of include problem with this version of perl on freebsd and mailscanner. I am not sure what exact condition triggers the issue, but enough people have complained about this. As of now I am unable to run mailscanner on any of my systems with perl 5.8.9, which version are you using? http://www.mail-archive.com/freebsd-ports@freebsd.org/msg18581.html Upgrading perl can indeed be a pain, as this problem shows, however i am not a perl programmer and i don't know how to address this issue. Perl 5.10 seems to work great. Since no one has addressed this and Jan does not seem to maintain this anymore, i took the initiative to update the port, as i needed a new version. This is the latest version, which is labeled as beta. It seems to be running just fine here, but it would be nice if more people could test it. ___ 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: Updating the Mailscanner port
Mike Jakubik wrote: On Fri, August 14, 2009 11:18 am, Kevin Kobb wrote: I do remember seeing these problems reported, but for the life of me, I can not reproduce them. I use 5.8.9 in production, and get 20 to 40 thousand messages a day scanned without a problem. I am setting up a new server, and I will try 5.10 on that and see how things go. There seems to be some kind of include problem with this version of perl on freebsd and mailscanner. I am not sure what exact condition triggers the issue, but enough people have complained about this. As of now I am unable to run mailscanner on any of my systems with perl 5.8.9, which version are you using? http://www.mail-archive.com/freebsd-ports@freebsd.org/msg18581.html Upgrading perl can indeed be a pain, as this problem shows, however i am not a perl programmer and i don't know how to address this issue. Perl 5.10 seems to work great. Since no one has addressed this and Jan does not seem to maintain this anymore, i took the initiative to update the port, as i needed a new version. This is the latest version, which is labeled as beta. It seems to be running just fine here, but it would be nice if more people could test it. ___ 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 In production, I am using the official 4.75 FreeBSD port, which I submitted the patches for so if it is messed up it is probably my fault ;) I've also used 4.77 without problem, and very briefly tested 4.78. If people are having trouble and the port could strongly recommend using 5.10 that might be better. Doing a quick scan of /usr/ports, I didn't find any ports that specifically required 5.10+. I am not a perl programmer either, but if you want to take this port and upgrade it, I would be happy to help or test. I'm not sure what the status is of the listed maintainer. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
RE: Updating the Mailscanner port
Johan Hendriks wrote: Mike Jakubik wrote: On Mon, March 30, 2009 9:49 pm, Mark Linimon wrote: On Thu, Mar 26, 2009 at 09:04:30PM +1100, Peter Jeremy wrote: If the existing maintainer has disappeared, one option would be for you to take over maintainership: Upgrade mailscanner yourself and submit the upgrade as a PR that also transfers maintainership to youself. If there's no response after about 2 weeks, the port is yours. Actually, there is a 2-week timeout on updates, but a 3-month timeout on maintainer inactivity for transferring maintainership. Vacations can last more than 2 weeks :-) I've just submitted a patch that updates this port to the latest version, perhaps we can squeeze it in before the freeze. http://www.freebsd.org/cgi/query-pr.cgi?pr=137747 Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org I noticed a couple of things here. The 4.78.9 version is still listed as Beta according to the MailScanner site, though the site may just not have updated yet. Second, the patch submitted forces perl 5.10+ as a requirement. I've seen nothing on the MailScanner site that says that this is a requirement, and have had no problems myself using any of the Beta versions with perl 5.8.9_3. Given that upgrading perl is not something to be done lightly, I was wondering what issues people were seeing that 5.10 fixed. Thanks I am running quit a few Mailscanner servers, and they all failed under perl 5.8.9 This was on FreeBSD 6.x, 7.x and 8-Current that time, when i switched to 5.10.x or back to 5.8.8 my problems went away. if you google on FreeBSD perl 5.8.9 and mailscanner there are a lot of people reporting issues. Regards, Johan Hendriks I do remember seeing these problems reported, but for the life of me, I can not reproduce them. I use 5.8.9 in production, and get 20 to 40 thousand messages a day scanned without a problem. I am setting up a new server, and I will try 5.10 on that and see how things go. ___ 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 This is most likely the common problem. ports/UPDATING states: 20090113: AFFECTS: users of lang/perl5.8 AUTHOR: s...@freebsd.org lang/perl5.8 has been updated to 5.8.9. You should update everything that depends on perl. The easiest way to do that is to use perl-after-upgrade script supplied with lang/perl5.8. Please see its manual page for details. Please check UPDATING after to follow up on any other updates for perl that you might have to perform. This explains why going back to 5.8.8 works for you. Best regards. -- Jason J. Hellenthal +1.616.403.8065 jas...@dataix.net Well i can assure you that that was not the case. I did test it by going to 5.10, which worked, do all the things in /usr/ports/UPDATING. Then going back to 5.8.9, it did not work. Going back to 5.8.8 it did work. I also did fresh installs on FreeBSD 6.x and 7.x with the new perl 5.8.9 at that time and MailScanner refused to work. 5.8.9. just did not work! here is the thread off that on the ports list http://lists.freebsd.org/pipermail/freebsd-ports/2009-February/052959.html I got an answer from someone who also had the same issue on a clean install. So let MailScanner depend on 5.10.x is not a so bad in my opinion. And if it is just a mailscanner server the update from 5.8.x to 5.10.x is not so bad to do. I did it on all my systems and not one did fail. approx 20 with FreeBSD 6.x, 7.x and 8-CURRENT at that time ___ 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: cmucl-19f_1
Hello, It looks like this port should depend on misc/compat6x rather than misc/compat4x. Douglas William Thrift doug...@douglasthrift.net http://douglasthrift.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
multimedia/mythtv - install fails
This is mythtv 0.21_2, installation fails: Added group mythtv. Added user mythtv. Starting mysql. *** Unable to start mysqld *** Error code 1 Stop in /usr/ports/multimedia/mythtv. *** Error code 1 Stop in /usr/ports/multimedia/mythtv. *** Error code 1 Stop in /usr/ports/multimedia/mythtv. And mysql is running: r...@kg-quiet# ps ax | grep mysql 23260 p0 S 0:00.01 /bin/sh /usr/local/bin/mysqld_safe --defaults-extra-file=/var/db/mysql/my.cnf --user=mysql 23281 p0 S 0:00.08 /usr/local/libexec/mysqld --defaults-extra-file=/var/db/mysql/my.cnf --basedir=/usr/local Running on: r...@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 7.2-STABLE FreeBSD 7.2-STABLE #6: Sat May 30 16:13:13 CEST 2009 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64 Wasn't this one fixed a while ago? -- Regards, Torfinn Ingolfsen ___ 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
