This bug was fixed in the package gce-compute-image-packages -
20180510+dfsg1-0ubuntu3~14.04.3
---------------
gce-compute-image-packages (20180510+dfsg1-0ubuntu3~14.04.3) trusty;
urgency=medium
* Restart services upon upgrade with upstart, too
* Remove handling the systemd cases from maintainer scripts
gce-compute-image-packages (20180510+dfsg1-0ubuntu3~14.04.2) trusty;
urgency=medium
* Revert to debhelper to perform most service operations
gce-compute-image-packages (20180510+dfsg1-0ubuntu3~14.04.1) trusty;
urgency=medium
* Stop obsoleted services before removing their upstart .conf files
gce-compute-image-packages (20180510+dfsg1-0ubuntu3~14.04.0) trusty;
urgency=medium
* Backport to Trusty
* Don't wait for snapd.seeded.service
* Keep recommending google-cloud-sdk
* Refresh patches
* debian/rules: Handle all upstart services in override_dh_installinit
* Clean up obsoleted services for upstart, too
* Manage upstart scripts in postinst/preinst/prerm
gce-compute-image-packages (20180510+dfsg1-0ubuntu3) cosmic;
urgency=medium
* Update prerm to stop google-network-daemon.service rather than the removed
ones
* Only Provide irqbalance without Breaks and Replaces to ensure smooth
upgrades
gce-compute-image-packages (20180510+dfsg1-0ubuntu2) cosmic;
urgency=medium
* debian/patches/0003-order-startup-scripts-after-snap-
seeding.service: Ensure that snaps have been seeded before startup
scripts run.
gce-compute-image-packages (20180510+dfsg1-0ubuntu1) cosmic;
urgency=medium
[ Balint Reczey ]
* Break, Replace and Provide irqbalance.
Optimization scripts are conflicting with irqbalance and the set
relationships ensure removal of irqbalance when it was accidentally
installed.
* Depend on virtual system-log-daemon as an alternative of rsyslog
* Update copyrights
* New upstream version 20180510 (LP: #1770650)
* Refresh patches
* Adjust tests to changed behaviour
* Update symlink to shared library with updated revision
* debian/gce-compute-image-packages.preinst: Add debhelper token
* Update Lintian overrides
[ Google Cloud Team ]
* Add module blacklist for GCE
* Fix Debian install when migrating to new network daemon
gce-compute-image-packages (20180129+dfsg1-0ubuntu3) bionic;
urgency=medium
* Drop the Recommends: on google-cloud-sdk; this is moving to be a snap
for 18.04 and we don't want to continue pulling in a deprecated deb.
gce-compute-image-packages (20180129+dfsg1-0ubuntu2) bionic;
urgency=medium
* No-change rebuild against libcurl4
-- Balint Reczey <rbal...@ubuntu.com> Thu, 07 Jun 2018 16:27:01 -0700
** 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/1770650
Title:
Update google compute-image-packages to 20180510
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 Artful:
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/1770650/+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
