[00:24] <teward> wxl @wxl23 so they've reproduced it when a file is deleted from the S3 store - my guess is the backend provided by DO deleted the file or some cleanup process did that, and that's what led to the existing issue
[00:25] <teward> at this point I just want them to state a better error
 @wxl23 @kc2bez @tsimonq2 if we're deleting files from the datastore in the backend that's the problem - that needs to not happen because the assumption is S3 hosted files will stay there perpetually
 Agreed, that seems like the wrong way to remove them.
 correct.
 also upstream indicates the files shouldn't be removed in these cases anyways
 so my 'bug report' is to use a better error message
 moar detail would be nice.
 yep
 To quote upstream dev:
 We could raise a more tailored error message here (“File data has been destroyed in the backing storage engine and can not be recovered.”), but the expectation is that S3 is a permanent datastore. If you destroy data in S3 manually, that will generally break Phabricator, just like Phabricator would break if you deleted some rows in 
 so i just want a more useful error message there
 even with that expectation because some users with deployments of things are... um... 'stupid' is one word but eh
[10:24] -lugito12:#lubuntu-devel- [rMANUALab39c2c2239e: Update to current directory] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALab39c2c2239e
[10:51] -lugito12:#lubuntu-devel- [rMANUAL22872e30f6f7: remove other uneeded dependencies for html will make snap build faster and is…] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL22872e30f6f7
 ouch snap stuff is not updating to latest commit when building and I don't know why
[11:03] -lugito12:#lubuntu-devel- [rMANUAL961d89b4b449: update libreoffice.png] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL961d89b4b449
[11:36] -lugito12:#lubuntu-devel- [rMANUAL4742fbd41403: Update libreoffice_calc.png] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL4742fbd41403
[11:50] -lugito12:#lubuntu-devel- [rMANUALdeb1fdb3992b: Update calc-save.png] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALdeb1fdb3992b
[11:53] -lugito12:#lubuntu-devel- [rMANUALef8d3e62e33a: Update calc-specialcharacter.png] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALef8d3e62e33a
[12:13] -lugito12:#lubuntu-devel- [rMANUAL0921d87c51e7: Update calc-link.png] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL0921d87c51e7
 @lynorian [ouch snap stuff is not updating to latest commit when building and I don't know …], Which branch is it on?
 Which Git branch?
 Calamares dev briefly talks about Lubuntu implementation of Calamares plus plans for the future of Calamares (switching to C++ & QML) … Lubuntu is a lightweight Ubuntu, which installs LxQt. There are a few Calamares modules for Ubuntu-derivatives that are developed by Lubuntu. Usually I’m an “eager upstream”, and I think that m
 Thank you for sharing @MichaelTunnell
 do you know why lxqt.org is offline?
[18:36] <wxl> https://github.com/lxqt/lxqt.github.io/issues/41
 @HMollerCl [do you know why lxqt.org is offline?], currently being merged with knome.org?
[18:37] <wxl> X'''D
 lol
 welcome to the collective!
 We Are Korg!
 Resistance is futile.
 wait a second . . . KDE sucks at naming stuff so instead of Korg which might be good they would likely just call it KBorg
 @tsimonq2 [Which branch is it on?], right now it is just from   source: https://phab.lubuntu.me/source/manual.git I did  not tell it to use a branch so wouldn't that be master by default
 @lynorian [right now it is just from   source: https://phab.lubuntu.me/source/manual.git I …], It should be, hm
 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551
 does that happen in Lubuntu?
 @HMollerCl you did the drivers tab did you not? ^^^
 I didi that tab
 @RikMills ^
 Then presumably you were able to test it at the time, and still can?
 I don't have a nvidia box spare
 I did, I had concerns however on how it would be affected in secure boot environments
 I will ask to test in software-properties-gtk then we now if it is a *-qt problem or software-properties-*
 ack. thanks
 done
 great. and good night