Project

dgh

0.0
No release in over 3 years
Low commit activity in last 3 years
Dgh helps when you have to manually downgrade a large amount of packages. It requires the user to generate a file with `apt-cache policy` output for all installed packages, which it then reads. It looks for packages that have a currently installed version that doesn't exist in any repository, and prints those. This includes both locally generated packages that never did exist in any repository, and more crucially, packages that have been upgraded from e.g. a PPA that has since been removed from the system.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.0.13
~> 1.1.0
~> 0.9.0
~> 2.7.0
~> 0.8.5
~> 0.7
~> 0.7.0

Runtime

~> 0.6.0
~> 2.3.0
~> 1.4.0
 Project Readme

dgh – the Debian/Ubuntu downgrade helper¶ ↑

Ever installed a bunch of stuff from a lovely PPA or other repository, only to find that you managed to break your entire system? And then when you want to go back to the way things were before, you have to find out which packages got installed or upgraded and downgrade them manually, and hope you caught them all?

Dgh can’t solve the whole problem, but it will help you. What it does is scan the installed and available versions of all packages, and report packages that have an installed version that is higher than the version in any repository. That way you can downgrade by first removing the offending repository, then updating your package cache, then running dgh and manually downgrading the packages it reports.

Note that it can’t know which repository a package originally came from, so if you are running some homebrew packages that are meant to override versions from repositories, dgh will report them too.

Usage ==¶ ↑

Create a file with the policy output for your installed packages:

$ dpkg --get-selections|egrep '\binstall'|awk '{print $1}'| \
  xargs env LANG=C apt-cache policy|tee packages.list

Run dgh on the file:

$ dgh packages.list

The output should be the list of packages you might want to downgrade.

Contributing to dgh¶ ↑

  • Check out the develop branch to make sure the feature hasn’t been implemented or the bug hasn’t been fixed yet

  • Check out the issue tracker to make sure someone already hasn’t requested it and/or contributed it

  • Fork the project

  • Start a feature/bugfix branch off of the develop branch

  • Commit and push until you are happy with your contribution

  • Make sure to add tests for it. This is important so I don’t break it in a future version unintentionally.

  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright © 2011 Ilkka Laukkanen. See LICENSE.txt for further details.