All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: b4 trouble!
Date: Wed, 1 Jul 2020 08:08:33 +0530	[thread overview]
Message-ID: <20200701023833.GB11489@Gentoo> (raw)
In-Reply-To: <20200701022934.GA11489@Gentoo>

[-- Attachment #1: Type: text/plain, Size: 3501 bytes --]

On 07:59 Wed 01 Jul 2020, Bhaskar Chowdhury wrote:
Never mind ...got it ...

08:04 $ sudo !!
sudo eselect python set 3
Password:
✔ ~/git-linux/b4 [master|✔]
08:05 $ eselect python list
Available Python interpreters, in order of preference:
   [1]   python3.7
   [2]   python3.6 (uninstalled)
   [3]   python3.8 (fallback)
   [4]   python2.7 (fallback)
✔ ~/git-linux/b4 [master|✔]
08:05 $ ./b4.sh
usage: b4 [-h] [--version] [-d] [-q]
{mbox,am,attest,attverify,pr,ty,diff} ...

A tool to work with public-inbox patches

positional arguments:
   {mbox,am,attest,attverify,pr,ty,diff}
                         sub-command help
     mbox                Download a thread as an mbox file
     am                  Create an mbox file that is ready to git-am
     attest              Submit cryptographic attestation for patches
     attverify           Verify cryptographic attestation of patches in
an mbox
     pr                  Fetch a pull request found in a message ID
     ty                  Generate thanks email when something gets
                         merged/applied
     diff                Show a range-diff to previous series revision

optional arguments:
   -h, --help            show this help message and exit
   --version             show program's version number and exit
   -d, --debug           Add more debugging info to the output (default:
False)
   -q, --quiet           Output critical information only (default:
False)


>Kai,
>
>The story goes like this :
>
>Once cloned the git repo and as suggested in README in the cloned repo
>,I made an alias in .bashrc like this :
>
>alias b4="The path to the b4.sh"
>
>source .bashrc 
>
>
>But...I got this ...I tried this from within the dir and outside of it..
>
>✔ ~/git-linux/b4 [master|✔]
>07:53 $ b4
>Traceback (most recent call last):
>   File "/home/bhaskar/git-linux/b4/b4/command.py", line 10, in <module>
>     import b4
>   File "/home/bhaskar/git-linux/b4/b4/__init__.py", line 15, in <module>
>     import requests
>ModuleNotFoundError: No module named 'requests'
>✘-1 ~/git-linux/b4 [master|✔]
>07:53 $ cd ~
>bhaskar@Gentoo_07:53:29_Wed Jul 01:~> b4
>Traceback (most recent call last):
>   File "/home/bhaskar/git-linux/b4/b4/command.py", line 10, in <module>
>     import b4
>   File "/home/bhaskar/git-linux/b4/b4/__init__.py", line 15, in <module>
>     import requests
>ModuleNotFoundError: No module named 'requests'
>
>
>Is this a expected behavior of it??? I know what it is missing, but the
>point is ,why the end user have to take care of this?? 
>
>OR, this is tool made for certain people and those people know what
>exactly do with this kind of return???
>
>I am lost ...and can we make some sanity check to before running . Will
>that be costly enough or bring more maintenance headache. I am not sure,
>because I lack knowledge ,probably.
>
>Kindly , shed some light.
>
>Thanks,
>Bhaskar

>-----BEGIN PGP SIGNATURE-----
>
>iQEzBAABCAAdFiEEnwF+nWawchZUPOuwsjqdtxFLKRUFAl779QsACgkQsjqdtxFL
>KRVU8Af+LmwX9EkEOMCY9vN55nU0Dgrzja11luTVNbAc1WvxNsbuc0xhOaC0rNdw
>AKv2W0T99iupiE7J6HJqH6dRlDqvSBwcpgqjRn3+l1x8nV+gXZOpkX8D5BTKRF38
>LVp8Vf+TPYGP/l5QzEajR205VQdoswFS42cT3UamPjm/Fg4a1iMdTm1OfP29PwQx
>PSfFRzH6ZCeZsZl/Yz8EKHW4DzrZiELWchCwOluBrMLJUyNEN8hu3zNkWbMgm6aV
>FQJ/OwrvlSIdQHgHri5KkvO3Bv+siY0FgKhsCmQIcxDONIL+MgHHc8w0vSBf4jzQ
>69wyz/IjeJmz2Anm8sVCcyjUpY2r2g==
>=fs7w
>-----END PGP SIGNATURE-----

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

      reply	other threads:[~2020-07-01  2:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01  2:29 b4 trouble! Bhaskar Chowdhury
2020-07-01  2:38 ` Bhaskar Chowdhury [this message]

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=20200701023833.GB11489@Gentoo \
    --to=unixbhaskar@gmail.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@linux.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.