Re: dns/libidn2 2.3.0 breaks gnutls for samba (was: Samba 4.10.10 can't find gnutls headers on one machine)
On Thu, Nov 21, 2019 at 8:46 PM Morgan Wesström wrote: > > > > On 2019-11-21 16:37, Morgan Wesström wrote: > >> Dear list, > >> > >> I need some help to figure out what I broke on my system. I have two > >> (almost) identical machines, one running 12.1-RELEASE and one waiting > >> to be upgraded and is still on 12.0-RELEASE-p10. Configuration and > >> software wise I try to keep them identical. > > I found the problem. Samba's config.log had the following error: > > err: //usr/local/lib/libidn2.so.0:(.text+0x2290): multiple definition of > `_idn2_punycode_encode@IDN2_0.0.0' > //usr/local/lib/libidn2.so.0:(.text+0x2610): multiple definition of > `_idn2_punycode_decode@IDN2_0.0.0' > cc: error: linker command failed with exit code 1 (use -v to see invocation) > > I tracked this down to a commit made to libidn2 a week ago: > > https://gitlab.com/libidn/libidn2/commit/089616574679a017f5d45c6bd40b05816ae4db6b > > I downgraded libidn2 to 2.2.0 and recompiled gnutls and the other > packages depending on it and now samba compiles without any problems. I > can't say if this is a bug in libidn2, gnutls or samba so I can't file a > bug report for it. Hi, It's a libidn2 bug. Antoine ___ 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 for Ruby
On Sat, Sep 14, 2019 at 6:27 AM Koichiro Iwao wrote: > On Fri, Sep 13, 2019 at 09:33:43AM -0600, Adam Weinberger wrote: > > Systems MUST be able to support concurrent installations of python2.7 > > and actual python. What is your use case for concurrent ruby? > > I know the importance of Python 2. Even if it is EoL-ed, it will be > required over the next a few years because not a few applications don't > migrate to Python 3. So that's true and reasonable. > > Excuse me that I'm answering your question with a question. What about > PHP? Concurrent installation is a MUST? > > FreeBSD ports allows concurrent installations of multiple Ruby versions > however doesn't allow concurrent installations of rubygems for multiple > Ruby versions. This inconsistency is the issue for me. This isn't a valid reason for me. Why do you need ruby version 2.4 or 2.5 concurrently installed with version 2.6? Is there a bug in version 2.6? Cheers, Antoine ___ 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 for Ruby
On Fri, Sep 13, 2019 at 9:45 AM Koichiro Iwao wrote: > Hi, > > I would like to suggest introducing FLAVOR to Ruby ports. > > AFAIK multiple version of Ruby ports (lang/ruby??) can be installed at > the same time. One of these ruby ports will be *default* installed as > PREFIX/bin/ruby. In contrast of Ruby lang, rubygem ports cannot be > installed for multiple Ruby version at the same time. > > I would say Ruby and rubygem ports needs FLAVORS like Python ports. > In Python ports, the same origin py- ports can be installed for multiple > versions such as py27, py35, py36. If the same thing can be done with > Ruby ports, FreeBSD Ruby ports will be much improved. > > I would appreciate if you Ruby folks bounce some ideas off each other. > Let me know if someone's already working on FLAVORS on Ruby. Is there > something that I can help you with? Please no. I don't see valid reasons. Antoine ___ 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: Django versions
On Thu, Mar 7, 2019 at 8:14 AM Craig Leres wrote: > > I'm working on a port for mailman 3. I want to use django 2.1 because > that's what I'm using on the systems I'm currently running mailman 2 on > you can't really run different version of django on the same system). > But it turns out a lot of ports have RUN_DEPENDS for www/py-django111. > > One possible solution would be to change these dependencies to the > www/py-django meta port. This allows the user pick the version of django > via py-django options. But I see a bunch of ports got added last month: > > www/py-dj21-django-cors-headers > www/py-dj21-django-debug-toolbar > www/py-dj21-django-filter > www/py-dj21-django-js-asset > www/py-dj21-django-mptt > www/py-dj21-django-tables2 > www/py-dj21-django-taggit > www/py-dj21-django-taggit-serializer > www/py-dj21-django-timezone-field > www/py-dj21-djangorestframework > www/py-dj21-drf-yasg > > which are the py-django21 version of the py-django111 ports with similar > names. > > Anyway the current situation prevents folks from using py-django20 if > that's what they want. And a ton of changes will be needed when django22 > (currently in beta) arrives. > > The downside I see to changing dependencies from py-django111 to > py-django is that only the py-django111 versions of things were get > built/tested automatically (due to py-django111 being the default > version). And I think there are issues for ports that don't work with > all version of django (is there a way for a port's Makefile to know what > version of django got installed?) > > Are there other problems? > > Are there other solutions? Flavors comes to mind but I'm told "doubly > flavored" ports (python flavor vs. django flavor) are very difficult. > > Without any changes I'll need to add DJANGO111 and DJANGO21 to my > mailman 3 port and forget about folks being able to use django20. This > will be extra messy because mailman 3 is split across several different > packages. Hi, Please don't use the django metaport, this port should be removed and people should stop using hacks. Someone needs to integrate a USE_PYTHON=django in python.mk Antoine ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: net-p2p/qbittorrent needs to be unblocked by portmgr
On Wed, Jun 20, 2018 at 8:18 AM, Yuri wrote: > Committing transaction... > svn: E165001: Commit failed (details follow): > svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output: > Do not commit a port with FLAVORS without first > getting approval from portmgr. Yes, you didn't receive approval to do this. Antoine (with hat: portmgr) ___ 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: Can not build dns/unbound and dns/nsd from latest ports with poudriere
On Sun, May 20, 2018 at 9:55 PM, Larry Rosenmanwrote: > On Sun, May 20, 2018 at 10:27:33PM +0300, Lev Serebryakov wrote: >> Hello Ports, >> >> I have poudriere -CURRENT jail with full fresh ports tree. And build of >> both `dns/unbound' and `dns/nsd' fails with very strange error: >> >> === >> === >> === >> ===> nsd-4.1.21 depends on shared library: libevent.so - not found >> ===> Installing existing package /packages/All/libevent-2.1.8_1.txz >> [12x64-gw-default-job-01] Installing libevent-2.1.8_1... >> [12x64-gw-default-job-01] Extracting libevent-2.1.8_1: .. done >> ===> nsd-4.1.21 depends on shared library: libevent.so - not found >> *** Error code 1 >> >> and >> >> === >> === >> ===> unbound-1.7.1 depends on shared library: libexpat.so - not found >> ===> Installing existing package /packages/All/expat-2.2.5.txz >> [12x64-gw-default-job-02] Installing expat-2.2.5... >> [12x64-gw-default-job-02] Extracting expat-2.2.5: .. done >> ===> unbound-1.7.1 depends on shared library: libexpat.so - not found >> *** Error code 1 >> >> Other 30+ ports I need had been built Ok! >> >> This jail is very trimmed-of to simulate NanoBSD environment, but both >> libevent-2.1.8_1 and expat-2.2.5 had been built without problems, too. > > I'm seeing this same behavior for ~300 ports since an upgrade from > r81 to r333924. > > http://home.lerctr.org:/build.html?mastername=live-host-ports=2018-05-20_10h16m46s > > I've pinged bdrew...@freebsd.org about it. Can you verify that: file -b -L --mime-type /usr/local/lib/libevent.so or file -b -L --mime-type /usr/local/lib/libexpat.so returns application/x-sharedlib? If not, this may be a regression in libmagic.. Antoine ___ 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: perl5.24 build failing on a new 11.1-STABLE install
On Wed, Mar 28, 2018 at 12:42 PM, Michael Grimm <trash...@ellael.org> wrote: > Antoine Brodin <anto...@freebsd.org> wrote: > >> On Wed, Mar 28, 2018 at 12:04 PM, Michael Grimm <trash...@ellael.org> wrote: > >>> FreeBSD 11.1-STABLE #0 r331660: Wed Mar 28 08:36:15 CEST 2018 >>> root@mer-waases:/usr/obj/usr/src/sys/CUSTOM > >> You can try to revert https://svnweb.freebsd.org/changeset/base/331551 > > Please excuse my ignorance, but I haven't done that before. After a quick > scan in svn help I came up with: > > svn merge -r 331660:331551 > > Is this correct? > What I want to achieve is keeping all commits besides 331551 svn merge -c -331551 . Antoine ___ 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: perl5.24 build failing on a new 11.1-STABLE install
On Wed, Mar 28, 2018 at 12:04 PM, Michael Grimmwrote: > Bob Willcox wrote: > >> --- perl --- >> cc -o perl -lpthread -Wl,-E -fstack-protector-strong -L/usr/local/lib >> -Wl,-R/usr/local/lib/perl5/5.24/mach/CORE maindtrace/perlmain.o >> dtrace_main.o libperl.so.5.24.3 `cat ext.libs` -lpthread -lm -lcrypt -lutil >> maindtrace/perlmain.o: In function `main': >> perlmain.c:(.text+0xa4): undefined reference to `perl_parse' >> perlmain.c:(.text+0xb4): undefined reference to `perl_run' >> perlmain.c:(.text+0x128): undefined reference to `perl_destruct' >> cc: error: linker command failed with exit code 1 (use -v to see invocation) >> *** [perl] Error code 1 > > I did run into this issue as well using poudriere to rebuild all ports. > Same error message. > Both FBSD systems of mine are hit by the very same error. > >> The system 'uname -a' is: >> >> FreeBSD exar.immure.com 11.1-STABLE FreeBSD 11.1-STABLE #0 r331606: Tue Mar >> 27 07:27:39 CDT 2018 > > FreeBSD 11.1-STABLE #0 r331660: Wed Mar 28 08:36:15 CEST 2018 > root@mer-waases:/usr/obj/usr/src/sys/CUSTOM > > >> Anyone have any idea as to what may be wrong with or missing on this system? Hi, You can try to revert https://svnweb.freebsd.org/changeset/base/331551 Antoine ___ 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: Go ports fail with fs violation: Error: Filesystem touched during build:,extra: root/.cache
On Wed, Feb 28, 2018 at 10:10 PM, Yuri <y...@rawbw.com> wrote: > On 02/28/18 13:07, Antoine Brodin wrote: >> >> No, HOME is already enough to fix the violation. The problem is that >> those ports/go.mk do fancy things and do not respect BUILD_ENV. > > > > Both examples don't use go.mk and still fail. Both examples do not use MAKE_ENV. Antoine ___ 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: Go ports fail with fs violation: Error: Filesystem touched during build:,extra: root/.cache
On Wed, Feb 28, 2018 at 9:57 PM, Yuri <y...@rawbw.com> wrote: > On 02/28/18 00:35, Antoine Brodin wrote: >> >> Ports that use CONFIGURE_ENV / MAKE_ENV have this violation issue with >> HOME=${WRKDIR}. >> Maybe this should be added to GO_ENV and go ports should respect more >> this environment. > > > > PGo also tries "XDG_CACHE_HOME" when "GOCACHE" isn't defined. > > Mk/ does define "XDG_DATA_HOME" in MAKE_ENV. > > Maybe the right solution is to just add "XDG_CACHE_HOME" there? No, HOME is already enough to fix the violation. The problem is that those ports/go.mk do fancy things and do not respect BUILD_ENV. Antoine ___ 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: Go ports fail with fs violation: Error: Filesystem touched during build:,extra: root/.cache
On Wed, Feb 28, 2018 at 8:35 AM, Antoine Brodin <anto...@freebsd.org> wrote: > On Wed, Feb 28, 2018 at 12:12 AM, Yuri <y...@rawbw.com> wrote: >> For example: >> >> http://package21.nyi.freebsd.org/data/111amd64-default-qat/462883/logs/errors/gogs-0.11.34_2.log >> >> http://package21.nyi.freebsd.org/data/111amd64-default-qat/462883/logs/errors/cryptoballot-g20170928.log > > Ports that use CONFIGURE_ENV / MAKE_ENV have this violation issue with ^^ fixed > HOME=${WRKDIR}. > Maybe this should be added to GO_ENV and go ports should respect more > this environment. > > Antoine ___ 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: Go ports fail with fs violation: Error: Filesystem touched during build:,extra: root/.cache
On Wed, Feb 28, 2018 at 12:12 AM, Yuriwrote: > For example: > > http://package21.nyi.freebsd.org/data/111amd64-default-qat/462883/logs/errors/gogs-0.11.34_2.log > > http://package21.nyi.freebsd.org/data/111amd64-default-qat/462883/logs/errors/cryptoballot-g20170928.log Ports that use CONFIGURE_ENV / MAKE_ENV have this violation issue with HOME=${WRKDIR}. Maybe this should be added to GO_ENV and go ports should respect more this environment. Antoine ___ 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: glib-compile-schemas
On Sat, Jan 20, 2018 at 10:09 AM, Kurt Jaegerwrote: > Hi! > >> I am building a gnome based port. >> >> The port builds and installs successfully but it doesn't work. >> >> Looking around I need to run glib-compile-schemas like this: >> >> glib-compile-schemas /usr/local/share/glib-2.0/schemas/ >> >> After running that command the port works as expected, is there a standard >> way to handle this in the port's Makefile? > > devel/glib20 has this in its pkg-plist: > > @postexec %D/bin/glib-compile-schemas %D/share/glib-2.0/schemas 2>/dev/null > || /usr/bin/true But it would be wrong to add it to another port, GLIB_SCHEMAS is there for this. Antoine ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: What is the solution when the port has __pycache__ fs violation: lib/python3.6/site-packages/PyQt5/__pycache__/pyrcc_main.cpython-36.pyc
On Sun, Dec 3, 2017 at 8:37 PM, Yuriwrote: > I am not getting the error when I build in podriere, but for some reason the > central builds fail. > >> =>> Error: Filesystem touched during build: >> extra: >> usr/local/lib/python3.6/site-packages/PyQt5/__pycache__/pyrcc_main.cpython-36.pyc > > > The port: audio/carla Hi, This seems to be a bug in textproc/py-qt5-xml, it doesn't package byte-compiled versions of some modules. Cheers, Antoine ___ 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: SPDX and LICENSE in the ports framework
On Wed, Nov 8, 2017 at 11:49 AM, Kurt Jaegerwrote: > Hi! > > Who is working on the LICENSE part of the ports framework ? > > I've found this website: > > https://spdx.org/ > > which describes SPDX as a > > standard format for communicating the components, licenses and > copyrights associated with software packages > > Do we need some mapping between our license and theirs ? > Some tools etc ? Hi, Mk/bsd.licenses.db.mk:18:# The canonical source of license names and short-name identifiers: Mk/bsd.licenses.db.mk:19:# - SPDX License List Mk/bsd.licenses.db.mk:20:# https://spdx.org/licenses/ Cheers, Antoine ___ 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: screen, ncurses and ncurses.mk
On Sat, Aug 26, 2017 at 10:55 AM, Walter Schwarzenfeldwrote: > The maintainer of sysutils/screen changed to USES=ncurses:base. > > This will not work if ncurses:ports is installed (python uses it). No, python uses ncurses, it doesn't require the one from ports. Only 3 or 4 anecdotal ports require ncurses from ports. Antoine ___ 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: svn commit: r315662 - in head: contrib/bsnmp/snmp_mibII contrib/ipfilter/ipsend lib/libprocstat sys/netinet sys/sys usr.bin/netstat usr.bin/sockstat usr.bin/systat usr.sbin/tcpdrop usr.sbin/trpt
On Tue, Mar 21, 2017 at 7:41 AM, Gleb Smirnoffwrote: > Hi! > > This change is known to break a ton of ports. More than 100 if > counting depends. I'm sorry for that and I already started to fix > them. > > Please send all new breakages to me. Hi, Exp-runs should happen before breakage happens, not after. If you already know that it breaks hundreds of ports, please revert and request an exp-run. Antoine (with hat: portmgr) > On Tue, Mar 21, 2017 at 06:39:49AM +, Gleb Smirnoff wrote: > T> Author: glebius > T> Date: Tue Mar 21 06:39:49 2017 > T> New Revision: 315662 > T> URL: https://svnweb.freebsd.org/changeset/base/315662 > T> > T> Log: > T> Hide struct inpcb, struct tcpcb from the userland. > T> > T> This is a painful change, but it is needed. On the one hand, we avoid > T> modifying them, and this slows down some ideas, on the other hand we > still > T> eventually modify them and tools like netstat(1) never work on next > version of > T> FreeBSD. We maintain a ton of spares in them, and we already got some > ifdef > T> hell at the end of tcpcb. > T> > T> Details: > T> - Hide struct inpcb, struct tcpcb under _KERNEL || _WANT_FOO. > T> - Make struct xinpcb, struct xtcpcb pure API structures, not including > T> kernel structures inpcb and tcpcb inside. Export into these structures > T> the fields from inpcb and tcpcb that are known to be used, and put > there > T> a ton of spare space. > T> - Make kernel and userland utilities compilable after these changes. > T> - Bump __FreeBSD_version. > T> > T> Reviewed by: rrs, gnn > T> Differential Revision: D10018 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: USES=pathfix broken?
On Sun, Jan 22, 2017 at 8:40 AM, Don Lewiswrote: > I've started getting a bunch of pkg-fallout@ email reporting missing > libdata/pkgconfig/*.pc files. It looks like the *.pc files are getting > installed under lib/pkgconfig. > > [snip] > /bin/mkdir -p > '/wrkdirs/usr/ports/devel/mtbl/work/stage/usr/local/lib/pkgconfig' > install -m 0644 mtbl/libmtbl.pc > '/wrkdirs/usr/ports/devel/mtbl/work/stage/usr/local/lib/pkgconfig' > [snip] > ===> Building package for mtbl-0.8.0 > pkg-static: Unable to access file > /wrkdirs/usr/ports/devel/mtbl/work/stage/usr/local/libdata/pkgconfig/libmtbl.pc: > No such file or directory > [snip] > > So far the problems have been with limited to > [package - head-amd64-default] and > [exp - 103i386-default-build-as-user]. The latter would seem to > eliminate the recent sed changes in -CURRENT as a cause. I'm not seeing > any problems with the r432015 revision of the ports tree, and I don't > see any suspicious commits to ports/Mk after that point. Hi, There seems to be a regression in pkgconf 1.2.0, see https://github.com/pkgconf/pkgconf/issues/108 Antoine ___ 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"
New 2016Q1 branch
Hi, The 2016Q1 branch has been created. It means that the next update on the quarterly packages will be on the 2016Q1 branch A lot of things happened in the last three months, including: - pkg 1.6.2 - New USES: pyqt, terminfo - New keyword: terminfo - Firefox 43.0.3 - Firefox-esr 38.5.2 - Chromium 47.0.2526.106 - OpenJDK 8 as default JDK Next quarterly package builds will start on 5 january at 1AM UTC and should be available on your closest mirrors few days later. For those stat nerds out there, here's what happened during the last 3 months on head: Number of commits: 6392 Number of committers: 153 Most active committers: 1413 sunpoet 742 amdmi3 176 miwi 172 olgeni 166 marino 157 junovitch 155 antoine 147 rakuco 135 pi 131 mat Diffstat: 14923 files changed, 288346 insertions(+), 226770 deletions(-) and on the 2015Q4 branch: Number of commits: 248 Number of committers: 45 Most active committers: 20 junovitch 20 amdmi3 19 feld 17 koobs 16 jbeich 15 swills 10 rakuco 10 mat 9 rene 9 kwm Diffstat: 737 files changed, 24175 insertions(+), 50934 deletions(-) Regards, Antoine, on behalf of portmgr@ ___ 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: graphics/jpeg-turbo breaks on strip-debug
On Sat, Sep 19, 2015 at 5:32 PM, Julian H. Staceywrote: > Hi ports@ > cc portmgr@ as MAINTAINER= of graphics/jpeg-turbo > > graphics/jpeg-turbo breaks on strip-debug > I've commented out all occurences I can find, but it's still breaking. > Any ideas ? Or a fix even ? Hi, Could you check that the version of nasm you are using has this fix: https://svnweb.freebsd.org/changeset/ports/384314 It's supposed to fix this issue. Cheers, Antoine > On current, kernel & src from yesterday, ports todays > uname -a > FreeBSD lapr.js.berklix.net 11.0-CURRENT FreeBSD 11.0-CURRENT > #12135: Thu Sep 17 14:54:15 CEST 2015 > j...@lapr.js.berklix.net:/usr/src/sys/amd64/compile/LAPR.small > amd64 > rm -r /var/db/ports/graphics_jpeg-turbo > cd /usr/ports/graphics/jpeg-turbo ; make clean ; make > strip --strip-debug > /data/release/11.0-CURRENT/usr/ports/graphics/jpeg-turbo/work/stage/usr/local/lib/libjpeg.a > strip: elf_update() failed: Layout constraint violation > *** Error code 1 > file > /data/release/11.0-CURRENT/usr/ports/graphics/jpeg-turbo/work/stage/usr/local/lib/libjpeg.a > /data/release/11.0-CURRENT/usr/ports/graphics/jpeg-turbo/work/\ > stage/usr/local/lib/libjpeg.a: current ar archive > -rwxr-xr-x 1 root wheel 560734 Sep 19 16:06 > strip --strip-debug /data/release/11.0-CURRENT/usr/ports/graphics/\ > jpeg-turbo/work/stage/usr/local/lib/libjpeg.a > strip: elf_update() failed: Layout constraint violation > strip > /data/release/11.0-CURRENT/usr/ports/graphics/jpeg-turbo/work/stage/usr/local/lib/libjpeg.a > Succeeded > -rwxr-xr-x 1 root wheel 411050 Sep 19 16:08 /data/release/\ > 11.0-CURRENT/usr/ports/graphics/jpeg-turbo/work/stage/\ > usr/local/lib/libjpeg.a* > file `which strip` > /usr/bin/strip: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), > dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 11.0 > (1100079), stripped > > strip-debug is not in a clean /usr/ports/graphics/jpeg-turbo/ > > but strip-debug turns up during building: > work/libjpeg-turbo-1.4.1/aclocal.m4: test -z "$old_striplib" && > old_striplib="$STRIP --strip-debug" > work/libjpeg-turbo-1.4.1/configure.libtool.bak: test -z > "$old_striplib" && old_striplib="$STRIP --strip-debug" > work/libjpeg-turbo-1.4.1/configure: test -z "$old_striplib" && > old_striplib="$STRIP --strip-debug" > work/libjpeg-turbo-1.4.1/libtool:old_striplib="strip --strip-debug" > > strip-debug is coming from a macro or include, but not from my /etc/make.conf > or includes > > MK/Uses/kmod.mk:STRIP_CMD+= --strip-debug # do not strip kernel symbols > Commented out > > rm -r /var/db/ports/graphics_jpeg-turbo > cd /usr/ports/graphics/jpeg-turbo ; make clean ; make > > Still breaks > cd /usr/share/mk > Grep strip-debug > bsd.lib.mk: ${OBJCOPY} --strip-debug > --add-gnu-debuglink=${SHLIB_NAME}.debug \ > bsd.prog.mk: ${OBJCOPY} --strip-debug > --add-gnu-debuglink=${PROGNAME}.debug \ > > rm -r /var/db/ports/graphics_jpeg-turbo > cd /usr/ports/graphics/jpeg-turbo ; make clean ; make MK_DEBUG_FILES=no > strip --strip-debug > /data/release/11.0-CURRENT/usr/ports/graphics/jpeg-turbo/work/stage/\ > usr/local/lib/libjpeg.a > strip: elf_update() failed: Layout constraint violation > > PS I did a trawl for strip-debug > ports/ > Mk/Uses/kmod.mk:STRIP_CMD+= --strip-debug # do not strip kernel symbols > devel/nasm/files/patch-elf64-alignment:% strip -o /dev/null --strip-debug > jccolss2-64.o > emulators/virtualbox-ose/files/extrapatch-Config.kmk:+# objcopy > --strip-debug $(out) > emulators/virtualbox-ose/files/extrapatch-Config.kmk:-objcopy > --strip-debug $(out) > > src/ > contrib/apr/configure: test -z "$old_striplib" && old_striplib="$STRIP > --strip-debug" > contrib/binutils/bfd/configure: test -z "$old_striplib" && > old_striplib="$STRIP --strip-debug" > contrib/binutils/binutils/ChangeLog-0203: (strip): Document -d as an > alias for --strip-debug. > contrib/binutils/binutils/ChangeLog-0203: --strip-debug. > contrib/binutils/binutils/ChangeLog-0203: Mention that --strip-debug > removes sections as well. > contrib/binutils/binutils/NEWS: those sections that would be stripped out > by --strip-debug. The idea is that > contrib/binutils/binutils/configure: test -z "$old_striplib" && > old_striplib="$STRIP --strip-debug" > contrib/binutils/binutils/doc/binutils.7:[-g|--strip-debug] > contrib/binutils/binutils/doc/binutils.7: [-S|-g|-d|--strip-debug] > contrib/binutils/binutils/doc/binutils.7:.It --strip-debug > contrib/binutils/binutils/doc/binutils.7:.Li objcopy --strip-debug foo > contrib/binutils/binutils/doc/binutils.7:.Li strip --strip-debug foo > contrib/binutils/binutils/doc/binutils.7:.Op
Re: FreeBSD Port: kibana-3.1.2
On Thu, Apr 30, 2015 at 10:49 AM, Albert Gabàs | Astabis aga...@astabis.com wrote: Dear Kibana port maintainer, Please, could you update the port to the latest version (Kibana 4.0.2)?? Hi, Kibana 4 is a complete rewrite so the kibana 3 port will stay for a bit. Cheers, Antoine ___ 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 failing to build with clang 3.6
Dear maintainer, The FreeBSD project is working on updating llvm and clang to 3.6.0 in head [1]. The following ports you maintain fail to build after this update: security/libtomcrypt http://pb2.nyi.freebsd.org/data/headi386PR197395-default/2015-02-27_12h37m23s/logs/errors/libtomcrypt-1.17_4.log http://package18.nyi.freebsd.org/data/headamd64PR197395-default/2015-02-27_12h37m16s/logs/errors/libtomcrypt-1.17_4.log mail/milter-manager http://pb2.nyi.freebsd.org/data/headi386PR197395-default/2015-02-27_12h37m23s/logs/errors/milter-manager-2.0.4.log http://package18.nyi.freebsd.org/data/headamd64PR197395-default/2015-02-27_12h37m16s/logs/errors/milter-manager-2.0.4.log games/stepmania-devel http://pb2.nyi.freebsd.org/data/headi386PR197395-default/2015-02-27_12h37m23s/logs/errors/stepmania-devel-5.0.a3_4,1.log http://package18.nyi.freebsd.org/data/headamd64PR197395-default/2015-02-27_12h37m16s/logs/errors/stepmania-devel-5.0.a3_4,1.log If you have a patch to fix the ports, please submit them in FreeBSD Bugzilla [2]. [1] https://bugs.freebsd.org/197395 [2] https://bugs.freebsd.org/submit/ Cheers, Antoine on behalf of portmgr@ ___ 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 failing to build with clang 3.5
Dear maintainer, The FreeBSD project is working on updating llvm and clang to 3.5.0 in head [1]. The following ports you maintain fail to build after this update: science/vmd http://pb2.nyi.freebsd.org/data/head-amd64-PR195480-default/2014-12-12_23h17m02s/logs/errors/vmd-1.9.1_3.log Usually, the -Werror warnings are pointing to actual bugs in the ports themselves. If you have a patch to fix the ports, please submit them in FreeBSD Bugzilla [2]. [1] https://lists.freebsd.org/pipermail/freebsd-current/2014-November/053570.html [2] https://bugs.freebsd.org/submit/ Cheers, Antoine on behalf of portmgr@ ___ 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 failing to build with clang 3.5
Dear maintainer, The FreeBSD project is working on updating llvm and clang to 3.5.0 in head [1]. The following ports you maintain fail to build after this update: games/rtb http://package18.nyi.freebsd.org/data/head-amd64-PR195480-default/2014-11-29_14h36m35s/logs/errors/RealTimeBattle-1.0.8_10.log net-p2p/libtorrent http://package18.nyi.freebsd.org/data/head-amd64-PR195480-default/2014-11-29_14h36m35s/logs/errors/libtorrent-0.13.4_1.log www/squid http://package18.nyi.freebsd.org/data/head-amd64-PR195480-default/2014-11-29_14h36m35s/logs/errors/squid-3.4.9_1.log Usually, the -Werror warnings are pointing to actual bugs in the ports themselves. If you have a patch to fix the ports, please submit them in FreeBSD Bugzilla [2]. [1] https://lists.freebsd.org/pipermail/freebsd-current/2014-November/053570.html [2] https://bugs.freebsd.org/submit/ Cheers, Antoine on behalf of portmgr@ ___ 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: print/muttprint
On Sat, Oct 11, 2014 at 6:28 PM, Kurt Jaeger li...@opsec.eu wrote: Hi! mat@ mailed that USE_TEX=latex dvipsk should be used instead of the two additional run_deps. A side note: bapt switched from 'latex' to texlive: [...] Can you test if this works in your use-case and report the results ? Btw, what is your use-case ? How do you invoke muttprint and what does it call and what does it do in the end ? Does it really generate a .ps to send to the printer ? and yes, when you compile the port directly with # make install 'USE_TEX= texlive' pulls in Tex, but it does not if you compile the ports with poudriere. I'm surprised that USE_TEX=texlive in poudriere does not pull it in. Can you provide a build log to show this ? Hi, Not sure what you are talking about, but USE_TEX=texlive doesn't exit. Cheers, Antoine I brought this question up in freebsd-pkg@ but did not got any comments on this. I can revoke the change in my VM / poudriere and send in a complete log of the compilation of print/muttprint if someone is willing to dig into. Yes, please. For the moment, I have not found any other solution as the two additional lines. Well, if it solves your problem, then it's definitly a good sign 8-) -- p...@opsec.eu+49 171 3101372 6 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: print/muttprint
On Sat, Oct 11, 2014 at 6:42 PM, Kurt Jaeger li...@opsec.eu wrote: Hi! Not sure what you are talking about, but USE_TEX=texlive doesn't exit. I think Matthias refers to this: https://lists.freebsd.org/pipermail/svn-ports-all/2014-April/054544.html where USE_TEX=texlive was committed. I'm by no means an expert in the TeX ports universe, so any hint is appreciated. texlive is the default, USE_TEX=texlive no longer exists (and you should have an error if you try to use it) Cheers, Antoine ___ 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: Check for set Makefile options and compile accordingly
On Wed, Sep 10, 2014 at 12:10 AM, Oliver Mahmoudi olivermahmo...@gmail.com wrote: Hello, I am working on a new port here and have a few questions regarding the new style of handling Makefile options. The program I got, is configured in a non standard way, i.e. there is no configure script or the like. Depending on what modules/libraries you want to build along with the executable, pre-build: ${GMAKE} ${MAKE_ARGS} cfg is run, to configure the program's build system. This can be translated to: pre-build: ${GMAKE} include_modules=module_1 module_2 ... cfg I set up MAKE_ARGS in the following way: .if !empty (EXTRA_MODULES) MAKE_ARGS= include_modules=${EXTRA_MODULES} .endif About a year ago, when writing the original Makefile, I handled the situation like this: .if ${PORT_OPTIONS:MMYSQL} BUILD_DEPENDS+= ${LOCALBASE}/libexec/mysqld:${PORTSDIR}/databases/mysql56-server RUN_DEPENDS+:= ${BUILD_DEPENDS} EXTRA_MODULES+= db_mysql PLIST_SUB+= MYSQL= .else PLIST_SUB+= MYSQL=@comment .endif To get the port out there, folks now want me to change the way I handle the Makefile options. Therefore, the above if/else/endif block now now looks like this: OPT_ABOVEVARIABLE= YES OPTIONS_SUB= YES MYSQL_BUILD_DEPENDS= ${LOCALBASE}/libexec/mysqld:${PORTSDIR}/databases/mysql56-server # # This stuff now hangs loose # RUN_DEPENDS+:= ${BUILD_DEPENDS} EXTRA_MODULES+= db_mysql # # # Given the new style of handling Makefile options how do I handle passing my EXTRA_MODULES variable - there is more than just the one above - to the port's configure stage via MAKE_ARGS and how would I deal with the RUN_DEPENDS+:= ${BUILD_DEPENDS} situation? None of the situations offered on: https://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html match my given scenario. Any pointers? Hi, If the options helpers do not fit your needs, you can still use constructs like .include bsd.port.options.mk .if ${PORT_OPTIONS:MMYSQL} ... Cheers, Antoine ___ 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/rabbitmq-c-devel and cmake hints needed (PR 186690)
On Sun, Aug 24, 2014 at 10:21 PM, Kurt Jaeger li...@opsec.eu wrote: Hi! I'm trying to upgrade net/rabbitmq-c-devel and prepared a patch for it. If someone understands more about cmake and the magic behind it, I would appreciate it. It builds fine on my host populated with approx. 2200 packages: http://people.freebsd.org/~pi/misc/non-verbose-build.txt Building it in poudriere, some bin/ stuff is not build (why?) and the commands are displayed, so it's much more verbose (why is it more verbose?). http://people.freebsd.org/~pi/misc/verbose-build.txt Thanks for any hint! Hi, From Uses/cmake.mk: .if defined(BATCH) || defined(PACKAGE_BUILDING) CMAKE_VERBOSE= yes CMAKE_NOCOLOR= yes .endif For the tools, it seems they need POPT and you didn't select the option in poudriere. Cheers, Antoine ___ 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: mass commit needed: python breakage in pkgng repo
On Tue, Jul 22, 2014 at 7:09 PM, olli hauer oha...@gmx.de wrote: On 2014-07-22 17:34, Nick Hilliard wrote: sysutils/py-salt has been broken for the last couple of weeks. The resulting package didn't include the python egg info directory and as a result, py-salt crashed on startup. There a PR in bugzilla for this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191986 From what I can tell, this problem has been fixed by this commit: http://svnweb.freebsd.org/ports?view=revisionrevision=362364 So py-salt will need to be rebuilt in the freebsd pkgng repo, but because the fix was in bsd.python.mk, the port will need to have PORTREVISION bumped in order to flush out the broken version from the pkgng repo. I've attached a list of other ports which may also be broken (i.e. ports whose makefiles include the text USE_PYDISTUTILS but not PYDISTUTILS_AUTOPLIST). Some of these ports may also need to rebuilt, but without testing each one of them individually, it may not be be possible to tell which. Could someone consider doing a mass commit to each of these ports to bump PORTREVISION so that any potential breakage is flushed out of the pkg repos? Sorry, my mobile has taken the discussion out of list ... isn't it easier to bump python instead ? yep sure would, but that will force a rebuild of ~2700 ports instead of 300. I suspect even more then the 2300 ports (depening ports also counting) but this way really everything will be cached. Dont know if the snap for weekly build was already taken if not it would be an option tbh, i'm not familiar enough with the main repo build process + consequences to be able to assess how best to deal with this. Best to address this also to portmgr@ for decicission (added to CC) Hi, py-setuptools was updated on Wednesday 16th so all ports depending on it will be rebuilt during next bulk on the pkg builders. But I can still bump PORTREVISION on py-salt as for this specific port the missing egginfo is harmful? (for most other ports it's harmless) Cheers, Antoine ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Error: Orphaned: @unexec rmdir /home /dev/null 21 || : (PING)
On Mon, Jun 30, 2014 at 6:48 PM, Gerald Pfeifer ger...@pfeifer.com wrote: On Fri, 20 Jun 2014, Antoine Brodin wrote: Build with a non-standard PREFIX and LOCALBASE in /home/gerald/10-i386, make ports builds have been failing with the following for a bit (for lang/gcc49 among others): Running regression-test, checking for orphans, checking pkg-plist. Checking for pkg-plist issues (check-plist) === Parsing plist === Checking for items in STAGEDIR missing from pkg-plist Error: Orphaned: @unexec rmdir /home/gerald /dev/null 21 || : Error: Orphaned: @unexec rmdir /home /dev/null 21 || : Any ideas what is going on here? And what is adding those interesting @unexec rmdir entries? You can try to add NO_PREFIX_RMDIR=yes to your port when you test it. Testing PREFIX!=LOCALBASE often produces strange results anyway, in most cases people should test PREFIX=LOCALBASE != /usr/local and not PREFIX!=LOCALBASE. Yes, but this had been working without problems for many years. :-) And now only problem is this new (pkg-ng?) code and check-plist; apart from that things work. In my case PREFIX points to /scratch. It's LOCALBASE that points to /home/gerald/10-i386, so I am really puzzled about those @unexec rmdir's that want to remove my LOCALBASE. Why should any port or package meddle with LOCALBASE?? Hi, You can try attached patch. Cheers, Antoine Index: Mk/Scripts/check-stagedir.sh === --- Mk/Scripts/check-stagedir.sh(revision 359891) +++ Mk/Scripts/check-stagedir.sh(working copy) @@ -157,6 +157,14 @@ fi unset MTREE_FILE GNOME_MTREE_FILE + # Add LOCALBASE + a=${LOCALBASE} + while :; do + echo ${a} + a=${a%/*} + [ -z ${a} ] break + done + # Add in PREFIX if this port wants it if [ ${NO_PREFIX_RMDIR} -eq 0 ]; then a=${PREFIX} ___ 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: Handling of /var/db/fontconfig in poudriere builds ?
On Sun, Jun 29, 2014 at 11:06 AM, Kurt Jaeger p...@freebsd.org wrote: Hi! I'm trying to test devel/doxygen using poudriere and it complains about Error: Filesystem touched during build: extra: var/db/fontconfig/8585c715aba2802b7a927639155fa2e5-le64.cache-4 extra: var/db/fontconfig/91d79561d5e9964953bbdbfe91ce9175-le64.cache-4 extra: var/db/fontconfig/4c599c202bc5c08e2d34565a40eac3b2-le64.cache-4 extra: var/db/fontconfig/70c03b3e3294210779bec362c79986d7-le64.cache-4 extra: var/db/fontconfig/822b97c336d865461182de9b27503dbd-le64.cache-4 [...] Is there a way to handle or avoid this error ? Hi, The port shouldn't create those files during build. It doesn't here, do you have special options? Antoine ___ 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: Handling of /var/db/fontconfig in poudriere builds ?
On Sun, Jun 29, 2014 at 11:30 AM, Kurt Jaeger p...@freebsd.org wrote: Hi! I'm trying to test devel/doxygen using poudriere and it complains about Error: Filesystem touched during build: extra: var/db/fontconfig/8585c715aba2802b7a927639155fa2e5-le64.cache-4 [...] Is there a way to handle or avoid this error ? The port shouldn't create those files during build. Ah, ok. Well, I'm still unsure where those files are created. Any ideas ? It doesn't here, do you have special options? None that I'm aware of... /var/db/ports/devel_doxygen/options # This file is auto-generated by 'make config'. # Options for doxygen-1.8.7 _OPTIONS_READ=doxygen-1.8.7 _FILE_COMPLETE_OPTIONS_LIST=HTMLDOCS PDFDOCS QT4 OPTIONS_FILE_SET+=HTMLDOCS OPTIONS_FILE_SET+=PDFDOCS OPTIONS_FILE_SET+=QT4 and poudriere /etc/make.conf: DEVELOPER=yes USE_PACKAGE_DEPENDS=yes BATCH=yes WRKDIRPREFIX=/wrkdirs WITH_PKGNG=yes # DEFAULT_VERSIONS= perl5=5.20 php=5.5 python=3.4 DEFAULT_VERSIONS= perl5=5.20 php=5.5 Ok i can reproduce with PDFDOCS option turned on. The problem seems to come from the amsfonts, they do not properly regenerate the cache after install, and during the pdfdocs build something regenerates this cache. Adding a run_depends on fontconfig in the amsfonts port and using the @fc keyword may solve it. Cheers, Antoine ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Error: Orphaned: @unexec rmdir /home /dev/null 21 || : (PING)
On Fri, Jun 20, 2014 at 2:07 PM, Gerald Pfeifer ger...@pfeifer.com wrote: [ No ideas? Shall I just file a bug report? ] Build with a non-standard PREFIX and LOCALBASE in /home/gerald/10-i386, make ports builds have been failing with the following for a bit (for lang/gcc49 among others): Running regression-test, checking for orphans, checking pkg-plist. Checking for pkg-plist issues (check-plist) === Parsing plist === Checking for items in STAGEDIR missing from pkg-plist Error: Orphaned: @unexec rmdir /home/gerald /dev/null 21 || : Error: Orphaned: @unexec rmdir /home /dev/null 21 || : Any ideas what is going on here? And what is adding those interesting @unexec rmdir entries? Either these should not be added, or check-plist should not error out when seeing them. Hi, You can try to add NO_PREFIX_RMDIR=yes to your port when you test it. Testing PREFIX!=LOCALBASE often produces strange results anyway, in most cases people should test PREFIX=LOCALBASE != /usr/local and not PREFIX!=LOCALBASE. Cheers, Antoine ___ 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: Who broke staging as user?
On Wed, Jun 11, 2014 at 2:58 PM, Gerald Pfeifer ger...@pfeifer.com wrote: This is a new failure that I found when testing a (trivial) update to lang/gcc410 with some of my usual scripts: Compressing man pages (compress-man) === Installing ldconfig configuration file cannot create $WRKDIRPREFIX/stage/home/gerald/10-i386/libdata/ldconfig/gcc49: No such file or directory *** Error code 2 After scratching my head, I reran my tests for lang/gcc49 as in the tree today, and -- failure as well. Since I never commit an update to one of these ports without this kind of testing something must have broken this on June 6th or later. Digging into svn log $PORTSDIR/Mk a bit, here is my suspect: r357076 | antoine | 2014-06-08 21:25:54 + (Sun, 08 Jun 2014) | 8 lines Kill NO_LDCONFIG_MTREE, it is long dead Make USE_LDCONFIG work when PREFIX!=LOCALBASE, LDCONFIG_DIR and LDCONFIG_32DIR are expected in LOCALBASE Phabric:D195 Reviewed by:bapt With hat: portmgr For my test, LOCALBASE=/home/gerald/10-i386 and PREFIX=/scratch2/tmp/gerald/prefix. But, in general LOCALBASE may not be writeable, whereas PREFIX is, so I somehow doubt the logic to begin with. Though the failure here is a lack of ${MKDIR} in the staging directory somewhere it seems? Hi, I think that the problem is that your ${STAGEDIR}/${LOCALBASE} is not populated with the usual mtree (which includes the libdata/pkgconfig directory) You can try to remove the .if defined(NO_MTREE) / .endif around @${MKDIR} ${STAGEDIR}${LOCALBASE}/${LDCONFIG_DIR} in bsd.port.mk, although i'm not sure it's the right fix. Cheers, Antoine ___ 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: Who broke staging as user?
On Wed, Jun 11, 2014 at 3:22 PM, Antoine Brodin anto...@freebsd.org wrote: On Wed, Jun 11, 2014 at 2:58 PM, Gerald Pfeifer ger...@pfeifer.com wrote: This is a new failure that I found when testing a (trivial) update to lang/gcc410 with some of my usual scripts: Compressing man pages (compress-man) === Installing ldconfig configuration file cannot create $WRKDIRPREFIX/stage/home/gerald/10-i386/libdata/ldconfig/gcc49: No such file or directory *** Error code 2 After scratching my head, I reran my tests for lang/gcc49 as in the tree today, and -- failure as well. Since I never commit an update to one of these ports without this kind of testing something must have broken this on June 6th or later. Digging into svn log $PORTSDIR/Mk a bit, here is my suspect: r357076 | antoine | 2014-06-08 21:25:54 + (Sun, 08 Jun 2014) | 8 lines Kill NO_LDCONFIG_MTREE, it is long dead Make USE_LDCONFIG work when PREFIX!=LOCALBASE, LDCONFIG_DIR and LDCONFIG_32DIR are expected in LOCALBASE Phabric:D195 Reviewed by:bapt With hat: portmgr For my test, LOCALBASE=/home/gerald/10-i386 and PREFIX=/scratch2/tmp/gerald/prefix. But, in general LOCALBASE may not be writeable, whereas PREFIX is, so I somehow doubt the logic to begin with. Though the failure here is a lack of ${MKDIR} in the staging directory somewhere it seems? Hi, I think that the problem is that your ${STAGEDIR}/${LOCALBASE} is not populated with the usual mtree (which includes the libdata/pkgconfig directory) You can try to remove the .if defined(NO_MTREE) / .endif around @${MKDIR} ${STAGEDIR}${LOCALBASE}/${LDCONFIG_DIR} in bsd.port.mk, although i'm not sure it's the right fix. Please try attached patch. Cheers, Antoine Index: Mk/bsd.port.mk === --- Mk/bsd.port.mk (revision 357478) +++ Mk/bsd.port.mk (working copy) @@ -4018,7 +4018,7 @@ .endif .if ${USE_LDCONFIG} != ${LOCALBASE}/lib !defined(INSTALL_AS_USER) @${ECHO_MSG} === Installing ldconfig configuration file -.if defined(NO_MTREE) +.if defined(NO_MTREE) || ${PREFIX} != ${LOCALBASE} @${MKDIR} ${STAGEDIR}${LOCALBASE}/${LDCONFIG_DIR} .endif @${ECHO_CMD} ${USE_LDCONFIG} | ${TR} ' ' '\n' \ @@ -4040,7 +4040,7 @@ .endif .if !defined(INSTALL_AS_USER) @${ECHO_MSG} === Installing 32-bit ldconfig configuration file -.if defined(NO_MTREE) +.if defined(NO_MTREE) || ${PREFIX} != ${LOCALBASE} @${MKDIR} ${STAGEDIR}${LOCALBASE}/${LDCONFIG_32DIR} .endif @${ECHO_CMD} ${USE_LDCONFIG32} | ${TR} ' ' '\n' \ ___ 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 back to the heap
On Thu, Jun 5, 2014 at 10:22 PM, Rusty Nejdl rne...@ringofsaturn.com wrote: I've spent a few days trying to get these ports to support staging and to actually compile with any version of GCC or CLANG and I cannot. games/vegastrike-data games/vegastrike Currently the last release from the developer was 2 years ago. In reading threads, there are numerous patches flying around to get it to compile with clang or a more modern compiler. If/when the team behind vegastrike makes a new update, I might be up for taking over maintainership but for now, I think this port should be depricated and put back on the heap for possible deletion. Maybe someone else can pick this up but it is too much of a mess for my time. I still have one other port to beat into submission for staging. Thanks for the notice, I have reset maintainership and marked the ports deprecated. Cheers, Antoine ___ 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: drop maintainership of databases/pg_reorg, databases/postgresql-repmgr
On Tue, May 13, 2014 at 6:08 PM, Alexander Pyhalov a...@rsu.ru wrote: Hello. We don't use FreeBSD on our database server longer. Besides, I became tightly involved in OpenIndiana development and just don't have time enough to support FreeBSD ports I've created, so I'd like to drop manitainership for databases/pg_reorg, databases/postgresql-repmgr. I think it would be honest, because I just can't support them on adequate level. Hi, Thanks for letting us know, I have reset maintainer. Cheers, Antoine ___ 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: [mail/xmailbopx] Exactly what does unmaintained mean?
On Mon, Mar 31, 2014 at 4:57 PM, A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Hi all, The port mail/xmailbox is set to be removed soon because it has been unmaintained since 2000. In this case, does unmaintained refer to just the FreeBSD port, or to the software itself? And in either case, is there anything that can be done to prevent removal? Hi, Would you like to take maintainership of this port, and add stage support to it? Cheers, Antoine ___ 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 and p5- ports
On Sat, Mar 29, 2014 at 11:54 AM, Muhammad Moinur Rahman 5u623...@gmail.com wrote: Hi, I am facing a problem with perl related ports. Whenever I am building a p5-* ports I can see that the following files are leftover: @dirrm lib/perl5/site_perl @dirrm lib/perl5/5.16/man @dirrm lib/perl5/5.16 @dirrm lib/perl5 @dirrm %%SITE_PERL%%/mach/auto @dirrm %%SITE_PERL%%/mach @dirrm %%SITE_PERL%% @dirrm %%PERL5_MAN3%% Additionally perl5.16 is failing to build with lots of error in package step. Is it a problem with Perl or Poudriere? Thanks in advance. Hi, Is it during testport? If yes, by default testport tries to build with PREFIX different from LOCALBASE. You can use testport -n so use PREFIX=LOCALBASE. Cheers, Antoine ___ 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: bsd.kmod.mk conflicts with port STAGE'ing
On Fri, Mar 7, 2014 at 11:51 PM, Lev Serebryakov l...@freebsd.org wrote: Hello, FreeBSD. If software uses FreeBSD makefile infrastructure and build kernel module (with using .include bsd.kmod.mk), it could not be properly staged in ports, as kernel module is installed with install -o root -g wheel always. Is here any way to workaround this problem? Hi, Try: USES= kmod uidfix Cheers, Antoine ___ 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: LEGAL and your ports
On Mon, Feb 17, 2014 at 12:39 PM, Takefu tak...@airport.fm wrote: I do not understand. I want you to evaluate whether this patch is correct. --- libaacplus-2.0.2_2.patch begins here --- diff -ruN /usr/ports/audio/libaacplus/Makefile ./Makefile --- /usr/ports/audio/libaacplus/Makefile2013-12-11 23:35:36.0 +0900 +++ ./Makefile 2014-02-17 19:23:37.0 +0900 @@ -15,6 +15,8 @@ COMMENT= HE-AAC+ Codec as Shared Library RESTRICTED=unclear legal status, probably need licenses from 3GPP, Via Licensing and Coding Technologies +NO_CDROM= Distribution requires acceptance of license agreement +NO_PACKAGE=${NO_CDROM} CONFLICTS= aacplusenc-0* --- libaacplus-2.0.2_2.patch ends here --- Hi, According to the porters handbook: NO_CDROM or NO_PACKAGE should not be set along with RESTRICTED since the latter variable implies the former ones. http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-restrictions.html Cheers, Antoine ___ 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: STAGE and INFO
On Sun, Jan 26, 2014 at 11:13 PM, Montgomery-Smith, Stephen step...@missouri.edu wrote: I am trying to implement staging on the port graphics/plotutils. Right now it has the following line in Makefile: INFO= libxmi plotutils When I do make stage; make check-orphans I get info/dir Is this something I need to worry about? Hello, This should be ok. I you use poudriere testport or poudriere bulk -t to check your port, the info/dir orphan should not be reported (poudriere compares stage to / after the package was installed to detect stage orphans) Cheers, Antoine ___ 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: [QAT] r333268: 4x leftovers
On Sun, Nov 10, 2013 at 2:59 PM, Gerald Pfeifer ger...@pfeifer.com wrote: On Sat, 9 Nov 2013, Dmitry Marakasov wrote: * Ports-QAT (q...@redports.org) wrote: +gerald@ Staging support broke INFO= here. The INFO= infrastructure should take care of not leaving anything upon deinstallation and it did so for years. I looked into fixing this in Mk/bsd.*.mk but failed. Hi, You can try patch at: http://people.freebsd.org/~antoine/ports/stage-info_subdir.diff (totally untested) Cheers, Antoine ___ 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
[RFC] Stage support for PEAR classes and channels
Hi there, The patch below adds stage support to pear classes and pear channels (not devel/pear itself) http://people.freebsd.org/~antoine/ports/stage-pear.diff I verified on ~170 ports from devel that the content of the generated package differs only in the timestamp in channel .reg files between staged and unstaged. Please comment, Cheers, Antoine ___ 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/tcpflow
On Wed, Jun 12, 2013 at 12:52 PM, andrew clarke m...@ozzmosis.com wrote: Maybe it would be useful to have a make config option to disable cairo in the net/tcpflow port? The Cairo dependency pulls in about twenty X11 libraries that I'd prefer not to install on my server. Yes, cairo is needed to have a nice 1 page PDF summary. You can compile cairo with custom options if you don't want x11 etc. Cheers, Antoine ___ 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/devel/libgii] Respect PTHREAD_LIBS
Norikatsu Shigemura [EMAIL PROTECTED] wrote: Hi Antoine. I found a issue of not respect PTHREAD_LIBS. May I commit following patch? [snip] Approved. Is there something to submit upstream ? Can you replace INSTALLS_SHLIB=yes by USE_LDCONFIG=yes, while you are at it ? Cheers, Antoine ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]