gimp3-devel @2.99.1-20200223_13: fatal: unable to read tree (9046c758e7b82ffe39b1acb93160a0c9c15743ff)

[saxfun]

Powerbook 5,6 - 1,67GhZ 10.5.8 Leopard

Maybe you guys have some hints for me?

sudo port -v install gimp3-devel
--->  Computing dependencies for gimp3-devel.
--->  Fetching distfiles for gimp3-devel
Cloning into '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_gimp3-devel/gimp3-devel/work/gimp3-devel-2.99.1-20200223'...
remote: Enumerating objects: 28320, done.      
remote: Counting objects: 100% (28320/28320), done.      
remote: Compressing objects: 100% (12191/12191), done.      
remote: Total 28320 (delta 20389), reused 22141 (delta 16036), pack-reused 0 (from 0)      
Receiving objects: 100% (28320/28320), 98.63 MiB | 1.81 MiB/s, done.
Resolving deltas: 100% (20389/20389), done.
Updating files: 100% (5081/5081), done.
fatal: unable to read tree (9046c758e7b82ffe39b1acb93160a0c9c15743ff)
Command failed: GIT_DIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_gimp3-devel/gimp3-devel/work/gimp3-devel-2.99.1-20200223/.git GIT_WORK_TREE=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_gimp3-devel/gimp3-devel/work/gimp3-devel-2.99.1-20200223 /opt/local/bin/git checkout -q 9046c758e7b82ffe39b1acb93160a0c9c15743ff 2>&1
Exit code: 128
Error: Failed to fetch gimp3-devel: Git checkout failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_gimp3-devel/gimp3-devel/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port gimp3-devel failed

[ryandesign (Ryan Carsten Schmidt)]

On macOS 12, the wording of the error message is a little different:

fatal: reference is not a tree: 9046c758e7b82ffe39b1acb93160a0c9c15743ff

As a workaround, you can edit the gimp3-devel Portfile and on the line that reads:

git.url             --depth 3000 https://gitlab.gnome.org/GNOME/gimp.git

change 3000 to a larger number, such as 4000.

Ideally the gimp3-devel port would be changed to fetch from a distfile, not from git.

If it is not possible to fetch from a distfile, then ideally the code in MacPorts base that fetches from git would be enhanced to fetch only the requested commit. Then individual ports would not have the need to specify arbitrary depth levels. The Aseprite Portfile contains an example of the git commands necessary to achieve that.

The port should also be updated to a newer version; it's 4½ years out of date.

[barracuda156]

Replying to ryandesign:

On macOS 12, the wording of the error message is a little different:

fatal: reference is not a tree: 9046c758e7b82ffe39b1acb93160a0c9c15743ff

Same on macOS 14.

[saxfun]

depth raised to 100000 (4000 was way too low). git cloned the files, began configuring, but the following error occurred:

:info:configure checking for poppler-glib >= 0.69.0... yes
:info:configure checking for poppler-data >= 0.4.9... yes
:info:configure checking for cairo-pdf >= 1.12.2... yes
:info:configure checking for libwmf-config... /opt/local/bin/libwmf-config
:info:configure checking for libwmf >= 0.2.8... yes (version 0.2.8)
:info:configure checking for libopenjp2 >= 2.1.0... yes
:info:configure checking for lcms2 >= 2.8... yes
:info:configure checking for xcursor... yes
:info:configure ./configure: line 34614: syntax error near unexpected token `)'
:info:configure ./configure: line 34614: `fi)'
:info:configure Configure failed or did not finish!
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_gimp3-devel/gimp3-devel/work/gimp3-devel-2.99.1-20200223" && ./autogen.sh --prefix=/opt/local --build=ppc-apple-darwin9.8.0 --enable-mp --with-bug-report-url=https://guide.macports.org/#project.tickets --with-pdbgen --with-x --x-includes=/opt/local/include --x-libraries=/opt/local/lib --with-javascript=no --with-lua=no --disable-silent-rules --without-alsa --without-gudev --without-webkit ac_cv_path_PERL=/opt/local/bin/perl5.34 
:info:configure Exit code: 2
:error:configure Failed to configure gimp3-devel: consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_gimp3-devel/gimp3-devel/work/gimp3-devel-2.99.1-20200223/config.log
:error:configure Failed to configure gimp3-devel: configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
:debug:configure     while executing
:debug:configure "$procedure $targetname"
:error:configure See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_gimp3-devel/gimp3-devel/main.log for details.

[saxfun]

in line 34614 there was a line

fi)

I changed it to

fi

next try. I'll report back here.

[ryandesign (Ryan Carsten Schmidt)]

Because this port fetches from the git repository, which does not contain a configure script, the port has to generate it from configure.ac. If what got generated doesn't work, manually editing the generated file won't be the right solution; instead, editing the configure.ac file from which it was generated is what's needed. Likely, the configure.ac script contains some error that old versions of autoconf were not sensitive to but which the version of autoconf which we use now fails on. This is likely a problem that has already been solved in the upstream repository, so updating the port is the first thing I would suggest trying.

[saxfun]

How to update the port? I did a port sync some days ago. You think there are fixed in the upstream which solves the issue?

I'll have a lot in the configure.ac file too. Where to look exactly and what to edit?

[ryandesign (Ryan Carsten Schmidt)]

I am not familiar with the code of the gimp project so I can't really give specific advice. I just suggest you don't spend too much time trying to fix problems in the 4½-year-old version of gimp we're offering in this port today. It seems likely to me that anybody else trying to build gimp would have encountered the same syntax error you did and would have fixed it in the upstream repository long ago. Therefore updating the port to a newer version is likely the best thing to try first.

Instructions for how to contribute to MacPorts are in ​the MacPorts Guide but if that's more effort than you wish to put in I understand; the suggestion to update the port was really more directed at the port's maintainers, to whom the ticket is assigned, but anyone can file pull requests to update ports if they would like to.

[saxfun]

Thanks for your suggestion. i Trend to compile the newest gimp2 2.10 yesterday, after countless fixes it builds at the end. but the app cannot open file formats like.png, .jpeg. that's why I switched to gimp3-devel, without success it seems.

[andlabs (Pietro Gagliardi)]

So I've started taking a crack at updating the Portfile. They changed the build system to meson, and simplified a lot of things in the process. Pertinent here: it no longer allows you to specify whether you want an X11 or a Quartz build yourself, instead basing its backend on whatever the GTK+ 3 install uses. Is there a preferred way to take something like that into consideration, or should we just let gimp3-devel break if gtk+'s configuration changes (which would require a breaking uninstall)?

Python is also now required; will figure out how to handle that appropriately before submitting a patch.

[ryandesign (Ryan Carsten Schmidt)]

Replying to andlabs:

it no longer allows you to specify whether you want an X11 or a Quartz build yourself, instead basing its backend on whatever the GTK+ 3 install uses. Is there a preferred way to take something like that into consideration, or should we just let gimp3-devel break if gtk+'s configuration changes (which would require a breaking uninstall)?

Continue to offer x11 and quartz variants that conflict with one another and verify that the user has chosen the variant that matches the gtk3 variant, using the active_variants-1.1 portgroup.

If the user wishes to change their choice of whether they use x11 or quartz, we have always said that the user should uninstall all ports before doing so.