FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
lang/guile  | 1.8.8   | 2.0.10
+-+
textproc/py-jaxml   | 3.02| 16.00
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
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] pkg 1.3.0 alpha1: Breath of fresh air from Kirov

[Baptiste Daroussin]

On Tue, Mar 18, 2014 at 01:57:51PM +1300, Andrew Thompson wrote:
> On 18 March 2014 06:21, Baptiste Daroussin  wrote:
> 
> > Hello,
> >
> > I'm really pleased to announce that the release process for the new major
> > version of pkg(8) has started with this first alpha1 release.
> >
> > The main feature for this release is the complete rework of the solver.
> > pkg(8) now features a real SAT solver and uses it for every operations
> > requested
> > by the user that may add, upgrade or remove packages.
> >
> >
> I am sure this has been discussed before but does this release do anything
> to help automating UPDATING or is this a planned feature?
> 
> Taking the last entry which says to "pkg set -o
> misc/p5-OSSP-uuid:misc/ossp-uuid-perl", just do it for me pkg!
> 
The new solver takes care of this without the need of pkg set -o :)
It would be now transparent for users. (all they might discover is that a
conflict is detected then a new pass in the solver is needed and and the
problems is solved properly by the removal of ossp-uuid-perl and installation of
p5-OSSP-uuid.

regards,
Bapt


pgpr2fmwsBvhq.pgp
Description: PGP signature

FreeBSD Port: textproc/apache-poi

[Liz pellettera]

___
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"

[QAT] 348530: 1x leftovers, 2x depend (??? in graphics/netpbm), 3x success

[Ports-QAT]

- Update to 2.18.2
-

  Build ID:  20140318101800-57662
  Job owner: g...@freebsd.org
  Buildtime: 59 minutes
  Enddate:   Tue, 18 Mar 2014 11:17:08 GMT

  Revision:  348530
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=348530

-

Port:print/lilypond 2.18.2

  Buildgroup: 10.0-QAT/amd64
  Buildstatus:   DEPEND (??? IN GRAPHICS/NETPBM)
  Log: 
https://qat.redports.org//~g...@freebsd.org/20140318101800-57662-303406/netpbm-10.35.89.log

  Buildgroup: 10.0-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~g...@freebsd.org/20140318101800-57662-303407/lilypond-2.18.2.log

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   DEPEND (??? IN GRAPHICS/NETPBM)
  Log: 
https://qat.redports.org//~g...@freebsd.org/20140318101800-57662-303408/netpbm-10.35.89.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~g...@freebsd.org/20140318101800-57662-303409/lilypond-2.18.2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~g...@freebsd.org/20140318101800-57662-303410/lilypond-2.18.2.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~g...@freebsd.org/20140318101800-57662-303411/lilypond-2.18.2.log


--
Buildarchive URL: 
redports 
___
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"

fully working rdp client

[Marko Cupać]

Hi,

I have a hard time working with RDP servers from FreeBSD 10-RELEASE.

I used remmina, but it appears to be broken at the moment:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/187140

I switched to freerdp, but the clipboard does not work:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/187474

I went back to rdesktop only to rediscover that clipboard works, but I
can't type some essential characters (like & {} etc.) in codepage
closest to mine (hr).

Are there any other options available?
-- 
Marko Cupać
___
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: fully working rdp client

[Andrea Venturoli]

On 03/18/14 12:31, Marko Cupać wrote:


I went back to rdesktop only to rediscover that clipboard works, but I
can't type some essential characters (like & {} etc.) in codepage
closest to mine (hr).


Did you pass option -k to it?

 bye
av.

___
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: fully working rdp client

[Marko Cupać]

On Tue, 18 Mar 2014 13:00:25 +0100
Andrea Venturoli  wrote:

> Did you pass option -k to it?

Yes, I am using -k hr, as there is no working switch for serbian
latin (the difference is only of political nature anyway).

Localized letters such as "čćžšđ" work fine. I also made a mistake
stating that "{}" do not work. Actually "<>" do not work, as well as
"%".
-- 
Marko Cupać
___
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"

[QAT] 348538: 2x leftovers, 4x success

[Ports-QAT]

New port: mod_proxy_uwsgi.
This is Apache2 proxy module to pass requests to uwsgi.
-

  Build ID:  20140318131600-23336
  Job owner: de...@freebsd.org
  Buildtime: 10 minutes
  Enddate:   Tue, 18 Mar 2014 13:25:45 GMT

  Revision:  348538
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=348538

-

Port:www/mod_proxy_uwsgi 2.0.3

  Buildgroup: 10.0-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~de...@freebsd.org/20140318131600-23336-303454/ap22-mod_proxy_uwsgi-2.0.3.log

  Buildgroup: 10.0-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~de...@freebsd.org/20140318131600-23336-303455/ap22-mod_proxy_uwsgi-2.0.3.log

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~de...@freebsd.org/20140318131600-23336-303456/ap22-mod_proxy_uwsgi-2.0.3.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~de...@freebsd.org/20140318131600-23336-303457/ap22-mod_proxy_uwsgi-2.0.3.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~de...@freebsd.org/20140318131600-23336-303458/ap22-mod_proxy_uwsgi-2.0.3.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~de...@freebsd.org/20140318131600-23336-303459/ap22-mod_proxy_uwsgi-2.0.3.log


--
Buildarchive URL: 
redports 
___
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"

net/samba36: ERROR: lock directory /var/run/samba/ does not exist

[O. Hartmann]

On CURRENT, I receive this error message when trying to start net/samba36:

ERROR: lock directory /var/run/samba/ does not exist

System: FreeBSD 11.0-CURRENT #1 r263252: Sun Mar 16 22:27:29 CET 2014 amd64

Filesystem /var/run is tmpfs and resides on a SSD!

I'm confused. Years ago, I had a similar problem with samba3[46] when I 
intriduced myself
to tmpfs-backed /var/run. The start-script of sambe residing in 
/usr/local/etc/rc.d/samba
wasn't capable of checking the existence of /var/run/samba so startup failed. 
in the
meanwhile, I thought this was fixed - the problem I report in is present 
somehow since
January, but I can not be more specific.

I deleted /usr/local/etc/rc.d/samba and reinstalled net/samba36. After 
reinstallation,
samba can be started on a regular basis. But after a reboot, it couldn't.

I have no clue what is happening here. Any suggestions?

Oliver


signature.asc
Description: PGP signature

Re: devel/doxygen: Need TeX help

[A.J. 'Fonz' van Werven]

Naram Qashat wrote:

>>> I basically get the following when it comes up to ./langhowto.tex:
>>>
>>>! LaTeX Error: Environment longtable undefined.
[snip]
>> It's probably not as simple as this, but I'll ask anyway: have you
>> tried the following?
>> # texconfig-sys rehash
>
> I hadn't tried that, but I did that just now and I still get the same
> error.
> Would've been nice if it had been that simple. :P

Bummer, sorry it didn't help. However, as you may have noticed I quoted
your entire message in my first reply and CC'ed it to the freebsd-tex@
mailing list. So hopefully someone on either list (the other being
freebsd-ports@) knows what else to try.

Furthermore: are you getting this error during building or during use? I
tried building devel/doxygen with PDF support and it built perfectly fine
here.

AvW

-- 
I'm not completely useless, I can be used as a bad example.


pgpy_pyecTkCq.pgp
Description: PGP signature

reason 23 why we've moved to linux

[Randy Bush]

/usr/ports# svn up
Updating '.':
Error validating server certificate for 'https://svn0.us-east.freebsd.org:443':
 - The certificate has an unknown error.
Certificate information:
 - Hostname: svnmir.ysv.FreeBSD.org
 - Valid: from Jul 29 22:01:21 2013 GMT until Dec 13 22:01:21 2040 GMT
 - Issuer: clusteradm, FreeBSD.org, CA, US(cluster...@freebsd.org)
 - Fingerprint: 1C:BD:85:95:11:9F:EB:75:A5:4B:C8:A3:FE:08:E4:02:73:06:1E:61
(R)eject or accept (t)emporarily? t
Error validating server certificate for 'https://svn0.us-east.freebsd.org:443':
 - The certificate has an unknown error.
Certificate information:
 - Hostname: svnmir.ysv.FreeBSD.org
 - Valid: from Jul 29 22:01:21 2013 GMT until Dec 13 22:01:21 2040 GMT
 - Issuer: clusteradm, FreeBSD.org, CA, US(cluster...@freebsd.org)
 - Fingerprint: 1C:BD:85:95:11:9F:EB:75:A5:4B:C8:A3:FE:08:E4:02:73:06:1E:61
(R)eject or accept (t)emporarily? t
Error validating server certificate for 'https://svn0.us-east.freebsd.org:443':
 - The certificate has an unknown error.
Certificate information:
 - Hostname: svnmir.ysv.FreeBSD.org
 - Valid: from Jul 29 22:01:21 2013 GMT until Dec 13 22:01:21 2040 GMT
 - Issuer: clusteradm, FreeBSD.org, CA, US(cluster...@freebsd.org)
 - Fingerprint: 1C:BD:85:95:11:9F:EB:75:A5:4B:C8:A3:FE:08:E4:02:73:06:1E:61
(R)eject or accept (t)emporarily?
___
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: reason 23 why we've moved to linux

[Alfred Perlstein]

Ugh, that's a mess, I haven't seen that personally, but I just tend to 
pull from git, although that takes a long time.


Using git lets me keep local changes easily.

The other option that works is just using portsnap.  I think "portsnap 
auto" or "portsnap alfred" should work for getting your the sources.


The other option would be just try a fresh checkout against 
https://svn.freebsd.org/ instead of https://svn0.us-east.freebsd.org/.


bummer!

lastly, just using "pkg(1)" works really nicely, if you're tired of 
dealing with port updates via source, then just try using pkg(1), it's 
basically just as nice as using "apt-get" these days, pretty nice stuff.


-Alfred


On 3/18/14, 9:42 AM, Randy Bush wrote:

/usr/ports# svn up
Updating '.':
Error validating server certificate for 'https://svn0.us-east.freebsd.org:443':
  - The certificate has an unknown error.
Certificate information:
  - Hostname: svnmir.ysv.FreeBSD.org
  - Valid: from Jul 29 22:01:21 2013 GMT until Dec 13 22:01:21 2040 GMT
  - Issuer: clusteradm, FreeBSD.org, CA, US(cluster...@freebsd.org)
  - Fingerprint: 1C:BD:85:95:11:9F:EB:75:A5:4B:C8:A3:FE:08:E4:02:73:06:1E:61
(R)eject or accept (t)emporarily? t
Error validating server certificate for 'https://svn0.us-east.freebsd.org:443':
  - The certificate has an unknown error.
Certificate information:
  - Hostname: svnmir.ysv.FreeBSD.org
  - Valid: from Jul 29 22:01:21 2013 GMT until Dec 13 22:01:21 2040 GMT
  - Issuer: clusteradm, FreeBSD.org, CA, US(cluster...@freebsd.org)
  - Fingerprint: 1C:BD:85:95:11:9F:EB:75:A5:4B:C8:A3:FE:08:E4:02:73:06:1E:61
(R)eject or accept (t)emporarily? t
Error validating server certificate for 'https://svn0.us-east.freebsd.org:443':
  - The certificate has an unknown error.
Certificate information:
  - Hostname: svnmir.ysv.FreeBSD.org
  - Valid: from Jul 29 22:01:21 2013 GMT until Dec 13 22:01:21 2040 GMT
  - Issuer: clusteradm, FreeBSD.org, CA, US(cluster...@freebsd.org)
  - Fingerprint: 1C:BD:85:95:11:9F:EB:75:A5:4B:C8:A3:FE:08:E4:02:73:06:1E:61
(R)eject or accept (t)emporarily?
___
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: reason 23 why we've moved to linux

[Randy Bush]

> Ugh, that's a mess, I haven't seen that personally, but I just tend to 
> pull from git, although that takes a long time.
> 
> Using git lets me keep local changes easily.
> 
> The other option that works is just using portsnap.  I think "portsnap 
> auto" or "portsnap alfred" should work for getting your the sources.
> 
> The other option would be just try a fresh checkout against 
> https://svn.freebsd.org/ instead of https://svn0.us-east.freebsd.org/.
> 
> bummer!
> 
> lastly, just using "pkg(1)" works really nicely, if you're tired of 
> dealing with port updates via source, then just try using pkg(1), it's 
> basically just as nice as using "apt-get" these days, pretty nice stuff.

alfred,

i know you mean well, but svn is legit and we have been using it until
the kiddies came over to freebsd from linux.  now that they left linux,
debian and ubuntu are quite usable, pretty stable, and the ports/package
system makes freebsd's look horrifying.  i am tired of dependency hell.
i am tired of package management du jour.  i have real work to do and
even an attempt at a real life.

i have been a bsd user since 4.whatever on the vax.  it is no longer
defensible in any situaion other than personal religion.  and it's the
ongoing ports disaster that has killed a really great system.  sad.

randy
___
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: net/samba36: ERROR: lock directory /var/run/samba/ does not exist

[Timur I. Bakeyev]

Hi, Oliver!

Please check in the rc.d/samba function samba_start_precmd(). It should
contain valid /var/run/samba path.

Is this problem occurs  only on restart(reboot) of the server? If you start
samba manually after the boot - does it run?

It could be, that in FreeBSD 11 rc order has changed somehow and samba
starts before /var/run is mounted. What does:

# rcorder /etc/rc.d/* /usr/local/etc.rc.d/*

say?

With regards,
Timur Bakeyev.


On Tue, Mar 18, 2014 at 3:11 PM, O. Hartmann wrote:

> On CURRENT, I receive this error message when trying to start net/samba36:
>
> ERROR: lock directory /var/run/samba/ does not exist
>
> System: FreeBSD 11.0-CURRENT #1 r263252: Sun Mar 16 22:27:29 CET 2014 amd64
>
> Filesystem /var/run is tmpfs and resides on a SSD!
>
> I'm confused. Years ago, I had a similar problem with samba3[46] when I
> intriduced myself
> to tmpfs-backed /var/run. The start-script of sambe residing in
> /usr/local/etc/rc.d/samba
> wasn't capable of checking the existence of /var/run/samba so startup
> failed. in the
> meanwhile, I thought this was fixed - the problem I report in is present
> somehow since
> January, but I can not be more specific.
>
> I deleted /usr/local/etc/rc.d/samba and reinstalled net/samba36. After
> reinstallation,
> samba can be started on a regular basis. But after a reboot, it couldn't.
>
> I have no clue what is happening here. Any suggestions?
>
> Oliver
>
___
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: net/samba36: ERROR: lock directory /var/run/samba/ does not exist

[O. Hartmann]

On Tue, 18 Mar 2014 18:13:20 +0100
"Timur I. Bakeyev"  wrote:

> Hi, Oliver!
> 
> Please check in the rc.d/samba function samba_start_precmd(). It should
> contain valid /var/run/samba path.

Checked - and it contains the propper path.

> 
> Is this problem occurs  only on restart(reboot) of the server? If you start
> samba manually after the boot - does it run?

It doesn't start on reboot, it starts on manauel issuing the command "service 
samba
start".

> 
> It could be, that in FreeBSD 11 rc order has changed somehow and samba
> starts before /var/run is mounted. What does:
> 
> # rcorder /etc/rc.d/* /usr/local/etc.rc.d/*

/etc/rc.d/sysctl
/etc/rc.d/hostid
/etc/rc.d/zvol
/etc/rc.d/dumpon
/etc/rc.d/ddb
/etc/rc.d/initrandom
/etc/rc.d/geli
/etc/rc.d/gbde
/etc/rc.d/ccd
/etc/rc.d/swap
/etc/rc.d/fsck
/etc/rc.d/root
/etc/rc.d/mdconfig
/etc/rc.d/hostid_save
/etc/rc.d/mountcritlocal
/etc/rc.d/zfs
/etc/rc.d/var
/etc/rc.d/cleanvar
/etc/rc.d/FILESYSTEMS
/etc/rc.d/kldxref
/etc/rc.d/kld
/etc/rc.d/addswap
/etc/rc.d/random
/etc/rc.d/postrandom
/etc/rc.d/adjkerntz
/etc/rc.d/atm1
/etc/rc.d/hostname
/etc/rc.d/ip6addrctl
/etc/rc.d/netoptions
/etc/rc.d/sppp
/etc/rc.d/ipfilter
/etc/rc.d/ipnat
/etc/rc.d/ipfs
/etc/rc.d/serial
/etc/rc.d/netif
/etc/rc.d/devd
/etc/rc.d/ipsec
/etc/rc.d/atm2
/etc/rc.d/pfsync
/etc/rc.d/pflog
/etc/rc.d/pf
/etc/rc.d/stf
/etc/rc.d/ppp
/etc/rc.d/faith
/etc/rc.d/routing
/etc/rc.d/mroute6d
/etc/rc.d/nsswitch
/etc/rc.d/rtsold
/etc/rc.d/resolv
/etc/rc.d/local_unbound
/etc/rc.d/static_ndp
/etc/rc.d/static_arp
/etc/rc.d/bridge
/etc/rc.d/route6d
/etc/rc.d/mrouted
/etc/rc.d/routed
/etc/rc.d/defaultroute
/etc/rc.d/ipfw
/etc/rc.d/NETWORKING
/etc/rc.d/netwait
/etc/rc.d/mountcritremote
/etc/rc.d/newsyslog
/etc/rc.d/syslogd
/etc/rc.d/ntpdate
/etc/rc.d/rpcbind
/etc/rc.d/devfs
/etc/rc.d/ipmon
/etc/rc.d/mdconfig2
/etc/rc.d/watchdogd
/etc/rc.d/savecore
/etc/rc.d/ldconfig
/etc/rc.d/archdep
/etc/rc.d/abi
/etc/rc.d/SERVERS
/etc/rc.d/nisdomain
/etc/rc.d/ypserv
/etc/rc.d/ypxfrd
/etc/rc.d/ypupdated
/etc/rc.d/ypbind
/etc/rc.d/ypset
/etc/rc.d/yppasswdd
/etc/rc.d/wpa_supplicant
/etc/rc.d/virecover
/etc/rc.d/accounting
/etc/rc.d/nfsclient
/etc/rc.d/amd
/etc/rc.d/atm3
/etc/rc.d/auditd
/etc/rc.d/auditdistd
/etc/rc.d/casperd
/etc/rc.d/tmp
/etc/rc.d/cleartmp
/etc/rc.d/ctld
/etc/rc.d/dmesg
/etc/rc.d/hastd
/etc/rc.d/iscsid
/etc/rc.d/iscsictl
/etc/rc.d/kerberos
/etc/rc.d/kadmind
/etc/rc.d/keyserv
/etc/rc.d/kpasswdd
/etc/rc.d/nfsuserd
/etc/rc.d/gssd
/etc/rc.d/quota
/etc/rc.d/mountd
/etc/rc.d/nfsd
/etc/rc.d/statd
/etc/rc.d/lockd
/etc/rc.d/pppoed
/etc/rc.d/pwcheck
/etc/rc.d/DAEMON
/etc/rc.d/utx
/etc/rc.d/ugidfw
/etc/rc.d/ubthidhci
/etc/rc.d/timed
/etc/rc.d/apm
/etc/rc.d/apmd
/etc/rc.d/bootparams
/etc/rc.d/hcsecd
/etc/rc.d/bthidd
/etc/rc.d/local
/etc/rc.d/lpd
/etc/rc.d/motd
/etc/rc.d/mountlate
/etc/rc.d/nscd
/etc/rc.d/ntpd
/etc/rc.d/powerd
/etc/rc.d/rarpd
/etc/rc.d/rctl
/etc/rc.d/sdpd
/etc/rc.d/rfcomm_pppd_server
/etc/rc.d/rtadvd
/etc/rc.d/rwho
/etc/rc.d/LOGIN
/etc/rc.d/syscons
/etc/rc.d/swaplate
/etc/rc.d/sshd
/etc/rc.d/sendmail
/etc/rc.d/cron
/etc/rc.d/jail
/etc/rc.d/localpkg
/etc/rc.d/securelevel
/etc/rc.d/power_profile
/etc/rc.d/othermta
/etc/rc.d/nfscbd
/etc/rc.d/natd
/etc/rc.d/msgs
/etc/rc.d/moused
/etc/rc.d/mixer
/etc/rc.d/kfd
/etc/rc.d/inetd
/etc/rc.d/hostapd
/etc/rc.d/gptboot
/etc/rc.d/geli2
/etc/rc.d/ftpd
/etc/rc.d/ftp-proxy
/etc/rc.d/dhclient
/etc/rc.d/bsnmpd
/etc/rc.d/bluetooth
/etc/rc.d/bgfsck


> 
> say?
> 
> With regards,
> Timur Bakeyev.
> 
> 
> On Tue, Mar 18, 2014 at 3:11 PM, O. Hartmann 
> wrote:
> 
> > On CURRENT, I receive this error message when trying to start net/samba36:
> >
> > ERROR: lock directory /var/run/samba/ does not exist
> >
> > System: FreeBSD 11.0-CURRENT #1 r263252: Sun Mar 16 22:27:29 CET 2014 amd64
> >
> > Filesystem /var/run is tmpfs and resides on a SSD!
> >
> > I'm confused. Years ago, I had a similar problem with samba3[46] when I
> > intriduced myself
> > to tmpfs-backed /var/run. The start-script of sambe residing in
> > /usr/local/etc/rc.d/samba
> > wasn't capable of checking the existence of /var/run/samba so startup
> > failed. in the
> > meanwhile, I thought this was fixed - the problem I report in is present
> > somehow since
> > January, but I can not be more specific.
> >
> > I deleted /usr/local/etc/rc.d/samba and reinstalled net/samba36. After
> > reinstallation,
> > samba can be started on a regular basis. But after a reboot, it couldn't.
> >
> > I have no clue what is happening here. Any suggestions?
> >
> > Oliver
> >




signature.asc
Description: PGP signature

pkg_replace and detecting pkg(ng)

[Michael Gmelin]

Hi,

In the past I've been able to use pkg_replace on machine that didn't
have the ports collection installed.

With the current version of pkg_replace this doesn't seem to be
possible anymore, since pkg(ng) detection breaks in those cases:

: ${use_pkgng="`/usr/bin/make -f/usr/share/mk/bsd.port.mk -V
WITH_PKGNG`"}
if [ "x${use_pkgng}" = "xdevel" ]; then
  use_pkgng="yes"
fi

bsd.port.mk requires /usr/ports/Mk/...

One of the main motivations to use pkg_replace for me is to not having
a ports tree on the machines I use it on.

I would suggest to replace this with a detection mechanism similar to
what ports does:

If sysctl -n kern.osreldate >= 117
 use_pkgng=yes, unless WITHOUT_PKGNG is defined
else if defined(WITH_PKGNG) (any value, not just ==yes)
 use_pkgng=yes
else
 use_pkgng=no

Determining WITH_PKGNG/WITHOUT_PKGNG should be done using make -V VAR
(without specifying a Makefile, so /etc/make.conf is read).

- Michael

-- 
Michael Gmelin
___
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: net/samba36: ERROR: lock directory /var/run/samba/ does not exist

[Timur I. Bakeyev]

Sorry, I made a typo:

 rcorder /etc/rc.d/* /usr/local/etc/rc.d/*

You can check yourself - see, where samba in that output relative to... Hm,
what would start your /var/run - /etc/rc.d/var I guess?


On Tue, Mar 18, 2014 at 6:33 PM, O. Hartmann wrote:

> On Tue, 18 Mar 2014 18:13:20 +0100
> "Timur I. Bakeyev"  wrote:
>
> > Hi, Oliver!
> >
> > Please check in the rc.d/samba function samba_start_precmd(). It should
> > contain valid /var/run/samba path.
>
> Checked - and it contains the propper path.
>
> >
> > Is this problem occurs  only on restart(reboot) of the server? If you
> start
> > samba manually after the boot - does it run?
>
> It doesn't start on reboot, it starts on manauel issuing the command
> "service samba
> start".
>
> >
> > It could be, that in FreeBSD 11 rc order has changed somehow and samba
> > starts before /var/run is mounted. What does:
> >
> > # rcorder /etc/rc.d/* /usr/local/etc.rc.d/*
>
> /etc/rc.d/sysctl
> /etc/rc.d/hostid
> /etc/rc.d/zvol
> /etc/rc.d/dumpon
> /etc/rc.d/ddb
> /etc/rc.d/initrandom
> /etc/rc.d/geli
> /etc/rc.d/gbde
> /etc/rc.d/ccd
> /etc/rc.d/swap
> /etc/rc.d/fsck
> /etc/rc.d/root
> /etc/rc.d/mdconfig
> /etc/rc.d/hostid_save
> /etc/rc.d/mountcritlocal
> /etc/rc.d/zfs
> /etc/rc.d/var
> /etc/rc.d/cleanvar
> /etc/rc.d/FILESYSTEMS
> /etc/rc.d/kldxref
> /etc/rc.d/kld
> /etc/rc.d/addswap
> /etc/rc.d/random
> /etc/rc.d/postrandom
> /etc/rc.d/adjkerntz
> /etc/rc.d/atm1
> /etc/rc.d/hostname
> /etc/rc.d/ip6addrctl
> /etc/rc.d/netoptions
> /etc/rc.d/sppp
> /etc/rc.d/ipfilter
> /etc/rc.d/ipnat
> /etc/rc.d/ipfs
> /etc/rc.d/serial
> /etc/rc.d/netif
> /etc/rc.d/devd
> /etc/rc.d/ipsec
> /etc/rc.d/atm2
> /etc/rc.d/pfsync
> /etc/rc.d/pflog
> /etc/rc.d/pf
> /etc/rc.d/stf
> /etc/rc.d/ppp
> /etc/rc.d/faith
> /etc/rc.d/routing
> /etc/rc.d/mroute6d
> /etc/rc.d/nsswitch
> /etc/rc.d/rtsold
> /etc/rc.d/resolv
> /etc/rc.d/local_unbound
> /etc/rc.d/static_ndp
> /etc/rc.d/static_arp
> /etc/rc.d/bridge
> /etc/rc.d/route6d
> /etc/rc.d/mrouted
> /etc/rc.d/routed
> /etc/rc.d/defaultroute
> /etc/rc.d/ipfw
> /etc/rc.d/NETWORKING
> /etc/rc.d/netwait
> /etc/rc.d/mountcritremote
> /etc/rc.d/newsyslog
> /etc/rc.d/syslogd
> /etc/rc.d/ntpdate
> /etc/rc.d/rpcbind
> /etc/rc.d/devfs
> /etc/rc.d/ipmon
> /etc/rc.d/mdconfig2
> /etc/rc.d/watchdogd
> /etc/rc.d/savecore
> /etc/rc.d/ldconfig
> /etc/rc.d/archdep
> /etc/rc.d/abi
> /etc/rc.d/SERVERS
> /etc/rc.d/nisdomain
> /etc/rc.d/ypserv
> /etc/rc.d/ypxfrd
> /etc/rc.d/ypupdated
> /etc/rc.d/ypbind
> /etc/rc.d/ypset
> /etc/rc.d/yppasswdd
> /etc/rc.d/wpa_supplicant
> /etc/rc.d/virecover
> /etc/rc.d/accounting
> /etc/rc.d/nfsclient
> /etc/rc.d/amd
> /etc/rc.d/atm3
> /etc/rc.d/auditd
> /etc/rc.d/auditdistd
> /etc/rc.d/casperd
> /etc/rc.d/tmp
> /etc/rc.d/cleartmp
> /etc/rc.d/ctld
> /etc/rc.d/dmesg
> /etc/rc.d/hastd
> /etc/rc.d/iscsid
> /etc/rc.d/iscsictl
> /etc/rc.d/kerberos
> /etc/rc.d/kadmind
> /etc/rc.d/keyserv
> /etc/rc.d/kpasswdd
> /etc/rc.d/nfsuserd
> /etc/rc.d/gssd
> /etc/rc.d/quota
> /etc/rc.d/mountd
> /etc/rc.d/nfsd
> /etc/rc.d/statd
> /etc/rc.d/lockd
> /etc/rc.d/pppoed
> /etc/rc.d/pwcheck
> /etc/rc.d/DAEMON
> /etc/rc.d/utx
> /etc/rc.d/ugidfw
> /etc/rc.d/ubthidhci
> /etc/rc.d/timed
> /etc/rc.d/apm
> /etc/rc.d/apmd
> /etc/rc.d/bootparams
> /etc/rc.d/hcsecd
> /etc/rc.d/bthidd
> /etc/rc.d/local
> /etc/rc.d/lpd
> /etc/rc.d/motd
> /etc/rc.d/mountlate
> /etc/rc.d/nscd
> /etc/rc.d/ntpd
> /etc/rc.d/powerd
> /etc/rc.d/rarpd
> /etc/rc.d/rctl
> /etc/rc.d/sdpd
> /etc/rc.d/rfcomm_pppd_server
> /etc/rc.d/rtadvd
> /etc/rc.d/rwho
> /etc/rc.d/LOGIN
> /etc/rc.d/syscons
> /etc/rc.d/swaplate
> /etc/rc.d/sshd
> /etc/rc.d/sendmail
> /etc/rc.d/cron
> /etc/rc.d/jail
> /etc/rc.d/localpkg
> /etc/rc.d/securelevel
> /etc/rc.d/power_profile
> /etc/rc.d/othermta
> /etc/rc.d/nfscbd
> /etc/rc.d/natd
> /etc/rc.d/msgs
> /etc/rc.d/moused
> /etc/rc.d/mixer
> /etc/rc.d/kfd
> /etc/rc.d/inetd
> /etc/rc.d/hostapd
> /etc/rc.d/gptboot
> /etc/rc.d/geli2
> /etc/rc.d/ftpd
> /etc/rc.d/ftp-proxy
> /etc/rc.d/dhclient
> /etc/rc.d/bsnmpd
> /etc/rc.d/bluetooth
> /etc/rc.d/bgfsck
>
>
> >
> > say?
> >
> > With regards,
> > Timur Bakeyev.
> >
> >
> > On Tue, Mar 18, 2014 at 3:11 PM, O. Hartmann <
> ohart...@zedat.fu-berlin.de>wrote:
> >
> > > On CURRENT, I receive this error message when trying to start
> net/samba36:
> > >
> > > ERROR: lock directory /var/run/samba/ does not exist
> > >
> > > System: FreeBSD 11.0-CURRENT #1 r263252: Sun Mar 16 22:27:29 CET 2014
> amd64
> > >
> > > Filesystem /var/run is tmpfs and resides on a SSD!
> > >
> > > I'm confused. Years ago, I had a similar problem with samba3[46] when I
> > > intriduced myself
> > > to tmpfs-backed /var/run. The start-script of sambe residing in
> > > /usr/local/etc/rc.d/samba
> > > wasn't capable of checking the existence of /var/run/samba so startup
> > > failed. in the
> > > meanwhile, I thought this was fixed - the problem I report in is
> present
> > > somehow since
> > > January, but I can not be more specific.
> > >
> > > I deleted /usr/local/etc/

Re: reason 23 why we've moved to linux

[Alfred Perlstein]

On 3/18/14, 9:56 AM, Randy Bush wrote:

Ugh, that's a mess, I haven't seen that personally, but I just tend to
pull from git, although that takes a long time.

Using git lets me keep local changes easily.

The other option that works is just using portsnap.  I think "portsnap
auto" or "portsnap alfred" should work for getting your the sources.

The other option would be just try a fresh checkout against
https://svn.freebsd.org/ instead of https://svn0.us-east.freebsd.org/.

bummer!

lastly, just using "pkg(1)" works really nicely, if you're tired of
dealing with port updates via source, then just try using pkg(1), it's
basically just as nice as using "apt-get" these days, pretty nice stuff.

alfred,

i know you mean well, but svn is legit and we have been using it until
the kiddies came over to freebsd from linux.  now that they left linux,
debian and ubuntu are quite usable, pretty stable, and the ports/package
system makes freebsd's look horrifying.  i am tired of dependency hell.
i am tired of package management du jour.  i have real work to do and
even an attempt at a real life.

i have been a bsd user since 4.whatever on the vax.  it is no longer
defensible in any situaion other than personal religion.  and it's the
ongoing ports disaster that has killed a really great system.  sad.

randy

I see what you're getting at, however I see a different picture with 
FreeBSD moving forward at a quick pace to close the gap in package 
management between itself and the Linux distros.


I myself was initially upset, however as the changes have kept coming I 
am more and more impressed and thrilled with the effort put in.  The 
changes by the ports+pkgng team have really come together to make a 
great product.


I think we can agree that the past 6 months have been interesting and 
challenging, however more importantly they have been necessary growing 
pains that we have just now passed.


If you want to vent, great, I hear you, but let's be honest about the 
state of things and not conflate with some weird transient issue with 
svn with the project coming apart at the seams, that would just be 
hyperbolic and not serve us any purpose.


-Alfred

___
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"

mail/thunderbird dependency on mercurial

[Mars G. Miro]

Hi,

It seems that thunderbird 24.3.0 now needs mercurial, otherwise it'll
fail on the build. I don't know if it really does an hg pull but a diff
between this and the previous version has something like :

+

-# Do a cvs pull of NSS
+# Do a HG pull of NSS
 

-cvs_pull()
+hg_pull()
 {
-# Tested NSS - by default using current CVS HEAD
+# Tested NSS - by default using HG default tip
 if [ "$NO_BUILD_TEST" = "false" ]; then
-echo "cloning NSS sources to be tested from CVS"
+echo "cloning NSS sources to be tested from HG"
 [ ! -d "$LOCALDIST" ] && mkdir -p "$LOCALDIST"
 cd "$LOCALDIST"
-cvs -d :pserver:anonym...@cvs-mirror.mozilla.org:/cvsroot co -r
HEAD NSPR &>> $TEST_OUTPUT/nisccBuildLog
-cvs -d :pserver:anonym...@cvs-mirror.mozilla.org:/cvsroot co -r
HEAD NSS &>> $TEST_OUTPUT/nisccBuildLog
+[ ! -d "$LOCALDIST/nspr" ] && hg clone --noupdate
https://hg.mozilla.org/projects/nspr
+cd nspr; hg pull; hg update -C -r default; cd ..
+[ ! -d "$LOCALDIST/nss" ] && hg clone --noupdate
https://hg.mozilla.org/projects/nss
+cd nss; hg pull; hg update -C -r default; cd ..
 #find . -exec touch {} \;
 fi


-- 
If society fits you comfortably enough, you call it freedom.
-- Robert Frost
___
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: devel/doxygen: Need TeX help

[Naram Qashat]

On 03/18/14 11:56, A.J. 'Fonz' van Werven wrote:

Naram Qashat wrote:


I basically get the following when it comes up to ./langhowto.tex:

! LaTeX Error: Environment longtable undefined.

[snip]

It's probably not as simple as this, but I'll ask anyway: have you
tried the following?
# texconfig-sys rehash


I hadn't tried that, but I did that just now and I still get the same
error.
Would've been nice if it had been that simple. :P


Bummer, sorry it didn't help. However, as you may have noticed I quoted
your entire message in my first reply and CC'ed it to the freebsd-tex@
mailing list. So hopefully someone on either list (the other being
freebsd-ports@) knows what else to try.

Furthermore: are you getting this error during building or during use? I
tried building devel/doxygen with PDF support and it built perfectly fine
here.

AvW


It was during building. The port is currently at 1.8.3.1, and I actually ran 
into the problem in the email when I initially was trying to update to 1.8.4. 
That was the main reason I haven't pushed out an update to the port yet.


Oddly enough, when I try to build 1.8.3.1 on my machine currently, I also get a 
TeX error, but an entirely different one. I can't recall what the error was, but 
it had nothing to do with longtable.


Thanks,
Naram Qashat
___
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"

Plex Media Server Port issues

[Kaya Saman]

Hi,

I'm experiencing 3 issues with the Plex Media Server

My configuration is running FreeBSD 10.0 x64 with the ports tree up to date.

Issue 1: Upon first installing the port everything went fine however, 
PMS wouldn't start and kept complaining about a Python C Lang issue... 
Google'ing  I managed to find a FreeBSD Forum posting stating to insert 
this line:


#!/bin/sh
export LD_LIBMAP="/lib/libc.so.7 /usr/local/share/plexmediaserver/libc.so.7"


in the start.sh file located in: /usr/local/share/plexmediaserver


In addition I had to comment out these two lines:

#export LC_ALL="en_US.UTF-8"
#export LANG="en_US.UTF-8"

in the start.sh file.


Issue 2: As I'm running PMS in a Jail on a headless server, for some 
reason the rc script doesn't start properly?? This is quite weird...


Using an SSH tunnel running: service plexmediaserver start or the 
/usr/local/etc/rc.d/plexmediaserver start method, not all services seem 
to come up properly.


Running ./start.sh sometimes works but not all.


I managed to find the solution in running: service plexmediaserver start 
from Xterm using a VNC server/client - tightvnc on the FBSD jail while 
GTK-VNC on my Linux desktop.


Probably linked in with this is that not VNC'ing leaves me unable to 
login at the web interface. Putting my Plex ID/passwd combo in doesn't 
do a thing.


The VNC method allows me unconditional access with no login prompts or 
anything.



I have customized the Preferences.xml file in /usr/local/plexdata to 
allow local-subnets access in any case so this issue is simply just odd!



Issue 3: For some reason the DLNA server doesn't work properly

Though it does show up as online using ps:

plex  89291  0.0  0.2 139844 17808  -  SJ   10:40PM 0:00.15 
/usr/local/share/plexmediaserver/Plex DLNA Server


It doesn't seem to broadcast itself.

I'm running a few uPNP clients on Android which I like to test 
connectivity with though I have the official Plex app installed too, but 
none of them see the server?


Running XBMC or the Playstation3 Media Server on my Linux Desktop is 
fine as the phone sees those without any issue.


Since I have my networks in separate vlans I'm running IGMPProxy on my 
router to enable cross-network igmp communication. It works fine and the 
config is totally correct; using tcpdump I can even see traffic being 
broadcast between both the Android and the Plex server to: 
239.255.255.250 (uPNP/DLNA multicast address) but the phone simply 
doesn't see the server??



I don't know if this is a Plex issue in itself or something that just 
simply needs patching in the port but for now one really needs to 
wrestle with the service to get it to work properly.



I wonder if anyone has any ideas to resolve the above?


Regards,


Kaya
___
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"

dante 1.3.2

[Carlos Fernando Assis Paniago]

This is the log of dante version 1.3.2 in 
# uname -a 
FreeBSD gw-ext.cnptia.embrapa.br 10.0-STABLE FreeBSD 10.0-STABLE #0: Thu Mar 13 
09:04:14 BRT 2014 
r...@gw-ext.cnptia.embrapa.br:/usr/src/sys/amd64/compile/GW-EXT amd64 

--- 
Mar 18 20:25:22 (1395185122.137041) sockd[87500]: error: symbolfunction(): 
compile time configuration error? Failed to find "_gethostbyname" using 
RTLD_NEXT: Undefined symbol "_gethostbyname" 
Mar 18 20:25:22 (1395185122.137164) sockd[87500]: alert: sockdexit(): 
terminating 
Mar 18 20:25:22 (1395185122.137201) sockd[87500]: warning: sockdexit(): 
truncate(/var/run/sockd.pid): No such file or directory (errno = 2) 
-- 

Someone know how to fix it? socksify is not working either with the message: 

ntid003: {1046} socksify ssh -X -Y -C panix.homeunix.org 
socksify: error: dante client not built with preloading support. 
ntid003: {1047} 

It worked before 

Paniago 

-- 

Carlos Fernando Assis Paniago 

Núcleo de Tecnologia da Informação 
Embrapa Informática Agropecuária 
Fone: +55(19)3211-5815 
fone@RNP: 55(19)1221-6000 
INOC-DBA: 11097*100 
http://www.cnptia.embrapa.br 



Aviso de confidencialidade 

Esta mensagem da Empresa  Brasileira de Pesquisa  Agropecuaria  (Embrapa),
empresa publica federal  regida pelo disposto  na Lei Federal no. 5.851,  de
7 de dezembro de 1972,  e  enviada exclusivamente  a seu destinatario e pode
conter informacoes  confidenciais, protegidas  por sigilo profissional.  Sua
utilizacao desautorizada  e ilegal e  sujeita o infrator as penas da lei. Se
voce  a recebeu indevidamente, queira, por gentileza, reenvia-la ao emitente,
esclarecendo o equivoco.

Confidentiality note

This message from Empresa  Brasileira de Pesquisa  Agropecuaria  (Embrapa), a
government company  established under  Brazilian law  (5.851/72), is directed
exclusively to  its addressee  and may contain  confidential data,  protected
under  professional secrecy  rules. Its unauthorized  use is illegal and  may
subject the transgressor to the law's penalties. If you are not the addressee,
please send it back, elucidating the failure.



___
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"

[QAT] 348583: 6x leftovers

[Ports-QAT]

New port: devel/p5-RPSL-Parser:

This is a rather simplistic lexer and tokenizer for the RPSL language.

It currently does not validate the object in any way, it just tries
(rather hard) to grab the biggest ammount of information it can from the
text presented and place it in a Parse Tree (that can be passed to other
objects from the RPSL namespace for validation and more RFC2622 related
functionality).

WWW: http://search.cpan.org/dist/RPSL-Parser/
-

  Build ID:  20140318175601-25782
  Job owner: z...@freebsd.org
  Buildtime: 6 hours
  Enddate:   Tue, 18 Mar 2014 23:46:58 GMT

  Revision:  348583
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=348583

-

Port:devel/p5-RPSL-Parser 0.04000

  Buildgroup: 10.0-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~z...@freebsd.org/20140318175601-25782-304084/p5-RPSL-Parser-0.04000.log

  Buildgroup: 10.0-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~z...@freebsd.org/20140318175601-25782-304085/p5-RPSL-Parser-0.04000.log

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~z...@freebsd.org/20140318175601-25782-304086/p5-RPSL-Parser-0.04000.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~z...@freebsd.org/20140318175601-25782-304087/p5-RPSL-Parser-0.04000.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~z...@freebsd.org/20140318175601-25782-304088/p5-RPSL-Parser-0.04000.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~z...@freebsd.org/20140318175601-25782-304089/p5-RPSL-Parser-0.04000.log


--
Buildarchive URL: 
redports 
___
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: Plex Media Server Port issues

[Waitman Gobble]

On 3/18/2014 4:36 PM, Kaya Saman wrote:

Hi,

I'm experiencing 3 issues with the Plex Media Server

My configuration is running FreeBSD 10.0 x64 with the ports tree up to 
date.


Issue 1: Upon first installing the port everything went fine however, 
PMS wouldn't start and kept complaining about a Python C Lang issue... 
Google'ing  I managed to find a FreeBSD Forum posting stating to 
insert this line:


#!/bin/sh
export LD_LIBMAP="/lib/libc.so.7 
/usr/local/share/plexmediaserver/libc.so.7"






I don't recall using Plex Media Server however I think you are missing 
something in your LD_LIBMAP.. like an equal sign, instead of the space.. 
ie libc.so.7=the other libc.so.7



--
Waitman Gobble
San Jose California USA

___
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"

[QAT] 348590: 2x leftovers, 4x success

[Ports-QAT]

Fix LIB_DEPENDS

Reported by:pkg-fallout
-

  Build ID:  20140318185800-20600
  Job owner: anto...@freebsd.org
  Buildtime: 5 hours
  Enddate:   Wed, 19 Mar 2014 00:09:02 GMT

  Revision:  348590
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=348590

-

Port:japanese/ibus-anthy 1.2.7_3,1

  Buildgroup: 10.0-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140318185800-20600-304126/ja-ibus-anthy-1.2.7_3,1.log

  Buildgroup: 10.0-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140318185800-20600-304127/ja-ibus-anthy-1.2.7_3,1.log

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140318185800-20600-304128/ja-ibus-anthy-1.2.7_3,1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140318185800-20600-304129/ja-ibus-anthy-1.2.7_3,1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140318185800-20600-304130/ja-ibus-anthy-1.2.7_3,1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~anto...@freebsd.org/20140318185800-20600-304131/ja-ibus-anthy-1.2.7_3,1.log


--
Buildarchive URL: 
redports 
___
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"

Problem installing dri 9.1.7_3,2

[sindrome]

 

Here's my current system

 

FreeBSD foo.bar.net 9.1-STABLE FreeBSD 9.1-STABLE #1 r250333: Tue May  7
22:30:37 CDT 2013 f...@foo.bar.net:/usr/obj/usr/src/sys/FOO  amd64

 

I am trying to install dri 9.1.7_3,2 and am getting the following errors

 

 

gmake  all-am

gmake[3]: Entering directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/mapi/glapi/gen'

gmake[3]: Nothing to be done for `all-am'.

gmake[3]: Leaving directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/mapi/glapi/gen'

gmake[2]: Leaving directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/mapi/glapi/gen'

Making all in mapi/glapi

gmake[2]: Entering directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/mapi/glapi'

  CC   glapi_dispatch.lo

  CC   glapi_entrypoint.lo

clang: warning: argument unused during compilation:
'-fno-builtin-memcmp'clang: warning: argument unused during compilation:
'-fno-builtin-memcmp'

 

  CC   glapi_gentable.lo

clang: warning: argument unused during compilation: '-fno-builtin-memcmp'

In file included from glapi_dispatch.c:90:

../../../src/mapi/glapi/glapitemp.h:7559:55: warning: passing 'const GLvoid
*const *' (aka 'const void *const *') to

  parameter of type 'const GLvoid **' (aka 'const void **') discards
qualifiers [-Wincompatible-pointer-types]

   DISPATCH(MultiDrawElementsEXT, (mode, count, type, indices, primcount),
(F, "glMultiDrawElements(0x%x, %p,...

  ^~~

glapi_dispatch.c:74:25: note: expanded from macro 'DISPATCH'

   GET_DISPATCH()->FUNC ARGS

^

1 warning generated.

  CC   glapi_getproc.lo

clang: warning: argument unused during compilation: '-fno-builtin-memcmp'

  CC   glapi_nop.lo

clang: warning: argument unused during compilation: '-fno-builtin-memcmp'

  CC   glthread.lo

clang: warning: argument unused during compilation: '-fno-builtin-memcmp'

  CC   glapi.lo

clang: warning: argument unused during compilation: '-fno-builtin-memcmp'

  CC   u_current.lo

clang: warning: argument unused during compilation: '-fno-builtin-memcmp'

  CC   u_execmem.lo

clang: warning: argument unused during compilation: '-fno-builtin-memcmp'

  CCLD libglapi.la

gmake[2]: Leaving directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/mapi/glapi'

Making all in gtest

gmake[2]: Entering directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/gtest'

gmake[2]: Nothing to be done for `all'.

gmake[2]: Leaving directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/gtest'

Making all in glsl

gmake[2]: Entering directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/glsl'

gmake  all-recursive

gmake[3]: Entering directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/glsl'

Making all in builtin_compiler

gmake[4]: Entering directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/glsl/builtin_compiler'

  CXX  glsl_lexer.lo

  CXX  glsl_parser.lo

clang++: warning: argument unused during compilation: '-fno-builtin-memcmp'

clang++: warning: argument unused during compilation: '-fno-builtin-memcmp'

In file included from glsl_parser.yy:29:

In file included from ../../../src/glsl/ast.h:30:

In file included from ../../../src/glsl/glsl_parser_extras.h:35:

In file included from ../../../src/glsl/glsl_symbol_table.h:34:

In file included from ../../../src/glsl/ir.h:33:

In file included from ../../../src/glsl/glsl_types.h:31:

../../../src/mesa/main/mtypes.h:3420:4: error: unknown type name
'GLDEBUGPROCARB'

   GLDEBUGPROCARB Callback;

   ^

In file included from glsl_lexer.ll:27:

In file included from ../../../src/glsl/ast.h:30:

In file included from ../../../src/glsl/glsl_parser_extras.h:35:

In file included from ../../../src/glsl/glsl_symbol_table.h:34:

In file included from ../../../src/glsl/ir.h:33:

In file included from ../../../src/glsl/glsl_types.h:31:

../../../src/mesa/main/mtypes.h:3420:4: error: unknown type name
'GLDEBUGPROCARB'

   GLDEBUGPROCARB Callback;

   ^

In file included from glsl_parser.yy:32:

In file included from ../../../src/mesa/main/context.h:52:

In file included from ../../../src/mesa/main/imports.h:41:

../../../src/mesa/main/errors.h:84:31: error: unknown type name
'GLDEBUGPROCARB'

_mesa_DebugMessageCallbackARB(GLDEBUGPROCARB callback,

  ^

2 errors generated.

gmake[4]: *** [glsl_parser.lo] Error 1

gmake[4]: *** Waiting for unfinished jobs

1 error generated.

gmake[4]: *** [glsl_lexer.lo] Error 1

gmake[4]: Leaving directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/glsl/builtin_compiler'

gmake[3]: *** [all-recursive] Error 1

gmake[3]: Leaving directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/glsl'

gmake[2]: *** [all] Error 2

gmake[2]: Leaving directory
`/usr/ports/graphics/dri/work/Mesa-9.1.7/src/glsl'

gmake[1]: *** [all-recursive] Error 1

gmake[1]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-9.1.7/src'

gmake: *** [all-recursive] Error 1

===> Compilation failed unexpecte

Re: [QAT] 348583: 6x leftovers

[Ryan Steinmetz]

This was resolved.

-r

On (03/18/14 23:47), Ports-QAT wrote:

New port: devel/p5-RPSL-Parser:

This is a rather simplistic lexer and tokenizer for the RPSL language.

It currently does not validate the object in any way, it just tries
(rather hard) to grab the biggest ammount of information it can from the
text presented and place it in a Parse Tree (that can be passed to other
objects from the RPSL namespace for validation and more RFC2622 related
functionality).

WWW: http://search.cpan.org/dist/RPSL-Parser/
-

 Build ID:  20140318175601-25782
 Job owner: z...@freebsd.org
 Buildtime: 6 hours
 Enddate:   Tue, 18 Mar 2014 23:46:58 GMT

 Revision:  348583
 Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=348583

-

   Port:devel/p5-RPSL-Parser 0.04000

 Buildgroup: 10.0-QAT/amd64
 Buildstatus:   LEFTOVERS
 Log: 
https://qat.redports.org//~z...@freebsd.org/20140318175601-25782-304084/p5-RPSL-Parser-0.04000.log

 Buildgroup: 10.0-QAT/i386
 Buildstatus:   LEFTOVERS
 Log: 
https://qat.redports.org//~z...@freebsd.org/20140318175601-25782-304085/p5-RPSL-Parser-0.04000.log

 Buildgroup: 8.4-QAT/amd64
 Buildstatus:   LEFTOVERS
 Log: 
https://qat.redports.org//~z...@freebsd.org/20140318175601-25782-304086/p5-RPSL-Parser-0.04000.log

 Buildgroup: 8.4-QAT/i386
 Buildstatus:   LEFTOVERS
 Log: 
https://qat.redports.org//~z...@freebsd.org/20140318175601-25782-304087/p5-RPSL-Parser-0.04000.log

 Buildgroup: 9.2-QAT/amd64
 Buildstatus:   LEFTOVERS
 Log: 
https://qat.redports.org//~z...@freebsd.org/20140318175601-25782-304088/p5-RPSL-Parser-0.04000.log

 Buildgroup: 9.2-QAT/i386
 Buildstatus:   LEFTOVERS
 Log: 
https://qat.redports.org//~z...@freebsd.org/20140318175601-25782-304089/p5-RPSL-Parser-0.04000.log


--
Buildarchive URL: 
redports 


--
Ryan Steinmetz
PGP: 9079 51A3 34EF 0CD4 F228  EDC6 1EF8 BA6B D028 46D7
___
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"

Accommodating the security/heimdal port on FreeBSD10

[Dewayne Geraghty]

Some port maintainers on FreeBSD 10 are modifying various ports to
accommodate gssapi use from heimdal base.  Typically the change is
something like
...
LDFLAGS+=   -lgssapi_krb5
..
which works for heimdal in the base system, but prevents a package (or
port build) because in security/heimdal the content of libgssapi_krb5 is
contained within libgssapi; and so doesn't exist as a separate library.

Would it be possible to wrap this dependency within a
.if !defined(HEIMDAL_HOME)
LDFLAGS+=   -lgssapi_krb5
.endif

Its fairly standard practice to test for HEIMDAL_HOME which invariably
implies that the security/heimdal port is being used, and incidentally
identifies where the libraries are located.

Though a better solution, which also reflects the real dependency upon
the security/heimdal port
.if defined(HEIMDAL_HOME)
BUILD_DEPENDS+= 
${HEIMDAL_HOME}/lib/libgssapi.so:${PORTSDIR}/security/heimdal
RUN_DEPENDS+=  ${HEIMDAL_HOME}/lib/libgssapi.so:${PORTSDIR}/security/heimdal
.else
LDFLAGS+=   -lgssapi_krb5
.endif

As this also adds the heimdal port dependency into +COMMENTS (& possible
MANIFEST?), as well as build dependency. 

I'm not a port maintainer/committer, but for those that are, there are a
few ports that might be useful as a reference regarding use of the
heimdal port:
security/cyrus-sasl2-gssapi
net/samba3
dns/bind99

I don't have heimdal from base installed, which is why I noticed that
mail/dovecot2 was the most recent port that needed some additional
lines, so I figured it might help others rather than my patching just my
ports tree.

Regards, Dewayne.
___
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"