On Sat, Jun 18, 2005 at 02:28:59PM +0200, [EMAIL PROTECTED] wrote: > Hi all, > > a few days ago I saw someone on the list advise the use of debfoster > for removing packages that had been installed as dependencies of no > longer present packages, and I decided to give it a try, and it broke > msmtp-ssl (I can no longer use it nor rebuild it).
Yes, I think that was me. Sorry my suggestion led to trouble for you. > First, debfoster seems to have removed (at least) one package > needed for msmtp, because when I try to send an e-mail I get > the following error message: > dyld: msmtp can't open library: /sw/lib/libgsasl.7.dylib (No such file or > +directory, errno = 2) > > (indeed I remember debfoster proposing me to remove packages with > gsasl9 in their names, and I accepted) That sounds like msmtp-ssl is missing a dependency or two. (I vaguely recall experiencing this myself, several months back.) Send an email to the msmtp-ssl maintainer letting them know about this. > I therefore tried to rebuild msmtp-ssl. As you discovered, you shouldn't have to do this; just satisfying the missing dependencies (with the .debs that, as you discovered are still on your system) should take care of the problem. > It claimed it needed the following packages: > The following package will be rebuilt: > msmtp-ssl > The following 10 additional packages will be installed: > gnutls gnutls-shlibs gsasl9 gsasl9-dev libgpg-error libidn libidn-shlibs > libtasn1 libtasn1-shlibs lzo > > Then the build failed on gnutls (I think) with the following > error: > <snip> > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/sw/include -I/sw/include > -no-cpp-precomp -I/sw/include -D_REENTRANT -D_THREAD_SAFE -I/sw/include > -I/sw/include -c gc-libgcrypt.c -o gc-libgcrypt.o >/dev/null 2>&1 > /bin/sh ../libtool --tag=CC --mode=link gcc -D_REENTRANT -D_THREAD_SAFE > -I/sw/include -I/sw/include -L/sw/lib -o libgc.la pkcs5.lo > gc-libgcrypt.lo -L/sw/lib -lgcrypt -L/sw/lib -lgpg-error -lz > grep: /sw/lib/libpth.la: No such file or directory > sed: /sw/lib/libpth.la: No such file or directory > libtool: link: `/sw/lib/libpth.la' is not a valid libtool archive > make[2]: *** [libgc.la] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 > ### execution of make failed, exit code 2 > Removing build lock... > dpkg -r fink-buildlock-gnutls-1.2.4-1 > (Reading database ... 103286 files and directories currently installed.) > Removing fink-buildlock-gnutls-1.2.4-1 ... > Failed: phase compiling: gnutls-1.2.4-1 failed Hm. I'm guessing a bit here, but I think this is a problem with gnutls, rather than another missing dependency. I could be wrong, but I believe that files with .la extensions are generated by libtool as part of the build process and shouldn't show up (in general) in the final package itself. In other words, libpth.la is generated during the build of gnutls. I'm not sure, given that, why the build is looking for it in /sw/lib, though. > Additionally, I would like to know if there are any special > precautions to take when using debfoster? Did I do something > wrong when using it? (I just launched the command 'debfoster' > and answered yes or no when it prompted me to keep or remove > packages) No, that's pretty much how you use it. In general, no precautions are necessary beyond those that you should generally take when performing system administration tasks. Richard ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
