GNU bug report logs -
#33623
Backtrace when running `guix system roll-back'
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 33623 in the body.
You can then email your comments to 33623 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#33623
; Package
guix
.
(Wed, 05 Dec 2018 11:38:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Diego Nicola Barbato <dnbarbato <at> posteo.de>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 05 Dec 2018 11:38:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello Guix,
When I run ‘guix system roll-back’ I get the following backtrace:
--8<---------------cut here---------------start------------->8---
root <at> tapuakh ~# guix system roll-back
Backtrace:
10 (primitive-load "/root/.config/guix/current/bin/guix")
In guix/ui.scm:
1603:12 9 (run-guix-command _ . _)
In ice-9/boot-9.scm:
829:9 8 (catch srfi-34 #<procedure 341ea60 at guix/ui.scm:615:…> …)
829:9 7 (catch system-error #<procedure 341eb00 at guix/script…> …)
In guix/scripts/system.scm:
1268:8 6 (_)
In guix/status.scm:
615:4 5 (call-with-status-report _ _)
In guix/scripts/system.scm:
1208:9 4 (process-command _ _ _)
469:10 3 (switch-to-system-generation #<build-daemon 256.99 1ec…> …)
In guix/store.scm:
1659:24 2 (run-with-store _ _ #:guile-for-build _ #:system _ # _)
In guix/scripts/system.scm:
499:6 1 (_ _)
In unknown file:
0 (_ #<build-daemon 256.99 1ec03c0>)
ERROR: Wrong type to apply: #<<computed-file> name: "grub.cfg" gexp: #<gexp 3971ab0> guile: #f options: (#:local-build? #t)>
--8<---------------cut here---------------end--------------->8---
I run GuixSD (commit: 1f51f0d975d95a2ba645193cf43d0a294d952e83) on an
x86_64 machine.
Greetings
Diego
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33623
; Package
guix
.
(Wed, 05 Dec 2018 23:57:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 33623 <at> debbugs.gnu.org (full text, mbox):
On 2018-12-05 12:36, Diego Nicola Barbato wrote:
> Hello Guix,
>
> When I run ‘guix system roll-back’ I get the following backtrace:
>
> --8<---------------cut here---------------start------------->8---
> root <at> tapuakh ~# guix system roll-back
> Backtrace:
> 10 (primitive-load "/root/.config/guix/current/bin/guix")
> In guix/ui.scm:
> 1603:12 9 (run-guix-command _ . _)
> In ice-9/boot-9.scm:
> 829:9 8 (catch srfi-34 #<procedure 341ea60 at guix/ui.scm:615:…> …)
> 829:9 7 (catch system-error #<procedure 341eb00 at guix/script…> …)
> In guix/scripts/system.scm:
> 1268:8 6 (_)
> In guix/status.scm:
> 615:4 5 (call-with-status-report _ _)
> In guix/scripts/system.scm:
> 1208:9 4 (process-command _ _ _)
> 469:10 3 (switch-to-system-generation #<build-daemon 256.99 1ec…> …)
> In guix/store.scm:
> 1659:24 2 (run-with-store _ _ #:guile-for-build _ #:system _ # _)
> In guix/scripts/system.scm:
> 499:6 1 (_ _)
> In unknown file:
> 0 (_ #<build-daemon 256.99 1ec03c0>)
>
> ERROR: Wrong type to apply: #<<computed-file> name: "grub.cfg" gexp:
> #<gexp 3971ab0> guile: #f options: (#:local-build? #t)>
> --8<---------------cut here---------------end--------------->8---
>
> I run GuixSD (commit: 1f51f0d975d95a2ba645193cf43d0a294d952e83) on an
> x86_64 machine.
Interesting. Could you provide a config.scm to help us reproduce the
issue?
--
Cheers
Swedebugia
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33623
; Package
guix
.
(Thu, 06 Dec 2018 15:06:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 33623 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello Swedebugia,
swedebugia <at> riseup.net writes:
> On 2018-12-05 12:36, Diego Nicola Barbato wrote:
>> Hello Guix,
>>
>> When I run ‘guix system roll-back’ I get the following backtrace:
>>
>> --8<---------------cut here---------------start------------->8---
>> root <at> tapuakh ~# guix system roll-back
>> Backtrace:
>> 10 (primitive-load "/root/.config/guix/current/bin/guix")
>> In guix/ui.scm:
>> 1603:12 9 (run-guix-command _ . _)
>> In ice-9/boot-9.scm:
>> 829:9 8 (catch srfi-34 #<procedure 341ea60 at guix/ui.scm:615:…> …)
>> 829:9 7 (catch system-error #<procedure 341eb00 at guix/script…> …)
>> In guix/scripts/system.scm:
>> 1268:8 6 (_)
>> In guix/status.scm:
>> 615:4 5 (call-with-status-report _ _)
>> In guix/scripts/system.scm:
>> 1208:9 4 (process-command _ _ _)
>> 469:10 3 (switch-to-system-generation #<build-daemon 256.99 1ec…> …)
>> In guix/store.scm:
>> 1659:24 2 (run-with-store _ _ #:guile-for-build _ #:system _ # _)
>> In guix/scripts/system.scm:
>> 499:6 1 (_ _)
>> In unknown file:
>> 0 (_ #<build-daemon 256.99 1ec03c0>)
>>
>> ERROR: Wrong type to apply: #<<computed-file> name: "grub.cfg" gexp:
>> #<gexp 3971ab0> guile: #f options: (#:local-build? #t)>
>> --8<---------------cut here---------------end--------------->8---
>>
>> I run GuixSD (commit: 1f51f0d975d95a2ba645193cf43d0a294d952e83) on an
>> x86_64 machine.
>
> Interesting. Could you provide a config.scm to help us reproduce the
> issue?
I've got something better.
Steps to reproduce:
Install GuixSD in a VM using the iso image and the attached config. The
image should be at least 16G (8G is to small for a reconfigure).
Reboot the VM.
Run ‘guix pull --commit=1f51f0’ as root.
Make sure to log out and back in again to avoid bug#33647.
Run ‘guix system reconfigure /etc/config.scm’.
Reboot the VM.
Run ‘guix system roll-back’ as root.
Backtrace ensues.
Greetings
Diego
[config.scm (application/octet-stream, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33623
; Package
guix
.
(Fri, 07 Dec 2018 09:45:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 33623 <at> debbugs.gnu.org (full text, mbox):
Diego Nicola Barbato <dnbarbato <at> posteo.de> writes:
> Hello Swedebugia,
>
> swedebugia <at> riseup.net writes:
>
>> On 2018-12-05 12:36, Diego Nicola Barbato wrote:
>>> Hello Guix,
>>>
>>> When I run ‘guix system roll-back’ I get the following backtrace:
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> root <at> tapuakh ~# guix system roll-back
>>> Backtrace:
>>> 10 (primitive-load "/root/.config/guix/current/bin/guix")
>>> In guix/ui.scm:
>>> 1603:12 9 (run-guix-command _ . _)
>>> In ice-9/boot-9.scm:
>>> 829:9 8 (catch srfi-34 #<procedure 341ea60 at guix/ui.scm:615:…> …)
>>> 829:9 7 (catch system-error #<procedure 341eb00 at guix/script…> …)
>>> In guix/scripts/system.scm:
>>> 1268:8 6 (_)
>>> In guix/status.scm:
>>> 615:4 5 (call-with-status-report _ _)
>>> In guix/scripts/system.scm:
>>> 1208:9 4 (process-command _ _ _)
>>> 469:10 3 (switch-to-system-generation #<build-daemon 256.99 1ec…> …)
>>> In guix/store.scm:
>>> 1659:24 2 (run-with-store _ _ #:guile-for-build _ #:system _ # _)
>>> In guix/scripts/system.scm:
>>> 499:6 1 (_ _)
>>> In unknown file:
>>> 0 (_ #<build-daemon 256.99 1ec03c0>)
>>>
>>> ERROR: Wrong type to apply: #<<computed-file> name: "grub.cfg" gexp:
>>> #<gexp 3971ab0> guile: #f options: (#:local-build? #t)>
>>> --8<---------------cut here---------------end--------------->8---
>>>
>>> I run GuixSD (commit: 1f51f0d975d95a2ba645193cf43d0a294d952e83) on an
>>> x86_64 machine.
>>
>> Interesting. Could you provide a config.scm to help us reproduce the
>> issue?
>
> I've got something better.
>
> Steps to reproduce:
>
> Install GuixSD in a VM using the iso image and the attached config. The
> image should be at least 16G (8G is to small for a reconfigure).
>
> Reboot the VM.
>
> Run ‘guix pull --commit=1f51f0’ as root.
>
> Make sure to log out and back in again to avoid bug#33647.
>
> Run ‘guix system reconfigure /etc/config.scm’.
>
> Reboot the VM.
>
> Run ‘guix system roll-back’ as root.
>
> Backtrace ensues.
I just repeated the aforementioned steps with the new (0.16.0) iso image
and by pulling from current master (5118e2) instead of 1f51f0 and got a
similar backtrace. I believe ‘guix system roll-back’ is currently
broken on master.
Judging from the backtrace this might have something to do with the
recent clean up of system code (specifically commit 46c296).
Greetings
Diego
Reply sent
to
Ludovic Courtès <ludo <at> gnu.org>
:
You have taken responsibility.
(Fri, 07 Dec 2018 14:16:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Diego Nicola Barbato <dnbarbato <at> posteo.de>
:
bug acknowledged by developer.
(Fri, 07 Dec 2018 14:16:01 GMT)
Full text and
rfc822 format available.
Message #19 received at 33623-done <at> debbugs.gnu.org (full text, mbox):
Hi Diego,
Diego Nicola Barbato <dnbarbato <at> posteo.de> skribis:
> When I run ‘guix system roll-back’ I get the following backtrace:
Fixed in commit 6ddc63e599a26c302f74d0622f67cfd987f0dc5f, thanks!
Ludo'.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33623
; Package
guix
.
(Fri, 07 Dec 2018 17:56:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 33623-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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 ludo <at> gnu.org:
> Hi Diego,
>
> Diego Nicola Barbato <> dnbarbato <at> posteo.de <mailto:dnbarbato <at> posteo.de>> > skribis:
>
>> When I run ‘guix system roll-back’ I get the following backtrace:
>>
>
> Fixed in commit 6ddc63e599a26c302f74d0622f67cfd987f0dc5f, thanks!
>
> Ludo'.
>
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33623
; Package
guix
.
(Fri, 07 Dec 2018 22:25:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 33623-done <at> debbugs.gnu.org (full text, mbox):
Hello,
<znavko <at> tutanota.com> skribis:
> 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.
There are lots of unit tests and system tests in Guix. Unfortunately
this particular bit is not covered by a test. We would need to come up
with a testing strategy for this but it can be quite challenging.
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33623
; Package
guix
.
(Sat, 08 Dec 2018 09:46:02 GMT)
Full text and
rfc822 format available.
Message #28 received at 33623 <at> debbugs.gnu.org (full text, mbox):
On 2018-12-07 15:15, Ludovic Courtès wrote:
> Hi Diego,
>
> Diego Nicola Barbato <dnbarbato <at> posteo.de> skribis:
>
>> When I run ‘guix system roll-back’ I get the following backtrace:
>
> Fixed in commit 6ddc63e599a26c302f74d0622f67cfd987f0dc5f, thanks!
>
> Ludo'.
Good catch Diego!
--
Cheers
Swedebugia
Information forwarded
to
bug-guix <at> gnu.org
:
bug#33623
; Package
guix
.
(Sat, 08 Dec 2018 09:46:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 05 Jan 2019 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 5 years and 84 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.