Bug#631938: glx-diversions: fails to upgrade or uninstall due to missing diversions with fglrx drivers
debian at abeckmann.de
Tue Jun 28 12:54:19 UTC 2011
reassign 631938 fglrx-driver 1:11-6-2
Patrick, you may not do anything to the old diversions of libGL.so.1,
libGL.so.1.2, libglx.so in your preinst scripts. Its too early, both the
diverted file and the file from 1:11-4-? exist at that time. Diversions
will be migrated in the postinst of glx-diversions.
To test: create minimal testing chroot + libgl1-mesa-dev + fglrx-glx
upgrade to unstable
On 2011-06-28 14:19, Mathias Kende wrote:
> Package: glx-diversions
> Version: 0.1.2
> Severity: serious
> Tags: sid
> Justification: Policy 0.0.0
> When upgrading glx yesterday (relevant aptitude logs are attached) the X server
> crashed during the processus (and it could not be restarted).
> This may or may not be due to the upgrade process and this may or may not have
> created the following problem.
> Package glx-diversions was left in an unconfigured state. But it could neither
> be installed nor removed. The following error message (in french, a traduction
> follow) was displayed :
>> dpkg-divert: error: erreur de correspondance dans divert-to
>> lors de la suppression de « détournement de /usr/lib/libGL.so.1.2 en par
> par fglrx-glx »
>> « détournement de /usr/lib/libGL.so.1.2
> en /usr/lib/fglrx/diversions/libGL.so.1.2 par fglrx-glx » trouvé
>> dpkg-divert: error: mismatching in divert-to during the deletion
>> of the « diversion of /usr/lib/libGL.so.1.2 in by by fglrx-glx »
>> « diversion of /usr/lib/libGL.so.1.2 in
> /usr/lib/fglrx/diversions/libGL.so.1.2 by fglrx-glx » found
> (this does not make much sense, but is is as close a traduction as I can make
> In the meantime there were no /usr/lib/libGL.so.1.2 file nor /usr/lib/fglrx
> folder on my system.
> I solved this problem by removing by hand the diversion. That is by running:
>> dpkg-divert --remove /usr/lib/libGL.so.1
>> dpkg-divert --remove /usr/lib/libGL.so.1.2
> Which did nothing (as the diversion did not exist), but put the database in a
> better state.
> After that, aptitude was able to upgrade my system (this workaround was applied
> before the first log entry of 2011-06-28).
> I think that the upgrade process broke the X server (so the upgrade is, in
> itself, responsible for the abortion of the aptitude process), but anyway
> aptitude should be able to recover from this state.
> P.S. Also reportbug is broken: I should not need to know the Debian Policy
> Manual to know that a package is unusable :)
> -- System Information:
> Debian Release: wheezy/sid
> APT prefers unstable
> APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Kernel: Linux 2.6.39-2-amd64 (SMP w/8 CPU cores)
> Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Versions of packages glx-diversions depends on:
> ii dpkg 184.108.40.206 Debian package management system
> ii nvidia-installer-cleanup 20110515+1 Cleanup after driver installation
> Versions of packages glx-diversions recommends:
> ii glx-alternative-mesa 0.1.2 allows the selection of MESA as GL
> glx-diversions suggests no packages.
> -- no debconf information
> pkg-nvidia-devel mailing list
> pkg-nvidia-devel at lists.alioth.debian.org
More information about the pkg-nvidia-devel