It seems some changes are being pushed without actually testing
on the non-clang architectures.
Can this get backed out until the correct procedure is followed?
But I think it is also important to realize that not every
new behaviour of clang is "systems ready". Some of what they
are pushing
On Thu, Dec 29, 2022 at 09:52:49AM +0100, Omar Polo wrote:
> ksh actually supports that style of globbing :)
Fair enough! TIL -- but the GNU Grep bit stands, though :)
Any takers on the diff? Should be an easy one
paultag
--
:wq
On 2022-12-30 15:06 +01, David Demelier wrote:
> On Fri, 2022-12-30 at 14:50 +0100, Florian Obser wrote:
>> That seems reasonable. This might be the full list, do you want to do
>> all?
>>
>> usr.bin/htpasswd/htpasswd.c:fprintf(stderr, "usage:\t%s [file]
>> login\n", __progname);
>>
On Fri, 2022-12-30 at 14:50 +0100, Florian Obser wrote:
> That seems reasonable. This might be the full list, do you want to do
> all?
>
> usr.bin/htpasswd/htpasswd.c:fprintf(stderr, "usage:\t%s [file]
> login\n", __progname);
> usr.sbin/installboot/installboot.c: fprintf(stderr,
That seems reasonable. This might be the full list, do you want to do
all?
usr.bin/htpasswd/htpasswd.c:fprintf(stderr, "usage:\t%s [file] login\n",
__progname);
usr.sbin/installboot/installboot.c: fprintf(stderr, "usage:\t%1$s [-nv] [-r
root] disk [stage1%2$s]\n"
Most utilities seem to use a unique space between the colon and the
program name, vmctl uses a tab that will expand to two spaces once
invoked.
e.g.
pfctl: unknown command line argument: tata ...
usage: pfctl [-deghNnPqrvz] [-a anchor] [-D macro=value] [-F modifier]
[-f file]
tar foobar
tar: f
On 2022/12/30 02:06, Theo Buehler wrote:
> I understand that it is a libcbor major bump. Why is the libfido2 bump
> needed?
We can run into a problem with bumps with inter-library dependencies
in base. If software from packages uses functions from both libraries,
if you _don't_ bump major for
