pkg-static: pkg-1.4.0.p.a11 conflicts with pkg-1.3.7 (installs files into the same place).
Matthew Seaman
m.seaman at infracaninophile.co.uk
Sun Aug 31 08:11:08 UTC 2014
On 31/08/2014 06:02, Craig Rodrigues wrote:
> I did a fresh install of 10-STABLE on a new system.
>
> I set up the new xorg repository as outlined here:
>
> https://lists.freebsd.org/pipermail/freebsd-announce/2014-July/001570.html
>
> When I tried to install a bunch of packages,
> I got this conflict:
>
> pkg-static: pkg-1.4.0.p.a11 conflicts with pkg-1.3.7 (installs files
> into the same place).
> Problematic file: /usr/local/etc/bash_completion.d/_pkg.bash
>
> The full log of what I typed is here:
> https://people.freebsd.org/~rodrigc/pkg-1.3.7-pkg-1.40.conflict.txt
>
> What is the best way to solve this?
>
> In future, how do we deal with the case where someone sets up
> multiple package repositories, but one repo has a dependency
> on a different version of pkg?
Presumably pkg-1.4.0.p.a11 is from the pkg-devel port? Your output
shows no sign of the pkg bootstrapping process, so pkg-devel must have
already been installed. Yet in your list of packages to install you
specifically include 'pkg'
As far as I know, the only package in the ports tree that has a specific
run-time dependency (ie. the only sort of dependency pkg(8) cares about
when handling binary packages) on pkg itself is net-snmp[*], but you
aren't installing that, so you could use either pkg or pkg-devel quite
happily.
Your transcript also shows pkg-1.3.7 being upgraded, and then later
deleted. That's a known bug --
https://github.com/freebsd/pkg/issues/980 -- but this is the first
report of pkg doing that to itself.
In order to sort out your specific case, try this:
- first, ensure that you have the version of pkg installed that you
want. For the standard release version:
# pkg install pkg
- then delete pkg from your list of stuff to install. Practically
speaking when installing a set of packages like this, you can assume
that pkg is already installed. If it isn't then the /usr/sbin/pkg
bootstrapping process will achieve the same effect as soon as you try
and install anything.
- try again to install your list of packages. Judging by the output
you showed, most of them were in fact installed then, but it looks like
there are 60-odd stragglers to deal with.
Cheers,
Matthew
[*] Run time dependencies on pkg(8) should as a rule, be avoided without
very good reason.
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
JID: matthew at infracaninophile.co.uk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 971 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-pkg/attachments/20140831/ff0c9248/attachment.sig>
More information about the freebsd-pkg
mailing list