| View previous topic :: View next topic |
| Author |
Message |
mintu
n00b
Joined: 18 Sep 2004
Posts: 21
|
 Posted: Tue Dec 25, 2007 3:53 am Post subject: update world ... manifest error again n again |
 |
|
I am trying to update the system. but i always get this error.
| Quote: | localhost ~ # emerge --update --deep world
Calculating world dependencies... done!
>>> Verifying ebuild Manifests...
!!! A file is not listed in the Manifest: '/usr/local/portage/net-p2p/azureus/files/azureus-bcprov-1.35.patch' |
i came to know that resyncing will solve this problem but no use. i am trying for last 2 days resyncing but this error doesnt go.
is there any way to remove this error. |
|
| Back to top |
|
 |
marrowhk
Apprentice
Joined: 25 Jul 2007
Posts: 250
|
| Posted: Tue Dec 25, 2007 4:23 am Post subject: |
|
|
Many solutions to this if you think about it.
(as root) brute force, remove offending element and rsync (as you suggested)
| Code: | # rm -Rf /usr/portage/net-p2p/azureus
# emerge --sync
# emerge -uDNpv world |
If you still have this issue why not just remove portage altogether and replace it with a snapshot then update it:
(as root)
| Code: | # cd /
# rm -Rf /usr/portage
# wget http://ftp.kaist.ac.kr/pub/gentoo/snapshots/portage-latest.tar.bz2
# tar -xjpf portage-latest.tar.bz2 -C /usr (note: never use the tar -v switch as it slows down the process!)
# rm portage-latest.tar.bz2
# emerge --rsync |
If you want to manually update ebuild manifests do the following:
| Code: | # cd /usr/portage/net-p2p/azureus
# ebuild azureus-3.0.3.4.ebuild digest |
_________________
You'll always come back to GENTOOOOOOO ! (Trust me...) |
|
| Back to top |
|
|
mintu
n00b
Joined: 18 Sep 2004
Posts: 21
|
| Posted: Tue Dec 25, 2007 10:42 am Post subject: |
|
|
| i have tried all the things.. it doesnt work. |
|
| Back to top |
|
|
aldraia
n00b
Joined: 10 Jul 2006
Posts: 16
|
| Posted: Tue Dec 25, 2007 11:34 am Post subject: |
|
|
have you tried to remove the file?
if it's not on the manifest, maybe azureus ebuild don't use it any more. |
|
| Back to top |
|
|
Rafal_Glazar
Apprentice
Joined: 10 Jul 2004
Posts: 167
Location: Rzeszow, Poland
|
| Posted: Tue Dec 25, 2007 11:43 am Post subject: |
|
|
It looks like broken Manifest file is in your portage overlay. Find out what ebuild you have in /usr/local/portage/net-p2p/azureus/ and then type command:
| Code: |
ebuild /usr/local/portage/net-p2p/azureus/ebuild-name.ebuild digest
|
in your console.
_________________
"All I ask for is choice. I want to be able to go into any store you can buy a computer in and say, "I want ______ OS on this computer." Is that too much to ask? We can't always be looking out Windows. We also need to get work done." - Bill Olson |
|
| Back to top |
|
|
marrowhk
Apprentice
Joined: 25 Jul 2007
Posts: 250
|
| Posted: Wed Dec 26, 2007 2:47 am Post subject: |
|
|
| Rafal_Glazar wrote: | It looks like broken Manifest file is in your portage overlay. Find out what ebuild you have in /usr/local/portage/net-p2p/azureus/ and then type command:
| Code: |
ebuild /usr/local/portage/net-p2p/azureus/ebuild-name.ebuild digest
|
in your console. |
He said this doesn't work, see my first answer! This is a portage error specific to this package only and it is resolved by our suggestions, either he doesn't understand the simple fix or he is unable to apply it.
| Code: | If you want to manually update ebuild manifests do the following:
Code:
# cd /usr/portage/net-p2p/azureus
# ebuild azureus-3.0.3.4.ebuild digest |
_________________
You'll always come back to GENTOOOOOOO ! (Trust me...)
Last edited by marrowhk on Wed Dec 26, 2007 2:51 am; edited 1 time in total |
|
| Back to top |
|
|
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5956
|
| Posted: Wed Dec 26, 2007 2:49 am Post subject: |
|
|
| marrowhk wrote: | | Rafal_Glazar wrote: | It looks like broken Manifest file is in your portage overlay. Find out what ebuild you have in /usr/local/portage/net-p2p/azureus/ and then type command:
| Code: |
ebuild /usr/local/portage/net-p2p/azureus/ebuild-name.ebuild digest
|
in your console. |
He said this doesn't work, see my first answer! |
yeah, he said it didn't work for the one you specified, the one in the portage tree. the error states it's the one in his local overlay that is the one that needs the new digest.
cheers
_________________
| Neddyseagoon wrote: | | The problem with leaving is that you can only do it once and it reduces your influence. |
banned from #gentoo since sept 2017 |
|
| Back to top |
|
|
marrowhk
Apprentice
Joined: 25 Jul 2007
Posts: 250
|
| Posted: Wed Dec 26, 2007 2:53 am Post subject: |
|
|
AAhh! Didn't read the post properly
Got it. Thanks.
All you have to do is apply the same fix to your local portage overlay or delete the local version.
Man, that's a quantum leap 
_________________
You'll always come back to GENTOOOOOOO ! (Trust me...) |
|
| Back to top |
|
|
|
Other Things Gentoo
