Arch Linux

denisal

Member

Registered: 2016-10-24

Posts: 9

makepkg gives WARNINGs after moving my AUR build directory

Hey there,
I recently installed anaconda from the AUR. I cloned the repo to ~/pacman_AUR_builds and ran makepkg -sri. A few days later I moved my aur build directory

 mv ~/pacman_AUR_builds ~/builds/aur

Well, now I wanted to install htop-vim-solarized-git from the AUR. And I recognized the following warning when building the package:

==> Validating source files with sha384sums...
    htop ... Skipped
    solarized-colors.patch ... WARNING: can't open config file: /home/denis/pacman_AUR_builds/anaconda/pkg/anaconda/opt/anaconda/ssl/openssl.cnf
Passed
    vim-keybindings-common.patch ... WARNING: can't open config file: /home/denis/pacman_AUR_builds/anaconda/pkg/anaconda/opt/anaconda/ssl/openssl.cnf
Passed
    vim-keybindings-d-for-kill.patch ... WARNING: can't open config file: /home/denis/pacman_AUR_builds/anaconda/pkg/anaconda/opt/anaconda/ssl/openssl.cnf
Passed
    vim-keybindings-x-for-kill.patch ... WARNING: can't open config file: /home/denis/pacman_AUR_builds/anaconda/pkg/anaconda/opt/anaconda/ssl/openssl.cnf
Passed

[...]

==> Creating package "htop-vim-solarized-git"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
WARNING: can't open config file: /home/denis/pacman_AUR_builds/anaconda/pkg/anaconda/opt/anaconda/ssl/openssl.cnf

Why does makepkg look up a config file in the build directory of anaconda (and not the actual installation directory /opt/anaconda...)?

Using ack, I found out that the build directory is stored in the .BUILDINFO file of the package. I would have thought the build directory does not matter once the package is installed (e.g. yaourt uses /tmp to build packages I think). Or does this become relevant at some point, e.g. when doing an upgrade? What would be the right way of moving my AUR build direcory?

And the fact that anaconda has anything to do with building another package looks like anaconda python is used for building packages instead of the system python (installed with pacman). Is that right? If so, wouldn't it be better to have system python build the packages (as they are depending on the system python version and not on whatever version anaconda uses). Any advise on how to handle this?

Last edited by denisal (2016-11-07 16:24:46)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,694

Re: makepkg gives WARNINGs after moving my AUR build directory

Is $OPENSSL_CONF set?

denisal

Member

Registered: 2016-10-24

Posts: 9

Re: makepkg gives WARNINGs after moving my AUR build directory

Is $OPENSSL_CONF set?

Nope, not set.

denisal

Member

Registered: 2016-10-24

Posts: 9

Re: makepkg gives WARNINGs after moving my AUR build directory

By setting

export OPENSSL_CONF=/opt/anaconda/ssl/openssl.cnf

the warnings disappear. I suppose this is where makepkg should look for it? Or the openssl.conf in /etc/ssl ?
So does anybody have an idea why its looking the the build directory of my anaconda package instead?