Re: www/joomla3 is no longer in the FreeBSD pkg repo

[Chris Rees]

On 04/03/2021 16:16, Chris wrote:

On 2021-03-04 00:50, Patrick M. Hausen wrote:

Hi all,


Am 04.03.2021 um 02:17 schrieb Chris Rees :
The problem is, that although the php80 flavour does not depend on 
pecl-pdflib, the default flavour does,
which means that the package will not be built as it you have to 
agree to pecl-pdflib's licence.


I am not a lawyer. That being said I have done some homework and did 
a lot if reading
in February 2020. Sent my findings to the port maintainer of 
print/pdflib, but did not get

a response, unfortunately.

My conclusion is that you don't need to agree to PDFlib GmbH's 
license, because all
of the legalese on their home page applies to a completely different 
product than the

one used by pecl-pdflib.

But step by step ...

1.    pecl-pdflib is published under the PHP license, so it is 
clearly open source.
2.    The FreeBSD port is not based on pdflib, but pdflib-lite - this 
is the crucial point.

3.    pdflib-lite is a product abandoned by PDFlib GmbH in 2011.
4.    pdflib-lite archives come with an open source license bundled 
in the archive.
5.    This is the only license applicable to our case. All the other 
licensing stuff on their
website applies to pdflib - *which is a completely different 
product*.
6.    The license bundled with pdflib-lite explicitly permits the 
distribution of binaries as
long as the license document and some other auxiliary files are 
included.
7.    The port does this and puts the necessary documents in 
/usr/local/share/doc/pdflib.


You won't find any information about pdflib-lite on PDFlib GmbH's 
website, because
they pulled it. Nonetheless the source is "out there", bundled with a 
permissive license

which cannot be taken back.

So the entire discussion is moot - as long as pecl-pdflib can be 
built with pdflib-lite.


The problem with the port/packages infrastructure is that this line in
ports/print/pdflib/Makefile
is nonsense, IMHO:

RESTRICTED= Many odd restrictions on usage and distribution


Download the pdflib-lite tarball and see the documents for yourself. 
I am repeating myself:
all the legalese on the PDFlib GmbH website *does not apply* to this 
product (pdflib-lite).
I needed the pdflib-lite for a script I cobbled up to batch convert 
to/from text/pdf
a couple of years ago. I can confirm that the lib is with a 
*non*restrictive license.

My humble suggestion;
Can't we please simply create a pdflib-lite port, and be done with all 
this and related? :-)


The pdflib that we have in the port *is* pdflib-lite :)   Hence my 
proposed review to ale@.


Chris

___
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: www/joomla3 is no longer in the FreeBSD pkg repo

[Chris Rees]

On 04/03/2021 13:21, Patrick M. Hausen wrote:

Hi Chris,


Am 04.03.2021 um 14:11 schrieb Chris Rees :

$ ll PDFlib-Lite-7.0.5p3.tar.gz
-rw-r--r--  1 pmh  staff  8179201  4 Mär 11:38 PDFlib-Lite-7.0.5p3.tar.gz
$ shasum PDFlib-Lite-7.0.5p3.tar.gz
42e0605ae21f4b6d25fa2d20e78fed6df36fbaa9  PDFlib-Lite-7.0.5p3.tar.gz

Which contains the old license I am referring to.

Anyone want a copy of that archive?

That's the actual archive that's been in the port since 2012 :)

Then whence the source tree with the entirely different license you linked to?
I did a `make fetch extract` with a ports tree just checked our from HEAD and
I found the "new" license. So someone must have replaced the archive?


There are two ways around this if you want joomla3 packaged:

- Negotiate with PDFlib GmbH (you might be better at German than me...) to 
allow for commercial use of pdflib (unlikely)

- Stop joomla3 depending on PDFlib by default.

Does it work without PDFlib?  If so, I suggest the latter, and that's easy to 
do.

I am not running joomla at all. We simply provide print/pecl-pdflib in our 
hosting
environment by default so when the `RESTRICTED` clause was introduced
into the Makefile of print/pdflib, I researched the license, came to the 
conclusion
that we can provide that software, if we tell the customer that they need a 
commercial
license, if they actually use it in production.

I tried to get into contact with Alex Dupre about this but he did not answer my 
mail.

Eventually we just set:

.if ${.CURDIR:M*print/pecl-pdflib*}
 _LICENSE_STATUS=accepted
.endif

in our poudriere.


And now I was triggered by the discussion. The license does permit binary 
distribution.
The necessary documents are included in the package. So if you just add a 
pkg-message
that hints at the docs, all should be well, IMHO - but that's not mine to 
decide.


I agree.

Having looked further at the licence, it would appear that commercial 
use is allowed as part of a Free software product:


[...] exempt users listed below are granted a world-wide, royalty-free, 
nonexclusive license to use the program.

2.1 Open Source Developer Exemption
Use of the program as part of an integrated product is exempt from 
commercial licensing provided the
integrated product is available under a license which has been approved 
by the Open Source Initiative
OSI (www.opensource.org), complete source code for the integrated 
product is available to anyone
free of charge, and the availability of source code is announced on a 
publicly accessible Web site.
Source code means the preferred machine-readable form in which a 
programmer would modify the

software.

As Joomla is Free (GPL), it is absolutely fine to use, even for-profit 
as I read it.


What a confusing mess...

I've suggested a couple of changes to the port-- I'll wait on the 
maintainer's feedback.


https://reviews.freebsd.org/D29059

Chris

___
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: www/joomla3 is no longer in the FreeBSD pkg repo

[Chris Rees]

Hi,

On 04/03/2021 10:44, Patrick M. Hausen wrote:

Hi,


Am 04.03.2021 um 11:26 schrieb Patrick M. Hausen :

I would be very interested to know when the distribution file on the FreeBSD 
"distfiles"
archive was exchanged, and and why?

I did a quick search on one of our older poudriere installations and *bingo*.
In the distfile cache I found this file:

$ ll PDFlib-Lite-7.0.5p3.tar.gz
-rw-r--r--  1 pmh  staff  8179201  4 Mär 11:38 PDFlib-Lite-7.0.5p3.tar.gz
$ shasum PDFlib-Lite-7.0.5p3.tar.gz
42e0605ae21f4b6d25fa2d20e78fed6df36fbaa9  PDFlib-Lite-7.0.5p3.tar.gz

Which contains the old license I am referring to.

Anyone want a copy of that archive?


That's the actual archive that's been in the port since 2012 :)

It seems to me that dist-mirror and pkg-mirror in 
ports/Mk/bsd.licenses.mk could be met by this, but not auto-accept.  
It'd mean that we had non-free/restricted software being distributed in FTP.


There are two ways around this if you want joomla3 packaged:

- Negotiate with PDFlib GmbH (you might be better at German than me...) 
to allow for commercial use of pdflib (unlikely)


- Stop joomla3 depending on PDFlib by default.

Does it work without PDFlib?  If so, I suggest the latter, and that's 
easy to do.


Chris

___
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: www/joomla3 is no longer in the FreeBSD pkg repo

[Chris Rees]

Hi Patrick,

On 04/03/2021 08:50, Patrick M. Hausen wrote:

Hi all,


Am 04.03.2021 um 02:17 schrieb Chris Rees :
The problem is, that although the php80 flavour does not depend on pecl-pdflib, 
the default flavour does,
which means that the package will not be built as it you have to agree to 
pecl-pdflib's licence.

I am not a lawyer. That being said I have done some homework and did a lot if 
reading
in February 2020. Sent my findings to the port maintainer of print/pdflib, but 
did not get
a response, unfortunately.

My conclusion is that you don't need to agree to PDFlib GmbH's license, because 
all
of the legalese on their home page applies to a completely different product 
than the
one used by pecl-pdflib.

But step by step ...

1.  pecl-pdflib is published under the PHP license, so it is clearly open 
source.
2.  The FreeBSD port is not based on pdflib, but pdflib-lite - this is the 
crucial point.
3.  pdflib-lite is a product abandoned by PDFlib GmbH in 2011.
4.  pdflib-lite archives come with an open source license bundled in the 
archive.
5.  This is the only license applicable to our case. All the other 
licensing stuff on their
website applies to pdflib - *which is a completely different product*.
6.  The license bundled with pdflib-lite explicitly permits the 
distribution of binaries as
long as the license document and some other auxiliary files are 
included.
7.  The port does this and puts the necessary documents in 
/usr/local/share/doc/pdflib.

You won't find any information about pdflib-lite on PDFlib GmbH's website, 
because
they pulled it. Nonetheless the source is "out there", bundled with a 
permissive license
which cannot be taken back.

So the entire discussion is moot - as long as pecl-pdflib can be built with 
pdflib-lite.

The problem with the port/packages infrastructure is that this line in 
ports/print/pdflib/Makefile
is nonsense, IMHO:

RESTRICTED= Many odd restrictions on usage and distribution


Download the pdflib-lite tarball and see the documents for yourself. I am 
repeating myself:
all the legalese on the PDFlib GmbH website *does not apply* to this product 
(pdflib-lite).


I'm afraid that this, which I found in pdflib-lite's readme.txt [1] 
differs on that opinion.




- PDFlib Lite
  Open-source edition for basic PDF generation, free for personal use.
  PDFlib Lite does not support all languages, and is not available on
  EBCDIC platforms.


"Free for personal use" is not Free, and that's why the licence must be 
acknowledged.


Unless you have found explicit mention that it is definitely under the 
PHP licence?


Chris

[1] https://github.com/Distrotech/PDFlib-Lite

___
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: www/joomla3 is no longer in the FreeBSD pkg repo

[Chris Rees]

On 25/02/2021 04:59, Greg Rivers via freebsd-ports wrote:

On Sunday, 4 October 2020 Greg Rivers wrote:

According to the poudriere build cluster (), joomla3 is 
being skipped for reason "php74-pecl-pdflib-4.1.4_1".


This problem persists, even though fluffy@ removed the pecl-pdflib dependency 
8+ weeks ago[1], and wen@ updated the port to the latest version 4 weeks 
ago[2]. Can someone please kick this to make it go?


[1] 
[2] 


The problem is, that although the php80 flavour does not depend on 
pecl-pdflib, the default flavour does, which means that the package will 
not be built as it you have to agree to pecl-pdflib's licence.


I know you don't need it for php80, but the package build infrastructure 
doesn't realise that.


Sorry-- you'll have to build it yourself until php80 is the current version.

@Larry, how about we change pdflib to be an off-by-default OPTION? 
That'd mean we'd have packages built at least.


Chris
___
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: Handling directory ownership in pkg-plist

[Chris Rees]

On 8 February 2021 08:01:22 GMT, Chris Rees  wrote:
>
>
>On 8 February 2021 01:28:06 GMT, Chris  wrote:
>>On 2021-02-07 12:19, Chris Rees wrote:
>>> Afternoon,
>>> 
>>> On 7 February 2021 19:05:26 GMT, Chris 
>>wrote:
>>>> On 2021-02-07 02:18, Chris Rees wrote:
>>>>> Hi Chris,
>>>>> 
>>>>> Thamks for the reply.
>>>>> 
>>>>> On 7 February 2021 03:57:03 GMT, Chris 
>>>> wrote:
>>>>>> On 2021-02-06 13:34, Chris Rees wrote:
>>>>>>> Hi all,
>>>>>>> 
>>>>>>> Resurrecting audio/ampache-resurrect, and I have @owner
>>www/@group
>>>>>> www above
>>>>>>> all
>>>>>>> of the WWWDIR files, and they are correctly owned.  However, the
>>>>>> directories
>>>>>>> under
>>>>>>> it are all still owned by root:wheel, and if I explicitly add
>>them
>>>>>> all with
>>>>>>> @dir
>>>>>>> pkg then complains about not being able to find them.
>>>>>>> 
>>>>>>> Would it be unacceptable to just have @exec chown -R www:www
>>>>>> %D/%%WWWDIR%%
>>>>>>> at the bottom?
>>>>>> Yes. By way of pre-install:
>>>>>> You'll probably get a complaint unless you use: ${CHOWN}
>>>>> 
>>>>> Perhaps I was unclear- I'm referring to pkg-plist, so there is no
>>>> ${CHOWN}
>>>>> there.
>>>>> 
>>>>> The exact proposed line is
>>>>> 
>>>>> @postexec chown -R www:www %D/%%WWWDIR%%
>>>>> 
>>>>> I was wondering what the 'proper' way to do this was.
>>>> I'm wondering why it's not enough to create a post-extract that
>>doesn't
>>>> 
>>>> something
>>>> like
>>>> cd ${WRKSRC}/some/dir && ${CHOWN} -R ${WWUSER}:${WWGROUP} .
>>>> Then the ports framework would create an appropriate pkg-plist
>based
>>on
>>>> that.
>>>> A
>>>> make -DBATCH makeplist would generate your target pkg-plist.
>>>> 
>>>> I'm paraphrasing, as I don't have your Makefile. But I've needed to
>>>> perform
>>>> tasks
>>>> like myself. Out of curiosity. What does a make -DBATCH makeplist
>>>> generate?
>>>> Does
>>>> the output provide the necessary clues to create a pkg-plist you're
>>>> interested in?
>>> 
>>> CHOWN can't be used in the Makefile as you need root.
>>> 
>>> make makeplist used after CHOWN does nothing different- it appears
>>not to 
>>> notice
>>> that they have different owners.
>>But what of the pkg-plist for www/kanboard? It has the clues you need
>>for 
>>setting the
>>pkg-plist. The ports framework will honor the perms set within it. eg;
>>@owner %%KANBOARD_USERNAME%%
>>@group %%KANBOARD_GROUPNAME%%
>>%%WWWDIR%%/.htaccess
>>%%WWWDIR%%/ChangeLog
>>%%WWWDIR%%/LICENSE
>>%%WWWDIR%%/app/.htaccess
>>%%WWWDIR%%/app/Action/Base.php
>>%%WWWDIR%%/app/Action/CommentCreation.php
>>...
>>
>>Just change the leader to the @user and @group to your desired names
>in
>>your
>>pkg-plist. Save it to your port. Done. :-)
>>> 
>>> There is nothing documented on this that I can find, so I'll commit
>>the 
>>> @postexec line.
>
>I need the directories also owned by www.
>
>This doesn't achieve that.
>

Solution was in fact to list it under @dir.  I guess I must have had duplicate 
@dir lines when I did it last time, hence the errors.

Chris

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Handling directory ownership in pkg-plist

[Chris Rees]

On 8 February 2021 01:28:06 GMT, Chris  wrote:
>On 2021-02-07 12:19, Chris Rees wrote:
>> Afternoon,
>> 
>> On 7 February 2021 19:05:26 GMT, Chris 
>wrote:
>>> On 2021-02-07 02:18, Chris Rees wrote:
>>>> Hi Chris,
>>>> 
>>>> Thamks for the reply.
>>>> 
>>>> On 7 February 2021 03:57:03 GMT, Chris 
>>> wrote:
>>>>> On 2021-02-06 13:34, Chris Rees wrote:
>>>>>> Hi all,
>>>>>> 
>>>>>> Resurrecting audio/ampache-resurrect, and I have @owner
>www/@group
>>>>> www above
>>>>>> all
>>>>>> of the WWWDIR files, and they are correctly owned.  However, the
>>>>> directories
>>>>>> under
>>>>>> it are all still owned by root:wheel, and if I explicitly add
>them
>>>>> all with
>>>>>> @dir
>>>>>> pkg then complains about not being able to find them.
>>>>>> 
>>>>>> Would it be unacceptable to just have @exec chown -R www:www
>>>>> %D/%%WWWDIR%%
>>>>>> at the bottom?
>>>>> Yes. By way of pre-install:
>>>>> You'll probably get a complaint unless you use: ${CHOWN}
>>>> 
>>>> Perhaps I was unclear- I'm referring to pkg-plist, so there is no
>>> ${CHOWN}
>>>> there.
>>>> 
>>>> The exact proposed line is
>>>> 
>>>> @postexec chown -R www:www %D/%%WWWDIR%%
>>>> 
>>>> I was wondering what the 'proper' way to do this was.
>>> I'm wondering why it's not enough to create a post-extract that
>doesn't
>>> 
>>> something
>>> like
>>> cd ${WRKSRC}/some/dir && ${CHOWN} -R ${WWUSER}:${WWGROUP} .
>>> Then the ports framework would create an appropriate pkg-plist based
>on
>>> that.
>>> A
>>> make -DBATCH makeplist would generate your target pkg-plist.
>>> 
>>> I'm paraphrasing, as I don't have your Makefile. But I've needed to
>>> perform
>>> tasks
>>> like myself. Out of curiosity. What does a make -DBATCH makeplist
>>> generate?
>>> Does
>>> the output provide the necessary clues to create a pkg-plist you're
>>> interested in?
>> 
>> CHOWN can't be used in the Makefile as you need root.
>> 
>> make makeplist used after CHOWN does nothing different- it appears
>not to 
>> notice
>> that they have different owners.
>But what of the pkg-plist for www/kanboard? It has the clues you need
>for 
>setting the
>pkg-plist. The ports framework will honor the perms set within it. eg;
>@owner %%KANBOARD_USERNAME%%
>@group %%KANBOARD_GROUPNAME%%
>%%WWWDIR%%/.htaccess
>%%WWWDIR%%/ChangeLog
>%%WWWDIR%%/LICENSE
>%%WWWDIR%%/app/.htaccess
>%%WWWDIR%%/app/Action/Base.php
>%%WWWDIR%%/app/Action/CommentCreation.php
>...
>
>Just change the leader to the @user and @group to your desired names in
>your
>pkg-plist. Save it to your port. Done. :-)
>> 
>> There is nothing documented on this that I can find, so I'll commit
>the 
>> @postexec line.

I need the directories also owned by www.

This doesn't achieve that.

Chris

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Handling directory ownership in pkg-plist

[Chris Rees]

Afternoon,

On 7 February 2021 19:05:26 GMT, Chris  wrote:
>On 2021-02-07 02:18, Chris Rees wrote:
>> Hi Chris,
>> 
>> Thamks for the reply.
>> 
>> On 7 February 2021 03:57:03 GMT, Chris 
>wrote:
>>> On 2021-02-06 13:34, Chris Rees wrote:
>>>> Hi all,
>>>> 
>>>> Resurrecting audio/ampache-resurrect, and I have @owner www/@group
>>> www above
>>>> all
>>>> of the WWWDIR files, and they are correctly owned.  However, the
>>> directories
>>>> under
>>>> it are all still owned by root:wheel, and if I explicitly add them
>>> all with
>>>> @dir
>>>> pkg then complains about not being able to find them.
>>>> 
>>>> Would it be unacceptable to just have @exec chown -R www:www
>>> %D/%%WWWDIR%%
>>>> at the bottom?
>>> Yes. By way of pre-install:
>>> You'll probably get a complaint unless you use: ${CHOWN}
>> 
>> Perhaps I was unclear- I'm referring to pkg-plist, so there is no
>${CHOWN} 
>> there.
>> 
>> The exact proposed line is
>> 
>> @postexec chown -R www:www %D/%%WWWDIR%%
>> 
>> I was wondering what the 'proper' way to do this was.
>I'm wondering why it's not enough to create a post-extract that doesn't
>
>something
>like
>cd ${WRKSRC}/some/dir && ${CHOWN} -R ${WWUSER}:${WWGROUP} .
>Then the ports framework would create an appropriate pkg-plist based on
>that. 
>A
>make -DBATCH makeplist would generate your target pkg-plist.
>
>I'm paraphrasing, as I don't have your Makefile. But I've needed to
>perform 
>tasks
>like myself. Out of curiosity. What does a make -DBATCH makeplist
>generate? 
>Does
>the output provide the necessary clues to create a pkg-plist you're 
>interested in?

CHOWN can't be used in the Makefile as you need root.

make makeplist used after CHOWN does nothing different- it appears not to 
notice that they have different owners.

There is nothing documented on this that I can find, so I'll commit the 
@postexec line.

Chris

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Handling directory ownership in pkg-plist

[Chris Rees]

Hi Chris,

Thamks for the reply.

On 7 February 2021 03:57:03 GMT, Chris  wrote:
>On 2021-02-06 13:34, Chris Rees wrote:
>> Hi all,
>> 
>> Resurrecting audio/ampache-resurrect, and I have @owner www/@group
>www above 
>> all
>> of the WWWDIR files, and they are correctly owned.  However, the
>directories 
>> under
>> it are all still owned by root:wheel, and if I explicitly add them
>all with 
>> @dir
>> pkg then complains about not being able to find them.
>> 
>> Would it be unacceptable to just have @exec chown -R www:www
>%D/%%WWWDIR%% 
>> at the bottom?
>Yes. By way of pre-install:
>You'll probably get a complaint unless you use: ${CHOWN}

Perhaps I was unclear- I'm referring to pkg-plist, so there is no ${CHOWN} 
there.

The exact proposed line is

@postexec chown -R www:www %D/%%WWWDIR%%

I was wondering what the 'proper' way to do this was.

Chris

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

Handling directory ownership in pkg-plist

[Chris Rees]

Hi all,

Resurrecting audio/ampache-resurrect, and I have @owner www/@group www 
above all of the WWWDIR files, and they are correctly owned.  However, 
the directories under it are all still owned by root:wheel, and if I 
explicitly add them all with @dir pkg then complains about not being 
able to find them.


Would it be unacceptable to just have @exec chown -R www:www 
%D/%%WWWDIR%% at the bottom?


Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Delete a port

[Chris Rees]

On 4 August 2018 18:59:30 BST, Eugene Grosbein  wrote:
>05.08.2018 0:42, Eitan Adler wrote:
>
>>> Feel free to commit, but please use the  absolute path to vi?
>> 
>> Why? Would't one want to respect the user's preference when it comes
>> to an editor? This preference is implicit when it comes to PATH.
>
>This is traditional overcautiousness against user's possibly insecure
>PATH having current directory that can lead to running malignant
>/tmp/vi
>in multiuser environment.
>
>Eugene

To be honest, I prefer this just so it definitely works.  If you choose to set 
PATH to something else, so you then put a symlink to emacs... Why not just set 
EDITOR to emacs?

I'm really not that bothered.  If you want to put plain vi there, go ahead.  
I'm just glad you chose the correct default :)

Chris

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Delete a port

[Chris Rees]

Hey,

On 4 August 2018 15:15:23 BST, Eugene Grosbein  wrote:
>04.08.2018 21:03, Romain Tartière wrote:
>
>> On Sat, Aug 04, 2018 at 12:28:41PM +0200, Matthias Fechner wrote:
>>> ./rmport: svnlog: not found
>>>
>>> Anyone an idea what is wrong?
>> 
>> Never used this script, but I guess you are hitting line 390:
>> 
>> | $EDITOR svnlog
>> 
>> Any chance $EDITOR is not set?
>
>It seems, rmport script needs a patch:
>
>Index: Tools/scripts/rmport
>===
>--- Tools/scripts/rmport(revision 476322)
>+++ Tools/scripts/rmport(working copy)
>@@ -39,6 +39,7 @@
> # MAINTAINER=  cr...@freebsd.org
> #
>
>+EDITOR=${EDITOR:-vi}
> PORTSDIR=${PORTSDIR:-/usr/ports}
> INDEX=${PORTSDIR}/`make -C ${PORTSDIR} -V INDEXFILE`

Thanks both.

Feel free to commit, but please use the  absolute path to vi?

Chris

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: WRKSRC/WRKSRC_SUBDIR/USE_GITHUB

[Chris Rees]

On 14 January 2018 17:25:54 GMT+00:00, Larry Rosenman  wrote:
>Greetings,
> I'm (finally) getting around to updating net/boinc-client, and 
>when I changed it to use USE_GITHUB, I get the following warning:
>
>You are using USE_GITHUB and WRKSRC is set which is wrong.  Set
>GH_PROJECT
>correctly, set WRKSRC_SUBDIR or remove WRKSRC entirely.
>
>But if I don't set WRKSRC, the patches, etc don't work.  
>
>Ideas?
>
>New Makefile:
># Created by: J.R. Oldroyd 
># $FreeBSD: head/net/boinc-client/Makefile 441503 2017-05-23 05:03:14Z
>rezny $
>
>PORTNAME=  boinc-client
>PORTVERSION=   7.8.6
>CATEGORIES=net
>#MASTER_SITES= LOCAL/rene
>
>MAINTAINER=l...@freebsd.org
>COMMENT=   Berkeley Open Infrastructure for Network Computing client
>
>LICENSE=   LGPL3
>
>LIB_DEPENDS+=  libfreetype.so:print/freetype2
>
>USES=  autoreconf dos2unix gettext gmake libtool pkgconfig ssl tar:xz
>USE_XORG+= x11 xscrnsaver
>INSTALL_TARGET=install-strip
>GNU_CONFIGURE= yes
>USE_GITHUB=yes
>GH_ACCOUNT=BOINC
>GH_PROJECT=boinc
>GH_TAGNAME=client_release/7.8/${PORTVERSION}
>USE_LDCONFIG=  yes
>DOS2UNIX_GLOB= *.xpm
>WRKSRC=${WRKDIR}
>WRKSRC_SUBDIR= boinc-client_release-7.8-${PORTVERSION}
>

You can set PATCH_WRKSRC if that helps?  Is it just patching that breaks?

By the way, NO_WRKSUBDIR is what you should put instead of redefining WRKSRC.

Chris
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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-p2p/transmission-daemon vulnerability

[Chris Rees]

Please excuse the earlier blank mail- Android Gmail being moronic again :(

Hello all,


I've just been alerted to an issue with transmission, but only the daemon.


Basically, you can fool it into believing that a remote host is localhost, and 
can therefore break in to it.


This is an issue if all of the following are true:


Port 9091 is accessible from the Internet (or you don't trust your LAN)

You have no password set

You rely on host authentication for security


Unless I'm misunderstanding the issue, you can resolve it by setting a 
password.  There is a patch at [1] that fixes this, but annoyingly they have 
messed with whitespace since 2.92, and the patch doesn't apply.  I expect a 
release very soon incorporating this fix anyway.  It also appears to break on 
all but Mac OS.


tl;dr set a password for transmission-daemon


Chris


[1] https://github.com/transmission/transmission/pull/468




On 11 January 2018 21:15:26 GMT+00:00, "Janky Jay, III"  wrote:
>Uhh... Chris? :)
>
>On 01/11/2018 02:08 PM, Chris Rees wrote:
>> ___
>> 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"

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

net-p2p/transmission-daemon vulnerability

[Chris Rees]

___
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: USES pgsql:plpython?

[Chris Rees]

Hey,

You can use variable modifiers instead of the != ECHO (should also be ECHO_CMD)

I'll test and show you the changes later.

I'd be happy to commit the pgsql.mk changes myself.

Chris


On 26 October 2017 06:15:29 BST, "L.Bartoletti"  
wrote:
>Hi Chris and all,
>
>I will propose soon a new patch for pgsql. Today you can select a 
>version like this 9.2+, 9.5- but not with an interval like this 9.5-10.
>
>It was ready, but pending since months, in this PR #213038. 
><https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213038>
>
>Can you also take a look at this, or do you want to separate this other
>
>request?
>
>Since postgis24 is landing #222703 
><https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222703>, I have to 
>rework on postgis.mk very soon.
>
>Regards
>
>Loïc
>
>On 05.09.2017 20:47, Lbartoletti wrote:
>> Yes sorry. I wrote too fast :)
>> My patch is near to be ready. Just some tests to be sure.
>>
>> Thanks.
>>
>> Envoyé de mon smartphone BlackBerry 10.
>>    Message d'origine
>> De: Chris Rees
>> Envoyé: mardi 5 septembre 2017 20:44
>> À: L.Bartoletti; po...@freebsd.org
>> Cc: pg...@freebsd.org
>> Objet: Re: USES pgsql:plpython?
>>
>> By the way, the syntax is:
>>
>> USES= pgsql
>> WANT_PGSQL= plpython
>>
>> The argument to USES is for version selection.
>>
>> Chris
>>
>> On 5 September 2017 19:33:53 BST, Chris Rees 
>wrote:
>>> Hey,
>>>
>>> No reason at all... I just missed it out when I wrote that bit of
>>> pgsql.mk :)
>>>
>>> If you feel up to patching Mk/Uses/pgsql.mk (have a look at line
>135,
>>> add plpython and make another line below it to match the others).
>>> Please alphabetise the list while you're at it!
>>>
>>> If you can't get it to work, I'll do it.
>>>
>>> Cheers,
>>>
>>> Chris
>>>
>>> On 5 September 2017 19:25:41 BST, "L.Bartoletti"
>>>  wrote:
>>>> Hi,
>>>>
>>>> I prepare a port which needs plpython. Is there any reason that we
>>>> don't
>>>> have the choice to write in our Makefile "USES pgsql:plpython"?
>>>>
>>>> Only because there are no ports dependent upon this port? Can I add
>it
>>>> to my diff?
>>>>
>>>> Regards
>>>>
>>>> Loïc Bartoletti.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Question: How to add a configuration file with autoplist ?

[Chris Rees]

On 2017-09-25 05:54, Kubilay Kocak wrote:

On 9/25/17 6:16 AM, Helen Koike wrote:

Hi,

According to
https://www.freebsd.org/doc/en/books/porters-handbook/plist-config.html
, I need to add a @sample macro in pkg-plist to add a configuration 
file.


But I am also using USE_PYTHON= autoplist in my Makefile, so I don't
have the pkg-plist file.

Should I remove autoplist and generate the pkg-plist by hand? Or is
there another way to do this?

I'll need this to update the version of the package
sysutils/py-google-compute-engine.

Thanks
Helen


Hi Helen,

As far as I'm aware, autoplist, PLIST_* definitions and pkg-plist
entries can be used cumulatively (in combination with each other) to
produce a correct and complete installed files list



Careful doing that!  If you do, you may find the sample file gets listed 
twice, or worse the actual config file gets listed.


If you want to view the final generated plist then in the normal ports 
directory:


% make package
% less `make -VTMPPLIST`

(those are backticks).

It's probably harmless to have a file listed twice, but if you list the 
actual config file it gets blown away on each update.


Cheers,

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: USES pgsql:plpython?

[Chris Rees]

By the way, the syntax is:

USES=  pgsql
WANT_PGSQL=  plpython

The argument to USES is for version selection.

Chris

On 5 September 2017 19:33:53 BST, Chris Rees  wrote:
>Hey,
>
>No reason at all...  I just missed it out when I wrote that bit of
>pgsql.mk :)
>
>If you feel up to patching Mk/Uses/pgsql.mk (have a look at line 135,
>add plpython and make another line below it to match the others). 
>Please alphabetise the list while you're at it!
>
>If you can't get it to work, I'll do it.
>
>Cheers,
>
>Chris
>
>On 5 September 2017 19:25:41 BST, "L.Bartoletti"
> wrote:
>>Hi,
>>
>>I prepare a port which needs plpython. Is there any reason that we
>>don't 
>>have the choice to write in our Makefile "USES pgsql:plpython"?
>>
>>Only because there are no ports dependent upon this port? Can I add it
>
>>to my diff?
>>
>>Regards
>>
>>Loïc Bartoletti.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: USES pgsql:plpython?

[Chris Rees]

Hey,

No reason at all...  I just missed it out when I wrote that bit of pgsql.mk :)

If you feel up to patching Mk/Uses/pgsql.mk (have a look at line 135, add 
plpython and make another line below it to match the others).  Please 
alphabetise the list while you're at it!

If you can't get it to work, I'll do it.

Cheers,

Chris

On 5 September 2017 19:25:41 BST, "L.Bartoletti"  
wrote:
>Hi,
>
>I prepare a port which needs plpython. Is there any reason that we
>don't 
>have the choice to write in our Makefile "USES pgsql:plpython"?
>
>Only because there are no ports dependent upon this port? Can I add it 
>to my diff?
>
>Regards
>
>Loïc Bartoletti.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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 issue after FreeBSD 11 upgrade

[Chris Rees]

Cassiano Peixoto wrote:

Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal
with when I need to restart a service without upgrading? Reaper
functionnality is a trouble for many administrators who made meta ports to
manage their servers. I really think it could be a option to be
enabled/disabled. Can you see this possibility?

Thanks.

On Wed, Aug 30, 2017 at 9:59 AM, Baptiste Daroussin 
wrote:


On Wed, Aug 30, 2017 at 09:55:22AM -0300, Cassiano Peixoto wrote:

Hi Baptiste,

Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only.

It only worked on FreeBSD 10 prior to 10.2, the reaper functionnality in
freebsd
kernel appeared in 10.2

Cron is just an example, I manage more than 50 FreeBSD servers, and I've
been using ports for years to update some configs and restart the service
on all of them. Many times I need to change nginx config, ldap, etc. I

just

need to restart the service.

HANDLE_RC_SCRIPTS=true in your pkg.conf and pkg will automatically restart
anything rc script provide once the package containing it is upgrading.

This is off by default because in many cases it is dangerous (database
upgrades,
dovecot like things upgrade etc). But if you know what you are doing it
does the
job.

Best regards,
Bapt





Hey,

I think you also want process supervision given your other comments.  
You can do this easily using daemon -P to run your scripts (but you'd 
need to rewrite the rc script...)


Or use runit or similar?  You could implement "runlevels" with that if 
that's REALLY what you want :)


Cheers,

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Trying to get poudriere to start

[Chris Rees]

On 29 July 2017 20:01:42 BST, Willem Jan Withagen  wrote:
>
>
>Op 29-7-2017 om 13:34 schreef Chris Rees:
>>
>>
>> On 29 Jul 2017 11:56, Willem Jan Withagen  wrote:
>>
>>
>>
>> Op 28-7-2017 om 22:50 schreef Chris Rees:
>>
>>
>>
>> On 26 Jul 2017 23:59, Willem Jan Withagen 
>> <mailto:w...@digiware.nl> wrote:
>>
>> Op 27-7-2017 om 00:48 schreef Miroslav Lachman:
>> > Willem Jan Withagen wrote on 2017/07/26 23:24:
>> >> Hi,
>> >>
>> >> This has been working, but now the jail does not even
>> start
>> >> Any suggestions why the linux module is giving me
>trouble?
>> >>
>> >>  >  sudo poudriere bulk -vv -j ceph -p local net/ceph
>> >> kldload: an error occurred while loading module linux.
>> Please check
>> >> dmesg(8) for more details.
>> >> [00:00:00] >> Error: Required kernel module
>'linux'
>> not found
>> >>
>> >> The parent system has linux stuff mounted in
>> /compat/linux/proc
>> >>
>> >> Running 12-CURRENT.
>> >
>> > Did you tried "kldload linux" in host system? Will
>> kldstat show you
>> > loaded kernel module "linux"?
>> >
>> Right,
>> I feel rather stupid... Because I do kknow how most of
>> this works.
>> So indeed this is all at the upper level:
>>
>> Looks like a incompatability
>> link_elf_obj: symbol freebsd32_exec_copyin_args undefined
>> linker_load_file: /boot/kernel/linux.ko - unsupported
>file
>> type
>>
>> But why
>>
>> [~] w...@freetest.digiware.nl
>> <mailto:w...@freetest.digiware.nl>> ls -asl
>> /boot/kernel/*linux*
>>   14 -r-xr-xr-x  1 root  wheel   13232 Jul 19 12:55
>> /boot/kernel/amr_linux.ko*
>>   47 -r-xr-xr-x  1 root  wheel   47480 Jul 19 12:55
>> /boot/kernel/geom_linux_lvm.ko*
>>   14 -r-xr-xr-x  1 root  wheel   13312 Jul 19 12:55
>> /boot/kernel/ipmi_linux.ko*
>> 771 -r-xr-xr-x  1 root  wheel  659248 Jul 19 12:55
>> /boot/kernel/linux.ko*
>> 643 -r-xr-xr-x  1 root  wheel  590328 Jul 19 12:55
>> /boot/kernel/linux64.ko*
>>   56 -r-xr-xr-x  1 root  wheel   55936 Jul 19 12:55
>> /boot/kernel/linux_common.ko*
>> 259 -r-xr-xr-x  1 root  wheel  186336 Jul 19 12:55
>> /boot/kernel/linuxkpi.ko*
>>   16 -r-xr-xr-x  1 root  wheel   15120 Jul 19 12:55
>> /boot/kernel/mfi_linux.ko*
>>   16 -r-xr-xr-x  1 root  wheel   15448 Jul 19 12:55
>> /boot/kernel/mrsas_linux.ko*
>> 102 -r-xr-xr-x  1 root  wheel  103416 Jul 19 12:55
>> /boot/kernel/systrace_linux.ko*
>> 112 -r-xr-xr-x  1 root  wheel  113416 Jul 19 12:55
>> /boot/kernel/systrace_linux32.ko*
>>
>> [~] w...@freetest.digiware.nl
>> <mailto:w...@freetest.digiware.nl>> file
>/boot/kernel/linux.ko
>> /boot/kernel/linux.ko: ELF 64-bit LSB relocatable,
>x86-64,
>> version 1
>> (FreeBSD), not stripped
>>
>> Are the jail and host the same version?
>>
>>
>> Nope,
>>
>> But if I check the jail scripts, the modules are loaded outside
>of
>> the jail in the host.
>> So I would expect that not to mater.
>>
>> --WjW
>>
>>
>> Well, depends entirely on which modules are loaded!  Are you loading 
>> host modules?
>>
>
>This is the code I commented out:
>
>/usr/local/share/poudriere/common.sh: 1780
>#   if [ -z "${NOLINUX}" ]; then
>#   if [ "${arch}" = "i386" -o "${arch}" = "amd64" ]; then
>#   needfs="${needfs} linprocfs"
>#   needkld="${needkld} linuxelf:linux"
>#   if [ "${arch}" = "amd64" ] && \

Re: Trying to get poudriere to start

[Chris Rees]

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

[Chris Rees]

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

[Chris Rees]

___
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: Trying to get poudriere to start

[Chris Rees]

___
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: Configuring options/knobs without `make config`

[Chris Rees]

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

[Chris Rees]

Hi all,

I have to say that actually the entire port is now a train wreck... the 
config directory is completely overwritten on install, and deleted on 
deinstall.  Config files should never go into pkg-plist directly!  I 
don't really understand why the previous method was changed as that has 
worked well.


I've marked it IGNORE and will fix it as quickly as I can.

Cheers,

Crhis

DutchDaemon - FreeBSD Forums Administrator wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
  
On 19-6-2017 07:18, Jeff Sickel wrote:

The MailScanner-5.0.3 update didn’t keep the /usr/local and other FreeBSD 
standard namespace in place.  I spent quite a bit of time correcting the perl 
scripts to pick up the /usr/local install locations after the upgrade.  The 
configuration files and other core pieces of MailScanner seem to keep more 
standard Linux namespaces with this release.  An upgrade from earlier versions 
is not recommended on FreeBSD until the correct file locations are handled by 
default.

Yeah .. https://forums.freebsd.org/threads/61298/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
  
iQEcBAEBCAAGBQJZR772AAoJEA9a9BMWOKcx4u4IALFdgmHYH78bvPlL8ALqZiLw

4Ma9mS73sP98XuSWcKUWzI3c+6piT0Qk1RAn/+OGEK2hj99TNTDWQjOt9Ttlr4TN
iOiA3e9+gsKW3M9TrCzoOTGYj7sDagdzLgU3mH/xfTeHWKyM7J3KFEdqIpV267g6
3Ft69e6A3aUIrqMEtGx6qFl/F2NegoEZrmwMdDGiHceZlPn8wRoc0GPRCZUOZS2B
DvEZuU7tARQ8PaH0H84NL9r7t9e3N84328sPwqll2YyAsymU1Cjvi0MjKppqtFgz
KfwCrIi6AM/h6dkz1vR0eB4HoM/MfC1in0gQSR8nlCStT9iLvFePyOiRmjs0svc=
=HMeS
-END PGP SIGNATURE-

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



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: openwebmail-2.53_2 - error Can't use 'defined(%hash)'

[Chris Rees]

Great, thanks.  I'll get that put in.
Chris


Sent from Samsung tablet.
 Original message From: Břetislav Kubesa 
 Date: 24/04/2017  19:06  (GMT+00:00) To: 
cr...@freebsd.org Cc: po...@freebsd.org Subject: FreeBSD Port: 
openwebmail-2.53_2 - error Can't use 'defined(%hash)' 
Hi,

I faced issues after upgrading to FBSD 10.3, getting error :

Can't use 'defined(%hash)' (Maybe you should just omit the defined()?) 
at /var/www/cgi-bin/mydomain/owm/shares/ow-shared.pl line 201.
Compilation failed in require at 
/var/www/cgi-bin/mydomain/owm/.openwebmail-tool.pl line 67.

Thanks to discussion 
http://www.linuxquestions.org/questions/slackware-14/openwebmail-in-14-2-compilation-failed-errors-from-defined-4175593135/
 
I maybe managed to fully fix it.

Hope this will be fine for fixing it for someone more experienced then 
me / port maintainer.

Thank you
Bretislav

PS : Don't kill me, just trying help

diff -ruN 
openwebmail-2.53_2_broken/cgi-bin/openwebmail/openwebmail-read.pl 
openwebmail-2.53_2/cgi-bin/openwebmail/openwebmail-read.pl
--- openwebmail-2.53_2_broken/cgi-bin/openwebmail/openwebmail-read.pl 
2017-04-24 19:43:15.081986000 +0200
+++ openwebmail-2.53_2/cgi-bin/openwebmail/openwebmail-read.pl 
2017-04-24 19:36:30.0 +0200
@@ -861,7 +861,7 @@
 my $has_nontext_att=0;

 foreach my $attnumber (0 .. $#{$message{attachment}}) {
-  next unless (defined %{$message{attachment}[$attnumber]});
+    next unless (%{$message{attachment}[$attnumber]});
    $has_nontext_att++ if (defined 
${$message{attachment}[$attnumber]}{'content-type'} &&
${$message{attachment}[$attnumber]}{'content-type'}!~/^text/i);
    my $attcharset=$convfrom;
@@ -886,7 +886,7 @@

    } else {    # attmode==simple
   # handle case to skip to next text/html attachment
- if ( defined %{$message{attachment}[$attnumber+1]} &&
+    if ( ref($message{attachment}[$attnumber+1]) eq "HASH" &&
    (${$message{attachment}[$attnumber+1]}{boundary} eq
    ${$message{attachment}[$attnumber]}{boundary}) ) {

@@ -1508,7 +1508,7 @@
 return ($msgsize, $errmsg) if ($msgsize<=0);
 ($message{header}, $message{body}, $message{attachment})
  =ow::mailparse::parse_rfc822block(\$block, "0", "all");
-   return 0 if (!defined @{$message{attachment}});
+   return 0 if (!defined {$message{attachment}});

 my @datas;
 my $boundary = "=OPENWEBMAIL_ATT_" . rand();
diff -ruN 
openwebmail-2.53_2_broken/cgi-bin/openwebmail/openwebmail-send.pl 
openwebmail-2.53_2/cgi-bin/openwebmail/openwebmail-send.pl
--- openwebmail-2.53_2_broken/cgi-bin/openwebmail/openwebmail-send.pl 
2017-04-24 19:43:15.085116000 +0200
+++ openwebmail-2.53_2/cgi-bin/openwebmail/openwebmail-send.pl 
2017-04-24 19:28:00.0 +0200
@@ -510,7 +510,7 @@
    } elsif ($message{'content-type'} =~ /^multipart/i) {
   # If the first attachment is text,
   # assume it's the body of a message in multi-part format
- if ( defined %{$message{attachment}[0]} &&
+ if ( %{$message{attachment}[0]} &&
    ${$message{attachment}[0]}{'content-type'} =~ /^text/i ) {
  if 
(${$message{attachment}[0]}{'content-transfer-encoding'} =~ 
/^quoted-printable/i) {
 $body = 
decode_qp(${${$message{attachment}[0]}{r_content}});
@@ -531,7 +531,7 @@
  # handle mail with both text and html version
  # rename html to other name so if user in text compose mode,
  # the modified/forwarded text won't be overridden by html 
again
-    if ( defined %{$message{attachment}[1]} &&
+    if ( %{$message{attachment}[1]} &&
   ${$message{attachment}[1]}{boundary} eq 
${$message{attachment}[0]}{boundary} ) {
 # rename html attachment in the same alternative group
 if ( 
(${$message{attachment}[0]}{subtype}=~/alternative/i &&
diff -ruN 
openwebmail-2.53_2_broken/cgi-bin/openwebmail/shares/getmessage.pl 
openwebmail-2.53_2/cgi-bin/openwebmail/shares/getmessage.pl
--- openwebmail-2.53_2_broken/cgi-bin/openwebmail/shares/getmessage.pl 
2017-04-24 19:43:15.037505000 +0200
+++ openwebmail-2.53_2/cgi-bin/openwebmail/shares/getmessage.pl 
2017-04-24 19:02:24.0 +0200
@@ -89,7 +89,7 @@
 $message{status} =~ s/\s//g;
 if ($message{'content-type'}=~/charset="?([^\s"';]*)"?\s?/i) {
    $message{charset}=$1;
-   } elsif (defined @{$message{attachment}}) {
+   } elsif (@{$message{attachment}}) {
    my @att=@{$message{attachment}};
    foreach my $i (0 .. $#att) {
   if (defined ${$att[$i]}{charset} && ${$att[$i]}{charset} ne '') {
diff -ruN 
openwebmail-2.53_2_broken/cgi-bin/openwebmail/shares/mailfilter.pl 
openwebmail-2.53_2/cgi-bin/openwebmail/shares/mailfilter.pl
--- openwebmail-2.53_2_broken/cgi-bin/openwebmail/shares/mailfilter.pl 
2017-04-24 19:43:15.040213000 +0200
+++ openwebmail-2.53_2/cgi-bin/openwebmail/shares/mailfilter.pl 
2017-04-24 19

Re: FreeBSD Port: neo4j-3.0.4_1

[Chris Rees]

Hey,

I guess your Java is working?

# chmod +x /usr/local/libexec/neo4j

Try that?  Should be done by the package.

Cheers,

Chris

On 25 January 2017 09:35:48 GMT+00:00, "Radek Krejča"  
wrote:
>Hello,
>
>After install and trying to run, I got:
>
>eval: /usr/local/libexec/neo4j: Permission denied
>
>
>This directory has owner root and no other messagess is shown.
>
>Thank you
>Radek
>
>Odesláno z aplikace
>Pošta pro Windows 10
>
>
>-- 
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Split irc/quassel into irc/quassel-client and irc/quassel-core

[Chris Rees]

Ben Woods wrote:

Hi Max,

I run quassel on my home FreeBSD server and again on my FreeBSD laptop.

Because I do not want to bring in the numerous dependencies related with
the client application to my server, I unset the MONO and CLIENT options in
my poudriere make.conf. But of course that means I cant use my poudriere
built packages to install quassel on my laptop (no client).

What do you think of either splitting irc/quassel into irc/quassel-client
and irc/quassel-core, or having a master port and slave ports?

Regards,
Ben


May I suggest just having a slave port for quassel-core?  The client and 
mono appear to have the heaviest dependencies.


Example at https://www.bayofrum.net/~crees/patches/quassel-core.diff 
(It's ready to commit, so if you're happy Max it can go in) 



Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Needed committer, multimedia/zoneminder forgotten again :(

[Chris Rees]

Done.

Chris

On 21 August 2016 19:40:40 BST, abi  wrote:
>Hello,
>
>can anyone commit 
>https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211681 ?
>This fixes build under CURRENT.
>___
>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"
>
>
>-- 
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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 happened to 'make missing'?

[Chris Rees]

Hi Warren (and others on the list)

Chris Rees wrote:

Warren Block wrote:

On Fri, 12 Aug 2016, Chris Rees wrote:


Warren Block wrote:
The missing target used to be very useful to see what impact 
installing a new port would have.


It seems to be increasingly broken.  On my desktop, any random port 
claims that misc/dejagnu and lang/expect are missing. Neither are 
installed, neither is installed as a dependency for any port where

'make missing' claims they are needed.

While trying to figure out which part of the recent clamav update 
wanted to pull in sphinx-doc for python, it seems even worse.


Clamav is installed, and did not install any additional ports 
before installing.  Yet 'make missing' shows this:




Hey Warren,

What is the output of:

# make -C/usr/ports//security/clamav all-depends-list




OK, and cat /etc/make.conf?

Chris


Following our IRC conversation, I have distilled the issue down to:

make missing checks every single dependency recursively

This means, for example, that make missing will list sphinx as a missing 
dependency, because llvm36 build-depends on it.  However, you already 
have llvm36 installed, resulting in a bogus 'missing' sphinx, even 
though it won't be needed.


In my view, make missing should recurse only for actual missing 
dependencies;


# find_missing origin
# Finds missing dependencies
find_missing() {
# check for installed of unified depends list (of ONLY $1)

for d in ${found_deps_that_are_not_installed}; do
find_missing $d
done
}

Does anyone disagree?  Unfortunately I can't prove that the behaviour 
was anything other than the current one, which I think is wrong.  Please 
see relevant (I think) changes below.


Chris

http://svnweb.freebsd.org/ports/head/Mk/bsd.port.mk?r1=414166&r2=414167&;

http://svnweb.freebsd.org/ports/head/Mk/bsd.port.mk?r1=255512&r2=255513&;

http://svnweb.freebsd.org/ports/head/Mk/bsd.port.mk?r1=399711&r2=399712&;

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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 happened to 'make missing'?

[Chris Rees]

Warren Block wrote:

On Fri, 12 Aug 2016, Chris Rees wrote:


Warren Block wrote:
The missing target used to be very useful to see what impact 
installing a new port would have.


It seems to be increasingly broken.  On my desktop, any random port 
claims that misc/dejagnu and lang/expect are missing. Neither are 
installed, neither is installed as a dependency for any port where

'make missing' claims they are needed.

While trying to figure out which part of the recent clamav update 
wanted to pull in sphinx-doc for python, it seems even worse.


Clamav is installed, and did not install any additional ports before 
installing.  Yet 'make missing' shows this:




Hey Warren,

What is the output of:

# make -C/usr/ports//security/clamav all-depends-list


/usr/ports/ports-mgmt/pkg
/usr/ports/devel/llvm36
/usr/ports/textproc/py-sphinx
/usr/ports/devel/py-Jinja2
/usr/ports/devel/py-setuptools27
/usr/ports/lang/python27
/usr/ports/devel/pkgconf
/usr/ports/devel/libffi
/usr/ports/print/indexinfo
/usr/ports/misc/dejagnu
/usr/ports/devel/gmake
/usr/ports/lang/expect
/usr/ports/devel/autoconf
/usr/ports/devel/m4
/usr/ports/misc/help2man
/usr/ports/lang/perl5.20
/usr/ports/devel/autoconf-wrapper
/usr/ports/devel/automake
/usr/ports/devel/automake-wrapper
/usr/ports/lang/tcl86
/usr/ports/textproc/py-MarkupSafe
/usr/ports/devel/py-babel
/usr/ports/devel/py-pytz
/usr/ports/textproc/py-docutils
/usr/ports/devel/py-six
/usr/ports/devel/py-pytest
/usr/ports/devel/py-py
/usr/ports/devel/py-mock
/usr/ports/devel/py-pbr
/usr/ports/devel/py-pip
/usr/ports/devel/py-pytest-capturelog
/usr/ports/devel/py-pytest-timeout
/usr/ports/devel/py-pytest-xdist
/usr/ports/devel/py-setuptools_scm
/usr/ports/sysutils/py-execnet
/usr/ports/misc/py-pexpect
/usr/ports/devel/py-virtualenv
/usr/ports/devel/py-scripttest
/usr/ports/devel/py-pretend
/usr/ports/devel/py-freezegun
/usr/ports/devel/py-dateutil
/usr/ports/devel/py-nose
/usr/ports/databases/py-sqlite3
/usr/ports/databases/sqlite3
/usr/ports/devel/git
/usr/ports/textproc/xmlto
/usr/ports/shells/bash
/usr/ports/devel/bison
/usr/ports/converters/libiconv
/usr/ports/misc/getopt
/usr/ports/textproc/libxml2
/usr/ports/textproc/libxslt
/usr/ports/security/libgcrypt
/usr/ports/security/libgpg-error
/usr/ports/textproc/docbook-xsl
/usr/ports/textproc/xmlcatmgr
/usr/ports/textproc/docbook
/usr/ports/textproc/docbook-sgml
/usr/ports/textproc/iso8879
/usr/ports/textproc/docbook-xml
/usr/ports/textproc/xmlcharent
/usr/ports/textproc/sdocbook-xml
/usr/ports/print/libpaper
/usr/ports/www/w3m
/usr/ports/devel/boehm-gc
/usr/ports/devel/libatomic_ops
/usr/ports/textproc/asciidoc
/usr/ports/lang/python2
/usr/ports/ftp/curl
/usr/ports/security/ca_root_nss
/usr/ports/lang/p5-Error
/usr/ports/textproc/expat2
/usr/ports/devel/pcre
/usr/ports/devel/cvsps
/usr/ports/mail/p5-Net-SMTP-SSL
/usr/ports/security/p5-IO-Socket-SSL
/usr/ports/security/p5-Net-SSLeay
/usr/ports/devel/p5-Test-Exception
/usr/ports/devel/p5-Sub-Uplevel
/usr/ports/devel/p5-Test-NoWarnings
/usr/ports/devel/p5-Test-Simple
/usr/ports/devel/p5-Test-Warn
/usr/ports/www/p5-Mozilla-CA
/usr/ports/net/p5-IO-Socket-IP
/usr/ports/devel/p5-Test-Pod
/usr/ports/net/p5-Socket
/usr/ports/security/p5-Authen-SASL
/usr/ports/security/p5-Digest-HMAC
/usr/ports/security/p5-GSSAPI
/usr/ports/devel/bzr
/usr/ports/lang/cython
/usr/ports/devel/gettext-tools
/usr/ports/devel/gettext-runtime
/usr/ports/security/py-paramiko
/usr/ports/security/py-cryptography
/usr/ports/devel/py-cffi
/usr/ports/devel/py-pycparser
/usr/ports/devel/py-pyasn1
/usr/ports/dns/py-idna
/usr/ports/net/py-ipaddress
/usr/ports/devel/py-enum34
/usr/ports/devel/py-iso8601
/usr/ports/security/py-ecdsa
/usr/ports/devel/py-funcsigs
/usr/ports/textproc/py-pygments
/usr/ports/textproc/py-sphinx_rtd_theme
/usr/ports/textproc/py-alabaster
/usr/ports/textproc/py-snowballstemmer
/usr/ports/textproc/py-pystemmer
/usr/ports/graphics/py-imagesize
/usr/ports/devel/libedit
/usr/ports/devel/libltdl
/usr/ports/devel/json-c
/usr/ports/archivers/arc
/usr/ports/archivers/arj
/usr/ports/archivers/lha
/usr/ports/archivers/unzoo


OK, and cat /etc/make.conf?

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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 happened to 'make missing'?

[Chris Rees]

Warren Block wrote:
The missing target used to be very useful to see what impact 
installing a new port would have.


It seems to be increasingly broken.  On my desktop, any random port 
claims that misc/dejagnu and lang/expect are missing. Neither are 
installed, neither is installed as a dependency for any port where

'make missing' claims they are needed.

While trying to figure out which part of the recent clamav update 
wanted to pull in sphinx-doc for python, it seems even worse.


Clamav is installed, and did not install any additional ports before 
installing.  Yet 'make missing' shows this:




Hey Warren,

What is the output of:

# make -C/usr/ports//security/clamav all-depends-list

?

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Ports with duplicate LATEST_LINKs

[Chris Rees]

Hi,

This looks like a bsd.port.mk or similar change resulting in PKGNAME*FIX not 
being put into LATEST_LINK?

Or have these all been broken a while?

Chris 

On 18 August 2015 13:37:23 BST, Ports Index build  
wrote:
>Dear port maintainers,
>
>The following list includes ports maintained by you that have duplicate
>LATEST_LINK values.  They should either be modified to use a unique
>PKGNAME, e.g. by using PKGNAMESUFFIX.  Note that NO_LATEST_LINK is
>deprecated.  See the portmgr blog post for more information:
>http://blogs.freebsdish.org/portmgr/2013/10/03/package-name-collisions/
>
>
>Thanks,
>Erwin "Annoying Reminder Guy III" Lansing
>
>
>LATEST_LINK  PORTNAME   MAINTAINER 
>
>==
>databases/postgresql-libpqxx3 20080111.freebsd@ab.ote.we.lv
>
>devel/tortoisehg 6year...@gmail.com
>
>math/cryptominisat   6year...@gmail.com
>
>math/py-cryptominisat 6year...@gmail.com   
> 
>math/stp 6year...@gmail.com
>
>security/qtkeychain-qt4 6year...@gmail.com 
>   
>security/qtkeychain-qt5 6year...@gmail.com 
>   
>x11-fonts/hasklig6year...@gmail.com
>
>russian/wordpress9267...@gmail.com 
>
>mail/postfinger  a.j.cai...@halplant.com   
>
>x11-wm/bbkeysa.j.cai...@halplant.com   
>
>x11-wm/bbpager   a.j.cai...@halplant.com   
>
>x11-wm/blackbox  a.j.cai...@halplant.com   
>
>databases/p5-DBIx-VersionedDDL a...@wave2.org  
>  
>devel/p5-MooseX-Attribute-ENV a...@wave2.org   
> 
>www/jawstats a...@wave2.org
>
>devel/p5-App-Build   alex.bakh...@gmail.com
>
>www/p5-Catalyst-TraitFor-Controller-DBIC-DoesPaging
>alex.bakh...@gmail.com 
>japanese/alias-fonts cqg00...@nifty.ne.jp  
>
>japanese/k10 cqg00...@nifty.ne.jp  
>
>japanese/k12 cqg00...@nifty.ne.jp  
>
>japanese/mh  cqg00...@nifty.ne.jp  
>
>accessibility/eflite david.k.ge...@gmail.com   
>
>accessibility/yasr   david.k.ge...@gmail.com   
>
>audio/hydrogen   free...@shaneware.biz 
>
>audio/hydrogen-devel free...@shaneware.biz 
>
>devel/godot  free...@shaneware.biz 
>
>graphics/opencolorio free...@shaneware.biz 
>
>graphics/opencolorio-tools free...@shaneware.biz   
>  
>graphics/openimageio free...@shaneware.biz 
>
>graphics/openshadinglanguage free...@shaneware.biz 
>
>graphics/py-openimageio free...@shaneware.biz  
>   
>audio/aften  ga...@zahemszky.hu
>
>audio/autocd k...@matpockuh.ru  
>
>net/wmwlmon  lu...@pobox.com   
>
>converters/asr10 m.indleko...@gmx.de   
>
>converters/cmios9m.indleko...@gmx.de   
>
>ports-mgmt/portrac   mario.g.pav...@gmail.com  
>
>mail/p5-MIME-Charset olivier.gir...@univ-angers.fr 
>
>mail/p5-MIME-EncWords olivier.gir...@univ-angers.fr
> 
>textproc/p5-Unicode-LineBreak olivier.gir...@univ-angers.fr
> 
>devel/p5-Time-Format sergey.dya...@gmail.com   
>
>devel/py-robotframework vladimir.chukha...@gmail.com   
>   
>devel/py-robotframework-pabot vladimir.chukha...@gmail.com 
> 
>devel/py-robotframework-ride vladimir.chukha...@gmail.com  
>
>devel/py-robotframework-selenium2library vladimir.chukha...@gmail.com  
>
>devel/py-robotremoteserver vladimir.chukha...@gmail.com
>  
>ports-mgmt/porttree  vladimir.chukha...@gmail.com  
>
>www/py-django-allauth vladimir.chukha...@gmail.com 
> 
>sysutils/pp  a.ar...@gmail.com 
>
>audio/xwave  a0...@marimga.de  
>
>games/xlogical   aa...@baugher.biz 
>
>sysutils/usrinfo aa...@snaphat.com 
>
>sysutils/btsixad a...@q-fu.com  
>
>ed

Re: FreeBSD Port: transmission-daemon-2.84_1

[Chris Rees]

Hi Andrew,

On 5 February 2015 19:41:54 GMT+00:00, Andrew Hotlab 
 wrote:
>Hi to all. Sorry to disturb, but I had not been able to solve the issue
>by myself, and I suspect the problem lies somewhere after the version
>2.82 of Transmission.
>I have been happily run transmission daemon in a jail for several
>years, but since the version 2.83 the daemon makes a core dumps and
>exits after a fews second since it starts.
>I waited for the latest 2.84 release, but the problem still plague me.
>I'm running it on FreeBSD 9.3/amd64. It crashes both inside and outside
>a jail.
>It looks like there is some other people having issue with the latest
>releases:https://forums.freebsd.org/threads/transmission-exited-on-signal-11-core-dumped.49483/https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197125
>If it can help, I just tried running the 2.84 port inside a FreeBSD
>10.1/amd64 jail, and it works fine. I attached the gzipped core dump of
>transmission-daemon 2.84 on FreeBSD 9.3.

I was never able to reproduce the bug, and suggested to the original reporter 
that they contact upstream.  I've been particularly useless with bugs 
semi-recently for several reasons, so I'm really sorry that I haven't been able 
to personally investigate.

Are the configuration and torrents identical for both instances you're trying?

Chris
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: postgresql-server depends on client. Why?

[Chris Rees]

Hi Dan,

http://svnweb.freebsd.org/ports/head/databases/postgresql90-server/Makefile?revision=286930&view=markup#l64

It was always supposed to be the case, however I agree that it's probably not 
necessary.

Anyone mind if it doesn't depend?

Chris


On 17 October 2014 15:12:51 BST, Dan Langille  wrote:
>Why is postgresql-server dependent upon postgresql-client?
>
>This wasn’t the case in the past and seems to be the case not.
>
>Not all server installations need the client.
>
>In addition, upgrading the client before upgrading the server is
>standard procedure:
>
>  http://www.postgresql.org/docs/9.3/static/upgrading.html
>
>i.e. upgrade the client, pg_dump using the new client, then upgrade
>server, pg_restore.
>
>Thanks
>
>— 
>Dan Langille

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: is bsd.database.mk out of sync with Uses/pgsql.mk?

[Chris Rees]

On 28 September 2014 11:36:41 BST, Baptiste Daroussin  wrote:
>On Sat, Sep 27, 2014 at 03:52:56PM -0400, Dan Langille wrote:
>> Today I encountered these build messages with poudriere:
>> 
>> Invalid PGSQL default version 92; valid versions are 8.4 9.0 9.1 9.2
>9.3 9.4
>> 
>> These messages originate in Mk/Uses/pgsql.mk
>> 
>> But Mk/bsd.database.mk claims a different format is correct:
>> 
>> # DEFAULT_PGSQL_VER
>> #   - PostgreSQL default version, currently 90.
>> 
>> 
>> Do you agree that the comments in Mk/bsd.database.mk need to updated?
>
>Everything should migrate to USES=pgsql and the code in bsd.database.mk
>should
>just die.
>

I'm pretty sure I put developer warnings there too about this!

Chris



>regards,
>Bapt

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Return ports www/sams

[Chris Rees]

Hi John,

It seems to me that this might have been better just put in as an update to 
www/sams.

Zlopi, please would you try out sams2 and let us know if it just works the 
same?  That could render this whole discussion pointless!

Chris

On 25 August 2014 19:56:11 BST, zlopi  wrote:
>It makes me sad to look at how changes in recent years FreeBSD - not
>for the better.
>New packages - it's good. But! Stable packages replaced by new
>unstable version - this is wrong.
>
>Thanks for taking your time on me.
>
>2014-08-25 21:26 GMT+04:00 John Marino :
>> On 8/25/2014 19:18, Jim Ohlstein wrote:
>>> Not for nothing, but since PHP 5.3 is still in the ports tree, then
>why
>>> delete ports that depend on it? I know PHP 5.3 has now reached EOL,
>but
>>> there is probably still a fair amount of legacy code which breaks
>with
>>> PHP 5.4. I'm not advocating using it, but some people have no
>choice. If
>>> people want it in the ports tree and they understand the risks,
>>> shouldn't it be their choice?
>>
>> When it was deleted, the port claimed that it *only* worked with
>PHP4.
>> It was only after the deletion that somebody said it would work with
>> 5.3.  At that point we weren't bringing back an long-time
>unmaintained
>> port for a PHP that is probably itself on it's way out.  Unmaintained
>at
>> the ports level *and* upstream.
>>
>> If these users really want to accept risk, they can always put a copy
>of
>> www/sams locally in their tree.
>>
>> www/sams2 is supposed to work with PHP 5.3, 5.4, and 5.5.  Until I
>hear
>> why it's not a suitable replacement for an unmaintained sams, I don't
>> understand why this discussion is happening at all.
>>
>> John
>
>-- 
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: question about "pkg install"

[Chris Rees]

On 08/23/14 09:14, Matthew Seaman wrote:

On 23/08/2014 08:40, Kurt Jaeger wrote:

 I have a program (several, actually) I need to install from the

generic package repository.
 These programs depend on openldap-client; however I have
openldap-sasl-client installed.  In my experience the two have been
interchangeable when compiling from ports.
 Is there a way to tell 'pkg install' "Yeah, I know it
says openldap-client, but the same version of
openldap-sasl-client satisfies the dependency"?  Or do I just use 'pkg
install -M' and hope everything works?

I had this issue in the past, too, and am not aware of a solution.

There isn't a good solution for this right now if you're using the
packages from the official FreeBSD repositories.  You get the default
dependency chain which is baked into the packages.  Which means
openldap-client rather than openldap-sasl-client[*].

If you need to change options for various ports, then the best solution
is to compile your own.  Give poudriere a go -- it is surprisingly easy
and unstressful to use.  Build yourself a repo with your customized
ports in it and away you go.

We do have plans for improving the ports behaviour in this reguard.
Dependencies based on Provides/Requires/Conflicts should help a lot, as
will sub-packages and dependency version-ranges.  This stuff is all on
the roadmap, but there's a lot of work to do to get from here to there,
so don't expect it to all start magically working tomorrow.

Cheers,

Matthew

[*] In this case openldap-client and openldap-sasl-client are clearly
API compatible, since on compilation, it's not a problem to swap from
one to the other.  The question when using binary packages is if they
are ABI compatible, which is a whole different kettle of fish.


Hum, I wonder if we couldn't just add sasl support by default?

Xin Li, would there be a downside to this?

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Return ports www/sams

[Chris Rees]

On 08/25/14 14:56, zlopi wrote:

Hi

Bring to your attention the correct port www / sams that has all the
necessary corrections for its  work.

Check and send to the ports. Thank you.



Hello-- did you mean to send a patch?

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: FreeBSD Port: git-2.0.2_1

[Chris Rees]

On 08/25/14 16:14, Kubilay Kocak wrote:

On 26/08/2014 1:02 AM, Kubilay Kocak wrote:

On 26/08/2014 12:52 AM, Michael Gmelin wrote:

On Mon, 25 Aug 2014 13:39:50 +
Sebastian Bach  wrote:


Hi!

I've an urgent problem with the current port devel/git (2.0.2). After
upgrading  we can't use our Atlassian Stash server anymore. Stash
rejects (hard check of 2.0.2 and 2.0.3) to use this specific git
version due to a critical bug in 'git diff-tree' which breaks Stash's
commit page. Please see the 'DVCS clients' section on their system
requirements page:
https://confluence.atlassian.com/display/STASH/Supported+platforms
https://jira.atlassian.com/browse/STASH-5052

I don't know how to downgrade this port. Is this even possible on
FreeBSD? However, can you tell me when git 2.0.4 or 2.1.0 will be
available in the ports collections?

Best regards
Sebastian Bach


If you're using pkg you might be lucky and still have a cached copy
in /var/cache/pkg. In that case try pkg delete git and pkg
add /var/cache/pkg/git-.txz.

Otherwise one way of doing this is getting the old package skeleton
from svn and build it from ports. You need revision 362475 of the ports
tree for git version 2.0.1. Alternatively you can download the files
from svnweb (a bit clumsy, but doesn't require you to install
subversion):

http://svnweb.freebsd.org/ports/head/devel/git/?pathrev=362475

If you don't have a ports tree yet, do: portsnap fetch extract

Then copy the files in /usr/ports/devel/git, go there and do make
install (do pkg delete git beforehand).


Thanks for the assist Michael :)

I have a patch updating git to 2.1.0 thats 98% complete (just updating
minor pkg-plist stuff for HTMLDOCS option)

I'll have it to you in 10-15


Sebastian,

Find attached a patch updating devel/git to 2.1.0 with the following
changes:

- Update to 2.1.0
- Sort pkg-plist (much easier to update when sorted!)
- Use CONFIGURE_ARGS user-knob to disable libiconv

There is a leftover issue (in the current version of the port too)
building *without* ICONV and *with* CONTRIB options, so avoid that
combination.

Otherwise it builds and packages cleanly (tested with poudriere).

Let us know how the update goes for you, whether it fixes your Atlassian
Stash issue, and report back.

I can then create a Bugzilla issue report and submit the update so you
can revert to using ports rather than a local patch :)

Hope that helps!

Koobs




For future reference, ports-mgmt/portdowngrade does the heavy svn 
lifting for you if you're not sure about exactly what to do.


Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Berkeley DB 4 and portupgrade

[Chris Rees]

On 23 Aug 2014, at 15:10, RW wrote:

> 
> 
> I've lost track of how portupgrade works these days (10.0). Has it
> switched to using pkg's sqlite database? 
> 
> 
> I was wondering whether I needed to do anything for the DB 4x
> deletions, but I don't see a separate database file:
> 
> $ ls -l /var/db/pkg
> total 41638
> -rw-r--r--  1 root  wheel  39279616 23 Aug 14:55 local.sqlite
> -rw-r--r--  1 root  wheel 38912 15 Sep  2013 repo-packagesite.sqlite
> -r--r--r--  1 root  wheel   3236956 22 Aug 11:23 vuln.xml

Nope, it doesn't:

https://github.com/freebsd/portupgrade/commit/633cdd7c90a117678f0bdd0c6d25c0b153d20c47

By the way, 10.0 is the release of FreeBSD, nothing to do with the portupgrade 
port.

Hope that helps!

Chris
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Building interactive ports with poudriere

[Chris Rees]

On 18/08/2014 06:21, Matthias Apitz wrote:
> El día Sunday, August 17, 2014 a las 07:21:06PM -0500, Greg Rivers escribió:
> 
>> What's the proper way to tell poudriere to accept a license?
>>
>> Example:
>> # DISABLE_LICENSES=yes poudriere bulk -j 100amd64 sysutils/fusefs-exfat 
>> sysutils/exfat-utils
>> [snip]
>> >> Building 2 packages using 2 builders
>> >> Starting/Cloning builders
>> >> Hit CTRL+t at any time to see build progress and stats
>> >> [01] Starting build of sysutils/fusefs-exfat
>> >> [02] Starting build of sysutils/exfat-utils
>> >> [02] Finished build of sysutils/exfat-utils: Ignored: License 
>> Microsoft-exFAT needs confirmation, but BATCH is defined
>> >> [01] Finished build of sysutils/fusefs-exfat: Ignored: License 
>> Microsoft-exFAT needs confirmation, but BATCH is defined
>> >> Stopping 2 builders
>> >> No package built, no need to update the repository
>> [snip]
>>
>> Setting environment variables doesn't seem to work.
> 
> I have set with success
> 
> NO_IGNORE=yes
> 
> in the make.conf file of the jail to build ports marked with IGNORE.
> Don't know if this helps in this case too.

Necro-post, sorry, but this should be in the archives.

The easiest way is to put DISABLE_LICENSES=yes into make.conf.  Using
NO_IGNORE will result in wasted time building known-broken ports.

Chris


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: texlive-texmf

[Chris Rees]

Hello Hiroki-san,

I think it would be a good idea to add

CONFLICTS_BUILD=texlive-texmf-201[23]*

to texlive-base Makefile.  It appears several people would appreciate this clue!

Do you agree?

Chris


On 23 Aug 2014, at 11:02, Dr. Peter Voigt wrote:

> Am Sat, 23 Aug 2014 05:49:02 -0400
> schrieb Ajtim :
> 
>> Hi!
>> 
>> I try to update ports on FreeBSD 10.0 RELELEASE and it stopped at:
>> 
>> ===>   Registering installation for texlive-base-20140525 as automatic
>> mktexlsr: Updating /usr/local/share/texmf/ls-R... 
>> mktexlsr: Updating /usr/local/share/texmf-config/ls-R... 
>> mktexlsr: Updating /usr/local/share/texmf-dist/ls-R... 
>> mktexlsr: Updating /usr/local/share/texmf-local/ls-R... 
>> mktexlsr: Updating /usr/local/share/texmf-var/ls-R... 
>> mktexlsr: Done.
>> pkg-static: texlive-base-20140525 conflicts with
>> texlive-texmf-20120701_4 (installs files into the same place).
>> Problematic file: /usr/local/share/texmf-
>> dist/bibtex/csf/base/88591lat.csf *** Error code 70
>> 
>> Stop.
>> make: stopped in /usr/ports/print/texlive-base
>> 
>> ===>>> Installation of texlive-base-20140525 (print/texlive-base)
>> failed
>> 
>> Thank you.
>> 
> 
> I have had the same problem. After I have removed the old
> packages texlive-base and texlive-texmf the new texlive ports install
> smoothly.
> 
> Regards,
> Peter


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: texlive-texmf conflicts with texlive-base

[Chris Rees]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 23/08/2014 11:14, O. Hartmann wrote:
> 
> ===>>> All >> tex-dvipsk-5.992_3 >> texlive-texmf-20120701_4 >> 
> print/texlive-base (5/16)
> 
> ===>  Installing for texlive-base-20140525 ===>   Registering 
> installation for texlive-base-20140525 as automatic mktexlsr: 
> Updating /usr/local/share/texmf/ls-R... mktexlsr: Updating 
> /usr/local/share/texmf-config/ls-R... mktexlsr: Updating 
> /usr/local/share/texmf-dist/ls-R... mktexlsr: Updating 
> /usr/local/share/texmf-local/ls-R... mktexlsr: Updating 
> /usr/local/share/texmf-var/ls-R... mktexlsr: Done. pkg-static: 
> texlive-base-20140525 conflicts with texlive-texmf-20120701_4 
> (installs files into the same place).  Problematic file: 
> /usr/local/share/texmf-dist/bibtex/csf/base/88591lat.csf *** Error 
> code 70
> 
> Stop. make: stopped in /usr/ports/print/texlive-base
> 

You need to keep texlive-base and texlive-texmf in sync.  Update
texlive-texmf and try again.

Might be an idea to use packages to speed this process up?

Chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (MingW32)

iQEcBAEBAgAGBQJT+JPgAAoJEJAPRaYeEulqbxEIAMlw8tQ3toP0m9QlI/frZzyn
i+djz61pt3hRM3Q1T7AdIrTpIRLO/N7jBS9t+icNIy+ezAQEQUUCVica67mw7KL+
P8uH3EcfXGEQFDYjpseNrqREQYWdXwLMTOspAk3llenPR82IZb11RdyRSvVduIgm
YK0/QpQEtm7NDBwFhawQTly+NQg0HS35C1wIgdbQHuxbPay9fIWAX5JD7l14loZG
Vm2A3XXQQciTllyADudBBDV+52W84Tvm5RCU25DEnRO03z3t0jcu3hj13BpXxFwR
7WcMJC37q+SdycSCCQEPJbLawFxGddkdAz7C7bDVLs4xjSIs9YG9xHoj+Mcs8rc=
=eXjR
-END PGP SIGNATURE-

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: databases/postgresql92-server does not honor uid/gid

[Chris Rees]

This is a general problem with the USERS framework.

I think I may have a PR in..

Chris

On 9 June 2014 23:08:21 BST, Dan Langille  wrote:
>FYI:
>
>I upgraded databases/postgresql92-server a system today.  Afterwards, I
>encountered this situation:
>
>$ sudo /usr/local/etc/rc.d/postgresql initdb 
>The files belonging to this database system will be owned by user
>"pgsql".
>This user must also own the server process.
>
>The database cluster will be initialized with locale "C".
>The default database encoding has accordingly been set to "SQL_ASCII".
>The default text search configuration will be set to "english".
>
>creating directory /usr/local/pgsql/data ... initdb: could not create
>directory "/usr/local/pgsql/data": Permission denied
>
>
>
>Oh… u…
>
>$ ls -ld /usr/local/pgsql
>drwxr-xr-x  2 70  70  6 Jun  9 21:03 /usr/local/pgsql
>
>eh?
>
>$ id pgsql
>uid=10837(pgsql) gid=10837(pgsql) groups=10837(pgsql)
>
>On this system, a jail. the uid/gid for pgsql are not standard.
>
>I solved the problem with: $ sudo chown pgsql:pgsql /usr/local/pgsql/
>
>
>— 
>Dan Langille

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Force Dependent ports OPTIONS

[Chris Rees]

Hi Muhammad,

On 04/05/2014 15:09, Muhammad Moinur Rahman wrote:
> Hi Dirk,
> 
> How can I enforce it from inside a ports Makefile?
> 
> Thanks in advance.
> 

Short answer, you can't, sorry.

You'll need to test it somehow in a target;

pre-configure:
if ! openssl --help 2>&1 | grep -q 3779; then \
${ECHO_MSG} "openssl was compiled without RFC3779 option; "; \
${ECHO_MSG} "please reinstall with RFC3779 selected"; \
${FALSE}; \
fi

Not sure if anyone else has a better idea

By the way, check that openssl --help actually tells you whether or
not RFC3779 was compiled, because I don't know :)

Chris

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

Re: net/minidlna update

[Chris Rees]

On 08/05/2014 17:08, Chris Ross wrote:
> 
> I am looking to try putting a DLNA server on a FreeBSD 9 sparc64
> box.  As Plex seems to be amd64 only, I’m looking now at minidlna.
> I see that ports has version 1.1.1, but 1.1.2 was released a couple
> months ago.
> 
> Is there any problem with 1.1.2, or has there just not yet been
> time to get ports updated?
> 
> Thanks…
> 

Hm, I don't think there's a problem, probably that the maintainer
hasn't got around to updating it :)

Is there a feature you're missing?  Using 1.1.1 shouldn't be an issue
if not.

Chris


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: [FIX] Re: FreeBSD Port: security/sshguard-pf

[Chris Rees]

On Mon, 14 Apr 2014 12:59:21 +0200, Stefan Esser wrote
> Am 14.04.2014 10:25, schrieb Benjamin Podszun:
> > I'd say this is a bug in sshguard: Failing to start shouldn't exit with 0.
> > That said, it first and foremost is a bug in the port.
> > 
> > Looking at the rc script and the diff [1] the problem's easy enough:
> > ${sshguard_pidfile} is passed as parameter to -i, but isn't set in the
> > script/has no default value. Either the related line from the previous
> > revision should be revived or the substitution should change to use
> > ${pidfile}, which _is_ set.
> 
> The attached diff fixes the problems in the sshguard rc file. I have
> replaced occurences of ${name} with "sshguard", in accordance with
> newer rc script style conventions. The diff has to be applied within
> the files sub-directory of the sshguard port.
> 
> The other problems of this port (see previous mail) are not fixed and
> should still be addressed ...

Sorry, I thought you'd committed this!

Thanks very much for the patch-- the trick with \$ to delay evaluation was
more elegant than my plan to stick that line inside _prestart.

Chris

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: [FIX] Re: FreeBSD Port: security/sshguard-pf

[Chris Rees]

Please commit it in the meantime, I'll fix the rest shortly.  Can't remember if 
you have a ports bit, if not "Approved" :)

Thanks,

Chris

On 14 April 2014 11:59:21 BST, Stefan Esser  wrote:
>Am 14.04.2014 10:25, schrieb Benjamin Podszun:
>> I'd say this is a bug in sshguard: Failing to start shouldn't exit
>with 0.
>> That said, it first and foremost is a bug in the port.
>> 
>> Looking at the rc script and the diff [1] the problem's easy enough:
>> ${sshguard_pidfile} is passed as parameter to -i, but isn't set in
>the
>> script/has no default value. Either the related line from the
>previous
>> revision should be revived or the substitution should change to use
>> ${pidfile}, which _is_ set.
>
>The attached diff fixes the problems in the sshguard rc file. I have
>replaced occurences of ${name} with "sshguard", in accordance with
>newer rc script style conventions. The diff has to be applied within
>the files sub-directory of the sshguard port.
>
>The other problems of this port (see previous mail) are not fixed and
>should still be addressed ...
>
>Regards, STefan
>
>-- 
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: FreeBSD Port: security/sshguard-pf

[Chris Rees]

On 14 April 2014 10:36:18 BST, Stefan Esser  wrote:
>Am 14.04.2014 10:25, schrieb Benjamin Podszun:
>> Looking at the rc script and the diff [1] the problem's easy enough:
>> ${sshguard_pidfile} is passed as parameter to -i, but isn't set in
>the
>> script/has no default value. Either the related line from the
>previous
>> revision should be revived or the substitution should change to use
>> ${pidfile}, which _is_ set.
>
>I just installed sshguard on one of my servers and noticed the same
>problem. The program is not started due to several bugs:
>
>1) $sshguard_pidfile vs. $pidfile as noticed by you

This one's my fault, sorry.

>2) Pasing of log files to watch. They are correctly processed by
>   sshguard_prestart(), but the result is not pasted into the
>   command line. (You can manually add "-l " options to
>   the command line in the rc script as a work around ...)

Don't think this one is, but I'll investigate.

Chris

>There are other deficiencies:
>
>a) The documentation lacks details about the mechanism used to block
>   attacks. E.g. in case of IPFW, blocking rules are injected in lines
>   55000 to 55050. You have to adapt your ruleset in such a way, that
>   any to-be-blocked service is only enabled at a later line, or the
>   blocking is ineffective. This port range should be mentioned at
>   least in the pkg message for ipfw. Better would be a section in
>   the man page, which explains the mechanism used by each backend.
>
>b) The security/sshguard-ipfw port is marked as NO_STAGE=no, while
>   security/sshguard seems to work just fine with staging enabled.
>   This is probably an oversight: when sshguard was fixed/verified
>   for staging, the sub-ports where not marked as staging clean.
>
>c) The MAKE_ARGS variable mention ACLOCAL, AUTOCONF and AUTOMAKE, but
>   no dependencies are registered for any of them.
>
>d) The master port's Makefile lists hosts, pf, and ipfw as possible
>   backends, selected by SSHGUARDFW, but does not mention ipfilter
>   as the fourth supported backend.
>
>I did not have time to check the code quality of the parser. I'm a
>bit suspicious, that it might be possible to attack sshguard via
>parameters passed under control of an attacker.
>
>If you create a PR, you may want to add these points to the PR ...
>
>Regards, STefan

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Quickly cleanroom building and installing software from ports

[Chris Rees]

I think you've both misunderstood :)

I'm quite familiar with package building; this is a wrapper script you've just 
suggested!

Never mind.

Chris

On 9 April 2014 19:52:31 BST, Freddie Cash  wrote:
>On Wed, Apr 9, 2014 at 11:36 AM, Chris Rees  wrote:
>
>> I'd be delighted if out of the box it could *install* just built
>packages.
>>  Can it do that?
>>
>
>​Poudriere is a package building tool (and repo building tool), nothing
>more.
>
>pkg(8) is how packages are installed​.  It's up to you to decide how
>you
>want the packages installed.  Write a wrapper script around poudriere
>to
>use pkg(8) to install the packages that were just created.
>
>
>
>-- 
>Freddie Cash
>fjwc...@gmail.com
>
>-- 
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Quickly cleanroom building and installing software from ports

[Chris Rees]

I'd be delighted if out of the box it could *install* just built packages.  Can 
it do that?

Chris

On 8 April 2014 22:12:19 BST, Steven Hartland  wrote:
>Look at poudriere its really good for exactly this, can even cross
>build
>different versions.
>
>Regards
>Steve
>
>- Original Message - 
>From: "Chris Rees" 
>To: 
>Sent: Tuesday, April 08, 2014 9:45 PM
>Subject: Quickly cleanroom building and installing software from ports
>
>
>> Hi all,
>>
>> I really enjoy using pkgng, and I love that all my packages are build
>on a clean system without any possible quirks.
>>
>> I found that installing from ports is a bit of a pain on these
>machines however, because I don't have any of the development 
>> packages installed (gcc47 etc).  I found I ended up installing these,
>but didn't like the 'pollution'.
>>
>> I chucked together two scripts, buildthis and upgradethis and figured
>people might find them useful.
>>
>> All you need do is install it and Tinderbox and either:
>>
>> # buildthis category/port [category2/port2 ]
>>
>> or
>>
>> # cd /usr/ports/category/port && buildthis
>>
>> A build will be created for Tinderbox if necessary and the port will
>have a package built and installed.
>>
>> Requires Tinderbox, if people want it around poudriere then please
>let me know.
>>
>> Caveat emptor: I just wanted this to work for me... the code quality
>isn't anything special
>>
>>
>http://www.bayofrum.net/cgi-bin/fossil/buildthis/tarball/buildthis-d503b895e8cc3883.tar.gz?uuid=d503b895e8cc3883dc5c6f2ed006b22ed10547ff
>>
>> Chris
>>
>> -- 
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>> ___
>> 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"
>> 
>
>
>-- 
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

Quickly cleanroom building and installing software from ports

[Chris Rees]

Hi all,

I really enjoy using pkgng, and I love that all my packages are build on 
a clean system without any possible quirks.


I found that installing from ports is a bit of a pain on these machines 
however, because I don't have any of the development packages installed 
(gcc47 etc).  I found I ended up installing these, but didn't like the 
'pollution'.


I chucked together two scripts, buildthis and upgradethis and figured 
people might find them useful.


All you need do is install it and Tinderbox and either:

# buildthis category/port [category2/port2 ]

or

# cd /usr/ports/category/port && buildthis

A build will be created for Tinderbox if necessary and the port will 
have a package built and installed.


Requires Tinderbox, if people want it around poudriere then please let 
me know.


Caveat emptor: I just wanted this to work for me... the code quality 
isn't anything special


http://www.bayofrum.net/cgi-bin/fossil/buildthis/tarball/buildthis-d503b895e8cc3883.tar.gz?uuid=d503b895e8cc3883dc5c6f2ed006b22ed10547ff

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: FreeBSD ports which are currently scheduled for deletion

[Chris Rees]

On 04/08/14 18:12, Mikhail T. wrote:

On 08.04.2014 12:55, Tijl Coosemans wrote:

On Tue, 08 Apr 2014 09:57:48 -0400 Mikhail T. wrote:

On 08.04.2014 08:00, freebsd-ports-requ...@freebsd.org wrote:

If people are using a port, then I would agree it should be kept
regardless of maintainer status. But that doesn't mean keeping
everything forever as long as it compiles.

Why not? Why not "keep everything forever as long as it compiles"? Where
is this idea coming from, that stuff must be continuously updated to be
considered usable?

It doesn't have to be updated continuously, but it has to be used.
Keeping a port requires effort.  It needs to be kept up to date with
infrastructural changes (like staging) and if nobody is using the port
that's just a waste of effort.

Tijl, there is no indication whatsoever, that ports on the chopping block are
not used. The argument put forth by the proponents of the removals is thus: "The
upstream authors haven't made a new release in a long time, therefor the
software must be neither any good, nor see much use."

I find this logic flawed -- some of my favorite books are more than 2000 years
old, for example... Their authors certainly aren't making new releases, yet they
continue to be maintained, built (published), and used by generations.

The closest we've ever come to estimating usage is the following: "If there is
any user-base to speak of, then there should be a person among them willing to
maintain the port -- or pay someone to maintain it." This, too, is flawed in my
opinion -- expecting a graphics-artist, a biologist, or an audiophile to also be
a half-decent software engineer is a stretch; expecting them to pay for
port-maintainership is also not fair, when the entire OS is free, done for fun,
rather than profit.

Though I agree, that unmaintained ports should be dropped when they break due to
things like security bugs or compiler-upgrades, the self-inflicted wounds like
infrastructure changes do not qualify. Volunteers taking it upon themselves to
perform such changes, should be prepared to deal with all that's required for 
them.




Hi Mikhail,

I think the term "self-inflicted" is a little strong... we can't really 
expect the tree to stand still.  I would expect people to loudly 
complain if their favourite port were dropped-- it's really not much 
effort to bring back, and some do come back.


If I have 1000 ports to fix, and decide to drop 50 of them because 
they're ancient and probably unused, it's no effort to restore and fix 
three if someone yells, and I've saved the effort of fixing 47 unused ports.


Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: LPPL10 license consequences intended? (arabic/arabtex)

[Chris Rees]

On 29 March 2014 11:01:04 GMT+00:00, John Marino  
wrote:
>On 3/29/2014 11:48, Chris Rees wrote:
>> On , John Marino wrote:
>>> This licensing topic is actually kind of a big mess that nobody
>seems to
>>> be leading, and it's not even clear if missing licenses is a
>problem.
>>> What's the policy?  It would be better to disable the entire
>framework
>>> than continue with this half-support.
>> 
>> The policy on the licensing framework is that it was submitted by a
>GSoC
>> student who has disappeared, and tabthorpe was the only one to step
>up
>> and take care of the "mess".
>> 
>> Unfortunately that's the case with a lot of stuff here-- someone
>drops
>> something, someone else generously picks it up and gets flak for
>> historical issues, as well as not being able to devote 110% of their
>> time to it.
>
>Ok, Chris, but that is not what happened here.  I noted that tabthorpe
>committed a license PR without changes 3 years ago and basically from
>courtesy I offered that he take the first look.  He wasn't getting any
>flak for making a mistake[1].  He also could have said, "no thanks"
>which, while disappointing, is his prerogative.  The problem was that
>the offer put the topic in tabthorpe's court and without response the
>topic died.  So the issue isn't lack of action, it's lack of response I
>guess.
>
>[1] It hasn't even fully been established that LPP10 is actually
>defined
>incorrectly although it leaning that way
>
>
>> If you're interested in the license framework, PLEASE fix it up!
>
>That is just the thing, I'm not pro-license framework.  I support it
>because it seems that ports wants it, but if you leave it to me, I'd
>remove all package-blocking capability and state publicly that LICENSE
>is a best guess, a courtesy, and not legally binding in any way (and
>FreeBSD isn't legally responsible in any way).  e.g. FYI, AS-IS, no
>guaranty
>
>I am not the person you want leading the license framework if you are a
>license nut.
>

I think you may have success as far as dports is concerned if you just disable 
it your end- there is a knob for that.

If you think it's inherently bad, you should probably do so-- you wouldn't hear 
complaints from dports users if you told them.

Chris

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Unable to install "Textproc/docbook-xml"

[Chris Rees]

On , Jerry wrote:

On: Saturday, March 29, 2014 12:41 AM, Kevin Oberman replied:



On Fri, Mar 28, 2014 at 7:06 AM, Jerry mailto:je...@seibercom.net> > wrote:

FreeBSD-10.0 amd64

I have been unable to get the “textproc/docbook-xml” to install. I
followed the directions in “UPDATING”; however, that did not seem to
make a difference. This is the build log for the port.

===>  Cleaning for docbook-xml-5.0_1
===>   docbook-xml-5.0_1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by docbook-xml-5.0_1 for building
===>  Extracting for docbook-xml-5.0_1
=> SHA256 Checksum OK for docbkx412.zip.
=> SHA256 Checksum OK for docbook-xml-4.2.zip.
=> SHA256 Checksum OK for docbook-xml-4.3.zip.
=> SHA256 Checksum OK for docbook-xml-4.4.zip.
=> SHA256 Checksum OK for docbook-xml-4.5.zip.
=> SHA256 Checksum OK for docbook-5.0.zip.
===>  Patching for docbook-xml-5.0_1
===>  Configuring for docbook-xml-5.0_1
===>  Staging for docbook-xml-5.0_1
===>   docbook-xml-5.0_1 depends on file:
/usr/local/share/xml/xmlcharent/catalog.xml - found
===>   docbook-xml-5.0_1 depends on file: /usr/local/bin/xmlcatmgr - 
found

echo "CATALOG \"/usr/local/share/xml/xmlcharent/catalog\""  >
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/catalog
/usr/local/bin/xmlcatmgr -c
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/catalog.xml
create
/usr/local/bin/xmlcatmgr -c
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/catalog.xml
 add nextCatalog "/usr/local/share/xml/xmlcharent/catalog.xml"
===>   Generating temporary packing list
cd /usr/ports/textproc/docbook-xml/work/docbkx412 &&  /bin/sh -c
'(/usr/bin/find -d $0 $2 | /usr/bin/cpio -dumpl $1 >/dev/null  2>&1)
&&  /usr/sbin/chown -Rh root:wheel $1 &&  /usr/bin/find -d $0 $2 -type
d -exec chmod 755 $1/{} \; &&  /usr/bin/find -d $0 $2 -type f -exec
chmod 444 $1/{} \;' -- .
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/4.1.2
/usr/local/bin/xmlcatmgr -c
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/catalog.xml
 add nextCatalog "/usr/local/share/xml/docbook/4.1.2/catalog.xml"
test "4.1.2" = 5.0 ||  echo "CATALOG
\"/usr/local/share/xml/docbook/4.1.2/docbook.cat 
\""  >>
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/catalog
cd /usr/ports/textproc/docbook-xml/work/docbook-xml-4.2 &&  /bin/sh -c
'(/usr/bin/find -d $0 $2 | /usr/bin/cpio -dumpl $1 >/dev/null  2>&1)
&&  /usr/sbin/chown -Rh root:wheel $1 &&  /usr/bin/find -d $0 $2 -type
d -exec chmod 755 $1/{} \; &&  /usr/bin/find -d $0 $2 -type f -exec
chmod 444 $1/{} \;' -- .
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/4.2
/usr/local/bin/xmlcatmgr -c
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/catalog.xml
 add nextCatalog "/usr/local/share/xml/docbook/4.2/catalog.xml"
test "4.2" = 5.0 ||  echo "CATALOG
\"/usr/local/share/xml/docbook/4.2/docbook.cat 
\""  >>
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/catalog
cd /usr/ports/textproc/docbook-xml/work/docbook-xml-4.3 &&  /bin/sh -c
'(/usr/bin/find -d $0 $2 | /usr/bin/cpio -dumpl $1 >/dev/null  2>&1)
&&  /usr/sbin/chown -Rh root:wheel $1 &&  /usr/bin/find -d $0 $2 -type
d -exec chmod 755 $1/{} \; &&  /usr/bin/find -d $0 $2 -type f -exec
chmod 444 $1/{} \;' -- .
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/4.3
/usr/local/bin/xmlcatmgr -c
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/catalog.xml
 add nextCatalog "/usr/local/share/xml/docbook/4.3/catalog.xml"
test "4.3" = 5.0 ||  echo "CATALOG
\"/usr/local/share/xml/docbook/4.3/docbook.cat 
\""  >>
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/catalog
cd /usr/ports/textproc/docbook-xml/work/docbook-xml-4.4 &&  /bin/sh -c
'(/usr/bin/find -d $0 $2 | /usr/bin/cpio -dumpl $1 >/dev/null  2>&1)
&&  /usr/sbin/chown -Rh root:wheel $1 &&  /usr/bin/find -d $0 $2 -type
d -exec chmod 755 $1/{} \; &&  /usr/bin/find -d $0 $2 -type f -exec
chmod 444 $1/{} \;' -- .
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/4.4
/usr/local/bin/xmlcatmgr -c
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/catalog.xml
 add nextCatalog "/usr/local/share/xml/docbook/4.4/catalog.xml"
test "4.4" = 5.0 ||  echo "CATALOG
\"/usr/local/share/xml/docbook/4.4/docbook.cat 
\""  >>
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/catalog
cd /usr/ports/textproc/docbook-xml/work/docbook-xml-4.5 &&  /bin/sh -c
'(/usr/bin/find -d $0 $2 | /usr/bin/cpio -dumpl $1 >/dev/null  2>&1)
&&  /usr/sbin/chown -Rh root:wheel $1 &&  /usr/bin/find -d $0 $2 -type
d -exec chmod 755 $1/{} \; &&  /usr/bin/find -d $0 $2 -type f -exec
chmod 444 $1/{} \;' -- .
/usr/ports/textproc/docbook-xml/work/stage/usr/local/share/xml/docbook/4.5
/usr/local/bin/xmlcat

Re: LPPL10 license consequences intended? (arabic/arabtex)

[Chris Rees]

On , John Marino wrote:

On 3/29/2014 11:14, Mark Linimon wrote:

On Sat, Mar 29, 2014 at 09:39:42AM +0100, John Marino wrote:

*this* is a crappy attitude though.


No, that's the sound of burnout.

IMVHO, one of the contributing factors to burnout is exactly this kind
of email.  It was certainly the case in my decision to step back over 
a

year ago.


Come on, Mark.
First of all, he started with the attitude, not me.  Don't dish it out
if you don't want a response.  But everyone is a victim nowadays, 
rights?




I appreciate that you are doing some good work for the project, but I
find your current attitude disappointing.  Not everything that ought
to happen quickly does, on a volunteer project.


tabthorpe is not just anybody, he's an assigned leader.  Despite his
intention to step down, he's still in that role today.  I do expect
people in leadership positions that they've agreed to assume to lead by
example.  Part of that is not just blowing off emails.  The "volunteer"
excuse is old and used as a blanket excuse for not doing what ought to
be done.  obviously it is often valid, but now it is often abused.

Happen quickly? sure, I agree with that, it's life.  Not Responding /
acknowledging quickly? I disagree.  It's easy to say, "Hey, I see the
issue, I'm pretty swamped for the next 10 days.  I'll take a look at it
after that if nobody else does in the meantime.  And we should think
about how to centralize licensing...".

This licensing topic is actually kind of a big mess that nobody seems 
to

be leading, and it's not even clear if missing licenses is a problem.
What's the policy?  It would be better to disable the entire framework
than continue with this half-support.


The policy on the licensing framework is that it was submitted by a GSoC 
student who has disappeared, and tabthorpe was the only one to step up 
and take care of the "mess".


Unfortunately that's the case with a lot of stuff here-- someone drops 
something, someone else generously picks it up and gets flak for 
historical issues, as well as not being able to devote 110% of their 
time to it.


If you're interested in the license framework, PLEASE fix it up!

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: WARNING: devel/icu: recent update redners openldap-server and other ports unusable!

[Chris Rees]

Shane Ambler  wrote:
>On 08/02/2014 08:24, O. Hartmann wrote:
>> 
>> Today a couple of updates has been introduced, one of them was an
>> update of port devel/icu.
>> 
>> I the good manner/tradition of updating UPDATING, I expect a
>> warning/hint/advice a couple of days from now - when everybody has
>> already stepped into the mess.
>> 
>> On several boxes running 11.0-CURRENT and 9.2-STABLE, updating ports
>> including devel/icu renders many ports unusable due to a library
>> version bump in libicu.
>> 
>> After updating ports relying on devel/icu via
>> 
>> portmaster -r devel/icu
>> 
>> and the updating of port
>> 
>> net/openldap24-server
>> 
>> (which is openldap-sasl-server in my case), OpenLDAP doesn't start
>> anymore on all boxes affected by the update of devel/icu!
>> 
>> I always get the error
>> 
>> 52f5551f hdb_db_init: Initializing HDB database
>> 52f5551f olcDbDirectory: value #0: invalid path: Permission denied
>> 52f5551f config error processing olcDatabase={1}hdb,cn=config:
>> olcDbDirectory: value #0: invalid path: Permission denied 52f5551f
>> send_ldap_result: conn=-1 op=0 p=0 52f5551f slapd destroy: freeing
>> system resources. 52f5551f syncinfo_free: rid=001
>> 52f5551f slapd stopped.
>> 52f5551f connections_destroy: nothing to destroy.
>> /usr/local/etc/rc.d/slapd: WARNING: failed to start slapd
>> 
>> 
>> This obscure 
>> 
>> olcDbDirectory: value #0: invalid path: Permission denied
>> 
>> is not obvious to me. The server ran minutes ago BEFORE the update,
>the
>> directories containing the DB5 databases have all the correct
>ownership
>> (ldap:ldap, I suspected first a misconfiguration as this error seems
>> typical for a misconfiguration of the ownership).
>> 
>> Does anyone see the same problem? And maybe please would put out some
>> notes in UPDATING within a considerable narrow timeframe regarding
>> devel/icu! It seems, FreeBSD's ports systems get more and more messy.
>> 
>> oh
>> 
>
>Not the same problem but I did see building postgresql server break -
>I changed databases/postgresql92-server/makefile with the following.
>Ideally the test for *_52 should be added to configure.in rather than
>replacing the oldest.
>
>--- a/databases/postgresql92-server/Makefile
>+++ b/databases/postgresql92-server/Makefile
>@@ -355,6 +355,8 @@ post-patch:
> .  if defined(SERVER_ONLY) && ${PORT_OPTIONS:MICU}
>@${REINPLACE_CMD} -E -e \
>"s|^(m4_if.*)2.6[0-9](.*Autoconf version
>)2.6[0-9]|\1${AUTOCONF_VERSION}\2${AUTOCONF_VERSION}|g" \
>+   -e "s|ucol_open_43|ucol_open_52|g" \
>+   -e "s|ucnv_fromUChars_43|ucnv_fromUChars_52|g" \
>${WRKSRC}/configure.in
> .  endif

Hmm, the ICU support was written by Palle, hence we are the upstream for it.

Palle, do you think this is a good fix?

Thanks Shane, by the way :)

Chris
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Maximizing the use of binary packages and minimizing building packages

[Chris Rees]

On 01/14/14 17:46, Matt Reimer wrote:

I'd like to switch from installing and upgrading our packages using
portmaster/portupgrade to using pkg + binary packages from the ports
cluster as much as possible.

I understand that the ports cluster builds its packages using default
options, but some of our packages we need built with custom options (e.g.
enable mysql for postfix).

Is there a tool that can look at /var/db/ports/foo/options and tell which
options differ from the default options? Then I could decide whether I can
live with the defaults (and therefore use the binary package), or whether
to pkg-lock that package and update it by hand using portmaster.

Or is there a better way to handle this situation, where I want to use
binary packages where possible and only build when necessary?



Mixing ports and packages is discouraged and can get messy, because 
upgrades can get out of sync...


Your best bet is to set up a little build server, if you have the 
hardware-- I just use a computer I have hidden away from my wife for it, 
which pulls down changes and builds a new repo using Tinderbox every day.


It works really well, so if you're interested, I suppose I could bash 
some of my scripts into shape and document how to do it.


Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: transmission-gtk not workin :-(

[Chris Rees]

On 12/30/13 19:45, CeDeROM wrote:
> Hey hey :-)
>
> Stil there is some problem with transmission-gtk on FreeBSD 10.0-RC3 AMD64;
>
> % transmission-gtk
> Assertion failed: (! _cairo_surface_has_mime_data (surface)), function
> cairo_surface_mark_dirty_rectangle, file cairo-surface.c, line 1174.
> Abort (core dumped)
> % uname -a
> FreeBSD hexagon 10.0-RC3 FreeBSD 10.0-RC3 #0 r259778: Mon Dec 23
> 23:27:58 UTC 2013
> r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
> % transmission-gtk -v
> transmission-gtk 2.82 (14160)
>
> Best regards :-)
> Tomek
>
Didn't we decide this was a gnome system tray issue?

Chris

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: portdowngrade(CVS) deprecated -> alternative for portsnap(8) usage

[Chris Rees]

OK, done :)

Chris

 

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: 10.0-hosted tinderbox: 8.4 builds broken?

[Chris Rees]

On 2013-10-20 15:51, Alexey Dokuchaev wrote:

On Sun, Oct 13, 2013 at 01:36:45PM +0100, Chris Rees wrote:
It appears that really weird SRCBASE assumptions are made throughout 
the
code.  I'll have to put a temporary hack in to just make SRCBASE 
appear

inside the chroot whatever it's set to.  Setting and unsetting SRCBASE
just breaks different things in weird ways, and this is the only 
reliable

fix I've found.


I've just setup another tinderbox here on 11-CURRENT and did a fresh
checkout from CVS; I confirm that I can build packages for both 9.2 and
10.0-BETA just fine now, thanks!

However I've noticed another regression: doing chmod g+w 
/usr/ports/distfiles

in the middle of the tinder run totally confuses it: all build attempts
after chmod fail with identical tiny log files:

  building lcms2-2.5 in directory /usr/home/danfe/tb/9.2-wip
  make: cannot open /a/ports/Mk/bsd.port.mk.
  cd: /usr/ports/graphics/lcms2: No such file or directory

The reason for a chmod: I normally build ports from a user, and to 
allow
it to fetch distfiles, give write permissions to wheel group.  I also 
do
./tc configDistfile -c /usr/ports/distfiles, and it always changed 
perms
back.  It's annoying, but I can live with it: just chmod the damn 
directory

again.

chmod'ing in the middle of tinder run is because I often do the runs 
while

installing something from ports manually at the same time.

Previously tinderbox simply complained like this in the end of the 
build

log:


Fatal error: filesystem was touched prior to 'make install' phase
distcache changed
permissions expected 0755 found 0775


But this (and subsequent) packages were still built successfully.

Now chmod'ing totally screws up the whole (remaining) build.

BTW, would it be possible to prevent forcing 0755 perms?  I don't 
really

see any point for doing this in the first place...


This annoys me for the same reason, and eventually I gave up doing make 
fetch without sudo :P


I would very much like to fix that, so I shall try to see what I can do.

I think it may be an mtree thing.

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: 10.0-hosted tinderbox: 8.4 builds broken?

[Chris Rees]

On 12 Oct 2013, at 12:49, Chris Rees wrote:

> [cross posted to tinderbox-list]
> 
> On 2013-10-09 22:27, Alexey Dokuchaev wrote:
>> On Wed, Oct 09, 2013 at 09:11:10PM +0100, Chris Rees wrote:
>>> Alexey, if you're interested, the patch hitting CVS is at:
>>> http://www.bayofrum.net/~crees/patches/tinderbox-calculate-deps-in-chroot-9.diff
>> Ah, it seems you mean it's one of the patches recently committed, not the
>> proposed fix. ;-)
>> I've 'cvs up -A' again, and applied the patch in reverse mode.  Strangely,
>> now every build log (inc. dependent packages) immediately ends with this
>> message:
>>  jexec: getpwnam: root: No such file or directory
> 
> OK, try cvs head with
> 
> http://www.bayofrum.net/~crees/patches/tinderbox-chroot-srcbase.diff
> 
> It appears that I may have been overexcited with my fix for Olli's problem, 
> but this fixes it in a less drastic way with fewer assumptions.
> 
> This patch works for me, so if you confirm I'd like to ask Joe to approve 
> please!
> 
> Also, Bernhard, I'm certain that redports will run as well as it did with 
> patch7 if you apply this patch.
> 
> I'm really sorry for the breakage :(

It appears that really weird SRCBASE assumptions are made throughout the code.  
I'll have to put a temporary hack in to just make SRCBASE appear inside the 
chroot whatever it's set to.  Setting and unsetting SRCBASE just breaks 
different things in weird ways, and this is the only reliable fix I've found.

Joe, please can I stick this in, and merge to the beta?

http://www.bayofrum.net/~crees/patches/tinderbox-fake-srcbase.diff

Alexey, try this patch.  This one definitely works for me, and gets the 
dependencies working correctly.

Chris
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: 10.0-hosted tinderbox: 8.4 builds broken?

[Chris Rees]

[cross posted to tinderbox-list]

On 2013-10-09 22:27, Alexey Dokuchaev wrote:

On Wed, Oct 09, 2013 at 09:11:10PM +0100, Chris Rees wrote:

Alexey, if you're interested, the patch hitting CVS is at:

http://www.bayofrum.net/~crees/patches/tinderbox-calculate-deps-in-chroot-9.diff


Ah, it seems you mean it's one of the patches recently committed, not 
the

proposed fix. ;-)

I've 'cvs up -A' again, and applied the patch in reverse mode.  
Strangely,
now every build log (inc. dependent packages) immediately ends with 
this

message:

  jexec: getpwnam: root: No such file or directory


OK, try cvs head with

http://www.bayofrum.net/~crees/patches/tinderbox-chroot-srcbase.diff

It appears that I may have been overexcited with my fix for Olli's 
problem, but this fixes it in a less drastic way with fewer assumptions.


This patch works for me, so if you confirm I'd like to ask Joe to 
approve please!


Also, Bernhard, I'm certain that redports will run as well as it did 
with patch7 if you apply this patch.


I'm really sorry for the breakage :(

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: 10.0-hosted tinderbox: 8.4 builds broken?

[Chris Rees]

That's really annoying... I'll have to track it down Friday I'm afraid.

Alexey, if you're interested, the patch hitting CVS is at:

http://www.bayofrum.net/~crees/patches/tinderbox-calculate-deps-in-chroot-9.diff

And

http://www.bayofrum.net/~crees/patches/tinderbox-addPort-a.diff

The patch Bernhard reports didn't have this problem is:

http://www.bayofrum.net/~crees/patches/tinderbox-calculate-deps-in-chroot-7.diff

Chris

Sent from my android device.

-Original Message-
From: "Bernhard Fröhlich" 
To: Alexey Dokuchaev 
Cc: "po...@freebsd.org Ports" , Chris Rees 

Sent: Wed, 09 Oct 2013 20:52
Subject: Re: 10.0-hosted tinderbox: 8.4 builds broken?

Am 09.10.2013 13:10 schrieb "Alexey Dokuchaev" :
>
> Hi there,
>
> I've started to observe the following error when trying to tinderbuild
> (freshly cvs up'ed from marcuscom.com) a port for -b 8.4:
>
>   ...
>   add_pkg pkg-1.1.4_7.tbz
>   adding dependencies
>   pkg_add pkg-1.1.4_7.tbz
>   The package management tool is not yet installed on your system.
>   Do you want to fetch and install it now? [y/N]: tar: Error opening
> archive: Failed to open 'pkg-1.1.4_7.tbz'
>   /buildscript: ./pkg-static: not found
>   error in dependency pkg-1.1.4_7.tbz, exiting
>
> In fact, pkg-1.1.4_7.txz *is* generated for 8.4, but extensions are
> different (.txz vs. .tbz).
>
> Why does it happen?  I was under impression that 8.x will never switch to
> pkgng.  Am I doing something wrong, or need to configure my tindy somehow?

I have seen the same on redports today. It did work fine with crees chroot
patch r7 but seems to be broken with what has landed it the ports tree.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: 10.0-hosted tinderbox: 8.4 builds broken?

[Chris Rees]

On 2013-10-09 19:59, Alexey Dokuchaev wrote:

On Wed, Oct 09, 2013 at 05:59:50PM +0200, Baptiste Daroussin wrote:

On Wed, Oct 09, 2013 at 06:09:55PM +0700, Alexey Dokuchaev wrote:
> Why does it happen?  I was under impression that 8.x will never switch to
> pkgng.  Am I doing something wrong, or need to configure my tindy somehow?
>
1/ yes 8.x will one day switch to pkgng :) but that is not the case 
yet.
2/ this is one of the design bugs of tinderbox. The very recent update 
of

tinderbox might have fixed that one.


It looks more like some recent update of tinderbox actually broke it: 
now,

regardless of -b switch of tinderbuild command, "building for:" line in
the logs always says "10.0-ALPHA4 i386", which is just another jail of 
mine.


I will try to track it down and report of the results later.


Please CC me in replies.

I can't reproduce myself, but I can try to look tomorrow or Friday.

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

[CFT] Tinderbox using chroots to calculate dependencies

[Chris Rees]

Hi all,

I've been working on fixing Tinderbox to calculate dependencies in 
chroots instead of on the host system (meaning things like cvs 
dependencies are correct).


It's a fairly drastic change, and a few guys have generously volunteered 
their time to test it, but I need a few more testers before committing 
it and getting it in the ports tree.


Normally I'd just be patient, but this is holding up the compiler 
abstraction mechanism (USES=compiler), so please, if you use Tinderbox, 
give this a try!


This patch is to a head checkout (doesn't work with the port, sorry);

http://www.bayofrum.net/~crees/patches/tinderbox-calculate-deps-in-chroot-8.diff

Alternatively,

http://www.bayofrum.net/~crees/scratch/tinderbox-chroot.tbz

contains a head checkout and the patch.

Please test, it's easy!

cd /usr/local/tinderbox
mv scripts.old
fetch -o - http://www.bayofrum.net/~crees/scratch/tinderbox-chroot.tbz | 
tar xjvf -

mv tinderbox scripts
cp scripts.old/*.ph scripts/
cp scripts.old/webui/inc_*.php scripts/webui

Ion-Mihai, this will need to go in the port asap if it works for most 
people, otherwise Tinderbox will not work with the ports tree once 
compiler.mk is committed.  I am happy to deal with that for you if 
necessary.


Chris

PS I'm especially keen to hear about issues involving USE_XZ; Olli Hauer 
had some trouble, but I think it's a local issue; ideas welcome!


http://marcuscom.com/pipermail/tinderbox-list/2013-September/003101.html

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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: Problem with pkg-config and porting

[Chris Rees]

On 16 June 2013 20:07, Rod Person  wrote:
> On 06/16/13 14:42, Chris Rees wrote:
>> PORTNAME=   dunst
>> PORTVERSION=1.0.0
>> #PORTREVISION=  1
>> EXTRACT_SUFX=   .tar.bz2
>> CATEGORIES= sysutils
>> MASTER_SITES=   http://www.knopwob.org/public/dunst-release/
>>
>> MAINTAINER= rodper...@rodperson.com
>> COMMENT=Lightweight notification deamon
>>
>> LIB_DEPENDS=dbus:${PORTSDIR}/devel/dbus \
>> freetype:${PORTSDIR}/print/freetype2 \
>> cairo:${PORTSDIR}/graphics/cairo \
>>
>> /usr/local/libdata/pkgconfig/xscrnsaver.pc:${PORTSDIR}/x11/libXScrnSaver
>> This shouldn't be a LIB_DEPENDS.  LIB_DEPENDS checks the output of ldconfig 
>> -r.
>>
>> The line should probably read Xss:${PORTSDIR}/x11/libXScrnSaver
> Thanks Chris and Ruslan.
>
> This worked.
>
>> Have a try-- for future reference, depending on a *file* needs
>> RUN_DEPENDS and/or BUILD_DEPENDS.
>>
>> Chris
> I then changed LIB_DEPENDS to BUILD_DEPENDS and this installed
> and it built and installed dbus, freetype and cairo, even though I
> thought these were already installed since using the LIB_DEPENDS found them?
>
> I'll have to read up on these again.
>

LIB_DEPENDS is OK for cairo, dbus and freetype because those are
library names; they should not be used with BUILD_DEPENDS because that
looks for the executables cario, dbus and freetype that don't exist.
Since they don't exist, it tries to install the port again.

Chris
___
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: Problem with pkg-config and porting

[Chris Rees]

On 16 June 2013 19:34, Rod Person  wrote:
> Hi,
>
> I am attempting to create a port for dunst
> (http://www.knopwob.org/dunst/). It requires xscrnsaver.pc to build.
> I've found that it is located in the port x11/libXScrnSaver.  I've
> created a Makefile that checks and installs that port, but even after it
> successfully installs I still get the following error:
>
> ===>   dunst-1.0.0 depends on shared library:
> /usr/local/libdata/pkgconfig/xscrnsaver.pc - not found
> ===>Verifying install for /usr/local/libdata/pkgconfig/xscrnsaver.pc
> in /usr/ports/x11/libXScrnSaver
> ===>   Returning to build of dunst-1.0.0
> Error: shared library "/usr/local/libdata/pkgconfig/xscrnsaver.pc" does
> not exist
> *** [lib-depends] Error code 1
>
> Stop in /usr/home/roddierod/Projects/Ports/dunst.
>
> I've verified that xscrnsaver.pc does exist in the correct location.
>
> Here is what I have so far for the Makefile:
>
> PORTNAME=   dunst
> PORTVERSION=1.0.0
> #PORTREVISION=  1
> EXTRACT_SUFX=   .tar.bz2
> CATEGORIES= sysutils
> MASTER_SITES=   http://www.knopwob.org/public/dunst-release/
>
> MAINTAINER= rodper...@rodperson.com
> COMMENT=Lightweight notification deamon
>
> LIB_DEPENDS=dbus:${PORTSDIR}/devel/dbus \
> freetype:${PORTSDIR}/print/freetype2 \
> cairo:${PORTSDIR}/graphics/cairo \
>
> /usr/local/libdata/pkgconfig/xscrnsaver.pc:${PORTSDIR}/x11/libXScrnSaver

This shouldn't be a LIB_DEPENDS.  LIB_DEPENDS checks the output of ldconfig -r.

The line should probably read Xss:${PORTSDIR}/x11/libXScrnSaver

Have a try-- for future reference, depending on a *file* needs
RUN_DEPENDS and/or BUILD_DEPENDS.

Chris
___
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: Are ports supposed to build and run on 10-CURRENT?

[Chris Rees]

It's worth bearing in mind that head becomes a release every so often.  If you 
don't make sure your ports build there, it makes life harder for people running 
and testing it, and makes for a mad rush and scramble to fix broken ports 
before a major release.

Since the port can often be fixed with a USE_GCC=any conditional on OSVERSION, 
I must question how much of a hardship it really is...

Chris
___
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: Can't build Xorg --> make failed for ports-mgmt/pkg

[Chris Rees]

On 12 June 2013 19:34,   wrote:
> I'm attempting to install kde4 in FreeBSD 10-current, after 3 days
> dealing with some dependency issues I was able to install kde4  with
> portmaster...
>
> Before kde  already installed Xorg, but I get a "green" and sometime
> "purple"screen when X starts, the log pointed me to this problem:
>
> http://www.mail-archive.com/freebsd-current@freebsd.org/msg146880.html
>
> However when trying to rebuild Xorg with portmaster it stops on "pkg"
> with the following error:
>
> 
> --- pkg-static ---
> gcc -O2 -pipe -I/usr/local/include -fno-strict-aliasing
> -I/data/ports/ports-mgmt/pkg/work/pkg-1.0.12/pkg-static/../libpkg
> -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall
> -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
> -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align
> -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
> -Wold-style-definition -Wno-pointer-sign  -L/usr/local/lib -static -o
> pkg-static add.o audit.o autoremove.o backup.o check.o clean.o
> create.o delete.o event.o info.o install.o main.o progressmeter.o
> query.o register.o repo.o rquery.o update.o upgrade.o search.o set.o
> shlib.o updating.o utils.o version.o which.o fetch.o shell.o stats.o
> -L/data/ports/ports-mgmt/pkg/work/pkg-1.0.12/pkg-static/../libpkg
> -lpkg  -larchive  -lutil  -lpthread  -lsbuf  -lfetch  -lssl  -lcrypto
> -lmd  -lz  -lbz2  -llzma
> -L/data/ports/ports-mgmt/pkg/work/pkg-1.0.12/pkg-static/../external/sqlite
> -lbsdyml -lsqlite3  -larchive  -lsbuf  -lfetch  -lpthread  -lelf
> -lssl  -lcrypto  -lmd  -lz  -lbz2  -llzma -ledit  -lncursesw -ljail
> /usr/local/lib/libpkg.a(pkgdb.o): In function `pkgdb_cmd':
> pkgdb.c:(.text+0x947f): undefined reference to `sqlite3_shell'
> *** [pkg-static] Error code 1
>
> make: stopped in /data/ports/ports-mgmt/pkg/work/pkg-1.0.12/pkg-static
> 1 error
> =
>
> Is anyone else having this problem? Or has anyone build/installed
> xorg+kde4 from ports on current with sucess?
>

You possibly have an out-of-date wrkdir for pkg.

Try removing all the work/ directories;

# echo `make -f /usr/share/mk/bsd.port.mk
-VWRKDIRPREFIX`/usr/ports/*/*/work | xargs rm -r

Chris
___
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: Binary packages (from ports) how often are they built ?

[Chris Rees]

It depends entirely on the version that you are after.  There is a release set 
of packages that isn't updated, but the stable set are updated fairly regularly.

Have a look in man pkg_add for some environment variables to set to change the 
site/set you are downloading.

Chris
___
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: The vim port needs a refresh

[Chris Rees]

On 7 June 2013 19:56, David O'Brien  wrote:
> On Sat, May 25, 2013 at 09:50:50AM +0100, Chris Rees wrote:
>> For years, people have been begging him to get over his fear of
>> OPTIONS, and he sits in the way of progress against almost everyone's
>> wishes.
>
> It's funny -- it's not just my fear of options -- every FreeBSD using
> co-worker I talk to frequently about OPTIONS do not like them either.

What's not funny is your dreadful attitude at replying to email.  The
number of timeouts on the vim and bash ports are shameful, and we're
stuck with two bash ports because you're too lazy to keep the main one
up to date.  I really have no idea why you're still allowed to plant
your flag in the ports tree and stand in the way of progress.  Please
consider dropping the ports, so people who are happy to keep them up
to date and don't ignore bug reports can work on them.

Chris
___
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: How to build openjdk7 for customized FreeBSD system

[Chris Rees]

On 8 Jun 2013 04:05, "Peter Xu"  wrote:
>
> I did this in a stupid way. I am sending this out in case someone met the
> same problem (or to say, you want to build openjdk on an platform that
have
> no older version of JDK supported).
>
> The main idea is, firstly find a generic FreeBSD 8.2 system, build the
> openjdk7 package (well, there is no problem on generic system, as long as
> you are using the port collections corresponding to that specific version
I
> suppose). Then, we can leverage all the Java-built output (includes
> *.class, *.jar, and some *.java/*.[ch] if they are auto-generated by the
> build system using JVM) in the generic systems, replacing all the
> $(JAVAC_CMD) and $(JAVAH_CMD) lines in Makefiles with something like (or
we
> can try direct copy of the object files, but sometimes we still need to do
> this since the dependencies of 'make' are not the JAR files sometimes):
>
> scp $GENERIC_BSD:$JAR_FILE_PATH $PRIVATE_BSD:$JAR_FILE_PATH
>
> Or to say, we do fetch the good 'jar' from the generic systems instead of
> invoking a sick JVM and build it until we met error and stop the make
> process.
>
> I suppose all these things need some knowledge on the Makefile structure
of
> openjdk. This is nasty work, but it did work for us.
>
> Another solution I thought about is cross-compile the whole JDK on a
> generic system, and copy all the private C libraries on the private system
> to the generic one before-hand (this may only be working when the generic
> system has cross-toolchain I suppose, or in my case that the two systems
> are using the same CPU arch). Just an idea, no need to try currently.

I'm really pleased you fixed it in the end; I'd just succeeded in making
you a package too, but never mind.

Now you have time to migrate your hacks to later FreeBSD, and even get some
of them committed ;)

Chris
___
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: Conversion to new options framework over

[Chris Rees]

On 7 June 2013 18:55, Jim Trigg  wrote:
> On Thu, Jun 06, 2013 at 08:45:10AM +0200, Baptiste Daroussin wrote:
>> The compatibility code to parse the WITH/WITHOUT entries in make.conf
>> will be removed in 6 months either.
>>
>> Do not forget to convert your configuration (make.conf, portsconf etc).
>> A reminder will be send a month before the removal of the compatibility
>> code.
>
> It would be useful to provide a pointer to instructions for doing so --
> what exactly replaces WITH/WITHOUT entries in make.conf? For example,
> my dedicated server has WITHOUT_X11=yes in /etc/make.conf because it's
> headless and doesn't run an X server. What should that become?
>
> I tried googling, and the github doc page's only mention of make.conf is
> to add "WITH_PKGNG=yes". Likewise the FreeBSD Handbook. The wiki
> apparently just points to the Handbook.

WITH_PKGNG is not a classical OPTION, because it doesn't apply to any
port in particular.

There is some documentation for users at [1], basically you need to
change any WITH_ variables to OPTIONS_SET=, and WITHOUT_ to
OPTIONS_UNSET=.  I'll hopefully find some time soon to get it in the
Handbook

For example;

WITHOUT_X11=yes
WITH_CUPS=yes
WITHOUT_PULSEAUDIO=yes

becomes

OPTIONS_SET=CUPS
OPTIONS_UNSET=PULSEAUDIO X11

Chris

[1] https://wiki.freebsd.org/Ports/Options/OptionsNG#What_users_need_to_know
___
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] dialog4ports does not popup anymore only for global options

[Chris Rees]

On 7 June 2013 18:49, Andrew W. Nosenko  wrote:
> On Fri, Jun 7, 2013 at 8:15 PM, Chris Rees  wrote:
>>
>> I can see your point when talking about DOCS, but for NLS it's insanity
>> *for general use*.  Give me an example of where NLS non-globals are
>> appropriate and I'll shut up.
>
> The GIMP in Russian locale.
> GNU Make in any non-English locale.

I guess you mean the translations are bad?

Chris
___
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] dialog4ports does not popup anymore only for global options

[Chris Rees]

On 7 Jun 2013 17:57, "Michael Gmelin"  wrote:
>
> On Fri, 7 Jun 2013 15:42:44 +0200
> Baptiste Daroussin  wrote:
>
> > On Fri, Jun 07, 2013 at 03:30:15PM +0200, Tijl Coosemans wrote:
> > > On 2013-06-07 13:40, Baptiste Daroussin wrote:
> > > > On Fri, Jun 07, 2013 at 12:46:08PM +0200, Tijl Coosemans wrote:
> > > >> On 2013-06-07 12:17, Baptiste Daroussin wrote:
> > > >>> On Fri, Jun 07, 2013 at 01:15:49PM +0300, Vitaly Magerya wrote:
> > >  Baptiste Daroussin wrote:
> > > >> Is it possible to still show the dialog if one of those
> > > >> options implies additional dependencies?
> > > >>
> > > >> If not, what should those of us who do not want them
> > > >> installed do?
> > > >
> > > > make config will always show those options so you can always
> > > > tune them.
> > > >
> > > > just make config-conditional will not fireup a new dialog
> > > > automatically if the defined options are only those from the
> > > > global options.
> > > 
> > >  I see. As far as I can tell though, and correct me if I'm
> > >  wrong, but 'make install' doesn't show those options. It also
> > >  does not show those options for dependent ports. Neither does
> > >  'make config-recursive'.
> > > 
> > >  Tools like portmaster will now ignore those as well during
> > >  install and reinstall.
> > > 
> > >  So, again, what are my options if I don't want dependencies to
> > >  be pulled in silently?
> > > >>>
> > > >>> You have no options and you never had one in the ports tree
> > > >>> sorry.
> > > >>>
> > > >>> If you have a way to implement that cleanly, I'll be happy to
> > > >>> push such features in the ports but really I see a way to do
> > > >>> what you ask for.
> > > >>
> > > >> How about only suppressing the dialog if the options have been
> > > >> explicitly set or unset in make.conf?
> > > >
> > > > That would be easy but is that a really desired feature?
> > >
> > > I can only speak for myself, but I don't see DOCS as a global
> > > option. For some ports I want documentation, for others I don't, so
> > > I want the dialog to show up even if DOCS is the only option.
> > >
> > > There doesn't seem to be a clear cut line between global and per
> > > port options and different users have different opinions about it.
> > >
> > > Can you make it such that config-conditional suppresses the dialog
> > > if all options have been explicitly set or unset either through
> > > command line, make.conf or optionsfile? Or in other words only show
> > > the dialog if one of the options falls back to a default value (e.g.
> > > when a new option has been added to a port and that option has not
> > > been set globally).
> > >
> > > I think that would allow anyone to set/unset any option globally and
> > > not be bothered by dialogs without enforcing that view on everybody
> > > else. You wouldn't need GLOBAL_OPTIONS any more then.
> > >
> >
> > Ok so I misunderstood at first.
> >
> > That looks not easy to do, and I'm a bit borred with hacking the
> > options.
> >
> > If someone do something in that direction, I'll be happy to review
> > and help, but honnestly I don't plan to do it myself.
> >
> > regads,
> > Bapt
>
> I can feel your pain, Bapt :)
>
> Anyway, I think the problem with those options (especially DOCS) is that
> they are not really "global" in that you want to set them for all
> ports, but more like "general" as in well-known. So many ports provide
> them and the user has a good idea what they're supposed to mean, but
> ultimately you don't want to set them to the same value for all ports.
>
> Regardless of implementation details I would like to see something like
> the following at least for DOCS, either through config-recursive or -
> maybe more likely - through a tool like portmaster:
>
> After starting the build process and collecting dependencies, an ncurses
> dialog should be shown that says "The following ports provide
> documentation" and a check-box list showing all packages as well as a
> "All" and "None" options on top of the list. That way the user can
> easily select which port documentation to install and at the same time
> can easily set it for all affected ports, e.g.
>
> # portmaster shells/bash
>
> +-- Install documentation -+
> + [ ] All  +
> + [X] None +
> + [ ] converters/libiconv  +
> + [ ] devel/gettext+
> + [ ] shells/bash  +
> +--+
> +  < OK >   < Cancel > +
> +--+
>
> I have no idea what it would take to implement this in a sane way
> within the current framework, but IMHO this would provide a pretty good
> user experience.
>
> Cheers,
> Michael
>
> p.s. - If you wanted to provide this for more than one "general"
> option, dialog4ports' section feature might become handy, e.g.:
>
> + General options -+
> + [ ] All 

Re: devel/flatzebra broken, maintainer timeout, please reverse commit

[Chris Rees]

On 7 Jun 2013 10:16, "Ganael LAPLANCHE" 
wrote:
>
> On Fri, 7 Jun 2013 09:52:44 +0100 (BST), Anton Shterenlikht wrote
>
> >   Anton, can you test it and tell me how it goes ?
> >
> > works fine on ia64
>
> Thanks.
>
> I'll wait for Edwin approval and commit the update.

I think maintainer timeout applies here; unless there was an
acknowledgement from the maintainer before we shouldn't make people wait
any longer.

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

Re: devel/flatzebra broken, maintainer timeout, please reverse commit

[Chris Rees]

On 6 Jun 2013 18:27, "Matthias Andree"  wrote:
>
> Am 06.06.2013 19:14, schrieb Chris Rees:
> > On 6 June 2013 16:11, Ganael LAPLANCHE 
wrote:
> >> On Thu, 6 Jun 2013 16:07:08 +0100 (BST), Anton Shterenlikht wrote
> >>
> >>> yes, this helps on ia64, thank you.
> >>> Probably will help on amd64, will check later.
> >>> Sorry for not thinking about is myself,
> >>> I just tried to update with portmaster, as usual.
> >>
> >> Tested on amd64, I can reproduce the problem.
> >>
> >> I'll have a look at that, thanks for reporting the problem.
> >>
> >
> > Usual approach is:
> >
> > CONFLICTS_BUILD= ${PKGBASE}-[0-9]*
> >
> > which clearly informs the user that's what s/he has to do.
>
> What an unfortunate situation, and especially recommendation.
>
> I'd propose that the build be fixed so it prefers the local headers from
> the distfiles, rather than the older ones in the system.

That's the proper fix- sorry I was unclear there; I meant if it can't be
fixed easily.

Chris

> Can we please put that into the porter's handbook as a test requirement,
> à la "installed older version of the port must not break the build of a
> newer version"?  This is a frequent nuisance.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: devel/flatzebra broken, maintainer timeout, please reverse commit

[Chris Rees]

On 6 June 2013 16:11, Ganael LAPLANCHE  wrote:
> On Thu, 6 Jun 2013 16:07:08 +0100 (BST), Anton Shterenlikht wrote
>
>> yes, this helps on ia64, thank you.
>> Probably will help on amd64, will check later.
>> Sorry for not thinking about is myself,
>> I just tried to update with portmaster, as usual.
>
> Tested on amd64, I can reproduce the problem.
>
> I'll have a look at that, thanks for reporting the problem.
>

Usual approach is:

CONFLICTS_BUILD= ${PKGBASE}-[0-9]*

which clearly informs the user that's what s/he has to do.

Chris
___
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: JVM panic when build openjdk7 on private FreeBSD 8.2

[Chris Rees]

On 2 Jun 2013 13:47, "Xu Zhe"  wrote:
>
> 于 6/2/13 6:29 AM, Ronald Klop 写道:
>>
>> On Thu, 30 May 2013 02:53:01 +0200, Xu Zhe  wrote:
>>
>>
>>> 于 5/30/13 1:42 AM, Chris Rees 写道:
>>>>
>>>> On 29 May 2013 09:28, Peter Xu  wrote:
>>>>>
>>>>> Hi, all,
>>>>>
>>>>> I got strange issue when trying to build opendjk7 using ports utility
on a
>>>>> private-built FreeBSD 8.2 system. Here is the output of make:
>>>>>
>>>> 
>>>>
>>>> I'm going to suggest that you upgrade to FreeBSD 8.3-- it's not a big
>>>> jump, so it shouldn't break anything.
>>>>
>>>> Unfortunately ports can't be tested on unsupported versions, and 8.3
>>>> has been out over a year now.
>>>>
>>>> However, I've added java@ in case they have any suggestions.
>>>>
>>>> Chris
>>>
>>> Hi, Chris,
>>>
>>> Thanks for the mail.
>>>
>>> The problem is, the target FreeBSD 8.2 system has been heavily hacked
(on both kernel and libc, as far as I know), and they have been doing
system test for months. If we (or say they) do the swtich, the porting of
the kernel part will be huge, and test results in the past months will be
wasted. So I suppose that is not the working solution for my case. :(
>>>
>>> BTW, I would appreciate if anyone can tell me why build java need java
support?
>>
>>
>> I don't know the internals of building Java, but with compilers it is
generally a chicken-and-egg-problem. How do you compile the compiler? The
compiler javac is written in Java, so you need java to build it.
>> But you can build a pkg of java on another machine and copy it.
>> Or it might work to use a ports tree of FreeBSD 8.2.
>> http://svnweb.freebsd.org/ports/tags/RELEASE_8_2_0/
>>
>> Didn't try, buy might be worth a try.
>>
>> Ronald.
>
>
> I have tried to use the old port but still failed after being good for a
while. What I got are vast quantities of errors like this:
>
> ../../../src/share/classes/java/lang/reflect/Field.java:1028: cannot find
symbol
> private transient Map, Annotation>
declaredAnnotations;
>   ^
>   symbol:   class Annotation
>   location: class Field
> ../../../src/share/classes/java/lang/reflect/Field.java:1028: cannot find
symbol
> private transient Map, Annotation>
declaredAnnotations;
>^
>   symbol:   class Annotation
>   location: class Field
> ../../../src/share/classes/java/lang/reflect/Field.java:1030: cannot find
symbol
> private synchronized  Map, Annotation>
declaredAnnotations() {
>   ^
>   symbol:   class Annotation
>   location: class Field
> ../../../src/share/classes/java/lang/reflect/Field.java:1030: cannot find
symbol
> private synchronized  Map, Annotation>
declaredAnnotations() {
>^
>   symbol:   class Annotation
>   location: class Field
>
> I wanted to change another version of JVM to test the build process, but
this (/usr/local/diablo-jdk1.6.0/bin/java) seems the only one I can get in
the old port tree... I tried to build openjdk6 first (then I may try use
this JVM1.6 to build my 1.7 version if possible), but got familiar error
during java code compilation, which told me something like 'cannot find
class'.
>
> Why not people just write Java compiler in C... :(
>
> Or shall I test to build the java-part of openjdk7 on another host (maybe
any computer with openjdk1.7 installed) ? Though I still don't know how to
do that.

Ports-mgmt/portdowngrade has a -r option, which will recursively allow you
to install a port + its dependencies at a lower version.  Try that on it
perhaps?

Chris
___
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: fetch: expansion of correct source location in MASTER_SITES fails

[Chris Rees]

On 1 Jun 2013 15:12, "Jimmy Kelley"  wrote:
>
> On Sat, Jun 01, 2013 at 02:47:18PM +0200, O. Hartmann wrote:
> > On Sat, 01 Jun 2013 11:48:37 +
> > Steve Wills  wrote:
> >
> > > On 06/01/13 11:17, O. Hartmann wrote:
> > > >
> > > > I'm preparing a port and I fail downloading the sources, although
> > > > the base URL and the target tar ball are expanded correctly. But
> > > > the fetch process then complains with this:
> > > >
> > > > [...]
> > > > ===>   pocl-0.8.0 depends on file: /usr/local/sbin/pkg - found
> > > > => pocl-0.8rc1.tar.gz doesn't seem to exist
> > > > in /usr/ports/distfiles/. => Attempting to fetch
> > > > http://sourceforge.net/projects/pocl/files/pocl-0.8rc1.tar.gz fetch:
> > > > http://sourceforge.net/projects/pocl/files/pocl-0.8rc1.tar.gz: Moved
> > > > Temporarily
> > > >
> > > > If one the takes the error line named
> > > >
> > > > fetch http://sourceforge.net/projects/pocl/files/pocl-0.8rc1.tar.gz
> > > >
> > > > and issue it directly on the console, surprisingly the the fetch
> > > > works! This is weird.
> > > >
> > > > What is wrong here? Is this a bug in fetch?
> > >
> > > Nothing is wrong here. The "=> Attempting..." line is not trying to
> > > tell you what command it is running, but rather what it is doing.
> > > This result is perfectly normal due to the default args that ports
> > > pass to fetch. See bsd.port.mk:
> > >
> > >2214 FETCH_ARGS?=-AFpr
> > >
> > > The fetch man page will explain these further.
> > >
> > > For Sourceforge, there is a "SF" macro in bsd.sites.mk which you
> > > should use so that users will try the various mirrors. Many ports use
> > > this, so there are many examples to follow.
> > >
> > > Steve
> >
> > Thank you for clearify this.
> >
> > Even if I use the SF macro and set FETCH_ARGS= to en ampty string (I
> > suppose this will result in a "plain" fetch command without options)
> > the result is as described intially.
> >
> > Applying the -v option to fetch then shows what happens and everything
> > looks fine to me so far - except that the Makefile-Port-Fetch doesn't
> > work. This is strange!
>
> The SF macro used with nothing else expects the project on Sourceforge to
be
> layed out with subdirectories corresponding to the PORTVERSION, which
then would
> contain the file to be downloaded.
>
> If you use SF/${PORTNAME} for MASTER_SITES, it will fetch the file
> ${PORTNAME}-${PORTVERSION}.tar.gz from the top-level download directory.
>
>
> The -A fetch option for ports is something you do not want to ignore:
always
> go straight to a file location, and don't trust something telling you that
> it has "moved"...

Ignoring redirects makes things more reliable because it forces one to get
a real location, but with checksums it's not really a security problem.

Chris
___
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: ruby 1.9 upgrade and puppet

[Chris Rees]

On 31 May 2013 14:27, Steve Wills  wrote:
>> Moving to ruby 1.9 by following the instructions in UPDATING breaks
>> puppet.
>>
>> When updating with portmaster, at install time it says 'could not load
>> facter; cannot install' and exits. I had to manually run 'gem install
>> facter', then puppet installed.
>
> It's better to install via the port so that the package management knows
> it's there. This could be causing the later problems.
>
>> However, 'service puppetmaster status'
>> was reporting puppet as not running even though it was, so I had to kill
>> the running process before 'service puppetmaster start'. I assume this
>> is related to $command_interpreter in the rc script being changed from
>> ruby18 to ruby19? Although, /usr/local/bin/ruby and
>> /usr/local/bin/ruby19 are identical, can't the script use plain ruby
>> instead of ruby19?
>>
>
> It would probably be best to kill puppet before the upgrade.

This is definitely the problem here.  I'm afraid you'll have to
manually kill it here, since the old rc script has been deinstalled.
You'll only have to do it this once.

Chris
___
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: JVM panic when build openjdk7 on private FreeBSD 8.2

[Chris Rees]

On 29 May 2013 09:28, Peter Xu  wrote:
> Hi, all,
>
> I got strange issue when trying to build opendjk7 using ports utility on a
> private-built FreeBSD 8.2 system. Here is the output of make:
>


I'm going to suggest that you upgrade to FreeBSD 8.3-- it's not a big
jump, so it shouldn't break anything.

Unfortunately ports can't be tested on unsupported versions, and 8.3
has been out over a year now.

However, I've added java@ in case they have any suggestions.

Chris
___
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: The vim port needs a refresh

[Chris Rees]

On 28 May 2013 06:08, "Jeremy Messenger"  wrote:
>
> On Sat, May 25, 2013 at 3:50 AM, Chris Rees  wrote:
> > On 24 May 2013 22:23, Kenta Suzumoto  wrote:
> >>
> >> Hello all. The editors/vim port is currently a mess and needs some
changes.
> >>
> >> - It fetches almost 700 patches from what seems like a dial-up
connection in AUSTRALIA.
> >>
> >> You might as well be downloading a 1080p movie from a rock in the
north pole, because that's about how fast it is.
> >> This can be very easily avoided by putting all the patches into a
single tarball and hosting it anywhere decent. I've
> >> seen someone in ##freebsd on freenode handing out a tarball with all
the patches many times, and everyone asks
> >> "why isn't this the default? why is some random guy giving me
distfiles?" etc. Seems like a no-brainer.
> >>
> >> - By default, it builds lots of gui stuff that certainly almost no one
wants
> >>
> >> It almost seems like the vim-lite port should be renamed vim and the
vim port should be renamed gvim. I had to
> >> google to come up with this solution, because I can't even disable
that stuff in "make config" (another problem!)
> >>
> >> .if ${.CURDIR}=="/usr/ports/editors/vim"
> >> WITH_VIM_OPTIONS=yes
> >> WITHOUT_X11=yes
> >> .endif
> >>
> >> People shouldn't have to find this hack to be able to install vim
normally (and no, telling them to use vim-lite isn't normal).
> >> I'm surprised that none of these changes have been made yet. I've
heard it's "because the maintainer won't listen to reason"
> >> but I have no way to know if that's the case or not. I also heard bapt@had 
> >> an optionsNG patch that he wouldn't
> >> integrate into the port for some reason. Please, let's get this stuff
fixed once and for all. None of it requires a large amount
> >> of work on anyone's part.
> >
> > I'm very sad to talk of a fellow developer like this, but I'm afraid
> > the maintainer of vim is a contrarian who thinks he knows better than
> > everyone else on the matter.
> >
> > For years, people have been begging him to get over his fear of
> > OPTIONS, and he sits in the way of progress against almost everyone's
> > wishes.
>
> FYI, the OPTIONS is not required to have. I agree with him pretty much
> everything about the OPTIONS. I have refused to add OPTIONS in any of
> my ports before I gave up a lot of them long time ago. All of his
> thought of OPTIONS are very valid. The OPTIONS still has bugs.
>
> BTW: I always have BATCH=yes in my make.conf, because I hate OPTIONS a
lot.

Putting BATCH=yes in your environment is entirely up to you, but forcing
every user of the ports tree to learn a new way of dealing with certain
ports because "They're mine and they're special" is absolutely wrong.

If you don't like OPTIONS, fix them, but please don't labour under the
misapprehension that users are happy to have an inconsistent ports tree and
unpredictable ports tree on the whim of a few maverick developers.

Chris
___
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: Why does Samba requires 777 permissions on /tmp

[Chris Rees]

On 27 May 2013 20:45, "sindrome"  wrote:
>
> Hi Guys,
>
> I just got home from being out of town and the problem still persists even
> after I removed . from my path.
>
> echo $PATH
>
/bin:/usr/lib:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/home/sindrome/.gnupg:/home/sindrome/bin:/home/sindrome/docs:/home/sindrome/docs/info:/home/sindrome/docs/config:/sbin:/bin:/etc:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:

Remove the trailing : too?

Chris

> Here's what I get when I portupgrade an outdated port.
>
>
> /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning:
> Insecure world writable dir /tmp/ in PATH, mode 041777
> /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:1170: warning:
> Insecure world writable dir /tmp/ in PATH, mode 041777
> /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgmisc.rb:108: warning:
> Insecure world writable dir /tmp/ in PATH, mode 041777
> /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning:
> Insecure world writable dir /tmp/ in PATH, mode 041777
>
>
>
> On Mon, May 20, 2013 at 4:58 PM, Simon Wright 
wrote:
>
> > On 20/05/2013 15:38, Bob Eager wrote:
> >
> >> On Mon, 20 May 2013 08:03:09 -0500
> >> sindrome  wrote:
> >>
> >> What I think is happening is that portupgrade is building and running
> >> shell scripts in /tmp. It's running them with (in ruby):
> >>
> >>system('/tmp/script') [roughly]
> >>
> >> The ruby runtime is checking the *path-to-the-command* and THAT is what
> >> it's complaining about.
> >>
> >> Try setting PKG_TMPDIR (in pkgtools.conf) to some suitable non world
> >> writable temporary directory.
> >>
> >> I have an older ports tree on this machine or I'd try it myself. I had
> >> to download the latest sources to check all this,
> >>
> >
> > Trying to summarise what I've tested here with the results.
> >
> > My PKG_TMPDIR and TMPDIR are set to /var/tmp:
> >
> > pkgtools.conf:
> >
> >   ENV['TMPDIR'] ||= '/var/tmp'
> >   ENV['PKG_TMPDIR'] ||= '/var/tmp'
> >   ENV['PORTSDIR'] ||= '/usr/ports'
> >   ENV['PACKAGES'] ||= ENV['PORTSDIR'] + '/packages'
> >
> > from /usr/local/etc/sudoers:
> > # Uncomment if needed to preserve environmental variables related to the
> > # FreeBSD pkg_* utilities and fetch.
> > Defaultsenv_keep += "PKG_PATH PKG_DBDIR PKG_TMPDIR TMPDIR
> > PACKAGEROOT PACKAGESITE PKGDIR FTP_PASSIVE_MODE"
> >
> > [simon@vmserver04 ~]$ ls -ld /var/tmp
> > drwxrwxr-t  9 root  wheel  33280 May 20 23:02 /var/tmp/
> >
> > Note: /var/tmp is not world writeable
> >
> > [simon@vmserver04 ~]$ echo $PATH
> > /sbin:/bin:/usr/sbin:/usr/bin:**/usr/games:/usr/local/sbin:/**
> > usr/local/bin:/usr/X11R6/bin:/**usr/local/scripts:
> >
> > root@vmserver04:/root # echo $PATH
> > /sbin:/bin:/usr/sbin:/usr/bin:**/usr/games:/usr/local/sbin:/**
> > usr/local/bin:/root/bin
> >
> > I run portupgrade via sudo but both $PATH's show no /tmp or .
> >
> > [simon@vmserver04 ~]$ ruby -v
> > ruby 1.8.7 (2012-10-12 patchlevel 371) [amd64-freebsd9]
> >
> > portupgrade-2.4.10.5_1,2 FreeBSD ports/packages administration and
> > management tool s
> >
> > Other (not likely) relevant stuff:
> > - I have /usr/ports mounted rw with NFS
> > - I have the packages directory mounted rw with NFS and amd then
redefine
> > $PACKAGES to point to the mount point
> > This has been working for several years with no issues
> >
> > [simon@vmserver04 ~]$ sudo portupgrade -v portupgrade*
> > --->  Reading default options: -v -D -l /var/tmp/portupgrade.results_
> > 20130520-22:**56:25 -L /var/tmp/portupgrade/%s::%s.**log
> > --->  Session started at: Mon, 20 May 2013 22:56:26 +0200
> > ** None has been installed or upgraded.
> > --->  Saving the results to '/var/tmp/portupgrade.results_20130520-22**
> > :56:25'
> > /usr/local/lib/ruby/site_ruby/**1.8/pkgtools/pkgtools.rb:483: warning:
> > Insecure world writable dir /tmp/ in PATH, mode 041777
> >
> > Still the complaint about /tmp/
> >
> > [simon@vmserver04 ~]$ sudo chmod 1775 /tmp
> >
> > [simon@vmserver04 ~]$ ls -ld /tmp
> > drwxrwxr-t  9 root  wheel  1024 May 20 23:16 /tmp/
> >
> > [simon@vmserver04 ~]$ sudo portupgrade -v portupgrade*
> > --->  Reading default options: -v -D -l /var/tmp/portupgrade.results_
> > 20130520-23:**16:07 -L /var/tmp/portupgrade/%s::%s.**log
> > --->  Session started at: Mon, 20 May 2013 23:16:07 +0200
> > ** None has been installed or upgraded.
> > --->  Saving the results to '/var/tmp
> > /portupgrade.results_20130520-23:16:07'
> > --->  Session ended at: Mon, 20 May 2013 23:16:08 +0200 (consumed
00:00:00)
> >
> > No more complaint.
> >
> > I can't read the portupgrade code well enough to see what it's doing
with
> > the script, but if Bob is right that Ruby is running the portupgrade
> > commands from /tmp then the error is within the checks in Ruby which is
> > saying the 777 permission on /tmp is not acceptable, 775 *is*
acceptable.
> > Which is strange since surely then everyone with 777 permissions on /tmp
> > would be seeing this message? Does th

Re: textproc/libwps install fail

[Chris Rees]

On 26 May 2013 20:13, Beeblebrox  wrote:
> port builds but fails to install with
>
> ===>  Checking if textproc/libwps already installed
> make: don't know how to make do-config. Stop
>
> make: stopped in /asp/obj/asp/git/ports/textproc/libwps/work/libwps-0.2.8
> *** Error code 2
>

It's bad enough that you're spamming this list despite others asking
you to stop, but you haven't even read my reply to one of your earlier
emails.

Please learn to fix these things and be helpful or stick to releases.

Chris
___
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: graphics/graphviz "missing separator" at install

[Chris Rees]

On 26 May 2013 19:57, "Beeblebrox"  wrote:
>
> port builds but when trying to "make install", fails with
> ===>  Checking if graphics/graphviz already installed
> /asp/git/ports/graphics/graphviz/Makefile:91: *** missing separator.
 Stop.
> *** Error code 2
>
> line 91 is: include 
>
> Completely unrelated, poudriere run fails to build with message:
> gmake[4]: Entering directory
> `/wrkdirs/usr/ports/graphics/graphviz/work/graphviz-2.30.1/cmd/dot'
>  /bin/mkdir -p '/usr/local/bin'
>   /bin/sh /usr/local/bin/libtool   --mode=install install  -s -o root -g
> wheel -m 555 dot dot_builtins '/usr/local/bin'
> libtool: install: install -o root -g wheel -m 555 -s .libs/dot
> /usr/local/bin/dot
> libtool: install: install -o root -g wheel -m 555 -s .libs/dot_builtins
> /usr/local/bin/dot_builtins
> gmake  install-exec-hook
> gmake[5]: Entering directory
> `/wrkdirs/usr/ports/graphics/graphviz/work/graphviz-2.30.1/cmd/dot'
> (cd /usr/local/bin; if test -x dot; then for i in neato twopi fdp circo
> osage patchwork sfdp; do rm -f $i; ln -s dot $i; done; fi;)
> if test "x" = "x"; then if test -x /usr/local/bin/dot; then if test -x
> /sbin/ldconfig; then /sbin/ldconfig 2>/dev/null; fi; /usr/local/bin/dot
-c;
> else /usr/local/bin/dot_static -c; fi; fi
> >> Killing runaway build
>

Do you understand that this isn't helpful?  We find out pretty quickly if
ports fail on head now pointyhat is back, so all you're making here is
noise.

If you want to help, have a go at fixing the ports; as a hint, "missing
separator" is almost certainly from the bmake switchover.  Try
USE_GMAKE=yes.

Chris
___
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: The vim port needs a refresh

[Chris Rees]

On 25 May 2013 11:54, Niclas Zeising  wrote:
> On 05/25/13 10:50, Chris Rees wrote:
>>
>> Alternatively, perhaps we need an editors/vim-options port
>
> Just for the record, editors/vim was (and shells/bash) was converted to
> optionsNG not too long ago.

Ah, that's at least some good news.  I notice that it was on yet
another maintainer timeout, so that criticism stands.

It appears that David is no longer interested.

Chris
___
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: The vim port needs a refresh

[Chris Rees]

On 24 May 2013 22:23, Kenta Suzumoto  wrote:
>
> Hello all. The editors/vim port is currently a mess and needs some changes.
>
> - It fetches almost 700 patches from what seems like a dial-up connection in 
> AUSTRALIA.
>
> You might as well be downloading a 1080p movie from a rock in the north pole, 
> because that's about how fast it is.
> This can be very easily avoided by putting all the patches into a single 
> tarball and hosting it anywhere decent. I've
> seen someone in ##freebsd on freenode handing out a tarball with all the 
> patches many times, and everyone asks
> "why isn't this the default? why is some random guy giving me distfiles?" 
> etc. Seems like a no-brainer.
>
> - By default, it builds lots of gui stuff that certainly almost no one wants
>
> It almost seems like the vim-lite port should be renamed vim and the vim port 
> should be renamed gvim. I had to
> google to come up with this solution, because I can't even disable that stuff 
> in "make config" (another problem!)
>
> .if ${.CURDIR}=="/usr/ports/editors/vim"
> WITH_VIM_OPTIONS=yes
> WITHOUT_X11=yes
> .endif
>
> People shouldn't have to find this hack to be able to install vim normally 
> (and no, telling them to use vim-lite isn't normal).
> I'm surprised that none of these changes have been made yet. I've heard it's 
> "because the maintainer won't listen to reason"
> but I have no way to know if that's the case or not. I also heard bapt@ had 
> an optionsNG patch that he wouldn't
> integrate into the port for some reason. Please, let's get this stuff fixed 
> once and for all. None of it requires a large amount
> of work on anyone's part.

I'm very sad to talk of a fellow developer like this, but I'm afraid
the maintainer of vim is a contrarian who thinks he knows better than
everyone else on the matter.

For years, people have been begging him to get over his fear of
OPTIONS, and he sits in the way of progress against almost everyone's
wishes.

He has also impeded progress on the bash port, resulting in the
ridiculous situation where we now have two bash ports, where one will
do.  For historical reasons, people seem reluctant to confront him
about this, and he ignores all attempts to reason about it.

It's far beyond time to remove David O'Brien from MAINTAINER lines--
he doesn't do the job properly anyway; several PRs he's timed out on
for his ports:

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/177597

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/174965

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/175447

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/178462

Last time I timed him out on a PR I was subjected to a tirade from
him, with questionable justification, but I may process these too when
I have time.

Alternatively, perhaps we need an editors/vim-options port

Chris
___
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: error: possibly undefined macro: AC_MSG_WARN

[Chris Rees]

On 24 May 2013 18:17, "O. Hartmann"  wrote:
>
> I work on a port tha comes with a configure.ac file which contains a m4
> macro AC_MSG_WARN.
>
> I have set this in the port's toplevel Makefile to ensure the correct
> build of the software:
>
> USES=   pkgconfig
> USE_AUTOTOOLS=  aclocal libtoolize libltdl autoheader autoconf
> automake
>
> There is a well known issue with this error message regarding pkg-config
> and libtool (look at https://github.com/Pulse-Eight/libcec/issues/15).
>
> Since my configured toplevel makefile indicates the usage of both,
> libtool and pkg-config, the still persistent error suggests that this
> couldn't be all.
>
> The port's sources has compiled well previous to the introduction of
> those AC_MSG_WARN([...]) macros and they are the only add-ons to the
> configure.ac.
>
> How can this be fixed?

Providing the files would help :)

Can't you just patch those lines out?

Chris
___
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: Proposal: do not show up the dialog(1) by default?

[Chris Rees]

On 23 May 2013 16:38, "Freddie Cash"  wrote:
>
> On Thu, May 23, 2013 at 8:36 AM, Chris Rees  wrote:
>>
>> Please read the docs before stating things that are incorrect.
>
>
> I've read the docs, I've installed ports, I've mangled my make.conf to
make it work in The New World Order.
>>
>> We can still set things globally, and it's not a hack.
>
> Compared to the simplicity of how things were before, it's a hack.

Don't confuse familiarity with simplicity.  Just because you've had to cope
with a small change doesn't mean it's a bad one.

Chris
___
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: Proposal: do not show up the dialog(1) by default?

[Chris Rees]

On 23 May 2013 16:32, "Freddie Cash"  wrote:
>
> On Thu, May 23, 2013 at 6:58 AM, Lars Engels  wrote:
>
> > On Thu, May 23, 2013 at 07:45:42AM +0200, Baptiste Daroussin wrote:
> > > hi,
> > >
> > > A lot of people seems to be complaining about the configuration dialog
> > popping
> > > up all the time.
> > >
> > > What if we change the default behaviour to not pop up the dialog each
> > time there
> > > is a changed option but only when the user explicitly type make
config?
> > >
> > > Just a proposal, please give your opinion.
> > >
> > > Of course make config-recursive behaviour won't change.
> > >
> > > regards,
> > > Bapt
> >
> > I am strongly against it. Firstly, it's against POLA, secondly, while it
> > hides complexity of the ports system it also hides its biggest
> > advantage.
> > You'll never know which knobs the ports you want to build offer and new
> > users will never find out how to build an Apache web server with PHP
> > support.
> >
> > My proposal get rid of the nagging NLS and DOCS window, ask the user
> > initially if they want NLS and DOCS and enable/disable it globally.
> > Second, encourage the use of portmaster to install new ports, which
> > recursively displays the OPTIONS dialog and does this much faster than
> > make config-recursive.
> > That way you can set/unset all OPTIONS, go to bed and don't find an
> > unanswered dialog in the next morning.
> >
>
> I agree.  The dialog needs to appear if there are no saved options for the
> port (thus saving the options).  And it needs to appear if the list of
> options has changed or if the defaults have changed from what's saved in
> /var/db/ports/.
>
> If the defaults are the same as what's saved in /var/db/ports/ then the
> options window does not need to appear.
>
> IOW, the way the ports tree worked before we lost the ability to set
things
> globally in /etc/make.conf (although it appears a convoluted hack has been
> added to make this work).

Please read the docs before stating things that are incorrect.

We can still set things globally, and it's not a hack.

Chris
___
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: Proposal: do not show up the dialog(1) by default?

[Chris Rees]

On 23 May 2013 06:55, "Alex Dupre"  wrote:
>
> Baptiste Daroussin ha scritto:
>
>> A lot of people seems to be complaining about the configuration dialog
popping
>> up all the time.
>
>
> Probably because now every ports that list DOCS/EXAMPLES/NLS pop up the
dialog?
>
>
>> What if we change the default behaviour to not pop up the dialog each
time there
>> is a changed option but only when the user explicitly type make config?
>>
>> Just a proposal, please give your opinion.
>
>
> I find such behavior very useful, I find annoying the above behavior. If
the dialog will not pop-up if the only options are the global ones it'd be
much better, IMO.

The correct solution to this is to not add those to DEFINE.

Chris
___
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: Why does Samba requires 777 permissions on /tmp

[Chris Rees]

Please let us know if it's still a problem and we can narrow it down
further. :)

Chris
On 20 May 2013 20:20, "sindrome"  wrote:

> Apologies Chris.  I removed it but am out of town so will have to test
> next week.  I appreciate all your help.  I'll let you know if that makes it
> go away.
>
>
> On Mon, May 20, 2013 at 1:04 PM, Chris Rees  wrote:
>
>> You are not 'sure'.
>>
>> Please do not solicit help and claim that you know better-- I told you
>> hours ago to remove . from your path.
>>
>> Chris
>>
>> On 20 May 2013 17:49, sindrome  wrote:
>> > Fair enough but that's not the root of this problem I'm sure
>> >
>> >
>> > On Mon, May 20, 2013 at 11:47 AM, Torfinn Ingolfsen > >wrote:
>> >
>> >> On Mon, May 20, 2013 at 6:45 PM, sindrome  wrote:
>> >> > Clearly I'm not the only one with this problem.  Something is
>> amending
>> >> onto
>> >> > the PATH and I'd like to get to the bottom of this.  I'm sure it will
>> >> help a
>> >> > lot of people.
>> >>
>> >> Well, start by taking the current directory ('.') out of your PATH.
>> >> (It is bad, for a number of reasons).
>> >>
>> >> HTH
>> >> --
>> >> Regards,
>> >> Torfinn Ingolfsen
>> >> ___
>> >> 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: Browsers...

[Chris Rees]

On 20 May 2013 19:11, David Wolfskill  wrote:
> On Mon, May 20, 2013 at 07:07:32PM +0100, Chris Rees wrote:
>> ...
>> Do you have an NFS mounted home directory?  I've discovered that
>> Firefox doesn't like that, perhaps something to do with sqlite
>> locking.
>> 
>
> It (firefox-21.0_1,1 with an NFS-resident ~) worked OK on my home
> desktop machine, once I ensured that I (vs.  root) owned the
> ~david/.cache directory.  And on that machine, home directories reside
> on a ReadyNAS.

You're one of those crazy head/ people like me, aren't you?  Perhaps
this is a regression-- I really should have filed a PR about it to be
honest...

Chris
___
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: Browsers...

[Chris Rees]

On 20 May 2013 19:05, Jeffrey Bouquet  wrote:
> Firefox 21 would not run (segfaulted).  I pkg_added Firefox 20, and it works, 
> but I lost all the sites it for years had open at the start, they are 
> nowhere... maybe I'll find them in a backup later.
>
> ...
> Midori would not run, but "midori -d -p'  seems to work.  (The latest one 
> will not build, but
> that is unique to here probably...)
> 
>
> This all prompted by one site refusing to proceed to the next clicked action 
> in both
> opera and seamonkey, which otherwise work fine...
>
> Meant just as a FYI for anyone facing a similar situation, not needing an 
> answer to
> this post...

Do you have an NFS mounted home directory?  I've discovered that
Firefox doesn't like that, perhaps something to do with sqlite
locking.

You can work around by moving your .mozilla folder somewhere local and
symlinking it.

Even if you're not on NFS, have you tried moving your .mozilla away?

Chris
___
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: Why does Samba requires 777 permissions on /tmp

[Chris Rees]

You are not 'sure'.

Please do not solicit help and claim that you know better-- I told you
hours ago to remove . from your path.

Chris

On 20 May 2013 17:49, sindrome  wrote:
> Fair enough but that's not the root of this problem I'm sure
>
>
> On Mon, May 20, 2013 at 11:47 AM, Torfinn Ingolfsen wrote:
>
>> On Mon, May 20, 2013 at 6:45 PM, sindrome  wrote:
>> > Clearly I'm not the only one with this problem.  Something is amending
>> onto
>> > the PATH and I'd like to get to the bottom of this.  I'm sure it will
>> help a
>> > lot of people.
>>
>> Well, start by taking the current directory ('.') out of your PATH.
>> (It is bad, for a number of reasons).
>>
>> HTH
>> --
>> Regards,
>> Torfinn Ingolfsen
>> ___
>> 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"