Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@jedevc
Copy link
Contributor

@jedevc jedevc commented Feb 6, 2023

⬆️ Follow up to #1485

When base is set, it should appear identically to when we scan the root filesystem - and as a result, the path should begin with the path separator.

E.g. when scanning the root ./target/ with the same base, target/bin/busybox should appear in the output as /bin/busybox, not as previously as bin/busybox.

Signed-off-by: Justin Chadwell [email protected]

When base is set, it should appear identically to when we scan the root
filesystem - and as a result, the path should begin with the path
separator.

E.g. when scanning the root `./target/` with the same base,
`target/bin/busybox` should appear in the output as `/bin/busybox`, not
as previously as `bin/busybox`.

Signed-off-by: Justin Chadwell <[email protected]>
@spiffcs
Copy link
Contributor

spiffcs commented Feb 6, 2023

Reran the AC tests since the failure was a connection issue and not a test failure

@spiffcs spiffcs merged commit 6ba5953 into anchore:main Feb 6, 2023
@wagoodman wagoodman added the bug Something isn't working label Feb 9, 2023
GijsCalis pushed a commit to GijsCalis/syft that referenced this pull request Feb 19, 2024
When base is set, it should appear identically to when we scan the root
filesystem - and as a result, the path should begin with the path
separator.

E.g. when scanning the root `./target/` with the same base,
`target/bin/busybox` should appear in the output as `/bin/busybox`, not
as previously as `bin/busybox`.

Signed-off-by: Justin Chadwell <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants