From: Niklas Cassel <cassel@kernel.org>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
tools@kernel.org, users@kernel.org
Subject: Re: b4 0.14.0 available
Date: Mon, 17 Jun 2024 09:41:05 +0200 [thread overview]
Message-ID: <Zm_okcZroqs_PXur@ryzen.lan> (raw)
In-Reply-To: <16c45272-8ece-4503-87b0-5fd67d052a74@kernel.org>
Hello Jiri,
On Mon, Jun 17, 2024 at 07:49:58AM +0200, Jiri Slaby wrote:
> On 14. 06. 24, 21:26, Konstantin Ryabitsev wrote:
> > If you're using b4 via the git checkout, you can either update to latest
> > master, or checkout the new stable-0.14.y branch. You can also download signed
> > tarballs from the usual location:
>
> Hi,
>
> with the new toml, strange files are installed:
> /usr/lib/python3.11/site-packages/tests/__init__.py
> /usr/lib/python3.11/site-packages/tests/__pycache__/__init__.cpython-311.opt-1.pyc
> /usr/lib/python3.11/site-packages/tests/__pycache__/__init__.cpython-311.pyc
> /usr/lib/python3.11/site-packages/tests/__pycache__/conftest.cpython-311.opt-1.pyc
> /usr/lib/python3.11/site-packages/tests/__pycache__/conftest.cpython-311.pyc
> /usr/lib/python3.11/site-packages/tests/__pycache__/test___init__.cpython-311.opt-1.pyc
> /usr/lib/python3.11/site-packages/tests/__pycache__/test___init__.cpython-311.pyc
> /usr/lib/python3.11/site-packages/tests/__pycache__/test_ez.cpython-311.opt-1.pyc
> /usr/lib/python3.11/site-packages/tests/__pycache__/test_ez.cpython-311.pyc
> /usr/lib/python3.11/site-packages/tests/__pycache__/test_mbox.cpython-311.opt-1.pyc
> /usr/lib/python3.11/site-packages/tests/__pycache__/test_mbox.cpython-311.pyc
> /usr/lib/python3.11/site-packages/tests/conftest.py
> /usr/lib/python3.11/site-packages/tests/test___init__.py
> /usr/lib/python3.11/site-packages/tests/test_ez.py
> /usr/lib/python3.11/site-packages/tests/test_mbox.py
> /usr/lib/python3.11/site-packages/b4/man/b4.5.rst
>
>
> and OTOH, man is not installed (path from 0.13):
> /usr/share/man/man5/b4.5.gz
>
> Any thoughts? I don't speak python...
There is already an issue open for this:
https://github.com/mricon/b4/issues/37
which has some more information on this.
Kind regards,
Niklas
next prev parent reply other threads:[~2024-06-17 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 19:26 b4 0.14.0 available Konstantin Ryabitsev
2024-06-17 5:49 ` Jiri Slaby
2024-06-17 7:41 ` Niklas Cassel [this message]
2024-06-17 19:10 ` Konstantin Ryabitsev
2024-07-17 12:59 ` Maxime Ripard
2024-07-17 17:15 ` Konstantin Ryabitsev
2024-07-18 11:05 ` Maxime Ripard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zm_okcZroqs_PXur@ryzen.lan \
--to=cassel@kernel.org \
--cc=jirislaby@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=tools@kernel.org \
--cc=users@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.