Your message dated Tue, 03 Jul 2012 18:12:41 +0800
with message-id <[email protected]>
and subject line Re: Bug#680002: wrong dependency states
has caused the Debian Bug report #680002,
regarding wrong dependency states
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 [email protected]
immediately.)
--
680002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680002
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 6.4
X-debbugs-CC: [email protected]
$ dpkg -l libscim\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=====================-===============-===============-================================================
hi libscim8c2a:i386 1.4.13-5 i386 library for SCIM
platform
$ reportbug --template scim |grep libscim
pn libscim8c2a <none>
--- End Message ---
--- Begin Message ---
On 03.07.2012 05:23, [email protected] wrote:
> Package: reportbug
> Version: 6.4
> X-debbugs-CC: [email protected]
>
> $ dpkg -l libscim\*
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name Version Architecture Description
> +++-=====================-===============-===============-================================================
> hi libscim8c2a:i386 1.4.13-5 i386 library for SCIM
> platform
>
> $ reportbug --template scim |grep libscim
> pn libscim8c2a <none>
I don't see any bug report here. In fact, there's nothing but a bunch
of output from the command line - and the output looks sane. I can
merely guess that maybe there is the possibility that you could be
talking about the same thing you already reported in the invalid bug
679999. Or maybe you are really reporting a bug in dpkg or reportbug?
But it's too much guesswork to be meaningful anyhow.
If you expect us as maintainers to spend time on your bug report please
have at least the minimal courtesy to describe what you were doing and
what happened and why you think that's wrong. You've been around the
FOSS world for years, so I'm sure you should know how to write a proper
bug report. Closing this ticket as invalid as well.
--- End Message ---
