Bug 1608832 - sway-0.15.2 is available
Summary: sway-0.15.2 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: sway
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Till Hofmann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-26 11:16 UTC by Lukas Ruzicka
Modified: 2018-08-07 01:14 UTC (History)
3 users (show)

Fixed In Version: sway-0.15.2-1.fc28
Clone Of:
Environment:
Last Closed: 2018-08-07 01:14:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lukas Ruzicka 2018-07-26 11:16:10 UTC
Description of problem:

Hello, I have realized that for Rawhide, we still do not ship the newer version of Sway - 0.15.2. That version is announced on their wepage as a stable release and fixes several bugs.

I think that it would be worth to package for Fedora 29.

https://github.com/swaywm/sway/releases/tag/0.15.2

Comment 1 Till Hofmann 2018-07-26 12:42:52 UTC
Thanks for pointing out the release, I missed it in between all those alpha releases. Interestingly, release monitoring also missed it.

I'll update it in the next few days.

Comment 2 Fedora Update System 2018-07-26 13:05:14 UTC
sway-0.15.2-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2a0f57fdda

Comment 3 Fedora Update System 2018-07-27 18:14:46 UTC
sway-0.15.2-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2a0f57fdda

Comment 4 Fedora Update System 2018-08-07 01:14:54 UTC
sway-0.15.2-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.