#448908 apt-get update does not use status-fd

Package:
apt
Source:
apt
Description:
commandline package manager
Submitter:
Joey Hess
Date:
2013-10-22 03:30:04 UTC
Severity:
wishlist
#448908#5
Date:
2007-11-01 17:47:50 UTC
From:
To:
Like the subject says, a debconf-apt-progress status-fd doesn't work
during apt-get update.

Compare:

debconf-apt-progress aptitude update # updates the progress bar througout
debconf-apt-progress apt-get update  # no progress bar updates

This may force us to use aptitude in more places in d-i..

#448908#10
Date:
2007-11-01 21:55:25 UTC
From:
To:
Otavio Salvador wrote:

Either bug #448908 or bug #448958 needs to be fixed before apt-setup can
display really nice detailed progress bars. My preference would be
fixing apt..

#448908#15
Date:
2013-10-21 03:20:56 UTC
From:
To:
This bug is still in Ubuntu 12.04 and I was wondering if its been fixed
yet? There is a workaround available by using aptitude but as this is not
part of a standard install now and apt-get is regarded as the preferred
method of installation, it would be better if this be fixed so that tools
like debconf-apt-progress work correctly with it.

#448908#20
Date:
2013-10-21 10:52:27 UTC
From:
To:
I presume yes as I can't reproduce it in debian/sid and in a fresh precise
chroot + universe + dialog (from the former) I see no progress from both…
[but the behavior of debconf-apt-progress seems to have changed since precise]

Some details on what you mean and how you reproduce it exactly might help.


Best regards

David Kalnischkies

#448908#25
Date:
2013-10-22 03:27:11 UTC
From:
To:
Please keep in mind that I'm not actually a sysadmin just a developer
attempting to do some bash shell scripting to create an installation script
for our application. So if something is unclear please let me know.

Having said that, I'm having trouble reproducing the error now myself even
though I ran into it repeatedly during testing previously. I started from a
stock standard Ubuntu 12.04 LTS 64-bit server install that is using the
default install settings. The aim is then that my script can be run to
install all necessary packages and configure the system so that our
application is installed correctly (its a Rails application plus extras).

The script is using whiptail (rather than dialog) and I'm using 'sudo
apt-get *operation*' as my way of handling packages and I'm using this in
conjunction with debconf-apt-progress to track operations. I was having
trouble with 'sudo apt-get update' but as I said I can't reproduce that bug
now myself, although there are some things with whiptail I've noticed that
don't work quite the same when comparing them in the regular terminal vs
when I ssh in with gnome terminal (for example a documented bug with the
whiptail infobox).



On 21 October 2013 21:52, David Kalnischkies <kalnischkies+debian@gmail.com>wrote: