[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
Is there some detailed notes on why upstart is still used for user sessions instead of systemd? Is it just lack of time or there are some technical reasons not to switch to systemd here as well? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in init-system-helpers source package in Vivid: Fix Released Status in ubuntu-meta source package in Vivid: Fix Released Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
gravy45, this sounds like bug 953875 (or similar). Please file a new bug, this is unrelated to this FFE and doesn't affect all installations (i. e. it's specific to your system). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in init-system-helpers source package in Vivid: Fix Released Status in ubuntu-meta source package in Vivid: Fix Released Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
The previous post is where it sits for about 30 seconds or so. Here is another screenshot. ** Attachment added: Screenshot-2.png https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1427654/+attachment/4357544/+files/Screenshot-2.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in init-system-helpers source package in Vivid: Fix Released Status in ubuntu-meta source package in Vivid: Fix Released Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
Switching to systemd for Ubuntu MATE 15.04 (Beta 2) seems to have resulted in extended boot time in a Virtualbox guest (approximately 45 seconds longer). ** Attachment added: Screenshot-1.png https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1427654/+attachment/4357543/+files/Screenshot-1.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in init-system-helpers source package in Vivid: Fix Released Status in ubuntu-meta source package in Vivid: Fix Released Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
As stated on the mailing list few months ago (https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2014-December/015154.html), Ubuntu never offered a choice of init system, and won't start doing that. systemd is mandatory to be the supported ubuntu path. That's the reason why ubuntu-standard won't depend on systemd|upstart. Note that for some kernel reasons, the Touch image is still using upstart, but that will change in the future. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in init-system-helpers source package in Vivid: Fix Released Status in ubuntu-meta source package in Vivid: Fix Released Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
See also bug 1399766. I guess the question is whether having a non- systemd installation is going to be supported and I hope the answer will be yes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in init-system-helpers source package in Vivid: Fix Released Status in ubuntu-meta source package in Vivid: Fix Released Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
would it be possible to have ubuntu-standard depend on systemd|upstart instead of systemd only? I'd like to avoid systemd while having ubuntu- standard installed for a fully supported system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in init-system-helpers source package in Vivid: Fix Released Status in ubuntu-meta source package in Vivid: Fix Released Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
Being able to run a script like this over SSH: apt-get -y remove openssh-server shutdown -h now Can be extremely useful in automation tooling, but the switch to systemd breaks this: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1429938 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in init-system-helpers source package in Vivid: Fix Released Status in ubuntu-meta source package in Vivid: Fix Released Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
This bug was fixed in the package init-system-helpers - 1.22ubuntu4 --- init-system-helpers (1.22ubuntu4) vivid; urgency=medium * init: Switch preferred alternative to systemd, and update package description to make sense for Ubuntu. (LP: #1427654) -- Martin Pitt martin.p...@ubuntu.com Sun, 08 Mar 2015 12:26:24 +0100 ** Changed in: init-system-helpers (Ubuntu Vivid) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in init-system-helpers source package in Vivid: Fix Released Status in ubuntu-meta source package in Vivid: Fix Released Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
This bug was fixed in the package ubuntu-meta - 1.332 --- ubuntu-meta (1.332) vivid; urgency=medium * Refreshed dependencies * Added systemd-sysv to standard (LP: #1427654) -- Martin Pitt martin.p...@ubuntu.com Mon, 09 Mar 2015 06:20:44 +0100 ** Changed in: ubuntu-meta (Ubuntu Vivid) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Fix Released Status in init-system-helpers source package in Vivid: Fix Committed Status in ubuntu-meta source package in Vivid: Fix Released Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Changed in: init-system-helpers (Ubuntu Vivid) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: In Progress Status in init-system-helpers source package in Vivid: Fix Committed Status in ubuntu-meta source package in Vivid: In Progress Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Branch linked: lp:ubuntu/vivid-proposed/init-system-helpers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in init-system-helpers source package in Vivid: Fix Committed Status in ubuntu-meta source package in Vivid: Fix Committed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Branch linked: lp:~ubuntu-core-dev/ubuntu-seeds/platform.vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: In Progress Status in init-system-helpers source package in Vivid: Fix Committed Status in ubuntu-meta source package in Vivid: In Progress Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-meta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in init-system-helpers source package in Vivid: Fix Committed Status in ubuntu-meta source package in Vivid: Fix Committed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Changed in: ubuntu-meta (Ubuntu Vivid) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: Fix Committed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in init-system-helpers source package in Vivid: Fix Committed Status in ubuntu-meta source package in Vivid: Fix Committed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Changed in: ubuntu-meta (Ubuntu Vivid) Status: Confirmed = In Progress ** Changed in: ubuntu-meta (Ubuntu Vivid) Assignee: (unassigned) = Martin Pitt (pitti) ** Also affects: init-system-helpers (Ubuntu) Importance: Undecided Status: New ** Changed in: init-system-helpers (Ubuntu Vivid) Status: New = In Progress ** Changed in: init-system-helpers (Ubuntu Vivid) Assignee: (unassigned) = Martin Pitt (pitti) ** Changed in: init-system-helpers (Ubuntu Vivid) Milestone: None = ubuntu-15.03 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: In Progress Status in init-system-helpers source package in Vivid: In Progress Status in ubuntu-meta source package in Vivid: In Progress Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
Filed a bug on apache2 where stop; start on systemd fails: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1428796 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: In Progress Status in init-system-helpers source package in Vivid: In Progress Status in ubuntu-meta source package in Vivid: In Progress Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
Pursuant to many conversations on the topic, this is a formal approval of the FFe, with an assumption that it will land early in the week of March 9th. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in init-system-helpers package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: In Progress Status in init-system-helpers source package in Vivid: In Progress Status in ubuntu-meta source package in Vivid: In Progress Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Changed in: ubuntu-meta (Ubuntu Vivid) Milestone: None = ubuntu-15.03 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Vivid: Confirmed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
I just downloaded today's lubuntu desktop, did an ubiquity install under it (boot the live system with init=/bin/systemd), and also tested the installed system under systemd. No problems encountered. ** Description changed: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411-systemd- migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: - * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) + * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd-sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Vivid: Confirmed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Description changed: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411-systemd- migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE - * Land NFS (bug 1312976) + * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd-sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Vivid: Confirmed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - DONE * Land NFS (bug 1312976) - DONE * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Description changed: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411-systemd- migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not - scheduled for vivid. For that we need to fork ubuntu-minimal-touch to - keep upstart (there is a work item on the spec). + scheduled for vivid. For that we need to ensure to keep upstart on Touch + (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: - * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) - * Land NFS - * Fork ubuntu-minimal-touch + * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) + * Land NFS (bug 1312976) + * Ensure Touch keeps upstart (bug 1428026) Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd-sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Vivid: Confirmed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) * Land NFS (bug 1312976) * Ensure Touch keeps upstart (bug 1428026) Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
** Description changed: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411-systemd- migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) * Land NFS (bug 1312976) - * Ensure Touch keeps upstart (bug 1428026) + * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd-sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Vivid: Confirmed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to ensure to keep upstart on Touch (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) * Land NFS (bug 1312976) * Ensure Touch keeps upstart (bug 1428026) - DONE Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Vivid: Confirmed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to fork ubuntu-minimal- touch to keep upstart (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) * Land NFS * Fork ubuntu-minimal-touch Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1427654/+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
[Touch-packages] [Bug 1427654] Re: FFE: switch system init to systemd [not touch] in 15.04
I got confirmation from Xubuntu (Unit193) and MATE (Martin Wimpress) that switching to systemd works fine and is OK for them. I mailed Julien for Lubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1427654 Title: FFE: switch system init to systemd [not touch] in 15.04 Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-meta source package in Vivid: Confirmed Bug description: As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411 -systemd-migration we aimed for switching the system (not session) init from upstart to systemd this cycle. As this was by and large a 1.2 man show, this took a little longer. One of the remaining blockers for switching the default was to fix NFS (bug 1312976) which is now ready to be uploaded. There is also juju (bug 1409639, landed upstream now) and maas (bug 1423613, scheduled), but for those we can work around missing systemd support by installing upstart on instances. We are a few days past feature freeze now, bug Steve and I discussed last week, and we still want to aim for switching the default in vivid. To be clear, this will affect Ubuntu desktop/server/cloud and the flavours like Kubuntu, but *NOT* ubuntu-touch. Migration to systemd is blocked on touch (too old kernels, some unported jobs), and was not scheduled for vivid. For that we need to fork ubuntu-minimal- touch to keep upstart (there is a work item on the spec). I know from at least Kubuntu and Ubuntu GNOME that they are pushing for switching to systemd. We should get an ack from the others (Lubuntu/Xubuntu/MATE) before doing the switch; but quite a lot of vivid users are running systemd already, and I believe we shook out the worst bugs now. So if/once the release team generally agrees, these are the things which need to happen before switching: * Signoff/test from remaining flavours (MATE, Xubuntu, Lubuntu) * Land NFS * Fork ubuntu-minimal-touch Operationally, the switch is merely to change s/upstart/systemd-sysv/ in the seeds, i. e. flip the dependency in ubuntu-minimal. I did that in https://launchpad.net/~pitti/+archive/ubuntu/systemd, fixed ureadahead, and verified that upgrades from trusty and utopic cleanly upgrade to vivid+PPA with removing upstart and installing systemd- sysv. Around that time I will send a mail to ubuntu-devel-announce@ to warn about the impending switch, and give some pointers how to boot with upstart (from grub menu or reinstalling upstart), how to debug boot/shutdown issues, etc. Contingency plan: This will trigger wider testing, and most certainly uncover more integration issues. I'll try to keep up with them, but if we get to a point where we find that there are too many/too serious regressions, we can flip the seed back to upstart and get back to the situation today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1427654/+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
