Jabberd in 2.2 needs some care. Dennis already done the work for server in commits: be9ecccc30a57e2ac099f8ee9ceaec70f508b42d 4a285c8c76a4b8e1960306c8a4c6cb7bd2697904 4c6745758a93ae519cc3857c67703a313bf8140e 7aa107431836e3451c865700ad3225b56226dfcb f3c277f05b0bd36428da319652cf6f1f4055bc9c 0c7b8d77390a2505395feca4f10f26b4bc7f3fdf We should do it in proxy code base as well.
rel-eng ticket #38658 to include jabberd-2.2.5 dependencies into the Red Hat Network Proxy v5.3 channels
Mirek, is there anything needed for jabberd on Proxy or is this neatly handled by the fact that jabberd 2.2+ is in EPEL and in Fedoras?
I just made this bug to track it, and since QA installed proxy dozen times (and users in spacewalk) I assume it works without problem. Moving to MODIFIED.
Moving ON_QA. Please use the Spacewalk 1.2 release candidate yum repo at http://koji.spacewalkproject.org/spacewalk/split/spacewalk-5E/server/spacewalk-5E-1.2/$basearch/os http://koji.spacewalkproject.org/spacewalk/split/spacewalk-f12/server/spacewalk-f12-1.2/$basearch/os http://koji.spacewalkproject.org/spacewalk/split/spacewalk-f13/server/spacewalk-f13-1.2/$basearch/os http://koji.spacewalkproject.org/spacewalk/split/spacewalk-f14/server/spacewalk-f14-1.2/$basearch/os (depending on your OS) to verify the bugzilla.
With Spacewalk 1.2 released, marking as CLOSED CURRENTRELEASE. https://www.redhat.com/archives/spacewalk-list/2010-November/msg00111.html