From owner-freebsd-pkgbase@freebsd.org Mon May 9 10:49:54 2016 Return-Path: Delivered-To: freebsd-pkgbase@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 900F7B34578 for ; Mon, 9 May 2016 10:49:54 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.229]) by mx1.freebsd.org (Postfix) with ESMTP id 660D61C17 for ; Mon, 9 May 2016 10:49:54 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from [96.28.178.143] ([96.28.178.143:64147] helo=localhost) by dnvrco-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 6B/1A-13014-A4B60375; Mon, 09 May 2016 10:49:46 +0000 Date: Mon, 09 May 2016 10:49:31 +0000 Message-ID: <6B.1A.13014.A4B60375@dnvrco-oedge01> From: "Thomas Mueller" To: freebsd-current@freebsd.org CC: freebsd-pkgbase@freebsd.org Subject: Re: NO_INSTALLEXTRAKERNELS and PkgBase References: <20160506221151.GN1362@FreeBSD.org> <7018EDCD-A567-446D-965C-9E886D543238@gmail.com> <20160507074159.GC47527@FreeBSD.org> X-RR-Connecting-IP: 107.14.64.118:25 X-Authority-Analysis: v=2.1 cv=GMCGE49K c=1 sm=1 tr=0 a=RKm8ZHSrUWUxlfG+7GhaOw==:117 a=RKm8ZHSrUWUxlfG+7GhaOw==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=twB3heYG8Bnj1b6Z6Z4A:9 X-Cloudmark-Score: 0 X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 10:49:54 -0000 I don't really know what to quote here, but the documentation is not clear. There ought to be something in UPDATING. Issue is building and installing more than one kernel. I tried once, and it didn't work right. I had to go back to one kernel at a time and NO_MODULES=yes on second and subsequent to avoid building the same modules redundantly. What now happens on HEAD if I make kernel KERNCONF=SANDY11NC GENERIB ? I don't want to build all modules more than once. GENERIB is modified from GENERIC to remove really drivers for really outdated hardware, such as old SCSI cards, and add some wireless drivers such as rsu. Tom From owner-freebsd-pkgbase@freebsd.org Mon May 9 18:11:13 2016 Return-Path: Delivered-To: freebsd-pkgbase@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 253C9B344C7; Mon, 9 May 2016 18:11:13 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0672118C4; Mon, 9 May 2016 18:11:13 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D41CEB9A3; Mon, 9 May 2016 14:11:11 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org, "freebsd-pkgbase@freebsd.org" Subject: Re: NO_INSTALLEXTRAKERNELS and PkgBase Date: Mon, 09 May 2016 11:05:55 -0700 Message-ID: <3382220.3AgOZzUBmF@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <20160507135005.GN62286@albert.catwhisker.org> References: <20160507135005.GN62286@albert.catwhisker.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 09 May 2016 14:11:11 -0400 (EDT) X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 18:11:13 -0000 On Saturday, May 07, 2016 06:50:05 AM David Wolfskill wrote: > [Recipient list trimmed a bit -- dhw] > > I'm speaking up here because IIRC, I whined to Gleb at what I perceived > to be a POLA violation a while back.... > > On Sat, May 07, 2016 at 09:59:06AM +0200, Ben Woods wrote: > > On 7 May 2016 at 09:48, Ngie Cooper (yaneurabeya) > > wrote: > > > > > glebius changed the defaults to fix POLA, but the naming per the behavior > > > is confusing. Right now the behavior between ^/head and ^/stable/10 > > > before/now match -- I just had to wrap my mind around the default being the > > > affirmative of a negative (i.e. only install one kernel, as opposed to > > > install all extra kernels by default). > > > -Ngie > > > > > > Indeed, I am not sure I understand the POLA violation entirely (ignoring > > the fact that this variable requires affirmation of a negative). > > > > If you list 2 kernels in the KERNCONF variable, why is it astonishing that > > 2 kernels get installed? Even if the old behaviour was to only install 1 > > kernel, if you are listing 2 kernels in KERNCONF presumably that is because > > you want to install 2 kernels? > > Errr... no: I don't. At least, not on the machine where I built them. Then don't pass them to 'installkernel'? That is, I think this makes sense if you want to build N kernels but only install 1: make buildkernel KERNCONF="FOO BAR BAZ" # only install the FOO kernel make installkernel KERNCONF="FOO" And then if you want to install multiple: # install both FOO and BAR kernels make installkernel KERNCONF="FOO BAR" The runaround seems to be whether this last case now should require multiple explicit installkernel invocations which I find inconsistent since the build stage doesn't. I would fully expect 'installkernel' to install all of the kernels listed in KERNCONF and would assume that it is up to the invoker to choose KERNCONF appropriately. -- John Baldwin From owner-freebsd-pkgbase@freebsd.org Mon May 9 18:45:47 2016 Return-Path: Delivered-To: freebsd-pkgbase@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 5E91EB34132; Mon, 9 May 2016 18:45:47 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 281EF1E8B; Mon, 9 May 2016 18:45:46 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id u49Ijip2020173; Mon, 9 May 2016 18:45:44 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id u49Ijiq9020172; Mon, 9 May 2016 11:45:44 -0700 (PDT) (envelope-from david) Date: Mon, 9 May 2016 11:45:44 -0700 From: David Wolfskill To: John Baldwin Cc: freebsd-current@freebsd.org, "freebsd-pkgbase@freebsd.org" Subject: Re: NO_INSTALLEXTRAKERNELS and PkgBase Message-ID: <20160509184544.GU1063@albert.catwhisker.org> Reply-To: freebsd-current@freebsd.org, "freebsd-pkgbase@freebsd.org" Mail-Followup-To: freebsd-current@freebsd.org, "freebsd-pkgbase@freebsd.org" , John Baldwin References: <20160507135005.GN62286@albert.catwhisker.org> <3382220.3AgOZzUBmF@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="HC0F8i/BfMshQzR8" Content-Disposition: inline In-Reply-To: <3382220.3AgOZzUBmF@ralph.baldwin.cx> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 18:45:47 -0000 --HC0F8i/BfMshQzR8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 09, 2016 at 11:05:55AM -0700, John Baldwin wrote: > On Saturday, May 07, 2016 06:50:05 AM David Wolfskill wrote: > > [Recipient list trimmed a bit -- dhw] > ...=20 > > > 2 kernels get installed? Even if the old behaviour was to only instal= l 1 > > > kernel, if you are listing 2 kernels in KERNCONF presumably that is b= ecause > > > you want to install 2 kernels? > >=20 > > Errr... no: I don't. At least, not on the machine where I built them. >=20 > Then don't pass them to 'installkernel'? That is, I think this makes sen= se > if you want to build N kernels but only install 1: >=20 > make buildkernel KERNCONF=3D"FOO BAR BAZ" >=20 > # only install the FOO kernel >=20 > make installkernel KERNCONF=3D"FOO" >=20 > And then if you want to install multiple: >=20 > # install both FOO and BAR kernels >=20 > make installkernel KERNCONF=3D"FOO BAR" I suppose there's probably some way to arrange things so the KERNCONF specification in /etc/src.conf has one value during "buildkernel" and a different value during "inistallkernel" -- but ... seriously...??!? Wouldn't it be cleaner to have different variables (e.g., that could each default to the KERNCONF specification, but could be overridden in a simple text file that doesn't require delving into make(1) arcana to craft or understand)? Why make things harder for folks who are trying to use the system? > The runaround seems to be whether this last case now should require multi= ple > explicit installkernel invocations which I find inconsistent since the bu= ild > stage doesn't. I would fully expect 'installkernel' to install all of the > kernels listed in KERNCONF and would assume that it is up to the invoker = to > choose KERNCONF appropriately. > .... Multiple installkernel invocations is certainly not something I would advocate -- I do silly things sometimes, but I hope nothing I wrote was interpreted thus. :-} Suppose that src/Makefile.inc1 were modified so that: * KERNCONF_BUILD is set to the value (explicit or otherwise) of KERNCONF unless it already has a value (in which case, the explicit value is used). * KERNCONF_INSTALL is set to the value (explicit or otherwise) of KERNCONF unless it already has a value (in which case, the explicit value is used). buildkernel then builds the kernel configs listed in KERNCONF_BUILD; installkernel then installs the kernels listed in KERNCONF_INSTALL. Folks who want to build & install the same set of kernels see no change. Folks who want a difference between "buildkernel" and "installkernel" have a simple way to specify it. Only 1 invocation of installkernel is needed in any case. Would that work? It seems as if that would work for my case. Peace, david --=20 David H. Wolfskill david@catwhisker.org Those who would murder in the name of God or prophet are blasphemous coward= s. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --HC0F8i/BfMshQzR8 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJXMNrYXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XovMH/RgLIQb3OHBChCDDfb8FnV3v VP7E9MMLLLT7JvaSp0HVRyFzQPaCGqZwJi0e1g/UvfcEbUZKtBdRvhGE3FeMP5Ck yzTe5KBtHon9azxnjVjEk0+83d18zNdECxu+mZA4+xT8jKf9n0S7hle2lTGuDpHa q/s8Yn6Iso3pD87Fic4fCBaXHpgreo215lfccri6EbFgrYy0gLUCUA9z/W2gudEi TCzigy3uej6Bt76xPzyLvnGb8Ev4oFcecEkEwVTYQvneOLCNbjbam0UykI+KaHSU 9AJUwSt7giuL44lWtX9pNFL/wfoLWRWcMqYvDmAPmcd+KYxuiQm0cxdY7xAsJ9k= =hnbh -----END PGP SIGNATURE----- --HC0F8i/BfMshQzR8-- From owner-freebsd-pkgbase@freebsd.org Mon May 9 22:18:47 2016 Return-Path: Delivered-To: freebsd-pkgbase@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 41827B35BF1; Mon, 9 May 2016 22:18:47 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 155F017C7; Mon, 9 May 2016 22:18:47 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 2810AB93E; Mon, 9 May 2016 18:18:46 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org, "freebsd-pkgbase@freebsd.org" Subject: Re: NO_INSTALLEXTRAKERNELS and PkgBase Date: Mon, 09 May 2016 12:43:42 -0700 Message-ID: <6691787.Xk1Kup9mab@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: <20160509184544.GU1063@albert.catwhisker.org> References: <3382220.3AgOZzUBmF@ralph.baldwin.cx> <20160509184544.GU1063@albert.catwhisker.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 09 May 2016 18:18:46 -0400 (EDT) X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 22:18:47 -0000 On Monday, May 09, 2016 11:45:44 AM David Wolfskill wrote: > On Mon, May 09, 2016 at 11:05:55AM -0700, John Baldwin wrote: > > On Saturday, May 07, 2016 06:50:05 AM David Wolfskill wrote: > > > [Recipient list trimmed a bit -- dhw] > > ... > > > > 2 kernels get installed? Even if the old behaviour was to only install 1 > > > > kernel, if you are listing 2 kernels in KERNCONF presumably that is because > > > > you want to install 2 kernels? > > > > > > Errr... no: I don't. At least, not on the machine where I built them. > > > > Then don't pass them to 'installkernel'? That is, I think this makes sense > > if you want to build N kernels but only install 1: > > > > make buildkernel KERNCONF="FOO BAR BAZ" > > > > # only install the FOO kernel > > > > make installkernel KERNCONF="FOO" > > > > And then if you want to install multiple: > > > > # install both FOO and BAR kernels > > > > make installkernel KERNCONF="FOO BAR" > > I suppose there's probably some way to arrange things so the KERNCONF > specification in /etc/src.conf has one value during "buildkernel" and a > different value during "inistallkernel" -- but ... seriously...??!? One could do some ugly things with .make() to change the default based on the target being invoked (kind of like folks storing port options in /etc/make.conf conditional on the current directory), but that would be hackish. > Wouldn't it be cleaner to have different variables (e.g., that could > each default to the KERNCONF specification, but could be overridden in > a simple text file that doesn't require delving into make(1) arcana to > craft or understand)? I think having separate variables is fine, and I think your suggestion of KERNCONF_BUILD and KERNCONF_INSTALL that default to KERNCONF would be fine. From the thread, I think it would mean you would need to use the two settings in your /etc/src.conf but that other folks wanting to install both would just stick with KERNCONF, correct? > Multiple installkernel invocations is certainly not something I would > advocate -- I do silly things sometimes, but I hope nothing I wrote was > interpreted thus. :-} FWIW, my wrapper script I use arould buildworld, etc. actually invokes installkernel multiple times (but it also uses buildkernel multiple times as well. I think my script predates multiple kernel support in KERNCONF). > Suppose that src/Makefile.inc1 were modified so that: > * KERNCONF_BUILD is set to the value (explicit or otherwise) of KERNCONF > unless it already has a value (in which case, the explicit value is > used). > * KERNCONF_INSTALL is set to the value (explicit or otherwise) of KERNCONF > unless it already has a value (in which case, the explicit value is > used). > > buildkernel then builds the kernel configs listed in KERNCONF_BUILD; > installkernel then installs the kernels listed in KERNCONF_INSTALL. > > Folks who want to build & install the same set of kernels see no change. > > Folks who want a difference between "buildkernel" and "installkernel" have > a simple way to specify it. > > Only 1 invocation of installkernel is needed in any case. > > Would that work? It seems as if that would work for my case. Yes. I think that is also simpler than having a new WITH/WITHOUT variable to control how installkernel treats KERNCONF. -- John Baldwin From owner-freebsd-pkgbase@freebsd.org Mon May 9 22:27:02 2016 Return-Path: Delivered-To: freebsd-pkgbase@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 669A3B35FAD; Mon, 9 May 2016 22:27:02 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 1FBEB10C7; Mon, 9 May 2016 22:27:01 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id u49MQxbZ022010; Mon, 9 May 2016 22:26:59 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id u49MQxQh022009; Mon, 9 May 2016 15:26:59 -0700 (PDT) (envelope-from david) Date: Mon, 9 May 2016 15:26:59 -0700 From: David Wolfskill To: John Baldwin Cc: freebsd-current@freebsd.org, "freebsd-pkgbase@freebsd.org" Subject: Re: NO_INSTALLEXTRAKERNELS and PkgBase Message-ID: <20160509222659.GB20662@albert.catwhisker.org> Reply-To: freebsd-current@freebsd.org, "freebsd-pkgbase@freebsd.org" Mail-Followup-To: freebsd-current@freebsd.org, "freebsd-pkgbase@freebsd.org" , John Baldwin References: <3382220.3AgOZzUBmF@ralph.baldwin.cx> <20160509184544.GU1063@albert.catwhisker.org> <6691787.Xk1Kup9mab@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="l76fUT7nc3MelDdI" Content-Disposition: inline In-Reply-To: <6691787.Xk1Kup9mab@ralph.baldwin.cx> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2016 22:27:02 -0000 --l76fUT7nc3MelDdI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 09, 2016 at 12:43:42PM -0700, John Baldwin wrote: > ... > > I suppose there's probably some way to arrange things so the KERNCONF > > specification in /etc/src.conf has one value during "buildkernel" and a > > different value during "inistallkernel" -- but ... seriously...??!? >=20 > One could do some ugly things with .make() to change the default based on > the target being invoked (kind of like folks storing port options in > /etc/make.conf conditional on the current directory), but that would be > hackish. Right; "hackish" is probably a bit ... kinder than what came to mind. :-} > > Wouldn't it be cleaner to have different variables (e.g., that could > > each default to the KERNCONF specification, but could be overridden in > > a simple text file that doesn't require delving into make(1) arcana to > > craft or understand)? >=20 > I think having separate variables is fine, and I think your suggestion of > KERNCONF_BUILD and KERNCONF_INSTALL that default to KERNCONF would be > fine. From the thread, I think it would mean you would need to use the > two settings in your /etc/src.conf but that other folks wanting to install > both would just stick with KERNCONF, correct? That is my understanding, yes. I don't mind tweaking things a bit for an uncommon case; I'd rather avoid twisting my mind into a pretzel to do something that's been quite easy historically. :-) > ... > > Would that work? It seems as if that would work for my case. >=20 > Yes. I think that is also simpler than having a new WITH/WITHOUT variable > to control how installkernel treats KERNCONF. > .... Yay...! :-) Peace, david --=20 David H. Wolfskill david@catwhisker.org Those who would murder in the name of God or prophet are blasphemous coward= s. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --l76fUT7nc3MelDdI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJXMQ6yXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4X/aMH/RA4QnvgmPhIqD7ZiUuQ6Tu3 9VXh9y7by0kfidojlNoA/CD1MGnOWigeHMhjgT1TVOgx/Z/J+DyrYRnbJetEf0/+ /ed7dinzdNeWlksW9gTc1ltzAfxf/rqMSXBTSp0/Fk3vrAn9X9sewL45/mbPKjP5 SRlirayuW3wtQx8MNmeaqZUh+JW9qTt1hlYuCHq2kraksyYieGLhApyeIeacTgq+ v98etvJStvRZ0xf59KhxlQ79KaQAue8Qmw0HoT7aJEZK43Klp4AXcfsZMzZhpFg3 jYI34N/ZFrtZJ95ynKir8GNRMipS3dXr14zaTrZ7cCqvCGkF3CdpTR9FjPO0egI= =0lIX -----END PGP SIGNATURE----- --l76fUT7nc3MelDdI--