There are two versions of the Oh-My-Posh application after a Winget update #6028

litmowise · 2024-12-17T05:09:05Z

litmowise
Dec 17, 2024

Code of Conduct

I agree to follow this project's Code of Conduct

What happened?

1.After upgrading Oh-My-Posh using winget upgrade, there were two versions of Oh-My-Posh.

2.Use the winget uninstall JanDeDobbeleer.OhMyPosh --all-versions command to uninstall and reinstall, wait for the new version to be released and then use winget to update again, there will still be two versions of the problem!

Theme

theme: agnoster.minimal
config: default

What OS are you seeing the problem on?

Windows

Which shell are you using?

powershell

Log output

XIN@LAPTOP-LITMOWISE  ~  oh-my-posh debug --plain

Version: 24.13.1

Shell: pwsh (7.5.0-rc.1)

Prompt:

XIN@LAPTOP-LITMOWISE  ~ 

Segments:

ConsoleTitle(false)                       -   0 ms
Status(false)                             -   1 ms
Root(false)                               -   0 ms
Session(true)                             -   0 ms
Path(true)                                -   1 ms
Git(false)                                -  12 ms
Text(true)                                -   0 ms

Run duration: 33.8797ms

Cache path: C:\Users\XIN\AppData\Local\oh-my-posh

Config path: C:\Users\XIN\AppData\Local\Programs\oh-my-posh\themes\agnoster.minimal.omp.json

Logs:

[DEBUG] 13:02:29.039 command.go:execute:989 → debug mode enabled
[DEBUG] 13:02:29.057 debug.go:40 → config set using POSH_THEME: C:\Users\XIN\AppData\Local\Programs\oh-my-posh\themes\agnoster.minimal.omp.json
[TRACE] 13:02:29.057 debug.go() - 0s
[TRACE] 13:02:29.058 load.go:Load() - 1.0688ms
[TRACE] 13:02:29.058 debug.go() - 1.0688ms
[DEBUG] 13:02:29.059 debug.go:52 → plain mode enabled
[TRACE] 13:02:29.059 terminal.go() - 0s
[DEBUG] 13:02:29.059 terminal.go:59 → loading cache file: C:\Users\XIN\AppData\Local\oh-my-posh\omp.cache
[TRACE] 13:02:29.059 terminal.go(C:\Users\XIN\AppData\Local\oh-my-posh\omp.cache) - 0s
[TRACE] 13:02:29.059 terminal.go() - 0s
[DEBUG] 13:02:29.059 terminal.go:59 → loading cache file: C:\Users\XIN\AppData\Local\oh-my-posh\omp.cache.6592ef83-d04f-409a-98ad-e5d48354d6ad
[DEBUG] 13:02:29.059 terminal.go:59 → loading cache key: prompt_count_cache
[TRACE] 13:02:29.059 terminal.go(C:\Users\XIN\AppData\Local\oh-my-posh\omp.cache.6592ef83-d04f-409a-98ad-e5d48354d6ad) - 523.8µs
[TRACE] 13:02:29.059 terminal.go:Init() - 0s
[TRACE] 13:02:29.059 terminal.go() - 0s
[DEBUG] 13:02:29.059 terminal.go:Init:67 → C:\Users\XIN
[TRACE] 13:02:29.059 terminal.go:Init() - 0s
[TRACE] 13:02:29.059 debug.go() - 1.0457ms
[TRACE] 13:02:29.059 init.go:Init() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[DEBUG] 13:02:29.059 home.go:Home:26 → C:\Users\XIN
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[DEBUG] 13:02:29.059 cache.go:loadCache:60 → XIN
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[DEBUG] 13:02:29.059 cache.go:loadCache:61 → LAPTOP-LITMOWISE
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[TRACE] 13:02:29.059 cache.go:loadCache() - 0s
[DEBUG] 13:02:29.059 cache.go:loadCache:71 → NO DATA
[TRACE] 13:02:29.059 cache.go:loadCache(SHLVL) - 0s
[DEBUG] 13:02:29.059 debug.go:61 → terminal program: Windows Terminal
[DEBUG] 13:02:29.059 debug.go:61 → terminal shell: shell
[DEBUG] 13:02:29.059 config.go:MakeColors:58 → NO DATA
[TRACE] 13:02:29.059 config.go:MakeColors(OMP_CACHE_DISABLED) - 0s
[TRACE] 13:02:29.059 colors_windows.go:GetAccentColor(HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM\ColorizationColor) - 0s
[DEBUG] 13:02:29.060 colors_windows.go:GetAccentColor:19 → ColorizationColor(DWORD): 0xC40078D4
[TRACE] 13:02:29.060 colors.go:SetAccentColor() - 520µs
[TRACE] 13:02:29.060 colors.go:MakeColors() - 520µs
[TRACE] 13:02:29.060 debug.go:PrintDebug() - 0s
[DEBUG] 13:02:29.060 debug.go:PrintDebug:16 → 7.5.0-rc.1
[TRACE] 13:02:29.060 debug.go:PrintDebug(POSH_SHELL_VERSION) - 0s
[DEBUG] 13:02:29.060 debug.go:72 → segment: Title
[TRACE] 13:02:29.060 engine.go:getTitleTemplateText() - 0s
[TRACE] 13:02:29.060 primary.go:needsPrimaryRightPrompt() - 0s
[DEBUG] 13:02:29.060 terminal.go:CursorPosition:583 → 2
[TRACE] 13:02:29.060 terminal.go:CursorPosition(POSH_CURSOR_LINE) - 0s
[DEBUG] 13:02:29.060 terminal.go:CursorPosition:587 → 1
[TRACE] 13:02:29.060 terminal.go:CursorPosition(POSH_CURSOR_COLUMN) - 0s
[TRACE] 13:02:29.060 primary.go:writePrimaryPrompt() - 0s
[TRACE] 13:02:29.060 primary.go:writePrimaryPrompt() - 0s
[TRACE] 13:02:29.060 segment.go:Execute() - 0s
[TRACE] 13:02:29.060 segment.go:Execute() - 0s
[DEBUG] 13:02:29.060 home.go:Home:26 → C:\Users\XIN
[DEBUG] 13:02:29.060 home.go:Home:26 → C:\Users\XIN
[TRACE] 13:02:29.060 terminal.go:DirMatchesOneOf() - 0s
[TRACE] 13:02:29.060 terminal.go:DirMatchesOneOf() - 0s
[DEBUG] 13:02:29.060 segment.go:Execute:110 → segment: Text
[DEBUG] 13:02:29.060 segment.go:Execute:110 → segment: Status
[TRACE] 13:02:29.060 terminal.go:DirMatchesOneOf() - 0s
[DEBUG] 13:02:29.060 segment.go:Execute:112 → no toggles found
[DEBUG] 13:02:29.060 segment.go:Execute:110 → segment: Session
[DEBUG] 13:02:29.060 segment.go:Execute:112 → no toggles found
[TRACE] 13:02:29.060 segment.go:Execute() - 0s
[TRACE] 13:02:29.060 status.go:Enabled() - 0s
[DEBUG] 13:02:29.060 session.go:activeSSHSession:31 → NO DATA
[TRACE] 13:02:29.060 session.go:activeSSHSession(SSH_CONNECTION) - 0s
[DEBUG] 13:02:29.060 status.go:formatStatus:45 → {{ .Code }}
[DEBUG] 13:02:29.060 session.go:activeSSHSession:31 → NO DATA
[DEBUG] 13:02:29.060 home.go:Home:26 → C:\Users\XIN
[TRACE] 13:02:29.060 session.go:activeSSHSession(SSH_CLIENT) - 0s
[TRACE] 13:02:29.060 terminal.go:DirMatchesOneOf() - 0s
[DEBUG] 13:02:29.060 segment.go:Execute:110 → segment: Path
[TRACE] 13:02:29.060 segment.go:Execute() - 0s
[DEBUG] 13:02:29.060 segment.go:Execute:112 → no toggles found
[DEBUG] 13:02:29.060 home.go:Home:26 → C:\Users\XIN
[TRACE] 13:02:29.060 terminal.go:DirMatchesOneOf() - 0s
[DEBUG] 13:02:29.060 segment.go:Execute:110 → segment: Root
[DEBUG] 13:02:29.060 segment.go:Execute:112 → no toggles found
[DEBUG] 13:02:29.060 path.go:147 → display_cygpath: false
[TRACE] 13:02:29.060 path.go:setPaths() - 0s
[TRACE] 13:02:29.060 path.go:setPaths() - 0s
[TRACE] 13:02:29.060 path.go:setPaths() - 0s
[TRACE] 13:02:29.060 path.go:setPaths() - 0s
[TRACE] 13:02:29.060 path.go:parsePath() - 0s
[TRACE] 13:02:29.060 root.go:Enabled() - 0s
[TRACE] 13:02:29.060 segment.go:Execute() - 0s
[DEBUG] 13:02:29.060 path.go:setMappedLocations:557 → mapped_locations_enabled: true
[DEBUG] 13:02:29.060 path.go:setMappedLocations:558 → 
[DEBUG] 13:02:29.060 path.go:setMappedLocations:559 → 
[DEBUG] 13:02:29.060 home.go:Home:26 → C:\Users\XIN
[TRACE] 13:02:29.060 clean.go:Clean() - 0s
[TRACE] 13:02:29.060 path.go:normalize() - 0s
[DEBUG] 13:02:29.060 home.go:Home:26 → C:\Users\XIN
[TRACE] 13:02:29.060 terminal.go:DirMatchesOneOf() - 0s
[DEBUG] 13:02:29.060 segment.go:Execute:110 → segment: Git
[DEBUG] 13:02:29.060 segment.go:Execute:112 → no toggles found
[TRACE] 13:02:29.060 scm.go:hasCommand() - 0s
[DEBUG] 13:02:29.060 path.go:setMappedLocations:565 → mapped_locations: map[]
[TRACE] 13:02:29.060 clean.go:Clean() - 0s
[TRACE] 13:02:29.060 path.go:normalize() - 0s
[TRACE] 13:02:29.060 clean.go:Clean() - 0s
[TRACE] 13:02:29.060 path.go:normalize() - 0s
[TRACE] 13:02:29.060 path.go:parsePath() - 0s
[TRACE] 13:02:29.060 path.go:parsePath() - 0s
[TRACE] 13:02:29.060 path.go:parsePath() - 0s
[TRACE] 13:02:29.060 path.go:setStyle() - 0s
[DEBUG] 13:02:29.060 path.go:colorizePath:734 → cycle: []
[DEBUG] 13:02:29.060 path.go:getFolderSeparator:267 → NO DATA
[DEBUG] 13:02:29.060 path.go:getFolderSeparator:269 →  
[DEBUG] 13:02:29.060 path.go:colorizePath:737 → cycle_folder_separator: false
[DEBUG] 13:02:29.060 path.go:colorizePath:738 → %s
[DEBUG] 13:02:29.061 path.go:colorizePath:740 → %s
[DEBUG] 13:02:29.061 path.go:colorizePath:741 → %s
[DEBUG] 13:02:29.061 path.go:colorizePath:742 → %s
[TRACE] 13:02:29.061 path.go:Enabled() - 0s
[TRACE] 13:02:29.061 path.go:Enabled() - 0s
[TRACE] 13:02:29.061 path.go:Enabled() - 0s
[TRACE] 13:02:29.061 status.go:formatStatus({{ .Code }}) - 1.0415ms
[DEBUG] 13:02:29.061 status.go:Enabled:37 → always_enabled: false
[TRACE] 13:02:29.061 segment.go:resolve(plain) - 0s
[TRACE] 13:02:29.061 segment.go:resolve(plain) - 0s
[TRACE] 13:02:29.061 segment.go:string({{ .UserName }}@{{ .HostName }} ) - 519.9µs
[TRACE] 13:02:29.061 segment.go:resolve(plain) - 0s
[DEBUG] 13:02:29.061 terminal_windows.go:DirIsWritable:216 → not current user or in group
[DEBUG] 13:02:29.061 terminal_windows.go:DirIsWritable:216 → current user is member of S-1-5-32-544
[DEBUG] 13:02:29.061 win32_windows.go:isWriteable:271 ↓
    WRITE_DAC
    WRITE_OWNER
    SYNCHRONIZE
    DELETE
    READ_CONTROL
[DEBUG] 13:02:29.061 terminal_windows.go:DirIsWritable:216 → user has write access
[TRACE] 13:02:29.061 path.go:Enabled() - 519.9µs
[TRACE] 13:02:29.062 segment.go:string(<transparent></> {{ .Path }} ) - 524.4µs
[TRACE] 13:02:29.062 segment.go:resolve(plain) - 0s
[DEBUG] 13:02:29.072 terminal.go:HasCommand:323 → C:\Program Files\Git\cmd\git.exe
[TRACE] 13:02:29.072 terminal.go:HasCommand(git.exe) - 11.8913ms
[TRACE] 13:02:29.072 scm.go:hasCommand(git.exe) - 11.8913ms
[DEBUG] 13:02:29.072 git.go:shouldDisplay:328 → fetch_bare_info: false
[DEBUG] 13:02:29.073 terminal.go:HasParentFilePath:446 → C:\Users\XIN
[TRACE] 13:02:29.073 terminal.go:HasParentFilePath(C:\Users\XIN) - 999.4µs
[ERROR] 13:02:29.073 git.go:shouldDisplay:338 → CreateFile .git: The system cannot find the file specified.
[TRACE] 13:02:29.073 git.go:shouldDisplay(.git) - 999.4µs
[TRACE] 13:02:29.073 segment.go:resolve(plain) - 0s
[TRACE] 13:02:29.073 segment.go:string( ) - 0s
[TRACE] 13:02:29.073 segment.go:resolve(plain) - 0s
[TRACE] 13:02:29.073 engine.go:applyPowerShellBleedPatch() - 0s
[TRACE] 13:02:29.073 primary.go:Primary() - 0s
[TRACE] 13:02:29.073 debug.go:PrintDebug() - 0s
[TRACE] 13:02:29.073 debug.go:PrintDebug() - 0s

Answered by JanDeDobbeleer

Dec 28, 2024

@litmowise this is a winget bug. When using upgrade it doesn't respect the previously used scope and installs system wide. You can see this because it pops UAC, which install (default to user) doesn't do. I created an issue on their end.

Evidence

Install v27.17.0

winget install JanDeDobbeleer.OhMyPosh -v 24.17.0

2024-12-28 17:24:43.631 [CLI ] Starting installer selection.
2024-12-28 17:24:43.631 [CLI ] Installer [X64,msi,Machine,] is current best choice
2024-12-28 17:24:43.631 [CLI ] Installer [X64,msi,User,] is better [strong] than [X64,msi,Machine,] due to: Scope
2024-12-28 17:24:43.631 [CLI ] Installer [X64,msi,User,] is current best choice
2024-12-28 17:24:43.631 [CLI ] Installer [X6…

View full answer

pattacini · 2024-12-17T07:16:32Z

pattacini
Dec 17, 2024

Probably related to this is the fact that I'm unable to upgrade oh-my-posh via winget.
Here's the failure:

A newer version was found, but the install technology is different from the current version installed. Please uninstall the package and install the newer version.

I managed to upgrade using oh-my-posh straight away:

oh-my-posh upgrade
oh-my-posh version
24.13.1

However, winget is still messed up, apparently:

winget upgrade
...
Oh My Posh   JanDeDobbeleer.OhMyPosh  24.12.0  24.13.1  winget
...

2 replies

JanDeDobbeleer Dec 17, 2024
Maintainer

@pattacini this is unrelated to the issue above. winget has a different database, it doesn't query the executable's version. I can't solve that (did look for it). In your case, you should have only uninstalled and install again using winget as it does state the underlying installer technology changed (which is true).

pattacini Dec 17, 2024

Oh I see, thank you!
It worked out indeed.

JanDeDobbeleer · 2024-12-17T07:57:22Z

JanDeDobbeleer
Dec 17, 2024
Maintainer

@litmowise could it be you installed as admin/user first then switched? Because an MSI installer can't be used for the two contexts.

9 replies

litmowise Dec 17, 2024
Author

Is this caused by the winget upgrade command update, or is the program itself designed this way with two sets of environment variables (I always install as the current user)?

litmowise Dec 17, 2024
Author

I have a feeling it's a UAC popup problem with the Oh-My-Posh program after updating with the winget upgrade command, and clicking yes immediately adds another set of system environment variables!

JanDeDobbeleer Dec 17, 2024
Maintainer

is the program itself designed this way with two sets of environment variables

@litmowise no, it understands that context of system install and user.

have a feeling it's a UAC popup problem with the Oh-My-Posh

it shouldn't do that as this implies you're installing system wide

litmowise Dec 17, 2024
Author

is the program itself designed this way with two sets of environment variables

@litmowise no, it understands that context of system install and user.

have a feeling it's a UAC popup problem with the Oh-My-Posh

it shouldn't do that as this implies you're installing system wide

I see, so after updating Oh-My-Posh with winget, the UAC popup adds system environment variables if you click Yes, and not if you click otherwise.

JanDeDobbeleer Dec 17, 2024
Maintainer

@litmowise allow me to validate why it pops UAC though. It shouldn't.

EdiTurn · 2024-12-25T08:55:25Z

EdiTurn
Dec 25, 2024

Have the same issue, and confirm it happens with the versions using msi.

16 replies

JanDeDobbeleer Dec 28, 2024
Maintainer

@litmowise but also in Windows settings? Because that's what I can't reproduce. And that's still the only setting that needs to be correct.

litmowise Dec 28, 2024
Author

@JanDeDobbeleer using the winget uninstall JanDeDobbeleer.OhMyPosh --all-versions command has completely uninstalled it, the two version entries do not exist, and the user environment variables and system environment variables are completely removed.

but also in Windows settings? What that means, I don't understand.

JanDeDobbeleer Dec 28, 2024
Maintainer

Confirmed to also have 2 entries when using winget, but not when using the standalone installer....

JanDeDobbeleer Dec 28, 2024
Maintainer

@litmowise this is a winget bug. When using upgrade it doesn't respect the previously used scope and installs system wide. You can see this because it pops UAC, which install (default to user) doesn't do. I created an issue on their end.

Evidence

Install v27.17.0

winget install JanDeDobbeleer.OhMyPosh -v 24.17.0

2024-12-28 17:24:43.631 [CLI ] Starting installer selection.
2024-12-28 17:24:43.631 [CLI ] Installer [X64,msi,Machine,] is current best choice
2024-12-28 17:24:43.631 [CLI ] Installer [X64,msi,User,] is better [strong] than [X64,msi,Machine,] due to: Scope
2024-12-28 17:24:43.631 [CLI ] Installer [X64,msi,User,] is current best choice
2024-12-28 17:24:43.631 [CLI ] Installer [X64,msi,User,] is better [strong] than [X86,msi,Machine,] due to: Scope
2024-12-28 17:24:43.631 [CLI ] Installer [X64,msi,User,] is better [weak] than [X86,msi,User,] due to: Machine Architecture
2024-12-28 17:24:43.631 [CLI ] Installer [X64,msi,User,] is better [strong] than [Arm64,msi,Machine,] due to: Scope
2024-12-28 17:24:43.631 [CLI ] Installer [Arm64,msi,User,] is better [strong] than [X64,msi,User,] due to: Machine Architecture
2024-12-28 17:24:43.631 [CLI ] Installer [Arm64,msi,User,] is current best choice
2024-12-28 17:24:43.631 [CLI ] Completed installer selection.
2024-12-28 17:24:43.631 [CLI ] Selected installer Architecture: 4
2024-12-28 17:24:43.631 [CLI ] Selected installer URL: https://github.com/JanDeDobbeleer/oh-my-posh/releases/download/v24.17.0/install-arm64.msi
2024-12-28 17:24:43.631 [CLI ] Selected installer InstallerType: msi
2024-12-28 17:24:43.631 [CLI ] Selected installer Scope: User

Upgrade to latest

winget upgrade JanDeDobbeleer.OhMyposh

2024-12-28 17:26:57.914 [CLI ] Starting installer selection.
2024-12-28 17:26:57.914 [CLI ] Installer [X64,msi,Machine,] is current best choice
2024-12-28 17:26:57.914 [CLI ] Installer [X64,msi,User,] not applicable: Installer scope does not match currently installed scope: User != Machine
2024-12-28 17:26:57.914 [CLI ] Installer [X64,msi,Machine,] is better [weak] than [X86,msi,Machine,] due to: Machine Architecture
2024-12-28 17:26:57.914 [CLI ] Installer [X86,msi,User,] not applicable: Installer scope does not match currently installed scope: User != Machine
2024-12-28 17:26:57.914 [CLI ] Installer [Arm64,msi,Machine,] is better [strong] than [X64,msi,Machine,] due to: Machine Architecture
2024-12-28 17:26:57.914 [CLI ] Installer [Arm64,msi,Machine,] is current best choice
2024-12-28 17:26:57.914 [CLI ] Installer [Arm64,msi,User,] not applicable: Installer scope does not match currently installed scope: User != Machine
2024-12-28 17:26:57.914 [CLI ] Completed installer selection.
2024-12-28 17:26:57.914 [CLI ] Selected installer Architecture: 4
2024-12-28 17:26:57.914 [CLI ] Selected installer URL: https://github.com/JanDeDobbeleer/oh-my-posh/releases/download/v24.17.1/install-arm64.msi
2024-12-28 17:26:57.914 [CLI ] Selected installer InstallerType: msi
2024-12-28 17:26:57.914 [CLI ] Selected installer Scope: Machine

Answer selected by litmowise

litmowise Dec 29, 2024
Author

@JanDeDobbeleer ok, thank you!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

There are two versions of the Oh-My-Posh application after a Winget update #6028

{{title}}

Replies: 3 comments 27 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

There are two versions of the Oh-My-Posh application after a Winget update #6028

litmowise Dec 17, 2024

Code of Conduct

What happened?

Theme

What OS are you seeing the problem on?

Which shell are you using?

Log output

Evidence

Install v27.17.0

Replies: 3 comments · 27 replies

pattacini Dec 17, 2024

JanDeDobbeleer Dec 17, 2024 Maintainer

pattacini Dec 17, 2024

JanDeDobbeleer Dec 17, 2024 Maintainer

litmowise Dec 17, 2024 Author

litmowise Dec 17, 2024 Author

JanDeDobbeleer Dec 17, 2024 Maintainer

litmowise Dec 17, 2024 Author

JanDeDobbeleer Dec 17, 2024 Maintainer

EdiTurn Dec 25, 2024

JanDeDobbeleer Dec 28, 2024 Maintainer

litmowise Dec 28, 2024 Author

JanDeDobbeleer Dec 28, 2024 Maintainer

JanDeDobbeleer Dec 28, 2024 Maintainer

Evidence

Install v27.17.0

Upgrade to latest

litmowise Dec 29, 2024 Author

litmowise
Dec 17, 2024

Replies: 3 comments 27 replies

pattacini
Dec 17, 2024

JanDeDobbeleer Dec 17, 2024
Maintainer

JanDeDobbeleer
Dec 17, 2024
Maintainer

litmowise Dec 17, 2024
Author

litmowise Dec 17, 2024
Author

JanDeDobbeleer Dec 17, 2024
Maintainer

litmowise Dec 17, 2024
Author

JanDeDobbeleer Dec 17, 2024
Maintainer

EdiTurn
Dec 25, 2024

JanDeDobbeleer Dec 28, 2024
Maintainer

litmowise Dec 28, 2024
Author

JanDeDobbeleer Dec 28, 2024
Maintainer

JanDeDobbeleer Dec 28, 2024
Maintainer

litmowise Dec 29, 2024
Author