Your message dated Wed, 18 Nov 2009 20:13:07 -0500
with message-id <19930.1258593...@mixed>
and subject line Re: Bug#379166: imgsizer: man page has broken markup
has caused the Debian Bug report #379166,
regarding imgsizer: man page has broken markup
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.)


-- 
379166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379166
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: imgsizer
Version: 2.7-1
Severity: normal

This is quite easy to see, I think there are several small problems.
Just look at "man imgsizer" to see the problems.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages imgsizer depends on:
ii  file                       4.17-2        Determines file type using "magic"
ii  imagemagick                7:6.2.4.5-0.8 Image manipulation programs
ii  libjpeg-progs              6b-13         Programs for manipulating JPEG fil
ii  python                     2.3.5-11      An interactive high-level object-o

imgsizer recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Reuben Thomas <[email protected]> wrote:

> Package: imgsizer
> Version: 2.7-1
> Severity: normal
> 
> This is quite easy to see, I think there are several small problems.
> Just look at "man imgsizer" to see the problems.

Hi,

Just looking through old bugs.  I don't see anything wrong with the man
page so assume that your database got mangled somehow,  Reopn if it's
still a problem.

Thanks, and sorry it took so long...
Peter
-- 
Peter S. Galbraith, Debian Developer          <[email protected]>
                                 http://people.debian.org/~psg
GPG key 1024/D2A913A1 - 97CE 866F F579 96EE  6E68 8170 35FF 799E


--- End Message ---

Reply via email to