Bug #8454
Test gdisk minimal fix for Jessie
100%
Files
Subtasks
History
#1 Updated by intrigeri 2014-12-18 11:33:57
- blocks
Bug #8455: Have gdisk fixed in Jessie added
#2 Updated by anonym 2015-01-16 19:50:33
The “minimal fix” can be found in Bug #8274#note-4.
#3 Updated by Anonymous 2015-01-16 20:05:49
- Assignee deleted (
anonym)
#4 Updated by Anonymous 2015-02-24 22:05:32
- % Done changed from 0 to 10
I’ve patched the source and am testing it.
#5 Updated by BitingBird 2015-02-24 22:36:59
- Status changed from Confirmed to In Progress
#6 Updated by Anonymous 2015-02-26 15:07:03
Waiting for a working Jessie ISO image, I’ll be on it again in about 2 days.
#7 Updated by intrigeri 2015-03-01 21:42:14
- Target version changed from Tails_2.0 to Tails_1.3.2
This needs to be fixed in Jessie soon, otherwise we’ll have to workaround it in nasty ways in our Installer.
#8 Updated by intrigeri 2015-03-01 21:44:59
- Due date set to 2015-03-05
#9 Updated by Anonymous 2015-03-04 16:31:51
Ok, here is what I did. I hope that’s enough testing:
I ran this deletion of the MBR before each test:
gdisk /dev/sdb
GPT fdisk (gdisk) version 0.8.10
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): x
Expert command (? for help): z
About to wipe out GPT on /dev/sdb. Proceed? (Y/N): y
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.
Blank out MBR? (Y/N): y
then with Jessie’s gdisk, 0.8.10-1, writing a new GPT MBR:
gdisk /dev/sdb
GPT fdisk (gdisk) version 0.8.10
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y
Command (? for help): w
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
Exit code:
# echo $?
1
now using a package I built with the patches from the relevant commit i get:
gdisk /dev/sdb
GPT fdisk (gdisk) version 0.8.10
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sdb.
The operation has completed successfully.
Exit code:
# echo $?
0
#10 Updated by Anonymous 2015-03-04 16:49:53
- File gdisk.debdiff added
- Assignee set to intrigeri
here is the debdiff, feel free to do whatever needs to be done with it.
#11 Updated by Anonymous 2015-03-04 17:09:51
- QA Check set to Ready for QA
#12 Updated by intrigeri 2015-03-04 21:04:18
- Status changed from In Progress to Resolved
- Assignee deleted (
intrigeri) - % Done changed from 10 to 100
- QA Check deleted (
Ready for QA)
Thanks. I’ve built on top of that and written a reproducer script, that I’ve run on Wheezy, Jessie, and Jessie + the fix. You’ll see the details on the Debian bug report that I’ve just sent.
Notes about the debdiff:
- you imported in
support.diff
unrelated changes that we didn’t mean to see tested, nor to even try to include in Jessie (hence the minimal in the ticket title, and the details are made clearer onBug #8274); thankfully that doesn’t invalidate your results :) - a debdiff should generally not include any local quilt artifacts (the
.pc
directory), but instead be built using debdiff run against the old and new.dsc
(although these days, git format-patch against the Vcs-Git is often preferred)
Cheers!
#13 Updated by BitingBird 2015-03-22 12:15:05
- Target version changed from Tails_1.3.2 to Tails_1.3.1