[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#984535: marked as done (ITP: dnsperf -- accurate latency and throughput metrics for Domain Name Service (DNS))



Your message dated Mon, 08 Mar 2021 17:00:08 +0000
with message-id <E1lJJEm-000261-R6@fasolo.debian.org>
and subject line Bug#984535: fixed in dnsperf 2.4.2+debian-1
has caused the Debian Bug report #984535,
regarding ITP: dnsperf -- accurate latency and throughput metrics for Domain Name Service (DNS)
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 owner@bugs.debian.org
immediately.)


-- 
984535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984535
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp

  * Package name : dnsperf
  * Upstream Author : DNS-OARC (https://www.dns-oarc.net)
  * License : Apache
  * Homepage : https://www.dns-oarc.net/tools/dnsperf

(the following is copied from the website, not the actual package
description to be used)

dnsperf and resperf are free tools developed by Nominum/Akamai
(2006-2018) and DNS-OARC (since 2019) that make it simple to gather
accurate latency and throughput metrics for Domain Name Service (DNS).
These tools are easy-to-use and simulate typical Internet, so network
operators can benchmark their naming and addressing infrastructure and
plan for upgrades. The latest version of the dnsperf and resperf can be
used with test files that include IPv6 queries.

dnsperf “self-paces” the DNS query load to simulate network conditions.
New features in dnsperf improve the precision of latency measurements
and allow for per packet per-query latency reporting is possible.
dnsperf is now multithreaded, multiple dnsperf clients can be supported
in multicore systems (each client requires two cores). The output of
dnsperf has also been improved so it is more concise and useful. Latency
data can be used to make detailed graphs, so it is simple for network
operators to take advantage of the data.

resperf systematically increases the query rate and monitors the
response rate to simulate caching DNS services.

Regards,
Daniel

--- End Message ---
--- Begin Message ---
Source: dnsperf
Source-Version: 2.4.2+debian-1
Done: Daniel Baumann <daniel.baumann@progress-linux.org>

We believe that the bug you reported is fixed in the latest version of
dnsperf, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 984535@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Baumann <daniel.baumann@progress-linux.org> (supplier of updated dnsperf package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 04 Mar 2021 19:40:24 +0100
Source: dnsperf
Binary: dnsperf dnsperf-dbgsym
Architecture: source amd64
Version: 2.4.2+debian-1
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann <daniel.baumann@progress-linux.org>
Changed-By: Daniel Baumann <daniel.baumann@progress-linux.org>
Description:
 dnsperf    - DNS Performance Testing Tool
Closes: 984535
Changes:
 dnsperf (2.4.2+debian-1) sid; urgency=medium
 .
   * Initial upload to sid (Closes: #984535).
   * Rebuilding upstream tarball without debian directory.
Checksums-Sha1:
 2b7a9052d6332c55ee6b3c40b10b0baeec0623b7 1983 dnsperf_2.4.2+debian-1.dsc
 4024a41fa3d2ca3a154d1f695bb0d37e80c308fb 62472 dnsperf_2.4.2+debian.orig.tar.xz
 1e67b89806a225075f7edfb9d20f2cfe9164afc6 1976 dnsperf_2.4.2+debian-1.debian.tar.xz
 416999c632317d9063fc60f3cbf1e4661df28dbd 126568 dnsperf-dbgsym_2.4.2+debian-1_amd64.deb
 5ebd85bd4928a0d8f88eb16604a9341dee0365d2 6191 dnsperf_2.4.2+debian-1_amd64.buildinfo
 257a4266ad7563b15ed2fecd3a847c3fdc8c84e9 61772 dnsperf_2.4.2+debian-1_amd64.deb
Checksums-Sha256:
 36e8ecdc649a8b55599c0651e911824db4ee96ad9a60706a4bc1bf8ed09adbd6 1983 dnsperf_2.4.2+debian-1.dsc
 14e6eee1e7992f56719b1c8b3580a6552b1092c98f22c2eaef6096b40b3cef2c 62472 dnsperf_2.4.2+debian.orig.tar.xz
 41dba5da993c055885360618c2fec6c71d13036f475ea509e2a14cb21efb43e7 1976 dnsperf_2.4.2+debian-1.debian.tar.xz
 b6803a64a3f3f26453eb26cdfd80379b0eab99d4f87ef36da9951de7f9e93515 126568 dnsperf-dbgsym_2.4.2+debian-1_amd64.deb
 3af280a66f5564f29678e8d360feed3a98c7a03637ba7d06a301f39880c3f672 6191 dnsperf_2.4.2+debian-1_amd64.buildinfo
 868c6867f2b3579e0d4f10f24513ad17ba4b46ed2f2832ec06594cce2d4363d6 61772 dnsperf_2.4.2+debian-1_amd64.deb
Files:
 5360a062e6881f33099b64e4bca03341 1983 utils optional dnsperf_2.4.2+debian-1.dsc
 b504a1cfc232a53b80a68fb629875725 62472 utils optional dnsperf_2.4.2+debian.orig.tar.xz
 704acd80c4336fc00ac701b1f7146653 1976 utils optional dnsperf_2.4.2+debian-1.debian.tar.xz
 9fb0c029b6ad726a80c1a7e2e3b31293 126568 debug optional dnsperf-dbgsym_2.4.2+debian-1_amd64.deb
 3818ae68ce7ed3ed560ba8fff7301837 6191 utils optional dnsperf_2.4.2+debian-1_amd64.buildinfo
 ea8a78e64fdf57bc4d8bebddcc000f2e 61772 utils optional dnsperf_2.4.2+debian-1_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmBBMJwACgkQVc8b+Yar
ucfEghAAwreaNfGZ2bs++9ypb8YZM2CXPAtOE0bAsYe/1wxf+iIiVvlCyGvr6gSk
c4qSL7G79guNxFdc/hJD9F2BW5wtxPsUkIsNw7fMDV9ocRTjrOx+kDxFL3+Dk3P2
mBsPOe6r0VeyKl8z1RFkm4hVcLixLn+gCMUkE3xVUkR0wNl+9qx1xGi/6kgYyF4y
NZOGHB1T0kCAukShmnxMpelos+eS1fExYHwMkTmH5D1nG2zz2gV1f3uLm+2YfRB5
aiV2yAZsXSJTnEmo2/bwzu+FRqR6vQqC41q4B+NqJmZpGbIDpBoI2aBE0/JWZXJJ
6W7y4z2KYy2+oqpT14+n6k66O9guWo3jsQrRAeq6BsCSjc0yZ+g3PgTLSJp8nMsr
QUbRJmwQAjB1pePfH8MGaQyBCEtvL+KupmixoXhdEiHjIwgcp8qwf1ZXpOUWRk9m
qN1nj4lvI3CsavM9epnTHpXVoWmoTXDYr1/zrcut08LhUyZbZ5AJVrXgeGxCNYW/
J/zWB01oHMGxoYFxSbUD+rLjyP0xnGLOTYe8dfobr1273tEYQsuyj+7Aq8KocUqM
V84k9A3VqtuHym+TzRgNamlTDXyI9KG586ez4hvRP0yOHaQnUg7DJAfgY6qu9RMX
B+yL21xY0SOCriDzOFUnZZ9Uq8SU92yBoKgTiTJtS4J0/nh13VM=
=8GRF
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: