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: Conditional patch

Le 27/08/2017 à 19:33, Kurt Jaeger a écrit : > Hi! > >> Is it possible to apply a patch in files/ conditionally? I can't find >> this information in the handbook. > There's EXTRA_PATCHES, search in devel/*/Makefile for examples > on how to use them. > There is away to fast reference to

Re: Conditional patch

El 28 ago. 2017 11:09, "Mathieu Arnold" escribió: Le 27/08/2017 à 19:33, Kurt Jaeger a écrit : > Hi! > >> Is it possible to apply a patch in files/ conditionally? I can't find >> this information in the handbook. > There's EXTRA_PATCHES, search in devel/*/Makefile for examples

Re: GVFS build fail

I don't know whose idea it was to include GVFS, but it's glued onto everything and the constant warnings about how this or that part doesn't work are getting right up my nostril. Perhaps whoever decided to include it is a hobbyist who, if asked, would say "well yeah, it doesn't work, but I

Re: gtkmm30 package install failed: size mismatch

[Default] On Mon, 28 Aug 2017 03:08:05 +0200, Jan Beich wrote: >Try running: pkg update -f Are you thinking of something else, perhaps? The man page doesn't show an -f switch, and pkg thinks the repositories were already current, which is why (I suppose) it tried a remote

Re: gtkmm30 package install failed: size mismatch

On 08/28/17 16:58, scratch65...@att.net wrote: > [Default] On Mon, 28 Aug 2017 03:08:05 +0200, Jan Beich > wrote: > >> Try running: pkg update -f > > Are you thinking of something else, perhaps? The man page > doesn't show an -f switch, and pkg thinks the repositories

Re: gtkmm30 package install failed: size mismatch

Thanks, Manish. Very non-standard syntax, that. So evidently when pkg claims that the repositories are current, as it did, it may be, in effect, lying. Which suggests that *it* should be doing the forced update as step 3 in its attempt to get good bits. [sigh] [Default] On Mon, 28 Aug

PR commit request

Dear committers, Would someone please commit following PR with maintainer timeout? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221186 With best regards. --- Yasuhiro KIMURA ___ freebsd-ports@freebsd.org mailing list

PR looking for committer

Hi, Can a committer have a look at this? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221835 Thanks ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: FreeBSD Port: RetroArch-1.3.6_7

On 07/11/17 01:02, bluesky wrote: Hello. The Retroarch port seems a bit out of date. Retroarch is on version 1.6.0 now. Thank you. Your mistake is that you CCed ports@. As a result, it landed in the folder for ports@, and not in the personal mailbox, so I didn't see it. I will update

Re: PR commit request

Hi! > Would someone please commit following PR with maintainer timeout? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221186 Done. It helps if you note the port involved in the subject 8-} -- p...@opsec.eu+49 171 3101372 3 years to go !