NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: daily `makemandb -Q' drops core



On Sat, 30 Aug 2025, Van Ly wrote:

I try to be consistent with the file path to the pkg commands and have set /etc/pkgpath.conf with

# Add local overrides below
#
pkg_add=/usr/pkg/sbin/pkg_add
pkg_admin=/usr/pkg/sbin/pkg_admin
pkg_create=/usr/pkg/sbin/pkg_create
pkg_delete=/usr/pkg/sbin/pkg_delete
pkg_info=/usr/pkg/sbin/pkg_info


That's fine.

but the state of pkg for an item version such as qemu has got confused, a situation I had wanted to avoid

$ pkgin se qemu
pkgin se qemu
fs-uae-qemu-uae-3.8.6  FS-UAE plugin for PPC and networking support
qemu-10.0.2 =        Machine emulator and virtualizer
qemu-7.2.16nb3 >     Machine emulator and virtualizer
qemu-guest-agent-10.0.2  QEMU guest agent
unicorn-2.1.3        CPU emulator engine framework based on QEMU

=: package is installed and up-to-date
<: package is installed but newer version is available
: installed package has a greater version than available package


This is correct, too, because there are 2 version of QEMU available in the
repository. You should ignore the '>' marker against the version you haven't
got installed. Bash is the same:

```
$ pkgin se ^bash-
bash-5.2.37 =        The GNU Bourne Again Shell
bash-2.05.2.13 >     The GNU Bourne Again Shell (version 2)
bash-completion-2.11  Programmable completion specifications for bash
bash-doc-2.05.2nb1   Documentation for the GNU Bourne Again Shell
bash-preexec-0.5.0   Preexec and precmd hook functions a la zsh

=: package is installed and up-to-date
<: package is installed but newer version is available
: installed package has a greater version than available package
$
```

File a PR against pkgin(1) if you feel this is confusing.

Didn't get this. Shrunk where? console or in X11?

In X11's xterm, I had a tmux session running and it was displaying all
the fonts I had interest in, and I guess the fontsize was 12 or higher.

I went to restart CTWM but misfired and quit the xsession.  On logging
back in, the X11 xterm had shrunk in size to 8 fontsize and tofu glyphs
appeared in place of expected characters.  I guess the font being used
doesn't have adequate coverage.  A fallback to the NOTO fonts avoids
this problem.


When an X11 session is done, both xinit(1) or xdm(8) will kill the X server,
which'll cause all clients to die. When a new session is started, X11 apps
will use the defaults (for things like fonts and sizes) or overrides in
~/.Xresources (or, ~/.Xdefaults). Is this what's happened?

If you want consistent settings, set them in ~/.Xresources:

```
XTerm*faceName:         DejaVu Sans Mono
XTerm*faceNameDoublesize:       Noto Sans Mono CJK KR
XTerm*faceSize:         12
XTerm*locale:           true
XTerm*renderFont:       true
```

(Note: need separate settings for UXTerm)

```
$ cat ~/.xinitrc
#!/bin/sh

export LANG=en.GB.UTF-8
[...]
xrdb -merge ~/.Xresources
[...]

$ cat ~/.xsession
#!/bin/sh

export PATH=$PATH:/usr/pkg/bin:/usr/pkg/sbin
. ~/.xinitrc
$
```

All this is basic X11 stuff...

-RVP


Home | Main Index | Thread Index | Old Index