New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qubes-release RPM errors #3756

Closed
mirrorway opened this Issue Mar 28, 2018 · 6 comments

Comments

Projects
None yet
4 participants
@mirrorway

Qubes OS version:

R4.0rc5

Affected component(s):

qubes-release package


Steps to reproduce the behavior:

Install or reinstall this package.

Expected behavior:

Install or reinstalls without errors.

Actual behavior:

RPM lock errors.

$ sudo qubes-dom0-update --action=reinstall qubes-release
Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time...
/usr/lib/qubes/qubes-rpc-multiplexer: 14: /etc/profile.d/20_power_savings_disable_in_vms.sh: shopt: not found
/usr/lib/qubes/qubes-rpc-multiplexer: 14: /etc/profile.d/20_power_savings_disable_in_vms.sh: shopt: not found
qubes-dom0-current-testing                               | 3.6 kB     00:00     
--> Running transaction check
---> Package qubes-release.noarch 0:4.0-1 will be reinstalled
--> Finished Dependency Resolution
/var/lib/qubes/dom0-updates/packages/qubes-release-4.0-1.noarch.rpm already exists and appears to be complete
find: `/var/lib/qubes/dom0-updates/var/cache/yum': No such file or directory
Qubes OS Repository for Dom0                     31 MB/s |  32 kB     00:00    
Dependencies resolved.
================================================================================
 Package              Arch          Version      Repository                Size
================================================================================
Reinstalling:
 qubes-release        noarch        4.0-1        qubes-dom0-cached         50 k

Transaction Summary
================================================================================

Total size: 50 k
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Reinstalling: qubes-release-4.0-1.noarch                                  1/2 
  Erasing     : qubes-release-4.0-1.noarch                                  2/2 
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-primary: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3.1-primary: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3.1-templates-community: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3.1-unstable: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3.2-primary: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3.2-templates-community: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3.2-unstable: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3-primary: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3-templates-community: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-3-unstable: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-4.0-primary: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-4.0-templates-community: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-4.0-unstable: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-4-primary: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-4-templates-community: key 1 import failed.
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-4-unstable: key 1 import failed.
  Verifying   : qubes-release-4.0-1.noarch                                  1/2 
  Verifying   : qubes-release-4.0-1.noarch                                  2/2 

Reinstalled:
  qubes-release.noarch 4.0-1                                                    

Complete!

General notes:

Renaming the lock file didn't fix it.


@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@mirrorway

This comment has been minimized.

Show comment
Hide comment
@mirrorway

mirrorway Mar 30, 2018

The "shopt" errors above is probably a different bug. For example, they also occur if you do qvm-run -p anon-whonix ls, where anon-whonix is based on whonix-ws-13.

The shopt errors go away in whonix-ws-14.

mirrorway commented Mar 30, 2018

The "shopt" errors above is probably a different bug. For example, they also occur if you do qvm-run -p anon-whonix ls, where anon-whonix is based on whonix-ws-13.

The shopt errors go away in whonix-ws-14.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Apr 5, 2018

Member

Passing along the following note from Achim:

On 2018-04-04 09:47, Achim wrote:

I've been running into this too; it is hitting an archlinux template
hard enough to make it impossible to upgrade it using either pacman,
yaourt or powerpill.

The reason is relatively obvious but as the mechanism is not
documented, I can't find it quickly: Someone is using /bin/sh to
execute a bash script (because he forgot that sh is not always an alias
for bash) and shopt is only built into bash). Could you ask wever is
responsible for the Qubes integration to look for the place where he is
explicitly executing something using "sh" for the call (or at least add
that request to the open issue)?

Member

andrewdavidwong commented Apr 5, 2018

Passing along the following note from Achim:

On 2018-04-04 09:47, Achim wrote:

I've been running into this too; it is hitting an archlinux template
hard enough to make it impossible to upgrade it using either pacman,
yaourt or powerpill.

The reason is relatively obvious but as the mechanism is not
documented, I can't find it quickly: Someone is using /bin/sh to
execute a bash script (because he forgot that sh is not always an alias
for bash) and shopt is only built into bash). Could you ask wever is
responsible for the Qubes integration to look for the place where he is
explicitly executing something using "sh" for the call (or at least add
that request to the open issue)?

@e6lk7dqzm83p

This comment has been minimized.

Show comment
Hide comment
@e6lk7dqzm83p

e6lk7dqzm83p Jun 19, 2018

Was anyone able to resolve this issue? I'm trying to update my kernel (to see if that solves the unusable lag I get in my R4 install) and got the same errors.

Was anyone able to resolve this issue? I'm trying to update my kernel (to see if that solves the unusable lag I get in my R4 install) and got the same errors.

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Jul 3, 2018

Automated announcement from builder-github

The package pykickstart-2.32-4.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

Automated announcement from builder-github

The package pykickstart-2.32-4.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@qubesos-bot qubesos-bot referenced this issue in QubesOS/updates-status Jul 3, 2018

Closed

installer-qubes-os v25.20.9-13-anaconda (r4.0) #570

marmarek added a commit to QubesOS/qubes-installer-qubes-os that referenced this issue Jul 14, 2018

qubes-release: schedule keys import after update
It isn't possible to import rpm signing keys during update, because
rpm itself holds a lock. Schedule the operation after update using
systemd-run.

Fixes QubesOS/qubes-issues#3756

(cherry picked from commit 7d5bb6f)

@qubesos-bot qubesos-bot referenced this issue in QubesOS/updates-status Jul 14, 2018

Closed

installer-qubes-os v3.2-2-qubes-release (r3.2) #582

@qubesos-bot

This comment has been minimized.

Show comment
Hide comment
@qubesos-bot

qubesos-bot Jul 23, 2018

Automated announcement from builder-github

The package pykickstart-2.32-4.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

Automated announcement from builder-github

The package pykickstart-2.32-4.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment