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 +-+ science/gwyddion| 2.45| 2.46 +-+ 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: Looking for a committer net-mgmt/prometheus
Thank you Kurt for committing both ports. For the prometheus one, I see now I attached a stale patch file that referenced version 1.1.3. Thanks for going the extra mile and fixing that for me. I have learned a lesson, and will be much more careful in the future. Again, thank you! Jev On Fri, Oct 14, 2016 at 10:25 PM Kurt Jaeger wrote: > Hi! > > > I just updated https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212468 > patch > > attachment to build the latest release of prometheus. It's now 1.2.1 > > Well, the version number in the patch was 1.1.3, but > changing that to 1.2.1 was easy, test-building was OK, so: done. > > > Can I get a committer to review, and possibly commit? This new port > request > > and my other one (node_exporter: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212467) have both been > > open since Sep 9th. > > Also done. > > -- > p...@opsec.eu+49 171 3101372 <+49%20171%203101372> >4 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"
wireshark 2.2.x build fail
Just a "heads up": wireshark 2.2.x introduces the compiler flag "-msse4.2" via 'configure' if the compiler accepts that flag. The capability, or otherwise, of the host machine is ignored as it is expected that the one module in which GCC will use these instructions has a run-time check. This does not work for CLANG on "deficient" hardware; LEMON (part of the build tool-chain) will also be compiled with these extended instructions and cause exceptions on hardware that doesn't support them :-( There's a related discussion on the wireshark-bugs list referring to "bug 10792" Michael ___ 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: harder and harder to avoid pkg
Has anyone actually looked/asked how other OS's solve this problem? I too found "xxx-dev" vs "xxx-lib" annoying until I realized how clean it actually is. We should definitely be surveying the landscape before rolling our own NIH solution. -Alfred On 10/14/16 8:30 AM, Julian Elischer wrote: On 14/10/2016 4:27 AM, Matthieu Volat wrote: On Fri, 14 Oct 2016 13:05:35 +0200 David Demelier wrote: 2016-10-14 11:22 GMT+02:00 Baptiste Daroussin : It is imho doable in both sides. We could imagine tagging the plist/manifest so pkg can allow a user to install only the things tagged as runtime for exemple which would do the job. for what Julian is asking for beside adding lots of complexity pkg(8) and adding a nightmare in the solver. That would "please" the people that want "hey keep the giant flat package as it is better for dev given I don't have to install the -devel version something" and the people wanting fine grain selection if they need to. But on the ports side that would be a nightmare having to tag all the plist (and this cannot be automated because there are to many corner cases. IIRC, rpm builders have script that automate this by finding files in standard directories. Probably by checking in the stage a include/ directory and "tag" it as the development part. Unless things changed very recently, not quite : you have to pile subpackage declaration and files sections according to the subpackages you create. The only things it has to ease the burden is you can use wildcard patterns to select files. It will be the most smart way of doing this but still require some addition to pkg. Probably like: - pkg install mylib - pkg install -t dev mylib - pkg install -t runtime mylib - pkg install -t dev,runtime,doc mylib Just thinking ;) More options, then more options to `pkg info` to get what was installed when something cannot build, then more pkg search options and manpage because more "-t" flags will be added and we don't know what's needed? I'm glad people are at least thinking about it... I don't think there are so many categories. Are we installing onto a development machine, user machine, or an appliance? appliances don't need man pages. User machines need man pages for programs but not for libraries and developer machines.. everything.. ___ 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"
poudriere failures after pkg 1.9.0 update
In my poudriere run from today nearly all packages failed. pkg was upgraded to 1.9.0 since the last run, Here are the relevant lines from 3 different build logs: [10amd64-default-job-01] `-- Extracting python27-2.7.12: .. pkg-static: Fail to create temporary file: /usr/local/lib/python2.7/test/decimaltestdata/.or.decTest.0zPFOC6i4BVl: File exists [10amd64-default-job-01] | | `-- Extracting libX11-1.6.4,1: ... pkg-static: Fail to create temporary file: /usr/local/man/man3/.XDrawString16.3.gz.zeXVDUi2eY7z: File exists [10amd64-default-job-01] Extracting ruby-2.2.5_1,1: .. pkg-static: Fail to create temporary file: /usr/local/share/ri/2.2/system/Fixnum/.inspect-i.ri.J96xApHkdlnr: File exists ___ 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"
