From mboxrd@z Thu Jan 1 00:00:00 1970 From: EuAndreh via Subject: Files not .gitignored when contributing to Guix Date: Fri, 17 Jan 2020 15:57:56 -0300 Message-ID: <8736cdewqz.fsf@euandre.org> Reply-To: EuAndreh Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:36485) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1isWok-00044B-SK for Help-Guix@gnu.org; Fri, 17 Jan 2020 13:58:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1isWoj-0005wp-9X for Help-Guix@gnu.org; Fri, 17 Jan 2020 13:58:02 -0500 Received: from box.euandre.org ([162.243.185.39]:38093) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1isWoj-0005w9-5U for Help-Guix@gnu.org; Fri, 17 Jan 2020 13:58:01 -0500 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane-mx.org@gnu.org Sender: "Help-Guix" To: help-guix Hi Guix! When running the setup steps to prepare a patch, I find myself with a dirty repository of changed files. Is this expected behaviour? I couldn't find guidance regarding that on the manual or the mailing list archives (only a similar issue[0]), and I wonder if is there a way to avoid it, or should I just get used to it? Is there something missing for things being this way that I didn't get yet? The output of make spits some warning regarding outdated .po files. If the dirty files are generated, should they even be commited in the repository if they are derived data? Looking at the diff, it confirms this hypothesis: the diff of the .po files contain mostly generated translation strings and timestamps. The setup steps I use are: --8<---------------cut here---------------start------------->8--- cd $GUIX_REPO git clean -ffdx guix environment guix --ad-hoc help2man git strace ./bootstrap ./configure --localstatedir=3D/var make --8<---------------cut here---------------end--------------->8--- At the end the dirty files are: --8<---------------cut here---------------start------------->8--- $ git status Sur la branche master Modifications qui ne seront pas valid=C3=A9es : (utilisez "git add ..." pour mettre =C3=A0 jour ce qui sera vali= d=C3=A9) (utilisez "git restore ..." pour annuler les modifications dans = le r=C3=A9pertoire de travail) modifi=C3=A9=C2=A0: po/guix/cs.po modifi=C3=A9=C2=A0: po/guix/da.po modifi=C3=A9=C2=A0: po/guix/de.po modifi=C3=A9=C2=A0: po/guix/eo.po modifi=C3=A9=C2=A0: po/guix/es.po modifi=C3=A9=C2=A0: po/guix/fr.po modifi=C3=A9=C2=A0: po/guix/hu.po modifi=C3=A9=C2=A0: po/guix/pl.po modifi=C3=A9=C2=A0: po/guix/pt_BR.po modifi=C3=A9=C2=A0: po/guix/sr.po modifi=C3=A9=C2=A0: po/guix/sv.po modifi=C3=A9=C2=A0: po/guix/vi.po modifi=C3=A9=C2=A0: po/guix/zh_CN.po modifi=C3=A9=C2=A0: po/packages/da.po modifi=C3=A9=C2=A0: po/packages/de.po modifi=C3=A9=C2=A0: po/packages/eo.po modifi=C3=A9=C2=A0: po/packages/es.po modifi=C3=A9=C2=A0: po/packages/fr.po modifi=C3=A9=C2=A0: po/packages/hu.po modifi=C3=A9=C2=A0: po/packages/pl.po modifi=C3=A9=C2=A0: po/packages/pt_BR.po modifi=C3=A9=C2=A0: po/packages/sr.po modifi=C3=A9=C2=A0: po/packages/vi.po modifi=C3=A9=C2=A0: po/packages/zh_CN.po aucune modification n'a =C3=A9t=C3=A9 ajout=C3=A9e =C3=A0 la validation (ut= ilisez "git add" ou "git commit -a") --8<---------------cut here---------------end--------------->8--- I'm looking to a better way to handle this situation (that I find a bit of a nuisance right now) or maybe just an explanation behind the way things currently are. Thanks :) EuAndreh [0]: https://lists.gnu.org/archive/html/guix-devel/2018-12/msg00387.html