Latest upstream release: 1.0-rc1 Current version/release in rawhide: 0.15.2-1.fc29 URL: https://github.com/swaywm/sway Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/11497/
Latest upstream release: 1.0-rc2 Current version/release in rawhide: 0.15.2-3.fc30 URL: https://github.com/swaywm/sway Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/11497/
Latest upstream release: 1.0-rc3 Current version/release in rawhide: 0.15.2-3.fc30 URL: https://github.com/swaywm/sway Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/11497/
Latest upstream release: 1.0-rc4 Current version/release in rawhide: 0.15.2-3.fc30 URL: https://github.com/swaywm/sway Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/11497/
Latest upstream release: 1.0-rc5 Current version/release in rawhide: 0.15.2-3.fc30 URL: https://github.com/swaywm/sway Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/11497/
Latest upstream release: 1.0 Current version/release in rawhide: 0.15.2-3.fc30 URL: https://github.com/swaywm/sway Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/11497/
So to sync on the plan here, due to multi-package character of what forms the sway ecosystem these days: 1. going to produce wlroots-0.5.0 soon [bug 1667603], the prerequisite got updated promptly ([bug 1672654], thanks!) 2. the first functionality that got split was screenshotting, and for that, I started package reviews for slurp and grim, but dropped the ball (sorry about that), need to raise it again: [bug 1645765], [bug 1645764] 3. any volunteers to adopt other split packages, swayidle, etc.? of course, there can be a line between must-have and nice-to-have 4. with the previous points addressed, only then it is perhaps reasonable to update sway in Fedora -- do you agree? Especially for 3., help of volunteers might be handy, but perhaps whoever has enough time and energy may help in whichever aspect.
I volunteer for maintenance help :) Is there list of packages that needs to be take care of?
Hi, I volunteer for maintenance help! I've worked a lot around sway packaging during the 0.X series. One of the problems I've noticed during that time was that was more a personal effort than a group one. I'm very glad to see that now the interest in Sway is much wider and many people are interested in packaging it. For those reasons, I would suggest to take the 1.0 occasion and the increased interest in Sway, to go toward a SIG approach, so that there is less admin (give package privileges to people) and more ability to operate as a team!
Hi, I don't have a lot of time those days but I would gladly co-maintain some of these packages :-)
Hi, I'd really like to help as well. Is there a package I can help out with?
> 1. going to produce wlroots-0.5.0 soon [bug 1667603], the prerequisite > got updated promptly ([bug 1672654], thanks!) Built for rawhide so far, you can follow the referenced bug. Are we aiming F30 with the updated sway stack as well? For volunteers, as sketched out in [comment 6], there will be bunch of new packages to introduce into Fedora, in the order of subjective importance, and volunteers are hopefully on both sides for that (packagers and reviewers): https://github.com/swaywm/swaylock (must-have, IMHO) https://github.com/swaywm/swayidle I'll try to finish package review for slurp/grim that stand for another previously built-in program, swaygrab (at least static screen snap part). (Also, sway combines nicely with rofi if dmenu seems too limited, already in Fedora via [bug 1509679].)
> For volunteers, as sketched out in [comment 6], there will be bunch > of new packages to introduce into Fedora, in the order of subjective > importance, and volunteers are hopefully on both sides for that > (packagers and reviewers): > > https://github.com/swaywm/swaylock (must-have, IMHO) > https://github.com/swaywm/swayidle I could give swayidle a try if that's fine. I'm new though, so someone will need to sponsor me!
(In reply to Jack H. from comment #12) > I could give swayidle a try if that's fine. I'm new though, so someone will > need to sponsor me! It doesn't prevent you from submitting a review ;-) It's the way to go to get sponsored! Do not hesitate to ask for help. (In reply to Jan Pokorný [poki] from comment #6) > 3. any volunteers to adopt other split packages, swayidle, etc.? > of course, there can be a line between must-have and nice-to-have I will take care of the mako [0] notification daemon over the weekend. (In reply to Fabio Alessandro Locati from comment #8) > For those reasons, I would suggest to take the 1.0 occasion and the > increased interest in Sway, to go toward a SIG approach, so that there is > less admin (give package privileges to people) and more ability to operate > as a team! A wiki page or a taiga [1] board could be nice to track the packaging effort. [0] https://github.com/emersion/mako [1] https://taiga.fedorainfracloud.org/
(In reply to Jan Pokorný [poki] from comment #11) > Are we aiming F30 with the updated sway stack as well? We should be able to use modularity [0] to provide some kind of backport for Fedora 29/30. [0] https://docs.fedoraproject.org/en-US/modularity/
(In reply to Jan Pokorný [poki] from comment #11) > For volunteers, as sketched out in [comment 6], there will be bunch > of new packages to introduce into Fedora, in the order of subjective > importance, and volunteers are hopefully on both sides for that > (packagers and reviewers): > > https://github.com/swaywm/swaylock (must-have, IMHO) > https://github.com/swaywm/swayidle I will take swaylock.
Review request for swaylock is in bug #1688873, review appreciated :) I'm also willing to review the other volunteer's packages -- just write me an e-mail.
It's great to see increased interest in sway! I started maintaining sway when it was orphaned, so I'm very happy if more people work on sway. I like the idea of creating a SIG for sway, especially with the increased number of packages and the number of people interested in the sway ecosystem. I will start the process described at https://fedoraproject.org/wiki/Creating_a_Fedora_SIG if nobody objects.
I got swayidle whipped up. It's in bug #1689251. Let me know if I did anything wrong!
(In reply to Timothée Floure from comment #13) > I will take care of the mako [0] notification daemon over the weekend. Review request for mako: https://bugzilla.redhat.com/show_bug.cgi?id=1689634
I posted an initial email about creating a SIG to the devel list: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/TPKAFZXTRPW7IWGFIAT45NY6J6OX6RGG/
Wow, really loving the work going on here! A few days ago I made an RPM for sway and yesterday, I posted it here: https://src.fedoraproject.org/rpms/sway/pull-request/1#. (Also one wlroots change: https://src.fedoraproject.org/rpms/wlroots/pull-request/1#) I'm sure neither are perfect, but hopefully provides a good base.
Thanks!, Can i suggest that dmenu should be a recommends as well. It does not work with "xwayland disabled" in sway/config, and you do not really need it either
I think this should be removed? https://src.fedoraproject.org/rpms/sway/blob/master/f/sway.spec#_78 This only applies on systems without logind, and it is also outdated because the README these day's say's that sway needs suid on systemd without logind please remove the cap_sys_ptrace and cap_sys_tty_config if possible
Thanks for your comments, I added your suggestions in sway 1.0-3: https://src.fedoraproject.org/rpms/sway/c/e59b8638fb856679b4eb0ca8c130056315555105?branch=master I'm closing this bug as sway 1.0 is in rawhide, but we should continue the work on the other packages. I'll continue with the SIG in the next couple of days.
Thanks Should probably reconsider this as well (Recommends): # dmenu (as well as rxvt any many others) requires XWayland on Sway Requires: xorg-x11-server-Xwayland These day's one should be able to do without, as QT5 and GTK3 have pretty decent wayland support.