[Bug 453855] Review Request: globus-openssl-module - Globus Toolkit - Globus OpenSSL Module Wrapper

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=453855


Orcan 'oget' Ogetbil <oget.fedora at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |oget.fedora at gmail.com
         AssignedTo|nobody at fedoraproject.org    |oget.fedora at gmail.com
               Flag|                            |fedora-review?

Bug 453855 depends on bug 453850, which changed state.

Bug 453850 Summary: Review Request: globus-openssl - Openssl Library (virtual GPT glue package)
https://bugzilla.redhat.com/show_bug.cgi?id=453850

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|ASSIGNED                    |CLOSED
         Resolution|                            |NEXTRELEASE



--- Comment #7 from Orcan 'oget' Ogetbil <oget.fedora at gmail.com>  2009-04-24 13:39:36 EDT ---
- Package builds in rawhide:
   http://koji.fedoraproject.org/koji/taskinfo?taskID=1319436

! BuildRequires: globus-openssl-devel >= 1   on the main package and
  Requires:       globus-openssl-devel >= 1 on the devel package seem
unnecessary. They are not harmful though (they are picked up by other deps).

? Actually could you explain me those other Requires' in the devel package? The
header file globus_openssl.h does not #include anything other than
"globus_common.h". Where do the other dependencies come from? I bet it is a
magical globus thingy, but I'd like to learn the mechanism.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.