<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On Wednesday 22 November 2017 03:16 PM,
      Sahina Bose wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CACjzOvfJnPcFz_gj3KhMWYDX2_OOsRZuCcsX2kykVzkfwy-3QA@mail.gmail.com">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Wed, Nov 22, 2017 at 3:06 PM,
            Niels de Vos <span dir="ltr">&lt;<a target="_blank"
                href="mailto:ndevos@redhat.com" moz-do-not-send="true">ndevos@redhat.com</a>&gt;</span>
            wrote:<br>
            <blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px
              solid rgb(204,204,204);padding-left:1ex"
              class="gmail_quote"><span class="gmail-">On Wed, Nov 22,
                2017 at 10:38:32AM +0530, Aravinda wrote:<br>
                &gt; On Tuesday 21 November 2017 08:29 PM, Niels de Vos
                wrote:<br>
                &gt; &gt; On Tue, Nov 21, 2017 at 11:06:59AM +0530,
                Aravinda wrote:<br>
                &gt; &gt; &gt; Hi Niels,<br>
                &gt; &gt; &gt;<br>
                &gt; &gt; &gt; I over looked the email about 3.12.3
                release.<br>
                &gt; &gt; &gt;<br>
                &gt; &gt; &gt; Please suggest what we can do for this
                package dependency. This is runtime<br>
                &gt; &gt; &gt; dependency for one of the sub feature, if
                it is delaying other things then<br>
                &gt; &gt; &gt; we can remove this dependency from spec
                file.(All features work except<br>
                &gt; &gt; &gt; signing the webhook data).<br>
                &gt; &gt; Hmm, normally new features do not get
                backported to prevent unforseen<br>
                &gt; &gt; problems...<br>
                &gt; &gt;<br>
                &gt; &gt; We have been delayed quite a bit already,
                users are asking for the<br>
                &gt; &gt; packages. If dropping the dependency from the
                .spec does not result in<br>
                &gt; &gt; errors or tracebacks, that would be one
                approach. Can you please confirm<br>
                &gt; &gt; that there are no problems when the package is
                missing?<br>
                &gt; Without the dependency, BZ 1501864 will not work. I
                will start working on<br>
                &gt; the alternate approach without using that library.
                We can remove from<br>
                &gt; dependency list now.<br>
                &gt;<br>
                &gt; @Sahina, Is it possible to wait for this feature
                till 3.12.4 release?<br>
                <br>
              </span>Many thanks Aravinda! I've spoken with Jiffin (one
              of the 3.12 release<br>
              managers) about this as well now. I will revert the change
              in the<br>
              packaging for the CentOS Storage SIG, both the code and
              the dependency.<br>
              <br>
              If a good alternative comes up, and the feature is
              critical to be in<br>
              3.12, we can do an update of the RPMs or wait for 3.12.4+.<br>
            </blockquote>
            <div><br>
            </div>
            <div>We did have a dependency for the eventing integration
              feature slated for oVirt 4.2 on <span class="gmail-">BZ
                1501864. We already missed the beta for oVirt 4.2, so if
                an update of RPMs is possible that would be ideal.<br>
              </span></div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    If we can include the dependency for 3.12.3, I will make sure to
    implement the alternative before 3.12.4 so that we can drop that
    dependency during 3.12.4 release.<br>
    <br>
    <br>
    <blockquote type="cite"
cite="mid:CACjzOvfJnPcFz_gj3KhMWYDX2_OOsRZuCcsX2kykVzkfwy-3QA@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><span class="gmail-"><br>
              </span> </div>
            <blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px
              solid rgb(204,204,204);padding-left:1ex"
              class="gmail_quote">
              <span class="gmail-HOEnZb"><font color="#888888"><br>
                  Niels<br>
                </font></span>
              <div class="gmail-HOEnZb">
                <div class="gmail-h5"><br>
                  <br>
                  &gt; &gt; If there is, we'll just bite the bullet and
                  include python-jws-1.5 in<br>
                  &gt; &gt; the CentOS Storage SIG while keeping an eye
                  on the Fedora package for<br>
                  &gt; &gt; updates. Additional maintainers for this and
                  other packages are much<br>
                  &gt; &gt; wanted.<br>
                  &gt; &gt;<br>
                  &gt; &gt; Niels<br>
                  &gt; &gt;<br>
                  &gt; &gt; &gt;<br>
                  &gt; &gt; &gt;<br>
                  &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; On Monday 20 November 2017 09:59 PM,
                  Niels de Vos wrote:<br>
                  &gt; &gt; &gt; &gt; Hi Aravinda,<br>
                  &gt; &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; &gt; A reply on the questions below is
                  still outstanding. At the moment, I<br>
                  &gt; &gt; &gt; &gt; tend to think that using the most
                  recent python-jwt package from Fedora<br>
                  &gt; &gt; &gt; &gt; is the most reasonable approach.
                  It is a little more maintained there,<br>
                  &gt; &gt; &gt; &gt; and the CentOS Storage SIG can
                  then piggy-back on the coming bugfixes<br>
                  &gt; &gt; &gt; &gt; and updates.<br>
                  &gt; &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; &gt; Is there someone who wants to
                  maintain/assist with watching over<br>
                  &gt; &gt; &gt; &gt; python-jwt for the CentOS Storage
                  SIG?<br>
                  &gt; &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; &gt; Thanks,<br>
                  &gt; &gt; &gt; &gt; Niels<br>
                  &gt; &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; &gt; On Tue, Nov 14, 2017 at 01:22:52PM
                  +0100, Niels de Vos wrote:<br>
                  &gt; &gt; &gt; &gt; &gt; On Tue, Nov 14, 2017 at
                  11:39:46AM +0000, <a
                    href="mailto:jenkins@build.gluster.org"
                    moz-do-not-send="true">jenkins@build.gluster.org</a>
                  wrote:<br>
                  &gt; &gt; &gt; &gt; &gt; &gt; SRC: <a target="_blank"
                    rel="noreferrer"
href="https://build.gluster.org/job/release-new/21/artifact/glusterfs-3.12.3.tar.gz"
                    moz-do-not-send="true">https://build.gluster.org/job/<wbr>release-new/21/artifact/<wbr>glusterfs-3.12.3.tar.gz</a><br>
                  &gt; &gt; &gt; &gt; &gt; &gt; HASH: <a
                    target="_blank" rel="noreferrer"
href="https://build.gluster.org/job/release-new/21/artifact/glusterfs-3.12.3.sha256sum"
                    moz-do-not-send="true">https://build.gluster.org/job/<wbr>release-new/21/artifact/<wbr>glusterfs-3.12.3.sha256sum</a><br>
                  &gt; &gt; &gt; &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; &gt; &gt; &gt; This release is made off
                  jenkins-release-21<br>
                  &gt; &gt; &gt; &gt; &gt; This release adds an
                  additional dependency for the glusterfs-events<br>
                  &gt; &gt; &gt; &gt; &gt; sub-package (<a
                    target="_blank" rel="noreferrer"
                    href="https://review.gluster.org/18519"
                    moz-do-not-send="true">https://review.gluster.org/<wbr>18519</a>).
                  There is no python-jwt<br>
                  &gt; &gt; &gt; &gt; &gt; in RHEL/CentOS-7 so, we'll
                  need to ship (and maintain!) this new package<br>
                  &gt; &gt; &gt; &gt; &gt; in the CentOS Storage SIG.<br>
                  &gt; &gt; &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; &gt; &gt; Will python-jwt become part
                  of RHEL at one point? Which version will be<br>
                  &gt; &gt; &gt; &gt; &gt; included in that case? I
                  would prefer not to have to maintain python-jwt<br>
                  &gt; &gt; &gt; &gt; &gt; longer than necessary, and
                  when RHEL-7 ships this package, it should<br>
                  &gt; &gt; &gt; &gt; &gt; ideally update the version I
                  need to add to the Storage SIG.<br>
                  &gt; &gt; &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; &gt; &gt; [Obviously this delays
                  packaging the update for CentOS.]<br>
                  &gt; &gt; &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; &gt; &gt; Thanks,<br>
                  &gt; &gt; &gt; &gt; &gt; Niels<br>
                  &gt; &gt; &gt; &gt; &gt;
                  ______________________________<wbr>_________________<br>
                  &gt; &gt; &gt; &gt; &gt; packaging mailing list<br>
                  &gt; &gt; &gt; &gt; &gt; <a
                    href="mailto:packaging@gluster.org"
                    moz-do-not-send="true">packaging@gluster.org</a><br>
                  &gt; &gt; &gt; &gt; &gt; <a target="_blank"
                    rel="noreferrer"
                    href="http://lists.gluster.org/mailman/listinfo/packaging"
                    moz-do-not-send="true">http://lists.gluster.org/<wbr>mailman/listinfo/packaging</a><br>
                  &gt; &gt; &gt;<br>
                  &gt; &gt; &gt; --<br>
                  &gt; &gt; &gt; regards<br>
                  &gt; &gt; &gt; Aravinda VK<br>
                  &gt; &gt; &gt;<br>
                  &gt;<br>
                  &gt;<br>
                  &gt; --<br>
                  &gt; regards<br>
                  &gt; Aravinda VK<br>
                  &gt;<br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
regards
Aravinda VK</pre>
  </body>
</html>