Re: Mariabackup core dump

2021-04-20 Thread Vincent Hoffman-Kazlauskas 



On 20/04/2021 18:34, Kurt Jaeger wrote:
> Hi!
> 
>> 
>>
>> This was posted 3 years ago, and I am having the identical issue. From what 
>> I can see on that page, no activity has taken place. Anyone have any ideas?
>>
>> (It does seem to work fine if you give the full path, but needless to say, 
>> I'm slightly concerned about that error)
> 
> Which version of FreeBSD and which version of mariadb can reproduce this ?
> 
I'd forgotten about this but I can easily reproduce it too.

FreeBSD 12.2
($18:57:32 <~>$) 1
root@copia # /usr/local/bin/mariabackup -v
/usr/local/bin/mariabackup based on MariaDB server 10.4.18-MariaDB
FreeBSD12.2 (amd64)
($18:57:37 <~>$) 0
root@copia # mariabackup -v
Segmentation fault (core dumped)
($18:57:49 <~>$) 139
root@copia # uname -v
FreeBSD 12.2-RELEASE-p3 GENERIC
($18:58:47 <~>$) 0
root@copia #

FreeBSD 11.4
root@banshee # /usr/local/bin/mariabackup -v
/usr/local/bin/mariabackup based on MariaDB server 10.4.18-MariaDB
FreeBSD11.4 (amd64)
($19:00:06 <~>$) 0
root@banshee # mariabackup -v
Segmentation fault (core dumped)
($19:00:13 <~>$) 139
root@banshee # uname -v
FreeBSD 11.4-RELEASE-p8 #0: Tue Feb 23 09:04:22 UTC 2021
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
($19:00:17 <~>$) 0


Built using poudriere

root@bsdpkgbuild:/usr/local/etc/poudriere.d/options # cat
databases_mariadb104-server/options
# This file is auto-generated by 'make config'.
# Options for mariadb104-server-10.4.6_1
_OPTIONS_READ=mariadb104-server-10.4.6_1
_FILE_COMPLETE_OPTIONS_LIST=AWS_KMS CONNECT_EXTRA DOCS WSREP GSSAPI_BASE
GSSAPI_HEIMDAL GSSAPI_MIT GSSAPI_NONE LZ4 LZO SNAPPY ZSTD INNOBASE
MROONGA OQGRAPH ROCKSDB SPHINX SPIDER TOKUDB ZMQ MSGPACK
OPTIONS_FILE_UNSET+=AWS_KMS
OPTIONS_FILE_SET+=CONNECT_EXTRA
OPTIONS_FILE_SET+=DOCS
OPTIONS_FILE_SET+=WSREP
OPTIONS_FILE_UNSET+=GSSAPI_BASE
OPTIONS_FILE_UNSET+=GSSAPI_HEIMDAL
OPTIONS_FILE_UNSET+=GSSAPI_MIT
OPTIONS_FILE_SET+=GSSAPI_NONE
OPTIONS_FILE_SET+=LZ4
OPTIONS_FILE_UNSET+=LZO
OPTIONS_FILE_UNSET+=SNAPPY
OPTIONS_FILE_UNSET+=ZSTD
OPTIONS_FILE_SET+=INNOBASE
OPTIONS_FILE_UNSET+=MROONGA
OPTIONS_FILE_UNSET+=OQGRAPH
OPTIONS_FILE_UNSET+=ROCKSDB
OPTIONS_FILE_SET+=SPHINX
OPTIONS_FILE_SET+=SPIDER
OPTIONS_FILE_UNSET+=TOKUDB
OPTIONS_FILE_UNSET+=ZMQ
OPTIONS_FILE_UNSET+=MSGPACK


root@bsdpkgbuild:/usr/local/etc/poudriere.d/options # cat
databases_mariadb104-client/options
# This file is auto-generated by 'make config'.
# Options for mariadb104-client-10.4.6_1
_OPTIONS_READ=mariadb104-client-10.4.6_1
_FILE_COMPLETE_OPTIONS_LIST= GSSAPI_BASE GSSAPI_HEIMDAL GSSAPI_MIT
GSSAPI_NONE
OPTIONS_FILE_UNSET+=GSSAPI_BASE
OPTIONS_FILE_UNSET+=GSSAPI_HEIMDAL
OPTIONS_FILE_UNSET+=GSSAPI_MIT
OPTIONS_FILE_SET+=GSSAPI_NONE

Regards,
Vince
___
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: Exim 4.94 Taint issues

2020-07-18 Thread Vincent Hoffman-Kazlauskas 



On 18/07/2020 02:34, The Doctor via freebsd-ports wrote:
> Trying Exim 4.94 and I am getting
> 
>





'/var/mail/doctor' (file or directory name for local_delivery transport)
not permitted
> 2020-07-17 19:30:09.145 [9601] 1jwbdm-00026Z-H4 == doc...@doctor.nl2k.ab.ca 
> R=localuser T=local_delivery defer (-1) DT=0.001s: Tainted '/var/mail/doctor' 
> (file or directory name for local_delivery transport) not permitted
> 2020-07-17 19:30:09.151 [9603] 1jwbcO-0001zD-9p == doc...@doctor.nl2k.ab.ca 
> R=localuser T=local_delivery defer (-1) DT=0.001s: Tainted '/var/mail/doctor' 
> (file or directory name for local_delivery transport) not permitted
> 2020-07-17 19:30:09.228 [9608] 1jwbdQ-00023D-Cx == doc...@nk.ca R=localuser 
> T=local_delivery defer (-1) DT=0.001s: Tainted '/var/mail/doctor' (file or 
> directory name for local_delivery transport) not permitted
> 
> Why is this happening?
> 
At a guess related to
https://github.com/Exim/exim/blob/master/src/README.UPDATING#L29


https://bugzilla.redhat.com/show_bug.cgi?id=1848926 had a reasonable
discussion with more links.

Regards,
Vince
___
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: Removal of www/apache22

2018-03-27 Thread Vincent Hoffman-Kazlauskas 


On 27/03/2018 13:52, Bernard Spil wrote:
> Hi all,
> 
> Just noticed that the Apache project has removed the patches they had
> for 2.2.34.
> 
>     http://www.apache.org/dist/httpd/patches/apply_to_2.2.34/
> 
> Combined with the security update of 2.4 branch to 2.4.33 leads me to
> believe that Apache 2.2 is now vulnerable and no patches will be provided.
> 
> If someone wishes to step up and get patches for 2.2 from e.g. RedHat,
> we may be able to keep the port alive for a bit longer. If no one steps
> up, I see no other way forward than to delete the port as indicated by
> the DEPRECATED variable and expiration date 2017-07-01 since July 2016.
> 

While I agree that apache 2.2 is now firmly dead, they moved the patches
for 2.2.34 to
https://archive.apache.org/dist/httpd/patches/apply_to_2.2.34/ , however
no new patches for the recent CVEs were added.


Vince



> Cheers,
> 
> Bernard.
> ___
> 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: Exim and CVE-2018-6789

2018-03-07 Thread Vincent Hoffman-Kazlauskas 


On 07/03/2018 20:13, Bob Willcox wrote:
> Hi All,
> 
> What is the status of FreeBSD's exim port regarding the CVE-2018-6789
> vulnerability?  Has it been fixed or is the fix in the works?
> 
> Thanks,
> Bob
> 

According to exim.org CVE-2018-6789 was fixed in 4.90.1. The port
version is 4.90.1 so yes it should be fixed.
see https://www.freshports.org/mail/exim/ for a handy overview.
Looks like the quarterly pkg repo is also up to date from a quick glance.


Vince
___
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: net/viamillipede seeks commiter

2018-03-07 Thread Vincent Hoffman-Kazlauskas 


On 07/03/2018 20:37, Vincent Hoffman-Kazlauskas wrote:
> 
> 
> On 07/03/2018 17:08, Ash Gokhale wrote:
>> On Wed, Mar 7, 2018 at 6:51 AM, Kurt Jaeger <p...@opsec.eu> wrote:
>>
>>> Hi!
>>>
>>>>> I've made peace with poudriere  in 10.4, 11.1 and 12 current jails with
>>>>> USES= uidfix, and also fixed the spurious pthreads cast that was
>>> choking
>>>>> gcc.  Would you  all try it again please?
>>>>> https://github.com/agokhale/freebsd-port-net-viamillipede/
>>> commits/master
>>>>
>>>> I've tested it on 10.3-i386, same build error as before. Maybe
>>>> the problem happens with 10.3, but not with 10.4. I'll retest with 10.4.
>>>
>>> Yes, builds with 10.4, fails with 10.3.
>>>
>>> --
>>> p...@opsec.eu+49 171 3101372 2 years to
>>> go !
>>>
>>
>>
>>
>> mat@'s feedback accepted,
>>
>> This is the error  from 10.3 release via poudriere jail:
>>
>> ===
>> ===>  Building for viamillipede-0.7
>> make[1]: "/usr/share/mk/bsd.own.mk" line 505: MK_DEBUG_FILES can't be set
>> by a user.
>> *** Error code 1
>>
>>
>> I'm not sure where to go from this; can I fence the port to build only on
>> 10.4+ ?
>>
>> I'll poke around in the jail for clues.
> 
> 
> Been a while but I think its something like
> 
> Something like this in the makefile
> 
> .if ${OSVERSION} > 1004000
> BROKEN=   Needs features from at least 10.4
> .endif
> 
> 
Doh
.if ${OSVERSION} < 1004000

of course.

> 
> Vince
> 
>> ___
>> 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"
> 
___
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: net/viamillipede seeks commiter

2018-03-07 Thread Vincent Hoffman-Kazlauskas 


On 07/03/2018 17:08, Ash Gokhale wrote:
> On Wed, Mar 7, 2018 at 6:51 AM, Kurt Jaeger  wrote:
> 
>> Hi!
>>
 I've made peace with poudriere  in 10.4, 11.1 and 12 current jails with
 USES= uidfix, and also fixed the spurious pthreads cast that was
>> choking
 gcc.  Would you  all try it again please?
 https://github.com/agokhale/freebsd-port-net-viamillipede/
>> commits/master
>>>
>>> I've tested it on 10.3-i386, same build error as before. Maybe
>>> the problem happens with 10.3, but not with 10.4. I'll retest with 10.4.
>>
>> Yes, builds with 10.4, fails with 10.3.
>>
>> --
>> p...@opsec.eu+49 171 3101372 2 years to
>> go !
>>
> 
> 
> 
> mat@'s feedback accepted,
> 
> This is the error  from 10.3 release via poudriere jail:
> 
> ===
> ===>  Building for viamillipede-0.7
> make[1]: "/usr/share/mk/bsd.own.mk" line 505: MK_DEBUG_FILES can't be set
> by a user.
> *** Error code 1
> 
> 
> I'm not sure where to go from this; can I fence the port to build only on
> 10.4+ ?
> 
> I'll poke around in the jail for clues.


Been a while but I think its something like

Something like this in the makefile

.if ${OSVERSION} > 1004000
BROKEN= Needs features from at least 10.4
.endif



Vince

> ___
> 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: pkg audit -F - insufficient privileges

2016-10-21 Thread Vincent Hoffman-Kazlauskas 


On 21/10/2016 16:24, Walter Schwarzenfeld wrote:
> |chmod 755 /var/db/pkg solved it.
> |
Possibly this is to do with the

"Update to 1.9.0

- Drop privileges in many commands
- Drop privileges when fetching a file"

Possibly dropping privs to early?

I found that my lazy pf rule to only allow root to have http outbound
connections broke remote updates with the upgrade to the 1.9.x version,
which I suspect to be related to the privilege dropping as an explicit
allow http to my update server fixed it.

Vince

> ___
> 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: Updating "wfimgr"

2016-10-21 Thread Vincent Hoffman-Kazlauskas 


On 21/10/2016 11:17, Gerard Seibert wrote:
> Unless I am in error, the "net-mgmt/wifimgr" port is based on the
> "NetworkManager" program. That program has been updated to version
> 1.4.2 . Is it possible
> to update the ports version from 1.11 to the latest stable version?
> 
I think you are confused, wifimgr is
http://opal.com/freebsd/ports/net-mgmt/wifimgr/ no relation to
networkmanager (still linux only) as far as I know.

Vince
___
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-update and portsnap users still at risk of compromise

2016-08-11 Thread Vincent Hoffman-Kazlauskas 
For those not on freebsd-announce (or reddit or anywhere else it got posted)

"FreeBSD Core statement on recent freebsd-update and related
vulnerabilities"
https://lists.freebsd.org/pipermail/freebsd-announce/2016-August/001739.html



Vince

On 11/08/2016 05:22, Julian Elischer wrote:
> On 11/08/2016 1:11 AM, Mail Lists via freebsd-security wrote:
>>
>>
>> sorry but this is blabla and does not come even near to answering the
>> real problem:
>>
>> It appears that freebsd and the US-government is more connected that
>> some of us might like:
>>
>> Not publishing security issues concerning update mechanisms - we all
>> can think WHY freebsd is not eager on this one.
>>
>> Just my thoughts...
> 
> this has been in discussion a lot in private circles within FreeBSD.
> It's not being ignored and a "correct" patch is being developed.
> 
> from one email I will quote just a small part..
> ===
> 
> As of yet, [the] patches for the libarchive vulnerabilities have not
> been released
> upstream to be pulled into FreeBSD. In the meantime, HardenedBSD has
> created
> patches for some of the libarchive vulnerabilities, the first[3] is being
> considered for inclusion in FreeBSD, at least until a complete fix is
> committed upstream, however the second[4] is considered too brute-force and
> will not be committed as-is. Once the patches are in FreeBSD and updated
> binaries are available, a Security Advisory will be issued.
> 
> ===
> so expect something soon.
> I will go on to say that the threat does need to come from an advanced
> MITM actor,
> though that does not make it a non threat..
> 
>>
>>
>>> Tuesday, August  9, 2016 8:21 PM UTC from Matthew Donovan
>>> :
>>>
>>> You mean operating system as distribution is a Linux term. There's
>>> not much
>>> different between HARDENEDBSD and FreeBSD besides that HardenedBSD fixes
>>> vulnerabilities and has a an excellent ASLR system compared to the
>>> proposed
>>> one for FreeBSD.
>>>
>>> On Aug 9, 2016 3:10 PM, "Roger Marquis" < marq...@roble.com > wrote:
>>>
 Timely update via Hackernews:

   >>> y-update-libarchive>

 Note in particular:

   "FreeBSD is still vulnerable to the portsnap, freebsd-update,
 bspatch,
   and libarchive vulnerabilities."

 Not sure why the portsec team has not commented or published an
 advisory
 (possibly because the freebsd list spam filters are so bad that
 subscriptions are being blocked) but from where I sit it seems that
 those exposed should consider:

   cd /usr/ports
   svn{lite} co  https://svn.FreeBSD.org/ports/head /usr/ports
   make index
   rm -rf /usr/sbin/portsnap /var/db/portsnap/*

 I'd also be interested in hearing from hardenedbsd users regarding the
 pros and cons of cutting over to that distribution.

 Roger



 On 2016-07-29 09:00, Julian Elischer wrote:
>> not sure if you've been contacted privately, but  I believe the
>> answer is
>> "we're working on it"
>>
> My concerns are as follows:
>
> 1. This is already out there, and FreeBSD users haven't been
> alerted that
> they should avoid running freebsd-update/portsnap until the
> problems are
> fixed.
>
> 2. There was no mention in the bspatch advisory that running
> freebsd-update to "fix" bspatch would expose systems to MITM
> attackers who
> are apparently already in operation.
>
> 3. Strangely, the "fix" in the advisory is incomplete and still
> permits
> heap corruption, even though a more complete fix is available. That's
> what prompted my post. If FreeBSD learned of the problem from the same
> source document we all did, which seems likely given the coincidental
> timing of an advisory for a little-known utility a week or two
> after that
> source document appeared, then surely FreeBSD had the complete fix
> available.
>
> ___
   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-secur...@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-security
>>> To unsubscribe, send any mail to "
>>> freebsd-security-unsubscr...@freebsd.org "
>>
>> Best regards,
>> Mail Lists
>> mli...@mail.ru
>> ___
>> freebsd-secur...@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-security
>> To unsubscribe, send any mail to
>> "freebsd-security-unsubscr...@freebsd.org"
>>
> 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to

Re: old ports/packages

2016-05-31 Thread Vincent Hoffman-Kazlauskas 


On 31/05/2016 14:17, Torsten Zuehlsdorff wrote:
> On 04.05.2016 19:17, Grzegorz Junka wrote:
> 
> Please excuse my late answer. I was right into vacation and need to
> handle some work right afterwards.
> 
 What you cannot do is create old-style packages from a new ports
 tree. This is because the ports infrastructure has been changing
 since pkg_install was deprecated, and pkg_install simply will not
 work with the current ports tree (and, as I understand it, cannot
 practically be modified in order to work with it).
>>>
>>> You are mostly correct. It is possible to modify and old ports-tree to
>>> get the new software in. I have at least two customer paying me for
>>> exact this work. But to be fair: it is no fun and harder with every
>>> new release :D
>>>
>>> I suppose what some customer need is an LTS version. Missing one is a
>>> show stopper for FreeBSD usage in many firms i talked to. I do not
>>> think this is a good idea from a technical point - but firms are slow
>>> and want stability.
>>
>> LTS of the base system or ports? The base system is already quite well
>> supported long-term.
> 
> This is a very good question, because it is not that clear. But let me
> state right here: No, the base system has not a good long-term support!
> 
> Yes, we have 2 years for the latest release, but 2 years seems to be
> very short for firms. Often they want 5 years.
> 
> And you are forced to update. You can't stay on say 10.1 or 10.2 because
> the support will end 2016. Which is short, because 10.2 was released in
> august 2015. This is only one and a half year.


To be fair the support is last release + 2 years, supporting a minor
version for more than 2 years seems unreasonable, compare to say redhat
a major commercial vendor. They provide up to 10 years sure but for a
major version ie 6 not a minor version ie 6.1. In fact their policy
page(1*) says "Under a Red Hat Enterprise Linux subscription, all
available RHSAs and RHBAs are provided for the current active minor
release until the availability of the next minor release" and that if
you want a minor release supported for longer you pay more and even then
its only approx 2 years, (example 6.7 (released 2015-07-22) ends July
31, 2017)
So far for me updating freebsd minor releases has been much the same
experience as upgrading Centos/RHEL minor releases.



Vince

(1*)
https://access.redhat.com/support/policy/updates/errata#Extended_Update_Support

> 
> Also on same points base system and ports are tied together. There were
> already changes in ports-tree which renders him unavailable for a older
> release just a couple of days after the version becomes unsupported.
> 
>> In this particular case it's probably not ports per
>> se but more the package manager? Because ports are not really FreeBSD's,
>> they are separate applications, each one of which is supported as long
>> as its author is willing to do so.
> 
> Yes - but the infrastructure changes. The ports are not really FreeBSD,
> the ports-tree is.
> 
>> Unless you mean the model adopted by some Linux companies, namely taking
>> the ports tree, freezing applications at some specific versions, and
>> only apply security and critical bug fixes to those applications? That
>> would mean creating and maintaining sources for all applications listed
>> in ports, rather than the ports tree itself! And that would be quite a
>> task considering that many applications have multiple configurable
>> compilation options. Not sure if it would be worth the effort if most
>> companies only need a limited set of applications from the whole tree.
>> On the other hand, if that was done then you would be left with no
>> work :)
> 
> Like i said: LTS is not a good idea from a technical point. But a
> missing LTS version is a main problem when trying to convince firms to
> change to FreeBSD.
> 
> 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"
> 
___
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: Port Request: Mono Moonlight

2014-03-28 Thread Vincent Hoffman 
Sorry for top posting but...
?http://www.mono-project.com/Moonlight/SecurityStatus
has the following information on Netflix


===
Silverlight 2 supports Microsoft /PlayReady/ Digital Rights Management
(DRM). This is the DRM solution being used by Netflix's Watch
Instantly service for streaming movies to PC (Windows-only) and Mac
computers.

Status: *unsupported*

==

And a quick google seems to indicate that the only way to watch netflix
on Linux is wine or a VM. So you'd have to look at one of those as a
solution.



Vince

--
On 28/03/2014 10:46, Paul Pathiakis wrote:
 Here's a big part of honesty I'm a senior systems architect.  I'm 
 building a company and hope to go live soon, after two years of developing 
 product and infrastructure.  I do this when not contracting/consulting.  


 I really don't have the time. :-(  Besides, haven't coded outside of 
 scripting in quite a while.  


 If the company is a success, I plan on having it financing a lot of projects. 
 :-)

 Once I retire (less than 15 years yeah, I'm old), I plan on spending a 
 lot of free time working for FreeBSD/ports/documentation. :-)

 P.




 On Friday, March 28, 2014 6:23 AM, John Marino freebsd.cont...@marino.st 
 wrote:
  
 On 3/27/2014 11:35, Paul Pathiakis wrote:

 Thank you, Anton. I'm now enlightened. I guess my main request for a
 port is the ability to watch Netflix.  Yes, I know Silverlight is
 dead, however, this hasn't stopped Netflix from it's continued use.
 :-) I didn't know how to request a port that plays Netflix video.
 ;-)
 I guess the first step to do that is identify the software that does
 this, and make a request that this software be added to ports.

 To improve your chances greatly of succeeding, you should attempt to
 write the port makefiles for that software and submit it via PR.  People
 are more likely to take a good base and make corrections than start from
 scratch.

 John
 ___
 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: pkg upgrade breaks with mariadb migration

2014-02-17 Thread Vincent Hoffman 
On 14/02/2014 15:24, Beeblebrox wrote:
 Well, I decided to try an old hack. Place in /etc/make.conf:
MYSQL_PORT= databases/mariadb55-client
 It seems I was hasty in responding. The hack works on host, but not
 in poudriere. Probably because the build looks for a mysql-library,
 finds it and is satisfied without checking whether the library
 actually came from databases/mysql55-client (meaning, the hack does
 nothing).

Bit late I know but for the poudriere repos I build I have
WITH_MYSQL_VER=55m
in my specific /usr/local/etc/poudriere.d/jailname-make.conf files
and havent seen any issues. I dont use any other repos though.

Vince



 -
 FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
 --
 View this message in context: 
 http://freebsd.1045724.n5.nabble.com/pkg-upgrade-breaks-with-mariadb-migration-tp5885723p5885993.html
 Sent from the freebsd-ports mailing list archive at Nabble.com.
 ___
 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: Massive ports update?

2014-02-04 Thread Vincent Hoffman 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 04/02/2014 17:29, Nikola Pavlović wrote:
 On 04/02/14 09:44, Colin Percival wrote:
 On 02/03/14 22:22, Xin Li wrote:
 On 2/3/14, 9:59 PM, Nikola Pavlović wrote:
 Was there a *huge* update to ports tree tonight between around
00:20 and
 06:30 CET?  Portsnap just fetched 24720 patches (this is more or less
 every port I guess), but I can't find anything in
 http://svnweb.freebsd.org/ports/head/ that would correspond to
this. I'm
 a bit worried. :)

 This may be related to my upgrade operation on the portsnap builder,
which
 happened around UTC midnight, right after a new snap snapshot is
taken.

 I'm pretty sure this resulted from changes to libarchive / bsdtar.  With
 them generating different tarballs for the same input, the portsnap build
 thinks that everything has changed.

 ... there's actually code on the portsnap builder to revert such changes,
 but I don't think delphij knew about it and I didn't realize he was
 upgrading the portsnap builder until too late.


 I see, thanks.  This sounds like mystery solved, but I can't be the only
 one who's seen this, so just to be sure---has anyone else had the same
 thing happen?  (Unfortunately, I don't have another FreeBSD machine at
 hand, unrelated to the one from the first post, to check.)

I had a huge list when I updated at approx 6am GMT.
I did initially wonder why there wasn't much to update considering this
but the explanation seems reasonable enough to me.

Vince



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJS8SVzAAoJEF4mgOY1fXowgdwP/0co37MQQQc1Fx94EIBi7g6a
ss/kOHxwisgvZwe3SN9Y3c5RYvqDhqvD+JdOD0C8rS73w+zi5D6FoGYvMf3IfZ91
FlkKihOcJjVpWlZLBbRtTGXgIBRNYIPnia8egs0aTKV+kQZGbzj5UwmvKvqRN7Dp
E3hWuMo4w5RrfFyrKep2Eq5IniWbyLoS7snTUug0cDTOP023H/hAsWV5GQMyPfZ1
jz5yD2EvqAUf1vlsESgVeO9wW8mAUA85iBRw1K48sQugsCG2M0cZ6/mxUKMoTdXj
AhNzn4M08gnG0x5EVpEABNPSY6/LUWWsPBYmcT7HENNz0g5xa2yg3FFcJREd/v5d
bNsBPhFQ96hExojT2f9DsRKnpxHbPQqLlAOD5uxkKtQ0byCBlfj2lN0NM1IrCiif
Xe/k+9U2YwWNnwSseF9OIE6pO6Pwt+IkXFn/XHnUGMVZBylTGIeJGUc1jvB7qbb4
pzX+gatjz4U1EYmIH1/bvgl5JUR/ly6aV0KV5odGaZsbVt8OIA/KKJjLp89F3X4F
5L/PvqwOVGC2ndWNB0erdzMgQ2pVw3Cvyycf+xwG0v8tv/Sq8ZQbtwopDCia+aaw
LaygbEAYHJY7ppXydE9G12Gc7kpvYFQrvtAeWE0E+G786ESIzyeZyAJsZ4uvy8mt
YGSrXZwtfRv1R5tCXXRS
=Zz3r
-END PGP SIGNATURE-

___
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

poke re:ports/181603 (net/mediatomb)

2013-11-14 Thread Vincent Hoffman 
Could someone commit ports/181603?
We're past maintainer timeout now and its the last port I use that wont
build for my (10-) server now.


Cheers,
Vince
___
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: [maintainer] Workaround: mariadb55-client and other ports using libmysqlclient.so

2013-10-15 Thread Vincent Hoffman 
I submitted a very badly formed PR about this, ports/1829
which was mean to follow on from my previous (ports/182565) but due to
me submitting without engaging brain more or less duplicated it.
Could this PR be closed?


Thanks,
Vince


On 15/10/2013 17:24, Alexandr Kovalenko wrote:
 Hello,

 Just want to notice you that build of ports which depend on
 libmysqlclient.so from MariaDB 5.5.33a is broken now on anything which
 is older than OSVERSION 152 (i.e. 9.x and older 10.x), 10-BETA1
 and 11-CURRENT are not affected. This happened due to introduction of
 libexecinfo dependency. Sorry about that :(

 The simpliest temporary workaround is, of course to create symlink:

 ln -sf /usr/local/lib/libexecinfo.so /usr/lib

 I'm working on a _proper_ solution with upstream now and will submit
 proper fix as soon as possible.

 Cheers,
 Alexandr.
 ___
 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: [maintainer] Workaround: mariadb55-client and other ports using libmysqlclient.so

2013-10-15 Thread Vincent Hoffman 
Doh 182993, brain still not engaged.

On 15/10/2013 20:21, Vincent Hoffman wrote:
 I submitted a very badly formed PR about this, ports/1829
 which was mean to follow on from my previous (ports/182565) but due to
 me submitting without engaging brain more or less duplicated it.
 Could this PR be closed?


 Thanks,
 Vince


 On 15/10/2013 17:24, Alexandr Kovalenko wrote:
 Hello,

 Just want to notice you that build of ports which depend on
 libmysqlclient.so from MariaDB 5.5.33a is broken now on anything which
 is older than OSVERSION 152 (i.e. 9.x and older 10.x), 10-BETA1
 and 11-CURRENT are not affected. This happened due to introduction of
 libexecinfo dependency. Sorry about that :(

 The simpliest temporary workaround is, of course to create symlink:

 ln -sf /usr/local/lib/libexecinfo.so /usr/lib

 I'm working on a _proper_ solution with upstream now and will submit
 proper fix as soon as possible.

 Cheers,
 Alexandr.
 ___
 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


___
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: [maintainer] Workaround: mariadb55-client and other ports using libmysqlclient.so

2013-10-15 Thread Vincent Hoffman 
This lets me build apr1 and py-MySQLdb (poudriere logs available if wanted)
Looks good to me.

Vince

On 15/10/2013 20:28, Alexandr Kovalenko wrote:
 On Tue, Oct 15, 2013 at 10:21 PM, Vincent Hoffman vi...@unsane.co.uk wrote:
 ports/182565
 I've submitted fix. Could you please try it and check if it helps?

 http://www.freebsd.org/cgi/query-pr.cgi?pr=183001
 ___
 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

anyone else using WITH_MYSQL_VER=55m and having problems?

2013-10-04 Thread Vincent Hoffman 
I've opened a PR for apr1 but i'm thinking maybe it should be for mariadb55?
http://www.freebsd.org/cgi/query-pr.cgi?pr=182565

a working build (against mysql55) has

checking for mysql_config... /usr/local/bin/mysql_config
  adding -lmysqlclient_r to LDFLAGS
  adding -pthread to LDFLAGS
  adding -lz to LDFLAGS
  adding -lm to LDFLAGS
  setting LIBS to -L/usr/local/lib/mysql -lmysqlclient_r  -pthread -lz -lm
configure: checking for mysql in /usr/local
checking for mysql.h... yes
checking for mysql_init in -lmysqlclient_r... yes
checking for my_global.h... yes
checking for mysql_init in -lmysqlclient_r... (cached) yes
checking for my_sys.h... yes
checking for mysql_init in -lmysqlclient_r... (cached) yes
  adding -I/usr/local/include/mysql to APRUTIL_PRIV_INCLUDES
  setting LDADD_dbd_mysql to -L/usr/local/lib/mysql -lmysqlclient_r  -pthread 
-lz -lm -lmysqlclient_r -L/usr/local/lib/mysql -lmysqlclient_r  -pthread -lz 
-lm


The failed build (with mariadb55)

checking for mysql_config... /usr/local/bin/mysql_config
  adding -I/usr/local/include/mysql/.. to CPPFLAGS
  adding -lmysqlclient_r to LDFLAGS
  adding -pthread to LDFLAGS
  adding -lz to LDFLAGS
  adding -lm to LDFLAGS
  adding -lexecinfo to LDFLAGS
  setting LIBS to -L/usr/local/lib/mysql -lmysqlclient_r  -pthread -lz -lm 
-lexecinfo
configure: checking for mysql in /usr/local
checking for mysql.h... yes
checking for mysql_init in -lmysqlclient_r... no
checking for my_global.h... yes
checking for mysql_init in -lmysqlclient_r... (cached) no
checking for my_sys.h... yes
checking for mysql_init in -lmysqlclient_r... (cached) no
checking for mysql/mysql.h... yes
checking for mysql_init in -lmysqlclient_r... (cached) no
checking for mysql/my_global.h... yes
checking for mysql_init in -lmysqlclient_r... (cached) no
checking for mysql/my_sys.h... yes
checking for mysql_init in -lmysqlclient_r... (cached) no

Thanks,
Vince
___
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: anyone else using WITH_MYSQL_VER=55m and having problems?

2013-10-04 Thread Vincent Hoffman 
On 04/10/2013 14:29, Florian Smeets wrote:
 On 04.10.13 13:45, Vincent Hoffman wrote:
 I've opened a PR for apr1 but i'm thinking maybe it should be for
mariadb55?
 http://www.freebsd.org/cgi/query-pr.cgi?pr=182565

 a working build (against mysql55) has


   setting LDADD_dbd_mysql to -L/usr/local/lib/mysql -lmysqlclient_r 
-pthread -lz -lm -lmysqlclient_r -L/usr/local/lib/mysql -lmysqlclient_r 
-pthread -lz -lm



 The failed build (with mariadb55)

   setting LIBS to -L/usr/local/lib/mysql -lmysqlclient_r  -pthread
-lz -lm -lexecinfo

 I see the error, it's a typo

 -LIB_DEPENDS=libexecinfo.so:${PORTSDIR}/devel/libexecinfo
 +LIB_DEPENDS+=libexecinfo.so:${PORTSDIR}/devel/libexecinfo

 I'll test this and commit the fix shortly.
Thanks for the quick reply/fix
Vince

 Florian



___
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: oddness with py27-ldap2 port vs poudiere package, also how to sign digests.txz?

2013-07-02 Thread Vincent Hoffman 
Not sure this will be useful to anyone but it turned out that the reason
py-ldap2 was being odd is because i was building openldap-client and
openldap-sasl-client, it was building against the sasl-client but I only
had the non sasl client installed.

Thanks to the pkg developers for fixing the digests.txz issue too.


Vince

On 28/06/2013 15:06, Vincent Hoffman wrote:
 I build my packages locally using poudriere-devel
 root@bsdpkgbuild:~ # pkg info poudriere-devel
 poudriere-devel-3.0.99.20130614

 I am trying to add py-ldap2 however I'm getting errors installing
 py27-ldap2 from packages which I dont when I build it locally.

 The output when I try to install the package I have build and put in my
 repo:

 root@ipamtest:~ # pkg install py27-ldap2
 Updating repository catalogue
 digests.txz   
 
 100%   22KB  22.4KB/s  22.4KB/s   00:00
 pkg: fopen((null)): Bad address
 pkg: /etc/ssl/certs/pkg.cert: error:04077068:rsa routines:RSA_verify:bad
 signature
 pkg: Invalid signature, removing repository.
 pkg: No digest falling back on legacy catalog format
 repo.txz  
 
 100%  185KB 185.4KB/s 185.4KB/s   00:00
 pkg: Repo repo-packagesite upgrade schema 2001 to 2002: Modify shlib
 tracking to add 'provided' capability
 pkg: Repo repo-packagesite upgrade schema 2002 to 2003: Add abstract
 metadata capability
 pkg: Repo repo-packagesite upgrade schema 2003 to 2004: Add manifest
 digest field
 pkg: Repo repo-packagesite upgrade schema 2004 to 2005: Rename
 'abstract metadata' to 'annotations'
 The following 1 packages will be installed:

 Installing py27-ldap2: 2.4.12

 The installation will require 724 kB more space

 107 kB to be downloaded

 Proceed with installing packages [y/N]: y
 pkg: cached package py27-ldap2-2.4.12: checksum mismatch, fetching from
 remote
 py27-ldap2-2.4.12.txz 
 
 100%  108KB 107.6KB/s 107.6KB/s   00:00
 Checking integrity... done
 [1/1] Installing py27-ldap2-2.4.12...defines: HAVE_SASL HAVE_TLS
 HAVE_LIBLDAP_R
 extra_compile_args:
 extra_objects:
 include_dirs: /opt/openldap-RE24/include /usr/include/sasl /usr/include
 library_dirs: /opt/openldap-RE24/lib /usr/lib
 libs: ldap_r
 file Lib/ldap.py (for module ldap) not found
 file Lib/ldap/controls.py (for module ldap.controls) not found
 file Lib/ldap/extop.py (for module ldap.extop) not found
 file Lib/ldap/schema.py (for module ldap.schema) not found
 warning: no files found matching 'Makefile'
 warning: no files found matching 'Modules/LICENSE'
 file Lib/ldap.py (for module ldap) not found
 file Lib/ldap/controls.py (for module ldap.controls) not found
 file Lib/ldap/extop.py (for module ldap.extop) not found
 file Lib/ldap/schema.py (for module ldap.schema) not found
 file Lib/ldap.py (for module ldap) not found
 file Lib/ldap/controls.py (for module ldap.controls) not found
 file Lib/ldap/extop.py (for module ldap.extop) not found
 file Lib/ldap/schema.py (for module ldap.schema) not found
 In file included from Modules/LDAPObject.c:9:
 Modules/errors.h:8:18: error: lber.h: No such file or directory
 Modules/errors.h:9:18: error: ldap.h: No such file or directory
 In file included from Modules/LDAPObject.c:9:
 Modules/errors.h:12: error: expected ')' before '*' token
 In file included from Modules/LDAPObject.c:11:
 Modules/LDAPObject.h:12:2: error: #error Current python-ldap requires
 OpenLDAP 2.x
 In file included from Modules/LDAPObject.c:11:
 Modules/LDAPObject.h:23: error: expected specifier-qualifier-list before
 'LDAP'
 Modules/LDAPObject.h:31: error: expected ')' before '*' token
 In file included from Modules/LDAPObject.c:12:
 Modules/ldapcontrol.h:11: error: expected ')' before '*' token
 Modules/ldapcontrol.h:12: error: expected declaration specifiers or
 '...' before 'LDAPControl'
 Modules/ldapcontrol.h:13: error: expected ')' before '*' token
 In file included from Modules/LDAPObject.c:13:
 Modules/message.h:11: error: expected ')' before '*' token
 In file included from Modules/LDAPObject.c:14:
 Modules/berval.h:10: warning: 'struct berval' declared inside parameter list
 Modules/berval.h:10: warning: its scope is only this definition or
 declaration, which is probably not what you want
 Modules/berval.h:12: warning: 'struct berval' declared inside parameter list
 Modules/berval.h:13: warning: 'struct berval' declared inside parameter list
 Modules/LDAPObject.c:18:18: error: sasl.h: No such file or directory
 Modules/LDAPObject.c:26: error: expected ')' before '*' token
 Modules/LDAPObject.c: In function 'dealloc':
 Modules/LDAPObject.c:42: error: 'LDAPObject' has no member named 'ldap'
 Modules/LDAPObject.c:43: error: 'LDAPObject' has no member named 'valid'
 Modules/LDAPObject.c:44: error: 'LDAPObject' has no member named '_save'
 Modules/LDAPObject.c:44: error

oddness with py27-ldap2 port vs poudiere package, also how to sign digests.txz?

2013-06-28 Thread Vincent Hoffman 
I build my packages locally using poudriere-devel
root@bsdpkgbuild:~ # pkg info poudriere-devel
poudriere-devel-3.0.99.20130614

I am trying to add py-ldap2 however I'm getting errors installing
py27-ldap2 from packages which I dont when I build it locally.

The output when I try to install the package I have build and put in my
repo:

root@ipamtest:~ # pkg install py27-ldap2
Updating repository catalogue
digests.txz 
  
100%   22KB  22.4KB/s  22.4KB/s   00:00
pkg: fopen((null)): Bad address
pkg: /etc/ssl/certs/pkg.cert: error:04077068:rsa routines:RSA_verify:bad
signature
pkg: Invalid signature, removing repository.
pkg: No digest falling back on legacy catalog format
repo.txz
  
100%  185KB 185.4KB/s 185.4KB/s   00:00
pkg: Repo repo-packagesite upgrade schema 2001 to 2002: Modify shlib
tracking to add 'provided' capability
pkg: Repo repo-packagesite upgrade schema 2002 to 2003: Add abstract
metadata capability
pkg: Repo repo-packagesite upgrade schema 2003 to 2004: Add manifest
digest field
pkg: Repo repo-packagesite upgrade schema 2004 to 2005: Rename
'abstract metadata' to 'annotations'
The following 1 packages will be installed:

Installing py27-ldap2: 2.4.12

The installation will require 724 kB more space

107 kB to be downloaded

Proceed with installing packages [y/N]: y
pkg: cached package py27-ldap2-2.4.12: checksum mismatch, fetching from
remote
py27-ldap2-2.4.12.txz   
  
100%  108KB 107.6KB/s 107.6KB/s   00:00
Checking integrity... done
[1/1] Installing py27-ldap2-2.4.12...defines: HAVE_SASL HAVE_TLS
HAVE_LIBLDAP_R
extra_compile_args:
extra_objects:
include_dirs: /opt/openldap-RE24/include /usr/include/sasl /usr/include
library_dirs: /opt/openldap-RE24/lib /usr/lib
libs: ldap_r
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/controls.py (for module ldap.controls) not found
file Lib/ldap/extop.py (for module ldap.extop) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
warning: no files found matching 'Makefile'
warning: no files found matching 'Modules/LICENSE'
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/controls.py (for module ldap.controls) not found
file Lib/ldap/extop.py (for module ldap.extop) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/controls.py (for module ldap.controls) not found
file Lib/ldap/extop.py (for module ldap.extop) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
In file included from Modules/LDAPObject.c:9:
Modules/errors.h:8:18: error: lber.h: No such file or directory
Modules/errors.h:9:18: error: ldap.h: No such file or directory
In file included from Modules/LDAPObject.c:9:
Modules/errors.h:12: error: expected ')' before '*' token
In file included from Modules/LDAPObject.c:11:
Modules/LDAPObject.h:12:2: error: #error Current python-ldap requires
OpenLDAP 2.x
In file included from Modules/LDAPObject.c:11:
Modules/LDAPObject.h:23: error: expected specifier-qualifier-list before
'LDAP'
Modules/LDAPObject.h:31: error: expected ')' before '*' token
In file included from Modules/LDAPObject.c:12:
Modules/ldapcontrol.h:11: error: expected ')' before '*' token
Modules/ldapcontrol.h:12: error: expected declaration specifiers or
'...' before 'LDAPControl'
Modules/ldapcontrol.h:13: error: expected ')' before '*' token
In file included from Modules/LDAPObject.c:13:
Modules/message.h:11: error: expected ')' before '*' token
In file included from Modules/LDAPObject.c:14:
Modules/berval.h:10: warning: 'struct berval' declared inside parameter list
Modules/berval.h:10: warning: its scope is only this definition or
declaration, which is probably not what you want
Modules/berval.h:12: warning: 'struct berval' declared inside parameter list
Modules/berval.h:13: warning: 'struct berval' declared inside parameter list
Modules/LDAPObject.c:18:18: error: sasl.h: No such file or directory
Modules/LDAPObject.c:26: error: expected ')' before '*' token
Modules/LDAPObject.c: In function 'dealloc':
Modules/LDAPObject.c:42: error: 'LDAPObject' has no member named 'ldap'
Modules/LDAPObject.c:43: error: 'LDAPObject' has no member named 'valid'
Modules/LDAPObject.c:44: error: 'LDAPObject' has no member named '_save'
Modules/LDAPObject.c:44: error: 'LDAPObject' has no member named '_save'
Modules/LDAPObject.c:45: error: 'LDAPObject' has no member named 'ldap'
Modules/LDAPObject.c:46: error: 'LDAPObject' has no member named '_save'
Modules/LDAPObject.c:46: error: 'LDAPObject' has no member named '_save'
Modules/LDAPObject.c:47: error: 'LDAPObject' has no member named 'valid'
Modules/LDAPObject.c:49: error: 'LDAPObject' has no member named 'ldap'
Modules/LDAPObject.c: In function 'not_valid':

missing/changed config options on various ports

2013-06-06 Thread Vincent Hoffman 
Hi,
I've got a machine running poudriere to build package, at my last update
(around midday BST) the optsions for a number of ports seem to have
vanished or changed oddly

 Options changed, deleting: exim-4.80.1_2.txz
 Pkg: AUTH_CRAM_MD5 AUTH_PLAINTEXT AUTH_SPA CDB CONTENT_SCAN DAEMON 
DISABLE_D_OPT DKIM DNSDB DSEARCH EMBEDDED_PERL ICONV IPV6 LMTP LSEARCH MAILDIR 
MYSQL NIS OLD_DEMIME PAM PASSWD SA_EXIM SPF SQLITE SUID TLS 
 New: 
 Options changed, deleting: p5-Mail-SpamAssassin-3.3.2_8.txz
 Pkg: AS_ROOT DKIM GNUPG RAZOR SPAMC SSL 
 New: 
 Options changed, deleting: mediatomb-0.12.1_10.txz
 Pkg: CURL EXTERNAL_TRANSCODING FFMPEG FFMPEGTHUMBNAILER JS LIBEXIF MYSQL 
SQLITE TAGLIB 
 New: CURL EXTERNAL_TRANSCODING FFMPEG FFMPEGTHUMBNAILER JS LIBEXIF MYSQL 
MYSQL SQLITE SQLITE TAGLIB 

doing a make config in the relevent port directories seems to confirm something 
is up
root@bsdpkgbuild:/usr/ports/mail/p5-Mail-SpamAssassin # make config
=== No options to configure
root@bsdpkgbuild:/usr/ports/mail/p5-Mail-SpamAssassin # cd -
root@bsdpkgbuild:/usr/ports/mail/exim # make config
=== No options to configure


I'm guessing this is related to the removal of the old options framework? 
should I put in PRs for the individual ports or is there a more general plan in 
effect?

Thanks,
Vince


___
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] current switched by default to pkgng

2012-10-19 Thread Vincent Hoffman 
On 19/10/2012 15:39, Alex Keda wrote:
 On 10.10.2012 17:44, Baptiste Daroussin wrote:
 Hi all,

 If you are using the ports tree on a FreeBSD current setup, then you are
 concerned by the announce.

 As nvidia-drivers has been fixed and is now properly working with pkgng, the
 ports tree as been switch by default to use pkgng on FreeBSD Current based on
 version = 117 which was the version when we tested the switch code.

 Make sure to read UPDATING (from ports) to correctly migrate your system or 
 find
 instruction to make your system still running with legacy pkg_install tools.

 regards,
 Bapt

 pkg command does not have key for list options - no autocompletions

 for example, for service command, I use
 complete service'n/*/`service -l`/'
 in .cshrc

 what I can use for pkg command?

horrible but working example
pkg help 21 | sed -e '1,/Commands supported:/d ; /For more information
on the different commands/,$d; s/^   *// ; s/  .*.*$// ;/^$/d'

There's bound to be better ways, I was just bored enough to knock this up.
note s/^*//   is a tab, while s/  .*.*$// is 2 spaces
dont think our sed has any other way to express tab other than an actual
tab (ctrl-v then tab on the command line)

Vince
 ___
 freebsd-curr...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-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/lighttpd: lighttpd won't start anymore after SSL Update in 8.1-PRERELEASE (2010-05-27 09:34:56: (network.c.529) SSL: error:00000000:lib(0):func(0):reason(0))

2010-05-27 Thread Vincent Hoffman 
On 27/05/2010 08:39, O. Hartmann wrote:
 Since I performed a make buildworld and installed everything and after
 an update of the ports tree (with which lighttpd was updated from
 lighttpd-1.4.26 to lighttpd-1.4.26_1 I receive this error when trying
 to start lighttpd:

 2010-05-27 09:34:56: (network.c.529) SSL:
 error::lib(0):func(0):reason(0)

 Are there any suggestions/known issues/workaround or is this a serious
 error and should be ready for a PR?

It sounds like this error
http://dev.modmancer.com/index.php/2010/05/23/lighttpd-and-network-c-529-ssl-error/
There is a fix in that URL but a PR if there isnt one would probably
make sense.


Vince

 Thanks ina advance,
 Oliver
 ___
 freebsd-sta...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-stable
 To unsubscribe, send any mail to freebsd-stable-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: [Call For Testing] VirtualBox for FreeBSD! take 6

2009-09-08 Thread Vincent Hoffman 
Danny Braniss wrote:
 [...]
   
 ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is no
 longer available, there is a
 ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2
 then again in ports/emulatores/virtualbox the version is 3.0.51r6,

 can someone please explain?
 

 hi, the above was my question, which was totally ignored, not nice.
 I will try and refrase it:
 the call for testing is for a version (2.2.51r20457) which is not available, 
 while
 the ports is 3.0.51r6, so while I managed to compile it, it complains 
 that COM
 is not running, all this under 8BETA-3, both under 32 and 64 bit.
 thnaks,
   danny

   
The call for testing went out on 11th june
(http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008061.html)  
I can only assume it was considered tested and working as the port was
committed on 15th june
(http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/virtualbox/Makefile?rev=1.1;content-type=text%2Fplain)

Since then there have been 4 updates to the port. The last of which
updated it to 3.0.51r6 on august 14th.

I would say the call for testing is no longer valid, please use the
version in ports.


Vince

 ___
 freebsd-curr...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-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