Here is the actual proposal: https://www.debian.org/vote/2019/vote_002
I've been watching this closely. Voting ends on December 27.

This year I learned to use OpenBSD and also Tiny Core Linux 64-bit (they call it "Pure64" for some reason). Both of these operating systems are completely immune to systemd nonsense. It doesn't hurt to have options...

Tiny Core uses Busybox init and is minimalistic in every regard, but can be built up to be a full desktop replacement OS. It has been my daily driver since August 2019 and at this point I've added enough polish to it that it does all I need. Warning: It is very much a do-it-yourself OS, similar to Arch Linux but even more extreme in its minimalism. I think Devuan users would find TCL much to their liking.

Hopefully Debian will do the right thing and my wanderings will have been for naught!

fsmithred wrote:

I'm not clear on what this means:

Majority Requirement

The proposals need a simple majority

From section A.3 of the constitution:

Options which do not have an explicit supermajority requirement have a 1:1 majority requirement.

So that would be >50% (I think).

But the counting is complicated, see section A.6 for the full breakdown:

https://www.debian.org/devel/constitution#item-A

Thanks, I will give this a read.  This is all uncharted territory for me.

HevyDevy wrote:

Im old school though, we will eventually get left behind and overtaken with tech that is shiny and "progressive"...

You'd think so, but then you've got people like me majoring in CSE.

tlathm wrote:

I was just looking and it doesn't appear I kept track, and can't recall. However seeing as version 28.7.2 is available I just kicked off an update (running with nice), and will post back. To clarify, this is an old Dell 8250 with a 2.53GHz P4...pretty ancient.

Compiling Palemoon 28.7.2 with gcc 8.3.0 (using nice) took me almost exactly 12 hours:

time nice emerge -auv palemoon
Calculating dependencies... done!
[ebuild     U ~] www-client/palemoon-28.7.2::palemoon [28.5.0::palemoon] USE="devtools gtk2 jemalloc official-branding optimize -dbus -debug -gnome (-gtk3) -necko-wifi -pulseaudio -threads -valgrind" CPU_FLAGS_X86="sse sse2" 0 KiB
....
real	722m4.230s
user	550m32.601s
sys	33m4.531s

Also note that I only have 2 GB of RAM which is a big factor as well. No possible way could I compile FF I'd imagine, even if it didn't require rust (the rust source alone is like 275 MB....ouch).

Tom

HevyDevy wrote:

mckaygerhard wrote:

what's the problem? OBS works fine for build FF and/or palemoon.. i have my own packages.. for ascii of course .. but not without dbus and for puseshit i'm using apulse

Ive never heard of OBS until it was mentioned just now. Not going to sign up for it though, if i build something ill do it locally.

without offending you that it's bit stupid.. maybe you can build your package locally just at final stage.. and some other must use OBS to don't waste own resources. compiling FF or chromium browsers need huge amount of resources.. that OBS provides easyle and agnostic environment for right dependences (where you can see if all are meet or fails for some one)

HevyDevy wrote:

^ Looks like you would need to build firefox from source to be able to patch it, would that be right?

It certainly appears that way, and that's a really massive compile (requiring rust for some time now) if you've never attempted it.

My company uses Devuan for headless servers, and our needs are very lean so none of this applies. On my own machines I'm currently using Gentoo, and switched from FF to palemoon quite some time ago for more reasons than I can count, including the compile requirements. I can even compile palemoon on very old hardware where I literally wouldn't live long enough to compile FF. Also note that palemoon already has a configuration option to omit dbus.

Tom