I was really astonished that this was the case with gzip and Mac. Brian told me about it after I noticed this here. He also told me to use homebrew gzip and follow the steps on the draft-release.yml for the plugin. I would not use homebrew gzip over the builtin Apple gzip as I also think this could break some things. Just for creating the archives to get correct checksums.
> Am 04.06.2026 um 17:54 schrieb Norman Breau via dev <[email protected]>: > > The builtin gzip utility on MacOS is an Apple implementation and does > not produce a binary equivalent of GNU's gzip so the checksums will not > match if you're trying to compare a product from GNU's gzip (as you > would typically get on a linux machine) with a product produced from > Apple's gzip. > > Mac users could brew install gzip to get a GNU gzip binary and fix > their PATH to use homebrew gzip instead of over Apple's builtin, but > Apple builtin binaries sometimes have custom options or proprietary > options that other builtins rely on so doing that might cause other > problems on your workstation. > > On Thu, 2026-06-04 at 16:58 +0200, Manuel Beck wrote: >> I will need some time to make the verification, because there is an >> issue with gzip on macos. >> >>> Am 04.06.2026 um 15:28 schrieb Manuel Beck >>> <[email protected]>: >>> >>> Where you got "cordova-plugin-inappbrowser-source-6.0.1-atr“ from? >>> When I click on "Download all (ZIP)“ on ATR, I get a "cordova- >>> plugin-inappbrowser-6.0.1.zip“ file, which unpacked, has a same >>> structure like the ".asf-release“ folder inside my local git >>> project. >>> >>> What do you mean with "The verification command from Brians gist >>> does not do that.“? The archives are created by "git archive“ and >>> the check sums by „sha512sum“. After that I compare the check sums >>> by hand and eye. I don’t use a verification command for it. >>> >>>> Am 04.06.2026 um 14:52 schrieb Niklas Merz >>>> <[email protected]>: >>>> >>>> It's just packaged differently. >>>> >>>> ATR puts the files in subdirectory: >>>> >>>> ❯ tree cordova-plugin-inappbrowser-source-6.0.1-atr >>>> cordova-plugin-inappbrowser-source-6.0.1-atr >>>> └── cordova-plugin-inappbrowser-source-6.0.1 >>>> ├── CONTRIBUTING.md >>>> >>>> The verification command from Brians gist does not do that. >>>> >>>> ❯ tree cordova-plugin-inappbrowser-source-6.0.1 >>>> cordova-plugin-inappbrowser-source-6.0.1 >>>> ├── CONTRIBUTING.md >>>> >>>> >>>> On June 4, 2026, Manuel Beck <[email protected]> wrote: >>>>> I followed Brians guide on >>>>> < >>>>> https://gist.github.com/erisu/c45a04c850ef15fc69032e372fa6ec00#e >>>>> xample- >>>>> reproducible-testing> but had to first manually checkout the >>>>> branch >>>>> "draft/6.0.1" to make the steps work. >>>>> >>>>> I compared the check sum of ".asf-release/cordova-plugin- >>>>> inappbrowser- >>>>> 6.0.1.tgz.sha512“ with the one of the release "cordova-plugin- >>>>> inappbrowser-npm-6.0.1.tgz.sha512“, and it was equal. >>>>> >>>>> I compared the check sum of ".asf-release/cordova-plugin- >>>>> inappbrowser- >>>>> source-6.0.1.tar.gz.sha512“ with the one of the release >>>>> "cordova- >>>>> plugin-inappbrowser-source-6.0.1.tar.gz.sha512“ and my was >>>>> „8d483fccd928899eddf08048bf47b03085d04e53c40d2668fac16039ec2c7e >>>>> 7cfcfb0a61f2f42a51e5eb5c39bdca5813aca4bb784533a12d003ed44eb943e >>>>> 186“ >>>>> and your was >>>>> „4eb5b1dc523448cec04ca427c55843a5ceed0d8ba782f3630d8670924b4003 >>>>> c18d2c208d694f68fc6a4b175221eb28c03093f7d49dc931a5bc0b61fd5b73a >>>>> a32“. >>>>> >>>>> I compared the check sum of ".asf-release/cordova-plugin- >>>>> inappbrowser- >>>>> source-6.0.1.zip.sha512“ with the one of the release "cordova- >>>>> plugin- >>>>> inappbrowser-source-6.0.1.zip.sha512“ and my was >>>>> „f396bc513f8167ff0253af7ab4a46a96b3e19ed9c5a9b72b91cd10a9f40f3d >>>>> dc01e9ed446828da0a4db3cbd9815d6d355755acd6218d9b0b0ae65c70e0a20 >>>>> bdf“ >>>>> and your was >>>>> „f5b6dcb3f28c0377e3f78a3917a62449f5db2993f3a9b2bcad9d1d55dd816e >>>>> 4b7f1fe78bcd7852cdc14b42235c5f3e49fa13c90712f0fabe30c873fa20758 >>>>> e41“. >>>>> >>>>> I’m not so familiar with this process, so I don’t know what >>>>> could be >>>>> wrong. >>>>> >>>>>> Am 04.06.2026 um 13:01 schrieb Niklas Merz >>>>>> <[email protected]>: >>>>>> >>>>>> Can you give more detail? To me they look alright. I used ATR >>>>>> for >>>>> the >>>>>> release so there is not really a way to get this wrong. >>>>>> >>>>>> Or did you try to do a reproduceable build? >>>>>> >>>>>> On June 4, 2026, Manuel Beck <[email protected]> >>>>>> wrote: >>>>>>> Some check sums differ: >>>>>>> - cordova-plugin-inappbrowser-source-6.0.1.tar.gz.sha512 >>>>>>> - cordova-plugin-inappbrowser-source-6.0.1.zip.sha512 >>>>>>> >>>>>>> I followed Brians Release Guide for this to test. >>>>>>> >>>>>>> >>>>>>>> Am 04.06.2026 um 11:10 schrieb Niklas Merz >>>>> <[email protected]>: >>>>>>>> >>>>>>>> Can some test this and vote on this to finally get it >>>>>>>> out? >>>>>>>> >>>>>>>> On June 3, 2026, Manuel Beck <[email protected]> >>>>>>>> wrote: >>>>>>>>> Ok, I didn’t know. If this is not relevant for npm than >>>>>>>>> it’s ok >>>>> to >>>>>>>>> bump it for the next major. >>>>>>>>> >>>>>>>>>> Am 03.06.2026 um 23:10 schrieb Niklas Merz >>>>>>> <[email protected]>: >>>>>>>>>> >>>>>>>>>> tests is not included in the npm package. As this is >>>>>>>>>> just a tiny >>>>>>>>> patch >>>>>>>>>> release I don't think it's worth restarting the >>>>>>>>>> release for that >>>>>>> and >>>>>>>>>> wait another 72 hours. The next major can fix this >>>>>>>>>> and should >>>>> come >>>>>>>>>> soon. >>>>>>>>>> >>>>>>>>>> Whats do you think? >>>>>>>>>> >>>>>>>>>> On June 3, 2026, Manuel Beck >>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>> In the plugin exists a „tests" directory, which >>>>>>>>>>> contains a >>>>>>>>>>> package.json and plugin.xml where version 6.0.0 is >>>>>>>>>>> set. I think >>>>>>>>> they >>>>>>>>>>> should be updated also? >>>>>>>>>>> >>>>>>>>>>>> Am 01.06.2026 um 09:25 schrieb >>>>>>>>>>>> [email protected]: >>>>>>>>>>>> >>>>>>>>>>>> Hello Cordova, >>>>>>>>>>>> >>>>>>>>>>>> I'd like to call a vote on releasing the >>>>>>>>>>>> following artifacts >>>>> as >>>>>>>>>>>> Apache Cordova Plugin InAppBrowser 6.0.1. This >>>>>>>>>>>> vote is being >>>>>>>>>>> conducted using an >>>>>>>>>>>> Alpha version of the Apache Trusted Releases >>>>>>>>>>>> (ATR) platform. >>>>>>>>>>>> Please report any bugs or issues to the ASF >>>>>>>>>>>> Tooling team. >>>>>>>>>>>> >>>>>>>>>>>> The release candidate page, including downloads, >>>>>>>>>>>> can be found >>>>>>> at: >>>>>>>>>>>> >>>>>>>>>>>> < >>>>>>>>>>>> https://release-test.apache.org/vote/cordova-plugi >>>>>>>>>>>> n>- >>>>>>>>>>> inappbrowser/6.0.1 >>>>>>>>>>>> >>>>>>>>>>>> The release artifacts are signed with one or more >>>>>>>>>>>> OpenPGP keys >>>>>>>>> from: >>>>>>>>>>>> >>>>>>>>>>>> < >>>>>>>>>>>> https://release-test.apache.org/downloads/cordova/ >>>>>>>>>>>> KEYS> >>>>>>>>>>>> >>>>>>>>>>>> Please review the release candidate and vote >>>>>>>>>>>> accordingly. >>>>>>>>>>>> >>>>>>>>>>>> [ ] +1 Release this package >>>>>>>>>>>> [ ] +0 Abstain >>>>>>>>>>>> [ ] -1 Do not release this package (please >>>>>>>>>>>> provide specific >>>>>>>>>>> comments) >>>>>>>>>>>> >>>>>>>>>>>> You can vote on ATR at the URL above, or manually >>>>>>>>>>>> by replying >>>>> to >>>>>>>>>>> this email. >>>>>>>>>>>> >>>>>>>>>>>> The vote is open for 72 hours. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> Niklas Merz (niklasmerz) >>>>>>>>>>>> >>>>>>>>>>>> This email was sent by [email protected] on >>>>>>>>>>>> the Apache >>>>>>> Trusted >>>>>>>>>>> Releases platform >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>> >>>>> --------------------------------------------------------------- >>>>> ------ >>>>>>>>>>>> To unsubscribe, e-mail: >>>>>>>>>>>> [email protected] >>>>>>>>>>>> For additional commands, e-mail: >>>>>>>>>>>> [email protected] >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>> >>>>> --------------------------------------------------------------- >>>>> ------ >>>>>>>>>>> To unsubscribe, e-mail: >>>>>>>>>>> [email protected] >>>>>>>>>>> For additional commands, e-mail: >>>>>>>>>>> [email protected] >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> >>>>> --------------------------------------------------------------- >>>>> ------ >>>>>>>>> To unsubscribe, e-mail: >>>>>>>>> [email protected] >>>>>>>>> For additional commands, e-mail: >>>>>>>>> [email protected] >>> >>> >>> ------------------------------------------------------------------- >>> -- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
