Tagging oddity when installing a package from public channel

I installed  sed and zip from public channel and discovered that the following JSON files are untagged

- untagged T=off -rw-r--r-- 1 BPXROOT MVSBASIS 2111 Mar 26 09:46 ./conda-meta/sed-4.2.2-10.json
- untagged T=off -rw-r--r-- 1 BPXROOT MVSBASIS 3548 Mar 26 09:35 ./conda-meta/zip-3.0-6.json
- untagged T=off -rw-r--r-- 1 BPXROOT MVSBASIS 501 Mar 26 09:46 ./pkgs/sed-4.2.2-10/info/repodata_record.json
- untagged T=off -rw-r--r-- 1 BPXROOT MVSBASIS 495 Mar 26 09:33 ./pkgs/zip-3.0-6/info/repodata_record.json

They should be tagged as ISO8859-1. Or do I miss anything?

--
Manfred

Hi Tatjana,

I agree that is should not do any harm. I just didn't like that all json files coming from intial conda installation are tagged, and only those installed later are not.

Where is the tagging of those files controlled?

It is also ugly that the ownerships of those installed files are strange.

Here an example.

#l bin/zip*
-rwxrwxr-x 2 11039 200 884736 Jan 13 2020 zip
-rwxrwxr-x 2 11039 200 499712 Jan 13 2020 zipcloak
-rwxrwxr-x 2 11039 200 438272 Jan 13 2020 zipnote
-rwxrwxr-x 2 11039 200 454656 Jan 13 2020 zipsplit


--
Manfred