"FutureWarning: apt API not stable yet" during upgrade

[Paul van Genderen]

Launchpad OOPSes when I try to "Nominate for release"

TEST CASE:
1. use hardy
2. run do-release-upgrade --proposed
3. verify that the "apt API not stable yet" line is no longer there

Binary package hint: update-manager

When upgrading a Xen domain with Ubuntu 8.04 to lucid using do-release-upgrade -d, it gave this e̶r̶r̶o̶r̶ warning:

E̶x̶c̶e̶p̶t̶i̶o̶n̶ ̶d̶u̶r̶i̶n̶g̶ ̶p̶m̶.̶D̶o̶I̶n̶s̶t̶a̶l̶l̶(̶)̶:̶ ̶ ̶E̶:̶I̶n̶t̶e̶r̶n̶a̶l̶ ̶E̶r̶r̶o̶r̶,̶ ̶C̶o̶u̶l̶d̶ ̶n̶o̶t̶ ̶p̶e̶r̶f̶o̶r̶m̶ ̶i̶m̶m̶e̶d̶i̶a̶t̶e̶ ̶c̶o̶n̶f̶i̶g̶u̶r̶a̶t̶i̶o̶n̶ ̶(̶2̶)̶ ̶o̶n̶ ̶l̶i̶b̶c̶6

C̶o̶u̶l̶d̶ ̶n̶o̶t̶ ̶i̶n̶s̶t̶a̶l̶l̶ ̶t̶h̶e̶ ̶u̶p̶g̶r̶a̶d̶e̶s̶

T̶h̶e̶ ̶u̶p̶g̶r̶a̶d̶e̶ ̶i̶s̶ ̶n̶o̶w̶ ̶a̶b̶o̶r̶t̶e̶d̶.̶ ̶Y̶o̶u̶r̶ ̶s̶y̶s̶t̶e̶m̶ ̶c̶o̶u̶l̶d̶ ̶b̶e̶ ̶i̶n̶ ̶a̶n̶ ̶u̶n̶u̶s̶a̶b̶l̶e̶
s̶t̶a̶t̶e̶.̶ ̶A̶ ̶r̶e̶c̶o̶v̶e̶r̶y̶ ̶w̶i̶l̶l̶ ̶r̶u̶n̶ ̶n̶o̶w̶ ̶(̶d̶p̶k̶g̶ ̶-̶-̶c̶o̶n̶f̶i̶g̶u̶r̶e̶ ̶-̶a̶)̶.̶

P̶l̶e̶a̶s̶e̶ ̶r̶e̶p̶o̶r̶t̶ ̶t̶h̶i̶s̶ ̶b̶u̶g̶ ̶a̶g̶a̶i̶n̶s̶t̶ ̶t̶h̶e̶ ̶'̶u̶p̶d̶a̶t̶e̶-̶m̶a̶n̶a̶g̶e̶r̶'̶ ̶p̶a̶c̶k̶a̶g̶e̶ ̶a̶n̶d̶
i̶n̶c̶l̶u̶d̶e̶ ̶t̶h̶e̶ ̶f̶i̶l̶e̶s̶ ̶i̶n̶ ̶/̶v̶a̶r̶/̶l̶o̶g̶/̶d̶i̶s̶t̶-̶u̶p̶g̶r̶a̶d̶e̶/̶ ̶i̶n̶ ̶t̶h̶e̶ ̶b̶u̶g̶ ̶r̶e̶p̶o̶r̶t̶.̶
i̶n̶s̶t̶a̶l̶l̶A̶r̶c̶h̶i̶v̶e̶s̶(̶)̶ ̶f̶a̶i̶l̶e̶d̶ ̶

/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)

[Nathan Stratton Treadway (nathanst)]

I also got this message when attempting to upgrade from Hardy to Lucid using "do-release-upgrade -d" .

I noticed that /usr/bin/do-release-upgrade script on my system contains the line
    warnings.filterwarnings("ignore", "apt API not stable yet", FutureWarning)
(right near the top), but the "lucid" script that gets extracted out of the downloaded lucid.tar.gz file (and unpacked under a /tmp/tmp*/ directory) does not include such a line.

(The DistUpgradeMain.py that is also extracted from that tar file has a different filterwarnings() call, but doesn't include one for "apt API not stable yet".)

[Paul van Genderen (paulvg)]

Adding that warning line to the DistUpgradeMain.py script solved the problem, thanks!

[Nathan Stratton Treadway (nathanst)]

(Note: to avoid any possible confusion, I should mention that the "E:Internal Error, Could not perform immediate configuration (2) on libc6" message, and the resulting termination of the upgrade process, actually have nothing to do with the "apt API not stable yet" message. [The title of this bug only mentions the latter, but the bug report includes both sets of error messages, which might give the impression that they were related.]

The "E: Internal Error" message was caused by a dependency loop [one involving the libc6 package], which has recently been resolved via a new version of the "findutils" package, as discussed in bug #533638.)

[Nathan Stratton Treadway (nathanst)]

Interestingly, I see that several other .py files found in that same directory as DistUpgradeMain.py do already include the
   warnings.filterwarnings("ignore", "apt API not stable yet", FutureWarning)
line, though DistUpgradeMain.py itself does not (at least as of version 1:0.133.6).

[Nathan Stratton Treadway (nathanst)]

I just tried running a new test of the Hardy -> Lucid upgrade using "do-release-upgrade -d", and this time I got the FutureWarning message right at the beginning of the upgrade process (rather than at the end just before aborting due to an error condition):

==================
# do-release-upgrade -d
Checking for a new ubuntu release
Done Upgrade tool signature
Done Upgrade tool
Done downloading
extracting 'lucid.tar.gz'
authenticate 'lucid.tar.gz' against 'lucid.tar.gz.gpg'
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
tar: Removing leading `/' from member names

Reading cache

Checking package manager

Continue running under SSH?
[....]
==================

The /tmp/*/DistUpgradeVersion.py file contains
VERSION='0.134.7

[Michael Gras (virtualmischa)]

Same error for me. I wanted to update from 8.04 to 10.04 via ssh and same warning occured. It happened on the new installed version of Ubuntu. No other software was installed so far.

[Alberto (apedraza)]

Same error here. Trying to update from Hardy to Lucid via ssh.

Error authenticating some packages

It was not possible to authenticate some packages. This may be a
transient network problem. You may want to try again later. See below
for a list of unauthenticated packages.

apt
apt-transport-https
apt-utils
ghostscript
ghostscript-x
grub-common
gs
gs-common
gs-esp
libapache2-mod-php5
libcups2
libcupsimage2
libgl1-mesa-dev
libgl1-mesa-glx
libglib2.0-0
libglib2.0-data
libglib2.0-dev
libglu1-mesa
libglu1-mesa-dev
libgs8
libgtk2.0-0
libgtk2.0-bin
libgtk2.0-common
librsvg2-2
mesa-common-dev
mountall
openssh-client
openssh-server
php5-common
python-apt
tzdata
update-manager-core

Restoring original system state

Aborting
Reading package lists: Donehardy-security/multiverse Packages: 98
Reading state information: Done
Reading state information: Done
Reading state information: Done

[Martin Pitt (pitti)]

Ah, I suppose this is irrelevant for maverick, as it only affects hardy upgrades.

[Martin Pitt (pitti)]

Accepted update-manager into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Jean-Baptiste Lallement (jibel)]

SRU verification for Lucid:
I have reproduced the problem with update-manager 1:0.134.9 in lucid-updates and have verified that the version of update-manager 1:0.134.10 in -proposed fixes the issue.

To reproduce I had to manually add a lucid record to the local meta-release-lts file because http://changelogs.ubuntu.com/meta-release-lts doesn't contain such entry (bug 573010) and the development release point to the version of the upgrader in -proposed.

Marking as verification-done

[Launchpad Janitor (janitor)]

This bug was fixed in the package update-manager - 1:0.134.10

---------------
update-manager (1:0.134.10) lucid-proposed; urgency=low

  * DistUpgrade/DistUpgradeMain.py:
    - add filter for "apt API not stable yet" warning (for
      hardy->lucid upgrades) (LP: #534200)
  * UpdateManager/Core/utils.py:
    - fix url_downloadable and add tests, based on the patch from
      Paulo Albuquerque, many thanks (LP: #396187)
  * DistUpgrade/DistUpgradeViewNonInteractive.py:
    - make the dpkg-status file parser more robust against
      unexpected data (LP: #574837)
 -- Michael Vogt <email address hidden> Wed, 30 Jun 2010 16:01:01 +0200