Project

General

Profile

Bug #1957

db-update spits errors about "bsdtar: Error opening archive: Failed to open 'staging/…'"

lukeshu - over 5 years ago - . Updated over 5 years ago.

Status:
fixed
Priority:
bug
Assignee:
lukeshu
% Done:

100%

Description

Here's a sample of the output from librerelease. I think db-update has done this on every run for a while.

…
==> Running db-update on repos
copied 'sources/parabola/opentmpfiles-0.1.3-8-any.src.tar.gz' -> '/srv/repo/main/sources/parabola/opentmpfiles-0.1.3-8-any.src.tar.gz'
removed 'sources/parabola/opentmpfiles-0.1.3-8-any.src.tar.gz'
copied 'sources/parabola/opensysusers-0.4.8-5-any.src.tar.gz' -> '/srv/repo/main/sources/parabola/opensysusers-0.4.8-5-any.src.tar.gz'
removed 'sources/parabola/opensysusers-0.4.8-5-any.src.tar.gz'
copied 'sources/parabola/opentmpfiles-0.1.3-8-any.src.tar.gz.sig' -> '/srv/repo/main/sources/parabola/opentmpfiles-0.1.3-8-any.src.tar.gz.sig'
removed 'sources/parabola/opentmpfiles-0.1.3-8-any.src.tar.gz.sig'
copied 'sources/parabola/opensysusers-0.4.8-5-any.src.tar.gz.sig' -> '/srv/repo/main/sources/parabola/opensysusers-0.4.8-5-any.src.tar.gz.sig'
removed 'sources/parabola/opensysusers-0.4.8-5-any.src.tar.gz.sig'
bsdtar: Error opening archive: Failed to open 'staging/luke/staging//pcr/opensysusers-0.4.8-5-any.pkg.tar.xz'
bsdtar: Error opening archive: Failed to open 'staging/luke/staging//pcr/opensysusers-manpages-0.4.8-5-any.pkg.tar.xz'
bsdtar: Error opening archive: Failed to open 'staging/luke/staging//pcr/opensysusers-systemdcompat-0.4.8-5-any.pkg.tar.xz'
bsdtar: Error opening archive: Failed to open 'staging/luke/staging//pcr/opentmpfiles-0.1.3-8-any.pkg.tar.xz'
bsdtar: Error opening archive: Failed to open 'staging/luke/staging//pcr/opentmpfiles-systemdcompat-0.1.3-8-any.pkg.tar.xz'
==> Updating [pcr]...
  -> opensysusers-0.4.8-5-any.pkg.tar.xz (x86_64)
…

History

#1

Updated by lukeshu over 5 years ago

  • % Done changed from 0 to 90
  • Assignee set to lukeshu
  • Status changed from open to in progress

It seems that the issue is that librerelease sets STAGING to a relative path, but db-update's check_splitpkgs() calls pushd, meaning that the relative path doesn't work inside of that function.

In dbscripts v20180926 the default config has changed to set STAGING to the absolute path when inheriting a relative path from the environment.

Leaving this at 90% until we get some verifications that the v20180926 rollout fixes the issue.

#2

Updated by lukeshu over 5 years ago

  • % Done changed from 90 to 100
  • Status changed from in progress to fixed

confirmed

Also available in: Atom PDF