From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6487873561298993152 X-Received: by 10.80.167.162 with SMTP id i31mr4161657edc.9.1510648982897; Tue, 14 Nov 2017 00:43:02 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.80.241.28 with SMTP id w28ls14567666edl.6.gmail; Tue, 14 Nov 2017 00:43:02 -0800 (PST) X-Google-Smtp-Source: AGs4zMZIRouw6WxkvJ+jxa92q4yeRF2qWsIwzZDGF3nb4ck53etjEpaGrXi5b20CcCV4DmeYRnDh X-Received: by 10.80.151.161 with SMTP id e30mr2405697edb.4.1510648982603; Tue, 14 Nov 2017 00:43:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510648982; cv=none; d=google.com; s=arc-20160816; b=nxSk0TrhRLtWEKGk9az3Gth/DoaQa5kNus0sbOQleh8LOJW8QOvSK6zBs5J5hWZR4y wk3ef1sWpbEWKYarGrUZ1e7r763hLJK2+hOecfyQl3L3wktqV6pyGRQ6tyghk1b0asxa RQA7Y1l+68kJt2d4s3YWDzubpyjy4JX7G60g7D2Iz98rUo01B0mghFvAq2+rOOsRloZV wJHXuFzM6FZBUWYG2qOQSMQ21eCamQTzxbokoJaO88KfXwrUw3aUdnenYDd/d2aO1aHM rnxfJ6oFZiodLUTnKIQgQpd8gf1SnSTMttoIVG8dusR4Sh5m3pVmIqE6ipz9ys2+Jd72 thkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:mail-followup-to:message-id :subject:to:from:date:arc-authentication-results; bh=JQwiTSP9aw/LYAg9IN3Yg1xa2S6yewXs4P9QcqvgnK8=; b=xYc794hJuM+RhQqNJ2INRqqCMVcCCsoiPyUwIcMdAzjSJn6O5MEhY0qaCyxbEdGkyi WPIpxfWvLefDG4wek01VHe3HBVwj48xOcjNRSkLZW7GEfIlREP/Xd/lVzT9tJtS5aekV oGPWipGJl9JR/OaUZK2o+mkj4tDmAfZrK4bv9qLljtqwHkR7QlbvM7xKLGUgbkV5uLn5 XzWS7QxLB5oQ6zyIamnwR593J6eMP1yvlcyX5bBtm1PcP7U4s3t8lRTqDK8iwTRuEm8Z xQlryz++vYipN/WHMC7iUyKkYvexcy1nPF6UFoR+rSqICN7iN5HT1VPbKLY2r1aHGavd Nx7w== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of christian.storm@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=christian.storm@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id h23si1849321ede.4.2017.11.14.00.43.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Nov 2017 00:43:02 -0800 (PST) Received-SPF: pass (google.com: domain of christian.storm@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of christian.storm@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=christian.storm@siemens.com Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id vAE8h2O9022310 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 14 Nov 2017 09:43:02 +0100 Received: from localhost ([139.25.69.251]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTPS id vAE8h1Um009851 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 14 Nov 2017 09:43:02 +0100 Date: Tue, 14 Nov 2017 09:41:52 +0100 From: Christian Storm To: isar-users@googlegroups.com Subject: Re: [PATCH] build.sh: Fix perl complaints about locale Message-ID: <20171114084152.dc56j6m5witxtn7c@MD1KR9XC.ww002.siemens.net> Mail-Followup-To: isar-users@googlegroups.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1d007209-046a-381e-341d-ba5735be5ad2@ilbers.de> User-Agent: Mutt/20170113 (1.7.2) X-TUID: biJpiWcyvy3o > >>> [...] > >>> > >>> Not sure what "ignorenativearch" does, but "sed /etc/locale.gen && > >>> locale-gen" is clearer and probably free of side-effects. Are we > >>> sure about all implications of ignorenativearch? > >> > >> To be honest, I don't exactly know what multistrap does in native > >> mode (to be investigated), but with "ignorenativearch=true" we can > >> guarantee that Isar has the same build flow for *all* the > >> architectures. Otherwise we will have 2 possible flows: for native > >> arch and for foreign archs, what could be the source of potential > >> bugs like we have now with locales. > > > > True, but without that knowledge and looking at the one issue, i would > > prefer that patch that i understand ;). > > > > Yeah, but on the other hand: > - There is dedicated code which should setup locales, seems it's > broken in master for native builds now. > - Instead of fixing it, yet another locale setup is proposed. Well, strictly speaking, it's not yet another locale setup. If you do the `sed` and `dpkg-reconfigure locale` it's merely an explicit setup, more of the same so to say. The `dpkg --configure -a` at the bottom of configscript.sh may not *re-*configure a (wrongly) configured locale package. > - This new locale setup affects already working builds. Yes, to the extent that after locale setup, a *re-*configure is explicitly triggered. Shouldn't be a problem but instead intended behavior as you may have changed the locale in configscript.sh above this line nonetheless. > - Old locale stays in the tree. With my commit ec997ad "isar-image-base: purge locales and installed packages' .deb", unused locale are purged. Or didn't I get the point here? > So, for me it would be better to spend a few hours to understand > 'ignorenativearch' option before taking any decision. I'd happy to this :-) Independently of the issue at hand, this is a very welcome proposal of yours! I'd like to hear the results... That said, from a quick multistrap manpage glimpse, I read "A native multistrap can be used directly with chroot, so "multistrap" runs "dpkg --configure -a" at the end of the multistrap process, unless the ignorenativearch option is set to true in the General section of the configuration file." So, on native multistrap, `dpkg --configure -a` is run if ignorenativearch=false. Otherwise, if ignorenativearch=true, it's not run. However, `dpkg --configure -a` is run unconditionally in configscript.sh... Besten Gru�, Christian -- Dr. Christian Storm Siemens AG, Corporate Technology, CT RDA ITP SES-DE Otto-Hahn-Ring 6, 81739 M�nchen, Germany