From mboxrd@z Thu Jan 1 00:00:00 1970 From: Subject: bug#33623: Backtrace when running `guix system roll-back' Date: Fri, 7 Dec 2018 18:55:16 +0100 (CET) Message-ID: References: <87k1ko2ois.fsf@tapuakh.i-did-not-set--mail-host-address--so-tickle-me> <<87k1ko2ois.fsf@tapuakh.i-did-not-set--mail-host-address--so-tickle-me> (Diego Nicola Barbato's message of "Wed, 05 Dec 2018 12:36:59 +0100")> <87h8fpfmoj.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_14628_900281125.1544205316800" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47349) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gVKMA-0007KM-DN for bug-guix@gnu.org; Fri, 07 Dec 2018 12:56:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gVKM7-00051p-3i for bug-guix@gnu.org; Fri, 07 Dec 2018 12:56:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:33022) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gVKM6-00051Y-OF for bug-guix@gnu.org; Fri, 07 Dec 2018 12:56:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gVKM6-00016f-MQ for bug-guix@gnu.org; Fri, 07 Dec 2018 12:56:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87h8fpfmoj.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" Cc: 33623-done@debbugs.gnu.org, Diego Nicola Barbato ------=_Part_14628_900281125.1544205316800 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello! This is just an idea. Is it possible to automatize detection of this kind of problems?=20 As I see, some PC can has crontab job to do `guix pull`, so that if 'Backtr= ace' message occurs, it sends a report to developer not to rush up to push = his branch to master branch. Different branches can be defended from such a minor issues, just trying `g= uix pull` for all branches using channels.=20 Dec 7, 2018, 2:15 PM by ludo@gnu.org: > Hi Diego, > > Diego Nicola Barbato <> dnbarbato@posteo.de >= > skribis: > >> When I run =E2=80=98guix system roll-back=E2=80=99 I get the following b= acktrace: >> > > Fixed in commit 6ddc63e599a26c302f74d0622f67cfd987f0dc5f, thanks! > > Ludo'. > ------=_Part_14628_900281125.1544205316800 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello! This is just an idea.
<= /div>
Is it possible to automatize d= etection of this kind of problems?
As I see, some PC can has crontab job to do `guix pull`, so tha= t if 'Backtrace' message occurs, it sends a report to developer not to rush= up to push his branch to master branch.
Different branches can be defended from such a minor issue= s, just trying `guix pull` for all branches using channels.


Dec 7, 20= 18, 2:15 PM by ludo@gnu.org:
Hi Diego,

Diego Nicola Barbato <dnbarbato@posteo.de> sk= ribis:
When I run =E2=80=98guix system roll-back=E2= =80=99 I get the following backtrace:

Fi= xed in commit 6ddc63e599a26c302f74d0622f67cfd987f0dc5f, thanks!
=

Ludo'.

------=_Part_14628_900281125.1544205316800--