Date: Sat, 13 Dec 2003 00:25:02 +0000 (GMT) From: David Carter-Hitchin <david@carter-hitchin.clara.co.uk> To: freebsd-questions@freebsd.org Subject: Re: pkg_info: read_plist: bad command '@conflicts acroread-3*' Message-ID: <20031212232012.S499@stoat.clara.net> In-Reply-To: <44vfoqcc6x.fsf@be-well.ilk.org> References: <20031208233230.A1004@stoat.clara.net> <44vfoqcc6x.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Lowell,
Thanks for your help here... my short question is now "How can I
completely refresh my pkg_* suite of tools (apart from
ports/sysutils/pkg_install)?" The background is below.
On Tue, 9 Dec 2003, Lowell Gilbert wrote:
> David Carter-Hitchin <david@carter-hitchin.clara.co.uk> writes:
>
> > Anyone got a clue why this is happening? Should I pkg_delete acroread-3
> > and reinstall? I googled this one with no luck.
>
> I don't think acroread-3 has been in the ports system in quite some
> time. I think the 'conflicts' support post-dates it, so if you remove
> it and install a newer acroread port, the problem should go away.
Unfortunately this is not a simple as that.
acroread-5.08/+CONTENTS is actually the file with the "offending" line
"@conflics acroread-3*", so my first thought was "hey, acrobat 5 is not
*that* old, I don't want to remove that". So, I thought I'd try a little
hack; made a backup of +CONTENTS (with pico actually, couldn't figure out
why 'vi \+CONTENTS' and suchlike variants were not working.. a digression
I haven't got time for now :-) and removed the "conflicts" line; hey
presto! the pkg_info command progressed beyond the point it was getting
stuck on before. It then barfed in the same way on another package (which
happened to be reasonably old), so I edited that one's +CONTENTS and again
pkg_info went further... however it now stuck on linux-base which was
installed less than a month ago... suspicious...
Hmm... time to google again. I turned up this recent reply to a post to
this list from Erik Trulsson:
>> And that still doesn't help me figure out why the packages are not
>> installing? I have not had problems installing packages up until I've
>> tried to update the ports collection.
>>
>> {error}
>> [EMAIL PROTECTED]:/apps/pkgs] pkg_add openssh-portable-3.7.1p2.tgz
>> pkg_add: bad command '@conflicts openssh-3.*'
>
>> [EMAIL PROTECTED]:/apps/pkgs] pkg_add openssh-3.6.1_5.tgz
>> pkg_add: bad command '@conflicts openssh-portable-*'
>> {/error}
> Because the packages in question rely on a feature (the "@conflicts"
> directive in this case) that the pkg_add(1) command shipped with
> FreeBSD 4.0 does not know how to handle.
> To handle packages that have been built from an up-to-date ports
> collection, you usually need up-to-date versions of the pkg_* tools.
> (It seems as if you can get such via the sysutils/pkg_install port, but
> I haven't tested that myself, so I don't know how well it works.)
Well, guess what? I've recently (couple of months ago) upgraded from FBSD
4.2 to 4.8 and so there must be something still archaic about my pkg_*
tools or underlying libraries that is causing this. The upgrade generally
went without any problems and everything (200+ packages) are working ok
(apart from some annoying TeX type errors and this pkg problem).
I have also installed sysutils/pkg_install (in fact I had originally tried
that under 4.2) and have recently done a reinstall too. I managed to get
pkg_version to report:
pkg_install-20030714_1 = up-to-date with port
Can anyone say what needs refreshing on my FBSD? I ktrace'd pkg_info and
listed all the libraries I could see it using and they seem up to date:
-r-xr-xr-x 3 root wheel 10168 Nov 16 21:23 /usr/bin/perl
-r--r--r-- 1 root wheel 577872 Nov 16 21:21 /usr/lib/libc.so.4
-r--r--r-- 1 root wheel 577872 Nov 16 21:21 /usr/lib/libc.so.4
-r--r--r-- 1 root wheel 28432 Nov 16 21:21 /usr/lib/libcrypt.so.2
-r--r--r-- 1 root wheel 28432 Nov 16 21:21 /usr/lib/libcrypt.so.2
-r--r--r-- 1 root wheel 117024 Nov 16 21:21 /usr/lib/libm.so.2
-r--r--r-- 1 root wheel 117024 Nov 16 21:21 /usr/lib/libm.so.2
-r--r--r-- 1 root wheel 117024 Nov 16 21:21 /usr/lib/libm.so.2
-r--r--r-- 1 root wheel 34092 Nov 16 21:21 /usr/lib/libmd.so.2
-r--r--r-- 1 root wheel 34092 Nov 16 21:21 /usr/lib/libmd.so.2
-r--r--r-- 1 root wheel 614824 Nov 16 21:23 /usr/lib/libperl.so.3
-r--r--r-- 1 root wheel 32728 Nov 16 21:21 /usr/lib/libutil.so.3
-r--r--r-- 1 root wheel 32728 Nov 16 21:21 /usr/lib/libutil.so.3
-r-xr-xr-x 1 root wheel 10293 Nov 16 21:23 /usr/libdata/perl/5.00503/Carp.pm
-r-xr-xr-x 1 root wheel 9900 Nov 16 21:23 /usr/libdata/perl/5.00503/Cwd.pm
-r-xr-xr-x 1 root wheel 14112 Nov 16 21:23 /usr/libdata/perl/5.00503/Exporter.pm
-r-xr-xr-x 1 root wheel 14112 Nov 16 21:23 /usr/libdata/perl/5.00503/Exporter.pm
-r-xr-xr-x 1 root wheel 4320 Nov 16 21:23 /usr/libdata/perl/5.00503/Getopt/Std.pm
-r-xr-xr-x 1 root wheel 81932 Oct 31 01:00 /usr/libexec/ld-elf.so.1
-r-xr-xr-x 1 root wheel 16551 Nov 16 21:26 /usr/sbin/pkg_version
-r-xr-xr-x 1 root wheel 16551 Nov 16 21:26 /usr/sbin/pkg_version
Obviously something needs refeshing... but what? If this is a documented
somewhere, then I'm sorry about the bandwidth wastage, but I've searched
extensively on google and freebsd.org and the man pages, but I've found
nothing which says "this is a known problem, do X and Y to fix it", only
references to other poor souls who were suffering with the same problem).
The thing I'm really trying to do is to remove dvips-5.76, but it
complains:
[548]->pkg_delete dvips-5.76
pkg_delete: package 'dvips-5.76' doesn't have a prefix
I really don't want to mess around with pkg_delete if it's not going to
work correctly, or make thing worse.
Many thanks
David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031212232012.S499>