bug#23971: Nobody has a shell

[Leo Famulari]

On Thu, Jul 14, 2016 at 12:25:57PM +0200, Vincent Legoll wrote:
> > Indeed, fixed in 2d94702ff4133606cda1e51a2c8378a8e79afb9d.
> >
> > The ‘shell’ field was omitted from the definition of “nobody”, which is
> > why it ended up using Bash, which is the default shell.
> 
> Thanks the fix looks good, but I tried with guix system reconfigure
> after guix pull
> That does not change /etc/passwd

I've noticed that certain changes to my own user require reboot.

Others, which involve bringing previously non-Guix controlled user
parameters under control of Guix, seemed to require me to remove the
user from my system configuration, reconfigure, and then re-add the
user. I'm not sure what nobody's GuixSD user configuration would look
like.

Neither is a good solution, but could you try them out?

bug#23984: Bug avr-toolchain

[Ricardo Wurmus]

Daniel Pimentel  writes:

> I'd like report a bug in our avr-toolchain. I try compile to Arduino 
> plataform using Microscheme (installed with: guix package -i 
> microscheme) on GuixSD, but there are errors.
>
> I did:
> sudo microscheme -m UNO -d /dev/ttyACM0 -au lightom.ms
>
> Output:
> ...
> 32 lines compiled OK
> Assembling...
> ...
> avr-ld: cannot find crtatmega328p.o: No such file or directory

This looks like a search path issue.  If you copy this file from the
depths of the output directory to the current directory it should work
fine (works for me).

> ...
> avrdude: Device signature = 0x1e950f
> avrdude: reading input file "lightom.hex"
> avrdude: can't open input file lightom.hex: No such file or directory
> avrdude: read from file 'lightom.hex' failed

These errors will disappear once the above error is fixed.
Thanks for taking care of this!

~~ Ricardo

bug#23971: Nobody has a shell

[Efraim Flashner]

On Thu, Jul 14, 2016 at 12:25:57PM +0200, Vincent Legoll wrote:
> > Indeed, fixed in 2d94702ff4133606cda1e51a2c8378a8e79afb9d.
> >
> > The ‘shell’ field was omitted from the definition of “nobody”, which is
> > why it ended up using Bash, which is the default shell.
> 
> Thanks the fix looks good, but I tried with guix system reconfigure
> after guix pull
> That does not change /etc/passwd
> 
> I tried guix refresh, but got that bt:
> 
> #
> Backtrace:
> In unknown file:
>?: 19 [apply-smob/1 #]
> In ice-9/boot-9.scm:
>   63: 18 [call-with-prompt prompt0 ...]
> In ice-9/eval.scm:
>  432: 17 [eval # #]
> In ice-9/boot-9.scm:
> 2401: 16 [save-module-excursion # ice-9/boot-9.scm:4045:3 ()>]
> 4050: 15 [#]
> 1724: 14 [%start-stack load-stack # ice-9/boot-9.scm:4041:10 ()>]
> 1729: 13 [#]
> In unknown file:
>?: 12 [primitive-load
> "/gnu/store/1g2ygiq4z0b5snnwmddfks4flnippna6-guix-0.10.0-0.e901/bin/.guix-real"]
> In guix/ui.scm:
> 1209: 11 [run-guix-command refresh]
> In ice-9/boot-9.scm:
>  157: 10 [catch srfi-34 # ...]
>  157: 9 [catch system-error ...]
> In guix/scripts/refresh.scm:
>  382: 8 [#]
>  401: 7 [#]
> In srfi/srfi-1.scm:
>  616: 6 [for-each # guix/scripts/refresh.scm:401:22 (package)> ...]
> In guix/scripts/refresh.scm:
>  402: 5 [# #]
> In guix/upstream.scm:
>  135: 4 [package-update-path # #]
> In ice-9/boot-9.scm:
>  157: 3 [catch srfi-34 # guix/import/pypi.scm:313:2 ()> ...]
> In guix/import/pypi.scm:
>  317: 2 [#]
>   68: 1 [latest-source-release #f]
> In unknown file:
>?: 0 [find # #f]
> 
> ERROR: In procedure find:
> ERROR: In procedure find: Wrong type argument in position 2 (expecting list): 
> #f
> #
> 
> What did I do wrong ?
> 
> -- 
> Vincent Legoll
> 

`guix refresh' checks upstream for newer releases of software than
what Guix currently knows, so here it was checking for newer software
from pypi, which hasn't been updated since pypi changed their uri
scheme.

-- 
Efraim Flashner      אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted


signature.asc
Description: PGP signature

bug#23969: hard to understand error message

[Ludovic Courtès]

Hi,

Vincent Legoll  skribis:

> I'm discovering guix, and started to try to package something.
>
> I made an error (add a string URL parameter to license x11-style):
>
> (license x11-style "file://LICENSE")
>
> But this is not working, because I've forgotten the scheme call syntax
> (missing parens)
>
> I'll fix my package definition with:
>
> (license (x11-style "file://LICENSE"))
>
> which seems to be working OK...
>
> But the error message I got was very unhelpful:
>
> something.scm:10:2: warning: source expression failed to match any pattern
>
> the line 10 is:
>   (package
>
> whereas the real error happened on line 32 (the license one)
>
> So what's wrong:
> - wrong line number
> - 'source expression' meaning is shady, as there is a "(source (origin
> ...))" element defined in the package, which is also not on line 10,
> but misleading anyways

Indeed.  This is fixed or at least improved in commit
babc2c80a7e1f1b5e72fd1685ef6604b93157a8e.  Now the message looks like:

--8<---cut here---start->8---
ice-9/psyntax.scm:1422:32: Syntax error:
gnu/packages/idutils.scm:42:4: package: invalid field specifier in form 
(synopsis "Identifier database utilities" foo)
--8<---cut here---end--->8---

Thanks,
Ludo’.

bug#23973: 'guix environment guix' fails with "Argument 1 out of range: 10"

[Andreas Enge]

So closing this bug, simply by a cc to 23973-d...@debbugs.gnu.org.

Andreas

bug#23984: Bug avr-toolchain

[Daniel Pimentel]

Guix,

I'd like report a bug in our avr-toolchain. I try compile to Arduino 
plataform using Microscheme (installed with: guix package -i 
microscheme) on GuixSD, but there are errors.


I did:
sudo microscheme -m UNO -d /dev/ttyACM0 -au lightom.ms

Output:
...
32 lines compiled OK
Assembling...
...
avr-ld: cannot find crtatmega328p.o: No such file or directory
...
avrdude: Device signature = 0x1e950f
avrdude: reading input file "lightom.hex"
avrdude: can't open input file lightom.hex: No such file or directory
avrdude: read from file 'lightom.hex' failed

I have avr-gcc avr-libc avrdude avr-binutils avr-toolchain installed 
(only avr-toolchain is needed).


I'll try debug and fix it.

--
Daniel Pimentel (aka d4n1)

bug#23970: colordiff glitch

[Ludovic Courtès]

Vincent Legoll  skribis:

>>> during "guix package -i colordiff" I saw this error being reported:
>>>
>>> chown: invalid user: ‘root.root’
>>> Makefile:24: recipe for target 'install' failed
>>> make: [install] Error 1 (ignored)
>>> phase `install' succeeded after 0.1 seconds
>>>
>>> But it looks like it is harmless (at least from the guix install PoV)
>>
>> It’s indeed harmless and fine.
>
> The problem I saw here, was that a build *error* is ignored, even if
> in this particular case it
> is harmless. Or maybe chown is kind of special-cased when it is done
> inside /gnu/store ?

The error is purposefully ignored here: upstream’s Makefile explicitly
marks it as can be ignored, using a hyphen (info "(make) Errors").

And indeed, it makes a lot of sense to ignore this error with Guix since
this operation is not permitted.

Hope this clarifies things,
Ludo’.

bug#23979: [ER] guix gc should tell how much space it recovered

[Vincent Legoll]

It already shows:
note: currently hard linking saves 485.41 MiB

Recovered disk space would nicely complement that.

I could be mentored to do it myself, but I'm very new to guile & guix
;-)

I'd at least require high level directions as to where I should look (in
the code) to graft that functionality.

-- 
Vincent Legoll

bug#23971: Nobody has a shell

[Vincent Legoll]

> Indeed, fixed in 2d94702ff4133606cda1e51a2c8378a8e79afb9d.
>
> The ‘shell’ field was omitted from the definition of “nobody”, which is
> why it ended up using Bash, which is the default shell.

Thanks the fix looks good, but I tried with guix system reconfigure
after guix pull
That does not change /etc/passwd

I tried guix refresh, but got that bt:

#
Backtrace:
In unknown file:
   ?: 19 [apply-smob/1 #]
In ice-9/boot-9.scm:
  63: 18 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
 432: 17 [eval # #]
In ice-9/boot-9.scm:
2401: 16 [save-module-excursion #]
4050: 15 [#]
1724: 14 [%start-stack load-stack #]
1729: 13 [#]
In unknown file:
   ?: 12 [primitive-load
"/gnu/store/1g2ygiq4z0b5snnwmddfks4flnippna6-guix-0.10.0-0.e901/bin/.guix-real"]
In guix/ui.scm:
1209: 11 [run-guix-command refresh]
In ice-9/boot-9.scm:
 157: 10 [catch srfi-34 # ...]
 157: 9 [catch system-error ...]
In guix/scripts/refresh.scm:
 382: 8 [#]
 401: 7 [#]
In srfi/srfi-1.scm:
 616: 6 [for-each # ...]
In guix/scripts/refresh.scm:
 402: 5 [# #]
In guix/upstream.scm:
 135: 4 [package-update-path # #]
In ice-9/boot-9.scm:
 157: 3 [catch srfi-34 # ...]
In guix/import/pypi.scm:
 317: 2 [#]
  68: 1 [latest-source-release #f]
In unknown file:
   ?: 0 [find # #f]

ERROR: In procedure find:
ERROR: In procedure find: Wrong type argument in position 2 (expecting list): #f
#

What did I do wrong ?

-- 
Vincent Legoll

bug#23970: colordiff glitch

[Vincent Legoll]

>> during "guix package -i colordiff" I saw this error being reported:
>>
>> chown: invalid user: ‘root.root’
>> Makefile:24: recipe for target 'install' failed
>> make: [install] Error 1 (ignored)
>> phase `install' succeeded after 0.1 seconds
>>
>> But it looks like it is harmless (at least from the guix install PoV)
>
> It’s indeed harmless and fine.

The problem I saw here, was that a build *error* is ignored, even if
in this particular case it
is harmless. Or maybe chown is kind of special-cased when it is done
inside /gnu/store ?

-- 
Vincent Legoll