Looking for a commiter
Hi, I asked for a enchancement to print/gutenprint-base to which the maintainer agreed, but now need a good soul with commit bit: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196321 I'd also like that if somebody with an interest in image processing ports would be nice enough to have a look at a graphic/lensfun update I posted more than two month without any reply: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196182 I'm not feeling this is the right way to bump issues, is there any way I don't know of in the bugzilla to draw attention? Thanks in advance -- Matthieu Volat ma...@alkumuna.eu pgpmIEZYHZefe.pgp Description: OpenPGP digital signature
Re: Looking for a commiter
On 2015-02-24 15:07, Matthieu Volat wrote: Hi, I asked for a enchancement to print/gutenprint-base to which the maintainer agreed, but now need a good soul with commit bit: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196321 I'd also like that if somebody with an interest in image processing ports would be nice enough to have a look at a graphic/lensfun update I posted more than two month without any reply: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196182 I'm not feeling this is the right way to bump issues, is there any way I don't know of in the bugzilla to draw attention? Thanks in advance Committers are busy working on making the ports the way they are so the updates will happen when a committer has time to do so and I am sure they are aware of this. However you may join #bsdports on efnet and talk to any op. ___ 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: Looking for a commiter
On Tue, 24 Feb 2015 22:07:26 +0100 Matthieu Volat ma...@alkumuna.eu wrote Hi, I asked for a enchancement to print/gutenprint-base to which the maintainer agreed, but now need a good soul with commit bit: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196321 I'd also like that if somebody with an interest in image processing ports would be nice enough to have a look at a graphic/lensfun update I posted more than two month without any reply: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196182 I'm not feeling this is the right way to bump issues, is there any way I don't know of in the bugzilla to draw attention? Maybe this is what you'd like? https://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html#pr-followup HTH. Best wishes. --Chris Thanks in advance -- Matthieu Volat ma...@alkumuna.eu ___ 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: Looking for a commiter
On Tue, 24 Feb 2015 15:10:49 -0600 cpet c...@sdf.org wrote: On 2015-02-24 15:07, Matthieu Volat wrote: Hi, I asked for a enchancement to print/gutenprint-base to which the maintainer agreed, but now need a good soul with commit bit: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196321 I'd also like that if somebody with an interest in image processing ports would be nice enough to have a look at a graphic/lensfun update I posted more than two month without any reply: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196182 I'm not feeling this is the right way to bump issues, is there any way I don't know of in the bugzilla to draw attention? Thanks in advance Committers are busy working on making the ports the way they are so the updates will happen when a committer has time to do so and I am sure they are aware of this. However you may join #bsdports on efnet and talk to any op. Of course, I am very aware of this, I hope the request did not sound like a complain or such. I was just affraid that those PR would just never go anywhere, since I don't see how they would reach devs... -- Matthieu Volat ma...@alkumuna.eu pgptxWS7uUjve.pgp Description: OpenPGP digital signature
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/p5-File-MimeInfo | 0.26| 0.27 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt 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
opensmtpd 5.4.4 in freebsd 9 jail
Hello, Since I upgraded my freebsd 9 jail with the latest opensmtpd 5.4.4_1,1 port, smtp-out refuse to send any email to the outside world. I've seen a similar issue reported by Meutel here, but with no apparent solution: http://blog.gmane.org/gmane.mail.opensmtpd.general/day=20150211, 2nd post. Based on ktrace analysis, I believe the faulty code starts at line 210 of getaddrinfo_async.c in libasr: https://github.com/OpenSMTPD/libasr/blob/libasr-1.0.1/src/getaddrinfo_async.c This code returns EAI_NONAME if there is no non-loopback interface configured in the jail. This is my case, as a jail by default has only loopback interfaces configured (this doesn't prevent connecting to the outside world). If my analysis is correct, I believe that if no non-loopback interface is found, the code should also (in a second step) consider loopback interfaces when selecting IPv4 versus IPv6, instead of just bailing out. That would make the code more robust. Thanks, Cedric -- Cedric Berger Precidata Sarl Maladière 71c 2000 Neuchâtel ced...@precidata.com 032 930 29 62 079 934 11 02 ___ 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: squid 3.5 plans
On Mon, Feb 23, 2015 at 5:41 PM, Dewayne Geraghty dewayne.gerag...@heuristicsystems.com.au wrote: Thank you so much for posting this link! Merging r275456 and r275502 from stable/10 to my releng/10.1 src tree and rebuilding and installing the kernel, means that I can once again manage squid 3.4.n via the rc.d script instead of a prescribed series of kill(1) commands. Back to the original question: lets drop 3.3x and only support 3.4/3.5 in ports. ___ 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
