You are not logged in.

#1 2023-09-19 15:58:44

flaki
Member
Registered: 2023-09-19
Posts: 4

[Solved] Reproducible build issue

Im trying to reproduce some packages using the repro command and came across an issue.

When running the comman "repro -d lf-31-1-x86_64.pkg.tar.zst" I eventually get to the folowing:

-> Finished preparing packages
==> Starting build...
  -> Create snapshot for lf_6698...
  -> Fetching PKGBUILD from git...
resolving dependencies...
looking for conflicting packages...

Packages (39) apr-1.7.3-1  apr-util-1.6.3-1  binutils-2.41-3  breezy-3.3.4-1  db-6.2.32-1  db5.3-5.3.28-4  diffutils-3.10-1  dnssec-anchors-20190629-3  fakeroot-1.32.1-1  git-2.42.0-1  jansson-2.14-2
              jq-1.7-1  ldns-1.8.3-2  libedit-20230828_3.1-1  libnsl-2.0.0-3  libutf8proc-2.8.0-1  libyaml-0.2.5-2  mercurial-6.5.2-1  oniguruma-6.9.8-1  openssh-9.4p1-4  parallel-20230822-1
              perl-5.38.0-1  perl-error-0.17029-5  perl-mailtools-2.21-7  perl-timedate-2.33-5  python-3.11.5-2  python-configobj-5.0.8-4  python-dulwich-0.21.6-2  python-fastbencode-0.2-2
              python-merge3-0.0.14-1  python-patiencediff-0.2.14-1  python-six-1.16.0-8  python-urllib3-1.26.15-1  python-yaml-6.0.1-2  rsync-3.2.7-4  serf-1.3.9-8  subversion-1.14.2-9  xxhash-0.8.2-1
              devtools-1:1.0.3-3

Total Download Size:    40.77 MiB
Total Installed Size:  390.06 MiB

:: Proceed with installation? [Y/n]
:: Retrieving packages...
Total ( 0/28)                                                                                40.8 MiB  39.8 GiB/s 00:00 [#########################################################################] 100%
error: could not open file /var/cache/pacman/pkg/python-3.11.5-2-x86_64.pkg.tar.zst.part: Required key not available
error: failed to setup a download payload for python-3.11.5-2-x86_64.pkg.tar.zst
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.
bash: line 5: pkgctl: command not found
ERROR: Failed checkout lf
  -> Delete snapshot for lf_6698...

I made sure to update all packages on the host system first but I cant get past this point and I didnt find any similar issues.
Perhaps anyone can point out what is wrong here?

Last edited by flaki (2023-09-19 18:38:06)

Offline

#2 2023-09-19 16:05:14

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,798

Re: [Solved] Reproducible build issue

delete the file that's causing a problem and try again.

Offline

#3 2023-09-19 16:26:50

flaki
Member
Registered: 2023-09-19
Posts: 4

Re: [Solved] Reproducible build issue

/var/cache/pacman/pkg/python-3.11.5-2-x86_64.pkg.tar.zst.part does not exist and deleting /var/cache/pacman/pkg/python-3.11.5-2-x86_64.pkg.tar.zst did not change anything either.

I suspect it has something todo with archlinux-keyring due to the "Required key not found" error and the fact that the keyring package was updates yesterday.

The same issue also arisis with other packages when I try to reproduce them

Last edited by flaki (2023-09-19 16:44:29)

Offline

#4 2023-09-19 17:51:38

flaki
Member
Registered: 2023-09-19
Posts: 4

Re: [Solved] Reproducible build issue

After trying the reproduction on other arch systems that were not updated recently I first got the same issue, but the error message indicated that the python package could not be fetched from the remote site. After a few more attempts, eventually the python package installed and repro showed the package to be reproducible.

While I am not certain, it looks like this issue was caused by the remote repository for the python package being temporarily unavailable/unstable

Offline

#5 2023-09-19 18:37:52

flaki
Member
Registered: 2023-09-19
Posts: 4

Re: [Solved] Reproducible build issue

The remote repo error seems to have been unrelated after all.

After I moved the reproduction to /tmp it worked just fine.
I suspect the issue "Required key not available" is caused by restrictions on my home directory and the used ext4 encryption (fscrypt)
Alternatively, the mount option for my home directory include nosuid,nodev which might also have caused issues.

In any case, running the command in /tmp worked

Offline

Board footer

Powered by FluxBB