Bug#920772: Why is this bug unclassified instead of confirmed

To: 920772@bugs.debian.org
Subject: Bug#920772: Why is this bug unclassified instead of confirmed
From: kts yvuv <jeckferson@gmail.com>
Date: Fri, 26 Jul 2019 09:52:29 +0630
Message-id: <[🔎] CAL65FyY6LAJmq4CBCF5qFWx8eZ8VC55pV6gFQNvU0h1U7Lcs0A@mail.gmail.com>
Reply-to: kts yvuv <jeckferson@gmail.com>, 920772@bugs.debian.org
References: <154871978683.9599.4054428500100207068.reportbug@mars>

I verify this bug on Debian Buster KDE. It's reproducible.

So it should be marked as confirmed. What criteria does a bts bug need to be listed as confirmed.

Reply to:

Prev by Date: Bug#933022: kxmlrpcclient FTCBFS: missing Build-Depends: qttools5-dev
Next by Date: Bug#933083: baloo-kf5 FTCBFS: missing Build-Depends: qttools5-dev
Previous by thread: Bug#933022: kxmlrpcclient FTCBFS: missing Build-Depends: qttools5-dev
Next by thread: Bug#933083: baloo-kf5 FTCBFS: missing Build-Depends: qttools5-dev
Index(es):
- Date
- Thread