Strange error and behaviour with sysutils/fusefs-smbnetfs
Hi, On recently updated freebsd 11 machine with samba47 and fusefs-smbnetfs-0.6.1_1 creating files on smb mount is impossible. When I try to create file on the mount receive the following error: cp /var/log/smbnet.log . cp: ./smbnet.log: Input/output error The error message which I receive in debug mode is: 2018-10-08 14:49:42.220 srv(24576)->smb_conn_srv_listen: process query=13, query_len=8 2018-10-08 14:49:42.221 srv(24576)->smb_conn_srv_fstat: errno=22, Invalid argument After this error the file is created with zero size e.g. empty. I can read and delete the file. I found this bug report in ubuntu - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892841 and this patch - https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=892841;filename=0001-fix-opening-a-file-with-O_CREAT-and-reading-created-.patch;msg=10 But unfortunately this workaround leads to another error (e.g. call not implemented). A month ago everything worked fine, so I'm suspecting changing default samba from 46 to 47 (https://reviews.freebsd.org/D16904) as the reason for this. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224205
Hi, Can a port commiter look into this - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224205 ? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Porting Chronograf to FreeBSD
Hi, I've got the port to a working state ( https://github.com/cheffo/FreeBSD-Ports/tree/master/net-mgmt/chronograf) make install/make package works but the issue with "yarm" is still there - this package manager download extra files during the build process. Funny it downloads and install node-sass as dev dependency inside the port dir, while npm from ports core dump and fails. The port is still not polished - the rc.d script for example and you cannot build package using poudriere, but it works ok with make and pkg. I have no idea how to make it work under poudriere at this moment, so if someone can help it will be great. On Fri, Nov 24, 2017 at 1:45 PM, Stefan Lambrev <che...@freebsd-bg.org> wrote: > Hi all, > > I'm trying to port Chronograf to FreeBSD (part of influxdb project). > > My current work is available here - https://github.com/cheffo/ > FreeBSD-Ports/tree/master/net-mgmt/chronograf (port is not polished - I > know) > > But I'm facing few issues which I do not know how to address. > > First issue is the building process which is not very tipical for Go > projects. > Before building it needs "yarn" to fetch additional packages - if someone > can help me get this done on the "fetch" phase of the port build I'll be > very greatful as I'm note very familiar with yarn. > > Basically this is how vendor's build process looks (short version): > > 1) cd ui && yarn --no-progress --no-emoji (fetches external archives - > does not work with poudriere) > 2) yar run build - no idea what this is doing :) > 3) go generate -x `find all .go files` - crazy > 3) go get -u go-bindata - I've put this currently as external build > dependency as it's already ported to FreeBSD, patched Makefile and just > skip this step so it's poudriere compatible > 4) go-bindata .. `find all gen.go files` > 5) go build > > I'm miserably failing on step 1 - tried --offline but no luck, also no > idea how to provide access for yarn to the archive fiels that are download > in dist (they got extracted from by the ports system) > > If there is a port that already solves those issues please point me to it > and I'll find out how to do it, otherwise I'm open to ideas :) > > > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Porting Chronograf to FreeBSD
Hi all, I'm trying to port Chronograf to FreeBSD (part of influxdb project). My current work is available here - https://github.com/cheffo/FreeBSD-Ports/tree/master/net-mgmt/chronograf (port is not polished - I know) But I'm facing few issues which I do not know how to address. First issue is the building process which is not very tipical for Go projects. Before building it needs "yarn" to fetch additional packages - if someone can help me get this done on the "fetch" phase of the port build I'll be very greatful as I'm note very familiar with yarn. Basically this is how vendor's build process looks (short version): 1) cd ui && yarn --no-progress --no-emoji (fetches external archives - does not work with poudriere) 2) yar run build - no idea what this is doing :) 3) go generate -x `find all .go files` - crazy 3) go get -u go-bindata - I've put this currently as external build dependency as it's already ported to FreeBSD, patched Makefile and just skip this step so it's poudriere compatible 4) go-bindata .. `find all gen.go files` 5) go build I'm miserably failing on step 1 - tried --offline but no luck, also no idea how to provide access for yarn to the archive fiels that are download in dist (they got extracted from by the ports system) If there is a port that already solves those issues please point me to it and I'll find out how to do it, otherwise I'm open to ideas :) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: please test sysutlis/apcupsd update
Hi, Ion-Mihai Tetcu wrote: On Tue, 01 Jul 2008 15:19:29 +0300 Stefan Lambrev [EMAIL PROTECTED] wrote: Greetings Ion-Mihai, Ion-Mihai Tetcu wrote: On Tue, 01 Jul 2008 13:38:49 +0300 Stefan Lambrev [EMAIL PROTECTED] wrote: [ .. ] === Patching for apcupsd-3.14.4 === Applying FreeBSD patches for apcupsd-3.14.4 Ignoring previously applied (or reversed) patch. 3 out of 3 hunks ignored--saving rejects to ./src/drivers/usb/bsd/bsd-usb.c.rej = Patch patch-src__drivers__usb__bsd__bsd-usb.c failed to apply cleanly. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.54579.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=apcupsd-3.14.3_1 UPGRADE_PORT_VER=3.14.3_1 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! sysutils/apcupsd (apcupsd-3.14.3_1) (patch error) Can you please send me tar of your port? May be the diff is broken? That file was removed as it was integrated upstream; I did diff -u instead of diff -uN. Thanks for catching this. Try the one attached or just rm the file. Removing the old patch fix the compilation problem. The new version of apcups (usb) works fine with: ugen0: American Power Conversion Back-UPS CS 500 FW:808.q7.I USB FW:q7, class 0/0, rev 1.10/0.06, addr 2 on uhub0 I hope to find time to test and with Smart-UPS 3000 RM (serial) and network too. I just tested and can confirm that new port works fine with APC Smart-UPS 3000 RM I missed -N to cvs diff. The patch is no longer useful since it has been incorporated upstream. I uploaded the good patch: http://t32.tecnik93.com/FreeBSD/ports/apcupsd/port/apcupsd-3.14.3_2-to-3.14.4.diff Thanks, -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: please test sysutlis/apcupsd update
Hi, Sorry I didn't reply earlier. Ion-Mihai Tetcu wrote: Hi, At: http://t32.tecnik93.com/FreeBSD/ports/apcupsd/port/apcupsd-3.14.3_2-to-3.14.4.diff you'll find a diff (also attached to this mail) which updates sysutlis/apcupsd to the latest stable version. cd /usr/ports/sysutils/apcupsd \ fetch http://T32.TecNik93.com/FreeBSD/ports/apcupsd/port/apcupsd-3.14.3_2-to-3.14.4.diff \ patch apcupsd-3.14.3_2-to-3.14.4.diff \ make clean make config make install clean Notable changes are: - it now builds using gmake - NLS and POWERFLUTE are removed - POLLTIME directive to control UPS polling interval. This directive specifies the number of seconds to delay between polling the UPS for status. Previously, NETTIME allowed this to be adjusted for network connections only (snmp, pcnet, nis-net). POLLTIME configures the delay for all connection types. NETTIME is accepted as a synonym for compatibility with old config files. - you can now use the graphical client via GAPCMON OPTION - it won't build on anything pre 6.3R I need to know if it works OK for you, especially the CGI and CAPGCOM. If I don't receive any complains I plan to commit this in 3 days. Thanks, --- Upgrading 'apcupsd-3.14.3_1' to 'apcupsd-3.14.4' (sysutils/apcupsd) --- Building '/usr/ports/sysutils/apcupsd' === Cleaning for apcupsd-3.14.4 === Found saved configuration for apcupsd-3.14.4 === Extracting for apcupsd-3.14.4 = MD5 Checksum OK for apcupsd-3.14.4.tar.gz. = SHA256 Checksum OK for apcupsd-3.14.4.tar.gz. = MD5 Checksum OK for apcupsd.pdf. = SHA256 Checksum OK for apcupsd.pdf. === Patching for apcupsd-3.14.4 === Applying FreeBSD patches for apcupsd-3.14.4 Ignoring previously applied (or reversed) patch. 3 out of 3 hunks ignored--saving rejects to ./src/drivers/usb/bsd/bsd-usb.c.rej = Patch patch-src__drivers__usb__bsd__bsd-usb.c failed to apply cleanly. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.54579.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=apcupsd-3.14.3_1 UPGRADE_PORT_VER=3.14.3_1 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! sysutils/apcupsd (apcupsd-3.14.3_1) (patch error) Can you please send me tar of your port? May be the diff is broken? -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: please test sysutlis/apcupsd update
Greetings Ion-Mihai, Ion-Mihai Tetcu wrote: On Tue, 01 Jul 2008 13:38:49 +0300 Stefan Lambrev [EMAIL PROTECTED] wrote: [ .. ] === Patching for apcupsd-3.14.4 === Applying FreeBSD patches for apcupsd-3.14.4 Ignoring previously applied (or reversed) patch. 3 out of 3 hunks ignored--saving rejects to ./src/drivers/usb/bsd/bsd-usb.c.rej = Patch patch-src__drivers__usb__bsd__bsd-usb.c failed to apply cleanly. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.54579.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=apcupsd-3.14.3_1 UPGRADE_PORT_VER=3.14.3_1 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! sysutils/apcupsd (apcupsd-3.14.3_1) (patch error) Can you please send me tar of your port? May be the diff is broken? That file was removed as it was integrated upstream; I did diff -u instead of diff -uN. Thanks for catching this. Try the one attached or just rm the file. Removing the old patch fix the compilation problem. The new version of apcups (usb) works fine with: ugen0: American Power Conversion Back-UPS CS 500 FW:808.q7.I USB FW:q7, class 0/0, rev 1.10/0.06, addr 2 on uhub0 I hope to find time to test and with Smart-UPS 3000 RM (serial) and network too. -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
mc, centerim centerim-devel partly broken/cyrillic problems
Greetings, I have some strange problems with those ports. misc/mc no more draw windows borders. Sometimes it happens to draw some symbols when one expect lines, but for first time I see no borders at all, just spaces. At the same time Cyrillic in centerim (jabber) is now broken. I was wandering what can broke this. Because of new gnome update I upgraded using portupgrade -P (packages), so I thought something is not compiled ok. But today I switches from 6.3 to 7-STABLE, and removed almost all ports the ports that left where some libX* held hostages of nvidia-driver. All ports where recompiled and I installed misc/mc and net-im/centerim with the hope, that the problem will disappear. Unfortunately it is still here. Even when I send messages to myself they are unreadable. I'm to blame new glib and gnome, but centerim depends only on curl, gettext, gmake libiconv .. Any ideas? Is there good howto use UTF-8? ncurses in FreeBSD support UTF-8, KDE support it too, so I still do not understand why UTF-8 is so broken under FreeBSD. For comparison most Linux distros work out of the box when we talk about UTF-8. -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
patch to get apcupsd-3.14.3.tar.gz compiling under freebsd
Greetings,
Could you consider the attached patch (if you plan to upgrade the port
to the latest version)?
v3.14.3 does not compile under FreeBSD 6.3 without it.
Thanks.
--- src/drivers/usb/bsd/bsd-usb.c.orig 2007-10-27 20:15:14.0 +0300
+++ src/drivers/usb/bsd/bsd-usb.c 2008-03-18 01:10:26.0 +0200
@@ -351,9 +351,9 @@
int pusb_ups_get_capabilities(UPSINFO *ups, const struct s_known_info
*known_info)
{
- int i, rc, ci, phys;
+ int i, ci, phys, input, feature;
USB_DATA *my_data = (USB_DATA *)ups-driver_internal_data;
- hid_item_t item;
+ hid_item_t item, witem;
USB_INFO *info;
write_lock(ups);
@@ -506,7 +506,7 @@
// Store a (possibly truncated) copy of the floating point value in the
// integer field as well.
- val.iValue = val.dValue;
+ val.iValue = (int) val.dValue;
Dmsg4(200, Def val=%d exp=%d dVal=%f ci=%d\n, info-value,
exponent, val.dValue, info-ci);
@@ -775,7 +775,7 @@
return true;
}
-int pusb_write_int_to_ups(UPSINFO *ups, int ci, int value, char *name)
+int pusb_write_int_to_ups(UPSINFO *ups, int ci, int value, const char *name)
{
USB_DATA *my_data = (USB_DATA *)ups-driver_internal_data;
USB_INFO *info;
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new version of devel/pwlib does not compile on 7.0-RELEASE
Greetings, Steve Ames wrote: Jeremy Messenger wrote: On Wed, 05 Mar 2008 11:15:03 -0600, Steve Ames [EMAIL PROTECTED] wrote: All of your errors seem to stem from: /usr/local/include/iodbcunix.h which isn't part of pwlib and doesn't exist on my system. It comes from databases/libiodbc. Comment: An ODBC 3.x driver manager, for universal data source access Required by: openldap-sasl-server-2.3.41 Hrm. I'll install that locally and see what I can do to fix these errors. devel/pwlib definately compiles cleanly on 7.0-R but it appears not so much if database/libiodbc is installed. -Steve Not sure why pwlib interfere with libiodbc. If it doesn't need it, the patch can be to explicitly disable it? -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
new version of devel/pwlib does not compile on 7.0-RELEASE
../../ptclib/podbc.cxx: At global scope: ../../ptclib/podbc.cxx:1535: error: reference to 'BOOL' is ambiguous /usr/ports/devel/pwlib/work/ptlib_v1_12_0/include/ptlib/unix/ptlib/contain.h:135: error: candidates are: typedef int BOOL /usr/local/include/iodbcunix.h:136: error: typedef int PTODBC::BOOL ../../ptclib/podbc.cxx:1535: error: reference to 'BOOL' is ambiguous /usr/ports/devel/pwlib/work/ptlib_v1_12_0/include/ptlib/unix/ptlib/contain.h:135: error: candidates are: typedef int BOOL /usr/local/include/iodbcunix.h:136: error: typedef int PTODBC::BOOL ../../ptclib/podbc.cxx:1535: error: 'BOOL' does not name a type ../../ptclib/podbc.cxx:1553: error: reference to 'BOOL' is ambiguous /usr/ports/devel/pwlib/work/ptlib_v1_12_0/include/ptlib/unix/ptlib/contain.h:135: error: candidates are: typedef int BOOL /usr/local/include/iodbcunix.h:136: error: typedef int PTODBC::BOOL ../../ptclib/podbc.cxx:1553: error: reference to 'BOOL' is ambiguous /usr/ports/devel/pwlib/work/ptlib_v1_12_0/include/ptlib/unix/ptlib/contain.h:135: error: candidates are: typedef int BOOL /usr/local/include/iodbcunix.h:136: error: typedef int PTODBC::BOOL ../../ptclib/podbc.cxx:1553: error: 'BOOL' does not name a type ../../ptclib/podbc.cxx:1567: error: reference to 'BOOL' is ambiguous /usr/ports/devel/pwlib/work/ptlib_v1_12_0/include/ptlib/unix/ptlib/contain.h:135: error: candidates are: typedef int BOOL /usr/local/include/iodbcunix.h:136: error: typedef int PTODBC::BOOL ../../ptclib/podbc.cxx:1567: error: reference to 'BOOL' is ambiguous /usr/ports/devel/pwlib/work/ptlib_v1_12_0/include/ptlib/unix/ptlib/contain.h:135: error: candidates are: typedef int BOOL /usr/local/include/iodbcunix.h:136: error: typedef int PTODBC::BOOL ../../ptclib/podbc.cxx:1567: error: 'BOOL' does not name a type ../../ptclib/podbc.cxx: In member function 'unsigned int PODBCRecord::ColumnPrecision(PINDEX)': ../../ptclib/podbc.cxx:1590: error: cannot convert 'PTODBC::SWORD*' to 'long int*' for argument '7' to 'PTODBC::SQLRETURN PTODBC::SQLColAttribute(void*, PTODBC::SQLUSMALLINT, PTODBC::SQLUSMALLINT, void*, PTODBC::SQLSMALLINT, PTODBC::SQLSMALLINT*, long int*)' gmake[3]: *** [/usr/ports/devel/pwlib/work/ptlib_v1_12_0/lib/obj_d/podbc.o] Error 1 gmake[3]: Leaving directory `/usr/ports/devel/pwlib/work/ptlib_v1_12_0/src/ptlib/unix' gmake[2]: *** [debug] Error 2 gmake[2]: Leaving directory `/usr/ports/devel/pwlib/work/ptlib_v1_12_0' gmake[1]: *** [libs] Error 2 gmake[1]: Leaving directory `/usr/ports/devel/pwlib/work/ptlib_v1_12_0' gmake: *** [debuglibs] Error 2 *** Error code 2 Stop in /usr/ports/devel/pwlib. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.1857.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=pwlib-1.10.3_4,1 UPGRADE_PORT_VER=1.10.3_4,1 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! devel/pwlib (pwlib-1.10.3_4,1)(bad C++ code) -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
security/heimdal openssh-portable problems
Greetings, As described here: http://www.mail-archive.com/freebsd-ports@freebsd.org/msg10808.html upgrading heimdal break kauth (and openssh-portable). If I replace /usr/lib/libasn1.so.8 with /usr/local/lib/libasn1.so.8 ssh partly works, but gssapi-with-mic is still broken and I cannot login anymore. Here is some debug info from ssh -: debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug2: we sent a gssapi-with-mic packet, wait for reply debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password,keyboard-interactive This worked with older heimdal without problems: debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug2: we sent a gssapi-with-mic packet, wait for reply debug1: Authentication succeeded (gssapi-with-mic). debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 I'm using FreeBSD 7.0-RC1 i386, openssh-gssapi-4.7.p1_1,1 heimdal-1.0.1 Openssh is compiled with KRB5_HOME=/usr/local/ (but removing it doesn't help except that I can build ssh) Any ideas how to get gssapi-keyex working again ? or should I just downgrade heimdal to 0.7.2_2? Btw it will be nice if the base ssh in FreeBSD 7 works with gssapi-with-mic too :) -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sunbird marked as broken with gcc4.2
Hi, Garrett Cooper wrote: Stefan Lambrev wrote: Hi again, Stefan Lambrev wrote: Hi again, I removed the BROKEN line from the port and compiled sunbird without problems. /var/db/ports/sunbird/options: WITHOUT_DEBUG=true WITHOUT_LOGGING=true WITHOUT_OPTIMIZED_CFLAGS=true May be because I do not use OPTIMIZED_CFLAGS? I'll check and this :) Sunbird compiles without problems and WITH_OPTIMIZED_CFLAGS=true It does even work ;) So I'm not sure why it is marked as broken. FreeBSD 7.0-CURRENT #4: Mon Oct 1 11:17:32 EEST 2007 i386 Could this be broken with amd64? -Garrett Unfortunately I do not have FreeBSD 7 amd64 with X, so I can't check now. But I did this before 2-3 weeks and sunbird was working then. P.S. I'm receiving failure to delivery mails from [EMAIL PROTECTED] - subscribed to freebsd-ports. -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
sunbird - Mark as broken with gcc4.2.
Hello, Why is sunbird marked as broken with gcc 4.2? I have working sunbird-0.5,1 installed on 28.Sept.2007 running on FreeBSD 7.0-CURRENT #4: Mon Oct 1 11:17:32 EEST 2007 i386 compiled with : Using built-in specs. Target: i386-undermydesk-freebsd Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 4.2.1 20070719 [FreeBSD] Just to be sure I'll try to rebuild again today. -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
sunbird marked as broken with gcc4.2
Hi again, I removed the BROKEN line from the port and compiled sunbird without problems. /var/db/ports/sunbird/options: WITHOUT_DEBUG=true WITHOUT_LOGGING=true WITHOUT_OPTIMIZED_CFLAGS=true May be because I do not use OPTIMIZED_CFLAGS? I'll check and this :) -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sunbird marked as broken with gcc4.2
Hi again, Stefan Lambrev wrote: Hi again, I removed the BROKEN line from the port and compiled sunbird without problems. /var/db/ports/sunbird/options: WITHOUT_DEBUG=true WITHOUT_LOGGING=true WITHOUT_OPTIMIZED_CFLAGS=true May be because I do not use OPTIMIZED_CFLAGS? I'll check and this :) Sunbird compiles without problems and WITH_OPTIMIZED_CFLAGS=true It does even work ;) So I'm not sure why it is marked as broken. FreeBSD 7.0-CURRENT #4: Mon Oct 1 11:17:32 EEST 2007 i386 -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
ports/games/frozenbubble on FreeBSD 7
Hello, Frozen bubble on FreeBSD7 should depend on compat6x and the message how to start the program (if core dumps) should be changed to: LD_PRELOAD=/usr/local/lib/compat/libc_r.so.6 frozen-bubble Anyone care to fix this ? -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
heimdal-1.0.1
Hello,
There is a problem with new heimdal port in this part:
post-build:
.if defined(WITH_CRACKLIB)
${SED} -e s;%%LOCALBASE%%;${LOCALBASE};g \
${FILESDIR}/kpasswdd-cracklib.c.in
${WRKSRC}/kpasswdd-cracklib.c
(cd ${WRKSRC} \
${CC} ${CFLAGS} -fPIC -shared -I${LOCALBASE}/include
-I./include \
-L${LOCALBASE}/lib -o ./kpasswdd-cracklib.so
./kpasswdd-cracklib.c -lcrack)
.endif
but files/kpasswdd-cracklib.c.in does not exist, so remove CRACKLIB as
option or add the missing patch ? :)
--
Best Wishes,
Stefan Lambrev
ICQ# 24134177
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
p5-Mail-SpamAssassin-3.2.3 - manual whitelist_from broken
Hello, I noticed that after upgrading spamassassin to the latest (in ports) version, manual whitelist is somehow broken. In previous version spamassassin detects without a problem forged From headers and even with whitelist_from [EMAIL PROTECTED] mails that are spam got caught. With the latest version of spamassassins the following example will not be detected as spam: telnet mailserver-spamprotected.com 25 helo somedomain.com mail from: [EMAIL PROTECTED] rcpt to: [EMAIL PROTECTED] data From: [EMAIL PROTECTED] some spam xxx. . quit In this case whitelist_from [EMAIL PROTECTED] is triggered, and I'm pretty sure that wasn't a case in older versions of spamassassin. Any ideas what is changed, and how I can restored the old behavior. -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: p5-Mail-SpamAssassin-3.2.3 - manual whitelist_from broken
Hello, John Marshall wrote: Stefan Lambrev wrote: Hello, I noticed that after upgrading spamassassin to the latest (in ports) version, manual whitelist is somehow broken. In previous version spamassassin detects without a problem forged From headers and even with whitelist_from [EMAIL PROTECTED] mails that are spam got caught. With the latest version of spamassassins the following example will not be detected as spam: telnet mailserver-spamprotected.com 25 helo somedomain.com mail from: [EMAIL PROTECTED] rcpt to: [EMAIL PROTECTED] data From: [EMAIL PROTECTED] some spam xxx. . quit In this case whitelist_from [EMAIL PROTECTED] is triggered, and I'm pretty sure that wasn't a case in older versions of spamassassin. Any ideas what is changed, and how I can restored the old behavior. As far as I know, nothing has changed. What you are seeing is expected behaviour. whitelist_from should only be used as a last resort because it blindly trusts the (alleged) envelope sender address. The documentation warns about this: http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_Conf.html#whitelist_and_blacklist_options Personally, I include the SPF plugin and use whitelist_from_spf entries wherever possible. Failing that (if sending domain doesn't publish SPF details) I use whitelist_from_rcvd. This document says that envelope_sender_header is used to check whitelist_from - and I'm using postfix - it set Return-path header, and I think the problem is that spamassassin no more read this. I'll check if setting manually envelope_sender_header will change something. -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
adding new user for a port.
Hello, I'm trying to make a small port, but want to ask what is the right procedure, if my port requires a certain user to be on the installed system? Do I have to use pkg-install/pkg-deinstall for this? P.S. Please CC me as I'm not subscribed to freebsd-ports. -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
nagios plugins under freebsd 7-current
Hello, I'm having strange problem with one of the nagios plugins: /usr/local/libexec/nagios/check_disk - if I use the -p option it core dumps zsh: segmentation fault (core dumped) /usr/local/libexec/nagios/check_disk -w 5% -c 3% -p /usr Can someone help with patch please ? :) ktrace.out (22KB) can be downloaded from http://cheffo.freebsd-bg.org/ktrace.out Thanks in advance. -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
ports/security/blocksshd
Hi list, This is very annoying: pkg_delete: '/usr/local/etc/blocksshd.conf' fails original MD5 checksum - deleted anyway. can someone fix please ? -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/security/blocksshd
Hi list, Craig Butler wrote: Stefan Lambrev wrote: Hi list, This is very annoying: pkg_delete: '/usr/local/etc/blocksshd.conf' fails original MD5 checksum - deleted anyway. can someone fix please ? did you edit it ? Of course i edit it, after all it is the configuration file, I have different table in my pf, I have specified e-mail where to send notification, I have whitelisted IPs and etc. And simple upgrade *destroy* my configurations which is not nice ;) If I have little more time tomorrow I can send patch and the config file will be renamed to .sample so upgrading won't destroy configuration, and if you prefer I can add and pkg-msg or *echo* to tell user to copy config.sample to config when installing. If I have time I can even *steal* from other ports and make the port only to create blocksshd.conf only if it does not exist :) Sorry for moaning without sending patches ;) This email has been handled by lerwick.hopto.org mail server and has been scanned by 3 virus killers and spamassassin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
openssh-portable upgrade.
Hi all, After upgrade from openssh from 4.5 to 4.6 I'm unable to login using password authentication. Any idea what is broken ? From make config I have selected PAM,TCP_WRAPPERS,LIBEDIT,KERBEROS,GSSAPI,KERB_GSSAPI,OPENSSH_CHROOT and HPN From the original configuration file I have changed the protocol (support only for 2), few settings for GSSAPI KERBEROS. Everything works fine with 4.5 but not with 4.6. After putting PasswordAuthentication yes in sshd_conf I'm able to login using username/password, but this is built-in password authentication and skips PAM? -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
ports/sysutils/aaccli
Hello, Why aaccli is marked only for arch i386 ? :) It's a binary package build for i386, but it work perfect on amd64. Is there any other reason for this? -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
