[02:12] <Eickmeyer> OvenWerks: I think he borked his install during install by failing to read the release notes. :/
[03:52] <studiobot> <azbulutlu> re mypaint if it gets in it gets in, if not as you said there is the backport. thats all we can do... :) mypaint is just amazing for sketching (it is an infinite canvas software which krita isn't. so they are not direct alternatives to each other).
[10:01] <RikMills> doesn't look co-installable to me. looks like a library transition where gimp would need to be rebuilt for the bumped soname
[12:44] <RikMills> ok. current gimp would fail to build with the new mypaint lib/brushes, so that is a blocker in debian and us
[18:19] <Eickmeyer> RikMills: Except gimp specifies libmypaint2.0 and Mypaint specifies libmypaint1.5, so why couldn't the two be coinstallable? Unless the soname is an issue.
[18:24] <RikMills> Eickmeyer: gimp in focal currently depends: libmypaint-1.3-0 (>= 1.3.0)
[18:26] <Eickmeyer> RikMills: Ok, so are the two libraries coinstallable or is someone in Debian being super dumb about this?
[18:26] <RikMills> which is because that is what it build with. replace that with libmypaint-1.5-1 required for new mypaint, amd gimp would have to be recompiled to work with that
[18:27] <RikMills> actually it is not so much the lib that rebuilding gimp has an issue with, but more the mypaint-brushes version
[18:27] <RikMills> but they all need to be shipped for the transition to build new mypaint
[18:28] <Eickmeyer> Ok, I'm asking this because Fedora seems to have figured it out by having both mypaint-brushes versions coinstallable. Why can't Debian do the same?
[18:28] <Eickmeyer> (and both libmypaint versions)
[18:28] <RikMills> Eickmeyer: See: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/experimental/+packages
[18:28] <RikMills> debian is not fedora ;?
[18:29] <Eickmeyer> Yes, but the principle is still there.
[18:29] <Eickmeyer> It all comes down to the packaging.
[18:32] <RikMills> it always is, but point is at the moment it will crash and burn which is why that stuff is in experimental
[18:33] <Eickmeyer> Well, I'm not sweating it too much, but it's an issue that has been going on for two years that nobody has figured out and I don't have the influence in Debian to tell people to make stuff coninstallable. Seems like the right hand has no idea what the left hand is doing on this.
[18:34] <Eickmeyer> Either way, we have people installing gimp from PPAs that have figured out how to make it coninstallable with MyPaint.
[18:34] <RikMills> Eickmeyer: same issue with fuse3. It is v annoying
[18:34] <Eickmeyer> And then filing bug reports against that gimp package when it crashes, filling launchpad with useless bug reports that get reported to us because gimp is in the packageset.
[18:35] <Eickmeyer> I get at least two emails a day about gimp because someone improperly reported a bug against the gimp that's in the PPA (skipping-over ubuntu-bug/apport).
[18:37] <RikMills> Eickmeyer: PPAs are an 'overlay' which means you can gave a lib from that and a different version from the ubuntu primary archive installed AT THE SAME TIME as long as there is no file conflict. We can;t so that in the ubuntu main archive without renaming the source package
[18:37] <RikMills> *have a lib
[18:37] <Eickmeyer> Right. Either way, it's annoying.
[18:38] <RikMills> It is
[18:39] <studiobot> <teward001> (this was the headache I had to encounter with a filesystem compat lib/toolset in Debian - vmfs-tools and vmfs6-tools achieve much of the same 'goals' but with different compat levels for VMware filesystems - the first request was to make coinstallable.)
[18:39] <studiobot> <teward001> (but that was pain :P)
[18:39] <RikMills> easiest hope is gimp do a bugfix version to work with new mypaint sources 
[19:27] <studiobot> <Eickmeyer> @azbulutlu So, there's our answer, probably not going to happen. :/
[19:27] <studiobot> <Eickmeyer> @azbulutlu Did you ever have a chance to design a new default wallpaper?