Sway May 2019

sway@lists.fedoraproject.org

5 participants
6 discussions

Sway Module
by Till Hofmann 16 May '19

16 May '19

Hi all, I just submitted the first modular updates for sway: F29: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-9777e7f338 F30: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-24a6de6750 The rawhide build failed due to the issue with wlroots [1]. Following the naming guidelines for modules, I named the stream 'rolling', as it's supposed to contain the latest release of all packages. You can find the modulemd in the modules/sway repository [2]. There are two profiles: 'default' only contains sway, swaylock, and swayidle. 'full' additionally contains rofi and mako. I always used the master branch as source for each package, except for mako, where I created a separate branch 'rolling', as mako needed a small change. This is my first module build, so please test (once the update has been pushed)! Kind regards, Till [1] https://lists.fedoraproject.org/archives/list/sway@lists.fedoraproject.org/… [2] https://src.fedoraproject.org/modules/sway/blob/rolling/f/sway.yaml

1 1

Missing mesa-dri-drivers dependency
by Fabio Alessandro Locati 13 May '19

13 May '19

Hi, Today I tried to install Fedora 30 minimal on a machine, and just after install sway from the SIG COPR repo. It did not work, due to a missing swrast driver. After a few researches on Google, I found that the problem was the package mesa-dri-drivers that was not installed. After the installation, sway started perfectly. I think we should add this package as a dependency. What do you think? Best, Fale

1 0

Should I always create a dedicated stream branch for my module?
by Till Hofmann 10 May '19

10 May '19

Hi all, I'm currently working on a module for sway. We basically just want to have a stream that always contains the latest version of sway (including all its dependencies), the same version that is also in rawhide (this stream should be named 'rolling' if I understand the guidelines correctly). In that case, is it better to just use the master branch of the package git, or should I create a dedicated stream branch nevertheless? Thanks, Till

2 1

wlroots build failure (glesv2.pc)
by Jan Staněk 09 May '19

09 May '19

Hi everyone, I have noticed the recent build failure of wlroots in rawhide, which seems to be related to this change [1]. There is already mesa bug related to this [2], so the build should be fine again once that is fixed. Have a nice day! [1]: https://src.fedoraproject.org/rpms/mesa/c/e83e90968fdca65b8b386d3ff08ebc993… [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1707777 -- Jan Staněk Associate Software Engineer, Core Services Red Hat Czech jstanek(a)redhat.com IM: jstanek

1 0

wlroots 0.6.0 in PR, ready to build
by Jan Pokorný 05 May '19

05 May '19

Hello, when you are ready to roll with the new sway 1.1, you can chain the build with https://src.fedoraproject.org/rpms/wlroots/pull-request/2 (archive already uploaded). Sway 1.0 cannot be built with this new version of wlroots: > ../sway/desktop/desktop.c: In function 'desktop_damage_surface': > ../sway/desktop/desktop.c:9:56: error: 'struct wlr_output' has no member named 'lx' > 9 | output_damage_surface(output, lx - output->wlr_output->lx, > | ^~ > ../sway/desktop/desktop.c:10:28: error: 'struct wlr_output' has no member named 'ly' > 10 | ly - output->wlr_output->ly, surface, whole); > | ^~ -- Jan (Poki)

1 1

Next steps towards a module
by qrsBRWN 01 May '19

01 May '19

The packages from the sway-sig copr seems to behave as expected thus far. What are the next steps on the route to modularity? Are there test cases from the regular sway packaging we can reuse? Is there any special hoops to jump through? Br Markus

3 2

2024

2023

2022

2021

2020

2019

Sway May 2019