Tag Info

__future__ belongs to the Python standard library as provided by the libpython2.7-minimal package:
$ dpkg -S /usr/lib/python2.7/__future__.py
libpython2.7-minimal:amd64: /usr/lib/python2.7/__future__.py
It should already be installed on any version of Ubuntu. In older versions, it would be provided by python2.7-minimal, but still present anyway.

You can check the value of APT::Periodic::Update-Package-Lists (Do apt-get update automatically every n-days, 0=disable):
grep APT::Periodic::Update-Package-Lists /etc/apt/apt.conf.d/10periodic
1: Every day
7: Every week

I know that this is an old question, but I stumbled upon it and it came very close to solving my problem on Ubuntu 14.04.
I thought I would post some additional instructions to add to the answer that was given above by yossile. I had to make a few minor modifications to their instructions for complete success.
Download the openssh-server package (this ...

One way to get most of the build dependencies would be to run sudo apt-get build-dep gitg. This would install all of the build dependencies needed to compile gitg.
However, note that because of the old version (0.2.7), there might be some dependencies installed that aren't needed, and some dependencies that are needed but not installed.

I WORK AROUND THIS ISSUE USING A PREVIOUS KERNEL!
user283885 is offering good solutions.
I try other (previous) kernel.
You may try a newer or previous kernel (from the ones available in the apt-cache list 3.16*).
Here is the test i made:
My actual kernel: 3.13.0-45-generic
uname -a
Linux pc-01 3.13.0-45-generic #74~precise1-Ubuntu SMP Thu Jan 15 ...

13.13 seems to be an old kernel from trusty? Whereas 3.16 is the kernel shipped with utopic.
If you ran do-release-upgrade lately, and you still use the old kernel be advised that all your old repositories ( where the old kernel headers reside) are disabled/cleaned from /etc/apt.
Usually doing a release upgrade bumps the kernel minor by at least 2 versions ...

I got some error messages removing a package, the only way I found that worked was this:
mv /var/lib/dpkg/info/package.* /tmp/
dpkg --remove --force-remove-reinstreq package
I found that although using only
dpkg --remove --force-remove-reinstreq package
does not remove the package it shows me the correct path to the file to move with:
mv ...

Vlc problem is solved when I did these:
completely removed vlc
removed the driver of my ZTE modem (ZTE MF-193E) that uses qt plugins to run
installed vlc again; and vlc runs normally
Later I installed the modem driver again, but this time vlc kept working!

It depends on the nature of the update:
If the new release fixes critical bugs, you can ask for a Stable Release Update (SRU).
If the new release provides new features, but not fixes for critical bugs, you can ask for a Backport.

Building off of @crysman's answer:
This worked for many packages on ubuntu 14.04, and the ${packages:amd64} part was to navigate to the correct folder based on my processor.
for package in `dpkg -l | grep ^ii | awk '{print $2}'`; do echo -e $package"\t"`grep License /usr/share/doc/${package%:amd64}/copyright`; done > ~/dpkg.txt

Although I personally haven't experienced this and I'm curious as to why this unfortunate turn of events has found its way to your desktop, I just opened the Software Center with no issues. I'll try my best to help.
If you want to install a piece of software, you can simply install it manually via the terminal:
sudo apt-get install [package-name]
After ...

At first sight, it looks like a dependency problem. To fix it, open the Terminal and type the following commands:
$ sudo apt-get clean
$ sudo apt-get -f install
The first one will remove any cached packages, the second one will fix all missing dependencies between packages currently installed in your system.

Your output indicates the below packages have unmet dependencies:
fglrx-amdcccle
xvba-va-driver
Which means APT tried to install the above packages but failed half way, because some other required packages are not available in your system.
Therefore we need to remove the above packages before doing anything else.
sudo dpkg --purge --force-all ...

to install software/packages on ubuntu the best way is to use
ubuntu software center
or you can use synaptic, to install synaptic on ubuntu type following in terminal
sudo apt-get install synaptic
enter your password and synaptic will be installed and then open synaptic through terminal using
sudo synaptic
or search dash for synaptic and you can ...

its very hard to decide which packages are required to your machine for installing wine. It is possible that some packages may be already installed on your system by some other applications.
I followed these steps to install wine on different machine.
note: 32bit architecture files won't work on 64bit and vise versa.
all of you systems should be ...

Solved
system settings > programs & upgrades # my system is in Portuguese
Go through all tabs and uncheck all sources (repos). Everything. It will comment the source.list and source.list.d/files* from top to bottom.
# The goal is to make a new source list
Close it with everything unchecked to make the system load an empty source
Close all apps and ...

Thanks @Serg for answer my questions! Well,, I have resolved this, and this is easy to resolved. I post here for anyone has the same propblem! Here:
$ sudo apt-get purge libpcap0.8-dev libpcap0.8:i386 libpcap-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
...

What I suggest is clear the lists and obtain a fresh copy.
Clear the List(s):
Command:
sudo rm -rf /var/lib/apt/lists/*
Obtain a Fresh Copy of Lists:
Command:
sudo apt-get update
See if that rectifies the problem. :)

This is actually a bug. I have already reported this issue on Bugs Launchpad and you can follow it using these two bug-tracker links.
bug 1424263
bug 1424265
You can fix it manually but it is to complicated. Ubuntu devs will fix it soon so I advise you just wait for updates.

Deb packages can be installed in a few ways, the most easy being through the Ubuntu Software Center. By double clicking any Deb file, by default in all supported version of Ubuntu, the Ubuntu Software Center will launch and you will have the ability to install the package. The Software Center, however, is notorious for lagging and being buggy and personally ...

The safest way is to use Ubuntu Software Center without adding personal archives to your system. You can also download them yourself: http://packages.ubuntu.com/ and use either Ubuntu Software Center or the command dpkg to install them.
A bit less safe is downloading DEB files yourself from resources you can trust. Personal archives are safe if you install ...

deb is the extension of the Debian software package format. Debian packages are used in the Debian distribution and distributions based on Debian, such as Ubuntu and others.
Double click a .deb file to open it for installation in the Ubuntu Software Center. Don't install .deb files from sources that you are not sure about.

There is a full list in the manifest file of each distribution at http://releases.ubuntu.com
To a list use
wget http://releases.ubuntu.com/utopic/ubuntu-14.10-desktop-amd64.manifest \
-q -O - | cut -f 1 > packages.manifest.list
# compare it with the list generated by
dpkg --get-selections | cut -f 1 > packages.installed.list
# from moreutils ...

There is a full list in the manifest file of each distribution at http://releases.ubuntu.com
To get just the list use
source /etc/lsb-release
wget http://releases.ubuntu.com/$DISTRIB_CODENAME/ubuntu-$DISTRIB_RELEASE-desktop-amd64.manifest \
-q -O - | cut -f 1 > packages.manifest.list
# compare it with the list generated by
dpkg --get-selections | ...

My only solution was to revert back to the old setup.
Uninstall the kernel 3.16 with (replace the version with the right one)
sudo apt-get purge linux-image-3.4.0-* linux-headers-3.4.0-*
Remove everything which brought on the problem.
sudo apt-get purge linux-generic-lts-utopic xserver-xorg-lts-utopic libgl1-mesa-glx-lts-utopic ...

I had a similar case, where libjack0 will not automatically install because skype:i386 was messing up with it (because Skype has no 64-bit version for Linux).
The solution for me simply was to force it:
sudo apt-get install libjack0
Then it asked me to confirm installation of libjack0 which meant the uninstalling of a few other conflicting programs ...

I was able to solve the problem in two steps.
Since vim had not been able to generate the required index from the compressed documentation, I extracted these files before re-running the indexer. As vim is able to deal with compressed documentation, I removed the extracted documents and adjusted the filenames of the index accordingly.
#!/bin/bash
#set -x
...

Another alternative would be to use aptitude with a search term:
aptitude search '~U'
(Note the uppercase 'U')
That means: "search for all packages that are installed and can be upgraded". Reference: aptitude user's manual
By default, aptitude search shows for each package its name, description and a few flags, but you could also adapt the output to ...

The sources.list files are in /etc/apt/sources.list.d in newer version of Ubuntu. So you need to make a symbolic link from official-package-repositories.list to the old place to solve this problem:
sudo ln -s /etc/apt/sources.list.d/official-package-repositories.list /etc/apt/sources.list

In order to fix the situation I simply removed the two packages using dpkg and re-installed using apt-get install -f. The commands I used were:
sudo dpkg --force-all -r libcairo2 libcairo-gobject2
sudo apt-get install -f

sudo apt-get clean
it will clean the repository
or
you dpkg is installing another package in Ubuntu software center or in another terminal. or you break any package during installing.
check that and run
sudo apt-get update

The basic command to show dependencies is
apt-cache depends <package>
which will show you the dependencies (there is even a rdepends option to show the reversed dependencies).
You can add this to the @ByteCommander's suggestion to use simulate install to see which packages will be installed in your system:
apt-get install -s ubuntu-desktop
...

You can try this PPA by Ivan Larionov who built a newer package from Debian experimental to try and fix this bug. I haven't tested it, so caveat emptor. See What are PPAs and how do I use them? if you don't know what a PPA is.

You don't. You divert them instead. For convenience, what I do is use a helper package like config-package-dev. With config-package-dev, you give your configuration files some specific names, and the installation will automatically do the required diversion.
For example, if your package is named foo-bar, then:
Your debian/rules will have:
%:
dh $@ ...

The observed behavior seems to result from a legitimate bug that is described at
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1365375
The above-cited report contains my short-term workaround that will render apt-get usable again.
I believe that, in essence, sudo apt-get -f install fails is a duplicate of this question.

I can not comment on posts yet, I only have enough "rep" to answer questions. As such, this is a suggestion.
Open terminal: CTRL-ALT-T
try running:
sudo apt-get install -f
This should try to resolve any dependency issues.