[Group.of.nepali.translators] [Bug 1913852] Re: zLib link failures on Xenial
** Also affects: golang-1.13 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Description changed:
+ [impact]
+ Applications that use the "compress/zlib" package fail to build.
+
+ [test case]
+ $ cat > go.mod
+ module github.com/foo/baz
+
+ go 1.13
+ $ cat > main.go
+ package main
+
+ import (
+ "bytes"
+ "compress/zlib"
+ )
+
+ func main() {
+ var b bytes.Buffer
+ w := zlib.NewWriter()
+ w.Write([]byte("hello, world\n"))
+ w.Close()
+ }
+ $ go build -v
+
+ The final command will fail before this is fixed and pass after.
+
+ [regression potential]
+ The fix is just preventing debhelper from stripping the zlib.a file in
golang-1.13-go. Rebuilding the go toolchain one more time should not introduce
any changes (the go project is pretty good about bootstrap hygiene).
+
+ [original description]
Backported go-1.13 came with issues with zlib.
In some projects i see link errors:
golang.org/x/crypto/openpgp/packet.(*Compressed).parse: relocation target
compress/zlib.NewReaderDict not defined
github.com/go-git/go-git/v5/plumbing/format/packfile.NewEncoder: relocation
target compress/zlib.NewWriterLevelDict not defined
github.com/go-git/go-git/v5/plumbing/format/packfile.(*Encoder).entry:
relocation target compress/zlib.(*Writer).Reset not defined
github.com/go-git/go-git/v5/plumbing/format/packfile.(*Scanner).copyObject:
relocation target type.compress/zlib.Resetter not defined
...
+ also reported in
+ https://github.com/GoogleCloudPlatform/osconfig/issues/279
- also reported in https://github.com/GoogleCloudPlatform/osconfig/issues/279
+ and compiling a trivial program (example from compress/zlib reference)
+ causes crash during linking:
-
- and compiling a trivial program (example from compress/zlib reference) causes
crash during linking:
-
-
- root@a6a24cdee4e3:/src/qqq# cat go.mod
+ root@a6a24cdee4e3:/src/qqq# cat go.mod
module github.com/foo/baz
go 1.13
- root@a6a24cdee4e3:/src/qqq# cat main.go
+ root@a6a24cdee4e3:/src/qqq# cat main.go
package main
import (
- "bytes"
- "compress/zlib"
+ "bytes"
+ "compress/zlib"
)
func main() {
- var b bytes.Buffer
- w := zlib.NewWriter()
- w.Write([]byte("hello, world\n"))
- w.Close()
+ var b bytes.Buffer
+ w := zlib.NewWriter()
+ w.Write([]byte("hello, world\n"))
+ w.Close()
}
root@a6a24cdee4e3:/src/qqq# go version
go version go1.13.8 linux/amd64
- root@a6a24cdee4e3:/src/qqq# cat /etc/lsb-release
+ root@a6a24cdee4e3:/src/qqq# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS"
root@a6a24cdee4e3:/src/qqq# go build -v
# github.com/foo/baz
panic: runtime error: index out of range [23] with length 0
goroutine 1 [running]:
cmd/link/internal/ld.decodetypeKind(...)
- /usr/lib/go-1.13/src/cmd/link/internal/ld/decodesym.go:69
+ /usr/lib/go-1.13/src/cmd/link/internal/ld/decodesym.go:69
cmd/link/internal/ld.newtype(0xc0006f4000, 0xc0007146e0, 0xc000618e68)
- /usr/lib/go-1.13/src/cmd/link/internal/ld/dwarf.go:424 +0x29e1
+ /usr/lib/go-1.13/src/cmd/link/internal/ld/dwarf.go:424 +0x29e1
cmd/link/internal/ld.defgotype(0xc0006f4000, 0xc0007146e0, 0x1a)
- /usr/lib/go-1.13/src/cmd/link/internal/ld/dwarf.go:419 +0x1c8
+ /usr/lib/go-1.13/src/cmd/link/internal/ld/dwarf.go:419 +0x1c8
cmd/link/internal/ld.dwarfGenerateDebugInfo(0xc0006f4000)
- /usr/lib/go-1.13/src/cmd/link/internal/ld/dwarf.go:1900 +0x91c
+ /usr/lib/go-1.13/src/cmd/link/internal/ld/dwarf.go:1900 +0x91c
cmd/link/internal/ld.Main(0x84cdc0, 0x10, 0x20, 0x1, 0x7, 0x10, 0x69ac6f,
0x1b, 0x697756, 0x14, ...)
- /usr/lib/go-1.13/src/cmd/link/internal/ld/main.go:212 +0xb92
+ /usr/lib/go-1.13/src/cmd/link/internal/ld/main.go:212 +0xb92
main.main()
- /usr/lib/go-1.13/src/cmd/link/main.go:65 +0x1d6
+ /usr/lib/go-1.13/src/cmd/link/main.go:65 +0x1d6
--
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/1913852
Title:
zLib link failures on Xenial
Status in golang-1.13 package in Ubuntu:
New
Status in golang-1.13 source package in Xenial:
New
Bug description:
[impact]
Applications that use the "compress/zlib" package fail to build.
[test case]
$ cat > go.mod
module github.com/foo/baz
go 1.13
$ cat > main.go
package main
import (
"bytes"
"compress/zlib"
)
func main() {
var b bytes.Buffer
w := zlib.NewWriter()
w.Write([]byte("hello, world\n"))
w.Close()
}
$ go build -v
The final command will fail before this is fixed and pass after.
[regression potential]
The fix is
[Group.of.nepali.translators] [Bug 1914131] Re: xenial/linux-cascade: 4.4.0-1031.34 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true built: main: build#1 meta: build#1 + signed: build#1 kernel-stable-master-bug: 1914140 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 10. February 2021 19:16 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 10. February 2021 23:51 UTC + promote: + - main + - signed + - meta reason: - :prepare-packages: Pending -- building in ppa signed:queued - prepare-package-signed: Ongoing -- signed package not yet fully - built + promote-to-proposed: Pending -- ready for review synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-cascade/cascade-kernel: bug 1914130 variant: debs versions: main: 4.4.0-1031.34 meta: 4.4.0.1031.34 signed: 4.4.0-1031.34 -- 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/1914131 Title: xenial/linux-cascade: 4.4.0-1031.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: main: build#1 meta: build#1 signed: build#1 kernel-stable-master-bug: 1914140 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Ready for Promote to Proposed phase-changed: Wednesday, 10. February 2021 23:51 UTC promote: - main - signed - meta reason: promote-to-proposed: Pending -- ready for review synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-cascade/cascade-kernel: bug 1914130 variant: debs versions: main: 4.4.0-1031.34 meta: 4.4.0.1031.34 signed: 4.4.0-1031.34 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1914131/+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
[Group.of.nepali.translators] [Bug 1914131] Re: xenial/linux-cascade: 4.4.0-1031.34 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: + main: build#1 meta: build#1 kernel-stable-master-bug: 1914140 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Holding before Promote to Proposed phase-changed: Wednesday, 10. February 2021 19:16 UTC reason: - :prepare-packages: Pending -- building in ppa main:queued - signed:depwait - prepare-package: Ongoing -- main package not yet fully built + :prepare-packages: Ongoing -- building in ppa signed:depwait prepare-package-signed: Ongoing -- signed package not yet fully built synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-cascade/cascade-kernel: bug 1914130 variant: debs versions: main: 4.4.0-1031.34 meta: 4.4.0.1031.34 signed: 4.4.0-1031.34 -- 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/1914131 Title: xenial/linux-cascade: 4.4.0-1031.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Committed Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: main: build#1 meta: build#1 kernel-stable-master-bug: 1914140 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Holding before Promote to Proposed phase-changed: Wednesday, 10. February 2021 19:16 UTC reason: :prepare-packages: Ongoing -- building in ppa signed:depwait prepare-package-signed: Ongoing -- signed package not yet fully built synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-cascade/cascade-kernel: bug 1914130 variant: debs versions: main: 4.4.0-1031.34 meta: 4.4.0.1031.34 signed: 4.4.0-1031.34 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1914131/+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
[Group.of.nepali.translators] [Bug 1848923] Re: pollinate.service fails to start: ERROR: should execute as the [pollinate] user -- missing CacheDirectory=
This bug was fixed in the package pollinate - 4.33-3ubuntu2 --- pollinate (4.33-3ubuntu2) hirsute; urgency=medium * d/pollinate.service: ensure cache directory is recreated (LP: #1848923) -- Christian Ehrhardt Tue, 09 Feb 2021 10:57:54 +0100 ** Changed in: pollinate (Ubuntu) Status: In Progress => 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/1848923 Title: pollinate.service fails to start: ERROR: should execute as the [pollinate] user -- missing CacheDirectory= Status in pollinate package in Ubuntu: Fix Released Status in pollinate source package in Xenial: Won't Fix Status in pollinate source package in Bionic: Triaged Status in pollinate source package in Focal: Triaged Status in pollinate source package in Groovy: Triaged Bug description: [Impact] * /var/cache is expected to be able to be cleared for a reboot without drawbacks. But the directory of pollinate is a classic cache, yet it only is created in postinst. That leads to the service failing on reboot after the path was cleared. For example the cockpit images are affected by that * The Fix for that is to instruct systemd to (if needed) create that path under the same permissions. [Test Case] * sudo rm -rf /var/cache/pollinate * sudo reboot * systemctl status pollinate Without the fix it will fail to start missing the directory (but complaining about a wrong user). With the fix it works as systemd recreates that directory if needed. [Where problems could occur] * We modify the service file, so issues would be around the /var/cache/pollinate creation/usage or the start/stop/restart of the service. [Other Info] * the postinst bits doeing the mkdir are not removed to easen backport to e.g. Xenial where this systemd feature does not exist. In a standard Ubuntu 19.10 cloud image install, pollinate fails to start: ● pollinate.service - Pollinate to seed the pseudo random number generator Loaded: loaded (/lib/systemd/system/pollinate.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2019-10-20 12:17:10 EEST; 3 months 4 days ago Docs: https://launchpad.net/pollinate Main PID: 665 (code=exited, status=1/FAILURE) Oct 20 12:17:10 ubuntu systemd[1]: Starting Pollinate to seed the pseudo random number generator... Oct 20 12:17:10 ubuntu pollinate[708]: ERROR: should execute as the [pollinate] user Oct 20 12:17:10 ubuntu systemd[1]: pollinate.service: Main process exited, code=exited, status=1/FAILURE Oct 20 12:17:10 ubuntu systemd[1]: pollinate.service: Failed with result 'exit-code'. Oct 20 12:17:10 ubuntu systemd[1]: Failed to start Pollinate to seed the pseudo random number generator. The user does exist: # id pollinate uid=110(pollinate) gid=1(daemon) groups=1(daemon) and the unit has "User=pollinate" This happens outside of systemd as well: # sudo -u pollinate /usr/bin/pollinate <13>Jan 24 09:31:05 pollinate[21456]: ERROR: should execute as the [pollinate] user set -x shows why: + [ ! -w /var/cache/pollinate ] + error should execute as the [pollinate] user This directory doesn't exist. So (1) this is a bad error message, and (2) pollinate.service is missing "CacheDirectory=pollinate". When adding that, it works. pollinate 4.33-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1848923/+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
[Group.of.nepali.translators] [Bug 1914131] Re: xenial/linux-cascade: 4.4.0-1031.34 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + built: + meta: build#1 kernel-stable-master-bug: 1914140 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Holding before Promote to Proposed phase-changed: Wednesday, 10. February 2021 19:16 UTC reason: - :prepare-packages: Pending -- building in ppa main:building - meta:queued + :prepare-packages: Ongoing -- building in ppa main:building prepare-package: Ongoing -- main package not yet fully built - prepare-package-meta: Ongoing -- meta package not yet fully built prepare-package-signed: Ongoing -- signed package not yet fully built synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-cascade/cascade-kernel: bug 1914130 variant: debs versions: main: 4.4.0-1031.34 meta: 4.4.0.1031.34 signed: 4.4.0-1031.34 -- 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/1914131 Title: xenial/linux-cascade: 4.4.0-1031.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Committed Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Committed Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: meta: build#1 kernel-stable-master-bug: 1914140 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Holding before Promote to Proposed phase-changed: Wednesday, 10. February 2021 19:16 UTC reason: :prepare-packages: Ongoing -- building in ppa main:building prepare-package: Ongoing -- main package not yet fully built prepare-package-signed: Ongoing -- signed package not yet fully built synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-cascade/cascade-kernel: bug 1914130 variant: debs versions: main: 4.4.0-1031.34 meta: 4.4.0.1031.34 signed: 4.4.0-1031.34 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1914131/+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
[Group.of.nepali.translators] [Bug 1911448] Re: Please update to upstream release 20201217.02
This bug was fixed in the package google-guest-agent - 20201217.02-0ubuntu1~18.04.0 --- google-guest-agent (20201217.02-0ubuntu1~18.04.0) bionic; urgency=medium * Backport to Bionic * Relax debhelper requirement to debhelper 10 * Build with golang-1.13 google-guest-agent (20201217.02-0ubuntu1) hirsute; urgency=medium * New upstream release (LP: #1911448) * debian/watch: Fix version handing in the download URL * Update vendored files google-guest-agent (20200617.00-0ubuntu8) hirsute; urgency=medium * debian/rules: Build the package as preferred by upstream - Strip the binary - Set main.version (LP: #1900897) * Declare Breaks: on python3-google-compute-engine to force conscious removal of the Python libraries that are not maintained and this package make obsolete. (LP: #1905986) google-guest-agent (20200617.00-0ubuntu7) hirsute; urgency=medium * No-change rebuild using new golang google-guest-agent (20200617.00-0ubuntu6) groovy; urgency=medium * Import relevant patches from earlier gce-compute-image-packages package (LP: #1901033) google-guest-agent (20200617.00-0ubuntu5) groovy; urgency=medium * debian/rules: Don't stop or start google-startup-scripts and google-shutdown-scripts services google-guest-agent (20200617.00-0ubuntu4) groovy; urgency=medium * debian/gbp.conf: Use Ubuntu tags * Don't ship /etc/default/instance_configs.cfg. Also don't remove it when it exists according to upstream's request. * debian/extra/vendor/*: Add vendored module sources * debian/control: Drop unused Go build dependencies google-guest-agent (20200617.00-0ubuntu3) groovy; urgency=medium * debian/copyright: Use "Google Inc" as copyright holder instead of Google Cloud Platform google-guest-agent (20200617.00-0ubuntu2) groovy; urgency=medium * Install /etc/default/instance_configs.cfg to the right path google-guest-agent (20200617.00-0ubuntu1) groovy; urgency=medium * Initial release (LP: #1870314) -- Balint Reczey Fri, 15 Jan 2021 14:19:51 +0100 ** Changed in: google-guest-agent (Ubuntu Xenial) 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/1911448 Title: Please update to upstream release 20201217.02 Status in google-guest-agent package in Ubuntu: Fix Released Status in google-guest-agent source package in Xenial: Fix Released Status in google-guest-agent source package in Bionic: Fix Released Status in google-guest-agent source package in Focal: Fix Released Status in google-guest-agent source package in Groovy: Fix Released Bug description: [Impact] This package is provided by Google for installation within guests that run on Google Compute Engine. It is part of a collection of tools and daemons, 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 this package to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of this package 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 [Note to SRU team] The bionic and xenial SRUs require golang-1.13, which is also currently in -proposed (LP: #1911478). The package does not build on riscv64 on Focal and on powerpc in Xenial, but this is not an issue since those are not target architectures for the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1911448/+subscriptions ___ Mailing list:
[Group.of.nepali.translators] [Bug 1911448] Re: Please update to upstream release 20201217.02
This bug was fixed in the package google-guest-agent - 20201217.02-0ubuntu1~20.04.0 --- google-guest-agent (20201217.02-0ubuntu1~20.04.0) focal; urgency=medium * Backport to Focal google-guest-agent (20201217.02-0ubuntu1) hirsute; urgency=medium * New upstream release (LP: #1911448) * debian/watch: Fix version handing in the download URL * Update vendored files google-guest-agent (20200617.00-0ubuntu8) hirsute; urgency=medium * debian/rules: Build the package as preferred by upstream - Strip the binary - Set main.version (LP: #1900897) * Declare Breaks: on python3-google-compute-engine to force conscious removal of the Python libraries that are not maintained and this package make obsolete. (LP: #1905986) google-guest-agent (20200617.00-0ubuntu7) hirsute; urgency=medium * No-change rebuild using new golang google-guest-agent (20200617.00-0ubuntu6) groovy; urgency=medium * Import relevant patches from earlier gce-compute-image-packages package (LP: #1901033) google-guest-agent (20200617.00-0ubuntu5) groovy; urgency=medium * debian/rules: Don't stop or start google-startup-scripts and google-shutdown-scripts services google-guest-agent (20200617.00-0ubuntu4) groovy; urgency=medium * debian/gbp.conf: Use Ubuntu tags * Don't ship /etc/default/instance_configs.cfg. Also don't remove it when it exists according to upstream's request. * debian/extra/vendor/*: Add vendored module sources * debian/control: Drop unused Go build dependencies google-guest-agent (20200617.00-0ubuntu3) groovy; urgency=medium * debian/copyright: Use "Google Inc" as copyright holder instead of Google Cloud Platform google-guest-agent (20200617.00-0ubuntu2) groovy; urgency=medium * Install /etc/default/instance_configs.cfg to the right path google-guest-agent (20200617.00-0ubuntu1) groovy; urgency=medium * Initial release (LP: #1870314) -- Balint Reczey Wed, 13 Jan 2021 19:20:08 +0100 ** Changed in: google-guest-agent (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: google-guest-agent (Ubuntu Bionic) 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/1911448 Title: Please update to upstream release 20201217.02 Status in google-guest-agent package in Ubuntu: Fix Released Status in google-guest-agent source package in Xenial: Fix Released Status in google-guest-agent source package in Bionic: Fix Released Status in google-guest-agent source package in Focal: Fix Released Status in google-guest-agent source package in Groovy: Fix Released Bug description: [Impact] This package is provided by Google for installation within guests that run on Google Compute Engine. It is part of a collection of tools and daemons, 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 this package to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of this package 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 [Note to SRU team] The bionic and xenial SRUs require golang-1.13, which is also currently in -proposed (LP: #1911478). The package does not build on riscv64 on Focal and on powerpc in Xenial, but this is not an issue since those are not target architectures for the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1911448/+subscriptions ___ Mailing list:
[Group.of.nepali.translators] [Bug 1848923] Re: pollinate.service fails to start: ERROR: should execute as the [pollinate] user -- missing CacheDirectory=
SRU Template added. For backport planning I'll add B/F/G since the solution on't help Xenial and that really is old enough by now to have more people complain about this issue there to make it super-important. ** Also affects: pollinate (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: pollinate (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: pollinate (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: pollinate (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: pollinate (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: pollinate (Ubuntu Bionic) Status: New => Triaged ** Changed in: pollinate (Ubuntu Focal) Status: New => Triaged ** Changed in: pollinate (Ubuntu Groovy) Status: New => Triaged -- 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/1848923 Title: pollinate.service fails to start: ERROR: should execute as the [pollinate] user -- missing CacheDirectory= Status in pollinate package in Ubuntu: In Progress Status in pollinate source package in Xenial: Won't Fix Status in pollinate source package in Bionic: Triaged Status in pollinate source package in Focal: Triaged Status in pollinate source package in Groovy: Triaged Bug description: [Impact] * /var/cache is expected to be able to be cleared for a reboot without drawbacks. But the directory of pollinate is a classic cache, yet it only is created in postinst. That leads to the service failing on reboot after the path was cleared. For example the cockpit images are affected by that * The Fix for that is to instruct systemd to (if needed) create that path under the same permissions. [Test Case] * sudo rm -rf /var/cache/pollinate * sudo reboot * systemctl status pollinate Without the fix it will fail to start missing the directory (but complaining about a wrong user). With the fix it works as systemd recreates that directory if needed. [Where problems could occur] * We modify the service file, so issues would be around the /var/cache/pollinate creation/usage or the start/stop/restart of the service. [Other Info] * the postinst bits doeing the mkdir are not removed to easen backport to e.g. Xenial where this systemd feature does not exist. In a standard Ubuntu 19.10 cloud image install, pollinate fails to start: ● pollinate.service - Pollinate to seed the pseudo random number generator Loaded: loaded (/lib/systemd/system/pollinate.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2019-10-20 12:17:10 EEST; 3 months 4 days ago Docs: https://launchpad.net/pollinate Main PID: 665 (code=exited, status=1/FAILURE) Oct 20 12:17:10 ubuntu systemd[1]: Starting Pollinate to seed the pseudo random number generator... Oct 20 12:17:10 ubuntu pollinate[708]: ERROR: should execute as the [pollinate] user Oct 20 12:17:10 ubuntu systemd[1]: pollinate.service: Main process exited, code=exited, status=1/FAILURE Oct 20 12:17:10 ubuntu systemd[1]: pollinate.service: Failed with result 'exit-code'. Oct 20 12:17:10 ubuntu systemd[1]: Failed to start Pollinate to seed the pseudo random number generator. The user does exist: # id pollinate uid=110(pollinate) gid=1(daemon) groups=1(daemon) and the unit has "User=pollinate" This happens outside of systemd as well: # sudo -u pollinate /usr/bin/pollinate <13>Jan 24 09:31:05 pollinate[21456]: ERROR: should execute as the [pollinate] user set -x shows why: + [ ! -w /var/cache/pollinate ] + error should execute as the [pollinate] user This directory doesn't exist. So (1) this is a bad error message, and (2) pollinate.service is missing "CacheDirectory=pollinate". When adding that, it works. pollinate 4.33-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1848923/+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
[Group.of.nepali.translators] [Bug 1912830] Re: Use non-removable uefi bootloader in cloud-images by default
** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Fix Committed => Won't Fix -- 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/1912830 Title: Use non-removable uefi bootloader in cloud-images by default Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Won't Fix Status in livecd-rootfs source package in Bionic: Fix Committed Status in livecd-rootfs source package in Focal: Fix Committed Status in livecd-rootfs source package in Groovy: Fix Committed Bug description: [Impact] * use non --removable uefi installation for cloud-images * Currently cloud-images use --removable grub installation, which makes the disk images look at lot more like our installer .isos, than installed systems. This causes many issues: * ubuntu efiboot entry is not created by the fallback manager from shim * one cannot reorder ubuntu boot entry, and/or boot and apply fwupdate updates (if possible) * measurements are unstable, and change if one call grub-install and or upgrades things * often grub & shim upgrades are not applied at all as \EFI\ubuntu does not exist on the ESP * We should switch to only shipping shim/fallback/mm in \ESP\Boot and ship \ESP\ubuntu on the cloud-image ESPs such that we regain stable measurements; ubuntu boot entry; and upgrades of grub and shim. [Test Case] * After UEFI firstboot $ efibootmgr --verbose => should contain `ubuntu` entry pointing at ESP\ubuntu\shim*.efi binary, which should be added to the bootorder [Where problems could occur] * Existing systems which were booted from previous style images, will not upgrade shim|grub on the ESP, and must call `grub-install` or `grub-multi-install` to correct that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912830/+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
[Group.of.nepali.translators] [Bug 1778848] Re: Support for grub upgrades with bios+uefi bootloader targets
** Also affects: grub2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: grub-installer (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: grub2-signed (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: shim-signed (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1778848 Title: Support for grub upgrades with bios+uefi bootloader targets Status in grub-installer package in Ubuntu: Fix Released Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in grub-installer source package in Xenial: New Status in grub2 source package in Xenial: New Status in grub2-signed source package in Xenial: New Status in shim-signed source package in Xenial: New Status in ubiquity source package in Xenial: New Status in grub-installer source package in Bionic: Fix Released Status in grub2 source package in Bionic: Fix Released Status in grub2-signed source package in Bionic: Fix Released Status in shim-signed source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Fix Released Bug description: [Impact] There are multiple use cases which require both BIOS and UEFI bootloaders installed on a target image and to keep them both updated. - cloud images on clouds that support both BIOS and UEFI boot in alternate instance types - PC installs that should remain bootable in the face of firmware upgrades or reconfigurations This currently doesn't work because 'grub-install' selects its install target based on which of grub-pc or grub-efi-amd64 is installed. In cosmic we have introduced a --auto-nvram grub-install option that automatically determines if we're running with NVRAM access or not and if yes, updates the NVRAM contents. This allows such dual BIOS-UEFI bootloader setups to work. Same changes are required to be backported to bionic for our cloud images. [Test Case] Basic grub2 grub-install test: * Boot up a bionic system in UEFI mode. * Upgrade grub2-common to the version in -proposed. * Run `grub-install --target=x86_64-efi --auto-nvram` and make sure it succeeds. * Prepare a system with an UEFI installed system that can be booted into in legacy BIOS mode. * Boot up the UEFI-installed bionic system in legacy BIOS mode. * Upgrade grub2-common to the version in -proposed. * Run `grub-install --target=x86_64-efi --auto-nvram` and make sure it succeeds (actually not doing anything). Install test for UEFI (repeat for both server-live, server and desktop): * Download the latest bionic -proposed-enabled image. * Make sure the image includes the -proposed version of grub2, grub2-signed, shim-signed and grub-installer (and/or ubiquity). * Install the system normally on an EFI system. * Reboot and make sure the system is bootable. Install test for legacy BIOS (repeat for both server-live, server and desktop): * Download the latest bionic -proposed-enabled image. * Make sure the image includes the -proposed version of grub2, grub2-signed, shim-signed and grub-installer (and/or ubiquity). * Install the system normally on a BIOS system. * Reboot and make sure the system is bootable. TODO: Add cloud image testing. [Regression Potential] The backport introduces a change in the dependency chain for grub which, in some cases, can lead to systems loosing their ability to boot. Basically the symptoms to look for is the inability of booting the installed system on EFI or BIOS. A lot of testing and dogfooding will be required to make sure no installation-case has been broken by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1778848/+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
[Group.of.nepali.translators] [Bug 1780897] Re: Installation failure on UEFI systems using older images with automatic download of updates enabled
** Also affects: grub2-signed (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1780897 Title: Installation failure on UEFI systems using older images with automatic download of updates enabled Status in grub2-signed package in Ubuntu: Fix Released Status in grub2-signed source package in Xenial: New Status in grub2-signed source package in Bionic: Fix Released Status in grub2-signed source package in Cosmic: Fix Released Bug description: [Impact] Recent grub2-signed dependency chain changes required some changes to be made to the installer parts to make sure the end system is bootable. However, older isos (like, release images for bionic) do not have these installer changes, so users using those with automatic download of updates enabled on UEFI systems will end up with a broken system. [Test Case] Checking if the bug has been fixed: * Download an older iso (for bionic, let it be the 18.04 release image) * Prepare an UEFI-based VM * Install Ubuntu with automatic download of updates enabled * Reboot and make sure the system is bootable Checking if no regressions have been introduced for the installer: * Download the latest daily server iso * Prepare an UEFI-based VM * Install Ubuntu * Reboot and make sure the system is bootable [Regression Potential] There should be no real regression potential here as we are basically adding dependencies that should otherwise be installed when using a newer image. All potential regressions would be made visible during the installation tests from the test case. [Original Description] Regression caused by https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1778848 Steps to reproduce 1) Install ubuntu-18.04-desktop-amd64.iso in a VM using QEMU and OVMF 2) Reboot the VM 3) See GRUB shell instead of GDM The system can be rescued by running configfile (hd0,gpt2)/boot/grub/grub.cfg at the GRUB shell Installing grub-efi-amd64 in the rescued system then makes it bootable. Previously grub-efi-amd64-signed depended on grub-efi-amd64, and the system was bootable immediately after installation. Additionally, the removal of this dependency has resulted in a very sparse /etc/default/grub after installation. I've attached a simple script for installation with QEMU and OVMF. I suspect that installs are broken on actual hardware with SecureBoot disabled, but I'm not able to test that right now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1780897/+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
[Group.of.nepali.translators] [Bug 1892335] Re: New upstream microreleases 9.5.23 10.14 and 12.4
** Changed in: postgresql-12 (Ubuntu) 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/1892335 Title: New upstream microreleases 9.5.23 10.14 and 12.4 Status in postgresql-12 package in Ubuntu: Fix Released Status in postgresql-9.5 source package in Xenial: Fix Released Status in postgresql-10 source package in Bionic: Fix Released Status in postgresql-12 source package in Focal: Fix Released Bug description: [Impact] * MRE for latest stable fixes of Postgres release on August 13th. [Test Case] * The Postgres MREs traditionally rely on the large set of autopkgtests to run for verification. In a PPA those are all already pre-checked to be good for this upload. [Regression Potential] * Upstreams tests are usually great and in additon in the Archive there are plenty of autopkgtests that in the past catched issues before being released. But never the less there always is a risk for something to break. Since these are general stable releases I can't pinpoint them to a most-likely area. - usually this works smoothly except a few test hickups (flaky) that need to be clarified to be sure. Pre-checks will catch those to be discussed upfront (as last time) [Other Info] * This is a reoccurring MRE, see below and all the references * This includes a fix for two CVEs: CVE-2020-14349 CVE-2020-14350 --- Current versions in supported releases: postgresql-9.5 | 9.5.21-0ubuntu0.16.04.1 xenial postgresql-10 | 10.12-0ubuntu0.18.04.1 bionic postgresql-12 | 12.2-4 focal Special cases: - Groovy will as usual be synced from Debian. I already see postgresql-12 | 12.4-1 | groovy-proposed | source, amd64, i386, ppc64el, s390x Last relevant related stable updates: 9.5.23, 10.14 and 12.4 You'll see that the last update was missed, so I'll combined them. Standing MRE - Consider last updates as template: - pad.lv/1637236 - pad.lv/1664478 - pad.lv/1690730 - pad.lv/1713979 - pad.lv/1730661 - pad.lv/1747676 - pad.lv/1752271 - pad.lv/1786938 - pad.lv/1815665 - pad.lv/1828012 - pad.lv/1833211 - pad.lv/1839058 - pad.lv/1863108 As usual we test and prep from the PPA and then push through SRU/Security as applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-12/+bug/1892335/+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
