So jardiff isn't reporting any differences but diffoscope does, see
https://gist.github.com/mdedetrich/172c369af2a4ac39e2b21f3ad8e8daf6 . The
diff appears to be coming from files such as NOTICE and LICENSE, so I think
that the issue is that maybe you published from the latest main rather than
the tag when there was a difference in these files? Here is also the
relevant output of sbt-reproducible-diff for Scala 2.13
https://gist.github.com/mdedetrich/08e02b787d4f712d104fba1d47252864

Locally I am checking from git tag c1bab5a116b7f4c654f9d7ae3886a344e0f3771e



On Tue, Aug 8, 2023 at 9:43 AM Matthew de Detrich <
matthew.dedetr...@aiven.io> wrote:

> I am getting a mismatch in jvm binary jars with sbt-reproducible-builds so
> I will block the release until I confirm its either an issue on my end or
> the binaries are fixed
>
> -1
>
> On Sat, Aug 5, 2023 at 10:23 PM PJ Fanning <fannin...@apache.org> wrote:
>
>> Hello Pekko Community,
>>
>> This is a call for a vote to release Apache Pekko(incubating)
>> Management version 1.0.0-RC2.
>>
>> There are some license fixes since 1.0.0-RC1.
>>
>> The discussion thread:
>>
>> https://lists.apache.org/thread/g1hhcsvzbd8o1zdholds41k0jrknrx3q
>>
>> The release candidate:
>>
>>
>> https://dist.apache.org/repos/dist/dev/incubator/pekko/MANAGEMENT-1.0.0-RC2/
>>
>> This release has been signed with a PGP key available here:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS
>>
>> Release Notes:
>>
>>
>> https://pekko.apache.org/docs/pekko-management/current/release-notes/index.html
>>
>> Git branch for the release:
>>
>> https://github.com/apache/incubator-pekko-management/tree/v1.0.0-RC2
>> Git commit ID: c1bab5a116b7f4c654f9d7ae3886a344e0f3771e
>>
>> Please download, verify, and test.
>>
>> We have also staged jars in the Apache Nexus Repository. These were
>> built with the same code
>> as appears in this Source Release Candidate. We would appreciate if
>> users could test with these too.
>> If anyone finds any serious problems with these jars, please also
>> notify us on this thread.
>>
>> https://repository.apache.org/content/groups/staging/org/apache/pekko/
>>
>> In sbt, you can add this resolver.
>>
>> resolvers += "Apache Pekko Staging" at
>> "https://repository.apache.org/content/groups/staging";
>>
>>
>> The VOTE will pass if we have more positive votes than negative votes
>> and there must be a minimum of 3 approvals from Pekko PPMC members.
>> Anyone voting in favour of the release, could you please provide a
>> list of the checks you have done?
>> The vote will be left open until 21:00 UTC on 8 August 2023.
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove with the reason
>>
>> To learn more about Apache Pekko, please see https://pekko.apache.org/
>>
>> Checklist for reference:
>>
>> [ ] Download links are valid.
>> [ ] Checksums and signatures.
>> [ ] LICENSE/NOTICE files exist
>> [ ] No unexpected binary files
>> [ ] Source files have ASF headers
>> [ ] Can compile from source
>>
>> To compile from the source, please refer to:
>>
>>
>> https://github.com/apache/incubator-pekko-management/blob/main/README.md#building-from-source
>>
>> Some notes about verifying downloads can be found at:
>>
>> https://pekko.apache.org/download.html#verifying-downloads
>>
>>
>> Here is my +1.
>>
>> Thanks,
>>
>> PJ Fanning (Apache Pekko PPMC member)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org
>> For additional commands, e-mail: dev-h...@pekko.apache.org
>>
>>
>
> --
>
> Matthew de Detrich
>
> *Aiven Deutschland GmbH*
>
> Immanuelkirchstraße 26, 10405 Berlin
>
> Amtsgericht Charlottenburg, HRB 209739 B
>
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>
> *m:* +491603708037
>
> *w:* aiven.io *e:* matthew.dedetr...@aiven.io
>


-- 

Matthew de Detrich

*Aiven Deutschland GmbH*

Immanuelkirchstraße 26, 10405 Berlin

Amtsgericht Charlottenburg, HRB 209739 B

Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen

*m:* +491603708037

*w:* aiven.io *e:* matthew.dedetr...@aiven.io

Reply via email to