From awd at awdcomp.net Mon Dec 1 01:20:55 2008 From: awd at awdcomp.net (Andrew) Date: Mon Dec 1 01:21:02 2008 Subject: Exim 4.69_1 and locking issues. Message-ID: <4933A6CE.6000003@awdcomp.net> Hi all, Running Exim 4.69 on 7.0-RELEASE-p6 FreeBSD. The box has been recently upgraded from 6.3 (like 24 hours ago). Currently Exim is sending the following lines to the log files. 2008-12-01 19:02:35 Failed to get write lock for /var/spool/exim/db/callout.lockfile: Invalid argument 2008-12-01 19:02:35 Failed to get write lock for /var/spool/exim/db/callout.lockfile: Invalid argument 2008-12-01 19:02:35 1L74Cp-000GRN-3R Cannot lock /var/spool/exim/input//1L74Cp-000GRN-3R-D (22): Invalid argument The permissions are all correct for the directories and for Exim itself. It is creating stacks and stacks of 0 byte files in the message spool directory. I have recompiled all the ports but to no avail. I've upgraded 2 other machines with 99.0% the same setup with no issues. The only difference is hostnames/ips and that this machine is running mysql on it. Everything else on the machine (spam-assassin, clamav, mysql) is working fine. Has anybody got any ideas? Cheers cya Andrew From bugmaster at FreeBSD.org Mon Dec 1 03:06:05 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 1 03:06:31 2008 Subject: Current unassigned ports problem reports Message-ID: <200812011106.mB1B65MU051593@freefall.freebsd.org> (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/129325 Update port: print/latex-csquotes update to 4.3 f ports/129296 [PATCH] net-im/pidgin-libnotify: add Russian translati o ports/129295 [PATCH] mesagl works on amd64 with x11/xlockmore f ports/129289 update net/vnc f ports/129288 patch by PR ports/108413 for net/vnc is not applied we o ports/129262 upgrade of finance/ledgersmb12 o ports/129235 www/wml is broken since update to 2.1a2 o ports/129134 update port: devel/jude-community: update to version 5 o ports/129130 [bsd.sites.mk] The source URL list in /usr/ports/Mk/bs o ports/129128 [Maintainer-update] graphics/sdl_image: update to 1.2. o ports/129123 [PATCH] japanese/ctags: update to 5.7j1 f ports/129086 [patch] Update port audio/ventrilo-server to 3.0.3 o ports/129069 [UPDATE] www/asterisk-gui to 2.0.4 f ports/129063 Update math/R to version 2.8.0 o ports/129043 Experimental version of net/poptop in FreeBSD ports o ports/128952 [NEW PORT] java/javadb: Sun's supported distribution o o ports/128846 New port: sysutils/linux-megacli2 - LSI MegaRAID SAS c o ports/128726 [NEW PORT] print/lyx16: Document processor interfaced f ports/128703 net/isc-dhcp40-client and net/isc-dhcp40-relay refer t o ports/128603 textproc/flex has too small capacity o ports/128558 New ports: emulators/sdlmame-devel f ports/128537 [patch] databases/rrdtool add missing font runtime dep f ports/128521 [patch] devel/icu build failed on TestFormatRelative f ports/128513 [PATCH] Fixed editors/emacs-devel for non-GTK support f ports/128490 net/freenx port does not work properly on freebsd-7 st f ports/128489 [PATCH] mail/sympa5 update to 5.4.3 o ports/128384 new port x11/xorg-minimal f ports/128323 Update of ports/x11-fonts/terminus-font f ports/128288 sysutils/hpacucli does not work f ports/128271 biology/ncbi-toolkit - blastall segfaults when output f ports/128142 update net/ekiga to 3.0.0 to fit GNOME 2.24 f ports/128141 update net/opal to 3.4.1 to fit GNOME 2.24 o ports/128140 update devel/pwlib to 2.4.1 to fit GNOME 2.24 f ports/128082 sysutils/megarc binary causes memory corruption f ports/128074 multimedia/mplayer does not play CSS encrypted DVDs f ports/128048 www/mod_proxy_html port installs broken configuration f ports/127995 net/isc-dhcp3-server creates a user/group with dynamic f ports/127905 science/gramps: installation and runtime problems with f ports/127854 [PATCH] databases/couchdb: update to 0.8.1 o ports/127851 Port update: multimedia/libdvdnav-mplayer - Update to f ports/127810 print/hplip 2.8.2 can't talk to my usnb printer (HP PS o ports/127728 ports/games/freebsd-games doesn't build, and larn(6) s f ports/127675 [patch] net/nss_ldap version 259, with fix for pw_{cha f ports/127513 mail/dcc-dccd sets home to /var/dcc even if you didn' o ports/127321 japanese/kon2-16dot: buffer overflow and mouse bugs f ports/127302 security/swatch: swatch-3.2.1_1 multiple issues f ports/127259 [update] devel/jude-community to 5.3 f ports/127181 audio/musicpd logs warning s ports/127087 mail/bincimap port does not include an rc.d file o ports/126905 Update port: audio/libmtp to version 0.3.1 o ports/126890 port update: lang/cmucl o ports/126674 New port: print/latex-babel o ports/126655 java/jboss4 can not take standard parameter "-b host_n s ports/126577 [Update]graphics/qgis:update to 0.11.0 f ports/126518 Unbroke archivers/lzo2 on i386 f ports/126322 [patch] sysutils/fusefs-kmod: Make install location co f ports/126228 [PATCH] mail/courier: new version 0.60.0 f ports/126161 security/bsp_upektfmess does not work on 7.0 o ports/126151 [NEW PORT] security/p5-Bro-devel: Perl module for scri o ports/126150 [NEW PORT] security/broccoli-devel: The Bro Client Com o ports/126148 [NEW PORT] security/bro-devel: System for detecting Ne f ports/126058 net/generic-nqs fails to compile f ports/126055 x11-toolkits/p5-Tk - segmentation fault running perl-t f ports/125960 sysutils/syscp lacks of chattr/chflags f ports/125783 New port: www/vulture - A HTTP reverse proxy for your o ports/125719 shells/pdksh, zombie process's occouring on SMP Machin o ports/125714 [patch] www/httptunnel: users not added f ports/125362 New port: devel/ocaml-lwt (cooperative threading libra o ports/125324 editors/the (3.2) looses cursor when compiled with PDC o ports/125201 audio/aqualung crashes o ports/124905 new port: databases/sqlitejdbc 051 o ports/124597 [NEW PORT] net/callweaver: Fork of the popular Open So o ports/124548 net/mDNSResponder port incompatible with gnome desktop f ports/124238 sysutils/heartbeat: patch request f ports/123424 [NEW PORT] net/winexe o ports/123247 linux-firefox and linux-seamonkey from multiple users o ports/123239 New port: graphics/diamondbox Layer based photo editor f ports/122276 Compiled audio/musicpd segfaults on FreeBSD 7.0 s ports/121902 [PATCH] textproc/ispell add OPTIONS o ports/121831 [PATCH] net/openbgpd: [SUMMARIZE CHANGES] o ports/121325 Xorg crashes when x11-wm/xcompmgr is running o ports/121259 New port: net/openamq OpenAMQ is a complete AMQP messa o ports/121050 New port: sysutils/heartbeat2 Linux High-Availability o ports/119183 [NEW PORT] net/freeradius-client: FreeRADIUS Client li f ports/118877 audio/streamripper does not detect song title from str f ports/116385 net/vnc using vnc.so crashes Xorg 7.3 when remote comp f ports/115304 multimedia/gpac-mp4box cannot import files larger than o ports/108795 ports/icc: Proposed update to icc port for intel compi f ports/107304 print/apsfilter does not print PDF to raw PostScript p o amd64/104311 ports/wine should be installable on amd64 s ports/85513 Intel C++ compiler not 100% binary compatible with sys 91 problems total. From avg at icyb.net.ua Mon Dec 1 03:19:07 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Mon Dec 1 03:19:13 2008 Subject: p5-Mail-IMAPClient-3.12 Message-ID: <4933C827.70503@icyb.net.ua> Should this port be marked with IS_INTERACTIVE or be fixed to not try to interact? Rationale: ---> Upgrading 'p5-Mail-IMAPClient-3.11' to 'p5-Mail-IMAPClient-3.12' (mail/p5-Mail-IMAPClient) ---> Building '/usr/ports/mail/p5-Mail-IMAPClient' ===> Cleaning for p5-Mail-IMAPClient-3.12 => Mail-IMAPClient-3.12.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from ftp://ftp.funet.fi/pub/languages/perl/CPAN/modules/by-module/Mail/. Mail-IMAPClient-3.12.tar.gz 100% of 165 kB 82 kBps ===> Extracting for p5-Mail-IMAPClient-3.12 => MD5 Checksum OK for Mail-IMAPClient-3.12.tar.gz. => SHA256 Checksum OK for Mail-IMAPClient-3.12.tar.gz. ===> p5-Mail-IMAPClient-3.12 depends on file: /usr/local/bin/perl5.8.8 - found ===> Patching for p5-Mail-IMAPClient-3.12 ===> p5-Mail-IMAPClient-3.12 depends on file: /usr/local/bin/perl5.8.8 - found ===> p5-Mail-IMAPClient-3.12 depends on file: /usr/local/bin/perl5.8.8 - found ===> Configuring for p5-Mail-IMAPClient-3.12 Checking if your kit is complete... Looks good Warning: prerequisite Test::Pod 0 not found. Writing Makefile for Mail::IMAPClient You have the option of running an extended suite of tests during 'make test'. This requires an IMAP server name, user account, and password to test with. Do you want to run the extended tests? (n/y) -- Andriy Gapon From jadawin at FreeBSD.org Mon Dec 1 03:42:48 2008 From: jadawin at FreeBSD.org (Philippe =?iso-8859-1?Q?Aud=E9oud?=) Date: Mon Dec 1 03:42:55 2008 Subject: p5-Mail-IMAPClient-3.12 In-Reply-To: <4933C827.70503@icyb.net.ua> References: <4933C827.70503@icyb.net.ua> Message-ID: <20081201113957.GA56381@tuxaco.net> On Lun, 01 d?c 2008, Andriy Gapon wrote: > > Should this port be marked with IS_INTERACTIVE or be fixed to not try to > interact? > [...] > Do you want to run the extended tests? (n/y) > Hello, I'm last committer for this port. I will have a look today or tomorrow -- Philippe Audeoud FreeBSD Committer | jadawin@FreeBSD.org From pawciobiel at gmail.com Mon Dec 1 09:59:19 2008 From: pawciobiel at gmail.com (P Bielecki) Date: Mon Dec 1 09:59:26 2008 Subject: python leftovers - native_libs.txt In-Reply-To: <1228068944.95696.36.camel@hood.oook.cz> References: <1228068944.95696.36.camel@hood.oook.cz> Message-ID: <49341CE1.5040800@gmail.com> Pav Lucistnik pisze: > A bunch of python ports suddenly install extra file that they didn't > install in the past: native_libs.txt. > > Anyone knows what's up? > > Example: > http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.6.20081128152658/py25-fusefs-0.2_1.log > http://peak.telecommunity.com/DevCenter/EggFormats#native-libs-txt Hope this help. -- P Bielecki http://pawciobiel.com From shild at sbcglobal.net Mon Dec 1 10:45:00 2008 From: shild at sbcglobal.net (Scott T. Hildreth) Date: Mon Dec 1 10:45:06 2008 Subject: Trying to build libcdio Message-ID: <1228155383.52982.7.camel@fbsd1.dyndns.org> I am trying to build libcdio, which vcdimager depends on, but I get this error, cd-info.c:37:28: error: libvcd/logging.h: No such file or directory cd-info.c:38:26: error: libvcd/files.h: No such file or directory cd-info.c:39:25: error: libvcd/info.h: No such file or directory libcdio doesn't depend on vcdimager, which installs these header files (I believe). Information for libcdio-0.78.2_2: Depends on: Dependency: pkg-config-0.23_1 Dependency: libiconv-1.11_1 Dependency: gettext-0.17_1 Dependency: popt-1.7_5 Dependency: libcddb-1.3.0 Dependency: cdparanoia-3.9.8_8 vcdimager depends on libcdio, but libcdio can't compile without the vcd header files. Information for vcdimager-0.7.23_5: Depends on: Dependency: pkg-config-0.23_1 Dependency: libiconv-1.11_1 Dependency: libxml2-2.6.32_2 Dependency: gettext-0.17_1 Dependency: popt-1.7_5 Dependency: libcddb-1.3.0 Dependency: cdparanoia-3.9.8_8 Dependency: libcdio-0.78.2_2 Any ideas? I am missing something here? Thanks, Scott From pz-freebsd-ports at ziemba.us Mon Dec 1 13:32:16 2008 From: pz-freebsd-ports at ziemba.us (G. Paul Ziemba) Date: Mon Dec 1 13:32:22 2008 Subject: Proposal: mechanism for local patches Message-ID: Hi Folks, I sometimes have local patches that I need to apply to ports. For various reasons, these patches are not available in the ports tree (e.g., bug fixes could be still propagating, or I'm trying out a bug fix locally before submitting it, or the local patches might be inappropriate or unwanted for the general FreeBSD populace, etc.) My current practice is to maintain my own tree of patch files and then reference them via EXTRA_PATCHES in /etc/make.conf. Mostly the patches get applied automatically when I upgrade my ports, and when the patches fail I learn about it immediately - no additional recordkeeping is required. However, I am looking for a better way. It's probably an unnatural use of EXTRA_PATCHES. Some ports define EXTRA_PATCHES themselves and override what I have defined in /etc/make.conf, so I have to resort to modifying the ports tree in place and keep yet another list of items to pay attention to when upgrading my ports. In hopes of stimulating some discussion, I propose a new variable, LOCAL_PATCHES (or maybe SITE_PATCHES), that would behave just like EXTRA_PATCHES, except that it would be designated specifically for site-local patches. It would be implemented in the do-patch target in bsd.port.mk at the end, after patches from PATCHDIR are applied, and patch Makefiles would, by convention, leave it unmolested. Have I overlooked some better approach to integrating site-local fixes? -- G. Paul Ziemba FreeBSD unix: 1:31PM up 23:01, 5 users, load averages: 0.20, 0.37, 0.72 From pav at FreeBSD.org Mon Dec 1 13:43:08 2008 From: pav at FreeBSD.org (Pav Lucistnik) Date: Mon Dec 1 13:43:15 2008 Subject: python leftovers - native_libs.txt In-Reply-To: <49341CE1.5040800@gmail.com> References: <1228068944.95696.36.camel@hood.oook.cz> <49341CE1.5040800@gmail.com> Message-ID: <1228167778.95696.62.camel@hood.oook.cz> P Bielecki p??e v po 01. 12. 2008 v 18:20 +0100: > Pav Lucistnik pisze: > > A bunch of python ports suddenly install extra file that they didn't > > install in the past: native_libs.txt. > > > > Anyone knows what's up? > > > > Example: > > http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/a.6.20081128152658/py25-fusefs-0.2_1.log > > > > http://peak.telecommunity.com/DevCenter/EggFormats#native-libs-txt > > Hope this help. Based on this and some other information I got, I think I'll just start adding them to the plists. -- Pav Lucistnik Two sausages are in a frying pan. One says, "Geez, it's hot in here isn't it?" And the other one says, "Aaaaaah! A talking sausage!" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081201/29170853/attachment.pgp From wxs at FreeBSD.org Mon Dec 1 19:20:14 2008 From: wxs at FreeBSD.org (Wesley Shields) Date: Mon Dec 1 19:20:20 2008 Subject: Proposal: mechanism for local patches In-Reply-To: References: Message-ID: <20081202032013.GG85116@atarininja.org> On Mon, Dec 01, 2008 at 09:31:35PM +0000, G. Paul Ziemba wrote: > Hi Folks, > > I sometimes have local patches that I need to apply to ports. For > various reasons, these patches are not available in the ports tree > (e.g., bug fixes could be still propagating, or I'm trying out a > bug fix locally before submitting it, or the local patches might be > inappropriate or unwanted for the general FreeBSD populace, etc.) > > My current practice is to maintain my own tree of patch files and > then reference them via EXTRA_PATCHES in /etc/make.conf. Mostly > the patches get applied automatically when I upgrade my ports, and > when the patches fail I learn about it immediately - no additional > recordkeeping is required. > > However, I am looking for a better way. It's probably an unnatural > use of EXTRA_PATCHES. Some ports define EXTRA_PATCHES themselves and > override what I have defined in /etc/make.conf, so I have to resort > to modifying the ports tree in place and keep yet another list of > items to pay attention to when upgrading my ports. > > In hopes of stimulating some discussion, I propose a new variable, > LOCAL_PATCHES (or maybe SITE_PATCHES), that would behave just like > EXTRA_PATCHES, except that it would be designated specifically for > site-local patches. It would be implemented in the do-patch target > in bsd.port.mk at the end, after patches from PATCHDIR are applied, > and patch Makefiles would, by convention, leave it unmolested. > > Have I overlooked some better approach to integrating site-local > fixes? I'm not aware of anything of this nature which exists. I think it's a good idea and would be happy to review anything you are willing to submit back to FreeBSD. -- WXS From Johan at double-l.nl Tue Dec 2 05:14:19 2008 From: Johan at double-l.nl (Johan Hendriks) Date: Tue Dec 2 05:14:26 2008 Subject: Samba 32-devel on 7.1 PRERELEASE fails to update Message-ID: <57200BF94E69E54880C9BB1AF714BBCB0111B0@w2003s01.double-l.local> Hello i try to portupgrade samba32-devel but i?ll get the following error. I also try?d to deinstall and reinstall the package but then the error comes up also. Compiling lib/netapi/user.c Linking non-shared library bin/libnetapi.a Compiling libsmb/libsmb_cache.c In file included from libsmb/libsmb_cache.c:25: include/libsmb_internal.h:176: error: expected specifier-qualifier-list before 'smbc_smb_encrypt_level' libsmb/libsmb_cache.c: In function 'SMBC_add_cached_server': libsmb/libsmb_cache.c:91: error: dereferencing pointer to incomplete type libsmb/libsmb_cache.c:91: error: dereferencing pointer to incomplete type libsmb/libsmb_cache.c:91: error: dereferencing pointer to incomplete type libsmb/libsmb_cache.c:91: error: dereferencing pointer to incomplete type libsmb/libsmb_cache.c:91: error: dereferencing pointer to incomplete type libsmb/libsmb_cache.c: In function 'SMBC_get_cached_server': libsmb/libsmb_cache.c:121: error: dereferencing pointer to incomplete type libsmb/libsmb_cache.c:163: error: called object 'smbc_getFunctionRemoveCachedServer(context)' is not a function libsmb/libsmb_cache.c:178: error: called object 'smbc_getFunctionRemoveCachedServer(context)' is not a function libsmb/libsmb_cache.c: In function 'SMBC_remove_cached_server': libsmb/libsmb_cache.c:203: error: dereferencing pointer to incomplete type libsmb/libsmb_cache.c:207: error: dereferencing pointer to incomplete type libsmb/libsmb_cache.c:207: error: dereferencing pointer to incomplete type libsmb/libsmb_cache.c:207: error: dereferencing pointer to incomplete type libsmb/libsmb_cache.c:207: error: dereferencing pointer to incomplete type libsmb/libsmb_cache.c:207: error: dereferencing pointer to incomplete type libsmb/libsmb_cache.c: In function 'SMBC_purge_cached_servers': libsmb/libsmb_cache.c:232: error: dereferencing pointer to incomplete type The following command failed: cc -I. -I/usr/ports/net/samba32-devel/work/samba-3.2.4/source -O -D_SAMBA_BUILD_=3 -I/usr/local/include -I/usr/ports/net/samba32-devel/work/samba-3.2.4/source/iniparser/src -Iinclude -I./include -I. -I. -I./lib/replace -I./lib/talloc -I./lib/tdb/include -I./libaddns -I./librpc -DHAVE_CONFIG_H -I/usr/local/include -Iinclude -I./include -I. -I. -I./lib/replace -I./lib/talloc -I./lib/tdb/include -I./libaddns -I./librpc -I./popt -I/usr/local/include -DLDAP_DEPRECATED -I/include -I/usr/ports/net/samba32-devel/work/samba-3.2.4/source/lib -D_SAMBA_BUILD_=3 -fPIC -DPIC -c libsmb/libsmb_cache.c -o libsmb/libsmb_cache.o gmake: *** [libsmb/libsmb_cache.o] Error 1 *** Error code 2 Stop in /usr/ports/net/samba32-devel. *** Error code 1 Stop in /usr/ports/net/samba32-devel. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.62477.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=samba-3.2.4 UPGRADE_PORT_VER=3.2.4 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! net/samba32-devel (samba-3.2.4) (unknown build error) Regards Johan Hendriks From randy at psg.com Tue Dec 2 06:02:23 2008 From: randy at psg.com (Randy Bush) Date: Tue Dec 2 06:02:31 2008 Subject: pptp mpd can not find /usr/local/sbin/pptpctrl Message-ID: <49353FEC.9080607@psg.com> [ maintainer listed as this mailing list :( ] running very current i386 on a soekris 5510 following the instructions on http://www.section6.net/wiki/index.php/Setting_up_a_PPTP_VPN_server_in_FreeBSD gets pptpd[76801]: MGR: Failed to exec /usr/local/sbin/pptpctrl! but no one installs pptpctrl, pptod, ... randy From amdmi3 at amdmi3.ru Tue Dec 2 10:30:01 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Tue Dec 2 10:30:08 2008 Subject: Proposal: mechanism for local patches In-Reply-To: References: Message-ID: <20081202180743.GB70240@hades.panopticon> * G. Paul Ziemba (pz-freebsd-ports@ziemba.us) wrote: > In hopes of stimulating some discussion, I propose a new variable, > LOCAL_PATCHES (or maybe SITE_PATCHES), that would behave just like > EXTRA_PATCHES, except that it would be designated specifically for > site-local patches. It would be implemented in the do-patch target > in bsd.port.mk at the end, after patches from PATCHDIR are applied, > and patch Makefiles would, by convention, leave it unmolested. > > Have I overlooked some better approach to integrating site-local > fixes? I am not aware of any mechanism for this. But I agree that it's really needed. Before (in cvsup times) we could just place patches under files/ and be happy, but now when more people use portsnap we need something better. I think making another variable that behaves like EXTRA_PATCHES is not convenient - you'll have to provide it per-port which means conditionals in make.conf. I think the most convenient way of implementing this is having a directory hierarchy (either two level ${CATEGORY}/${PORTNAME}/patch-*) or single level ${PORTNAME}/patch-*) and a single variable that makes port system look there for patches in addition to ${PATCHDIR}. Thus, you only have to add a single line to make.conf: USE_LOCALPATCHES= /usr/ports/local-patches (or /whereever) and from there on files will be searced in either /usr/ports/local-patches/${CATEGORY}/${PORTNAME} /usr/ports/local-patches/${PORTNAME}. AFAIK, port names are unique in the whole portstree, so single level layout seems to be easier to handle. Here's the draft patch for this functionality: http://people.freebsd.org/~amdmi3/local-patchdir.patch -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From lambert at lambertfam.org Tue Dec 2 12:00:03 2008 From: lambert at lambertfam.org (Scott Lambert) Date: Tue Dec 2 12:00:10 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081202180743.GB70240@hades.panopticon> References: <20081202180743.GB70240@hades.panopticon> Message-ID: <20081202192410.GA69963@sysmon.tcworks.net> On Tue, Dec 02, 2008 at 09:07:43PM +0300, Dmitry Marakasov wrote: > * G. Paul Ziemba (pz-freebsd-ports@ziemba.us) wrote: > > > In hopes of stimulating some discussion, I propose a new variable, > > LOCAL_PATCHES (or maybe SITE_PATCHES), that would behave just like > > EXTRA_PATCHES, except that it would be designated specifically for > > site-local patches. It would be implemented in the do-patch target > > in bsd.port.mk at the end, after patches from PATCHDIR are applied, > > and patch Makefiles would, by convention, leave it unmolested. > > > > Have I overlooked some better approach to integrating site-local > > fixes? > > I am not aware of any mechanism for this. But I agree that it's > really needed. Before (in cvsup times) we could just place patches > under files/ and be happy, but now when more people use portsnap > we need something better. > > I think making another variable that behaves like EXTRA_PATCHES is > not convenient - you'll have to provide it per-port which means > conditionals in make.conf. > > I think the most convenient way of implementing this is having > a directory hierarchy (either two level ${CATEGORY}/${PORTNAME}/patch-*) > or single level ${PORTNAME}/patch-*) and a single variable that makes > port system look there for patches in addition to ${PATCHDIR}. > > Thus, you only have to add a single line to make.conf: > > USE_LOCALPATCHES= /usr/ports/local-patches > (or /whereever) > > and from there on files will be searced in > > either /usr/ports/local-patches/${CATEGORY}/${PORTNAME} > /usr/ports/local-patches/${PORTNAME}. > > AFAIK, port names are unique in the whole portstree, so single level > layout seems to be easier to handle. > > Here's the draft patch for this functionality: > > http://people.freebsd.org/~amdmi3/local-patchdir.patch How about something like WRKDIRPREFIX? Presumably the logic for dealing with that structure is already in the system. Maybe you could have USE_LOCAL_PATCHES boolean which uses ${CATEGORY}/${PORTNAME}/files subdirs in WRKDIRPREFIX, or LOCALPATCHDIRPREFIX if you want to keep your patches in CVS/SVN without polluting the CVS/SVN working directory. Just a thought. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org From john.marshall at riverwillow.com.au Tue Dec 2 12:01:02 2008 From: john.marshall at riverwillow.com.au (John Marshall) Date: Tue Dec 2 12:01:08 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081202180743.GB70240@hades.panopticon> References: <20081202180743.GB70240@hades.panopticon> Message-ID: <20081202194551.GC45319@rwpc12.mby.riverwillow.net.au> On Tue, 02 Dec 2008, 21:07 +0300, Dmitry Marakasov wrote: > I think the most convenient way of implementing this is having > a directory hierarchy (either two level ${CATEGORY}/${PORTNAME}/patch-*) > or single level ${PORTNAME}/patch-*) and a single variable that makes > port system look there for patches in addition to ${PATCHDIR}. Or keep local patches under /var/db/ports/ rather than building a new tree? -- John Marshall From wxs at FreeBSD.org Tue Dec 2 12:16:13 2008 From: wxs at FreeBSD.org (Wesley Shields) Date: Tue Dec 2 12:16:19 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081202180743.GB70240@hades.panopticon> References: <20081202180743.GB70240@hades.panopticon> Message-ID: <20081202201610.GA8753@atarininja.org> On Tue, Dec 02, 2008 at 09:07:43PM +0300, Dmitry Marakasov wrote: > * G. Paul Ziemba (pz-freebsd-ports@ziemba.us) wrote: > > > In hopes of stimulating some discussion, I propose a new variable, > > LOCAL_PATCHES (or maybe SITE_PATCHES), that would behave just like > > EXTRA_PATCHES, except that it would be designated specifically for > > site-local patches. It would be implemented in the do-patch target > > in bsd.port.mk at the end, after patches from PATCHDIR are applied, > > and patch Makefiles would, by convention, leave it unmolested. > > > > Have I overlooked some better approach to integrating site-local > > fixes? > > I am not aware of any mechanism for this. But I agree that it's > really needed. Before (in cvsup times) we could just place patches > under files/ and be happy, but now when more people use portsnap > we need something better. > > I think making another variable that behaves like EXTRA_PATCHES is > not convenient - you'll have to provide it per-port which means > conditionals in make.conf. > > I think the most convenient way of implementing this is having > a directory hierarchy (either two level ${CATEGORY}/${PORTNAME}/patch-*) > or single level ${PORTNAME}/patch-*) and a single variable that makes > port system look there for patches in addition to ${PATCHDIR}. > > Thus, you only have to add a single line to make.conf: > > USE_LOCALPATCHES= /usr/ports/local-patches > (or /whereever) > > and from there on files will be searced in > > either /usr/ports/local-patches/${CATEGORY}/${PORTNAME} > /usr/ports/local-patches/${PORTNAME}. > > AFAIK, port names are unique in the whole portstree, so single level > layout seems to be easier to handle. I like you're idea here, but unfortunately directory names are not unique. For example there is japanese/xchat and irc/xchat. This means you'll have to go with the "dual-level" layout. > Here's the draft patch for this functionality: > > http://people.freebsd.org/~amdmi3/local-patchdir.patch Other than the above comment I like the patch and would love to see it implemented. I think it can provide a benefit in situations where companies/people are doing things with ports that they do not want to contribute back. -- WXS From wxs at FreeBSD.org Tue Dec 2 12:18:10 2008 From: wxs at FreeBSD.org (Wesley Shields) Date: Tue Dec 2 12:18:17 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081202201610.GA8753@atarininja.org> References: <20081202180743.GB70240@hades.panopticon> <20081202201610.GA8753@atarininja.org> Message-ID: <20081202201810.GB8753@atarininja.org> On Tue, Dec 02, 2008 at 03:16:10PM -0500, Wesley Shields wrote: > On Tue, Dec 02, 2008 at 09:07:43PM +0300, Dmitry Marakasov wrote: > > * G. Paul Ziemba (pz-freebsd-ports@ziemba.us) wrote: > > > > > In hopes of stimulating some discussion, I propose a new variable, > > > LOCAL_PATCHES (or maybe SITE_PATCHES), that would behave just like > > > EXTRA_PATCHES, except that it would be designated specifically for > > > site-local patches. It would be implemented in the do-patch target > > > in bsd.port.mk at the end, after patches from PATCHDIR are applied, > > > and patch Makefiles would, by convention, leave it unmolested. > > > > > > Have I overlooked some better approach to integrating site-local > > > fixes? > > > > I am not aware of any mechanism for this. But I agree that it's > > really needed. Before (in cvsup times) we could just place patches > > under files/ and be happy, but now when more people use portsnap > > we need something better. > > > > I think making another variable that behaves like EXTRA_PATCHES is > > not convenient - you'll have to provide it per-port which means > > conditionals in make.conf. > > > > I think the most convenient way of implementing this is having > > a directory hierarchy (either two level ${CATEGORY}/${PORTNAME}/patch-*) > > or single level ${PORTNAME}/patch-*) and a single variable that makes > > port system look there for patches in addition to ${PATCHDIR}. > > > > Thus, you only have to add a single line to make.conf: > > > > USE_LOCALPATCHES= /usr/ports/local-patches > > (or /whereever) > > > > and from there on files will be searced in > > > > either /usr/ports/local-patches/${CATEGORY}/${PORTNAME} > > /usr/ports/local-patches/${PORTNAME}. > > > > AFAIK, port names are unique in the whole portstree, so single level > > layout seems to be easier to handle. > > I like you're idea here, but unfortunately directory names are not Make that "port names" instead of "directory names" in this context. -- WXS From pz-freebsd-ports at ziemba.us Tue Dec 2 14:33:43 2008 From: pz-freebsd-ports at ziemba.us (G. Paul Ziemba) Date: Tue Dec 2 14:33:49 2008 Subject: Proposal: mechanism for local patches References: <20081202201610.GA8753@atarininja.org> Message-ID: > [Site-local patches to ports] wxs@freebsd.org (Wesley Shields) writes: >On Tue, Dec 02, 2008 at 09:07:43PM +0300, Dmitry Marakasov wrote: >> Here's the draft patch for this functionality: >> >> http://people.freebsd.org/~amdmi3/local-patchdir.patch >Other than the above comment I like the patch and would love to see it >implemented. I think it can provide a benefit in situations where >companies/people are doing things with ports that they do not want to >contribute back. I, too, am happy with the idea of an administrator-specifiable parallel tree that would have the same structure as /usr/ports. So this approach involves, for the administrator (I am restating Dmitry's comments): 1. in /etc/make.conf, define USE_LOCALPATCHES= 2. put patches in ///patch-* If I may offer comments on Dmitry's draft patch: 1. Good that it's at the end of the do-patch target - that way local patches can happen after the "official" patches 2. I'm not sure we need the test for *.orig|*.rej|*~|*,v, but it wouldn't hurt. Maybe it helps admins who are actively developing local patches. I see that it's in the existing do-patch code above. 3. Does ${OPSYS} belong in the echoed messages for local patches? -- G. Paul Ziemba FreeBSD unix: 2:31PM up 2 days, 1 min, 8 users, load averages: 1.36, 1.30, 1.33 From pz-freebsd-ports at ziemba.us Tue Dec 2 18:11:15 2008 From: pz-freebsd-ports at ziemba.us (G. Paul Ziemba) Date: Tue Dec 2 18:11:21 2008 Subject: Proposal: mechanism for local patches References: <20081202192410.GA69963@sysmon.tcworks.net> Message-ID: lambert@lambertfam.org (Scott Lambert) writes: >How about something like WRKDIRPREFIX? >Presumably the logic for dealing with that structure is already in >the system. Maybe you could have USE_LOCAL_PATCHES boolean which >uses ${CATEGORY}/${PORTNAME}/files subdirs in WRKDIRPREFIX, or >LOCALPATCHDIRPREFIX if you want to keep your patches in CVS/SVN without >polluting the CVS/SVN working directory. I'm not sure I undersand - do you mean that you'd pick one of $(WRKDIRPREFIX)/${CATEGORY}/${PORTNAME}/files or $(LOCALPATCHDIRPREFIX)/${CATEGORY}/${PORTNAME}/files to get patches from, based on the state of USE_LOCAL_PATCHES? But I was hoping to augment $(WRKDIRPREFIX)/${CATEGORY}/${PORTNAME}/files instead of replacing it. -- G. Paul Ziemba FreeBSD unix: 6:06PM up 2 days, 3:36, 8 users, load averages: 1.55, 1.38, 1.31 From pz-freebsd-ports at ziemba.us Tue Dec 2 18:14:55 2008 From: pz-freebsd-ports at ziemba.us (G. Paul Ziemba) Date: Tue Dec 2 18:15:02 2008 Subject: Proposal: mechanism for local patches References: <20081202194551.GC45319@rwpc12.mby.riverwillow.net.au> Message-ID: john.marshall@riverwillow.com.au (John Marshall) writes: >On Tue, 02 Dec 2008, 21:07 +0300, Dmitry Marakasov wrote: >> I think the most convenient way of implementing this is having >> a directory hierarchy (either two level ${CATEGORY}/${PORTNAME}/patch-*) >> or single level ${PORTNAME}/patch-*) and a single variable that makes >> port system look there for patches in addition to ${PATCHDIR}. >Or keep local patches under /var/db/ports/ rather than building a >new tree? Hmm. I haven't really understood the way directories get named in /var/db/ports/ - what happens when there is a collision in the base name of two ports? It seems less obvious than //${CATEGORY}/${PORTNAME}/ -- G. Paul Ziemba FreeBSD unix: 6:11PM up 2 days, 3:41, 8 users, load averages: 1.58, 1.39, 1.31 From fbsd06 at mlists.homeunix.com Tue Dec 2 18:24:46 2008 From: fbsd06 at mlists.homeunix.com (RW) Date: Tue Dec 2 18:24:58 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081202180743.GB70240@hades.panopticon> References: <20081202180743.GB70240@hades.panopticon> Message-ID: <20081203020857.523645bc@gumby.homeunix.com> On Tue, 2 Dec 2008 21:07:43 +0300 Dmitry Marakasov wrote: > I am not aware of any mechanism for this. But I agree that it's > really needed. Before (in cvsup times) we could just place patches > under files/ and be happy, but now when more people use portsnap > we need something better. I wonder if portsnap actually needs to behave the way it does. Portsnap stores its compressed snapshot as one .gz file for each port plus one for each additional file (files in Mk/ etc). When you do an "update" any modified snapshot files are extracted over the appropriate location in the ports tree. The reason that "portsnap extract" deletes patch-files is that before each .gz file is extracted, the corresponding file or port directory is deleted. I wonder why, if an "update" can decompress over the top of a port, an "extract" need to delete it first. I can't think of any good reason offhand. Modifying portsnap not to delete extra files is just a matter of deleting one line. The behaviour of portsnap extract would then be virtually identical to csup. Alternately, it wouldn't be much harder to create a new portsnap command. From fbsd06 at mlists.homeunix.com Tue Dec 2 18:24:49 2008 From: fbsd06 at mlists.homeunix.com (RW) Date: Tue Dec 2 18:24:59 2008 Subject: Proposal: mechanism for local patches In-Reply-To: References: <20081202194551.GC45319@rwpc12.mby.riverwillow.net.au> Message-ID: <20081203022445.13cd2100@gumby.homeunix.com> On Wed, 3 Dec 2008 02:14:20 +0000 (UTC) "G. Paul Ziemba" wrote: > john.marshall@riverwillow.com.au (John Marshall) writes: > > >Or keep local patches under /var/db/ports/ rather than > >building a new tree? > > Hmm. I haven't really understood the way directories get named in > /var/db/ports/ - what happens when there is a collision in the > base name of two ports? It seems less obvious than > //${CATEGORY}/${PORTNAME}/ The names are not labelled by port names, but rather by UNIQUENAME # UNIQUENAME - A name for your port that is globally unique. By default, # this is set to ${LATEST_LINK} when LATEST_LINK is set, # and to ${PKGNAMEPREFIX}${PORTNAME} otherwise. From wxs at FreeBSD.org Tue Dec 2 18:25:04 2008 From: wxs at FreeBSD.org (Wesley Shields) Date: Tue Dec 2 18:25:10 2008 Subject: Proposal: mechanism for local patches In-Reply-To: References: <20081202194551.GC45319@rwpc12.mby.riverwillow.net.au> Message-ID: <20081203022503.GC8753@atarininja.org> On Wed, Dec 03, 2008 at 02:14:20AM +0000, G. Paul Ziemba wrote: > john.marshall@riverwillow.com.au (John Marshall) writes: > > >On Tue, 02 Dec 2008, 21:07 +0300, Dmitry Marakasov wrote: > >> I think the most convenient way of implementing this is having > >> a directory hierarchy (either two level ${CATEGORY}/${PORTNAME}/patch-*) > >> or single level ${PORTNAME}/patch-*) and a single variable that makes > >> port system look there for patches in addition to ${PATCHDIR}. > > >Or keep local patches under /var/db/ports/ rather than building a > >new tree? > > Hmm. I haven't really understood the way directories get named in > /var/db/ports/ - what happens when there is a collision in the > base name of two ports? It seems less obvious than > //${CATEGORY}/${PORTNAME}/ It uses UNIQUENAME, which is documented in Mk/bsd.port.mk. -- WXS From jtrigg at spamcop.net Tue Dec 2 19:25:09 2008 From: jtrigg at spamcop.net (Jim Trigg) Date: Tue Dec 2 19:25:15 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081203020857.523645bc@gumby.homeunix.com> References: <20081202180743.GB70240@hades.panopticon> <20081203020857.523645bc@gumby.homeunix.com> Message-ID: <87ef649b0812021903x7e2d3ee9h90dde2dcffe4e2be@mail.gmail.com> On Tue, Dec 2, 2008 at 9:08 PM, RW wrote: > I wonder if portsnap actually needs to behave the way it does. > > Portsnap stores its compressed snapshot as one .gz file for each > port plus one for each additional file (files in Mk/ etc). When you > do an "update" any modified snapshot files are extracted over > the appropriate location in the ports tree. > > The reason that "portsnap extract" deletes patch-files is that before > each .gz file is extracted, the corresponding file or port directory is > deleted. I wonder why, if an "update" can decompress over the top of a > port, an "extract" need to delete it first. I can't think of any good > reason offhand. > > Modifying portsnap not to delete extra files is just a matter of > deleting one line. The behaviour of portsnap extract would then be > virtually identical to csup. Alternately, it wouldn't be much harder to > create a new portsnap command. I would presume that it does that to get rid of "standard" patch files that are no longer part of the port... Jim Trigg From dino_vliet at yahoo.com Wed Dec 3 00:37:25 2008 From: dino_vliet at yahoo.com (Dino Vliet) Date: Wed Dec 3 00:37:31 2008 Subject: kldload: can't load /usr/local/modules/fuse.ko: Exec format error & fusefs-ntfs-1.2531 Message-ID: <255166.65897.qm@web51106.mail.re2.yahoo.com> Hi people, I can't use my maxtor basic 640gb external harddrive on Freebsd amd64 running 7.0 because when I try to load fusefs with this command, kldload /usr/local/modules/fuse.ko I get the following error: kldload: can't load /usr/local/modules/fuse.ko: Exec format error Adding fusefs_enable="YES" to /etc/rc.conf and fuse_load="YES" to /boot/loader.conf and rebooting doesn't help either, because then that error message is printed on the console. uname -a gives: FreeBSD zouk.telfort.nl 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #1: Thu Nov 27 13:42:17 CET 2008???? rgilaard@zouk.telfort.nl:/usr/obj/usr/src/sys/GENERIC? amd64 pkg_info | grep fuse gives: fusefs-kmod-0.3.9.p1.20080208_4 Kernel module for fuse fusefs-libs-2.7.3?? FUSE allows filesystem implementation in userspace fusefs-ntfs-1.2531? Mount NTFS partitions (read/write) and disk images Does anyone have a clue as to what is causing this behavior? I prefer to keep the external harddisk in ntfs format, although I could easily reformat it as ufs or ext3 because my whole system environment consists of bsd and linux. But I don't know if I will violate maxtor's guarantee. So I hope someone can help me with this. Brgds Dino From swhetzel at gmail.com Wed Dec 3 03:17:22 2008 From: swhetzel at gmail.com (Scot Hetzel) Date: Wed Dec 3 03:17:33 2008 Subject: kldload: can't load /usr/local/modules/fuse.ko: Exec format error & fusefs-ntfs-1.253 In-Reply-To: <255166.65897.qm@web51106.mail.re2.yahoo.com> References: <255166.65897.qm@web51106.mail.re2.yahoo.com> Message-ID: <790a9fff0812030317t579bb5c9kd950703f0a3ec976@mail.gmail.com> On 12/3/08, Dino Vliet wrote: > Hi people, > > I can't use my maxtor basic 640gb external harddrive on Freebsd amd64 running 7.0 because when I try to load fusefs with this command, kldload /usr/local/modules/fuse.ko I get the following error: > > kldload: can't load /usr/local/modules/fuse.ko: Exec format error > > Adding fusefs_enable="YES" to /etc/rc.conf and fuse_load="YES" to /boot/loader.conf and rebooting doesn't help either, because then that error message is printed on the console. > > uname -a gives: > FreeBSD zouk.telfort.nl 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #1: Thu Nov 27 13:42:17 CET 2008 rgilaard@zouk.telfort.nl:/usr/obj/usr/src/sys/GENERIC amd64 > > pkg_info | grep fuse gives: > > fusefs-kmod-0.3.9.p1.20080208_4 Kernel module for fuse > fusefs-libs-2.7.3 FUSE allows filesystem implementation in userspace > fusefs-ntfs-1.2531 Mount NTFS partitions (read/write) and disk images > > Does anyone have a clue as to what is causing this behavior? How did you install the fusefs-kmod was it from a package or did you build it through the ports system? The most likely cause of this error is due to the fuse.ko module was not built against the same source as your kernel. Rebuild fusefs-kmod and that should resolve the problem. Scot From swhetzel at gmail.com Wed Dec 3 03:21:47 2008 From: swhetzel at gmail.com (Scot Hetzel) Date: Wed Dec 3 03:21:59 2008 Subject: kldload: can't load /usr/local/modules/fuse.ko: Exec format error & fusefs-ntfs-1.253 In-Reply-To: <790a9fff0812030317t579bb5c9kd950703f0a3ec976@mail.gmail.com> References: <255166.65897.qm@web51106.mail.re2.yahoo.com> <790a9fff0812030317t579bb5c9kd950703f0a3ec976@mail.gmail.com> Message-ID: <790a9fff0812030321w4fcb000ew850d7c1a289a0365@mail.gmail.com> On 12/3/08, Scot Hetzel wrote: > On 12/3/08, Dino Vliet wrote: > > Hi people, > > > > I can't use my maxtor basic 640gb external harddrive on Freebsd amd64 running 7.0 because when I try to load fusefs with this command, kldload /usr/local/modules/fuse.ko I get the following error: > > > > kldload: can't load /usr/local/modules/fuse.ko: Exec format error > > : > > > > Does anyone have a clue as to what is causing this behavior? > > > How did you install the fusefs-kmod was it from a package or did you > build it through the ports system? > > The most likely cause of this error is due to the fuse.ko module was > not built against the same source as your kernel. Rebuild fusefs-kmod > and that should resolve the problem. > I usually see this problem after cvs updating the FreeBSD sources and then rebuilding a module, and trying to load that module. Rebuilding the kernel and all external modules should resolve the problem. Scot From amdmi3 at amdmi3.ru Wed Dec 3 04:42:57 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Wed Dec 3 04:43:03 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081202201610.GA8753@atarininja.org> References: <20081202180743.GB70240@hades.panopticon> <20081202201610.GA8753@atarininja.org> Message-ID: <20081203124236.GC70240@hades.panopticon> * Wesley Shields (wxs@FreeBSD.org) wrote: > I like you're idea here, but unfortunately directory names are not > unique. For example there is japanese/xchat and irc/xchat. This means > you'll have to go with the "dual-level" layout. As it was suggested, there's UNIQUENAME, but I'd prefer category/portname then. UNIQUENAME may be unintuitive sometimes. > > Here's the draft patch for this functionality: > > > > http://people.freebsd.org/~amdmi3/local-patchdir.patch > > Other than the above comment I like the patch and would love to see it > implemented. I think it can provide a benefit in situations where > companies/people are doing things with ports that they do not want to > contribute back. That's always useful, I think I'll improve it and make it committed after the freeze is over. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From amdmi3 at amdmi3.ru Wed Dec 3 05:12:54 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Wed Dec 3 05:13:06 2008 Subject: Proposal: mechanism for local patches In-Reply-To: References: <20081202201610.GA8753@atarininja.org> Message-ID: <20081203131234.GD70240@hades.panopticon> * G. Paul Ziemba (pz-freebsd-ports@ziemba.us) wrote: > I, too, am happy with the idea of an administrator-specifiable parallel > tree that would have the same structure as /usr/ports. So this approach > involves, for the administrator (I am restating Dmitry's comments): > > 1. in /etc/make.conf, define USE_LOCALPATCHES= > 2. put patches in ///patch-* > > If I may offer comments on Dmitry's draft patch: > > 1. Good that it's at the end of the do-patch target - that way local > patches can happen after the "official" patches Not sure if it's good actually. On the one hand, you usually have patches against vanilla sources, and just want to drop them to some dir and have them applied. Also, there's USE_DOS2UNIX that comes before any actual patching, so for ports that use USE_DOS2UNIX you'll have to adapt patches by hand. On the other hand, this may cause conflicts with patches from ports, and those would be hard to resolve. > 2. I'm not sure we need the test for *.orig|*.rej|*~|*,v, but it > wouldn't hurt. Maybe it helps admins who are actively developing > local patches. I see that it's in the existing do-patch code above. I suppose that check was done to help to detect patching failures, so it may be removed. > 3. Does ${OPSYS} belong in the echoed messages for local patches? Maybe not, I just copypasted the chunk. Yes, while what comes from portstree is definitely `FreeBSD', local patches are more just simply local & system-independent. I guess even patch- prefix is not required, but I'll keep it for now. Updated version here: http://people.freebsd.org/~amdmi3/local-patchdir.patch - Renamed some vars I guess LOCALPATCHDIR name is consistent with other user-settable directories (PORTSDIR, PKGDIR etc.) and internal PATCHDIR_LOCAL is (somewhat) consistent with PATCHDIR I guess s/LOCALPATCHDIR/LOCALPATCHESDIR/ may be even better - Added comment in LOCALPATCHDIR - Now uses 2 level tree under LOCALPATCHDIR (category/port) - Removed some (likely unneeded) checks -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From wxs at FreeBSD.org Wed Dec 3 07:12:02 2008 From: wxs at FreeBSD.org (Wesley Shields) Date: Wed Dec 3 07:12:09 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081203131234.GD70240@hades.panopticon> References: <20081202201610.GA8753@atarininja.org> <20081203131234.GD70240@hades.panopticon> Message-ID: <20081203151201.GE8753@atarininja.org> On Wed, Dec 03, 2008 at 04:12:34PM +0300, Dmitry Marakasov wrote: > * G. Paul Ziemba (pz-freebsd-ports@ziemba.us) wrote: > > > I, too, am happy with the idea of an administrator-specifiable parallel > > tree that would have the same structure as /usr/ports. So this approach > > involves, for the administrator (I am restating Dmitry's comments): > > > > 1. in /etc/make.conf, define USE_LOCALPATCHES= > > 2. put patches in ///patch-* > > > > If I may offer comments on Dmitry's draft patch: > > > > 1. Good that it's at the end of the do-patch target - that way local > > patches can happen after the "official" patches > > Not sure if it's good actually. > > On the one hand, you usually have patches against vanilla sources, and > just want to drop them to some dir and have them applied. > Also, there's USE_DOS2UNIX that comes before any actual patching, so for > ports that use USE_DOS2UNIX you'll have to adapt patches by hand. > > On the other hand, this may cause conflicts with patches from ports, > and those would be hard to resolve. I'd like to see any local patches applied after everything from the normal patch process is applied. It makes sense that local modifications happen after the normal process. This means that some patches may have to be massaged a bit. By doing local patching early you run into the same problem where the normal patches may have the be massaged a bit. I'd rather local patches be massaged as they will not be over-written during the next portsnap run. > > 2. I'm not sure we need the test for *.orig|*.rej|*~|*,v, but it > > wouldn't hurt. Maybe it helps admins who are actively developing > > local patches. I see that it's in the existing do-patch code above. > > I suppose that check was done to help to detect patching failures, so it > may be removed. I imagine this is because some people may have those left over from updates. We should continue to not use these files, just like the normal patching process does. > > 3. Does ${OPSYS} belong in the echoed messages for local patches? > > Maybe not, I just copypasted the chunk. Yes, while what comes from > portstree is definitely `FreeBSD', local patches are more just simply > local & system-independent. I guess even patch- prefix is not required, > but I'll keep it for now. > > Updated version here: > http://people.freebsd.org/~amdmi3/local-patchdir.patch > > - Renamed some vars > I guess LOCALPATCHDIR name is consistent with other user-settable > directories (PORTSDIR, PKGDIR etc.) and internal PATCHDIR_LOCAL is > (somewhat) consistent with PATCHDIR > I guess s/LOCALPATCHDIR/LOCALPATCHESDIR/ may be even better > - Added comment in LOCALPATCHDIR > - Now uses 2 level tree under LOCALPATCHDIR (category/port) > - Removed some (likely unneeded) checks A quick review looks good to me. I would have left the ${OPSYS} piece in there and gone with "Applying local ${OPSYS}..." to be more consistent with the description of other patches being applied. But that's just a minor nit and no big deal in the grand scheme of things. This sounds like a good idea to me and would love to see it get committed. -- WXS From mcdouga9 at egr.msu.edu Wed Dec 3 10:01:24 2008 From: mcdouga9 at egr.msu.edu (Adam McDougall) Date: Wed Dec 3 10:01:31 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081203020857.523645bc@gumby.homeunix.com> References: <20081202180743.GB70240@hades.panopticon> <20081203020857.523645bc@gumby.homeunix.com> Message-ID: <4936C567.70709@egr.msu.edu> RW wrote: > On Tue, 2 Dec 2008 21:07:43 +0300 > Dmitry Marakasov wrote: > > >> I am not aware of any mechanism for this. But I agree that it's >> really needed. Before (in cvsup times) we could just place patches >> under files/ and be happy, but now when more people use portsnap >> we need something better. >> > > I wonder if portsnap actually needs to behave the way it does. > > Portsnap stores its compressed snapshot as one .gz file for each > port plus one for each additional file (files in Mk/ etc). When you > do an "update" any modified snapshot files are extracted over > the appropriate location in the ports tree. > > The reason that "portsnap extract" deletes patch-files is that before > each .gz file is extracted, the corresponding file or port directory is > deleted. I wonder why, if an "update" can decompress over the top of a > port, an "extract" need to delete it first. I can't think of any good > reason offhand. > > Modifying portsnap not to delete extra files is just a matter of > deleting one line. The behaviour of portsnap extract would then be > virtually identical to csup. Alternately, it wouldn't be much harder to > create a new portsnap command. > > I've encountered a similar situation where I wanted to add patches or even patch/replace standard files in a port to meet my needs, but portsnap wipes them out. For now I'm using cfengine to re-apply my local changes to the ports tree on about 10 systems, but I have to remember to run cfagent after portsnap manually (I don't want to use cfengine in daemon mode). I thought it would be nice if portsnap.conf would let me specify a post-execution command so I could make it run cfagent on its own, so there is little chance to forget. My goal is to allow customizations while retaining the same standard command procedures that would be used on a plain system, to provide consistency across the board without introducing custom scripts that replace standard commands. In that light, it would be useful if csup had something similar, however I practically never need to maintain patches to /usr/src/. Just posting this as food for thought. From dino_vliet at yahoo.com Wed Dec 3 10:08:50 2008 From: dino_vliet at yahoo.com (Dino Vliet) Date: Wed Dec 3 10:08:56 2008 Subject: kldload: can't load /usr/local/modules/fuse.ko: Exec format error & fusefs-ntfs-1.253 In-Reply-To: <790a9fff0812030317t579bb5c9kd950703f0a3ec976@mail.gmail.com> Message-ID: <128452.3938.qm@web51108.mail.re2.yahoo.com> --- On Wed, 12/3/08, Scot Hetzel wrote: From: Scot Hetzel Subject: Re: kldload: can't load /usr/local/modules/fuse.ko: Exec format error & fusefs-ntfs-1.253 To: dino_vliet@yahoo.com Cc: alepulver@freebsd.org, freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Date: Wednesday, December 3, 2008, 12:17 PM On 12/3/08, Dino Vliet wrote: > Hi people, > > I can't use my maxtor basic 640gb external harddrive on Freebsd amd64 running 7.0 because when I try to load fusefs with this command, kldload /usr/local/modules/fuse.ko I get the following error: > > kldload: can't load /usr/local/modules/fuse.ko: Exec format error > > Adding fusefs_enable="YES" to /etc/rc.conf and fuse_load="YES" to /boot/loader.conf and rebooting doesn't help either, because then that error message is printed on the console. > > uname -a gives: > FreeBSD zouk.telfort.nl 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #1: Thu Nov 27 13:42:17 CET 2008 rgilaard@zouk.telfort.nl:/usr/obj/usr/src/sys/GENERIC amd64 > > pkg_info | grep fuse gives: > > fusefs-kmod-0.3.9.p1.20080208_4 Kernel module for fuse > fusefs-libs-2.7.3 FUSE allows filesystem implementation in userspace > fusefs-ntfs-1.2531 Mount NTFS partitions (read/write) and disk images > > Does anyone have a clue as to what is causing this behavior? How did you install the fusefs-kmod was it from a package or did you build it through the ports system? The most likely cause of this error is due to the fuse.ko module was not built against the same source as your kernel. Rebuild fusefs-kmod and that should resolve the problem. Scot Hi Scot, I installed it from ports. I think as a dependency on fusefs-ntfs? I will rebuild my system as I upgraded lately from 6.3 to 7, but I'm sure I just followed the handbook and did everything allright. Will post the results when I try this again afterwards. Brgds Dino From lambert at lambertfam.org Wed Dec 3 13:00:12 2008 From: lambert at lambertfam.org (Scott Lambert) Date: Wed Dec 3 13:00:19 2008 Subject: Proposal: mechanism for local patches In-Reply-To: References: <20081202192410.GA69963@sysmon.tcworks.net> Message-ID: <20081203202211.GA11883@sysmon.tcworks.net> On Wed, Dec 03, 2008 at 02:10:40AM +0000, G. Paul Ziemba wrote: > lambert@lambertfam.org (Scott Lambert) writes: > > >How about something like WRKDIRPREFIX? > > >Presumably the logic for dealing with that structure is already in > >the system. Maybe you could have USE_LOCAL_PATCHES boolean which > >uses ${CATEGORY}/${PORTNAME}/files subdirs in WRKDIRPREFIX, or > >LOCALPATCHDIRPREFIX if you want to keep your patches in CVS/SVN without > >polluting the CVS/SVN working directory. > > > I'm not sure I undersand - do you mean that you'd pick one of > $(WRKDIRPREFIX)/${CATEGORY}/${PORTNAME}/files or > $(LOCALPATCHDIRPREFIX)/${CATEGORY}/${PORTNAME}/files to get > patches from, based on the state of USE_LOCAL_PATCHES? But I was > hoping to augment $(WRKDIRPREFIX)/${CATEGORY}/${PORTNAME}/files > instead of replacing it. I meant them as implementation options. The person doing the work to add the functionality could choose which method to setup. I did *not* mean that both options should be setup in the Mk infrastructure and leave the choice to the user. But if the implementor wanted to do so, that would be their choice. Although, I suppose it could be setup such that only one new variable is required, something like LOCALPATCHDIRPREFIX. LOCALPATCHDIRPREFIX could default to WRKDIRPREFIX. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org From peter.schuller at infidyne.com Wed Dec 3 13:02:35 2008 From: peter.schuller at infidyne.com (Peter Schuller) Date: Wed Dec 3 13:02:42 2008 Subject: Deterministic package building with ports Message-ID: <20081203210233.GA55633@hyperion.scode.org> Hello, I have been in a perpetual multi-year struggle to sort out package building in a way which is practical for me. For the past half year or so I have ended up using a hacked together shell script which does approximately what I need, which is: To build deterministically as a function of (a) base system (b) /etc/make.conf (c) /usr/local/etc/ports.conf (sysutils/portconf) (d) a list of specifically desired origins/packages which is manually mainteined (NOT a complete list of dependencies, this is critical) (e) the ports tree a set of packages for later installation on another system (typically the host system or other jails). I build them in a dedicated package building jail, and can then either just "pkg_add *.tbz" or use a hacked script which sort of ends up doing the same, but differently. This has *sort* of worked, but not quite. I am fairly close now to have something that works, but am running into determinism issues. For example, the dependencies of audio/aumix is a function of what happens to already be built on the system. So initially when my script wants to build audio/aumix, it happens to be the case that no X stuff has been brought in yet, so 'make package-name' returns aumix-x.y.z. Later on when aumix is picked up as a dependency as part of building something else, 'make package-name' returns aumix-gtk-x.y.z. This causes confusion because the tool thinks the "origin"[1] audio/aumix has not been installed on the system. Is it the intent of the design of ports that the behavior of packages be implicitly dependent on the state of installed packages? If the answer is no, is there active interest in trying to fix any outstanding issues with respect to non-detemrinism that would allow people to write package managers that do things that depend on this[2]? If the answer is yes, can someone suggest a practically viable that consistently works, method of building binary packages under the above conditions? (I know of portupgrade/portmaster of course. I have never found a tool that both (1) does what I want and (2) actually works consistently. tinderbox I presume works, being used for official bulk builds if I am not mistaken, but it is *hugely* too administratively heavy/complex to set up just to be able to keep a system up-to-date! Have I just completely missed the existence of a silver-bullet solution that everyone is using?) [1] What is a proper term here? I have not come up with anything better, given that "package" is often interpreted as "binary package file". [2] I ran into the exact same problem with pkgsrc when writing pkgmanager, and I see no way to do what I want without having the relevant packaging system change. I need/want to perform higher-level operations on the packaging system, without having to work around specific issues that are a function of the exact details of the makefiles. Things I want to be determinstic include the plist, the list of dependencies, the package name, and the distfiles required. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081203/ab40eb49/attachment.pgp From peter.schuller at infidyne.com Wed Dec 3 13:16:28 2008 From: peter.schuller at infidyne.com (Peter Schuller) Date: Wed Dec 3 13:16:35 2008 Subject: Deterministic package building with ports In-Reply-To: <20081203210233.GA55633@hyperion.scode.org> References: <20081203210233.GA55633@hyperion.scode.org> Message-ID: <20081203211627.GA56450@hyperion.scode.org> > consistently. tinderbox I presume works, being used for official bulk Scratch the bit about tindexbox; brain lapse. But I also wanted to clarify that I specifically do not want to perform in-place upgrading from source, because the intent is to have a minimal time window during which the system is inoperative. In fact the current procedure is do pkg_delete *all* packages and just re-install. This is in fact fine (though it would be better to be able to intelligently re-install only what is needed). However note that I specifically do *not* want to play games with trying to minimalistically upgrade only those things that specifically are required according to dependency information. I gave up on this years ago; it just doesn't work without some perfect mythological ports tree. I specifically want to build packages from a snapshot of the ports tree; I do not want to mix old/new software, regardless of whether the dependency claims that some particular major version of a library is supposed to be compatible. The intent is to effectively build and deploy something which is as close as possible to what the port maintainer/build cluster will have tested, at all times. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081203/3eb0b49b/attachment.pgp From jonathan at kc8onw.net Wed Dec 3 13:22:41 2008 From: jonathan at kc8onw.net (Jonathan) Date: Wed Dec 3 13:22:48 2008 Subject: Preview of the 0.9.3 multimedia/handbrake port update Message-ID: <4936F885.8000307@kc8onw.net> Hello all, I have handbrake building successfully on FreeBSD 7 32bit and it seems to run fine. I would appreciate it if anyone interested could test this out before I file a PR to have it committed to the tree as this is my first significant port update. The distfiles can be found at [1] and should be unarchived into /usr/ports/distfiles/handbrake. The port itself can be found at [2]. If you have problems compiling please do a "make clean && script build.log make" compress the log and send it to me. Please let me know of any issues, Jonathan Stewart [1] http://www.kc8onw.net/~jonathan/temp/handbrake_distfiles.tar.bz2 [2] http://www.kc8onw.net/~jonathan/temp/handbrake_port_0.9.3.zip From smcafee at collaborativefusion.com Wed Dec 3 13:53:49 2008 From: smcafee at collaborativefusion.com (Sean McAfee) Date: Wed Dec 3 13:53:56 2008 Subject: Deterministic package building with ports In-Reply-To: <20081203211627.GA56450@hyperion.scode.org> References: <20081203210233.GA55633@hyperion.scode.org> <20081203211627.GA56450@hyperion.scode.org> Message-ID: <4936F9A4.8030504@collaborativefusion.com> Peter Schuller wrote: >> consistently. tinderbox I presume works, being used for official bulk > > Scratch the bit about tindexbox; brain lapse. > > But I also wanted to clarify that I specifically do not want to > perform in-place upgrading from source, because the intent is to have > a minimal time window during which the system is inoperative. In fact > the current procedure is do pkg_delete *all* packages and just > re-install. This is in fact fine (though it would be better to be able > to intelligently re-install only what is needed). > > However note that I specifically do *not* want to play games with > trying to minimalistically upgrade only those things that specifically > are required according to dependency information. I gave up on this > years ago; it just doesn't work without some perfect mythological > ports tree. I specifically want to build packages from a snapshot of > the ports tree; I do not want to mix old/new software, regardless of > whether the dependency claims that some particular major version of a > library is supposed to be compatible. The intent is to effectively > build and deploy something which is as close as possible to what the > port maintainer/build cluster will have tested, at all times. > I do something similar on a limited basis for clustered servers. It's a bit different because they all (theoretically) have the same packages installed, but I use this procedure: On the "donor" system: 1. portupgrade -a 2. for a in `pkg_info -ao | awk '{ print $1 }'` ; do pkg_create -b $a ; done 3. Push packages up to NFS'ed ports tree host's /usr/ports/packages On the remaining systems, it's just a matter of running portupgrade -aPP. Some pros: 1. Any local modifications (like to the rc script) follow the package 2. Easy, easy, easy 3. No "already installed" errors from doing make package 4. Automatically builds dependent packages Some cons: 1. Assumes that there are similar packages on all systems - i.e. no xorg 2. If the package is unavailable, it'll try to fetch it. This isn't a problem for us because firewall rules prevent the machines from getting to the internet, but it could be for others. As long as you'd be able to "profile" your varying systems (web servers vs. db servers vs. whatever) in jails, something similar might work for you. -- Sean McAfee System Engineer Collaborative Fusion, Inc. smcafee@collaborativefusion.com 412-422-3463 x 4025 5849 Forbes Avenue Pittsburgh, PA 15217 **************************************************************** IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. **************************************************************** IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. From dino_vliet at yahoo.com Wed Dec 3 13:54:54 2008 From: dino_vliet at yahoo.com (Dino Vliet) Date: Wed Dec 3 13:55:07 2008 Subject: kldload: can't load /usr/local/modules/fuse.ko: Exec format error & fusefs-ntfs-1.253 SOLVED In-Reply-To: <790a9fff0812030317t579bb5c9kd950703f0a3ec976@mail.gmail.com> Message-ID: <809060.17846.qm@web51112.mail.re2.yahoo.com> --- On Wed, 12/3/08, Scot Hetzel wrote: From: Scot Hetzel Subject: Re: kldload: can't load /usr/local/modules/fuse.ko: Exec format error & fusefs-ntfs-1.253 To: dino_vliet@yahoo.com Cc: alepulver@freebsd.org, freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Date: Wednesday, December 3, 2008, 12:17 PM On 12/3/08, Dino Vliet wrote: > Hi people, > > I can't use my maxtor basic 640gb external harddrive on Freebsd amd64 running 7.0 because when I try to load fusefs with this command, kldload /usr/local/modules/fuse.ko I get the following error: > > kldload: can't load /usr/local/modules/fuse.ko: Exec format error > > Adding fusefs_enable="YES" to /etc/rc.conf and fuse_load="YES" to /boot/loader.conf and rebooting doesn't help either, because then that error message is printed on the console. > > uname -a gives: > FreeBSD zouk.telfort.nl 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #1: Thu Nov 27 13:42:17 CET 2008 rgilaard@zouk.telfort.nl:/usr/obj/usr/src/sys/GENERIC amd64 > > pkg_info | grep fuse gives: > > fusefs-kmod-0.3.9.p1.20080208_4 Kernel module for fuse > fusefs-libs-2.7.3 FUSE allows filesystem implementation in userspace > fusefs-ntfs-1.2531 Mount NTFS partitions (read/write) and disk images > > Does anyone have a clue as to what is causing this behavior? How did you install the fusefs-kmod was it from a package or did you build it through the ports system? The most likely cause of this error is due to the fuse.ko module was not built against the same source as your kernel. Rebuild fusefs-kmod and that should resolve the problem. Scot Hi all, this did the trick, thanks! I rebuild my kernel and had to rebuild that port as well. Was sure I had done a portupgrade -fa before, but still it seemed I had to rebuild the port first. After this, I could start fusefs with the script in rc.d and after rebooting it recognized that option as well. Now I managed to mount my external disk with that as well, so everything is ok:-) Thanks again, Dino From dirk.meyer at dinoex.sub.org Wed Dec 3 14:00:38 2008 From: dirk.meyer at dinoex.sub.org (Dirk Meyer) Date: Wed Dec 3 14:00:46 2008 Subject: Deterministic package building with ports References: <20081203210233.GA55633@hyperion.scode.org> Message-ID: <74nEoWYVjf@dmeyer.dinoex.sub.org> Hallo Peter Schuller, > I have been in a perpetual multi-year struggle to sort out package > building in a way which is practical for me. For the past half year or > so I have ended up using a hacked together shell script which does > approximately what I need, which is: > > To build deterministically as a function of > (a) base system > (b) /etc/make.conf > (c) /usr/local/etc/ports.conf (sysutils/portconf) > (d) a list of specifically desired origins/packages which is manually > mainteined (NOT a complete list of dependencies, this is critical) > (e) the ports tree > a set of packages for later installation on another system > (typically the host system or other jails). > Have I just completely missed the existence of a silver-bullet > solution that everyone is using?) It may be not the silver bullet. Please take a look at: http://www.dinoex.net/training/package2.html kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany - [dirk.meyer@dinoex.sub.org],[dirk.meyer@guug.de],[dinoex@FreeBSD.org] http://people.freebsd.org/~dinoex/errorlogs/ From peter.schuller at infidyne.com Wed Dec 3 14:19:05 2008 From: peter.schuller at infidyne.com (Peter Schuller) Date: Wed Dec 3 14:19:13 2008 Subject: Deterministic package building with ports In-Reply-To: <4936F9A4.8030504@collaborativefusion.com> References: <20081203210233.GA55633@hyperion.scode.org> <20081203211627.GA56450@hyperion.scode.org> <4936F9A4.8030504@collaborativefusion.com> Message-ID: <20081203221903.GA57472@hyperion.scode.org> > On the "donor" system: > 1. portupgrade -a > 2. for a in `pkg_info -ao | awk '{ print $1 }'` ; do pkg_create -b $a ; done > 3. Push packages up to NFS'ed ports tree host's /usr/ports/packages > > On the remaining systems, it's just a matter of running portupgrade -aPP. Thanks! It helps to know what people are doing in practice. The problem I have with this is the 'portupgrade -a' step. portupgrade, in my experience, has sever issues with consistenty relative to the actual ports tree in dependencies and figuring out correctly what needs to be built and not. In addition, '-a' only upgrades individual ports that have changed; not ports depending on them. You can do -arR instead or similar, but that does not help because the process is not re-startable. I have not found out a way to make portupgrade ensure that installed packages are what you would have gotten had you installed your packages on a clean system from scratch. This latter is what portmanager tries to do. While I like the idea for in-place updating on a system, it has no supports for building packages, and it too has its own set of issues with respect to deciding what to upgrade and in what order. portupgrade also does not support the concept of maintaining a list of packages that you specifically want. This leads to problems over time as dependency ports move around, disappear and have files moving between them. Both tools, portmanager and portupgrade, have always ended up, for me, leading to a subset of broken packages that won't build or install for various reasons - with said set growing larger over time. The only method I have found which allows me to build and install ports in a way which mostly works, assuming the port is not broken, is to do "clean slate" installations. However, just doing "for origin in $(cat somelist) ; do cd ... ; make package-recusrive clean" and similar solutions have issues, including non-restability and issues with recursion and duplicate work/package creation. This is what I am trying to automate with my shell hacks... which again *mostly* work, but not quite either. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081203/9955fc3e/attachment.pgp From dougb at FreeBSD.org Wed Dec 3 14:45:56 2008 From: dougb at FreeBSD.org (Doug Barton) Date: Wed Dec 3 14:46:03 2008 Subject: Deterministic package building with ports In-Reply-To: <20081203210233.GA55633@hyperion.scode.org> References: <20081203210233.GA55633@hyperion.scode.org> Message-ID: <493705E2.907@FreeBSD.org> Peter Schuller wrote: > Hello, > > I have been in a perpetual multi-year struggle to sort out package > building in a way which is practical for me. One thing I'm confused about here, what are your goals? You don't mention why you need to build the packages. The answer to this might inform the rest of the conversation. > For the past half year or > so I have ended up using a hacked together shell script which does > approximately what I need, which is: > > To build deterministically as a function of > (a) base system > (b) /etc/make.conf > (c) /usr/local/etc/ports.conf (sysutils/portconf) These are givens, but it never hurts to mention requirements explicitly. > (d) a list of specifically desired origins/packages which is manually > mainteined (NOT a complete list of dependencies, this is critical) Why is not maintaining the list of dependencies critical? I'm guessing the answer is related to the dependencies being fluid over time. > (e) the ports tree > a set of packages for later installation on another system > (typically the host system or other jails). I'm assuming this last bit is the answer to my question above, which makes me even more curious as to your comment about the dependencies. > This has *sort* of worked, but not quite. I am fairly close now to > have something that works, but am running into determinism issues. For > example, the dependencies of audio/aumix is a function of what happens > to already be built on the system. So initially when my script wants > to build audio/aumix, it happens to be the case that no X stuff has > been brought in yet, so 'make package-name' returns aumix-x.y.z. Later > on when aumix is picked up as a dependency as part of building > something else, 'make package-name' returns aumix-gtk-x.y.z. This > causes confusion because the tool thinks the "origin"[1] audio/aumix > has not been installed on the system. > > Is it the intent of the design of ports that the behavior of packages > be implicitly dependent on the state of installed packages? > > If the answer is yes, can someone suggest a practically viable that > consistently works, method of building binary packages under the above > conditions? Yes, this is a feature. You could solve the problem you describe above by building the X stuff first. > (I know of portupgrade/portmaster of course. I have never found a tool > that both (1) does what I want What you want is beyond the scope of current tools. I have a proposal for adding this functionality to portmaster but it is a considerable amount of work and therefore I was hoping to get some funding to support it. > and (2) actually works consistently. If you wanted to list the ways that portmaster does not work consistently in a different thread I'd be interested. hth, Doug -- This .signature sanitized for your protection From peter.schuller at infidyne.com Wed Dec 3 15:00:15 2008 From: peter.schuller at infidyne.com (Peter Schuller) Date: Wed Dec 3 15:00:31 2008 Subject: Deterministic package building with ports In-Reply-To: <493705E2.907@FreeBSD.org> References: <20081203210233.GA55633@hyperion.scode.org> <493705E2.907@FreeBSD.org> Message-ID: <20081203230005.GB57472@hyperion.scode.org> Hello, > One thing I'm confused about here, what are your goals? You don't > mention why you need to build the packages. The answer to this might > inform the rest of the conversation. At the very highest level, the goal is to keep a system, or a set of system (large or small) up-to-date in an efficient manner, while minimizing downtime. I want to build packages separately not just to minimize the time window, but also to ensure that the full set of packages can successfully be built - avoiding a half-upgraded system that has issues to be resolved. The system(s) is/are assumed to need custom port options; thus use of bulk built packages is not an option. > > For the past half year or > > so I have ended up using a hacked together shell script which does > > approximately what I need, which is: > > > > To build deterministically as a function of > > (a) base system > > (b) /etc/make.conf > > (c) /usr/local/etc/ports.conf (sysutils/portconf) > > These are givens, but it never hurts to mention requirements explicitly. My intent was also to convey that I want it to be a function of *only* the list of things I provided, rather than an unknown set of factors. > > (d) a list of specifically desired origins/packages which is manually > > mainteined (NOT a complete list of dependencies, this is critical) > > Why is not maintaining the list of dependencies critical? I'm guessing > the answer is related to the dependencies being fluid over time. Because it becomes a huge pain when your complete package list is 1000 packages. What always ended up happening back when I tried keeping machines up to date by portupgrade/portmanager, was that every now and then I would just get fed up with all the built-up issues and re-install everything from scratch. The actual real-life goals are often very easily expressed in terms of a pretty small set of packages that one is actively interested in. Any manual maintenance of a very very significantly longer list of dependencies is just manual labor that you want to automate. I view it as the package management equivalent of maintaining a set of patches against a source tree instead of just forking it. I have something that I can realistically maintain manually which expresses exactly my intent, nothing more, nothing less. When writing pkgmanager (pkgsrc only) this was a major goal. You maintained your want list, and your pkgsrc tree, and you just told it "sync". It then did whatever it needed to do to produce a system which is identical to what you would have gotten by taking your list of desired packages and "bmake install":ing them on a clean system. It was all a function of a defined set of things, and the process was 100% restartable because all necessary discovery happened based on persistent information on disk. In short, you told it what you wanted, rather than what to do. Of course, this didn't work perfectly - mostly due to non-determinism. > > (e) the ports tree [keeping the above to keep the quoted list complete] > > Is it the intent of the design of ports that the behavior of packages > > be implicitly dependent on the state of installed packages? > > > > If the answer is yes, can someone suggest a practically viable that > > consistently works, method of building binary packages under the above > > conditions? > > Yes, this is a feature. You could solve the problem you describe above > by building the X stuff first. The problem is that I do not want to care about that. I know that "I want aumix" and that "I want firefox". I do not want to discover by a long period of trial and error that I need to fudge my tools to install aumix prior to firefox, or the other way around. We have even more trikier issues like "I want subversion" and "I want apache", and having to specify which apr has to be used. I see no general and simple way of implementing detection of such conflicts in a package manager built on top of ports, without modifying ports to accomodate. If being impacted by installed packages is considered a feature, it may be that my preferences/goals are just fundamentally incompatible with that of ports. Would there be interest/opinions on having ports support a mode of operation specifically targetted at automated tools and determinism? I suspect having a separate mode will just lead to too much complexity and breakage. > > (I know of portupgrade/portmaster of course. I have never found a tool > > that both (1) does what I want > > What you want is beyond the scope of current tools. I have a proposal > for adding this functionality to portmaster but it is a considerable > amount of work and therefore I was hoping to get some funding to support > it. Do you think it is appropriate to solve this elaborately in tools, as opposed to making changes to the ports infrastructure to facilitate these things? Am I barking up the wrong tree, hoping to see the latter? I have a genuine interest in having something which works and is reasonable simple to use for an administrator, and am willing to spend time on it. But not if the work is going to be linear with respect to various quirks and oddities of the underlying system. In my personal ideal world, the fact that the installed set of packages affects the dependency decision of a port would be a bug. I take it from the above that this is not consistent with the generally accepted view. I have planned for a long time to re-write pkgmanager and support both ports and pkgsrc; but fundamental issues such as determinism are putting me off (other than lazyness) because I know that it will never really work as well as I would want it to in order to be truly useful and more effective than the hacks I am currently using as a poor man's alternative. > > and (2) actually works consistently. > > If you wanted to list the ways that portmaster does not work > consistently in a different thread I'd be interested. I want to clarify right here for the record that I am not accusing portmaster of not working consistently. However, it did fall into (1) - that is, that it does not do what I personally want. portupgrade however does fall into both categories in my book. I'd be very very interesting in discussing package management and tool issues if you are willing. However, I'm not sure whether my personal goals are sufficiently in synch with yours or others for it to be very fruitful. I could try to recall past experience and issues I have run into administratively and when developing pkgmanager and try to state more clearly what my biased view is, with respect to what I would like tools to do, and how I think ports could facilitate those tools. Would freebsd-ports@ be a suitable forum for that? -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081203/7c764a2f/attachment.pgp From peter.schuller at infidyne.com Wed Dec 3 15:00:52 2008 From: peter.schuller at infidyne.com (Peter Schuller) Date: Wed Dec 3 15:00:59 2008 Subject: Deterministic package building with ports In-Reply-To: <74nEoWYVjf@dmeyer.dinoex.sub.org> References: <20081203210233.GA55633@hyperion.scode.org> <74nEoWYVjf@dmeyer.dinoex.sub.org> Message-ID: <20081203230051.GC57472@hyperion.scode.org> > It may be not the silver bullet. > Please take a look at: > http://www.dinoex.net/training/package2.html Thanks! I will. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081203/0270a206/attachment.pgp From fbsd06 at mlists.homeunix.com Wed Dec 3 17:30:45 2008 From: fbsd06 at mlists.homeunix.com (RW) Date: Wed Dec 3 17:30:51 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <87ef649b0812021903x7e2d3ee9h90dde2dcffe4e2be@mail.gmail.com> References: <20081202180743.GB70240@hades.panopticon> <20081203020857.523645bc@gumby.homeunix.com> <87ef649b0812021903x7e2d3ee9h90dde2dcffe4e2be@mail.gmail.com> Message-ID: <20081204011855.5132f7d8@gumby.homeunix.com> On Tue, 2 Dec 2008 22:03:08 -0500 "Jim Trigg" wrote: > On Tue, Dec 2, 2008 at 9:08 PM, RW wrote: > > directory is deleted. I wonder why, if an "update" can decompress > > over the top of a port, an "extract" need to delete it first. I > > can't think of any good reason offhand. > > > > I would presume that it does that to get rid of "standard" patch files > that are no longer part of the port... Yes, that is a good reason, I should have thought that through a bit. I still think that it's more aggressive than it needs be. I think it could probably just delete Makefile (in case the port is moved) plus any files in files/ that don't end in .local. That way you could still have local patchfiles, and anything else would be untouched including README.html and makefile.local From linimon at FreeBSD.org Wed Dec 3 21:23:08 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Dec 3 21:23:17 2008 Subject: FreeBSD unmaintained ports which are currently marked broken Message-ID: <20081204052306.DF5AA1CCED@mail.droso.net> As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 5.x/6.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/tse3 broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=tse3 portname: audio/xmms-imms broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=xmms-imms portname: chinese/iiimf-le-xcin broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-xcin portname: chinese/stardict2-dict-zh_TW broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=stardict2-dict-zh_TW portname: deskutils/mical broken because: Miscellaneous run-time failures due out of sync with the current versions of dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=mical portname: devel/fampp broken because: FAM system mismatch: gamin is installed, while desired FAM system is fam build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=fampp portname: devel/p5-ORBit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-ORBit portname: devel/pear-apd broken because: Incomplete pkg-plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=pear-apd portname: devel/py-coro broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=py-coro portname: devel/ruby-p4 broken because: does not compile build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/ruby18-p4-1.4251.log (Thu Nov 13 00:36:30 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ruby-p4 portname: emulators/xgs broken because: Does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=xgs portname: games/clanbomber broken because: Does not compile with the newer clanCore build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=clanbomber portname: games/euchre broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=euchre portname: graphics/libvisual-plugins broken because: Broken objformat handling build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=libvisual-plugins portname: graphics/ray++ broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=ray%2B%2B portname: irc/erc broken because: Conflicting dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=irc&portname=erc portname: japanese/okphone broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=okphone portname: japanese/oleo broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=oleo portname: japanese/p5-Text-ChaSen broken because: does not install build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081128152658/ja-p5-Text-ChaSen-1.03_3.log (Sat Nov 29 18:16:42 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=p5-Text-ChaSen portname: japanese/plain2 broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=plain2 portname: japanese/tkstep80 broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=tkstep80 portname: java/cacao broken because: does not configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=cacao portname: java/openjit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=openjit portname: java/tya broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=tya portname: lang/pfe-devel broken because: Does not compile with GCC 4.2 build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.6.20081122001658/pfe-0.32.94_1.log (Fri Nov 28 08:56:29 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pfe-devel portname: lang/pm3-base broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/pm3-base-1.1.15_2.log (Sat Jul 12 14:34:59 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-base portname: lang/pnet-base broken because: Bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pnet-base portname: lang/q broken because: bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=q portname: lang/quack broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=quack portname: lang/screamer broken because: Does not compile (dumps core) build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/screamer-3.20.log (Sat Jul 12 14:19:50 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=screamer portname: lang/scriba broken because: Does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=scriba portname: lang/wamcc broken because: does not compile on 7.X build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=wamcc portname: math/rascal broken because: Does not compile with GCC 4.2 build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.6.20081122001658/rascal-0.3.2_4.log (Fri Nov 28 09:06:59 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=rascal portname: math/ses broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=ses portname: misc/pybliographer broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=pybliographer portname: multimedia/jahshaka broken because: does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=jahshaka portname: multimedia/mplayerxp broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mplayerxp portname: multimedia/mythtv broken because: Incorrect handling of user addition build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mythtv portname: multimedia/smpeg-xmms broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=smpeg-xmms portname: multimedia/xmps-win32-plugin broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=xmps-win32-plugin portname: net-mgmt/NeTraMet broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=NeTraMet portname: net-p2p/py-kenosis-bittorrent broken because: fails to install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=py-kenosis-bittorrent portname: net/cap broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=cap portname: net/gnometelnet broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=gnometelnet portname: net/libunpipc broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=libunpipc portname: net/py-mantissa broken because: Leaves files behind after deinstallation build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=py-mantissa portname: net/versuch broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=versuch portname: palm/pdbc broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=pdbc portname: palm/synce-kde broken because: No longer supported by developers build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=synce-kde portname: palm/synce-multisync broken because: No longer supported by developers build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=synce-multisync portname: ports-mgmt/barry broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ports-mgmt&portname=barry portname: print/ifhp broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=ifhp portname: print/perlftlib broken because: Does not build if devel/p5-ExUtils-CBuilder is installed build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=perlftlib portname: science/gerris broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=gerris portname: science/oof broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=oof portname: security/newpki-lib broken because: does not compile with OpenSSL 0.9.8b build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=newpki-lib portname: security/newpki-server broken because: does not compile with OpenSSL 0.9.8b build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=newpki-server portname: security/opensaml broken because: Does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081128152658/opensaml-1.1.1_1.log (Sat Nov 29 18:13:15 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=opensaml portname: security/xmlsec broken because: Does not compile on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=xmlsec portname: shells/zoidberg broken because: does not package build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20081119214133/zoidberg-0.96.log (Fri Nov 7 18:59:47 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=zoidberg portname: sysutils/sjog broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=sjog portname: textproc/Ebnf2ps broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=Ebnf2ps portname: textproc/htmlize.el broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=htmlize.el portname: textproc/opensched broken because: Does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=opensched portname: www/bk_edit broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=bk_edit portname: www/gforge broken because: bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=gforge portname: www/ocaml-wdialog broken because: does not build with new ocaml build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=ocaml-wdialog portname: www/py-nevow broken because: doesn't build: in nevow/static.py", line 18, twisted.web import error build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=py-nevow portname: www/wb0 broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=wb0 portname: www/winhelpcgi broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=winhelpcgi portname: x11-themes/gtk-industrial-theme broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-themes&portname=gtk-industrial-theme portname: x11-toolkits/flu broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=flu portname: x11-toolkits/p5-Gnome broken because: fails to install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-Gnome portname: x11-toolkits/p5-qt broken because: Configure fails build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-qt portname: x11-toolkits/wxmozilla broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=wxmozilla portname: x11-wm/alloywm broken because: Checksum mismatch build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/alloywm-0.4.0_4.log (Sat Jul 12 14:19:21 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=alloywm portname: x11-wm/fluxspace broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=fluxspace portname: x11-wm/kahakai broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=kahakai portname: x11/9term broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=9term portname: x11/bbuname broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=bbuname From linimon at FreeBSD.org Wed Dec 3 21:23:48 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Dec 3 21:23:56 2008 Subject: FreeBSD ports which are currently marked broken Message-ID: <20081204052345.890611CC8A@mail.droso.net> As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 5.x/6.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/dream broken because: Needs DRM enabled in FAAD build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=dream portname: audio/esperanza broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=esperanza portname: audio/gstreamer-plugins-spc broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gstreamer-plugins-spc portname: audio/p5-Audio-TagLib broken because: does not build with taglib 1.5 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/p5-Audio-TagLib-1.43.log (Sat Jul 12 14:20:07 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=p5-Audio-TagLib portname: audio/py-sdl_mixer broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-sdl_mixer portname: audio/ruby-xmms2-ecore broken because: Fails to configure (can not find ecore-config) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ruby-xmms2-ecore portname: audio/shellac broken because: Not updated to the DrJekyl clientlib API build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=shellac portname: audio/snett broken because: Not updated to the DrJekyll clientlib API build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=snett portname: audio/tse3 broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=tse3 portname: audio/xmms-imms broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=xmms-imms portname: cad/opencascade broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=opencascade portname: chinese/iiimf-le-xcin broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-xcin portname: chinese/stardict2-dict-zh_TW broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=stardict2-dict-zh_TW portname: comms/hcfmdm broken because: Does not compile at 7.x build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=hcfmdm portname: converters/mimelib broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=converters&portname=mimelib portname: databases/erserver broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=erserver portname: databases/mysql-query-browser broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=mysql-query-browser portname: databases/mysqlbigram broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=mysqlbigram portname: databases/p5-DBD-PgSPI broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=p5-DBD-PgSPI portname: databases/py-tada broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=py-tada portname: databases/qdbm-java broken because: fails to install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=qdbm-java portname: databases/rubygem-rrdtool broken because: does not compile with rrdtool 1.3 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=rubygem-rrdtool portname: deskutils/launchy broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=launchy portname: deskutils/mical broken because: Miscellaneous run-time failures due out of sync with the current versions of dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=mical portname: deskutils/remember.el broken because: Conflicting dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=remember.el portname: devel/ace+tao broken because: Does not compile on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ace%2Btao portname: devel/cocktail broken because: Segfault during build on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=cocktail portname: devel/fampp broken because: FAM system mismatch: gamin is installed, while desired FAM system is fam build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=fampp portname: devel/gdb53-act broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=gdb53-act portname: devel/hs-buddha broken because: Does not build with recent GHC build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hs-buddha portname: devel/hs-fps broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hs-fps portname: devel/hs-hat broken because: Does not build with recent ghc build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hs-hat portname: devel/hs-hpl broken because: Does not build with current ghc build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hs-hpl portname: devel/hs-tclhaskell-ghc broken because: Needs updating to build with latest GHC build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hs-tclhaskell-ghc portname: devel/msp430-gdb broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=msp430-gdb portname: devel/nx broken because: leaves files behind on deinstall build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=nx portname: devel/p5-ORBit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-ORBit portname: devel/pear-apd broken because: Incomplete pkg-plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=pear-apd portname: devel/py-coro broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=py-coro portname: devel/py-turbocheetah broken because: does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=py-turbocheetah portname: devel/root broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=root portname: devel/ruby-p4 broken because: does not compile build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/ruby18-p4-1.4251.log (Thu Nov 13 00:36:30 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ruby-p4 portname: devel/ruby-rjudy broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ruby-rjudy portname: devel/xfc broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=xfc portname: editors/setedit broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=setedit portname: editors/zed broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=zed portname: emulators/mupen64-glide broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=mupen64-glide portname: emulators/mupen64-tr64 broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=mupen64-tr64 portname: emulators/snes9express broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=snes9express portname: emulators/xgs broken because: Does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=xgs portname: games/amy broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=amy portname: games/aqbubble broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=aqbubble portname: games/clanbomber broken because: Does not compile with the newer clanCore build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=clanbomber portname: games/emacs-chess broken because: Conflicting dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=emacs-chess portname: games/euchre broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=euchre portname: games/linux-alienarena broken because: needs missing/outdated Linux dependencies (need new linux_compat port and FreeBSD 7); use native instead for now build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=linux-alienarena portname: games/pykawari broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=pykawari portname: games/xrally broken because: Doesn't work (yet?) on 7.x build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=xrally portname: graphics/crystalspace-devel broken because: Incorrect pkg-plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=crystalspace-devel portname: graphics/gstreamer-plugins-swfdec broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=gstreamer-plugins-swfdec portname: graphics/ivtools broken because: Incomplete pkg-plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=ivtools portname: graphics/libvisual-plugins broken because: Broken objformat handling build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=libvisual-plugins portname: graphics/qgis broken because: Does not build with geos 3.x build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=qgis portname: graphics/ray++ broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=ray%2B%2B portname: irc/erc broken because: Conflicting dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=irc&portname=erc portname: irc/ircg broken because: Does not build with newer st build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/iRCG-2.7.log (Fri Nov 7 00:04:50 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=irc&portname=ircg portname: japanese/escpf broken because: Unfetchable build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/ja-escpf-0.4.log (Sat Jul 12 14:19:24 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=escpf portname: japanese/okphone broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=okphone portname: japanese/oleo broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=oleo portname: japanese/p5-Text-ChaSen broken because: does not install build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081128152658/ja-p5-Text-ChaSen-1.03_3.log (Sat Nov 29 18:16:42 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=p5-Text-ChaSen portname: japanese/plain2 broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=plain2 portname: japanese/tkstep80 broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=tkstep80 portname: java/cacao broken because: does not configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=cacao portname: java/dbvis broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=dbvis portname: java/eclipse-clay-core broken because: does not package build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=eclipse-clay-core portname: java/jakarta-commons-dbcp broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20081119214133/jakarta-commons-dbcp-1.2.1_2.log (Fri Nov 21 08:48:19 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=jakarta-commons-dbcp portname: java/java-gcj-compat broken because: leaves egg file behind on deinstall build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=java-gcj-compat portname: java/jboss5 broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20081106123942/jboss-5.0.0.cr1,1.log (Sat Nov 8 05:01:54 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=jboss5 portname: java/jdk14 broken because: Does not compile with GCC 4.2 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/jdk-1.4.2p8_13.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=jdk14 portname: java/openjit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=openjit portname: java/tya broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=tya portname: lang/chameleon broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=chameleon portname: lang/dylan broken because: does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=dylan portname: lang/gcl broken because: Gcl compiled with gcc42 dumps core build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=gcl portname: lang/hope broken because: Patch fails build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/hope-1.1.log (Sat Jul 12 14:22:59 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=hope portname: lang/mozart broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=mozart portname: lang/pfe-devel broken because: Does not compile with GCC 4.2 build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.6.20081122001658/pfe-0.32.94_1.log (Fri Nov 28 08:56:29 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pfe-devel portname: lang/pm3-base broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/pm3-base-1.1.15_2.log (Sat Jul 12 14:34:59 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-base portname: lang/pnet-base broken because: Bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pnet-base portname: lang/q broken because: bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=q portname: lang/qscheme broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=qscheme portname: lang/quack broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=quack portname: lang/screamer broken because: Does not compile (dumps core) build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/screamer-3.20.log (Sat Jul 12 14:19:50 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=screamer portname: lang/scriba broken because: Does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=scriba portname: lang/wamcc broken because: does not compile on 7.X build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=wamcc portname: lang/xsb broken because: Does not compile on FreeBSD 7.x build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=xsb portname: mail/claws-mail-clamav broken because: Doesn't build with clamav-0.93 or higher build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=claws-mail-clamav portname: mail/silkymail broken because: doesn't fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=silkymail portname: mail/sylpheed2-devel broken because: does not link build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=sylpheed2-devel portname: math/linalg broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=linalg portname: math/rascal broken because: Does not compile with GCC 4.2 build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.6.20081122001658/rascal-0.3.2_4.log (Fri Nov 28 09:06:59 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=rascal portname: math/rpy broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=rpy portname: math/ses broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=ses portname: misc/ipbt broken because: Size mismatch build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/ipbt-r7471.log (Sat Jul 12 14:17:24 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=ipbt portname: misc/pybliographer broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=pybliographer portname: multimedia/dvbcut broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.2007101601/dvbcut-0.5.4_2.log (Fri Sep 5 13:06:04 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=dvbcut portname: multimedia/helixplayer broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=helixplayer portname: multimedia/jahshaka broken because: does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=jahshaka portname: multimedia/mjpegtools-yuvfilters broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mjpegtools-yuvfilters portname: multimedia/mplayerxp broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mplayerxp portname: multimedia/mythtv broken because: Incorrect handling of user addition build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mythtv portname: multimedia/smilutils broken because: Does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.2007101601/smilutils-0.3.2_3.log (Fri Sep 5 12:41:20 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=smilutils portname: multimedia/smpeg-xmms broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=smpeg-xmms portname: multimedia/xmps-win32-plugin broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=xmps-win32-plugin portname: net-im/ginsu broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-im&portname=ginsu portname: net-im/sulci broken because: don't work with ocaml 3.10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-im&portname=sulci portname: net-mgmt/NeTraMet broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=NeTraMet portname: net-mgmt/nav broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=nav portname: net-mgmt/nfsen-devel broken because: fails to install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=nfsen-devel portname: net-p2p/py-kenosis-bittorrent broken because: fails to install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=py-kenosis-bittorrent portname: net/acx100 broken because: Does not compile on FreeBSD >= 6.x build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=acx100 portname: net/b2bua broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=b2bua portname: net/cap broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=cap portname: net/ggsd broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ggsd portname: net/globus4 broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=globus4 portname: net/gnometelnet broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=gnometelnet portname: net/isc-dhcp31-client broken because: Not yet integrated and tested build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=isc-dhcp31-client portname: net/isc-dhcp31-relay broken because: Not yet integrated and tested build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=isc-dhcp31-relay portname: net/isc-dhcp31-server broken because: Not yet integrated and tested build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=isc-dhcp31-server portname: net/libunpipc broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=libunpipc portname: net/openpbx.org broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=openpbx.org portname: net/p5-Parallel-MPI broken because: fails to link build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=p5-Parallel-MPI portname: net/py-mantissa broken because: Leaves files behind after deinstallation build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=py-mantissa portname: net/samba4wins broken because: Does not compile with GCC 4.2 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/samba4wins-1.0.6_1.log (Thu Sep 4 08:03:17 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=samba4wins portname: net/ssltunnel-client broken because: does not compile with OpenSSL 0.9.8b build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ssltunnel-client portname: net/versuch broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=versuch portname: net/vnc broken because: checksum mismatch build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20081111020653/vnc-4.1.2_5.log (Tue Nov 11 10:08:30 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=vnc portname: net/vserver broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=vserver portname: net/ztelnet broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ztelnet portname: news/inn-current broken because: Does not install (makedbz segfaults) build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/inn-current-20061024_1.log (Sat Jul 12 14:25:27 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=news&portname=inn-current portname: news/openftd broken because: Does not install build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.6.20081122001658/openftd-1.1.0_1.log (Fri Nov 28 09:09:21 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=news&portname=openftd portname: palm/pdbc broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=pdbc portname: palm/romeo broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=romeo portname: palm/synce-gnomevfs broken because: No longer supported by developers build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=synce-gnomevfs portname: palm/synce-kde broken because: No longer supported by developers build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=synce-kde portname: palm/synce-multisync broken because: No longer supported by developers build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=synce-multisync portname: ports-mgmt/barry broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ports-mgmt&portname=barry portname: print/ifhp broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=ifhp portname: print/kaspaliste broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=kaspaliste portname: print/perlftlib broken because: Does not build if devel/p5-ExUtils-CBuilder is installed build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=perlftlib portname: science/gerris broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=gerris portname: science/hdf broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=hdf portname: science/oof broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=oof portname: science/pcp broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=pcp portname: science/pnetcdf broken because: Does not configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=pnetcdf portname: security/dazuko broken because: Currently does not support FreeBSD > 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=dazuko portname: security/krb4 broken because: Incorrect pkg-plist on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=krb4 portname: security/newpki-lib broken because: does not compile with OpenSSL 0.9.8b build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=newpki-lib portname: security/newpki-server broken because: does not compile with OpenSSL 0.9.8b build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=newpki-server portname: security/opensaml broken because: Does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081128152658/opensaml-1.1.1_1.log (Sat Nov 29 18:13:15 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=opensaml portname: security/prelude-manager broken because: does not build with current lib build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=prelude-manager portname: security/shibboleth-sp broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=shibboleth-sp portname: security/squidclam broken because: Doesn't build with clamav-0.93 or higher build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=squidclam portname: security/xmlsec broken because: Does not compile on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=xmlsec portname: shells/zoidberg broken because: does not package build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20081119214133/zoidberg-0.96.log (Fri Nov 7 18:59:47 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=zoidberg portname: sysutils/dtc broken because: bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=dtc portname: sysutils/dtc-toaster broken because: bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=dtc-toaster portname: sysutils/dusage broken because: Unfetchable build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/dusage-19900227.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=dusage portname: sysutils/linux-megacli broken because: Unfetchable build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20081111020653/linux-megacli-1.01.40_1.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=linux-megacli portname: sysutils/perf broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=perf portname: sysutils/quicksynergy broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=quicksynergy portname: sysutils/sjog broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=sjog portname: sysutils/upsdaemon broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=upsdaemon portname: sysutils/xwipower broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=xwipower portname: sysutils/xwlans broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=xwlans portname: textproc/Ebnf2ps broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=Ebnf2ps portname: textproc/dixit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=dixit portname: textproc/htmlize.el broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=htmlize.el portname: textproc/opensched broken because: Does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=opensched portname: www/bk_edit broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=bk_edit portname: www/c-icap broken because: Doesn't build with clamav-0.93 or higher build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=c-icap portname: www/cacheboy broken because: leaves leftover binary after deinstall build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/cacheboy-1.4.1_12.log (Thu Sep 4 07:59:04 UTC 2008) http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20081130033632/cacheboy-1.4.1_12.log (Wed Sep 24 10:59:26 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=cacheboy portname: www/cybercalendar broken because: does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=cybercalendar portname: www/geneweb broken because: does not build with new ocaml build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/geneweb-4.10_4.log (Sat Jul 12 14:21:44 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=geneweb portname: www/gforge broken because: bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=gforge portname: www/mod_webapp broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20081106084257/mod_webapp-4.1.24_2.log (Fri Nov 7 21:10:46 UTC 2008) http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20081130033632/mod_webapp-4.1.24_2.log (Fri Oct 3 06:48:31 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=mod_webapp portname: www/ocaml-wdialog broken because: does not build with new ocaml build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=ocaml-wdialog portname: www/ocsigen broken because: unsatisfiable dependency line build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=ocsigen portname: www/pecl-mnogosearch broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=pecl-mnogosearch portname: www/py-nevow broken because: doesn't build: in nevow/static.py", line 18, twisted.web import error build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=py-nevow portname: www/roxen broken because: does not configure build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/roxen-2.1.231.log (Sat Jul 12 14:16:16 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=roxen portname: www/rt3 broken because: Broken due the new mod_perl2 API build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=rt3 portname: www/rt32 broken because: Broken due the new mod_perl2 API build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=rt32 portname: www/toofpy broken because: Installs files outside of localbase build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=toofpy portname: www/wb0 broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=wb0 portname: www/winhelpcgi broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=winhelpcgi portname: x11-drivers/xf86-video-i810 broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.8.20080904173358/xf86-video-i810-1.7.4_1.log (Sat Sep 6 12:27:02 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-drivers&portname=xf86-video-i810 portname: x11-fm/evidence broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-fm&portname=evidence portname: x11-fm/velocity broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-fm&portname=velocity portname: x11-themes/camaelon-nesedah broken because: conflicts with its own dependency build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-themes&portname=camaelon-nesedah portname: x11-themes/gtk-industrial-theme broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-themes&portname=gtk-industrial-theme portname: x11-toolkits/flu broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=flu portname: x11-toolkits/fox10 broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=fox10 portname: x11-toolkits/fxscintilla-fox10 broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=fxscintilla-fox10 portname: x11-toolkits/p5-Gnome broken because: fails to install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-Gnome portname: x11-toolkits/p5-qt broken because: Configure fails build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-qt portname: x11-toolkits/wxmozilla broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=wxmozilla portname: x11-wm/alloywm broken because: Checksum mismatch build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/alloywm-0.4.0_4.log (Sat Jul 12 14:19:21 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=alloywm portname: x11-wm/fluxspace broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=fluxspace portname: x11-wm/kahakai broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=kahakai portname: x11/9term broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=9term portname: x11/bbuname broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=bbuname From linimon at FreeBSD.org Wed Dec 3 21:24:09 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Dec 3 21:24:19 2008 Subject: FreeBSD unmaintained ports which are currently scheduled for deletion Message-ID: <20081204052407.B51EA1CCD8@mail.droso.net> As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: audio/q-audio description: Q-Audio -- digital audio interface for the Q language maintainer: ports@FreeBSD.org deprecated because: depends on deprecated port lang/q expiration date: 2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=q-audio portname: devel/p5-Getopt-Mixed description: Perl module for processing of both short and long command line options maintainer: ports@FreeBSD.org deprecated because: Use devel/p5-Getopt-Long instead expiration date: 2007-04-23 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-Getopt-Mixed portname: devel/pear-apd description: A full-featured engine-level PHP profiler/debugger maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=pear-apd portname: editors/sam description: A unix version of Rob Pike's editor for plan9 maintainer: ports@FreeBSD.org deprecated because: distfile and homepage disappeared expiration date: 2007-01-04 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=sam portname: games/clanbomber description: A bomberman-like multiplayer game maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=clanbomber portname: graphics/q-graph description: Q-Graph -- graph library and editor for the Q language maintainer: ports@FreeBSD.org deprecated because: depends on deprecated port lang/q expiration date: 2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=q-graph portname: irc/erc description: ERC is an Emacs InternetRelayChat client maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=irc&portname=erc portname: lang/pm3-base description: Compiler and base libs of Polytechnique Montreal Modula-3 distribution maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/pm3-base-1.1.15_2.log (Sat Jul 12 14:34:59 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-base portname: lang/q description: Q -- equational programming language maintainer: ports@FreeBSD.org status: BROKEN deprecated because: old version, broken plist expiration date: 2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=q portname: lang/screamer description: Extension of Common Lisp for nondeterministic programming maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/screamer-3.20.log (Sat Jul 12 14:19:50 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=screamer portname: math/ses description: Simple Emacs Spreadsheet maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=ses portname: misc/documancer description: A programmer's documentation reader maintainer: ports@FreeBSD.org deprecated because: Unmaintained upstream expiration date: 2008-10-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=documancer portname: multimedia/mythtv description: MythTV is a homebrew PVR project maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mythtv portname: net-p2p/py-kenosis-bittorrent description: A Kenosis enabled, distributed BitTorrent maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=py-kenosis-bittorrent portname: net/p54u description: Driver for USB wireless devices with Conexant (Prism 54) chipsets maintainer: ports@FreeBSD.org deprecated because: website disappeared expiration date: 2008-01-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=p54u portname: palm/synce-kde description: SynCE KDE Utilities maintainer: ports@FreeBSD.org status: BROKEN deprecated because: No longer supported by developers expiration date: 2008-08-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=synce-kde portname: palm/synce-multisync description: SynCE synchronisation plugin for Multisync maintainer: ports@FreeBSD.org status: BROKEN deprecated because: No longer supported by developers expiration date: 2008-08-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=synce-multisync portname: sysutils/sjog description: Userland daemon for Sony Vaio Jog Dial maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=sjog portname: textproc/Ebnf2ps description: Generate EPS/FIG diagrams from EBNF/yacc/bison grammars maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=Ebnf2ps portname: x11-toolkits/p5-Gnome description: The main Gnome module of Gtk-Perl maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-Gnome portname: x11-toolkits/p5-qt description: A set of Perl bindings for the Qt toolkit maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-qt portname: x11-toolkits/py-fox description: Python interface to FOX Graphics library maintainer: ports@FreeBSD.org deprecated because: depends on deprecated port x11-toolkits/fox10 expiration date: 2009-01-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=py-fox portname: x11-toolkits/scx description: A GUI library for scsh and Scheme 48 maintainer: ports@FreeBSD.org deprecated because: Version branch long since retired expiration date: 2007-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=scx portname: x11-toolkits/xclasses description: C++ layout library for X maintainer: ports@FreeBSD.org deprecated because: Version branch long since retired expiration date: 2007-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=xclasses portname: x11-toolkits/xg description: Windows(tm) controls - like widget set for Motif(tm) maintainer: ports@FreeBSD.org deprecated because: Project is dead, last release from 1998 expiration date: 2007-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=xg portname: x11-wm/alloywm description: Has title bars, shading, resizing, automatic placement, window list maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/alloywm-0.4.0_4.log (Sat Jul 12 14:19:21 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=alloywm portname: x11-wm/flwm description: The Fast Light Window Manager maintainer: ports@FreeBSD.org deprecated because: Project is dead, and uses obsolete version of fltk expiration date: 2008-10-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=flwm portname: x11-wm/kahakai description: Kahakai window manager maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Development ceased expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=kahakai portname: x11/9term description: An X11 program which emulates a plan9 window maintainer: ports@FreeBSD.org status: BROKEN deprecated because: depends on expired port expiration date: 2008-07-18 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=9term From linimon at FreeBSD.org Wed Dec 3 21:24:19 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Dec 3 21:24:37 2008 Subject: FreeBSD ports which are currently scheduled for deletion Message-ID: <20081204052416.CAFD41CD2E@mail.droso.net> As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: audio/q-audio description: Q-Audio -- digital audio interface for the Q language maintainer: ports@FreeBSD.org deprecated because: depends on deprecated port lang/q expiration date: 2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=q-audio portname: audio/ruby-xmms2-ecore description: Ruby ecore mainloop bindings for XMMS2 maintainer: alexbl@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ruby-xmms2-ecore portname: audio/shellac description: Shellac is a PyGTK XMMS2 Client maintainer: alexbl@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=shellac portname: audio/snett description: A simple XMMS2 client inspired by strange-quark maintainer: alexbl@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=snett portname: databases/firebird-client description: The open-source InterBase(tm) 6.0 spin-off (client) maintainer: skv@FreeBSD.org status: IGNORE deprecated because: no longer under development, please consider using Firebird2 expiration date: 2009-02-24 build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081202081507/firebird-client-1.5.5.log (Tue Dec 2 09:49:26 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=firebird-client portname: databases/firebird-server description: The open-source InterBase(tm) 6.0 spin-off (Classic version) maintainer: skv@FreeBSD.org status: IGNORE deprecated because: no longer under development, please consider using Firebird2 expiration date: 2009-02-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=firebird-server portname: databases/mysql-query-browser description: A database querying tool for MySQL servers maintainer: pgollucci@FreeBSD.org status: BROKEN deprecated because: has been BROKEN for more than six months expiration date: 2008-11-04 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=mysql-query-browser portname: databases/p5-DBD-PgSPI description: Provides access to PostgreSQL db through DBI within pl/perl functions maintainer: mat@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=p5-DBD-PgSPI portname: databases/py-tada description: Twisted Asynchronous Database API maintainer: clive@darkarts.co.za status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=py-tada portname: databases/qdbm-java description: Java API for QDBM maintainer: ahze@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=qdbm-java portname: devel/hs-buddha description: A declarative debugger for Haskell 98 maintainer: haskell@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hs-buddha portname: devel/hs-tclhaskell-ghc description: Tcl/Tk binding for Haskell maintainer: haskell@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hs-tclhaskell-ghc portname: devel/p5-Getopt-Mixed description: Perl module for processing of both short and long command line options maintainer: ports@FreeBSD.org deprecated because: Use devel/p5-Getopt-Long instead expiration date: 2007-04-23 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-Getopt-Mixed portname: devel/pear-apd description: A full-featured engine-level PHP profiler/debugger maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=pear-apd portname: dns/bind9-dlz description: The Berkeley Internet Name Daemon, with DLZ extensions maintainer: dinoex@FreeBSD.org status: FORBIDDEN deprecated because: expiration date: 2008-08-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=dns&portname=bind9-dlz portname: editors/sam description: A unix version of Rob Pike's editor for plan9 maintainer: ports@FreeBSD.org deprecated because: distfile and homepage disappeared expiration date: 2007-01-04 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=sam portname: games/clanbomber description: A bomberman-like multiplayer game maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=clanbomber portname: games/linux-alienarena description: Alien Arena 2006 (Linux version) maintainer: alepulver@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=linux-alienarena portname: graphics/crystalspace-devel description: Free and portable 3D Game Development Kit maintainer: acm@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=crystalspace-devel portname: graphics/gstreamer-plugins-swfdec description: Gstreamer flash redering plugin maintainer: multimedia@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=gstreamer-plugins-swfdec portname: graphics/q-graph description: Q-Graph -- graph library and editor for the Q language maintainer: ports@FreeBSD.org deprecated because: depends on deprecated port lang/q expiration date: 2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=q-graph portname: irc/erc description: ERC is an Emacs InternetRelayChat client maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=irc&portname=erc portname: japanese/escpf description: Text filters for ESC/P, ESC/Page and ESC/PS printers maintainer: mita@jp.FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/ja-escpf-0.4.log (Sat Jul 12 14:19:24 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=escpf portname: java/java-gcj-compat description: A collection of wrapper scripts, symlinks and jar files for GCJ maintainer: maho@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=java-gcj-compat portname: lang/chameleon description: A Haskell-style language maintainer: haskell@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=chameleon portname: lang/hope description: Hope is lazy interpriter for HOPE applicative language maintainer: lev@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/hope-1.1.log (Sat Jul 12 14:22:59 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=hope portname: lang/pm3-base description: Compiler and base libs of Polytechnique Montreal Modula-3 distribution maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/pm3-base-1.1.15_2.log (Sat Jul 12 14:34:59 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-base portname: lang/q description: Q -- equational programming language maintainer: ports@FreeBSD.org status: BROKEN deprecated because: old version, broken plist expiration date: 2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=q portname: lang/screamer description: Extension of Common Lisp for nondeterministic programming maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/screamer-3.20.log (Sat Jul 12 14:19:50 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=screamer portname: math/ses description: Simple Emacs Spreadsheet maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=ses portname: misc/documancer description: A programmer's documentation reader maintainer: ports@FreeBSD.org deprecated because: Unmaintained upstream expiration date: 2008-10-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=documancer portname: misc/heyu description: Control a CM11A interface from the command line maintainer: mstowe@chicago.us.mensa.org deprecated because: no longer under development, use misc/heyu2 expiration date: 2008-12-06 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=heyu portname: misc/ipbt description: A high-tech ttyrec player with improvements over ttyplay maintainer: matt_mills@btopenworld.com status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/ipbt-r7471.log (Sat Jul 12 14:17:24 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=ipbt portname: multimedia/manslide description: Utility to simply create your own slideshow maintainer: trebestie@gmail.com deprecated because: Use multimedia/smile instead expiration date: 2008-10-13 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=manslide portname: multimedia/mythtv description: MythTV is a homebrew PVR project maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mythtv portname: net-im/ginsu description: A client for the gale secure instant messaging system maintainer: jason-fbsd-ports-ginsu@shalott.net status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-im&portname=ginsu portname: net-p2p/py-kenosis-bittorrent description: A Kenosis enabled, distributed BitTorrent maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=py-kenosis-bittorrent portname: net/acx100 description: Texas Instruments (TI) ACX100 IEEE 802.11 driver maintainer: leoz.2005@gmail.com status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=acx100 portname: net/globus4 description: Grid computing toolkit maintainer: brooks@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=globus4 portname: net/p5-Parallel-MPI description: Perl interface to the MPI message passing system maintainer: skv@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=p5-Parallel-MPI portname: net/p54u description: Driver for USB wireless devices with Conexant (Prism 54) chipsets maintainer: ports@FreeBSD.org deprecated because: website disappeared expiration date: 2008-01-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=p54u portname: news/sabnzbd description: A web-interface based binary newsgrabber in python, with nzb support maintainer: daniel@netwalk.org deprecated because: no longer developed, use news/sabnzbdplus instead expiration date: 2008-12-21 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=news&portname=sabnzbd portname: palm/synce-gnomevfs description: Gnome VFS module for WinCE devices maintainer: ports@logvinov.com status: BROKEN deprecated because: No longer supported by developers expiration date: 2008-08-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=synce-gnomevfs portname: palm/synce-kde description: SynCE KDE Utilities maintainer: ports@FreeBSD.org status: BROKEN deprecated because: No longer supported by developers expiration date: 2008-08-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=synce-kde portname: palm/synce-multisync description: SynCE synchronisation plugin for Multisync maintainer: ports@FreeBSD.org status: BROKEN deprecated because: No longer supported by developers expiration date: 2008-08-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=synce-multisync portname: security/openssl-stable description: SSL and crypto library maintainer: dinoex@FreeBSD.org status: IGNORE deprecated because: expiration date: 2008-11-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=openssl-stable portname: security/xyssl description: A liteweight SSL and TLS toolkit for C developers maintainer: mattdharris@users.sourceforge.net deprecated because: Download sites are down, cannot update due to software website being down. expiration date: 2008-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=xyssl portname: shells/ksh93-devel description: Official AT&T Beta release of KornShell 93 maintainer: joe@zircon.seattle.wa.us deprecated because: This port is Outdated. Please use shells/ksh93 expiration date: 2008-12-06 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=ksh93-devel portname: sysutils/dtc-toaster description: A hosting web GUI for admin and accounting all hosting services maintainer: thomas@goirand.fr status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=dtc-toaster portname: sysutils/dusage description: Report about disk space in use, change since last run, etc maintainer: CPE1704TKS@bellsouth.net status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081111095232/dusage-19900227.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=dusage portname: sysutils/sjog description: Userland daemon for Sony Vaio Jog Dial maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=sjog portname: textproc/Ebnf2ps description: Generate EPS/FIG diagrams from EBNF/yacc/bison grammars maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=Ebnf2ps portname: textproc/p5-Text-CSV_PP description: Comma-separated values manipulation routines PP version maintainer: perl@FreeBSD.org deprecated because: textproc/Text-CSV_PP was merged into textproc/p5-Text-CSV expiration date: 2008-12-11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=p5-Text-CSV_PP portname: textproc/py-wbxml description: Python bindings for the wbxml2 library maintainer: ports@logvinov.com deprecated because: No longer supported by developers expiration date: 2009-01-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=py-wbxml portname: www/roxen description: The Roxen WebServer 2.1 maintainer: k@123.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/roxen-2.1.231.log (Sat Jul 12 14:16:16 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=roxen portname: www/squid26 description: HTTP Caching Proxy maintainer: tmseck@web.de deprecated because: The 2.6 series is no longer actively maintained by the Squid developers expiration date: 2009-03-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=squid26 portname: www/zope-btreefolder2 description: Zope product that can store many items maintainer: kaeru@inigo-tech.com deprecated because: Included in Zope 2.8 and later expiration date: 2007-08-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=zope-btreefolder2 portname: x11-fm/evidence description: Enlightened file-manager maintainer: freebsd@troback.com status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-fm&portname=evidence portname: x11-toolkits/fox10 description: Fast and extensive C++ GUI toolkit maintainer: araujo@FreeBSD.org status: BROKEN deprecated because: does not compile with latest gcc; use x11-toolkits/fox16 instead expiration date: 2009-01-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=fox10 portname: x11-toolkits/fxscintilla-fox10 description: A Fox toolkit reimplementation of Scintilla editing widget maintainer: araujo@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=fxscintilla-fox10 portname: x11-toolkits/p5-Gnome description: The main Gnome module of Gtk-Perl maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-Gnome portname: x11-toolkits/p5-qt description: A set of Perl bindings for the Qt toolkit maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-qt portname: x11-toolkits/py-fox description: Python interface to FOX Graphics library maintainer: ports@FreeBSD.org deprecated because: depends on deprecated port x11-toolkits/fox10 expiration date: 2009-01-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=py-fox portname: x11-toolkits/ruby-fox10 description: Ruby extension module to use FOX, aka FXRuby maintainer: araujo@FreeBSD.org deprecated because: depends on deprecated port x11-toolkits/fox10 expiration date: 2009-01-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=ruby-fox10 portname: x11-toolkits/scx description: A GUI library for scsh and Scheme 48 maintainer: ports@FreeBSD.org deprecated because: Version branch long since retired expiration date: 2007-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=scx portname: x11-toolkits/xclasses description: C++ layout library for X maintainer: ports@FreeBSD.org deprecated because: Version branch long since retired expiration date: 2007-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=xclasses portname: x11-toolkits/xg description: Windows(tm) controls - like widget set for Motif(tm) maintainer: ports@FreeBSD.org deprecated because: Project is dead, last release from 1998 expiration date: 2007-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=xg portname: x11-wm/alloywm description: Has title bars, shading, resizing, automatic placement, window list maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081122122931/alloywm-0.4.0_4.log (Sat Jul 12 14:19:21 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=alloywm portname: x11-wm/flwm description: The Fast Light Window Manager maintainer: ports@FreeBSD.org deprecated because: Project is dead, and uses obsolete version of fltk expiration date: 2008-10-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=flwm portname: x11-wm/kahakai description: Kahakai window manager maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Development ceased expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=kahakai portname: x11/9term description: An X11 program which emulates a plan9 window maintainer: ports@FreeBSD.org status: BROKEN deprecated because: depends on expired port expiration date: 2008-07-18 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=9term From linimon at FreeBSD.org Wed Dec 3 21:24:21 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Dec 3 21:24:38 2008 Subject: FreeBSD unmaintained ports which are currently marked forbidden Message-ID: <20081204052421.49E321CD35@mail.droso.net> As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: chinese/wordpress forbidden because: http://www.vuxml.org/freebsd/622bc638-be27-11dd-a578-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=wordpress portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: www/linux-firefox-devel forbidden because: Security issus http://www.vuxml.org/freebsd/f29fea8f-b19f-11dd-a55e-00163e000016.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-firefox-devel From linimon at FreeBSD.org Wed Dec 3 21:24:22 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Dec 3 21:24:38 2008 Subject: FreeBSD ports which are currently marked forbidden Message-ID: <20081204052422.2A25E1CC70@mail.droso.net> As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: chinese/wordpress forbidden because: http://www.vuxml.org/freebsd/622bc638-be27-11dd-a578-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=wordpress portname: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: dns/bind9-dlz forbidden because: vulnerable to cache poisioning if recursive lookup enabled build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=dns&portname=bind9-dlz portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: net-p2p/peercast forbidden because: arbitrary code execution, http://www.vuxml.org/freebsd/402ae710-26a2-11dd-ae05-825f4c35000a.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=peercast portname: www/linux-firefox-devel forbidden because: Security issus http://www.vuxml.org/freebsd/f29fea8f-b19f-11dd-a55e-00163e000016.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-firefox-devel portname: www/tdiary-devel forbidden because: contains a vulnerability: http://www.tdiary.org/20071215.html written in Japanese build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=tdiary-devel portname: www/zope forbidden because: contains cross-site scripting vulnerability http://VuXML.FreeBSD.org/34414a1e-e377-11db-b8ab-000c76189c4c.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=zope From leslie at eskk.nu Wed Dec 3 23:16:22 2008 From: leslie at eskk.nu (Leslie Jensen) Date: Wed Dec 3 23:16:28 2008 Subject: Installing kdebase-4.1.1 or kdebase-workspace-4.1.1 Message-ID: <49378069.4010907@eskk.nu> Hi I wondering what's the difference between these two ports? Thanks /Leslie From pz-freebsd-ports at ziemba.us Thu Dec 4 00:13:41 2008 From: pz-freebsd-ports at ziemba.us (G. Paul Ziemba) Date: Thu Dec 4 00:13:47 2008 Subject: Proposal: mechanism for local patches References: <20081203131234.GD70240@hades.panopticon> Message-ID: amdmi3@amdmi3.ru (Dmitry Marakasov) writes: >> 1. Good that it's at the end of the do-patch target - that way local >> patches can happen after the "official" patches >Not sure if it's good actually. >On the one hand, you usually have patches against vanilla sources, and >just want to drop them to some dir and have them applied. >Also, there's USE_DOS2UNIX that comes before any actual patching, so for >ports that use USE_DOS2UNIX you'll have to adapt patches by hand. >On the other hand, this may cause conflicts with patches from ports, If the local patches were applied before the official ports patches, the official patches could fail, or they could undo some of the modifications made by local patches. I think it would be an incorrect result. >From the point of view of the local patches, there is potential for variation in the upstream files regardless of whether they are modified by official ports patches, so doing local patching first doesn't let you avoid tweaking local patches from time to time. >Updated version here: >http://people.freebsd.org/~amdmi3/local-patchdir.patch It looks good to me. Thanks! -- G. Paul Ziemba FreeBSD unix: 12:11AM up 3 days, 9:41, 12 users, load averages: 0.42, 0.40, 0.37 From silver.salonen at gmail.com Thu Dec 4 00:21:53 2008 From: silver.salonen at gmail.com (Silver Salonen) Date: Thu Dec 4 00:22:00 2008 Subject: cmake cannot link against libxml++ Message-ID: <20828880.post@talk.nabble.com> Hello. I created a port for Museek+ which is built with cmake now. The problem is that although it gets built OK, cmake cannot link one of its executables against libxml++: ===== ... [100%] Building CXX object museekd/CMakeFiles/museekd.dir/distributedsocket.cpp.o Linking CXX executable museekd /usr/bin/ld: cannot find -lxml++-2.6 *** Error code 1 ===== Concerning libxml++, cmake seems to find it OK - before building: ===== -- checking for one of the modules 'libxml++-2.6' -- found libxml++-2.6, version 2.22.0 ===== Previously I had a problem with cmake finding libiconv.h, but I resolved it with "CMAKE_ARGS+= -DCMAKE_REQUIRED_INCLUDES="${LOCALBASE}/include". But I guess it's irrelevant and not even similar. Is there anything to be specified in order to cmake to find libxml++ correctly? -- View this message in context: http://www.nabble.com/cmake-cannot-link-against-libxml%2B%2B-tp20828880p20828880.html Sent from the freebsd-ports mailing list archive at Nabble.com. From admin at lissyara.su Thu Dec 4 00:42:05 2008 From: admin at lissyara.su (Alex Keda) Date: Thu Dec 4 00:42:17 2008 Subject: after last update xmms get all processor resourses Message-ID: <493792CF.1010805@lissyara.su> subj. last pid: 2718; load averages: 0.87, 1.08, 1.15 up 0+18:02:08 11:17:45 134 processes: 4 running, 130 sleeping CPU: 9.7% user, 0.0% nice, 49.8% system, 1.9% interrupt, 38.6% idle Mem: 398M Active, 730M Inact, 414M Wired, 488K Cache, 194M Buf, 307M Free Swap: 905M Total, 905M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 2669 lissyara 3 44 0 73452K 12288K select 0 0:31 92.19% xmms ============== lissyara$ uname -a FreeBSD lissyara.moskb.local 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri Nov 28 13:20:28 MSK 2008 lissyara@lissyara.moskb.local:/usr/obj/mnt/jabber/DISTR/FreeBSD/src/CURRENT/sys/GENERIC amd64 lissyara$ pkg_info | grep xmms librcc-0.2.6_1 Library used by rusxmms for language autodetection librcd-0.1.11 Library used by rusxmms for autodetection of russian charse xmms-1.2.11_4 X Multimedia System -- An audio player with Winamp GUI xmms-kde-3.2_4 Integrates XMMS into the KDE3 Panel xmms-skins-0.1_3 Skins for X Multimedia System (XMMS) lissyara$ From yanefbsd at gmail.com Thu Dec 4 01:40:09 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Dec 4 01:40:15 2008 Subject: Proposal: mechanism for local patches In-Reply-To: References: <20081203131234.GD70240@hades.panopticon> Message-ID: <7d6fde3d0812040140i44ec44bdw529b625674417949@mail.gmail.com> On Thu, Dec 4, 2008 at 12:13 AM, G. Paul Ziemba wrote: > amdmi3@amdmi3.ru (Dmitry Marakasov) writes: >>> 1. Good that it's at the end of the do-patch target - that way local >>> patches can happen after the "official" patches > >>Not sure if it's good actually. > >>On the one hand, you usually have patches against vanilla sources, and >>just want to drop them to some dir and have them applied. >>Also, there's USE_DOS2UNIX that comes before any actual patching, so for >>ports that use USE_DOS2UNIX you'll have to adapt patches by hand. > >>On the other hand, this may cause conflicts with patches from ports, > > If the local patches were applied before the official ports patches, > the official patches could fail, or they could undo some of the > modifications made by local patches. I think it would be an incorrect > result. > > >From the point of view of the local patches, there is potential for > variation in the upstream files regardless of whether they are > modified by official ports patches, so doing local patching first > doesn't let you avoid tweaking local patches from time to time. > >>Updated version here: >>http://people.freebsd.org/~amdmi3/local-patchdir.patch > > It looks good to me. Thanks! FreeBSD maintained patches can change at any instant a developer makes a commit to the ports tree, so doing either a vanilla patch or a patch after a patch will require some level of rework, regardless. One thing though -- I think that if this item does get supported it should be noted that while the FreeBSD project supports the patching functionality, they shouldn't be in charge of the patches. I know most users / admins would understand this point clearly, but it needs to be made apparent in the port distfiles, or using some method, that an individual is using self-patched and maintained sources. Gentoo Linux uses the concept of portage overlays to deal with this issue, but I'm not sure if that's the best method to approach this problem with, as our ports system isn't yet adapted to this level of thinking, and since we don't have a means of masking port versions today (mind you -- I'm not really suggesting that this should be done -- version masking and arch masking is a real maintenance nightmare for the support groups and we have enough fun dealing with our ports tree :)..). My 2 cents, -Garrett From yanefbsd at gmail.com Thu Dec 4 01:41:56 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Dec 4 01:42:03 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <7d6fde3d0812040140i44ec44bdw529b625674417949@mail.gmail.com> References: <20081203131234.GD70240@hades.panopticon> <7d6fde3d0812040140i44ec44bdw529b625674417949@mail.gmail.com> Message-ID: <7d6fde3d0812040141i45957174w1cf1ff95c25e6bde@mail.gmail.com> On Thu, Dec 4, 2008 at 1:40 AM, Garrett Cooper wrote: > On Thu, Dec 4, 2008 at 12:13 AM, G. Paul Ziemba > wrote: >> amdmi3@amdmi3.ru (Dmitry Marakasov) writes: >>>> 1. Good that it's at the end of the do-patch target - that way local >>>> patches can happen after the "official" patches >> >>>Not sure if it's good actually. >> >>>On the one hand, you usually have patches against vanilla sources, and >>>just want to drop them to some dir and have them applied. >>>Also, there's USE_DOS2UNIX that comes before any actual patching, so for >>>ports that use USE_DOS2UNIX you'll have to adapt patches by hand. >> >>>On the other hand, this may cause conflicts with patches from ports, >> >> If the local patches were applied before the official ports patches, >> the official patches could fail, or they could undo some of the >> modifications made by local patches. I think it would be an incorrect >> result. >> >> >From the point of view of the local patches, there is potential for >> variation in the upstream files regardless of whether they are >> modified by official ports patches, so doing local patching first >> doesn't let you avoid tweaking local patches from time to time. >> >>>Updated version here: >>>http://people.freebsd.org/~amdmi3/local-patchdir.patch >> >> It looks good to me. Thanks! > > FreeBSD maintained patches can change at any instant a developer makes > a commit to the ports tree, so doing either a vanilla patch or a patch > after a patch will require some level of rework, regardless. > > One thing though -- I think that if this item does get supported it > should be noted that while the FreeBSD project supports the patching > functionality, they shouldn't be in charge of the patches. I know most > users / admins would understand this point clearly, but it needs to be > made apparent in the port distfiles, or using some method, that an > individual is using self-patched and maintained sources. Just to clarify: s/be in charge of patches/be expected to support patching issues/ > Gentoo Linux uses the concept of portage overlays to deal with this > issue, but I'm not sure if that's the best method to approach this > problem with, as our ports system isn't yet adapted to this level of > thinking, and since we don't have a means of masking port versions > today (mind you -- I'm not really suggesting that this should be done > -- version masking and arch masking is a real maintenance nightmare > for the support groups and we have enough fun dealing with our ports > tree :)..). > > My 2 cents, > -Garrett -Garrett From yanefbsd at gmail.com Thu Dec 4 01:43:47 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Dec 4 01:43:54 2008 Subject: cmake cannot link against libxml++ In-Reply-To: <20828880.post@talk.nabble.com> References: <20828880.post@talk.nabble.com> Message-ID: <7d6fde3d0812040143n374c63edyead7aa4f44e7c0f1@mail.gmail.com> On Thu, Dec 4, 2008 at 12:02 AM, Silver Salonen wrote: > > Hello. > > I created a port for Museek+ which is built with cmake now. The problem is > that although it gets built OK, cmake cannot link one of its executables > against libxml++: > ===== > ... [100%] Building CXX object > museekd/CMakeFiles/museekd.dir/distributedsocket.cpp.o Linking CXX > executable museekd /usr/bin/ld: cannot find -lxml++-2.6 *** Error code 1 > ===== > > Concerning libxml++, cmake seems to find it OK - before building: > ===== > -- checking for one of the modules 'libxml++-2.6' -- found libxml++-2.6, > version 2.22.0 > ===== > > Previously I had a problem with cmake finding libiconv.h, but I resolved it > with "CMAKE_ARGS+= -DCMAKE_REQUIRED_INCLUDES="${LOCALBASE}/include". But > I guess it's irrelevant and not even similar. > > Is there anything to be specified in order to cmake to find libxml++ > correctly? 1. Does /usr/local/lib/libxml++-2.6.a and/or /usr/local/lib/libxml++-2.6.so exist? 2. What are your CXXFLAGS / LDFLAGS? -Garrett From yanefbsd at gmail.com Thu Dec 4 02:00:39 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Dec 4 02:00:46 2008 Subject: after last update xmms get all processor resourses In-Reply-To: <493792CF.1010805@lissyara.su> References: <493792CF.1010805@lissyara.su> Message-ID: <7d6fde3d0812040200q647f21f9jb019892c3a47cb30@mail.gmail.com> On Thu, Dec 4, 2008 at 12:20 AM, Alex Keda wrote: > subj. > > last pid: 2718; load averages: 0.87, 1.08, 1.15 up 0+18:02:08 > 11:17:45 > 134 processes: 4 running, 130 sleeping > CPU: 9.7% user, 0.0% nice, 49.8% system, 1.9% interrupt, 38.6% idle > Mem: 398M Active, 730M Inact, 414M Wired, 488K Cache, 194M Buf, 307M Free > Swap: 905M Total, 905M Free > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 2669 lissyara 3 44 0 73452K 12288K select 0 0:31 92.19% xmms > ============== > lissyara$ uname -a > FreeBSD lissyara.moskb.local 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri Nov 28 > 13:20:28 MSK 2008 > lissyara@lissyara.moskb.local:/usr/obj/mnt/jabber/DISTR/FreeBSD/src/CURRENT/sys/GENERIC > amd64 > > lissyara$ pkg_info | grep xmms > librcc-0.2.6_1 Library used by rusxmms for language autodetection > librcd-0.1.11 Library used by rusxmms for autodetection of russian > charse > xmms-1.2.11_4 X Multimedia System -- An audio player with Winamp GUI > xmms-kde-3.2_4 Integrates XMMS into the KDE3 Panel > xmms-skins-0.1_3 Skins for X Multimedia System (XMMS) Could you start up xmms via strace or truss in a terminal and provide output on pastebin.com please? Thanks, -Garrett From admin at lissyara.su Thu Dec 4 02:17:51 2008 From: admin at lissyara.su (Alex Keda) Date: Thu Dec 4 02:18:04 2008 Subject: after last update xmms get all processor resourses In-Reply-To: <7d6fde3d0812040200q647f21f9jb019892c3a47cb30@mail.gmail.com> References: <493792CF.1010805@lissyara.su> <7d6fde3d0812040200q647f21f9jb019892c3a47cb30@mail.gmail.com> Message-ID: <4937AE4C.8090203@lissyara.su> Garrett Cooper ?????: > On Thu, Dec 4, 2008 at 12:20 AM, Alex Keda wrote: > >> subj. >> >> last pid: 2718; load averages: 0.87, 1.08, 1.15 up 0+18:02:08 >> 11:17:45 >> 134 processes: 4 running, 130 sleeping >> CPU: 9.7% user, 0.0% nice, 49.8% system, 1.9% interrupt, 38.6% idle >> Mem: 398M Active, 730M Inact, 414M Wired, 488K Cache, 194M Buf, 307M Free >> Swap: 905M Total, 905M Free >> >> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND >> 2669 lissyara 3 44 0 73452K 12288K select 0 0:31 92.19% xmms >> ============== >> lissyara$ uname -a >> FreeBSD lissyara.moskb.local 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri Nov 28 >> 13:20:28 MSK 2008 >> lissyara@lissyara.moskb.local:/usr/obj/mnt/jabber/DISTR/FreeBSD/src/CURRENT/sys/GENERIC >> amd64 >> >> lissyara$ pkg_info | grep xmms >> librcc-0.2.6_1 Library used by rusxmms for language autodetection >> librcd-0.1.11 Library used by rusxmms for autodetection of russian >> charse >> xmms-1.2.11_4 X Multimedia System -- An audio player with Winamp GUI >> xmms-kde-3.2_4 Integrates XMMS into the KDE3 Panel >> xmms-skins-0.1_3 Skins for X Multimedia System (XMMS) >> > > Could you start up xmms via strace or truss in a terminal and provide > output on pastebin.com please? > Thanks, > -Garrett > > very big. pastebin.com give 500 error =) http://lissyara.su/patch/xmms/typescript.txt From silver.salonen at gmail.com Thu Dec 4 02:21:00 2008 From: silver.salonen at gmail.com (Silver Salonen) Date: Thu Dec 4 02:21:07 2008 Subject: cmake cannot link against libxml++ In-Reply-To: <7d6fde3d0812040143n374c63edyead7aa4f44e7c0f1@mail.gmail.com> References: <20828880.post@talk.nabble.com> <7d6fde3d0812040143n374c63edyead7aa4f44e7c0f1@mail.gmail.com> Message-ID: <20830760.post@talk.nabble.com> Garrett Cooper-6 wrote: > > On Thu, Dec 4, 2008 at 12:02 AM, Silver Salonen > wrote: >> >> Hello. >> >> I created a port for Museek+ which is built with cmake now. The problem >> is >> that although it gets built OK, cmake cannot link one of its executables >> against libxml++: >> ===== >> ... [100%] Building CXX object >> museekd/CMakeFiles/museekd.dir/distributedsocket.cpp.o Linking CXX >> executable museekd /usr/bin/ld: cannot find -lxml++-2.6 *** Error code 1 >> ===== >> >> Concerning libxml++, cmake seems to find it OK - before building: >> ===== >> -- checking for one of the modules 'libxml++-2.6' -- found libxml++-2.6, >> version 2.22.0 >> ===== >> >> Previously I had a problem with cmake finding libiconv.h, but I resolved >> it >> with "CMAKE_ARGS+= -DCMAKE_REQUIRED_INCLUDES="${LOCALBASE}/include". >> But >> I guess it's irrelevant and not even similar. >> >> Is there anything to be specified in order to cmake to find libxml++ >> correctly? > > 1. Does /usr/local/lib/libxml++-2.6.a and/or > /usr/local/lib/libxml++-2.6.so exist? > 2. What are your CXXFLAGS / LDFLAGS? > 1. Yes: $ ls -1 /usr/local/lib/libxml++* /usr/local/lib/libxml++-2.6.a /usr/local/lib/libxml++-2.6.la /usr/local/lib/libxml++-2.6.so /usr/local/lib/libxml++-2.6.so.2 2. CXXFLAGS: -O2 -fno-strict-aliasing -pipe LDFLAGS: nothing -- View this message in context: http://www.nabble.com/cmake-cannot-link-against-libxml%2B%2B-tp20828880p20830760.html Sent from the freebsd-ports mailing list archive at Nabble.com. From trebestie at gmail.com Thu Dec 4 02:30:11 2008 From: trebestie at gmail.com (Diego Depaoli) Date: Thu Dec 4 02:30:44 2008 Subject: after last update xmms get all processor resourses In-Reply-To: <493792CF.1010805@lissyara.su> References: <493792CF.1010805@lissyara.su> Message-ID: <83e5fb980812040203q4f3c74a1r6af4d19ea4a9ed29@mail.gmail.com> 2008/12/4 Alex Keda : > subj. > > last pid: 2718; load averages: 0.87, 1.08, 1.15 up 0+18:02:08 > 11:17:45 > 134 processes: 4 running, 130 sleeping > CPU: 9.7% user, 0.0% nice, 49.8% system, 1.9% interrupt, 38.6% idle > Mem: 398M Active, 730M Inact, 414M Wired, 488K Cache, 194M Buf, 307M Free > Swap: 905M Total, 905M Free > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 2669 lissyara 3 44 0 73452K 12288K select 0 0:31 92.19% xmms on my system pulseaudio and pcmanfm too. Moreover some mono dependent application (banshee, f-spot) stops working. Cheers -- Diego Depaoli From snvoronkov at yandex.ru Thu Dec 4 02:53:38 2008 From: snvoronkov at yandex.ru (Sergey N. Voronkov) Date: Thu Dec 4 02:53:49 2008 Subject: after last update xmms get all processor resourses Message-ID: <4937B440.2010009@yandex.ru> Helo! > last pid: 2718; load averages: 0.87, 1.08, 1.15 up 0+18:02:08 > 11:17:45 > 134 processes: 4 running, 130 sleeping > CPU: 9.7% user, 0.0% nice, 49.8% system, 1.9% interrupt, 38.6% idle > Mem: 398M Active, 730M Inact, 414M Wired, 488K Cache, 194M Buf, 307M Free > Swap: 905M Total, 905M Free Some here. Looks like ports/multimedia/xmms/files/patch-main.c is buggy. Just remove it and recompile port. Serg N. Voronkov, Sibitex Ltd. From mrtg at subnets.ru Thu Dec 4 03:12:36 2008 From: mrtg at subnets.ru (Alexey V. Panfilov) Date: Thu Dec 4 03:13:09 2008 Subject: after last update xmms get all processor resourses In-Reply-To: <4937AE4C.8090203@lissyara.su> References: <493792CF.1010805@lissyara.su> <7d6fde3d0812040200q647f21f9jb019892c3a47cb30@mail.gmail.com> <4937AE4C.8090203@lissyara.su> Message-ID: <4937B4E2.9070400@subnets.ru> Alex Keda ?????: > Garrett Cooper ?????: >> On Thu, Dec 4, 2008 at 12:20 AM, Alex Keda wrote: >> >>> subj. >>> >>> last pid: 2718; load averages: 0.87, 1.08, 1.15 up 0+18:02:08 >>> 11:17:45 >>> 134 processes: 4 running, 130 sleeping >>> CPU: 9.7% user, 0.0% nice, 49.8% system, 1.9% interrupt, 38.6% idle >>> Mem: 398M Active, 730M Inact, 414M Wired, 488K Cache, 194M Buf, 307M >>> Free >>> Swap: 905M Total, 905M Free >>> >>> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU >>> COMMAND >>> 2669 lissyara 3 44 0 73452K 12288K select 0 0:31 92.19% >>> xmms >>> ============== >>> lissyara$ uname -a >>> FreeBSD lissyara.moskb.local 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri >>> Nov 28 >>> 13:20:28 MSK 2008 >>> lissyara@lissyara.moskb.local:/usr/obj/mnt/jabber/DISTR/FreeBSD/src/CURRENT/sys/GENERIC >>> >>> amd64 >>> >>> lissyara$ pkg_info | grep xmms >>> librcc-0.2.6_1 Library used by rusxmms for language autodetection >>> librcd-0.1.11 Library used by rusxmms for autodetection of >>> russian >>> charse >>> xmms-1.2.11_4 X Multimedia System -- An audio player with >>> Winamp GUI >>> xmms-kde-3.2_4 Integrates XMMS into the KDE3 Panel >>> xmms-skins-0.1_3 Skins for X Multimedia System (XMMS) >>> >> >> Could you start up xmms via strace or truss in a terminal and provide >> output on pastebin.com please? >> Thanks, >> -Garrett >> >> > very big. pastebin.com give 500 error =) > http://lissyara.su/patch/xmms/typescript.txt I've the same effect. Output of truss: http://subnets.ru/files/xmms.log > -- Best regards, Alexey V. Panfilov ICQ: 1053180 Jabber: lehis@jabber.ru mailto: ports@subnets.ru www: http://www.subnets.ru From yanefbsd at gmail.com Thu Dec 4 03:20:43 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Dec 4 03:20:59 2008 Subject: cmake cannot link against libxml++ In-Reply-To: <20830760.post@talk.nabble.com> References: <20828880.post@talk.nabble.com> <7d6fde3d0812040143n374c63edyead7aa4f44e7c0f1@mail.gmail.com> <20830760.post@talk.nabble.com> Message-ID: <7d6fde3d0812040320p2df5474av631d9139c1e9f205@mail.gmail.com> On Thu, Dec 4, 2008 at 2:20 AM, Silver Salonen wrote: > > > Garrett Cooper-6 wrote: >> >> On Thu, Dec 4, 2008 at 12:02 AM, Silver Salonen >> wrote: >>> >>> Hello. >>> >>> I created a port for Museek+ which is built with cmake now. The problem >>> is >>> that although it gets built OK, cmake cannot link one of its executables >>> against libxml++: >>> ===== >>> ... [100%] Building CXX object >>> museekd/CMakeFiles/museekd.dir/distributedsocket.cpp.o Linking CXX >>> executable museekd /usr/bin/ld: cannot find -lxml++-2.6 *** Error code 1 >>> ===== >>> >>> Concerning libxml++, cmake seems to find it OK - before building: >>> ===== >>> -- checking for one of the modules 'libxml++-2.6' -- found libxml++-2.6, >>> version 2.22.0 >>> ===== >>> >>> Previously I had a problem with cmake finding libiconv.h, but I resolved >>> it >>> with "CMAKE_ARGS+= -DCMAKE_REQUIRED_INCLUDES="${LOCALBASE}/include". >>> But >>> I guess it's irrelevant and not even similar. >>> >>> Is there anything to be specified in order to cmake to find libxml++ >>> correctly? >> >> 1. Does /usr/local/lib/libxml++-2.6.a and/or >> /usr/local/lib/libxml++-2.6.so exist? >> 2. What are your CXXFLAGS / LDFLAGS? >> > > 1. Yes: > $ ls -1 /usr/local/lib/libxml++* > /usr/local/lib/libxml++-2.6.a > /usr/local/lib/libxml++-2.6.la > /usr/local/lib/libxml++-2.6.so > /usr/local/lib/libxml++-2.6.so.2 > > 2. CXXFLAGS: -O2 -fno-strict-aliasing -pipe > LDFLAGS: nothing Sorry -- let me rephrase: what are CXXFLAGS and LDFLAGS set to for the port? -Garrett From silver.salonen at gmail.com Thu Dec 4 03:27:04 2008 From: silver.salonen at gmail.com (Silver Salonen) Date: Thu Dec 4 03:27:10 2008 Subject: cmake cannot link against libxml++ In-Reply-To: <7d6fde3d0812040320p2df5474av631d9139c1e9f205@mail.gmail.com> References: <20828880.post@talk.nabble.com> <7d6fde3d0812040143n374c63edyead7aa4f44e7c0f1@mail.gmail.com> <20830760.post@talk.nabble.com> <7d6fde3d0812040320p2df5474av631d9139c1e9f205@mail.gmail.com> Message-ID: <20831657.post@talk.nabble.com> Garrett Cooper-6 wrote: > > On Thu, Dec 4, 2008 at 2:20 AM, Silver Salonen > wrote: >> Garrett Cooper-6 wrote: >>> >>> On Thu, Dec 4, 2008 at 12:02 AM, Silver Salonen >>> wrote: >>>> >>>> Hello. >>>> >>>> I created a port for Museek+ which is built with cmake now. The problem >>>> is >>>> that although it gets built OK, cmake cannot link one of its >>>> executables >>>> against libxml++: >>>> ===== >>>> ... [100%] Building CXX object >>>> museekd/CMakeFiles/museekd.dir/distributedsocket.cpp.o Linking CXX >>>> executable museekd /usr/bin/ld: cannot find -lxml++-2.6 *** Error code >>>> 1 >>>> ===== >>>> >>>> Concerning libxml++, cmake seems to find it OK - before building: >>>> ===== >>>> -- checking for one of the modules 'libxml++-2.6' -- found >>>> libxml++-2.6, >>>> version 2.22.0 >>>> ===== >>>> >>>> Previously I had a problem with cmake finding libiconv.h, but I >>>> resolved >>>> it >>>> with "CMAKE_ARGS+= -DCMAKE_REQUIRED_INCLUDES="${LOCALBASE}/include". >>>> But >>>> I guess it's irrelevant and not even similar. >>>> >>>> Is there anything to be specified in order to cmake to find libxml++ >>>> correctly? >>> >>> 1. Does /usr/local/lib/libxml++-2.6.a and/or >>> /usr/local/lib/libxml++-2.6.so exist? >>> 2. What are your CXXFLAGS / LDFLAGS? >>> >> >> 1. Yes: >> $ ls -1 /usr/local/lib/libxml++* >> /usr/local/lib/libxml++-2.6.a >> /usr/local/lib/libxml++-2.6.la >> /usr/local/lib/libxml++-2.6.so >> /usr/local/lib/libxml++-2.6.so.2 >> >> 2. CXXFLAGS: -O2 -fno-strict-aliasing -pipe >> LDFLAGS: nothing > > Sorry -- let me rephrase: what are CXXFLAGS and LDFLAGS set to for the > port? > -Garrett > I got the values from pre-everything: @${ECHO_MSG} "${CXXFLAGS}" @${ECHO_MSG} "${LDFLAGS}" So I guess they are valid in this matter? -- View this message in context: http://www.nabble.com/cmake-cannot-link-against-libxml%2B%2B-tp20828880p20831657.html Sent from the freebsd-ports mailing list archive at Nabble.com. From serg at tmn.ru Thu Dec 4 03:29:41 2008 From: serg at tmn.ru (Sergey N. Voronkov) Date: Thu Dec 4 03:29:49 2008 Subject: after last update xmms get all processor resourses In-Reply-To: <4937B4E2.9070400@subnets.ru> References: <493792CF.1010805@lissyara.su> <7d6fde3d0812040200q647f21f9jb019892c3a47cb30@mail.gmail.com> <4937AE4C.8090203@lissyara.su> <4937B4E2.9070400@subnets.ru> Message-ID: <20081204111905.GA35733@tmn.ru> On Thu, Dec 04, 2008 at 01:45:54PM +0300, Alexey V. Panfilov wrote: > Alex Keda ?????: > >Garrett Cooper ?????: > >>On Thu, Dec 4, 2008 at 12:20 AM, Alex Keda wrote: > >> > >>>subj. > >>> > >>>last pid: 2718; load averages: 0.87, 1.08, 1.15 up 0+18:02:08 > >>> 11:17:45 > >>>134 processes: 4 running, 130 sleeping > >>>CPU: 9.7% user, 0.0% nice, 49.8% system, 1.9% interrupt, 38.6% idle > >>>Mem: 398M Active, 730M Inact, 414M Wired, 488K Cache, 194M Buf, 307M > >>>Free > >>>Swap: 905M Total, 905M Free > >>> > >>> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU > >>>COMMAND > >>>2669 lissyara 3 44 0 73452K 12288K select 0 0:31 92.19% > >>>xmms > >>>============== > >>>lissyara$ uname -a > >>>FreeBSD lissyara.moskb.local 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri > >>>Nov 28 > >>>13:20:28 MSK 2008 > >>>lissyara@lissyara.moskb.local:/usr/obj/mnt/jabber/DISTR/FreeBSD/src/CURRENT/sys/GENERIC > >>> > >>> amd64 > >>> > >>>lissyara$ pkg_info | grep xmms > >>>librcc-0.2.6_1 Library used by rusxmms for language autodetection > >>>librcd-0.1.11 Library used by rusxmms for autodetection of > >>>russian > >>>charse > >>>xmms-1.2.11_4 X Multimedia System -- An audio player with > >>>Winamp GUI > >>>xmms-kde-3.2_4 Integrates XMMS into the KDE3 Panel > >>>xmms-skins-0.1_3 Skins for X Multimedia System (XMMS) > >>> > >> > >>Could you start up xmms via strace or truss in a terminal and provide > >>output on pastebin.com please? > >>Thanks, > >>-Garrett > >> > >> > >very big. pastebin.com give 500 error =) > >http://lissyara.su/patch/xmms/typescript.txt > I've the same effect. > > Output of truss: http://subnets.ru/files/xmms.log Once again. Helped for me: # rm -f /usr/ports/multimedia/xmms/patch-main.c Serg N. Voronkov, Sibitex Ltd. From admin at lissyara.su Thu Dec 4 03:48:35 2008 From: admin at lissyara.su (Alex Keda) Date: Thu Dec 4 03:48:47 2008 Subject: after last update xmms get all processor resourses In-Reply-To: <4937B440.2010009@yandex.ru> References: <4937B440.2010009@yandex.ru> Message-ID: <4937C391.2050602@lissyara.su> Sergey N. Voronkov ?????: > Helo! > > > last pid: 2718; load averages: 0.87, 1.08, 1.15 up 0+18:02:08 > > 11:17:45 > > 134 processes: 4 running, 130 sleeping > > CPU: 9.7% user, 0.0% nice, 49.8% system, 1.9% interrupt, 38.6% idle > > Mem: 398M Active, 730M Inact, 414M Wired, 488K Cache, 194M Buf, 307M > Free > > Swap: 905M Total, 905M Free > > Some here. Looks like ports/multimedia/xmms/files/patch-main.c is buggy. > Just remove it and recompile port. > with this patch I have additional bug. I select track in list, double click to him - it play musik. if I double click to another track - xmms crash. If I press stop, or pause button - double click to another composition - play it ========== without ports/multimedia/xmms/files/patch-main.c - cpu load - little, no crash with select track From beech at alaskaparadise.com Thu Dec 4 04:31:34 2008 From: beech at alaskaparadise.com (Beech Rintoul) Date: Thu Dec 4 04:31:47 2008 Subject: after last update xmms get all processor resourses In-Reply-To: <4937C391.2050602@lissyara.su> References: <4937B440.2010009@yandex.ru> <4937C391.2050602@lissyara.su> Message-ID: <200812040313.17103.beech@alaskaparadise.com> On Thursday 04 December 2008 02:48:33 Alex Keda wrote: > Sergey N. Voronkov ?????: > > Helo! > > > > > last pid: 2718; load averages: 0.87, 1.08, 1.15 up 0+18:02:08 > > > 11:17:45 > > > 134 processes: 4 running, 130 sleeping > > > CPU: 9.7% user, 0.0% nice, 49.8% system, 1.9% interrupt, 38.6% idle > > > Mem: 398M Active, 730M Inact, 414M Wired, 488K Cache, 194M Buf, 307M > > > > Free > > > > > Swap: 905M Total, 905M Free > > > > Some here. Looks like ports/multimedia/xmms/files/patch-main.c is buggy. > > Just remove it and recompile port. > > with this patch I have additional bug. > I select track in list, double click to him - it play musik. > if I double click to another track - xmms crash. > If I press stop, or pause button - double click to another composition - > play it > ========== > without ports/multimedia/xmms/files/patch-main.c - cpu load - little, no > crash with select track I'll remove it. Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --------------------------------------------------------------------------------------- From astraserg at proc.ru Thu Dec 4 06:58:26 2008 From: astraserg at proc.ru (Sergey V. Yaroshevskiy) Date: Thu Dec 4 06:58:33 2008 Subject: tora2 Message-ID: <200812041738.25805.astraserg@proc.ru> Good day Do you have plans about porting tora2? Thanks -- Sergey V. Yaroshevskiy, astraserg@proc.ru TechDirector www.proc.ru From thierry at FreeBSD.org Thu Dec 4 10:16:05 2008 From: thierry at FreeBSD.org (Thierry Thomas) Date: Thu Dec 4 10:16:11 2008 Subject: tora2 In-Reply-To: <200812041738.25805.astraserg@proc.ru> References: <200812041738.25805.astraserg@proc.ru> Message-ID: <20081204174100.GB2839@graf.pompo.net> Le Jeu 4 d?c 08 ? 15:38:25 +0100, Sergey V. Yaroshevskiy ?crivait?: > Good day Hello, > Do you have plans about porting tora2? Could you please test ? It does not work here, and I have not yet investigated it. Regards, -- Th. Thomas. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081204/54ac90a7/attachment.pgp From yanefbsd at gmail.com Thu Dec 4 12:05:43 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Dec 4 12:05:52 2008 Subject: cmake cannot link against libxml++ In-Reply-To: <20831657.post@talk.nabble.com> References: <20828880.post@talk.nabble.com> <7d6fde3d0812040143n374c63edyead7aa4f44e7c0f1@mail.gmail.com> <20830760.post@talk.nabble.com> <7d6fde3d0812040320p2df5474av631d9139c1e9f205@mail.gmail.com> <20831657.post@talk.nabble.com> Message-ID: <7d6fde3d0812041205h493da747vffede0a613c390b8@mail.gmail.com> On Thu, Dec 4, 2008 at 3:27 AM, Silver Salonen wrote: > > > Garrett Cooper-6 wrote: >> >> On Thu, Dec 4, 2008 at 2:20 AM, Silver Salonen >> wrote: >>> Garrett Cooper-6 wrote: >>>> >>>> On Thu, Dec 4, 2008 at 12:02 AM, Silver Salonen >>>> wrote: >>>>> >>>>> Hello. >>>>> >>>>> I created a port for Museek+ which is built with cmake now. The problem >>>>> is >>>>> that although it gets built OK, cmake cannot link one of its >>>>> executables >>>>> against libxml++: >>>>> ===== >>>>> ... [100%] Building CXX object >>>>> museekd/CMakeFiles/museekd.dir/distributedsocket.cpp.o Linking CXX >>>>> executable museekd /usr/bin/ld: cannot find -lxml++-2.6 *** Error code >>>>> 1 >>>>> ===== >>>>> >>>>> Concerning libxml++, cmake seems to find it OK - before building: >>>>> ===== >>>>> -- checking for one of the modules 'libxml++-2.6' -- found >>>>> libxml++-2.6, >>>>> version 2.22.0 >>>>> ===== >>>>> >>>>> Previously I had a problem with cmake finding libiconv.h, but I >>>>> resolved >>>>> it >>>>> with "CMAKE_ARGS+= -DCMAKE_REQUIRED_INCLUDES="${LOCALBASE}/include". >>>>> But >>>>> I guess it's irrelevant and not even similar. >>>>> >>>>> Is there anything to be specified in order to cmake to find libxml++ >>>>> correctly? >>>> >>>> 1. Does /usr/local/lib/libxml++-2.6.a and/or >>>> /usr/local/lib/libxml++-2.6.so exist? >>>> 2. What are your CXXFLAGS / LDFLAGS? >>>> >>> >>> 1. Yes: >>> $ ls -1 /usr/local/lib/libxml++* >>> /usr/local/lib/libxml++-2.6.a >>> /usr/local/lib/libxml++-2.6.la >>> /usr/local/lib/libxml++-2.6.so >>> /usr/local/lib/libxml++-2.6.so.2 >>> >>> 2. CXXFLAGS: -O2 -fno-strict-aliasing -pipe >>> LDFLAGS: nothing >> >> Sorry -- let me rephrase: what are CXXFLAGS and LDFLAGS set to for the >> port? >> -Garrett >> > > I got the values from pre-everything: > @${ECHO_MSG} "${CXXFLAGS}" > @${ECHO_MSG} "${LDFLAGS}" > > So I guess they are valid in this matter? Eh? It all depends on where you're doing the echo... Honestly I'd need to see more around where you're running configure, or passing in args for the parent make (if it doesn't use configure). You're probably just missing /usr/local/lib in your LDFLAGS though. -Garrett From trebestie at gmail.com Thu Dec 4 14:41:51 2008 From: trebestie at gmail.com (Diego Depaoli) Date: Thu Dec 4 14:41:58 2008 Subject: Various issues Message-ID: <83e5fb980812041441p12527d43qffa677638e6e4202@mail.gmail.com> I've posted yet, but replying the wrong thread. On my system 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Sun Nov 30 21:57:16 CET 2008 pulseaudio get 100% cpu resources. These are last lines of truss 48732: wait4(0xffffffff,0xbfbfe518,0x2,0x0,0x213,0x1) = 48739 (0xbe63) 48732: read(10,"lay=$DISPLAY session_manager=$SE"...,1023) = 69 (0x45) 48732: fork(0x28337350,0xbfbfe478,0xa,0x28097f64,0x1,0xbfbfe494) = 48746 (0xbe6a) 48732: getpgrp(0x1,0xbfbfe494,0xbe6a,0x0,0x28333240,0x0) = 48732 (0xbe5c) 48732: wait4(0xffffffff,0xbfbfe458,0x2,0x0,0x28337598,0x1) ERR#10 'No child processes' Banshee and f-spot (both mono related) don't work anymore. These are last lines of truss [banshee|f-spot] write(25,"/home/diego/.config/banshee-1",29) = 29 (0x1d) write(25,"\n",1) = 1 (0x1) write(25,"/usr/local/lib/banshee-1",24) = 24 (0x18) write(25,"\n",1) = 1 (0x1) read(26,"process-ps-plog:scan:/usr/local/"...,8192) = 75 (0x4b) read(26,"\n",8192) = 1 (0x1) read(26,"process-ps-plog:endscan",8192) = 23 (0x17) read(26,"\nprocess-ps-plog:scan:/usr/loca"...,8192) = 64 (0x40) read(26,0x83d2010,8192) = 0 (0x0) gettimeofday({1228429590.827982 },0x0) = 0 (0x0) semop(0x10001,0xbf9feef6,0x1,0x28230f64,0x1,0x3ef14) = 0 (0x0) semop(0x10001,0xbf9feef6,0x1,0x28230f64,0x1,0x2ef14) = 0 (0x0) semop(0x10001,0xbf9feef6,0x1,0x28443751,0x1,0x2ef14) = 0 (0x0) semop(0x10001,0xbf9feef6,0x1,0x28443751,0x1,0x3ef14) = 0 (0x0) wait4(0x271d,0xbf9feea4,0x1,0x0,0x200282,0x28445a8c) ERR#10 'No child processes' Looks like these Issues appeared after last world/kernel. Any idea? Regards -- Diego Depaoli From erwin at FreeBSD.org Thu Dec 4 23:01:22 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Thu Dec 4 23:01:30 2008 Subject: INDEX build failed for 6.x Message-ID: <200812050701.mB571DLq083446@pointyhat.freebsd.org> INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: php5-mssql-5.2.6_2: no entry for /usr/ports/databases/freetds-msdblib make_index: php5-mssql-5.2.6_2: no entry for /usr/ports/databases/freetds-msdblib make_index: php4-mssql-4.4.9: no entry for /usr/ports/databases/freetds-msdblib make_index: php4-mssql-4.4.9: no entry for /usr/ports/databases/freetds-msdblib make_index: py25-mssql-0.8.0: no entry for /usr/ports/databases/freetds-msdblib make_index: py25-mssql-0.8.0: no entry for /usr/ports/databases/freetds-msdblib Committers on the hook: acm beech glewis tabthorpe Most recent CVS update was: U MOVED U databases/freetds/Makefile U databases/freetds/distinfo U databases/freetds/pkg-plist U databases/freetds/files/patch-doc_Makefile.in U emulators/mupen64-base/Makefile.common U emulators/mupen64-glide/Makefile U emulators/mupen64-tr64/Makefile U java/diablo-jdk15/Makefile U java/diablo-jdk15/distinfo U java/diablo-jdk15/pkg-plist U java/diablo-jdk16/Makefile U java/diablo-jdk16/distinfo U java/diablo-jdk16/pkg-plist U java/diablo-jre15/Makefile U java/diablo-jre15/distinfo U java/diablo-jre15/pkg-plist U java/diablo-jre16/Makefile U java/diablo-jre16/distinfo U java/diablo-jre16/pkg-plist U mail/squirrelmail/Makefile U mail/squirrelmail/bsd.squirrelmail.mk U mail/squirrelmail/distinfo From silver.salonen at gmail.com Thu Dec 4 23:35:46 2008 From: silver.salonen at gmail.com (Silver Salonen) Date: Thu Dec 4 23:35:53 2008 Subject: cmake cannot link against libxml++ In-Reply-To: <7d6fde3d0812041205h493da747vffede0a613c390b8@mail.gmail.com> References: <20828880.post@talk.nabble.com> <7d6fde3d0812040143n374c63edyead7aa4f44e7c0f1@mail.gmail.com> <20830760.post@talk.nabble.com> <7d6fde3d0812040320p2df5474av631d9139c1e9f205@mail.gmail.com> <20831657.post@talk.nabble.com> <7d6fde3d0812041205h493da747vffede0a613c390b8@mail.gmail.com> Message-ID: <20849062.post@talk.nabble.com> Garrett Cooper-6 wrote: > > On Thu, Dec 4, 2008 at 3:27 AM, Silver Salonen > wrote: >> >> Garrett Cooper-6 wrote: >>> >>> On Thu, Dec 4, 2008 at 2:20 AM, Silver Salonen >>> >>> wrote: >>>> Garrett Cooper-6 wrote: >>>>> >>>>> On Thu, Dec 4, 2008 at 12:02 AM, Silver Salonen >>>>> wrote: >>>>>> >>>>>> Hello. >>>>>> >>>>>> I created a port for Museek+ which is built with cmake now. The >>>>>> problem >>>>>> is >>>>>> that although it gets built OK, cmake cannot link one of its >>>>>> executables >>>>>> against libxml++: >>>>>> ===== >>>>>> ... [100%] Building CXX object >>>>>> museekd/CMakeFiles/museekd.dir/distributedsocket.cpp.o Linking CXX >>>>>> executable museekd /usr/bin/ld: cannot find -lxml++-2.6 *** Error >>>>>> code >>>>>> 1 >>>>>> ===== >>>>>> >>>>>> Concerning libxml++, cmake seems to find it OK - before building: >>>>>> ===== >>>>>> -- checking for one of the modules 'libxml++-2.6' -- found >>>>>> libxml++-2.6, >>>>>> version 2.22.0 >>>>>> ===== >>>>>> >>>>>> Previously I had a problem with cmake finding libiconv.h, but I >>>>>> resolved >>>>>> it >>>>>> with "CMAKE_ARGS+= >>>>>> -DCMAKE_REQUIRED_INCLUDES="${LOCALBASE}/include". >>>>>> But >>>>>> I guess it's irrelevant and not even similar. >>>>>> >>>>>> Is there anything to be specified in order to cmake to find libxml++ >>>>>> correctly? >>>>> >>>>> 1. Does /usr/local/lib/libxml++-2.6.a and/or >>>>> /usr/local/lib/libxml++-2.6.so exist? >>>>> 2. What are your CXXFLAGS / LDFLAGS? >>>>> >>>> >>>> 1. Yes: >>>> $ ls -1 /usr/local/lib/libxml++* >>>> /usr/local/lib/libxml++-2.6.a >>>> /usr/local/lib/libxml++-2.6.la >>>> /usr/local/lib/libxml++-2.6.so >>>> /usr/local/lib/libxml++-2.6.so.2 >>>> >>>> 2. CXXFLAGS: -O2 -fno-strict-aliasing -pipe >>>> LDFLAGS: nothing >>> >>> Sorry -- let me rephrase: what are CXXFLAGS and LDFLAGS set to for the >>> port? >>> -Garrett >>> >> >> I got the values from pre-everything: >> @${ECHO_MSG} "${CXXFLAGS}" >> @${ECHO_MSG} "${LDFLAGS}" >> >> So I guess they are valid in this matter? > > Eh? It all depends on where you're doing the echo... > > Honestly I'd need to see more around where you're running configure, > or passing in args for the parent make (if it doesn't use configure). > You're probably just missing /usr/local/lib in your LDFLAGS though. > I echoed these in "pre-everything" section. Now I set "LDFLAGS+= -L${LOCALBASE}/lib", but it doesn't help much. My Makefile is structured smth like that: PORTNAME=... ... USE_CMAKE= yes ... LDFLAGS+= -L${LOCALBASE}/lib CMAKE_ARGS+= -DCMAKE_REQUIRED_INCLUDES="${LOCALBASE}/include" ... OPTIONS=... ... .include ... pre-everything:: @${ECHO_MSG} "${CXXFLAGS}" @${ECHO_MSG} "${LDFLAGS}" ... post-install: ... .include -- View this message in context: http://www.nabble.com/cmake-cannot-link-against-libxml%2B%2B-tp20828880p20849062.html Sent from the freebsd-ports mailing list archive at Nabble.com. From silver.salonen at gmail.com Thu Dec 4 23:46:32 2008 From: silver.salonen at gmail.com (Silver Salonen) Date: Thu Dec 4 23:46:38 2008 Subject: cmake cannot link against libxml++ In-Reply-To: <20849062.post@talk.nabble.com> References: <20828880.post@talk.nabble.com> <7d6fde3d0812040143n374c63edyead7aa4f44e7c0f1@mail.gmail.com> <20830760.post@talk.nabble.com> <7d6fde3d0812040320p2df5474av631d9139c1e9f205@mail.gmail.com> <20831657.post@talk.nabble.com> <7d6fde3d0812041205h493da747vffede0a613c390b8@mail.gmail.com> <20849062.post@talk.nabble.com> Message-ID: <20849140.post@talk.nabble.com> Silver Salonen wrote: > > > Garrett Cooper-6 wrote: >> >> On Thu, Dec 4, 2008 at 3:27 AM, Silver Salonen >> wrote: >>> >>> Garrett Cooper-6 wrote: >>>> >>>> On Thu, Dec 4, 2008 at 2:20 AM, Silver Salonen >>>> >>>> wrote: >>>>> Garrett Cooper-6 wrote: >>>>>> >>>>>> On Thu, Dec 4, 2008 at 12:02 AM, Silver Salonen >>>>>> wrote: >>>>>>> >>>>>>> Hello. >>>>>>> >>>>>>> I created a port for Museek+ which is built with cmake now. The >>>>>>> problem >>>>>>> is >>>>>>> that although it gets built OK, cmake cannot link one of its >>>>>>> executables >>>>>>> against libxml++: >>>>>>> ===== >>>>>>> ... [100%] Building CXX object >>>>>>> museekd/CMakeFiles/museekd.dir/distributedsocket.cpp.o Linking CXX >>>>>>> executable museekd /usr/bin/ld: cannot find -lxml++-2.6 *** Error >>>>>>> code >>>>>>> 1 >>>>>>> ===== >>>>>>> >>>>>>> Concerning libxml++, cmake seems to find it OK - before building: >>>>>>> ===== >>>>>>> -- checking for one of the modules 'libxml++-2.6' -- found >>>>>>> libxml++-2.6, >>>>>>> version 2.22.0 >>>>>>> ===== >>>>>>> >>>>>>> Previously I had a problem with cmake finding libiconv.h, but I >>>>>>> resolved >>>>>>> it >>>>>>> with "CMAKE_ARGS+= >>>>>>> -DCMAKE_REQUIRED_INCLUDES="${LOCALBASE}/include". >>>>>>> But >>>>>>> I guess it's irrelevant and not even similar. >>>>>>> >>>>>>> Is there anything to be specified in order to cmake to find libxml++ >>>>>>> correctly? >>>>>> >>>>>> 1. Does /usr/local/lib/libxml++-2.6.a and/or >>>>>> /usr/local/lib/libxml++-2.6.so exist? >>>>>> 2. What are your CXXFLAGS / LDFLAGS? >>>>>> >>>>> >>>>> 1. Yes: >>>>> $ ls -1 /usr/local/lib/libxml++* >>>>> /usr/local/lib/libxml++-2.6.a >>>>> /usr/local/lib/libxml++-2.6.la >>>>> /usr/local/lib/libxml++-2.6.so >>>>> /usr/local/lib/libxml++-2.6.so.2 >>>>> >>>>> 2. CXXFLAGS: -O2 -fno-strict-aliasing -pipe >>>>> LDFLAGS: nothing >>>> >>>> Sorry -- let me rephrase: what are CXXFLAGS and LDFLAGS set to for the >>>> port? >>>> -Garrett >>>> >>> >>> I got the values from pre-everything: >>> @${ECHO_MSG} "${CXXFLAGS}" >>> @${ECHO_MSG} "${LDFLAGS}" >>> >>> So I guess they are valid in this matter? >> >> Eh? It all depends on where you're doing the echo... >> >> Honestly I'd need to see more around where you're running configure, >> or passing in args for the parent make (if it doesn't use configure). >> You're probably just missing /usr/local/lib in your LDFLAGS though. >> > > I echoed these in "pre-everything" section. Now I set "LDFLAGS+= > -L${LOCALBASE}/lib", but it doesn't help much. My Makefile is structured > smth like that: > > PORTNAME=... > ... > USE_CMAKE= yes > ... > LDFLAGS+= -L${LOCALBASE}/lib > CMAKE_ARGS+= -DCMAKE_REQUIRED_INCLUDES="${LOCALBASE}/include" > ... > OPTIONS=... > ... > .include > ... > pre-everything:: > @${ECHO_MSG} "${CXXFLAGS}" > @${ECHO_MSG} "${LDFLAGS}" > ... > post-install: > ... > .include > OK, the problem disappeared when I also set: CONFIGURE_ENV+= CPPFLAGS="${CPPFLAGS}" LDFLAGS="${LDFLAGS}" Thanks for your help! :) -- View this message in context: http://www.nabble.com/cmake-cannot-link-against-libxml%2B%2B-tp20828880p20849140.html Sent from the freebsd-ports mailing list archive at Nabble.com. From yanefbsd at gmail.com Fri Dec 5 00:27:47 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 5 00:27:54 2008 Subject: cmake cannot link against libxml++ In-Reply-To: <20849140.post@talk.nabble.com> References: <20828880.post@talk.nabble.com> <7d6fde3d0812040143n374c63edyead7aa4f44e7c0f1@mail.gmail.com> <20830760.post@talk.nabble.com> <7d6fde3d0812040320p2df5474av631d9139c1e9f205@mail.gmail.com> <20831657.post@talk.nabble.com> <7d6fde3d0812041205h493da747vffede0a613c390b8@mail.gmail.com> <20849062.post@talk.nabble.com> <20849140.post@talk.nabble.com> Message-ID: <7d6fde3d0812050027n712d78fxf9e70f2a4568e43@mail.gmail.com> On Thu, Dec 4, 2008 at 11:46 PM, Silver Salonen wrote: > > > Silver Salonen wrote: >> >> >> Garrett Cooper-6 wrote: >>> >>> On Thu, Dec 4, 2008 at 3:27 AM, Silver Salonen >>> wrote: >>>> >>>> Garrett Cooper-6 wrote: >>>>> >>>>> On Thu, Dec 4, 2008 at 2:20 AM, Silver Salonen >>>>> >>>>> wrote: >>>>>> Garrett Cooper-6 wrote: >>>>>>> >>>>>>> On Thu, Dec 4, 2008 at 12:02 AM, Silver Salonen >>>>>>> wrote: >>>>>>>> >>>>>>>> Hello. >>>>>>>> >>>>>>>> I created a port for Museek+ which is built with cmake now. The >>>>>>>> problem >>>>>>>> is >>>>>>>> that although it gets built OK, cmake cannot link one of its >>>>>>>> executables >>>>>>>> against libxml++: >>>>>>>> ===== >>>>>>>> ... [100%] Building CXX object >>>>>>>> museekd/CMakeFiles/museekd.dir/distributedsocket.cpp.o Linking CXX >>>>>>>> executable museekd /usr/bin/ld: cannot find -lxml++-2.6 *** Error >>>>>>>> code >>>>>>>> 1 >>>>>>>> ===== >>>>>>>> >>>>>>>> Concerning libxml++, cmake seems to find it OK - before building: >>>>>>>> ===== >>>>>>>> -- checking for one of the modules 'libxml++-2.6' -- found >>>>>>>> libxml++-2.6, >>>>>>>> version 2.22.0 >>>>>>>> ===== >>>>>>>> >>>>>>>> Previously I had a problem with cmake finding libiconv.h, but I >>>>>>>> resolved >>>>>>>> it >>>>>>>> with "CMAKE_ARGS+= >>>>>>>> -DCMAKE_REQUIRED_INCLUDES="${LOCALBASE}/include". >>>>>>>> But >>>>>>>> I guess it's irrelevant and not even similar. >>>>>>>> >>>>>>>> Is there anything to be specified in order to cmake to find libxml++ >>>>>>>> correctly? >>>>>>> >>>>>>> 1. Does /usr/local/lib/libxml++-2.6.a and/or >>>>>>> /usr/local/lib/libxml++-2.6.so exist? >>>>>>> 2. What are your CXXFLAGS / LDFLAGS? >>>>>>> >>>>>> >>>>>> 1. Yes: >>>>>> $ ls -1 /usr/local/lib/libxml++* >>>>>> /usr/local/lib/libxml++-2.6.a >>>>>> /usr/local/lib/libxml++-2.6.la >>>>>> /usr/local/lib/libxml++-2.6.so >>>>>> /usr/local/lib/libxml++-2.6.so.2 >>>>>> >>>>>> 2. CXXFLAGS: -O2 -fno-strict-aliasing -pipe >>>>>> LDFLAGS: nothing >>>>> >>>>> Sorry -- let me rephrase: what are CXXFLAGS and LDFLAGS set to for the >>>>> port? >>>>> -Garrett >>>>> >>>> >>>> I got the values from pre-everything: >>>> @${ECHO_MSG} "${CXXFLAGS}" >>>> @${ECHO_MSG} "${LDFLAGS}" >>>> >>>> So I guess they are valid in this matter? >>> >>> Eh? It all depends on where you're doing the echo... >>> >>> Honestly I'd need to see more around where you're running configure, >>> or passing in args for the parent make (if it doesn't use configure). >>> You're probably just missing /usr/local/lib in your LDFLAGS though. >>> >> >> I echoed these in "pre-everything" section. Now I set "LDFLAGS+= >> -L${LOCALBASE}/lib", but it doesn't help much. My Makefile is structured >> smth like that: >> >> PORTNAME=... >> ... >> USE_CMAKE= yes >> ... >> LDFLAGS+= -L${LOCALBASE}/lib >> CMAKE_ARGS+= -DCMAKE_REQUIRED_INCLUDES="${LOCALBASE}/include" >> ... >> OPTIONS=... >> ... >> .include >> ... >> pre-everything:: >> @${ECHO_MSG} "${CXXFLAGS}" >> @${ECHO_MSG} "${LDFLAGS}" >> ... >> post-install: >> ... >> .include >> > > OK, the problem disappeared when I also set: CONFIGURE_ENV+= > CPPFLAGS="${CPPFLAGS}" LDFLAGS="${LDFLAGS}" > > Thanks for your help! :) Bingo, ya got it ;) (I was kind of pointing you in that direction, but I wasn't sure where you did or didn't pass the variables through). Environment variables that need to be communicate to the underlying processes for compiling things should be communicate via either configure (which just is a wrapper produced by autotools / autoconf) or gmake, or via the double-dashed args to configure. There are other make systems like scons, or waf, etc that do different things, but that's outside the scope of what most folks try to do, and the syntax is similar. Best of luck, -Garrett From yanefbsd at gmail.com Fri Dec 5 00:32:42 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 5 00:32:48 2008 Subject: INDEX build failed for 6.x In-Reply-To: <200812050701.mB571DLq083446@pointyhat.freebsd.org> References: <200812050701.mB571DLq083446@pointyhat.freebsd.org> Message-ID: <7d6fde3d0812050032w17b928c7va4b92158f0e770b0@mail.gmail.com> On Thu, Dec 4, 2008 at 11:01 PM, Erwin Lansing wrote: > INDEX build failed with errors: > Generating INDEX-6 - please wait..pkg_info: not found > pkg_info: not found > pkg_info: not found > pkg_info: not found > Done. > make_index: php5-mssql-5.2.6_2: no entry for /usr/ports/databases/freetds-msdblib > make_index: php5-mssql-5.2.6_2: no entry for /usr/ports/databases/freetds-msdblib > make_index: php4-mssql-4.4.9: no entry for /usr/ports/databases/freetds-msdblib > make_index: php4-mssql-4.4.9: no entry for /usr/ports/databases/freetds-msdblib > make_index: py25-mssql-0.8.0: no entry for /usr/ports/databases/freetds-msdblib > make_index: py25-mssql-0.8.0: no entry for /usr/ports/databases/freetds-msdblib > > Committers on the hook: > acm beech glewis tabthorpe > > Most recent CVS update was: > U MOVED > U databases/freetds/Makefile > U databases/freetds/distinfo > U databases/freetds/pkg-plist > U databases/freetds/files/patch-doc_Makefile.in > U emulators/mupen64-base/Makefile.common > U emulators/mupen64-glide/Makefile > U emulators/mupen64-tr64/Makefile > U java/diablo-jdk15/Makefile > U java/diablo-jdk15/distinfo > U java/diablo-jdk15/pkg-plist > U java/diablo-jdk16/Makefile > U java/diablo-jdk16/distinfo > U java/diablo-jdk16/pkg-plist > U java/diablo-jre15/Makefile > U java/diablo-jre15/distinfo > U java/diablo-jre15/pkg-plist > U java/diablo-jre16/Makefile > U java/diablo-jre16/distinfo > U java/diablo-jre16/pkg-plist > U mail/squirrelmail/Makefile > U mail/squirrelmail/bsd.squirrelmail.mk > U mail/squirrelmail/distinfo I've seen this issue happen from time to time with the INDEX checker. I assume that this is running in a jail (for 6.x and 7.x). Is there a sufficient amount of sleep time between when the jail is setup and when the INDEX checking is run? Maybe this should be a prereq step in a setup section of some kind :\? -Garrett From erwin at FreeBSD.org Fri Dec 5 01:52:16 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Fri Dec 5 01:52:22 2008 Subject: INDEX now builds successfully on 6.x Message-ID: <200812050952.mB59q7pc064322@pointyhat.freebsd.org> From patrick at spacesurfer.com Fri Dec 5 06:46:02 2008 From: patrick at spacesurfer.com (Patrick Mackinlay) Date: Fri Dec 5 06:46:08 2008 Subject: tentakel 2.2 Message-ID: <49393A6C.1050802@spacesurfer.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am writing to you regarding the tentakel 2.2 port. I have the latest ports version (updated a couple of hours ago) and I am running FreeBSD 7.0 on an amd64 system. The tentakel 2.2 port does not work with either python 2.5, 2.6 or 3.0 For 2.5 and 2.6 I get the following error when I run tentakel using the configuration file provided in the distribution (/usr/local/share/doc/tentakel/tentakel.conf.example) Traceback (most recent call last): File "/usr/local/bin/tentakel", line 101, in conf.load(f) File "/usr/local/lib/python2.5/site-packages/lekatnet/config.py", line 181, in load self.parse("".join(file.readlines())) File "/usr/local/lib/python2.5/site-packages/lekatnet/config.py", line 175, in parse self.update(tp(txt)) File "/usr/local/lib/python2.5/site-packages/lekatnet/tpg.py", line 921, in __call__ return self.parse('START', input, *args, **kws) File "/usr/local/lib/python2.5/site-packages/lekatnet/tpg.py", line 934, in parse value = getattr(self, axiom)(*args, **kws) File "", line 8, in START File "", line 5, in SETTING File "", line 15, in PARAM File "/usr/local/lib/python2.5/site-packages/lekatnet/tpg.py", line 986, in extract return self.lexer[start:stop] TypeError: object cannot be interpreted as an index regards, Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk5OmwACgkQD97IpyzY3RJ7agCdEYT01+Kg66QaGGMzPnEqLjie 58cAn13EvAIQ0jbO+pVpOQCn0965yVK+ =4Hc/ -----END PGP SIGNATURE----- From phk at phk.freebsd.dk Fri Dec 5 06:54:22 2008 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Fri Dec 5 06:54:29 2008 Subject: XYSSL lives, in a new place it seems... Message-ID: <21819.1228487248@critter.freebsd.dk> The security/xyssl port could use an update, the project seems to have moved and release 3 versions since the 0.6 we have in the tree: http://www.ohloh.net/p/xyssl -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From frank at shute.org.uk Sat Dec 6 00:50:53 2008 From: frank at shute.org.uk (Frank Shute) Date: Sat Dec 6 00:51:01 2008 Subject: print/cm-super size mismatch Message-ID: <20081206083250.GA54798@melon.esperance-linux.co.uk> Hi, I just had a problem when building print/cm-super. cm-super.zip doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from ftp://ftp.funet.fi/pub/TeX/CTAN/fonts/ps-type1/. fetch: ftp://ftp.funet.fi/pub/TeX/CTAN/fonts/ps-type1/cm-super.zip: size mismatch: expected 67310332, actual 67319909 => Attempting to fetch from ftp://ctan.unsw.edu.au/tex-archive/fonts/ps-type1/. fetch: ftp://ctan.unsw.edu.au/tex-archive/fonts/ps-type1/cm-super.zip: Connection refused => Attempting to fetch from ftp://ftp.tex.ac.uk/tex-archive/fonts/ps-type1/. fetch: ftp://ftp.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super.zip: size mismatch: expected 67310332, actual 67319909 => Attempting to fetch from ftp://ftp.kddlabs.co.jp/CTAN/fonts/ps-type1/. It did fetch it from the jp mirror but slowly & build it. But I would have thought that the tarball at ftp.tex.ac.uk would be the canonical one. Any thoughts? Apologies if this has been reported before. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html From jdk at lawyers.nl Sat Dec 6 03:58:48 2008 From: jdk at lawyers.nl (Jeroen de Kreek) Date: Sat Dec 6 03:58:55 2008 Subject: No source for OpenOffice2 Message-ID: <200812061219.10080.jdk@lawyers.nl> Hi people Can not find the source for OpenOffice 2 Something wrong? http://www.freebsd.org/cgi/pds.cgi?ports/editors/openoffice.org-2 Regards, Jeroen. From hrs at FreeBSD.org Sat Dec 6 10:57:43 2008 From: hrs at FreeBSD.org (Hiroki Sato) Date: Sat Dec 6 10:57:51 2008 Subject: print/cm-super size mismatch In-Reply-To: <20081206083250.GA54798@melon.esperance-linux.co.uk> References: <20081206083250.GA54798@melon.esperance-linux.co.uk> Message-ID: <20081207.035520.258690873.hrs@allbsd.org> Frank Shute wrote in <20081206083250.GA54798@melon.esperance-linux.co.uk>: fr> Hi, fr> fr> I just had a problem when building print/cm-super. fr> fr> cm-super.zip doesn't seem to exist in /usr/ports/distfiles/. fr> => Attempting to fetch from ftp://ftp.funet.fi/pub/TeX/CTAN/fonts/ps-type1/. fr> fetch: ftp://ftp.funet.fi/pub/TeX/CTAN/fonts/ps-type1/cm-super.zip: size mismatch: expected 67310332, actual 67319909 fr> => Attempting to fetch from ftp://ctan.unsw.edu.au/tex-archive/fonts/ps-type1/. fr> fetch: ftp://ctan.unsw.edu.au/tex-archive/fonts/ps-type1/cm-super.zip: Connection refused fr> => Attempting to fetch from ftp://ftp.tex.ac.uk/tex-archive/fonts/ps-type1/. fr> fetch: ftp://ftp.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super.zip: size mismatch: expected 67310332, actual 67319909 fr> => Attempting to fetch from ftp://ftp.kddlabs.co.jp/CTAN/fonts/ps-type1/. fr> fr> It did fetch it from the jp mirror but slowly & build it. fr> fr> But I would have thought that the tarball at ftp.tex.ac.uk would be fr> the canonical one. Any thoughts? This was because the distfile was updated. The port was also updated just now, so please try the latest ports tree. Thank you for the report! -- | Hiroki SATO -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081206/3275e380/attachment.pgp From erwin at FreeBSD.org Sun Dec 7 05:06:25 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Sun Dec 7 05:06:34 2008 Subject: INDEX build failed for 6.x Message-ID: <200812071306.mB7D6E23054302@pointyhat.freebsd.org> INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: phpGedView-4.1.4_1: no entry for /usr/ports/devel/php5-pcre make_index: drupal6-6.6: no entry for /usr/ports/devel/php5-pcre make_index: pivot-weblog-1.40.6: no entry for /usr/ports/devel/php5-pcre make_index: phpwiki-1.2.10_4: no entry for /usr/ports/devel/php5-pcre make_index: phpwebgallery-1.7.2: no entry for /usr/ports/devel/php5-pcre make_index: pear-Net_UserAgent_Mobile-1.0.0: no entry for /usr/ports/devel/php5-pcre make_index: netoffice-2.6.0b2_1: no entry for /usr/ports/devel/php5-pcre make_index: fruity-1.0.r2_3: no entry for /usr/ports/devel/php5-pcre make_index: campsite-2.6.7_5: no entry for /usr/ports/devel/php5-pcre make_index: campsite-2.6.7_5: no entry for /usr/ports/devel/php5-pcre make_index: roundcube-0.2.b,1: no entry for /usr/ports/devel/php5-pcre make_index: torrentflux-2.0.b1: no entry for /usr/ports/devel/php5-pcre make_index: habari-0.5.2: no entry for /usr/ports/devel/php5-pcre make_index: amavis-stats-0.1.12_2: no entry for /usr/ports/devel/php5-pcre make_index: eventum-2.1.1_1: no entry for /usr/ports/devel/php5-pcre make_index: dalbum-140.152_2: no entry for /usr/ports/devel/php5-pcre make_index: eyeOS-0.9.3.5: no entry for /usr/ports/devel/php5-pcre make_index: mywwwatcher-3.2: no entry for /usr/ports/devel/php5-pcre make_index: phpldapadmin-1.1.0.5_2,1: no entry for /usr/ports/devel/php5-pcre make_index: pgfouine-1.0_1: no entry for /usr/ports/devel/php5-pcre [...] make_index: ampache-3.4.3: no entry for /usr/ports/devel/php5-pcre make_index: adodb-4.99.1: no entry for /usr/ports/devel/php5-pcre make_index: adodb-5.06.a: no entry for /usr/ports/devel/php5-pcre make_index: ilohamail-0.8.13_1: no entry for /usr/ports/devel/php5-pcre make_index: twig-2.8.3_2: no entry for /usr/ports/devel/php5-pcre make_index: cakephp-1.1.19.6305_1: no entry for /usr/ports/devel/php5-pcre make_index: WebCalendar-1.0.5_1: no entry for /usr/ports/devel/php5-pcre make_index: xaraya-1.1.5: no entry for /usr/ports/devel/php5-pcre make_index: phpminiadmin-1.4.080217: no entry for /usr/ports/devel/php5-pcre make_index: pecl-zip-1.9.0: no entry for /usr/ports/devel/php5-pcre make_index: pecl-zip-1.9.0: no entry for /usr/ports/devel/php5-pcre make_index: joomla-1.0.15: no entry for /usr/ports/devel/php5-pcre make_index: snortsms-1.7.8: no entry for /usr/ports/devel/php5-pcre make_index: dokuwiki-20080505_1: no entry for /usr/ports/devel/php5-pcre make_index: asterisk-stat-2.0.1_4: no entry for /usr/ports/devel/php5-pcre make_index: phpmp-0.11.0_1: no entry for /usr/ports/devel/php5-pcre make_index: phpMyAdmin211-2.11.9.3: no entry for /usr/ports/devel/php5-pcre make_index: nocc-1.6_1: no entry for /usr/ports/devel/php5-pcre make_index: sqstat-1.20_1: no entry for /usr/ports/devel/php5-pcre make_index: lifetype-1.2.8: no entry for /usr/ports/devel/php5-pcre Committers on the hook: ale miwi stas Most recent CVS update was: U MOVED U comms/mgetty+sendfax/Makefile U comms/mgetty+sendfax/files/patch-CVE-2008-4936 U converters/php5-recode/Makefile U databases/php5-pdo_pgsql/Makefile U databases/php5-pdo_sqlite/files/patch-sqlite_statement.c U databases/php5-pgsql/Makefile U devel/php5-gettext/Makefile U devel/ruby-fam/Makefile U games/Makefile U games/bsdrain/Makefile U games/bsdrain/distinfo U games/bsdrain/pkg-descr U graphics/Makefile U graphics/silgraphite/Makefile U graphics/silgraphite/distinfo U graphics/silgraphite/pkg-descr U graphics/silgraphite/pkg-plist U graphics/silgraphite/files/patch-engine_Makefile.in U lang/php5/Makefile U lang/php5/Makefile.ext U lang/php5/distinfo U lang/php5/pkg-plist U lang/php5/files/patch-configure.in U lang/php5-extensions/Makefile U mail/php5-imap/Makefile U russian/xneur/Makefile U russian/xneur/distinfo U russian/xneur/pkg-plist U security/vuxml/vuln.xml U sysutils/spindown/Makefile U sysutils/spindown/distinfo U textproc/php5-pspell/Makefile U www/pecl-pecl_http/Makefile U www/pecl-pecl_http/distinfo From erwin at FreeBSD.org Sun Dec 7 08:04:46 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Sun Dec 7 08:04:52 2008 Subject: INDEX now builds successfully on 6.x Message-ID: <200812071604.mB7G4ZF9070318@pointyhat.freebsd.org> From hrs at FreeBSD.org Sun Dec 7 10:35:04 2008 From: hrs at FreeBSD.org (Hiroki Sato) Date: Sun Dec 7 10:35:16 2008 Subject: RFC: $USE_[GU]ID for consistent [GU]ID handling Message-ID: <20081208.033250.137441016.hrs@allbsd.org> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081207/019426de/attachment.pgp From hrs at FreeBSD.org Sun Dec 7 10:35:04 2008 From: hrs at FreeBSD.org (Hiroki Sato) Date: Sun Dec 7 10:35:17 2008 Subject: RFC: $OPTIONS in line-oriented terminal Message-ID: <20081208.031844.45215576.hrs@allbsd.org> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081207/42b27e56/attachment.pgp From nork at FreeBSD.org Sun Dec 7 10:41:47 2008 From: nork at FreeBSD.org (Norikatsu Shigemura) Date: Sun Dec 7 10:41:53 2008 Subject: RFC: $USE_[GU]ID for consistent [GU]ID handling In-Reply-To: <20081208.033250.137441016.hrs@allbsd.org> References: <20081208.033250.137441016.hrs@allbsd.org> Message-ID: <20081208034144.8db455fa.nork@FreeBSD.org> Hi Hiroki! On Mon, 08 Dec 2008 03:32:50 +0900 (JST) Hiroki Sato wrote: > The attached patch includes an example of rewrite of an existing > ports (japanese/sj3-server). After investigating ~300 ports in the > ports tree which add uid/gid I think the attached implementation can > cover most of the use case, but there may be something I missed. > Comments are welcome. Wow! That's cool! If this patch will be committed, I'll rewrite some my ports to USE_[GU]ID. From agabas at astabis.com Sun Dec 7 11:46:10 2008 From: agabas at astabis.com (=?iso-8859-1?Q?Albert_Gab=E0s_|_Astabis?=) Date: Sun Dec 7 11:46:23 2008 Subject: FreeBSD Port: php5-5.2.7 Message-ID: <000001c958a1$83531950$89f94bf0$@com> Dear Ale, I have updated the PHP to 5.2.7 version, and now some code give me the next error: [Sun Dec 07 19:46:00 2008] [error] [client X.X.X.X] PHP Warning: preg_replace() [function.preg-replace]: Internal pcre_fullinfo() error -3 in /usr/local/share/cacti/lib/functions.php on line 1924, referer: http://www.XXX.com/cacti/ PHP Version 5.2.7: Configure Command './configure' '--with-layout=GNU' '--with-config-file-scan-dir=/usr/local/etc/php' '--disable-all' '--enable-libxml' '--with-libxml-dir=/usr/local' '--with-pcre-regex=/usr/local' '--enable-reflection' '--program-prefix=' '--disable-cgi' '--with-apxs2=/usr/local/sbin/apxs' '--with-regex=php' '--with-zend-vm=CALL' '--disable-ipv6' '--prefix=/usr/local' '--mandir=/usr/local/man' '--infodir=/usr/local/info/' '--build=amd64-portbld-freebsd7.0' pcrePCRE (Perl Compatible Regular Expressions) Support enabled PCRE Library Version 3.9 02-Jan-2002 I'm trying to fix it without success. Well, If you know any fix, your help will be welcomed. Regards -- Albert Gab?s - Astabis Information Risk Management Movil: +34 687 733 222 | Oficina: +34 932 417 962 Directo: +34 931 145 262 | Fax: +34 932 400 545 SkypeID: albert.gabas From agabas at astabis.com Sun Dec 7 11:57:03 2008 From: agabas at astabis.com (=?iso-8859-1?Q?Albert_Gab=E0s_|_Astabis?=) Date: Sun Dec 7 11:57:09 2008 Subject: RV: FreeBSD Port: php5-5.2.7 Message-ID: <000001c958a5$f76f1470$e64d3d50$@com> Dear Ale, For me, the port installation works well when I have changed the --with-pcre-regex argument. CONFIGURE_ARGS= \ --with-layout=GNU \ --with-config-file-scan-dir=${PREFIX}/etc/php \ --disable-all \ --enable-libxml \ --with-libxml-dir=${LOCALBASE} \ **** --with-pcre-regex \ --enable-reflection \ --program-prefix="" Best regards -- Albert Gab?s - Astabis Information Risk Management Movil: +34 687 733 222 | Oficina: +34 932 417 962 Directo: +34 931 145 262 | Fax: +34 932 400 545 SkypeID: albert.gabas Le informamos que los datos personales que facilite/ha facilitado pasar?n a formar parte de un fichero responsabilidad de ASTABIS IRM, S.L. y que tiene por finalidad gestionar las relaciones con usted. Tiene derecho al acceso, rectificaci?n cancelaci?n y oposici?n en nuestro domicilio social sito en la calle Balmes, 297 1? 2? de Barcelona o a la direcci?n de e-mail lopd@astabis.com -----Mensaje original----- De: Albert Gab?s | Astabis [mailto:agabas@astabis.com] Enviado el: domingo, 07 de diciembre de 2008 20:25 Para: 'ale@FreeBSD.org' CC: 'ports@FreeBSD.org' Asunto: FreeBSD Port: php5-5.2.7 Importancia: Alta Dear Ale, I have updated the PHP to 5.2.7 version, and now some code give me the next error: [Sun Dec 07 19:46:00 2008] [error] [client X.X.X.X] PHP Warning: preg_replace() [function.preg-replace]: Internal pcre_fullinfo() error -3 in /usr/local/share/cacti/lib/functions.php on line 1924, referer: http://www.XXX.com/cacti/ PHP Version 5.2.7: Configure Command './configure' '--with-layout=GNU' '--with-config-file-scan-dir=/usr/local/etc/php' '--disable-all' '--enable-libxml' '--with-libxml-dir=/usr/local' '--with-pcre-regex=/usr/local' '--enable-reflection' '--program-prefix=' '--disable-cgi' '--with-apxs2=/usr/local/sbin/apxs' '--with-regex=php' '--with-zend-vm=CALL' '--disable-ipv6' '--prefix=/usr/local' '--mandir=/usr/local/man' '--infodir=/usr/local/info/' '--build=amd64-portbld-freebsd7.0' pcrePCRE (Perl Compatible Regular Expressions) Support enabled PCRE Library Version 3.9 02-Jan-2002 I'm trying to fix it without success. Well, If you know any fix, your help will be welcomed. Regards -- Albert Gab?s - Astabis Information Risk Management Movil: +34 687 733 222 | Oficina: +34 932 417 962 Directo: +34 931 145 262 | Fax: +34 932 400 545 SkypeID: albert.gabas From ale at FreeBSD.org Sun Dec 7 13:02:43 2008 From: ale at FreeBSD.org (Alex Dupre) Date: Sun Dec 7 13:02:52 2008 Subject: FreeBSD Port: php5-5.2.7 In-Reply-To: <000001c958a1$83531950$89f94bf0$@com> References: <000001c958a1$83531950$89f94bf0$@com> Message-ID: <493C39F1.6060903@FreeBSD.org> Albert Gab?s | Astabis wrote: > pcrePCRE (Perl Compatible Regular Expressions) Support enabled > PCRE Library Version 3.9 02-Jan-2002 3.9 ?! You have only half library ;-) (and a screwed up pcre installation) -- Alex Dupre From catone at cpan.org Sun Dec 7 13:40:04 2008 From: catone at cpan.org (Denis Pokataev) Date: Sun Dec 7 13:40:10 2008 Subject: [update req] FreeBSD Port: p5-Catalyst-Authentication-Store-DBIx-Class-0.106 Message-ID: <4638255b0812071309r6ab83d41t7d39126b60a56905@mail.gmail.com> Update request. Please, update port p5-Catalyst-Authentication-Store-DBIx-Class to latest cpan stable version ( 0.1082 at time of writing ). -- Regards, Denis. From bsd-unix at embarqmail.com Sun Dec 7 15:06:07 2008 From: bsd-unix at embarqmail.com (Randy Pratt) Date: Sun Dec 7 15:06:14 2008 Subject: php5-5.2.7 commit mail missing from cvs-ports list Message-ID: <20081207174605.0a54fb58.bsd-unix@embarqmail.com> I follow the cvs-ports mailing list and noticed that the recent commit for php5-5.2.7 never showed up on the list: http://docs.freebsd.org/mail/current/cvs-ports.html The cvsweb shows the commit as expected. I also checked the cvs-all mailing list but the php update is not listed there either. Any ideas as to why its missing? Its not a big thing but I've come to rely on the cvs-ports list for commits that affect my installed ports. Randy -- From jgelinas at tasam.com Sun Dec 7 15:46:11 2008 From: jgelinas at tasam.com (Joseph Gelinas) Date: Sun Dec 7 15:46:19 2008 Subject: php5-5.2.7 commit mail missing from cvs-ports list In-Reply-To: <20081207174605.0a54fb58.bsd-unix@embarqmail.com> References: <20081207174605.0a54fb58.bsd-unix@embarqmail.com> Message-ID: <493C603B.5090601@tasam.com> Randy Pratt wrote: > I follow the cvs-ports mailing list and noticed that the > recent commit for php5-5.2.7 never showed up on the > list: > > http://docs.freebsd.org/mail/current/cvs-ports.html > > The cvsweb shows the commit as expected. > > I also checked the cvs-all mailing list but the php update > is not listed there either. > > Any ideas as to why its missing? Its not a big thing but I've > come to rely on the cvs-ports list for commits that affect my > installed ports. > > Randy It is not missing. You may not have noticed it because the subject starts with MOVED etc. http://docs.FreeBSD.org/cgi/mid.cgi?200812071154.mB7Bsa5o058919 From jgelinas at tasam.com Sun Dec 7 15:50:38 2008 From: jgelinas at tasam.com (Joseph Gelinas) Date: Sun Dec 7 15:50:44 2008 Subject: FreeBSD Port: php5-5.2.7 In-Reply-To: <493C39F1.6060903@FreeBSD.org> References: <000001c958a1$83531950$89f94bf0$@com> <493C39F1.6060903@FreeBSD.org> Message-ID: <493C5B65.9000101@tasam.com> Alex Dupre wrote: > Albert Gab?s | Astabis wrote: >> pcrePCRE (Perl Compatible Regular Expressions) Support enabled >> PCRE Library Version 3.9 02-Jan-2002 > > 3.9 ?! You have only half library ;-) (and a screwed up pcre installation) > I have a similar issue. When --with-pcre-regex= is set to ${LOCALBASE} phpinfo() tells me I have PCRE Library Version 5.0 13-Sep-2004, however when that config option is set to nothing phpinfo() returns version 7.8. Is it possible there is a stray file somewhere from php5-pcre module that could cause this? From bsd-unix at embarqmail.com Sun Dec 7 15:58:53 2008 From: bsd-unix at embarqmail.com (Randy Pratt) Date: Sun Dec 7 15:59:00 2008 Subject: php5-5.2.7 commit mail missing from cvs-ports list In-Reply-To: <493C603B.5090601@tasam.com> References: <20081207174605.0a54fb58.bsd-unix@embarqmail.com> <493C603B.5090601@tasam.com> Message-ID: <20081207185851.ed44e56d.bsd-unix@embarqmail.com> On Sun, 07 Dec 2008 18:46:03 -0500 Joseph Gelinas wrote: > Randy Pratt wrote: > > I follow the cvs-ports mailing list and noticed that the > > recent commit for php5-5.2.7 never showed up on the > > list: > > > > http://docs.freebsd.org/mail/current/cvs-ports.html > > > > The cvsweb shows the commit as expected. > > > > I also checked the cvs-all mailing list but the php update > > is not listed there either. > > > > Any ideas as to why its missing? Its not a big thing but I've > > come to rely on the cvs-ports list for commits that affect my > > installed ports. > > > > Randy > > It is not missing. You may not have noticed it because the subject > starts with MOVED etc. > > http://docs.FreeBSD.org/cgi/mid.cgi?200812071154.mB7Bsa5o058919 Doh! ;-) I didn't catch the truncation in the summary list. I'll have to pay closer attention in the future. My apologies for the noise. I'll go back to my corner now. Randy -- From randy at psg.com Sun Dec 7 21:12:33 2008 From: randy at psg.com (Randy Bush) Date: Sun Dec 7 21:12:40 2008 Subject: sshguard-ipfw mashes /etc/syslog.conf Message-ID: <493CACBE.8050203@psg.com> if you already run sshguard-ipfw you have an entry in /etc/syslog.conf that you like. it would be nice if upgrade of sshguard-ipfw did not mash it with a new one that is commented out. it is the commenting out that really bites. randy From randy at psg.com Sun Dec 7 22:46:41 2008 From: randy at psg.com (Randy Bush) Date: Sun Dec 7 22:46:48 2008 Subject: p5-GSSAPI - missing dependency? In-Reply-To: <493CAE0B.70904@psg.com> References: <493BAB57.8070306@afrinic.net> <493BC77E.8040408@psg.com> <493BD04B.5070304@psg.com> <8CDC9BE6-C2CB-4424-8EA3-C4F1900080A2@afrinic.net> <493BDED3.9030306@psg.com> <493C1EC6.2060301@afrinic.net> <493C2156.3060206@nsrc.org> <493CAE0B.70904@psg.com> Message-ID: <493CC2CF.40405@psg.com> ---> Upgrade of security/p5-GSSAPI started at: Mon, 08 Dec 2008 04:24:31 +0000 ---> Upgrading 'p5-GSSAPI-0.23' to 'p5-GSSAPI-0.26' (security/p5-GSSAPI) ---> Build of security/p5-GSSAPI started at: Mon, 08 Dec 2008 04:24:31 +0000 ---> Building '/usr/ports/security/p5-GSSAPI' ===> Cleaning for p5-GSSAPI-0.26 ===> Vulnerability check disabled, database not found ===> Extracting for p5-GSSAPI-0.26 => MD5 Checksum OK for GSSAPI-0.26.tar.gz. => SHA256 Checksum OK for GSSAPI-0.26.tar.gz. ===> p5-GSSAPI-0.26 depends on file: /usr/local/bin/perl5.8.8 - found ===> Patching for p5-GSSAPI-0.26 ===> p5-GSSAPI-0.26 depends on file: /usr/local/bin/perl5.8.8 - found ===> p5-GSSAPI-0.26 depends on file: /usr/local/bin/perl5.8.8 - found ===> Configuring for p5-GSSAPI-0.26 Welcome to GSSAPI.pm setup! run "perl Makefile.PL --help" to see further installation options ---------------------------------------------------------- Searching krb5-config command... NOT FOUND! seems this is a missing prerequirement. The README file shipped with this module provides more information regarding prerequirements. Can't open Makefile: No such file or directory. ===> Building for p5-GSSAPI-0.26 ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.71799.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=p5-GSSAPI-0.23 UPGRADE_PORT_VER=0.23 make FETCH_BEFORE_ARGS=-q ** Fix the problem and try again. ---> Build of security/p5-GSSAPI ended at: Mon, 08 Dec 2008 04:24:33 +0000 (consumed 00:00:01) ---> Upgrade of security/p5-GSSAPI ended at: Mon, 08 Dec 2008 04:24:33 +0000 (consumed 00:00:01) From ale at FreeBSD.org Mon Dec 8 00:38:57 2008 From: ale at FreeBSD.org (Alex Dupre) Date: Mon Dec 8 00:39:03 2008 Subject: FreeBSD Port: php5-5.2.7 In-Reply-To: <493C5B65.9000101@tasam.com> References: <000001c958a1$83531950$89f94bf0$@com> <493C39F1.6060903@FreeBSD.org> <493C5B65.9000101@tasam.com> Message-ID: <493CDD1E.5080703@FreeBSD.org> Joseph Gelinas wrote: > Is it possible there is a stray file somewhere from php5-pcre module > that could cause this? It seems you have up-to-date include files, but a stray old libpcre.(a|so) library. Find it and destroy :-) -- Alex Dupre From bms at incunabulum.net Mon Dec 8 01:16:39 2008 From: bms at incunabulum.net (Bruce M Simpson) Date: Mon Dec 8 01:16:46 2008 Subject: Problem with aclocal, pkg.m4 and ports Message-ID: <493CE1EB.60107@incunabulum.net> Hi, I basically just ran into the same problem as this guy did, whilst trying to roll a FUSE port: http://lists.freebsd.org/pipermail/freebsd-questions/2008-April/172377.html It seems if I run the *same* aclocal binary from the command line, pkg.m4 is expanded in aclocal.m4 inside WRKSRC. But if I let it run from the Makefile targets, it doesn't. What's going on? I have reworked the port in progress to just push CPPFLAGS in the environment, obviously this isn't "the pkgconfig way". thanks, BMS From bugmaster at FreeBSD.org Mon Dec 8 03:06:05 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 8 03:06:30 2008 Subject: Current unassigned ports problem reports Message-ID: <200812081106.mB8B65Cx013295@freefall.freebsd.org> (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f ports/129493 [patch] - add two patches to deskutils/pypanel f ports/129490 Update games/wargus to latest version o ports/129489 lang/php5-5.2.7 breaks mediawiki, joomla, typo3 and mo o ports/129485 [patch] net-mgmt/ndoutil rc script f ports/129478 multimedia/acidrip: patch file to commit to ports f ports/129453 ports-mgmt/jailaudit does not work since jail supporti f ports/129439 devel/libusb does not compile in FreeBSD 7.0-RELEASE f ports/129435 java/jakarta-commons-dbcp not BROKEN on jdk15 o ports/129411 Fix shutdown script for www/tomcat6 o ports/129402 New port: www/Template-Provider-FromDATA - load templa f ports/129369 Failed to build multimedia/mencoder with samba support f ports/129296 [PATCH] net-im/pidgin-libnotify: add Russian translati o ports/129271 www/jakarta-tomcatX are obsolete f ports/129063 Update math/R to version 2.8.0 o ports/129043 Experimental version of net/poptop in FreeBSD ports o ports/128952 [NEW PORT] java/javadb: Sun's supported distribution o o ports/128846 New port: sysutils/linux-megacli2 - LSI MegaRAID SAS c o ports/128726 [NEW PORT] print/lyx16: Document processor interfaced f ports/128703 net/isc-dhcp40-client and net/isc-dhcp40-relay refer t o ports/128603 textproc/flex has too small capacity o ports/128558 New ports: emulators/sdlmame-devel f ports/128537 [patch] databases/rrdtool add missing font runtime dep f ports/128490 net/freenx port does not work properly on freebsd-7 st f ports/128489 [PATCH] mail/sympa5 update to 5.4.3 o ports/128384 new port x11/xorg-minimal f ports/128323 Update of ports/x11-fonts/terminus-font f ports/128288 sysutils/hpacucli does not work f ports/128271 biology/ncbi-toolkit - blastall segfaults when output o ports/128241 update www/geronimo to 2.1.3 o ports/128140 update devel/pwlib to 2.4.1 to fit GNOME 2.24 f ports/128082 sysutils/megarc binary causes memory corruption f ports/128074 multimedia/mplayer does not play CSS encrypted DVDs f ports/128048 www/mod_proxy_html port installs broken configuration f ports/127995 net/isc-dhcp30-server creates a user/group with dynami f ports/127905 science/gramps: installation and runtime problems with f ports/127854 [PATCH] databases/couchdb: update to 0.8.1 o ports/127851 Port update: multimedia/libdvdnav-mplayer - Update to f ports/127810 print/hplip 2.8.2 can't talk to my usnb printer (HP PS o ports/127728 ports/games/freebsd-games doesn't build, and larn(6) s f ports/127513 mail/dcc-dccd sets home to /var/dcc even if you didn' o ports/127321 japanese/kon2-16dot: buffer overflow and mouse bugs o ports/127306 [patch] Upgrade www/tomcat6 to 6.0.18 f ports/127302 security/swatch: swatch-3.2.1_1 multiple issues f ports/127181 audio/musicpd logs warning s ports/127087 mail/bincimap port does not include an rc.d file o ports/126905 Update port: audio/libmtp to version 0.3.1 o ports/126890 port update: lang/cmucl o ports/126674 New port: print/latex-babel o ports/126655 java/jboss4 can not take standard parameter "-b host_n s ports/126577 [Update]graphics/qgis:update to 0.11.0 f ports/126518 Unbroke archivers/lzo2 on i386 f ports/126322 [patch] sysutils/fusefs-kmod: Make install location co f ports/126228 [PATCH] mail/courier: new version 0.60.0 f ports/126161 security/bsp_upektfmess does not work on 7.0 f ports/126058 net/generic-nqs fails to compile f ports/126055 x11-toolkits/p5-Tk - segmentation fault running perl-t f ports/125960 sysutils/syscp lacks of chattr/chflags o ports/125719 shells/pdksh, zombie process's occouring on SMP Machin o ports/125714 [patch] www/httptunnel: users not added f ports/125362 New port: devel/ocaml-lwt (cooperative threading libra o ports/125324 editors/the (3.2) looses cursor when compiled with PDC o ports/125266 [Update]biology/biojava:update to 1.6 o ports/125201 audio/aqualung crashes o ports/124905 new port: databases/sqlitejdbc 051 o ports/124597 [NEW PORT] net/callweaver: Fork of the popular Open So o ports/124548 net/mDNSResponder port incompatible with gnome desktop f ports/124238 sysutils/heartbeat: patch request f ports/123424 [NEW PORT] net/winexe o ports/123247 linux-firefox and linux-seamonkey from multiple users o ports/123239 New port: graphics/diamondbox Layer based photo editor f ports/122276 Compiled audio/musicpd segfaults on FreeBSD 7.0 o ports/121831 [PATCH] net/openbgpd: [SUMMARIZE CHANGES] o ports/121325 Xorg crashes when x11-wm/xcompmgr is running o ports/121259 New port: net/openamq OpenAMQ is a complete AMQP messa o ports/121050 New port: sysutils/heartbeat2 Linux High-Availability f ports/119183 [NEW PORT] net/freeradius-client: FreeRADIUS Client li f ports/118877 audio/streamripper does not detect song title from str f ports/116385 net/vnc using vnc.so crashes Xorg 7.3 when remote comp f ports/115304 multimedia/gpac-mp4box cannot import files larger than o ports/108795 ports/icc: Proposed update to icc port for intel compi f ports/107304 print/apsfilter does not print PDF to raw PostScript p o amd64/104311 ports/wine should be installable on amd64 s ports/85513 Intel C++ compiler not 100% binary compatible with sys 83 problems total. From ale at FreeBSD.org Mon Dec 8 03:44:40 2008 From: ale at FreeBSD.org (Alex Dupre) Date: Mon Dec 8 03:44:46 2008 Subject: FreeBSD Port: php5-5.2.7 In-Reply-To: <493CDD1E.5080703@FreeBSD.org> References: <000001c958a1$83531950$89f94bf0$@com> <493C39F1.6060903@FreeBSD.org> <493C5B65.9000101@tasam.com> <493CDD1E.5080703@FreeBSD.org> Message-ID: <493D08A5.9000304@FreeBSD.org> Alex Dupre wrote: >> Is it possible there is a stray file somewhere from php5-pcre module >> that could cause this? I think to have found the root cause: apache2 ports use an old bundled pcre library and mod_php picks up such wrong library. I'm working with clement to fix this issue, in the meantime as temporary fix you can modify the php5 port to use the bundled library, or select the pcre port from the apache2 options menu. -- Alex Dupre From avg at icyb.net.ua Mon Dec 8 04:50:33 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Mon Dec 8 04:50:39 2008 Subject: ktorrent changes Message-ID: <493D1815.7030601@icyb.net.ua> > 20081205: > AFFECTS: users of net-p2p/ktorrent > AUTHOR: makc@FreeBSD.org > > ktorrent has been updated to 3.1.5 for KDE 4. The last release of ktorrent > for KDE 3 is available under net-p2p/ktorrent2. Shouldn't this be somehow reflected in MOVED file so that KDE3 users don't do a harmful UPDATE whilst KDE4 users would need explicitly switch ktorrent version. Or am I confused? -- Andriy Gapon From bseklecki at collaborativefusion.com Mon Dec 8 11:31:30 2008 From: bseklecki at collaborativefusion.com (Brian A. Seklecki) Date: Mon Dec 8 11:31:36 2008 Subject: FreeBSD Port: php5-5.2.7 In-Reply-To: <000001c958a1$83531950$89f94bf0$@com> References: <000001c958a1$83531950$89f94bf0$@com> Message-ID: <1228763086.2805.606.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> On Sun, 2008-12-07 at 20:25 +0100, Albert Gab?s | Astabis wrote: > Dear Ale, > > I have updated the PHP to 5.2.7 version, and now some code give me the > next error: Looks like 5.2.7 got off'd anyway. 5.2.8 pushed. They must be working with the MySQL folks on release engineering... ~BAS -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081208/e63a7e44/attachment.pgp From mail at ozzmosis.com Mon Dec 8 12:28:25 2008 From: mail at ozzmosis.com (andrew clarke) Date: Mon Dec 8 12:28:32 2008 Subject: sshguard-ipfw mashes /etc/syslog.conf In-Reply-To: <493CACBE.8050203@psg.com> References: <493CACBE.8050203@psg.com> Message-ID: <20081208200142.GA68373@ozzmosis.com> On Mon 2008-12-08 14:12:30 UTC+0900, Randy Bush (randy@psg.com) wrote: > if you already run sshguard-ipfw you have an entry in /etc/syslog.conf > that you like. it would be nice if upgrade of sshguard-ipfw did not > mash it with a new one that is commented out. it is the commenting out > that really bites. Seconded. Since reading this I just noticed sshguard-ipfw hasn't been running on my server ever since I ran "portmaster sshguard-ipfw" to rebuild it. (I upgraded from FreeBSD 6.3 to 6.4 recently and took the opportunity to rebuild all my installed ports...) I really wasn't expecting "make deinstall" to comment it out! From jgelinas at tasam.com Mon Dec 8 13:00:38 2008 From: jgelinas at tasam.com (Joseph Gelinas) Date: Mon Dec 8 13:00:44 2008 Subject: FreeBSD Port: php5-5.2.7 In-Reply-To: <493D08A5.9000304@FreeBSD.org> References: <000001c958a1$83531950$89f94bf0$@com> <493C39F1.6060903@FreeBSD.org> <493C5B65.9000101@tasam.com> <493CDD1E.5080703@FreeBSD.org> <493D08A5.9000304@FreeBSD.org> Message-ID: On Mon, 8 Dec 2008, Alex Dupre wrote: > Alex Dupre wrote: >>> Is it possible there is a stray file somewhere from php5-pcre module that >>> could cause this? > > I think to have found the root cause: apache2 ports use an old bundled pcre > library and mod_php picks up such wrong library. I'm working with clement to > fix this issue, in the meantime as temporary fix you can modify the php5 port > to use the bundled library, or select the pcre port from the apache2 options > menu. > Yeah, the pcre from ports apache option is certainly a better fix than local edits to the php5 Makefile. Thanks for looking into it and for the continued porting effort. From bengta at sics.se Mon Dec 8 14:15:48 2008 From: bengta at sics.se (Bengt Ahlgren) Date: Mon Dec 8 14:16:11 2008 Subject: print/acroread8: LD_LIBRARY_PATH breaks helper programs Message-ID: Hi! When testing acroread8 (on 7.1-PRE) I got the following error when trying to print using KDE's kprinter on i386: The following error occurred while printing... '/libexec/ld-elf.so.1: /usr/local/Adobe/Reader8/ENU/Adobe/Reader8/Reader/intellinux/lib/libstdc++.so.6: unsupported file layout' and on amd64: The following error occurred while printing... '/libexec/ld-elf.so.1: Shared object "libm.so.6" not found, required by "libstdc++.so.6"' The reason is that the acroread launch script sets LD_LIBRARY_PATH to: LD_LIBRARY_PATH=/usr/local/Adobe/Reader8/ENU/Adobe/Reader8/Reader/intellinux/lib:/usr/local/Adobe/Reader8/ENU/Adobe/Reader8/Reader/intellinux/sidecars:/..//usr/local/lib/linux-nvu which makes (some) helper programs fail to link its shared libs if it happens to pick up a (Linux) library from the above. libstdc++.so.6 is one of them. The problem is easily worked around for the print program - you can do "env -u LD_LIBRARY_PATH kprinter" for instance directly in the print dialogue. But that does not work for the browser executable set in the "edit/preferences/internet" dialogue. So if you want to be able to launch a browser from acroread, you need a wrapper script. Question: is there a proper fix for these problems??? I see that the Linux dynamic linker (/usr/compat/linux/lib/ld-linux.so.2) has a flag: --library-path PATH use given PATH instead of content of the environment variable LD_LIBRARY_PATH so I tried to patch the acroread launch script in /usr/local/Adobe/Reader8/ENU/Adobe/Reader8/bin with: --- acroread.orig 2008-10-08 06:28:27.000000000 +0200 +++ acroread 2008-12-08 22:59:46.000000000 +0100 @@ -16,7 +16,9 @@ LaunchBinary() { if [ "`uname -s`" = "Linux" ] && [ ! -x /lib/ld-lsb.so.3 ]; then - exec /lib/ld-linux.so.2 ${1+"$@"} + TEMP_LIB_PATH="$LD_LIBRARY_PATH" + unset LD_LIBRARY_PATH + exec /lib/ld-linux.so.2 --library-path "$TEMP_LIB_PATH" ${1+"$@"} else exec ${1+"$@"} fi which indeed works! Bengt From mij at bitchx.it Mon Dec 8 14:57:25 2008 From: mij at bitchx.it (Mij) Date: Mon Dec 8 14:57:56 2008 Subject: sshguard-ipfw mashes /etc/syslog.conf In-Reply-To: <20081208200142.GA68373@ozzmosis.com> References: <493CACBE.8050203@psg.com> <20081208200142.GA68373@ozzmosis.com> Message-ID: Interesting and relevant observation. If you have a patch for it, it's welcome. Otherwise be patient, I'm too busy for taking care of this in these very weeks. On Dec 8, 2008, at 21:01 , andrew clarke wrote: > On Mon 2008-12-08 14:12:30 UTC+0900, Randy Bush (randy@psg.com) wrote: > >> if you already run sshguard-ipfw you have an entry in /etc/ >> syslog.conf >> that you like. it would be nice if upgrade of sshguard-ipfw did not >> mash it with a new one that is commented out. it is the commenting >> out >> that really bites. > > Seconded. > > Since reading this I just noticed sshguard-ipfw hasn't been running on > my server ever since I ran "portmaster sshguard-ipfw" to rebuild it. > (I upgraded from FreeBSD 6.3 to 6.4 recently and took the opportunity > to rebuild all my installed ports...) > > I really wasn't expecting "make deinstall" to comment it out! From gurdiga at gmail.com Tue Dec 9 01:32:02 2008 From: gurdiga at gmail.com (Vlad GURDIGA) Date: Tue Dec 9 01:32:08 2008 Subject: FreeBSD Port: php5-5.2.8 Message-ID: Hello! When I make install a port, I see something like: Build complete. Don't forget to run 'make test'. Do we have a "make test" for the lang/php5 port? From ale at FreeBSD.org Tue Dec 9 02:21:36 2008 From: ale at FreeBSD.org (Alex Dupre) Date: Tue Dec 9 02:21:43 2008 Subject: FreeBSD Port: php5-5.2.8 In-Reply-To: References: Message-ID: <493E46AC.1080909@FreeBSD.org> Vlad GURDIGA ha scritto: > Do we have a "make test" for the lang/php5 port? Yes, but the message is printed by the php makefile, not port makefile. You have to know also that the suhosin patch will make a few tests failing. -- Alex Dupre From rhurlin at gwdg.de Tue Dec 9 02:22:52 2008 From: rhurlin at gwdg.de (Rainer Hurling) Date: Tue Dec 9 02:22:59 2008 Subject: print/cm-super installation error Message-ID: <493E3168.9010809@gwdg.de> Hi list, when I try to install the port print/cm-super from sources I get the following error on several machines: ---------------------------------------- ===> Installing for cm-super-0.3.4 ===> cm-super-0.3.4 depends on executable: mktexlsr - found ===> Generating temporary packing list ===> Checking if print/cm-super already installed /bin/mkdir -p /usr/local/share/fonts/cm-super/afm install -o root -g wheel -m 444 /usr/ports/print/cm-super/work/cm-super/afm/* [.. snip ..] mktexlsr: Updating /usr/local/share/texmf/ls-R... mktexlsr: Done. Adding cm-super-t1.map... *** Error code 1 ---------------------------------------- Obviously there is something wrong with 'updmap-sys'. After commenting out the option '--quiet' in print/cm-super/Makefile (line 37) I get this messages: ---------------------------------------- ===> Installing for cm-super-0.3.4 ===> cm-super-0.3.4 depends on executable: mktexlsr - found ===> Generating temporary packing list ===> Checking if print/cm-super already installed /bin/mkdir -p /usr/local/share/fonts/cm-super/afm install -o root -g wheel -m 444 /usr/ports/print/cm-super/work/cm-super/afm/* [.. snip ..] mktexlsr: Updating /usr/local/share/texmf/ls-R... mktexlsr: Done. Adding cm-super-t1.map... updmap: This is updmap, version 1107552857 updmap: using transcript file `/usr/local/share/texmf-var/web2c/updmap.log' updmap: initial config file is `/usr/local/share/texmf-config/web2c/updmap.cfg' updmap: configuration (updmap.cfg) unchanged. *** Error code 1 ---------------------------------------- Is it a known error or is something misconfigured within my teTeX installation? This is on FreeBSD 8.0-CURRENT from yesterday (i386). Please let me know if you need more information. Thanks in advance, Rainer Hurling From ale at FreeBSD.org Tue Dec 9 02:28:13 2008 From: ale at FreeBSD.org (Alex Dupre) Date: Tue Dec 9 02:28:19 2008 Subject: RFC: $USE_[GU]ID for consistent [GU]ID handling In-Reply-To: <20081208.033250.137441016.hrs@allbsd.org> References: <20081208.033250.137441016.hrs@allbsd.org> Message-ID: <493E41FB.7060904@FreeBSD.org> Hiroki Sato ha scritto: > I would like your comments about the attached patch. Not tested, but it's a great idea. BTW, a lot of ports still check for / add www uid/gid, but actually we have such user in base system in all supported releases. Can/Should we drop such checks? -- Alex Dupre From mike at reifenberger.com Tue Dec 9 04:05:59 2008 From: mike at reifenberger.com (Michael Reifenberger) Date: Tue Dec 9 04:06:08 2008 Subject: llvm-c++ fails to compile/link trivial c++ program Message-ID: Hi, compiling the attached program test2.c++ using `llvm-c++ -Wall test2.c++` gives: /usr/bin/ld: BFD 2.15 [FreeBSD] 2004-05-23 assertion fail elf64-amd64-fbsd.c:2166 /usr/bin/ld: BFD 2.15 [FreeBSD] 2004-05-23 assertion fail elf64-amd64-fbsd.c:2166 Is our linker too old or is it a llvm-gcc bug? Or an interference with the base compiler? I'm using the current llvm and llvm-gcc ports on FreeBSD RELENG_7 amd64. BTW: commenting out the '#include ' line fixes the error... Bye/2 --- Michael Reifenberger Michael@Reifenberger.com http://www.Reifenberger.com From wahjava.ml at gmail.com Tue Dec 9 05:18:29 2008 From: wahjava.ml at gmail.com (Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IA==?= =?utf-8?B?4KS24KWB4KSV4KWN4KSy?=) Date: Tue Dec 9 05:19:05 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles Message-ID: <87fxkxjywk.fsf@chateau.d.lf> Hi all, I'm to proposing an enhancement to existing FreeBSD ports system. I think it'll be great if ports can use SCM (source code management) repositories like CVS, Subversion, Git, etc. as their sources instead of distfiles. Following are some of the {dis,}advantages of this approach: * Anyone interested in tracking the development branch of any project can do so with installation/deinstallation of the project integrated in the ports management system. e.g. anyone interested in trying out GNU Emacs CVS version, can simply use editors/emacs-cvs (not-implemented atm), which will checkout from the Emacs's CVS repository and build and install the port with all installed files recorded in 'plist' of the port. And if anyone wants to uninstall the Emacs CVS port, {s,}he can simply deinstall it in their preferred ports/package way. * ATM, development versions of ports are packaged as snapshots, and maintainer has to keep updating ports snapshots. And sometimes, it is not possible for maintainer (due to lack of time and other issues) to update snapshots timely. So going proposed way can ease the work for them, and beneficial for users who are interested in latest bits. * As far as PR related to such ports are concerned I think one should directly submit them to the upstream rather than maintainer, unless that PR has anything to do with its packaging, in which case it should be submitted to FreeBSD PR system. * I've not played (or worked) with dynamic packaging lists on FreeBSD, so I'm not sure if it is possible to properly track all installed files dynamically, e.g. if a new commit in the upstream causes 3 new files to be installed, then is it possible for FreeBSD ports management system to include those 3 files also in the packing list, in the next installation of the port, hmm...? BtW, I've implemented a basic proof-of-concept and hacked a port audio/scrobby (for scrobby[1] application, not submitted to PR system yet) based on proof-of-concept. The shar can be downloaded from following URL: http://wahjava.googlepages.com/scm-ports.shar (md5: 7f8392e7c9e31fe5842279e1730a2051, size: 4710 bytes) Some existing tools like patchtool also needs to be modified which rely for the presence of 'distinfo' file in the port directory, which in this case will never be present. References: [1] - http://unkart.ovh.org/scrobby/ Thanks for trying it. -- Ashish Shukla -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081209/ddd55f96/attachment.pgp From amdmi3 at amdmi3.ru Tue Dec 9 06:31:16 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Tue Dec 9 06:31:24 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <87fxkxjywk.fsf@chateau.d.lf> References: <87fxkxjywk.fsf@chateau.d.lf> Message-ID: <20081209143052.GA29817@hades.panopticon> * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: > I'm to proposing an enhancement to existing FreeBSD ports system. I > think it'll be great if ports can use SCM (source code management) > repositories like CVS, Subversion, Git, etc. as their sources instead of > distfiles. Following are some of the {dis,}advantages of this approach: This was discussed before. The summary: this won't work with ports. Reasons: - No way to track port updates. - No way to save distfile. Source will be redownloaded on every rebuild. - Security. No one can guarantee that malicious source won't be cheched into the repository at some random time. Fixed versions can be at least minimally checked and it is possible to not update the port to new version if it contains problems and/or tell users to not install version XXX. Impossible for SCM-based ports. > * ATM, development versions of ports are packaged as snapshots, and > maintainer has to keep updating ports snapshots. And sometimes, > it is not possible for maintainer (due to lack of time and other > issues) to update snapshots timely. So going proposed way can ease the > work for them, and beneficial for users who are interested in latest > bits. - _Much_ more (instead of less) work for maintainer, as he won't be able to test the port before committing it and will have to deal with all the problems post factum, under extra pressure. - Actually, any SCM-based port will become broken rather soon than later with no ability to prevent it. The port uses patches? Due to mutable source it'll become broken. Any structural change upstream? Port broken. Changed build system? Broken. Changed paths? Broken. Changed depends? Broken. Changed options/configure args? Broken. Etc. > * I've not played (or worked) with dynamic packaging lists on FreeBSD, > so I'm not sure if it is possible to properly track all installed > files dynamically, e.g. if a new commit in the upstream causes 3 new > files to be installed, then is it possible for FreeBSD ports > management system to include those 3 files also in the packing list, > in the next installation of the port, hmm...? - Generic dynamic plist generation is impossible unless the port is installed into some clean chrooted environemnt (for example, using DESTDIR). The latter, however takes extra space and time, as you need the whole system and all dependent packages installed there as well. Simply building the port will become more more like producing package in a tinderbox: - unpack the system image - mount all required filesystems - devfs, ports, distfiles, packages - install all required packages - take list of all files in the chroot - chroot and install the port - take list of all files in the chroot, compare with previous one and make a plist out of it - umount and remove everything - now you have package and may install in normally > * As far as PR related to such ports are concerned I think one should > directly submit them to the upstream rather than maintainer, unless > that PR has anything to do with its packaging, in which case it should > be submitted to FreeBSD PR system. Sometimes it's hard to tell whether the problem is FreeBSD-specific. Also, upstream is unlikely to have FreeBSD box for testing, so again it'll be more work for maintainer. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From flz at xbsd.org Tue Dec 9 08:28:46 2008 From: flz at xbsd.org (Florent Thoumie) Date: Tue Dec 9 08:28:52 2008 Subject: RFC: $USE_[GU]ID for consistent [GU]ID handling In-Reply-To: <20081208.033250.137441016.hrs@allbsd.org> References: <20081208.033250.137441016.hrs@allbsd.org> Message-ID: On Sun, Dec 7, 2008 at 6:32 PM, Hiroki Sato wrote: > Hello, > > I would like your comments about the attached patch. This is for > adding USE_UID and USE_GID which allow uid/gid addition on > installation and the removal on deinstallation. It uses > ${PORTSDIR}/[GU]IDs for the detail information and can eliminate > complex shell scripts from individual ports. > > For example, if you define > > USE_UID= foo > > in Makefile, the uid "foo" is added before pre-su-install, and > removed on deinstallation by using pw(8). If the uid already exists, > no error occurred. The multiple uids are also allowed. > > The attached patch includes an example of rewrite of an existing > ports (japanese/sj3-server). After investigating ~300 ports in the > ports tree which add uid/gid I think the attached implementation can > cover most of the use case, but there may be something I missed. > Comments are welcome. Hi Hiroki-san, There's an open PR with patches for this feature (ports/108514). Could you have a look and maybe send your comments? -- Florent Thoumie flz@FreeBSD.org FreeBSD Committer From wahjava.ml at gmail.com Tue Dec 9 09:04:21 2008 From: wahjava.ml at gmail.com (Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IA==?= =?utf-8?B?4KS24KWB4KSV4KWN4KSy?=) Date: Tue Dec 9 09:04:28 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081209143052.GA29817@hades.panopticon> (Dmitry Marakasov's message of "Tue, 9 Dec 2008 17:30:52 +0300") References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> Message-ID: <873agxjn1x.fsf@chateau.d.lf> Dmitry Marakasov writes: > * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: >> I'm to proposing an enhancement to existing FreeBSD ports system. I >> think it'll be great if ports can use SCM (source code management) >> repositories like CVS, Subversion, Git, etc. as their sources instead of >> distfiles. Following are some of the {dis,}advantages of this approach: > This was discussed before. The summary: this won't work with ports. > Reasons: > - No way to track port updates. > - No way to save distfile. Source will be redownloaded on every rebuild. > - Security. No one can guarantee that malicious source won't be cheched > into the repository at some random time. Fixed versions can be at > least minimally checked and it is possible to not update the port to > new version if it contains problems and/or tell users to not install > version XXX. Impossible for SCM-based ports. >> * ATM, development versions of ports are packaged as snapshots, and >> maintainer has to keep updating ports snapshots. And sometimes, >> it is not possible for maintainer (due to lack of time and other >> issues) to update snapshots timely. So going proposed way can ease the >> work for them, and beneficial for users who are interested in latest >> bits. > - _Much_ more (instead of less) work for maintainer, as he won't be able > to test the port before committing it and will have to deal with all > the problems post factum, under extra pressure. > - Actually, any SCM-based port will become broken rather soon than > later with no ability to prevent it. > The port uses patches? Due to mutable source it'll become broken. > Any structural change upstream? Port broken. Changed build system? > Broken. Changed paths? Broken. Changed depends? Broken. Changed > options/configure args? Broken. Etc. These are the problems already expected with this but the only suggestion is to have PRs filed if anything breaks during compilation and investigate what caused it. >> * I've not played (or worked) with dynamic packaging lists on FreeBSD, >> so I'm not sure if it is possible to properly track all installed >> files dynamically, e.g. if a new commit in the upstream causes 3 new >> files to be installed, then is it possible for FreeBSD ports >> management system to include those 3 files also in the packing list, >> in the next installation of the port, hmm...? > - Generic dynamic plist generation is impossible unless the port > is installed into some clean chrooted environemnt (for example, > using DESTDIR). The latter, however takes extra space and time, > as you need the whole system and all dependent packages installed > there as well. Simply building the port will become more more like > producing package in a tinderbox: > - unpack the system image > - mount all required filesystems - devfs, ports, distfiles, packages > - install all required packages > - take list of all files in the chroot > - chroot and install the port > - take list of all files in the chroot, compare with previous one and > make a plist out of it > - umount and remove everything > - now you have package and may install in normally So, this is the main reason which prevents this :( . >> * As far as PR related to such ports are concerned I think one should >> directly submit them to the upstream rather than maintainer, unless >> that PR has anything to do with its packaging, in which case it should >> be submitted to FreeBSD PR system. > Sometimes it's hard to tell whether the problem is FreeBSD-specific. > Also, upstream is unlikely to have FreeBSD box for testing, so again > it'll be more work for maintainer. True, so either have all PRs should be submitted to FreeBSD PR system, where maintainer will decide if its porting issue or upstream related issue. So with all the problems you mentioned above, I guess, I'll take my proposal back :) . Thanks for your comments. -- Ashish Shukla -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081209/2b961228/attachment.pgp From peter.schuller at infidyne.com Tue Dec 9 09:43:49 2008 From: peter.schuller at infidyne.com (Peter Schuller) Date: Tue Dec 9 09:43:56 2008 Subject: print/cm-super installation error In-Reply-To: <493E3168.9010809@gwdg.de> References: <493E3168.9010809@gwdg.de> Message-ID: <20081209174347.GA69765@hyperion.scode.org> > [.. snip ..] > mktexlsr: Updating /usr/local/share/texmf/ls-R... > mktexlsr: Done. > Adding cm-super-t1.map... > *** Error code 1 [snip] > Is it a known error or is something misconfigured within my teTeX > installation? FWIW I get this too, also on 8.0-CURRENT. I have not investigated. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081209/e0adb47f/attachment.pgp From amdmi3 at amdmi3.ru Tue Dec 9 10:14:18 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Tue Dec 9 10:14:27 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <873agxjn1x.fsf@chateau.d.lf> References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> Message-ID: <20081209181354.GB29817@hades.panopticon> * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: > > - _Much_ more (instead of less) work for maintainer, as he won't be able > > to test the port before committing it and will have to deal with all > > the problems post factum, under extra pressure. > > > - Actually, any SCM-based port will become broken rather soon than > > later with no ability to prevent it. > > The port uses patches? Due to mutable source it'll become broken. > > Any structural change upstream? Port broken. Changed build system? > > Broken. Changed paths? Broken. Changed depends? Broken. Changed > > options/configure args? Broken. Etc. > > These are the problems already expected with this but the only > suggestion is to have PRs filed if anything breaks during compilation > and investigate what caused it. No, those problems will not arise as long as the maintainer tests the port before submitting an update. And the tested port of fixed version will be usable for a long time, unlike SCM-based one which may break every second. > > - Generic dynamic plist generation is impossible unless the port > > is installed into some clean chrooted environemnt (for example, > > using DESTDIR). The latter, however takes extra space and time, > > as you need the whole system and all dependent packages installed > > there as well. > > So, this is the main reason which prevents this :( . I'd say it's the least significant reason. The main reasons are the first three which can be shortened as `the port will be unuseable and sometimes dangerous'. What's for automatic plist generation, I've given it some thought, and it seems like there could be a more or less reliable way after all. I'm currently doing some experiments. > > Sometimes it's hard to tell whether the problem is FreeBSD-specific. > > Also, upstream is unlikely to have FreeBSD box for testing, so again > > it'll be more work for maintainer. > > True, so either have all PRs should be submitted to FreeBSD PR system, > where maintainer will decide if its porting issue or upstream related > issue. My opinion is that if you can diagnose the problem by yourself and come with a proper fix, you should submit it directly upstream. If you think that the problem is serious enough, you can send a port PR as well. If you cannot do it all by yourself though, you should submit a PR, in which case port's maintainer will take care of it. > So with all the problems you mentioned above, I guess, I'll take my > proposal back :) . It's not like your proposal is bad, ports instantaneously tracking upstream changes and not needing maintainers would really be cool, but unfortunately that's practically impossible. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From wahjava.ml at gmail.com Tue Dec 9 10:57:36 2008 From: wahjava.ml at gmail.com (Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IA==?= =?utf-8?B?4KS24KWB4KSV4KWN4KSy?=) Date: Tue Dec 9 10:57:43 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081209181354.GB29817@hades.panopticon> (Dmitry Marakasov's message of "Tue, 9 Dec 2008 21:13:54 +0300") References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> <20081209181354.GB29817@hades.panopticon> Message-ID: <87tz9di38u.fsf@chateau.d.lf> Dmitry Marakasov writes: > * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: >> > - _Much_ more (instead of less) work for maintainer, as he won't be able >> > to test the port before committing it and will have to deal with all >> > the problems post factum, under extra pressure. >> >> > - Actually, any SCM-based port will become broken rather soon than >> > later with no ability to prevent it. >> > The port uses patches? Due to mutable source it'll become broken. >> > Any structural change upstream? Port broken. Changed build system? >> > Broken. Changed paths? Broken. Changed depends? Broken. Changed >> > options/configure args? Broken. Etc. >> >> These are the problems already expected with this but the only >> suggestion is to have PRs filed if anything breaks during compilation >> and investigate what caused it. > No, those problems will not arise as long as the maintainer tests the > port before submitting an update. And the tested port of fixed version > will be usable for a long time, unlike SCM-based one which may break > every second. That is true, but the only problem I see with snapshots is, if maintainer is busy you can't do anything except maintaining your own local port version on your box. And anyone using these SCM ports is the one who knows things can go wrong often, and this is only for development use. >> > - Generic dynamic plist generation is impossible unless the port >> > is installed into some clean chrooted environemnt (for example, >> > using DESTDIR). The latter, however takes extra space and time, >> > as you need the whole system and all dependent packages installed >> > there as well. >> >> So, this is the main reason which prevents this :( . > I'd say it's the least significant reason. The main reasons are the > first three which can be shortened as `the port will be unuseable and > sometimes dangerous'. > What's for automatic plist generation, I've given it some thought, > and it seems like there could be a more or less reliable way after all. > I'm currently doing some experiments. Cool, would like to see the results of your experiments :). >> > Sometimes it's hard to tell whether the problem is FreeBSD-specific. >> > Also, upstream is unlikely to have FreeBSD box for testing, so again >> > it'll be more work for maintainer. >> >> True, so either have all PRs should be submitted to FreeBSD PR system, >> where maintainer will decide if its porting issue or upstream related >> issue. > My opinion is that if you can diagnose the problem by yourself and come > with a proper fix, you should submit it directly upstream. If you think > that the problem is serious enough, you can send a port PR as well. If > you cannot do it all by yourself though, you should submit a PR, in > which case port's maintainer will take care of it. I agree. >> So with all the problems you mentioned above, I guess, I'll take my >> proposal back :) . > It's not like your proposal is bad, ports instantaneously tracking > upstream changes and not needing maintainers would really be cool, > but unfortunately that's practically impossible. Gentoo GNU/Linux which is a source-based GNU/Linux distribution has this feature available, what is different in that is, that it uses a separate root for recording the packing list port and optionally creating a package. Maybe we can introduce a hack in ports system like by adding some variable like 'USES_DYNAMIC_PLIST=yes' in Makefile, which fill let the port first installed with DESTDIR=/var/tmp/ports/${PORTNAME} and then a packing list is generated and then finally whole tree is moved to ${PREFIX}, hmm...? What do you say ? Thanks for you replies. Ashish Shukla P.S. do you've any ideas about when a discussion on this subject took place on this list, hmm..? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081209/16aa3958/attachment.pgp From jonc at chen.org.nz Tue Dec 9 13:57:07 2008 From: jonc at chen.org.nz (Jonathan Chen) Date: Tue Dec 9 13:57:14 2008 Subject: Commit request ports/128241 Message-ID: <20081209213726.GA40500@osiris.chen.org.nz> Hi, Would some kind committer please commit: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128241 It's been on the wait queue for more than a month now. Cheers. -- Jonathan Chen ---------------------------------------------------------------------- Do not take life too seriously. You will never get out of it alive. From amdmi3 at amdmi3.ru Tue Dec 9 14:21:07 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Tue Dec 9 14:21:15 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <87tz9di38u.fsf@chateau.d.lf> References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> Message-ID: <20081209222042.GC29817@hades.panopticon> * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: > > No, those problems will not arise as long as the maintainer tests the > > port before submitting an update. And the tested port of fixed version > > will be usable for a long time, unlike SCM-based one which may break > > every second. > > That is true, but the only problem I see with snapshots is, if > maintainer is busy you can't do anything There's no other way, unfortunately. There's 2 weeks maintainer timeout (usually pot gets committed somewhere between 2 weeks and 1 month). But there was and idea of having multiple maintainers for a port, maybe it could lower response times. > except maintaining your own local port version on your box. And > anyone using these SCM ports is the one who knows things can go > wrong often, and this is only for development use. Having bleeding edge software and support for development versions is not the goal of ports (though I consider ports pretty good in those). Ports are intended for everyone's use and are expected to be more or less stable. > > I'd say it's the least significant reason. The main reasons are the > > first three which can be shortened as `the port will be unuseable and > > sometimes dangerous'. > > What's for automatic plist generation, I've given it some thought, > > and it seems like there could be a more or less reliable way after all. > > I'm currently doing some experiments. > > Cool, would like to see the results of your experiments :). I will post something on this list if I manage to get any useful results. > > It's not like your proposal is bad, ports instantaneously tracking > > upstream changes and not needing maintainers would really be cool, > > but unfortunately that's practically impossible. > > Gentoo GNU/Linux which is a source-based GNU/Linux distribution has this > feature available, what is different in that is, that it uses a separate > root for recording the packing list port and optionally creating a > package. Yes, I've heard of it. Maybe I'll look closely at how it's done. > Maybe we can introduce a hack in ports system like by adding some > variable like 'USES_DYNAMIC_PLIST=yes' in Makefile, which fill let the > port first installed with DESTDIR=/var/tmp/ports/${PORTNAME} and then a > packing list is generated and then finally whole tree is moved to > ${PREFIX}, hmm...? What do you say ? Current DESTDIR implementation uses chroot and obviously requires complete system installed in DESTDIR. Also installing a port will install all dependencies in the chroot as well. There was proposal of another implementation that would behave as you describe without chroot, but it would require too much work, as most ports will need hacks so they install software into ${DESTDIR}/${PREFIX}, but the software would think that it's installed into ${PREFIX}. That is not even always possible, so the idea was dropped. Thus, the only reliable way to generate plist with standart tools is using fat chroot. My idea however is monitor all filesystem writes by port's make and all descendant processes. That may be done with monitoring or replacing syscalls and may be done with LD_PRELOAD or some *trace kernel facilities. The former is what I'm currently experimenting with. > P.S. do you've any ideas about when a discussion on this subject took > place on this list, hmm..? The last one was, afair, this one: http://groups.google.com/group/mailing.freebsd.ports/browse_thread/thread/5f6fca39526c0fc4/8987f328fd95f0c5?lnk=gst&q=fetch+from+vcs#8987f328fd95f0c5 there should be more http://groups.google.com/group/mailing.freebsd.ports/search?group=mailing.freebsd.ports&q=fetch+from+repository -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From pav at FreeBSD.org Tue Dec 9 14:28:34 2008 From: pav at FreeBSD.org (Pav Lucistnik) Date: Tue Dec 9 14:28:41 2008 Subject: Commit request ports/128241 In-Reply-To: <20081209213726.GA40500@osiris.chen.org.nz> References: <20081209213726.GA40500@osiris.chen.org.nz> Message-ID: <1228860082.917.9.camel@hood.oook.cz> Jonathan Chen p??e v st 10. 12. 2008 v 10:37 +1300: > Would some kind committer please commit: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128241 > > It's been on the wait queue for more than a month now. Let me have a look. -- Pav Lucistnik A)bort, R)etry, H)it with big hammer -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081209/4635013e/attachment.pgp From beech at alaskaparadise.com Tue Dec 9 14:36:34 2008 From: beech at alaskaparadise.com (Beech Rintoul) Date: Tue Dec 9 14:36:41 2008 Subject: Commit request ports/128241 In-Reply-To: <20081209213726.GA40500@osiris.chen.org.nz> References: <20081209213726.GA40500@osiris.chen.org.nz> Message-ID: <200812091319.50528.beech@alaskaparadise.com> On Tuesday 09 December 2008 12:37:26 Jonathan Chen wrote: > Hi, > > Would some kind committer please commit: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/128241 > > It's been on the wait queue for more than a month now. > > Cheers. It's already been committed. I'll check why the pr wasn't closed. Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --------------------------------------------------------------------------------------- From realvaemailservices91 at gmail.com Tue Dec 9 20:34:08 2008 From: realvaemailservices91 at gmail.com (Top Mailer) Date: Tue Dec 9 20:34:14 2008 Subject: UNLIMITED Liberty Reserve ( LR ) for Sale!!! Message-ID: <493f42cc.06876e0a.0cbe.7c7d@mx.google.com> UNLIMITED Liberty Reserve ( LR ) for Sale!!! We can provide you UNLIMITED Liberty Reserve for your need at the lowest rate. Just tell us how much LR you need and we will give you the best rate. Email me for more details postmaster@hitechbp.com Or, chat with us via yahoo messenger ID: ( libertyreserveseller ) From hrs at FreeBSD.org Tue Dec 9 23:41:24 2008 From: hrs at FreeBSD.org (Hiroki Sato) Date: Tue Dec 9 23:41:30 2008 Subject: RFC: $USE_[GU]ID for consistent [GU]ID handling In-Reply-To: References: <20081208.033250.137441016.hrs@allbsd.org> Message-ID: <20081210.164055.15552079.hrs@allbsd.org> "Florent Thoumie" wrote in : fl> There's an open PR with patches for this feature (ports/108514). Could fl> you have a look and maybe send your comments? Oh, sorry, I did not notice that. I will read the PR and follow-ups first. Thank you for the pointer. -- | Hiroki SATO -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081210/55004fe8/attachment.pgp From silver.salonen at gmail.com Wed Dec 10 00:57:54 2008 From: silver.salonen at gmail.com (Silver Salonen) Date: Wed Dec 10 00:58:02 2008 Subject: PYTHON_SITELIBDIR gets parsed incorrectly Message-ID: <20930607.post@talk.nabble.com> Hello. I'm creating a port that uses python. I've set in Makefile: USE_PYTHON= yes PYTHON_SITELIBDIR=${PYTHON_SITELIBDIR:S|^${PREFIX}/||g} PLIST_SUB+= PYTHON_SITELIBDIR="${PYTHON_SITELIBDIR}" And pkg-plist has entries a'la: %%BINDINGS%%%%PYTHON_SITELIBDIR%%/ This %%BINDINGS%% gets replaced with "", so that should not be an issue. Anyway, when I install port, +CONTENTS contains lines a'la: /usr/local/lib/python2.5/site-packages/museek/__init__.py And when I try deinstalling it, I get errors a'la: pkg_delete: file '/usr/local//usr/local/lib/python2.5/site-packages/museek/__init__.py' doesn't exist Why do these files get prefixed with $LOCALBASE (or $PREFIX)? -- View this message in context: http://www.nabble.com/PYTHON_SITELIBDIR-gets-parsed-incorrectly-tp20930607p20930607.html Sent from the freebsd-ports mailing list archive at Nabble.com. From shuvaev at physik.uni-wuerzburg.de Wed Dec 10 02:23:46 2008 From: shuvaev at physik.uni-wuerzburg.de (Alexey Shuvaev) Date: Wed Dec 10 02:23:52 2008 Subject: PYTHON_SITELIBDIR gets parsed incorrectly In-Reply-To: <20930607.post@talk.nabble.com> References: <20930607.post@talk.nabble.com> Message-ID: <20081210102342.GA11556@wep4035.physik.uni-wuerzburg.de> Hello! On Wed, Dec 10, 2008 at 12:57:52AM -0800, Silver Salonen wrote: > > Hello. > > I'm creating a port that uses python. I've set in Makefile: > USE_PYTHON= yes > PYTHON_SITELIBDIR=${PYTHON_SITELIBDIR:S|^${PREFIX}/||g} > PLIST_SUB+= PYTHON_SITELIBDIR="${PYTHON_SITELIBDIR}" > > And pkg-plist has entries a'la: > %%BINDINGS%%%%PYTHON_SITELIBDIR%%/ > > This %%BINDINGS%% gets replaced with "", so that should not be an issue. > > Anyway, when I install port, +CONTENTS contains lines a'la: > /usr/local/lib/python2.5/site-packages/museek/__init__.py > This is wrong. They should be relative to ${LOCALBASE}, lib/python2.5/site-packages/bla-bla-bla in this case. Can't say why %) Examine the behavior of PYTHON_SITELIBDIR variable in the Makefile. > And when I try deinstalling it, I get errors a'la: > pkg_delete: file > '/usr/local//usr/local/lib/python2.5/site-packages/museek/__init__.py' > doesn't exist > > Why do these files get prefixed with $LOCALBASE (or $PREFIX)? > 0.02$, Alexey. From aturetta at commit.it Wed Dec 10 03:30:11 2008 From: aturetta at commit.it (Angelo Turetta) Date: Wed Dec 10 03:30:28 2008 Subject: Please include emulators/open-vm-tools in 7.1 release Message-ID: <493FA4F6.3020707@commit.it> The open-vm-tools port has been working fine for months, but at the time of RELEASE_7_1_0 tagging of the ports tree there were some pkg-list and install problems, so it was marked BROKEN. Those problems have been solved since several weeks now, so I think it would be really a pity non to have a binary package for open-vm-tools and open-vm-tools-nox11 in the 7.1 release. Thanks, Angelo Turetta From swhetzel at gmail.com Wed Dec 10 05:57:13 2008 From: swhetzel at gmail.com (Scot Hetzel) Date: Wed Dec 10 05:57:20 2008 Subject: PYTHON_SITELIBDIR gets parsed incorrectly In-Reply-To: <20930607.post@talk.nabble.com> References: <20930607.post@talk.nabble.com> Message-ID: <790a9fff0812100557v105ab514vebef685b02400c18@mail.gmail.com> On 12/10/08, Silver Salonen wrote: > > Hello. > > I'm creating a port that uses python. I've set in Makefile: > USE_PYTHON= yes > PYTHON_SITELIBDIR=${PYTHON_SITELIBDIR:S|^${PREFIX}/||g} > PLIST_SUB+= PYTHON_SITELIBDIR="${PYTHON_SITELIBDIR}" > > And pkg-plist has entries a'la: > %%BINDINGS%%%%PYTHON_SITELIBDIR%%/ > > This %%BINDINGS%% gets replaced with "", so that should not be an issue. > > Anyway, when I install port, +CONTENTS contains lines a'la: > /usr/local/lib/python2.5/site-packages/museek/__init__.py > > And when I try deinstalling it, I get errors a'la: > pkg_delete: file > '/usr/local//usr/local/lib/python2.5/site-packages/museek/__init__.py' > doesn't exist > > Why do these files get prefixed with $LOCALBASE (or $PREFIX)? > The problem is that you are redefining PYTHON_SITELIBDIR in PLIST_SUB. If you remove: > PYTHON_SITELIBDIR=${PYTHON_SITELIBDIR:S|^${PREFIX}/||g} > PLIST_SUB+= PYTHON_SITELIBDIR="${PYTHON_SITELIBDIR}" from your make file, and use 'make -V PLIST_SUB' and 'make -V PYTHON_SITELIBDIR', you should get this: $ make -V PLIST_SUB PYVER=2.5 PYVER_WITHPAT=2.5.2 PYTHON_INCLUDEDIR=include/python2.5 PYTHON_LIBDIR=lib/python2.5 PYTHON_PLATFORM=freebsd8 PYTHON_SITELIBDIR=lib/python2.5/site-packages PYTHON_VERSION=python2.5 IF_DEFAULT="" X86_ONLY="@comment " 32BIT_ONLY="@comment " NO_NIS="" OSREL=8.0 PREFIX=%D LOCALBASE=/usr/local X11BASE=/usr/local PORTDOCS="" PORTEXAMPLES="" PORTDATA="" LIB32DIR=lib XAWVER=8 PERL_VERSION=5.8.8 PERL_VER=5.8.8 PERL_ARCH=mach SITE_PERL=lib/perl5/site_perl/5.8.8 DOCSDIR="share/doc/python25" EXAMPLESDIR="share/examples/python25" DATADIR="share/python25" WWWDIR="www/python25" ETCDIR="etc/python25" $ make -V PYTHON_SITELIBDIR /usr/local/lib/python2.5/site-packages Scot From wahjava.ml at gmail.com Wed Dec 10 05:58:03 2008 From: wahjava.ml at gmail.com (Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IA==?= =?utf-8?B?4KS24KWB4KSV4KWN4KSy?=) Date: Wed Dec 10 05:58:09 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081209222042.GC29817@hades.panopticon> (Dmitry Marakasov's message of "Wed, 10 Dec 2008 01:20:42 +0300") References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> <20081209222042.GC29817@hades.panopticon> Message-ID: <8763lsi10m.fsf@chateau.d.lf> Dmitry Marakasov writes: [...] >> Maybe we can introduce a hack in ports system like by adding some >> variable like 'USES_DYNAMIC_PLIST=yes' in Makefile, which fill let the >> port first installed with DESTDIR=/var/tmp/ports/${PORTNAME} and then a >> packing list is generated and then finally whole tree is moved to >> ${PREFIX}, hmm...? What do you say ? > Current DESTDIR implementation uses chroot and obviously requires > complete system installed in DESTDIR. Also installing a port will > install all dependencies in the chroot as well. The Debian package building system, also expects the package files in a directory named ${packageroot}/debian/${packagename}/ which you can install by doing 'make install DESTDIR=debian/${packagename}' in ${packageroot} directory (the directory where you've extracted the package tarball, similar to the FreeBSD's ${WRKSRC} directory. So, my idea is to specify "make -C ${WRKSRC} install DESTDIR=/var/tmp/${PORTNAME}" in the "install" target of port's Makefile, not to be confused with upstream package's Makefile. And I think you confused it with passing 'DESTDIR' variable to 'make' commandline to start port building procedure: Following is an example illustrating how port is going to be installed in the way I'm thinking: ,---- | % sudo make -C /usr/ports/editors/emacs-cvs install | ...checkout from CVS... | ...configuring... | ./configure --prefix=${LOCALBASE} <...and other configure options ...> | ...configuration messages... | ...compilation begins... | make | ...compiling the files... | ...compilation over... | make install DESTDIR=/var/tmp/emacs | ...files being copied to /var/tmp/emacs directory... | ...package list creation... | ...package list finished... | ...copying files into ${LOCALBASE}... | ...end copying files... | ...package installed successfully... `---- The package list can be created via he automated package-list creation method[1] documented in porters-handbook with a 'mtree' command executed in 'pre-install' to prepare the '/var/tmp/${PORTNAME}' prior to installing package. And to assure safety to this procedure, ports should be built with a separate unprivileged user 'portbuilder' whose job is to build ports and install them in '/var/tmp/${PORTNAME}', and create a temporary package list. And to perform the actual installation, the port process should switch to 'root' user. > There was proposal of another implementation that would behave as > you describe without chroot, but it would require too much work, > as most ports will need hacks so they install software into > ${DESTDIR}/${PREFIX}, but the software would think that it's installed > into ${PREFIX}. That is not even always possible, so the idea was > dropped. > Thus, the only reliable way to generate plist with standart tools > is using fat chroot. > My idea however is monitor all filesystem writes by port's make and all > descendant processes. That may be done with monitoring or replacing > syscalls and may be done with LD_PRELOAD or some *trace kernel > facilities. The former is what I'm currently experimenting with. This is also a cool way if something like this can be hacked ? How about using truss or other syscall tracing facilities, hmm..? Thanks for the links and replies. References: [1] - http://www.freebsd.org/doc/en/books/porters-handbook/plist-autoplist.html -- Ashish Shukla -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081210/0e1bd7d7/attachment.pgp From silver.salonen at gmail.com Wed Dec 10 06:52:44 2008 From: silver.salonen at gmail.com (Silver Salonen) Date: Wed Dec 10 06:52:51 2008 Subject: PYTHON_SITELIBDIR gets parsed incorrectly In-Reply-To: <790a9fff0812100557v105ab514vebef685b02400c18@mail.gmail.com> References: <20930607.post@talk.nabble.com> <790a9fff0812100557v105ab514vebef685b02400c18@mail.gmail.com> Message-ID: <20936842.post@talk.nabble.com> Scot Hetzel wrote: > > On 12/10/08, Silver Salonen wrote: >> >> Hello. >> >> I'm creating a port that uses python. I've set in Makefile: >> USE_PYTHON= yes >> PYTHON_SITELIBDIR=${PYTHON_SITELIBDIR:S|^${PREFIX}/||g} >> PLIST_SUB+= PYTHON_SITELIBDIR="${PYTHON_SITELIBDIR}" >> >> And pkg-plist has entries a'la: >> %%BINDINGS%%%%PYTHON_SITELIBDIR%%/ >> >> This %%BINDINGS%% gets replaced with "", so that should not be an issue. >> >> Anyway, when I install port, +CONTENTS contains lines a'la: >> /usr/local/lib/python2.5/site-packages/museek/__init__.py >> >> And when I try deinstalling it, I get errors a'la: >> pkg_delete: file >> '/usr/local//usr/local/lib/python2.5/site-packages/museek/__init__.py' >> doesn't exist >> >> Why do these files get prefixed with $LOCALBASE (or $PREFIX)? >> > > The problem is that you are redefining PYTHON_SITELIBDIR in PLIST_SUB. > If you remove: > >> PYTHON_SITELIBDIR=${PYTHON_SITELIBDIR:S|^${PREFIX}/||g} >> PLIST_SUB+= PYTHON_SITELIBDIR="${PYTHON_SITELIBDIR}" > > from your make file, and use 'make -V PLIST_SUB' and 'make -V > PYTHON_SITELIBDIR', you should get this: > > $ make -V PLIST_SUB > PYVER=2.5 PYVER_WITHPAT=2.5.2 PYTHON_INCLUDEDIR=include/python2.5 > PYTHON_LIBDIR=lib/python2.5 PYTHON_PLATFORM=freebsd8 > PYTHON_SITELIBDIR=lib/python2.5/site-packages > PYTHON_VERSION=python2.5 IF_DEFAULT="" X86_ONLY="@comment " > 32BIT_ONLY="@comment " NO_NIS="" OSREL=8.0 PREFIX=%D > LOCALBASE=/usr/local X11BASE=/usr/local PORTDOCS="" PORTEXAMPLES="" > PORTDATA="" LIB32DIR=lib XAWVER=8 PERL_VERSION=5.8.8 PERL_VER=5.8.8 > PERL_ARCH=mach SITE_PERL=lib/perl5/site_perl/5.8.8 > DOCSDIR="share/doc/python25" EXAMPLESDIR="share/examples/python25" > DATADIR="share/python25" WWWDIR="www/python25" ETCDIR="etc/python25" > > $ make -V PYTHON_SITELIBDIR > /usr/local/lib/python2.5/site-packages > > Scot > Aha, thanks. I didn't realize that %%PYTHON_SITELIBDIR%% gets replaced automatically (via USE_PYTHON=yes, right?). It's OK now :) -- View this message in context: http://www.nabble.com/PYTHON_SITELIBDIR-gets-parsed-incorrectly-tp20930607p20936842.html Sent from the freebsd-ports mailing list archive at Nabble.com. From amdmi3 at amdmi3.ru Wed Dec 10 10:11:50 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Wed Dec 10 10:11:57 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <8763lsi10m.fsf@chateau.d.lf> References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> Message-ID: <20081210181125.GA86341@hades.panopticon> * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: > > Current DESTDIR implementation uses chroot and obviously requires > > complete system installed in DESTDIR. Also installing a port will > > install all dependencies in the chroot as well. > > The Debian package building system, also expects the package files in a > directory named ${packageroot}/debian/${packagename}/ which you can > install by doing 'make install DESTDIR=debian/${packagename}' in > ${packageroot} directory (the directory where you've extracted the > package tarball, similar to the FreeBSD's ${WRKSRC} directory. > > So, my idea is to specify "make -C ${WRKSRC} install DESTDIR=/var/tmp/${PORTNAME}" > in the "install" target of port's Makefile, not to be confused with > upstream package's Makefile. And I think you confused it with passing > 'DESTDIR' variable to 'make' commandline to start port building > procedure: How do you expect all ports to respect DESTDIR in their Makefiles, while many ports don't even use make? As I've said, that will require tremendous amount of hacking and is not even possible sometimes. > > My idea however is monitor all filesystem writes by port's make and all > > descendant processes. That may be done with monitoring or replacing > > syscalls and may be done with LD_PRELOAD or some *trace kernel > > facilities. The former is what I'm currently experimenting with. > > This is also a cool way if something like this can be hacked ? How about > using truss or other syscall tracing facilities, hmm..? Truss uses ptrace(2). There are other facilities, but they are less useable - ktrace (produces too much output, needs to be enabled in kernel) and dtrace (only available in current for now, also should be enabled in kernel). -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From wahjava.ml at gmail.com Wed Dec 10 14:00:18 2008 From: wahjava.ml at gmail.com (Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IA==?= =?utf-8?B?4KS24KWB4KSV4KWN4KSy?=) Date: Wed Dec 10 14:00:25 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081210181125.GA86341@hades.panopticon> (Dmitry Marakasov's message of "Wed, 10 Dec 2008 21:11:25 +0300") References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> Message-ID: <87zlj3heor.fsf@chateau.d.lf> Dmitry Marakasov writes: > * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: >> > Current DESTDIR implementation uses chroot and obviously requires >> > complete system installed in DESTDIR. Also installing a port will >> > install all dependencies in the chroot as well. >> >> The Debian package building system, also expects the package files in a >> directory named ${packageroot}/debian/${packagename}/ which you can >> install by doing 'make install DESTDIR=debian/${packagename}' in >> ${packageroot} directory (the directory where you've extracted the >> package tarball, similar to the FreeBSD's ${WRKSRC} directory. >> >> So, my idea is to specify "make -C ${WRKSRC} install DESTDIR=/var/tmp/${PORTNAME}" >> in the "install" target of port's Makefile, not to be confused with >> upstream package's Makefile. And I think you confused it with passing >> 'DESTDIR' variable to 'make' commandline to start port building >> procedure: > How do you expect all ports to respect DESTDIR in their Makefiles, > while many ports don't even use make? As I've said, that will require > tremendous amount of hacking and is not even possible sometimes. How about adding a variable like REQUIRES_DYNAMIC_INSTALLATION=yes, which will then generate a plist on the basis of "/var/tmp/${PORTNAME}", so now it is the port's responsibility to install all contents to "/var/tmp/${PORTNAME}" either by "make install DESTDIR=..." or by some other way. Having that REQUIRES_DYNAMIC_INSTALLATION also includes a 'post-install' target which will copy all files from /var/tmp/${PORTNAME} to ${PREFIX}. -- Ashish Shukla -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081210/e7f8719c/attachment.pgp From amdmi3 at amdmi3.ru Wed Dec 10 14:35:46 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Wed Dec 10 14:35:57 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <87zlj3heor.fsf@chateau.d.lf> References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> Message-ID: <20081210223522.GA6367@hades.panopticon> * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: > > How do you expect all ports to respect DESTDIR in their Makefiles, > > while many ports don't even use make? As I've said, that will require > > tremendous amount of hacking and is not even possible sometimes. > > How about adding a variable like REQUIRES_DYNAMIC_INSTALLATION=yes, > which will then generate a plist on the basis of "/var/tmp/${PORTNAME}", > so now it is the port's responsibility to install all contents to > "/var/tmp/${PORTNAME}" either by "make install DESTDIR=..." or by some > other way. Having that REQUIRES_DYNAMIC_INSTALLATION also includes a > 'post-install' target which will copy all files from > /var/tmp/${PORTNAME} to ${PREFIX}. You do not understand the basic thing. The PROBLEM is to make all ports install into one dir, but be runnable from another. As simple as that. Imagine a software like that: --- foo.c #include int main() { return system("cat "DATAFILE); } --- datafile.dat Hello, world! --- Makefile PREFIX?= /usr/local DATADIR?= ${PREFIX}/share/foo all: foo foo: foo.c cc -DDATAFILE=\"${DATADIR}/datafile.dat\" foo.c -o foo install: foo datafile.dat install -s foo ${PREFIX}/bin install -d ${DATADIR} install datafile.dat ${DATADIR} --- As you can see, if this is installed with PREFIX=/var/tmp/foobar, then moved to /usr and ran, it won't work, as it has DATAFILE compiled in as "/var/tmp/foobar/share/foo/datafile.dat" instead of "/usr/local/share/foo/datafile.dat". To make it behave as we indend, you'll have to either hack Makefile to distinguish DESTDIR and PREFIX, or do all installation in port's Makefile by yourself. We have around 20k ports, and it will be extremely hard task to convert them all to such scheme (though afaik configure-based ones should support this without modifications). The example above is quite simple, the real life can be much more ugly, I assure. The worst thing is that we won't be able to test ports automatically, as the fact the port builds and installs successfully won't mean that it will run without problems. I wonder how debian and gentoo get around this problem... -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From wahjava.ml at gmail.com Wed Dec 10 15:16:06 2008 From: wahjava.ml at gmail.com (Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IA==?= =?utf-8?B?4KS24KWB4KSV4KWN4KSy?=) Date: Wed Dec 10 15:16:13 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081210223522.GA6367@hades.panopticon> (Dmitry Marakasov's message of "Thu, 11 Dec 2008 01:35:22 +0300") References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> Message-ID: <87vdtrhb6r.fsf@chateau.d.lf> Dmitry Marakasov writes: [snip] > --- Makefile > PREFIX?= /usr/local > DATADIR?= ${PREFIX}/share/foo > all: foo > foo: foo.c > cc -DDATAFILE=\"${DATADIR}/datafile.dat\" foo.c -o foo > install: foo datafile.dat > install -s foo ${PREFIX}/bin > install -d ${DATADIR} > install datafile.dat ${DATADIR} # Above statements should be changed to: install -s foo ${DESTDIR}${PREFIX}/bin install -d ${DESTDIR}${DATADIR} install datafile.dat ${DESTDIR}${DATADIR} > --- In above case the package list can be created with: $ find ${DESTDIR} -type f |sed -e "s[${DESTDIR}${PREFIX}/[[g" > As you can see, if this is installed with PREFIX=/var/tmp/foobar, > then moved to /usr and ran, it won't work, as it has DATAFILE > compiled in as "/var/tmp/foobar/share/foo/datafile.dat" instead of > "/usr/local/share/foo/datafile.dat". > To make it behave as we indend, you'll have to either hack Makefile > to distinguish DESTDIR and PREFIX, or do all installation in port's > Makefile by yourself. > We have around 20k ports, and it will be extremely hard task to > convert them all to such scheme (though afaik configure-based ones > should support this without modifications). The example above is > quite simple, the real life can be much more ugly, I assure. The > worst thing is that we won't be able to test ports automatically, > as the fact the port builds and installs successfully won't mean > that it will run without problems. > I wonder how debian and gentoo get around this problem... I understood what you're trying to say, but you're missing my point, so I'm explaining it in the following example: ,---- Quoting from my earlier example | % sudo make -C /usr/ports/editors/emacs-cvs install | ...checkout from CVS... | ...configuring... | ./configure --prefix=${LOCALBASE} <...and other configure options ...> That will compile Emacs with PREFIX=${LOCALBASE} (which is /usr/local by default) | ...configuration messages... | ...compilation begins... | make | ...compiling the files... | ...compilation over... | make install DESTDIR=/var/tmp/emacs This will install all files into DESTDIR=/var/tmp/emacs, with directory structure similar to following: /var/tmp/emacs /usr/local/bin/emacs /usr/local/share/emacs/23.0.60/... etc. | ...files being copied to /var/tmp/emacs directory... | ...package list creation... | ...package list finished... | ...copying files into ${LOCALBASE}... And finally this will copy all files present in /var/tmp/emacs to ${LOCALBASE} for final installation with package we recorded earlier. | ...end copying files... | ...package installed successfully... `---- This is what Debian and Gentoo does. Remember we don't have to pass DESTDIR variable to 'make -C /usr/ports/editors/emacs-cvs' instead it will be passed to the 'gmake' process invoked by port's Makefile. If we pass DESTDIR to port's commandline, then it will install all dependencies in that chroot which is not desired, we simply care about the files installed by that port. Since there're already 20,000 ports we can't do it by default, so we've to hack some knob (like REQUIRES_DYNAMIC_INSTALLATION) which if defined will enable this behaviour. Following are some links: Debian's New Maintainer's Guide http://www.debian.org/doc/maint-guide/ch-modify.en.html#s-destdir Gentoo's Ebuild Quickstart Guide http://devmanual.gentoo.org/quickstart/index.html I hope I'm clear now. Thanks -- Ashish Shukla -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081210/0d4989c0/attachment.pgp From akitada at gmail.com Thu Dec 11 00:16:50 2008 From: akitada at gmail.com (Akira Kitada) Date: Thu Dec 11 00:16:56 2008 Subject: FreeBSD Port: omake-0.9.8.1_1 Message-ID: Hi, Could you please update omake to the latest veraion? Thanks, From amdmi3 at amdmi3.ru Thu Dec 11 00:23:50 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Thu Dec 11 00:23:57 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <87vdtrhb6r.fsf@chateau.d.lf> References: <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> Message-ID: <20081211082325.GA6167@hades.panopticon> * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: > This is what Debian and Gentoo does. Remember we don't have to pass > DESTDIR variable to 'make -C /usr/ports/editors/emacs-cvs' instead it > will be passed to the 'gmake' process invoked by port's Makefile. If we I understand. But you're implying that there is Makefile and it supports DESTDIR. As I understand, you're referring to autotools-based ports. Remember, those are less than 1/4 of the collection. > pass DESTDIR to port's commandline, then it will install all > dependencies in that chroot which is not desired, we simply care about > the files installed by that port. Since there're already 20,000 ports we > can't do it by default, so we've to hack some knob (like > REQUIRES_DYNAMIC_INSTALLATION) which if defined will enable this > behaviour. So if I understand correctly, you're proposing to only use dynamic plist generation for the ports that support it without modification, i.e. autotools-based? My opinion is that we should support the feature for all ports, or don't support it at all. Only getting rid of ~5k pkg-plists is not a huge accomplishment considering the mess it causes and I doubt it's worth the work on adding the feature to port.mk and then rebuilding and testing all affected ports. Being able to forget about pkg-plists once and forever however would be a huge accomplishment and if that's possible it should be done sooner or later. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From yanefbsd at gmail.com Thu Dec 11 01:01:47 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Dec 11 01:01:57 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081211082325.GA6167@hades.panopticon> References: <20081209143052.GA29817@hades.panopticon> <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> Message-ID: <7d6fde3d0812110101t1dab2abl9b97945ea1689baa@mail.gmail.com> On Thu, Dec 11, 2008 at 12:23 AM, Dmitry Marakasov wrote: > * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: > >> This is what Debian and Gentoo does. Remember we don't have to pass >> DESTDIR variable to 'make -C /usr/ports/editors/emacs-cvs' instead it >> will be passed to the 'gmake' process invoked by port's Makefile. If we > > I understand. But you're implying that there is Makefile and it supports > DESTDIR. As I understand, you're referring to autotools-based ports. > Remember, those are less than 1/4 of the collection. > >> pass DESTDIR to port's commandline, then it will install all >> dependencies in that chroot which is not desired, we simply care about >> the files installed by that port. Since there're already 20,000 ports we >> can't do it by default, so we've to hack some knob (like >> REQUIRES_DYNAMIC_INSTALLATION) which if defined will enable this >> behaviour. > > So if I understand correctly, you're proposing to only use dynamic > plist generation for the ports that support it without modification, > i.e. autotools-based? > > My opinion is that we should support the feature for all ports, or don't > support it at all. Only getting rid of ~5k pkg-plists is not a huge > accomplishment considering the mess it causes and I doubt it's worth > the work on adding the feature to port.mk and then rebuilding and > testing all affected ports. Being able to forget about pkg-plists > once and forever however would be a huge accomplishment and if that's > possible it should be done sooner or later. > > -- > Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D > amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru Agreed. I've come across many ports where folks haven't written Makefiles properly and it results in problems . Most cases you can make the following assumption: if a port can be cross-compiled, it can most likely be installed under another destination directory. The converse is not necessarily true. These are issues which should be documented in a Makefile FAQ for everyone, and this should be noted whenever an issue is found so that folks can be educated and things like this can be fixed. -Garrett From erwin at FreeBSD.org Thu Dec 11 02:12:21 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Thu Dec 11 02:12:28 2008 Subject: INDEX build failed for 6.x Message-ID: <200812111012.mBBAC8h0072162@pointyhat.freebsd.org> INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: phpwebgallery-1.7.2: no entry for /usr/ports/security/pecl-filter make_index: php5-extensions-1.2: no entry for /usr/ports/security/pecl-filter make_index: php5-extensions-1.2: no entry for /usr/ports/security/pecl-filter Committers on the hook: ale flz leeym Most recent CVS update was: U archivers/Makefile U archivers/pecl-zip/Makefile U archivers/php5-zip/Makefile U devel/Makefile U devel/pecl-json/Makefile U devel/php5-json/Makefile U lang/php5/Makefile U lang/php5/Makefile.ext U lang/php5/distinfo U net-p2p/rtorrent/Makefile U security/Makefile U security/pecl-hash/Makefile U security/php5-filter/Makefile U security/php5-hash/Makefile U textproc/p5-RDF-Simple/Makefile U textproc/p5-RDF-Simple/distinfo U textproc/p5-RDF-Simple/pkg-plist From andrew.w.nosenko at gmail.com Thu Dec 11 02:20:36 2008 From: andrew.w.nosenko at gmail.com (Andrew W. Nosenko) Date: Thu Dec 11 02:20:42 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081211082325.GA6167@hades.panopticon> References: <20081209143052.GA29817@hades.panopticon> <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> Message-ID: <6161f3180812110156n43803ee9s88443b6777bd0743@mail.gmail.com> On Thu, Dec 11, 2008 at 10:23 AM, Dmitry Marakasov wrote: > * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: > >> This is what Debian and Gentoo does. Remember we don't have to pass >> DESTDIR variable to 'make -C /usr/ports/editors/emacs-cvs' instead it >> will be passed to the 'gmake' process invoked by port's Makefile. If we > > I understand. But you're implying that there is Makefile and it supports > DESTDIR. As I understand, you're referring to autotools-based ports. > Remember, those are less than 1/4 of the collection. Excuse me, but he refers not to autotools-based ports, but to ports that follows GNU Coding Standards (section "Makefile Conventions" if more preciously). Autotools just brings such support out-of-the-box. And, IMO, projects that violates these things heavy, should be fixed upstream. BTW, from my expiriense, there are little amount of project that doesn't support DESTDIR of it's analog. And many of them may be worked around anyway. -- Andrew W. Nosenko From regisr at pobox.com Thu Dec 11 02:48:11 2008 From: regisr at pobox.com (regisr) Date: Thu Dec 11 02:48:20 2008 Subject: build problem Message-ID: <20081211114807.b23377b2.regisr@pobox.com> When building ImageMagick-6.4.7-5 on FreeBSD 6.4 I have a build error: /usr/obj/home/ports/graphics/ImageMagick/work/ImageMagick-6.4.7-5/tests/.libs/co nstitute -storagetype double /usr/obj/home/ports/graphics/ImageMagick/work/Image Magick-6.4.7-5/tests/input_truecolor.miff cmy Constitute check failed: 6615/0.0587497/0.843137 FAIL: tests/constitute_double_cmy.sh -- regis From amdmi3 at amdmi3.ru Thu Dec 11 03:36:22 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Thu Dec 11 03:36:30 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <6161f3180812110156n43803ee9s88443b6777bd0743@mail.gmail.com> References: <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> <6161f3180812110156n43803ee9s88443b6777bd0743@mail.gmail.com> Message-ID: <20081211113556.GA7422@hades.panopticon> * Andrew W. Nosenko (andrew.w.nosenko@gmail.com) wrote: > > I understand. But you're implying that there is Makefile and it supports > > DESTDIR. As I understand, you're referring to autotools-based ports. > > Remember, those are less than 1/4 of the collection. > Excuse me, but he refers not to autotools-based ports, but to ports > that follows GNU Coding Standards (section "Makefile Conventions" if > more preciously). > Autotools just brings such support out-of-the-box. > And, IMO, projects that violates these things heavy, should be fixed upstream. > BTW, from my expiriense, there are little amount of project that > doesn't support DESTDIR of it's analog. And many of them may be > worked around anyway. I didn't count or check thoroughfully, but the feeling I've got from my 150+ ports is that no one actually supports it. I may be wrong though. And again, GNU Coding Standards don't cover build systems other than make. Also, it's not even a requirement: "So, we strongly recommend GNU packages support DESTDIR, though it is not an absolute requirement." I agree with that you can't require all upstream maintainers to support this feature. Architecturally this should be completely package manager's problem (i.e. upstream should only provide installation into PREFIX, and may optionally support DESTDIR, and if package manager needs features like that staged install or automatic plist generation, and upstream don't provide it, package manager should take care of it by itself. Tecnically, we may support DESTDIR in all ports. But considering the amount of work required, and increased complexety of everything as a result, I'd stick with static plists without hesitation. See http://lists.freebsd.org/pipermail/freebsd-ports/2006-August/034745.html those are some real examples of complexity and resulting confusion, from first variant of DESTDIR support in ports. Now, when we have one DESTDIR implementation, adding another will likely make some heads explode, just think of variable naming. I'll remind that what we are talking about is automatic plist generation, and I think that this can be done without any hacks like installing a port into intermediate directory before real installation just by logging all writes to the filesystem. This will require no modifications to the ports, very minor modifications to Mk, and will (in theory) work without fail whatever the port will install, also ensuring there're no runaway files (that is, files not listed in plist, or files not installed into DESTDIR for some reason). -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From erwin at FreeBSD.org Thu Dec 11 05:25:29 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Thu Dec 11 05:25:36 2008 Subject: INDEX now builds successfully on 6.x Message-ID: <200812111325.mBBDPGSF052386@pointyhat.freebsd.org> From david at catwhisker.org Thu Dec 11 05:27:41 2008 From: david at catwhisker.org (David Wolfskill) Date: Thu Dec 11 05:27:48 2008 Subject: [ImageMagick] build problem In-Reply-To: <20081211114807.b23377b2.regisr@pobox.com> References: <20081211114807.b23377b2.regisr@pobox.com> Message-ID: <20081211132740.GN60731@albert.catwhisker.org> On Thu, Dec 11, 2008 at 11:48:07AM +0100, regisr wrote: > When building ImageMagick-6.4.7-5 on FreeBSD 6.4 I have a build error: > > /usr/obj/home/ports/graphics/ImageMagick/work/ImageMagick-6.4.7-5/tests/.libs/co > nstitute -storagetype > double /usr/obj/home/ports/graphics/ImageMagick/work/Image > Magick-6.4.7-5/tests/input_truecolor.miff cmy Constitute check failed: > 6615/0.0587497/0.843137 FAIL: tests/constitute_double_cmy.sh For what it's worth, I did not encounter this. Running on: FreeBSD g1-35.catwhisker.org 6.4-STABLE FreeBSD 6.4-STABLE #659: Thu Dec 11 05:01:52 PST 2008 root@g1-35.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY i386 I ran "portmaster -ad" and: ===>>> Upgrade of ImageMagick-6.4.5.5 to ImageMagick-6.4.7.5 succeeded Peace, david -- David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081211/f5512ab0/attachment.pgp From wahjava.ml at gmail.com Thu Dec 11 06:08:44 2008 From: wahjava.ml at gmail.com (Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IA==?= =?utf-8?B?4KS24KWB4KSV4KWN4KSy?=) Date: Thu Dec 11 06:08:51 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081211113556.GA7422@hades.panopticon> (Dmitry Marakasov's message of "Thu, 11 Dec 2008 14:35:56 +0300") References: <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> <6161f3180812110156n43803ee9s88443b6777bd0743@mail.gmail.com> <20081211113556.GA7422@hades.panopticon> Message-ID: <87vdtqls4g.fsf@chateau.d.lf> Dmitry Marakasov writes: > * Andrew W. Nosenko (andrew.w.nosenko@gmail.com) wrote: >> > I understand. But you're implying that there is Makefile and it supports >> > DESTDIR. As I understand, you're referring to autotools-based ports. >> > Remember, those are less than 1/4 of the collection. >> Excuse me, but he refers not to autotools-based ports, but to ports >> that follows GNU Coding Standards (section "Makefile Conventions" if >> more preciously). >> Autotools just brings such support out-of-the-box. >> And, IMO, projects that violates these things heavy, should be fixed upstream. >> BTW, from my expiriense, there are little amount of project that >> doesn't support DESTDIR of it's analog. And many of them may be >> worked around anyway. Yes, I meant that only. > I didn't count or check thoroughfully, but the feeling I've got > from my 150+ ports is that no one actually supports it. I may be > wrong though. > And again, GNU Coding Standards don't cover build systems other > than make. Also, it's not even a requirement: "So, we strongly > recommend GNU packages support DESTDIR, though it is not an absolute > requirement." > I agree with that you can't require all upstream maintainers to > support this feature. Architecturally this should be completely > package manager's problem (i.e. upstream should only provide > installation into PREFIX, and may optionally support DESTDIR, and > if package manager needs features like that staged install or > automatic plist generation, and upstream don't provide it, package > manager should take care of it by itself. > Tecnically, we may support DESTDIR in all ports. But considering > the amount of work required, and increased complexety of everything > as a result, I'd stick with static plists without hesitation. Yes, that is why I mentioned having a variable which enables this behaviour, by default it is disabled. I mean ports which are okay with providing static plists are fine, but ports which aren't predictable with what files are going to installed can go with this dynamic plist support, where ports infrastructure will only help in generating a plist from an already setup directory tree (/var/tmp/${portname}), now it is maintainer's responsibility to make sure that all files will be installed in /var/tmp/${portname} which {s,}he can do by either using 'make install DESTDIR=/var/tmp/${portname}' or something similar if supported by port's upstream or {s,}he has to add installation commands in ports Makefile rather than going with upstream's way of installing things. > See > http://lists.freebsd.org/pipermail/freebsd-ports/2006-August/034745.html > those are some real examples of complexity and resulting confusion, > from first variant of DESTDIR support in ports. Now, when we have > one DESTDIR implementation, adding another will likely make some heads > explode, just think of variable naming. The DESTDIR issue in above link refers to the DESTDIR support[1] present in FreeBSD Ports system, and the one which I'm talking about has nothing to do with that. > I'll remind that what we are talking about is automatic plist generation, > and I think that this can be done without any hacks like installing a > port into intermediate directory before real installation just by > logging all writes to the filesystem. Yes that intermediate directory is what DESTDIR is. And if you're capable of logging all writes in the DESTDIR, then its cool, but remember you're also talking about installing port in an intermediate directory. After the port gets installed in intermediate directory, the plist can be generated with your filesystem writes logger component or a well tested version of following simply command line: % find /var/tmp/${PORTNAME} -type f |sed -e \ "s[/var/tmp/${PORTNAME}${PREFIX}/[[g" > plist.tmp HTH -- Ashish Shukla -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081211/6da8c7eb/attachment.pgp From anatoli.marinov at gmail.com Thu Dec 11 06:29:29 2008 From: anatoli.marinov at gmail.com (Anatoli Marinov) Date: Thu Dec 11 06:29:36 2008 Subject: latest asterisk and zaptel and app meeatme In-Reply-To: References: Message-ID: Guys, I have the latest ports from yesterday - asterisk 1.4.22 and zaptel 1.4.11, FreeBSD 7.1 PRE My server uses app_meatme for our conferences. The there is an issue with latest software. When I tried to enter in the conference i got: -- Executing [13003@incomingInternal:1] Ringing("SIP/3004-28713000", "") in new stack -- Executing [13003@incomingInternal:2] Wait("SIP/3004-28713000", "3") in new stack -- Executing [13003@incomingInternal:3] MeetMe("SIP/3004-28713000", "13003|Mpcid") in new stack -- Created MeetMe conference 1023 for conference '13003' -- Recording -- Playing 'vm-rec-name' (language 'en') -- Playing 'beep' (language 'en') -- x=0, open writing: /var/spool/asterisk/meetme/meetme-username-13003-1 format: sln, 0x28b3e200 -- User ended message by pressing # -- Playing 'auth-thankyou' (language 'en') -- Playing 'vm-review' (language 'en') -- Playing 'vm-msgsaved' (language 'en') -- Playing 'conf-onlyperson' (language 'en') [Dec 11 15:52:28] WARNING[57181]: app_meetme.c:1621 conf_run: Unable to set flags: Inappropriate ioctl for device And the application fails.... At this line there is a new fdset for ASYNC socket I commented these lines there and now I have the application running but I am not sure this is correct. is there another solution? Thanks in advance Anatoli Marinov From mezz7 at cox.net Thu Dec 11 07:07:30 2008 From: mezz7 at cox.net (Jeremy Messenger) Date: Thu Dec 11 07:07:36 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081211082325.GA6167@hades.panopticon> References: <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> Message-ID: On Thu, 11 Dec 2008 02:23:25 -0600, Dmitry Marakasov wrote: > * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: > >> This is what Debian and Gentoo does. Remember we don't have to pass >> DESTDIR variable to 'make -C /usr/ports/editors/emacs-cvs' instead it >> will be passed to the 'gmake' process invoked by port's Makefile. If we > > I understand. But you're implying that there is Makefile and it supports > DESTDIR. As I understand, you're referring to autotools-based ports. > Remember, those are less than 1/4 of the collection. > >> pass DESTDIR to port's commandline, then it will install all >> dependencies in that chroot which is not desired, we simply care about >> the files installed by that port. Since there're already 20,000 ports we >> can't do it by default, so we've to hack some knob (like >> REQUIRES_DYNAMIC_INSTALLATION) which if defined will enable this >> behaviour. > > So if I understand correctly, you're proposing to only use dynamic > plist generation for the ports that support it without modification, > i.e. autotools-based? > > My opinion is that we should support the feature for all ports, or don't > support it at all. Only getting rid of ~5k pkg-plists is not a huge > accomplishment considering the mess it causes and I doubt it's worth > the work on adding the feature to port.mk and then rebuilding and > testing all affected ports. Being able to forget about pkg-plists > once and forever however would be a huge accomplishment and if that's > possible it should be done sooner or later. I object on get rid of pkg-plist. I depend on pkg-plist too much. I think it's important for us to keep on track where the files/directories are. Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From rodrigo.furb at gmail.com Thu Dec 11 08:53:29 2008 From: rodrigo.furb at gmail.com (=?ISO-8859-1?Q?Rodrigo_M=FCller?=) Date: Thu Dec 11 08:53:35 2008 Subject: FreeBSD Port: zaptel-1.4.11 Message-ID: <9cf03db80812110816hf0b7dadg6a6ebe53636ac4b@mail.gmail.com> Hello, I recently installed the new version of zaptel-bsd (1.4.11), and noticed that the module wcfxo no longer exists. Is there a way to set up a card X100P Clone with this version of zaptel? I'm using FreeBSD 7.0 Thank you very much, Rodrigo M?ller From beckman at angryox.com Thu Dec 11 10:34:49 2008 From: beckman at angryox.com (Peter Beckman) Date: Thu Dec 11 10:35:01 2008 Subject: net/asterisk: b2bua.org down, patch fails Message-ID: Tried to upgrade asterisk today: ===> Found saved configuration for asterisk-1.4.22 => asterisk-1.4.22-codec-negotiation-20081110.diff.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from http://b2bua.org/chrome/site/. fetch: http://b2bua.org/chrome/site/asterisk-1.4.22-codec-negotiation-20081110.diff.gz: Internal Server Error => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/asterisk-1.4.22-codec-negotiation-20081110.diff.gz: File unavailable (e.g., file not found, no access) => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles/ and try again. Then with codec-negotiation patch turned off: ===> Found saved configuration for asterisk-1.4.22 ===> Extracting for asterisk-1.4.22 => MD5 Checksum OK for asterisk-1.4.22.tar.gz. => SHA256 Checksum OK for asterisk-1.4.22.tar.gz. /bin/mkdir -p /usr/ports/net/asterisk/work/asterisk-1.4.22/codecs/ilbc /usr/bin/find /usr/ports/net/asterisk/work/asterisk-1.4.22 -name '*.d' -delete ===> Patching for asterisk-1.4.22 ===> Applying extra patch /usr/ports/net/asterisk/files/nocodecnego-patch-Makefile ===> Applying extra patch /usr/ports/net/asterisk/files/dtmf_debug.diff ===> Applying extra patch /usr/ports/net/asterisk/files/feature_disconnect.diff ===> Applying extra patch /usr/ports/net/asterisk/files/sip_force_callid.diff ===> Applying extra patch /usr/ports/net/asterisk/files/sip_set_auth.diff ===> Applying extra patch /usr/ports/net/asterisk/files/rtp_force_dtmf-nocodecnego.diff 1 out of 1 hunks failed--saving rejects to configs/sip.conf.sample.rej Looks like the sip.conf.sample changed in the slightest of ways: -; See doc/README.tos for a description of these parameters. +; See doc/ip-tos.txt for a description of these parameters. Even then, it doesn't compile... cc -o chan_dahdi.o -c chan_dahdi.c -D_THREAD_SAFE -pthread -I/usr/ports/net/asterisk/work/asterisk-1.4.22/include -O2 -fno-strict-aliasing -pipe -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g3 -include /usr/ports/net/asterisk/work/asterisk-1.4.22/include/asterisk/autoconfig.h -I/usr/local/include -fPIC -DAST_MODULE=\"chan_dahdi\" -MD -MT chan_dahdi.o -MF .chan_dahdi.o.d -MP chan_dahdi.c: In function `get_alarms': chan_dahdi.c:3693: error: structure has no member named `chan_alarms' gmake[1]: *** [chan_dahdi.o] Error 1 gmake[1]: Leaving directory `/usr/ports/net/asterisk/work/asterisk-1.4.22/channels' gmake: *** [channels] Error 2 --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ --------------------------------------------------------------------------- From beckman at angryox.com Thu Dec 11 10:44:50 2008 From: beckman at angryox.com (Peter Beckman) Date: Thu Dec 11 10:44:56 2008 Subject: net/asterisk: b2bua.org down, patch fails Message-ID: Tried to upgrade asterisk today: ===> Found saved configuration for asterisk-1.4.22 => asterisk-1.4.22-codec-negotiation-20081110.diff.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from http://b2bua.org/chrome/site/. fetch: http://b2bua.org/chrome/site/asterisk-1.4.22-codec-negotiation-20081110.diff.gz: Internal Server Error => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/asterisk-1.4.22-codec-negotiation-20081110.diff.gz: File unavailable (e.g., file not found, no access) => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles/ and try again. Then with codec-negotiation patch turned off: ===> Found saved configuration for asterisk-1.4.22 ===> Extracting for asterisk-1.4.22 => MD5 Checksum OK for asterisk-1.4.22.tar.gz. => SHA256 Checksum OK for asterisk-1.4.22.tar.gz. /bin/mkdir -p /usr/ports/net/asterisk/work/asterisk-1.4.22/codecs/ilbc /usr/bin/find /usr/ports/net/asterisk/work/asterisk-1.4.22 -name '*.d' -delete ===> Patching for asterisk-1.4.22 ===> Applying extra patch /usr/ports/net/asterisk/files/nocodecnego-patch-Makefile ===> Applying extra patch /usr/ports/net/asterisk/files/dtmf_debug.diff ===> Applying extra patch /usr/ports/net/asterisk/files/feature_disconnect.diff ===> Applying extra patch /usr/ports/net/asterisk/files/sip_force_callid.diff ===> Applying extra patch /usr/ports/net/asterisk/files/sip_set_auth.diff ===> Applying extra patch /usr/ports/net/asterisk/files/rtp_force_dtmf-nocodecnego.diff 1 out of 1 hunks failed--saving rejects to configs/sip.conf.sample.rej Looks like the sip.conf.sample changed in the slightest of ways: -; See doc/README.tos for a description of these parameters. +; See doc/ip-tos.txt for a description of these parameters. Even then, it doesn't compile... cc -o chan_dahdi.o -c chan_dahdi.c -D_THREAD_SAFE -pthread -I/usr/ports/net/asterisk/work/asterisk-1.4.22/include -O2 -fno-strict-aliasing -pipe -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g3 -include /usr/ports/net/asterisk/work/asterisk-1.4.22/include/asterisk/autoconfig.h -I/usr/local/include -fPIC -DAST_MODULE=\"chan_dahdi\" -MD -MT chan_dahdi.o -MF .chan_dahdi.o.d -MP chan_dahdi.c: In function `get_alarms': chan_dahdi.c:3693: error: structure has no member named `chan_alarms' gmake[1]: *** [chan_dahdi.o] Error 1 gmake[1]: Leaving directory `/usr/ports/net/asterisk/work/asterisk-1.4.22/channels' gmake: *** [channels] Error 2 --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ --------------------------------------------------------------------------- From njm at njm.me.uk Thu Dec 11 14:23:57 2008 From: njm at njm.me.uk (N.J. Mann) Date: Thu Dec 11 14:24:05 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081203131234.GD70240@hades.panopticon> References: <20081202201610.GA8753@atarininja.org> <20081203131234.GD70240@hades.panopticon> Message-ID: <20081211215712.GA72408@titania.njm.me.uk> In message <20081203131234.GD70240@hades.panopticon>, Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: > * G. Paul Ziemba (pz-freebsd-ports@ziemba.us) wrote: [...] > > > 2. I'm not sure we need the test for *.orig|*.rej|*~|*,v, but it > > wouldn't hurt. Maybe it helps admins who are actively developing > > local patches. I see that it's in the existing do-patch code above. > > I suppose that check was done to help to detect patching failures, so it > may be removed. I've just been trying out your patch and I think from an organisational point of view it is very good. What I mean by this is that with the patch I am now able to keep my local patches completely separate from the official, FreeBSD patches. No more backing up the whole of /usr/ports just in case I have a private patch in there somewhere. Now I just need to backup /usr/ports.localpatchdir (which is what I called the directory LOCAPATCHDIR points to). However, please consider putting back in the test for *.orig and *~ files. That way one can be actively be hacking on a patch without having to keep deleting editor backup files, which you may not wish to delete anyway, before attempting another build. In my case I see no need to skip *.rej and *,v files, but others may have a need for them. I hope some form of your patch gets into the tree once 7.1 ships. Cheers, Nick. -- From jpedras at webvolution.net Thu Dec 11 17:25:38 2008 From: jpedras at webvolution.net (Joao Pedras) Date: Thu Dec 11 17:25:44 2008 Subject: FreeBSD Port: apache-2.2.9_5 Message-ID: <4941B9BC.2060508@webvolution.net> Greetings, I would like to report that apache-2.2.9 port doesn't include usr/local/etc/rc.d/* into a binary package. I am doing this in RELENG_7 using 'make package-recursive'. Thanks. From beckman at angryox.com Thu Dec 11 19:13:01 2008 From: beckman at angryox.com (Peter Beckman) Date: Thu Dec 11 19:13:07 2008 Subject: portupgrade and freebsd-update: A better way? Message-ID: So I took on binary upgrading one of my FreeBSD servers today from 6.2-RELEASE to 7.0-RELEASE. Many useful sites outline exactly how to do this right, and they are mostly useful. Except when it comes to ports. http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html http://www.cyberciti.biz/faq/howto-freebsd-server-upgrades/ You get a few production servers with 200+ ports installed, and upgrading could take several days and lots of headaches and a lot of babysitting. Is there some sort of automated way that someone smart has figured out how to determine which ports are actually affected by the upgrade, so I only have to upgrade a hopefully small subset of installed ports? Are ALL the libraries upgraded during the OS upgrade modified in a way that breaks ALL existing ports? My gut says no, but my brain says it's not trivial to match the two together to limit the number of times you have to rebuild a port. Is there a better way? Does portsnap or portmanager or portupgrade keep track? What have I missed? Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ --------------------------------------------------------------------------- From yanefbsd at gmail.com Thu Dec 11 21:46:40 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Dec 11 21:46:45 2008 Subject: portupgrade and freebsd-update: A better way? In-Reply-To: References: Message-ID: <7d6fde3d0812112146o28596b11vdf730f2b3afc9759@mail.gmail.com> On Thu, Dec 11, 2008 at 7:13 PM, Peter Beckman wrote: > So I took on binary upgrading one of my FreeBSD servers today from > 6.2-RELEASE to 7.0-RELEASE. Many useful sites outline exactly how to do > this right, and they are mostly useful. > > Except when it comes to ports. > > > http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html > http://www.cyberciti.biz/faq/howto-freebsd-server-upgrades/ > > You get a few production servers with 200+ ports installed, and upgrading > could take several days and lots of headaches and a lot of babysitting. > > Is there some sort of automated way that someone smart has figured out how > to determine which ports are actually affected by the upgrade, so I only > have to upgrade a hopefully small subset of installed ports? Are ALL the > libraries upgraded during the OS upgrade modified in a way that breaks ALL > existing ports? My gut says no, but my brain says it's not trivial to > match the two together to limit the number of times you have to rebuild a > port. > > Is there a better way? Does portsnap or portmanager or portupgrade keep > track? What have I missed? > > Beckman 7.x and 6.2 aren't ABI compatible, so unfortunately no, you have to babysit a bit. -Garrett From swhetzel at gmail.com Thu Dec 11 22:25:38 2008 From: swhetzel at gmail.com (Scot Hetzel) Date: Thu Dec 11 22:25:45 2008 Subject: portupgrade and freebsd-update: A better way? In-Reply-To: References: Message-ID: <790a9fff0812112225p3bb549d6iab5c76bffb86bea1@mail.gmail.com> On 12/11/08, Peter Beckman wrote: > So I took on binary upgrading one of my FreeBSD servers today from > 6.2-RELEASE to 7.0-RELEASE. Many useful sites outline exactly how to do > this right, and they are mostly useful. > > Except when it comes to ports. > > > http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html > > http://www.cyberciti.biz/faq/howto-freebsd-server-upgrades/ > > You get a few production servers with 200+ ports installed, and upgrading > could take several days and lots of headaches and a lot of babysitting. > > Is there some sort of automated way that someone smart has figured out how > to determine which ports are actually affected by the upgrade, so I only > have to upgrade a hopefully small subset of installed ports? Are ALL the > libraries upgraded during the OS upgrade modified in a way that breaks ALL > existing ports? My gut says no, but my brain says it's not trivial to > match the two together to limit the number of times you have to rebuild a > port. > > Is there a better way? Does portsnap or portmanager or portupgrade keep > track? What have I missed? > If you have the compat6x port installed, you will not need to upgrade any of the 200+ ports on those productions servers. If you upgrade one port, you'll then need to upgrade all of it dependencies, as well as the ports that depend on these dependencies. To minimize your down time, you should set up a port build server that will build these 200+ ports as packages. On the production systems, you would use portupgrade to install the pre-built packages Scot From yanefbsd at gmail.com Thu Dec 11 22:32:18 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Dec 11 22:32:28 2008 Subject: portupgrade and freebsd-update: A better way? In-Reply-To: <790a9fff0812112225p3bb549d6iab5c76bffb86bea1@mail.gmail.com> References: <790a9fff0812112225p3bb549d6iab5c76bffb86bea1@mail.gmail.com> Message-ID: <7d6fde3d0812112232w71b69c3ekb239483d5ab83314@mail.gmail.com> On Thu, Dec 11, 2008 at 10:25 PM, Scot Hetzel wrote: > On 12/11/08, Peter Beckman wrote: >> So I took on binary upgrading one of my FreeBSD servers today from >> 6.2-RELEASE to 7.0-RELEASE. Many useful sites outline exactly how to do >> this right, and they are mostly useful. >> >> Except when it comes to ports. >> >> >> http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html >> >> http://www.cyberciti.biz/faq/howto-freebsd-server-upgrades/ >> >> You get a few production servers with 200+ ports installed, and upgrading >> could take several days and lots of headaches and a lot of babysitting. >> >> Is there some sort of automated way that someone smart has figured out how >> to determine which ports are actually affected by the upgrade, so I only >> have to upgrade a hopefully small subset of installed ports? Are ALL the >> libraries upgraded during the OS upgrade modified in a way that breaks ALL >> existing ports? My gut says no, but my brain says it's not trivial to >> match the two together to limit the number of times you have to rebuild a >> port. >> >> Is there a better way? Does portsnap or portmanager or portupgrade keep >> track? What have I missed? >> > If you have the compat6x port installed, you will not need to upgrade > any of the 200+ ports on those productions servers. > > If you upgrade one port, you'll then need to upgrade all of it > dependencies, as well as the ports that depend on these dependencies. > > To minimize your down time, you should set up a port build server that > will build these 200+ ports as packages. On the production systems, > you would use portupgrade to install the pre-built packages > > Scot True... forgot about compat6x. -Garrett From amdmi3 at amdmi3.ru Fri Dec 12 02:25:43 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Fri Dec 12 02:25:50 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081211215712.GA72408@titania.njm.me.uk> References: <20081202201610.GA8753@atarininja.org> <20081203131234.GD70240@hades.panopticon> <20081211215712.GA72408@titania.njm.me.uk> Message-ID: <20081212102516.GB7422@hades.panopticon> * N.J. Mann (njm@njm.me.uk) wrote: > > I suppose that check was done to help to detect patching failures, so it > > may be removed. > > I've just been trying out your patch and I think from an organisational > point of view it is very good. What I mean by this is that with the > patch I am now able to keep my local patches completely separate from > the official, FreeBSD patches. No more backing up the whole of > /usr/ports just in case I have a private patch in there somewhere. Now > I just need to backup /usr/ports.localpatchdir (which is what I called > the directory LOCAPATCHDIR points to). Nice to hear that it's useful :) > However, please consider putting back in the test for *.orig and *~ > files. That way one can be actively be hacking on a patch without > having to keep deleting editor backup files, which you may not wish to > delete anyway, before attempting another build. In my case I see no > need to skip *.rej and *,v files, but others may have a need for them. Done, patch updated. Btw, as someone who uses it, what do you think about the fact that local patches are applied after FreeBSD ones? (see my doubts up the thread). > I hope some form of your patch gets into the tree once 7.1 ships. Will try to make it in after the release. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From amdmi3 at amdmi3.ru Fri Dec 12 02:29:30 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Fri Dec 12 02:29:35 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: References: <20081209181354.GB29817@hades.panopticon> <87tz9di38u.fsf@chateau.d.lf> <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> Message-ID: <20081212102905.GC7422@hades.panopticon> * Jeremy Messenger (mezz7@cox.net) wrote: >> So if I understand correctly, you're proposing to only use dynamic >> plist generation for the ports that support it without modification, >> i.e. autotools-based? >> >> My opinion is that we should support the feature for all ports, or don't >> support it at all. Only getting rid of ~5k pkg-plists is not a huge >> accomplishment considering the mess it causes and I doubt it's worth >> the work on adding the feature to port.mk and then rebuilding and >> testing all affected ports. Being able to forget about pkg-plists >> once and forever however would be a huge accomplishment and if that's >> possible it should be done sooner or later. > > I object on get rid of pkg-plist. I depend on pkg-plist too much. I think > it's important for us to keep on track where the files/directories are. It's useful for me too sometimes, but it's already not 100% reliable, as some ports still generate it dynamically, some use PLIST_FILES, some use PLIST_SUB so it's not apparent under which path and/or name the file mentioned in plist is actually installed. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From amdmi3 at amdmi3.ru Fri Dec 12 02:38:52 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Fri Dec 12 02:38:59 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <87vdtqls4g.fsf@chateau.d.lf> References: <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> <6161f3180812110156n43803ee9s88443b6777bd0743@mail.gmail.com> <20081211113556.GA7422@hades.panopticon> <87vdtqls4g.fsf@chateau.d.lf> Message-ID: <20081212103827.GD7422@hades.panopticon> * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: > Yes, that is why I mentioned having a variable which enables this > behaviour, by default it is disabled. I mean ports which are okay > with providing static plists are fine, but ports which aren't > predictable with what files are going to installed can go with this > dynamic plist support, where ports infrastructure will only help in > generating a plist from an already setup directory tree > (/var/tmp/${portname}), now it is maintainer's responsibility to make > sure that all files will be installed in /var/tmp/${portname} which > {s,}he can do by either using 'make install DESTDIR=/var/tmp/${portname}' > or something similar if supported by port's upstream or {s,}he has to > add installation commands in ports Makefile rather than going with > upstream's way of installing things. I really don't see any point in supporting this only in individual ports. If you can do something, you expect (and should be able) to do it with any and all ports. > > See > > http://lists.freebsd.org/pipermail/freebsd-ports/2006-August/034745.html > > those are some real examples of complexity and resulting confusion, > > from first variant of DESTDIR support in ports. Now, when we have > > one DESTDIR implementation, adding another will likely make some heads > > explode, just think of variable naming. > > The DESTDIR issue in above link refers to the DESTDIR support[1] present in > FreeBSD Ports system, and the one which I'm talking about has nothing to > do with that. Yes, I just meant that that'll bring too much confusion. > > I'll remind that what we are talking about is automatic plist generation, > > and I think that this can be done without any hacks like installing a > > port into intermediate directory before real installation just by > > logging all writes to the filesystem. > > Yes that intermediate directory is what DESTDIR is. And if you're > capable of logging all writes in the DESTDIR, then its cool, but No. If there's DESTDIR, you don't need to log writes to it, as you can just use `find` to see what's there after installation as in quote below. The idea is that if we log all writes to the fulesystem during port installation, we don't need intermediate directory at all. > remember you're also talking about installing port in an intermediate > directory. After the port gets installed in intermediate directory, the > plist can be generated with your filesystem writes logger component or a > well tested version of following simply command line: > > % find /var/tmp/${PORTNAME} -type f |sed -e \ > "s[/var/tmp/${PORTNAME}${PREFIX}/[[g" > plist.tmp -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From mail at ozzmosis.com Fri Dec 12 03:59:12 2008 From: mail at ozzmosis.com (andrew clarke) Date: Fri Dec 12 03:59:20 2008 Subject: [ImageMagick] build problem In-Reply-To: <20081211132740.GN60731@albert.catwhisker.org> References: <20081211114807.b23377b2.regisr@pobox.com> <20081211132740.GN60731@albert.catwhisker.org> Message-ID: <20081212115908.GA90370@ozzmosis.com> On Thu 2008-12-11 05:27:40 UTC-0800, David Wolfskill (david@catwhisker.org) wrote: > On Thu, Dec 11, 2008 at 11:48:07AM +0100, regisr wrote: > > When building ImageMagick-6.4.7-5 on FreeBSD 6.4 I have a build error: > > > > /usr/obj/home/ports/graphics/ImageMagick/work/ImageMagick-6.4.7-5/tests/.libs/co > > nstitute -storagetype > > double /usr/obj/home/ports/graphics/ImageMagick/work/Image > > Magick-6.4.7-5/tests/input_truecolor.miff cmy Constitute check failed: > > 6615/0.0587497/0.843137 FAIL: tests/constitute_double_cmy.sh > > For what it's worth, I did not encounter this. Me neither. > Running on: > > > FreeBSD g1-35.catwhisker.org 6.4-STABLE FreeBSD 6.4-STABLE #659: Thu > Dec 11 05:01:52 PST 2008 > root@g1-35.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY i386 $ uname -a FreeBSD blizzard.phoenix 6.4-RELEASE FreeBSD 6.4-RELEASE #0: Wed Nov 26 11:43:51 UTC 2008 root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 $ pwd /usr/ports/graphics/ImageMagick $ cd /usr/ports/graphics/ImageMagick $ make showconfig ===> The following configuration options are available for ImageMagick-nox11-6.4.7.5: X11=off "X11 support" IMAGEMAGICK_TESTS=on "Run bundled self-tests after build" IMAGEMAGICK_OPENMP=off "OpenMP for SMP (needs threads)" IMAGEMAGICK_PERL=off "Perl support" IMAGEMAGICK_MODULES=off "Modules support (broken)" IMAGEMAGICK_BZLIB=on "Bzlib support" IMAGEMAGICK_16BIT_PIXEL=on "16bit pixel support" IMAGEMAGICK_DJVU=off "DJVU format support (needs threads)" IMAGEMAGICK_LCMS=off "LCMS support" IMAGEMAGICK_HDRI=off "High Dynamic Range Images (HDRI)" IMAGEMAGICK_TTF=off "Freetype support" IMAGEMAGICK_FONTCONFIG=off "Fontconfig support" IMAGEMAGICK_JPEG=on "JPG format support" IMAGEMAGICK_OPENEXR=off "OpenEXR support (needs threads)" IMAGEMAGICK_PNG=on "PNG format support" IMAGEMAGICK_TIFF=on "TIFF format support" IMAGEMAGICK_FPX=off "FPX format support" IMAGEMAGICK_JBIG=off "JBIG format support" IMAGEMAGICK_JPEG2000=off "JPEG2000 format support" IMAGEMAGICK_DOT=off "GraphViz dot graphs support" IMAGEMAGICK_WMF=off "WMF format support" IMAGEMAGICK_SVG=off "SVG format support" IMAGEMAGICK_PDF=off "PDF format support" IMAGEMAGICK_GSLIB=off "libgs (Postscript SHLIB) support" ===> Use 'make config' to modify these settings From beckman at angryox.com Fri Dec 12 08:20:11 2008 From: beckman at angryox.com (Peter Beckman) Date: Fri Dec 12 08:20:18 2008 Subject: portupgrade and freebsd-update: A better way? In-Reply-To: <7d6fde3d0812112146o28596b11vdf730f2b3afc9759@mail.gmail.com> References: <7d6fde3d0812112146o28596b11vdf730f2b3afc9759@mail.gmail.com> Message-ID: On Thu, 11 Dec 2008, Garrett Cooper wrote: > On Thu, Dec 11, 2008 at 7:13 PM, Peter Beckman wrote: > >> You get a few production servers with 200+ ports installed, and upgrading >> could take several days and lots of headaches and a lot of babysitting. >> >> Is there a better way? Does portsnap or portmanager or portupgrade keep >> track? What have I missed? > > 7.x and 6.2 aren't ABI compatible, so unfortunately no, you have to > babysit a bit. Is there some sort of chart that shows binary application compatibility between FreeBSD versions? That'd be handy. It took me a bit to find out that GENERIC now included SMP, but several google searches have led me to no good data. I found this: http://people.freebsd.org/~deischen/symver/library_versioning.txt But `cat /usr/src/lib/libc/Versions.def` got me no real data. I did also find this: http://wiki.freebsd.org/VendorInformation "No compatibility for API and ABI is guaranteed from one to the next major release, though an effort is made to make the upgrade process and source code changes as untroubled as possible." Is it safe to assume ABI compatibility between minor releases (6.1 -> 6.2) and must recompile everything between major releases (6.3 -> 7.0)? Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ --------------------------------------------------------------------------- From seventhdayslumber at mac.com Fri Dec 12 08:41:54 2008 From: seventhdayslumber at mac.com (Seventh Day Slumber) Date: Fri Dec 12 08:42:01 2008 Subject: SDS Newsletter Message-ID: Your email client cannot read this email. To view it online, please go here: http://www.newsletterserve.com/display.php?M=237786&C=b4213c1f912b09c8bff11f75dffc0df3&S=1080&L=200&N=1003 To stop receiving these emails:http://www.newsletterserve.com/unsubscribe.php?M=237786&C=b4213c1f912b09c8bff11f75dffc0df3&L=200&N=1080 From beckman at angryox.com Fri Dec 12 08:59:50 2008 From: beckman at angryox.com (Peter Beckman) Date: Fri Dec 12 09:00:23 2008 Subject: portupgrade and freebsd-update: A better way? In-Reply-To: <7d6fde3d0812112146o28596b11vdf730f2b3afc9759@mail.gmail.com> References: <7d6fde3d0812112146o28596b11vdf730f2b3afc9759@mail.gmail.com> Message-ID: <01b801c95c78$c07b3260$41719720$@com> On Thu, 11 Dec 2008, Garrett Cooper wrote: > On Thu, Dec 11, 2008 at 7:13 PM, Peter Beckman wrote: > >> You get a few production servers with 200+ ports installed, and upgrading >> could take several days and lots of headaches and a lot of babysitting. >> >> Is there a better way? Does portsnap or portmanager or portupgrade keep >> track? What have I missed? > > 7.x and 6.2 aren't ABI compatible, so unfortunately no, you have to > babysit a bit. Is there some sort of chart that shows binary application compatibility between FreeBSD versions? That'd be handy. It took me a bit to find out that GENERIC now included SMP, but several google searches have led me to no good data. I found this: http://people.freebsd.org/~deischen/symver/library_versioning.txt But `cat /usr/src/lib/libc/Versions.def` got me no real data. I did also find this: http://wiki.freebsd.org/VendorInformation "No compatibility for API and ABI is guaranteed from one to the next major release, though an effort is made to make the upgrade process and source code changes as untroubled as possible." Is it safe to assume ABI compatibility between minor releases (6.1 -> 6.2) and must recompile everything between major releases (6.3 -> 7.0)? Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ --------------------------------------------------------------------------- _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From wahjava.ml at gmail.com Fri Dec 12 09:29:46 2008 From: wahjava.ml at gmail.com (Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IA==?= =?utf-8?B?4KS24KWB4KSV4KWN4KSy?=) Date: Fri Dec 12 09:29:52 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081212103827.GD7422@hades.panopticon> (Dmitry Marakasov's message of "Fri, 12 Dec 2008 13:38:27 +0300") References: <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> <6161f3180812110156n43803ee9s88443b6777bd0743@mail.gmail.com> <20081211113556.GA7422@hades.panopticon> <87vdtqls4g.fsf@chateau.d.lf> <20081212103827.GD7422@hades.panopticon> Message-ID: <86wse5wb9m.fsf@chateau.d.lf> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 194 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081212/57834bcb/attachment-0001.pgp From pschmehl_lists at tx.rr.com Fri Dec 12 12:38:23 2008 From: pschmehl_lists at tx.rr.com (Paul Schmehl) Date: Fri Dec 12 12:38:30 2008 Subject: Problems with php5 upgrade Message-ID: I recently portupgraded a box and now I'm having problems with two ports that fail to upgrade; devel/php5-spl and security/php5-filter. Both of them fail because they can't find the pcre header file. According to UPDATING, pcre is now distributed as part of the core install of php5 I've deleted php5-pcre and run pkgdb -F but I'm still having problems with those two ports. I followed the instructions in UPDATING for the pecl has and json ports, and those worked fine. For some reason these two ports can't find that header file. Will deinstalling and reinstalling php6 fix the problem? Is there another way to fix it? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* Check the headers before clicking on Reply. From ale at FreeBSD.org Fri Dec 12 13:04:55 2008 From: ale at FreeBSD.org (Alex Dupre) Date: Fri Dec 12 13:05:03 2008 Subject: Problems with php5 upgrade In-Reply-To: References: Message-ID: <4942D1F4.20206@FreeBSD.org> Paul Schmehl wrote: > Will deinstalling and reinstalling php6 fix the problem? Yes. -- Alex Dupre From pschmehl_lists at tx.rr.com Fri Dec 12 13:58:56 2008 From: pschmehl_lists at tx.rr.com (Paul Schmehl) Date: Fri Dec 12 13:59:02 2008 Subject: Problems with php5 upgrade In-Reply-To: <4942D1F4.20206@FreeBSD.org> References: <4942D1F4.20206@FreeBSD.org> Message-ID: <799E3A2A38D82235439B77FC@utd65257.utdallas.edu> --On Friday, December 12, 2008 15:04:52 -0600 Alex Dupre wrote: > > Paul Schmehl wrote: >> Will deinstalling and reinstalling php6 fix the problem? > > Yes. > Thanks, Alex. That fixed the problem. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* Check the headers before clicking on Reply. From advertise at worldhyip.com Fri Dec 12 14:10:40 2008 From: advertise at worldhyip.com (advertise@worldhyip.com) Date: Fri Dec 12 14:10:46 2008 Subject: Passive Income - Up to $37,500.00 Message-ID: Passive Income - Up to $37,500.00 This is not a joke! Open this site now and look how easy you can get cash only within 5 hours. If you not trust, do not enter to our site. But once you open our site, you'll know how easy to make home income. Only within 5 hours. 5 HOURS TO BE RICH - [1]ENTER NOW!!! References 1. http://5ivehourspayment.com/ From freebsd-ports-local at be-well.ilk.org Fri Dec 12 19:09:16 2008 From: freebsd-ports-local at be-well.ilk.org (Lowell Gilbert) Date: Fri Dec 12 19:09:22 2008 Subject: portupgrade and freebsd-update: A better way? In-Reply-To: (Peter Beckman's message of "Fri\, 12 Dec 2008 11\:20\:10 -0500") References: <7d6fde3d0812112146o28596b11vdf730f2b3afc9759@mail.gmail.com> Message-ID: <443agsbxta.fsf@lowell-desk.lan> Peter Beckman writes: > Is it safe to assume ABI compatibility between minor releases (6.1 -> 6.2) > and must recompile everything between major releases (6.3 -> 7.0)? That's the intended approach, but read the release notes and updating instructions rather than assuming anything. From romain at blogreen.org Sat Dec 13 02:52:29 2008 From: romain at blogreen.org (Romain =?iso-8859-1?Q?Tarti=E8re?=) Date: Sat Dec 13 02:52:36 2008 Subject: Maintaining meta-data for patches Message-ID: <20081213103348.GA80526@blogreen.org> Hi! As a port maintainer, you sometimes have to provide patches in your ports in order to have a piece of code working. If you maintain projects in a team, you will likely have to handle patches that you wrote along with patches that your co-workers have created. While this situation is not hard to handle while creating the port, it is slightly more complex when you want to update the port in question. You have to deal with each patch and see if it is still relevant, and since you don't have many info about it, you first have to figure out what it is supposed to fix. Generally, you try with / without the patch and see if you keep it, but don't go any further (search is the bug has been reported upstream, if solutions have been provided upstream, etc.). If I consider for example the port of Mono: http://code.google.com/p/bsd-sharp/source/browse/trunk/lang/mono/files We have 13 patches I want to review in order to cleanup the port. I would like to ask random questions like: - who made this patch? [*] - what is-it supposed to do? [*] - has it been reported upstream? where? - is it fixed in projects trunk upstream? - will it expire at some point (e.g. trunk has been fixed after foo-1.0.1 was tagged so the patch will be useless as soon as foo is at version>1.0.1) Questions marked with a * can be answered directly using some version control system (even if in my case it will not help much since most patches come from revision 3: ?Initial import: copy of the cvs repo.?). I am so wondering if anyone has ever setup some tools to ease collaborative ports maintenance? Thanks! Romain -- Romain Tarti?re http://romain.blogreen.org/ pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081213/fe89eea7/attachment.pgp From njm at njm.me.uk Sat Dec 13 02:55:49 2008 From: njm at njm.me.uk (N.J. Mann) Date: Sat Dec 13 02:55:56 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081212102516.GB7422@hades.panopticon> References: <20081202201610.GA8753@atarininja.org> <20081203131234.GD70240@hades.panopticon> <20081211215712.GA72408@titania.njm.me.uk> <20081212102516.GB7422@hades.panopticon> Message-ID: <20081213105545.GA40560@titania.njm.me.uk> In message <20081212102516.GB7422@hades.panopticon>, Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: > * N.J. Mann (njm@njm.me.uk) wrote: > > > > I suppose that check was done to help to detect patching failures, so it > > > may be removed. > > > > I've just been trying out your patch and I think from an organisational > > point of view it is very good. What I mean by this is that with the > > patch I am now able to keep my local patches completely separate from > > the official, FreeBSD patches. No more backing up the whole of > > /usr/ports just in case I have a private patch in there somewhere. Now > > I just need to backup /usr/ports.localpatchdir (which is what I called > > the directory LOCAPATCHDIR points to). > > Nice to hear that it's useful :) I found that it was not quite enough. For one port I am developing local patches for I found I either needed to modify the ports' FreeBSD Makefile or add a post-extract script. Since I no longer want to have locally modified files in /usr/ports I needed to have a local post-extract script. So, I have modified your change to support both patch files and script files. %%%%% --- bsd.port.mk~ +++ bsd.port.mk @@ -591,6 +591,13 @@ # Default: ${MASTERDIR}/files # PKGDIR - A directory containing any package creation files. # Default: ${MASTERDIR} +# LOCALDIRPREFIX +# - Root of local patches and scripts tree. +# LOCALPATCHDIR - An optional directory for storing local patches. +# Default: ${LOCALDIRPREFIX}/${CATEGORY}/${PORT}/files +# LOCALSCRIPTDIR +# - An optional directory for storing local scripts. +# Default: ${LOCALDIRPREFIX}/${CATEGORY}/${PORT}/scripts # # Variables that serve as convenient "aliases" for your *-install targets. # Use these like: "${INSTALL_PROGRAM} ${WRKSRC}/prog ${PREFIX}/bin". @@ -1371,6 +1378,11 @@ SCRIPTDIR?= ${MASTERDIR}/scripts PKGDIR?= ${MASTERDIR} +.if defined(LOCALDIRPREFIX) +LOCALPATCHDIR?= ${LOCALDIRPREFIX}/${.CURDIR:C/^.*\/([^\/]+\/[^\/]+)$/\\1/}/files +LOCALSCRIPTDIR?= ${LOCALDIRPREFIX}/${.CURDIR:C/^.*\/([^\/]+\/[^\/]+)$/\\1/}/scripts +.endif + .if defined(USE_IMAKE) && !defined(USE_X_PREFIX) USE_X_PREFIX= yes .endif @@ -3604,6 +3616,35 @@ done; \ fi; \ fi +.if defined(LOCALPATCHDIR) + @if [ -d ${LOCALPATCHDIR} ]; then \ + if [ "`${ECHO_CMD} ${LOCALPATCHDIR}/patch-*`" != "${LOCALPATCHDIR}/patch-*" ]; then \ + ${ECHO_MSG} "===> Applying local patches for ${PKGNAME}" ; \ + PATCHES_APPLIED="" ; \ + for i in ${LOCALPATCHDIR}/patch-*; do \ + case $$i in \ + *.orig|*.rej|*~|*,v) \ + ${ECHO_MSG} "===> Ignoring patchfile $$i" ; \ + ;; \ + *) \ + if [ ${PATCH_DEBUG_TMP} = yes ]; then \ + ${ECHO_MSG} "===> Applying local patch $$i" ; \ + fi; \ + if ${PATCH} ${PATCH_ARGS} < $$i ; then \ + PATCHES_APPLIED="$$PATCHES_APPLIED $$i" ; \ + else \ + ${ECHO_MSG} `${ECHO_CMD} "=> Local patch $$i failed to apply cleanly." | ${SED} "s|${LOCALPATCHDIR}/||"` ; \ + if [ x"$$PATCHES_APPLIED" != x"" ]; then \ + ${ECHO_MSG} `${ECHO_CMD} "=> Local patch(es) $$PATCHES_APPLIED applied cleanly." | ${SED} "s|${LOCALPATCHDIR}/||g"` ; \ + fi; \ + ${FALSE} ; \ + fi; \ + ;; \ + esac; \ + done; \ + fi; \ + fi +.endif .endif .if !target(run-autotools) @@ -4248,6 +4289,12 @@ cd ${.CURDIR} && ${SETENV} ${SCRIPTS_ENV} ${SH} \ ${SCRIPTDIR}/${.TARGET:S/-script$//}; \ fi +.if defined(LOCALSCRIPTDIR) + @if [ -f ${LOCALSCRIPTDIR}/${.TARGET:S/-script$//} ]; then \ + cd ${.CURDIR} && ${SETENV} ${SCRIPTS_ENV} ${SH} \ + ${LOCALSCRIPTDIR}/${.TARGET:S/-script$//}; \ + fi +.endif .endif .endfor %%%%% > > However, please consider putting back in the test for *.orig and *~ > > files. That way one can be actively be hacking on a patch without > > having to keep deleting editor backup files, which you may not wish to > > delete anyway, before attempting another build. In my case I see no > > need to skip *.rej and *,v files, but others may have a need for them. > > Done, patch updated. > > Btw, as someone who uses it, what do you think about the fact that > local patches are applied after FreeBSD ones? (see my doubts up the > thread). I think the local patches should be applied after the FreeBSD ones. It just seems more logical. I just see problems occurring if the local patches are applied prior to the FreeBSD ones. For example, if a FreeBSD patch changes and no longer applies due to changes made by a local (previously applied) patch, what do you do? You would have to modify the FreeBSD patch locally which surely is partly what the idea of local patches is trying to prevent. Conversely, when local patches are applied after FreeBSD ones, if a local patch fails to apply because a FreeBSD patch has changed, you change the local patch. No problem! :-) Cheers, Nick. -- From njm at njm.me.uk Sat Dec 13 04:05:25 2008 From: njm at njm.me.uk (N.J. Mann) Date: Sat Dec 13 04:05:32 2008 Subject: Proposal: mechanism for local patches In-Reply-To: <20081213105545.GA40560@titania.njm.me.uk> References: <20081202201610.GA8753@atarininja.org> <20081203131234.GD70240@hades.panopticon> <20081211215712.GA72408@titania.njm.me.uk> <20081212102516.GB7422@hades.panopticon> <20081213105545.GA40560@titania.njm.me.uk> Message-ID: <20081213120522.GB40560@titania.njm.me.uk> In message <20081213105545.GA40560@titania.njm.me.uk>, N.J. Mann (njm@njm.me.uk) wrote: > In message <20081212102516.GB7422@hades.panopticon>, > Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: > > * N.J. Mann (njm@njm.me.uk) wrote: > > > > > > I suppose that check was done to help to detect patching failures, so it > > > > may be removed. > > > > > > I've just been trying out your patch and I think from an organisational > > > point of view it is very good. What I mean by this is that with the > > > patch I am now able to keep my local patches completely separate from > > > the official, FreeBSD patches. No more backing up the whole of > > > /usr/ports just in case I have a private patch in there somewhere. Now > > > I just need to backup /usr/ports.localpatchdir (which is what I called > > > the directory LOCAPATCHDIR points to). > > > > Nice to hear that it's useful :) > > I found that it was not quite enough. For one port I am developing > local patches for I found I either needed to modify the ports' FreeBSD > Makefile or add a post-extract script. Since I no longer want to have > locally modified files in /usr/ports I needed to have a local > post-extract script. So, I have modified your change to support both > patch files and script files. I spoke too soon. :-( I found I needed LOCALPATCHDIR and LOCALSCRIPTDIR in the environment passed to the my script and so had to change my patch. %%%%% --- bsd.port.mk.orig +++ bsd.port.mk @@ -591,6 +591,13 @@ # Default: ${MASTERDIR}/files # PKGDIR - A directory containing any package creation files. # Default: ${MASTERDIR} +# LOCALDIRPREFIX +# - Root of local patches and scripts tree. +# LOCALPATCHDIR - An optional directory for storing local patches. +# Default: ${LOCALDIRPREFIX}/${CATEGORY}/${PORT}/files +# LOCALSCRIPTDIR +# - An optional directory for storing local scripts. +# Default: ${LOCALDIRPREFIX}/${CATEGORY}/${PORT}/scripts # # Variables that serve as convenient "aliases" for your *-install targets. # Use these like: "${INSTALL_PROGRAM} ${WRKSRC}/prog ${PREFIX}/bin". @@ -1371,6 +1378,11 @@ SCRIPTDIR?= ${MASTERDIR}/scripts PKGDIR?= ${MASTERDIR} +.if defined(LOCALDIRPREFIX) +LOCALPATCHDIR?= ${LOCALDIRPREFIX}/${.CURDIR:C/^.*\/([^\/]+\/[^\/]+)$/\\1/}/files +LOCALSCRIPTDIR?= ${LOCALDIRPREFIX}/${.CURDIR:C/^.*\/([^\/]+\/[^\/]+)$/\\1/}/scripts +.endif + .if defined(USE_IMAKE) && !defined(USE_X_PREFIX) USE_X_PREFIX= yes .endif @@ -2887,6 +2899,14 @@ SCRIPTS_ENV+= BATCH=yes .endif +.if defined(LOCALPATCHDIR) +SCRIPTS_ENV+= LOCALPATCHDIR=${LOCALPATCHDIR} +.endif + +.if defined(LOCALSCRIPTDIR) +SCRIPTS_ENV+= LOCALSCRIPTDIR=${LOCALSCRIPTDIR} +.endif + .if ${PREFIX} == /usr MANPREFIX?= /usr/share .else @@ -3604,6 +3624,35 @@ done; \ fi; \ fi +.if defined(LOCALPATCHDIR) + @if [ -d ${LOCALPATCHDIR} ]; then \ + if [ "`${ECHO_CMD} ${LOCALPATCHDIR}/patch-*`" != "${LOCALPATCHDIR}/patch-*" ]; then \ + ${ECHO_MSG} "===> Applying local patches for ${PKGNAME}" ; \ + PATCHES_APPLIED="" ; \ + for i in ${LOCALPATCHDIR}/patch-*; do \ + case $$i in \ + *.orig|*.rej|*~|*,v) \ + ${ECHO_MSG} "===> Ignoring patchfile $$i" ; \ + ;; \ + *) \ + if [ ${PATCH_DEBUG_TMP} = yes ]; then \ + ${ECHO_MSG} "===> Applying local patch $$i" ; \ + fi; \ + if ${PATCH} ${PATCH_ARGS} < $$i ; then \ + PATCHES_APPLIED="$$PATCHES_APPLIED $$i" ; \ + else \ + ${ECHO_MSG} `${ECHO_CMD} "=> Local patch $$i failed to apply cleanly." | ${SED} "s|${LOCALPATCHDIR}/||"` ; \ + if [ x"$$PATCHES_APPLIED" != x"" ]; then \ + ${ECHO_MSG} `${ECHO_CMD} "=> Local patch(es) $$PATCHES_APPLIED applied cleanly." | ${SED} "s|${LOCALPATCHDIR}/||g"` ; \ + fi; \ + ${FALSE} ; \ + fi; \ + ;; \ + esac; \ + done; \ + fi; \ + fi +.endif .endif .if !target(run-autotools) @@ -4248,6 +4297,12 @@ cd ${.CURDIR} && ${SETENV} ${SCRIPTS_ENV} ${SH} \ ${SCRIPTDIR}/${.TARGET:S/-script$//}; \ fi +.if defined(LOCALSCRIPTDIR) + @if [ -f ${LOCALSCRIPTDIR}/${.TARGET:S/-script$//} ]; then \ + cd ${.CURDIR} && ${SETENV} ${SCRIPTS_ENV} ${SH} \ + ${LOCALSCRIPTDIR}/${.TARGET:S/-script$//}; \ + fi +.endif .endif .endfor %%%%% Cheers, Nick. -- From amdmi3 at amdmi3.ru Sat Dec 13 04:19:34 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Sat Dec 13 04:19:42 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <86wse5wb9m.fsf@chateau.d.lf> References: <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> <6161f3180812110156n43803ee9s88443b6777bd0743@mail.gmail.com> <20081211113556.GA7422@hades.panopticon> <87vdtqls4g.fsf@chateau.d.lf> <20081212103827.GD7422@hades.panopticon> <86wse5wb9m.fsf@chateau.d.lf> Message-ID: <20081213121906.GA81902@hades.panopticon> * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: > > No. If there's DESTDIR, you don't need to log writes to it, as you > > can just use `find` to see what's there after installation as in > > quote below. The idea is that if we log all writes to the fulesystem > > during port installation, we don't need intermediate directory at > > all. > > Okay, so if we go with your approach, then can you tell me how do you > plan to go about logging writes to filesystem with your .so which you're > planning to preload as you mentioned in one of your mails in this thread ? The idea is to redefine functions that execute syscalls which will modify the filesystem add add loging there. Here's a test code http://www.amdmi3.ru/files/ldpreload.c. Compile it into shared lib and run `LD_PRELOAD=path_to_lib.so someapp`. It turned out to be not the best solution as it relies on environment heavily, and some apps may clear the environment (scons does this by default), or call syscalls via syscall(), instead of libc wrapper, thus it's not reliable enough. Another way is ptrace, which should intercept syscalls without fail. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From jmc-freebsd2 at milibyte.co.uk Sat Dec 13 05:16:25 2008 From: jmc-freebsd2 at milibyte.co.uk (Mike Clarke) Date: Sat Dec 13 05:16:33 2008 Subject: [ImageMagick] build problem Message-ID: <200812131252.19895.jmc-freebsd2@milibyte.co.uk> andrew clarke wrote: > On Thu 2008-12-11 05:27:40 UTC-0800, David Wolfskill (david at catwhisker.org) wrote: > > On Thu, Dec 11, 2008 at 11:48:07AM +0100, regisr wrote: > > > When building ImageMagick-6.4.7-5 on FreeBSD 6.4 I have a build > > > error: > > > > > > /usr/obj/home/ports/graphics/ImageMagick/work/ImageMagick-6.4.7-5 > > >/tests/.libs/co nstitute -storagetype > > > double /usr/obj/home/ports/graphics/ImageMagick/work/Image > > > Magick-6.4.7-5/tests/input_truecolor.miff cmy Constitute check > > > failed: 6615/0.0587497/0.843137 FAIL: > > > tests/constitute_double_cmy.sh > > > > For what it's worth, I did not encounter this. > > Me neither. I get this problem both with the default options and with the same options as you, i.e. curlew:/usr/ports/graphics/ImageMagick# make showconfig ===> The following configuration options are available for ImageMagick-nox11-6.4.7.5: X11=off "X11 support" IMAGEMAGICK_TESTS=on "Run bundled self-tests after build" IMAGEMAGICK_OPENMP=off "OpenMP for SMP (needs threads)" IMAGEMAGICK_PERL=off "Perl support" IMAGEMAGICK_MODULES=off "Modules support (broken)" IMAGEMAGICK_BZLIB=on "Bzlib support" IMAGEMAGICK_16BIT_PIXEL=on "16bit pixel support" IMAGEMAGICK_DJVU=off "DJVU format support (needs threads)" IMAGEMAGICK_LCMS=off "LCMS support" IMAGEMAGICK_HDRI=off "High Dynamic Range Images (HDRI)" IMAGEMAGICK_TTF=off "Freetype support" IMAGEMAGICK_FONTCONFIG=off "Fontconfig support" IMAGEMAGICK_JPEG=on "JPG format support" IMAGEMAGICK_OPENEXR=off "OpenEXR support (needs threads)" IMAGEMAGICK_PNG=on "PNG format support" IMAGEMAGICK_TIFF=on "TIFF format support" IMAGEMAGICK_FPX=off "FPX format support" IMAGEMAGICK_JBIG=off "JBIG format support" IMAGEMAGICK_JPEG2000=off "JPEG2000 format support" IMAGEMAGICK_DOT=off "GraphViz dot graphs support" IMAGEMAGICK_WMF=off "WMF format support" IMAGEMAGICK_SVG=off "SVG format support" IMAGEMAGICK_PDF=off "PDF format support" IMAGEMAGICK_GSLIB=off "libgs (Postscript SHLIB) support" curlew:/usr/ports/graphics/ImageMagick# uname -a FreeBSD curlew.lan 6.4-RELEASE FreeBSD 6.4-RELEASE #0: Sat Dec 13 10:56:34 GMT 2008 root@curlew.lan:/usr/obj/usr/src/sys/GENERIC i386 My ports were last updated on Dec 12 09:24 -- Mike Clarke From yanefbsd at gmail.com Sat Dec 13 11:33:45 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sat Dec 13 11:33:52 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081212102905.GC7422@hades.panopticon> References: <20081209181354.GB29817@hades.panopticon> <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> <20081212102905.GC7422@hades.panopticon> Message-ID: <7d6fde3d0812131133g3956eea7n6830eefde3532a4f@mail.gmail.com> On Fri, Dec 12, 2008 at 2:29 AM, Dmitry Marakasov wrote: > * Jeremy Messenger (mezz7@cox.net) wrote: > >>> So if I understand correctly, you're proposing to only use dynamic >>> plist generation for the ports that support it without modification, >>> i.e. autotools-based? >>> >>> My opinion is that we should support the feature for all ports, or don't >>> support it at all. Only getting rid of ~5k pkg-plists is not a huge >>> accomplishment considering the mess it causes and I doubt it's worth >>> the work on adding the feature to port.mk and then rebuilding and >>> testing all affected ports. Being able to forget about pkg-plists >>> once and forever however would be a huge accomplishment and if that's >>> possible it should be done sooner or later. >> >> I object on get rid of pkg-plist. I depend on pkg-plist too much. I think >> it's important for us to keep on track where the files/directories are. > > It's useful for me too sometimes, but it's already not 100% reliable, > as some ports still generate it dynamically, some use PLIST_FILES, some > use PLIST_SUB so it's not apparent under which path and/or name the file > mentioned in plist is actually installed. Getting rid of the plist files will force a major rewrite of pkg_install. Are you really comfortable doing that :\? -Garrett From yanefbsd at gmail.com Sat Dec 13 11:36:00 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sat Dec 13 11:36:07 2008 Subject: Maintaining meta-data for patches In-Reply-To: <20081213103348.GA80526@blogreen.org> References: <20081213103348.GA80526@blogreen.org> Message-ID: <7d6fde3d0812131135p5c47fcegd1115b2da2237427@mail.gmail.com> On Sat, Dec 13, 2008 at 2:33 AM, Romain Tarti?re wrote: > Hi! > > As a port maintainer, you sometimes have to provide patches in your > ports in order to have a piece of code working. If you maintain > projects in a team, you will likely have to handle patches that you > wrote along with patches that your co-workers have created. > > While this situation is not hard to handle while creating the port, it > is slightly more complex when you want to update the port in question. > You have to deal with each patch and see if it is still relevant, and > since you don't have many info about it, you first have to figure out > what it is supposed to fix. Generally, you try with / without the patch > and see if you keep it, but don't go any further (search is the bug has > been reported upstream, if solutions have been provided upstream, etc.). > > > If I consider for example the port of Mono: > http://code.google.com/p/bsd-sharp/source/browse/trunk/lang/mono/files > > We have 13 patches I want to review in order to cleanup the port. > > I would like to ask random questions like: > - who made this patch? [*] > - what is-it supposed to do? [*] > - has it been reported upstream? where? > - is it fixed in projects trunk upstream? > - will it expire at some point (e.g. trunk has been fixed after > foo-1.0.1 was tagged so the patch will be useless as soon as foo is > at version>1.0.1) > > Questions marked with a * can be answered directly using some version > control system (even if in my case it will not help much since most > patches come from revision 3: ?Initial import: copy of the cvs repo.?). > > > I am so wondering if anyone has ever setup some tools to ease > collaborative ports maintenance? > > > Thanks! > Romain No, but setting up svk is the best way to maintain local patches against a repository. I have yet to set it up though because I haven't taken the time to do so yet. -Garrett From freebsd at bitfreak.org Sat Dec 13 14:41:48 2008 From: freebsd at bitfreak.org (Darren Pilgrim) Date: Sat Dec 13 14:41:59 2008 Subject: What happened to devel/php5-pcre? Message-ID: <49443662.3010805@bitfreak.org> I updated my ports tree today and pkg_version tells me: php5-pcre-5.2.6_2 > succeeds index (index has 5.2.5) Which was caused by an out-of-date index. When I run make index: Generating INDEX-6 - please wait..pear-File_Archive-1.5.4: "/data/sys/ports/devel/php5-pcre" non-existent -- d ependency list incomplete ===> archivers/pear-File_Archive failed *** Error code 1 1 error *** Error code 1 Stop in /data/sys/ports. *** Error code 1 Stop in /data/sys/ports. Searching cvs-all shows a commit by ale on 2008-12-07 11:54:36 UTC in which: Log: Update to 5.2.7 release. Revision Changes Path 1.5 +0 -14 ports/devel/php5-pcre/Makefile (dead) 1.2 +0 -13 ports/devel/php5-pcre/files/patch-php_pcre.c (dead) However, the commit log doesn't indicate why this was done. The release notes for PHP 5.2.7 and don't mention anything about PCRE other than it was updated to v7.8 to fix CVE-2008-2371. I cvsup'ed ports-all twice, so I'm fairly sure my tree is sound. How do I fix this? From wxs at FreeBSD.org Sat Dec 13 14:50:26 2008 From: wxs at FreeBSD.org (Wesley Shields) Date: Sat Dec 13 14:50:32 2008 Subject: What happened to devel/php5-pcre? In-Reply-To: <49443662.3010805@bitfreak.org> References: <49443662.3010805@bitfreak.org> Message-ID: <20081213225025.GN150@atarininja.org> On Sat, Dec 13, 2008 at 02:25:38PM -0800, Darren Pilgrim wrote: > I updated my ports tree today and pkg_version tells me: > > php5-pcre-5.2.6_2 > succeeds index (index has 5.2.5) > > Which was caused by an out-of-date index. When I run make index: > > Generating INDEX-6 - please wait..pear-File_Archive-1.5.4: > "/data/sys/ports/devel/php5-pcre" non-existent -- d > ependency list incomplete > ===> archivers/pear-File_Archive failed > *** Error code 1 > 1 error > > > > *** Error code 1 > > Stop in /data/sys/ports. > *** Error code 1 > > Stop in /data/sys/ports. > > > Searching cvs-all shows a commit by ale on 2008-12-07 11:54:36 UTC in which: > > Log: > Update to 5.2.7 release. > > Revision Changes Path > 1.5 +0 -14 ports/devel/php5-pcre/Makefile (dead) > 1.2 +0 -13 ports/devel/php5-pcre/files/patch-php_pcre.c (dead) > > However, the commit log doesn't indicate why this was done. The release > notes for PHP 5.2.7 and don't mention anything about PCRE other than it > was updated to v7.8 to fix CVE-2008-2371. > > I cvsup'ed ports-all twice, so I'm fairly sure my tree is sound. > > How do I fix this? Take a look at UPDATING, specifically the 20081211 entry. -- WXS From roberthuff at rcn.com Sat Dec 13 14:58:18 2008 From: roberthuff at rcn.com (Robert Huff) Date: Sat Dec 13 14:58:25 2008 Subject: What happened to devel/php5-pcre? In-Reply-To: <49443662.3010805@bitfreak.org> References: <49443662.3010805@bitfreak.org> Message-ID: <18756.15212.970492.959732@jerusalem.litteratus.org> Darren Pilgrim writes: > How do I fix this? Have you read /usr/port/UPDATING? Robert Huff From freebsd at bitfreak.org Sat Dec 13 15:52:50 2008 From: freebsd at bitfreak.org (Darren Pilgrim) Date: Sat Dec 13 15:53:01 2008 Subject: What happened to devel/php5-pcre? In-Reply-To: <20081213225025.GN150@atarininja.org> References: <49443662.3010805@bitfreak.org> <20081213225025.GN150@atarininja.org> Message-ID: <49444AD2.4020403@bitfreak.org> Wesley Shields wrote: > Take a look at UPDATING, specifically the 20081211 entry. Yeah. What's funny is, I habitually read {src,ports}/UPDATING. Must be too much egg nog. :) Thanks. From yanegomi at gmail.com Sat Dec 13 19:29:23 2008 From: yanegomi at gmail.com (Garrett Cooper) Date: Sat Dec 13 19:29:54 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081209181354.GB29817@hades.panopticon> References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> <20081209181354.GB29817@hades.panopticon> Message-ID: On Dec 9, 2008, at 10:13 AM, Dmitry Marakasov wrote: > It's not like your proposal is bad, ports instantaneously tracking > upstream changes and not needing maintainers would really be cool, > but unfortunately that's practically impossible. Some software projects are switching over to this kind of a model, like glibc. -Garrett From wahjava.ml at gmail.com Sun Dec 14 01:07:34 2008 From: wahjava.ml at gmail.com (=?utf-8?B?4KSG4KS24KWA4KS3IOCktuClgeCkleCljeCksg==?= Ashish Shukla) Date: Sun Dec 14 01:07:40 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> <20081209181354.GB29817@hades.panopticon> Message-ID: <20081214090937.GC8403@chateau.d.lf> In , Garrett Cooper wrote: > On Dec 9, 2008, at 10:13 AM, Dmitry Marakasov wrote: > >> It's not like your proposal is bad, ports instantaneously tracking >> upstream changes and not needing maintainers would really be cool, >> but unfortunately that's practically impossible. > > Some software projects are switching over to this kind of a model, like > glibc. What kind of model ? You mean using repositories instead of release tarballs, hmm..? -- Ashish Shukla -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081214/6e26bef4/attachment.pgp From yanefbsd at gmail.com Sun Dec 14 01:08:37 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Dec 14 01:08:44 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081214090937.GC8403@chateau.d.lf> References: <87fxkxjywk.fsf@chateau.d.lf> <20081209143052.GA29817@hades.panopticon> <873agxjn1x.fsf@chateau.d.lf> <20081209181354.GB29817@hades.panopticon> <20081214090937.GC8403@chateau.d.lf> Message-ID: <7d6fde3d0812140108g49c95a5cg7c8610373b3dc6b@mail.gmail.com> On Sun, Dec 14, 2008 at 1:09 AM, ???? ????? Ashish Shukla wrote: > In , Garrett Cooper wrote: >> >> On Dec 9, 2008, at 10:13 AM, Dmitry Marakasov wrote: >> >>> It's not like your proposal is bad, ports instantaneously tracking >>> upstream changes and not needing maintainers would really be cool, >>> but unfortunately that's practically impossible. >> >> Some software projects are switching over to this kind of a model, like >> glibc. > > What kind of model ? You mean using repositories instead of release > tarballs, hmm..? Exactly. -Garrett From fenner at FreeBSD.org Sun Dec 14 02:00:04 2008 From: fenner at FreeBSD.org (Bill Fenner) Date: Sun Dec 14 02:00:10 2008 Subject: Possibly unbuildable ports reminder Message-ID: <200812141000.mBEA01xw056536@freefall.freebsd.org> Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/ports@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill "annoying port email" Fenner From postfix at bitfreak.org Sun Dec 14 03:40:06 2008 From: postfix at bitfreak.org (Darren Pilgrim) Date: Sun Dec 14 03:40:15 2008 Subject: Source-upgrading FreeBSD "breaks" postfix+dovecot? Message-ID: <4944EC3F.5080708@bitfreak.org> Tonight I source-upgraded a FreeBSD system from i386 6.3p5 to i386 6.4-R. I have postfix 2.5.5 and dovecot 1.1.7 installed with postfix using dovecot for SASL and dovecot LDA for mailbox delivery. After installing 6.4-R, postfix refused to work until I recompiled and reinstalled both it and dovecot. Dovecot itself (i.e., the IMAP server) worked fine. Postfix worked fine if I set smtpd_sasl_auth_enable=no and defer_transports=dovecot, effectively preventing postfix from using any dovecot bits. Examples of the logged errors: Before reinstalling anything: postfix/pipe[36617]: fatal: get_service_attr: unknown group: vmail postfix/qmgr[36614]: warning: private/dovecot socket: malformed response private/dovecot is the socket dovecot creates for SMTP AUTH. After recompiling and reinstalling just postfix: postfix/pipe[36755]: warning: unexpected end-of-input from dovecot socket while reading input attribute name postfix/pipe[36755]: warning: deliver_request_get: error receiving common attributes postfix/smtpd[36771]: fatal: no SASL authentication mechanisms This doesn't happen reliably so I've had little luck finding a cause. Searching on the error logs didn't yield any useful results. Does anyone else experience this? Does anyone know the cause? postconf -n and other configuration details available on request. From wahjava.ml at gmail.com Sun Dec 14 04:26:01 2008 From: wahjava.ml at gmail.com (Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IA==?= =?utf-8?B?4KS24KWB4KSV4KWN4KSy?=) Date: Sun Dec 14 04:26:09 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081213121906.GA81902@hades.panopticon> (Dmitry Marakasov's message of "Sat, 13 Dec 2008 15:19:06 +0300") References: <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> <6161f3180812110156n43803ee9s88443b6777bd0743@mail.gmail.com> <20081211113556.GA7422@hades.panopticon> <87vdtqls4g.fsf@chateau.d.lf> <20081212103827.GD7422@hades.panopticon> <86wse5wb9m.fsf@chateau.d.lf> <20081213121906.GA81902@hades.panopticon> Message-ID: <87hc57eyaz.fsf@chateau.d.lf> Dmitry Marakasov writes: > * Ashish Shukla ???? ????? (wahjava.ml@gmail.com) wrote: >> > No. If there's DESTDIR, you don't need to log writes to it, as you >> > can just use `find` to see what's there after installation as in >> > quote below. The idea is that if we log all writes to the fulesystem >> > during port installation, we don't need intermediate directory at >> > all. >> >> Okay, so if we go with your approach, then can you tell me how do you >> plan to go about logging writes to filesystem with your .so which you're >> planning to preload as you mentioned in one of your mails in this thread ? > The idea is to redefine functions that execute syscalls which will > modify the filesystem add add loging there. Here's a test code > http://www.amdmi3.ru/files/ldpreload.c. Compile it into shared lib > and run `LD_PRELOAD=path_to_lib.so someapp`. Cool, this works great :) . > It turned out to be not the best solution as it relies on environment > heavily, and some apps may clear the environment (scons does this > by default), or call syscalls via syscall(), instead of libc wrapper, > thus it's not reliable enough. > Another way is ptrace, which should intercept syscalls without fail. So, we're going with ptrace way, lets hope this way is foolproof :) . Thanks -- Ashish Shukla -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081214/1d66b25a/attachment.pgp From schweikh at schweikhardt.net Sun Dec 14 06:18:59 2008 From: schweikh at schweikhardt.net (Jens Schweikhardt) Date: Sun Dec 14 06:19:05 2008 Subject: Where are the java/jdk16 files? Message-ID: <20081214135726.GD22221@schweikhardt.net> hello, world\n i grabbed the latest ports.tar.gz and "make fetch" in java/jdk16 tells me [...] Please open http://download.java.net/jdk6/6u3/promoted/b05/index.html in a web browser. Download the Update 3 Source, jdk-6u3-fcs-src-b05-jrl-24_sep_2007.jar and the Source Binaries, jdk-6u3-fcs-bin-b05-jrl-24_sep_2007.jar and the Mozilla Headers, jdk-6u3-fcs-mozilla_headers-b05-unix-24_sep_2007.jar . [...] I can't find these files on that page. I surfed around half of download.java.net to find them elsewhere. No joy. Please hit me with the clue bat. :-) No, I'm not in a country where the paragraph at the page bottom applies: "International Use Restrictions - Due to limited intellectual property protection and enforcement in certain countries, the JDK source code may only be distributed to an authorized list of countries. You will not be able to access the source code if you are downloading from a country that is not on this list. We are continuously reviewing this list for addition of other countries." Even from freefall the page looks the same... Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) From schweikh at schweikhardt.net Sun Dec 14 08:36:21 2008 From: schweikh at schweikhardt.net (Jens Schweikhardt) Date: Sun Dec 14 08:36:28 2008 Subject: Where are the java/jdk16 files? In-Reply-To: References: <20081214135726.GD22221@schweikhardt.net> Message-ID: <20081214163608.GG22221@schweikhardt.net> On Mon, Dec 15, 2008 at 01:38:31AM +1100, Some Dude wrote: # do a google search for the exact name of the first file, then click on # the cached page that'll show the sources and links Thanks, dude ;-) That was exactly what I a minuta after sending to the list. But still, it appears that someone messed up the download page with the wrong contents. It's all java binary packages when the page is supposed to contain src jars (as it is still the case for the google-cached page; man, I love the google cache!). I ended up on the very same page from other links saying "Source". My intention is to bring this to the port maintainer's attention (Cc'd). Maybe they know a contact at Sun to fix the page contents. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) From cokane at FreeBSD.org Sun Dec 14 10:37:50 2008 From: cokane at FreeBSD.org (Coleman Kane) Date: Sun Dec 14 10:37:57 2008 Subject: APNG patch for graphics/png port Message-ID: <1229278954.1718.10.camel@localhost> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081214/a311dc9f/attachment.pgp From kline at thought.org Sun Dec 14 12:50:05 2008 From: kline at thought.org (Gary Kline) Date: Sun Dec 14 12:50:14 2008 Subject: Where are the java/jdk16 files? In-Reply-To: <20081214163608.GG22221@schweikhardt.net> References: <20081214135726.GD22221@schweikhardt.net> <20081214163608.GG22221@schweikhardt.net> Message-ID: <20081214203121.GB3311@thought.org> On Sun, Dec 14, 2008 at 05:36:08PM +0100, Jens Schweikhardt wrote: > On Mon, Dec 15, 2008 at 01:38:31AM +1100, Some Dude wrote: > # do a google search for the exact name of the first file, then click on > # the cached page that'll show the sources and links > > Thanks, dude ;-) > > That was exactly what I a minuta after sending to the list. But still, > it appears that someone messed up the download page with the wrong > contents. It's all java binary packages when the page is supposed to > contain src jars (as it is still the case for the google-cached page; > man, I love the google cache!). I ended up on the very same page from > other links saying "Source". My intention is to bring this to the port > maintainer's attention (Cc'd). Maybe they know a contact at Sun to fix > the page contents. > > Regards, > > Jens just a footnote: after _years_ of poking around sun's links, i finally tried google. and YES. "god bless mommy and daddy, godbless google-cache... ." -g > -- > Jens Schweikhardt http://www.schweikhardt.net/ > SIGSIG -- signature too long (core dumped) > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" -- Gary Kline kline@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 2.12a release of Jottings: http://jottings.thought.org/index.php From ache at nagual.pp.ru Sun Dec 14 15:46:32 2008 From: ache at nagual.pp.ru (Andrey Chernov) Date: Sun Dec 14 15:46:38 2008 Subject: APNG patch for graphics/png port In-Reply-To: <1229278954.1718.10.camel@localhost> References: <1229278954.1718.10.camel@localhost> Message-ID: <20081214232818.GA36767@nagual.pp.ru> On Sun, Dec 14, 2008 at 01:22:34PM -0500, Coleman Kane wrote: > One thing that I noticed was the APNG patch from here: > * http://littlesvr.ca/apng/. > This seems to be expected by Thunderbird and is part of the latest > source tree. Mozilla has been maintaining a format spec here: > * https://wiki.mozilla.org/APNG_Specification It should be either accepted by libpng developers (and this way appears in the png port automatically) or separate slave apng port should be made. Porter is poor replacement for developer, especially considering lots of security holes libpng long history. -- http://ache.pp.ru/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081214/47b4c89f/attachment.pgp From rodrigo at bebik.net Sun Dec 14 15:48:18 2008 From: rodrigo at bebik.net (Rodrigo (ros)) Date: Sun Dec 14 15:48:26 2008 Subject: Problem using GNU autotools Message-ID: <494596B3.7030200@bebik.net> Hi, I'm in trouble updating a port. The configuration / compilation and install manually from the console works fine. When I try to integrate it in a port Makefile, some "configure" scripts fail whit this message : [...] configure: warning: build_alias=amd64-portbld-freebsd6.3: invalid host type configure: error: can only configure for one host and one target at a time [...] As I can see this is caused by configuration scrpts generated by 2 versions of autoconf (2.13 and 2.61), who doesn't handle the same options. Looking inside the subdirectories I discover few Makefine.am or config.ac, but not all are in. So I can't use the alternative way to generate the makefiles... It looks weird, but how can I handle this properly ? - I remember you ./configure without options works fine - Cheers, Rodrigo OSORIO From cokane at FreeBSD.org Sun Dec 14 16:03:36 2008 From: cokane at FreeBSD.org (Coleman Kane) Date: Sun Dec 14 16:03:42 2008 Subject: APNG patch for graphics/png port In-Reply-To: <20081214232818.GA36767@nagual.pp.ru> References: <1229278954.1718.10.camel@localhost> <20081214232818.GA36767@nagual.pp.ru> Message-ID: <1229299403.1718.17.camel@localhost> On Mon, 2008-12-15 at 02:28 +0300, Andrey Chernov wrote: > On Sun, Dec 14, 2008 at 01:22:34PM -0500, Coleman Kane wrote: > > One thing that I noticed was the APNG patch from here: > > * http://littlesvr.ca/apng/. > > This seems to be expected by Thunderbird and is part of the latest > > source tree. Mozilla has been maintaining a format spec here: > > * https://wiki.mozilla.org/APNG_Specification > > It should be either accepted by libpng developers (and this way appears in > the png port automatically) or separate slave apng port should be made. > Porter is poor replacement for developer, especially considering lots of > security holes libpng long history. > That is a good point, though the author of libpng suggests the MNG format for animated graphics (and JNG as a jpeg version). This leads me to believe that he's probably uninterested in actually incorporating the APNG patch into libpng. Honestly, I don't understand why the mozilla people have decided to push this APNG standard now. Maybe I'll just go and post into that mozilla issue a complain about wasting development time on an unfinished spec that seems like a reimplementation of MNG. I'll write to Greg (author) and see what he says. This is one of those annoying points in software evolution where big entity A begins spreading around a patched version of Author B's software, which may end up rivaling Author B's implementation of the patch's functionality. -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081215/bc33bf17/attachment.pgp From david.karapetyan at gmail.com Sun Dec 14 20:22:10 2008 From: david.karapetyan at gmail.com (David Karapetyan) Date: Sun Dec 14 20:22:20 2008 Subject: Most Pager Message-ID: <20081215035811.GA3645@vagrant.hsd1.in.comcast.net> FreeBSD home19.hsd1.in.comcast.net 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #0: Mon Nov 24 06:43:33 UTC 2008 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 Hello everyone. My most pager stopped working properly a few minutes ago. I do not recall changing any settings. The problem is occurring with how it renders colors; I have specified in my mostrc that text be highlighted in green; however, most renders everything in black and white. Does anyone know how to remedy this; it was working fine a few hours ago. -- -- Best, David Karapetyan http://davidkarapetyan.homeunix.com University of Notre Dame Department of Mathematics 255 Hurley Hall Notre Dame, IN 46556-4618 Phone: 574-631-5706 Cell: 202-460-5173 Fax: 574-631-6579 From max at love2party.net Sun Dec 14 20:53:12 2008 From: max at love2party.net (Max Laier) Date: Sun Dec 14 20:53:18 2008 Subject: Most Pager In-Reply-To: <20081215035811.GA3645@vagrant.hsd1.in.comcast.net> References: <20081215035811.GA3645@vagrant.hsd1.in.comcast.net> Message-ID: <200812150540.33521.max@love2party.net> On Monday 15 December 2008 04:58:11 David Karapetyan wrote: > FreeBSD home19.hsd1.in.comcast.net 7.0-RELEASE-p6 FreeBSD > 7.0-RELEASE-p6 #0: Mon Nov 24 06:43:33 UTC 2008 > root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 > > Hello everyone. My most pager stopped working properly a few minutes > ago. I do not recall changing any settings. The problem is occurring > with how it renders colors; I have specified in my mostrc that text be > highlighted in green; however, most renders everything in black and > white. Does anyone know how to remedy this; it was working fine a few > hours ago. Is your TERMCAP environment set (correctly)? -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From mezz7 at cox.net Sun Dec 14 20:54:34 2008 From: mezz7 at cox.net (Jeremy Messenger) Date: Sun Dec 14 20:54:40 2008 Subject: APNG patch for graphics/png port In-Reply-To: <1229278954.1718.10.camel@localhost> References: <1229278954.1718.10.camel@localhost> Message-ID: On Sun, 14 Dec 2008 12:22:34 -0600, Coleman Kane wrote: > Hello, > > I recently played with building Thunderbird 3.0b1 from source (it works > pretty well, btw). I was playing with some of the options to enable > using the system versions of a number of libraries, rather than relying > upon statically linking them into the project. We should keep compile static link, because PNG folks disapprove Mozilla's APNG patch. It's what we did with Firefox 3. Cheers, Mezz > One thing that I noticed was the APNG patch from here: > * http://littlesvr.ca/apng/. > This seems to be expected by Thunderbird and is part of the latest > source tree. Mozilla has been maintaining a format spec here: > * https://wiki.mozilla.org/APNG_Specification > > Sadly the patch has lagged behind the latest releases of libpng. I > merged the patch into the latest version (1.2.33) that we use, and have > made an appropriate change to the port files of graphics/png. I think > that APNG support from libpng may be useful in other software as well. > > I am attaching the patch, to apply in /usr/ports, for anyone to test. So > far it doesn't seem to regress anything for me, and I can use > thunderbird 3 with --with-system-png=/usr/local in my .mozconfig. I'd > like to see some other testers, and get a comment from the graphics/png > maintainer. -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From bugmaster at FreeBSD.org Mon Dec 15 03:06:05 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 15 03:06:30 2008 Subject: Current unassigned ports problem reports Message-ID: <200812151106.mBFB64Na003327@freefall.freebsd.org> (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/129650 x11-fm/xfm runtime error o ports/129637 graphics/autotrace will not compile against current Im f ports/129629 databases/mysql-connector-odbc (3.51.26) compile fails o ports/129606 benchmarks/iozone does not support O_DIRECT o ports/129598 Update ports: finance/aqbanking, devel/gwenhywfar to 3 f ports/129478 multimedia/acidrip: patch file to commit to ports f ports/129453 ports-mgmt/jailaudit does not work since jail supporti f ports/129439 devel/libusb does not compile in FreeBSD 7.0-RELEASE f ports/129435 java/jakarta-commons-dbcp not BROKEN on jdk15 o ports/129402 New port: www/Template-Provider-FromDATA - load templa f ports/129369 Failed to build multimedia/mencoder with samba support f ports/129296 [PATCH] net-im/pidgin-libnotify: add Russian translati o ports/129043 Experimental version of net/poptop in FreeBSD ports o ports/128952 [NEW PORT] java/javadb: Sun's supported distribution o o ports/128846 New port: sysutils/linux-megacli2 - LSI MegaRAID SAS c o ports/128726 [NEW PORT] print/lyx16: Document processor interfaced f ports/128703 net/isc-dhcp40-client and net/isc-dhcp40-relay refer t o ports/128603 textproc/flex has too small capacity o ports/128558 New ports: emulators/sdlmame-devel f ports/128490 net/freenx port does not work properly on freebsd-7 st o ports/128384 new port x11/xorg-minimal o ports/128371 New port: textproc/ibus Intelligent Input Bus for Linu f ports/128323 Update of ports/x11-fonts/terminus-font f ports/128288 sysutils/hpacucli does not work f ports/128271 biology/ncbi-toolkit - blastall segfaults when output o ports/128140 update devel/pwlib to 2.4.1 to fit GNOME 2.24 f ports/128082 sysutils/megarc binary causes memory corruption f ports/128074 multimedia/mplayer does not play CSS encrypted DVDs f ports/128048 www/mod_proxy_html port installs broken configuration f ports/127995 net/isc-dhcp30-server creates a user/group with dynami f ports/127905 science/gramps: installation and runtime problems with f ports/127854 [PATCH] databases/couchdb: update to 0.8.1 o ports/127851 Port update: multimedia/libdvdnav-mplayer - Update to f ports/127810 print/hplip 2.8.2 can't talk to my usnb printer (HP PS o ports/127728 ports/games/freebsd-games doesn't build, and larn(6) s f ports/127513 mail/dcc-dccd sets home to /var/dcc even if you didn' o ports/127321 japanese/kon2-16dot: buffer overflow and mouse bugs f ports/127302 security/swatch: swatch-3.2.1_1 multiple issues f ports/127181 audio/musicpd logs warning s ports/127087 mail/bincimap port does not include an rc.d file o ports/126890 port update: lang/cmucl o ports/126674 New port: print/latex-babel o ports/126655 java/jboss4 can not take standard parameter "-b host_n s ports/126577 [Update]graphics/qgis:update to 0.11.0 f ports/126518 Unbroke archivers/lzo2 on i386 f ports/126228 [PATCH] mail/courier: new version 0.60.0 f ports/126161 security/bsp_upektfmess does not work on 7.0 f ports/126058 net/generic-nqs fails to compile f ports/126055 x11-toolkits/p5-Tk - segmentation fault running perl-t f ports/125960 sysutils/syscp lacks of chattr/chflags o ports/125719 shells/pdksh, zombie process's occouring on SMP Machin o ports/125714 [patch] www/httptunnel: users not added f ports/125362 New port: devel/ocaml-lwt (cooperative threading libra o ports/125324 editors/the (3.2) looses cursor when compiled with PDC o ports/125201 audio/aqualung crashes o ports/124905 new port: databases/sqlitejdbc 051 o ports/124597 [NEW PORT] net/callweaver: Fork of the popular Open So o ports/124548 net/mDNSResponder port incompatible with gnome desktop f ports/124238 sysutils/heartbeat: patch request f ports/123424 [NEW PORT] net/winexe o ports/123247 linux-firefox and linux-seamonkey from multiple users o ports/123239 New port: graphics/diamondbox Layer based photo editor o ports/123068 sysutils/bubblemon2 bubblemon-dockapp: error extractin f ports/122276 Compiled audio/musicpd segfaults on FreeBSD 7.0 o ports/121831 [PATCH] net/openbgpd: [SUMMARIZE CHANGES] o ports/121325 Xorg crashes when x11-wm/xcompmgr is running o ports/121259 New port: net/openamq OpenAMQ is a complete AMQP messa o ports/121050 New port: sysutils/heartbeat2 Linux High-Availability f ports/119183 [NEW PORT] net/freeradius-client: FreeRADIUS Client li f ports/118877 audio/streamripper does not detect song title from str f ports/116385 net/vnc using vnc.so crashes Xorg 7.3 when remote comp f ports/115304 multimedia/gpac-mp4box cannot import files larger than o ports/108795 ports/icc: Proposed update to icc port for intel compi f ports/107304 print/apsfilter does not print PDF to raw PostScript p o amd64/104311 ports/wine should be installable on amd64 s ports/85513 Intel C++ compiler not 100% binary compatible with sys 76 problems total. From kamikaze at bsdforen.de Mon Dec 15 03:26:37 2008 From: kamikaze at bsdforen.de (Dominic Fandrey) Date: Mon Dec 15 03:26:44 2008 Subject: firefox3 support in bsd.gecko.mk Message-ID: <49463ED0.5040804@bsdforen.de> There is no firefox3 support in bsd.gecko.mk. This seems to keep plugins and add-ons that would work in Firefox 3 as well from being ported. Regards From cyberbotx at cyberbotx.com Mon Dec 15 05:21:50 2008 From: cyberbotx at cyberbotx.com (Naram Qashat) Date: Mon Dec 15 05:22:00 2008 Subject: firefox3 support in bsd.gecko.mk In-Reply-To: <49463ED0.5040804@bsdforen.de> References: <49463ED0.5040804@bsdforen.de> Message-ID: <4946562B.3010205@cyberbotx.com> Dominic Fandrey wrote: > There is no firefox3 support in bsd.gecko.mk. This seems to keep > plugins and add-ons that would work in Firefox 3 as well from being > ported. As far as I understand, plugins for any Mozilla products are made using xulrunner now. Naram Qashat > Regards > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From mad at madpilot.net Mon Dec 15 07:28:26 2008 From: mad at madpilot.net (Guido Falsi) Date: Mon Dec 15 07:28:33 2008 Subject: rrdtool 1.3.3 and dejavu dependency Message-ID: <20081215152824.GA18862@megatron.madpilot.net> Hello, I have noted that the dependency in the subject has been added to the rrdtool port. This has the unfortunate effect of sucking in a libX11 dependency(others too...) which was not before. Maybe I'm an extremist, but I don't like having X11 pieces on headless server machines, I really don't see a reson for that(it also triggers some more ports on depending on them, since the configures find them...This is annoying at least). I don't want to look demanding, but I'd like to spell my thought, if anybody cares to listen. What is the reson for this added dependency? I read the PR but don't really see such effects.. I'm using mrtg and smokeping, with mrtg.cgi [1] and mailgraph.cgi. They all work fine, mailgraph at least seems to use the functionality described in the PR. Are we sure it isn't something else which is depending on dejavu? Thank you for listening. [1] http://www.fi.muni.cz/~kas/mrtg-rrd/ -- Guido Falsi From rotkaps_spam_trap at gmx.de Mon Dec 15 08:14:27 2008 From: rotkaps_spam_trap at gmx.de (Heino Tiedemann) Date: Mon Dec 15 08:14:35 2008 Subject: print/cm-super size mismatch References: <20081206083250.GA54798@melon.esperance-linux.co.uk> <20081207.035520.258690873.hrs@allbsd.org> Message-ID: Hiroki Sato wrote: > Frank Shute wrote > in <20081206083250.GA54798@melon.esperance-linux.co.uk>: > > fr> Hi, > fr> > fr> I just had a problem when building print/cm-super. > fr> > fr> cm-super.zip doesn't seem to exist in /usr/ports/distfiles/. > fr> => Attempting to fetch from ftp://ftp.funet.fi/pub/TeX/CTAN/fonts/ps-type1/. > fr> fetch: ftp://ftp.funet.fi/pub/TeX/CTAN/fonts/ps-type1/cm-super.zip: size mismatch: expected 67310332, actual 67319909 > fr> => Attempting to fetch from ftp://ctan.unsw.edu.au/tex-archive/fonts/ps-type1/. > fr> fetch: ftp://ctan.unsw.edu.au/tex-archive/fonts/ps-type1/cm-super.zip: Connection refused > fr> => Attempting to fetch from ftp://ftp.tex.ac.uk/tex-archive/fonts/ps-type1/. > fr> fetch: ftp://ftp.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super.zip: size mismatch: expected 67310332, actual 67319909 > fr> => Attempting to fetch from ftp://ftp.kddlabs.co.jp/CTAN/fonts/ps-type1/. > fr> > fr> It did fetch it from the jp mirror but slowly & build it. > fr> > fr> But I would have thought that the tarball at ftp.tex.ac.uk would be > fr> the canonical one. Any thoughts? > > This was because the distfile was updated. The port was also updated > just now, so please try the latest ports tree. Thank you for the > report! This Bug ist still There. I updated my ports collection, I deleteed all in my distfile folder -> then I tried it today, und got this: => cm-super.zip doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from ftp://ftp.funet.fi/pub/TeX/CTAN/fonts/ps-type1/. fetch: ftp://ftp.funet.fi/pub/TeX/CTAN/fonts/ps-type1/cm-super.zip: size mismatch: expected 67319909, actual 67310332 => Attempting to fetch from ftp://ctan.unsw.edu.au/tex-archive/fonts/ps-type1/. fetch: ftp://ctan.unsw.edu.au/tex-archive/fonts/ps-type1/cm-super.zip: Connection refused => Attempting to fetch from ftp://ftp.tex.ac.uk/tex-archive/fonts/ps-type1/. fetch: ftp://ftp.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super.zip: size mismatch: expected 67319909, actual 67310332 => Attempting to fetch from ftp://ftp.kddlabs.co.jp/CTAN/fonts/ps-type1/. fetch: ftp://ftp.kddlabs.co.jp/CTAN/fonts/ps-type1/cm-super.zip: size mismatch: expected 67319909, actual 67310332 => Attempting to fetch from ftp://ctan.tug.org/tex-archive/fonts/ps-type1/. fetch: ftp://ctan.tug.org/tex-archive/fonts/ps-type1/cm-super.zip: size mismatch: expected 67319909, actual 67310332 => Attempting to fetch from ftp://ftp.dante.de/tex-archive/fonts/ps-type1/. fetch: ftp://ftp.dante.de/tex-archive/fonts/ps-type1/cm-super.zip: size mismatch: expected 67319909, actual 67310332 => Attempting to fetch from http://ring.nict.go.jp/archives/text/CTAN/fonts/ps-type1/. fetch: http://ring.nict.go.jp/archives/text/CTAN/fonts/ps-type1/cm-super.zip: size mismatch: expected 67319909, actual 67310332 => Attempting to fetch from http://ring.sakura.ad.jp/archives/text/CTAN/fonts/ps-type1/. fetch: http://ring.sakura.ad.jp/archives/text/CTAN/fonts/ps-type1/cm-super.zip: No address record => Attempting to fetch from http://ring.riken.jp/archives/text/CTAN/fonts/ps-type1/. fetch: http://ring.riken.jp/archives/text/CTAN/fonts/ps-type1/cm-super.zip: size mismatch: expected 67319909, actual 67310332 => Attempting to fetch from ftp://ftp.chg.ru/pub/TeX/CTAN/fonts/ps-type1/. fetch: ftp://ftp.chg.ru/pub/TeX/CTAN/fonts/ps-type1/cm-super.zip: size mismatch: expected 67319909, actual 67310332 => Attempting to fetch from ftp://mirror.macomnet.net/pub/CTAN/fonts/ps-type1/. fetch: ftp://mirror.macomnet.net/pub/CTAN/fonts/ps-type1/cm-super.zip: size mismatch: expected 67319909, actual 67310332 => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/cm-super.zip: size mismatch: expected 67319909, actual 67310332 => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles/ and try again. *** Error code 1 Stop in /usr/ports/print/cm-super. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.16592.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=cm-super-0.3.3_1 UPGRADE_PORT_VER=0.3.3_1 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! print/cm-super (cm-super-0.3.3_1) (fetch error) From glewis at eyesbeyond.com Mon Dec 15 08:30:52 2008 From: glewis at eyesbeyond.com (Greg Lewis) Date: Mon Dec 15 08:31:01 2008 Subject: Where are the java/jdk16 files? In-Reply-To: <20081214163608.GG22221@schweikhardt.net> References: <20081214135726.GD22221@schweikhardt.net> <20081214163608.GG22221@schweikhardt.net> Message-ID: <20081215160245.GA89670@misty.eyesbeyond.com> On Sun, Dec 14, 2008 at 05:36:08PM +0100, Jens Schweikhardt wrote: > On Mon, Dec 15, 2008 at 01:38:31AM +1100, Some Dude wrote: > # do a google search for the exact name of the first file, then click on > # the cached page that'll show the sources and links > > Thanks, dude ;-) > > That was exactly what I a minuta after sending to the list. But still, > it appears that someone messed up the download page with the wrong > contents. It's all java binary packages when the page is supposed to > contain src jars (as it is still the case for the google-cached page; > man, I love the google cache!). I ended up on the very same page from > other links saying "Source". My intention is to bring this to the port > maintainer's attention (Cc'd). Maybe they know a contact at Sun to fix > the page contents. Well, this is quite a pain for us. I imagine that Sun would actually like us to switch to OpenJDK6 instead and won't want to put the source code back up. Unfortunately thats not something we can do instantly. What is really needed is for someone to host the current source files. The tricky part is you need some sort of click through agreement with the JRL. I don't have enough bandwidth to host such a large download unfortunately. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org From daniel at roe.ch Mon Dec 15 09:41:25 2008 From: daniel at roe.ch (Daniel Roethlisberger) Date: Mon Dec 15 09:41:34 2008 Subject: rrdtool 1.3.3 and dejavu dependency In-Reply-To: <20081215152824.GA18862@megatron.madpilot.net> References: <20081215152824.GA18862@megatron.madpilot.net> Message-ID: <20081215173812.GA42598@hobbes.ustdmz.roe.ch> Guido Falsi 2008-12-15: > I have noted that the dependency in the subject has been added > to the rrdtool port. > > This has the unfortunate effect of sucking in a libX11 > dependency(others too...) which was not before. > > Maybe I'm an extremist, but I don't like having X11 pieces on > headless server machines, I really don't see a reson for > that(it also triggers some more ports on depending on them, > since the configures find them...This is annoying at least). Even as the submitter of the PR in question, I fully agree. > I don't want to look demanding, but I'd like to spell my > thought, if anybody cares to listen. > > What is the reson for this added dependency? rrdtool requires a suitable font for it's graphing features. It used to ship with dejavu, but since the update to 1.3.0 it relies on fonts installed on the system (which the dependency on dejavu is providing). > I read the PR but don't really see such effects.. I'm using > mrtg and smokeping, with mrtg.cgi [1] and mailgraph.cgi. They > all work fine, mailgraph at least seems to use the > functionality described in the PR. > > Are we sure it isn't something else which is depending on > dejavu? Yes, pretty much. Note that rrdtool can fall back to other fonts, such as Bitstream Vera, but if no fonts are found, using `rrdtool graph` or language bindings such as RRDs::graph will fail. I just used Tobi's tutorial [2] to verify this again. Can you try to reproduce this with no fonts installed under /usr/local/lib/X11/fonts and using the tutorial [2] as a test? If it works for you, can you try to find out where it takes the font from? I guess it might be possible to make `rrdtool graph` work without the full install of x11-fonts/dejavu and all it's dependencies by either creating a lightweight dejavu font port without X11, or by adding dejavu to the rrdtool port somehow. I'm all open to better ideas than the current run-time dependency on x11-fonts/dejavu. I kind of hoped that the maintainer would be able to find a better solution, but unfortunately, there was no reaction from the maintainer. > Thank you for listening. > > [1] http://www.fi.muni.cz/~kas/mrtg-rrd/ [2] http://oss.oetiker.ch/rrdtool/tut/rrdtutorial.en.html -- Daniel Roethlisberger http://daniel.roe.ch/ From stephen at math.missouri.edu Mon Dec 15 09:50:10 2008 From: stephen at math.missouri.edu (Stephen Montgomery-Smith) Date: Mon Dec 15 09:50:16 2008 Subject: print/cm-super size mismatch In-Reply-To: References: <20081206083250.GA54798@melon.esperance-linux.co.uk> <20081207.035520.258690873.hrs@allbsd.org> Message-ID: <49469295.2010309@math.missouri.edu> Heino Tiedemann wrote: > Hiroki Sato wrote: > >> Frank Shute wrote >> in <20081206083250.GA54798@melon.esperance-linux.co.uk>: >> >> fr> Hi, >> fr> >> fr> I just had a problem when building print/cm-super. >> >> This was because the distfile was updated. The port was also updated >> just now, so please try the latest ports tree. Thank you for the >> report! > > This Bug ist still There. > > I updated my ports collection, I deleteed all in my distfile folder -> > then I tried it today, und got this: I had this problem yesterday, when it was fixed last week. My guess is that that the bug is not "still there" but that it was "renewed." I am thinking that distfile was updated yet again. The odd thing was that even the distfile on the freebsd site was wrong. Shouldn't the distfile on the freebsd site be the one that the port wants, rather than whatever the master sites have? Stephen From cmeyer1969+freebsd at gmail.com Mon Dec 15 10:32:11 2008 From: cmeyer1969+freebsd at gmail.com (Chris Meyer) Date: Mon Dec 15 10:32:23 2008 Subject: RT 3.8? Message-ID: Anyone out there working on a port of RT 3.8? The latest version in the tree is rt-3.6.7_1. There was some promising work a few months ago but everything seems to have stopped and there is nothing new in the ports tree... From wxs at FreeBSD.org Mon Dec 15 11:15:36 2008 From: wxs at FreeBSD.org (Wesley Shields) Date: Mon Dec 15 11:15:43 2008 Subject: RT 3.8? In-Reply-To: References: Message-ID: <20081215191535.GC33004@atarininja.org> On Mon, Dec 15, 2008 at 10:11:51AM -0800, Chris Meyer wrote: > Anyone out there working on a port of RT 3.8? > > The latest version in the tree is rt-3.6.7_1. > > There was some promising work a few months ago but everything seems to > have stopped and there is nothing new in the ports tree... Philip (pgollucci@) was working on it. I know he has been very busy with other commitments lately so he has not been able to polish the edges. There are two PRs related to this work which may be of interest to you or others who may be willing to pick up where Philip has left off: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/125745 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/125785 The first one appears to be where the relevant information is, and it includes links to http://people.freebsd.org/~pgollucci/rt38/ which has a TODO file in there. I have no idea how accurate these things are but it can be a good starting point to gather relevant information for people who want to pick up where Philip left off. I've also added him as CC to this reply so he can speak up if he has any more information to add. -- WXS From regisr at pobox.com Mon Dec 15 11:42:11 2008 From: regisr at pobox.com (regisr) Date: Mon Dec 15 11:42:18 2008 Subject: [ImageMagick] build problem In-Reply-To: <20081212115908.GA90370@ozzmosis.com> References: <20081211114807.b23377b2.regisr@pobox.com> <20081211132740.GN60731@albert.catwhisker.org> <20081212115908.GA90370@ozzmosis.com> Message-ID: <20081215204206.f0a195ce.regisr@pobox.com> On Thu 2008-12-11 05:27:40 UTC-0800, David Wolfskill wrote: > > For what it's worth, I did not encounter this. On Fri, 12 Dec 2008 22:59:08 +1100 andrew clarke wrote: > Me neither. > > > /usr/obj/home/ports/graphics/ImageMagick/work/ImageMagick-6.4.7-5/tests/.libs/co > > > nstitute -storagetype > > > double /usr/obj/home/ports/graphics/ImageMagick/work/Image > > > Magick-6.4.7-5/tests/input_truecolor.miff cmy Constitute check failed: > > > 6615/0.0587497/0.843137 FAIL: tests/constitute_double_cmy.sh The maintener corrected this on 10 Dec 2008 14:16:02... After a new cvsup I can build ImageMagick (see http://www.freshports.org/graphics/ImageMagick/ ) How can I have a 6.4.7-5 version with a modification not yet commited? Best regards -- regis From pgollucci at freebsd.org Mon Dec 15 11:42:25 2008 From: pgollucci at freebsd.org (Philip M. Gollucci) Date: Mon Dec 15 11:42:32 2008 Subject: RT 3.8? In-Reply-To: <20081215191535.GC33004@atarininja.org> References: <20081215191535.GC33004@atarininja.org> Message-ID: <4946B0C0.90106@freebsd.org> Wesley Shields wrote: > I've also added him as CC to this reply so he can speak up if he has any > more information to add. I've gotten several comments (esp recently). My first thought is to commit it as is and let the PRs come it. Several people have been using the prototype in production for a while now. I'm still mentored though and will not be in a position to provide TB(tinderbox) logs for a bit yet. -- ------------------------------------------------------------------------ Philip M. Gollucci (pgollucci@p6m7g8.com) c: 703.336.9354 Consultant - P6M7G8 Inc. http://p6m7g8.net Senior System Admin - RideCharge, Inc. http://ridecharge.com 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. From pgollucci at freebsd.org Mon Dec 15 11:46:06 2008 From: pgollucci at freebsd.org (Philip M. Gollucci) Date: Mon Dec 15 11:46:13 2008 Subject: RT 3.8? In-Reply-To: <20081215191535.GC33004@atarininja.org> References: <20081215191535.GC33004@atarininja.org> Message-ID: <4946B3FC.6040303@freebsd.org> Wesley Shields wrote: >> There was some promising work a few months ago but everything seems to >> have stopped and there is nothing new in the ports tree... > > Philip (pgollucci@) was working on it. I know he has been very busy > with other commitments lately so he has not been able to polish the > edges. > I've also added him as CC to this reply so he can speak up if he has any > more information to add. I think my first thought is to commit it as is and wait for the PRs to come it. I've had several reports of people using it in production for a while now. I know there are still some things that will change though, but I can't think of them off the top of my head. I'm still mentored, and won't be in a position to do a final tinderbox(tb) build for a bit just yet. Unfortunately, the RT ports in the tree (esp p5-) will need to change to use this instead since RT36 isn't packagable. Which is why they were still there, but they seem to have got comitted today by someone else. Also, we need to mark the other ports as deprecated and whack some of them. I'm pretty sure some of that qualifies as a sweep, so I don't know if we can do it yet, but I'm definitely not opposed to it. -- ------------------------------------------------------------------------ Philip M. Gollucci (pgollucci@p6m7g8.com) c: 703.336.9354 Consultant - P6M7G8 Inc. http://p6m7g8.net Senior System Admin - RideCharge, Inc. http://ridecharge.com 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. From wxs at FreeBSD.org Mon Dec 15 11:54:21 2008 From: wxs at FreeBSD.org (Wesley Shields) Date: Mon Dec 15 11:54:30 2008 Subject: RT 3.8? In-Reply-To: <4946B3FC.6040303@freebsd.org> References: <20081215191535.GC33004@atarininja.org> <4946B3FC.6040303@freebsd.org> Message-ID: <20081215195421.GE33004@atarininja.org> On Mon, Dec 15, 2008 at 02:46:04PM -0500, Philip M. Gollucci wrote: > Wesley Shields wrote: > >> There was some promising work a few months ago but everything seems to > >> have stopped and there is nothing new in the ports tree... > > > > Philip (pgollucci@) was working on it. I know he has been very busy > > with other commitments lately so he has not been able to polish the > > edges. > > > I've also added him as CC to this reply so he can speak up if he has any > > more information to add. > I think my first thought is to commit it as is and wait for the PRs to > come it. I've had several reports of people using it in production for > a while now. That's certainly good news. I'm willing to help field the PRs also. > I know there are still some things that will change though, but I can't > think of them off the top of my head. > > I'm still mentored, and won't be in a position to do a final > tinderbox(tb) build for a bit just yet. > > Unfortunately, the RT ports in the tree (esp p5-) will need to change to > use this instead since RT36 isn't packagable. Which is why they were > still there, but they seem to have got comitted today by someone else. > > Also, we need to mark the other ports as deprecated and whack some of them. If I can be of any assistance please let me know. > I'm pretty sure some of that qualifies as a sweep, so I don't know if we > can do it yet, but I'm definitely not opposed to it. I'd agree with you. Hopefully after the slush you can work to get them in and I'll help clean up with you. Thanks! -- WXS From m.seaman at infracaninophile.co.uk Mon Dec 15 12:06:56 2008 From: m.seaman at infracaninophile.co.uk (Matthew Seaman) Date: Mon Dec 15 12:07:03 2008 Subject: RT 3.8? In-Reply-To: <4946B3FC.6040303@freebsd.org> References: <20081215191535.GC33004@atarininja.org> <4946B3FC.6040303@freebsd.org> Message-ID: <4946B8CB.9080004@infracaninophile.co.uk> Philip M. Gollucci wrote: > Unfortunately, the RT ports in the tree (esp p5-) will need to change to > use this instead since RT36 isn't packagable. Which is why they were > still there, but they seem to have got comitted today by someone else. I'm the maintainer of the half dozen or so RT extension ports that just got committed last night. Updating them all (where feasible) to rt38 when it comes out always was the plan, but I'm glad to have them in the tree and usable with rt36 now. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 258 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081215/2c634631/signature.pgp From rock_on_the_web at comcen.com.au Mon Dec 15 13:16:29 2008 From: rock_on_the_web at comcen.com.au (Da Rock) Date: Mon Dec 15 13:16:35 2008 Subject: [Fwd: Re: Firebird client fails port install] Message-ID: <1229375777.1647.70.camel@laptop2.herveybayaustralia.com.au> I tried the questions list, but I can't seem to get an answer apart from a workaround (which I already implemented anyway). Any ideas on how to fix this? -------------- next part -------------- An embedded message was scrubbed... From: Da Rock Subject: Re: Firebird client fails port install Date: Tue, 16 Dec 2008 06:37:18 +1000 Size: 4914 Url: http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081215/fcd599c4/attachment.eml From cokane at FreeBSD.org Mon Dec 15 14:39:10 2008 From: cokane at FreeBSD.org (Coleman Kane) Date: Mon Dec 15 14:39:17 2008 Subject: APNG patch for graphics/png port In-Reply-To: References: <1229278954.1718.10.camel@localhost> Message-ID: <1229380736.6657.3.camel@localhost> On Sun, 2008-12-14 at 22:54 -0600, Jeremy Messenger wrote: > On Sun, 14 Dec 2008 12:22:34 -0600, Coleman Kane > wrote: > > > Hello, > > > > I recently played with building Thunderbird 3.0b1 from source (it works > > pretty well, btw). I was playing with some of the options to enable > > using the system versions of a number of libraries, rather than relying > > upon statically linking them into the project. > > We should keep compile static link, because PNG folks disapprove Mozilla's > APNG patch. It's what we did with Firefox 3. > > Cheers, > Mezz > Any idea why the mozilla folk jumped on further developing APNG, rather than just using (much more mature) MNG for the same purpose? -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081215/b4f005a0/attachment.pgp From kitchetech at gmail.com Mon Dec 15 15:02:44 2008 From: kitchetech at gmail.com (matt donovan) Date: Mon Dec 15 15:02:51 2008 Subject: firefox3 support in bsd.gecko.mk In-Reply-To: <4946562B.3010205@cyberbotx.com> References: <49463ED0.5040804@bsdforen.de> <4946562B.3010205@cyberbotx.com> Message-ID: <28283d910812151502i13a16979sc21453e15db8bbae@mail.gmail.com> On Mon, Dec 15, 2008 at 8:05 AM, Naram Qashat wrote: > Dominic Fandrey wrote: > >> There is no firefox3 support in bsd.gecko.mk. This seems to keep >> plugins and add-ons that would work in Firefox 3 as well from being >> ported. >> > > As far as I understand, plugins for any Mozilla products are made using > xulrunner now. > > Naram Qashat > > > Regards >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >> >> _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > it's just xulrunner and bsd.gecko.mk has it just that to use xulrunner you have to do make USE_GECKO=xulrunner install. but if you read /usr/ports/UPDATING it tells you how to use plugins inside of firefox3. From beech at alaskaparadise.com Mon Dec 15 16:15:28 2008 From: beech at alaskaparadise.com (Beech Rintoul) Date: Mon Dec 15 16:15:41 2008 Subject: Problem with net/x11vnc update. Message-ID: <200812151515.27475.beech@alaskaparadise.com> I'm trying to update the x11vnc port to the latest and I'm getting the following configure error: checking jpeglib.h usability... yes checking jpeglib.h presence... yes checking for jpeglib.h... yes checking for jpeg_CreateCompress in -ljpeg... no <------------ Note configure: WARNING: ========================================================================== *** The libjpeg compression library was not found. *** This may lead to reduced performance, especially over slow links. If libjpeg is in a non-standard location use --with-jpeg=DIR to indicate the header file is in DIR/include/jpeglib.h and the library in DIR/lib/libjpeg.a. A copy of libjpeg may be obtained from: ftp://ftp.uu.net/graphics/jpeg/ ========================================================================== I'm running -CURRENT as of Sunday and I tried adding the path in configure, but it makes no difference. I also tried googling but the only references I found were either Mac or FreeBSD 4.x. The previous version didn't have this check, so I don't know if this is a new or ongoing problem. Anyone have any thoughts on this? Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --------------------------------------------------------------------------------------- From beech at alaskaparadise.com Mon Dec 15 16:33:08 2008 From: beech at alaskaparadise.com (Beech Rintoul) Date: Mon Dec 15 16:33:14 2008 Subject: Problem with net/x11vnc update. In-Reply-To: <27FE0234-A135-4E40-97FE-D8091CF7D433@mac.com> References: <200812151515.27475.beech@alaskaparadise.com> <27FE0234-A135-4E40-97FE-D8091CF7D433@mac.com> Message-ID: <200812151533.06818.beech@alaskaparadise.com> On Monday 15 December 2008 15:25:34 Chuck Swiger wrote: > On Dec 15, 2008, at 4:15 PM, Beech Rintoul wrote: > > I'm trying to update the x11vnc port to the latest and I'm getting the > > following configure error: > > > > checking jpeglib.h usability... yes > > checking jpeglib.h presence... yes > > checking for jpeglib.h... yes > > checking for jpeg_CreateCompress in -ljpeg... no <------------ > > Note > > I see that symbol here: > > % nm /usr/local/lib/libjpeg.a | grep jpeg_CreateCompress > 00000000 T jpeg_CreateCompress > > % pkg_info | grep jpeg > jpeg-6b_7 IJG's jpeg compression utilities > > Are you sure you have the latest version of the port, and that you > have these files: > > /usr/local/lib/libjpeg.a > /usr/local/lib/libjpeg.la > /usr/local/lib/libjpeg.so > /usr/local/lib/libjpeg.so.9 > > ...? :-) > > Regards, Yes, I have the latest and all libs. My box shows: stargate# nm /usr/local/lib/libjpeg.a | grep jpeg_CreateCompress 00000340 T jpeg_CreateCompress So this appears to be a problem in configure. Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --------------------------------------------------------------------------------------- From yanefbsd at gmail.com Mon Dec 15 16:35:22 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Mon Dec 15 16:35:29 2008 Subject: Problem with net/x11vnc update. In-Reply-To: <200812151533.06818.beech@alaskaparadise.com> References: <200812151515.27475.beech@alaskaparadise.com> <27FE0234-A135-4E40-97FE-D8091CF7D433@mac.com> <200812151533.06818.beech@alaskaparadise.com> Message-ID: <7d6fde3d0812151635n2e268c12i91d3655ed47e4bf7@mail.gmail.com> On Mon, Dec 15, 2008 at 4:33 PM, Beech Rintoul wrote: > On Monday 15 December 2008 15:25:34 Chuck Swiger wrote: >> On Dec 15, 2008, at 4:15 PM, Beech Rintoul wrote: >> > I'm trying to update the x11vnc port to the latest and I'm getting the >> > following configure error: >> > >> > checking jpeglib.h usability... yes >> > checking jpeglib.h presence... yes >> > checking for jpeglib.h... yes >> > checking for jpeg_CreateCompress in -ljpeg... no <------------ >> > Note >> >> I see that symbol here: >> >> % nm /usr/local/lib/libjpeg.a | grep jpeg_CreateCompress >> 00000000 T jpeg_CreateCompress >> >> % pkg_info | grep jpeg >> jpeg-6b_7 IJG's jpeg compression utilities >> >> Are you sure you have the latest version of the port, and that you >> have these files: >> >> /usr/local/lib/libjpeg.a >> /usr/local/lib/libjpeg.la >> /usr/local/lib/libjpeg.so >> /usr/local/lib/libjpeg.so.9 >> >> ...? :-) >> >> Regards, > > Yes, I have the latest and all libs. My box shows: > > stargate# nm /usr/local/lib/libjpeg.a | grep jpeg_CreateCompress > 00000340 T jpeg_CreateCompress > > So this appears to be a problem in configure. > > Beech Bug filing time with the x11vnc folks :). -Garrett From cswiger at mac.com Mon Dec 15 16:42:58 2008 From: cswiger at mac.com (Chuck Swiger) Date: Mon Dec 15 16:43:04 2008 Subject: Problem with net/x11vnc update. In-Reply-To: <200812151515.27475.beech@alaskaparadise.com> References: <200812151515.27475.beech@alaskaparadise.com> Message-ID: <27FE0234-A135-4E40-97FE-D8091CF7D433@mac.com> On Dec 15, 2008, at 4:15 PM, Beech Rintoul wrote: > I'm trying to update the x11vnc port to the latest and I'm getting the > following configure error: > > checking jpeglib.h usability... yes > checking jpeglib.h presence... yes > checking for jpeglib.h... yes > checking for jpeg_CreateCompress in -ljpeg... no <------------ > Note I see that symbol here: % nm /usr/local/lib/libjpeg.a | grep jpeg_CreateCompress 00000000 T jpeg_CreateCompress % pkg_info | grep jpeg jpeg-6b_7 IJG's jpeg compression utilities Are you sure you have the latest version of the port, and that you have these files: /usr/local/lib/libjpeg.a /usr/local/lib/libjpeg.la /usr/local/lib/libjpeg.so /usr/local/lib/libjpeg.so.9 ...? :-) Regards, -- -Chuck From beech at alaskaparadise.com Mon Dec 15 16:56:15 2008 From: beech at alaskaparadise.com (Beech Rintoul) Date: Mon Dec 15 16:56:22 2008 Subject: Problem with net/x11vnc update. In-Reply-To: <7d6fde3d0812151635n2e268c12i91d3655ed47e4bf7@mail.gmail.com> References: <200812151515.27475.beech@alaskaparadise.com> <200812151533.06818.beech@alaskaparadise.com> <7d6fde3d0812151635n2e268c12i91d3655ed47e4bf7@mail.gmail.com> Message-ID: <200812151556.14259.beech@alaskaparadise.com> On Monday 15 December 2008 15:35:22 Garrett Cooper wrote: > On Mon, Dec 15, 2008 at 4:33 PM, Beech Rintoul wrote: > > On Monday 15 December 2008 15:25:34 Chuck Swiger wrote: > >> On Dec 15, 2008, at 4:15 PM, Beech Rintoul wrote: > >> > I'm trying to update the x11vnc port to the latest and I'm getting the > >> > following configure error: > >> > > >> > checking jpeglib.h usability... yes > >> > checking jpeglib.h presence... yes > >> > checking for jpeglib.h... yes > >> > checking for jpeg_CreateCompress in -ljpeg... no <------------ > >> > Note > >> > >> I see that symbol here: > >> > >> % nm /usr/local/lib/libjpeg.a | grep jpeg_CreateCompress > >> 00000000 T jpeg_CreateCompress > >> > >> % pkg_info | grep jpeg > >> jpeg-6b_7 IJG's jpeg compression utilities > >> > >> Are you sure you have the latest version of the port, and that you > >> have these files: > >> > >> /usr/local/lib/libjpeg.a > >> /usr/local/lib/libjpeg.la > >> /usr/local/lib/libjpeg.so > >> /usr/local/lib/libjpeg.so.9 > >> > >> ...? :-) > >> > >> Regards, > > > > Yes, I have the latest and all libs. My box shows: > > > > stargate# nm /usr/local/lib/libjpeg.a | grep jpeg_CreateCompress > > 00000340 T jpeg_CreateCompress > > > > So this appears to be a problem in configure. > > > > Beech > > Bug filing time with the x11vnc folks :). > -Garrett Yep, just did. I thought I'd ask the list first in case someone has seen this before. Thanks guys, Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --------------------------------------------------------------------------------------- From mezz7 at cox.net Mon Dec 15 21:02:44 2008 From: mezz7 at cox.net (Jeremy Messenger) Date: Mon Dec 15 21:02:51 2008 Subject: APNG patch for graphics/png port In-Reply-To: <1229380736.6657.3.camel@localhost> References: <1229278954.1718.10.camel@localhost> <1229380736.6657.3.camel@localhost> Message-ID: On Mon, 15 Dec 2008 16:38:56 -0600, Coleman Kane wrote: > On Sun, 2008-12-14 at 22:54 -0600, Jeremy Messenger wrote: >> On Sun, 14 Dec 2008 12:22:34 -0600, Coleman Kane >> wrote: >> >> > Hello, >> > >> > I recently played with building Thunderbird 3.0b1 from source (it >> works >> > pretty well, btw). I was playing with some of the options to enable >> > using the system versions of a number of libraries, rather than >> relying >> > upon statically linking them into the project. >> >> We should keep compile static link, because PNG folks disapprove >> Mozilla's >> APNG patch. It's what we did with Firefox 3. >> >> Cheers, >> Mezz >> > > Any idea why the mozilla folk jumped on further developing APNG, rather > than just using (much more mature) MNG for the same purpose? I have no idea. The google has found useful links and I think two URLs might help you. I didn't read there as I have no interest with and don't care about APNG vs MNG. http://mozilla.wikia.com/wiki/APNG_vs_MNG http://en.wikipedia.org/wiki/APNG#History Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From QAT at FreeBSD.org Mon Dec 15 21:43:22 2008 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Mon Dec 15 21:43:28 2008 Subject: cvs commit: ports/net/py-pcapy Makefile In-Reply-To: <200812160525.mBG5P4aw004299@repoman.freebsd.org> References: In-Reply-To: <200812160525.mBG5P4aw004299@repoman.freebsd.org> Message-ID: <20081216054327.4C6A912E424C@quark.ds9.tecnik93.com> Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/py25-pcapy-0.10.5.log : building py25-pcapy-0.10.5 in directory /var/tinderbox/7-STABLE-FTP maintained by: ports@FreeBSD.org building for: 7.1-PRERELEASE amd64 port directory: /usr/ports/net/py-pcapy Makefile ident: $FreeBSD: ports/net/py-pcapy/Makefile,v 1.5 2008/12/16 05:25:04 linimon Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Tue Dec 16 05:42:59 UTC 2008 ................................................... ================================================================ ======================================== add_pkg python25-2.5.2_3.tbz adding dependencies pkg_add python25-2.5.2_3.tbz skipping python25-2.5.2_3, already added ===> Installing for py25-pcapy-0.10.5 ===> py25-pcapy-0.10.5 depends on file: /usr/local/bin/python2.5 - found ===> Generating temporary packing list ===> Checking if net/py-pcapy already installed running install running build running build_ext running install_lib copying build/lib.freebsd-7.1-PRERELEASE-amd64-2.5/pcapy.so -> /usr/local/lib/python2.5/site-packages running install_data creating /usr/local/share/doc/pcapy copying README -> /usr/local/share/doc/pcapy copying LICENSE -> /usr/local/share/doc/pcapy copying pcapy.html -> /usr/local/share/doc/pcapy running install_egg_info Writing /usr/local/lib/python2.5/site-packages/pcapy-0.10.5-py2.5.egg-info ===> Registering installation for py25-pcapy-0.10.5 ================================================================ ======================================== ===> Building package for py25-pcapy-0.10.5 Creating package /tmp/packages/All/py25-pcapy-0.10.5.tbz Registering depends: python25-2.5.2_3. Creating bzip'd tar ball in '/tmp/packages/All/py25-pcapy-0.10.5.tbz' Deleting py25-pcapy-0.10.5 ================================================================ === Checking filesystem state list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) 9540292 4 drwxr-xr-x 2 root wheel 512 Dec 16 05:43 usr/local/share/doc/pcapy 9540293 8 -rw-r--r-- 1 root wheel 2697 Mar 28 2007 usr/local/share/doc/pcapy/README 9540294 8 -rw-r--r-- 1 root wheel 2657 Mar 28 2007 usr/local/share/doc/pcapy/LICENSE 9540295 60 -rw-r--r-- 1 root wheel 30315 Mar 28 2007 usr/local/share/doc/pcapy/pcapy.html ================================================================ build of /usr/ports/net/py-pcapy ended at Tue Dec 16 05:43:25 UTC 2008 A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From dstegner at earthlink.net Mon Dec 15 23:05:21 2008 From: dstegner at earthlink.net (Dave Stegner) Date: Mon Dec 15 23:05:28 2008 Subject: FreeBSD Port: exim-4.69_2 Message-ID: <000501c95f49$b69db550$69dea8c0@xws001> Am working with Exim, started a few months ago. I have 4.69 port. This evening I wanted to see if there was a newer version available. Still at 4.69, but changes say Makefile was updated 3 days ago to 1.240. I downloaded from webpage and examined files, specifically Makefile. It is still the old version, 1.237. I searched ftp site for exim-4.69_2, but could only find exim-4.69_1. Where have I gone wrong or how am I reading the info given wrong or is something else wrong??? David R. Stegner From beech at alaskaparadise.com Mon Dec 15 23:15:54 2008 From: beech at alaskaparadise.com (Beech Rintoul) Date: Mon Dec 15 23:16:01 2008 Subject: FreeBSD Port: exim-4.69_2 In-Reply-To: <000501c95f49$b69db550$69dea8c0@xws001> References: <000501c95f49$b69db550$69dea8c0@xws001> Message-ID: <200812152215.52640.beech@alaskaparadise.com> On Monday 15 December 2008 21:44:14 Dave Stegner wrote: > Am working with Exim, started a few months ago. I have 4.69 port. > > This evening I wanted to see if there was a newer version available. > > Still at 4.69, but changes say Makefile was updated 3 days ago to 1.240. > > I downloaded from webpage and examined files, specifically Makefile. > It is still the old version, 1.237. > > I searched ftp site for exim-4.69_2, but could only find exim-4.69_1. > > > Where have I gone wrong or how am I reading the info given wrong or is > something else wrong??? The new version is in the ports tree. Read the handbook on updating and use portsnap, portupgrade, or one of the other port utilities to update your tree, then build it yourself. If you're using binaries, you may have to wait a couple of weeks for the new package to show up in ftp. Packages are built on a continuing basis, but lag the tree by weeks sometimes. Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --------------------------------------------------------------------------------------- From beech at freebsd.org Tue Dec 16 00:04:36 2008 From: beech at freebsd.org (Beech Rintoul) Date: Tue Dec 16 00:04:42 2008 Subject: FreeBSD Port: exim-4.69_2 In-Reply-To: <200812152215.52640.beech@alaskaparadise.com> References: <000501c95f49$b69db550$69dea8c0@xws001> <200812152215.52640.beech@alaskaparadise.com> Message-ID: <200812152245.39924.beech@freebsd.org> On Monday 15 December 2008 22:15:52 Beech Rintoul wrote: > On Monday 15 December 2008 21:44:14 Dave Stegner wrote: > > Am working with Exim, started a few months ago. I have 4.69 port. > > > > This evening I wanted to see if there was a newer version available. > > > > Still at 4.69, but changes say Makefile was updated 3 days ago to 1.240. > > > > I downloaded from webpage and examined files, specifically Makefile. > > It is still the old version, 1.237. > > > > I searched ftp site for exim-4.69_2, but could only find exim-4.69_1. > > > > > > Where have I gone wrong or how am I reading the info given wrong or is > > something else wrong??? > > The new version is in the ports tree. Read the handbook on updating and use > portsnap, portupgrade, or one of the other port utilities to update your > tree, then build it yourself. If you're using binaries, you may have to > wait a couple of weeks for the new package to show up in ftp. Packages are > built on a continuing basis, but lag the tree by weeks sometimes. > > Beech Sorry, I meant to say use portsnap, or csup to update your tree. Then use portupgrade or one of the other utilities to update your ports. Beech -- --------------------------------------------------------------------------------------- Beech Rintoul - FreeBSD Developer - beech@FreeBSD.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.0R/announce.html --------------------------------------------------------------------------------------- From kamikaze at bsdforen.de Tue Dec 16 02:12:00 2008 From: kamikaze at bsdforen.de (Dominic Fandrey) Date: Tue Dec 16 02:12:07 2008 Subject: firefox3 support in bsd.gecko.mk In-Reply-To: <28283d910812151502i13a16979sc21453e15db8bbae@mail.gmail.com> References: <49463ED0.5040804@bsdforen.de> <4946562B.3010205@cyberbotx.com> <28283d910812151502i13a16979sc21453e15db8bbae@mail.gmail.com> Message-ID: <49477EC9.1050209@bsdforen.de> matt donovan wrote: > On Mon, Dec 15, 2008 at 8:05 AM, Naram Qashat wrote: > >> Dominic Fandrey wrote: >> >>> There is no firefox3 support in bsd.gecko.mk. This seems to keep >>> plugins and add-ons that would work in Firefox 3 as well from being >>> ported. >>> >> As far as I understand, plugins for any Mozilla products are made using >> xulrunner now. >> >> Naram Qashat >> >> >> Regards >> > > it's just xulrunner and bsd.gecko.mk has it just that to use xulrunner you > have to do make USE_GECKO=xulrunner install. but if you read > /usr/ports/UPDATING it tells you how to use plugins inside of firefox3. My trouble is with german/bsdforen-firefox-searchplugin, which pulls in www/firefox as a dependency. Sure I can use it with Firefox3, but I see no reason to have Firefox2 installed as well. From mad at madpilot.net Tue Dec 16 03:23:22 2008 From: mad at madpilot.net (Guido Falsi) Date: Tue Dec 16 03:23:29 2008 Subject: rrdtool 1.3.3 and dejavu dependency In-Reply-To: <20081215173812.GA42598@hobbes.ustdmz.roe.ch> References: <20081215152824.GA18862@megatron.madpilot.net> <20081215173812.GA42598@hobbes.ustdmz.roe.ch> Message-ID: <20081216112320.GB29493@megatron.madpilot.net> On Mon, Dec 15, 2008 at 06:38:12PM +0100, Daniel Roethlisberger wrote: > Even as the submitter of the PR in question, I fully agree. This is a good starting point :P > > I read the PR but don't really see such effects.. I'm using > > mrtg and smokeping, with mrtg.cgi [1] and mailgraph.cgi. They > > all work fine, mailgraph at least seems to use the > > functionality described in the PR. > > > > Are we sure it isn't something else which is depending on > > dejavu? > > Yes, pretty much. Note that rrdtool can fall back to other > fonts, such as Bitstream Vera, but if no fonts are found, using > `rrdtool graph` or language bindings such as RRDs::graph will > fail. I just used Tobi's tutorial [2] to verify this again. > > Can you try to reproduce this with no fonts installed under > /usr/local/lib/X11/fonts and using the tutorial [2] as a test? > If it works for you, can you try to find out where it takes the > font from? > > I guess it might be possible to make `rrdtool graph` work without > the full install of x11-fonts/dejavu and all it's dependencies by > either creating a lightweight dejavu font port without X11, or by > adding dejavu to the rrdtool port somehow. > > I'm all open to better ideas than the current run-time dependency > on x11-fonts/dejavu. I kind of hoped that the maintainer would > be able to find a better solution, but unfortunately, there was > no reaction from the maintainer. I made a few experiments on a spare PC at work(this is an AMD64 8.0 on which I was testing ZFS, grat work to all the developers for that). I reverted your change on the machine, defined WITHOUT_X11 and made sure all rrdtools dependencies where configured to require the least x11 pieces(cairo requires disabling both xcb and glitz support). The machine had no ports installed. I ended up with the following ports installed: bdftopcf-1.0.1 Convert X font from BDF to PCF bitstream-vera-1.10_4 Bitstream Vera TrueType font collection cairo-1.6.4_3,1 Vector graphics library with cross-device output support encodings-1.0.2,1 X.Org Encoding fonts expat-2.0.1 XML 1.0 parser written in C font-bh-ttf-1.0.0 X.Org Bigelow & Holmes TTF font font-misc-ethiopic-1.0.0 X.Org miscellaneous Ethiopic font font-misc-meltho-1.0.0_1 X.Org miscellaneous Meltho font font-util-1.0.1 Create an index of X font files in a directory fontcacheproto-0.1.2 Fontcache extension headers fontconfig-2.5.0,1 An XML-based font configuration API for X Windows fontsproto-2.0.2 Fonts extension headers freetype2-2.3.7 A free and portable TrueType font rendering engine gamin-0.1.9_2 A file and directory monitoring system gettext-0.17_1 GNU gettext package gio-fam-backend-2.16.5 FAM backend for GLib's GIO library glib-2.16.5_1 Some useful routines of C programming (current stable versi gmake-3.81_3 GNU version of 'make' utility icu-3.8.1_1 International Components for Unicode (from IBM) libXfont-1.3.1_3,1 X font libary libfontenc-1.0.4 The fontenc Library libiconv-1.11_1 A character set conversion library libtool-1.5.26 Generic shared library support script libxml2-2.6.32_2 XML parser library for GNOME mkfontdir-1.0.3_1 Create an index of X font files in a directory mkfontscale-1.0.3 Creates an index of scalable font files for X pango-1.20.5 An open-source framework for the layout and rendering of i1 pcre-7.8 Perl Compatible Regular Expressions library perl-5.8.8_1 Practical Extraction and Report Language pixman-0.10.0_2 Low-level pixel manipulation library pkg-config-0.23_1 A utility to retrieve information about installed libraries png-1.2.33 Library for manipulating PNG images python25-2.5.2_3 An interpreted object-oriented programming language rrdtool-1.3.3_2 Round Robin Database Tools xorg-fonts-truetype-7.3 X.Org TrueType fonts xproto-7.0.10_1 X11 protocol headers xtrans-1.0.4 Abstract network code for X As you can see it already sucked in various things and some fonts. I tried the tutorial and it works flawlessly in such a setup. I think the trick is this port: bitstream-vera-1.10_4. If there were some way to install dejavu without sucking in all of libX11 it would be good too. could you make your tests without dejavu but with bitstream-vera and see if it works? I see pango is depending on x11-fonts/xorg-fonts-truetype, which depends on some fonts pacjkages but not on libX11. Hope my feedback helps. -- Guido Falsi From eculp at encontacto.net Tue Dec 16 05:15:58 2008 From: eculp at encontacto.net (eculp) Date: Tue Dec 16 05:16:06 2008 Subject: Can't build Wine 1.1.10,1 port on up to date current. Message-ID: <20081216071554.19716ikpfazg3l8o@econet.encontacto.net> I am running up to date current latest cvsup this morning. # uname -a FreeBSD ed.local.net.mx 8.0-CURRENT FreeBSD 8.0-CURRENT #107: Mon Dec 15 07:08:45 CST 2008 root@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO i386 After wine 1.1.4 I started to have some functionality problems but it would still build with no problem. Now that I try the updated 1.1.10,1 I get as far as: ipstats.c: In function 'getNumArpEntries': ipstats.c:1253: error: 'RTF_LLINFO' undeclared (first use in this function) ipstats.c:1253: error: (Each undeclared identifier is reported only once ipstats.c:1253: error: for each function it appears in.) ipstats.c: In function 'getArpTable': ipstats.c:1311: error: 'RTF_LLINFO' undeclared (first use in this function) ipstats.c:1311: warning: initialization makes integer from pointer without a cast gmake[2]: *** [ipstats.o] Error 1 gmake[2]: Leaving directory `/usr/ports/emulators/wine/work/wine-1.1.10/dlls/iphlpapi' gmake[1]: *** [iphlpapi] Error 2 gmake[1]: Leaving directory `/usr/ports/emulators/wine/work/wine-1.1.10/dlls' gmake: *** [dlls] Error 2 *** Error code 2 Stop in /usr/ports/emulators/wine. ===>>> make failed for emulators/wine ===>>> Aborting update Any suggestions would be greatly appreciated. ed From eculp at encontacto.net Tue Dec 16 07:03:36 2008 From: eculp at encontacto.net (eculp) Date: Tue Dec 16 07:03:43 2008 Subject: Can't build Wine 1.1.10,1 port on up to date current. In-Reply-To: <18759.48677.138398.819711@jerusalem.litteratus.org> References: <20081216071554.19716ikpfazg3l8o@econet.encontacto.net> <18759.48677.138398.819711@jerusalem.litteratus.org> Message-ID: <20081216090332.17135dh6cgjg5kkc@econet.encontacto.net> Quoting Robert Huff : > > eculp writes: >> I am running up to date current latest cvsup this morning. >> # uname -a >> FreeBSD ed.local.net.mx 8.0-CURRENT FreeBSD 8.0-CURRENT #107: Mon Dec >> 15 07:08:45 CST 2008 >> root@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO i386 >> >> After wine 1.1.4 I started to have some functionality problems >> but it would still build with no problem. Now that I try the >> updated 1.1.10,1 I get as far as: > > It built correctly (haven't tested it yet) under: > 7.1-PRERELEASE #769 > FreeBSD 7.0-CURRENT #2: Wed Nov 19 06:02:02 EST 2008 Hi Robert, Built fine for me under 3 boxes with 7.1-PRERELEASE #769, too, and seems to work perfectly. I don't understand what is happening in current on my laptop. Thanks for the verification on 7.0. ed > > > Robert Huff > > From roberthuff at rcn.com Tue Dec 16 07:10:57 2008 From: roberthuff at rcn.com (Robert Huff) Date: Tue Dec 16 07:11:04 2008 Subject: Can't build Wine 1.1.10,1 port on up to date current. In-Reply-To: <20081216071554.19716ikpfazg3l8o@econet.encontacto.net> References: <20081216071554.19716ikpfazg3l8o@econet.encontacto.net> Message-ID: <18759.48677.138398.819711@jerusalem.litteratus.org> eculp writes: > I am running up to date current latest cvsup this morning. > # uname -a > FreeBSD ed.local.net.mx 8.0-CURRENT FreeBSD 8.0-CURRENT #107: Mon Dec > 15 07:08:45 CST 2008 > root@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO i386 > > After wine 1.1.4 I started to have some functionality problems > but it would still build with no problem. Now that I try the > updated 1.1.10,1 I get as far as: It built correctly (haven't tested it yet) under: FreeBSD 7.0-CURRENT #2: Wed Nov 19 06:02:02 EST 2008 Robert Huff From talon at lpthe.jussieu.fr Tue Dec 16 07:27:30 2008 From: talon at lpthe.jussieu.fr (Michel Talon) Date: Tue Dec 16 07:27:36 2008 Subject: print/cm-super size mismatch Message-ID: <20081216145757.GA15521@lpthe.jussieu.fr> Stephen Montgomery-Smith wrote: > I had this problem yesterday, when it was fixed last week. My guess is > that that the bug is not "still there" but that it was "renewed." I am > thinking that distfile was updated yet again. By the way, does someone knows why cm-super is listed as a dependency of print/teTeX while it is obviously *not* necessary to run teTeX and is a very big download? Notably since there exist other conversions of the Computer Modern fonts to Type1 requiring infinitely less space than cm-super, for example: http://www.ctan.org/tex-archive/fonts/ps-type1/cm-lgc/ -- Michel TALON From tijl at ulyssis.org Tue Dec 16 12:59:37 2008 From: tijl at ulyssis.org (Tijl Coosemans) Date: Tue Dec 16 12:59:44 2008 Subject: Can't build Wine 1.1.10,1 port on up to date current. In-Reply-To: <20081216071554.19716ikpfazg3l8o@econet.encontacto.net> References: <20081216071554.19716ikpfazg3l8o@econet.encontacto.net> Message-ID: <200812162129.50216.tijl@ulyssis.org> On Tuesday 16 December 2008 14:15:54 eculp wrote: > I am running up to date current latest cvsup this morning. > # uname -a > FreeBSD ed.local.net.mx 8.0-CURRENT FreeBSD 8.0-CURRENT #107: Mon Dec > 15 07:08:45 CST 2008 > root@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO i386 > > After wine 1.1.4 I started to have some functionality problems but it > would still build with no problem. Now that I try the updated > 1.1.10,1 I get as far as: > > ipstats.c: In function 'getNumArpEntries': > ipstats.c:1253: error: 'RTF_LLINFO' undeclared (first use in this function) > ipstats.c:1253: error: (Each undeclared identifier is reported only once > ipstats.c:1253: error: for each function it appears in.) > ipstats.c: In function 'getArpTable': > ipstats.c:1311: error: 'RTF_LLINFO' undeclared (first use in this function) > ipstats.c:1311: warning: initialization makes integer from pointer > without a cast > gmake[2]: *** [ipstats.o] Error 1 > gmake[2]: Leaving directory > `/usr/ports/emulators/wine/work/wine-1.1.10/dlls/iphlpapi' > gmake[1]: *** [iphlpapi] Error 2 > gmake[1]: Leaving directory `/usr/ports/emulators/wine/work/wine-1.1.10/dlls' > gmake: *** [dlls] Error 2 > *** Error code 2 > > Stop in /usr/ports/emulators/wine. > > ===>>> make failed for emulators/wine > ===>>> Aborting update > > Any suggestions would be greatly appreciated. It's because of this: http://lists.freebsd.org/pipermail/freebsd-current/2008-December/001264.html From lme at FreeBSD.org Tue Dec 16 13:56:20 2008 From: lme at FreeBSD.org (Lars Engels) Date: Tue Dec 16 13:56:26 2008 Subject: Where are the java/jdk16 files? In-Reply-To: <20081215160245.GA89670@misty.eyesbeyond.com> References: <20081214135726.GD22221@schweikhardt.net> <20081214163608.GG22221@schweikhardt.net> <20081215160245.GA89670@misty.eyesbeyond.com> Message-ID: <20081216215618.GO161@e.0x20.net> On Mon, Dec 15, 2008 at 08:02:45AM -0800, Greg Lewis wrote: > On Sun, Dec 14, 2008 at 05:36:08PM +0100, Jens Schweikhardt wrote: > > On Mon, Dec 15, 2008 at 01:38:31AM +1100, Some Dude wrote: > > # do a google search for the exact name of the first file, then click on > > # the cached page that'll show the sources and links > > > > Thanks, dude ;-) > > > > That was exactly what I a minuta after sending to the list. But still, > > it appears that someone messed up the download page with the wrong > > contents. It's all java binary packages when the page is supposed to > > contain src jars (as it is still the case for the google-cached page; > > man, I love the google cache!). I ended up on the very same page from > > other links saying "Source". My intention is to bring this to the port > > maintainer's attention (Cc'd). Maybe they know a contact at Sun to fix > > the page contents. > > Well, this is quite a pain for us. I imagine that Sun would actually like > us to switch to OpenJDK6 instead and won't want to put the source code back > up. Unfortunately thats not something we can do instantly. > > What is really needed is for someone to host the current source files. > The tricky part is you need some sort of click through agreement with > the JRL. I don't have enough bandwidth to host such a large download > unfortunately. Can't we do this on freebsdfoundation.org just like the diablo-jdk files? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081216/6e6a393c/attachment.pgp From beginners-bounces at haskell.org Tue Dec 16 14:30:03 2008 From: beginners-bounces at haskell.org (beginners-bounces@haskell.org) Date: Tue Dec 16 14:30:10 2008 Subject: Your message to Beginners awaits moderator approval Message-ID: Your mail to 'Beginners' with the subject error Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://www.haskell.org/mailman/confirm/beginners/98affdbc4f929d36bd16fbd767d49b27f27fc644 From daniel at roe.ch Tue Dec 16 15:38:08 2008 From: daniel at roe.ch (Daniel Roethlisberger) Date: Tue Dec 16 15:38:15 2008 Subject: rrdtool 1.3.3 and dejavu dependency In-Reply-To: <20081216112320.GB29493@megatron.madpilot.net> References: <20081215152824.GA18862@megatron.madpilot.net> <20081215173812.GA42598@hobbes.ustdmz.roe.ch> <20081216112320.GB29493@megatron.madpilot.net> Message-ID: <20081216233455.GC76371@hobbes.ustdmz.roe.ch> Guido Falsi 2008-12-16: > On Mon, Dec 15, 2008 at 06:38:12PM +0100, Daniel Roethlisberger wrote: > > > Even as the submitter of the PR in question, I fully agree. > > This is a good starting point :P > > > > I read the PR but don't really see such effects.. I'm using > > > mrtg and smokeping, with mrtg.cgi [1] and mailgraph.cgi. They > > > all work fine, mailgraph at least seems to use the > > > functionality described in the PR. > > > > > > Are we sure it isn't something else which is depending on > > > dejavu? > > > > Yes, pretty much. Note that rrdtool can fall back to other > > fonts, such as Bitstream Vera, but if no fonts are found, using > > `rrdtool graph` or language bindings such as RRDs::graph will > > fail. I just used Tobi's tutorial [2] to verify this again. > > > > Can you try to reproduce this with no fonts installed under > > /usr/local/lib/X11/fonts and using the tutorial [2] as a test? > > If it works for you, can you try to find out where it takes the > > font from? > > > > I guess it might be possible to make `rrdtool graph` work without > > the full install of x11-fonts/dejavu and all it's dependencies by > > either creating a lightweight dejavu font port without X11, or by > > adding dejavu to the rrdtool port somehow. > > > > I'm all open to better ideas than the current run-time dependency > > on x11-fonts/dejavu. I kind of hoped that the maintainer would > > be able to find a better solution, but unfortunately, there was > > no reaction from the maintainer. > > I made a few experiments on a spare PC at work(this is an AMD64 8.0 on > which I was testing ZFS, grat work to all the developers for that). > > I reverted your change on the machine, defined WITHOUT_X11 and made sure > all rrdtools dependencies where configured to require the least x11 > pieces(cairo requires disabling both xcb and glitz support). > > The machine had no ports installed. I ended up with the following ports > installed: > > bdftopcf-1.0.1 Convert X font from BDF to PCF > bitstream-vera-1.10_4 Bitstream Vera TrueType font collection > cairo-1.6.4_3,1 Vector graphics library with cross-device output > support > encodings-1.0.2,1 X.Org Encoding fonts > expat-2.0.1 XML 1.0 parser written in C > font-bh-ttf-1.0.0 X.Org Bigelow & Holmes TTF font > font-misc-ethiopic-1.0.0 X.Org miscellaneous Ethiopic font > font-misc-meltho-1.0.0_1 X.Org miscellaneous Meltho font > font-util-1.0.1 Create an index of X font files in a directory > fontcacheproto-0.1.2 Fontcache extension headers > fontconfig-2.5.0,1 An XML-based font configuration API for X Windows > fontsproto-2.0.2 Fonts extension headers > freetype2-2.3.7 A free and portable TrueType font rendering engine > gamin-0.1.9_2 A file and directory monitoring system > gettext-0.17_1 GNU gettext package > gio-fam-backend-2.16.5 FAM backend for GLib's GIO library > glib-2.16.5_1 Some useful routines of C programming (current > stable versi > gmake-3.81_3 GNU version of 'make' utility > icu-3.8.1_1 International Components for Unicode (from IBM) > libXfont-1.3.1_3,1 X font libary > libfontenc-1.0.4 The fontenc Library > libiconv-1.11_1 A character set conversion library > libtool-1.5.26 Generic shared library support script > libxml2-2.6.32_2 XML parser library for GNOME > mkfontdir-1.0.3_1 Create an index of X font files in a directory > mkfontscale-1.0.3 Creates an index of scalable font files for X > pango-1.20.5 An open-source framework for the layout and > rendering of i1 > pcre-7.8 Perl Compatible Regular Expressions library > perl-5.8.8_1 Practical Extraction and Report Language > pixman-0.10.0_2 Low-level pixel manipulation library > pkg-config-0.23_1 A utility to retrieve information about installed > libraries > png-1.2.33 Library for manipulating PNG images > python25-2.5.2_3 An interpreted object-oriented programming language > rrdtool-1.3.3_2 Round Robin Database Tools > xorg-fonts-truetype-7.3 X.Org TrueType fonts > xproto-7.0.10_1 X11 protocol headers > xtrans-1.0.4 Abstract network code for X > > As you can see it already sucked in various things and some fonts. I > tried the tutorial and it works flawlessly in such a setup. I think the > trick is this port: bitstream-vera-1.10_4. If there were some way to > install dejavu without sucking in all of libX11 it would be good too. > > could you make your tests without dejavu but with bitstream-vera and see > if it works? My tests show that it falls back to bitstream-vera, but I haven't tested it on a clean system. I think what we need is something along the lines of depending on (dejavu OR bitstream-vera). Or even any TTF font. There are other possibilities, like making graphing support optional in rrdtool, or replacing the dependency with a pkg-message, asking the user to install some font if graphing is to be used. > I see pango is depending on x11-fonts/xorg-fonts-truetype, which depends > on some fonts pacjkages but not on libX11. > > Hope my feedback helps. Due to ENOTIME, I wont be able to devote any meaningful amount of time to this any time soon. Can you submit the information in this thread as a PR against rrdtool so it doesn't get lost? -- Daniel Roethlisberger http://daniel.roe.ch/ From contactway2 at gmail.com Tue Dec 16 16:08:48 2008 From: contactway2 at gmail.com (J.W) Date: Tue Dec 16 16:08:54 2008 Subject: List of available ports in CDs Message-ID: <000901c95fd8$c4a1c300$4de54900$@com> Dear Supporter Please tell me how can I get a list of existent ports in the FreeBSD CDs which are available as ISO 1, 2 and 3 files at the ftp sites. It's required to find out which ports are on the ISO files and which are necessary to download directly from the site. Thank You From eculp at encontacto.net Tue Dec 16 20:00:19 2008 From: eculp at encontacto.net (eculp) Date: Tue Dec 16 20:00:26 2008 Subject: Can't build Wine 1.1.10,1 port on up to date current. In-Reply-To: <200812162129.50216.tijl@ulyssis.org> References: <20081216071554.19716ikpfazg3l8o@econet.encontacto.net> <200812162129.50216.tijl@ulyssis.org> Message-ID: <20081216220011.10706ozrfek9yrk0@econet.encontacto.net> Quoting Tijl Coosemans : > On Tuesday 16 December 2008 14:15:54 eculp wrote: >> I am running up to date current latest cvsup this morning. >> # uname -a >> FreeBSD ed.local.net.mx 8.0-CURRENT FreeBSD 8.0-CURRENT #107: Mon Dec >> 15 07:08:45 CST 2008 >> root@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO i386 >> >> After wine 1.1.4 I started to have some functionality problems but it >> would still build with no problem. Now that I try the updated >> 1.1.10,1 I get as far as: >> >> ipstats.c: In function 'getNumArpEntries': >> ipstats.c:1253: error: 'RTF_LLINFO' undeclared (first use in this function) >> ipstats.c:1253: error: (Each undeclared identifier is reported only once >> ipstats.c:1253: error: for each function it appears in.) >> ipstats.c: In function 'getArpTable': >> ipstats.c:1311: error: 'RTF_LLINFO' undeclared (first use in this function) >> ipstats.c:1311: warning: initialization makes integer from pointer >> without a cast >> gmake[2]: *** [ipstats.o] Error 1 >> gmake[2]: Leaving directory >> `/usr/ports/emulators/wine/work/wine-1.1.10/dlls/iphlpapi' >> gmake[1]: *** [iphlpapi] Error 2 >> gmake[1]: Leaving directory >> `/usr/ports/emulators/wine/work/wine-1.1.10/dlls' >> gmake: *** [dlls] Error 2 >> *** Error code 2 >> >> Stop in /usr/ports/emulators/wine. >> >> ===>>> make failed for emulators/wine >> ===>>> Aborting update >> >> Any suggestions would be greatly appreciated. > > It's because of this: > http://lists.freebsd.org/pipermail/freebsd-current/2008-December/001264.html > Thanks, Tijl. That would also be why I able to copy a package from one of my FreeBSD 7.1-PRERELEASE machines, install it and it seems to work fine on current. Everything I've tested does anyway. So this is my current work around. Thanks again, ed From mad at madpilot.net Wed Dec 17 00:43:18 2008 From: mad at madpilot.net (Guido Falsi) Date: Wed Dec 17 00:43:25 2008 Subject: rrdtool 1.3.3 and dejavu dependency In-Reply-To: <20081216233455.GC76371@hobbes.ustdmz.roe.ch> References: <20081215152824.GA18862@megatron.madpilot.net> <20081215173812.GA42598@hobbes.ustdmz.roe.ch> <20081216112320.GB29493@megatron.madpilot.net> <20081216233455.GC76371@hobbes.ustdmz.roe.ch> Message-ID: <20081217084315.GA42762@megatron.madpilot.net> On Wed, Dec 17, 2008 at 12:34:55AM +0100, Daniel Roethlisberger wrote: > > My tests show that it falls back to bitstream-vera, but I haven't > tested it on a clean system. It does on a clean system, but perhaps letting users know or giving options would be much better. > > I think what we need is something along the lines of depending on > (dejavu OR bitstream-vera). Or even any TTF font. There are > other possibilities, like making graphing support optional in > rrdtool, or replacing the dependency with a pkg-message, asking > the user to install some font if graphing is to be used. I think some options in the port, like "depend on xorg-fonts-truetype" and "depend on dejavu (requires X11)" could be some good starting point. The user would have control on what to install. > > I see pango is depending on x11-fonts/xorg-fonts-truetype, which depends > > on some fonts pacjkages but not on libX11. > > > > Hope my feedback helps. > > Due to ENOTIME, I wont be able to devote any meaningful amount of > time to this any time soon. Can you submit the information in > this thread as a PR against rrdtool so it doesn't get lost? I understand... I'll be too busy during christmas, but I'll have a look at it and try to send some patch for the port. -- Guido Falsi From andrew.w.nosenko at gmail.com Wed Dec 17 01:12:27 2008 From: andrew.w.nosenko at gmail.com (Andrew W. Nosenko) Date: Wed Dec 17 01:12:34 2008 Subject: Valgrind and FreeBSD-7.0 Message-ID: <6161f3180812170112g561967d3vb861f6d87a2ee159@mail.gmail.com> Whether someone working for make valgrind work under FreeBSD-7.0? At the meantime it is compiliable but absolutelly unusable :-( Thanks in advance for your time and responses. -- Andrew W. Nosenko From jbaggen at ip2.nl Wed Dec 17 07:05:48 2008 From: jbaggen at ip2.nl (IP2 Internet (Jan Baggen)) Date: Wed Dec 17 07:05:55 2008 Subject: FreeBSD Port: amanda-client-2.5.1p3_3,1 Message-ID: <3966AD734485204CB664C31647FB73D43E8143@SRV01.ip2.local> Most recent stable release is version 2.6.0p2. When will the FreeBSD port be updated to version 2.6.0p2 ? 2.6.0p2 was released on August 28, 2008. Met vriendelijke groet, Jan Baggen IP2 Internet B.V. Damrak 37-38 1012 LK Amsterdam T: +31.205186040 F: +31.205186041 www.ip2.nl From skreuzer at exit2shell.com Wed Dec 17 07:31:20 2008 From: skreuzer at exit2shell.com (Steven Kreuzer) Date: Wed Dec 17 07:31:33 2008 Subject: RT 3.8? In-Reply-To: <4946B0C0.90106@freebsd.org> References: <20081215191535.GC33004@atarininja.org> <4946B0C0.90106@freebsd.org> Message-ID: On Dec 15, 2008, at 2:32 PM, Philip M. Gollucci wrote: > Wesley Shields wrote: >> I've also added him as CC to this reply so he can speak up if he >> has any >> more information to add. > I've gotten several comments (esp recently). My first thought is to > commit it as is and let the PRs come it. Several people have been > using the prototype in production for a while now. I have been running this port in both production with roughly 15 people using it. (This number of users should grown to around 40 in the near future). The production version has been extremely reliable and I would say that it ready to be added into the ports tree. I am willing to assist with any PRs that open up regarding this port. If you would like, put me down as the maintainer until your workload dies down and then you can take maintainership back from me. -- Steven Kreuzer http://www.exit2shell.com/~skreuzer From craig at animalhead.com Wed Dec 17 10:38:33 2008 From: craig at animalhead.com (craig@animalhead.com) Date: Wed Dec 17 10:38:40 2008 Subject: FreeBSD Port: x86info-1.21_1 Message-ID: Tried to install x86info from the /ports directory on my Verio freeBSD 6.3 web site. Lots of compiling and things happened, but the process ended with an error as shown below. Why should a utility to show info about the cpu need a print spooler? Any advice you could offer, as to a workaround, would be much appreciated. cmac www.animalhead.com ----------------------------------------------------------------------------------- LPRng - Print Spooler (http://www.lprng.com) ********************************************************************** ===> Installing rc.d startup script(s) ===> Compressing manual pages for LPRng-3.8.32_1 ===> Running ldconfig /sbin/ldconfig -m /usr/local/lib ===> Registering installation for LPRng-3.8.32_1 ===> SECURITY REPORT: This port has installed the following files which may act as network servers and may therefore pose a remote security risk to the system. /usr/local/sbin/lpd This port has installed the following startup scripts which may cause these network services to be started at boot time. /usr/local/etc/rc.d/lprng If there are vulnerabilities in these programs there may be a security risk to the system. FreeBSD makes no guarantee about the security of ports included in the Ports Collection. Please type 'make deinstall' to deinstall the port if this is a concern. For more information, and contact details about the security status of this software, see the following webpage: http://www.lprng.com/ ===> LPRngTool ===> LPRngTool-1.3.2_1 depends on executable: a2ps - not found ===> Verifying install for a2ps in /usr/ports/print/a2ps-letter ===> Building for a2ps-letter-4.13b_4 make all-recursive 1.4: not found 1.5: not found 1.6: not found 1.3+: not found 1.4+: not found 1.5+: not found 1.6+: not found 1.1+: not found 1.2+: not found bsdjava: not found sun: not found blackdown: not found linux: not found *** Error code 127 Stop in /var/build/ports/print/a2ps-letter/work/a2ps-4.13. *** Error code 1 Stop in /var/build/ports/print/a2ps-letter/work/a2ps-4.13. *** Error code 1 Stop in /ports/print/a2ps-letter. *** Error code 1 Stop in /ports/sysutils/LPRngTool. *** Error code 1 Stop in /ports/sysutils. From stas at FreeBSD.org Wed Dec 17 10:45:03 2008 From: stas at FreeBSD.org (Stanislav Sedov) Date: Wed Dec 17 10:45:10 2008 Subject: FreeBSD Port: x86info-1.21_1 In-Reply-To: References: Message-ID: <20081217214653.697682b2.stas@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 17 Dec 2008 10:13:11 -0800 craig@animalhead.com mentioned: > > Stop in /ports/sysutils/LPRngTool. > *** Error code 1 > > Stop in /ports/sysutils I'm not sure what you're doing, but it seems that you ran make from sysutils and not from sysutils/x86info. - -- Stanislav Sedov ST4096-RIPE -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAklJSSEACgkQK/VZk+smlYFa7wCeNaiy3pxncWoM0qfadKnj4ty4 V5MAnRnvOmugZdLjvjbUmqeci1rRGopZ =1jeD -----END PGP SIGNATURE----- From amdmi3 at amdmi3.ru Wed Dec 17 10:48:26 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Wed Dec 17 10:48:33 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <7d6fde3d0812131133g3956eea7n6830eefde3532a4f@mail.gmail.com> References: <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> <20081212102905.GC7422@hades.panopticon> <7d6fde3d0812131133g3956eea7n6830eefde3532a4f@mail.gmail.com> Message-ID: <20081217184756.GA92643@hades.panopticon> * Garrett Cooper (yanefbsd@gmail.com) wrote: > > It's useful for me too sometimes, but it's already not 100% reliable, > > as some ports still generate it dynamically, some use PLIST_FILES, some > > use PLIST_SUB so it's not apparent under which path and/or name the file > > mentioned in plist is actually installed. > Getting rid of the plist files will force a major rewrite of > pkg_install. Are you really comfortable doing that :\? Not getting rid but generating automatically. Many ports already have no pkg-plist. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From mezz7 at cox.net Wed Dec 17 15:01:22 2008 From: mezz7 at cox.net (Jeremy Messenger) Date: Wed Dec 17 15:01:29 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: <20081217184756.GA92643@hades.panopticon> References: <20081209222042.GC29817@hades.panopticon> <8763lsi10m.fsf@chateau.d.lf> <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> <20081212102905.GC7422@hades.panopticon> <7d6fde3d0812131133g3956eea7n6830eefde3532a4f@mail.gmail.com> <20081217184756.GA92643@hades.panopticon> Message-ID: On Wed, 17 Dec 2008 12:47:56 -0600, Dmitry Marakasov wrote: > * Garrett Cooper (yanefbsd@gmail.com) wrote: > >> > It's useful for me too sometimes, but it's already not 100% reliable, >> > as some ports still generate it dynamically, some use PLIST_FILES, >> some >> > use PLIST_SUB so it's not apparent under which path and/or name the >> file >> > mentioned in plist is actually installed. >> Getting rid of the plist files will force a major rewrite of >> pkg_install. Are you really comfortable doing that :\? > > Not getting rid but generating automatically. Many ports already > have no pkg-plist. I mean by keep static pkg-plist (not get rid of it). I don't like dynamic plist. I do not need to list my reasons as it's already in the archives by someone and maybe me (not remember). Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From erwin at FreeBSD.org Wed Dec 17 17:12:11 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Wed Dec 17 17:12:17 2008 Subject: INDEX build failed for 6.x Message-ID: <200812180112.mBI1C96J071129@pointyhat.freebsd.org> INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: handbrake-0.9.3: no entry for :/a/erwin/tindex/ports/devel/automake19 Committers on the hook: ahze beech Most recent CVS update was: U multimedia/handbrake/Makefile U multimedia/handbrake/distinfo U multimedia/handbrake/pkg-descr U multimedia/handbrake/files/patch-contrib-Jamfile U multimedia/handbrake/files/patch-contrib-libavformat-udp.c U multimedia/handbrake/files/patch-libhb-fifo.c U sysutils/serpentine/Makefile U www/cherokee/Makefile U www/cherokee/distinfo From QAT at FreeBSD.org Wed Dec 17 19:21:49 2008 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Wed Dec 17 19:22:00 2008 Subject: cvs commit: ports/audio/emms Makefile ports/chinese/fcitx Makefile ports/databases/py-sqlalchemy Makefile ports/databases/py-sqlobject Makefile ports/deskutils/planner.el Makefile ports/devel/cedet Makefile ports/devel/ecb Makef In-Reply-To: <200812180224.mBI2O4xN011835@repoman.freebsd.org> References: In-Reply-To: <200812180224.mBI2O4xN011835@repoman.freebsd.org> Message-ID: <20081218032154.21C9512E4255@quark.ds9.tecnik93.com> Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/py25-PasteScript-1.6.2_1.log : building py25-PasteScript-1.6.2_1 in directory /var/tinderbox/7-STABLE-FTP maintained by: ports@FreeBSD.org building for: 7.1-PRERELEASE amd64 port directory: /usr/ports/www/py-pastescript Makefile ident: $FreeBSD: ports/www/py-pastescript/Makefile,v 1.14 2008/12/18 02:24:03 linimon Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Thu Dec 18 03:21:16 UTC 2008 ................................................... byte-compiling build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/paste/debug/testserver.py to testserver.pyc byte-compiling build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/paste/debug/debugapp.py to debugapp.pyc byte-compiling build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/paste/debug/prints.py to prints.pyc byte-compiling build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/paste/debug/fsdiff.py to fsdiff.pyc byte-compiling build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/paste/debug/profile.py to profile.pyc byte-compiling build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/paste/debug/wdg_validate.py to wdg_validate.pyc byte-compiling build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/paste/debug/__init__.py to __init__.pyc byte-compiling build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/paste/debug/watchthreads.py to watchthreads.pyc byte-compiling build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/paste/debug/doctest_webapp.py to doctest_webapp.pyc creating build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/EGG-INFO copying Paste.egg-info/PKG-INFO -> build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/EGG-INFO copying Paste.egg-info/SOURCES.txt -> build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/EGG-INFO copying Paste.egg-info/dependency_links.txt -> build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/EGG-INFO copying Paste.egg-info/entry_points.txt -> build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/EGG-INFO copying Paste.egg-info/namespace_packages.txt -> build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/EGG-INFO copying Paste.egg-info/not-zip-safe -> build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/EGG-INFO copying Paste.egg-info/requires.txt -> build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/EGG-INFO copying Paste.egg-info/top_level.txt -> build/bdist.freebsd-7.1-PRERELEASE-amd64/egg/EGG-INFO creating dist creating 'dist/Paste-1.7.2-py2.5.egg' and adding 'build/bdist.freebsd-7.1-PRERELEASE-amd64/egg' to it removing 'build/bdist.freebsd-7.1-PRERELEASE-amd64/egg' (and everything under it) ===> Installing for py25-Paste-1.7.2 ===> py25-Paste-1.7.2 depends on file: /usr/local/bin/easy_install-2.5 - found ===> py25-Paste-1.7.2 depends on file: /usr/local/bin/python2.5 - found ===> Generating temporary packing list ===> Checking if www/py-paste already installed ===> py25-Paste-1.7.2 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of www/py-paste without deleting it first, set the variable "FORCE_PKG_REGISTER" in your environment or the "make install" command line. *** Error code 1 Stop in /a/ports/www/py-paste. *** Error code 1 Stop in /a/ports/www/py-pastescript. ================================================================ build of /usr/ports/www/py-pastescript ended at Thu Dec 18 03:21:52 UTC 2008 A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From erwin at FreeBSD.org Wed Dec 17 20:12:19 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Wed Dec 17 20:12:29 2008 Subject: INDEX now builds successfully on 6.x Message-ID: <200812180412.mBI4CIsH030019@pointyhat.freebsd.org> From amdmi3 at amdmi3.ru Thu Dec 18 05:15:19 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Thu Dec 18 05:15:26 2008 Subject: [PROPOSAL] Ports using SCM repositories as source instead of distfiles In-Reply-To: References: <20081210181125.GA86341@hades.panopticon> <87zlj3heor.fsf@chateau.d.lf> <20081210223522.GA6367@hades.panopticon> <87vdtrhb6r.fsf@chateau.d.lf> <20081211082325.GA6167@hades.panopticon> <20081212102905.GC7422@hades.panopticon> <7d6fde3d0812131133g3956eea7n6830eefde3532a4f@mail.gmail.com> <20081217184756.GA92643@hades.panopticon> Message-ID: <20081218131450.GA89064@hades.panopticon> * Jeremy Messenger (mezz7@cox.net) wrote: > I mean by keep static pkg-plist (not get rid of it). I don't like dynamic > plist. I do not need to list my reasons as it's already in the archives by > someone and maybe me (not remember). I understand your point, but it's only theoretical research for now. If we manage to get soemthing useful it may be used optionally, may be used only for generating static plists etc. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From cokane at FreeBSD.org Thu Dec 18 06:58:53 2008 From: cokane at FreeBSD.org (Coleman Kane) Date: Thu Dec 18 06:59:00 2008 Subject: APNG patch for graphics/png port In-Reply-To: References: <1229278954.1718.10.camel@localhost> <1229380736.6657.3.camel@localhost> Message-ID: <1229612314.3893.14.camel@localhost> On Mon, 2008-12-15 at 23:02 -0600, Jeremy Messenger wrote: > On Mon, 15 Dec 2008 16:38:56 -0600, Coleman Kane > wrote: > > > On Sun, 2008-12-14 at 22:54 -0600, Jeremy Messenger wrote: > >> On Sun, 14 Dec 2008 12:22:34 -0600, Coleman Kane > >> wrote: > >> > >> > Hello, > >> > > >> > I recently played with building Thunderbird 3.0b1 from source (it > >> works > >> > pretty well, btw). I was playing with some of the options to enable > >> > using the system versions of a number of libraries, rather than > >> relying > >> > upon statically linking them into the project. > >> > >> We should keep compile static link, because PNG folks disapprove > >> Mozilla's > >> APNG patch. It's what we did with Firefox 3. > >> > >> Cheers, > >> Mezz > >> > > > > Any idea why the mozilla folk jumped on further developing APNG, rather > > than just using (much more mature) MNG for the same purpose? > > I have no idea. The google has found useful links and I think two URLs > might help you. I didn't read there as I have no interest with and don't > care about APNG vs MNG. > > http://mozilla.wikia.com/wiki/APNG_vs_MNG > http://en.wikipedia.org/wiki/APNG#History > > Cheers, > Mezz > Short version: whatwg.org and Mozilla people seemed to think that an "Animated PNG" specification would work best (quickest adoption) if they piggy-backed it on top of the already supported PNG file format. Due to the political implications of such things, the hill was much steeper to climb to get everyone to agree to use MNG than it was to get them to use APNG, even though the latter is basically a reimplementation of the former (actually MNG is a superset of APNG functionality). One key component was that a non-APNG viewer will still view the first image in an APNG, while an MNG file would come up with a "broken image" placeholder. Another key component was that IE would be more likely to adopt it (we remember how long it took them to adopt PNG, right?) if it was based on PNG rather than MNG. The PNG maintainers, coming at it from a pure maintainability standpoint stood their ground and said that they didn't want to absorb the burden of maintaining an "Animated" feature within libpng, they would rather that be handled by the separate libmng. So now we basically have an unofficial fork of libpng that I'd call "mozilla-libpng", which implements the desired features from WHATWG, but makes a very liberal interpretation of the PNG specification. Oh yeah, and it also is based upon a Specification started by an SoC'er, and a patchset which is no longer maintained by him, and instead is maintained by mozilla.org at their discretion (read: whenever they update their png dependency). Again it is unofficial, and Mozilla.org's specification is unfinished as of now. And, from the bug report linked in one of the articles above, it doesn't seem like the two camps are getting along very well. PNG maintainers won't accept APNG, and WHATWG and Mozilla.org won't replace it with MNG. Especially now that APNG is pretty much out of the bag, my opinion is that the libpng people should either adopt APNG into their tree, or yield control over PNG to Mozilla.org. It's not about being the "right" thing to do, it is about avoiding a highly user-confusing feature-based fork of a file format. Okay. So that was actually still kinda long. -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081218/e86da82d/attachment.pgp From Kristjan.Sander at rmk.ee Thu Dec 18 07:18:04 2008 From: Kristjan.Sander at rmk.ee (Kristjan Sander) Date: Thu Dec 18 07:18:11 2008 Subject: Zope 2.10, MySQL and Python 2.5 Message-ID: Dear All, I am having trouble with using Zope 2.10 together with MySQL. I have _mysql Python support library for Python 2.5 from some previous port but Zope came with Python 2.4 and I do not have _mysql support for that. I guess that there will not be a Zope 2.10 port with Python 2.5 support in the near future because Zope 2.10 does not support Python 2.5 as they say at http://www.zope.org/Products/Zope/2.10.7/Zope-2.10.7-released . I tried to change Python used by Zope in Zope conf to Python 2.5 but it resulted in dramatic traceback. Has anybody solved this problem? Thanks in advance, Kristjan Sander From gesbbb at yahoo.com Thu Dec 18 07:29:22 2008 From: gesbbb at yahoo.com (Jerry) Date: Thu Dec 18 07:29:29 2008 Subject: Unable to build x11vnc Message-ID: <20081218100229.1e0f93ba@scorpio> FreeBSD 6.3-RELEASE-p6 #0: Thu Dec 11 22:02:51 I am unable to build the net/x11vnc port. Actually, I am unable to update the port. I do have an older version installed. The build terminates with this message: /usr/local/lib/libavahi-common.so: undefined reference to `libintl_bindtextdomain' /usr/local/lib/libavahi-common.so: undefined reference to `libintl_dgettext' /usr/local/lib/libavahi-common.so: undefined reference to `libintl_bind_textdomain_codeset' *** Error code 1 Stop in /usr/ports/net/x11vnc/work/x11vnc-0.9.5/x11vnc. *** Error code 1 Stop in /usr/ports/net/x11vnc/work/x11vnc-0.9.5/x11vnc. *** Error code 1 Stop in /usr/ports/net/x11vnc/work/x11vnc-0.9.5. *** Error code 1 Stop in /usr/ports/net/x11vnc/work/x11vnc-0.9.5. *** Error code 1 Stop in /usr/ports/net/x11vnc. The entire build log is available here: http://seibercom.net/logs/x11vnc.txt Hopefully, someone might be able to assist me. I have tried build the port manually, as well as using 'portmanager' and 'portupgrade' to handle the task. All failed. -- Jerry gesbbb@yahoo.com Try to divide your time evenly to keep others happy. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081218/cb0ed194/signature.pgp From ottk at zzz.ee Thu Dec 18 07:37:04 2008 From: ottk at zzz.ee (Ott =?iso-8859-1?q?K=F6stner?=) Date: Thu Dec 18 07:37:11 2008 Subject: When can we expect BIND 9.4.3 FreeBSD port... Message-ID: <200812181721.03304.ottk@zzz.ee> Greetings list, Does anybody have an idea, when can we expect BIND 9.4.3 FreeBSD port? Current version is BIND 9.4.2-P2, and as JINMEI, Tatuya from Internet Systems Consortium, Inc. wrote yesterday in 'freebsd-net' list, "Even with all attempts to mitigate the trouble and with tweaking parameters, 9.4.2-P2 still has a fundamental limitation on performance." So, BIND 9.4.3 is probably a great need by BSD community... Best regards, O.K. -- M??da oma inteneti kiirust / Test Your Internet speed http://tallinn.speedtest.net/ From jhein at timing.com Thu Dec 18 10:32:34 2008 From: jhein at timing.com (John Hein) Date: Thu Dec 18 10:32:42 2008 Subject: [patch] support systems that have been built WITHOUT_INFO=yes (no makeinfo & install-info) Message-ID: <200812181814.mBIIEhYK093725@gromit.timing.com> >Submitter-Id: current-users >Originator: John Hein >Organization: >Confidential: no >Synopsis: [patch] support systems that have been built WITHOUT_INFO=yes (no makeinfo & install-info) >Severity: non-critical >Priority: medium >Category: ports >Class: change-request >Release: FreeBSD 7.1-PRERELEASE i386 >Environment: >Description: If world is built with WITHOUT_INFO=yes, then as of 7.x, it does not install install-info and makeinfo, etc. (see the exclusion of the texinfo subdir in gnu/usr.bin/Makefile). But lots of ports and bsd.port.mk expect these tools to be there unconditionally. Worlds without these tools (think building for embedded boxes with nanobsd, for example) break when building these ports. The port I hit first that has this problem is libtool15 which has this... CONFIGURE_ENV= MAKEINFO="makeinfo --no-split" See also at least these PRs for more: ports/121296, ports/121717 >How-To-Repeat: make buildworld WITHOUT_INFO=yes make installworld WITHOUT_INFO=yes (or just manually move away /usr/bin/makeinfo and /usr/bin/install-info) Then cd ports/devel/libtool15 make && make install >Fix: Support WITHOUT_INFO (or detect missing install-info) in ports/Mk. See patch below. Ports can be fixed by keying on HAS_INFO (the preferred method, I think) or changing hard-coded invocations of makeinfo and/or install-info to the MAKEINFO and INSTALLINFO commands as defined below in bsd.commands.mk. Once this fix (or similar) is in place, we can generate a patch for all the ports that have hard-coded references to the *info utilities. Index: bsd.commands.mk =================================================================== RCS file: /base/FreeBSD-CVS/ports/Mk/bsd.commands.mk,v retrieving revision 1.3 diff -u -p -r1.3 bsd.commands.mk --- bsd.commands.mk 14 Apr 2008 16:46:41 -0000 1.3 +++ bsd.commands.mk 18 Dec 2008 17:58:12 -0000 @@ -92,6 +92,18 @@ XARGS?= /usr/bin/xargs XMKMF?= ${LOCALBASE}/bin/xmkmf -a YACC?= /usr/bin/yacc +.if exists(/usr/bin/install-info) && !defined(WITHOUT_INFO) +HAS_INFO= yes +INSTALLINFO?= /usr/bin/install-info +MAKEINFO?= /usr/bin/makeinfo +.else +# Ideally, ports should key on HAS_INFO. In some cases, it +# may make more sense to just have a port use ${MAKEINFO} and +# ${INSTALLINFO} which are defined to a no-op here. +INSTALLINFO?= true +MAKEINFO?= true +.endif + .if exists(/sbin/md5) MD5?= /sbin/md5 .else Index: bsd.port.mk =================================================================== RCS file: /base/FreeBSD-CVS/ports/Mk/bsd.port.mk,v retrieving revision 1.604 diff -u -p -r1.604 bsd.port.mk --- bsd.port.mk 5 Sep 2008 19:41:43 -0000 1.604 +++ bsd.port.mk 18 Dec 2008 17:58:05 -0000 @@ -5672,13 +5672,16 @@ add-plist-data: .if !target(add-plist-info) add-plist-info: # Process GNU INFO files at package install/deinstall time -.if defined(INFO) +.if defined(INFO) && defined(HAS_INFO) .for i in ${INFO} - install-info --quiet ${PREFIX}/${INFO_PATH}/$i.info ${PREFIX}/${INFO_PATH}/dir - @${ECHO_CMD} "@unexec install-info --quiet --delete %D/${INFO_PATH}/$i.info %D/${INFO_PATH}/dir" \ + -ls -alF ${PREFIX}/${INFO_PATH}/$i.info ${PREFIX}/${INFO_PATH}/dir + -cat ${PREFIX}/${INFO_PATH}/dir + ${INSTALLINFO} --quiet ${PREFIX}/${INFO_PATH}/$i.info ${PREFIX}/${INFO_PATH}/dir || \ + { echo "*** ignoring failed ${INSTALLINFO} for possible duplicate entry ***" >&2; true; } + @${ECHO_CMD} "@unexec ${INSTALLINFO} --quiet --delete %D/${INFO_PATH}/$i.info %D/${INFO_PATH}/dir" \ >> ${TMPPLIST} @${LS} ${PREFIX}/${INFO_PATH}/$i.info* | ${SED} -e s:${PREFIX}/::g >> ${TMPPLIST} - @${ECHO_CMD} "@exec install-info --quiet %D/${INFO_PATH}/$i.info %D/${INFO_PATH}/dir" \ + @${ECHO_CMD} "@exec ${INSTALLINFO} --quiet %D/${INFO_PATH}/$i.info %D/${INFO_PATH}/dir" \ >> ${TMPPLIST} .endfor .if defined(INFO_SUBDIR) From Lokadamus at gmx.de Thu Dec 18 18:14:04 2008 From: Lokadamus at gmx.de (Lokadamus) Date: Thu Dec 18 18:14:11 2008 Subject: FreeBSD Port: MailScanner-4.67.6_3 Message-ID: <494AFD33.707@gmx.de> Whats about security news from Secunia? http://secunia.com/Advisories/33117/ MailScanner Multiple Insecure Temporary Files Will Mailscanner be updatet? Kind Regards From uwe at laverenz.de Fri Dec 19 02:44:30 2008 From: uwe at laverenz.de (Uwe Laverenz) Date: Fri Dec 19 02:44:39 2008 Subject: Zope 2.10, MySQL and Python 2.5 In-Reply-To: References: Message-ID: <20081219103158.GB15916@laverenz.de> On Thu, Dec 18, 2008 at 04:48:22PM +0200, Kristjan Sander wrote: > Zope came with Python 2.4 and I do not have _mysql support for that. I > guess that there will not be a Zope 2.10 port with Python 2.5 support in > the near future because Zope 2.10 does not support Python 2.5 as they > say at http://www.zope.org/Products/Zope/2.10.7/Zope-2.10.7-released . I > tried to change Python used by Zope in Zope conf to Python 2.5 but it > resulted in dramatic traceback. > > Has anybody solved this problem? Yes, I run Zope+Plone in a dedicated jail and set the jail's python version to 2.4 via /etc/make.conf: PYTHON_DEFAULT_VERSION=python2.4 Uwe From Kristjan.Sander at rmk.ee Fri Dec 19 04:22:30 2008 From: Kristjan.Sander at rmk.ee (Kristjan Sander) Date: Fri Dec 19 04:22:37 2008 Subject: Zope FreeBSD port for Python 2.5 Message-ID: Dear Sir or Madam Could you please provide information about possible Zope 2.10 port supporting Python 2.5? I have a FreeBSD installation with Python 2.5 and Zope 2.10 using Python 2.4 and that creates problems because Python _mysql library is installed for Python 2.5 and does not work with Python 2.4. I would rather not compile and install mysql support for Python 2.4 by hand. Yours faithfully, Kristjan Sander From fmysh at iijmio-mail.jp Fri Dec 19 05:43:49 2008 From: fmysh at iijmio-mail.jp (TAOKA Fumiyoshi) Date: Fri Dec 19 05:43:56 2008 Subject: Zope FreeBSD port for Python 2.5 In-Reply-To: References: Message-ID: On 2008/12/19, at 20:53, Kristjan Sander wrote: > Dear Sir or Madam > > Could you please provide information about possible Zope 2.10 port > supporting Python 2.5? I have a FreeBSD installation with Python 2.5 > and Zope 2.10 using Python 2.4 and that creates problems because > Python _mysql library is installed for Python 2.5 and does not work > with Python 2.4. I would rather not compile and install mysql > support for Python 2.4 by hand. > > Yours faithfully, > > Kristjan Sander Hi Kristjan Zope 2.x does not support Python 2.5 at upsteam. Quoted from http://www.zope.org/Products/Zope/2.10.7/Zope-2.10.7-released Supported Python versions: Zope 2.10 requires Python 2.4.5 or higher (Python 2.4.4 is still acceptable). Older Python versions are no longer supported. Python 2.5 is not supported at this time. You can set PYTHON_VERSION to install a port specifying a Python version. See /usr/ports/Mk/bsd.python.mk. # cd /usr/ports/databases/py-MySQLdb # env PYTHON_VERSION=python2.4 make install Fortunately MySQL-python port seems not to conflict for multiple python versions. -- TAOKA Fumiyoshi From mad at madpilot.net Fri Dec 19 06:56:18 2008 From: mad at madpilot.net (Guido Falsi) Date: Fri Dec 19 06:56:25 2008 Subject: rrdtool 1.3.3 and dejavu dependency In-Reply-To: <20081216233455.GC76371@hobbes.ustdmz.roe.ch> References: <20081215152824.GA18862@megatron.madpilot.net> <20081215173812.GA42598@hobbes.ustdmz.roe.ch> <20081216112320.GB29493@megatron.madpilot.net> <20081216233455.GC76371@hobbes.ustdmz.roe.ch> Message-ID: <494BB60B.9040901@madpilot.net> Daniel Roethlisberger wrote: > > Due to ENOTIME, I wont be able to devote any meaningful amount of > time to this any time soon. Can you submit the information in > this thread as a PR against rrdtool so it doesn't get lost? > As suggested I did send a PR. I post it here so someone can look at it and see if it's worth improving and committing: http://www.freebsd.org/cgi/query-pr.cgi?pr=129716 Thank you! -- Guido Falsi From ben at altesco.nl Fri Dec 19 09:28:20 2008 From: ben at altesco.nl (Ben Stuyts) Date: Fri Dec 19 09:28:27 2008 Subject: php imap_rfc822_parse_adrlist problem Message-ID: Hi, Since upgrading to php 5.2.8 I have a problem with imap_rfc822_parse_adrlist. When I run the example given on the manual page at http://nl3.php.net/imap_rfc822_parse_adrlist: $adds = 'ian eiloart , shuf6@example.ac.uk, blobby, "ian,eiloart", <@example.com:foo@example.ac.uk>, foo@#, ian@-example.com, ian@one@two'; $add_arr = imap_rfc822_parse_adrlist($adds, 'example.com'); var_export ($add_arr); I should get: ... 2 => class stdClass { var $mailbox = 'blobby'; var $host = 'example.ac.uk'; }, ... but I get: ... 2 => stdClass::__set_state(array( 'mailbox' => 'blobby', 'host' => 'p?a(', )), ... So the host part isn't filled in correctly. I have verified this on two FreeBSD 7 machines. On an older FreeBSD 5 machine with php4 this works fine. Before the update, I was running php 5.2.6 and there was no problem either. Any ideas? Thanks, Ben From g.martinez at pcbsd.es Fri Dec 19 15:51:42 2008 From: g.martinez at pcbsd.es (Gonzalo =?iso-8859-1?q?Mart=EDnez-Sanjuan?= =?iso-8859-1?q?_S=E1nchez?=) Date: Fri Dec 19 15:51:49 2008 Subject: linux-ePSXe Message-ID: <200812200035.34547.g.martinez@pcbsd.es> Hello! Would someone take care of the port emulators/linux-ePSXe? Theres a new version since 8 months in their website: 1.7.0 http://www.epsxe.com/ Thnx everybody for their work in freebsd ports tree. -- Un saludo Gonzalo Mart?nez - Sanjuan S?nchez PC-BSD Software ---------------------------- http://www.pcbsd.org http://www.pbidir.es From yanefbsd at gmail.com Fri Dec 19 19:53:01 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 19 19:53:08 2008 Subject: [patch] support systems that have been built WITHOUT_INFO=yes (no makeinfo & install-info) In-Reply-To: <200812181814.mBIIEhYK093725@gromit.timing.com> References: <200812181814.mBIIEhYK093725@gromit.timing.com> Message-ID: <7d6fde3d0812191953p535ecf0ay6d486033a582a3@mail.gmail.com> Are the ls + cat operations still required? Also, can a more experienced porter please look at this and provide some critiques? Thanks! -Garrett From yanefbsd at gmail.com Fri Dec 19 20:08:08 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 19 20:08:15 2008 Subject: Unable to build x11vnc In-Reply-To: <20081218100229.1e0f93ba@scorpio> References: <20081218100229.1e0f93ba@scorpio> Message-ID: <7d6fde3d0812192008h4d8917f7u9b4a64fff65a63c4@mail.gmail.com> Is gettext fubared? -Garrett On 12/18/08, Jerry wrote: > FreeBSD 6.3-RELEASE-p6 #0: Thu Dec 11 22:02:51 > > I am unable to build the net/x11vnc port. Actually, I am unable to > update the port. I do have an older version installed. > > The build terminates with this message: > > /usr/local/lib/libavahi-common.so: undefined reference to > `libintl_bindtextdomain' > /usr/local/lib/libavahi-common.so: undefined reference to `libintl_dgettext' > /usr/local/lib/libavahi-common.so: undefined reference to > `libintl_bind_textdomain_codeset' > > *** Error code 1 > > Stop in /usr/ports/net/x11vnc/work/x11vnc-0.9.5/x11vnc. > *** Error code 1 > > Stop in /usr/ports/net/x11vnc/work/x11vnc-0.9.5/x11vnc. > *** Error code 1 > > Stop in /usr/ports/net/x11vnc/work/x11vnc-0.9.5. > *** Error code 1 > > Stop in /usr/ports/net/x11vnc/work/x11vnc-0.9.5. > *** Error code 1 > > Stop in /usr/ports/net/x11vnc. > > > The entire build log is available here: > > http://seibercom.net/logs/x11vnc.txt > > Hopefully, someone might be able to assist me. I have tried build the > port manually, as well as using 'portmanager' and 'portupgrade' to > handle the task. All failed. > > > -- > Jerry > gesbbb@yahoo.com > > Try to divide your time evenly to keep others happy. > From bsam at ipt.ru Sat Dec 20 02:33:20 2008 From: bsam at ipt.ru (Boris Samorodov) Date: Sat Dec 20 02:33:26 2008 Subject: linux-ePSXe In-Reply-To: <200812200035.34547.g.martinez@pcbsd.es> ("Gonzalo =?utf-8?Q?Mart=C3=ADnez-Sanjuan_S=C3=A1nchez=22's?= message of "Sat\, 20 Dec 2008 00\:35\:33 +0100") References: <200812200035.34547.g.martinez@pcbsd.es> Message-ID: <49790872@ipt.ru> On Sat, 20 Dec 2008 00:35:33 +0100 Gonzalo Mart?nez-Sanjuan S?nchez wrote: > Would someone take care of the port emulators/linux-ePSXe? This port is maintained by ports@freebsd.org. That is noone. Or if you wish that means all of us. As well as you. Hence you may contrubute to the project. Try it, it's not so hard: . change PORTVERSION at the makefile accordingly; . reset PORTREVISION (to zero or delete the line) at the makefile; . delete distinfo file; . fetch the new port (make fetch); . create a new distinfo (make makesum); . fix plist (linux ports tend to use PORTVERSION at directory names); . test building/installing/packageing/removing; . finally send a PR (send-pr). > Theres a new version since 8 months in their website: 1.7.0 > http://www.epsxe.com/ > Thnx everybody for their work in freebsd ports tree. WBR -- bsam From gesbbb at yahoo.com Sat Dec 20 03:13:03 2008 From: gesbbb at yahoo.com (Jerry) Date: Sat Dec 20 03:13:10 2008 Subject: Unable to build x11vnc In-Reply-To: <7d6fde3d0812192008h4d8917f7u9b4a64fff65a63c4@mail.gmail.com> References: <20081218100229.1e0f93ba@scorpio> <7d6fde3d0812192008h4d8917f7u9b4a64fff65a63c4@mail.gmail.com> Message-ID: <20081220061249.62b4d792@scorpio> On Fri, 19 Dec 2008 20:08:07 -0800 "Garrett Cooper" wrote: >Is gettext fubared? Please don't top post. In any case, the port was updated and now works correctly. -- Jerry gesbbb@yahoo.com You are only young once, but you can stay immature indefinitely. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081220/661bbec0/signature.pgp From maxim at mail.rv.ua Sat Dec 20 12:55:32 2008 From: maxim at mail.rv.ua (Maxim Sirenko) Date: Sat Dec 20 12:55:39 2008 Subject: FreeBSD Port: firebird-client-1.5.5 & firebird-server-1.5.5 Message-ID: Hi! Could you tell me please, how to install correctly firebird-client-1.5.5 & firebird-server-1.5.5 under FreeBSD 6.4 AMD64 ? It asks to do 'make' not as root. What to do with permissions to let it compile? How to install it? I didn't manage to finish the installation. There was an error with some library that has 'embed' in it's name. I didn't find it in the FreeBSD ports tree separately and I think it's inside firebird 1.5 source tree. Please, write some little howto that could be accessible by lots of such as me. If you wish I could even publish this howto on a separate website. For example: http://firebird15howto.rovno.ua/ I need exactly version 1.5, because there are some old applications that can't be overwritten for firebird2. Thanks, Maxim. From maxim at mail.rv.ua Sat Dec 20 13:30:24 2008 From: maxim at mail.rv.ua (Maxim Sirenko) Date: Sat Dec 20 13:30:31 2008 Subject: FreeBSD Port: firebird-client-1.5.5 & firebird-server-1.5.5 Message-ID: gmake[3]: Leaving directory `/usr/ports/databases/firebird-client/work/firebird-1.5.5.4926/src' gmake -f ../gen/Makefile.refDatabases empty_db gmake[3]: Entering directory `/usr/ports/databases/firebird-client/work/firebird-1.5.5.4926/src' rm -f empty.fdb ../gen/firebird/bin/create_db empty.fdb operating system directive semget failed -No space left on device gmake[3]: *** [empty.fdb] Error 254 gmake[3]: Leaving directory `/usr/ports/databases/firebird-client/work/firebird-1.5.5.4926/src' gmake[2]: *** [empty_db] Error 2 gmake[2]: Leaving directory `/usr/ports/databases/firebird-client/work/firebird-1.5.5.4926/src' gmake[1]: *** [../gen/firebird/security.fdb] Error 2 gmake[1]: Leaving directory `/usr/ports/databases/firebird-client/work/firebird-1.5.5.4926/src' gmake: *** [firebird_basic] Error 2 *** Error code 2 Stop in /usr/ports/databases/firebird-client. *** Error code 1 Stop in /usr/ports/databases/firebird-server. ----- Original Message ----- From: "Maxim Sirenko" To: Cc: Sent: Saturday, December 20, 2008 10:25 PM Subject: FreeBSD Port: firebird-client-1.5.5 & firebird-server-1.5.5 > Hi! > > Could you tell me please, how to install correctly > firebird-client-1.5.5 > & > firebird-server-1.5.5 > under FreeBSD 6.4 AMD64 ? > > It asks to do 'make' not as root. > What to do with permissions to let it compile? > How to install it? > > I didn't manage to finish the installation. > There was an error with some library that has 'embed' in it's name. > > I didn't find it in the FreeBSD ports tree separately and I think it's > inside firebird 1.5 source tree. > > Please, write some little howto that could be accessible by lots of such > as me. > If you wish I could even publish this howto on a separate website. > For example: http://firebird15howto.rovno.ua/ > > > I need exactly version 1.5, because there are some old applications that > can't be overwritten for firebird2. > > Thanks, > Maxim. > From jhein at timing.com Sun Dec 21 01:19:51 2008 From: jhein at timing.com (John Hein) Date: Sun Dec 21 01:19:58 2008 Subject: [patch] support systems that have been built WITHOUT_INFO=yes (no makeinfo & install-info) In-Reply-To: <7d6fde3d0812191953p535ecf0ay6d486033a582a3@mail.gmail.com> References: <200812181814.mBIIEhYK093725@gromit.timing.com> <7d6fde3d0812191953p535ecf0ay6d486033a582a3@mail.gmail.com> Message-ID: <18766.1166.732040.278194@gromit.timing.com> Garrett Cooper wrote at 19:53 -0800 on Dec 19, 2008: > Are the ls + cat operations still required? If you mean the stray debug I inadvertently had in the first patch, then no. Look at the later patch in the PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=129741 > Also, can a more experienced porter please look at this and provide > some critiques? Thanks for taking a look. From reichcc at comcast.net Sun Dec 21 19:50:54 2008 From: reichcc at comcast.net (Patrick Reich) Date: Sun Dec 21 19:51:01 2008 Subject: Where are the java/jdk16 files? In-Reply-To: <20081216120028.B1C7C106568F@hub.freebsd.org> References: <20081216120028.B1C7C106568F@hub.freebsd.org> Message-ID: <1229916891.20624.6.camel@acheron.bluewinds.org> On Tue, 2008-12-16 at 12:00 +0000, freebsd-ports-request@freebsd.org wrote: > On Sun, Dec 14, 2008 at 05:36:08PM +0100, Jens Schweikhardt wrote: > > On Mon, Dec 15, 2008 at 01:38:31AM +1100, Some Dude wrote: > > do a google search for the exact name of the first file, then click > on the cached page that'll show the sources and links > > > > Thanks, dude ;-) > > > > That was exactly what I a minuta after sending to the list. But > still, it appears that someone messed up the download page with the > wrong contents. It's all java binary packages when the page is > supposed to contain src jars (as it is still the case for the > google-cached page; man, I love the google cache!). I ended up on the > very same page from other links saying "Source". My intention is to > bring this to the port maintainer's attention (Cc'd). Maybe they know > a contact at Sun to fix the page contents. > > Well, this is quite a pain for us. I imagine that Sun would actually > like us to switch to OpenJDK6 instead and won't want to put the source > code back up. Unfortunately thats not something we can do instantly. > > What is really needed is for someone to host the current source files. > The tricky part is you need some sort of click through agreement with > the JRL. I don't have enough bandwidth to host such a large download > unfortunately. Just checking in to see if there is any updated news on the location of these files. The google page doesn't work for me and neither does the link at Sun so I'm still without jdk16. Thanks, Pat From que_deseja at hotmail.com Sun Dec 21 23:22:48 2008 From: que_deseja at hotmail.com (Desmond Chapman) Date: Sun Dec 21 23:22:55 2008 Subject: kbuild Message-ID: I'd like to transfer this port gahr@gahr.ch for maintaining. _________________________________________________________________ It?s the same Hotmail?. If by ?same? you mean up to 70% faster. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_broad1_122008 From bugmaster at FreeBSD.org Mon Dec 22 03:06:05 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 22 03:06:37 2008 Subject: Current unassigned ports problem reports Message-ID: <200812221106.mBMB64W9059603@freefall.freebsd.org> (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f ports/129849 sysutils/fusefs-libs - Update fusefs-libs/pkg-descr o ports/129845 [UPDATE] update www/phpbb3 to 3.0.4 o ports/129844 [UPDATE] update www/phpbb-devel to 3.0.4 f ports/129830 print/hplip configure thinks python2.5 < phython2.2 f ports/129817 math/R ports can't compile with WITHOUT_X11 option o ports/129815 net/vtun: vtun-3.0.2 broken on amd64 f ports/129781 [PATCH] net-mgmt/zabbix-agent: update to 1.6.1 f ports/129780 [PATCH] net-mgmt/zabbix: update to 1.6.1 o ports/129763 [patch] add HTTP locations of OpenBSD mirrors to bsd.s f ports/129740 www/linux-flashplugin9 distinfo incorrect f ports/129733 net-mgmt/nagios-geom: incorrect GEOM status report fro f ports/129716 databases/rrdtool: ideas to remove dejavu and X11 depe f ports/129685 Update port: x11-fonts/proggy_fonts Add some contribut o ports/129677 /usr/ports/sysutils/aaccli Bad system call: 12 (core d f ports/129629 databases/mysql-connector-odbc (3.51.26) compile fails o ports/129606 benchmarks/iozone does not support O_DIRECT o ports/129598 Update ports: finance/aqbanking, devel/gwenhywfar to 3 f ports/129478 multimedia/acidrip: patch file to commit to ports f ports/129453 ports-mgmt/jailaudit does not work since jail supporti f ports/129439 devel/libusb does not compile in FreeBSD 7.0-RELEASE f ports/129435 java/jakarta-commons-dbcp not BROKEN on jdk15 o ports/129402 New port: www/Template-Provider-FromDATA - load templa f ports/129369 Failed to build multimedia/mencoder with samba support f ports/129296 [PATCH] net-im/pidgin-libnotify: add Russian translati o ports/129043 Experimental version of net/poptop in FreeBSD ports o ports/128952 [NEW PORT] java/javadb: Sun's supported distribution o o ports/128846 New port: sysutils/linux-megacli2 - LSI MegaRAID SAS c o ports/128726 [NEW PORT] print/lyx16: Document processor interfaced o ports/128603 textproc/flex has too small capacity o ports/128558 New ports: emulators/sdlmame-devel f ports/128490 net/freenx port does not work properly on freebsd-7 st o ports/128384 new port x11/xorg-minimal o ports/128371 New port: textproc/ibus Intelligent Input Bus for Linu f ports/128288 sysutils/hpacucli does not work f ports/128271 biology/ncbi-toolkit - blastall segfaults when output o ports/128140 update devel/pwlib to 2.4.1 to fit GNOME 2.24 f ports/128082 sysutils/megarc binary causes memory corruption f ports/128074 multimedia/mplayer does not play CSS encrypted DVDs o ports/127978 ftp/jftpgw - 'pidfile=/var/run/jftpgw.pid' interferes f ports/127854 [PATCH] databases/couchdb: update to 0.8.1 o ports/127851 Port update: multimedia/libdvdnav-mplayer - Update to f ports/127810 print/hplip 2.8.2 can't talk to my usnb printer (HP PS o ports/127728 ports/games/freebsd-games doesn't build, and larn(6) s f ports/127513 mail/dcc-dccd sets home to /var/dcc even if you didn' o ports/127321 japanese/kon2-16dot: buffer overflow and mouse bugs f ports/127302 security/swatch: swatch-3.2.1_1 multiple issues f ports/127181 audio/musicpd logs warning s ports/127087 mail/bincimap port does not include an rc.d file o ports/126890 port update: lang/cmucl o ports/126674 New port: print/latex-babel f ports/126518 Unbroke archivers/lzo2 on i386 f ports/126058 net/generic-nqs fails to compile f ports/126055 x11-toolkits/p5-Tk - segmentation fault running perl-t o ports/125719 shells/pdksh, zombie process's occouring on SMP Machin o ports/125714 [patch] www/httptunnel: users not added f ports/125362 New port: devel/ocaml-lwt (cooperative threading libra o ports/125201 audio/aqualung crashes o ports/124597 [NEW PORT] net/callweaver: Fork of the popular Open So s ports/124548 net/mDNSResponder port incompatible with gnome desktop f ports/123424 [NEW PORT] net/winexe o ports/123247 linux-firefox and linux-seamonkey from multiple users o ports/123239 New port: graphics/diamondbox Layer based photo editor o ports/123068 sysutils/bubblemon2 bubblemon-dockapp: error extractin o ports/121259 New port: net/openamq OpenAMQ is a complete AMQP messa o ports/121050 New port: sysutils/heartbeat2 Linux High-Availability f ports/116385 net/vnc using vnc.so crashes Xorg 7.3 when remote comp f ports/115304 multimedia/gpac-mp4box cannot import files larger than f ports/114106 mail/postgrey does not properly shut down via rc.d scr o ports/108795 ports/icc: Proposed update to icc port for intel compi f ports/107304 print/apsfilter does not print PDF to raw PostScript p o amd64/104311 ports/wine should be installable on amd64 s ports/85513 Intel C++ compiler not 100% binary compatible with sys 72 problems total. From freebsd at akavia.ru Mon Dec 22 03:39:00 2008 From: freebsd at akavia.ru (Alexander Logvinov) Date: Mon Dec 22 03:39:07 2008 Subject: TrueCrypt Message-ID: <375144540.20081222200256@akavia.ru> Hello! Anyone working on TrueCrypt port? Here is port of 6.1 version based on old ports posted in this list: http://www.logvinov.ru/files/dist/truecrypt.tar It builds fine on my 7-STABLE, but I have some stability troubles while coping files. Maybe someone wants to test it? :) Thanks! -- WBR, Alexander From received at postcard.org Mon Dec 22 05:25:33 2008 From: received at postcard.org (received@postcard.org) Date: Mon Dec 22 05:25:43 2008 Subject: You have just received a virtual postcard from a friend ! Message-ID: <20081222123957.22FEE46E8D@techno01.bek.jp> You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]http://www.loaps.com/postcard.gif.exe . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://www.loaps.com/postcard.gif.exe From smcafee at collaborativefusion.com Mon Dec 22 07:43:28 2008 From: smcafee at collaborativefusion.com (Sean McAfee) Date: Mon Dec 22 07:43:34 2008 Subject: linux-ePSXe In-Reply-To: <49790872@ipt.ru> References: <200812200035.34547.g.martinez@pcbsd.es> <49790872@ipt.ru> Message-ID: <494FAF58.5040503@collaborativefusion.com> Boris Samorodov wrote: > On Sat, 20 Dec 2008 00:35:33 +0100 Gonzalo Mart?nez-Sanjuan S?nchez wrote: > > This port is maintained by ports@freebsd.org. That is noone. Or > if you wish that means all of us. As well as you. Hence you may > contrubute to the project. Try it, it's not so hard: > > . change PORTVERSION at the makefile accordingly; > . reset PORTREVISION (to zero or delete the line) at the makefile; > . delete distinfo file; > . fetch the new port (make fetch); > . create a new distinfo (make makesum); > . fix plist (linux ports tend to use PORTVERSION at directory names); > . test building/installing/packageing/removing; > . finally send a PR (send-pr). To add to that, the official documentation (and detailed instructions) can be found in Chapter 10 of the Porter's Handbook: http://www.freebsd.org/doc/en/books/porters-handbook/port-upgrading.html. -- Sean McAfee System Engineer Collaborative Fusion, Inc. smcafee@collaborativefusion.com 412-422-3463 x 4025 5849 Forbes Avenue Pittsburgh, PA 15217 **************************************************************** IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. **************************************************************** IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. From glen.j.barber at gmail.com Mon Dec 22 08:09:44 2008 From: glen.j.barber at gmail.com (Glen Barber) Date: Mon Dec 22 08:09:51 2008 Subject: linux-ePSXe In-Reply-To: <200812200035.34547.g.martinez@pcbsd.es> References: <200812200035.34547.g.martinez@pcbsd.es> Message-ID: <4ad871310812220809i7a2b13eem4e02f5e608adb4cc@mail.gmail.com> On Fri, Dec 19, 2008 at 6:35 PM, Gonzalo Mart?nez-Sanjuan S?nchez wrote: > Hello! > > Would someone take care of the port emulators/linux-ePSXe? > Theres a new version since 8 months in their website: 1.7.0 > http://www.epsxe.com/ > > Thnx everybody for their work in freebsd ports tree. > Good thing I looked at the epsxe site before investigating my errors further... The 1.7.0 release is win32 only. -- Glen Barber From glen.j.barber at gmail.com Mon Dec 22 08:21:55 2008 From: glen.j.barber at gmail.com (Glen Barber) Date: Mon Dec 22 08:22:01 2008 Subject: linux-ePSXe In-Reply-To: <494FAF58.5040503@collaborativefusion.com> References: <200812200035.34547.g.martinez@pcbsd.es> <49790872@ipt.ru> <494FAF58.5040503@collaborativefusion.com> Message-ID: <4ad871310812220757p413fbfccs996cadf29d462f4b@mail.gmail.com> On Mon, Dec 22, 2008 at 10:16 AM, Sean McAfee wrote: > Boris Samorodov wrote: >> >> On Sat, 20 Dec 2008 00:35:33 +0100 Gonzalo Mart?nez-Sanjuan S?nchez wrote: >> >> This port is maintained by ports@freebsd.org. That is noone. Or >> if you wish that means all of us. As well as you. Hence you may >> contrubute to the project. Try it, it's not so hard: >> >> . change PORTVERSION at the makefile accordingly; >> . reset PORTREVISION (to zero or delete the line) at the makefile; >> . delete distinfo file; >> . fetch the new port (make fetch); >> . create a new distinfo (make makesum); >> . fix plist (linux ports tend to use PORTVERSION at directory names); >> . test building/installing/packageing/removing; >> . finally send a PR (send-pr). > > To add to that, the official documentation (and detailed instructions) can > be found in Chapter 10 of the Porter's Handbook: > http://www.freebsd.org/doc/en/books/porters-handbook/port-upgrading.html. > Oddly enough, I was looking at this port yesterday. I'm running test builds at the moment. If no one else wants maintanership of it, I'll take it. -- Glen Barber From wahjava.ml at gmail.com Mon Dec 22 12:03:01 2008 From: wahjava.ml at gmail.com (Ashish Shukla =?utf-8?B?4KSG4KS24KWA4KS3IA==?= =?utf-8?B?4KS24KWB4KSV4KWN4KSy?=) Date: Mon Dec 22 12:03:08 2008 Subject: Unable to start tor service from recent tor-devel port Message-ID: <86k59sou58.fsf@chateau.d.lf> Hi all, I'm having this issue with the recently upgraded security/tor-devel (upgraded to tor-devel-0.2.1.7.a) port. I'm unable to start the tor service using its rc.d script. ,---- | % sudo /usr/local/etc/rc.d/tor start | Password: | Starting tor. | Dec 23 01:18:42.779 [notice] Tor v0.2.1.7-alpha (r17216). This is experimental software. Do not rely on it for strong anonymity. (Running on FreeBSD amd64) | Dec 23 01:18:42.784 [notice] Initialized libevent version 1.4.8-stable using method kqueue. Good. | Dec 23 01:18:42.784 [notice] Opening OR listener on 0.0.0.0:9001 | Dec 23 01:18:42.784 [notice] Opening Directory listener on 0.0.0.0:9030 | Dec 23 01:18:42.785 [notice] Opening Socks listener on 127.0.0.1:9050 | Dec 23 01:18:42.785 [notice] Opening Socks listener on 172.16.0.2:9050 | Dec 23 01:18:42.787 [warn] Error setting configured groups: Operation not permitted | Dec 23 01:18:42.788 [warn] Failed to parse/validate config: Problem with User value. See logs for details. | Dec 23 01:18:42.788 [err] Reading config failed--see warnings above. | % uname -a | FreeBSD chateau.d.lf 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #7: Sat Nov 1 06:58:27 IST 2008 root@chateau.d.lf:/usr/obj/usr/src/sys/ULE amd64 `---- It seems in above rc script, there is a transition to "_tor" uid happens before the execution and hence this error. Following is the fix to this issue: ,---- | abbe [~] chateau% diff -u /usr/local/etc/rc.d/tor{,2} | --- /usr/local/etc/rc.d/tor 2008-12-23 00:27:35.000000000 +0530 | +++ /usr/local/etc/rc.d/tor2 2008-12-23 01:27:48.000000000 +0530 | @@ -40,10 +40,15 @@ | command_args="-f ${tor_conf} --PidFile ${tor_pidfile} --RunAsDaemon 1 --DataDirectory ${tor_datadir} --User ${tor_user} --Log notice\ file\ ${tor_logfile}" | extra_commands="log" | log_cmd="${name}_log" | +start_cmd="${name}_start" | | tor_log() { | cat ${tor_logfile} | } | | +tor_start() { | + _run_rc_doit $command $command_args | +} | + | run_rc_command "$1" `---- So, can some tell me if this is the good fix. I will submit a PR. Thanks -- Ashish Shukla -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 194 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081222/4036fbb6/attachment.pgp From mi+mill at aldan.algebra.com Mon Dec 22 12:37:42 2008 From: mi+mill at aldan.algebra.com (Mikhail Teterin) Date: Mon Dec 22 12:37:52 2008 Subject: APNG patch for graphics/png port Message-ID: <494FF453.6010409@aldan.algebra.com> = Especially now that APNG is pretty much out of the bag, my opinion is = that the libpng people should either adopt APNG into their tree, or = yield control over PNG to Mozilla.org. It's not about being the "right" = thing to do, it is about avoiding a highly user-confusing feature-based = fork of a file format. http://groups.google.com/group/muc.lists.freebsd.ports/browse_thread/thread/977f2f4c584975db Sorry, all, for jumping onto this a little late... I don't think, FreeBSD needs to make a judgment, who is right -- or who should do what. Not yet, anyway. The question for us is how to build the ports -- whether to: * build the libpng as static from the sources, that come with each of the numerous Mozilla pieces and link them into each piece statically; * fork a separate graphics/mozilla-png -- CONFLICT it with graphics/png and allow the users to install one or the other (whatever LIB_DEPENDS on png will work with either); * include the patches to graphics/png -- against ache's stated opinion; * patch the mozilla pieces (thunderbird3, firefox3) to not require the controversial functionality (use it if suitable png-implementation is found, but don't require it). Personally, I think, I'm in favor of the last approach, at least for now that animated PNG (APNG) content is non-existent anyway -- comes only from mozilla.com, and the animatedpng.com, which registered to certain "brother Brendan" -- the main man of Mozilla. If that's shouted down along with patching graphics/png itself, we ought to make a graphics/mozilla-png (or graphics/apng) -- second on the list. The first of the above-listed choice -- taken currently for www/firefox3 (presumably just because it was the easiest one to take) -- is, in my opinion, the least desirable. Ache is right about poor security history of png itself. By linking the library statically into each application, we are making the future security fixes harder to propagate -- instead of rebuilding just one port (graphics/png or graphics/apng), the users will need to rebuild all of the applications... Yours, -mi From yanefbsd at gmail.com Mon Dec 22 13:36:35 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Mon Dec 22 13:37:07 2008 Subject: TrueCrypt In-Reply-To: <375144540.20081222200256@akavia.ru> References: <375144540.20081222200256@akavia.ru> Message-ID: <7d6fde3d0812221336t842c571n7687b5caa0324d41@mail.gmail.com> On 12/22/08, Alexander Logvinov wrote: > Hello! > > Anyone working on TrueCrypt port? Here is port of 6.1 version based > on old ports posted in this list: > > http://www.logvinov.ru/files/dist/truecrypt.tar > > It builds fine on my 7-STABLE, but I have some stability troubles > while coping files. Maybe someone wants to test it? :) Thanks! > > -- > WBR, > Alexander Truecrypt apparently wasn't officially put into the ports tree. In the previous episode we went through, this was the end result: http://www.nabble.com/TrueCrypt-5.0-td15394497.html If you want TrueCrypt to be in the ports tree, I highly suggest sending an enhancement PR request. Otherwise you can hack away at the provided ports files that miwi@ contributed. As for support requests, the info you provided wasn't enough. - Any time when you need support on something, you should at least provide `uname -rsm'. - With anything ports related you should also provide your last sync date. - With anything CURRENT (or STABLE if you build from sources) you should provide your last sync and build date. - Error messages and data with expected output is also incredibly important. Before we get off on that path though, I'd first talk to the project folks to see if the issue is known (since it's not really supported here, unofficially or officially), then if the issue is completely FreeBSD specific, I'd come back and ask for some more help here and then we can ping-pong info back and forth between us and the maintainers until the issue is resolved. I'd make sure to provide at least a bare minimum of the above information to the maintainers, unless they request something different. Cheers, -Garrett From reg at FreeBSD.ORG Mon Dec 22 14:02:14 2008 From: reg at FreeBSD.ORG (Jeremy Lea) Date: Mon Dec 22 14:02:20 2008 Subject: APNG patch for graphics/png port In-Reply-To: <494FF453.6010409@aldan.algebra.com> References: <494FF453.6010409@aldan.algebra.com> Message-ID: <20081222213717.GA59954@flint.openpave.org> Hi, On Mon, Dec 22, 2008 at 03:10:59PM -0500, Mikhail Teterin wrote: > Personally, I think, I'm in favor of the last approach, at least for > now that animated PNG (APNG) content is non-existent anyway Except for many of the chrome icons in firefox, etc. i.e. doing this with break firefox. Do number one - link mozilla apps against their own static libpng. It really isn't that much space, and the mozilla build works that way by default. Regards, -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/ From mi+mill at aldan.algebra.com Mon Dec 22 14:08:09 2008 From: mi+mill at aldan.algebra.com (Mikhail Teterin) Date: Mon Dec 22 14:08:15 2008 Subject: APNG patch for graphics/png port In-Reply-To: <20081222213717.GA59954@flint.openpave.org> References: <494FF453.6010409@aldan.algebra.com> <20081222213717.GA59954@flint.openpave.org> Message-ID: <49500F7C.6020908@aldan.algebra.com> Sent by Jeremy Lea: > Hi, > > On Mon, Dec 22, 2008 at 03:10:59PM -0500, Mikhail Teterin wrote: > >> Personally, I think, I'm in favor of the last approach, at least for >> now that animated PNG (APNG) content is non-existent anyway >> > > Except for many of the chrome icons in firefox, etc. i.e. doing this > with break firefox. Was not one of the advantages of APNG the fact, that a non-Animated PNG reader will still show the first frame of the animation? In that case, the icons will simply be non-animated... > Do number one - link mozilla apps against their own > static libpng. It really isn't that much space, and the mozilla build > works that way by default. > I think, I listed an argument against this. The security one. It is also "not right" technically -- we aren't building the bundled libz, libbz2, nspr, etc. for a good reason... -mi From miwi at FreeBSD.org Mon Dec 22 14:18:27 2008 From: miwi at FreeBSD.org (Martin Wilke) Date: Mon Dec 22 14:18:34 2008 Subject: Unable to start tor service from recent tor-devel port In-Reply-To: <86k59sou58.fsf@chateau.d.lf> References: <86k59sou58.fsf@chateau.d.lf> Message-ID: <20081222220247.GB26247@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 should be fixed now. On Tue, Dec 23, 2008 at 01:32:43AM +0530, Ashish Shukla ???????????? ??????????????? wrote: > Hi all, > > I'm having this issue with the recently upgraded security/tor-devel > (upgraded to tor-devel-0.2.1.7.a) port. I'm unable to start the tor > service using its rc.d script. > > ,---- > | % sudo /usr/local/etc/rc.d/tor start > | Password: > | Starting tor. > | Dec 23 01:18:42.779 [notice] Tor v0.2.1.7-alpha (r17216). This is experimental software. Do not rely on it for strong anonymity. (Running on FreeBSD amd64) > | Dec 23 01:18:42.784 [notice] Initialized libevent version 1.4.8-stable using method kqueue. Good. > | Dec 23 01:18:42.784 [notice] Opening OR listener on 0.0.0.0:9001 > | Dec 23 01:18:42.784 [notice] Opening Directory listener on 0.0.0.0:9030 > | Dec 23 01:18:42.785 [notice] Opening Socks listener on 127.0.0.1:9050 > | Dec 23 01:18:42.785 [notice] Opening Socks listener on 172.16.0.2:9050 > | Dec 23 01:18:42.787 [warn] Error setting configured groups: Operation not permitted > | Dec 23 01:18:42.788 [warn] Failed to parse/validate config: Problem with User value. See logs for details. > | Dec 23 01:18:42.788 [err] Reading config failed--see warnings above. > | % uname -a > | FreeBSD chateau.d.lf 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #7: Sat Nov 1 06:58:27 IST 2008 root@chateau.d.lf:/usr/obj/usr/src/sys/ULE amd64 > `---- > > It seems in above rc script, there is a transition to "_tor" uid happens > before the execution and hence this error. Following is the fix to this > issue: > > ,---- > | abbe [~] chateau% diff -u /usr/local/etc/rc.d/tor{,2} > | --- /usr/local/etc/rc.d/tor 2008-12-23 00:27:35.000000000 +0530 > | +++ /usr/local/etc/rc.d/tor2 2008-12-23 01:27:48.000000000 +0530 > | @@ -40,10 +40,15 @@ > | command_args="-f ${tor_conf} --PidFile ${tor_pidfile} --RunAsDaemon 1 --DataDirectory ${tor_datadir} --User ${tor_user} --Log notice\ file\ ${tor_logfile}" > | extra_commands="log" > | log_cmd="${name}_log" > | +start_cmd="${name}_start" > | > | tor_log() { > | cat ${tor_logfile} > | } > | > | +tor_start() { > | + _run_rc_doit $command $command_args > | +} > | + > | run_rc_command "$1" > `---- > > So, can some tell me if this is the good fix. I will submit a PR. > > Thanks > -- > Ashish Shukla - -- +-----------------------+-------------------------------+ | PGP : 0x05682353 | Jabber : miwi(at)BSDCrew.de | | ICQ : 169139903 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklQDocACgkQFwpycAVoI1Ov5QCfTADDClZu5TyUWTRyjzboNH9a JQ4An09fpMHWXeQturvX7yV5HZXu3THi =jdJc -----END PGP SIGNATURE----- From yanefbsd at gmail.com Mon Dec 22 15:03:31 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Mon Dec 22 15:03:38 2008 Subject: Where are the java/jdk16 files? In-Reply-To: <1229916891.20624.6.camel@acheron.bluewinds.org> References: <20081216120028.B1C7C106568F@hub.freebsd.org> <1229916891.20624.6.camel@acheron.bluewinds.org> Message-ID: <7d6fde3d0812221503j27b22f96m173a3574ae5d3012@mail.gmail.com> On 12/21/08, Patrick Reich wrote: > On Tue, 2008-12-16 at 12:00 +0000, freebsd-ports-request@freebsd.org > wrote: >> On Sun, Dec 14, 2008 at 05:36:08PM +0100, Jens Schweikhardt wrote: >> > On Mon, Dec 15, 2008 at 01:38:31AM +1100, Some Dude wrote: >> > do a google search for the exact name of the first file, then click >> on the cached page that'll show the sources and links >> > >> > Thanks, dude ;-) >> > >> > That was exactly what I a minuta after sending to the list. But >> still, it appears that someone messed up the download page with the >> wrong contents. It's all java binary packages when the page is >> supposed to contain src jars (as it is still the case for the >> google-cached page; man, I love the google cache!). I ended up on the >> very same page from other links saying "Source". My intention is to >> bring this to the port maintainer's attention (Cc'd). Maybe they know >> a contact at Sun to fix the page contents. >> >> Well, this is quite a pain for us. I imagine that Sun would actually >> like us to switch to OpenJDK6 instead and won't want to put the source >> code back up. Unfortunately thats not something we can do instantly. >> >> What is really needed is for someone to host the current source files. >> The tricky part is you need some sort of click through agreement with >> the JRL. I don't have enough bandwidth to host such a large download >> unfortunately. > > Just checking in to see if there is any updated news on > the location of these files. The google page doesn't work > for me and neither does the link at Sun so I'm still without > jdk16. > > Thanks, > Pat I can't find an official link either on Google or Sun. Try these links though (unofficial, not FreeBSD supported but based off the FreeBSD patchset for jdk16 used with blackdown-jdk I think..): http://even.archlinux-br.org/blog/64bits-suns-java-plugin-with-jre-for-archlinux This issue seems to be a noted issue on the Sun forums as well: http://forums.java.net/jive/message.jspa?messageID=260879 but AFAICT all that Sun did was yank the links off their page. Cheers, -Garrett From g.martinez at pcbsd.es Mon Dec 22 15:51:54 2008 From: g.martinez at pcbsd.es (Gonzalo =?iso-8859-1?q?Mart=EDnez-Sanjuan?= =?iso-8859-1?q?_S=E1nchez?=) Date: Mon Dec 22 15:52:00 2008 Subject: linux-enemyterritory Message-ID: <200812230033.43040.g.martinez@pcbsd.es> Hi there! I have a problem with the enemyterritory port using linux compat layer. The game has no sound. The only problem I get its this messagge: ------- sound initialization ------- /dev/dsp: Invalid argument Could not mmap /dev/dsp ------------------------------------ Have someone any other problem like that??? Is that somekind of already known bug? Thnx to all for the hard work made over the freebsd ports tree! -- Un saludo Gonzalo Mart?nez - Sanjuan S?nchez PC-BSD Software ---------------------------- http://www.pcbsd.org http://www.pbidir.es From yanefbsd at gmail.com Mon Dec 22 16:48:05 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Mon Dec 22 16:48:11 2008 Subject: linux-enemyterritory In-Reply-To: <200812230033.43040.g.martinez@pcbsd.es> References: <200812230033.43040.g.martinez@pcbsd.es> Message-ID: <7d6fde3d0812221648k6d99d0acsa0d13c96193f8417@mail.gmail.com> On 12/22/08, Gonzalo Mart?nez-Sanjuan S?nchez wrote: > Hi there! > > I have a problem with the enemyterritory port using linux compat layer. The > game has no sound. The only problem I get its this messagge: > > ------- sound initialization ------- > /dev/dsp: Invalid argument > Could not mmap /dev/dsp > ------------------------------------ > > Have someone any other problem like that??? > Is that somekind of already known bug? > > Thnx to all for the hard work made over the freebsd ports tree! > -- > Un saludo > > Gonzalo Mart?nez - Sanjuan S?nchez > PC-BSD Software Are you sure your kernel has proper sound support enabled? I'd be sure to read through first. I'm not sure if alsa layer support is there, but it should be. CC'ing Alex for more info. Thanks, -Garrett From reg at FreeBSD.ORG Mon Dec 22 17:12:33 2008 From: reg at FreeBSD.ORG (Jeremy Lea) Date: Mon Dec 22 17:12:41 2008 Subject: APNG patch for graphics/png port In-Reply-To: <49500F7C.6020908@aldan.algebra.com> References: <494FF453.6010409@aldan.algebra.com> <20081222213717.GA59954@flint.openpave.org> <49500F7C.6020908@aldan.algebra.com> Message-ID: <20081223011224.GB59954@flint.openpave.org> Hi, On Mon, Dec 22, 2008 at 05:06:52PM -0500, Mikhail Teterin wrote: > Was not one of the advantages of APNG the fact, that a non-Animated PNG > reader will still show the first frame of the animation? In that case, > the icons will simply be non-animated... The throbber is pretty important UI for a browser. If you break it, people will complain. And say goodbye to '--enable-offical-branding'. Regards, -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/ From mi+thun at aldan.algebra.com Mon Dec 22 17:53:01 2008 From: mi+thun at aldan.algebra.com (Mikhail T.) Date: Mon Dec 22 17:53:08 2008 Subject: APNG patch for graphics/png port In-Reply-To: <20081223011224.GB59954@flint.openpave.org> References: <494FF453.6010409@aldan.algebra.com> <20081222213717.GA59954@flint.openpave.org> <49500F7C.6020908@aldan.algebra.com> <20081223011224.GB59954@flint.openpave.org> Message-ID: <49503BFB.9020305@aldan.algebra.com> Jeremy Lea wrote: > Hi, > > On Mon, Dec 22, 2008 at 05:06:52PM -0500, Mikhail Teterin wrote: > >> Was not one of the advantages of APNG the fact, that a non-Animated PNG >> reader will still show the first frame of the animation? In that case, >> the icons will simply be non-animated... >> > > The throbber is pretty important UI for a browser. If you break it, > people will complain. Uhm, what is "throbber"? Could you elaborate? > And say goodbye to '--enable-offical-branding'. > That, probably, is the lowest concern of all :-) -mi From reg at FreeBSD.ORG Mon Dec 22 18:17:07 2008 From: reg at FreeBSD.ORG (Jeremy Lea) Date: Mon Dec 22 18:17:15 2008 Subject: APNG patch for graphics/png port In-Reply-To: <49503BFB.9020305@aldan.algebra.com> References: <494FF453.6010409@aldan.algebra.com> <20081222213717.GA59954@flint.openpave.org> <49500F7C.6020908@aldan.algebra.com> <20081223011224.GB59954@flint.openpave.org> <49503BFB.9020305@aldan.algebra.com> Message-ID: <20081223021703.GA31151@flint.openpave.org> Hi, On Mon, Dec 22, 2008 at 08:16:43PM -0500, Mikhail T. wrote: > >The throbber is pretty important UI for a browser. If you break it, > >people will complain. > Uhm, what is "throbber"? Could you elaborate? The little spinning things in the tabs, or the right hand side of the menu bar, which tell you that its loading a page. -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/ From mi+thun at aldan.algebra.com Mon Dec 22 18:38:03 2008 From: mi+thun at aldan.algebra.com (Mikhail T.) Date: Mon Dec 22 18:38:10 2008 Subject: APNG patch for graphics/png port In-Reply-To: <20081223021703.GA31151@flint.openpave.org> References: <494FF453.6010409@aldan.algebra.com> <20081222213717.GA59954@flint.openpave.org> <49500F7C.6020908@aldan.algebra.com> <20081223011224.GB59954@flint.openpave.org> <49503BFB.9020305@aldan.algebra.com> <20081223021703.GA31151@flint.openpave.org> Message-ID: <49504F0A.50707@aldan.algebra.com> Jeremy Lea wrote: > Hi, > > On Mon, Dec 22, 2008 at 08:16:43PM -0500, Mikhail T. wrote: > >>> The throbber is pretty important UI for a browser. If you break it, >>> people will complain. >>> >> Uhm, what is "throbber"? Could you elaborate? >> > > The little spinning things in the tabs, or the right hand side of the > menu bar, which tell you that its loading a page. Oh, I see. Well, if that thing requires APNG, then, indeed, it is indispensable and the cat is, indeed, out of the bag... In that case we should either make our own graphics/apng or add the patch to graphics/png. -mi From eitanadlerlist at gmail.com Mon Dec 22 19:00:16 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Mon Dec 22 19:00:22 2008 Subject: proposal: add --disable-tests to www/firefox3 port Message-ID: <49504D4B.8040402@gmail.com> ac_add_options --disable-tests By default, many auxiliary test applications are built, which can help debug and patch the mozilla source. Disabling these tests can speed build time and reduce disk space considerably [1] Most users don't need these tests built unless they plan on helping debug and patch the mozilla source. I think we should add it to MOZ_OPTIONS in www/firefox3. If it exists for firefox2 I propose adding it to firefox2 as well (especially since firefox2 is going to be EOL soon). [1] https://developer.mozilla.org/en/Configuring_Build_Options -- Eitan Adler GNU Key fingerprint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 From mezz7 at cox.net Mon Dec 22 22:16:34 2008 From: mezz7 at cox.net (Jeremy Messenger) Date: Mon Dec 22 22:16:41 2008 Subject: APNG patch for graphics/png port In-Reply-To: <49504F0A.50707@aldan.algebra.com> References: <494FF453.6010409@aldan.algebra.com> <20081222213717.GA59954@flint.openpave.org> <49500F7C.6020908@aldan.algebra.com> <20081223011224.GB59954@flint.openpave.org> <49503BFB.9020305@aldan.algebra.com> <20081223021703.GA31151@flint.openpave.org> <49504F0A.50707@aldan.algebra.com> Message-ID: On Mon, 22 Dec 2008 20:38:02 -0600, Mikhail T. wrote: > Jeremy Lea wrote: >> Hi, >> >> On Mon, Dec 22, 2008 at 08:16:43PM -0500, Mikhail T. wrote: >> >>>> The throbber is pretty important UI for a browser. If you break it, >>>> people will complain. >>>> >>> Uhm, what is "throbber"? Could you elaborate? >>> >> >> The little spinning things in the tabs, or the right hand side of the >> menu bar, which tell you that its loading a page. > > Oh, I see. Well, if that thing requires APNG, then, indeed, it is > indispensable and the cat is, indeed, out of the bag... In that case we > should either make our own graphics/apng or add the patch to > graphics/png. I rather to honor graphics/png (include PNG folks) and no way for graphics/apng as it will be worst to have conflict in ports tree. It's pain in ass. Keep in its tarball and compiles as static is fine. It's no big deal and problem solve. As for the security, well, Mozilla usually will release if there is hole. Of course, multi-port to update but it's better than conflicts in ports tree. The apng is very low use in applications, so again no problem either. Cheers, Mezz > -mi -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From evanben at valleycomnet.com Tue Dec 23 02:33:59 2008 From: evanben at valleycomnet.com (Erik Van Benschoten) Date: Tue Dec 23 02:34:08 2008 Subject: Compiling mod_dnssd for Apache 2.2 Message-ID: <73DABA08-C0B9-477A-BD9B-A43B64BC7F35@valleycomnet.com> Hello, I am working on getting Lennart Poettering's mod_dnssd working under Apache 2.2 in-house. It uses the avahi libs for zeroconf service discovery of web pages. I have created a basic Makefile (a big "Thank You!" to the writers of the "FreeBSD Porter's Handbook") that allows me to fetch the source and start configuration. The problem seems to be that the configure script is looking for a pkg-config file named 'apr-1.pc'. The apache 2.2 port does not appear to create a .pc file for the apr-1 utility. I can see that the apr-1 headers, libs and util are installed by doing a 'pkg_info -L apache\* | grep apr-1'. Anyone have any ideas? Thanks, Erik Van Benschoten P.S. Here's the Makefile for those interested: # New ports collection makefile for: mod_dnssd # Date created: 22 December 2008 # PORTNAME= mod_dnssd PORTVERSION= 0.5 CATEGORIES= www MASTER_SITES= http://0pointer.de/lennart/projects/mod_dnssd/ MAINTAINER= COMMENT= Zeroconf support using Avahi for the Apache2 webserver USE_APACHE= 20+ GNU_CONFIGURE= yes CONFIGURE_ARGS= --with-apxs=${APXS} # mod_dnssd requires a current release of Apache 2.2 with apxs and a # development installation of Avahi 0.6 or newer. #LIB_DEPENDS+= avahi-client:${PORTSDIR}/net/avahi-app .include From mitya at cabletv.dp.ua Tue Dec 23 05:49:16 2008 From: mitya at cabletv.dp.ua (Mitya) Date: Tue Dec 23 05:49:23 2008 Subject: graphics/sane-backends Message-ID: <4950E54B.6000109@cabletv.dp.ua> --- include/sane/sanei_tcp.h.orig 2006-12-01 01:23:19.000000000 +0200 +++ include/sane/sanei_tcp.h 2008-12-23 15:11:05.456497255 +0200 @@ -22,6 +22,9 @@ #include #include +#include +#include +#include extern SANE_Status sanei_tcp_open(const char *host, int port, int *fdp); extern void sanei_tcp_close(int fd); # cat patch-sanei_tcp.h From varga.michal at gmail.com Tue Dec 23 10:00:10 2008 From: varga.michal at gmail.com (Michal Varga) Date: Tue Dec 23 10:00:17 2008 Subject: linux-enemyterritory In-Reply-To: <7d6fde3d0812221648k6d99d0acsa0d13c96193f8417@mail.gmail.com> References: <200812230033.43040.g.martinez@pcbsd.es> <7d6fde3d0812221648k6d99d0acsa0d13c96193f8417@mail.gmail.com> Message-ID: <3f1fd1ea0812230938q6187ed1am26b33499f07bc295@mail.gmail.com> On Tue, Dec 23, 2008 at 1:48 AM, Garrett Cooper wrote: > On 12/22/08, Gonzalo Mart?nez-Sanjuan S?nchez wrote: >> Hi there! >> >> I have a problem with the enemyterritory port using linux compat layer. The >> game has no sound. The only problem I get its this messagge: >> >> ------- sound initialization ------- >> /dev/dsp: Invalid argument >> Could not mmap /dev/dsp >> ------------------------------------ >> >> Have someone any other problem like that??? >> Is that somekind of already known bug? >> Yep, for a long time, sort of. Though I haven't been playing ET for quite a while, I'm pretty positive that the patch linked here will solve your problem, hopefuly it can still be applied cleanly these days: http://lists.freebsd.org/pipermail/freebsd-current/2007-June/073454.html Dunno why it never got commited/properly fixed, maybe you can push someone to finish it this time :) m. From c0nsumer at nuxx.net Tue Dec 23 13:18:33 2008 From: c0nsumer at nuxx.net (Steve Vigneau) Date: Tue Dec 23 13:18:39 2008 Subject: FreeBSD Port: lighttpd-1.4.20 Message-ID: Hey there... I'd recently delt with a problem with lighttpd on FreeBSD 7.0-RELEASE SMP where, when using PHP as a FastCGI, the php-cgi process would occasionally hang with a status of sbwait. This blog post covers it (http://nuxx.net/blog/2008/11/18/php-cgi-hung-as-sbwait-with-lighttpd-on-freebsd/), and it turns out the fix (http://redmine.lighttpd.net/boards/2/topics/show/141) is to set the option server.network-backend to "writev". Since you are the maintainer of the port, I thought that you'd like to know about this and possibly make the change in the port. This setting was fine at its default of "write" on FreeBSD 6.2, but not any more. Thanks very much! -Steve From dougb at FreeBSD.org Tue Dec 23 14:05:46 2008 From: dougb at FreeBSD.org (Doug Barton) Date: Tue Dec 23 14:05:52 2008 Subject: proposal: add --disable-tests to www/firefox3 port In-Reply-To: <49504D4B.8040402@gmail.com> References: <49504D4B.8040402@gmail.com> Message-ID: <49515A77.3050204@FreeBSD.org> Eitan Adler wrote: > ac_add_options --disable-tests > By default, many auxiliary test applications are built, which can > help debug and patch the mozilla source. Disabling these tests can speed > build time and reduce disk space considerably [1] > > Most users don't need these tests built unless they plan on helping > debug and patch the mozilla source. > > I think we should add it to MOZ_OPTIONS in www/firefox3. If it exists > for firefox2 I propose adding it to firefox2 as well (especially since > firefox2 is going to be EOL soon). > > [1] https://developer.mozilla.org/en/Configuring_Build_Options Perhaps this could be part of the WITH_DEBUG option? Doug -- This .signature sanitized for your protection From yanefbsd at gmail.com Tue Dec 23 14:20:06 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Tue Dec 23 14:20:13 2008 Subject: proposal: add --disable-tests to www/firefox3 port In-Reply-To: <49515A77.3050204@FreeBSD.org> References: <49504D4B.8040402@gmail.com> <49515A77.3050204@FreeBSD.org> Message-ID: On Dec 23, 2008, at 13:39, Doug Barton wrote: > Eitan Adler wrote: >> ac_add_options --disable-tests >> By default, many auxiliary test applications are built, which can >> help debug and patch the mozilla source. Disabling these tests can >> speed >> build time and reduce disk space considerably [1] >> >> Most users don't need these tests built unless they plan on helping >> debug and patch the mozilla source. >> >> I think we should add it to MOZ_OPTIONS in www/firefox3. If it >> exists >> for firefox2 I propose adding it to firefox2 as well (especially >> since >> firefox2 is going to be EOL soon). >> >> [1] https://developer.mozilla.org/en/Configuring_Build_Options > > Perhaps this could be part of the WITH_DEBUG option? > > Doug I agree with Doug. -Garrett From eitanadlerlist at gmail.com Tue Dec 23 16:09:42 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Tue Dec 23 16:09:48 2008 Subject: proposal: add --disable-tests to www/firefox3 port In-Reply-To: References: <49504D4B.8040402@gmail.com> <49515A77.3050204@FreeBSD.org> Message-ID: <49517DB4.1060704@gmail.com> >> Perhaps this could be part of the WITH_DEBUG option? Like this? --- firefox3/Makefile 2008-12-19 15:13:01.000000000 -0500 +++ firefox-new/Makefile 2008-12-23 19:07:09.000000000 -0500 @@ -57,6 +57,10 @@ .include +.if defined(WITHOUT_DEBUG) +MOZ_OPTIONS+= --disable-tests +.endif + GECKO_PTHREAD_LIBS!=${CC} -dumpspecs | ${GREP} -m 1 '%{\!pg: %{pthread:' | ${SED} -e 's|^.*%{\!pg: %{pthread:|| ; s|}.*$$||' || ${TRUE} Also WARN: Makefile: [SMB is listed in OPTIONS, but neither WITH_SMB nor WITHOUT_SMB appears.]: WARN: Makefile: [LOGGING is listed in OPTIONS, but neither WITH_LOGGING nor WITHOUT_LOGGING appears.]: WARN: Makefile: [OPTIMIZED_CFLAGS is listed in OPTIONS, but neither WITH_OPTIMIZED_CFLAGS nor WITHOUT_OPTIMIZED_CFLAGS appears.]: Are they used at all? should they just be removed? -- Eitan Adler GNU Key fingerprint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 From yanefbsd at gmail.com Tue Dec 23 18:29:58 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Tue Dec 23 18:30:04 2008 Subject: proposal: add --disable-tests to www/firefox3 port In-Reply-To: <49517DB4.1060704@gmail.com> References: <49504D4B.8040402@gmail.com> <49515A77.3050204@FreeBSD.org> <49517DB4.1060704@gmail.com> Message-ID: <2DD9A4BD-EFFF-482F-90DA-F9078229539A@gmail.com> On Dec 23, 2008, at 16:09, Eitan Adler wrote: >>> Perhaps this could be part of the WITH_DEBUG option? > Like this? > --- firefox3/Makefile 2008-12-19 15:13:01.000000000 -0500 > +++ firefox-new/Makefile 2008-12-23 19:07:09.000000000 -0500 > @@ -57,6 +57,10 @@ > > .include > > +.if defined(WITHOUT_DEBUG) > +MOZ_OPTIONS+= --disable-tests > +.endif > + > GECKO_PTHREAD_LIBS!=${CC} -dumpspecs | ${GREP} -m 1 '%{\!pg: > %{pthread:' | ${SED} -e 's|^.*%{\!pg: %{pthread:|| ; s|}.*$$||' || $ > {TRUE} > > Also > WARN: Makefile: [SMB is listed in OPTIONS, but neither WITH_SMB nor > WITHOUT_SMB appears.]: > WARN: Makefile: [LOGGING is listed in OPTIONS, but neither > WITH_LOGGING > nor WITHOUT_LOGGING appears.]: > WARN: Makefile: [OPTIMIZED_CFLAGS is listed in OPTIONS, but neither > WITH_OPTIMIZED_CFLAGS nor WITHOUT_OPTIMIZED_CFLAGS appears.]: > > Are they used at all? should they just be removed? > > -- > Eitan Adler > GNU Key fingerprint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 Looks good. The suggestion to remove those flags first warrants checking the mozilla include makefile. Cheers, -Garrett From perryh at pluto.rain.com Wed Dec 24 03:38:18 2008 From: perryh at pluto.rain.com (perryh@pluto.rain.com) Date: Wed Dec 24 03:38:28 2008 Subject: vpnc connects, but does not work Message-ID: <49521954.BcMAlOlPOLu7CRKx%perryh@pluto.rain.com> I have installed vpnc to connect to an employer's Cisco VPN system, and it seems to make the connection, but after connecting I can't ping the gateway nor anything beyond it. The symptom seems to resemble what is described in the Routing section of http://www.cs.rpi.edu/~flemej/fbsd-cisco-vpn.pdf, but since that is using a completely different setup on the FreeBSD side I have no idea whether the remedy described there is applicable (nor, if it is, how to determine the addresses to use in this case). Does this look at all familiar to anyone? I didn't find anything that seemed applicable in recent ports@ or questions@ archives. (I have XX'd out potentially-sensitive material in the following.) # /usr/local/sbin/vpnc Enter password for XXX@XXX.XXX.com: Connect Banner: | *** XXX, Inc. Authorized Use Only *** add host YYY.YYY.127.228: gateway 192.168.200.254 add net ZZZ.ZZZ.0.0: gateway ZZZ.ZZZ.233.42 add net ZZZ.ZZZ.57.128: gateway ZZZ.ZZZ.233.42 add net ZZZ.ZZZ.57.133: gateway ZZZ.ZZZ.233.42 VPNC started in background (pid: 24776)... The addresses in those last two "add net" lines seem to be the nameservers: $ cat /etc/resolv.conf #@VPNC_GENERATED@ -- this file is generated by vpnc # and will be overwritten by vpnc # as long as the above mark is intact nameserver ZZZ.ZZZ.57.128 nameserver ZZZ.ZZZ.57.133 search XXX.com which leads me to wonder whether they really ought to be "add host" -- for that matter it's not clear they're needed at all since they should be covered by the "add net ZZZ.ZZZ.0.0" -- but I guess that may not make much difference when I can't even ping my own gateway (tun0) address :( $ ping ZZZ.ZZZ.233.42 PING ZZZ.ZZZ.233.42 (ZZZ.ZZZ.233.42): 56 data bytes ^C --- ZZZ.ZZZ.233.42 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss $ ping ZZZ.ZZZ.57.128 PING ZZZ.ZZZ.57.128 (ZZZ.ZZZ.57.128): 56 data bytes ^C --- ZZZ.ZZZ.57.128 ping statistics --- 10 packets transmitted, 0 packets received, 100% packet loss $ ping ZZZ.ZZZ.57.133 PING ZZZ.ZZZ.57.133 (ZZZ.ZZZ.57.133): 56 data bytes ^C --- ZZZ.ZZZ.57.133 ping statistics --- 27 packets transmitted, 0 packets received, 100% packet loss $ ifconfig -a xl0: flags=8843 mtu 1500 options=9 inet6 fe80::2b0:d0ff:fe28:ad4f%xl0 prefixlen 64 scopeid 0x1 inet 192.168.200.61 netmask 0xffffff00 broadcast 192.168.200.255 ether 00:b0:d0:28:ad:4f media: Ethernet autoselect (10baseT/UTP) status: active plip0: flags=108810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 tun0: flags=8051 mtu 1412 inet6 fe80::2b0:d0ff:fe28:ad4f%tun0 prefixlen 64 scopeid 0x4 inet ZZZ.ZZZ.233.42 --> ZZZ.ZZZ.233.42 netmask 0xffffffff Opened by PID 24635 Meanwhile I _can_ ping YYY.YYY.127.228, which I guess is the concentrator's public IP address: $ ping YYY.YYY.127.228 PING YYY.YYY.127.228 (YYY.YYY.127.228): 56 data bytes 64 bytes from YYY.YYY.127.228: icmp_seq=0 ttl=116 time=53.226 ms 64 bytes from YYY.YYY.127.228: icmp_seq=1 ttl=116 time=52.982 ms 64 bytes from YYY.YYY.127.228: icmp_seq=2 ttl=116 time=53.130 ms ^C --- YYY.YYY.127.228 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 52.982/53.113/53.226/0.100 ms $ netstat -r -n Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.200.254 UGS 0 2209723 xl0 127.0.0.1 127.0.0.1 UH 0 2 lo0 ZZZ.ZZZ ZZZ.ZZZ.233.42 UGS 0 0 tun0 ZZZ.ZZZ.57.128/32 ZZZ.ZZZ.233.42 UGS 0 19 tun0 ZZZ.ZZZ.57.133/32 ZZZ.ZZZ.233.42 UGS 0 18 tun0 ZZZ.ZZZ.233.42 ZZZ.ZZZ.233.42 UH 59 20 tun0 YYY.YYY.127/27 ZZZ.ZZZ.233.42 UGS 0 0 tun0 YYY.YYY.127.96/27 ZZZ.ZZZ.233.42 UGS 0 0 tun0 YYY.YYY.127.224/27 ZZZ.ZZZ.233.42 UGS 0 0 tun0 YYY.YYY.127.228 192.168.200.254 UGHS 0 106 xl0 192.168.200 link#1 UC 0 0 xl0 192.168.200.254 00:09:5b:a1:c8:9e UHLW 3 4318078 xl0 1148 192.168.200.255 ff:ff:ff:ff:ff:ff UHLWb 1 3 xl0 From romain at blogreen.org Wed Dec 24 05:10:21 2008 From: romain at blogreen.org (Romain =?iso-8859-1?Q?Tarti=E8re?=) Date: Wed Dec 24 05:10:28 2008 Subject: TeXLive Message-ID: <20081224131012.GA8392@blogreen.org> Hi! There have been numerous mails about adding ports for TeXLive to FreeBSD [1,2,3,4], unfortunately, nothing is available so far. Since I really think TeXLive can be a plus for FreeBSD, and because I use TeXLive on another system, I started another effort to bring it to the ports tree. In order to avoid loosing everything if I run out of time, I created a Google code project for working: http://code.google.com/p/freebsd-texlive/ Currently, I have all TeXLive binaries compiling from source (installation is still not perfect though) and quite a precise idea of how all TeXLive distfiles are organised and how to build FreeBSD ports from the metadata they enclose (refer to the project's wiki for details, I am trying to dump all there [5]). I am now facing the problem of the organisation of the ports to create. The freebsd-ports archives reveal some interesting points: 1. TeXLive should be very modular It is then possible to run a version of XeTeX more recent then the one provided with TeXLive (i.e. compile TeXLive --without-xetex and depend on a port print/xetex-devel). 2. TeXLive should be provided as 3-4 packages just like teTeX It is the way teTeX fits in the FreeBSD ports tree, and TeXLive is then kind-of a drop-in replacement of teTeX. 3. TeXLive should be provided as ~10 packages TeXLive is too big to be included as just 3-4 packages, but splitting everything will create 100's of ports and this will be a mess. So group all in say 10 ports and it will be a good compromise. 4. TeXLive should be provided as many many small packages If I need a package, I don't want to install a set of thousands of packages to have it: I just want it to be available and install it. If we consider that ports are build from source, it important to know that TeXLive provide a single tarball for all applications binaries source code. All the rest (macros, fonts, etc.) is provided as a lot of small tarball. As a consequence, I see #1 as ? Split the applications ?, and #2, #3 and #4 as ? Split the rest ?. But maybe the question is more about ? Split both ?. For now, I do not intend to make the port that install all binaries a meta-port (so no #1). It is quite huge and complex, include modified version of libraries that are statically linked to the binaries, ... well, I don't want to spend time on this right now (maybe in the future but unsure ? However, contributions are welcomed). Splitting the rest (#2, #3, #4) is another problem: I am convinced that is is important to have very low granularity for experienced users: as an unexperienced TeX user, I would need this, so I guess that anybody with more skills than I have will think the same. But having a lot of ports does not necessarily leads to complexity to beginners, since we can provide meta-ports (just like Xorg). The big picture: TeXLive provide 5229 packages ... Well... We can remove more than 1200 packages of binaries for various platforms, and there is still distfiles related to the TeXLive installation system that are not needed on FreeBSD. So basically, we have 4000 distfiles to arrange in ports. Some of the distfiles are sort of meta-packages, this helps grouping [5, Categories]. Here are some ports organisation possibilities: 1. One port per Scheme (10 ports) + very few ports; - low granularity; - each port conflict with others. 2. One port per Collection (84 ports) + One meta-port per Scheme (10 Meta-ports) + no conflict (AFAIK); - low granularity. 3. One port per Package, grouping related packages (e.g. foo, foo.source and foo.doc) (/[0-9]{4}/ ports) + meta-port for Collections (84 meta-ports) + meta-port for Scheme (10 meta-ports) + high granularity; + no conflict; - many ports. 4. Same as #3 without grouping packages + highest granularity; - many many ports. I am in favor of #3 since it allows TeXLive users to install a basic set that fit their needs (a beginner will install the full scheme meta-package and have everything, another will choose a minimal scheme, another will directory install the collections he wants, it is possible to install a particular package without installing loads of other packages (say you have a document that use svninfo for example and you don't have / want collection-latexextra)). I would however be pleased to read what teTeX/TeXLive [future] users think about all this. With kind regards, Romain References: 1. http://lists.freebsd.org/pipermail/freebsd-ports/2007-July/042729.html 2. http://lists.freebsd.org/pipermail/freebsd-ports/2007-December/045860.html 3. http://lists.freebsd.org/pipermail/freebsd-questions/2007-October/161492.html 4. http://lists.freebsd.org/pipermail/freebsd-advocacy/2003-November/000705.html 5. http://code.google.com/p/freebsd-texlive/wiki/source -- Romain Tarti?re http://romain.blogreen.org/ pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081224/e4869941/attachment.pgp From QAT at FreeBSD.org Wed Dec 24 05:19:14 2008 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Wed Dec 24 05:19:31 2008 Subject: cvs commit: ports/archivers/xmill Makefile distinfo pkg-descr ports/archivers/xmill/files patch-XMill+BZlib.cpp patch-makefile patch-src::Main.cpp patch-src::ZLib.cpp In-Reply-To: <200812241309.mBOD9ZQL097559@repoman.freebsd.org> References: In-Reply-To: <200812241309.mBOD9ZQL097559@repoman.freebsd.org> Message-ID: <20081224131911.B705A12E43D3@quark.ds9.tecnik93.com> Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/xmill-0.8.log : building xmill-0.8 in directory /var/tinderbox/7-STABLE-FTP maintained by: ports@FreeBSD.org building for: 7.1-PRERELEASE amd64 port directory: /usr/ports/archivers/xmill Makefile ident: $FreeBSD: ports/archivers/xmill/Makefile,v 1.13 2008/12/24 13:09:34 danfe Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Wed Dec 24 13:18:10 UTC 2008 ................................................... => Attempting to fetch from http://nchc.dl.sourceforge.net/sourceforge/xmill/. xmill-0.8.zip 3039 kB 54 kBps => MD5 Checksum OK for xmill-0.8.zip. => SHA256 Checksum OK for xmill-0.8.zip. ================================================================ ======================================== add_pkg unzip-5.52_5.tbz adding dependencies pkg_add unzip-5.52_5.tbz ===> Extracting for xmill-0.8 => MD5 Checksum OK for xmill-0.8.zip. => SHA256 Checksum OK for xmill-0.8.zip. ===> xmill-0.8 depends on executable: unzip - found Deleting unzip-5.52_5 ================================================================ ======================================== add_pkg ===> Patching for xmill-0.8 ===> Converting DOS text file to UNIX text file: ===> Applying FreeBSD patches for xmill-0.8 ================================================================ ======================================== add_pkg unzip-5.52_5.tbz adding dependencies pkg_add unzip-5.52_5.tbz ===> Configuring for xmill-0.8 ===> Building for xmill-0.8 c++ -o ./tmp/realmain.o -O2 -fno-strict-aliasing -pipe -c -w -DXMILL -IXMill -Ippmdi ./XMill/realmain.cpp c++ -o ./tmp/Options.o -O2 -fno-strict-aliasing -pipe -c -w -DXMILL -IXMill -Ippmdi ./XMill/Options.cpp c++ -o ./tmp/CompressMan.o -O2 -fno-strict-aliasing -pipe -c -w -DXMILL -IXMill -Ippmdi ./XMill/CompressMan.cpp ./XMill/CompressMan.cpp: In member function 'void BothCompressMan::DebugPrint()': ./XMill/CompressMan.cpp:426: error: cast from 'UserCompressorFactory*' to 'unsigned int' loses precision *** Error code 1 Stop in /work/a/ports/archivers/xmill/work/xmill. *** Error code 1 Stop in /a/ports/archivers/xmill. ================================================================ build of /usr/ports/archivers/xmill ended at Wed Dec 24 13:19:10 UTC 2008 A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From shuvaev at physik.uni-wuerzburg.de Wed Dec 24 06:21:04 2008 From: shuvaev at physik.uni-wuerzburg.de (Alexey Shuvaev) Date: Wed Dec 24 06:21:11 2008 Subject: TeXLive In-Reply-To: <20081224131012.GA8392@blogreen.org> References: <20081224131012.GA8392@blogreen.org> Message-ID: <20081224142101.GA62046@wep4035.physik.uni-wuerzburg.de> On Wed, Dec 24, 2008 at 02:10:12PM +0100, Romain Tarti?re wrote: > Hi! > > There have been numerous mails about adding ports for TeXLive to FreeBSD > [1,2,3,4], unfortunately, nothing is available so far. > > > Since I really think TeXLive can be a plus for FreeBSD, and because I > use TeXLive on another system, I started another effort to bring it to > the ports tree. In order to avoid loosing everything if I run out of > time, I created a Google code project for working: > > http://code.google.com/p/freebsd-texlive/ > Nice! > > Some of the distfiles are sort of meta-packages, this helps grouping > [5, Categories]. Here are some ports organisation possibilities: > > 1. One port per Scheme (10 ports) > + very few ports; > - low granularity; > - each port conflict with others. > > 2. One port per Collection (84 ports) + One meta-port per Scheme (10 > Meta-ports) > + no conflict (AFAIK); > - low granularity. > > 3. One port per Package, grouping related packages (e.g. foo, > foo.source and foo.doc) (/[0-9]{4}/ ports) + meta-port for > Collections (84 meta-ports) + meta-port for Scheme (10 meta-ports) > + high granularity; > + no conflict; > - many ports. > > 4. Same as #3 without grouping packages > + highest granularity; > - many many ports. > > > I am in favor of #3 since it allows TeXLive users to install a basic set > that fit their needs (a beginner will install the full scheme > meta-package and have everything, another will choose a minimal scheme, > another will directory install the collections he wants, it is possible > to install a particular package without installing loads of other > packages (say you have a document that use svninfo for example and you > don't have / want collection-latexextra)). > > I would however be pleased to read what teTeX/TeXLive [future] users > think about all this. > As a current teTeX and Xorg user, I like your choice #3. As a little note, you can consider sub-splitting Package port into 'meat' part (always installed), documentation, examples, etc. (controlled by NOPORTDOCS, NOPORTEXAMPLES, etc. variables set by the end user). So, it is still one FreeBSD port, but user can choose whether to install doc and so on, or not. Just FYI, debian seems to have chosen something between #1 and #2: ~> grep ^texlive allpackages | wc 93 775 7736 Just my 0.02$, Alexey. From romain at blogreen.org Wed Dec 24 07:18:30 2008 From: romain at blogreen.org (Romain =?iso-8859-1?Q?Tarti=E8re?=) Date: Wed Dec 24 07:18:39 2008 Subject: TeXLive In-Reply-To: <20081224142101.GA62046@wep4035.physik.uni-wuerzburg.de> References: <20081224131012.GA8392@blogreen.org> <20081224142101.GA62046@wep4035.physik.uni-wuerzburg.de> Message-ID: <20081224151828.GA12100@blogreen.org> On Wed, Dec 24, 2008 at 03:21:01PM +0100, Alexey Shuvaev wrote: > On Wed, Dec 24, 2008 at 02:10:12PM +0100, Romain Tarti?re wrote: > > 3. One port per Package, grouping related packages (e.g. foo, > > foo.source and foo.doc) (/[0-9]{4}/ ports) + meta-port for > > Collections (84 meta-ports) + meta-port for Scheme (10 meta-ports) > > + high granularity; > > + no conflict; > > - many ports. > As a current teTeX and Xorg user, I like your choice #3. > As a little note, you can consider sub-splitting Package port into 'meat' part > (always installed), documentation, examples, etc. (controlled by > NOPORTDOCS, NOPORTEXAMPLES, etc. variables set by the end user). > So, it is still one FreeBSD port, but user can choose whether to install > doc and so on, or not. Yup! This is already planned this way in bsd.texlive.mk [1]. > Just FYI, debian seems to have chosen something between #1 and #2: > ~> grep ^texlive allpackages | wc > 93 775 7736 I will have a look at it! Thanks! Romain References: 1. http://code.google.com/p/freebsd-texlive/source/browse/trunk/print/texlive/bsd.texlive.mk -- Romain Tarti?re http://romain.blogreen.org/ pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081224/3704912f/attachment.pgp From hrs at FreeBSD.org Wed Dec 24 07:38:10 2008 From: hrs at FreeBSD.org (Hiroki Sato) Date: Wed Dec 24 07:38:16 2008 Subject: TeXLive In-Reply-To: <20081224131012.GA8392@blogreen.org> References: <20081224131012.GA8392@blogreen.org> Message-ID: <20081225.003246.131998417.hrs@allbsd.org> Romain Tarti?re wrote in <20081224131012.GA8392@blogreen.org>: ro> Hi! ro> ro> There have been numerous mails about adding ports for TeXLive to FreeBSD ro> [1,2,3,4], unfortunately, nothing is available so far. ro> ro> ro> Since I really think TeXLive can be a plus for FreeBSD, and because I ro> use TeXLive on another system, I started another effort to bring it to ro> the ports tree. In order to avoid loosing everything if I run out of ro> time, I created a Google code project for working: ro> ro> http://code.google.com/p/freebsd-texlive/ ro> ro> ro> Currently, I have all TeXLive binaries compiling from source ro> (installation is still not perfect though) and quite a precise idea of ro> how all TeXLive distfiles are organised and how to build FreeBSD ports ro> from the metadata they enclose (refer to the project's wiki for details, ro> I am trying to dump all there [5]). ro> ro> ro> I am now facing the problem of the organisation of the ports to create. ro> The freebsd-ports archives reveal some interesting points: I am the one who were saying the porting was going, and sorry for being out of touch with public lists, but the points include not only how to import them to our ports tree but also how to integrate them with the large number of ports depending TeX. The reasons why I could not import them so far are: 1) some remaining issues could not be solved until the last month and 2) I need to wait for the recent releases being rolled out (much-delayed, as you know). I have three sort of experimental ports of texlive now; the first is a large one, the second is completely-modularized one, and the last is a combination of modularized binaries and macro part in a few ports with scripts to interface CTAN between the installed macros. Considering migration from teTeX, I am planning to commit a part of 1) just after 7.1R is rolled out, then break them, and finally form them into 3). This integration involves many other ports which depend on TeX, and probably the new category named "tex". Also, we are using TeX in our documentation infrastructure, so updating the related ports are very sensitive. I think discussion of the organization in the ports tree would be a good thing, but please also consider this factor; for example, if we are not able to make JadeTeX work as before we need to solve the issue first, and we have solve the current situation that we have print/tex independent from the old teTeX, which often confuses the users. Anyway, I think major technical issues (functionality, compatibility, and so on) are solved now while a large change is needed to TeX-related ports in the current ports tree. And I think unless we are sure that these points and long-standing complaints which exist from the teTeX era can be solved, it should not be imported. Again, please accept my sincere apologies for your inconvenience of missing TeXLive in FreeBSD for a long time. I do not want to make others do duplicated work and conflict with other efforts, but at the same time I have no right to bothering your effort. This is my comment at this moment as one of people who are involved. -- | Hiroki SATO -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081224/cfd6f11e/attachment.pgp From romain at blogreen.org Wed Dec 24 08:19:28 2008 From: romain at blogreen.org (Romain =?iso-8859-1?Q?Tarti=E8re?=) Date: Wed Dec 24 08:19:41 2008 Subject: TeXLive In-Reply-To: <20081225.003246.131998417.hrs@allbsd.org> References: <20081224131012.GA8392@blogreen.org> <20081225.003246.131998417.hrs@allbsd.org> Message-ID: <20081224161925.GA28946@blogreen.org> On Thu, Dec 25, 2008 at 12:32:46AM +0900, Hiroki Sato wrote: > Romain Tarti?re wrote > in <20081224131012.GA8392@blogreen.org>: > > ro> There have been numerous mails about adding ports for TeXLive to FreeBSD > ro> [1,2,3,4], unfortunately, nothing is available so far. > > I am the one who were saying the porting was going, and sorry for > being out of touch with public lists, but the points include not only > how to import them to our ports tree but also how to integrate them > with the large number of ports depending TeX. Well, I don't think of importing TeXLive into the FreeBSD ports tree as a replacement of teTeX (sorry if that was unclear by what I meant by "drop-in replacement"). I was just thinking about having both in the ports tree, leaving existing dependencies untouched so that ports that used to depend on teTeX still depend on it... TeXLive would only be installed if the user explicitly want TeXLive instead of teTeX. > The reasons why I could not import them so far are: 1) some remaining > issues could not be solved until the last month and 2) I need to wait > for the recent releases being rolled out (much-delayed, as you know). Err... Well in fact I am not a *TeX* addict... Just an user: I have a document I started to typeset on Windows with TeXLive and it don't compile on FreeBSD's teTeX (too old macros I guess)... I just want to continue this document. Porting TeXLive is a need, not a goal :-) SO no, I was not aware that another release was imminent. > I have three sort of experimental ports of texlive now; the first is > a large one, the second is completely-modularized one, and the last > is a combination of modularized binaries and macro part in a few > ports with scripts to interface CTAN between the installed macros. > Considering migration from teTeX, I am planning to commit a part of > 1) just after 7.1R is rolled out, then break them, and finally form > them into 3). This sounds cool! > This integration involves many other ports which depend on TeX, and > probably the new category named "tex". Also, we are using TeX in our > documentation infrastructure, so updating the related ports are very > sensitive. I think discussion of the organization in the ports tree > would be a good thing, but please also consider this factor; for > example, if we are not able to make JadeTeX work as before we need to > solve the issue first, and we have solve the current situation that > we have print/tex independent from the old teTeX, which often > confuses the users. Anyway, I think major technical issues > (functionality, compatibility, and so on) are solved now while a > large change is needed to TeX-related ports in the current ports > tree. And I think unless we are sure that these points and > long-standing complaints which exist from the teTeX era can be > solved, it should not be imported. As I just explained, maybe teTeX and TeXLive can co-exist for a while? > Again, please accept my sincere apologies for your inconvenience of > missing TeXLive in FreeBSD for a long time. I do not want to make > others do duplicated work and conflict with other efforts, but at the > same time I have no right to bothering your effort. This is my > comment at this moment as one of people who are involved. Maybe having the TeXLive work available publicly may help people who want TeXLive on FreeBSD to merge it into their ports-tree, give more visibility to the porting effort, then contributions may arrive... It's the way we try to handle the BSD# Project [1] that aims to update all Mono related stuff for FreeBSD. Individuals who are looking for bleeding-edge .NET support in FreeBSD can access a ports tree that will make them happy, even if they now it might be broken. Kind regards, Romain References: 1. http://code.google.com/p/bsd-sharp/ -- Romain Tarti?re http://romain.blogreen.org/ pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081224/768c10de/attachment.pgp From amdmi3 at amdmi3.ru Wed Dec 24 10:02:16 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Wed Dec 24 10:02:24 2008 Subject: proposal: add --disable-tests to www/firefox3 port In-Reply-To: <49517DB4.1060704@gmail.com> References: <49504D4B.8040402@gmail.com> <49515A77.3050204@FreeBSD.org> <49517DB4.1060704@gmail.com> Message-ID: <20081224171413.GA57137@hades.panopticon> * Eitan Adler (eitanadlerlist@gmail.com) wrote: I'd suggest -+.if defined(WITHOUT_DEBUG) ++.if !defined(WITH_DEBUG) DEBUG knob is assumed to defauly to false, this WITH_DEBUG is checked everywhere. See `grep -R _DEBUG /usr/ports/Mk` -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From talon at lpthe.jussieu.fr Wed Dec 24 11:43:47 2008 From: talon at lpthe.jussieu.fr (Michel Talon) Date: Wed Dec 24 11:43:54 2008 Subject: TeXLive Message-ID: <20081224194343.GA37842@lpthe.jussieu.fr> Romain Tarti?re wrote: > Well, I don't think of importing TeXLive into the FreeBSD ports tree as > a replacement of teTeX (sorry if that was unclear by what I meant by > "drop-in replacement"). I was just thinking about having both in the > ports tree, leaving existing dependencies untouched so that ports that > used to depend on teTeX still depend on it... TeXLive would only be > installed if the user explicitly want TeXLive instead of teTeX. I concur with that, as a TeX user since many years. For me teTeX is already overbloated as far as possible, particularly when some unconscious maintainer adds dependencies like cm-super which are perfectly non necessary, please don't impose on us abominations like TeXLive, leave that optional. -- Michel TALON From nikola.lecic at anthesphoria.net Wed Dec 24 14:30:40 2008 From: nikola.lecic at anthesphoria.net (Nikola =?UTF-8?B?TGXEjWnEhw==?=) Date: Wed Dec 24 14:30:49 2008 Subject: TeXLive In-Reply-To: <20081224131012.GA8392@blogreen.org> References: <20081224131012.GA8392@blogreen.org> Message-ID: <20081224232607.43ea938a@anthesphoria.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Hello Romain, Thank you for the interesting analysis and for renewing the discussion about TeXLive on FreeBSD. On Wed, 24 Dec 2008 14:10:12 +0100 Romain Tarti?re wrote: [...] > 1. TeXLive should be very modular > > It is then possible to run a version of XeTeX more recent > then the one provided with TeXLive (i.e. compile TeXLive > --without-xetex and depend on a port print/xetex-devel). [...] > If we consider that ports are build from source, it important to know > that TeXLive provide a single tarball for all applications binaries > source code. All the rest (macros, fonts, etc.) is provided as a lot > of small tarball. As a consequence, I see #1 as ? Split the > applications ?, and #2, #3 and #4 as ? Split the rest ?. But maybe > the question is more about ? Split both ?. > > For now, I do not intend to make the port that install all binaries a > meta-port (so no #1). It is quite huge and complex, include modified > version of libraries that are statically linked to the binaries, ... > well, I don't want to spend time on this right now (maybe in the > future but unsure ? However, contributions are welcomed). (I am the one who wrote #1.) What do you exactly mean by making a meta-port for binaries? To make a port for every binary group provided in their source tree? Sounds interesting, although what I meant there was to use the internal TeXLive build options, such as --without-xetex, so it's basically as simple as any of WITH_* options used in thousands of existing ports. > 3. One port per Package, grouping related packages (e.g. foo, > foo.source and foo.doc) (/[0-9]{4}/ ports) + meta-port for > Collections (84 meta-ports) + meta-port for Scheme (10 meta-ports) > + high granularity; > + no conflict; > - many ports. The main thing with TeXLive is that they make releases once a year. My opinion is that if we just stick with their releases -- we don't need any fine-grained work because such year-long cemented code somehow contradicts the idea of FreeBSD's flexible ports. The idea is to provide porters a flexible TeXLive base that can be enriched with many TeX-related projects that are not included in current TeXLive distribution (new and updated LaTeX packages, new versions of TeX extensions, etc). Once an initial TeXLive ports structure is committed, I'd like to see many porters grabbing parts of their particular areas of interest (or creating -devel ports) in order to provide users with versions newer than those initially included. It seems to me that your your proposal #3 supports this approach. Best regards. - -- Nikola Le?i? = ?????? ????? fingerprint : FEF3 66AF C90E EDC3 D878 7CDC 956D F4AB A377 1C9B ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iJwEAQEDAAYFAklStwQACgkQ/MM/0rYIoZiFhQQApUO7pofWE19GskMfQ34GRWSQ f5+AKlGvf2JKcMpB9Z0eq3aksIhxYFESAMwoEdWd+g0Z4gkyE9NdA4RCGflASahM yaqnLsf8Ri2C0QcXbUdgufE49Yw1coGOkPT3TklB5NL2TVY+2PGJ/FfnxznU7pNY CdeiNOZicsIRXfyUV/Q= =lp2b -----END PGP SIGNATURE----- From nikola.lecic at anthesphoria.net Wed Dec 24 14:40:44 2008 From: nikola.lecic at anthesphoria.net (Nikola =?UTF-8?B?TGXEjWnEhw==?=) Date: Wed Dec 24 14:40:55 2008 Subject: TeXLive In-Reply-To: <20081225.003246.131998417.hrs@allbsd.org> References: <20081224131012.GA8392@blogreen.org> <20081225.003246.131998417.hrs@allbsd.org> Message-ID: <20081224233612.233d3d85@anthesphoria.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On Thu, 25 Dec 2008 00:32:46 +0900 (JST) Hiroki Sato wrote: > I have three sort of experimental ports of texlive now; the first is > a large one, the second is completely-modularized one, and the last > is a combination of modularized binaries and macro part in a few > ports with scripts to interface CTAN between the installed macros. Is it possible to download your experimental versions for testing and suggestions before committing? Is it possible to make your work more visible -- as it is the case with many other ongoing FreeBSD projects -- to make a wiki page or something like that? It seems to me that TeXLive project is one of the most secretive FreeBSD projects. There is no need for that since there are many interested future users who might be helpful. :-) Anyway, thank you for your efforts and for the good news. Best wishes. - -- Nikola Le?i? = ?????? ????? fingerprint : FEF3 66AF C90E EDC3 D878 7CDC 956D F4AB A377 1C9B ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iJwEAQEDAAYFAklSuWIACgkQ/MM/0rYIoZjauQQAoclkZ1w//yh69RtTk1M2Lo3X 0l+KLqvxke+5v1crhwjiGpP6mHKbvZDLlseIY8XXfcNJgtj68Pt7t1FztckM70ZX ZFEv2cyFZHZgX85QX7uWiyTQZxbqohnJAIwzyVHYZmff5uDOPf5vk02lqbFxD0/E YfUY2vQUjyOXGDELve0= =Tuyp -----END PGP SIGNATURE----- From romain at blogreen.org Thu Dec 25 00:27:39 2008 From: romain at blogreen.org (Romain =?iso-8859-1?Q?Tarti=E8re?=) Date: Thu Dec 25 00:27:52 2008 Subject: TeXLive In-Reply-To: <20081224232607.43ea938a@anthesphoria.net> References: <20081224131012.GA8392@blogreen.org> <20081224232607.43ea938a@anthesphoria.net> Message-ID: <20081225082732.GA62698@blogreen.org> Hi Nikola! On Wed, Dec 24, 2008 at 11:26:07PM +0100, Nikola Le?i? wrote: > On Wed, 24 Dec 2008 14:10:12 +0100 > Romain Tarti?re wrote: > > [...] > > > 1. TeXLive should be very modular > > > > It is then possible to run a version of XeTeX more recent > > then the one provided with TeXLive (i.e. compile TeXLive > > --without-xetex and depend on a port print/xetex-devel). > > [...] > > > If we consider that ports are build from source, it important to know > > that TeXLive provide a single tarball for all applications binaries > > source code. All the rest (macros, fonts, etc.) is provided as a lot > > of small tarball. As a consequence, I see #1 as ? Split the > > applications ?, and #2, #3 and #4 as ? Split the rest ?. But maybe > > the question is more about ? Split both ?. > > > > For now, I do not intend to make the port that install all binaries a > > meta-port (so no #1). It is quite huge and complex, include modified > > version of libraries that are statically linked to the binaries, ... > > well, I don't want to spend time on this right now (maybe in the > > future but unsure ? However, contributions are welcomed). > > (I am the one who wrote #1.) What do you exactly mean by making a > meta-port for binaries? To make a port for every binary group provided > in their source tree? Sounds interesting, although what I meant there > was to use the internal TeXLive build options, such as --without-xetex, > so it's basically as simple as any of WITH_* options used in thousands > of existing ports. Well, my vision of TeXLive may be wrong (remember that I am just a lower average user of LaTeX), but AFAIK it can be compared to a GNU/Linux distro. You have TeX (the Kernel), and a set of packages. This set of package is a choice of the distribution and has been tested extensively, so installing a distro you are sure to have all pieces working together. So it's just like installing say Debian GNU/Linux: you switch-on a time-travelling machine (your software packages are OLD) _but_ you should not run into trouble with some buggy package. The counterpart of this is less frequent and bigger updates (Debian 4.0 has been updated 6 times since April 2007) while the FreeBSD ports tree has been updated ~60 times yesterday (Okay, this does not include system updates, but I'm speaking about software packages). So the idea is that TeXLive is just a set of TeX, LaTeX, etc. ; TeXLive-2008 being this set of packages at a defined version. So if the ports tree provide these package at that version, it "is" TeXLive-2008. We can therefore consider a port for each piece (TeX, XeTeX, etc.) ... or multiple ports for each piece (AFAICR, you are interested in the latest XeTeX): ports `-> print |-> tex |-> tex-texlive |-> xetex |-> xetex-devel `-> xetex-texlive print/texlive should depend on print/xetex-texlive that provide TeXLive's version of XeTeX (maybe not the latest, maybe patched), but you can have the TeXLive port not depend on it but rather the latest stable or the development version. Then you, don't really have TeXLive because you have a different version of XeTeX, but it is somewhat similar, you know what I mean. So basically, you can apply this example for all the set of applications that compose TeXLive, and you have many *-texlive ports in you ports-tree. A meta-port print/texlive can depend on all of them (with options for building with non-default packages). > > 3. One port per Package, grouping related packages (e.g. foo, > > foo.source and foo.doc) (/[0-9]{4}/ ports) + meta-port for > > Collections (84 meta-ports) + meta-port for Scheme (10 meta-ports) > > + high granularity; > > + no conflict; > > - many ports. > > The main thing with TeXLive is that they make releases once a year. My > opinion is that if we just stick with their releases -- we don't need > any fine-grained work because such year-long cemented code somehow > contradicts the idea of FreeBSD's flexible ports. The idea is to > provide porters a flexible TeXLive base that can be enriched with many > TeX-related projects that are not included in current TeXLive > distribution (new and updated LaTeX packages, new versions of TeX > extensions, etc). Yes, I totally agree. But as explained, after a few days of hack for having TeXLive building (and working), I don't have motivation to split the binaries port now. Moreover, the reply of Hiroki Sato on this list seems to indicate that he has already do that. So I'm waiting for more info about this work for now. > Once an initial TeXLive ports structure is committed, I'd like to see > many porters grabbing parts of their particular areas of interest (or > creating -devel ports) in order to provide users with versions newer > than those initially included. > > It seems to me that your your proposal #3 supports this approach. #1 can be combined with #2, #3 and #4, since #1 is about binaries, and #2, #3, #4 about the rest. Kind regards, Romain -- Romain Tarti?re http://romain.blogreen.org/ pgp: 8DAB A124 0DA4 7024 F82A E748 D8E9 A33F FF56 FF43 (ID: 0xFF56FF43) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081225/86f5d8ca/attachment.pgp From gamato at users.sf.net Thu Dec 25 01:21:14 2008 From: gamato at users.sf.net (mato) Date: Thu Dec 25 01:21:20 2008 Subject: ports/104255: x11/wdm Unable to change window manager after the first selection/login. Message-ID: <20081224150939.M10363@pobox.sk> Hallo, This PR for x11/wdm has not been acted on for more than 2 years despite many details and patches included. I use the port daily and after each (re)installation I have to patch it manually. :-/ Could someone please look at and commit it sooner than later ? Many thanks! Martin From dandee at hellteam.net Thu Dec 25 05:53:32 2008 From: dandee at hellteam.net (=?utf-8?Q?Daniel_Dvo=C5=99=C3=A1k?=) Date: Thu Dec 25 05:53:39 2008 Subject: FreeBSD Port: portupgrade-2.4.6,2 Message-ID: <79454A6D7BD64C0188EE0EB40A5E0794@tocnet28.jspoj.czf> Hi, my portugrade does not upgrade my ports at all. I wanted to upgrade some ports with security risks. I upgraded my ports successfuly 2 months ago without any problem. server# portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching snapshot tag from portsnap1.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Tue Dec 23 20:09:45 CET 2008 to Thu Dec 25 12:30:47 CET 2008. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 97 patches.....10....20....30....40....50....60....70....80....90... done. Applying patches... done. Fetching 5 new ports or files... done. server# portversion -vL= GeoIP < needs updating (port has 1.4.5_1) apache < needs updating (port has 2.2.11) glib < needs updating (port has 2.16.5_1) libexecinfo < needs updating (port has 1.1_3) lsof < needs updating (port has 4.82A,3) p5-HTML-Parser < needs updating (port has 3.59) p5-libwww < needs updating (port has 5.822) php5 < needs updating (port has 5.2.8) php5-bz2 < needs updating (port has 5.2.8) php5-ctype < needs updating (port has 5.2.8) php5-gd < needs updating (port has 5.2.8) php5-mbstring < needs updating (port has 5.2.8) php5-mcrypt < needs updating (port has 5.2.8) php5-mysql < needs updating (port has 5.2.8) php5-mysqli < needs updating (port has 5.2.8) php5-openssl < needs updating (port has 5.2.8) php5-session < needs updating (port has 5.2.8) php5-simplexml < needs updating (port has 5.2.8) php5-spl < needs updating (port has 5.2.8) php5-xml < needs updating (port has 5.2.8) php5-zlib < needs updating (port has 5.2.8) phpMyAdmin < needs updating (port has 3.1.1) quagga < needs updating (port has 0.99.11_1) samba < needs updating (port has 3.0.32_2,1) smartmontools < needs updating (port has 5.38_1) server# portupgrade -av ---> Session started at: Thu, 25 Dec 2008 14:13:31 +0100 ** None has been installed or upgraded. ---> Session ended at: Thu, 25 Dec 2008 14:14:31 +0100 (consumed 00:00:59) server# Why doesn?t portupgrade do its work when portversion thinks it should work ? And what can I do with it ? server# portupgrade -v quagga ---> Session started at: Thu, 25 Dec 2008 14:18:40 +0100 ** None has been installed or upgraded. ---> Session ended at: Thu, 25 Dec 2008 14:18:41 +0100 (consumed 00:00:00) server# Individual port does not work too. server#pkg_info ... portupgrade-2.4.6,2 FreeBSD ports/packages administration and management tool s ... quagga-0.99.10_3 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software ... Portupgrade is up to date. server# uname -a FreeBSD x.y.z 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun May 11 15:18:09 CEST 2008 abc@x.y.z:/usr/obj/usr/src/sys/SERVER i386 I can repeat this upgrading process on others system, they are 6.3-stable too and the same version of portupgrade, with the same failure. I tried to find something about this problem and I found one non-answered thread from October here: http://lists.freebsd.org/pipermail/freebsd-ports/2008-October/051187.html I think it is somehow connected with my problem. Thank you Dan Merry Xmas From gesbbb at yahoo.com Thu Dec 25 06:06:33 2008 From: gesbbb at yahoo.com (Jerry) Date: Thu Dec 25 06:06:40 2008 Subject: FreeBSD Port: portupgrade-2.4.6,2 In-Reply-To: <79454A6D7BD64C0188EE0EB40A5E0794@tocnet28.jspoj.czf> References: <79454A6D7BD64C0188EE0EB40A5E0794@tocnet28.jspoj.czf> Message-ID: <20081225090620.2e5f2479@scorpio> On Thu, 25 Dec 2008 14:37:03 +0100 Daniel Dvo??k wrote: >Hi, > >my portugrade does not upgrade my ports at all. I wanted to upgrade >some ports with security risks. I upgraded my ports successfuly 2 >months ago without any problem. > >server# portsnap fetch Shouldn't that be "portsnap fetch update"? At least that is what it seems to indicate on the 'man' page for portsnap assuming that you have used the extract command previously. -- Jerry gesbbb@yahoo.com Sometimes I simply feel that the whole world is a cigarette and I'm the only ashtray. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081225/7094af57/signature.pgp From dandee at hellteam.net Thu Dec 25 07:20:41 2008 From: dandee at hellteam.net (=?utf-8?Q?Daniel_Dvo=C5=99=C3=A1k?=) Date: Thu Dec 25 07:20:49 2008 Subject: FW: FreeBSD Port: portupgrade-2.4.6,2 Message-ID: Ou ! You are right. I am so so sorry for disturbing all kind people here. 2 months and I completly forgot right command to execute portupgrade process. Dan Jerry gesbbb at yahoo.com Thu Dec 25 06:06:33 PST 2008 * Previous message: FreeBSD Port: portupgrade-2.4.6,2 * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] _____ On Thu, 25 Dec 2008 14:37:03 +0100 Daniel Dvo??k > wrote: >Hi, > >my portugrade does not upgrade my ports at all. I wanted to upgrade >some ports with security risks. I upgraded my ports successfuly 2 >months ago without any problem. > >server# portsnap fetch Shouldn't that be "portsnap fetch update"? At least that is what it seems to indicate on the 'man' page for portsnap assuming that you have used the extract command previously. -- Jerry gesbbb at yahoo.com Sometimes I simply feel that the whole world is a cigarette and I'm the only ashtray. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081225/7094af57/signature.pgp _____ From: Daniel Dvo??k [mailto:dandee@hellteam.net] Sent: Thursday, December 25, 2008 2:37 PM To: 'sem@FreeBSD.org' Cc: 'ports@FreeBSD.org' Subject: FreeBSD Port: portupgrade-2.4.6,2 Hi, my portugrade does not upgrade my ports at all. I wanted to upgrade some ports with security risks. I upgraded my ports successfuly 2 months ago without any problem. server# portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching snapshot tag from portsnap1.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Tue Dec 23 20:09:45 CET 2008 to Thu Dec 25 12:30:47 CET 2008. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 97 patches.....10....20....30....40....50....60....70....80....90... done. Applying patches... done. Fetching 5 new ports or files... done. server# portversion -vL= GeoIP < needs updating (port has 1.4.5_1) apache < needs updating (port has 2.2.11) glib < needs updating (port has 2.16.5_1) libexecinfo < needs updating (port has 1.1_3) lsof < needs updating (port has 4.82A,3) p5-HTML-Parser < needs updating (port has 3.59) p5-libwww < needs updating (port has 5.822) php5 < needs updating (port has 5.2.8) php5-bz2 < needs updating (port has 5.2.8) php5-ctype < needs updating (port has 5.2.8) php5-gd < needs updating (port has 5.2.8) php5-mbstring < needs updating (port has 5.2.8) php5-mcrypt < needs updating (port has 5.2.8) php5-mysql < needs updating (port has 5.2.8) php5-mysqli < needs updating (port has 5.2.8) php5-openssl < needs updating (port has 5.2.8) php5-session < needs updating (port has 5.2.8) php5-simplexml < needs updating (port has 5.2.8) php5-spl < needs updating (port has 5.2.8) php5-xml < needs updating (port has 5.2.8) php5-zlib < needs updating (port has 5.2.8) phpMyAdmin < needs updating (port has 3.1.1) quagga < needs updating (port has 0.99.11_1) samba < needs updating (port has 3.0.32_2,1) smartmontools < needs updating (port has 5.38_1) server# portupgrade -av ---> Session started at: Thu, 25 Dec 2008 14:13:31 +0100 ** None has been installed or upgraded. ---> Session ended at: Thu, 25 Dec 2008 14:14:31 +0100 (consumed 00:00:59) server# Why doesn?t portupgrade do its work when portversion thinks it should work ? And what can I do with it ? server# portupgrade -v quagga ---> Session started at: Thu, 25 Dec 2008 14:18:40 +0100 ** None has been installed or upgraded. ---> Session ended at: Thu, 25 Dec 2008 14:18:41 +0100 (consumed 00:00:00) server# Individual port does not work too. server#pkg_info ... portupgrade-2.4.6,2 FreeBSD ports/packages administration and management tool s ... quagga-0.99.10_3 Free RIPv1, RIPv2, OSPFv2, BGP4, IS-IS route software ... Portupgrade is up to date. server# uname -a FreeBSD x.y.z 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun May 11 15:18:09 CEST 2008 abc@x.y.z:/usr/obj/usr/src/sys/SERVER i386 I can repeat this upgrading process on others system, they are 6.3-stable too and the same version of portupgrade, with the same failure. I tried to find something about this problem and I found one non-answered thread from October here: http://lists.freebsd.org/pipermail/freebsd-ports/2008-October/051187.html I think it is somehow connected with my problem. Thank you Dan Merry Xmas From nork at FreeBSD.org Thu Dec 25 08:23:22 2008 From: nork at FreeBSD.org (Norikatsu Shigemura) Date: Thu Dec 25 08:23:30 2008 Subject: ports/graphics/ImageMagick: Fix pkg-plist WITH_IMAGEMAGICK_MODULES Message-ID: <20081226012310.cc415680.nork@FreeBSD.org> Hi mm! I found a issue of pkg-plist WITH_IMAGEMAGICK_MODULES. Please apply following patch: Index: Makefile =================================================================== RCS file: /home/ncvs/ports/graphics/ImageMagick/Makefile,v retrieving revision 1.274 diff -u -r1.274 Makefile --- Makefile 10 Dec 2008 14:16:02 -0000 1.274 +++ Makefile 24 Dec 2008 18:24:46 -0000 @@ -7,6 +7,7 @@ PORTNAME= ImageMagick DISTVERSION= 6.4.7-5 +PORTREVISION= 1 CATEGORIES= graphics perl5 MASTER_SITES= ftp://ftp.imagemagick.org/pub/ImageMagick/ \ ftp://gd.tuwien.ac.at/pub/graphics/ImageMagick/ \ Index: pkg-plist =================================================================== RCS file: /home/ncvs/ports/graphics/ImageMagick/pkg-plist,v retrieving revision 1.115 diff -u -r1.115 pkg-plist --- pkg-plist 11 Nov 2008 10:13:28 -0000 1.115 +++ pkg-plist 24 Dec 2008 18:23:38 -0000 @@ -139,316 +139,316 @@ lib/ImageMagick-%%PORTVERSION%%/config/type-solaris.xml lib/ImageMagick-%%PORTVERSION%%/config/type-windows.xml lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/.keep -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/art.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/art.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/art.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/avi.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/avi.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/avi.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/avs.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/avs.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/avs.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/bmp.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/bmp.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/bmp.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/caption.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/caption.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/caption.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/cin.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/cin.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/cin.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/cip.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/cip.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/cip.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/clip.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/clip.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/clip.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/cmyk.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/cmyk.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/cmyk.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/cut.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/cut.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/cut.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dcm.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dcm.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dcm.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dib.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dib.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dib.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dng.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dng.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dng.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dot.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dot.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dot.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dps.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dps.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dps.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dpx.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dpx.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/dpx.so -%%TIFF%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ept.a -%%TIFF%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ept.la -%%TIFF%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ept.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/fax.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/fax.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/fax.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/fits.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/fits.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/fits.so -%%FPX%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/fpx.a -%%FPX%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/fpx.la -%%FPX%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/fpx.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/gif.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/gif.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/gif.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/gradient.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/gradient.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/gradient.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/gray.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/gray.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/gray.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/histogram.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/histogram.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/histogram.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/html.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/html.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/html.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/icon.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/icon.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/icon.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/info.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/info.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/info.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ipl.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ipl.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ipl.so -%%JBIG%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/jbig.a -%%JBIG%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/jbig.la -%%JBIG%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/jbig.so -%%JPEG2000%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/jp2.a -%%JPEG2000%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/jp2.la -%%JPEG2000%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/jp2.so -%%JPEG%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/jpeg.a -%%JPEG%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/jpeg.la -%%JPEG%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/jpeg.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/label.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/label.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/label.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/magick.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/magick.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/magick.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/map.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/map.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/map.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mat.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mat.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mat.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/matte.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/matte.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/matte.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/meta.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/meta.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/meta.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/miff.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/miff.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/miff.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mono.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mono.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mono.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mpc.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mpc.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mpc.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mpeg.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mpeg.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mpeg.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mpr.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mpr.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mpr.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/msl.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/msl.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/msl.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mtv.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mtv.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mtv.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mvg.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mvg.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/mvg.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/null.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/null.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/null.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/otb.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/otb.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/otb.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/palm.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/palm.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/palm.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pattern.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pattern.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pattern.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pcd.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pcd.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pcd.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pcl.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pcl.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pcl.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pcx.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pcx.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pcx.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pdb.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pdb.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pdb.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pdf.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pdf.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pdf.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pict.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pict.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pict.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pix.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pix.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pix.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/plasma.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/plasma.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/plasma.so -%%PNG%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/png.a -%%PNG%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/png.la -%%PNG%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/png.so -%%OPENEXR%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/exr.a -%%OPENEXR%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/exr.la -%%OPENEXR%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/exr.so -%%DJVU%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/djvu.a -%%DJVU%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/djvu.la -%%DJVU%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/djvu.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pnm.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pnm.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pnm.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/preview.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/preview.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/preview.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ps.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ps.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ps.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ps2.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ps2.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ps2.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ps3.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ps3.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ps3.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/psd.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/psd.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/psd.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pwp.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pwp.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/pwp.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/raw.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/raw.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/raw.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/rgb.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/rgb.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/rgb.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/rla.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/rla.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/rla.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/rle.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/rle.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/rle.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/scr.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/scr.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/scr.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/sct.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/sct.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/sct.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/sfw.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/sfw.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/sfw.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/sgi.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/sgi.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/sgi.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/stegano.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/stegano.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/stegano.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/sun.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/sun.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/sun.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/svg.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/svg.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/svg.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/tga.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/tga.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/tga.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/thumbnail.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/thumbnail.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/thumbnail.so -%%TIFF%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/tiff.a -%%TIFF%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/tiff.la -%%TIFF%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/tiff.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/tile.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/tile.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/tile.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/tim.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/tim.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/tim.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ttf.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ttf.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ttf.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/txt.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/txt.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/txt.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/uil.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/uil.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/uil.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/url.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/url.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/url.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/uyvy.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/uyvy.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/uyvy.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/vicar.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/vicar.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/vicar.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/vid.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/vid.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/vid.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/viff.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/viff.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/viff.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/wbmp.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/wbmp.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/wbmp.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/wmf.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/wmf.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/wmf.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/wpg.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/wpg.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/wpg.so -%%X11%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/x.a -%%X11%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/x.la -%%X11%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/x.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xbm.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xbm.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xbm.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xc.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xc.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xc.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xcf.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xcf.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xcf.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xpm.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xpm.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xpm.so -%%X11%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xwd.a -%%X11%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xwd.la -%%X11%%%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/xwd.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ycbcr.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ycbcr.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/ycbcr.so -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/yuv.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/yuv.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/coders/yuv.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/art.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/art.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/art.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/avi.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/avi.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/avi.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/avs.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/avs.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/avs.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/bmp.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/bmp.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/bmp.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/caption.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/caption.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/caption.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/cin.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/cin.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/cin.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/cip.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/cip.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/cip.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/clip.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/clip.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/clip.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/cmyk.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/cmyk.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/cmyk.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/cut.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/cut.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/cut.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dcm.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dcm.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dcm.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dib.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dib.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dib.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dng.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dng.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dng.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dot.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dot.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dot.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dps.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dps.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dps.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dpx.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dpx.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/dpx.so +%%TIFF%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ept.a +%%TIFF%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ept.la +%%TIFF%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ept.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/fax.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/fax.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/fax.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/fits.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/fits.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/fits.so +%%FPX%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/fpx.a +%%FPX%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/fpx.la +%%FPX%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/fpx.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/gif.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/gif.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/gif.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/gradient.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/gradient.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/gradient.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/gray.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/gray.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/gray.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/histogram.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/histogram.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/histogram.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/html.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/html.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/html.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/icon.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/icon.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/icon.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/info.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/info.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/info.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ipl.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ipl.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ipl.so +%%JBIG%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/jbig.a +%%JBIG%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/jbig.la +%%JBIG%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/jbig.so +%%JPEG2000%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/jp2.a +%%JPEG2000%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/jp2.la +%%JPEG2000%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/jp2.so +%%JPEG%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/jpeg.a +%%JPEG%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/jpeg.la +%%JPEG%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/jpeg.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/label.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/label.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/label.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/magick.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/magick.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/magick.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/map.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/map.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/map.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mat.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mat.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mat.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/matte.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/matte.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/matte.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/meta.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/meta.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/meta.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/miff.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/miff.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/miff.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mono.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mono.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mono.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mpc.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mpc.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mpc.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mpeg.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mpeg.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mpeg.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mpr.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mpr.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mpr.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/msl.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/msl.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/msl.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mtv.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mtv.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mtv.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mvg.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mvg.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/mvg.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/null.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/null.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/null.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/otb.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/otb.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/otb.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/palm.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/palm.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/palm.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pattern.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pattern.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pattern.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pcd.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pcd.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pcd.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pcl.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pcl.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pcl.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pcx.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pcx.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pcx.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pdb.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pdb.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pdb.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pdf.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pdf.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pdf.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pict.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pict.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pict.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pix.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pix.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pix.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/plasma.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/plasma.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/plasma.so +%%PNG%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/png.a +%%PNG%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/png.la +%%PNG%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/png.so +%%OPENEXR%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/exr.a +%%OPENEXR%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/exr.la +%%OPENEXR%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/exr.so +%%DJVU%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/djvu.a +%%DJVU%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/djvu.la +%%DJVU%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/djvu.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pnm.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pnm.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pnm.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/preview.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/preview.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/preview.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ps.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ps.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ps.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ps2.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ps2.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ps2.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ps3.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ps3.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ps3.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/psd.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/psd.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/psd.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pwp.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pwp.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/pwp.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/raw.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/raw.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/raw.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/rgb.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/rgb.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/rgb.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/rla.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/rla.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/rla.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/rle.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/rle.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/rle.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/scr.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/scr.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/scr.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/sct.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/sct.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/sct.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/sfw.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/sfw.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/sfw.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/sgi.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/sgi.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/sgi.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/stegano.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/stegano.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/stegano.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/sun.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/sun.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/sun.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/svg.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/svg.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/svg.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/tga.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/tga.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/tga.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/thumbnail.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/thumbnail.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/thumbnail.so +%%TIFF%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/tiff.a +%%TIFF%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/tiff.la +%%TIFF%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/tiff.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/tile.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/tile.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/tile.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/tim.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/tim.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/tim.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ttf.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ttf.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ttf.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/txt.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/txt.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/txt.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/uil.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/uil.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/uil.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/url.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/url.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/url.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/uyvy.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/uyvy.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/uyvy.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/vicar.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/vicar.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/vicar.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/vid.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/vid.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/vid.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/viff.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/viff.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/viff.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/wbmp.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/wbmp.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/wbmp.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/wmf.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/wmf.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/wmf.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/wpg.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/wpg.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/wpg.so +%%X11%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/x.a +%%X11%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/x.la +%%X11%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/x.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xbm.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xbm.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xbm.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xc.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xc.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xc.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xcf.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xcf.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xcf.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xpm.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xpm.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xpm.so +%%X11%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xwd.a +%%X11%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xwd.la +%%X11%%%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/xwd.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ycbcr.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ycbcr.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/ycbcr.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/yuv.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/yuv.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/coders/yuv.so lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/filters/.keep -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/filters/analyze.a -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/filters/analyze.la -%%MODULES%%lib/ImageMagick/modules-%%QBIT%%/filters/analyze.so +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/filters/analyze.a +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/filters/analyze.la +%%MODULES%%lib/ImageMagick-%%PORTVERSION%%/modules-%%QBIT%%/filters/analyze.so lib/libMagick++.a lib/libMagick++.la lib/libMagick++.so From david.fleck at mchsi.com Thu Dec 25 16:17:16 2008 From: david.fleck at mchsi.com (David Fleck) Date: Thu Dec 25 16:17:22 2008 Subject: Error building ruby-1.8.2_4 port Message-ID: Background: I have a 6.4-RELEASE system, that I have just freebsd-update'ed to 7.0-RELEASE. So far, I've run the first two 'freebsd-update install' commands, and am now trying to update the few ports I have installed. So, since ruby isn't installed yet, and I need that to run portupgrade, I am trying to build the ruby port. It bombs with this error: cc -fPIC -O2 -fno-strict-aliasing -pipe -fPIC -I. -I../.. -I../../. -I../.././ext/openssl -DHAVE_UNISTD_H -DHAVE_SYS_TIME_H -DHAVE_ASSERT_H -DHAVE_OPENSSL_SSL_H -DHAVE_OPENSSL_CONF_API_H -DHAVE_BN_MOD_ADD -DHAVE_BN_MOD_SQR -DHAVE_BN_MOD_SUB -DHAVE_BN_PSEUDO_RAND_RANGE -DHAVE_BN_RAND_RANGE -DHAVE_CONF_GET1_DEFAULT_CONFIG_FILE -DHAVE_EVP_CIPHER_CTX_SET_PADDING -DHAVE_EVP_CIPHERFINAL_EX -DHAVE_EVP_CIPHERINIT_EX -DHAVE_EVP_DIGESTFINAL_EX -DHAVE_EVP_DIGESTINIT_EX -DHAVE_EVP_MD_CTX_CLEANUP -DHAVE_EVP_MD_CTX_CREATE -DHAVE_EVP_MD_CTX_DESTROY -DHAVE_EVP_MD_CTX_INIT -DHAVE_HMAC_CTX_CLEANUP -DHAVE_HMAC_CTX_INIT -DHAVE_PEM_DEF_CALLBACK -DHAVE_X509V3_SET_NCONF -DHAVE_X509_CRL_ADD0_REVOKED -DHAVE_X509_CRL_SET_ISSUER_NAME -DHAVE_X509_CRL_SET_VERSION -DHAVE_X509_CRL_SORT -DHAVE_VA_ARGS_MACRO -DHAVE_OPENSSL_ENGINE_H -DHAVE_ENGINE_ADD -DHAVE_ENGINE_LOAD_BUILTIN_ENGINES -DHAVE_ENGINE_GET_DIGEST -DHAVE_ENGINE_GET_CIPHER -DHAVE_ENGINE_CLEANUP -DHAVE_OPENSSL_OCSP_H -DHAVE_ST_FLAGS -DHAVE_ST_ENGINE -DHAVE_ST_SINGLE -c ossl_x509store.c ossl_x509store.c: In function 'ossl_x509stctx_set_time': ossl_x509store.c:541: error: 'X509_STORE_CTX' has no member named 'flags' *** Error code 1 I've uninstalled and reinstalled the openssl-0.9.8a port, and done a 'make clean' in /usr/ports/lang/ruby18, but this error still occurs. I've seen hints (e.g., https://savannah.cern.ch/bugs/?32304) that this is because there are changes in openssl that aren't accounted for in ruby. Anyway, what's the best way to proceed right now to get the port installed? -- David Fleck david.fleck@mchsi.com From yanefbsd at gmail.com Fri Dec 26 00:42:16 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 26 00:42:23 2008 Subject: Error building ruby-1.8.2_4 port In-Reply-To: References: Message-ID: <27888DAF-4D61-4BDF-9AD9-2A2EE8CA7248@gmail.com> On Dec 25, 2008, at 16:03, David Fleck wrote: > Background: > > I have a 6.4-RELEASE system, that I have just freebsd-update'ed to > 7.0-RELEASE. So far, I've run the first two 'freebsd-update > install' commands, and am now trying to update the few ports I have > installed. So, > since ruby isn't installed yet, and I need that to run portupgrade, > I am trying to build the ruby port. It bombs with this error: > > cc -fPIC -O2 -fno-strict-aliasing -pipe -fPIC -I. -I../.. - > I../../. -I../.././ext/openssl -DHAVE_UNISTD_H -DHAVE_SYS_TIME_H - > DHAVE_ASSERT_H -DHAVE_OPENSSL_SSL_H -DHAVE_OPENSSL_CONF_API_H - > DHAVE_BN_MOD_ADD -DHAVE_BN_MOD_SQR -DHAVE_BN_MOD_SUB - > DHAVE_BN_PSEUDO_RAND_RANGE -DHAVE_BN_RAND_RANGE - > DHAVE_CONF_GET1_DEFAULT_CONFIG_FILE - > DHAVE_EVP_CIPHER_CTX_SET_PADDING -DHAVE_EVP_CIPHERFINAL_EX - > DHAVE_EVP_CIPHERINIT_EX -DHAVE_EVP_DIGESTFINAL_EX - > DHAVE_EVP_DIGESTINIT_EX -DHAVE_EVP_MD_CTX_CLEANUP - > DHAVE_EVP_MD_CTX_CREATE -DHAVE_EVP_MD_CTX_DESTROY - > DHAVE_EVP_MD_CTX_INIT -DHAVE_HMAC_CTX_CLEANUP -DHAVE_HMAC_CTX_INIT - > DHAVE_PEM_DEF_CALLBACK -DHAVE_X509V3_SET_NCONF - > DHAVE_X509_CRL_ADD0_REVOKED -DHAVE_X509_CRL_SET_ISSUER_NAME - > DHAVE_X509_CRL_SET_VERSION -DHAVE_X509_CRL_SORT -DHAVE_VA_ARGS_MACRO > -DHAVE_OPENSSL_ENGINE_H -DHAVE_ENGINE_ADD - > DHAVE_ENGINE_LOAD_BUILTIN_ENGINES -DHAVE_ENGINE_GET_DIGEST - > DHAVE_ENGINE_GET_CIPHER -DHAVE_ENGINE_CLEANUP -DHAVE_OPENSSL_OCSP_H - > DHAVE_ST_FLAGS -DHAVE_ST_ENGINE -DHAVE_ST_SINGLE -c ossl_x509store.c > ossl_x509store.c: In function 'ossl_x509stctx_set_time': > ossl_x509store.c:541: error: 'X509_STORE_CTX' has no member named > 'flags' > *** Error code 1 > > I've uninstalled and reinstalled the openssl-0.9.8a port, and done a > 'make clean' in /usr/ports/lang/ruby18, but this error still > occurs. I've seen hints (e.g., https://savannah.cern.ch/bugs/? > 32304) that this is because there are changes in openssl that aren't > accounted for in ruby. Anyway, what's the best way to proceed right > now to get the port installed? > > -- > David Fleck > david.fleck@mchsi.com Is compat6x support enabled in the kernel and from ports yet? -Garrett From pgollucci at p6m7g8.com Fri Dec 26 00:46:00 2008 From: pgollucci at p6m7g8.com (Philip M. Gollucci) Date: Fri Dec 26 00:46:07 2008 Subject: Error building ruby-1.8.2_4 port In-Reply-To: References: Message-ID: <4954974F.7090804@p6m7g8.com> David Fleck wrote: > Background: > > I have a 6.4-RELEASE system, that I have just freebsd-update'ed to > 7.0-RELEASE. So far, I've run the first two 'freebsd-update install' > commands, and am now trying to update the few ports I have installed. So, > since ruby isn't installed yet, and I need that to run portupgrade, I am > trying to build the ruby port. It bombs with this error: Your ports tree isn't just old, is ANCIENT! http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html' The port is at 1.8.7.287_1 or so. -- ------------------------------------------------------------------------ 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollucci@p6m7g8.com) c: 703.336.9354 Consultant - P6M7G8 Inc. http://p6m7g8.net Director IT - RideCharge, Inc. http://ridecharge.com Contractor - PositiveEnergyUSA http://positiveenergyusa.com ASF Member - Apache Software Foundation http://apache.org FreeBSD Committer - FreeBSD Foundation http://freebsd.org Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. From xyin at gmx.com Fri Dec 26 01:37:25 2008 From: xyin at gmx.com (Xihong Yin) Date: Fri Dec 26 01:37:39 2008 Subject: Latex port Message-ID: I installed teTeX from port, but I found that I have no 'table' environment. Can anybody tell me what's wrong? Also, can I download TeX Live and build it on my FreeBSD box? Thanks, Xihong From talon at lpthe.jussieu.fr Fri Dec 26 02:20:45 2008 From: talon at lpthe.jussieu.fr (Michel Talon) Date: Fri Dec 26 02:20:51 2008 Subject: Latex port Message-ID: <20081226100458.GA97124@lpthe.jussieu.fr> Xihong Yin wrote: > I installed teTeX from port, but I found that I have no 'table' > environment. Can anybody tell me what's wrong? Works perfectly fine for me: Compiling the following under teTeX and FreeBSD-7 works and gives the expected result: \documentclass{article} \begin{document} \begin{table}[ht] \centerline{ \begin{tabular}{|l|c|c|} \hline colonne 1 & colonne 2 & colonne 3 \\ \hline 1.1 & 1.2 & 1.3 \\ 2.1 & 2.2 & 2.3 \\ \hline \end{tabular} } \caption{\label{mylabel} Title} \end{table} \end{document} niobe% latex toto This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) entering extended mode (./toto.tex LaTeX2e <2003/12/01> Babel and hyphenation patterns for american, french, german, ngerman, b ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur kish, ukrainian, nohyphenation, loaded. (/usr/local/share/texmf-dist/tex/latex/base/article.cls Document Class: article 2004/02/16 v1.4f Standard LaTeX document class (/usr/local/share/texmf-dist/tex/latex/base/size10.clo)) (./toto.aux) [1] (./toto.aux) ) Output written on toto.dvi (1 page, 624 bytes). Transcript written on toto.log. niobe% ls /var/db/pkg|grep teTeX teTeX-3.0_1/ teTeX-base-3.0_6/ teTeX-texmf-3.0_3/ -- Michel TALON From david.fleck at mchsi.com Fri Dec 26 05:13:44 2008 From: david.fleck at mchsi.com (David Fleck) Date: Fri Dec 26 05:13:51 2008 Subject: Error building ruby-1.8.2_4 port In-Reply-To: <4954974F.7090804@p6m7g8.com> References: <4954974F.7090804@p6m7g8.com> Message-ID: On Fri, 26 Dec 2008, Philip M. Gollucci wrote: > Your ports tree isn't just old, is ANCIENT! Yes, it is. After about an hour of messing around, I realized that while I'd upgraded the system, I'd completely forgotten about /usr/ports. After running portsnap, everything appears to compile OK. Sorry for the bogus error. -- David Fleck david.fleck@mchsi.com From mail at ozzmosis.com Fri Dec 26 07:57:08 2008 From: mail at ozzmosis.com (andrew clarke) Date: Fri Dec 26 07:57:16 2008 Subject: Unable to build strace-4.5.18 under FreeBSD 6.4 Message-ID: <20081226155704.GA45251@ozzmosis.com> # uname -a FreeBSD blizzard.phoenix 6.4-RELEASE FreeBSD 6.4-RELEASE #0: Wed Nov 26 11:43:51 UTC 2008 root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 # make ===> Vulnerability check disabled, database not found ===> Extracting for strace-4.5.18 => MD5 Checksum OK for strace-4.5.18.tar.bz2. => SHA256 Checksum OK for strace-4.5.18.tar.bz2. ===> strace-4.5.18 depends on file: /usr/local/bin/perl5.8.8 - found ===> Patching for strace-4.5.18 ===> strace-4.5.18 depends on file: /usr/local/bin/perl5.8.8 - found ===> Applying FreeBSD patches for strace-4.5.18 /usr/bin/sed -i.bak 's,/usr/bin/perl,/usr/local/bin/perl,' /spare/ports/devel/strace/work/strace-4.5.18/strace-graph ===> strace-4.5.18 depends on file: /usr/local/bin/perl5.8.8 - found ===> Configuring for strace-4.5.18 ... ===> Building for strace-4.5.18 make all-am cc -DHAVE_CONFIG_H -I. -Ifreebsd/i386 -I./freebsd/i386 -Ifreebsd -I./freebsd -Wall -O2 -fno-strict-aliasing -pipe -MT strace.o -MD -MP -MF .deps/strace.Tpo -c -o strace.o strace.c mv -f .deps/strace.Tpo .deps/strace.Po cc -DHAVE_CONFIG_H -I. -Ifreebsd/i386 -I./freebsd/i386 -Ifreebsd -I./freebsd -Wall -O2 -fno-strict-aliasing -pipe -MT syscall.o -MD -MP -MF .deps/syscall.Tpo -c -o syscall.o syscall.c syscall.c: In function `internal_syscall': syscall.c:719: error: `sys_waitpid' undeclared (first use in this function) syscall.c:719: error: (Each undeclared identifier is reported only once syscall.c:719: error: for each function it appears in.) *** Error code 1 Stop in /spare/ports/devel/strace/work/strace-4.5.18. *** Error code 1 Regards Andrew From sfourman at gmail.com Fri Dec 26 11:36:01 2008 From: sfourman at gmail.com (Sam Fourman Jr.) Date: Fri Dec 26 11:36:07 2008 Subject: Can't build Wine 1.1.10,1 port on up to date current. In-Reply-To: <200812162129.50216.tijl@ulyssis.org> References: <20081216071554.19716ikpfazg3l8o@econet.encontacto.net> <200812162129.50216.tijl@ulyssis.org> Message-ID: <11167f520812261106k16ac2706wa383a3be2ffa57@mail.gmail.com> > It's because of this: > http://lists.freebsd.org/pipermail/freebsd-current/2008-December/001264.html does someone have a patch handy that we can use to get around this issue? Sam Fourman Jr. Fourman Networks From tijl at ulyssis.org Fri Dec 26 12:07:26 2008 From: tijl at ulyssis.org (Tijl Coosemans) Date: Fri Dec 26 12:07:33 2008 Subject: Can't build Wine 1.1.10,1 port on up to date current. In-Reply-To: <11167f520812261106k16ac2706wa383a3be2ffa57@mail.gmail.com> References: <20081216071554.19716ikpfazg3l8o@econet.encontacto.net> <200812162129.50216.tijl@ulyssis.org> <11167f520812261106k16ac2706wa383a3be2ffa57@mail.gmail.com> Message-ID: <200812262107.22665.tijl@ulyssis.org> On Friday 26 December 2008 20:06:37 Sam Fourman Jr. wrote: >> It's because of this: >> http://lists.freebsd.org/pipermail/freebsd-current/2008-December/001264.html > > does someone have a patch handy that we can use to get around this > issue? Attached. I also needed the mkdir patch with wine 1.1.11, so I included that as well. Without it, wine creates directories with wrong permissions. This has already been fixed upstream though, so you should remove it when version 1.1.12 arrives. -------------- next part -------------- diff --git dlls/iphlpapi/ipstats.c dlls/iphlpapi/ipstats.c index 3fc91eb..99e78a0 100644 --- dlls/iphlpapi/ipstats.c +++ dlls/iphlpapi/ipstats.c @@ -1250,7 +1250,11 @@ DWORD getRouteTable(PMIB_IPFORWARDTABLE *ppIpForwardTable, HANDLE heap, DWORD getNumArpEntries(void) { #if defined(HAVE_SYS_SYSCTL_H) && defined(NET_RT_DUMP) +#ifdef RTF_LLINFO int mib[] = {CTL_NET, PF_ROUTE, 0, AF_INET, NET_RT_FLAGS, RTF_LLINFO}; +#else + int mib[] = {CTL_NET, PF_ROUTE, 0, AF_INET, NET_RT_FLAGS, 0}; +#endif #define MIB_LEN (sizeof(mib) / sizeof(mib[0])) DWORD arpEntries = 0; size_t needed; @@ -1308,7 +1312,11 @@ DWORD getArpTable(PMIB_IPNETTABLE *ppIpNetTable, HANDLE heap, DWORD flags) #if defined(HAVE_SYS_SYSCTL_H) && defined(NET_RT_DUMP) if (table) { +#ifdef RTF_LLINFO int mib[] = {CTL_NET, PF_ROUTE, 0, AF_INET, NET_RT_FLAGS, RTF_LLINFO}; +#else + int mib[] = {CTL_NET, PF_ROUTE, 0, AF_INET, NET_RT_FLAGS, 0}; +#endif #define MIB_LEN (sizeof(mib) / sizeof(mib[0])) size_t needed; char *buf, *lim, *next; -------------- next part -------------- --- include/wine/port.h.orig 2008-12-26 13:38:31.000000000 +0100 +++ include/wine/port.h 2008-12-26 13:38:55.000000000 +0100 @@ -115,7 +115,6 @@ #endif #ifdef HAVE__MKDIR -#define mkdir(path,mode) _mkdir(path) #endif #if !defined(HAVE_FTRUNCATE) && defined(HAVE_CHSIZE) From w8hdkim at gmail.com Fri Dec 26 13:22:26 2008 From: w8hdkim at gmail.com (Kim Culhan) Date: Fri Dec 26 13:22:33 2008 Subject: 7.1-RC2 audio/x11amp missing symbol at startup Message-ID: <89dbfdc30812261253sd13d85fn9d2c079d644818b@mail.gmail.com> Using the ports tree cvsup'd 12-26-08 running on FreeBSD 7.1-RC2 At startup audio/x11amp returns: /usr/local/lib/x11amp/Input/libwav.so: Undefined symbol "effects_enabled" /usr/local/lib/x11amp/Input/libmpg123.so: Undefined symbol "effects_enabled" /usr/local/lib/x11amp/Input/libmikmod.so: Undefined symbol "effects_enabled" Gdk-ERROR **: BadMatch (invalid parameter attributes) serial 82 error_code 8 request_code 2 minor_code 0 Anyone else seeing this? -kim -- From yanefbsd at gmail.com Fri Dec 26 13:43:24 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 26 13:43:31 2008 Subject: 7.1-RC2 audio/x11amp missing symbol at startup In-Reply-To: <89dbfdc30812261253sd13d85fn9d2c079d644818b@mail.gmail.com> References: <89dbfdc30812261253sd13d85fn9d2c079d644818b@mail.gmail.com> Message-ID: <54BC6DF8-BEC3-4133-8394-9FEF055E8A4A@gmail.com> On Dec 26, 2008, at 12:53, "Kim Culhan" wrote: > Using the ports tree cvsup'd 12-26-08 running on FreeBSD 7.1-RC2 > > At startup audio/x11amp returns: > > /usr/local/lib/x11amp/Input/libwav.so: Undefined symbol > "effects_enabled" > /usr/local/lib/x11amp/Input/libmpg123.so: Undefined symbol > "effects_enabled" > /usr/local/lib/x11amp/Input/libmikmod.so: Undefined symbol > "effects_enabled" > Gdk-ERROR **: BadMatch (invalid parameter attributes) > serial 82 error_code 8 request_code 2 minor_code 0 > > Anyone else seeing this? > > -kim How did you initially install freebsd? What version did you install? What versions were your ports compiled against? -Garrett From marshc187 at gmail.com Fri Dec 26 14:02:16 2008 From: marshc187 at gmail.com (t-u-t) Date: Fri Dec 26 14:02:25 2008 Subject: general ports problem Message-ID: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> hi, i have a quick question and don't know what this problem is related to. i am getting an error on *every* port i try to build -- Script "configure" failed unexpectedly. etc,etc, please check log. searching the net i am finding pages on particular ports (not same as mine yet) -- but baffled as to why every port giving this error. I have no clue what is in these log files and was wondering whether the "unknown' entries is normal at "/bin/arch=" below. this below is the topmost part of config.log and just noticed the parts with win32 and don't know what that means. the very last line in the log file reads configure. exit 77. ======================== It was created by configure, which was generated by GNU Autoconf 2.61. Invocation command line was $ ./configure --with-w32-path=/usr/local/lib/win32 --enable-ipv6 --with-external-libmad --with-external-libdts --with-libflac --disable-v4l --disable-arts --disable-artstest --without-caca --disable-cacatest --disable-gnomevfs --disable-xvmc --disable-aalib --disable-aalibtest --without-imagemagick --disable-gdkpixbuf --with-wavpack --disable-vidix --x-libraries=/usr/local/lib --x-includes=/usr/local/include --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ --build=amd64-portbld-freebsd7.1 ## --------- ## ## Platform. ## ## --------- ## hostname = ilras.barsh uname -m = amd64 uname -r = 7.1-PRERELEASE uname -s = FreeBSD uname -v = FreeBSD 7.1-PRERELEASE #0: Tue Dec 23 22:24:03 CET 2008 root@ilras.barsh:/usr/obj/usr/src/sys/DAMON /usr/bin/uname -p = amd64 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown -- ce la vie From glen.j.barber at gmail.com Fri Dec 26 14:30:34 2008 From: glen.j.barber at gmail.com (Glen Barber) Date: Fri Dec 26 14:30:40 2008 Subject: general ports problem In-Reply-To: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> Message-ID: <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> On Fri, Dec 26, 2008 at 5:02 PM, t-u-t wrote: > hi, > i have a quick question and don't know what this problem is related to. > > i am getting an error on *every* port i try to build -- Script "configure" > failed unexpectedly. etc,etc, please check log. > > searching the net i am finding pages on particular ports (not same as mine > yet) -- but baffled as to why every port giving this error. > > I have no clue what is in these log files and was wondering whether the > "unknown' entries is normal at "/bin/arch=" below. > > this below is the topmost part of config.log and just noticed the parts with > win32 and don't know what that means. > > the very last line in the log file reads configure. exit 77. > Is there anything odd in /etc/make.conf ? Are your ports up to date? -- Glen Barber From marshc187 at gmail.com Fri Dec 26 14:33:26 2008 From: marshc187 at gmail.com (t-u-t) Date: Fri Dec 26 14:33:33 2008 Subject: general ports problem In-Reply-To: <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> Message-ID: <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> On Fri, Dec 26, 2008 at 11:05 PM, Glen Barber wrote: > On Fri, Dec 26, 2008 at 5:02 PM, t-u-t wrote: > > hi, > > i have a quick question and don't know what this problem is related to. > > > > i am getting an error on *every* port i try to build -- Script > "configure" > > failed unexpectedly. etc,etc, please check log. > > > > searching the net i am finding pages on particular ports (not same as > mine > > yet) -- but baffled as to why every port giving this error. > > > > I have no clue what is in these log files and was wondering whether the > > "unknown' entries is normal at "/bin/arch=" below. > > > > this below is the topmost part of config.log and just noticed the parts > with > > win32 and don't know what that means. > > > > the very last line in the log file reads configure. exit 77. > > > > Is there anything odd in /etc/make.conf ? Are your ports up to date? > > > -- > Glen Barber > ports are updated, yes, and make.conf has some settings but have to check, since i'm new and used a copy of the example file and have to check what is enabled. this is a quick reply cuz i just noticed a previous error messge stating - " C compiler cannot create executables " tried a couple of ports, they have this error thanks make.conf CFLAGS= -O -pipe MAKE_SHELL?=sh COPTFLAGS= -O -pipe WITH_XINERAMA="YES" WITH_GNOME="YES" WITH_DOCHTML="YES" WITH_IMLIB2="YES" -- ce la vie From sfourman at gmail.com Fri Dec 26 15:26:25 2008 From: sfourman at gmail.com (Sam Fourman Jr.) Date: Fri Dec 26 15:26:31 2008 Subject: Can't build Wine 1.1.10,1 port on up to date current. In-Reply-To: <200812262107.22665.tijl@ulyssis.org> References: <20081216071554.19716ikpfazg3l8o@econet.encontacto.net> <200812162129.50216.tijl@ulyssis.org> <11167f520812261106k16ac2706wa383a3be2ffa57@mail.gmail.com> <200812262107.22665.tijl@ulyssis.org> Message-ID: <11167f520812261526j1320da54t893806324a59e5dd@mail.gmail.com> > Attached. > > I also needed the mkdir patch with wine 1.1.11, so I included that as > well. Without it, wine creates directories with wrong permissions. > This has already been fixed upstream though, so you should remove it > when version 1.1.12 arrives. this set of patches worked like a charm on wine 1.1.11 Sam Fourman Jr. From yanefbsd at gmail.com Fri Dec 26 15:51:03 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 26 15:51:15 2008 Subject: general ports problem In-Reply-To: <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> Message-ID: <7A841BD7-C2C2-4CE7-9792-C7E0D71B4019@gmail.com> On Dec 26, 2008, at 14:33, t-u-t wrote: > On Fri, Dec 26, 2008 at 11:05 PM, Glen Barber > wrote: > >> On Fri, Dec 26, 2008 at 5:02 PM, t-u-t wrote: >>> hi, >>> i have a quick question and don't know what this problem is >>> related to. >>> >>> i am getting an error on *every* port i try to build -- Script >> "configure" >>> failed unexpectedly. etc,etc, please check log. >>> >>> searching the net i am finding pages on particular ports (not same >>> as >> mine >>> yet) -- but baffled as to why every port giving this error. >>> >>> I have no clue what is in these log files and was wondering >>> whether the >>> "unknown' entries is normal at "/bin/arch=" below. >>> >>> this below is the topmost part of config.log and just noticed the >>> parts >> with >>> win32 and don't know what that means. >>> >>> the very last line in the log file reads configure. exit 77. >>> >> >> Is there anything odd in /etc/make.conf ? Are your ports up to date? >> >> >> -- >> Glen Barber >> > > > ports are updated, yes, and make.conf has some settings but have to > check, > since i'm new and used a copy of the example file and have to check > what is > enabled. this is a quick reply cuz i just noticed a previous error > messge > stating - > " C compiler cannot create executables " > > tried a couple of ports, they have this error > > thanks > > make.conf > > CFLAGS= -O -pipe > MAKE_SHELL?=sh > COPTFLAGS= -O -pipe > > WITH_XINERAMA="YES" > WITH_GNOME="YES" > WITH_DOCHTML="YES" > WITH_IMLIB2="YES" > -- > ce la vie Try commenting out COPTFLAGS. gcc -V says? -Garrett From yanefbsd at gmail.com Fri Dec 26 15:54:12 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 26 15:54:25 2008 Subject: general ports problem In-Reply-To: <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> Message-ID: <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> On Dec 26, 2008, at 14:33, t-u-t wrote: > On Fri, Dec 26, 2008 at 11:05 PM, Glen Barber > wrote: > >> On Fri, Dec 26, 2008 at 5:02 PM, t-u-t wrote: >>> hi, >>> i have a quick question and don't know what this problem is >>> related to. >>> >>> i am getting an error on *every* port i try to build -- Script >> "configure" >>> failed unexpectedly. etc,etc, please check log. >>> >>> searching the net i am finding pages on particular ports (not same >>> as >> mine >>> yet) -- but baffled as to why every port giving this error. >>> >>> I have no clue what is in these log files and was wondering >>> whether the >>> "unknown' entries is normal at "/bin/arch=" below. >>> >>> this below is the topmost part of config.log and just noticed the >>> parts >> with >>> win32 and don't know what that means. >>> >>> the very last line in the log file reads configure. exit 77. >>> >> >> Is there anything odd in /etc/make.conf ? Are your ports up to date? >> >> >> -- >> Glen Barber >> > > > ports are updated, yes, and make.conf has some settings but have to > check, > since i'm new and used a copy of the example file and have to check > what is > enabled. this is a quick reply cuz i just noticed a previous error > messge > stating - > " C compiler cannot create executables " > > tried a couple of ports, they have this error > > thanks > > make.conf > > CFLAGS= -O -pipe > MAKE_SHELL?=sh > COPTFLAGS= -O -pipe > > WITH_XINERAMA="YES" > WITH_GNOME="YES" > WITH_DOCHTML="YES" > WITH_IMLIB2="YES" > -- > ce la vie A config.log file would help too.. -Garrett From w8hdkim at gmail.com Fri Dec 26 16:03:24 2008 From: w8hdkim at gmail.com (Kim Culhan) Date: Fri Dec 26 16:11:17 2008 Subject: 7.1-RC2 audio/x11amp missing symbol at startup In-Reply-To: <54BC6DF8-BEC3-4133-8394-9FEF055E8A4A@gmail.com> References: <89dbfdc30812261253sd13d85fn9d2c079d644818b@mail.gmail.com> <54BC6DF8-BEC3-4133-8394-9FEF055E8A4A@gmail.com> Message-ID: <89dbfdc30812261603y20f262a8g7f6d3cb52605ec24@mail.gmail.com> On Fri, Dec 26, 2008 at 4:42 PM, Garrett Cooper wrote: > On Dec 26, 2008, at 12:53, "Kim Culhan" wrote: > >> Using the ports tree cvsup'd 12-26-08 running on FreeBSD 7.1-RC2 >> >> At startup audio/x11amp returns: >> >> /usr/local/lib/x11amp/Input/libwav.so: Undefined symbol "effects_enabled" >> /usr/local/lib/x11amp/Input/libmpg123.so: Undefined symbol >> "effects_enabled" >> /usr/local/lib/x11amp/Input/libmikmod.so: Undefined symbol >> "effects_enabled" >> Gdk-ERROR **: BadMatch (invalid parameter attributes) >> serial 82 error_code 8 request_code 2 minor_code 0 >> >> Anyone else seeing this? > > How did you initially install freebsd? What version did you install? What > versions were your ports compiled against? FreeBSD was newly installed directly from 7.1-RC2-i386-disc1.iso cvsup was installed as a package and was then run to bring the ports tree up to the latest. The gnome2-lite port was then installed, followed by /audio/x11amp x11amp was then run and returned the result above. An attempt was made previously where the same iso was installed followed by x11-wm/windowmaker. x11amp was installed next and run with the same result. thanks -kim -- From erwin at FreeBSD.org Fri Dec 26 17:13:45 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Fri Dec 26 17:13:57 2008 Subject: INDEX build failed for 6.x Message-ID: <200812270113.mBR1Dd97071246@pointyhat.freebsd.org> INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: py25-clutter-0.8.0: no entry for /usr/ports//graphics/clutter-gtk make_index: py25-clutter-0.8.0: no entry for /usr/ports//graphics/clutter-gtk Committers on the hook: danfe miwi pav Most recent CVS update was: U deskutils/Makefile U deskutils/ganyremote/Makefile U deskutils/ganyremote/distinfo U deskutils/ganyremote/pkg-descr U deskutils/ganyremote/pkg-plist U devel/antlrworks/Makefile U devel/antlrworks/distinfo U devel/etl/Makefile U devel/etl/distinfo U devel/synfig/Makefile U devel/synfig/distinfo U devel/synfig/pkg-plist U games/pokerth/Makefile U games/pokerth/distinfo U games/pokerth/pkg-plist U graphics/Makefile U graphics/clutter/Makefile U graphics/clutter/distinfo U graphics/clutter/pkg-descr U graphics/clutter/pkg-plist U graphics/clutter-box2d/Makefile U graphics/clutter-box2d/distinfo U graphics/clutter-box2d/pkg-descr U graphics/clutter-box2d/pkg-plist U graphics/clutter-cairo/Makefile U graphics/clutter-cairo/distinfo U graphics/clutter-cairo/pkg-descr U graphics/clutter-cairo/pkg-plist U graphics/clutter-gtk/Makefile U graphics/clutter-gtk/distinfo U graphics/clutter-gtk/pkg-descr U graphics/clutter-gtk/pkg-plist U graphics/p5-clutter/Makefile U graphics/p5-clutter/distinfo U graphics/p5-clutter/pkg-descr U graphics/p5-clutter/pkg-plist U graphics/py-clutter/Makefile U graphics/py-clutter/distinfo U graphics/py-clutter/pkg-descr U graphics/py-clutter/pkg-plist U graphics/synfigstudio/Makefile U graphics/synfigstudio/distinfo U graphics/synfigstudio/pkg-plist U lang/cython/Makefile U lang/cython/distinfo U multimedia/Makefile U multimedia/clutter-gst/Makefile U multimedia/clutter-gst/distinfo U multimedia/clutter-gst/pkg-descr U multimedia/clutter-gst/pkg-plist U net-im/gajim/Makefile U net-im/gajim/distinfo U net-im/gajim/pkg-plist U net-im/gajim/files/patch-data-Makefile.in U net-im/gajim/files/patch-src-Makefile.in U print/fontforge/Makefile U print/fontforge/distinfo U print/fontforge/pkg-plist U print/fontforge/files/patch-fontforge::Makefile.dynamic.in U science/gchemutils/Makefile U security/dropbear/Makefile U security/dropbear/distinfo U security/switzerland/Makefile U security/switzerland/distinfo U sysutils/syscp/pkg-plist U www/ilias/Makefile U www/ilias/distinfo U www/mediawiki12/Makefile U www/mediawiki12/distinfo U www/pear-Services_Facebook/Makefile U www/pear-Services_Facebook/distinfo U www/typo3/Makefile U www/typo3/distinfo From marshc187 at gmail.com Fri Dec 26 17:38:42 2008 From: marshc187 at gmail.com (t-u-t) Date: Fri Dec 26 17:38:50 2008 Subject: general ports problem In-Reply-To: <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> Message-ID: <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> On Sat, Dec 27, 2008 at 12:53 AM, Garrett Cooper wrote: > On Dec 26, 2008, at 14:33, t-u-t wrote: > > On Fri, Dec 26, 2008 at 11:05 PM, Glen Barber > >wrote: >> >> On Fri, Dec 26, 2008 at 5:02 PM, t-u-t wrote: >>> >>>> hi, >>>> i have a quick question and don't know what this problem is related to. >>>> >>>> i am getting an error on *every* port i try to build -- Script >>>> >>> "configure" >>> >>>> failed unexpectedly. etc,etc, please check log. >>>> >>>> searching the net i am finding pages on particular ports (not same as >>>> >>> mine >>> >>>> yet) -- but baffled as to why every port giving this error. >>>> >>>> I have no clue what is in these log files and was wondering whether the >>>> "unknown' entries is normal at "/bin/arch=" below. >>>> >>>> this below is the topmost part of config.log and just noticed the parts >>>> >>> with >>> >>>> win32 and don't know what that means. >>>> >>>> the very last line in the log file reads configure. exit 77. >>>> >>>> >>> Is there anything odd in /etc/make.conf ? Are your ports up to date? >>> >>> >>> -- >>> Glen Barber >>> >>> >> >> ports are updated, yes, and make.conf has some settings but have to check, >> since i'm new and used a copy of the example file and have to check what >> is >> enabled. this is a quick reply cuz i just noticed a previous error messge >> stating - >> " C compiler cannot create executables " >> >> tried a couple of ports, they have this error >> >> thanks >> >> make.conf >> >> CFLAGS= -O -pipe >> MAKE_SHELL?=sh >> COPTFLAGS= -O -pipe >> >> WITH_XINERAMA="YES" >> WITH_GNOME="YES" >> WITH_DOCHTML="YES" >> WITH_IMLIB2="YES" >> -- >> ce la vie >> > > A config.log file would help too.. > -Garrett > oh, i thought that would be too long. i have attached one from a port i just chose at random now. for the record, i was building/updating ports just fine till a few days ago. i csup'd src and built world+kernel early this week, but still updated a couple of ports fine after that. besides that, only other changes to my system was adding kde4 (through packages) to tryit out, then deleted that plus qt4 stuff with pkg_delete. this is the error using /ports/mail/fetchmail (( /usr/ports/mail/fetchmail/work/fetchmail-6.3.8/config.log )) ce la vie From yanefbsd at gmail.com Fri Dec 26 17:43:32 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 26 17:43:38 2008 Subject: 7.1-RC2 audio/x11amp missing symbol at startup In-Reply-To: References: <89dbfdc30812261253sd13d85fn9d2c079d644818b@mail.gmail.com> <54BC6DF8-BEC3-4133-8394-9FEF055E8A4A@gmail.com> <89dbfdc30812261603y20f262a8g7f6d3cb52605ec24@mail.gmail.com> Message-ID: <7d6fde3d0812261743l1b19dbbao33443c2f1077cb1d@mail.gmail.com> On Fri, Dec 26, 2008 at 5:35 PM, Garrett Cooper wrote: > On Dec 26, 2008, at 16:03, "Kim Culhan" wrote: > >> On Fri, Dec 26, 2008 at 4:42 PM, Garrett Cooper >> wrote: >>> >>> On Dec 26, 2008, at 12:53, "Kim Culhan" wrote: >>> >>>> Using the ports tree cvsup'd 12-26-08 running on FreeBSD 7.1-RC2 >>>> >>>> At startup audio/x11amp returns: >>>> >>>> /usr/local/lib/x11amp/Input/libwav.so: Undefined symbol >>>> "effects_enabled" >>>> /usr/local/lib/x11amp/Input/libmpg123.so: Undefined symbol >>>> "effects_enabled" >>>> /usr/local/lib/x11amp/Input/libmikmod.so: Undefined symbol >>>> "effects_enabled" >>>> Gdk-ERROR **: BadMatch (invalid parameter attributes) >>>> serial 82 error_code 8 request_code 2 minor_code 0 >>>> >>>> Anyone else seeing this? >>> >>> How did you initially install freebsd? What version did you install? What >>> versions were your ports compiled against? >> >> FreeBSD was newly installed directly from 7.1-RC2-i386-disc1.iso >> >> cvsup was installed as a package and was then run to bring the ports tree >> up to the latest. >> >> The gnome2-lite port was then installed, followed by /audio/x11amp >> >> x11amp was then run and returned the result above. >> >> An attempt was made previously where the same iso was installed >> followed by x11-wm/windowmaker. x11amp was installed next and run >> with the same result. >> >> thanks >> -kim > > Actually, let's try a better test -- do export > LD_LIBRARY_PATH="/usr/local/lib" Sorry, my iPhone cut off my last message. Let's try this again... Do the following steps to see whether or not things work: 1. Open up a terminal. 2. Do: export LD_LIBRARY_PATH="/usr/local/lib:/usr/local/lib/x11amp/Input/"; x11amp does this work? If so, proceed to 3. 3. Do: export LD_LIBRARY_PATH="/usr/local/lib"; x11amp does this work? These are tests to eliminate potential runtime linker issues with compiled apps. Thanks, -Garrett From w8hdkim at gmail.com Fri Dec 26 18:55:13 2008 From: w8hdkim at gmail.com (Kim Culhan) Date: Fri Dec 26 18:55:20 2008 Subject: 7.1-RC2 audio/x11amp missing symbol at startup In-Reply-To: <89dbfdc30812261851m30fa9fc6g512bfdf63cd00634@mail.gmail.com> References: <89dbfdc30812261253sd13d85fn9d2c079d644818b@mail.gmail.com> <54BC6DF8-BEC3-4133-8394-9FEF055E8A4A@gmail.com> <89dbfdc30812261603y20f262a8g7f6d3cb52605ec24@mail.gmail.com> <7d6fde3d0812261743l1b19dbbao33443c2f1077cb1d@mail.gmail.com> <89dbfdc30812261851m30fa9fc6g512bfdf63cd00634@mail.gmail.com> Message-ID: <89dbfdc30812261855g10354b12w2d287b44b4460b72@mail.gmail.com> On Fri, Dec 26, 2008 at 8:43 PM, Garrett Cooper wrote: > On Fri, Dec 26, 2008 at 5:35 PM, Garrett Cooper wrote: >> On Dec 26, 2008, at 16:03, "Kim Culhan" wrote: >> >>> On Fri, Dec 26, 2008 at 4:42 PM, Garrett Cooper >>> wrote: >>>> >>>> On Dec 26, 2008, at 12:53, "Kim Culhan" wrote: >>>> >>>>> Using the ports tree cvsup'd 12-26-08 running on FreeBSD 7.1-RC2 >>>>> >>>>> At startup audio/x11amp returns: >>>>> >>>>> /usr/local/lib/x11amp/Input/libwav.so: Undefined symbol >>>>> "effects_enabled" >>>>> /usr/local/lib/x11amp/Input/libmpg123.so: Undefined symbol >>>>> "effects_enabled" >>>>> /usr/local/lib/x11amp/Input/libmikmod.so: Undefined symbol >>>>> "effects_enabled" >>>>> Gdk-ERROR **: BadMatch (invalid parameter attributes) >>>>> serial 82 error_code 8 request_code 2 minor_code 0 >>>>> >>>>> Anyone else seeing this? > Sorry, my iPhone cut off my last message. Let's try this again... > > Do the following steps to see whether or not things work: > > 1. Open up a terminal. > 2. Do: > export LD_LIBRARY_PATH="/usr/local/lib:/usr/local/lib/x11amp/Input/"; > x11amp > > does this work? If so, proceed to 3. No does not, the problem appears to be the shared libraries: /usr/local/lib/x11amp/Input/libwav.so /usr/local/lib/x11amp/Input/libmpg123.so /usr/local/lib/x11amp/Input/libmikmod.so as the error message states, have an undefined symbol: "effects_enabled" nm /usr/local/lib/x11amp/Input/libmpg123 | grep effects U effects_enabled It looks like this is related to linking with -pthread which appears to be a problem in fbsd 7.1 -kim -- From yanefbsd at gmail.com Fri Dec 26 18:55:31 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 26 18:55:38 2008 Subject: 7.1-RC2 audio/x11amp missing symbol at startup In-Reply-To: <89dbfdc30812261851m30fa9fc6g512bfdf63cd00634@mail.gmail.com> References: <89dbfdc30812261253sd13d85fn9d2c079d644818b@mail.gmail.com> <54BC6DF8-BEC3-4133-8394-9FEF055E8A4A@gmail.com> <89dbfdc30812261603y20f262a8g7f6d3cb52605ec24@mail.gmail.com> <7d6fde3d0812261743l1b19dbbao33443c2f1077cb1d@mail.gmail.com> <89dbfdc30812261851m30fa9fc6g512bfdf63cd00634@mail.gmail.com> Message-ID: <7d6fde3d0812261855m75816888ga476edac2c56b6e6@mail.gmail.com> On Fri, Dec 26, 2008 at 6:51 PM, Kim Culhan wrote: > On Fri, Dec 26, 2008 at 8:43 PM, Garrett Cooper wrote: >> On Fri, Dec 26, 2008 at 5:35 PM, Garrett Cooper wrote: >>> On Dec 26, 2008, at 16:03, "Kim Culhan" wrote: >>> >>>> On Fri, Dec 26, 2008 at 4:42 PM, Garrett Cooper >>>> wrote: >>>>> >>>>> On Dec 26, 2008, at 12:53, "Kim Culhan" wrote: >>>>> >>>>>> Using the ports tree cvsup'd 12-26-08 running on FreeBSD 7.1-RC2 >>>>>> >>>>>> At startup audio/x11amp returns: >>>>>> >>>>>> /usr/local/lib/x11amp/Input/libwav.so: Undefined symbol >>>>>> "effects_enabled" >>>>>> /usr/local/lib/x11amp/Input/libmpg123.so: Undefined symbol >>>>>> "effects_enabled" >>>>>> /usr/local/lib/x11amp/Input/libmikmod.so: Undefined symbol >>>>>> "effects_enabled" >>>>>> Gdk-ERROR **: BadMatch (invalid parameter attributes) >>>>>> serial 82 error_code 8 request_code 2 minor_code 0 >>>>>> >>>>>> Anyone else seeing this? >> Sorry, my iPhone cut off my last message. Let's try this again... >> >> Do the following steps to see whether or not things work: >> >> 1. Open up a terminal. >> 2. Do: >> export LD_LIBRARY_PATH="/usr/local/lib:/usr/local/lib/x11amp/Input/"; >> x11amp >> >> does this work? If so, proceed to 3. > > No does not, the problem appears to be the shared libraries: > > /usr/local/lib/x11amp/Input/libwav.so > /usr/local/lib/x11amp/Input/libmpg123.so > /usr/local/lib/x11amp/Input/libmikmod.so > > as the error message states, have an undefined symbol: "effects_enabled" > > nm /usr/local/lib/x11amp/Input/libmpg123 | grep effects > U effects_enabled > > It looks like this is related to linking with -pthread which appears to > be a problem in fbsd 7.1 > > -kim -pthread should *not* be used. According to the gcc manpage it's HP-alpha specific... Is it actually implemented in the author's makefiles? -Garrett From yanefbsd at gmail.com Fri Dec 26 19:00:52 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 26 19:00:58 2008 Subject: vpnc connects, but does not work In-Reply-To: <49521954.BcMAlOlPOLu7CRKx%perryh@pluto.rain.com> References: <49521954.BcMAlOlPOLu7CRKx%perryh@pluto.rain.com> Message-ID: <7d6fde3d0812261900q5a647f5l3782264aba604199@mail.gmail.com> On Wed, Dec 24, 2008 at 3:13 AM, wrote: > I have installed vpnc to connect to an employer's Cisco VPN > system, and it seems to make the connection, but after connecting > I can't ping the gateway nor anything beyond it. The symptom > seems to resemble what is described in the Routing section of > http://www.cs.rpi.edu/~flemej/fbsd-cisco-vpn.pdf, but since that > is using a completely different setup on the FreeBSD side I have > no idea whether the remedy described there is applicable (nor, > if it is, how to determine the addresses to use in this case). > > Does this look at all familiar to anyone? I didn't find anything > that seemed applicable in recent ports@ or questions@ archives. > (I have XX'd out potentially-sensitive material in the following.) I have no idea since I haven't used vpnc, yet, but have you tried tracerouting a connection and/or using tcpdump? Cheers, -Garrett From erwin at FreeBSD.org Fri Dec 26 20:28:59 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Fri Dec 26 20:29:06 2008 Subject: INDEX build failed for 6.x Message-ID: <200812270428.mBR4SrvN092715@pointyhat.freebsd.org> INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: py25-clutter-0.8.0: no entry for /usr/ports//graphics/clutter-gtk make_index: py25-clutter-0.8.0: no entry for /usr/ports//graphics/clutter-gtk Committers on the hook: beech danfe miwi pav pgollucci wxs Most recent CVS update was: U audio/firefly/Makefile U audio/firefly/files/mt-daapd.in U net/vnc/Makefile U net/vnc/distinfo U www/Makefile U www/rt2/Makefile U www/rt32/Makefile U www/rt34/Makefile U www/rt36/Makefile U www/rt38/Makefile U www/rt38/Makefile.cpan U www/rt38/distinfo U www/rt38/pkg-deinstall U www/rt38/pkg-descr U www/rt38/pkg-install U www/rt38/pkg-plist U www/rt38/files/patch-Makefile.in U www/rt38/files/patch-aclocal.m4 U www/rt38/files/pkg-message.in From perryh at pluto.rain.com Fri Dec 26 20:48:50 2008 From: perryh at pluto.rain.com (perryh@pluto.rain.com) Date: Fri Dec 26 20:48:57 2008 Subject: vpnc connects, but does not work In-Reply-To: <7d6fde3d0812261900q5a647f5l3782264aba604199@mail.gmail.com> References: <49521954.BcMAlOlPOLu7CRKx%perryh@pluto.rain.com> <7d6fde3d0812261900q5a647f5l3782264aba604199@mail.gmail.com> Message-ID: <4955b272.MWjQx+xO4J2XXL7M%perryh@pluto.rain.com> > > I have installed vpnc to connect to an employer's Cisco > > VPN system, and it seems to make the connection, but after > > connecting I can't ping the gateway nor anything beyond it ... > > > > Does this look at all familiar to anyone? > > I have no idea since I haven't used vpnc, yet, but have you > tried tracerouting a connection and/or using tcpdump? Traceroute to YYY.YYY.127.228, which I guess is the concentrator's public IP address, produces the same 14-hop result whether connected or disconnected (modulo the need to use "traceroute -n" while connected: vpnc replaces /etc/resolv.conf with one specifying only the corporate nameservers, and I can't reach them with the link not working, so there is no name service while connected). Traceroute to the tun0 IP address, while connected, produced nothing: $ traceroute -n ZZZ.ZZZ.233.42 traceroute to ZZZ.ZZZ.233.42 (ZZZ.ZZZ.233.42), 64 hops max, 40 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * ^C What seems truly bizarre is that, while connected, I couldn't ping the tun0 interface: $ ping ZZZ.ZZZ.233.42 PING ZZZ.ZZZ.233.42 (ZZZ.ZZZ.233.42): 56 data bytes ^C --- ZZZ.ZZZ.233.42 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss even though it was reported as up: $ ifconfig -a ... tun0: flags=8051 mtu 1412 inet6 fe80::2b0:d0ff:fe28:ad4f%tun0 prefixlen 64 scopeid 0x4 inet ZZZ.ZZZ.233.42 --> ZZZ.ZZZ.233.42 netmask 0xffffffff Opened by PID 24635 Shouldn't a local interface, reported as up, *always* respond to a ping of its own IP address? What could cause it not to do so? From peterjeremy at optushome.com.au Fri Dec 26 23:09:26 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Fri Dec 26 23:09:32 2008 Subject: general ports problem In-Reply-To: <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> Message-ID: <20081227065709.GA54990@server.vk2pj.dyndns.org> On 2008-Dec-27 02:38:41 +0100, t-u-t wrote: >On Sat, Dec 27, 2008 at 12:53 AM, Garrett Cooper wrote: >> A config.log file would help too.. >oh, i thought that would be too long. i have attached one from a port i just >chose at random now. Unfortunately, it got deleted by mailman. Can you post one of the shorter logs somewhere (eg pastebin.ca). Also, what does 'gcc -V' report and can you manually compile (eg) a "hello world" program. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081227/444baf32/attachment.pgp From erwin at FreeBSD.org Fri Dec 26 23:17:38 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Fri Dec 26 23:17:47 2008 Subject: INDEX build failed for 6.x Message-ID: <200812270717.mBR7HWR3042645@pointyhat.freebsd.org> INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: py25-clutter-0.8.0: no entry for /usr/ports//graphics/clutter-gtk make_index: py25-clutter-0.8.0: no entry for /usr/ports//graphics/clutter-gtk Committers on the hook: beech danfe gerald miwi pav pgollucci wxs Most recent CVS update was: U GIDs U UPDATING U devel/strace/Makefile U devel/strace/files/patch-net.c U devel/strace/files/patch-syscall.c U devel/strace/files/patch-time.c U lang/gcc43/Makefile U lang/gcc43/distinfo U www/rt38/Makefile U www/rt38/files/extra-patch-noportdocs-Makefile.in U www/rt38/files/pkg-message.in From yanefbsd at gmail.com Sat Dec 27 00:27:54 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sat Dec 27 00:28:01 2008 Subject: general ports problem In-Reply-To: <20081227065709.GA54990@server.vk2pj.dyndns.org> References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> <20081227065709.GA54990@server.vk2pj.dyndns.org> Message-ID: <9268DAD1-17B4-4FCF-8A5B-8083933F4D60@gmail.com> On Dec 26, 2008, at 22:57, Peter Jeremy wrote: > On 2008-Dec-27 02:38:41 +0100, t-u-t wrote: >> On Sat, Dec 27, 2008 at 12:53 AM, Garrett Cooper >> wrote: >>> A config.log file would help too.. >> oh, i thought that would be too long. i have attached one from a >> port i just >> chose at random now. > > Unfortunately, it got deleted by mailman. Can you post one of the > shorter logs somewhere (eg pastebin.ca). Also, what does 'gcc -V' > report and can you manually compile (eg) a "hello world"? He's using the stock compiler and it appears that ld is screwed up because it fires back an error when linking. I'll forward you the log in my next email. Thanks, -Garrett From erwin at FreeBSD.org Sat Dec 27 01:58:11 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Sat Dec 27 01:58:17 2008 Subject: INDEX build failed for 6.x Message-ID: <200812270958.mBR9w5Qq019529@pointyhat.freebsd.org> INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: py25-clutter-0.8.0: no entry for /usr/ports//graphics/clutter-gtk make_index: py25-clutter-0.8.0: no entry for /usr/ports//graphics/clutter-gtk Committers on the hook: beech danfe gerald miwi novel pav pgollucci wxs Most recent CVS update was: U mail/msmtp/Makefile U mail/msmtp/distinfo From mail at ozzmosis.com Sat Dec 27 03:18:11 2008 From: mail at ozzmosis.com (andrew clarke) Date: Sat Dec 27 03:18:18 2008 Subject: Unable to build strace-4.5.18 under FreeBSD 6.4 In-Reply-To: <20081226155704.GA45251@ozzmosis.com> References: <20081226155704.GA45251@ozzmosis.com> Message-ID: <20081227111807.GA67410@ozzmosis.com> On Sat 2008-12-27 02:57:04 UTC+1100, andrew clarke (mail@ozzmosis.com) wrote: > ===> Building for strace-4.5.18 > make all-am > cc -DHAVE_CONFIG_H -I. -Ifreebsd/i386 -I./freebsd/i386 -Ifreebsd -I./freebsd -Wall -O2 -fno-strict-aliasing -pipe -MT strace.o -MD -MP -MF .deps/strace.Tpo -c -o strace.o strace.c > mv -f .deps/strace.Tpo .deps/strace.Po > cc -DHAVE_CONFIG_H -I. -Ifreebsd/i386 -I./freebsd/i386 -Ifreebsd -I./freebsd -Wall -O2 -fno-strict-aliasing -pipe -MT syscall.o -MD -MP -MF .deps/syscall.Tpo -c -o syscall.o syscall.c > syscall.c: In function `internal_syscall': > syscall.c:719: error: `sys_waitpid' undeclared (first use in this function) > syscall.c:719: error: (Each undeclared identifier is reported only once > syscall.c:719: error: for each function it appears in.) > *** Error code 1 Update: Fixed in strace-4.5.18_1. Thanks! From erwin at FreeBSD.org Sat Dec 27 04:57:44 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Sat Dec 27 04:57:51 2008 Subject: INDEX build failed for 6.x Message-ID: <200812271257.mBRCvbU9037407@pointyhat.freebsd.org> INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: py25-clutter-0.8.0: no entry for /usr/ports//graphics/clutter-gtk make_index: py25-clutter-0.8.0: no entry for /usr/ports//graphics/clutter-gtk Committers on the hook: beech danfe gerald itetcu miwi novel pav pgollucci wxs Most recent CVS update was: U emulators/wine/pkg-descr U www/opera/files/operapluginwrapper From marshc187 at gmail.com Sat Dec 27 05:10:30 2008 From: marshc187 at gmail.com (t-u-t) Date: Sat Dec 27 05:10:37 2008 Subject: general ports problem In-Reply-To: <9268DAD1-17B4-4FCF-8A5B-8083933F4D60@gmail.com> References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> <20081227065709.GA54990@server.vk2pj.dyndns.org> <9268DAD1-17B4-4FCF-8A5B-8083933F4D60@gmail.com> Message-ID: <332f78510812270510x291812c3p973761815c3984b3@mail.gmail.com> On Sat, Dec 27, 2008 at 9:27 AM, Garrett Cooper wrote: > On Dec 26, 2008, at 22:57, Peter Jeremy > wrote: > > On 2008-Dec-27 02:38:41 +0100, t-u-t wrote: >> >>> On Sat, Dec 27, 2008 at 12:53 AM, Garrett Cooper >>> wrote: >>> >>>> A config.log file would help too.. >>>> >>> oh, i thought that would be too long. i have attached one from a port i >>> just >>> chose at random now. >>> >> >> Unfortunately, it got deleted by mailman. Can you post one of the >> shorter logs somewhere (eg pastebin.ca). Also, what does 'gcc -V' >> report and can you manually compile (eg) a "hello world"? >> > > He's using the stock compiler and it appears that ld is screwed up because > it fires back an error when linking. I'll forward you the log in my next > email. > Thanks, > -Garrett > i tried hello world, here's the output. $ gcc -Wall hello.c -o hello /usr/bin/ld:built in linker script:2: syntax error -- ce la vie From erwin at FreeBSD.org Sat Dec 27 07:59:14 2008 From: erwin at FreeBSD.org (Erwin Lansing) Date: Sat Dec 27 07:59:20 2008 Subject: INDEX now builds successfully on 6.x Message-ID: <200812271559.mBRFx8rX089960@pointyhat.freebsd.org> From yanefbsd at gmail.com Sat Dec 27 08:58:27 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sat Dec 27 08:58:33 2008 Subject: general ports problem In-Reply-To: <332f78510812270510x291812c3p973761815c3984b3@mail.gmail.com> References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> <20081227065709.GA54990@server.vk2pj.dyndns.org> <9268DAD1-17B4-4FCF-8A5B-8083933F4D60@gmail.com> <332f78510812270510x291812c3p973761815c3984b3@mail.gmail.com> Message-ID: On Dec 27, 2008, at 5:10, t-u-t wrote: > > > On Sat, Dec 27, 2008 at 9:27 AM, Garrett Cooper > wrote: > On Dec 26, 2008, at 22:57, Peter Jeremy > wrote: > > On 2008-Dec-27 02:38:41 +0100, t-u-t wrote: > On Sat, Dec 27, 2008 at 12:53 AM, Garrett Cooper > wrote: > A config.log file would help too.. > oh, i thought that would be too long. i have attached one from a > port i just > chose at random now. > > Unfortunately, it got deleted by mailman. Can you post one of the > shorter logs somewhere (eg pastebin.ca). Also, what does 'gcc -V' > report and can you manually compile (eg) a "hello world"? > > He's using the stock compiler and it appears that ld is screwed up > because it fires back an error when linking. I'll forward you the > log in my next email. > Thanks, > -Garrett > > i tried hello world, here's the output. > > $ gcc -Wall hello.c -o hello > /usr/bin/ld:built in linker script:2: syntax error > -- > ce la vie Yup. Your binutils is hosed :(. -Garrett From marshc187 at gmail.com Sat Dec 27 09:04:26 2008 From: marshc187 at gmail.com (cwt) Date: Sat Dec 27 09:04:34 2008 Subject: general ports problem In-Reply-To: References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> <20081227065709.GA54990@server.vk2pj.dyndns.org> <9268DAD1-17B4-4FCF-8A5B-8083933F4D60@gmail.com> <332f78510812270510x291812c3p973761815c3984b3@mail.gmail.com> Message-ID: <49565FFF.5070203@gmail.com> Garrett Cooper wrote: > On Dec 27, 2008, at 5:10, t-u-t > wrote: > >> >> >> On Sat, Dec 27, 2008 at 9:27 AM, Garrett Cooper > > wrote: >> >> On Dec 26, 2008, at 22:57, Peter Jeremy >> > > wrote: >> >> On 2008-Dec-27 02:38:41 +0100, t-u-t > > wrote: >> >> On Sat, Dec 27, 2008 at 12:53 AM, Garrett Cooper >> > wrote: >> >> A config.log file would help too.. >> >> oh, i thought that would be too long. i have attached one >> from a port i just >> chose at random now. >> >> >> Unfortunately, it got deleted by mailman. Can you post one >> of the >> shorter logs somewhere (eg pastebin.ca ). >> Also, what does 'gcc -V' >> report and can you manually compile (eg) a "hello world"? >> >> >> He's using the stock compiler and it appears that ld is screwed >> up because it fires back an error when linking. I'll forward you >> the log in my next email. >> Thanks, >> -Garrett >> >> >> i tried hello world, here's the output. >> >> $ gcc -Wall hello.c -o hello >> /usr/bin/ld:built in linker script:2: syntax error >> -- >> ce la vie > > Yup. Your binutils is hosed :(. > -Garrett thanks for your help. i tried to give buildworld a try a moment ago before anything, but also got the above ld error. From yanefbsd at gmail.com Sat Dec 27 09:08:02 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sat Dec 27 09:08:11 2008 Subject: general ports problem In-Reply-To: <49565FFF.5070203@gmail.com> References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> <20081227065709.GA54990@server.vk2pj.dyndns.org> <9268DAD1-17B4-4FCF-8A5B-8083933F4D60@gmail.com> <332f78510812270510x291812c3p973761815c3984b3@mail.gmail.com> <49565FFF.5070203@gmail.com> Message-ID: <8A06544D-6E9C-4F00-A2FB-74D9627BCF9F@gmail.com> On Dec 27, 2008, at 9:03, cwt wrote: > Garrett Cooper wrote: >> On Dec 27, 2008, at 5:10, t-u-t > >> wrote: >> >>> >>> >>> On Sat, Dec 27, 2008 at 9:27 AM, Garrett Cooper >>> > wrote: >>> >>> On Dec 26, 2008, at 22:57, Peter Jeremy >>> >> > wrote: >>> >>> On 2008-Dec-27 02:38:41 +0100, t-u-t >> > wrote: >>> >>> On Sat, Dec 27, 2008 at 12:53 AM, Garrett Cooper >>> > wrote: >>> >>> A config.log file would help too.. >>> >>> oh, i thought that would be too long. i have attached one >>> from a port i just >>> chose at random now. >>> >>> >>> Unfortunately, it got deleted by mailman. Can you post one >>> of the >>> shorter logs somewhere (eg pastebin.ca ). >>> Also, what does 'gcc -V' >>> report and can you manually compile (eg) a "hello world"? >>> >>> >>> He's using the stock compiler and it appears that ld is screwed >>> up because it fires back an error when linking. I'll forward you >>> the log in my next email. >>> Thanks, >>> -Garrett >>> >>> >>> i tried hello world, here's the output. >>> >>> $ gcc -Wall hello.c -o hello >>> /usr/bin/ld:built in linker script:2: syntax error >>> -- >>> ce la vie >> >> Yup. Your binutils is hosed :(. >> -Garrett > thanks for your help. > i tried to give buildworld a try a moment ago before anything, but > also got the above ld error. > From yanefbsd at gmail.com Sat Dec 27 09:12:32 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sat Dec 27 09:12:39 2008 Subject: general ports problem In-Reply-To: <49565FFF.5070203@gmail.com> References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> <20081227065709.GA54990@server.vk2pj.dyndns.org> <9268DAD1-17B4-4FCF-8A5B-8083933F4D60@gmail.com> <332f78510812270510x291812c3p973761815c3984b3@mail.gmail.com> <49565FFF.5070203@gmail.com> Message-ID: <1A5D46CF-986E-45BB-A889-34ABC6F3C684@gmail.com> On Dec 27, 2008, at 9:03, cwt wrote: > Garrett Cooper wrote: >> On Dec 27, 2008, at 5:10, t-u-t > >> wrote: >> >>> >>> >>> On Sat, Dec 27, 2008 at 9:27 AM, Garrett Cooper >>> > wrote: >>> >>> On Dec 26, 2008, at 22:57, Peter Jeremy >>> >> > wrote: >>> >>> On 2008-Dec-27 02:38:41 +0100, t-u-t >> > wrote: >>> >>> On Sat, Dec 27, 2008 at 12:53 AM, Garrett Cooper >>> > wrote: >>> >>> A config.log file would help too.. >>> >>> oh, i thought that would be too long. i have attached one >>> from a port i just >>> chose at random now. >>> >>> >>> Unfortunately, it got deleted by mailman. Can you post one >>> of the >>> shorter logs somewhere (eg pastebin.ca ). >>> Also, what does 'gcc -V' >>> report and can you manually compile (eg) a "hello world"? >>> >>> >>> He's using the stock compiler and it appears that ld is screwed >>> up because it fires back an error when linking. I'll forward you >>> the log in my next email. >>> Thanks, >>> -Garrett >>> >>> >>> i tried hello world, here's the output. >>> >>> $ gcc -Wall hello.c -o hello >>> /usr/bin/ld:built in linker script:2: syntax error >>> -- >>> ce la vie >> >> Yup. Your binutils is hosed :(. >> -Garrett > thanks for your help. > i tried to give buildworld a try a moment ago before anything, but > also got the above ld error. I'd just reinstall the developer package from sysinstall to be honest. That should do the trick. Then we wash, rinse, and repeat all the steps to get a working ports install of stuff. The question is how did binutils get fubared? -Garrett From marshc187 at gmail.com Sat Dec 27 13:27:24 2008 From: marshc187 at gmail.com (cwt) Date: Sat Dec 27 13:27:30 2008 Subject: general ports problem In-Reply-To: <1A5D46CF-986E-45BB-A889-34ABC6F3C684@gmail.com> References: <332f78510812261402m289b6130qb56e5625258fb2f2@mail.gmail.com> <4ad871310812261405k4db568bch768bb61439b8bc25@mail.gmail.com> <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> <20081227065709.GA54990@server.vk2pj.dyndns.org> <9268DAD1-17B4-4FCF-8A5B-8083933F4D60@gmail.com> <332f78510812270510x291812c3p973761815c3984b3@mail.gmail.com> <49565FFF.5070203@gmail.com> <1A5D46CF-986E-45BB-A889-34ABC6F3C684@gmail.com> Message-ID: <49569DA9.6050305@gmail.com> Garrett Cooper wrote: > On Dec 27, 2008, at 9:03, cwt wrote: > >> Garrett Cooper wrote: >>> On Dec 27, 2008, at 5:10, t-u-t >> > wrote: >>> >>>> >>>> >>>> On Sat, Dec 27, 2008 at 9:27 AM, Garrett Cooper >>> > wrote: >>>> >>>> On Dec 26, 2008, at 22:57, Peter Jeremy >>>> >>> > wrote: >>>> >>>> On 2008-Dec-27 02:38:41 +0100, t-u-t >>> > wrote: >>>> >>>> On Sat, Dec 27, 2008 at 12:53 AM, Garrett Cooper >>>> > wrote: >>>> >>>> A config.log file would help too.. >>>> >>>> oh, i thought that would be too long. i have attached one >>>> from a port i just >>>> chose at random now. >>>> >>>> >>>> Unfortunately, it got deleted by mailman. Can you post one >>>> of the >>>> shorter logs somewhere (eg pastebin.ca ). >>>> Also, what does 'gcc -V' >>>> report and can you manually compile (eg) a "hello world"? >>>> >>>> >>>> He's using the stock compiler and it appears that ld is screwed >>>> up because it fires back an error when linking. I'll forward you >>>> the log in my next email. >>>> Thanks, >>>> -Garrett >>>> >>>> >>>> i tried hello world, here's the output. >>>> >>>> $ gcc -Wall hello.c -o hello >>>> /usr/bin/ld:built in linker script:2: syntax error >>>> -- >>>> ce la vie >>> >>> Yup. Your binutils is hosed :(. >>> -Garrett >> thanks for your help. >> i tried to give buildworld a try a moment ago before anything, but >> also got the above ld error. > > I'd just reinstall the developer package from sysinstall to be honest. > That should do the trick. Then we wash, rinse, and repeat all the > steps to get a working ports install of stuff. > > The question is how did binutils get fubared? > > -Garrett > beats me, if you were actually asking. i usually have some trouble building world on amd64, but always somewhere in gnu tree. this week it didn't fail and seemed to build and install ok, but apparently... thanks again, i reinstalled base off install discs. From w8hdkim at gmail.com Sat Dec 27 13:54:03 2008 From: w8hdkim at gmail.com (Kim Culhan) Date: Sat Dec 27 13:54:10 2008 Subject: 7.1-RC2 audio/x11amp missing symbol at startup Message-ID: <89dbfdc30812271354x5ba2fffftcaf8464cf3463618@mail.gmail.com> On Fri, Dec 26, 2008 at 9:55 PM, Garrett Cooper wrote: >> On Fri, Dec 26, 2008 at 6:51 PM, Kim Culhan wrote: >> It looks like this is related to linking with -pthread which appears to >> be a problem in fbsd 7.1 > > -pthread should *not* be used. According to the gcc manpage it's > HP-alpha specific... Is it actually implemented in the author's > makefiles? > -Garrett One more datapoint: In FreeBSD ports, in multimedia, is an audio player: Audacious In many ways better than x11amp and the port compiles and installs with no problem. Also works with the OSS sound system, an audio hardware driver among other things, which compiles and installs on modern laptop hardware with no problem. Thanks for all your help -kim -- From peterjeremy at optushome.com.au Sat Dec 27 14:59:19 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Sat Dec 27 14:59:26 2008 Subject: general ports problem In-Reply-To: <49569DA9.6050305@gmail.com> References: <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> <20081227065709.GA54990@server.vk2pj.dyndns.org> <9268DAD1-17B4-4FCF-8A5B-8083933F4D60@gmail.com> <332f78510812270510x291812c3p973761815c3984b3@mail.gmail.com> <49565FFF.5070203@gmail.com> <1A5D46CF-986E-45BB-A889-34ABC6F3C684@gmail.com> <49569DA9.6050305@gmail.com> Message-ID: <20081227225915.GA64280@server.vk2pj.dyndns.org> On 2008-Dec-27 22:27:05 +0100, cwt wrote: >i usually have some trouble building world on amd64, but always >somewhere in gnu tree. this week it didn't fail and seemed >to build and install ok, but apparently... I have been running amd64 on 6, 7 and 8 for several years and haven't bumped into any consistent problems building world. Can you provide more details of your hardware and the troubles you have? It is possible you have a hardware issue. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081227/399fe33a/attachment.pgp From 240olofsson at telia.com Sat Dec 27 16:57:32 2008 From: 240olofsson at telia.com (Roger Olofsson) Date: Sat Dec 27 16:57:39 2008 Subject: FreeBSD Port: tikiwiki-2.2 Message-ID: <4956C9A3.3030304@telia.com> Hello, I have made a small fix to the tikiwiki port. The details are at http://tikiwiki.org/tiki-view_forum_thread.php?comments_parentId=31524&topics_offset=2&topics_sort_mode=lastPost_desc&forumId=6 and here: I have fixed the script fixperms.sh making it usable for FreeBSD 7. Below are the changes to the script - use it with 'su -m www -c "sh fixperms.sh"'. Line 21 UNAME=`uname | cut -c 1-7` .. .. 42 43 if "$UNAME" = "FreeBSD" ; then 44 AUSER=www 45 AGROUP=www 46 fi fixperms.sh is in the tikiwiki root folder. /Roger From spawk at acm.poly.edu Sat Dec 27 17:39:22 2008 From: spawk at acm.poly.edu (Boris Kochergin) Date: Sat Dec 27 17:39:28 2008 Subject: security/pecl-hash no longer builds for PHP 5? Message-ID: <4956D26E.3010005@acm.poly.edu> Hi. I tried installing the security/pecl-hash port with PHP 5.2.8 today and got this: # make ===> pecl-hash-1.5 cannot install: doesn't work with PHP version : 5 (Doesn't support PHP 5). *** Error code 1 I've installed it on many machines with PHP 5 in the past--I guess before it was marked as not working with PHP 5--and it has worked fine in the capacity I've used it (hash('sha256', ...)). -Boris From eitanadlerlist at gmail.com Sat Dec 27 18:03:33 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Sat Dec 27 18:03:39 2008 Subject: security/pecl-hash no longer builds for PHP 5? In-Reply-To: <4956D26E.3010005@acm.poly.edu> References: <4956D26E.3010005@acm.poly.edu> Message-ID: <4956DE5E.9020203@gmail.com> Boris Kochergin wrote: > Hi. I tried installing the security/pecl-hash port with PHP 5.2.8 today > and got this: > > # make > ===> pecl-hash-1.5 cannot install: doesn't work with PHP version : 5 > (Doesn't support PHP 5). > *** Error code 1 > > I've installed it on many machines with PHP 5 in the past--I guess > before it was marked as not working with PHP 5--and it has worked fine > in the capacity I've used it (hash('sha256', ...)). > > -Boris > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > from UPDATING 20081211: If you have the pecl hash, json and/or zip extensions you need to replace them with the php5 bundled ones, ie.: portmaster/portupgrade -o archivers/php5-zip archivers/pecl-zip portmaster/portupgrade -o devel/php5-json devel/pecl-json portmaster/portupgrade -o security/php5-hash security/pecl-hash -- Eitan Adler "Security is increased by designing for the way humans actually behave." -Jakob Nielsen From yuri.pankov at gmail.com Sat Dec 27 18:09:09 2008 From: yuri.pankov at gmail.com (Yuri Pankov) Date: Sat Dec 27 18:09:15 2008 Subject: security/pecl-hash no longer builds for PHP 5? In-Reply-To: <4956D26E.3010005@acm.poly.edu> References: <4956D26E.3010005@acm.poly.edu> Message-ID: <20081228014742.GA1348@darklight.homeunix.org> On Sat, Dec 27, 2008 at 08:12:14PM -0500, Boris Kochergin wrote: > Hi. I tried installing the security/pecl-hash port with PHP 5.2.8 today > and got this: > > # make > ===> pecl-hash-1.5 cannot install: doesn't work with PHP version : 5 > (Doesn't support PHP 5). > *** Error code 1 > > I've installed it on many machines with PHP 5 in the past--I guess > before it was marked as not working with PHP 5--and it has worked fine > in the capacity I've used it (hash('sha256', ...)). > > -Boris You should probably use security/php5-hash, check /usr/ports/UPDATING for details. HTH, Yuri From pgollucci at p6m7g8.com Sat Dec 27 21:13:05 2008 From: pgollucci at p6m7g8.com (Philip M. Gollucci) Date: Sat Dec 27 21:13:12 2008 Subject: Unable to build strace-4.5.18 under FreeBSD 6.4 In-Reply-To: <20081226155704.GA45251@ozzmosis.com> References: <20081226155704.GA45251@ozzmosis.com> Message-ID: <49570AC5.3050005@p6m7g8.com> Sorry, this was fixed in the next commit 4.5.18_1 Update your ports tree. andrew clarke wrote: > # uname -a > FreeBSD blizzard.phoenix 6.4-RELEASE FreeBSD 6.4-RELEASE #0: Wed Nov 26 11:43:51 UTC 2008 root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > # make > ===> Vulnerability check disabled, database not found > ===> Extracting for strace-4.5.18 > => MD5 Checksum OK for strace-4.5.18.tar.bz2. > => SHA256 Checksum OK for strace-4.5.18.tar.bz2. > ===> strace-4.5.18 depends on file: /usr/local/bin/perl5.8.8 - found > ===> Patching for strace-4.5.18 > ===> strace-4.5.18 depends on file: /usr/local/bin/perl5.8.8 - found > ===> Applying FreeBSD patches for strace-4.5.18 > /usr/bin/sed -i.bak 's,/usr/bin/perl,/usr/local/bin/perl,' /spare/ports/devel/strace/work/strace-4.5.18/strace-graph > ===> strace-4.5.18 depends on file: /usr/local/bin/perl5.8.8 - found > ===> Configuring for strace-4.5.18 > > ... > > ===> Building for strace-4.5.18 > make all-am > cc -DHAVE_CONFIG_H -I. -Ifreebsd/i386 -I./freebsd/i386 -Ifreebsd -I./freebsd -Wall -O2 -fno-strict-aliasing -pipe -MT strace.o -MD -MP -MF .deps/strace.Tpo -c -o strace.o strace.c > mv -f .deps/strace.Tpo .deps/strace.Po > cc -DHAVE_CONFIG_H -I. -Ifreebsd/i386 -I./freebsd/i386 -Ifreebsd -I./freebsd -Wall -O2 -fno-strict-aliasing -pipe -MT syscall.o -MD -MP -MF .deps/syscall.Tpo -c -o syscall.o syscall.c > syscall.c: In function `internal_syscall': > syscall.c:719: error: `sys_waitpid' undeclared (first use in this function) > syscall.c:719: error: (Each undeclared identifier is reported only once > syscall.c:719: error: for each function it appears in.) > *** Error code 1 > > Stop in /spare/ports/devel/strace/work/strace-4.5.18. > *** Error code 1 > > Regards > Andrew > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" -- ------------------------------------------------------------------------ 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollucci@p6m7g8.com) c: 703.336.9354 Consultant - P6M7G8 Inc. http://p6m7g8.net Director IT - RideCharge, Inc. http://ridecharge.com Contractor - PositiveEnergyUSA http://positiveenergyusa.com ASF Member - Apache Software Foundation http://apache.org FreeBSD Committer - FreeBSD Foundation http://freebsd.org Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. From yanefbsd at gmail.com Sat Dec 27 21:46:26 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sat Dec 27 21:46:33 2008 Subject: general ports problem In-Reply-To: <20081227225915.GA64280@server.vk2pj.dyndns.org> References: <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> <20081227065709.GA54990@server.vk2pj.dyndns.org> <9268DAD1-17B4-4FCF-8A5B-8083933F4D60@gmail.com> <332f78510812270510x291812c3p973761815c3984b3@mail.gmail.com> <49565FFF.5070203@gmail.com> <1A5D46CF-986E-45BB-A889-34ABC6F3C684@gmail.com> <49569DA9.6050305@gmail.com> <20081227225915.GA64280@server.vk2pj.dyndns.org> Message-ID: <653B5364-6D9B-4BCB-8802-78C340339E0E@gmail.com> On Dec 27, 2008, at 14:59, Peter Jeremy wrote: > On 2008-Dec-27 22:27:05 +0100, cwt wrote: >> i usually have some trouble building world on amd64, but always >> somewhere in gnu tree. this week it didn't fail and seemed >> to build and install ok, but apparently... > > I have been running amd64 on 6, 7 and 8 for several years and haven't > bumped into any consistent problems building world. Can you provide > more details of your hardware and the troubles you have? It is > possible > you have a hardware issue. > > -- > Peter Could just be bad media. -Garrett From fenner at FreeBSD.org Sun Dec 28 02:00:11 2008 From: fenner at FreeBSD.org (Bill Fenner) Date: Sun Dec 28 02:00:18 2008 Subject: Possibly unbuildable ports reminder Message-ID: <200812281000.mBSA07BC026707@freefall.freebsd.org> Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/ports@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill "annoying port email" Fenner From eitanadlerlist at gmail.com Sun Dec 28 09:06:05 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Sun Dec 28 09:06:23 2008 Subject: thunderbird port - a few issues Message-ID: <4957B1E5.3030305@gmail.com> WANT_GNOME= yes should that be WANT_GNOME or WITH_GNOME? We should add --disable-tests to MOZ_OPTIONS unless WITH_DEBUG is enabled. Lastly: $portlint WARN: Makefile: [45]: use of != in assignments is almost never a good thing to do. Try to avoid using them. See http://lists.freebsd.org/pipermail/freebsd-ports/2008-July/049777.html for some helpful hints on what to do instead. could GECKO_PTHREAD_LIBS!=${CC} -dumpspecs | ${GREP} pthread | ${SED} -e 's|^.*%{\!pg: %{pthread:|| ; s|}.*$$||' || ${TRUE} be rewritten ? From marshc187 at gmail.com Sun Dec 28 11:06:28 2008 From: marshc187 at gmail.com (cwt) Date: Sun Dec 28 11:06:35 2008 Subject: general ports problem In-Reply-To: <653B5364-6D9B-4BCB-8802-78C340339E0E@gmail.com> References: <332f78510812261433v30ebfa82n13ec572c07e53b67@mail.gmail.com> <15A1EF0E-AFBF-403C-A351-8AFAA3EABA00@gmail.com> <332f78510812261738i549daeb3t6f8bd65c1387e119@mail.gmail.com> <20081227065709.GA54990@server.vk2pj.dyndns.org> <9268DAD1-17B4-4FCF-8A5B-8083933F4D60@gmail.com> <332f78510812270510x291812c3p973761815c3984b3@mail.gmail.com> <49565FFF.5070203@gmail.com> <1A5D46CF-986E-45BB-A889-34ABC6F3C684@gmail.com> <49569DA9.6050305@gmail.com> <20081227225915.GA64280@server.vk2pj.dyndns.org> <653B5364-6D9B-4BCB-8802-78C340339E0E@gmail.com> Message-ID: <4957CE1F.1000900@gmail.com> Garrett Cooper wrote: > On Dec 27, 2008, at 14:59, Peter Jeremy > wrote: > >> On 2008-Dec-27 22:27:05 +0100, cwt wrote: >>> i usually have some trouble building world on amd64, but always >>> somewhere in gnu tree. this week it didn't fail and seemed >>> to build and install ok, but apparently... >> >> I have been running amd64 on 6, 7 and 8 for several years and haven't >> bumped into any consistent problems building world. Can you provide >> more details of your hardware and the troubles you have? It is possible >> you have a hardware issue. >> >> -- >> Peter > > Could just be bad media. > -Garrett > to kinda recap and close on this issue, i have been using fbsd7 for a few months now, simply trying to learn something off and on, and use it for general net stuff, so as long as i don't have too many issues, i'm happy for now, so i haven't been looking into too much detail on any issue. i did suspect some hardware issue, and a while back searched on info about memory checkers, but did not fully get what i was looking for or doing. apart from that i used to have error messages at boot time from the dvd-drives when they get probed or whatever happens there, but they have finally disappeared with this 7.1rc2 i installed yesterday. (they work fine in windows xp on a separate disk). to further suspect a hardware issue, i have had little trouble , if any, building world amd64 on a macbook pro, both in vmware and boot camp. I also never had any issue with i386 on this pc, which i managed to build on more than a few occasions. as too bad media, i can't exclude it, but have tried different discs, plus fully csup'ed sources, so i figure that must amount to something. for now i was doing to stick to binary updates to avoid this problem, but was thinking off seeing how world builds without installing this week, and i'll take it from there. thanks again for all the help, at least i know what to avoid for now. thanks From Helko.Glathe at freenet.de Sun Dec 28 14:21:01 2008 From: Helko.Glathe at freenet.de (Helko Glathe) Date: Sun Dec 28 14:21:09 2008 Subject: Installation of audio/aacplusenc fails Message-ID: <200812282316.50711.Helko.Glathe@freenet.de> Hi Installation of port audio/aacplusenc fails. The file http://teknoraver.net/software/mp4tools/aacplusenc-0.17.tar.bz2 is unfetchable. It seems to be that the server is down? -- Yours sincerely Helko Glathe From venture37 at gmail.com Sun Dec 28 18:10:12 2008 From: venture37 at gmail.com (Sevan / Venture37) Date: Sun Dec 28 18:10:23 2008 Subject: minimal FreeSBIE bombs out Message-ID: <495829E5.5010109@gmail.com> Hi Guys Trying to build a FreeSBIE with MINIMAL=YES defined causes the buildworld process to bomb out, below is the output from the log file, any ideas?? ------------------------------------------------------------- >>> stage 4.2: building libraries -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac _SHLIBDIRPREFIX=/usr/obj/usr/src/tmp VERSION="FreeBSD 7.1-RC2 amd64 701000" INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin NO_CTF=1 make -f Makefile.inc1 DESTDIR=/usr/obj/usr/src/tmp -DNO_FSCHG -DWITHOUT_HTML -DWITHOUT_INFO -DNO_LINT -DWITHOUT_MAN -DWITHOUT_NLS -DWITHOUT_PROFILE libraries cd /usr/src; make -f Makefile.inc1 _prereq_libs; make -f Makefile.inc1 _startup_libs; make -f Makefile.inc1 _prebuild_libs; make -f Makefile.inc1 _generic_libs; ===> gnu/lib/libgcc (obj,depend,all,install) make -f /usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile MFILE=/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile GCCDIR=/usr/src/gnu/lib/libgcc/../../../contrib/gcc tm.h TARGET_CPU_DEFAULT="" HEADERS="options.h i386/biarch64.h i386/i386.h i386/unix.h i386/att.h dbxelf.h elfos.h freebsd-native.h freebsd-spec.h freebsd.h i386/x86-64.h i386/freebsd.h i386/freebsd64.h freebsd64-fix.h defaults.h" DEFINES="" /bin/sh /usr/src/gnu/lib/libgcc/../../../contrib/gcc/mkconfig.sh tm.h echo '#define EXTRA_MODES_FILE "i386/i386-modes.def"' >> tm.h make -f /usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile MFILE=/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile GCCDIR=/usr/src/gnu/lib/libgcc/../../../contrib/gcc tconfig.h TARGET_CPU_DEFAULT="" HEADERS="auto-host.h ansidecl.h" DEFINES="USED_FOR_TARGET" /bin/sh /usr/src/gnu/lib/libgcc/../../../contrib/gcc/mkconfig.sh tconfig.h make -f /usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile MFILE=/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile GCCDIR=/usr/src/gnu/lib/libgcc/../../../contrib/gcc options.h awk -f /usr/src/gnu/lib/libgcc/../../../contrib/gcc/opt-gather.awk /usr/src/gnu/lib/libgcc/../../../contrib/gcc/c.opt /usr/src/gnu/lib/libgcc/../../../contrib/gcc/common.opt /usr/src/gnu/lib/libgcc/../../../contrib/gcc/config/i386/i386.opt > optionlist awk -f /usr/src/gnu/lib/libgcc/../../../contrib/gcc/opt-functions.awk -f /usr/src/gnu/lib/libgcc/../../../contrib/gcc/opth-gen.awk < optionlist > options.h make -f /usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile MFILE=/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile GCCDIR=/usr/src/gnu/lib/libgcc/../../../contrib/gcc unwind.h ln -sf /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-generic.h unwind.h make -f /usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile MFILE=/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile GCCDIR=/usr/src/gnu/lib/libgcc/../../../contrib/gcc gthr-default.h ln -sf /usr/src/gnu/lib/libgcc/../../../contrib/gcc/gthr-posix.h gthr-default.h cc -c -O2 -fno-strict-aliasing -pipe -DIN_GCC -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -DHAVE_GTHR_DEFAULT -I/usr/src/gnu/lib/libgcc/../../../contrib/gcclibs/include -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -I/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools -fvisibility=hidden -DHIDE_EXPORTS -fPIC -fexceptions -D__GLIBC__=3 -DElfW=__ElfN -o unwind-dw2.o /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c In file included from /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:32: /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:47:20: error: stddef.h: No such file or directory /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:48:19: error: float.h: No such file or directory /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:87:20: error: stdarg.h: No such file or directory /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:90:19: error: stdio.h: No such file or directory /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:96:19: error: errno.h: No such file or directory /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:103:20: error: string.h: No such file or directory /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:104:20: error: stdlib.h: No such file or directory /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:105:20: error: unistd.h: No such file or directory /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:108:20: error: limits.h: No such file or directory /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:111:18: error: time.h: No such file or directory In file included from /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:40: /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-pe.h: In function 'size_of_encoded_value': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-pe.h:90: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-pe.h: In function 'base_of_encoded_value': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-pe.h:122: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-pe.h: In function 'read_encoded_value_with_base': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-pe.h:259: warning: incompatible implicit declaration of built-in function 'abort' In file included from /usr/src/gnu/lib/libgcc/../../../contrib/gcc/gthr.h:114, from /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:42: ./gthr-default.h:43:21: error: pthread.h: No such file or directory In file included from /usr/src/gnu/lib/libgcc/../../../contrib/gcc/gthr.h:114, from /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:42: ./gthr-default.h: At top level: ./gthr-default.h:92: error: 'pthread_once' undeclared here (not in a function) ./gthr-default.h:93: error: 'pthread_getspecific' undeclared here (not in a function) ./gthr-default.h:94: error: 'pthread_setspecific' undeclared here (not in a function) ./gthr-default.h:95: error: 'pthread_create' undeclared here (not in a function) ./gthr-default.h:96: error: 'pthread_cancel' undeclared here (not in a function) ./gthr-default.h:97: error: 'pthread_mutex_lock' undeclared here (not in a function) ./gthr-default.h:98: error: 'pthread_mutex_trylock' undeclared here (not in a function) ./gthr-default.h:99: error: 'pthread_mutex_unlock' undeclared here (not in a function) ./gthr-default.h:100: error: 'pthread_mutex_init' undeclared here (not in a function) ./gthr-default.h:103: error: 'pthread_key_create' undeclared here (not in a function) ./gthr-default.h:104: error: 'pthread_key_delete' undeclared here (not in a function) ./gthr-default.h:105: error: 'pthread_mutexattr_init' undeclared here (not in a function) ./gthr-default.h:106: error: 'pthread_mutexattr_settype' undeclared here (not in a function) ./gthr-default.h:107: error: 'pthread_mutexattr_destroy' undeclared here (not in a function) ./gthr-default.h: In function '__gthread_active_p': ./gthr-default.h:173: error: 'PTHREAD_MUTEX_INITIALIZER' undeclared (first use in this function) ./gthr-default.h:173: error: (Each undeclared identifier is reported only once ./gthr-default.h:173: error: for each function it appears in.) ./gthr-default.h:174: error: 'PTHREAD_ONCE_INIT' undeclared (first use in this function) ./gthr-default.h:188: error: called object '__gthrw_pthread_mutex_lock' is not a function ./gthr-default.h:189: error: called object '__gthrw_pthread_once' is not a function ./gthr-default.h:190: error: called object '__gthrw_pthread_mutex_unlock' is not a function ./gthr-default.h: In function '__gthread_once': ./gthr-default.h:578: error: called object '__gthrw_pthread_once' is not a function ./gthr-default.h: In function '__gthread_key_create': ./gthr-default.h:586: error: called object '__gthrw_pthread_key_create' is not a function ./gthr-default.h: In function '__gthread_key_delete': ./gthr-default.h:592: error: called object '__gthrw_pthread_key_delete' is not a function ./gthr-default.h: In function '__gthread_getspecific': ./gthr-default.h:598: error: called object '__gthrw_pthread_getspecific' is not a function ./gthr-default.h: In function '__gthread_setspecific': ./gthr-default.h:604: error: called object '__gthrw_pthread_setspecific' is not a function ./gthr-default.h: In function '__gthread_mutex_lock': ./gthr-default.h:611: error: called object '__gthrw_pthread_mutex_lock' is not a function ./gthr-default.h: In function '__gthread_mutex_trylock': ./gthr-default.h:620: error: called object '__gthrw_pthread_mutex_trylock' is not a function ./gthr-default.h: In function '__gthread_mutex_unlock': ./gthr-default.h:629: error: called object '__gthrw_pthread_mutex_unlock' is not a function ./gthr-default.h: In function '__gthread_recursive_mutex_init_function': ./gthr-default.h:643: error: called object '__gthrw_pthread_mutexattr_init' is not a function ./gthr-default.h:645: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared (first use in this function) ./gthr-default.h:645: error: called object '__gthrw_pthread_mutexattr_settype' is not a function ./gthr-default.h:647: error: called object '__gthrw_pthread_mutex_init' is not a function ./gthr-default.h:649: error: called object '__gthrw_pthread_mutexattr_destroy' is not a function /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function '_Unwind_GetGR': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:168: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function '_Unwind_SetGR': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:208: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function '_Unwind_SetGRValue': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:257: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function 'extract_cie_info': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:350: warning: incompatible implicit declaration of built-in function 'strlen' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function 'execute_stack_op': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:611: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:829: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:836: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function 'execute_cfa_program': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1082: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function 'uw_frame_state_for': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1099: warning: incompatible implicit declaration of built-in function 'memset' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function '__frame_state_for': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1184: warning: incompatible implicit declaration of built-in function 'memset' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function '_Unwind_SetSpColumn': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1234: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function 'uw_update_context_1': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1290: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function 'uw_init_context_1': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1408: warning: incompatible implicit declaration of built-in function 'memset' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1413: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1417: error: 'PTHREAD_ONCE_INIT' undeclared (first use in this function) /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function 'uw_install_context_1': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1472: warning: incompatible implicit declaration of built-in function 'abort' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1480: warning: incompatible implicit declaration of built-in function 'memcpy' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1486: warning: incompatible implicit declaration of built-in function 'memcpy' /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1490: warning: incompatible implicit declaration of built-in function 'memcpy' In file included from /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1518: /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind.inc: In function '_Unwind_RaiseException_Phase2': /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind.inc:75: warning: incompatible implicit declaration of built-in function 'abort' From scott at friedemann.us Sun Dec 28 18:11:52 2008 From: scott at friedemann.us (Scott D Friedemann) Date: Sun Dec 28 18:11:59 2008 Subject: timeseal -- bad system call Message-ID: <49582B49.6000003@friedemann.us> Installed the 2008-09-23 02:47:00 package to a 7.0 system and ran a ktrace giving 2079 ktrace RET ktrace 0 2079 ktrace CALL execve(0xbfbfed94,0xbfbfec90,0xbfbfec98) 2079 ktrace NAMI "/usr/local/bin/timeseal" 2079 timeseal RET execve 0 2079 timeseal CALL compat.sigaction 2079 timeseal RET compat.sigaction -1 errno 78 Function not implemented 2079 timeseal PSIG SIGSYS SIG_DFL 2079 timeseal NAMI "timeseal.core" I'm not sure how to enable compat.sigaction and would appreciate any assistance that can be given. I have a.out compiled into the kernel. Best regards, Scott D Friedemann From kitchetech at gmail.com Sun Dec 28 18:18:07 2008 From: kitchetech at gmail.com (matt donovan) Date: Sun Dec 28 18:18:14 2008 Subject: minimal FreeSBIE bombs out In-Reply-To: <495829E5.5010109@gmail.com> References: <495829E5.5010109@gmail.com> Message-ID: <28283d910812281818p523d09f5wd2062fed32154fc4@mail.gmail.com> On Sun, Dec 28, 2008 at 8:37 PM, Sevan / Venture37 wrote: > Hi Guys > Trying to build a FreeSBIE with MINIMAL=YES defined causes the buildworld > process to bomb out, below is the output from the log file, any ideas?? > > > > ------------------------------------------------------------- > > >>> stage 4.2: building libraries > > -------------------------------------------------------------- > > cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64 > CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin > GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font > GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac > _SHLIBDIRPREFIX=/usr/obj/usr/src/tmp VERSION="FreeBSD 7.1-RC2 amd64 701000" > INSTALL="sh /usr/src/tools/install.sh" > PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > NO_CTF=1 make -f Makefile.inc1 DESTDIR=/usr/obj/usr/src/tmp -DNO_FSCHG > -DWITHOUT_HTML -DWITHOUT_INFO -DNO_LINT -DWITHOUT_MAN -DWITHOUT_NLS > -DWITHOUT_PROFILE libraries > > cd /usr/src; make -f Makefile.inc1 _prereq_libs; make -f Makefile.inc1 > _startup_libs; make -f Makefile.inc1 _prebuild_libs; make -f Makefile.inc1 > _generic_libs; > > ===> gnu/lib/libgcc (obj,depend,all,install) > > make -f /usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile > MFILE=/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile > GCCDIR=/usr/src/gnu/lib/libgcc/../../../contrib/gcc tm.h > > TARGET_CPU_DEFAULT="" HEADERS="options.h i386/biarch64.h i386/i386.h > i386/unix.h i386/att.h dbxelf.h elfos.h freebsd-native.h freebsd-spec.h > freebsd.h i386/x86-64.h i386/freebsd.h i386/freebsd64.h freebsd64-fix.h > defaults.h" DEFINES="" /bin/sh > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/mkconfig.sh tm.h > > echo '#define EXTRA_MODES_FILE "i386/i386-modes.def"' >> tm.h > > make -f /usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile > MFILE=/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile > GCCDIR=/usr/src/gnu/lib/libgcc/../../../contrib/gcc tconfig.h > > TARGET_CPU_DEFAULT="" HEADERS="auto-host.h ansidecl.h" > DEFINES="USED_FOR_TARGET" /bin/sh > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/mkconfig.sh tconfig.h > > make -f /usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile > MFILE=/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile > GCCDIR=/usr/src/gnu/lib/libgcc/../../../contrib/gcc options.h > > awk -f /usr/src/gnu/lib/libgcc/../../../contrib/gcc/opt-gather.awk > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/c.opt > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/common.opt > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/config/i386/i386.opt > > optionlist > > awk -f /usr/src/gnu/lib/libgcc/../../../contrib/gcc/opt-functions.awk -f > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/opth-gen.awk < optionlist > > options.h > > make -f /usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile > MFILE=/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile > GCCDIR=/usr/src/gnu/lib/libgcc/../../../contrib/gcc unwind.h > > ln -sf /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-generic.h > unwind.h > > make -f /usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile > MFILE=/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools/Makefile > GCCDIR=/usr/src/gnu/lib/libgcc/../../../contrib/gcc gthr-default.h > > ln -sf /usr/src/gnu/lib/libgcc/../../../contrib/gcc/gthr-posix.h > gthr-default.h > > cc -c -O2 -fno-strict-aliasing -pipe -DIN_GCC -DIN_LIBGCC2 > -D__GCC_FLOAT_NOT_NEEDED -DHAVE_GTHR_DEFAULT > -I/usr/src/gnu/lib/libgcc/../../../contrib/gcclibs/include > -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config > -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. > -I/usr/src/gnu/lib/libgcc/../../usr.bin/cc/cc_tools -fvisibility=hidden > -DHIDE_EXPORTS -fPIC -fexceptions -D__GLIBC__=3 -DElfW=__ElfN -o > unwind-dw2.o /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c > > In file included from > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:32: > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:47:20: error: > stddef.h: No such file or directory > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:48:19: error: > float.h: No such file or directory > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:87:20: error: > stdarg.h: No such file or directory > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:90:19: error: > stdio.h: No such file or directory > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:96:19: error: > errno.h: No such file or directory > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:103:20: error: > string.h: No such file or directory > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:104:20: error: > stdlib.h: No such file or directory > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:105:20: error: > unistd.h: No such file or directory > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:108:20: error: > limits.h: No such file or directory > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:111:18: error: > time.h: No such file or directory > > In file included from > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:40: > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-pe.h: In function > 'size_of_encoded_value': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-pe.h:90: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-pe.h: In function > 'base_of_encoded_value': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-pe.h:122: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-pe.h: In function > 'read_encoded_value_with_base': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-pe.h:259: warning: > incompatible implicit declaration of built-in function 'abort' > > In file included from > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/gthr.h:114, > > from > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:42: > > ./gthr-default.h:43:21: error: pthread.h: No such file or directory > > In file included from > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/gthr.h:114, > > from > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:42: > > ./gthr-default.h: At top level: > > ./gthr-default.h:92: error: 'pthread_once' undeclared here (not in a > function) > > ./gthr-default.h:93: error: 'pthread_getspecific' undeclared here (not in a > function) > > ./gthr-default.h:94: error: 'pthread_setspecific' undeclared here (not in a > function) > > ./gthr-default.h:95: error: 'pthread_create' undeclared here (not in a > function) > > ./gthr-default.h:96: error: 'pthread_cancel' undeclared here (not in a > function) > > ./gthr-default.h:97: error: 'pthread_mutex_lock' undeclared here (not in a > function) > > ./gthr-default.h:98: error: 'pthread_mutex_trylock' undeclared here (not in > a function) > > ./gthr-default.h:99: error: 'pthread_mutex_unlock' undeclared here (not in > a function) > > ./gthr-default.h:100: error: 'pthread_mutex_init' undeclared here (not in a > function) > > ./gthr-default.h:103: error: 'pthread_key_create' undeclared here (not in a > function) > > ./gthr-default.h:104: error: 'pthread_key_delete' undeclared here (not in a > function) > > ./gthr-default.h:105: error: 'pthread_mutexattr_init' undeclared here (not > in a function) > > ./gthr-default.h:106: error: 'pthread_mutexattr_settype' undeclared here > (not in a function) > > ./gthr-default.h:107: error: 'pthread_mutexattr_destroy' undeclared here > (not in a function) > > ./gthr-default.h: In function '__gthread_active_p': > > ./gthr-default.h:173: error: 'PTHREAD_MUTEX_INITIALIZER' undeclared (first > use in this function) > > ./gthr-default.h:173: error: (Each undeclared identifier is reported only > once > > ./gthr-default.h:173: error: for each function it appears in.) > > ./gthr-default.h:174: error: 'PTHREAD_ONCE_INIT' undeclared (first use in > this function) > > ./gthr-default.h:188: error: called object '__gthrw_pthread_mutex_lock' is > not a function > > ./gthr-default.h:189: error: called object '__gthrw_pthread_once' is not a > function > > ./gthr-default.h:190: error: called object '__gthrw_pthread_mutex_unlock' > is not a function > > ./gthr-default.h: In function '__gthread_once': > > ./gthr-default.h:578: error: called object '__gthrw_pthread_once' is not a > function > > ./gthr-default.h: In function '__gthread_key_create': > > ./gthr-default.h:586: error: called object '__gthrw_pthread_key_create' is > not a function > > ./gthr-default.h: In function '__gthread_key_delete': > > ./gthr-default.h:592: error: called object '__gthrw_pthread_key_delete' is > not a function > > ./gthr-default.h: In function '__gthread_getspecific': > > ./gthr-default.h:598: error: called object '__gthrw_pthread_getspecific' is > not a function > > ./gthr-default.h: In function '__gthread_setspecific': > > ./gthr-default.h:604: error: called object '__gthrw_pthread_setspecific' is > not a function > > ./gthr-default.h: In function '__gthread_mutex_lock': > > ./gthr-default.h:611: error: called object '__gthrw_pthread_mutex_lock' is > not a function > > ./gthr-default.h: In function '__gthread_mutex_trylock': > > ./gthr-default.h:620: error: called object '__gthrw_pthread_mutex_trylock' > is not a function > > ./gthr-default.h: In function '__gthread_mutex_unlock': > > ./gthr-default.h:629: error: called object '__gthrw_pthread_mutex_unlock' > is not a function > > ./gthr-default.h: In function '__gthread_recursive_mutex_init_function': > > ./gthr-default.h:643: error: called object '__gthrw_pthread_mutexattr_init' > is not a function > > ./gthr-default.h:645: error: 'PTHREAD_MUTEX_RECURSIVE' undeclared (first > use in this function) > > ./gthr-default.h:645: error: called object > '__gthrw_pthread_mutexattr_settype' is not a function > > ./gthr-default.h:647: error: called object '__gthrw_pthread_mutex_init' is > not a function > > ./gthr-default.h:649: error: called object > '__gthrw_pthread_mutexattr_destroy' is not a function > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function > '_Unwind_GetGR': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:168: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function > '_Unwind_SetGR': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:208: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function > '_Unwind_SetGRValue': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:257: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function > 'extract_cie_info': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:350: warning: > incompatible implicit declaration of built-in function 'strlen' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function > 'execute_stack_op': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:611: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:829: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:836: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function > 'execute_cfa_program': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1082: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function > 'uw_frame_state_for': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1099: warning: > incompatible implicit declaration of built-in function 'memset' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function > '__frame_state_for': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1184: warning: > incompatible implicit declaration of built-in function 'memset' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function > '_Unwind_SetSpColumn': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1234: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function > 'uw_update_context_1': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1290: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function > 'uw_init_context_1': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1408: warning: > incompatible implicit declaration of built-in function 'memset' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1413: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1417: error: > 'PTHREAD_ONCE_INIT' undeclared (first use in this function) > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c: In function > 'uw_install_context_1': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1472: warning: > incompatible implicit declaration of built-in function 'abort' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1480: warning: > incompatible implicit declaration of built-in function 'memcpy' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1486: warning: > incompatible implicit declaration of built-in function 'memcpy' > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1490: warning: > incompatible implicit declaration of built-in function 'memcpy' > > In file included from > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind-dw2.c:1518: > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind.inc: In function > '_Unwind_RaiseException_Phase2': > > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/unwind.inc:75: warning: > incompatible implicit declaration of built-in function 'abort' > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" does your normal buildworld bomb out? I tend to do a make buildworld outside of freesbie then just put NO_BUILDWORLD in my freesbie.conf. From linimon at FreeBSD.org Sun Dec 28 19:05:47 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Dec 28 19:05:53 2008 Subject: FreeBSD unmaintained ports which are currently marked broken Message-ID: <20081229030545.A75341CCD6@mail.droso.net> As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 5.x/6.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/tse3 broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=tse3 portname: audio/umodplayer broken because: Does not compile with audio/libaiff build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20081226112844/umodplayer-0.b5.1.log (Fri Dec 26 15:58:18 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=umodplayer portname: audio/xmms-imms broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=xmms-imms portname: chinese/iiimf-le-xcin broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-xcin portname: chinese/stardict2-dict-zh_TW broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=stardict2-dict-zh_TW portname: deskutils/mical broken because: Miscellaneous run-time failures due out of sync with the current versions of dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=mical portname: devel/ace+tao broken because: Does not compile on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ace%2Btao portname: devel/cogito broken because: this port does not work with new asciidoc and is deprecated by upstream build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=cogito portname: devel/fampp broken because: FAM system mismatch: gamin is installed, while desired FAM system is fam build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=fampp portname: devel/p5-ORBit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-ORBit portname: devel/py-coro broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=py-coro portname: devel/ruby-p4 broken because: does not compile build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20081226112844/ruby18-p4-1.4251.log (Fri Nov 7 17:08:50 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ruby-p4 portname: emulators/xgs broken because: Does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=xgs portname: games/euchre broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=euchre portname: graphics/gephex broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20081226112844/gephex-0.4.4.log (Fri Dec 12 08:10:54 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=gephex portname: graphics/libvisual-plugins broken because: Broken objformat handling build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=libvisual-plugins portname: graphics/ray++ broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=ray%2B%2B portname: japanese/okphone broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=okphone portname: japanese/oleo broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=oleo portname: japanese/plain2 broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=plain2 portname: japanese/tkstep80 broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=tkstep80 portname: java/cacao broken because: does not configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=cacao portname: java/jboss5 broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.8.20080904173358/jboss-5.0.0.b1_2,1.log (Sat Sep 6 11:57:51 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=jboss5 portname: java/openjit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=openjit portname: java/tya broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=tya portname: lang/pfe-devel broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pfe-devel portname: lang/pm3-base broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-base portname: lang/pnet-base broken because: Bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pnet-base portname: lang/q broken because: bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=q portname: lang/quack broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=quack portname: lang/scriba broken because: Does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=scriba portname: lang/wamcc broken because: does not compile on 7.X build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=wamcc portname: math/rascal broken because: Does not compile with GCC 4.2 build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081228115029/rascal-0.3.2_4.log (Sat Nov 29 18:14:31 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=rascal portname: misc/pybliographer broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=pybliographer portname: multimedia/dvbcut broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.2007101601/dvbcut-0.5.4_2.log (Fri Sep 5 13:06:04 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=dvbcut portname: multimedia/jahshaka broken because: does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=jahshaka portname: multimedia/mplayerxp broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mplayerxp portname: multimedia/mythtv broken because: Incorrect handling of user addition build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mythtv portname: multimedia/smpeg-xmms broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=smpeg-xmms portname: multimedia/xmps-win32-plugin broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=xmps-win32-plugin portname: net-im/ocaml-jabbr broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081222123807/ocaml-jabbr-0.0.20021124_1.log (Fri Dec 19 01:13:53 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-im&portname=ocaml-jabbr portname: net-mgmt/NeTraMet broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=NeTraMet portname: net/cap broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=cap portname: net/gnometelnet broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=gnometelnet portname: net/libunpipc broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=libunpipc portname: net/py-mantissa broken because: Leaves files behind after deinstallation build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=py-mantissa portname: net/versuch broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=versuch portname: palm/pdbc broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=pdbc portname: ports-mgmt/barry broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ports-mgmt&portname=barry portname: print/ifhp broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=ifhp portname: print/perlftlib broken because: Does not build if devel/p5-ExUtils-CBuilder is installed build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=perlftlib portname: science/gerris broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=gerris portname: science/oof broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=oof portname: science/pnetcdf broken because: Does not configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=pnetcdf portname: security/newpki-lib broken because: does not compile with OpenSSL 0.9.8b build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=newpki-lib portname: security/newpki-server broken because: does not compile with OpenSSL 0.9.8b build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=newpki-server portname: security/xmlsec broken because: Does not compile on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=xmlsec portname: shells/zoidberg broken because: does not package build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081222123807/zoidberg-0.96.log (Sat Nov 29 18:16:39 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=zoidberg portname: textproc/opensched broken because: Does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=opensched portname: www/bk_edit broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=bk_edit portname: www/gforge broken because: bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=gforge portname: www/ocaml-wdialog broken because: does not build with new ocaml build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=ocaml-wdialog portname: www/py-nevow broken because: doesn't build: in nevow/static.py", line 18, twisted.web import error build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=py-nevow portname: www/wb0 broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=wb0 portname: www/winhelpcgi broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=winhelpcgi portname: x11-themes/gtk-industrial-theme broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-themes&portname=gtk-industrial-theme portname: x11-toolkits/flu broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=flu portname: x11-toolkits/p5-Gnome broken because: fails to install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-Gnome portname: x11-toolkits/wxmozilla broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=wxmozilla portname: x11-wm/fluxspace broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=fluxspace portname: x11/bbuname broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=bbuname From linimon at FreeBSD.org Sun Dec 28 19:06:15 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Dec 28 19:06:25 2008 Subject: FreeBSD ports which are currently marked broken Message-ID: <20081229030612.BB9991CC56@mail.droso.net> As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 5.x/6.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/esperanza broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=esperanza portname: audio/gstreamer-plugins-spc broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gstreamer-plugins-spc portname: audio/p5-Audio-TagLib broken because: does not build with taglib 1.5 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=p5-Audio-TagLib portname: audio/py-sdl_mixer broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-sdl_mixer portname: audio/tse3 broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=tse3 portname: audio/umodplayer broken because: Does not compile with audio/libaiff build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20081226112844/umodplayer-0.b5.1.log (Fri Dec 26 15:58:18 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=umodplayer portname: audio/xmms-imms broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=xmms-imms portname: biology/p5-bioperl-run-devel broken because: this port needs dependency update to p5-bioperl=1.5.2 and Build.PL mechanism build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081222123807/p5-bioperl-run-1.5.1_1.log (Wed Dec 17 20:15:20 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=biology&portname=p5-bioperl-run-devel portname: cad/opencascade broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=opencascade portname: chinese/iiimf-le-xcin broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-xcin portname: chinese/stardict2-dict-zh_TW broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=stardict2-dict-zh_TW portname: comms/hcfmdm broken because: Does not compile at 7.x build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=hcfmdm portname: converters/mimelib broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=converters&portname=mimelib portname: databases/erserver broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=erserver portname: databases/mysqlbigram broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=mysqlbigram portname: databases/rubygem-rrdtool broken because: does not compile with rrdtool 1.3 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=rubygem-rrdtool portname: deskutils/mical broken because: Miscellaneous run-time failures due out of sync with the current versions of dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=mical portname: deskutils/remember.el broken because: Conflicting dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=remember.el portname: devel/ace+tao broken because: Does not compile on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ace%2Btao portname: devel/cocktail broken because: Segfault during build on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=cocktail portname: devel/cogito broken because: this port does not work with new asciidoc and is deprecated by upstream build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=cogito portname: devel/fampp broken because: FAM system mismatch: gamin is installed, while desired FAM system is fam build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=fampp portname: devel/gdb53-act broken because: Does not compile with GCC 4.2 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081226112057/gdb-act-5.3_2,1.log (Sat Dec 27 00:05:20 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=gdb53-act portname: devel/hs-hat broken because: Does not build with recent ghc build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hs-hat portname: devel/hs-hpl broken because: Does not build with current ghc build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hs-hpl portname: devel/msp430-gdb broken because: Does not compile with GCC 4.2 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081226112057/msp430-gdb-5.1.1.20030909_1.log (Fri Dec 26 22:50:08 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=msp430-gdb portname: devel/p5-ORBit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-ORBit portname: devel/p5-P4-Client broken because: does not compile build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20081226112844/p5-P4-Client-2.4319.log (Fri Dec 19 10:09:20 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-P4-Client portname: devel/py-coro broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=py-coro portname: devel/root broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=root portname: devel/ruby-p4 broken because: does not compile build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20081226112844/ruby18-p4-1.4251.log (Fri Nov 7 17:08:50 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ruby-p4 portname: devel/ruby-rjudy broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ruby-rjudy portname: devel/xfc broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=xfc portname: editors/setedit broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=setedit portname: editors/zed broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=zed portname: emulators/snes9express broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=snes9express portname: emulators/xgs broken because: Does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulators&portname=xgs portname: games/amy broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=amy portname: games/aqbubble broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=aqbubble portname: games/emacs-chess broken because: Conflicting dependencies build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=emacs-chess portname: games/euchre broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=euchre portname: games/pykawari broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=pykawari portname: games/xrally broken because: Doesn't work (yet?) on 7.x build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=xrally portname: graphics/crystalspace-devel broken because: Incorrect pkg-plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=crystalspace-devel portname: graphics/gephex broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20081226112844/gephex-0.4.4.log (Fri Dec 12 08:10:54 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=gephex portname: graphics/ivtools broken because: Incomplete pkg-plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=ivtools portname: graphics/libvisual-plugins broken because: Broken objformat handling build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=libvisual-plugins portname: graphics/ray++ broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=ray%2B%2B portname: irc/ircg broken because: Does not build with newer st build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20081226112844/iRCG-2.7.log (Fri Nov 7 16:59:32 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=irc&portname=ircg portname: japanese/okphone broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=okphone portname: japanese/oleo broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=oleo portname: japanese/plain2 broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=plain2 portname: japanese/tkstep80 broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=tkstep80 portname: java/cacao broken because: does not configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=cacao portname: java/dbvis broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=dbvis portname: java/jakarta-commons-dbcp broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20081209125646/jakarta-commons-dbcp-1.2.1_2.log (Wed Dec 10 17:39:50 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=jakarta-commons-dbcp portname: java/jboss5 broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.8.20080904173358/jboss-5.0.0.b1_2,1.log (Sat Sep 6 11:57:51 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=jboss5 portname: java/jdk14 broken because: Does not compile with GCC 4.2 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081226112057/jdk-1.4.2p8_13.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=jdk14 portname: java/openjit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=openjit portname: java/tya broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=tya portname: lang/dylan broken because: does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=dylan portname: lang/gcl broken because: Gcl compiled with gcc42 dumps core build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=gcl portname: lang/mozart broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=mozart portname: lang/pfe-devel broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pfe-devel portname: lang/pm3-base broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-base portname: lang/pnet-base broken because: Bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pnet-base portname: lang/q broken because: bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=q portname: lang/qscheme broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=qscheme portname: lang/quack broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=quack portname: lang/scriba broken because: Does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=scriba portname: lang/wamcc broken because: does not compile on 7.X build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=wamcc portname: lang/xsb broken because: Does not compile on FreeBSD 7.x build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20081218140000/XSB-2.6_1.log (Wed Dec 24 22:23:37 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=xsb portname: mail/claws-mail-clamav broken because: Doesn't build with clamav-0.93 or higher build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=claws-mail-clamav portname: mail/silkymail broken because: doesn't fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=silkymail portname: mail/sylpheed2-devel broken because: does not link build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=sylpheed2-devel portname: math/linalg broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=linalg portname: math/rascal broken because: Does not compile with GCC 4.2 build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081228115029/rascal-0.3.2_4.log (Sat Nov 29 18:14:31 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=rascal portname: misc/pybliographer broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=pybliographer portname: multimedia/dirac-reference broken because: bad plist build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081228103651/dirac-reference-0.7.0.log (Thu Dec 25 01:41:30 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=dirac-reference portname: multimedia/dvbcut broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.2007101601/dvbcut-0.5.4_2.log (Fri Sep 5 13:06:04 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=dvbcut portname: multimedia/helixplayer broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=helixplayer portname: multimedia/jahshaka broken because: does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=jahshaka portname: multimedia/mjpegtools-yuvfilters broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mjpegtools-yuvfilters portname: multimedia/mplayerxp broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mplayerxp portname: multimedia/mythtv broken because: Incorrect handling of user addition build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mythtv portname: multimedia/smilutils broken because: Does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.2007101601/smilutils-0.3.2_3.log (Fri Sep 5 12:41:20 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=smilutils portname: multimedia/smpeg-xmms broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=smpeg-xmms portname: multimedia/xmps-win32-plugin broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=xmps-win32-plugin portname: net-im/icqnd broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081228115029/icqnd-0.1.9.6_2.log (Fri Dec 19 01:14:44 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-im&portname=icqnd portname: net-im/ocaml-jabbr broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081222123807/ocaml-jabbr-0.0.20021124_1.log (Fri Dec 19 01:13:53 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-im&portname=ocaml-jabbr portname: net-im/sulci broken because: don't work with ocaml 3.10 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-im&portname=sulci portname: net-mgmt/NeTraMet broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=NeTraMet portname: net-mgmt/nav broken because: does not compile build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081226112057/nav-3.4.4.log (Fri Dec 26 23:05:21 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=nav portname: net-mgmt/nfsen-devel broken because: fails to install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=nfsen-devel portname: net/acx100 broken because: Does not compile on FreeBSD >= 6.x build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=acx100 portname: net/b2bua broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=b2bua portname: net/cap broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=cap portname: net/ggsd broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ggsd portname: net/gnometelnet broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=gnometelnet portname: net/isc-dhcp31-client broken because: Not yet integrated and tested build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=isc-dhcp31-client portname: net/isc-dhcp31-relay broken because: Not yet integrated and tested build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=isc-dhcp31-relay portname: net/isc-dhcp31-server broken because: Not yet integrated and tested build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=isc-dhcp31-server portname: net/libunpipc broken because: checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=libunpipc portname: net/openpbx.org broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=openpbx.org portname: net/py-mantissa broken because: Leaves files behind after deinstallation build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=py-mantissa portname: net/samba4wins broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=samba4wins portname: net/ssltunnel-client broken because: does not compile with OpenSSL 0.9.8b build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ssltunnel-client portname: net/versuch broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=versuch portname: net/vserver broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=vserver portname: net/ztelnet broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ztelnet portname: news/inn-current broken because: Does not install (makedbz segfaults) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=news&portname=inn-current portname: news/openftd broken because: Does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=news&portname=openftd portname: palm/pdbc broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=pdbc portname: palm/romeo broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=romeo portname: ports-mgmt/barry broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ports-mgmt&portname=barry portname: print/ifhp broken because: Size mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=ifhp portname: print/kaspaliste broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=kaspaliste portname: print/perlftlib broken because: Does not build if devel/p5-ExUtils-CBuilder is installed build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=perlftlib portname: science/gerris broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=gerris portname: science/hdf broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=hdf portname: science/oof broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=oof portname: science/pcp broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=pcp portname: science/pnetcdf broken because: Does not configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=pnetcdf portname: security/dazuko broken because: Currently does not support FreeBSD > 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=dazuko portname: security/krb4 broken because: Incorrect pkg-plist on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=krb4 portname: security/newpki-lib broken because: does not compile with OpenSSL 0.9.8b build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=newpki-lib portname: security/newpki-server broken because: does not compile with OpenSSL 0.9.8b build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=newpki-server portname: security/prelude-manager broken because: does not build with current lib build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=prelude-manager portname: security/shibboleth-sp broken because: Does not compile with GCC 4.2 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.20081228103651/shibboleth-sp-1.3f.log (Sun Dec 28 12:54:56 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=shibboleth-sp portname: security/squidclam broken because: Doesn't build with clamav-0.93 or higher build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=squidclam portname: security/xmlsec broken because: Does not compile on FreeBSD >= 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=xmlsec portname: shells/zoidberg broken because: does not package build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081222123807/zoidberg-0.96.log (Sat Nov 29 18:16:39 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=zoidberg portname: sysutils/dtc broken because: bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=dtc portname: sysutils/linux-megacli broken because: Unfetchable build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20081209125646/linux-megacli-1.01.40_1.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=linux-megacli portname: sysutils/perf broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=perf portname: sysutils/upsdaemon broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=upsdaemon portname: sysutils/xwipower broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=xwipower portname: sysutils/xwlans broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=xwlans portname: textproc/dixit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=dixit portname: textproc/opensched broken because: Does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=opensched portname: www/bk_edit broken because: Broken with gcc 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=bk_edit portname: www/c-icap broken because: Doesn't build with clamav-0.93 or higher build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=c-icap portname: www/cacheboy broken because: leaves leftover binary after deinstall build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20081003043826/cacheboy-1.4.1_12.log (Wed Sep 24 10:59:26 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=cacheboy portname: www/cybercalendar broken because: does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=cybercalendar portname: www/geneweb broken because: does not build with new ocaml build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=geneweb portname: www/gforge broken because: bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=gforge portname: www/mod_webapp broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20081225024348/mod_webapp-4.1.24_2.log (Sat Dec 27 09:26:13 UTC 2008) http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20081003043826/mod_webapp-4.1.24_2.log (Fri Oct 3 06:48:31 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=mod_webapp portname: www/ocaml-wdialog broken because: does not build with new ocaml build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=ocaml-wdialog portname: www/ocsigen broken because: unsatisfiable dependency line build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=ocsigen portname: www/pecl-mnogosearch broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=pecl-mnogosearch portname: www/py-nevow broken because: doesn't build: in nevow/static.py", line 18, twisted.web import error build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=py-nevow portname: www/rt32 broken because: Broken due the new mod_perl2 API build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=rt32 portname: www/thttpd-st broken because: does not compile with new st build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20081226125948/thttpd-st-2.25b_3.log (Wed Dec 24 22:49:07 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=thttpd-st portname: www/toofpy broken because: Installs files outside of localbase build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=toofpy portname: www/wb0 broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=wb0 portname: www/winhelpcgi broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=winhelpcgi portname: x11-drivers/xf86-video-i810 broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.8.20080904173358/xf86-video-i810-1.7.4_1.log (Sat Sep 6 12:27:02 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-drivers&portname=xf86-video-i810 portname: x11-fm/velocity broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-fm&portname=velocity portname: x11-themes/camaelon-nesedah broken because: conflicts with its own dependency build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-themes&portname=camaelon-nesedah portname: x11-themes/gtk-industrial-theme broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-themes&portname=gtk-industrial-theme portname: x11-toolkits/flu broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=flu portname: x11-toolkits/fox10 broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=fox10 portname: x11-toolkits/fxscintilla-fox10 broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=fxscintilla-fox10 portname: x11-toolkits/p5-Gnome broken because: fails to install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-Gnome portname: x11-toolkits/wxmozilla broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=wxmozilla portname: x11-wm/fluxspace broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=fluxspace portname: x11/bbuname broken because: Checksum mismatch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=bbuname From linimon at FreeBSD.org Sun Dec 28 19:06:39 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Dec 28 19:06:48 2008 Subject: FreeBSD unmaintained ports which are currently scheduled for deletion Message-ID: <20081229030637.0F5D61CCD6@mail.droso.net> As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: audio/q-audio description: Q-Audio -- digital audio interface for the Q language maintainer: ports@FreeBSD.org deprecated because: depends on deprecated port lang/q expiration date: 2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=q-audio portname: audio/xmms-imms description: Automatic, weight-based playlist ordering plugin for XMMS maintainer: ports@FreeBSD.org status: BROKEN deprecated because: does not configure or build expiration date: 2009-02-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=xmms-imms portname: chinese/stardict2-dict-zh_TW description: English-Chinese(T)/Chinese(T)-English dictionaries for StarDict maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=stardict2-dict-zh_TW portname: devel/cogito description: The Cogito Version Control System maintainer: ports@FreeBSD.org status: BROKEN deprecated because: expiration date: 2009-01-11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=cogito portname: devel/p5-Getopt-Mixed description: Perl module for processing of both short and long command line options maintainer: ports@FreeBSD.org deprecated because: Use devel/p5-Getopt-Long instead expiration date: 2007-04-23 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-Getopt-Mixed portname: devel/py-coro description: Python coroutine implementation maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=py-coro portname: editors/sam description: A unix version of Rob Pike's editor for plan9 maintainer: ports@FreeBSD.org deprecated because: distfile and homepage disappeared expiration date: 2007-01-04 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=sam portname: graphics/q-graph description: Q-Graph -- graph library and editor for the Q language maintainer: ports@FreeBSD.org deprecated because: depends on deprecated port lang/q expiration date: 2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=q-graph portname: java/cacao description: JIT compiler for JAVA maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=cacao portname: lang/pm3-base description: Compiler and base libs of Polytechnique Montreal Modula-3 distribution maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-base portname: lang/pm3-forms description: High-level GUI libraries and tools for the PM3 Modula-3 distribution maintainer: ports@FreeBSD.org deprecated because: depends on broken, expired port expiration date: 2008-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-forms portname: lang/pm3-gui description: Low-level GUI libraries for the PM3 Modula-3 distribution maintainer: ports@FreeBSD.org deprecated because: depends on broken, expired port expiration date: 2008-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-gui portname: lang/pm3-m3tk description: Modula-3 source code analysis and transformation toolkit (PM3 distribution) maintainer: ports@FreeBSD.org deprecated because: depends on broken, expired port expiration date: 2008-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-m3tk portname: lang/pm3-net description: Low-level networking libraries for the PM3 Modula-3 distribution maintainer: ports@FreeBSD.org deprecated because: depends on broken, expired port expiration date: 2008-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-net portname: lang/pm3-netobj description: PM3 distributed objects package supporting robust distributed applications maintainer: ports@FreeBSD.org deprecated because: depends on broken, expired port expiration date: 2008-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-netobj portname: lang/q description: Q -- equational programming language maintainer: ports@FreeBSD.org status: BROKEN deprecated because: old version, broken plist expiration date: 2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=q portname: lang/quack description: Enhanced support for editing and running Scheme code maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=quack portname: misc/pybliographer description: GUI and command-line tools for editing and searching bibliographic databases maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=pybliographer portname: multimedia/mythtv description: MythTV is a homebrew PVR project maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mythtv portname: net-mgmt/NeTraMet description: Implementation of the Internet Accounting Architecture maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=NeTraMet portname: net/gnometelnet description: A nice frontend to the telnet, ssh, and rlogin clients for GNOME maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=gnometelnet portname: net/libunpipc description: The networking library used in UNIX Network Programming Volume 2 2e maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=libunpipc portname: net/py-mantissa description: Mantissa is an application server using the DivMod components maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=py-mantissa portname: net/versuch description: H323 voice&video proxy maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=versuch portname: palm/pdbc description: Palm DataBase Compiler/Decompiler maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=pdbc portname: print/ifhp description: IFHP - A highly configurable print filter for LPRng maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=ifhp portname: print/virtualpaper description: Virtual Paper document storage and viewing software maintainer: ports@FreeBSD.org deprecated because: depends on broken, expired port expiration date: 2008-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=virtualpaper portname: www/jakarta-tomcat4 description: Open-source Java web server by Apache, stable 4.0.x branch maintainer: ports@FreeBSD.org deprecated because: www/jakarta-tomcat5 is recommended instead for new installations expiration date: 2009-01-12 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=jakarta-tomcat4 portname: www/jakarta-tomcat5 description: Open-source Java web server by Apache, 5.0.x branch maintainer: ports@FreeBSD.org deprecated because: Old version, consider using www/tomcat55 or www/tomcat6 instead expiration date: 2009-01-12 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=jakarta-tomcat5 portname: www/ocaml-wdialog description: Advanced system to create dialog-centric web applications maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=ocaml-wdialog portname: x11-themes/gtk-industrial-theme description: Slick theme for GTK1 from Ximian maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-themes&portname=gtk-industrial-theme portname: x11-toolkits/p5-Gnome description: The main Gnome module of Gtk-Perl maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-Gnome portname: x11-toolkits/p5-GtkXmHTML description: The HTML widget module of Gtk-Perl maintainer: ports@FreeBSD.org deprecated because: depends on a broken, expired port expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-GtkXmHTML portname: x11-toolkits/py-fox description: Python interface to FOX Graphics library maintainer: ports@FreeBSD.org deprecated because: depends on deprecated port x11-toolkits/fox10 expiration date: 2009-01-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=py-fox portname: x11-toolkits/scx description: A GUI library for scsh and Scheme 48 maintainer: ports@FreeBSD.org deprecated because: Version branch long since retired expiration date: 2007-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=scx portname: x11-toolkits/wxmozilla description: Embedding Mozilla in wxWidgets maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=wxmozilla portname: x11-toolkits/xclasses description: C++ layout library for X maintainer: ports@FreeBSD.org deprecated because: Version branch long since retired expiration date: 2007-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=xclasses portname: x11-toolkits/xg description: Windows(tm) controls - like widget set for Motif(tm) maintainer: ports@FreeBSD.org deprecated because: Project is dead, last release from 1998 expiration date: 2007-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=xg portname: x11-wm/fluxspace description: A window manager and workspace enhancer and integrator maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=fluxspace portname: x11/bbuname description: A Flux/Black-box applet displaying system information a la GNU uname maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=bbuname From linimon at FreeBSD.org Sun Dec 28 19:06:51 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Dec 28 19:07:12 2008 Subject: FreeBSD ports which are currently scheduled for deletion Message-ID: <20081229030649.9D0C11CC51@mail.droso.net> As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: audio/dream description: Digital Radio Mondiale (DRM) software receiver maintainer: xride@FreeBSD.org deprecated because: Needs DRM enabled in FAAD expiration date: 2009-01-06 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20081218140000/dream-1.6.25_4.log (Wed Dec 24 22:21:45 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=dream portname: audio/gstreamer-plugins-spc description: Gstreamer OpenSPC frontend maintainer: multimedia@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gstreamer-plugins-spc portname: audio/py-sdl_mixer description: Pysdl_mixer is a python interface to SDL's sdl_mixer maintainer: acm@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-sdl_mixer portname: audio/q-audio description: Q-Audio -- digital audio interface for the Q language maintainer: ports@FreeBSD.org deprecated because: depends on deprecated port lang/q expiration date: 2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=q-audio portname: audio/xmms-imms description: Automatic, weight-based playlist ordering plugin for XMMS maintainer: ports@FreeBSD.org status: BROKEN deprecated because: does not configure or build expiration date: 2009-02-09 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=xmms-imms portname: cad/opencascade description: Open CASCADE Technology, 3D modeling & numerical simulation maintainer: thierry@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=opencascade portname: chinese/stardict2-dict-zh_TW description: English-Chinese(T)/Chinese(T)-English dictionaries for StarDict maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=stardict2-dict-zh_TW portname: databases/firebird-client description: The open-source InterBase(tm) 6.0 spin-off (client) maintainer: skv@FreeBSD.org status: IGNORE deprecated because: no longer under development, please consider using Firebird2 expiration date: 2009-02-24 build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20081228115029/firebird-client-1.5.5.log (Sun Dec 28 14:20:04 UTC 2008) overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=firebird-client portname: databases/firebird-server description: The open-source InterBase(tm) 6.0 spin-off (Classic version) maintainer: skv@FreeBSD.org status: IGNORE deprecated because: no longer under development, please consider using Firebird2 expiration date: 2009-02-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=firebird-server portname: databases/mysqlbigram description: Simple N-Gram (bi-gram) FULLTEXT parser plugin for MySQL 5.1+ maintainer: gslin@gslin.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=mysqlbigram portname: deskutils/remember.el description: A Emacs mode for remembering data maintainer: dryice@dryice.name status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=remember.el portname: devel/cogito description: The Cogito Version Control System maintainer: ports@FreeBSD.org status: BROKEN deprecated because: expiration date: 2009-01-11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=cogito portname: devel/hs-hat description: A source-level tracer for Haskell 98 maintainer: haskell@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hs-hat portname: devel/hs-hpl description: Haskell Ports Library provides ports in Haskell maintainer: haskell@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hs-hpl portname: devel/p5-Getopt-Mixed description: Perl module for processing of both short and long command line options maintainer: ports@FreeBSD.org deprecated because: Use devel/p5-Getopt-Long instead expiration date: 2007-04-23 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-Getopt-Mixed portname: devel/py-coro description: Python coroutine implementation maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=py-coro portname: dns/bind9-dlz description: The Berkeley Internet Name Daemon, with DLZ extensions maintainer: dinoex@FreeBSD.org status: FORBIDDEN deprecated because: DLZ functions are now included in bind9.4 expiration date: 2008-08-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=dns&portname=bind9-dlz portname: editors/sam description: A unix version of Rob Pike's editor for plan9 maintainer: ports@FreeBSD.org deprecated because: distfile and homepage disappeared expiration date: 2007-01-04 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=sam portname: games/emacs-chess description: Play chess with emacs maintainer: dryice@dryice.name status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=emacs-chess portname: games/planeshift description: First 3D MMORPG to be free for players maintainer: acm@FreeBSD.org deprecated because: Depends on broken, expired port expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=planeshift portname: graphics/crystalentitylayer-devel description: CEL is a layer that sits on top of Crystal Space 3D Engine maintainer: acm@FreeBSD.org deprecated because: Depends on broken, expired port expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=crystalentitylayer-devel portname: graphics/crystalspace-devel description: Free and portable 3D Game Development Kit maintainer: acm@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=crystalspace-devel portname: graphics/q-graph description: Q-Graph -- graph library and editor for the Q language maintainer: ports@FreeBSD.org deprecated because: depends on deprecated port lang/q expiration date: 2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=q-graph portname: java/cacao description: JIT compiler for JAVA maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=cacao portname: java/dbvis description: DbVisualizer database tool maintainer: contact@toha.org.ua status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=dbvis portname: lang/pm3-base description: Compiler and base libs of Polytechnique Montreal Modula-3 distribution maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-base portname: lang/pm3-forms description: High-level GUI libraries and tools for the PM3 Modula-3 distribution maintainer: ports@FreeBSD.org deprecated because: depends on broken, expired port expiration date: 2008-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-forms portname: lang/pm3-gui description: Low-level GUI libraries for the PM3 Modula-3 distribution maintainer: ports@FreeBSD.org deprecated because: depends on broken, expired port expiration date: 2008-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-gui portname: lang/pm3-m3tk description: Modula-3 source code analysis and transformation toolkit (PM3 distribution) maintainer: ports@FreeBSD.org deprecated because: depends on broken, expired port expiration date: 2008-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-m3tk portname: lang/pm3-net description: Low-level networking libraries for the PM3 Modula-3 distribution maintainer: ports@FreeBSD.org deprecated because: depends on broken, expired port expiration date: 2008-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-net portname: lang/pm3-netobj description: PM3 distributed objects package supporting robust distributed applications maintainer: ports@FreeBSD.org deprecated because: depends on broken, expired port expiration date: 2008-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=pm3-netobj portname: lang/q description: Q -- equational programming language maintainer: ports@FreeBSD.org status: BROKEN deprecated because: old version, broken plist expiration date: 2008-12-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=q portname: lang/quack description: Enhanced support for editing and running Scheme code maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=quack portname: mail/claws-mail-clamav description: Clamav plugin for claws-mail maintainer: miwi@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=claws-mail-clamav portname: mail/sylpheed2-devel description: A lightweight, featureful, and fast GTK+ based e-mail client maintainer: nork@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=sylpheed2-devel portname: misc/heyu description: Control a CM11A interface from the command line maintainer: mstowe@chicago.us.mensa.org deprecated because: no longer under development, use misc/heyu2 expiration date: 2008-12-06 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=heyu portname: misc/pybliographer description: GUI and command-line tools for editing and searching bibliographic databases maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=pybliographer portname: multimedia/helixplayer description: The Helix Community's open source media player maintainer: shaun@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=helixplayer portname: multimedia/mjpegtools-yuvfilters description: Mjpeg-tools YUV video stream processing tools maintainer: multimedia@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mjpegtools-yuvfilters portname: multimedia/mythtv description: MythTV is a homebrew PVR project maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=mythtv portname: net-im/sulci description: A Jabber bot maintainer: dsh@vlink.ru status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-im&portname=sulci portname: net-mgmt/NeTraMet description: Implementation of the Internet Accounting Architecture maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=NeTraMet portname: net-p2p/peercast description: A peer-to-peer network for broadcasting and listening to streams maintainer: jadawin@FreeBSD.org status: FORBIDDEN deprecated because: has been forbidden for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=peercast portname: net/acx100 description: Texas Instruments (TI) ACX100 IEEE 802.11 driver maintainer: leoz.2005@gmail.com status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=acx100 portname: net/gacxtool description: Displays the status of the ACX driver maintainer: leoz.2005@gmail.com deprecated because: depends on expired, broken port expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=gacxtool portname: net/gnometelnet description: A nice frontend to the telnet, ssh, and rlogin clients for GNOME maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=gnometelnet portname: net/libunpipc description: The networking library used in UNIX Network Programming Volume 2 2e maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=libunpipc portname: net/py-mantissa description: Mantissa is an application server using the DivMod components maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=py-mantissa portname: net/versuch description: H323 voice&video proxy maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=versuch portname: news/sabnzbd description: A web-interface based binary newsgrabber in python, with nzb support maintainer: daniel@netwalk.org deprecated because: no longer developed, use news/sabnzbdplus instead expiration date: 2008-12-21 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=news&portname=sabnzbd portname: palm/pdbc description: Palm DataBase Compiler/Decompiler maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=pdbc portname: print/ifhp description: IFHP - A highly configurable print filter for LPRng maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=ifhp portname: print/virtualpaper description: Virtual Paper document storage and viewing software maintainer: ports@FreeBSD.org deprecated because: depends on broken, expired port expiration date: 2008-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=print&portname=virtualpaper portname: security/openssl-stable description: SSL and crypto library maintainer: dinoex@FreeBSD.org status: IGNORE deprecated because: expiration date: 2008-11-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=openssl-stable portname: security/squidclam description: Bridge betwean ClamAV antivirus software and Squid caching proxy maintainer: alecn2002@yandex.ru status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=squidclam portname: security/xyssl description: A liteweight SSL and TLS toolkit for C developers maintainer: mattdharris@users.sourceforge.net deprecated because: Download sites are down, cannot update due to software website being down. expiration date: 2008-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=xyssl portname: textproc/p5-Text-CSV_PP description: Comma-separated values manipulation routines PP version maintainer: perl@FreeBSD.org deprecated because: textproc/Text-CSV_PP was merged into textproc/p5-Text-CSV expiration date: 2008-12-11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=p5-Text-CSV_PP portname: textproc/py-wbxml description: Python bindings for the wbxml2 library maintainer: ports@logvinov.com deprecated because: No longer supported by developers expiration date: 2009-01-24 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=py-wbxml portname: www/c-icap description: An implementation of an ICAP server maintainer: b3k@mail.ru status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=c-icap portname: www/cybercalendar description: CyberCalendar is a web based calendar program written in perl maintainer: janos.mohacsi@bsd.hu status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=cybercalendar portname: www/geneweb description: An advanced genealogy software maintainer: hubert@frbsd.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=geneweb portname: www/jakarta-tomcat4 description: Open-source Java web server by Apache, stable 4.0.x branch maintainer: ports@FreeBSD.org deprecated because: www/jakarta-tomcat5 is recommended instead for new installations expiration date: 2009-01-12 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=jakarta-tomcat4 portname: www/jakarta-tomcat5 description: Open-source Java web server by Apache, 5.0.x branch maintainer: ports@FreeBSD.org deprecated because: Old version, consider using www/tomcat55 or www/tomcat6 instead expiration date: 2009-01-12 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=jakarta-tomcat5 portname: www/ocaml-wdialog description: Advanced system to create dialog-centric web applications maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=ocaml-wdialog portname: www/ocsigen description: Web programming framework for OCaml maintainer: jaapb@kerguelen.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=ocsigen portname: www/pecl-mnogosearch description: The mnoGoSearch Bindings for php51+ maintainer: breaker1@gmail.com status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=pecl-mnogosearch portname: www/squid26 description: HTTP Caching Proxy maintainer: tmseck@web.de deprecated because: The 2.6 series is no longer actively maintained by the Squid developers expiration date: 2009-03-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=squid26 portname: www/tdiary-devel description: A Web-based diary system (like weblog) written in Ruby maintainer: tota@rtfm.jp status: FORBIDDEN deprecated because: has been forbidden for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=tdiary-devel portname: www/zope description: An object-based web application platform maintainer: estartu@augusta.de status: FORBIDDEN deprecated because: has been forbidden for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=zope portname: www/zope-btreefolder2 description: Zope product that can store many items maintainer: kaeru@inigo-tech.com deprecated because: Included in Zope 2.8 and later expiration date: 2007-08-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=zope-btreefolder2 portname: x11-themes/gtk-industrial-theme description: Slick theme for GTK1 from Ximian maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-themes&portname=gtk-industrial-theme portname: x11-toolkits/fox10 description: Fast and extensive C++ GUI toolkit maintainer: araujo@FreeBSD.org status: BROKEN deprecated because: does not compile with latest gcc; use x11-toolkits/fox16 instead expiration date: 2009-01-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=fox10 portname: x11-toolkits/fxscintilla-fox10 description: A Fox toolkit reimplementation of Scintilla editing widget maintainer: araujo@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=fxscintilla-fox10 portname: x11-toolkits/p5-Gnome description: The main Gnome module of Gtk-Perl maintainer: ports@FreeBSD.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date: 2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-Gnome portname: x11-toolkits/p5-GtkXmHTML description: The HTML widget module of Gtk-Perl maintainer: ports@FreeBSD.org deprecated because: depends on a broken, expired port expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=p5-GtkXmHTML portname: x11-toolkits/py-fox description: Python interface to FOX Graphics library maintainer: ports@FreeBSD.org deprecated because: depends on deprecated port x11-toolkits/fox10 expiration date: 2009-01-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=py-fox portname: x11-toolkits/ruby-fox10 description: Ruby extension module to use FOX, aka FXRuby maintainer: araujo@FreeBSD.org deprecated because: depends on deprecated port x11-toolkits/fox10 expiration date: 2009-01-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=ruby-fox10 portname: x11-toolkits/scx description: A GUI library for scsh and Scheme 48 maintainer: ports@FreeBSD.org deprecated because: Version branch long since retired expiration date: 2007-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=scx portname: x11-toolkits/wxmozilla description: Embedding Mozilla in wxWidgets maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=wxmozilla portname: x11-toolkits/xclasses description: C++ layout library for X maintainer: ports@FreeBSD.org deprecated because: Version branch long since retired expiration date: 2007-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=xclasses portname: x11-toolkits/xg description: Windows(tm) controls - like widget set for Motif(tm) maintainer: ports@FreeBSD.org deprecated because: Project is dead, last release from 1998 expiration date: 2007-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=xg portname: x11-wm/fluxspace description: A window manager and workspace enhancer and integrator maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-wm&portname=fluxspace portname: x11/bbuname description: A Flux/Black-box applet displaying system information a la GNU uname maintainer: ports@FreeBSD.org status: BROKEN deprecated because: has been broken for more than 6 months expiration date: 2009-01-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=bbuname From linimon at FreeBSD.org Sun Dec 28 19:06:55 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Dec 28 19:07:13 2008 Subject: FreeBSD unmaintained ports which are currently marked forbidden Message-ID: <20081229030655.37B961CD01@mail.droso.net> As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: chinese/wordpress forbidden because: http://www.vuxml.org/freebsd/622bc638-be27-11dd-a578-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=wordpress portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: www/linux-firefox-devel forbidden because: Security issus http://www.vuxml.org/freebsd/f29fea8f-b19f-11dd-a55e-00163e000016.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-firefox-devel From linimon at FreeBSD.org Sun Dec 28 19:06:56 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Dec 28 19:07:14 2008 Subject: FreeBSD ports which are currently marked forbidden Message-ID: <20081229030656.3991A1CD0C@mail.droso.net> As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: chinese/wordpress forbidden because: http://www.vuxml.org/freebsd/622bc638-be27-11dd-a578-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=wordpress portname: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: dns/bind9-dlz forbidden because: vulnerable to cache poisioning if recursive lookup enabled build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=dns&portname=bind9-dlz portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: net-p2p/peercast forbidden because: arbitrary code execution, http://www.vuxml.org/freebsd/402ae710-26a2-11dd-ae05-825f4c35000a.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=peercast portname: www/linux-firefox-devel forbidden because: Security issus http://www.vuxml.org/freebsd/f29fea8f-b19f-11dd-a55e-00163e000016.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-firefox-devel portname: www/tdiary-devel forbidden because: contains a vulnerability: http://www.tdiary.org/20071215.html written in Japanese build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=tdiary-devel portname: www/twiki forbidden because: Remote server compromise vulnerability in this version build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=twiki portname: www/zope forbidden because: contains cross-site scripting vulnerability http://VuXML.FreeBSD.org/34414a1e-e377-11db-b8ab-000c76189c4c.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=zope From venture37 at gmail.com Sun Dec 28 19:08:09 2008 From: venture37 at gmail.com (Sevan / Venture37) Date: Sun Dec 28 19:08:16 2008 Subject: minimal FreeSBIE bombs out In-Reply-To: <28283d910812281818p523d09f5wd2062fed32154fc4@mail.gmail.com> References: <495829E5.5010109@gmail.com> <28283d910812281818p523d09f5wd2062fed32154fc4@mail.gmail.com> Message-ID: <49583F15.4020100@gmail.com> matt donovan wrote: > does your normal buildworld bomb out? I tend to do a make buildworld > outside of freesbie then just put NO_BUILDWORLD in my freesbie.conf. I don't have any problems running make buildworld when doing system upgrades. I've copied the make.conf.minimal which is bundled with freesbie to /etc/make.conf & rerun make buildworld by hand, same thing happend, it bombed out. From bugmaster at FreeBSD.org Mon Dec 29 03:06:07 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 29 03:06:32 2008 Subject: Current unassigned ports problem reports Message-ID: <200812291106.mBTB66a0023415@freefall.freebsd.org> (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/130017 Request for reprocopy of net-mgmt/hobbit-* net-mgmt/xy o ports/130014 New port: sysutils/rsyslog4 - Syslogd supporting SQL, o ports/130012 [PATCH] sysutils/rubygem-capistrano: update to 2.5.3 f ports/129977 [UPDATE] net/acx100 to latest (working?) version f ports/129918 devel/pwlib broken by recent changes to routing on 8-C o ports/129893 net/nxserver: ldconfig not set up properly f ports/129878 www/linux-flashplugin9 unfetchable f ports/129864 editors/emacs-devel fails to build when gettext f ports/129830 print/hplip configure thinks python2.5 < phython2.2 f ports/129817 math/R ports can't compile with WITHOUT_X11 option f ports/129781 [PATCH] net-mgmt/zabbix-agent: update to 1.6.1 f ports/129780 [PATCH] net-mgmt/zabbix: update to 1.6.1 o ports/129763 [patch] add HTTP locations of OpenBSD mirrors to bsd.s f ports/129740 www/linux-flashplugin9 distinfo incorrect f ports/129716 databases/rrdtool: ideas to remove dejavu and X11 depe f ports/129685 Update port: x11-fonts/proggy_fonts Add some contribut o ports/129677 /usr/ports/sysutils/aaccli Bad system call: 12 (core d f ports/129629 databases/mysql-connector-odbc (3.51.26) compile fails o ports/129606 benchmarks/iozone does not support O_DIRECT o ports/129598 Update ports: finance/aqbanking, devel/gwenhywfar to 3 f ports/129478 multimedia/acidrip: patch file to commit to ports f ports/129453 ports-mgmt/jailaudit does not work since jail supporti f ports/129439 devel/libusb does not compile in FreeBSD 7.0-RELEASE f ports/129435 java/jakarta-commons-dbcp not BROKEN on jdk15 f ports/129369 Failed to build multimedia/mencoder with samba support o ports/129363 devel/ace build fails if kernel module aio is loaded o ports/128726 [NEW PORT] print/lyx16: Document processor interfaced o ports/128603 textproc/flex has too small capacity f ports/128490 net/freenx port does not work properly on freebsd-7 st f ports/128271 biology/ncbi-toolkit - blastall segfaults when output o ports/128140 update devel/pwlib to 2.4.1 to fit GNOME 2.24 f ports/128082 sysutils/megarc binary causes memory corruption f ports/128074 multimedia/mplayer does not play CSS encrypted DVDs o ports/127978 ftp/jftpgw - 'pidfile=/var/run/jftpgw.pid' interferes f ports/127854 [PATCH] databases/couchdb: update to 0.8.1 f ports/127810 print/hplip 2.8.2 can't talk to my usnb printer (HP PS o ports/127728 ports/games/freebsd-games doesn't build, and larn(6) s f ports/127513 mail/dcc-dccd sets home to /var/dcc even if you didn' o ports/127377 java/netbeans61 fails to make internet connections o ports/127321 japanese/kon2-16dot: buffer overflow and mouse bugs f ports/127302 security/swatch: swatch-3.2.1_1 multiple issues f ports/127181 audio/musicpd logs warning s ports/127087 mail/bincimap port does not include an rc.d file f ports/126518 Unbroke archivers/lzo2 on i386 f ports/126058 net/generic-nqs fails to compile f ports/126055 x11-toolkits/p5-Tk - segmentation fault running perl-t o ports/125719 shells/pdksh, zombie process's occouring on SMP Machin o ports/125714 [patch] www/httptunnel: users not added o ports/125201 audio/aqualung crashes s ports/124548 net/mDNSResponder port incompatible with gnome desktop o ports/123247 linux-firefox and linux-seamonkey from multiple users o ports/123068 sysutils/bubblemon2 bubblemon-dockapp: error extractin o ports/121259 New port: net/openamq OpenAMQ is a complete AMQP messa o ports/121050 New port: sysutils/heartbeat2 Linux High-Availability f ports/116385 net/vnc using vnc.so crashes Xorg 7.3 when remote comp f ports/115304 multimedia/gpac-mp4box cannot import files larger than f ports/114106 mail/postgrey does not properly shut down via rc.d scr o ports/108795 ports/icc: Proposed update to icc port for intel compi f ports/107304 print/apsfilter does not print PDF to raw PostScript p o amd64/104311 ports/wine should be installable on amd64 s ports/85513 Intel C++ compiler not 100% binary compatible with sys 61 problems total. From peterjeremy at optushome.com.au Mon Dec 29 04:18:38 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Mon Dec 29 04:18:46 2008 Subject: timeseal -- bad system call In-Reply-To: <49582B49.6000003@friedemann.us> References: <49582B49.6000003@friedemann.us> Message-ID: <20081229101107.GB67480@server.vk2pj.dyndns.org> On 2008-Dec-28 19:43:37 -0600, Scott D Friedemann wrote: >I'm not sure how to enable compat.sigaction and would appreciate any >assistance that can be given. I have a.out compiled into the kernel. You need COMPAT_43 in your kernel. Any code calling compat.sigaction is _really_ old - that interface was obsoleted before FreeBSD 4.x -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081229/8809007d/attachment.pgp From tingox at gmail.com Mon Dec 29 04:53:21 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Mon Dec 29 04:53:27 2008 Subject: amule 2 port - trying an upgrade In-Reply-To: <20080823020518.GA75067@hades.panopticon> References: <20080821105506.GA25154@wep4017.physik.uni-wuerzburg.de> <20080822125845.GB4663@hades.panopticon> <20080822221339.GH1421@hades.panopticon> <20080823020518.GA75067@hades.panopticon> Message-ID: Hello, Real life got in the way, and my amule2 porting efforts had to be put on hold. Buttime waits for no man, and now aMule 2.2.3 has been released. So I wil restart my efforts with the newest version. On Sat, Aug 23, 2008 at 3:05 AM, Dmitry Marakasov wrote: > No, they are automake's macro language and are expanded my automake > to produce Makefile.in. Since the final product is Makefiles, shell > stuff is possible there. > > However, you shouldn't modify .am stuff in this case, as automake > is not executed in the build process. The only things you're to > modify are configure and Makefile.in files. > You can, of course, modify .am stuff instead and call automake/autoconf > to regenerate stuff (via USE_AUTOTOOLS), but that's only needed in > extreme cases. Thanks for explaining this. > PORTREVISION should be removed when PORTVERSION is bumped Good to know. >> +USE_XORG= x11 > Not actually needed, as the port uses wx which assumes x11. OK, I'll remove it then. >> +USE_GETTEXT= yes > Using gettext conditionally like before no longer work? I don't really know. What exactly do we gain by using gettext conditionally? >> -CONFIGURE_TARGET=--build=${MACHINE_ARCH}-portbld-freebsd${OSREL} >> + >> +CONFIGURE_TARGET= --build=${MACHINE_ARCH}-portbld-freebsd${OSREL} > Please remove, this is now handled automatically. Ok, will do. >> CONFIGURE_ARGS= --disable-debug \ >> + --mandir=${MANPREFIX}/man \ > Not needed, --mandir is appended to CONFIGURE_ARGS by default I had noted that, but forhot tom remove that part. >> -.if !defined(WITHOUT_OPTIMIZE) >> +.if defined(WITH_OPTIMIZE) > No, checking WITHOUT_OPTIMIZE is correct. You should check > counter-default values for options, i.e. check WITH_FOO if FOO is > off by default, and WITHOUT_FOO if FOO is on by default. Same for > other checks. Is this documented in the Porters Handbook anywhere? If so, I must have missed it. > There are automatic ways to handle docs, so you don't need to change > plist on every update. > > One way is to define DOCSDIR in the Makefile: > DOCSDIR= ${PREFIX}/share/doc/aMule-${PORTVERSION} > > and use %%DOCSDIR%% instead of share/doc/aMule-2.2.2 in the plist. > > Another way is to add PORTDOCS=* to Makefile in addition to DOCSDIR, > and remove doc files from plist completely - they'll be added > automatically on install. I will look into this. Your comments are valuable - thank you. -- Regards, Torfinn Ingolfsen, Norway From ricardo.meb.jesus at gmail.com Mon Dec 29 04:53:33 2008 From: ricardo.meb.jesus at gmail.com (Ricardo Jesus) Date: Mon Dec 29 04:53:40 2008 Subject: linux-enemyterritory In-Reply-To: <3f1fd1ea0812230938q6187ed1am26b33499f07bc295@mail.gmail.com> References: <200812230033.43040.g.martinez@pcbsd.es> <7d6fde3d0812221648k6d99d0acsa0d13c96193f8417@mail.gmail.com> <3f1fd1ea0812230938q6187ed1am26b33499f07bc295@mail.gmail.com> Message-ID: <4958C3EA.20606@gmail.com> Michal Varga wrote: > On Tue, Dec 23, 2008 at 1:48 AM, Garrett Cooper wrote: >> On 12/22/08, Gonzalo Mart?nez-Sanjuan S?nchez wrote: >>> Hi there! >>> >>> I have a problem with the enemyterritory port using linux compat layer. The >>> game has no sound. The only problem I get its this messagge: >>> >>> ------- sound initialization ------- >>> /dev/dsp: Invalid argument >>> Could not mmap /dev/dsp >>> ------------------------------------ >>> >>> Have someone any other problem like that??? >>> Is that somekind of already known bug? >>> > Yep, for a long time, sort of. Though I haven't been playing ET for > quite a while, I'm pretty positive that the patch linked here will > solve your problem, hopefuly it can still be applied cleanly these > days: > http://lists.freebsd.org/pipermail/freebsd-current/2007-June/073454.html > > Dunno why it never got commited/properly fixed, maybe you can push > someone to finish it this time :) > > m. > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" No need for a patch. It's simply a matter of sysctl. Take a look here: http://linux-bsd-sharing.blogspot.com/2008/12/tip-enable-sound-on-enemy-territory.html Happy fragging. From stanb at panix.com Mon Dec 29 17:04:40 2008 From: stanb at panix.com (stan) Date: Mon Dec 29 17:04:47 2008 Subject: Build problems with amarok Message-ID: <20081229164749.GA19620@teddy.fas.com> I'm building a new machine which I cvsup'd yesterday. I am having trouble getting the amarok port to compile. here is the end of the compile failure: /usr/local/bin/moc ./njbmediadevice.h -o njbmediadevice.moc.cpp /bin/sh /usr/local/bin/libtool --silent --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../amarok/src -I../../../../amarok/src -I../../../../amarok/src/amarokcore -I../../../../amarok/src/amarokcore -I../../../../amarok/src/engine -I../../../../amarok/src/engine -I../../../../amarok/src/mediadevice -I/usr/local/include/taglib -I/usr/local/include -I/usr/local/include -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -D_THREAD_SAFE -Wno-long-long -Wundef -Wall -W -Wpointer-arith -O2 -fno-strict-aliasing -pipe -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT njbmediadevice.moc.lo -MD -MP -MF .deps/njbmediadevice.moc.Tpo -c -o njbmediadevice.moc.lo njbmediadevice.moc.cpp mv -f .deps/njbmediadevice.moc.Tpo .deps/njbmediadevice.moc.Plo /bin/sh /usr/local/bin/libtool --silent --tag=CXX --mode=link c++ -Wno-long-long -Wundef -Wall -W -Wpointer-arith -O2 -fno-strict-aliasing -pipe -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -avoid-version -module -no-undefined -R /usr/local/lib -R /usr/local/lib -R /usr/local/lib -R /usr/local/lib -R /usr/local/lib -D_THREAD_SAFE -pthread -L/usr/local/lib -D_THREAD_SAFE -pthread -L/usr/local/lib -L/usr/local/lib -o libamarok_njb-mediadevice.la -rpath /usr/local/lib/kde3 njbmediadevice.lo playlist.lo track.lo njbmediadevice.moc.lo ../../../../amarok/src/libamarok.la -lkdeui -lkdecore -lnjb -Wl,-export-dynamic -L/usr/local/lib -ljpeg -L/usr/local/lib gmake[5]: Leaving directory `/usr/ports/audio/amarok/work/amarok-1.4.10/amarok/src/mediadevice/njb' Making all in mtp gmake[5]: Entering directory `/usr/ports/audio/amarok/work/amarok-1.4.10/amarok/src/mediadevice/mtp' /bin/sh /usr/local/bin/libtool --silent --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../amarok/src -I../../../../amarok/src -I../../../../amarok/src/amarokcore -I../../../../amarok/src/amarokcore -I../../../../amarok/src/engine -I../../../../amarok/src/engine -I../../../../amarok/src/mediadevice -I/usr/local/include/taglib -I/usr/local/include -I/usr/local/include -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT -I/usr/local/include -D_THREAD_SAFE -Wno-long-long -Wundef -Wall -W -Wpointer-arith -O2 -fno-strict-aliasing -pipe -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT mtpmediadevice.lo -MD -MP -MF .deps/mtpmediadevice.Tpo -c -o mtpmediadevice.lo mtpmediadevice.cpp /usr/local/include/libmtp.h: In member function 'virtual MediaItem* MtpMediaDevice::copyTrackToDevice(const MetaBundle&)': /usr/local/include/libmtp.h:489: error: too many arguments to function 'int LIBMTP_Send_Track_From_File(LIBMTP_mtpdevice_t*, const char*, LIBMTP_track_t*, int (*)(uint64_t, uint64_t, const void*), const void*)' mtpmediadevice.cpp:302: error: at this point in file mtpmediadevice.cpp: In member function 'uint32_t MtpMediaDevice::getDefaultParentId()': mtpmediadevice.cpp:383: warning: deprecated conversion from string constant to 'char*' /usr/local/include/libmtp.h: In member function 'LIBMTP_album_t* MtpMediaDevice::getOrCreateAlbum(QPtrList*)': /usr/local/include/libmtp.h:533: error: too many arguments to function 'int LIBMTP_Create_New_Album(LIBMTP_mtpdevice_t*, LIBMTP_album_t*)' mtpmediadevice.cpp:532: error: at this point in file /usr/local/include/libmtp.h: In member function 'uint32_t MtpMediaDevice::createFolder(const char*, uint32_t)': /usr/local/include/libmtp.h:508: error: too few arguments to function 'uint32_t LIBMTP_Create_Folder(LIBMTP_mtpdevice_t*, char*, uint32_t, uint32_t)' mtpmediadevice.cpp:611: error: at this point in file /usr/local/include/libmtp.h: In member function 'void MtpMediaDevice::playlistFromItem(MtpMediaItem*)': /usr/local/include/libmtp.h:521: error: too many arguments to function 'int LIBMTP_Create_New_Playlist(LIBMTP_mtpdevice_t*, LIBMTP_playlist_t*)' mtpmediadevice.cpp:916: error: at this point in file gmake[5]: *** [mtpmediadevice.lo] Error 1 gmake[5]: Leaving directory `/usr/ports/audio/amarok/work/amarok-1.4.10/amarok/src/mediadevice/mtp' Stop in /usr/ports/audio/amarok. *** Error code 1 Stop in /usr/ports/audio/amarok. # ^Dexit Script done on Mon Dec 29 11:33:50 2008 Can anyne sugest how to resolve this? -- One of the main causes of the fall of the roman empire was that, lacking zero, they had no way to indicate successful termination of their C programs. From tingox at gmail.com Mon Dec 29 17:15:22 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Mon Dec 29 17:15:28 2008 Subject: portupgrade fails - how to fix? In-Reply-To: References: <20081007082129.GA32825@holstein.holy.cow> <20081022140053.D39538@n.cwu.edu> Message-ID: Hello, Just so it won't be forgotten - the annoying bug in the latest version (2.4.6*) of portupgrade is still there: root@kg-v2# portupgrade -R xterm xscreensaver smartmontools [Gathering depends for x11/xterm ................................................................................................ done] [Exclude up-to-date packages .................................. done] /usr/local/lib/ruby/site_ruby/1.8/pkginfo.rb:74:in `initialize': : Not in due form: - (ArgumentError) from /usr/local/sbin/portupgrade:614:in `new' from /usr/local/sbin/portupgrade:614:in `main' from /usr/local/sbin/portupgrade:613:in `each' from /usr/local/sbin/portupgrade:613:in `main' from /usr/local/sbin/portupgrade:588:in `catch' from /usr/local/sbin/portupgrade:588:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:1303:in `call' from /usr/local/lib/ruby/1.8/optparse.rb:1303:in `parse_in_order' ... 7 levels... from /usr/local/lib/ruby/1.8/optparse.rb:785:in `initialize' from /usr/local/sbin/portupgrade:229:in `new' from /usr/local/sbin/portupgrade:229:in `main' from /usr/local/sbin/portupgrade:2208 And the workaround is still to downgrade to version 2.4.3: root@kg-v2# portupgrade -f portupgrade ---> Downgrading 'portupgrade-2.4.6,2' to 'portupgrade-2.4.3_2,2' (ports-mgmt/portupgrade) ---> Building '/usr/ports/ports-mgmt/portupgrade' [......] ===> Registering installation for portupgrade-2.4.3_2,2 ===> Cleaning for portupgrade-2.4.3_2,2 ---> Cleaning out obsolete shared libraries [Updating the pkgdb in /var/db/pkg ... - 536 packages found (-0 +1) . done] root@kg-v2# after that, portupgrade works again. Continued happy holidays to all! -- Regards, Torfinn Ingolfsen From makc at freebsd.org Mon Dec 29 19:35:33 2008 From: makc at freebsd.org (Max Brazhnikov) Date: Mon Dec 29 19:35:39 2008 Subject: Build problems with amarok In-Reply-To: <20081229164749.GA19620@teddy.fas.com> References: <20081229164749.GA19620@teddy.fas.com> Message-ID: <200812292218.05073.makc@freebsd.org> On Mon, 29 Dec 2008 11:47:49 -0500, stan wrote: > I'm building a new machine which I cvsup'd yesterday. I am having trouble > getting the amarok port to compile. here is the end of the compile > failure: > Can anyne sugest how to resolve this? amarok was broken with libmtp update to 0.3.1 (ports/126905). Expectation that amarok will be updated soon is not right -- amarok2 (which is for KDE 4) will be added as separate port. So someone should recreate libmtp-0.2 for amarok. Max From makc at issp.ac.ru Mon Dec 29 20:05:46 2008 From: makc at issp.ac.ru (Max Brazhnikov) Date: Mon Dec 29 20:05:53 2008 Subject: Build problems with amarok In-Reply-To: <200812292218.05073.makc@freebsd.org> References: <20081229164749.GA19620@teddy.fas.com> <200812292218.05073.makc@freebsd.org> Message-ID: <200812292241.33940.makc@issp.ac.ru> On Mon, 29 Dec 2008 22:18:04 +0300, Max Brazhnikov wrote: > On Mon, 29 Dec 2008 11:47:49 -0500, stan wrote: > > I'm building a new machine which I cvsup'd yesterday. I am having trouble > > getting the amarok port to compile. here is the end of the compile > > failure: > > Can anyne sugest how to resolve this? > > amarok was broken with libmtp update to 0.3.1 (ports/126905). Expectation > that amarok will be updated soon is not right -- amarok2 (which is for KDE > 4) will be added as separate port. So someone should recreate libmtp-0.2 > for amarok. in the meantime you can build amarok without mtp support. Max From trebestie at gmail.com Mon Dec 29 20:22:50 2008 From: trebestie at gmail.com (Diego Depaoli) Date: Mon Dec 29 20:22:57 2008 Subject: Build problems with amarok In-Reply-To: <200812292218.05073.makc@freebsd.org> References: <20081229164749.GA19620@teddy.fas.com> <200812292218.05073.makc@freebsd.org> Message-ID: <83e5fb980812291149u196c822br6953a1077edd9d9d@mail.gmail.com> On Mon, Dec 29, 2008 at 8:18 PM, Max Brazhnikov wrote: > On Mon, 29 Dec 2008 11:47:49 -0500, stan wrote: >> I'm building a new machine which I cvsup'd yesterday. I am having trouble >> getting the amarok port to compile. here is the end of the compile >> failure: >> Can anyne sugest how to resolve this? > amarok was broken with libmtp update to 0.3.1 (ports/126905). Expectation that > amarok will be updated soon is not right -- amarok2 (which is for KDE 4) will > be added as separate port. So someone should recreate libmtp-0.2 for amarok. Put attached patch (taken from gentoo) into amarok/files and rebuild. It worked for me Cheers -- Diego Depaoli -------------- next part -------------- A non-text attachment was scrubbed... Name: patch-amarok_src_mediadevice_mtp_mtpmediadevice.cpp Type: application/octet-stream Size: 1911 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081229/4bc6b7d4/patch-amarok_src_mediadevice_mtp_mtpmediadevice.obj From amdmi3 at amdmi3.ru Mon Dec 29 21:43:14 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Mon Dec 29 21:43:21 2008 Subject: amule 2 port - trying an upgrade In-Reply-To: References: <20080821105506.GA25154@wep4017.physik.uni-wuerzburg.de> <20080822125845.GB4663@hades.panopticon> <20080822221339.GH1421@hades.panopticon> <20080823020518.GA75067@hades.panopticon> Message-ID: <20081229163113.GA81059@hades.panopticon> * Torfinn Ingolfsen (tingox@gmail.com) wrote: > >> +USE_GETTEXT= yes > > Using gettext conditionally like before no longer work? > I don't really know. What exactly do we gain by using gettext conditionally? Optional NLS support. Less depends, not installing unneeded locales if NLS is not needed. > >> -.if !defined(WITHOUT_OPTIMIZE) > >> +.if defined(WITH_OPTIMIZE) > > No, checking WITHOUT_OPTIMIZE is correct. You should check > > counter-default values for options, i.e. check WITH_FOO if FOO is > > off by default, and WITHOUT_FOO if FOO is on by default. Same for > > other checks. > > Is this documented in the Porters Handbook anywhere? Doesn't look like this. Maybe it should be. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From tingox at gmail.com Mon Dec 29 21:49:42 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Mon Dec 29 21:49:49 2008 Subject: aMule 22.3 porting - some questions Message-ID: Ok, I have passed the first milestone or two - the aMule 2.2.3 port now compiles and installs. During the install step I see this: if test "amule" = "gettext" \ && test '' = 'intl-compat.o'; then \ /bin/sh `case "./mkinstalldirs" in /*) echo "./mkinstalldirs" ;; *) echo ".././mkinstalldirs" ;; esac` /usr/local/lib /usr/local/include; \ install -o root -g wheel -m 444 libintl.h /usr/local/include/libintl.h; \ @LIBTOOL@ --mode=install \ install -o root -g wheel -m 444 libintl.a /usr/local/lib/libintl.a; \ else \ : ; \ fi These files are installed by gettext (verified with pkg_info -W ..). So what exactly are the aMule install trying to do here? Ok, that was only one question. :-) -- Regards, Torfinn Ingolfsen, Norway From QAT at FreeBSD.org Mon Dec 29 22:27:11 2008 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Mon Dec 29 22:27:18 2008 Subject: cvs commit: ports/www/rt32 Makefile ports/www/rt34 Makefile ports/www/rt36 Makefile ports/www/rt38 Makefile In-Reply-To: <200812292219.mBTMJ7He050824@repoman.freebsd.org> References: In-Reply-To: <200812292219.mBTMJ7He050824@repoman.freebsd.org> Message-ID: <20081229222709.2067D12E4450@quark.ds9.tecnik93.com> Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/rt-3.8.1_2.log : building rt-3.8.1_2 in directory /var/tinderbox/7-STABLE-FTP maintained by: ports@FreeBSD.org building for: 7.1-PRERELEASE amd64 port directory: /usr/ports/www/rt38 Makefile ident: $FreeBSD: ports/www/rt38/Makefile,v 1.4 2008/12/29 22:19:07 pgollucci Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Mon Dec 29 22:25:25 UTC 2008 ................................................... usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Text/Iconv/Iconv.bs changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Text/Iconv/Iconv.so changed permissions expected 0555 found 0755 usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Text/Iconv/autosplit.ix changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Time/HiRes/HiRes.bs changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Time/HiRes/HiRes.so changed permissions expected 0555 found 0755 usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Want/Want.bs changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Want/Want.so changed permissions expected 0555 found 0755 usr/local/lib/perl5/site_perl/5.8.8/mach/auto/XML/Parser/Expat/Expat.bs changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/mach/auto/XML/Parser/Expat/Expat.so changed permissions expected 0555 found 0755 usr/local/lib/perl5/site_perl/5.8.8/mach/auto/version/vxs/vxs.bs changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/mach/auto/version/vxs/vxs.so changed permissions expected 0555 found 0755 usr/local/lib/perl5/site_perl/5.8.8/mach/dbixs_rev.pl changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/mach/encoding.pm changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/mach/mod_perl2.pm changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/mach/qd.pl changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/mach/version/vxs.pm changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/mach/version.pm changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/mach/version.pod changed permissions expected 0444 found 0644 usr/local/lib/perl5/site_perl/5.8.8/newgetopt.pl changed permissions expected 0444 found 0644 ================================================================ build of /usr/ports/www/rt38 ended at Mon Dec 29 22:27:07 UTC 2008 A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From QAT at FreeBSD.org Mon Dec 29 22:38:51 2008 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Mon Dec 29 22:39:18 2008 Subject: cvs commit: ports/japanese/chasen Makefile ports/japanese/chasen-base Makefile distinfo pkg-plist ports/japanese/chasen-base/files patch-dartsdic.cpp In-Reply-To: <200812292235.mBTMZrRN052268@repoman.freebsd.org> References: In-Reply-To: <200812292235.mBTMZrRN052268@repoman.freebsd.org> Message-ID: <20081229223849.01E8212E4450@quark.ds9.tecnik93.com> Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/ja-chasen-2.4.4.log : building ja-chasen-2.4.4 in directory /var/tinderbox/7-STABLE-FTP maintained by: ports@FreeBSD.org building for: 7.1-PRERELEASE amd64 port directory: /usr/ports/japanese/chasen Makefile ident: $FreeBSD: ports/japanese/chasen/Makefile,v 1.25 2008/12/29 22:35:53 amdmi3 Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Mon Dec 29 22:38:45 UTC 2008 ................................................... building ja-chasen-2.4.4 in directory /var/tinderbox/7-STABLE-FTP maintained by: ports@FreeBSD.org building for: 7.1-PRERELEASE amd64 port directory: /usr/ports/japanese/chasen Makefile ident: $FreeBSD: ports/japanese/chasen/Makefile,v 1.25 2008/12/29 22:35:53 amdmi3 Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Mon Dec 29 22:38:45 UTC 2008 FETCH_DEPENDS= PATCH_DEPENDS= EXTRACT_DEPENDS= BUILD_DEPENDS= RUN_DEPENDS=libiconv-1.11_1.tbz ja-chasen-base-2.4.4.tbz ja-ipadic-2.7.0.tbz add_pkg ================================================================ ======================================== ================================================================ ======================================== add_pkg ===> Extracting for ja-chasen-2.4.4 ================================================================ ======================================== add_pkg ===> Patching for ja-chasen-2.4.4 ================================================================ ======================================== add_pkg ===> Configuring for ja-chasen-2.4.4 ================================================================ ======================================== make: don't know how to make regression-test(continuing) ================================================================ ======================================== add_pkg libiconv-1.11_1.tbz ja-chasen-base-2.4.4.tbz ja-ipadic-2.7.0.tbz adding dependencies pkg_add libiconv-1.11_1.tbz pkg_add ja-chasen-base-2.4.4.tbz pkg_add ja-ipadic-2.7.0.tbz pkg_add: can't stat package file 'ja-ipadic-2.7.0.tbz' error in dependency ja-ipadic-2.7.0.tbz, exiting A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From tingox at gmail.com Mon Dec 29 23:04:06 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Mon Dec 29 23:04:14 2008 Subject: aMule 22.3 porting - some questions In-Reply-To: References: Message-ID: Another question: how do I create a diff that removes one of the files in amule2/files? I tried diff -u amule2.org/files/patch-amuleDlg.cpp /dev/null >> amule2.diff And the diff looks ok: --- amule2.org/files/patch-amuleDlg.cpp 2006-01-04 06:59:25.000000000 +0100 +++ /dev/null 2008-12-29 23:22:00.000000000 +0100 @@ -1,24 +0,0 @@ ---- src/amuleDlg.cpp.orig Sun Jan 1 06:17:25 2006 -+++ src/amuleDlg.cpp Tue Jan 3 19:12:04 2006 -@@ -413,9 +413,9 @@ - { - wxString msg = wxT(" "); - #ifdef CLIENT_GUI -- msg << _("aMule remote control ") << wxT(VERSION); -+ msg << _("aMule remote control ") << wxT(VERSION) << wxT(" for FreeBSD"); - #else -- msg << wxT("aMule ") << wxT(VERSION); -+ msg << wxT("aMule ") << wxT(VERSION) << wxT(" for FreeBSD"); - #endif - msg << wxT(" "); - #ifdef CVSDATE -@@ -425,7 +425,8 @@ - " 'All-Platform' p2p client based on eMule \n\n" - " Website: http://www.amule.org \n" - " Forum: http://forum.amule.org \n" -- " FAQ: http://wiki.amule.org \n\n" -+ " FAQ: http://wiki.amule.org \n" -+ " FreeBSD port: http://contribs.martymac.com \n\n" - " Contact: admin@amule.org (administrative issues) \n" - " Copyright (C) 2003-2006 aMule Team \n\n" - " Part of aMule is based on \n" But when I try to apply it, patch rejects it. -- Regards, Torfinn Ingolfsen From varga.michal at gmail.com Mon Dec 29 23:24:44 2008 From: varga.michal at gmail.com (Michal Varga) Date: Mon Dec 29 23:24:50 2008 Subject: linux-enemyterritory In-Reply-To: <4958C3EA.20606@gmail.com> References: <200812230033.43040.g.martinez@pcbsd.es> <7d6fde3d0812221648k6d99d0acsa0d13c96193f8417@mail.gmail.com> <3f1fd1ea0812230938q6187ed1am26b33499f07bc295@mail.gmail.com> <4958C3EA.20606@gmail.com> Message-ID: <3f1fd1ea0812291524i5b4abf42sbf845f46834d49f2@mail.gmail.com> On Mon, Dec 29, 2008 at 1:34 PM, Ricardo Jesus wrote: > No need for a patch. It's simply a matter of sysctl. > > Take a look here: > http://linux-bsd-sharing.blogspot.com/2008/12/tip-enable-sound-on-enemy-territory.html > Interesting, so it actually got fixed at around the same time. My apologies for not checking first, I was assuming that the problem is still there simply based on the error message in the original post. (by the way, the linked tip is missing a 'sysctl' command in step 2) m. From tingox at gmail.com Mon Dec 29 23:39:52 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Mon Dec 29 23:39:59 2008 Subject: amule 2.2.3 port - first try Message-ID: Hello, I am updating the amule2 port to version 2.2.3, this is the first try. The patch is attached. There is (at least) one problem with the patch: it doesn't remove the file ./files/patch-amuleDlg.cpp. For now, just remove the file manually. Doesn't FreeBSDs diff have an option to remove files? I read the ma page but didn't find anything that looked useful. Testing: I have tested this patch on FreeBSD 7.1-prerelease / amd64, and the amule 2.2.3 port compiles and installs fine. It would be nice if others coyld test the patch as well. Feedback is welcome. -- Regards, Torfinn Ingolfsen -------------- next part -------------- A non-text attachment was scrubbed... Name: amule2-2.2.3.diff Type: text/x-diff Size: 4454 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081229/30985c12/amule2-2.2.3.bin From stanb at panix.com Tue Dec 30 00:30:54 2008 From: stanb at panix.com (stan) Date: Tue Dec 30 00:31:00 2008 Subject: Which ISC dhcp server to install? Message-ID: <20081230003053.GA31813@teddy.fas.com> Which ISC DHCP serverr port should I install? The 2 that I tried are both marked as broken. -- One of the main causes of the fall of the roman empire was that, lacking zero, they had no way to indicate successful termination of their C programs. From spawk at acm.poly.edu Tue Dec 30 00:52:22 2008 From: spawk at acm.poly.edu (Boris Kochergin) Date: Tue Dec 30 00:52:28 2008 Subject: Which ISC dhcp server to install? In-Reply-To: <20081230003053.GA31813@teddy.fas.com> References: <20081230003053.GA31813@teddy.fas.com> Message-ID: <495970A0.1050006@acm.poly.edu> stan wrote: > Which ISC DHCP serverr port should I install? The 2 that I tried are both > marked as broken. > > I have multiple installations of net/isc-dhcp30-server and find them all to work fine. Needless to say, it's not marked as broken. -Boris From eitanadlerlist at gmail.com Tue Dec 30 00:56:20 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Tue Dec 30 00:56:27 2008 Subject: Which ISC dhcp server to install? In-Reply-To: <495970A0.1050006@acm.poly.edu> References: <20081230003053.GA31813@teddy.fas.com> <495970A0.1050006@acm.poly.edu> Message-ID: <4959719B.1010400@gmail.com> Boris Kochergin wrote: > stan wrote: >> Which ISC DHCP serverr port should I install? The 2 that I tried are both >> marked as broken. Update ports, run make config, ensure that you have one and only one openSSL version selected, try again. -- Eitan Adler "Security is increased by designing for the way humans actually behave." -Jakob Nielsen From spawk at acm.poly.edu Tue Dec 30 01:19:59 2008 From: spawk at acm.poly.edu (Boris Kochergin) Date: Tue Dec 30 01:20:06 2008 Subject: Which ISC dhcp server to install? In-Reply-To: <4959719B.1010400@gmail.com> References: <20081230003053.GA31813@teddy.fas.com> <495970A0.1050006@acm.poly.edu> <4959719B.1010400@gmail.com> Message-ID: <49597718.8060702@acm.poly.edu> Eitan Adler wrote: > Boris Kochergin wrote: > >> stan wrote: >> >>> Which ISC DHCP serverr port should I install? The 2 that I tried are both >>> marked as broken. >>> > Update ports, run make config, ensure that you have one and only one > openSSL version selected, try again. > > > He probably means the "BROKEN=..." lines in the Makefiles of the net/isc-dhcp31-server and net/isc-dhcp40-server ports. -Boris From tingox at gmail.com Tue Dec 30 01:48:22 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Tue Dec 30 01:48:29 2008 Subject: amule 2.2.3 port - first try In-Reply-To: References: Message-ID: Small update. On Tue, Dec 30, 2008 at 12:39 AM, Torfinn Ingolfsen wrote: > Testing: I have tested this patch on FreeBSD 7.1-prerelease / amd64, > and the amule 2.2.3 port compiles and installs fine. FWIW, It also compiled, installed and is currently running on FreeBSD 6.4-stable / amd64. -- Regards, Torfinn Ingolfsen From QAT at FreeBSD.org Tue Dec 30 01:54:11 2008 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Tue Dec 30 01:54:18 2008 Subject: cvs commit: ports/shells/zoidberg Makefile pkg-plist In-Reply-To: <200812300152.mBU1qVRg095108@repoman.freebsd.org> References: In-Reply-To: <200812300152.mBU1qVRg095108@repoman.freebsd.org> Message-ID: <20081230015408.619A812E4450@quark.ds9.tecnik93.com> Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/zoidberg-0.96_1.log : building zoidberg-0.96_1 in directory /var/tinderbox/7-STABLE-FTP maintained by: ports@FreeBSD.org building for: 7.1-PRERELEASE amd64 port directory: /usr/ports/shells/zoidberg Makefile ident: $FreeBSD: ports/shells/zoidberg/Makefile,v 1.7 2008/12/30 01:52:30 beech Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Tue Dec 30 01:53:23 UTC 2008 ................................................... Installing /usr/local/etc/zoidberg/pixmaps/zoid32.png Installing /usr/local/etc/zoidberg/pixmaps/zoid64.png Installing /usr/local/etc/zoidberg/pixmaps/zoid70.png Installing /usr/local/etc/zoidberg/plugins/Commands.pl Installing /usr/local/etc/zoidberg/plugins/CPAN.pm Installing /usr/local/etc/zoidberg/plugins/Intel.pl Installing /usr/local/etc/zoidberg/plugins/Log.pl Installing /usr/local/etc/zoidberg/plugins/ReadLine.pl ===> Compressing manual pages for zoidberg-0.96_1 ===> Registering installation for zoidberg-0.96_1 ================================================================ ======================================== ===> Building package for zoidberg-0.96_1 Creating package /tmp/packages/All/zoidberg-0.96_1.tbz Registering depends: p5-Env-PS1-0.05 p5-Exporter-Tidy-0.07 p5-Term-ReadLine-Zoid-0.07 p5-Module-Build-0.30 p5-ExtUtils-ParseXS-2.19 p5-ExtUtils-CBuilder-0.24 p5-YAML-0.66 p5-Test-Base-0.54_1 p5-Spiffy-0.30 p5-Term-ReadKey-2.30 perl-5.8.8_1. Creating bzip'd tar ball in '/tmp/packages/All/zoidberg-0.96_1.tbz' Deleting zoidberg-0.96_1 pkg_delete: unable to completely remove directory '/usr/local/lib/perl5/site_perl/5.8.8/auto' pkg_delete: unable to completely remove directory '/usr/local/lib/perl5/site_perl/5.8.8' pkg_delete: unable to completely remove directory '/usr/local/lib/perl5/site_perl' pkg_delete: unable to completely remove directory '/usr/local/lib/perl5/5.8.8/man/man3' pkg_delete: unable to completely remove directory '/usr/local/lib/perl5/5.8.8/man' pkg_delete: unable to completely remove directory '/usr/local/lib/perl5/5.8.8' pkg_delete: unable to completely remove directory '/usr/local/lib/perl5' pkg_delete: couldn't entirely delete package (perhaps the packing list is incorrectly specified?) ================================================================ === Checking filesystem state list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) 15215031 4 drwxr-xr-x 3 root wheel 512 Dec 30 01:54 usr/local/share/doc/zoidberg 15215204 56 -r--r--r-- 1 root wheel 27390 Dec 30 01:54 usr/local/share/doc/zoidberg/Changes 15215205 8 -r--r--r-- 1 root wheel 3233 Dec 30 01:54 usr/local/share/doc/zoidberg/README 15215206 4 -r--r--r-- 1 root wheel 1721 Dec 30 01:54 usr/local/share/doc/zoidberg/index.html 15215207 4 drwxr-xr-x 2 root wheel 512 Dec 30 01:54 usr/local/share/doc/zoidberg/examples 15215208 8 -r--r--r-- 1 root wheel 2761 Dec 30 01:54 usr/local/share/doc/zoidberg/examples/cpan.pl 15215209 8 -r--r--r-- 1 root wheel 3033 Dec 30 01:54 usr/local/share/doc/zoidberg/examples/Menu.pl 15215210 4 -r--r--r-- 1 root wheel 1389 Dec 30 01:54 usr/local/share/doc/zoidberg/examples/word_expansion.pl ================================================================ build of /usr/ports/shells/zoidberg ended at Tue Dec 30 01:54:06 UTC 2008 A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From QAT at FreeBSD.org Tue Dec 30 02:18:05 2008 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Tue Dec 30 02:18:21 2008 Subject: cvs commit: ports/shells/zoidberg Makefile pkg-plist ports/shells/zoidberg/files extra-patch-MANIFEST In-Reply-To: <200812300215.mBU2FwgF097860@repoman.freebsd.org> References: In-Reply-To: <200812300215.mBU2FwgF097860@repoman.freebsd.org> Message-ID: <20081230021802.83E3212E4450@quark.ds9.tecnik93.com> Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/zoidberg-0.96_2.log : building zoidberg-0.96_2 in directory /var/tinderbox/7-STABLE-FTP maintained by: ports@FreeBSD.org building for: 7.1-PRERELEASE amd64 port directory: /usr/ports/shells/zoidberg Makefile ident: $FreeBSD: ports/shells/zoidberg/Makefile,v 1.8 2008/12/30 02:15:57 beech Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Tue Dec 30 02:17:16 UTC 2008 ................................................... Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::Shell.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::Utils::Output.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::Contractor.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::DispatchTable.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::PluginHash.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::Utils::FileSystem.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::Utils.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::Utils::GetOpt.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::StringParser.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Bundle::Zoidberg.3 Installing /usr/local/bin/zoid Installing /usr/local/etc/zoidberg/AppInfo.xml Installing /usr/local/etc/zoidberg/pixmaps/zoid16.png Installing /usr/local/etc/zoidberg/pixmaps/zoid32.png Installing /usr/local/etc/zoidberg/pixmaps/zoid64.png Installing /usr/local/etc/zoidberg/pixmaps/zoid70.png Installing /usr/local/etc/zoidberg/plugins/Commands.pl Installing /usr/local/etc/zoidberg/plugins/CPAN.pm Installing /usr/local/etc/zoidberg/plugins/Intel.pl Installing /usr/local/etc/zoidberg/plugins/Log.pl Installing /usr/local/etc/zoidberg/plugins/ReadLine.pl ===> Compressing manual pages for zoidberg-0.96_2 ===> Registering installation for zoidberg-0.96_2 ================================================================ ======================================== ===> Building package for zoidberg-0.96_2 Creating package /tmp/packages/All/zoidberg-0.96_2.tbz Registering depends: p5-Env-PS1-0.05 p5-Exporter-Tidy-0.07 p5-Term-ReadLine-Zoid-0.07 p5-Module-Build-0.30 p5-ExtUtils-ParseXS-2.19 p5-ExtUtils-CBuilder-0.24 p5-YAML-0.66 p5-Test-Base-0.54_1 p5-Spiffy-0.30 p5-Term-ReadKey-2.30 perl-5.8.8_1. Creating bzip'd tar ball in '/tmp/packages/All/zoidberg-0.96_2.tbz' Deleting zoidberg-0.96_2 ================================================================ === Checking filesystem state list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) 15217325 4 drwxr-xr-x 2 root wheel 512 Dec 30 02:17 usr/local/share/doc/zoidberg 15217358 56 -r--r--r-- 1 root wheel 27390 Dec 30 02:17 usr/local/share/doc/zoidberg/Changes 15217359 8 -r--r--r-- 1 root wheel 3233 Dec 30 02:17 usr/local/share/doc/zoidberg/README ================================================================ build of /usr/ports/shells/zoidberg ended at Tue Dec 30 02:18:01 UTC 2008 A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From jeffrey at goldmark.org Tue Dec 30 05:45:53 2008 From: jeffrey at goldmark.org (Jeffrey Goldberg) Date: Tue Dec 30 05:46:04 2008 Subject: Which ISC dhcp server to install? In-Reply-To: <20081230003053.GA31813@teddy.fas.com> References: <20081230003053.GA31813@teddy.fas.com> Message-ID: <649ADBCB-0349-45FD-9330-8AC59B3E6A2A@goldmark.org> On Dec 29, 2008, at 6:30 PM, stan wrote: > Which ISC DHCP serverr port should I install? The 2 that I tried are > both > marked as broken. I've been using isc-dhcp30-server without difficulty. It is not marked as broken in my instance of it. -j From QAT at FreeBSD.org Tue Dec 30 06:12:28 2008 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Tue Dec 30 06:12:45 2008 Subject: cvs commit: ports/shells/zoidberg Makefile pkg-plist ports/shells/zoidberg/files extra-patch-MANIFEST In-Reply-To: <200812300609.mBU69wfH032683@repoman.freebsd.org> References: In-Reply-To: <200812300609.mBU69wfH032683@repoman.freebsd.org> Message-ID: <20081230061225.4F90F12E4450@quark.ds9.tecnik93.com> Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/zoidberg-0.96_3.log : building zoidberg-0.96_3 in directory /var/tinderbox/7-STABLE-FTP maintained by: ports@FreeBSD.org building for: 7.1-PRERELEASE amd64 port directory: /usr/ports/shells/zoidberg Makefile ident: $FreeBSD: ports/shells/zoidberg/Makefile,v 1.9 2008/12/30 06:09:57 beech Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Tue Dec 30 06:11:40 UTC 2008 ................................................... Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::Shell.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::Utils::Output.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::Contractor.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::DispatchTable.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::PluginHash.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::Utils::FileSystem.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::Utils.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::Utils::GetOpt.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Zoidberg::StringParser.3 Installing /usr/local/lib/perl5/5.8.8/man/man3/Bundle::Zoidberg.3 Installing /usr/local/bin/zoid Installing /usr/local/etc/zoidberg/AppInfo.xml Installing /usr/local/etc/zoidberg/pixmaps/zoid16.png Installing /usr/local/etc/zoidberg/pixmaps/zoid32.png Installing /usr/local/etc/zoidberg/pixmaps/zoid64.png Installing /usr/local/etc/zoidberg/pixmaps/zoid70.png Installing /usr/local/etc/zoidberg/plugins/Commands.pl Installing /usr/local/etc/zoidberg/plugins/CPAN.pm Installing /usr/local/etc/zoidberg/plugins/Intel.pl Installing /usr/local/etc/zoidberg/plugins/Log.pl Installing /usr/local/etc/zoidberg/plugins/ReadLine.pl echo "share/doc/zoidberg/README" >> /work/a/ports/shells/zoidberg/work/.PLIST.mktmp echo "share/doc/zoidberg/Changes" >> /work/a/ports/shells/zoidberg/work/.PLIST.mktmp ===> Compressing manual pages for zoidberg-0.96_3 ===> Registering installation for zoidberg-0.96_3 ================================================================ ======================================== ===> Building package for zoidberg-0.96_3 Creating package /tmp/packages/All/zoidberg-0.96_3.tbz Registering depends: p5-Env-PS1-0.05 p5-Exporter-Tidy-0.07 p5-Term-ReadLine-Zoid-0.07 p5-Module-Build-0.30 p5-ExtUtils-ParseXS-2.19 p5-ExtUtils-CBuilder-0.24 p5-YAML-0.66 p5-Test-Base-0.54_1 p5-Spiffy-0.30 p5-Term-ReadKey-2.30 perl-5.8.8_1. Creating bzip'd tar ball in '/tmp/packages/All/zoidberg-0.96_3.tbz' Deleting zoidberg-0.96_3 ================================================================ === Checking filesystem state list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) 15192420 4 drwxr-xr-x 2 root wheel 512 Dec 30 06:12 usr/local/share/doc/zoidberg ================================================================ build of /usr/ports/shells/zoidberg ended at Tue Dec 30 06:12:23 UTC 2008 A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From decke at bluelife.at Tue Dec 30 12:30:08 2008 From: decke at bluelife.at (Bernhard Froehlich) Date: Tue Dec 30 12:30:15 2008 Subject: amule 2.2.3 port - first try References: Message-ID: Torfinn Ingolfsen gmail.com> writes: > > Hello, > I am updating the amule2 port to version 2.2.3, this is the first try. > The patch is attached. > There is (at least) one problem with the patch: it doesn't remove the > file ./files/patch-amuleDlg.cpp. For now, just remove the file > manually. > Doesn't FreeBSDs diff have an option to remove files? I read the ma > page but didn't find anything that looked useful. > > Testing: I have tested this patch on FreeBSD 7.1-prerelease / amd64, > and the amule 2.2.3 port compiles and installs fine. > > It would be nice if others coyld test the patch as well. > Feedback is welcome. Looks like you are in the wrong folder. Patches are relative to the WRKSRC directory. (work/aMule-2.2.3 or something like that) So recreate the patch from within that directory and it should work. I've had a quick look over your patch and it seems to miss a few files. Have a look at ports-mgmt/porttools which is your swiss army knife as a porting guy. Sorry but i haven't found an english tutorial for it but i think a german one is also worth a look: http://www.chruetertee.ch/blog/archive/2008/05/03/freebsd-ports-mit-hilfe-von-porttools-erstellen-oder-aktualisieren.html -- Bernhard Froehlich http://www.bluelife.at/ From QAT at FreeBSD.org Tue Dec 30 13:02:41 2008 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Tue Dec 30 13:02:50 2008 Subject: cvs commit: ports/lang/p5-F77 Makefile distinfo In-Reply-To: <200812301300.mBUD0xHd096405@repoman.freebsd.org> References: In-Reply-To: <200812301300.mBUD0xHd096405@repoman.freebsd.org> Message-ID: <20081230130236.2594F12E4477@quark.ds9.tecnik93.com> Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/p5-ExtUtils-F77-1.16.log : building p5-ExtUtils-F77-1.16 in directory /var/tinderbox/7-STABLE-FTP maintained by: ports@FreeBSD.org building for: 7.1-PRERELEASE amd64 port directory: /usr/ports/lang/p5-F77 Makefile ident: $FreeBSD: ports/lang/p5-F77/Makefile,v 1.15 2008/12/30 13:00:59 araujo Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Tue Dec 30 13:01:55 UTC 2008 ................................................... Writing Makefile for ExtUtils::F77 ===> Building for p5-ExtUtils-F77-1.16 cp F77.pm blib/lib/ExtUtils/F77.pm cp ._F77.pm blib/lib/ExtUtils/._F77.pm Manifying blib/man3/ExtUtils::F77.3 ================================================================ ======================================== make: don't know how to make regression-test(continuing) ================================================================ ======================================== add_pkg perl-5.8.8_1.tbz adding dependencies pkg_add perl-5.8.8_1.tbz skipping perl-5.8.8_1, already added ===> Installing for p5-ExtUtils-F77-1.16 ===> p5-ExtUtils-F77-1.16 depends on file: /usr/local/bin/perl5.8.8 - found ===> Generating temporary packing list ===> Checking if lang/p5-F77 already installed Manifying blib/man3/ExtUtils::F77.3 Installing /usr/local/lib/perl5/site_perl/5.8.8/ExtUtils/F77.pm Installing /usr/local/lib/perl5/site_perl/5.8.8/ExtUtils/._F77.pm Installing /usr/local/lib/perl5/5.8.8/man/man3/ExtUtils::F77.3 Writing /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/ExtUtils/F77/.packlist ===> Compressing manual pages for p5-ExtUtils-F77-1.16 ===> Registering installation for p5-ExtUtils-F77-1.16 ================================================================ ======================================== ===> Building package for p5-ExtUtils-F77-1.16 Creating package /tmp/packages/All/p5-ExtUtils-F77-1.16.tbz Registering depends: perl-5.8.8_1. Creating bzip'd tar ball in '/tmp/packages/All/p5-ExtUtils-F77-1.16.tbz' Deleting p5-ExtUtils-F77-1.16 ================================================================ === Checking filesystem state list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) 15238387 4 drwxr-xr-x 2 root wheel 512 Dec 30 13:02 usr/local/lib/perl5/site_perl/5.8.8/ExtUtils 15238389 4 -r--r--r-- 1 root wheel 82 Apr 2 2007 usr/local/lib/perl5/site_perl/5.8.8/ExtUtils/._F77.pm ================================================================ build of /usr/ports/lang/p5-F77 ended at Tue Dec 30 13:02:34 UTC 2008 A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From dominique.goncalves at gmail.com Tue Dec 30 14:08:47 2008 From: dominique.goncalves at gmail.com (Dominique Goncalves) Date: Tue Dec 30 14:08:53 2008 Subject: minimal FreeSBIE bombs out In-Reply-To: <49583F15.4020100@gmail.com> References: <495829E5.5010109@gmail.com> <28283d910812281818p523d09f5wd2062fed32154fc4@mail.gmail.com> <49583F15.4020100@gmail.com> Message-ID: <7daacbbe0812300536n6d1e0585w77645c06c0848832@mail.gmail.com> Hi, On Mon, Dec 29, 2008 at 4:08 AM, Sevan / Venture37 wrote: > matt donovan wrote: >> >> does your normal buildworld bomb out? I tend to do a make buildworld >> outside of freesbie then just put NO_BUILDWORLD in my freesbie.conf. > > I don't have any problems running make buildworld when doing system > upgrades. I've copied the make.conf.minimal which is bundled with freesbie > to /etc/make.conf & rerun make buildworld by hand, same thing happend, it > bombed out. I don't have a solution only a workaround, comment NO_CXX=YES and NO_TOOLCHAIN=YES. It seems using these variables are broken (tested with 7.1-RC) BTW, you should use src.conf(5), freesbie2 supports this file. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > Regards. -- There's this old saying: "Give a man a fish, feed him for a day. Teach a man to fish, feed him for life." From amdmi3 at amdmi3.ru Tue Dec 30 17:44:30 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Tue Dec 30 17:44:38 2008 Subject: aMule 22.3 porting - some questions In-Reply-To: References: Message-ID: <20081230174454.GB81218@hades.panopticon> * Torfinn Ingolfsen (tingox@gmail.com) wrote: > Ok, I have passed the first milestone or two - the aMule 2.2.3 port > now compiles and installs. > During the install step I see this: > if test "amule" = "gettext" \ > && test '' = 'intl-compat.o'; then \ > /bin/sh `case "./mkinstalldirs" in /*) echo "./mkinstalldirs" ;; *) > echo ".././mkinstalldirs" ;; esac` /usr/local/lib /usr/local/include; > \ > install -o root -g wheel -m 444 libintl.h /usr/local/include/libintl.h; \ > @LIBTOOL@ --mode=install \ > install -o root -g wheel -m 444 libintl.a /usr/local/lib/libintl.a; \ > else \ > : ; \ > fi > These files are installed by gettext (verified with pkg_info -W ..). > So what exactly are the aMule install trying to do here? > > Ok, that was only one question. :-) Seems like gettext and all gettext consumers use the same set of autotools macros, but gettext itself should be processed differently by them. Thus the `if'. Since "amule" = "gettext" evaluates to false, this code does nothing, it just gets echoed my gmake. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From amdmi3 at amdmi3.ru Tue Dec 30 17:55:05 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Tue Dec 30 17:55:12 2008 Subject: aMule 22.3 porting - some questions In-Reply-To: References: Message-ID: <20081230175527.GC81218@hades.panopticon> * Torfinn Ingolfsen (tingox@gmail.com) wrote: > Another question: how do I create a diff that removes one of the files > in amule2/files? > I tried > diff -u amule2.org/files/patch-amuleDlg.cpp /dev/null >> amule2.diff > > And the diff looks ok: > --- amule2.org/files/patch-amuleDlg.cpp 2006-01-04 06:59:25.000000000 +0100 > +++ /dev/null 2008-12-29 23:22:00.000000000 +0100 Obviously this way diff will have no idea on what file to delete, as amule2.org/files/patch-amuleDlg.cpp path does not exist. This way it should work: --- amule2/files/patch-amuleDlg.cpp 2006-01-04 06:59:25.000000000 +0100 +++ /dev/null 2008-12-29 23:22:00.000000000 +0100 or this way: --- amule2.orig/files/patch-amuleDlg.cpp 2006-01-04 06:59:25.000000000 +0100 +++ amule2/files/patch-amuleDlg.cpp 2008-12-29 23:22:00.000000000 +0100 (only '-' lines follow, `patch` will remove resulting empty file) But I assume what you need is -r option for diff - it compares 2 directories recursively, processing all changes as well as new and removed files correctly. % diff -ruN /usr/ports/net-p2p/amule amule where amule is your modified port. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From tingox at gmail.com Tue Dec 30 18:04:31 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Tue Dec 30 18:04:38 2008 Subject: amule 2.2.3 port - first try In-Reply-To: References: Message-ID: Hello, On Tue, Dec 30, 2008 at 11:20 AM, Bernhard Froehlich wrote: > Looks like you are in the wrong folder. Patches are relative to the WRKSRC > directory. (work/aMule-2.2.3 or something like that) So recreate the patch from > within that directory and it should work. I'm not really sure what you are saying here? The patch I provide is fr the port itself (ie the 'amule2' directory in /usr/ports/net-p2p). It is best applied from withing the amule2 directory, uing patch -p1 ... Or did you find some other problem with the patch? If so, it would help if you could be more specific about the error(s). > I've had a quick look over your patch and it seems to miss a few files. Have a Could you be more specific? > look at ports-mgmt/porttools which is your swiss army knife as a porting guy. Thanks, I'll have a look at it. > Sorry but i haven't found an english tutorial for it but i think a german one is > also worth a look: > http://www.chruetertee.ch/blog/archive/2008/05/03/freebsd-ports-mit-hilfe-von-porttools-erstellen-oder-aktualisieren.html Sorry, I can't read german, only english. -- Regards, Torfinn Ingolfsen From yanefbsd at gmail.com Tue Dec 30 18:08:04 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Tue Dec 30 18:08:10 2008 Subject: minimal FreeSBIE bombs out In-Reply-To: <7daacbbe0812300536n6d1e0585w77645c06c0848832@mail.gmail.com> References: <495829E5.5010109@gmail.com> <28283d910812281818p523d09f5wd2062fed32154fc4@mail.gmail.com> <49583F15.4020100@gmail.com> <7daacbbe0812300536n6d1e0585w77645c06c0848832@mail.gmail.com> Message-ID: On Dec 30, 2008, at 5:36, "Dominique Goncalves" wrote: > Hi, > > On Mon, Dec 29, 2008 at 4:08 AM, Sevan / Venture37 > wrote: >> matt donovan wrote: >>> >>> does your normal buildworld bomb out? I tend to do a make buildworld >>> outside of freesbie then just put NO_BUILDWORLD in my freesbie.conf. >> >> I don't have any problems running make buildworld when doing system >> upgrades. I've copied the make.conf.minimal which is bundled with >> freesbie >> to /etc/make.conf & rerun make buildworld by hand, same thing >> happend, it >> bombed out. > > I don't have a solution only a workaround, comment NO_CXX=YES and > NO_TOOLCHAIN=YES. > It seems using these variables are broken (tested with 7.1-RC) > > BTW, you should use src.conf(5), freesbie2 supports this file. >> - Yes one should use src.conf in place of make.conf for src tree controlled knobs in 7+. - NO_* was replaced with WITHOUT_* in 7.x. Cheers, -Garrett From pav at FreeBSD.org Tue Dec 30 18:17:32 2008 From: pav at FreeBSD.org (Pav Lucistnik) Date: Tue Dec 30 18:17:39 2008 Subject: Build problems with amarok In-Reply-To: <83e5fb980812291149u196c822br6953a1077edd9d9d@mail.gmail.com> References: <20081229164749.GA19620@teddy.fas.com> <200812292218.05073.makc@freebsd.org> <83e5fb980812291149u196c822br6953a1077edd9d9d@mail.gmail.com> Message-ID: <1230661042.23930.4.camel@hood.oook.cz> Diego Depaoli p??e v po 29. 12. 2008 v 20:49 +0100: > On Mon, Dec 29, 2008 at 8:18 PM, Max Brazhnikov wrote: > > On Mon, 29 Dec 2008 11:47:49 -0500, stan wrote: > >> I'm building a new machine which I cvsup'd yesterday. I am having trouble > >> getting the amarok port to compile. here is the end of the compile > >> failure: > >> Can anyne sugest how to resolve this? > > amarok was broken with libmtp update to 0.3.1 (ports/126905). Expectation that > > amarok will be updated soon is not right -- amarok2 (which is for KDE 4) will > > be added as separate port. So someone should recreate libmtp-0.2 for amarok. > Put attached patch (taken from gentoo) into amarok/files and rebuild. > It worked for me Added the patch to the port. Thank you! -- Pav Lucistnik Your sig line (k) was stolen! -more- There is a puff of smoke! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081230/447f3dca/attachment.pgp From tingox at gmail.com Tue Dec 30 18:27:48 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Tue Dec 30 18:27:55 2008 Subject: aMule 22.3 porting - some questions In-Reply-To: <20081230175527.GC81218@hades.panopticon> References: <20081230175527.GC81218@hades.panopticon> Message-ID: Hello, On Tue, Dec 30, 2008 at 6:55 PM, Dmitry Marakasov wrote: > But I assume what you need is -r option for diff - it compares 2 > directories recursively, processing all changes as well as new and > removed files correctly. I actually tried with the -r option to diff after sending mail to this list. But it seems like -r on it's own isn't enough, I also need patch with the -E argument. I created the attached patch with diff -ruN ... when I try patch without '-E': root@kg-vm# patch -C -p1 < /home/tingo/work/amule/amule2-3.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |diff -ruN amule2.org/Makefile amule2/Makefile |--- amule2.org/Makefile 2008-08-21 08:18:04.000000000 +0200 |+++ amule2/Makefile 2008-12-29 21:18:08.000000000 +0100 -------------------------- Patching file Makefile using Plan A... Hunk #1 succeeded at 6. Hunk #2 succeeded at 45 (offset 1 line). Hunk #3 succeeded at 121 (offset 1 line). Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff -ruN amule2.org/Makefile.man amule2/Makefile.man |--- amule2.org/Makefile.man 2006-01-04 06:59:25.000000000 +0100 |+++ amule2/Makefile.man 2008-12-29 20:51:00.000000000 +0100 -------------------------- Patching file Makefile.man using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 20. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff -ruN amule2.org/distinfo amule2/distinfo |--- amule2.org/distinfo 2007-01-12 18:18:48.000000000 +0100 |+++ amule2/distinfo 2008-12-29 20:43:48.000000000 +0100 -------------------------- Patching file distinfo using Plan A... Hunk #1 succeeded at 1. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff -ruN amule2.org/files/patch-amuleDlg.cpp amule2/files/patch-amuleDlg.cpp |--- amule2.org/files/patch-amuleDlg.cpp 2006-01-04 06:59:25.000000000 +0100 |+++ amule2/files/patch-amuleDlg.cpp 1970-01-01 01:00:00.000000000 +0100 -------------------------- Patching file files/patch-amuleDlg.cpp using Plan A... Hunk #1 failed at 0. 1 out of 1 hunks failed--saving rejects to files/patch-amuleDlg.cpp.rej Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff -ruN amule2.org/pkg-plist amule2/pkg-plist |--- amule2.org/pkg-plist 2007-10-25 01:36:24.000000000 +0200 |+++ amule2/pkg-plist 2008-12-29 22:24:25.000000000 +0100 -------------------------- Patching file pkg-plist using Plan A... Hunk #1 succeeded at 39. done Looks like it doesn't remove the file. Next try - now with '-E': root@kg-vm# patch -C -Ep1 < /home/tingo/work/amule/amule2-3.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |diff -ruN amule2.org/Makefile amule2/Makefile |--- amule2.org/Makefile 2008-08-21 08:18:04.000000000 +0200 |+++ amule2/Makefile 2008-12-29 21:18:08.000000000 +0100 -------------------------- Patching file Makefile using Plan A... Hunk #1 succeeded at 6. Hunk #2 succeeded at 45 (offset 1 line). Hunk #3 succeeded at 121 (offset 1 line). Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff -ruN amule2.org/Makefile.man amule2/Makefile.man |--- amule2.org/Makefile.man 2006-01-04 06:59:25.000000000 +0100 |+++ amule2/Makefile.man 2008-12-29 20:51:00.000000000 +0100 -------------------------- Patching file Makefile.man using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 20. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff -ruN amule2.org/distinfo amule2/distinfo |--- amule2.org/distinfo 2007-01-12 18:18:48.000000000 +0100 |+++ amule2/distinfo 2008-12-29 20:43:48.000000000 +0100 -------------------------- Patching file distinfo using Plan A... Hunk #1 succeeded at 1. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff -ruN amule2.org/files/patch-amuleDlg.cpp amule2/files/patch-amuleDlg.cpp |--- amule2.org/files/patch-amuleDlg.cpp 2006-01-04 06:59:25.000000000 +0100 |+++ amule2/files/patch-amuleDlg.cpp 1970-01-01 01:00:00.000000000 +0100 -------------------------- Patching file files/patch-amuleDlg.cpp using Plan A... Hunk #1 failed at 0. Removing files/patch-amuleDlg.cpp (empty after patching). 1 out of 1 hunks failed--saving rejects to files/patch-amuleDlg.cpp.rej Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff -ruN amule2.org/pkg-plist amule2/pkg-plist |--- amule2.org/pkg-plist 2007-10-25 01:36:24.000000000 +0200 |+++ amule2/pkg-plist 2008-12-29 22:24:25.000000000 +0100 -------------------------- Patching file pkg-plist using Plan A... Hunk #1 succeeded at 39. done It stills says "hunk failed" but now it removes the empty file. So this is good then? Thanks for your feedback, helpful as always. -- Regards, Torfinn Ingolfsen -------------- next part -------------- A non-text attachment was scrubbed... Name: amule2-3.diff Type: text/x-diff Size: 5545 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20081230/5669ba64/amule2-3.bin From amdmi3 at amdmi3.ru Tue Dec 30 18:33:02 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Tue Dec 30 18:33:09 2008 Subject: amule 2.2.3 port - first try In-Reply-To: References: Message-ID: <20081230183321.GD81218@hades.panopticon> * Torfinn Ingolfsen (tingox@gmail.com) wrote: Something tells me that he meant to answer your previous message about a patch that removes a file. I thought you're trying to make a patch-* for ports's files/ too, before I understood that you're trying to make a patch to a port itself. This patch looks good at a first glance, I've scheduled it to be build in a tinderbox. Btw, I'll second porttools advice, it really does much work for you, such as patch creation and partially filling send-pr form. Also look at portlint - it inspects a port and porints you at some common errors. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From amdmi3 at amdmi3.ru Tue Dec 30 18:39:14 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Tue Dec 30 18:39:21 2008 Subject: aMule 22.3 porting - some questions In-Reply-To: References: <20081230175527.GC81218@hades.panopticon> Message-ID: <20081230183939.GE81218@hades.panopticon> * Torfinn Ingolfsen (tingox@gmail.com) wrote: > It stills says "hunk failed" but now it removes the empty file. > So this is good then? The patch you attached applies without any problems. `patch -E`: -------------------------- |diff -ruN amule2.org/files/patch-amuleDlg.cpp amule2/files/patch-amuleDlg.cpp |--- amule2.org/files/patch-amuleDlg.cpp 2006-01-04 06:59:25.000000000 +0100 |+++ amule2/files/patch-amuleDlg.cpp 1970-01-01 01:00:00.000000000 +0100 -------------------------- Patching file amule2/files/patch-amuleDlg.cpp using Plan A... Hunk #1 succeeded at 0. Removing amule2/files/patch-amuleDlg.cpp (empty after patching). ensure that you're testing it on really original amule2 port (I guess that you're not, considering (offset 1 line) messages in the first chunk). -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From decke at bluelife.at Tue Dec 30 18:48:19 2008 From: decke at bluelife.at (Bernhard =?iso-8859-1?Q?Fr=F6hlich?=) Date: Tue Dec 30 18:48:25 2008 Subject: amule 2.2.3 port - first try In-Reply-To: References: Message-ID: On Tue, December 30, 2008 7:04 pm, Torfinn Ingolfsen wrote: > Hello, > > On Tue, Dec 30, 2008 at 11:20 AM, Bernhard Froehlich > wrote: >> Looks like you are in the wrong folder. Patches are relative to the >> WRKSRC >> directory. (work/aMule-2.2.3 or something like that) So recreate the >> patch from >> within that directory and it should work. > > I'm not really sure what you are saying here? The patch I provide is > fr the port itself (ie the 'amule2' directory in /usr/ports/net-p2p). > It is best applied from withing the amule2 directory, uing patch -p1 ... > Or did you find some other problem with the patch? If so, it would > help if you could be more specific about the error(s). > >> I've had a quick look over your patch and it seems to miss a few files. >> Have a > > Could you be more specific? > Sorry that was my fault. I thought you wanted to delete a file from within the aMule sourcecode and not one of the port files. That makes a lot more sense now. -- Bernhard Fr?hlich http://www.bluelife.at/ From tingox at gmail.com Tue Dec 30 18:57:06 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Tue Dec 30 18:57:15 2008 Subject: amule 2.2.3 port - first try In-Reply-To: <20081230183321.GD81218@hades.panopticon> References: <20081230183321.GD81218@hades.panopticon> Message-ID: On Tue, Dec 30, 2008 at 7:33 PM, Dmitry Marakasov wrote: > Something tells me that he meant to answer your previous message > about a patch that removes a file. I thought you're trying to make a > patch-* for ports's files/ too, before I understood that you're trying to > make a patch to a port itself. I see. I'm sorry if I have confused anyone, it wasn't intentional. > This patch looks good at a first glance, I've scheduled it to be build > in a tinderbox. Which reminds me I have to fix my own tinderbox, after the last update it doesn't run anymore. Probably just ome config files that mut be changed. BTW, do I need to run tinderd to mae the web ui work? I can't remember how it worked when it worked. :) > Btw, I'll second porttools advice, it really does much work for you, > such as patch creation and partially filling send-pr form. Sounds great, I will install it next. > Also look at portlint - it inspects a port and porints you at some > common errors. Yes, portlint says: root@kg-v2# portlint amule2 WARN: Makefile: [17]: use tab (not space) to make indentation WARN: Conflict "ed2k-hash-*" specified too broad. You should end it with a version number fragment (-[0-9]*). 0 fatal errors and 2 warnings found. root@kg-v2# portlint -a amule2 WARN: Makefile: [17]: use tab (not space) to make indentation WARN: Conflict "ed2k-hash-*" specified too broad. You should end it with a version number fragment (-[0-9]*). WARN: Makefile: manpage for chapter 1 should be listed in MAN1, even if compression is not necessary. WARN: Makefile: how about using MANLANG for designating manual language, such as "fr"? 0 fatal errors and 4 warnings found. After changing the first two reported problems, portlint now reports this: root@kg-v2# portlint amule2 looks fine. root@kg-v2# portlint -a amule2 WARN: Makefile: manpage for chapter 1 should be listed in MAN1, even if compression is not necessary. WARN: Makefile: how about using MANLANG for designating manual language, such as "fr"? 0 fatal errors and 2 warnings found. I'll work more on the port. -- Regards, Torfinn Ingolfsen From amdmi3 at amdmi3.ru Tue Dec 30 19:06:35 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Tue Dec 30 19:06:42 2008 Subject: amule 2.2.3 port - first try In-Reply-To: References: <20081230183321.GD81218@hades.panopticon> Message-ID: <20081230190658.GF81218@hades.panopticon> * Torfinn Ingolfsen (tingox@gmail.com) wrote: > > This patch looks good at a first glance, I've scheduled it to be build > > in a tinderbox. > > Which reminds me I have to fix my own tinderbox, after the last update > it doesn't run anymore. Probably just ome config files that mut be > changed. > BTW, do I need to run tinderd to mae the web ui work? I can't remember > how it worked when it worked. :) No, web ui just needs a working database. > WARN: Makefile: manpage for chapter 1 should be listed in MAN1, even > if compression is not necessary. > WARN: Makefile: how about using MANLANG for designating manual > language, such as "fr"? Those are likely false positives, as portlint doesn't seem see Makefile.man. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From tingox at gmail.com Tue Dec 30 19:09:28 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Tue Dec 30 19:09:35 2008 Subject: aMule 22.3 porting - some questions In-Reply-To: <20081230183939.GE81218@hades.panopticon> References: <20081230175527.GC81218@hades.panopticon> <20081230183939.GE81218@hades.panopticon> Message-ID: On Tue, Dec 30, 2008 at 7:39 PM, Dmitry Marakasov wrote: > The patch you attached applies without any problems. `patch -E`: Nice! > ensure that you're testing it on really original amule2 port (I guess > that you're not, considering (offset 1 line) messages in the first > chunk). You were correct. Somehow my amule2.org directory had been changed, I checked out a fresh version and now the patch applies without problems. Thanks! -- Regards, Torfinn Ingolfsen From amdmi3 at amdmi3.ru Tue Dec 30 19:24:32 2008 From: amdmi3 at amdmi3.ru (Dmitry Marakasov) Date: Tue Dec 30 19:24:42 2008 Subject: amule 2.2.3 port - first try In-Reply-To: References: Message-ID: <20081230192455.GG81218@hades.panopticon> * Torfinn Ingolfsen (tingox@gmail.com) wrote: It builds OK, but plist (and Makefile.man I guess) is incorrect. http://people.freebsd.org/~amdmi3/aMule-nooptimize-2.2.3.log don't mind -nooptimize, I'm just testing it with different options. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From tingox at gmail.com Tue Dec 30 20:16:53 2008 From: tingox at gmail.com (Torfinn Ingolfsen) Date: Tue Dec 30 20:16:59 2008 Subject: amule 2.2.3 port - first try In-Reply-To: <20081230192455.GG81218@hades.panopticon> References: <20081230192455.GG81218@hades.panopticon> Message-ID: On Tue, Dec 30, 2008 at 8:24 PM, Dmitry Marakasov wrote: > * Torfinn Ingolfsen (tingox@gmail.com) wrote: > > It builds OK, but plist (and Makefile.man I guess) is incorrect. I knew about plist - I haven't done too much updating of that. I need to figure out a manageable way of maintaining it. Some files are added to the install based on what options a user chooses, and thererfore should only e added then. OTOH, there are just too many files add everything dynamically. Oh well, it must be fixed one way or the other. With regards to man pages,aMule ships with man pages for en, de, es, eu, fr and hu. However, the fr set is incomplete, almost half the man pages are missing. A few commands only have man pages in en and de languages. I'm not really sure how to handle this. Also, the man page are installed uncompressed, and it seems like 'make package' doesn't like that. > http://people.freebsd.org/~amdmi3/aMule-nooptimize-2.2.3.log I see that 'port test' also reports much of the same - porttools looks like a _very_ useful tool thanks to both Bernhard and you for pointing me towards it. -- Regards, Torfinn Ingolfsen From QAT at FreeBSD.org Tue Dec 30 23:54:46 2008 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Tue Dec 30 23:54:52 2008 Subject: cvs commit: ports/sysutils/searchmonkey Makefile distinfo In-Reply-To: <200812302347.mBUNlsUC085612@repoman.freebsd.org> References: In-Reply-To: <200812302347.mBUNlsUC085612@repoman.freebsd.org> Message-ID: <20081230235444.0955912E445F@quark.ds9.tecnik93.com> Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/searchmonkey-0.8.1.log : building searchmonkey-0.8.1 in directory /var/tinderbox/7-STABLE-FTP maintained by: ports@FreeBSD.org building for: 7.1-PRERELEASE amd64 port directory: /usr/ports/sysutils/searchmonkey Makefile ident: $FreeBSD: ports/sysutils/searchmonkey/Makefile,v 1.13 2008/12/30 23:47:54 amdmi3 Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Tue Dec 30 23:53:15 UTC 2008 ................................................... installing en_GB.gmo as /usr/local/share/locale/en_GB/LC_MESSAGES/searchmonkey.mo mkdir -p -- /usr/local/share/locale/en_UK/LC_MESSAGES installing en_UK.gmo as /usr/local/share/locale/en_UK/LC_MESSAGES/searchmonkey.mo mkdir -p -- /usr/local/share/locale/en_US/LC_MESSAGES installing en_US.gmo as /usr/local/share/locale/en_US/LC_MESSAGES/searchmonkey.mo if test "searchmonkey" = "glib"; then if test -r ".././mkinstalldirs"; then .././mkinstalldirs /usr/local/share/glib-2.0/gettext/po; else /bin/sh ../mkinstalldirs /usr/local/share/glib-2.0/gettext/po; fi; install -o root -g wheel -m 444 ./Makefile.in.in /usr/local/share/glib-2.0/gettext/po/Makefile.in.in; else : ; fi if test -d ./pixmaps; then /bin/sh ./mkinstalldirs /usr/local/share/pixmaps/searchmonkey; for pixmap in ./pixmaps/*; do if test -f $pixmap; then install -o root -g wheel -m 444 $pixmap /usr/local/share/pixmaps/searchmonkey; fi done; ln -sf /usr/local/share/pixmaps/searchmonkey/searchmonkey-48x48.png /usr/local/share/pixmaps/searchmonkey.png; fi mkdir -p -- /usr/local/share/pixmaps/searchmonkey ===> Registering installation for searchmonkey-0.8.1 ================================================================ ======================================== ===> Building package for searchmonkey-0.8.1 Creating package /tmp/packages/All/searchmonkey-0.8.1.tbz Registering depends: gtk-2.12.11_1 atk-1.22.0_1 pango-1.20.5 shared-mime-info-0.51 gio-fam-backend-2.16.5 gamin-0.1.9_2 glib-2.16.5_1 gettext-0.17_1 libxml2-2.6.32_2 libiconv-1.11_1 cairo-1.6.4_3,1 xcb-util-0.2.1 libxcb-1.1.90.1 libpthread-stubs-0.1 pcre-7.8 pixman-0.10.0_2 xorg-fonts-truetype-7.3 font-misc-ethiopic-1.0.0 font-misc-meltho-1.0.0_1 font-bh-ttf-1.0.0 mkfontdir-1.0.3_1 mkfontscale-1.0.3 libfontenc-1.0.4 libXft-2.1.13 libXrandr-1.2.2_1 libXcursor-1.1.9_1 libXrender-0.9.4_1 libXinerama-1.0.2,1 libXi-1.1.3,1 libXcomposite-0.4.0,1 libXext-1.0.3,1 libXdamage-1.1.1 libXfixes-4.0.3_1 libX11-1.1.3_1,1 libXau-1.0.3_2 libXdmcp-1.0.2_1 xproto-7.0.10_1 bitstream-vera-1.10_4 fontconfig-2.5.0,1 freetype2-2.3.7 pkg-config-0.23_1 tiff-3.8.2_2 jpeg-6b_7 png-1.2.33 perl-5.8.8_1 xcb-proto-1.2 python25-2.5.2_3 hicolor-icon-theme-0.10_2 expat-2.0.1 encodings-1.0.2,1 font-util-1.0.1 compositeproto-0.4 damageproto-1.1.0_2 fixesproto-4.0 inputproto-1.4.2.1 kbproto-1.0.3 randrproto-1.2.1 renderproto-0.9.3 xextproto-7.0.2 xineramaproto-1.1.2. Creating bzip'd tar ball in '/tmp/packages/All/searchmonkey-0.8.1.tbz' Deleting searchmonkey-0.8.1 ================================================================ === Checking filesystem state list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) 15242824 544 -r-xr-xr-x 1 root wheel 245776 Dec 30 23:54 usr/local/bin/searchmonkey 15285836 4 -r--r--r-- 1 root wheel 386 Dec 30 23:54 usr/local/share/locale/en_GB/LC_MESSAGES/searchmonkey.mo 15427025 4 drwxr-xr-x 3 root wheel 512 Dec 30 23:54 usr/local/share/locale/en_UK 15427029 4 drwxr-xr-x 2 root wheel 512 Dec 30 23:54 usr/local/share/locale/en_UK/LC_MESSAGES 15427030 4 -r--r--r-- 1 root wheel 386 Dec 30 23:54 usr/local/share/locale/en_UK/LC_MESSAGES/searchmonkey.mo 15427034 4 drwxr-xr-x 3 root wheel 512 Dec 30 23:54 usr/local/share/locale/en_US 15427035 4 drwxr-xr-x 2 root wheel 512 Dec 30 23:54 usr/local/share/locale/en_US/LC_MESSAGES 15427038 4 -r--r--r-- 1 root wheel 830 Dec 30 23:54 usr/local/share/locale/en_US/L