On Thu, October 5, 2006 8:10 pm, Iain Day wrote:
> Jean-François Mertens wrote:
>> Was this really during an update-all today or yesterday ?
>> Could you re-do update-all ?
>> (that error has been < 5 mins in CVS, more than a week ago...)
>>
>> JF Mertens
>
> Yes, I'm still getting the same error. Is there a way to force fink to
> get a fresh copy of the source to rebuild the .deb or something similar?
>
> Iain
>
(as mentioned in my other message)
"fink rebuild gtk+2" is what you want.
What has gone on is that there have been modifications to the Fink
package description and build options that didn't change the revision of
the package (the last number: -1002). Because of that, if you try to
use "fink updae gtk+2" or "fink update-all", Fink sees the package as
current, and that there is a current binary archive of the package to
install from.
"fink rebuild gtk+2" will make the fink tool ignore the presence of a
binary archive and build the package again.
(redownloading the source wouldn't work, by the way, because we don't muck
with the sources directly)
--
Alexander K. Hansen
(akh)
Fink Documenter
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users
