[10:46] teward: You're the xca maintainer in Debian. Since xca has a new DB format, mightn't it be useful to upload that to backports? [12:15] JackFrost: on my list of things to do but its wayyyyy lower on the priority list. [12:17] Since I can do the backport at $INSERT_TIME_HERE I am focusing on higher priority things at the moment - Studio needs some things poked and theres other higher priority things I keep an eye on for the dev cycle that I need to keep an eye on from now until featurefreeze [12:29] JackFrost: however how old are you thinking for the backport? Any xca >= 2 i believe uses the new DB format. Theres some other deps I think might not exist in older versions as well - and for EOL Releases I am hesitant to really backport to those (so 16.04 is the oldest I may keep an eye on) [12:30] But for now E:EXHAUSTION from 72h+ of hell from this week and a major infra outage at work so I am heading back to sleep for another 5 hours :P [12:30] Well considering Ubuntu backports aren't really a thing, I was thinking buster here. [12:30] Ahhhh in Debian. [12:31] Context next time since this is #ubuntu-motu ;) [12:31] E:LackOfContext :P [12:31] On my list of things [12:31] But again not ultra critical since right now I need sleep more [12:31] (Also Ubuntu does have backports ;) ) [12:32] Sure, but functioning* [14:44] I don't understand one thing: In the .dsc (debian/control), there is a specific g++ version pinned (g++-9), whereas in the debian/rules, the GCC Version varies based on what is available for that distribution. What is the background there? [14:44] I just patched the dsc to accept g++8 for now, as the rules file would pick g++8 on buster anyway