>Keeping s2ram in the archive just confuses the issue horribly. Here's a solution -- put the s2ram binary in it's own package. Have both pm-utils and swsusp dependent on this third package. The pm-suspend script can execute the s2ram binary rather than introduce more bugs by trying to re-implement it.
The other acceptable solution is to leave s2ram in swsusp, since that is part of the swsusp project and just have 2 tools that do the same job. I'm sorry you have trouble receiving bug reports on your fork of s2ram, but when I install swsusp with apt-get I expect to get everything that I would get building from source on my own (minus stuff that's excluded cause it's non-free) just as I expect from any other package I've ever installed with apt-get. Nobody forced you to fork the package, please let me continue to use the original. That's why I use free software in the first place. -- Please re-enable build of s2ram binary https://bugs.launchpad.net/bugs/134238 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
