Updating world with `emerge -Duv world` failed on gv-3.5.8-r4 due to problems with Xaw3d I searched further in that direction. Querying the database with `emerge -s Xaw3d` told me the actual version was installed. But it wasn't. It was removed a few days before when I switched from XFree-X11 to Xorg-X11. Reproducible: Always Steps to Reproduce: 1. Take a system with Xfree-X11, Xaw3d and old version of gv installed 2. Switch from Xfree-X11 to Xorg-X11 3. update gv Actual Results: 1. Xaw3d removed without being tagged as such 2. Lot's of lines telling me about syntax errors in Button.c and another source file, AFAIR Clip.c. Expected Results: Xaw3d tagged as removed or better reinstalled with switch to Xorg-X11 Clean update of gv from 3.5.8-r3 to 3.5.8-r4 I selected Severity = Critical due to the fact that emerge wasn't able to track the status of the Xaw3d package.
Doesn't sound like an X bug to me.
How/why was Xaw3d removed ?
Hi, Marius> How/why was Xaw3d removed ? I don't know how it was removed for I didn't know I removed it before I ran into these problems. As I am not that familiar with portage and ebuilds I didn't create local ebuilds yet. For I want to strictly use one mechanism for package management I am stuck with the official portage tree and the given tools. Updating gv didn't try to install Xaw3d and when manually installing Xaw3d emerge gave me the information that I was going to normally reinstall an already installed Xaw3d. So for me it looks like an inconsistency within the package management system. I wasn't able to trace back what happened. So I only know this: a) I installed all packages using emerge and official ebuilds. b) I had a properly installed gv for I had used it only a couple of days before this incident. c) I switched from Xfree-X11 to xorg-x11 using standard emerge. d) I wasn't able to update gv due to Xaw3d being tagged as installed when it wasn't. At this stage gv wasn't usable. Donnie> Doesn't sound like an X bug to me. I did file the bug for I was deeply concerned that my package db was broken to an unknown extend which I wasn't able to trace back. After some fixing (I reinstalled each single package) I didn't run into this problem again and the system appears stable. bye caspar
Without knowing the steps taken to induce this, there's no way to fix it. Marking as invalid (a hunch), w/out any info... reopen if it occurs again, or logs are available...
