Your message dated Mon, 10 Jun 2019 03:42:33 +0200
with message-id <20190610014233.itbnbmtqyksnp...@fatal.se>
and subject line Re: mender-client fails to build from source on all
architectures
has caused the Debian Bug report #930227,
regarding mender-client fails to build from source on all architectures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
930227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mender-client
Version: 1.7.0-4
Severity: serious
Justification: FTBFS
Tags: security ftbfs
While rebuilding all packages in buster for CVE-2018-17846 /
CVE-2018-17847 / CVE-2018-17848 in golang-golang-x-net-dev,
mender-client fails to build from source on all architectures where it
was tried.
The log on amd64
https://buildd.debian.org/status/fetch.php?pkg=mender-client&arch=amd64&ver=1.7.0-4%2Bb11&stamp=1559989410&raw=0
ends like this:
mdb.c: In function 'mdb_cursor_put':
mdb.c:6725:9: warning: this statement may fall through
[-Wimplicit-fallthrough=]
if (SIZELEFT(fp) < offset) {
^
mdb.c:6730:5: note: here
case MDB_CURRENT:
^~~~
github.com/mendersoftware/mender/installer
# github.com/mendersoftware/mender/installer
src/github.com/mendersoftware/mender/installer/installer.go:40:8:
rootfs.InstallHandler undefined (type *handlers.Rootfs has no field or
method InstallHandler)
github.com/mendersoftware/mender/store
dh_auto_build: cd obj-x86_64-linux-gnu && go install
-gcflags=all=\"-trimpath=/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src\"
-asmflags=all=\"-trimpath=/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src\" -v
-p 4 -ldflags "-X main.Version=1.7.0-4+b11"
github.com/mendersoftware/mender github.com/mendersoftware/mender/client
github.com/mendersoftware/mender/client/test
github.com/mendersoftware/mender/installer
github.com/mendersoftware/mender/statescript
github.com/mendersoftware/mender/store
github.com/mendersoftware/mender/utils returned exit code 2
make[1]: *** [debian/rules:18: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:15: build-arch] Error 2
-- System Information:
Debian Release: 10.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-debug'), (200,
'testing'), (100, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hello,
On Sat, Jun 08, 2019 at 09:00:52PM +0200, Paul Gevers wrote:
> Source: mender-client
> Version: 1.7.0-4
> Severity: serious
> Justification: FTBFS
> Tags: security ftbfs
>
> While rebuilding all packages in buster for CVE-2018-17846 /
> CVE-2018-17847 / CVE-2018-17848 in golang-golang-x-net-dev,
> mender-client fails to build from source on all architectures where it
> was tried.
You say building in buster, yet the build log is clearly from sid:
>
> The log on amd64
> https://buildd.debian.org/status/fetch.php?pkg=mender-client&arch=amd64&ver=1.7.0-4%2Bb11&stamp=1559989410&raw=0
> ends like this:
[...]
I'm going to claim if you built in buster there's no issue. As I see it
the correct action is thus to close this bug report.
If we put buster aside and focus on sid, I see two obvious ways to fix
the build problem. The first would be to upload the updated
mender-client packages sitting in git, the second to revert the
mender-artifact package to previous version. As the second already seems
to have happened, then as I see it the correct approach would be to just
close this bug report.
(I forsee if you do builds in sid that you aim to migrate to buster,
there might be problems that the newly (re)built mender-client package
will have a Built-Using field pointing to the new fugly "foo+reallybar"
version of mender-artifact. I'm confident you know better than me how to
handle that situation, just thought I'd mention it.)
Either way it seems this bug report should be closed, thus doing so.
(Adressing/CCing me or Lluis directly would also most likely be useful.)
If there are any remaining issues, please share what those are.
Regards,
Andreas Henriksson
--- End Message ---
