Bug#967012: marked as done (vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern)

From	"Debian Bug Tracking System" <owner@bugs.debian.org>
Newsgroups	linux.debian.bugs.rc
Subject	Bug#967012: marked as done (vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern)
Date	2020-08-16 13:00 +0200
Message-ID	<AEoyl-33e-3@gated-at.bofh.it> (permalink)
References	<AEoyl-33e-5@gated-at.bofh.it> <AzGPf-2oN-11@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Your message dated Sun, 16 Aug 2020 10:50:29 +0000
with message-id <E1k7GFB-000Die-7x@fasolo.debian.org>
and subject line Bug#967012: fixed in vmem 1.8-2
has caused the Debian Bug report #967012,
regarding vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern
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@bugs.debian.org
immediately.)


-- 
967012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967012
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Back to linux.debian.bugs.rc | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Bug#967012: vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern Lucas Nussbaum <lucas@debian.org> - 2020-08-03 13:30 +0200
  Bug#967012: marked as done (vmem: FTBFS: FAIL: match:  out0.log.match:2 did not match pattern) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-08-16 13:00 +0200

csiph-web