> You should be able to get out of that apt state by just calling
> «dpkg --configure --pending».
great -- thanks. FWIW This indeed allowed to mitigate it.
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist,Psycho
Hi!
On Fri, 2015-01-23 at 17:01:34 +, Simon McVittie wrote:
> Control: tags 776063 + moreinfo
I think this one should be merged with the other dbus+triggers+apt
bugs.
> On 23/01/15 14:43, Niels Thykier wrote:
> > On Fri, 23 Jan 2015 09:07:37 -0500 Yaroslav Halchenko
> > wrote:
> >> Decided
; > against corporate policy) make this public, you can also mail it just
> > to me – in case you find this acceptable as a compromise of course).
> /var/log/apt/history.log, /var/log/apt/term.log are probably also
> interesting information.
http://www.onerussian.com/tmp/dpkg.log.201
Control: tags 776063 + moreinfo
On 23/01/15 14:43, Niels Thykier wrote:
> On Fri, 23 Jan 2015 09:07:37 -0500 Yaroslav Halchenko
> wrote:
>> Decided to upgrade my jessie/sid system today to see if remedy for hangouts
>> not
>> working came about (#770659) and upgrade failed because of dbus.
>
> T
gt; debugging? Last time we saw this issue, we were unable to reproduce it
> due to lack of information.
Here are complete dpkg.log and apt logs I have which includes
today attempt to upgrade
http://www.onerussian.com/tmp/dpkg.log.20150123
http://www.onerussian.com/tmp/apt-term.log.20150123
ht
On Fri, 23 Jan 2015 09:07:37 -0500 Yaroslav Halchenko
wrote:
> Package: dbus
> Version: 1.8.12-1
> Severity: critical
>
> Decided to upgrade my jessie/sid system today to see if remedy for hangouts
> not
> working came about (#770659) and upgrade failed because of dbus. Here is an
> output of
6 matches
Mail list logo
