Package: upgrade-reports
Followup-For: Bug #680626
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
On Mon, Aug 06, 2012 at 08:43:57AM +0200, Raphael Hertzog wrote:
Hello,
On Sun, 05 Aug 2012, Robert Luberda wrote:
Processing triggers for doc-base ...
/usr/bin/perl: symbol lookup error: /usr/lib/perl5/auto/UUID/UUID.so:
undefined symbol: Perl_xs_apiversion_bootcheck
dpkg: error
On Tue, Aug 7, 2012 at 14:37:10 +0200, berta...@ptitcanardnoir.org wrote:
However, when I ldd /usr/bin/python, it seems to be linked against libssl,
so I'm wondering if this bug isn't related to the python package missing a
dependency against libssl. It also seem to be linked against
Hello,
On Sun, 05 Aug 2012, Robert Luberda wrote:
Processing triggers for doc-base ...
/usr/bin/perl: symbol lookup error: /usr/lib/perl5/auto/UUID/UUID.so:
undefined symbol: Perl_xs_apiversion_bootcheck
dpkg: error processing doc-base (--unpack):
subprocess installed
Julien Cristau wrote:
As a variation on this theme (triggers being run when the triggered
package is unconfigured in the middle of an upgrade from squeeze to
wheezy), I just got the following:
Processing triggers for doc-base ...
/usr/bin/perl: symbol lookup error:
On Wed, Aug 01, 2012 at 12:22:22AM +0200, Julien Cristau wrote:
On Mon, Jul 16, 2012 at 14:19:03 +0200, Julien Cristau wrote:
On Sun, Jul 15, 2012 at 18:26:50 +0200, Guillem Jover wrote:
W/o having looked yet at the details I'd say this *seems* like #671711,
which I'm not planning on
On Fri, Aug 3, 2012 at 11:04:25 +0200, Bill Allombert wrote:
The current behaviour of triggers is well documented.
triggers.txt.gz says Packages in t-awaited and t-pending demand
satisfaction of their dependencies just like package in installed. The
current behaviour doesn't seem to satisfy
On Sat, Jul 7, 2012 at 14:51:32 +0200, bertagaz wrote:
In an attempt to test upgrading Squeeze to Wheezy now that the Big Wheezy
Freeze has come, it failed at the dist-upgrade step.
I installed a fresh Debian Squeeze and tested from it.
I wanted first to see if it would be possible to
On Wed, Aug 01, 2012 at 12:22:22AM +0200, Julien Cristau wrote:
On Mon, Jul 16, 2012 at 14:19:03 +0200, Julien Cristau wrote:
On Sun, Jul 15, 2012 at 18:26:50 +0200, Guillem Jover wrote:
W/o having looked yet at the details I'd say this *seems* like #671711,
which I'm not planning on
Hi,
berta...@ptitcanardnoir.org wrote:
I can understand the reasons not to fix the trigger bug, sounds like
something not that tricky.
However, given how it actually break the upgrade process, and will like
likely in the future, it would probably be a good idea to document
somewhere for
On Mon, Jul 16, 2012 at 14:19:03 +0200, Julien Cristau wrote:
On Sun, Jul 15, 2012 at 18:26:50 +0200, Guillem Jover wrote:
W/o having looked yet at the details I'd say this *seems* like #671711,
which I'm not planning on fixing for wheezy as it would introduce
regressions on other
On Sun, Jul 15, 2012 at 18:26:50 +0200, Guillem Jover wrote:
W/o having looked yet at the details I'd say this *seems* like #671711,
which I'm not planning on fixing for wheezy as it would introduce
regressions on other situations, and given that this behaviour has
been around since the
On Sat, Jul 7, 2012 at 14:51:32 +0200, bertagaz wrote:
In an attempt to test upgrading Squeeze to Wheezy now that the Big Wheezy
Freeze has come, it failed at the dist-upgrade step.
I installed a fresh Debian Squeeze and tested from it.
I wanted first to see if it would be possible to
On Sun, 2012-07-15 at 17:14:26 +0200, Julien Cristau wrote:
On Sat, Jul 7, 2012 at 14:51:32 +0200, bertagaz wrote:
In an attempt to test upgrading Squeeze to Wheezy now that the Big Wheezy
Freeze has come, it failed at the dist-upgrade step.
I installed a fresh Debian Squeeze and tested
Package: upgrade-reports
Severity: normal
Hi,
In an attempt to test upgrading Squeeze to Wheezy now that the Big Wheezy
Freeze has come, it failed at the dist-upgrade step.
I installed a fresh Debian Squeeze and tested from it.
I wanted first to see if it would be possible to upgrade with a
15 matches
Mail list logo
