[Bug 1131127] Review Request: safelease - legacy locking mechanism for VDSM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

Michael Schwendt <bugs.michael@xxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(vdelima@xxxxxxxxx |
                   |m)                          |
                   |needinfo?(bugs.michael@gmx. |
                   |net)                        |



--- Comment #14 from Michael Schwendt <bugs.michael@xxxxxxx> ---
Directory ownership has been corrected after comment 7 (bottom).

My question in comment 11 is based on the fact that vdsm places safelease in a
different directory. It does not know about the new location chosen by this
package. Unless it will be patched to look there. That's why I want to know
what is the plan?

> Vitor, why don't we install safelease in the same location
> (%{_libexecdir}/%{vdsm_name}/safelease) and sign the package
> as Obsolote vdsm **

It certainly must not obsolete vdsm.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review




[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]