On 2020/08/01 16:53, Austin Hook wrote:
> Stuart suggested sending the entire pkg_add -u" output for a quick scan
> of my foolishness, so I an including it at the bottom of this email --
> lines chopped at character 78, because all the linking stuff makes it half
> a megabyte, which seems excessive to burden the archives with. Maybe
> seeing the full link into is not necessary to allow one more comment if
> any of you folks care to peek at my pkg_add -u output.
Full output would be better, I think that chopping at column 78 has
truncated some useful information. At least I didn't spot the direct
cause of the problem (though clearly there's an issue with handling
the gettext packages, which was split/renamed - this certainly causes
some issues for pkg_add, though in cases that I've seen before just
rerunning pkg_add -u was enough to clear it up).
Good that you considered the lists (I wish people who send multi-
megabyte fuzzy photos of panic messages that they could have typed in
fairly easily would do the same...) but they can cope with 500K once
in a while, or sending as a gzipped attachment would shrink it a lot.
If you need to get it fixed, the following should do the trick;
save a list of packages, remove them all, and reinstall:
pkg_info -mz >/root/pkg_list_manual
pkg_info -z >/root/pkg_list_full
pkg_delete -X /var/db/pkg/*-firmware-[0-9]*
pkg_add -z -l /root/pkg_list_manual
pkg_add -za -l /root/pkg_list_full
but it would be good to get more details if possible first in case
they point at a bug/something missing in pkg_add.
> Merging nano-3.1->4.4 (ok)
>
Checking packages|No need to update python-3.4.5[K[K
[KNOT MERGING: can't
The missing text in lines like the above, or in some of the merge lines,
might have something useful. But it's easier to include everything
rather than try to figure out what might help.
