`ujust upgrade` installs duplicate pip executable inside ~/.local/bin

When I launched ujust upgrade it installed pip locally for my user:

~ 
❯ which pip
~/.local/bin/pip

~ 
❯ stat .local/bin/pip
  File: .local/bin/pip
  Size: 220       	Blocks: 8          IO Block: 4096   regular file
Device: 0,42	Inode: 482165      Links: 1
Access: (0755/-rwxr-xr-x)  Uid: ( 1000/ devoops)   Gid: ( 1000/ devoops)
Context: unconfined_u:object_r:gconf_home_t:s0
Access: 2024-06-07 16:10:58.758464874 +0400
Modify: 2024-06-07 16:10:58.747464780 +0400
Change: 2024-06-07 16:10:58.747464780 +0400
 Birth: 2024-06-07 16:10:58.747464780 +0400

But my system already had global pip installed:

~ 
❯ stat /usr/bin/pip
  File: /usr/bin/pip
  Size: 221       	Blocks: 8          IO Block: 4096   regular file
Device: 0,34	Inode: 115745      Links: 10
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Context: system_u:object_r:bin_t:s0
Access: 2024-06-05 12:10:38.886578649 +0400
Modify: 1970-01-01 04:00:00.000000000 +0400
Change: 2024-06-07 11:13:15.038553824 +0400
 Birth: 2024-06-05 12:10:38.886578649 +0400

Is this the intended behaviour of updating system via ujust? I haven’t seen other Linuxes installing pip in ~/.local/bin before, so that’s kinda strange

1 Like