Question on how parrot-upgrade works.

Briefly describe your issue below:
I was wondering what in “parrot-upgrade” determines which version of a package is installed? The reason I ask is because for the second week in a row, “codium” (not a parrot product) has updates posted, but “parrot-upgrade” does not flag them for update. (Note, this may reside in the underlying mechanism of “apt”, in all probability.) Since “codium” also nags you when it is out-of-date, this can be a bit irritating.
See below for additional information.
(Please Note, could not find a “General Questions” category, otherwise I would post have posted this there.)
Thank you for your time.

What version of Parrot are you running? (include version (e.g. 4.6), edition(e.g. Home//KDE/OVA, etc.), and architecture (currently we only support amd64)
DISTRIB_ID=Parrot
DISTRIB_RELEASE=4.7
DISTRIB_CODENAME=stable
DISTRIB_DESCRIPTION=“Parrot 4.7”
PRETTY_NAME=“Parrot GNU/Linux 4.7”
NAME=“Parrot GNU/Linux”
ID=parrot
ID_LIKE=debian
VERSION=“4.7”
VERSION_ID=“4.7”
HOME_URL=“https://www.parrotsec.org/
SUPPORT_URL=“https://community.parrotsec.org/
BUG_REPORT_URL=“https://nest.parrotsec.org/

What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)
Debian Standard
Configured to multiboot with other systems? (yes / no)
No
If there are any similar issues or solutions, link to them below:
None that I can find.
If there are any error messages or relevant logs, post them below:

apt-cache showpkg codium
Package: codium
Versions: 
1.40.2-1574798581 (/var/lib/apt/lists/gitlab.com_paulcarroty_vscodium-deb-rpm-repo_raw_repos_debs_dists_vscodium_main_binary-amd64_Packages)
 Description Language: 
                 File: /var/lib/apt/lists/gitlab.com_paulcarroty_vscodium-deb-rpm-repo_raw_repos_debs_dists_vscodium_main_binary-amd64_Packages
                  MD5: b38f8538d3cead7a194af6aeeaf02e6a
 Description Language: 
                 File: /var/lib/apt/lists/deb.parrot.sh_parrot_dists_rolling_main_binary-amd64_Packages
                  MD5: b38f8538d3cead7a194af6aeeaf02e6a

1.40.1-1573814789 (/var/lib/apt/lists/deb.parrot.sh_parrot_dists_rolling_main_binary-amd64_Packages) (/var/lib/apt/lists/mirrors.mit.edu_parrot_dists_rolling_main_binary-amd64_Packages) (/var/lib/apt/lists/mirror.clarkson.edu_parrot_dists_rolling_main_binary-amd64_Packages) (/var/lib/dpkg/status)
 Description Language: 
                 File: /var/lib/apt/lists/gitlab.com_paulcarroty_vscodium-deb-rpm-repo_raw_repos_debs_dists_vscodium_main_binary-amd64_Packages
                  MD5: b38f8538d3cead7a194af6aeeaf02e6a
 Description Language: 
                 File: /var/lib/apt/lists/deb.parrot.sh_parrot_dists_rolling_main_binary-amd64_Packages
                  MD5: b38f8538d3cead7a194af6aeeaf02e6a


Reverse Depends: 
  parrot-devel,codium
  vscodium,codium
Dependencies: 
1.40.2-1574798581 - libnotify4 (0 (null)) libnss3 (2 2:3.26) gnupg (0 (null)) apt (0 (null)) libxkbfile1 (0 (null)) libsecret-1-0 (0 (null)) libgtk-3-0 (2 3.10.0) libxss1 (0 (null)) visual-studio-codium (0 (null)) visual-studio-codium (0 (null)) 
1.40.1-1573814789 - libnotify4 (0 (null)) libnss3 (2 2:3.26) gnupg (0 (null)) apt (0 (null)) libxkbfile1 (0 (null)) libsecret-1-0 (0 (null)) libgtk-3-0 (2 3.10.0) libxss1 (0 (null)) visual-studio-codium (0 (null)) visual-studio-codium (0 (null)) 
Provides: 
1.40.2-1574798581 - visual-studio-codium (= ) 
1.40.1-1573814789 - visual-studio-codium (= ) 
Reverse Provides: 

sudo apt search codium
Sorting... Done
Full Text Search... Done
codium/rolling,rolling,rolling,now 1.40.1-1573814789 amd64 [installed]
  Code editing. Redefined.

vscodium/rolling,rolling,rolling 4.7+parrot7 all
  Free/Libre Open Source Software Binaries of VSCode

We changed the name of vscodium to codium on the repository so you can remove vscodium. That change made the conflict. The version will be upgraded should be the latest version on the repository.

Hi dmknight,

I’m a bit confused. What vscodium?
Trying as best I can in satisfying your answer, I renamed the “paulcarroty” list; ran “apt update”, and deleted “/var/lib/apt/lists/gitlab.com_paulcarroty_vscodium-deb-rpm-repo_raw_repos_debs_dists_vscodium_main_binary-amd64_Packages” and
“/var/lib/apt/lists/gitlab.com_paulcarroty_vscodium-deb-rpm-repo_raw_repos_debs_dists_vscodium_InRelease”
There was no effect.

locate vscodium
/etc/firejail/vscodium.profile
/home/kbassford/.config/firejail/vscodium.profile
/usr/share/pixmaps/vscodium.png

Other than an icon and firejail profiles, what is there to delete?

Sorry, now I see this …
apt-cache showpkg codium
Package: codium
Versions:
1.40.1-1573814789 (/var/lib/apt/lists/deb.parrot.sh_parrot_dists_rolling_main_binary-amd64_Packages) (/var/lib/apt/lists/mirrors.mit.edu_parrot_dists_rolling_main_binary-amd64_Packages) (/var/lib/apt/lists/mirror.clarkson.edu_parrot_dists_rolling_main_binary-amd64_Packages) (/var/lib/dpkg/status)
Description Language:
File: /var/lib/apt/lists/deb.parrot.sh_parrot_dists_rolling_main_binary-amd64_Packages
MD5: b38f8538d3cead7a194af6aeeaf02e6a

Reverse Depends:
parrot-devel,codium
vscodium,codium
Dependencies:
1.40.1-1573814789 - libnotify4 (0 (null)) libnss3 (2 2:3.26) gnupg (0 (null)) apt (0 (null)) libxkbfile1 (0 (null)) libsecret-1-0 (0 (null)) libgtk-3-0 (2 3.10.0) libxss1 (0 (null)) visual-studio-codium (0 (null)) visual-studio-codium (0 (null))
Provides:
1.40.1-1573814789 - visual-studio-codium (= )
Reverse Provides:

looks like parrot has not updated?!?

If you check the Debian, you’ll see the “Stable”, “Testing” and “Unstable” branch. In here we are using Stable and Testing. The main branch is stable which is maybe out of dated but should have no bug (or as stable as possible).

OK, so back to the original situation, if a third party repo has an updated version, why would “apt search”, “parrot-upgrade” and “apt upgrade” not detect the updated version? (This still does not make sense to me. I’m sure a lot of folks would be interested in knowing why.)

The update model of Debian is packages wont’ be upgraded directly but they are maintained and updated by maintainers. I think you can read about how Debian packaging work on Debian docs.

I think I have found it …

  • Added the “paulcarroty” repo back in.
  • Ran “apt update”
  • Used the command: apt policy codium
apt policy codium
codium:
  Installed: 1.40.1-1573814789
  Candidate: 1.40.1-1573814789
  Version table:
     1.40.2-1574798581 500
        500 https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/raw/repos/debs vscodium/main amd64 Packages
 *** 1.40.1-1573814789 1001
       1001 https://deb.parrot.sh/parrot rolling/main amd64 Packages
       1001 http://mirrors.mit.edu/parrot rolling/main amd64 Packages
       1001 https://mirror.clarkson.edu/parrot rolling/main amd64 Packages
        100 /var/lib/dpkg/status

The higher score takes precedence.

Should I mark this as solved?