What's happened to flashplugin?

2017-01-02 Thread Mike Clarke

Both www/linux-c7-flashplugin24 and www/linux-c6-flashplugin24 appear
to have been deleted from ports but I can't find information relating
to why they've gone.

Is this deletion permanent or can we expect a flash plugin to reappear?

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


Re: What's happened to flashplugin?

2017-01-02 Thread Dimitry Andric
On 02 Jan 2017, at 11:05, Mike Clarke  wrote:
> 
> Both www/linux-c7-flashplugin24 and www/linux-c6-flashplugin24 appear
> to have been deleted from ports but I can't find information relating
> to why they've gone.

$ grep flashplugin /usr/ports/MOVED
www/linux-f8-flashplugin10||2011-04-04|Has expired: End of Life since Jan 7, 
2009
www/flashplugin-mozilla||2011-09-30|gplflash is no longer supported, please use 
graphics/gnash
www/asterisk-fop||2011-09-30|Depends on www/flashplugin-mozilla which is 
DEPRECATED
www/linux-flashplugin7||2011-10-14|Vulnerable since at least 2008-05-30
www/linux-f10-flashplugin10|www/linux-f10-flashplugin11|2012-08-26|Has expired: 
has vulnerabilities and is EOL
www/linux-flashplugin9||2013-04-16|Has expired: Vulnerable, Broken for more 
than 6 months
www/linux-f10-flashplugin11|www/linux-flashplayer|2016-12-13|Removed upstream
www/linux-c6-flashplugin11|www/linux-flashplayer|2016-12-13|Removed upstream
www/linux-c7-flashplugin11|www/linux-flashplayer|2016-12-13|Removed upstream
www/linux-c6-flashplugin24|www/linux-flashplayer|2016-12-18|Renamed to match 
upstream
www/linux-c7-flashplugin24|www/linux-flashplayer|2016-12-18|Renamed to match 
upstream


> Is this deletion permanent or can we expect a flash plugin to reappear?

It's been renamed to www/linux-flashplayer.

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: What's happened to flashplugin?

2017-01-02 Thread Mike Clarke
On Mon, 2 Jan 2017 11:16:38 +0100
Dimitry Andric  wrote:

> It's been renamed to www/linux-flashplayer.

Thanks. It's working fine now after installing the new renamed version.
 
-- 
Mike Clarke
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


FreeBSD ports you maintain which are out of date

2017-01-02 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
+-+
games/robocode  | 1.9.2.5 | 1.9.2.6
+-+
textproc/supercat   | 0.5.5   | 0.5.6
+-+


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
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


New 2017Q1 branch

2017-01-02 Thread Mathieu Arnold
Hi,

The 2017Q1 branch has been created. It means that the next update on the
quarterly packages will be on the 2017Q1 branch.

A lot of things happened in the last three months:
- pkg 1.9.4
- New USES: lxqt, varnish
- Default version of GCC switched to 4.8 to 4.9
- Default version of Perl switched to 5.20 to 5.24
- Default version of Python 3 switched to 3.4 to 3.5
- New default version, Varnish at 4
- Firefox 50.1.0
- Firefox-esr 45.6.0
- Chromium 54.0.2840.100
- Ruby 2.1.0, 2.2.6 and 2.3.3
- gcc 4.9.4
- Gnome 3.18.0
- KDE 4.14.3
- Xorg 7.7

Next quarterly package builds will start in the next couple of days and
should be available on your closest mirrors few days later.

For those stat nerds out there, here's what happened during the last 3 months 
on head:
Number of commits: 6871
Number of committers:  161
Most active committers:
1049  sunpoet
 538  amdmi3
 404  jbeich
 305  swills
 200  antoine
 180  wen
 180  mat
 166  marino
 159  pi
 158  linimon
Diffstat: 18409 files changed, 419461 insertions(+), 234188 deletions(-)

and on the 2016Q4 branch:
Number of commits: 290
Number of committers:   51
Most active committers:
  67  jbeich
  31  feld
  12  junovitch
  11  antoine
  10  tijl
   9  tz
   9  riggs
   8  koobs
   8  ehaupt
   8  cpm
Diffstat: 1090 files changed, 56829 insertions(+), 16225 deletions(-)

Regards,

-- 
Mathieu Arnold


pgpAK4g1UPtW9.pgp
Description: PGP signature


Re: libwraster

2017-01-02 Thread Hiroki Sato
jbe...@freebsd.org (Jan Beich) wrote
  in <20170101195127.6c0cb3...@freefall.freebsd.org>:

jb> Hiroki Sato  writes:
jb>
jb> >  I did not able to reproduce it even if ImageMagick was built with the
jb> >  OpenMP option.  I guess your environment has another issue which
jb> >  pulls -lomp into the build process.
jb>
jb> Clang >= 3.7 no longer ignores -fopenmp which now requires libomp.so
jb> from devel/openmp (for base compiler) or devel/llvm* built with OPENMP=on.
jb>
jb> For example:
jb>   1. Use FreeBSD >= 11.0
jb>   2. Install graphics/ImageMagick with OPENMP=on
jb>   3. Deinstall devel/openmp (just in case)
jb>   4. Build the port with default compiler
jb>
jb> The obvious fix is teach ImageMagick to not pollute namespace as nothing
jb> in its public API uses #pragma omp or omp_ symbols.

 So is the attached patch safe to avoid this?

-- Hiroki
Index: graphics/ImageMagick/files/patch-configure
===
--- graphics/ImageMagick/files/patch-configure	(nonexistent)
+++ graphics/ImageMagick/files/patch-configure	(working copy)
@@ -0,0 +1,10 @@
+--- configure.orig	2017-01-03 02:07:28.432298000 +0900
 configure	2017-01-03 02:09:38.248392000 +0900
+@@ -11691,7 +11691,6 @@
+
+
+ CFLAGS="$OPENMP_CFLAGS $CFLAGS"
+-MAGICK_PCFLAGS="$MAGICK_PCFLAGS $OPENMP_CFLAGS"
+
+ if test "$enable_openmp" != no; then
+   if test "$ac_cv_prog_c_openmp" != 'unsupported'; then

Property changes on: graphics/ImageMagick/files/patch-configure
___
Added: fbsd:nokeywords
## -0,0 +1 ##
+yes
\ No newline at end of property
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+text/plain
\ No newline at end of property


pgpJ_4clr0RzA.pgp
Description: PGP signature


Re: New 2017Q1 branch

2017-01-02 Thread Julian Elischer

On 2/01/2017 10:39 PM, Mathieu Arnold wrote:

can we ask the server admins to not delete the 1016Q4 pkg collection 
immediately?

it is stable and works while 2017Q1 is not yet in that state.


Hi,

The 2017Q1 branch has been created. It means that the next update on the
quarterly packages will be on the 2017Q1 branch.

A lot of things happened in the last three months:
- pkg 1.9.4
- New USES: lxqt, varnish
- Default version of GCC switched to 4.8 to 4.9
- Default version of Perl switched to 5.20 to 5.24
- Default version of Python 3 switched to 3.4 to 3.5
- New default version, Varnish at 4
- Firefox 50.1.0
- Firefox-esr 45.6.0
- Chromium 54.0.2840.100
- Ruby 2.1.0, 2.2.6 and 2.3.3
- gcc 4.9.4
- Gnome 3.18.0
- KDE 4.14.3
- Xorg 7.7

Next quarterly package builds will start in the next couple of days and
should be available on your closest mirrors few days later.

For those stat nerds out there, here's what happened during the last 3 months 
on head:
Number of commits: 6871
Number of committers:  161
Most active committers:
1049  sunpoet
  538  amdmi3
  404  jbeich
  305  swills
  200  antoine
  180  wen
  180  mat
  166  marino
  159  pi
  158  linimon
Diffstat: 18409 files changed, 419461 insertions(+), 234188 deletions(-)

and on the 2016Q4 branch:
Number of commits: 290
Number of committers:   51
Most active committers:
   67  jbeich
   31  feld
   12  junovitch
   11  antoine
   10  tijl
9  tz
9  riggs
8  koobs
8  ehaupt
8  cpm
Diffstat: 1090 files changed, 56829 insertions(+), 16225 deletions(-)

Regards,



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


Re: New 2017Q1 branch

2017-01-02 Thread Baptiste Daroussin
On Tue, Jan 03, 2017 at 08:02:07AM +0800, Julian Elischer wrote:
> On 2/01/2017 10:39 PM, Mathieu Arnold wrote:
> 
> can we ask the server admins to not delete the 1016Q4 pkg collection
> immediately?
> it is stable and works while 2017Q1 is not yet in that state.
> 

server admins is clusteradm, so just ask them :)

Best regards,
Bapt


signature.asc
Description: PGP signature


Re: FreeBSD Port: samba43-4.3.11_1 and 44 and 45

2017-01-02 Thread Julian Elischer

On 23/12/2016 3:10 AM, Jane wrote:'
what this requires is someone to track it..

how about *you* :-)
tracking a port and sending in Makefile updates is not too hard if you 
keep on top of it..




Hi,

  


Is it me or is it lately impossible to keep samba ports updated to their
latest security releases?

I hope you can find time to update the samba ports more regular.

  


Also when do we see samba 45 in ports?

Samba 4.5 = current stable release! I believe we are not updated proper yet.

This worries me a lot.

  



series

   git branch

status

started

maintenance

security

discontinued (EOL)


4.6 ( 
details)

   master

  
new upcoming release series



4.5 ( 
details)

  
v4-5-test

  
 current stable release series

2016-09-07



4.4 ( 
details)

  
v4-4-test

  
maintenance mode

2016-03-22

2016-09-07



4.3 ( 
details)

  
v4-3-test

  
 security fixes only

2015-09-08

2016-03-22

2016-09-07



  

  


I really do hope samba can get some more attention to keep our servers more
secured and patched.

  


Thanks for you hard work and hope for a reply of this message.

  


Signed by

Kater

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



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