[01:21] <mup> PR pc-amd64-gadget#31 closed: grub.cfg: switch to new style kernel_status failover handling <Created by anonymouse64> <Merged by xnox> <https://github.com/snapcore/pc-amd64-gadget/pull/31>
[10:27] <aiena> WHo maintains the Krita snap is it safe to use?
[10:35] <jamesh> aiena: it is published by the Krita project  themselves.
[10:35] <aiena> hmm the krita projects say's only appimages are official
[10:35] <aiena> so I'm confused lol
[10:35] <aiena> project
[10:35] <aiena> or at least when I asked the devs at #krita
[10:37] <jamesh> "snap info krita" says "publisher: Stichting Krita Foundation (krita✓)"
[10:38] <jamesh> the tick means that Canonical has verified that the "krita" publisher account is actually controlled by the Krita Foundation
[10:40] <jamesh> If the Krita folks say that the snap is not yet at a stage where they recommend it, then I guess  you should trust them
[10:45] <aiena> ok
[13:57] <pokk> *hurray* my rsync over ssh with ssh-keys are working
[13:58] <pokk> now to figure out how to publish it :D
[14:00] <pokk> well... honestly I don't know if it actually works :| it might just be to good permissions
=== QuosqueTandem is now known as hggdh
[20:03] <pokk> Trying to do a remote-build but get an error "Failed to pull source, command" followed by a git command and "exited with code 128." any ideas on what this might be caused by?
[20:45] <cjp256> Pokk: do you have a gitconfig with gpg signing enabled by chance ?
[20:48] <pokk> cjp256: shouldn't have, it's a clean install of ubuntu with no git configured really. But, installed
[20:48] <cjp256> Try running the command manually and see if you get an error? There is an open PR I put up to improve the error and messaging there, but hasn’t been merged yet, unfortunately.
[20:49] <pokk> cjp256: no, it doesn't run, it complains about \n's I'm guessing that's not the case when actually run
[20:51] <pokk> oh, it might because it's such a clean git install
[20:52] <pokk> yepp, that was it :| I had no user.name / user.email
[20:52] <pokk> when setting that it runs
[21:02] <cjp256> Ah thanks for the feedback, I’ll have to address that
[21:36] <pokk> the build targets seem a bit borken as well :( Only able to build one arch
[21:40] <pokk> cjp256: it's in no way unreasonable to need a user.email / user.name but it wasn't obvious from the error message )
[21:40] <pokk> :)
[21:52] <pokk> nice, it did work. But apperantly you can't access it in the way I thought, back to debuging
=== msalvatore_ is now known as msalvatore