package libgtest-dev (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

Bug #1678353 reported by Marc
66
This bug affects 12 people
Affects Status Importance Assigned to Milestone
googletest (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

This happened during the upgrade from 16.10 to 17.4

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libgtest-dev (not installed)
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Sat Apr 1 10:11:20 2017
DuplicateSignature:
 package:libgtest-dev:(not installed)
 Preparing to unpack .../288-libgtest-dev_1.8.0-6_amd64.deb ...
 dpkg-maintscript-helper: error: directory '/usr/src/gtest' contains files not owned by package libgtest-dev:amd64, cannot switch to symlink
 dpkg: error processing archive /tmp/apt-dpkg-install-QrnqCc/288-libgtest-dev_1.8.0-6_amd64.deb (--unpack):
  subprocess new pre-installation script returned error exit status 1
ErrorMessage: subprocess new pre-installation script returned error exit status 1
InstallationDate: Installed on 2015-09-12 (567 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.4~rc2
SourcePackage: googletest
Title: package libgtest-dev (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
UpgradeStatus: Upgraded to zesty on 2017-04-01 (0 days ago)

Revision history for this message
Marc (mflerackers) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in googletest (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :
Changed in googletest (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Terry Jones (terry-taralga) wrote :

I encountered this same bug on upgrade from 16.04 to 18.04

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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