Generating the incremental MAR files for Tor Browser 8.0a10 fails as the script does not know about the new compression format. I guess while we are still in the transitioning period it could check both formats making sure the new format is getting used when recompressing things.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
We are not checking that xz is used in the generated incrementals as this would require extracting them again after they are created. But we are using the mar-tools from the new version, and MAR_OLD_FORMAT is not set, so I think it should get used.
Trac: Status: new to needs_review Keywords: TorBrowserTeam201808 deleted, TorBrowserTeam201808R added
We are not checking that xz is used in the generated incrementals as this would require extracting them again after they are created. But we are using the mar-tools from the new version, and MAR_OLD_FORMAT is not set, so I think it should get used.
After manually extracting one of the generated incremental, I see that the files are indeed compressed with xz.
Works for me. Applied to master (commit 93acbf12b01c83facfb6fb023ceff10d9f601b98). We should file follow-up bugs to adapt this patch during the whole watershed thing (and mark those bugs as child bugs for #26050 (moved)). I'll file the one for 8.0a10->8.0a11 (or 8.0a10-8.5a1 if 8.0a10 will be the last alpha) incremental creation.