FYI clang fails to build ports argp-standalone

[Outback Dingo]

build on CURRENT Not sure if its appropriate here, but when trying to
get through a new glusterfs FYI clang fails to build ports
argp-standalone on CURRENT
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ports/net/click anyone ?

[Outback Dingo]

On Fri, Jul 1, 2011 at 1:41 PM, Luigi Rizzo  wrote:
> [Cc to ports@freebsd,org, but please followup at n...@freebsd.org]
>
> anyone interested in taking over maintainership of ports/net/click ?
> We have 1.5.0 in the tree, which is old and partly broken.

Luigi, coming back to an earlier email post you had on click
has someone taken maintainership, Id be willing since I am
using it in development areas, and belive it should be part of
the ports tree still
___
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: KDE3?

[Outback Dingo]

On Thu, Mar 3, 2011 at 12:47 PM, Heino Tiedemann
wrote:

> Tilman Keskinöz  wrote:
>
> > On 03/02/2011 05:26 PM, Heino Tiedemann wrote:
> >> is KDE3 "out"?
> >>
> >>
> >>  - misc/kdeutils3 (marked as IGNORE)
> >>
> >> or will it be compilable soon?
> >>
> >
> > Is there actually still interest in KDE3?
>
> at least me :)
>

you might be the sole surviving user


>
>
> > How about starting the removal of the coredesktop?
>
>
> ??
>
>
> ___
> 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"
>
___
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: Busybox update, call for testers on amd64

[Outback Dingo]

looks like the depency list might need work FreeBSD-HEAD 9 x86  fresh
install

pod2text: not found
gmake: [docs/BusyBox.txt] Error 127 (ignored)
  DOC busybox.1
pod2man: not found
gmake: [docs/busybox.1] Error 127 (ignored)
pod2html: not found
gmake: [docs/busybox.net/BusyBox.html] Error 127 (ignored)
  DOC BusyBox.html
cp: docs/busybox.net/BusyBox.html: No such file or directory
gmake: [docs/BusyBox.html] Error 1 (ignored)


On Fri, Jan 28, 2011 at 12:06 PM, Chris Rees  wrote:

> On 28 January 2011 05:27, Eygene Ryabinkin  wrote:
> > Chris, good day.
> >
> > Tue, Jan 25, 2011 at 07:18:56PM +, Chris Rees wrote:
> >> New patch to stop use of utmp.h when FEATURE_UTMP is off.
> >>
> >> Try these now (I tried them in my Tinderbox for 9-CURRENT, so they do
> >> work on i386)
> >
> > Works on my amd64/-CURRENT host.
>
>
> Thanks a lot.
>
> It's submitted as http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/154312
>
> Chris
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
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: Porting "ispconfig"

[Outback Dingo]

On Wed, Dec 22, 2010 at 10:20 AM, Jerry wrote:

> On Wed, 22 Dec 2010 09:15:02 -0500
> Outback Dingo  articulated:
>
> > On Wed, Dec 22, 2010 at 9:11 AM, Jerry
> > wrote:
> >
> > > I was looking to see if there was a port for "ispconfig"
> > > <http://www.ispconfig.org/> in the ports system. I was not able to
> > > locate one. Assuming that one doesn't exist, is anyone working on
> > > porting this to FreeBSD?
> >
> > actually youll probably want to look into ISPCP Omega, much better,
> > and does the same and runs on FreeBSD
>
> There is no existing port for that either as far as I can tell.
> Interesting though. I will give it a test run as soon as I get a chance.
>
> BTW, could you define "much better"?
>
> --
> Jerry ✌
> freebsd-ports.u...@seibercom.net
>



 
http://isp-control.net/documentation/doku.php?id=start:installation:freebsd
___
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: Porting "ispconfig"

[Outback Dingo]

On Wed, Dec 22, 2010 at 9:11 AM, Jerry wrote:

> I was looking to see if there was a port for "ispconfig"
>  in the ports system. I was not able to
> locate one. Assuming that one doesn't exist, is anyone working on
> porting this to FreeBSD?


actually youll probably want to look into ISPCP Omega, much better, and does
the same and runs on FreeBSD
___
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: Deluge Broken - error_already_set

[Outback Dingo]

yes, working to get it resolved

On Mon, Mar 15, 2010 at 10:05 PM, Chris Telting
wrote:

> Just wondering if anyone is working on it or knows how to fix it.
>
> I'm not sure if it's Deluge or the boost library.
>
> The port should be marked broken regardless.
>
>
> ___
> 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"
>
___
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: sqlite and tcl

[Outback Dingo]

Actually i question why the extra tcl is even required.

On Tue, Nov 10, 2009 at 10:03 AM, andrew clarke  wrote:

> On Tue 2009-11-10 15:51:11 UTC+0100, Alex Dupre (a...@freebsd.org) wrote:
>
> > As you have seen, the up-to-date sqlite port requires tcl for
> > *building*. A few of you complained about it, but I don't understand why
> > you are not complaining about ports that have perl or python configure
> > scripts, too ;-)
>
> In my case it was more a query about whether this new behaviour was
> correct, since TCL was required regardless of the TCLWRAPPER toggle in
> "make config", and I thought that was unusual.  I have no strong
> beliefs for or against TCL :-)
> ___
> 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"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: kde

[Outback Dingo]

try pkg_add -r kde3 i think their transitioning the tree for prep for kde4
also


On Fri, Apr 18, 2008 at 2:37 AM, Mike Nalls <[EMAIL PROTECTED]> wrote:

> Hello, I just loaded free BSD on another computer and when I try to use
> pkg_add -r kde to get the program, I recieve an "unable to fetch" error.  Do
> you have an easy installation script or other advice?  Thanks.  -Mike
>
>
>
>
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fprint (finger print sensor framework) port ready for testing

[Outback Dingo]

any luck on this ?

On Wed, Apr 16, 2008 at 2:43 AM, Simon Barner <[EMAIL PROTECTED]> wrote:

> Outback Dingo wrote:
> > pam_fprint works (see below) but when i try to run the fprint demo i get
> >
> > STATUS: No Devices Found
>
> Are you sure you have r/w access to the sensor's USB device?
> >
> > pam_fprint_enroll -f 7
> > This program will enroll your finger, unconditionally overwriting any
> selected
> > print that was enrolled previously. If you want to continue, press
> enter,
> > otherwise hit Ctrl+C
> >
> > Found device claimed by UPEK TouchStrip driver
> > Opened device. It's now time to enroll your finger.
> >
> > You will need to successfully scan your Right Index Finger 3 times to
> complete
> > the process.
> >
> > Scan your finger now.
> > upekts:error [read_msg] non-zero bytes in cmd response
> > upekts:error [read_msg28] expected response, got -1 seq=40
>
> Something seems to go wrong. I have never seenn this error message.
>
> Which sensor are you using? Can you send me the output of `usbdevs -vd'
> in a private mail please?
>
> --
> Best regards / Viele Grüße, [EMAIL PROTECTED]
>  Simon Barner[EMAIL PROTECTED]
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fprint (finger print sensor framework) port ready for testing

[Outback Dingo]

Yupp I even set the permissions 777 and added the user i tested to group
operator still no joy
ive used the upek port no problems even with GDM. the "root" user works
great, but regular users cant even register

ls -al /dev/ugen*
crw-rw-rw-  1 root  operator0,  84 Apr 15 14:14 /dev/ugen0
crw-rw-rw-  1 root  operator0,  85 Apr 15 14:14 /dev/ugen0.1
crw-rw-rw-  1 root  operator0,  86 Apr 15 14:14 /dev/ugen0.2
crw-rw-rw-  1 root  operator0,  87 Apr 15 14:14 /dev/ugen0.3
crw-rw-rw-  1 root  operator0,  88 Apr 15 14:14 /dev/ugen0.4
crwxrwxrwx  1 root  operator0,  89 Apr 15 14:14 /dev/ugen1
crwxrwxrwx  1 root  operator0,  90 Apr 15 14:14 /dev/ugen1.1
crwxrwxrwx  1 root  operator0,  91 Apr 16 01:34 /dev/ugen1.2
crwxrwxrwx  1 root  operator0,  92 Apr 15 14:14 /dev/ugen1.3

usbdevs -vd
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x),
Intel(0x), rev 1.00
  uhub0
 port 1 powered
 port 2 addr 2: low speed, power 98 mA, config 1, USB Receiver(0xc521),
Logitech(0x046d), rev 57.00
   ums0
   uhid0
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, UHCI root hub(0x),
Intel(0x), rev 1.00
  uhub1
 port 1 powered
 port 2 powered
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, UHCI root hub(0x),
Intel(0x), rev 1.00
  uhub2
 port 1 addr 2: full speed, self powered, config 1, BCM2045B(0x2110),
Broadcom Corp(0x0a5c), rev 1.00
   ugen0
 port 2 addr 3: full speed, power 100 mA, config 1, Biometric
Coprocessor(0x2016), STMicroelectronics(0x0483), rev 0.01
   ugen1
Controller /dev/usb3:
addr 1: full speed, self powered, config 1, UHCI root hub(0x),
Intel(0x), rev 1.00
  uhub3
 port 1 powered
 port 2 powered
Controller /dev/usb4:
addr 1: high speed, self powered, config 1, EHCI root hub(0x),
Intel(0x), rev 1.00
  uhub4
 port 1 powered
 port 2 powered
 port 3 powered
 port 4 powered
 port 5 powered
 port 6 powered
 port 7 powered
 port 8 powered




On Wed, Apr 16, 2008 at 2:43 AM, Simon Barner <[EMAIL PROTECTED]> wrote:

> Outback Dingo wrote:
> > pam_fprint works (see below) but when i try to run the fprint demo i get
> >
> > STATUS: No Devices Found
>
> Are you sure you have r/w access to the sensor's USB device?
> >
> > pam_fprint_enroll -f 7
> > This program will enroll your finger, unconditionally overwriting any
> selected
> > print that was enrolled previously. If you want to continue, press
> enter,
> > otherwise hit Ctrl+C
> >
> > Found device claimed by UPEK TouchStrip driver
> > Opened device. It's now time to enroll your finger.
> >
> > You will need to successfully scan your Right Index Finger 3 times to
> complete
> > the process.
> >
> > Scan your finger now.
> > upekts:error [read_msg] non-zero bytes in cmd response
> > upekts:error [read_msg28] expected response, got -1 seq=40
>
> Something seems to go wrong. I have never seenn this error message.
>
> Which sensor are you using? Can you send me the output of `usbdevs -vd'
> in a private mail please?
>
> --
> Best regards / Viele Grüße, [EMAIL PROTECTED]
>  Simon Barner[EMAIL PROTECTED]
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: fprint (finger print sensor framework) port ready for testing

[Outback Dingo]

pam_fprint works (see below) but when i try to run the fprint demo i get

STATUS: No Devices Found

pam_fprint_enroll -f 7
This program will enroll your finger, unconditionally overwriting any
selected print that was enrolled previously. If you want to continue, press
enter, otherwise hit Ctrl+C

Found device claimed by UPEK TouchStrip driver
Opened device. It's now time to enroll your finger.

You will need to successfully scan your Right Index Finger 3 times to
complete the process.

Scan your finger now.
upekts:error [read_msg] non-zero bytes in cmd response
upekts:error [read_msg28] expected response, got -1 seq=40
Enroll stage passed. Yay!

Scan your finger now.
Enroll stage passed. Yay!

Scan your finger now.
Enroll complete!
Enrollment completed!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Ports Request: OpenNMS

[Outback Dingo]

First thing to determine is if all the pices could actually be made to run
on freeBSd before even considering a port of it, has anyone gotten OpenNMS
to actually run on FreeBSD ?

On Sat, Apr 12, 2008 at 1:34 AM, Wesley Shields <[EMAIL PROTECTED]> wrote:

> On Fri, Apr 11, 2008 at 01:08:51PM -0500, Paul Schmehl wrote:
> > --On Friday, April 11, 2008 10:33:26 -0700 Mark Foster <[EMAIL PROTECTED]>
> wrote:
> >
> >> Paul Schmehl wrote:
> >>> If you're really serious that you want OpenNMS ported, then it's time
> >>> to make your contribution to FreeBSD.  :-)  Solicit help from other
> >>> FreeBSD users who use/want OpenNMS, and work together to distribute
> >>> the load and get the job done.  There's plenty of people on this list
> >>> who can help you when you run into problems.
> >>>
> >> I couldn't agree more!
> >> But for the last statement. I have to say I've been underwhelmed with
> the
> >> amount of maintainership support I have received from this
> >> ([EMAIL PROTECTED]) list. Perhaps it's just me, I know the ports-mgr
> are also
> >> very busy. Or in other cases the answer is just unknown.
> >> So, as a maintainer I tend to ask google before bugging the list. Is a
> >> dedicated maintainer-support list  something discussed before?
>
> If you're having a specific problem with a port you should ask the
> maintainer about it.  Maintainers are not _required_ to subscribe to
> this list, though it is a good idea.  If the port is unmaintained you
> will either have to ask her for help on what is going wrong or fix it
> yourself (sad, but true).  We try to be as helpful as possible here but
> you can't please everyone all the time.  :)
>
> > I think this *is* the dedicated maintainer-support list.  :-)
> >
> > It's been my experience that most of the questions I ask here are fairly
> > dumb and easily answered with a little research.  Perhaps that's why
> some
> > are slow to answer?  :-)
> >
> > I discussed, one time, on this list, updating the porting handbook to
> more
> > accurately describe the process, but that too requires some work and a
> PR,
> > so I just haven't gotten to it yet.  (Which I suspect is everyone's
> > problem.)
>
> The porter's handbook is a great resource, but it could certainly use
> some cleanup and better organization.  I'd be happy to work with anyone
> interested in brainstorming ideas and getting them implemented.  Either
> on a new thread or privately.
>
> > I try to help when I can, but I defer to more knowledgeable folks in
> most
> > cases.  I know that my porting skills have improved greatly since I
> first
> > started and *much* of what I've learned has come from other ports.  If
> you
> > want to know how to do a port, study the existing ports - especially
> ones
> > that are fairly complex, because those are *usually* done by very
> > knowledgeable people. (Mine are all relatively simple, mind you.)
>
> Yes, looking at existing ports is a great resource.  If they can't give
> you the right answer then asking here or Google will certainly get you
> the right answer.
>
> -- WXS
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"