Bug#811952: marked as done (x265: FTBFS with GCC 6: unable to find string literal operator)

Mon Feb 8 00:06:04 UTC 2016

Your message dated Mon, 8 Feb 2016 01:03:35 +0100
with message-id <20160208000335.GE29577 at ramacher.at>
and subject line Re: Bug#811952: x265: FTBFS with GCC 6: unable to find string literal operator
has caused the Debian Bug report #811952,
regarding x265: FTBFS with GCC 6: unable to find string literal operator
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)

-- 
811952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811952
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Martin Michlmayr <tbm at hpe.com>
Subject: x265: FTBFS with GCC 6: unable to find string literal operator
Date: Tue, 19 Jan 2016 19:59:18 -0800
Size: 6567
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20160208/232aa071/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Sebastian Ramacher <sramacher at debian.org>
Subject: Re: Bug#811952: x265: FTBFS with GCC 6: unable to find string literal operator
Date: Mon, 8 Feb 2016 01:03:35 +0100
Size: 8656
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20160208/232aa071/attachment-0001.mht>