On Wed, Feb 10, 2016 at 11:16:10AM +0100, John Marino wrote:
> On 2/10/2016 11:09 AM, Lars Engels wrote:
> > On Wed, Feb 10, 2016 at 10:40:44AM +0100, John Marino wrote:
> >> On 2/10/2016 10:37 AM, Lars Engels wrote:
> >>> On Tue, Feb 09, 2016 at 06:28:11PM +0100, John Marino wrote:
> >>>> On 2/9/2016 4:15 PM, Lars Engels wrote:
> >>>>>
> >>>>> root@fbsd01:~ # synth status
> >>>>> Querying system about current package installations.
> >>>>> Stand by, comparing installed packages against the ports tree.
> >>>>> Stand by, building pkg(8) first ... Failed!!  (Synth must exit)
> >>>>> Unfortunately, the system upgrade failed.
> >>>>
> >>>> Do you have a file called /var/log/synth/ports-mgmt___pkg.log ?  If so,
> >>>> does it provide clues?
> >>>
> >>> So it's missing the proxy variables.
> >>>
> >>
> >> okay, so internally it's only installing resolv.conf in the builder
> >> environment.  Where are these proxy variables defined?  When I
> >> understand what's needed, I can give you a patch to try (if required)
> > 
> > resolv.conf doesn't work in that proxy scenario. DNS requests are
> > handled by the proxy server.
> > 
> > I set
> > HTTP_PROXY=http://proxyserver:8888; export HTTP_PROXY
> > http_proxy=http://proxyserver:8888; export http_proxy
> > ftp_proxy=http://proxyserver:8888; export FTP_PROXY
> > ftp_proxy=http://proxyserver:8888; export ftp_proxy
> > 
> > NO_PROXY="localhost,127.0.0.1,..."; export NO_PROXY
> > 
> > in /etc/profile and
> > :setenv=MAIL=/var/mail/$,BLOCKSIZE=K,HTTP_PROXY=http\c//proxyserver\c8888,FTP_PROXY=http\c//proxyserver\c8888,NO_PROXY=localhost\054127.0.0.1\054...:\
> > 
> > in /etc/login.conf
> > 
> 
> wow, okay, so basically these 4 variables would have to be present in
> the builder environment then?
> 
> I'll have to think about this.  I'll probably have to add a feature like
> a file like "/usr/local/etc/synth/<profile>-environment which will
> append user environment variables to the stock ones.
> 
> That's not exactly a 1-line change, but would that solve this issue?

That should work, yes.

Attachment: pgpieLkC5c1Qe.pgp
Description: PGP signature

Reply via email to