Apt install/autoremove shows 1 not upgraded

Briefly describe your issue below:
using apt autoremove OR install shows:

0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

while using full-upgrade shows
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Nowhere does it list which package it is referring to. Presumably this has no effect on the OS though is there a way to determine which package it is referring to and/or why it continues to display this?

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)
Installed from Parrot-security-4.7_x64.iso
$uname -a
Linux parrot 5.2.0-2parrot1-amd64 #1 SMP Debian 5.2.9-2parrot1 (2019-08-25) x86_64 GNU/Linux

What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)
Running on encrypted persistent USB

cat /etc/os-release 
PRETTY_NAME="Parrot GNU/Linux 4.7"
NAME="Parrot GNU/Linux"
ID=parrot
ID_LIKE=debian
VERSION="4.7"
VERSION_ID="4.7"

Configured to multiboot with other systems? (yes / no)
no

If there are any similar issues or solutions, link to them below:

If there are any error messages or relevant logs, post them below:

sudo apt list --upgradeable
Listing... Done

cat /var/log/aptitude 
Aptitude 0.8.12: log report
Wed, Oct 23 2019 16:24:28 -0500

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 0 packages, and remove 0 packages.

========================================

Log complete.

1 Like

Hi! Thank you for report our bug. Can you please check the output of sudo apt list --upgradeable please? I think your output above is missed something.

Hey, I included that in my post but again:
$sudo apt list --upgradeable
Listing… Done

That is really weird because i am seeing that so it should show something in upgradeable.
For example, i am having

$apt list --upgradable 
Listing... Done
intel-media-va-driver/rolling 19.3.0+dfsg1-1 amd64 [upgradable from: 19.2.1+dfsg1-2]
ldap-utils/rolling 2.4.48+dfsg-1+b1 amd64 [upgradable from: 2.4.48+dfsg-1]
libegl-mesa0/rolling 19.2.1-1 amd64 [upgradable from: 19.1.6-1]
libfreetype6/rolling 2.10.1-2 amd64 [upgradable from: 2.9.1-4]
libgbm1/rolling 19.2.1-1 amd64 [upgradable from: 19.1.6-1]
libgl1-mesa-dri/rolling 19.2.1-1 amd64 [upgradable from: 19.1.6-1]
libglapi-mesa/rolling 19.2.1-1 amd64 [upgradable from: 19.1.6-1]
libglx-mesa0/rolling 19.2.1-1 amd64 [upgradable from: 19.1.6-1]
libgraphite2-3/rolling 1.3.13-11 amd64 [upgradable from: 1.3.13-8]
libldap-2.4-2/rolling 2.4.48+dfsg-1+b1 amd64 [upgradable from: 2.4.48+dfsg-1]
libosmesa6/rolling 19.2.1-1 amd64 [upgradable from: 19.1.6-1]
libssl-dev/rolling 1.1.1d-2 amd64 [upgradable from: 1.1.1d-1]
libssl1.1/rolling 1.1.1d-2 amd64 [upgradable from: 1.1.1d-1]
mesa-va-drivers/rolling 19.2.1-1 amd64 [upgradable from: 19.1.6-1]
mesa-vdpau-drivers/rolling 19.2.1-1 amd64 [upgradable from: 19.1.6-1]
mesa-vulkan-drivers/rolling 19.2.1-1 amd64 [upgradable from: 19.1.6-1]
phonon-backend-gstreamer-common/rolling 4:4.9.1-2 amd64 [upgradable from: 4:4.9.1-1]
seclists/rolling,rolling 2019.3-0kali1 all [upgradable from: 2019.2-0kali6]

They are not upgraded because of package conflict problem

it looks like those have already been installed for me e.g.

$sudo cat /var/log/dpkg.log | grep mesa | tail -1
2019-10-19 12:46:59 status installed libglx-mesa0:amd64 19.2.1-1

It is a little weird. I meant if the package isn’t upgraded, it should be in upgradeable list. Let me ask other guys in team for help.

thank you, and again when I run full-upgrade it says
$sudo apt full-upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

if I run sudo parrot-upgrade
on the step where it runs:
apt --fix-broken --fix-missing install || echo failed to fix conflicts
it spits out
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
but the final step with dist-upgrade again is all 0’s

Oh okay so it could be problem from parrot-upgrade output. We have to verify and fix this. Thanks for your report :smiley:

1 Like

you’re welcome. but to be sure its the calling of apt install from below

cat /usr/bin/parrot-upgrade
#!/bin/bash
set -e
DEBIAN_FRONTEND=“noninteractive”
DEBIAN_PRIORITY=“critical”
DEBCONF_NOWARNINGS=“yes”
export DEBIAN_FRONTEND DEBIAN_PRIORITY DEBCONF_NOWARNINGS
apt update || echo failed to update index lists
dpkg --configure -a || echo failed to fix interrupted upgrades
apt --fix-broken --fix-missing install || echo failed to fix conflicts #THIS LINE
apt -y --allow-downgrades --fix-broken --fix-missing dist-upgrade

this also occurs when i run apt autoremove

$sudo apt autoremove
Reading package lists… Done
Building dependency tree
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

1 Like

Hello, I have the same problem.
sudo apt list --upgradeable
Listing… Done
gnuradio-dev/rolling 3.8.0.0-5 amd64 [upgradable from: 3.7.13.4-4+b1]
gnuradio/rolling 3.8.0.0-5 amd64 [upgradable from: 3.7.13.4-4+b1]
ldap-utils/rolling 2.4.48+dfsg-1+b1 amd64 [upgradable from: 2.4.48+dfsg-1]
libfreetype6/rolling 2.10.1-2 amd64 [upgradable from: 2.9.1-4]
libldap-2.4-2/rolling 2.4.48+dfsg-1+b1 amd64 [upgradable from: 2.4.48+dfsg-1]
mesa-vulkan-drivers/rolling 19.2.1-1 amd64 [upgradable from: 19.1.6-1]
phonon-backend-gstreamer-common/rolling 4:4.9.1-2 amd64 [upgradable from: 4:4.9.1-1]
seclists/rolling,rolling 2019.3-0kali1 all [upgradable from: 2019.2-0kali6]

This is not the same issue, as apt list --upgradeable does not echo any packages in my case.

1 Like

So the contents of /etc/apt/preferences.d/parrot-pinning are as follows:

Package: *
Pin: release o=Parrot
Pin-Priority: 1001

Package: *
Pin: release o=Debian
Pin-Priority: 50

Package: *
Pin: release o=Kali
Pin-Priority: 50

Package: *
Pin: release o=Ubuntu
Pin-Priority: 50

Package: *
Pin: release o=vscode stable
Pin-Priority: 50

////
This is the same contents I see on a live boot, though if I comment out the first three lines the ‘1 not upgraded’ goes away. Hopefully that helps.

1 Like

Able to reproduce this bug. Made a new live persistent USB. changed nothing; just set the language/time and added a network connection. Ran sudo parrot-upgrade and upon reaching the end the same exact problem occurs.

We must wait,such is our destiny.

there are still i386 packages having error so i don’t understand the 1 part :frowning:

yes its common that happens cause some packages are not upgraded thus prevent them from crashing and they have this notation:-“The following packages have been kept back”

Please read through the whole thread, if it were that simple this would be closed:

  • In this instance there is no “the following packages have been kept back” message.
  • Again only apt install or apt autoremove list ‘1 not upgraded’.
  • full upgrade or dist upgrade do not display ‘1 not upgraded’.
  • apt-mark showhold # shows nothing
  • apt list --upgradeable # shows nothing
1 Like

Screenshot%20at%202019-11-10%2011-21-11

2 Likes

ok …i’ve seen it
don’t use sudo apt full-upgrade and sudo apt dist-upgrade in parrot os those are kali-linux commands of late they didn’t work for so to fully upgrade,in screenshot you got ; ie sudo parrot-upgrade
and to update is: sudo apt-get update
and sudo apt autoremove (PACKAGE_NAME)… the package to be removed is missing

As I said in my previous post I made a new live boot and used only parrot-upgrade and the problem persists. Furthermore, the parrot-upgrade command calls the dist-upgrade command. To see run:

cat /usr/bin/parrot-upgrade

and
“and sudo apt autoremove (PACKAGE_NAME)… the package to be removed is missing”
you don’t have to pass an argument to autoremove

1 Like