error building from pkgsrc-wip -- Package 'x11' not found

Out-of-topic and not related but, pinentry-dmenu says,

NO FURTHER DEVELOPMENT
This project is no longer under development. If you have another opinion feel free to fork it.

pfr

pin Sometimes I wonder ... how you are building stuff

$ doas make install

pin Either, you learn something about dependencies

Please, tell me where I'm going wrong.

pin or, you build as root ... then it will also build the missing dependencies while building the target package.

I am building everything as root because I simply cannot build anything as a normal user.

/usr λ ls
drwxr-xr-x - root  3 May 14:14  bin
drwxr-xr-x - root  6 May 20:55  distfiles
drwxr-xr-x - root  3 May 14:14  games
drwxr-xr-x - root  3 May 14:14  include
drwxr-xr-x - root  3 May 14:18  INSTALL
drwxr-xr-x - root  3 May 14:14  lib
drwxr-xr-x - root  2 May 07:34  libdata
drwxr-xr-x - root  3 May 14:14  libexec
drwxr-xr-x - root  3 May 15:52  local
drwxr-xr-x - root  2 May 07:34  mdec
drwxr-xr-x - root  6 May 13:32  pkg
drwxrwxr-x - dave  4 May 23:08  pkgsrc
drwxr-xr-x - root  3 May 14:14  sbin
drwxr-xr-x - root  3 May 14:14  share
drwxr-xr-x - root  2 May 07:34  tests
drwxr-xr-x - root  2 May 07:34  X11R7

/usr λ cd pkgsrc/x11/rofi/
/usr/pkgsrc/x11/rofi λ ls
drwxrwxr-x    - dave  8 Apr 11:01  CVS
.rw-r--r--  404 dave 13 Jun  2016  DESCR
.rw-r--r--  348 dave 26 Oct  2021  distinfo
.rw-r--r-- 1.1k dave  8 Apr 11:01  Makefile
.rw-r--r-- 1.4k dave 18 Oct  2021  PLIST
lrwxr-xr-x    - 1524  7 Apr  2021  README.html -> index.html

/usr/pkgsrc/x11/rofi λ make
=> Bootstrap dependency digest>=20211023: found digest-20220214
=> Fetching rofi-1.7.0.tar.xz
fetch: WARNING: DISTDIR /usr/distfiles looks non-writable.
=> Total size: 733632 bytes
Requesting https://github.com/DaveDavenport/rofi/releases/download/1.7.0/rofi-1.7.0.tar.xz
Redirected to https://github.com/davatorium/rofi/releases/download/1.7.0/rofi-1.7.0.tar.xz
Requesting https://github.com/davatorium/rofi/releases/download/1.7.0/rofi-1.7.0.tar.xz
Redirected to https://objects.githubusercontent.com/github-production-release-asset-2e65be/7715820/b67c288e-0300-493f-9de6-76099d99538a?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20240506%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20240506T111500Z&X-Amz-Expires=300&X-Amz-Signature=99c5d0b96cc35674cb5ffe68907afb281069d0cbfd306f8d2280cfb40456765d&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=7715820&response-content-disposition=attachment%3B%20filename%3Drofi-1.7.0.tar.xz&response-content-type=application%2Foctet-stream
Trying 185.199.110.133:443 ...
Requesting https://objects.githubusercontent.com/github-production-release-asset-2e65be/7715820/b67c288e-0300-493f-9de6-76099d99538a?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAVCODYLSA53PQK4ZA%2F20240506%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20240506T111500Z&X-Amz-Expires=300&X-Amz-Signature=99c5d0b96cc35674cb5ffe68907afb281069d0cbfd306f8d2280cfb40456765d&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=7715820&response-content-disposition=attachment%3B%20filename%3Drofi-1.7.0.tar.xz&response-content-type=application%2Foctet-stream
ftp: Can't open `rofi-1.7.0.tar.xz': Permission denied
fetch: Unable to fetch expected file rofi-1.7.0.tar.xz
Trying [2a04:4e42:600::262]:443 ...
Requesting https://cdn.NetBSD.org/pub/pkgsrc/distfiles/rofi-1.7.0.tar.xz
ftp: Can't open `rofi-1.7.0.tar.xz': Permission denied
fetch: Unable to fetch expected file rofi-1.7.0.tar.xz
Trying [2001:660:3302:282a:204:75ff:fe9f:9e11]:80 ...
Requesting http://ftp.fr.NetBSD.org/pub/pkgsrc/distfiles/rofi-1.7.0.tar.xz
ftp: Can't open `rofi-1.7.0.tar.xz': Permission denied
fetch: Unable to fetch expected file rofi-1.7.0.tar.xz
Trying [2001:470:a085:999::21]:443 ...
Requesting https://ftp.NetBSD.org/pub/pkgsrc/distfiles/rofi-1.7.0.tar.xz
ftp: Can't open `rofi-1.7.0.tar.xz': Permission denied
fetch: Unable to fetch expected file rofi-1.7.0.tar.xz
*** Error code 1

Stop.
make: stopped in /usr/pkgsrc/x11/rofi

As you can see user dave owns the entire pkgsrc directory. My user is in the wheel group.. etc
I show this just as an example to highlight that I have been building all packages as root.

pin NO FURTHER DEVELOPMENT

It still works, but I guess you're right, I should find another pinentry program, but I still need to understand what is going wrong here.

pfr Please, tell me where I'm going wrong.

Honestly, I don't know. Here, if I start a build of a package that requires a dependency that it's not installed, it will start by building the dependency first followed by the target package.

So, why building gnupg2 at your end doesn't trigger the build of readline, I don't know.

rvp

pfr As you can see user dave owns the entire pkgsrc directory.

But, why is distfiles outside the pkgsrc tree? And, owned by root instead of dave:

drwxr-xr-x - root  6 May 20:55  distfiles

No wonder just make as dave fails to download files.

What other screwiness is going on, I can't tell...

pkgsrc is very simple on NetBSD:

$ whoami
bld                           # separate user for building pkgs.; must be in group `wheel'
$ tar -C ~ -xf pkgsrc-2024Q1.tar.xz
$ cd ~/pkgsrc/some/package
$ make install clean          # clean-depends

That should (nay, will) fetch, compile and install all of package's deps. And ask for the root password when privileges are needed for the install phase.

kc9udx

As far as I know, you have to bootstrap pkgsrc to run unprivileged if you want to use it without root.

Doing this could possibly alleviate your other problem, too.

See this

pfr

kc9udx thanks, I'll try this.

I've never had to do this. But, maybe this is related to doas and the absence of persist outside OpenBSD.
For sure, I haven't bootstraped unprivileged.

EDIT: What I usually do is probably not recommended but, I don't really care, it works for me.
After fetching and unpackning the tarball,

cd /usr
su
chown -R pin pkgsrc/

Also, I use please which has fine grained control of permissions.

pfr

pin doas and the absence of persist outside OpenBSD.

I was wondering why persist doesn't work... I'm using opendoas and I could have sworn persist has worked in the past but my memory has proven to be untrustworthy 😆

pin Also, I use please which has fine grained control of permissions.

I still have my old please.ini file backed up. Might ditch opendoas and use this again. it'll just mean that I need to change my alias alias please='doas $(fc -ln -1)' ... doh! perhaps?

rvp But, why is distfiles outside the pkgsrc tree? And, owned by root instead of dave:

I never manually moved any files or folders. I installed pkgsrc during the system install and, as Pin suggested above I just did chown -R dave /usr/pkgsrc/ as root.

I'm going to fetch a new pkgsrc tarball tonight and try again.

rvp pkgsrc is very simple on NetBSD

You're the second person to say this, amplifying my feelings of inadequacy 🙄
But I plead Not Guilty! ...at least until I can trace the root cause of the error back to me.

kc9udx

I always do it. Not because it's necessary; but there are packages for which all the dependencies are already installed, where I can build the package without ever being root.

For what it's worth, I typically chown myself /usr/pkgsrc, too, so it works either way.

kc9udx Exactly but, our friend says it's not working 🤔

rvp Well spotted 😀

Indeed it's weird, wonder how this ia possible.

rvp

pfr at least until I can trace the root cause of the error back to me.

What's your /etc/mk.conf look like?

kc9udx

I suggest to backup and remove your /etc/mk.conf
Of course, make sure to rm -R /usr/pkgsrc before you extract the new tarball and check that you don't have a mk.conf hiding somewhere else (home directories, etc.)
Then do the unprivileged bootstrap. You'll get a giant new mk.conf and it will likely need tailoring by you. But it will specify distfiles in /usr/pkgsrc

rvp Again, well spotted 😀

I just had a look at our mates dotfiles on his repository and look what I found,

# /etc/mk.conf
[...]
DISTDIR=                /usr/distfiles
[...]

There're other "interesting choices" that may cause trouble in the future.

rvp

# /etc/mk.conf
[...]
DISTDIR=                /usr/distfiles
[...]

Ay yi yi.

pfr

pin There're other "interesting choices" that may cause trouble in the future.

Ok ok.. but the word "choices" implies I knew what I was doing... I honestly have no idea where I've copied and pasted that from, into my mk.conf but if it's wrong then I admit it's my fault 😅 But it wasn't a conscious choice per se, more of an accident (have mercy!) 🙏 🙏

So.. here is the current mk.conf file. Please tell me what to keep, what to remove, or what to change, before I fetch another pkgsrc tarball

VARBASE=                /var
LOCALBASE=              /usr/pkg
WKROBJDIR=              /usr/work
DISTDIR=                /usr/distfiles
PKG_DBDIR=              /usr/pkg/pkgdb
PKG_TOOLS_BIN=          /usr/pkg/sbin
PKGINFODIR=             info
PKGMANDIR=              man
MAKE_JOBS=              6
PKGSRC_USE_MKTOOLS=     yes
ALLOW_VULNERABLE_PACKAGES= yes
SKIP_LICENSE_CHECK= yes
RUST_TYPE=              src
PKG_DEVELOPER=          yes

Honestly, I'd like to just keep the things I need and remove the unecessary stuff. Looking at this thread it seems that many have a pretty minimal mk.conf.

If I was to have a guess, I'd try this:

MAKE_JOBS=              6
PKGSRC_USE_MKTOOLS=     yes
ALLOW_VULNERABLE_PACKAGES= yes
SKIP_LICENSE_CHECK= yes

@pfr It's all about options/choices but, if you ask me, I would say:

These should be set. Probably not as critical as when the package database was moved, might be overkill in the future but, they won't harm anything,

PKG_DBDIR=                      /usr/pkg/pkgdb
LOCALBASE=                      /usr/pkg
VARBASE=                        /var
PKG_TOOLS_BIN=                  /usr/pkg/sbin
PKGINFODIR=                     info
PKGMANDIR=                      man

These are for build speed,

PKGSRC_USE_MKTOOLS=             yes
MAKE_JOBS=                      4    # Set to the number of cpu cores

Other things are preferences and package options. But, you might want to set at least ALLOW_VULNERABLE_PACKAGES and ACCEPTABLE_LICENSES

Besides the problematic ones that you had set, already discussed on this or, other threads, there's one more that you might want to remove, WKROBJDIR= /usr/work.

pfr

pin Thanks, will make these adjustments and then attempt to re-fetch pkgsrc

pin ACCEPTABLE_LICENSES

Can I not just use SKIP_LICENSE_CHECK as I'm not at all fussed with licenses.

Right now, if I were you, I would fix my mk.conf and then remove the whole pkgsrc directory and distfiles.

Fetch a fresh tarball, unpack it into place and chown the directory. Bring it up-to-date and check if anything that you already have installed needs updating. After that, you may proceed with building what you still missing.

pfr This is up to you. I find some licenses non-acceptable and refuse to use software under those.

If you are building rust packages, you should set that also.

« Previous Page Next Page »