Your message dated Mon, 21 May 2012 21:35:20 -0400
with message-id <[email protected]>
and subject line Re: Bug#673897: gimp: can't export to XCF
has caused the Debian Bug report #673897,
regarding gimp: can't export to XCF
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.)
--
673897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673897
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gimp
Version: 2.8.0-2
Severity: normal
After the ill-thought split of saving into "save" and "export", "save"
offers XCF with a few decorations. Ok, while I thoroughly disagree with
this decision, I can kind of understand it.
However, when trying to "export" and selecting XCF, gimp instead returns
an error message. It allows 50ish formats, including XCF-analogues like
PSD, but mysteriously can't export its very own format.
Besides muddling the interface (can't do things the way most users expect,
the way any program I can think of works), this also disallows binding
Export to ^S to restore sanity.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (150, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gimp depends on:
ii gimp-data 2.8.0-2
ii libaa1 1.4p5-39
ii libatk1.0-0 2.4.0-2
ii libbabl-0.1-0 0.1.10-1
ii libbz2-1.0 1.0.6-1
ii libc6 2.13-32
ii libcairo2 1.12.2-2
ii libdbus-1-3 1.5.12-1
ii libdbus-glib-1-2 0.98-1
ii libexif12 0.6.20-2
ii libfontconfig1 2.9.0-5
ii libfreetype6 2.4.9-1
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libgegl-0.2-0 0.2.0-2
ii libgimp2.0 2.8.0-2
ii libglib2.0-0 2.32.3-1
ii libgs9 9.05~dfsg-5
ii libgtk2.0-0 2.24.10-1
ii libgudev-1.0-0 175-3.1
ii libjasper1 1.900.1-13
ii libjpeg8 8d-1
ii liblcms1 1.19.dfsg-1+b2
ii libmng1 1.0.10-3
ii libpango1.0-0 1.30.0-1
ii libpng12-0 1.2.49-1
ii libpoppler-glib6 0.16.7-3
ii librsvg2-2 2.36.1-1
ii libtiff4 3.9.6-5
ii libwebkitgtk-1.0-0 1.8.1-2
ii libwmf0.2-7 0.2.8.4-10
ii libx11-6 2:1.4.99.901-2
ii libxcursor1 1:1.1.13-1
ii libxext6 2:1.3.1-2
ii libxfixes3 1:5.0-4
ii libxmu6 2:1.1.1-1
ii libxpm4 1:3.5.10-1
ii python 2.7.2-10
ii python-gtk2 2.24.0-3
ii python2.7 2.7.3~rc2-2.1
ii zlib1g 1:1.2.7.dfsg-2
Versions of packages gimp recommends:
ii ghostscript 9.05~dfsg-5
Versions of packages gimp suggests:
ii gimp-data-extras 1:2.0.1-3
ii gimp-help-en [gimp-help] 2.6.1-1
ii gvfs-backends <none>
ii libasound2 1.0.25-3
-- no debconf information
--- End Message ---
--- Begin Message ---
This is a feature, not a bug. The gimp developers have thought a lot
about this, and I'm sure they won't want to change the current behavior.
http://gui.gimp.org/index.php/Save_%2B_export_specification
--- End Message ---
