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

Bug#860931: marked as done (apt: disable dpkg "Reading database" progress indicator under unattended-upgrades)

Your message dated Sat, 25 Feb 2023 11:15:32 +0800
with message-id <cdeeb2998ffb258219e78b4fe13c891ee640bcac.camel@debian.org>
and subject line Re: apt: disable dpkg "Reading database" progress indicator under unattended-upgrades
has caused the Debian Bug report #860931,
regarding apt: disable dpkg "Reading database" progress indicator under unattended-upgrades
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.)


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

I have unattended-upgrades enabled, with the report emailed to me. I
also have Unattended-Upgrade::MinimalSteps enabled, which means apt is
run many times for each unattended-upgrades run. Each run of apt within
the unattended-upgrades report prints a 22-line dpkg progress
indicator. The progress indicator multiplied by each apt run gives many
many lines of output to wade through. It would be great if apt would
make dpkg only print the first half of last line before starting to
read and the 2nd half of the last line after the database is read.
AFAICT, this is caused by apt's Dpkg::Use-Pty config option defaulting
to true, instead of checking if stdout is a terminal and only turning
the option on if it is.

(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 123456 files and directories currently installed.)

-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 'testing-proposed-updates'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apt depends on:
ii  adduser                 3.115
ii  debian-archive-keyring  2014.3
ii  gpgv                    2.1.18-6
ii  init-system-helpers     1.47
ii  libapt-pkg5.0           1.4
ii  libc6                   2.24-9
ii  libgcc1                 1:6.3.0-12
ii  libstdc++6              6.3.0-12

Versions of packages apt recommends:
ii  gnupg   2.1.18-6
ii  gnupg1  1.4.21-2
ii  gnupg2  2.1.18-6

Versions of packages apt suggests:
pn  apt-doc         <none>
ii  aptitude        0.8.6-1
ii  dpkg-dev        1.18.23
ii  powermgmt-base  1.31+nmu1
ii  python-apt      1.4.0~beta2

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

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


--- End Message ---
--- Begin Message --- 
Source: unattended-upgrades
Source-Version: 1.10
Done: Balint Reczey <rbalint@ubuntu.com>

On Fri, 2023-02-24 at 15:27 +0100, Alexandre Detiste wrote:

> But it seams to be gone from Bookworm.
> 
> Can you check again ?

That seems correct indeed. The last time I had it was 2019-01-28
20:34:51 and 2019-01-29 14:18:42 didn't have it. Looking at my apt
history logs, in between those two I upgraded unattended-upgrades to
1.10, which has a related changelog entry, so closing the bug now.

   Start-Date: 2019-01-29  07:59:50
   Requested-By: pabs (1000)
   Upgrade: unattended-upgrades:amd64 (1.9, 1.10)
   End-Date: 2019-01-29  08:00:16
   
   unattended-upgrades (1.10) unstable; urgency=medium
   
     ...
     * Fix filtering out dpkg progress indicator (LP: #1599646) (Closes: #919407)
     ...
   
    -- Balint Reczey <rbalint@ubuntu.com>  Mon, 28 Jan 2019 21:35:26 +0700

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

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


--- End Message ---
Reply to: