[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
[00:32] <lubot> <teward001> @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
[00:34] <lubot> <kc2bez> Agreed, that seems like the wrong way to remove them.
[00:36] <lubot> <teward001> correct.
[00:36] <lubot> <teward001> also upstream indicates the files shouldn't be removed in these cases anyways
[00:36] <lubot> <teward001> so my 'bug report' is to use a better error message
[00:37] <lubot> <kc2bez> moar detail would be nice.
[00:37] <lubot> <teward001> yep
[00:37] <lubot> <teward001> To quote upstream dev:
[00:37] <lubot> <teward001> 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 
[00:37] <lubot> the database or some of its source code.
[00:38] <lubot> <teward001> so i just want a more useful error message there
[00:38] <lubot> <teward001> even with that expectation because some users with deployments of things are... um... 'stupid' is one word but eh
=== krytarik is now known as kryten
[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
[10:55] <lubot> <lynorian> 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
[15:17] <lubot> <tsimonq2> @lynorian [ouch snap stuff is not updating to latest commit when building and I don't know …], Which branch is it on?
[15:18] <lubot> <tsimonq2> Which Git branch?
[15:44] <lubot> <MichaelTunnell> 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
[15:44] <lubot> odules should live upstream. This module, automirror, is really distro-family specific though and I’m happy to see that it’s good code (smart enough to fetch cached GeoIP results) and maintained downstream – and if Lubuntu needs something, they know where I live on IRC. (Edit 2020-04-09: not LXDE, LxQt – I said I don’t pay much attention to what th
[15:44] <lubot> e environment is, eh.) … https://euroquis.nl//calamares/2020/04/08/calamares-q1.html
[16:15] <lubot> <kc2bez> Thank you for sharing @MichaelTunnell
[18:32] <lubot> <HMollerCl> do you know why lxqt.org is offline?
[18:36] <wxl> https://github.com/lxqt/lxqt.github.io/issues/41
[18:36] <ubot93> Issue 41 in lxqt/lxqt.github.io "lxqt.org is down: Connection reset by peer" [Open]
[18:37] <lubot> <RikMills> @HMollerCl [do you know why lxqt.org is offline?], currently being merged with knome.org?
[18:37] <wxl> X'''D
[18:37] <lubot> <MichaelTunnell> lol
[18:38] <lubot> <RikMills> welcome to the collective!
[18:39] <lubot> <MichaelTunnell> We Are Korg!
[18:40] <lubot> <kc2bez> Resistance is futile.
[18:40] <lubot> <MichaelTunnell> wait a second . . . KDE sucks at naming stuff so instead of Korg which might be good they would likely just call it KBorg
[20:43] <lubot> <lynorian> @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
[22:01] <lubot> <tsimonq2> @lynorian [right now it is just from   source: https://phab.lubuntu.me/source/manual.git I …], It should be, hm
[22:05] <lubot> <RikMills> https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551
[22:06] <lubot> <RikMills> does that happen in Lubuntu?
[22:23] <lubot> <RikMills> @HMollerCl you did the drivers tab did you not? ^^^
[22:32] <lubot> <HMollerCl> I didi that tab
[22:32] <lubot> <HMollerCl> @RikMills ^
[22:33] <lubot> <RikMills> Then presumably you were able to test it at the time, and still can?
[22:34] <lubot> <RikMills> I don't have a nvidia box spare
[22:34] <lubot> <HMollerCl> I did, I had concerns however on how it would be affected in secure boot environments
[22:36] <lubot> <HMollerCl> I will ask to test in software-properties-gtk then we now if it is a *-qt problem or software-properties-*
[22:36] <lubot> <RikMills> ack. thanks
[22:39] <lubot> <HMollerCl> done
[22:40] <lubot> <RikMills> great. and good night