FreeBSD ports you maintain which are out of date

2015-03-05 Thread 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/sbcl   | 1.1.12  | 1.2.9
+-+


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: rubygems not working with ruby 2.2?

2015-03-05 Thread Koichiro IWAO

Reproduced in clean environment.

I think devel/ruby-gems is too old and needs updating.
ports version is 1.8.30 and the latest rubygems release is 2.4.6[1].

[1] https://github.com/rubygems/rubygems/releases

# confirm default ruby version is set to 2.2
grep DEFAULT_VERSIONS /etc/make.conf
DEFAULT_VERSIONS=   ruby=2.2 perl5=5.20

# remove all pkgs
pkg remove -fa

# update ports tree
portsnap fetch update

# install ruby and some rubygem- ports
make -C /usr/ports/lang/ruby22
make -C /usr/ports/devel/rubygem-rake
(snip)
===>   rubygem-rake-10.4.2 depends on file: /usr/local/bin/gem22 - found
===>   rubygem-rake-10.4.2 depends on file: /usr/local/bin/ruby22 - 
found

===>  Configuring for rubygem-rake-10.4.2
===>  Building for rubygem-rake-10.4.2
/usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1960:in 
`block (2 levels) in to_yaml': stack level too deep (SystemStackError)

from /usr/local/lib/ruby/2.2/psych/coder.rb:36:in `map'
	from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1959:in 
`block in to_yaml'

from /usr/local/lib/ruby/2.2/psych/deprecated.rb:19:in `call'
	from /usr/local/lib/ruby/2.2/psych/deprecated.rb:19:in `block in 
quick_emit'
	from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1960:in 
`block (2 levels) in to_yaml'

from /usr/local/lib/ruby/2.2/psych/coder.rb:36:in `map'
	from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1959:in 
`block in to_yaml'

from /usr/local/lib/ruby/2.2/psych/deprecated.rb:19:in `call'
 ... 9619 levels...
	from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/command_manager.rb:147:in 
`process_args'
	from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/command_manager.rb:117:in 
`run'
	from /usr/local/lib/ruby/site_ruby/2.2/rubygems/gem_runner.rb:65:in 
`run'

from /usr/local/bin/gem22:30:in `'
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure 
to

the maintainer.
*** Error code 1

--
`whois vmeta.jp | nkf -w`
meta 
___
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"


www/seamonkey 2.32.1 vulnerable?

2015-03-05 Thread Thomas Mueller
What is the vulnerability status of www/seamonkey?

A massive portmaster upgrade resulting from png last December 25, delayed by 
other snags, stopped quickly because www/seamonkey was said to be vulnerable.

But this is the newest version of Seamonkey either on FreeBSD ports or upstream 
(www.seamonkey-project.org where there was no mention of vulnerability in 
current version).


Tom

___
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: rubygems not working with ruby 2.2?

2015-03-05 Thread Steve Wills
Hi,

Yep, I'm aware, there's an update to devel/ruby-gems pending, see:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197083

Steve

On Thu, Mar 05, 2015 at 09:25:43AM +, Koichiro IWAO wrote:
> Reproduced in clean environment.
> 
> I think devel/ruby-gems is too old and needs updating.
> ports version is 1.8.30 and the latest rubygems release is 2.4.6[1].
> 
> [1] https://github.com/rubygems/rubygems/releases
> 
> # confirm default ruby version is set to 2.2
> grep DEFAULT_VERSIONS /etc/make.conf
> DEFAULT_VERSIONS= ruby=2.2 perl5=5.20
> 
> # remove all pkgs
> pkg remove -fa
> 
> # update ports tree
> portsnap fetch update
> 
> # install ruby and some rubygem- ports
> make -C /usr/ports/lang/ruby22
> make -C /usr/ports/devel/rubygem-rake
> (snip)
> ===>   rubygem-rake-10.4.2 depends on file: /usr/local/bin/gem22 - found
> ===>   rubygem-rake-10.4.2 depends on file: /usr/local/bin/ruby22 - 
> found
> ===>  Configuring for rubygem-rake-10.4.2
> ===>  Building for rubygem-rake-10.4.2
> /usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1960:in 
> `block (2 levels) in to_yaml': stack level too deep (SystemStackError)
>   from /usr/local/lib/ruby/2.2/psych/coder.rb:36:in `map'
>   from 
> /usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1959:in 
> `block in to_yaml'
>   from /usr/local/lib/ruby/2.2/psych/deprecated.rb:19:in `call'
>   from /usr/local/lib/ruby/2.2/psych/deprecated.rb:19:in `block in 
> quick_emit'
>   from 
> /usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1960:in 
> `block (2 levels) in to_yaml'
>   from /usr/local/lib/ruby/2.2/psych/coder.rb:36:in `map'
>   from 
> /usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1959:in 
> `block in to_yaml'
>   from /usr/local/lib/ruby/2.2/psych/deprecated.rb:19:in `call'
>... 9619 levels...
>   from 
> /usr/local/lib/ruby/site_ruby/2.2/rubygems/command_manager.rb:147:in 
> `process_args'
>   from 
> /usr/local/lib/ruby/site_ruby/2.2/rubygems/command_manager.rb:117:in 
> `run'
>   from /usr/local/lib/ruby/site_ruby/2.2/rubygems/gem_runner.rb:65:in 
> `run'
>   from /usr/local/bin/gem22:30:in `'
> ===> Compilation failed unexpectedly.
> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure 
> to
> the maintainer.
> *** Error code 1
> 
> -- 
> `whois vmeta.jp | nkf -w`
> meta 
> ___
> freebsd-r...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ruby
> To unsubscribe, send any mail to "freebsd-ruby-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: www/seamonkey 2.32.1 vulnerable?

2015-03-05 Thread Jan Beich
"Thomas Mueller"  writes:

> A massive portmaster upgrade resulting from png last December 25,
> delayed by other snags, stopped quickly because www/seamonkey was said
> to be vulnerable.
>
> But this is the newest version of Seamonkey either on FreeBSD ports or
> upstream (www.seamonkey-project.org where there was no mention of
> vulnerability in current version).

Mozilla vulnerabilities are often generic to the engine/core. While many
cannot be exploited in Thunderbird due to scripting disabled the same
cannot be said about SeaMonkey which includes a browser.

After looking through the past MFSAs it appears upstream only marks
SeaMonkey vulnerable after there's a corresponding release with
vulnerabilities fixed. In a situation where such release is delayed
(like 2.33) or even canceled (2.27, 2.28) there's a window for attackers
to take action on the disclosure.

Do you have a better suggestion? I'm in favor of populating VuXML first
instead of pretending using 2.32.1 is safe at this point.

--
SeaMonkey 2.33 status can be tracked in bug 1137028 or via hg tags:

https://bugzilla.mozilla.org/show_bug.cgi?id=1137028
https://hg.mozilla.org/releases/comm-release/


signature.asc
Description: PGP signature


Re: devel/dbus no longer starts at system poweron

2015-03-05 Thread Beeblebrox
Hi.
This thread is probably more appropriate for further dbus discussion.
Per your comment,
1. "# rcorder /etc/rc.d/* /usr/local/etc/rc.d/* > /dev/null" >>
rcorder: file `/usr/local/etc/rc.d/tcsd' is before unknown provision `named'
rcorder: file `/usr/local/etc/rc.d/clamav-freshclam' is before unknown 
provision `mail'
rcorder: Circular dependency on provision `ldconfig' in file 
`/usr/local/etc/rc.d/dbus'.
rcorder: Circular dependency on provision `DAEMON' in file 
`/usr/local/etc/rc.d/dbus'.
rcorder: requirement `kdc' in file `/etc/rc.d/SERVERS' has no providers.
rcorder: requirement `tpmd' in file `/usr/local/etc/rc.d/tcsd' has no providers.
rcorder: requirement `USR' in file `/usr/local/etc/rc.d/tor' has no providers.
rcorder: requirement `usbd' in file `/usr/local/etc/rc.d/hald' has no providers.
rcorder: requirement `kerberos' in file `/usr/local/etc/rc.d/ipropd_slave' has 
no providers.
rcorder: requirement `kerberos' in file `/usr/local/etc/rc.d/ipropd_master' has 
no providers.
rcorder: requirement `DAEMON%%MYSQLPGSQL%%' in file 
`/usr/local/etc/rc.d/barnyard2' has no providers.
++ Separate isue, but the last line above may be a contributing cause why I am 
unable to get sguil to start on my system

Source of the problem might be a combination of port config options that leaves 
out some port that would normally trigger dbus startup without problems.

2. "# rcorder /etc/rc.d/* /usr/local/etc/rc.d/* " >> (snipped, not much insight 
though)
rcorder: Circular dependency on provision `ldconfig' in file 
`/usr/local/etc/rc.d/dbus'.
rcorder: Circular dependency on provision `DAEMON' in file 
`/usr/local/etc/rc.d/dbus'.
/usr/local/etc/rc.d/dbus
/etc/rc.d/kldxref
/etc/rc.d/kld
/etc/rc.d/addswap
/etc/rc.d/adjkerntz
/etc/rc.d/atm1
/etc/rc.d/hostname
/etc/rc.d/ip6addrctl
/etc/rc.d/netoptions
/etc/rc.d/random
/etc/rc.d/sppp
/etc/rc.d/ipfilter
/etc/rc.d/ipnat
/etc/rc.d/ipfs
/etc/rc.d/serial
/etc/rc.d/netif
/usr/local/etc/rc.d/webcamd
/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/routing
/etc/rc.d/mroute6d
/etc/rc.d/nsswitch
/etc/rc.d/rtsold
/usr/local/etc/rc.d/vboxnet
/etc/rc.d/static_ndp
/etc/rc.d/static_arp
/etc/rc.d/bridge
/etc/rc.d/resolv
/etc/rc.d/route6d
/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/ldconfig
/etc/rc.d/newsyslog
/etc/rc.d/syslogd
/etc/rc.d/ntpdate
/etc/rc.d/rpcbind
/etc/rc.d/nfsclient
/etc/rc.d/devfs
/etc/rc.d/ipmon
/etc/rc.d/mdconfig2

-- 
FreeBSD_amd64_11-Current_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
___
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/dbus no longer starts at system poweron

2015-03-05 Thread Beeblebrox
> Just to let you know, I have not forgotten your issue. Just have not
> gotten to it

No worries. As you saw on the thread on current, this is really the least of my 
woes with X.org.

> The output you provided will at least get me started, but I really
> need the full rcorder output.

https://drive.google.com/file/d/0Bxs_eepbMt6qRkQ3YmJlR2FkcVk/view?usp=sharing

I can attempt to sort through parts of it if you give me some idea of howto / 
what to look for.

Regards.
-- 
FreeBSD_amd64_11-Current_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
___
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"