Beloved porters,
following some discussions related to the rights and duties of ports
maintainers it became obvious that our handbook was not specific enough
on the matter. Hence an update was committed that aims at clarifying
the notion of maintainership and all porters are invited to peruse the
Hi!
Log see http://people.freebsd.org/~pi/misc/build-libgcrypt.txt
Hmm. I'm a bit confused now. I checked the newly linked libgcrypt.so.20
(located in src/.libs) and it seems to have all of the missing symbols in
its symbol table, but all are undefined. I ran nm -D on the file and:
The
Hi!
Log see http://people.freebsd.org/~pi/misc/build-libgcrypt.txt
Hmm. I'm a bit confused now. I checked the newly linked libgcrypt.so.20
(located in src/.libs) and it seems to have all of the missing symbols in
its symbol table, but all are undefined. I ran nm -D on the file and:
Hello, Tijl,
Someone prepared a patch to bring security/libgcrypt from 1.5.3 to 1.6.1, see:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191256
I prepared a diff which builds and tests, see
http://people.freebsd.org/~pi/misc/libgcrypt.svndiff
and
On Sun, 6 Jul 2014 13:16:43 +0200 Kurt Jaeger wrote:
Hello, Tijl,
Someone prepared a patch to bring security/libgcrypt from 1.5.3 to 1.6.1, see:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191256
I prepared a diff which builds and tests, see
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a
Dnia 2014-07-05, o godz. 12:04:57
Mikolaj Golub troc...@freebsd.org napisał(a):
Hi,
It looks like COPYTREE_BIN/COPYTREE_SHARE does not work as it is
documented in bsd.port.mk:
# Example use:
# cd ${WRKSRC}/doc ${COPYTREE_SHARE} . ${DOCSDIR}
! -name *.bak #
#
Hi,
On Sun, 6 Jul 2014, Pawel Pekala wrote:
Dnia 2014-07-05, o godz. 12:04:57
Mikolaj Golub troc...@freebsd.org napisał(a):
Hi,
It looks like COPYTREE_BIN/COPYTREE_SHARE does not work as it is
documented in bsd.port.mk:
# Example use:
# cd ${WRKSRC}/doc
These ports already have been staged and are very simple script only
ports which are ready to be committed.
191660 qjail bug fix
191502 qchroot new port
190259 ppars updated
186269 can be closed
___
freebsd-ports@freebsd.org mailing
Hi Melvyn,
On 2014-07-06 16:34 +0200, Melvyn Sopacua mel...@magemana.nl wrote:
Hi,
On Sun, 6 Jul 2014, Pawel Pekala wrote:
Dnia 2014-07-05, o godz. 12:04:57
Mikolaj Golub troc...@freebsd.org napisał(a):
Hi,
It looks like COPYTREE_BIN/COPYTREE_SHARE does not work as it is
documented in
On Sun, Jul 6, 2014 at 12:59 AM, Frederic Culot cu...@freebsd.org wrote:
Beloved porters,
following some discussions related to the rights and duties of ports
maintainers it became obvious that our handbook was not specific enough
on the matter. Hence an update was committed that aims at
Hi Pawel,
On Sun, 6 Jul 2014, Pawel Pekala wrote:
Hi Melvyn,
On 2014-07-06 16:34 +0200, Melvyn Sopacua mel...@magemana.nl wrote:
+ /usr/bin/find -d . -not -name '*.bak'
This has always been broken for globs as far as I know, which is why
cleaning up in post-patch is done.
Little hackish,
Hi!
It needs USES=libtool, but does it *need* libtool:oldver or libtool:keepla ?
Do I need to bump PORTREVISION on the dependencies ?
[...]
You can deal with the amd64 versus x86_64 problem by adding this to the
Makefile:
On Sun, 6 Jul 2014, Kevin Oberman wrote:
On Sun, Jul 6, 2014 at 12:59 AM, Frederic Culot cu...@freebsd.org wrote:
Beloved porters,
following some discussions related to the rights and duties of ports
maintainers it became obvious that our handbook was not specific enough
on the matter.
On Sun, 6 Jul 2014 19:48:59 +0200 Kurt Jaeger wrote:
I prepared a new diff, see
http://people.freebsd.org/~pi/misc/libgcrypt.svndiff-v2
Can you have a look at it, before I mess up the whole tree 8-} ?
net/samba4/Makefile: PORTREVISION messed up
net/samba41/Makefile: PORTREVISION messed up
On Sun, 6 Jul 2014 20:52:03 +0200 Tijl Coosemans wrote:
On Sun, 6 Jul 2014 19:48:59 +0200 Kurt Jaeger wrote:
I prepared a new diff, see
http://people.freebsd.org/~pi/misc/libgcrypt.svndiff-v2
Can you have a look at it, before I mess up the whole tree 8-} ?
net/samba4/Makefile:
Hi!
On Sun, 6 Jul 2014 20:52:03 +0200 Tijl Coosemans wrote:
On Sun, 6 Jul 2014 19:48:59 +0200 Kurt Jaeger wrote:
I prepared a new diff, see
http://people.freebsd.org/~pi/misc/libgcrypt.svndiff-v2
Can you have a look at it, before I mess up the whole tree 8-} ?
On Sun, 6 Jul 2014 21:27:20 +0200 Kurt Jaeger wrote:
On Sun, 6 Jul 2014 20:52:03 +0200 Tijl Coosemans wrote:
On Sun, 6 Jul 2014 19:48:59 +0200 Kurt Jaeger wrote:
I prepared a new diff, see
http://people.freebsd.org/~pi/misc/libgcrypt.svndiff-v2
Can you have a look at it, before I mess up
Hi!
Have you tried to compile some of the ports that depend on libgcrypt
to see if nothing breaks?
No, due to number of ports involved (104), list at
http://people.freebsd.org/~pi/misc/libgcrypt-related-ports
[...]
For this we probably need some exp-run ?
It's safer to do an
Hello,
I'm coming accross a few ports that are in the tree as we speak, that do
not actually install correctly with Python 3.x but aren't marked as 2.7
only.
There seems to be 2 cases:
1. incompatibility in setup.py or related, thus failing in configure
2. incompatibility in the code itself,
Beautiful Soup 3.x is Python 2.x only. From the website:
Beautiful Soup 3 works only under Python 2.x.
http://www.crummy.com/software/BeautifulSoup/
On Sun, Jul 6, 2014 at 3:56 PM, Melvyn Sopacua mel...@magemana.nl wrote:
Hello,
I'm coming accross a few ports that are in the tree as we speak,
On Sun, 6 Jul 2014, Robert Simmons wrote:
Beautiful Soup 3.x is Python 2.x only. From the website:
I know that.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191387#c3
The port doesn't:
http://svn.freebsd.org/ports/head/www/py-beautifulsoup32/Makefile
That was the point of the mail.
--
On 7/07/2014 7:52 AM, Melvyn Sopacua wrote:
On Sun, 6 Jul 2014, Robert Simmons wrote:
Beautiful Soup 3.x is Python 2.x only. From the website:
I know that.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191387#c3
The port doesn't:
On 2014-07-05 19:09, Bjoern A. Zeeb wrote:
Hi,
given ports@ ist listed as maintainer, you get the email. The Subject says
it. The world has moved on; in March I had a hard time arguing, in July I
just cannot anymore. We must switch to 2.4; whatever breaks needs fixing,
but somehow
Hi Kubilay!
On Mon, 7 Jul 2014, Kubilay Kocak wrote:
On 7/07/2014 7:52 AM, Melvyn Sopacua wrote:
Submit an issue with patch, I'll add maintainer_approval flag cc'ing
maintainer if you cant, just let me know the issue ID :)
Thought I submitted more already, but they're still in the queue and
On Mon, Jul 07, 2014 at 12:27:48AM +0200, olli hauer wrote:
On 2014-07-05 19:09, Bjoern A. Zeeb wrote:
Hi,
given ports@ ist listed as maintainer, you get the email. The Subject says
it. The world has moved on; in March I had a hard time arguing, in July I
just cannot anymore. We
On 7/07/2014 8:41 AM, Melvyn Sopacua wrote:
Hi Kubilay!
On Mon, 7 Jul 2014, Kubilay Kocak wrote:
On 7/07/2014 7:52 AM, Melvyn Sopacua wrote:
Submit an issue with patch, I'll add maintainer_approval flag cc'ing
maintainer if you cant, just let me know the issue ID :)
Thought I submitted
On 07/05/14 03:18, Mike Brown wrote:
Warren Block wrote:
The documentation team has a standing offer to either assist with markup
or accept content-only submissions and do the markup on them.
That's good to know. I was under the impression it had to be submitted as
DocBook XML. Thanks!
On 06/26/14 14:30, Baptiste Daroussin wrote:
On Thu, Jun 19, 2014 at 10:22:30AM -0700, Nathan Whitehorn wrote:
On 05/28/14 10:04, Baptiste Daroussin wrote:
On Wed, May 28, 2014 at 09:54:03AM -0700, Nathan Whitehorn wrote:
The following was in a deep and increasingly branched thread on the
29 matches
Mail list logo
