All of lore.kernel.org
 help / color / mirror / Atom feed
From: nokia ceph <nokiacephusers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Brad Hubbard <bhubbard-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Ceph Users <ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org>,
	ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Recompiling source code - to find exact RPM
Date: Thu, 23 Mar 2017 18:11:55 +0530	[thread overview]
Message-ID: <CALWuvY_bR7BZLwE+BzCxdWFm+bw4Xx58C1GnFZMkA0JgQMzwmA@mail.gmail.com> (raw)
In-Reply-To: <CAF-wwdFNgsq9+Z2Y3JcBxQoWfUtvtfZ0Y8C3WWArX9fPFVzR5Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2560 bytes --]

Hey brad,

Thanks for the info.

Yea we know that these are test rpm's.

The idea behind my question is if I made any changes in the ceph source
code, then I recompile it. Then I need to find which is the appropriate rpm
mapped to that changed file. If I find the exact RPM, then apply that RPM
in our existing ceph cluster instead of applying/overwriting  all the
compiled rpms.

I hope this cleared your doubt.

Thanks




On Wed, Mar 22, 2017 at 5:47 AM, Brad Hubbard <bhubbard-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:

> Based solely on the information given the only rpms with this specific
> commit in
> them would be here
> https://shaman.ceph.com/builds/ceph/wip-prune-past-intervals-kraken/
> (specifically
> https://4.chacra.ceph.com/r/ceph/wip-prune-past-intervals-kraken/
> 8263140fe539f9c3241c1c0f6ee9cfadde9178c0/centos/7/flavors/default/x86_64/
> ).
> These are test rpms, not official releases.
>
> Note that the branch "wip-prune-past-intervals-kraken" exists only in the
> ceph-ci repo and *not* the main ceph repo and that the particular commit
> above
> does not seem to have made it into the "ceph" repo.
>
> $ git log -S _simplify_past_intervals
> $ git log --grep="_simplify_past_intervals"
> $
>
> Given this commit is not in the ceph repo I would suggest we have never
> shipped
> an official rpm that contains this commit.
>
> It's not totally clear to me exactly what you are trying to achieve, maybe
> you
> could have another go at describing your objective?
>
> On Wed, Mar 22, 2017 at 12:26 AM, nokia ceph <nokiacephusers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> wrote:
> > 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
> >
> >
> > _______________________________________________
> > ceph-users mailing list
> > ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> >
>
>
>
> --
> Cheers,
> Brad
>

[-- Attachment #1.2: Type: text/html, Size: 4156 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

      parent reply	other threads:[~2017-03-23 12:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 14:26 Recompiling source code - to find exact RPM nokia ceph
     [not found] ` <CALWuvY9kyuZgSHeLFwBw86J=tDzX-xc2FPvAQ8Qq__o3s_oodw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-22  0:17   ` Brad Hubbard
     [not found]     ` <CAF-wwdFNgsq9+Z2Y3JcBxQoWfUtvtfZ0Y8C3WWArX9fPFVzR5Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-23 12:41       ` nokia ceph [this message]

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=CALWuvY_bR7BZLwE+BzCxdWFm+bw4Xx58C1GnFZMkA0JgQMzwmA@mail.gmail.com \
    --to=nokiacephusers-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=bhubbard-H+wXaHxf7aLQT0dZR+AlfA@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.