Homebrew-core: ldns: build --with-python fails at install due to permissions issues

[ts826848]

Gist

Build completes successfully. The relevant portion is at the top of 03.make, copied here for convenience:

install

./install-sh  -m 755 -d /usr/local/Cellar/ldns/1.6.17_1/include/ldns
./install-sh  -m 755 -d /usr/local/Cellar/ldns/1.6.17_1/lib
./install-sh  -d /usr/local/Cellar/ldns/1.6.17_1/bin
./install-sh  -d /usr/local/Cellar/ldns/1.6.17_1/share/man/man1
./install-sh  -m 755 -d /usr/local/Cellar/python/2.7.12/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ldns
./install-sh  -c -m 644 ./contrib/ldnsx/ldnsx.py /usr/local/Cellar/python/2.7.12/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ldnsx.py
./install-sh  -m 755 -d /usr/local/Cellar/ldns/1.6.17_1/bin
cp: /usr/local/Cellar/python/2.7.12/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_inst.73948_: Operation not permitted
make: *** [install-pyldnsx] Error 1
make: *** Waiting for unfinished jobs....
for i in buffer.h dane.h dname.h dnssec.h dnssec_sign.h dnssec_verify.h dnssec_zone.h duration.h error.h higher.h host2str.h host2wire.h keys.h ldns.h packet.h parse.h radix.h rbtree.h rdata.h resolver.h rr_functions.h rr.h sha1.h sha2.h str2host.h tsig.h update.h wire2host.h zone.h ; do \
        ./install-sh  -c -m 644 ./ldns/$i /usr/local/Cellar/ldns/1.6.17_1/include/ldns/; done
./install-sh  -m 755 -d /usr/local/Cellar/ldns/1.6.17_1/share/man
./install-sh  -c -m 755 packaging/ldns-config /usr/local/Cellar/ldns/1.6.17_1/bin
./libtool --tag=CC --quiet --mode=install cp libldns.la /usr/local/Cellar/ldns/1.6.17_1/lib
mkdir: /usr/local/Cellar/python/2.7.12/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ldns: Operation not permitted
./install-sh  -m 755 -d /usr/local/Cellar/ldns/1.6.17_1/share/man/man1
make: *** [install-pyldns] Error 1
./install-sh  -c -m 444 ./packaging/ldns-config.1 /usr/local/Cellar/ldns/1.6.17_1/share/man/man1/
./libtool --tag=CC --quiet --mode=install cp drill/drill /usr/local/Cellar/ldns/1.6.17_1/bin
./libtool --tag=CC --quiet --mode=finish /usr/local/Cellar/ldns/1.6.17_1/lib
./install-sh  -m 644 drill/drill.1 /usr/local/Cellar/ldns/1.6.17_1/share/man/man1/drill.1
for i in common.h util.h net.h; do \
        ./install-sh  -c -m 644 ldns/$i /usr/local/Cellar/ldns/1.6.17_1/include/ldns/; done

Something to do with writing in the .framework? Not entirely sure yet what is going on

[dunn]

From your brew doctor:

With a non-standard origin, Homebrew won't pull updates from
the main repository. The current git origin is:
  [email protected]:aw1621107/brew.git

Unless you have compelling reasons, consider setting the
origin remote to point at the main repository, located at:
https://github.com/Homebrew/brew.git

Is that a mirror? Is it up to date?

[ts826848]

It's my fork, which I use to break formulae to make the maintainers' lives harder :P

I think it was up to date? I'll have to check tomorrow morning. Thought I updated everything before starting that series of installs...

On Oct 10, 2016, at 9:07 PM, Alex Dunn [email protected] wrote:

From your brew doctor:

With a non-standard origin, Homebrew won't pull updates from
the main repository. The current git origin is:
[email protected]:aw1621107/brew.git

Unless you have compelling reasons, consider setting the
origin remote to point at the main repository, located at:
https://github.com/Homebrew/brew.git
Is that a mirror? Is it up to date?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[dunn]

Gotcha. Anyway looks like a standard sandbox violation, if it's trying to write to another Cellar:

cp: /usr/local/Cellar/python/2.7.12/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_inst.73948_: Operation not permitted

[dunn]

But looks like those above it succeed; @tdsmith do we make an exception for site-packages?

[tdsmith]

Nope

[ts826848]

@dunn For what it's worth, just tried again with freshly updated brew and taps, and same error. I see @tdsmith got a fix, already, though