package bat (not installed) failed to install/upgrade: Versuch, »/usr/.crates2.json« zu überschreiben, welches auch in Paket ripgrep 11.0.2-1build1 ist

Bug #1904699 reported by Michael Mosmann
This bug report is a duplicate of:  Bug #1868517: Stray /usr/.crates2.json file. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rust-bat (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have ripgrep installed.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bat (not installed)
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
AptOrdering:
 bat:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Nov 18 09:11:03 2020
DpkgTerminalLog:
 Vorbereitung zum Entpacken von .../bat_0.12.1-1build1_amd64.deb ...
 Entpacken von bat (0.12.1-1build1) ...
 dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/bat_0.12.1-1build1_amd64.deb (--unpack):
  Versuch, »/usr/.crates2.json« zu überschreiben, welches auch in Paket ripgrep 11.0.2-1build1 ist
ErrorMessage: Versuch, »/usr/.crates2.json« zu überschreiben, welches auch in Paket ripgrep 11.0.2-1build1 ist
InstallationDate: Installed on 2020-07-22 (119 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SourcePackage: rust-bat
Title: package bat (not installed) failed to install/upgrade: Versuch, »/usr/.crates2.json« zu überschreiben, welches auch in Paket ripgrep 11.0.2-1build1 ist
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Michael Mosmann (michael-mosmann) wrote :
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1868517, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.