Re: The future of portmaster

On 30.05.2017 16:00, Adam Weinberger wrote: On 30 May, 2017, at 7:51, Anton Shterenlikht wrote: when portmaster have gone away? What? WHAT? portmaster going away??? I hope not Anton The ports tree continues to evolve. Major new features are planned and in the process of being implemen

Re: The future of portmaster [and of ports-mgmt/synth]

I would just like a clarification here. For the record, synth is broken on FreeBSD-11 and above with amd64. Is that correct? -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, se

Re: The future of portmaster [and of ports-mgmt/synth]

On Wed, 2017-05-31 at 12:47 +, Gerard Seibert wrote: > I would just like a clarification here. For the record, synth is > broken > on FreeBSD-11 and above with amd64. Is that correct? My understanding was that the breakage is in gcc6-aux on 12-CURRENT with 64 bit inodes. I may be wrong... --

Re: texinfo build failure

On Tuesday 30 May 2017 16:09:56 Michael Butler wrote: > Anyone care to address this? There is some really cryptic issue. texinfo port build completed successfully after both devel/libuv and lang/perl5.24 rebuild. > > On 5/26/17 2:41 PM, Michael Butler wrote: > > Is anyone else seeing this fail

Re: The future of portmaster [and of ports-mgmt/synth]

Mark Linimon wrote: * some extensive changes to the ports framework are coming; Is there a URL (other than svnweb) where we can see a project plan for these changes? As in the recent past (i.e., since 8-REL) the FreeBSD end-user community has reason to be worried that: * popular tools that w

Re: Xorg error 'alphasort'

Hi. I was using 12-current r318249 and did 'pkg upgrade', and could not start xorg with alphasort error. After updating r319315, xorg works again. -- Masachika ISHIZUKA ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/l

Re: The future of portmaster [and of ports-mgmt/synth]

On Wed, 31 May 2017 09:11:23 -0700, Roger Marquis stated: >Mark Linimon wrote: >> * some extensive changes to the ports framework are coming; > >Is there a URL (other than svnweb) where we can see a project plan for >these changes? As in the recent past (i.e., since 8-REL) the FreeBSD >end-user

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

Re: The future of portmaster [and of ports-mgmt/synth]

On 2017/05/31 17:11, Roger Marquis wrote: > Mark Linimon wrote: >> * some extensive changes to the ports framework are coming; > > Is there a URL (other than svnweb) where we can see a project plan for > these changes? As in the recent past (i.e., since 8-REL) the FreeBSD > end-user community has

Re: The future of portmaster [and of ports-mgmt/synth]

On 2017-05-31 02:10, Kevin Oberman wrote: On Tue, May 30, 2017 at 2:53 PM, Mark Linimon > wrote: On Tue, May 30, 2017 at 11:46:46PM +0200, Per olof Ljungmark wrote: > Hello, I have not followed this thread before but just wanted to say > that I use port

Re: The future of portmaster [and of ports-mgmt/synth]

On Wed, May 31, 2017 at 07:28:38PM +0200, Per olof Ljungmark wrote: > > On 2017-05-31 02:10, Kevin Oberman wrote: > > On Tue, May 30, 2017 at 2:53 PM, Mark Linimon > > wrote: > > > > On Tue, May 30, 2017 at 11:46:46PM +0200, Per olof Ljungmark wrote: > > > He

Re: The future of portmaster [and of ports-mgmt/synth]

> On 31 May, 2017, at 11:28, Per olof Ljungmark wrote: > > > > On 2017-05-31 02:10, Kevin Oberman wrote: >> On Tue, May 30, 2017 at 2:53 PM, Mark Linimon > > wrote: >>On Tue, May 30, 2017 at 11:46:46PM +0200, Per olof Ljungmark wrote: >>> Hello, I have not f

Re: freebsd-ports Digest, Vol 732, Issue 4

> Since portmaster is still popult and since the only solutions that > looks to be available in the near term are pouderiere or raw make, > neither terribly viable for many, I will look into updating > portmaster to deal with 'flavors'. Thank you so very much for attempting this. I too am depend

Firefox (and other Mozilla products) after ino64

Hi, Due to the recent ino64 update in 12.0-CURRENT, there have been some reports by Firefox port users about crashes. While I personally have not experienced these crashes, as I immediately rebuilt all my ports from scratch after the ino64 update, I think can explain why the following combination

Re: The future of portmaster [and of ports-mgmt/synth]

If you can give me access to a development system, I'll help. (I only have a production server for the domains I host for a few not-for-profit organizations, and my home server is currently out of service with a bad power supply.) Jim Trigg On May 30, 2017 8:10:17 PM EDT, Kevin Oberman wrote

Re: The future of portmaster [and of ports-mgmt/synth]

On Wed, 31 May 2017, Per olof Ljungmark wrote: > Let me just say that I would really, really appriciate if we could keep > such a simple tool. Why does it suit us? Because we have a limited > number of systems, [...] And the sytems we do have can be somewhat limited; I mean, Ada, FFS? -- Dave

Hosting distfiles on HTTPS w/Let's Encrypt - how?

Hello, I have posted my port's local distfiles to a machine that is serving them with SSL behind the Let's Encrypt certificate (https://distfile.net). This is SSL-only. However, poudriere fails on certificate check when trying to fetch it: === ===>

Re: Firefox (and other Mozilla products) after ino64

On Wed, 31 May 2017 23:27:16 +0200, Dimitry Andric wrote: > Hi, > > Due to the recent ino64 update in 12.0-CURRENT, there have been some > reports by Firefox port users about crashes. While I personally have > not experienced these crashes, as I immediately rebuilt all my ports > from scratch

Re: The future of portmaster

> On Wed, 2017-05-31 at 12:47 +, Gerard Seibert wrote: > > I would just like a clarification here. For the record, synth is > > broken > > on FreeBSD-11 and above with amd64. Is that correct? > My understanding was that the breakage is in gcc6-aux on 12-CURRENT > with 64 bit inodes. > I may b

Re: Hosting distfiles on HTTPS w/Let's Encrypt - how?

can you dowload the file distfiles/INIT.2014-12-24.tgz using browser such as chrome？ be sure to use full chain cert file，I rember I had similar problem and use full chain cert fixed. 2017年6月1日 8:01 AM，"Marcin Cieslak" 写道： Hello, I

Problems using OpenMP

Hello guys; FWIW, I tried using OpenMP in a port (hypre) and I thought the option would be something as simple as this: OPENMP_CONFIGURE_WITH=openmp OPENMP_CONFIGURE_USES=compiler:openmp Unfortunately that is not enough: ... In file included from ./_hypre_utilities.h:16: ./HYPRE_uti

Re: Problems using OpenMP

On Wed, May 31, 2017 at 08:56:18PM -0500, Pedro Giffuni wrote: > > FWIW, I tried using OpenMP in a port (hypre) and I thought the option > would be something as simple as this: > > OPENMP_CONFIGURE_WITH=openmp > OPENMP_CONFIGURE_USES=compiler:openmp > > Unfortunately that is not enough:

Sylpheed bug?

Rececently installed Sylpheed Port on FreeBSD-11.0, everything works unless I press 'Get' or 'Get All' buttons at the top, if i do that it instally kills everything running from /usr/local and restarts xorg. Seconds flat. Maybe it's good for a bug report? I haven't done much on this machine and

Re: Problems using OpenMP

On 05/31/17 21:45, Steve Kargl wrote: On Wed, May 31, 2017 at 08:56:18PM -0500, Pedro Giffuni wrote: FWIW, I tried using OpenMP in a port (hypre) and I thought the option would be something as simple as this: OPENMP_CONFIGURE_WITH=openmp OPENMP_CONFIGURE_USES=compiler:openmp Unfortun