No Code Attached Yet bug
avatar Fedik
Fedik
28 Oct 2021

Patch updates is malfunction for 4.x series, and /media folder is outdated.
Everyone who installed patch update since 4.0.0 have outdated /media folder.

Temporary work around: install 4.0.x-Stable-Update_Package .

The issue comes from a reason that we have moved source of /media folder to /build/media_source/ and so build script does not see difference.

$command = $systemGit . ' diff tags/' . $previousTag . ' ' . $remote . ' --name-status > diffdocs/' . $version . '.' . $num;

We need another solution for /media diff.
Maybe need to compare content of /media itself, somehow. And not relay on GIT history.

avatar Fedik Fedik - open - 28 Oct 2021
avatar joomla-cms-bot joomla-cms-bot - change - 28 Oct 2021
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 28 Oct 2021
avatar Fedik Fedik - change - 28 Oct 2021
The description was changed
avatar Fedik Fedik - edited - 28 Oct 2021
avatar laoneo
laoneo - comment - 9 Nov 2021

Or just include media also in patch updates.

avatar Fedik Fedik - change - 20 Nov 2021
Labels Added: Release Blocker
avatar Fedik Fedik - labeled - 20 Nov 2021
avatar Fedik
Fedik - comment - 20 Nov 2021

We have a problem. Everyone who made patch update since 4.0.x to 4.0.4 will not be able to update to next release.
Because after #35388 merged they did not received a JS files that comes with that PR (and old JS files was removed).
On next update they will get JS error.

I set it as release blocker, we need a solution before 4.0.5
Ping @wilsonge

avatar richard67
richard67 - comment - 20 Nov 2021

This will have happened only if they used upload and update and the smaller packages but not when using live update, which always fetches the big update package for update from any version, as far as I know.

avatar Fedik Fedik - change - 20 Nov 2021
Labels Removed: Release Blocker
avatar Fedik Fedik - unlabeled - 20 Nov 2021
avatar Fedik
Fedik - comment - 20 Nov 2021

@richard67 thanks for info ?

avatar zero-24 zero-24 - change - 20 Nov 2021
Labels Added: Release Blocker
avatar zero-24 zero-24 - labeled - 20 Nov 2021
avatar zero-24
zero-24 - comment - 20 Nov 2021

Should still be a RB so so make sure our releases are not broken.

avatar richard67
richard67 - comment - 20 Nov 2021

Yes, just not as urgent as it seemed, but it needs to be fixed of course.

avatar wilsonge
wilsonge - comment - 28 Nov 2021

For now I've decided to not ship the patch packages with Joomla 4.0.5 as this isn't going to be a trivial problem. There's a new flag in the build script to handle that.

avatar richard67
richard67 - comment - 25 Dec 2021

Meanwhile I've found a bit time to check how our build script works (because I need that knowledge for another thing I'm working on).

For creating the "small" update packages, it uses "git diff" on tags. This would only work if we would have all the build results checked in into our sources (which would be silly).

So we have to compare folders and not tags.

But the build script also deletes stuff in the temporary build folder (with name = some number, located in build/tmp) after having created the full package and before creating the update package.

So we can't just compare the content of that temporary folder with the same of another version (and if we could it would still mean we have to run a build for every version which we compare.

We have the same problem when we want to generate the list of deleted files and folders.

The solution up to now for the latter was to compare folders into which a full installation package has been unpacked before.

The same could be done in the build script, too. It could download and unpack the full packages and then use git diff --name-status <folder1> <folder2> to compare these folders in the same way as it now compares tags, but with the difference that it now includes all results the build script, too.

I will try to find the time to work on such a solution.

avatar PhilETaylor
PhilETaylor - comment - 18 Jan 2022

@zero-24 added the Release Blocker label on 20 Nov 2021

Im guessing, as there have been releases since then, that this is not a release blocker after all and can have that label removed.

avatar zero-24
zero-24 - comment - 18 Jan 2022

@PhilETaylor This is correct after that release an "workaround" has been implemented by not delivering said broken update packages. Still this is an issue that should be looked at and fixed, will take down the label for now while it is defenitly not a ideal solution at all.

avatar zero-24 zero-24 - change - 18 Jan 2022
Labels Removed: Release Blocker
avatar zero-24 zero-24 - unlabeled - 18 Jan 2022
avatar Hackwar Hackwar - change - 22 Feb 2023
Labels Added: bug
avatar Hackwar Hackwar - labeled - 22 Feb 2023

Add a Comment

Login with GitHub to post a comment