> Those are the only *git* packages in 7.4/packages-stable/aarch64
Thank you for your insights.
Essentially, when neither `-a` nor `-A` is present, the current logic is to:
1. search "packages-stable", if there is a match at all, then the search
stops
2. if no match is found in
On Fri, 16 Feb 2024 23:13:59 +
"C. Li" wrote:
>
> # pkg_info -Q git
> debug-gitwrapper-0.94
> debug-gitwrapper-0.95
> gitwrapper-0.94
> gitwrapper-0.95
>
> ...
> Tested on OpenBSD 7.4 arm64.
Those are the only *git* packages in 7.4/packages-stable/aarch64
I guess that -Q doesn't
Suppose we would like to search for a package named "cgit":
# pkg_info -Q cgit
cgit-1.2.3
This works as expected. Now if we try the search with "git", the cgit
package should also show up. However, it does not:
# pkg_info -Q git
debug-gitwrapper-0.94
debug-gitwrapper-0.95
There is no bug.
The distrib directory requires building inside a "full snapshot build" sequence.
Workaround shortcuts can done to make it work, but I will not be adding
workarounds inside the tree to encourage shorcuts, because they will encourage
other fragile breakage. libstubs has
> I noticed that there is a problem with libstubs in this process from a
> "vanilla" riscv64 build box. It will error out. The work around is to
> go into /usr/src/distrib/special/libstubs and manually make it there, where
> it gets ranlib'ed. Then go back to the former path and continue
kn@: I will take a look at my earlier bug report with the RISCV disk encryption
bug in the installer.
Right now I have installed OpenBSD/riscv64 on my Mango Pi. Thank you very
much OpenBSD! This is a great effort making this mango pi work!
I found that I needed a new kernel to detect
> > Do you have machdep.forceukbd=1 somewhere in /etc/sysctl.conf?
>
> Ah, yes! And there's no USB keyboard now, I added that when the
> disk was in a real machine before I moved it to a VM.
Ok, so this is what causes the keymap pointer to be reset to NULL. Phew!
Root cause found.
Anton, could
On 2024/02/16 16:04, Miod Vallat wrote:
> > Diff does fix the crash -
> >
> > # kbd -l
> > tables available for pc-xt/pc-at keyboard:
> > encoding
>
> Do you have machdep.forceukbd=1 somewhere in /etc/sysctl.conf?
Ah, yes! And there's no USB keyboard now, I added that when the
disk was in a
> Diff does fix the crash -
>
> # kbd -l
> tables available for pc-xt/pc-at keyboard:
> encoding
Do you have machdep.forceukbd=1 somewhere in /etc/sysctl.conf?
On 2024/02/15 14:53, Stuart Henderson wrote:
> On 2024/02/13 08:44, Miod Vallat wrote:
> > > Does this help?
> > >
> > > diff --git sys/dev/wscons/wskbd.c sys/dev/wscons/wskbd.c
> > > index 7631cd5f701..dd65f61ce63 100644
> > > --- sys/dev/wscons/wskbd.c
> > > +++ sys/dev/wscons/wskbd.c
> > > @@
On Fri, 16 Feb 2024 12:13:32 +0100,
Stefan Sperling wrote:
>
> I might have found the root cause of your problem in iwx.
> Can you try this diff please?
>
> diff /usr/src
> commit - 5f5902b3789b6f994566004963a31af6304d3a70
> path + /usr/src
> blob - 4b945edf2c73c6e2582819b283277baff81a6586
>
On Fri, Feb 16, 2024 at 11:25:51AM +, Stuart Henderson wrote:
> Also: regardless of whether it really makes sense for a given network,
> sometimes a network operator will do this anyway and as a user you have
> no control over it - and based on Kirill's description this seems a
> regression
On 15/02/24(Thu) 20:06, Kurt Miller wrote:
> On Feb 15, 2024, at 3:01 PM, Miod Vallat wrote:
> >
> >> Has been running for the last few hours without any issue.
> >> OK claudio@ on that diff.
> >
> > But it's your diff! I only polished it a bit.
> >
>
> I have also been testing various
On 2024/02/16 10:13, Stefan Sperling wrote:
> Tne driver uses the lowest basic rate anncounced by the AP:
>
> const struct iwx_rate *
> iwx_tx_fill_cmd(struct iwx_softc *sc, struct iwx_node *in,
> struct ieee80211_frame *wh, uint16_t *flags, uint32_t *rate_n_flags)
> {
> [...]
>
On Fri, Feb 16, 2024 at 11:45:30AM +0100, Kirill A. Korinsky wrote:
> Stefan,
>
> On Fri, 16 Feb 2024 10:13:50 +0100,
> Stefan Sperling wrote:
> >
> > If your AP still announces 6M even while you've disabled this rate in
> > settings,
> > then the AP is broken and there is nothing to fix for us,
Stefan,
On Fri, 16 Feb 2024 10:13:50 +0100,
Stefan Sperling wrote:
>
> If your AP still announces 6M even while you've disabled this rate in
> settings,
> then the AP is broken and there is nothing to fix for us, you could only try
> asking the vendor for an AP firmware fix. Otherwise, there
On Fri, Feb 16, 2024 at 03:22:07AM +0100, Kirill A. Korinsky wrote:
> Thus, disabling 5Ghz does help. that lead me to dig an issue on network
> settings
> side. After poking around I've discovered that settings which triggers an
> issue
> is "Minimum Data Rate Control" inside Unifi UI. It has
17 matches
Mail list logo
