[12:10] <sgmoore[m]> <Eickmeyer[m]> "sgmoore (@sgmoore:kde.org): Hi..." <- Yes, but right now snaps are on hold: core22 need my kde-neon extension finalized and merged into snapcraft upstream. And core20 snaps are being removed until security updates issue is solved. Since Neon does not maintain packages when they move to a new base I am creating a PPA to maintain security updates. This is a WIP. I just can't allow my name to be attached to a bunch of
[12:10] <sgmoore[m]> snaps with secuirty holes.
[12:11] <sgmoore[m]> and morning all
[13:45] <RikMills> santa_: going to get 5.27.0 built in the archive, then will do 5.103.0
[13:45] <RikMills> hope that is ok
[13:47] <santa_> RikMills: of course, thanks a lot for uploading to archive
[13:47] <RikMills> 5.27.0 uploaded
[13:48] <RikMills> pushing git
[14:11] <BluesKaj> Hi all
[14:33] <Eickmeyer[m]> <sgmoore[m]> "Yes, but right now snaps are..." <- I totally get that. :)
[16:56] <RikMills> 5.27.0 for kinetic is in backports-landing
[17:18] <IrcsomeBot> <RikMills> https://irc-attachments.kde.org/a4830d01/file_63489.jpg
[17:18] <IrcsomeBot> <RikMills> Forwarded from RikMills: So far so good in virtualbox......
[17:56] <mmikowski> hi everyone.
[17:57] <mmikowski> Anybody seen this: running meld gives: "Cannot import: GTK+ | No module named 'gi'"
[17:57] <mmikowski> oh, and then it refuses to run, making it substantially less valuable :P
[18:07] <Eickmeyer> mmikowski: Ran meld yesterday without issues. Sounds like a dependency got deleted inadvertently.
[18:09] <mmikowski> Eickmeyer: Hi! I agree and am now testing on a separate machine to see if its a consistent problem. 
[18:10] <mmikowski> Eickmeyer: And, it's not. So it's specific to this machine. Which is great news, actually.
[18:10] <mmikowski> Now to figure out what the heck happened here...
[18:10] <Eickmeyer> Yep. Meld isn't one of those packages that sees a lot of updates in the archive.
[18:11] <mmikowski> Yeah, was thinking it was a python update that might have caused it, as the python software properties did get updated. I'll work it out.
[18:14] <mmikowski> oh, classic. Home is 99% full. All bets are off.
[18:14] <Eickmeyer[m]> That'd do it.
[18:15] <mmikowski> Although / is 42%. That's a relief
[18:22] <arraybolt3> Heh, I start getting worried when my drive gets even 50% full :P
[18:28] <mmikowski> meh, I don't have time to fix it now. At least it is not systematic.
[18:44] <mmikowski> Yeah, well all of python now looks squirrelly. Again, specific to this system.
[18:51] <mmikowski> fwiw, I fixed it by reinstall all python packages as found in a working system. Not sure how that happened, now its fixed.
[18:51] <mmikowski> That's from the department of redundancy department :)
[19:13] <arraybolt3> :P