From owner-freebsd-pkg@freebsd.org Sun Apr 23 21:00:16 2017 Return-Path: Delivered-To: freebsd-pkg@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 7E49BD4D9A1 for ; Sun, 23 Apr 2017 21:00:16 +0000 (UTC) (envelope-from bugzilla-noreply@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 6F4681DBE for ; Sun, 23 Apr 2017 21:00:16 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6EC8AD4D99F; Sun, 23 Apr 2017 21:00:16 +0000 (UTC) Delivered-To: pkg@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 6E82DD4D99E for ; Sun, 23 Apr 2017 21:00:16 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DBB51DBC for ; Sun, 23 Apr 2017 21:00:16 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v3NL01kV071305 for ; Sun, 23 Apr 2017 21:00:16 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201704232100.v3NL01kV071305@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: pkg@FreeBSD.org Subject: Problem reports for pkg@FreeBSD.org that need special attention Date: Sun, 23 Apr 2017 21:00:16 +0000 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Apr 2017 21:00:16 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 212022 | ports-mgmt/pkg: Segfaults when installing sensu p Open | 211141 | ports-mgmt/pkg: pkg+pw: Doesn't run pwd_mkdb, may New | 193995 | [PATCH] ports-mgmt/pkg: floating point exception 3 problems total for which you should take action. From owner-freebsd-pkg@freebsd.org Tue Apr 25 16:10:57 2017 Return-Path: Delivered-To: freebsd-pkg@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 0C2E0D50EA5 for ; Tue, 25 Apr 2017 16:10:57 +0000 (UTC) (envelope-from mellisa.hutchina@opsview.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id A76BA83C for ; Tue, 25 Apr 2017 16:10:56 +0000 (UTC) (envelope-from mellisa.hutchina@opsview.com) Received: by mailman.ysv.freebsd.org (Postfix) id A3E0ED50EA2; Tue, 25 Apr 2017 16:10:56 +0000 (UTC) Delivered-To: pkg@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 A36FDD50EA1 for ; Tue, 25 Apr 2017 16:10:56 +0000 (UTC) (envelope-from mellisa.hutchina@opsview.com) Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0093.outbound.protection.outlook.com [104.47.0.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C010382E for ; Tue, 25 Apr 2017 16:10:55 +0000 (UTC) (envelope-from mellisa.hutchina@opsview.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORG856710.onmicrosoft.com; s=selector1-opsview-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=3Ir493+9DbX6UJ+Q0cDeVj7TfmY8RcrrG9oIxzI8hLk=; b=yZ7SZw1IgYePimkdnX+UNqFFP7/KNMTlz6v9vGSIRALCeMCQpsdGU/IogLPu+IpzdamhnJfNGvzG1WJww8W1ykgYbOjWj3BfskFqLAYD5CsK++95SSOXTsqkTq47FY/ekjCadqmzTyXB7E8suvpeYntn+EHP3dEfuKrAOvNaI2Y= Received: from DB3PR02MB089.eurprd02.prod.outlook.com (10.141.2.142) by DB3PR02MB089.eurprd02.prod.outlook.com (10.141.2.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.13; Tue, 25 Apr 2017 16:10:51 +0000 Received: from DB3PR02MB089.eurprd02.prod.outlook.com ([fe80::d5f:b0e4:9cfe:eef3]) by DB3PR02MB089.eurprd02.prod.outlook.com ([fe80::d5f:b0e4:9cfe:eef3%27]) with mapi id 15.01.1047.019; Tue, 25 Apr 2017 16:10:51 +0000 From: Mellisa Hutchina To: "tech@openbsd.org" , "pkg@freebsd.org" Subject: About Your Linux Monitoring Post Thread-Topic: About Your Linux Monitoring Post Thread-Index: AQHSvd6BqisQgMaBmkaA85rIpSTvpg== Date: Tue, 25 Apr 2017 16:10:50 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: yes X-MS-TNEF-Correlator: authentication-results: openbsd.org; dkim=none (message not signed) header.d=none;openbsd.org; dmarc=none action=none header.from=opsview.com; x-originating-ip: [81.145.162.242] x-microsoft-exchange-diagnostics: 1; DB3PR02MB089; 7:2Y89SSCwClDQ+HqYfDRGk6lgeWvkhx1RlFm87dWEMYFvM3w0WGBteYGMcZB1gLE7a6G9zJJl8+vvOd2Ew0Iw6FYdfsSaa/qRcsVedsRStA+UUhxtL+5sp9VmpuboGQ1aeCJB1wB5xjy28RqFq6g+LQF4A3P2HXO8j6r/j60w9DJa1qAXbm9fOuKsuVzAHGOSjTgMqwWE5+hE6/Z61r/Pckem0PLvCgW+XioBqrjhdyt44/AtG3RPu0nlY9fCv4yGDrXq1eDQeuSZTE8EB2JzaJ551oX7UMJRd37pxI64q1NaNEPb3eR96zCHXewf3XRYPw79LlBoV7svbLwKwZaoXQ== x-ms-office365-filtering-correlation-id: 4529e5a5-03c6-428e-5f29-08d48bf5a4a2 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:DB3PR02MB089; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863)(72170088055959)(31418570063057)(128460861657000)(211936372134217)(80641642340047)(86561027422486)(81160342030619)(64217206974132); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040450)(601004)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123562025)(20161123560025)(20161123564025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(6072148); SRVR:DB3PR02MB089; BCL:0; PCL:0; RULEID:; SRVR:DB3PR02MB089; x-forefront-prvs: 0288CD37D9 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39400400002)(39830400002)(39410400002)(39450400003)(365934003)(84964002)(51414003)(252514010)(3846002)(102836003)(6116002)(9686003)(236005)(33656002)(189998001)(8936002)(25786009)(861006)(54896002)(6606003)(7696004)(53936002)(5250100002)(99286003)(8676002)(55016002)(54556002)(6306002)(5890100001)(86362001)(38730400002)(74316002)(81166006)(606005)(7736002)(733005)(5660300001)(7906003)(19618635001)(2900100001)(2501003)(3660700001)(6436002)(2906002)(345774005)(66066001)(99936001)(19627405001)(6506006)(3280700002)(50986999)(54356999)(40973001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR02MB089; H:DB3PR02MB089.eurprd02.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: opsview.com X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Apr 2017 16:10:50.8405 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: e371eae9-7106-409b-ab02-4cd08daadd1a X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR02MB089 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2017 16:10:57 -0000 Hi there, I work on the web team here at Opsview, we are an= industry leading server monitoring company. You may be wondering if I am s= elling you something. There is no charge or cost involved in any of this. M= y team are responsible for creating web content and making sure that it is = relevant and useful. I=92m contacting you because I noticed that your website offers content aro= und Linux monitoring, such as https://38elements.github.io/2016/10/15/c-rep= ository-github-star-ranking.html. Over the next year Opsview will be creating a host of content in this space= , I wanted to run the following article by you to collect your thoughts on = it. The article discusses how to organise your servers, how to prioritise comma= nds and how to safeguard your Linux environment. The link is: https://www.opsview.com/resources/blog/monitor-linux-servers. We are always on the lookout for new partnerships and would be keen to disc= uss any ideas you may have for shared content across your website and ours.= We would be willing to amplify any content you created across our social m= edia. Thank you for taking the time to read this. I look forward to hearing from you, Mellisa Hutchina Marketing Executive Opsview [1483545863281_s.png] E-mail: mellisa.hutchina@opsview.com www.opsview.com [1483546000499_sd.png][1483546010464_d.png][148354601= 7743_e.png][1483546022772_3.png][14835460= 25720_q.png] This e-mail is confidential, intended only for the named recipient(s) above= and may contain information that is privileged and confidential. If you re= ceive this message in error, or are not the named recipient(s), please noti= fy the sender at the phone number above, do not copy this message, do not d= isclose its contents to anyone, and delete this e-mail message from your co= mputer. Although we routinely screen for viruses, addressees should scan th= is e-mail and any attachments for viruses. Opsview Limited is a company reg= istered in the UK under Company Number 5396532. Our registered office is En= terprise Centre, Whiteknights Road, Reading, RG6 6BU, UK Please consider the environment before printing this email message. From owner-freebsd-pkg@freebsd.org Tue Apr 25 21:44:29 2017 Return-Path: Delivered-To: freebsd-pkg@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 0AE80D50A2E for ; Tue, 25 Apr 2017 21:44:29 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id E59B7C90 for ; Tue, 25 Apr 2017 21:44:28 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 679223AE87 for ; Tue, 25 Apr 2017 14:34:54 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-pkg@freebsd.org Subject: Help please... Upgrade to pkg no workie Date: Tue, 25 Apr 2017 14:34:54 -0700 Message-ID: <83939.1493156094@segfault.tristatelogic.com> X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2017 21:44:29 -0000 This is rather embarassing, but OK, I confess... One of my systems here is running the ancient FreeBSD 9.1 and it hasn't been upgraded in a long long time. Like not at all. No package updates, nothing. Today however I desperately need to upgrade the installed Perl. (Apparently, the Perl that I have installed on this system, v5.16, has an old and not at all up-to-date Unicode implementation.) As you all know, fBSD 9.1 used the older package system. I am well and truly aware of the fact that, in order to move forward, I will need to upgrade to the new package system (pkg). So I've been reading this page that purports to give directions on exactly how to do that: https://www.freebsd.org/doc/handbook/pkgng-intro.html Unfortunately, for me at least, the guidance here raises nearly as many questions as it answers. For example, it says to do these two things: 1) Run pkg2ng. 2) Put a line like "WITH_PKGNG=yes" into /etc/make.conf What it doesn't say is whether the first thing must be done strictly *before* the second thing, or vise versa, or if the order here even matters at all. (I don't want to totally screw up my system, so in the absence of complete clarity, and since I don't really know exactly what the effects of either of these two steps really are, I am inclined to proceed with great caution and thus requast clarification from this list.) Anyway, I decided to look and see if perchance I might already have the new & improved pkg command on my system. So I did "which pkg" and lo and behold, an executable with that name is already present on this system as /usr/sbin/pkg. (I have no clear recollection, one way or the other, whether or not, in years past, I may have deliberately installed this /usr/sbin/pkg or not.) Anyway, I decided to throw the dice and run this, with no options or arguments, just to see if that would give me a list of command line options or what. I was almost immediately greeted with a message saying that the new pkg system was *not* in fact actually installed and asking me ([y/N]) if I wanted to install it. I control-C'd out of this, before I did any damage, and plotted my next move. I realized that to actually install this thing, I'd probably need to be root, so I su'd to root and then cd'd to ~root and started "script" so that I'd have a full log in case anything went wrong... which it promptly did. Here's the log. It isn't pretty. ============================================================================== root@segfault:/root # pkg The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: y Bootstrapping pkg please wait Installing pkg-1.9.4_1... pkg-static: dup2(rootfd): Invalid argument Extracting pkg-1.9.4_1: 0% pkg-static: Fail to create /usr: Bad file descriptor Extracting pkg-1.9.4_1: 100% Failed to install the following 1 package(s): /tmp//pkg.txz.q9abRX root@segfault:/root # exit ============================================================================== So? NOW what should I do? Any & all advice appreciated. (I still desperately need to get Perl upgraded.) From owner-freebsd-pkg@freebsd.org Wed Apr 26 07:32:30 2017 Return-Path: Delivered-To: freebsd-pkg@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 B77E3D51B7B for ; Wed, 26 Apr 2017 07:32:30 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5F539D8E for ; Wed, 26 Apr 2017 07:32:30 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from liminal.local (unknown [IPv6:2001:8b0:151:1:1c1d:86a1:a200:b700]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id B030BC932 for ; Wed, 26 Apr 2017 07:32:21 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/B030BC932; dkim=none; dkim-atps=neutral Subject: Re: Help please... Upgrade to pkg no workie To: freebsd-pkg@freebsd.org References: <83939.1493156094@segfault.tristatelogic.com> From: Matthew Seaman Message-ID: <89617edf-9411-2d3e-2f3c-4cab1e530bfd@FreeBSD.org> Date: Wed, 26 Apr 2017 08:32:15 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <83939.1493156094@segfault.tristatelogic.com> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GgXFVnlHoSSaDcNN1u2K2rnUMvp6Lk6gA" X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,RDNS_NONE, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2017 07:32:30 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --GgXFVnlHoSSaDcNN1u2K2rnUMvp6Lk6gA Content-Type: multipart/mixed; boundary="4xnSkGfFIhISEtfT9qxhNP2uMlrLoqIq9"; protected-headers="v1" From: Matthew Seaman To: freebsd-pkg@freebsd.org Message-ID: <89617edf-9411-2d3e-2f3c-4cab1e530bfd@FreeBSD.org> Subject: Re: Help please... Upgrade to pkg no workie References: <83939.1493156094@segfault.tristatelogic.com> In-Reply-To: <83939.1493156094@segfault.tristatelogic.com> --4xnSkGfFIhISEtfT9qxhNP2uMlrLoqIq9 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 25/04/2017 22:34, Ronald F. Guilmette wrote: >=20 > This is rather embarassing, but OK, I confess... One of my > systems here is running the ancient FreeBSD 9.1 and it hasn't > been upgraded in a long long time. Like not at all. No package > updates, nothing. Today however I desperately need to upgrade > the installed Perl. (Apparently, the Perl that I have installed > on this system, v5.16, has an old and not at all up-to-date Unicode > implementation.) Given how many packages you tend to have that depend on perl, in this situation my advice would be to punt on this system entirely, and build a new 11.0 setup to fulfil the same functions. Even if you have to buy a new hard drive to install the 11.0 system on within the same chassis. > As you all know, fBSD 9.1 used the older package system. I am well and= > truly aware of the fact that, in order to move forward, I will need > to upgrade to the new package system (pkg). So I've been reading this > page that purports to give directions on exactly how to do that: It's not just pkg that you're going to have problems with when running such an old system. The ports tree hasn't supported FreeBSD 9.x since 9.3-RELEASE went out of support at the end of December, and lots of compatibility hacks have since been dyked out. > https://www.freebsd.org/doc/handbook/pkgng-intro.html >=20 > Unfortunately, for me at least, the guidance here raises nearly > as many questions as it answers. For example, it says to do these > two things: >=20 > 1) Run pkg2ng. This converts the existing pkg_tools /var/db/pkg into the package database used by pkg(8) > 2) Put a line like "WITH_PKGNG=3Dyes" into /etc/make.conf This tells the ports to use pkg(8) rather than pkg_tools. I'm not sure if this variable still does anything with a current ports tree -- pkg(8) is assumed nowadays. Even so, both of these steps should be taken before trying to use the ports with pkg(8), but it doesn't really matter what order you do them in= =2E > What it doesn't say is whether the first thing must be done strictly > *before* the second thing, or vise versa, or if the order here even > matters at all. (I don't want to totally screw up my system, so in > the absence of complete clarity, and since I don't really know exactly > what the effects of either of these two steps really are, I am inclined= > to proceed with great caution and thus requast clarification from this > list.) >=20 > Anyway, I decided to look and see if perchance I might already have > the new & improved pkg command on my system. So I did "which pkg" > and lo and behold, an executable with that name is already present > on this system as /usr/sbin/pkg. (I have no clear recollection, one > way or the other, whether or not, in years past, I may have deliberatel= y > installed this /usr/sbin/pkg or not.) /usr/sbin/pkg is pkg(7). It's a small shim that serves to download and install the up-to-date pkg(8). Which isn't going to work, as there isn't a FreeBSD-9.x version of pkg(8) or even a FreeBSD-9.x package repo available today. > Anyway, I decided to throw the dice and run this, with no options or > arguments, just to see if that would give me a list of command line > options or what. I was almost immediately greeted with a message > saying that the new pkg system was *not* in fact actually installed > and asking me ([y/N]) if I wanted to install it. I control-C'd out > of this, before I did any damage, and plotted my next move. >=20 > I realized that to actually install this thing, I'd probably need to be= > root, so I su'd to root and then cd'd to ~root and started "script" so > that I'd have a full log in case anything went wrong... which it > promptly did. Here's the log. It isn't pretty. >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > root@segfault:/root # pkg > The package management tool is not yet installed on your system. > Do you want to fetch and install it now? [y/N]: y > Bootstrapping pkg please wait > Installing pkg-1.9.4_1... > pkg-static: dup2(rootfd): Invalid argument > Extracting pkg-1.9.4_1: 0% > pkg-static: Fail to create /usr: Bad file descriptor > Extracting pkg-1.9.4_1: 100% >=20 > Failed to install the following 1 package(s): /tmp//pkg.txz.q9abRX > root@segfault:/root # exit > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D >=20 > So? NOW what should I do? What you would need to do is build pkg from source via the ports-mgmt/pkg port > Any & all advice appreciated. >=20 > (I still desperately need to get Perl upgraded.) Like I said, in the end you'll find it a lot easier and more productive to start from a fresh install on a blank system and recreate the functionality of your server from scratch. Cheers, Matthew --4xnSkGfFIhISEtfT9qxhNP2uMlrLoqIq9-- --GgXFVnlHoSSaDcNN1u2K2rnUMvp6Lk6gA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZAE0FXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATRL8P/0OU9YMuJcIwlmNUl5+Fonyr jIim0NiEhHFKyMRcOTDuPPcrgPksZswR6h6E3a83uDhigy9Oe6L4qYYZjm7nT+ys oz/V8pdP9QRz/voNUok0XXBmKEeHmaM5+LFClWPlryDy1OtujyagGcS7no9ktQ3y vXrdD15cFtFL3pBe8AgnGad5SymySS+rR7FJ6yQiHcu5KQRmp0h7Z8VeotM88byD 1qc5PvKKkfs346ML6INsNdQwoJ7TRCLGi2ks+tPjHBv++HSl9BJToD1Jejq+GUxN 3MOaHXAZFQN7+4T7ys7RIhaCLUOKuIBoc2SFM4R4TMDlamc0UH699JtJvCJgswYZ oFgDspoHNpFP1TecvCrZyUL4NCW3p8cxYCbOWoYMcgQcSspFE1tue7eHQTfZve2D 4+2eTgiw3bQZDvBtxNQ/QYYeKiGOGSd99XDVtJwOOlmBurMrJPkS3uY9gBSV43UA VTPo70WbQxupi97eFQIEb9/kGyzpUjtT29OUWlx910RHe86CgEIIY9HXGZHt8H17 k2MUMXLZrRxL/1tjDYJXb64yT6UC7fysYz3DREBq7HGrjHdt1SbflU4zbNT6GyEO JW6VCY44tzZ2skt9wt9sD9kbJ2HnOXGcV9kQ8bzcV9UFRXq1japIQgKW24gsAgNJ Ad8iaDGAupHydY6cC7YQ =g45Y -----END PGP SIGNATURE----- --GgXFVnlHoSSaDcNN1u2K2rnUMvp6Lk6gA-- From owner-freebsd-pkg@freebsd.org Wed Apr 26 13:31:37 2017 Return-Path: Delivered-To: freebsd-pkg@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 3559ED5080F for ; Wed, 26 Apr 2017 13:31:37 +0000 (UTC) (envelope-from bugzilla-noreply@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 1EA5BED3 for ; Wed, 26 Apr 2017 13:31:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1E063D5080E; Wed, 26 Apr 2017 13:31:37 +0000 (UTC) Delivered-To: pkg@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 1DB63D5080C for ; Wed, 26 Apr 2017 13:31:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E90FFED1 for ; Wed, 26 Apr 2017 13:31:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v3QDVaNA075810 for ; Wed, 26 Apr 2017 13:31:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 218888] ports-mgmt/pkg: build fails on arm64.aarch64: error: C compiler cannot create executables Date: Wed, 26 Apr 2017 13:31:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ohartmann@walstatt.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: pkg@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2017 13:31:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218888 Bug ID: 218888 Summary: ports-mgmt/pkg: build fails on arm64.aarch64: error: C compiler cannot create executables Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: pkg@FreeBSD.org Reporter: ohartmann@walstatt.org Assignee: pkg@FreeBSD.org Flags: maintainer-feedback?(pkg@FreeBSD.org) Port ports-mgmt/pkg fails to build within a poudriere system with a jail cr= oss compling for arm64.aarch64 in stage configure. The poudriere log reports that configure complains about a non working C compiler which can not produce executables. This initial failing build of pkg renders a complete repository for arm64.aarch64 non-working. The build/poudriere environment is the most recent 12-CURRENT as host (Free= BSD 12.0-CURRENT #16 r317435: Wed Apr 26 10:22:35 CEST 2017 amd64), most recent emulators/qemu_user_static (qemu-user-static-2.8.50.g20170307_2, recompiled today), recent poudriere jail: Jail name: headarm64 Jail version: 12.0-CURRENT Jail arch: arm64.aarch64 Jail method: src=3D/pool/sources/CURRENT/src Jail mount: /pool/poudriere/jails/headarm64 Jail fs: FTAATT/pool/poudriere/jails/headarm64 Jail updated: 2017-04-26 13:12:00 Poudriere version: 3.1.17 Host OSVERSION: 1200030 Jail OSVERSION: 1200030 The error from poudriere: [...] checking whether the C compiler works... no configure: error: in `/wrkdirs/usr/ports/ports-mgmt/pkg/work/pkg-1.10.1': configure: error: C compiler cannot create executables [...] --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-pkg@freebsd.org Wed Apr 26 13:31:36 2017 Return-Path: Delivered-To: freebsd-pkg@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 CB830D50804 for ; Wed, 26 Apr 2017 13:31:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id B588DECF for ; Wed, 26 Apr 2017 13:31:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B4E20D50803; Wed, 26 Apr 2017 13:31:36 +0000 (UTC) Delivered-To: pkg@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 B487FD50802 for ; Wed, 26 Apr 2017 13:31:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A3391ECE for ; Wed, 26 Apr 2017 13:31:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v3QDVaN6075810 for ; Wed, 26 Apr 2017 13:31:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: maintainer-feedback requested: [Bug 218888] ports-mgmt/pkg: build fails on arm64.aarch64: error: C compiler cannot create executables Date: Wed, 26 Apr 2017 13:31:36 +0000 X-Bugzilla-Type: request X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: pkg@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2017 13:31:36 -0000 O. Hartmann has reassigned Bugzilla Automation 's request for maintainer-feedback to pkg@FreeBSD.org: Bug 218888: ports-mgmt/pkg: build fails on arm64.aarch64: error: C compiler cannot create executables https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218888 --- Description --- Port ports-mgmt/pkg fails to build within a poudriere system with a jail cr= oss compling for arm64.aarch64 in stage configure. The poudriere log reports that configure complains about a non working C compiler which can not produce executables. This initial failing build of pkg renders a complete repository for arm64.aarch64 non-working. The build/poudriere environment is the most recent 12-CURRENT as host (Free= BSD 12.0-CURRENT #16 r317435: Wed Apr 26 10:22:35 CEST 2017 amd64), most recent emulators/qemu_user_static (qemu-user-static-2.8.50.g20170307_2, recompiled today), recent poudriere jail: Jail name: headarm64 Jail version: 12.0-CURRENT Jail arch: arm64.aarch64 Jail method: src=3D/pool/sources/CURRENT/src Jail mount: /pool/poudriere/jails/headarm64 Jail fs: FTAATT/pool/poudriere/jails/headarm64 Jail updated: 2017-04-26 13:12:00 Poudriere version: 3.1.17 Host OSVERSION: 1200030 Jail OSVERSION: 1200030 The error from poudriere: [...] checking whether the C compiler works... no configure: error: in `/wrkdirs/usr/ports/ports-mgmt/pkg/work/pkg-1.10.1': configure: error: C compiler cannot create executables [...] From owner-freebsd-pkg@freebsd.org Thu Apr 27 20:35:36 2017 Return-Path: Delivered-To: freebsd-pkg@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 BE7C1D51AB4 for ; Thu, 27 Apr 2017 20:35:36 +0000 (UTC) (envelope-from anatoly@kazanfieldhockey.ru) Received: from kazanfieldhockey.ru (kazanfieldhockey.ru [78.138.152.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "kazanfieldhockey.ru", Issuer "kazanfieldhockey.ru" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 36D0C91E for ; Thu, 27 Apr 2017 20:35:35 +0000 (UTC) (envelope-from anatoly@kazanfieldhockey.ru) Received: from asd2 (host-175-22.static.telecet.ru [87.117.175.22] (may be forged)) (authenticated bits=0) by kazanfieldhockey.ru (8.14.3/8.14.3) with ESMTP id v3RKZJWT099200 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 27 Apr 2017 23:35:23 +0300 (MSK) (envelope-from anatoly@kazanfieldhockey.ru) Date: Thu, 27 Apr 2017 23:35:20 +0300 From: Anatoly To: freebsd-pkg@freebsd.org Subject: Re: Help please... Upgrade to pkg no workie Message-ID: <20170427233520.25251605@asd2> In-Reply-To: <89617edf-9411-2d3e-2f3c-4cab1e530bfd@FreeBSD.org> References: <83939.1493156094@segfault.tristatelogic.com> <89617edf-9411-2d3e-2f3c-4cab1e530bfd@FreeBSD.org> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.2) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2017 20:35:36 -0000 > > This is rather embarassing, but OK, I confess... If you're not exposing vulnerable services to the wild networks, this is not a shame. >One of my > > systems here is running the ancient FreeBSD 9.1 Oldest version I have in production is 5.3 > > > > (I still desperately need to get Perl upgraded.) > > Like I said, in the end you'll find it a lot easier and more > productive to start from a fresh install on a blank system and > recreate the functionality of your server from scratch. > If for some reasons you still don't want to reinstall whole system, you may try to build new perl from source. From owner-freebsd-pkg@freebsd.org Fri Apr 28 04:02:12 2017 Return-Path: Delivered-To: freebsd-pkg@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 7A164D54DC5 for ; Fri, 28 Apr 2017 04:02:12 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 6641CBC for ; Fri, 28 Apr 2017 04:02:11 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id C31A53AE87; Thu, 27 Apr 2017 21:02:05 -0700 (PDT) From: "Ronald F. Guilmette" To: Anatoly cc: freebsd-pkg@freebsd.org Subject: Re: Help please... Upgrade to pkg no workie In-Reply-To: <20170427233520.25251605@asd2> Date: Thu, 27 Apr 2017 21:02:05 -0700 Message-ID: <18908.1493352125@segfault.tristatelogic.com> X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 04:02:12 -0000 In message <20170427233520.25251605@asd2>, Anatoly wrote: >If for some reasons you still don't want to reinstall whole system, you >may try to build new perl from source. Thanks. I found this thing called perlbrew, which allows generating a freah new perl binary quite easily and *without* messing up an existing set of perl binaries and associated libraries. So that *would have been* a solution to the problem that I had *seemed* to be facing. But (sigh) in the end it turned out that I didn't need to upgrade Perl after all. I just needed to upgrade my *understanding* of my Perl program... the one I had built which tried to process some internationalized domain names, but which kept on crashing for rather mysterious resons. I read something that suggested that my Perl might not have the latest and greatest understanding of international character sets, so I figured that that was the problem. But it tuned out that it was just barfing because I had failed to convert input from UTF-8 into Perl's internal representation (of international characters). So, all's well that ends well. But thanks for the suggestions guys. I appreciate it. From owner-freebsd-pkg@freebsd.org Fri Apr 28 11:42:28 2017 Return-Path: Delivered-To: freebsd-pkg@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 CF920D54BE0 for ; Fri, 28 Apr 2017 11:42:28 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: from mail-pg0-x230.google.com (mail-pg0-x230.google.com [IPv6:2607:f8b0:400e:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A28CFC44 for ; Fri, 28 Apr 2017 11:42:28 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: by mail-pg0-x230.google.com with SMTP id v1so13780505pgv.1 for ; Fri, 28 Apr 2017 04:42:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berentweb-com.20150623.gappssmtp.com; s=20150623; h=sender:date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=TH3GWi+yb65bSmHXYYSPBabNRrV/NRoCNE8X9Kh1DBs=; b=TegwUx9XurD3XqN3ZKJCAwqGLZ/vWKqgGsm9euAjORoQY4OiRh5rJwUrj7+8IA062+ HA7tzedgeQ/ZCe6X9K5Va6qRuYovwx2zJc9X1go+86SK6HwSzULqdnxtbZK4DMM5t3sy twlBbhmymLhmyHlWHL5zIRPUYIyBkz4VI/VuMolCRyj+HZt43ERg0h7MYuV2a4uXYzMR x3MljXCLPF/Ti5hEgmuMt78DbU4QiwTXi6GXqp9S+deiyDNQBMksSJVvzRSMlwvbXvjb cRrdulP9snjxArWs92dW/sBUKnS1BmM5GuMlHvQgoOXzq1iAj/RUcyv8dyiu55HI/YRa XJMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:subject:message-id :mime-version:content-transfer-encoding; bh=TH3GWi+yb65bSmHXYYSPBabNRrV/NRoCNE8X9Kh1DBs=; b=pxjZg8z8qkk/9M5G31i8b63nC9SW06c1qItIWXKkLsFT0bKLvUuvqYv+XHP9w9xrFO IvK0vTrZC//3lwEMGZMPKuwY87bHthGrL8BUf1DuLOH8s85fU4jmmadlyDzTZ+WIFVPf Kj6WPI8Vh8VrvUAYWy+Rm38yNpdAzIg5thFx7GJEKanXlLoAWqcoI+bM/TRd9myZvk3W VQiDZiAEHWLtemvmTZ/c4Hs92BLEHltt8VlvC5UziP8J+qj2wE6eZLkpQv8sX2iVz3MF Zk7beDsw5CafjTx83KuFbT/S0KNMAY31FlNXbwYnmJPUfL3zHeJ8zuf/uFK8H/eieClM y2Aw== X-Gm-Message-State: AN3rC/4NJE4bd1ZQdYhn6+DZuKwkn2YRoYghfYOmT7v/p8BkuLXSu/h2 P5IujpHwQXh4cq7r X-Received: by 10.99.131.66 with SMTP id h63mr11390347pge.39.1493379747870; Fri, 28 Apr 2017 04:42:27 -0700 (PDT) Received: from rsbsd ([24.133.238.42]) by smtp.gmail.com with ESMTPSA id g89sm10842116pfk.25.2017.04.28.04.42.24 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 28 Apr 2017 04:42:26 -0700 (PDT) Sender: "Raif S. Berent" Date: Fri, 28 Apr 2017 14:41:50 +0300 From: Beeblebrox To: freebsd-pkg@freebsd.org Subject: poudriere suggestions Message-ID: <20170428144150.4db646cc@rsbsd> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 11:42:28 -0000 Hello. I noticed recently that you guys implemented the "set source-path" option (= -S) for jail creation; thanks a bunch for that tweak. I have some questions about other poudriere functions: * Does poudriere do incremental fetch of source file diffs or does it downl= oad the whole thing from scratch? I seem to remember that it can be increme= ntal? * There's a cache folder under poudriere/data, full of package files but a= ll 3B in size. What's the purpose for this? * Some ports have no option flags and they take extremely long (6+ hours)to= build (prime example is the webkit-gtk2/3 ports). Might there be a "fetch-= only" list in poudriere for such ports? * The build que optimization in poudriere might consider port build length = as a parameter, so that all build jails get full usage. I sometimes see 2 o= r 3 jails idle because poudriere is waiting on an ongoing build, whereas th= e port in question could have been built much sooner in the process but sma= ller ports had been queued. Thanks --=20 FreeBSD_amd64_12-Current_RadeonKMS Please CC my email when responding, mail from list is not delivered. From owner-freebsd-pkg@freebsd.org Fri Apr 28 14:34:59 2017 Return-Path: Delivered-To: freebsd-pkg@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 E80DCD536D6 for ; Fri, 28 Apr 2017 14:34:59 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from h2.pinyon.org (h2.pinyon.org [65.101.20.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BFCD07A0 for ; Fri, 28 Apr 2017 14:34:59 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: by h2.pinyon.org (Postfix, from userid 58) id 088E21708B; Fri, 28 Apr 2017 07:29:13 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1493389753; bh=FGM9QVfYrBnaDdFUhiH9Yev3tSsVHi39w2wjLeuWxPM=; h=Subject:To:References:From:Date:In-Reply-To; b=nT7cWUbwbuhkXDNk1x9Qrr8kEVguBH6uJ5LNssgoHAK7RZ60JVNFcYs07opZ/ZhMH 2t6z8oHEuvLNN32gaGiY3JvCk+gTqrDwBBNfptNqC+VaSzS8RY/Jy0eT/U6yhs1mVQ y6+mtOo0aDQq8yzwzvxKIiinaoNQBzfvfE7MLWEY= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on h2.n1.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from [10.0.10.15] (h1.pinyon.org [65.101.20.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by h2.pinyon.org (Postfix) with ESMTPSA id 20C701706B for ; Fri, 28 Apr 2017 07:29:12 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1493389752; bh=FGM9QVfYrBnaDdFUhiH9Yev3tSsVHi39w2wjLeuWxPM=; h=Subject:To:References:From:Date:In-Reply-To; b=fvkfTrNiyLj5p1eSVOm69Im6WlaifXWbxJctjRWQNPdFeMpWAUt9LC692hYXa1d+B ggRL4OVkiKDtYbBYNSJaw+LzD8SO6qBtGs1bcTJ/UBC/FHlGVevD40jzWg82KQ3B/w svl3o49JwTXjt5k+MmQrgMTl50Y+6tCnabFt52UQ= Subject: Re: poudriere suggestions To: freebsd-pkg@freebsd.org References: <20170428144150.4db646cc@rsbsd> From: "Russell L. Carter" Message-ID: Date: Fri, 28 Apr 2017 07:29:11 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <20170428144150.4db646cc@rsbsd> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 14:35:00 -0000 On 04/28/17 04:41, Beeblebrox via freebsd-pkg wrote: > Hello. [...] > * The build que optimization in poudriere might consider port build > length as a parameter, so that all build jails get full usage. I > sometimes see 2 or 3 jails idle because poudriere is waiting on an > ongoing build, whereas the port in question could have been built > much sooner in the process but smaller ports had been queued. There is a tension between the (mostly) single-threaded ports and the monsters like libreoffice, chromium, webkit-*, firefox, and llvm*. I recently built up a (used) dual E5-2650 (32 threads) w/ 128GB of RAM to study the problem because my FX-8300 (8 threads) w/ 32GB of RAM was starting to take regularly more than 8 hrs w/ e.g. PARALLEL_JOBS=4 and MAKE_JOBS_NUMBER=3. Any higher parallelism and the build runs out of swap (standard 2GB) and takes forever. However, that configuration leaves lots and lots of space waiting, similar to what you have observed. With a few overnights in on the new box I am now running PARALLEL_JOBS=6, MAKE_JOBS_NUMBER=7, w/ build times (not repeatable workloads, nature of the beast) around 4 hours. Still, I see lots of idle in the beginning stages (mostly single-threaded) and chromium trudges along with 7 cores for a long time at the end. For throughput to improve, MAKE_JOBS_NUMBER and PARALLEL_JOBS need to be a bit smarter. I think a worthy experiment might be to dynamically generate MAKE_JOBS_NUMBER like so: MAKE_JOBS_NUMBER(current scheduling step) = NCORES - CURRENT_ACTIVE_NJOBS(single threaded) - CURRENT_ACTIVE_NJOBS(multi threaded) * MAKE_JOBS_NUMBER(previous scheduling step) Even this has problems though; chromium could get launched with just a thread or two, and then the waiting would begin. But it's a start. It's a fun, and not easy to solve problem. Optimal dynamic bin packing. I suspect google has spent a lot of time working on it... The HPC crowd have been working on it for 40 years. Russell > Thanks > From owner-freebsd-pkg@freebsd.org Fri Apr 28 19:11:09 2017 Return-Path: Delivered-To: freebsd-pkg@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 D398BD543BE for ; Fri, 28 Apr 2017 19:11:09 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 3B696102E for ; Fri, 28 Apr 2017 19:11:08 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Fri, 28 Apr 2017 21:09:56 +0200 Authentication-Results: connect.ultra-secure.de; iprev=temperror; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id 30C9A93B-DFDC-4A39-B412-B638B2213FC2.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Fri, 28 Apr 2017 21:09:54 +0200 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: poudriere suggestions From: Rainer Duffner In-Reply-To: Date: Fri, 28 Apr 2017 21:09:51 +0200 Cc: freebsd-pkg@freebsd.org Message-Id: <4E32A700-BD92-4BF1-A0C4-A7269123A827@ultra-secure.de> References: <20170428144150.4db646cc@rsbsd> To: "Russell L. Carter" X-Mailer: Apple Mail (2.3124) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=14 total_conn=1 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 2881, bad: 1, connections: 3285, history: 2880, asn_score: 422, asn_connections: 430, asn_good: 422, asn_bad: 0, pass:asn, asn_all_good, relaying Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 19:11:10 -0000 > Am 28.04.2017 um 16:29 schrieb Russell L. Carter : >=20 > There is a tension between the (mostly) single-threaded ports and > the monsters like libreoffice, chromium, webkit-*, firefox, and > llvm*.=20 So, it=E2=80=99s not possible to speed up the build of libreoffice by = parallelizing it? I only build a 2000-ish subset of ports - and libreoffice (together with = webkit-gtk2) takes more time than anything else. Or rather, these take more time than the rest, combined. I=E2=80=99ve got a 2x6 core Xeon and 64GB RAM.=20= From owner-freebsd-pkg@freebsd.org Fri Apr 28 20:10:25 2017 Return-Path: Delivered-To: freebsd-pkg@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 A940CD54855 for ; Fri, 28 Apr 2017 20:10:25 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from h2.pinyon.org (h2.pinyon.org [65.101.20.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 66E9DF1C for ; Fri, 28 Apr 2017 20:10:24 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: by h2.pinyon.org (Postfix, from userid 58) id 7419417945; Fri, 28 Apr 2017 13:10:23 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1493410223; bh=Jz8KF7vEU6c0GVtSYfIBZAW9fQ6QRilOp9foOubjV2Y=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=T7AXB7GCgIYcerrE8l9MojU4FqeJXVSAzjPJNMNzlQ45GHMX/D+06FK3SNc2GguCC eJ6EFQM0VVlTJzjEhCKDKVx61KOXIs8uIdvi0mjOX3/sSWyYu4DxPvWaLqgbqElVPN ude9xH3I2/eoiNaNLDjUB5bTTTJaovjQhKL2xy30= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on h2.n1.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=unavailable autolearn_force=no version=3.4.1 Received: from [10.0.10.15] (h1.pinyon.org [65.101.20.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by h2.pinyon.org (Postfix) with ESMTPSA id 2DB2417918; Fri, 28 Apr 2017 13:10:22 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1493410222; bh=Jz8KF7vEU6c0GVtSYfIBZAW9fQ6QRilOp9foOubjV2Y=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=fW8hVFwQ/nllbl7rbw6Em8UUb82zQbSBs6SYxBhbOFwbKTN9h5nRgfwK9fCEu25w5 26ydwkvHRrH7qKLO5vaEYjLbsPJNRlUxNzFPLwPJihFuE2S7ezzOSjNCZ/pfvgLi1w /eo3l890NcooM/45wrwjrkdXm1DOWkFPlEeDR1HE= Subject: Re: poudriere suggestions To: Rainer Duffner Cc: freebsd-pkg@freebsd.org References: <20170428144150.4db646cc@rsbsd> <4E32A700-BD92-4BF1-A0C4-A7269123A827@ultra-secure.de> From: "Russell L. Carter" Message-ID: <71a8cb99-6c1e-d552-43e2-34b2f1dcd3b3@pinyon.org> Date: Fri, 28 Apr 2017 13:10:21 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <4E32A700-BD92-4BF1-A0C4-A7269123A827@ultra-secure.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 20:10:25 -0000 On 04/28/17 12:09, Rainer Duffner wrote: > >> Am 28.04.2017 um 16:29 schrieb Russell L. Carter > >: >> >> There is a tension between the (mostly) single-threaded ports and >> the monsters like libreoffice, chromium, webkit-*, firefox, and >> llvm*. > > > So, it’s not possible to speed up the build of libreoffice by > parallelizing it? I must have not been clear. The "monsters" (so to speak), are fully parallelizable, but if you set PARALLEL_JOBS to a high number (e.g. the number of cores/threads) and also set MAKE_JOBS_NUMBER in poudriere.d/make.conf to a high number (e.g. the number of cores/threads), then you might end up with a portion of the build scheduling MAKE_JOBS_NUMBER*PARALLEL_JOBS cores/threads. That will bring many systems to their knees. So for instance, via a lot of observation, I've found that PARALLEL_JOBS=6, MAKE_JOBS_NUMBER=7 works best for my 32 thread Xeons. This has the disadvantage that when running a lot of single threaded jobs through only PARALLEL_JOBS number of threads are active, but I keep the peak load down far enough that the big multithreaded jobs minimize thrashing and maximize efficiency. Similarly, if at the end of the poudriere bulk build there are 2 long running jobs, it does not matter that PARALLEL_JOBS is set higher; you will only get 2*MAKE_JOBS_NUMBER available threads working on the those two jobs (and nothing else will run, everything else is complete). So I see a lot of either 7 or 2*7 load average for up to a couple of hours on my 32 thread box. Suboptimal. I would like to get hard numbers on this but that would be a really big effort given the computational effort in a 4-8 hr poudriere run. What eventually needs to happen is that MAKE_JOBS_NUMBER changes according to the current number of buildable JOBS and the available cores/threads (which is a function of the current working set of jobs at the time of scheduling this job). This will require reservations and priorities and tracking the current thread demand, but I suppose that's a long way off yet. HPC schedulers do this. It turns out this is a supercomputer problem, kinda cool. > I only build a 2000-ish subset of ports - and libreoffice (together with > webkit-gtk2) takes more time than anything else. > Or rather, these take more time than the rest, combined. I've got a similar number subset, but it seems to be chromium that's the real time sink. > > I’ve got a 2x6 core Xeon and 64GB RAM. hth, Russell