editors/komodo-edit native FreeBSD build (rather than Linux)

[Ben Woods]

The current port editors/komodo-edit uses a precompiled binary for Linux,
is out of date and has a license restricting distribution. However, it
could instead be compiled from source available on GitHub, and then it
would be available under the Mozilla Public License:
https://github.com/Komodo/KomodoEdit

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

Re: editors/komodo-edit native FreeBSD build (rather than Linux)

[Ben Woods]

(I accidentally sent that last email beforeI was finished)

Referring to the build instructions on GitHub:
cd komodo/mozilla
python build.py configure -k 9.10
python build.py distclean all

This will cause the build.py script to
- download a complete copy of the Mozilla Mercurial repository using wget
(908 Mb),
- using Mercurial revision FIREFOX_31_0_RELEASE make a clone of
TAG_MOZILLA_31,
- apply a series of patches to allow it to work with Komodo Edit,
- build the patched Firefox 31.0 source.


Then the build instructions build the main Komodo Edit source against these
binaries:
cd ..
export PATH=`pwd`/util/black:$PATH   # Komodo's "bk" build tool
bk configure -V 9.10.0-devel
bk build


Rather than follow these instructions, does anyone know a smarter way to
get the port to build the Firefox 31.0 source with their patch set, and
then build Komodo Edit using those binaries? It looks like USES=gecko may
be able to help, but I am new to it and not really sure how to apply it.

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com

On 4 January 2015 at 17:06, Ben Woods  wrote:
>
> The current port editors/komodo-edit uses a precompiled binary for Linux,
is out of date and has a license restricting distribution. However, it
could instead be compiled from source available on GitHub, and then it
would be available under the Mozilla Public License:
> https://github.com/Komodo/KomodoEdit
>
> --
> From: Benjamin Woods
> woods...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Combining GitHub and regular MASTER_SITES for multiple DISTFILES

[Ben Woods]

I am trying to create a new port, where the main source code should be
retrieved from GitHub, and a secondary piece of source code should be
retrieved from an FTP site.

The USE_GITHUB port magic does not work for the primary source code if the
MASTER_SITES and DISTFILES variables are also specified in the Makefile for
the secondary source code. The result is that only the secondary code is
downloaded and extracted. Using += for the MASTER_SITES and DISTFILES
assignment does not fix the issue.

Is there a way that these can be used together for this propose?

Regards,
Ben


-- 

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

Re: upgrading texlive broken due to cmake

[Ben Woods]

textproc/py-sphinx port depends on the devel/py-Jinja2 port... but the port
only requires py-Jinja >= 2.3.

Try adding this patch to your ports tree and then retry you build:

Index: textproc/py-sphinx/Makefile
===
--- textproc/py-sphinx/Makefile (revision 376204)
+++ textproc/py-sphinx/Makefile (working copy)
@@ -14,9 +14,9 @@

 LICENSE=   BSD2CLAUSE

-BUILD_DEPENDS=
${PYTHON_PKGNAMEPREFIX}Jinja2>=2.3:${PORTSDIR}/devel/py-Jinja2 \
+BUILD_DEPENDS=
${PYTHON_PKGNAMEPREFIX}Jinja2>=2.7:${PORTSDIR}/devel/py-Jinja2 \

${PYTHON_PKGNAMEPREFIX}docutils>=0.7:${PORTSDIR}/textproc/py-docutils
-RUN_DEPENDS=
${PYTHON_PKGNAMEPREFIX}Jinja2>=2.3:${PORTSDIR}/devel/py-Jinja2 \
+RUN_DEPENDS=
${PYTHON_PKGNAMEPREFIX}Jinja2>=2.7:${PORTSDIR}/devel/py-Jinja2 \

${PYTHON_PKGNAMEPREFIX}docutils>=0.7:${PORTSDIR}/textproc/py-docutils \

${PYTHON_PKGNAMEPREFIX}pygments>=1.2:${PORTSDIR}/textproc/py-pygments


--
From: Benjamin Woods
woods...@gmail.com

> > tex-kpathsea installed, but texlive-base didn't due to a failure to
> > build the cmake dependency:
> [...]
> > ===>  Building for py27-sphinx-1.2.3
> > /usr/local/bin/python2.7: No module named jinja2
>
> See how this is actually a failure to build the py-sphinx dependency.
> Does the port build if you try to build it individually?
___
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: Ports quarterly branches

[Ben Woods]

I also wonder how that works. For example, I presume there is an attempt to
ensure most of the ports a building successfully prior to the quarterly
branch?

A gnome3 dependency stopped building the other day, meaning the gnome3
metapackage was no longer available to install. Would be a bit harsh to
branch a quarterly branch at that point. If it did, can people then still
commit fixes and security updates to the quarterly branch, or is it frozen?

On Thursday, January 8, 2015, Michael Grünewald  wrote:

> Since one year or so, FreeBSD ports are branched quarterly to provide
> stable branches.
>
> Where can I read more on this topic?  How does it affect my work as
> a port maintainer?
>
> --
> Thanks!
> Michael
>
> ___
> 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
> "
>


-- 

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

Re: official amd64 pkg repo: need to rebuild paraview for png-1.6.16

[Ben Woods]

The port revision was bumped on Christmas Day for the png version update.
However new packages are not available as the paraview port fails to build.

It was marked as broken on 19th December:
http://www.freshports.org/science/paraview

On Thursday, January 8, 2015, Anton Shterenlikht  wrote:

> All packages installed/upgraded via the
> official pkg repo, i.e. /etc/pkg/FreeBSD.conf
>
> $ pkg info -xo paraview png
> paraview-4.1.0_6   science/paraview
> linux-c6-png-1.2.49_1  graphics/linux-c6-png
> png-1.6.16 graphics/png
> $ paraview
> Shared object "libpng15.so.15" not found, required by
> "libvtkIOExport-pv4.1.so.1"
> $
>
> Seems paraview should have been rebuilt for
> png-1.6.16. Some missing dependency maybe?
>
> Anton
> ___
> 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
> "
>


-- 

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

Re: Combining GitHub and regular MASTER_SITES for multiple DISTFILES

[Ben Woods]

> See ports-mgmt/poudriere Makefile.
>
> Use 'GH' in MASTER_SITES for the USE_GITHUB source:
>
> MASTER_SITES=   LOCAL/bdrewery/${PORTNAME}/ \
> http://mirror.shatow.net/freebsd/${PORTNAME}/ \
> GH
>
> You can use whatever order you wish.


Thanks Bryan - that worked great :)

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

Re: upgrading texlive broken due to cmake

[Ben Woods]

> Also, I seem to already have py27-Jinja2 2.7.3 installed.

If that is the case, my idea won't help. Not sure what next (some googling
shows similar issues resolved on Mac OS X by reinstalling Python, but I
don't think that will help with freebsd ports).

-- 

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

Re: do-install fails when files in .PLIST.mktmp are truncated

[Ben Woods]

First off, since this is your first attempt to update a port, welcome!
There may be a slight hurdle to get over to understanding port basics, but
once you get there it is quite rewarding.

This resource is priceless, read it and refer back to it often:
https://www.freebsd.org/doc/en/books/porters-handbook/book.html

Also, the great thing about ports is you can read all of the shell
scripts that are doing the work if you don't understand something (such as
copytree_share), by grepping through the files here:
/usr/ports/Mk/

Lastly, the mailing lists do not have the formatting features of the
forums, so no need for the [FILE][/FILE] stuff.

I would say the most obvious thing for your port is the need to update the
pkg-plist file which lists ever file your port will install on the system.
Easy way to test this with your updated port is to do the following:
# cd PORTDIR
# make clean
# make
# make makeplist

That will dump the new plist to the console standard output, but doesn't
actually update the pkg-plist for you (you have to do that by redirecting
the output to the file). But note, you need to follow the instructions of
the first line (delete the first line, and check the output of the rest of
the file looks reasonable). I would redirect the output to a new plist file
and compare the difference before overwriting the main plist file:
# make makeplist > pkg-plist.new
# diff -u pkg-plist pkg-plist.new

Good luck!


-- 

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

Re: do-install fails when files in .PLIST.mktmp are truncated

[Ben Woods]

Submit a bug report here:
bugs.freebsd.org/bugzilla/

Include devel/hadoop2 at the start of the bug title.

Then you need to attach a patch of the changes to the ports tree that will
update the port per your work.

The easiest way to generate the patch file to update is to ensure you
retrieved your ports tree using svn (Per
https://www.freebsd.org/doc/handbook/svn.html).

Then change devel/hadoop2 to match your needs, and run:
# cd /usr/ports
# svn diff devel/hadoop2 > /home/USERNAME/hadoop2.patch

Good luck!

On Friday, January 9, 2015, Freddy Andersen  wrote:

> Thank you ben! you have no idea how helpful the make and makeplist was for
> me :) the issues was not with my Makefile but rather that I did not
> understand what roll the pkg-plist had in the do-install process. I’m all
> good now and my updated hadoop2 builds and install …
>
> Now I just need to figure how I can get this sent to upstream after some
> testing on my end.
>
>
>
> On Jan 8, 2015, at 3:02 PM, Ben Woods  > wrote:
>
> First off, since this is your first attempt to update a port, welcome!
> There may be a slight hurdle to get over to understanding port basics, but
> once you get there it is quite rewarding.
>
> This resource is priceless, read it and refer back to it often:
> https://www.freebsd.org/doc/en/books/porters-handbook/book.html
>
> Also, the great thing about ports is you can read all of the shell
> scripts that are doing the work if you don't understand something (such as
> copytree_share), by grepping through the files here:
> /usr/ports/Mk/
>
> Lastly, the mailing lists do not have the formatting features of the
> forums, so no need for the [FILE][/FILE] stuff.
>
> I would say the most obvious thing for your port is the need to update the
> pkg-plist file which lists ever file your port will install on the system.
> Easy way to test this with your updated port is to do the following:
> # cd PORTDIR
> # make clean
> # make
> # make makeplist
>
> That will dump the new plist to the console standard output, but doesn't
> actually update the pkg-plist for you (you have to do that by redirecting
> the output to the file). But note, you need to follow the instructions of
> the first line (delete the first line, and check the output of the rest of
> the file looks reasonable). I would redirect the output to a new plist file
> and compare the difference before overwriting the main plist file:
> # make makeplist > pkg-plist.new
> # diff -u pkg-plist pkg-plist.new
>
> Good luck!
>
>
> --
>
> --
> From: Benjamin Woods
> woods...@gmail.com 
>
>
>

-- 

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

Re: do-install fails when files in .PLIST.mktmp are truncated

[Ben Woods]

Sorry, ensure you do a
# make clean

Before you do the
# svn diff



-- 

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

Re: games/wesnoth: How to cope with "invalid DSO for symbol `_ZN5boost6system15system_categoryEv'"

[Ben Woods]

What is the output of the following command on both computers (the one it
works on and the one it doesn't)?
# pkg info boost-libs
___
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: sysutils/bbcp: Anyone interesting in helping upgrade this port?

[Ben Woods]

>
> With the requirement for the NONE cipher in OpenSSH requiring a custom
> compile of the world or a custom compile of the openssh-portable port
>

Note that there are 2 open PRs on freebsd base to turn the NONE
cipher option on by default in the build process of ssh in freebsd base (as
was agreed in the freebsd current mailing list):
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163127
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163095


-- 

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

Re: updating alpine port to new version (as a maintainer)

[Ben Woods]

Good news - that means the port is now compiling fine, and the last thing
you need to do is fix the pkg-plist file to ensure it accurately reflects
all the files the port will install:
# cd PORTDIR
# make clean
# make
# make makeplist

That will dump the new plist to the console standard output, but doesn't
actually update the pkg-plist for you (you have to do that by redirecting
the output to the file). But note, you need to follow the instructions of
the first line (delete the first line, and check the output of the rest of
the file looks reasonable). I would redirect the output to a new plist file
and compare the difference before overwriting the main plist file:
# make makeplist > pkg-plist.new
# diff -u pkg-plist pkg-plist.new

Then you can make the necessary changes to the pkg-plist file and delete
the pkg-plist.new file.

On Sunday, January 18, 2015, Marco Beishuizen  wrote:

> On Sat, 17 Jan 2015, the wise Scot Hetzel wrote:
>
> Well, problems with the maildir patch seem to have dissappeared, but I'm
> not there yet. Alpine compiles, but the problems with the plist remain.
> I'll look further into the Makefile and see if I can solve this.
>
> The current error is:
>
> > Compressing man pages (compress-man)
> > Running Q/A tests (stage-qa)
> > Checking for pkg-plist issues (check-plist)
> ===> Parsing plist
> ===> Checking for items in STAGEDIR missing from pkg-plist
> Error: Orphaned: %%PORTDOCSDOCSDIR%%/tech-notes.txt
> ===> Checking for items in pkg-plist which are not in STAGEDIR
> Error: Missing: %%DOCSDIR%%/tech-notes/tech-notes.txt
> ===> Error: Plist issues found.
> *** Error code 1
>
> Regards,
> Marco
>
>

-- 

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

Re: Fail to kill children

[Ben Woods]

On face value, that is quite a shocking mailing list topic!


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

Re: Poudriere in a jail error

[Ben Woods]

That looks similar to this bug entry:
https://github.com/freebsd/poudriere/issues/216

Does that information help at all?

On Friday, January 30, 2015, Cassiano Peixoto 
wrote:

> Hi,
>
> I'm trying to run Poudriere inside a jail to build my packages but i'm
> having the following error:
>
> [00:00:00] >> Creating the reference jail... done
> [00:00:03] >> Mounting system devices for 10amd64-system
> [00:00:03] >> Mounting ports/packages/distfiles
> [00:00:03] >> Using packages from previously failed build
> [00:00:03] >> Mounting packages from:
> /poudriere/data/packages/10amd64-system
> [00:00:03] >> Mounting /var/db/ports from:
> /usr/local/etc/poudriere.d/options
> [00:00:03] >> Appending to make.conf:
> /usr/local/etc/poudriere.d/make.conf
> /etc/resolv.conf -> /poudriere/data/.m/10amd64-system/ref/etc/resolv.conf
> [00:00:03] >> Starting jail 10amd64-system
> jail: jail_set: Operation not permitted
> [00:00:03] >> Cleaning up
> [00:00:03] >> Umounting file systems
>
> Any idea what's going on?
>
> Thanks
> ___
> 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
> "
>


-- 

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

Re: FreeBSD Port: transmission-daemon-2.84_1

[Ben Woods]

For the record, I am running transmission-daemon 2.84_1 in a jail on
FreeBSD 10.1 amd64 with no issues.

I have the following lines in rc.conf:
transmission_enable="YES"
transmission_download_dir="/media/downloads"
transmission_flags="-a 127.0.0.*,192.168.1.*"

Regards,
Ben

On Friday, February 6, 2015, Chris Rees  wrote:

> Hi Andrew,
>
> On 5 February 2015 19:41:54 GMT+00:00, Andrew Hotlab <
> andrew.hot...@hotmail.com > 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
> "
>


-- 

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

Re: multimedia/x264 build failure

[Ben Woods]

This issue was discussed in November here:
https://lists.freebsd.org/pipermail/freebsd-ports/2014-November/096717.html

The result was an entry being added to UPDATING, which can be found here:
https://docs.freebsd.org/cgi/getmsg.cgi?fetch=2729771+0+/usr/local/www/db/text/2014/svn-ports-all/20141130.svn-ports-all

"With the recent split of multimedia/x264 in library and binary and
library components, if an application that uses libx264 is updated
before x264 itself, multimedia/libx264 will conflict with the existing
x264 package. Delete
this package before continuing any update that depends on it:

# pkg delete -f x264

Install the updated x264 and/or upgrade the other applications that
depend on libx264, such as ffmpeg."


Regards,

Ben


On Saturday, February 7, 2015, Bob Willcox  wrote:

> I'm getting the following error when trying to build x264:
>
> cc -o x264  x264.o input/input.o input/timecode.o input/raw.o input/y4m.o
> output/raw.o output/matroska.o output/matroska_ebml.o output/flv.o
> output/flv_bytestream.o filters/filters.o filters/video/video.o
> filters/video/source.o filters/video/internal.o filters/video/resize.o
> filters/video/cache.o filters/video/fix_vfr_pts.o
> filters/video/select_every.o filters/video/crop.o filters/video/depth.o
> input/thread.o output/mp4.o  -lgpac -lz  -L/usr/local/lib -lx264   -m64
> -fstack-protector -L/usr/local/lib -lm -pthread
> x264.o: In function `main':
> x264.c:(.text+0x1aea): undefined reference to `x264_encoder_open_142'
> cc: error: linker command failed with exit code 1 (use -v to see
> invocation)
> Makefile:177: recipe for target 'x264' failed
> gmake[1]: *** [x264] Error 1
> gmake[1]: Leaving directory
> '/usr/ports/multimedia/x264/work/x264-snapshot-20140827-2245-stable'
> ===> Compilation failed unexpectedly.
> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
> the maintainer.
> *** Error code 1
>
> Stop.
> make: stopped in /usr/ports/multimedia/x264
>
>
> Also, I get these warnings on every compilation:
>
> cc -Wno-maybe-uninitialized -Wshadow -O3 -ffast-math -m64 -O2 -pipe
> -fstack-protector -fno-strict-aliasing -Wall -I. -I. -I/usr/local/include
> -std=gnu99 -fomit-frame-pointer -fno-tree-vectorize   -c -o output/mp4.o
> output/mp4.c
> warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
> '-Wno-uninitialized'?
>   [-Wunknown-warning-option]
> warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
> '-Wno-uninitialized'?
>   [-Wunknown-warning-option]
>
> But they don't seem to be failing the build (it's the link error shown
> above).
>
> I'm currently at revision 378554 (just updated minutes ago).
>
> System info:
>
> FreeBSD vader.immure.com 10.1-STABLE FreeBSD 10.1-STABLE #0 r276511: Thu
> Jan  1 16:19:21 CST 2015 
> b...@vader.immure.com:/usr/obj/usr/src/sys/GENERIC
> amd64
>
>
> Bob
>
> --
> Bob Willcox| You climb to reach the summit, but once
> b...@immure.com  | there, discover that all roads lead down.
> Austin, TX |   -- Stanislaw Lem, "The Cyberiad"
> ___
> 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
> "
>


-- 

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

Re: multimedia/x264 build failure

[Ben Woods]

Correct. x264 port is no longer needed. Instead, the libx264 port is used
(and should be installed automatically).

On Saturday, February 7, 2015, Bob Willcox  wrote:

> On Sat, Feb 07, 2015 at 02:42:44PM +0800, Ben Woods wrote:
> > This issue was discussed in November here:
> >
> https://lists.freebsd.org/pipermail/freebsd-ports/2014-November/096717.html
> >
> > The result was an entry being added to UPDATING, which can be found here:
> >
> https://docs.freebsd.org/cgi/getmsg.cgi?fetch=2729771+0+/usr/local/www/db/text/2014/svn-ports-all/20141130.svn-ports-all
> >
> > "With the recent split of multimedia/x264 in library and binary and
> > library components, if an application that uses libx264 is updated
> > before x264 itself, multimedia/libx264 will conflict with the existing
> > x264 package. Delete
> > this package before continuing any update that depends on it:
> >
> > # pkg delete -f x264
> >
> > Install the updated x264 and/or upgrade the other applications that
> > depend on libx264, such as ffmpeg."
>
> Thanks Ben for your response.
>
> So, I went ahead and deleted x264 and then ran 'portupgrade -a' to upgrade
> the
> dependent packages (ffmpeg & minidlna in my case, I believe). Is that all
> I need to do? Note that the x264 package did not reinstall. Is this because
> I no longer need it?
>
> Thanks,
> Bob
>
> --
> Bob Willcox| You climb to reach the summit, but once
> b...@immure.com  | there, discover that all roads lead down.
> Austin, TX |   -- Stanislaw Lem, "The Cyberiad"
>


-- 

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

Re: question about settings in www/linkchecker

[Ben Woods]

The port has a compile time option "LOGIN", which adds the port www/twill
to the runtime dependencies if selected.

This is not the port option you are looking for (said in my best Obi-Wan
Kenobi voice).

Regards,
Ben

On Thursday, February 19, 2015, Henrik Hudson  wrote:

> Hello,
>
> I'm working on submitting a change to www/linkchecker to move the
> INSTALL_ICONS into a option dependency if QT or GTK is defined.
>
> However, there is setting in the Makefile labeled:
> LOGIN_RUN_DEPENDS=
>
> What is that for? A Google search only returns various forms of the
> Makefile in github, etc... for linkchecker. Can that be removed?
>
>
> henrik
>
> --
> Henrik Hudson
> li...@rhavenn.net 
> -
> "God, root, what is difference?" Pitr; UF
>
> ___
> 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
> "
>


-- 

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

Re: plist problems upgrading alpine port

[Ben Woods]

It's the opposite actually. That line was already in pkg-plist, but needed
to be removed. You have now added it a second time, meaning you get the
error twice.

You need to now delete both instances of that line from pkg-plist.

Regards,
Ben

On Friday, February 20, 2015, Marco Beishuizen  wrote:

> On Thu, 19 Feb 2015, the wise cpet wrote:
>
>  On 2015-02-19 14:48, Marco Beishuizen wrote:
>>
>>> Hi,
>>>
>>> I'm trying to upgrade the alpine port to 2.20 but I'm having problems
>>> with plist and staging. The error is:
>>>
>>> ...
>>> install  -o root -g wheel -m 444
>>> /home/marco/tmp/alpine/work/alpine-2.20/doc/tech-notes/low-level.html
>>> /home/marco/tmp/alpine/work/stage/usr/local/share/doc/alpine/tech-notes
>>> > Compressing man pages (compress-man)
>>> > Running Q/A tests (stage-qa)
>>> > Checking for pkg-plist issues (check-plist)
>>> ===> Parsing plist
>>> ===> Checking for items in STAGEDIR missing from pkg-plist
>>> ===> Checking for items in pkg-plist which are not in STAGEDIR
>>> Error: Missing: %%DOCSDIR%%/tech-notes/tech-notes.txt
>>> ===> Error: Plist issues found.
>>> *** Error code 1
>>> ...
>>>
>>> I guess the Makefile should be changed somewhere but I've no idea where.
>>>
>>> Does anyone have a clue how to solve this?
>>>
>>> Regards,
>>>
>>> Marco
>>>
>>
>> Copy and paste that to pkg-plist problem solved.
>>
>
> This makes it worse:
>
> ...
> install  -o root -g wheel -m 444 /home/marco/tmp/alpine/work/
> alpine-2.20/doc/tech-notes/low-level.html /home/marco/tmp/alpine/work/
> stage/usr/local/share/doc/alpine/tech-notes
> > Compressing man pages (compress-man)
> > Running Q/A tests (stage-qa)
> > Checking for pkg-plist issues (check-plist)
> ===> Parsing plist
> ===> Checking for items in STAGEDIR missing from pkg-plist
> ===> Checking for items in pkg-plist which are not in STAGEDIR
> Error: Missing: %%DOCSDIR%%/tech-notes/tech-notes.txt
> Error: Missing: %%DOCSDIR%%/tech-notes/tech-notes.txt
> ===> Error: Plist issues found.
> *** Error code 1
> ...
>
> Regards,
> Marco
>
> --
> Mr. Rockford, this is the Thomas Crown School of Dance and Contemporary
> Etiquette.  We aren't going to call again!  Now you want these free
> lessons or what?
> ___
> 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"
>


-- 

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

Re: xfce4-notifyd provides notification-daemon issues

[Ben Woods]

I have submitted a bug report for this issue, and provided a patch which
should resolve it:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197851


--
From: Benjamin Woods
woods...@gmail.com

On 20 February 2015 at 21:12, Santiago Pastorino 
wrote:

> Hi everyone,
>
>   I was trying to figure out an issue I'm hitting.
>
> Basically I was trying to install banshee from ports, which depends on
> notify-sharp, which depends on notification-daemon but I have already
> installed xfce4-notifyd and when I try to install I get an error
> `notification-daemon conflicts with xfce4-notifyd`.
>
> From what I see xfce4-notifyd is supposed to provide
> notification-daemon but when I run portmaster --check-depends says
> /usr/local/libexec/notification-daemon - not found so seems like
> xfce4-notifyd doesn't provide that file so the installation process does
> not reuse xfce4-notifyd.
>
> I'm not entirely sure my assumptions are correct. So my question is
> should xfce4-notifyd provide that file if it provides
> notification-daemon?, if not how can I fix this issue? or what else
> should I do?.
>
> Thanks in advance.
> ___
> 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: editors/libreoffice[-i18n]: compile failure: cannot install: the port wants postgresql-client

[Ben Woods]

I think the issue is simply that you have the DEBUG options enabled for
your ports building (most likely in /etc/make.conf).

According to editors/libreoffice/Makefile, building libreoffice with DEBUG
enabled is broken.

Try building without DEBUG and see how you go.

Regards,
Ben

On Monday, February 23, 2015, O. Hartmann 
wrote:

> Updating and installig of port editors/libreoffice[-i18n] fails with
> the strange error shown below. Port
> databases/postgresql94-[server|client] is installed on the system in
> question, running
>
> 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r279201: Mon Feb 23 10:00:43 CET
> 2015 amd64
>
> What is wrong with this installation/with the ports tree? Deleting the
> port doesn't solve the problem.
>
> Please CC
>
> Regards and thanks in advance,
>
> OH
>
> ===>>> Port directory: /usr/ports/editors/libreoffice
>
> ===>>> This port is marked IGNORE
> ===>>> cannot install: the port wants postgresql-client version
> 9.0 9.1 9.2 9.3 9.4 and you have version 9.4 installed
>
>
> ===>>> If you are sure you can build it, remove the
>IGNORE line in the Makefile and try again.
>
> ===>>> Update for editors/libreoffice failed
> ___
> 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
> "
>


-- 

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

Re: How could I increase "runaway" timer for package build cluster?

[Ben Woods]

You can increase the max_execution_time in /usr/local/share/common.sh
(default 3600 seconds). There are individual timeout values for extract,
install, package and deinstall. These are the maximum values for each stage
(with or without output being produced).

But more likely, you need to look at the NOHANG_TIME value in the same
common.sh file (default 7200 seconds). This is the one related to having no
output produced (aka "runaway build").

Someone has previously spoken about exposing these kinds of values for
tweaking in the poudriere configuration files, but I'm not sure it ever
progressed:
https://lists.freebsd.org/pipermail/freebsd-ports/2015-January/097757.html

Regards,
Ben

On Sunday, March 8, 2015, Lev Serebryakov  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
>  One of my ports (devel/gcc-arm-embedded) doesn't produce much output
> on build (output is redirected to log files), but takes severa hours
> to be built.
>
>  Looks like pkg building cluster doesn't like such behavior.
>
>  Could I notify build cluster (poudrere?) that this package takes a
> lot of time without output?
>
> - --
> // Lev Serebryakov AKA Black Lion
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (MingW32)
>
> iQJ8BAEBCgBmBQJU+3EZXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF
> QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EeP7MkP+wWeoKfCY2eydyIsQ8zMJrb+
> XaI9FQrfw1p5+/E4J2KYb3r+Luf5lxMoeNR9tOBE4NLcnrQQPCYokmXVugOb0prd
> U3Ta+gee4Fgo/5mbeSpRvRyZTbEGB7IAvra/65XtDg30TH2menO6LCPtfujFsPMn
> OryIa+ucBltkCFPTVtsNTTJNLzzjt1lgrMKLSKgpXATp4+k78xQZR9qassN7VMtg
> YvbMe+zalAyTKxGXicw3R1LwtjIjrzyiJfM+nLV/MJBrtVSMb2zdOWN0qTS2dhKV
> c2D+pR5RRi15wPGzLe7CfHEePJna52PK3HDXSurkRWyZCUqxsXj9lUtcungAWBrB
> 2viSCIl3Yzss3RsTnGnQoISjH8VbykzElM7dQfSwRooOt3URP6ZiJD5TYA8dzZ8g
> LqED0n+/SDySB5IwfRgzqDRE0zfmucgiUDRYYr1Dm8pXxDub3pwI7g9YCdFuATxY
> de58w2P/5qQ9QbmbHN0sNUSYRnXG9icq0VW87ZoxdBZPNZczbWzhlQAK5tdjBq8/
> 6eUqiCr+vpN/gMlsoQrJ/71GjbIb+SGsvsWij5Tzj/Lqz0OjrT5K7hgFKqjgSE8v
> 7pOK1d1d0u6mtRO1Qb2eDzAOaCjBAfJ13tSDMrCNIcqlTTalR9uFJQUgFwMu9sGI
> PTAY2Rban07jl0MDLHXD
> =nrHJ
> -END PGP SIGNATURE-
> ___
> freebsd-ports@freebsd.org  mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org
> "
>


-- 

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

Re: How could I increase "runaway" timer for package build cluster?

[Ben Woods]

Actually, taking a look at my /usr/local/etc/poudriere.conf configuration
file, I see these settings have indeed been exposed for configuration there
without having to touch the poudriere code itself. The appropriate settings
are:

# This defines the max time (in seconds) that a command may run for a build
# before it is killed for taking too long. Default: 86400
#MAX_EXECUTION_TIME=86400

# This defines the time (in seconds) before a command is considered to
# be in a runaway state for having no output on stdout. Default: 7200
#NOHANG_TIME=7200

Regards,
Ben


--
From: Benjamin Woods
woods...@gmail.com

On 8 March 2015 at 07:00, Ben Woods  wrote:
>
> You can increase the max_execution_time in /usr/local/share/common.sh
(default 3600 seconds). There are individual timeout values for extract,
install, package and deinstall. These are the maximum values for each stage
(with or without output being produced).
>
> But more likely, you need to look at the NOHANG_TIME value in the same
common.sh file (default 7200 seconds). This is the one related to having no
output produced (aka "runaway build").
>
> Someone has previously spoken about exposing these kinds of values for
tweaking in the poudriere configuration files, but I'm not sure it ever
progressed:
> https://lists.freebsd.org/pipermail/freebsd-ports/2015-January/097757.html
>
> Regards,
> Ben
>
>
> On Sunday, March 8, 2015, Lev Serebryakov  wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>>
>>  One of my ports (devel/gcc-arm-embedded) doesn't produce much output
>> on build (output is redirected to log files), but takes severa hours
>> to be built.
>>
>>  Looks like pkg building cluster doesn't like such behavior.
>>
>>  Could I notify build cluster (poudrere?) that this package takes a
>> lot of time without output?
>>
>> - --
>> // Lev Serebryakov AKA Black Lion
___
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 you maintain which are out of date

[Ben Woods]

PR submitted: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198486
deskutils/genius: Update to 1.0.20


--
From: Benjamin Woods
woods...@gmail.com

On 10 March 2015 at 17:49,  wrote:
>
> Dear port maintainer,
>
> The portscout new distfile checker has detected that one or more of your
> ports appears to be out of date. Please take the opportunity to check
> each of the ports listed below, and if possible and appropriate,
> submit/commit an update. If any ports have already been updated, you can
> safely ignore the entry.
>
> You will not be e-mailed again for any of the port/version combinations
> below.
>
> Full details can be found at the following URL:
> http://portscout.freebsd.org/po...@freebsd.org.html
>
>
> Port| Current version | New
version
>
+-+
> deskutils/genius| 1.0.19  | 1.0.20
>
+-+
>
>
> If any of the above results are invalid, please check the following page
> for details on how to improve portscout's detection and selection of
> distfiles on a per-port basis:
>
> http://portscout.freebsd.org/info/portscout-portconfig.txt
>
> Thanks.
> ___
> freebsd-ports@freebsd.org mailing list
> 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: converters/iconv versioning

[Ben Woods]

FreeBSD has its own native iconv (since FreeBSD 10).

More details (including reference to commits) here:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/using-iconv.html

Regards,
Ben

On Wednesday, March 11, 2015, Scott Furry  wrote:

> I am running into in a situation with other C code where a call to iconv
> and passing in a non-const source buffer would result in a build warning.
> Others who use the same code on other platforms do not report this warning.
>
> In tracking down the issue, I have discovered that there may be a
> difference in the iconv.h header file used on FreeBSD versus Mac/Linux et
> al.
>
> http://www.opensource.apple.com/source/libiconv/libiconv-
> 30/install/iconv.h
> line 48 shows that call to iconv
> -
> size_t iconv (iconv_t /*cd*/,
> char ** __restrict /*inbuf*/,  size_t * __restrict /*inbytesleft*/,
> char ** __restrict /*outbuf*/, size_t * __restrict /*outbytesleft*/);
> 
>
> /usr/local/include/iconv.h, line 83, shows something rather different.
> Even the commentary around the code is different.
> -
> extern size_t iconv (iconv_t cd, const char* * inbuf, size_t *inbytesleft,
> char* * outbuf, size_t *outbytesleft);
> -
>
>
> My question is this, are we using a different or FreeBSD-specific version
> of iconv?
>
> S
> ___
> 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"
>


-- 

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

Re: [HEADSUP] WIP on fonts

[Ben Woods]

My poudriere is acting funny now, and I'm not sure if it's related. It
keeps deleting xorg-fonts-truetype because there is a new dependency
(x11-fonts/dejavu), and then having to rebuild a whole suit of packages as
a result.

The interesting thing is that dejavu was a dependency the entire time. It
will successfully peform the bulk build and update the package set. If I
then re-run the bulk build, it does the same thing every time.

My make.conf file (which hasn't changed in some time) contains:
OPTIONS_SET=VAAPI VDPAU X265 ASS FAAC LAME
MDNSRESPONDER RRDTOOL STATGRAB DEJAVU


The strange output from poudriere:

[00:00:22] >> Sanity checking the repository
[00:00:22] >> Checking packages for incremental rebuild needed
[00:00:42] >> Deleting xorg-fonts-truetype-7.7_1.txz: new dependency:
x11-fonts/dejavu
[00:00:45] >> Deleting pango-1.36.8.txz: missing dependency:
xorg-fonts-truetype-7.7_1
[00:00:45] >> Deleting plexhometheater-1.2.2_7.txz: missing dependency:
pango-1.36.8
[00:00:45] >> Deleting policykit-gnome-0.9.2_7.txz: missing dependency:
pango-1.36.8
[00:00:45] >> Deleting rrdtool-1.4.8_6.txz: missing dependency:
pango-1.36.8


Any ideas?
-Ben

On Sunday, March 22, 2015, Baptiste Daroussin  wrote:

> On Fri, Mar 20, 2015 at 04:37:13PM +0100, Baptiste Daroussin wrote:
> > Hi all,
> >
> > Some of you may have notice some work on the font area.
> >
> > The goal of this work is to prevent every single font package to act
> differently
> > and most of the time not correctly.
> >
> > The change will be done in multiple steps:
> > 1/ Convert every ports to USES=fonts
> > 2/ Remove @fc and @fontsdir keywords to only keep @fcfontsdir
> > 3/ Move all fonts from ${LOCALBASE}/lib/X11/fonts to
> ${LOCALBASE}/share/fonts in
> > order to make the fonts following XDG as well as making them working for
> non-x11
> > world (wayland for example)
> >
> > Best regards,
> > Bapt
>
>
> Done in r381876 please report me all possible issue, I have done quite a
> lot of
> testing but I cannot test everything.
>
> Best regards,
> Bapt
>


-- 

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

Re: [HEADSUP] WIP on fonts

[Ben Woods]

I can confirm this issue is now resolved with the latest ports tree. Thanks
for your help Bryan and Bapt!
On Tue, 24 Mar 2015 at 1:25 pm Baptiste Daroussin  wrote:

> On Mon, Mar 23, 2015 at 05:51:51PM -0500, Bryan Drewery wrote:
> > On 3/23/2015 11:44 AM, Bryan Drewery wrote:
> > > On 3/23/2015 11:39 AM, Bryan Drewery wrote:
> > >> On 3/22/2015 5:28 AM, Ben Woods wrote:
> > >>> My poudriere is acting funny now, and I'm not sure if it's related.
> It
> > >>> keeps deleting xorg-fonts-truetype because there is a new dependency
> > >>> (x11-fonts/dejavu), and then having to rebuild a whole suit of
> packages as
> > >>> a result.
> > >>>
> > >>> The interesting thing is that dejavu was a dependency the entire
> time. It
> > >>> will successfully peform the bulk build and update the package set.
> If I
> > >>> then re-run the bulk build, it does the same thing every time.
> > >>>
> > >>> My make.conf file (which hasn't changed in some time) contains:
> > >>> OPTIONS_SET=VAAPI VDPAU X265 ASS FAAC LAME
> > >>> MDNSRESPONDER RRDTOOL STATGRAB DEJAVU
> > >>>
> > >>>
> > >>
> > >> It will do this if a port has a dependency listed that it does not
> > >> actually use. So the xorg-fonts-truetype is incorrectly depending on
> > >> x11-fonts/dejavu.
> > >
> > >
> > > xorg-fonts-trutype has:
> > > +
> > > ${FONTDIR}/dejavu/DejaVuSans.ttf:${PORTSDIR}/x11-fonts/dejavu
> > > ~/svn/ports/x11-fonts/xorg-fonts-truetype # make -V FONTDIR
> > > /usr/local/share/fonts
> > >
> > >
> > > The dejavu port has:
> > >
> > > ~/svn/ports/x11-fonts/dejavu # grep DejaVuSans.ttf pkg-plist
> > > %%FONTSDIR%%/DejaVuSans.ttf
> > > ~/svn/ports/x11-fonts/dejavu # make -V '${PLIST_SUB:MFONTSDIR*}'
> > > FONTSDIR="/usr/local/share/fonts/dejavu"
> > >
> > > So somehow the package is lacking this file, or poudriere is wrong
> here.
> > >
> > > I'm double checking with some builds now.
> > >
> >
> > It seems fine to me. Does it still happen for you every time?
> >
> >
> > --
> > Regards,
> > Bryan Drewery
> >
>
>
> This was due to me not bumping dejavu fonts, that is fixed now
>
> Bapt
>
___
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: mc-4.8.14

[Ben Woods]

Hi Jiri,

I am having difficulty replicating this fault, however it is no doubt
linked to the change made in 4.8.14 under MC bug report #2027. See here:
http://www.midnight-commander.org/ticket/2027

Have you set a custom bash prompt in a .bashrc or .bash_profile or
/etc/profile? If so, what have you set so that I can try and replicate this
issue?

Thanks,
Ben


On Sat, Mar 28, 2015 at 12:20 AM Jiri Lazansky  wrote:

> Dear maintainer:
>
> I tried to upgrade well working mc-4.8.13_3 to mc-4.8.14 on FreeBSD 9.3
> (AMD64) with subshell using the port misc/mc. My shell is 'bash'.
>
> The result was:
>
> 1. Very long start-up time
> 2. Subshell not working (has not read ~/.bashrc).
>
> Following patch resolved the situation:
>
> ==
> --- src/subshell.c.orig
> +++ src/subshell.c
> @@ -874,8 +874,7 @@
>  {
>  case BASH:
>  g_snprintf (precmd, sizeof (precmd),
> -" PROMPT_COMMAND=${PROMPT_COMMAND:+$PROMPT_COMMAND;
> }'pwd>&%d;kill -STOP $$'\n",
> -subshell_pipe[WRITE]);
> +" PROMPT_COMMAND='pwd>&%d;kill -STOP $$'\n",
> subshell_pipe[WRITE]);
>  break;
>
>  case ZSH:
> ===
>
> The output of 'mc -V' is
>
> GNU Midnight Commander 4.8.14
> Built with GLib 2.42.2
> Using the S-Lang library with terminfo database
> With builtin Editor
> With subshell support as default
> With support for background operations
> With mouse support on xterm
> With support for X11 events
> With internationalization support
> With multiple codepages support
> Virtual File Systems: cpiofs, tarfs, sfs, extfs, ftpfs, sftpfs, fish, smbfs
> Data types: char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64;
>
> Please analyse the reasons and try to update the port.
>
> Best regards
>
> Jiri Lazansky
> 
>
>
>
___
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"

Update editors/abiword to 3.0.1

[Ben Woods]

I am trying to update editors/abiword from 2.8.6 to 3.0.1.

Part way through compiling my new test port, I get the following errors:

gmake[7]: Entering directory
'/wrkdirs/usr/ports/editors/abiword/work/abiword-3.0.1/src/text/fmt/xp'
  CXX  fl_Squiggles.lo
  CXX  fb_Alignment.lo
In file included from fb_Alignment.cpp:22:
./fb_Alignment.h:114:8: warning: private field 'm_iSpaceCountLeft' is
not used [-Wunused-private-field]
int m_iSpaceCountLeft;
^
./fb_Alignment.h:115:8: warning: private field 'm_iSpaceCount' is not
used [-Wunused-private-field]
int m_iSpaceCount;
^
2 warnings generated.
  CXX  fb_ColumnBreaker.lo
In file included from fb_ColumnBreaker.cpp:22:
./fb_ColumnBreaker.h:53:24: warning: private field 'm_pCurrentBlock'
is not used [-Wunused-private-field]
fl_BlockLayout *  m_pCurrentBlock;
  ^
1 warning generated.
  CXX  fb_LineBreaker.lo
  CXX  fg_Graphic.lo
  CXX  fg_GraphicRaster.lo
  CXX  fg_GraphicVector.lo
  CXX  fl_AutoLists.lo
  CXX  fl_AutoNum.lo
  CXX  fl_BlockLayout.lo
  CXX  fl_ContainerLayout.lo
  CXX  fl_DocLayout.lo
  CXX  fl_DocListener.lo
  CXX  fl_FootnoteLayout.lo
  CXX  fl_FrameLayout.lo
  CXX  fl_Layout.lo
  CXX  fl_SectionLayout.lo
  CXX  fl_SelectionPreserver.lo
  CXX  fl_TableLayout.lo
  CXX  fl_TestRoutines.lo
  CXX  fl_TOCLayout.lo
In file included from fl_TOCLayout.cpp:32:
./fl_TOCLayout.h:82:20: warning: private field 'm_iStartAt' is not
used [-Wunused-private-field]
UT_sint32 m_iStartAt;
  ^
1 warning generated.
  CXX  fp_AnnotationRun.lo
  CXX  fp_RDFAnchorRun.lo
In file included from fp_RDFAnchorRun.cpp:23:
In file included from ./fp_Run.h:33:
In file included from ../../../../src/af/util/xp/ut_misc.h:39:
In file included from /usr/include/c++/v1/string:439:
In file included from /usr/include/c++/v1/algorithm:627:
In file included from /usr/include/c++/v1/memory:601:
/usr/include/c++/v1/__functional_base:63:21: error: invalid operands
to binary expression ('const PD_URI' and 'const PD_URI')
{return __x < __y;}
~~~ ^ ~~~
/usr/include/c++/v1/map:457:17: note: in instantiation of member
function 'std::__1::less::operator()' requested here
{return static_cast(*this)(__x.__cc.first,
__y.__cc.first);}
^
/usr/include/c++/v1/__tree:1573:29: note: in instantiation of member
function 'std::__1::__map_value_compare, std::__1::less,
true>::operator()' requested here
if (__hint == end() || !value_comp()(*__hint, __v))  // check before
^
/usr/include/c++/v1/__tree:1912:36: note: in instantiation of member
function 'std::__1::__tree,
std::__1::__map_value_compare, std::__1::less, true>,
std::__1::allocator >
>::__find_leaf' requested here
__node_base_pointer& __child = __find_leaf(__p, __parent, __v);
   ^
/usr/include/c++/v1/map:1779:25: note: in instantiation of member
function 'std::__1::__tree,
std::__1::__map_value_compare, std::__1::less, true>,
std::__1::allocator >
>::__insert_multi' requested here
__tree_.__insert_multi(__e.__i_, *__f);
^
/usr/include/c++/v1/map:1612:13: note: in instantiation of function
template specialization 'std::__1::multimap, std::__1::allocator >
>::insert, std::__1::__tree_node, void *> *, long> > >' requested here
insert(__m.begin(), __m.end());
^
../../../../src/text/ptbl/xp/pd_DocumentRDF.h:198:18: note: in
instantiation of member function 'std::__1::multimap,
std::__1::allocator >
>::multimap' requested here
class ABI_EXPORT PD_RDFModelIterator
 ^
../../../../src/af/util/xp/ut_string_class.h:124:17: note: candidate
function not viable: no known conversion from 'const PD_URI' to 'const
UT_String' for 1st argument
ABI_EXPORT bool operator<(const UT_String& s1, const UT_String& s2);
^
../../../../src/af/util/xp/ut_string_class.h:277:17: note: candidate
function not viable: no known conversion from 'const PD_URI' to 'const
UT_UTF8String' for 1st argument
ABI_EXPORT bool operator<(const UT_UTF8String& s1, const UT_UTF8String& s2);
^
../../../../src/af/util/xp/ut_string_class.h:394:6: note: candidate
function not viable: no known conversion from 'const PD_URI' to 'const
UT_UCS4String' for 1st argument
bool operator<(const UT_UCS4String& s1, const UT_UCS4String& s2);
 ^
/usr/include/c++/v1/utility:419:1: note: candidate template ignored:
could not match 'pair' against
'const PD_URI'
operator< (const pair<_T1,_T2>& __x, const pair<_T1,_T2>& __y)
^
/usr/include/c++/v1/iterator:582:1: note: candidate template ignored:
could not match 'reverse_iterator' against 'const
PD_URI'
operator<(const reverse_iterator<_Iter1>& __x, const
reverse_ite

Re: Update editors/abiword to 3.0.1

[Ben Woods]

Thanks for the feedback Gleb. I am compiling with clang 3.4.1 in FreeBSD
10.1 base.

I have since spoken to an Abiword developer, who kindly helped me fix this
issue with the following patch (which I will include in the PR I will
submit to update this port):

diff --git a/src/text/ptbl/xp/pd_DocumentRDF.cpp
b/src/text/ptbl/xp/pd_DocumentRDF.cpp
index 798e262..3406b88 100644
--- a/src/text/ptbl/xp/pd_DocumentRDF.cpp
+++ b/src/text/ptbl/xp/pd_DocumentRDF.cpp
@@ -570,6 +570,11 @@ bool PD_URI::operator==(const std::string& b) const
 return m_value == b;
 }

+bool PD_URI::operator<(const PD_URI& b) const
+{
+return m_value < b.m_value;
+}
+
 PD_URI
 PD_URI::prefixedToURI( PD_RDFModelHandle model ) const
 {
@@ -611,11 +616,6 @@ bool PD_URI::write( std::ostream& ss ) const
 return true;
 }

-bool operator<( PD_URI a, PD_URI b)
-{
-return a.toString() < b.toString();
-}
-
 bool operator<( std::pair< PD_URI, PD_URI > a, PD_URI b)
 {
 return a.first.toString() < b.toString();
diff --git a/src/text/ptbl/xp/pd_DocumentRDF.h
b/src/text/ptbl/xp/pd_DocumentRDF.h
index 66e9fd6..3e6b8ef 100644
--- a/src/text/ptbl/xp/pd_DocumentRDF.h
+++ b/src/text/ptbl/xp/pd_DocumentRDF.h
@@ -68,6 +68,7 @@ class ABI_EXPORT PD_URI
 bool isValid() const;
 bool operator==(const PD_URI& b) const;
 bool operator==(const std::string& b) const;
+bool operator<(const PD_URI& b) const;

 virtual bool read( std::istream& ss );
 virtual bool write( std::ostream& ss ) const;


Regards,
Ben

On Wed, Apr 1, 2015 at 2:22 AM Gleb Popov <6year...@gmail.com> wrote:

> On Tue, Mar 31, 2015 at 6:00 PM, Ben Woods  wrote:
>
>> I am trying to update editors/abiword from 2.8.6 to 3.0.1.
>>
>> Part way through compiling my new test port, I get the following errors:
>>
>> gmake[7]: Entering directory
>> '/wrkdirs/usr/ports/editors/abiword/work/abiword-3.0.1/src/text/fmt/xp'
>>   CXX  fl_Squiggles.lo
>>   CXX  fb_Alignment.lo
>> In file included from fb_Alignment.cpp:22:
>> ./fb_Alignment.h:114:8: warning: private field 'm_iSpaceCountLeft' is
>> not used [-Wunused-private-field]
>> int m_iSpaceCountLeft;
>> ^
>> ./fb_Alignment.h:115:8: warning: private field 'm_iSpaceCount' is not
>> used [-Wunused-private-field]
>> int m_iSpaceCount;
>> ^
>> 2 warnings generated.
>>   CXX  fb_ColumnBreaker.lo
>> In file included from fb_ColumnBreaker.cpp:22:
>> ./fb_ColumnBreaker.h:53:24: warning: private field 'm_pCurrentBlock'
>> is not used [-Wunused-private-field]
>> fl_BlockLayout *  m_pCurrentBlock;
>>   ^
>> 1 warning generated.
>>   CXX  fb_LineBreaker.lo
>>   CXX  fg_Graphic.lo
>>   CXX  fg_GraphicRaster.lo
>>   CXX  fg_GraphicVector.lo
>>   CXX  fl_AutoLists.lo
>>   CXX  fl_AutoNum.lo
>>   CXX  fl_BlockLayout.lo
>>   CXX  fl_ContainerLayout.lo
>>   CXX  fl_DocLayout.lo
>>   CXX  fl_DocListener.lo
>>   CXX  fl_FootnoteLayout.lo
>>   CXX  fl_FrameLayout.lo
>>   CXX  fl_Layout.lo
>>   CXX  fl_SectionLayout.lo
>>   CXX  fl_SelectionPreserver.lo
>>   CXX  fl_TableLayout.lo
>>   CXX  fl_TestRoutines.lo
>>   CXX  fl_TOCLayout.lo
>> In file included from fl_TOCLayout.cpp:32:
>> ./fl_TOCLayout.h:82:20: warning: private field 'm_iStartAt' is not
>> used [-Wunused-private-field]
>> UT_sint32 m_iStartAt;
>>   ^
>> 1 warning generated.
>>   CXX  fp_AnnotationRun.lo
>>   CXX  fp_RDFAnchorRun.lo
>> In file included from fp_RDFAnchorRun.cpp:23:
>> In file included from ./fp_Run.h:33:
>> In file included from ../../../../src/af/util/xp/ut_misc.h:39:
>> In file included from /usr/include/c++/v1/string:439:
>> In file included from /usr/include/c++/v1/algorithm:627:
>> In file included from /usr/include/c++/v1/memory:601:
>> /usr/include/c++/v1/__functional_base:63:21: error: invalid operands
>> to binary expression ('const PD_URI' and 'const PD_URI')
>> {return __x < __y;}
>> ~~~ ^ ~~~
>> /usr/include/c++/v1/map:457:17: note: in instantiation of member
>> function 'std::__1::less::operator()' requested here
>> {return static_cast(*this)(__x.__cc.first,
>> __y.__cc.first);}
>> ^
>> /usr/include/c++/v1/__tree:1573:29: note: 

How do I specify port opt1 requires opt2

[Ben Woods]

I am working on modifying a port, and was wondering how do I specify that
selecting port option1 requires that option2 is also selected?

Note that in my example it is perfectly acceptable to have option2 selected
without option1.

Thanks in advance,
Ben
___
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: editors/abiword fails on not-really-missing dependency

[Ben Woods]

I have just submitted a bug report which includes a patch to update abiword
to the latest upstream release version 3.0.1.

This fixes the issues you have identified in your email.

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

I would be greatful if you could test this patch to the port and confirm it
fixes your issue.

Regards,
Ben

On Mon, Mar 30, 2015 at 10:05 AM Thomas Mueller 
wrote:

> I tried to build editors/abiword, but it failed for lack of libwpg-0.1 and
> libwpd-0.8.
>
> pkg info -a | grep -n "libwp" produces
>
> 314:libwpd-0.9.9_2 Tools for importing and exporting
> WordPerfect(tm) documents
> 315:libwpg-0.2.2_3 Library and tools to work with
> WordPerfect Graphics (WPG) files
>
> So it looks like I have the required dependencies, but the configure
> script seemed to be looking for an earlier version.
>
> Relevant part of build log is
>
> configure: error: Package requirements ( libgsf-1 >= 1.12 libwpg-0.1 >=
> 0.1.0 libwpd-0.8 >= 0.8.0 ) were not met:
>
> Package libwpg-0.1 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libwpg-0.1.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'libwpg-0.1', required by 'world', not found
> Package 'libwpd-0.8', required by 'world', not found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables WPG_CFLAGS
> and WPG_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> ===>  Script "configure" failed unexpectedly.
>
>
> Is this a bug in the configure script or FreeBSD ports' patches?
>
> I could cd /usr/local/libdata/pkgconfig  and
> ln -s libwpg-0.2.pc libwpg-0.1.pc
> ln -s libwpd-0.9.pc libwpd-0.8.pc
>
> and thereby give the configure script what it's looking for, a kludge with
> no certainty of success.
>
> Maybe delete the symbolic links afterward.
>
> Tom
>
> ___
> 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: blender 2.74

[Ben Woods]

Actually, blender 2.74 hit the ports tree earlier today.
https://svnweb.freebsd.org/ports?view=revision&revision=383098

On Sat, Apr 4, 2015 at 3:02 PM Shane Ambler  wrote:

> On 04/04/2015 09:01, ajtiM wrote:
> > Hi!
> >
> > I did install Blender 2.74 on my FreeBSD 10.1 (amd64) without a problem
> > but it doesn't want to start. When I run from terminal I got:
> >
> > "blender
> > Two passes with the same argument (-alloca-hoisting) attempted to be
> > registered!
> > Writing: /tmp/blender.crash.txt
> > Segmentation fault (core dumped)"
> >
> >
> > In /tmp/blender.crash.txt is just:
> > # Blender 2.74 (sub 0), Unknown revision
> >
> > # backtrace
> >
>
> 2.74 hasn't been added to ports yet, are you compiling yourself?
>
> The error looks familiar, I think it was from different llvm versions
> being used. blender needs to use the same llvm/clang version as osl. -3.4
>
> Check your LLVM_* settings in cmake.
>
>
> --
> FreeBSD - the place to B...Software Developing
>
> Shane Ambler
>
> ___
> 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: Blender 2.74 cannot compile on FreeBSD 10.1

[Ben Woods]

The graphics/libraw package installs /usr/local/lib/libraw_r.so.10, not
libraw_r.so.9 so it will not be detected. See the pkg-plist for
graphics/libraw here:
https://svnweb.freebsd.org/ports/head/graphics/libraw/pkg-plist?revision=379518&view=markup

The interesting thing is that whilst graphics/blender depends on
the graphics/openimageio library, neither depend on the graphics/libraw
library.

It might be worth asking the port maintainers for graphics/blender and
graphics/openimageio if they have come across this before. I have added
m...@freebsd.org and free...@shaneware.biz to the recipients of this email
to check with them.

Regards,
Ben

On Sun, Apr 5, 2015 at 9:33 AM Robert Backhaus  wrote:

> To get the simple things out of the road - you have reinstalled libraw, and
> checked that libraw_r.so.9 is in /usr/local/lib?
>
> This error tells me that your install of libOpenImageIO.so.1.4 is faulty,
> so you should also rebuild the port that includes that (pkg which `locate
> \*libOpenImageIO.so.1.4`)
>
> On 5 April 2015 at 02:36, pipolandi  wrote:
>
> > I forgot to say that libraw is installed.
> >
> >
> >
> > --
> > View this message in context:
> > http://freebsd.1045724.n5.nabble.com/Blender-2-74-
> cannot-compile-on-FreeBSD-10-1-tp6002715p6002716.html
> > Sent from the freebsd-ports mailing list archive at Nabble.com.
> > ___
> > freebsd-ports@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> >
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
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: Blender 2.74 cannot compile on FreeBSD 10.1

[Ben Woods]

Thanks for the feedback Shane :)

On Mon, Apr 6, 2015 at 3:35 PM Shane Ambler  wrote:

> On 05/04/2015 18:08, Ben Woods wrote:
> > The graphics/libraw package installs /usr/local/lib/libraw_r.so.10, not
> > libraw_r.so.9 so it will not be detected. See the pkg-plist for
> > graphics/libraw here:
> > https://svnweb.freebsd.org/ports/head/graphics/libraw/
> pkg-plist?revision=379518&view=markup
> >
> > The interesting thing is that whilst graphics/blender depends on
> > the graphics/openimageio library, neither depend on the graphics/libraw
> > library.
> >
> > It might be worth asking the port maintainers for graphics/blender and
> > graphics/openimageio if they have come across this before. I have added
> > m...@freebsd.org and free...@shaneware.biz to the recipients of this
> email
> > to check with them.
>
> Yes that's my fault, if openimageio finds libraw it will use it but
> doesn't seem to find the current libraw. I should add that as an option
> and patch it to find the current version. Looks like I should also do
> the same for libgif.
>
> thanks
>
> >
> > On Sun, Apr 5, 2015 at 9:33 AM Robert Backhaus 
> wrote:
> >
> >> To get the simple things out of the road - you have reinstalled libraw,
> and
> >> checked that libraw_r.so.9 is in /usr/local/lib?
> >>
> >> This error tells me that your install of libOpenImageIO.so.1.4 is
> faulty,
> >> so you should also rebuild the port that includes that (pkg which
> `locate
> >> \*libOpenImageIO.so.1.4`)
> >>
> >> On 5 April 2015 at 02:36, pipolandi  wrote:
> >>
> >>> I forgot to say that libraw is installed.
> >>>
>
>
> --
> FreeBSD - the place to B...Software Developing
>
> Shane Ambler
>
>
___
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: [package - head-i386-default][emulators/wine-compholio] Failed for wine-compholio-1.7.40,1 in build

[Ben Woods]

It looks like this is a bug which has been reported upstream in the wine
forums:
https://forum.winehq.org/viewtopic.php?t=24430&p=99442
On Tue, 7 Apr 2015 at 1:53 pm Gerald Pfeifer  wrote:

> On Tue, 7 Apr 2015, pkg-fall...@freebsd.org wrote:
> > Ident:  $FreeBSD: head/emulators/wine-compholio/Makefile 375756
> 2014-12-28 20:39:48Z dbn $
> > Log URL:http://beefy3.isc.freebsd.org/data/head-i386-default/
> p383446_s281156/logs/wine-compholio-1.7.40,1.log
> > Build URL:  http://beefy3.isc.freebsd.org/
> build.html?mastername=head-i386-default&build=p383446_s281156
> > Log:
> >
> > >> Building emulators/wine-compholio
> > build started at Tue Apr  7 04:55:12 UTC 2015
> > port directory: /usr/ports/emulators/wine-compholio
> > building for: FreeBSD head-i386-default-job-13 11.0-CURRENT FreeBSD
> 11.0-CURRENT #0 r279966: Fri Mar 13 22:02:53 UTC 2015
>  pe...@build-11.freebsd.org:/usr/obj/usr/src/sys/CLUSTER11  i386
> > maintained by: ger...@freebsd.org
> > Makefile ident:  $FreeBSD: head/emulators/wine-compholio/Makefile
> 375756 2014-12-28 20:39:48Z dbn $
> > Poudriere version: 3.1.3
> > Host OSVERSION: 1100064
> > Jail OSVERSION: 1100067
> >
> > !!! Jail is newer than host. (Jail: 1100067, Host: 1100064) !!!
> > !!! This is not supported. !!!
> > !!! Host kernel must be same or newer than jail. !!!
> > !!! Expect build failures. !!!
>
> Apart from me wondering why those test results are shared if
> build failures are to be expected
>
> > cc -c -o socket.o socket.c -I. -I../../include -D__WINESRC__
> -DUSE_WS_PREFIX -D_REENTRANT -fPIC -Wall \
> >   -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body
> -Wignored-qualifiers \
> >   -Wstrict-prototypes -Wtype-limits -Wvla -Wwrite-strings
> -Wpointer-arith -fno-omit-frame-pointer \
> >   -I/usr/local/include -O2 -pipe  -fstack-protector -fno-strict-aliasing
> > socket.c:368:27: error: use of undeclared identifier 'WS_IPX_PTYPE'
> > DEBUG_SOCKOPT(WS_IPX_PTYPE);
> >   ^
> > socket.c:330:32: note: expanded from macro 'DEBUG_SOCKOPT'
> > #define DEBUG_SOCKOPT(x) case (x): stropt = #x; break
> >^
> > socket.c:369:27: error: use of undeclared identifier 'WS_IPX_FILTERPTYPE'
> > DEBUG_SOCKOPT(WS_IPX_FILTERPTYPE);
> >   ^
> > socket.c:330:32: note: expanded from macro 'DEBUG_SOCKOPT'
> > #define DEBUG_SOCKOPT(x) case (x): stropt = #x; break
> >^
> > socket.c:370:27: error: use of undeclared identifier 'WS_IPX_DSTYPE'
> > DEBUG_SOCKOPT(WS_IPX_DSTYPE);
> >   ^
>
> ...does anyone know what is going on in HEAD and what to do about
> it?
>
> Or is this a temporary thing and we should ignore this on the ports
> side?
>
> Gerald
> ___
> 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: MooseFS Ports for versions 2.0 and 3.0

[Ben Woods]

Those ports currently have their maintainer fields set to "po...@freebsd.org",
meaning there is no maintainer.

When you submit the bug report and attach your patch to update the port,
simply ensure the maintainer email address is updated to your own. You will
then be volunteering as the maintainer for those ports.

Regards,
Ben
On Thu, 9 Apr 2015 at 9:12 pm Fernando Apesteguía <
fernando.apesteg...@gmail.com> wrote:

> El 09/04/2015 15:00, "Piotr Robert Konopelko"  >
> escribió:
> >
> > Dear FreeBSD Ports team,
> >
> > On FreeBSD Ports site only ports for MooseFS 1.6.27-5 are available:
> > https://www.freebsd.org/cgi/ports.cgi?query=moosefs&stype=all[1]
> >
> > Longer than a half year ago MooseFS 2.0 has been released and few days
> ago - MooseFS
> > 3.0.
> >
> > We would like to inform, that we have prepared ports for MooseFS versions
> 2.0 and 3.0.
> >
> > How is the way to upgrade them in FreeBSD ports tree?
>
> You can start here:
>
> https://bugs.freebsd.org/bugzilla/
>
> And file a request
>
> > Is there a possibility to make our team the maintainer of the MooseFS
> FreeBSD Ports?
>
> Since ports@ is the current maintainer, you could file another request and
> see if they are willing to drop mantainership in your favor or ask here :)
>
> >
> >
> > --
> > Best regards,
> > Piotr Robert Konopelko
> > *MooseFS Technical Support Engineer* | moosefs.com[2]
> >
> >
> > 
> > [1] https://www.freebsd.org/cgi/ports.cgi?query=moosefs&stype=all
> > [2] http://moosefs.com
> > ___
> > freebsd-ports@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
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: HandBrake port?

[Ben Woods]

It looks like a few volunteers have been putting in some good effort to get
this port working (thanks to Walter Schwarzenfeld and kwhite). The patch
which is needed to make this work is not committed yet, but is attached to
PR199126 here and awaiting a committer:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199126

To build this port with this patch:
$ cd ~
$ fetch -o handbrake.patch "
https://bugs.freebsd.org/bugzilla/attachment.cgi?id=155525";
$ cd /usr/ports
$ sudo patch -p0 < ~/handbrake.patch

Then build and install the port as per normal.

Regards,
Ben

On Mon, Apr 13, 2015 at 3:16 PM Kurt Jaeger  wrote:

> Hi!
>
> > I'm attempting to install HandBrake on my FreeNAS version 9.3 in a
> jail.  I
> > can not find a pkg for handbrake.  Can you provide me with the
> installation
> > steps to install handbrake in a jail?  Or provide me with a link that
> shows
> > how to install handbrake in a jail?
>
> This should work:
>
> cd /usr/ports/multimedia/handbrake
> make install
>
> but right now it seems to fail.
>
> --
> p...@opsec.eu+49 171 3101372 5 years to
> go !
> ___
> 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: MooseFS Ports for versions 2.0 and 3.0

[Ben Woods]

Nice work putting the ports together - its a good first effort! I have a
few comments about the format of the ports and bug reports - sorry there
are quite a few. I don't mean to be picky, but I wanted to minimise the
back-and-forth for you to get these committed.

1. Updates to existing ports should be attached as patches to the current
ports tree. The easiest way to do this if you got the ports tree from
subversion (not portsnap) is using the svn diff command. Tick the "patch"
option when attaching so we can see a nice pretty diff from within bugzilla.

2. New ports should be attached as a shar(1) file. Assuming the port is
called oneko, cd to the directory above where the oneko directory is
located, and then type: shar `find oneko` > oneko.shar

3. It's nice for ports for share parts of their configuration, but I don't
think it should be called "bsd.port.moosefs.mk" (this implies it is part of
the port build scripts). A good example of what you could do
is devel/libtool. It has a Makefile which includes Makefile.common. The
devel/libltdl port also includes "${.CURDIR}/../libtool/Makefile.common".

4. @dirrm is now deprecated in pkg-plist. Suggest it is probably easier to
build this with "make install && make makeplist > pkg-plist". Note that you
should check the plist looks correct, and also delete the top warning line
from the generated file.

5. The pkg-descr file should be updated to include a better description of
the package, and link to the website.

6. Before submitting a port, check that it passes the normal checks by
installing the ports-mgmt/portlint program, and running "portlint -AC" in
the port directory.

7. If you have access to a poudriere installation, you should submit the
"poudriere testport" logs showing that this port will build successfully.
Myself or other ports contributors/committers can help with this if you do
not have access to a poudriere installation, but please make sure you have
at least tested the build on FreeBSD with a "make install".

Much of this is covered in the porter's handbook. It's a good read if you
haven't already seen it. You can find it here:
https://www.freebsd.org/doc/en/books/porters-handbook/book.html

Note that if you re-submit patches to each bug report, be sure to tick the
option that it obsolete's the previous patch.

Good luck! :)

Regards,
Ben

On Mon, Apr 13, 2015 at 7:05 PM Piotr Robert Konopelko <
piotr.konope...@moosefs.com> wrote:

>  Thank you very much for this information.
>
>
>
> I posted requests to the FreeBSD bugzilla:
>
>
>
>
> https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=moosefs&list_id=56910
>
>
>
>
>
> --
>
> Best regards,
>
> Piotr Robert Konopelko
>
> MooseFS Technical Support Engineer | moosefs.com
>
>
>
>
> On Thursday 09 of April 2015 2:52:32 PM Ben Woods wrote:
>
> Those ports currently have their maintainer fields set to "
> po...@freebsd.org", meaning there is no maintainer.
>
> When you submit the bug report and attach your patch to update the port,
> simply ensure the maintainer email address is updated to your own. You will
> then be volunteering as the maintainer for those ports.
>
> Regards,
> Ben
>
> On Thu, 9 Apr 2015 at 9:12 pm Fernando Apesteguía <
> fernando.apesteg...@gmail.com> wrote:
>
> El 09/04/2015 15:00, "Piotr Robert Konopelko"  >
> escribió:
> >
> > Dear FreeBSD Ports team,
> >
> > On FreeBSD Ports site only ports for MooseFS 1.6.27-5 are available:
> > https://www.freebsd.org/cgi/ports.cgi?query=moosefs&stype=all[1]
> >
> > Longer than a half year ago MooseFS 2.0 has been released and few days
> ago - MooseFS
> > 3.0.
> >
> > We would like to inform, that we have prepared ports for MooseFS versions
> 2.0 and 3.0.
> >
> > How is the way to upgrade them in FreeBSD ports tree?
>
> You can start here:
>
> https://bugs.freebsd.org/bugzilla/
>
> And file a request
>
> > Is there a possibility to make our team the maintainer of the MooseFS
> FreeBSD Ports?
>
> Since ports@ is the current maintainer, you could file another request and
> see if they are willing to drop mantainership in your favor or ask here :)
>
> >
> >
> > --
> > Best regards,
> > Piotr Robert Konopelko
> > *MooseFS Technical Support Engineer* | moosefs.com[2]
> >
> >
> > 
> > [1] https://www.freebsd.org/cgi/ports.cgi?query=moosefs&stype=all
> > [2] http://moosefs.com
> > ___
> > freebsd-ports@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> >

Re: svn: E130003: The XML response contains invalid XML

[Ben Woods]

I'm not having any issues updating my ports tree with svn right now.

For reference, my configuration:
% freebsd-version -ku
10.1-RELEASE-p9
10.1-RELEASE-p9

% svn info
Path: .
Working Copy Root Path: /usr/ports
URL: https://svn0.us-west.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn0.us-west.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 383989
Node Kind: directory
Schedule: normal
Last Changed Author: robak
Last Changed Rev: 383989
Last Changed Date: 2015-04-14 17:04:54 +0800 (Tue, 14 Apr 2015)

% svn --version
svn, version 1.8.13 (r1667537)
   compiled Apr  4 2015, 06:49:39 on amd64-portbld-freebsd10.1

Copyright (C) 2014 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_svn : Module for accessing a repository using the svn network protocol.
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using
serf.
  - using serf 1.3.8
  - handles 'http' scheme
  - handles 'https' scheme


Regards,
Ben

On Tue, Apr 14, 2015 at 4:55 PM O. Hartmann 
wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Since this morning, updating ports tree via SVN isn't possible anymore, I
> receive :
>
> Updating '.':
> svn: E130003: The XML response contains invalid XML
> *** Error code 1
>
> Stop.
> make: stopped in /usr/ports
>
>
> Can somebody please explain whats happening? the problem occurs on several
> locations here and several CURRENT/10-STABLE boxes
>
> Regards,
>
> O. Hartmann
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJVLNVeAAoJEOgBcD7A/5N8jnsIAJgs1Dslbs4szz4G/w/O6zdC
> 3+KnZ567ock66LhA7SQ3JgdmiqyGIsh5FKS22VWlzeVS8XEiTBrJpzK2y8Q4rNzR
> ByTLBWGRKsxpB2YfDC64M+KhXuYb5H6uneez46ebCiHeaXDVJzUfX36qW+8Yv8rK
> sjjHMJ/5EvOVHobHXAVr0CFIdtN2toh17b+0+TA+lBQfeY8ki/kTl+ZkNsaj+eAI
> Ogrmn7rnB2mY8evgtERaIJqNOWwF17vcjP+KxRqbb7LMBLIho2HEZ/ctQaKCMizK
> 1mQX8ouKB1gfe4m7m6JOKzJHRp0T3jShBCFlgUAb4cIbZgemhxTg0bB5CZ+XZOk=
> =CSBs
> -END PGP SIGNATURE-
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
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"

Maintainer feedback and committer needed to update abiword

[Ben Woods]

Hi everyone,

Could a member of the FreeBSD GNOME team please review the patch I have
attached to PR199156? It updates abiword to 3.0.1 (which now uses GTK3).

It also fixes the issues reported in PR 195452, PR193318, PR199544.

Lastly, editors/abiword-docs should also be updated in parallel. There is a
patch for that under PR199158.

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

Re: pkg-static: Insufficient privileges to add packages

[Ben Woods]

That error is generated in the pkg exec_add function in src/add.c here:
https://github.com/freebsd/pkg/blob/master/src/add.c

It occurs because it checks the package database for read, write, create
access using the pkgdb_access and pkgdb_check_access functions in
libpkg/pkgdb.c
here:
https://github.com/freebsd/pkg/blob/master/libpkg/pkgdb.c

I believe this is inside the jail created by poudriere testport. It would
be interesting to add the -i interactive flag to the testport run and check
the permissions on/in the pkg database. Mine are here for reference:
% ls -lah /var/db/pkg/
total 37484
drwxr-xr-x   2 root  wheel 8B 21 Apr 06:00 .
drwxr-xr-x  13 root  wheel19B 21 Apr 06:13 ..
-rw-r--r--   1 root  wheel   246B  4 Dec 06:22 FreeBSD.meta
-rw-r--r--   1 root  wheel11M 21 Apr 06:00 local.sqlite
-rw-r--r--   1 root  wheel   246B 21 Apr 03:05 poudriere.meta
-rw-r--r--   1 root  wheel49M  4 Dec 06:22 repo-FreeBSD.sqlite
-rw-r--r--   1 root  wheel   1.6M 21 Apr 03:05 repo-poudriere.sqlite
-r--r--r--   1 root  wheel   3.3M 21 Apr 03:17 vuln.xml

Regards,
Ben


On Tue, Apr 21, 2015 at 4:02 AM Dan Langille  wrote:

> I am running a testport on www/py-django-tastypie
>
> My goal it to add an option for using www/django16 as well as www/django
> (1.7).
>
> The error I get is:
>
> $ sudo poudriere testport -v -j 101amd64 -p testing -z testing -i -o
> www/py-django-tastypie
> ...
> ===>Verifying install for py27-django>=1.5 in
> /usr/ports/www/py-django16
> ===>   Installing existing package /packages/All/py27-django16-1.6.11.txz
> pkg-static: Insufficient privileges to add packages
>
> But because I'm running testport interactively, I see I can install the
> port it mentions:
>
> root@101amd64-testing-testing:~ # pkg install
> /packages/All/py27-django16-1.6.11.txz
> Updating local repository catalogue...
> [101amd64-testing-testing] Fetching meta.txz: 100%816 B   0.8kB/s
> 00:01
> [101amd64-testing-testing] Fetching packagesite.txz: 100%   50 KiB
> 51.4kB/s00:01
> Processing entries: 100%
> local repository update completed. 205 packages processed.
> Updating database digests format: 100%
> Checking integrity... done (0 conflicting)
> The following 1 package(s) will be affected (of 0 checked):
>
> New packages to be INSTALLED:
> py27-django16: 1.6.11
>
> The process will require 27 MiB more space.
>
> Proceed with this action? [y/N]: y
> [101amd64-testing-testing] [1/1] Installing py27-django16-1.6.11...
> [101amd64-testing-testing] [1/1] Extracting py27-django16-1.6.11: 100%
> root@101amd64-testing-testing:~ #
>
>
> Why does the testport fail?
>
> Full build log here:
> http://services.unixathome.org/poudriere/data/101amd64-testing-testing/2015-04-20_19h53m23s/logs/errors/py27-django-tastypie-0.12.1.log
>
>
>
> —
> Dan Langille
> http://langille.org/
>
>
>
>
>
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg-static: Insufficient privileges to add packages

[Ben Woods]

Hand on a minute now my poudriere system is doing the same thing -
looks like we have a bug somewhere.

I am running pkg 1.5.1 and poudriere 3.1.4. According to freshports, pkg
was updated on 16th April, and poudriere on 10th April.

Inside my poudriere testport jail (using the -i interactive mode flag), I
have:
# ls -lah /var/db/pkg/
total 7953
drwxr-xr-x   2 root  wheel 3B Apr 20 23:17 .
drwxr-xr-x  12 root  wheel14B Apr 20 23:17 ..
-rw-r--r--   1 root  wheel   7.7M Apr 20 23:17 local.sqlite

Thoughts?

On Tue, Apr 21, 2015 at 6:56 AM Ben Woods  wrote:

> That error is generated in the pkg exec_add function in src/add.c here:
> https://github.com/freebsd/pkg/blob/master/src/add.c
>
> It occurs because it checks the package database for read, write, create
> access using the pkgdb_access and pkgdb_check_access functions in 
> libpkg/pkgdb.c
> here:
> https://github.com/freebsd/pkg/blob/master/libpkg/pkgdb.c
>
> I believe this is inside the jail created by poudriere testport. It would
> be interesting to add the -i interactive flag to the testport run and check
> the permissions on/in the pkg database. Mine are here for reference:
> % ls -lah /var/db/pkg/
> total 37484
> drwxr-xr-x   2 root  wheel 8B 21 Apr 06:00 .
> drwxr-xr-x  13 root  wheel19B 21 Apr 06:13 ..
> -rw-r--r--   1 root  wheel   246B  4 Dec 06:22 FreeBSD.meta
> -rw-r--r--   1 root  wheel11M 21 Apr 06:00 local.sqlite
> -rw-r--r--   1 root  wheel   246B 21 Apr 03:05 poudriere.meta
> -rw-r--r--   1 root  wheel49M  4 Dec 06:22 repo-FreeBSD.sqlite
> -rw-r--r--   1 root  wheel   1.6M 21 Apr 03:05 repo-poudriere.sqlite
> -r--r--r--   1 root  wheel   3.3M 21 Apr 03:17 vuln.xml
>
> Regards,
> Ben
>
>
> On Tue, Apr 21, 2015 at 4:02 AM Dan Langille  wrote:
>
>> I am running a testport on www/py-django-tastypie
>>
>> My goal it to add an option for using www/django16 as well as www/django
>> (1.7).
>>
>> The error I get is:
>>
>> $ sudo poudriere testport -v -j 101amd64 -p testing -z testing -i -o
>> www/py-django-tastypie
>> ...
>> ===>Verifying install for py27-django>=1.5 in
>> /usr/ports/www/py-django16
>> ===>   Installing existing package /packages/All/py27-django16-1.6.11.txz
>> pkg-static: Insufficient privileges to add packages
>>
>> But because I'm running testport interactively, I see I can install the
>> port it mentions:
>>
>> root@101amd64-testing-testing:~ # pkg install
>> /packages/All/py27-django16-1.6.11.txz
>> Updating local repository catalogue...
>> [101amd64-testing-testing] Fetching meta.txz: 100%816 B   0.8kB/s
>> 00:01
>> [101amd64-testing-testing] Fetching packagesite.txz: 100%   50 KiB
>> 51.4kB/s00:01
>> Processing entries: 100%
>> local repository update completed. 205 packages processed.
>> Updating database digests format: 100%
>> Checking integrity... done (0 conflicting)
>> The following 1 package(s) will be affected (of 0 checked):
>>
>> New packages to be INSTALLED:
>> py27-django16: 1.6.11
>>
>> The process will require 27 MiB more space.
>>
>> Proceed with this action? [y/N]: y
>> [101amd64-testing-testing] [1/1] Installing py27-django16-1.6.11...
>> [101amd64-testing-testing] [1/1] Extracting py27-django16-1.6.11: 100%
>> root@101amd64-testing-testing:~ #
>>
>>
>> Why does the testport fail?
>>
>> Full build log here:
>> http://services.unixathome.org/poudriere/data/101amd64-testing-testing/2015-04-20_19h53m23s/logs/errors/py27-django-tastypie-0.12.1.log
>>
>>
>>
>> —
>> Dan Langille
>> http://langille.org/
>>
>>
>>
>>
>>
>>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg-static: Insufficient privileges to add packages

[Ben Woods]

>> On Tue, Apr 21, 2015 at 4:02 AM Dan Langille  wrote:
>>>
>>> I am running a testport on www/py-django-tastypie
>>>
>>> My goal it to add an option for using www/django16 as well as www/django
>>> (1.7).
>>>
>>> The error I get is:
>>>
>>> $ sudo poudriere testport -v -j 101amd64 -p testing -z testing -i -o
>>> www/py-django-tastypie
>>> ...
>>> ===>Verifying install for py27-django>=1.5 in
>>> /usr/ports/www/py-django16
>>> ===>   Installing existing package /packages/All/py27-django16-1.6.11.txz
>>> pkg-static: Insufficient privileges to add packages
>>>
>>> But because I'm running testport interactively, I see I can install the
>>> port it mentions:
>>>
>>> root@101amd64-testing-testing:~ # pkg install
>>> /packages/All/py27-django16-1.6.11.txz
>>> Updating local repository catalogue...
>>> [101amd64-testing-testing] Fetching meta.txz: 100%816 B   0.8kB/s
>>> 00:01
>>> [101amd64-testing-testing] Fetching packagesite.txz: 100%   50 KiB
>>> 51.4kB/s00:01
>>> Processing entries: 100%
>>> local repository update completed. 205 packages processed.
>>> Updating database digests format: 100%
>>> Checking integrity... done (0 conflicting)
>>> The following 1 package(s) will be affected (of 0 checked):
>>>
>>> New packages to be INSTALLED:
>>> py27-django16: 1.6.11
>>>
>>> The process will require 27 MiB more space.
>>>
>>> Proceed with this action? [y/N]: y
>>> [101amd64-testing-testing] [1/1] Installing py27-django16-1.6.11...
>>> [101amd64-testing-testing] [1/1] Extracting py27-django16-1.6.11: 100%
>>> root@101amd64-testing-testing:~ #
>>>
>>>
>>> Why does the testport fail?
>>>
>>> Full build log here:
>>> http://services.unixathome.org/poudriere/data/101amd64-testing-testing/2015-04-20_19h53m23s/logs/errors/py27-django-tastypie-0.12.1.log
>>
>>
>> That error is generated in the pkg exec_add function in src/add.c here:
>> https://github.com/freebsd/pkg/blob/master/src/add.c
>>
>> It occurs because it checks the package database for read, write, create
>> access using the pkgdb_access and pkgdb_check_access functions in
>> libpkg/pkgdb.c here:
>> https://github.com/freebsd/pkg/blob/master/libpkg/pkgdb.c
>>
>> I believe this is inside the jail created by poudriere testport. It would
>> be interesting to add the -i interactive flag to the testport run and check
>> the permissions on/in the pkg database. Mine are here for reference:
>> % ls -lah /var/db/pkg/
>> total 37484
>> drwxr-xr-x   2 root  wheel 8B 21 Apr 06:00 .
>> drwxr-xr-x  13 root  wheel19B 21 Apr 06:13 ..
>> -rw-r--r--   1 root  wheel   246B  4 Dec 06:22 FreeBSD.meta
>> -rw-r--r--   1 root  wheel11M 21 Apr 06:00 local.sqlite
>> -rw-r--r--   1 root  wheel   246B 21 Apr 03:05 poudriere.meta
>> -rw-r--r--   1 root  wheel49M  4 Dec 06:22 repo-FreeBSD.sqlite
>> -rw-r--r--   1 root  wheel   1.6M 21 Apr 03:05 repo-poudriere.sqlite
>> -r--r--r--   1 root  wheel   3.3M 21 Apr 03:17 vuln.xml
>>
>> Regards,
>> Ben
>>
>>
>>
>>
>> Hand on a minute now my poudriere system is doing the same thing -
>> looks like we have a bug somewhere.
>>
>> I am running pkg 1.5.1 and poudriere 3.1.4. According to freshports, pkg
>> was updated on 16th April, and poudriere on 10th April.
>>
>> Inside my poudriere testport jail (using the -i interactive mode flag), I
>> have:
>> # ls -lah /var/db/pkg/
>> total 7953
>> drwxr-xr-x   2 root  wheel 3B Apr 20 23:17 .
>> drwxr-xr-x  12 root  wheel14B Apr 20 23:17 ..
>> -rw-r--r--   1 root  wheel   7.7M Apr 20 23:17 local.sqlite
>>
>> Thoughts?
>
> Here's what I have:
>
> Edit /etc/motd to change this login announcement.
> root@101amd64-testing-testing:~ # ls -lah /var/db/pkg/
> total 2991
> drwxr-xr-x   2 root  wheel 3B Apr 21 13:28 .
> drwxr-xr-x  10 root  wheel12B Mar 14 19:18 ..
> -rw-r--r--   1 root  wheel   2.8M Apr 21 13:28 local.sqlite
> root@101amd64-testing-testing:~ #
>
> —
> Dan Langille
> http://langille.org/

For the record, downgrading pkg to 1.4.12 and poudriere to 3.1.2 did
not fix this issue for me.

The port that I am trying to testport on FreeBSD 10.1 is
math/plplot-ada. The testport permission issues do not occur with the
port as it is currently - only after making the changes I have
proposed to math/plplot here:
https://bugs.freebsd.org/bugzilla/attachment.cgi?id=155771&action=diff
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg-static: Insufficient privileges to add packages

[Ben Woods]

On Wednesday, April 22, 2015, Baptiste Daroussin  wrote:

> On Tue, Apr 21, 2015 at 11:44:01PM +0800, Ben Woods wrote:
> > >> On Tue, Apr 21, 2015 at 4:02 AM Dan Langille  > wrote:
> > >>>
> > >>> I am running a testport on www/py-django-tastypie
> > >>>
> > >>> My goal it to add an option for using www/django16 as well as
> www/django
> > >>> (1.7).
> > >>>
> > >>> The error I get is:
> > >>>
> > >>> $ sudo poudriere testport -v -j 101amd64 -p testing -z testing -i -o
> > >>> www/py-django-tastypie
> > >>> ...
> > >>> ===>Verifying install for py27-django>=1.5 in
> > >>> /usr/ports/www/py-django16
> > >>> ===>   Installing existing package
> /packages/All/py27-django16-1.6.11.txz
> > >>> pkg-static: Insufficient privileges to add packages
> > >>>
> > >>> But because I'm running testport interactively, I see I can install
> the
> > >>> port it mentions:
> > >>>
> > >>> root@101amd64-testing-testing:~ # pkg install
> > >>> /packages/All/py27-django16-1.6.11.txz
> > >>> Updating local repository catalogue...
> > >>> [101amd64-testing-testing] Fetching meta.txz: 100%816 B   0.8kB/s
> > >>> 00:01
> > >>> [101amd64-testing-testing] Fetching packagesite.txz: 100%   50 KiB
> > >>> 51.4kB/s00:01
> > >>> Processing entries: 100%
> > >>> local repository update completed. 205 packages processed.
> > >>> Updating database digests format: 100%
> > >>> Checking integrity... done (0 conflicting)
> > >>> The following 1 package(s) will be affected (of 0 checked):
> > >>>
> > >>> New packages to be INSTALLED:
> > >>> py27-django16: 1.6.11
> > >>>
> > >>> The process will require 27 MiB more space.
> > >>>
> > >>> Proceed with this action? [y/N]: y
> > >>> [101amd64-testing-testing] [1/1] Installing py27-django16-1.6.11...
> > >>> [101amd64-testing-testing] [1/1] Extracting py27-django16-1.6.11:
> 100%
> > >>> root@101amd64-testing-testing:~ #
> > >>>
> > >>>
> > >>> Why does the testport fail?
> > >>>
> > >>> Full build log here:
> > >>>
> http://services.unixathome.org/poudriere/data/101amd64-testing-testing/2015-04-20_19h53m23s/logs/errors/py27-django-tastypie-0.12.1.log
> > >>
> > >>
> > >> That error is generated in the pkg exec_add function in src/add.c
> here:
> > >> https://github.com/freebsd/pkg/blob/master/src/add.c
> > >>
> > >> It occurs because it checks the package database for read, write,
> create
> > >> access using the pkgdb_access and pkgdb_check_access functions in
> > >> libpkg/pkgdb.c here:
> > >> https://github.com/freebsd/pkg/blob/master/libpkg/pkgdb.c
> > >>
> > >> I believe this is inside the jail created by poudriere testport. It
> would
> > >> be interesting to add the -i interactive flag to the testport run and
> check
> > >> the permissions on/in the pkg database. Mine are here for reference:
> > >> % ls -lah /var/db/pkg/
> > >> total 37484
> > >> drwxr-xr-x   2 root  wheel 8B 21 Apr 06:00 .
> > >> drwxr-xr-x  13 root  wheel19B 21 Apr 06:13 ..
> > >> -rw-r--r--   1 root  wheel   246B  4 Dec 06:22 FreeBSD.meta
> > >> -rw-r--r--   1 root  wheel11M 21 Apr 06:00 local.sqlite
> > >> -rw-r--r--   1 root  wheel   246B 21 Apr 03:05 poudriere.meta
> > >> -rw-r--r--   1 root  wheel49M  4 Dec 06:22 repo-FreeBSD.sqlite
> > >> -rw-r--r--   1 root  wheel   1.6M 21 Apr 03:05 repo-poudriere.sqlite
> > >> -r--r--r--   1 root  wheel   3.3M 21 Apr 03:17 vuln.xml
> > >>
> > >> Regards,
> > >> Ben
> > >>
> > >>
> > >>
> > >>
> > >> Hand on a minute now my poudriere system is doing the same thing -
> > >> looks like we have a bug somewhere.
> > >>
> > >> I am running pkg 1.5.1 and poudriere 3.1.4. According to freshports,
> pkg
> > >> was updated on 16th April, and poudriere on 10th April.
> > >>
> > >> Inside my poudriere testport jail (using the -i interactive mode
> flag), I

Re: pkg-static: Insufficient privileges to add packages

[Ben Woods]

On 22 April 2015 at 07:51, Baptiste Daroussin  wrote:
>> >
>> > I found the reason for Dan by checking the logs,  If I could see your own
>> > logs
>> > then I will tell you where you mistake is.
>> >
>> > actually you are having poudriere building as a user (internally to the
>> > jail)
>> > which is a very good thing as it allows to catch things like this :D)
>> >
>> > I mean it is dropping roots priviledges to build, stage and make package.
>> >
>> > but still try to install a dependency there, probably because the
>> > dependency
>> > line you have in your port is buggy. In dan case he was testing if
>> > py27-django>=1.5 but was refering to the www/py-django16 port which result
>> > in a
>> > package named py27-django16 which is not py27-django aka the test will
>> > always
>> > fail and the ports tree will try to reinstall again and again even in
>> > phases
>> > when it cannot due to lack of priviledges
>> >
>> > As a conclusion the bug is in the port you are testing not in pkg, neither
>> > in
>> > poudriere.
>> >
>> > If you show me the logs of your own build I will tell you what is your
>> > mistake.
>> >
>> > Best regards,
>> > Bapt
>> >
>>
>> Thanks for your help Bapt. You are right, it was an issue with the port
>> dependency list. In my case the library had changed from plplotd.so to
>> plplot.so (now without the 'd'). I have fixed that in the LIB_DEPENDS line
>> and the problem is fixed.
>>
>> Trying to debug this issue took some time, because the error message was
>> about permissions and I didn't make the connection was with unsatisfied
>> dependencies.
>>
>> Could we perhaps add an additional check somewhere in the process that
>> informs you the dependencies have not been correctly satisfied? Do you
>> think this extra check belongs in poudriere or the ports infrastructure?
>
> Improvement for that has been added into the ports tree and taken in account 
> by
> poudriere in latest poudriere-devel 3.1.99.20150421_1 by Bryan
>
> Best regards,
> Bapt

Thanks Bapt and Bryan - looks like a helpful change!
___
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 make install in graphics/graphviz : "Compilation failed unexpectedly"

[Ben Woods]

Hi Avinash,

I am able to compile graphics/graphviz fine on my FreeBSD 10.1 amd64 computer.

Can you please let us know what options you had selected, and the
contents of your make.conf file?

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com


On 13 May 2015 at 19:31, Avinash Sonawane  wrote:
> # uname -a
> FreeBSD titanic.rootkea.me
>
>
>
> 10.1-RELEASE FreeBSD 10.1-RELEASE #0
> r274401: Tue Nov 11 21:02:49 UTC 2014
> r...@releng1.nyi.freebsd.org:/
> usr/obj/usr/src/sys/GENERIC  amd64
>
> Hello!
>
> When I say `make install` in graphics/graphviz it says
> "Makefile:2022: recipe for target 'libgv_php_la-gv_php_init.lo' failed
> .
> .
> .
> ===> Compilation failed unexpectedly.
> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
> the maintainer."
>
> Here is the complete log : http://pastebin.com/iLpd0wJg
>
> Then I added "MAKE_JOBS_UNSAFE= YES" in graphics/graphviz/Makefile but
> then it again said the same. i.e.
> "Makefile:2022: recipe for target 'libgv_php_la-gv_php_init.lo' failed"
>
> Here is the complete log after doing MAKE_JOBS_UNSAFE= YES
> http://pastebin.com/6bvMCF0X
>
> Now since x11/gnome3 depends on graphviz I'm not able to compile to
> gnome3 because of this bug in graphviz.
>
> Any pointers will be really helpful?
>
> --
> Avinash Sonawane (RootKea)
> PICT, Pune
> http://rootkea.wordpress.com
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: creating a port for bitcoin/secp256k1

[Ben Woods]

The security category looks about right to me.

I notice the github project doesn't have any releases yet, so you have had
to reference a specific commit. Are they planning on tagging releases at
some point in the future? Perhaps you could encourage them to :)

Regards,
Ben

On Friday, May 15, 2015, Daniel Morante  wrote:

> I've made a port for secp256k1 library that is provided seperatly by the
> Bitcoin developers.  The need was due to some 'altcoins' now requiring it
> when building.I plan on submitting it to the ports tree, but I am
> unsure of the category to use.
>
> My first draft uses the 'security' category.
>
> https://github.com/tuaris/secp256k1-freebsd
>
> Does that seem fitting?
>
>

-- 

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

Re: www/elinks && JavaScript

[Ben Woods]

On Thursday, May 21, 2015, Matthias Apitz  wrote:

> El día Wednesday, May 20, 2015 a las 06:22:46PM +0300, Beat Gätzi escribió:
>
> > > I'm trying to use ports/www/elinks and to configure it to understand
> > > JavaScript, but it does not; for example this test page
> > >
> > > elinks http://javatester.org/javascript.html
> > >
> > > says that JS is not enabled; I think it is. It has it in the options
> > > compiled for:
> >
> > As far as I know elinks uses spidermonkey for javascript. Could
> > you please check if spidermonkey is installed and if yes, please check
> > if it is recognised during configure. Check for something like
> > "ECMAScript (JavaScript)”.
>
> $ pkg info spidermonke*
> spidermonkey17-1.7.0_1
>
> $ pkg info spidermonke*
> spidermonkey17-1.7.0_1
>
> $ pwd
> /usr/ports/www/elinks/work/elinks-0.11.7
> $ grep -i ECMAScript config.*
> config.h:/* Define if you want: ECMAScript (JavaScript) support */
> config.h:#define CONFIG_ECMASCRIPT 1
> config.h.in:/* Define if you want: ECMAScript (JavaScript) support */
> config.h.in:#undef CONFIG_ECMASCRIPT
> config.log:| #define CONFIG_ECMASCRIPT 1
> config.log:| #define CONFIG_ECMASCRIPT 1
> config.log:| #define CONFIG_ECMASCRIPT 1
> config.log:| #define CONFIG_ECMASCRIPT 1
> config.log:| #define CONFIG_ECMASCRIPT 1
> config.log:| #define CONFIG_ECMASCRIPT 1
> config.log:| #define CONFIG_ECMASCRIPT 1
> config.log:| #define CONFIG_ECMASCRIPT 1
> config.log:| #define CONFIG_ECMASCRIPT 1
> config.log:| #define CONFIG_ECMASCRIPT 1
> config.log:CONFIG_ECMASCRIPT='yes'
> config.log:#define CONFIG_ECMASCRIPT 1
> config.status:s,@CONFIG_ECMASCRIPT@,|#_!!_#|yes,g
> config.status:s,^\([ #]*\)[^ ]*\([   ]*CONFIG_ECMASCRIPT\)[
> (].*,\1define\2 1 ,
>
> I saw it as well while making it:
>
> # make
> ...
> The following feature summary has been saved to features.log
> Feature summary:
> Documentation Tools . Pod2HTML
> Manual Formats .. no
> Man Page Formats  no
> ...
> ECMAScript (JavaScript) . SpiderMonkey
> Browser scripting ... SpiderMonkey
> ...
>
> Thanks
>
> matthias
>

Can you please check if the SPIDERMONKEY option was enabled when your
package was built?
$ pkg info elinks | grep SPIDERMONKEY

It is disabled in the default configuration and therefore in the normal
FreeBSD package sets. You may need to compile that one from ports (or
better yet your own poudriere) and enable the SPIDERMONKEY option when you
do.

Regards,
Ben


-- 

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

Re: SOLVED: pkg version mismatch [succeeds port...]

[Ben Woods]

On Monday, June 1, 2015, Jeffrey Bouquet via freebsd-ports <
freebsd-ports@freebsd.org> wrote:

> I noticed the ports tree here had net/uget 1.10.4_1 even after "svn up"...
> while
> pkg upgrading installed 2.0.  "pkg version" (one of 3 ways) reported
> "succeeds port"... was about to post a question about pkg, but it can be
> fixed
> by
>
> cd /usr/ports/net/uget
> svn revert . -R
>

That command will revert any local changes you have made to the port files
(if you edited them manually, it reverts them to the official version from
FreeBSD ports).

I guess it is not documented within pkg(8) as it has nothing to do with
pkg. It's purely related to how subversion deals with local modifications
to repository files.

For more documentation on the subversion command, you can check:
$ svn help revert

Regards,
Ben


-- 

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

Re: Conflict with pkgconf/pkg-config

[Ben Woods]

On Tuesday, June 2, 2015, Dave Horsfall  wrote:

> ===>   cups-client-1.7.3_2 depends on executable: pkgconf - not found
> ===>Verifying install for pkgconf in /usr/ports/devel/pkgconf
> ===>  Installing for pkgconf-0.9.7
> ===>  Checking if pkgconf already installed
> ===>   Registering installation for pkgconf-0.9.7 as automatic
> pkg-static: pkgconf-0.9.7 conflicts with pkg-config-0.25_1 (installs files
> into the same place).  Problematic file: /usr/local/bin/pkg-config
> *** [fake-pkg] Error code 70
>

This entry from /usr/ports/UPDATING has your answer:

20120726: AFFECTS: users of devel/pkg-config AUTHOR: b...@freebsd.org
devel/pkg-config
has been replaced by devel/pkgconf # portmaster -o devel/pkgconf
devel/pkg-config or # portupgrade -fo devel/pkgconf pkg-config-\* pkgng: #
pkg set -o devel/pkg-config:devel/pkgconf # pkg install -f devel/pkgconf

Regards,
Ben


-- 

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

net/samba41 4.1.18 fails to build with MAKE_JOBS

[Ben Woods]

Since net/samba41 was updated to 4.1.18, it has been failing to build
in poudriere with MAKE_JOBS (when /usr/local/etc/poudriere.conf has
ALLOW_MAKE_JOBS_PACKAGES=samba*).

The issue is a stage-runaway (>> Killing runaway build after 7200
seconds with no output).

The failing poudriere logs for version 4.1.18 with MAKE_JOBS can be found here:
http://woodsb02.no-ip.org/poudriere/data/101amd64-default/2015-06-02_01h00m00s/logs/errors/samba41-4.1.18.log


However, if I do not allow MAKE_JOBS, then 4.1.18 builds fine:
http://woodsb02.no-ip.org/poudriere/data/11amd64-default/2015-06-03_22h00m32s/logs/samba41-4.1.18.log


Version 4.1.17 used to build fine with MAKE_JOBS:
http://woodsb02.no-ip.org/poudriere/data/101amd64-default/2015-05-20_01h00m00s/logs/samba41-4.1.17.log


Any ideas? If it makes any difference, poudriere will be using 8
parallel jobs when MAKE_JOBS is allowed.

Regards,
Ben
___
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/samba41 4.1.18 fails to build with MAKE_JOBS

[Ben Woods]

On Monday, June 8, 2015, Timur I. Bakeyev  wrote:

> I didn't experience anything like this on my test build but I can point to
> the few places, that make 4.1.18 port different from 4.1.17.
>
> I've, possibly wrongly, added 'fakeroot' facility to the USES line. For me
> it worked fine, but I've tested in the live environment and it may behave
> strangly in poudre. In general, the need for 'fakeroot' is questionable, so
> if you can remove it and verify port build in poudre it would be nice.
>


Yep, fakeroot seems to be the problem. I did nothing but remove fakeroot
from the USES= line and samba41 is back to building in 13 minutes.

Poudriere logs here:
http://woodsb02.no-ip.org/poudriere/data/11amd64-default/2015-06-08_06h40m18s/logs/samba41-4.1.18.log


Regards,
Ben


-- 

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

Update editors/abiword

[Ben Woods]

Can I ask for a  ports committer to please review and commit my patch to
update editors/abiword to 3.0.1?

The maintainer timeout has long since passed, and I have not been able to
get any feedback from freebsd-gnome@.

2 bug reports need committing:
PR199156: Updates abiword to 3.0.1 (which now uses GTK3).
PR199158: Updates the related editors/abiword-docs to 3.0.1.

The patches attached to the above 2 bug reports also include fixes for the
issues reported in PR 195452, PR193318, PR199544. (These 3 bugs reports can
be closed once the top 2 bug reports are committed).

Thanks,
Ben


-- 

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

cmake fails if OSVERSION set in /etc/make.conf

[Ben Woods]

Hi everyone,

Yesterday I was having difficulty building a port in a jailed
environment (I am using iocage to create a FreeBSD 10.1 amd64 jail).

After a fair bit of investigation, suspecting either the port or clang
to be at fault due to the error message, I realised that cmake fails
to build a port if OSVERSION is set in /etc/make.conf.

I am confident it is not a problem with the port, as I have seen this
error message in two separate ports (output of trying to build lang/io
and science/InsightToolkit is below).

Why did I have OSVERSION set? I can't remember exactly why, but I must
have been having a problem building ports in the FreeBSD 10.1 jail on
my FreeBSD current host, and would have followed the advice in this
notice in /usr/ports/CHANGES:

20140930:
AUTHOR: bdrew...@freebsd.org

 Building ports in a chroot or jail have always required a particular
 environment be setup. This was not clear though and the ports framework
 did not enforce it. These requirements are:
 1. Either a SRC_BASE/sys/sys/param.h, or /usr/include/sys/param.h be
 present with the __FreeBSD_version_ number of the target system,
 or OSVERSION be set in the environment. Lack of these would fallback
 on kern.osreldate before, which is no longer the case.
 2. UNAME_r,UNAME_v,UNAME_s all must be set for the target system.

 Not having these values in sync will now cause the build to error until it is
 resolved.

 Setting these in the environment can be done via your own wrapper scripts,
 or /etc/login.conf (along with cap_mkdb /etc/login.conf) or
 via /etc/make.conf using appropriate values. Note that OSVERSION is redundant
 if a proper param.h is in the environment:

 OSVERSION+= 1100036
 UNAME_ENV+= OSVERSION=${OSVERSION}
 UNAME_ENV+= UNAME_s=FreeBSD
 UNAME_ENV+= UNAME_r=11.0-CURRENT
 UNAME_ENV+= UNAME_v="${UNAME_s} ${UNAME_r}"
 .MAKEFLAGS: ${UNAME_ENV}
 MAKE_ENV+=  ${UNAME_ENV}
 CONFIGURE_ENV+= ${UNAME_ENV}
 SCRIPTS_ENV+=   ${UNAME_ENV}


Has anyone else come across this? What are the thoughts?

Regards,
Ben


*** FULL CONTENTS OF /ETC/MAKE.CONF INSIDE JAIL ***
WRKDIRPREFIX=/var/ports
DISTDIR=/var/ports/distfiles
PACKAGES=/var/ports/packages
INDEXDIR=/var/ports
USE_PACKAGE_DEPENDS_ONLY=yes
DEVELOPER=yes
#WITH_DEBUG=yes
OSVERSION+= 1001000
UNAME_ENV+= OSVERSION=${OSVERSION}
UNAME_ENV+= UNAME_s=FreeBSD
UNAME_ENV+= UNAME_r=10.1-RELEASE
UNAME_ENV+= UNAME_v="${UNAME_s} ${UNAME_r}"
.MAKEFLAGS: ${UNAME_ENV}
MAKE_ENV+=  ${UNAME_ENV}
CONFIGURE_ENV+= ${UNAME_ENV}
SCRIPTS_ENV+=   ${UNAME_ENV}




*** OUTPUT WHEN TRYING TO BUILD SCIENCE/INSIGHTTOOLKIT ***
root@jail:/usr/ports/science/InsightToolkit # make
===>   InsightToolkit-4.8.0 depends on file: /usr/local/bin/cmake - found
===>  Configuring for InsightToolkit-4.8.0
===>  Performing out-of-source build
/bin/mkdir -p /var/ports/usr/ports/science/InsightToolkit/work/.build
-- The C compiler identification is Clang 3.4.1
-- The CXX compiler identification is Clang 3.4.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- broken
CMake Error at /usr/local/share/cmake/Modules/CMakeTestCCompiler.cmake:61
(message):
  The C compiler "/usr/bin/cc" is not able to compile a simple test program.

  It fails with the following output:

   Change Dir: 
/var/ports/usr/ports/science/InsightToolkit/work/.build/CMakeFiles/CMakeTmp



  Run Build Command:"/usr/bin/make" "cmTryCompileExec2149568943/fast"

  /usr/bin/make -f CMakeFiles/cmTryCompileExec2149568943.dir/build.make
  CMakeFiles/cmTryCompileExec2149568943.dir/build

  /usr/local/bin/cmake -E cmake_progress_report
  
/var/ports/usr/ports/science/InsightToolkit/work/.build/CMakeFiles/CMakeTmp/CMakeFiles
  1

  Building C object
  CMakeFiles/cmTryCompileExec2149568943.dir/testCCompiler.c.o

  /usr/bin/cc -O2 -pipe -fstack-protector -fno-strict-aliasing -o
  CMakeFiles/cmTryCompileExec2149568943.dir/testCCompiler.c.o -c
  
/var/ports/usr/ports/science/InsightToolkit/work/.build/CMakeFiles/CMakeTmp/testCCompiler.c


  Linking C executable cmTryCompileExec2149568943

  /usr/local/bin/cmake -E cmake_link_script
  CMakeFiles/cmTryCompileExec2149568943.dir/link.txt --verbose=1

  /usr/bin/cc -O2 -pipe -fstack-protector -fno-strict-aliasing
  -fstack-protector
  CMakeFiles/cmTryCompileExec2149568943.dir/testCCompiler.c.o -o
  cmTryCompileExec2149568943



  make[2]: stopped in
  /var/ports/usr/ports/science/InsightToolkit/work/.build/CMakeFiles/CMakeTmp


  make[2]: don't know how to make 1001000.  Stop





  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:14 (project)


-- Configuring incomplete, errors occurred!
See also 
"/var/ports/usr/ports/science/InsightToolkit/work/.build/CMakeFiles/CMakeOutput.log".
See also 
"/var/ports/usr/ports/science/InsightToolkit/work/.build/CMakeFiles/CMakeError.log".
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/science/InsightToolkit
*** Error code 1

Committer needed for PR199802: update synfigstudio

[Ben Woods]

Hey everyone,

Can a committer please take a look at PR199082, which updates the
following related ports:
graphics/synfigstudio: Update to 1.0
graphics/synfigstudio: Update to 1.0
devel/etl: Update to 0.04.18

It was waiting for 3.5 months on the maintainer (dhn@) but he has
since relinquished his maintainership (I will take it on for these
three now).

Cheers,
Ben

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

Re: Committer needed for PR199802: update synfigstudio

[Ben Woods]

On Tuesday, August 11, 2015, Ben Woods  wrote:

> Hey everyone,
>
> Can a committer please take a look at PR199082, which updates the
> following related ports:
> graphics/synfigstudio: Update to 1.0
> graphics/synfigstudio: Update to 1.0
> devel/etl: Update to 0.04.18
>
> It was waiting for 3.5 months on the maintainer (dhn@) but he has
> since relinquished his maintainership (I will take it on for these
> three now).
>
> Cheers,
> Ben
>

Hey folks,

Are any committers able to help me out with this one?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199802

Regards,
Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: Is there an equivalent of NO_EXTRACT?

[Ben Woods]

On 9 September 2015 at 07:00, Piotr Kubaj  wrote:
> On 09/09/2015 06:44, Don Lewis wrote:
>> If you list the distfiles that you want to have automatically extracted
>> in EXTRACT_ONLY, then it will leave the unlisted ones untouched.
> But I want the other one to properly extract and compile. Does that mean
> I'd have to write my own extract: step?

No need to write your own extract: step. EXTRACT_ONLY will do what you
need. A quote from the Porter's handbook:

5.4.6. EXTRACT_ONLY

If only some of the DISTFILES must be extracted—for example, one of
them is the source code, while another is an uncompressed
document—list the filenames that must be extracted in EXTRACT_ONLY.

DISTFILES= source.tar.gz manual.html
EXTRACT_ONLY= source.tar.gz

When none of the DISTFILES need to be uncompressed, set EXTRACT_ONLY
to the empty string.

EXTRACT_ONLY=


Hope that clears it up for you.

Cheers,
Ben
___
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"

ffmpeg build fails only if being built as a dependency of emby-server

[Ben Woods]

On 9 January 2017 at 23:52, Tsaki Stan  wrote:

> Hello,
>
> even though it's one of the dependencies that fails (ffmpeg), if I install
> it separately it compiles just fine. I'm not quite sure who to contact.
> I've attached the full log if you want to check it out.
>
>
> [root@crystal ~]# uname -a
> FreeBSD crystal 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24
> 06:55:27 UTC 2016 
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
>  amd64
> [root@crystal ~]# cat /etc/make.conf
> OPTIONS_UNSET=X11 OPENGL XCB FONTCONFIG
> multimedia_ffmpeg_SET=LAME OPUS SMB X265
> multimedia_ffmpeg_UNSET=VAAPI VDPAU FREI0R
> graphics_ImageMagick-nox11_UNSET=16BIT_PIXEL PDF
> [root@crystal ~]# pkg leaf
> bash-4.4.5
> dialog4ports-0.1.6
> pkg-1.9.4_1
> portmaster-3.17.9_4
> samba44-4.4.8
> [root@crystal ~]# pkg autoremove
> Checking integrity... done (0 conflicting)
> Nothing to do.
> [root@crystal ~]# make -C /usr/ports/multimedia/emby-server/ install
> clean BATCH=yes 2>&1 | tee -a emby_fail.txt
> ...
> libavcodec/libavcodec.so: undefined reference to `ff_blockdsp_init_x86'
> gmake[2]: *** [Makefile:131: ffprobe_g] Error 1
> gmake[2]: *** Waiting for unfinished jobs
> libavcodec/libavcodec.so: undefined reference to `ff_xvid_idct_init_x86'
> libavcodec/libavcodec.so: undefined reference to `ff_me_cmp_init_x86'
> libavfilter/libavfilter.so: undefined reference to `ff_hqdn3d_init_x86'
> libavcodec/libavcodec.so: undefined reference to `ff_h264_pred_init_x86'
> libavfilter/libavfilter.so: undefined reference to `ff_showcqt_init_x86'
> libavcodec/libavcodec.so: undefined reference to
> `ff_mpegvideoencdsp_init_x86'
> libavfilter/libavfilter.so: undefined reference to `ff_w3fdif_init_x86'
> libavutil/libavutil.so: undefined reference to `ff_get_cpu_flags_x86'
> libavcodec/libavcodec.so: undefined reference to `ff_pixblockdsp_init_x86'
> cc: error: linker command failed with exit code 1 (use -v to see
> invocation)
> gmake[2]: *** [Makefile:131: ffmpeg_g] Error 1
> gmake[2]: Leaving directory '/usr/ports/multimedia/ffmpeg/
> work/ffmpeg-3.2.2'
> ===> Compilation failed unexpectedly.
> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
> the maintainer.
> *** Error code 1
> Stop.
> make[1]: stopped in /usr/ports/multimedia/ffmpeg
> *** Error code 1
> Stop.
> make: stopped in /usr/ports/multimedia/emby-server
> [root@crystal ~]#
>
> This works fine:
> make -C /usr/ports/multimedia/ffmpeg WITH="LAME OPUS SMB X265"
> WITHOUT="VAAPI VDPAU FREI0R" install clean BATCH=yes &&
> make -C /usr/ports/graphics/ImageMagick-nox11 WITHOUT="16BIT_PIXEL PDF"
> installclean BATCH=yes &&
> make -C /usr/ports/multimedia/emby-server install clean BATCH=yes
>
> Am I doing something wrong?
>
> Thanks
>


Hi Tsaki,

Thanks for pointing this out. I use poudriere to build my ports, so I had
never noticed this, but was able to reproduce it today.

Any porters out there have any idea why multimedia/ffmpeg would fail to
build when being built as a dependency of multimedia/emby-server, but not
if it is build directly?

Regards,
Ben
___
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: ffmpeg build fails only if being built as a dependency of emby-server

[Ben Woods]

> On 5 Feb 2017, at 11:48 pm, Jan Beich  wrote:
> 
> Probably a regression from https://svnweb.freebsd.org/changeset/ports/428896
> which would be fixed after 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215401

Indeed, that looks like the issue. Thanks for pointing that out.

Tsaki: looks like it will be fixed soon™.

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

Re: New port gitsome

[Ben Woods]

On Wed, 22 Feb 2017 at 6:52 pm, Danilo G. Baio (dbaio) 
wrote:

> Hi.
>
> I am working on a new port for gitsome[1] which depends on python:3.4-3.5.
>
> But it will fail on FreeBSD poudriere (building infrastructure) because
> some
> of its dependencies (at least 17) won't be build with python 3.
>
> What is the advice here ? Submit for each dependency [2] a py3-\* slave
> port ?
>
> Regards.
>
> [1] - http://dbaio.bs2cloud.com.br/FreeBSD/misc_py-gitsome.patch
>
> [2]
> textproc/py-pygments
> textproc/py-pystemmer
> textproc/py-alabaster
> textproc/py-snowballstemmer
> devel/py-six
> textproc/py-docutils
> devel/py-wcwidth
> graphics/py-imagesize
> textproc/py-sphinx_rtd_theme
> devel/py-colorama
> textproc/py-feedparser
> devel/py-docopt
> devel/py-ply
> textproc/py-sphinx
> net/py-uritemplate
> devel/py-prompt_toolkit
> textproc/py-numpydoc
>
> --
> Danilo G. Baio (dbaio)
>
Hi Danilo,

Apologies in the delay in getting back to you.

Yes, at the moment that is the only way to get a port working which depends
on multiple python3 ports.

Bapt is working on bringing "flavours" to the ports tree, which will allow
each python port to be built multiple times with python2 and python3,
therefore satisfying your dependencies.

However, it is probably not have in the next week or so, so you should go
ahead and make the py3- versions of those ports. It is easy to find and
revert them once flavours exist anyway :)

Before we commit all of those new py3- ports, please make sure you have
tested that it all successfully builds to provide a working gitsome we
don't want to commit them and find out they were not needed after all :)

Regards,
Ben
-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: [CFT] pkg-plist generator

[Ben Woods]

On 26 March 2017 at 01:14, Dominic Fandrey  wrote:

> Since February I have been working on a pkg-plist generator that
> understands and handles options. I believe it is now ready for public
> testing as a part of my bsda2 script collection:
>

Hi Dominic,

Nice idea!

I had a similar idea for adding this functionality to the poudriere
testport command, which I mentioned here:
https://github.com/freebsd/poudriere/issues/303

I never got around to implementing anything though... it staid just an
idea. Looking forward to trying yours.

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
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: Fetching binaries from GitHub

[Ben Woods]

On Sun, 30 Apr 2017 at 10:33 pm, Alexander Moisseev via freebsd-ports <
freebsd-ports@freebsd.org> wrote:

> Is there a way to fetch binaries from GitHub instead of sources?
> In particular I need to fetch BackupPC-4.1.2.tar.gz from
> https://github.com/backuppc/backuppc/releases/tag/4.1.2
>
Hi Alexander,

I believe downloading binaries from GitHub (such as that manually uploaded
source tarball) is only possible only using the normal method for
downloading source binaries in ports (by defining DISTNAME, EXTRACT_SUFX
and MASTER_SITES).

I don't believe there exists any shortcut in the ports framework for
downloading files attached to tagged releases in GitHub.

https://www.freebsd.org/doc/en/books/porters-handbook/makefile-distfiles.html

Regards,
Ben
-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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"

MP3 licensing over - can we remove LAME restrictions?

[Ben Woods]

"On April 23, 2017, Technicolor's mp3 licensing program for certain mp3
related patents and software of Technicolor and Fraunhofer IIS has been
terminated."
http://www.mp3licensing.com/

It seems that the FreeBSD port for LAME could now have the restriction
removed, allowing the packages to be available for users by default.

Perhaps the LAME option could also be enabled by default in ffmpeg?

Thoughts?

Regards,
Ben
-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: MP3 licensing over - can we remove LAME restrictions?

[Ben Woods]

On Tue, 9 May 2017 at 1:07 pm, Koichiro IWAO  wrote:

> Hi,
>
> FYI, MP3 is coming back to Fedora. I think FreeBSD may able to do that.
> https://fedoramagazine.org/full-mp3-support-coming-soon-to-fedora/
>

If this analysis is correct, it sounds like the final patents will expire
by the end of this year?

http://www.tunequest.org/a-big-list-of-mp3-patents/20070226/

Regards,
Ben
-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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"

pkg(8) fails to upgrade to different branches of software

[Ben Woods]

Hi everyone,

The recent change of postgresql default version from 9.3 to 9.5 in r444116
required pkg to replace any postgresql93-* packages with postgresql95-*
packages, and also reinstall any ports which changed their dependency from
the 93 version to the 95 version.

This did not succeed automatically with "pkg upgrade -y" as can be seen
below. I realise the UPDATING entry explained to first remove the old
packages and then install the new packages, but I would like to ask if
there is a way this can be improved so it works automatically, and if there
is a plan in place to improve this?

This problem appears to have 2 issues:
1. pkg is not recognising the CONFLICTS when initially determining the
upgrade path (they are specified in the master port
databases/postgresql92-server/Makefile)
2. once the packages have been fetched and pkg notices the file conflict,
the solver does not decide to remove the pkg with the lower version

# pkg upgrade -y
Updating FreeBSD-ports repository catalogue...
FreeBSD-ports repository is up to date.
All repositories are up to date.
Checking for upgrades (8 candidates):  done
Processing candidates (8 candidates): 
done
The following 9 package(s) will be affected (of 0
checked):

New packages to be INSTALLED:
postgresql95-client: 9.5.7 [FreeBSD-ports]

Installed packages to be UPGRADED:
vim: 8.0.0642 -> 8.0.0670 [FreeBSD-ports]
qt5-script: 5.7.1_1 -> 5.7.1_2 [FreeBSD-ports]
llvm40: 4.0.1.r1_5 -> 4.0.1 [FreeBSD-ports]
libreoffice: 5.3.3_2 -> 5.3.4 [FreeBSD-ports]
gutenprint: 5.2.12_1 -> 5.2.12_2 [FreeBSD-ports]
freebsd-release-manifests: 20170617 -> 20170624 [FreeBSD-ports]

Installed packages to be REINSTALLED:
rubygem-pg-0.21.0 [FreeBSD-ports] (direct dependency changed:
postgresql95-client)
gimp-gutenprint-5.2.12 [FreeBSD-ports] (direct dependency changed:
perl5)

Number of packages to be installed: 1
Number of packages to be upgraded: 6
Number of packages to be reinstalled: 2

The process will require 10 MiB more space.
370 MiB to be downloaded.
[1/9] Fetching vim-8.0.0670.txz: .. done
[2/9] Fetching rubygem-pg-0.21.0.txz: .. done
[3/9] Fetching qt5-script-5.7.1_2.txz: .. done
[4/9] Fetching llvm40-4.0.1.txz: .. done
[5/9] Fetching libreoffice-5.3.4.txz: .. done
[6/9] Fetching gutenprint-5.2.12_2.txz: .. done
[7/9] Fetching gimp-gutenprint-5.2.12.txz: .. done
[8/9] Fetching freebsd-release-manifests-20170624.txz: ... done
[9/9] Fetching postgresql95-client-9.5.7.txz: .. done
Checking integrity... done (1 conflicting)
  - postgresql95-client-9.5.7 [FreeBSD-ports] conflicts with
postgresql93-client-9.3.17 [installed] on /usr/local/bin/clusterdb
Checking integrity... done (0 conflicting)
Conflicts with the existing packages have been found.
One more solver iteration is needed to resolve them.
The following 12 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
postgresql95-client: 9.5.7 [FreeBSD-ports]

Installed packages to be UPGRADED:
gutenprint: 5.2.12_1 -> 5.2.12_2 [FreeBSD-ports]
vim: 8.0.0642 -> 8.0.0670 [FreeBSD-ports]
qt5-script: 5.7.1_1 -> 5.7.1_2 [FreeBSD-ports]
llvm40: 4.0.1.r1_5 -> 4.0.1 [FreeBSD-ports]
libreoffice: 5.3.3_2 -> 5.3.4 [FreeBSD-ports]
freebsd-release-manifests: 20170617 -> 20170624 [FreeBSD-ports]

Installed packages to be REINSTALLED:
pkg-1.10.1 [FreeBSD-ports]
rubygem-pg-0.21.0 [FreeBSD-ports] (direct dependency changed:
postgresql95-client)
gimp-gutenprint-5.2.12 [FreeBSD-ports] (direct dependency changed:
perl5)

Number of packages to be installed: 1
Number of packages to be upgraded: 6
Number of packages to be reinstalled: 3

The process will require 10 MiB more space.
3 MiB to be downloaded.
[1/12] Fetching pkg-1.10.1.txz: .. done
[1/12] Fetching postgresql93-client-9.3.17.txz: .. done
[1/12] Deinstalling postgresql93-client-9.3.17...
Deleting files for postgresql93-client-9.3.17: .. done
[1/12] Upgrading gutenprint from 5.2.12_1 to
5.2.12_2...

Extracting gutenprint-5.2.12_2: .. done
[1/12] Installing postgresql95-client-9.5.7...
Extracting postgresql95-client-9.5.7: .. done
Installing postgresql93-client-9.3.17...
pkg: postgresql93-client-9.3.17 conflicts with
postgresql95-client-9.5.7 (installs files into the same place).
Problematic file: /usr/local/bin/clusterdb



Note that this appears to effectively remove the old postgresql93-client
port, so a subsequent pkg run succeeds:

# pkg info | grep postgres
postgresql95-client-9.5.7  PostgreSQL database (client)
rubygem-postgres_ext-3.0.0 PostgreSQL data types extension for
ActiveRecord
# pkg upgrade
Updating Fre

Re: github repo to port

[Ben Woods]

On Tue, 18 Jul 2017 at 9:54 pm, Athanasios Douitsis 
wrote:

> Hello,
>
> Totally new to ports maintenance, please bear.
>
> Is there a way for a port to be semi-automatically updated from a github
> repo as its source?
>
> I understand that a ports committer (which I am not) must always be present
> in the process, just looking for the optimal way to handle maintenance.
>
> If this has been discussed before, my apologies.
>
> Many thanks,
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
Hi Athanasios,

It's not automatic unfortunately.

The process for updating a port (github or otherwise) is generally:
1. Change PORTVERSION in port Makefile
2. Run make makesum to update distfiles
3. Attempt port build to determine if it works, and if the files it
installs has changed
4. Update pkg-plist with any changes to installed files (make makeplist).
5. Final testing/QA/QC and commit or submit bug report with patch if you
are not a committee

Regards,
Ben
-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: Minor bug in pkg?

[Ben Woods]

On 6 August 2017 at 15:18, Grzegorz Junka  wrote:

> Shouldn't pkg be incrementing the first number when installing/upgrading
> packages?
>
> [1/247] Reinstalling blender-2.78c_3...
> Extracting blender-2.78c_3: 100%
> [1/247] Reinstalling abiword-3.0.1_5...
> Extracting abiword-3.0.1_5: 100%
> [1/247] Upgrading R from 3.4.0_2 to 3.4.1_4...
> Extracting R-3.4.1_4: 100%
> [1/247] Upgrading GraphicsMagick from 1.3.25_3,1 to 1.3.26,1...
> Extracting GraphicsMagick-1.3.26,1: 100%
>


For the record, I have also seen this erroneous behaviour before, but
haven't been able to work out why it only happens some of the time.

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
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: Samba4 needs switch to turn off messages

[Ben Woods]

On Mon, 21 Aug 2017 at 4:16 am,  wrote:

> Whenever there is more than 1 Samba server running in the same
> netbios space, they INCESSANTLY put out the same worthless
> message every 5 minutes exactly, filling up disc space or
> disrupting whatever's happening on the console.
>
> The message always has the same form:
>
> "query name response:  Multiple [n] reponses received on subnet
> [this ip address] for name [netbios group name].  This response
> was from [other ip address]."
>
> This has been a problem for years, but  so far nobody seems to
> know how to stop the damned things.  Log levels appear to have no
> effect on them.
>
> The server needs to have a switch to turn off such messages!
>
> Preferably as a patch, distributed  s o o n.
>
> I'm just before lodging a bug report, because anyone trying to
> construe that message as a feature would be likely to spend time
> in hospital by reason of having herniated their imagination.
> ___
> 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"


Hi scratch,

I recommend asking your question about how these messages can be turned off
on the samba mailing list. For best results, you probably want to leave out
commentary like "worthless messages" and stick to the facts (not that I
disagree with you, just might encourage more discussion).

https://lists.samba.org/archive/samba/

If you don't get much of a response, you could try raising an upstream
samba bug report:

https://bugzilla.samba.org/

Good luck!
-Ben
-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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 ?

[Ben Woods]

On Mon, 25 Sep 2017 at 2:59 pm, Matthew Seaman  wrote:

> On 25/09/2017 12:10, Chris Rees wrote:
> > It's probably harmless to have a file listed twice,
>
> Listing a file twice will get you nasty-grams from the package build
> systems.
>
> Cheers,
>
> Matthew


Thanks Matthew - Interesting.

So what is the solution for this then? I am also curious.

Regards,
Ben

> --

--
From: Benjamin Woods
woods...@gmail.com
___
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: Welcome flavors! portmaster now dead? synth?

[Ben Woods]

On Sat, 2 Dec 2017 at 2:36 am, Carmel NY  wrote:

> > First, welcome flavors. It has been badly needed for a while and is
> going to
> > clean up a couple of messes that have been plaguing the port system for a
> > long time.
> >
> > Second, whither port msanagement tools? At least portmaster now appears
> > dead. Any reason to expect it to be workable again? I have not tried
> synth
> > with flavors, yet,.but I see noting committed to deal with them, so it
> looks
> > like port management has devolved to raw "make" operations or poudriere.
> > Am I missing some other option?
> >
> > I really with there ha been at least a days warning of the flavoring of
> python
> > so I could have set up to do tings a bit more smoothly.
> >
> > Some issues are still unclear. e.g. pygobject3 is orphaned. Since I have
> 23
> > ports that depend on py34-gobject3, I don't see deleting it as viable.
> pkg
> > shows no upgrade path... just "orphaned: devel/py3-gobject3". None of the
> > ports htat depend in it show that they need updates. I'm going to guess
> that I
> > can build the py-gobject3 port with FLAVOR=36 and that will fix a bunch
> of
> > stuff, but I am not really sure. If I rebuild that way, will I break any
> of the
> > ports that previously wanted ry34-gobject3? Don't know, but it will
> break my
> > entire desktop if it fails.
> >
> > I might mention that cython, compat10x, compat9x are also orphaned. This
> > looks pretty ugly. Are they really gone? Or re there flavor here, as
> well?
> > again, pkg gives no clues.
>
> Synth is failing since this change. I get the feeling that, as usually
> happens, nobody
> actually vetted this correctly.
>
> --
> Carmel


Hi Carmel,

My understanding is that poudriere is the only package building system that
is officially supported by the portmgr, apart from raw make.

There are many other nice ports building tools contributed by the
community, which each have their niche market, but the maintenance of those
tools is a community responsibility also.

The announcement of impending flavors and breakage of package building
infrastructure that doesn’t support it was some time ago (I believe at
least 6 months), with a number of reminders since then. If a community
developed and maintained package building tool does not support flavors, I
don’t believe that is the fault of portmgr. I don’t believe FreeBSD could
delay such an important feature to the ports tree any longer.

I welcome the introduction of flavors, think the timing was good (not
immediately before the new quarterly branch), and also hope someone steps
up to update the community maintained package building tools to support it
soon.

Thanks to all those involved in bringing flavors to the ports tree! This is
a great day.

Regards,
Ben

> --

--
From: Benjamin Woods
woods...@gmail.com
___
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"

Bringing SUB-PACKAGES to ports

[Ben Woods]

Hi everyone,

Thank you very much for flavors. It has been long awaited, and will be a
great step forward for FreeBSD.

Onwards and upwards: What is the status of subpackages?

Speaking to bapt at BSDTW, it sounded like flavors was going to be the
difficult change, and subpackages would then be easy.

Given that we are going through the transition to flavors now, and the
ports tools are getting updated to support it, would it be a good idea to
introduce subpackages now also? That way people who are getting familiar
with the changes required to the ports tools can use their new familiarity
whilst it is fresh to support both.

For those that aren’t familiar:
- Flavors: build a port multiple times with different options/dependencies
to create multiple packages
- Subpackages: build a port once and chop the resulting files into multiple
subpackages

https://wiki.freebsd.org/Ports/FlavorsAndSubPackages

Regards,
Ben
-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: Flavors support of portupgrade

[Ben Woods]

On Sat, 9 Dec 2017 at 5:18 pm, Yasuhiro KIMURA  wrote:

> Hello.
>
> Poudriere and synth already support flavors. As for portmaster, Stefan
> Esser (s...@freebsd.org) said he is working now. Then what about
> portupgrade? Is anybody working?
>
> ---
> Yasuhiro KIMURA
> ___
> 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"
>

Hi Yasuhiro,
Bryan Drewery has generously said he plans to look into this over the next
couple of weeks:

https://lists.freebsd.org/pipermail/freebsd-ports/2017-December/111445.html

Regards,
Ben
-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: Keeping your Poudriere dry!

[Ben Woods]

On Wed, 13 Dec 2017 at 7:31 am, blubee blubeeme  wrote:

> This still leaves the other question; Can I make a svn diff from poudriere
> ports tree?
>
If the poudriere ports tree was checked out with svn, then yes. In a shell,
simply cd to the directory, and then type svn diff.

You can check which method was used to create the poudriere ports tree with:
$ poudriere ports -l

The default method for creating a ports tree is portsnap, but at the time
of creating a ports tree this can be overridden with -m:
$ poudriere ports -c -p name -m svn+https

Regards,
Ben
-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: Option vs. flavor?

[Ben Woods]

On Sun, 17 Dec 2017 at 3:29 am, Thierry Thomas  wrote:

> Le sam. 16 déc. 17 à  2:38:51 +0100, Yuri 
>  écrivait :
>
> > One port is small by itself, but it semi-optionally requires 4.5GB of
> > static data installed.
> >
> > It is possible to download this data optionally, conditional on the port
> > option DATA_FILES which will be "off" by default, so that the users who
> > need the data will install it with DATA_FILES=on.
> >
> > Alternatively, it is possible to create a flavor, something like
> @withData.
> >
> >
> > Should the option be preferred, or should the flavor be preferred?
>
> I'd say that this is a case for sub-packages.
> --
> Th. Thomas.
>

I believe Sub-packages would normally still download the data for the port
build (make fetch), but it would not be included main pkg.

The original post was requesting that the port make fetch only downloads
the data conditionally based on the option. Not sure how possible that is.

Regards,
Ben
-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: Option vs. flavor?

[Ben Woods]

On Sun, 17 Dec 2017 at 8:29 am, Yuri  wrote:

> On 12/16/17 11:14, Ben Woods wrote:
> > The original post was requesting that the port make fetch only downloads
> > the data conditionally based on the option. Not sure how possible that
> is.
>
>
> Yes, I was in doubt too. sub-packages will probably always fetch and
> build, and I am trying to avoid that.
>
> So I would just stick to flavor. @withData should be a virtual flavor,
> that can be built on demand.
>
> IMO, this makes most sense.
>
>
> Yuri


Hi Yuri,

Is there any reason why you want to avoid the download with the port “make
fetch”?

This should not impact you if it uses subpackages and you just install the
program with pkg.

Regards,
Ben

> --

--
From: Benjamin Woods
woods...@gmail.com
___
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/vinagre

[Ben Woods]

On Wed, 21 Feb 2018 at 5:46 am, The Doctor  wrote:

> Yet again
>
> The port is at 3.18
>
> yet the newest version is 3.22 .
>
> What gives?


This is maintained by the gnome team, and all of the gnome ports are
currently at version 3.18. They have historically been updated together to
we move from release to release for the entire gnome system, rather than
per port.

That being said, graphics/evince has just been updated to version 3.26...
so if newer versions of vinagre are tested and found to work without
updating the entire gnome system, then new versions of vinagre can be
included in ports.

Are you able to do some testing and provide a patch?

Cheers,
Ben

> --

--
From: Benjamin Woods
woods...@gmail.com
___
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: Syslog Example For InfluxDB Port

[Ben Woods]

On Thu, 22 Mar 2018 at 5:49 am, Pete Wright  wrote:

> Interestingly enough I'm unable to get log messages to end up in
> /var/log/influxdb/influxd.log.  When I manually run daemon, without any
> syslog flags passed, I do see plenty of logs ending up in stdout tho.
> I'm guessing I'm tired and missing something obvious - any other
> influxdb people have logging working as expected?


Sorry to ask a basic question, but have you made sure that the file
/var/log/influxd/influxdb.log exists, so that syslog can write to it?

Can you provide the entire contents your /etc/syslog.conf file, and the
relevant included files?

Regards,
Ben
-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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 checksum mismatch for a variety of ports

[Ben Woods]

Sorry for missing this earlier.

This has now been resolved by commit r504347:
https://svnweb.freebsd.org/ports?view=revision&revision=504347

Thanks for the tip Tijl.

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com


On Wed, 15 Mar 2017 at 23:34, Tijl Coosemans  wrote:

> On Wed, 15 Mar 2017 14:55:00 + tech-lists 
> wrote:
> > Hello ports@,
> >
> > What's the significance of this and what can I do about it? Deinstalling
> > and reinstalling doesn't help. These were installed with ports r436245
> > on 11.0-stable r314138:
> >
> > # pkg check -s
> >
> > Checking all packages:   3%
> > bluefish-2.2.10: checksum mismatch for
> > /usr/local/share/applications/mimeinfo.cache
> > bluefish-2.2.10: checksum mismatch for
> /usr/local/share/mime/XMLnamespaces
> > bluefish-2.2.10: checksum mismatch for /usr/local/share/mime/aliases
> > bluefish-2.2.10: checksum mismatch for
> /usr/local/share/mime/generic-icons
> > bluefish-2.2.10: checksum mismatch for /usr/local/share/mime/globs
> > bluefish-2.2.10: checksum mismatch for /usr/local/share/mime/globs2
> > bluefish-2.2.10: checksum mismatch for /usr/local/share/mime/icons
> > bluefish-2.2.10: checksum mismatch for /usr/local/share/mime/magic
> > bluefish-2.2.10: checksum mismatch for /usr/local/share/mime/mime.cache
> > bluefish-2.2.10: checksum mismatch for /usr/local/share/mime/subclasses
> > bluefish-2.2.10: checksum mismatch for /usr/local/share/mime/treemagic
> > bluefish-2.2.10: checksum mismatch for /usr/local/share/mime/types
> > Checking all packages:   4%
> > calibre-2.81.0: checksum mismatch for
> > /usr/local/share/mime/application/epub+zip.xml
> > calibre-2.81.0: checksum mismatch for
> > /usr/local/share/mime/application/x-mobipocket-ebook.xml
> >
> > thanks
>
> It's a problem with the packaging.  "--disable-update-databases" should
> be added to CONFIGURE_ARGS in www/bluefish/Makefile.
>
___
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: head -r355027 context, poudiere jail constructions with the likes of -a arm64.aarch64 -x : awk: can't open file /sys/param.h

[Ben Woods]

On Sun, 24 Nov 2019 at 1:27 pm, Mark Millard  wrote:

> My poudiere jail constructions with the likes of -a arm64.aarch64 -x are
> all getting:
>
> awk: can't open file /sys/param.h
>  source line number 1


Hi Mark,

I have been getting this same error on amd64 for some time when I use the
command below.
# poudriere jail -j 13amd64 -u -m src=/usr/src

Any ideas what it could be?

Regards,
Ben

> --

--
From: Benjamin Woods
woods...@gmail.com
___
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: 2020Q1 and firefox/thunderbird

[Ben Woods]

On Tue, 10 Mar 2020 at 03:37, Boris Samorodov  wrote:

> Hi all,
>
> There are no firefox/thunderbird ports at the
> quarterly repository. Is there any ETA to fix this?
>
>
Hi Boris,

I believe this problem was caused by commit r527969 to the quarterly ports
branch:
https://svnweb.freebsd.org/ports?view=revision&revision=527969

The broken firefox ports problem was subsequently pointed out by kevans
here:
https://lists.freebsd.org/pipermail/svn-ports-branches/2020-March/008270.html

The problem was then fixed by jbeich in r528114:
https://svnweb.freebsd.org/ports?view=revision&revision=528114

Long story short: if the above is correct, I believe the problem should be
rectified after the next pkg build run for the quarterly branch (next
couple of days).

Regards,
Ben
___
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"

Committer needed: Update multimedia/emby-server

[Ben Woods]

Hey everyone,

Are any committers able to have a look at this simple PR for me?

It a run of the mill update of multimedia/emby-server which has been
waiting a couple of weeks:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202928

Thanks for your help.

-Ben

--
From: Benjamin Woods
woods...@gmail.com
___
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: Committer needed: Update multimedia/emby-server

[Ben Woods]

On Wednesday, 23 September 2015, Kurt Jaeger  wrote:

> Hi!
>
> > Are any committers able to have a look at this simple PR for me?
> >
> > It a run of the mill update of multimedia/emby-server which has been
> > waiting a couple of weeks:
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202928
>
> Done. I took the liberty to upgrade to 3.0.5724.5 (not .4).
>

Thanks - I hadn't even spotted the .5 release yet :)

Cheers,
Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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"

Committer needed for PR201175: Update graphics/synfigstudio to 1.0.1

[Ben Woods]

Hi guys and gals,

Are there any ports committers that could take a look at this bug report please?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201175

It updates the following related ports with one patch:
devel/etl: Update from 0.04.18 to 0.04.19
devel/synfig: Update from 1.0 to 1.0.1
graphics/synfigstudio: Update from 1.0 to 1.0.1

It also implements some improvements to the above ports recommended by
user tkato...@yahoo.com

Thanks in advance!
-Ben

--
From: Benjamin Woods
woods...@gmail.com
___
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: Committer needed for PR201175: Update graphics/synfigstudio to 1.0.1

[Ben Woods]

On Friday, 2 October 2015, Kurt Jaeger  wrote:

> Hi!
>
> > graphics/synfigstudio fails to build on 9.3-amd64, see the build-log at
> >
> >
> http://people.freebsd.org/~pi/logs/graphics__synfigstudio-93a-1443720936.txt
> >
> > Everything else builds fine. Any quick fix ?
>
> One quick fix: If you as maintainer declare it as broken on 9,
> we can commit the update and work on the fix later.
>
> Just sayin' 8-}
>

Hi Kurt,

Yes, as maintainer I can confirm this is broken on FreeBSD 9. I am
continuing to investigate, as per my comments at the end of PR199802, but
this will not be a quick fix.

Can we please commit this as is, and declare this broken on FreeBSD 9 amd64?

Regards,
Ben



-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: How to debug a Mk-Script?

[Ben Woods]

On Monday, 19 October 2015, Torsten Zuehlsdorff <
mailingli...@toco-domains.de> wrote:

> Hello,
>
> after defining a USES pgsql:9.3+ in an port-update i stumbled over this
> error message:
>
> the port wants postgresql-client version 9.3 9.4 and you have version 9.4
> installed.
>
> This seems to be an error in Mk/Uses/pgsql.mk which i found to track down
> (in order to gather some more experience).
>
> While i have already an idea what the case can be, i just want to add some
> output into the script. How is this possible? Can someone guide me please?
>
> Thanks,
> Torsten
>

If you just want to know the value that a variable  is being assigned, you
can run the following command at the console the print it out:
$ make -V YOURVARIABLEHERE

This doesn't let you choose where in the flow of the Makefile is the
variable changing, only once the whole Makefile has been parsed.

Regards,
Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: Poudriere, build older version of port

[Ben Woods]

On 30 November 2015 at 21:48, Frank de Bot (lists) 
wrote:

> Hi,
>
> I have some issue with a certain port version update. If I downgrade
> this port everything works well.
>
> I use poudriere to build my own packages with own options. Is it
> possible with poudriere to stick to a certain revision of a port?
>
>
> Regards,
>
> Frank de Bot
>

Yes, you just maintain a ports tree with your custom version of the port.
Depending on how you are updating your ports tree for the poudriere builds,
you may need to make sure it is not overwriting your local changes. You
might be better copying the port to a new port in your local tree, so any
changes to the actual one don't over-write your local changes.

However, I am not sure this is the best idea. If there is a problem with
the port, you should probably either raise a bug report or get in contact
with the port maintainer (you can see who maintains the port using
freshports.org or by looking in the Makefile. If you keep a custom port and
it stops working in the future, you will be on your own. If you report the
problem and get it fixed for everyone, you can enjoy the new port updates
and fixes as they become available in the future.

Regards,
Ben
___
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: How do I use "USES=shebangfix"

[Ben Woods]

On Tuesday, 8 December 2015, Avery Rozar 
wrote:

> I'm trying to build port for snort-2.9.8.0 and have run into a snag. I get
> this error during "make makeplist". How do I use "USES=shebangfix" to fix
> this error? Do I put it in /etc/make.conf, the make file for snort?
>
> > Running Q/A tests (stage-qa)
>
> Error: '/bin/bash' is an invalid shebang you need USES=shebangfix for
> 'bin/appid_detector_builder.sh'
>
>
> Thank you,
> Avery
>
>
The FreeBSD porter's handbook has your answer here:

https://www.freebsd.org/doc/en/books/porters-handbook/book.html#uses-shebangfix

The rest of that document is a great read and ongoing reference for all
your porting needs :)

Good luck!
-Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: [HEADS-UP] portscout now works with Ports using GitHub

[Ben Woods]

On 6 January 2016 at 19:27, Kubilay Kocak  wrote:

> Dear Porters/Maintainers,
>
> An hour or so ago, an updated version of portscout was deployed that
> finally fixes detection of updates for ports using USE_GITHUB=yes
>

I just wanted to say a quick thank you to all those involved in getting
this working. It has immediately helped me, and I'm sure it will help many
others too.

Cheers,
Ben
___
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: great a diff with a new patch

[Ben Woods]

On Sunday, 13 March 2016, Jochen Neumeister 
wrote:

> Hi there,
>
> how can I great a diff with a new patch?
>
> I run make makepatch, and then I move the new patch in the /file folder.
>
> Now I run svn diff > ~/dev/patches/foo.diff, but the new patch is not
> into diff.
>
> someone has a tip for me?
>
> Cheers
> Jochen
>

Hi Jochen,

Small correction: your patches should be in the "files/" directory, not the
"file/" directory.

To check the status of which files have changed from the upstream svn
repository, you can run "svn status" in the ports directory. Files which
have been modified show an "M" next to their name. Files which have been
added but svn is not aware of them show an "?" next to their name.

To tell svn to add a file, use:
$ svn add 

Then you can run "svn status" again to see the files now have an "A" next
to their name.

Now when you run "svn diff" it will include your additional patches.

Good luck!
-Ben


-- 

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

Multiple ffmpeg versions in ports

[Ben Woods]

Hello ports people,

What do you think about having numerous versions of ffmpeg in ports,
similar to lang/python?

There seems to be a common problem with ffmpeg being a fast moving project,
with backward incompatible API/ABI changes between major versions. This
results in regular difficulties building ports which depend on ffmpeg, and
often ports bundle their own version of ffmpeg to avoid incorrect API
difficulties across different operating systems / distros (e.g. HandBrake,
plexhometheater). Bundled libraries should be avoided where possible to
ensure we can provide clarity on where security vulnerabilities exist (of
which there are a few for ffmpeg). [1]

Whilst the ffmpeg team appear to be supporting 2.5.x, 2.6.x, 2.7.x, 2.8.x
and 3.0.x, we probably only need to maintain a port where it is required
for another port to build correctly. To start with I was thinking we should
simply create multimedia/ffmpeg30, move multimedia/ffmpeg to
multimedia/ffmpeg28, and create a dummy multimedia/ffmpeg which depends on
multimedia/ffmpeg30. Any ports which fail to build against
multimedia/ffmpeg30 can instead require multimedia/ffmpeg28, and we could
add a comment next to the dependency reminding the port maintainer to move
to the later version of ffmpeg once it is supported by the package.

This would likely mean we will have a number of versions of ffmpeg in the
ports system over time, but I think it is the reality that different
packages support different versions of the ffmpeg API/ABI, and it would
help keep track of what is vulnerable / outdated rather than hiding it by
bundled ffmpeg versions.

Thoughts? If the idea is supported, I could prepare a phabricator review of
the proposed changes.

[1] https://www.freebsd.org/doc/en/books/porters-handbook/bundled-libs.html

--
From: Benjamin Woods
woods...@gmail.com
___
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: Multiple ffmpeg versions in ports

[Ben Woods]

On 30 March 2016 at 23:28, Ben Woods  wrote:

>
> What do you think about having numerous versions of ffmpeg in ports,
> similar to lang/python?
>


I guess the obvious question is how could it be possible for multiple
ffmpeg versions to be installed at the same time? Is it possible to ensure
the files do not overlap, and that each package is linking against the
correct installed version?

--
From: Benjamin Woods
woods...@gmail.com
___
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: Recording TIMESTAMPs in distinfo for reproducible builds work

[Ben Woods]

On Thursday, 12 May 2016, Ed Maste  wrote:

> Baptiste and I have been looking at reproducible builds in the FreeBSD
> ports tree, and one thing we'll need is a consistent timestamp that
> doesn't change when a port is rebuilt without changes.
>
> We considered a few different ideas, and have settled on experimenting
> with the time 'make makesum' is run.
>

Hi Ed,

Thanks for the heads up.

Quick question: is there now an expectation that each time a port is
changed the timestamp should be updated?

I.e. If a port changes in a way which does not change the distfiles, are we
supposed to run "make makesum" again anyway to record it has changed?

Or is the timestamp only supposed to change when the port is updates /
distfiles change?

Regards,
Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: Nfsen install problem - missing profile data

[Ben Woods]

On Saturday, 11 June 2016, Radek Krejča  wrote:

> Hello,
>
> I need to install nfsen on new hardware. When I use pkg or comile from
> ports, there is problem, that I have empty directories and start of nfsen
> got error:
>
> /usr/local/etc/rc.d/nfsen start
> Error reading profile 'live': Can't open profile data file for profile:
> 'live' in group '.': No such file or directory
> Died at /usr/local/bin/nfsen line 455.
>
> In the log is:
>
> Jun 11 19:06:38 nfsen nfsen: Error reading hints: can't open
> /usr/local/var/nfsen/profiles/hints: No such file or directory at
> /usr/local/libexec/nfsen/NfSen.pm line 798.
> Jun 11 19:06:38 nfsen nfsen: Initialize hints to defaults.
>
> How to create proper files?
>
> Thank you very much.
>
> Radek
>

Hi Radek,

I put together a guide on how to use nfdump/nfsen on FreeBSD a year or so
ago.
https://forums.freebsd.org/threads/49724/

It also includes details on how to make FreeBSD the netflow exporter - skip
this it it is not what you're trying to achieve.

I haven't had a look to see if it solves your exact problem. Perhaps have a
read through that and see if it helps?

Good luck,
Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: Nfsen install problem - missing profile data

[Ben Woods]

On Sunday, 12 June 2016, Radek Krejča  wrote:

> Solved. Thank you.
>
> Radek
>

Glad it is working :)

In case someone else finds this thread in the future, could you please
share what fixed this for you?

Thanks,
Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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"

pkg(8) conflicts when install gnome3 - what are they?

[Ben Woods]

Hi everyone,

I have build gnome3 with my local poudriere instance, but when I try to install 
it pkg complains of conflicts.

# pkg install gnome3
 <[1526][23:35]]
Updating FreeBSD-base repository catalogue...
FreeBSD-base repository is up-to-date.
Updating poudriere repository catalogue...
poudriere repository is up-to-date.
All repositories are up-to-date.
Checking integrity... done (1 conflicting)
Cannot solve problem using SAT solver, trying another plan
Checking integrity... done (0 conflicting)
The following 169 package(s) will be affected (of 0 checked):

How can I determine what the conflicts are? Is there a way to tell pkg to be 
verbose and explain the conflict?

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
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(8) conflicts when install gnome3 - what are they?

[Ben Woods]

On Wed, Jun 15, 2016 at 02:53:25PM -0700, Freddie Cash wrote:
> On Wed, Jun 15, 2016 at 2:45 PM, Ben Woods  wrote:
> 
> > Hi everyone,
> >
> > I have build gnome3 with my local poudriere instance, but when I try to
> > install it pkg complains of conflicts.
> >
> > # pkg install gnome3
> ><[1526][23:35]]
> > Updating FreeBSD-base repository catalogue...
> > FreeBSD-base repository is up-to-date.
> > Updating poudriere repository catalogue...
> > poudriere repository is up-to-date.
> > All repositories are up-to-date.
> > Checking integrity... done (1 conflicting)
> > Cannot solve problem using SAT solver, trying another plan
> > Checking integrity... done (0 conflicting)
> > The following 169 package(s) will be affected (of 0 checked):
> >
> > How can I determine what the conflicts are? Is there a way to tell pkg to
> > be verbose and explain the conflict?
> >
> > Regards,
> > Ben
> >
> >
> ???There's a -d / --debug option that can be passed.  Perhaps that will give
> you the info you need.???
> 
> 
> 
> -- 
> Freddie Cash
> fjwc...@gmail.com

Thanks for the reply Freddie, I wasn't aware of that flag, because I was 
reading pkg-install(8) man page rather than pkg(8).

However, unfortunately it doesn't reveal the conflict.

# pkg -d install gnome3
Password:
DBG(1)[1860]> pkg initialized
Updating FreeBSD-base repository catalogue...
DBG(1)[1860]> PkgRepo: verifying update for FreeBSD-base
DBG(1)[1860]> Pkgrepo, begin update of '/var/db/pkg/repo-FreeBSD-base.sqlite'
DBG(1)[1860]> Fetch: fetching from: 
http://127.0.0.1/FreeBSD-base/FreeBSD:11:amd64/latest/meta.txz with opts "i"
DBG(1)[1860]> Fetch: fetching from: 
http://127.0.0.1/FreeBSD-base/FreeBSD:11:amd64/latest/packagesite.txz with opts 
"i"
FreeBSD-base repository is up-to-date.
Updating poudriere repository catalogue...
DBG(1)[1860]> PkgRepo: verifying update for poudriere
DBG(1)[1860]> Pkgrepo, begin update of '/var/db/pkg/repo-poudriere.sqlite'
DBG(1)[1860]> Fetch: fetching from: 
http://127.0.0.1/poudriere/pkg/FreeBSD:11:amd64/meta.txz with opts "i"
DBG(1)[1860]> Fetch: fetching from: 
http://127.0.0.1/poudriere/pkg/FreeBSD:11:amd64/packagesite.txz with opts "i"
poudriere repository is up-to-date.
All repositories are up-to-date.
DBG(1)[1860]> want to get an advisory lock on a database
DBG(1)[1860]> found stale pid 1702 in lock database, my pid is: 1860
DBG(1)[1860]> no concurrent processes found, cleanup the lock
DBG(1)[1860]> want to get an advisory lock on a database
...
Checking integrity...DBG(1)[1860]> check integrity for 299 items added
 done (1 conflicting)
Cannot solve problem using SAT solver, trying another plan
Checking integrity...DBG(1)[1860]> check integrity for 169 items added
 done (0 conflicting)
The following 169 package(s) will be affected (of 0 checked):


Are there any other methods to get pkg to reveal the conflict?

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
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(8) conflicts when install gnome3 - what are they?

[Ben Woods]

On Thu, Jun 16, 2016 at 01:58:31AM -0700, Don Lewis wrote:
> >> On Wed, Jun 15, 2016 at 2:45 PM, Ben Woods  wrote:
> >> 
> >> > How can I determine what the conflicts are? Is there a way to tell pkg to
> >> > be verbose and explain the conflict?
> 
> It definitely would be nice if pkg was more helpful about this.
> 
> One thing to check is that your currently installed packages are up to
> date.  I've gotten into similar situation when I've forgotten to run
>   pkg upgrade
> before doing
>   pkg install
> 
> I think that what happens is if I have packages A and B installed, and B
> depends on A, and if A has been updated to A' since A and B were
> installed, then when I try to install C, which depends on A', then pkg
> wants to delete A and install A', which makes in want to delete B as
> well.  If I run pkg upgrade first, then A gets upgrade to A', and I
> don't run into a problem when I then install C.
> 

Indeed, I have come across that before as well.

However, on this occasion I have already ensured that all packages are up to 
date.
I even went to the extent of removing them all and then re-installing them from
the latest poudriere packages (after a "pkg clean -ay").

There seems to be something inherently conflicting in the gnome3 package and 
it's
dependencies that will be installed.

The main point of this thread, however, was to discuss how to get pkg to further
explain the conflict.

Regards,
Ben

--
From: Benjamin Woods
woods...@gmail.com
___
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"