Re: Cannot build x11/libX11 in poudriere addendum: x11/xcb-util, too
Apologies for the top post. But I think your answer is here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218208 HTH --Chris On Wed, 29 Mar 2017 21:06:08 +0200 "O. Hartmann" wrote > Am Wed, 29 Mar 2017 19:13:13 +0200 > Miroslav Lachman <000.f...@quip.cz> schrieb: > > > I am trying to upgrade my package repository which was working fine for > > a long time. I didn't change any options. Run just usual commands > > > > # poudriere ports -u -p default > > > > # poudriere options -z global -p default -f > > /usr/local/etc/poudriere.d/pkglists/global > > > > # poudriere bulk -v -j 10_3_amd64 -z global -p default -f > > /usr/local/etc/poudriere.d/pkglists/global > > > > but it failed with the following error: > > > > [00:00:14] >> [01][00:00:00] Starting build of x11/libX11 > > [00:00:14] >> [01][00:00:00] Status for build x11/libX11: check-sanity > > [00:00:14] >> [01][00:00:00] Status for build x11/libX11: pkg-depends > > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: fetch-depends > > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: fetch > > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: distfiles > > /vol0/poudriere/distfiles -> > > /vol0/poudriere/data/.m/10_3_amd64-default-global/01/portdistfiles > > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: checksum > > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: distfiles > > /vol0/poudriere/data/.m/10_3_amd64-default-global/01/portdistfiles -> > > /vol0/poudriere/distfiles > > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: > > extract-depends > > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: extract > > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: patch-depends > > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: patch > > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: build-depends > > [00:00:17] >> [01][00:00:03] Status for build x11/libX11: lib-depends > > [00:00:17] >> [01][00:00:03] Status for build x11/libX11: configure > > [00:00:19] >> [01][00:00:05] Finished build of x11/libX11: Failed: > > configure > > [00:00:19] >> [01][00:00:05] Skipping build of devel/apache-ant: > > Dependent port x11/libX11 failed > > [00:00:19] >> [01][00:00:05] Skipping build of > > textproc/elasticsearch: Dependent port x11/libX11 failed > > [00:00:19] >> [01][00:00:05] Skipping build of textproc/fop: > > Dependent port x11/libX11 failed > > [00:00:19] >> [01][00:00:05] Skipping build of java/sigar: Dependent > > port x11/libX11 failed > > [00:00:19] >> [01][00:00:05] Skipping build of x11/libXext: > > Dependent port x11/libX11 failed > > [00:00:19] >> [01][00:00:05] Skipping build of x11/libXrender: > > Dependent port x11/libX11 failed > > [00:00:19] >> [01][00:00:05] Skipping build of x11-toolkits/libXt: > > Dependent port x11/libX11 failed > > [00:00:19] >> [01][00:00:05] Skipping build of java/openjdk7: > > Dependent port x11/libX11 failed > > [00:00:19] >> [01][00:00:05] Skipping build of java/openjdk8: > > Dependent port x11/libX11 failed > > [00:00:19] >> [01][00:00:05] Skipping build of > > converters/wkhtmltopdf: Dependent port x11/libX11 failed > > [00:00:19] >> Stopping 8 builders > > > > > > Poudriere log + work/libX11-1.6.5/config.log are attached. > > > > Miroslav Lachman > > ___ > > freebsd-...@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org" > > On several building machines (3) the same failure after updating just right > now the ports tree and trying rebuilding everything (see below). Every X11 > related ports fails to build :-( > > [...] > checking for XCB... no > configure: error: Package requirements (xcb >= 1.4) were not met: > > Package pthread-stubs was not found in the pkg-config search path. > Perhaps you should add the directory containing 'pthread-stubs.pc' > to the PKG_CONFIG_PATH environment variable > Package 'pthread-stubs', required by 'xcb', not found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standar
Re: Cannot build x11/libX11 in poudriere addendum: x11/xcb-util, too
Am Wed, 29 Mar 2017 19:13:13 +0200 Miroslav Lachman <000.f...@quip.cz> schrieb: > I am trying to upgrade my package repository which was working fine for > a long time. I didn't change any options. Run just usual commands > > # poudriere ports -u -p default > > # poudriere options -z global -p default -f > /usr/local/etc/poudriere.d/pkglists/global > > # poudriere bulk -v -j 10_3_amd64 -z global -p default -f > /usr/local/etc/poudriere.d/pkglists/global > > but it failed with the following error: > > [00:00:14] >> [01][00:00:00] Starting build of x11/libX11 > [00:00:14] >> [01][00:00:00] Status for build x11/libX11: check-sanity > [00:00:14] >> [01][00:00:00] Status for build x11/libX11: pkg-depends > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: fetch-depends > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: fetch > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: distfiles > /vol0/poudriere/distfiles -> > /vol0/poudriere/data/.m/10_3_amd64-default-global/01/portdistfiles > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: checksum > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: distfiles > /vol0/poudriere/data/.m/10_3_amd64-default-global/01/portdistfiles -> > /vol0/poudriere/distfiles > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: > extract-depends > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: extract > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: patch-depends > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: patch > [00:00:15] >> [01][00:00:01] Status for build x11/libX11: build-depends > [00:00:17] >> [01][00:00:03] Status for build x11/libX11: lib-depends > [00:00:17] >> [01][00:00:03] Status for build x11/libX11: configure > [00:00:19] >> [01][00:00:05] Finished build of x11/libX11: Failed: > configure > [00:00:19] >> [01][00:00:05] Skipping build of devel/apache-ant: > Dependent port x11/libX11 failed > [00:00:19] >> [01][00:00:05] Skipping build of > textproc/elasticsearch: Dependent port x11/libX11 failed > [00:00:19] >> [01][00:00:05] Skipping build of textproc/fop: > Dependent port x11/libX11 failed > [00:00:19] >> [01][00:00:05] Skipping build of java/sigar: Dependent > port x11/libX11 failed > [00:00:19] >> [01][00:00:05] Skipping build of x11/libXext: > Dependent port x11/libX11 failed > [00:00:19] >> [01][00:00:05] Skipping build of x11/libXrender: > Dependent port x11/libX11 failed > [00:00:19] >> [01][00:00:05] Skipping build of x11-toolkits/libXt: > Dependent port x11/libX11 failed > [00:00:19] >> [01][00:00:05] Skipping build of java/openjdk7: > Dependent port x11/libX11 failed > [00:00:19] >> [01][00:00:05] Skipping build of java/openjdk8: > Dependent port x11/libX11 failed > [00:00:19] >> [01][00:00:05] Skipping build of > converters/wkhtmltopdf: Dependent port x11/libX11 failed > [00:00:19] >> Stopping 8 builders > > > Poudriere log + work/libX11-1.6.5/config.log are attached. > > Miroslav Lachman > ___ > freebsd-...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org" On several building machines (3) the same failure after updating just right now the ports tree and trying rebuilding everything (see below). Every X11 related ports fails to build :-( [...] checking for XCB... no configure: error: Package requirements (xcb >= 1.4) were not met: Package pthread-stubs was not found in the pkg-config search path. Perhaps you should add the directory containing `pthread-stubs.pc' to the PKG_CONFIG_PATH environment variable Package 'pthread-stubs', required by 'xcb', not found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XCB_CFLAGS and XCB_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. ===> Script "configure" failed unexpectedly. Please report the problem to ga...@freebsd.org [maintainer] and attach the "/wrkdirs/usr/ports/x11/xcb-util/work/xcb-util-0.4.0/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Stop. make: stopped in /usr/ports/x
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
On Thu, 26 Jan 2012 11:20:27 -0600, Kevin Oberman wrote: Have you run 'pkg-libchk -o | grep xcb-' from sysutils/bsdadminscripts? it should provide a list of ports that need to be re-built after the xcb-utils upgrade to 1.8. What's strange is that this didn't work for me the first five times I tried it. I had to use the portmaster --check-depends to find a missing package that wasn't getting picked up by the broken things listed in pkg_libchk ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
Hello, On Thu, Jan 26, 2012 at 6:20 PM, Kevin Oberman wrote: > Have you run 'pkg-libchk -o | grep xcb-' from > sysutils/bsdadminscripts? it should provide a list of ports that need > to be re-built after the xcb-utils upgrade to 1.8. > > Funny, I logged in just now to write about this posting from the forums: http://forums.freebsd.org/showpost.php?p=163415&postcount=17 I've used pkg_linchk on one machine, and reinstalled all ports that depended on the missing libs. After that xfce4-wm upgraded easily. One machine fixed. One more machine to go... -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
On Thu, Jan 26, 2012 at 5:23 AM, Torfinn Ingolfsen wrote: > Hello, > > On Thu, Jan 26, 2012 at 1:24 AM, Zhihao Yuan wrote: > >> On Tue, Jan 17, 2012 at 10:39 PM, Heino Tiedemann >> wrote: >> > Michael Johnson wrote: >> > >> >> Out of curiosity, what does 'grep xcb-aux >> /usr/local/libdata/pkgconfig/*' >> >> show? >> > >> > Nothing. No Output. >> > >> > Heino >> > >> > ___ >> > freebsd-ports@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" >> >> I solved this problem by rebuilding libxfce4menu (to update the >> libtool profile). >> >> I tried that, but it didn't help here. I used 'portupgrade -f > libxfce4menu'. > My machine runs: > root@kg-v2# uname -a > FreeBSD kg-v2.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Jul 16 02:07:14 > CEST 2011 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 > and the ports tree was updated today (26.1.2012). > > I also tried rebuilding (using portupgrade -f) a few other packages, to see > if xfce4-wm would upgrade afterwards: > libxfce4gui > libxfce4util > xfce4-conf > xfce4-desktop > xfce4-settings > > But that didn't help either. Have you run 'pkg-libchk -o | grep xcb-' from sysutils/bsdadminscripts? it should provide a list of ports that need to be re-built after the xcb-utils upgrade to 1.8. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
Hello, On Thu, Jan 26, 2012 at 1:24 AM, Zhihao Yuan wrote: > On Tue, Jan 17, 2012 at 10:39 PM, Heino Tiedemann > wrote: > > Michael Johnson wrote: > > > >> Out of curiosity, what does 'grep xcb-aux > /usr/local/libdata/pkgconfig/*' > >> show? > > > > Nothing. No Output. > > > > Heino > > > > ___ > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > I solved this problem by rebuilding libxfce4menu (to update the > libtool profile). > > I tried that, but it didn't help here. I used 'portupgrade -f libxfce4menu'. My machine runs: root@kg-v2# uname -a FreeBSD kg-v2.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Jul 16 02:07:14 CEST 2011 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 and the ports tree was updated today (26.1.2012). I also tried rebuilding (using portupgrade -f) a few other packages, to see if xfce4-wm would upgrade afterwards: libxfce4gui libxfce4util xfce4-conf xfce4-desktop xfce4-settings But that didn't help either. -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
On Wed, Jan 18, 2012 at 5:39 AM, Heino Tiedemann
wrote:
> Michael Johnson wrote:
>
> > Out of curiosity, what does 'grep xcb-aux /usr/local/libdata/pkgconfig/*'
> > show?
>
> Nothing. No Output.
>
I have the same problem, on two machines, with updated ports.
Machine a:
root@kg-v2# uname -a
FreeBSD kg-v2.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Jul 16 02:07:14
CEST 2011 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
root@kg-v2# grep xcb-aux /usr/local/libdata/pkgconfig/*
root@kg-v2#
Machine b:
root@kg-quiet# uname -a
FreeBSD kg-quiet.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #1: Sat Jan 7
14:05:57 CET 2012 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/GENERIC
amd64
root@kg-quiet# grep xcb-aux /usr/local/libdata/pkgconfig/*
root@kg-quiet#
For comparison, here is output from another machine, where I haven't
updated ports yet:
root@kg-v7# uname -a
FreeBSD kg-v7.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #7: Sat Jul 9 23:00:31
CEST 2011 r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
root@kg-v7# grep xcb-aux /usr/local/libdata/pkgconfig/*
/usr/local/libdata/pkgconfig/xcb-aux.pc:Libs: -L${libdir} -lxcb-aux
root@kg-v7# pkg_info -W /usr/local/libdata/pkgconfig/xcb-aux.pc
/usr/local/libdata/pkgconfig/xcb-aux.pc was installed by package
xcb-util-0.3.6,1
Upgrading (portupgrade -R) xfce4-wm fails on both machine a and b, like
this:
gmake[2]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/po'
Making all in settings-dialogs
gmake[2]: Entering directory
`/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs'
gmake all-am
gmake[3]: Entering directory
`/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs'
CC xfwm4_settings-xfwm4-settings.o
CCLD xfwm4-settings
CC xfwm4_tweaks_settings-tweaks-settings.o
CCLD xfwm4-tweaks-settings
CC xfwm4_workspace_settings-workspace-settings.o
CCLD xfwm4-workspace-settings
libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or
unhandled argument `/usr/local/lib/libxcb-aux.la'
gmake[3]: *** [xfwm4-workspace-settings] Error 1
gmake[3]: Leaving directory
`/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3'
gmake: *** [all] Error 2
*** Error code 1
Stop in /usr/ports/x11-wm/xfce4-wm.
*** Error code 1
Stop in /usr/ports/x11-wm/xfce4-wm.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade20120126-14455-tviad6-0 env UPGRADE_TOOL=portupgrade
UPGRADE_PORT=xfce4-wm-4.8.2 UPGRADE_PORT_VER=4.8.2 make
** Fix the problem and try again.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! x11-wm/xfce4-wm (xfce4-wm-4.8.2)(unknown build error)
--
Regards,
Torfinn Ingolfsen
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
On Tue, Jan 17, 2012 at 10:39 PM, Heino Tiedemann wrote: > Michael Johnson wrote: > >> Out of curiosity, what does 'grep xcb-aux /usr/local/libdata/pkgconfig/*' >> show? > > Nothing. No Output. > > Heino > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" I solved this problem by rebuilding libxfce4menu (to update the libtool profile). -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
On Wednesday 18 January 2012 22:51:49 Kevin Oberman wrote: > On Wed, Jan 18, 2012 at 6:08 PM, Jason Hellenthal wrote: > > On Wed, Jan 18, 2012 at 05:46:07PM -0600, ajtiM wrote: > > > On Wednesday 18 January 2012 08:28:38 Volodymyr Kostyrko wrote: > > > > Subbsd wrote: > > > > > I found two broken rebuild after upgrade xcb: > > > > pkg_libchk from sysutils/bsdadminscripts would point you to all ports > > > > that should be rebuilt. > > > > > > I ran pkg_libchk and I got: > > > diablo-jdk-16 misses libz.so.4 > > > > Unrelated to the issue... > > > > FYI the above package provides what the below package is utilized for. > > > > > diablo-jre-16 misses libz.so.4 > > > and both misses liodbcinst.so > > FYI The man page for pkg_libchk discusses this and explains that thy are > false positives. > > pkg_libchk -o | grep xcb- > should just give the relevant information. Thank you. I did and I didn't get anything. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
Heino Tiedemann wrote: Kevin Oberman wrote: pkg_libchk -o | grep xcb- should just give the relevant information. Its a lot (all ports up to Date except x11-wm/xfce4-wm): It's not about been up to date, it's about been correctly linked. Go rebuild them. -- Sphinx of black quartz judge my vow. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
Kevin Oberman wrote: > pkg_libchk -o | grep xcb- > should just give the relevant information. Its a lot (all ports up to Date except x11-wm/xfce4-wm): # pkg_libchk -o | grep xcb- x11-fm/thunar: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-aux.so.0 x11-fm/thunar: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-event.so.1 x11-fm/thunar: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-atom.so.1 x11-fm/thunar: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-aux.so.0 x11-fm/thunar: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-event.so.1 x11-fm/thunar: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-atom.so.1 x11-toolkits/libwnck: /usr/local/bin/wnck-urgency-monitor misses libxcb-aux.so.0 x11-toolkits/libwnck: /usr/local/bin/wnck-urgency-monitor misses libxcb-event.so.1 x11-toolkits/libwnck: /usr/local/bin/wnck-urgency-monitor misses libxcb-atom.so.1 x11-toolkits/libwnck: /usr/local/bin/wnckprop misses libxcb-aux.so.0 x11-toolkits/libwnck: /usr/local/bin/wnckprop misses libxcb-event.so.1 x11-toolkits/libwnck: /usr/local/bin/wnckprop misses libxcb-atom.so.1 x11-toolkits/libwnck: /usr/local/lib/libwnck-1.so.22 misses libxcb-aux.so.0 x11-toolkits/libwnck: /usr/local/lib/libwnck-1.so.22 misses libxcb-event.so.1 x11-toolkits/libwnck: /usr/local/lib/libwnck-1.so.22 misses libxcb-atom.so.1 x11-toolkits/libxfce4gui: /usr/local/lib/libxfcegui4.so.7 misses libxcb-aux.so.0 x11-toolkits/libxfce4gui: /usr/local/lib/libxfcegui4.so.7 misses libxcb-event.so.1 x11-toolkits/libxfce4gui: /usr/local/lib/libxfcegui4.so.7 misses libxcb-atom.so.1 x11-toolkits/libxfce4gui: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-aux.so.0 x11-toolkits/libxfce4gui: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-event.so.1 x11-toolkits/libxfce4gui: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-atom.so.1 editors/mousepad: /usr/local/bin/mousepad misses libxcb-aux.so.0 editors/mousepad: /usr/local/bin/mousepad misses libxcb-event.so.1 editors/mousepad: /usr/local/bin/mousepad misses libxcb-atom.so.1 archivers/squeeze: /usr/local/bin/squeeze misses libxcb-aux.so.0 archivers/squeeze: /usr/local/bin/squeeze misses libxcb-event.so.1 archivers/squeeze: /usr/local/bin/squeeze misses libxcb-atom.so.1 x11-fm/thunar-vfs: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-aux.so.0 x11-fm/thunar-vfs: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-event.so.1 x11-fm/thunar-vfs: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-atom.so.1 x11-wm/xfce4-desktop: /usr/local/bin/xfdesktop misses libxcb-aux.so.0 x11-wm/xfce4-desktop: /usr/local/bin/xfdesktop misses libxcb-event.so.1 x11-wm/xfce4-desktop: /usr/local/bin/xfdesktop misses libxcb-atom.so.1 x11-wm/xfce4-desktop: /usr/local/bin/xfdesktop-settings misses libxcb-aux.so.0 x11-wm/xfce4-desktop: /usr/local/bin/xfdesktop-settings misses libxcb-event.so.1 x11-wm/xfce4-desktop: /usr/local/bin/xfdesktop-settings misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libclock.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libclock.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libclock.so misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libdirectorymenu.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libdirectorymenu.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libdirectorymenu.so misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/liblauncher.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/liblauncher.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/liblauncher.so misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libpager.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libpager.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libpager.so misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libseparator.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libseparator.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libseparator.so misses libxc
Re: xcb-util
On Wed, Jan 18, 2012 at 6:08 PM, Jason Hellenthal wrote: > > > On Wed, Jan 18, 2012 at 05:46:07PM -0600, ajtiM wrote: > > On Wednesday 18 January 2012 08:28:38 Volodymyr Kostyrko wrote: > > > Subbsd wrote: > > > > I found two broken rebuild after upgrade xcb: > > > > > > > pkg_libchk from sysutils/bsdadminscripts would point you to all ports > > > that should be rebuilt. > > > > I ran pkg_libchk and I got: > > diablo-jdk-16 misses libz.so.4 > > Unrelated to the issue... > > FYI the above package provides what the below package is utilized for. > > > diablo-jre-16 misses libz.so.4 > > and both misses liodbcinst.so > FYI The man page for pkg_libchk discusses this and explains that thy are false positives. pkg_libchk -o | grep xcb- should just give the relevant information. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
On Wed, Jan 18, 2012 at 05:46:07PM -0600, ajtiM wrote: > On Wednesday 18 January 2012 08:28:38 Volodymyr Kostyrko wrote: > > Subbsd wrote: > > > I found two broken rebuild after upgrade xcb: > > > > > pkg_libchk from sysutils/bsdadminscripts would point you to all ports > > that should be rebuilt. > > I ran pkg_libchk and I got: > diablo-jdk-16 misses libz.so.4 Unrelated to the issue... FYI the above package provides what the below package is utilized for. > diablo-jre-16 misses libz.so.4 > and both misses liodbcinst.so > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
On Wednesday 18 January 2012 08:28:38 Volodymyr Kostyrko wrote: > Subbsd wrote: > > I found two broken rebuild after upgrade xcb: > > > > 1) vlc doesn't build ( > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) > > 2) kalzium doesn't build ( It is corrected after force rebuild > > something from ocaml\* or > > facile\*) > > pkg_libchk from sysutils/bsdadminscripts would point you to all ports > that should be rebuilt. I ran pkg_libchk and I got: diablo-jdk-16 misses libz.so.4 diablo-jre-16 misses libz.so.4 and both misses liodbcinst.so but I have: ocate libz.so.4 /usr/local/lib/compat/libz.so.4 but I don't have libodbcinst.so and I rebuilt diablo. libreoffice 3.4.5 misses libjawt.so I have: locate libjawt.so /usr/local/diablo-jdk1.6.0/jre/lib/i386/libjawt.so /usr/local/diablo-jre1.6.0/lib/i386/libjawt.so redland and rasqar misses libyajl.so.1 which I don't have and opera -11.60 misses libz.so.5 which I don't have. Which ports have libs which I need it, please? Mitja http://jpgmag.com/people/lumiwa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
Subbsd wrote: I found two broken rebuild after upgrade xcb: 1) vlc doesn't build ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) 2) kalzium doesn't build ( It is corrected after force rebuild something from ocaml\* or facile\*) pkg_libchk from sysutils/bsdadminscripts would point you to all ports that should be rebuilt. -- Sphinx of black quartz judge my vow. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
On Wednesday 18 January 2012 03:07:09 you wrote: > I found two broken rebuild after upgrade xcb: > > 1) vlc doesn't build ( > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) > 2) kalzium doesn't build ( It is corrected after force rebuild > something from ocaml\* or > facile\*) I use mplayer and I don't have a problem. Is kalzium part of kdeedu? If it is than I didn't have a problem to rebuilt. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
Subbsd wrote: > I found two broken rebuild after upgrade xcb: > > 1) vlc doesn't build ( > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) > 2) kalzium doesn't build ( It is corrected after force rebuild > something from ocaml\* or > facile\*) 3) xfce4-wm libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' g Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
I found two broken rebuild after upgrade xcb: 1) vlc doesn't build ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) 2) kalzium doesn't build ( It is corrected after force rebuild something from ocaml\* or facile\*) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
Michael Johnson wrote: > Out of curiosity, what does 'grep xcb-aux /usr/local/libdata/pkgconfig/*' > show? Nothing. No Output. Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
On Tue, Jan 17, 2012 at 10:32 PM, Heino Tiedemann wrote: > Kevin Oberman wrote: > > > On Tue, Jan 17, 2012 at 11:18 AM, Heino Tiedemann > > wrote: > >> gmake[3]: Entering directory > >> `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' > >> CC xfwm4_settings-xfwm4-settings.o > >> CCLD xfwm4-settings > >> CC xfwm4_tweaks_settings-tweaks-settings.o > >> CCLD xfwm4-tweaks-settings > >> CC xfwm4_workspace_settings-workspace-settings.o > >> CCLD xfwm4-workspace-settings > >> libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' > or > >> unhandled argument `/usr/local/lib/libxcb-aux.la' > >> gmake[3]: *** [xfwm4-workspace-settings] Error 1 > >> gmake[3]: Leaving directory > >> `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' > >> gmake[2]: *** [all] Error 2 > >> gmake[2]: Leaving directory > >> `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' > >> gmake[1]: *** [all-recursive] Error 1 > >> gmake[1]: Leaving directory > `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3' > >> gmake: *** [all] Error 2 > >> *** Error code 1 > >> > >> Stop in /usr/ports/x11-wm/xfce4-wm. > >> *** Error code 1 > >> > >> Stop in /usr/ports/x11-wm/xfce4-wm. > >> > >> > >> > >> Any ideas? > >> > >> > > Install sysutils/bsdadminscripts and use pkg_libchk to find the missed > > dependency. I just tracked down that metacity had been missed causing > > several ports to fail, but your case may well be something different. > > > Ooops: > > # pkg_libchk > Thunar-1.3.0: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-aux.so.0 > Thunar-1.3.0: /usr/local/lib/thunarx-2/thunar-uca.so misses > libxcb-event.so.1 > Thunar-1.3.0: /usr/local/lib/thunarx-2/thunar-uca.so misses > libxcb-atom.so.1 > Thunar-1.3.0: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses > libxcb-aux.so.0 > Thunar-1.3.0: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses > libxcb-event.so.1 > Thunar-1.3.0: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses > libxcb-atom.so.1 > libwnck-2.30.6: /usr/local/bin/wnck-urgency-monitor misses libxcb-aux.so.0 > libwnck-2.30.6: /usr/local/bin/wnck-urgency-monitor misses > libxcb-event.so.1 > libwnck-2.30.6: /usr/local/bin/wnck-urgency-monitor misses libxcb-atom.so.1 > libwnck-2.30.6: /usr/local/bin/wnckprop misses libxcb-aux.so.0 > libwnck-2.30.6: /usr/local/bin/wnckprop misses libxcb-event.so.1 > libwnck-2.30.6: /usr/local/bin/wnckprop misses libxcb-atom.so.1 > libwnck-2.30.6: /usr/local/lib/libwnck-1.so.22 misses libxcb-aux.so.0 > libwnck-2.30.6: /usr/local/lib/libwnck-1.so.22 misses libxcb-event.so.1 > libwnck-2.30.6: /usr/local/lib/libwnck-1.so.22 misses libxcb-atom.so.1 > libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-aux.so.0 > libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-event.so.1 > libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-atom.so.1 > libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses > libxcb-aux.so.0 > libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses > libxcb-event.so.1 > libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses > libxcb-atom.so.1 > mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-aux.so.0 > mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-event.so.1 > mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-atom.so.1 > squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-aux.so.0 > squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-event.so.1 > squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-atom.so.1 > thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses > libxcb-aux.so.0 > thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses > libxcb-event.so.1 > thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses > libxcb-atom.so.1 > vlc-1.1.13,3: > /usr/local/lib/vlc/plugins/control/libglobalhotkeys_plugin.so misses > libxcb-keysyms.so.1 > vlc-1.1.13,3: > /usr/local/lib/vlc/plugins/video_output/libxcb_window_plugin.so misses > libxcb-keysyms.so.1 > xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-aux.so.0 > xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-event.so.1 > xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-atom.so.1 > xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses > libxcb-aux.so.0 > xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses > libxcb-event.so.1 > xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses > libxcb-atom.so.1 > xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libactions.so misses > libxcb-aux.so.0 > xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libactions.so misses > libxcb-event.so.1 > xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libactions.so misses > libxcb-atom.so.1 > xfce4-panel-4.8.6: > /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses > libxcb-aux.so.0 > xfce4-panel-4.8.6: > /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
Kevin Oberman wrote: > On Tue, Jan 17, 2012 at 11:18 AM, Heino Tiedemann > wrote: >> gmake[3]: Entering directory >> `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' >> CC xfwm4_settings-xfwm4-settings.o >> CCLD xfwm4-settings >> CC xfwm4_tweaks_settings-tweaks-settings.o >> CCLD xfwm4-tweaks-settings >> CC xfwm4_workspace_settings-workspace-settings.o >> CCLD xfwm4-workspace-settings >> libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or >> unhandled argument `/usr/local/lib/libxcb-aux.la' >> gmake[3]: *** [xfwm4-workspace-settings] Error 1 >> gmake[3]: Leaving directory >> `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' >> gmake[2]: *** [all] Error 2 >> gmake[2]: Leaving directory >> `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' >> gmake[1]: *** [all-recursive] Error 1 >> gmake[1]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3' >> gmake: *** [all] Error 2 >> *** Error code 1 >> >> Stop in /usr/ports/x11-wm/xfce4-wm. >> *** Error code 1 >> >> Stop in /usr/ports/x11-wm/xfce4-wm. >> >> >> >> Any ideas? >> >> > Install sysutils/bsdadminscripts and use pkg_libchk to find the missed > dependency. I just tracked down that metacity had been missed causing > several ports to fail, but your case may well be something different. Ooops: # pkg_libchk Thunar-1.3.0: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-aux.so.0 Thunar-1.3.0: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-event.so.1 Thunar-1.3.0: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-atom.so.1 Thunar-1.3.0: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-aux.so.0 Thunar-1.3.0: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-event.so.1 Thunar-1.3.0: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-atom.so.1 libwnck-2.30.6: /usr/local/bin/wnck-urgency-monitor misses libxcb-aux.so.0 libwnck-2.30.6: /usr/local/bin/wnck-urgency-monitor misses libxcb-event.so.1 libwnck-2.30.6: /usr/local/bin/wnck-urgency-monitor misses libxcb-atom.so.1 libwnck-2.30.6: /usr/local/bin/wnckprop misses libxcb-aux.so.0 libwnck-2.30.6: /usr/local/bin/wnckprop misses libxcb-event.so.1 libwnck-2.30.6: /usr/local/bin/wnckprop misses libxcb-atom.so.1 libwnck-2.30.6: /usr/local/lib/libwnck-1.so.22 misses libxcb-aux.so.0 libwnck-2.30.6: /usr/local/lib/libwnck-1.so.22 misses libxcb-event.so.1 libwnck-2.30.6: /usr/local/lib/libwnck-1.so.22 misses libxcb-atom.so.1 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-aux.so.0 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-event.so.1 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-atom.so.1 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-aux.so.0 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-event.so.1 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-atom.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-aux.so.0 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-event.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-atom.so.1 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-aux.so.0 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-event.so.1 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-atom.so.1 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-aux.so.0 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-event.so.1 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-atom.so.1 vlc-1.1.13,3: /usr/local/lib/vlc/plugins/control/libglobalhotkeys_plugin.so misses libxcb-keysyms.so.1 vlc-1.1.13,3: /usr/local/lib/vlc/plugins/video_output/libxcb_window_plugin.so misses libxcb-keysyms.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-aux.so.0 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-event.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-atom.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-aux.so.0 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-event.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-atom.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-aux.so.0 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-event.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-atom.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-aux.so.0 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-event.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-atom.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libclock.so misses libxcb-aux.so.0 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
On Tue, Jan 17, 2012 at 11:18 AM, Heino Tiedemann wrote: > Hi, > > > after I did that: > > , > | 20120116: > | AFFECTS: users of x11/xcb-util > | AUTHOR: ga...@freebsd.org > | > | x11/xcb-util was updated to 0.3.8 and was split in new modules. > | Dependencies were adjusted but main port symbols were moved to a single > | library, xcb-util.so. For this reason, all dependent ports must be > | recompiled.If you use portmaster, run: > | > | # portmaster -R -r xcb-util-0 > | > | Or for portupgrade: > | > | # portupgrade -r xcb-util-0\* > ` > > > I got that: > > > gmake[3]: Entering directory > `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' > CC xfwm4_settings-xfwm4-settings.o > CCLD xfwm4-settings > CC xfwm4_tweaks_settings-tweaks-settings.o > CCLD xfwm4-tweaks-settings > CC xfwm4_workspace_settings-workspace-settings.o > CCLD xfwm4-workspace-settings > libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or > unhandled argument `/usr/local/lib/libxcb-aux.la' > gmake[3]: *** [xfwm4-workspace-settings] Error 1 > gmake[3]: Leaving directory > `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' > gmake[2]: *** [all] Error 2 > gmake[2]: Leaving directory > `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3' > gmake: *** [all] Error 2 > *** Error code 1 > > Stop in /usr/ports/x11-wm/xfce4-wm. > *** Error code 1 > > Stop in /usr/ports/x11-wm/xfce4-wm. > > > > Any ideas? > > Install sysutils/bsdadminscripts and use pkg_libchk to find the missed dependency. I just tracked down that metacity had been missed causing several ports to fail, but your case may well be something different. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
Hi, after I did that: , | 20120116: | AFFECTS: users of x11/xcb-util | AUTHOR: ga...@freebsd.org | | x11/xcb-util was updated to 0.3.8 and was split in new modules. | Dependencies were adjusted but main port symbols were moved to a single | library, xcb-util.so. For this reason, all dependent ports must be | recompiled.If you use portmaster, run: | | # portmaster -R -r xcb-util-0 | | Or for portupgrade: | | # portupgrade -r xcb-util-0\* ` I got that: gmake[3]: Entering directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' CC xfwm4_settings-xfwm4-settings.o CCLD xfwm4-settings CC xfwm4_tweaks_settings-tweaks-settings.o CCLD xfwm4-tweaks-settings CC xfwm4_workspace_settings-workspace-settings.o CCLD xfwm4-workspace-settings libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' gmake[3]: *** [xfwm4-workspace-settings] Error 1 gmake[3]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/x11-wm/xfce4-wm. *** Error code 1 Stop in /usr/ports/x11-wm/xfce4-wm. Any ideas? Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
I had fresh installed FreeBSD 9.0-RC3 ad than I updated to 9.0-Release. I ran portsnap fetch update and portmaster -a and xcb was updated. It happened day before when was /usr/ports/UPDATING update wtih portmaster -R -r xcb-util.0 which I ran yesterday and it happened what I wrote before. On Mon, Jan 16, 2012 at 5:17 PM, Freddie Cash wrote: > On Mon, Jan 16, 2012 at 3:11 PM, Chuck Swiger wrote: > > On Jan 16, 2012, at 2:51 PM, ajtiM wrote: > >> FreeBSD 9.0 is out, many people updated, new installation...KDE 4.7.4 is > >> coming in the ports (I hope no) and now all this reinstallation for > xcb-util. > >> Is it not possible to synchronized a little with the other ports? > > > > You're the one managing your machine(s). If you want a package systems > which releases less frequently than FreeBSD ports are updated, then either > do not update your ports as rapidly, or consider switching to something > like pkgsrc from NetBSD. > > Alternatively, switch to using pre-built, binary packages via the -P > and -PP switches to portmaster/portupgrade, or even pkg_upgrade (from > the sysutils/bsdadminscripts port). > > >> I need to reinstall about 300 ports (KDE, Firefox, libxul, GIMP...). > >> It is to much... > > > > Why do you need to reinstall? > > Perhaps because he just completed an upgrade from 8.x to 9.0? While > there are ways to mitigate the need for awhile (misc/compat8x, leaving > old libraries around, various switches to portmaster/portupgrade to > keep old versions of libs in /usr/local/compat, etc), eventually, one > should reinstall all ports when upgrading between major versions of > FreeBSD. > > However, one has the option of scheduling when that rebuilt/reinstall > occurs. If you know a new version of X, KDE, Firefox are coming down > the pipe soon, then why not wait until those major updates hit the > ports tree? And then do everything all at once? Rather than > reinstalling everything after the 8->9 upgrade, and then again for > libxcb, then again for KDE, then again for Port X, Port Y, etc, etc, > etc. > > Just because a new version hits the ports tree, doesn't mean you have > to rush right out, this second, and upgrade to it. :) > > > -- > Freddie Cash > fjwc...@gmail.com > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
On Mon, Jan 16, 2012 at 3:16 PM, Olivier Smedts wrote: > The only direct dependency on xcb-util is set by cairo. Please note I > use "EXPLICIT_PACKAGE_DEPENDS=yes" in my /etc/make.conf, that could > explain the difference ? What is EXPLICIT_PACKAGE_DEPENDS, and where is it documented? I think I understand what it's supposed to do (only list direct dependencies between packages during install, not not everything all the way up the dependency chain in every package). But there's no mention of it in make.conf(5). And the only result of a grep for it in /usr/ports/Mk is a conditional that compares it's value. -- Freddie Cash fjwc...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
On Mon, Jan 16, 2012 at 3:11 PM, Chuck Swiger wrote: > On Jan 16, 2012, at 2:51 PM, ajtiM wrote: >> FreeBSD 9.0 is out, many people updated, new installation...KDE 4.7.4 is >> coming in the ports (I hope no) and now all this reinstallation for xcb-util. >> Is it not possible to synchronized a little with the other ports? > > You're the one managing your machine(s). If you want a package systems which > releases less frequently than FreeBSD ports are updated, then either do not > update your ports as rapidly, or consider switching to something like pkgsrc > from NetBSD. Alternatively, switch to using pre-built, binary packages via the -P and -PP switches to portmaster/portupgrade, or even pkg_upgrade (from the sysutils/bsdadminscripts port). >> I need to reinstall about 300 ports (KDE, Firefox, libxul, GIMP...). >> It is to much... > > Why do you need to reinstall? Perhaps because he just completed an upgrade from 8.x to 9.0? While there are ways to mitigate the need for awhile (misc/compat8x, leaving old libraries around, various switches to portmaster/portupgrade to keep old versions of libs in /usr/local/compat, etc), eventually, one should reinstall all ports when upgrading between major versions of FreeBSD. However, one has the option of scheduling when that rebuilt/reinstall occurs. If you know a new version of X, KDE, Firefox are coming down the pipe soon, then why not wait until those major updates hit the ports tree? And then do everything all at once? Rather than reinstalling everything after the 8->9 upgrade, and then again for libxcb, then again for KDE, then again for Port X, Port Y, etc, etc, etc. Just because a new version hits the ports tree, doesn't mean you have to rush right out, this second, and upgrade to it. :) -- Freddie Cash fjwc...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
2012/1/16 ajtiM :
> FreeBSD 9.0 is out, many people updated, new installation...KDE 4.7.4 is
> coming in the ports (I hope no) and now all this reinstallation for xcb-util.
> Is it not possible to synchronized a little with the other ports?
>
> I need to reinstall about 300 ports (KDE, Firefox, libxul, GIMP...).
> It is to much...
Du you use portmaster, or portupgrade ?
For me, also KDE and firefox user (~400 ports installed), portmaster
only wants to upgrade few ports...
Before the xcb-util update, during the ports tree freeze, my installed
ports were nearly up-to-date.
# portsnap fetch update
# portmaster -R -r xcb-util-0
===>>> The following actions will be taken if you choose to proceed:
Upgrade xcb-util-0.3.6,1 to xcb-util-0.3.8,1
Install devel/gmake
Install devel/gperf
Install devel/libtool
Upgrade cairo-1.10.2_2,1 to cairo-1.10.2_3,1
Upgrade glib-2.28.8_2 to glib-2.28.8_3
Upgrade pcre-8.21 to pcre-8.21_1
Install x11/xcb-util-renderutil
The only direct dependency on xcb-util is set by cairo. Please note I
use "EXPLICIT_PACKAGE_DEPENDS=yes" in my /etc/make.conf, that could
explain the difference ?
After the upgrade, KDE and firefox still work fine.
--
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org - against HTML email & vCards X
www: http://www.gid0.org - against proprietary attachments / \
"Il y a seulement 10 sortes de gens dans le monde :
ceux qui comprennent le binaire,
et ceux qui ne le comprennent pas."
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
On Jan 16, 2012, at 2:51 PM, ajtiM wrote: > FreeBSD 9.0 is out, many people updated, new installation...KDE 4.7.4 is > coming in the ports (I hope no) and now all this reinstallation for xcb-util. > Is it not possible to synchronized a little with the other ports? You're the one managing your machine(s). If you want a package systems which releases less frequently than FreeBSD ports are updated, then either do not update your ports as rapidly, or consider switching to something like pkgsrc from NetBSD. > I need to reinstall about 300 ports (KDE, Firefox, libxul, GIMP...). > It is to much... Why do you need to reinstall? Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
xcb-util
FreeBSD 9.0 is out, many people updated, new installation...KDE 4.7.4 is coming in the ports (I hope no) and now all this reinstallation for xcb-util. Is it not possible to synchronized a little with the other ports? I need to reinstall about 300 ports (KDE, Firefox, libxul, GIMP...). It is to much... Mitja http://jpgmag.com/people/lumiwa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11/xcb-util downgraded?
On Sat, 17 Dec 2011, Chris Rees wrote: On 17 December 2011 10:47, Denise H. G. wrote: With the version bump of x11/xcb-util, some ports seems to be broken. However, after recompiling x11/startup-notification, and all the ports that depend on x11/startup-notification, everything will be OK. And x11/startup-notification needs to be set to depend on x11/xcb-util, whose library is 'xcb-util.0' insead of 'xcb-aux.o' Thanks for reporting-- this problem is known [1] and affects many ports. A 'proper' solution will come soon! Chris [1] http://www.mail-archive.com/cvs-all@freebsd.org/msg207773.html xfce4-session conked out after installing the new version (xcb-util-0.3.8,1 - 2012-01-15). xfce4-session can't be rebuilt, either. CCLD libxfsm-4.6.la grep: /usr/local/lib/libxcb-aux.la: No such file or directory sed: /usr/local/lib/libxcb-aux.la: No such file or directory libtool: link: `/usr/local/lib/libxcb-aux.la' is not a valid libtool archive gmake[2]: *** [libxfsm-4.6.la] Error 1 gmake[2]: Leaving directory `/usr/ports/x11-wm/xfce4-session/work/xfce4-session-4.8.2/libxfsm' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-wm/xfce4-session/work/xfce4-session-4.8.2' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/x11-wm/xfce4-session. *** Error code 1 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
pulseaudio upgrade (after xcb-util)
>>I don't know why it didn't happened on the first build, but for sysutils/gnome-settings-daemon now I'm getting an error caused by the removal of /usr/local/lib/libxcb-aux.la from xcb-util > >It seems that the removal of > libxcb-atom.so.1 > libxcb-event.so.1 > libxcb-aux.so.0 >is causing troubles (http://pastebin.com/7494x4sc) making the problem with pulseaudio looks like a joke. > I solved rebuilding the following ports I have installed: x11-toolkits/libwnck x11-wm/compizconfig-python x11/gnome-desktop x11-wm/compizconfig-backend-gconf x11-wm/metacity x11/yelp sysutils/gnome-system-monitor x11-toolkits/eel graphics/eog sysutils/gnome-settings-daemon x11-fm/nautilus www/epiphany x11/gnome-panel x11-toolkits/py-gnome-desktop sysutils/gnome-control-center x11-wm/compiz x11-wm/emerald x11-wm/compiz-plugins-main x11/gnome-applets x11-wm/compiz-plugins-extra so I guess that a rebuild of all the ports depending on xcb-util should be suggested. Barbara ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11/xcb-util downgraded?
On Sat, 17 Dec 2011 11:18:04 + Chris Rees wrote: > On 17 December 2011 10:47, Denise H. G. wrote: > > > > Hi all > > > > With the version bump of x11/xcb-util, some ports seems to be > > broken. However, after recompiling x11/startup-notification, and > > all the ports that depend on x11/startup-notification, everything > > will be OK. > > > > And x11/startup-notification needs to be set to depend on > > x11/xcb-util, whose library is 'xcb-util.0' insead of > > 'xcb-aux.o'startup-notification > > > > Hope this will work. > > Thanks for reporting-- this problem is known [1] and affects many > ports. A 'proper' solution will come soon! > > Chris Hmm, could this be why my attempt to upgrade claws-mail just now failed with: libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' gmake[4]: *** [claws-mail] Error 1 I checked and libxcb-aux.la indeed does not exist, although I did find an old *.so version under /usr/local/lib/compat/pkg. OK, I just rebuilt all of my *xcb* ports after making the suggested changes in x11/startup-notification and, sure enough, claws-mail now compiles successfully. Thanks! -- Conrad J. Sabatier conr...@cox.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11/xcb-util downgraded?
On 17 December 2011 10:47, Denise H. G. wrote: > > Hi all > > With the version bump of x11/xcb-util, some ports seems to be broken. > However, after recompiling x11/startup-notification, and all the > ports that depend on x11/startup-notification, everything will be OK. > > And x11/startup-notification needs to be set to depend on > x11/xcb-util, whose library is 'xcb-util.0' insead of 'xcb-aux.o' > > Hope this will work. Thanks for reporting-- this problem is known [1] and affects many ports. A 'proper' solution will come soon! Chris [1] http://www.mail-archive.com/cvs-all@freebsd.org/msg207773.html ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
x11/xcb-util downgraded?
Hi all With the version bump of x11/xcb-util, some ports seems to be broken. However, after recompiling x11/startup-notification, and all the ports that depend on x11/startup-notification, everything will be OK. And x11/startup-notification needs to be set to depend on x11/xcb-util, whose library is 'xcb-util.0' insead of 'xcb-aux.o' Hope this will work. Regards. -- When you are sure you're right, you have a moral duty to impose your will upon anyone who disagrees with you. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[Fwd: portupgrade failure xcb-util failure]
Ports at FreeBSD.org: I should have sent this also to you - it seems like it bounced from Thanks in advance for any help you can provide... John Stubblebine js...@jstub.com Original Message Subject:portupgrade failure xcb-util failure Date: Thu, 01 Oct 2009 11:58:26 -0700 From: John B Stubblebine Reply-To: John Stubblebine Organization: jstub Family To: FreeBSD xcb-util Maintainer CC: js...@jstub.com To: xcb-util Maintainer: The entire output of my session attempting to portupgrade xcb-util follows. It failed, and asked me to inform you. I have also attached both the listing of pkg_info and "ls /var/db/pkg" as well as the config.log file from this portupgrade failure. If you need any other information, please ask! Thank you. John Stubblebine js...@jstub.com Session output: * [r...@pcbsd]/usr/ports(26)# portupgrade -P -R -y xcb-util ---> Session started at: Thu, 01 Oct 2009 11:14:13 -0700 [Gathering depends for x11/xcb-util ... done] [Exclude up-to-date packages .. done] ---> Checking for the latest package of 'x11/xcb-util' ---> Fetching the package(s) for 'xcb-util-0.3.6' (x11/xcb-util) ---> Fetching xcb-util-0.3.6 ++ Will try the following sites in the order named: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-7-stable/ ---> Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgrade70jsMQjE/xcb-util-0.3.6.tbz' 'ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/xcb-util-0.3.6.tbz' fetch: ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/xcb-util-0.3.6.tbz: No address record ** The command returned a non-zero exit status: 1 ** Failed to fetch ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/xcb-util-0.3.6.tbz ---> Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgrade70jsMQjE/xcb-util-0.3.6.tgz' 'ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/xcb-util-0.3.6.tgz' fetch: ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/xcb-util-0.3.6.tgz: No address record ** The command returned a non-zero exit status: 1 ** Failed to fetch ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/xcb-util-0.3.6.tgz ** Failed to fetch xcb-util-0.3.6 ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) ! xcb-util-0.3.6(fetch error) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed ** Could not find the latest version (0.3.6) ---> Using the port instead of a package ---> Upgrade of x11/xcb-util started at: Thu, 01 Oct 2009 11:14:29 -0700 ---> Upgrading 'xcb-util-0.3.5' to 'xcb-util-0.3.6' (x11/xcb-util) ---> Build of x11/xcb-util started at: Thu, 01 Oct 2009 11:14:29 -0700 ---> Building '/usr/ports/x11/xcb-util' ===> Cleaning for gperf-3.0.3 ===> Cleaning for xcb-util-0.3.6 ===> Vulnerability check disabled, database not found ===> Extracting for xcb-util-0.3.6 => MD5 Checksum OK for xcb-util-0.3.6.tar.bz2. => SHA256 Checksum OK for xcb-util-0.3.6.tar.bz2. ===> Patching for xcb-util-0.3.6 ===> xcb-util-0.3.6 depends on file: /usr/local/bin/gperf - found ===> xcb-util-0.3.6 depends on executable: gmake - found ===> xcb-util-0.3.6 depends on file: /usr/local/libdata/pkgconfig/xau.pc - found ===> xcb-util-0.3.6 depends on file: /usr/local/libdata/pkgconfig/xdmcp.pc - found ===> xcb-util-0.3.6 de
Re: xcb-util 0.3.4 breaks awesome
On Fri, 8 May 2009, Dmitry Marakasov wrote: * Josh Rickmar (joshua_rick...@eumx.net) wrote: starup-notification was updated, and I've just committed update of awesome to 3.3-rc2. This should have no problems with new xcb-util. Thanks! Yeah, I saw the update to 3.3-rc2 and the new startup-notification version. Upgrading right now. I'll notify you again if I see any more problems (not necessarily with xcb-util). -- IRC nick: jrick Jabber: jr...@jabber.org http://identi.ca/jrick ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util 0.3.4 breaks awesome
* Josh Rickmar (joshua_rick...@eumx.net) wrote: starup-notification was updated, and I've just committed update of awesome to 3.3-rc2. This should have no problems with new xcb-util. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util 0.3.4 breaks awesome
On Fri, 2009-05-08 at 02:53 +0400, Dmitry Marakasov wrote: > * Robert Noland (rnol...@freebsd.org) wrote: > > > > That's quite complicated problem actually - xcb-util update has > > > broken awesome; we could update awesome to 3.3-rc1, but it requires > > > startup-notification 0.10 (which likely requires new xcb-util as > > > well). > > > > > > Thus we'll likely have to wait for s-n 0.10 and consider awesome > > > broken for now. Meanwhile, awesome users are recommended to not > > > upgrade from/downgrade to xcb-util 0.3.3. > > > > > > This is really our fault as there should've been more testing and > > > coordination with this update. > > > > Holding back X or it's sub-components is really not an option. The > > applications have to keep up. xcb-util doesn't fall under my umbrella, > > exactly, but I do update it in Xorg sweeps on occasion. Unless the > > damage is widespread progress must continue. Awesome needs to be > > patched, updated or marked BROKEN temporarily. > > Sure, I've just did exactly that - marked awesome BROKEN in presence of > newer xcb-util. The note above was for awesome users who, regardless of > ports progression and updates, will need a way to use them :) Agreed, providing a solution whatever it may be is always a good thing for users. robert. -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: xcb-util 0.3.4 breaks awesome
* Josh Rickmar (joshua_rick...@eumx.net) wrote: > OK. I've known about this break for quite some time now as there have > been many Linux users who had this same problem. In case of something > like this in the future, should I send a message to the maintainer > telling him/her about the potential break? Probably. Productive communication and collaboration haven't harmed anyone yet. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util 0.3.4 breaks awesome
* Robert Noland (rnol...@freebsd.org) wrote: > > That's quite complicated problem actually - xcb-util update has > > broken awesome; we could update awesome to 3.3-rc1, but it requires > > startup-notification 0.10 (which likely requires new xcb-util as > > well). > > > > Thus we'll likely have to wait for s-n 0.10 and consider awesome > > broken for now. Meanwhile, awesome users are recommended to not > > upgrade from/downgrade to xcb-util 0.3.3. > > > > This is really our fault as there should've been more testing and > > coordination with this update. > > Holding back X or it's sub-components is really not an option. The > applications have to keep up. xcb-util doesn't fall under my umbrella, > exactly, but I do update it in Xorg sweeps on occasion. Unless the > damage is widespread progress must continue. Awesome needs to be > patched, updated or marked BROKEN temporarily. Sure, I've just did exactly that - marked awesome BROKEN in presence of newer xcb-util. The note above was for awesome users who, regardless of ports progression and updates, will need a way to use them :) -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util 0.3.4 breaks awesome
On Thu, 2009-05-07 at 18:39 -0400, Josh Rickmar wrote: > On Fri, 8 May 2009, Dmitry Marakasov wrote: > > > * Josh Rickmar (joshua_rick...@eumx.net) wrote: > > > > That's quite complicated problem actually - xcb-util update has > > broken awesome; we could update awesome to 3.3-rc1, but it requires > > startup-notification 0.10 (which likely requires new xcb-util as > > well). > > > > Thus we'll likely have to wait for s-n 0.10 and consider awesome > > broken for now. Meanwhile, awesome users are recommended to not > > upgrade from/downgrade to xcb-util 0.3.3. > > > > This is really our fault as there should've been more testing and > > coordination with this update. > > > > > > OK. I've known about this break for quite some time now as there have > been many Linux users who had this same problem. In case of something > like this in the future, should I send a message to the maintainer > telling him/her about the potential break? Sending a HEADS UP message to the maintainer if you are aware of an issue would be a good courtesy and hopefully minimize any breakage. A short delay for a maintainer to address the issue is reasonable, but that is a slippery slope. I say give a reasonable amount of time for the breakage to be addressed (where the definition of reasonable is open to interpretation). If it isn't addressed, please move forward and commit. robert. > Also, to anyone who hasn't updated their xcb-util port yet, here's what > I did to prevent tools like portmaster from installing the newer > version: > > # touch /var/db/pkg/xcb-util-0.3.3/+IGNOREME > > Now in portmaster, I get the following message when using -a to update > all my ports: > > ===>>> Launching child to update xcb-util-0.3.3 to xcb-util-0.3.4 > > ===>>> xcb-util-0.3.3 has an +IGNOREME file > > ===>>> Update anyway? [n] -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: xcb-util 0.3.4 breaks awesome
On Fri, 8 May 2009, Dmitry Marakasov wrote: * Josh Rickmar (joshua_rick...@eumx.net) wrote: That's quite complicated problem actually - xcb-util update has broken awesome; we could update awesome to 3.3-rc1, but it requires startup-notification 0.10 (which likely requires new xcb-util as well). Thus we'll likely have to wait for s-n 0.10 and consider awesome broken for now. Meanwhile, awesome users are recommended to not upgrade from/downgrade to xcb-util 0.3.3. This is really our fault as there should've been more testing and coordination with this update. OK. I've known about this break for quite some time now as there have been many Linux users who had this same problem. In case of something like this in the future, should I send a message to the maintainer telling him/her about the potential break? Also, to anyone who hasn't updated their xcb-util port yet, here's what I did to prevent tools like portmaster from installing the newer version: # touch /var/db/pkg/xcb-util-0.3.3/+IGNOREME Now in portmaster, I get the following message when using -a to update all my ports: ===>>> Launching child to update xcb-util-0.3.3 to xcb-util-0.3.4 ===>>> xcb-util-0.3.3 has an +IGNOREME file ===>>> Update anyway? [n] -- IRC nick: jrick Jabber: jr...@jabber.org http://identi.ca/jrick ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util 0.3.4 breaks awesome
On Fri, 2009-05-08 at 02:07 +0400, Dmitry Marakasov wrote: > * Josh Rickmar (joshua_rick...@eumx.net) wrote: > > That's quite complicated problem actually - xcb-util update has > broken awesome; we could update awesome to 3.3-rc1, but it requires > startup-notification 0.10 (which likely requires new xcb-util as > well). > > Thus we'll likely have to wait for s-n 0.10 and consider awesome > broken for now. Meanwhile, awesome users are recommended to not > upgrade from/downgrade to xcb-util 0.3.3. > > This is really our fault as there should've been more testing and > coordination with this update. Holding back X or it's sub-components is really not an option. The applications have to keep up. xcb-util doesn't fall under my umbrella, exactly, but I do update it in Xorg sweeps on occasion. Unless the damage is widespread progress must continue. Awesome needs to be patched, updated or marked BROKEN temporarily. robert. -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: xcb-util 0.3.4 breaks awesome
* Josh Rickmar (joshua_rick...@eumx.net) wrote: That's quite complicated problem actually - xcb-util update has broken awesome; we could update awesome to 3.3-rc1, but it requires startup-notification 0.10 (which likely requires new xcb-util as well). Thus we'll likely have to wait for s-n 0.10 and consider awesome broken for now. Meanwhile, awesome users are recommended to not upgrade from/downgrade to xcb-util 0.3.3. This is really our fault as there should've been more testing and coordination with this update. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
xcb-util 0.3.4 breaks awesome
I've been following the discussions on awesome's IRC channel lately, and there have been a lot of problems with users not being able to use their modkey. It turned out that the problem was that a newer version of xcb-util (0.3.4) conflicts with the current released stable version of awesome. Now I see that xcb-util has been pushed to this version in ports. I'm not sure what the proper procedure is for ports which don't work together, but this is just a heads up that there will be problems for awesome users. According to the awesome devs, the solution is to either stay on xcb-util 0.3.3 or install a newer version of awesome (either from git, or use the release candidate for the next version). -- IRC nick: jrick Jabber: jr...@jabber.org http://identi.ca/jrick ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
