What to do if upstream doesn't fix bug?

Rahul Sundaram metherid at gmail.com
Tue May 14 17:03:22 UTC 2013


On Tue, May 14, 2013 at 12:59 PM, Mattia Verga wrote:

> Hello,
> actually kde-partitionmanager is completely broken in F18, F19 and
> rawhide. This is because KDE have switched to udisks2 backend and it seems
> to me that solid (a component of kdelibs) doesn't correctly parse udisks2
> output.
> I've opened a bug [1] in KDE tracker six months ago, but it doesn't seem
> to get too much attention... I also opened a bug in bugzilla as a
> reminder/note for everyone that hits this problem [2]. So, what
> alternatives have I? Should I retire kde-partitionmanager from F18 and
> above? Or can I leave it completely broken in functionality with the hope
> that the bug will eventually be fixed?

If you are unable to do the work required and upstream is unresponsive in
general, orphan the package or retire it.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20130514/fadcc9f3/attachment.html>

More information about the devel mailing list