Packages was corrupt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debootstrap (Debian) |
Fix Released
|
Unknown
|
|||
debootstrap (Ubuntu) |
Fix Released
|
High
|
Louis Bouchard | ||
Lucid |
Fix Released
|
Undecided
|
Louis Bouchard | ||
Precise |
Fix Released
|
Undecided
|
Louis Bouchard |
Bug Description
SRU justification :
Without this fix, unattended installation using preseed/kickstart files for 10.04.4 fails with a red screen and the message "Packages was corrupt"
Impact :
Impossible to preform unattended preseed installation in 10.04.4
Fix :
Backport and adapt the upstream debian fix in the following commit :
http://
Test Case :
1) Build new debootstrap-
2) Make a local copy of the 10.04.4 alternate cd
3) Use instructions in the following Wiki entry to rebuild the local archive with the modified .udeb package
https:/
4) Use PXE installation with the rebuilt local archive to verify that the new .udeb does a complete installation without the "Packages was corrupt" message
Regression :
This could only potentially affect netinst installation as no new .iso file will be created for Lucid. Moreover, this fix is already implemented in 12.04 LTS which runs debootstrap 1.0.39
Description of the problem :
Doing unattended kickstart-
I have to click "Continue" to go on.
The file in question (Packages.gz) is only 20 bytes bit, same file on ubuntu-
There is nothing problem with my download. My downloaded iso has md5 9fcc322536575dd
Either there is a problem with Packages.gz that should have some content, or it is a problem with the installer that detects an empty .gz-file as "corrupt". Anyways - it's a bug.
Changed in debian-installer (Ubuntu): | |
status: | Expired → Confirmed |
importance: | Undecided → High |
Changed in debootstrap (Ubuntu Lucid): | |
status: | New → In Progress |
Changed in debootstrap (Debian): | |
status: | Unknown → Fix Released |
description: | updated |
Changed in debootstrap (Ubuntu Lucid): | |
status: | In Progress → Fix Committed |
tags: | added: cts-client-review |
tags: | removed: cts-client-review |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem.
We have instructions on debugging some types of problems at http:// wiki.ubuntu. com/DebuggingPr ocedures
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!