Please confirm the status of this. I suppose package flow can go as
normal now, right?
We had a problem with our dbus socket:
ExecStartPost pointed to /bin/systemctl causing that command to fail.
After a remerge it now looks OK:
andromeda ~ # cat /usr/lib/systemd/user/dbus.socket
[Unit]
Description=D-Bus User Message Bus Socket
[Socket]
ListenStream=%t/bus
Just for reference,
==
this is the service file we produce now:
==
[Unit]
Description=Simple Desktop Display Manager
Documentation=man:sddm(1) man:sddm.conf(5)
Conflicts=getty@tty1.service
After=systemd-user-sessions.service
3.19.18 KDE-dev.iso
SDDM is still broken, now in a different way. SDDM doesn't even load on the
live disc on its own anymore.
dubs.socket: Failed at step EXEC Spawning /bin/systemctl: no such file or
directory
what did we change to get this ^
after starting sddm manually, everything
Yes, you're correct. More focused testing occurs before the release. We are
looking for OOTB experience and making sure users don't install fresh with
broken stuff.
On Tue, Mar 13, 2018, 2:34 PM Sławomir Nizio
wrote:
> > Its testing in general. I don't just test raw
I'm baffled by this. I just logged in. locked the screen, attempted to
unlock and it fails..
thinking I may have typo'd the password, I login as root at terminal,
change password for user, force unlock-sessions, logout, log back in as
user, lockscreen, same issue!
joost_op: it would be sure nice
Its testing in general. I don't just test raw images. If I see something or
hear complaints, I test, and file a bug where necessary.
the idea is we're testing all the time, not just ISOs during/after freeze.
On Sun, Mar 11, 2018 at 5:56 PM Joost Ruis wrote:
> obs-studio
obs-studio isn't part of the images. What does this have to do with image
testing?
On Sun, Mar 11, 2018 at 8:11 PM, Jerrod Frost
wrote:
> As far as testing is concerned, we're testing all the time. We aren't just
> testing right before or after a freeze :) . I get
As far as testing is concerned, we're testing all the time. We aren't just
testing right before or after a freeze :) . I get complaints in single
packages every once in a while and we submit bugzilla bugs to have packages
recompiled or upgraded. I've even gone upstream before if the ebuild needed
Hello,
We've been talking on IRC and figured some pieces of information related
to actions might be missing here.
So,
Has testing started?
How is it going?
Is it blocked by anything? Are you waiting for someone or something?
Is there help needed with something?
Let's have it straight where's
I checked the versions in entropy that were installed vs what was in the
portage tree.
On Tue, Mar 6, 2018 at 7:27 AM Joost Ruis wrote:
> You checked for versions without our overlay attached or what?
>
> On Tue, Mar 6, 2018 at 5:03 AM, Jerrod Frost
You checked for versions without our overlay attached or what?
On Tue, Mar 6, 2018 at 5:03 AM, Jerrod Frost
wrote:
> We need to bump:
> sys-libs/efivar (currently using .21 which isn't in portage)
> sys-fs/btrfs-progs (currently using 4.12 which isn't in portage)
>
We need to bump:
sys-libs/efivar (currently using .21 which isn't in portage)
sys-fs/btrfs-progs (currently using 4.12 which isn't in portage)
sys-boot/grub (currently using 2.02_beta3-r1 which isn't in portage)
sys-boot/efibootmgr (currently using .12 which isn't in portage)
sys-boot/plymouth
13 matches
Mail list logo