Alessio Biancalana 8abacf7205 fix(migrate): use the shared config scripts dir for migration ...

The migrate command introduced a parallel insidedistrobox.ScriptsDir()
that resolved to the old v2 prerelease location
(~/.local/share/distrobox/v2), which was abandoned in 94ae7fa with a
BREAKING CHANGE note. The two resolutions only agree when
DBX_SCRIPTS_DIR is set, which is exactly what the tests do - hiding the
divergence: migrate provisioned and filtered on a different host
directory than the create command mounts into new containers.

- drop insidedistrobox.ScriptsDir(); migrate now provisions and filters
  on c.cfg.ScriptsDir, the same resolution the create command uses
- set ScriptsDir on the recreated container's CreateOptions: it was
  left empty, which made ProvisionScripts("") fail on real runtimes
- make the scripts-mount filter path-boundary aware
- add an end-to-end migration test driving a fake podman runtime:
  v1 inspect JSON in, then compare the recreated container's create
  spec to the known-good v2 layout (scripts mounted from the config
  scripts dir, distrobox.version label set, v1 helper mounts gone)

2026-08-07 16:36:57 +02:00

..

cli

fix: add license headers to new files

2026-08-02 17:40:16 +02:00

inside-distrobox

fix(migrate): use the shared config scripts dir for migration

2026-08-07 16:36:57 +02:00

rootful

chore(license): add GPL-3.0 SPDX header to Go sources (#2173)

2026-07-24 18:08:51 +02:00

userenv

chore(license): add GPL-3.0 SPDX header to Go sources (#2173)

2026-07-24 18:08:51 +02:00