Re: My packages are SO hosed.

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

I pointed out the old link to the wiki to underline you need X11_TYPE
type be modular in order to actually build modular_xorg, otherwise you
get all these errors about missing packages - which are actually
present, but in the built-in Xorg, which defies the purpose in the
first place. I also mentioned earler about pkgtools/osabi (this has
been discussed earlier, seems to be too finegrained for use with
-current, but can be disregarded), in a sence that I always manually
rebuild osabi for the tiny version of -current prenestly in use,
together with all those depending on it (always x11-links, net-snmp,
lsof in my case), then do anything with pkg_rolling-replace or a long
build like this one.

I am also building modular Xorg on a clean pkgsrc -current box, having
some problems from time to time (e.g. cmake refused to build and had
to edit its configuration files to complete it), but there is no more
problem with the missing .pc files. My initial plan after I finish the
build is to install a new -current instance under VirtualBox, but
without the X sets, then pkgin the newly built modular Xorg  (it has
vboxvideo driver). After that I might try it with a new USB setup on
real hardware.

On Sun, 17 Mar 2019 at 08:48, Sad Clouds <cryintothebluesky%gmail.com@localhost> wrote:
>
> On Sun, 17 Mar 2019 00:46:55 -0400
> Bob Bernstein <poobah%ruptured-duck.com@localhost> wrote:
>
> > My spidey-sense is warning me that my pkg collection is seriously
> > corrupt, and that I ought to give equally serious consideration to
> > beginning over again, with a fresh install of -current.
> >
> > Buy, sell, or hold?
> >
> > Thank you,
>
> What exactly are you attempting to do? If you want to get pkgsrc going
> but you have some corruption issues??, just remove manually all your
> existing packages, i.e.
>
> rm -rf /usr/pkg
> rm -rf /var/db/pkg
>
> and start from scratch. It's as simple as that. But then I don't know
> how and where you install your packages. If you build them yourself
> from source, then you should know exactly where they are located. If
> you install binary packages from NetBSD public locations, then all
> packages and database live in the well known locations.
>
> >From your previous email, it seems you're building from source, but I
> can't tell if only one package install gives you errors, or if this
> happens for other packages as well. Have you tried running "pkg_info
> -a"? and looking for the package name? If you're not building and
> installing packages in a chroot, then you will be overwriting
> previously installed packages and possibly causing conflicts. Is this
> what may be happening here?
>


-- 
----