[Update Request]: VideoLAN.VLC

[3xploiton3]

What type of update are you requesting?

A new version of an existing package

Current Package Identifier

vlc

Package Version

3.0.21

Please describe the changes you would like to see

https://www.filepuma.com/download/vlc_media_player_64bit_3.0.21-39456/download/

[PckgrBot]

When I checked last the MSI had not been released yet

[3xploiton3]

https://get.videolan.org/vlc/3.0.21/win64/vlc-3.0.21-win64.exe

[PckgrBot]

https://get.videolan.org/vlc/3.0.21/win64/vlc-3.0.21-win64.exe

That is only the exe. The manifests needs to include the MSI.

[stephengillie]

If only the EXE is in the manifest, then for people with the MSI installed, I think the package manager will offer the upgrade, then deny with the message that they have the wrong installer type. This isn't a good UX and should be avoided if possible, especially since switching installer types isn't possible for some users, such as corporate users.

One option could be splitting this pacakge by installer type, with VideoLAN.VLC.EXE and VideoLAN.VLC.MSI - then the EXE version could be updated, and the MSI version could linger. But with the current arrangement, I believe that waiting for the MSI installer is preferrable.

• This package is a community project - is there any way for extra community members to expedite the build and release of the MSI installer? There's obviously a supply of talented engineers demanding this installer, so where is the bottleneck, and how to embiggen it?

[MagicAndre1981]

MSI is not ready yet because of bugs:

The msi package is not published yet, mainly because there are a couple of critical regressions that need to be fixed before that step.
As soon as the fixes are out, we will be able to generate and publish the msi (maybe with a new minor version).

https://code.videolan.org/videolan/vlc/-/issues/28677#note_441953

[hueldoeu]

i have the same problem too. for personal reasons i prefer the MSI over the EXE

[3xploiton3]

[MagicAndre1981]

MSi for 3.0.21 will be skipped and released with 3.0.22

The issue has been recently resolved, but unfortunately, given the delay and the recent internal discussions, the msi publication will probably be skipped for this release.
A 3.0.22 Release Candidate should be out soon.