** Attachment added: "Log of install of mopidy 0.18.3-1 on a clean Debian unstable system" https://bugs.launchpad.net/ubuntu/+source/mopidy/+bug/1295370/+attachment/4034666/+files/mopidy-0.18.3-1-install.log
** Description changed: I request a Feature Freeze Exception to sync Mopidy 0.18.3-1 from Debian unstable. An init script was added in Mopidy 0.17.0-2. Mopidy 0.17.0-3 is the version currently packaged in Trusty. In the month following the 0.17 releases, we got a lot of user feedback which resulted in several improvements to the init script and tools for debugging of Mopidy running as a system service. These improvements were released in the 0.18 series of Mopidy, of which the latest release is 0.18.3-1, which has been in wide use for a month now without any serious issues. Relevant bugs are: - Add debugging subcommands to init script for e.g. seeing the effective configuration of the system-wide install: https://github.com/mopidy/mopidy/pull/672 - Don't crash if extensions have wrong dependencies: https://github.com/mopidy/mopidy/issues/657 - Don't crash on unconfigured extensions: https://github.com/mopidy/mopidy/issues/682 As a side note, 0.18 also includes backwards compatible improvements to the extension API. The additions are already used by most Mopidy extensions. Without these improvements, extensions that are not packaged in Debian/Ubuntu yet, and are thus installed with `pip`, will not work with Mopidy installed from Ubuntu 14.04. - Attached is: + Attached are: - diff of upstream changelog between 0.17.0 and 0.18.3 - build log from pbuilder building 0.18.3-1 on Debian unstable - install output I can attest that the package in Debian unstable works, as it has been in use for a month by users of Debian testing/unstable and the Mopidy project's own APT repo at https://apt.mopidy.com. ** Description changed: I request a Feature Freeze Exception to sync Mopidy 0.18.3-1 from Debian unstable. An init script was added in Mopidy 0.17.0-2. Mopidy 0.17.0-3 is the version currently packaged in Trusty. In the month following the 0.17 releases, we got a lot of user feedback which resulted in several improvements to the init script and tools for debugging of Mopidy running as a system service. These improvements were released in the 0.18 series of Mopidy, of which the latest release is 0.18.3-1, which - has been in wide use for a month now without any serious issues. + has been in wide use for a month now without any major issues. Relevant bugs are: - Add debugging subcommands to init script for e.g. seeing the effective configuration of the system-wide install: https://github.com/mopidy/mopidy/pull/672 - Don't crash if extensions have wrong dependencies: https://github.com/mopidy/mopidy/issues/657 - Don't crash on unconfigured extensions: https://github.com/mopidy/mopidy/issues/682 As a side note, 0.18 also includes backwards compatible improvements to the extension API. The additions are already used by most Mopidy extensions. Without these improvements, extensions that are not packaged in Debian/Ubuntu yet, and are thus installed with `pip`, will not work with Mopidy installed from Ubuntu 14.04. Attached are: - diff of upstream changelog between 0.17.0 and 0.18.3 - build log from pbuilder building 0.18.3-1 on Debian unstable - install output I can attest that the package in Debian unstable works, as it has been in use for a month by users of Debian testing/unstable and the Mopidy project's own APT repo at https://apt.mopidy.com. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295370 Title: FFE: Sync Mopidy 0.18.3-1 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mopidy/+bug/1295370/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
