Stray /usr/.crates2.json file

This seems to be an issue with the Rust build tools, as the file is present in both the 'bat' and 'ripgrep' packages. The two are of course uninstallable together because of this.

The file appeared when the packages have been rebuilt with this changelog entry:

 * No-change rebuild for libgcc-s1 package name change.

I rebuilt the package on an up-to-date Debian/sid system and the stray file is not present in the resulting binary package, so the problem seems to be specific to Ubuntu.

(I maintain the Debian bat package.)

I rebuilt bat 0.12.1-1build1 on Focal with focal-proposed enabled and the stray file *is* there.

This is an issue with the cargo package, which is ahead of Debian at the moment.

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

This has also been reported on the 'bat' issue tracker: https://github.com/sharkdp/bat/issues/938

I found this section on the Arch Linux wiki on "Rust package guidelines" (https://wiki.archlinux.org/index.php/Rust_package_guidelines#Notes_about_using_cargo_install):

"The --no-track argument should always be used, because cargo install may create unwanted files such as /usr/.crates.toml or /usr/.crates2.json unless it is specified."

I'm sorry about these state changes. They were done by accident. That was not my intention.

This bug has been reported in Debian [1] against the dh-cargo package, but fixed in version 0.43.1-3 of the cargo package.

Syncing with Debian will prevent new package builds from having the stray .crates2.json file, but binary packages built with the buggy version of cargo need to be rebuilt to get rid of the file.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958301

Rebuilds are being prepared.

This bug was fixed in the package cargo - 0.42.0-0ubuntu2

---------------
cargo (0.42.0-0ubuntu2) groovy; urgency=medium

  * Cherry-pick commit from Debian to remove /usr/.crates2.json (LP: #1868517)

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:28:25 +0200

This bug was fixed in the package rust-xml-rs - 0.8.0-1build2

---------------
rust-xml-rs (0.8.0-1build2) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:40:28 +0200

This bug was fixed in the package rust-ripgrep - 12.0.1-1build1

---------------
rust-ripgrep (12.0.1-1build1) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:38:03 +0200

This bug was fixed in the package rust-rusty-tags - 3.5.1-2build2

---------------
rust-rusty-tags (3.5.1-2build2) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:38:51 +0200

This bug was fixed in the package rust-ucd-generate - 0.2.3-1build2

---------------
rust-ucd-generate (0.2.3-1build2) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:40:05 +0200

This bug was fixed in the package rust-nitrocli - 0.2.4-1build2

---------------
rust-nitrocli (0.2.4-1build2) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:36:42 +0200

This bug was fixed in the package rust-pulldown-cmark - 0.2.0-1build2

---------------
rust-pulldown-cmark (0.2.0-1build2) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:37:42 +0200

This bug was fixed in the package rust-difference - 2.0.0-1build2

---------------
rust-difference (2.0.0-1build2) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:34:46 +0200

This bug was fixed in the package rust-hexyl - 0.7.0-1build1

---------------
rust-hexyl (0.7.0-1build1) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:35:37 +0200

This bug was fixed in the package rust-lscolors - 0.7.0-1build1

---------------
rust-lscolors (0.7.0-1build1) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:36:18 +0200

This bug was fixed in the package rust-cbindgen - 0.14.1-1build1

---------------
rust-cbindgen (0.14.1-1build1) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:34:25 +0200

This bug was fixed in the package rust-lalrpop - 0.17.2-4build2

---------------
rust-lalrpop (0.17.2-4build2) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:35:57 +0200

This bug was fixed in the package rust-rustdoc-stripper - 0.1.9-2build2

---------------
rust-rustdoc-stripper (0.1.9-2build2) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 29 Apr 2020 13:38:24 +0200

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

So updates:

* Found out that sniffglue from rust-sniffglue also includes file -> new
* rust-bat is sitting in proposed still -> fix committed
* rust-fd-find does not actually seem to include the file, at least on amd64 -> incomplete

@Julian: fd-find 7.4.0-2build1 and 8.0.0-1 (in Focal and Groovy respectively) do include the file:

$ dpkg -l fd-find
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-==================================================
ii fd-find 8.0.0-1 amd64 Simple, fast and user-friendly alternative to find

$ dpkg -L fd-find | grep -F crates2
/usr/lib/cargo/.crates2.json

This bug was fixed in the package rust-fd-find - 8.0.0-1build1

---------------
rust-fd-find (8.0.0-1build1) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 06 May 2020 13:22:34 +0200

This bug was fixed in the package rust-dotenv - 0.15.0-2build1

---------------
rust-dotenv (0.15.0-2build1) groovy; urgency=high

  * No change rebuild to remove /usr/.crates2.json (LP: #1868517).

 -- Julian Andres Klode <email address hidden> Wed, 06 May 2020 13:21:24 +0200

Two months later and I still can't install ripgrep and bat. This is fixed in the source, but can we have a new release for focal please?

Seconded. I just edited the two *.list file and hand-removed /usr/.crates.json to have bat and ripgrep coexist. I really shouldn't have to.

I stumbled on this and thought I'd post my workaround in case someone else needed it:

```shell
$ apt-get download ripgrep

$ sudo dpkg --force-overwrite -i ripgrep*.deb
```

It is now July and using Ubuntu 20.04 and get this:

# apt install ripgrep
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  ripgrep
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1228 kB of archives.
After this operation, 4502 kB of additional disk space will be used.
(Reading database ... 107634 files and directories currently installed.)
Preparing to unpack .../ripgrep_11.0.2-1build1_amd64.deb ...
Unpacking ripgrep (11.0.2-1build1) ...
dpkg: error processing archive /var/cache/apt/archives/ripgrep_11.0.2-1build1_amd64.deb (--unpack):
 trying to overwrite '/usr/.crates2.json', which is also in package bat 0.12.1-1build1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/ripgrep_11.0.2-1build1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

$ date
Sun 11 Oct 2020 01:38:28 PM PDT

$ sudo apt update
...
Fetched 1,404 kB in 1s (1,056 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ sudo apt-get install ripgrep
[sudo] password for zachariah:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  ripgrep
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,228 kB of archives.
After this operation, 4,502 kB of additional disk space will be used.
(Reading database ... 445348 files and directories currently installed.)
Preparing to unpack .../ripgrep_11.0.2-1build1_amd64.deb ...
Unpacking ripgrep (11.0.2-1build1) ...
dpkg: error processing archive /var/cache/apt/archives/ripgrep_11.0.2-1build1_amd64.deb (--unpack):
 trying to overwrite '/usr/.crates2.json', which is also in package bat 0.12.1-1build1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/ripgrep_11.0.2-1build1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal

$ apt --version
apt 2.0.2ubuntu0.1 (amd64)

So I guess we're... waiting for a backport?

In the meanwhile, edit /var/lib/dpkg/info/ripgrep.list and remove the usr/.* junk that rust helpfully leaves around.

This still appears to be an issue on focal:

± apt-file search '/usr/.crates2.json'
bat: /usr/.crates2.json
cbindgen: /usr/.crates2.json
difference: /usr/.crates2.json
hexyl: /usr/.crates2.json
lalrpop: /usr/.crates2.json
lscolors: /usr/.crates2.json
nitrocli: /usr/.crates2.json
pulldown-cmark: /usr/.crates2.json
ripgrep: /usr/.crates2.json
rustdoc-stripper: /usr/.crates2.json
rusty-tags: /usr/.crates2.json
ucd-generate: /usr/.crates2.json
xml-rs: /usr/.crates2.json

Does apt-file work with updates or just what's in a release pocket?

Thanks

No back port for 20.04 **LTS** planned?
How long will it take?

Could someone please finally fix this on 20.04 LTS? I imagine it should be trivial, but I don't have the knowledge/skill at this time.

When will this be fixed in 20.04 LTS? If not, why not?

another person bit by this on LTS and wondering why it never got fixed.

Since the fixed version of cargo has reached Focal through -security, it should simply be a matter of uploading no-change rebuilds for all those packages. The actual problem would be testing all the affected packages afterwards, though.