I was concerned about the native rocksdb jni library than the Mac generated meta files :)
The release build script should include -Drocks_tools_native to build it. Probably better to repeat the build on a Linux box instead. BTW, tools/fault-injection-service build is not managed by Maven. I'll skip it from the binary tarball. On Sun, Mar 23, 2025 at 10:26 AM Tsz-Wo Nicholas Sze <szets...@gmail.com> wrote: > > ... this is caused by using Mac's built-in tar, ... > > The ._ (and also .DS_Store) files are the mac meta files. We probably > should exclude them in maven assembly or remove them by a script/maven > plugin ? > > Tsz-Wo > > > On Sun, Mar 23, 2025 at 3:37 AM Attila Doroszlai <adorosz...@apache.org> > wrote: > > > Thanks Wei-Chiu for working on the release. > > > > > Source code and binary tarball: > > > https://dist.apache.org/repos/dist/release/ozone/2.0.0-rc0/ > > > > RC should be added in dist/dev, not dist/release. > > > > > I built on a Mac M3. Does it make any difference if I build on an x86 > > Linux? > > > > On Linux, the binary tarball created on Mac has an extra item for each > > file, like: > > > > ozone-2.0.0/._README.md > > ozone-2.0.0/README.md > > ozone-2.0.0/._NOTICE.txt > > ozone-2.0.0/NOTICE.txt > > > > I think this is caused by using Mac's built-in tar, and can be fixed > > by installing and using GNU tar. The RM guide vaguely mentions this, > > clarification proposed in HDDS-12672. > > > > HDDS-12662 and HDDS-12668 are upgrade test bugs, but I think we should > > fix them for 2.0. PRs are ready. > > > > .editorconfig and .run (new items for developers, added in HDDS-12365) > > are missing from the source tarball. I don't think it's a blocker, > > but it can be fixed easily (HDDS-12671). If a new RC is needed, we > > can add this one, too. > > > > -Attila > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org > > For additional commands, e-mail: dev-h...@ozone.apache.org > > > > >
