[Bug 346386] Re: [MASTER] Update fails with invalid package fileswith "Encountered a section with no Package: header"
Kayode Odusote
odusote.kayode at gmail.com
Sat Oct 13 05:44:48 UTC 2012
No CHOICE. Who does one reply to?
On 10/12/12, Les H <les.horrocks at btconnect.com> wrote:
> Couldn't we ask everyone to stop using the "reply to all" button?
>
> ----- Original Message -----
> From: "David Parry" <d.dry.parry at gmail.com>
> To: <les.horrocks at btconnect.com>
> Sent: Friday, October 12, 2012 2:00 PM
> Subject: Re: [Bug 346386] Re: [MASTER] Update fails with invalid package
> fileswith "Encountered a section with no Package: header"
>
>
> sudo before the command then you will
> David Parry
>
>
> On Fri, Oct 12, 2012 at 3:25 AM, Chris Hunt <346386 at bugs.launchpad.net>
> wrote:
>> Brian
>> Thanks for this.
>> When I go to delete the file I don’t have permission.
>> Why is that, can you help.
>> Thanks
>> Chris Hunt
>>
>>
>> On 10/10/12 22:17, Brian Murray wrote:
>>> ** Changed in: apt (Ubuntu Precise)
>>> Status: Confirmed => Fix Committed
>>>
>>> ** Changed in: apt (Ubuntu Precise)
>>> Importance: Undecided => High
>>>
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1064994).
>> https://bugs.launchpad.net/bugs/346386
>>
>> Title:
>> [MASTER] Update fails with invalid package files with "Encountered a
>> section with no Package: header"
>>
>> Status in “apt” package in Ubuntu:
>> Fix Released
>> Status in “apt” source package in Natty:
>> Fix Released
>> Status in “apt” source package in Precise:
>> Fix Committed
>> Status in “apt” package in Debian:
>> Fix Released
>>
>> Bug description:
>> Binary package hint: adept-updater
>>
>> Pertinent data printed when attempting to run Updater as follows:
>>
>> An unresolvable problem occurred while initializing the package
>> information.
>>
>> Please report this bug against the 'update-manager' package and
>> include the following error message:
>>
>> 'E:Encountered a section with no Package: header, E:Problem with
>> MergeList /var/lib/apt/lists/us.archive.ubuntu
>> .com_ubuntu_dists_intrepid_universe_binary-amd64_Packages, E:The
>> package lists or status file could not be parsed or opened.'
>>
>> WORKAROUND:
>> Remove problematic files from /var/lib/apt/lists/ and rerun apt-get
>> update.
>>
>> In the event that one is connected to a network with a proxy server
>> that returns html pages (like a web page requesting you to login) and
>> not package list files. Those html files will get downloaded to
>> /var/lib/apt/lists/ and prevent someone from using a package manager
>> until the problem html pages are removed.
>>
>> TEST CASE:
>> 1) download the dummy-proxy attachment from this bug report
>> 2) run dummy-proxy (python dummy-proxy) on a precise system (this
>> simulates a proxy that is not allowing access to archive.ubuntu.com and
>> gives you garbage html instead)
>> 3) Execute 'http://localhost:8080 sudo apt-get update' in a terminal
>> 4) Observe the following error messages in your terminal:
>> W: GPG error: http://archive.ubuntu.com precise InRelease: File
>> /var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_precise_InRelease
>>
>> doesn't start with a clearsigned message
>> W: Failed to fetch
>> http://archive.ubuntu.com/ubuntu/dists/precise/multiverse/i18n/Index No
>> Hash entry in Release file /var/lib/apt/lists/partial/
>> archive.ubuntu.com_ubuntu_dists_precise_multiverse_i18n_Index
>> W: Failed to fetch
>> gzip:/var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_precise_multiverse_source_Sources
>>
>> Encountered a section with no Package: header
>> 5) Stop dummy-proxy
>> 6) Execute 'sudo apt-get update' in a terminal
>> 7) Observe the following error message:
>> Reading package lists... Done
>> W: GPG error: http://archive.ubuntu.com precise Release: The following
>> signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic
>>
>> Signing Key <ftpmaster at ubuntu.com>
>> 8) Remove the problematic files in /var/lib/apt/lists (sudo rm
>> /var/lib/apt/lists/*)
>>
>> Install apt from -proposed
>> 1) run dummy-proxy (python dummy-proxy) on a precise system (this
>> simulates a proxy that is not allowing access to archive.ubuntu.com and
>> gives you garbarge html instead)
>> 2) Execute 'http://localhost:8080 sudo apt-get update' in a terminal
>> 3) Observe the following error messages in your terminal:
>> W: A error occurred during the signature verification. The repository is
>>
>> not updated and the previous index files will be used. GPG error: http://
>>
>> archive.ubuntu.com precise Release: The following signatures were invalid:
>>
>> NODATA 1 NODATA 2
>> W: Failed to fetch
>> http://archive.ubuntu.com/ubuntu/dists/precise/Release
>> W: Some index files failed to download. They have been ignored, or old
>> ones used instead.
>> 4) Stop dummy-proxy
>> 5) Execute 'sudo apt-get update' in a terminal
>> 6) Observe the update succeed
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/346386/+subscriptions
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1055368).
> https://bugs.launchpad.net/bugs/346386
>
> Title:
> [MASTER] Update fails with invalid package files with "Encountered a
> section with no Package: header"
>
> Status in “apt” package in Ubuntu:
> Fix Released
> Status in “apt” source package in Natty:
> Fix Released
> Status in “apt” source package in Precise:
> Fix Committed
> Status in “apt” package in Debian:
> Fix Released
>
> Bug description:
> Binary package hint: adept-updater
>
> Pertinent data printed when attempting to run Updater as follows:
>
> An unresolvable problem occurred while initializing the package
> information.
>
> Please report this bug against the 'update-manager' package and
> include the following error message:
>
> 'E:Encountered a section with no Package: header, E:Problem with
> MergeList /var/lib/apt/lists/us.archive.ubuntu
> .com_ubuntu_dists_intrepid_universe_binary-amd64_Packages, E:The
> package lists or status file could not be parsed or opened.'
>
> WORKAROUND:
> Remove problematic files from /var/lib/apt/lists/ and rerun apt-get
> update.
>
> In the event that one is connected to a network with a proxy server
> that returns html pages (like a web page requesting you to login) and
> not package list files. Those html files will get downloaded to
> /var/lib/apt/lists/ and prevent someone from using a package manager
> until the problem html pages are removed.
>
> TEST CASE:
> 1) download the dummy-proxy attachment from this bug report
> 2) run dummy-proxy (python dummy-proxy) on a precise system (this
> simulates a proxy that is not allowing access to archive.ubuntu.com and
> gives you garbage html instead)
> 3) Execute 'http://localhost:8080 sudo apt-get update' in a terminal
> 4) Observe the following error messages in your terminal:
> W: GPG error: http://archive.ubuntu.com precise InRelease: File
> /var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_precise_InRelease
>
> doesn't start with a clearsigned message
> W: Failed to fetch
> http://archive.ubuntu.com/ubuntu/dists/precise/multiverse/i18n/Index No
> Hash entry in Release file /var/lib/apt/lists/partial/
> archive.ubuntu.com_ubuntu_dists_precise_multiverse_i18n_Index
> W: Failed to fetch
> gzip:/var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_precise_multiverse_source_Sources
>
> Encountered a section with no Package: header
> 5) Stop dummy-proxy
> 6) Execute 'sudo apt-get update' in a terminal
> 7) Observe the following error message:
> Reading package lists... Done
> W: GPG error: http://archive.ubuntu.com precise Release: The following
> signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic
> Signing Key <ftpmaster at ubuntu.com>
> 8) Remove the problematic files in /var/lib/apt/lists (sudo rm
> /var/lib/apt/lists/*)
>
> Install apt from -proposed
> 1) run dummy-proxy (python dummy-proxy) on a precise system (this
> simulates a proxy that is not allowing access to archive.ubuntu.com and
> gives you garbarge html instead)
> 2) Execute 'http://localhost:8080 sudo apt-get update' in a terminal
> 3) Observe the following error messages in your terminal:
> W: A error occurred during the signature verification. The repository is
> not updated and the previous index files will be used. GPG error: http://
> archive.ubuntu.com precise Release: The following signatures were invalid:
> NODATA 1 NODATA 2
> W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/precise/Release
> W: Some index files failed to download. They have been ignored, or old
> ones used instead.
> 4) Stop dummy-proxy
> 5) Execute 'sudo apt-get update' in a terminal
> 6) Observe the update succeed
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/346386/+subscriptions
>
>
> Cordialement,
> M. Leslie Horrocks,
> 557 Lotissement La Cabro d'Or,
> Vieux Chemin d'Entrecasteaux,
> Carcès, 83570
> +33 (0) 489 670 312
> +33 (0) 667 245 935 (Mobile)
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1041914).
> https://bugs.launchpad.net/bugs/346386
>
> Title:
> [MASTER] Update fails with invalid package files with "Encountered a
> section with no Package: header"
>
> Status in “apt” package in Ubuntu:
> Fix Released
> Status in “apt” source package in Natty:
> Fix Released
> Status in “apt” source package in Precise:
> Fix Committed
> Status in “apt” package in Debian:
> Fix Released
>
> Bug description:
> Binary package hint: adept-updater
>
> Pertinent data printed when attempting to run Updater as follows:
>
> An unresolvable problem occurred while initializing the package
> information.
>
> Please report this bug against the 'update-manager' package and
> include the following error message:
>
> 'E:Encountered a section with no Package: header, E:Problem with
> MergeList /var/lib/apt/lists/us.archive.ubuntu
> .com_ubuntu_dists_intrepid_universe_binary-amd64_Packages, E:The
> package lists or status file could not be parsed or opened.'
>
> WORKAROUND:
> Remove problematic files from /var/lib/apt/lists/ and rerun apt-get
> update.
>
> In the event that one is connected to a network with a proxy server
> that returns html pages (like a web page requesting you to login) and
> not package list files. Those html files will get downloaded to
> /var/lib/apt/lists/ and prevent someone from using a package manager
> until the problem html pages are removed.
>
> TEST CASE:
> 1) download the dummy-proxy attachment from this bug report
> 2) run dummy-proxy (python dummy-proxy) on a precise system (this
> simulates a proxy that is not allowing access to archive.ubuntu.com and
> gives you garbage html instead)
> 3) Execute 'http://localhost:8080 sudo apt-get update' in a terminal
> 4) Observe the following error messages in your terminal:
> W: GPG error: http://archive.ubuntu.com precise InRelease: File
> /var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_precise_InRelease
> doesn't start with a clearsigned message
> W: Failed to fetch
> http://archive.ubuntu.com/ubuntu/dists/precise/multiverse/i18n/Index No
> Hash entry in Release file /var/lib/apt/lists/partial/
> archive.ubuntu.com_ubuntu_dists_precise_multiverse_i18n_Index
> W: Failed to fetch
> gzip:/var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_precise_multiverse_source_Sources
> Encountered a section with no Package: header
> 5) Stop dummy-proxy
> 6) Execute 'sudo apt-get update' in a terminal
> 7) Observe the following error message:
> Reading package lists... Done
> W: GPG error: http://archive.ubuntu.com precise Release: The following
> signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic
> Signing Key <ftpmaster at ubuntu.com>
> 8) Remove the problematic files in /var/lib/apt/lists (sudo rm
> /var/lib/apt/lists/*)
>
> Install apt from -proposed
> 1) run dummy-proxy (python dummy-proxy) on a precise system (this
> simulates a proxy that is not allowing access to archive.ubuntu.com and
> gives you garbarge html instead)
> 2) Execute 'http://localhost:8080 sudo apt-get update' in a terminal
> 3) Observe the following error messages in your terminal:
> W: A error occurred during the signature verification. The repository is
> not updated and the previous index files will be used. GPG error: http://
> archive.ubuntu.com precise Release: The following signatures were invalid:
> NODATA 1 NODATA 2
> W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/precise/Release
> W: Some index files failed to download. They have been ignored, or old
> ones used instead.
> 4) Stop dummy-proxy
> 5) Execute 'sudo apt-get update' in a terminal
> 6) Observe the update succeed
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/346386/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/346386
Title:
[MASTER] Update fails with invalid package files with "Encountered a
section with no Package: header"
Status in “apt” package in Ubuntu:
Fix Released
Status in “apt” source package in Natty:
Fix Released
Status in “apt” source package in Precise:
Fix Committed
Status in “apt” package in Debian:
Fix Released
Bug description:
Binary package hint: adept-updater
Pertinent data printed when attempting to run Updater as follows:
An unresolvable problem occurred while initializing the package
information.
Please report this bug against the 'update-manager' package and
include the following error message:
'E:Encountered a section with no Package: header, E:Problem with
MergeList /var/lib/apt/lists/us.archive.ubuntu
.com_ubuntu_dists_intrepid_universe_binary-amd64_Packages, E:The
package lists or status file could not be parsed or opened.'
WORKAROUND:
Remove problematic files from /var/lib/apt/lists/ and rerun apt-get update.
In the event that one is connected to a network with a proxy server
that returns html pages (like a web page requesting you to login) and
not package list files. Those html files will get downloaded to
/var/lib/apt/lists/ and prevent someone from using a package manager
until the problem html pages are removed.
TEST CASE:
1) download the dummy-proxy attachment from this bug report
2) run dummy-proxy (python dummy-proxy) on a precise system (this simulates a proxy that is not allowing access to archive.ubuntu.com and gives you garbage html instead)
3) Execute 'http://localhost:8080 sudo apt-get update' in a terminal
4) Observe the following error messages in your terminal:
W: GPG error: http://archive.ubuntu.com precise InRelease: File /var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_precise_InRelease doesn't start with a clearsigned message
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/precise/multiverse/i18n/Index No Hash entry in Release file /var/lib/apt/lists/partial/ archive.ubuntu.com_ubuntu_dists_precise_multiverse_i18n_Index
W: Failed to fetch gzip:/var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_precise_multiverse_source_Sources Encountered a section with no Package: header
5) Stop dummy-proxy
6) Execute 'sudo apt-get update' in a terminal
7) Observe the following error message:
Reading package lists... Done
W: GPG error: http://archive.ubuntu.com precise Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <ftpmaster at ubuntu.com>
8) Remove the problematic files in /var/lib/apt/lists (sudo rm /var/lib/apt/lists/*)
Install apt from -proposed
1) run dummy-proxy (python dummy-proxy) on a precise system (this simulates a proxy that is not allowing access to archive.ubuntu.com and gives you garbarge html instead)
2) Execute 'http://localhost:8080 sudo apt-get update' in a terminal
3) Observe the following error messages in your terminal:
W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http:// archive.ubuntu.com precise Release: The following signatures were invalid: NODATA 1 NODATA 2
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/precise/Release
W: Some index files failed to download. They have been ignored, or old ones used instead.
4) Stop dummy-proxy
5) Execute 'sudo apt-get update' in a terminal
6) Observe the update succeed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/346386/+subscriptions
More information about the foundations-bugs
mailing list