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/ocaml-xstrp4 | 1.8.1 | 1.8.2 +-+ net-mgmt/weathermap | 1.1.1 | 29.0.0 +-+ 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"
Re: FreeBSD Port: phpvirtualbox-4.3.2 & virtualbox-ose-4.3.36
Am 05.03.2016 1:01 vorm. schrieb "Michael" : > > Hi all, > > > > I write this as I like to request a major upgrade for virtualbox related > ports on freebsd. > > > > Currently I face problems using the current ports with php70 port compiled. > > I don't want to go back to port php56. > > > > Those problems can easy be fixed when phpvirtualbox-4.3.2 gets an upgrade to > phpvirtualbox-5.0-5 > > as it now support php7 out of the box. > > Please have a look: > https://github.com/imoore76/phpvirtualbox/blob/develop/CHANGELOG.txt > Changelog. > > But before upgrading, the new Virtualbox version must be upgraded also see > https://www.virtualbox.org/wiki/Downloads > > > > Please can those ports be upgraded by someone for support of systems running > PHP 7? > > > > Category www > > > > > > phpvirtualbox-4.3.2 needs an upgrade for support of php 7 and > phpvirtualbox-5.0-5 > > > > > > Category emulators > > -- > > > > virtualbox-ose-4.3.36 needs an upgrade for support of php 7 and > phpvirtualbox-5.0-5 > > > > virtualbox-ose-additions-4.3.36 needs an upgrade for support of php 7 and > phpvirtualbox-5.0-5 > > > > virtualbox-ose-kmod-4.3.36 needs an upgrade for support of php 7 and > phpvirtualbox-5.0-5 > > > > > > > > Thank you for all the work! > > > > With best regards, > > Michael Hi Michael, we know that we need to update vbox to 5.x but the sad truth is that we do not have a reasonable stable version of it. The port builds but the kernel module doesn't work properly so instead of breaking vbox for all people we will just stay at the last stable version that we have. phpvirtualbox is not backwards compatible so you have two options: 1) help on vbox 5.x port 2) create a phpvirtualbox patch for php7 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [CFT] net-im/ejabberd to 16.01
On Mon, 29 Feb 2016 19:34:09 +0530 ash...@freebsd.org (Ashish SHUKLA) wrote: > On Mon, 29 Feb 2016 14:37:22 +0100, Matthieu Volat said: > > > [...] > > > | Hmm, I'll be a bit overwhelmed until thursday, I'll check that... > > Thanks, and I appreciate it. > > [...] > > | Thanks, there was another blocking issue for me yesterday, which is the > ejabberdctl is now in bash. > > | If possible, I'd like to make a patch to (optionally) revert to pure sh, as > I find it a bit sad to go full bash only to read a few parameters... > > | I'll keep you informed > > Thanks in advance, if you could provide the patch. For now, I have updated the > diff to include dependency on bash, which I apparently missed before :/ > > New diff: > > https://people.freebsd.org/~ashish/diffs/ejabberd-16.01-01.diff > sha256 sum: ec71fdd19c752b22271ce6e3f899b966b0017f05fa13532d1decf18478e41b6e > Ok, back on business! My issue with the non-applied patchs is that those were not creates in the files subdir in ejabberd, but in a ejabberd/files subdir. Regarding the pam module installation, it seems to be installed in : /usr/local/lib/erlang/lib/ejabberd-16.01/lib/p1_pam-1.0.0/priv/bin/epam But ejabberd at start will fail with : 2016-03-05 17:52:49.297 [error] <0.394.0> Can't open file "/usr/local/lib/erlang/lib/ejabberd-16.01/lib/erlang/lib/ejabberd-16.01/priv/bin/epam": enoent So I guess it's not installed in the right place? Then, regarding the bash issue, I made some progress, but I still need to test it a bit more to be sure it do not introduce new bugs (it's not much, but I have to see if the kinda simple shell escaping function equivalent I put is enough). -- Matthieu Volat pgpCwzOQ0hyZ_.pgp Description: OpenPGP digital signature
Re: graphics/giflib: Update to 5.1.2_1 breaks GIF rendering in Konqueror
Stefan Ehmann wrote: > On 29.02.2016 18:25, Patrick Hess wrote: > > After upgrading graphics/giflib from 5.1.1 to 5.1.2_1, > > Konqueror won't display GIF images in web pages: > I'm seeing the same issue. > > If I use webkit rendering (via www/kwebkitpart) GIFs work. Just gave it a try, and indeed, GIFs render fine with webkit. Unfortunately, webkit still has the same issue where it chooses the wrong font faces for some of the fonts, especially on pages that use web fonts. > But I don't know if webkit depends on giflib or uses it's > own GIF rendering. I don't think it uses giflib, as "pkg info --required-by giflib" doesn't mention webkit. Patrick ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: graphics/giflib: Update to 5.1.2_1 breaks GIF rendering in Konqueror
On 05.03.2016 19:12, Patrick Hess wrote: Stefan Ehmann wrote: On 29.02.2016 18:25, Patrick Hess wrote: After upgrading graphics/giflib from 5.1.1 to 5.1.2_1, Konqueror won't display GIF images in web pages: I'm seeing the same issue. If I use webkit rendering (via www/kwebkitpart) GIFs work. Just gave it a try, and indeed, GIFs render fine with webkit. Unfortunately, webkit still has the same issue where it chooses the wrong font faces for some of the fonts, especially on pages that use web fonts. There's another workaround: Settings->Configure Konqueror File Management->File Associations Select image/gif Go to embedding tag: Select gvpart (part of gwenview) as preferred handler The default khtmlimage (part of kdelibs) doesn't work. Haven't done any further analysis yet. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: graphics/giflib: Update to 5.1.2_1 breaks GIF rendering in Konqueror
Patrick Hess writes: > After upgrading graphics/giflib from 5.1.1 to 5.1.2_1, Konqueror won't > display GIF images in web pages: > > http://www.phess.net/images/giflib-bug.png > > On the left hand side, with giflib 5.1.1, everything looks as expected. > On the right hand side, after upgrading giflib to 5.1.2_1, none of the > GIF icons are rendered correctly. Only the Fresh Ports logo and the two > magnifying glass icons are still there (as they're JPEGs, not GIFs). > > I personally prefer using Konqueror over that obese Firefox for most of > my web browsing, but it feels like I'm the only one. Is anybody else out > there using Konqueror and can confirm (or disconfirm, for that matter) > this behaviour? It's weird, but it works fine here with an up-to-date ports tree, but I build my own packages with Poudriere. I see a new kdelibs4 package was generated in the cluster a couple of days ago, can you try reinstalling to see if it was a matter of somehow giflib being originally updated without triggering a rebuild of the kdelibs4 port caused it (it shouldn't, I think)? Otherwise, do you get any useful messages on the terminal when you open FreshPorts with khtml? ___ 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: openblas 0.2.15,1 port broke build for BARCELONA AMD core
Andrew Reilly writes: > Hi there, > > My portmsaster run just broke on the recent openblas upgrade, with version > stamp in head/math/openblas/Makefile 409114 26-02-18 16:35:48Z rakuco. Now > that > I’ve hacked on this to make it build, I remember having done something like > this the last time, so perhaps nothing has actually changed in this respect, > there’s just been a version increase that still doesn’t know about my CPU. > > My build/target machine is, according to sysctl: > hw.machine: amd64 > hw.model: AMD A6-3500 APU with Radeon(tm) HD Graphics > hw.ncpu: 3 > > The auto-config system for openblas has determined that this is (in config.h): > #define AMD_UNKNOWN > but also > #define CORE_BARCELONA > #define CHAR_CORENAME “BARCELONA” > > So on the assumption that the AMD_UNKNOWN should be BARCELONA, I have tweaked > cpuid_x86.c to add case 3 along with case 1 and case 10 in the > switch(exfamily) > to return CPUTYPE_BARCELONA. > > I’m not sure if it wouldn’t have been better to slide that in with case 6, > because model=1 and support_avx()->0, so that would have worked too. > > the full set of get_cputype() values for my machine are: > family=0xf, exfamily=0x3, model=0x1, exmodel=0x0, support_avx=0 > > The code in cpuid_x86.c thinks that NUM_CORES is 1, despite the sysctl > information above, so I guess that only one core is going to be used, but > since > this is not a high performance machine and is generally thermally challenged, > I’m not too concerned about that. Just want it to build at all. > > With this couple of tweaks the math/openblas port seems to have built OK, so I > hope that this change can be included in the port or the up-stream so that I > don’t have to remember to do this all again next time! Hi Andrew, I don't maintain the openblas port, I just committed a patch for it that was sent to Bugzilla. This looks like a problem that should be reported upstream (https://github.com/xianyi/OpenBLAS/issues), it's even possible it's already been fixed in their git repository. You can also file a bug in our bug tracker so the port maintainer can take a look at this, but I don't think there's much he can do besides relaying that information upstream. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
pkg lock doesn't work if a dependency wants an upgrade
What can I do to help diagnose this? I have setup an isolated test system where I can easily return it to a pre-upgraded state. I don't remember pkg printing a list of locked packages in the past so my faith in proper operation was increased but I was tricked. It looks like pkg upgraded postfix anyway because mailman depends on postfix. If I lock both postfix and mailman, pkg leaves postfix alone. Why can't the action of upgrading a package make a last minute check to make sure a package is not locked? Additionally why would upgrading a package cause it to become unlocked? Thanks. Note: I am not interested in formally modifying things so they avoid upgrading to postfix 3. I plan to upgrade soon but not tonight. # pkg lock postfix postfix-2.11.7_1,1: lock this package? [y/N]: y Locking postfix-2.11.7_1,1 # pkg lock -l Currently locked packages: postfix-2.11.7_1,1 # pkg query %ro postfix mail/mailman # pkg upgrade Updating pkg-2015 repository catalogue... pkg-2015 repository is up-to-date. All repositories are up-to-date. New version of pkg detected; it needs to be installed first. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pkg: 1.6.4 -> 1.6.4_1 The operation will free 64 B. 2 MiB to be downloaded. Proceed with this action? [y/N]: y Fetching pkg-1.6.4_1.txz: 100%2 MiB 2.5MB/s00:01 Checking integrity... done (0 conflicting) [1/1] Upgrading pkg from 1.6.4 to 1.6.4_1... [1/1] Extracting pkg-1.6.4_1: 100% Updating pkg-2015 repository catalogue... pkg-2015 repository is up-to-date. All repositories are up-to-date. Checking for upgrades (6 candidates): 100% Processing candidates (6 candidates): 16% postfix-2.11.7_1,1 is locked and may not be modified Processing candidates (6 candidates): 100% The following 8 package(s) will be affected (of 0 checked): Installed packages LOCKED: Package postfix-2.11.7_1,1 is locked and may not be upgraded to version 3.1.0,1 New packages to be INSTALLED: (don't worry about this part, it is from a package I left off) icu: 55.1 python: 2.7_2,2 Installed packages to be UPGRADED: openssh-portable: 7.1.p2,1 -> 7.2.p1,1 mailman: 2.1.20_2 -> 2.1.21_3 krb5: 1.14 -> 1.14.1 ca_root_nss: 3.22 -> 3.22.2 The process will require 68 MiB more space. 20 MiB to be downloaded. Proceed with this action? [y/N]: y Fetching openssh-portable-7.2.p1,1.txz: 100% 699 KiB 715.6kB/s00:01 Fetching mailman-2.1.21_3.txz: 100%3 MiB 3.6MB/s00:01 Fetching krb5-1.14.1.txz: 100%1 MiB 1.1MB/s00:01 Fetching ca_root_nss-3.22.2.txz: 100% 322 KiB 330.2kB/s00:01 Fetching postfix-3.1.0,1.txz: 100%1 MiB 1.6MB/s00:01 Fetching icu-55.1.txz: 100% 14 MiB 15.1MB/s00:01 Fetching python-2.7_2,2.txz: 100%996 B 1.0kB/s00:01 Checking integrity... done (0 conflicting) [1/8] Upgrading krb5 from 1.14 to 1.14.1... [1/8] Extracting krb5-1.14.1: 100% [2/8] Installing icu-55.1... [2/8] Extracting icu-55.1: 100% [3/8] Upgrading ca_root_nss from 3.22 to 3.22.2... [3/8] Extracting ca_root_nss-3.22.2: 100% [4/8] Upgrading postfix from 2.11.7_1,1 to 3.1.0,1... You may need to manually remove /usr/local/etc/postfix/main.cf if it is no longer needed. ==> You should manually remove the "postfix" user. ===> Creating users and/or groups. Using existing group 'mail'. Using existing group 'maildrop'. Using existing group 'postfix'. Using existing user 'postfix'. [4/8] Extracting postfix-3.1.0,1: 100% === Postfix already activated in /etc/mail/mailer.conf === postfix: Postfix is running with backwards-compatible default settings postfix: See http://www.postfix.org/COMPATIBILITY_README.html for details postfix: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload" postfix/postfix-script: refreshing the Postfix mail system <...> # pkg lock -l Currently locked 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"
