@Ponnuvel, I'm not fully familiar with how ceph deals with rocksdb code so this is mostly observations from my end.
Specifically looking at 15.2.4 for groovy. In https://github.com/ceph/ceph/tree/v15.2.4/src, it appears to pick up rocksdb from a specific commit (rocksdb @ e24b452) that exists in ceph's forked rocksdb repo (https://github.com/ceph/rocksdb @ ceph- octopus-v5.8-1436). The commit for ac304ad doesn't appear to exist in the forked repo, but does exist in the fb repo at https://github.com/facebook/rocksdb/. I'm not sure what the process is but it seems that ac304ad needs to get into ceph's forked repo. Perhaps a cherry-pick with a PR is enough. James probably knows the process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894453 Title: Building Ceph packages with RelWithDebInfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1894453/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
