archlinux package produces warnings when installed

[j-tai]

What happened?

When nfpm generates an archlinux package, and that package is installed, several warnings are printed by pacman:

loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (1) foo-1.2.3-1

Total Installed Size:  0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring                               [################################] 100%
(1/1) checking package integrity                             [################################] 100%
(1/1) loading package files                                  [################################] 100%
(1/1) checking for file conflicts                            [################################] 100%
(1/1) checking available disk space                          [################################] 100%
:: Processing package changes...
(1/1) installing foo                                         [################################] 100%
warning: file not found in file list for package foo. skipping extraction of usr/
warning: file not found in file list for package foo. skipping extraction of usr/share/
warning: file not found in file list for package foo. skipping extraction of usr/share/foo/

I expected the package to install without these warnings.

How can we reproduce this?

On a machine running Arch Linux:

$ git clone https://git.jtai.ca/repro/nfpm-2
$ cd nfpm-2
$ nfpm package -p archlinux
$ sudo pacman -U foo-1.2.3-1-any.pkg.tar.zst 

For reference, here is the nfpm.yaml:

name: foo
arch: all
version: 1.2.3
maintainer: asdf

contents:
  - src: test.txt
    dst: /usr/share/foo/test.txt

nfpm version

nfpm version nfpm version 2.27.1
commit: d30c22f50d30d92a8039bd14d789ad85d0019fd8
built at: 2023-03-20T01:43:40Z
built by: goreleaser
module version: v2.27.1, checksum: h1:+q7/aY+SCQjB5OKiqzdBVoFIhG1XnxRBU2Pxqt8qm3U=

Search

• I did search for other open and closed issues before opening this.

Code of Conduct

• I agree to follow this project's Code of Conduct

Additional context

No response

[j-tai]

It might be because the parent directories need to be added to the package's .MTREE.

[caarlos0]

investigating this a bit...

it seems that .BUILDINFO is missing... which I think is fine... but the main issue seems to be that the permissions are different... maybe that's the issue?

[caarlos0]

oh, when creating the pkg directly from nfpm, it indeed does not have the parent dirs there...