[SOLVED] Mint 16 to 17 __ Can't get CAJA upgraded to 1.8.x

[LinWinux]

Aaaaarrrrgh .... still having package and/or sources issues ... !!!

I thought my printer issues was the only thing that was left to get corrected. After much much reading and many attempts at making corrections, I still continue to get "broken packages" and "bad sources" messages that I can not track down. I did figure out eventually that these problems appear to be linked to anything KDE related since none of my KDE applications such as kshisen, kpatience, kbreakout work anymore. When I try to reinstall any of those in the software manager I receive use apt-get install instead (which never works) and you have held broken packages messages.
When I try to install the entire KDE desktop, I get the same message.
I also found out that I'm apparently missing numerous python files or modules.
However, I could never install any of the python related applications or files individually.

Finally, when I tried to install python 3.5 this "wanted to work" but I decided to say "NO" to the hundreds of extra packages with 2.x GB of additional disk space ... because I figured that that might really mess things up for me. So now I know that I have printer, python, KDE packages, and sources issues. At this point I would almost have to start testing each and every installed app to see if other KDE and python related applications are broken as well. I just did another sudo apt-get update and looked at the entire string. There were no errors but I noticed that there are also still 8 "saucy" lines which show up in the update process. These here ...

Code: Select all

Ign http://ppa.launchpad.net saucy InRelease
Hit http://ppa.launchpad.net saucy Release.gpg
Hit http://ppa.launchpad.net saucy Release
Hit http://ppa.launchpad.net saucy/main Sources
Hit http://ppa.launchpad.net saucy/main amd64 Packages
Hit http://ppa.launchpad.net saucy/main i386 Packages
Ign http://ppa.launchpad.net saucy/main Translation-en_US                      
Ign http://ppa.launchpad.net saucy/main Translation-en

The software sources via "Point 'n' Click" are no longer accessible. I can try to get to them from the update manager but when I select software sources ... nothing happens ... no matter how long I wait. If I try to use the icon in start menu/system ... same thing happens there ... nothing.

Again, there are no errors during the update process and it terminates normally with ... Reading package lists ... Done.
The two sources.list files which were discussed earlier in this topic are clean. No references to "saucy" there.
YES, I know that a fresh installation will probably fix everything, but I prefer to learn by doing, and not by running away from a problem.

.

[eanfrid]

There is a limit to fiddling with sources with the GUI: some incoherences may need manual editing. These "saucy" lines do not appear automagically, so what does the following command tell you ?

Code: Select all

inxi -r

[LinWinux]

Thanks for the quick response. Here's that output:
(The Venerix have to remain saucy since there's nothing newer for them)

Code: Select all

[b]inxi -r[/b]
Repos:     Active apt sources in file: /etc/apt/sources.list.d/additional-repositories.list
           deb http://liveusb.info/multisystem/depot all main
           Active apt sources in file: /etc/apt/sources.list.d/irie-blender-saucy.list
           deb http://ppa.launchpad.net/irie/blender/ubuntu trusty main
           deb-src http://ppa.launchpad.net/irie/blender/ubuntu trusty main
           Active apt sources in file: /etc/apt/sources.list.d/linrunner-tlp-saucy.list
           deb http://ppa.launchpad.net/linrunner/tlp/ubuntu trusty main
           deb-src http://ppa.launchpad.net/linrunner/tlp/ubuntu trusty main
           Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
           deb http://packages.linuxmint.com qiana main upstream import #id:linuxmint_main
           deb http://extra.linuxmint.com qiana main #id:linuxmint_extra
           deb http://archive.ubuntu.com/ubuntu trusty main restricted universe multiverse
           deb http://archive.ubuntu.com/ubuntu trusty-updates main restricted universe multiverse
           deb http://security.ubuntu.com/ubuntu/ trusty-security main restricted universe multiverse
           deb http://archive.canonical.com/ubuntu/ trusty partner
           Active apt sources in file: /etc/apt/sources.list.d/otto-kesselgulasch-gimp-saucy.list
           deb http://ppa.launchpad.net/otto-kesselgulasch/gimp/ubuntu trusty main
           deb-src http://ppa.launchpad.net/otto-kesselgulasch/gimp/ubuntu trusty main
           Active apt sources in file: /etc/apt/sources.list.d/venerix-pkg-saucy.list
           deb http://ppa.launchpad.net/venerix/pkg/ubuntu saucy main
           deb-src http://ppa.launchpad.net/venerix/pkg/ubuntu saucy main

.

[eanfrid]

Nothing new about "venerix" ? Are you sure ? http://ppa.launchpad.net/venerix/pkg/ubuntu/dists/
BTW these are the not so "mysterious" 8 lines you were talking about

(The Venerix have to remain saucy since there's nothing newer for them)

For the rest I do not see weird things in your sources. Where does python 3.5 come from, it is not in the official distro repos

[LinWinux]

I provided that information for the sake of showing how far I've taken these issues in order to find a solution. I agree that I don't think there's anything wrong with the sources.list files but it did strike me as odd that I found those 8 saucy lines in the update sequence. As far as Python 3.5 is concerned, you weren't paying attention to the details of my post. Initially there were individual python related files missing that I could track down ... none of which I was able to install due to continuous errors with this file or that file being dependent on another file. So logically thinking, I figured if python 3.5 is the latest version then perhaps the installation of the entire python 3.5 package might solve all of those file issues that I kept running across. So I did a sudo apt-get install python 3.5 in the terminal. There were no errors and the installation was going to install hundreds of new files which would take up over 2 GB of space. Up to that point I had no idea how massive python was. So to be on the safe side, I decided to opt out of installing python 3.5 by answering "N" to prevent the installation.
I'll probably end up doing a fresh install later today from scratch.

This is the one thing about Linux that I think totally *SUCKS* because say what you will about Windows which I haven't used in the past 5 years, but at least I never had to install Windows new over and over and over endlessly. I used Windows for 18 years, built and sold custom computers for years Online. In order to move people, especially noobs and long time, older Windows users from their Win to Linux instead, telling people to have fresh new installations every so often is just plain stupid. Even moreso when you tell noobs that that is the *EXPECTED* ??? way to upgrade. That's the fastest way to scare people away since many people are used to "upgrades" when a new version is released 4, 5, or even more years later at which point they're probably upgrading to a new computer anyway.

Mint developers should really spend more time working on an "all screen solution" from within already working systems.
I really am sick to death of making fresh installations all of the time. There has to be an easier more convenient way!

.

[eanfrid]

Looks like the more you explain, the more I get lost in your explanations

1/ you decided to do a release upgrade voluntarily using the explicitely not recommended method. Not recommended because this method has big chances to turn out like what you met.
2/ LM16 is not a LTS. non-LTS are testing/experimental releases, not supposed to be (my POV) your regular working config, as opposed to LTS releases.
3/ non-LTS must be upgraded every 6 months and yes, it is just plain stupid to have to do so. LTS can be upgraded every 2 years or even every 4 years. And in the latter case, you will probably never upgrade a particular machine because indeed you will have bought a new one at this time.
4/ the Mint dev team has just decided to stick to Ubuntu LTS releases to get rid of this 6-months cycle stupidity for sane and stable development.

[LinWinux]

1/ you decided to do a release upgrade voluntarily using the explicitely not recommended method. Not recommended because this method has big chances to turn out like what you met.
2/ LM16 is not a LTS. non-LTS are testing/experimental releases, not supposed to be (my POV) your regular working config, as opposed to LTS releases.

I did that because A. I knew that it wouldn't be too terrible if I ended up having to rebuild my system from scratch (which it wasn't), and B. because I just can't believe that a manual upgrade from one release to the next could be such a fiasco, and C. I'd like to think that by version *17* the Mint developers would have figured out a better/safer/more convenient way to upgrade ... hence the reason why I think it's beyond absurd, having to upgrade an entire system from scratch with a brand new installation, especially for noobs. Sounds to me like a bunch of baloney, sorry. I could see that argument if someone wanted to skip a version or two between upgrades, but when someone is going from a constantly updated 16 to a new release 17 ... that should be possible without too much fuss. Anyway, that's my thought on that and I'm sticking to it.

.