On Sat, Dec 23, 2017 at 05:46:05PM -0600, Don Wright wrote:
> Might as well start a thread for those of us who /didn't/ have significant
> issues upgrading from Devuan Jessie to ASCII as our part of the sprint, just
> to provide some balance to the problem-oriented bug database and other
>
On Sat, Jan 06, 2018 at 04:41:57PM +0300, Hleb Valoshka wrote:
> On 2018-01-05 20:08, Andreas Messer wrote:
> > If anyone like to try it out, checkout branch suites/experimental
> > from https://git.devuan.org/amesser/elogind.git and build with
> > debbuild. This is my first package, comments are
On Sat, Jan 06, 2018 at 08:46:03PM +0300, Hleb Valoshka wrote:
> Do we need consolekit2 packaged?
I think yes. consolekit (without 2) seems to have issues with
ck-lauch-session in combination with displaymanagers like sddm. This was
actually the reason for me to package elogind in the hope it
On Sat, Jan 06, 2018 at 04:41:57PM +0300, Hleb Valoshka wrote:
> On 2018-01-05 20:08, Andreas Messer wrote:
> > If anyone like to try it out, checkout branch suites/experimental
> > from https://git.devuan.org/amesser/elogind.git and build with
> > debbuild. This is my first package, comments are
On Fri, Jan 05, 2018 at 09:52:48PM +0100, viverna wrote:
> When the KPTI patch will be in ascii and jessie?
> With AMD processor is possible to ignore patch?
The patched kernel is already in ascii, if you have ascii-security
enabled, and comes directly from stretch.
HND
KatolaZ
--
[ ~.,_
Do we need consolekit2 packaged?
I've spent a few hours to make initial packaging and installed it
instead of old consolekit. So far so good, I'm able suspend my pc and
mount usb drives from Thunar.
If dev1 needs it I can afford a bit more time to polish it and prepare
for uploading.
On 2018-01-05 20:08, Andreas Messer wrote:
> If anyone like to try it out, checkout branch suites/experimental
> from https://git.devuan.org/amesser/elogind.git and build with
> debbuild. This is my first package, comments are welcome.
-> d/changelog
elogind (234.4-devuan1) experimental;
