This bug was fixed in the package gce-compute-image-packages - 20180905+dfsg1-0ubuntu1~14.04.0
--------------- gce-compute-image-packages (20180905+dfsg1-0ubuntu1~14.04.0) trusty; urgency=medium * Backport to Trusty - Revert ordering shutdown scripts after snapd.service. - Revert adding /snap/bin to PATH for startup/shutdown scripts - Revert to using dh-systemd because Xenial does not have the debhelper * Revert "Build depend on debhelper (>= 9.20160709) instead of on dh-systemd" This reverts commit 1afdbde3f27ab4d1712b1a0d4cc14df3a0528bdc. Xenial does not have that debhelper version thus dh-systemd is needed there. * Build-depend on libboost-regex-dev for regex support * Choose std:: or boost:: regex based on support for C++11 * Set LDFLAGS at the end of the the c++ command line right before libs. This fixes passig additional libs to make, namely -lboost_regex * Link with boost for regex support * Free tests from C++11 constructs to let them being compiled without C++11 support gce-compute-image-packages (20180905+dfsg1-0ubuntu1) cosmic; urgency=medium [ Balint Reczey ] * New upstream version 20180905+dfsg1 (LP: #1792466) - Restart the network daemon if networking is restarted. - Prevent setup of the default ethernet interface. - Accounts daemon can now verify username is 32 characters or less. - Prevent IP forwarding daemon log spam. - Make default shell configurable when executing metadata scripts. - Rename distro directory to distro_lib. * debian/control: Update Vcs-* fields to point to the new packaging repository * Update shared library symlinks * Drop 0001-Adjust-tests-to-changed-LoadJsonArrayToCache-behavio.patch, it is integrated upstream * Build depend on debhelper (>= 9.20160709) instead of on dh-systemd to keep Lintian happy. [ Google Cloud Team ] * Remove NTP dependency from packaging gce-compute-image-packages (20180510+dfsg1-0ubuntu5) cosmic; urgency=medium * Depend on the same version of google-compute-engine-oslogin * Only Recommend rsyslog | system-log-daemon (LP: #1780109) gce-compute-image-packages (20180510+dfsg1-0ubuntu4) cosmic; urgency=medium * debian/patches/0004-order-shutdown-scripts-after-snapd.patch: Order shutdown scripts after snapd.service. * debian/patches/0005-add-snap-bin-to-path.patch: Add /snap/bin to PATH for startup/shutdown scripts. -- Balint Reczey <rbal...@ubuntu.com> Mon, 17 Sep 2018 00:17:02 +0200 ** Changed in: gce-compute-image-packages (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1792466 Title: Update google compute-image-packages to 20180905 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Bionic: Fix Released Bug description: [Impact] compute-image-packages is provided by Google for installation within guests that run on Google Compute Engine. It is a collection of tools and daemons, packaged as gce-compute-image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating gce-compute-image-packages to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. With this release we also add a new binary package to the suite - google-compute-engine-oslogin which is for a future feature of using OS Login on GCE VM instances. In the SRU for Trusty the maintainer scripts removed manual handling of systemd services because systemd can be present on Trusty systemd due to recent changes. In the Trusty SRU the maintainer scripts are also changed to start/restart the shipped upstart jobs and also running google_instance_setup. [Test Case] When a new version of gce-compute-image-packages is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1792466/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp