On 06/30/2011 07:37 PM, Genes MailLists wrote:
On 06/30/2011 12:16 PM, Jeff Spaleta wrote:
> On Thu, Jun 30, 2011 at 3:51 AM, Jiri Moskovcak<jmoskovc(a)redhat.com> wrote:
>> - I was afraid, that it would be against some Fedora policy ;) Then just
>> the rawhide..
>
>
> Okay if this isn't coming to F15, can you provide the sufficient
> instructions on how to revert the libreport packages from F15 updates
> testing so that the packages that require report-gtk will work
> properly again.
>
> I'm not pointing fingers. I just want to know, from you, the package
> maintainer, how to back out of the semi brokenness introduced by the
> malformed obsoletes in the updates-testing package that is now a dead
> end if
> this isn't going to firm up as an official update.
>
>
Am I misremembering? I recall an official update which broke sealert -
the libreport fix from updates testing never installed as it was broken
and never was pushed stable.
So now F15 stock with official stable updates only, has a broken
sealert (maybe other things).
Whats the way forward from here in F15?
gene/
1. bumping the version of the report-gtk package should do the trick - I
already contacted the maintainer and ask him to do - as this seems to
work for rawhide:
https://bugzilla.redhat.com/show_bug.cgi?id=715373#c55
2. fix the yum so it can handle this situation better
3. last resort would be asking rel-engs to remove the broken libreport
from the stable repositories (if it's even possible)
J.