Bug#822369: fixed in qemu 1:2.6+dfsg-1
Control: reopen -1
Hi Michael!
You closed a bug in src:xfsprogs with a new version of qemu, I don't think this is correct and this bug should therefore be reopened.
While qemu doesn't seem to be affected by this particular issue anymore, I don't think the bug in src:xfsprogs itself has been fixed since there hasn't been a new upload of xfsprogs since February.
Please be more careful when handling of bug reports!
Adrian
Signature · 9 lines
.''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
19.05.2016 17:37, John Paul Adrian Glaubitz пишет:
Quoted 4 lines
Control: reopen -1
Hi Michael!
Quoted 8 lines
You closed a bug in src:xfsprogs with a new version of qemu, I don't think this is correct and this bug should therefore be reopened.
While qemu doesn't seem to be affected by this particular issue anymore, I don't think the bug in src:xfsprogs itself has been fixed since there hasn't been a new upload of xfsprogs since February.
Please be more careful when handling of bug reports!
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
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.
How it is present in both qemu and xfsprogs bug lists, I've no idea :)
/mjt
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 4 lines · Michael Tokarev
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.
Quoted 4 lines
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
Signature · 9 lines
.''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
Control: affects -1 - qemu
Control:
Quoted 9 lines · John Paul Adrian Glaubitz
Quoted 4 lines · Michael Tokarev
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=xfsprogsIf 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.
Quoted 5 lines
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.
Quoted 8 lines
Quoted 4 lines
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
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Control: affects -1 - src:qemu
Quoted 2 lines · On Thu, 19 May 2016 18:07:27 +0300 Michael Tokarev <[email protected]> wrote:
Control: affects -1 - qemu
Control:
That should have been src:qemu; fixed above :)
Regards,
James
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs