bug#22492: create new user guixsd

2016-02-01 Thread Ludovic Courtès
ren...@openmailbox.org skribis:

> i run 'guix system reconfigure config.scm --falback', and add new
> user: tron.

How did you add the new user account?  You added it in the
‘operating-system’ declaration and then run ‘guix system reconfigure’,
right?

> When i try to login such as tron does not allow login and slim restart.
>
> i check secure and slim.log log files, this message appears in slim.log:
>
> slim: pam_authentication(): User not known to the underlying
> authentication module
>
> The solution to fix this issue was: changing the owner:group for the
> home user.

Could it be that /home is on a separate partition?  There’s a problem
when that is the case: .

Thanks,
Ludo’.





bug#22492: create new user guixsd

2016-02-01 Thread rennes

Hi ludo,

On 2016-01-31 17:29, l...@gnu.org wrote:

ren...@openmailbox.org skribis:


i run 'guix system reconfigure config.scm --falback', and add new
user: tron.


How did you add the new user account?  You added it in the
‘operating-system’ declaration and then run ‘guix system reconfigure’,
right?

When i try to login such as tron does not allow login and slim 
restart.


i check secure and slim.log log files, this message appears in 
slim.log:


slim: pam_authentication(): User not known to the underlying
authentication module

The solution to fix this issue was: changing the owner:group for the
home user.


Could it be that /home is on a separate partition?  There’s a problem
when that is the case: .

Thanks,
Ludo’.


i replace bob user with tron in the configuration file, and later i 
reconfigure. And i have only root partition.


Thanks








bug#22492: create new user guixsd

2016-02-01 Thread rennes

Hi,

On 2016-02-01 01:55, Leo Famulari wrote:

On Sat, Jan 30, 2016 at 03:48:26AM +0100, ren...@openmailbox.org wrote:

Hi,

i run 'guix system reconfigure config.scm --falback', and add new 
user:

tron.

When i try to login such as tron does not allow login and slim 
restart.


i check secure and slim.log log files, this message appears in 
slim.log:


slim: pam_authentication(): User not known to the underlying 
authentication

module

The solution to fix this issue was: changing the owner:group for the 
home

user.

cd /home
chown -Rf 30019:users tron


If I am reading this correctly, it means that you changed ownership of
all files in /home to the "tron" user. In general that seems like a bad
idea. What about other users?



and works.






In the new generations the user are created but do not enter.

Thanks







bug#22514: emacs INFO pages have "?"s instead of "'"s

2016-02-01 Thread myglc2
myglc2  writes:

> In emacs INFO pages, single quotes "'" appear as question marks "?" and
> 'echo $LANG' returns a blank line.

Note/clarification: the problem is only with user accounts. root emacs
INFO "'" quotes are normal and 'echo $LANG' returns "en_US.UTF-8".

> I am running guixSD on a headless server & logging in via the iTerm2
> terminal emulator running on Max OS X... e.g. 'ssh' & 'emacs -nw'
>
> When I log into an identical server running Debian 8, emacs INFO "'"
> quotes are normal and 'echo $LANG' returns "en_US.UTF-8".
>
> ITerm is set to UTF-8 and xterm-256color.
>
> I am running the configuration shown below built earlier today as shown
> further below.
>
> Note: I also tried the alternate form, '(locale "en_US.utf8")', which is
> commented out in the config, and observed the same behavior.
>
> Many Thanks - George
>
> config.9.scm:
> vv
> vv
> ;; 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)
> (use-package-modules disk ssh rsync wget screen)
> (use-package-modules emacs)
> (use-package-modules guile)
> (use-package-modules version-control)
> (use-package-modules graphviz)
>
> (operating-system
>   (host-name "g1")
>   (timezone "America/New_York")
>   (locale "en_US.UTF-8")
>   ;; (locale "en_US.utf8")
>
>   ;; Assuming /dev/sdX is the target hard disk, and "root" is
>   ;; the label of the target root file system.
>   (bootloader (grub-configuration (device "/dev/sda")))
>   (file-systems (cons (file-system
> (device "g1sd")
> (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 "glc")
> (comment "g l c")
> (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/glc"))
>%base-user-accounts))
>
>   ;; Globally-installed packages.
>   (packages (cons*
>glibc-utf8-locales
>parted
>openssh
>rsync
>wget
>screen
>emacs
>;; emacs-flycheck
>emacs-w3m geiser git-modes guile-emacs guile-for-guile-emacs magit 
> paredit
>git git-manpages magit
>graphviz
>%base-packages
>)
>   )
>
>   ;; Add services to the baseline: a DHCP client and
>   ;; an SSH server.
>   (services (cons* (dhcp-client-service)
>(lsh-service #:port-number 22)
>%base-services)))
> ^^
> ^^
>
>
> root@g1 ~# guix pull
>
> Starting download of /tmp/guix-file.wq8eGI
> From http://git.savannah.gnu.org/cgit/guix.git/snapshot/master.tar.gz...
>  master.tar.gz   1.8MiB/s 00:05 | 9.7MiB 
> transferred
> unpacking '/gnu/store/z7fyrgm8f03ns5ils40cw0p1480ddh99-guix-latest.tar.gz'...
> Guix already up to date
> root@g1 ~# guix system reconfigure config.9.scm
> substitute: updating list of substitutes from 'http://hydra.gnu.org'... 100.0%
> The following derivation will be built:
>/gnu/store/s70k68pvgnc72vzbqldfns0qinh4563k-grub.cfg.drv
> /gnu/store/gla18i7ii7krc548j0yskg834i6d8fxv-system
> /gnu/store/wx2piqvbys781q2k4f2k6gpjp0dpf2xb-grub.cfg
> /gnu/store/6jdnd5c830qggwdmrkfl6kgz79jxymzy-grub-2.00
> activating system...
> setting up setuid programs in '/run/setuid-programs'...
> populating /etc from /gnu/store/z9c8lfifwbgcwrlsvhr10s6vjbnkjz43-etc...
> usermod: no changes
> usermod: no changes
> usermod: no changes
> making '/gnu/store/gla18i7ii7krc548j0yskg834i6d8fxv-system' the current 
> system...
> Installation finished. No error reported.
> root@g1 ~# exit
> exit
>
> Process shell finished





bug#22533: Non-determinism in python-3 ".pyc" bytecode

2016-02-01 Thread Leo Famulari
While preparing a package for borg [0], I found that the built output
was not reproducible. The problem is that the bytecode compiler [1] for
Python 3.4.3 (our current version) encodes the mtime of the
corresponding Python source file in the output. This is described in
PEP-3147 [2], and the responsible Python code is referenced below [3].

I tested a few of our existing python-3 packages: python-ccm,
python-pysam, and python-scripttest all exhibit the same problem.

We fixed this in python-2 with the patch
python-2.7-source-date-epoch.patch, but I don't know how to write this
patch for python-3.

Can somebody write this patch?

I asked about this on #debian-reproducible and they said that it wasn't
an issue for Debian since they don't ship bytecode, but instead generate
it at install time. Of course, that doesn't really apply to Guix.

I used diffoscope-34 to inspect the build outputs to find this, and you
can see the report here:
https://famulari.name/misc/7c55c9e97f668234ddea50299d986f14/borg-diffoscope-report.html

It's first demonstrated in the file
...-borg-0.30.0/lib/python3.4/site-packages/__pycache__/site.cpython-34.pyc.

The first 2 bytes are the "magic numbers" described in PEP-3147, which
specify the version of the bytecode format. The next 2 bytes are the
problematic timestamp, as described in the PEP-3147.

[0]
http://borgbackup.github.io/

[1]
https://docs.python.org/3/library/py_compile.html

[2]
https://www.python.org/dev/peps/pep-3147/

[3] Check out the Guix git commit 4efc8eb27502c, and from there:
$ tar xf $(./pre-inst-env guix build --source python-3)
$ sed -n 139,140p Python-3.4.3/Lib/py_compile.py
bytecode = importlib._bootstrap._code_to_bytecode(
code, source_stats['mtime'], source_stats['size'])