Control: affects -1 - qemu Control: 19.05.2016 17:55, John Paul Adrian Glaubitz wrote: > On 05/19/2016 04:48 PM, Michael Tokarev wrote: >> Actually it is more interesting. This bug is listed in qemu bug list, >> see https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=qemu , AND in >> xfsprogs bug list, see >> https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xfsprogs > > If you look closer that the package is actually "xfsprogs" in both > cases. The bug just shows up in the bug tracker of the qemu package > because it is affected by the bug. Ok, that makes sense. Indeed, while it is listed for qemu, it is marked belonging to xfsprogs. I've never saw this before, and thought it is qemu bug not xfsprogs bug. > If that is no longer the case, we should remove the association > here, i.e. removing "affects src:qemu", but not close the actual > bug because the package which is the actual origin of the bug has > not been fixed yet. > >> I closed it thinking it is in qemu. But I closed it wrongly anyway, >> and that's where I should've been more careful. In qemu there was >> a workaround proposed for this issue, but it hasn't been applied, >> and I thought it has been. So it has already been reopened meanwhile. > > Apparently the workaround has been applied in qemu, otherwise qemu > wouldn't build. I will verify that. I have to build a patched version > of qemu for sparc64 manually anyway. And now this is lack of closer look on my side again. Yes, the workaround has actually been applied, and I hasn't reopened this bug yesterday.. Oh well :)) I was thinking about different bug. Thank you for your patience and explanations! /mjt _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
