Portsbase and maildir
I am going to submit that PORTSBASE should be something other than /usr/local/. My current preference (though not solid) is /ports/. I would like to reclaim /usr/local for true local (site-based, not distribution-based) things. (Example: local [site-based] scripts in /usr/local/s?bin/.) On a related note, I would like to see maildirmake separated out as a port of its own on which ports supporting Maildir depend. That way we avoid clunkiness like "/usr/local/bin/maildrop-maildirmake". (The first point most recently evidenced itself as "where do I put a symbolic link to maildrop-maildirmake called maildirmake?".) Thanks, Jim Trigg ___ 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"
Problem with nginx
When I try to build nginx using poudriere, I get an error in mod_zip even though I've made sure that HTTP_ZIP is unset. How can I correct this? /wrkdirs/usr/ports/www/nginx/work/mod_zip-74ef235/ngx_http_zip_module.c:74:4: error: no member named 'charset' in '' offsetof(ngx_http_zip_conf_t, charset), ^ ~~~ /usr/include/stddef.h:75:31: note: expanded from macro 'offsetof' #define offsetof(type, field) __offsetof(type, field) ^~ /usr/include/sys/cdefs.h:476:34: note: expanded from macro '__offsetof' #define __offsetof(type, field) __builtin_offsetof(type, field) ^~ 1 error generated. *** Error code 1 Stop. make[2]: stopped in /wrkdirs/usr/ports/www/nginx/work/nginx-1.16.1 *** Error code 1 Stop. make[1]: stopped in /wrkdirs/usr/ports/www/nginx/work/nginx-1.16.1 *** Error code 1 Stop. make: stopped in /usr/ports/www/nginx =>> Cleaning up wrkdir ===> Cleaning for nginx-1.16.1_2,2 build of www/nginx | nginx-1.16.1_2,2 ended at Sat Sep 14 23:20:55 EDT 2019 build time: 00:02:36 !!! build failure encountered !!! Thanks, Jim Trigg ___ 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: postfix and postfix-current
If you're using portmaster the best way is portmaster -o mail/postfix postfix-current Thanks, Jim Trigg On April 20, 2019 6:39:59 AM EDT, "@lbutlr" wrote: >I see today that > >===>>> postfix-current-3.4.20190106,5 > ===>>> New version available: postfix-current-3.5.20190330,5 > >What is the proper way to move from postfix-current-3.4.20190106,5 to >postfix-3.4.5 (mail/postfix)? > >I was on postfix current because the root postfix had not updated to >the 3.4 branch, I am not ready to move to 3.5 at this point. > >is it enough to simply pkg delete -f postfix-current-3.4.20190106,5 and >then postmaster mail/postfix or is there any other steps to take? > > >-- >'Everything will be all right. From History's point of view, that is. >There really isn't any other.' > > >___ >freebsd-ports@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to >"freebsd-ports-unsubscr...@freebsd.org" -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ 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"
rc script problems
How do I write an rc script to preserve the pid of a child process? The "port" I'm working with (technically a commercial package) has a startup script that launches a java process. I had written a simple rc wrapper around the script but have found it doesn't support stop because the pid captured is the script's pid rather than the java process's pid. Thanks, Jim Trigg ___ 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: Why portmaster try to install python 3.6 when I have 3.4 set in /etc/make.conf?
ISTR that there is a more generic variable that will cause make to work with all flavors instead of the default "common" set. Not where I can easily look up specifics right now... Thanks, Jim Trigg On January 10, 2018 3:59:17 PM EST, Stefan Esser wrote: >Am 10.01.18 um 21:30 schrieb Stefan Esser: >> Am 10.01.18 um 17:29 schrieb Lev Serebryakov: >>> I have system with pre-FLAVORed ports installed, and try to update >>> ports with new version of "portmaster". My "/etc/make.conf" >contains: >>> >>> DEFAULT_VERSIONS+= python2=2.7 >>> DEFAULT_VERSIONS+= python3=3.4 >>> DEFAULT_VERSIONS+= python=3.4 >>> >>> But "portmaster -a" try to install python 3.6: >>> >>> ===>>> All >> py34-pip-9.0.1 (12/12) >>> ===>>> The devel/py3-pip port moved to devel/py-pip@py36 >>> ===>>> Reason: Moved to a flavored, generic, version >>> [...] >>> ===>>> All >> py34-pip-9.0.1 >> devel/py-setuptools@py36 >> >>> lang/python36 (14/14) >> >> Another example that the FLAVOR feature is not well designed :( >> >> The entry in /usr/ports/MOVED maps devel/py3-pip to devel/py-pip@py36 >> even though building that port with FLAVOR=py34 builds the correct >> version with the expected dependency on Python-3.4. >> >> If at least the output of "make pretty-flavors-package-names" did >hint >> at the existence of a package for FLAVOR=py34, I could make >portmaster >> override the wrong FLAVOR obtained from the MOVED file. >> >> But the output of that command is: >> >> $ cd /usr/ports/devel/py-py >> $ make pretty-flavors-package-names >> py27: py27-py-1.5.2 >> py36: py36-py-1.5.2 > >I have just checked, that the ports infrastructure already kind of >supports this case. With PYTHON3_DEFAULT=3.4 set in /etc/make.conf, >it is possible to determine the flavor that corresponds to the >package to be upgraded: > >$ PYTHON3_DEFAULT=3.4 make pretty-flavors-package-names >py27: py27-py-1.5.2 >py34: py34-py-1.5.2 > >I'll try to get this feature implemented in portmaster, but it may >take a few days ... > >Regards, STefan >___ >freebsd-ports@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to >"freebsd-ports-unsubscr...@freebsd.org" -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ 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 portmaster fails to build devel/py-libzfs@py36 because of failing cython
On December 15, 2017 4:50:53 AM EST, Johan Hendriks wrote: >Hello all. >First of all thank you for the update of portmaster, much appreciated. > >When i am updating my ports, portmaster fails with the following error. > >> Compressing man pages (compress-man) >===>>> Starting check for runtime dependencies >===>>> Gathering dependency list for lang/cython@py36 from ports >===>>> Dependency check complete for lang/cython@py36 > >===>>> devel/py-libzfs@py36 1/10 >> lang/cython@py36 (1/1) > >===> Installing for py36-cython-0.26 >===> Checking if py36-cython already installed >===> Registering installation for py36-cython-0.26 as automatic >Installing py36-cython-0.26... >pkg-static: py36-cython-0.26 conflicts with cython3-0.26 (installs >files >into the same place). Problematic file: /usr/local/bin/cygdb-3.6 >*** Error code 70 > >Stop. >make: stopped in /usr/ports/lang/cython > >===>>> Installation of py36-cython-0.26 (lang/cython@py36) failed >===>>> Aborting update > >===>>> Update for lang/cython@py36 failed >===>>> Aborting update > >===>>> Update for devel/py-libzfs@py36 failed >===>>> Aborting update > > >Is there someting i can try or do? Question: is 3.6 your default python version? I've discovered that the current version of portmaster uses python default version for dependencies when building a flavored port. Thanks, Jim Trigg -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ 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 portmaster fails to build devel/py-libzfs@py36 because of failing cython
On 12/15/2017 11:12 AM, Stefan Esser wrote: Am 15.12.17 um 14:25 schrieb Stefan Esser> Hmmm, now I see what's the problem: The package name seems to have been changed during the conversion to a flavored port (from "cython3-0.26.tbz" to "py36-cython-0.26.tar.bz"). This is not typical of ports that use flavors now, in general they generate packages under the same name as the non-flavored port did. I have to see, whether I can easily detect this case - the current logic that distinguishes between fresh installs and re-installs does not see that the old version needs to be deleted before installing the new one. For now the advice to manually delete the cython3 port is right and will let you install the new version. I'm sorry, but fixing this problem will take quite some effort ... The problem is, that portmaster operates in phases and recursively invokes itself with an always smaller set of options. While knows that the port origin has moved in one invocation, it then goes on and just calls itself to build and install with only the new origin (in this case "lang/cython@py36"). It is not possible to derive the old package name from that information, portmaster must assume, that the package name (sans version) did not change, it can then lookup the nane of the package to be replaced in the package DB. But in the case of this port, the origin changed and the package name changed at the same time, and I'd need to have at least one of these parameters unchanged to lookup the old package name to de-install it before installing the new version. I have plans to refactor portmaster and completely rewrite the logic that builds and installs packages, but this is a major undertaking and earlier maintainers have given up after trying. So please accept that it may be necessary to manually remove a package in case both port directory (origin) and package name change at the same time. All information is there at a point, but the structure of the program does not allow to easily access it when actually needed. As I said in a reply to an earlier message (that I just sent), I think this is exactly what the -o switch was meant for. portmaster -o lang/cython@py36 cython3 The question is whether the flavor support will work with the -o switch. Thanks, Jim Trigg ___ 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 portmaster fails to build devel/py-libzfs@py36 because of failing cython
On 12/15/2017 08:25 AM, Stefan Esser wrote: Am 15.12.17 um 11:21 schrieb Kubilay Kocak: On 15/12/2017 8:50 pm, Johan Hendriks wrote: Hello all. Hi Johan First of all thank you for the update of portmaster, much appreciated. When i am updating my ports, portmaster fails with the following error. > Compressing man pages (compress-man) ===>>> Starting check for runtime dependencies ===>>> Gathering dependency list for lang/cython@py36 from ports ===>>> Dependency check complete for lang/cython@py36 ===>>> devel/py-libzfs@py36 1/10 >> lang/cython@py36 (1/1) ===> Installing for py36-cython-0.26 ===> Checking if py36-cython already installed ===> Registering installation for py36-cython-0.26 as automatic Installing py36-cython-0.26... pkg-static: py36-cython-0.26 conflicts with cython3-0.26 (installs files Well, actually portmaster is expected to deal with that conversion of the cython3 port. I have tested the upgrade of individual ports and of all ports that are either back-level or where the ORIGIN changed (as in the case of this particular port). Hmmm, now I see what's the problem: The package name seems to have been changed during the conversion to a flavored port (from "cython3-0.26.tbz" to "py36-cython-0.26.tar.bz"). This is not typical of ports that use flavors now, in general they generate packages under the same name as the non-flavored port did. I have to see, whether I can easily detect this case - the current logic that distinguishes between fresh installs and re-installs does not see that the old version needs to be deleted before installing the new one. For now the advice to manually delete the cython3 port is right and will let you install the new version. Would using -o work? portmaster -o lang/cython@py36 cython3 Thanks, Jim Trigg ___ 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: Working on FLAVOR support in portmaster
I volunteer to test. Thanks, Jim Trigg On December 5, 2017 4:35:05 AM EST, Torsten Zuehlsdorff wrote: >Aloha Stefan, >On 05.12.2017 08:35, Stefan Esser wrote: >> Am 05.12.17 um 00:43 schrieb Tatsuki Makino: >>> By the way, where is the clever way to update to flavor? >>> I am using portmaster. >> >> I'm working on FLAVOR support in portmaster. My version did already >build >> all updated ports, the FLAVOR parameter is passed to build >sub-processes, >> but there is still some confusion between multiple flavored versions >of the >> same port (installing the py27 version wants to deinstall the py36 >version >> and vice versa), which I still have to fix. > >Great news. I was starting today and just read your email. Lucky me :D > >> My work version has all non PKG_NG support stripped, but that is >mainly to >> not waste effort fixing irrelevant sub-routines. >> >> Is it acceptable, to have portmaster stop supporting the old package >system? >> AFAIK, there is no way that a modern ports tree with flavor support >works >> with a non-PKG_NG infrastructure? > >This was something i aimed for in portmaster 2 since many changes were >very subtle and there is no test-suite. > >But if there are some volunteers to test, i'm fine with it right now. > >Greetings, >Torsten >-- >Support me at: >https://www.patreon.com/TorstenZuehlsdorff >___ >freebsd-ports@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to >"freebsd-ports-unsubscr...@freebsd.org" -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ 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: Perl broken after upgrade
Specifics are always a good idea. What versions did you update from and to? What command did you use? (Pkg, portmaster, make reinstall, etc.) Thanks, Jim Trigg On August 20, 2017 8:42:31 PM EDT, AN wrote: >After a recent update, it seems things that depend on Perl are broken. >Any suggestions to fix are greatly appreciated. Thanks in advance. > > ># uname -aK >FreeBSD mail.x.x 12.0-CURRENT FreeBSD 12.0-CURRENT #3 r322714: Sun Aug >20 06:05:58 EDT 2017 root@mail.x.x:/usr/obj/usr/src/sys/MYKERNEL >amd64 1200040 > > ># sa-update >Socket.c: loadable library and perl binaries are mismatched (got >handshake >key 0xd200080, needed 0xdf00080) > >___ >freebsd-ports@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to >"freebsd-ports-unsubscr...@freebsd.org" -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ 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: php71-pdo_sqlite won't build with poudriere
On 7/19/2017 3:44 AM, Torsten Zuehlsdorff wrote: > On 19.07.2017 06:23, Jim Trigg wrote: >> I'm trying to set up a poudriere repository, and php71-pdo_sqlite >> refuses to build. >> >> [00:01:37] >> [02][00:00:18] Finished build of >> databases/php71-pdo_sqlite: Failed: build-depends >> >> But php71-pdo_sqlite properly depends (runtime) on php71-pdo. >> >> Why can't the jail find the shared library? I thought that's what >> poudriere was all about... >> >> (Note: formerly a satisfied portmaster user...) > > Just a guess in the wild: did you set PHP default version to 7.1 in > /etc/make.conf? > > Otherwise please send me the error-log. No, it's the same thing that was biting me back in December on 7.0, but I had given up on poudriere then by the time the solution was pointed out to me. The answer is in pkg-message for 7.0 but not 7.1: If you are building PHP-based ports in poudriere(8) with ZTS enabled, add WITH_MPM=event to /etc/make.conf to prevent build failures. Thanks, Jim Trigg --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ 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"
php71-pdo_sqlite won't build with poudriere
I'm trying to set up a poudriere repository, and php71-pdo_sqlite refuses to build. [00:01:37] >> [02][00:00:18] Finished build of databases/php71-pdo_sqlite: Failed: build-depends But php71-pdo_sqlite properly depends (runtime) on php71-pdo. Why can't the jail find the shared library? I thought that's what poudriere was all about... (Note: formerly a satisfied portmaster user...) Thanks, Jim --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ___ 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: The future of portmaster [and of ports-mgmt/synth]
If you can give me access to a development system, I'll help. (I only have a production server for the domains I host for a few not-for-profit organizations, and my home server is currently out of service with a bad power supply.) Jim Trigg On May 30, 2017 8:10:17 PM EDT, Kevin Oberman wrote: >On Tue, May 30, 2017 at 2:53 PM, Mark Linimon >wrote: > >> On Tue, May 30, 2017 at 11:46:46PM +0200, Per olof Ljungmark wrote: >> > Hello, I have not followed this thread before but just wanted to >say >> > that I use portmaster extensively, it works for us and I would miss >> > it if it went. Are there actually plans to retire it? >> >> To reiterate the status: >> >> * some extensive changes to the ports framework are coming; >> * these will require large changes to all the port upgrade tools; >> * no one has stepped forwards to offer to do the work for anything >>other than poudriere AFAIK. >> >> If no one does the work, at the time the large changes come, the >> other tools will break. >> >> People have been wanting subpackages (aka flavors) for many years; >> IIUC these are parts of the changes that are coming. >> >> Someone needs to step forwards and say "yes, I will do the work." >> >> mcl > > >Since portmaster is still popult and since the only solutions that >looks to >be available in the near term are pouderiere or raw make, neither >terribly >viable for many, I will look into updating portmaster to deal with >'flavors'. This looks fairly straight forward and I my have the sh >capability to manage it. (And then again, I am far from a great shell >person, so I may well be wrong.) I have looked at Doug's script and it >is >pretty readable, but writing may require help. > >Can someone point me where to look for documentation on flavors? I have >poked around the wiki, but to no avail. Unless there is documentation >on >what needs to be done, doing it will be hopeless and waiting for the >packaging system to updated means portmaster WILL be broken for some >period >of time. >-- >Kevin Oberman, Part time kid herder and retired Network Engineer >E-mail: rkober...@gmail.com >PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 >___ >freebsd-ports@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to >"freebsd-ports-unsubscr...@freebsd.org" -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ 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 and packages
ISTR that it's Thunar that depends on Samba by default. Jim On May 4, 2017 7:18:46 AM MDT, RW via freebsd-ports wrote: >On Thu, 04 May 2017 08:09:47 -0400 >scratch65...@att.net wrote: >> >> I can't imagine what code could possibly be in thunar and samba >> that the xfce desktop would need, particularly since the desktop >> is very simple, and also because I've never got samba >> functionality for free after installing xfce which if you're >> right I should have done. But I'll check on that, and report >> back. > >AFAIK samba isn't a dependency of XFCE. I don't have it and it's not in >the output of make all-depends-list. > >Thunar is scarcely "unrelated", it's the XFCE integrated file manager. >XFCE uses the libthunarx library if built with the Thunar option. > >If you want something without integrated utilities you might be better >off with a window manager, like Fluxbox, rather than a desktop >environment. > >It is possible to have XFCE without THUNAR from ports, or by building >custom packages. >___ >freebsd-ports@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to >"freebsd-ports-unsubscr...@freebsd.org" -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ 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: Perl - what is the default?
On 2017-04-18 15:22, Rainer Hurling wrote: Am 18.04.2017 um 16:56 schrieb Mathieu Arnold: Le 18/04/2017 à 15:59, Jim Trigg a écrit : According to UPDATING as of 20161103, "The default Perl version has been switched to Perl 5.24." However, when I follow the instructions Yes, I added "DEFAULT_VERSIONS+= perl=5.24" to /etc/make.conf, and grep confirms that that is the only incidence of perl in the file. Perhaps, it is only a small typo at your side (missing number 5)? DEFAULT_VERSIONS+= perl=5.24 instead of DEFAULT_VERSIONS+= perl5=5.24 But did you add: DEFAULT_VERSIONS+= perl5=5.24 like the message says you have to ? If you did, it is possible that you have a really really old system and you still have a /usr/local/etc/perl5_version file, you should remove it. Yes, you are both correct. I misread UPDATING when modifying make.conf. Thanks, Jim Trigg ___ 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"
Perl - what is the default?
According to UPDATING as of 20161103, "The default Perl version has been switched to Perl 5.24." However, when I follow the instructions there to switch, I get the following message (after running portsnap fetch update manually even though it runs automatically every night): " This is *NOT* the DEFAULT perl version It will *NOT* install /usr/local/bin/perl It will *ONLY* install /usr/local/bin/perl5.24.1 The default Perl version currently is 5.20." Yes, I added "DEFAULT_VERSIONS+= perl=5.24" to /etc/make.conf, and grep confirms that that is the only incidence of perl in the file. Thanks, Jim Trigg ___ 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: The ports collection has some serious issues
On 12/19/2016 09:02 AM, John Marino wrote: On 12/18/2016 23:42, Jim Trigg wrote: On 12/18/2016 02:24 AM, John Marino wrote: 2) portmaster's dirty build method is inferior to clean environment builds (true) 3) There is better and official alternative (true) Maybe. I have a case where portmaster (on my current production box) builds fine but poudriere (on my intended replacement production box) does not. Case in point: php70-pdo_*. The first time I tried a build pdo_sqlite failed. This time (after correcting other ports' option problems) pdo_mysql fails for basically the same reason - pdo_* cannot find pdo because pdo thinks PHP_EXT_DIR=20151012-zts but pdo_* thinks PHP_EXT_DIR=20151012 - log for the latter below signature. Yet doing the build with postmaster works fine. Wasn't that a global bug that was fixed?7 I don't know; I can't find any record of it...\ You logic is faulty IMO. All binary packages produced officially for FreeBSD are built with poudriere. If poudriere can't build it due to a bug in the port itself, then nobody gets the package. Obviously that's unacceptable, so the port bug gets fixed, quickly. All binary packages produced officially for FreeBSD are built with poudriere *with default options*. ZTS is not the default (even though it's needed in most cases for mod_php and apache). So it sounds like you're saying that poudriere is too strict at enforcing correctness and you need something more forgiving? No, that's not what I'm saying. I can't find anything online showing that this problem has been reported. I can't reproduce it using the tool that I've been using for years (portmaster). Therefore my first assumption was that the problem was the new tool I had just started using. Note: while my phrasing may have been poor, I was not meaning to imply that the tool (poudriere) was necessarily broken, just that I couldn't figure out what was going wrong and that it seemed (based on my data sample) to be poudriere rather than the port. Having now tested using the ports tree directly (make -C /usr/ports/databases/php70-pdo_mysql on a basically clean ports tree with "OPTIONS_SET+= ZTS" in /etc/make.conf) and gotten the same failure as with poudriere, I now have no idea how it worked in portmaster, and acknowledge that it is a problem with the port. Unfortunately, port maintainers break the tree. Usually the big breaks are avoid with EXP-RUNs but it's common to see updates where downstream dependencies weren't tested and break (aside: IMO this it is the responsibility of the person updating the first port to verify the deps still build but not everyone does this). So sometimes you hit a tree break and that's what happened. It was fixed right? The bottom line: if a port doesn't build on poudriere and synth, the issue must be fixed, not worked around by using a tool incapable of detecting it. That's how most of the "I use portmaster and this doesn't work" topics get started. It doesn't seem to have been fixed, since I'm still seeing the error. I'm saying that 90% of the time portmaster works for me, and when it doesn't I can figure out a solution 90% of that time. I haven't gotten poudriere to work for me yet given the set of options I need set. 4) There's a second, even more effective alternative for x86 platforms (true) I can not as yet contest this. I haven't tried synth because if poudriere works it will have further value add for me (as a port maintainer I can build my port in multiple environments on a single box). Dealing with the conversion factor isn't worth it to me for the alleged gains synth brings. I am a big supporter of poudriere. While many people find they prefer synth and enjoy its performance advantage, I will never tell a poudriere user to switch if they are happy with poudriere. But you will tell a portmaster user to switch if they are happy with portmaster because it doesn't do things the way you think they should be done... Never mind that the whole pkgng system was forced on us willy-nilly, and it's the main reason there are problems with portmaster. Note that the "cannot as yet contest this" is because I'm not convinced that synth is "more effective" than poudriere - I expect that they are each better suited for a particular use case. The difference is that as far as I can tell, poudriere is satisfactory for the use case synth is designed for, but synth is not suited for the use case poudriere was initially intended for. (Note that a primary use of poudriere is/was to replace the now extinct port tinderbox.) Jim Trigg ___ 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: The ports collection has some serious issues
On 12/18/2016 02:24 AM, John Marino wrote:
2) portmaster's dirty build method is inferior to clean environment
builds (true)
3) There is better and official alternative (true)
Maybe. I have a case where portmaster (on my current production box)
builds fine but poudriere (on my intended replacement production box)
does not.
Case in point: php70-pdo_*. The first time I tried a build pdo_sqlite
failed. This time (after correcting other ports' option problems)
pdo_mysql fails for basically the same reason - pdo_* cannot find pdo
because pdo thinks PHP_EXT_DIR=20151012-zts but pdo_* thinks
PHP_EXT_DIR=20151012 - log for the latter below signature. Yet doing the
build with postmaster works fine.
4) There's a second, even more effective alternative for x86 platforms
(true)
I can not as yet contest this. I haven't tried synth because if
poudriere works it will have further value add for me (as a port
maintainer I can build my port in multiple environments on a single
box). Dealing with the conversion factor isn't worth it to me for the
alleged gains synth brings.
--
Jim Trigg
Log for php70-pdo_mysql
>> Building databases/php70-pdo_mysql
build started at Sun Dec 18 23:53:21 EST 2016
port directory: /usr/ports/databases/php70-pdo_mysql
building for: FreeBSD freebsd_10-3x64-HEAD-job-04 10.3-RELEASE-p14
FreeBSD 10.3-RELEASE-p14 amd64
maintained by: t...@freebsd.org
Makefile ident: $FreeBSD: head/databases/php70-pdo_mysql/Makefile
422569 2016-09-21 15:43:47Z tz $
Poudriere version: 3.1.14
Host OSVERSION: 1003000
Jail OSVERSION: 1003000
---Begin Environment---
SHELL=/bin/csh
UNAME_v=FreeBSD 10.3-RELEASE-p14
UNAME_r=10.3-RELEASE-p14
BLOCKSIZE=K
MAIL=/var/mail/root
STATUS=1
ARCH=amd64
SAVED_TERM=screen
MASTERMNT=/srv/poudriere/data/.m/freebsd_10-3x64-HEAD/ref
UID=0
FORCE_PACKAGE=yes
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin
_JAVA_VERSION_LIST_REGEXP=1.6\|1.7\|1.8\|1.6+\|1.7+\|1.8+
POUDRIERE_BUILD_TYPE=bulk
PKGNAME=php70-pdo_mysql-7.0.14
OSREL=10.3
_OSRELEASE=10.3-RELEASE-p14
PYTHONBASE=/usr/local
OLDPWD=/
_SMP_CPUS=4
PWD=/srv/poudriere/data/.m/freebsd_10-3x64-HEAD/ref/.p/pool
HAVE_COMPAT_IA32_KERN=YES OPSYS=FreeBSD
MASTERNAME=freebsd_10-3x64-HEAD
SCRIPTPREFIX=/usr/local/share/poudriere
_JAVA_VENDOR_LIST_REGEXP=openjdk\|oracle\|sun
USER=root
HOME=/root
POUDRIERE_VERSION=3.1.14
SCRIPTPATH=/usr/local/share/poudriere/bulk.sh
CONFIGURE_MAX_CMD_LEN=262144
LIBEXECPREFIX=/usr/local/libexec/poudriere
LOCALBASE=/usr/local
PACKAGE_BUILDING=yes
_JAVA_OS_LIST_REGEXP=native\|linux
OSVERSION=1003000
---End Environment---
---Begin OPTIONS List---
===> The following configuration options are available for
php70-pdo_mysql-7.0.14:
MYSQLND=on: Use MySQL Native Driver
===> Use 'make config' to modify these settings
---End OPTIONS List---
--CONFIGURE_ARGS--
--with-pdo-mysql=mysqlnd --with-php-config=/usr/local/bin/php-config
--prefix=/usr/local ${_LATE_CONFIGURE_ARGS}
--End CONFIGURE_ARGS--
--CONFIGURE_ENV--
XDG_DATA_HOME=/wrkdirs/usr/ports/databases/php70-pdo_mysql/work
XDG_CONFIG_HOME=/wrkdirs/usr/ports/databases/php70-pdo_mysql/work
HOME=/wrkdirs/usr/ports/databases/php70-pdo_mysql/work TMPDIR="/tmp"
SHELL=/bin/sh CONFIG_SHELL=/bin/sh
AUTOCONF=/usr/local/bin/autoconf-2.69
AUTOCONF_DIR=/usr/local/share/autoconf-2.69
AUTOHEADER=/usr/local/bin/autoheader-2.69
AUTOIFNAMES=/usr/local/bin/ifnames-2.69
AUTOM4TE=/usr/local/bin/autom4te-2.69
AUTORECONF=/usr/local/bin/autoreconf-2.69
AUTOSCAN=/usr/local/bin/autoscan-2.69
AUTOUPDATE=/usr/local/bin/autoupdate-2.69 AUTOCONF_VERSION=2.69
CONFIG_SITE=/usr/ports/Templates/config.site lt_cv_sys_max_cmd_len=262144
--End CONFIGURE_ENV--
--MAKE_ENV--
XDG_DATA_HOME=/wrkdirs/usr/ports/databases/php70-pdo_mysql/work
XDG_CONFIG_HOME=/wrkdirs/usr/ports/databases/php70-pdo_mysql/work
HOME=/wrkdirs/usr/ports/databases/php70-pdo_mysql/work TMPDIR="/tmp"
NO_PIE=yes WITHOUT_DEBUG_FILES=yes WITHOUT_KERNEL_SYMBOLS=yes
SHELL=/bin/sh NO_LINT=YES AUTOCONF=/usr/local/bin/autoconf-2.69
AUTOCONF_DIR=/usr/local/share/autoconf-2.69
AUTOHEADER=/usr/local/bin/autoheader-2.69
AUTOIFNAMES=/usr/local/bin/ifnames-2.69
AUTOM4TE=/usr/local/bin/autom4te-2.69
AUTORECONF=/usr/local/bin/autoreconf-2.69
AUTOSCAN=/usr/local/bin/autoscan-2.69
AUTOUPDATE=/usr/local/bin/autoupdate-2.69 AUTOCONF_VERSION=2.69
PREFIX=/usr/local LOCALBASE=/usr/local LIBDIR="/usr/lib" CC="cc"
CFLAGS="-O2 -pipe -fstack-protector -fno-strict-aliasing" CPP="cpp"
CPPFLAGS="" LDFLAGS=" -fstack-protector" LIBS="" CXX="c++"
CXXFLAGS="-O2 -pipe -fstack-protector -fno-strict-aliasing "
MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install -s -m 555"
BSD_INSTALL_LIB="install -s -m 444" BSD_INSTALL_SCRIPT="install -m
555" BSD_INSTALL_DATA=
Re: rc script problem - pidfile not being recognised
On 2015-09-14 13:32, RW via freebsd-ports wrote: On Sat, 12 Sep 2015 08:02:11 -0700 (PDT) Roger Marquis wrote: RW via freebsd-ports wrote: > You'd rather an rc script fails at run-time and shuts down the wrong > daemon than fail when the script is being developed? It's not so much where the script fails than that it fails in the first place. Neither a pidfile nor a command_interpreter needs to be required for an rc scripts to work. These are nice features but making them mandatory is at best a sort of premature optimization. It's not mandatory; you only need to define it if you want to be able to stop an interpreted daemon using the default method. If you have some other way of shutting down a daemon without knowing its name and PID then you can just supply a stop function to do it. One easy fix would be to have stoprc first check the entire process command and then shift it by one and check again... Then it would work for both binaries and scripts without a special variable for scripts. Jim Trigg ___ 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: Problem building maildrop with exim as MTA
On 2015-06-10 15:45, Carmel NY wrote: On Tue, 09 Jun 2015 23:59:29 -0400, Jim Trigg stated: Any suggestions as to how to fix this? I'm attempting to migrate from one host running Postfix to a new host running Exim but want to continue my maildrop support. (The switch is an attempt to reduce backscatter by doing more antispam during the SMTP session rather than after message acceptance.) I have a question regarding "backscatter". Why are you accepting mail for non existent clients? I'm not. I'm accepting mail for the request interface of the mailing lists I host, and the return addresses are forged so the automated replies can't go through. Thanks, Jim Trigg ___ 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"
Problem building maildrop with exim as MTA
When I try to build maildrop after installing exim as my primary mta I get the following error: checking location of system mailboxes... configure: error: Cannot determine default mailbox configure: error: ./configure failed for libs/maildrop ===> Script "configure" failed unexpectedly. Please report the problem to madpi...@freebsd.org [maintainer] and attach the "/usr/ports/mail/maildrop/work/maildrop-2.8.2/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Any suggestions as to how to fix this? I'm attempting to migrate from one host running Postfix to a new host running Exim but want to continue my maildrop support. (The switch is an attempt to reduce backscatter by doing more antispam during the SMTP session rather than after message acceptance.) Thanks, Jim Trigg ___ 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 requesting committer action for staging cleanup
This is the second request, and as it is less than two weeks to the
deadline I'm getting concerned. I am the maintainer of mail/ecartis. A
user has graciously done the conversion to staging for me and submitted
it as PR 190753; could someone please commit it? I have annotated the
PR with my approval.
Thanks,
Jim Trigg
___
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: Update php from 5.4 to 5.5 ?
Quoting "Matthew D. Fuller" :
On Wed, Jun 18, 2014 at 10:05:46PM +0200 I heard the voice of
Melvyn Sopacua, and lo! it spake thus:
You can do the following:
pkg query -e '%o ~ */php5-*' '%o'| while read origin; do \
new_origin=`echo ${origin} | sed -e 's/php5-/php55-/'`
echo portmaster -o ${new_origin} ${origin}; done > update.sh
You could just use 'pkg set -o' on these instead to shuffle the origin
in the pkgdb, then just a regular round of
portmaster/portupgrade/whatever will look at versions in the new
place. That's equivalent to how I've done such migrations in the past
with pkgog (creepy sed'ery through /var/db/pkg).
That sounds clever, but I've been trying to come up with a syntax that
actually works. What I think will work (once my current portmaster
-aRf finishes -- don't ask) is:
pkg query -e '%o ~ */php5-*' '%o'|while read origin; do \
new_origin=`echo ${origin} | sed -e 's/php5-/php55-/'`
echo y | pkg -o ${origin}:${new_origin}; done
But I'm not completely sure.
Jim Trigg
___
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"
Committer action requested - staging cleanup
I am the maintainer of mail/ecartis. A user has graciously done the conversion to staging for me and submitted it as PR 190753; could someone please commit it? I have annotated the PR with my approval. Thanks, Jim Trigg - Forwarded message from "Matthew D. Fuller" - Date: Sat, 7 Jun 2014 09:18:22 -0500 From: "Matthew D. Fuller" To: Jim Trigg Subject: ecartis port cleanup (was Re: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.) User-Agent: Mutt/1.5.23 (2014-03-12) Jim, > Got some time tonite to mess with it. 2 patches attached: one for > the ports UIDs/GIDs file, the other for the ecartis port. Just submitted them in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190753 too so they don't get lost. -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. - End forwarded message - ___ 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"
Integrating with pkg
I'm looking to port a utility from Ubuntu, and need to know what hooks there are in pkg. I want to port etckeeper, a tool that automates version control for /etc (and in our case $PREFIX/etc). Its current implementation uses hooks in apt to automatically check in changes when a package is installed/updated; I'm wondering what I can do to support that functionality (checking in changes when a package or the base system is installed/updated) in FreeBSD. Thanks, Jim Trigg ___ 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: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
On Sat, May 10, 2014 11:33 am, Bryan Drewery wrote: > You are receiving this mail as it affects FreeBSD ports that you maintain. > > This decision was not easy, but if a port is not being staged after > almost a year, we wonder if the ports are actually maintained and > updated for releases and security issues. In my case, I missed the call to convert *all ports* to staging, as my pants have been bankrupt for about a year (working on restarting the upstream of the port I'm maintainer for). This may have been exacerbated by an interaction of greylisting and duplicate elimination that I just realized occurs - messages get past greylisting faster through the list than direct, so for messages that are sent both to the list and directly to me the copy that gets put in the list folder gets kept instead of the one that would go into my inbox. I will have a very hard time finishing converting to staging in three months - A. I have a day job. B. This port's current configuration (inherited from the previous maintainer) is sufficiently kludgy that I will probably have to rewrite it from scratch. (I've been trying over the weekend to hack it into shape but am realizing that I have to give up and rewrite the whole mess.) Jim Trigg Maintainer, mail/ecartis ___ 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: Fallout from UPDATING entry 20140416: gtk3 vs. libxcb
On Thu, April 17, 2014 4:49 pm, Tijl Coosemans wrote: > The UPDATING entry has been updated. It now says: > > portmaster -r freetype2 -r libxml2 -r pixman -r freeglut -r libxcb > > So everything that depends on libxcb must also be rebuilt. This does not fix things for me - I have php53 installed, and php53-gd explicitly depends on the old versioning of libfreetype2.so. Having searched to see what ports depend explicitly on libfreetype2, I discover that it is the only one; I will be submitting a PR on php53 to change its dependence on print/freetype2 to libfreetype2.so generically as the other 7 ports do. Thanks, Jim Trigg ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Anyone having problems with CMake 2.8.12.1_3 and ftp/curl?
On Sun, March 9, 2014 9:53 am, Raphael Kubo da Costa wrote: > Raphael Kubo da Costa writes: > >> Has anyone else experienced the same issue? > > I've finally managed to reproduce the issue locally by installing > security/openssl. A bit late, but FWIW I'm seeing it on 9.2-RELEASE as well. Thanks, Jim Trigg ___ 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: Searching the port tree with portmaster?
On Thu, Aug 15, 2013 at 09:45:30AM -0600, LuKreme wrote: > On 15 Aug 2013, at 00:56 , Sergey V. Dyatko wrote: > > > man ports > > > /search[enter] > > cd /usr/ports && make search name=pear- > cd /usr/ports && make search name=pear- xname='ht(tp|ml)' > > Well, OK. That seems a lot more effort, and loses your current directory, > but that does work. It's fugly though. OK, so "alias search='make -C /usr/ports search'". Then you can, as needed, "search name=whatever" (or whatever criteria you want to use). Jim ___ 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: texinfo vs. emacs...
On Fri, June 21, 2013 3:46 pm, Matthew Seaman wrote: > On 21/06/2013 20:11, Jim Trigg wrote: >> OK, is there a way to do this for specific ports so that an >> administrator >> can approve specific combinations of ports without giving blanket >> permission? > > No, unfortunately there isn't. Given that you need root permissions to > install packaged software in any case, it would be impossible to enforce > any selectivity like that. I didn't see this as necessarily more difficult than doing similar things in make.conf (either old-style or optionsNG)... > Besides which, two or more ports installing a file in the same place is > a bug, when those ports might reasonably be installed on the same system > simultaneously. The old pkg_tools were incredibly lax about such > things, so there hasn't been sufficient impetus to clean up such > occurrences. My point is that if an admin runs into a bug between one pair of ports and installs this workaround, s/he won't see similar bugs between other pairs of ports to report them. If there were a way to specify this at the port level (something like "ignore conflicts with these other ports"), that would give a workaround for known bugs without masking not-yet-known bugs. Thanks, Jim ___ 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: texinfo vs. emacs...
On Fri, Jun 21, 2013 at 07:18:43PM +0200, Baptiste Daroussin wrote:
> On Fri, Jun 21, 2013 at 05:32:54PM +0100, Ben Laurie wrote:
> > On 21 June 2013 15:55, Matthew Seaman wrote:
> > > On 21/06/2013 14:34, Ben Laurie wrote:
> > >> Installing texinfo-5.1.20130419_1...pkg-static: texinfo-5.1.20130419_1
> > >> conflicts with emacs-24.3,3 (installs files into the same place).
> > >> Problematic file: /usr/local/info/info.info.gz
> > >>
> > >> There doesn't seem to be any clean way to fix this ... hints?
> > >
> > > Add
> > >
> > > PERMISSIVE : yes
> > >
> > > to ${LOCALBASE}/etc/pkg.conf
> > >
> > > It's not really clean in that it just allows packages to stomp over each
> > > other's files, but it lets you get the job done.
> >
> > Also, is there an env flag that does the same thing?
> >
> All configuration in pkg.conf can also be set by env flags. so PERMISSIVE=yes
> will do the same.
OK, is there a way to do this for specific ports so that an administrator
can approve specific combinations of ports without giving blanket
permission?
Thanks,
Jim
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Conversion to new options framework over
On Fri, Jun 07, 2013 at 08:09:30PM +0100, Chris Rees wrote: > On 7 June 2013 18:55, Jim Trigg wrote: > > On Thu, Jun 06, 2013 at 08:45:10AM +0200, Baptiste Daroussin wrote: > >> The compatibility code to parse the WITH/WITHOUT entries in make.conf > >> will be removed in 6 months either. > >> > >> Do not forget to convert your configuration (make.conf, portsconf etc). > >> A reminder will be send a month before the removal of the compatibility > >> code. > > > > It would be useful to provide a pointer to instructions for doing so -- > > what exactly replaces WITH/WITHOUT entries in make.conf? For example, > > my dedicated server has WITHOUT_X11=yes in /etc/make.conf because it's > > headless and doesn't run an X server. What should that become? > > > > I tried googling, and the github doc page's only mention of make.conf is > > to add "WITH_PKGNG=yes". Likewise the FreeBSD Handbook. The wiki > > apparently just points to the Handbook. > > WITH_PKGNG is not a classical OPTION, because it doesn't apply to any > port in particular. I hadn't meant to refer to that as one of the WITH_ options that needed to be changed... > There is some documentation for users at [1], basically you need to > change any WITH_ variables to OPTIONS_SET=, and WITHOUT_ to > OPTIONS_UNSET=. I'll hopefully find some time soon to get it in the > Handbook > > For example; > > WITHOUT_X11=yes > WITH_CUPS=yes > WITHOUT_PULSEAUDIO=yes > > becomes > > OPTIONS_SET=CUPS > OPTIONS_UNSET=PULSEAUDIO X11 That works for binary options, but what about version options? E.g., WITH_BDB_VER=47 ... Thanks, Jim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Conversion to new options framework over
On Thu, Jun 06, 2013 at 08:45:10AM +0200, Baptiste Daroussin wrote: > The compatibility code to parse the WITH/WITHOUT entries in make.conf > will be removed in 6 months either. > > Do not forget to convert your configuration (make.conf, portsconf etc). > A reminder will be send a month before the removal of the compatibility > code. It would be useful to provide a pointer to instructions for doing so -- what exactly replaces WITH/WITHOUT entries in make.conf? For example, my dedicated server has WITHOUT_X11=yes in /etc/make.conf because it's headless and doesn't run an X server. What should that become? I tried googling, and the github doc page's only mention of make.conf is to add "WITH_PKGNG=yes". Likewise the FreeBSD Handbook. The wiki apparently just points to the Handbook. Thanks, Jim Trigg ___ 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: Portmaster/Portupgrade | pkg2ng
On Tue, Oct 16, 2012 at 06:51:59PM -0500, Bryan Drewery wrote: > On 10/16/2012 4:11 PM, Jos Chrispijn wrote: > > Somewhat lost here; just read UPDATING in which is reported about an > > additional function support of pkgng by portupgrade and portmaster: > > > > PORTMASTER > > # make -C /usr/ports/ports-mgmt/portmaster config build deinstall > > install clean > > # echo 'WITH_PKGNG=yes' >> /etc/make.conf > > # pkg2ng* > > > > PORTUPGRADE > > # echo 'WITH_PKGNG=yes' >> /etc/make.conf > > # pkg2ng* > > # pkgdb -fu > > > > The only issue I have is that this pkg2ng command doesn't work as this > > program* cannot be found so the command returns with a 'pkg2ng: Command > > not found.' > > Can someone tell me what I miss here? > > make -C /usr/ports/ports-mgmt/pkg install clean > > Sorry for the confusion. I will add that in. I think what's needed for portmaster is an explicit mention that the PKGNGPATCH option needs to be selected. That will cause pkg to be installed automatically, and installing it manually just increases the risk that portmaster won't have been built correctly to support it. Jim ___ 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: portmaster
On Tue, Oct 16, 2012 at 01:03:08PM -0400, Jim Trigg wrote:
> I'm having a worse problem upgrading to 3.14_4...
>
> ===>>> Creating a backup package for old version portmaster-3.14
>
> ===>>> Starting check for runtime dependencies
> ===>>> Gathering dependency list for ports-mgmt/portmaster from ports
> ===>>> Launching child to install ports-mgmt/pkg
>
> ===>>> All >> portmaster-3.14 >> ports-mgmt/pkg (2/9)
> /usr/local/sbin/portmaster: /usr/local/sbin/portmaster: not found
>
> ===>>> Update for ports-mgmt/pkg failed
> ===>>> Aborting update
>
> ===>>> Update for ports-mgmt/portmaster failed
> ===>>> Aborting update
>
> Terminated
> Terminated
> Terminated
> Terminated
> Terminated
> Terminated
> Terminated
> Terminated
> Terminated
> Terminated
> Terminated
>
> ===>>> You can restart from the point of failure with this command line:
>portmaster ports-mgmt/portmaster ports-mgmt/pkg
> misc/mime-support databases/mysql51-client net/openldap24-client sysu
> tils/coreutils math/gmp databases/mysql51-server mail/roundcube
>
> Except of course that I can't, because /usr/local/sbin/portmaster has
> vanished...
Never mind, I misread UPDATING, and missed the critical line ("make -C
/usr/ports/ports-mgmt/portmaster config build deinstall install clean").
I've reinstalled portmaster and everything looks good now.
Thanks,
Jim
___
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: portmaster
On Mon, Oct 15, 2012 at 10:51:50AM -0500, Bryan Drewery wrote:
> On 10/15/2012 10:36 AM, Bryan Drewery wrote:
> > On 10/15/2012 5:46 AM, ajtiM wrote:
> >> Update on my FreeBSD 9.1-RC2 #0 of portmaster does not works:
> >>
> >> ===> Registering installation for portmaster-3.14_1
> >> %n: {origin: %o, version: "%v"}: not found
> >> pkg_create: invalid option -- l
> >> usage: pkg_create [-YNOhjnvyz] [-C conflicts] [-P pkgs] [-p prefix]
> >> [-i iscript] [-I piscript] [-k dscript] [-K pdscript]
> >> [-r rscript] [-s srcdir] [-S basedir]
> >> [-t template] [-X excludefile]
> >> [-D displayfile] [-m mtreefile] [-o originpath]
> >> -c comment -d description -f packlist pkg-filename
> >>pkg_create [-EGYNRhnvxy] -b pkg-name [pkg-filename]
> >> *** [fake-pkg] Error code 1
> >>
> >> Stop in /usr/ports/ports-mgmt/portmaster.
> >> *** [install] Error code 1
>
> This is a problem with the ports-mgmt/portmaster changes. I've fixed
> this in 3.14_2. Please update your ports tree and try again. I've just
> committed the fix, it may take 15 minutes to get updated.
I'm having a worse problem upgrading to 3.14_4...
===>>> Launching child to install ports-mgmt/portmaster
===>>> All >> ports-mgmt/portmaster (1/9)
===>>> Currently installed version: portmaster-3.14
===>>> Port directory: /usr/ports/ports-mgmt/portmaster
===>>> Starting check for build dependencies
===>>> Gathering dependency list for ports-mgmt/portmaster from ports
===>>> No dependencies for ports-mgmt/portmaster
===> Cleaning for portmaster-3.14_4
===> License BSD accepted by the user
===> Found saved configuration for portmaster-3.14_4
=> patch-portmaster-pkgng.gz doesn't seem to exist in /usr/ports/distfiles//.
=> Attempting to fetch
http://mirror.shatow.net/freebsd/portmaster/patch-portmaster-pkgng.gz
patch-portmaster-pkgng.gz 100% of 9937 B 133 kBps
===> Extracting for portmaster-3.14_4
=> SHA256 Checksum OK for portmaster-portmaster-3.14-31009f6.tar.gz.
=> SHA256 Checksum OK for patch-portmaster-pkgng.gz.
===> Patching for portmaster-3.14_4
===> Applying distribution patches for portmaster-3.14_4
===> Applying extra patch
/usr/ports/ports-mgmt/portmaster/files/extra-patch-files::zsh-completions
===> Configuring for portmaster-3.14_4
===> Building for portmaster-3.14_4
/usr/bin/sed -e 's#/usr/local#/usr/local#g'
/usr/ports/ports-mgmt/portmaster/work/portmaster-portmaster-31009f6/portmaster
> /usr/p
orts/ports-mgmt/portmaster/work/portmaster
/usr/bin/sed -e 's#/usr/local#/usr/local#g'
/usr/ports/ports-mgmt/portmaster/work/portmaster-portmaster-31009f6/files/portmaster.rc.
sample > /usr/ports/ports-mgmt/portmaster/work/portmaster.rc.sample
===>>> Creating a backup package for old version portmaster-3.14
===>>> Starting check for runtime dependencies
===>>> Gathering dependency list for ports-mgmt/portmaster from ports
===>>> Launching child to install ports-mgmt/pkg
===>>> All >> portmaster-3.14 >> ports-mgmt/pkg (2/9)
/usr/local/sbin/portmaster: /usr/local/sbin/portmaster: not found
===>>> Update for ports-mgmt/pkg failed
===>>> Aborting update
===>>> Update for ports-mgmt/portmaster failed
===>>> Aborting update
Terminated
Terminated
Terminated
Terminated
Terminated
Terminated
Terminated
Terminated
Terminated
Terminated
Terminated
===>>> You can restart from the point of failure with this command line:
portmaster ports-mgmt/portmaster ports-mgmt/pkg
misc/mime-support databases/mysql51-client net/openldap24-client sysu
tils/coreutils math/gmp databases/mysql51-server mail/roundcube
Except of course that I can't, because /usr/local/sbin/portmaster has
vanished...
Thanks,
Jim
___
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: Instafix for FreeBSD ports brokenness on 10.0?
On Fri, Sep 30, 2011 at 5:10 AM, Erwin Lansing wrote: > That said, this patch is the wrong place to fix a problem to autotools. > It needs to be fixed in autotools, not bsd.port.mk. No matter if it's > bsd.ports.mk or autotools, such a fix needs proper testing, for which > we do not currently have the resources as we are concentrating on > releasing 9.0. I would suggest you do the same and make 9.0 the best > release possible during the next few weeks, after that we'll start > looking into 10.0. I have to admit that my reaction is not so much "Why won't you fix ports for 10.0" as "Why was 9.0 dropped out of CURRENT and 10.0 introduced before 9.0 went STABLE?" Jim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Problem using devel/apr1 with OpenLDAP 2.4.25_1
I did. This did not look like the fetchGetURL problem, and it was in trying to run 'portmaster -r net/openldap24-client' as recommended that I encountered the problem. Thanks, Jim On Sat, Apr 2, 2011 at 5:20 PM, Doug Barton wrote: > Please read /usr/ports/UPDATING, and get in the habit of doing so regularly. > :) > > > Doug > > -- > > Nothin' ever doesn't change, but nothin' changes much. > -- OK Go > > Breadth of IT experience, and depth of knowledge in the DNS. > Yours for the right price. :) http://SupersetSolutions.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"
Problem using devel/apr1 with OpenLDAP 2.4.25_1
I'm having a problem which affects my web server quite strongly. I
upgraded openldap24-client to 2.4.25_1, and now can neither run nor
rebuild devel/apr1 (which blocks apache and squirrelmail). The make
in /usr/ports/devel/apr1 reports (cut down to just what looks like it
might be applicable):
===> apr-ipv6-devrandom-gdbm-db42-ldap24-mysql51-1.4.2.1.3.10
depends on shared library: ldap-2.4.8 - found
build/apu-conf.m4:215: APU_FIND_LDAP is expanded from...
configure.in:152: the top level
cd /usr/ports/devel/apr1/work/apr-util-1.3.10; /usr/bin/env CC="cc"
LIBS="" PYTHON="/usr/local/bin/python2.6" SHELL=/bin/sh
CONFIG_SHELL=/bin/sh AUTOMAKE=/usr/local/bin/automake-1.11
AUTOMAKE_DIR=/usr/local/share/automake-1.11 AUTOMAKE_VERSION=1.11
AUTOMAKE_APIVER=1.11.1 ACLOCAL=/usr/local/bin/aclocal-1.11
ACLOCAL_DIR=/usr/local/share/aclocal-1.11
AUTOCONF=/usr/local/bin/autoconf-2.68
AUTOCONF_DIR=/usr/local/share/autoconf-2.68
AUTOHEADER=/usr/local/bin/autoheader-2.68
AUTOIFNAMES=/usr/local/bin/ifnames-2.68
AUTOM4TE=/usr/local/bin/autom4te-2.68
AUTORECONF=/usr/local/bin/autoreconf-2.68
AUTOSCAN=/usr/local/bin/autoscan-2.68
AUTOUPDATE=/usr/local/bin/autoupdate-2.68 AUTOCONF_VERSION=2.68
LIBTOOL=/usr/local/bin/libtool LIBTOOLIZE=/usr/local/bin/libtoolize
LIBTOOL_LIBEXECDIR=/usr/local/libexec/libtool
LIBTOOL_SHAREDIR=/usr/local/share/libtool
LIBTOOL_M4=/usr/local/share/aclocal/libtool.m4
LTMAIN=/usr/local/share/libtool/config/ltmain.sh
lt_cv_sys_max_cmd_len=262144 CFLAGS="-O2 -pipe -I/usr/local/include
-I/usr/local/include/mysql -DHAVE_MYSQL_H -DLDAP_DEPRECATED
-fno-strict-aliasing" /bin/sh ./configure --prefix=/usr/local
${_LATE_CONFIGURE_ARGS}
--with-apr=/usr/ports/devel/apr1/work/apr-1.4.2
--with-expat=/usr/local --with-iconv=/usr/local
--with-gdbm=/usr/local
--with-berkeley-db=/usr/local/include/db42:/usr/local/lib/db42
--without-ndbm --with-ldap-include=/usr/local/include
--with-ldap-lib=/usr/local/lib --with-ldap=ldap
--with-mysql=/usr/local --without-pgsql --without-sqlite3
checking for ldap support...
checking for ldap_init in -lldap... no
checking for ldap_init in -lldap... no
checking for ldap_init in -lldap... no
checking for ldap_init in -lldap... no
configure: error: could not find an LDAP library
Any suggestions?
Thanks,
Jim
___
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 - dovecot
On Tue, Aug 24, 2010 at 4:04 PM, Jerry wrote: > On Tue, 24 Aug 2010 20:46:49 +0200 > DZIOBAK articulated: > >> Could you please tell me when can be released dovecot-1.2.14 and >> dovecot-2.0.1? The versions 1.2.13 and 2.0.0 are released for couple >> of weeks, but ports are not created. > > While releasing the former into the ports system is a worthwhile goal, > it would be a mistake IMHO to do the same for the latter. The software > author is releasing on what appears to be an almost hourly schedule, > patches to the base program. Until it stabilizes, I would not recommend > releasing it into the wild. If it has as many problems as it appears to > on the system it was written on, one can only imagine what sort of > problems await FreeBSD users. I think it would be perfectly reasonable to release it as dovecot-devel (which is currently DEPRECATED because it's lagging behind the main dovecot port). Jim ___ 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: what next for the pkg_install rewrite
On Thu, Aug 19, 2010 at 6:10 PM, Ivan Voras wrote:
> On 19/08/2010, jhell wrote:
>> Adding to this I would like to see a central database created for
>> packages that have been removed like in Slackware Linux. They keep a
>> file in /var/log/preserved_packages with a flat text format with the
>> file name looking like:
>>
>> ${PORTNAME}-${PORTVERSION}${PORTREVISION}-`date +%Y%m%d%H%M%S`
>
> Ah yes, you reminded me of this other thing: I would also suggest
> getting rid of text files carrying rich information in ad-hoc formats
> :)
>
> I'm not saying XML should be the only choice, but it *is* well
> supported - expat is even in base as libbsdxml.
That might be acceptable.
> While suggesting nebulous things I know will be hard to pass near a
> lot of people: sqlite is *the* choice for any record-based file
> databases today. The single most important thing I'll promote with it
> is its transaction capabilities and ACID - these would get much use if
> parallel operations (upgrades / installs) are to be supported. There
> are a ton of other reasons too.
On the other hand, I have strong philosophical objections to core
port/package management utilities requiring large support structures
of other ports/packages.
Jim
___
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"
Next question from a basically novice maintainer
OK, I'm trying to set up tinderbox to validate the port I maintain and another that I'm attempting to put together (well, technically to update since the maintainer has not responded to my inquiry). How do I set up ports trees for individual ports and their dependencies? The README only shows how to pull a full ports tree from CVS. Thanks, Jim ___ 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: keep-alive option for sudo in portmaster
On Fri, Aug 6, 2010 at 6:58 PM, Doug Barton wrote: > On 08/06/2010 15:54, Anonymous wrote: >> Doug Barton writes: >>> While I can sympathize with your situation, I think you'd be better off >>> in this case running your portmaster commands in an actual root shell. >> >> Wouldn't periodic hook be useful to smth else besides PM_SU_CMD? Like >> sending time passed since current port build started to xterm title. >> It may help to guess how long till it completes the build. > > I look forward to reviewing your patches to implement this feature. :) I use aliases: alias portadd="sudo portmaster" alias portrm="sudo portmaster -e" alias portls="portmaster -L" alias portupg="sudo portmaster -aDG" Speaking of such things (particularly the usage of -l/-L, which shouldn't need root privileges), did you get my PR and patch to allow for five-digit UIDs? HTH, Jim ___ 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: i keep *trying* to move from portupgrade to portmaster
On Fri, Aug 6, 2010 at 5:26 PM, Doug Barton wrote: > On 08/06/2010 04:34, jhell wrote: >> Do not prompt for a backup package creation failure > > I need to add an option for this, but it will likely be an "expert" > option that you can set in the rc file. The theory is that package > creation failure should be a rare thing, and since portmaster has no way > to know what packages are really critical to any given system it treats > inability to safely recover from an upgrade failure as a critical error. > However, having the ability to disable this is an oft-requested feature, > I just haven't gotten to it yet. > >> and force creation of whatever you have on the system already? > > Not sure what this means, can you explain it in more detail? One example I have (unfortunately): I accidentally wiped out /usr/local/. Reinstalling all my ports was easy -- first reinstall portmaster and then run "portmaster -af". The problem was that for every single port I had to say "Yes, ignore the fact that the port wasn't already there". So I had to tend the process all the way through. An option to force ignoring the package creation failure would allow that to be an unattended process. Jim ___ 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"
Trying to use the USERS and SHAREOWN functionalities
Are there any examples of how to use the USERS functionality together with the SHAREOWN functionality in a port makefile? I'm working on updating the ecartis port to use standard functionality for its user ID, but can't seem to tell how to make sure that the USERS are created before files are installed, and that installed files are then owned by the user that is created. Thanks, Jim ___ 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: Problems with sysutils/screen (GNU Screen)
On Fri, Jul 23, 2010 at 10:25 PM, jhell wrote: > On 07/23/2010 15:43, Jim Trigg wrote: > > ls -l /usr/share/misc/termcap* > > You should see two files termcap and termcap.db > > Check the perms of both and the existence of both. > > I believe that cap_mkdb(1) is run on termcap to create the db but > someone else should chime in on this because I am not sure at the moment. argent(2) ~$ ls -l /usr/share/misc/termc* -r--r--r-- 1 root wheel 206791 Mar 26 10:02 /usr/share/misc/termcap -r--r--r-- 1 root wheel 1339392 Mar 26 10:02 /usr/share/misc/termcap.db However, it is seeming like termcap.db isn't getting found, since it runs correctly when I run screen with TERM set to xterm but fails when TERM is set to linux (as it does automatically using either of my standard terminal emulators). Thanks, Jim ___ 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: Problems with sysutils/screen (GNU Screen)
On Fri, Jul 23, 2010 at 3:42 PM, Scott Sanbeg wrote:
> /etc/termcap is symlinked to /usr/share/misc/termcap, which if not available
> during your session (singer-user mode, for instance), produces that exact
> type of error message. Test if the termcap db is actually available.
It is; further, I will observe that unsetting the TERMCAP environment
variable makes it work in an interactive shell window, but when I use
the "screen {command}" functionality it fails (and I can't get logging
to work to find out what error I'm actually getting; the window closes
too fast for me to see the error).
Thanks,
Jim
___
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: Problems with sysutils/screen (GNU Screen)
On Fri, Jul 23, 2010 at 3:29 PM, David Wolfskill wrote:
> On Fri, Jul 23, 2010 at 03:23:41PM -0400, Jim Trigg wrote:
>> I've been having problems with GNU Screen on FreeBSD 8.x. First, the
>> TERMCAP environment variable as automatically set by screen causes
>> things not to work. (vi says "cannot open terminal database", mutt
>> says "no terminal database", etc.) Second, when I put `eval tset -s`
>> in .bashrc to reset the TERMCAP, curses-based programs work from
>> command lines in open windows but don't work through "screen
>> {command}" to launch them in a separate window -- the window flashes
>> open and back closed. /usr/local/bin/bash is my login shell. This
>> all still works in FreeBSD 7.
>>
>> Any suggestions?
>
> Is screen built under 8.x or 7.x?
8.x. (I have one server running 7.x and another running 8.x.)
Also, to the other responder, "unset TERMCAP" in ~/.profile gives the
same behavior as "eval `tset -s`".
Thanks,
Jim
___
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"
Problems with sysutils/screen (GNU Screen)
I've been having problems with GNU Screen on FreeBSD 8.x. First, the
TERMCAP environment variable as automatically set by screen causes
things not to work. (vi says "cannot open terminal database", mutt
says "no terminal database", etc.) Second, when I put `eval tset -s`
in .bashrc to reset the TERMCAP, curses-based programs work from
command lines in open windows but don't work through "screen
{command}" to launch them in a separate window -- the window flashes
open and back closed. /usr/local/bin/bash is my login shell. This
all still works in FreeBSD 7.
Any suggestions?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for testers: www/shellinabox (Shell in a Box)
2010/6/28 Olivier Cochard-Labbé : > patch ../../UIDs UIDs.diff > patch ../../GIDs GIDs.diff > > For information: > I've used the UID/GID 139 that seem available. Oh, bother. I was getting ready to use that for mail/ecartis (ecartis:ecartis). OK, I'll find another slot. Jim ___ 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: revisiting Spamassassin problem
On Fri, Apr 23, 2010 at 02:27:03PM -0400, Robert Huff wrote: > > Back in February there was a thread - "spamassassin problem > with upgrade" - about spamd failing to start with this error: > > child process [76967] exited or timed out without signaling production of > a PID file: exit 255 at /usr/local/bin/spamd line 2588. > /usr/local/etc/rc.d/sa-spamd: WARNING: failed to start spamd > > The thread offered no definite solution except to downgrade. > Is this still the case? When I've seen that, it's meant that I needed to run sa-update to rebuild the rule database (I think it is). Jim -- Jim Trigg, Lord High Everything Else O- /"\ \ / ASCII RIBBON CAMPAIGN Hostmaster, Huie Kin family websiteXHELP CURE HTML MAIL Verger, All Saints Church - Sharon Chapel / \ ___ 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: [REPOST] problem upgrading perl
On Tue, Jun 16, 2009 at 11:44:54PM -0500, Scott Bennett wrote: > On Tue, 16 Jun 2009 20:07:26 +0200 Alexey Shuvaev > wrote: > >Hmmm... Looking at portmaster sources I've got one idea. > >Can you try more precise command to upgrade everything depending on perl? > > > >nice +18 portmaster -v -r perl-threaded-5.10.0_3 > > > >The point is that perl\* wildcard gives you both perl-threaded-XXX and > >perltidy- which might be bad idea. > > Bingo!! Very nice call. It has now driven me to distraction with dialog > boxes for configuration stuff for many ports/packages, and is now busily > reinstalling perl intself. > > > >If this is the case I think UPDATING entry should be improved > >to use perl-\* wildcard. > > I think you meant to *not* use the wildcard, and yes, /usr/ports/UPDATING > is clearly wrong in this case and should be fixed. > Thanks very much for solving this. I still have to deal with some > problems with options on the various packages/ports to be updated, but I can > proceed for now. Actually, he was suggesting changing from perl\* to perl-\* so it would only match the perl port. Unfortunately, that won't work as there is at least one other port that will match that -- net/p5-perl-ldap (portname perl-ldap). So it should be revised to instruct users to use the exact portname in /var/db/pkg. Jim -- Jim Trigg, Lord High Everything Else O- /"\ \ / ASCII RIBBON CAMPAIGN Hostmaster, Huie Kin family websiteXHELP CURE HTML MAIL Verger, All Saints Church - Sharon Chapel / \ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
On Thu, Feb 12, 2009 at 07:15:50PM -0500, Eitan Adler wrote: > Thomas Abthorpe wrote: > > The gauntlet has been thrown down, who among you is prepared to pick it up? > I'll take x11/xclip in addition to what I currently maintain. I'm > looking through the others and will submit a followup email soon. I'll take mail/ecartis, as I'm one of the folks who has contributed patches to the upstream in the last few years. Jim -- Jim Trigg, Lord High Everything Else O- /"\ \ / ASCII RIBBON CAMPAIGN Hostmaster, Huie Kin family websiteXHELP CURE HTML MAIL Verger, All Saints Church - Sharon Chapel / \ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Proposal: mechanism for local patches
On Tue, Dec 2, 2008 at 9:08 PM, RW <[EMAIL PROTECTED]> wrote: > I wonder if portsnap actually needs to behave the way it does. > > Portsnap stores its compressed snapshot as one .gz file for each > port plus one for each additional file (files in Mk/ etc). When you > do an "update" any modified snapshot files are extracted over > the appropriate location in the ports tree. > > The reason that "portsnap extract" deletes patch-files is that before > each .gz file is extracted, the corresponding file or port directory is > deleted. I wonder why, if an "update" can decompress over the top of a > port, an "extract" need to delete it first. I can't think of any good > reason offhand. > > Modifying portsnap not to delete extra files is just a matter of > deleting one line. The behaviour of portsnap extract would then be > virtually identical to csup. Alternately, it wouldn't be much harder to > create a new portsnap command. I would presume that it does that to get rid of "standard" patch files that are no longer part of the port... Jim Trigg ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Can't install gnome2 - docbook-utils is broken
Running 7.0-RELEASE; attempting to install gnome2 from ports. (Note:
I tried installing from packages on the distribution CDs and
upgrading; that was a worse nightmare...)
First, docbook-utils insists that docbook-310 is not installed when it
is. I tracked that one down:
/usr/ports/textproc/docbook-utils/Makefile:
19c19
<
${LOCALBASE}/share/sgml/docbook/3.1/docbook.dtd:${PORTSDIR}/textproc/docbook-310
\
---
>
> ${LOCALBASE}/share/sgml/docbook/3.1/dtd:${PORTSDIR}/textproc/docbook-310 \
Then, docbook-utils fails with the following error:
jade:../../doc/docbook-utils.sgml:1:55:W:cannot generate system
identifier for public text "-//OASIS//DTD DocBook V3.1//EN"
followed by a lot of subsequent errors about unknown entities.
How do I fix this? I've already searched the archives, the bug
database, and the web with no useful results.
Thanks,
Jim Trigg
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't install gnome2 - docbook-utils is broken
On Thu, Aug 14, 2008 at 12:12 PM, Jim Trigg <[EMAIL PROTECTED]> wrote:
> First, docbook-utils insists that docbook-310 is not installed when it
> is. I tracked that one down:
>
> /usr/ports/textproc/docbook-utils/Makefile:
> 19c19
> <
> ${LOCALBASE}/share/sgml/docbook/3.1/docbook.dtd:${PORTSDIR}/textproc/docbook-310
> \
> ---
>>
>> ${LOCALBASE}/share/sgml/docbook/3.1/dtd:${PORTSDIR}/textproc/docbook-310 \
Correction: that should be ${LOCALBASE}/share/sgml/docbook/3.1/dtd/docbook.dtd.
Thanks,
Jim Trigg
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade query
On Thu, March 1, 2007 10:02 am, Vizion wrote: > I have multiple lines of stale dependencies reported from pkgdb -F all of > which relate to bsdpan-Archive-Tar-1.30 or 1.16 witha report that the > package is held. > > The lines are > Stale dependency:bsdpan-Archive-Tar-[version] -> [see NOTE below]: -> > Ignored (the package is held; specify -f to force) > > How do I get out of the following loop! > : > I run > # pkgdb -f > Then try > # portupgrade -a > and get > Stale dependency . manuall run 'pkgdb -F to fix or specify -O to > force > I run > # pkgdb -O You're misreading the message -- you need to run "pkgdb -F" to fix the database or run "portupgrade -a -O" to force the portupgrade to ignore the stale dependencies. Jim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Porting a Linux application to FreeBSD
Chuck Swiger wrote:
> On Feb 12, 2007, at 4:39 PM, Andrew Pantyukhin wrote:
>>> Linux does not have it's own libpng and neither do we. Most Linux
>>> distros and us use libpng from libpng.org. I took a quick look at the
>>> current libpng in the ports tree and it appears to have png_read_png().
>>> With out seeing a Makefile for the ports system and some error output it
>>> is hard to comment as to the specific reason stuff is failing for you.
>>
>> Yes, but my money says
>> ==
>> =CPPFLAGS= -I${LOCALBASE}/include
>> =LDFLAGS=-L${LOCALBASE}/lib
>> =GNU_CONFIGURE= yes
>> =CONFIGURE_ENV= CPPFLAGS="${CPPFLAGS}" LDFLAGS="${LDFLAGS}"
>> ===
>> will help, it always(x0.999) does :-) It's one
>> of those things everyone knows about but no one
>> commits into Mk/* because we enjoy routine so
>> much.
>
> I believe your suggestion is exactly right as to the problem; my only
> question would be whether it would be better to change the ports Mk
> infrastructure, or to change the system compiler to add
> /usr/local/{include,lib} to the default search paths...
Adding ${PREFIX}/{include,lib} would be significantly better than
hardcoding /usr/local/...
Jim
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems upgrading glib20
On Tue, October 24, 2006 9:46 am, Erwin Van de Velde wrote: > Hi all, > > This is an error in the compilation of icu and has been reported a couple > of weeks ago... It would be nice if someone found the time to look into > this as it indeed blocks multiple updates on many systems. So folks are specifically aware -- glib20 will install fine *if* the collation fix is unselected. icu is only a dependency for the collation fix. Jim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mail/mutt-devel: regression in 1.5.12
On Wed, August 9, 2006 11:01 am, Vasil Dimov wrote: > On Wed, Aug 09, 2006 at 09:43:21AM -0400, Jim Trigg wrote: >> On Wed, August 9, 2006 6:49 am, Vasil Dimov wrote: >> > Firstly some more deatils on my setup: >> > >> > I have 14 folders listed in my muttrc: >> > mailboxes imaps://vd:[EMAIL PROTECTED]/ >> > mailboxes imaps://vd:[EMAIL PROTECTED]/freebsd-ports >> > ... >> >> Have you tried using imap_user and imap_pass variables in .muttrc >> instead of putting the user and password in the URL? > > That simplifies my muttrc but does not resolve the problem. > Nor does playing with the other imap_* variables. I didn't know whether it would or not but thought it might at least help pin down which part of the code is having problems. Jim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mail/mutt-devel: regression in 1.5.12
On Wed, August 9, 2006 6:49 am, Vasil Dimov wrote: > Firstly some more deatils on my setup: > > I have 14 folders listed in my muttrc: > mailboxes imaps://vd:[EMAIL PROTECTED]/ > mailboxes imaps://vd:[EMAIL PROTECTED]/freebsd-ports > mailboxes imaps://vd:[EMAIL PROTECTED]/freebsd-hackers > mailboxes imaps://vd:[EMAIL PROTECTED]/freebsd-amd64 > mailboxes imaps://vd:[EMAIL PROTECTED]/freebsd-ports-bugs > mailboxes imaps://vd:[EMAIL PROTECTED]/spam > ... Have you tried using imap_user and imap_pass variables in .muttrc instead of putting the user and password in the URL? Jim -- Jim Trigg, Lord High Everything Else O- /"\ Hostmaster, Huie Kin family website\ / ASCII RIBBON CAMPAIGN Verger and System Administrator,XHELP CURE HTML MAIL All Saints Church - Sharon Chapel / \ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't install ruby-bdb on RELEASE-6.1
On Fri, Jul 21, 2006 at 12:43:40PM -0400, Jim Trigg wrote: > On Fri, July 21, 2006 12:10 pm, Donald J. O'Neill wrote: > > On Friday 21 July 2006 09:45, Jim Trigg wrote: > >> On Fri, July 21, 2006 2:22 am, Sergey Matveychuk wrote: > >> > Jim Trigg wrote: > >> >> I'm setting up a new system with 6.1-RELEASE, and I forgot to install > >> >> portupgrade from a package during the OS install. ruby-bdb fails to > >> >> build, complaining that it doesn't know how to make 'all' (it doesn't > >> >> specify which directory it's in, but it's right after it runs > >> >> extconf.rb). Any clues? > >> >> > >> >> (Note: when I posted this earlier I mentioned changing LOCALBASE. > >> >> Further testing has shown that it fails regardless of LOCALBASE > >> >> setting.) Cleaning out installed ports, refreshing the ports tree with portsnap, and building WITH_BDB_VER=43 worked; thanks for all the advice, folks. Jim -- Jim Trigg, Lord High Everything Else O- /"\ \ / ASCII RIBBON CAMPAIGN Hostmaster, Huie Kin family websiteXHELP CURE HTML MAIL Verger, All Saints Church - Sharon Chapel / \ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't install ruby-bdb on RELEASE-6.1
On Fri, July 21, 2006 12:10 pm, Donald J. O'Neill wrote: > On Friday 21 July 2006 09:45, Jim Trigg wrote: >> On Fri, July 21, 2006 2:22 am, Sergey Matveychuk wrote: >> > Jim Trigg wrote: >> >> I'm setting up a new system with 6.1-RELEASE, and I forgot to install >> >> portupgrade from a package during the OS install. ruby-bdb fails to >> >> build, complaining that it doesn't know how to make 'all' (it doesn't >> >> specify which directory it's in, but it's right after it runs >> >> extconf.rb). Any clues? >> >> >> >> (Note: when I posted this earlier I mentioned changing LOCALBASE. >> >> Further testing has shown that it fails regardless of LOCALBASE >> >> setting.) >> > >> Full list of what I've done: > >> - Installed 6.1-RELEASE from CD > OK, fine. >> - Installed cvsup > >> - Ran cvsup ports-all > Please explain this a little more. What's ports-all? Is that the name of a > sup-file you're using? If so, what's in it? > >> - Attempted to install portupgrade with BDB4; ruby-bdb failed to build > What is the failure message. The failure could have occurred at the > beginning of ruby-bdb. Do you have /usr/ports/databases/db(what version?) > installed? I don't have the complete error message anymore, but it was basically "don't know how to make 'all'" after running extconf.rb. IIRC I had db41 installed; on at least one attempt I tried installing db44 instead (and setting WITH_BDB_VER=44). >> - Uninstalled all ports, changed LOCALBASE to /opt and X11BASE to >> $LOCALBASE > Are you saying you uninstalled the ports-tree and reinstalled it using > cvsup, or are you saying you uninstalled the installed ports? I'm saying I uninstalled all installed ports, in order to change LOCALBASE. > Is there a reason you are messing with LOCALBASE? Is this a linux thing > you're doing? Sort of, but not really. I'm changing LOCALBASE because I prefer having my filesystems at root level, and want my ports on a separate filesystem from /usr. /opt happens to be used by both Linux and Solaris. Note that while this is a new system (and my first 6.x system), I've been managing a 4.x system for at least six years now; I'm not new to FreeBSD or ports. > What is the output from 'df -m'? I'll send this later, when I'm at home where the system is. Offhand, /usr and /opt each are 20G partitions with plenty of free space. > Do you have anything in /etc/make.conf? Only LOCALBASE, X11BASE, and WITH_BDB_VER when those are defined. > I would suggest installing /usr/ports/databases/db43 before trying to > install portupgrade. It might work out a little better for you. OK, I'll try against that version as well. Thanks, Jim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't install ruby-bdb on RELEASE-6.1
On Fri, July 21, 2006 2:22 am, Sergey Matveychuk wrote: > Jim Trigg wrote: >> I'm setting up a new system with 6.1-RELEASE, and I forgot to install >> portupgrade from a package during the OS install. ruby-bdb fails to >> build, complaining that it doesn't know how to make 'all' (it doesn't >> specify which directory it's in, but it's right after it runs >> extconf.rb). Any clues? >> >> (Note: when I posted this earlier I mentioned changing LOCALBASE. >> Further >> testing has shown that it fails regardless of LOCALBASE setting.) > > Make sure you have a fresh ports tree. > May be you should reinstall ruby. I did have a fresh ports tree, and I've tried that. Full list of what I've done: - Installed 6.1-RELEASE from CD - Installed cvsup - Ran cvsup ports-all - Attempted to install portupgrade with BDB4; ruby-bdb failed to build - Uninstalled all ports, changed LOCALBASE to /opt and X11BASE to $LOCALBASE - Attempted to install portupgrade with BDB4; ruby-bdb failed to build - Uninstalled all ports, changed LOCALBASE back to /usr/local - Installed ruby18, attempted to install ruby-bdb; ruby-bdb failed to build - Uninstalled all ports, changed LOCALBASE back to /opt - Installed portupgrade with BDB1. Thanks, Jim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Can't install ruby-bdb on RELEASE-6.1
I'm setting up a new system with 6.1-RELEASE, and I forgot to install portupgrade from a package during the OS install. ruby-bdb fails to build, complaining that it doesn't know how to make 'all' (it doesn't specify which directory it's in, but it's right after it runs extconf.rb). Any clues? (Note: when I posted this earlier I mentioned changing LOCALBASE. Further testing has shown that it fails regardless of LOCALBASE setting.) Thanks, Jim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can't install fresh ruby-bdb (was when LOCALBASE is not /usr/local)
On Wed, Jul 19, 2006 at 03:00:09PM +0400, Sergey Matveychuk wrote: > Jim Trigg wrote: > > I'm setting up a new system with 6.1-RELEASE, and I forgot to install > > portupgrade from a package during the OS install. ruby-bdb fails to > > build, complaining that it doesn't know how to make 'all' (it doesn't > > specify which directory it's in, but it's right after it runs > > extconf.rb). Any clues? > > How subject joins to the message? > When you changed LOCALBASE? Sorry, I lost track and forgot to update the subject. I tried again after changing LOCALBASE back and ruby-bdb still fails to build. I've gotten portupgrade working for the time being by specifying BDB1 instead of BDB4. Thanks, Jim -- Jim Trigg, Lord High Everything Else O- /"\ \ / ASCII RIBBON CAMPAIGN Hostmaster, Huie Kin family websiteXHELP CURE HTML MAIL Verger, All Saints Church - Sharon Chapel / \ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Can't install fresh ruby-bdb when LOCALBASE is not /usr/local
I'm setting up a new system with 6.1-RELEASE, and I forgot to install portupgrade from a package during the OS install. ruby-bdb fails to build, complaining that it doesn't know how to make 'all' (it doesn't specify which directory it's in, but it's right after it runs extconf.rb). Any clues? Thanks, Jim -- Jim Trigg, Lord High Everything Else O- /"\ \ / ASCII RIBBON CAMPAIGN Hostmaster, Huie Kin family websiteXHELP CURE HTML MAIL Verger, All Saints Church - Sharon Chapel / \ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
