[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#432829: marked as done (O: grokking-the-gimp -- GIMP tutorial book by Carey Bunks (HTML))



Your message dated 
with message-id <20100909203537.4772.11662.mass-bugs-close@merkel.debian.org>
and subject line grokking-the-gimp removed from Debian unstable
has caused the Debian Bug report #432829,
regarding O: grokking-the-gimp -- GIMP tutorial book by Carey Bunks (HTML)
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.)


-- 
432829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432829
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: grokking-the-gimp
Version: 1.0-1
Severity: serious

Hi,

Looking at very old packages in Debian, I came across grokking-the-gimp.
I'd like you to consider not releasing it with lenny:

* it documents gimp as it was in 2000, it's probably confusing for
  users.

* the gimp help has improved and is translated in ~10 languages

* the book is available online anyway (
  http://gimp-savvy.com/BOOK/index.html ) 

* it's in non-free (ok, that's not really a good point ;)

Thank you,
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |


--- End Message ---
--- Begin Message ---
Version: 1.0-2+rm

grokking-the-gimp has been removed from Debian unstable: http://bugs.debian.org/595304

Closing its bugs with a Version higher than the last unstable upload.

More information about this script at:
  http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD


--- End Message ---

Reply to: