Re: castget port

2016-01-24 Thread Kurt Jaeger
Hi! > i use /www/castget, and i noticed the port is version is 1.0.1, > the new version is 1.2.1, released a couple of weeks ago. > can someone update the port, or if not i'd like to volunteer to do it. > i will need someones help as i'm a computer hobbyist Thanks for the patch that you sent to

FreeBSD ports you maintain which are out of date

2016-01-24 Thread portscout
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

Re: Enabling AVAHI-option in cups-client results in circular dependency

2016-01-24 Thread Kurt Jaeger
Hi! > If cups-client is built with the AVAHI option, there will be a circular > dependency, it seems. There's a whole bunch of problem reports for some cups, and we're missing someone to really look into those. Difficult issue. -- p...@opsec.eu+49 171 3101372

Re: castget port

2016-01-24 Thread Kurt Jaeger
Hi! > Thanks for the patch that you sent to me directly. I'm build-testing > it right now and the patch looks fine, with those two changes: Building it on 9.3amd64 needed some patch (g_strlen -> strlen), see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206565 I have no idea if it still run

Re: castget port

2016-01-24 Thread don subleski via freebsd-ports
thanks for the help and guidance sorry to send it to you directly. from now on i'll send to https://bugs.freebsd.org i'll build the patched versionĀ  and let you know if there's any issues regards On Sunday, January 24, 2016 7:12 AM, Kurt Jaeger wrote: Hi! > Thanks for the patch that yo

textproc/elasticsearch2 Update to 2.1.1

2016-01-24 Thread Robert Simmons
Is there a committer that can take a look at this update. It includes Poudriere QA logs, and I can verify that it builds correctly in my environment ( 10.2-RELEASE-p10). https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206107 ___ freebsd-ports@freebsd.o

Re: textproc/elasticsearch2 Update to 2.1.1

2016-01-24 Thread Walter Schwarzenfeld
It is a maintained port. It needs approval from the maintainer. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: textproc/elasticsearch2 Update to 2.1.1

2016-01-24 Thread Robert Simmons
Understood. I'm trying to follow the protocol of submit bug, then ask on freebsd-ports, and only after those two, ping the maintainer directly. On Sun, Jan 24, 2016 at 5:33 PM, Walter Schwarzenfeld < w.schwarzenf...@utanet.at> wrote: > It is a maintained port. It needs approval from the maintaine

Re: textproc/elasticsearch2 Update to 2.1.1

2016-01-24 Thread Matthew Donovan
So your not following protocol then as the mailing list should only be asked until after the timeout happens. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-por

"synth status" same error as all commands, more data posted.

2016-01-24 Thread Jeffrey Bouquet via freebsd-ports
synth status Querying system about current package installations. Stand by, comparing installed packages against the ports tree. Stand by, building pkg(8) first ... Failed!! (Synth must exit) Unfortunately, the system upgrade failed. 11.0-CURRENT r288246 pkg-1.6.2 synth-0.98_5 /usr/ports /var/

Re: textproc/elasticsearch2 Update to 2.1.1

2016-01-24 Thread Kubilay Kocak
On 25/01/2016 2:31 PM, Matthew Donovan wrote: > So your not following protocol then as the mailing list should only be > asked until after the timeout happens. But we also LOVE proactive people/feedback, keep being vocal Robert! Also, if anyone would like clarification or has questions about our

Re: textproc/elasticsearch2 Update to 2.1.1

2016-01-24 Thread Kurt Jaeger
Hi! > So your not following protocol then as the mailing list should only be > asked until after the timeout happens. 10th of January to 24th of January, so 14 days. Doesn't that count as maintainer timeout ? -- p...@opsec.eu+49 171 3101372 4 years to go ! __