Your message dated Tue, 31 Jul 2018 23:09:01 +0100
with message-id <6b24ef68-87f4-da43-4a49-10ad06f8d...@tincho.org>
and subject line Re: [pkg-go] Bug#895889: Bug#895889:
golang-github-weaveworks-mesh: new version causes regression in
prometheus-alertmanager
has caused the Debian Bug report #895889,
regarding golang-github-weaveworks-mesh: new version causes regression in
prometheus-alertmanager
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.)
--
895889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-weaveworks-mesh
Version: 0.1+git20180323.0c91e69-1
Severity: serious
User: debian...@lists.debian.org
Usertags: triggers
Affects: prometheus-alertmanager
Since the upload of golang-github-weaveworks-mesh version
0.1+git20180323.0c91e69-1, the autopkgtest of prometheus-alertmanager¹
fails with the errors copied below.
As the it seems that the same code is used to build the
prometheus-alertmanager package, I think this means that that now FTBFS
(haven't verified). If you believe this was exaggerated or the issue is
really in prometheus-alertmanager, please don't hesitate to lower it
accordingly and/or reassign to prometheus-alertmanager.
I suggest the maintainers of golang-github-weaveworks-mesh and
prometheus-alertmanager discuss how this issue should be solved (hence
the CC).
Paul
¹ https://ci.debian.net/packages/p/prometheus-alertmanager
dh_auto_build: cd build && go install
-gcflags=\"-trimpath=/tmp/autopkgtest-lxc.6nk_tdek/downtmp/autopkgtest_tmp/build/src\"
-asmflags=\"-trimpath=/tmp/autopkgtest-lxc.6nk_tdek/downtmp/autopkgtest_tmp/build/src\"
-v -p 2 -ldflags " -X
github.com/prometheus/common/version.Version=0.6.2+ds -X
github.com/prometheus/common/version.Revision=0.6.2+ds-5 -X
github.com/prometheus/common/version.Branch=debian/sid -X
github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
-X github.com/prometheus/common/version.BuildDate=20180327-00:03:07 -X
github.com/prometheus/common/version.GoVersion=go1.10rc2"
github.com/prometheus/alertmanager/api
github.com/prometheus/alertmanager/artifacts
github.com/prometheus/alertmanager/cli
github.com/prometheus/alertmanager/cli/format
github.com/prometheus/alertmanager/cmd/alertmanager
github.com/prometheus/alertmanager/cmd/amtool
github.com/prometheus/alertmanager/config
github.com/prometheus/alertmanager/dispatch
github.com/prometheus/alertmanager/examples/webhook
github.com/prometheus/alertmanager/inhibit
github.com/prometheus/alertmanager/nflog
github.com/prometheus/alertmanager/nflog/nflogpb
github.com/prometheus/alertmanager/notify
github.com/prometheus/alertmanager/pkg/parse
github.com/prometheus/alertmanager/provider
github.com/prometheus/alertmanager/provider/mem
github.com/prometheus/alertmanager/silence
github.com/prometheus/alertmanager/silence/silencepb
github.com/prometheus/alertmanager/template
github.com/prometheus/alertmanager/template/internal/deftmpl
github.com/prometheus/alertmanager/test
github.com/prometheus/alertmanager/types
github.com/prometheus/alertmanager/ui returned exit code 2
debian/rules:51: recipe for target 'override_dh_auto_build' failed
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.6nk_tdek/downtmp/autopkgtest_tmp'
make[1]: *** [override_dh_auto_build] Error 2
debian/rules:31: recipe for target 'build' failed
make: *** [build] Error 2
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Finally, the alertmanager version I uploaded does not use this package
any more. I might even consider removing it unless some new rdep appears
soon...
In any case, this bug does not apply any more, so I am closing it.
On 20/04/18 13:17, Paul Gevers wrote:
> Not in testing *yet* (that is the purpose of this bug), but it would
> break it if allowed to migrate.
--
Martín Ferrari (Tincho)
--- End Message ---
