Gimptalk - Premier Gimp Community: GIMP 2.6.9 released (bugfix release) - Gimptalk - Premier Gimp Community

Jump to content

  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

GIMP 2.6.9 released (bugfix release)

#21 User is offline   bilbo 

  • Member
  • PipPip
  • Group: Members
  • Posts: 45
  • Joined: 26-October 07

Posted 04 July 2010 - 03:20 AM

jolie said:

Does 2.7.1 also force you to uninstall if you install it on another place on your hard drive?

According to the warning I receive when installing, it states the the older version of gimp will be uninstalled even if the new version is installed in a different directory. I confirmed this.
0

#22 User is offline   PhotoComix 

  • GT Senior Moderator
  • Group: Senior Moderators
  • Posts: 11,288
  • Joined: 13-June 05

Posted 04 July 2010 - 10:35 AM

yes it was a warning...just i overlook it supposing was the standard warning about that being a unstable version

i get a few replies from my questions in the dev list (no replies about the dll yet, just about the installers

Quoted from http://www.gimpusers.com/forums/gimp-de ... l#msg58826

Quote

Permalink: 20100703161304.CEF2C1806C11D@a.dev001...
Date: yesterday 06:13 PM
From: photocomix (gimpusers.com)
Subject: ANNOUNCE: GIMP 2.7.1
For not clear reasons the Windows installer of 2.7.1
force unistall of previous version of gimp

Apparently no way to skip unistall, or to cancell unistall/install process

The point is i can't see any reason to force unistall,
the 2 version create 2 different gimp folder in the user directory...and for
the rest seems run well alongside

about the question on ufraw and thor reply

>But be aware then that telling about it might inspire random, more
>clueless, other people to repeat the trick without really knowing what
>they are doing.
>
>--tml

reply is correct but replacing intl.dll with libintl-8.doesn't not create
problem only with ufraw

But with most, almost all "extra" plugins without intl.dll they all (except
Gmic, including Gap-2.6)
abort at loding time with error messages

Only solution i could find is adding back intl.dll,
(not renaming libintl-8, just add bact intl.dll )

Do you think may be a better solution?
Advice all plugin writers to remap all the calls to intl to libintl may be
pratical in long term to port plugins to gimp 2.8

but will not solve any of present problem

As far i could test add back that intl.dll has no practical adverse side
effects

--
photocomix (via www.gimpusers.com)
_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/ ... -developer
↑Back to thread overview
Permalink: 841622763.20100703212038@eternallybor...
Date: yesterday 09:20 PM
From: Jernej Simončič
Subject: ANNOUNCE: GIMP 2.7.1
On Saturday, July 3, 2010, 18:13:04, photocomix wrote:

> For not clear reasons the Windows installer of 2.7.1
> force unistall of previous version of gimp

That is correct.

> Apparently no way to skip unistall, or to cancell unistall/install process

Apparently somebody is claiming things without even trying the
installer.

> The point is i can't see any reason to force unistall,

The point is that the new installer combines 32 and 64-bit GIMP in a
common installer, and once it becomes stable, many people will be
upgrading from 32-bit GIMP 2.6 - it would make no sense for these
people to keep both GIMP 2.6 and 2.8 at the same time, so the new
installer removes the old version first. Since this functionality
needs to be tested before it's deployed in the stable installer, it's
forced in the unstable one (the uninstall will be optional, but I
haven't implemented that yet).

--
< Jernej Simončič >

The more campaigning, the better.
-- O'Brien's First Law of Politics

_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/ ... -developer
↑Back to thread overview
Permalink: 20100703200150.9568C1806C11D@a.dev001...
Date: yesterday 10:01 PM
From: photocomix (gimpusers.com)
Subject: ANNOUNCE: GIMP 2.7.1




>> Apparently no way to skip unistall, or to cancell unistall/install
process
>
>Apparently somebody is claiming things without even trying the
>installer.

Sergey i tried the installer
and i could not see how cancel or skip unistalling
AT THE POINT OF UNISTALLING
Judging from messages i see here
>
>> The point is i can't see any reason to force unistall,
>
>The point is that the new installer combines 32 and 64-bit GIMP in a
>common installer, and once it becomes stable, many people will be
>upgrading from 32-bit GIMP 2.6 -

I didn't saw any option in the 2.7.1 installer for chose 32 or 64 bit
even if my computer support 64 bit i suppose installed, without asking the 32
bit version since all my extra plugin, that were usually not compiled to work
at 64 bit, seem working fine



>.. many people will be
>upgrading from 32-bit GIMP 2.6 -
>it would make no sense for these
>people to keep both GIMP 2.6 and 2.8 at the same time, so the new
>installer removes the old version first. Since this functionality
>needs to be tested before it's deployed in the stable installer, it's
>forced in the unstable one (the uninstall will be optional, but I
>haven't implemented that yet).

Sure?
most (if not all) of third party plugin are not compiled for 64 bit but only
for 32 so many may prefer run a 32 bit gimp even if a 64 bit version could be
available

Or simple they may wish to run a stable version for work...and a beta for the
fun to test new features...




--
photocomix (via www.gimpusers.com)
_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/ ... -developer
↑Back to thread overview
Permalink: 135666757.20100703222902@eternallybor...
Date: yesterday 10:29 PM
From: Jernej Simončič
Subject: ANNOUNCE: GIMP 2.7.1
On Saturday, July 3, 2010, 22:01:50, photocomix wrote:

> Sergey i tried the installer
> and i could not see how cancel or skip unistalling
> AT THE POINT OF UNISTALLING
> Judging from messages i see here

Once the uninstaller is running, there's no way to cancel it - it
wouldn't make any sense anyway, since some files are already deleted
at that time, and there's no way to bring them back. This is why the
installer displays a warning before it starts. However, since you are
apparently the third person who ignored that dialog, I guess I'll have
to bring the checkbox back.

> Sure?
> most (if not all) of third party plugin are not compiled for 64 bit but only
> for 32 so many may prefer run a 32 bit gimp even if a 64 bit version could be
> available

By default, the 64-bit version installs everything needed to run
32-bit plug-ins as well (in fact, the 64-bit version always uses
32-bit TWAIN plug-in, since the 64-bit one doesn't work).

BTW, please fix your e-mail program so that it doesn't strip Re: from
subject.

--
< Jernej Simončič >

_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/ ... -developer
↑Back to thread overview
Permalink: 4C305407.6020300@gmail.com
Date: today 11:27 AM
From: Alec Burgess
Subject: ANNOUNCE: GIMP 2.7.1


One other thing I noticed about the installer is that it does not AFAICT
allow user to chose where to install but forces to:
C:\Program Files\GIMP 2.7\ (on WinXP SP3).

Was this to test some other part of the Win32/Win64 and/or Win7 business
or just oversight?
Regards ... Alec

_______________________________________________
0

#23 User is offline   bilbo 

  • Member
  • PipPip
  • Group: Members
  • Posts: 45
  • Joined: 26-October 07

Posted 04 July 2010 - 03:11 PM

[quote]
One other thing I noticed about the installer is that it does not AFAICT
allow user to chose where to install but forces to:
C:\Program Files\GIMP 2.7\ (on WinXP SP3).

Was this to test some other part of the Win32/Win64 and/or Win7 business
or just oversight?
Regards ... Alec[/quote]
_______________________________________________[/quote]

If one chooses the custom setup, it asks for directory to install.
0

#24 User is offline   paynekj 

  • Member
  • PipPip
  • Group: Members
  • Posts: 317
  • Joined: 01-June 05
  • LocationUK

Posted 05 July 2010 - 04:17 PM

Given the number of people asking for help here after finding the serious bug in 2.6.9:

https://bugzilla.gno...g.cgi?id=622608

how would the moderators feel about changing the title of this thread to include something about not installing 2.6.9?
Kevin
0

#25 User is offline   lylejk 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 1,369
  • Joined: 19-November 07

Posted 05 July 2010 - 04:21 PM

I have Win7, but am running the 32-bit version of GIMP and have just tried this. GIMP 2.6.9 doesn't crash in my system. Might just be an XP thing. Still bad though of course. :)
0

#26 User is offline   lylejk 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 1,369
  • Joined: 19-November 07

Posted 08 July 2010 - 07:32 PM

Looks like more bugs were found since 2.6.10 is now released. lol

:)

Changelog: http://developer.gimp.org/NEWS-2.6
0

#27 User is offline   HeroLink 

  • Member
  • PipPip
  • Group: Members
  • Posts: 92
  • Joined: 24-October 09

Posted 29 August 2010 - 02:33 PM

does it look any different from 2.6.8?
any new features? or is it just bug fixes?
Posted Image
0

#28 User is offline   lylejk 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 1,369
  • Joined: 19-November 07

Posted 06 October 2010 - 01:38 PM

Rod (GIMPChat) just shared with me that GIMP 2.6.11 has just been released. Just a few more bugs have been patched. Probably going to wait til later in the day myself before installing it (to see if you Guinea pigs find something; lol). :)
0

#29 User is offline   lylejk 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 1,369
  • Joined: 19-November 07

Posted 06 October 2010 - 07:36 PM

If you use PSPI, do not install the 2.6.11 update. Trust me. Very disappointed I am (should have listened to my own advice; lol). 2.6.10 still works fine (after re-install). :)
0

Share this topic:


  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic