Check updates seems to be broken

[joekamprad]

You both are banned now till 2030 because … how dare are you this is so off the topic i do even not read it. For posting food go #insta

very interesting !

[pebcak]

I needed to “resource” .bashrc where I have /.local/bin adde to the path. Now everything seems to be working:

cut --version 
cut (GNU coreutils) 8.32
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David M. Ihnat, David MacKenzie, and Jim Meyering.

$ echo `echo "1:OK:3:4"|cut -d: -f2`
OK

And checkupdates has nothing to declare for the moment!

[Kresimir]

Phew!

It should work now, when there are updates available.

[pebcak]

@Kresimir

This is turning into quite a detective story.

That was a great detective work! Amazing! Thank you so much! You have lifted a great weight off my chest not being able to use checkupdates.

It was stupid of me to call the script cut at the first place. I didn’t realize the collision. It is now called cute . It is a modified version of checkupdates to look for updates in Testing repo.

CheckUpdatesTesting >> cut

[pebcak]

Here it is:

$ cute

archlinux-keyring 20210820-1 -> 20210902-1
dnscrypt-proxy 2.0.45-2 -> 2.1.0-1
edk2-ovmf 202105-1 -> 202108-1
grep 3.6-1 -> 3.7-1
gtk3 1:3.24.30-2 -> 1:3.24.30+29+gfe19b20492-1
krb5 1.19.1-1 -> 1.19.2-1
libblockdev 2.25-2 -> 2.26-1
libedit 20210522_3.1-1 -> 20210714_3.1-1
libglvnd 1.3.3-1 -> 1.3.4-1
libnsl 1.3.0-2 -> 2.0.0-1
libseccomp 2.5.1-2 -> 2.5.2-1
libxml2 2.9.10-9 -> 2.9.12-2
libxslt 1.1.34-5 -> 1.1.34-6
linux-lts 5.10.61-1 -> 5.10.62-1
linux-lts-headers 5.10.61-1 -> 5.10.62-1
ntfs-3g 2017.3.23-5 -> 2021.8.22-1
python 3.9.6-1 -> 3.9.7-1
python-dnspython 1:1.16.0-3 -> 1:2.1.0-1
sdl 1.2.15-14 -> 1.2.15+387+gfbfcca32-1
smbclient 4.14.7-1 -> 4.14.7-2
soundtouch 2.3.0-1 -> 2.3.0-2

Isn’t that cute?

[Kresimir]

Just adorable!

[manuel]

As you can see, adding user paths to PATH can lead to problems, and can be even dangerous…
If you must add user paths, better add them as last in the PATH.

Or if you want to replace a system command with your own version, add it to /usr/local/bin. It works because /usr/local/bin is in PATH before /usr/bin.

Anyway, you really have to know what you are doing. Otherwise you may even compromise the security of your system.

[pebcak]

I have really lived up to my username today, haven’t I?

@manuel

If you must add user paths, better add them as last in the PATH.

How do I do that just in case? This is how it is now:

echo $PATH
/home/pebcak/.local/bin:/home/pebcak/.local/bin:/usr/local/bin:/usr/bin:/var/lib/snapd/snap/bin:/usr/local/sbin:/var/lib/flatpak/exports/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl

I have the following line in .bashrc:

export PATH="$HOME/.local/bin:$PATH"

[manuel]

@pebcak

How do I do that just in case?

Simply put the PATH “components” in different order:

export PATH="$PATH:$HOME/.local/bin"

[pebcak]

Nice! Thanks! Done!