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. 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. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@xxxxxxxxxx `. `' Freie Universitaet Berlin - glaubitz@xxxxxxxxxxxxxxxxxxx `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
