**** BEGIN LOGGING AT Tue Sep 18 03:00:00 2018
Sep 18 09:30:44 <sixwheeledbeast> I think pastebin looks normal but it has been a while.
Sep 18 09:33:22 <KotCzarny> maybe he just needs some if [ -f ... ]; then rm ...; fi in installation script
Sep 18 09:33:36 <KotCzarny> users are easily scared of error messages
Sep 18 09:34:53 <sixwheeledbeast> flopswap creates it's own sudoers IIRC there is update preinst and postinst due to some compatibility between flopswap versions and upstart version. flopswap needs to know which version of upstart due to differences.
Sep 18 09:35:40 <KotCzarny> i'm just commenting on that single rm line in pastebin
Sep 18 09:35:59 <KotCzarny> unless he confirms flopswap doesnt work or something
Sep 18 09:37:48 <sixwheeledbeast> I felt at the time that, echo "try to remove previous file" was enough to justify the rm: no file exists.
Sep 18 09:41:25 <sixwheeledbeast> I agree it would be nicer
Sep 18 09:44:16 <sixwheeledbeast> Looking at your pastebin again i would say that ssh would be my first guess at your sudo issue.
Sep 18 13:59:46 <DocScrutinizer05> UMMM  >> Remove sudoers Update sudoers<<
Sep 18 14:00:17 <DocScrutinizer05> are you sure this does the right thing[TM]?
Sep 18 14:01:30 <DocScrutinizer05> I guess when anybody would remove sudoers on my system, I'd prolly fetch the sledgehammer ;-D Unless this script is WAY smarter than the diagnostic output suggests
Sep 18 14:02:39 <DocScrutinizer05> for sure my recent sudoers is not compatible with a braindead remoce&&replace script
Sep 18 14:03:19 <DocScrutinizer05> not saying the actual flopswap was braindead in that regard, I didn't look into it
Sep 18 14:04:14 <DocScrutinizer05> just saying my sudoers prolly look quite different than what you might have expected, and replacing them by a (modified) default version might cause havoc
Sep 18 14:06:20 <DocScrutinizer05> actually maemo5 sudoers is a tricky critter since it doesn'T yet support sudoers.d/* genuinely and instead runs a script ... ... which is exactly what might produce the diagnostic output quoted above
Sep 18 14:07:33 <DocScrutinizer05> so maybe it's the OP ( <{-0-}> ?) who messed up sudoers by editing the /wtc/sudoers file in a way they better had not?
Sep 18 14:09:37 <DocScrutinizer05> W*T*F?????  >>Installing new version of config file /etc/event.d/avahi-daemon<<
Sep 18 14:12:21 <DocScrutinizer05> sixwheeledbeast: there are TWO "Remove sudoers" in flopswap context. I think that's one too many
Sep 18 14:12:54 <DocScrutinizer05> line 41 and line 61
Sep 18 14:13:02 <DocScrutinizer05> in pastebin
Sep 18 14:17:37 <sixwheeledbeast> See above, I can't recall reason but I had to deal with compatibility between flopswap versions and upstart versions.
Sep 18 14:27:44 <sixwheeledbeast> flopswap only touches a flopswap.sudoers file IIRC
Sep 18 14:34:01 <sixwheeledbeast> certainly not replacing any systems files with a stock version like seen in other packages.
Sep 18 14:50:43 <DocScrutinizer05> maybe a former flopswap version did, though?
Sep 18 14:50:46 <sixwheeledbeast> line 41 is version 0.1.9 postrm and line 61 is version 0.2.4 postinst.
Sep 18 14:50:53 <sixwheeledbeast> no
Sep 18 14:51:35 <DocScrutinizer05> hmm, I wonder what happens when two instances of update_sudoers run concurrently
Sep 18 14:51:51 <DocScrutinizer05> prolly disaster
Sep 18 14:53:59 <sixwheeledbeast> I can't see how that could happen, debian install scripts are ran sequentially 
Sep 18 15:31:06 <DocScrutinizer05> no idea if update_sudoers spawns an async process
Sep 18 15:32:27 <DocScrutinizer05> anyway the most plausible cause in my book is >>maybe it's the OP ( <{-0-}> ?) who messed up sudoers by editing the /wtc/sudoers file in a way they better had not?<<
Sep 18 15:34:29 <DocScrutinizer05> it's a known and seen frequently problem that users unaware of update-sudoers (and ignoring the warnings in /etc/sudoers) run into fubar sudoers after next time update-sudoers is running
Sep 18 17:37:11 * {-0-} comes from Slackware... sudo is the land of the unknown :D No, I hadn't, still haven't and won't edit sudoers
Sep 18 17:37:58 <KotCzarny> dont lie. sudo is essential in slack too
Sep 18 17:39:19 <{-0-}> true, it's there. "su -" once then do all your root stuff rather than typing 5 extra chars on every command
Sep 18 17:39:59 <KotCzarny> yes, till you shoot yourself in the foot
Sep 18 17:40:37 <{-0-}> that's part of learning :)
Sep 18 17:40:55 <KotCzarny> (although i have root terminal open, so i'm guilty too)
Sep 18 17:41:10 <KotCzarny> but sudo is still important
Sep 18 17:41:22 <KotCzarny> for the user, and for misc. system scripts
Sep 18 17:43:26 <{-0-}> root shell with different colour prompt from the user shell works here *touch wood*
Sep 18 17:55:23 <KotCzarny> you need to knock on wood. touching your wood is teens fun
Sep 18 19:52:16 <{-0-}> Ah, the US version of the phrase! Unless of course this stuff gives you a woody which case... */me edges away from KotCzarny*
**** ENDING LOGGING AT Wed Sep 19 03:00:00 2018