Update errors [mostly Solved]

[towwire]

I went to use Gparted and could not find it. So open MXPI and instaled it and while I was there checked to see if mkvtoolnix had made it yet, it had so I installed it. As soon as I finished I was notified that I had updates. This is what I get.

Code: Select all

 full upgrade
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Calculating upgrade...
  The following packages were automatically installed and are no longer required:
     libbrotli1 (1.0.7-2~mx17+1)
     libjavascriptcoregtk-4.0-18 (2.24.3-1~mx17+1)
     libparted-fs-resize0 (3.2-17)
     libwoff1 (1.0.2-1~mx17+1)
     yelp-xsl (3.20.1-2)
  Use 'apt autoremove' to remove them.
  The following packages will be REMOVED:
     gparted (0.33.0-0.1~mx17+1)
     libwebkit2gtk-4.0-37 (2.24.3-1~mx17+1)
     libyelp0 (3.22.0-1)
     yelp (3.22.0-1)
  The following packages will be upgraded:
     libjavascriptcoregtk-4.0-18 (2.22.7-1~mx17+1 => 2.24.3-1~mx17+1)
  1 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
  Need to get 0 B/4,854 kB of archives.
  After this operation, 56.4 MB disk space will be freed.

What's going on ? Why does it want to remove gpart ? I just installed it again.

[Stevo]

Often it's because of bogus newer packages that are from deb-multimedia or other third party distros. They have one that kills gufw and another that causes our GIMP to fail to start.

Usually using aptitude carefully on the command line and using its multiple solutions can restore the correct MX packages and bring sanity back to your system. Just make sure you read carefully what aptitude proposes to do, and don't let it it uninstall any programs that you use. If it does want to remove programs, hit "N" to go to another solution.

[towwire]

Often it's because of bogus newer packages that are from deb-multimedia or other third party distros. They have one that kills gufw and another that causes our GIMP to fail to start.

Usually using aptitude carefully on the command line and using its multiple solutions can restore the correct MX packages and bring sanity back to your system. Just make sure you read carefully what aptitude proposes to do, and don't let it it uninstall any programs that you use. If it does want to remove programs, hit "N" to go to another solution.

Every thing I have install or update has come thru MXPI.
Most of the upgrade are one's from the test repo. Like all the packages for winehq-staging, vlc, mesa-va-drivers, handbrake, ffmpeg, claws-mail, mkvtoolnix, and reinstalled gparted.

I can copy the history, if it would help. What do I need to do using aptitude commands?

[towwire]

Ok I started aptitude and it showed four programs two adobe and two being held in their state.
libjavascriptcoregtk-4.0-18 This in the update was no longer required
libwedkit2gtk-4.0-37 This in the update will be REMOVED

I close it and then open synaptic and installed the adobe ones. Restarted aptitude and the two held programs could not be upgrade without deleting some stuff but could be downgraded to a lower version. Did not do anything.

So then I check history, they were installed when I upgrade mkvtoolkit and reinstalled gparted, the same version I had before.

Code: Select all

2019-08-13  15:49:49  upgrade  mkvtoolnix                           amd64  35.0.0-1~mx17+2                 36.0.0-1~mx17+1
2019-08-13  15:49:48  upgrade  mkvtoolnix-gui                       amd64  35.0.0-1~mx17+2                 36.0.0-1~mx17+1
2019-08-13  15:48:40  install  yelp-xsl                             all    <none>                          3.20.1-2
2019-08-13  15:48:40  install  yelp                                 amd64  <none>                          3.22.0-1
2019-08-13  15:48:40  install  libyelp0                             amd64  <none>                          3.22.0-1
2019-08-13  15:48:40  install  gparted                              amd64  <none>                          0.33.0-0.1~mx17+1
2019-08-13  15:48:38  install  libwoff1                             amd64  <none>                          1.0.2-1~mx17+1
2019-08-13  15:48:38  install  libwebkit2gtk-4.0-37                 amd64  <none>                          2.22.7-1~mx17+1
2019-08-13  15:48:38  install  libparted-fs-resize0                 amd64  <none>                          3.2-17
2019-08-13  15:48:38  install  libjavascriptcoregtk-4.0-18          amd64  <none>                          2.22.7-1~mx17+1
2019-08-13  15:48:38  install  libbrotli1                           amd64  <none>                          1.0.7-2~mx17+1

So I tried running the update again and when Y/n show it was n.

Code: Select all

Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libbrotli1 libjavascriptcoregtk-4.0-18 libwebkit2gtk-4.0-37 libwoff1
  libyelp0 yelp yelp-xsl
Suggested packages:
  kpartx dmraid gpart udftools libwebkit2gtk-4.0-37-gtk2
Recommended packages:
  gnome-user-guide
The following NEW packages will be installed:
  libbrotli1 libjavascriptcoregtk-4.0-18 libwebkit2gtk-4.0-37 libwoff1
  libyelp0 yelp yelp-xsl
The following packages will be upgraded:
  gparted
1 upgraded, 7 newly installed, 0 to remove and 223 not upgraded.
Need to get 0 B/19.6 MB of archives.
After this operation, 72.8 MB of additional disk space will be used.
Do you want to continue? [Y/n] 

So I decided to try some deleting, first the mkvtoolnix packages and then check for updates.
Still some of the stuff showed, so deleted gparted (0.33.0-0.1~mx17+1) and of course the was some auto-remove when checked for updates. I did do the auto-remove and did a couple of check for updates.

I then installed mkvtoolnix packages and ran check for updates after, nothing wrong. So I decided to install gparted from stable instead of the one in test since that seems to be where the errors come from. Funny since I've used the test one for quite awhile.

Anyway the check for updates show fine now. The gparted in test should be tested by others and maybe removed.

NOTE: GParted has a new live stable version 1.0.0-3, maybe a new deb made at least for MX-19.

[oops]

FI: I had the same issue with GParted, lollypop and midori.

[Stevo]

I'm not familiar with aptitude's sort-of-a-gui. I use it on the command line with commands like

Code: Select all

sudo aptitude install <problem-package-name>

and it starts presenting proposed solutions. If you don't like the first, you hit "N" to get it to try another. You want one that installs the problem package without removing any other programs, even if it means downgrading some packages down to stretch or mx17 versions. You can then try upgrading those from the test repo again (mesa-va-drivers) to see if you get them back.

The NZ repos also seem to be missing packages often, and that can lead to the same sort of issues.

[towwire]

For now I will just stick with the older version of Gparted. I have the latest on a usb if I want to use it. But thanks for your help.