Alright, I'll look into it.
-Bill
On Aug 26, 2013, at 9:37 AM, Frank Schima wrote:
> FYI, I committed a change just now on a port with a lint failure:
>
> $ port lint
> ---> Verifying Portfile for sheepshaver
> Warning: Variant no_x11 does not have a description
> Warning: no license set
>
FYI, I committed a change just now on a port with a lint failure:
$ port lint
---> Verifying Portfile for sheepshaver
Warning: Variant no_x11 does not have a description
Warning: no license set
---> 0 errors and 2 warnings found.
I did not receive a lint email. I got the 3 buildbot slave failur
The job was running but never finding any problems, as far as I can tell. I
have tweaked some permissions and added some debugging. Let me know the next
time you expected a lint email.
-Bill
On Aug 26, 2013, at 5:56 AM, Clemens Lang wrote:
> On Mon, Aug 26, 2013 at 10:48:17PM +1000, Joshua
On Mon, Aug 26, 2013 at 10:48:17PM +1000, Joshua Root wrote:
> And of course you do get email if the build fails or port lint doesn't
> pass, though that doesn't cover all the ways a port could be broken.
Are the lint mails actually working? I have never received a lint
warning mail, and I'm prett
On 2013-8-26 22:40 , Peter Danecek wrote:
>
> Hi all,
>
> I am wondering if there is a way to be notified when a port I am maintaining
> is modified?
>
> The point is that it happened that these modifications would break the port.
> I would like to be aware of these ASAP, so that I can give it
Hi all,
I am wondering if there is a way to be notified when a port I am maintaining is
modified?
The point is that it happened that these modifications would break the port. I
would like to be aware of these ASAP, so that I can give it a quick look and
eventually do some testing.
Thanks!
~p
