From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Re: [PATCH] po: Drop removed file 'weechat.scm'. Date: Thu, 03 Mar 2016 07:47:13 -0800 Message-ID: <87d1rb5zsu.fsf@gmail.com> References: <1457005486-25235-1-git-send-email-justus@gnupg.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60307) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1abVTB-000739-C8 for guix-devel@gnu.org; Thu, 03 Mar 2016 10:47:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1abVTA-0004nQ-Dc for guix-devel@gnu.org; Thu, 03 Mar 2016 10:47:17 -0500 Received: from mail-pf0-x22d.google.com ([2607:f8b0:400e:c00::22d]:34329) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1abVTA-0004nJ-62 for guix-devel@gnu.org; Thu, 03 Mar 2016 10:47:16 -0500 Received: by mail-pf0-x22d.google.com with SMTP id 4so16929746pfd.1 for ; Thu, 03 Mar 2016 07:47:15 -0800 (PST) In-Reply-To: <1457005486-25235-1-git-send-email-justus@gnupg.org> (Justus Winter's message of "Thu, 3 Mar 2016 12:44:46 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Justus Winter Cc: guix-devel@gnu.org Hi Justus, Is it not necessary to also do something about the other files that mention weechat's prevoius location? For example: --8<---------------cut here---------------start------------->8--- $ grep -r gnu/packages/weechat . ./po/packages/da.po:#: gnu/packages/weechat.scm:92 ./po/packages/da.po:#: gnu/packages/weechat.scm:93 ./po/packages/pl.po:#: gnu/packages/weechat.scm:92 ./po/packages/pl.po:#: gnu/packages/weechat.scm:93 ./po/packages/POTFILES.in:gnu/packages/weechat.scm --8<---------------cut here---------------end--------------->8--- Also, FYI I filed a bug report about this yesterday because I noticed the problem but wasn't sure how to fix it. If you figure out how to fix it, we can probably resolve that! https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22888 Chris