public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: 822369@bugs.debian.org
Subject: Bug#822369: fixed in qemu 1:2.6+dfsg-1
Date: Thu, 19 May 2016 18:07:27 +0300	[thread overview]
Message-ID: <573DD6AF.5020608@msgid.tls.msk.ru> (raw)
In-Reply-To: <573DD3CC.6040608@physik.fu-berlin.de>

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@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-05-19 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 14:37 Bug#822369: fixed in qemu 1:2.6+dfsg-1 John Paul Adrian Glaubitz
2016-05-19 14:48 ` Michael Tokarev
2016-05-19 14:55   ` John Paul Adrian Glaubitz
2016-05-19 15:07     ` Michael Tokarev [this message]
2016-05-29 10:48       ` James Clarke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=573DD6AF.5020608@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=822369@bugs.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox