#39445 closed defect (invalid)
Activating xorg-libxcb fails
| Reported by: | jochen@… | Owned by: | jeremyhu (Jeremy Huddleston Sequoia) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.3 |
| Keywords: | Cc: | ||
| Port: | xorg-libxcb |
Description
---> Activating xorg-libxcb @1.9_0+python27
Error: org.macports.activate for port xorg-libxcb returned: Image error: /opt/local/include/xcb/bigreq.h already exists and does not belong to a registered port. Unable to activate port xorg-libxcb. Use 'port -f activate xorg-libxcb' to force the activation.
Error: Failed to install xorg-libxcb
Please see the log file for port xorg-libxcb for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_xorg-libxcb/xorg-libxcb/main.log
Error: The following dependencies were not installed: xorg-libxcb
Error: Unable to upgrade port: 1
Forcing activation as suggested let's me continue as normal and apparently everything seems to be working fine.
Change History (6)
comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)
| Owner: | changed from jeremyhu to jeremyhu@… |
|---|
comment:2 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:3 Changed 11 years ago by jochen@…
Correct (and I am fine with your "invalid"), but this hiccup was caused by port / MacPorts itself. I did not manually perform any action in /opt/local...
comment:4 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Ok, well I'm not really sure how to get to that point. From the perspective of the xorg-libxcb port (which this was filed against), everything is behaving correctly. It looks like you "somehow" got that file into your MacPorts prefix, and we balked at the collision. If you didn't put that file there yourself, and you're certain this is an issue with base, then try to track down the cause and send this over to get fixed in base.
comment:5 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Are you on recent trunk? I am always on trunk, but I haven't seen something like this. If you're on 2.1.x, it would be worth upgrading just to make sure you're testing 2.2. If you're on trunk or 2.2 beta, I'd like to know what revision you're at, so I can live on it for a while to see if I see anything like this.
comment:6 Changed 11 years ago by jochen@…
This is using 2.1.3.
Thinking about it I realize it only happened on my MacBook, not on any of my desktops. I have had issues with sleep during port upgrade outdated before, so it could have been that.
As I said, it works for me now. Unfortunately, I do not have time to look at beta or trunk/.
Thank you for your efforts