Re: Is there a way to subscribe to the commit messages for only ports you maintain?
On Tue, 18 May 2021, Julian H. Stacey wrote: I'd use /usr/ports/mail/procmail I wouldn't; it's an unsupported and obscure scripting language just asking for bugs, and actually has several CVEs against it. Better filters exist, such as "sieve" etc. -- Dave ___ 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: Hungarian: rST localisation for language "hu" not found
On Wed, 14 Apr 2021, Thierry Thomas wrote: [...] Note: it builds for the other languages, and only fails for Hungarian. Well, somebody has to say it so it may as well be me: is your hovercraft full of eels? -- Dave ___ 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: Deprecation of portsnap (was: Proposed ports git transition schedule)
On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote: Except that git will arbitrarily and randomly decide that it needs to run "gc" - which is similarly extravagant in memory usage. Last time I found one running, it thrashed that poor VM for 3 days. Would this be a good time to mention the https://ohshitgit.com/ site? Warning: it contains strong language... -- Dave ___ 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: INDEX build failed for 11.x
On Thu, 8 Apr 2021, at 03:23, Li-Wen Hsu wrote: > On Thu, Apr 8, 2021 at 9:49 AM Yasuhiro Kimura wrote: > > > > From: Ports Index build > > Subject: INDEX build failed for 11.x > > Date: Thu, 8 Apr 2021 00:05:39 GMT > > > > > INDEX build failed with errors: > > > Generating INDEX-11 - please wait..--- describe.accessibility --- > ... > > > make_index: /home/indexbuild/tindex/ports/databases/p5-AnyEvent-CouchDB: > > > no entry for /home/indexbuild/tindex/ports/databases/couchdb2 > > > > > (snip) > > > > Attached patch fixes the failure. Would someone please commit it? > > > > Best Regards. > > > > > > From 00e18b09e2438be2d7c1f4ca86a9092c5b46d585 Mon Sep 17 00:00:00 2001 > > From: Yasuhiro Kimura > > Date: Thu, 8 Apr 2021 10:40:22 +0900 > > Subject: [PATCH] databases/p5-AnyEvent-CouchDB: remove port > > > > Remove databases/p5-AnyEvent-CouchDB because it depends on expired > > databases/couchdb2. > ... > > The EXPIRATION_DATE of databases/couchdb2 and > databases/p5-AnyEvent-CouchDB are 2021-06-23, but couchdb2 got removed > earlier.The fastest way should be unremoving couchdb2, or, might be > better to check if p5-AnyEvent-CouchDB can use couchdb3. > > BTW, databases/couchdb3 also has an expiration date of 2021-06-23. > > Best, > Li-Wen Apologies for breaking the index. fixed in 71d418aef0c5999a575e4bd264526375823848c7 & updated 254869 Evidently I didn't even think of checking for dependencies of CouchDB - as a network service there shouldn't be *any* runtime depencies on CouchDB if you just install a client.. I'll make sure to do this in future for ports removals. - I've built databases/p5-AnyEvent-CouchDB & it functions perfectly without the unnecessary dependency - for CouchDB 3.x we're working on addressing the spidermonkey version dependency atm A+ Dave — O for a muse of fire, that would ascend the brightest heaven of invention! ___ 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: INDEX build failed for 11.x
On Mon, 29 Mar 2021, at 09:03, Ports Index build wrote: > INDEX build failed with errors: > Generating INDEX-11 - please wait..--- describe.accessibility --- ... > --- describe.lang --- > make[5]: "/home/indexbuild/tindex/ports/lang/gleam/Makefile" line 20: > Could not find Makefile.deps > make[5]: Fatal errors encountered -- cannot continue===> lang/gleam > failed Fixed in r569443 A+ Dave ___ 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: Python 2.7 removal outline
On Thu, 25 Mar 2021, George Mitchell wrote: [...] it is really not for everybody to use overlays in current state (overlays are poor documented at least). [...] Until this thread I had never heard of them. -- George I can't remember the last time I used overlays (certainly with CP/M); I didn't know that FreeBSD even supported them (why bother when you've got VM?). -- Dave ___ 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: MAIL ADMINISTRATIVE SERVICE CENTER
On Tue, 16 Feb 2021, Yuri Pankov wrote: As this came from freebsd.org, were they trying to shout something or do they have a compromised server? It's obvious it did NOT come from freebsd.org once you check the headers: Really? Here are my headers: Return-Path: Received: from mx2.freebsd.org (mx2.freebsd.org [96.47.72.81]) by aneurin.horsfall.org (8.15.2/8.15.2) with ESMTP id 11FFDtmL039444 for ; Tue, 16 Feb 2021 02:14:09 +1100 (EST) (envelope-from owner-freebsd-po...@freebsd.org) Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "mx1.freebsd.org", Issuer "R3" (verified OK)) by mx2.freebsd.org (Postfix) with ESMTPS id EE5DF95ED7; Mon, 15 Feb 2021 15:13:53 + (UTC) (envelope-from owner-freebsd-po...@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DfSL95Fdgz4gt0; Mon, 15 Feb 2021 15:13:53 + (UTC) (envelope-from owner-freebsd-po...@freebsd.org) Sure looks like freebsd.org to me, hence my comment about a compromised server... -- Dave ___ 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: MAIL ADMINISTRATIVE SERVICE CENTER
On Tue, 15 Feb 2021, administra...@freebsd.org wrote: (Nothing) As this came from freebsd.org, were they trying to shout something or do they have a compromised server? -- Dave ___ 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: CMAKE_PREFIX_PATH and /usr/local
On Fri, 15 Jan 2021, Gleb Popov wrote:
+if (CMAKE_SYSTEM_NAME MATCHES "BSD")
+include_directories("/usr/local/include")
This is most certainly a wrong thing to do. Instead of simply adding
-I/usr/local/include everywhere, you should fix problems for each
dependency that the software requires.
What's the problem, exactly? Ports have always installed themselves under
/usr/local, and I refuse to overwrite the base system (as Penguin/OS does;
well, Debian anyway), and the Mac ports system uses /opt/local.
I generally regard the base system i.e. that as distributed as being
non-userland, and overwritten only with updates. Backups are much more
manageable, as I don't have to worry about /bin, /lib etc.
-- Dave
___
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"
Bug 251656
Is there a method for getting this assigned? I'll admit I misspelled the port name in the subject, but now how do I fix the process? Thanks in advance. -- Dave Hayes - Consultant - LA CA, USA - d...@dream-tech.com >>>> *The opinions expressed above are entirely my own* <<<< One of the big differences between questions and answers is that a question may be asked at almost any time, but its answer may only come at a special time and place. ___ 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: FireFox keeps loosing data
On Thu, 12 Nov 2020, Andrea Venturoli wrote: Firefox uses sqlite databases to store cookies, history and other items. You should never store these on NFS. Really? It has worked properly for years; it's only been broken for some months. Besides history works perfectly. Wouldn't any corruption produce some sort of log somewhere? Never use file locking on NFS. Period. One day it *will* bite you, due to some yet-to-be-discovered bug. In the meantime, feel free to ignore the advice of those who have been there before... -- Dave ___ 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: Patch compiler warnings away?
On Thu, 1 Oct 2020, Moritz Schmitt wrote: I recently took over my first maintainership of a port and I have a question regarding on how to deal with compiler warnings. I've always treated warnings as potential errors, and act accordingly. One place I worked insisted that "-Wall" produce no messages, and my own Perl stuff has "use strict". -- Dave ___ 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: Aggressive ports removal
On Sun, 30 Aug 2020, Yuri wrote: However, not many people are willing to install sysutils/bsdstats, or know about it, so it only counts based on a tiny fraction of hosts running FreeBSD. Tried to install it, and... aneurin# portinstall bsdstats [Reading data from pkg(8) ... - 322 packages found - done] /usr/local/lib/ruby/site_ruby/2.4/pkgtools/pkgtools.rb:1180: warning: Insecure world writable dir /tmp/ in PATH, mode 040777 ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! sysutils/bsdstats (could not find a temporary directory) Gosh; /tmp is world-writable... Who'd've thought? aneurin# echo $PATH /sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/home/dave/bin: Hmmm... I don't see /tmp in there. aneurin# uname -a FreeBSD aneurin.horsfall.org 10.4-RELEASE-p13 FreeBSD 10.4-RELEASE-p13 #0: Thu Sep 27 09:21:23 UTC 2018 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 Yeah, it's old, but I'm building a new one. -- Dave ___ 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: Aggressive ports removal
On Mon, 31 Aug 2020 08:03:32 +1000 (EST) Dave Horsfall wrote: > What does "xtset" do that the following script does not? While accurate, this point is not relevant to the discussion at hand. I believe this discussion is about some people (including myself) feeling that ports are removed too aggressively. I would like to add my small voice to the people calling for some restraint on this. Ports that continue to work, despite years of changes in other software, shouldn't be removed. Those are likely the some of the best written ports. Part of the appeal of FreeBSD is it's ability to run legacy software, and a port that does not need maintenance isn't "dead" if it never needs maintenance in the first place. -- Dave Hayes - Consultant - LA CA, USA - d...@dream-tech.com >>>> *The opinions expressed above are entirely my own* <<<< Due to confusion, people mistake things for themselves; covetousness flares up, and they get into vicious cycles that cloud perceptions and enshroud them in ignorance. The vicious cycles go on and on, and people cannot be free. ___ 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: Aggressive ports removal
[ I seem to have missed the post to which this refers ] On Sun, 30 Aug 2020, Niclas Zeising wrote: Exactly. Another case in point: x11/xtset. Maintenance stopped in 1993, 11 days after the FreeBSD project came into existence. It works fine, and I find it very useful. If at some time in the future it should no longer work with the latest and greatest iteration of the C programming language or ports structure, that shouldn't be a reason to discard it. What does "xtset" do that the following script does not? I picked it up from $JOB a couple of decades ago. /usr/local/bin/wintit: # Change window title. # # 0 means both title and icon. # 1 means icon # 2 means title # echo -n ']0;'$*'' Watch out for the embedded ESC and ^G chars, and modify as necessary for SysVile i.e. "-n" vs. "\c". And no, printf(1) didn't exist back then, and I'm too lazy to fix it now. aneurin% cat /usr/ports/x11/xtset/pkg-descr Utility to set title on an xterm. -- Dave ___ 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: [HEADS UP] Planned deprecation of portsnap
On Mon, 10 Aug 2020, Robert Huff wrote: There are many users who never create any patches, but simply use the ports tree to install software. Add my name to that list. Mine too; this is a great way to drive "ordinary users" away from FreeBSD and towards, gasp, Penguin/OS... I took up FreeBSD when BSD/OS was shut down by WinDriver and found that the OpenBSD bods weren't too friendly towards newbies; the Mac is now my major system (with porting attempts to FreeBSD and Penguin, then back). Well, at least it has FreeBSD roots... (Used to use cvsup ... now subversion ... soon git ... where will the insanity end? :-) ) Hah! I started with SCCS :-) Before that we had an in-house system called SLUP (Source Line Update Program? This was in the 70s, and was based upon that canonical example of diff/ed). -- Dave ___ 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: State changes via pkg's scripts
On Wed, 8 Jul 2020, Dewayne Geraghty wrote: # cat +MANIFEST | jq -rM '.scripts' Sorry, but this always pushes one of my buttons. When using "cat file | proc" what's wrong with "proc < file"? -- Dave ___ 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: Port OPTIONS advice
On Wednesday, 20 May 2020 18:25:00 BST SirDice wrote: > Some time ago I took over maintainership of fs-uae. And I'd like to thank you very much for that! :-) I finally got around to installing it, what with have an unexpected few spare months of time on my hands. I managed to dump my old A1200 HDD to a file and eventually got it to boot after a trip down memory lane figuring out how to edit startup-sequence and user-startup to remove things like the SCSI drivers. There was one issue when I upgraded FreeBSD 11.3 --> 11.4. fs-uae would crash out immediately the main window opened. Even after doing a pkg upgrade -f I still ended up having to manually build some related graphics libraries before it would work again (Sorry, I didn't keep notes, IIRC it was mesa stuff) So now all I need to do is find a cheap gamepad that will work with it on FreeBSD :-) If anyone is interested, you can download the Assassin Games CDs full of PD games from archive.org (and much other Amiga related goodness. They boot and play just fine on fs-uae assuming you have the correct ROM file(s)) Sorry if that last bit came over as a bit of a commercial but it's years since I even plugged my old A1200 in, let alone played games on it. ___ 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: Fwd: unifi5, mongodb and python2
On Wed, 17 Jun 2020, at 09:04, Kurt Jaeger wrote: > Hi! > > > Looking for some feedback on this. Or should I just go ahead and create PRs? > Sounds good to me. I have recently done a few mongo Mongo mongo upgrades would I can prep some notes on that, perhaps in the wiki? We could reference it in the pkg-message perhaps? Dave ___ 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: LibreOffice 6.4.4 is coming!
On Thu, 11 Jun 2020, Shawn Webb wrote: There is nothing inconvenient about enjoying your hard work. You're awesome and your work (along with any other contributors) is very much appreciated. Thank you so much for all you do. Agreed; don't apologise for doing (hard) volunteer work, and of course anyone who complains is free to step forward... -- Dave, a happy LibreOffice user ___ 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: games/linux-steam-utils
On Wed, 10 Jun 2020, at 17:42, Jose Quinteiro wrote: > Howdy, > > Any chance we could get some committer love on > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246712 > > It's a smallish change that only affects Steam users. > > Thanks, > Jose pi@ has grabbed this, BTW. A+ Dave ___ 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"
Kodi 18.6 upgrade
Is anyone looking at upgrading the port of Kodi from the now rather old 17.6 to the current 18.6? I see there is a dev port for v19 which is still in alpha but no movement on v18 series. 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: lsof marked ignored
On Fri, 20 Mar 2020, Adam Weinberger wrote: That error should only occur if system sources are missing from /usr/src. Check that they're still there, and if not then check them out from svn. Does it not require kernel header files only? Only distributed with the source, which annoyed me because at the time I didn't have the room... -- Dave ___ 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: [RFC] Adding a Rados block driver to bhyve
On Mon, 9 Mar 2020, Miroslav Lachman wrote: There are some ports (for example sysutils/lsof) which need kernel sources to build. [...] Kernel sources, or just the headers? -- Dave ___ 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: xterm-353
On Mon, 3 Feb 2020, Christoph Moench-Tegeder wrote: You're right. For some reason, firefox is not handling the additional compression correctly (I see Content-Encoding: gzip in the headers, so it's advertised, but not unzipped by the browser, so I get a double- compressed file. Oh tempora, oh mores). Not enough time to dig into that right now. FWIW, I find that Firefox is becoming increasingly unreliable, with "dead" buttons etc (yes, I have JS enabled against my better judgement) and have to use Safari/Chrome instead. This is a pity, as I find that FF is much faster and I've used it for many years. -- Dave ___ 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"
"dlsym: resource temporarily unavailable" errors during build of lang/erlang on 11.3 i386
On beefy[1] I see the same error repeatedly during i386-only builds. I googled and am not even mildly enlightened [4]. Can anybody give me a hint please as to what this is about? gmake[5]: Entering directory '/wrkdirs/usr/ports/lang/erlang/work/otp-OTP-21.3.8.7/erts/emulator' if utils/gen_git_version i386-portbld-freebsd11.3/gen_git_version.mk; then touch beam/erl_bif_info.c; fi echo " PROFILE beam.prof.smp" PROFILE beam.prof.smp rm -f obj/i386-portbld-freebsd11.3/opt/smp/erl*.profraw set -e; LLVM_PROFILE_FILE="obj/i386-portbld-freebsd11.3/opt/smp/erlc-%m.profraw" \ ERL_FLAGS="-emu_type prof +S 1" erlc -W -DPGO \ -o obj/i386-portbld-freebsd11.3/opt/smp test/estone_SUITE.erl > obj/i386-portbld-freebsd11.3/opt/smp/PROFILE_LOG dlsym: Resource temporarily unavailable gmake[5]: *** [i386-portbld-freebsd11.3/Makefile:733: obj/i386-portbld-freebsd11.3/opt/smp/PROFILE] Abort trap (core dumped) I've also read LLVM's profile data page [2] and maybe this is something we don't even need to build at all? [1]: http://beefy1.nyi.freebsd.org/data/113i386-quarterly/518722/logs/erlang-21.3.8.7,4.log [2]: http://llvm.org/docs/CommandGuide/llvm-profdata.html [3]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234451 [4]: https://www.reactiongifs.com/wp-content/uploads/2013/11/I-have-no-idea-what-I-am-doing.gif thanks Dave ___ 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: Is IPV6 option still necessary?
On Wed, 9 Oct 2019, Wolfgang Zenker wrote: So, you don't *need* IPv6. But you might *want* to have it anyway. In my 40+ years career I've only encountered one (1) client that ran IPv6 internally (oddly enough, a law firm) and that was by management decree, not the tehchies' (come to think of it, I don't think they *had* a techie department). Roll the lawyer jokes... My router tries IPv6 first, but inevitably falls back to IPv4; IPv6 is a camel i.e. a horse designed by a committee. If you've ever tried to grok the IPv6 spec, your brain will explode... -- Dave ___ 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: FireFox and NFSv4
On Thu, 13 Jun 2019, Andrea Venturoli wrote: For years I've had my home on an NFSv3 server. Finally I decided to move to NFSv4. [...] I got bitten quite badly by NFS in its early years; I see nothing much has changed... I think it was to do with file-locking, I think. -- Dave ___ 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"
weather package weather-2.3_1 and port.
I have weather-2.3_1 installed on FreeBSD freebsd12 12.0-RELEASE-p3
FreeBSD 12.0-RELEASE-p3 GENERIC amd64, and the command, `weather lax`
gives the output:
Searching via airport...
Traceback (most recent call last):
File "/usr/local/bin/weather", line 66, in
if selections.get_bool("conditions", argument) or not (
File "/usr/local/lib/python3.6/site-packages/weather.py", line 102,
in get_bool
return bool(self.get(option, argument))
File "/usr/local/lib/python3.6/site-packages/weather.py", line 83, in
get
quiet=self.get_bool("quiet")
File "/usr/local/lib/python3.6/site-packages/weather.py", line 749,
in guess
stations.read(datafile)
File "/usr/local/lib/python3.6/configparser.py", line 697, in read
self._read(fp, filename)
File "/usr/local/lib/python3.6/configparser.py", line 1015, in _read
for lineno, line in enumerate(fp, start=1):
File "/usr/local/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
3699: ordinal not in range(128)
That is with latest package install or port compiled. Although it does
work compiled with `DEFAULT_VERSIONS+=python=2.7` in make.conf
What to do?
Thanks in advance, Dave Males.
___
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: Is there a way to build only the port from source, and install dependencies from packages with the make command?
On Tue, 30 Apr 2019, at 21:17, Adam wrote:
> On Tue, Apr 30, 2019 at 12:36 PM Yuri wrote:
>
> > Sometimes instructions to build some port from source are needed. "cd
> > /usr/ports/{caregory}/{port-name} && make" rebuilds everything from
> > source, including dependencies.
> >
> > Is there an easy way to make it install missing dependencies with pkg,
> > without listing them? I couldn't find such feature.
from within the appropriate port directory:
function make-depends --description 'installs runtime and buildtime
dependencies for a given port'
sudo pkg install -r FreeBSD --automatic (make build-depends-list
run-depends-list | sed -E -e 's,^.+/([^/]+/[^/]+$),\1,')
end
function make-pkg --description 'test port build locally'
make clean \
check-sanity \
fetch makesum checksum \
extract patch \
configure build \
stage stage-qa \
check-orphans \
check-plist \
package \
&& find /tmp/usr/ports -name \*.txz -type f
end
I use these locally while working on ports - should work similar for you too.
A+
Dave
___
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: FreeCAD 0.17 && /lib//libgcc_s.so.1
On Fri, 22 Feb 2019, Tijl Coosemans wrote: If I were the lang/gcc maintainer this -rpath problem would be my number one priority. The current maintainer has never proposed any solutions and when I submit patches he always resists. I'm done wasting my time fighting him. I'm late to this discussion (not being a Fortran/Python user) but is there any way to remove a recalcitrant maintainer? -- Dave ___ 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 does pkg want to install emby-server?
On Fri, 18 Jan 2019, at 22:27, Stefan Bethke wrote: > No matter what package I try to install on my 12-stable machine, pkg > always adds emby-server. When I check after the install, nothing > requires emby-server. What’s going on? you probably have a further package that is missing the emby-server as a dependency. sudo pkg check -d -v should tell you what package that is, either delete it or accept the corrective action A+ Dave ___ 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 falls behind port version - how do ports become pkg's?
On Mon, 12 Nov 2018, at 23:06, Karl Pielorz wrote: > >From what I can see mysql56-server in quarterly really does need updating > to fix the CVE's - so who am I best emailing to ask if > mysql56-server/client could be updated on security grounds? > > Thanks again, Hi Karl the best person is the maintainer of that port (now in CC) and request a "MFH" or "Move From Head". You can see who this in the Makefile or via https://www.freshports.org/databases/mysql56-server for example. A+ Dave ___ 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: databases/couchdb upgrade to 2.2
On Mon, 10 Sep 2018, at 11:33, Miroslav Lachman wrote:
> Hi,
>
> are there any plans to create port for CouchDB 2.2?
> According to latest vulnerability in 1.7.2 and statement on upstream
> website http://docs.couchdb.org/en/stable/cve/2018-11769.html there are
> no plans to fix it in 1.7, because this version is no longer supported.
Correct; however:
1. the risk is low (rogue admin destroys the things they already have access to
via DB API)
2. update your /_config to exclude this in /usr/local/etc/couchdb/default.ini
*note NOTE local.ini
[httpd_global_handlers]
;_config = {couch_httpd_misc_handlers, handle_config_req}
> I am not able to create / maintain CouchDB 2.2 port by myself but I
> really would like to have not vulnerable version on our server.
I'm focused on getting a thing ready for eurobsdcon and ports stuff has had to
take a back seat for a couple of weeks, but it's so close now. The phab review
patch is already 100% functional https://reviews.freebsd.org/D16819 what
remains is polishing up the port esp round how it handles docs. Feedback is
welcome of course. You can build / install it and send some feedback in.
I'm interested to know how you're using CouchDB on FreeBSD (yay) email me
sometime about it!
A+
Dave
___
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"
kmod driver incompatibilities with 11.1R created packages used on 11.2R
We've probably all seen the problems that non-developer users have run into with the various packages that have a dependency on kernel versions, when using the official pkg.freebsd.org built versions. We know that the problem will go away as soon as 11.1R is EOL end September, but in the interim I can imagine this must be really frustrating for people who don't have a familiarity with building from sources. Is there anything we can do to help them? they're often newcomers to FreeBSD so their new user experience is crap. Here's a few ideas, but there may be better ones: - put a note in pkg-message informing users of the issue and a link to a forums.freebsd.org post on how to build it manually - add something to the port's pkg-install script to only display that message on < 11.2R kernels - provide an alternative pkg repo so they don't have to build from source (possibly community supported) I'm specifically thinking of x11/nvidia-driver here but there are presumably other packages impacted from https://www.freshports.org/kld/ https://www.freebsd.org/security/security.html#sup A+ Dave ___ 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: Of Git and M$
On Fri, 15 Jun 2018, Michael Gmelin wrote: github != git I didn't say that it was; did you misunderstand my message or something? -- Dave ___ 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"
Of Git and M$
A related discussion reminded me of this: how would Microsoft's purchase of GitHub affect future development? After all, they'll get to call the shots...[*] The only good thing that came out of M$ is their RTF document format (used natively by the Mac's TextEdit utility, for example), which being plain ASCII can be edited directly if necessary (and I have). I've been looking at BitKeeper, for example, the author of which (Larry McEvoy) I happen to know from another mailing list. Apparently, converting from Git is as simple as: "git fast-export | bk fast-import". And no, before some here accuse me of being a shill for BK, I have nothing to do with the product whatsoever, other than as someone looking for an alternative to something now owned by M$ (and I've used just about everything since SCCS). [*] Remember their motto: "Embrace, extend, extinguish". -- Dave, who has been called paranoid before ___ 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: Practice of "Sponsored by" in commit messages
On Mon, 14 May 2018, Maxim Sobolev wrote: It is like someone trying to moderate what people in general or some group in particular (e.g. freebsd committers) are allowed to put on their t-shirts just because you find it offensive or inappropriate. Now, where did I put that link to the "t-shirt incident"? :-) -- Dave ___ 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 and Packages
On Fri, 20 Apr 2018, Jos Chrispijn wrote: Due to a mistake (...) I now got a mix of ports and packages on my BSD system. What mistake? Can someone advise how to savely switch to packages only on this live system? Why? I run both ports and packages (the latter when I discovered that Ruby blew away my swap/tmp) with no problems. I prefer to use ports because that way I get to specify the options that I want (as opposed to generic ones which may not apply to me), but I'll use the package when someone assumes that I have both terabytes and gigahertz to burn... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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 old files in freebsd-update/files
FreeBSD 10.4-RELEASE-p3 (GENERIC) #0: Tue Nov 14 09:06:09 UTC 2017 I wrote about this before, and was told to use "pkg clean" to clean up old files which I now do every week, but... aneurin# pwd /usr/local/freebsd-update/files aneurin# ls | wc -l 49445 aneurin# du -sk . 1616854 . aneurin# ls -lt | tail -rw-r--r-- 1 root wheel602524 Nov 8 2014 1989e6faab36e0ccc9324af44fb6928586772fc40318324fb6f0159ce07db83f.gz -rw-r--r-- 1 root wheel597128 Nov 8 2014 614014e1e1d4911440c94f7f9144821652109b8409173de30a0104de43994c37.gz -rw-r--r-- 1 root wheel316738 Nov 8 2014 791153db5706bc7c90feb891b6396a284cfd466478ae99ae37865598e810c946.gz -rw-r--r-- 1 root wheel 2071102 Nov 8 2014 47110fb62b51ef4c7ae1d8a4c8fc1b4b96d7aabc8581a4069d95dd7b23183f62.gz -rw-r--r-- 1 root wheel586770 Nov 8 2014 f9e0c754890cea69f72d27a3a60fd3d6e13f3332de23a1ecf36b51633a6df089.gz -rw-r--r-- 1 root wheel 18427 Nov 8 2014 b77d9d3a7e25dbff03c03e7bdec9439df52944c3ad798eda3b0d52f8d4fb2d1e.gz -rw-r--r-- 1 root wheel 4680559 Nov 8 2014 beed4d84d6da3bc99f097a36095ea273fa5e1d72fb44554ca3aac1aee7b77958.gz -rw-r--r-- 1 root wheel 15731339 Nov 8 2014 3fcea2e78cbe67c42c2e74464d71a72ced6627871102e9b18d4f88cd0f0a4744.gz -rw-r--r-- 1 root wheel 24945 Nov 8 2014 3cdd4a6ea017cdfdc37283c69a265ff89be327addbf0fef7c793b6e275e34c60.gz -rw-r--r-- 1 root wheel 20862 Nov 8 2014 1b1e8f42628bcadd6b9a073012d798b0a4809bf72c1bf7cebefae7de5af7.gz Bit old, aren't they? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: MESON_ARGS
On Tue, 20 Feb 2018, Walter Schwarzenfeld wrote: There were whitespaces in the Makfile, seems caused this. This dates from PWB/UNIX i.e. about 40 years ago; I wonder if it will ever be fixed? White space is white space, FFS... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: apache24 and pkg check --recompute
On Wed, 14 Feb 2018, Rafal Lukawiecki wrote: apache24-2.4.29: missing file /usr/local/www/apache24/cgi-bin/printenv apache24-2.4.29: missing file /usr/local/www/apache24/cgi-bin/test-cgi apache24-2.4.29: missing file /usr/local/www/apache24/error/HTTP_BAD_GATEWAY.html.var Was there some reason to remove those files? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: ClusterSSH runtime errors
On Thursday 01 February 2018 00:01:06 Borge Brunes wrote: > Hi, > > Did you fint at solution for this? I'm having the same issue. > > uname -a > FreeBSD kahuka 11.1-RELEASE FreeBSD 11.1-RELEASE #0: Thu Aug 3 08:40:15 > CEST 2017 CUT:/usr/src/obj/usr/src/sys/GENERIC amd64 > > regards, Yes and no :-) I upgraded from 10.3 to 10.4 and upgraded all installed packages and the problem went away. Best guess, since you are on 11, is a mismatch in some installed port version which was "fixed" when I upgraded everything. Maybe you could try a pkg upgrade -f or may be just do pkg upgrade -f clusterssh (although I think I tried this one in the past and it didn't work, maybe it's a dependency of a dependency not picked up with the latter command) ___ 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 Palemoon branding violation
On Wed, 7 Feb 2018 20:18:48 -0600 Jake Roberts wrote: > Does Pale Moon do anything that something like Otter doesn't? I have never used Pale Moon. I just saw a comment and am truly curious as to where it's coming from. :) Perhaps at this point, to balance the sentiment against pale moon, someone knowledgeable about it should engage in some advocacy as to why Pale Moon is something to use? -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< It is no accident that those cultures which most strongly and often affirm the value and individuality of people are the ones which do the most towards automatizing people. ___ 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 Palemoon branding violation
On Thu, 8 Feb 2018 02:42:12 +0300 Rozhuk Ivan wrote: > Such a reaction is not appropriate for educated people. Are you actually implying that modern education somehow teaches emotional stability? -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< Politeness and telling the truth are, to your certain knowledge and mine, often opposites. Any society which enjoins its members to adhere to both of these is a fraud. All sorts of compromise formula have been devised to gloss over or obscure this basic weakness. It remains nonetheless. This is not an exhortation to abandon politeness or telling the truth. It is a statement which has to be carefully thought about. ___ 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 Palemoon branding violation
On Thu, 8 Feb 2018, Michelle Sullivan wrote: The reaction to the repo in question is also very weird to me, and possibly what worries me the most. He is hurting his own trademarked (heh) product by doing this. Quite the opposite. He has done the right thing to protect his trademark. There's a difference between gently pointing out to a volunteer that they are not complying with the terms of the licence and could they please fix it, and being an arrogant prick with said volunteer and acting like a scum-sucking bottom-feeding lawyer (as if there's any other sort). Oddly enough, I find that I get better results from volunteers when I ask them to do something, instead of ordering them around like an arse-hat boss. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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 Palemoon branding violation
On Tue, 6 Feb 2018, Dan Mahoney (Gushi) wrote: My $dayjob is with a company that makes open-source software which we redistribute under the MPL. I've shared that link with our team as an example of the absolute wrong way to go about engaging with the community. Back when I was active in Toastmasters (that's the "DTM" in my signature) and training people, I found that having examples of what *not* to do were more effective; people tended to remember them e.g. "The Radio Ham" is essential viewing for anyone who is involved in emergency communications (that's the "VK2KFU" in my signature). -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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 Palemoon branding violation
On Tue, 6 Feb 2018, Mark Felder wrote: Would you like us to delete our port of it now? I can arrange for that if you insist on not having proper ports of your software. At this point it might be easier to just add a clause to your license that prohibits non-Linux platforms. You're a lot politer than I would've been; then again, being an Aussie I tend to be an outspoken bastard, and I would've told him to perform an anatomically-impossible act. "You will" indeed... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Mailman has mismatched checksums
On Tue, 16 Jan 2018, Ted Hatfield wrote: My best guess is that some time in the past I changed the variables DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in the Defaults.py file rather than mm_cfg.py, and the files Defaults.py and Defaults.pyc didn't change when I did a pkg update. After further investigation (a complete removal of Mailman, updated the "locate" database, and confirmed that not a skerrick of Mailman was left on the server), I did another installation of the package (not the port), and stood back and waited for the overnight check. And... Checking for packages with mismatched checksums: mailman-2.1.25: /usr/local/mailman/Mailman/Defaults.py mailman-2.1.25: /usr/local/mailman/Mailman/Defaults.pyc Suspicious (since *I* hadn't touched anything), I looked further, and found: DEFAULT_EMAIL_HOST = 'aneurin.horsfall.org' DEFAULT_URL_HOST = 'aneurin.horsfall.org' DEFAULT_URL_PATTERN = 'http://%s/mailman/' In other words, the installation gratuitously changes a file that by its own admission should not be changed, and then the system has the hide to complain that it has been changed i.e. it installs itself as pre-corrupted... I'm surprised that this breakage hasn't been noted until now. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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"
Mailman has mismatched checksums
When trying to get Mailman going (and seeing what looked like several updates in quick succession), I completely cleaned it out, waited a bit for any more updates, installed the package, waited a bit for any more updates, and I was hoping that this would go away: Checking for packages with mismatched checksums: mailman-2.1.25: /usr/local/mailman/Mailman/Defaults.py mailman-2.1.25: /usr/local/mailman/Mailman/Defaults.pyc No configuration whatsoever was done; I merely installed the package and waited for any more updates to arrive. So, what can I do about it? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: All those notes...
Thanks, all; I've made a note to myself on my Mac's calendar to use script/tee (something I always think of *after* the event, and on the Mac as well). Some random observations: Why would /usr/local/etc/apache24/httpd.conf need to be removed if not needed? Surely as I've just upgraded it, I might want it? Simh renaming some commands: I had to really laugh about this one, as I raised the very same issue in "Bug 218436 - emulators/simh pollutes the namespace" and some clown rejected it with a rather snotty response. Well, it's even worse now! So "nova" becomes "simh-nova" but "vax" doesn't become "simh-vax" etc. What a shambles... Now to pay vewwy vewwy close attention to the Mailman notes, as I've just installed it for the first time and it ain't working... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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"
All those notes...
I'm not quite sure what happened since my last weekly "pkg update" etc but it sure got busy: Checking for upgrades (198 candidates): 100% Processing candidates (198 candidates): 100% The following 110 package(s) will be affected (of 0 checked): New packages to be INSTALLED: ruby24-bdb: 0.6.6_5 icu: 60.2_1,1 py27-ply: 3.10_1 Installed packages to be UPGRADED: zsh: 5.4.2 -> 5.4.2_1 tevent: 0.9.31 -> 0.9.34_1 tdb: 1.3.12,1 -> 1.3.15_1,1 talloc: 2.1.9 -> 2.1.10_1 [...] Etc (over a hundred of 'em). This was accompanied by zillions of notes, warning me to "do this" and "avoid doing that" etc. Err, were those notes squirreled away somewhere, or do I have to hope that I don't lose the window and its scrollback buffer? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: I've started getting ^@^@> in my xterms w/mutt
On Wed, 3 Jan 2018, Kurt Jaeger wrote: I had the same problem. Since then I use the SLANG option instead of NCURSES to build mutt. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208659 Hmmm... I wonder if that's related to something I found in Alpine 2.21? After upgrading from 2.20, I found that UTF-8 characters were displaying as "??" despite having "display-character-set=UTF-8" set. I asked the maintainer on record some months ago, with no response. I fixed it by adding "LANG=en_US.UTF-8" to the environment. Funny; it worked all the way up to 2.20 without it... Oh, and still no response from "mb...@xs4all.nl"; is he/she/it still alive? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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"
ClusterSSH runtime errors
ClusterSSH is continuously generating the following while running.
On at least one occasion I cam back to find all the client xterms
closed. Maybe the error counter overflowed and crashed it?
Tk::Error: Can't use an undefined value as a symbol reference at
/usr/local/lib/perl5/site_perl/App/ClusterSSH.pm line 1457.
Tk::After::repeat at /usr/local/lib/perl5/site_perl/mach/5.24/Tk/After.pm line
80
[repeat,[{},after#23481,500,repeat,[\&App::ClusterSSH::__ANON__]]]
("after" script)
XS_Tk__Callback_Call error:Can't use an undefined value as a symbol reference
at /usr/local/lib/perl5/site_perl/App/ClusterSSH.pm line 1457.
uname -a
FreeBSD laptop 10.3-RELEASE-p24 FreeBSD 10.3-RELEASE-p24 #0: Wed Nov 15
04:57:40 UTC 2017
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
pkgs/ports up to date as of about an hour ago.
___
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: Of LSOF
On Wed, 27 Dec 2017, Kevin Oberman wrote: fstat(1) does much of what lsof does. I'll be damned; so it does... Thanks! -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Of LSOF
On Tue, 26 Dec 2017, Kevin Oberman wrote: [...] Putting header files into the port is a non-starter as they MUST match the kernel on which lsof is built. I added lsof to PORTS_MODULES so it is rebuilt with any new kernel on my stable system and on one release system so I can use that package to install elsewhere rather then use the repo package. Good point; thanks. "lsof" is a superb tool, BTW... Now that 10.3 is EOL I would expect that the package built for 10-STABLE would be built on 10.4-RELEASE, but I don't know for sure. It should be and the next quarterly should be 10.4 based, too. OK. The history is that I used to build from ports because the then-boss did, and I didn't even know about pre-built packages. Then, one day, Ruby needed to be rebuilt, which promptly blew away /tmp i.e. swap... I'm a big fan of TMPFS; I had it on the old BSDi box (where it was "mfs"), and even my old CP/M box (where it was "M:"). -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Of LSOF
On Wed, 27 Dec 2017, Dimitry Andric wrote: Binary packages are built on the oldest supported 10.x release, which currently is 10.3. I think that lsof is just one of the few programs that care about this, and show a warning. This is probably because lsof pokes around in half-documented (or undocumented) system structures, which might change even in minor releases. Thanks for that. The path of lowest resistance is to ignore the warning, otherwise build (or package) the port yourself. Which I discovered last year required that kernel sources be installed (which I didn't have at the time; I didn't build this system) because it wanted a certain #include file. I reported this in a PR saying that perhaps all header files be shipped, but I dunno what happened. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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"
Of LSOF
aneurin# freebsd-version 10.4-RELEASE-p5 aneurin# which lsof /usr/local/sbin/lsof aneurin# lsof > /dev/null lsof: WARNING: compiled for FreeBSD release 10.3-RELEASE-p22; this is 10.4-RELEASE-p3. aneurin# pkg upgrade lsof Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) Your packages are up to date. aneurin# Building it from ports updated it (as I probably did before), but should not the binary have been updated? Or are binaries not available for all ports (I guess)? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Procmail got updated!
I'm beginning to regret starting this thread; then again, I do come from a long line of stirrers (to which some bods on this list will attest)... And yes, I'm still annoyed that "jive"[*] got deleted for no technical reason whatsoever; then again, I'm still bemused by Americans taking a leak in the bath or the bed, or is it having a bath in the toilet? I can never remember. [*] I was working at NECISA for a bit (PeterJ may remember it) when me being me, I inserted "valspeak" into the "man" script. Well, how was I to know that $BOSS, when he came in late the next morning, had been on the turps all night? Call it a wild guess on his part, but he somehow knew that I was the perp... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Procmail got updated!
On Wed, 20 Dec 2017, Adam Weinberger wrote: I'm a little unsettled by this discussion, because it is moving into territory with which we have very little precedent. And the precedent that it would establish is not wholly within our mandate. Am I the only one who remembers the kerfuffle over "jive" being de-ported (to coin a phrase)? No technical reason whatsoever, but apparently it upset someone's delicate sensibilities, so there's sort of a precedent. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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"
Procmail got updated!
Doing my regular update, and... Upgrading procmail from 3.22_9 to 3.22_10... Good grief; who's the masochist who volunteered to support this obscure insecure and hitherto-unsupported scripting language? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Procmail Vulnerabilities check
On Mon, 11 Dec 2017, Chris H wrote: pf(4) has dropped any/all communication from the showdan "project" *long* ago for all the systems I'm responsible for, and along with all the myriad of other "like" projects. They all have the policy backward; ask *before* not *after*. I'd love to do that; what's the IP range of their scanners (I assume that they have more than one)? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Procmail Vulnerabilities check
On Sun, 10 Dec 2017, Adam Weinberger wrote: DMA is a phenomenal program and is totally sufficient for a large percentage of our user-base. I wasn’t aware of the lack of .forward support, and I completely agree that that’s a very detrimental omission. What about its spam filtering, such as /etc/mail/access and DNSBLs etc? (I hope it's a coincidence that its name is also the same as the pro-spam Direct Marketing Association...) -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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@ list is now subscriber-post only
rom owner-freebsd-po...@freebsd.org Wed Oct 18 05:04:14 2017 From owner-freebsd-po...@freebsd.org Thu Oct 19 01:28:28 2017 From owner-freebsd-po...@freebsd.org Thu Oct 19 03:31:58 2017 From owner-freebsd-po...@freebsd.org Sat Oct 21 02:05:34 2017 From owner-freebsd-po...@freebsd.org Mon Oct 23 19:17:42 2017 From owner-freebsd-po...@freebsd.org Mon Oct 23 19:18:00 2017 From owner-freebsd-po...@freebsd.org Thu Oct 26 18:41:30 2017 From owner-freebsd-po...@freebsd.org Thu Oct 26 22:32:06 2017 From owner-freebsd-po...@freebsd.org Fri Oct 27 03:27:41 2017 From owner-freebsd-po...@freebsd.org Thu Nov 2 00:37:07 2017 From owner-freebsd-po...@freebsd.org Thu Nov 2 00:46:35 2017 From owner-freebsd-po...@freebsd.org Thu Nov 2 08:43:56 2017 From owner-freebsd-po...@freebsd.org Thu Nov 2 20:56:36 2017 From owner-freebsd-po...@freebsd.org Sat Nov 4 11:13:56 2017 From owner-freebsd-po...@freebsd.org Thu Nov 9 18:41:15 2017 From owner-freebsd-po...@freebsd.org Fri Nov 10 01:35:23 2017 From owner-freebsd-po...@freebsd.org Mon Nov 13 12:06:54 2017 From owner-freebsd-po...@freebsd.org Mon Nov 13 12:09:02 2017 From owner-freebsd-po...@freebsd.org Tue Nov 14 04:07:59 2017 From owner-freebsd-po...@freebsd.org Tue Nov 21 03:33:38 2017 From owner-freebsd-po...@freebsd.org Thu Nov 30 02:46:50 2017 From owner-freebsd-po...@freebsd.org Thu Nov 30 16:25:12 2017 And that was only from when I started saving them; I just *love* demolishing specious arguments such as the above. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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@ list is now subscriber-post only
On Sat, 9 Dec 2017, Adam Weinberger wrote: * This should cut back tremendously on spam coming through the list. Many many thanks! Now if I can just get some other lists I'm on to see the light of day (Debian, I'm looking at you)... Half-seriously, I'll probably stick with FreeBSD after all now (yes, that would've been a major factor in my decision to flee elsewhere). -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Procmail Vulnerabilities check
On Fri, 8 Dec 2017, Steve Kargl wrote: https://lists.freebsd.org/pipermail/freebsd-arch/2017-December/018712.html Well, I saw no reason to subscribe to freebsd-arch (I'm on enough lists as it is)... Are there any other lists that we should be following? I guess a suit and tie will be required soon :-( I'm bemused by Bapt's remark that "it does not support anything an entreprised [sic] grade mta setup would require: ldap support for example"; funny, as I had it working just fine with OpenLDAP with hundreds of users spread over many offices in my last job, with no trouble at all; there's even a schema for it, FFS: aneurin% locate -i sendmail.schema /usr/share/sendmail/cf/sendmail.schema with all the right gear in it: # OID arcs for Sendmail # enterprise: 1.3.6.1.4.1 # sendmail: enterprise.6152 WTF? Sure as hell looks like Sendmail supports LDAP to me... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Procmail Vulnerabilities check
On Sat, 9 Dec 2017, Kurt Jaeger wrote: [ On removing Sendmail from FreeBSD ] If sendmail is available via ports, wouldn't that be enough ? It better be in ports (but don't look at me; I have my hands full with my Mac & iPad with possibly an iPhone and an Android thrown in, and two Penguins); I've spent about 30 years with Sendmail and I ain't changing (I looked at Postfix but didn't like it)... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Procmail Vulnerabilities check
On Fri, 8 Dec 2017, Steve Kargl wrote: First, there is movement afoot to remove sendmail from FreeBSD and replace it with dma(1). There is? Is there anything else that they're going to spring on us? (I'm still annoyed that they removed "jive" because it upset someone's delicate sensibilities.) -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Flavors *COMPLETELY* break the port system (synth and poudriere are useless)
On Thu, 7 Dec 2017, Jan Bramkamp wrote: [ Cogent explanation deleted ] Thanks for that clear explanation; I've been promised a much bigger server in return for some contract work, so I'll start planning for it. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: THANK YOU for flavors! (fwd)
Errkk... This was meant for the list. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." -- Forwarded message -- Date: Thu, 7 Dec 2017 11:01:51 +1100 (EST) From: Dave Horsfall To: Mel Pilgrim Subject: Re: THANK YOU for flavors! Serious question: is "FLAVOUR" accepted as an alias, or does the rest of the world have to put up with American spelling? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Flavors *COMPLETELY* break the port system (synth and poudriere are useless)
On Wed, 6 Dec 2017, Jan Bramkamp wrote: Synth and poudriere are parallel build tools and as such are very taxing on the system. I suspect your system is unstable under such load, because of a configuration error or unreliable hardware. One such configuration error that bit me is tmpfs mounted without size limitation. Without size limits it can exhaust RAM + swap and crash the system. Limit the sum of all your tmpfs mounts to significantly less than RAM + swap. What happens then? Does the build process merely crash instead? I ask because my minimal system (all I can afford on my "income") has 512MB memory (all it will take) ad 1GB swap; building Ruby etc kills it, so I use packages in that case i.e. no customisation if I wanted it. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: (upgrading a port)
On Sat, 25 Nov 2017, Johan Hendriks wrote: How do u upgrade a port? A installed port can be updated with portmaster or portupgrade, or you can create packages with synth or poudriere and install those. First update the ports tree. [...] Thanks for a concise summary of the port upgrade process; I've been looking for one for quite a while... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Does /var/cache/pkg ever get cleaned out?
On Tue, 21 Nov 2017, Eugene Grosbein wrote: Shouldn't one of the divers package tools be cleaning them out, or is that a separate task? man pkg-clean Thanks; that's over a half-gigabyte recovered on a 1GB /var... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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"
Does /var/cache/pkg ever get cleaned out?
I've got files going back as far as 2014 (and so help me, one that claims to be 1974): -rw-r--r-- 1 root wheel 2119648 Nov 7 2014 awstats-7.3,1-c836dfdf16.txz -rw-r--r-- 1 root wheel 94028 Nov 7 2014 portupgrade-2.4.13_1,2-1e91f12d05.txz [...] -rw-r--r-- 1 root wheel 2492468 Oct 24 2014 openssl-1.0.1_16-79d63feebc.txz -rw-r--r-- 1 root wheel753604 Oct 24 2014 sudo-1.8.11.p1-5a500fa78b.txz [...] -rw-r--r-- 1 root wheel 2568456 Apr 21 1974 pkg-1.9.4_1-1cee9ebad1.txz Shouldn't one of the divers package tools be cleaning them out, or is that a separate task? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Firefox became much slower
On Wed, 8 Nov 2017, Dave Horsfall wrote:
It got really bad around 53 or so; I wish their programmers (no doubt
fresh out of school) would fix existent bugs instead of adding frilly
new "features"' we don't all have terabytes of free memory.
Hmmm... Firefox 57.0 ("Quantum") seems to have fixed these deficiencies,
so I guess they've found real programmers (tm) after all. The eye-candy
has changed of course, but I can live with that.
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
___
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.d script ordering for net/zerotier & firewalls
zerotier is a peer-to-peer layer 2 overlay network that creates a tap interface for its traffic. In the current net/zerotier port[1], if you want to define firewall rules (e.g. pf) that rely on the existence of the zerotier interface, it will fail on reboot as the rc.d dependencies aren't sufficient: # PROVIDE: zerotier # REQUIRE: LOGIN # KEYWORD: shutdown This variant seems to "work on my machine" to manage the dependencies appropriately, see rcorder(8) output below. # PROVIDE: zerotier # REQUIRE: FILESYSTEMS netif # BEFORE: pf ipfw # KEYWORD: shutdown the intention is that the ordering would be as follows: 1. physical network interfaces are available 2. zerotier's tap interfaces are created via its daemon 3. then firewalls can be started up 4. jails and daemons (nginx, haproxy etc) can be assigned a zerotier address Is there a better way of handling this? Is there a reason why /pf/ is missing from /etc/rc.d/NETWORKING ? # PROVIDE: NETWORKING NETWORK # REQUIRE: netif netwait netoptions routing ppp ipfw stf # REQUIRE: defaultroute route6d resolv bridge # REQUIRE: static_arp static_ndp > rcorder /usr/local/etc/rc.d/* /etc/rc.d/* ... /etc/rc.d/hostname /etc/rc.d/ip6addrctl /etc/rc.d/netoptions /etc/rc.d/random /etc/rc.d/sppp /etc/rc.d/ipfilter /etc/rc.d/ipnat /etc/rc.d/ipfs /etc/rc.d/serial /etc/rc.d/iovctl /etc/rc.d/netif /etc/rc.d/devd /etc/rc.d/zfsd /etc/rc.d/ipsec /usr/local/etc/rc.d/zerotier /etc/rc.d/pfsync /etc/rc.d/pflog /etc/rc.d/pf /etc/rc.d/stf /etc/rc.d/ppp /etc/rc.d/routing /etc/rc.d/ipfw /etc/rc.d/netwait /etc/rc.d/resolv /etc/rc.d/local_unbound /etc/rc.d/nsswitch /etc/rc.d/routed /etc/rc.d/rtsold /etc/rc.d/static_ndp /etc/rc.d/static_arp /etc/rc.d/bridge /etc/rc.d/route6d /etc/rc.d/defaultroute /etc/rc.d/NETWORKING ... A+ Dave [1]: https://svnweb.freebsd.org/ports/head/net/zerotier/files/zerotier.in?revision=398568&view=markup ___ 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: Firefox became much slower
On Tue, 7 Nov 2017, Chris H wrote: FWIW Firefox has always leaked memory like water through a sieve. As a result, no matter how many resources I have on any given system. I can't leave FF open for any length of time, w/o having to restart it; else system starts swapping until all resources are exhausted; then panic && reboot. It got really bad around 53 or so; I wish their programmers (no doubt fresh out of school) would fix existent bugs instead of adding frilly new "features"' we don't all have terabytes of free memory. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Committer wanted: www/webhook
On Sun, 5 Nov 2017, at 13:36, Stefan Bethke wrote: > Hey, > > I would be grateful if some committer could take a look at > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222883 > > > Thanks, > Stefan Servus Stefan! Happy to take care of it, as I'm still under mentorship it might take a tad longer to file off any rough edges. A+ Dave ___ 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: SF mastersites
On Sat, 28 Oct 2017, Mark Millard wrote:
${NAME:tl} is Makefile notation even in Makefiles having nothing to do
with ports (or potentially even FreeBSD). There probably is lots of
involved Makefile notation not separately documented in
makefile-distfiles.html or other parts of porters-handbook/ .
I've been using "make" since the PWB days, and this is news... The
trouble is, one would have to suspect that this is yet another variant
before looking for specific documentation (and I thought "gmake" was bad
enough).
At least my Makefiles and shell scripts will work anywhere; I don't make
use of local "features".
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
___
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"
Spam on -ports
Is it official FreeBSD policy to allow spammers free reign on this list, or is the list owner merely incompetent? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: portmaster, portupgrade, etc
On Thu, 5 Oct 2017, Chris H wrote: I'll second that.-- George (old fart w/50 years software experience) WooHoo! another greybeard! I'm at ~50yrs myself! Only 47 years exp here (the last 42 with Unix). -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: Status of portupgrade and portmaster?
> What is the current status of portupgrade and portmaster? > > I haven't used portupgrade in some time, but what about portmaster? > > What is one officially supposed to use to build and upgrade packages from > source? In the interests of having some numbers other than email list replies I threw up a straw poll: https://forums.freebsd.org/threads/62633/ pick your poison and I'll report back in a week. RT/posts welcomed to spread the word. A+ Dave ___ 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"
GVFS build fail
Getting a build fail with GVFS from ports. Tried rebuilding everything list in make build-depends portupgrade -cf libxslt py27-lxml p5-Locale-libintl intltool msgfmt docbook-xsl Tried rebuilding libxml and related ports portupgrade -cf libxml++ libxml2 p5-XML-LibXML py27-libxml2 py27-lxml %uname -a FreeBSD amd.asgard.uk 10.3-RELEASE-p20 FreeBSD 10.3-RELEASE-p20 #0: Wed Jul 12 03:13:07 UTC 2017 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 I'm guessing that the lack of others reporting this points to something I need ti update/rebuild, or as left over config/library file somewhere Any suggestions? Making all in man gmake[4]: Entering directory '/usr/ports/devel/gvfs/work/gvfs-1.26.3/man' /usr/local/bin/xsltproc --nonet --stringparam man.output.quietly 1 --stringparam funcsynopsis.style ansi --stringparam man.th.extra1.suppress 1 --stringparam man.authors.section.enabled 0 --stringparam man.copyright.section.enabled 0 http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl gvfs-cat.xml /usr/local/bin/xsltproc --nonet --stringparam man.output.quietly 1 --stringparam funcsynopsis.style ansi --stringparam man.th.extra1.suppress 1 --stringparam man.authors.section.enabled 0 --stringparam man.copyright.section.enabled 0 http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl gvfs-copy.xml /usr/local/bin/xsltproc --nonet --stringparam man.output.quietly 1 --stringparam funcsynopsis.style ansi --stringparam man.th.extra1.suppress 1 --stringparam man.authors.section.enabled 0 --stringparam man.copyright.section.enabled 0 http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl gvfs-info.xml /usr/local/bin/xsltproc --nonet --stringparam man.output.quietly 1 --stringparam funcsynopsis.style ansi --stringparam man.th.extra1.suppress 1 --stringparam man.authors.section.enabled 0 --stringparam man.copyright.section.enabled 0 http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl gvfs-ls.xml /usr/local/bin/xsltproc --nonet --stringparam man.output.quietly 1 --stringparam funcsynopsis.style ansi --stringparam man.th.extra1.suppress 1 --stringparam man.authors.section.enabled 0 --stringparam man.copyright.section.enabled 0 http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl gvfs-less.xml /usr/local/bin/xsltproc --nonet --stringparam man.output.quietly 1 --stringparam funcsynopsis.style ansi --stringparam man.th.extra1.suppress 1 --stringparam man.authors.section.enabled 0 --stringparam man.copyright.section.enabled 0 http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl gvfs-mime.xml file:///usr/local/share/xml/catalog.ports:1: parser file:///usr/local/share/xml/catalog.ports:1: error : Document is empty ^ I/O parser error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl"; cannot parse http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl error : Document is empty gmake[4]: *** [Makefile:708: gvfs-cat.1] Error 4 file:///usr/local/share/xml/catalog.ports:1: parser error : Document is empty ^ gmake[4]: *** Waiting for unfinished jobs I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl"; cannot parse http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl file:///usr/local/share/xml/catalog.ports:1: ^ I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl"; cannot parse http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl parser file:///usr/local/share/xml/catalog.ports:1: parser error : Document is empty ^ error : Document is empty ^ gmake[4]: *** [Makefile:708: gvfs-mime.1] Error 4 I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl"; cannot parse http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl"; cannot parse http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl gmake[4]: *** [Makefile:708: gvfs-info.1] Error 4 gmake[4]: *** [Makefile:708: gvfs-ls.1] Error 4 gmake[4]: *** [Makefile:708: gvfs-copy.1] Error 4 file:///usr/local/share/xm
Re: Repository statistics
On Tue, 1 Aug 2017, Miroslav Lachman wrote: There is some interesting project - repository statistics - comparison with many different OS package repositories like Ubuntu, Fedora, Debian etc. Good stuff! I never liked Penguin/OS anyway. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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"
Monday Pick (fwd)
When is the cocksucker who runs this this list going to implement some simple anti-spam provisions? Or are you one of those idiotic "frea speach" spam supporters, so prevalent amongst Americans these days? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." -- Forwarded message -- Return-Path: Received: from mx2.freebsd.org (mx2.freebsd.org [8.8.178.116]) by aneurin.horsfall.org (8.15.2/8.15.2) with ESMTP id v6VEqdIT047270 for ; Tue, 1 Aug 2017 00:52:53 +1000 (EST) (envelope-from owner-freebsd-po...@freebsd.org) Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx2.freebsd.org (Postfix) with ESMTPS id 1D0417BE1A; Mon, 31 Jul 2017 14:52:37 + (UTC) (envelope-from owner-freebsd-po...@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D6CCB7DA55; Mon, 31 Jul 2017 14:52:36 + (UTC) (envelope-from owner-freebsd-po...@freebsd.org) Delivered-To: freebsd-po...@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48AA9DAFA74 for ; Mon, 31 Jul 2017 14:52:33 + (UTC) (envelope-from 0100015d991cd2d1-50f2e2be-fac5-4d7b-a235-e1f515e86deb-000...@amazonses.com) Received: from a8-78.smtp-out.amazonses.com (a8-78.smtp-out.amazonses.com [54.240.8.78]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 096017DA4F for ; Mon, 31 Jul 2017 14:52:32 + (UTC) (envelope-from 0100015d991cd2d1-50f2e2be-fac5-4d7b-a235-e1f515e86deb-000...@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=h2t7bxqbsvj67klqsmladohnc6xaimr7; d=pennyinvesting.ltd; t=1501512389; h=Date:From:Reply-To:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Tr ansfer-Encoding:List-Unsubscribe; bh=E3Ex1n5L30tu/MHQvqlhdnXmR2N1ukz7e10ZmwnARUM=; b=LK5kWoth7KiHyUQB36VVhf4qlaqgm4EzlNL1dpkL8dSycGtweq1HC0UR1Hh8H63Q wHesZlxV72iAXi+yt+s6uJ50tIxV7eozc+oIcKhBWTwaZAP2B6CJwun+V+PFd1AEFH0 Y/4Wqai9X7TT7F9uljSwXUYAHSgFQCGbLagX8ErM= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1501512389; h=Date:From:Reply-To:To:Message-ID:Subject:Mime-Version:Content-Type:Content-Tr ansfer-Encoding:List-Unsubscribe:Feedback-ID; bh=E3Ex1n5L30tu/MHQvqlhdnXmR2N1ukz7e10ZmwnARUM=; b=J6fkRVamgpVA0mVV96SV0hl4mH5zsaqqg5T/13/3wrx8yHCDndbT+HZxbJ1bEdDc nhNKujrDQmcH5pfe+kXjWl26jSmu850vzZxQrfbfm21qpiKJBHRKblH95UMPbySoU+7 XzbdrOy1feRWGc6G9pEYywHMNzRZZvZeNubxzBVQ= Date: Mon, 31 Jul 2017 14:46:29 + From: PennyInvesting Ltd To: freebsd-ports@freebsd.org Message-ID: <0100015d991cd2d1-50f2e2be-fac5-4d7b-a235-e1f515e86deb-00@email.amazonse s.com> Subject: Monday Pick Mime-Version: 1.0 X-SES-Outgoing: 2017.07.31-54.240.8.78 Feedback-ID: 1.us-east-1.N+eH7c/JVHWqWoDvUh/hyI9vxLhu6cfaFz8vP7Fg5DE=:AmazonSES X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>, <mailto:freebsd-ports-requ...@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/> List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-requ...@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-requ...@freebsd.org?subject=subscribe> Reply-To: PennyInvesting Ltd Content-Type: text/plain; charset="utf-8" Errors-To: owner-freebsd-po...@freebsd.org Sender: owner-freebsd-po...@freebsd.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by aneurin.horsfall.org id v6VEqdIT047270 The most common question or request we get in our email mailbox is " How can i get the ticker before anybody else ?" , Before the rest of the stock alert subscribers ! I always give you a ticker before the rest of the world knows about it , but you guys still wait to jump on it. Isn't this the reason you subscribe in the first place ! so you can know which public company is gonna move up before it actually does. I alerted LKMNF this week . I said ( you guys can go read my previous emails) that they gonna start drilling and exploiting gold in beginning of august. I also said , a very reliable source informed us that there is big news alerts gonna b
Re: Alpine not displaying UTF-8
On Thu, 13 Jul 2017, Dave Horsfall wrote: I upgraded my Alpine to 2.21 (from 2.20) recently, now it is no longer displaying UTF-8 characters (yes, I have it set). Anyone else noticed this? I need to know whether it's a port bug or an upstream bug, so I know who to beat up. Replies, anyone? Or am I the only one seeing this, and if so, how could I have screwed up with a mere upgrade? As an example "e grave" (=C3=A8 in quoted printable) merely displays as "?" i.e. unknown. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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"
Alpine not displaying UTF-8
I upgraded my Alpine to 2.21 (from 2.20) recently, now it is no longer displaying UTF-8 characters (yes, I have it set). Anyone else noticed this? I need to know whether it's a port bug or an upstream bug, so I know who to beat up. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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 problem
On Tue, 20 Jun 2017, at 14:21, Jeffrey Bouquet via freebsd-ports wrote: > Attachment probably not sent to the list. > > CD /usr/ports/devel/p5-List-Regexp [new june 20 ] > make build > ... > Encode.c: loadable library and perl binaries are mismatched ( got > handshake key 0x8900080, needed > 0x7b00080 > *** Error code 1 > Stop. > make: stopped in /usr/ports/devel/p5-List-Regexp > > I've installed perl from v11 pkg because v12-CURRENT has not been > updated lately This is a very google-able error message. TLDR your perl bits need to be consistently compiled - you can't mix and match. When your perl version gets bumped you'll need to rebuild all your locally compiled packages, incl any local dependencies. The FreeBSD project 12.0-CURRENT binary packages are updated most weeks I think; what leads you to believe they are not? > and binaries fail with 'fstat' or 'stat' errors Is it possible that you have a 12.0-CURRENT from prior to the ino64 updates, and are trying to install binary packages from after that point in time? For most of the last year its been possible to get away with this, but not this time - a `uname -a` would probably confirm that. If that's the case, your 12.0-CURRENT needs to be CURRENT, so if you really need to, the 11.0 bits into an 11.0 jail and not on the host system. Background: https://lists.freebsd.org/pipermail/freebsd-current/2017-April/065687.html https://lists.freebsd.org/pipermail/freebsd-current/2017-May/066114.html https://svnweb.freebsd.org/base/head/UPDATING?view=markup&pathrev=318792#l54 Either way a bit more specific information (kernel version, your package repo, your ports tree svn revision) will help us narrow things down for you. I have tried mixing home-grown ports & FreeBSD packages . before; it always bit me in the end. If you have the build capacity, use poudriere and let it keep things consistent for you A+ Dave ___ 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: [RFC] Why FreeBSD ports should have branches by OS version
On 06/26/2017 00:27, Guido Falsi wrote: I only partly agree with what you say, but anyway insisting on the mailing lists with individual committers, and defending a general idea ignoring all the details, dismissing the actual problems in the detailed implementation that are raised by committers is not going to get much done. I agree that empirical evidence would suggest this to be true. It has also been suggested here to write a full blown, planned and though out proposal to be submitted via the new "FreeBSD Community Process" [1], which could be much more effective. Perhaps. I'm more of a 'get stuff done' kind of person than an RFC writer myself, but I'd like to see someone take a shot at it. I'd say the difficult part in such a problem is not in the idea but in the boring details of it's implementation and long term maintenance. Actually I see the difficult part as how to solve the conflicting needs of this community. There appear to be two ideas: bleeding edge ports and stable ports. These are somewhat mutually exclusive and exacerbated by the need for security patches for the latter. I "solve" this problem by using quarterlies and running builds often, but it's not necessarily the best way. I'd personally envision a "version" knob for ports, so you could explicitly specify the exact version of software you wanted to build; kind of like the options knobs are now. The work involved in making each value of that knob actually build is probably prohibitive, but it would allow various people to focus on the versions that matter to them. This would also limit discussions like these to specific support for specific ports, but those happen anyway so at least this particular discussion would become moot. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< A generous person may not have wisdom. Unlike others, this person has the means to gain wisdom. ___ 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: [RFC] Why FreeBSD ports should have branches by OS version
On 06/23/2017 01:53, Guido Falsi wrote: If your model works fine I'm quite sure the FreeBSD community and project will be quite happy to embrace it. ... > I cannot think of a better way to show there actually is no manpower problem than creating a working example of such a workflow maintained by just a few people with little effort, as you said repeatedly. ... On other hand demanding and/or insisting that others implement your idea when they clearly disagree with you is not very constructive. The fallacy in your suggestion to "do it yourself" is that the others who are actually working and committing on ports are far more efficient at implementing these ideas than the rest of us. I've never seen someone who says "do it yourself if you want it different" actually take into account that the expertise and experience of the people currently doing it result in a far lower manpower cost, sometimes by orders of magnitude. Thus, in some cases, people demand or insist because they want something they either cannot accomplish themselves, or cannot accomplish in the limited time they have. As far as I have observed, you can't even -pay- the ports experts to do something you might want. If you do not have this time or expertise, the only recourses left are: demand, insist, request, plead, or attempt to logically convince. As I see it, the emotions you see people expressing don't come as much from "not having their own way" as it does from being forced to adopt someone else's way. Looking at just that idea, the situation is not really that much different from using Microsoft and Apple; you take what they give you or go use something else. I think there's a general perception that open source is not supposed to be like that so much, but I think we all know differently here. To be absolutely clear, I'm not demanding or insisting on anything here out of ports maintainers or FreeBSD. I can and do support myself, when I am able. I'm merely pointing out ideas which may not be immediately visible to the people in this thread. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< In a dream, Nasrudin saw himself being counted out coins. When there were nine silver pieces in his hand, the invisible donor stopped giving them. Nasrudin shouted, "I must have ten!" so loudly that he woke himself up. Finding all the money gone he closed his eyes again and said. "All right, then, give them back. I'll take the nine." ___ 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: [RFC] Why FreeBSD ports should have branches by OS version
On 06/22/2017 11:43, demelier.da...@gmail.com wrote: Let me use my example of www/node back. I have built the port www/node in poudriere using this origin (so no version). At the time I've built it it was a 6.x version. When I upgraded my machine, www/node has switched to 7.x version and since this software follows semantic versioning, every application using the 6.x branch may or may not work anymore. I completely agree that an annoying consequence of what the volunteers are doing with the ports tree. These unwelcome surprises are the bulk of my non-automated work in creating package repositories. Frankly, I also wish this kind of thing would stop. Ultimately my wishes are irrelevant for reasons far far beyond the scope of this thread. Now, I'm in a state where if I pull the ports tree, I must check if www/node6 still exists or I must not upgrade. With releases branches I will be sure that: 1. www/node will *always* be at a 6.x version; 2. www/node will still be supported for the version of the FreeBSD system. That sounds reasonable...yet others will likely expect www/node to always be the latest version. Perhaps these others might complain that it is not the latest version and it would be reasonable to have node always be at the latest version. Would you agree that release branches would be unnecessary if somehow you could select the version of node that the ports tree builds via some (as yet unspecified) mechanism? -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< If you want to get rid of somebody, just tell them something for their own good. ___ 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: [RFC] Why FreeBSD ports should have branches by OS version
On 06/22/2017 09:16, scratch65...@att.net wrote: I can't help feeling that there's something very wrong when people for whom the system is a tool rather than a plaything have to work around the choices made by the "official" developers. I'd say this is true no matter what OS you use these days. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< It is only knowledge that will destroy bias. ___ 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: [RFC] Why FreeBSD ports should have branches by OS version
On 06/22/2017 08:53, Julian Elischer wrote: Yeah but the quarterly branches are relatively useless because they a not sync'd to anything and mean nothing special to anyone. They are not useless to me. I maintain a fair number of different package repositories for various purposes. Over a long period of time I've found that trying to build from HEAD is a random crapshoot as to whether everything you want will build without you having to svn random ports back and forth through the revision tree (or patch them yourself), patch your build processes, and/or ask for help (which you often might not get). In contrast, the quarterly branches (so far) have built everything I've wanted cleanly and this has been true for some years. No, the quarterlies are not perfect, but they seem to be closer to perfect than HEAD is. Note that you have to handle the edge cases (recent security patches, revision mismatch, etc) anyway, HEAD or no. I find I have to handle less with the quarterlies because they do generally build cleanly. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< Possession of a system of knowledge, or an interest in it, or in discovering one, shouldn't be assumed to confer any license or capacity to operate it. Individual criticisms of a system, incapacity to operate it, or dissatisfaction with it should not be confused with any shortcoming of the system itself. ___ 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]
On Wed, 31 May 2017, Per olof Ljungmark wrote: > Let me just say that I would really, really appriciate if we could keep > such a simple tool. Why does it suit us? Because we have a limited > number of systems, [...] And the sytems we do have can be somewhat limited; I mean, Ada, FFS? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: cdecl port
On Sun, 30 Apr 2017, Paul J. Lucas wrote: > Note that I don’t use FreeBSD myself; I’m just the author of the new > cdecl. And a great program it is too! I've been using it since it was first posted to Usenet. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: consul-0.7.5
On Mon, 3 Apr 2017, at 20:32, Douglas Thrift via freebsd-ports wrote: > Hello, > > It looks like the newly updated consul version is not showing when > running "consul members". Instead of showing 0.7.5 it is still showing > 0.7.1. > > Thanks! > -- > Douglas William Thrift Hi Douglas patch + bugzilla filed. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218340 A+ Dave ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
new port needs committer -- sysutils/lava - apache couchdb view heater & databases/p5-Store-CouchDB
hi all, This very simple (and therefore hopefully error-free on my part :D) port from December would like a committer: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215508 It ensures that all couchdb indexes (views) are kept up to date, even if not directly used by the application. I also added a new perl-based port for Store::CouchDB yesterday, which as my first perl port may not be as error free as sysutils/lava, but feedback would be welcome. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217597 A+ Dave ___ 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: Kodi build fails /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.11 required
On Monday 27 February 2017 21:25:08 you wrote: > > Enviar: lunes 27 de febrero de 2017 a las 21:12 > > De: Dave > > Para: freebsd-ports@freebsd.org > > CC: "Carlos Jacobo Puga Medina" > > Asunto: Re: Kodi build fails /usr/local/lib/compat/libstdc++.so.6: version > > GLIBCXX_3.4.11 required > > > > On Monday 27 February 2017 18:54:56 you wrote: > > > Hi Dave, > > > > > > You must deinstall misc/compat9x before install multimedia/kodi. > > > > > > When the kodi installation is complete, you can install compat9x port > > > again. > > > > Yes, that fixed it. Thanks! > > > > I was almost at the solution myself when your email arrived. > > > > I was being a bit blind in terms of the relevant file being in > > the compat hierarchy and had just noticed that. I'd not quite > > got to the point of thinking of or trying a deinstall of compat9x > > though. I was just about to try a reinstall of compat9x > > > > Doing a pgk delete of compat9x showed only archivers/rar as > > a dependency. Sadly, I need rar installed so need compat9 too. > > > > Both reinstalled safely after the Kodi build/install though. > > > > Thanks again. > > > > Unfortunately, build conflicts are not recorded in the resulting package. > > % cd /usr/ports/multimedia/kodi && make -V CONFLICTS_BUILD > compat9x > > misc/compat9x is listed in CONFLICTS_BUILD [0]. So it's a good idea to > manually check the Makefile. > > [0] > https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/conflicts.html Thanks Carlos, I wasn't aware of that. Added to my "fix it" armoury :-) (Copied into ports@ list for completeness of solution) ___ 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: Kodi build fails /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.11 required
On Monday 27 February 2017 18:54:56 you wrote: > Hi Dave, > > You must deinstall misc/compat9x before install multimedia/kodi. > > When the kodi installation is complete, you can install compat9x port again. Yes, that fixed it. Thanks! I was almost at the solution myself when your email arrived. I was being a bit blind in terms of the relevant file being in the compat hierarchy and had just noticed that. I'd not quite got to the point of thinking of or trying a deinstall of compat9x though. I was just about to try a reinstall of compat9x Doing a pgk delete of compat9x showed only archivers/rar as a dependency. Sadly, I need rar installed so need compat9 too. Both reinstalled safely after the Kodi build/install though. Thanks again. ___ 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"
Kodi build fails /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.11 required
It seems Kodi requires GLIBCXX_3.4.11 /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.11 required by /usr/ports/multimedia/kodi/work/xbmc-c327c53/tools/depends/native/JsonSchemaBuilder/bin/JsonSchemaBuilder not found I can't find anything in ports or packages which might install GLIBCXX_3.4.11 Anyone got any pointers for me? Or is it broken? ___ 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"
