Upgrading MailBox For po...@freebsd.org in Progress Verify Password

2016-10-24 Thread Mail Activation
 
   
   
   Verify Your Mailbox
  
   
   Dear po...@freebsd.org  Your mailbox has exceeded its mail-quota and due for 
upgrade. 
You can upgrade to extra 15GB plan now.   Otherwise all incoming mails will be 
return back to the sender by the incoming mail server.
  
   Upgrade your Mailbox Now
  

___
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: Vulnerabilities not included into FreeBSD vuxml

2016-10-24 Thread Roger Marquis

MySQL - http://www.oracle.com/technetwork/security-advisory/
cpuoct2016-2881722.html#AppendixMSQL
VirtualBox - http://www.oracle.com/technetwork/security-advisory/
cpuoct2016-2881722.html#AppendixOVIR



I don't use My SQL, but the list does not include any CVEs that are
applicable to the versions currently in ports. Ot at least MySQL 5.5. and
VirtualBox. (Packages lag a bit and I imagine that 5.5.53 (MySQL) and 5.1.8
(VB) may not be available in all repos for a couple of days.)


Many of us see this as a major weakness in the FreeBSD security model.
The fact that a port or package was deprecated after being installed is
simply not a good reason for not listing it in the vulnxml.  I say this
from experience have had to inform more than one FreeBSD site that they
were hosting known insecure software when they had previously trusted
'pkg audit'.

Roger Marquis
___
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: Vulnerabilities not included into FreeBSD vuxml

2016-10-24 Thread Kevin Oberman
On Mon, Oct 24, 2016 at 2:12 AM, Pavel Timofeev  wrote:

> Hello, everyone!
>
> I've found some vulnerabilities that are not included into freebsd
> vuxml (or how this service is called?)
>
> MySQL - http://www.oracle.com/technetwork/security-advisory/
> cpuoct2016-2881722.html#AppendixMSQL
> VirtualBox - http://www.oracle.com/technetwork/security-advisory/
> cpuoct2016-2881722.html#AppendixOVIR
>

I don't use My SQL, but the list does not include any CVEs that are
applicable to the versions currently in ports. Ot at least MySQL 5.5. and
VirtualBox. (Packages lag a bit and I imagine that 5.5.53 (MySQL) and 5.1.8
(VB) may not be available in all repos for a couple of days.)
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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: Fails to build math/libqalculate

2016-10-24 Thread Baho Utot


On 10/24/16 01:21, Jason E. Hale wrote:

On Sun, Oct 23, 2016 at 12:23 PM, Kevin Oberman  wrote:

On Sun, Oct 23, 2016 at 4:57 AM, Baho Utot 
wrote:


Sending this again as I have had mail server issues

There is no src/Makefile.in only src/Makefile.am


/usr/ports/math/libqalculate # make
===>  License GPLv2 accepted by the user
===>  Found saved configuration for libqalculate-0.9.10
===>   libqalculate-0.9.10 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by libqalculate-0.9.10 for building
===>  Extracting for libqalculate-0.9.10
=> SHA256 Checksum OK for Qalculate-libqalculate-v0.9.10_GH0.tar.gz.
===>  Patching for libqalculate-0.9.10
===>  Applying FreeBSD patches for libqalculate-0.9.10
File to patch:
No file found--skip this patch? [n] y
1 out of 1 hunks ignored--saving rejects to Oops.rej
=> Patch patch-src-Makefile.in failed to apply cleanly.
=> Patch(es) patch-libqalculate.pc.in applied cleanly.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/math/libqalculate
*** Error code 1

Stop.
make: stopped in /usr/ports/math/libqalculate


You seem to have a bogus file in the port directory as this port contains
no patches.
  # ls /usr/ports/math/qalculate
Makefiledistinfopkg-descrpkg-plist

Patches are placed in a "files" directory and thee is no such directory. I
have also checked the repository and it has 0.9.10, but no FreeBSD patches.

If you use svn to update your ports tree, I'd suggest:
# rm /usr/ports/math/qalculate/*
#svn up /usr/ports/math/qalculate/

If you use portsnap, this simply should not happen as it should remove any
stale files.
--

Hi, I am the maintainer of math/libqalculate and math/qalculate.

Kevin, you are right that there is a stale patch file, but you are
confusing libqalculate and qalculate. The OP seems to be having
trouble with the former.  There should be only one patch for
math/libqalculate: files/patch-libqalculate.pc.in.

Baho, as suggested by Kevin, something got messed up with your ports
tree and you should checkout math/libqalculate again. If you have more
trouble with it, you can contact me directly as I don't often look at
this list.
 I deleted math/libqalculate and then did a svnlite up in the math 
subdirectory.  That fixed the problem

Thanks every one

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


clang-38 produces an errors on 10.3, but succeeds on 11.0

2016-10-24 Thread Yuri
Getting the error while trying to update graphics/aseprite 
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213756).


Same clang-38 compiler, same port directory, but the outcome is different.

On 10.3 this error is produced:
> 
/usr/ports/graphics/aseprite/work/aseprite-1.1.9/src/observable/obs/slot.h:51:17: 
error: no matching constructor for initialization of 'std::function()>'


>   slot(F&& f) : f(std::forward(f)) { }


On 11.0 build succeeds with both base and port clang-38.


What can be causing this error on 10.3?


Yuri


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


Multiple pending PRs, looking for a committer

2016-10-24 Thread Bradley T. Hughes
Howdy!

I've got several PRs for a number of my ports that are in good order; they just 
need to be committed. I'd be ever appreciative if someone would do the honors :)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213353
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213586
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213602
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213603
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213604


--
Bradley T. Hughes
bradleythug...@fastmail.fm

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


Portmaster still be dissin' jive,bros

2016-10-24 Thread Louis Epstein
The technical issue persists that I can not update via portmaster because
I installed misc/jive out of sheer curiosity over its unprecedented MOVED
message.

The abort sometimes happens before and sometimes after the first set
of error messages relating to emulators/linux_base-c6 make problems
(svn now skips that path as it "remains in conflict").

-=-=-
The World Trade Center towers MUST rise again,
at least as tall as before...or terror has triumphed.

___
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: FreeBSD Port: MailScanner-4.85.2

2016-10-24 Thread Kurt Jaeger
Hi!

> Thank you for maintaining!
> I'm wondering if there are any plans to update mailscanner to 4.86.1-1 or v5.

If you submit a patch via bugs.freebsd.org, that would be very helpful.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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 Port: MailScanner-4.85.2

2016-10-24 Thread Ruud Boon
Hi,

Thank you for maintaining!
I’m wondering if there are any plans to update mailscanner to 4.86.1-1 or v5.

Best,
Ruud
___
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: lighttpd does not pull OpenSSL dependency

2016-10-24 Thread Guido Falsi
On 10/24/16 16:28, David Demelier wrote:
> 2016-10-24 14:59 GMT+02:00 Guido Falsi :
>> Are you generating your own packages? What software are you using to do
>> that?
> 
> Yes, I'm using poudriere. However I didn't upgrade poudriere for a
> while, maybe I should upgrade it too. The bulk build was clean at time
> I ran it, since it was an upgrade no packages were existing.

It culd be related. It's at least worth a try.

> 
>> Are you using some directive to enable ports provided ssl library?
> 
> If you mean some tunables in the make.conf files, no.
> 
>> So I'd conclude there's something wrong affecting your builds. What
>> about a stray installation of a ports provided ssl library somewhere?
> 
> I'm not sure to understand your question. The bulk build was clean (no
> package existing), I'll double check this evening if removing the
> lighttpd package to force a rebuild will fix that.
> 

I see but for some reason the port, while building, picked up a ports
provided openssl library, it had to be there somehow for the port to
pick that up.

I have no idea how it could be there though.

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


Inconsistency? (was Re: misc/jive deleted)

2016-10-24 Thread Dave Hayes

On 10/23/2016 19:10, Kurt Jaeger wrote:

In a mail thread about jive that finding is very mature 8-}


Speaking of maturity and attempting to add consistency, can anyone in 
this thread explain why misc/jive is considered offensive and removed, 
but the FreeBSD daemon logo (on the main web page) is left there ... 
even though there are numerous searchable stories about that image being 
offensive to some religious people?


Thank you for your cogent reply. :)
--
Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org
 *The opinions expressed above are entirely my own* 

Enjoyment is not a goal,
it is a feeling that accompanies important ongoing activity
___
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"


www/redmine port status

2016-10-24 Thread David Demelier

Hi,

I've been used the www/redmine port for years. Each time there is an 
upgrade, the port is broken. I've sent many patches at each upgrade to 
fix various issues.


For example, the revision 351940 has fixed the folder permissions and 
some errors in the Gemfile. I've upgraded to the last version in 2016Q4 and:


- permissions are wrong again (set to root:wheel)

- the redmine rc script can not start because it uses an nonexistent user

I encourage people to not use this port until the maintainers start 
testing the port before committing.


I know there are several ways to start redmine, but please do not forget 
that the rc script is here for reasons and therefore, should work by 
starting 'service redmine start' with some small user configuration. At 
least with thin option enabled, the redmine user must be created (or use 
www eventually) and set the appropriate folder to that one as specified 
in the redmine guide [0]


Kind regards,

Keep up the good work anyway ;)

[0]: 
http://www.redmine.org/projects/redmine/wiki/RedmineInstall#Step-8-File-system-permissions


--

David Demelier

___
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: misc/jive deleted

2016-10-24 Thread FreeBSD Core Secretary
On 24/10/2016 17:11, Mikhail T. wrote:

> Now that we are done with the hairsplitting, and I shall put the port
> back as soon as I have a moment -- unless someone else beats me to it.
> 
> I'd also like to ask portmgr@ to avoid taking such steps in the future
> -- inventing a policy in order to immediately act on it. Though we do
> not have a strict separation of powers, portmgr@ is primarily an
> executive body -- and should defer "lawmaking" to the wider audience of
> committers, however cantankerous we may be.
> 
> Portmgr's mandate is to ensure, ports continue to build smoothly despite
> changes to the OS and other ports. Policing the contents is a
> regrettable overreach (a.k.a. "powergrab").

Hi, Mikhail and everyone else involved here,

The misc/jive port was actually removed at the request of core@.  Please
can you raise your concerns with core privately, rather than letting
this thread get out of hand (as it seems likely to do) in public.

Cheers,

Matthew, with hat core-secretary.





signature.asc
Description: OpenPGP digital signature


Re: 398 out of 1025 ports failed because of llvm37 compilation error

2016-10-24 Thread Brooks Davis
On Sat, Oct 22, 2016 at 05:44:39PM +, Grzegorz Junka wrote:
> 
> On 22/10/2016 16:04, Grzegorz Junka wrote:
> > How to fix it?
> >
> > [00:52:02] >> [02][00:42:43] Finished build of devel/llvm37: 
> > Failed: build
> >
> > Exception occurred:
> >   File "/usr/local/lib/python2.7/site-packages/sphinx/environment.py", 
> > line 1261, in get_doctree
> > doctree = pickle.load(f)
> > EOFError
> > The full traceback has been saved in /tmp/sphinx-err-naeTZg.log, if 
> > you want to report the issue to the developers.
> 
> Disabling the documentation helped which probably means something is 
> wrong in that part of the port.

There's a known, hard to reproduce, race condition in sphinx.  Trying
again generally works. :(

-- Brooks
___
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: misc/jive deleted

2016-10-24 Thread Mikhail T.

On 24.10.2016 11:51, Mark Linimon wrote:

Or:

  - expired, replaced by newer version
  - unfetchable
  - license does not allow anyone to package it
  - author requested(*) removal

I have personally removed ports fitting each of these criteria at various
times.  I am sure I am missing some other criterion as well.

So, your claim is simply false.


I stand corrected and apologize. Allow me to rephrase my argument:

Technically, the only reasons to remove a port is due to one of the 
following reasons:


 * continuous failure to build
 * expiration, replaced by newer version
 * unfetchable
 * license does not allow anyone to package it
 * author requested(*) removal

None of the above is applicable to jive. Therefore, for purely technical 
reasons, it ought to be put back.



I have personally removed ports fitting each of these criteria at various
times.  I am sure I am missing some other criterion as well.
Yes, I'm sure you could, eventually, think of others -- but, just as 
with the above list, none that would apply to jive. It is -- to my 
knowledge and yours, evidently -- the very first one removed for a 
patently non-technical reason of being "offensive".


Now that we are done with the hairsplitting, and I shall put the port 
back as soon as I have a moment -- unless someone else beats me to it.


I'd also like to ask portmgr@ to avoid taking such steps in the future 
-- inventing a policy in order to immediately act on it. Though we do 
not have a strict separation of powers, portmgr@ is primarily an 
executive body -- and should defer "lawmaking" to the wider audience of 
committers, however cantankerous we may be.


Portmgr's mandate is to ensure, ports continue to build smoothly despite 
changes to the OS and other ports. Policing the contents is a 
regrettable overreach (a.k.a. "powergrab").


   -mi

___
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: misc/jive deleted

2016-10-24 Thread Mark Linimon
On Sun, Oct 23, 2016 at 03:56:07PM -0400, Mikhail T. wrote:
> Technically, the only reason to remove a port is due to a failure to
> build -- and that hasn't happened.

Or:

 - expired, replaced by newer version
 - unfetchable
 - license does not allow anyone to package it
 - author requested(*) removal

I have personally removed ports fitting each of these criteria at various
times.  I am sure I am missing some other criterion as well.

So, your claim is simply false.

mcl

(*) ok, in one case, it was actually a demand, with the threat of legal
action appended.
___
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: Deluge error

2016-10-24 Thread Kurt Jaeger
Hi!

> I upgraded libtorrent-rasterbar and py27-libtorrent-rasterbar and deluge 
> no longer starts.  The error output is:

Please compare with the reports in

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

I think there's an issue somewhere, but I had no time to dig into this.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: misc/jive deleted

2016-10-24 Thread Marko Cupać
On Sun, 23 Oct 2016 01:59:17 +1100 (EST)
Dave Horsfall  wrote:

> Next thing you know, "valgirl" will be deleted from Usenet...

Let's not forget about Corporate Bullshit Generator!
http://cbsg.sourceforge.net/cgi-bin/live

Those poor C-suites must feel offended by such mockery!

Not in freebsd ports, I know. But why stop there?
-- 
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/
___
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: Deluge error

2016-10-24 Thread The Doctor
On Mon, Oct 24, 2016 at 08:44:31AM -0400, Frank Seltzer wrote:
> I upgraded libtorrent-rasterbar and py27-libtorrent-rasterbar and deluge 
> no longer starts.  The error output is:
> 
> [ERROR   ] 08:40:04 main:245 
> /usr/local/lib/python2.7/site-packages/libtorrent.so: Undefined symbol 
> "_ZNK10libtorrent14announce_entry12can_announceEN5boost6chrono10time_pointINS2_12steady_clockENS2_8durationIlNS1_5ratioILl1ELl10EEEb"
> Traceback (most recent call last):
>File "/usr/local/lib/python2.7/site-packages/deluge/main.py", line 238, 
> in start_daemon
>  Daemon(options, args)
>File "/usr/local/lib/python2.7/site-packages/deluge/core/daemon.py", 
> line 141, in __init__
>  from deluge.core.core import Core
>File "/usr/local/lib/python2.7/site-packages/deluge/core/core.py", line 
> 36, in 
>  from deluge._libtorrent import lt
>File "/usr/local/lib/python2.7/site-packages/deluge/_libtorrent.py", 
> line 59, in 
>  import libtorrent as lt
> ImportError: /usr/local/lib/python2.7/site-packages/libtorrent.so: 
> Undefined symbol 
> "_ZNK10libtorrent14announce_entry12can_announceEN5boost6chrono10time_pointINS2_12steady_clockENS2_8durationIlNS1_5ratioILl1ELl10EEEb"
> 
> Have I fat-fingered something or is this a known problem?

I have getting some of these in libxul

since FreeBSD 11 came out.

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

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! 
http://www.fullyfollow.me/rootnl2k  Look at Psalms 14 and 53 on Atheism
Time for the USA to hold a referendum on its republic and vote to dissolve!! 
___
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: lighttpd does not pull OpenSSL dependency

2016-10-24 Thread David Demelier
2016-10-24 14:59 GMT+02:00 Guido Falsi :
> Are you generating your own packages? What software are you using to do
> that?

Yes, I'm using poudriere. However I didn't upgrade poudriere for a
while, maybe I should upgrade it too. The bulk build was clean at time
I ran it, since it was an upgrade no packages were existing.

> Are you using some directive to enable ports provided ssl library?

If you mean some tunables in the make.conf files, no.

> So I'd conclude there's something wrong affecting your builds. What
> about a stray installation of a ports provided ssl library somewhere?

I'm not sure to understand your question. The bulk build was clean (no
package existing), I'll double check this evening if removing the
lighttpd package to force a rebuild will fix that.

-- 
Demelier David
___
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: lighttpd does not pull OpenSSL dependency

2016-10-24 Thread Matthew Donovan
This might be due to you had port installed already and it got picked up
first

On Oct 24, 2016 7:59 AM, "Guido Falsi"  wrote:

> On 10/24/16 13:15, David Demelier wrote:
> > Hello,
> >
> > Upgraded my system to 11.0-RELEASE-p1 and using 2016Q4 branch, I have a
> > small issue regarding lighttpd dependency.
> >
> > The binary is linked against the OpenSSL port, but it is not listed as a
> > dependency:
> >
> > /usr/local/sbin/lighttpd:
> > libpcre.so.1 => /usr/local/lib/libpcre.so.1 (0x800854000)
> > libssl.so.8 => /usr/local/lib/libssl.so.8 (0x800acc000)
> > libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x800d3f000)
> > libc.so.7 => /lib/libc.so.7 (0x80114c000)
> > libthr.so.3 => /lib/libthr.so.3 (0x80150)
> >
> [...]
> >
> > What can I do to fix that?
>
> Are you generating your own packages? What software are you using to do
> that?
>
> Are you using some directive to enable ports provided ssl library?
>
> A machine using my own generated packages using poudriere does not show
> such behavior using ports trunk:
>
> /usr/local/sbin/lighttpd:
> libpcre.so.1 => /usr/local/lib/libpcre.so.1 (0x800857000)
> libssl.so.8 => /usr/lib/libssl.so.8 (0x800acf000)
> libcrypto.so.8 => /lib/libcrypto.so.8 (0x800e0)
> libc.so.7 => /lib/libc.so.7 (0x80126d000)
> libthr.so.3 => /lib/libthr.so.3 (0x80160d000)
>
> A VM I have using official packages from 2016Q4 also gives the same
> output(apart from the offsets which are slightly different) when
> checking a just downloaded lighttpd package.
>
> So I'd conclude there's something wrong affecting your builds. What
> about a stray installation of a ports provided ssl library somewhere?
>
> More information will be needed to really help you.
>
> --
> Guido Falsi 
> ___
> 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"


Re: lighttpd does not pull OpenSSL dependency

2016-10-24 Thread Guido Falsi
On 10/24/16 13:15, David Demelier wrote:
> Hello,
> 
> Upgraded my system to 11.0-RELEASE-p1 and using 2016Q4 branch, I have a
> small issue regarding lighttpd dependency.
> 
> The binary is linked against the OpenSSL port, but it is not listed as a
> dependency:
> 
> /usr/local/sbin/lighttpd:
> libpcre.so.1 => /usr/local/lib/libpcre.so.1 (0x800854000)
> libssl.so.8 => /usr/local/lib/libssl.so.8 (0x800acc000)
> libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x800d3f000)
> libc.so.7 => /lib/libc.so.7 (0x80114c000)
> libthr.so.3 => /lib/libthr.so.3 (0x80150)
> 
[...]
> 
> What can I do to fix that?

Are you generating your own packages? What software are you using to do
that?

Are you using some directive to enable ports provided ssl library?

A machine using my own generated packages using poudriere does not show
such behavior using ports trunk:

/usr/local/sbin/lighttpd:
libpcre.so.1 => /usr/local/lib/libpcre.so.1 (0x800857000)
libssl.so.8 => /usr/lib/libssl.so.8 (0x800acf000)
libcrypto.so.8 => /lib/libcrypto.so.8 (0x800e0)
libc.so.7 => /lib/libc.so.7 (0x80126d000)
libthr.so.3 => /lib/libthr.so.3 (0x80160d000)

A VM I have using official packages from 2016Q4 also gives the same
output(apart from the offsets which are slightly different) when
checking a just downloaded lighttpd package.

So I'd conclude there's something wrong affecting your builds. What
about a stray installation of a ports provided ssl library somewhere?

More information will be needed to really help you.

-- 
Guido Falsi 
___
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: Deluge error

2016-10-24 Thread Frank Seltzer

On Mon, 24 Oct 2016, Frank Seltzer wrote:

I upgraded libtorrent-rasterbar and py27-libtorrent-rasterbar and deluge no 
longer starts.  The error output is:


[ERROR   ] 08:40:04 main:245 
/usr/local/lib/python2.7/site-packages/libtorrent.so: Undefined symbol 
"_ZNK10libtorrent14announce_entry12can_announceEN5boost6chrono10time_pointINS2_12steady_clockENS2_8durationIlNS1_5ratioILl1ELl10EEEb"

Traceback (most recent call last):
 File "/usr/local/lib/python2.7/site-packages/deluge/main.py", line 238, in 
start_daemon

   Daemon(options, args)
 File "/usr/local/lib/python2.7/site-packages/deluge/core/daemon.py", line 
141, in __init__

   from deluge.core.core import Core
 File "/usr/local/lib/python2.7/site-packages/deluge/core/core.py", line 36, 
in 

   from deluge._libtorrent import lt
 File "/usr/local/lib/python2.7/site-packages/deluge/_libtorrent.py", line 
59, in 

   import libtorrent as lt
ImportError: /usr/local/lib/python2.7/site-packages/libtorrent.so: Undefined 
symbol 
"_ZNK10libtorrent14announce_entry12can_announceEN5boost6chrono10time_pointINS2_12steady_clockENS2_8durationIlNS1_5ratioILl1ELl10EEEb"


Have I fat-fingered something or is this a known problem?


I forgot to mention that I have rebuilt python27, py27\* and deluge.
___
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"


Deluge error

2016-10-24 Thread Frank Seltzer
I upgraded libtorrent-rasterbar and py27-libtorrent-rasterbar and deluge 
no longer starts.  The error output is:


[ERROR   ] 08:40:04 main:245 
/usr/local/lib/python2.7/site-packages/libtorrent.so: Undefined symbol 
"_ZNK10libtorrent14announce_entry12can_announceEN5boost6chrono10time_pointINS2_12steady_clockENS2_8durationIlNS1_5ratioILl1ELl10EEEb"

Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/deluge/main.py", line 238, 
in start_daemon

Daemon(options, args)
  File "/usr/local/lib/python2.7/site-packages/deluge/core/daemon.py", 
line 141, in __init__

from deluge.core.core import Core
  File "/usr/local/lib/python2.7/site-packages/deluge/core/core.py", line 
36, in 

from deluge._libtorrent import lt
  File "/usr/local/lib/python2.7/site-packages/deluge/_libtorrent.py", 
line 59, in 

import libtorrent as lt
ImportError: /usr/local/lib/python2.7/site-packages/libtorrent.so: 
Undefined symbol 
"_ZNK10libtorrent14announce_entry12can_announceEN5boost6chrono10time_pointINS2_12steady_clockENS2_8durationIlNS1_5ratioILl1ELl10EEEb"


Have I fat-fingered something or is this a known problem?
___
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"


lighttpd does not pull OpenSSL dependency

2016-10-24 Thread David Demelier

Hello,

Upgraded my system to 11.0-RELEASE-p1 and using 2016Q4 branch, I have a 
small issue regarding lighttpd dependency.


The binary is linked against the OpenSSL port, but it is not listed as a 
dependency:


/usr/local/sbin/lighttpd:
libpcre.so.1 => /usr/local/lib/libpcre.so.1 (0x800854000)
libssl.so.8 => /usr/local/lib/libssl.so.8 (0x800acc000)
libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x800d3f000)
libc.so.7 => /lib/libc.so.7 (0x80114c000)
libthr.so.3 => /lib/libthr.so.3 (0x80150)

The OpenSSL option is activated as well :

pkg info lighttpd :
lighttpd-1.4.41_1
Name   : lighttpd
Version: 1.4.41_1
Installed on   : Mon Oct 24 12:52:45 2016 CEST
Origin : www/lighttpd
Architecture   : freebsd:11:x86:64
Prefix : /usr/local
Categories : www
Licenses   : BSD3CLAUSE
Maintainer : pku...@anongoth.pl
WWW: http://www.lighttpd.net/
Comment: Secure, fast, compliant, and flexible Web Server
Options:
ATTR   : off
BZIP2  : on
DOCS   : on
FAM: off
GDBM   : off
IPV6   : on
LDAP   : off
LIBEV  : off
LUA: off
MEMCACHED  : off
MYSQL  : off
MYSQLAUTH  : off
OPENSSL: on
SPAWNFCGI  : off
VALGRIND   : off
WEBDAV : off
Shared Libs required:
libpcre.so.1
Annotations:
cpe: 
cpe:2.3:a:lighttpd:lighttpd:1.4.41:freebsd11:x64:1

repo_type  : binary
repository : server

What can I do to fix that?

Thanks!

--

David Demelier

___
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: Advise requested when a repo split occurs

2016-10-24 Thread Miroslav Lachman

Ultima wrote on 2016/10/22 21:14:

  Hello,

  Some what recently a couple of the ports I maintain split into two, one
being -server, and the other being -client. The code was more or less
cloned then removed some make args/files that one would be used to enable
both.

  Currently the code is so similar it would be possible to create a slave
port and use the same patches, makefile and plist with minimal changes,
however I have no idea the direction this split may go and this maybe short
lived. So onto my topic for this post.

Would it be better to create a new port with mostly duplicate code and
remove/add the little changes required? Or as previously stated make a
slave port and use the common code.

I am struggling to decide on this and would appreciate opinions.


I think it is fine to use slave port first. See some databases like 
MySQL or PostgreSQL.


When server and client will diverge too much in the future, you can 
rework it as too separate ports.


Miroslav Lachman
___
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

2016-10-24 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
+-+
www/py-beaker   | 1.8.0   | 1.8.1
+-+


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"


Vulnerabilities not included into FreeBSD vuxml

2016-10-24 Thread Pavel Timofeev
Hello, everyone!

I've found some vulnerabilities that are not included into freebsd
vuxml (or how this service is called?)

MySQL - 
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html#AppendixMSQL
VirtualBox - 
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html#AppendixOVIR
___
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: Jive prejudices

2016-10-24 Thread Vlad K.

On 2016-10-24 07:33, Horatiu Moldovan wrote:

Maybe off-topic, but I can't help wondering if we're close to the
point when a port should be removed because someone finds a
variable/type name "offensive".
Am I being paranoid? Let's wait and see.


I was just wondering the same. In which case, we must remove 
security/sudo from the tree because it contains racial slurs.


Yea, it's optional (INSULTS), but hey, so is installing any ports.


(btw, if it isn't clear, I am _NOT_ complaining about sudo. don't you 
dare remove insults, that's its best feature! The "racial" ones can be 
patched out with  INSULTS_CONFIGURE_ON+= --with-pc-insults, if anyone 
really WAS thinking about bringing a banhammer to that option...)



--

Vlad K.
___
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: misc/jive deleted

2016-10-24 Thread Greg Byshenk
On Mon, Oct 24, 2016 at 09:54:56AM +0200, Torsten Zuehlsdorff wrote:
> On 24.10.2016 09:16, Greg Byshenk wrote:
> > On Mon, Oct 24, 2016 at 01:05:52AM +0200, Julian H. Stacey wrote:
> >
> >> "Common decency" is disputable even in within USA; Europe is less
> >> infested with USA style prissy "political correctness", & other
> >> places less than Europe.  Censorship of Global FreeBSD to USA norms
> >> is Offensive.
> >
> > Point of information: I can't speak knowledgeably about the
> > rest of the world, but Europe tends to have -more- stringent
> > restrictions on abusive speech than does the USA.
> 
> Just at a side note - this statement is far to general. It depends very 
> heavenly on the country. There are around 50 different countries in 
> Europe which differs quite a lot - some have more restrictions and some 
> less than the USA. Its quite surprising.

Yes, it is overly general, but it was in response to an 
equally overly-general statement. To my knowledge, it also
is -generally- (though not univerally) true. (And, of course,
the nature of such restrictions is highly variable from one
state to another.) 

-- 
greg byshenk  -  gbysh...@byshenk.net  -  Leiden, NL
___
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: misc/jive deleted

2016-10-24 Thread Torsten Zuehlsdorff

On 24.10.2016 09:16, Greg Byshenk wrote:

On Mon, Oct 24, 2016 at 01:05:52AM +0200, Julian H. Stacey wrote:

Mark Linimon wrote:



It's not delusions of moral superiority.  It's common decency.



"Common decency" is disputable even in within USA; Europe is less
infested with USA style prissy "political correctness", & other
places less than Europe.  Censorship of Global FreeBSD to USA norms
is Offensive.


Point of information: I can't speak knowledgeably about the
rest of the world, but Europe tends to have -more- stringent
restrictions on abusive speech than does the USA.


Just at a side note - this statement is far to general. It depends very 
heavenly on the country. There are around 50 different countries in 
Europe which differs quite a lot - some have more restrictions and some 
less than the USA. Its quite surprising.


Greetings,
Torsten
___
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: misc/jive deleted

2016-10-24 Thread Greg Byshenk
On Mon, Oct 24, 2016 at 01:05:52AM +0200, Julian H. Stacey wrote:
> Mark Linimon wrote:

> > It's not delusions of moral superiority.  It's common decency.
 
> "Common decency" is disputable even in within USA; Europe is less
> infested with USA style prissy "political correctness", & other
> places less than Europe.  Censorship of Global FreeBSD to USA norms
> is Offensive.

Point of information: I can't speak knowledgeably about the
rest of the world, but Europe tends to have -more- stringent
restrictions on abusive speech than does the USA. 
 

-- 
greg byshenk  -  gbysh...@byshenk.net  -  Leiden, NL
___
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"