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

Bug#1054044: marked as done (iproute2: ss show wrong timer value in unit ms)

Your message dated Wed, 26 Mar 2025 19:46:59 +0100
with message-id <328356f89feba6e67929bf39f3fd077c19de7e66.camel@decadent.org.uk>
and subject line Re: iproute2: ss show wrong timer value in unit ms
has caused the Debian Bug report #1054044,
regarding iproute2: ss show wrong timer value in unit ms
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.)


-- 
1054044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054044
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: iproute2
Version: 5.10.0-4
Severity: normal
Tags: l10n upstream
X-Debbugs-Cc: 16a16j0q@duck.com

Dear Maintainer,

When using the ‘ss’ command with the ‘–options’ parameter to display
timers, times less than 9 seconds are displayed as ‘1.234ms’. However,
this actually represents 1 second and 234 milliseconds. The use of the
period (.) is quite confusing to me. It seems to be used as a digit
group separator(thousands separator). However, I am more familiar with
using the period as a decimal separator. Could this be an issue of
internationalization (i10n)?

-- System Information:
Debian Release: 11.8
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable-proposed-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-19-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages iproute2 depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  libbpf0                1:0.3-2
ii  libbsd0                0.11.3-1+deb11u1
ii  libc6                  2.31-13+deb11u7
ii  libcap2                1:2.44-1
ii  libcap2-bin            1:2.44-1
ii  libdb5.3               5.3.28+dfsg1-0.8
ii  libelf1                0.183-1
ii  libmnl0                1.0.4-3
ii  libselinux1            3.1-3
ii  libxtables12           1.8.7-1

Versions of packages iproute2 recommends:
pn  libatm1  <none>

Versions of packages iproute2 suggests:
pn  iproute2-doc  <none>

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
Version: 6.11.0-1

On Mon, 16 Oct 2023 23:41:00 +0800 douniwan5788 <16a16j0q@duck.com>
wrote:
> Package: iproute2
> Version: 5.10.0-4
> Severity: normal
> Tags: l10n upstream
> X-Debbugs-Cc: 16a16j0q@duck.com
> 
> Dear Maintainer,
> 
> When using the ‘ss’ command with the ‘–options’ parameter to display
> timers, times less than 9 seconds are displayed as ‘1.234ms’. However,
> this actually represents 1 second and 234 milliseconds. The use of the
> period (.) is quite confusing to me. It seems to be used as a digit
> group separator(thousands separator). However, I am more familiar with
> using the period as a decimal separator. Could this be an issue of
> internationalization (i10n)?

This was actually a logic error, nothing to do with localisation.

Fixed upstream in version 6.11.0.

Ben.

-- 
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
                                                      - Albert Einstein

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: