#23287 closed defect (invalid)
rdiff-backup fails to install
Reported by: | sschym@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.8.2 |
Keywords: | Cc: | drkp (Dan Ports), ryandesign (Ryan Carsten Schmidt) | |
Port: | rdiff-backup |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
On a Macbook Pro with OSX 10.4.11, I get the following error messages when trying to install rdiff-backup:
[The full output of sudo port install -d rdiff-backup is in attached file]
checking for XPROTO... configure: error: Package requirements (xproto >= 7.0.13) were not met: Requested 'xproto >= 7.0.13' but version of Xproto is 7.0.11 Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XPROTO_CFLAGS and XPROTO_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. Error: The following dependencies failed to build: py26-xattr py26-setuptools python26 tk xorg-libXScrnSaver xorg-libXext xorg-libX11 xorg-scrnsaverproto Error: Status 1 encountered during processing. Before reporting a bug, first run the command again with the -d flag to get complete output.
Attachments (2)
Change History (13)
Changed 15 years ago by sschym@…
Attachment: | port_rdiff-backup_log.txt added |
---|
Changed 15 years ago by sschym@…
Attachment: | port_installed.txt added |
---|
Output of sudo port installed
comment:1 Changed 15 years ago by drkp (Dan Ports)
Yep, sure enough, your xproto is out of date -- you have 7.0.11 installed and 7.0.16 is current. 'port upgrade xorg-xproto' should get things working. (I'm assuming you've also done a port selfupdate recently; if not, wouldn't hurt to do that first.)
But this sounds like there's still a bug somewhere. xorg-libX11 1.3.2 depends on xorg-xproto >= 7.0.13. xorg-libX11 depends_lib on xorg-xproto, and we have a sufficiently recent version of xorg-xproto in the ports tree. Shouldn't installing libX11 automatically force xproto to be upgraded?
comment:3 follow-up: 4 Changed 15 years ago by jmroot (Joshua Root)
Port: | rdiff-backup added |
---|
Can't tell what's happening without actual debug output.
comment:4 follow-up: 5 Changed 15 years ago by drkp (Dan Ports)
Replying to jmr@…:
Can't tell what's happening without actual debug output.
Isn't that what's attached?
Seems unlikely that the problem actually involves the rdiff-backup port, though.
comment:5 follow-up: 6 Changed 15 years ago by jmroot (Joshua Root)
Replying to dports@…:
Isn't that what's attached?
Seems unlikely that the problem actually involves the rdiff-backup port, though.
There's no debug output in the attachment. I'm making no assumptions about what the actual problem is with.
comment:6 Changed 15 years ago by drkp (Dan Ports)
Replying to jmr@…:
There's no debug output in the attachment. I'm making no assumptions about what the actual problem is with.
Uh, yeah, you're right. I am a moron. I even noticed it looked remarkably unhelpful, as debug output goes!
I guess that's the difference between "port install -d" and "port -d install"
Stan, can you run "port -d install rdiff-backup" and attach the output?
comment:7 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
comment:8 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|
Most of your installed ports are quite outdated and seem to date from about October 2008. For example, you have libpng 1.2.32; libpng was updated to 1.2.33 in November 2008 and is currently at 1.2.42. Please "sudo port selfupdate" to update MacPorts base and your port definitions, then see "port outdated" for the list of everything that you need to update. You can then update everything with "sudo port upgrade outdated". You've got a lot of rebuilding ahead of you. :)
comment:9 follow-up: 11 Changed 15 years ago by sschym@…
Sorry for the noise. I figured out that something was seriously wrong with my macports installation. When I installed it, ran selfupdate and tried to install rdiff-backup for the first time, I was on wireless network, which for some reason did not allow to fetch packages properly. Later on, port upgrade outdated did not even work on a wired network, so I uninstalled macports, re-installed it and ran the updates on the wired network without problems. Now I also installed rdiff-backup on the wired network without any error messages, but I don't find it in /opt/local/bin, although "port installed" lists it as active. I suppose that's a different issue, though, so I will email support about this.
Thanks again for you help and sorry about my novice mistakes.
comment:10 Changed 15 years ago by mf2k (Frank Schima)
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:11 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to sschym@…:
I don't find it in /opt/local/bin, although "port installed" lists it as active.
That's correct. See another report of this issue. FYI, "port contents rdiff-backup" will tell you what it installed and where.
Output of sudo port install -d rdiff-backup