This looks great. I tested it in a VM, on my local machine, mako and on the emulator (the emulator suffers from bug #1320329 still). Upstart does not regress as seen on my system, mako and the VM. In a VM, systemd job correctly starts when booting with "init=/lib/systmed/systemd" as seen from both "sudo ufw status" and "systemctl status ufw". "sudo systemctl stop ufw" and "sudo systemctl start ufw" operate correctly. Image tests pass on mako (and mostly on goldfish, see above).
I will sponsor the debdiff once we leave TRAINCON-0. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1341083 Title: ufw needs systemd unit or init.d script Status in “ufw” package in Ubuntu: In Progress Bug description: Always get an 'inactive' status when the system is booted, even if the setting is set to be 'active' into the 'system settings' oem@dev32:~$ sudo ufw status [sudo] password for oem: Status: inactive ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ufw 0.34~rc-0ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.16.0-3-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Sat Jul 12 11:07:30 2014 PackageArchitecture: all SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1341083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
