Nut upsdev - Jan 2013 - [nut-commits] buildbot failure in Network UPS Tools on FreeBSD-x64

On Mon, Jan 14, 2013 at 4:36 AM, Arnaud Quette <aquette.dev at gmail.com>
wrote:
> Hey Charles,
>
> I hope you're doing fine...
>
> There seems to be an issue on your BSD: permission denied on Asciidoc
> generation.
It looks like this is due to a new version of AsciiDoc (8.6.8 vs
8.6.6). I'll take a look again later, but I doubt it's related to the
most recent SVN commit.
> ---------- Forwarded message ----------
> Date: 2013/1/14
> Subject: [nut-commits] buildbot failure in Network UPS Tools on FreeBSD-x64
> To: emilienkia-guest at alioth.debian.org, fbohe-guest at alioth.debian.org
> Cc: nut-commits at lists.alioth.debian.org
>
>
> The Buildbot has detected a new failure on builder FreeBSD-x64 while
> building Network UPS Tools.
> Full details are available at:
>
>
http://buildbot.networkupstools.org/public/nut/builders/FreeBSD-x64/builds/47
>
> Buildbot URL: http://buildbot.networkupstools.org/public/nut/
>
> Buildslave for this Build: cabrio
>
> Build Reason: scheduler
> Build Source Stamp: [branch trunk] 3838
> Blamelist: emilienkia-guest,fbohe-guest
>
> BUILD FAILED: failed compile
>
> sincerely,
>  -The Buildbot
--
- Charles Lepple

On Jan 14, 2013, at 8:47 AM, Charles Lepple wrote:
> On Mon, Jan 14, 2013 at 4:36 AM, Arnaud Quette <aquette.dev at
gmail.com> wrote:
>> Hey Charles,
>> 
>> I hope you're doing fine...
>> 
>> There seems to be an issue on your BSD: permission denied on Asciidoc
>> generation.
> 
> It looks like this is due to a new version of AsciiDoc (8.6.8 vs
> 8.6.6). I'll take a look again later, but I doubt it's related to
the
> most recent SVN commit.

I'm not sure about the best way to fix this long-term, short of patching
asciidoc. Basically, asciidoc is overwriting a common CSS file, and on BSD, if
you don't have write permission to that file, you get a permission error.
(Come to think of it, I don't know why this isn't an issue on other
Unix-like platforms.) I adjusted permissions on the source file, but it will
probably happen again after the next upgrade.

-- 
Charles Lepple
clepple at gmail