Bug#663574: marked as done (PTS: incorrectly reports 'neither part of unstable or experimental')
Your message dated Wed, 31 Oct 2012 07:22:35 +0000
with message-id <20121031072235.GG12985@master.debian.org>
and subject line PTS: incorrectly reports 'neither part of unstable or experimental'
has caused the Debian Bug report #663574,
regarding PTS: incorrectly reports 'neither part of unstable or experimental'
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.)
--
663574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663574
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: PTS: incorrectly reports 'neither part of unstable or experimental'
- From: Andreas Beckmann <debian@abeckmann.de>
- Date: Mon, 12 Mar 2012 14:03:58 +0100
- Message-id: <20120312130358.27692.96921.reportbug@cake.ae.cs.uni-frankfurt.de>
Package: qa.debian.org
Severity: normal
Hi,
the PTS incorrectly reports
This package is neither part of unstable nor experimental.
even if the package is in experimental:
http://packages.qa.debian.org/q/qpopper.html
oldstable 4.0.9.dfsg-1
stable 4.0.9.dfsg-1.2
exp 4.1~a4+dfsg-1
Andreas
--- End Message ---
--- Begin Message ---
- To: 663574-done@bugs.debian.org
- Subject: PTS: incorrectly reports 'neither part of unstable or experimental'
- From: Bart Martens <bartm@debian.org>
- Date: Wed, 31 Oct 2012 07:22:35 +0000
- Message-id: <20121031072235.GG12985@master.debian.org>
At this time the package qpopper is not in unstable and not in experimental.
The problem could have been a duplicate of bug 640806 and then we can continue
tracking the problem with bug 640806.
--- End Message ---
Reply to: