| View previous topic :: View next topic |
| Author |
Message |
bsnipes
n00b
Joined: 30 May 2002
Posts: 37
|
 Posted: Fri Jun 14, 2002 8:21 pm Post subject: Invalid ebuild detection |
 |
|
OK. I went to install ethereal and it bombed because of problems with libpcap on the configure. I scrolled up and it said that the libpcap had been merged successfully. After peering around a bit I found out that he ebuild file for 0.7.1 version of libpcap was empty except for whitespace.
After looking at about 10 ebuild files the only common characters I saw in all of the nonempty ones was the '#' comment character. If all empty/whitespace only ebuild files are broken (valid assumption?), how about a script (probably much better than this one) to check on invalid ones and report them to the proper maintainer. I used find and got:
bash-2.05a# find ./ -name "*.ebuild" -exec grep -L \# {} \;
./app-text/jadetex/jadetex-2.20.ebuild
./app-text/noweb/noweb-2.9-r1.ebuild
./gnome-base/nautilus/nautilus-1.1.19.ebuild
./media-gfx/xv/xv-3.10a-r2.ebuild
./media-libs/libpng/libpng-1.2.3.ebuild
./net-ftp/gftp/gftp-2.0.11.ebuild
./net-ftp/gftp/gftp-2.0.12.ebuild
./net-libs/libpcap/libpcap-0.7.1.ebuild
./x11-misc/xwrits/xwrits-2.20.ebuild
./x11-misc/mowitz/mowitz-0.2.1.ebuild
bash-2.05a#
Brian Snipes |
|
| Back to top |
|
 |
delta407
Bodhisattva
Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL
|
| Posted: Tue Jun 18, 2002 12:05 am Post subject: |
|
|
Or, you could do this:
| Code: | | find -size 0b -name "*.ebuild" |
...which would simply display a list of all the zero-byte ebuilds. Or you could even do:
| Code: | | rm `find -size 0b -name "*.ebuild"` |
...which would remove the zero-byte ebuild files and allow Portage to function as normal. Currently, in my recently-synced tree, noweb-2.9-r1.ebuild and jadetex-2.20.ebuild are empty, which is kinda... yeah.
Last edited by delta407 on Tue Jun 18, 2002 3:34 am; edited 1 time in total |
|
| Back to top |
|
|
bsnipes
n00b
Joined: 30 May 2002
Posts: 37
|
| Posted: Tue Jun 18, 2002 3:20 am Post subject: |
|
|
I originally used in the find command but then it didn't get the ebuild files that were greater than 0 bytes but only had whitespace.
Out of curiosity what is the content of your libpcap ebuild file? I submitted a Bugzilla item and it was listed as closed with a note of that says doing an emerge rsync fixes the problem. Unless I manually delete the empty/whitespace-only ebuilds, they do not get overwritten. |
|
| Back to top |
|
|
delta407
Bodhisattva
Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL
|
| Posted: Tue Jun 18, 2002 3:33 am Post subject: |
|
|
| Running emerge rsync --clean forces your local Portage tree to syncronize with the remote one, meaning any differences in files (such as the all-whitespace being replaced with one that had content) will be overwritten. By default, different files by the same name are left alone (which is smart); just run emerge rsync --clean and your problems will be all better. |
|
| Back to top |
|
|
|
Gentoo Chat
