sway module updated to 1.5

[Aleksei Bavshin]

Hi all,

It took a while, but with 4th build attempt we finally have update for
f32 sway module. Sorry if you've seen some excess noise from fedmsg.

If anyone else here (besides me) is using it, please test and give your
feedback:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-284df052dc

Just reminding that f31 is out of luck this time due to old `wayland`
package.

--

A moment of advertisement: as likely most of the SIG, I have copr repo
with extra packages[1]. Some of those might be of interest for fellow
SIG members:
 - `gammastep` - maintained fork of redshift with wlroots
wlr-gamma-control support.
 - `rofi-wayland` - non-upstreamable fork of `rofi` that uses
wlr-layer-shell for native wayland rendering. It addresses all of the
focus issues I had with rofi due to its X11 nature and keeps being
notably faster than `wofi`.
 - `greetd` - lightweight login manager - is an interesting project
which I'm now using daily with `greetd-tuigreet` text mode greeter.

Feel free to try it and let me know if it's worth proceeding with
including any of those into Fedora. I certainly don't want to deal with
a headache of rust packaging if I'm the only user of greetd :)

[1] https://copr.fedorainfracloud.org/coprs/alebastr/sway-extras/

-- 
With best regards,
Aleksei Bavshin

[Onyeibo Oku]

On Thu, 6 Aug 2020 22:48:08 -0700
Aleksei Bavshin <alebastr89(a)gmail.com&gt; wrote:

Good Morning Aleksei

>  Hi all, 
Interesting collection you've got there.  Hoping these projects will be
sustained.
 
>  A moment of advertisement: as likely most of the SIG, I have copr
> repo
>  with extra packages[1]. Some of those might be of interest for fellow
>  SIG members:
>   - `gammastep` - maintained fork of redshift with wlroots
>  wlr-gamma-control support.
>   - `rofi-wayland` - non-upstreamable fork of `rofi` that uses
>  wlr-layer-shell for native wayland rendering. It addresses all of the
>  focus issues I had with rofi due to its X11 nature and keeps being
>  notably faster than `wofi`. 
Why "non-upstreamable"?  Is this a good thing?

>   - `greetd` - lightweight login manager - is an interesting project
>  which I'm now using daily with `greetd-tuigreet` text mode greeter.
>  
>  Feel free to try it and let me know if it's worth proceeding with
>  including any of those into Fedora. I certainly don't want to deal
>  with a headache of rust packaging if I'm the only user of greetd :)
>  
>  [1] https://copr.fedorainfracloud.org/coprs/alebastr/sway-extras/
>   
I will try them out

Regards
Onyeibp

[Onyeibo Oku]

On Thu, 6 Aug 2020 22:48:08 -0700
Aleksei Bavshin <alebastr89(a)gmail.com&gt; wrote:

 
>  Feel free to try it and let me know if it's worth proceeding
> with
>  including any of those into Fedora. I certainly don't want to deal
>  with a headache of rust packaging if I'm the only user of greetd :)
>  
>  [1] https://copr.fedorainfracloud.org/coprs/alebastr/sway-extras/
>   
Here is my experience with rofi-wayland. Seems it is mixed with ARM
architecture somewhat.

Copr repo for sway-extras owned by alebastr
                                                        17 kB/s |  45
kB     00:02 Error: Problem: problem with installed package
rofi-1.5.4-2.fc32.x86_64
  - package rofi-wayland-1.5.4-1.20200727git498fd2f.fc33.x86_64
conflicts with rofi provided by rofi-1.5.4-2.fc32.x86_64
  - package rofi-wayland-1.5.4-1.20200727git498fd2f.fc33.x86_64
conflicts with rofi provided by rofi-1.5.4-4.fc33.x86_64
  - conflicting requests
  - package rofi-wayland-1.5.4-1.20200727git498fd2f.fc32.armv7hl does
not have a compatible architecture
  - nothing provides ld-linux-armhf.so.3 needed by
rofi-wayland-1.5.4-1.20200727git498fd2f.fc32.armv7hl
  - nothing provides ld-linux-armhf.so.3(GLIBC_2.4) needed by
rofi-wayland-1.5.4-1.20200727git498fd2f.fc32.armv7hl
  - nothing provides libgcc_s.so.1(GCC_3.5) needed by
rofi-wayland-1.5.4-1.20200727git498fd2f.fc32.armv7hl (try to add
'--allowerasing' to command line to replace conflicting packages or
'--skip-broken' to skip uninstallable packages)

[Dominique Martinet]

Onyeibo Oku wrote on Fri, Aug 07, 2020:
>  > Feel free to try it and let me know if it's worth proceeding
> with
>  > including any of those into Fedora. I certainly don't want to deal
>  > with a headache of rust packaging if I'm the only user of greetd :)
>  > 
>  > [1] https://copr.fedorainfracloud.org/coprs/alebastr/sway-extras/
>  > 
>  
>  Here is my experience with rofi-wayland. Seems it is mixed with ARM
>  architecture somewhat.
>  
>  Copr repo for sway-extras owned by alebastr
>                                                          17 kB/s |  45
>  kB     00:02 Error: Problem: problem with installed package
>  rofi-1.5.4-2.fc32.x86_64
>    - package rofi-wayland-1.5.4-1.20200727git498fd2f.fc33.x86_64
>  conflicts with rofi provided by rofi-1.5.4-2.fc32.x86_64
>    - package rofi-wayland-1.5.4-1.20200727git498fd2f.fc33.x86_64
>  conflicts with rofi provided by rofi-1.5.4-4.fc33.x86_64
>    - conflicting requests
>    - package rofi-wayland-1.5.4-1.20200727git498fd2f.fc32.armv7hl does
>  not have a compatible architecture
>    - nothing provides ld-linux-armhf.so.3 needed by
>  rofi-wayland-1.5.4-1.20200727git498fd2f.fc32.armv7hl
>    - nothing provides ld-linux-armhf.so.3(GLIBC_2.4) needed by
>  rofi-wayland-1.5.4-1.20200727git498fd2f.fc32.armv7hl
>    - nothing provides libgcc_s.so.1(GCC_3.5) needed by
>  rofi-wayland-1.5.4-1.20200727git498fd2f.fc32.armv7hl (try to add
>  '--allowerasing' to command line to replace conflicting packages or
>  '--skip-broken' to skip uninstallable packages) 

I think the arm stuff is just what dnf somehow comes up when it tries to
work around the conflict between rofi and rofi-wayland - how does it get
if you uninstall rofi first?


Some Obsolete tag or similar might make that more transparent...

-- 
Dominique

[Onyeibo Oku]

On Fri, 7 Aug 2020 17:03:51 +0200
Dominique Martinet <asmadeus(a)codewreck.org&gt; wrote:

>  Onyeibo Oku wrote on Fri, Aug 07, 2020:
>  > > Feel free to try it and let me know if it's worth proceeding with
>  > > including any of those into Fedora. I certainly don't want to deal
>  > > with a headache of rust packaging if I'm the only user of greetd
>  > > :)
>  > > 
>  > > [1] https://copr.fedorainfracloud.org/coprs/alebastr/sway-extras/
>  > >   
>  > 
>  > Here is my experience with rofi-wayland. Seems it is mixed with ARM
>  > architecture somewhat.
>  > 
>  > Copr repo for sway-extras owned by alebastr
>  >                                                         17 kB/s |
>  > 45 kB     00:02 Error: Problem: problem with installed package
>  > rofi-1.5.4-2.fc32.x86_64
>  >   - package rofi-wayland-1.5.4-1.20200727git498fd2f.fc33.x86_64
>  > conflicts with rofi provided by rofi-1.5.4-2.fc32.x86_64
>  >   - package rofi-wayland-1.5.4-1.20200727git498fd2f.fc33.x86_64
>  > conflicts with rofi provided by rofi-1.5.4-4.fc33.x86_64
>  >   - conflicting requests
>  >   - package rofi-wayland-1.5.4-1.20200727git498fd2f.fc32.armv7hl
>  > does not have a compatible architecture
>  >   - nothing provides ld-linux-armhf.so.3 needed by
>  > rofi-wayland-1.5.4-1.20200727git498fd2f.fc32.armv7hl
>  >   - nothing provides ld-linux-armhf.so.3(GLIBC_2.4) needed by
>  > rofi-wayland-1.5.4-1.20200727git498fd2f.fc32.armv7hl
>  >   - nothing provides libgcc_s.so.1(GCC_3.5) needed by
>  > rofi-wayland-1.5.4-1.20200727git498fd2f.fc32.armv7hl (try to add
>  > '--allowerasing' to command line to replace conflicting packages or
>  > '--skip-broken' to skip uninstallable packages)  
>  
>  
>  I think the arm stuff is just what dnf somehow comes up when it tries
>  to work around the conflict between rofi and rofi-wayland - how does
>  it get if you uninstall rofi first?
>  
>  
>  Some Obsolete tag or similar might make that more transparent...
>   
That worked well.  It installed but it is not yet working as expected.
Perhaps I need to review my configuration.  Any difference between drun
and +drun?

Error:  Mode window is not found.  The following modi are known: +run
ssh +drun combi keys

[Aleksei Bavshin]

Ah, sorry, been a bit busy and didn't have time to respond properly.

>  Why "non-upstreamable"?  Is this a good thing? 
Not really. rofi upstream didn't like that the code is tied to
wlroots-specific protocols and rejected the PR. Meaning that wayland
fork would continue existing as a git snapshot from a third party repo
until they come up with generic wayland solution that satisfies everyone.

> > Some Obsolete tag or similar might make that more transparent...
Yep, copr leaked arm builds into x86_64 repository. ¯\_(ツ)_/¯
dnf is smart enough to ignore wrong arch packages normally, but might
show those anyways if there are broken deps.

I'm not sure about Obsoletes. Don't want to force git snapshot to anyone
who enables copr repo. There's an explicit Conflicts: rofi though.
`dnf swap rofi rofi-wayland` should work good enough and I'll definitely
need to document that in the copr landing page.

>  That worked well.  It installed but it is not yet working as
> expected.
>  Perhaps I need to review my configuration.  Any difference between drun
>  and +drun?
>  
>  Error:  Mode window is not found.  The following modi are known: +run
>  ssh +drun combi keys 
wayland fork does not support 'window' mode. Not that it worked before
anyways, since it wasn't be able to see wayland windows.
If you have `modi` in your rofi config you'll need to remove 'window'
from the option value. I.e' `modi: "run, drun"` in config.rasi should
fix that.

-- 
With best regards,
Aleksei Bavshin