Hi all, I'm trying to install gnome-doc-utils : $ sudo pkg_add gnome-doc-utils perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LC_ALL = (unset), LC_CTYPE = "en_US.UTF-8", LANG = (unset) are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). Collision: the following files already exist /usr/local/bin/gnome-doc-prepare (same md5) /usr/local/bin/gnome-doc-tool (same md5) /usr/local/bin/xml2po (same md5) /usr/local/lib/pkgconfig/gnome-doc-utils.pc (same md5) /usr/local/lib/pkgconfig/xml2po.pc (same md5) /usr/local/man/man1/xml2po.1 (same md5) /usr/local/share/aclocal/gnome-doc-utils.m4 (same md5) /usr/local/share/xml2po/xhtml.pyc (same md5) etc, etc, etc... /usr/sbin/pkg_add: fatal issues in installing gnome-doc-utils-0.10.3p2 $ The Perl error just appeared today but it is no big deal for me right now. My problem is that I can't find any way in pkg_add(1) for dealing with this. There are just to many collision files to remove manually and I don't know how te make a script wich automaticly removes all these files. How should I handle this? Pieter Verberne
First, how did this happen? Is the package system out of sync, or did you have a failed install? Second, to deal with it: make a script to automatically remove the files. Just pipe the output to a file, go in with your favourite editor and delete everything before and after the filelists, and then replace " (same md5)" with "", and then for file in `cat files`; do rm file; done Or just rm every file it lists by hand?
I'm not sure but my system might be out of sync. I read the faq and some other guides but the package system kept vague for me. I install current +/- 8 months ago. I never got any problem with the package system till, lets say, 4.2 release came out. Becaulse of these kind (and other) errors I tried the "Following -current" manual. But is it possible to download a new snapshot bootalble cd image and upgrade by booting the cd? That would be much easier for me:-) I think pkg_add isn't able to upgrade the core/userland system (exept for manually install apps), isn't it? *sigh* sometimes I feel so, well, newby. (No, I don't have low self Someone send me a private mail with a semi-working answer: sudo pkg_add gnome-doc-utils | grep 'same md5' | \ cut -d'(' -f1 | sed 's/^/echo sudo rm /' I was adviced to paste the input in my term. I changed this to: sudo pkg_add gnome-doc-utils | grep 'same md5' | cut -d'(' -f1 | sed 's/^/sudo rm /' (removed 'echo') This does the job fine, exept for the pasting part. But after a few times getting a big mess on my term, I deleted all the files:-) So, what is you advice to do with this:? $ sudo pkg_add -v grip Error from ftp://ftp.calyx.nl/pub/OpenBSD/snapshots/packages/i386/grip-3.2.0p7.tgz: 550 grip-3.2.0p7.tgz: No such file or directory. Error from ftp://ftp.calyx.nl/pub/OpenBSD/snapshots/packages/i386/grip-3.2.0p7.tgz: 550 grip-3.2.0p7.tgz: No such file or directory. Error from ftp://ftp.calyx.nl/pub/OpenBSD/snapshots/packages/i386/grip-3.2.0p7.tgz: 550 grip-3.2.0p7.tgz: No such file or directory. Error from ftp://ftp.calyx.nl/pub/OpenBSD/snapshots/packages/i386/grip-3.2.0p7.tgz: 550 grip-3.2.0p7.tgz: No such file or directory. parsing grip-3.2.0p7 Dependencies for grip-3.2.0p7 resolve to: gettext-0.16.1, cdparanoia-3.a9.8p0, yelp-2.18.1p1, curl-7.17.0, libiconv-1.9.2p4, libgnomeui-188.8.131.52, vorbis-tools-1.1.1p2, vte-0.16.9p0, id3lib-3.8.3p2 (todo: libgnomeui-184.108.40.206,yelp-2.18.1p1) grip-3.2.0p7:parsing ...
yes, I tend to track snapshots that way. You do need to handle /etc separately though. I've been tracking snapshots on a few machines including my ever-present laptop roughly like, 0) download the install42.iso from the snapshots directory on a convenient mirror (in my case ftp.se.openbsd.org), burn to CD 1) csup most recent source from a convenient mirror 2 run mergemaster to merge in new /etc with your local changes 3) set PGK_PATH to something sensible, eg the snapshot's packages directory on that same mirror 4) run sudo pkg_add -ui -F update -F updatedepends 5) boot from the CD and choose upgrade, reboot to upgraded system This assumes you are starting with a fairly recent snapshot. In your case, going IIRC from 4.0 to 4.2 you will need to go through the steps in the upgrade guides. Depending on your situation it might even be useful to wipe and reinstall. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.datadok.no/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd: 220.127.116.11: disconnected after 42673 seconds.
Why not use -F conflicts ? pkg_add should be able to handle this... -- If you don't remember something, it never existed... If you aren't remembered, you never existed... I don't quite understand what love is like... But if there was someone who liked me, I'd be happy.
We don't have support for UTF8 yet, and perl sees that. It's just an innocuous So, it definitely looks like you've got gnome-doc-utils installed already (or most of it). Did you look at installed your package list ? check for gnome-doc-utils-*, or partial-gnome-doc-utils-* in case something went wrong. It is totally *impossible* that you've got those files on this computer without having already tried to install this package (voluntarily, or by accident): just look at this report, you've got loads of files with the same md5, so they come from the same package. The package should say it's already installed if it is, and should say there's a conflict with a partial-* of the same name. I don't know how you did it, but something very wrong happened here. Did you erase /var/db/pkg ? did you get an error message from a pkg_add you didn't read and went forward anyways ?
Corruption of the filesystem holding /var/db/pkg could do this.
I have installed the package before indeed. However, it was not installed at the I don't know how I did this either. Can I always erase /var/db/pkg safly? However, I think I'm doing a new install soon, and then try to keep my package managemet system clean:-) Pieter
Just to make one point clear: yep the collision report does not give you an `easy' way to delete the files (though saving the file and apply some simple sed/awk like pattern is not that hard), because that's the wrong way to think about the problem. If you've got files in /usr/local, and pkg_* can't figure out where they come from, then you are in trouble... Those dangling files are usually a symptom something much more fishy is going on, like file system corruption. And most often, you don't want to just fix the local problem, you want to figure out what is going on, for real. It's possible to extend pkg_add to sniff around, and to recover from some simple situations... just means it will fail later in weirder ways. Like, sure, you've got files right from a package, you could just reinstall the package on top of it, and expect things to be right... except they won't ! If this package was installed at some point, it probably also means some stuff is/was depending on it. So you would need to also re-check each and every dependency in packages to make sure they don't want this package (fairly important in case of updates). And if one package has missing meta-information, who says it's the only one ? rescanning /usr/local looking for orphaned files would be needed. then probably perusing pkglocatedb to try to figure out where they come from in the first place, and trying to re-obtain those packages and check more things out. Assuming you still can grab the missing packages somewhere, all this is feasible. It's just not being done with the current tools, and it's probably a bit too complex to implement quickly...