From owner-freebsd-pkg@FreeBSD.ORG Sun Nov 24 20:16:01 2013 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 922D64B3; Sun, 24 Nov 2013 20:16:01 +0000 (UTC) Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E709A2387; Sun, 24 Nov 2013 20:16:00 +0000 (UTC) Received: by mail-lb0-f178.google.com with SMTP id c11so2527733lbj.37 for ; Sun, 24 Nov 2013 12:15:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xjnxrOq9ybi50F1x+Xx7ggES7/Fib3ZA/2ai0a2BROc=; b=ZfS6A3umwfFRzDaN0kERLG55ZD9AZDYkl53LR4c0eNWigHYgaACSGzwkzGDHuYIhzR hHWULkICPDBoP+DVs2Yba0gqdGZ0nhSRI5IV50rr63n8g5i9lp8Z69qYR0AekVY2Qllo mlSPZBISK/BAybVIXgm4ZakAfSUPfRjApzyUtqtFUqJylkbZk3fTtt5fDli+DxhPMdgH oLsBlSXF4YDH625Wbp0ZcaGgzYwqvXftO8Nm4hOJKZ/4D5qocMMyqhuCqpbEERACsRMo OVBaDyvWRZDhsIX4Psy/Xw0CZqukYhXXmjHshaJ91V6QbXPTVw0XEBSc/t48ZQTYlDob sONQ== MIME-Version: 1.0 X-Received: by 10.112.171.228 with SMTP id ax4mr18705604lbc.6.1385324158820; Sun, 24 Nov 2013 12:15:58 -0800 (PST) Received: by 10.112.140.132 with HTTP; Sun, 24 Nov 2013 12:15:58 -0800 (PST) In-Reply-To: <3C7FDCC66C27FB5606ABC454@atuin.in.mat.cc> References: <3C7FDCC66C27FB5606ABC454@atuin.in.mat.cc> Date: Sun, 24 Nov 2013 21:15:58 +0100 Message-ID: Subject: Re: Few missing packages from the new PKG repositories From: Daniel Nebdal To: Mathieu Arnold Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.16 Cc: freebsd Ports , freebsd-pkg@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.16 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, 24 Nov 2013 20:16:01 -0000 On Sat, Nov 23, 2013 at 11:34 PM, Mathieu Arnold wrote: > +--On 23 novembre 2013 16:27:12 +0200 Kimmo Paasiala > wrote: > | Were these left out by accident or why aren=92t they included? > | > | - x11/gnome2, x11/gnome2-lite is in the repo. > | > | - editors/vim, editors/vim-lite is in the repo as well. > > The packages are built from the ports tree as it is at 1 UTC every > Wednesday, so, if something is broken at that time, like openjpeg was (my > fault) many dependencies are not included. You'll have to wait for next > week. > > -- > Mathieu Arnold > > Right, I guessed it was something like that - thanks. --=20 Daniel Nebdal From owner-freebsd-pkg@FreeBSD.ORG Sun Nov 24 20:51:18 2013 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3DC2DE14 for ; Sun, 24 Nov 2013 20:51:18 +0000 (UTC) Received: from nm1-vm1.bullet.mail.bf1.yahoo.com (nm1-vm1.bullet.mail.bf1.yahoo.com [98.139.213.163]) by mx1.freebsd.org (Postfix) with SMTP id B8A9F2513 for ; Sun, 24 Nov 2013 20:51:17 +0000 (UTC) Received: from [98.139.215.143] by nm1.bullet.mail.bf1.yahoo.com with NNFMP; 24 Nov 2013 20:48:00 -0000 Received: from [98.139.213.12] by tm14.bullet.mail.bf1.yahoo.com with NNFMP; 24 Nov 2013 20:48:00 -0000 Received: from [127.0.0.1] by smtp112.mail.bf1.yahoo.com with NNFMP; 24 Nov 2013 20:48:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1385326080; bh=Bg1iUzrH16vNJkaSPVNgonVUD3zZ2cPzMPiJl5Z3Nok=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Subject:From:Reply-To:To:Content-Type:Date:Message-ID:Mime-Version:X-Mailer; b=IRPPdo0cRBOuRSS+ZNJosvWQTZqHOxTmCHgipA+i68/IfQUM0sAEuk5IEDUvQJPrXrd/nhx87OoylWLERtgfdm38poDrFwa6fE/w1gt1yk6AX1mUVNuLSChQDubEYJl17iEY9VFYVU0A72rsmtSGyktLyTpd/tog6vqPKTNvAfw= X-Yahoo-Newman-Id: 859175.15585.bm@smtp112.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: moiE6hwVM1lwxQqoaPyShtBw24mrX4ru7PEybzfT73tIeKV q0cOqDuaj9mWPSrqnSG97rb0t_a0emBSRxE0k7xwt7s9N2puVsKPR0BBxgd4 3_54No6aCrylvq_XYV0.r6MMxHvVGffZlII7mMeRIZxSyyZ4hiERwCO5dXdE 8f7hRNlettHloPEFBRW0HOEk22n9fuBj.MnsEpc.0HI5KSxkJbOsGZQ1JLHK 9X1HXJFqB6gcMX63F5QXBWpZaaeXPMLCXw__qnk1sqQKnqQZXb_51SfgmaWk cRlZIxuwgrQAA3qNPcVZtLHCL8rafGH57xO6L9KZOS4_5kEZzcxnQkR1jL69 fa937BqMN5VQS0uoapdzOU7QTFwmtFddwx8HVIdJSzTEb_9L1y1lgT23AgIA rHHKVJx6GIWOvdR.syrCHdcRmU8zNR.DRBiytP8iYF9XXKuJiNrV6wmDQuhN _hS.g7Fcgys5OxX9Y0WkJDZ6vM2SmTJf.mzbcWn6vETXcCKI2bX2.rTLF3zC tBBwtRqPUSsWcjG92vf9YB2wrKoZg.ibZ_I0ZkGd_AxH7tp.qhkyZ X-Yahoo-SMTP: u5BKR6OswBC_iZJVfGRoMkTIpc8pEA4- X-Rocket-Received: from [192.168.100.228] (sean_bruno@24.23.220.111 with ) by smtp112.mail.bf1.yahoo.com with SMTP; 24 Nov 2013 12:48:00 -0800 PST Subject: i386/amd64 coexistence From: Sean Bruno To: freebsd-pkg@freebsd.org Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-Pile1Eu85mNiyEAqCUET" Date: Sun, 24 Nov 2013 12:47:58 -0800 Message-ID: <1385326078.47935.24.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: sbruno@freebsd.org List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Nov 2013 20:51:18 -0000 --=-Pile1Eu85mNiyEAqCUET Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'm trying to understand two things simultaneously. 1. How to build a useable emulators/wine with poudriere. I *think* I have to build this in an i386 jail for this and it does build there. I keep being pointed at i386-wine though, so I'm very confused as to what am I supposed to use here. 2. How to maintain and use an i386 & amd64 repo locally on my machine. If I need to use a i386 pkg repo locally, how do I innstall from it if my machine is amd64? I'm super happy with poudriere thus far and am looking to figure out how to install from a second repo if I want to. Currently, my pkg.conf defines: PACKAGESITE : file:///usr/local/poudriere/data/packages/11amd64-default --=-Pile1Eu85mNiyEAqCUET Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (FreeBSD) iQEcBAABAgAGBQJSkmX1AAoJEBkJRdwI6BaHL00H+gMYNgw5p0wZ/b7r0YwE1qNt z1v+9tvYkSgz225obpUuwHt7agoqxQbaSEnxL4pV+EJMRXWMucDL49uR8Gva9VOH 0425GOB8KzqUQNL7B8iyFCiseFzxvQlRpPEcq2wRZIwVaDueY8Y60rzAHUoVl8CY gLa7Rv5TAGczy/Hz7j9+Lc2r/lVElbE2odHpxV59SOqw6wg8joPstCf5iVSsND6m V20umpbpQ5K67Q9dRsZArPNMqBSzLrRKyOm9Ve9Fec7yA7Yao1tkKcAfFkO/AAUv PCDR/XyP08KlJamRyGi1QWq+nh7cNMKl4iJPDi0tlIWWVumbpkiJkaLc664MmnU= =EWP7 -----END PGP SIGNATURE----- --=-Pile1Eu85mNiyEAqCUET-- From owner-freebsd-pkg@FreeBSD.ORG Mon Nov 25 15:13:17 2013 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7E369E2; Mon, 25 Nov 2013 15:13:17 +0000 (UTC) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7349920C4; Mon, 25 Nov 2013 15:13:16 +0000 (UTC) Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 099572148B; Mon, 25 Nov 2013 10:13:15 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Mon, 25 Nov 2013 10:13:15 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=Zaa Am11IcTF4lliRnMeGwcBb3tg=; b=qCCd+3oQJzDwQPKxrrUezBqbh5IEuIgJCzw t+QbuflLOHHPmxzIn7PNMIpj5kKDgf995HYI73IG4iKUo5aYiG/GVajVptsctwBj dUHNyXNmlWNWbRM1pG2yQqc2BxleEdPY/7ILGDpW+5KjxosbU8aPzRdWZfUhjIPB gBmRH7p4= X-Sasl-enc: ze0jmPBBMWKCLSurYk3fwIjLKSMTDGS0N2s1N0n+OVhc 1385392394 Received: from [172.16.1.145] (unknown [68.117.126.78]) by mail.messagingengine.com (Postfix) with ESMTPA id 7686D680096; Mon, 25 Nov 2013 10:13:14 -0500 (EST) Content-Type: multipart/signed; boundary="Apple-Mail=_A05C6D5A-E4BC-4EF4-9A10-A170EAD0FE39"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) Subject: Re: i386/amd64 coexistence From: Mark Felder In-Reply-To: <1385326078.47935.24.camel@powernoodle.corp.yahoo.com> Date: Mon, 25 Nov 2013 09:13:13 -0600 Message-Id: <255FFBC1-421D-4A2C-8838-D64D38293F54@FreeBSD.org> References: <1385326078.47935.24.camel@powernoodle.corp.yahoo.com> To: sbruno@freebsd.org X-Mailer: Apple Mail (2.1822) Cc: freebsd-pkg@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.16 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: Mon, 25 Nov 2013 15:13:17 -0000 --Apple-Mail=_A05C6D5A-E4BC-4EF4-9A10-A170EAD0FE39 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Nov 24, 2013, at 14:47, Sean Bruno wrote: > I'm trying to understand two things simultaneously. >=20 > 1. How to build a useable emulators/wine with poudriere. > I *think* I have to build this in an i386 jail for this and it does > build there. I keep being pointed at i386-wine though, so I'm very > confused as to what am I supposed to use here. >=20 What we currently have in ports (i386-wine) is a precompiled package for = amd64. Building it requires a 32bit chroot or jail and then packaging up = not only wine but all of its 32bit dependencies. It is very tedious and = the guy who is doing it has it down to a science. We can=92t really = build this in poudriere as the resulting package will be 32bit and you = won=92t be able to install it on amd64 because pkg will notice the arch = difference. > 2. How to maintain and use an i386 & amd64 repo locally on my = machine. > If I need to use a i386 pkg repo locally, how do I innstall from it if > my machine is amd64? I'm super happy with poudriere thus far and am > looking to figure out how to install from a second repo if I want to. > Currently, my pkg.conf defines: >=20 > PACKAGESITE : > file:///usr/local/poudriere/data/packages/11amd64-default You can use multiple repos, but I don=92t think you will be able to use = a different architecture. If you want to use multiple repos, however, you should also move to the = new pkg configuration format: /usr/local/etc/pkg/repos/*.conf You can put all of your repos into their own config files. Format looks = like this: FreeBSD: { url: "http://pkg.FreeBSD.org/${ABI}/latest=94, mirror_type: "srv=94, enabled: yes } --Apple-Mail=_A05C6D5A-E4BC-4EF4-9A10-A170EAD0FE39 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJSk2kJAAoJEJg7ZFAfE+JSf8oH/2C4aKthoSkBRwIXXI98+K7+ Yqr653MV8a/E7aq278VAJeSYMGKWKite1YiOWxR9DtYD1x4i6gGkHUrrreLWrWYE y0KayO0oZrFQuW8TXY6LC8BGFSlAqBtBDjOq6bF/bPVgaKJ5Ml8TlGRajTWfDCux ev2OEUeZmXpyA5lAJtnVreD3iklKdH6Y2GyUxprZIjr2Wwg0Rhk969SKaQ2bPMYu eSl3fCvlwjWPW/mFRnB9xobUViamZe1+2zCJkW1KnLuG3yzRlg3Dp43+YLD/KasS 72A7Ai+3jCaCWEpOCPc/khyiPVvqqUiJaix2WQEDmGcXKKssUxfHtisXL/2hkh8= =To3K -----END PGP SIGNATURE----- --Apple-Mail=_A05C6D5A-E4BC-4EF4-9A10-A170EAD0FE39-- From owner-freebsd-pkg@FreeBSD.ORG Wed Nov 27 03:43:21 2013 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1B5EED59 for ; Wed, 27 Nov 2013 03:43:21 +0000 (UTC) Received: from st11p09mm-asmtp001.mac.com (st11p09mm-asmtp001.mac.com [17.164.24.96]) by mx1.freebsd.org (Postfix) with ESMTP id E84F323CE for ; Wed, 27 Nov 2013 03:43:20 +0000 (UTC) Received: from [10.71.14.10] (dsl-hkibrasgw2-58c360-195.dhcp.inet.fi [88.195.96.195]) by st11p09mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0MWW00E4OKZZ6U50@st11p09mm-asmtp001.mac.com> for freebsd-pkg@freebsd.org; Wed, 27 Nov 2013 03:43:13 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.72,1.0.14,0.0.0000 definitions=2013-11-27_02:2013-11-26,2013-11-27,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=5 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1308280000 definitions=main-1311260229 From: Kimmo Paasiala Content-type: multipart/signed; boundary="Apple-Mail=_6600FF0D-9B6F-4066-959C-9EBE19DB90D6"; protocol="application/pgp-signature"; micalg=pgp-sha512 Subject: Pkg 1.2 and port options? Message-id: <49AA9D9E-6EB7-47E1-A40D-9A3E15A6A761@icloud.com> Date: Wed, 27 Nov 2013 05:43:02 +0200 To: freebsd-pkg@freebsd.org MIME-version: 1.0 (Mac OS X Mail 7.0 \(1822\)) X-Mailer: Apple Mail (2.1822) X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.16 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, 27 Nov 2013 03:43:21 -0000 --Apple-Mail=_6600FF0D-9B6F-4066-959C-9EBE19DB90D6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Where did the options go? pkg query -e "%n=3Dpython27" "%n-%v %Ok %Ov=94 produces no output and = pkg info -R python27 shows no =93options=94 -section in the package. -Kimmo --Apple-Mail=_6600FF0D-9B6F-4066-959C-9EBE19DB90D6 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJSlWpNAAoJEFvLZC0FWRVpHi4H+gJQoX7do3B7QjsDRE6Mn3nq PV6YzzNSxIinlCGi0+b1RzWcKbMDQuHmjba82W4W2s54TKLklU0TGLGkaLu1OYeE sSm4g8Z/vdV6TafquzNcmb2AdBbXCgkMIbhL6vQoZIYHal7g0qU0XzYnt6eoph6w ebZpQYI1nd5ROltXAwSoZ8h5jztWYLnOtnDF+aLhTtCeXKECLhUNN5Pi2A9GverA 8+j2ihCCYQCtODCF5Yi48/nQDfQN3Khdlz93nYpXWACbBkppMvdhWiz6wFKegElC vb+U9ime+1XU+jjWXuyendfL6ZkUX4rP6oY23NzpnJjJ/UVVpz04qCRcoFLVLnA= =JU5P -----END PGP SIGNATURE----- --Apple-Mail=_6600FF0D-9B6F-4066-959C-9EBE19DB90D6-- From owner-freebsd-pkg@FreeBSD.ORG Wed Nov 27 15:22:18 2013 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9BFB149A for ; Wed, 27 Nov 2013 15:22:18 +0000 (UTC) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 45EEF2675 for ; Wed, 27 Nov 2013 15:22:16 +0000 (UTC) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 4955FBDC5D; Wed, 27 Nov 2013 16:22:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=mat.cc; h=date:from:to :subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=plouf; bh=C146CxSm5av HlWBk0BAZMDMfYP4=; b=1H7LVhhRBwDYwxJ0CEfT2mDoIlmmFNMjjxk6vxfDrye 3/VdPr5ooxC3IymxPs9QUIIUw3hTwKVltGYwCeu/7gC2ED4jlHgd14MYXYSwpuhR /OEeU0oy4ysV8e2U0BpLbv1Ak2ohYKFvSY7rYRv7iOjVOSuMHhR+vUPptDMkPpHQ = Received: from gw.in.absolight.net (gw-ecl.in.absolight.net [79.143.241.69]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "gw.in.absolight.net", Issuer "CA Cert Signing Authority" (not verified)) by prod2.absolight.net (Postfix) with ESMTPSA id 4257ABDC1D; Wed, 27 Nov 2013 16:22:14 +0100 (CET) Received: from ogg.in.absolight.net (ogg.in.absolight.net [79.143.241.239]) by gw.in.absolight.net (Postfix) with ESMTP id F267D6153; Wed, 27 Nov 2013 16:22:13 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by ogg.in.absolight.net (Postfix) with ESMTP id E98A865082E8; Wed, 27 Nov 2013 16:22:13 +0100 (CET) Date: Wed, 27 Nov 2013 16:22:13 +0100 From: Mathieu Arnold To: Kimmo Paasiala , freebsd-pkg@freebsd.org Subject: Re: Pkg 1.2 and port options? Message-ID: <55D62A1A188DB3529810B86E@ogg.in.absolight.net> In-Reply-To: <49AA9D9E-6EB7-47E1-A40D-9A3E15A6A761@icloud.com> References: <49AA9D9E-6EB7-47E1-A40D-9A3E15A6A761@icloud.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.16 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, 27 Nov 2013 15:22:18 -0000 +--On 27 novembre 2013 05:43:02 +0200 Kimmo Paasiala wrote: | Where did the options go? |=20 | pkg query -e "%n=3Dpython27" "%n-%v %Ok %Ov=E2=80=9D produces no output = and pkg | info -R python27 shows no =E2=80=9Coptions=E2=80=9D -section in the = package. Yes, it is, amongst other things, do wait for 1.2.1 :-) --=20 Mathieu Arnold From owner-freebsd-pkg@FreeBSD.ORG Fri Nov 29 11:30:12 2013 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EC8EF47B for ; Fri, 29 Nov 2013 11:30:11 +0000 (UTC) Received: from eu1sys200aog121.obsmtp.com (eu1sys200aog121.obsmtp.com [207.126.144.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 48CB51FCB for ; Fri, 29 Nov 2013 11:30:10 +0000 (UTC) Received: from mail-we0-f177.google.com ([74.125.82.177]) (using TLSv1) by eu1sys200aob121.postini.com ([207.126.147.11]) with SMTP ID DSNKUph6u9ZLZhqXhTz4JHLZgjL+AY2iYBPy@postini.com; Fri, 29 Nov 2013 11:30:11 UTC Received: by mail-we0-f177.google.com with SMTP id p61so9101609wes.22 for ; Fri, 29 Nov 2013 03:30:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:message-id:to:subject:reply-to; bh=4s58t+0piWDgtkTJHVJra57gZJBxDs4Wjv5zV6cy2go=; b=AhalbirKT7aBwQCfMgjR3UeDpRDUOyFgWtyglNsVPLLKH6CenPzT3XUdOWzuJ+3CO8 ztqOSKPLGqbGZPMSmiBlGpYUwo3ZASTD7fwiG+nZZBESTM4hW4Dzvb9sBxL55kF1pqnY bhSuVsU4swq7WNvcMXG1GplNIji+27/niLpwbgSntDhA3gPealB7MlQG0p4R5B0KnSmI 5k5me2tMj+vSQh5QQ0YLF2bJJ9HXGQijlcUs2ZD0cSVDW8c0xv3ji0lKHme9K5rGwmFS HUhsdnMcjMjVCh0EXvVk+i5+DWgsZBqkvBaFvlJ2uSupCCQQorLju54tlfrchBoWGTWD tIdQ== X-Received: by 10.180.108.132 with SMTP id hk4mr6367802wib.12.1385723033547; Fri, 29 Nov 2013 03:03:53 -0800 (PST) X-Gm-Message-State: ALoCoQmBrmXZrOdKxo2Jm2Ajs9hW+CctdxwNlzlHjBLaF/rapfNgdIGeQNJGupZXBPyTxH+rjmlEuEtcUrTRoFDxUvQBMetbqKfivLkXttnvI+uXUg7/9hDK562bcHTqV44L3SR9E4IxDm75O10jAvSQc6tHsdohVIEldpeDdvVCWzBXN13h8cg= X-Received: by 10.180.108.132 with SMTP id hk4mr6367770wib.12.1385723033189; Fri, 29 Nov 2013 03:03:53 -0800 (PST) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id dj8sm91088710wid.2.2013.11.29.03.03.51 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Nov 2013 03:03:52 -0800 (PST) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id rATB3ooO078490 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 29 Nov 2013 11:03:50 GMT (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id rATB3obl078489 for freebsd-pkg@freebsd.org; Fri, 29 Nov 2013 11:03:50 GMT (envelope-from mexas) Date: Fri, 29 Nov 2013 03:03:52 -0800 (PST) From: Anton Shterenlikht Message-Id: <201311291103.rATB3obl078489@mech-cluster241.men.bris.ac.uk> To: freebsd-pkg@freebsd.org Subject: v 1.2.1 - config confusion X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: mexas@bris.ac.uk List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Nov 2013 11:30:12 -0000 pkg is a great tool! Many thanks to all developers. However, the pace of development is so fast, I can't keep up. And, it seems, the documentation is a bit behind too. I've seen some posts in ports@ about configuring pkg 1.2.1, but I'm still not clear. Is seems pkg.conf(5) man page is out of date. It still says PACKAGESITE should be in this file, which is now obsolete. https://wiki.freebsd.org/pkgng is more up-to-date. Still: 2. Remove any repository-specific configuration from /usr/local/etc/pkg.conf, such as PACKAGESITE, MIRROR_TYPE, PUBKEY. If this leaves your pkg.conf empty, just remove it. 3. mkdir -p /usr/local/etc/pkg/repos 4. Create the file /usr/local/etc/pkg/repos/FreeBSD.conf with: FreeBSD: { url: "http://pkg.FreeBSD.org/${ABI}/latest", mirror_type: "srv", enabled: yes } So where does PUBKEY goes now? What is the meaning of FreeBSD identifier? Can I give it another name? pkg-repo(8) says SIGNATURE_TYPE should be set to FINGERPRINTS. Should this also appear in /usr/local/etc/pkg/repos/FreeBSD.conf? And so on... I'm on ia64, so I have to build my own packages. Please provide an up-to-date guide on the transition from version 1.1 to 1.2. Again, thank you for a great too! Many thanks Anton From owner-freebsd-pkg@FreeBSD.ORG Fri Nov 29 21:40:28 2013 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4F2E4C9D for ; Fri, 29 Nov 2013 21:40:28 +0000 (UTC) Received: from kaworu.ch (kaworu.ch [IPv6:2001:41d0:1:5db0::1]) by mx1.freebsd.org (Postfix) with ESMTP id 1792610EC for ; Fri, 29 Nov 2013 21:40:26 +0000 (UTC) Received: from [192.168.0.18] (46-126-186-69.dynamic.hispeed.ch [46.126.186.69]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: alex@kaworu.ch) by kaworu.ch (Postfix) with ESMTPSA id 98C6C89422 for ; Fri, 29 Nov 2013 22:38:34 +0100 (CET) Message-ID: <529909B9.2050007@kaworu.ch> Date: Fri, 29 Nov 2013 22:40:09 +0100 From: Alex User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-pkg@freebsd.org Subject: [dev] about unchecked functions calls X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.16 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, 29 Nov 2013 21:40:28 -0000 Hi list, We do have currently several libc function calls that are completely unchecked. Amongst them, the malloc(3) family calls are almost always assumed to succeed and I am feeling uneasy about it. To be honest, I've never experienced genuine ENOMEM as a programmer. What makes me uneasy is that I personally think that when writting C, one has to take a stand on some question like "what do I do if malloc(3) ever fail?". UNIX as a strong tradition about robust C programming and we should embrace it. About solutions, the alternatives I have in mind are: 1. assume that ENOMEM is fatal. We just abort() as soon as we see it. In that case we should have some kind of xmalloc(3) & Co. and use them consistently accross all the project. On the pros side it's very easy to do, on the cons it could leave the system in a unclean state (half done install / uninstall, corrupted pkg database etc.). 2. assume that pkg should fail gracefully when ENOMEM occurs. In general it is considered bad design for a library to abort() (in any case) and so if part of pkg can be considered as a library (like libpkg suggest by its name) then maybe this is the Right Thing™ to do. Basically, it means that functions considered part of the library would return an error code (EPKG_FATAL) while other "higher part" would gracefully cleanup and exit (using for example err(3)). On the pros side we would have a more robust application, a more reliable library and a cleaner codebase. On the cons side it is hard to achieve and time consuming. To me, (1) is better that what we do now (i.e. nothing) and (2) is better than (1). Obviously, (1) can be achieved easily while (2) is a long process. I've been playing Coccinelle[1] on the pkg codebase recently (long story short: Coccinelle is a matching and transformation engine for C). What is relevant to know is that Coccinelle is a great tool to achieve (1), and that I am willing to integrate it. In other words we have a way to step quickly to (1). My proposition is to use Coccinelle in order to step to a first goal (1) and achieve (2) as a second, long-term and shared goal. If at anytime (2) seems unreasonable, we can still drop it and fallback to (1). It is much more a change of mindset than a change in the code. It's about writting cleaner, hopefully more robust code. I think that the two steps could (and should) also be applied for other other calls like strlcpy(3). However, in order to succeed cooperation is required at every levels (all the contributors should try to comply to it and commiters should enforce it). Therefore comments and inputs are welcome, in particular from current active pkg commiters. Regards, Alex. [1]: http://coccinelle.lip6.fr/ From owner-freebsd-pkg@FreeBSD.ORG Sat Nov 30 10:02:36 2013 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0FE5EC2F for ; Sat, 30 Nov 2013 10:02:36 +0000 (UTC) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8B7461705 for ; Sat, 30 Nov 2013 10:02:35 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.2.117.99]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.7/8.14.7) with ESMTP id rAUA2Tx7051426 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sat, 30 Nov 2013 10:02:29 GMT (envelope-from m.seaman@infracaninophile.co.uk) DKIM-Filter: OpenDKIM Filter v2.8.3 smtp.infracaninophile.co.uk rAUA2Tx7051426 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1385805749; bh=5kJPGHKENA8vt7MloY7WKy1zDRcD7UkT8dPyScPeu9k=; h=Date:From:To:Subject:References:In-Reply-To; z=Date:=20Sat,=2030=20Nov=202013=2010:02:20=20+0000|From:=20Matthew =20Seaman=20|To:=20freebsd-pkg@fr eebsd.org|Subject:=20Re:=20[dev]=20about=20unchecked=20functions=2 0calls|References:=20<529909B9.2050007@kaworu.ch>|In-Reply-To:=20< 529909B9.2050007@kaworu.ch>; b=ypVEOXuHBBi7EBw+HH5K6LW02V02K3WY3Q4pSexeRERtiX8DKaIenoMRNzxJUds+O 0rN4FwJAGkXXk2+yaNSOkKBBWWAeZiqiaL/7IHKqiij/ISr0SSAL56h3OPuqekes0o UtlItKIwVjA65ivXgi7oViO1FTcdvEqI0buoQ09s= Message-ID: <5299B7AC.1000603@infracaninophile.co.uk> Date: Sat, 30 Nov 2013 10:02:20 +0000 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: freebsd-pkg@freebsd.org Subject: Re: [dev] about unchecked functions calls References: <529909B9.2050007@kaworu.ch> In-Reply-To: <529909B9.2050007@kaworu.ch> X-Enigmail-Version: 1.6 OpenPGP: id=E7F39EBF Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="JFja7vFwEsiMqbQnGtVDBPWSbrvq7dmd7" X-Virus-Scanned: clamav-milter 0.98 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.16 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: Sat, 30 Nov 2013 10:02:36 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JFja7vFwEsiMqbQnGtVDBPWSbrvq7dmd7 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 29/11/2013 21:40, Alex wrote: > About solutions, the alternatives I have in mind are: >=20 > 1. assume that ENOMEM is fatal. We just abort() as soon as we see it. I= n > that case we should have some kind of xmalloc(3) & Co. and use them > consistently accross all the project. On the pros side it's very easy t= o > do, on the cons it could leave the system in a unclean state (half done= > install / uninstall, corrupted pkg database etc.). abort(3) is almost certainly the wrong answer. If malloc(3) et al fail, then, yes pkg(8) should terminate itself. But it should rollback any pending database transactions and perform other cleanup and generally take care to leave the system in a consistent state. The other critical condition we have to cope with is running out of space on the filesystem. Again the ideal is to leave the system in a consistent state -- no half installed packages and preferably without having deleted a package prior to upgrading it, but failing to install the newer version. (I don't think we can make an absolute guarrantee that won't happen in the general case, but we can make pkg(8) resistant to it (well, we already do), and we could certainly facilitate using features like filesystem snapshots where those are available.) Note 'consistent' here means pretty much treating each package atomically; so we always complete the operation on one package or roll back to the previous one. That's not necessarily going to leave the system in a state with all package dependencies properly fulfilled, but it will mean its in a state where further pkg(8) calls can sort things ou= t. This is by no means an academic consideration: we want to support embedded systems and those may well be quite memory constrained, so handling all that as gracefully as possible is going to be important. > 2. assume that pkg should fail gracefully when ENOMEM occurs. In genera= l > it is considered bad design for a library to abort() (in any case) and > so if part of pkg can be considered as a library (like libpkg suggest b= y > its name) then maybe this is the Right Thing=99 to do. Basically, it me= ans > that functions considered part of the library would return an error cod= e > (EPKG_FATAL) while other "higher part" would gracefully cleanup and exi= t > (using for example err(3)). On the pros side we would have a more robus= t > application, a more reliable library and a cleaner codebase. On the con= s > side it is hard to achieve and time consuming. Yes, indeed. libpkg functions should either succeed or indicate failure by returning an error code. It's up to the calling program to handle the consequences of the failure. > steps could (and should) also be applied for other other calls like > strlcpy(3). However, in order to succeed cooperation is required at Huh? What's wrong with strlcpy(3)? strlcpy is a *good thing* and should be used in preference to strcpy(3) or strncpy(3). Which we generally do already. Similarly snprintf(3) rather than sprintf(3) and similarly bounded functions which won't overrun memory buffers. Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matthew@infracaninophile.co.uk --JFja7vFwEsiMqbQnGtVDBPWSbrvq7dmd7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQJ8BAEBCgBmBQJSmbe0XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATzP8P/2MIfz0+gGN0wX62dj9zNtWv jkqBCWZ+dpaVqy/6RUHQdTVIe4xaidCaBxDS6dx8fXHFzyIS78D03+XRGZm3s/25 BQTqaMi2WdVjddKdYqyAc1omS+VlnhS8x6lVsXpErStO9sxkFNptrNzM0hOxDNAX +9KVhJDfYRqvmvuQxEmVVsjFr2BwOdDa1h8dsUYV97o/QmzIjnfaw99TA/baDuSG H/04GCuEXvcrtf1ZdMguM6Ji8pDVf++EISM/f63d6+m8al2ATkB7giwYhJk6/9E7 onVg4wKv9buJs0jL1spFzqT2nUBmGONkOmycY1qIHE5UNPSABUZZ6L7jLzNSe5l8 Xk+eqsZetRBLstFvJzTJnMlzGnOayNE0kSJD2IYOvCUeYHpE7rU0FcY+0wEwEp9k g4hISd9ncVwTZMkfpcG3RMvihpLuDDZzIBCKbNt/D7XODt/KvJDmMIT4WpHRY+iX x0RoFnw0aqS63u+zzZ6FPV2hnIONsQvQ6/YOhGxDkTjGk8EwcpYbh4PEKuJKU06F zLrq0oRv6I6fQ5Jjc0WgQDNd35pORpwc4k8J/YzkV2zAfXNz0sIATplsV9TOCdFD 9HhCG2zKP1DSC92mh+31kZNLyFUM/MFDuXwJNV174fjcOR2ftjQmkx54Bruxuarn 322zY73mddNXpT8dy9qm =tvkm -----END PGP SIGNATURE----- --JFja7vFwEsiMqbQnGtVDBPWSbrvq7dmd7--