package libruby2.7 2.7.0-5ubuntu1.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/libruby2.7:amd64.list-new': Operation not permitted

Bug #1905134 reported by Svenja Marten
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ruby2.7 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Installation of latest version failed

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libruby2.7 2.7.0-5ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Nov 21 16:12:36 2020
DuplicateSignature:
 package:libruby2.7:2.7.0-5ubuntu1.1
 Unpacking libruby2.7:amd64 (2.7.0-5ubuntu1.1) ...
 dpkg: error processing archive /tmp/apt-dpkg-install-SWkjZb/294-libruby2.7_2.7.0-5ubuntu1.1_amd64.deb (--unpack):
  unable to create new file '/var/lib/dpkg/info/libruby2.7:amd64.list-new': Operation not permitted
ErrorMessage: unable to create new file '/var/lib/dpkg/info/libruby2.7:amd64.list-new': Operation not permitted
InstallationDate: Installed on 2018-02-20 (1005 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SourcePackage: ruby2.7
Title: package libruby2.7 2.7.0-5ubuntu1.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/libruby2.7:amd64.list-new': Operation not permitted
UpgradeStatus: Upgraded to focal on 2020-11-21 (0 days ago)

Revision history for this message
Svenja Marten (svenjamarten) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Bryce Harrington (bryce) wrote :

Bug #1685984 suggests there is a bug in dpkg itself that can lead to installation failures with this same message. I'm going to mark this as a dupe of that.

It sounds like it's possible to workaround the issue, though unclear what would work in your case. If you're still having trouble, there are some pointers for community support at http://www.ubuntu.com/support/community that may be able to assist.

Revision history for this message
Bryce Harrington (bryce) wrote :

There is a similar bug against emacs: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1805135

The error message itself comes from atomic_file_open() in dpkg.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.