* Casey Connor [01-05-17 23:46]:

Hi -- I'm using GIMP 2.9.5, the "edge", via the otto-kesselgulasch-gimp-edge PPA.

Is it appropriate to report bugs for that version at bugzilla.gnome.org, or is it too alpha for bug reports?

If it's appropriate, what version should I pick from the menu: "git master", or "unspecified" (and then specify in the description, obviously)? The version options only go to 2.9.4.

https://www.gimp.org/bugs/

(paka)Patrick Shanahan       Plainfield, Indiana, USA          @ptilopteri
http://en.opensuse.org    openSUSE Community Member    facebook/ptilopteri
Photos: http://wahoo.no-ip.org/gallery2      Registered Linux User #207535                    
Photos: http://wahoo.no-ip.org/piwigo		 @ http://linuxcounter.net

On Fri, Jan 6, 2017 at 7:37 AM, Casey Connor wrote:

Hi -- I'm using GIMP 2.9.5, the "edge", via the otto-kesselgulasch-gimp-edge PPA.

Is it appropriate to report bugs for that version at bugzilla.gnome.org, or is it too alpha for bug reports?

Not too alpha.

If it's appropriate, what version should I pick from the menu: "git master",

That one.

Alex

On 01/06/2017 05:37 AM, Casey Connor wrote:

Hi -- I'm using GIMP 2.9.5, the "edge", via the otto-kesselgulasch-gimp-edge PPA.

Hi Casey,

Is it appropriate to report bugs for that version at bugzilla.gnome.org, or is it too alpha for bug reports?

yes, it is appropriate.

Even more than appropriate, it is essential to GIMP development: If you do not report bugs in a development version, then it is likely they stay in for all eternity unless someone else happens to encounter the same same.

This is under the assumption that you are going to update GIMP from this repository quite frequently, as changes happen every day.

If you are afraid to report bugs other people have reported already, then use the bug tracker links below to search for the issue you have encountered before reporting a bug. But even if you find one, you may still be able to contribute additional information, especially if comments in the bug ask for this.

The question remaining would be where to report the bugs, as both the gimp-edge repository maintainer and GIMP itself maintain a bug tracker, respectively:

https://bugs.launchpad.net/~otto-kesselgulasch

https://bugzilla.gnome.org/browse.cgi?product=GIMP

The GIMP developers prefer when bugs encountered in third-party builds (this includes Linux distros, too) are reported in the bug trackers specific to that build.

From there, it can either be forwarded by the build and/or tracker maintainers is deemed necessary. It can also be done by the users reporting the bugs, either to ensure the bug is known in general or if the maintainers turn out to be unresponsive. Please include a reference to the other bugs in such cases.

For build made from the code as-is, it almost doesn't matter where the bug is reported. But there can still be platform-specific issues the build maintainer is much more aware of than the GIMP developers are.

For modified builds, getting the build maintainer to do an active part in bug research and triaging is crucial.

If it's appropriate, what version should I pick from the menu: "git master", or "unspecified" (and then specify in the description, obviously)? The version options only go to 2.9.4.

An important thing to realize is that there is not "one" 2.9.5, but many - this version number is used by the current development master branch, and so every build made from there currently uses the 2.9.5 version number. So using "git master" is appropriate.

The 2.9.5 version serves as an indication of what we are dealing with in general - a build made from the development branch past the 2.9.4 release.

The commit id can become interesting if we're trying to figure out if a bug may still be present, or if it is supposed to be gone already. The commit id is shown in the empty image window and in the Help -> About dialog, and looks like "commit 8a15064" with whatever commit id your build was based on.

Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD

On Sun, Jan 8, 2017 at 8:23 AM, Casey Connor wrote:

That PPA bug tracker apparently has no gimp bugs present in it (and only one other bug from 2.5 years ago), so perhaps I can safely skip it and report to the main tracker

We suggest that you do exactly that :)

Re: feature requests -- my understanding (per gimp.org/bugs) is that I should propose things on this list before submitting FR bugs. Assuming I've searched for existing FRs and done the related homework, is that correct?

That would be nice :)

Alex

Dear Developers,

I'm going slightly mad.

Why do you need libpng >= 1.6.25, and lcms2 >= 2.7 in order to build Gimp 2.9.5 - commit 36ebe03770fd8b87102e95cd6c45b194a45a8ba3?

Thank you

Thorsten

On Wed, 2017-01-11 at 18:40 +0100, Thorsten Stettin wrote:

Dear Developers,

I'm going slightly mad.

Why do you need libpng >= 1.6.25, and lcms2 >= 2.7 in order to build  Gimp 2.9.5 - commit 36ebe03770fd8b87102e95cd6c45b194a45a8ba3?

Probably for bug fixes.

The general rule is that we can depend on what is in debian testing.

Regards,
Mitch

Dear Developers,

I'm going slightly mad.

Why do you need libpng >= 1.6.25, and lcms2 >= 2.7 in order to build Gimp 2.9.5 - commit 36ebe03770fd8b87102e95cd6c45b194a45a8ba3?

Thank you

Thorsten

On 01/11/2017 12:40 PM, Thorsten Stettin wrote:

Dear Developers,

I'm going slightly mad.

Why do you need libpng >= 1.6.25, and lcms2 >= 2.7 in order to build Gimp 2.9.5 - commit 36ebe03770fd8b87102e95cd6c45b194a45a8ba3?

libpng:
https://bugzilla.gnome.org/show_bug.cgi?id=765850

lcms: https://bugzilla.gnome.org/show_bug.cgi?id=736701

Best, Elle

On 01/11/2017 06:40 PM, Thorsten Stettin wrote:

Why do you need libpng >= 1.6.25, and lcms2 >= 2.7 in order to build Gimp 2.9.5 - commit 36ebe03770fd8b87102e95cd6c45b194a45a8ba3?

libpng 1.6.25:

https://git.gnome.org/browse/gimp/commit/configure.ac?id=a5073ad9289f7e05ef38d2ce99dc71e91983b434

https://bugzilla.gnome.org/show_bug.cgi?id=765850

lcms2 2.7

https://git.gnome.org/browse/gimp/commit/configure.ac?id=0ce364ee4dd2200e6607a4575af0cc657600afc9

https://bugzilla.gnome.org/show_bug.cgi?id=736701

Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD

Hello,

For LCMS, see https://bugzilla.gnome.org/show_bug.cgi?id=736701.

Alex

11 янв. 2017 г. 8:46 PM пользователь "Thorsten Stettin" < thorsten.stettin@gmail.com> написал:

Dear Developers,

I'm going slightly mad.

Why do you need libpng >= 1.6.25, and lcms2 >= 2.7 in order to build Gimp 2.9.5 - commit 36ebe03770fd8b87102e95cd6c45b194a45a8ba3?

Thank you

Thorsten

_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp- developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list

Thorsten Stettin (thorsten.stettin@gmail.com) wrote:

Why do you need libpng >= 1.6.25, and lcms2 >= 2.7 in order to build Gimp 2.9.5 - commit 36ebe03770fd8b87102e95cd6c45b194a45a8ba3?

Libpng is due to security issues:

commit a5073ad9289f7e05ef38d2ce99dc71e91983b434 Author: Michael Natterer
Date: Mon Oct 31 09:36:15 2016 +0100

configure.ac: require libpng 1.6.25
Addresses bug #765850, and probably avoids a gazillion of vulnerabilities in the versions since the ancient 1.2.37 we required before.

For libcms2 this is due to some rounding errors that affected some blending modes in gimp:

commit 0ce364ee4dd2200e6607a4575af0cc657600afc9 Author: Michael Natterer
Date: Thu Sep 15 12:52:20 2016 +0200

configure.ac, app: require liblcms2 >= 2.7
and add an lcms2 runtime version check to app/sanity.c
Fixes:
Bug 736701 - LCMS2 rounding errors cause problems with certain GIMP blend modes

I hope this helps, Simon

simon@budig.de              http://simon.budig.de/

Am 11.01.2017 um 18:50 schrieb Michael Schumacher:

On 01/11/2017 06:40 PM, Thorsten Stettin wrote:

Why do you need libpng >= 1.6.25, and lcms2 >= 2.7 in order to build Gimp 2.9.5 - commit 36ebe03770fd8b87102e95cd6c45b194a45a8ba3?

libpng 1.6.25:

https://git.gnome.org/browse/gimp/commit/configure.ac?id=a5073ad9289f7e05ef38d2ce99dc71e91983b434

https://bugzilla.gnome.org/show_bug.cgi?id=765850

lcms2 2.7

https://git.gnome.org/browse/gimp/commit/configure.ac?id=0ce364ee4dd2200e6607a4575af0cc657600afc9

https://bugzilla.gnome.org/show_bug.cgi?id=736701

I understand, but I need to provide packages for Ubuntu LTS versions at least. I'll do my very best regarding backporting. Shit!

Cheers

Thorsten

Lao-Tse sagt: Nichtstun ist besser, als mit viel Mühe nichts zu schaffen.
Und er sagt auch: Ich habe drei Schätze, die ich hüte und hege.
Der eine ist die Liebe, der zweite ist die Genügsamkeit, der dritte ist die Demut.
Nur der Liebende ist mutig, nur der Genügsame ist großzügig, nur der Demütige ist fähig zu herrschen.

On 01/11/2017 06:59 PM, Thorsten Stettin wrote:

I understand, but I need to provide packages for Ubuntu LTS versions at least. I'll do my very best regarding backporting. Shit!

Not necessarily - you could decide "no, users of LTS versions where dependencies are not available aren't going to get the bleeding-edge development versions of GIMP.

Or you could try to switch to one of the emerging package formats like AppImage or Flatpak et al and provide 2.9.x this way. This might also help with having both 2.8.x and 2.9.x available to the users at the same time, thus maximizing their ability to compare their behavior.

Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD

Am 11.01.2017 um 18:59 schrieb Simon Budig:

Thorsten Stettin (thorsten.stettin@gmail.com) wrote:

Why do you need libpng >= 1.6.25, and lcms2 >= 2.7 in order to build Gimp 2.9.5 - commit 36ebe03770fd8b87102e95cd6c45b194a45a8ba3?

Libpng is due to security issues:

commit a5073ad9289f7e05ef38d2ce99dc71e91983b434 Author: Michael Natterer
Date: Mon Oct 31 09:36:15 2016 +0100

configure.ac: require libpng 1.6.25
Addresses bug #765850, and probably avoids a gazillion of vulnerabilities in the versions since the ancient 1.2.37 we required before.

For libcms2 this is due to some rounding errors that affected some blending modes in gimp:

commit 0ce364ee4dd2200e6607a4575af0cc657600afc9 Author: Michael Natterer
Date: Thu Sep 15 12:52:20 2016 +0200

configure.ac, app: require liblcms2 >= 2.7
and add an lcms2 runtime version check to app/sanity.c
Fixes:
Bug 736701 - LCMS2 rounding errors cause problems with certain GIMP blend modes

I hope this helps, Simon

My problem is to clean backporting it for Ubuntu LTS versions since Trusty. Are libpng 1.6.25, and liblcms2 2.7 backward compatible?

Cheers

Lao-Tse sagt: Nichtstun ist besser, als mit viel Mühe nichts zu schaffen.
Und er sagt auch: Ich habe drei Schätze, die ich hüte und hege.
Der eine ist die Liebe, der zweite ist die Genügsamkeit, der dritte ist die Demut.
Nur der Liebende ist mutig, nur der Genügsame ist großzügig, nur der Demütige ist fähig zu herrschen.

Am 11.01.2017 um 19:08 schrieb Michael Schumacher:

On 01/11/2017 06:59 PM, Thorsten Stettin wrote:

I understand, but I need to provide packages for Ubuntu LTS versions at least. I'll do my very best regarding backporting. Shit!

Not necessarily - you could decide "no, users of LTS versions where dependencies are not available aren't going to get the bleeding-edge development versions of GIMP.

Or you could try to switch to one of the emerging package formats like AppImage or Flatpak et al and provide 2.9.x this way. This might also help with having both 2.8.x and 2.9.x available to the users at the same time, thus maximizing their ability to compare their behavior.

Flatpak, AppImage or Snap aren't options for now. I understand your reasons to decide for upstream releases.

Cheers

Thorsten

Lao-Tse sagt: Nichtstun ist besser, als mit viel Mühe nichts zu schaffen.
Und er sagt auch: Ich habe drei Schätze, die ich hüte und hege.
Der eine ist die Liebe, der zweite ist die Genügsamkeit, der dritte ist die Demut.
Nur der Liebende ist mutig, nur der Genügsame ist großzügig, nur der Demütige ist fähig zu herrschen.