[package - 93amd64-default][devel/rubygem-rugged] Failed for rubygem-rugged-0.23.3 in stage

2016-03-19 Thread pkg-fallout
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: sunp...@freebsd.org Ident: $FreeBSD: head/devel/rubygem-rugged/Mak

[package - 93i386-default][devel/rubygem-rugged] Failed for rubygem-rugged-0.23.3 in stage

2016-03-19 Thread pkg-fallout
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: sunp...@freebsd.org Ident: $FreeBSD: head/devel/rubygem-rugged/Mak

[Bug 207795] devel/rubygem-rugged: Update to 0.24.0

2016-03-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207795 --- Comment #2 from Torsten Zühlsdorff --- Yes, to fix the problem this patch should be committed. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@free

[exp - 103i386-default-build-as-user][devel/rubygem-rugged] Failed for rubygem-rugged-0.23.3 in stage

2016-03-19 Thread pkg-fallout
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: sunp...@freebsd.org Ident: $FreeBSD: head/devel/rubygem-rugged/Mak

[Bug 207795] devel/rubygem-rugged: Update to 0.24.0

2016-03-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207795 Vikash Badal changed: What|Removed |Added CC||vika...@where-ever.za.net --- Comme

[package - head-amd64-default][devel/rubygem-rugged] Failed for rubygem-rugged-0.23.3 in stage

2016-03-19 Thread pkg-fallout
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: sunp...@freebsd.org Ident: $FreeBSD: head/devel/rubygem-rugged/Mak

[exp - 103i386-default-build-as-user][devel/rubygem-rugged] Failed for rubygem-rugged-0.23.3 in stage

2016-03-19 Thread pkg-fallout
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: sunp...@freebsd.org Ident: $FreeBSD: head/devel/rubygem-rugged/Mak

[package - head-i386-default][devel/rubygem-rugged] Failed for rubygem-rugged-0.23.3 in stage

2016-03-19 Thread pkg-fallout
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: sunp...@freebsd.org Ident: $FreeBSD: head/devel/rubygem-rugged/Mak

FreeBSD ports you maintain which are out of date

2016-03-19 Thread portscout
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

FreeBSD ports you maintain which are out of date

2016-03-19 Thread portscout
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