Comment 11 for bug 1300557

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

According to the dpkg.log for that date, quite a lot: libc-bin for amd64. Also gcc-4.8, gcc-4.9, along with g++, cpp, libgcc1, libstdc++6 etc, for amd64 and i386; and libitm1, libgomp1, libgfortran3, libasan0, libatomic1, libtsan0, libquadmath0, libthumbnailer0, apport, apport-gtk, python3-problem-report, python3-apport, binfmt-support, dh-apport, libgtk2-perl, python-boto, python-lxml, python3-lxml, unity-webapps-qml, mobile-broadband-provider-info, python-keystoneclient,

The day before I upgraded among other things libffi6 (for i386 and amd64) and libffi-dev, dconf-gsettings-backend, dconf-service, libdconf1, various dconf tools and frontends, libglib2.0-*, libunity-control-center1 and unity-control-center, libido3-0.1-0, lxc and related packages, libapparmor1 and apparmor, libqt5positioning5, libunity-gtk3-parser0, openjdk-7 and icedtea-7, ubuntu-release-upgrader and update-manager, libcompizconfig0, compiz-gnome, compiz-plugins-default, libdecoration0, compiz-core, compiz, im-config, kerneloops-daemon, indicator-*, unity-scope-*, libreoffice, unity, libunity-core-6.0.9, unity-services, ubuntu-mono, libvirt, the kernel, and dh-apparmor.