Date: Fri, 14 Aug 2009 20:53:10 +0200 From: "Johan Hendriks" <Johan@double-l.nl> To: <jasonh@DataIX.net> Cc: freebsd-ports@freebsd.org Subject: RE: Updating the "Mailscanner" port Message-ID: <57200BF94E69E54880C9BB1AF714BBCB0111BB@w2003s01.double-l.local> References: <20090325090758.1015bc2a@scorpio><20090326100430.GI56137@server.vk2pj.dyndns.org><20090331014900.GA24235@lonesome.com><1f8447334a4d96d2edfc74608d16f794.squirrel@wettoast.dyndns.org><4A855E0C.3090805@skylinecorp.com><57200BF94E69E54880C9BB1AF714BBCB5DEAEE@w2003s01.double-l.local><4A858035.80107@skylinecorp.com> <20090814115210.97a614b2.jasonh@DataIX.net>
next in thread | previous in thread | raw e-mail | index | archive | help
=20 >> Johan Hendriks wrote: >> >> Mike Jakubik wrote: >> >> =20 >> >>> On Mon, March 30, 2009 9:49 pm, Mark Linimon wrote: >> >>> =20 >> >>> =20 >> >>>> On Thu, Mar 26, 2009 at 09:04:30PM +1100, Peter Jeremy wrote: >> >>>> =20 >> >>>> =20 >> >>>>> 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 >> >>>>> =20 >> > yours. >> > =20 >> >>>>> =20 >> >>>>> =20 >> >>>> Actually, there is a 2-week timeout on updates, but a 3-month >> >>>> =20 >> > timeout >> > =20 >> >>>> on maintainer inactivity for transferring maintainership. = Vacations >> >>>> can last more than 2 weeks :-) >> >>>> =20 >> >>>> =20 >> >>> I've just submitted a patch that updates this port to the latest >> >>> =20 >> > version, >> > =20 >> >>> perhaps we can squeeze it in before the freeze. >> >>> >> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D137747 >> >>> >> >>> Thanks. >> >>> >> >>> _______________________________________________ >> >>> freebsd-ports@freebsd.org mailing list >> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> >>> To unsubscribe, send any mail to >> >>> =20 >> > "freebsd-ports-unsubscribe@freebsd.org" > > =20 > >>> =20 > >>> =20 > >> I noticed a couple of things here. The 4.78.9 version is still = listed >> >> =20 >> > as >> > =20 >> >> 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 >> >> =20 >> > >> > =20 >> >> 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 >> >> =20 >> > >> > 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 >> > =20 >> 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-unsubscribe@freebsd.org" >This is most likely the common problem. ports/UPDATING states: >20090113: > AFFECTS: users of lang/perl5.8 > AUTHOR: skv@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 j>asonh@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!=20 =20 here is the thread off that on the ports list http://lists.freebsd.org/pipermail/freebsd-ports/2009-February/052959.htm= l 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 =20 =20 =20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57200BF94E69E54880C9BB1AF714BBCB0111BB>