Re: Building 'apcupsd' package with 'no_x11' flavor fails in 6.9-stable

2021-05-02 Thread Matthias Pressfreund
That was it. I removed the masking entry, then it built. Thank you!


On 2021-05-02 19:00, Stuart Henderson wrote:
> 
> For Solene's example, check that the 'keepenv' lines really are taking
> effect and aren't masked by another entry in the file.
> 



Re: Building 'apcupsd' package with 'no_x11' flavor fails in 6.9-stable

2021-05-02 Thread Stuart Henderson
On 2021/05/02 18:50, Matthias Pressfreund wrote:
> I was following Solene Rapenne's instructions on 
> https://dataswamp.org/~solene/2020-01-11-privsep.html
> 
> If it was the setup, I'd also expect building the port without the flavor to 
> fail.

No, because building the port without a flavour doesn't involved
passing a flavour through sudo/doas (which defaults to _not_ passing
arbitrary environment variables) to another process.

For Solene's example, check that the 'keepenv' lines really are taking
effect and aren't masked by another entry in the file.

(Also if you're using the 'permit keepenv nopass .. as root' line,
be aware that you are turning your normal user account into a
root-equivalent account).



Re: Building 'apcupsd' package with 'no_x11' flavor fails in 6.9-stable

2021-05-02 Thread Matthias Pressfreund
I was following Solene Rapenne's instructions on 
https://dataswamp.org/~solene/2020-01-11-privsep.html

If it was the setup, I'd also expect building the port without the flavor to 
fail.


On 2021-05-02 18:38, Stuart Henderson wrote:
> When this happens it's usually connected with use of sudo or doas with an 
> incomplete setup (required environment variables not getting passed through), 
> could that be the problem here?
> 



Re: Building 'apcupsd' package with 'no_x11' flavor fails in 6.9-stable

2021-05-02 Thread Stuart Henderson
When this happens it's usually connected with use of sudo or doas with an 
incomplete setup (required environment variables not getting passed 
through), could that be the problem here?


--
 Sent from a phone, apologies for poor formatting.
On 2 May 2021 15:34:30 Matthias Pressfreund  wrote:


I was trying to build the sysutils/apcupsd package with the 'no_x11' flavor.
Looks like it's trying to cd into /usr/ports/pobj/apcupsd-3.14.14 while  its
real name is apcupsd-3.14.14-no_x11 because of the flavor.
Building without flavor succeeds.

$ FLAVOR='no_x11' make package
===>  Checking files for apcupsd-3.14.14
`/usr/ports/distfiles/apcupsd-3.14.14.tar.gz' is up to date.

(SHA256) apcupsd-3.14.14.tar.gz: OK

===> apcupsd-3.14.14p6 depends on: gmake-* -> gmake-4.3
===> apcupsd-3.14.14p6 depends on: libusb-compat-* -> libusb-compat-0.1.5p0
===> apcupsd-3.14.14p6 depends on: gd-* -> gd-2.3.2
===>  Verifying specs:  c++ c++abi pthread c m pthread usb c++ c++abi 
pthread c m pthread gd

===>  found c++.7.0 c++abi.5.0 pthread.26.1 c.96.0 m.10.1 usb.10.0 gd.22.2
===>  Extracting for apcupsd-3.14.14
/bin/sh: cd: /usr/ports/pobj/apcupsd-3.14.14 - No such file or directory
*** Error 1 in /usr/ports/sysutils/apcupsd 
(/usr/ports/infrastructure/mk/bsd.port.mk:2713 'do-extract': 
@PATH=/usr/ports/pobj/apcupsd-3.14.1...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2686 
'/usr/ports/pobj/apcupsd-3.14.14-no_x11/.extract_done': @cd 
/usr/ports/sysut...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2134 
'/usr/ports/packages/amd64/all/apcupsd-3.14.14p6.tgz': @cd 
/usr/ports/sysuti...)
*** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2623 
'_internal-package': @case X${_DEPENDS_CACHE} in  X) _DEPENDS_CACHE=$(doas 
-...)
*** Error 2 in /usr/ports/sysutils/apcupsd 
(/usr/ports/infrastructure/mk/bsd.port.mk:2602 'package': 
@lock=apcupsd-3.14.14;  export _LOCKS_H...)