xcb fails to install on Snow Leopard MacPort 1.8.1

[felix@…]

Whie trying to install glade-3, I get a problem with xcb

[Zig:~] felix% sudo port -v install xcb
--->  Computing dependencies for xcb.
--->  Staging xcb into destroot
. missing (directory not created: File exists)
./Applications missing (directory not created: File exists)
./Developer missing (directory not created: File exists)
./Library missing (directory not created: File exists)
install -c   xcb /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb/work/destroot/opt/local/bin/xcb
+ mkdir -p /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb/work/destroot/opt/local/lib/X11/app-defaults
install -c -m 0444 Xcb.ad /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb/work/destroot/opt/local/share/X11/app-defaults/Xcb
install in . done
install -c -m 0444 xcb._man /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb/work/destroot/opt/local/share/man/man1/xcb.1
install.man in . done
Error: Target org.macports.destroot returned: no such file or directory
Warning: the following items did not execute (for xcb): org.macports.activate org.macports.destroot org.macports.install
Error: Status 1 encountered during processing.

[felix@…]

Cc Me!

[qbarnes (Quentin Barnes)]

Portfile patch

[qbarnes (Quentin Barnes)]

I upgraded to v1.8.1 and it broke as described above. Looks like the Portfile was not updated correctly last time it was touched. I added the ${destroot} in front of the post-destroot rule. Looks like it was automatic in the past and is not now?

Comparing with other Porfiles for similar packages, I also made a couple of other tweaks to the Portfile. Please review all changes and apply if appropriate.

[qbarnes (Quentin Barnes)]

Oh, I have no idea why glade3 would in any way reference this package. Any idea why it was picked up as part of a glade3 build?

[felix@…]

Replying to qbarnes@…:

Oh, I have no idea why glade3 would in any way reference this package. Any idea why it was picked up as part of a glade3 build?

Here is what glade-3 try to install: devhelp libwnck startup-notification xcb xorg-libxcb xorg-libpthread-stubs xorg-xcb-proto xorg-xcb-util xorg-libXres xorg-resourceproto python25 webkit-gtk enchant aspell hunspell gst-plugins-base gnome-vfs desktop-file-utils gnome-mime-data gstreamer gzip libogg liboil libtheora libvorbis icu libsoup gnutls libgcrypt libgpg-error libtasn1 lzo opencdk libproxy hicolor-icon-theme libgnomeui gnome-icon-theme icon-naming-utils p5-xml-simple p5-xml-namespacesupport p5-xml-sax gnome-keyring libbonoboui libbonobo libglade2 libgnome esound audiofile libgnomecanvas libart_lgpl py26-gtk py26-cairo py26-numpy atlas gcc43 gmp mpfr fftw-3 py26-nose py26-setuptools py26-gobject libffi

;-)

[felix@…]

Replying to qbarnes@…:

I upgraded to v1.8.1 and it broke as described above. Looks like the Portfile was not updated correctly last time it was touched. I added the ${destroot} in front of the post-destroot rule. Looks like it was automatic in the past and is not now?

Comparing with other Porfiles for similar packages, I also made a couple of other tweaks to the Portfile. Please review all changes and apply if appropriate.

I am not familiar with this last part... oh can I review and test it? I just do a port install xcb? Sorry for being a newbie...

[qbarnes (Quentin Barnes)]

I'm a "newbie" too for the most part. I just wait until one of the maintainers sees the patch, reviews it, tests it, and checks it in. In the mean time, you can download the patch and apply it yourself to get going.

There is no reason for glade3 to have any dependency on the "xcb" package. My guess is that the dependency on "xcb" in the gnome "startup-notification" is not necessary thinking it had something to do with xorg-xcb-* packages. If this dependency is in any way necessary, I'd be completely shocked. The xorg-xcb-* packages have to do with "X protocol C-language Binding" where the xcb package itself has to do with "X Cut Buffers".

Maybe the other way to get going is to remove the dependency on xcb from the gnome "startup-notification" package. You can let us know what happens taking that route.

[felix@…]

Replying to qbarnes@…:

I'm a "newbie" too for the most part. I just wait until one of the maintainers sees the patch, reviews it, tests it, and checks it in. In the mean time, you can download the patch and apply it yourself to get going.

I downloaded the patch, and install xcb. It seems to work.

Thanks,

There is no reason for glade3 to have any dependency on the "xcb" package. My guess is that the dependency on "xcb" in the gnome "startup-notification" is not necessary thinking it had something to do with xorg-xcb-* packages. If this dependency is in any way necessary, I'd be completely shocked. The xorg-xcb-* packages have to do with "X protocol C-language Binding" where the xcb package itself has to do with "X Cut Buffers".

To be honest with you, I am not quite sure which package in the list needs xcb... At least, for now, the glade3 install is ongoing.

Thanks gain,

[launchpad@…]

Cc Me!

[launchpad@…]

Cc Me!

[launchpad@…]

Cc Me!

[jmroot (Joshua Root)]

Committed in r59997. For future reference, there is no automated way for committers to be notified that you have attached a fix to a ticket (unless one of them happens to be the owner of the ticket or on the cc list). You will usually need to ask on IRC or the macports-dev list for someone to commit your patches.

[ac90b671@…]

Cc Me!