On 8/13/14 4:00 AM, Alexis La Goutte wrote:
> On Sun, Aug 10, 2014 at 2:07 PM, Evan Huus <[email protected]> wrote:
>>> On Aug 10, 2014, at 7:06, Bálint Réczey <[email protected]> wrote:
>>> Hi Evan,
>>> 2014-08-10 4:41 GMT+02:00 Evan Huus <[email protected]>:
>>>> I took a quick look at the recent check-abi buildbot failure, which
>>>> appears to be manpage related:
>>>> wireshark.pod around line 3525: Non-ASCII character seen before
>>>> =encoding in 'KovE<aacute>ř'. Assuming UTF-8
>>>> POD document had syntax errors at /usr/bin/pod2man line 71.
>>>> Which is curious, because wireshark.pod.template *does* have an
>>>> =encoding line...
The =encoding line is between a "=begin man / =end man" pair and so only
applies to man page generation. We might want to remove that restriction
since our input is always guaranteed to be UTF-8.
>>>> Also of note is that we appear to be passing --title="The Wireshark
>>>> Network Analyzer 1.8.2" to the generator on trunk, which is just
>>>> Anybody know what's going on?
>>> This is the lts-1.8.2 branch but the builds are shown on trunk's buildbot.
>>> I updated the LTS branches before releasing the update to Debian in a
>>> hope that the patched could be fuzz-tested by the buildbots, but I
>>> think LTS branches are not fuzz-tested.
>>> I have fixed a few build problems along the security fixes, but did
>>> not have time to fix this one, too.
>> Ah ok. I wonder why lts branch builds are showing up on the master Buildbot...?
I added a match for "lts-*" at Sharkfest so that Balint's commits would
be tested. We probably need a separate (and perhaps Linux-only) "lts"
> I think, need to see to modify buildbot trunk to follow git repertory
> (and no Gerrit with all merge/ref-update/patch-set...)
It's on my to-do list.