From: nokia ceph <nokiacephusers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ceph Users <ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org>,
ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Recompiling source code - to find exact RPM
Date: Tue, 21 Mar 2017 19:56:13 +0530 [thread overview]
Message-ID: <CALWuvY9kyuZgSHeLFwBw86J=tDzX-xc2FPvAQ8Qq__o3s_oodw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 623 bytes --]
Hello,
I made some changes in the below file on ceph kraken v11.2.0 source code as
per this article
https://github.com/ceph/ceph-ci/commit/wip-prune-past-intervals-kraken
..src/osd/PG.cc
..src/osd/PG.h
Is there any way to find which rpm got affected by these two files. I
believe it should be ceph-osd-11.2.0-0.el7.x86_64.rpm . Can you confirm
please ?
I failed to find it from the ceph.spec file.
Could anyone please guide me the right procedure to check this.
The main intention is that if we find the exact rpm affected by these
files, we can simply overwrite it with the old rpm.
Awaiting for comments.
Thanks
[-- Attachment #1.2: Type: text/html, Size: 990 bytes --]
[-- Attachment #2: Type: text/plain, Size: 178 bytes --]
_______________________________________________
ceph-users mailing list
ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
next reply other threads:[~2017-03-21 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 14:26 nokia ceph [this message]
[not found] ` <CALWuvY9kyuZgSHeLFwBw86J=tDzX-xc2FPvAQ8Qq__o3s_oodw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-22 0:17 ` Recompiling source code - to find exact RPM Brad Hubbard
[not found] ` <CAF-wwdFNgsq9+Z2Y3JcBxQoWfUtvtfZ0Y8C3WWArX9fPFVzR5Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-23 12:41 ` nokia ceph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALWuvY9kyuZgSHeLFwBw86J=tDzX-xc2FPvAQ8Qq__o3s_oodw@mail.gmail.com' \
--to=nokiacephusers-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.