Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
The Latest Gimp 3 AppImage From The Gimp Dev Team
#1
The only permanent link to a new appimage i could find is from the Artifacts page.
Look for a gimp-debian-x64 with 4 files and click the folder on the RHS. Then 'build' then 'linux'.

The team are pretty happy with it for good reason. It's the current state of the Gimp3 source code and its had many AppImage issues solved.
So far it's working on most Linux distros.

I find gnome gimp on Gitlab confusing because I haven't studied how to use it.
Reply
#2
I wonder how they can work with Gitlab being down again and again.
At this moment it's again "Error 503 No healthy backends".

Has been like this for a few weeks now ... and feels like getting worse evry day.
Reply
#3
(11-27-2024, 09:18 AM)MrsP-from-C Wrote: I wonder how they can work with Gitlab being down again and again.
At this moment it's again "Error 503 No healthy backends".

Has been like this for a few weeks now ... and feels like getting worse evry day.

It is quite annoying, I assure you. Mostly we work on stuff locally and then merge into the main repository whenever it comes back online. I got a few fixes in yesterday when GitLab was running well for a few hours. Smile

My understanding is that the issues are related to GNOME migrating their web infrastructure gradually to a new server, and once they're done the problems should be fixed.
Reply
#4
The link I posted at the top is now a '404: Page not found'. I think there is more going on at gitlab gimp than migrating to a new server.
Reply
#5
(11-29-2024, 08:02 AM)Tas_mania Wrote: The link I posted at the top is now a '404: Page not found'. I think there is more going on at gitlab gimp than migrating to a new server.

Given the URL, looks more like the URL for the result of a specific job so a newer AppImage is probably somewhere else. There may be a more "stable" URL to use somewhere.

OK, so 

1) yes, the products of that build were removed about 2 days ago (a build run must be generating Gigabytes of files these days, they aren't likely to keep all these indefinitely).


2) For the latest working AppImage, you go here and search for the latest image-debian one with a green dot. You click on the folder icon at the end of the line and navigate to build/linux/appimage/_Output/. Of course when I say "working", it means it compiled and passed some tests. Those that come from the master branch may be a bit more representative than those from a joe-developer/see-if-that-works at last branch.
Reply
#6
The migration to the new server will be on December,4th see here:
https://discourse.gnome.org/t/scheduled-...c/25271/13

As they say here:
https://discourse.gnome.org/t/login-prob...b/25132/38

the problems will persist till then.
We just have to be patient till after the migration.
Reply
#7
Quote:The migration to the new server will be on December,4th see here:

Next Wednesday here in Australia Smile  it will go unnoticed for sure.

I found appimages can be generated just 3 hours apart. The top and bottom artifacts in the image are valid appimages.

   

There are probably no real 'milestones' but incremental improvements with the same filename?
Reply
#8
I think just incremental commits as https://github.com/GNOME/gimp/commits
Reply
#9
it doesn't look like appimages will be appearing on Gimp downloads anytime soon.
The gimp3 appimages are much improved carrying fusemount3 which makes them faster, they are on the backburner.

Looking at the last comment here the lead dev has some general issues about it.

_____________________________________________________________________________

I figured-out how to get a direct link to the last appimage.

Make an image from an artifact, after you have gone thru the steps you get a link to your download.

I'm not sure how long these links last.

You don't need to be logged-in to do this.
Reply
#10
I just look for the successful gimp build with 4 entries and just chase the path. Old builds do seem to drop off the list, at least they were last week.

Interesting to see the changes between builds. A 5 Nov file size 243 MB and the build from today, (about 5 hours old at time of writing) 167 MB

As far as I can see everything is still there. A bias towards flatpak ? Maybe but no reason (apart from effort) for not having an appimage.

hmmm....nothing is ever simple. I have to link the libgimp-3.0 files out of /x86_64-linux-gnu to /lib to get my compiled gimp_gmic_qt to work. To repack the appimage or not , that is the question.
Reply


Forum Jump: