Re: [kde-freebsd] HEADS UP: [CFT] KDE SC 4.4.0 for FreeBSD.

2010-02-14 Thread Dima Panov 
On Monday 15 February 2010 16:19:51 Freddie Cash wrote:
> On Tue, Feb 9, 2010 at 6:32 AM, Martin Wilke  wrote:
> > We the FreeBSD KDE Team are happy to let you know KDE SC 4.4.0 was
> > released few mins ago, and we're ready for a public test. Before
> > you ask we don't want to put KDE 4.4.0 in the ports tree before
> > FreeBSD 7.3 was released.
> > 
> > What is new:
> > KDE SC 4.4.0 provide many new features, designed to integrate
> > local and network social services .. and a lot more. The official
> > release notes for this release can be found at
> > http://kde.org/announcements/4.4/
> > 
> > Now you can get KDE SC 4.4 with a svn checkout:
> > 
> > svn co http://area51.pcbsd.org/trunk/area51/PORTS
> > svn co http://area51.pcbsd.org/trunk/area51/KDE
> > svn co http://area51.pcbsd.org/trunk/area51/Tools/
> > 
> > now try:
> > sh Tools/scripts/portsmerge
> > sh Tools/scripts/kdemerge
> > 
> > Please read carefull /usr/ports/UPDATING-area51
> 
> On a clean install (reformatted /usr/local and clean /var/db/pkg), I get
> errors trying to install any KDE ports that require Nepomuk.  So far,
> graphics/kdegraphics4 and deskutils/plasma-applet-playwolf have errored
> out.
> 
> Here's the output from playwolf.  The kdegraphics4 error is the same.
> 
> ===>  Patching for plasma-applet-playwolf-0.7.2_3
> CMake Error at
> /usr/local/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:70
> (MESSAGE):
>   Could NOT find Nepomuk (missing: NEPOMUK_LIBRARIES NEPOMUK_INCLUDE_DIR
>   SOPRANO_PLUGIN_REDLANDBACKEND_FOUND)
> Call Stack (most recent call first):
>   /usr/local/kde4/share/apps/cmake/modules/FindNepomuk.cmake:69
> (find_package_handle_standard_args)
>   CMakeLists.txt:4 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> *** Error code 1
> 
> Stop in /usr/ports/deskutils/plasma-applet-playwolf.

Why you have disable default options for redland/soprano, which prevent nepomuk 
lib to be 
builded?


> 
> Here are the major KDE components installed:
> kde4-icons-oxygen-4.4.0
> kde4-shared-mime-info-1.0
> kde4-xdg-env-1.0
> kdebase-4.4.0
> kdebase-runtime-4.4.0
> kdebase-workspace-4.4.0
> kdehier4-1.0.4
> kdelibs-4.4.0
> kdemultimedia-4.4.0
> kdepimlibs-4.4.0
> 
> Uname:  FreeBSD rogue.ashesofthe.net 8.0-STABLE FreeBSD 8.0-STABLE #1
> r201931: Tue Jan 12 21:46:23 PST 2010
> r...@rogue.ashesofthe.net:/usr/src-8/sys/i386/compile/ROGUE
> i386




-- 
Dima "Red Fox" Panov @ Home | C73E 2B72 1FFD 61BD E206 1234 A626 76ED 93E3 B018
Khabarovsk, Russia  | 2D30 2CCB 9984 130C 6F87 BAFC FB8B A09D D539 8F29
k...@freebsd Team | FreeBSD committer since 10.08.2009 | FreeBSD since Sept 1995
Twitter.com:fluffy_khv | Skype:dima.panov | Jabber.org:fluffy.khv | ICQ:1745024
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: HEADS UP: [CFT] KDE SC 4.4.0 for FreeBSD.

2010-02-14 Thread Freddie Cash 
On Tue, Feb 9, 2010 at 6:32 AM, Martin Wilke  wrote:

> We the FreeBSD KDE Team are happy to let you know KDE SC 4.4.0 was
> released few mins ago, and we're ready for a public test. Before
> you ask we don't want to put KDE 4.4.0 in the ports tree before
> FreeBSD 7.3 was released.
>
> What is new:
> KDE SC 4.4.0 provide many new features, designed to integrate
> local and network social services .. and a lot more. The official
> release notes for this release can be found at
> http://kde.org/announcements/4.4/
>
> Now you can get KDE SC 4.4 with a svn checkout:
>
> svn co http://area51.pcbsd.org/trunk/area51/PORTS
> svn co http://area51.pcbsd.org/trunk/area51/KDE
> svn co http://area51.pcbsd.org/trunk/area51/Tools/
>
> now try:
> sh Tools/scripts/portsmerge
> sh Tools/scripts/kdemerge
>
> Please read carefull /usr/ports/UPDATING-area51
>

On a clean install (reformatted /usr/local and clean /var/db/pkg), I get
errors trying to install any KDE ports that require Nepomuk.  So far,
graphics/kdegraphics4 and deskutils/plasma-applet-playwolf have errored out.

Here's the output from playwolf.  The kdegraphics4 error is the same.

===>  Patching for plasma-applet-playwolf-0.7.2_3
echo >>
/usr/ports/workdir/usr/ports/deskutils/plasma-applet-playwolf/work/playwolf/flowlayout.cpp
echo >>
/usr/ports/workdir/usr/ports/deskutils/plasma-applet-playwolf/work/playwolf/flowlayout.h
echo >>
/usr/ports/workdir/usr/ports/deskutils/plasma-applet-playwolf/work/playwolf/playwolf.cpp
echo >>
/usr/ports/workdir/usr/ports/deskutils/plasma-applet-playwolf/work/playwolf/playwolf.h
echo >>
/usr/ports/workdir/usr/ports/deskutils/plasma-applet-playwolf/work/playwolf/wolfbuttons.cpp
echo >>
/usr/ports/workdir/usr/ports/deskutils/plasma-applet-playwolf/work/playwolf/wolflabel.h
cd
/usr/ports/workdir/usr/ports/deskutils/plasma-applet-playwolf/work/playwolf
&& /usr/bin/sed -i.bak -e 's|usr|/usr/local/kde4|g'  infomanager.cpp
wolflabel.cpp
===>   plasma-applet-playwolf-0.7.2_3 depends on file:
/usr/local/lib/qt4/libQtDBus.so - found
===>   plasma-applet-playwolf-0.7.2_3 depends on file:
/usr/local/lib/qt4/libQtGui.so - found
===>   plasma-applet-playwolf-0.7.2_3 depends on file:
/usr/local/bin/moc-qt4 - found
===>   plasma-applet-playwolf-0.7.2_3 depends on file:
/usr/local/lib/qt4/libQtNetwork.so - found
===>   plasma-applet-playwolf-0.7.2_3 depends on file:
/usr/local/lib/qt4/libQtOpenGL.so - found
===>   plasma-applet-playwolf-0.7.2_3 depends on file:
/usr/local/bin/qmake-qt4 - found
===>   plasma-applet-playwolf-0.7.2_3 depends on file: /usr/local/bin/rcc -
found
===>   plasma-applet-playwolf-0.7.2_3 depends on file:
/usr/local/lib/qt4/libQtSvg.so - found
===>   plasma-applet-playwolf-0.7.2_3 depends on file:
/usr/local/bin/uic-qt4 - found
===>   plasma-applet-playwolf-0.7.2_3 depends on file:
/usr/local/lib/qt4/libQtWebKit.so - found
===>   plasma-applet-playwolf-0.7.2_3 depends on file:
/usr/local/lib/qt4/libQtXml.so - found
===>   plasma-applet-playwolf-0.7.2_3 depends on file:
/usr/local/bin/automoc4 - found
===>   plasma-applet-playwolf-0.7.2_3 depends on file: /usr/local/bin/cmake
- found
===>   plasma-applet-playwolf-0.7.2_3 depends on shared library: kimproxy.5
- found
===>  Configuring for plasma-applet-playwolf-0.7.2_3
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - found
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found.
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found.
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - not found.
-- Found Qt-Version 4.6.1 (using /usr/local/bin/qmake-qt4)
-- Looking for XOpenDisplay in
/usr/local/lib/libX11.so;/usr/local/lib/libXext.so;/usr/local/lib/libXft.so;/usr/local/lib/libXau.so;/usr/local/lib/libXdmcp.so;/usr/local/lib/libXpm.so
-- Looking for XOpenDisplay in
/usr/local/lib/libX11.so;/usr/local/lib/libXext.so;/usr/local/lib/libXft.so;/usr/local/lib/libXau.so;/usr/local/lib/libXdmcp.so;/usr/local/lib/libXpm.so
- found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found X11: /usr/local/lib/libX11.so
-- Looking for include files CMAKE_HAVE_PTHREAD_H
-- Looking for include files CMAKE_HAVE_PTHREAD_H - found
-- Found Threads: TRUE
-- Looking for _POSIX_TIMERS
-- Looking for _POSIX_TIMERS - found
-- Found Automoc4: /usr/local/bin/automoc4
-- Found Perl: /usr/bin/perl
-- Phon

Problems with policykit and printer-applet

2010-02-14 Thread Duncan Young 
Hi all,

I'm currently trying to resolve an ongoing issue I have with printer-applet 
refusing to run for me.

The output from running it on the command line is as follows.


% printer-applet
printer-applet(10724) KLocalePrivate::initEncoding: Cannot resolve system 
encoding, defaulting to ISO 8859-1.QEventDispatcherUNIX::unregisterTimer: 
invalid argument
Traceback (most recent call last):
  File "/usr/local/kde4/bin/printer-applet", line 1161, in 
applet = JobManager()
  File "/usr/local/kde4/bin/printer-applet", line 297, in __init__
notification = NewPrinterNotification(bus, self)
  File "/usr/local/kde4/bin/printer-applet", line 1050, in __init__
bus_name = dbus.service.BusName (PDS_OBJ, bus=bus)
  File "/usr/local/lib/python2.6/site-packages/dbus/service.py", line 129, in 
__new__
retval = bus.request_name(name, name_flags)
  File "/usr/local/lib/python2.6/site-packages/dbus/bus.py", line 306, in 
request_name
'su', (name, flags))
  File "/usr/local/lib/python2.6/site-packages/dbus/connection.py", line 622, 
in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: 
Connection ":1.44" is not allowed to own the service 
"com.redhat.NewPrinterNotification" due to security policies in the 
configuration file

I'm running FreeBSD 8.0-RELEASE-p2 on amd64 an have a fairly up to date set of 
ports. i.e. kdebase-4.3.5 and kdeutils-printer-applet-4.3.5_2.

I believe the problem is due to policykit settings, but I must admit I'm not up 
on how to modify the config files.

I believe the relevant file is 
/usr/local/etc/dbus-1/system.d/newprinternotification.conf.

cat http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";>




















Any help would be greatly appreciated

Duncan
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Update of net/ntp to 4.2.6p1-RC5

2010-02-14 Thread Cy Schubert 
Doug,

I can't get to this tonight. Do you mind committing this for me please?


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  http://www.FreeBSD.org

e**(i*pi)+1=0


In message <4b786894.7070...@dougbarton.us>, Doug Barton writes:
> This is a multi-part message in MIME format.
> --090501030708000508000703
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
> 
> hth,
> 
> Doug
> 
> -- 
> 
>   ... and that's just a little bit of history repeating.
>   -- Propellerheads
> 
>   Improve the effectiveness of your Internet presence with
>   a domain name makeover!http://SupersetSolutions.com/
> 
> 
> --090501030708000508000703
> Content-Type: text/plain;
>  name="ntp.diff"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: attachment;
>  filename="ntp.diff"
> 
> ? work
> Index: Makefile
> ===
> RCS file: /home/pcvs/ports/net/ntp/Makefile,v
> retrieving revision 1.58
> diff -u -r1.58 Makefile
> --- Makefile  30 Dec 2009 19:09:51 -  1.58
> +++ Makefile  14 Feb 2010 21:11:59 -
> @@ -6,7 +6,7 @@
>  #
>  
>  PORTNAME=ntp
> -PORTVERSION?=4.2.6p1.r2
> +PORTVERSION?=4.2.6p1.r5
>  CATEGORIES=  net ipv6
>  MASTER_SITES=ftp://ftp.udel.edu/pub/ntp/ntp4/ \
>   http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ \
> Index: distinfo
> ===
> RCS file: /home/pcvs/ports/net/ntp/distinfo,v
> retrieving revision 1.31
> diff -u -r1.31 distinfo
> --- distinfo  27 Dec 2009 04:51:27 -  1.31
> +++ distinfo  14 Feb 2010 21:11:59 -
> @@ -1,3 +1,3 @@
> -MD5 (ntp-4.2.6p1-RC2.tar.gz) = 3d757f69085c125cb885bd648b441b82
> -SHA256 (ntp-4.2.6p1-RC2.tar.gz) = 3a2f05f5f915800a25b4915361c5f30e309985af40
> feac1b64f5eac508c219a5
> -SIZE (ntp-4.2.6p1-RC2.tar.gz) = 4333146
> +MD5 (ntp-4.2.6p1-RC5.tar.gz) = 7080acba1d742af81c101d4028f83642
> +SHA256 (ntp-4.2.6p1-RC5.tar.gz) = f4864d64da710394dd2104f95ed46e75918481ce68
> 2be4de0187c6e7290915a7
> +SIZE (ntp-4.2.6p1-RC5.tar.gz) = 4336386
> 
> --090501030708000508000703--


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: bsd.gcc.mk PREFIX or LOCALBASE?

2010-02-14 Thread Gerald Pfeifer 
On Sun, 14 Feb 2010, jhell wrote:
> Could this possibly be the cause of the samba3* and cups ports getting 
> profiling enabled on them ? possibly others ?

I don't think the the use of ${PREFIX} versus ${LOCALBASE} can have
such an effect, and by default (and thus the vast majority of uses)
the two are set to the same value.

Gerald
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Shoud devel port be RC or GIT based?

2010-02-14 Thread CeDeROM 
Hello world!

In a moments of hard testing just before a software release, releases
of a RC (Release Candidate) packages are done to alow some final
tests. I am wondering if it is convenient to create the devel port, to
allow better testing for non-freebsd-aware users. Would that be more
convenient to base such devel port on a RC releases, or directly the
GIT repository?

How would the dynamic pkg-plist file content look like in case of GIT build?
Would files built from GIT repository are to be installed in
/usr/local or some easry-to-remove specific location such as
/tmp/devel/portname ?

Is it convenient at all to create GIT based devel port if the user
needs to use standard git procedure anyway to upload the
rewritten/updated files?

Please advise :-)
Tomek Cedro

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

compiz-fusion update problem

2010-02-14 Thread barbara 
I'm not on this mailing list but I read you message. Sorry for not replying 
directly.

The problem is that a patch for libcompizconfig has been removed, but this 
patch is still necessary on RELENG_7 and older RELENG_8.
I wrote to rnoland@ on Feb. 11 and he replayed that he will fix the port as 
soon as he can.
There is also a PR pointing the correct osreldate for which the patch could be 
removed (try googling). Maybe someone else can do it before him.

In the meanwhile, if you really need this update, you can grab the removed 
patch from here:
http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/x11-wm/libcompizconfig/files/Attic/patch-src-compiz.cpp?rev=1.1;content-type=text%2Fplain
( http://zipp.it/i/P962E )
and put in /usr/ports/x11-wm/libcompizconfig/files

Best Regards
Barbara



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: RC1 suffix in PORTVERSION

2010-02-14 Thread CeDeROM 
Hello Dimitry!

On Sun, Feb 14, 2010 at 3:36 AM, Dmitry Marakasov  wrote:
> * CeDeROM (tomek.ce...@gmail.com) wrote:
>
>> I am trying to create a helper local port for testing RC1 version of a
>> program that will soon have stable port update. Unfortunately the
>> package is named "openocd-0.4.0-rc1.tar.gz" and I dont know how to
>> construct a variable containing this "-RC1" suffix.
>
> You can use DISTVERSION=0.4.0-rc1 instead of PORTVERSION.
>
> + you won't have to redefine DISTNAME, as DISTVERSION is substituded
>  there directly
> + legal PORTVERSION will be constructed for you (that'll be 0.4.0.r1),
>  and the nicest thing is that 0.4.0.r1 < 0.4.0, thus when you update
>  the port to release, you won't need to bump PORTEPOCH.

BINGO! The DISTVERSION=0.4.0-rc2 does the job right - download proper
package (openocd-0.4.0-rc2.tar.gz), extracts it and then build from
right place (${WRKDIR}/openocd-0.4.0-rc2/) - no other variables are
necessary :-) Thank you!

However, in that situation, one must remember not to touch $WRKSRC
unnecessairly as it might to point at wrong directory ;P

Best regards,
Tomek Cedro

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: bsd.gcc.mk PREFIX or LOCALBASE?

2010-02-14 Thread Gerald Pfeifer 
On Sat, 13 Feb 2010, b. f. wrote:
> I agree with you, and I meant to mention this to gerald@ earlier, but
> I forgot.  The Ports system is not now well-equipped to deal with
> LOCALBASE != PREFIX for a lot of software, and most people don't do
> this, so the impact is limited, but it does break some test builds and
> utilities, as you have seen.

Thanks for forwarding this report my way b.  I agree, based on personal
experience, that in general once one uses some of the flexibility the
Ports Collection provides deviating from the defaults, things tend to
become interesting, but still we should address issues when we encounter
them to the extent possible.

On Sat, 13 Feb 2010, Rob Farmer wrote:
> Yeah, I realize this is kind of an unusual situation and I understand
> that with the ports freeze coming up that now is not a good time to be
> making these kind of changes, but just thought I would mention it
> since I came across it.

Well, one can reasonably call this a bug -- after all, you ran into a
very concrete problem -- and for default settings PREFIX and LOCALBASE
are the same, so the risk of the change is very low and I went ahead
and committed a patch.

Thanks for reporting this, Rob, and I'm sorry you ran into this.

Gerald @FreeBSD.org
-- 
Gerald (Jerry) Pfeifer   ger...@pfeifer.com   http://www.pfeifer.com/gerald/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Installing a different PORTVERSION based on OSVERSION?

2010-02-14 Thread Darren Pilgrim 

Garrett Cooper wrote:

Vendor provided binaries are a fun ball of wax to deal with
because you need to have all dependencies come from the same generic
pool as the package [/ port] itself, as any
This sounds trivial, but it requires changes to pkg_add (for
fetching / installing a particular revision of the code, as well as
`slotting' the packages themselves), determining elf-version, ld
modifications, as well as a few other things. It's been implemented at
my work [Ironport] from what I've been told, but 1) I'm not sure how
complete it is, 2) I'm not sure how tested it is, and 3) it hasn't
been reviewed yet and I'm not sure how much would be put back in the
community at large to be honest...


Or you can take the vendor's approach and make a static binary with all 
the dependencies (i.e., libraries) compiled in.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Checksum mismatch for ports/finance/homebank-4.2

2010-02-14 Thread Doug Barton 

On 02/14/10 13:56, Ruslan Mahmatkhanov wrote:

Hi.

I've contacted the author. It confirm that it was rerrolled:


That's fine, but our process mandates that any committer who makes the 
update needs to verify the diff between the two tarballs.



Doug

--

... and that's just a little bit of history repeating.
-- Propellerheads

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Checksum mismatch for ports/finance/homebank-4.2

2010-02-14 Thread Ruslan Mahmatkhanov 

Hi.

I've contacted the author. It confirm that it was rerrolled:

==
Hi,

It is intentional, done by myself to fix a problem into the package.

Regards,
Max.

- Mail Original -
De: "Ruslan Mahmatkhanov" 
À: homeb...@free.fr
Envoyé: Dimanche 14 Février 2010 21h45:52 GMT +01:00 Amsterdam / Berlin 
/ Berne / Rome / Stockholm / Vienne

Objet: 4.2 tarball size

Good day!

Was 4.2 tarball rerolled after release?
It had size of 2611432 and md5 checksum 558be92f996c339e87ad396795691364,
but now it has 2611439 and 5d76ab58f6e211c6cc3902b3f38ff22d accordingly.
And mtime it has is 12 Feb 16:12.
Was it intentional or it was somehow backdoored )?

Thanks.
==

Can please anybody commit attached patch?


On 15.02.2010 00:28, Doug Barton wrote:

On 02/14/10 03:46, hanno Krusken wrote:

Hi there,

since the last upgrade there is a "Checksum mismatch for FBSD
port/finance/homebank-4.2"
see my log file from portupgrade running FreeBSD-8.0-releng-p2


Does anyone have the old distfile (the one corresponding to what's
currently in the ports tree)? If so, can you make it available for
comparison?


Doug



--- distinfo.orig   2010-02-13 11:46:43.0 +0300
+++ distinfo2010-02-15 00:53:32.0 +0300
@@ -1,3 +1,3 @@
-MD5 (homebank-4.2.tar.gz) = 558be92f996c339e87ad396795691364
-SHA256 (homebank-4.2.tar.gz) = 
0bb52d4d4ca2ed128fe614d4ad1cf1923004392f5651f12389256d336898e834
-SIZE (homebank-4.2.tar.gz) = 2611432
+MD5 (homebank-4.2.tar.gz) = 5d76ab58f6e211c6cc3902b3f38ff22d
+SHA256 (homebank-4.2.tar.gz) = 
67b7026deccd14023dbfecdd46983d0337f039fb1896222620d39423fae61224
+SIZE (homebank-4.2.tar.gz) = 2611439
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Installing a different PORTVERSION based on OSVERSION?

2010-02-14 Thread Garrett Cooper 
On Sun, Feb 14, 2010 at 12:58 PM, Darren Pilgrim  wrote:
> Wesley Shields wrote:
>>
>> On Sat, Feb 13, 2010 at 07:26:39PM -0800, Darren Pilgrim wrote:
>>>
>>> I'm working on a revision to a port where the current version doesn't
>>> work on 8.0-R; however, an older version does.  Rather than roll the entire
>>> port back to an older version, I'd like to have the newer version available
>>> to 7.x and older and the older version available to 8.x and newer.  Is it
>>> appropriate to install different versions of a port based on ${OSVERSION}?
>>>  If so, do I just set the necessary variables after including
>>> bsd.port.pre.mk?
>>
>> This seems like a bad idea to me. How much effort would it take to fix
>> the port on 8.x and newer?
>
> The port contains a static-linked binary from the vendor--not something I
> can patch.
>
>> The other option is to mark it broken on 8.x and newer.
>
> The port currently sets BROKEN if OSVERSION >= 80.

Vendor provided binaries are a fun ball of wax to deal with
because you need to have all dependencies come from the same generic
pool as the package [/ port] itself, as any
This sounds trivial, but it requires changes to pkg_add (for
fetching / installing a particular revision of the code, as well as
`slotting' the packages themselves), determining elf-version, ld
modifications, as well as a few other things. It's been implemented at
my work [Ironport] from what I've been told, but 1) I'm not sure how
complete it is, 2) I'm not sure how tested it is, and 3) it hasn't
been reviewed yet and I'm not sure how much would be put back in the
community at large to be honest...
HTH,
-Garrett
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Update of net/ntp to 4.2.6p1-RC5

2010-02-14 Thread Doug Barton 

hth,

Doug

--

... and that's just a little bit of history repeating.
-- Propellerheads

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

? work
Index: Makefile
===
RCS file: /home/pcvs/ports/net/ntp/Makefile,v
retrieving revision 1.58
diff -u -r1.58 Makefile
--- Makefile30 Dec 2009 19:09:51 -  1.58
+++ Makefile14 Feb 2010 21:11:59 -
@@ -6,7 +6,7 @@
 #
 
 PORTNAME=  ntp
-PORTVERSION?=  4.2.6p1.r2
+PORTVERSION?=  4.2.6p1.r5
 CATEGORIES=net ipv6
 MASTER_SITES=  ftp://ftp.udel.edu/pub/ntp/ntp4/ \
http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ \
Index: distinfo
===
RCS file: /home/pcvs/ports/net/ntp/distinfo,v
retrieving revision 1.31
diff -u -r1.31 distinfo
--- distinfo27 Dec 2009 04:51:27 -  1.31
+++ distinfo14 Feb 2010 21:11:59 -
@@ -1,3 +1,3 @@
-MD5 (ntp-4.2.6p1-RC2.tar.gz) = 3d757f69085c125cb885bd648b441b82
-SHA256 (ntp-4.2.6p1-RC2.tar.gz) = 
3a2f05f5f915800a25b4915361c5f30e309985af40feac1b64f5eac508c219a5
-SIZE (ntp-4.2.6p1-RC2.tar.gz) = 4333146
+MD5 (ntp-4.2.6p1-RC5.tar.gz) = 7080acba1d742af81c101d4028f83642
+SHA256 (ntp-4.2.6p1-RC5.tar.gz) = 
f4864d64da710394dd2104f95ed46e75918481ce682be4de0187c6e7290915a7
+SIZE (ntp-4.2.6p1-RC5.tar.gz) = 4336386
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Checksum mismatch for ports/finance/homebank-4.2

2010-02-14 Thread Doug Barton 

On 02/14/10 03:46, hanno Krusken wrote:

Hi there,

since the last upgrade there is a "Checksum mismatch for FBSD 
port/finance/homebank-4.2"
see my log file from portupgrade running FreeBSD-8.0-releng-p2


Does anyone have the old distfile (the one corresponding to what's 
currently in the ports tree)? If so, can you make it available for 
comparison?



Doug

--

... and that's just a little bit of history repeating.
-- Propellerheads

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [HEADSUP]: ports feature freeze starts in one week

2010-02-14 Thread Erwin Lansing 
On Sun, Jan 31, 2010 at 07:36:33PM +0100, Erwin Lansing wrote:
> In preparation for 7.3-RELEASE, the ports tree will be in feature freeze
> after release candidate 1 (RC1 )is released, currently planned for
> February 8.

For those wondering why the freeze hasn't taken effect yet, as the
freeze coincides with RC1, we are waiting for RC1 to be announced which
should be any day now.

-erwin

> If you have any commits with high impact planned, get them in the tree
> before then and if they require an experimental build, have a request
> for one in portmgr hands within the next few days.
> 
> Note that this again will be a feature freeze and not a full freeze.
> Normal upgrade, new ports, and changes that only affect other branches
> will be allowed without prior approval but with the extra
> Feature safe: yes tag in the commit message.  Any commit that is sweeping,
> i.e. touches a large number of ports, infrastructural changes, commts to
> ports with unusually high number of dependencies, and any other commit
> that requires the rebuilding of many packages will not be allowed
> without prior explicit approval from portmgr after that date.
> 
> -erwin
> 
> -- 
> Erwin Lansing   http://droso.org
> Prediction is very difficult
> especially about the futureer...@freebsd.org


-- 
Erwin Lansing   http://droso.org
Prediction is very difficult
especially about the futureer...@freebsd.org


pgpU2NS5UPBMg.pgp
Description: PGP signature

Re: Installing a different PORTVERSION based on OSVERSION?

2010-02-14 Thread Darren Pilgrim 

Wesley Shields wrote:

On Sat, Feb 13, 2010 at 07:26:39PM -0800, Darren Pilgrim wrote:
I'm working on a revision to a port where the current version doesn't 
work on 8.0-R; however, an older version does.  Rather than roll the 
entire port back to an older version, I'd like to have the newer version 
available to 7.x and older and the older version available to 8.x and 
newer.  Is it appropriate to install different versions of a port based 
on ${OSVERSION}?  If so, do I just set the necessary variables after 
including bsd.port.pre.mk?


This seems like a bad idea to me. How much effort would it take to fix
the port on 8.x and newer?


The port contains a static-linked binary from the vendor--not something 
I can patch.



The other option is to mark it broken on 8.x and newer.


The port currently sets BROKEN if OSVERSION >= 80.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: bsd.gcc.mk PREFIX or LOCALBASE?

2010-02-14 Thread jhell 


On Sat, 13 Feb 2010 21:47, rfarmer@ wrote:

On Sat, Feb 13, 2010 at 12:08 AM, b. f.  wrote:

In bsd.gcc.mk there is:

.   if ${_USE_GCC} != 3.4
CFLAGS+=                -Wl,-rpath=${PREFIX}/lib/${_GCC_BUILD_DEPENDS}
LDFLAGS+=               -Wl,-rpath=${PREFIX}/lib/${_GCC_BUILD_DEPENDS}
.   endif

However, I think this should be ${LOCALBASE} instead of ${PREFIX}.


I agree with you, and I meant to mention this to gerald@ earlier, but
I forgot.  The Ports system is not now well-equipped to deal with
LOCALBASE != PREFIX for a lot of software, and most people don't do
this, so the impact is limited, but it does break some test builds and
utilities, as you have seen.


Yeah, I realize this is kind of an unusual situation and I understand
that with the ports freeze coming up that now is not a good time to be
making these kind of changes, but just thought I would mention it
since I came across it.



Could this possibly be the cause of the samba3* and cups ports getting 
profiling enabled on them ? possibly others ?


If so I would think this should be important enough to fix before.

Inquisitive question.

--

 jhell

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Checksum mismatch for ports/finance/homebank-4.2

2010-02-14 Thread Ruslan Mahmatkhanov 

On 14.02.2010 14:46, hanno Krusken wrote:

Hi there,

since the last upgrade there is a "Checksum mismatch for FBSD 
port/finance/homebank-4.2"
see my log file from portupgrade running FreeBSD-8.0-releng-p2

===>   Cleaning for homebank-4.2
===>   Found saved configuration for homebank-4.1
=>  homebank-4.2.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
=>  Attempting to fetch from http://homebank.free.fr/public/.
fetch: http://homebank.free.fr/public/homebank-4.2.tar.gz: size mismatch: 
expected 2611432, actual 2611439


Seems like tarball was rerolled.
4.2 was released on 10 February, but tarball's mtime is 12 Feb 16:12.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: smbclient from net/smbclient generates smbclient.gmon files

2010-02-14 Thread jhell 


On Sun, 14 Feb 2010 06:54, barbara.xxx1975@ wrote:



On Sun, Feb 14, 2010 at 1:27 AM, barbara  wrote:

During the recent massive port upgrades, I decided to uninstall net/samba3 and 
install net/smb-smbclient as I need just the client component.
Now I've noticed that, every times I start smbclient, a file named "smbclient.gmon" 
(about 2 mb), reported as "data" by file(1), is generated in the CWD.
I've no idea about what is that file and a search on google reported 0 results.
This is pretty annoying because I'll get a copy of this file in every directory 
where I start smbclient.
This wasn't happening with smbclient built from net/samba3 and just before the 
upgrade smb-smbclient has been updated from 3.0 to 3.4, so I'm wondering if 
this behavior depends on the version or on the port (samba3* vs 
samba-smbclient).
But what really matters is how can it stop it creating this file?


There's a PR related to this (ports/143924) - it is a problem with the
port and hopefully will be fixed soon.

--
Rob Farmer



I hope it will be fixed soon because I know for a fact it has infected my 
systems with the .gmon for samba33 samba34 and cups. So far that is all I 
noticed. :(


These are all from recent cups and samba34 on two machines. I'm not willing 
to upgrade anymore machines until these disappear.


Had to nail down some symlinks in /.

lrwxr-xr-x  1 root  wheel  9 Feb 11 00:17 /cupsd.gmon -> /dev/null
lrwxr-xr-x  1 root  wheel  9 Feb 10 18:42 /nmbd.gmon -> /dev/null
lrwxr-xr-x  1 root  wheel  9 Feb 10 18:42 /smbd.gmon -> /dev/null
lrwxr-xr-x  1 root  wheel  9 Feb 10 18:42 /testparm.gmon -> /dev/null
lrwxr-xr-x  1 root  wheel  9 Feb 10 18:43 /winbindd.gmon -> /dev/null



Ok, thanks to both of you for the information!




--

 jhell

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

compiz-fusion update problem

2010-02-14 Thread Bc. Radek Krejca 
Hi,

  I updatet ports tree and try to update compiz fusion, but I got
  this message:

  compiz.Tpo -c compiz.cpp  -fPIC -DPIC -o .libs/compiz.o
compiz.cpp: In function 'void loadPluginsFromXMLFiles(CCSContext*, char*)':
compiz.cpp:2884: error: invalid conversion from 'int (*)(const dirent*)'
to 'int (*)(dirent*)'
compiz.cpp:2884: error:   initializing argument 3 of 'int scandir(const
char*, dirent***, int (*)(dirent*), int (*)(const void*, const void*))'
compiz.cpp: In function 'void loadPluginsFromName(CCSContext*, char*)':
compiz.cpp:2947: error: invalid conversion from 'int (*)(const dirent*)'
to 'int (*)(dirent*)'
compiz.cpp:2947: error:   initializing argument 3 of 'int scandir(const
char*, dirent***, int (*)(dirent*), int (*)(const void*, const void*))'
gmake[2]: *** [compiz.lo] Error 1
gmake[2]: Leaving directory
`/usr/ports/x11-wm/libcompizconfig/work/libcompizconfig-0.8.4/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/usr/ports/x11-wm/libcompizconfig/work/libcompizconfig-0.8.4'
gmake: *** [all] Error 2
*** Error code 1

Stop in /usr/ports/x11-wm/libcompizconfig.

===>>> make failed for x11-wm/libcompizconfig
===>>> Aborting update

===>>> Update for x11-wm/libcompizconfig failed
===>>> Aborting update


FreeBSD 8.0 amd64

-- 
Regards,
 Bc. Radek Krejca
 STARNET, s. r. o.
 ra...@ceskedomeny.cz

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Installing a different PORTVERSION based on OSVERSION?

2010-02-14 Thread Wesley Shields 
On Sat, Feb 13, 2010 at 07:26:39PM -0800, Darren Pilgrim wrote:
> I'm working on a revision to a port where the current version doesn't 
> work on 8.0-R; however, an older version does.  Rather than roll the 
> entire port back to an older version, I'd like to have the newer version 
> available to 7.x and older and the older version available to 8.x and 
> newer.  Is it appropriate to install different versions of a port based 
> on ${OSVERSION}?  If so, do I just set the necessary variables after 
> including bsd.port.pre.mk?

This seems like a bad idea to me. How much effort would it take to fix
the port on 8.x and newer? The other option is to mark it broken on 8.x
and newer.

-- WXS
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Checksum mismatch for ports/finance/homebank-4.2

2010-02-14 Thread hanno Krusken 
Hi there,

since the last upgrade there is a "Checksum mismatch for FBSD 
port/finance/homebank-4.2"
see my log file from portupgrade running FreeBSD-8.0-releng-p2

===>  Cleaning for homebank-4.2
===>  Found saved configuration for homebank-4.1
=> homebank-4.2.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch from http://homebank.free.fr/public/.
fetch: http://homebank.free.fr/public/homebank-4.2.tar.gz: size mismatch: 
expected 2611432, actual 2611439
=> Attempting to fetch from ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/.
fetch: ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/homebank-4.2.tar.gz: 
File unavailable (e.g., file not found, no access)
=> Attempting to fetch from 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/Latest/.
fetch: 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/Latest/homebank-4.2.tar.gz: 
File unavailable (e.g., file not found, no access)
=> Attempting to fetch from 
ftp://ftp3.dk.freebsd.org/pub/FreeBSD/ports/distfiles/.
fetch: 
ftp://ftp3.dk.freebsd.org/pub/FreeBSD/ports/distfiles/homebank-4.2.tar.gz: File 
unavailable (e.g., file not found, no access)
=> Attempting to fetch from 
ftp://ftp2.dk.freebsd.org/pub/FreeBSD/ports/distfiles/.
fetch: 
ftp://ftp2.dk.freebsd.org/pub/FreeBSD/ports/distfiles/homebank-4.2.tar.gz: File 
unavailable (e.g., file not found, no access)
=> Attempting to fetch from 
ftp://ftp.uk.freebsd.org/pub/FreeBSD/ports/distfiles/.
fetch: 
ftp://ftp.uk.freebsd.org/pub/FreeBSD/ports/distfiles/homebank-4.2.tar.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.
*** Error code 1

Stop in /usr/ports/finance/homebank.


hope the issue can be fixed soon... thanks
-- 
Hanno Krusken

Important note:
please do not replay with any HTML tags in your mail which will be blocked and 
deleted.
Regarding known SPAM, VIRUS and junk mail sender, which often use this way of 
fooling recipients
with fancy images and HTML-artwork. Remember that I'm using a very strict spam 
setup on top of it.
Thanks for your understanding.


signature.asc
Description: PGP signature

Re: smbclient from net/smbclient generates smbclient.gmon files

2010-02-14 Thread barbara 

> On Sun, Feb 14, 2010 at 1:27 AM, barbara  wrote:
> > During the recent massive port upgrades, I decided to uninstall net/samba3 
> > and install net/smb-smbclient as I need just the client component.
> > Now I've noticed that, every times I start smbclient, a file named 
> > "smbclient.gmon" (about 2 mb), reported as "data" by file(1), is generated 
> > in the CWD.
> > I've no idea about what is that file and a search on google reported 0 
> > results.
> > This is pretty annoying because I'll get a copy of this file in every 
> > directory where I start smbclient.
> > This wasn't happening with smbclient built from net/samba3 and just before 
> > the upgrade smb-smbclient has been updated from 3.0 to 3.4, so I'm 
> > wondering if this behavior depends on the version or on the port (samba3* 
> > vs samba-smbclient).
> > But what really matters is how can it stop it creating this file?
>
> There's a PR related to this (ports/143924) - it is a problem with the
> port and hopefully will be fixed soon.
>
> --
> Rob Farmer
>

Ok, thanks to both of you for the information!


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: smbclient from net/smbclient generates smbclient.gmon files

2010-02-14 Thread Rob Farmer 
On Sun, Feb 14, 2010 at 1:27 AM, barbara  wrote:
> During the recent massive port upgrades, I decided to uninstall net/samba3 
> and install net/smb-smbclient as I need just the client component.
> Now I've noticed that, every times I start smbclient, a file named 
> "smbclient.gmon" (about 2 mb), reported as "data" by file(1), is generated in 
> the CWD.
> I've no idea about what is that file and a search on google reported 0 
> results.
> This is pretty annoying because I'll get a copy of this file in every 
> directory where I start smbclient.
> This wasn't happening with smbclient built from net/samba3 and just before 
> the upgrade smb-smbclient has been updated from 3.0 to 3.4, so I'm wondering 
> if this behavior depends on the version or on the port (samba3* vs 
> samba-smbclient).
> But what really matters is how can it stop it creating this file?

There's a PR related to this (ports/143924) - it is a problem with the
port and hopefully will be fixed soon.

-- 
Rob Farmer

>
>
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>



-- 
Rob Farmer
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: smbclient from net/smbclient generates smbclient.gmon files

2010-02-14 Thread Matthew Seaman 
On 14/02/2010 09:27, barbara wrote:
> During the recent massive port upgrades, I decided to uninstall 
> net/samba3 and install net/smb-smbclient as I need just the client 
> component. Now I've noticed that, every times I start smbclient, a
> file named "smbclient.gmon" (about 2 mb), reported as "data" by
> file(1), is generated in the CWD. I've no idea about what is that
> file and a search on google reported 0 results. This is pretty
> annoying because I'll get a copy of this file in every directory
> where I start smbclient. This wasn't happening with smbclient built
> from net/samba3 and just before the upgrade smb-smbclient has been
> updated from 3.0 to 3.4, so I'm wondering if this behavior depends on
> the version or on the port (samba3* vs samba-smbclient). But what
> really matters is how can it stop it creating this file?

You've somehow got profiling turned on.  See gprof(1) for the full
details, but in short, what you are seeing is a record of what
functions are called in your application, how long is spent within each
function and the linkage between called and calling functions.  It is
of no conceivable use to you unless you are working on the development
of smbclient.

Profiling is turned on by adding -pg to the compiler flags when the
application is built. Check your /etc/make.conf for suspicious entries.
Eliminate wherever -pg comes from and rebuild smbclient to get rid of
the problem.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.  7 Priory Courtyard, Flat 3
Black Earth Consulting   Ramsgate
 Kent, CT11 9PW
Free and Open Source Solutions   Tel: +44 (0)1843 580647



signature.asc
Description: OpenPGP digital signature

Possibly unbuildable ports reminder

2010-02-14 Thread Bill Fenner 
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/po...@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
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

smbclient from net/smbclient generates smbclient.gmon files

2010-02-14 Thread barbara 
During the recent massive port upgrades, I decided to uninstall net/samba3 and 
install net/smb-smbclient as I need just the client component.
Now I've noticed that, every times I start smbclient, a file named 
"smbclient.gmon" (about 2 mb), reported as "data" by file(1), is generated in 
the CWD.
I've no idea about what is that file and a search on google reported 0 results.
This is pretty annoying because I'll get a copy of this file in every directory 
where I start smbclient.
This wasn't happening with smbclient built from net/samba3 and just before the 
upgrade smb-smbclient has been updated from 3.0 to 3.4, so I'm wondering if 
this behavior depends on the version or on the port (samba3* vs 
samba-smbclient).
But what really matters is how can it stop it creating this file?


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"