https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194013
Steve Wills changed:
What|Removed |Added
Status|Needs Triage|Issue Resolved
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194012
Steve Wills changed:
What|Removed |Added
Status|Needs Triage|Issue Resolved
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193833
Steve Wills changed:
What|Removed |Added
Status|Needs Triage|Issue Resolved
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193833
--- Comment #4 from commit-h...@freebsd.org ---
A commit references this bug:
Author: swills
Date: Mon Sep 29 21:05:05 UTC 2014
New revision: 369555
URL: https://svnweb.freebsd.org/changeset/ports/369555
Log:
print/rubygem-prawn: update
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194012
--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:
Author: swills
Date: Mon Sep 29 21:05:05 UTC 2014
New revision: 369555
URL: https://svnweb.freebsd.org/changeset/ports/369555
Log:
print/rubygem-prawn: update
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194013
--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:
Author: swills
Date: Mon Sep 29 21:05:05 UTC 2014
New revision: 369555
URL: https://svnweb.freebsd.org/changeset/ports/369555
Log:
print/rubygem-prawn: update
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194011
Steve Wills changed:
What|Removed |Added
Status|Needs Triage|Issue Resolved
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194013
--- Comment #2 from kved...@kvedulv.de ---
Created attachment 147802
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147802&action=edit
buildlog
--
You are receiving this mail because:
You are the assignee for the bug.
__
kved...@kvedulv.de has asked r...@freebsd.org for maintainer-feedback:
Bug 194013: [patch] update print/rubygem-prawn to 1.3.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194013
--- Additional Comments from kved...@kvedulv.de
update 1.2.1 -> 1.3.0
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194013
Bug ID: 194013
Summary: [patch] update print/rubygem-prawn to 1.3.0
Product: Ports Tree
Version: Latest
Hardware: Any
OS: Any
Status: Needs Triage
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194012
--- Comment #2 from kved...@kvedulv.de ---
Created attachment 147800
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147800&action=edit
buildlog
--
You are receiving this mail because:
You are the assignee for the bug.
__
kved...@kvedulv.de has asked r...@freebsd.org for maintainer-feedback:
Bug 194012: [patch] update print/rubygem-ttfunk to 1.4.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194012
--- Additional Comments from kved...@kvedulv.de
update 1.2.2 -> 1.4.0
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194012
Bug ID: 194012
Summary: [patch] update print/rubygem-ttfunk to 1.4.0
Product: Ports Tree
Version: Latest
Hardware: Any
OS: Any
Status: Needs Triage
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194011
--- Comment #2 from kved...@kvedulv.de ---
Created attachment 147797
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147797&action=edit
update to 1.0.4
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194011
Bug ID: 194011
Summary: [patch] update devel/rubygem-safe_yaml to 1.0.4
Product: Ports Tree
Version: Latest
Hardware: Any
OS: Any
Status: Needs Triage
kved...@kvedulv.de has asked r...@freebsd.org for maintainer-feedback:
Bug 194011: [patch] update devel/rubygem-safe_yaml to 1.0.4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194011
--- Additional Comments from kved...@kvedulv.de
update devel/rubygem-safe_yaml 1.0.3 -> 1.0.4
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194011
--- Comment #3 from kved...@kvedulv.de ---
Created attachment 147798
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147798&action=edit
buildlog
--
You are receiving this mail because:
You are the assignee for the bug.
__
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
18 matches
Mail list logo