Ubuntu
update-manager package

No Package Header

Asked by TheOldFellow

Could not initialise the package information

An unresolvable problem occurred while initialising the package information.

Please report this bug for the 'update-manager' package and try to include the following error message:

'E:Encountered a section with no Package: header, E:Problem with MergeList /var/lib/apt/lists/gb.archive.ubuntu.com_ubuntu_dists_oneiric_main_binary-amd64_Packages, E:The package lists or status file could not be parsed or opened.'

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu update-manager Edit question
Assignee:
No assignee Edit question
Solved by:
TheOldFellow
Solved:
Last query:
Last reply:

This question was originally filed as bug #870741.

Revision history for this message
Sam_ (and-sam) said : 		#1

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs.

Revision history for this message
Sam_ (and-sam) said : 		#2

In order to repair package configuration please follow the troubleshooting procedure.
https://help.ubuntu.com/community/PackageManagerTroubleshootingProcedure

Other resources.
https://answers.launchpad.net/ubuntu/+source/update-manager/+question/157283
https://answers.launchpad.net/ubuntu/+faq/1591

Revision history for this message
TheOldFellow (theoldfellow) said : 		#3

I fixed this easily (by a similar method to that you have supplied), but the message given by the application (update-manager) UNEQUIVOCALLY instructed me to raise this as a BUG. Wishing to help development I just obeyed the instruction.

Perhaps the true bug is in the update-manager 's error message? No reply needed.
R.