This replacement is causing an issue with how debian system package resources are found and associated in the scancode.io docker pipeline. Some debian .list files have : in their names to separate the architecture from the package name, e.g. libc6:amd64.list. However, extractcode extracts this file as libc6_amd64.list. The code run in the docker pipeline is trying to find the original, unmodified name (libc6:amd64.list), and such the pipeline does not find the declared resources of a package from the .list as it was extracted as libc6_amd64.list
This replacement is causing an issue with how debian system package resources are found and associated in the scancode.io docker pipeline. Some debian
.listfiles have:in their names to separate the architecture from the package name, e.g.libc6:amd64.list. However, extractcode extracts this file aslibc6_amd64.list. The code run in the docker pipeline is trying to find the original, unmodified name (libc6:amd64.list), and such the pipeline does not find the declared resources of a package from the.listas it was extracted aslibc6_amd64.list