On Tue, Apr 9, 2013 at 18:17:00 +0200, David Kalnischkies wrote:
> On Thu, Apr 4, 2013 at 10:46 PM, Julien Cristau <jcristau@debian.org> wrote:
> > On Sun, Mar 24, 2013 at 18:17:46 +0100, David Kalnischkies wrote:
> >
> >> Pictures^Wdpkg-status files or it didn't happen, as I said multiple times now.
> >>
> > You'll find the (compressed) status file attached.
> […]
> > E: Could not perform immediate configuration on 'openjdk-6-jre'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
>
> Thanks.
>
> After wasting a few days on this now I know at least who is at fault: me.
> And as I am not a dependency I pass the blame on to Java5 and OpenOffice.
>
> [I will spare you the details now, you will find some below as very long P.S.]
>
> I have done very few tests, but it seems like bringing openoffice.org-core
> back (as a transitional package) is the simplest workaround. If I remember
> right all status-files I have seen so far about this issue (not that many,
> but yeah) included openoffice (as I wondered why it was touched so early
> and wanted to investigate this after wheezy), so while this sounds indeed
> crazy I guess it would solve all known issues. Hence CC'ing the previous
> maintainers to gaining some intelligence on how feasible this is.
>
> (Such a transition package needs to break at least
> "openoffice.org-report-builder-bin" as it is otherwise not removed
> on upgrade. I have no idea what else / how depends should look like)
>
>
I've tried to build a transitional openoffice.org-core package, but
either I did it wrong (quite possible) or it doesn't help.
In the mean time I've applied the following change to the release notes:
Author: jcristau <jcristau@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Fri Apr 19 15:47:54 2013 +0000
upgrading: mention the 'Could not perform immediate configuration' issue
See Debian bug#645713
Signed-off-by: Julien Cristau <jcristau@debian.org>
git-svn-id: svn+ssh://svn.debian.org/svn/ddp/manuals/trunk/release-notes@9747 313b444b-1b9f-4f58-a734-7bb04f332e8d
diff --git a/en/upgrading.dbk b/en/upgrading.dbk
index 5628c6e..58d4bb8 100644
--- a/en/upgrading.dbk
+++ b/en/upgrading.dbk
@@ -933,6 +933,22 @@ The following sections describe known issues that might appear
during an upgrade to &releasename;.
</para>
+<section id="immediate-configure">
+<title>Dist-upgrade fails with "Could not perform immediate configuration"</title>
+<para>
+In some cases the <command>apt-get dist-upgrade</command> step can fail after
+downloading packages with:
+<screen>
+E: Could not perform immediate configuration on '<replaceable>package</replaceable>'. Please see man 5 apt.conf under APT::Immediate-Configure for details.
+</screen>
+</para>
+<para>
+If that happens, running <command>apt-get dist-upgrade -o
+APT::Immediate-Configure=0</command> instead should allow the upgrade
+to proceed.
+</para>
+</section>
+
<section arch="amd64" id="ia32libs">
<title>Transitioning from ia32-libs to multiarch</title>
<para>
I'm leaving this bug open for now because of the issue brought up by
Andreas, but if you want to reassign to release-notes that would be fine
with me.
Cheers,
Julien
Attachment:
signature.asc
Description: Digital signature