Created attachment 147985 [details] shar file for newtonsoft-json-6.0.5 Popular high-performance JSON framework for .NET * Flexible JSON serializer for converting between .NET objects and JSON * LINQ to JSON for manually reading and writing JSON * High performance, faster than .NET's built-in JSON serializers * Write indented, easy to read JSON * Convert JSON to and from XML * Supports .NET 2, .NET 3.5, .NET 4, .NET 4.5, Silverlight, Windows Phone and Windows 8 Store The JSON serializer in Json.NET is a good choice when the JSON you are reading or writing maps closely to a .NET class. WWW: http://james.newtonking.com/json Poudriere logs: http://pdr.s.ubze.ro/bulk/latest-per-pkg/newtonsoft-json/6.0.5/
I love the set of 8 poudriere logs, but I notice that they don't have the -t option enabled to invoke the stage-qa and make check-plist checks. Is there any way to ensure that option gets checked in the future?
I am not aware of that option for "testport". But I believe it is available for bulk package building in "bulk". It seems like poudriere is saving bulk build logs and showing the testport output to stdout. So there are two possibilities: 1. I change my script to output the the stdout to a different location using testport. 2. I change my script to use bulk instead. What's your opinion? (In reply to John Marino from comment #1) > I love the set of 8 poudriere logs, but I notice that they don't have the -t > option enabled to invoke the stage-qa and make check-plist checks. Is there > any way to ensure that option gets checked in the future?
poudriere testport does the tests unconditionally. I assumed these were bulk builds because I don't see the tests being run. Is the poudriere up to date? In any case, "poudriere bulk -t" should be fine if you want to switch to it.
If you use testport the stage-qa and other checks are thrown to stdout while keeping bulk log in the logs directory. But if I use bulk with -t it is available in the log. So I am shifting towards bulk -t. From my next PR those will be available. (In reply to John Marino from comment #3) > poudriere testport does the tests unconditionally. I assumed these were > bulk builds because I don't see the tests being run. > > Is the poudriere up to date? > > In any case, "poudriere bulk -t" should be fine if you want to switch to it.
it's strange because I ran into one of your log sets that contained stage-qa checks (and I recalled that I'd see them before as well). i don't know what changed, but it was ok before.
portmaster updated poudriere a couple of times in the last couple of weeks. Might be there are some issues then. (In reply to John Marino from comment #5) > it's strange because I ran into one of your log sets that contained stage-qa > checks (and I recalled that I'd see them before as well). > > i don't know what changed, but it was ok before.
A commit references this bug: Author: marino Date: Mon Oct 6 23:10:30 UTC 2014 New revision: 370259 URL: https://svnweb.freebsd.org/changeset/ports/370259 Log: Add new port devel/newtonsoft-json PR: 194147 Submitted by: Muhammad Rahman Popular high-performance JSON framework for .NET * Flexible JSON serializer for converting between .NET objects and JSON * LINQ to JSON for manually reading and writing JSON * High performance, faster than .NET's built-in JSON serializers * Write indented, easy to read JSON * Convert JSON to and from XML * Supports .NET 2, .NET 3.5, .NET 4, .NET 4.5, Silverlight, Windows Phone and Windows 8 Store The JSON serializer in Json.NET is a good choice when the JSON you are reading or writing maps closely to a .NET class. Changes: head/devel/Makefile head/devel/newtonsoft-json/ head/devel/newtonsoft-json/Makefile head/devel/newtonsoft-json/distinfo head/devel/newtonsoft-json/files/ head/devel/newtonsoft-json/files/Newtonsoft.Json.pc.in head/devel/newtonsoft-json/pkg-descr
Thanks!