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: ghostscript8 port not building
On Tue, 5 May 2009, Josh Rickmar wrote: Hi all. I've been having this problem for some time, but have just gotten around to posting it to this list. Basically, I have ghostscript8-nox11-8.64 installed and want to upgrade it to 8.64_1. This is the error that I am getting: cc -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FONTCONFIG -O2 -fno-strict-aliasing -pipe -march=prescott -fPIC -DUPD_SIGNAL=0 -I. -I/usr/ports/print/ghostscript8/work/ghostscript-8.64/jasper/src/libjasper/ include -I/usr/local/include/libpng -I/usr/local/include -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -Wno-strict-aliasing -Wdeclaration-after-statem ent -fno-builtin -fno-common -DHAVE_STDINT_H -DGX_COLOR_INDEX_TYPE="unsigned long long" -O2 -fno-strict-aliasing -pipe -march=prescott -DUSE_LIBICONV_GNU -DGS_DEVS_SHARED -DGS_DEVS_SHARED_DIR=\"/usr/ local/lib/ghostscript/8.64\" -I./psi -I./obj/../soobj -I./obj/../soobj -I./base -o ./obj/../soobj/iconfig.o -c ./obj/../soobj/iconfig.c cc -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FONTCONFIG -O2 -fno-strict-aliasing -pipe -march=prescott -fPIC -DUPD_SIGNAL=0 -I. -I/usr/ports/print/ghostscript8/work/ghostscript-8.64/jasper/src/libjasper/ include -I/usr/local/include/libpng -I/usr/local/include -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -Wno-strict-aliasing -Wdeclaration-after-statem ent -fno-builtin -fno-common -DHAVE_STDINT_H -DGX_COLOR_INDEX_TYPE="unsigned long long" -O2 -fno-strict-aliasing -pipe -march=prescott -DUSE_LIBICONV_GNU -DGS_DEVS_SHARED -DGS_DEVS_SHARED_DIR=\"/usr/ local/lib/ghostscript/8.64\" -I./obj/../soobj -I./base -o ./obj/../soobj/gsromfs0.o -c ./base/gsromfs0.c ./obj/../soobj/echogs -w ./obj/../soobj/ldt.tr -n - cc -L/usr/local/lib -L/usr/local/lib -shared -Wl,-soname=libgs.so.8 -o ./bin/../sobin/libgs.so.8.64 ./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -n -s ./obj/../soobj/gsromfs0.o ./obj/../soobj/gs.o -s cat ./obj/../soobj/ld.tr >>./obj/../soobj/ldt.tr ./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -s - -lm -liconv -lstdc++ -L/usr/local/lib -lfontconfig -Wl,-export-dynamic -lpthread -lm if [ x != x ]; then LD_RUN_PATH=; export LD_RUN_PATH; fi; \ XCFLAGS= XINCLUDE= XLDFLAGS= XLIBDIRS= XLIBS= \ FEATURE_DEVS= DEVICE_DEVS= DEVICE_DEVS1= DEVICE_DEVS2= DEVICE_DEVS3= \ DEVICE_DEVS4= DEVICE_DEVS5= DEVICE_DEVS6= DEVICE_DEVS7= DEVICE_DEVS8= \ DEVICE_DEVS9= DEVICE_DEVS10= DEVICE_DEVS11= DEVICE_DEVS12= \ DEVICE_DEVS13= DEVICE_DEVS14= DEVICE_DEVS15= DEVICE_DEVS16= \ DEVICE_DEVS17= DEVICE_DEVS18= DEVICE_DEVS19= DEVICE_DEVS20= \ DEVICE_DEVS_EXTRA= \ /bin/sh <./obj/../soobj/ldt.tr ./obj/../soobj/gdevl256.o(.text+0x73a): In function `gs_shared_init': : multiple definition of `gs_shared_init' ./obj/../soobj/gdevxalt.o(.text+0x1759): first defined here /usr/bin/ld: Warning: size of symbol `gs_shared_init' changed from 150 in ./obj/../soobj/gdevxalt.o to 38 in ./obj/../soobj/gdevl256.o ./obj/../soobj/gdevvglb.o(.text+0x995): In function `gs_shared_init': : multiple definition of `gs_shared_init' ./obj/../soobj/gdevxalt.o(.text+0x1759): first defined here gmake[1]: *** [bin/../sobin/libgs.so.8.64] Error 1 gmake[1]: Leaving directory `/usr/ports/print/ghostscript8/work/ghostscript-8.64' gmake: *** [so] Error 2 *** Error code 1 Any help? I am on 7.2-RELEASE now, but I was also getting this error while still on 7.1. Well, I finally got frustrated with this problem and blew-away all of my ports, to see if I had messed up something by accident. I also removed /var/db/ports/ghostscript8/options to make sure that that was not affecting it. Here is the my new error: cc -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FONTCONFIG -O2 -fno-strict-aliasing -pipe -march =prescott -fPIC -DUPD_SIGNAL=0 -I. -I/usr/ports/print/ghostscript8/work/ghostscript-8.64/ jasper/src/libjasper/include -I/usr/local/include/libpng -I/usr/local/include -Wall -Wst rict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -Wno- strict-aliasing -Wdeclaration-after-statement -fno-builtin -fno-common -DHAVE_STDINT_H -D GX_COLOR_INDEX_TYPE="unsigned long long" -O2 -fno-strict-aliasing -pipe -march=prescott - DUSE_LIBICONV_GNU -DGS_DEVS_SHARED -DGS_DEVS_SHARED_DIR=\"/usr/local/lib/ghostscript/8.64 \" -I./base/rinkj -o ./obj/../soobj/rinkj-screen-eb.o -c ./base/rinkj/rinkj-screen-eb.c ./base/rinkj/rinkj-screen-eb.c: In function 'rinkj_screen_eb_write': ./base/rinkj/rinkj-screen-eb.c:176: warning: assignment discards qualifiers from pointer target type ./base/rinkj/rinkj-screen-eb.c:184: warning: passing argument 2 of 'even_better_line' fro m incompatible pointer type ./base/rinkj/rinkj-screen-eb.c:184: warning: passing argument 3 of 'even_better_line' fro m incompatible pointer type ./
Re: ghostscript8 port not building
On Fri, 15 May 2009, Josh Rickmar wrote: Well, I finally got frustrated with this problem and blew-away all of my ports, to see if I had messed up something by accident. I also removed /var/db/ports/ghostscript8/options to make sure that that was not affecting it. Here is the my new error: [...] # uname -a FreeBSD FGD135.localdomain 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Tue May 5 01:52:24 EDT 2009 jos...@fgd135.localdomain:/usr/obj/usr/src/sys/CUSTOM i386 I have also CC'd the maintainer since I forgot to do that in my first email. It seems that the second build problem I was having is fixed now. Probably should have updated my ports tree before updating... I don't get the first error anymore either, so everything seems to be working fine. -- 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"
screen and tmux should be listed under the same category
GNU screen is listed under sysutils, while tmux is listed under misc. Shouldn't the two at least be in the same category, since they both do the exact same thing? (tmux is even designed to be a BSD-licensed replacement for screen.) -- 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"
x11/hs-x11-ghc can't find proper version of haddock
I am trying to install xmonad, but the hs-x11-ghc dependency is not building. It is looking for a haddock version >=0.6, but can not find what the version actually is. ===> Building for hs-x11-ghc-1.4.5_1 cd /usr/ports/x11/hs-x11-ghc/work/X11-1.4.5 && /usr/local/bin/runghc Set up.hs build && /usr/local/bin/runghc Setup.hs --gen-script register Preprocessing library X11-1.4.5... Building X11-1.4.5... /usr/bin/ar: creating dist/build/libHSX11-1.4.5.a Writing registration script: register.sh for X11-1.4.5... cd /usr/ports/x11/hs-x11-ghc/work/X11-1.4.5 && /usr/local/bin/runghc Set up.hs haddock Setup.hs: haddock version >=0.6 is required but the version of /usr/loca l/bin/haddock could not be determined. *** Error code 1 Stop in /usr/ports/x11/hs-x11-ghc. *** Error code 1 Stop in /usr/ports/x11/hs-x11-ghc. -- 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: x11/hs-x11-ghc can't find proper version of haddock
On Tue, 19 May 2009, Gabor PALI wrote: Hello Josh, On Tue, May 19, 2009 at 11:32 PM, Josh Rickmar wrote: I am trying to install xmonad, but the hs-x11-ghc dependency is not building. It is looking for a haddock version >=0.6, but can not find what the version actually is. I am on it :) Hopefully, I can tell you what the problem is soon. Cheers, :g Well, I'm not sure what was happening, but after a 'make clean', everything seems to be working again. Probably should have checked this before hand... -- 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"
emulators/open-vm-tools fails to build
The latest update of open-vm-tools is not compiling for me. Here's the error: mv -f .deps/pointer.Tpo .deps/pointer.Po c++ -DPACKAGE_NAME=\"open-vm-tools\" -DPACKAGE_TARNAME=\"open-vm-tools\" -DPACKAGE_VERSION=\"2009.05.22\" -DPACKAGE_STRING=\"open-vm-tools\ 2009.05.22\" -DPACKAGE_BUGREPORT=\"open-vm-tools-de...@lists.sourcefor ge.net\" -DPACKAGE=\"open-vm-tools\" -DVERSION=\"2009.05.22\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAV E_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H =1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_DLOPEN=1 -DNO_PROCP S=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_ SYS_TYPES_H=1 -DHAVE_SYS_USER_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DTIME_W ITH_SYS_TIME=1 -I. -I/usr/ports/emulators/open-vm-tools/work/open-vm-tools-2009.05.22-167859/lib/inclu de -I/usr/ports/emulators/open-vm-tools/work/open-vm-tools-2009.05.22-167859/lib/include -I/usr/local/inc lude -DUSING_AUTOCONF=1 -DOPEN_VM_TOOLS -I/usr/local/include -I/usr/local/include -DUSE_ICU -DHAVE_ICU_3 8 -DVMX86_TOOLS -DNO_CORE_ICU -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/includ e -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/inc lude -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr /local/include/freetype2 -DGTK2-I../include -I../lib/dndGuest -DRESOLUTION_X11 -I../services/plugi ns/vix -O2 -fno-strict-aliasing -pipe -march=prescott -MT vmware-user.o -MD -MP -MF .deps/vmware-user.Tpo -c -o vmware-user.o vmware-user.cpp vmware-user.cpp: In function 'Bool VMwareUserRpcInSetOptionCB(const char**, size_t*, const char*, const c har*, size_t, void*)': vmware-user.cpp:551: warning: deprecated conversion from string constant to 'char*' vmware-user.cpp:557: warning: deprecated conversion from string constant to 'char*' vmware-user.cpp:560: warning: deprecated conversion from string constant to 'char*' vmware-user.cpp:577: warning: deprecated conversion from string constant to 'char*' vmware-user.cpp:594: warning: deprecated conversion from string constant to 'char*' vmware-user.cpp:598: warning: deprecated conversion from string constant to 'char*' vmware-user.cpp:603: warning: deprecated conversion from string constant to 'char*' mv -f .deps/vmware-user.Tpo .deps/vmware-user.Po make: don't know how to make ../lib/dndGuest/libDndGuest.la. Stop *** Error code 1 Stop in /usr/ports/emulators/open-vm-tools/work/open-vm-tools-2009.05.22-167859. *** Error code 1 Stop in /usr/ports/emulators/open-vm-tools. -- 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: AW: emulators/open-vm-tools fails to build
On Tue, 9 Jun 2009, Josh Rickmar wrote: On Wed, 10 Jun 2009, Blapp, Martin wrote: Hi, You forgot to mention some things: OS-Version and Level ? Port (NO-X11 or normal version) ? Ah, right. Sorry about that. % uname -a FreeBSD FGD135.localdomain 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Tue May 5 01:52:24 EDT 2009 jos...@fgd135.localdomain:/usr/obj/usr/src/sys/CUSTOM i386 I'm trying to build the normal port, not the no-x11 version. Forgot to CC to list. -- 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: AW: AW: emulators/open-vm-tools fails to build
On Wed, 10 Jun 2009, Blapp, Martin wrote: Hi, Strange. I sucessfully built the port on 7.2. Do you have any special /etc/make.conf settings ? Special gcc flags ? The only setting in my /etc/make.conf is that I'm building to a prescott processor. I'll try building the -nox11 version to see if that solves the problems, since I don't use any of the GUI tools. -- 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: AW: AW: emulators/open-vm-tools fails to build
On Tue, 9 Jun 2009, Josh Rickmar wrote: On Wed, 10 Jun 2009, Blapp, Martin wrote: Hi, Strange. I sucessfully built the port on 7.2. Do you have any special /etc/make.conf settings ? Special gcc flags ? The only setting in my /etc/make.conf is that I'm building to a prescott processor. I'll try building the -nox11 version to see if that solves the problems, since I don't use any of the GUI tools. -nox11 builds and installs fine. -- 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"
KDEmod with Ports
Hi. Last weekend I switched my desktop computer from Arch Linux to FreeBSD. On Arch, I used KDEmod [1] (a modular and splitted KDE) in place of Arch's vanilla KDE. I am now wondering if it is possible to port KDEmod to FreeBSD with Ports. KDEmod is built using a different build system than Arch's standard PKGBUILD and makepkg tools. Instead of building one package for each PKGBUILD, a SPLITBUILD is used to create multiple packages. This way, instead of having just kdetoys (like in /usr/ports/x11-clocks/kdetoys3), it is possible to build seperate packages for amor, kteatime, ktux, kweather... all part of kdetoys, with the same SPLITBUILD or PKGBUILD. (Here's a better explanation of how the build system works [2]. This is for KDE3, the KDE4 version is (slightly?) different, but the concept is similar.) I have started this thread [3] on the KDEmod forums asking if it is still possible to port KDEmod to other distros or systems with the new buildsystem. Funkyou (the original developer of KDEmod) replied saying that if you can port the kdetoys example, it should be relatively easy to port the rest. I am willing to write Ports for this (if it is possible), however, I have only basic knowledge of writting PKGBUILDs and no knowledge in making Ports. Any help would be appreciated. Links: [1] http://www.kdemod.ath.cx/ [2] http://www.kdemod.ath.cx/bbs/viewtopic.php?id=592 [3] http://www.kdemod.ath.cx/bbs/viewtopic.php?id=791 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
open-vm-tools port
It seems that the emulators/open-vm-tools is broken. After deinstalling it and installing it again, whenever I run '/usr/local/etc/rc.d/vmware-guestd start' or reboot the virtual machine, then there is an error about a missing /usr/local/sbin/vmware-checkvm. I do have a vmware-checkvm, but it is in /usr/local/bin/, so a 'ln -s /usr/local/bin/vmware-checkvm /usr/local/sbin/vmware-checkvm' fixed the problem. Also, the mouse is only able to seamlessly integrate with the host machine when the vmmouse driver is used. When I had emulators/vmware-tools6 installed, it would work even with the generic mouse driver (which I would prefer to use). Also, there seems to be some features of vmware-tools/open-vm-tools missing. If I add a shared folder in VMware, then I am not able to access it through /mnt/hgfs even after I run vmware-hgfsclient as root. I am also not able to drag and drop files between the host and guest machines, even though I am able to pass the mouse through each seamlessly. (But I had these same problems when using emulators/vmware-tools6...) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Lilypond does not build
Ever since the update to 2.11.55 on August 7th, I have not been able to update print/lilypond. Here is the build failure: ===> Cleaning for lilypond-2.11.55 ===> Found saved configuration for lilypond-2.11.52 ===> Extracting for lilypond-2.11.55 => MD5 Checksum OK for lilypond-2.11.55.tar.gz. => SHA256 Checksum OK for lilypond-2.11.55.tar.gz. => MD5 Checksum OK for lilypond-2.11.55-1.freebsd-x86.sh. => SHA256 Checksum OK for lilypond-2.11.55-1.freebsd-x86.sh. ( /usr/bin/tail -c+4597 /usr/ports/distfiles/lilypond-2.11.55-1.freebsd -x86.sh > /usr/ports/print/lilypond/work/lilypond.tmp.tar.bz2 && /usr/bin/tar -xjf /usr/ports/print/lilypond/work/lilypond.tmp.tar.bz2 -C /usr/ports/print/lil ypond/work && /bin/mkdir -p /usr/ports/print/lilypond/work/lilypond-2.11.55/mf/ out && /bin/cp /usr/ports/print/lilypond/work/usr/share/lilypond/current/fonts/ otf/*.otf /usr/ports/print/lilypond/work/lilypond-2.11.55/mf/out ) ===> Patching for lilypond-2.11.55 ===> Applying FreeBSD patches for lilypond-2.11.55 /usr/bin/sed -i.bak -e 's|makeinfo|/usr/local/bin/makeinfo|' /usr/ports/print/l ilypond/work/lilypond-2.11.55/configure ===> lilypond-2.11.55 depends on executable: latex - found ===> lilypond-2.11.55 depends on executable: mftrace - found ===> lilypond-2.11.55 depends on executable: rarian-sk-config - found ===> lilypond-2.11.55 depends on executable: texi2pdf - found ===> lilypond-2.11.55 depends on file: /usr/local/bin/python2.5 - found ===> lilypond-2.11.55 depends on executable: gmake - found ===> lilypond-2.11.55 depends on executable: bison - found ===> lilypond-2.11.55 depends on file: /usr/local/bin/autoconf-2.61 - found ===> lilypond-2.11.55 depends on executable: pkg-config - found rm -f ./out/includable-lexer.dep; DEPENDENCIES_OUTPUT="./out/includable-lexer.de p ./out/includable-lexer.o" c++ -c -O2 -fno-strict-aliasing -pipe -Woverloaded-v irtual -DHAVE_CONFIG_H -DNDEBUG -I./include -I./out -I../flower/include -I../fl ower/./out -I../flower/include -O2 -fno-strict-aliasing -pipe -O2 -finline-fun ctions -g -pipe -I/usr/local/include -I/usr/local/include -D_THREAD_SAFE -pthrea d -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include/pan go-1.0 -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include/ glib-2.0 -I/usr/local/lib/glib-2.0/include -Wno-pmf-conversions -W -Wall -Wco nversion -o out/includable-lexer.o includable-lexer.cc includable-lexer.cc: In constructor 'Includable_lexer::Includable_lexer()': includable-lexer.cc:42: error: 'yy_current_buffer' was not declared in this scop e includable-lexer.cc: In member function 'virtual void Includable_lexer::new_inpu t(std::string, Sources*)': includable-lexer.cc:63: error: 'yy_current_buffer' was not declared in this scop e includable-lexer.cc: In member function 'void Includable_lexer::new_input(std::s tring, std::string, Sources*)': includable-lexer.cc:86: error: 'yy_current_buffer' was not declared in this scop e includable-lexer.cc: In member function 'bool Includable_lexer::close_input()': includable-lexer.cc:106: error: 'yy_current_buffer' was not declared in this sco pe gmake[1]: *** [out/includable-lexer.o] Error 1 gmake[1]: Leaving directory `/usr/ports/print/lilypond/work/lilypond-2.11.55/lil y' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/print/lilypond. *** Error code 1 Stop in /usr/ports/print/lilypond. ===>>> make failed for print/lilypond ===>>> Aborting update ===>>> Update for lilypond-2.11.52_1 failed ===>>> Aborting update ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Concern about using pkg_delete -r
I'm hoping that this list covers port tools as well as the usual discussions about the actual ports. If not, please CC this to the proper list. I want to use pkg_delete to remove an installed port, but also want to remove its orphaned dependencies along with it. After looking at the pkg_delete(1) man page, the -r flag seems to be the option to use for this job. My concern, though, is about the wording: > In addition to specified packages, delete all > packages that depend on those packages as well. Does this mean that if I pkg_delete -r pkgA, than pkgB (a dependency) will be removed with it, even though it is dependency of pkgC? Or is pkg_delete (or pkg_deinstall) smart enough to understand this dependency and keep pkgB installed? If in this scenario pkgB would be deleted, should an extra warning be added to the man page so that users know that using this flag could potentially break their other ports? -- To send me a personal email, please place [personal] in the Subject line. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Concern about using pkg_delete -r
On Thu, October 23, 2008 10:05 pm, Stephen Montgomery-Smith wrote: > Josh Rickmar wrote: > >> I'm hoping that this list covers port tools as well as the usual >> discussions about the actual ports. If not, please CC this to the >> proper list. >> >> I want to use pkg_delete to remove an installed port, but also want to >> remove its orphaned dependencies along with it. After looking at the >> pkg_delete(1) man page, the -r flag seems to be the option to use for >> this job. My concern, though, is about the wording: >> >>> In addition to specified packages, delete all >>> packages that depend on those packages as well. >> >> Does this mean that if I pkg_delete -r pkgA, than pkgB (a dependency) >> will be removed with it, even though it is dependency of pkgC? Or is >> pkg_delete (or pkg_deinstall) smart enough to understand this >> dependency and keep pkgB installed? >> >> If in this scenario pkgB would be deleted, should an extra warning be >> added to the man page so that users know that using this flag could >> potentially break their other ports? > > I think you have the dependency relationship the wrong way around. > > > If you do "pkg_delete -r pkgA", and pkgA is a dependency of pkgB (not > the other way around as you have it), then pkgB will be deleted. > Ah, my bad. Yeah, after re-reading the wording it seems that is the case. What about for pkg_deinstall (part of portupgrade)? According to its man page, it has two options, --recursive (-r) and --upward-recursive (-R). Maybe it's just a little bit late, but what /exactly/ is the difference? It sounds like the --upward-recursive option would be better called --downward-recursive, since it will remove the ports/packages "below" it. So, if that is the case, would pkg_deinstall -R pkgA remove pkgB or not? -- To send me a personal email, please place [personal] in the Subject line. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Concern about using pkg_delete -r
On Thu, October 23, 2008 10:30 pm, Robert Noland wrote: > On Thu, 2008-10-23 at 22:25 -0400, Josh Rickmar wrote: > >> On Thu, October 23, 2008 10:05 pm, Stephen Montgomery-Smith wrote: >> >>> Josh Rickmar wrote: >>> >>> >>>> I'm hoping that this list covers port tools as well as the usual >>>> discussions about the actual ports. If not, please CC this to the >>>> proper list. >>>> >>>> I want to use pkg_delete to remove an installed port, but also want >>>> to remove its orphaned dependencies along with it. After looking at >>>> the pkg_delete(1) man page, the -r flag seems to be the option to >>>> use for this job. My concern, though, is about the wording: >>>> >>>>> In addition to specified packages, delete all >>>>> packages that depend on those packages as well. >>>> >>>> Does this mean that if I pkg_delete -r pkgA, than pkgB (a >>>> dependency) will be removed with it, even though it is dependency of >>>> pkgC? Or is pkg_delete (or pkg_deinstall) smart enough to >>>> understand this dependency and keep pkgB installed? >>>> >>>> If in this scenario pkgB would be deleted, should an extra warning >>>> be added to the man page so that users know that using this flag >>>> could potentially break their other ports? >>> >>> I think you have the dependency relationship the wrong way around. >>> >>> >>> >>> If you do "pkg_delete -r pkgA", and pkgA is a dependency of pkgB (not >>> the other way around as you have it), then pkgB will be deleted. >>> >> >> Ah, my bad. Yeah, after re-reading the wording it seems that is the >> case. >> >> What about for pkg_deinstall (part of portupgrade)? According to its >> man page, it has two options, --recursive (-r) and --upward-recursive >> (-R). >> Maybe it's just a little bit late, but what /exactly/ is the difference? >> It sounds like the --upward-recursive option would be better called >> --downward-recursive, since it will remove the ports/packages "below" >> it. > > Semantically, it is an inverted tree... i.e. the root is at the top. > > > robert. OK, I guess that makes sense. > >> So, if that is the case, would pkg_deinstall -R pkgA remove pkgB or >> not? >> > Well, I tested using pkg_deinstall -rRn, and if I were to remove the -n flag, it would be uninstalling ports all the way down to gettext. Not good. So, it would be removing 'pkgB' with this option. Any way to prevent this? -- To send me a personal email, please place [personal] in the Subject line. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: emulators/open-vm-tools
This port is not building for me right now. Here's the error: cc -DPACKAGE_NAME=\"open-vm-tools\" -DPACKAGE_TARNAME=\"open-vm-tools\" -DPACKA GE_VERSION=\"2008.07.01-102166\" "-DPACKAGE_STRING=\"open-vm-tools 2008.07.01-10 2166\"" -DPACKAGE_BUGREPORT=\"open-vm-tools-de...@lists.sourceforge.net\" -DPACK AGE=\"open-vm-tools\" -DVERSION=\"2008.07.01-102166\" -DSTDC_HEADERS=1 -DHAVE_SY S_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMOR Y_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_DLOPEN=1 -DNO_PROCPS=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDIN T_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TYPES_H =1 -DHAVE_SYS_USER_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STRUCT_STAT_ST_R DEV=1 -DTIME_WITH_SYS_TIME=1 -I. -I/usr/local/include -DUSING_AUTOCONF=1 -I/usr/ local/include -I/usr/local/include -DUSE_ICU -DHAVE_ICU_38 -DVMX86_TOOLS -DNO_CO RE_ICU -I/usr/ports/emulators/open-vm-tools/work/open-vm-tools-2008.07.01-102166 /lib/include -O2 -fno-strict-aliasing -pipe -march=prescott -Wall -Werror -Wno-p ointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas -Wno-uni nitialized -MT hostname.lo -MD -MP -MF .deps/hostname.Tpo -c ../hostname.c -fPI C -DPIC -o .libs/hostname.o cc1: warnings being treated as errors ../hostname.c: In function 'Hostinfo_HostName': ../hostname.c:248: warning: implicit declaration of function 'Unicode_Format' ../hostname.c:248: warning: return makes pointer from integer without a cast *** Error code 1 Stop in /usr/ports/emulators/open-vm-tools/work/open-vm-tools-2008.07.01-102166/ lib/misc/shared. *** Error code 1 Stop in /usr/ports/emulators/open-vm-tools/work/open-vm-tools-2008.07.01-102166/ lib/misc. *** Error code 1 Stop in /usr/ports/emulators/open-vm-tools/work/open-vm-tools-2008.07.01-102166/ lib. *** Error code 1 Stop in /usr/ports/emulators/open-vm-tools/work/open-vm-tools-2008.07.01-102166. *** Error code 1 Stop in /usr/ports/emulators/open-vm-tools. Also, it a new version was released on Janurary 21, 2009, so an update for the port would be greatly appreciated. :) -- To send me a personal email, please place [personal] in the Subject line. ___ 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: FreeBSD Port: emulators/open-vm-tools
On Wed, February 4, 2009 3:50 pm, Josh Rickmar wrote: > This port is not building for me right now. Here's the error: > > > cc -DPACKAGE_NAME=\"open-vm-tools\" -DPACKAGE_TARNAME=\"open-vm-tools\" > -DPACKA > GE_VERSION=\"2008.07.01-102166\" "-DPACKAGE_STRING=\"open-vm-tools > 2008.07.01-10 > 2166\"" -DPACKAGE_BUGREPORT=\"open-vm-tools-de...@lists.sourceforge.net\" > -DPACK > AGE=\"open-vm-tools\" -DVERSION=\"2008.07.01-102166\" -DSTDC_HEADERS=1 > -DHAVE_SY > S_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_MEMOR > Y_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 > -DHAVE_UNISTD_H=1 > -DHAVE_DLFCN_H=1 -DHAVE_DLOPEN=1 -DNO_PROCPS=1 -DHAVE_INTTYPES_H=1 > -DHAVE_STDIN > T_H=1 -DHAVE_STDLIB_H=1 -DHAVE_WCHAR_H=1 -DHAVE_SYS_PARAM_H=1 > -DHAVE_SYS_TYPES_H > =1 -DHAVE_SYS_USER_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 > -DHAVE_STRUCT_STAT_ST_R > DEV=1 -DTIME_WITH_SYS_TIME=1 -I. -I/usr/local/include -DUSING_AUTOCONF=1 > -I/usr/ > local/include -I/usr/local/include -DUSE_ICU -DHAVE_ICU_38 -DVMX86_TOOLS > -DNO_CO > RE_ICU > -I/usr/ports/emulators/open-vm-tools/work/open-vm-tools-2008.07.01-102166 > /lib/include -O2 -fno-strict-aliasing -pipe -march=prescott -Wall -Werror > -Wno-p > ointer-sign -Wno-unused-value -fno-strict-aliasing -Wno-unknown-pragmas > -Wno-uni > nitialized -MT hostname.lo -MD -MP -MF .deps/hostname.Tpo -c ../hostname.c > -fPI > C -DPIC -o .libs/hostname.o > cc1: warnings being treated as errors > ../hostname.c: In function 'Hostinfo_HostName': > ../hostname.c:248: warning: implicit declaration of function > 'Unicode_Format' > ../hostname.c:248: warning: return makes pointer from integer without a > cast *** Error code 1 > > > Stop in > /usr/ports/emulators/open-vm-tools/work/open-vm-tools-2008.07.01-102166/ > lib/misc/shared. *** Error code 1 > > > Stop in > /usr/ports/emulators/open-vm-tools/work/open-vm-tools-2008.07.01-102166/ > lib/misc. *** Error code 1 > > > Stop in > /usr/ports/emulators/open-vm-tools/work/open-vm-tools-2008.07.01-102166/ > lib. *** Error code 1 > > > Stop in > /usr/ports/emulators/open-vm-tools/work/open-vm-tools-2008.07.01-102166. > *** Error code 1 > > > Stop in /usr/ports/emulators/open-vm-tools. > > > > Also, it a new version was released on Janurary 21, 2009, so an update > for the port would be greatly appreciated. :) > > I don't mean to sound pushy, but I still can't build this. I tried manually installing the latest version, and get (different) problems with that as well. And since I can't find a package of this... -- To send me a personal email, please place [personal] in the Subject line. ___ 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: FreeBSD Port: emulators/open-vm-tools
On Mon, February 9, 2009 2:08 pm, Sean McAfee wrote: > Josh Rickmar wrote: > >> On Wed, February 4, 2009 3:50 pm, Josh Rickmar wrote: >> >> >> I don't mean to sound pushy, but I still can't build this. I tried >> manually installing the latest version, and get (different) problems >> with that as well. And since I can't find a package of this... > It's very hard for people to help you if they don't know what > architecture or version of FreeBSD you're running. > > I'll throw you a bone here: it builds just fine for me in 7.1p2 amd64 w/ > GENERIC. > Ah, ok I understand. I'm using 7.1-RELEASE-p2 as well, but on i386. -- To send me a personal email, please place [personal] in the Subject line. ___ 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: FreeBSD Port: emulators/open-vm-tools
On Mon, February 9, 2009 2:08 pm, Sean McAfee wrote: > Josh Rickmar wrote: > >> On Wed, February 4, 2009 3:50 pm, Josh Rickmar wrote: >> >> >> I don't mean to sound pushy, but I still can't build this. I tried >> manually installing the latest version, and get (different) problems >> with that as well. And since I can't find a package of this... > It's very hard for people to help you if they don't know what > architecture or version of FreeBSD you're running. > > I'll throw you a bone here: it builds just fine for me in 7.1p2 amd64 w/ > GENERIC. > Ah, ok I understand. I'm using 7.1-RELEASE-p2 as well, but on i386. -- To send me a personal email, please place [personal] in the Subject line. ___ 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"
Configure fails for open-vm-tools
I'm getting this error when trying to build the latest open-vm-tools ports: configure: error: uriparser library not found or is too old. Please configure without Unity (using --disable-unity) or install the liburiparser devel package. I still get the same error after installing the uriparser port. -- To send me a personal email, please place [personal] in the Subject line. ___ 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"
net-im/finch crashing on startup
Hi, First, some system details: [18:41][jos...@fgd135] % uname -a FreeBSD FGD135.localdomain 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #0: Sun Mar 22 12:35:36 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 I have just built the net-im/finch port (and libpurple) using the following configure options: BONJOUR=on "Enable mDNS support" DBUS=on "Enable DBUS bindings" GNUTLS=on "GNUTLS encryption support" NSS=off "Mozilla NSS encryption support" SASL=off "Cyrus SASL support (for jabberd)" PERL=off "Perl scripting" TCLTK=off "Tcl/Tk scripting" SAMETIME=off "The Lotus Sametime chat protocol" SILC=off "The Secure Internet Live Conferencing protocol" GG=off "The Gadu-Gadu chat protocol" IRC=off "The Internet Relay Chat protocol" JABBER=on "The Jabber/XMPP/Google Talk protocol" MSN=off "The MSN Messenger protocol" MYSPACE=off "The MySpaceIM protocol" NOVELL=off "The Novell GroupWise chat protocol" OSCAR=on "The AIM/ICQ/Oscar protocol" QQ=off "The Tercent QQ chat protocol" SIMPLE=off "The SIMPLE chat protocol" YAHOO=off "The Yahoo! Messenger protocol" ZEPHYR=off "The Zephyr chat protocol" As soon as I try and start finch, it loads for a brief second, but then I get a segmentation fault. My terminal is also messed up afterwards. Can anybody help? I'm not quite sure what to do to fix this, or even figure out what is going wrong. Also, does anyone has any other recommendations as to a console-based IM client supporting at least XMPP if I can't get finch working? ___ 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: net-im/finch crashing on startup
On Sat, 25 Apr 2009, Joe Marcus Clarke wrote: I can't reproduce on -STABLE. Finch seems to be working just fine for me. See http://www.freebsd.org/gnome/doc/bugging.html on how to rebuild finch and libpurple with debugging symbols. When it crashes again, get a gdb back trace. Joe Well, it seems to be a non-issue for me now, since I found a replacement for finch instead (I'm now using mcabber). Thanks for the help, though. Would you still like me to rebuild finch with the debugging symbols to see what was wrong and how is can be fixed, or am I the only one experiencing this problem on 7.1-RELEASE? ___ 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"
www/firefox-devel?
I just noticed that www/firefox-devel was still in the ports tree. Looking at the Makefile, this port will install 3.0 alpha 2. Shouldn't this port be deleted? -- To send me a personal email, please place [personal] in the Subject line. ___ 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"
ghostscript8 port not building
Hi all. I've been having this problem for some time, but have just gotten around to posting it to this list. Basically, I have ghostscript8-nox11-8.64 installed and want to upgrade it to 8.64_1. This is the error that I am getting: cc -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FONTCONFIG -O2 -fno-strict-aliasing -pipe -march=prescott -fPIC -DUPD_SIGNAL=0 -I. -I/usr/ports/print/ghostscript8/work/ghostscript-8.64/jasper/src/libjasper/ include -I/usr/local/include/libpng -I/usr/local/include -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -Wno-strict-aliasing -Wdeclaration-after-statem ent -fno-builtin -fno-common -DHAVE_STDINT_H -DGX_COLOR_INDEX_TYPE="unsigned long long" -O2 -fno-strict-aliasing -pipe -march=prescott -DUSE_LIBICONV_GNU -DGS_DEVS_SHARED -DGS_DEVS_SHARED_DIR=\"/usr/ local/lib/ghostscript/8.64\" -I./psi -I./obj/../soobj -I./obj/../soobj -I./base -o ./obj/../soobj/iconfig.o -c ./obj/../soobj/iconfig.c cc -DHAVE_MKSTEMP -DHAVE_HYPOT -DHAVE_FONTCONFIG -O2 -fno-strict-aliasing -pipe -march=prescott -fPIC -DUPD_SIGNAL=0 -I. -I/usr/ports/print/ghostscript8/work/ghostscript-8.64/jasper/src/libjasper/ include -I/usr/local/include/libpng -I/usr/local/include -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -Wno-strict-aliasing -Wdeclaration-after-statem ent -fno-builtin -fno-common -DHAVE_STDINT_H -DGX_COLOR_INDEX_TYPE="unsigned long long" -O2 -fno-strict-aliasing -pipe -march=prescott -DUSE_LIBICONV_GNU -DGS_DEVS_SHARED -DGS_DEVS_SHARED_DIR=\"/usr/ local/lib/ghostscript/8.64\" -I./obj/../soobj -I./base -o ./obj/../soobj/gsromfs0.o -c ./base/gsromfs0.c ./obj/../soobj/echogs -w ./obj/../soobj/ldt.tr -n - cc -L/usr/local/lib -L/usr/local/lib -shared -Wl,-soname=libgs.so.8 -o ./bin/../sobin/libgs.so.8.64 ./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -n -s ./obj/../soobj/gsromfs0.o ./obj/../soobj/gs.o -s cat ./obj/../soobj/ld.tr >>./obj/../soobj/ldt.tr ./obj/../soobj/echogs -a ./obj/../soobj/ldt.tr -s - -lm -liconv -lstdc++ -L/usr/local/lib -lfontconfig -Wl,-export-dynamic -lpthread -lm if [ x != x ]; then LD_RUN_PATH=; export LD_RUN_PATH; fi; \ XCFLAGS= XINCLUDE= XLDFLAGS= XLIBDIRS= XLIBS= \ FEATURE_DEVS= DEVICE_DEVS= DEVICE_DEVS1= DEVICE_DEVS2= DEVICE_DEVS3= \ DEVICE_DEVS4= DEVICE_DEVS5= DEVICE_DEVS6= DEVICE_DEVS7= DEVICE_DEVS8= \ DEVICE_DEVS9= DEVICE_DEVS10= DEVICE_DEVS11= DEVICE_DEVS12= \ DEVICE_DEVS13= DEVICE_DEVS14= DEVICE_DEVS15= DEVICE_DEVS16= \ DEVICE_DEVS17= DEVICE_DEVS18= DEVICE_DEVS19= DEVICE_DEVS20= \ DEVICE_DEVS_EXTRA= \ /bin/sh <./obj/../soobj/ldt.tr ./obj/../soobj/gdevl256.o(.text+0x73a): In function `gs_shared_init': : multiple definition of `gs_shared_init' ./obj/../soobj/gdevxalt.o(.text+0x1759): first defined here /usr/bin/ld: Warning: size of symbol `gs_shared_init' changed from 150 in ./obj/../soobj/gdevxalt.o to 38 in ./obj/../soobj/gdevl256.o ./obj/../soobj/gdevvglb.o(.text+0x995): In function `gs_shared_init': : multiple definition of `gs_shared_init' ./obj/../soobj/gdevxalt.o(.text+0x1759): first defined here gmake[1]: *** [bin/../sobin/libgs.so.8.64] Error 1 gmake[1]: Leaving directory `/usr/ports/print/ghostscript8/work/ghostscript-8.64' gmake: *** [so] Error 2 *** Error code 1 Any help? I am on 7.2-RELEASE now, but I was also getting this error while still on 7.1. -- 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"
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"
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"
