package volatility 2.3.1-7 failed to install/upgrade: trying to overwrite directory '/usr/lib/python2.7/dist-packages/volatility-2.5.egg-info' in package python-volatility 2.5-1-trusty1 with nondirectory

Bug #1762393 reported by me
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
volatility (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: volatility 2.3.1-7
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Mon Apr 9 13:00:03 2018
ErrorMessage: trying to overwrite directory '/usr/lib/python2.7/dist-packages/volatility-2.5.egg-info' in package python-volatility 2.5-1-trusty1 with nondirectory
InstallationDate: Installed on 2016-10-19 (536 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt 1.2.26
SourcePackage: volatility
Title: package volatility 2.3.1-7 failed to install/upgrade: trying to overwrite directory '/usr/lib/python2.7/dist-packages/volatility-2.5.egg-info' in package python-volatility 2.5-1-trusty1 with nondirectory
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
me (meupyou974) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Kai Kasurinen (kai-kasurinen) wrote :

python-volatility 2.5-1-trusty1

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in volatility (Ubuntu):
status: New → Invalid
Revision history for this message
Kai Kasurinen (kai-kasurinen) wrote :

Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories.

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.