[omniORB] regression: omniORB-4.0.6 and omniORBpy-2.6 RPM build failures

[Bastiaan Bakker]

Hi Duncan,

For previous releases of omniORB and omniORBpy it was possible build
RPMs directly from the pristine dist tarball by simply doing:

rpmbuild -ta omniORB-x.y.z.tar.gz

However the omniORB-4.0.6 and omniORBpy-2.6 tar balls break this feature
because their top level directories are omni and omniORBpy rather than
omniORB-4.0.6 and omniORBpy-2.6, causing rpmbuild to try to cd to non
existing directories. 
Could you please create tar balls with the convential TLD names
(omniORB-4.0.6) again? Or, if you really want the alternative names, set
them in the spec files as well by changing '%setup -q' to '%setup -q -n
omni' and '%setup -q -n omniORBpy'?

Thanks!

Bastiaan Bakker
Senior Software Engineer
E.Novation LifeLine Networks bv