HOW TO: Revert installed packages to official release versions

[millusions]

Love your work!!!

thanks so much for this information, took me a couple of hours of tinkering to find it!

but all is good now

[geoaraujo]

Healthy computing starts with proper package hygiene!

[SteveRiley]

In my approximately four year history with *buntu distros, I've encountered this problem two times previous to this occurrence. Eventually the problem self-resolves as newer package versions appear in either the PPA or one of the normal pockets.

However, I don't think it's wise for systems to remain in an "orphan" state. If some other packaging related problem surfaced, such a state would complicate troubleshooting. That's why I documented a method for returning to "normal."

Healthy computing starts with proper package hygiene!

[doctordruidphd]

I believe you meant "saucy 13.10":

Yep, sorry.

I think (hope) it was a one-time mess-up.

I do my updates from the command line, so:

sudo apt-get -d dist-upgrade

downloads the packages to be updated. The file name will include git if it is a git package.

[geoaraujo]

I believe you meant "saucy 13.10":

The issue before was that the PPA had been set up (in saucy 13.04) to grab and build daily snapshots of code from KDE's git

So that was an one-time error? But how can I know that is not happenning anymore? As I've said, I had kubuntu-ppa enabled and don't mind having git packages as long as they eventually got update to final release.

[doctordruidphd]

As of yesterday, I re-enabled the kubuntu ppas on my system, as I heard about a kde update. The update is indeed there, went fine, no problems with package versions, and no git packages. So all appears to be fixed.

[claydoh]

Well to muddy things for you a bit, just because a package has git in the file name does not necessarily mean it is something that is a problem. The issue before was that the PPA had been set up (in saucy 13.04) to grab and build daily snapshots of code from KDE's git. All of KDE, built very day automatically. The stoppage of these daily builds is what was causing the orphan packages after time. That problem is, I believe solved by Steve's instructions. Having daily builds running near and after final release was an error, something that should not have happened.


These packages had version names based on date and git revision numbers, so most, hence the "git" reference in the filenames. However normal package still might (rarely) have it if the code was pulled from git to fix a specific bug or something. The version naming used in this case takes into account future upgrades, so that in theory would not cause a problem down the road.

I do not see any 13.10 packages in the kubuntu updates PPA that contain "git" in the file name, but there are a couple hundred, so I might have missed some. There are no packages in the kubuntu backports ppa for Saucy 13.10 yet. If you can provide info on which packages you see that has this, I am sure we can see if it is an issue or not.

[geoaraujo]

I'm sorry if I'm being redundant but I've always had kubuntu-ppa and kubuntu-ppa/backports enabled and never had a problem, except for some now and then not-so-stable packages. But as I recall this thread was started because kubuntu-ppa had git stuff that were orphan packages. But then, it got the 4.11.3 update and now it has git stuff again. Are those git packages orphan as well? I thought we were disabling the ppa because it had orphan packages that would never be update, and the our systems would be in some kind of limbo. But now it got the update. So if we enable it again, we'll get the 4.11.3, then the git stuff and later the 4.11.4? Is this how it works?

[marco07]

You have the kubuntu ppa disabled, right?

That is right.

[doctordruidphd]

You have the kubuntu ppa disabled, right?

I am showing the git packages already mentioned still in the kubuntu ppa.
Until they are pulled, it is probably a good idea not to re-enable it (unless you want the git stuff).

[marco07]

marco@Lenovo:~$ apt-cache policy kate
kate:
Installed: 4:4.11.2a-0ubuntu1
Candidate: 4:4.11.2a-0ubuntu1
Version table:
*** 4:4.11.2a-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages
100 /var/lib/dpkg/status

I am on my other desktop and just out of criusity tried for kate. Again seems the system should be OK.

[SteveRiley]

However... kate kate-data katepart kwrite libkateinterfaces4 libkatepartinterfaces4

Yeah, seems that kate and its hangers-on still haven't been removed: https://launchpad.net/~kubuntu-ppa/+...s_filter=saucy



You need to comment out the lines in /etc/apt/sources.list.d/kubuntu-ppa-ppa-release.list and run apt-get update to remove those leftovers from your local package cache.

[doctordruidphd]

However:

greenman@Wolfenstein:/etc/apt$ apt-cache policy kate
kate:
  Installed: 4:4.11.2a-0ubuntu1
  Candidate: 4:4.11.2a+git20131023+bzr2699+pkg147~ubuntu13.10.1
  Version table:
     4:4.11.2a+git20131023+bzr2699+pkg147~ubuntu13.10.1 0
        500 http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu/ saucy/main amd64 Packages
 *** 4:4.11.2a-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
        100 /var/lib/dpkg/status

Same deal with: kate kate-data katepart kwrite libkateinterfaces4 libkatepartinterfaces4

[marco07]

marco@DX200:~$ apt-cache policy kde-workspace
kde-workspace:
Installed: 4:4.11.2-0ubuntu1
Candidate: 4:4.11.2-0ubuntu1
Version table:
*** 4:4.11.2-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages
100 /var/lib/dpkg/status
marco@DX200:~$

Thus, it seems my system should be OK.
Thanks!

[doctordruidphd]

As of right now (All Hallows Eve / Samhain) there are still a handful of git packages in there, and nothing else. So now would not be a good time.