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: 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"
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
[ 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: 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: 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"
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"
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: 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: 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"
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
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 <d...@horsfall.org> To: Mel Pilgrim <list_free...@bluerosetech.com> 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"
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: 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: 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: <owner-freebsd-po...@freebsd.org> 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 <d...@horsfall.org>; 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 <freebsd-po...@mailman.ysv.freebsd.org>; 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 <freebsd-ports@freebsd.org>; 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 <n...@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 <n...@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
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: 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: Do I need /var/db/portsnap/distfiles and /usr/port/distfiles?
On Thu, 16 Feb 2017, RW via freebsd-ports wrote: > > aneurin# du -sk /usr/ports/distfiles /var/db/portsnap/files > > 965198 /usr/ports/distfiles > > This is a cache, so you can delete it, or trim it with distclean > (installed with portupgrade), or portmaster. Thanks; nearly 1GB here I come... > > 106594 /var/db/portsnap/files > > If you don't use portsnap then you can delete everything under > /var/db/portsnap. Don't delete these files if you do. Yes, I do use portsnap, so thanks for the advice. -- 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"
Finally got ports rebuilt!
Well, almost; just a few rough edges to smooth over. Background: after upgrading to 10.3 from 9.3, I then attacked the long-neglected ports area. Now, I sort of inherited this installation, and having an engineering background i.e. "if it ain't broke, don't fix it". Just so you know where I come from, I also have 40+ years of Unix experience across a wide range of platforms; FreeBSD is my first, although I used SunOS and BSDi for many years, so I'm hardly new to BSD. I was scrupulous about installing various security fixes, however... So... There appears to be circular dependencies involving libiconv and libxslt, which I resolved by installing them by hand. All sorts of things want the Ruby bloatware (it won't build on my box) so I installed it as a package. Riding shotgun for most of the night (yawn...), some things kept wanting to build LLVM (!), so I merely blew them away one by one (there's no way that LLVM will build here); I doubt whether I'll miss them, but I can always install them as packages if they're needed. UUCP needed to be rebuilt? And Apache, although installed from ports, was not selected to be rebuilt for some reason. Anyway, that's pretty much it; many thanks to David Wolfskill and Tijl Coosemans for their kind assistance, and to the list members for their forbearance as I went through this learning exercise; I promise to keep ports up to date in the future. Thanks again. -- 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: Problem with building libgcrypt
> > What is the output of "pkg which /usr/local/lib/libiconv.la"? > > Not found; I sense a generic approach to any more errors of this type :-) Removed as suggested (along with libxslt) as nothing claimed to be using it, now it's complaining that they're missing when building graphics/peps (I gave docbook a miss): libtool: error: cannot find the library '/usr/local/lib/libiconv.la' or unhandled argument '/usr/local/lib/libiconv.la' Why is libiconv.la now suddenly required? At this rate it'll be a full install, but that is definitely a last resort (and the 10.3 CD I burned had better be readable). -- 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: Problem with building libgcrypt
On Mon, 13 Feb 2017, Tijl Coosemans wrote: > > cc: error: no such file or directory: '/usr/local/lib/libiconv.so' > > gmake[4]: *** [Makefile:534: libxslt.la] Error 1 > > That's probably still because of some .la file. I did run those commands as suggested... > Does /usr/local/lib/libiconv.la still exist? -r--r--r-- 1 root wheel 919 Dec 12 2010 /usr/local/lib/libiconv.la Hmmm... That should go too. Note that I didn't build this system; I merely "inherited" it and not having any FreeBSD experience I took the cautious "engineers" approach of "it it ain't broke, don't fix it" so I confined myself to kernel and security updates, otherwise leaving ports strictly alone. > What is the output of "pkg which /usr/local/lib/libiconv.la"? Not found; I sense a generic approach to any more errors of this type :-) 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: Problem with building libgcrypt
On Sun, 12 Feb 2017, Tijl Coosemans wrote: > > *** [libgcrypt.la] Error code 1 > > See the 20140909 entry in /usr/ports/UPDATING about missing .la files. Thanks - that did the trick. Next problem: when building misc/freebsd-doc-en, it fails with: libtool: link: cc -shared -fPIC -DPIC .libs/attrvt.o .libs/xslt.o .libs/xsltlocale.o .libs/xsltutils.o .libs/pattern.o .libs/templates.o .libs/variables.o .libs/keys.o .libs/numbers.o .libs/extensions.o .libs/extra.o .libs/functions.o .libs/namespaces.o .libs/imports.o .libs/attributes.o .libs/documents.o .libs/preproc.o .libs/transform.o .libs/security.o -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib -L/usr/local/lib /usr/local/lib/libxml2.so /usr/local/lib/libiconv.so -lz -llzma -L/usr/lib -lm -O2 -fstack-protector -Wl,--version-script=./libxslt.syms -fstack-protector -Wl,-soname -Wl,libxslt.so.1 -o .libs/libxslt.so.1.1.29 cc: error: no such file or directory: '/usr/local/lib/libiconv.so' gmake[4]: *** [Makefile:534: libxslt.la] Error 1 I take it that this is a manifestation of 20130904: AFFECTS: 10-CURRENT users with any port depending on converters/libiconv AUTHOR: madpi...@freebsd.org 10-CURRENT after r254273 (committed on August 13, 2013) has an implementation of iconv enabled by default in libc. ? -- 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 building libgcrypt
Rebuilding ports on 10.3 after upgrade from 9.3, on the final portmaster leg: libtool: link: ranlib .libs/libgcrypt.a libtool: link: rm -fr .libs/libgcrypt.lax sed: /usr/local/lib/libintl.la: No such file or directory libtool: link: `/usr/local/lib/libintl.la' is not a valid libtool archive *** [libgcrypt.la] Error code 1 ... ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. (Followed by a few "Aborting update" messages) Ummm, that's equivalent to the M$ "solution" of trying a reboot to see if it fixes it. It's asking me to review those errors before it continues; what could be wrong? Think of me as a beta tester for novices :-) -- 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"
Question on upgrading ports after 9.3->10.3
Me again :-) I finally got around to following the notes that David Wolfskill kindly provided (thanks!) and apart from some oddity about "httpd" requiring a missing "libdb-4.2.so.2" (which will get rebuilt anyway), I'm a bit wary of this: 7. Back up any files in /usr/local that you wish to save [...] 8. Manually check /usr/local [...] to make sure that they are really empty. Errm, why? Is it going to clean out /usr/local from under my feet? If so, then that's a bit rude... Because of disk space limitations, I've got /usr/ports -> /usr/local/ports (/usr/local is a separate file system). And then there's all my private stuff... I think it means "save any local configuration files etc"; if so, it could be better phrased. PS: For those who also have a Mac, do *not* futz around with symlinks in this manner, as it confuses the hell out of macports... -- 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: libstdc++
On Wed, 11 Jan 2017, Adam Weinberger wrote: > Okay. So what command did you use to rebuild all your ports? You won't > really be able install anything new until you've rebuilt everything. > Everything. Haven't had a chance to try your script yet; been too busy trying to get my nameserver to support my internal domain ".kfu" (yes, it's 10.3); it doesn't even work on the box itself, but the resolver is fine. My guess is that something has changed in BIND... > I'm not aware of any problems building alpine on 10.3. I do see a typo > in its OpenSSL handling and I'll fix that shortly. That's the only problem with Alpine; it's not seeing "1.0.2j" of OpenSSL, yet wants ">= 1.0.1c", hence the 9.3 version... It was critical that I get email working ASAP, and this is the only FreeBSD box I have. > If you keep running into headaches upgrading in-place, you should really > switch to poudriere. Even if you get stuff working, you should really > switch to poudriere. See > https://www.freebsd.org/handbook/ports-poudriere.html for how to get up > and running with it. I thought poudriere was for building packages to support a server farm? Sorry for all this, but until now this box has always been on 9.x, so this is my first major upgrade, hence I have zero experience... -- 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: libstdc++
On Tue, 10 Jan 2017, Adam Weinberger wrote: > > I want to install "aspell", and it wants "libstdc++.so.6". All I can > > find under ports is /usr/ports/lang/libstdc++_stldoc_4.2.2, which > > seems to be documentation only. Is the port for the library itself > > available, to make "aspell" happy? Or is it one of those silly GNU > > things are aren't allowed to be distributed under another licence? > > You said in a prior message that you'd put 9.x libraries into your > system. That's quite far from being a supported operation and it will > lead to failures. Not all of them, no; only the ones needed to support stuff like Alpine which won't build on 10.3 due to its schizophrenic view of OpenSSL (maintainer contacted, but no reply); I explained this in another thread. > Assuming that you have installed everything from packages, you can > upgrade and reinstall all of them with "pkg upgrade -f". Remove all > those 9.x libraries that you installed and run that command. I prefer to install from ports, to get the options I want rather than someone else's opinion of what I might want... > If you're getting packages with the wrong ABI, have you changed anything > in /etc/pkg/ or /usr/local/etc/pkg/? Haven't touched them, because I don't know what they are... -- 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"
libstdc++
Sigh... Will I ever get ports going under 10.3? I want to install "aspell", and it wants "libstdc++.so.6". All I can find under ports is /usr/ports/lang/libstdc++_stldoc_4.2.2, which seems to be documentation only. Is the port for the library itself available, to make "aspell" happy? Or is it one of those silly GNU things are aren't allowed to be distributed under another licence? -- 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: portsnap temporary files
Sigh... It seems those files were needed after all, as they must refer to the current system; chalk it up to my lack of understanding of how "portsnap" works. I got them back (plus more besides) from a backup on my MacBook. What freaked me out was actually looking at the list of files being backed up, and thought the worst. And the sooner I upgrade to FreeBSD-10 the better, I think. Sorry for wasting everyone's time... -- 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: portsnap temporary files
On Fri, 6 Jan 2017, Xin LI wrote: > Because the files are still being used? What makes you believe they are > unused, by the way? How would I tell? Some were there since last October, surviving a few reboots... What I do see is the INDEX file containing "...|$tmpfile"; could that be the problem? That INDEX hadn't been cleaned out for some reason? -- 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: portsnap temporary files
(Many responses) I note that no-one has answered the question which caused me to post the message in the first place viz: why weren't the files being removed automatically? Everyone appears to have missed this point... -- 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: portsnap temporary files
On Fri, 6 Jan 2017, olli hauer wrote: > Why? For the reason I stated; I had to remove hundreds of them by hand. > As soon you run "portsnap fetch" old files in this directory are purged! Not here they weren't... > If you look into /var/db/portsnap/INDEX you can see the mapping of the > files I don't have that file. > I'm running portsnap on one system since portsnap was introduced and > never had issues with cleanups. Hmmm... -- 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"
portsnap temporary files
Is there some reason why portsnap cannot clean up /var/db/portsnap/files? I've just had to remove a zillion of them, a bunch at a time because "rm" choked on the arg list. Perhaps a "portsnap clean" command? I'm surprised that there isn't 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: The ports collection has some serious issues
On Mon, 19 Dec 2016, John Marino wrote: > I never, not once, tried to "get rid of portmaster". By repeating this > untruth after I already corrected you is trolling. There was a very > small chance you were just ignorant but thanks for admitting you knew > exactly what you were doing and making Dave H. look silly. > > What I have (and others) wanted? What would make us happy? Perhaps for you to just quietly FOAD? When it comes to common sense, you appear to be utterly impervious. -- 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 collection has some serious issues
On Sun, 18 Dec 2016, John Marino wrote: > > > Real smooth there, Slick. > > > > Sarcasm might get you somewhere, but I'm not sure you want to be > > there. > > He was trolling. You know it. I know it. Everyone that read it knows it. I happen to know Peter as a friend; you don't. He doesn't troll; you do. And who is this "everyone", anyway? Either enumerate them, or STFU. -- 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"
FOCAL
Be there an implementation of FOCAL? I have a hankering to get back to my early programming days :-) -- 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"
Binary for Ruby?
Is a binary available for Ruby? System is (currently) 9.3-RELEASE-p43 (soon to go to 10 when I get a new server one day). It's not possible to compile the thing on my (minimal) box, as it keeps blowing away swap. The only reason I need Ruby (I don't even know the language) is that it's used by something which I've forgotten. -- 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: Inconsistency? (was Re: misc/jive deleted)
On Tue, 25 Oct 2016, David Demelier wrote: > I'm a bit surprised to see so much traffic about the jive removal. I'm not :-) > I personally don't care about offensive software, users are free to not > use it (sudo may have funny insults, disabled by default though). > Perhaps marking it broken because it's offensive was inappropriate. Which was the whole point of the argument. > However bapt pointed out some valuable reasons, the software is not > maintained and has no more distfiles available and this was a good > reason for being removed. So once the *technical* requirements have been met (as opposed to someone's delicate sensibilities being offended), it's OK to bring it back? Could be tricky, though, as the sources were posted to USENET some time in the 80s... > And the daemon logo is a ball for several years now, not really a daemon > anymore. :) Have you seen the FreeBSD home page? -- 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: misc/jive deleted
On Sat, 22 Oct 2016, Alphons van Werven wrote: > There used to be "offensive" (a term to be taken rather loosely in this > case) fortune cookies, but they got kicked out somewhere in 9.X. That > was the base system though; not the ports tree. Not to mention "fortune -o" (to get the obscene versions) and there were some beauties there... > Come to think of it, I'm quite (be it pleasantly) surprised to see that > deskutils/hot-babe is still allowed. I'm still half waiting for someone > with misguided delusions of moral superiority to delete that port, > thinking it's their decision to make that FreeBSD must not enable people > to display their system load as a cartoon woman in various stages of > undress. Or something along those lines. But I digress... I never cease to be astonished by censorship. > Anyway, if anyone misses this port, I'll be happy to maintain it > privately and make it available from a public repository, if only > because I strongly oppose censorship, so I would gladly help circumvent > what I consider to be a hopelessly outdated and even morally wrong > concept. Yes please; it seems to be marked as broken: aneurin% cd wmfortune aneurin% less *descr WMFortune outputs fortune messages, just as its name says. aneurin% make ===> wmfortune-0.241_3 is marked as broken: No public disfiles. *** [all] Error code 1 Stop in /usr/ports/games/wmfortune. Sigh... -- 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: misc/jive deleted
On Sat, 22 Oct 2016, andrew clarke wrote: > At the risk of this developing into a flame war, I thought this was > curious: > > https://lists.freebsd.org/pipermail/svn-ports-head/2016-August/126687.html > > Is this the first time a port has been deleted for being "offensive"? "man jive | jive" is quite hilarious, and I almost lost my job for piping all man pages through it; the boss had a "drinkful night" and was sure that his eyes were playing tricks on him, until he figured out that I was the perp. The man page for UUCP was quite interesting, for example; I actually had UUCP running on my home Z-80 box (there were overlays to hell and back). Next thing you know, "valgirl" will be deleted from 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: harder and harder to avoid pkg
On Fri, 14 Oct 2016, David Demelier wrote: > It's not writing a port that is complicated, it's the whole > infrastructure. You should see the Macports infrastructure... Fairly easy for the end user, but those developers sweat blood to make it so. -- 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: What sort of a hog is Ruby?
On Fri, 7 Oct 2016, Graham Menhennitt wrote: > > First it blew out my disk space (the "work" sub-directory), so when I > > rearranged a few things to make more room it blew out my swap space! > > Not sure what's going on with yours, but mine doesn't show any of those > symptoms. I build it regularly on a relatively low spec box (AMD G-T40E > Processor (1000.02-MHz K8-class CPU) with 4Gb RAM). Which version of > Ruby and which version of FreeBSD? Current Ruby is ruby-2.0.0.576_1,1, trying to go to ruby23-2.3.1_1,1 . It regularly blows out /tmp (i.e. swap) when compiling ripper.c . FreeBSD is 9.3-RELEASE-p43, trying to get to 10.3 once I'm sure that my entire system (inc. ports) is clean i.e. start from a known base. Box itself is an ancient Asus Evo picked up from a flea market (I think; I know that it came with the virus known as Windoze, but that was quickly repaired). CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1794.22-MHz 686-class CPU), Real memory = 537395200 (512 MB) (the other SIMM failed). Disk layout: System 1K-blocksUsed Avail Capacity Mounted on /dev/ad0s1a507630 266022 20099857%/ devfs 1 1 0 100%/dev tmpfs 197988 28 197960 0%/tmp /dev/ad0s1d 3045006 1969334 83207270%/usr /dev/ad0s1e 1012974 791796 14014285%/var /dev/ad0s1f 4058062 2244968 148845060%/home /dev/ad0s1g 9287662 4991590 355306058%/usr/local devfs 1 1 0 100%/var/named/dev Swap: Device 1K-blocks UsedAvail Capacity /dev/ada0s1b 1048576 932100 11647689% (I'm busy rebuilding Ruby again; if it fails then I'll just stick with the old one, or make /tmp a real FS.) On Fri, 7 Oct 2016, Peter Jeremy wrote: > My ruby22 work tree is 415MB. That's not small but it pales next to > openjdk, firefox or mongodb. Never had to compile those, thank $BABBAGE... On Fri, 7 Oct 2016, Garance A Drosehn wrote: > The size of ruby compared to ? Compared to anything else I've compiled... > How big is the partition with /usr/ports on it? See above. > What size is your swap area? See above. > I do not know much about the 'pkg' command, but it looks > like you could try: >pkg info lang/ruby\* > > Which for me lists: >ruby-2.2.5_1,1 >ruby21-2.1.9_1,1 aneurin% pkg info lang/ruby\* ruby-2.0.0.576_1,1 > Then to see what ruby depends on, try: >pkg query %dn ruby aneurin% pkg query %dn ruby readline libyaml libffi libexecinfo >Which for me lists these ports as dependencies *of* ruby > (you need to build these ports before building ruby): >libedit >openssl >libyaml >libffi >libexecinfo As it happens, I'm busy compiling OpenSSL right now (I'm a bit anal when it comes to security). > ruby itself isn't too large, but if building ruby means that > you need to build those ports, then the build of all of that > will chew up a lot more resources (both disk space and swap). Sure does :-( > If you want to find out what packages depend on ruby, try: >pkg query %rn ruby aneurin% pkg query %rn ruby portupgrade ruby20-bdb > which for me (on my machines) lists: >ruby22-bdb >portupgrade > > Portupgrade is what I use to build freebsd ports, so I would not > be dropping that anytime soon. > > Ruby isn't tiny, but building it has never been a problem on > any of my systems, ever. I seem to remember that I have run > into issues when I went to build some port which in turn built > many other ports, but that was quite some time ago. Maybe that > is what you're seeing. Yeah, it's a requirement of something else (I didn't install it by choice). I must see if I can install just binaries, like I can with the Mac. -- 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: Vulnerabilities in X libs
On Sat, 8 Oct 2016, Kevin Oberman wrote: > > libXrender-0.9.9 is vulnerable > > libX11-1.6.3,1 is vulnerable > > > > "freebsd-update fetch" is not (yet) fetching anything. > > Depending on timezone, these were resolved last night. Update your ports > tree (svn or portsnap) and you should have it. If you are using > packages, you will need to wait until the next build is completed. > freebsd-update only updates the base system, not ports. Nope, at least not as of 1400 UTC+11. System is 9.3-REL p43 (soon to go to 10.3 when I'm sure that my ports are clean - it was corrupt for a while), and won't go to p47 because of those vulnerabilities. I'm not too concerned; my system is locked down tighter than a duck's bum. -- 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"
Vulnerabilities in X libs
May I assume that these are being addressed? libXrender-0.9.9 is vulnerable libX11-1.6.3,1 is vulnerable "freebsd-update fetch" is not (yet) fetching anything. -- 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"
What sort of a hog is Ruby?
Looks like I need to upgrade it for security issues; so I tried to compile it from the ports area. First it blew out my disk space (the "work" sub-directory), so when I rearranged a few things to make more room it blew out my swap space! On my box /tmp is "tmpfs" i.e. use memory first before overflowing into swap; that's going to be trickier to fix... I guess I'll have to kludge /tmp as a symlink into /usr/local or something, where I have heaps of room. On the other hand I guess I could figure out what requires Ruby, and decide whether I really need it. What sort of disk farms do these developers have? I'm only a small-time user and wannabe developer... -- 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: Will 10.3 clobber my ports area?
On Tue, 4 Oct 2016, Kevin Oberman wrote: [ Reloading ports ] > Of course. You can use portsnap(8) to do this. See 4.5 - Using the Ports > Collection > <https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html> > for details. It's quite trivial. This also will give you the latest > versions of all ports. Many thanks! Now to pick a time to gird my loins... -- 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: Will 10.3 clobber my ports area?
On Wed, 5 Oct 2016, Dave Horsfall wrote: > Oh, this is for Joseph Mingrove: my mail log shows a message from you > (relayed via FreeBSD.org) but there's nothing in my mailbox about it > (and it certainly wasn't rejected). I guess I accidentally deleted it, > so could you please send it again? Skip it; it would've been some unassociated message on the list... -- 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: Will 10.3 clobber my ports area?
On Mon, 3 Oct 2016, Kevin Oberman wrote: > The ports will not be touched, but some will not run on 10.3 because of > ABI changes in some shareable libraries. Most of the base system uses > versioned symbols, so will work fine, but some, usually contributed > code, don't. Ports that use them will need to be re-installed/rebuilt. [...] Many thanks; I'm a bit nervous, as this is my only FreeBSD server :-) I know I'm going to have trouble with the ports area anyway, because I seem to have corrupted it somehow (during the switch between pkg* etc), and I cannot seem to reload it from the CD (disc1). Is there a way to fetch the entire ports tree online? Oh, this is for Joseph Mingrove: my mail log shows a message from you (relayed via FreeBSD.org) but there's nothing in my mailbox about it (and it certainly wasn't rejected). I guess I accidentally deleted it, so could you please send it again? -- 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"
Will 10.3 clobber my ports area?
Assuming the binary upgrade from 9.3 to 10.3 is "clean" i.e. it won't clobber any of my local stuff (this is my only FreeBSD server), what will happen to the ports area? Left alone, saved, or overwritten with/without any local chnages? -- 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: [maintainer change] net-mgmt/cnagios
On Sat, 17 Sep 2016, Alexander wrote: > P.S. Sorry for my English. Please don't apologise for your English; we are multi-national here (and Americans don't speak English anyway). I know some French, and a small amount of Italian, Spanish, and German; I am currently trying to learn Mandarin. As for Portuguese, it may as well come from a different planet... -- 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: LICENSE documentation
On Wed, 14 Sep 2016, Kurt Jaeger wrote: > This interpretation is based on the hypothesis that the user is located > in a country that has this kind of legal rule. > > This is not the case in every country, so your conclusion is not always > valid. What percentage of countries are signatories to the Berne Convention? Last I looked, only nice friendly places such as China and North Korea were holding out (and USA was one of the last to sign, and even then with conditions). -- 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 47.0 hangs when accessing cnn.com
Binary works fine for me on my MacBook (OS/X), if that helps. -- 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"
