Try removing ide-generic from your /etc/modules so that it doesn't load
so early in the boot sequence. I found that ide-generic was stealing
port 1f0, preventing the native chipset IDE driver from loading.
ide-generic does not include support for DMA, so once it has loaded and
monopolised the
I don't understand the holdup with PDO. Even php.net says that PDO is
enabled by default, so people who compile PHP themselves from the
upstream dist will get it by default.
Best source I've found for binary PHP packages is dotdeb,
http://packages.dotdeb.org/dists/sarge/php5/
--
To
horde3 is still not installable on etch or sid in conjunction with php5.
The horde3 package incorrectly requires php5-pear, which should be
php-pear as it is named in etch and sid. It also requires php5-domxml,
which is nonexistent because DOM XML is deprecated in PHP5. Instead it
is provided
Is this package still actually being maintained? One could be forgiven
for thinking it had become orphaned.
Please at least get something in -unstable or experimental - I noticed
that the current package (1.36.3) is no longer even in -testing for some
reason.
We, the community, are eager to
Package: isdnactivecards
Version: 3.8.2005-12-06-4
When invoking 'divaload -c 1 -f ETSI', error message returned is:
EICON DIVALOAD: Firmware loader for Eicon DIVA Server ISDN adapters
/dev/Divas DETECT Error -1
I suspect the version of divaload does not support newer hardware
revisions. The
Unofficial packages of PHP 5.1.4 are available at
http://people.debian.org/~dexter/dists/php5.1/ or alternatively from
packages.dotdeb.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: kronolith2
Version: 2.1-1
Uninstallable on a PHP 5 system. Currently requires php4-mcal,
php4-mysql or php4-pgsql. Needs to alternatively support php5-mcal,
php5-mysql or php5-pgsql.
Another of kronolith2's dependencies, php-date, also has a PHP4-only
dependency (php4-pear),
PDO has been available in unofficial php5.1 packages for months now at
http://people.debian.org/~dexter/dists/php5.1/
Why is it taking so long to get PDO into the official repos?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Sorry Georg, I should have been more specific.
The file is /usr/share/pyshared/libsvn/core.py. It's a fairly large file
(swig'ed libsvn bindings). I've actually since upgraded libsvn1 on that
particular box to 1.7.5-1 from sid, and the problem is no longer there
(eg. without patching core.py
Without digging too deep into the code, I found that if I patched the
offending line 4801 of core.py from:
return _core.svn_stream_read(*args)
to instead:
return _core.svn_stream_read(args[0], int(args[1]))
it would work ok. For reference, args was:
(libsvn.core.svn_stream_t; proxy of Swig
Package: snmpd
Version: 5.7.2~dfsg-8.1
Severity: normal
Dear Maintainer,
net-snmp-config split the functionality to create a SNMPv3 user in v5.5
into a separate script called net-snmp-create-v3-user. This script is
missing from the snmpd package (v5.7 and later).
-- System Information:
Debian
I have a few test VMs running on Ubuntu 13.04, which connect to a
Debian-powered Ceph cluster (using v0.61.3 ceph packages from ceph.com
repos). This is working without any problems.
The ceph / librbd packages in Debian are *ancient*, even by Debian
standards. Can we please sync with what the
Thanks for packaging 1.4.4, however it appears to be incomplete. Trying
to load the http plugin reveals missing symbols:
$ uwsgi --plugin http
open(/usr/lib/uwsgi/plugins/corerouter_plugin.so): No such file or
directory [core/utils.c line 4733]
!!! UNABLE to load uWSGI plugin:
On 09/12/2013 03:13 AM, László Böszörményi (GCS) wrote:
#714881 is already fixed with 0.48-2 , closed the bugreport.
Bastian won't NMU Ceph, but started cooperating. He started working on
the current pkg-ceph Git tree[1], which is version 0.67.2 . It's the
latest stable version. Upstream
On Sun, Sep 15, 2013 at 12:00 PM, Bastian Blank wa...@debian.org wrote:
- ceph depends on fdisk, parted and whole lot other crap it does not
need.
This is most likely a dependency of the ceph-disk-prepare or ceph-deploy
scripts, which handle preparing partitions and filesystems on new disks
On Sun, Sep 15, 2013 at 1:03 PM, Bastian Blank wa...@debian.org wrote:
There is a python script ceph-rest-api. Where is this used? Why does
it warrant a dependency on 20 other packages?
This is the as yet sparsely documented admin REST WSGI app (which can also
run as a standalone server),
Having pondered this for a while, it's more complex than I at first
thought. UDP checksums are optional (for IPv4) according to RFC 768:
If the computed checksum is zero, it is transmitted as all ones (the
equivalent in one's complement arithmetic). An all zero transmitted
checksum
FYI, #661510 now reports that a python3-gevent package is available.
However, it appears that the gevent-websocket repo has gone through a
long period of inactivity, and several owner transitions / forks.
The https://github.com/jgelens/gevent-websocket mirror hasn't been
touched since January
We are also seeing what appears to be a memory leak, which becomes quite
a problem when users upload large files. We are _not_ using RMemoryLimit.
On one of our FTP servers, a user is currently uploading a large file,
430 GB so far, and the proftpd process has used almost 10 GB of memory.
It
On 18/12/16 22:58, Hilmar Preuße wrote:
> On 01.12.2016 14:09, Daniel Swarbrick wrote:
>
> Hi Daniel,
>
> Upstream asked to provide full configuration of proftp including
> possible include file. Please be so kind.
Apologies for the late response. Here we go, blank lines,
Hi Martin,
We've been running your 0.15.0~rc.1~git20180507.28967e3+ds-1 packages
from experimental for about a week now, with no issues bar one - the
tilde in the version number upsets the semantic version parsing in
Cloudflare's "unsee" dashboard
On 12.06.2018 17:50, Martín Ferrari wrote:
I had not heard about unsee until now, we should package it too! :)
That would totally rock!
There are a couple of other exporters which I think would be of quite
high interest to a lot of sites, such as the snmp_exporter. Perhaps I
could assist you
On 12.06.2018 18:04, Martín Ferrari wrote:
Does it understand that 0.15.0-rc.1 is lower than 0.15.0, for example?
If that is the case, I could replace the tilde in the metadata.
I have not tested it, but looking at the code, it seems to be reasonably
intelligent and handling major, minor,
Package: prometheus-node-exporter
Version: 0.15.2+ds-1~bpo9+1
Severity: wishlist
Dear Maintainer,
node_exporter 0.16.0 has been released upstream. Please update the
prometheus-node-exporter package to this version, and backport to
stretch & jessie.
Many thanks in advance!
-- System
Package: wnpp
Followup-For: Bug #840759
Owner: Daniel Swarbrick
I am in the process of packaging this.
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
* Package name: prometheus-snmp-exporter
Version : 0.11.0
Upstream Author : Brian Brazil
* URL : https://github.com/prometheus/snmp_exporter
* License : Apache-2.0
Programming Lang: Go
Description
Package: golang-github-gorilla-mux-dev
Version: 1.1-2
Severity: wishlist
Dear Maintainer,
The current packaged version of mux is over two years old. There have
been many improvements made upstream since then. Also, the API
documentation (http://www.gorillatoolkit.org/pkg/mux#api) refers to
Martin,
The Alertmanager UI requires Elm 0.18 (as specified in its
elm-package.json). Over at
https://github.com/elm-lang/elm-platform#1-get-haskell-working, they
state that Elm <= 0.16 should build with GHC 7.8. I take this to mean
that later versions of Elm require a later version of GHC,
Package: prometheus-alertmanager
Version: 0.6.2+ds-3~bpo9+1
Severity: normal
Dear Maintainer,
Current Debian packages for prometheus-alertmanager are extremely out of
date. The web UI and (undocumented / unstable) API has changed
considerably in the ten versions that have been released since
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
Package: prometheus-blackbox-exporter
Version: 0.11.0+ds-4~bpo9+1
Severity: wishlist
Dear Maintainer,
Please package upstream release 0.12.0 and backport to stretch.
-- System Information:
Debian Release: 9.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Hi Martin,
I just had a quick look at the docs for build Elm from source, and it looks
like a pretty direct journey to npm hell. I'm pretty out of touch with
modern web development, so I'm not sure how much help I can be be in terms
of packaging Elm.
I can suggest a couple of alternatives. One
Martin,
I was a bit too hasty in my previous reply. It appears that Alertmanager
compresses and encodes all the web UI assets a Go "blob" (
https://github.com/prometheus/alertmanager/blob/master/ui/bindata.go). Elm
libraries are only needed if you intend to hack / develop the web UI.
I just
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
* Package name: prometheus-bird-exporter
Version : 1.2.1
Upstream Author : Daniel Czerwonk
* URL : https://github.com/czerwonk/bird_exporter
* License : MIT
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
* Package name: prometheus-process-exporter
Version : 0.4.0
Upstream Author : Nick Cabatoff
* URL : http://github.com/ncabatoff/process-exporter
* License : MIT
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
* Package name: prometheus-nginx-exporter
Version : 0.1.0
Upstream Author : NGINX, Inc.
* URL : https://github.com/nginxinc/nginx-prometheus-exporter
* License : Apache-2.0
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
* Package name: prometheus-postfix-exporter
Version : 0.1.2
Upstream Author : Bart Vercoulen , Ed Schouten
* URL : https://github.com/kumina/postfix_exporter
* License : Apache-2.0
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
* Package name: prometheus-squid-exporter
Version : 1.4
Upstream Author : Mohamad Arab
* URL : https://github.com/boynux/squid-exporter
* License : MIT
Programming Lang: Go
Description
I am also witnessing multiple hosts where ntp is failing to start,
however the disable-with-time-daemon.conf file /is/ present on these
systems:
$ dpkg -S disable-with-time-daemon.conf
systemd:
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
System is buster
I'm fairly sure this error disappear if you attempt a rebuild now.
Earlier versions of dh-golang disabled GOCACHE, and Go 1.12 and later
requires that the GOCACHE env var point to a writable directory. This is
AFAIK now the case in the current dh-golang package.
If the error still occurs,
On Thu, 14 Feb 2019 10:10:47 +0100 Santiago Vila wrote:
> Ok, that worked, but I think it would be much better if such option
> could be added to the README.md.gz somewhere, or a README.Debian, or
> something. That will avoid searches in search engines, stackoverflow
> or the Debian BTS.
>
>
I tracked the problem down to the fact that the http.ResponseWriter is
being wrapped by github.com/opentracing-contrib/go-stdlib, causing the
Flusher() method to be masked. As a result, the ResponseWriter does not
satisfy the http.Flusher interface.
I have tested building with a newer version
The upstream pull request for opentracing-contrib/go-stdlib which
resolved the issue is
https://github.com/opentracing-contrib/go-stdlib/pull/26.
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
* Package name: golang-gopkg-yaml.v3
Version : 3.0.0
Upstream Author : Canonical Ltd
* URL : https://gopkg.in/yaml.v3
* License : Apache-2.0
Programming Lang: Go
Description : YAML support
On 24.01.21 17:17, Helge Kreutzmann wrote:
Thanks. Are you unfuzzying the Debconf translations before the upload
or are you issuing a call for updates anyway?
If you want I can unfuzzy the Debconf translations where possible.
Thanks!
I noticed that your submitted German translation, as well
On 24.01.21 18:30, Helge Kreutzmann wrote:
And you removed the fuzzy mark as well? The grammar fix only applies
to the original.
If you feel uncomfortable editing po files you can provide them to me
and I can do it for you.
I'm not sure exactly which fuzzy mark you are referring to. Can you
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
* Package name: golang-github-prometheus-exporter-toolkit-dev
Version : 0.5.1
Upstream Author : The Prometheus Authors
* URL : https://github.com/prometheus/exporter-toolkit
* License : Apache-2.0
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
* Package name: prometheus-smokeping-prober
Version : 0.4.1
Upstream Author : Ben Kochie
* URL : https://github.com/SuperQ/smokeping_prober
* License : Apache-2.0
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
* Package name: golang-github-go-ping-ping
Version : 0+git20201106.b6486c6
Upstream Author : Ben Kochie , et al
* URL : https://github.com/go-ping/ping
* License : MIT
Programming Lang: Go
such errors
are not debian-specific. I recommend that you open an issue upstream on
github to address that.
Daniel Swarbrick
take the new 0.4.2-1 package for a test drive.
Daniel Swarbrick
This bug is now blocking Prometheus (which I co-maintain) from
transitioning to testing.
In the meantime, I see that there is a new release of moment-timezone.js
upstream (0.5.34) which updates the IANA TZDB to 2021e, and would thus
perhaps resolve the test failures that I see when trying to
I noticed in the debian/rules that rebuilding the timezone JS data from the
tzdata package is *optional*, and only occurs if the moment-timezone
package has a +x suffix, e.g. +2021e. If not, the timezone JS data from
the upstream moment-timezone source will be used.
I just tried building
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: prometheus-frr-exporter
Version : 0.2.20
Upstream Author : Tynan Young
* URL : https://github.com/tynany/frr_exporter
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: golang-github-nginxinc-nginx-plus-go-client
Version : 0.9.0
Upstream Author : NGINX, Inc.
* URL : https://github.com/nginxinc/nginx-plus-go-client
Reproduced with prometheus-smokeping-prober 0.4.2-2, built with go-ping
0.0~git20210312.d90f377-1.
# HELP smokeping_response_duration_seconds A histogram of latencies for
ping responses.
# TYPE smokeping_response_duration_seconds histogram
Unable to reproduce with an earlier, in-house build of smokeping_prober
0.3.1 (prior to first debian upload):
# HELP smokeping_response_duration_seconds A histogram of latencies for
ping responses.
# TYPE smokeping_response_duration_seconds histogram
I tested some upstream tags, i.e. "go run ..." to build with the exact
module versions specified by their go.mod:
v0.3.1 - OK
v0.4.0 - counters latch at 65536
v0.4.1 - counters latch at 65534
v0.4.2 - OK
master (as of writing) - OK
Between v0.4.1 and v0.4.2, the go-ping version specified by
A git bisect seems to suggest that
https://github.com/go-ping/ping/commit/30a8f08ad2a9d0b88ca9c1978114d253f63748c3
is the commit which resulted in the regression in go-ping. Sadly that made
it into the package that shipped with bullseye.
I can update the go-ping package to a newer version that
Tags: unreproducible upstream
Sadly I am not able to reproduce this (in a de_DE.UTF-8 locale). However,
the issue has also been mentioned upstream, and since this is (in theory)
not a Debian-specific issue, I suggested that it should be fixed upstream.
See
On Wed, 26 Jul 2023 22:08:15 +0200 Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > mkdir -p temp/zic/2023c temp/zdump/2023c
> > cp -RL /usr/share/zoneinfo/posix/* temp/zic/2023c/
> > cp: cannot stat '/usr/share/zoneinfo/posix/*': No such file or
directory
> > make[1]: ***
systemd support is broken upstream. See
https://github.com/kumina/postfix_exporter/issues/55
This is mentioned in the Debian changelog:
prometheus-postfix-exporter (0.3.0-2) unstable; urgency=medium
[ Daniel Swarbrick ]
...
* Disable systemd journal support until fixed upstream
/prometheus-alertmanager/-/commit/51802d88957fc08bf13daab426e59718fadcf66e)
Regards,
Daniel Swarbrick
OpenPGP_signature.asc
Description: OpenPGP digital signature
I am not able to reproduce this using one of the suggested methods at
https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild:
sbuild -A -d unstable -v --no-run-lintian \
--finished-build-commands="cd %SBUILD_PKGBUILD_DIR && runuser -u $(id
-un) -- dpkg-buildpackage --sanitize-env -us -uc
Disregard my previous comment - I was mistaken.
prometheus-alertmanager ships with a generate-ui.sh script which in the
past fetched the Elm compiler from upstream (since it was not available
in Debian), but the script has always used the Alertmanager web UI
sources as shipped in the package.
On 25.08.23 19:40, Mathias Gibbens wrote:
Something has changed in sid's golang environment since August 4
which is causing dh-make-golang to fail to determine a package's
dependencies and generate a correct d/control. For example, this worked
fine on August 4 but now fails:
It's probably
Note that the Debian prometheus-alertmanager package strips out the web
UI, so the fix in 0.25.1 would actually result in no changes to this
package.
OpenPGP_signature
Description: OpenPGP digital signature
Several months ago I encountered the same bug with
prometheus-smokeping-prober, and fixed it, but my brain is a bit foggy
right now as to what the root cause was.
However, for prometheus-blackbox-exporter at least, the --log.level flag is
respected so long as you build / run it with the
) and is built with
prometheus/common v0.26.0 or later.
blackbox_exporter v0.19.0 still uses go-kit/kit/log, so the options are
either to patch that in Debian to use go-kit/log, or update to
blackbox_exporter v0.20.0, which uses the latter.
On Tue, May 10, 2022 at 8:08 PM Daniel Swarbrick
wrote:
> Seve
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: golang-gopkg-telebot.v3
Version : 3.0.0
Upstream Author : Ilya Kowalewski
* URL : https://gopkg.in/telebot.v3
* License : Expat
Programming
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: prometheus-ui-classic
Version : 2.33.5+ds-1
Upstream Author : The Prometheus Authors
* URL : https://prometheus.io/
* License : Apache-2.0
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: golang-github-scaleway-scaleway-sdk-go
Version : 1.0.0~beta9-1
Upstream Author : Scaleway
* URL : https://github.com/scaleway/scaleway-sdk-go
* License
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: golang-github-ionos-cloud-sdk-go
Version : 6.1.3-1
Upstream Author : IONOS Cloud
* URL : https://github.com/ionos-cloud/sdk-go
* License
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: golang-github-dennwc-ioctl
Version : 1.0.0
Upstream Author : Denys Smirnov
* URL : https://github.com/dennwc/ioctl
* License : MIT
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: golang-github-dennwc-btrfs
Version : 0.0~git20220403.b3db0b2
Upstream Author : Denys Smirnov
* URL : https://github.com/dennwc/btrfs
* License
On 22.12.22 20:52, Shengjing Zhu wrote:
Hmm, this works for me, the generated pb.go uses old timestamp type.
I have added above change and built the package, then checked the result.
My mistake, I think I must have looked at a stale build. The suggested
.proto mapping workaround seems to do
Hi Mathias,
Given that a pristine, upstream checkout fails on that test for the last
two releases, I think we will have to just skip the test.
See https://github.com/prometheus/blackbox_exporter/issues/969
OpenPGP_signature
Description: OpenPGP digital signature
In general, the gRPC tests (in a pristine v0.23.0 checkout) seem to be
utterly broken.
What's more, isolating the tests to just the GRPC tests fails in a
completely different way:
$ go test ./...
ok github.com/prometheus/blackbox_exporter (cached)
ok
I am able to reproduce the FTBFS in a schroot, sans tzdata package.
However, this is weird, because Go ships with an embedded copy of tzdata
(https://pkg.go.dev/time/tzdata). AFAICT, this is not stripped out in
Debian golang-go packages.
Only selected tests fails, and only those which
Aha, reading the docs for the Go tzdata package more thoroughly sheds
some light on the topic:
> Package tzdata provides an embedded copy of the timezone database. If
this package is imported anywhere in the program, then if the time
package cannot find tzdata files on the system, it will use
Studying the test failure with the panic more closely, I think it is due
to the inherent raciness caused by tests which spin up http servers, tcp
servers etc in goroutines within the same test.
I think that what's happening is that the grpc server in the goroutine
is not ready in time, so
I think I just found the smoking gun, so to speak.
In the reproducible builds log, I spotted this:
=== RUN TestDNSProtocol
dns_test.go:490: "localhost" doesn't resolve to ::1.
--- SKIP: TestDNSProtocol (0.00s)
This is due to this check in TestDNSProtocol:
_, err :=
60 minutes is a big jump up from 20 minutes, especially if the test
duration is only just on the border of the current 20 minute timeout. I
would suggest a slightly more conservative increase, e.g. 30 minutes, so
as not to unnecessarily tie up the s390x hosts if some test has
terminally
On Wed, 22 Jun 2022 17:01:51 -0700 Rob Leslie wrote:
> Attached is at least one patch needed to make the sample consoles usable.
Unfortunately it requires a slightly more extensive patch than that. See
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: golang-github-mdlayher-packet
Version : 1.1.0-1
Upstream Contact: Matt Layher
* URL : https://github.com/mdlayher/packet
* License : Expat
For the record, the following test also just timed out on i386:
=== RUN TestRulesUnitTest/Long_evaluation_interval
Unit Testing: ./testdata/long-period.yml
panic: test timed out after 20m0s
So perhaps we need to increase the baseline test timeout for _all_ archs
to at least e.g. 30 mins.
After a fair amount of head scratching, I tracked this down to a change
in behaviour of the protobuf compiler. Version 3.14.0+ generates
slightly different pb.go files with respect to the timestamp type (and
possibly others):
--- metrics.pb.go.old 2022-11-08 23:31:00.0 +1300
+++
Updating the 01-Use_go_generate.patch as follows results in a successful
build (without needing to add golang-google-protobuf-dev as a dependency):
diff --git a/debian/patches/01-Use_go_generate.patch
b/debian/patches/01-Use_go_generate.patch
index cafa5e2..ffa83cf 100644
---
Hi,
On 22.12.22 00:41, Shengjing Zhu wrote:
Hi,
The workaroud could be like this:
https://salsa.debian.org/go-team/packages/notary/-/commit/b0a072faa72857f7523c8245ecaa8814d5a60051
Fixing the build failure in golang-github-prometheus-client-model is a
simple matter of including
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: golang-github-mdlayher-ethtool
Version : 0.0~git20220830.0e16326-1
Upstream Author : Matt Layher
* URL : https://github.com/mdlayher/ethtool
* License
Package: wnpp
Severity: wishlist
Owner: Daniel Swarbrick
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: golang-github-grafana-regexp
Version : 0.0~git20221122.6b5c0a4-1
Upstream Author : Grafana Labs
* URL : https://github.com/grafana/regexp
* License
Hi Paul,
I have also noticed the fairly frequent failures of the memory-intensive
tests on 32-bit, and I am doing my best to keep on top of them with
t.Skip() patches where appropriate. Several of the tests result in the 4
GiB memory footprint threshold being exceeded.
Prometheus itself is
Package: nvme-cli
Version: 2.2.1-4
Severity: normal
Dear Maintainer,
Since the update of nvme-cli to v2.x, the JSON output of an "nvme list"
command contains wrapped-around negative integers for various fields,
e.g.:
{
"Devices":[
{
"NameSpace":1,
"DevicePath":"/dev/nvme0n1",
Hi Eric,
Thanks for the detailed bug report. As this is something which can
theoretically affect _any_ apt-based distributed (i.e., derivatives of
Debian), I feel that it should ideally be reported upstream.
I personally run this textfile collector on a Debian bookworm system, as
well as
Paraphrasing myself from #1027365, this package's tests will pass (even
without tzdata present) if "-tags timetzdata" is used, e.g. by
overriding dh_auto_test.
OpenPGP_signature
Description: OpenPGP digital signature
Paraphrasing myself from #1027365, this package's tests will pass (even
without tzdata present) if "-tags timetzdata" is used, e.g. by
overriding dh_auto_test.
OpenPGP_signature
Description: OpenPGP digital signature
On 07.01.23 12:40, Adrian Bunk wrote:
Does running the autopkgtests on 32-bit bring more benefits than hassle,
or should they be run only on 64-bit architectures?
As troublesome as the tests are on 32-bit, and as much as it would
probably be simpler to just blanket disable them in d/rules, I
I am able to reproduce the reported error with 0.24.0-4.
A vanilla upstream build does not exhibit the error. It appears to be
caused by 02-Do_not_embed_blobs.patch, as omitting that also results in
a working build.
OpenPGP_signature
Description: OpenPGP digital signature
The email template was split out of default.tmpl by upstream commit
https://github.com/prometheus/alertmanager/commit/c0a7b75c9cfb0772bdf5ec7362775f5f7798a3a0,
into email.tmpl.
The Debian package does not install email.tmpl, and even if that file is
copied manually into the
Such a change is unlikely to be met with enthusiasm by the vast majority
of users, and would likely be the source of many subsequent bug reports
requesting the change to be reverted.
Whilst I acknowledge that node_exporter provides a wealth of information
which could potentially be useful to
1 - 100 of 137 matches
Mail list logo
