| 1 |
Ok, I attached all the information...including the patch output. |
| 2 |
|
| 3 |
|
| 4 |
I'm not sure why, but I might of gotten the bug number wrong or there was some kind of mix up with the bug numbers but it is bug #283470. |
| 5 |
|
| 6 |
|
| 7 |
----- Original Message ----- |
| 8 |
From: Mike Edenfield <kutulu@××××××.org> |
| 9 |
To: gentoo-hardened@l.g.o |
| 10 |
Cc: d hee <coolio@×××××.com> |
| 11 |
Sent: Saturday, July 23, 2011 8:30 PM |
| 12 |
Subject: Re: [gentoo-hardened] SELinux bughunt |
| 13 |
|
| 14 |
On 7/23/2011 4:54 PM, d hee wrote: |
| 15 |
> Can anything be done about this bug(that is originally 2 years old)? Since the patch no longer works, and I can not install glibc-2.13-r2 because of it's own problems, I can not create a Luks partition that I need to create. |
| 16 |
|
| 17 |
You did the right thing by posting an update to the bug tracker, but you missed a step from the error message: |
| 18 |
|
| 19 |
* Include in your bugreport the contents of: |
| 20 |
* |
| 21 |
* /var/tmp/portage/sys-fs/cryptsetup-1.1.3-r3/temp/newpatch.patch.out |
| 22 |
|
| 23 |
The patch is failing because the source is too different from what it's expecting; someone just needs to re-roll the patch. Posting the output of that file into the bug report may improve the chances of that happening quickly. |
| 24 |
|
| 25 |
--Mike |
Archives