Re: libnotify
On 24-8-2011 23:51, Doug Barton wrote: On Wed, 24 Aug 2011 05:38:50 -0500 ajtiMlum...@gmail.com wrote: My system: FreeBSD 8.2-RELEASE-p1 I did: portmaster -r libnotify-0.\* libproxy-0.\* portmaster -a It's not clear to me exactly what you were trying to accomplish there, but a few notes The -r option can only be run for one port at a time. Ok I didn't know this. Does portmaster support it if you specify something like -r libnotify -r libproxy? Or is the only way to go to run portmaster -r twice for both ports? The issue is that there is possible a good amount of overlap between the the two commands, so your forced to rebuilding several things double. -Koop Portmaster glob patterns do not need (and in fact strip) a * from the end of the input. hth, Doug ___ 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: [CFT] Dolphin-emu preliminary port
On Tue, 19 Jul 2011 13:38:16 +0200, Ganael Laplanche wrote Hi list, I've been working on a dolphin (Wii/GC emulator) port, see : http://forums.dolphin-emulator.com/showthread.php?tid=8254 The emulator works on i386 with software rendering. Unfortunately, I can't get OpenGL rendering work on my laptop, because of lack of support for GL_EXT_framebufer_object. I would be glad to see if some of you can get it working. Amd64 support is not ready yet because of the lack of a MAP_32BIT flag for mmap(2). I've tried a workaround, but without much luck (using MAP_FIXED). The port has been updated : Dolphin now builds and run on amd64 (the MAP_FIXED hack now works). OpenGL still needs testing : does it work on your box ? I would be happy to get comments on that. Please, see Dolphin's forum thread if you are interested in testing the port. Best regards, -- Ganael LAPLANCHE ganael.laplan...@martymac.org http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac marty...@freebsd.org, http://www.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: ruby and amarok - dead lock?
On Tue, 23 Aug 2011 22:57:11 +0200 Heino Tiedemann rotkaps_spam_t...@gmx.de wrote: Oliver Heesakkers free...@heesakkers.info wrote: Op dinsdag 23 augustus 2011 17:22:07 schreef Heino Tiedemann: Hi There ist is like a bite in your own ass (dead lock): [UODATING]: The default ruby version has been updated to 1.9. Please rebuild all ports that [AMAROK] BROKEN= does not build with ruby 1.9 What To do? Switch to audio/amarok-kde4. Bad idea. +1 I feel the kde4 version lost everything that made amarok unique. That meins complete KDE switch. For me too. And honestly, if I want something that looks like vista, I can install windows 7 :) At least recent kde4 versions are snapier that the fist ones, but I still don't feel motivated to move (which brings on the question of what WM I'll be using in a year or two). Unless it's an easy fix, I doubt these kde3/qt3 programs will get the attention needed to fix it. .. unfortunately :( Yep. -- Ion-Mihai Tetcu io...@tetcu.info ___ 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
libreoffice-legacy vs libreoffice?
Hi, whats the difference between libreoffice-legacy and libreoffice? Freshports says: Add libreoffice-legacy port for those with problems upgrading ?? What doas the legacy ports, waht the libreoffice does not? 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: libreoffice-legacy vs libreoffice?
Heino Tiedemann wrote on 25.08.2011 01:57: Hi, whats the difference between libreoffice-legacy and libreoffice? Freshports says: Add libreoffice-legacy port for those with problems upgrading ?? What doas the legacy ports, waht the libreoffice does not? Heino legacy - libreoffice 3.3.x non-legacy - libreoffice 3.4.x You may consult libreoffice.org documentation about the differences. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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
Update of libnotify and libproxy failed
I tried to update libnotify and libproxy as described in UPDATING from 20110823. After successfully building and installing some ports the process stops when it tries to build x11-toolkits/py-gnome-desktop: mv -f .deps/ecal_la-evo-calendar.Tpo .deps/ecal_la-evo-calendar.Plo (cd . \ /usr/local/bin/pygtk-codegen-2.0 \ --override ecal.override \ --register /usr/local/share/pygtk/2.0/defs/gtk-types.defs \ --register /usr/local/share/pygtk/2.0/defs/gdk-types.defs \ --register /usr/local/share/pygtk/2.0/defs/gdk-base-types.defs \ --prefix pyecal ecal.defs) gen-ecal.c \ cp gen-ecal.c ecal.c \ rm -f gen-ecal.c note: pygtk-codegen-2.0 is deprecated, use pygobject-codegen-2.0 instead note: I will now try to invoke pygobject-codegen-2.0 in the same directory Warning: Constructor for ECalComponent needs to be updated to new API See http://live.gnome.org/PyGTK_2fWhatsNew28#update-constructors ***INFO*** The coverage of global functions is 100.00% (5/5) ***INFO*** The coverage of methods is 100.00% (25/25) ***INFO*** There are no declared virtual proxies. ***INFO*** There are no declared virtual accessors. ***INFO*** There are no declared interface proxies. /bin/sh ../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I.. -I/usr/local/include/python2.7 -I/usr/local/include/python2.7 -I/usr/local/include -D_REENTRANT -DORBIT2=1 -I/usr/local/include/evolution-data-server-2.32 -I/usr/local/include -I/usr/local/include/ -I/usr/local/include/libxml2 -I/usr/local/include/gconf/2 -I/usr/local/include/libsoup-2.4 -I/usr/local/include/glib-2.0 -I/usr/local/include/orbit-2.0 -I/usr/local/include/pygtk-2.0 -I/usr/local/lib/libffi-3.0.9/include -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -O2 -pipe -fno-strict-aliasing -Wall -std=c9x -MT ecal_la-ecal.lo -MD -MP -MF .deps/ecal_la-ecal.Tpo -c -o ecal_la-ecal.lo `test -f 'ecal.c' || echo './'`ecal.c libtool: compile: cc -DHAVE_CONFIG_H -I. -I.. -I/usr/local/include/python2.7 -I/usr/local/include/python2.7 -I/usr/local/include -D_REENTRANT -DORBIT2=1 -I/usr/local/include/evolution-data-server-2.32 -I/usr/local/include -I/usr/local/include/ -I/usr/local/include/libxml2 -I/usr/local/include/gconf/2 -I/usr/local/include/libsoup-2.4 -I/usr/local/include/glib-2.0 -I/usr/local/include/orbit-2.0 -I/usr/local/include/pygtk-2.0 -I/usr/local/lib/libffi-3.0.9/include -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -O2 -pipe -fno-strict-aliasing -Wall -std=c9x -MT ecal_la-ecal.lo -MD -MP -MF .deps/ecal_la-ecal.Tpo -c ecal.c -fPIC -DPIC -o .libs/ecal_la-ecal.o mv -f .deps/ecal_la-ecal.Tpo .deps/ecal_la-ecal.Plo /bin/sh ../libtool --tag=CC --mode=link cc -D_REENTRANT -DORBIT2=1 -I/usr/local/include/evolution-data-server-2.32 -I/usr/local/include -I/usr/local/include/ -I/usr/local/include/libxml2 -I/usr/local/include/gconf/2 -I/usr/local/include/libsoup-2.4 -I/usr/local/include/glib-2.0 -I/usr/local/include/orbit-2.0 -I/usr/local/include/pygtk-2.0 -I/usr/local/lib/libffi-3.0.9/include -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -O2 -pipe -fno-strict-aliasing -Wall -std=c9x -module -avoid-version -export-symbols-regex initecal -L/usr/local/lib -o ecal.la -rpath /usr/local/lib/python2.7/site-packages/gtk-2.0/evolution ecal_la-ecalmodule.lo ecal_la-override_common.lo ecal_la-evo-ecal-environment.lo ecal_la-evo-calendar.lo ecal_la-ecal.lo -pthread -L/usr/local/lib -lecal-1.2 -lical -licalss -licalvcal -ledataserver-1.2 -lxml2 -lgconf-2 -lsoup-2.4 -lgio-2.0 -lgdk_pixbuf-2.0 -lpango-1.0 -lm -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 grep: /usr/local/lib/libproxy.la: No such file or directory sed: /usr/local/lib/libproxy.la: No such file or directory libtool: link: `/usr/local/lib/libproxy.la' is not a valid libtool archive gmake[2]: *** [ecal.la] Fehler 1 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/py-gnome-desktop/work/gnome-python-desktop-2.32.0/evolution' gmake[1]: *** [all-recursive] Fehler 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/py-gnome-desktop/work/gnome-python-desktop-2.32.0' gmake: *** [all] Fehler 2 *** Error code 1 Because of this failure I am not able to finish the update. Searching the forums and the web does not help. It seems that I am the only one with this problem? This happens at least on three boxes, all running FreeBSD 9.0-BETA1 from August, 22th. (rev. 199506). Any help would be really appreciated. Thanks in advance, Rainer Hurling ___ 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
[PATCH] japanese/jcode.pl Fix defined(%hash) is deprecated
Submitter-Id: current-users
Originator:Takefu
Organization: FOX Amateur Radio Club
Confidential: no
Synopsis: [PATCH] japanese/jcode.pl Fix defined(%hash) is deprecated
Severity: non-critical
Priority: low
Category: ports
Class: change-request
Release: FreeBSD 8.2 amd64
Description:
lang/perl5.12 or lang/perl5.14 problems occur in combination.
z2h_euc z2h_sjis and was out of the way to improve call and message.
# fined(%hash) is deprecated at /usr/local/lib/perl5/site_perl/5.12.1/jcode.pl
line 684.
# (Maybe you should just omit the defined()?)
# defined(%hash) is deprecated at
/usr/local/lib/perl5/site_perl/5.12.1/jcode.pl line 693.
# (Maybe you should just omit the defined()?)
see PR#149544
How-To-Repeat:
#!/usr/local/bin/perl
require jcode.pl;
$data = ;
jcode::z2h_sjis(\$data);
exit;
Fix:
--- ja-jcode.pl.patch begins here ---
diff -ruN /usr/ports/japanese/jcode.pl/Makefile japanese/jcode.pl/Makefile
--- /usr/ports/japanese/jcode.pl/Makefile 2011-05-30 10:51:40.0
+0900
+++ japanese/jcode.pl/Makefile 2011-08-24 15:10:04.0 +0900
@@ -7,26 +7,27 @@
PORTNAME= jcode.pl
PORTVERSION= 2.13
+PORTREVISION= 1
CATEGORIES=japanese perl5
MASTER_SITES= ftp://ftp.iij.ad.jp/pub/IIJ/dist/utashiro/perl/ \
- ftp://ftp.sra.co.jp/pub/lang/perl/sra-scripts/ \
- http://srekcah.org/jcode/
-EXTRACT_SUFX= # none
+ ftp://ftp.sra.co.jp/pub/lang/perl/sra-scripts/
+EXTRACT_SUFX=
MAINTAINER=po...@freebsd.org
COMMENT= Perl library for Japanese character code conversion
+CONFLICTS= ja-p5-jcode.pl-[0-9]*
+
USE_PERL5_RUN= yes
NO_WRKSUBDIR= yes
NO_BUILD= yes
EXTRACT_CMD= ${CP}
EXTRACT_BEFORE_ARGS=
-EXTRACT_AFTER_ARGS=.
-
-PLIST_FILES= %%SITE_PERL%%/${PORTNAME}
+EXTRACT_AFTER_ARGS=${WRKDIR}
+PLIST_FILES= ${SITE_PERL_REL}/${PORTNAME}
do-install:
- ${MKDIR} ${PREFIX}/${SITE_PERL_REL}/
+ ${MKDIR} ${PREFIX}/${SITE_PERL_REL}
${INSTALL_DATA} ${WRKDIR}/${DISTNAME}
${PREFIX}/${SITE_PERL_REL}/${PORTNAME}
.include bsd.port.mk
diff -ruN /usr/ports/japanese/jcode.pl/files/patch-aa
japanese/jcode.pl/files/patch-aa
--- /usr/ports/japanese/jcode.pl/files/patch-aa 1970-01-01 09:00:00.0
+0900
+++ japanese/jcode.pl/files/patch-aa2010-10-08 12:19:58.0 +0900
@@ -0,0 +1,20 @@
+--- jcode.pl-2.13.orig 2010-07-28 14:46:52.0 +0900
jcode.pl-2.13 2010-07-28 14:51:52.0 +0900
+@@ -681,7 +681,7 @@
+
+ sub z2h_euc {
+ local(*s, $n) = @_;
+-init_z2h_euc unless defined %z2h_euc;
++init_z2h_euc unless %z2h_euc;
+ $s =~ s/($re_euc_c|$re_euc_kana)/
+ $z2h_euc{$1} ? ($n++, $z2h_euc{$1}) : $1
+ /geo;
+@@ -690,7 +690,7 @@
+
+ sub z2h_sjis {
+ local(*s, $n) = @_;
+-init_z2h_sjis unless defined %z2h_sjis;
++init_z2h_sjis unless %z2h_sjis;
+ $s =~ s/($re_sjis_c)/$z2h_sjis{$1} ? ($n++, $z2h_sjis{$1}) : $1/geo;
+ $n;
+ }
--- ja-jcode.pl.patch ends here ---
___
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: libreoffice-legacy vs libreoffice?
On Thu, 25 Aug 2011 11:06:21 +0400, Ruslan Mahmatkhanov wrote: Heino Tiedemann wrote on 25.08.2011 01:57: Hi, whats the difference between libreoffice-legacy and libreoffice? Freshports says: Add libreoffice-legacy port for those with problems upgrading ?? What doas the legacy ports, waht the libreoffice does not? Heino legacy - libreoffice 3.3.x non-legacy - libreoffice 3.4.x You may consult libreoffice.org documentation about the differences. To be a bit more specific. We decided to follow upstream why will support two version of the libreoffice at the sametime. legacy which is the previous stable version and the current stable version. And because we mess up with libreoffice 3.4 we decided to applicate this rule now. see my previous mail Libreoffice plan sent to this list yesterday. Bapt ___ 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: Update of libnotify and libproxy failed
Am 25.08.2011 09:25, schrieb Rainer Hurling: I tried to update libnotify and libproxy as described in UPDATING from 20110823. After successfully building and installing some ports the process stops when it tries to build x11-toolkits/py-gnome-desktop: ... /bin/sh ../libtool --tag=CC --mode=link cc -D_REENTRANT -DORBIT2=1 -I/usr/local/include/evolution-data-server-2.32 -I/usr/local/include -I/usr/local/include/ -I/usr/local/include/libxml2 -I/usr/local/include/gconf/2 -I/usr/local/include/libsoup-2.4 -I/usr/local/include/glib-2.0 -I/usr/local/include/orbit-2.0 -I/usr/local/include/pygtk-2.0 -I/usr/local/lib/libffi-3.0.9/include -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -O2 -pipe -fno-strict-aliasing -Wall -std=c9x -module -avoid-version -export-symbols-regex initecal -L/usr/local/lib -o ecal.la -rpath /usr/local/lib/python2.7/site-packages/gtk-2.0/evolution ecal_la-ecalmodule.lo ecal_la-override_common.lo ecal_la-evo-ecal-environment.lo ecal_la-evo-calendar.lo ecal_la-ecal.lo -pthread -L/usr/local/lib -lecal-1.2 -lical -licalss -licalvcal -ledataserver-1.2 -lxml2 -lgconf-2 -lsoup-2.4 -lgio-2.0 -lgdk_pixbuf-2.0 -lpango-1.0 -lm -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 grep: /usr/local/lib/libproxy.la: No such file or directory sed: /usr/local/lib/libproxy.la: No such file or directory libtool: link: `/usr/local/lib/libproxy.la' is not a valid libtool archive gmake[2]: *** [ecal.la] Fehler 1 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/py-gnome-desktop/work/gnome-python-desktop-2.32.0/evolution' gmake[1]: *** [all-recursive] Fehler 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/py-gnome-desktop/work/gnome-python-desktop-2.32.0' gmake: *** [all] Fehler 2 *** Error code 1 Because of this failure I am not able to finish the update. Have you been using portmaster or portupgrade? In either case, try: grep -l libproxy\\.la /usr/local/lib/*.la \ | xargs -n1 pkg_info -q -W | sort -u This should give you a list of packages that still refer to the old version of libproxy. Update only these -- I suppose evolution-related ports will be part of the list --, then retry rebuilding py-gnome-desktop. You may also want to run pkg_libchk --raw (from the bsdadminscripts port) afterwards in order that to catch any other ports that need to be rebuilt. ___ 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: libnotify
On 08/24/2011 23:09, Koop Mast wrote: Ok I didn't know this. I cannot possibly say this enough: Read The Man Page -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.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
print/cups-* ports vs. GNUTLS
Hi Dirk, *, there seem to be a few issues with an up-to-date GNUTLS and cups-client (and possibly cups-image): When leaving the default port options alone, the cups-base port gets built WITHOUT_GNUTLS, while cups-client and cups-image get built WITH_GNUTLS. On my computer (8.2-RELEASE-psomething), this fails after the CUPS 1.4.8 configure script has complained that current GNU TLS cannot be made thread-safe. (Why this causes an abort in spite of being AC_WARN() and not AC_ERROR() escapes me.) However, Dirk, can I ask you to consider/change these points: - the defaults for all CUPS ports WRT. GNUTLS should be the same, IOW all other cups-* ports should also be switched to default GNUTLS=off. - the OPTIONS texts should use language like Use GNUTLS instead of OpenSSL or similar because that's what happens under the hood. To reproduce: 1. update gnutls and dependencies, 2. remove /var/db/ports/cups-client*/options 3. portmaster cups-client- Thanks. Best regards, Matthias ___ 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: print/cups-* ports vs. GNUTLS
Oh I see Dirk has just fixed this at 08:51 UTC. Thanks, that was quick! ___ 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: portmaster -r vs. ports/UPDATING (was: libnotify)
Am 24.08.2011 23:51, schrieb Doug Barton: On Wed, 24 Aug 2011 05:38:50 -0500 ajtiM lum...@gmail.com wrote: My system: FreeBSD 8.2-RELEASE-p1 I did: portmaster -r libnotify-0.\* libproxy-0.\* portmaster -a It's not clear to me exactly what you were trying to accomplish there, but a few notes The -r option can only be run for one port at a time. Doug, the user probably stuck to a ports/UPDATING entry, 20110823, written by gnome@ (cc'd). (Do we need to audit ports/UPDATING altogether for such misdirections?) Perhaps this behaviour could change in a future version of portmaster, in order to avoid rebuilding ports twice that depend on both... I've been longing for such a feature more than once and usually resorted to update just the ports, then figure out/update dependent ports with 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: portmaster -r vs. ports/UPDATING
On 08/25/2011 01:58, Matthias Andree wrote: Am 24.08.2011 23:51, schrieb Doug Barton: On Wed, 24 Aug 2011 05:38:50 -0500 ajtiM lum...@gmail.com wrote: My system: FreeBSD 8.2-RELEASE-p1 I did: portmaster -r libnotify-0.\* libproxy-0.\* portmaster -a It's not clear to me exactly what you were trying to accomplish there, but a few notes The -r option can only be run for one port at a time. Doug, the user probably stuck to a ports/UPDATING entry, 20110823, written by gnome@ (cc'd). Yes, that's apparent, and quite unfortunate. (Do we need to audit ports/UPDATING altogether for such misdirections?) I just fixed the libnotify entry, and searched down some of the more recent entries and didn't see any other similar problems. Perhaps this behaviour could change in a future version of portmaster, Patches are always welcome. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.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: vbox-manager shows nissan.de as background
On Wed, 24 Aug 2011 23:38:59 +0200, Norbert Augenstein wrote: Hi list, i was suprised to see the nissan.de webpage starting up in the background of my Virtualbox-Manager window. I coud not create a screenshot, i had to use my camera:) www.augenstein.net/auge/vbox_nissan.jpg rebuilding vbox and/or the kernel module does not help. Does anyone else see this? This looks a lot like an known nvidia rendering corruption problem that I have also seen on Linux. There is some common setting for xorg.conf to disable some option but I cannot recall which one exactly right now. I've also learned quite recently that a similar problem exists for Intel IGP and they also have an xorg.conf option for that. -- Bernhard Froehlich http://www.bluelife.at/ ___ 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: Update of libnotify and libproxy failed
Am 25.08.2011 10:20 (UTC+1) schrieb Matthias Andree: Am 25.08.2011 09:25, schrieb Rainer Hurling: I tried to update libnotify and libproxy as described in UPDATING from 20110823. After successfully building and installing some ports the process stops when it tries to build x11-toolkits/py-gnome-desktop: ... /bin/sh ../libtool --tag=CC --mode=link cc -D_REENTRANT -DORBIT2=1 -I/usr/local/include/evolution-data-server-2.32 -I/usr/local/include -I/usr/local/include/ -I/usr/local/include/libxml2 -I/usr/local/include/gconf/2 -I/usr/local/include/libsoup-2.4 -I/usr/local/include/glib-2.0 -I/usr/local/include/orbit-2.0 -I/usr/local/include/pygtk-2.0 -I/usr/local/lib/libffi-3.0.9/include -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -O2 -pipe -fno-strict-aliasing -Wall -std=c9x -module -avoid-version -export-symbols-regex initecal -L/usr/local/lib -o ecal.la -rpath /usr/local/lib/python2.7/site-packages/gtk-2.0/evolution ecal_la-ecalmodule.lo ecal_la-override_common.lo ecal_la-evo-ecal-environment.lo ecal_la-evo-calendar.lo ecal_la-ecal.lo -pthread -L/usr/local/lib -lecal-1.2 -lical -licalss -licalvcal -ledataserver-1.2 -lxml2 -lgconf-2 -lsoup-2.4 -lgio-2.0 -lgdk_pixbuf-2.0 -lpango-1.0 -lm -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 grep: /usr/local/lib/libproxy.la: No such file or directory sed: /usr/local/lib/libproxy.la: No such file or directory libtool: link: `/usr/local/lib/libproxy.la' is not a valid libtool archive gmake[2]: *** [ecal.la] Fehler 1 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/py-gnome-desktop/work/gnome-python-desktop-2.32.0/evolution' gmake[1]: *** [all-recursive] Fehler 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/py-gnome-desktop/work/gnome-python-desktop-2.32.0' gmake: *** [all] Fehler 2 *** Error code 1 Because of this failure I am not able to finish the update. Have you been using portmaster or portupgrade? Thanks for answering so fast. I used portmaster. But portupgrade produces the same result in this case. In either case, try: grep -l libproxy\\.la /usr/local/lib/*.la \ | xargs -n1 pkg_info -q -W | sort -u This generates only three files evolution-data-server-2.32.1_1 libchamplain-0.8.1 libgweather-2.30.3 This should give you a list of packages that still refer to the old version of libproxy. libgweather builds fine, libchamplain stops with the same error as py-gnome-desktop did. Any other idea? Rainer Update only these -- I suppose evolution-related ports will be part of the list --, then retry rebuilding py-gnome-desktop. You may also want to run pkg_libchk --raw (from the bsdadminscripts port) afterwards in order that to catch any other ports that need to be rebuilt. ___ 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: Update of libnotify and libproxy failed
Am 25.08.2011 11:37, schrieb Rainer Hurling: Am 25.08.2011 10:20 (UTC+1) schrieb Matthias Andree: Am 25.08.2011 09:25, schrieb Rainer Hurling: I tried to update libnotify and libproxy as described in UPDATING from 20110823. After successfully building and installing some ports the process stops when it tries to build x11-toolkits/py-gnome-desktop: ... /bin/sh ../libtool --tag=CC --mode=link cc -D_REENTRANT -DORBIT2=1 -I/usr/local/include/evolution-data-server-2.32 -I/usr/local/include -I/usr/local/include/ -I/usr/local/include/libxml2 -I/usr/local/include/gconf/2 -I/usr/local/include/libsoup-2.4 -I/usr/local/include/glib-2.0 -I/usr/local/include/orbit-2.0 -I/usr/local/include/pygtk-2.0 -I/usr/local/lib/libffi-3.0.9/include -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -O2 -pipe -fno-strict-aliasing -Wall -std=c9x -module -avoid-version -export-symbols-regex initecal -L/usr/local/lib -o ecal.la -rpath /usr/local/lib/python2.7/site-packages/gtk-2.0/evolution ecal_la-ecalmodule.lo ecal_la-override_common.lo ecal_la-evo-ecal-environment.lo ecal_la-evo-calendar.lo ecal_la-ecal.lo -pthread -L/usr/local/lib -lecal-1.2 -lical -licalss -licalvcal -ledataserver-1.2 -lxml2 -lgconf-2 -lsoup-2.4 -lgio-2.0 -lgdk_pixbuf-2.0 -lpango-1.0 -lm -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 grep: /usr/local/lib/libproxy.la: No such file or directory sed: /usr/local/lib/libproxy.la: No such file or directory libtool: link: `/usr/local/lib/libproxy.la' is not a valid libtool archive gmake[2]: *** [ecal.la] Fehler 1 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/py-gnome-desktop/work/gnome-python-desktop-2.32.0/evolution' gmake[1]: *** [all-recursive] Fehler 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/py-gnome-desktop/work/gnome-python-desktop-2.32.0' gmake: *** [all] Fehler 2 *** Error code 1 Because of this failure I am not able to finish the update. Have you been using portmaster or portupgrade? Thanks for answering so fast. I used portmaster. But portupgrade produces the same result in this case. In either case, try: grep -l libproxy\\.la /usr/local/lib/*.la \ | xargs -n1 pkg_info -q -W | sort -u This generates only three files evolution-data-server-2.32.1_1 libchamplain-0.8.1 libgweather-2.30.3 port/package names actually (not files). This should give you a list of packages that still refer to the old version of libproxy. libgweather builds fine, libchamplain stops with the same error as py-gnome-desktop did. You're not mentioning evolution-data-server which is likely the culprit - if you pass all three on the same portmaster command line, it should sort out the proper build order. Any other idea? The relevant ports/UPDATING instructions were faulty and have recently been revised by Doug Barton, they read # portmaster -r libnotify-0 # portmaster -r libproxy-0 # portmaster -a now. Does that help? ___ 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: portmaster -r vs. ports/UPDATING
[ multi -r arguments ] In article xs4all.4e560f4b.40...@freebsd.org, Doug Barton do...@freebsd.org writes: On 08/25/2011 01:58, Matthias Andree wrote: [...] Perhaps this behaviour could change in a future version of portmaster, Patches are always welcome. Can I send some money? I also want to run portmaster -r without argument list too long. ___ 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: Update of libnotify and libproxy failed
Am 25.08.2011 09:25, schrieb Rainer Hurling: I tried to update libnotify and libproxy as described in UPDATING from 20110823. After successfully building and installing some ports the process stops when it tries to build x11-toolkits/py-gnome-desktop: ... /bin/sh ../libtool --tag=CC --mode=link cc -D_REENTRANT -DORBIT2=1 -I/usr/local/include/evolution-data-server-2.32 -I/usr/local/include -I/usr/local/include/ -I/usr/local/include/libxml2 -I/usr/local/include/gconf/2 -I/usr/local/include/libsoup-2.4 -I/usr/local/include/glib-2.0 -I/usr/local/include/orbit-2.0 -I/usr/local/include/pygtk-2.0 -I/usr/local/lib/libffi-3.0.9/include -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -O2 -pipe -fno-strict-aliasing -Wall -std=c9x -module -avoid-version -export-symbols-regex initecal -L/usr/local/lib -o ecal.la -rpath /usr/local/lib/python2.7/site-packages/gtk-2.0/evolution ecal_la-ecalmodule.lo ecal_la-override_common.lo ecal_la-evo-ecal-environment.lo ecal_la-evo-calendar.lo ecal_la-ecal.lo -pthread -L/usr/local/lib -lecal-1.2 -lical -licalss -licalvcal -ledataserver-1.2 -lxml2 -lgconf-2 -lsoup-2.4 -lgio-2.0 -lgdk_pixbuf-2.0 -lpango-1.0 -lm -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 grep: /usr/local/lib/libproxy.la: No such file or directory sed: /usr/local/lib/libproxy.la: No such file or directory libtool: link: `/usr/local/lib/libproxy.la' is not a valid libtool Any other idea? The relevant ports/UPDATING instructions were faulty and have recently been revised by Doug Barton, they read # portmaster -r libnotify-0 # portmaster -r libproxy-0 # portmaster -a now. Does that help? I tried Dougs way of upgrading and got in trouble too. Brasero don't build because of a similar failture like Rainers Error during the py-gnome-desktop build. You have to update libnotify and libproxy first because some ports don't build with a new libnotify version and an old libproxy versin. The following way works for me: # portmaster devel/libnotify net/libproxy # portmaster -r libnotify-0 # portmaster -r libproxy-0 # portmaster -a Regards, Florian ___ 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: portmaster -r vs. ports/UPDATING
On 08/25/2011 02:55, Henk van Oers wrote: [ multi -r arguments ] In article xs4all.4e560f4b.40...@freebsd.org, Doug Barton do...@freebsd.org writes: On 08/25/2011 01:58, Matthias Andree wrote: [...] Perhaps this behaviour could change in a future version of portmaster, Patches are always welcome. Can I send some money? Always. :) http://dougbarton.us/portmaster-proposal.html I also want to run portmaster -r without argument list too long. That's one of the reasons I'm hesitant about this. Portmaster makes extensive use of environment variables to cache state about things, which is one reason it's so fast. However, this can lead to problems when the environment variables take up so much memory that command lines for the various system tools called by portmaster take up more space than is available. Over the last couple of years I've been working on reducing this, but it's difficult to find the happy medium. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.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: libreoffice with java: build fails in UTF-8 env
Le Tue, 23 Aug 2011 17:05:09 +, Baptiste Daroussin b...@freebsd.org a écrit : Hello, Yes building libreoffice with java option in an UTF8 environement is known to fail there is nothing I found to workaround that :( As it uses Ant to build the java code I think we could add -Dfile.encoding=iso-8859-1 to an ANT_OPTS environment variable. http://ant.apache.org/manual/running.html I've not tested this but I hope this should work (not sure for the encoding to use) Regards. ___ 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
ruby port downgrade
I probably missed it, but according to the 20110823: entry in UPDATING, the ruby port was downgraded to 1.8. My first question is why? Second, when checking on which version I have installed, this is the output: ruby --version ruby 1.9.2p290 (2011-07-09 revision 32553) [amd64-freebsd8] I therefore assume that I only have version 1.9 installed. Is that correct? Third, is there really any reason to go though all that bullshit to downgrade to the previous version? I have not seen any problems occurring on my system. -- Jerry ✌ jerry+po...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: ruby port downgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/25/11 06:43, Jerry wrote: I probably missed it, but according to the 20110823: entry in UPDATING, the ruby port was downgraded to 1.8. My first question is why? Only which version is installed by default is changed back. There are ports for both 1.8 and 1.9. Second, when checking on which version I have installed, this is the output: ruby --version ruby 1.9.2p290 (2011-07-09 revision 32553) [amd64-freebsd8] I therefore assume that I only have version 1.9 installed. Is that correct? Not necessarily, you may have ruby 1.8 installed also. Third, is there really any reason to go though all that bullshit to downgrade to the previous version? I have not seen any problems occurring on my system. That's fine, you can keep that, just add RUBY_DEFAULT_VER=1.9 to /etc/make.conf. The more people we have testing 1.9 the better! Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOVi5mAAoJEPXPYrMgexuh4rYH/RWY839hyYtwmSpsTPdmbBOa Zem6zJJuXwe0/y1k4i8Qt5c4xbI4fPjjleMRCTUQxj2lrL3o9g+syOJx8V3KoJcU b9/BJsUGmThaO5/GQTC4LsVn1zbxEj+XcS8ifmSKdHHwk1DsoaqXTyxnO4h9AkQ+ ElV0X8+AFV7TqUcTP8ZjzUHBeQomkeoutLO7NcgAvGxLwzff5xM2XbRFkGDIwVGb A05/rGfOk48KxJLCn7BJPSN5zowOIoSRviH2ZqvqwwQzrVvy298vYv0MB7mKQQnA OcQOrCjNHw2IFd7IBjDmVKQmGC6Ni+5XdkBRZaGWaJu0WIxipECVvlMenBdcvYM= =yVtu -END PGP SIGNATURE- ___ 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: ruby port downgrade
On Thu, 25 Aug 2011 07:13:42 -0400 Steve Wills articulated: On 08/25/11 06:43, Jerry wrote: I probably missed it, but according to the 20110823: entry in UPDATING, the ruby port was downgraded to 1.8. My first question is why? Only which version is installed by default is changed back. There are ports for both 1.8 and 1.9. Second, when checking on which version I have installed, this is the output: ruby --version ruby 1.9.2p290 (2011-07-09 revision 32553) [amd64-freebsd8] I therefore assume that I only have version 1.9 installed. Is that correct? Not necessarily, you may have ruby 1.8 installed also. Third, is there really any reason to go though all that bullshit to downgrade to the previous version? I have not seen any problems occurring on my system. That's fine, you can keep that, just add RUBY_DEFAULT_VER=1.9 to /etc/make.conf. The more people we have testing 1.9 the better! That did not actually answer my question(s). Exactly why is the port being reverted to 1.8 as the default; and how can I positively ascertain if I both versions installed? -- Jerry ✌ jerry+po...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: ruby port downgrade
On 25 Aug 2011 12:34, Jerry je...@seibercom.net wrote: On Thu, 25 Aug 2011 07:13:42 -0400 Steve Wills articulated: On 08/25/11 06:43, Jerry wrote: I probably missed it, but according to the 20110823: entry in UPDATING, the ruby port was downgraded to 1.8. My first question is why? Only which version is installed by default is changed back. There are ports for both 1.8 and 1.9. Second, when checking on which version I have installed, this is the output: ruby --version ruby 1.9.2p290 (2011-07-09 revision 32553) [amd64-freebsd8] I therefore assume that I only have version 1.9 installed. Is that correct? Not necessarily, you may have ruby 1.8 installed also. Third, is there really any reason to go though all that bullshit to downgrade to the previous version? I have not seen any problems occurring on my system. That's fine, you can keep that, just add RUBY_DEFAULT_VER=1.9 to /etc/make.conf. The more people we have testing 1.9 the better! That did not actually answer my question(s). Exactly why is the port being reverted to 1.8 as the default; and how can I positively ascertain if I both versions installed? Where have you been? Many people had trouble upgrading, asking on this very list about it, then the default switch was reverted, and again announced on this list. Please check the archive before making more demands on Steve's time. Chris ___ 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: libreoffice with java: build fails in UTF-8 env
On Thu, 25 Aug 2011 12:20:05 +0200, Patrick Lamaiziere wrote: Le Tue, 23 Aug 2011 17:05:09 +, Baptiste Daroussin b...@freebsd.org a écrit : Hello, Yes building libreoffice with java option in an UTF8 environement is known to fail there is nothing I found to workaround that :( As it uses Ant to build the java code I think we could add -Dfile.encoding=iso-8859-1 to an ANT_OPTS environment variable. http://ant.apache.org/manual/running.html I've not tested this but I hope this should work (not sure for the encoding to use) Regards. ___ 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 have a better fix :) I unbundled nearly all the java things, now I don't have utf8 problems anymore. Should be in the tree soon Bapt ___ 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: ruby port downgrade
Jerry writes: That did not actually answer my question(s). Exactly why is the port being reverted to 1.8 as the default; Insufficient testing for whether 1.9 works with ruby-using ports. and how can I positively ascertain if I have both versions installed? ls -al /var/db/pkg | grep ruby Robert Huff ___ 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: ruby port downgrade
On Thu, 25 Aug 2011 12:41:48 +0100 Chris Rees articulated: Where have you been? Many people had trouble upgrading, asking on this very list about it, then the default switch was reverted, and again announced on this list. Please check the archive before making more demands on Steve's time. Many people have problems installing/updating programs on FreeBSD and report them here on nearly a daily basis. That is certainly not news. There are all ready reported problems with the libnotify and libproxy updates. Are you inferring that no one should update a port until it has been verified as compatible and in proper working order or else risk having it reverted? Isn't it the responsibility of who ever releases said update into the ports system to verify if correctness? If not, then there is a serious deficiency in the entire ports system release mechanism. A problem that is becoming more and more profound on a nearly daily basis that even a simple perusal of the daily list messages would verify. And where do you get off accusing me of violating Steve's time? He volunteered an answer, abet not the one I was seeking, but never-the-less a response. I certainly did not seek his counsel out. -- Jerry ✌ jerry+po...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: ruby port downgrade
On 25 August 2011 13:01, Jerry je...@seibercom.net wrote: On Thu, 25 Aug 2011 12:41:48 +0100 Chris Rees articulated: Where have you been? Many people had trouble upgrading, asking on this very list about it, then the default switch was reverted, and again announced on this list. Please check the archive before making more demands on Steve's time. Many people have problems installing/updating programs on FreeBSD and report them here on nearly a daily basis. That is certainly not news. There are all ready reported problems with the libnotify and libproxy updates. Are you inferring that no one should update a port until it has been verified as compatible and in proper working order or else risk having it reverted? Isn't it the responsibility of who ever releases said update into the ports system to verify if correctness? If not, then there is a serious deficiency in the entire ports system release mechanism. A problem that is becoming more and more profound on a nearly daily basis that even a simple perusal of the daily list messages would verify. Do you really think he switched the default without testing? How many ports depend on ruby, compared to how many people actually maintain it? There are always edge cases, and not everything is caught -- ruby19 has been in ports for a long time now [1], and Steve even sent a patch out for review [2] before committing it -- as usual there was no public feedback from anyone until it was committed. And where do you get off accusing me of violating Steve's time? He volunteered an answer, abet not the one I was seeking, but never-the-less a response. I certainly did not seek his counsel out. Common etiquette (as well as the rules of this list) dictates that you should at least do a search on Google and the list archives before posting yet another question on the same topic. (there's one I've picked up by searching for ruby upgrade failed freebsd [3]) Chris [1] http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/ruby19/Makefile [2] http://www.freebsd.org/cgi/getmsg.cgi?fetch=425540+429185+/usr/local/www/db/text/2011/freebsd-ports/20110814.freebsd-ports [3] http://groups.google.com/group/mailing.freebsd.ports/browse_thread/thread/9bb9c58da10ae4c9 ___ 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
tinderbox: how to drop unneded Jail and Build
How to correctly remove Jail and Build, created by ./tc createJail and
./tc createBuild accordingly? I have 7.3-FreeBSD, that was needed to
one-time test single port. As far i understand, it's not enough to
remove directory ${pb}/7.3-FreeBSD, since there is logs/packages/build
etc for this build and database records also. How to deal with this
correctly?
--
Regards,
Ruslan
Tinderboxing kills... the drives.
___
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: Re: FreeBSD unmaintained ports which are currently scheduled for deletion
On 24 August 2011 14:47, Mikhail T. mi+t...@aldan.algebra.com wrote:
On -10.01.-28163 14:59, Peter Jeremy wrote:
portname: sysutils/cpuburn
Actually, the mastersite has been discontinued by the ISP. It looks
like it's still available elsewhere but I can't find a replacement
mastersite.
So this one is correct???
It seems to be - which is unfortunate.
Can it be unbroken by using the Internet archive?
--- Makefile 2 Aug 2011 17:03:41 - 1.9
+++ Makefile 24 Aug 2011 13:46:21 -
@@ -9,5 +9,5 @@
PORTVERSION= 1.4
CATEGORIES= sysutils
-MASTER_SITES= http://pages.sbcglobal.net/redelm/
+MASTER_SITES=
http://web.archive.org/web/20070304200856/http://pages.sbcglobal.net/redelm/
DISTNAME= cpuburn_${PORTVERSION:S/./_/g}
EXTRACT_SUFX= _tar.gz
If so, quite a few other victims of this latest purging can be given a new
life.
Mi,
Matthias recently made reference on this subject, if you care to take a look:
http://lists.freebsd.org/pipermail/cvs-ports/2011-August/223266.html
Thanks for sorting cpuburn by the way.
Chris
--
Chris Rees | FreeBSD Developer
cr...@freebsd.org | http://people.freebsd.org/~crees
___
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: tinderbox: how to drop unneded Jail and Build
Ruslan Mahmatkhanov wrote on 25.08.2011 16:44:
How to correctly remove Jail and Build, created by ./tc createJail and
./tc createBuild accordingly? I have 7.3-FreeBSD, that was needed to
one-time test single port. As far i understand, it's not enough to
remove directory ${pb}/7.3-FreeBSD, since there is logs/packages/build
etc for this build and database records also. How to deal with this
correctly?
And how to create Jail for 9.0-BETA1 (ftp method)? I see that in 9.0
layout is changed, so i got this error:
mirror: 550 Failed to change directory.
(/pub/FreeBSD/releases/i386/9.0-BETA1/base)
mirror: 550 Failed to change directory.
(/pub/FreeBSD/releases/i386/9.0-BETA1/dict)
mirror: 550 Failed to change directory.
(/pub/FreeBSD/releases/i386/9.0-BETA1/proflibs)
mirror: 550 src: No such file or directory.
(/pub/FreeBSD/releases/i386/9.0-BETA1/src)
When issuing ./tc createJail -j 9.0-BETA1 -d FreeBSD 9.0-BETA1 -t
9.0-BETA1 -u LFTP -H ftp.freebsd.org
Thanks.
--
Regards,
Ruslan
Tinderboxing kills... the drives.
___
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: tinderbox: how to drop unneded Jail and Build
On 25 August 2011 13:44, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:
How to correctly remove Jail and Build, created by ./tc createJail and ./tc
createBuild accordingly? I have 7.3-FreeBSD, that was needed to one-time
test single port. As far i understand, it's not enough to remove directory
${pb}/7.3-FreeBSD, since there is logs/packages/build
etc for this build and database records also. How to deal with this
correctly?
cd ${pb}/scripts ./tc rmBuild -b ${build} ./tc rmJail -j ${jail}
rm -r ${pb}/*/${jail_name} ${pb}/*/${build_name} ${pb}/${build_name}
PLEASE check the globbing using echo first
You may want to join tinderbox-l...@marcuscom.com too ;)
Chris
___
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 unmaintained ports which are currently scheduled for deletion
Am 24.08.2011 15:47, schrieb Mikhail T.:
On -10.01.-28163 14:59, Peter Jeremy wrote:
portname: sysutils/cpuburn
Actually, the mastersite has been discontinued by the ISP. It
looks
like it's still available elsewhere but I can't find a replacement
mastersite.
So this one is correct???
It seems to be - which is unfortunate.
Can it be unbroken by using the Internet archive?
--- Makefile2 Aug 2011 17:03:41 - 1.9
+++ Makefile24 Aug 2011 13:46:21 -
@@ -9,5 +9,5 @@
PORTVERSION= 1.4
CATEGORIES=sysutils
-MASTER_SITES= http://pages.sbcglobal.net/redelm/
+MASTER_SITES=
http://web.archive.org/web/20070304200856/http://pages.sbcglobal.net/redelm/
DISTNAME= cpuburn_${PORTVERSION:S/./_/g}
EXTRACT_SUFX= _tar.gz
If so, quite a few other victims of this latest purging can be given a
new life. Yours,
Wrong way. Either you become or find the/a new upstream maintainer or
it gets removed. We don't need to prolong life of otherwise dead
software. Again, FreeBSD ports are not a museum. For further
arguments, Chris has linked to an earlier message I'd sent.
If a port is really that important, someone can/will pick it up.
___
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: tinderbox: how to drop unneded Jail and Build
Chris Rees wrote on 25.08.2011 16:51:
On 25 August 2011 13:44, Ruslan Mahmatkhanovcvs-...@yandex.ru wrote:
How to correctly remove Jail and Build, created by ./tc createJail and ./tc
createBuild accordingly? I have 7.3-FreeBSD, that was needed to one-time
test single port. As far i understand, it's not enough to remove directory
${pb}/7.3-FreeBSD, since there is logs/packages/build
etc for this build and database records also. How to deal with this
correctly?
cd ${pb}/scripts ./tc rmBuild -b ${build} ./tc rmJail -j ${jail}
rm -r ${pb}/*/${jail_name} ${pb}/*/${build_name} ${pb}/${build_name}
PLEASE check the globbing using echo first
You may want to join tinderbox-l...@marcuscom.com too ;)
Chris
Nice, thank you. I believe that this should be added to the Tinderbox
Manual. And what about creating 9.0-BETA1 jail with -u LFTP question?
--
Regards,
Ruslan
Tinderboxing kills... the drives.
___
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: ruby port downgrade
On Thu, 25 Aug 2011 07:47:50 -0400 Robert Huff articulated: Jerry writes: That did not actually answer my question(s). Exactly why is the port being reverted to 1.8 as the default; Insufficient testing for whether 1.9 works with ruby-using ports. and how can I positively ascertain if I have both versions installed? ls -al /var/db/pkg | grep ruby Thanks Robert! Unlike Chris who apparently likes to see his name in print, you actually answered my question. ls -al /var/db/pkg | grep ruby drwxr-xr-x 2 root wheel 512 Aug 22 18:01 plasma-scriptengine-ruby-4.6.5/ drwxr-xr-x 2 root wheel 512 Aug 22 07:22 ruby-1.8.7.352,1/ drwxr-xr-x 2 root wheel 512 Aug 22 05:24 ruby-1.9.2.290,1/ drwxr-xr-x 2 root wheel 512 Aug 22 18:01 ruby18-kdebindings-4.6.5/ drwxr-xr-x 2 root wheel 512 Aug 22 07:22 ruby19-bdb48-0.6.6/ So it appears I do have both versions installed. -- Jerry ✌ jerry+po...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: vbox-manager shows nissan.de as background
On Thu, Aug 25, 2011 at 11:07:36AM +0200, Bernhard Froehlich wrote: On Wed, 24 Aug 2011 23:38:59 +0200, Norbert Augenstein wrote: Hi list, i was suprised to see the nissan.de webpage starting up in the background of my Virtualbox-Manager window. I coud not create a screenshot, i had to use my camera:) www.augenstein.net/auge/vbox_nissan.jpg rebuilding vbox and/or the kernel module does not help. Does anyone else see this? This looks a lot like an known nvidia rendering corruption problem that I have also seen on Linux. There is some common setting for xorg.conf to disable some option but I cannot recall which one exactly right now. I've also learned quite recently that a similar problem exists for Intel IGP and they also have an xorg.conf option for that. i found a simple workaround on freebsd forum, just disabeling hardware acceleration in flash settings remedies the problem. i could not reproduce it on my laptop and/or with any other website. thanx, -- auge ___ 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: tinderbox: how to drop unneded Jail and Build
On 25 August 2011 14:27, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:
Chris Rees wrote on 25.08.2011 16:51:
On 25 August 2011 13:44, Ruslan Mahmatkhanovcvs-...@yandex.ru wrote:
How to correctly remove Jail and Build, created by ./tc createJail and
./tc
createBuild accordingly? I have 7.3-FreeBSD, that was needed to one-time
test single port. As far i understand, it's not enough to remove
directory
${pb}/7.3-FreeBSD, since there is logs/packages/build
etc for this build and database records also. How to deal with this
correctly?
cd ${pb}/scripts ./tc rmBuild -b ${build} ./tc rmJail -j ${jail}
rm -r ${pb}/*/${jail_name} ${pb}/*/${build_name} ${pb}/${build_name}
PLEASE check the globbing using echo first
You may want to join tinderbox-l...@marcuscom.com too ;)
Chris
Nice, thank you. I believe that this should be added to the Tinderbox
Manual. And what about creating 9.0-BETA1 jail with -u LFTP question?
I've added it to the README, thanks for the suggestion [1].
For now I think you need to use csup and make world method for 9-,
sorry. I'm talking to re about what the future plans are regarding ftp
-- not sure if this xz distribution is The Future.
Chris
[1] http://marcuscom.com/pipermail/tinderbox-cvs/2011-August/001527.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
Re: FreeBSD unmaintained ports which are currently scheduled for deletion
On 25.08.2011 08:48, Chris Rees wrote: On 24 August 2011 14:47, Mikhail T.mi+t...@aldan.algebra.com wrote: Can it be unbroken by using the Internet archive? ... If so, quite a few other victims of this latest purging can be given a new life. Matthias recently made reference on this subject, if you care to take a look: http://lists.freebsd.org/pipermail/cvs-ports/2011-August/223266.html Thanks for the pointer. I disagree with Matthias very strongly on this -- and made my disagreement known in the past. It remains my deeply-held opinion, that only those ports, which fail to build, ought to be removed from the tree. I'm happy to learn, amdmi3@ is of similar persuasion. Matthias warns, that something we mirrored years ago could be missing crucial patches -- but that's inevitable even with actively-maintained ports, and FreeBSD, wisely, makes no promises of software quality or security. Matthias' proposal to remove unmaintained ports makes it impossible to find a PERFECT program, port it and wash one's hands away from it. Sooner or later somebody will come to claim, your software is too old and thus /could/ contain security holes, and therefor must be removed. Because we have too many ports or something. Perhaps more importantly, Matthias' argument is different from the problem at hand -- he seems to dislike old distfiles, but the current campaign targets not the old pieces, but those, for which the master-sites' have disappeared. For example, the sources of audio/adpcm date to 1994, but the port only got into trouble, when the FTP-site hosting it disappeared from the Internet... Likewise, sysutils/cpuburn's sources are from 2003, but the port arose no questions, until ATT discontinued subscribers' web-spaces (where the author was hosting the distfile) two months ago... Do we really want to allow ISPs to affect the contents of our ports collection in this manner? If we were really ruled by consensus, these unfortunate ports would've stayed because, evidently, there is no consensus, as Dmitry and Matthias discuss at the very beginning of the e-mail you linked to... It appears, that the rule currently being applied, is: remove, if there are no master-sites other than FreeBSD's mirrors (the deprecation messages state something else, but this is the real meaning). Though this rule is refreshingly objective, I still don't like it -- FreeBSD claimed there is a port for it long before the catchy there is an app for it, and this remains a major selling point for the OS. But, if the rule's application is unstoppable, then I'd save most of the victims of the current purge by switching them to archive.org. It can even be done automatically by a clever script... Yours, -mi ___ 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: Update of libnotify and libproxy failed
Am 25.08.2011 11:45 (UTC+1) schrieb Matthias Andree: Am 25.08.2011 11:37, schrieb Rainer Hurling: Am 25.08.2011 10:20 (UTC+1) schrieb Matthias Andree: Am 25.08.2011 09:25, schrieb Rainer Hurling: I tried to update libnotify and libproxy as described in UPDATING from 20110823. After successfully building and installing some ports the process stops when it tries to build x11-toolkits/py-gnome-desktop: ... /bin/sh ../libtool --tag=CC --mode=link cc -D_REENTRANT -DORBIT2=1 -I/usr/local/include/evolution-data-server-2.32 -I/usr/local/include -I/usr/local/include/ -I/usr/local/include/libxml2 -I/usr/local/include/gconf/2 -I/usr/local/include/libsoup-2.4 -I/usr/local/include/glib-2.0 -I/usr/local/include/orbit-2.0 -I/usr/local/include/pygtk-2.0 -I/usr/local/lib/libffi-3.0.9/include -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -O2 -pipe -fno-strict-aliasing -Wall -std=c9x -module -avoid-version -export-symbols-regex initecal -L/usr/local/lib -o ecal.la -rpath /usr/local/lib/python2.7/site-packages/gtk-2.0/evolution ecal_la-ecalmodule.lo ecal_la-override_common.lo ecal_la-evo-ecal-environment.lo ecal_la-evo-calendar.lo ecal_la-ecal.lo -pthread -L/usr/local/lib -lecal-1.2 -lical -licalss -licalvcal -ledataserver-1.2 -lxml2 -lgconf-2 -lsoup-2.4 -lgio-2.0 -lgdk_pixbuf-2.0 -lpango-1.0 -lm -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 grep: /usr/local/lib/libproxy.la: No such file or directory sed: /usr/local/lib/libproxy.la: No such file or directory libtool: link: `/usr/local/lib/libproxy.la' is not a valid libtool archive gmake[2]: *** [ecal.la] Fehler 1 gmake[2]: Leaving directory `/usr/ports/x11-toolkits/py-gnome-desktop/work/gnome-python-desktop-2.32.0/evolution' gmake[1]: *** [all-recursive] Fehler 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/py-gnome-desktop/work/gnome-python-desktop-2.32.0' gmake: *** [all] Fehler 2 *** Error code 1 Because of this failure I am not able to finish the update. Have you been using portmaster or portupgrade? Thanks for answering so fast. I used portmaster. But portupgrade produces the same result in this case. In either case, try: grep -l libproxy\\.la /usr/local/lib/*.la \ | xargs -n1 pkg_info -q -W | sort -u This generates only three files evolution-data-server-2.32.1_1 libchamplain-0.8.1 libgweather-2.30.3 port/package names actually (not files). Of course these are ports/packages, sorry for my impreciseness. This should give you a list of packages that still refer to the old version of libproxy. libgweather builds fine, libchamplain stops with the same error as py-gnome-desktop did. You're not mentioning evolution-data-server which is likely the culprit - if you pass all three on the same portmaster command line, it should sort out the proper build order. Aah, I did it the wrong direction, first reinstall libgweather, then trying libchamplain ... Thanks for the hint. Now evolution-data-server-2.32.1_1 builds and reinstalls, but libchamplain-0.8.1 again fails :-( Any other idea? The relevant ports/UPDATING instructions were faulty and have recently been revised by Doug Barton, they read # portmaster -r libnotify-0 # portmaster -r libproxy-0 # portmaster -a This also does not change my build problem with libchamplain. So I deinstalled libchamplain, build it new and reinstalled it (in this order). This worked. now. Does that help? Thanks again for your detailed help, Rainer Hurling ___ 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: ports/sysutils/diskcheckd (Re: bad sector in gmirror HDD)
On 24 August 2011 16:14, per...@pluto.rain.com wrote: When the specified or calculated rate exceeds 64KB/sec, the required sleep interval between 64KB chunks is less than one second. Since diskcheckd calculates the interval in whole seconds -- because it calls sleep() rather than usleep() or nanosleep() -- an interval of less than one second is calculated as zero ... I suspect the fix will be to calculate in microseconds, and call usleep() instead of sleep(). I think I may have this fixed. Could one of you try the attached patch? I'm especially interested to see if this also clears up the issues reported as connected with gmirror (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/143566), since I haven't been able to reproduce that part here. Summary of changes: * Calculate delays in microseconds, so that delays of less than one second between reads (needed to implement rates exceeding 64KB/sec) do not get rounded down to zero. * Fix a reinitialization problem when handling SIGHUP. * Additional debug messages (only with -d). * Comment and manpage improvememts. Hi Perry, The changes look good, so if there's no response for a few days I'll commit the changes. Thanks for rescuing the port :) Chris -- Chris Rees | FreeBSD Developer cr...@freebsd.org | http://people.freebsd.org/~crees ___ 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
Problems building devel/gobject-introspection
I am having problems building devel/gobject-introspection on one
9.0-BETA1 host. I can build it without problems on 8.2 and another
9.0-BETA1 box. In all cases, I'm using gcc and amd64. The failure
is:
GISCAN GLib-2.0.gir
g-ir-scanner: GLib: warning: 484 warnings suppressed (use --warn-all to see
them)
Traceback (most recent call last):
File ./g-ir-scanner, line 43, in module
sys.exit(scanner_main(sys.argv))
File ./giscanner/scannermain.py, line 427, in scanner_main
exported_packages, options.c_includes)
File ./giscanner/girwriter.py, line 40, in __init__
c_includes)
File ./giscanner/girwriter.py, line 64, in _write_repository
self._write_namespace(namespace, shlibs)
File ./giscanner/girwriter.py, line 100, in _write_namespace
self._write_node(node)
File ./giscanner/girwriter.py, line 125, in _write_node
self._write_constant(node)
File ./giscanner/girwriter.py, line 350, in _write_constant
with self.tagcontext('constant', attrs):
File /usr/local/lib/python2.7/contextlib.py, line 17, in __enter__
return self.gen.next()
File ./giscanner/xmlwriter.py, line 165, in tagcontext
self.push_tag(tag_name, attributes)
File ./giscanner/xmlwriter.py, line 153, in push_tag
self._open_tag(tag_name, attributes)
File ./giscanner/xmlwriter.py, line 97, in _open_tag
len(tag_name) + 2)
UnicodeDecodeError: 'utf8' codec can't decode byte 0x93 in position 39: invalid
start byte
gmake[2]: *** [GLib-2.0.gir] Error 1
gmake[2]: Leaving directory
`/tmp/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/tmp/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8'
gmake: *** [all] Error 2
*** Error code 1
Stop in /usr/ports/devel/gobject-introspection.
Note that if I go to the work directory and run gmake, the error
changes to:
UnicodeDecodeError: 'utf8' codec can't decode byte 0x81 in position 74: invalid
start byte
Since this only happens on one box, it's presumably something I've done
but I'm not sure what. Google hasn't helped. Does anyone have any
ideas on where to start looking?
--
Peter Jeremy
pgpJsAmfRItdk.pgp
Description: PGP signature
Re: ruby port downgrade
On Aug 25, 2011, at 5:01 AM, Jerry wrote: On Thu, 25 Aug 2011 12:41:48 +0100 Chris Rees articulated: Where have you been? Many people had trouble upgrading, asking on this very list about it, then the default switch was reverted, and again announced on this list. Please check the archive before making more demands on Steve's time. Many people have problems installing/updating programs on FreeBSD and report them here on nearly a daily basis. That is certainly not news. There are all ready reported problems with the libnotify and libproxy updates. Are you inferring that no one should update a port until it has been verified as compatible and in proper working order or else risk having it reverted? Isn't it the responsibility of who ever releases said update into the ports system to verify if correctness? If not, then there is a serious deficiency in the entire ports system release mechanism. A problem that is becoming more and more profound on a nearly daily basis that even a simple perusal of the daily list messages would verify. Hi, Jerry! You're certainly right that it's a task of maintainer that the new version won't cause any problems and will continue to work fine before upgrading. Steve Wills and a other people did a lot of work verifying that switching the default ruby version to 1.9 will have a minimal impact on FreeBSD users. This included, among other stuff, fixing ruby application to work with ruby 1.9, most notably portupgrade. However, when we turned the switch, a lot of users reported problems using ruby 1.9 we didn't anticipated in the beginning. We fixed some of them during the process, but it became obvious at that time that some work that have to be done will require a good amount of time, so we (me and swills@, who peformed the updated) decided to switch the default ruby version to 1.8 again, after 3 days ruby 1.9 being the default version. Those who are interested keeping ruby 1.9 default can still do it by using the above mentioned make.conf knob. Most of the problems reported are related to people using some applications that have not been updated to work with ruby 1.9 vm. Meanwhile, we continue to work on fixing the major issued people reported (some portupgrade glitches, ability to use the newer ruby-gems under ruby 1.9), and hopefully we'll be able to make it default again soon enough. -- ST4096-RIPE ___ 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
