Bug#868067: marked as done (/usr/bin/uscan: hard-coded uupdate script name for different behavior)

[Debian Bug Tracking System]

Your message dated Sat, 12 Aug 2017 15:18:52 -0400
with message-id <20170812191852.wsydtwjfu7hq75wi at tc4.so-net.ne.jp>
and subject line Why "uupdate -f"? Because v4
has caused the Debian Bug report #868067,
regarding /usr/bin/uscan: hard-coded uupdate script name for different behavior
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.)


-- 
868067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868067
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Vincent Danjean <vdanjean at debian.org>
Subject: /usr/bin/uscan: hard-coded uupdate script name for different behavior
Date: Tue, 11 Jul 2017 20:47:44 +0200
Size: 6975
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20170812/18efc05e/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Osamu Aoki <osamu at debian.org>
Subject: Why "uupdate -f"? Because v4
Date: Sat, 12 Aug 2017 15:18:52 -0400
Size: 2300
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20170812/18efc05e/attachment-0001.mht>