Hi,
over the last 3 1/2 days, I endeavoured to switch my fink
installation over to the newer 10.4 tree, starting from
10.4-transitional. Along the way, I ran into a number of
problems, fortunately all quickly resolved with the help
of the fabulous #fink crew.
I have recorded my transition experience and included the
text below, as agreed upon on IRC. Hopefully it will serve
to make the process a smoother one, or help other fink
users avoid any unfortunate decisions I may have made
during it.
Here goes:
* A small overview of the system preceding the transition effort:
- iBook G4 800 Mhz
- Mac OS X 10.4.6
- Xcode 2.2.1
- Up-to-date installation of Fink's 10.4-t tree, using unstable.
Prime objective is to run a bunch of KDE things.
* Steps I performed to kick off the transition procedure, under
supervision from #fink's jack in a query:
1. Changed references to 10.4-transitional to just 10.4 in fink.conf
and sources.list
2. Ran selfupdate successfully.
3. Ran update-all. Aborts complaining about not finding much of any-
thing.
4. jack remembers the dists symlink in /sw/fink. I change it to 10.4
as well.
5. Ran selfupdate successfully again.
6. Kicked off update-all.
* Failure #1: Compilation error with mjpegtools-1.6.2-1003
Steps taken:
- Ran selfupdate, hoping the problem would vanish. Ran update-all,
which started up again with another package (which was unpredic-
table to me). See Failure #4 for the follow-up.
* Failure #2: File not found: automake1.7_1.7.9-2_darwin-powerpc.deb
Steps taken:
- Ran "fink rebuild automake1.7" as suggested by msachs on #fink.
Appears to generate the missing .deb, and indeed, running
update-all again, it successfully moves past this one and on to
flac.
* Failure #3: Missing openmotif .deb
Steps taken:
- Changed UseBinaryDist in fink.conf to false as suggested by akh on
#fink (alternatively, it was suggested I use the --no-use-b flag).
akh voiced some doubts about this actually helping, but afterwards,
update-all ran fine without any more missing .deb errors.
* Failure #4: Compilation error with mjpegtools
Error message: "glibtool: compile: unable to infer tagged configuration"
Steps taken:
- Ran "fink rebuild libtool24" as suggested by pogma on #fink.
update-all successfully moved past mjpegtools afterwards.
Note: pogma went on to say: "and annoy the mjpegtools maintainer
telling him/her not to call the installed libtool script"
This resulted in the following discussion:
<RangerRick> pogma: so what's wrong with calling the installed
libtool script? Why's it there if not to be called?
<pogma> RangerRick: 'cause if you cahange the compiler (as Sho_
did by moving to the 10.4 tree g++-3.3 became g++) then
libtool will fail to work
After some prodding of the package by RangerRick, the consensus
seemed to be that bumping the rev of the libtool package in 10.4
and depending on it would be the best real-world fix, as it takes
care of the most common case of moving from 10.4-t to non-t.
* Failure #5: "xyz depends on t1lib1, but t1lib1 is not installed"
Unfortunately I didn't write down the name of the complaining
package, as I was on the run and still half-asleep at the time.
Steps taken:
- Ran "fink rebuild t1lib1" as a shot in the dark. Sent update-all
on its way again afterwards - successfully.
Note: <drm> Sho_: and to explain the message: when a library has a
non-compatible upgrade, there are two different header
packages (in this case, t1lib1 and t1lib5) which have
to be swapped back and forth... the fink dependency
engine is not always capable of doing the swapping when
a large number of pkgs are being built at the same time
* Failure #6: "Can't set build lock for gnome-vfs2 (2.10.1-1005)" /
conflict with libcdparanoia0-dev
See http://www.eikehein.com/failure6.txt for the complete error log
of the failure.
Steps taken:
- Following the suggestion of fink, ran "fink build gnome-vfs2; fink
update-all". This removed libcdparanoia0-dev automatically.
- Ctrl-C'd the above as I forgot to add -y to the update-all command
and was on the run once more.
- Now, "fink build gnome-vfs2" would complain about a buildlock for
gnome-vfs2. In the event that a prior build attempt had crashed, it
suggested to remove the buildlock package, which I did.
- Ran update-all, which happily built gnome-vfs2 and went on.
After those failures, update-all completed successfully. I ran another
selfupdate and update-all at this time, to be up to date after three
days of compiling - getting me the new libtool14 agreed upon as the
tentative fix for Failure #4, among other things.
Everything is in working order now.
Best regards,
Eike Hein
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
