Skip to content

dir: Don't pass temp repo path to flatpak_dir_log during initial pull - #6713

Merged
swick merged 1 commit into
mainfrom
bbhtt/log-system-pulls
Jun 23, 2026
Merged

swick merged 1 commit into
mainfrom
bbhtt/log-system-pulls

Conversation

@bbhtt

@bbhtt bbhtt commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator

During a system install with the system helper enabled, the initial network pull goes to a temporary repo and then via pull local from that repo to the final system repo while during user install there is only one pull from network to the final repo.

c672c55 set the logger to use the temporary repo path as installation but the history command afc87ad since the same day filters the initial pull out as the installation name will never match the temporary path.

This causes the initial pull operation to be never show up in flatpak history when using system installs while they work for user installs as INSTALLATION=user.

This is presumably also broken for custom installations as they will similarly not match the temp repo path.

So don't pass the path at all to flatpak_dir_log and we can later fall back via flatpak_dir_get_name_cached() which sets the correct INSTALLATION for system installs ie. INSTALLATION=system.

This also allows us to remove the workaround of adding two different expected history outputs from ad1ff6d as both branches log the pull.

Without system helper flatpak install needs to be executed as priviledged to operate on system install so the initial pull was always logged correctly for that branch.

During a system install with the system helper enabled, the initial
network pull goes to a temporary repo and then via pull local from that
repo to the final system repo while during user install there is only
one pull from network to the final repo.

c672c55 set the logger to use the temporary repo path as installation
but the history command afc87ad since the same day filters the initial
pull out as the installation name will never match the temporary path.

This causes the initial pull operation to be never show up in flatpak
history when using system installs while they work for user installs as
`INSTALLATION=user`.

This is presumably also broken for custom installations as they
will similarly not match the temp repo path.

So don't pass the path at all to flatpak_dir_log and we can later
fall back via flatpak_dir_get_name_cached() which sets the correct
`INSTALLATION` for system installs ie. `INSTALLATION=system`.

This also allows us to remove the workaround of adding two different
expected history outputs from ad1ff6d as both branches log the pull.

Without system helper `flatpak install` needs to be executed as
priviledged to operate on system install so the initial pull was
always logged correctly for that branch.
@bbhtt
bbhtt force-pushed the bbhtt/log-system-pulls branch from 3aca69e to 98e8d84 Compare June 19, 2026 02:39
@bbhtt

bbhtt commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator Author

I checked system installs now show the pull in history command after this, haven't checked custom installations but I assume they should be ok too.

@swick
swick added this pull request to the merge queue Jun 23, 2026
Merged via the queue into main with commit 5fcf748 Jun 23, 2026
16 of 17 checks passed
@swick
swick deleted the bbhtt/log-system-pulls branch June 23, 2026 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants