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,

Re: The ports collection has some serious issues

On Fri, 16 Dec 2016, at 16:34, Roger Marquis wrote: > If portmaster was part of base I'd agree that it should be deprecated, > however, being a port it can be afforded more leeway. All portmaster > needs IMO is a strong WARNING message to be displayed on installation A) > enumerating some of the

Re: Gettext Issues

On Fri, 16 Dec 2016 17:17:52 -0700 "@lbutlr" wrote: >> On 16 Dec 2016, at 00:22, @lbutlr wrote: >>> 2014-11-30 >>> Affects: users of devel/gettext (close to everyone) >>> Author: t...@freebsd.org >>> Reason: >>> The devel/gettext port has been split up in

Re: The ports collection has some serious issues

I tried to switch from portmaster to synth yesterday. Tests was sponsored by zfs snapshots. I still have strong opinion that synth IS NOT replacement for portmaster and not usable at all. Yes, synth build ports, however it's just builds them. I don't receive information: 1. Why it builds

Re: The ports collection has some serious issues

tacking a slightly off-topic topic onto this one On 12/15/16 10:31 AM, list-freebsd-po...@jyborn.se wrote: On Thu, Dec 15, 2016 at 01:18:05PM -0500, George Mitchell wrote: On 12/15/16 09:40, Warren Block wrote: On Thu, 8 Dec 2016, Matt Smith wrote: On Dec 08 05:16, Daniil Berendeev wrote:

Re: The ports collection has some serious issues

John Marino wrote: > In fact, anyone that updates ports should use either poudriere testport > or synth test. Then consider these relinquished: /usr/ports/archivers/zip /usr/ports/astro/wmmoonclock /usr/ports/astro/xearth /usr/ports/devel/byaccj /usr/ports/devel/csmith /usr/ports/devel/gzstream

Re: www/h2o needs a committer [BZ#213733]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213733 www/h2o update this still needs a committer - I am getting bugged by users waiting for this to land. thanks! A+ Dave ___ freebsd-ports@freebsd.org mailing list

Re: The ports collection has some serious issues

On 17/12/2016 13:22, Torfinn Ingolfsen wrote: On Fri, Dec 16, 2016 at 3:45 PM, John Marino wrote: Now, regarding synth: as I have already said, I have no special interest in package builders. I do need a tool to build and install the ports I use, and my current

Re: The ports collection has some serious issues

On 12/17/2016 01:49, Hrant Dadivanyan wrote: On Fri, Dec 16, 2016 at 6:42 AM, Peter Jeremy wrote: On 2016-Dec-15 19:31:22 +0100, list-freebsd-ports at jyborn.se wrote: Interestingly, the most vocal proponent of deleting portmaster and portupgrade is the author/maintainer of synch. It's not

The ports collection has some serious issues

From Thomas Mueller: From John Marino: Starting with a clean system: 1) install synth from binary package from official freebsd builder (a single package) 2) Configure synth if necessary 3) command synth to build itself 4) pkg delete synth (system is once again clean) 5) pkg add -F

The ports collection has some serious issues

abi wrote: I tried to switch from portmaster to synth yesterday. Tests was sponsored by zfs snapshots. I still have strong opinion that synth IS NOT replacement for portmaster and not usable at all. Yes, synth build ports, however it's just builds them. I don't receive information: 1. Why it

Re: The ports collection has some serious issues

> On 17 Dec 2016, at 14:26, Alphons van Werven wrote: > > John Marino wrote: > >> In fact, anyone that updates ports should use either poudriere testport >> or synth test. > > Then consider these relinquished: > > /usr/ports/archivers/zip > /usr/ports/astro/wmmoonclock

Re: The ports collection has some serious issues

On 12/17/2016 07:55, Michael Gmelin wrote: On 17 Dec 2016, at 14:26, Alphons van Werven wrote: John Marino wrote: In fact, anyone that updates ports should use either poudriere testport or synth test. Then consider these relinquished: /usr/ports/archivers/zip

Re: The ports collection has some serious issues

On Fri, Dec 16, 2016 at 3:45 PM, John Marino wrote: >> > >> I won't say "never". But I feel that both package builders (poudriere, >> synth) need some more time to shake out more issues / bugs and get >> into a better shape first. This isn't based on any specific

Re: The ports collection has some serious issues

2. It doesn't provide dialog for port options, so 2.1 I don't receive information if port options have changed. I don't know what else will be pulled to my system after port tree update. which of course is a false statement. If you set port options which then change, Synth will stop and tell

graphics/ocropus - new repository?

FWIW, it looks like https://github.com/tmbdev/ocropy is a (new) repository for ocropus source code. HTH -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe,

Re: The ports collection has some serious issues

On 12/17/2016 12:34, abi wrote: 2. It doesn't provide dialog for port options, so 2.1 I don't receive information if port options have changed. I don't know what else will be pulled to my system after port tree update. which of course is a false statement. If you set port options which then

Re: The ports collection has some serious issues

On 12/17/2016 13:35, Mark Linimon wrote: This is the sixth "top of thread" post. Could you please arrange to stop breaking email threading? Thanks. mcl I have to assume you're talking to me. Mark: 1) I am not subscribed to the mail list 2) FreeBSD chooses not to store the raw email content

Re: The ports collection has some serious issues

On 12/17/2016 13:47, Alphons van Werven wrote: Needless to say, not being a committer myself, whether/that said folks are required to use Poudriere and/or Synth for their QA checking is ipso facto none of my concern. However, I'm pretty sure I know what comes next. When maintainers need to

Dropping enigmail support from enigmail

After upgrading to thunderbird-45.5.1_6 I noticed that enigmail (and lightning) support were gone from thunderbird. I tried to find a replacement package until I read the svn log message: gecko: drop ENIGMAIL, LIGHTNING to simplify updates ENIGMAIL can still return as www/xpi-enigmail but, alas,

Re: The ports collection has some serious issues

This is the sixth "top of thread" post. Could you please arrange to stop breaking email threading? Thanks. mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: The ports collection has some serious issues

Michael Gmelin wrote: > Maybe you could elaborate a bit more what you find so annoying about > running "poudriere testport origin" before doing "svn commit" that you > are willing to drop port maintainership over it? Sure. In this case it's the precedent that bugs me. Needless to say, not being

Re: The ports collection has some serious issues

> On 17 Dec 2016, at 20:47, Alphons van Werven wrote: > > Michael Gmelin wrote: > >> Maybe you could elaborate a bit more what you find so annoying about >> running "poudriere testport origin" before doing "svn commit" that you >> are willing to drop port maintainership

Re: The ports collection has some serious issues

>From John Marino: > At face value, this doesn't make sense because synth is a tool for building > everything from source, so your development system is exactly where it should > be installed. > So you must be talking about build dependencies of synth (there are no run > dependencies). While I

Re: The ports collection has some serious issues

Since you insist it's perfect, I thought I'd try synth... On 2016-Dec-16 09:06:30 -0600, John Marino wrote: >Starting with a clean system: >1) install synth from binary package from official freebsd builder (a >single package) I don't understand why I need to install

Re: The ports collection has some serious issues

On 12/17/2016 19:35, Peter Jeremy wrote: $ cd /usr/ports/ports-mgmt/synth/ && make [ about an hour of grinding away elided ] ===> ini_file_manager-03_2 depends on file: /usr/local/gcc6-aux/bin/ada - not found ===> gcc6-aux-20160822 is only for amd64 i386, while you are running armv6.

Re: The ports collection has some serious issues

John Marino wrote: > maybe you could open one final PR and provide a patch that does this? Fair enough, will do. Fonz -- A.J. "Fonz" van Werven Notice: this e-mail address wil expire on Sat 24 Dec 2016. signature.asc Description: PGP signature

Re: Dropping enigmail support from enigmail

Martin Birgmeier writes: > After upgrading to thunderbird-45.5.1_6 I noticed that enigmail (and > lightning) support were gone from thunderbird. I tried to find a > replacement package until I read the svn log message: Lightning had 2 copies, only one of those was removed. For

Re: The ports collection has some serious issues

On Saturday, 17 December 2016 at 20:16:12 -0600, John Marino wrote: > On 12/17/2016 19:35, Peter Jeremy wrote: >> $ cd /usr/ports/ports-mgmt/synth/ && make >> [ about an hour of grinding away elided ] >> ===> ini_file_manager-03_2 depends on file: /usr/local/gcc6-aux/bin/ada - >> not found >>

Re: The ports collection has some serious issues

On 12/18/2016 00:43, Greg 'groggy' Lehey wrote: On Saturday, 17 December 2016 at 20:16:12 -0600, John Marino wrote: On 12/17/2016 19:35, Peter Jeremy wrote: $ cd /usr/ports/ports-mgmt/synth/ && make [ about an hour of grinding away elided ] ===> ini_file_manager-03_2 depends on file:

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,