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

Bug#679419: marked as done (apt: Funny time overflow when clock is set during apt-get update)

Your message dated Thu, 30 Jan 2025 12:36:30 +0100
with message-id <ckmp7knw5uavaf4nswmgdiaiqmnrz3gjvbn6uc5s24q7vwpnzl@43tspmwzdity>
and subject line Re: Bug#679419: apt: Funny time overflow when clock is set during apt-get update
has caused the Debian Bug report #679419,
regarding apt: Funny time overflow when clock is set during apt-get update
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.)


-- 
679419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679419
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.9.6
Severity: minor

I just run "pon" immediately followd by "apt-get update". Since the
computer is running 1 hour fast (i.e. one hour in the future) the
clock was set while apt-get update was running (one hour back). The
result was:
root@sneo:~# apt-get update
Holen: 1 http://127.0.0.1 wheezy InRelease [190 kB]
Holen: 2 http://127.0.0.1 sid InRelease [238 kB]
...
Holen: 26 http://127.0.0.1 sid/main 2012-06-28-0817.04.pdiff [29,9 kB]
Es wurden 661 kB in 213503982334601 d 6 h 0 min 46 s geholt (0 B/s).
Paketlisten werden gelesen... Fertig

This would be 584 billion years if I counted the digits correctly ;-))

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.15sneo.01-grsec (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apt depends on:
ii  debian-archive-keyring  2012.4
ii  gnupg                   1.4.12-4+b1
ii  libapt-pkg4.12          0.9.6
ii  libc6                   2.13-33
ii  libgcc1                 1:4.7.0-8
ii  libstdc++6              4.7.0-8

apt recommends no packages.

Versions of packages apt suggests:
pn  apt-doc     <none>
ii  aptitude    0.6.8-1
ii  dpkg-dev    1.16.3
ii  python-apt  0.8.4
ii  synaptic    0.75.12
ii  xz-utils    5.1.1alpha+20110809-3

-- no debconf information

-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Version: 1.7.0~alpha1

apt (1.7.0~alpha1) experimental; urgency=medium
[…]
  [ David Kalnischkies ]
[…]
  * Use a steady clock source for progress reporting
[…]
 -- Julian Andres Klode <jak@debian.org>  Mon, 25 Jun 2018 17:12:30 +0200

Am Tue, Jan 28, 2025 at 09:41:47PM +0100, schrieb Kamil Ignacak:
> This issue is most probably fixed with https://salsa.debian.org/apt-team/apt/-/commit/79b61ae7673eb6213493e2cb202f0d70c390932d.
> 
> There are also other commits that address the problem of durations (see
> https://salsa.debian.org/apt-team/apt/-/commit/ef50424be1586b91a99d28bf5108f3999cc908fb),
> but 79b61ae seems to be the main one.
> 
> I was able to reproduce the issue in a last commit before 79b61ae, i.e. in
> 484babb.

As the author of those commits I can say that it was indeed the
intention to fix this problem class by moving from the system clock
(that can change "at random") to a clock that monotonically ticks
forward (not only in progress reporting, but that is most visible
I guess).

I am therefore closing this report with the version of the initial
change (even if that included a bug also noted by Kamil above fixed
2 years later -- included since 1.9.10).

Feel free to reopen (or in this case perhaps better report a new bug)
if you still encounter this type of problem of course.


Also, Kamil, feel free to close bugs with your analyse directly!
After all, you verified them. In the unlikely event that something was
missed and/or more work is needed its easy enough to reopen a report.


Thanks & Best regards,

David Kalnischkies

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: