[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#33623: Backtrace when running `guix system roll-back'
From: |
znavko |
Subject: |
bug#33623: Backtrace when running `guix system roll-back' |
Date: |
Fri, 7 Dec 2018 18:55:16 +0100 (CET) |
Hello! This is just an idea.
Is it possible to automatize detection of this kind of problems?
As I see, some PC can has crontab job to do `guix pull`, so that 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 issues, just trying `guix pull` for all branches using channels.
Dec 7, 2018, 2:15 PM by address@hidden:
Hi Diego,
When I run ‘guix system roll-back’ I get the following backtrace:
Fixed in commit 6ddc63e599a26c302f74d0622f67cfd987f0dc5f, thanks!
Ludo'.