[Bug 20646] gimp: new changes from Debian require merging

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Fri Dec 9 19:23:00 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=20646
Ubuntu (merge) | gimp


daniel.holbach at ubuntu.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|seb128 at ubuntu.com           |daniel.holbach at ubuntu.com
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From daniel.holbach at ubuntu.com  2005-12-09 19:23 UTC -------
 gimp (2.2.9-7ubuntu1) dapper; urgency=low
 .
   * Resynchronized with Debian:
     - app/dialogs/user-install-dialog.c:
       - skip the user installation dialog.
     - data/misc/gimp.desktop.in.in:
       - ship some translations.
 .
 gimp (2.2.9-7) unstable; urgency=low
 .
   * Remove unnecessary build-dependency on libmpeg-dev
   * Remove unnecessary build-dependency on sharutils
   * Remove dependency on xlibs-dev, replace with appropriate -dev
     packages
 .
 gimp (2.2.9-6) unstable; urgency=low
 .
   * Add explicit build-dependency on libfreetype6-dev since gimp
     uses symbols from that library (Closes: #341459)
   * Fix downloading of images in gimp when "verbose=off" is present
     in wgetrc (Closes: #341221)
 .
 gimp (2.2.9-5) unstable; urgency=low
 .
   * Get rid of gcc-3.3 dependency in libgimp2.0-dev, I'm not sure
     why it was there in the first place.
 .
 gimp (2.2.9-4) unstable; urgency=low
 .
   * I found out from Manish Singh that gcc 3.3 generates incredibly
     bloated debugging symbols. So I've switched to building
     gimp with gcc 4.0 on all arches except arm (which FTBFSs with gcc-4.0),
     which now builds with gcc 3.4.


-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the desktop-bugs mailing list