Re: libcdio upgrade problems
Thank you :-) Unfortunatly I took someone elses advice and upgraded to 7.0, which created it's own problem :-( But the libcdio thing did get fixed, at least! Jen --- On Wed, 6/18/08, Lowell Gilbert <[EMAIL PROTECTED]> wrote: From: Lowell Gilbert <[EMAIL PROTECTED]> Subject: Re: libcdio upgrade problems To: "Dr. Jennifer Nussbaum" <[EMAIL PROTECTED]> Cc: freebsd-questions@freebsd.org Date: Wednesday, June 18, 2008, 12:57 PM "Dr. Jennifer Nussbaum" <[EMAIL PROTECTED]> writes: > Lowell Gilbert <[EMAIL PROTECTED]> wrote: "Dr. Jennifer Nussbaum" writes: > >> Im trying to upgrade some ports, and have a problem with libcdio. At least i >> think i do. >> >> When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the >> end with a "libcdio-0.78.2_2 is already installed. You may wish to make deinstall" >> etc. message. >> >> But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, >> and this was successful. I sync'd the ports collection again, but no luck. Nothing >> in UPDATING about this. > > Sounds like the dependencies are confused. pkgdb(1) may help with > that. If not, the brute force approach would be to remove the > affected ports all the way back to (and including) libcdio, and build > them over. > I havent been able to figure out how to fix things with pkgdb. And i have tried, over and over, to remove the affected ports and build them from scratch but it hasnt been working. > > So i went to libcdio and did a make deinstall, deleted the work files, and did a make install clean, and it installed fine. Then i tried to build gvfs, also by doing a make install clean, and it died in the same way--telling me to make deinstall and make reinstall of libcdio. > > Ive tried this several times with no luck. If theres an even more brute force way id like to know what it is so i can do that. This is preventing a lot of other upgrades to GNOME, which i need. I found it. I think you need to reset the options on libcdio to re-enable the cdparanoia option. Some gnome ports seem to depend on the library specifically with the paranoia option, and I've seen some systems get the options jammed. Something like: (cd /usr/ports/sysutils/libcdio ; make rmconfig ; portupgrade -f libcdio) -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: libcdio upgrade problems
"Dr. Jennifer Nussbaum" <[EMAIL PROTECTED]> writes: > Lowell Gilbert <[EMAIL PROTECTED]> wrote: "Dr. Jennifer Nussbaum" writes: > >> Im trying to upgrade some ports, and have a problem with libcdio. At least i >> think i do. >> >> When i try to upgrade, say, Nautilus (or a buncha other things), it dies in >> the >> end with a "libcdio-0.78.2_2 is already installed. You may wish to make >> deinstall" >> etc. message. >> >> But i did go to /usr/ports/sysytils/libcdio and make deinstall and make >> reinstall, >> and this was successful. I sync'd the ports collection again, but no luck. >> Nothing >> in UPDATING about this. > > Sounds like the dependencies are confused. pkgdb(1) may help with > that. If not, the brute force approach would be to remove the > affected ports all the way back to (and including) libcdio, and build > them over. > I havent been able to figure out how to fix things with pkgdb. And i have > tried, over and over, to remove the affected ports and build them from > scratch but it hasnt been working. > > So i went to libcdio and did a make deinstall, deleted the work files, and > did a make install clean, and it installed fine. Then i tried to build gvfs, > also by doing a make install clean, and it died in the same way--telling me > to make deinstall and make reinstall of libcdio. > > Ive tried this several times with no luck. If theres an even more brute force > way id like to know what it is so i can do that. This is preventing a lot of > other upgrades to GNOME, which i need. I found it. I think you need to reset the options on libcdio to re-enable the cdparanoia option. Some gnome ports seem to depend on the library specifically with the paranoia option, and I've seen some systems get the options jammed. Something like: (cd /usr/ports/sysutils/libcdio ; make rmconfig ; portupgrade -f libcdio) -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: libcdio upgrade problems
>Im trying to upgrade some ports, and have a problem with libcdio. At least i >think i do. > >When i try to upgrade, say, Nautilus (or a buncha other things), it dies in >the >end with a "libcdio-0.78.2_2 is already installed. You may wish to make >deinstall" >etc. message. > >But i did go to /usr/ports/sysytils/libcdio and make deinstall and make >reinstall, >and this was successful. I sync'd the ports collection again, but no luck. >Nothing >in UPDATING about this. > >Thanks! I've run into similar experiences with other ports, and what I have done to get it to work is to deinstall the complaining port (in this instance libcdio), and let the original port install it as a dependency instead of doing a "make reinstall". -- Im afraid this didnt work either--whether libcdio is installed or not (and installing it seems to work fine), any other port that requires it tells me that it is installed and need to be make deinstalled and make reinstalled. Yet this doesnt work. Is there any other brute-force way to get around this? This is getting difficult. Thanks again, everyone. Jen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: libcdio upgrade problems
Dr. Jennifer Nussbaum wrote: Hi, Im trying to upgrade some ports, and have a problem with libcdio. At least i think i do. When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the end with a "libcdio-0.78.2_2 is already installed. You may wish to make deinstall" etc. message. But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, and this was successful. I sync'd the ports collection again, but no luck. Nothing in UPDATING about this. Thanks! Jen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" I've run into similar experiences with other ports, and what I have done to get it to work is to deinstall the complaining port (in this instance libcdio), and let the original port install it as a dependency instead of doing a "make reinstall". Best regards, Greg Groth ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: libcdio upgrade problems
Pietro Cerutti <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dr. Jennifer Nussbaum wrote: | | Lowell Gilbert wrote: "Dr. Jennifer Nussbaum" writes: | |> Im trying to upgrade some ports, and have a problem with libcdio. At least i |> think i do. |> |> When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the |> end with a "libcdio-0.78.2_2 is already installed. You may wish to make deinstall" |> etc. message. |> |> But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, |> and this was successful. I sync'd the ports collection again, but no luck. Nothing |> in UPDATING about this. | | Sounds like the dependencies are confused. pkgdb(1) may help with | that. If not, the brute force approach would be to remove the | affected ports all the way back to (and including) libcdio, and build | them over. | I havent been able to figure out how to fix things with pkgdb. And i have tried, over and over, to remove the affected ports and build them from scratch but it hasnt been working. | | So i went to libcdio and did a make deinstall, deleted the work files, and did a make install clean, and it installed fine. Then i tried to build gvfs, also by doing a make install clean, and it died in the same way--telling me to make deinstall and make reinstall of libcdio. | | Ive tried this several times with no luck. If theres an even more brute force way id like to know what it is so i can do that. This is preventing a lot of other upgrades to GNOME, which i need. Not to point out the obvious, but you're sure your port tree is up-to-date? Yes as i said in my first post i resynced ports before this, and just did it again to make sure. No changes to this port or any of the others involved. Jen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: libcdio upgrade problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dr. Jennifer Nussbaum wrote: | | Lowell Gilbert <[EMAIL PROTECTED]> wrote: "Dr. Jennifer Nussbaum" writes: | |> Im trying to upgrade some ports, and have a problem with libcdio. At least i |> think i do. |> |> When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the |> end with a "libcdio-0.78.2_2 is already installed. You may wish to make deinstall" |> etc. message. |> |> But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, |> and this was successful. I sync'd the ports collection again, but no luck. Nothing |> in UPDATING about this. | | Sounds like the dependencies are confused. pkgdb(1) may help with | that. If not, the brute force approach would be to remove the | affected ports all the way back to (and including) libcdio, and build | them over. | I havent been able to figure out how to fix things with pkgdb. And i have tried, over and over, to remove the affected ports and build them from scratch but it hasnt been working. | | So i went to libcdio and did a make deinstall, deleted the work files, and did a make install clean, and it installed fine. Then i tried to build gvfs, also by doing a make install clean, and it died in the same way--telling me to make deinstall and make reinstall of libcdio. | | Ive tried this several times with no luck. If theres an even more brute force way id like to know what it is so i can do that. This is preventing a lot of other upgrades to GNOME, which i need. Not to point out the obvious, but you're sure your port tree is up-to-date? | | Thanks! | | Jen | | | ___ | freebsd-questions@freebsd.org mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-questions | To unsubscribe, send any mail to "[EMAIL PROTECTED]" - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkhOjCcACgkQwMJqmJVx944niQCeMNdtOQOfePqCiys0RFK1xg20 nnMAnRpHOqMO4BiSTpO+KY5ZBuRPT1Ok =nNAK -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: libcdio upgrade problems
Lowell Gilbert <[EMAIL PROTECTED]> wrote: "Dr. Jennifer Nussbaum" writes: > Im trying to upgrade some ports, and have a problem with libcdio. At least i > think i do. > > When i try to upgrade, say, Nautilus (or a buncha other things), it dies in > the > end with a "libcdio-0.78.2_2 is already installed. You may wish to make > deinstall" > etc. message. > > But i did go to /usr/ports/sysytils/libcdio and make deinstall and make > reinstall, > and this was successful. I sync'd the ports collection again, but no luck. > Nothing > in UPDATING about this. Sounds like the dependencies are confused. pkgdb(1) may help with that. If not, the brute force approach would be to remove the affected ports all the way back to (and including) libcdio, and build them over. I havent been able to figure out how to fix things with pkgdb. And i have tried, over and over, to remove the affected ports and build them from scratch but it hasnt been working. So i went to libcdio and did a make deinstall, deleted the work files, and did a make install clean, and it installed fine. Then i tried to build gvfs, also by doing a make install clean, and it died in the same way--telling me to make deinstall and make reinstall of libcdio. Ive tried this several times with no luck. If theres an even more brute force way id like to know what it is so i can do that. This is preventing a lot of other upgrades to GNOME, which i need. Thanks! Jen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: libcdio upgrade problems
"Dr. Jennifer Nussbaum" <[EMAIL PROTECTED]> writes: > Im trying to upgrade some ports, and have a problem with libcdio. At least i > think i do. > > When i try to upgrade, say, Nautilus (or a buncha other things), it dies in > the > end with a "libcdio-0.78.2_2 is already installed. You may wish to make > deinstall" > etc. message. > > But i did go to /usr/ports/sysytils/libcdio and make deinstall and make > reinstall, > and this was successful. I sync'd the ports collection again, but no luck. > Nothing > in UPDATING about this. Sounds like the dependencies are confused. pkgdb(1) may help with that. If not, the brute force approach would be to remove the affected ports all the way back to (and including) libcdio, and build them over. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
libcdio upgrade problems
Hi, Im trying to upgrade some ports, and have a problem with libcdio. At least i think i do. When i try to upgrade, say, Nautilus (or a buncha other things), it dies in the end with a "libcdio-0.78.2_2 is already installed. You may wish to make deinstall" etc. message. But i did go to /usr/ports/sysytils/libcdio and make deinstall and make reinstall, and this was successful. I sync'd the ports collection again, but no luck. Nothing in UPDATING about this. Thanks! Jen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
