mutt builds to fail on a barebones sytem

mutt builds to fail on a barebones sytem

[Carlos Sánchez de La Lama]

Hi all,

in my new system (almost identical to the barebones template), mutt does
not build:

--8<---------------cut here---------------start------------->8---
$ guix package -i mutt

...

chgrp: invalid group: ‘mail’
Can't fix mutt_dotlock's permissions!  This is required to lockmailboxes in the mail spool directory.
Makefile:1337: recipe for target 'install-exec-hook' failed
--8<---------------cut here---------------end--------------->8---

I have tried looking for a module which creates the mail group but I
have not found it. Do I need to add "mail" to groups field on system
definition? Or is it somehow automatically added it mutt is added at the
system level?

Thanks!

Carlos

Re: mutt builds to fail on a barebones sytem

[ng0]

Hi,

Carlos Sánchez de La Lama writes:

> Hi all,
>
> in my new system (almost identical to the barebones template), mutt does
> not build:
>
> $ guix package -i mutt
>
> ...
>
> chgrp: invalid group: ‘mail’
> Can't fix mutt_dotlock's permissions!  This is required to lockmailboxes in the mail spool directory.
> Makefile:1337: recipe for target 'install-exec-hook' failed

This is most strange. On my GuixSD system mutt was able to
builtand install, but this was earliest on June 21th or 29th or
sometime between those dates.

> I have tried looking for a module which creates the mail group but I
> have not found it. Do I need to add "mail" to groups field on system
> definition? Or is it somehow automatically added it mutt is added at the
> system level?
>
> Thanks!
>
> Carlos
>

Could you provide some more info and maybe the system definition
you use?
I don't use the barebones template here, but with your system
definition file someone could reproduce the problem in a VM.

-- 
♥Ⓐ  ng0
For non-prism friendly talk find me on http://www.psyced.org
SecuShare – http://secushare.org

Re: mutt builds to fail on a barebones sytem

[Leo Famulari]

On Thu, Jul 14, 2016 at 05:14:19PM +0200, Carlos Sánchez de La Lama wrote:
> Hi all,
> 
> in my new system (almost identical to the barebones template), mutt does
> not build:
> 
> --8<---------------cut here---------------start------------->8---
> $ guix package -i mutt
> 
> ...
> 
> chgrp: invalid group: ‘mail’
> Can't fix mutt_dotlock's permissions!  This is required to lockmailboxes in the mail spool directory.
> Makefile:1337: recipe for target 'install-exec-hook' failed
> --8<---------------cut here---------------end--------------->8---

Strange, it works for me on GuixSD (where I don't have a 'mail' group)
and also with Guix on Debian.

Can you give some more information about your setup?

Re: mutt builds to fail on a barebones sytem

[Carlos Sánchez de La Lama]

[-- Attachment #1: Type: text/plain, Size: 875 bytes --]

>> in my new system (almost identical to the barebones template), mutt does
>> not build:
>> 
>> --8<---------------cut here---------------start------------->8---
>> $ guix package -i mutt
>> 
>> ...
>> 
>> chgrp: invalid group: ‘mail’
>> Can't fix mutt_dotlock's permissions!  This is required to lockmailboxes in the mail spool directory.
>> Makefile:1337: recipe for target 'install-exec-hook' failed
>> --8<---------------cut here---------------end--------------->8---
>
> Strange, it works for me on GuixSD (where I don't have a 'mail' group)
> and also with Guix on Debian.

Seems it happens on some other systems as well (see "Misc. errors" on
this report:
https://lists.gnu.org/archive/html/guix-devel/2016-01/msg00237.html) 

> Can you give some more information about your setup?

My system is nothing strange, I attach the definition.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: config.scm --]
[-- Type: text/x-scheme, Size: 1693 bytes --]

;; This is an operating system configuration template
;; for a "bare bones" setup, with no X11 display server.

(use-modules (gnu))
(use-service-modules networking ssh)
(use-package-modules admin)

(operating-system
  (host-name "gollum")
  (timezone "Europe/Madrid")
  (locale "es_ES.UTF-8")

  ;; Assuming /dev/sdX is the target hard disk, and "my-root" is
  ;; the label of the target root file system.
  (bootloader (grub-configuration (device "/dev/sda")))
  (file-systems (cons (file-system
                        (device "my-root")
                        (title 'label)
                        (mount-point "/")
                        (type "ext4"))
                      %base-file-systems))

  ;; This is where user accounts are specified.  The "root"
  ;; account is implicit, and is initially created with the
  ;; empty password.
  (users (cons (user-account
                (name "csanchez")
                (comment "Carlos Sanchez de La Lama")
                (group "users")

                ;; Adding the account to the "wheel" group
                ;; makes it a sudoer.  Adding it to "audio"
                ;; and "video" allows the user to play sound
                ;; and access the webcam.
                (supplementary-groups '("wheel"
                                        "audio" "video"))
                (home-directory "/home/csanchez"))
               %base-user-accounts))

  ;; Globally-installed packages.
  (packages (cons tcpdump %base-packages))

  ;; Add services to the baseline: a DHCP client and
  ;; an SSH server.
  (services (cons* (dhcp-client-service)
                   (lsh-service #:port-number 2222)
                   %base-services)))

[-- Attachment #3: Type: text/plain, Size: 1492 bytes --]


I think I can shed some light on the problem. *If* during mutt configure
step, "/var/mail" is found to be group-writable, then mutt makefiles
decide mutt has to be setgid, to group "mail" unless overriden by
configure parameters. If "/var/mail" is not group-writable, then mutt is
built without setgid.

This is performed by a test program in configure.ac which is:

--8<---------------cut here---------------start------------->8---
#include <sys/stat.h>
#include <stdlib.h>

int main (int argc, char **argv)
{
        struct stat s;

        stat ("$mutt_cv_mailpath", &s);
        if (s.st_mode & S_IWGRP) exit (0);
        exit (1);
}
--8<---------------cut here---------------end--------------->8---

where $mutt_cv_mailpath is "/var/mail" (passed as configure parameter).

The problem happens when "/var/mail" does not exist. "stat" return value
is not checked, so whatever garbage happens to be in s.st_mode can
randomly lead to detecting it as group-writable or not.

If I create "/var/mail" on my system, I can build & install mutt in
"guix environment mutt". However, building in the chroot (with "guix
build") still fails. I am reaching the limits of my guix knowledge
here... how/where are chroot contents defined?

I was going to report the bug to mutt (strictly speaking, it's theirs),
but seems it was already reported *and fixed* as bug #3810:

https://dev.mutt.org/trac/ticket/3810

So reconfiguring with an updated tree would fix my problem (it's
building now).

BR

Carlos

Re: mutt builds to fail on a barebones sytem

[Carlos Sánchez de La Lama]

> So reconfiguring with an updated tree would fix my problem (it's
> building now).

I can confirm newer mutt versions used in current guix snapshot do not
suffer from this building problem.

I am sorry about the noise :S

BR

Carlos

Re: mutt builds to fail on a barebones sytem

[Ludovic Courtès]

Hi!

csanchezdll@gmail.com (Carlos Sánchez de La Lama) skribis:

> I think I can shed some light on the problem. *If* during mutt configure
> step, "/var/mail" is found to be group-writable, then mutt makefiles
> decide mutt has to be setgid, to group "mail" unless overriden by
> configure parameters. If "/var/mail" is not group-writable, then mutt is
> built without setgid.
>
> This is performed by a test program in configure.ac which is:
>
> #include <sys/stat.h>
> #include <stdlib.h>
>
> int main (int argc, char **argv)
> {
>         struct stat s;
>
>         stat ("$mutt_cv_mailpath", &s);
>         if (s.st_mode & S_IWGRP) exit (0);
>         exit (1);
> }
>
> where $mutt_cv_mailpath is "/var/mail" (passed as configure parameter).
>
> The problem happens when "/var/mail" does not exist. "stat" return value
> is not checked, so whatever garbage happens to be in s.st_mode can
> randomly lead to detecting it as group-writable or not.

Terrible.

> If I create "/var/mail" on my system, I can build & install mutt in
> "guix environment mutt". However, building in the chroot (with "guix
> build") still fails. I am reaching the limits of my guix knowledge
> here... how/where are chroot contents defined?

The chroot content is described in the bullet list at:

  https://www.gnu.org/software/guix/manual/html_node/Build-Environment-Setup.html

The code that populates it is in nix/libstore/build.cc:1825.

There’s no /var in the chroot.

> I was going to report the bug to mutt (strictly speaking, it's theirs),
> but seems it was already reported *and fixed* as bug #3810:
>
> https://dev.mutt.org/trac/ticket/3810
>
> So reconfiguring with an updated tree would fix my problem (it's
> building now).

Great.

Thanks,
Ludo’.

Re: mutt builds to fail on a barebones sytem

[Carlos Sánchez de La Lama]

Hi Ludo,

>> how/where are chroot contents defined?
>
> The chroot content is described in the bullet list at:
>
>   https://www.gnu.org/software/guix/manual/html_node/Build-Environment-Setup.html

Yes, but description is a bit abstract. I wanted to know the exact details.

> The code that populates it is in nix/libstore/build.cc:1825.

Thanks! I was unable to find it.

Carlos