Actually, you should just upgrade gwm before proceeding. gwm-1.8c-4 has the proper dependencies. This release has been out for quite a while now. The old release of gwm did not have the correct dependencies. Of course, if you are trying to upgrade gwm and the X libraries at the same time, you may run into difficulty.
You could argue that it is a dpkg bug which prevents updating the libraries because the package depends upon it, even though the new release of the package has a dependency upon the new library. This "bug" may be difficult to explain. Fortunately, the new Debian packaging tools make this type of problem less likely in the future. Stephen Early <[EMAIL PROTECTED]> writes: > In this particular case it's a bug in the gwm package; it depends on > xlib when it should have depended on elf-x11r6lib. If you remove it > before upgrading, the upgrade should work. > > You may find that there are other packages with a similar bug. You can > tell which package it is that is getting in the way; dpkg tells you here: > > > > ============================================================================ > > dpkg: considering removing xlib in favour of xlib6 ... > > dpkg: no, cannot remove xlib (--auto-deconfigure will help): > > gwm depends on xlib (>= 3.1.2-4) > ^^^ > > xlib is to be removed. > > dpkg: regarding xlib6_3.2-1.deb containing xlib6: > > xlib6 conflicts with elf-x11r6lib > > xlib provides elf-x11r6lib and is installed. > > dpkg: error processing xlib6_3.2-1.deb (--install): > > conflicting packages - not installing xlib6 > > Errors were encountered while processing: > > xlib6_3.2-1.deb > > =========================================================================== > > Once you have upgraded the X packages you can re-install the buggy > packages using the --force-depends option. > -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
