Steve Langasek <[email protected]> writes: > I don't think it's reasonable to leave testing and unstable users of our > default desktop environment without working suspend and resume for more > than a month (systemd-shim was accepted into unstable on Dec 28, and > this was mentioned on the bug) when a one-line change would fix the > problem.
With the caveat that of course Josh's opinion on the correct status of this bug is not necessarily that of the GNOME maintainers, personally, I simply disagree with this statement. These are not normal circumstances, and normal expectations about usability of unstable and testing do not apply. We're in the middle of one of the most controversial decisions that the project has ever made. I think it's completely reasonable to want to wait for the dust to settle, even if it means that things are temporarily broken in the process. systemd-shim was controversial when you uploaded it, there still are (so far as I know) unresolved questions about conflicts and replaces and configuration file handling, and the whole discussion has been intensely contentious. All sides are making blanket statements that certain things are obvious or easy, which have then been hotly contested by everyone else. The sane thing for a maintainer who doesn't want to wade into this problem to do is to simply do nothing until some sanity and clear direction emerges. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
