On lun., 2014-08-25 at 14:23 -0700, Eduard Bloch wrote:
> Let's imagine we would take the 1.3.x version and add it to Sid. Do you
> consider this possible, anyhow? If no, what are the reasons against it,
> apart from the convention "1.3 is development and therefore evil". I
> mean, what's the most minimal subset of things that are required to fix
> in order to use it?

Read the backlog for this bug (and especially #135)?

> 
> I seriously suggest doing what serves more users and push these things
> to Sid ASAP. I cannot imagine anyone wants to go Stable with the current
> state.

But rushing to experimental/development version doesn't really help. And
whining on bugs either.

I already stated that, but let me kindly remind you that the current
plan is to have a working status (for the *whole* desktop, not just
xfpm) with both init=sysvrc and init=systemd, and handle the upower0.99
transition (no fallback in this case).

Xfce 4.11 seems to have correct status wrt. init=systemd and upower0.99,
but is 4.12 unlikely to be released before transition freeze (sep 5th).

Xfce 4.10 in Jessie/sid have some patches integrated to xfce4-session,
xfce4-settings and xfce4-power-manager, trying to replace consolekit by
logind and support properly init=sysvrc+systemd-shim. It seems that
there are bugs in systemd-shim which might prevent it working correctly
(and might affect lightdm).

Right now it's seems really unlikely that we'll switch to 4.12, but in
case patches against xfpm 1.2 are really too invasive, it's possible
we'll upgrade to 1.4 *when it's released*.

In any case, if you want to help, try the whole desktop under both
sysvrc and systemd, see what works, what doesn't, *investigate* what's
not working (because it might be at the other layer in the stack, like
libpam-systemd or systemd-shim). Also check upower0.99 status (which are
a /different/ issue than systemd/sysvrc), and do that both on laptop and
desktops, since the use cases are different.

If you don't, then please refrain from posting any longer, because
reading (and writing long answers) actually takes a lot of time, which
is then not used doing the above.

Regards,
-- 
Yves-Alexis

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to