FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/ucommon | 6.1.11 | 6.5.2 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
net-mgmt/phpipam upgrade port to latest version
Hi, according to phpipam website, latest version since December of 2014 is 1.1.010: http://phpipam.net/phpipam-1-1-010-update-released/ Is there a reason why version in FreeBSD ports is still at 1.0? Can it be upgraded to the latest version? Regards, -- Marko Cupać https://www.mimar.rs/ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Ports with duplicate LATEST_LINKs
Ports Index build wrote: Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is deprecated. See the portmgr blog post for more information: http://blogs.freebsdish.org/portmgr/2013/10/03/package-name-collisions/ Thanks, Erwin Annoying Reminder Guy III Lansing LATEST_LINK PORTNAME MAINTAINER == databases/postgresql-libpqxx3 20080111.freebsd@ab.ote.we.lv devel/tortoisehg 6year...@gmail.com databases/p5-DBIx-SearchBuilder miche...@sorbs.net databases/pgpool-II-33 miche...@sorbs.net net/bmon miche...@sorbs.net www/p5-REST-Client miche...@sorbs.net www/py-collective.easytemplate miche...@sorbs.net www/py-collective.templateengines miche...@sorbs.net Total: 25123 ports Epic misfire, or did I misread the intent? [michelle@colossus /usr/home/michelle]$ grep LATEST_LINK /usr/ports/databases/pgpool-II-33/* [michelle@colossus /usr/home/michelle]$ grep PKGNAMESUFFIX /usr/ports/databases/pgpool-II-33/* /usr/ports/databases/pgpool-II-33/Makefile:PKGNAMESUFFIX=33 -- Michelle Sullivan http://www.mhix.org/ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Ports with duplicate LATEST_LINKs
Am 18.08.2015 um 14:37 schrieb Ports Index build indexbu...@freebsd.org: The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is deprecated. See the portmgr blog post for more information: http://blogs.freebsdish.org/portmgr/2013/10/03/package-name-collisions/ devel/firmware-utils s...@assitu.de graphics/pngnq s...@lassitu.de mail/roundcube-sauserprefs s...@lassitu.de mail/squirrelmail-login_auth-plugin s...@lassitu.de science/py-ws2300s...@lassitu.de www/ttf2eot s...@lassitu.de I’m trying to make sense of this, but having trouble. What exactly is the problem with these ports? None of the ports use LATEST_LINK, I believe the package names are unique, and there’s no multiple ports for these that only differ in the version number. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Samba 4.2.3 exited on signal 4
Could be that you are affected by https://bugzilla.samba.org/show_bug.cgi?id=11455 Can you, please, verify, that it is the case? With best regards, Timur On Tue, Aug 18, 2015 at 1:43 PM, Enrique Ayesta Perojo eaye...@portugalete.uned.es wrote: Hello, I have updated a Samba 4.1 installation to latest Samba 4.2.3 from ports and it doesn't start anymore, it seems to start but after a while (it seems that it's reading or trying to read from disk) it suddenly stops with signal 4 (Illegal instruction). Has anybody have the same problem or have any idea what could be the reason? Thanks ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ 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
Samba 4.2.3 exited on signal 4
Hello, I have updated a Samba 4.1 installation to latest Samba 4.2.3 from ports and it doesn't start anymore, it seems to start but after a while (it seems that it's reading or trying to read from disk) it suddenly stops with signal 4 (Illegal instruction). Has anybody have the same problem or have any idea what could be the reason? Thanks ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: net-mgmt/phpipam upgrade port to latest version
Hi! according to phpipam website, latest version since December of 2014 is 1.1.010: http://phpipam.net/phpipam-1-1-010-update-released/ Is there a reason why version in FreeBSD ports is still at 1.0? Can it be upgraded to the latest version? If someone provides a patch to update the port, that would speed up things. That's probably the only reason for the missing update. Jake ? -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Ports with duplicate LATEST_LINKs
+--On 18 août 2015 14:53:31 +0200 Michelle Sullivan miche...@sorbs.net wrote: | Ports Index build wrote: | Dear port maintainers, | | The following list includes ports maintained by you that have duplicate | LATEST_LINK values. They should either be modified to use a unique | PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is | deprecated. See the portmgr blog post for more information: | http://blogs.freebsdish.org/portmgr/2013/10/03/package-name-collisions/ | | | Thanks, | Erwin Annoying Reminder Guy III Lansing | | | LATEST_LINK PORTNAME MAINTAINER | | == databases/postgresql-libpqxx3 20080111.freebsd@ab.ote.we.lv | devel/tortoisehg 6year...@gmail.com | | databases/p5-DBIx-SearchBuilder miche...@sorbs.net | databases/pgpool-II-33 miche...@sorbs.net | net/bmon miche...@sorbs.net | www/p5-REST-Client miche...@sorbs.net | www/py-collective.easytemplate miche...@sorbs.net | www/py-collective.templateengines miche...@sorbs.net | | | | Total: 25123 ports | | Epic misfire, or did I misread the intent? Epic misfire, LATEST_LINK is gone, so, every port has the same, empty string, value. -- Mathieu Arnold pgpE1PAYQDYKC.pgp Description: PGP signature
Re: Samba 4.2.3 exited on signal 4
Hi, Stefan! Was it a recent case? I belive this problem with md5.so was addressed while ago in the upstream. With regards, Timur Bakeyev. On Tue, Aug 18, 2015 at 5:58 PM, Stefan Esser s...@freebsd.org wrote: Am 18.08.2015 um 14:07 schrieb Timur I. Bakeyev: Could be that you are affected by https://bugzilla.samba.org/show_bug.cgi?id=11455 Can you, please, verify, that it is the case? A good test is to install the pre-compiled package and compare ldd output for the port compiled by you and the package binaries (i.e. strip off the addresses and compare only the filenames that ldd reports for either smbd binary). In my case the smbd and smbclient where linked against a wrong MD5 library (/usr/local/lib/libmd5.so from www/libwww) instead of the system library (/usr/lib/libmd.so). This was due to the configure script preferring libmd5.so over libmd.so ... 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 ___ 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: Removal of $UNIQUENAME
On Aug 18 22:49, Kimmo Paasiala wrote: It would have been nice to have some kind of announcement about the removal of $UNIQUENAME. I for example was depending on it in my make.conf with declarations like these: vim_SET= CONSOLE vim_UNSET= GTK2 RUBY TCL I can of course rewrite those now using $OPTIONS_NAME (editors_vim prefix instead of vim) after reading bsd.option.mk and figuring out the way that works... -Kimmo There was. pkg updating UNIQUENAME will show you the announcement. Or just look at the top of /usr/ports/UPDATING. -- Matt ___ 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
Removal of $UNIQUENAME
It would have been nice to have some kind of announcement about the removal of $UNIQUENAME. I for example was depending on it in my make.conf with declarations like these: vim_SET= CONSOLE vim_UNSET= GTK2 RUBY TCL I can of course rewrite those now using $OPTIONS_NAME (editors_vim prefix instead of vim) after reading bsd.option.mk and figuring out the way that works... -Kimmo ___ 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: Removal of $UNIQUENAME
+--On 18 août 2015 22:49:47 +0300 Kimmo Paasiala kpaas...@gmail.com wrote: | It would have been nice to have some kind of announcement about the | removal of $UNIQUENAME. I for example was depending on it in my | make.conf with declarations like these: | | vim_SET= CONSOLE | vim_UNSET= GTK2 RUBY TCL | | I can of course rewrite those now using $OPTIONS_NAME (editors_vim | prefix instead of vim) after reading bsd.option.mk and figuring out | the way that works... Just running make will tell you that: # make vim_SET=CONSOLE vim_UNSET=GTK2 RUBY TCL /!\ WARNING /!\ You are using vim_SET which is not supported any more, use: editors_vim_SET= CONSOLE You are using vim_UNSET which is not supported any more, use: editors_vim_UNSET= GTK2 RUBY TCL -- Mathieu Arnold pgpHxXoL0D3wG.pgp Description: PGP signature
Re: Removal of $UNIQUENAME
On Wed, Aug 19, 2015 at 1:18 AM, Mathieu Arnold m...@freebsd.org wrote: +--On 18 août 2015 22:49:47 +0300 Kimmo Paasiala kpaas...@gmail.com wrote: | It would have been nice to have some kind of announcement about the | removal of $UNIQUENAME. I for example was depending on it in my | make.conf with declarations like these: | | vim_SET= CONSOLE | vim_UNSET= GTK2 RUBY TCL | | I can of course rewrite those now using $OPTIONS_NAME (editors_vim | prefix instead of vim) after reading bsd.option.mk and figuring out | the way that works... Just running make will tell you that: # make vim_SET=CONSOLE vim_UNSET=GTK2 RUBY TCL /!\ WARNING /!\ You are using vim_SET which is not supported any more, use: editors_vim_SET= CONSOLE You are using vim_UNSET which is not supported any more, use: editors_vim_UNSET= GTK2 RUBY TCL -- Mathieu Arnold I see none of those warnings in my poudriere build logs, I'm not exactly sure where the problem is but I guess that's why I missed the change altogether. I do see the warnings fine when I run make(1) directly in a port directory though. -Kimmo ___ 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: Removal of $UNIQUENAME
On Wed, Aug 19, 2015 at 5:45 AM, Kimmo Paasiala kpaas...@gmail.com wrote: On Wed, Aug 19, 2015 at 1:18 AM, Mathieu Arnold m...@freebsd.org wrote: +--On 18 août 2015 22:49:47 +0300 Kimmo Paasiala kpaas...@gmail.com wrote: | It would have been nice to have some kind of announcement about the | removal of $UNIQUENAME. I for example was depending on it in my | make.conf with declarations like these: | | vim_SET= CONSOLE | vim_UNSET= GTK2 RUBY TCL | | I can of course rewrite those now using $OPTIONS_NAME (editors_vim | prefix instead of vim) after reading bsd.option.mk and figuring out | the way that works... Just running make will tell you that: # make vim_SET=CONSOLE vim_UNSET=GTK2 RUBY TCL /!\ WARNING /!\ You are using vim_SET which is not supported any more, use: editors_vim_SET= CONSOLE You are using vim_UNSET which is not supported any more, use: editors_vim_UNSET= GTK2 RUBY TCL -- Mathieu Arnold I see none of those warnings in my poudriere build logs, I'm not exactly sure where the problem is but I guess that's why I missed the change altogether. I do see the warnings fine when I run make(1) directly in a port directory though. -Kimmo Disregard, the warnings do show up fine now in poudriere logs: ===phase: check-sanity /!\ WARNING /!\ You are using vim_SET which is not supported any more, use: editors_vim_SET= CONSOLE === I was confused because the warnings apparently weren't added until the commit yesterday that removed the support for $UNIQUENAME and I was searching trough my old logs for the warnings and found nothing. -Kimmo ___ 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
Running ''portmaster ghostscript9-9.06_10'' takes a lot of time
All my ports are up to date, but running ''portmaster -va'' on ~1000 ports takes more then 50 minutes. Most time is spend on ghostscript9-9.06_10 I started a ''portmaster ghostscript9-9.06_10'' a while ago and it does not do any thing yet but using 100% CPU on one prosessor. What is going on? -- Henk ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Ports with duplicate LATEST_LINKs
On Tuesday, 18 August 2015 at 12:37:31 +, Ports Index build wrote: Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. Without counting, it looks like a complete list of all ports, unsorted. Would it be possible to modify the script to send a list of relevant ports to each committer affected? Greg -- Sent from my desktop computer. Finger g...@freebsd.org for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft MUA reports problems, please read http://tinyurl.com/broken-mua pgp4Jh11Hj09K.pgp Description: PGP signature
Re: Perl 5.20 breaks /usr/bin/perl
Yes, it does not create a /usr/bin/perl symlink, starting with Perl 5.20. I'm curious about the logic behind this (automatic symlink removal without a large warning message)? It would seem to come with a high cost and little (any?) benefit. Shouldn't this at least be a dialog option? If you still need one, and are not using some common shebang, like /usr/local/bin/perl, which still works, or /usr/bin/env perl, which also still works, create one yourself. /usr/bin/env may or may not work depending on the PATH it inherits. A symlink to /usr/bin would be best practice considering how many perl scripts specify this path, how many FreeBSD end-users are likely to be negatively impacted, how few might be positively impacted, and how it's removal will make it that much harder to advocate for FreeBSD's otherwise good cross-platform and cross-version compatibility. Roger ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Ports with duplicate LATEST_LINKs
On 2015-08-18 18:15, Greg 'groggy' Lehey wrote: On Tuesday, 18 August 2015 at 12:37:31 +, Ports Index build wrote: Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. Without counting, it looks like a complete list of all ports, unsorted. Would it be possible to modify the script to send a list of relevant ports to each committer affected? Greg This, apparently, was fallout from LATEST_LINK going away, and the check script not getting the memo.. erwin@'s disabled the nastygram. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Ports with duplicate LATEST_LINKs
I got an email with this subject but I’m not sure what to do about it. The port on the list which I maintain (deskutils/autocutsel) doesn’t use LATEST_LINK or munge PKGNAME at all, and I don’t see any collisions in e.g. INDEX-10. I tried the recipes at https://wiki.freebsd.org/ports/PkgNameCollisions but they didn’t produce any output, and my awk-foo isn’t nearly good enough to debug. I’m all for cleaning up the ports tree, but need a little more direction if my ports aren’t up to par. JN ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Ports with duplicate LATEST_LINKs
Hi! I got an email with this subject but I?m not sure what to do about it. Ignore it, someone sent the wrong stuff. -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Ports with duplicate LATEST_LINKs
Hi, This looks like a bsd.port.mk or similar change resulting in PKGNAME*FIX not being put into LATEST_LINK? Or have these all been broken a while? Chris On 18 August 2015 13:37:23 BST, Ports Index build indexbu...@freebsd.org wrote: Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique PKGNAME, e.g. by using PKGNAMESUFFIX. Note that NO_LATEST_LINK is deprecated. See the portmgr blog post for more information: http://blogs.freebsdish.org/portmgr/2013/10/03/package-name-collisions/ Thanks, Erwin Annoying Reminder Guy III Lansing LATEST_LINK PORTNAME MAINTAINER == databases/postgresql-libpqxx3 20080111.freebsd@ab.ote.we.lv devel/tortoisehg 6year...@gmail.com math/cryptominisat 6year...@gmail.com math/py-cryptominisat 6year...@gmail.com math/stp 6year...@gmail.com security/qtkeychain-qt4 6year...@gmail.com security/qtkeychain-qt5 6year...@gmail.com x11-fonts/hasklig6year...@gmail.com russian/wordpress9267...@gmail.com mail/postfinger a.j.cai...@halplant.com x11-wm/bbkeysa.j.cai...@halplant.com x11-wm/bbpager a.j.cai...@halplant.com x11-wm/blackbox a.j.cai...@halplant.com databases/p5-DBIx-VersionedDDL a...@wave2.org devel/p5-MooseX-Attribute-ENV a...@wave2.org www/jawstats a...@wave2.org devel/p5-App-Build alex.bakh...@gmail.com www/p5-Catalyst-TraitFor-Controller-DBIC-DoesPaging alex.bakh...@gmail.com japanese/alias-fonts cqg00...@nifty.ne.jp japanese/k10 cqg00...@nifty.ne.jp japanese/k12 cqg00...@nifty.ne.jp japanese/mh cqg00...@nifty.ne.jp accessibility/eflite david.k.ge...@gmail.com accessibility/yasr david.k.ge...@gmail.com audio/hydrogen free...@shaneware.biz audio/hydrogen-devel free...@shaneware.biz devel/godot free...@shaneware.biz graphics/opencolorio free...@shaneware.biz graphics/opencolorio-tools free...@shaneware.biz graphics/openimageio free...@shaneware.biz graphics/openshadinglanguage free...@shaneware.biz graphics/py-openimageio free...@shaneware.biz audio/aften ga...@zahemszky.hu audio/autocd k...@matpockuh.ru net/wmwlmon lu...@pobox.com converters/asr10 m.indleko...@gmx.de converters/cmios9m.indleko...@gmx.de ports-mgmt/portrac mario.g.pav...@gmail.com mail/p5-MIME-Charset olivier.gir...@univ-angers.fr mail/p5-MIME-EncWords olivier.gir...@univ-angers.fr textproc/p5-Unicode-LineBreak olivier.gir...@univ-angers.fr devel/p5-Time-Format sergey.dya...@gmail.com devel/py-robotframework vladimir.chukha...@gmail.com devel/py-robotframework-pabot vladimir.chukha...@gmail.com devel/py-robotframework-ride vladimir.chukha...@gmail.com devel/py-robotframework-selenium2library vladimir.chukha...@gmail.com devel/py-robotremoteserver vladimir.chukha...@gmail.com ports-mgmt/porttree vladimir.chukha...@gmail.com www/py-django-allauth vladimir.chukha...@gmail.com sysutils/pp a.ar...@gmail.com audio/xwave a0...@marimga.de games/xlogical aa...@baugher.biz sysutils/usrinfo aa...@snaphat.com sysutils/btsixad a...@q-fu.com editors/texstudioabili...@gmail.com devel/nxt-python
Re: Samba 4.2.3 exited on signal 4
Am 18.08.2015 um 14:07 schrieb Timur I. Bakeyev: Could be that you are affected by https://bugzilla.samba.org/show_bug.cgi?id=11455 Can you, please, verify, that it is the case? A good test is to install the pre-compiled package and compare ldd output for the port compiled by you and the package binaries (i.e. strip off the addresses and compare only the filenames that ldd reports for either smbd binary). In my case the smbd and smbclient where linked against a wrong MD5 library (/usr/local/lib/libmd5.so from www/libwww) instead of the system library (/usr/lib/libmd.so). This was due to the configure script preferring libmd5.so over libmd.so ... 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
