Created attachment 115580 [details] Screenshot of 7-zip console showing inner archive SUMMARY Downloaded archive "Kdenlive-18.08.1-w64.7z" for Windows size 167MB to regression test bugs filed for v16. Website instructions for install are: "Now, you don’t need to do anything more to set up. To run Kdenlive, you just have to unzip the downloaded Kdenlive version, and start Kdenlive from kdenlive.exe in kdenlive-windows folder." Top level 7z archive unpacks to a "Kdenlive-18.08.1" root folder containing an obvious install tree of files and dirs. No issue. However, the "Kdenlive-18.08.1" root folder also contains *another* 7z archive "Kdenlive-18.08.1-w64.7z" size 83MB with same name as the original download archive. Since the current install method is manual unzips, this fact is exposed to the user and now confusion sets in. The inner archive also contains an obvious install tree. Is this situation a packaging error and the embedded archive can be ignored or is it required and presumably also should be manually unpacked? If required, there are now two kdenlive.exe files exposed. Which should be executed to launch the app or does it matter? If the inner archive is auto-magically unpacked if needed, that assumes the first user to do so has the Windows perms to create a new tree in within the location of the top level tree - not a good assumption if the top level tree has been installed in C:\Programs.... Install instructions on Website need to account for any inner archives that need user attention at install time. STEPS TO REPRODUCE 1. Download Kdenlive-18.08.1-w64.7z from https://files.kde.org/kdenlive/release/Kdenlive-18.08.1-w64.7z 2. Launch 7-zip console and explore the Kdenlive 7z archive for inner archive as described. 3. OBSERVED RESULT Observe presence of inner archives not mentioned in install instructions. EXPECTED RESULT Install instructions account for inner archives including an instruction to ignore them if not user attention required at install time. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Hello, Thanks for detailed explanations, but when I look at the download folder, I don't see a 167MB file, and the link you give is a 82MB file without the weird structure you are talking about... It's true that I still generate these archives manually, not very professionally with a common pattern (I'm also just fixing a translation install bug breaking languages for 9 months) /o\ Cheers, Vincent
Created attachment 115598 [details] 7z download size diffs 11 Oct to 12 Oct Something changed in the download archive for Windows between my 11 Oct original download and my 12 Oct 2018 followup to this bug report. File Kdenlive-18.08.1-w64.7z was silently changed on the KDE servers. This screenshot shows a 60MB diff between the 11 Oct download of Kdenlive-18.08.1-w64.7z and a 12 Oct download of same (marked "copy2") - note the file dates shown in Windows Exploder. Investigation with the 7z console of "copy2" shows the inner 7z archive reported is no longer present. Possibly an earlier version of the 18.08.1 release archive was made then additional contents added to the tree and then the tree re-archived. But since you were doing this manually, you did not notice a very common goof with Windows Exploder (happens to *everybody*) - you inadvertently mouse select a file or dir and drag it under some random other dir in the Exploder window and don't notice. I've even witnessed this live sitting next to someone and they didn't notice until I pointed it out. So, please indicate a packaging error was made and corrected and we can close this bug. R
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!