Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 82529 - glibc can't be patched with 6010_alpha_2.3.2-pwrite.patch
Summary: glibc can't be patched with 6010_alpha_2.3.2-pwrite.patch
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Hardened (show other bugs)
Hardware: Alpha Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
: 82530 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-02-18 22:57 UTC by oh sanghoon
Modified: 2005-05-28 08:50 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description oh sanghoon 2005-02-18 22:57:34 UTC 
glibc 2.3.4 20050125(-r1)  can't be patched with 6010_alpha_2.3.2-pwrite.patch

Reproducible: Always
Steps to Reproduce:
1. emerge glibc-2.3.4.20050125-r1.ebuild
2. failed patch with 6010_alpha_2.3.2-pwrite.patch
3. stop emergeing



Expected Results:  
glibc-2.3.4.20041102.ebuild

patch log.

PATCH COMMAND:  patch -p4 -g0 <
/var/tmp/portage/glibc-2.3.4.20050125-r1/work/patches/6010_alpha_2.3.2-pwrite.patch

=========================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- glibc-2.3.2/sysdeps/unix/sysv/linux/alpha/syscalls.list.old	2003-11-01
19:21:19.000000000 -0500
|+++ glibc-2.3.2/sysdeps/unix/sysv/linux/alpha/syscalls.list	2003-11-01
19:21:25.000000000 -0500
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
Comment 1 solar (RETIRED) gentoo-dev 2005-02-19 02:49:11 UTC 
*** Bug 82530 has been marked as a duplicate of this bug. ***
Comment 2 solar (RETIRED) gentoo-dev 2005-02-19 02:49:51 UTC 
Why is this bug assigned to hardened? (twice at that?)
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2005-05-28 08:50:32 UTC 
Is this still a problem?