After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 403509 - hal-kernel-includes patch does not apply cleany
hal-kernel-includes patch does not apply cleany
Status: RESOLVED FIXED
Product: GARNOME
Classification: Deprecated
Component: general
2.17.x
Other All
: Normal blocker
: ---
Assigned To: GARNOME Maintainers
garnome list
Depends on:
Blocks:
 
 
Reported: 2007-02-02 09:40 UTC by Yiannis Mavroukakis
Modified: 2007-02-22 21:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Yiannis Mavroukakis 2007-02-02 09:40:21 UTC 
Please describe the problem:
On Slackware the hal-kernel-includes patch is not applied in configure as a reversed or previously applied patch is detected. There are also further problems with the patch down the patch line

can't find file to patch at input line 152
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --speed-large-files --minimal -Npru hal-0.5.4.orig/hald/linux2/probing/probe-input.c hal-0.5.4/hald/linux2/probing/probe-input.c
|--- hal-0.5.4.orig/hald/linux2/probing/probe-input.c   2005-08-24 05:59:45.000000000 +1000
|+++ hal-0.5.4/hald/linux2/probing/probe-input.c        2005-09-19 16:18:15.422550640 +1000
--------------------------



Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?
Yes

Other information:
Comment 1 Karsten Bräckelmann 2007-02-22 21:03:12 UTC 
2007-02-22  Karsten Bräckelmann  <guenther@rudersport.de>

        * freedesktop/hal: Removing the reportedly unnecessary and yet
        again broken hal-kernel-includes.diff patch. Fixes bug 403509.


Fixed in SVN. See this thread for the full discussion:
http://mail.gnome.org/archives/garnome-list/2007-February/thread.html#00003

Thanks for reporting this issue and the great discussion on list. :)