[Pan-users] Re: Preview "corrupted"

[roderick]

walt <address@hidden> writes:
> This is almost always caused by 'white-space corruption' in the patch
> file due to line-wrap during posting or downloading.  The line that
> 'patch' is complaining about should look like this:
> +      {
> 
> The + should be the first character in the line instead of in the
> middle somewhere.  The best remedy is to fetch the file again, being
> very careful to avoid any moves which will change the formatting, like
> making your browser window too narrow while cutting and pasting, etc.
> 
> One other remedy is nice to know about:  look up the -l flag in the
> patch man page, which was invented just for the problem you are having.
> 
> Yell if you have more problems.  Most likely you will :o)
> 

[bart_simpson]AI...CARAMBA...!!![/bart_simpson]

It works so far so good. The minor glitch was in your final instruction where
the ebuild command had pan-0.132-ebuild. When I first attempted I received: 

xuan pan-0.132 # ebuild /usr/portage/net-nntp/pan/pan-0.132-ebuild compile
install qmerge
'/usr/portage/net-nntp/pan/pan-0.132-ebuild' does not exist.

I hunted and found the correct name:

-rw-r--r-- 1 root root  180 2005-01-17 13:08 metadata.xml
-rw-r--r-- 1 root root 1.5K 2006-11-03 18:37 pan-0.14.2-r1.ebuild
-rw-r--r-- 1 root root 1.4K 2006-11-03 18:37 pan-0.14.2.ebuild
-rw-r--r-- 1 root root 1.6K 2006-11-03 18:37 pan-0.14.2.91-r3.ebuild
-rw-r--r-- 1 root root  973 2007-05-30 12:59 pan-0.131.ebuild
-rw-r--r-- 1 root root  973 2007-08-04 05:33 pan-0.132.ebuild
drwxr-xr-x 2 root root 4.0K 2007-08-04 05:36 files
-rw-r--r-- 1 root root 1.5K 2007-08-13 16:06 pan-0.14.2.91-r2.ebuild
-rw-r--r-- 1 root root 6.5K 2007-08-13 16:06 Manifest
-rw-r--r-- 1 root root  13K 2007-08-13 16:06 ChangeLog

Ran ebuild with the correct file name and it successfully compiled.

So to translate the patch into English, all the patch does is to run the diff
command, the (@@ -815,8 +815,15 @@) means go to line 815, in the targeted file
remove any line that are marked by (-) indicated in the patch file, then insert
all (+) lines as indicated in the patch file. Correct? If so, then if I know
what I was doing with how gdk_pixbuf works, I should be able to just edit the
body-pane.cc file itself instead of writing the actual patch? Since it worked, I
made notes in that patch file and saved it off my box for future reference.

As far as Sabayonlinux goes, the distro was the first one for me to successfully
installed with no problems on ALL my machines: two desktops and two notebooks.
SuSE, up to 10.2, could not run my notebook's Intel 3945 wireless but did worked
for others. Somehow just not mine. SL properly detected and configured my nvidia
graphics cards the desktops and the larger notebook. The 12 in. notebook just
uses the Intel integrated graphics.

The only issue with the latest Sabayonlinux install is with my new build that I
have the Intel E6550 and the Intel DG33BU matx board. Initially it would not
install at all. Then I looked at the CPU itself and it had EMT64 capability. On
a hunch I installed the Sabayonlinux 86_64 version and I am using the new box
today. Do not know why the EMT64 feature prevented the regular x86 version to
work. This distro is probably the best for any experienced linux user to run
Gentoo without compiling from sources, which I will attempt in the future.

Anyway...This had been an education and thanks *VERY* much for your help.