You are receiving this mail as a port that you maintain
is failing to build on the FreeBSD package build server.
Please investigate the failure and submit a PR to fix
build.
Maintainer: r...@freebsd.org
Last committer: swi...@freebsd.org
Ident: $FreeBSD: head/devel/rubygem-gobject-int
You are receiving this mail as a port that you maintain
is failing to build on the FreeBSD package build server.
Please investigate the failure and submit a PR to fix
build.
Maintainer: r...@freebsd.org
Last committer: swi...@freebsd.org
Ident: $FreeBSD: head/devel/rubygem-gobject-int
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209359
Steve Wills changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209359
--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:
Author: swills
Date: Sun Sep 4 00:51:23 UTC 2016
New revision: 421301
URL: https://svnweb.freebsd.org/changeset/ports/421301
Log:
lang/ruby22: fix plist with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196326
John Marino changed:
What|Removed |Added
CC||swi...@freebsd.org
--- Comment #15 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196326
--- Comment #14 from John Marino ---
yes, we all know for a long time that portmgr makes itself exempt for the same
rules it imposes on others, and the only way to get it changed is through
portmgr so there's zero checks and balances here.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196326
--- Comment #13 from Mathieu Arnold ---
Good to know your opinion on the matter.
Now, the point is, you do not touch the ports framework, ever, without
portmgr's approval.
--
You are receiving this mail because:
You are the assignee for
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
