[Bug 1048241]

Ubuntu Foundation's Bug Bot 1048241 at bugs.launchpad.net
Sun Sep 9 16:26:04 UTC 2012

*** This bug is a duplicate of bug 346386 ***

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your bug report it seems that you are
experiencing bug 346386.  This issue happens when you have tried to
update your package information when you are a network that didn't
return the right files.  This issue can be cleaned up by using the
following commands in a terminal:

1.) sudo rm /var/lib/apt/lists/*
2.) sudo apt-get update

Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please reopen the bug task if it was incorrect.]

** This bug has been marked a duplicate of bug 346386
   [MASTER] Update fails with invalid package files with "Encountered a section with no Package: header"

** Tags added: bot-comment

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.

  Encountered a section with no Package: header, impossible to update

Status in “update-manager” package in Ubuntu:

Bug description:
  I was told in the error I get to report this bug, so here goes :

  'E:Encountered a section with no Package: header, E:Problem with
  MergeList /var/lib/apt/lists/fr.archive.ubuntu
  .com_ubuntu_dists_precise_main_binary-amd64_Packages, E:Les listes de
  paquets ou le fichier « status » ne peuvent être analysés ou lus.'

  (last part in English : The package lists or status file could not be
  parsed or opened)

  As I was using for a week a wifi hotspot, I think this guy made a good point :

  Apparently there is an easy fix, haven't try it yet but this bug seems
  to occur with "normal" use of Ubuntu, I fear it may happened to less
  terminal-used people...

  My apologies, this error prevent me to tell you this package's version ! But I can tell for sure that the whole system was up to date by the first of September.

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list