On Thu, 1 Sep 2016, Roland Rosenfeld wrote:
>
> Hi Cristian!
Roland,
> On Thu, 01 Sep 2016, Cristian Ionescu-Idbohrn wrote:
>
> In the meantime I did some testing with debconf configured with
> readline mode. Except that this is not as fluent to handle as the
> dialog frontend, everything works correct. But usually I'm asked
> during the upgrade, whether I want to keep the old version, use the
> maintainers version, show diffs or want to merge them.
>
> I'm a little surprised, that you aren't asked for input, while the
> debonf frontend is running on your system...
Right.
> > ,----
> > | Noticed that after migration to testin/stretch privoxy is taking with
> > | it even this problem. To reiterate...
> > |
> > | # apt-get install privoxy
> > | ...
> > | Preparing to unpack .../privoxy_3.0.25-2_amd64.deb ...
> > | [ ok ] Stopping filtering proxy server: privoxy.
> > | Unpacking privoxy (3.0.25-2) over (3.0.25-1) ...
> > | Processing triggers for readahead-fedora (2:1.5.6-5.2) ...
> > | Setting up privoxy (3.0.25-2) ...
> > | [ ok ] Starting filtering proxy server: privoxy.
> > |
> > | Progress: [ 42%]
> > [########################..................................]
> > `----
>
> Where does this progress bar come from?
apt.conf option:
Dpkg::Progress-Fancy "1";
> I don't know this personally. Maybe this is part of the problem,
> because it may block the interaction of debconf readline?
Could be. Been using it for about a year now, on several boxes, but
didn't notice any other package illbehave.
> > Looking at the process table where it's stuck:
> >
> > ,----
> > | root 24049 1.0 0.4 120888 77092 pts/74 S+ 11:34 0:01 |
> > \_ apt-get install privoxy
> > | root 24821 0.1 0.0 28012 15568 pts/76 Ss+ 11:34 0:00 |
> > \_ /usr/bin/dpkg --status-fd 48 --configure --pending
> > | root 24829 0.2 0.1 69688 20880 pts/76 S+ 11:34 0:00 |
> > \_ /usr/bin/perl -w /usr/share/debconf/frontend
> > /var/lib/dpkg/info/privoxy.postinst configure 3.0.25-1
> > | root 24860 0.0 0.0 0 0 pts/76 Z+ 11:34 0:00 |
> > \_ [privoxy.postins] <defunct>
> > `----
>
> I'd expect, that 24829 opens some kind of dialog/readline with you, if
> you cannot see this, it may be the center of the problem.
Right.
> > Cleanup:
> >
> > ,----
> > | # apt-get -f install
> > | Reading package lists... Done
> > | Building dependency tree
> > | Reading state information... Done
> > | 0 upgraded, 0 newly installed, 0 to remove and 98 not upgraded.
> > | 1 not fully installed or removed.
> > | After this operation, 0 B of additional disk space will be used.
> > | Setting up privoxy (3.0.25-2) ...
> > | [ ok ] Starting filtering proxy server: privoxy.
> > `----
>
> This time no debconf interaction, so it runs without problems.
>
> Maybe you could check, where upgrading from 3.0.25-1 to 3.0.25-2 works
> correct, if you install 3.0.25-2 via
> dpkg -i /var/cache/apt/archives/privoxy_3.0.25-2_amd64.de
> instead of using apt-get (which may use some external hooks).
Same, same, but different ;)
,----
| root 5478 0.5 0.7 138344 118304 pts/48 S+ 13:15 0:00 | \_
dpkg -i /var/cache/apt/archives/privoxy_3.0.25-2_amd64.deb
| root 5479 0.0 0.0 4304 720 pts/48 S+ 13:15 0:00 |
\_ sh -c (test -x /usr/lib/needrestart/dpkg-status &&
/usr/lib/needrestart/dpkg-status || cat > /dev/null)
| root 5480 0.0 0.0 4304 92 pts/48 S+ 13:15 0:00 |
| \_ sh -c (test -x /usr/lib/needrestart/dpkg-status &&
/usr/lib/needrestart/dpkg-status || cat > /dev/null)
| root 5481 0.0 0.0 4304 800 pts/48 S+ 13:15 0:00 |
| \_ /bin/sh /usr/lib/needrestart/dpkg-status
| root 5535 0.2 0.1 70404 21540 pts/48 S+ 13:15 0:00 |
\_ /usr/bin/perl -w /usr/share/debconf/frontend
/var/lib/dpkg/info/privoxy.postinst configure 3.0.25-2
| root 5543 0.0 0.0 0 0 pts/48 Z+ 13:15 0:00 |
\_ [privoxy.postins] <defunct>
`----
Yes, I do have needrestart installed too on a few boxes, but not all.
One of them (a testing/stretch) where needrestart isn't installed
misbehaves in the same manner.
I see no debconf dialog.
Killing 5535 gets me here:
,----
| dpkg: error processing package privoxy (--install):
| subprocess installed post-installation script was killed by signal
(Terminated)
| Processing triggers for systemd (231-5) ...
| Processing triggers for readahead-fedora (2:1.5.6-5.2) ...
| Processing triggers for doc-base (0.10.7) ...
| Processing 3 changed doc-base files, 2 added doc-base files...
| Registering documents with scrollkeeper...
| Processing triggers for man-db (2.7.5-1) ...
| Errors were encountered while processing:
| privoxy
`----
And:
# dpkg --configure -a
cleans it up.
> Sorry, I'm still digging in the fog, since I cannot reproduce the
> issue and do not fully understand, what goes wrong on your system...
No worries, as long as it's only me and there's a way out :)
Cheers,
--
Cristian
