Good news is that Gimp 2.10 which I have been awaiting with bated breath has landed in Sid.
Kind of. Actually the package upgrade should be avoided as Gimp ends up being removed due to the lack, currently, of the appropriate gimp-data package to go with it.
I ran the package upgrade to see what happened. Sid is the secondary OS on this drive so not a big deal with me. I am using testing as the primary OS.
I find it strange that gimp and gimp-data have never shown up in an 'apt-cache policy gimp' (or gimp-data) query output. Gimp-data doesn't now either.
If it were there I would install it over on the Sid install. Would have a while ago actually.
Hopefully this means that the Debian crew thinks it is all good and just need to get their act together and get the .debs done and in the repo.
2.10 is supposed to feature non destructive editing which is really the only real disadvantage to using Gimp. It is not a disadvantage to most users but is pretty important to people that really like to do post processing of digital photos for more than just touching them up, cropping and scaling for screen or internet viewing.
I will post further developments on this in this thread.
This sort of thing is more common in Sid than testing but the only real difference between Sid and testing is the 'rule' that RC bugs in packages should not be released to the testing repos. RC bugs being defined as packages that will prevent the OS from booting to the desktop. But this is not that sort of bug at all. It merely removes Gimp. There is no rule that prevents that sort of thing in either sid or testing.
It does make me look at the list of packages to be removed in both sid and testing pretty closely. Have had 2 x11 upgrades this testing cycle (Debian10) in Sid that definitely would have prevented booting to a desktop. Just removed most, or all of, x11 packages and the stuff like any DE that depends on that stuff.
Learned to watch out for that stuff really closely in Ubuntu-testing. They always blamed it on "upstream" (Debian). I always believed that until I installed Debian testing along with the Ubuntu-testing things. Did that, at first, just to get a heads up on the crap Debian was sending to poor Canonical. Then discovered that there were no such problems with Debian testing in about 85 to 95% of the cases where there was a problem in Ubuntu-testing.
This turns out to be caused by Ubuntu not using Debian testing, or even Sid, packages but just grabbing them from the Debian experimental repo. I Debian the testing dev team actually uses those packages in testing to detect bugs and this is why, if using apt-listbugs, there are bugs filed against package that are new to Sid most times. This makes Sid actually more stable than Ubuntu-testing way too often for comfort.
Also goes a long ways in explaining the number of serious bugs that turn up in about every new release of new "stable" Ubuntu versions. This is particularly true of the "regular" Ubuntu versions which are nominally based on Sid but also the LTS versions nominally based on Debian testing. They pull in a LOT of packages straight from the Debian experimental repo for both.
I expect this to not effect Debian testing but I will be watching any Gimp package upgrades VERY carefully in testing until this switch to Gimp2.10 is complete. I have, as a precaution, put the package Gimp on hold in testing.
# apt-mark hold Gimp