Your message dated Wed, 20 Jun 2018 11:28:29 +0100
with message-id <[email protected]>
and subject line done
has caused the Debian Bug report #894129,
regarding prometheus: Please backport Prometheus 2.2.1 to stretch.
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 [email protected]
immediately.)
--
894129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894129
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: prometheus
Version: 2.2.1+ds-1
Severity: wishlist
Dear Maintainer,
Please backport Prometheus 2.2.1 to stretch.
-- System Information:
Debian Release: 9.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/4 CPU cores)
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)
Versions of packages prometheus depends on:
ii adduser 3.115
ii debconf [debconf-2.0] 1.5.61
ii libc6 2.24-11+deb9u3
ii libjs-bootstrap 3.3.7+dfsg-2
ii libjs-eonasdan-bootstrap-datetimepicker 4.17.43-1
ii libjs-jquery 3.1.1-2
ii libjs-jquery-hotkeys 0~20130707+git2d51e3a9+dfsg-2
ii libjs-moment 2.17.1+ds-1
ii libjs-mustache 2.3.0-2
ii libjs-rickshaw 1.5.1.dfsg-2
ii systemd-sysv 232-25+deb9u2
Versions of packages prometheus recommends:
ii prometheus-node-exporter 0.15.2+ds-1~bpo9+1
prometheus suggests no packages.
-- Configuration Files:
/etc/default/prometheus changed [not included]
/etc/prometheus/prometheus.yml changed [not included]
-- debconf information:
prometheus/remove-version1-database: true
--- End Message ---
--- Begin Message ---
This was already fixed a couple of months ago, but the bug was not closed.
--
MartÃn Ferrari (Tincho)
--- End Message ---
